Related
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
I would get nvflash set up with bekit's images and flash that to get yourself back to a working stock image. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=861950
After that, put Clockworkmod ( v .8, get it from development forum) on it and repartition your sdcard to 2048 and 0 then you should be ready to flash.
Then get a ROM from the development forum here, there are some based off cm7 (gingerbread builds).
I was hoping not to have to use NVflash cuz people report problems with the boot loop, however I havent found any other option so far so I guess i'm trying that. Thanks for the link.
Xxlgeek,
Every time I hear boot loop I think re-partition -- because most of the time that
seems to fix the problem.
I agree you should NVFlash to get a stock version working. Then install CWM so
you can partition -- and the do the Fix Permissions, Wipe Dalvik Cache, Wipe
Cache, Wipe Factory Data.
With that I would try to wind up with a stock machine and let it OTA up to 3588.
I wouldn't load another Alternate Rom until I knew my tablet is working good and
until I know a lot more about the roms and how to work with the G-Tablet.
IMHO.
Rev
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Xxlgeek,
If it didn't work, I would erase the Cyanogenmod 7 file -- and I would go back to a stock rom until I could make sure all the hardware is working right and the system
is stable.
When you know the tablet is good and stable, you can always download and re-do.
Rev
Xxlgeek said:
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1021978
you are not alone...
it may have to do with the boot loader .... further investigation needed. CW does not replace this but the stock does I have been running the old one since december on my personal tab. but most of these woot pads are updated .... hmmmmmm
Xxlgeek said:
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Click to expand...
Click to collapse
Which version of CM7 are you running?
jivy26 said:
Which version of CM7 are you running?
Click to expand...
Click to collapse
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Just throwing this out there. I bought 2 from Woot myself. On my first G-Tab I had the same issue with every single ROM I tried. I finally used NVFlash to go back to stock and everything was good again. I then flashed to the G-Harmony Gingerbread ROM and it worked and still runs like a CHAMP. Now, I finally get the other G-Tab out and start to go through the same routine as the first and it's been a no go repeatedly. I have mostly been trying with the Cyanogen 7 Final ROM to no avail and even with the G-Harmony. Going to try NVFlash on number 2 tab and see what the result is and will post back in a bit with updates.
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
tunez23 said:
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
Click to expand...
Click to collapse
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Did you extract both archives to the same directory on your computer?
akodoreign said:
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Click to expand...
Click to collapse
2 partitions are reversed and Gingerbread roms don't like it. Using bekits original nvflash files will fix the partitioning permanently as far as flashing between froyo and gingerbread.
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Edit.....This is not all tablets. I'm guessing around 30% or so have the 2 reversed partitions but it seems 50% of the woot tabs. Helped fix many of these on irc in the last 2 weeks
KrazyOne7 said:
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Click to expand...
Click to collapse
Having the same problem too!! Any help would be much appreciated.
Tried wiping everything with FORMAT.zip from another thread, and get and error for unknown device when running that *.bat file.
This newbie needs some serious help!
Locked bootloader??!
thebadfrog said:
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Click to expand...
Click to collapse
I think I must have the locked bootloader, but tried both Gojimis's fix and nvflash fix and get the error as mentioned above.
So I am getting nowhere, won't go past the "booting..." splash screen to install any of the update.zip files from the microSD card.
Help!
K J Rad said:
Did you extract both archives to the same directory on your computer?
Click to expand...
Click to collapse
Yes, I extracted both the gtablet and the windows zip files.
KrazyOne7 said:
Yes, I extracted both the gtablet and the windows zip files.
Click to expand...
Click to collapse
Me too, and still getting the error "nvflash configuration file error: file not found Press enter to continue:"
Are they in the same directory. If they are not then nvflash can not find the files to flash. Both zips have to be unzipped in the same directory and the driver has to work. You must be able to see the tablet from the computer when you boot into apx mode. APX mode is power/vol- NOT power/vol+
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
dw21 said:
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
Click to expand...
Click to collapse
You need to follow the nvflash instructions on the developer page. Your partitions need to be fixed before gb roms will work
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
dw21 said:
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
Click to expand...
Click to collapse
Anytime you brick it, you can use nvFlash to un-brick it. Its just a matter of knowing what you are doing and reflashing it with the correct files. From what I have experienced, its pretty much impossible to brick these tablets once you have nvFlash setup. No matter how bad that situation is, I have always been able to recover using nvFlash(and I have been in very terrible situtations where I got a blank screen when i booted...turns out I was stuck in apx mode when i booted)
rbansal2 said:
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
Click to expand...
Click to collapse
Can you go into more details on these two steps? I know it's done with cwm but I want to make sure I do it exactly right.
worked for me
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
clayvikings said:
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
Click to expand...
Click to collapse
Awesome, that's great news! Welcome to the club!
rbansal2 said:
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
Click to expand...
Click to collapse
I did exactly this (minus step 1. as it was already a stock device) and I had exactly the same problem - gtab stuck at viewsonic splash screen. My unit was fresh outta the box and fully charged, and this was the firstht hing I tried to do with it. CWM installed without a hitch (yes, 0.8) and I repartitioned without fear (I had no data on it anyway). Did the wipes, mounted the tab and copied over the rom... all instructions I found on XDA for doing it. It still sticks at the splash screen.
So, to get a working tablet again, I used nvflash to go back to stock (though I have a superuser app now, which is odd for 'stock'), did the ota update to 3588, loaded Spark+ on it for a launcher and add the amazon marketplace app (looking for more free apps).
I still want to get VEGAn installed though, just wish I new why it was freezing up/not booting/not correctly installing or whatever the problem is.
If you have run nvflash you can now install Gingerbread roms as it fixed your partitioning. When you got stuck on the vs birds it meant your partitioning was wrong and you needed to nflash. If you did then your fine now.
The nvflash provided does not bring you to complete stock. If you want complete stock just flash the 3588 update.
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
dw21 said:
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
Click to expand...
Click to collapse
I've been watching the VEGAn-TAB logo flash and pulse at me for the past hour. Think I'm going to try to flash the ROM again...
EDIT:
Scratch that. restarted into cwm, cleared user data again, booted right into V. Going through setup screens now. Question though... If this was writtne for the G-Tab, then why does it still have the phone stuff in it?
was working but now it isn't?
++++i had to use nvflash for my gtab and it worked. I loaded vegan-tab 7.0 GE and it took "literally HOURS" to boot to the tablet setup page, after that it was working great until I rebooted it after 1 day of use and now i can't get past the "powered by g-tabdevs" boot page?????? any thoughts?++++
UPDATE: I repartitioned the sd card 2048/0 and that didn't work, then i cleared the dalvik (?) cache and the other cache and it booted up successfully (warning to newbs like me, this did clear all my data so back up everything)
SIDE NOTE: I love this website!!!
Two things I always do before I decide to try a new ROM, backup anything I don't want to lose, then go do a factory reset. When you install a new ROM, it doesn't automatically wipes all the partitions, especially the user data and settings. By leaving that there, you are allowing the ROM have access to that information which in turn, can cause problems because not every ROM setups the same. I have seen many people run into problems because they don't do a data wipe. If you do this, you will see a lot less problems in the future and if you do get a new install running but seeing FCs with a lot of apps, do a factory reset.
VEGAn-TAB GingerEdition STABLE RC1 Still In Boot Loop
Hi, I've tried doing as per what the instructions said about clearing the cashes and partition SD card sizing. I've load VEGAn-Tab 6 times already and everytime I still end up with a boot loop error. I just decided to use tntlite instead, but I really want to get this working. I noticed one thing as I was loading tntlite and the stock rom that when I go back to ClockworkMod v08 to mount “/system” and “/data”.
I see the following:
“unmount/system”
and,
“unmount/data”
which is right, but when after I load VEGAn-Tab
I see the following:
“mount/system”
and,
“unmount/data”
From what I've been reading this should not be the case. I'm not sure it this is related to my problem with the boot loop or not.
Please help!
Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.
Hi,
i just got my G tablet recently and I decided to install Clockworkmod and TNT Lite.I followed instructions to install Clockworkmod using the a USB cable and it worked perfectly.I installed v3.0.2.8.Then, I downloaded TNTLite and moved the update.zip file to the root.When I did that, the only option to put it on the root was to replace the update.zip file from Clockworkmod with the new file from TNTLite.I went ahead and installed TNTLite and installed pefectly.I booted the tablet but it got stucked on the splash page with the Viewsonic logo.I don`t know what I did next but now every time i boot it goes straight into Clockwordmod.I reboot and doesd the same thing.When the splash page appears, in the top left corner it says:booting recovery kernel image.
Can anyone help me?
There are a couple of issues here.
First of all you need to determine which bootloader your gtab is on. There is a sticky which will help you with the whole bootloader issue. You are likely on 1.1, which is incompatible with the version of clockwork you loaded. You need clockwork .08 for the 1.1 bootloader. v3.0.2.8 only works with the 1.2 boot loader.
TNT lite has been retired, and although it is a solid ROM, it isn't being actively developed. The active "version" of TNT lite is hosted on slatedroid and is called Mountain Laurel (almost certain of the name, but I could be mixing them up). Both of those are based on the 1.2 bootloader.
Also TNT lite and Roebeet's other mods are typically installed via standard recovery rather than clockwork mod. This is at Roebeet's recommendation, and should have less rick of brickage.
Goodintention's site http://viewsonic-gtablet-for-dummies.webs.com/ should get you up to speed.
Your best bet at the moment may be a full restore with nvflash, which you can read about on the site above. The site will also help clear up the 1.1 vs 1.2 issues.
Thank you very much for the post!
I will follow your instructions and I will post a message tonite with the results of my experiment
Wish me luck
Good luck. Be careful though, my instructions are only a quick guideline, be sure to stick to gtab for dummies site, or something like of these tutorials:
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=865245
I`ve got it back to stock!!! Thank you!!
Now, I have to install a ROM on it. I will post back the results!
Thank you again! Any tips on getting a ROM installed?
adirom28 said:
I`ve got it back to stock!!! Thank you!!
Now, I have to install a ROM on it. I will post back the results!
Thank you again! Any tips on getting a ROM installed?
Click to expand...
Click to collapse
You really need to go to my site gtab for dummies linked in my signature. There you will find step by step instructions on how to flash (install) a new rom. I hope you used the files provided on my site because the nvflash on my site came with cwm pre-installed. And on my site, you will also find a list of all available roms at this time. Just go there and see for yourself. Make sure you use the "start here" page.
If your on stock 3588 then this tutorial is a great reference guide:
http://forum.xda-developers.com/showthread.php?t=865245
As for installing a ROM it's pretty straightforward and it doesn't sound like you'll have much trouble. Vegan Froyo and Vegan Gingerbread are great solid roms. There's a lot to try out so have fun.
Thank you very much for your help! I will work on this tomorrow and post the results!
Really appreciate your help! Thanks!
adirom28 said:
Hi,
i just got my G tablet recently and I decided to install Clockworkmod and TNT Lite.I followed instructions to install Clockworkmod using the a USB cable and it worked perfectly.I installed v3.0.2.8.Then, I downloaded TNTLite and moved the update.zip file to the root.When I did that, the only option to put it on the root was to replace the update.zip file from Clockworkmod with the new file from TNTLite.I went ahead and installed TNTLite and installed pefectly.I booted the tablet but it got stucked on the splash page with the Viewsonic logo.I don`t know what I did next but now every time i boot it goes straight into Clockwordmod.I reboot and doesd the same thing.When the splash page appears, in the top left corner it says:booting recovery kernel image.
Can anyone help me?
Click to expand...
Click to collapse
Just to add my two cents - it looks like you are mixing up 1.1 / 1.2 dev branch items (luckily you didn't soft-brick!).
TNT Lite is a 1.1 ROM (no longer being developed), but my 3.0.2.8 rev5 cwm is for the 1.2 bootloader, so they aren't compatible. Perhaps you used another 3.0.2.8 that's not mine?
"Mountain Laurel", over in Slatedroid, is he successor to TNT Lite. It's based off stock 4349, and it's 1.2 dev branch based.
As for the cwm reboot issue, did you try and wipe data in the UI, with cwm installed? If so, the "cwm forever reboot" is known to happen. The "fix" is to get standard recovery installed so that way the data wipe completes.
roebeet said:
As for the cwm reboot issue, did you try and wipe data in the UI, with cwm installed? If so, the "cwm forever reboot" is known to happen. The "fix" is to get standard recovery installed so that way the data wipe completes.
Click to expand...
Click to collapse
I too am stuck in CWM. I was on the 1.2 ROM branch, and was using the CWM v3.0.2.8 (1.2 branch). How did you get out of CWM? I'm guessing you had to do a nvflash - I've done that before, but how do you get to the APX screen? (if that's what you did).
Roebeet also said "As for the cwm reboot issue, did you try and wipe data in the UI, with cwm installed? If so, the "cwm forever reboot" is known to happen. The "fix" is to get standard recovery installed so that way the data wipe completes."
1) yes I did a wipe data using CWM but not sure what Roebeet meant by "UI (user interface), with cwm installed" - I'm not sure how else I could do a CWM data wipe using the UI?
Edit: got it. In the UI, sometimes under Security, you can do a factory/data wipe from there.
2) The "fix" " is to get standard recovery installed - what is the "standard recovery"? and more importantly, how do I install it?
Edit: Is the standard recovery - going back to the gtab stock (depending on what branch you are on)?
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2