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?

[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.

Help pls!!!! 20$ in it!!!

New that would get attention. Is there anyone out there that is dedicated to helping for a lil cabbage? I have this tf101 transformer that i cant seem to get rooted. Why is it so gosh dern hard to root one? I have followed all methods and tryed diff methods. The emulator runs but root is still not acheived. I have not bricked it. Its running ics. Ive rooted phones and tablets since the evo 4g..... this garbage a$$ tablet is without a doubt one of the worst i have ever had the displeasure of owning. Nexus 7,,,samsung note 1,,,note 2,,,,,,note 10.1,,,,,htc first,,,,evo 4g,,,,blackberry tour....AND NONE HAVE EVER BEEN THIS HARD TO ROOT. I wont buy another asus anything.
So,if som1 could explain what im doing wrong thatwould be great...also 20 buck in the paypal acct.....if you can think of it. Ive done it. Next is taking it apart to see what makes it tick

First thing - Does your tablet get seen by your PC in either APX or ADB mode? And did you update the driver using the Naked Drivers?
Last time I rooted I used Wolf's Method 3. Here is what I did:
Plugged in my tablet to my PC via USB (win 7 PC).
After the device was detected, I went to Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://forum.xda-developers.com/showthread.php?t=1998650
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Next, run the following commands (from Wolf's Exploit, Method 3)
Code:
adb push TWRP.blob /sdcard/
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
adb reboot
exit
It will reboot. Once you see the ASUS loading screen, you can continue:
Code:
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)
Now you can install your favorite SuperUser app.
Download a zip flashable SuperUser
ChainsDD SuperUser: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
ClockWorkMod SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Chainfire SuperSU: http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
I like the CWM SuperUser at the moment, but all three will work.
Put these where you can see them from the recovery you flashed. If using TWRP, it needs to be in the /sdcard/ directory or on the microSD card.
Next, reboot to recovery. Hold VOL DOWN and POWER for 12-15 seconds until you see some white text in the upper left of the screen. Release both buttons and tap VOL UP to enter RCK (Recovery).
Once in recovery, tap Install and choose the SuperUser.zip file to install. Once installed, you are rooted.
Another time I rooted, I used EasyFlasher and here is the thread on my rooting guide for that if you are interested: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once again, if you cannot get your tablet detected by ADB or APX, chances are it is a bad USB cable.

harley1rocker said:
-snip-
Click to expand...
Click to collapse
If you've 'tried everything', then it's likely Bad drivers or a bad USB cable, I'll assume you've tried my tool, the idcrisis tool, Easyflasher and wolf's method (Described by Fred) above.
If you'd like me to remote desktop you with Teamviewer to make sure your drivers are good I can do that, but if you've really tried everything then it's likely a bad cable.
ToD

To test the cable, simply transfer a file through USB with a known md5 signature, then verify it again after it's been transferred. You can use something like AFV to check the md5 once on the device. The bigger the file the better; the more chances it has to fail.

I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS

harley1rocker said:
I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS
Click to expand...
Click to collapse
Glad you got it sorted.

who got the 20 dollars
Sent from my Transformer TF101 using xda premium

stesteste said:
who got the 20 dollars
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Wasn't me. But I did not respond for the $20, I am just a good guy.

No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.

harley1rocker said:
No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.
Click to expand...
Click to collapse
We're all here to help, it really isn't about $, for me really it's just seeing that someone cares to donate that makes my day.. It's all about the passion of android though As fred will probably tell you.

[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).

Only APX mode and nothing else

Hi everybody! I have a trouble: it tries to load TWRP a few seconds, then reboot and the same... Only APX mode is available and nothing else. Is there any ways to resurrect it?

If you can boot to fastboot, yes - you can save it. If not, you will need a new mainboard.
Let us know and we take it from there

berndblb said:
If you can boot to fastboot, yes - you can save it. If not, you will need a new mainboard.
Let us know and we take it from there
Click to expand...
Click to collapse
I was tring to bring my TF700 to life through NvFlash.. Durnig downloading recovery.img, after 100%, my tablet started vibrating eternally and even time when I tape wheelie --blob blob.bin in SDK

You wrote that somewhere else and I don't understand it. You have your device specific nvflash blobs?? If you cannot get into fastboot, nvflash indeed would be your last chance BUT ONLY IF you generated your blobs when the tablet was still functioning. Did you?

berndblb said:
You wrote that somewhere else and I don't understand it. You have your device specific nvflash blobs?? If you cannot get into fastboot, nvflash indeed would be your last chance BUT ONLY IF you generated your blobs when the tablet was still functioning. Did you?
Click to expand...
Click to collapse
Yes, I have generated my specific blobs before.. But something error has happened when I tried to revive tablet using them yesterday (it is described in previous post)

However, it starts vibrating now, when I enter command "wheelie --blob blob.bin"
http://i12.pixs.ru/storage/5/0/0/SnimokPNG_1957953_25143500.png

Prizrak_M said:
However, it starts vibrating now, when I enter command "wheelie --blob blob.bin"
http://i12.pixs.ru/storage/5/0/0/SnimokPNG_1957953_25143500.png
Click to expand...
Click to collapse
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basicly the same.
https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessarry .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)

Unidave199 said:
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basicly the same.
https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessarry .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
Click to expand...
Click to collapse
Thanks, but I've already sold it by parts..:angel: