Database Users

My solution for bootloop in 3.1

I rooted the tablet and it updated fine. I then reboot it and it is now stuck in boot loop. It says bootloader version unknown when I press power and volume button. What do I do?
Update. I have been able to successfully make my tab bootloop three times and three times have brought it back to life. All three times it has been because of an app that I guess is not compatible with 3.1. Because of my low thread post count I can't provide links or post into the development forum but my method has worked all 3 times.
A little background. First time I hadn't changed recovery and it was a bit easier. Second and third times I had cwm recovery and it was harder because adb wasn't recognizing my tablet.
First you need to have adb installed into your computer. I installed the sdk and then added the adb option. I then went into this post in the development forum: Re: [Solution] HC 3.1 OTA Difficulties 13% + Stock ODIN. In that post you'll find the Odin application for your computer and the appropriate PDA file for your tab. The PDA file contains the stock recovery, bootloader, and rom.
Whether you have stock recovery or cwm the next instructions are the same.
1. Connect the tab to computer.
2. Holding power button and volume down button, get into screen where you can choose fastboot or download mode. Choose download mode.
3. Once in download mode, on your computer open the Odin application.
4. Where it says PDA file, click the browse option to look for the PDA file you downloaded. Open it and it will be listed in the PDA section. Also the box next to PDA will be checked. Don't change any other settings.
5. Now you can press the button to run Odin. Don't touch tablet until it's done.
6. Now you can try rebooting it but it will still bootloop. Difference now is that you can adb into it.
7. With tab connected, go into cmd mode on your computer and type: adb reboot recovery
8. The tablet should reboot into stock recovery. From there wipe data and cache.
9. Reboot tablet and it should work! The tablet will be reverted back to 3.0.1. Just run the update again and enjoy.
Couple of notes. I tried the fastboot method mentioned in some posts but it never worked for me. This method that I've done has been flawless for me. I do have I/O version so I'm not sure if it is different from retail version. I think bootloops occur because some apps are not ready, stable, or compatible with 3.1. Something in the bootloader and recovery has changed in 3.1, whether it is changed via the apps or the update itself I'm not sure. I do know that the problem apps work great in 3.0.1, never causing bootloops, thus my conclusions.

Same thing happened to me. Fastboot -w did the trick. It wipes the tablet though.

Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App

Help needed Samsung galaxy tab 10.1 stuck in boot loop
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .

saviressej said:
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
How did you ADB it while it was in a bootloop?..

I'm stuck with this same issue! Everything was fine, I was on version 3.1 and I had rebooted it several times. Then one time it just got stuck on a bootloop and I can't figure out how to fix it. This is the google i/o version and I haven't done anything to it other than update to version 3.1.
I've been googling for an hour or so, but I have no idea what i'm suppose to be looking for. =\

you can recover.
i have posted detailed instructions in the OTA thread on xda.

sramasub said:
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
Click to expand...
Click to collapse
+1, i have the same problem. drained battery, recharged, stuck in boot loop. also got the "entering upload mode; cause undefined" message too.

I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.

