Database Info

recovery screen

I cant get this into recovery. just bought and want to install clockwork. When I push the power and volume up buttons it just keeps going round and round. I see the ! mark, but doent go to recovery. help please!!!

which version of clockwork are you trying to install?

2.5.1.2 but cant get any recovery screen

Yeah, I can't flash 2.5.1.2. Do you have the tablet that came with a green wipe cloth? There is something different about the green ones. 2.5.1.1 installs easy though.

i cant get any kind of recovery screen though. did you just rename to update.zip and it flashed?

Yeah if you flashed 2.5.1.2 your probably getting the "magic mismatch error". Your going to have to NV flash restore to get her back up running.

dont know what you mean. please explain. also can you post the apk?

Its not a apk. Here's the link, follow everything carefully. This worked with mine several times.
http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=064f93edb521637e523f3365482dffc3

[Q] Unable to boot G-Tab after updating ClockworkMod inside of ROM Manager.

I have a new G-Tab. I was able to install ClockworkMod and update to the latest version of TnT Lite without an issue.
I stupidly installed ROM Manager and allowed it to install the new ClockworkMod Recovery. I realize now that I should not have allowed it to do that, as cwm 0.8 works better than cwm 0.12.
Now, I am unable to boot my tablet, specifically every time I shut the tablet off it goes into APX mode.
I have installed the APX drivers, the NVidia Tegra SDK, and have used NVflash. Using NVflash I am able to flash back to stock. I have tried using NVflash to flash clockworkmod back to recovery. Despite this, whenever I reboot the tablet, I am right back into APX mode. The only way to get my tablet back to working is to flash back to stock and allow NVflash to boot directly into the stock image. Once I turn off the tablet, I am unable to do anything except run NVflash again to get myself back into stock TnT.
I did not use NVflash with anything other than "nvflash_gtablet_2010110500". I did not use --odmdata. I have tried both Power+Vol(-), Power+Vol(+), Power+both Vols. With any of these methods I am unable to tell any difference in the power state of the tablet. The NVflash batch file is able to reflash the device without issue.
The battery is fully charged and I did not flash without using AC power.
Please excuse my verbosity but I am trying to answer all possible questions and be as specific as possible.
I am unable to boot my GTab after updating ClockworkMod to the newest version through ROM Manager. I have tried every recovery method I have found, and am unable to do anything but boot the stock image. Once I power down the tablet, I am unable to do anything except flash the stock image again. What are your suggestions?

There is an option to install bekit08 from the ROM Manager I think. Down towards the bottom. Once you nvflash into the stock OS have you tried installing ROM manager and letting it reflash the 08 CWM?

Join the limited club
You can nvflash the recovery.img from Bekit, just hold the Volume + when you push enter on your computer's keyboard.
ie...(recovery named bekit.img in this example)
have tablet attached via USB, have tablet in APX mode..
nvflash --bl bootloader.bin --download 9 bekit.img --go
press and hold Volume + on the tablet and immediately press ENTER on the computer to execute the above line.
This will push clockworkmod to the tablet and then boot into recovery. Use recovery to mount USB so you can copy whichever ROM you want to the device....
dismount USB, wipe system (factory reset option in recovery) then install ROM from sdcard.
When completed....and you reboot....of course it won't do anything...
So....while attached and in APX mode...
nvflash --bl bootloader.bin --download 9 bekit.img --go [ENTER]
This reflashes the recovery and boots the tablet.
Voila....VEGAn or TnT-lite installed. Configure, use....never reboot or power off.
If you must power off.....use nvflash to "force boot" the tablet again.
I have to do this on one of mine.
See this post...
http://forum.xda-developers.com/showthread.php?t=903684

