Database Info

[Q] Fastboot does not work

I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?

gaxiolafm said:
I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
Click to expand...
Click to collapse
It was saying the same for me too,but just go ahead and flash...it will work just fine.

Pretoriano80 said:
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Click to expand...
Click to collapse
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.

gaxiolafm said:
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
Click to expand...
Click to collapse
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.

Pretoriano80 said:
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Click to expand...
Click to collapse
I've tried everything in that thread. The command window still hangs at <waiting for device>
I downloaded drivers from 4 different places, still nothing. I just flashed the .30 update downloaded directly from Asus, and ran the Debugfs root method again, still nothing. At least now I don't have TWRP! I will just wait until there is another method for flashing CWM, since I'm not seeing any official ROMs I want to flash at the time, anyway.
Thanks for taking the time to reply.

I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.

Titanium318 said:
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Click to expand...
Click to collapse
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?

sbdags said:
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
Click to expand...
Click to collapse
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
Click to expand...
Click to collapse
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?

Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Click to expand...
Click to collapse
Rooting won't help here. You have unlocked it first right?

sbdags said:
Rooting won't help here. You have unlocked it first right?
Click to expand...
Click to collapse
Yes I unlocked it using the asus unlocker tool

Titanium318 said:
Yes I unlocked it using the asus unlocker tool
Click to expand...
Click to collapse
I tried a touch version and also a flashable zip both locked up my tablet the same as before. While my tablet is frozen after attempting to send the recovery I re-entered fastboot devices and it replied "????????????? fastboot" What does this mean?

Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..."
Click to expand...
Click to collapse
11.7 MB? Where did you get this recovery?

_that said:
11.7 MB? Where did you get this recovery?
Click to expand...
Click to collapse
This is where I downloaded CWM: http://d-h.st/YLd. So I switched and tried TWRP and it sent to my device and it did not freeze this time. It showed a blue loading bar at the bottom. I rebooted and opened RCK and TWRP opened successfully. I then Told my system to backup to my removable SD card. After it finished I tapped the reboot system button that came up. I opted not to root my device by installing superSU. I then downloaded Cromi-x to my tablet from here: http://forum.xda-developers.com/showthread.php?t=2425383 choosing the deodex option. Ithen followed the rest of the instructions and everything works great Thank you so much for your help!

Titanium318 said:
This is where I downloaded CWM: http://d-h.st/YLd.
Click to expand...
Click to collapse
Did you really expect a recovery for the Nexus 5 to run on the TF700?
Flashing stuff for different devices can just not work, as in your case, or it can turn your tablet into an expensive paperweight. Consider yourself lucky.

[Q] I seem to have soft-bricked my TF300. Ideas?

I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.

Guticb said:
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Click to expand...
Click to collapse
Try this link for access to recovery or apx.

No luck. The tablet literally doesn't have a recovery at all. Trying to flash any stock ROM through fastboot results in failure.
Every time I try, command prompt gives me the error FAILED (remote: (InvalidSize)) and my tablet does the "Failed to process command flash:system error(0xa)" message
I'm not sure if any flashes through fastboot are even working right. It says success, but the reboot command never works (Even though that says success, too)

Have you tried reflashing your recovery then installing a stock rom from there?

Guticb said:
No luck. The tablet literally doesn't have a recovery at all. Trying to flash any stock ROM through fastboot results in failure.
Every time I try, command prompt gives me the error FAILED (remote: (InvalidSize)) and my tablet does the "Failed to process command flash:system error(0xa)" message
I'm not sure if any flashes through fastboot are even working right. It says success, but the reboot command never works (Even though that says success, too)
Click to expand...
Click to collapse
No fastboot, no recovery, no apx backup
Sell it for parts
Lcd
Digitizer
Battery
Etc
Or buy a new mobo
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk

lightitwithfire said:
Have you tried reflashing your recovery then installing a stock rom from there?
Click to expand...
Click to collapse
Yeah. No luck. It'll say success, but the tablet freezes and the reboot command doesn't work. After I manually reboot, no luck either.

I've looked up some information about it. People who experience the same problem (not able to get into recovery, adb, etc) had to send their tablet into Asus and it got shipped to Czech Republic, then in about 3 weeks it's returned ready to go. Maybe that's a possible route? If not, search xda-developers deeper and check out transformerforums. They have alot of stuff linked to XDA so who knows, maybe what you're looking for is on there.
Best of luck to you!

Guticb said:
Yeah. No luck. It'll say success, but the tablet freezes and the reboot command doesn't work. After I manually reboot, no luck either.
Click to expand...
Click to collapse
Which recovery do you flash
Jb or ics version
Cwm or twrp
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk

dont waste more time
As i posted somewhere else, this tablet is a pretty bad purchase.
I bricked mine without unlocking bootloader, without flashing anything, without even connecting it to the computer.
One day it got stuck in asus screen.
After hard reset, recovery and wipe data i was left out with a brick. (no more snk, usb, wipe data screen)
Interesting you can brick a tablet without doing all those things they warn you not to do.
Dont waste more time looking for a solution. theres none, your tablet is now a useless brick.
sell it to someone who needs the parts.

gomezdf said:
As i posted somewhere else, this tablet is a pretty bad purchase.
I bricked mine without unlocking bootloader, without flashing anything, without even connecting it to the computer.
One day it got stuck in asus screen.
After hard reset, recovery and wipe data i was left out with a brick. (no more snk, usb, wipe data screen)
Interesting you can brick a tablet without doing all those things they warn you not to do.
Dont waste more time looking for a solution. theres none, your tablet is now a useless brick.
sell it to someone who needs the parts.
Click to expand...
Click to collapse
Wow, that's really weird. Hard to believe that it just bricked itself one day. Since it was never unlocked, did you take advantage of the warranty and say it was a manufacture defect?

Guticb said:
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Click to expand...
Click to collapse
I had the same issue although it stemmed from a different origin. I'm guessing it won't reboot on its own because you've wiped the /system files. Can you still connect to your PC using fastboot? If yes, try the command "fastboot -w", then try fastbooting the stock ICS blob file. By the way, I'm still new to the Android platform but I've learned quite a bit in the last few weeks by tinkering with my two Android devices and soft-bricking them several times in the process.
A

I had the same problem, and my understanding is that it stems from a messed up bootloader. Literally, I had the -exact- same error messages so I know what you are going through.
Fortunately, I was able to use NVFlash to recover mine. I don't know what other solution there would for you, my friend. Best of luck, let us know what ASUS charges for the repairs if you decide to go that route.

TF300T soft-bricked, please help!

Hi
I was trying to update from CM10 stable to the latest CM10.1 nightly. All went well until I got to reboot, when it got stuck on the "This device is unlocked / Asus logo" screen.
OK, I thought, I'll give this up as a bad job and restore my nandroid backup. But I got to the same point again, i.e. the stuck screen!
Now I'm starting to worry. I can boot into recovery OK, and also to the 3 icons menu. But I don't want to do anything else precipitous until I've got some good advice.
Thanks
Rob

If you can access fastboot, download stock Asus FW from their support site, extract it and flash blob into your system.

spenat said:
If you can access fastboot
Click to expand...
Click to collapse
I can get to "Starting Fastboot USB download protocol". PC recognises the device as "Asus Android Bootloader Interface" but nothing showing up with "fastboot devices" from a command box.

Well It worked for me plenty of times even when "fastboot devices" didn't showed up, so try just skipping this step. Also be sure to install Android SDK for drivers and official Asus drivers for it.
Also try different computers, fastboot just didn't worked on 4 computers I've tried, and the fifth worked even without installing drivers (both from Android SDK and official Asus drivers).

OK, thanks, that was a good tip to ignore fastboot devices. Was able to fastboot OK. But then...
I ran "fastboot -i 0x0B05 flash system blob", got an OKAY for sending but a failed for WRITING. Command box error was "FAILED <remote: <>", and the error message on the Asus was "Failed to process command flash:system error(0x170003)".

Well I don't know what's happened, but I thought I'd try and reflash my old CM10 ROM (which I'd fortunately left on the SD card) and this time it worked! No idea why it wouldn't work yesterday, but at least I now have a working device
Spenat, many thanks for your help.
Rob

You are welcome, glad to see another unbricked device

Nvidia Shield Tablet OEM Unlock

Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon

Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.

Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...

So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.

I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?

Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?

You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery

It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.

TF201 in TWRP bootloop/freeze brick

I was running version [ROM][N 7.1.2] [ KatKiss - Nougatella #027 ] by timduru on my TF201 for some time and today I decided to upgrade TWRP (from twrp-3.1.0-1-tf201t to twrp-3.2.3-0_KANG-tf201t).
I booted into TWRP, selected install twrp-3.2.3-0_KANG-tf201t into staging partition and then restarted.
After rebooting I ended up in TWRP bootloop.
As TF201 boots, skips fastboot and goes directly into TWRP splash screen then after several seconds without going into recovery it restarts again into TWRP splash screen.
That repeats several times until it freezes in TWRP splash screen. It never goes to recovery or boots into system anymore.
I tried to push Power and Volume Down together or Power button only it still keeps restarting into TWRP splash screen and rebooting. I tried different button combinations when I was in TWRP splash screen, Volume Down and Power restarted and I pushed immediately Volume Up, I got screen with error saying something about encryption error with the button reset. I tried to exit from there pushing Volume button but maybe I accidentally actually selected tablet reset?
During restarts or TWRP splash screen freeze I do not have access to recovery, fastboot or get any adb recognition on Windows (all drivers are installed).
My only possibility is to get into APX connected to my Windows.
Since I can still get it into APX and I have also created and stored my nvflash blobs backup long time ago should I start NvFlash recovery with generated blobs following this thread
Code:
[url]https://forum.xda-developers.com/showthread.php?t=2538028[/url]
or is there anything else I can try?
Any advice would be greatly appreciated.
Thank you all in advance!

Lucky that you have your nvflash blobs! Otherwise I would say it is a hard brick. Although why totally escapes me. A bad recovery flash should not brick it... I haven't heard of a 3.2 Kang version for the 201 though. Sure it is legit??
Anyway, no fastboot, no adb in recovery leaves you only the nvflash option. Good luck!
Post your steps if you don't mind, never saw anybody actually do a nvflash restore...
Sent from my Pixel 2 using Tapatalk

Download 'Minimal ADB and Fastboot' to a Windows 7 computer/laptop (found here): https://forum.xda-developers.com/showthread.php?t=2317790
Enter APX mode and plug your tablet into the computer/laptop and see if the TF201t shows up, fire up Minimal ADB and Fastboot and send the fastboot -i 0x0B05 reboot command to see if ADB is talking to the tablet.
Try this out, if you can flash the tablet from the PC you can wipe it and reinstall the recovery console, reboot and see if the tablet is saved. - NP
---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------
berndblb said:
Lucky that you have your nvflash blobs! Otherwise I would say it is a hard brick. Although why totally escapes me. A bad recovery flash should not brick it... I haven't heard of a 3.2 Kang version for the 201 though. Sure it is legit??
Anyway, no fastboot, no adb in recovery leaves you only the nvflash option. Good luck!
Post your steps if you don't mind, never saw anybody actually do a nvflash restore...
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
There a whole list of 'new' TWRP for the 201 here: https://androidfilehost.com/?w=files&flid=161771 any thoughts? - NP

georgecoat said:
Thank you very much for all your work and new upgrades.
I was running version 27 of this ROM successfully on my TF201 for some time and today decided to upgrade to version 34.
As a first step a decided to upgrade TWRP (from twrp-3.1.0-1-tf201t to twrp-3.2.3-0_KANG-tf201t).
I booted into TWRP, selected install twrp-3.2.3-0_KANG-tf201t into staging partition and then restart.
After rebooting I am in TWRP bootloop.
TF201 starts, goes directly into TWRP splash screen (showing the version of the recovery) then instead of going into TWRP it restarts again.
I tried to push power and Volume Down together or power only it does not react to anything, keeps restarting into TWRP splash screen and rebooting.
I would appreciate any suggestions.
Click to expand...
Click to collapse
For everybody with similar problem I am posting here how I fixed it.
I tried to push Power and Volume Down together or Power button only it does not react to anything, keeps restarting into TWRP splash screen and rebooting. When TF201 boots, skips fastboot and goes directly into TWRP but never loads TWRP and restarts or hang in TWRP splash screen.
In TWRP splash screen I do not have access to fastboot or do any adb.
I can still get it into APX and I have also created my nvflash backups long time ago and I have them available.
I was ready to start brick fix from the beggining.
But before I would get into that I tried last thing:
First I downloaded file djibe Transformer Prime pack v2 : http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
What i did first was that I had to restart Windows 10 64 bit into "Disable Driver control" othervise the driver would not install
Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Installed driver in extracted directory of "djibe Transformer Prime pack v2" pack (android_apxusb.inf).
Once driver installation is completed, reboot PC as usual.
Then I put all necessary files into nvflash folder.
Get ASUS into APX mode (Power and Volume Up, it will restart, hold it until creen is black)
I realised that old exe files are 32 bit, I had to use new nvflash exe files (from the package djibe Transformer Prime TF201 v2.zip) and replace rest with the files I had stored previously when I did blob backups. So everything I used was original folder but exe files replaced with 64-bit versions from the djibe Transformer Prime TF201 v2.zip package. In the last step I used original ASUS firmware downloaded long time go (also in the folder from the time of my blobs creation). This could be still found on ASUS page or here in the forum.
I started cmd window in nvflash folder and run this:
Code:
[B]wheelie --blob blob.bin[/B]
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d0787bc3ffa13
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Code:
[B]nvflash -r --download 5 twrp.blob[/B]
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
/ 8124520/8124520 bytes sent
twrp.blob sent successfully
After that I was able to get into fastboot finally!
From there I did:
Code:
[B]fastboot -i 0x0b05 flash recovery twrp_tf201t.blob[/B]
sending 'recovery' (7934 KB)...
OKAY [ 2.110s]
writing 'recovery'...
OKAY [ 2.128s]
finished. total time: 4.238s
Code:
[B]fastboot -i 0x0b05 reboot-bootloader[/B]
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.643s
Still no working...
I had to do this:
Code:
[B]fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache[/B]
Code:
[B]fastboot -i 0x0B05 flash system L:blob[/B]
(this was my path - your's may vary depending where you stored your blob)
Code:
[B]fastboot -i 0x0B05 reboot[/B]
Then I started the whole process of flashing the Hairybean bootloader (reboot), then TWRP (reboot) and then the rom 35, gapps, supersu again and I am back to normal.
Thanks : Timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber, berndblb, Nektopoli, djibe and Buster!

Hey guys... so... I am really desperate here. I tried updating my tf201 to nougat following the guide here on the forum but somewhere along the way things went terribly wrong and now the tablet is stuck in the aforementioned bootloop/freeze. I cannot get into fastboot. I can only get into ATX. I DO have my nvflash backup blobs, but even so I am unable to get the tablet from this state. I have tried like 4 different guides and approaches (including the one here, of course), but unfortunately nothing seems to work. I can't get fastboot.
Any ideas?
Things I've tried:
https://forum.xda-developers.com/t/nvflash-recovery-with-generated-blobs-tf-700-t.2538028/
commands like: nvflash -r --rawdevicewrite 0 2944 bricksafe.img (I find it strange that the command runs slowly for the first half of the upload and then it speeds up a lot... but that might be okay, I dunno)
Tried flashing back the original firmware / blob downloaded from asus.com etc. Nothingseems to work.
Please, any help will be greatly appreciated.
EDIT:
Ok. So after a good night's sleep I'm feeling a little less desperate and I can describe in more detail how I managed to get to this proper bricked state.
1) I followed https://forum.xda-developers.com/t/...me-tf201-stock-to-android-7-1-nougat.3486237/ this guide and got all the way to Step 6 (bootloader) at which my tablet started to behave a bit differently than what was described in the guide. It is also important to note, that the tablet display is a little bit damaged - just the first two lines of the display - but unfortunately, that makes reading important info, such as whether or not the device is unlocked, bootloader version etc., impossible.
2) Anyways... Halfway through step 6, just after:
Code:
The tab reboots and launches the HairyBean TWRP recovery (androwook).
My tab loaded back into android instead. So here I thought - with all my stupidity's might - "hmmm, so maybe I didn't unlock it properly" (keep in mind that due to the damaged display, I couldn't check),, and I went ahead and ran the unlock app again. That lead to the Tab's restart and here we are. When I turn on the tablet, it just shows the Asus logo for like half a second and then restarts. Shows the Asus logo again and restarts. And that way forever. Pressing power + volume- does nothing. The only thing that works is power + volume+ which starts ATX and I am able to interact with it using wheelie and nvflash.
3) At this point, I can't remember the exact order of things that I tried, but things I tried are:
Load back my nvflash blobs. I still have those. I followed this guide: https://forum.xda-developers.com/t/nvflash-recovery-with-generated-blobs-tf-700-t.2538028/
Load back stock ASUS firmware downloaded from asus.com
The steps in this thread as described by georgecoat.
At one point I think I tried following this guide: https://forum.xda-developers.com/t/...rick-recover-downgrade-upgrade-tf201.1927818/ and that I'm afraid might have been the proverbial nail in the coffin. So... you see, my nvflash files didn't match the ones described in that thread. SoI thought "hmmm, I have bootloader.ebt, so that's probably the same as his blob.EBT" so I executed
Code:
nvflash.exe -r --download 4 bootloader.EBT
And that I think got me to where I am now... It's cool how sometimes I can amaze myself with my own stupidity... and the worst part is that I'm an IT guy, I work with linux, docker, python a lot.... but android is a complete unknown for me and as I got more and more desperate I tried stupider and stupider things. Oh well...
So... any ideas? Anything goes, really. At this point I might as well use the tablet as a paperweight so really, any ideas are welcome.
Thanks in advance.