[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]

Search This thread

ccic2491

Senior Member
Jun 3, 2012
252
39
Charlotte
I'm really stuck here. I've installed TWRP 2.7.1.0 and the OtterX bootloader but I've accidentally wiped everything. I had all my files on the internal storage before I started and now they are gone. So now I have no OS and it wont let me mount the sd card to put the required files on it. Any ideas?
 

dokie80

Senior Member
May 23, 2008
637
247
jakarta
That's normal. When you convert to otterx partition, all data is wiped. This is mentioned on otterx project thread.
Boot to twrp, and push your file using adb push command. I suggest you follow the steps on otterx thread though, just in case you haven't format the cache, system, data partitions

Edit.
Fyi. This is otter cm11 thread, not otterx.
Instruction to convert to otterx partition can be found here: http://forum.xda-developers.com/showthread.php?p=50852361

I suggest you to follow the steps EXACTLY as the instructions.

Good luck

Sent from my Nexus 5 using Tapatalk
 
Last edited:

ccic2491

Senior Member
Jun 3, 2012
252
39
Charlotte
That's normal. When you convert to otterx partition, all data is wiped. This is mentioned on otterx project thread.
Boot to twrp, and push your file using adb push command. I suggest you follow the steps on otterx thread though, just in case you haven't format the cache, system, data partitions

Edit.
Fyi. This is otter cm11 thread, not otterx.
Instruction to convert to otterx partition can be found here: http://forum.xda-developers.com/showthread.php?p=50852361

I suggest you to follow the steps EXACTLY as the instructions.

Good luck

Sent from my Nexus 5 using Tapatalk

Thank you. I keep getting "access is denied" when I try to push the files, any ideas for that?
 

Ciespi

Senior Member
May 17, 2009
66
23
Mid West
I'm having trouble with this and Hellfire Rom I'm able to flash the Rom install gapps and get its first boot. However if I reboot the Rom refuses to boot. Stays stuck on spinning logo. I'm using fff1.4a twrp 2.8.2 I believe . please excuse my forum etiquette I've been away for a long time in military and recently found my kindle fire and would like to fix it up and gift it to a friend with less than what this device is worth. Thanks in advance.
 

mikeataol

Senior Member
Nov 21, 2013
670
332
I'm having trouble with this and Hellfire Rom I'm able to flash the Rom install gapps and get its first boot. However if I reboot the Rom refuses to boot. Stays stuck on spinning logo. I'm using fff1.4a twrp 2.8.2 I believe . please excuse my forum etiquette I've been away for a long time in military and recently found my kindle fire and would like to fix it up and gift it to a friend with less than what this device is worth. Thanks in advance.
Hi
not sure what the hellfire rom is,but my experience is you have to flash the rom, let it boot and step through setup,

THEN go back and flash gapps.

cant do them both in one recovery session.
 

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,557
2
9,091
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
I'm having trouble with this and Hellfire Rom I'm able to flash the Rom install gapps and get its first boot. However if I reboot the Rom refuses to boot. Stays stuck on spinning logo. I'm using fff1.4a twrp 2.8.2 I believe . please excuse my forum etiquette I've been away for a long time in military and recently found my kindle fire and would like to fix it up and gift it to a friend with less than what this device is worth. Thanks in advance.
could be gapps version
verify md5 for all files?
I recommend twrp 2.7.1.0

Sent from my KFFOWI using Tapatalk
 
  • Like
Reactions: dokie80

joshjryan

Member
May 4, 2011
9
1
Cannot connect to Chromecast

Hi everyone.
I have installed cyanogenmod11 on my first gen Kindle Fire, and everything is going great, except for one thing. I cannot connect to my chromecast (from any chromecast enabled app).
Do any of you have success connecting to a Chromecast?

All my Google-cast enabled apps (MLB At Bat, Plex, YouTube, Google-cast my screen) see my Chromecast (it is listed and selectable, when I click the cast button). This issue is that when I select the chromecast, it attempts to connect and fails (every time, for every app). I can successfully cast to this Chromecast from all other devices (various android versions and Windows w/ Google Chrome) at my house (connected to the same WiFi network).

Any thoughts, or recommendations on something that I should check?
 

mikeataol

Senior Member
Nov 21, 2013
670
332
Hi everyone.
I have installed cyanogenmod11 on my first gen Kindle Fire, and everything is going great, except for one thing. I cannot connect to my chromecast (from any chromecast enabled app).
Do any of you have success connecting to a Chromecast?

