Database Users

My tf101 is bricked !! Please help!!

My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks

! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?

baseballfanz said:
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
Click to expand...
Click to collapse
i tried cold boot , but it said cold booting up linux .. but no response
i tried wipe device , but it still freeze on ASUA screen too
yesterday, i try to root and install CWM via Prime V4.5
then the device comes this .....
Thanks ...

Never heard of that root utility before. You may not have used the right rooting utility for your device which can cause a brick situation. Also, are u sure u dont have the tf 101 and not thr tf prime? The vipermod utility found in the tf prime forum will root ics for both the 101 and prime. My suggestion is that u make sure u have the right device and search the right forum for brick recovery, unroot, or return to stock threads. They are usually found in the development sections.
Sent from my SGH-I777 using XDA

viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.

cholywell said:
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
Click to expand...
Click to collapse
i had an issue that was caused by lack of sleep last night that i might be able to help this guy out.he never used it to flash CWM.. he rooted it and never flashed from within the CWM app. The stock recovery doesn't have options for choosing files ect..

victor1144 said:
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
Click to expand...
Click to collapse
I might be able to help you... I saw your post around 4am. I had the same problem kinda. Was asleep most the day (got done at 6am).
I rooted with viperMod PrimeTime and it worked !
BUT i forgot to FLASH CWM RECOVERY from inside the app and proceeded to install the new ROM after root was made USING the CWM app. What happened in my case , the CWM app restarted trying to flash the new ROM, WITHOUT CWM being my recovery instead rebooted to STOCK recovery and something glitched up. I had the same thing as you stuck on Eee pad never re-starting. Cold boot wouldn't work or full wipe..In my case something conflicted.
Below is the NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build). You need to re-flash again using APX threw your USB connected to a PC (it self installs) :
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
the links are in Grey btw and says US version, ect ..read everything but its very straight forward... ill explain what i did toward the end of the post to simplify it since it took awhile to figure it out. Ill add side comments threw the process that explains better than the link.
Attention: These tools are designed to bring your device back to working condition. They are great for getting back to stock if you need to send your device in for repair or you need to downgrade to stock in order to root your device, etc.
Instructions for Windows users:
1. download the file from the original link i gave above. NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build) USWindows
2. unpack zip to desktop.
3. Press Volume up and Power at the same time on your Transformer to enter APX mode, connect to pc (hold for about 7 seconds). Basically, Power off.. THAN, power and Volume up at the same time to enter APX mode. IMPORTANT!! the screen remains BLACK like its frozen ,with no writing or indication something is happening. that's normal and the original poster in the link never mentioned it. That is APX mode..
4. drivers for APX are in there if you need them..inside the windows downloaded file its called NVFLASH towards the bottom
On your PC go Device manager.. if APX is working correctly and the Transformer is in APX mode it will appear as an exclamation on the device manager named APX.. you cant miss it.. it stands out. On my Windows 7 PC it changed and said Asus USB (or something like that)
5. double click Run Download.bat file and let run! everything is prepackaged so no copying files, etc. In the same file you downloaded that you unzipped named Windows its the 4th file that says "download" with a gear looking icons.
Your Transformer (based on what happened with mine) will go threw a self install like its pushing files and flashing it..the black screen looks like its being pushed the files and reflashing without a recovery. Your going back to stock. if you dont see anything on your Transformer screen after running/double clicking the Download.bat file ....Right click on APX in the device manager , properties, Drivers, update Firmware, choose manual install and find the Downloaded.bat file and click it. That should do the trick..I did both and only noticed the Transformer lighting up after manually pushing it threw APX.
6. After the device reboots power it off. Then hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
7. Download the latest update from the Asus website if applicable and follow the manual instructions. This step may not be necessary if your OTA update worked or my nvflash is the latest version. US update on there site is 9.2.1.17.Its the only one...
What i did was go back to stock since i didn't see any interesting ROMS..Point is THAT unbricked my device by flashing it in APX mode when it was connected to the PC.
I did use ViperMod again to Root, but used the Clockwork mod app in my Transformer to FLASH CWM RECOVERY to try a few ROMS out.
After trying a few of them out i choose to revert everything to stock, unrooted and reflashed STOCK recovery.
Hopefully that helps you out.. it did work for me...

Thank you so much it worked great

Lantek23 said:
Thank you so much it worked great
Click to expand...
Click to collapse
Glad i could help

