[Q] gtablet bootloops after nvflash, clockwork not accessible - G Tablet Q&A, Help & Troubleshooting

Hello all.
I've gotten into a serious bind here and I'm hoping someone can help me out.
I've had my gtablet since early January, and I've successfully flashed vegan 5.1, tnt lite, and calkulin 1.1.
this morning, I got the itch to try one of the CM7 nightly builds. i'd read it was a good idea to nvflash back to stock prior to installing a CM7 build, so I familiarized myself with that process and proceeded to nvflash. i successfully got back to stock, succesfully flashed cm_harmony_full_teamdesire_tt.RC2-20110407-1710, and then after powering down I wasn't able to boot back up succesfully. the rom hung at the 'A N D R O I D' screen prior to the boot animation.
at that point I figured i'd go back to calkulin 1.1, since the 2.2 OS had never given me much of a problem. I nvflashed successfully, which led me to where I am now:
I am bootlooping at the "with Tap N Tap" boot animation screen when I try to boot up. It'll cycle through the boot animation 10 times or so, then end on a black screen.
The worst part: I am unable to get into clockwork recovery mode. When I hold down VOL+ & power, it detects a recovery key, then it goes to an 'A N D R O I D' screen, hangs a few seconds, then I see a grey triangle with an exclamation point, then it reboots... then boot loops at the "with Tap N Tap" boot animation screen noted earlier.
help! i'm not new to all this, but it looks like I may have bitten off more than I can chew here jumping into the CM7 nightly builds.
is there anything I can do with the nvflash_gtablet.bat file to rewrite clockwork recovery?

never mind. I hadn't tried to get into clockwork with an external SD card. that method worked. thanks for the space -- just getting my thoughts together in writing helped point me in the right direction!

How did you fix this? the same thing is happening to mine. Thanks

pmoney420 said:
How did you fix this? the same thing is happening to mine. Thanks
Click to expand...
Click to collapse
My website in signature. Go to start here page. You're a code red.

Related

Now my new G-Tablet won't boot.

So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help

[Q] GTab woes

I'll try to keep this to the point and not too noobish. I've been a lurker for awhile and had Vegan Tab Ginger Edition on my Gtab awhile now. I tried to re-flash with this rom (Flashback - Honeycomb 10.1) the other day and that's when the problems have started. I used clockwork mod from this (Install clockwork, a rom, and market) thread back when I first re-flashed my device. I followed the guide for that rom and it seemed to be successful until it rebooted. I believe it just sat at the ViewSonic screen and didn't go any farther... I looked for NVFlash and set that up and was able to flash the recovery rom from here (I think..). I tried the hotkey to boot back into the recovery and the screen said android but had the exclamation point. I tried installing a later version of clockworkmod but it seems to be stuck in an installation loop unless I boot into TapnTap and remove the update.zip and recovery folder. So my questions are, is it possible to go back completely stock or to "square one" so I can get a later version of clockworkmod, then put either that Honeycomb rom or a newer version of VeganTAB (or even CyanogenMOD) on it? Also, how do I tell what bootloader I've got? I've had this tablet for at least a year and I know it was before the newer bootloader was released that had so many issues. Last but not least, When I try the shortcut to get it to boot into NVFlash mode it doesn't recognize the key... Here's hoping I didn't wear out the volume - button. :/
Thanks
dreamersrevenge said:
I'll try to keep this to the point and not too noobish. I've been a lurker for awhile and had Vegan Tab Ginger Edition on my Gtab awhile now. I tried to re-flash with this rom (Flashback - Honeycomb 10.1) the other day and that's when the problems have started. I used clockwork mod from this (Install clockwork, a rom, and market) thread back when I first re-flashed my device. I followed the guide for that rom and it seemed to be successful until it rebooted. I believe it just sat at the ViewSonic screen and didn't go any farther... I looked for NVFlash and set that up and was able to flash the recovery rom from here (I think..). I tried the hotkey to boot back into the recovery and the screen said android but had the exclamation point. I tried installing a later version of clockworkmod but it seems to be stuck in an installation loop unless I boot into TapnTap and remove the update.zip and recovery folder. So my questions are, is it possible to go back completely stock or to "square one" so I can get a later version of clockworkmod, then put either that Honeycomb rom or a newer version of VeganTAB (or even CyanogenMOD) on it? Also, how do I tell what bootloader I've got? I've had this tablet for at least a year and I know it was before the newer bootloader was released that had so many issues. Last but not least, When I try the shortcut to get it to boot into NVFlash mode it doesn't recognize the key... Here's hoping I didn't wear out the volume - button. :/
Thanks
Click to expand...
Click to collapse
Most probably you flashed a 1.2 ROM on a 1.1 Bootloader.
If you have a year old gtab you are most probably on a 1.1 Bootloader.
Bootloader/ROM table here
http://viewsonic-gtablet-for-dummies.webs.com/rom.htm
I havent had to do this myself, but from what I hear the best place to figure out how to fix in your case would be
http://viewsonic-gtablet-for-dummies.webs.com/
code red section.
Awesome, thanks, I'll check that out.
I tried the battery disconnect trick and let it sit like that overnight. Unfortunately it still refuses to boot into APX mode. Maybe I should try and short the capacitors out too?
Even if you soft brick the gtab, APX mode usually still works. When you press the - volume button and then the power button, do you see the 3 birds shows up and then the screen black out, if so it is normal.
Do a adb devices to see if you can see the gtab.
I'll see what I can do with it tonight, hopefully I Can get it un-bricked so I can throw a better ROM on it and make it usable again.

