Hello everyone,
I gave it a try to flash to HC Alpha3, so I nvflashed to 3588 and up to HC Alpha3, it seemed to be loading the Bottle of Smoke/HC screen and went dark...I decided to go back to 3588 and up to 4349 because of 1.2 based ROM, so I formatted Gtablet by using the Format.zip...but now my Gtablet (no matter what I do) just goes to TapNTap infinite loop screen..
Anyone experienced this issue? and how to fix it? Otherwise, I just need to "accidentally" damage my Gtablet and get a new one (too smart to be...I purchased $100 for Accidental Damage so ...)
Thanks guys!
rcjpth
rcjpth said:
Hello everyone,
I gave it a try to flash to HC Alpha3, so I nvflashed to 3588 and up to HC Alpha3, it seemed to be loading the Bottle of Smoke/HC screen and went dark...I decided to go back to 3588 and up to 4349 because of 1.2 based ROM, so I formatted Gtablet by using the Format.zip...but now my Gtablet (no matter what I do) just goes to TapNTap infinite loop screen..
Anyone experienced this issue? and how to fix it? Otherwise, I just need to "accidentally" damage my Gtablet and get a new one (too smart to be...I purchased $100 for Accidental Damage so ...)
Thanks guys!
rcjpth
Click to expand...
Click to collapse
This is what NVFlash exists for. It's damn near impossible to totally brick your device, just try reflashing to 4349 (or anything) through NVFlash, and if you want to flash HC alpha 3, do so AFTER you're on 4349 as a base.
TL,DR - your best way out of this is through more NVFlashing, which you can still get into regardless of your bootloop, so do that, this doesnt even deserve a thread in this section.
rcjpth said:
Hello everyone,
I gave it a try to flash to HC Alpha3, so I nvflashed to 3588 and up to HC Alpha3, it seemed to be loading the Bottle of Smoke/HC screen and went dark...I decided to go back to 3588 and up to 4349 because of 1.2 based ROM, so I formatted Gtablet by using the Format.zip...but now my Gtablet (no matter what I do) just goes to TapNTap infinite loop screen..
Anyone experienced this issue? and how to fix it? Otherwise, I just need to "accidentally" damage my Gtablet and get a new one (too smart to be...I purchased $100 for Accidental Damage so ...)
Thanks guys!
rcjpth
Click to expand...
Click to collapse
I met the same issue. What I did to solve it is:
1. install CWM via nvflash
2. format the internal sd to 2048/0 (different from previous setting)
3. nvflash 3588
4. boot to 3588 to make sure everything works
5. nvflash 4349, everything works
6. nvflash alpha 2.4, everything works
7, after alpha 3 came yesterday, I updated, works
I am not sure the exact reason of infinite loop, might be the partition config.
Let's know your progress
Yes I tried everything LOL - I think it's totally bricked! I tried to nvflash to 1.0.0, 1.1.3588 & 1.2.4349 - all go to loop tapntap screen...it's very limited now what it can be done except nvflash. And nvflash doesn't recover in this case - and again I think my gtab is just unrecoverable even with Nvflash now
any other method?
how to install CWM from the nvflash?
1) setup NVflash and recovery per Roebeet's instructions (link below)
2) download the CWM zip file
3) unzip CWM update.zip file and extract the "recovery.img" file
4) move the "recovery.img" file to the "NVFlash" directory Roebeet talks about in his instruction
5) make a new "nvflash_CWM_only_Install.bat" file with the following text in it in the "NVFlash" directory
"nvflash.exe" --bl bootloader.bin --download 9 recovery.img
you will need the entire text above including the quotation marks for nvflash.exe
6) once the ".bat" file is done, execute it with the gTablet plugged into to PC as an APX device (power plus "vol -")
7) after flashing is finished, restart gTablet with power plus "vol +" and you will have CWM back so you can ungoober what Rom Manager messed up
rcjpth said:
how to install CWM from the nvflash?
1) setup NVflash and recovery per Roebeet's instructions (link below)
2) download the CWM zip file
3) unzip CWM update.zip file and extract the "recovery.img" file
4) move the "recovery.img" file to the "NVFlash" directory Roebeet talks about in his instruction
5) make a new "nvflash_CWM_only_Install.bat" file with the following text in it in the "NVFlash" directory
"nvflash.exe" --bl bootloader.bin --download 9 recovery.img
you will need the entire text above including the quotation marks for nvflash.exe
6) once the ".bat" file is done, execute it with the gTablet plugged into to PC as an APX device (power plus "vol -")
7) after flashing is finished, restart gTablet with power plus "vol +" and you will have CWM back so you can ungoober what Rom Manager messed up
Click to expand...
Click to collapse
Bless you. I ran into precisely the same issues as the OP. Am now formatting. Hopefully this will get me back up and running. It's been an ugly ugly evening! (thankfully I've been a reader of these forums long enough to have seen other people be brought back from the brink, so I never panicked tonight!)
Thank You!! This method works perfectly!!
haymant said:
I met the same issue. What I did to solve it is:
1. install CWM via nvflash
2. format the internal sd to 2048/0 (different from previous setting)
3. nvflash 3588
4. boot to 3588 to make sure everything works
5. nvflash 4349, everything works
6. nvflash alpha 2.4, everything works
7, after alpha 3 came yesterday, I updated, works
I am not sure the exact reason of infinite loop, might be the partition config.
Let's know your progress
Click to expand...
Click to collapse
Thank You!! This method works perfectly!!
I am newby , how do I make the .bat file?
rgaspa said:
I am newby , how do I make the .bat file?
Click to expand...
Click to collapse
On your computer you open Notepad (not Word, not Wordpad). This program is found in the Accessories folder in Windows.
You paste the sentence rcjpth mentioned:
"nvflash.exe" --bl bootloader.bin --download 9 recovery.img
Go to File, Save file as
On the pulldown, change it from TEXT DOCUMENTS (*.TXT) to ALL FILES (*)
Type in the name: nvflash_CWM_only_Install.bat
Click save.
The file should appear on your desktop (or wherever you chose to save it) as a file with 2 gears on it.
Related
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
EDIT: Thank this guy rcgabriel
rcgabriel said:
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
Gajun said:
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
Click to expand...
Click to collapse
it's not broken - just flash the latest firmware
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
g1no23 said:
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
Click to expand...
Click to collapse
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Gajun said:
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Click to expand...
Click to collapse
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Dude! You are the best!!! You are a life saver!! It worked! I got into cwm! Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
EDIT: Just after few minutes of finally getting into CWM, I was able to install VEGAN on it easily. Seriously, I don't know how to thank you enough!
gtab won't boot on its own
ok so i followed the instructions and it worked i was able to boot into the tablet but when i reboot it won't do it i have to use nvflash again to get it to it and once i do and the tablet goes to sleep it wont come back up and once again i have to use nvflash. please help!!
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
I'm stuck in bootloop and I tried you solution and being I'm a noob at this I dont know how to rename the dile under partition 9. I just simply rename the file to recovery.img and i get an error when running the nvflash when it gets to partition 9. Can you please help me .... All help is appreciated.
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Thanks! And a potential pitfall:
Thanks! I was having the same problem all night last night, and repartitioning fixed it.
I'd like to highlight something I had a problem with: I wasted a couple of hours with the WRONG clockworkmod recovery image. I found a similar response from another user who didn't include a link, and I found the clockwork image for g-tablet pointed to by someone else. If you're still having boot loop problems, use the clockworkmod linked to from this thread (v2.5.1.1-bekit-0.8).
Thanks everyone!
Is there a way that a mod can make a Sticky of the "Bricked Solution" fix.
There is no such thing as a bricked Gtablet that I've ever seen. Ive messed mine up a few times now and still works fine no matter how bad it gets.
Same for me, this fixed worked. I was not able to mount /data prior to repartitioning, was able to after. Thus the GTab was able to boot again, I now have a stock GTab, formatted clean, running 3588. Always nice to have a path forward.
emanzi said:
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Click to expand...
Click to collapse
Use Notepad
Hey i've done as you suggested however I'm stuck at the entering nvflash recovery node / nv3p server print out on my viewsonic gtab.... I still have the device plugged into my computer and it is registered with the usb bus but it won't reboot into the recovery img. I tried to power it down and reboot with "power and volume up" but I get no response. Any suggestions?
One thing I noticed, when people say they try to use nvflash they are using volume +, that is incorrect. You have to do "volume - (the minus sign) with the power button at the same to get the point to be able to use nvflash. See this a lot places in the forums, no wonder there is problems with people trying to use nvflash.
Thank you so much for this. I started getting an error when trying to mount /data so I did an nvflash without reading into it...turned out to be a huge mistake because that caused bootloops and left me without CWM. Turns out I should have just repartitioned but I couldn't get CWM to install from an SD card even though I knew I need to get it back on. Tried dozens of other things - including the full format with no luck but this finally got me into CWM so I could repartition.
Thanks again.
may as well be a brick - in my gut...
Every attempt at customization seems to be a step backwards.
Late nights have been spent over the last week trying to get things back to "normal" and I've had little success. Actually, make that "no success"...
At current, I've been looking ALL DAY (at work) and the last 4 hours at the NVFlash process.
I've got:
USB drivers installed for Windows
Bekit's 1105 files in place (gtablet + windows files)
I can boot to apx with volume.minus and power
PC sees tablet
I can run NVFlash w/o issue
gtablet boots immediately to stock ROM
I power off the gtablet and all I get is APX MODE again.
And again.
I have tried re-running NVFLASH with Roebeet's updated (4/17) files - same thing
I have tried renaming recovery.img from clockwork as "part9.img" and re-running, no success.
I have tweaked the gtablet.cfg and actually adjusted the SIZE for partition 9 to match the clockwork version of what I've named "part9.img" and no luck.
I ran the Format.zip version of nvflash, then ran regular nvflash, no luck.
Every time I run bekit's NVFlash, it loads stock ROM a-ok. Power cycle brings APX mode... I can't get Clockwork to install via the "nvflash switcheroo" nor by dropping "update.zip" and the recovery folder + command file in the root directory.
I feel foolish for spending about $300 on a device like this, and I feel foolish for spending SO MANY LATE NIGHT HOURS trying to fix it, and now I'm essentially going to only be able to use it unless - unless! - someone can come up with something else for me to try.... or if I "boot with NVFlash and hope it doesn't fall asleep on me..."
Any ideas?
Trust me, I've read every thread, seen the same "oh this worked...!" over and over on steps I've tried 3x or more. I think I'm depressed as this is ALL I DID TODAY - research on how to fix my gadget. sigh.
EDIT:
Just thinking here... (scary!) Has anyone ever sideloaded ROM Manager into the stock 3588 ROM? What I'm thinking is that if I can get ROM Manager to install, it loads CWM simultaneously, correct? And from ROM Manager I can reboot into recovery, yes? I would have tried this last night but I didn't come up w/ the idea until past 1:30am.
Also, let me take a step back and explain how I got here:
Installed Cyanogen 7 stable
installed a different keyboard
next day I got keyboard force-closes incessantly
tried to reflash CM7 - boot looped.
I could flash to the stock 3588 ROM w/o issues, and could use Clockwork w/o issues
tried to flash CM7 again, no dice
I suppose what i should have done at this point is re-partition and THEN try to reinstall CM7 - but I was having an issue w/ clockwork not completing the Factory Wipe / Reset - it would get stuck...
so I decided to bring the hammer w/ NVFlash - and I've certainly accomplished that
I can't get clockwork to install despite all I've tried:
paste recovery.img into my NVFLASH folder
change part9.img to recovery.img in the gtablet.cfg file
put clockwork's update.zip in the root folder
put clockwork's update.zip (and change "command" file to SDCARD2
I guess - how do I know if I'm still rooted? When I (nvflash and boot into) the stock ROM, I can connect via usb and navigate the folder structure. I see .android-secure and "data" and other typical folders that I've seen for weeks now...
so tired...
What happens if you do a factory reset immediately after it boots?
@K J Rad - you mean after it boots to the stock ROM, going to settings/security/factory reset (or clear all user data, whatever it says?) - I've tried that twice, and each time it comes back to apx-mode only, and when I nvflash again all my wifi settings are still in place.
if you mean factory wipe / reset from w/in Clockwork - I can't get CW to install.
EDIT - I added more explanation in my earlier post - a "how did I get here" of sorts...
Ok... if you hold down the Volume Up key during the reboot after nvflash does it drop back to APX or enter Recovery? If it goes to recovery... try method I from this: http://forum.xda-developers.com/showthread.php?t=1030915
I read and read - did not see an answer to my question - if so I did not understand.
I have ran the NvFlash and it appeared to go okay - but now my Gpad does is rotate back and forth between the Viewsonic and Gtablet screen.
I am stuck on what to do next.
Thanks very much for your help!
Same exact thing happened to me Friday night. I fixed it by partitioning to 2048 0 using CWM via NVFlash.
How do you do that?
Sorry to be so thick!!!!
I found the downloads for cwm - how do you access that with NvFlash?
You can flash the stock recovery images and swap in teh part9.img with the CWM recovery file taken from the cwm zip.
Basically, you need to extract the CWM recovery zip and get the recovery.img file. You rename this to part9.img and replace the part9.img file in the nvflash_stock 1105 directory wherever you have it.
Alternativly, you can put CWM recovery on the microsd card, the instructions are in the CWM recovery thread.
Finally, I had issues failing to boot when I was using a different nvflash.exe. You should use the 140KB nvflash file for the process outlined int eh stock recovery thread.
CWM and nvflash are 2 different things. Install cwm and repartition as suggested.
tgatlinjr said:
How do you do that?
Sorry to be so thick!!!!
I found the downloads for cwm - how do you access that with NvFlash?
Click to expand...
Click to collapse
Here's a step-by-step tutorial:
http://forum.xda-developers.com/showthread.php?t=1030042
Once you're into CWM just go to advanced and then partition to change to 2048 & 0.
Btw, since you're going to be changing two files in your NVFlash folder (part9.img & nvflash_gtablet.bat) you may want to copy them somewhere else on your pc so you can put them back after you're done.
I did manage to get it to boot and download the 3588 update but when it reboots and tries to apply the update it fails.
Any ideas?
tgatlinjr said:
I did manage to get it to boot and download the 3588 update but when it reboots and tries to apply the update it fails.
Any ideas?
Click to expand...
Click to collapse
One way is to get the 3588 zip from the forum here & download it to the root of the G Tablet. Rename it to update.zip & install with CWM. I'd also wide data/factory reset & wipe cache partition too.
I have installed CWM now with no problem.
The Gpad boots to Viewsonic Tap UI version1.0-2638
It then informs me that there is an update to 3588
It proceeds to download the update - asks me to accept and apply the update
States it will shutdown to apply this update - it does, reboots - and after a few seconds a triangle with an exclimation mark along side the little Android man pops up and will do nothing else.
I, also, downloaded the 3588.zip file as suggested in the previous reply and got the same result.
I wiped the cache and did the data factory reset as well.
Any ideas to where I can go from here as all of this is new to me?
Hi everyone - got it fixed.
I appreciate everyones help.
I had been running BOS 5.4 and I kept getting errors saying that Tablet memory was low and nothing I tried could get that error to go away. I tried uninstalling apps, tried wiping user data, nothing fixed it. Everything would FC constantly.
Long story short, now every time that I boot my GTab it boots straight into recovery without me pushing the volume key. I have tried re-installing BOS but nothing takes. I mount USB through ClockWorkMod and nothing is there except for the BOS zip file that I placed on the memory. Everything else is gone. I tried partitioning the sd card to 2048/0 and then tried re-installing BOS but to no avail. I am all out of idea.
Any ideas??
First off, there is no BoS a5.4 - not sure if you're running BoS or another HC ROM.
Second, did you try and do a factory reset while in the UI, and while cwm was installed? If so, then this is a known issue with cwm. I have instruction on Slatedroid for my ROMs, but to paraphrase here. Use either method:
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
Again, this is assuming that this is really Bottle of Smoke and not another ROM. If it's not BoS, then the ADB instructions may not work.
roebeet said:
First off, there is no BoS a5.4 - not sure if you're running BoS or another HC ROM.
Second, did you try and do a factory reset while in the UI, and while cwm was installed? If so, then this is a known issue with cwm. I have instruction on Slatedroid for my ROMs, but to paraphrase here. Use either method:
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
Again, this is assuming that this is really Bottle of Smoke and not another ROM. If it's not BoS, then the ADB instructions may not work.
Click to expand...
Click to collapse
I apologize, it was BOS 5.2. I will try this out and report back, thank you very much for the reply, roebeet. I am LOVING Bottle of Smoke, btw. Thanks for your hard work.
adb method is not working. I can't get it to find my device :/
If the factory restore in the UI was the catalyst, then one of these two options should fix it (if you can get it working). I've had this happen to me with cwm, on my Froyo ROMs.
What happens is that the device wants to wipe the user data, but cwm doesn't understand how to do that the way the device wants it to. So on every reboot it just keeps trying. When standard recovery is added back, the process can complete.
There is potentially one other way, but will take a few steps and I've never tried it myself.... in cwm, mount the device to your PC via the mounts and storage -- USB storage option. Then, grab the 4349 recovery update.zip that I advertise in Slatedroid (sorry, not allowed to give you a link as its against XDA rules - just google "1.2 recovey gtablet 4349"). Take that update.zip and put it somewhere on the mounted drive, unmount, then use cwm to run that update.zip. That should, in theory, get you standard recovery again and might allow the data wipe process to finish.
roebeet said:
If the factory restore in the UI was the catalyst, then one of these two options should fix it (if you can get it working). I've had this happen to me with cwm, on my Froyo ROMs.
What happens is that the device wants to wipe the user data, but cwm doesn't understand how to do that the way the device wants it to. So on every reboot it just keeps trying. When standard recovery is added back, the process can complete.
There is potentially one other way, but will take a few steps and I've never tried it myself.... in cwm, mount the device to your PC via the mounts and storage -- USB storage option. Then, grab the 4349 recovery update.zip that I advertise in Slatedroid (sorry, not allowed to give you a link as its against XDA rules - just google "1.2 recovey gtablet 4349"). Take that update.zip and put it somewhere on the mounted drive, unmount, then use cwm to run that update.zip. That should, in theory, get you standard recovery again and might allow the data wipe process to finish.
Click to expand...
Click to collapse
roebeet, you are my freaking HERO!! I downloaded the 4349 recovery update.zip and BOOM Bottle of Smoke is booting up like a champ. Thank you for taking the time to help me do this!!
http://www.youtube.com/watch?v=0N-SyPEL-pA
fidju said:
roebeet, you are my freaking HERO!! I downloaded the 4349 recovery update.zip and BOOM Bottle of Smoke is booting up like a champ. Thank you for taking the time to help me do this!!
http://www.youtube.com/watch?v=0N-SyPEL-pA
Click to expand...
Click to collapse
Thanks for the update! I might actually need to add those steps to my ROM's cwm caveats in my first posts (might be easier than adb/nvflash for most people).
Didn't find "GTablet for dummies" until after the fact and the directions I found for installing cwmod didn't mention a conflict between v.8 and bootloader 1.2. Still ... it's my fault.
In any case. Upon attempt to boot into recovery, the unit just spits out:
Recovery key detected
Booting recovery kernel image
and hangs.
As a potential remedy, I put the right cwmod files (for loader 1.2) from the "Gtablet for dummies" tutorial into root of the internal sdcard and upon reboot (power and + volume) the unit still hangs with the same message.
I just want to go back to the native recovery and start all over if possible.
Help is appreciated. Thanks.
Mark
The only way I know is to nvflash to 4349 and start over.
Steve in CT
Sent from my GTablet using Tapatalk
Thanks Steve. That did the trick.
Finally got tired of all the FC with the stock image. Thought maybe I had done something wrong so reset the device from the settings menu. Now all I get is Booting recovery kernel image but nothing moves forward. All I see is Viewsonic with the birds.
How can I recovery or mod to a working image? I will most likely need step by step instructions
I have the same thing, so annoying, can't even get NVFlash working.
bricked
I've seen plenty of comments saying that these have not been bricked. Guess we are the first unless there is another term for what we have.
sorry to bring up an oldish thread ...
I'm having difficulty after trying to flash to 1.2 bootloader and was wondering if someone can point me in the right direction.
I went back to 3588 stock, worked fine. I then tried to update to 4349. Now I get the viewsonic boot logo, and it goes no further. If I try the recover key, it sits on "Detect a recovery key pressed \r Booting recovery kernel image" and doesn't go anywhere.
I tried nvflash via the volume- button, and I get to (after ensuring the driver is loaded);
D:\nvflash>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --config
file gtablet.cfg --create --go
Nvflash started
miniloader download failed (response read failed)
rcm version 0X0
Press enter to continue:
Can anyone give me a shove in the right direction?
Cheers
theadm said:
Can anyone give me a shove in the right direction?
Cheers
Click to expand...
Click to collapse
I think I had the same issue last week when I went from a v1.1 bootloader rom to a v1.2 bootloader rom without using stock recovery to go from the old version to the new version. I used ClockworkMod to flash the v1.2 bl rom and it made my gTab do what you are describing.
I had to NVFlash to a stock v1.1 TnT rom that included ClockworkMod .8 and then use ClockworkMod to flash the last v1.2 TnT rom which got rid of ClockworkMod and installed the stock recovery which I then had to use to flash to the latest v1.2 bootloader based rom I chose which was Mountain Laurel 3.1.0 (the last release from Roebeet on another site).
After I did that and had a gTab that had a v.1.2 bootloader ROM running on it I installed ClockworkMod that is v1.2 bootloader compatible and installed Pershoot's last FroYo kernel for our gTabs.
Now my gTab is running great and I'm a happy camper.
Good luck.
Hey there,
Thanks for the reply.
I ended up changing USB cables and got NVFLASH to work.
I'll have to throw the other one away.
So what I was stuck on was;
1. At boot, viewsonic logo screen.
2. At recovery, stuck on "Detect a recovery key pressed \r Booting recovery kernel image"
3. At APX mode, stuck on "miniloader download failed (response read failed)" after entering the nvflash_gtablet command.
I changed USB cables, and now I am back in business. I'm back to stock 3588.
Cheers!
theadm said:
I changed USB cables, and now I am back in business. I'm back to stock 3588.
Cheers!
Click to expand...
Click to collapse
That's great news.