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!

[Q] How can I fix a bad recovery flash?

Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.

stickplayer said:
Please see Update 5 at/near the top of:
http://forum.xda-developers.com/showthread.php?t=2176452
Basically, a bad USB cable was making fastboot operations flakey, and by the time I discovered it, the recovery program was wrecked. Everything else seems to work fine. The Nexus is running 4.2.2, and I have toolkit 4.3.5, running on win7x64.
I've tried reflashing various recovery programs, including the stock one. No error flashing is reported (with the now-good cable), but going into recovery mode fails, showing the android image with a red triangle and exclamation point in it.
[Edit: To be clear, I have NO recovery menu at all - when I select recovery in the bootloader, I get the regular boot "X" in the middle of the screen, then it is replaced with the android lying on its back with the alert notice above it]
The bootloader appears successfully unlocked, and in fact the entire unlock/root process was fine, once the cable was replaced. That is, no errors were reported, everything seems to be ok, but I can't use the recovery option. Note that the unlock wiped all data, so it was as clean as possible.
Should I completely reflash 4.2.2? Will that even matter?
Is there anything else I can try? I'm not keen to try sideloading 4.2.2, but will, if there are instructions some place.
If this is no go, I'm going to have to try restoring everything to the basic original state and asking for a replacement from Amazon. I don't know how that will go, and this was to be a gift due in about a week, that I was setting up for the recipient. I've spent literally 8 hours on this today, before realizing the flakeyness was due to the USB cable being bad. Any help is very appreciated.
Click to expand...
Click to collapse
So you've tried using fastboot to flash a custom recovery image? The command fastboot is a part of the Android SDK.
fastboot flash recovery <name of recovery .img>
There's plenty of stickies and information in this forum, which I won't re-hash here.

The stock recovery WILL show the android with the red triangle. To get into recovery from there, I believe you need to hold the up volume key. Other recoveries shouldn't do this though. Perhaps you should try using ROM Manager or Goomanager to flash a recovery from within android.

It took several attempts - flashing stock, then cwm, from the toolkit, before cwm finally "took". It's all working now.

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

[Q] Phone always boots to fastboot

Hey all, I figured it was time to make a post and see if anyone could help figure out what I'm missing.
So I recently got my G2 and rooted it, then I installed Team Win Recovery Mod (on accident, actually. Was intending to install Clockwork, but figured it wouldn't hurt anything and it was working fine). Anyway, moved on to install Cyanogen Mod and gapps following the usual factory reset -> flash from /sdcard/ approach. Unfortunately on reboot, it went into fastboot mode.
Since then I've read a ton of stuff about fastboot, and I've reflashed recovery, boot, and system a dozen times, but I'm still stuck in fastboot mode. I've grabbed the CWM for LG G2 (AT&T) from http://www.clockworkmod.com/rommanager and the latest stable Cyanogen Mod from http://wiki.cyanogenmod.org/w/D802_Info. Sadly everything I've seen just tells me to do what I did - reflash recovery and tell it to reboot. I've also tried the "volume down + power until logo, then release and re-hit" method of getting into recovery mode, but the logo is present for literally less than a second, so I just end up back in fastboot.
Perhaps I need to find an flash a stock OS first? The thread on returning to stock firmware scares me :/ http://forum.xda-developers.com/showthread.php?t=2432476 Edit: I gave in and tried playing with this anyway. No good, I can't get the phone to enter "download mode", no matter what I do, it reboots into fastboot.
Any ideas?
Edit: The flash method I used for TWRM: http://forum.xda-developers.com/showthread.php?t=2449670
Edit2: This seems possibly relevant. When I do "fastboot devices", I get "? fastboot". So something is wonky in terms of its detection. But all the commands seem to be getting executed fine...
Edit3: Finally a potentially useful piece of info: If I flash the boot image extracted from the Cyanogen mod zip, then run "fastboot continue" I get "ERROR: Getting device tree address failed". Which is the same message I get when trying to remotely run a boot image without flashing it. Possibly related to the "?" in the "fastboot devices" listing above? I switched to Koush's Universal Adb Drivers, but no change.

Pretty please?
I find it hard to believe I could manage to brick a 2 week old phone just by following the guides posted here

Well, I still have no clue what went wrong, but I was finally able to make use of the reset to stock thread. It was strange and scary and at no point did I really have any idea I was hitting the right buttons, and at the end it said it failed... BUT it rebooted me into a fresh install, apparently even unrooted! My problems along the way appear to have entirely been related to actually getting the phone *into* download mode since I couldn't get it to actually turn off. Once it ran itself out of battery and turned off, I was able to enter download mode while reconnecting it to power.
No to decide if I want to try installing a custom ROM again, or take this as a sign...
Who am I kidding. *re-roots phone and pulls up the mod threads*

TWRP won't boot - Nexus 7 2012 wifi

Hi
I know this is an old device but I got it for free and feel it's a good device to experiment on. Looked thru all the posts I could pertaining to this but am not clear what to try next and wish to avoid bricking.
I have tried to flash various versions of TWRP and none will boot. Can still get into fastboot, device is recognized by adb. Says it is loading, but when I try to get to TWRP recovery I only get the exclamation point. I can get to the stock bootloader (is that right?) with Power+Volume up.
On power up it goes thru the Android startup but then I am presented with a screen asking for location, goes to WiFi step and hangs. No problem powering down and getting to fastboot.
What should I do next? My thought is to try and re-install factory image (have it) via directions here - https://forum.xda-developers.com/showthread.php?t=1781250
Any other suggestions?

This is great - I can answer my own post!
Digging around I read post for a Samsung Device having same problem. Solution was that the device would re-write the bootloader on reboot (the solution there was an option to not overwrite bootloader in Odin).
So instead of running 'fastboot reboot' I ran 'flashboot reboot-bootloader' and there was TWRP.