Sorry to dig up slightly old threads, but I have a question for you. I have a TF101 that I was trying to update to ICS. It is currently running 3.2 courtesy of the unbricking tool listed in this thread. I had to unstore it as it was bricked from a bad install. That was many moons ago. It won't show an updaate listed, so I decided to go with the manual route. I downloaded the appropriate update (my device lists WW version) loaded it on an SD card had the install prompt come up and rebooted to install... For a split second it shows the android with the gears like it is installing the update and then shows the android with a triangle and exclamation mark. After that, nothing. I have to reboot to get it off that screen. Upon booting, I get a message saying system update failed (2) unknown error. Any ideas?

If Im not mistaken, the zip file you download (I guess from asus?) contains another zip.
Thats the zip you should place on your SD card, did you do that?

Also try renaming that zip to EP101_SDUPDATE.zip (the one extracted)

I already had the zip extracted, and renaming didn't do anything.

Killa357 said:
I already had the zip extracted, and renaming didn't do anything.
Click to expand...
Click to collapse
Are you rooted? Did you remove any system apps?
Another thing to try is on your micro sd card, make a folder name ASUS and inside that folder another folder call Update, inside the Update folder put the extracted zip file (don't rename). Turn off TF and turn it back on, see if it will detect the update file.
If that fail, you did mentioned you use the unbricking tool, use that NVFlash to flash a compatible ICS ROM

It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...

Killa357 said:
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Click to expand...
Click to collapse
You don't need to be root to use NVFlash.

Just when with a slightly older version of the update and it worked. There may be something wrong with the file Asus has hosted.

Hi
I have a slightly different problem. I have rooted my B60 serial number, it has the ICS from ASUS on it and it boots fine, its rooted and it works. Now the problem is I thought lets try a clockwork mod and play with custom roms.
So I set my win 7 up to adb etc, and pressed power button volume button - and off to recovery I went...
but all I got was a little green android on its back chest open and an exclamtion mark. No adb fastboot devices command.
I seem not to have a recovery nor a way of forcing a custom recovery.
Should I NV flash or just be happy the tab works and leave well alone?
Any other answers since a lack of recovery may come back to haunt me sooner or later.
I also tried the power button vol uyp for 7 secs and nothing happens I can get to the cold boot erase data option on power down, don't want to do that yet since Im not sure what data gets erased and I may have a totally non working tab.

Use RecoveryInstaller to install cwm recovery

Use RecoveryInstaller to install cwm recovery
This is my problem I can't get recovery - nor can I get adb to see the device. It shows as a hard drive/storage device but not in adb.

I messed up my N7 but recovered - how to check if Nand Flash is still good?

Hey guys,
Last night, I unlocked, rooted (with perm cust recovery - TWRP) my N7 which was successful.
I installed custom ROMS and it was really doing great, until I made a mistake.
In TWRP, I accidentally formatted SYSTEM without having a ROM zip file to flash in the internal storage (/sdcard).
I restarted and it was just sitting in the google splashscreen (with unlock icon) - no matter how to I try to reboot it it was just going stuck there. I manged to make it boot to TWRP (press volume keys + power) again and tried to PUSH a rom using adb command line.
When I pushed a ROM file (Cookie's and Cream 1.0) as soon as I pressed enter, it looks like it is doing the push. But I've been waiting for 45 mins and it was still on the same progress, so I had to unplug it while it was doing that in the command line.
When I restarted, I tried to go to TWRP again but I can't anymore no matter what I do. So I had no choice but to reboot to bootloader instead.
This time I used the tools (nexus toolkit 1.5.3 (GUI) and the other version (2.0) in XDA - command line looking).
On both instances on both tools, when it is pushing - it just gets stuck with a blinkng cursor and it does not continue to the next step. As if the file is not being pushed.
There was also a point that when I go to recovery (i think it was stock), the android picture had a red triangle with exclamation point.
Anyway, I managed to make it work by manually by doing the guide [GUIDE] Flashing a Factory Image with fastboot / return to stock
Again, when i was doing it, when it is sending the image file to the N7 it was just stuck with a flashing cursor. I waited for 30 mins and when I rebooted, it WORKED - booted to N7 screen etc .. all good.
But I was worried why about that pushing error - maybe my Nand flash got borked like bad sectors etc? Is there a way for me to check if my flash storage is still good?
TL;DR
I messed up flashing a custom ROM on my N7 and accidentally formatted system. I managed to recover using recover to stock using fastboot and it worked.
Now, when I'm pushing files and it is big, it just gets stuck, either in recovery or when it is booted up.
Is there a way for me to check if I made badsectors or borked my internal flash storage?
So far everything looks fine but I just want to make sure since I still have 20 days to return it.
Thanks!
EDIT: When pushing from Recovery it says "error: protocol fault (no status)"

keplenk said:
Hey guys,
Last night, I unlocked, rooted (with perm cust recovery - TWRP) my N7 which was successful.
I installed custom ROMS and it was really doing great, until I made a mistake.
In TWRP, I accidentally formatted SYSTEM without having a ROM zip file to flash in the internal storage (/sdcard).
I restarted and it was just sitting in the google splashscreen (with unlock icon) - no matter how to I try to reboot it it was just going stuck there. I manged to make it boot to TWRP (press volume keys + power) again and tried to PUSH a rom using adb command line.
When I pushed a ROM file (Cookie's and Cream 1.0) as soon as I pressed enter, it looks like it is doing the push. But I've been waiting for 45 mins and it was still on the same progress, so I had to unplug it while it was doing that in the command line.
When I restarted, I tried to go to TWRP again but I can't anymore no matter what I do. So I had no choice but to reboot to bootloader instead.
This time I used the tools (nexus toolkit 1.5.3 (GUI) and the other version (2.0) in XDA - command line looking).
On both instances on both tools, when it is pushing - it just gets stuck with a blinkng cursor and it does not continue to the next step. As if the file is not being pushed.
There was also a point that when I go to recovery (i think it was stock), the android picture had a red triangle with exclamation point.
Anyway, I managed to make it work by manually by doing the guide [GUIDE] Flashing a Factory Image with fastboot / return to stock
Again, when i was doing it, when it is sending the image file to the N7 it was just stuck with a flashing cursor. I waited for 30 mins and when I rebooted, it WORKED - booted to N7 screen etc .. all good.
But I was worried why about that pushing error - maybe my Nand flash got borked like bad sectors etc? Is there a way for me to check if my flash storage is still good?
TL;DR
I messed up flashing a custom ROM on my N7 and accidentally formatted system. I managed to recover using recover to stock using fastboot and it worked.
Now, when I'm pushing files and it is big, it just gets stuck, either in recovery or when it is booted up.
Is there a way for me to check if I made badsectors or borked my internal flash storage?
So far everything looks fine but I just want to make sure since I still have 20 days to return it.
Thanks!
EDIT: When pushing from Recovery it says "error: protocol fault (no status)"
Click to expand...
Click to collapse
My computer did that in windows, but switching to Linux and it all worked fine for me
Sent from my Nexus 7 using xda premium

lbbooga said:
My computer did that in windows, but switching to Linux and it all worked fine for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. Good thing I still have my Arch Linux box still up and running.
So is this a known issue?
Right now, I did it again and it worked.
It is like 80% chance it will get stuck while pushing thru adb and 20% it will just work successfully.
Just right now, I just did restore it using the tools. I didn't work for at least 5 times. The 6th time it worked. (Windows 64 bit)
I'm going to try linux and see if it will be better.

UPDATE:
It looks like it could be adb drivers in Windows.
OS X works fine. I haven't tried with Linux.
But is there a software to check if Flash storage has bad blocks?
Thanks!

[ TF300T ] How to unbrick when wrong recovery menu was flashed.

This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.:good:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link ---> http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 because that's the guy that wrote this procedure from above (credits to him) :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This part was me now -ozkrtech <--- (credits to me)
In addition to that, if you simply can't see your device using the command "adb devices" go check on device manager if you see a device called just "Transformer" with a yellow icon indicating it needs a driver, and manually update driver, select "browse my computer for drivers" and then select let me pick from a list of device drivers on my computer" there you will see a list of like 3 different drivers, one of them says "bootloader" and one of the others says "adb" (i think they self explain) but just in case try with each one of them you can keep on switching drivers until you get your device recognized by the command "adb devices".
You should be asking yourself... whats the right moment to do an "adb devices" command? well my tablet same as -Buster's tablet had the wrong recovery menu flashed (wrong bootloader version) and it just kept booting into the corrupted recovery (in my case TWRP) with the "can't mount anything" and "what's the password" issue. When you get to password screen just hit cancel and try the "adb devices" commando and you'll see it gets recognized with your device serial number.
Once your device gets recognized by "adb devices" command you will proceed to use "adb reboot-bootloader" command and the tablet will reboot into the menu that had 4 options but now have 3 options and its missing the fastboot option (don't panic) in the last bootloader it is auto-fastboot mode when you reach that screen with just 3 options in it now (yeah is the screen with the RCK option) at this point try "fastboot devices" command to see if your device gets recognized same as "adb devices" procedure, it should get recognized with a different serial number (don't know why, maybe that number isn't a serial number), at this time you are SO LUCKY! now you will follow what I posted at the beginning from that other dude ---> (-Buster) or follow his link --- > http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
And you'll have an unbricked tf300t in no time =) (I personally used the stock but newest Asus ROM) 4.2.1 (10.6.1.27.1) and it worked flawlessly.
**NOTE** don't turn off nor reset your device once you have formatted the partitions, no need for that (don't know what happends but it might get really hard bricked) just proceed to flash the stock rom after erasing the partitions.
I'm 100% positive this will work if your device is in same state as ours. (had TWRP for JB) then updated bootloader to version 4.2 and forgot to update twrp to version 4.2 or installed twrp version JB by mistake and lost fastboot and TWRP is asking password.
Hope it helps. Let me know your status and if it worked for you.

So I am in the same boat as I flashed the wrong twrp. My device shows up under adb devices and I can boot into the bootloader using adb reboot-bootloader. However, once there, I can not get the device recognized with fastboot. I have tried messing with the drivers like you suggested but nothing will get it to show up with fastboot. Anybody have advice on where to go from here?
So extra info. The device bootloops into twrp 2.6. The only way I can boot into fastboot mode is with adb reboot-bootloader and I can get into APX. I can also boot directly into my current ROM (Slim beta 3) by selecting android in the bootloader menu. I have tried flashing proper recovery through flashify, which is says was successful, but the wrong twrp never gets overwritten. Rebooting the device will send it back to twrp.
Thanks if anyone can help

Thanks, man! It took a while to find this thread, but this was exactly my problem. The adb driver in windows was the pre-solution to help get back to the fastboot server in the bootloader. Awesome information. Thanks again!

I have tried "adb reboot-bootloader" and then adb devices and fastboot devices and neither will show the tab listed while the tab reaches that screen with just 3 options. I have uninstalled reinstalled drivers, it does show in device manager as Asus Android Composite ADB Interface but when running the command it will not list the tablet. Any suggestions?

Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Remember please I cannot go in fastboot recovery menu, only apx. Thank you in advance!

I can not thank you enough!!! my tablet is now working I honestly though it was done for aha THANK YOU!!!

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following the OP's guide I was successfully able to reflash stock firmware and the device runs fine now.
However, upon reflashing said firmware, it became apparent to me (from reading various threads in the development subforum), that I would need to downgrade to an older firmware version to reflash TWRP. So I did that successfully, but now I am having a problem similar, or perhaps identical, to that of Bionicbowtieguy, in that ADB appears to be broken for my tablet. I have tried uninstalling and reinstalling the Asus usb drivers, in addition to reinstalling/updating all of the ADB software. Fastboot still works fine, but as such I'm unable to root using Motochop's rooting kit (I know there are other methods out there), nor am I able to flash a new recovery. I have also tried repeatedly reflashing the older stock in the hopes that ADB would magically start working again to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.

Kombatant said:
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Click to expand...
Click to collapse
Same here!
Thank you OP for making this a topic even if you didn't come up with it you made it a thread that has saved a few people like myself money and headaches. Literally I just stumbled on this thread 10 minutes after I told my wife is be Tablet shipping Black Friday. Thank you sir.

Thank you.
I did this on a hackintosh running OSX since on Win 8.1 fastboot kept crashing.
March of this year I bricked my tablet during that 1 week period where nobody knew that TWRP was broken + fastboot freezing.
I must have tried everything, Maybe that erase misc was the key factor for success.
I was about to sell this for what I could get or send it to asus, now I can use it again!

How are you guys getting your tablet into fastboot mode? I've tried power on with volume down, the reset hole with volume down, and letting the battery die then recharge, then power on with volume down... Nothing. What am I doing wrong?
Sent from my Galaxy Nexus using Tapatalk

Best thread ever!! You are a life saver !!! thank you!!

leris2 said:
Best thread ever!! You are a life saver !!! thank you!!
Click to expand...
Click to collapse
Indeed. You are a god among men. Thank you so much

This worked! I thought I was out of luck. Thanks a lot.
I accidentally flashed an incomparable version of twrp. It would only boot straight into recovery and I couldn't get into recovery. TWRP kept asking for a password even though I never set one up and it wouldn't mount the internal storage or sd card.
I had to follow the instructions at the bottom to intall the drivers so adb and fastboot to work. After that I followed the instructions at the top.
The only thing different I did was skip the "fastboot erase boot" step. I was afraid that would really brick my device if I screwed up (Does this really erase the bootaloader leaving the device with no bootloader?).

Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers

Fastboot
Bolandk said:
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Click to expand...
Click to collapse
They do not sit at all they will go right to it. You must not have the right combination yet. Keep trying.
Took me awhile to get the link.
norm883

FIXED!
BY GOD, I have no words for how incredible grateful I am right now! You not only saved my TF300T's life but also a lot of money for me and gave me another lesson of Android insight.
Thanks so much for this!
Let me know if I can return the favor somehow!
Regards,
(a very happy) philleicht

Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan

same problem reboot back to twrp
well i may be stupid because i can't understand why i have tried a couple of commands and i still get the same problem reset volume down still goes back to twrp and ask for a password can someone please explain this in alittle more detail and what commands i also get the waiting for device in my commands is there another way to push these files into this device tf201 please help is there a way to do something in the twrp recovery like terminal command

I was a fool for flashing wrong recovery!
DrPhant0m said:
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
Click to expand...
Click to collapse
I have exactly this! I hope someone knows the answer for this issue. Else the tablet will learn how to fly!
I tried to push the reset button as described earlier but nothing changes. Not able to go into recovery Just stuck at ASUS in the middle NVidia in the bottomright corner en upperleft corner 'this device is unlocked'

[SOLVED] OTA update failed and now tablet is soft bricked

I have a rooted Nexus 10. I recently received a popup that an update was ready to install (4.4.2). Somewhere during the install process it crashed. I can't remember exactly what it said but something about e:\ and invalid files. Now when I boot the tablet it loads the Google logo and then it displays the 4 color ball animation until the battery dies. I don't mind wiping everything so I downloaded the 4.4.2 rom from google and figured I could wipe and flash a fresh copy. The problem is I can't get ODIN to see my tablet. I plug in the USB and I hear the normal chirp that windows has found new hardware and it installs some strange driver (SAMSUNG CDC?) but ODIN never loads a com port.
Any thoughts on what's wrong, or other ways to try to fix the tablet?
Thanks.

I'm afraid I don't know much about ODIN....but:
I think there's hope yet! First things first, download the (dl.google.com/android/installer_r22.3-windows.exe) Android SDK Tools and install them - you'll need at least the Tools and the USB drivers.
Once those are installed, launch a command prompt (windows key + r on the keyboard, type in cmd and preess enter). Use cd and the tab key to get to the directory where you installed the SDK tools (e.g. cd "Documents\SDK Tools\platform-tools").
Now, on your Nexus 10, go into recovery by pressing the power button, volume up, and volume down buttons at the same time until you see a little Android with a red exclamation mark (I believe). Then, to show the menu hold the power button and volume up. Choose "Apply update from ADB"
Back on the computer, on the command prompt, type "adb sideload C:\Users\Where\You\Downloaded\The\Rom" without the quotes. It should transfer the rom to the nexus 10 and reflash it.
Please, let me know if you have any questions, I'm happy to help!

Have you tried doing a factory reset/ cache wipe in the recovery? (hold vol up+down and power from tablet off , then select Recovery Mode in fastboot)
You flash the factory image in fastboot NOT Odin .. you dont flash anything in Odin for Nexus you do everything thru the bootloader/fastboot

bjschafer said:
Back on the computer, on the command prompt, type "adb sideload C:\Users\Where\You\Downloaded\The\Rom" without the quotes. It should transfer the rom to the nexus 10 and reflash it.
Click to expand...
Click to collapse
First off tried just doing a wipe/factory reset and that didn't solve it (but thanks for the suggestion NewMagnus).
I was able to get into recovery and sideload the rom over. After it copied this is what came up on the Recovery (which by the way appears to be ClockWorkMod 6.0.1.6, which I don't actually remember installing but oh well):
Restarting adbd...
Finding update package...
Opening update package...
E:Can't open .temp/update.zip
(bad)
Installation aborted.
So, small progress but still no joy.

And an update...
I ran the Nexus Root Toolkit again but restarted the bootloader first. This time it somehow found FASTBOOT and installed the image no problem. I'm back up and running now. Wahoo!
Thanks for the help to get me here.

e2p219 said:
And an update...
I ran the Nexus Root Toolkit again but restarted the bootloader first. This time it somehow found FASTBOOT and installed the image no problem. I'm back up and running now. Wahoo!
Thanks for the help to get me here.
Click to expand...
Click to collapse
Well, as bad as it is to say, I'm glad I'm not the only one who had this problem. Thanks for the advice, hopefully I can pull a Lazarus on mine, its been dead and buried in a drawer for months. Unfortunately my SIII just bit the dust (permanently) so its time to try to resurrect this one again.

[Q] Rooted Nexus 10 Stuck in Bootloop, Please Help!

Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.

Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks

Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.

danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.

Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!