Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
DeBedenHasen said:
Hello XDA.
After whipping my Moto E out the other day, I noticed that turning it on results in it just... laying there and showing me the "WARNING - BOOTLOADER UNLOCKED" message.
Around 1 1/2 years ago, it just turned itself on after clicking the power button once. Now, not even Fastboot mode helps, as choosing any of the options listed there results in the warning mentioned above. For clarification, here is everything in short:
The phone does NOT turn on normally
Using any option in the Fastboot boot menu restarts the loop (i. e. instantly goes back to warning message)
NEITHER does Minimal ADB and Fastboot recognize the device, NOR does the phone recognize the connection to any PC (I've tried 4 different PCs)
Since Fastboot is unresponsive, suggestions to restore stock recovery are useless to me
Suggestions to perform a factory reset are also useless, since Fastboot is unresponsive.
So, am I right if I suppose that this is a hard brick? Or is this somehow salvageable? If so, please help me...
Thanks in advance!
Click to expand...
Click to collapse
If its stuck on boot, its definitely not hard brick.
What was the android version when you wiped data?
Was there any custom recovery you used to wipe data?
You possibly wiped /system too, wiping system can result in bootloop.
Daman5202 said:
If its stuck on boot, its definitely not hard brick.
Click to expand...
Click to collapse
That's a relief. Thanks.
What was the android version when you wiped data?
Click to expand...
Click to collapse
I'm not sure about it, but I think it was 4.x.
Was there any custom recovery you used to wipe data?
Click to expand...
Click to collapse
No, there wasn't.
You possibly wiped /system too, wiping system can result in bootloop.
Click to expand...
Click to collapse
Sorry, but that doesn't make sense. The phone's been rooted for almost 2 years now, and 1 year ago, it turned on perfectly fine.
But let's assume that actually happened somehow, how do I recover from this?
Related
This thread is referring to this method of unbricking:
http://forum.xda-developers.com/showthread.php?t=1226470
I am having the same issue from the OP. However, when I get to step 3-5 where I use "adb reboot bootloader", it doesn't bring me to the bootloader (blue screen). At first when I tried to time it right, I got "device not found". However, as I tried more often, the command seems to go through as it returns blank, but the only thing that happens is the phone reboots and displays the "factory reset...formatting data...formatting cache...do not remove batttery...rebooting" again.
I've tried about 20 times now and, instead of bringing me to the bootloader screen, it keeps rebooting everytime I use "adb reboot bootloader. I would appreciate any help I can get.
I started a new thread because I cannot reply to the original thread as I do not have 10+ posts yet
I was thinking maybe I can't boot into bootloader since it cant even boot into recovery? Is that possible?
I'm in the exact same boat as the OP.
qmriis said:
I'm in the exact same boat as the OP.
Click to expand...
Click to collapse
well guys you are not alone :crying: i was try to fix my wife phone today and i have the same loop issue like OP. the hard part is the windows won't reconize the phone anymore just for a instance of sec when phone start the format processes t clear format and install and boot at the same screen over and over so way i can get to fastboot or even recovery mode
Please help a noob dad with a distraught teenage son who is not as tech savvy as his peers, or his noob dad.
Son and I both have absolutely stock TMo HTC Ones. Mine is fine.
His had all his music on it, and his music was not backed up. (His laptop's hard drive crashed just two weeks ago and he had not gotten around to restoring his music yet. He is not having a good month with tech.)
His phone without warning entered a boot loop. It restarted itself, reached the bootloader/simply brilliant splash page, reached the T Mobile LTE splash page, reached the HTC One Beats Audio splash page, dimmed a bit, went blank, and then restarted the boot sequence. This goes on infinitum, and even after we let the phone battery run down to zero, recharged and started it again.
We can enter the bootloader by pressing volume down and the power key at the point where the screen goes blank after the HTC One Beats Audio splash, and from there we can go to recovery or into fastboot. When in fastboot, the phone can be connected to a computer, where it shows up as an "unspecified" device called Android 1.0. This device does not show up as a storage device - so we don't see the files. It has a driver called MyHTC. The phone screen shows FASTBOOT USB in red, but running adb with the command adb devices doesn't show anything in the device list.
As I said, the phone is absolutely stock - that means it is locked, and never was unlocked. And I understand that unlocking the bootloader to install a custom recovery would wipe the data files, thus defeating the purpose of the exercise.
We won't mind trying a factory reset, or even trying to root the phone, if we can first get to the music and save it. Is there some way to save it?
Now, mind you, two days ago terms like adb, bootloader, Android SDK, custom recovery, etc., were completely foreign to me. These are things I have picked up trying to solve the problem with Google and personal grit. So please bear that in mind when answering.
Is there some way to access the data files on this phone from the bootloader screen or from the recovery screen? If the phone can't be booted up and the phone can't be unlocked without being wiped clean, it seems my son is going to be spending a lot of time and money recreating his music library. Is this true? Have we finally found a situation that Dad can't rescue his offspring from?
Thanks in advance for any ideas...
GenerousDad said:
Please help a noob dad with a distraught teenage son who is not as tech savvy as his peers, or his noob dad.
Son and I both have absolutely stock TMo HTC Ones. Mine is fine.
His had all his music on it, and his music was not backed up. (His laptop's hard drive crashed just two weeks ago and he had not gotten around to restoring his music yet. He is not having a good month with tech.)
His phone without warning entered a boot loop. It restarted itself, reached the bootloader/simply brilliant splash page, reached the T Mobile LTE splash page, reached the HTC One Beats Audio splash page, dimmed a bit, went blank, and then restarted the boot sequence. This goes on infinitum, and even after we let the phone battery run down to zero, recharged and started it again.
We can enter the bootloader by pressing volume down and the power key at the point where the screen goes blank after the HTC One Beats Audio splash, and from there we can go to recovery or into fastboot. When in fastboot, the phone can be connected to a computer, where it shows up as an "unspecified" device called Android 1.0. This device does not show up as a storage device - so we don't see the files. It has a driver called MyHTC. The phone screen shows FASTBOOT USB in red, but running adb with the command adb devices doesn't show anything in the device list.
As I said, the phone is absolutely stock - that means it is locked, and never was unlocked. And I understand that unlocking the bootloader to install a custom recovery would wipe the data files, thus defeating the purpose of the exercise.
We won't mind trying a factory reset, or even trying to root the phone, if we can first get to the music and save it. Is there some way to save it?
Now, mind you, two days ago terms like adb, bootloader, Android SDK, custom recovery, etc., were completely foreign to me. These are things I have picked up trying to solve the problem with Google and personal grit. So please bear that in mind when answering.
Is there some way to access the data files on this phone from the bootloader screen or from the recovery screen? If the phone can't be booted up and the phone can't be unlocked without being wiped clean, it seems my son is going to be spending a lot of time and money recreating his music library. Is this true? Have we finally found a situation that Dad can't rescue his offspring from?
Thanks in advance for any ideas...
Click to expand...
Click to collapse
Very well written question... I'd start with a Fastboot command (entered while the phone is connected to pc and phone screen shows fastboot usb) 'fastboot erase cache.' It will return success, failure, or waiting for device. If it returns success enter 'fastboot reboot.' There is a small possibility this will allow his phone to boot normally.
You are correct that unlocking the boatloader erases the phone although there may be alternative if s-off is possible while the bootloader is locked - anyone? And ADB commands only work when the phone is booted into android or recovery not fastboot. And I have no experience with stock recovery but it might be possible to wipe cache there too.
Sent from my HTC One using Tapatalk
Thanks very much for the reply.
I tried the command 'fastboot erase cache' and it replied with "******* Did you mean to fastboot format this partition?"
Then, without waiting for an answer to that question, it proceeded - it said "erasing cache" and then "OK [0.575s]" and then "finished. Total time 0.575s."
I interpreted that as success, so I proceeded to enter the command "fastboot reboot." The phone rebooted - into the same boot loop I described earlier.
If you (or anyone) thinks that adb will help, I CAN get the phone into recovery mode as well. The phone allows me the option to wipe the cache partition from there (which I did), but a friend of mine (actually, my ophthalmologist as well) suggested I wipe the dalvik cache. Not only do I not know what a dalvik cache is, but I don't see any option for it on the HTC One recovery menu. I also don't know whether wiping the cache partition from the recovery menu is any different than what I did with the fastboot command - but in either event neither one eliminated the boot loop.
Any more ideas for either getting the phone to boot or saving the music so we can factory reset and then restore the music would be appreciated!
make a full adb backup and then unpack the contents
http://androidforums.com/application-development/163138-how-basic-adb-commands.html
http://forum.xda-developers.com/showthread.php?t=1572600
holmesnmanny said:
make a full adb backup and then unpack the contents
http://androidforums.com/application-development/163138-how-basic-adb-commands.html
http://forum.xda-developers.com/showthread.php?t=1572600
Click to expand...
Click to collapse
The only abd access he'll have at this point is for sideloading (Does the stock recovery even do sideload?), which if I am not mistaken, allows only a small subset of abd access (not enough to do the backup).
Would be so much easier if the handset was unlocked. A custom recovery would go a long way to recovering any data from the device... I've never had a device I didn't unlock right away so I'm afraid I can't help much beyond giving my doubts regarding the adb solution...
PhoenixPath said:
The only abd access he'll have at this point is for sideloading (Does the stock recovery even do sideload?), which if I am not mistaken, allows only a small subset of abd access (not enough to do the backup).
Would be so much easier if the handset was unlocked. A custom recovery would go a long way to recovering any data from the device... I've never had a device I didn't unlock right away so I'm afraid I can't help much beyond giving my doubts regarding the adb solution...
Click to expand...
Click to collapse
PhoenixPath, I'm afraid, was right, and we ended up doing a factory reset. My son restored the phone's contents as best he could, making sure to back up this time, and then powered off, but when powering back on the PIN unlock keyboard doesn't come up.
Sigh.
Any ideas? I'll post another thread on this...
Thanks to all who offered ideas.
Did you even try to do what I said or did you just assume I was wrong in full ?
I guess if you're not really interesting in ideas I guess you'll just choose altogether not to try some.
Hello, as you can see the title, because of my stupid friend, my tablet can't work well now..
He set the password in my tablet and I didn't even noticed at that time.
After I asked him the password, He told me He forgot it.
Unfortunately, that was true, so for unlocking the tablet, I did the wipe data and factory reset.
That was the problem.
After did that, my tablet starts to bootloop, just showing the dell logo.
I tried to access the recovery mode again, but all I can see is that the broken robot, and can't go next step.
I searched the similar threads and I found that if I can approach the fastboot menu, it is able to unbrick the tablet.
I could approach that menu which I can choose normal boot, power off, reboot fastboot, and recovery mode, but that's it. I pressed the volume buttons (up & down simultaneouly) tried many times to recovery mode but after did the factory reset, it couldn't do it again.
Could you give me some advice to solve this problem? I'm looking forward to getting the solution. Thanks. :crying:
guesstres said:
Hello, as you can see the title, because of my stupid friend, my tablet can't work well now..
He set the password in my tablet and I didn't even noticed at that time.
After I asked him the password, He told me He forgot it.
Unfortunately, that was true, so for unlocking the tablet, I did the wipe data and factory reset.
That was the problem.
After did that, my tablet starts to bootloop, just showing the dell logo.
I tried to access the recovery mode again, but all I can see is that the broken robot, and can't go next step.
I searched the similar threads and I found that if I can approach the fastboot menu, it is able to unbrick the tablet.
I could approach that menu which I can choose normal boot, power off, reboot fastboot, and recovery mode, but that's it. I pressed the volume buttons (up & down simultaneouly) tried many times to recovery mode but after did the factory reset, it couldn't do it again.
Could you give me some advice to solve this problem? I'm looking forward to getting the solution. Thanks. :crying:
Click to expand...
Click to collapse
Reflash firmware with intel flash tool.
Look THIS thread and follow instruction.
Thanks for your tips!
minnaing said:
Reflash firmware with intel flash tool.
Look THIS thread and follow instruction.
Click to expand...
Click to collapse
Thanks for your tips!
I followed the steps which you told me, and I could flash that files.
But after did that, it made the tablet freeze, not bootloop.
The screen just shows dell logo and didn't work well. I waited for 15 minutes, even more but it didn't work well.
And still I can't approach the recovery mode. Just I can see the broken robot..
Is there anything I can do? Hope to get advice :'(
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.