Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
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+
Can one of the wooters upload the nvflash backup that they created. I noticed mine wont boot up with the backup provided http://db.tt/Wm25t7U.
rbansal2,
I'm not a wooter but I do know a few things about the nvflash procedure.
http://forum.xda-developers.com/showthread.php?t=861950
The two files called for in the NVFlash Procedure from the Developers Forum are
correct. The file with "windows" in the middle provides the nvflash.exe and related
files. The file with "gtablet" and 1105 in it is commonly called "bekit 1105" and has
been around as a stock fall back since at least last November. Using other file
combinations often causes problems for your tablet.
If you do a successful flash, it should show the whole process on your screen and you
will have to press a button to continue once. When you do it will boot all the way
through to the main screen of bekit 1105 -- AKA stock version 2638. If that version
runs, when you install wifi internet it very soon offers you OTA (over the air) Update 3588.
With stock 3588 running well you can go where you want to from there.
Second, if you don't get a successful install, the next step usually recommended is
to flash CWM on to your tablet either using a microSD card and the external slot.
http://forum.xda-developers.com/showthread.php?t=865245
http://forum.xda-developers.com/showthread.php?t=1020747
The above threads give info on installing CWM. And there are others.
If you successfully install CWM and can boot recovery (power/volume+)
to it, you need to go in to the Advanced Menu and run Partition (2048/0),
Fix Permissions and Wipe Dalvick Cache. Then go back to the Main menu
and run Wipe Cache and Wipe/Reset Factory Data. Then shut down.
When you re-boot, hopefully you'll be up with bekit 1105 and can wifi and
update as above.
I can't say iron clad this works "all" the time, but it has been more than
successful for a lot of folks.
Try it again if you like and let us know if you make progress.
Good Luck,
Rev
my problem is that I dont see anything when i boot up. My g tab is stuck in apx mode and I cant seem to get out of it, therefore i cant flash cwm :/
What my long thread was saying is I think you should go through the nvflash process
again, double checking everything along the way.
If that doesn't give you a working tab, then you can put CWM on a microSD and boot
recovery to /SDCARD2 and see if you can install CWM that way.
If neither of those work you are no worse off than you are now -- and if one of them works we have a chance.
Rev
did that..used the nvflash_gtablet_46_2010112600.zip file to recover it this time and it worked...thnx for your help...really appreciate it
rbansal2,
You are fortunate. When I said double-check things, I meant to do it
per the procedure. If you read these forums, you will see that the
"46" file is not recommended for a reason -- it frequently causes boot
loops. (Besides, it is a linux file for use with Linux though it is named
like a Windows file. I don't know why -- we're borrowing someone's
library to get the four correct files.
I say this not to diminish your joy, but to say watch for problems and
be careful.
Good luck,
Rev
So I am just about at my wits end. I am fairly computer literate but an absolute noob when it comes to my gtab and flashing it.
I’ll try and give a step by step.
1. Got my Gtab today. I was sooooo excited!
2. Installed CWM and the latest TNT lite ROM.
3. All is well everything worked great.
4. Started up Android market…all hell starts breaking loose with “forced closes”.
5. Ok…so I shut down and restart
6. It starts what I have learned is called a “boot loop” going from the birds to the “G Tablet” screen to black to the birds…
7. I try to reflash TNT…nothin’.
8. I try NVflash, it *says* it completed successfully, but stays in the boot loop.
9. I’ve tried copying the CWM onto the microsd card (yes, command is pointing to the micro card). I then go through the Hold down the plus and start.
10. CWM *seems* to install, then HEY…right back into the boot loop.
11. I try something else and get (in little red text in the top left corner of the screen) something about “Magic” something missing.
Does anybody have any suggestions? I am a smart guy…I can read. The thing is, is that it seems like the mods and the CWM’s are completing successfully, but then I am right back in the flippin’ boot loop. I am afraid I’ve just wasted $300.
Sorry to be the dumb noob.
Pat
Did you change the partition when you installed the new rom? That was what fixed mine.
No...none of the instructions I saw mentioned that. Now I am seeing using CWM to do it but the problem is I can't get CWM to load!
if CWM is installed, you just need to hold V+ and power button when restarting. if not (and this happened to me) you should follow the instructions that were given to me by regalpimpin on this thread http://forum.xda-developers.com/showthread.php?t=1025128 to install CWM, and re partition (you will loose all the data on your internal SD card so be sure to back up) but repartition at 2048 and 0 unless the ROM specifically asks for a different partition.
You need to nvflash if you are getting the magic value mismatch. You could have gotten out of the boot loop originally by repartitioning. Only use bekit 0.8 recovery as any others will bork your tab. Dont use rom manager either.
mocheesehead,
First don't panic. We can fix this. It's REALLY hard to brick
a G-Tablet!
You have done all the right things from what you have written.
As Lisa said the one thing you haven't done is re-partition and
it seems that re-partitioning fixes boot loops most of the time.
Double check. Use your microSD with the CWM update.zip on it.
Since the command file is erased when you use it, you will need
to copy a new copy of the command file edited for /SDCARD2 back
into the recovery folder. Boot into recovery with power/volume +.
When all is finished shut down properly. The reboot as above and
see if you get CWM.
If you don't, you will have to try to load CWM by nvflash. If you
will try the above again, I will see if I can find directions for CWM
by nvflash. I know the process but will have to find the correct
command line.
*************
Just in case CWM loads: I will go ahead put the fix process here:
1. When CWM starts, go to the Advanced Menu and run the
Partition SDCARD, Fix Permissions, and Wipe Dalvik Cache options.
The re-partition takes a few minutes so
don't panic! Then go back to the Main Menu and Wipe Cache
and Wipe/Reset Factory Settings.
2. Once that is done, reboot and hopefully you will be fixed.
3. If not fixed, nvflash back to stock as per the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Makes everything -- especially the files to load -- is correct.
Keep us posted on how you do. Meanwhile I will look for the
other procedure and post it.
Rev
Hi Lisa! Yes! That sounds like my problem. I'll give it a go.
Quick question...is there a preferred format (ie, FAT32, etc) for the micro SD card?
I'll let you know how it turns out!
Thanks...Pat
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
butchconner said:
Pat,
Read this thread. This person had about the same kind of situation
you do and had to nvflash to load CWM.
http://forum.xda-developers.com/showthread.php?t=1026757
Rev
Click to expand...
Click to collapse
Hey cheesehead! Absolutely follow Rev's advise! I was the Guy in the thread he references above. The fix worked like a champ.
You will get it fixed, just as I did. Same issue.
Mark
Thanks to everyone for the kind and informative responses. I probably won't get to a fix til Monday morning I as I have a soccer tourney (kids) all weekend, but I'll report back when I know something!
Thanks again,
Pat
As everybody said, it is almost brick proof, as long as you follow the correct procedures. Some people don't seem to understand missing one step can make things worse. Most of these post give you step by step instructions and by finding the right one to read you can't go wrong. I'm sure you will eventually have it worked out, learning what does what and why you did that will be a big help in the long run.
Ok! So I think I am breathing again! I partitioned the card and got back to the stock UI...man...it does really blow! So, a couple of questions...
1. I flashed TNT lite, and had force close issues. Would you recommend Vegan?
2. Now that I partitioned the card 2048 and 0 like everyone said, do I need to do this again before or after I flash a new rom?
Again, thanks for everyone's kind responses!
Pat
Glad to hear you made back to stock. Here in a bit I will write a step by step how to upgrade to TNTL 4.40 for you if some one doesn't beat me to it.
Thanks JH! I look forward to giving it another go! I appreciate your help!
Pat
Pat,
Remember that the bekit 1105 is about the oldest stock UI that exists!!! Most of us
started with 2967 on our first G-Tablets.
It WAS bad and there was no Flash and no replacement kernal and TnT was at about 2.x and VEGAn was at about .beta 3.
On the other hand, we didn't miss a lot of it because we were trying to keep them
running and find out what they would do and find apps we liked!!!
When I run the latest software I just can't believe how lucky we are.....IMHO.
Rev
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.