muqali said:
There is an option to install bekit08 from the ROM Manager I think. Down towards the bottom. Once you nvflash into the stock OS have you tried installing ROM manager and letting it reflash the 08 CWM?
Click to expand...
Click to collapse
I will try this.
[Edit]
ROM Manager installed, but the only option now is Advent Vega. I understand they are similar but I am not going to try flashing the Advent Vega CM image, especially considering I don't think it will fix the issue. (I have no problem flashing CMW, I can just never get into recovery.) Thank you for the suggestion though!
[Edit #2]
I tried it anyways, despite my reasoning against it. I had options to change to CMW 2.5.1.0, 2.5.1.1, 2.5.1.3, 2.5.1.4 (curiously no 2.5.1.2, which is what caused this all). I was unable to change to these other CMW recoveries, it gave me an error.
tcrews said:
Join the limited club
...
See this post...
http://forum.xda-developers.com/showthread.php?t=903684
Click to expand...
Click to collapse
This is exactly the symptoms I'm experiencing. That's disappointing. I hope the latest two posts or so end up working!

Are you able to boot into the version of CWM that was installed?

My suggestion....if it's within the return period of wherever you purchased.....take it back and swap it out.

NMCBR600 said:
Are you able to boot into the version of CWM that was installed?
Click to expand...
Click to collapse
Nope.
tcrews said:
My suggestion....if it's within the return period of wherever you purchased.....take it back and swap it out.
Click to expand...
Click to collapse
Yessir, these are the words I was expecting to hear. Gonna do that today...

I believe this is easier
I had issues with mine when I first started as well. I found that by using my sd card and renaming the sdcard in the "command" file I was able to recover. I still have issues but I am able to recover. I also still rely heavily on nvflash but I can install crm without forcing it. I am also able to use the power option on the device.
dcom222 original post: http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7

[Q] Apx bootloop after NVflash

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!!!!

[Q] Update Verification failed in 3e system recovery

Hi all. I'm new to android, but not to modding. I've been with xda for a few weeks and have appreciated the quality of the posts and tutorials. Btw-I have searched the forums and google and am still soo lost.
Any help would be appreciated.
Goal:
-To get stock kd1
Previous Config:
-Black Ice KD1, CWM recovery red, voodoo lag fix, ext4 on all, Bali 3.2 no uv, Juwe ram script
-was previously overclocked using tegrak ultimate to 1.2ghz, but about a day before my error it had been put back to 1.0ghz and tegrak uninstalled.
What I did (error):
-Boot CWM red wipe data, cache, factory reset
-boot download mode, flash T959VKB5-Custom.tar with Odin 1.7
-Phone reboots into stock android recovery (3e)
-selecting reboot phone bring galaxy s splash, then back to recovery
-selecting reinstall packages; it looks for the update.zip but I keep getting verification failed
What I Know
-verification fails because im using default 3e recovery
-i need to use odin to flash a new kernel with the 2e recovery
What I'm confused about
-All kernels that I've found are .zip, odin takes .tar
-I cant use the .zip kernels because I cant install a package
-I cant install a package because verification fails
-verification fails because using 3e recovery
-cant flash kernel with 2e recovery because i dont know how!
So again all comments are appreciated. Thanks for reading.

Mizun0h said:
Hi all. I'm new to android, but not to modding. I've been with xda for a few weeks and have appreciated the quality of the posts and tutorials. Btw-I have searched the forums and google and am still soo lost.
Any help would be appreciated.
Goal:
-To get stock kd1
Previous Config:
-Black Ice KD1, CWM recovery red, voodoo lag fix, ext4 on all, Bali 3.2 no uv, Juwe ram script
-was previously overclocked using tegrak ultimate to 1.2ghz, but about a day before my error it had been put back to 1.0ghz and tegrak uninstalled.
What I did (error):
-Boot CWM red wipe data, cache, factory reset
-boot download mode, flash T959VKB5-Custom.tar with Odin 1.7
-Phone reboots into stock android recovery (3e)
-selecting reboot phone bring galaxy s splash, then back to recovery
-selecting reinstall packages; it looks for the update.zip but I keep getting verification failed
What I Know
-verification fails because im using default 3e recovery
-i need to use odin to flash a new kernel with the 2e recovery
What I'm confused about
-All kernels that I've found are .zip, odin takes .tar
-I cant use the .zip kernels because I cant install a package
-I cant install a package because verification fails
-verification fails because using 3e recovery
-cant flash kernel with 2e recovery because i dont know how!
So again all comments are appreciated. Thanks for reading.
Click to expand...
Click to collapse
your so use to having the recovery file already put into system/bin so you forgot to do it when you flashed kb5
you see after kd1 it was no longer needed to push the recovery file yourself because its been implemented in all the roms since
so look into krlons CWM final and push the recovery file into /system/bin
then try again you wont get the error

dsexton702 said:
your so use to having the recovery file already put into system/bin so you forgot to do it when you flashed kb5
you see after kd1 it was no longer needed to push the recovery file yourself because its been implemented in all the roms since
so look into krlons CWM final and push the recovery file into /system/bin
then try again you wont get the error
Click to expand...
Click to collapse
Thank you. This definately sounds like the answer I'm looking for. But how would i go about pushing the file to the system if I cant boot my phone?
Will droid explorer still do that?

Mizun0h said:
Thank you. This definately sounds like the answer I'm looking for. But how would i go about pushing the file to the system if I cant boot my phone?
Will droid explorer still do that?
Click to expand...
Click to collapse
I think it'd be easier to get a ROM like this one:
http://forum.xda-developers.com/showthread.php?t=1063696
It already comes rooted so you can throw in the custom recovery file, then go back to a completely stock build (I think that's what you want).
After you flash that rom with odin, get both the files in the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1099374
You'll be able to get into CWM from there and that'll give you more flexibility.
You probably won't be able to get into download mode from the bootloop you're getting, so do a battery pull, then put the battery back in, hold down both volume keys, and while those are still pressed, press the power button. You should get a screen with a big yellow triangle with an exclamation mark in the middle, which you probably already know is download mode.

Thanks for the quick response. Worked like a charm until, only through impatience, come across another problem.
I was following the steps from this thread
http://forum.xda-developers.com/showthread.php?t=1141550
-I got cwm, flashed ext4 converter, flashed black ice, and then i wanted to install bali 3.1
-By mistake i downloaded the non uv package to the sd card. So out of impatience pulled the sd card and dropped the uv one on their.
-not to my surprise cwm didnt see any changes. so i went to advance, then reboot recovery
Now my phone boots straight to galaxy s splash and stays there. I cant access cwm or download mode. Any ideas?

Did you have bali 2.1 or higher before flashing the ext4 converter? If you don't it will soft brick, from what I know. Flash odin and restart.
Sent from my SGH-T959V using XDA Premium App

Mizun0h said:
Thanks for the quick response. Worked like a charm until, only through impatience, come across another problem.
I was following the steps from this thread
http://forum.xda-developers.com/showthread.php?t=1141550
-I got cwm, flashed ext4 converter, flashed black ice, and then i wanted to install bali 3.1
-By mistake i downloaded the non uv package to the sd card. So out of impatience pulled the sd card and dropped the uv one on their.
-not to my surprise cwm didnt see any changes. so i went to advance, then reboot recovery
Now my phone boots straight to galaxy s splash and stays there. I cant access cwm or download mode. Any ideas?
Click to expand...
Click to collapse
Check your mounts to make sure they are
Code:
unmount
mount
mount
unmount
You'll need to reflash a rom using odin though, you won't be able to use CWM until you do.

Thank you. worked great.

Bricked TF101 Need Some Help!

So I recently tried to install a new ROM and I bricked the TF101. So I will try to elaborate the best I can of the situation. The first thing I did was root the tablet which I was able to with the Peri 0.4 -->http://forum.xda-developers.com/showthread.php?t=1681155
I then installed ROM Manager and I was able to install CWM Recovery v6.0.1.3
At this point, I was like I just install zip from sdcard and just load my ROM. I then try to do so, but I kept getting the error:
E: unknown volume path [/sdcard/]
E: Can't mount /sdcard/
I remember reading somewhere here on XDA to refresh the storage so I went to the main menu of CVM recovery --> mounts and storage
format system/catche/data
After that, the TF101 couldn't boot up anymore. I tried the nvFlash fix here: http://forum.xda-developers.com/showthread.php?t=1123429
I do the Volume up + Power and the thing loads into my computer. I followed everything up until I run the download windows batch file, every time I click it nothing happens. The cmd just comes on for a split second then goes away.
So I am now stuck with a $200 tablet that is a paperweight. If anyone has any solution. It would be great!

Dorianking said:
So I recently tried to install a new ROM and I bricked the TF101. So I will try to elaborate the best I can of the situation. The first thing I did was root the tablet which I was able to with the Peri 0.4 -->http://forum.xda-developers.com/showthread.php?t=1681155
I then installed ROM Manager and I was able to install CWM Recovery v6.0.1.3
At this point, I was like I just install zip from sdcard and just load my ROM. I then try to do so, but I kept getting the error:
E: unknown volume path [/sdcard/]
E: Can't mount /sdcard/
I remember reading somewhere here on XDA to refresh the storage so I went to the main menu of CVM recovery --> mounts and storage
format system/catche/data
After that, the TF101 couldn't boot up anymore. I tried the nvFlash fix here: http://forum.xda-developers.com/showthread.php?t=1123429
I do the Volume up + Power and the thing loads into my computer. I followed everything up until I run the download windows batch file, every time I click it nothing happens. The cmd just comes on for a split second then goes away.
So I am now stuck with a $200 tablet that is a paperweight. If anyone has any solution. It would be great!
Click to expand...
Click to collapse
1. You used ROM manager - that is why your tf seems trashed. There is a warning thread stickied at the top of the general section to this effect.
2. Try a cold boot - power plus volume down (like you were booting to recovery) but don't push volume up and let it take you to the cold boot/wipe option.....select boot from Linux.
3. Hopefully that at least gets you into your ROM or recovery.
4. http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Read this to try and remedy the problem if you can get into the working system
If not and you've blanked the slate then one of the other guys who have used peri or one of the nvflash tools will hopefully guide you through.
Also what version of tf do you have? Are you B70+ or B60 or lower?
If your B70+ then the nvflash guide you used most likely failed as its not designed for your version.
---------- Post added at 08:28 AM ---------- Previous post was at 08:11 AM ----------
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Try white kidneys tool and see if it gets you back to life.

If I had a dollar for every person I have helped unbrick because they used ROM Manager, I could have a Nexus 7, Nexus 10, Note 10.1 and an Infinity.
Anywho, my recommendation is to use EasyFlasher in APX Mode (VOL UP & POWER)
I wrote a guide on how to install a custom recovery and then root and/or ROM here:
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
You can skip over the backing up your current ROM most likely, just install a custom recover (if you choose CWM, do NOT use ROM Manager to update it).
I personally like TWRP much better myself.
Hope this helps!

I use the EasyFlasher and it worked brillantly.
Thanks!