Hi everyone.
I've tried to read as much as I can here, but I haven't been able to make any solutions work.
I have the gtablet. It had the latest OTA update (Apr 15). I tried to install the clockwork mod.
When I first did the Volume+Power boot, it brought up the menu as expected.
I then tried to apply the update. It rebooted.
But since then, when I Volume+Power boot, it says the following:
"Recovery key detected"
"Booting Recovery Kernel Image"
BUT then it just sits there forever. I let it sit for over 30 minutes ... no change.
If I boot normal (just hit power) everything works fine as before. No data loss, etc.
But I wanted to get root access so I could use Titanium Backup (that's what started all this).
If anyone can give me some advice/help on this, I'd appreciate it very much.
Thanks in advance!
The standard ClockworkMod is not compatible with the latest update (1.2-4349). If you're familiar with nvflash you can probably pull the recovery image out of the 4349 update.zip and reflash it back onto your tablet. If you're not familiar with it then you'll need to start reading up on it...
http://forum.xda-developers.com/showthread.php?t=861950
K J Rad said:
The standard ClockworkMod is not compatible with the latest update (1.2-4349). If you're familiar with nvflash you can probably pull the recovery image out of the 4349 update.zip and reflash it back onto your tablet. If you're not familiar with it then you'll need to start reading up on it...
http://forum.xda-developers.com/showthread.php?t=861950
Click to expand...
Click to collapse
Thanks for your reply. I appreciate it.
What I don't understand is -- I've tried doing the "downgrading" and other approaches that use the "update.zip" and "command" files, but it's as if my gtablet doesn't read those now. Yet - as I said - if I boot normally it loads/runs everything fine.
Well, I guess I'll try the NVFlash. It's still a new tablet so even if everything gets wiped out, I haven't really lost much.
Thanks again for your reply.
barnell,
Your G-Tablet uses the "Recovery" function and software to load software, updates, etc.
When you tried to load CWM, it messed up the recovery software (or didn't re-load it, I
think) and so while the rest of your tablet works fine -- any call for recovery functions
go unanwered.
When you NVFlash as KJR said, it will restore the "Recovery" software along with the
rest.
Rev
butchconner said:
barnell,
Your G-Tablet uses the "Recovery" function and software to load software, updates, etc.
When you tried to load CWM, it messed up the recovery software (or didn't re-load it, I
think) and so while the rest of your tablet works fine -- any call for recovery functions
go unanwered.
When you NVFlash as KJR said, it will restore the "Recovery" software along with the
rest.
Rev
Click to expand...
Click to collapse
Rev,
Thanks very much for your reply.
I suspected it may be as you said, but being new to the gtablet and its architecture, I couldn't be sure.
I guess NVFlash is the way to go. I'll keep you all posted.
Thanks again.
barnell said:
Rev,
Thanks very much for your reply.
I suspected it may be as you said, but being new to the gtablet and its architecture, I couldn't be sure.
I guess NVFlash is the way to go. I'll keep you all posted.
Thanks again.
Click to expand...
Click to collapse
After totally trashing my g-tab yesterday with the new update and spending about 8 hours trying to get things back to where they were, I can say with all honesty.... NVFLASH IS YOUR FRIEND!!! Learn to use it.
Hi everyone, I'm new here, and I'm experiencing the same issue. The only difference is that I don't even see "Booting Recovery Kernel Image"
When I tried to use the nvflash method, my computer (Acer Aspire Revo) doesn't even detect my Gtab when I connect it to my tab. So, I'm at a loss, seeing as how both using an SD card and the nvflash method hasn't worked. Any help would be greatly appreciated, as I'm certain I may have completely bricked my device.
If you're using windows you'll need the appropriate driver for your tablet to be seen in APX mode. I don't use windows myself and the driver is version dependent so I can't really point you in the right direction on that without more information.
Actually, with a reboot of my coputer, it could detect my tab in APX mode, so I was able to run through nvflash. Phew, though now it can't load the update, so I'm stuck with the stock for now. Thanks for the reply!
IndyLateNite said:
After totally trashing my g-tab yesterday with the new update and spending about 8 hours trying to get things back to where they were, I can say with all honesty.... NVFLASH IS YOUR FRIEND!!! Learn to use it.
Click to expand...
Click to collapse
Indy (or anyone who cares to respond),
I wonder what you think of this ...
If I do nothing (ie, I don't nvflash back) and wait for another gtablet update, maybe the next update will 'fix' the problem of not working with the CWM?
I have no real pressing need to change anything at the moment - though I would like to get rooted (so I could use Titanium Backup) -- but I'm not keeping anything that critical on the tablet (yet). So I'm just thinking I might wait it out and see what the next update does (assuming there'll be one).
I'd appreciate your thoughts, as you seem pretty knowledgeable about all this.\
And, again, I appreciate your responses, so thanks in advance.
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.
My wife installed the update on her stock g-Tablet while it was still available OTA. I tried installing roebeet's Gapps without success, so used Z4root to root her tablet and tried again. Now I can't get into recovery at all! The tablet detects the recovery keypress, but no matter how long I wait, nothing ever happens. I've tried re-installing the update from the downloaded file - no dice, since it never gets beyond notifying me that it detected the keypress. The tablet will boot and things seem to run properly. I've tried un-rooting using Z4root, but this seems to make no difference.
Any ideas what to try before I resort to nvflash?
mstevens,
This is only my philosophy, so you don't have to do it -- can make your own choice.
When I don't know what's going on with my machines, I always go with a fix that will
get me back somewhere where I know what's going on and I know the machine is
working right.
If my tablet were doing what yours is doing, I wouldn't mess with anything else --
I just take about five minutes to NVFlash back to bekit 1105/Version 2638. Then
another 10 minutes to OTA up to 3588. The set things up enough to check and
make sure it's solid and working right.
Then I'm ready to head out where I want to go.
How many times have you read in these posts where someone has a problem and
then tries to flash two or three more roms on top of a questionable situation?
To me having a "known good" is critical for moving on -- and if I don't I don't.
I apologize for the rant. You are handling the situation well so far. NVFlash if
you want to, but make sure it's working right whatever you do so you can
have some fun!!!!
Rev
You could just try to nvflash part9 with the img file from the 1.2 cwr zip file. That would give you a recovery without having to start all over. Especially since the updater isn't allowing you to upgrade past 3588 anymore.
butchconner said:
To me having a "known good" is critical for moving on
Click to expand...
Click to collapse
Agreed. In this case, my wife had already applied the OTA update. Once that had been done, I couldn't see a way to back-up her setup. When she wanted me to try to install the Market, I did that knowing I might have to nvflash.
jasco13 said:
You could just try to nvflash part9 with the img file from the 1.2 cwr zip file. That would give you a recovery without having to start all over. Especially since the updater isn't allowing you to upgrade past 3588 anymore.
Click to expand...
Click to collapse
I'll certainly try that - it makes sense before doing a full nvflash and re-build. My concern is that the problem is with the kernel since I think Z4root caused the problem, so re-flashing just the recovery may not work. I'll give it a try and report back.
jasco13 said:
You could just try to nvflash part9 with the img file from the 1.2 cwr zip file.
Click to expand...
Click to collapse
Is it boot.img or bootloader.bin that gets renamed to part9.img?
If your gonna nvflash part you may as well nvflash all and reset
thebadfrog said:
If your gonna nvflash part you may as well nvflash all and reset
Click to expand...
Click to collapse
Except that I haven't found a way to do backup and restore on 1.2 yet, so she'll lose all of her settings and data.
I may wait until there's an actual problem before doing anything further.
mstevens said:
Is it boot.img or bootloader.bin that gets renamed to part9.img?
Click to expand...
Click to collapse
Neither, it's recovery.img
It shouldn't hurt to nvflash just the recovery partition. You probably won't be any worse off than you are now and you'll still have the option of a total nvflash anyway.
mstevens said:
Is it boot.img or bootloader.bin that gets renamed to part9.img?
Click to expand...
Click to collapse
FYI
http://forum.xda-developers.com/showthread.php?t=1030042&highlight=Nvflash+recovery
Make sure you use the 1.2 version of cwr. I think roebeet posted it.
jasco13,
The NVFLash CWM was my thread and at the time I wrote it there were only 1.1 version
ROMs/upgrades.
I started to put notes in it and update it to say use Roebeets CWM for 1.2
if it still is available anywhere.
BUT -- if you are so borked up you need to get back to stock, I'm not sure
it matters.
I did the CWM via NVFlash with the intention that someone would flash it and
use it to re-partition, etc. Then they would NVFlash the stock bekit 1105 (Version
2638) per the NVFlash Procedure. And then they would OTA to 3588 (which
will overwrite the CWM) and then on to 1.2.4349.
What do you think? Should I leave it alone on that premise?
Maybe I ought to wait a day or two. I read roebeet is working on and nvflash
version of 3588 to go back to as a baseline.
Rev
butchconner said:
jasco13,
The NVFLash CWM was my thread and at the time I wrote it there were only 1.1 version
ROMs/upgrades.
I started to put notes in it and update it to say use Roebeets CWM for 1.2
if it still is available anywhere.
BUT -- if you are so borked up you need to get back to stock, I'm not sure
it matters.
I did the CWM via NVFlash with the intention that someone would flash it and
use it to re-partition, etc. Then they would NVFlash the stock bekit 1105 (Version
2638) per the NVFlash Procedure. And then they would OTA to 3588 (which
will overwrite the CWM) and then on to 1.2.4349.
What do you think? Should I leave it alone on that premise?
Maybe I ought to wait a day or two. I read roebeet is working on and nvflash
version of 3588 to go back to as a baseline.
Rev
Click to expand...
Click to collapse
i haved used it only to flash cwr to do a partition and then fresh nvflash. That being said I think it is a usefull tool to have instructions to flash any form of recovery you want. I accidentally flashed 1.1 cwr over 4349 and had to do a full nvflash when all i really wanted was the stock recovery back. This process borked my touch screen which was a bit of an ordeal to recover from. The calibration in the 1.2 recovery would have fixed it. Being that 4349 seems to be missing from the updater now I'm not sure what the best answer is. Either way the instructions would need to be uber clear because of the dangers.
Matt
edit... maybe having downloadable nvflash packets for "approved/recommended" applications instead of advising people to edit the standard nvflash which could lead to more problems.
Most (if not all) of the factory updates have a recovery image included in the zip. Those can be nvflashed individually back into an otherwise working tablet to recover from this sort of thing. I've got linux versions of the commands I use on my laptop. I'll try to put a little something together tomorrow on it and put it up for perusal.
Hey, fellas. As you may or may not be aware, I am in dire straits. Recently I had been browsing the XDA forums for the first time in a long time, and lo and behold there was a magnificence I had thought to never see in our own development forum... a Honeycomb alpha! In my haste I tried to follow every instruction to the tee and discovered that I need the stock bootloader/ROM to do this.
Well, coming from cyanogenmod7 and a first time nvFlasher, I followed the instructions from one thread to flash back to stock 3588(I think it was)? So after fiddling with the drivers for about 5-10 minutes, I start flashing and everything is going great, no errors whatsoever. Then the tablet starts to boot up and what happens? A bootloop at the TapNTap screen. So, I tried to boot into recovery thinking it might be fixable with a factory/data reset...and recovery no longer works, it just reboots back int pthe TnT bootloop. And then I came to the this forum, particularly the Q&A, to ask one question...
Is my G-Tablet well and truly forked?
Sincerely, this guy.
[edit]P.S I am also currently trying a bunch of stuff atm to see if I can fix it myself, but just reply if anything I do is futile and I should consider recycling my new hunk of silicone and plastic.
Load cwm .8 via update.zip and repartition your tab. Then try nvflash again.
"Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared. "
Or try loading it by nvflash with instructions from this thread
http://forum.xda-developers.com/showthread.php?t=1058649
Here is a thread on how to easily flash to the 1.2 bootloader.
http://forum.xda-developers.com/showthread.php?t=1039000&highlight=guide
Holy heck, thanks man. Do you have a paypal or something so I can send you like 5 dollars?
Nope, just mash the thanks button ;-)
Good luck!
No offense to the OP, but from my observations it seems that NVFlash is more of a breaker than anything. Everybody says to know NVFlash in case you end up with problems...that's fine, people can apparantley use ot to help fix errors that may have happened...
The fact is, most of the "I've bricked my G-Tablet" posts usually contain the line "So I NVflashed..."
I know that the developers use NVFlash for it's ease of use to go between roms, and see what it is that they need to see (I've never used it, so I don't know)
The fact is, the instructions that Mantara posted do not require NVFlash at all. In fact, after flashing 3588, they don't even require CWM.
If I ever softbrick, THEN I'll mess with NVFlash...but until then, it seems that NVFlash might actually cause me to have my first softbrick.
Nvflash is a handy tool to have and yes it can cause errors. Most of the time those errors occur because the partition table on the tablet don't match the partition table for the Rom being flashed. About half the gtabs have different partition tables from what is considered standard. That's why I have been pressing the issue of repartitioning when you first get your gtab and also when you move from 1.1 to 1.2. It helps make sure your tab and the software are on the same page.
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.
Hello everyone,
i just recently purchased a gtab and tried to install clockwork recovery on it. that didnt seem to work so i tried to do a factory reset. my guess is it tried to boot to CWM but the files were messed so now its stuck at "booting recovery kernel image". can someone assist me? my plan was to put cwm on it, and then put Vegan on it, but that foiled.
Thanks!
Hubblemuffin said:
Hello everyone,
i just recently purchased a gtab and tried to install clockwork recovery on it. that didnt seem to work so i tried to do a factory reset. my guess is it tried to boot to CWM but the files were messed so now its stuck at "booting recovery kernel image". can someone assist me? my plan was to put cwm on it, and then put Vegan on it, but that foiled.
Thanks!
Click to expand...
Click to collapse
What version of CWM did you try to install? Do you know what bootloader you're on? I'd imagine that you tried flashing the 1.1 BL CWM and ended up in a softbrick because you have a 1.2 BL G-Tablet...
G-Tablet for Dummies is your friend...google it, read every page, then decide what you want to do. At the start here page, you're on a code red, I believe.
If you happened to install a wrong CWM bootloader version, you are in BIG trouble. The "stuck bird sign" is not a good sign
Last time it happened, I used code DETOX to set it straight in viewsonic gtablet for dummies.
THis thing is unbrickable (virtually unbrickable), so no worries~
I have to agree. I got my gtablet about a month ago. Nothing I did seemed to work, until I found the gtablet for dummies site. Within about two hours, I was up and running with a real android operating system with full market.
That site ROCKS!
Thank you all so much for the reply. I just got it today and knew I didnt want TnT but i guess i rushed with the process and did the wrong bootloader. Im gonna look in to that when i get home to my own PC and see what happens. Thank you!
ok. i read over the Gtablet for dummies website, and that reminded me that there must be something wrong with the install of CWM. all it does is say ANDROID in orange on the left of the screen and then a grey triangle shows up. im going to attempt to be the Triple Code Red tonight and hope that works.
Humblemuffin,
Don't give up! I totally messed up the g tablet shortly after taking it out of the box. After much research and trying various steps/techniques, I eventually was able to bring it back.
I posted the exact steps I used here on xda and on slatedroid.
They can also be found on the Viewsonic Gtablet For Dummies site under "How-To". Follow the steps exactly and I am confident you will get your g tab restored.
http://viewsonic-gtablet-for-dummies.webs.com/
Same steps, but recently added some content about APX and NVFLASH
http://forum.xda-developers.com/showthread.php?t=1167944
djab67
Sent from my ADR6400L using XDA Premium App
thaks for the advice. im quite grateful that theres people able to help me here. ive been reading gtablet for dummies, but i seem to be at even more of a standstill. i think my CWM is corrupt or something. after it says "Recovery Key Press Detected", it shows ANDROID in yellow/orange letters on the left of the screen for about a second, then a grey triangle with an exclamation mark pops up. i think using the wrong bootloader kind of screwd me over. i always try and rush with my technology like this. thank you!
Here is another potential solution for you to consider. It does not require the use of ADB which makes it a little easier than my steps. If it you think this one will work for you, then I would recommend doing it before mine.
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Thanks for the reccomendation! I sent you a message about it and maybe we could get it up and running. My main concern now is that my CWM still doesn't work. That's kind of worrysome to me because all the potential fixes I see envolve using it at one point or another.
Blank Screen, background light
I went to GTablet for Dummies as well, to install CWM and then a new OS. Unfortunately, my GTab would not accept the installation of CWM. I have a 1.1, and tried installing the version 1.1....following the directions exactly They then suggested I install nvflash, which I tried with no success. Now, my GTab just shut down...blank screen with background light. Prior to the shut down, it had over 40% battery life left. Any help would be greatly appreciated.
Well, when I first got a gtab, i messed up the bootloader (installing the wrong version of bootloader), CWM doesn't work. Etc...etc...luckily apx mode still work. This is what I do. I think it is sorta the ultimate wipe.
Edit: I wasn't allowed to put link outside since I was a new user. But you can just go to viewsonic gtablet for dummies website
USE THE CODE DETOX. The code detox invovles you nvflashing your rom with this format.zip file. It might look similar to other nvflash at first glance except when you use the format zip nvflash, you will see "magic-value -mismatch" in red color.
After you nvflashed your tab with format.zip. Do another Nvflash, but this time, Nvflash your tab with "NVFlash to Stock with CWM pre-installed" . Get the right bootloader, and follow the steps described later in viewsonic gtab for dummies, and you have a smoking gtab soon enough
Um... guys, just download my nvflash with cwm pre-installed and use that. No need to put cwm on separately.
To goodintentions, TJEvans, fury7, tidbit, djab76, SM Daly, ahandlen003, and goodintentions again.
Thank you so much. i know the task is yet to be complete, but i finally was able to get past the bootloop and in to TnT to do the OTA update. im going to be much more careful with any more modding. for the record, the NVflash with CWM pre installed for BL 1.2 was the ticket. CWM looks so beautiful after being in the pits for a few days.
if all goes to hell again, ill let you all know.
Thanks again!
Hubblemuffin.
Hubblemuffin said:
To goodintentions, TJEvans, fury7, tidbit, djab76, SM Daly, ahandlen003, and goodintentions again.
Thank you so much. i know the task is yet to be complete, but i finally was able to get past the bootloop and in to TnT to do the OTA update. im going to be much more careful with any more modding. for the record, the NVflash with CWM pre installed for BL 1.2 was the ticket. CWM looks so beautiful after being in the pits for a few days.
if all goes to hell again, ill let you all know.
Thanks again!
Hubblemuffin.
Click to expand...
Click to collapse
Before I bought my gtab, i spents hours reading up on roebeets and others @ xda, blogspot and slate. took tons of notes. had everything laid out step by step. even had nvflash files set up. Had minimal prblems.
In the last month or two, found out about goodintentions website. he pretty much compiled everything you would need to know.
spend some time there reading up and you'll be on your way.
Probably should send him a donation also...he deserve it
I have a question I think I jump the gun on this one. I tried to install ClockWorkMod for my G tab 1.2 I got the file from GTablet for dummies but everytime I tried to install it it will just sit on the "Recovery key detected" and then it says "Booting recovery kernel image" and with the 3 birds and it just sits there! I can't get into recovery mod. either but I can turn it off and it boots fine to the homepage. What can i do? The person I bought it from had it rooted but he said he returned it back to stock rom. Thanks for the help.
Can someone help me, please.
Big Thumbs Up to Goodintentions...
qkster said:
Before I bought my gtab, i spents hours reading up on roebeets and others @ xda, blogspot and slate. took tons of notes. had everything laid out step by step. even had nvflash files set up. Had minimal prblems.
In the last month or two, found out about goodintentions website. he pretty much compiled everything you would need to know.
spend some time there reading up and you'll be on your way.
Probably should send him a donation also...he deserve it
Click to expand...
Click to collapse
I donated to goodintentions...
you should too.
jjq13 said:
I have a question I think I jump the gun on this one. I tried to install ClockWorkMod for my G tab 1.2 I got the file from GTablet for dummies but everytime I tried to install it it will just sit on the "Recovery key detected" and then it says "Booting recovery kernel image" and with the 3 birds and it just sits there! I can't get into recovery mod. either but I can turn it off and it boots fine to the homepage. What can i do? The person I bought it from had it rooted but he said he returned it back to stock rom. Thanks for the help.
Click to expand...
Click to collapse
If it were my Gtab, I would nvflash it back to stock myself just in case. Just pay attention to the requirements of the custom ROM you want to flash: some are for 1.1 and some for 1.2 -- nvflash accordingly. Anyway, learning and setting up nvflash is a good thing if you plan to flash custom ROMS with any regularity.
Brian