Boot Loop - Transformer TF300T Q&A, Help & Troubleshooting

Hi Guys,
I am stuck in a bootloop with Asus TF300T. I can power down and get the four icons up but if I go to wipe it tries to restore to factory settings and then crashes with Android lying on its side with red warning triangle above its body. I have tried to install drivers on Windows 8.1 to no avail....
If I get it into RCK mode it states booting kernel recovery then it eventually goes to Android on its side again with warning triangle.
Looked on threads but I can't get into the modes to try what others are suggesting.
I can do this kind of thing on Samsung Galaxy S2 easily but baffled with this.
Thanks in advance.

steverido said:
Hi Guys,
I am stuck in a bootloop with Asus TF300T. I can power down and get the four icons up but if I go to wipe it tries to restore to factory settings and then crashes with Android lying on its side with red warning triangle above its body. I have tried to install drivers on Windows 8.1 to no avail....
If I get it into RCK mode it states booting kernel recovery then it eventually goes to Android on its side again with warning triangle.
Looked on threads but I can't get into the modes to try what others are suggesting.
I can do this kind of thing on Samsung Galaxy S2 easily but baffled with this.
Thanks in advance.
Click to expand...
Click to collapse
do you have a locked bootloader?

robgee789 said:
do you have a locked bootloader?
Click to expand...
Click to collapse
I believe that the Bootloader is locked.
Thanks

Related

[Q] 3.2 Update bricks my Transformer!

I got home on Friday and my Transformer told me there was an update available and it would take about 10 minutes to install. I followed the instructions and the tablet just hung on the boot screen. I left it for an hour and nothing changed. The only way I could get things working again was to wipe all data and restore it to factory settings. I did this and then went to the update screen where it once again told me there was an update available.
I followed the instructions and the exact same thing happened, so I wiped it again and started from scratch.
Anyone have any ideas here?
TIA.
Well first off it's not a brick. A brick is where you cant even get into APX mode. Secondly were you seeing an android image with an exclamation point on the screen? Or what did the screen look like that it hung on?
Are your rooted with CWM recovery installed?
stuntdouble said:
Well first off it's not a brick. A brick is where you cant even get into APX mode. Secondly were you seeing an android image with an exclamation point on the screen? Or what did the screen look like that it hung on?
Click to expand...
Click to collapse
It's the standard Eee Pad boot screen - the one that appears when you turn on the pad. No Android image.
Sounds like you need to hunt out and remove the .zip file on your device for the update that seems to remain after a hard reset, using ADB and the usb cable to your pc.

[A700] Bricked into "Boot image verified failed"

Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
V4lk0 said:
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
Click to expand...
Click to collapse
Just let the battery run dry. Then let it boot up normally without pressing any buttons when the battery runs out by connecting it to your charger. Hope it works!
Thanks for the reply. I tried that, but nothing happens, just the indicator LED on the power button turns on orange. The tablet does not boot on itself, if I connect the charger. I have to press the power button, but this results again in "Boot image verified failed"
Edit: Update. I figured out how to get into fastboot. I read something on google, with switching the screenlock switch on and off. That doesnt worked for me: The thing was, to hold the power button AND the volume button with the two knobs, then the tablet starts, to release the power button and THEN, while still HOLDING the volume button pressed, to switch on and off the screenlock button. Then the bootloader starts into fastboot mode, going into androidsdk and typed in cmd "fastboot oem unlock" solved the problem. The ROM starts and everything is fine
Why you don't write into the mentioned thread? There seems to come the issues from then ask there, sorry can't understand why opening new thread instead asking there.
Also the first time heard sucha thing, I also change the rooms from cm10 to Jacobus, back to stock, on cool one and to cm and back, to test everything and try something out.
Never had issues buy this ways
Gesendet von meinem GT-N7000 mit Tapatalk 2
I don't have the right to post in the proper thread, so I opened up a new one.
In order to install a JB based ROM, you need the JB compatible CWM. The version of CWM you used is apparently for ICS, so I am a little surprised it worked to install CM10. Where did this 6.0.2.3 come from? Use 6.0.1.5 from pawitp. I've used it and swapped/flashed ROMs at least ten times. Never encountered that issue (or any issue). As a matter of fact, I would just run Vorbeth's EasyRoot as it does all the grunt work for you. I've used it twice and it worked flawlessly.
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
V4lk0 said:
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
Click to expand...
Click to collapse
Hi I had the same issue after flashing from CM10.1 to CoolOne. However I fixed it by unlocking the bootloader => reinstalling recovery => flashing CM 10.1 back.
Did you have any luck recovering from APX?
Gullinbursti said:
Did you have any luck recovering from APX?
Click to expand...
Click to collapse
No, unfortunately not. I gave my tablet 2 weeks ago to the acer repair service and got it back today. The support said, that they have changed the mainboard and flashed the latest android on the tablet, but they did that on guarantee, so I didn't had to pay something ^^ Now it is running Android 4.1.1 Stock ROM from Acer.
Exact same problem
I am having the exact same problem. I am able to boot into recovery mode but then I get the android laying down with with the red triangle, question mark. My bootloader is unlocked but aftrer the update my screen is stucked on the ICONIA TAB startup screen.

