• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[discontinued][ROM][unlocked][ford,austin] Lineage-12.1 [05 MAY 2020]

Status
Not open for further replies.
Search This thread

Andrewmail83

Member
Jul 9, 2016
11
3
GOOD WORK...

Excuse me if I have mistakes in English. I use the google translator:
Excellent ROM, very well polished. And better yet in each Update. It gave me Tremendous joy to return after enough time and see that you continue on ROM CM 12.1. What can I say is an excellent and stable ROM and to my understanding it was the best of all (And believe me ... I have installed and tried them all, I have more fun making the poor Tablet suffer than using it)
When I read that you were going to contribute in the Fire Nexus ROM, I put myself in plan ¡NOooo Whyyyy, this is PERFECT do not abandon it !!! So when i saw this ROM, was like a child in a Candy Store.
Only one request. You could in future updates add more time zones. In my case specifically that I am from Cuba, In the case of mobiles, the provider assigns us (GMT-05: 00) Cuba's standard time. But in these cases where that is not an option we must select (UTC-05: 00) Eastern Time (USA and Canada). Although in theory any -05: 00 should work for me. Games like CoverFire give me an error.
Greetings and keep up the good work. Andrew.
 
  • Like
Reactions: akz1x1 and ggow

DB126

Senior Member
Oct 15, 2013
15,263
10,043
- There are issues using the binary blobs from FireOS 5.6.0.0
- The boot.img won't boot, perhaps amazon changed something in the boot.img header, my device is is on the 5.0.1 bootloader. Haven't had a chance to investigate properly.
- Several media functions break using these latest blobs
- Will make a new release with 5.4.0.0 blobs
No issue w/dirty flash from TWRP (caches wiped). Nice and easy. :)
 

akz1x1

Senior Member
Oct 20, 2013
177
27
Thanks for still keeping the device updated for some of us users still using it :)

---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------

Sorry for OT but is there a kitkat version of the fire nexus rom available for this device.
I think it'll run much better than LP.
 

DB126

Senior Member
Oct 15, 2013
15,263
10,043
Thanks for still keeping the device updated for some of us users still using it :)

---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------

Sorry for OT but is there a kitkat version of the fire nexus rom available for this device.
I think it'll run much better than LP.
All ROMs (stock and custom) for this device are Android 5.1.1 based due to kernel restriction. Not sure I concur with your KK/LP assessment having used both variants on similar hardware. Is there a specific issue you are facing?
 

t3chwizard

Senior Member
Jul 20, 2013
1,576
349
Why the heck would you do that? Arguably cache is flushed at each boot and dalvik will be regenerated as needed. That said, running with a stale cache is just asking for trouble. You loose nothing save an extra few minutes on the *initial* boot after a ROM update by flushing dalvik. Just say'in ...

Never forget to wipe, that's when things start to stink ?
 
  • Like
Reactions: DragonFire1024

ggow

Recognized Developer
May it be possible to get such a guide?

I certainly haven't got time to be writing guides as I work on many different projects.

Basic gist of it goes like this:

1. sync lineage-12.1 source tree
2. get https://bitbucket.org/amazonfire2015/cm_device_amazon_ford
3. get vendor blobs from stock rom
4. get https://bitbucket.org/amazonfire2015/android_kernel_amazon_ford
5. then build the rom following lineage instructions

I haven't synced my device configs in a while, it's on my todo list.
 
  • Like
Reactions: ajislav

xsteven77x

Senior Member
Jul 2, 2010
3,423
768
Pittsburgh
Dude, I thank you from the bottom of my heart... sincerely, for still supporting his piece of **** device that some of us are stuck with LOL. You make using this piece of garbage tolerable and if I wasn't an unemployed loser right now, I would tip you some money from here to the moon. Instead, all I can offer is my positive sentiment. Thanks a lot dude.
 
  • Like
Reactions: akz1x1 and ggow

akz1x1