All my Google-cast enabled apps (MLB At Bat, Plex, YouTube, Google-cast my screen) see my Chromecast (it is listed and selectable, when I click the cast button). This issue is that when I select the chromecast, it attempts to connect and fails (every time, for every app). I can successfully cast to this Chromecast from all other devices (various android versions and Windows w/ Google Chrome) at my house (connected to the same WiFi network).

Any thoughts, or recommendations on something that I should check?

Hi
I doubt you will have any luck with that rom.
I'm no expert by any means, but I believe the underlying drivers for the video subsystems , (these drivers are shared by the developers of various roms) need to be rewritten.
And I understand the manufacturer TI isn't supporting them any more.
It's deep in the system level, see my post here: (its for the HD 7" , but its true for all the OMAP devices I've tried lately
NOOK Tablet, Kindle Fire 1st gen, Kindle Fire 2nd gen, Kindle Fire HD 7" )
http://forum.xda-developers.com/kindle-fire-hd/7-inch-help/ti-omap-experts-left-wild-t3349287

I saw lots of activity in Samsung Galaxy Nexus threads related to similar issues, but the gist is that the drivers are at a point where they "mostly" work, but are not
really done completely or "right"

Ive been trying lots of roms lately , and on the 1st generation Kindle Fire you will get better results on a newer rom
I highly recommend the ResurrectionRemix flavors

you have to update the bootloader to the "OtterX" variant, and update TWRP recovery to a newer version.

in the new bootloader , you have to convert your partitions to the new OtterX format (it wipes everything. )

If youre willing to wipe the Kindle and start it over Ill come back with more info if you want. Its many steps from start to finish
-----edited for a couple of missing words
 
Last edited:

mikeataol

Senior Member
Nov 21, 2013
670
332
Hi everyone.
I have installed cyanogenmod11 on my first gen Kindle Fire, and everything is going great, except for one thing. I cannot connect to my chromecast (from any chromecast enabled app).
Do any of you have success connecting to a Chromecast?

All my Google-cast enabled apps (MLB At Bat, Plex, YouTube, Google-cast my screen) see my Chromecast (it is listed and selectable, when I click the cast button). This issue is that when I select the chromecast, it attempts to connect and fails (every time, for every app). I can successfully cast to this Chromecast from all other devices (various android versions and Windows w/ Google Chrome) at my house (connected to the same WiFi network).

Any thoughts, or recommendations on something that I should check?

I went back to this CM11 to test because a few things were nagging at me and it had been a while since I ran it ...
(/data partition is too small for me, and the combined storage roms just work better)

I installed the rom, gapps , and the google cast app from the app store , and updated all the loaded apps from Play Store
rom was the latest nightly for otter
https://www.cmxlog.com/11/otter/ cm-11-20160410-NIGHTLY-otter.zip
gapps was gapps-kk-20131119.zip 120MB

The apps that see the chromecast appear to connect and cast fine. I have a Chromecast 2015.
Mobdro, Dailymotion, CNN, Youtube. all good.
Other apps that "should" see the chromecast , dont see it and dont pop up the icon to cast.
(mediahhh, popcorntime,cast2TV)
This symptom has been true of most roms for OMAP devices lately EXCEPT the CM11 for Kindle Fire 2 (Otter2)
KF2 works very well, except for native screencasting

