[ROM][OTA][STABLE] CyanogenMod 12.1.1

BlueFlame4

Retired Recognized Developer
Mar 10, 2011
1,864
4,398
0
29
Dresden, Germany

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1(LP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include 
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! 
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Unofficial build of CyanogenMod 12.1 (Android 5.1.1) for the P8000

Working:
  • Everything! :highfive:

  • It boots and is hardware accelerated!
  • WiFi
  • Vibration
  • Audio
  • Rotation
  • Proximity Sensor
  • Bluetooth
  • Camera (Video and Photos!), thanks to @walter79
  • Ambient Light Sensor
  • External SD
  • RIL for SMS/Calls/Internet
  • GPS
  • MTP and Mass Storage mode (thanks, walter79!)
  • Audio over Bluetooth
  • Tethering
  • Enforcing SELinux
  • Fingerprint Scanner
  • FM Radio

Not working (yet):
If you get a notification saying updates are available it's sufficient to install the latest version.
Download:
OTAs:
http://download.cm.mkoas.de/OTAs/
Build 10:
http://download.cm.mkoas.de/cm-12.1-20160720-UNOFFICIAL-p8000.zip
Build 9:
http://download.cm.mkoas.de/cm-12.1-20160601-UNOFFICIAL-p8000.zip
Build 8.2:
http://download.cm.mkoas.de/cm-12.1-20160522-UNOFFICIAL-p8000.zip
Build 8:
http://download.cm.mkoas.de/cm-12.1-20160508-UNOFFICIAL-p8000.zip | mirror by @sellsky
Build 7.1:
http://download.cm.mkoas.de/cm-12.1-20160418-UNOFFICIAL-p8000.zip | nachfuellbar's mirror
Build 4:
http://d-h.st/nWtX Mirror, thanks to nachfuellbar: http://mkoas.de/cm-12.1-20160307-UNOFFICIAL-p8000.zip
Build 3:
http://d-h.st/yJbD
Build 2:
http://d-h.st/J1Cl
Build 1:
http://d-h.st/0roR

How to install:
It's usually a good idea to download the newest build version. Just install it via recovery. I tested it on CWM and TWRP but it should also work on other recoveries. You will also need gapps if you want to use Google services. I recommend stock OpenGApps - use the arm64 versions.

Supporters (in no particular order)



Sources:
Device Tree: https://github.com/visi0nary/android_device_elephone_p8000
Kernel: https://github.com/visi0nary/android_kernel_elephone_p8000


Thanks to:
@DerTeufel1980
@carliv
@Santhosh M
@walter79
@superdragonpt
@fire855
@valascus
@JulianXhokaxhiu for the OTA rest server!
ZOPO for releasing their sources!

Appendix:
If you want to mirror the files or port the ROM to another device, I encourage you to do so! Only please respect my work and give proper credits. Thank you!
 
Last edited:

alfredxyz

Senior Member
Aug 15, 2013
251
67
0
LE
Hi i could not flash cm with twrp and also not with cwm recovery does anybody get flashed cm successfully?
Edit:
I solved it! everytime i tryed to flash the zip i got the message :this package is for p8000 this is a k05ts_a
FIX:

1.Open the zip using WinRAR or 7ZIP. and decompress the package
2.Open the package and navigate to \META-INF\com\google\android
3.Open updater-script file in a text editor.
4.Change the two "P8000" entries with "k05ts_a"

before:
assert(getprop("ro.product.device") == "P8000" || getprop("ro.build.product") == "bacon" || abort("This package is for "P8000" devices; this is a "" + getprop("ro.product.device") + "".")

after:
assert(getprop("ro.product.device") == "k05ts_a" || getprop("ro.build.product") == "bacon" || abort("This package is for "k05ts_a" devices; this is a "" + getprop("ro.product.device") + "".")

5.Compress the folder back to zip.
6.Flash and enjoy
 
Last edited:

BlueFlame4

Retired Recognized Developer
Mar 10, 2011
1,864
4,398
0
29
Dresden, Germany
Hi i could not flash cm with twrp and also not with cwm recovery does anybody get flashed cm successfully?
Edit:
I solved it! everytime i tryed to flash the zip i got the message :this package is for p8000 this is a k05ts_a
FIX:

1.Open the zip using WinRAR or 7ZIP. and decompress the package
2.Open the package and navigate to \META-INF\com\google\android
3.Open updater-script file in a text editor.
4.Change the two "P8000" entries with "k05ts_a"

before:
assert(getprop("ro.product.device") == "P8000" || getprop("ro.build.product") == "bacon" || abort("This package is for "P8000" devices; this is a "" + getprop("ro.product.device") + "".")

after:
assert(getprop("ro.product.device") == "k05ts_a" || getprop("ro.build.product") == "bacon" || abort("This package is for "k05ts_a" devices; this is a "" + getprop("ro.product.device") + "".")

5.Compress the folder back to zip.
6.Flash and enjoy
Now that's becoming super weird! My early builds were for k05ts_a but rejected to be installed because they wanted p8000 as assertion. Looks like a different batch problem again, oh noes!
I am absolutely looking forward to this ROM. Thanks so much!

Will the ROM support device encryption?
Well for now I want to bring up all peripherals (current challenge is to fire up the camera) before adding features over stock. Of course Mediatek did a custom flashlight implementation which leads to a SystemUI crash when booting with camera enabled because the flashlight toggle can't find the flashlight pointer. Disabling the back camera works but then we obviously only can use the front cam which is not an option. Looks like I gotta hack kernel drivers...
 

El_Nino9

Senior Member
Dec 2, 2009
277
78
0
London
Now that's becoming super weird! My early builds were for k05ts_a but rejected to be installed because they wanted p8000 as assertion. Looks like a different batch problem again, oh noes!
i think its more of what rom they are coming from.
maybe a pre-req to be on latest stock before trying this rom?

surely that check is only there to prevent people flashing a rom not meant for their phone/model onto it? it can be removed and re-zipped for flashing without the check.

hats off for the great work @BlueFlame4.
hope elephone see this and actually help you out with the difficulties and provide you with free devices in the future LOL
 

BlueFlame4

Retired Recognized Developer
Mar 10, 2011
1,864
4,398
0
29
Dresden, Germany
hats off for the great work @BlueFlame4.
hope elephone see this and actually help you out with the difficulties and provide you with free devices in the future LOL
Thank you! :)

BTW Camera works now (front, back and flash) but video recording is still broken. I'll look into this later - next quest is RIL bringup ;)
 
Last edited:

adyana

Member
Jul 27, 2009
23
19
3
Jakarta
hi blueflame...

been lurking and use visi0nary's kernel since v1.2
subscribing this thread and will be also lurking here for ANY updates :)
really appreciate all the work you have done and many thanks for your effort and resources to have CM12 in this phone
 
  • Like
Reactions: BlueFlame4

BlueFlame4

Retired Recognized Developer
Mar 10, 2011
1,864
4,398
0
29
Dresden, Germany
Tank you!

I've read that for the Elephone Trunk is ou the CM13. Maybe is possible to implement that in the future.
Well, the Trunk uses a Qualcomm chipset which is relatively easy to handle even though it's still hard work to set up the device tree. Speaking of that my device tree is on Github so feel free to experiment with CM 13. I will do one thing after the other and get CM 12.1 running first before starting something new.

BTW thank you guys again for the donations! <3
 

BlueFlame4

Retired Recognized Developer
Mar 10, 2011
1,864
4,398
0
29
Dresden, Germany
Will use it as soon as mobile data works. Thanks for ur great work :)
Turns out this might be more work than expected but I'm making progress. The MUX daemon that coordinates the modems already fires up and initializes everything but somehow I still can't speak to it yet (i.e. Baseband is still unknown). Looks like a permission problem.

Fixed so far:
* Bluetooth
* Camera
* Long booting time is fixed
* Proximity Sensor

Unfortunately I had to make a change in the CM tree in order to get camera working so there's maybe a better way to do this. I'll look into this later though as it works for now. Gonna hit the sauna now with some friends and afterwards I don't have time until sunday so don't expect a release this week. Once RIL works, I'll push the build :)
 
Last edited:

PLSHELPIMANOOB

Senior Member
Mar 2, 2013
85
15
0
Mannheim
Gonna hit the sauna now with some friends and afterwards I don't have time until sunday so don't expect a release this week. Once RIL works, I'll push the build :)
Okay, wish u much fun :) Yeah no hurry , take ur time =) Until u get it to work I use the Nexus ROM with XPOSED :D But I´m already very excited for CM, mainly cuz of the theme Engine :)
 

Deepflex

Senior Member
Dec 11, 2014
560
1,730
0
Unknown
www.elephone.hk
Turns out this might be more work than expected but I'm making progress. The MUX daemon that coordinates the modems already fires up and initializes everything but somehow I still can't speak to it yet (i.e. Baseband is still unknown). Looks like a permission problem.

Fixed so far:
* Bluetooth
* Camera
* Long booting time is fixed

Unfortunately I had to make a change in the CM tree in order to get camera working so there's maybe a better way to do this. I'll look into this later though as it works for now. Gonna hit the sauna now with some friends and afterwards I don't have time until sunday so don't expect a release this week. Once RIL works, I'll push the build :)
Hello. Good job!
I'm working under cm12.1 to.. I don't have never long boot. First boot 2-3 min (2 on optimisation) very fast, small review of cm12.1 on p6000 pro. Will be better, if we cooperated with you.
http://www.youtube.com/watch?v=M_oN5QkfkXw
 
Last edited:

BlueFlame4

Retired Recognized Developer
Mar 10, 2011
1,864
4,398
0
29
Dresden, Germany
Hello. Good job!
I'm working under cm12.1 to.. I don't have never long boot. First boot 2-3 min (2 on optimisation) very fast, small review of cm12.1 on p6000 pro. Will be better, if we cooperated with you.
http://www.youtube.com/watch?v=M_oN5QkfkXw
Yeah, I forgot to a add a binary which basically lead to the long boot problem. Lessons learned, won't happen again ;) What is working on your build? Cooperation is always appreciated!
 

Deepflex

Senior Member
Dec 11, 2014
560
1,730
0
Unknown
www.elephone.hk
Yeah, I forgot to a add a binary which basically lead to the long boot problem. Lessons learned, won't happen again ;) What is working on your build? Cooperation is always appreciated!
Day ago i'm booted
Working:
led, vibrator, accelerometer, autorotation, wifi (fixed)
Now i'm going take logcats and modify a device tree :) My skype : rblmix1, if i fix something, i told you
 
Last edited: