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
Hi guys, first post!
I really need help as I think I've tried everything.
I installed CM7 but it was low on battery while installing. Midway through the install process the screen said I need to plug into the charger that came with my device. Then it instantly went to the screen with an exclamation point and says
www dot palm dot com/ROM
Power+Center just gets it back to the same screen.
WebOS always fails at 1% and says it could not be reset.
I've tried ClockworkMod but it is unable to reinstall the .zip files.
I ran WebOS through command prompt and it said the required files were locked by an unknown file.
PLEASE HELP, my touchpad is useless now and I don't fully know what to do in ClockworkMod, which seems to be the only thing that works right now.
Here is what I Did
This is what worked for me....good luck
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if this helps. You won't be the first or the last to get this issue.
Wait... it died while installing?
Part 1: breathe
Part 2:
IF you can get into cwm right?
In CWM, you can mount the tablet as a USB drive, then copy the update cm7.zip file to it... and install it.
DO you have the blue text boot menu?
If not you need to install moboot again...
you can do that AFTER you've fixed cm7...
IF all else fails, and you can't install cm7 via CWM, then doctor it.
If you don't know how to use CWM, google it... it's pretty straight forward.
Lesson: Don't update when battery is low?
My TP will not turn on. I have tried several button combinations for varying lengths of time.
Series of events leading to current issue:
-Last night I decided to install CM7.1 Alpha 2.1, I followed the guide on this forum
-I was unhappy with the performance of Android so decided this morning to remove CM7
-Used the Acme uninstaller to remove CM7, every seemed to go well, I left the room for several minutes and came back and then it looked not so well, the uninstall grinded to a halt. The touchpad was erasing and renaming file after file from what seemed to be Android apps, I waited about an hour with no progress, still slowly erasing bad files and renaming them.
-I sensed something was not right so I turned off the TP and back on, now I could not boot into anything, i got to moboot screen but could not boot into either Android or CM7, would just hang on their loading screens. So I put back in HP recovery mode and ran Acme uninstall again.
-This time it finished fairly quickly, only a couple of minutes. But upon reboot it freezes/sticks at the HP logo and will not boot into webOS.
-My next step was to try webOS Doctor 3.0.4 so I put back into recovery mode and ran Web Doctor, web doctor will only progress to 12% and then freezes there indefinitely.
-I have tried several times, I have installed the Palm webOS SDK, still stuck at at 12%.
-Turned TP off once more and now it fails to even turn on at all, when I press power nothing at all happens, it seems dead or worse, bricked.
Any suggestions? (I am running Mac OS X Lion)
I have it turning on now, it just goes to a boot image of a triangle with an acclamation mark, or if I hold the volume up button it will go into USB mode.
But no luck webOS doctor...and it will not turn off either now, it reboots to the exclamation symbol every time I shut it down.
Anyone help?
I don't know exactly what hapened to you, but there were another thread about webOSdoctor stuck at 12% with link to this precentral tread, http://forums.precentral.net/webos-internals/295881-webos-doctor-12-issue-fixed.html
You might give it a try
Ok solved!
What I did was remove webOS SDK using the provided uninstaller and removed all nova com stuff, rebooted my MacBook and reinstalled novacom only (not the SDK) and started novacomd manually then started webOS Doctor and success.
Help! stuck at 12%
HEY ... Same thing happened to me . i cant boot into neither webos or android.
..
i was using windows 7 and not Mac. So could you please give me a step by step solution..pls..m stuck with the screen for about a week..
Solved!!
Thanks...I've got my TP alive again...thanks..
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?
Dear community,
I tried to boot into CWM (installed via Rom Manager) but nothing happend after the reboot-to-recovery, invoked via Rom Manager. The tablet was stuck at boot, displaying the Asus logo. No animations and no error messages were displayed. I needed to press and hold power to reset my prime so it would boot my rom again. I was still able to load fastboot (power + volume down)
Next I tried to reboot-to-recovery using Goo Manager. The same issue occurred, stuck at startup, displaying the Asus logo, but now I am unable to recover from that state to load the rom!. When resetting my prime it is still stuck at displaying the Asus logo. No animations and no error message displayed. I can also no longer enter the menu using power+volume down...
I am afraid I perma-bricked my Prime but ofcourse hope it is not the case. Can anybody help me confirming my fear?
Thank you for helping me out!
straumli said:
Dear community,
I tried to boot into CWM (installed via Rom Manager) but nothing happend after the reboot-to-recovery, invoked via Rom Manager. The tablet was stuck at boot, displaying the Asus logo. No animations and no error messages were displayed. I needed to press and hold power to reset my prime so it would boot my rom again. I was still able to load fastboot (power + volume down)
Next I tried to reboot-to-recovery using Goo Manager. The same issue occurred, stuck at startup, displaying the Asus logo, but now I am unable to recover from that state to load the rom!. When resetting my prime it is still stuck at displaying the Asus logo. No animations and no error message displayed. I can also no longer enter the menu using power+volume down...
I am afraid I perma-bricked my Prime but ofcourse hope it is not the case. Can anybody help me confirming my fear?
Thank you for helping me out!
Click to expand...
Click to collapse
That is bricked unfortunately.
CWM only ever worked on the ICS bootloader and there are warning everywhere on here never to use it.
You needed the correct version of TWRP for what bootloader you was on.
If you cannot get into the rom, the bootloader menu or you have nvflash backups that you created before then you are out of luck.
Hi flumpster, Thanks for clearing this up :good:
I think I have the similar problem. I have TF201 Android 4.1.2 installed and a PC Ubuntu 13.04 installed.
-First of all, I used unlocker releases by Asus. Then I loaded CWM by fastboot, but it didn't launch, I loaded CWM Touch, but it didn't launch, I loaded TWRP and again it didn't launch. When I tried to launch recovery rom every time it stuck at splashscreen.(It says booting recovery rom or smth like that)
-Then I tried to start unlocker again, it gave network error.(If you shut down the wifi it asks for internet, I think Asus collecting some information about prime.)
-Then I rooted my device. Again it stuck at splashscreen while trying to launch recovery rom. I reloaded recovery roms again it didn't work. I choose restart to recovery from the ROM MANAGER, it stuck again but nothing about "booting recovery rom" just "device is unlocked" writen. Then finally I installed CWM from ROM Manager again and I choose restart to recovery from GOO Manager. Boom! I think it tries to boot recovery rom in everytime. I can't boot android, I can't boot fastboot, power+volume down didn't work. Even I can't close it, it always restarts and I had to wait until the battery last.
So is there anything to do?