just wondering,
anyone have insight into why the CM11 for Kindle Fire 2nd gen. (Otter 2 ) which uses the exact same drivers (system/vendor)
have much better Chromecast connectivity than this one?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 434
    STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
    EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
    http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
    Flash with the following adb commands:
    Code:
    adb shell
    su
    idme bootmode 4002
    reboot
    # back in your PC shell
    fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img

    If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
    Mirror 1: Download (Goo.im)

    BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.

    STEP 2: DOWNLOAD A BUILD OF CM11.0:
    DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM

    NIGHTLIES:
    http://download.cyanogenmod.org/?device=otter

    GAPPS (Use Version "CM 11" row):
    http://wiki.cyanogenmod.org/w/Gapps

    Older builds are found here:
    http://goo.im/devs/Hashcode/otter/cm10/
    http://goo.im/devs/Hashcode/otter/cm10.1/
    http://goo.im/devs/Hashcode/otter/cm10.2/

    GAPPS (For Android 4.3/CM10.2 builds):
    http://goo.im/gapps/gapps-jb-20130813-signed.zip

    CHANGES:
    • [05/15] More audio updates to fix low-power states (screen off / background music)
    • [11/25] Released updated build for cm11.0
    • [08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
    • [07/30] Updated to CM10.2 build
    • [05/26] Backlight driver update to help w/ SODs
    • [05/24] Sensor updates (includes light sensor now usable in Android OS
    • [05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
    • [05/14] New audio driver (WIP)
    • [03/27] Reboot Recovery mode is now fixed
    • [01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
    • [01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
    • [01/07] Battery life / sleep improvements
    • [01/06] Update to 3.0.50 kernel
    • [01/06] Update wifi firmware to R5.SP3.06
    • [12/16] Fixed Deep Sleep
    • [12/15] Added multi-profile fix

    CURRENT KNOWN ISSUES:
    • The headphone MIC input is not functioning correctly yet. Work in progress.

    KERNEL FEATURES:
    • [08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
    • [01/06] WLAN Firmware R5.SP3.06
    • [11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom)
    • [11/07] WLAN Firmware R5.SP3.03
    • [09/05] Updated to SGX/IMG DDK [email protected] for Android
    • Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
    • Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
    • Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
    • MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
    • Many bugfixes pulled down from TI's omapzoom sources.

    RESERVED FOR NOTES

    XDA:DevDB Information
    Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire

    Contributors
    Hashcode
    ROM OS Version: 4.4.x KitKat

    Version Information
    Status: Stable

    Created 2014-05-01
    Last Updated 2014-05-21
    150
    UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1

    DEVELOPER BUILDING:
    Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
    Patch 1: http://review.cyanogenmod.org/#/c/53917/
    Patch 2: http://review.cyanogenmod.org/#/c/54562/

    And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
    Won't get a decent build till that's all done.



    KNOWN BUGS:
    1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
    6. Headset recording via the MIC input jack doesn't work


    DEVS
    BUILDING THIS ROM:

    First, read through Google's Android website about "how to setup a build environment":
    http://source.android.com/source/initializing.html

    Then you can setup the Kindle Fire by doing the following:
    mkdir android
    cd android
    (Use main repo for CyanogenMod 10.2)
    repo init -u https://github.com/CyanogenMod/android -b cm-10.2
    repo sync
    vendor/cm/get-prebuilts
    . build/envsetup.sh && brunch otter
    44
    [09/16] CM10 STOCK + 4AI.1.7 KERNEL [STABLE]
    Download Here
    md5sum: b5746745f62c20ed5f6a2520ca506982

    Changes for 09/16:
    • Charging is now fixed. Including basic OTG support. Test away and I can make tweaks as needed. There may be a bug where adb doesn't restart after OTG devices are enabled.
    • Backlight / Panel driver updated. This was probably causing some of the battery drain.

    EDIT: "now" fixed.

    Enjoy.
    42
    I just wanted to do a quick update:

    Got my new device yesterday, and immediately put twrp, fff 1.4a and ICS on it.

    Should be good to pick up where I left off w/ the kernel now.

    Hope to have a new version in a few days.

    Sent from my Amazon Kindle Fire using Tapatalk 2
    42
    New kernel/ROM based on the 4AI.1.7 release are getting a lot better (IMHO) so I'm probably going to do another kernel/ROM release here soon.

    Here's an update of what's coming in the next release:

    1. Kernel Audio source: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now.
    2. Audio HAL module: updated to TI's latest source to help with #1 and future support for USB audio, etc.
    3. Lights HAL module: removed conflicting battery light operations. The kernel manages the battery light entirely. The OS should almost never do anything with it.
    4. (NEW to JB) Power HAL module: used by the OS for temporarily kicking up the CPU during certain events (using the interactive governor) -- this makes the system more responsive. This feature is also still under development over time and I'll continue to update it.
    5. HW acceleration / graphics buffer system: Completely updated sources from TI for the hwcomposer, libion and other graphics / buffer systems
    6. Along w/ #5 I was able to roll up to the latest PowerVR driver [email protected] (up from [email protected] in the last build). I noted right off the bat
    less GL issues and smoother game play.

    I may take a night or 2 and continue to play with the MIC settings to see if we can get it working, and that would be the delay in this release (if any).

    But, in general, the build for the Kindle Fire is a getting a lot cleaner (IMHO). And that's always a good thing.


    Still working on:

    - Memory management: I'm still not happy with how the OS is unloading certain processes at times (acore?!), and I'll be working with some of the ROM devs to setup better memory management in this main sources at GitHub. No reason why every dev should need to work that stuff out.
    - MIC function. Getting close, but I need to probably spend 2-3 more nights following audio routes and watching the OS setup the Audio input devices when the headset is plugged in.
    - Charger function. This is the big kahuna. Been a while since I worked on it, probably time to jump back into it.