[Q] Relay Boot Loop

Chrizuki said:
My Relay wont boot into recovery mode. Whenever I hold the Volume-Up + Home + Power, it turns on then it says on the top left corner a small blue colored message saying "RECOVERY BOOTING..." and then it goes to the "Galaxy S Relay from T-Mobile" screen and then black screen. Nothing happens, it doesnt boot into recovery but it can turn on and function well with the OTA Jelly Bean 4.1.2 update as well as boot into Download mode. I have rooted it before when It was still ICS 4.0.4 and I guess I didnt unroot it correctly.
A couple of days ago, I heard about the Jelly Bean update, which I wanted, so I used Kies to update. I connected my phone while in Download mode and Kies did its thing and my phone was unrooted when it booted up and had Jelly Bean. It worked perfectly, but it couldnt boot into recovery mode. I dont think it's a huge problem to not boot into recovery, but to me, I feel safer having it.
Is there a way to fix this using just Samsung Kies? Is there a way to flash that recovery or something using Odin? If so, where can I find it and how do I do it?
Thanks in advance!
Sent from Chrizuki's SGH-T699 in Development using xda app-developers app
Click to expand...
Click to collapse
My Relay wont boot into recovery mode. Whenever I hold the Volume-Up + Home + Power, it turns on then it says on the top left corner a small blue colored message saying "RECOVERY BOOTING..." and then it goes to the "Galaxy S Relay from T-Mobile" screen and then black screen. Then it goes back to the "Galaxy S Relay from T-Mobile" screen followed by black and back again.
My phone is currently NOT rooted. I attempted to root it when I first got it and almost bricked it so when I got it back to working I just left it. I've had my phone over a year and have recently over the past few months had issues with the charging port and batteries even holding a charge. Bought extended life slim batteries and a charger due to that issue. Then just yesterday I was using facebook on my phone and it randomly rebooted and wouldn't stop boot looping. Only way I've stopped it thus far is to take out the battery.
Any help would be greatly appreciated.
Sounds as though your recovery image might be corrupted. I'd utilize ODIN or heimdall to reflash recovery using download mode and see if that fixes your issue. If you were rooted, and feeling adventurous, you could even do so from within the OS. One more question though: Are you releasing the buttons when you see the samsung boot logo with 'RECOVERY BOOTING....' in the corner? If you do not, then the phone will simply reboot again into the OS. Always let the buttons go once the recovery boot process begins.
Magamo said:
Sounds as though your recovery image might be corrupted. I'd utilize ODIN or heimdall to reflash recovery using download mode and see if that fixes your issue. If you were rooted, and feeling adventurous, you could even do so from within the OS. One more question though: Are you releasing the buttons when you see the samsung boot logo with 'RECOVERY BOOTING....' in the corner? If you do not, then the phone will simply reboot again into the OS. Always let the buttons go once the recovery boot process begins.
Click to expand...
Click to collapse
Haven't had much of a chance to try due to distractions plus work along with internet issues at home and a friend's house. I will try ODIN. What is heimdall? I've never heard of that.
Yes, each time I try to reboot into recovery I am releasing the buttons as soon as I see the samsung boot logo with 'RECOVERY BOOTING....'
As always Magamo, Thanks for your help
RockinRita said:
Haven't had much of a chance to try due to distractions plus work along with internet issues at home and a friend's house. I will try ODIN. What is heimdall? I've never heard of that.
Yes, each time I try to reboot into recovery I am releasing the buttons as soon as I see the samsung boot logo with 'RECOVERY BOOTING....'
As always Magamo, Thanks for your help
Click to expand...
Click to collapse
Heimdal is an open source program that implements the ODIN functions. I usually use it as a command line tool, but it does have GUI front ends.
http://glassechidna.com.au/heimdall/
getting frustrated
Magamo said:
Heimdal is an open source program that implements the ODIN functions. I usually use it as a command line tool, but it does have GUI front ends.
http://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
Magamo, I've downloaded Odin 3. 10..6. Not exactly sure what to do now cos I just tried to put my phone into download mode and it boot loops again! So if I can't go into recovery mode or download mode, what can I do? My phone is not rooted and I don't want to root it. Ideally I want to be able to at least copy some of my text messages before rooting it but how can i do anything if I can't get it to go into recovery mode, download mode, or even turn on without boot looping?!
I dont even know what made it randomly one day decide to shut itself off and boot loop.
Any ideas you (or anyone else has) would be very much appreciated!
-Rita-
Sorry i guess i cant help u on this one. But good luck m8!

