Database Info

Soft brick downgrade CM12.1 to KitKat

Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!

I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.

Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?

I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.

vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?

FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!

Problem while flashing a new ROM

My phone is rooted. I have CM recovery installed. I am trying to flash a ROM but the installation is failing at 47%. It shows this message "Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and restarts the phone. When I try to wipe data or wipe media from recovery it restarts the phone. Even if I try to install from emulated storage it restarts the phone. I think there is something wrong with the storage. Can anyone help?

Karthikprabhu22 said:
My phone is rooted. I have CM recovery installed. I am trying to flash a ROM but the installation is failing at 47%. It shows this message "Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and restarts the phone. When I try to wipe data or wipe media from recovery it restarts the phone. Even if I try to install from emulated storage it restarts the phone. I think there is something wrong with the storage. Can anyone help?
Click to expand...
Click to collapse
Hi, are you on latest version of CWM corresponding to your phone model ? (let us know what phone model too )
Have you tried to flash and try with TWRP's latest version for your model ? (what's model, once again...)
What rom are you trying to flash (brand and build) ? Is your bootloader up to date ?
Not easy to help you without some precise informations...

satanas17 said:
Hi, are you on the latest version of CWM corresponding to your phone model? (let us know what phone model too )
Have you tried to flash and try with TWRP's latest version for your model? (what's model, once again...)
What ROM are you trying to flash (brand and build)? Is your bootloader up to date?
Not easy to help you without some precise information...
Click to expand...
Click to collapse
I had TWRP earlier. But it suddenly stopped working. I tried to reflash it didn't work. Then I tried CWM which was flashed successfully but was freezing. Currently, I have the latest recovery by CyanogenMod. It works fine.
My phone is Moto G XT-1033 (falcon).
I haven't updated my bootloader. I will try doing it.
Thank you

I am facing same problem in twrp recovery but now everything working fine after flashing stock recovery and twrp again

Tjsdj said:
I am facing same problem in twrp recovery but now everything working fine after flashing stock recovery and twrp again
Click to expand...
Click to collapse
:good:

[SOLVED ]"Patching system image unconditionally..." - can't install CM at all.

[SOLVED ]"Patching system image unconditionally..." - can't install CM at all.
my device (moto G (falcon) XT1032) is a GPE device.
in the last 2 days i tried to install CM 13 on my device.
i tried 3 different recoveries** - CWM, TWRP and CM recovery - to install cm-13.0-20160206-NIGHTLY-falcon (and yes, i checked before flashing, the SHA1).
in all those tryouts i always get into the sentence in the headline - Patching system image unconditionally... - and it just stays there forever.
one time i waited 40 minutes, and it still stayed on this message, and do nothing.
every time before flashing the rom, i wiped the device (dalvik cache, cache, system, Data).
i also try to flash the latest snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon) because i thought maybe there is a problem with the latest nightly.
i still stuck in the same stage(Patching system image unconditionally...).
i also try to flash stock rom 4.4.4 from motorola (from here: http://goo.gl/xAomMi) which succeeded, and then wipe device(factory reset and wipe dalvik cache, cache, system, Data) and install again cm-13.0-20160206-NIGHTLY-falcon, and it also didn't work.
i'm still get into the same message and stay there forever.
thanks for any help
** EDIT: http://forum.xda-developers.com/showpost.php?p=65237469&postcount=3

papandreoos said:
my device (moto G (falcon) XT1032) is a GPE device.
in the last 2 days i tried to install CM 13 on my device.
i tried 3 different recoveries - CWM, TWRP and CM recovery - to install cm-13.0-20160206-NIGHTLY-falcon (and yes, i checked before flashing, the SHA1).
in all those tryouts i always get into the sentence in the headline - Patching system image unconditionally... - and it just stays there forever.
one time i waited 40 minutes, and it still stayed on this message, and do nothing.
every time before flashing the rom, i wiped the device (dalvik cache, cache, system, Data).
i also try to flash the latest snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon) because i thought maybe there is a problem with the latest nightly.
i still stuck in the same stage(Patching system image unconditionally...).
i also try to flash stock rom 4.4.4 from motorola (from here: http://goo.gl/xAomMi) which succeeded, and then wipe device(factory reset and wipe dalvik cache, cache, system, Data) and install again cm-13.0-20160206-NIGHTLY-falcon, and it also didn't work.
i'm still get into the same message and stay there forever.
thanks for any help
Click to expand...
Click to collapse
Use Philz recovery and make sure you unlocked boot loader cleanly, if this Doesn't help try to flash some other ROM.
Best Of Luck

i also used philz_touch_6.58.7-falcon recovery.
still i got into the same problem i described in my first post.
p.s.
i forgot to mention this recovery in my first post, but after you suggested it, i remembered i used it already.

papandreoos said:
i also used philz_touch_6.58.7-falcon recovery.
still i got into the same problem i described in my first post.
p.s.
i forgot to mention this recovery in my first post, but after you suggested it, i remembered i used it already.
Click to expand...
Click to collapse
Try installing some other ROM.

[email protected] said:
Try installing some other ROM.
Click to expand...
Click to collapse
do you have a suggestion for good ROM (everything works) for moto g (xt1032), which has marshmallow in it?

papandreoos said:
do you have a suggestion for good ROM (everything works) for moto g (xt1032), which has marshmallow in it?
Click to expand...
Click to collapse
May be this helps
http://forum.xda-developers.com/showthread.php?t=3284323
Or
http://forum.xda-developers.com/showthread.php?t=3250449
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
If you can't install this flash stock and check if you can flash any Zip (try SuperSU zip in my word) if this ain't successful try to type unlock boot loader commands again.
Best of luck.

[email protected] said:
May be this helps
http://forum.xda-developers.com/showthread.php?t=3284323
Or
http://forum.xda-developers.com/showthread.php?t=3250449
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
If you can't install this flash stock and check if you can flash any Zip (try SuperSU zip in my word) if this ain't successful try to type unlock boot loader commands again.
Best of luck.
Click to expand...
Click to collapse
i tried now the AOSP rom in one of your links.
i wiped cache, dalvik cache, system and data and then continue to install the rom, but again it stuck in the same line as before and does nothing.

papandreoos said:
i tried now the AOSP rom in one of your links.
i wiped cache, dalvik cache, system and data and then continue to install the rom, but again it stuck in the same line as before and does nothing.
Click to expand...
Click to collapse
Flash back to stock and try to flash supersu zip from here if this doesn't work the problem must be while unlocking bootloader ,anyways was bootloader unlocked normally or you had any problems ?
https://download.chainfire.eu/696/SuperSU/
Flash via fast boot not some other flash able Zip
Best of luck.

[email protected] said:
Flash back to stock and try to flash supersu zip from here if this doesn't work the problem must be while unlocking bootloader ,anyways was bootloader unlocked normally or you had any problems ?
https://download.chainfire.eu/696/SuperSU/
Flash via fast boot not some other flash able Zip
Best of luck.
Click to expand...
Click to collapse
my bootloader is unlocked already.
before i tried to flash CM couple of days ago, i follow steps from CM wiki, and part of them is to unlock the bootloader.
here are the orders i followed(although it's for a different device (moto g 4g)), it worked great:
https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine#Unlocking_the_device
if i get into fastboot mode (volume down + power) it tells me in yellow line: Device is UNLOCKED. Status Code: 3.
i also have root access.

papandreoos said:
my bootloader is unlocked already.
before i tried to flash CM couple of days ago, i follow steps from CM wiki, and part of them is to unlock the bootloader.
here are the orders i followed(although it's for a different device (moto g 4g)), it worked great:
https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine#Unlocking_the_device
if i get into fastboot mode (volume down + power) it tells me in yellow line: Device is UNLOCKED. Status Code: 3.
i also have root access.
Click to expand...
Click to collapse
The metod sound the same...........Have you tried to flash stock ROM via Fast boot again?

[email protected] said:
The metod sound the same...........Have you tried to flash stock ROM via Fast boot again?
Click to expand...
Click to collapse
i forgot to mention that after every failure of flashing, i always get back to lollipop 5.1 GPE version with this helpfull tool:
http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
so everything is OK in my phone.
i'm just frustrated i can't install newer OS.

papandreoos said:
i forgot to mention that after every failure of flashing, i always get back to lollipop 5.1 GPE version with this helpfull tool:
http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
so everything is OK in my phone.
i'm just frustrated i can't install newer OS.
Click to expand...
Click to collapse
Try to flash KitKat for a while then flash CM 11 then any CM 12 then CM 13 I have have an similar error, whenever I try to flash another ROM the data partition doesn't format and then I have to do is to flash KitKat Stock then CM 11 then CM 12 then CM 13 .
Best Of Luck this should work.
---------- Post added at 08:25 AM ---------- Previous post was at 08:16 AM ----------
The tool isn't a good Idea I use to make an bat file and not customized a bit file of firmware if you don't know what it is I will give it to you .

Here , download the untouched version and flash via Fast boot if not completed find KitKat version :-
http://www.gimmickmag.com/restore-moto-g-xt1032-xt1033-xt1034-back-stock-firmware/
If you can't find there wait for FileFactory server to come up again it has all firmwares

[email protected] said:
Here , download the untouched version and flash via Fast boot if not completed find KitKat version :-
http://www.gimmickmag.com/restore-moto-g-xt1032-xt1033-xt1034-back-stock-firmware/
If you can't find there wait for FileFactory server to come up again it has all firmwares
Click to expand...
Click to collapse
i flashed 4.4.4 stock from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
i used the untouched version:
Retail EU 4.4.4 Stock ROM (Untouched) (457mb)
https://docs.google.com/uc?id=0B6RNTe4ygItBVFlwN2pqWmV1VXc&export=download
so far it's working.
i boot into the stock and it's 4.4.4.
the screen is flickering but it's stock 4.4.4.
now i'm gonna try flash this latest snapshot of CM11:
cm-11-20140504-SNAPSHOT-M6-falcon.zip
from here:
https://download.cyanogenmod.org/?device=falcon
i now into fastboot mode, installing TWRP 3.0.0.0:
fastboot flash recovery twrp-3.0.0.0-falcon.img
success!
get into recovery now.
sha1 verified.
copy CM11 into phone
i'm still on TWRP.
i now wipe data, cache, dalvik cache and system.
done.
now i'll try flash CM11
WOW!!!
after couple of seconds (maybe 30-40) it's done.
i reboot into CM11 without a problem (just the flickering screen again, but never mind. i'm not planing to stay in CM11).
the android version in latest CM11 is 4.4.2
now i'm gonna try to flash CM12
get into recovery again.
sha1 verified.
copy cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon into device.
wiping data, cache, dalvik cache and system again.
flashing!
not working
i again stuck in " "Patching system image unconditionally..." forever.
(going back to GPE 5.1)

Flash via Fast Boot it might be the problem.

[email protected] said:
Flash via Fast Boot it might be the problem.
Click to expand...
Click to collapse
you mean "adb sideload rom.zip"?
if yes, i already did that and it was stopped in 47 percent and sometime in 45 percent.
it stays there forever.

papandreoos said:
you mean "adb sideload rom.zip"?
if yes, i already did that and it was stopped in 47 percent and sometime in 45 percent.
it stays there forever.
Click to expand...
Click to collapse
No Flash Stock KitKat From Firmware via boot loader .

i think i'll pass.
i already flash kitkat and after that CM11 and it didn't help me to get into CM13.
i'm tired of flashing and restoring again and again.
thanks a lot for your help

As you wish...

I followed your steps too and i am exactly facing your problems, i am stuck in "patching system image unconditionally"...

No Response ,phone freeze on CM 13 ,CM12.1 Slim Bit, Resurrection Remix Help...

Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:

sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7

I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.

Try provide with a logcat, might be more useful in helping you.

No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?

sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.

Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz

[Help] Flashing 1st Gen Moto G (XT1031) Stock to CM12.1 or CM13, never boots

I posted this over on the CM forums, but wanted to post here as well for visibility.
I have multiple (read as 30+) 1st Gen Boost Moto Gs (XT1031) and this has been a problem on every.... single.... one...
Stock OS Info
Android Version: 4.4.2
Baseband version: MSM8626BP_1032.355.66.00R
Kernel version: 3.4.0-gc6fc9e1-00001-gf3bf628
System version: 175.44.1.falcon_cdma.Boost.en.US
Build number: KXB20.9-1.10-1.18-1.1
Bootloader: 41.1A
Recovery: twrp-2.8.7.0.-falcon_STOCK_NOTHEME
I've also tested with the Stock 4.4.4 and 5.1 Soak Test OS versions, both have the same results as well.
Additionally, this happens regardless of whether GAPPS is flashed or not.
I've tried the following, and ALWAYS results in an endless boot that just constantly stays on the CM Android head boot animation unless I flash & boot to CM11 first:
(Note: A TWRP Factory Reset is performed before flashing each new ROM)
CM11 - cm-11-20140504-SNAPSHOT-M6-falcon.zip
Stock -> CM11 = Boots and works fine
CM12.1 - cm-12.1-20151115-NIGHTLY-falcon.zip
Stock -> CM12.1 = Endless Boot
Stock -> CM11 (without booting to OS) -> CM12.1 = Endless Boot
Stock -> CM11 (Booted once) -> CM12.1 = Boots and works fine
CM13 (all nightly versions)
Stock -> CM13 = Endless Boot
Stock -> CM11 (without booting to OS) -> CM13 = Endless boot
Stock -> CM11 (Booted once) -> CM13 = Boots and works fine
So...The only way that I can get these to boot, is if I flash CM11 AND boot into it once and THEN flash CM12.1/CM13.
What is it about the first boot of CM11 that makes CM12.1 and CM13 work? any why doesn't direct from Stock -> CM12.1/CM13 work??? Is there a Kernel or something that gets installed when CM11 boots or something?
This is driving me insane. Please help me figure this out so that I can flash directly from Stock -> CM12.1/CM13.
---
Here is an example of exactly how to reproduce this problem. From the Stock ROM, do the following:
{Unlock Bootloader}
{Enable USB Debugging}
adb reboot bootloader
fastboot flash motoboot motoboot_41.1A.img
fastboot flash logo logo.bin
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
fastboot reboot
adb reboot recovery
adb shell twrp wipe factoryreset
adb push cm-12.1-20151115-NIGHTLY-falcon.zip /sdcard/
adb shell twrp install /sdcard/cm-12.1-20151115-NIGHTLY-falcon.zip
adb reboot
Click to expand...
Click to collapse
...Device never boots, and only stays on the CM logo animation.

I've just finished updating from Stock 5.1 (XT1033) to CM 13
Here's what I've done
1. Updated to the latest TWRP recovery
2. Copied the latest CM 13 nightly and Gapps (Pico) to internal storage
3. Reboot to recovery
4. Performed an advanced wipe. Wiping /system, /cache and /dalvik-cache
5. Performed a Factory Reset
6. Flashed both CM 13 and Gapps
7. Reboot
Wait for a few minutes.

mardobloom said:
I've just finished updating from Stock 5.1 (XT1033) to CM 13
Here's what I've done
1. Updated to the latest TWRP recovery
2. Copied the latest CM 13 nightly and Gapps (Pico) to internal storage
3. Reboot to recovery
4. Performed an advanced wipe. Wiping /system, /cache and /dalvik-cache
5. Performed a Factory Reset
6. Flashed both CM 13 and Gapps
7. Reboot
Wait for a few minutes.
Click to expand...
Click to collapse
Exact same steps on my XT1031, waited 6 hours, still didn't boot.
But if I flash CM11, boot to it once, then factory reset and install CM13... it will boot just fine. What magic does CM11 do that CM12.1/CM13 aren't doing?!
As a side note, the TRWP Factory Reset option wipes /system /cache and /dalvik-cache... so step #4 is redundant.... but I did it anyways.
Edit: I guess I skipped step #1 ... didn't realize that TWRP 3.0.2.0 was available for "falcon". I'll try this later tonight and see if it fixes the issue or not.
https://dl.twrp.me/falcon/

twig123 said:
As a side note, the TRWP Factory Reset option wipes /system /cache and /dalvik-cache... so step #4 is redundant.... but I did it anyways.
Click to expand...
Click to collapse
I followed the steps to perform a clean update from the official thread of CM 13 but when I tried to install the zip file it says that the data is incompatible and I needed to perform a factory reset. So that's why I've added that additional step so that there won't be any problems while installing CM 13. :laugh:
twig123 said:
Edit: I guess I skipped step #1 ... didn't realize that TWRP 3.0.2.0 was available for "falcon". I'll try this later tonight and see if it fixes the issue or not.
https://dl.twrp.me/falcon/
Click to expand...
Click to collapse
Okay try first with that one i.e. TWRP 3.02.0. If that doesn't work then maybe you can try this one from here :- http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 <------- This one worked fine for me i.e twrp-3.0.0.0_2-falcon following the above steps which I've mentioned.
P.S. I'm currently on baseband 1032.3116.98.00R - Retail Asia

mardobloom said:
I followed the steps to perform a clean update from the official thread of CM 13 but when I tried to install the zip file it says that the data is incompatible and I needed to perform a factory reset. So that's why I've added that additional step so that there won't be any problems while installing CM 13. :laugh:
Okay try first with that one i.e. TWRP 3.02.0. If that doesn't work then maybe you can try this one from here :- http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 <------- This one worked fine for me i.e twrp-3.0.0.0_2-falcon following the above steps which I've mentioned.
P.S. I'm currently on baseband 1032.3116.98.00R - Retail Asia
Click to expand...
Click to collapse
Nope. Flashed back to stock to test, updated to TWRP 3.0.2.0, attempted to flash to the latest CM13 nightly... still endless boot (waited 30min and it just stayed on the boot animation).
I'll try the recovery you mentioned later.... although, I also tried CM's own Nightly recovery... and the same thing happens with that as well.

I tried with the recovery you mentioned, and the same thing happens.
However, the story unfolds...
Recovery log when flashing from Stock-to-CM11:
http://pastebin.com/M0EGdLwu
Recovery log when flashing from Stock-to-CM12.1:
http://pastebin.com/HaderDW2
In the Stock-to-CM12.1 log.... it doesn't appear that anything is copied! if you look at the Stock-to-CM11 log, after the "Installing zip file '/sdcard/cm-11-20140504-SNAPSHOT-M6-falcon.zip'" line, it has a bunch of "minzip: Extracted file" lines. Comparing that to the Stock-to-CM12.1 long, none of those such lines exist in the log! I see the CM12.1 ROM file has a "system.new.dat" file, instead of all of the files extracted in the "system" folder, like the CM11 ROM has... not sure if that is causing the problem or not.
If none of the files are getting copied, that would explain why it never boots.... but this doesn't tell me how to fix it... or why CM11 doesn't have a problem, but CM12.1 and CM13 DO have a problem.

twig123 said:
I tried with the recovery you mentioned, and the same thing happens.
However, the story unfolds...
Recovery log when flashing from Stock-to-CM11:
http://pastebin.com/M0EGdLwu
Recovery log when flashing from Stock-to-CM12.1:
http://pastebin.com/HaderDW2
In the Stock-to-CM12.1 log.... it doesn't appear that anything is copied! if you look at the Stock-to-CM11 log, after the "Installing zip file '/sdcard/cm-11-20140504-SNAPSHOT-M6-falcon.zip'" line, it has a bunch of "minzip: Extracted file" lines. Comparing that to the Stock-to-CM12.1 long, none of those such lines exist in the log! I see the CM12.1 ROM file has a "system.new.dat" file, instead of all of the files extracted in the "system" folder, like the CM11 ROM has... not sure if that is causing the problem or not.
If none of the files are getting copied, that would explain why it never boots.... but this doesn't tell me how to fix it... or why CM11 doesn't have a problem, but CM12.1 and CM13 DO have a problem.
Click to expand...
Click to collapse
Backup first and try to restore your phone to stock firmware using the instructions over here. ----------> http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
And choose the firmware version which is related to your phone. They will be something like this:-
XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip
XT1031_FALCON_REPW_5.1_LPB23.13-51-R.10_cid6_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPB23.13-33.6_cid9_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPBS23.13-33.6-2_cid9_CFC.xml.zip

mardobloom said:
Backup first and try to restore your phone to stock firmware using the instructions over here. ----------> http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
And choose the firmware version which is related to your phone. They will be something like this:-
XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip
XT1031_FALCON_REPW_5.1_LPB23.13-51-R.10_cid6_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPB23.13-33.6_cid9_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPBS23.13-33.6-2_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already flashed to stock (XT1031_FALCON_BOOST_5.1 in this case).
The issue is coming FROM stock to CM12.1 or CM13 that is the problem, but Stock->CM11->CM12.1/CM13 works fine.
I don't want to have to install CM11 every time just to get a bootable rom... :-\

twig123 said:
Thanks for the suggestion, but I've already flashed to stock (XT1031_FALCON_BOOST_5.1 in this case).
The issue is coming FROM stock to CM12.1 or CM13 that is the problem, but Stock->CM11->CM12.1/CM13 works fine.
I don't want to have to install CM11 every time just to get a bootable rom... :-\
Click to expand...
Click to collapse
Save the recovery log while upgrading from CM11 to CM 12.1 to see what's the difference between that one which works and Stock to CM12.1/13

After playing with trying to flash CM13 directly for quite a long time.... I've come to the conclusions that something with the partition wipes don't actually work within the CM13 setup script, nor from Custom Recovery!
However, I found a workaround! Wiping the partitions from the Bootloader, instead of from Custom Recovery, allows a flash of CM13 to boot properly!
(The question still stands as to why CM11 doesn't have this issue, but CM12.1 and CM13 do...... but I have a workaround, so I'm not too worried about it)
I made a Windows Batch script to automate this flashing process, which I posted over on the CM Forum:
https://forum.cyanogenmod.org/topic...-to-cm121-or-cm13-never-boots/#comment-601380