I've got a Moto G (1.gen) XT1032 that I'm using temporarily while waiting for repair parts for my Nexus 5.
I managed to install Android 5.1 GPe version on the phone, and the boot sequence show it's unlocked (open padlock image). Everything kinda works fine, except I want to root the phone.
So I boot into recovery mode, I get the list of options, go down to "recovery", then up, and after a moment I now get the famous red triangle. I have searched a lot and it seems it's quite common to have this with a "no command" text, but I have no text or anything, just the dead android image. From here I've tried all the suggestions with holding up+down and hitting power, in various combinations, but nothing works. The only result I get is the phone reboots into normal mode.
I've tried to flash both the openrecovery-twrp-2.8.1.0-xt1032.img, the moto-g-CWM-recovery.img and even the standard recovery.img, but they all just throw an error in fastboot and nothing happens.
I've tried for many days, gone though every post here and on other websites, but finally have to admit defeat. I'm at the end of the line, no more ideas. Anyone seen this before? What am I missing?
In my frustration I kept tapping up+down+power while on the dead-android-red-triangle page and suddenly the recovery menu appeared. Must be a timing issue somehow.
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!
Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
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.
Hi everybody !
I have messed up my phone while installing and removing different progs like twrp and magisk. Now i'm stuck in a loop and can't figure out how to get out of it,despite having read many posts here and there. Here is what i have done:
- My phone is a Mi A2
- When i push the power button, i see briefly the android one logo, then a first message saying "your device can't be checked for corruption, please lock the bootloader", followed by a second message saying "your device has loaded a different operating system". Then it boot again with same messages infinitely.
- So i opened the phone, shorted the test points and flashed the "jasmine_global_images_V10.0.13.0.PDIMIXM_9.0" with miflash tool, apparently successfully. (By the way, i have never been able to boot in edl mode when the battery was disconnected) But alas, when rebooting after successful flashing, the phone did nothing more or less than before flashing: still stuck in the same loop.
- Pushing power and volume up does nothing else than bringing the loop mentioned above.
- Pushing power and volume down bring up fastboot, but then the device is not recognized in device manager, and i can't figure out why, as i already used adb and fastboot commands sometime ago before i messed up the phone.
Thank you in advance for any advice, and keep care of yourself and everyone around you all over the world !
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