Database Info

[GUIDE] How-To: Get your recovery back!

(if anyone can, please change these to links. I'm not allowed to post links yet since I'm a new user)
First, download the froyo image from:
developer DOT nvidia DOT com SLASH tegra SLASH downloads
Then, download this and merge it with the folder that the Nvidia tools install to (you'll have to overwrite 2 files).
www DOT dropbox DOT com SLASH s SLASH wrcd87u1iy31u4e SLASH nvflash_gtablet_2010110500.zip
Download Clockwork Recovery, get the recovery.img file from the update.zip, rename it to clockwork.img, and move it into the Nvidia folder.
android DOT d3xt3r01 DOT tk SLASH cyanogen SLASH harmony SLASH root SLASH ClockworkMod_Gtab_v08.zip
Connect the G-Tab to your computer via USB and power it on while holding Vol - (NOT +!). The screen will go on for a few seconds then turn off. The tablet's not off, it's just in APX mode.
Go to Device Manager and install the drivers for it (they're in theNvidiaFolder\usbpcdriver).
Open a command prompt in the nvidia folder and enter "nvflash --bl bootloader.bin --download 9 clockwork.img"
It should do it's thing and if it goes fine, you'll get your recovery back!

You are the man!!!! I am back in business. I was on the right track, but you figured it out and I am a happy camper.
Anything you need, let me know (except girls, currency, drugs)

Quick question, Now that I have NVFlash setup and working, is there a simple way using NVFlash to take a snapshot of my Tablet so I have a backup image if I need to restore?

brookfield said:
Quick question, Now that I have NVFlash setup and working, is there a simple way using NVFlash to take a snapshot of my Tablet so I have a backup image if I need to restore?
Click to expand...
Click to collapse
You could try this: http://tosh-ac100.wetpaint.com/page/Backup+and+Restore and just use bekit's bootloader.bin.

ngorgi said:
Then, download this and merge it with the folder that the Nvidia tools install to (you'll have to overwrite 2 files).
www DOT dropbox DOT com SLASH s SLASH wrcd87u1iy31u4e SLASH nvflash_gtablet_2010110500.zip
Click to expand...
Click to collapse
I'm a little confused. This says download the file, but overwrite two files?
I have downloaded and installed the first thing. Now i have downloaded the second file but not sure what to overwrite.

You need to unzip the files into the same directory. When you do it will ask you to overwrite 2files binloader is one of them

Ok, I know that I am missing something here. I have unzipped the "nvflash" file to this directory (C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105).
I am never asked to overwrite anything. Is this the "NVIDIA tools" folder mentioned in post 1?
Sorry this is so hard for my small brain.
EDIT:Nevermind, I figured it out anyway. Thanks

I'm confused as what you mean by get your recovery back. Did you have a problem where it was overwritten?

No, for some reason it just goes away. Not sure why. When you hold power + "vol +", it should boot to recovery, but it just boots to CM.
Anyway, this was a lifesaver for sure today. Thanks for your help everyone!

Thanks, that helped a lot - works fine!
T.

I hate this tablet. I got the unit today and installed the OTA update and doing so i disabled clockword recovery. I followed these steps and got it to work from cmd and it went through the downloading process. My tablet is stuck on entering nvflash recovery mode. When i reboot and try the recovery it goes black again. I am positive I did it correctly and got the confirmation screen at the end of cmd.

I had the same issue... could not boot into recovery or the rom... right after installing clockwork .12
I had to take my unit back and get a new one...

What version of the clockworkMod image do you use to FLASH into the recovery Partition. I did not use the latest, You may need to try the 2.5.1.3 (That is what I used and it works).

Thanks!
ngorgi,
I just wanted to give you a big thanks... I had borked my g tab till I ran through your walkthrough.
Thank you so much!
-Lil'

Glad to see this actually helped a few people out
Now I may be wrong here (and if I am, PLEASE correct me), but I've come to the conclusion that this device is simply UNBRICKABLE. I've had my recovery disappear, had the magic value mismatch error, even had the device freeze in Nvflash mode where I had to wait for the batteries to drain before I could restart and I've been able to fix it EVERY TIME. Nvflash is too awesome.

FWIW, this is the only method that would work for me getting clockword to install on a fresh out of the box unit....I tried the sticky and it would show me the ! for a brief second and then reboot...
thanks!

HELP recovery problem
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
bootloader.bin sent succesfully
sending file: cwm254recovery.img
-851968/4026368 bytes sentdata send failed NvError 0x30012
command failure: partition dowload failed
Click to expand...
Click to collapse
HELP!!!!!!!!!!!!!!!!!!!!!!!!

haltol said:
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
HELP!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Try doing:
nvflash --bl bootloader.bin --getpartitiontable mypt.text --go
To get you partition table and check the .text to confirn that part9 is SOS.
Jim

I am not so sure. One of my GTablets will no longer boot. I have to use nvflash to boot it. Battery drain, reset button inside, nvflash stock rom, TnT-light...whatever, the tablet will not boot. Nvflash and format parition 2 and I can get it to proceed into booting. I can nvflash bekits recovery and install roms or kernels.....reboot or power off and it will not come up until I nvflash "force" it to boot.
So i am not so sure they are completely unbrickable...just hard to do so. Mine started with the magic value mismatch error.
ngorgi said:
Glad to see this actually helped a few people out
Now I may be wrong here (and if I am, PLEASE correct me), but I've come to the conclusion that this device is simply UNBRICKABLE. I've had my recovery disappear, had the magic value mismatch error, even had the device freeze in Nvflash mode where I had to wait for the batteries to drain before I could restart and I've been able to fix it EVERY TIME. Nvflash is too awesome.
Click to expand...
Click to collapse
Sent from my Viewsonic 10" GTab...

help Got a brick.
Got a brick. I can not get into the APX mode.
Hold down Volume (-) and power while booting - did not work. May have other options?

Applied OTA now won't load recovery..HELP

this is a brand new unit that was recieved yesterday and applied newest OTA update.
I have tried the steps from norgi and that did not work for altnerative steps to get recovery . The screen stays stuck on entering Nv flash mode. I am pretty upset at viewsonic for disabling recovery in their new OTA. Without being able to flash any roms, I am left with no choice but to return it to amazon which will suck. I have put over 4hours into getting recovery to load off my sd cards and it simply will not load. My mistake for updating to OTA but there has to be a alternative way to get into recovery!!?? is there? any help appreciated

First off, don't worry. It's very unlikely that you bricked it.
Second, I honestly doubt that VS would have borked recovery on purpose (because how would they be able to do future updates without it?).
Questions: can you link to the post you tried, and the steps you went through to get to the point you are at now? That would help with troubleshooting. If you can get to APX mode, you should be able to get recovery back. Trust me, I've done some really nasty things to my device and I haven't bricked it (yet).
My only concern is that you might have a device that has a different partition structure , which means that nvflash might mess it up. I know that bekit himself had this issue, a few weeks back. We don't know why this is, or how many devices out there are affected.

roebeet said:
First off, don't worry. It's very unlikely that you bricked it.
Second, I honestly doubt that VS would have borked recovery on purpose (because how would they be able to do future updates without it?).
Questions: can you link to the post you tried, and the steps you went through to get to the point you are at now? That would help with troubleshooting. If you can get to APX mode, you should be able to get recovery back. Trust me, I've done some really nasty things to my device and I haven't bricked it (yet).
My only concern is that you might have a device that has a different partition structure , which means that nvflash might mess it up. I know that bekit himself had this issue, a few weeks back. We don't know why this is, or how many devices out there are affected.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=878751
I didnt brick it, the device turns off/on when it gets stuck on entering nv flash mode when I hard reboot holding down power for 10sec. I followed all the steps. Downloaeded the files, updated the drivers successfully. It never reads my SD card from the computer no matter what I do though. So i have to coopy it to the HD and manuelly copy it over? Could that be it.
I read your twitter post to viewsonic yesterday about they telling us that adobe HASN'T approved flash for tegra two devices. Let me tell you it is a crock of ****. The elocity a7 plays flash perfectly out the box without any hiccups.
http://www.youtube.com/watch?v=5CvY8jzyCWI . I hate when company promise something and cant delivery so they feel the need to lie and make up some lame excuse. I appreciate your efforts rohbeet. It's frustrating to put 4+hours of work into something I paid 400bucks with to not have it work. Im not a total n00b...I've flashed/rooted my evo/hero and wii successfully with no issues. So I hardly doubt Im doing something wrong... but who knows?

stugots101 said:
this is a brand new unit that was recieved yesterday and applied newest OTA update.
I have tried the steps from norgi and that did not work for altnerative steps to get recovery . The screen stays stuck on entering Nv flash mode. I am pretty upset at viewsonic for disabling recovery in their new OTA. Without being able to flash any roms, I am left with no choice but to return it to amazon which will suck. I have put over 4hours into getting recovery to load off my sd cards and it simply will not load. My mistake for updating to OTA but there has to be a alternative way to get into recovery!!?? is there? any help appreciated
Click to expand...
Click to collapse
Wrong section, try general. Getting old digging through all these questions to find something. No disrespect Roebeet, you the man round here.

Benblanko81 said:
Wrong section, try general. Getting old digging through all these questions to find something. No disrespect Roebeet, you the man round here.
Click to expand...
Click to collapse
How is it the wrong section? I am trying to flash my unit, and load a rom

stugots101 said:
http://forum.xda-developers.com/showthread.php?t=878751
I didnt brick it, the device turns off/on when it gets stuck on entering nv flash mode when I hard reboot holding down power for 10sec. I followed all the steps. Downloaeded the files, updated the drivers successfully. It never reads my SD card from the computer no matter what I do though. So i have to coopy it to the HD and manuelly copy it over? Could that be it.
I read your twitter post to viewsonic yesterday about they telling us that adobe HASN'T approved flash for tegra two devices. Let me tell you it is a crock of ****. The elocity a7 plays flash perfectly out the box without any hiccups.
http://www.youtube.com/watch?v=5CvY8jzyCWI . I hate when company promise something and cant delivery so they feel the need to lie and make up some lame excuse. I appreciate your efforts rohbeet. It's frustrating to put 4+hours of work into something I paid 400bucks with to not have it work. Im not a total n00b...I've flashed/rooted my evo/hero and wii successfully with no issues. So I hardly doubt Im doing something wrong... but who knows?
Click to expand...
Click to collapse
No worries. So, if I'm reading this right -- you had the device clean stock (?), then it ran the OTA update automatically when you connected Wifi (I assume it loaded 3053, btw) and then it rebooted into recovery and then what? Did it flash correctly at least once? But now, if you try to get into recovery, what happens? Nothing?
And then you tried ngorgi's nvflash trick but that's not working, I assume? How far do you get? Windows 64 bit user? APX drivers working? What do you see when you type "nvflash --bl bootloader.bin --download 9 clockwork.img"? Any errors? Sorry about the questions but the details are still hazy. I think the hardest thing about nvflash is getting the USB drivers working, especially if you are running Windows 64-bit.

I cant even get into recovery... Thats the problem. When i hit power L+R volume i get the viewsonic splash screen then it goes all black. And stays black until i hard reboot.
When i ran his workaround,, i got the whole way through. Ran CMD file, it download, flashed... apppear successfull. But the screen stays in "entering nv flash recovery"
'
Correct 3053

stugots101 said:
I cant even get into recovery... Thats the problem. When i hit power L+R volume i get the viewsonic splash screen then it goes all black. And stays black until i hard reboot.
When i ran his workaround,, i got the whole way through. Ran CMD file, it download, flashed... apppear successfull. But the screen stays in "entering nv flash recovery"
'
Correct 3053
Click to expand...
Click to collapse
That isn't how you enter recovery.
v+ and power = recovery
v- and power =apx/nvflash
If you hold + and -, it goes into apx, hence the black screen.
BTW, handling flash isn't the same as being approved by adobe. I bet elocity isn't approved yet either. The gtablet handles flash perfectly.

These are my results:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714400944400297
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928956/928956 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery.img
| 3862528/3862528 bytes sent
recovery.img sent successfully
And I also see the "Entering nvflash recovery mode".
It sounds like nvflash is working for you. If you want to throw caution to the wind, you might want to go one step further and try to completely flash your device's partition structure. I have a post here:
http://forum.xda-developers.com/showthread.php?t=861950
It's basically the last resort before throwing in the towel and returning it.
rothnic said:
That isn't how you enter recovery.
v+ and power = recovery
v- and power =apx/nvflash
If you hold + and -, it goes into apx, hence the black screen.
Click to expand...
Click to collapse
I think I used to press both, initially. It might actually work that way, but using just vol down is easier.

Maybe I'm misunderstanding, but he said he can't get into recovery. Not apx. If you hold both, you can't get into recovery.

Ok i did the volume + and power and it is sitting on the detect recovery key pressed booting recovery image screen for about 4minutes now? Is that normal

stugots101 said:
Ok i did the volume + and power and it is sitting on the detect recovery key pressed booting recovery image screen for about 4minutes now? Is that normal
Click to expand...
Click to collapse
Ok, that's what it should say before it boots to recovery, but that is way too long.
Have you tried flashing clockwork with nvflash?

rothnic said:
Maybe I'm misunderstanding, but he said he can't get into recovery. Not apx. If you hold both, you can't get into recovery.
Click to expand...
Click to collapse
My bad, you are correct! I was so busy looking at APX mode that the answer was right in front of me. Yes, it sounds like he's just using the wrong key combo for recovery.
Here I am, looking at the most complicated solution. D-oh! EDIT: Uh oh, never mind....
stugots101 said:
Ok i did the volume + and power and it is sitting on the detect recovery key pressed booting recovery image screen for about 4minutes now? Is that normal
Click to expand...
Click to collapse
Yeah, that's way too long. Recovery might still be borked - should take 5-10 seconds.

I just did the nvlfash command and
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvfl
loader.bin --download 9 clockwork.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411884060c317
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: clockwork.img
\ 393216/3862528 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>
Still sits on the detect recovery key pressed screen

Well, it could be that your efforts to fix recovery might have broken recovery. I would go with my suggestion earlier, if you can't get the clockwork.img to work. Or, try part9.img (that's the original recovery image).

stugots101 said:
I just did the nvlfash command and
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvfl
loader.bin --download 9 clockwork.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411884060c317
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: clockwork.img
\ 393216/3862528 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>
Still sits on the detect recovery key pressed screen
Click to expand...
Click to collapse
Ok, yeah that means you are using the bootloader.bin from the nvidia folder. You need to use one of the gtablet ones. Try the bootloader.bin from the tnt update.zip.

im good now! it works. Rohbeet was right, i think i broke it, trying to fix it, but then uninstalled everything and started from scratch. Thanks for the excellent help!

stugots101 said:
im good now! it works. Rohbeet was right, i think i broke it, trying to fix it, but then uninstalled everything and started from scratch. Thanks for the excellent help!
Click to expand...
Click to collapse
It was broken because you used the wrong bootloader. That is why it says flash failed. Make sure you take note or next time you try to nvflash you will have the same trouble all over again.

For us poor uneducated folk out here.. which method got you up and running...
stugots101 said:
im good now! it works. Rohbeet was right, i think i broke it, trying to fix it, but then uninstalled everything and started from scratch. Thanks for the excellent help!
Click to expand...
Click to collapse

HELP! I Brick the Tab.

Hi, im from Argentina.
My problem is the next.
I was trying to flash the new Flashback Rom 10.3.
Mi Clockworkmod was old, (cause i didnt have many options like the advance features). So i tried to update the recovery using ROM MANAGER from the market.
I use the first option (install clockworkmod) and then the fist item (dont remember wich, the name was like Elysium or so).
Then the tab restar and didn power up again.
My pc cant recognise the device by any form. Its not in APX mod cause of it
C:\Users\PC\Desktop\Gadgets\Gtablet\Nvflash>"nvflash.exe" --bct gtablet.bct --se
tbct --bl bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
USB device not foundPress enter to continue:
Please any help of the advanced users. Thanks so much.

Problem solved. Had to Open te Gtab and use the Hard Reset button on the back.
My problem now is the CWM. I try to re install it. Put the update.zip and the recovery folder (copy and paste above the cracked recovery from Rom Manager).
When i try to Boot into recovery it freezes on Loading kernel Image.
What can i do now?

hawksneo said:
Problem solved. Had to Open te Gtab and use the Hard Reset button on the back.
My problem now is the CWM. I try to re install it. Put the update.zip and the recovery folder (copy and paste above the cracked recovery from Rom Manager).
When i try to Boot into recovery it freezes on Loading kernel Image.
What can i do now?
Click to expand...
Click to collapse
If you can get your tablet into APX mode for NVflashing you need to get the latest pack to update your CWM and stock rom to a 1.2 bootloader in order to update to Flashback.
http://forum.xda-developers.com/showthread.php?t=1118898
This will help guide you into switching from 1.1 to 1.2 bootloaders.

.....and for God's sake, whatEVER you do with any other Android device, DON'T use Rom Manager on the GTab. You'll soft brick it 9 out of 10 times you use it. It's a fairly well documented issue with this device. just my 2 cents....

I would have to agree that if you are now able to get into APX mode, the best thing you can do is to NVFlash back to a stock 1.1 or 1.2 bootloader (see the previously mentioned thread) and start over from the beginning. Know which ROM you intend to use before you choose an NVFlash path, so that you flash to the proper bootloader version for the ROM you want to use.

Help, Gtab won't boot
My G-tab will not boot. It will only go to the APX mode. I have been reading this site for the past three days and have tried everything that I can find but nothing works. I can load CW and complete all of the steps, I can even get the gtab to boot up when I nvflash it but as soon as I reboot the gtab it goes into the APX mode. I would appreciate any help with this.

dakota_ev said:
My G-tab will not boot. It will only go to the APX mode. I have been reading this site for the past three days and have tried everything that I can find but nothing works. I can load CW and complete all of the steps, I can even get the gtab to boot up when I nvflash it but as soon as I reboot the gtab it goes into the APX mode. I would appreciate any help with this.
Click to expand...
Click to collapse
Take a look at gtabletfordummies website. Start with code RED if you haven't already done exactly those steps. Use the NvFlash file from their site for your bootloader version with CWM already installed. If you have to use code DETOX and have problems after, you may need to search XDA again for "magic value mismatch error". (Sorry I can't post links so you will have to search!) Make sure you read everything and don't skip any steps.

Thanks for the reply but I have already went through all of the different sections of Gtablet for Dummies and my gtablet will still not boot past the APX mode.

Only other thing I can think of to try would be to remove the back cover of your tablet and hold (10 - 15 seconds) the internal reset button on the back of the board. That should factory reset it. Search this site (xda) for "gtablet hardware breakdown" for pictures and some info about taking it apart.

[SOLVED] Did a nvflash backup but bricked now, can't access APX. Help?

Update: SOLVED! See post #9
Hi... I ended up with a brick, unable to boot into anything at all, not even APX mode.
I followed the guide on the AndroidRoot.mobi website and made backup of all the files before that, though.
After finish with the guide, my device was working, but stuck in APX mode after every reboot and the only way to boot further (into fastboot or system) was to go through the command sequence
Code:
wheelie -r --blob blob.bin
nvflash -r --go
So then I started experimenting on my own... Firstly I tried
Code:
nvflash -r --download 6 boot.blob.LNX
Where boot.blob.LNX I extracted from boot.blob in the latest CM10 nightly.
After a restart, nothing changed, so I did this
Code:
wheelie -r --blob blob.bin
nvflash -r --download 4 bootloader.ebt # [B]bootloader.ebt[/B] is the file from the backup
nvflash -r --go # Did this while swiftly pressing PowerDown and went into Fastboot mode only to break everything with the next command
fastboot reboot
Since then I don't get any reaction whatsoever when I plug in my tab through USB. Tried both Linux (I completed the guide under Linux, btw) and Windows - they don't even recognise there is a usb device connected. Pressing/holding down on Power, Power+VolumeUp or etc. seems to have no effect. wheelie is stuck on
Waiting for device in APX mode...
Click to expand...
Click to collapse
Is there hope for me? Is there some other way to get to APX?

Is there hope for me? Is there some way to get to APX?[/QUOTE]
Have you asked in the NVFlash thread? " http://forum.xda-developers.com/showthread.php?t=1894867 " They don't provide a thread in general for support so I assume that is proper.
The site with the guide " http://androidroot.mobi/t3_nvflash/ "does not appear to offer support either. However there is this quote " ** Failure to make this back-up file will lead to support being withheld if you brick your device. You have been warned. ** ". So it seems they expect to provide support!
Good Luck!
I have JB bootloader so no NVFlash for me.

tobdaryl said:
Is there hope for me? Is there some way to get to APX?
Click to expand...
Click to collapse
Have you asked in the NVFlash thread? " http://forum.xda-developers.com/showthread.php?t=1894867 " They don't provide a thread in general for support so I assume that is proper.
The site with the guide " http://androidroot.mobi/t3_nvflash/ "does not appear to offer support either. However there is this quote " ** Failure to make this back-up file will lead to support being withheld if you brick your device. You have been warned. ** ". So it seems they expect to provide support!
Good Luck!
I have JB bootloader so no NVFlash for me.
Click to expand...
Click to collapse
Thank you for your answer. I did ask in the NVFlash thread a few weeks ago, got no answer. I've now commented on the website with the guide, hope I get some support there. In the meantime, if anyone has ideas, I'm willing to experiment!

I am sorry, I had hoped someone involved with the project would give proper advice.
I was already on JB when nvflash arrived.
I will invest more time on searching and reply when I find answers or give up the chase!
I have seen a thread with some info about how the OP unbricked but it was not the same issue as you have. The OP stated that he received no help and just started trying commands and got lucky.

xilunas said:
Thank you for your answer. I did ask in the NVFlash thread a few weeks ago, got no answer. I've now commented on the website with the guide, hope I get some support there. In the meantime, if anyone has ideas, I'm willing to experiment!
Click to expand...
Click to collapse
Time for some background info. I know I will be covering ground you have already covered but try to humor me!
It seems the only way into apx is when unit reboots!
Does your unit charge, when you power on is there at least indication unit tries to come on ( slight glow, etc. )?
In linux terminal without unit plugged into computer type ( lsusb ), now plug unit into computer power on and type ( lsusb ). Are the results returned identical? If they are not identical in linux terminal type ( adb devices ) then type ( fastboot devices ).
Reply with results.
Be careful with the info in the link posted below. It is hard on your battery plus as voltage drops current flow rises to compensate and the chances of electronic components being damaged rises as well.
If you have gotten beyond my above suggestions then next power on, hold volume up, and use small paper clip to press reset ( this is done while plugged into computer to catch apx on reboot. Reset is located on left side about one inch below the external sdcard.
There is one more but I'll reserve it as I had this one so we didn't get ahead of ourselves.
Last of all if you are at the end of your road and still no love, disconnect battery (here you could also run your battery down) while usb plugged onto computer. When you replug battery ( while holding volume + ) unit should reboot and get apx mode.
The following may be what you wish if you are trying to exit NVFlash - http://androidroot.mobi/t3_nvflash/.
WARNING: If you run the following command it will boot your device into regular android. This is listed as an *EXAMPLE*. Run the commands in “What Next?” section first.
From this point you will be able to use nvflash as normal by running commands such as the following to continue booting your device:-
$ nvflash --resume --go​

i read this thread http://forum.xda-developers.com/showthread.php?t=1478361
maybe it good for u.....just try and tell me what u get

I think that this fix won't work for your TF cause you must use "ODIN" which it's particular to Samsung.
Read this sentence:
From here on out everything is easy sailing. Get the right firmware and Odin and flash the firmware you require. It doesn't matter what region you are from, the tablet is made to accept any regional firmware BUT the model number should be the same. Which mean's 7500 for 7500 ONLY.
Click to expand...
Click to collapse

xilunas said:
Thank you for your answer. I did ask in the NVFlash thread a few weeks ago, got no answer. I've now commented on the website with the guide, hope I get some support there. In the meantime, if anyone has ideas, I'm willing to experiment!
Click to expand...
Click to collapse
I got bored and decided to read the NVFlash thread. I copied everything in that thread I thought I would like to know if I had NVFlash.
Here is a link that includes that info.
http://forum.xda-developers.com/showthread.php?p=33428304#post33428304
Good Luck!
I know it is not laid out very well but at least the info is there.:good:

tobdaryl said:
If you have gotten beyond my above suggestions then next power on, hold volume up, and use small paper clip to press reset ( this is done while plugged into computer to catch apx on reboot. Reset is located on left side about one inch below the external sdcard.
Click to expand...
Click to collapse
This worked! After pressing the reset button my TF300 was recognized in APX mode and from then I was able to restore it to a working state!
Thank you, tobdaryl!
BTW, to recover the tablet from APX I used ideas using an automated linux script TF201-nvFlashFactoryRecovery-Linux which can be found in another forum. It is intended for tf200 but some small modifications it worked great for my TF300:
replace the nvflash and wheelie given there (for TF200) with the ones you have (for TF300)
replace flash.cfg with the attached to this post flash.cfg (I modified it to reflect some different partition sizes on TF300)
use AndroidRoot-BlobTools to unblob a system image (I used a 4.0 image from the asus website)
in my case, I have to use the -r flag with wheelie each time for it to work:
Code:
sudo ./wheelie -r --blob blob.bin
follow the README
I'll be happy to assist anyone in my situation, just write here or PM.
Finally, I am still unable to power on the tablet without wheelie and nvflash --resume --go because it is stuck in APX by default. I think I will flash the new bootloader and see if this fixes it.

[Q] NVFlash help

I recently replaced the motherboard of my TF300T that I bricked a year ago, successfully installed Wheelie and NVFlash and went about getting my tablet back to being unlocked, rooted and installed with CM 11. Had a problem flashing one of the recent nightly updates to CM 11 and couldn't get my tablet booted back up to any ROM (even tried flashing stock and that didn't work). So, I went about to save my tablet with the NVFlash files that I had saved. I got Wheelie started and went through the first couple of NVFlash commands that I could find on this forum (http://forum.xda-developers.com/showthread.php?t=2590450). I did this through Windows 8.1, despite the fact that the person who wrote this forum post said to use Linux Mint (I do have Ubuntu as my second bootable OS on my laptop but felt more comfortable doing this in Windows). Everything was fine until the command "nvflash -r --go". My tablet now appears to be stuck in APX mode no matter what I try. I also cannot bootstrap with Wheelie in order to retry flashing with NVFlash. Can anyone help me figure out how to get this back up and running? Was under the impression that after using Wheelie and NVFlash to generate the blobs needed, the tablet was unbrickable. Thanks!

CaliTexan5 said:
I recently replaced the motherboard of my TF300T that I bricked a year ago, successfully installed Wheelie and NVFlash and went about getting my tablet back to being unlocked, rooted and installed with CM 11. Had a problem flashing one of the recent nightly updates to CM 11 and couldn't get my tablet booted back up to any ROM (even tried flashing stock and that didn't work). So, I went about to save my tablet with the NVFlash files that I had saved. I got Wheelie started and went through the first couple of NVFlash commands that I could find on this forum (http://forum.xda-developers.com/showthread.php?t=2590450). I did this through Windows 8.1, despite the fact that the person who wrote this forum post said to use Linux Mint (I do have Ubuntu as my second bootable OS on my laptop but felt more comfortable doing this in Windows). Everything was fine until the command "nvflash -r --go". My tablet now appears to be stuck in APX mode no matter what I try. I also cannot bootstrap with Wheelie in order to retry flashing with NVFlash. Can anyone help me figure out how to get this back up and running? Was under the impression that after using Wheelie and NVFlash to generate the blobs needed, the tablet was unbrickable. Thanks!
Click to expand...
Click to collapse
So when you power on and off your tablet it goes right to APX mode? The tablet doesn't restart when that command is run, it just ends the server loop for me.

cmendonc2 said:
So when you power on and off your tablet it goes right to APX mode? The tablet doesn't restart when that command is run, it just ends the server loop for me.
Click to expand...
Click to collapse
Yes, holding down the power button for any length of time just restarts it back into APX mode, even if I hold down the volume down button or even hit the reset button. I also am getting error 3 messages when I go and try the Wheelie command again, in the hopes of getting it bootstrapped back into NVFlash.

CaliTexan5 said:
Yes, holding down the power button for any length of time just restarts it back into APX mode, even if I hold down the volume down button or even hit the reset button. I also am getting error 3 messages when I go and try the Wheelie command again, in the hopes of getting it bootstrapped back into NVFlash.
Click to expand...
Click to collapse
Error 3 is a communication error. Do it on you linux (ubuntu) OS and see what it says.

cmendonc2 said:
Error 3 is a communication error. Do it on you linux (ubuntu) OS and see what it says.
Click to expand...
Click to collapse
I get the same error on Ubuntu also. I should tell you that I get that error once, then the next time I try to enter the Wheelie command, I get "unknown error or incorrect RCM protocol version, nverror:0x2". I've also tried the command "wheelie -r --blob blob.bin" and everything looks fine and I get "Sending BCT" but even after leaving it like that all night, it never goes any further.

CaliTexan5 said:
I get the same error on Ubuntu also. I should tell you that I get that error once, then the next time I try to enter the Wheelie command, I get "unknown error or incorrect RCM protocol version, nverror:0x2". I've also tried the command "wheelie -r --blob blob.bin" and everything looks fine and I get "Sending BCT" but even after leaving it like that all night, it never goes any further.
Click to expand...
Click to collapse
BCT is referring to the partition layout. Are the files recovery.bct and create.bct in your NvFlash folder?

cmendonc2 said:
BCT is referring to the partition layout. Are the files recovery.bct and create.bct in your NvFlash folder?
Click to expand...
Click to collapse
Here are the files that I have in both the Ubuntu and Windows folders:
blob.bin
blob.log
boot.blob
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
flash.cfg
nvflash
pt_patch.log
pt_restore.log
recovery.bct
unlock-token.img
wheelie
Is there a way that maybe we could instant message or something?

CaliTexan5 said:
Here are the files that I have in both the Ubuntu and Windows folders:
blob.bin
blob.log
boot.blob
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
flash.cfg
nvflash
pt_patch.log
pt_restore.log
recovery.bct
unlock-token.img
wheelie
Is there a way that maybe we could instant message or something?
Click to expand...
Click to collapse
Can you copy and paste the exact commands and outputs you had?

cmendonc2 said:
Can you copy and paste the exact commands and outputs you had?
Click to expand...
Click to collapse
I decided to give it a try on another computer that has Vista on it and got the same results. Took pictures of both the Wheelie attempts and what I get when I attempt to "nvflash -r --go" (my thinking behind this was because I did have NVFlash working at one point and thought that maybe doing this command would exit out of NVFlash).

CaliTexan5 said:
I decided to give it a try on another computer that has Vista on it and got the same results. Took pictures of both the Wheelie attempts and what I get when I attempt to "nvflash -r --go" (my thinking behind this was because I did have NVFlash working at one point and thought that maybe doing this command would exit out of NVFlash).
Click to expand...
Click to collapse
Hmmm. Do you have the Universal Naked Drivers installed and does it show up under APX device in Device manager anymore?

cmendonc2 said:
Hmmm. Do you have the Universal Naked Drivers installed and does it show up under APX device in Device manager anymore?
Click to expand...
Click to collapse
Yes, I did install using the universal naked drivers and it shows up on both computers as Asus transformer prime APX Interface.

CaliTexan5 said:
Yes, I did install using the universal naked drivers and it shows up on both computers as Asus transformer prime APX Interface.
Click to expand...
Click to collapse
I posted this a while back for you error, you may want to give it a try:
http://forum.xda-developers.com/showpost.php?p=48790941&postcount=6

cmendonc2 said:
I posted this a while back for you error, you may want to give it a try:
http://forum.xda-developers.com/showpost.php?p=48790941&postcount=6
Click to expand...
Click to collapse
I did try that second version of wheelie and it basically gave me the same errors. I didn't try the other drivers though. I did do a two day search through the forums here before I posted this, just to make sure the answer wasn't already out there.

CaliTexan5 said:
I did try that second version of wheelie and it basically gave me the same errors. I didn't try the other drivers though. I did do a two day search through the forums here before I posted this, just to make sure the answer wasn't already out there.
Click to expand...
Click to collapse
I forwarded the issue to Nvidia through the dev program as a bug report, but I doubt they will be able to help.

cmendonc2 said:
I forwarded the issue to Nvidia through the dev program as a bug report, but I doubt they will be able to help.
Click to expand...
Click to collapse
First of all, wanna say thank you so much for helping me out here! Totally forgot to tell you sooner.
Anyway, a bit of an update on my quest here. After letting things sit for a week or so, I decided to give things another try. Had a feeling that something was gonna be different tonight, and in a good way. On a hunch (being in Windows at the time), I decided to open up Device Manager and thought that if I typed the Wheelie command in first and only hit Enter when I saw the tablet show up in Device Manager, that maybe.....
I actually got the command to go through but then for some reason, around the time when it's gonna start sending the bootloader, my laptop loses the connection with the tablet and/or I get a Wheelie/Windows error that stops the command from continuing but doesn't close down the command prompt. So, something may still be possible here. I'm gonna try to do this in Ubuntu again but since there's no Device Manager in Linux (that I know of), I'm gonna be guessing at when the two are actually connected.
Anyway, thought you'd like to know and let me know if you have any ideas from here.
Thanks again!
-=BRAD=-

CaliTexan5 said:
I'm gonna try to do this in Ubuntu again but since there's no Device Manager in Linux (that I know of), I'm gonna be guessing at when the two are actually connected.
Click to expand...
Click to collapse
Try lsusb, a command-line tool that lists all USB devices.
Sent from my TF300T using Tapatalk

I tried that. I also tried gnome device manager and a couple of other things. After about two hours I decided it was not worth it. I'm back to trying on a Windows machine but so far so good

After much tenacity, a little hair-pulling and then a drink or two, I finally got Wheelie to initiate correctly and was able to use NVFlash to recover my tablet! Now that I know what I'm doing, it'll be easier getting my TF300TL fitted with a replacement motherboard and on it's way to a productive life again. Thank you again for your help and all!
-=BRAD=-

CaliTexan5 said:
After much tenacity, a little hair-pulling and then a drink or two, I finally got Wheelie to initiate correctly and was able to use NVFlash to recover my tablet! Now that I know what I'm doing, it'll be easier getting my TF300TL fitted with a replacement motherboard and on it's way to a productive life again. Thank you again for your help and all!
-=BRAD=-
Click to expand...
Click to collapse
Just curious, but how did how solve the error or did you do something different?

cmendonc2 said:
Just curious, but how did how solve the error or did you do something different?
Click to expand...
Click to collapse
It could have been the combination of being on a non-Windows 8 computer, using a new cord and downloading new copies of Wheelie and NVFLASH (though I'm thinking it was just the new software).