_avatar said:
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
Click to expand...
Click to collapse
Yeah, I found your post a couple days ago, but couldn't get it to work. Once plugged into the wall charger, I couldn't get the charging icon to show up. I've tapped the power button, held it down for half a second, a full second, several seconds... it either does nothing, or tries to boot up.
I was able to get into Odin3 download mode and flash a ROM (see this thread: http://forum.xda-developers.com/showthread.php?t=1130216#2), but now my USB doesn't work and adb won't recognize it, so as a development device it's not very useful to me. I can't seem to get into the bootloader so I can't flash with adb or fastboot (when I boot into USB mode, adb doesn't recognize the device). I need to figure out how to flash an original I/O image, but can't seem to figure it out...

I've also had some difficulty getting to the "charging" screen, the trick is to be patient. Make sure the device is really off, plug it in, and walk away for a good while -- like 5 minutes.
When you say you're able to get it into USB mode what does that mean? Sounds like you are actually able to get it into fastboot mode. What operating system are you running? On my Mac the fastboot binaries I found floating around the net didn't work, I had to compile one from source. If you're able to get into fastboot mode but it's not detecting your device, and you have a Mac, I can send you the version I compiled from AOSP and you can try that. Let me know...

Try this...
http://forum.xda-developers.com/showthread.php?p=14791689#post14791689
Works for this guys.

I have a solution for the bootloop in my first post.
Sent from my GT-P7510 using XDA Premium App

I had a similar problem. Looks like Clockwork recovery can sometimes trash your /data partition and its format/wipe option won't fix it. I recovered by booting into stock recovery and formatting /data from there. Be forewarned that you'll lose your "sdcard," which really lives on /data.

Nice guide, thanks!

A200 bricked with black screen

Hi guys,
Original post was made on the AcerTabletForums, but I'd like to post it here too.
I kind of bricked my device, and I was hoping any of you might have useful input.
What did I do?
- I installed the CWN JB 4.1.1 found on this forum. Everything worked ok.
- I found the CWN JB 4.1.2 ROM on this forum, and decided to install that.
- Booted into recovery, wiped the cache partition -> ok
- Tried to wipe the data partition -> NOT ok, the system froze
- Could not boot anymore into the normal system, so rebooted again into recovery.
- Tried to install the CWN JB 4.1.2 ROM, to get back to a normal system -> NOT ok, the system froze again
And now, my A200 isn't doing anything anymore. I just get a black screen. The light on the button is on, but that's about it. All the key combinations to get it into recovery aren't working, it's simply black.
Is there a way to hack my way into the device without it booting? I guess I just have to build the file system again, but I can't manipulate the system if it's not booting ...
So far, I can only see my device popping up as "APX" in Windows. I can also see it in Linux when I probe it. That's good, right? The thing is still alive. However, I can't do any more than that ADB does not see it, so FastBoot doesn't see it either ...
Is there any way to do a low level flash of the device?
BTW: it is rooted, so I won't be able to send it to Acer. *sigh*

your device is still alive sort of... look around th thread there is some guide to revive it

calvin_ng said:
your device is still alive sort of... look around th thread there is some guide to revive it
Click to expand...
Click to collapse
You are in APX mode, which means, basically, you can only flash via NVFlash. This really is only useful for flashing bootloader files more or less. In some cases you can flash recovery image files , but probably not in your case, Unless you have the SBK (secured bootloader key), you're pretty much in a dire shape.
You can try installing an A200 stock update.zip from your ext sd. By holding vol+ and PWR. However, you may not get that far. Your recovery may be cooked as well.
I wouldn't worry too much about Acer Repair. Seeings they can't boot the tab to see what's on it, more than likely they will just change the mainboard and write it off as a bad chipset. They may try to run a service rom, which uses NVFlash, but the end result will be a clean tab anyhow.
Considering a percentage of tabs that take OTA result in APX or bootloop, I suspect there won't be an issue.

Hi there,
Sorry to hijack but I have a similar problem and I'm hoping someone can help.
I have a stock as a rock unrooted A200. I think my son let the battery drain and I haven't been able to turn it on ever since. I've kept the charger on overnight but I only get a black screen no matter what key combinations I use. The hard reset must have worked (even though I couldn't see anything) because my Win7 machine recognises the tablet and all my data is gone.
Is there a way I can revive it using the PC? I bought it cheap so it's not worth fixing but I kinda like it and it would be good for the kids to muck around on.
Thanks in advance.
Moscow Desire said:
You are in APX mode, which means, basically, you can only flash via NVFlash. This really is only useful for flashing bootloader files more or less. In some cases you can flash recovery image files , but probably not in your case, Unless you have the SBK (secured bootloader key), you're pretty much in a dire shape.
You can try installing an A200 stock update.zip from your ext sd. By holding vol+ and PWR. However, you may not get that far. Your recovery may be cooked as well.
I wouldn't worry too much about Acer Repair. Seeings they can't boot the tab to see what's on it, more than likely they will just change the mainboard and write it off as a bad chipset. They may try to run a service rom, which uses NVFlash, but the end result will be a clean tab anyhow.
Considering a percentage of tabs that take OTA result in APX or bootloop, I suspect there won't be an issue.
Click to expand...
Click to collapse

[Q] a500 with forgotten password and unable to restore unrooted tab

A coworker has given me an a500 to try and restore to a working conditiion. Here is the story I was given... Tablet was working fine but he had a pop up informing of an update. He ignored it for awhile but finally let it update and after it rebooted he was presented with a password screen. He has no clue what the password is. I don't know what the tablet was updated to and to my knowledge it is not rooted.
I have tried erasing user data by holding down volume up and power and toggling the screen lock switch back and fourth after the tablet vibrates. Tablet displays
Erasing Cache before SD update.
SD update cmd:recovery
--update_package=sdcard:update.zip.
Then displays in red Secure boot: image sos checksum fail. I have had a couple different update.zip files on the sdcard when trying this but none are successful and it never seems to erase user data as it always asks for a password.
I have also tried an EUU update and putting the tablet into apx mode manually but this to fails. I was able to get the CPUID off of the device using a thread on this forum and an Ubuntu installation.
I have poured over numberous threads and tried many things over the last couple days and have had no luck. I am look for some help in either just erasing user data so we can go through set up again or downgrading/rooting or what ever it takes to get the tablet in a usable state again. I have a little knowledge of rooting and using adb and have never tried ubuntu until this weekend.
Thanks

Can someone help me with this? Any suggestions?

jggrnaut said:
Can someone help me with this? Any suggestions?
Click to expand...
Click to collapse
theres a thread titled "will pay to get my tab fixed" actually there are 2, but in one of them I think the problem was resolved....I'll post a link to it if i can find it
oh... u say u used an update.zip - make sure it isnt still on yr sdcard???
out of interest what happens when u press power + vol UP - just wondering what bootloader the tab has...doing this will tell us
what part of apx mode failed???
i guess you've seen the SOS/LNX checksum thread???
you have a serious failure here, but hopefully not irrecoverable....fingers crossed

Hi, Thanks for responding. Its taken me a while to get back to this because of Thanksgiving and a project at work.
The update.zip is on the sd card. How do I move it the tablet?
When I press power + vol up the tablet vibrates then displays acer on the center of the screen. It then displays in the corner of the screen:
Erasing Cache before SD Update...
SD update cmd:recovery
--update_package=SDCARD:update.zip
Secure boot: image SOS checksum fail!
With the EUU update I run the PBJ20upgrade.exe. I then let it time out and manually put the tablet in apx mode. I then put in my CPUID and hit next. The tablet vibrates and displaces entering Acer download mode but the PBJ20upgrade.exe program displays that the upgrade process failed as soon as it vibrates.
The EUU update i tried was titled EUUs_SBK_Acer_A501_0.017.01_PA_ATT
Thanks again for the help

[Q] A500 Boot Issues...need assistance

I've searched and found a few similar (not identical) problems that people were having, and tried some of the solutions, and none have worked.
I'm trying to fix this stock Acer A500 for a friend. It will boot up part way, goes past the acer screen and android screen, but then stops at a black screen with 'android system' in the upper left corner, the home and back buttons in the bottom left, and the time, signal, and battery life logos in the bottom right. Then there's the Power Off thing in the center of the screen, and it says shutting down but it never shuts down.
I boot into the stock recovery mode, and it says in the upper left on the acer screen:
erasing cache before SD update
SD update cmd: recovery
--update_package=sdcard:update.zip
booting recovery kernel image
then it shows the android with the turning gears, then goes straight to the android with the warning symbol.
Since I can't get into the OS, i have no idea which version or specific model this is, but i downloaded a few different honeycomb update.zips, and put those on the SD card, and when i tried booting with those, the loading bar pops up under the android logo, and it goes to about 1/3 of completion before switching back to the warning symbol.
I tried downloading what im pretty sure was a full version of jellybean for this tablet, and it went straight to the warning symbol, no loading bar. same when i tried renaming the file update.zip >.>
im clearly very new to all this, but i'd really like to get this thing working.
is there a way to do a factory reset without booting all the way into the OS?
im not sure because it seems like the only file its looking for in recovery mode is update.zip.
if anyone has any bright ideas, id appreciate the help.
Also, not sure if this is relevant, but when i boot it normally, and it goes to the 'shutting down' screen, the battery level indicator says its almost dead, but i can leave it plugged in for hours and nothing changes at all.
EDIT: Also, it won't even boot if the power cable is not connected.

Similar issue hope there is a solution
I have a similar problem. Tablet was working fine, sitting on docking station. Returned to it the next day and when I went to wake it, it would not wake. Rebooted it but will not reboot. Sits on the ANDROID screen after the ASUS title screen indefinitely. If I try and boot into recovery it fails at "update.zip" and I see the broken Android image laying there.
Is there a means to restore it from PC via the usb cable and can someone please post a very noob friendly walk through step-by-step?
Greatly appreciate any positive advice!

Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD

zardoz99 said:
Probably the mmc failed. Same symptoms as mine. Non-recoverable.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
So, dead chip? So soon? Nice.

NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
Yep.. 14 months old in my case. Contacted Acer and said "what about a fix?" They said, "no chance unless you cross our palms with lots of silver."
So, bought a Samsung Note 10.1 instead. Acer can "stuff it". I won't be buying a tablet from them again. Considering that I bought their "flagship" product of the A501 with the 64GB memory, this is truly unacceptable.
I was incredibly careful with it and certainly never did anything to void the warranty. But, you only get 12 months and then it's over.

NoOneSpecific said:
So, dead chip? So soon? Nice.
Click to expand...
Click to collapse
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?

skurtov said:
I wouldn't go as far as to say dead, have you tried booting into APX mode and then running BABsector?
Click to expand...
Click to collapse
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!

NoOneSpecific said:
Definitely more than I can manage but I've handed the tablet over to a friend who is capable of understanding and performing your suggestions. All are greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD

skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
I'll have him PM you when he is able.
Thanks!

skurtov said:
Certainly if your friends wants a point in the right direction have him post here or pm
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!

coluwyvurne said:
Hey Skurtov,
Thanks for the offer to help my friend NoOneSpecific.
If my Android terminology is correct, APX mode is the diagnostic mode which invokes the Bootloader when a device specific combination is held while powering on, right? And while the Bootloader GUI is active, it is shown on a PC as an Nvidia device?
I believe the key combination on the A500 is Volume-Down and Power, but doing this causes the tablet to automatically boot from the recovery kernel image. The same message appears regardless of whether an SD card with a decrypted update.zip is present or not.
If I am mistaken, I would greatly appreciate your help in pointing me to the right step in getting my friend's tablet working again!
Cheers!
Click to expand...
Click to collapse
You are quite right sir, however the button combination I am most familiar with is holding the power and the reset button (the one you have to stick the paper clip in) when you first start it up. It should then either say APX mode on the screen or be blank, either way the computer will identify it as a APX device and automatically install the drivers.
Going into APX MODE manualy
You enter APX mode by holding down the Reset button(with paper clip). Do not release it. Hold down power for 3 secs and then release it. After another second, release the reset button.
Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
The screen of your tablet is black.
Quoted from Civato
Click to expand...
Click to collapse
The next course of action is to get the SBK, from what it sounds like the tablet didn't write a partition properly and that's why it's not booting. So what you can do is wipe out the partitions and install a custom bootloader and recovery. Not only does it fix things but it also opens up his world to custom roms . Okay, back to the matter at hand, I don't know if he has his SBK or not, and if he does skip the step to find it and just run babsector below. If not then follow the next step.
You'll have to pull the UID from the tablet using this method described here:
http://git.pappkartong.se/?p=a500/apxuid.git;a=snapshot;h=HEAD;sf=tgz
There's a readme
After getting the UID and calculating your SBK you'll just go to the next step.
All credit goes to user eppeP.
Click to expand...
Click to collapse
Run this file hosted here:
http://narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
And this file basically rewrites and formats the partitions out installs a custom bootloader and recovery
Credit goes to Danny2 for finding this and posting it.
Click to expand...
Click to collapse
Once this is done, pick a new rom. I prefer the Civato ones, load it on a SD, boot to recovery, erase dalvik cache, cache, do a factory reset wipe (from the recovery menu!), then wipe system, flash the rom and go on your merry way

Many thanks for the reply.
As per your instructions, I have booted the tablet into APX mode. However, as I do not know the UID of the device, I've had to try to run the utilities to create a driver for the device and then pull UID from the tablet...
I am able to create the driver for the device and install it with driver signing off in Windows, but I can't figure out how to run the script to get the UID. I notice the file in the package you directed me to contains an .SLN file, which would indicate it is a programming solution file. I have Visual Studio on my system but it cannot open this particular .SLN file.
How would I run what's in the package to pull out the UID of the tablet?
Any help getting past this hurdle would be much appreciated!

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