Senior Member
Oct 20, 2013
177
27
Just heard of the android Oreo Go version for low ram devices which struggles to run normal verison.
Wish there was some way it could be built for this device. :*(
 

DB126

Senior Member
Oct 15, 2013
15,263
10,043
Just heard of the android Oreo Go version for low ram devices which struggles to run normal verison.
Wish there was some way it could be built for this device. :*(
A rooted device can realize similar benefits through appropriate tuning. Oreo Go packages and optimizes the streamlined experience with emphasis on Google applications/services. How well it works in the wild has yet to be seen. Initial release is targeted for India.
 

platypoid

Senior Member
May 13, 2013
254
74
Stuck on Amazon Screen

update - I was able to adb side load back to stock 5.1.2 so guess I will start all over again !


I had Cyanogenmod working just fine on my Fire Kindle 5th generation and just followed all the instructions exactly as on first page to flash Lineage using Flashfire.
It rebooted up to Amazon screen and is stuck there.
I can get to Amazon system recovery with reboot, apply update from ADB, etc options . I tried reboot but no luck - same Amazon screen.

What is recommended I do next to try and get this back up and running ?
I don't remember the first stock kindle version I started with - I believe it was 5.1.4 maybe but not sure . Hopefully I posted somewhere when I was successful and can look it up.

Thanks for any help.
 
Last edited:

DB126

Senior Member
Oct 15, 2013
15,263
10,043
update - I was able to adb side load back to stock 5.1.2 so guess I will start all over again !

I had Cyanogenmod working just fine on my Fire Kindle 5th generation and just followed all the instructions exactly as on first page to flash Lineage using Flashfire.
It rebooted up to Amazon screen and is stuck there.
I can get to Amazon system recovery with reboot, apply update from ADB, etc options . I tried reboot but no luck - same Amazon screen.

What is recommended I do next to try and get this back up and running ?
I don't remember the first stock kindle version I started with - I believe it was 5.1.4 maybe but not sure . Hopefully I posted somewhere when I was successful and can look it up.

Thanks for any help.
If FireOS 5.1.2 has been successfully loaded head to the SuperTool thread to reroot and migrate to SuperSU in preparation for reinstalling a custom ROM. Recommend using a more recent FlashFire build (currently 0.73) which can be obtained from APKMirror. Be sure to maintain network isolation (WiFi radio off except when starting KingRoot runs) to avoid an unfortunate OTA update that may leave you with an unrootable device.

https://www.apkmirror.com/apk/chainfire/flashfire/
 

platypoid

Senior Member
May 13, 2013
254
74
If FireOS 5.1.2 has been successfully loaded head to the SuperTool thread to reroot and migrate to SuperSU in preparation for reinstalling a custom ROM. Recommend using a more recent FlashFire build (currently 0.73) which can be obtained from APKMirror. Be sure to maintain network isolation (WiFi radio off except when starting KingRoot runs) to avoid an unfortunate OTA update that may leave you with an unrootable device.

https://www.apkmirror.com/apk/chainfire/flashfire/

Thanks for the help .
So here is what I did - flashed Lineage 12/17/17 with gapps nano and it worked . But .... I didn't have any of the google stuff like playstore , gmail, etc so I tried apk mirror to put in playstore but that didn't seem to work. So I got idea to reflash again from scratch but use gapps micro . This did not work out so well and locked me up on the Amazon screen so I had to restore 5.12 again and reroot and run through all the Supertool options like block ota, install playstore, etc. So I put in Flashfire .73 from playstore .
But this time I used Flashfire to restore backup I had made in Cyanogenmod 12/1/2016 version from before I started all this . Flashed and it went all black but left it go awhile and restarted with ADB reboot and - here I am back to pretty much where I had started at . Lot of messing around for not much gain though I learned a few new things along the way. I will just stick with Cyanogenmod - always worked fine for what I use it for.
I guess the " If it's not broke , don't fix it " should apply to me and I don't need to try out Lineage - not sure what it would have gained for me anyway .
Thanks again for the help !
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 101
    Disclaimer
    Code:
    /*
     * 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.
     */
    LineageOS needs no introductions. This version of LineageOS-12.1 is a highly customised version solely for the Amazon Fire 7"

    - EVEN MORE IMPORTANT: As of January 2019 this ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.

    - IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required).

    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...

    Prerequisites for Installation
    - Unlocked Bootloader
    - TWRP Installed

    Downloads
    *** Please do NOT create any mirrors ***
    Lineage-12.1 for Amazon Fire 7"

    Source Code
    - ROM Source: https://github.com/cm12-amami
    - Kernel Source: https://github.com/ggow/android_kernel_amazon_mt8127-common
    - Common Tree: https://github.com/ggow/android_device_amazon_mt8127-common
    - Device Tree: https://github.com/ggow/android_device_amazon_ford
    - Device Tree: https://github.com/ggow/android_device_amazon_austin

    Thanks
    - @MSe1969 for the up to date cm-12.1 sources
    - @k4y0z and @xyz` for the bootloader hack
    - LineageOS

    XDA:DevDB Information
    LineageOS, ROM for the Amazon Fire

    Contributors
    ggow
    ROM OS Version: 5.1.x Lollipop

    Version Information
    Status: Stable
    Stable Release Date: 2017-08-02

    Created 2017-07-20
    Last Updated 2020-05-05
    32
    Changelog / Release Notes

    05 May 2020
    - Fixed video recording

    15 April 2020
    - ASB April 2020 patches (sec. string 2020-04-05)
    - Privacy Browser updated to version 3.4.1
    - Fix for CVE-2020-8597 (external/ppp)

    23 August 2019
    - August 2019 ASB patches (sec. string 2019-08-05)
    - Additional (backported) security patches from AOSP branch 'nougat-mr2-security-release
    - Privacy Browser updated to version 3.2
    - SetupWizard rebranded to LineageOS

    31 July 2019

    - Fix external sdcard not mounting correctly

    30 July 2019
    - ASB July 2019 patches (sec. string 2019-07-05)
    - System Webview M75 - updated to 75.0.3770.101
    - Fixed Keyboard Swype functionality
    - Front and rear cameras on ford and austin fixed and tested working

    24 May 2019
    - ASB May 2019 patches (sec. string 2019-05-05)
    - Privacy Browser updated to version 3.0.1
    - Fixed video recording
    - WiFi: Use hardware MAC address
    - Bluetooth: Use hardware MAC address

    22 April 2019
    - Rebased kernel with full history
    - Upstreamed kernel to 3.10.108

    18 April 2019
    - Fix sdcard write permissions
    - Fix screen off animation for odd hwrotation
    - Add support for amazon fire 7th gen
    - Merged common kernel for ford and austin (android_amazon_kernel_mt8127-common)

    16 April 2019

    - ASB March 2019 patches (sec. string 2019-04-05)
    - Privacy Browser updated to version 2.17.1
    - Android System Webview updated to M72 (includes CVE-2019-5786)
    - This is for unlocked devices only
    - Updated OP

    18 December 2018
    - ASB December 2018 patches (sec. string 2018-11-05)
    - Fix of 'adb root' bug (see LineageOS announcements)
    - Addl. fix of CVE-2018-9531, CVE-2018-9536 and CVE-2018-9537 from November ASB, which are flagged Android 9 only, but also apply
    - Backport of CVE-2017-15835 (skipped in November ASB)

    09 November 2018
    - ASB November 2018 patches (sec. string 2018-11-05)

    29 October 2018
    - ASB October 2018 patches (sec. string 2018-10-01)
    - Android System Webview updated to M69
    - Indication in Settings that Security patch level is unofficial

    12 September 2018
    - ASB September 2018 patches (sec. string 2018-09-05)

    18 August 2018
    - ASB August 2018 patches (sec. string 2018-08-05)
    - Privacy Browser updated to version 2.12

    01 August 2018
    - ASB July 2018 patches (sec. string 2018-07-05)
    - Privacy Browser updated to version 2.11
    - Android System Webview updated to M67

    23 June 2018
    - ASB June 2018 patches (sec. string 2018-06-05)
    - Privacy Browser updated to version 2.10
    - Privacy-default setting (at clean install): Sensitive information is hidden on the lock screen

    02 June 2018
    - ASB May 2018 patches (sec. string 2018-05-05)
    - Android System Webview updated to M66
    - Privacy Browser updated to version 2.9
    - Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google's 8.8.8.8)

    05 May 2018
    - Security patches up to April 2018 included

    25 March 2018
    - Fix privacy guard issue

    15 March 2018
    - Security patches up to March 2018 included

    30 January 2018
    - Fix root issue not appearing in developer options
    - Flashed clean with FF 0.73 - go figure - it worked for me this time no errors

    28 January 2018
    - Rebase ROM on https://github.com/cm12-amami - Thanks @MSe1969
    - Includes security patches up to Jan 2018
    - A clean install is recommended and may be required to function correctly.

    02 December 2017
    - Port relevant security patches to up November 2017
    - Switch to using FireOS 5.4.0.0 update-kindle-37.5.7.9_user_579225620 binaries and boot.img
    - Fixed backlight becoming stuck on minimum setting. This needs more users to test. It works for me so far :)

    29 November 2017
    - Use bin/wpa_supplicant blob from FireOS 5.4.0.0

    27 November 2017
    - Ported relevant November Security Patches
    - Ported relevant October Security Patches
    - Upgraded OpenSSL
    - Upgraded Privacy Browser to 2.7.2
    - NOTE: KRACK vulnerability is not patched in this one. The patch level for this version of the ROM is 01 November 2017. I am working on the 06 November 2017 patches. When I have it figured out, will do another release very shortly.

    28 September 2017
    - Ported relevant September Security Patches

    12 September 2017
    - Ported relevant August Security Patches
    - Fixed no way back from Charge Only mode

    02 August 2017
    - Fixed sdcard write issue
    - Fixed odd screen rotation glitch on power off
    - ROM status updated to "stable"

    20 July 2017
    - Initial Release
    - Ported security patches up to July 2017
    - Fixed up Xposed compatibility
    - Too many other fixes to list here
    - This ROM release is Alpha and needs a lot of testing that I can't cover off on my own.
    - All feedback will be greatly appreciated.
    - I have tested flashing using TWRP and FlashFire 0.57 so this should be OK.
    - A clean installation is mandatory.
    29
    New Build is Up

    - Dated 20 July 2017
    - Ported security patches up to July 2017
    - Fixed up Xposed compatibility
    - Too many other fixes to list here
    - This ROM release is Alpha and needs a lot of testing that I can't cover off on my own.
    - All feedback will be greatly appreciated.
    - I have tested flashing using TWRP and FlashFire 0.57 so this should be OK.
    - A clean installation is mandatory.
    18
    New Build is Up

    - Dated 27 November 2017
    - Ported relevant November Security Patches
    - Ported relevant October Security Patches
    - Upgraded OpenSSL
    - Upgraded Privacy Browser to 2.7.2
    18
    New Build is Up

    - Dated 28 September 2017
    - Ported relevant September Security Patches
    - Includes all bluebourne patches