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?
Related
Hey everyone, I need help for my Xoom 3G MZ601, I just rooted it and flashed EOS' rom and I'm stuck at bootanimation. I'm new to rooting and flashing custom roms for tablets, its different in phones.
When you say you are stuck, what have you tried to do? Have you tried to get back into your custom recovery? If you can, you could try to reflash your rom and gapps after wiping cache and dalvik cache. You would have your system wiped when you unlocked, but you could wipe again before reflashing...that might help.
Yes, I wiped everything, I did this 5 times and the same thing happens, stuck in bootanim.
okantomi said:
When you say you are stuck, what have you tried to do? Have you tried to get back into your custom recovery? If you can, you could try to reflash your rom and gapps after wiping cache and dalvik cache. You would have your system wiped when you unlocked, but you could wipe again before reflashing...that might help.
Click to expand...
Click to collapse
1. Do you have a backup of your stock rom? if you have a backup and recovery works you should be able to recover your stock system and everything will be allright.
2. If you don't have a backup enter this site motodev site (i can't post any links) download correct firmware for your device and flash every part of downloaded rom via fastboot.
I hope it will help you
It seems like your recovery img is the culprit, try downloading eos with goomanager..
try; adb reboot bootloader
fastboot flash recovery eos-recovery-r6.img http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6-softkeys.img or http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
adb reboot recovery
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Me too bro....
Jur13n said:
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Click to expand...
Click to collapse
Yeah Bro I have this exact problem, except i made a backup and my wifi is working fine now. One thing tho i cannot connect to google servers and when i boot up it says inconsistent UID's device may not work properly format your data partition(formatted it and yah nothing)
cated resionit
Jur13n said:
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Click to expand...
Click to collapse
For no-wifi problem try to flash the rom from page 9 in repack thread. Work for me.
Okay so I was trying to unroot my wifes phone and was told just to reflash the existing rom again. So after looking for instructions, I did a factory reset and wiped the cache, dalvik and system. I then tried to flash the 4.4.4 image again and it fails immediately.
So now there's no system on the phone and I have no way of flashing it. Can anyone suggest what I can do now?
To flash a stock ROM, you need to do it in fastboot mode. Which model do you have?
5After installation of the image i when to the recovery to check if everything went well and after it i wipe cache and dalvik then restart system. Now is looping into recovery. Any help TIA.
EDIT: tried backing up in recovery and restore its still going back to recovery. Also tried flashing 3.0.1 still the problem persist.
EDIT: also if i dirty flash sultans rom will i be able to enter? I havent able to back up anything :/
I just want to start by saying that I know how to recover my phone from this but I do not understand why this is happening. I just want to flash back the official rom and then install twrp and do a "factory reset" but after wiping with TWRP my phone gets stuck in bootloop. Am I doing something wrong?
drgx96 said:
I just want to start by saying that I know how to recover my phone from this but I do not understand why this is happening. I just want to flash back the official rom and then install twrp and do a "factory reset" but after wiping with TWRP my phone gets stuck in bootloop. Am I doing something wrong?
Click to expand...
Click to collapse
In TWRP you did 'factory reset' there isn't that option so which partitions did you formated? If you formated system, then is no more OS on your phone so what you trying to turn? xD If you want flash stock then use newest Odin 3.12.7 and learn some guide how to flash stock depend from which version (f.e. 7.x) you're coming. The guides are on that forum.
rifek4 said:
In TWRP you did 'factory reset' there isn't that option so which partitions did you formated? If you formated system, then is no more OS on your phone so what you trying to turn? xD If you want flash stock then use newest Odin 3.12.7 and learn some guide how to flash stock depend from which version (f.e. 7.x) you're coming. The guides are on that forum.
Click to expand...
Click to collapse
It says in the title which partitions I formated (date, cache, dalvik). I know how to flash stock. I will explain again the exact steps I did:
1. Flashed official rom using Odin after having a custom one.
2. I started the phone to check that the rom works.
3. I flashed TWRP 3.1.1 using odin.
4.Wanted to "factory reset" using TWRP, so I wiped cache, dalvik and data partitions.
5.The phone starts in bootloop.
It looks like TWRP doesn't wipe the partitions as is should.
Is not possible to TWRP didn't wiped right partitions. Why you wanted to factory reset if you flashed stock and you got factory settings? Flash stock with Odin again...
You need flash latest SuperSU zip in TWRP to fix the bootloop issue
forumber2 said:
You need flash latest SuperSU zip in TWRP to fix the bootloop issue
Click to expand...
Click to collapse
Maybe that. Personally I never flashed stock in S6 xD
You have to flash the SU Binary after flashing TWRP, else you will face a bootloop
Magisk. No "SuperSU". Then always will be it resolve if be only "Flashed TWRP". (Odin versions doesn't be affect of a bootlops with a 5secs~)
i flashed twrp now stuck in bootloop, not sure how to flash super su now?
fiorezy said:
You have to flash the SU Binary after flashing TWRP, else you will face a bootloop
Click to expand...
Click to collapse
Problem can also be solved after flashing the latest version of Magisk.