Hello,
I bought a new device and therefore wanted to factory-resent my Nexus 5 to give it to my wife.
I did it from within Android and then it restarted and stayed in the "Erasing..." screen for quite a while, then showed the dead robot with the "!" triangle sign, then rebooted and started "Erasing..." again, with apparently no way out.
I had unlocked bootloader and TWRP, but also booting the recovery went back into "Erasing..." mode.
I then tried to boot from an external TWRP iso image with fastboot from the PC. TWRP seemed to load, then started doing a bunch of things like formatting "something" (was too quick to read) and suddenly in a matter of second it was back to the robot but now without the "Erasing..." label anymore and now it's stuck there.
No idea what happened and how to fix and now I'm somewhat scared of trying something else.
Any idea?
Never mind... Flashed ALL stock images from fastboot (just userdata and cache didn't work) and it rebooted.
No idea what the problem was.
Related
I am not exactly sure what happened, but I am stuck in the "Android system recovery <3e>" menu. I had unlocked the phone before and was trying to relock it and get it back to stock because the new update wouldn't install.
While the HTC update utility was installing the stock firmware, I think the cable came loose at some point because it stopped part way. Now it boots, shows the HTC logo, goes black and then eventually shows a phone lying down with a red triangle and an exclamation point. I can push vol+/power to get "Android system recovery" to show up, but that seems to be all. It says "Mount SDCARD failed".It will only boot to this menu. I cannot load the bootloader or anything else so I can't seem to use fastboot or adb and can't seem to copy any files onto the phone. Does anyone have any ideas? Is it totally bricked?
Edit: doing a factory reset from recovery does nothing.
Edit2: Sorry!!! False alarm. After spending about an hour going back and forth with this and finally breaking down and posting about it on XDA, suddenly the bootloader DID appear. I have absolutely no idea what I did differently. I guess the 500th try was the charm. Reflashing stock now!
So I decided to try to flash Zombie-Pop today and everything went fine during installation but when the tablet started booting up it was stuck on "android is starting.." and it seems to load the apps. I knew it would take a bit of time to stabilize so I let it run but after 1 hour of it stuck there, I tried to reboot into recovery but I get a black screen and I can't access TWRP. It just boots right back to the android is starting screen. It doesn't seem to be a boot loop since it finishes the boot sequence. My biggest problem is not being able to access recovery because of the black screen which apparently is happening to some people with TWRP. I tried to go through adb but since my tablet isn't done installing, it doesn't have the drivers to run adb. Is my tablet toast? bricked?
edit: apologies for the title. I must have deleted the text before posting.
agentkalaw said:
So I decided to try to flash Zombie-Pop today and everything went fine during installation but when the tablet started booting up it was stuck on "android is starting.." and it seems to load the apps. I knew it would take a bit of time to stabilize so I let it run but after 1 hour of it stuck there, I tried to reboot into recovery but I get a black screen and I can't access TWRP. It just boots right back to the android is starting screen. It doesn't seem to be a boot loop since it finishes the boot sequence. My biggest problem is not being able to access recovery because of the black screen which apparently is happening to some people with TWRP. I tried to go through adb but since my tablet isn't done installing, it doesn't have the drivers to run adb. Is my tablet toast? bricked?
edit: apologies for the title. I must have deleted the text before posting.
Click to expand...
Click to collapse
Which bootloader are you on?
How are you trying to boot to recovery?
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
I was in snapchat when all of a sudden my nexus 5x totally froze and rebooted (which is normal considering how much snapchat sucks.)
I saw the warning about my bootloader being unlocked which was normal and it went to the Google screen, where it sat for about 5 minutes. Normally in every previous bootloop I've had in the past, the boot animation just loops forever and ever. I force shut it off and tried booting it up again and this time on the Google screen the phone totally shut off and restarted showing me the warning about my bootloader. I tried the recovery, but got the same results. So, I went home and plugged it in thinking maybe that would help but it still was shutting off and rebooting. It never got to the boot animation. I had all the adb and fastboot drivers so I just decided to flash the factory image. It flashed fine, and sadly the problem was still there. I'm so stuck, I can't get into the recovery to do anything and there's only so much that you can do over fastboot. I've found that if I press the power button every couple seconds while the Google screen is still showing and it doesn't reboot but the Google logo won't leave for the boot animation.
Seriously guys, please just give me any of your ideas.
My father-in-law's S6 was rebooting right after the menu screen came up. After trying numerous things which wouldn't work (still had varying boot loops) like getting into the recovery mode and doing a factory wipe, I decided to use Odin and flash the base stock Android nougat on this (it had the one verizon security patch after that, so should be no issue doing this).
That went okay and it rebooted and got all the way to "Android is starting" which you see after a firmware upgrade. But I didn't realize the battery had run down through all this so it died at this stage. So it was taking a charge now, so let it charge overnight and give it another run.
Got up today, tried to start it...back to the boot loop. So I figured I'd flash stock again with Odin (can always get back to that mode).
It completes successfully and then after the reboot at about 32% jumps to "erasing" and then the boot loop again.
Got into recovery mode once and wiped cache (pointless at this point, but whatever) and did factory reset there, then boot to bootloader. Got all the way to the verizon screen...and then boot loop again.
Is this phone just done? The only thing I can consistently get to is Odin mode. I tried the stock reflash a couple more times and keep ending up in a boot loop and it doesn't even get past the "custom" screen now. And I can't even actually get it to shutdown for that matter. I can get to the battery pull mode but if I try to power off from there, I just get the black screen with the blue light.
And, to make matters even worse, now on restart, it brings up the blue system update screen for a second, then jumps over to the no command screen, sits there for a second, then reboots again. I think I've somehow managed to even blow the recovery menu but this has all been stock and never had any custom firmware or root.
Any help/suggestions would be greatly appreciated!