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

[melvinaury]

I just forgot to clear cache and dalvik when upgrade. I just finish doing the wipe.

 

[Andrewmail83]

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.

 

[DB126]

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

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]

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]

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 ?

 

[ggow]

I'm new to your rom. Does it have an ota update feature?

No the ROM does not have OTA update.

 

[cybermcm]

Thanks for fixing the back light bug, really great!:good:

 

[Hallo32]

@ggow

Is there a guide how I can build this image from scratch?

 

[ggow]

@ggow

Is there a guide how I can build this image from scratch?

No, there is no guide as far as I'm aware.

 

[Hallo32]

No, there is no guide as far as I'm aware.

May it be possible to get such a guide?

 

[ggow]

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.

 

[Hallo32]

Thanks for the information.

 

[xsteven77x]

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.

 

[akz1x1]

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]

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]

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.

 

[ggow]

New Build is Up

- Dated 17 December 2017
- Port relevant security patches to up December 2017

 

[DB126]

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]

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 !