I ran nvflash to restore the gtablet to stock.
The flash completed successfully and Tapntap booted, however all my luanchers and old apps were still there. When I reboot the device goes directly into Apx. Powering with power button no volume, vol- or vol+ gives same result. If I repeat the flash It boots into tapntap bet debits into apx. Do I need to do a factory reset here or somthing else. I am going to try a data wipe and factory reset tonight at the first boot. I want to install TNTllite 5.00 a cordinto.the install post can't install clockworkmod but some post seem to indi ate install with clo kwor works Any Help appreciated.
Im having the exact issue any help would be greatly apreciated. I flashed to stock and all went well but when i power off it gets stuck in apx mode.. The only way I even know it's on is because when I plug the usb into the comp I get the connected notification. PLEASE HELP
Just a complete guess but did you check to see if the vol - was stuck?
Gentlemen:
When I nvflashed both of my tablets, it went through the process -- then it rebooted and started up the version being loaded right up to the main screen all by itself.
I never had to do a thing after starting the .bat file to flash except watch.
I don't know how this will help, but maybe it will stimulated and idea!!
Rev
Thanks to Roebeet I have a working gtablet again! The newer belkit img in his dropbox caused the APX bootloop, I dont know why. As instructed I used the older img and that worked. Did a factory reset and now have a clean install, ready for TNTlite 5.01!
got mine working last night had to use nvflash_gtablet_46 and nvflash_windows_20100500.zip instead of the nvflash_gtablet_2010110500.zip and it worked great for some reason that nvflash_gtablet_2010110500.zip would make my tab get stuck in a bootloop stuck in apx mode!!! Hope this helps it worked for me!
Can you guys please help me? i am in a similar issue. I tried using the 3588 stock .zip to get ready to install tnt 5/ ttx.9 and well it started to boot loop so to NVflash i went. I have tried
nvflash_gtablet_46 and nvflash_windows_20100500.zip and nvflash_gtablet_2010110500.zip and gtab.spx.stock.3588.zip and NONE of them work for me. I am able to sucessfully NVflash them but when the tablet restarts it goes to the tapntap screen the flashes back and forth between that screen and a black blank screen before it goes completely black... The tablet remains on though just with a blank screen and i must hold the power button for 10 seconds to power it off. i have tried every combination of flashing i can think of but no dice.. please help?
ddarvish said:
Can you guys please help me? i am in a similar issue. I tried using the 3588 stock .zip to get ready to install tnt 5/ ttx.9 and well it started to boot loop so to NVflash i went. I have tried
nvflash_gtablet_46 and nvflash_windows_20100500.zip and nvflash_gtablet_2010110500.zip and gtab.spx.stock.3588.zip and NONE of them work for me. I am able to sucessfully NVflash them but when the tablet restarts it goes to the tapntap screen the flashes back and forth between that screen and a black blank screen before it goes completely black... The tablet remains on though just with a blank screen and i must hold the power button for 10 seconds to power it off. i have tried every combination of flashing i can think of but no dice.. please help?
Click to expand...
Click to collapse
You might need a data wipe - if you can get past the birds but get stuck at some point after the "GTablet" screen, a data wipe would be my first suggestion.
The problem is that 1105 bekit nvflash (and mine) doesn't have clockworkmod embedded in it to fix that. But, as a workaround, you can replace "part9.img" in the bekit 1105 with clockworkmod's "recovery.img" (just rename part9.img to part9.img.org and then rename recovery.img to part9.img). Redo the nvflash, the reboot into recovery when you are stuck again and wipe data. Once "fixed", then you can undo the change and reflash one more time to get back to full stock, or OTA update to 3588 to get 3588 stock.
I know this is a bit of a PITN due to all the steps, but it does work.
robeet u are absolutely correct and i posted that as my solution in the other thread i started. It finally occured to me when i was reading and there was a line that said NVflash will keep ur /data untouched. I was like OH ****.. hah. I though NVFlash wiped EVERYTHING!!!. Anyway replacing the .img with CWM.img and then wiping and then redoing the 3588 apx update worked.
Please help, can't get win7 to detect the device. When u say usb, is it mini usb on your device or is it full size usb? I was be able to run TNTL 5.0, due to afew crashes, i decide to revert back to 4.2. Since then, my viewsonic g tablet never boot again.
Thanks in advance.
khem1288,
Look at the following thread on USB for nvflashing.
http://forum.xda-developers.com/showthread.php?t=989320
There also are a couple of "Windows" nvflash links in the middle of roebeet's TwoTapX thread.
Rev
butchconner said:
khem1288,
Look at the following thread on USB for nvflashing.
http://forum.xda-developers.com/showthread.php?t=989320
There also are a couple of "Windows" nvflash links in the middle of roebeet's TwoTapX thread.
Rev
Click to expand...
Click to collapse
Thank you for your response,
Got mine to work, just want to clarify for those who use win7x64. download three files from thread... nvflash_win, nvflash_gtablet, and usb driver. Turn on device in APX mod, plug in ur tablet via mini usb. Go to windows device manager, making sure it sees APX has proper driver. Go back to nvflash folder and double click on nvflash_gtablet.bat, and relax. Once it's done flash, reboot and enjoy.
thank you all for your hard work.
roebeet said:
You might need a data wipe - if you can get past the birds but get stuck at some point after the "GTablet" screen, a data wipe would be my first suggestion.
The problem is that 1105 bekit nvflash (and mine) doesn't have clockworkmod embedded in it to fix that. But, as a workaround, you can replace "part9.img" in the bekit 1105 with clockworkmod's "recovery.img" (just rename part9.img to part9.img.org and then rename recovery.img to part9.img). Redo the nvflash, the reboot into recovery when you are stuck again and wipe data. Once "fixed", then you can undo the change and reflash one more time to get back to full stock, or OTA update to 3588 to get 3588 stock.
I know this is a bit of a PITN due to all the steps, but it does work.
Click to expand...
Click to collapse
Thanks a lot Roebeet. Saved my life too! I formatted the tablet with the format tool that is supposed to erase the BCT and then did an NVflash for the rest and was stuck in a bootloop. Tried both the 1105 and the other bekit, and ended up renaming part9.img, getting CWM to wipe data and working from there. It's TnTlite 4.4 from here on out. Thanks again.
roebeet said:
You might need a data wipe - if you can get past the birds but get stuck at some point after the "GTablet" screen, a data wipe would be my first suggestion.
The problem is that 1105 bekit nvflash (and mine) doesn't have clockworkmod embedded in it to fix that. But, as a workaround, you can replace "part9.img" in the bekit 1105 with clockworkmod's "recovery.img" (just rename part9.img to part9.img.org and then rename recovery.img to part9.img). Redo the nvflash, the reboot into recovery when you are stuck again and wipe data. Once "fixed", then you can undo the change and reflash one more time to get back to full stock, or OTA update to 3588 to get 3588 stock.
I know this is a bit of a PITN due to all the steps, but it does work.
Click to expand...
Click to collapse
so after you re-nvflash with cwm as partition 9, how do you get into cwm? after i flash to the stock ROM, i can't get to anything other than apx on shutdown/reboot.
williec30 said:
so after you re-nvflash with cwm as partition 9, how do you get into cwm? after i flash to the stock ROM, i can't get to anything other than apx on shutdown/reboot.
Click to expand...
Click to collapse
You restart while holding down the Volume Up key. If it doesn't appear to be shutting down properly then hold down the power key for 30 - 45 seconds and try it again.
K J Rad said:
You restart while holding down the Volume Up key. If it doesn't appear to be shutting down properly then hold down the power key for 30 - 45 seconds and try it again.
Click to expand...
Click to collapse
it's doesn't do anything but boot into APX mode... holding power and volume up doesn't do anything other than enter / exit that mode. that is, unless i'm missing something else...
The only thing I can recommend is to try the nvflash again. Make sure you're using bekit's 1105 image and you're following the instructions on this thread...
http://forum.xda-developers.com/showthread.php?t=861950
It does work.
K J Rad said:
The only thing I can recommend is to try the nvflash again. Make sure you're using bekit's 1105 image and you're following the instructions on this thread...
http://forum.xda-developers.com/showthread.php?t=861950
It does work.
Click to expand...
Click to collapse
the first post doesn't talk about *how* to execute the CWM install, only the nvflash. other posts in the thread talk about the CWM piece, but there is no step by step to get out of APX and into clockwork... that's what i need because something in my config is definitely out of whack.
If your nvflash worked then there is no need for a step by step other than what has been said.
1) Make sure you are using befit's 1105 image
2) Make sure you are using ClockworkMod .8
3) Make sure you've modified the gtablet.cfg file properly.
4) Make sure you didn't get any errors reported from your nvflash.
5) When it is done it should reboot.
If it boots normally, then do a factory reset from within the system settings. Then reboot while holding the volume up key and you should get CWM.
If it doesn't then try to shut it down and restart while holding the volume up key and you should get CWM.
If you're still stuck in an APX loop then I would try nvflashing just the bekit 1105. If that will boot at all you can try to load CWM from an SD card.
If you'd like to post or PM your config file, the result from your nvflash and any other files you've changed I'll be happy to look at them.
Same situation here.... tried everything that was mention but still not working.
As soon I turned on, goes a black screen (apx mode) that's it!!! Power and vol + don't do anything. the only way to boot completely is nvflashing again.... tried to reset data factory but as soon the tablet turn off (restart turn on) black screen.
Can anybody help me.... it has been 12 days already.... I had posted for help before and I already did everything that was suggested..... I don't know what to do anymore.
PLEASE HELP!!!!
I'm trying to flash the Vegan-Tab ROM on the gTablet I just got. I installed the 1.1 bootloader and CM .8. Or, I think I did. When I power up using power and volume +, I never got a menu when I tried installing these. The green box just popped up, so I assumed it was installing, then it rebooted normally. So when I try to boot into recovery mode, it does the same thing, and the menu never comes up. Did I do something wrong?
I have a similar problem ... loaded CM7 safely, was working for a while, all good. Decided (stupidly) to update recovery from CWM and now, nothing I do can get it to boot into recovery! Not manually, not through software (boot to recovery) options...
Also, the viewsonic birds screen is gone, so I assume something bad happened to the bootloader.
Still boots to 'production' cleanly, just not recovery or bootloader. Help!
FIXED - had to nvflash back to stock and start over!
After flashing the latest ROM I was messing around with (WajkIUI 2.1.6) the phone would crash and reboot within 30 seconds of booting up. The previous ROM that was running was FAUXMIUI_RG2xV2.0.0 (01/08/2011 [v2.0.0]OVERCLOCK) that was stable except for when I’d turn wi-fi on after being off for 8 hours or so phone would reboot.
I figured I would boot into ClockworkMod Recovery and restore one of the nandroid backups, I tried booting into recovery I found out that I could not. When I hold the volume down and press the power button I see the screen that says software update (like when flashing with OneClickRecoveryFlasher).
Whenever I flash a new ROM I will Wipe data/factory reset, wipe cache partition, and then wipe dalvik before installing zip. I’ve always run cyanogenmod nighties; FAUXMIUI_RG2xV2.0.0 was the first MIUI ROM I’ve used.
When I run OneClickRecoveryFlasher, I do not see any errors on the command prompt so I am assuming it was successful, or at least thinks it was.
I tried to Restore LG G2x Stock Recovery using OneClickRecoveryFlasher and then flashing v5.0.2.0 and still no ClockworkMod Recovery, also tried v4.0.1.5 and still no ClockworkMod Recover.
I then tried http://forum.xda-developers.com/showthread.php?t=1248644 and with that I was able to get back to stock 2.3.3, tried to use OneClickRecoveryFlasher to flash ClockworkMod, still no go.
I tried LG Mobile Update and that proceeded to install something, not really sure what the update was, after the update finished, phone rebooted into stock 2.3.3. Shut the phone down and tried to flash ClockworkMod and still nothing.
I did a hard reset following http://mobilephonerepairguides.blogspot.com/2011/04/lg-g2x-hard-reset.html
I also tried http://forum.xda-developers.com/showthread.php?t=1183168, that got me to stock 2.3.3 but I still could not boot in to ClockwordMod Recovery.
I’m having a hell of a time wrapping my head around what I screwed up. Did I somehow destroy the recovery partition, is that possible? Any ideas what I broke and how to fix it? Can I used adb to view the partition table, would that tell me if something was corrupt?
Any help and ideas would be appreciated, I have tried doing my due diligence and I apologize if I missed something obvious.
Thanks,
-Matt
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
If you did the LG Updater it returned your phone to stock everything, including recovery. You need to use NVFlash (One Click method okay) to reflash CWM and then you should be good to go.
When the phone is completely off, hold volume down, then hold the power button and don't let go of both until the second lg logo.
If you hold volume down too early it'll give you the software update screen.
Well that's embarrassing, thanks buru898 that did the trick and got me into CWM Recovery. I never remember holding the power button for that long but it worked and I'll remember that for next time.
Thanks
fcisco13 said:
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Sorry, I only wrote in the actual zip file name, I meant RG2x-MIUI v2.1.6-MultiLang/Powered by Faux Kernels CM v0.4.8(01/08/2012)[v2.0.0].
Thanks
TF shutdown by itself and then entered into boot loop.
There used to be CWM on it but the last ICS update broke it and there was no one around to fix neither CWM nor restore root.
Just half an hour ago, before I came to check forums here, TF responded to both volume + power up and power down buttons and I've seen both broken recovery and "wipe" screens.
Now Power Up doesn't do anything and Power Down goes into cold boot that subsequently loops after reaching unlock screen.
I see there's a nandroid back up in CWM folder on sd card created back in March as well as Titanium Backup folder dated April.
What are my options here? I have only a vague idea what Nvflash does so need a general outline before I start reading up on details.
cold-boot into android and reflash working CWM with one of the one-click tools in the general section, or use an Nvflash tool in the Development section to Nvflash rouge recovery, which will let you get back up and running. Don't use ROM manager.
Plugged TF into USB and suddenly got Power + Volume Down to boot into CWM recovery again instead of cold boot, from there got into wipe menu and now TF is back, waiting to sync all the apps now.
Thing O Doom, thanks for advice but cold boot was impossible - it went into boot loop immediately after reaching unlock screen.
I understand CWM changed original button configuration, Volume Down was supposed to be cold boot but with CWM it's recovery, and Volume Up that was original recovery now does nothing?
Is that correct?
Then broken CWM refused to enter into recovery but magically came back after connecting to the computer.
Odd, mabye you did the sequence differently, but it's good that it's working properly now.
I don't know how it works exactly, but I understand, using PC analogy, that CWM is like a separate partition and certain button configuration tries to boot the system from it, and it also has it's own boot menu where I could choose to proceed with CWM or go to the screen with the original "wipe" menu.
Right now booting CWM itself is not possible but its own boot menu is still there, it just leads to broken Android with a red exclamation mark (or to the "wipe", of course).
I don't think I want to keep CWM anymore, just root with Titanium Backup, so one more question - how to properly uninstall CWM?
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img