[ROM] OFFICIAL CM12.1 KFire HD 7 (LP 5.1.x) [2015-06-24 ALPHA]

Search This thread

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,732
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 7"

*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***


BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848


CHECK KNOWN ISSUES BEFORE FLASHING. MAY NOT BE GOOD ENOUGH FOR DAILY USE.

Official nightly builds can be found here:
http://download.cyanogenmod.org/?device=tate

Download Google Apps for Android 5.1:
https://www.androidfilehost.com/?w=files&flid=25361
(Choose newest *-5.1-* file)

NOTES:
  • Older versions of TWRP will show a "mount failed error". This is safe to ignore.
  • First boot after a clean wipe will take a LONG time. Be patient.

KNOWN ISSUES:
Use XDA Bug Reporter

SCREEN SHOTS:
Use XDA Screenshots

XDA:DevDB Information
CM12.1 KFire HD 7 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD

Contributors
Hashcode
Source Code: http://www.github.com/CyanogenMod

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod

Version Information
Status: Alpha
Beta Release Date: 2015-06-24

Created 2014-12-27
Last Updated 2015-06-24
 

Attachments

  • device-2014-12-26-152952.jpg
    device-2014-12-26-152952.jpg
    58.1 KB · Views: 53,099
  • device-2014-12-26-153012.png
    device-2014-12-26-153012.png
    60.9 KB · Views: 52,451

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,732
Reserved

KERNEL UPDATES for Lollipop Android 5.0 / 5.1
  • Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
  • Combined defconfig setup to better support all HD models
  • Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
  • Picked IPV6 routing changes from Google's common 3.4 kernel
  • Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
 
Last edited:

xWolf13

Senior Member
Jul 6, 2012
1,387
843
Woke up from my nap and saw this! Amazing!!! Downloading now :D

Edit: I would like to point out that there will be a mount failed error in TWRP when flashing the build. Ignore the error and be patient. It'll flash! It took about 2-3 minutes.

Edit2: And it has booted! Approx time is 8 minutes. Be patient on your first boot guys!
 
Last edited:

Jrhoop

Senior Member
Dec 1, 2010
678
295
UK
Samsung Galaxy S22 Plus
Can confirm the 7/8 minute 1st boot. Must be to do with initialising ART?!
Anyway, now for a play and a few customisations.
Once again, Thank you and hope you managed to find some time to enjoy Christmas!!
 

xWolf13

Senior Member
Jul 6, 2012
1,387
843
I just got 5Ghz to work. At least on mine. So since a lot of my android devices don't detect my 5Ghz I had to do some researching. Changing the 5Ghz channel from Automatic/Auto to 44 or 48 will make it work. Can confirm on my Nexus 4 and the Kindle. Works superbly!
Source
 

jaxbierley

Senior Member
Jan 30, 2014
290
87
Everything seems to be working very nicely so far. Just flashed about an hour ago. Seems much smoother than kit kat did. Thank you very much. Looking forward to the updates.

Sent from my Amazon Tate
 

xWolf13

Senior Member
Jul 6, 2012
1,387
843
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94

As the title of thread says, its in Alpha. But may I ask what FC's your'e getting? I'm running the build on my Kindle at the moment and the only FC I get is Bluetooth Sharing. Bluetooth was activated on the main user and when I switch to another user it FC's.
 

cell2011

Senior Member
Apr 11, 2011
1,996
170
charleston wv
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94

---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------

Should i reflash just rom and gapps and supersu after i boot up?
 

xWolf13

Senior Member
Jul 6, 2012
1,387
843
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94

---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------

Should i reflash just rom and gapps and supersu after i boot up?

There's no need to flash SuperSU :p. SuperUser is built in already and working. Wipe System, Data, Cache, and Dalvik. Then flash the ROM and gAPPS.

---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------

Is anyone else getting a bootloop when clicking on reboot? I have to fully power down to be able to make it boot. Also, I'm unable to tick unknown sources when on another user (using Multi-Acc). Don't worry, I'm not downloading pirated apps xD. I download the APK's over at the Android Apps and Games forum.
 
Last edited:
  • Like
Reactions: cell2011

Random Username

Senior Member
Jan 7, 2013
329
36
This is great! Thank you Hashcode!

When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)

Is this something to be worried about? It boots just fine.
 
Last edited:

davigar

Senior Member
Feb 3, 2012
96
34
This is great! Thank you Hashcode!

When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)

Is this something to be worried about? It boots just fine.

My other problem is that I can't log in with my Google account? Is this maybe related?
I get the same error and google account works fine for me
 

Top Liked Posts

  • There are no posts matching your filters.
  • 69
    OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 7"

    *** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***


    BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
    http://forum.xda-developers.com/showthread.php?t=2128848


    CHECK KNOWN ISSUES BEFORE FLASHING. MAY NOT BE GOOD ENOUGH FOR DAILY USE.

    Official nightly builds can be found here:
    http://download.cyanogenmod.org/?device=tate

    Download Google Apps for Android 5.1:
    https://www.androidfilehost.com/?w=files&flid=25361
    (Choose newest *-5.1-* file)

    NOTES:
    • Older versions of TWRP will show a "mount failed error". This is safe to ignore.
    • First boot after a clean wipe will take a LONG time. Be patient.

    KNOWN ISSUES:
    Use XDA Bug Reporter

    SCREEN SHOTS:
    Use XDA Screenshots

    XDA:DevDB Information
    CM12.1 KFire HD 7 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD

    Contributors
    Hashcode
    Source Code: http://www.github.com/CyanogenMod

    ROM OS Version: 5.1.x Lollipop
    ROM Kernel: Linux 3.0.x
    Based On: CyanogenMod

    Version Information
    Status: Alpha
    Beta Release Date: 2015-06-24

    Created 2014-12-27
    Last Updated 2015-06-24
    21
    Reserved

    KERNEL UPDATES for Lollipop Android 5.0 / 5.1
    • Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
    • Combined defconfig setup to better support all HD models
    • Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
    • Picked IPV6 routing changes from Google's common 3.4 kernel
    • Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
    19
    Quick update:

    I've been really busy at work (anyone see Ara's DevCon2?), but wanted to do a quick build refresh as the theme engine was added recently.

    NO BUG FIXES. So be aware of the current KNOWN ISSUES in the Bug Reporter.

    (Downloads Section for the new ROM)

    Enjoy
    19
    When will you have a working 12.1 rom
    It's taking a while, since the Kfire HD's never had an official cm-12 (due to lack of SElinux enforcing).

    I've just recently started cleaning everything up, but it still need to run some more tests.. IE: try wiping the device and make sure there are no denials, etc.

    So maybe another week or 2.
    18
    The new builds are SElinux enforcing and while I did enable nightlies for testing, I might not recommend them unless you want to help debug and provide feedback.

    Also, I'm building a new TWRP with updated SElinux policies as well, which will be recommended before installing the new cm-12.1 ROMs.

    - Hash