Boot Loop, No Boot Loader! Help!

My tab is in a boot loop when i tried to put it back to stock rom, and i cannot get into any boot loader it never loads, i can get to the apx mode and nvflash.
This Tab had 1.1 to start, then somehow i ended up with 1.2 on it then i had a bad crash and i cant get into recovery. I press the power and sound button for recovery and get the litle message like its going into it but it wont. Ive tried to use nvflash to go back to stock rom but it is in a boot loop now.
How or where do i get something that will give me a way to get back into a functional clockwork mod or some sorta boot loader? I think i need "NVFlash rev5 by tlb1961" but the links to is are gone. Basically i need to know how to nvflash back to a functional boot loader. Or Fix this boot loop? From there i can install a new flashback 10.3 Can anyone help me? I need files and instructions.
Thanks
Try this procedure out.
You'll should get a 1.1 stock ROM. Then, let it update itself to the 1.2.
Ive tried it, i still get to the tap n tap screen and boot loop, meh ive even tried a format rom to try to clear everything so i can get a boot loader back on it to load something else besides stock. No luck!
Tarkster said:
Ive tried it, i still get to the tap n tap screen and boot loop, meh ive even tried a format rom to try to clear everything so i can get a boot loader back on it to load something else besides stock. No luck!
Click to expand...
Click to collapse
If you're experiencing a boot loop then the bootloader is actually OK. Problems with the bootloader present as a hang at the first splash screen or no splash screen at all--you don't get a boot loop.
Your problem is most likely a bad ROM install or a messed up SD internal card and the steps already given will fix both problems if you do them precisely. Some of the steps ask you to verify that some things have happened. You need to make sure that it was and not just continue on blindly.
Assuming you completed all the steps correctly, we should be able to look at the logs messages to find out if its some sort of HW problem.
Power off the gtab, connect a USB cable to the PC, and run this ADB command in a CMD window on the PC to collect the Android logs:
Code:
C:\SOME\PATH> [B]adb logcat -v time > log.txt[/B]
Then power on the gTab. Let it boot-loop a few times while the logs are being collected. Power off the gTab, stop the adb command in the window and post the log.txt file here.
Flashback 10.3 reboot problem
I can get Flashback 10.3 install - all apps run fine... but when I reboot it gets stuck on the three birds and I have to NVFlash it again.
Can someone help?

TWRP Recover Boot Noob Problems

Alright guys, I need some help.
I tried installing twrp using adp / fastboot. I thought everything was going well. Everything came up as finish, the blue bar was full for a good 10 min, so I issued the restart command, and crossed my fingers it restarted.
I stared as I hoped I didn't screw something up.... android seemed to load fine and go to the lock screen. I was relieved. :
So, I tried rebooting (PWR + Vol Down) and choose RCK to load twrp. Now it just sits there, at " Booting recovery kernal image" and dosen't go anywhere.
Any ideas?
My goal is to flash AndroWook HairyBean.
Edit
Let me add that I am a novice at this at best. As far as I know, twrp may not have even took? But once I get twrp working, I can flash Hairybean, right?

[Q] Stuck in recovery boot loop midflash upgrading to KitKat 4.4.2 on dtmo SGS3

My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...

Categories

Resources