[DISCONTINUED][UNOFFICIAL] CM-12.1 [22 Nov 2016]

ggow · Nov 15, 2015

IMPORTANT NOTICE

:
As many of you know, the CM-12.1 branch will not be supported in the new LineageOS fork. And many of the new Google security patches are difficult and fiddly to back-port as they are now geared towards Marshmallow and Nougat. So as a result there will be no further updates to this rom.

Instead my focus will now be Fire Nexus ROM for this device.

Also looking at possible ways to get later android versions on the device. Will let you know if there is any progress later.

Thanks for all the support :good:

Code:

[COLOR="gray"]
/*
 * 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 the products you find here before flashing it!
 * YOU are choosing to make these modifications.
 */
[/COLOR]

Current Progress

updated: 25 Jan 2016

Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
- Saying something isn't working without proper explanation will not attract any attention.

Prerequisites for Installation
- If you have FireOS 5.0.1 then use Cyanogen Recovery or TWRP Image
- If you have FireOS >= 5.1.1 then use FlashFire 0.50

Fresh Installation from TWRP
- From your recovery perform a Factory Reset
- Flash the ROM File
- Flash Open Gapps - Use either micro, pico or nano
- Do NOT use stock gapps as there is not enough space on the /system partition
- Reboot and enjoy!

- Fresh Installation from FlashFire 0.50
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Accept defaults
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.

Upgrading from FlashFire 0.50
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Click the Red + again and choose 'Wipe'
- ONLY tick Dalvik and Cache.
- Press the big FLASH button.

Downloads
*** Please do NOT create any mirrors ***
- CM-12.1 for Amazon Fire 7" 2015 Tablet
- Open Gapps

Source Code
- Device Tree
- Kernel Source: Ford stock kernel, build number update-kindle-global-37.5.6.0_user_560177220

Thanks
- Cyanogenmod
- csolanol
- diegocr
- k4y0z

XDA:DevDB Information
CM-12.1 Amazon Fire 2015, ROM for the Amazon Fire

Contributors
ggow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: Cyanogenmod

Version Information
Status: Stable

Created 2015-11-15
Last Updated 2017-02-03

ggow · Nov 15, 2015

Release Notes / Changelog

2016-11-22
- Fix Xposed - Needs testing

2016-11-21
- November 2016 AOSP Security Patch Level
- Switch to using lastest FireOS 5.3.2 - update-kindle-global-37.5.6.0_user_560177220 binaries and boot.img
- Fix Video Recorder bug [Cannot connect to camera]
- Fix bug in OMX causing freeze of video

2016-10-21
- October 2016 AOSP Security Patch Level
- Fix x265 video playback - Thanks @jeromeof

2016-09-22
- September 2016 AOSP Security Patch Level

2016-08-10
- August 2016 AOSP Security Patch Level
- Fix audio lag issue in games - thanks @$ideWinder

2016-07-10
- July 2016 AOSP Security Patch Level
- Re-tested exFAT with 32GB Sandisk microsd card and seems to work fine.

2016-06-14
- June 2016 AOSP Security Patch Level
- Added CIFS Support (Instructions here)
- Switch to using lastest update-kindle-37.5.4.4_user_544271020 binaries and boot.img

2016-05-30
- Fix Swipe for stock keyboard
- Added back fix for screen rotation glitch

2016-05-28
- May 2016 AOSP Security Patch Level
- Fixed bug: No way back from USB Charge Only Mode

2016-04-20
- Updated CM Code

2016-04-11
- Fix sdcard write access

2016-04-06
- Updated CM Code
- 01 April 2016 AOSP Security Patch Level

2016-04-04
- Updated CM Code
- Prevent recovery been overwritten: Modify build system to prevent recovery-resource.dat and recovery-from-boot.p from been generated. This needs testing preferably by people with the ability to boot TWRP.
- Fixed failure to mount /system partition error due to change in build system

2016-03-30
- Enable Bluetooth Low Energy Support

2016-03-29
- Updated CM Code
- Switch to using lastest update-kindle-global-37.5.4.2_user_542168620 binaries and boot.img

2016-03-11
- Updated CM Code
- 01 March 2016 AOSP Security Patch Level
- Updated FlashFire Flashing instructions on OP

