[ROM][OFFICIAL][condor] CyanogenMod 13 for Moto E 2014

Julian1307

Member
Dec 5, 2016
7
2
0
By data if you mean apps and appdata then you can just flash any working build directly . just wipe cache and dalvik cache. It won't delete your data.
Thank you !

There is apparently also another solution to make the current nightlys work (replace /system/lib/libcutils.so).
More information in the official cyanogenmod forum. I can not post the link unfortunately.
The thread title are "CM13 stuck in boot loop".
 
  • Like
Reactions: bira792 and Papdya

cosmicslice

Member
Jul 25, 2015
9
1
0
It was recommended here in the forum to flash build cm-13.0-20161108 or before.
However, I can not download this build anymore at the official CM Site.
Clean flash = wipe the device? A way without data loss would be great :)
You only had to go back 2 thread pages to find a link: download . cyanogenmod . org/get/jenkins/186355/cm-13.0-20161108-NIGHTLY-condor.zip
 

electrohippie

Member
Jun 23, 2016
16
13
3
Northern Parts
There is apparently also another solution to make the current nightlys work (replace /system/lib/libcutils.so).
More information in the official cyanogenmod forum. I can not post the link unfortunately.
The thread title are "CM13 stuck in boot loop".
I'm also not able to post the link, but I can confirm that the method works. I'm on the cm-13.0-20161204-NIGHTLY-condor.zip . Bootprocess took a bit longer than common but it's working.
 

ChavitoArg

Senior Member
Aug 13, 2011
1,250
656
0
I'm also not able to post the link, but I can confirm that the method works. I'm on the cm-13.0-20161204-NIGHTLY-condor.zip . Bootprocess took a bit longer than common but it's working.
I can double confirm this. Install the latest nightly + gapps then you can place the "libcutils.so" in his location with the twrp file manager. Make sure you mount system and chmod 755 file permissions.

Enviado desde mi Nexus 6P
 
  • Like
Reactions: Patufleon

squid2

Recognized Developer
Mar 9, 2015
1,722
10,971
0
Ontario
Thank you !

There is apparently also another solution to make the current nightlys work (replace /system/lib/libcutils.so).
More information in the official cyanogenmod forum. I can not post the link unfortunately.
The thread title are "CM13 stuck in boot loop".
Yes, that's my interim fix. Forum link: https://forum.cyanogenmod.org/topic/121580-cm13-stuck-in-boot-loop/?page=2
The same file will fix both otus and condor nightlies. Unfortunately, the modified libcutils breaks build of the ROM without a bunch of patches all over the tree. This is why the associated patch hasn't been merged. I'm looking for an alternative fix that doesn't cause build issues.
 

govind1233

Senior Member
Aug 17, 2016
978
1,018
103
New Delhi

Julian1307

Member
Dec 5, 2016
7
2
0
Now I have only the following small problem.
My micro SD card is accidentally ejected unexpectedly. After a restart, the SD card is again integrated.
The sd card is integrated as adopted storage. Has anyone the same problem or a solution?
 

Strobelite

Member
Jul 12, 2014
39
4
0
You need to flash cm 12 first before trying cm 13. Because file structure changed to ART.
Instead of updating stock ROM to Lollipop, flash cm 12 then flash cm13.
I flashed CM13 directly over stock, and my phone works, except that every once in a while, I'll take it out of my pocket and it'll be turned off and I will have to turn it on, or sometimes it will freeze and reboot while I'm using it. This doesn't happen often, though, and I'm not sure if it's even related to me flashing CM13 directly over stock. I am on the 11/08 nightly.
@squid2 So what is the recommended way to replace the libcutils.so included w/ the newer images with the "fixed" one?


If anyone is looking for the 11/08 nightly, link is above
 
Last edited:

amit.tiger12

Senior Member
Jul 15, 2015
623
444
83
Mumbai
I flashed CM13 directly over stock, and my phone works, except that every once in a while, I'll take it out of my pocket and it'll be turned off and I will have to turn it on, or sometimes it will freeze and reboot while I'm using it. This doesn't happen often, though, and I'm not sure if it's even related to me flashing CM13 directly over stock.
In my case, flashing directly on kitkat not worked, may be because it was too early build.
Maybe it's power key button problem. Moto e power key button have problem in most devices. Is hardware problem no solution for it need service center (but they also can't fix it).
In settings you can change to volume key for unlocking phone.

While removing from pocket don't hold device from side (this position you might be pressing power button) hold device from screen and back panel. Try this.
 
Last edited:
  • Like
Reactions: TigerKing00

bysch

Member
Nov 3, 2012
8
3
0
11 Dec build boot and works on my xt1025 (msim)!!!

Anyone tried new build? 11 Dec build?
I do not have time yet to test all things, but seems that all works fine:
- msim ok (receiving and making calls);
- sms ok;
- sd with 16 GB class 10 as internal ok: now i have 17 GB free, less than 1 GB used by the system (no one app and no gapps yet);
- wifi ok;
- 3g ok;
- batery seems ok till now; under test;
The first boot take a long time, seems to be in bootloop, but this time finally works!!!

bySch
from Brasil.
 
Last edited: