Related
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Athanasius said:
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Click to expand...
Click to collapse
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
mypat said:
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
Click to expand...
Click to collapse
I can't tell you exactly what I did but it seems to be working... somehow a factory reset resulted in CM10.0 and gapps installed correctly... i'm still scratching my head but i'm happy enough.
hello,
I've installed Dhollmen kernel 20130722 on top of a Cyanogenmod 10.1.2.
The recovery is PhilZ Touch build 5.05.0 p5100 (CWM base 6.0.3.2).
All works fine, but my troubles begin when I try to password-encrypt the tablet (Settings -> Security -> Encrypt tablet).
The encryption process requires a restart, but then the Cyanogenmod logo appears and begins to roll and nothing else happens!
After two hours the logo still rolls.... at this point I did a reset and newly performed a clean install of CM 10.1.2 to get back a working tablet.
Note: if I install only CM 10.1.2 (that is, without changing his official kernel), the Encryption process completes successfully, so I wonder if the problems are related to the Dhollmen kernel.
However, since I truly love this kernel, I would like to use it, but I cannot renounce to encryption (for security reasons).
Any idea?
loboz said:
hello,
I've installed Dhollmen kernel 20130722 on top of a Cyanogenmod 10.1.2.
The recovery is PhilZ Touch build 5.05.0 p5100 (CWM base 6.0.3.2).
All works fine, but my troubles begin when I try to password-encrypt the tablet (Settings -> Security -> Encrypt tablet).
The encryption process requires a restart, but then the Cyanogenmod logo appears and begins to roll and nothing else happens!
After two hours the logo still rolls.... at this point I did a reset and newly performed a clean install of CM 10.1.2 to get back a working tablet.
Note: if I install only CM 10.1.2 (that is, without changing his official kernel), the Encryption process completes successfully, so I wonder if the problems are related to the Dhollmen kernel.
However, since I truly love this kernel, I would like to use it, but I cannot renounce to encryption (for security reasons).
Any idea?
Click to expand...
Click to collapse
Ask the dev :cyclops::cyclops::cyclops:
I apologize, the problem doesn’t concern Dhollmen kernel, I’ve tried to install another kernel (Blackhawk) over CM and the issue was always the same: bootloop when trying to encrypt.
It’s clear that I’m doing something wrong, but I don’t know what!
In doubt, I’ve tried to start from a “clean” state; from CWM 6.0.2.7:
1. Format “/data/” and “/data/media/”
2. Format “/cache/”
3. Format “/preload/”
4. Format “/system/”
5. Flashed CM 10.1.2 (from external sd)
6. Flashed google apps (from external sd)
7. Flashed kernel (from external sd)
When I restart the tablet all seems to work fine, but when I try to encrypt… bootloop!
I’ve tried to connect the tablet to the PC to verify if logcat can help, but the device wasn’t detected at all...
At this point I’ve tried some variants (I’m desperate, I know ):
- I did a prudential reboot into CM after flashing it, and before flashing the new kernel.
- I’ve flashed CM, encrypted the tablet (encryption is successful with original CM kernel), and only after encryption I’ve tried to flash the new kernel.
- I’ve tried with: CM 10.1, 10.1.2 and 10.1.3rc2
… but the result is always… bootloop.
Any idea? What am I missing?
EDIT: I've installed a nightly version of CM 10.2, then Dhollmen custom kernel.
Encryption process ended successfully.
As suggested by tuxafgmur, there was some incompatibilities between CM 10.1 and his kernel, that can be solved only upgrading to CM 10.2.
I'm on CM10.2 M1 that just updated. I have the latest Gapps as I flashed everything fresh through TWRP. However, when I reboot or turn my phone off I get hung up on my Unlocked Bootloader screen. Nothing happens. I have to jump into recovery, wipe user data, then the phone will turn on as normal.
Not sure what the problem is but it's frustrating enough that I may jump back to cm 10.1.3
Megasoma said:
I'm on CM10.2 M1 that just updated. I have the latest Gapps as I flashed everything fresh through TWRP. However, when I reboot or turn my phone off I get hung up on my Unlocked Bootloader screen. Nothing happens. I have to jump into recovery, wipe user data, then the phone will turn on as normal.
Not sure what the problem is but it's frustrating enough that I may jump back to cm 10.1.3
Click to expand...
Click to collapse
make sure you have the latest version of twrp installed. the latest version has the fixed selinux support.
bweN diorD said:
make sure you have the latest version of twrp installed. the latest version has the fixed selinux support.
Click to expand...
Click to collapse
I originally had the latest CWM installed but I wasn't able to get it to load through that at all. Sideload wasn't working initially. I had to wipe all data, rom, user data etc. and sideload by installing the latest TWRP the first time this happened when upgrading from 10.1.3 to 10.2 M1
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
Very exited, good job
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)
coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk
unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!
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