2016-02-29
2016-02-19
- Updated CM Code

2016-02-03
- Updated CM Code
- 01 February 2016 AOSP Security Patch Level

2016-01-26
2016-01-20
2016-01-12
- Updated CM Code

2016-01-04
- Enable WiFi Display

2015-12-30-R01
- Fixed bug where FlashFire will fail to go from FireOS -> CM

2015-12-30
- Thanks to @chetta for testing and prompt feedback
- Reverted use of Google's prebuilt WebView for now (Too many issues)
- Clean Flash via TWRP Re-tested
- Google App Tested
- YouTube and NetFlix Re-tested
- Upgrade via TWRP re-tested
- FlashFire FireOS -> CM re-tested

2015-12-29-PM
- Fixed issue with GAPPS and SuperSU been overwritten on upgrade of ROM

2015-12-29-AM
- Fixed bug when using FlashFire where Gapps would not be preserved
- Use Google's Prebuilt WebView
- Update WebView to version 48.0.2564.48
- Updated CM code on 2015-12-29
- Re-tested ROM upgrade via TWRP, CM recovery and FlashFire
- Fixed Flash failure going from FireOS 5.1.1 -> CM
- Re-tested FlashFire functionality going from FireOS 5.1.1 -> CM

2015-12-23
- Fixed ability to use FlashFire to go from FireOS_5.1.1 to CM-12.1
- BLOCK_BASED_OTA is now enabled

- Updated CM code on 2015-12-22

2015-12-16
- Fixed screen-off animation rotation orientation
- Updated CM code

2015-12-11
- Fixed permissions on /system/etc/install-recovery-2.sh
- Implement fix for Play Video - thanks @diegocr

2015-12-10-PM
- Switch to using update-kindle-full_ford-37.5.4.1_user_541112720 binaries and boot.img
- New version of the selinux_permissive.ko module - thanks @k4y0z
- Added /system/etc/install-recovery-2.sh with the same content as /system/bin/install-recovery.sh
- Fixed Built-In Root Access (Privacy Guard)

2015-12-10-AM
- Fix problem with install-recovery.sh been overwritten
- exFAT should now work (was broken in the previous build)
- init.d now initialises correctly
- Enabled built in Root Access
- NuPlayer should now work correctly
- Fixed Camera Support (HDR mode is not working and not supported)
- Fixed Video Recording
- General Video Support should be good now
- I tested Netflix and YouTube

2015-12-09
- Switch to using update-kindle-37.5.2.2_user_522054520 binaries and boot.img
- Add kernel module to switch selinux operational mode to permissive - thanks @k4y0z
- This means SuperSU is now not required and much faster boot times

- Add exfat support
- Enable init.d support - thanks @k4y0z
- Remove GPS configs
- Removed NFC configs
- Removed GPS, telephony and NFC permission files
- Add further properties to disable some SIM/RIL related stuff

2015-12-04
- Fixed USB OTG - thanks @csolanol and @diegocr
- Updated CM Code

2015-12-02
- Fixed Bluetooth Audio
- Updated CM Code

2015-12-01
- Fixed Bluetooth - thanks @diegocr
- Enable Multi-user (5)
- Updated CM Code

2015-11-22
- Enable MTP
- Enable OTG Support
- Add properties to declare device has no radio
- Added configuration item to build for BLOCK_BASED or not.
- BLOCK_BASED build currently not flashing due to symlink error
- Add further config for MTK Bluetooth
- Fixed build errors in lib_driver_cmd_mt66xx private static lib
- Clean up config for WIFI
- Added IPv6 support
- Fixed battery stats - thanks @csolanol for providing the required power_profile.xml

2015/11/16
- This version will boot standalone - no more tethered boot

2015/11/15
- Initial Release

ggow · Nov 15, 2015

Frequency Asked Questions

Question 1:
How do I adjust the keyboard sound level?

Question 2:
Why does the screen image seem stretched or distorted?

Question 3:
Why is my brightness slider not working?

Question 4:
When installing Google Play Games and Google Calendar I get error -505?

Question 5:
How do I use CIFS?

bobbob1016 · Nov 15, 2015

Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?

ggow · Nov 15, 2015

bobbob1016 said:
Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?

- You will have to fastboot each time
- It's all in the OP including the reasons why this is the case at the moment.
- It's not ideal - but thought I would share what I have so far
- I am looking into solutions for this now.

ggow · Nov 15, 2015

- Links are now up

bobbob1016 · Nov 15, 2015

ggow said:
- You will have to fastboot each time
- It's all in the OP including the reasons why this is the case at the moment.
- It's not ideal - but thought I would share what I have so far
- I am looking into solutions for this now.

Thanks for the hard work!

blueberry.sky · Nov 15, 2015

Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?

ggow · Nov 15, 2015

blueberry.sky said:
Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?

- Yes customise as much as you want - all will be retained.
- Your data and OS is stored on the /data and /system partition respectively
- The only thing you have to reload on a reboot through fastboot is the modified_boot.img which won't affect anything else.

csolanol · Nov 15, 2015

Awesome work @ggow!. @diegocr and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.
Thanks.

ggow · Nov 15, 2015

csolanol said:
Awesome work @ggow!. @diegocr and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.
Thanks.

Hi csolanol,

- I am in the process of updating my bibucket with the most recent changes
- Having trouble with bluetooth too.
- Wifi is working fine - I got it working like this:
- put this in your device tree
- then add this to your boardconfig.mk:

Code:

[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_WLAN_DEVICE := mediatek
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx
WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi"
WIFI_DRIVER_FW_PATH_STA:=STA
WIFI_DRIVER_FW_PATH_AP:=AP
WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]

- Then add this to your device.mk or equivalent

Code:

[INDENT]# wifi
PRODUCT_PACKAGES += \
	lib_driver_cmd_mtk[/INDENT]

- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error
- Instead copy it into your ROM after building.

- Hope this helps for now.

Awesomeslayerg · Nov 15, 2015

Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?

esmith818 · Nov 15, 2015

diegocr · Nov 15, 2015

ggow said:
Hi csolanol,

- I am in the process of updating my bibucket with the most recent changes
- Having trouble with bluetooth too.
- Wifi is working fine - I got it working like this:
- put this in your device tree
- then add this to your boardconfig.mk:

Code:

[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X BOARD_WPA_SUPPLICANT_DRIVER := NL80211 BOARD_HOSTAPD_DRIVER := NL80211 BOARD_WLAN_DEVICE := mediatek BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi" WIFI_DRIVER_FW_PATH_STA:=STA WIFI_DRIVER_FW_PATH_AP:=AP WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]

- Then add this to your device.mk or equivalent

Code:

[INDENT]# wifi PRODUCT_PACKAGES += \ lib_driver_cmd_mtk[/INDENT]

- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error
- Instead copy it into your ROM after building.

- Hope this helps for now.

Thanks, I will wait bitbucket update :good:

ggow · Nov 15, 2015

Awesomeslayerg said:
Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?

- Yes, that was me who said that but Amazon have changed things since then.
- On the HDX at the time they were not enforcing an selinux policy
- Now that Amazon are enforcing it cannot work in the same way at least for the moment until a workaround is found.

ggow · Nov 15, 2015

diegocr said:
Thanks, I will wait bitbucket update :good:

- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?

diegocr · Nov 15, 2015

ggow said:
- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?

no, only fastboot

ggow · Nov 15, 2015

diegocr said:
no, only fastboot

@csolanol and @diegocr

I have linked my Device Tree in the OP.

diegocr · Nov 15, 2015

ggow said:
@csolanol and @diegocr

I have linked my Device Tree in the OP.

Thanks a ton :good:

ggow · Nov 15, 2015

diegocr said:
Thanks a ton :good:

- I built my ROM without block based image generation
- This means you can extract the ROM and use the proprietary-files.txt with the extract-files.sh to re-generate the vendor tree

[DISCONTINUED][UNOFFICIAL] CM-12.1 [22 Nov 2016]

Recognized Developer

Attachments

Recognized Developer

Recognized Developer

Member

Recognized Developer

Recognized Developer

Member

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Member

Senior Member

Recognized Developer

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Similar threads

Top Liked Posts