Okay so, Im a noob at all this and this was my first attempt at unlocking the bootloader.
I followed a website and I tried unlocking the bootloader.
I thought I did it right.
So when the phone restarted, it went to the "Android is optimising" screen
I wasnt there when it happened but when i returned, there were all these popups saying everything crashed (clock, settings, ANDROID)
So i tried shutting it down and hoped that when i restarted it, it would do the optimising again and work
So i restarted, but as soon as the Motorola start screen finished ( the spinning globe thing) the whole phone would crash and would be stuck on a blank black screen.
I can still access the Fastboot screen thing by pressing the Volume down and Power buttons.
Is there anything i can do to fix it?
Please make it detailed or very simple because again, I AM A NOOB D:
PLEASE HELP ME D::crying::crying::crying:
ticanou mustered
You can do a factory reset from the fastboot screen (Recovery > Wipe data/Factory reset). I used theandroidsoul's "unlock-bootloader-motorola-moto-g" guide to unlock the bootloader (I can't post a link). Which one did you use?
Related
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.
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.
Hey guys,
Sorry if the answer to this found somewhere else, tried searching but foud nothing for my situation.
My buddy, who is a super basic user and was not attempting to do anything with his phone, has a G4 that suddenly stopped working and went into a boot loop.
We tried factory resetting it and it got about half way through the apps before stopping, going back into a boot loop and was unable to get back to the same point in the factory reset.
I tried flashing the ROM using LGUP to H811-20o and it said that it went successfully on LGUP as well as the phone itself, but after it rebooted it went back into a boot loop.
Now the boot loop goes faster but is still looping and we cannot get back into download mode to try again or potentially try a different ROM. It goes to the first screen of download mode with the 5 blue dots but doesn't get past that, I've removed the battery waited for a while in between attempts and still nothing.
We can get to the factory reset screen and click yes, it will then go to the green android guy with his cog wheels exposed but then immediately goes back into a boot loop.
Any help is appreciated, even if its just a confirmation of being SOL.
Hi
a helpful thread may be found here
https://forum.xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
Hello.
I won't go too deep into detail on how it ended up like this, but basically I messed around with flashing a custom rom, tried to factory reset, and my phone ended up stuck on the following reboot loop:
1 - "Warning: Bootloader Unlocked" screen appears, then the phone emits a short vibration.
2 - Phone goes on to "Erasing..." screen, displaying the Android fella with his belly open and his robot innards spinning.
3 - Phone screen goes black, then back to step one again.
Now I might have bricked my phone to death, but I still have access to some menus and options that lead me to think that *maybe* a fix is possible:
I still have access to the bootloader menu, even though half the commands lead to a reboot of the phone. I still have access, on some extent to the recovery menu (I get the "No Command" screen, but I can still bypass it and get to a screen with a few clickable options.
The options "Apply update from ADB" and "Apply update from SD card" give me a bit of hope.
I did try flashing the stock rom using adb-fastboot (RDSLite doesnt even recognize my device) but I got the "Preflash validation failed" error at the first step (flashing gpt.bin).
So what I'd like to know is if there's anything I could possibly do to unbrick my device and flash the stockrom again, or is my Moto G 2015 just good to be sold for spare parts ? Thanks in advance for your replies.
Have you seen this thread/link?
https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Also,"Recovery Mode" is a two action process to get past the Dead Robot,
https://wasconet.com/solution-moto-g-android-recovery-mode-no-command/
Did you save a working ROM before flashing new ROMs?
Thierry_Salmon said:
Hello.
I won't go too deep into detail on how it ended up like this, but basically I messed around with flashing a custom rom, tried to factory reset, and my phone ended up stuck on the following reboot loop:
1 - "Warning: Bootloader Unlocked" screen appears, then the phone emits a short vibration.
2 - Phone goes on to "Erasing..." screen, displaying the Android fella with his belly open and his robot innards spinning.
3 - Phone screen goes black, then back to step one again.
Now I might have bricked my phone to death, but I still have access to some menus and options that lead me to think that *maybe* a fix is possible:
I still have access to the bootloader menu, even though half the commands lead to a reboot of the phone. I still have access, on some extent to the recovery menu (I get the "No Command" screen, but I can still bypass it and get to a screen with a few clickable options.
The options "Apply update from ADB" and "Apply update from SD card" give me a bit of hope.
I did try flashing the stock rom using adb-fastboot (RDSLite doesnt even recognize my device) but I got the "Preflash validation failed" error at the first step (flashing gpt.bin).
So what I'd like to know is if there's anything I could possibly do to unbrick my device and flash the stockrom again, or is my Moto G 2015 just good to be sold for spare parts ? Thanks in advance for your replies.
Click to expand...
Click to collapse
Pixel stuck on "google" screen after screen & battery replacement (initial boot ok..)
Hi -
Pretty sure phone is bricked as I've tried most stuff I can think of. I replaced the battery & screen on my pixel, everything worked ok once glued back together, phone booted into android and I got as far as unlocking at the lock screen. Then the phone froze, rebooted and is now stuck on the google screen (before the G screen).
I cant get into recovery mode and device appears to be locked - I can see it in fastboot but most fastboot commands fail due to lock (and it wont unlock).
Anyone got any ideas of anything else I could try?
Thanks
marcus-w said:
Hi -
Pretty sure phone is bricked as I've tried most stuff I can think of. I replaced the battery & screen on my pixel, everything worked ok once glued back together, phone booted into android and I got as far as unlocking at the lock screen. Then the phone froze, rebooted and is now stuck on the google screen (before the G screen).
I cant get into recovery mode and device appears to be locked - I can see it in fastboot but most fastboot commands fail due to lock (and it wont unlock).
Anyone got any ideas of anything else I could try?
Thanks
Click to expand...
Click to collapse
Any luck? I'm in the same situation. Bought a used pixel on ebay and it powered on and booted in to Android successfully the first time, but then frozen, and I try to reboot it
then it just won't pass the "Google" screen, can choose recovery in fastboot but will also stuck at "Google" screen forever. Only thing seems to work in the fastboot is the bar code mode.