Fix Bootloop when flashing custom rom - Moto G Stylus (Moto G Pro) Questions & Answers

Whenever I flash a custom rom for this phone with TWRP, I get a Bootloop. I'm wiping all data and I switch partitions so that it flashes on partition A, but the issue still persists. Any solutions?

Related

[Q] Moto G Stuck in CM12 Boot Loop

My Moto G, model XT1032 is stuck in a CM12 bootloop. I can boot into fastboot mode and ClockWorkMod Recovery.
So far I have tried re-flashing the CM12 ROM with no success, I have downloaded the original firmware and tried to flash that but I get a "Preflash Validation Failed" error, my phone won't show up on RSD, and I have tried wiping the phone to it's factory setting.
None of these worked and I am out of ideas. Are there any other options to try?
Thanks.
Did you ever have the GPE ROM on your phone? Does your data partition uses f2fs?
If you are getting the validation error when flashing motoboot.img, that is because your current bootloader is newer than the bootloader you are trying to flash.
Hi, I'm fairly certain I had the GPE ROM on it. It was what it came shipped with, that is all I know. As for the data partition I am unsure of the format of it, how would I go about finding this information?
Thanks.
If it has the GPE ROM, it would not use f2fs for data. Do you have twrp on it? If you do, boot into twrp, advanced wipe, and check partition info.
I do not have twrp, I have ClockWorkMod. How do I check the partition on this?
In CWM, go to wipe & format options, custom format options, toggle f2fs<->ext4 migration. Then wipe data, cache, Dalvik, and reboot.
I don't have those options on my CWM, All I have is Reboot, Install Zip, Wipe Data/Factory Reset, Wipe Cache Partition, Backup and Restore, Mounts and storage and advanced. I am using version 6.0.4.6 of CWM.
Install the latest version of Philz Touch for your phone.
Okay, I did that and now my device hangs at the Motorola Bootloader Unlocked Warning screen. Should I flash a new ROM such as CM or try again with the motoboot?
I would do a full wipe and re-install to see what happens.
It's just gone back into the CM boot loop where it hangs at the pulsing CM logo. Should I try a different version of CM that is more stable?
RyanVadera said:
It's just gone back into the CM boot loop where it hangs at the pulsing CM logo. Should I try a different version of CM that is more stable?
Click to expand...
Click to collapse
I'm running the latest CM12 on my xt1032 with no problem.
You may need to flash back to stock 4.4.4, re-install Philz, and them CM12.
The partition layout on the GPE ROM is different than the partition layout on the stock.
Do you know where I can find the stock 4.4.4 file? I can't seem to locate one?
Try here: http://motofirmware.center/files/category/26-falcon/
Thanks, I got 4.4.2 running fine. Any advice on how to avoid getting stuck in another bootloop when I try to re-flash CM12?
Install the latest Philz, create a backup, then flash a ROM of your choice. To be safe, do a full wipe, including system, but not internal storage, before and after the ROM was been flashed.
Okay, Thanks for all your help.
So it all worked? I hope it did.
I'm afraid to say it did not work, It just went back into the boot loop.
How about flashing stock 4.4.4 or ota to the latest stock before flashing cm.
Are you flashing the cm for your phone?

Stuck in hard bootloop

Hi there,
I was running CM 12.1 very smooth on my XT897 4G with f2f filesystem on cache about half a year. After rebooting I was stuck in a bootloop. The phone freezes during bootlogo and reboots again. Wiping Dalvik and reflashed CM 12.1 leads to no success. So I successfully flashed
asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml
Via RSD 6.1.6. But the same error appears, the only difference is the bootlogo.
TWRP can't mount the partitions I tried every possible version of it. I'm able to flash fastboot and enter recovery.
Is there anything I can do to get my loved modded phone back? :crying:
I have the same issue what did you do to resolve it?
if iam right u need a backup zip and load it via the recovery.
if u not have your own try this: http://forum.xda-developers.com/showthread.php?t=2532620
did you try to reflash a cm rom?

[HELP]Stuck in bootload

Hello, after I flashed the "Ressurection remix 5.8.3" ROM my phone doesn`t get past the bootload. It shows the logo, the animation and a white rectangle. I guess this happened because I hurried and flashed the rom without making a wipe. I have TWRP recovery mode on my phone and it's possible to get in it. Also, I tried to wipe dalvik/cache, but its the same.
I have the same problem. Wipe or without, same problem.
I solved this problem by flashing a stock android firmware with Odin.

Phone stuck in bootloop even after flashing stock rom!

Hello. My new phone got stolen. I currently have a phone named symphony W17 ( MT6572 ). I had flashed stock rom using sp flash tool, but its stuck in bootloop. I tried clearing data and dalvik cache from recovery but no luck, Its stuck in the bootloop. Please help me!
Most often we face a bootloop just after flashing a stock or custom ROM over an old one not having immediately cleared cache / data before a reboot. This might be a major factor behind the bootloop issue on your device.
xXx yYy said:
Most often we face a bootloop just after flashing a stock or custom ROM over an old one not having immediately cleared cache / data before a reboot. This might be a major factor behind the bootloop issue on your device.
Click to expand...
Click to collapse
But i cleared both cache and data and still its stuck in bootloop! Not just that I also did format whole flash using sp flash tool but the issue never goes. Please help me

So I flashed a stock rom with twrp but now it only boots into twrp

It gives Ana error in red saying android rescue party trigger
Is also says the reported problem is
‘—reason=set_policy_failed:/data/adb
I get this sometimes when working on my ROMs. I just format data (full format, not wipe) and reboot to recovery to see if it's fixed. If not I flash ROM again.
Honestly I don't know what causes it so if you don't want to lose your data try flashing your ROM again and rebooting to recovery without booting to system and without wiping or formatting data. Hopefully it works for you.

Categories

Resources