[Completed] [Q] Nexus 4 in boot loop after rooting

Hi,
This is my first post on this forum and I might sound like a total dummy (cos I am when it comes to rooting/flashing android devices).
My Nexus 4 was suffering from poor battery performance and to correct that I thought of trying my hands at rooting it and flashing it with a custom ROM. However, being a noob, little did I realize what I was getting myself in to.
Now, after unlocking the boot loader, when I tried to boot my device from recovery mode, it just wouldn't fire up, but kept showing the rotating dots of lollipop boot screen.
After a lot of fiddling, I managed to mess up even further as now, the rotating dots are also not appearing and I just get Google logo twice and after that the device's screen just keeps blinking with a faded background light on the screen.
I used Nexus4Root to root the device and have ADB installed on my Mac OS X machine.
Is there anything I can do to bring my Nexus 4 back to life?
Any help is appreciated.
Thanks.
ajxkid said:
Seems like unlocking your Boot loader have not been successful , Toolkits are not always dependable. I think you should unlock ur Boot loader manually with adb and fastboot .
You could find guides for that all over the web. Go on and try that..
Good luck
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the response. I think I did manage to unlock the Boot loader, as I can see that in the status when I switch ON the phone in 'recovery mode'. The problem is that I am not able to boot the phone through recovery mode. As I said, it goes in a sort of boot loop. It does not boot from normal mode, same thing happens (boot loop).
Is it possible to flash the factory image in the current state of device? The device is not detected by my Mac when I try to fastboot it.
Any guides/threads I can look at with similar information? Have been looking up quite a lot online, but to no avail.
Thanks again!

Nexus 5 won't start "no command" HELP PLEASEEE!

Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
DEVICE IS NOT ROOTED
So I went into recovery mode
I tried clearing partition... it didnt work (did that 5 times)
I tried reboot system (didnt work)
I turned it off and on like 10 times and it didnt work
I tried Wipe data/factory reset....lost everything (which sucks because I had photos that never got backed up)
I am official lost, can someone help me? I am not sure what to do next!
I have a macbook, if someone can help me I will greatly appreciate it!
agentjucey said:
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
Click to expand...
Click to collapse
Hello. I have this same problem.
I can't start my phone.
I have no idea what happened. Phone was connected to charger and everything looked ok, but this s**t happend ...
On error screen I've pushed power + volup button
Wipe cache
wipe device ...
nothing helped ...
Still getting this same error ...
Are you getting an error message on the screen or is the phone stuck at the boot animation?
audit13 said:
Are you getting an error message on the screen or is the phone stuck at the boot animation?
Click to expand...
Click to collapse
Android with red triangle and exclamation mark inside ...
Same problem here. This was after applying OTA latest security patch for April.
Would try to boot ("Google" word) 2x then go back to Android bot with red "!" - no command.
Tried wiping cache; factory reset - both multiple times. Still the same.
Tried also draining battery, then full re-charge, still the same problem.
Hope somebody could figure this out.
Thanks in advance.
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
audit13 said:
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
Click to expand...
Click to collapse
I did that ...
wiped cache - no result
reset to factory - no result
Flash the factory image. If your phone is not bootloader unlocked do that first
GtrCraft said:
Flash the factory image. If your phone is not bootloader unlocked do that first
Click to expand...
Click to collapse
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
tupper said:
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
Click to expand...
Click to collapse
Yeah its here in the general section
Flash factory images from NRT tool
1 Unlock ur bootloader
2 flash latest factory image and clear ur internal memory also! Coz the tool has an option to clear internal memory or not to clear internal memory!
3 Done!

Categories

Resources