No issue w/dirty flash from TWRP (caches wiped). Nice and easy.- There are issues using the binary blobs from FireOS 184.108.40.206
- 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 220.127.116.11 blobs
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?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.
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 ...
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.
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.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.
/* * 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. */