Database Info

[Q] Moto G stuck in boot loop

This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.

manicresin said:
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
Click to expand...
Click to collapse
What did you use to flash? fastboot or mfastboot?

280
oversleeper said:
What did you use to flash? fastboot or mfastboot?
Click to expand...
Click to collapse
I used mfastboot.

http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:

oversleeper said:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
Click to expand...
Click to collapse
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s

On a whim I decided to try the retail firmware and was able to get the phone to boot to stock, but I tried to load TWRP again and it went back to the boot looping state.
I really don't understand what is wrong with this phone because this are for the company I work for and we have flash about a thousand this exact same way and have never ran into this issue.
I am going to try philz recovery to see if it cause the normal boot process to break and if not I try loading the a custom rom from there.

manicresin said:
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
Click to expand...
Click to collapse
Pretty normal, you got errors because you upgraded the bootloader to the last version, so you can't downgrade it. Now you can: try to flash the 4.4.2 stock boost version (without flashing gpt.bin and motoboot.img) or if doesn't work due to upgraded bootloader, just wait few days until the 4.4.4 firmware for boost will be downloadable. It's already realeased don't worry, look https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/100754/p/30,6720,9050
EDIT: It's a boost version, it's pretty different... You can't flash whatever you want so easily... search for some guide, I can't help about boost version.

The boost 4.4.2 stock firmware failed but the retail version worked, I'm try that with philz recovery to see if I can get CM 11 to work. If that fails ill wait for the 4.4.4 boost firmware.
Thanks for the help

I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
ClockWorkMod Recovery 6.0.5.0

CodyF86 said:
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
Click to expand...
Click to collapse
I downloaded your recovery image and flashed it, wiped everything and reset.
Installed cm-11-20140903-NIGHTLY-falcon from usbdisk, it said completed only after ~20 seconds but there where no errors.
Rebooted the device and the cyanogenmod animated boot logo was displayed.
The phone booted fine was is working, now to try and see if I can get my image loaded.
Thanks for the recommendation, I didn't think to try CWM since Philz recovery is based on it, but it failed to load CM 11.

[Q] Can't boot into TWRP after updating to 4.4.3

Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.

maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything.
Any help is appreciated.
Click to expand...
Click to collapse
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?

dottat said:
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
Click to expand...
Click to collapse
Worked like a charm. Thanks!

maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.

santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
Brain fart on my part. Such an obvious mistake. Thanks!

santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?

cntryby429 said:
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
Click to expand...
Click to collapse
Yeah I know that was possible in the past, to flash a rom using a recovery one time, without overwriting the current one.
As I've never seen any real need or purpose to doing that, I've never done it that way.
I do know that the other command is what should be used to actually overwrite and flash a new recovery for further use.
So I can't really answer as to whether that method still works or not.
Didn't sound like it did for him though.

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

magisk module than HALFBRİCK

ttps://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
OPENBETA3 I installed this module magiskden to my oneplus 6 device installed in rom. I installed the system backup from twrp (bluspark v9.85) before installing.
When I set up the module and restart it, the screen was opened and closed, it was not possible to enter magisk manager.
Twrpye and I said 'restore system'. When the Restore process was completed, I said reboot system and went into fastboot mode.
I can't boot to the phone and write twrp. Fastboot is entering mode every time I restart.
I need to save my data. I don't want to flash fastboot rum.

I think there is no way without msmtool. I had the same problem when I tried to restore backup.

Kollachi said:
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Click to expand...
Click to collapse
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?

This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img

Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.

DevrimSeven60 said:
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
Click to expand...
Click to collapse
Yes I had the same error

Kollachi said:
Yes I had the same error
Click to expand...
Click to collapse
what is the solution? Bluspark twrp flash I do not get error, but twrpye can not enter, although it is completed.

DevrimSeven60 said:
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
Click to expand...
Click to collapse
You can try flash the boot.img like paphonb said. I didn't knew that and used msmtool. But I saved my data before restoring in twrp so I didn't lose anything just a lil bit time

paphonb said:
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Click to expand...
Click to collapse
open beta 3 i have downloaded full rom zip. Is there an img I can use in zip?

stuck on boot loader after trying to install twrp

after updating to android q dp3 on my t mobile version of one plus 7 pro to get my bootloader unlocked i restarted into fast boot to install twrp and i followed multiple post of people doing it but i get the error msg below or it says the same thing but it says success. i even tried fastboot flash boot twrp.img. after doing it i restart and it goes right to fastboot and not twrp. Do i have to downgrade out of dp3 first? im stuck any help would be appreciated!
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.209s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.211s

I forgot to mentioned that it worked the very first time and i got into twrp following the video on here xda posted but i failed to flash a custom rom and it was stuck in the splash screen when i installed havoc os rom and i used msm tool to revert back to stock and start over now i cant get twrp re installed

bj8622 said:
I forgot to mentioned that it worked the very first time and i got into twrp following the video on here xda posted but i failed to flash a custom rom and it was stuck in the splash screen when i installed havoc os rom and i used msm tool to revert back to stock and start over now i cant get twrp re installed
Click to expand...
Click to collapse
you need atleast on oos 9.5.7 firmware to able flash twrp again

can i instALL TWRP if im on 9.5.11? right now im on the 9.5.1 downgrade from dp3

bj8622 said:
can i instALL TWRP if im on 9.5.11? right now im on the 9.5.1 downgrade from dp3
Click to expand...
Click to collapse
Yes, also 9.5.10 works

benny3 said:
Yes, also 9.5.10 works
Click to expand...
Click to collapse
What do you flash to get back to 9.5.10 or 9.5.11? Using the downgrade re-locked my bootloader.