[TUT:Flashfire] Install FireOS 5.4.0.1, ROOT, GAPPS (& keep TWRP if 5.0.1)
- Thread starter bibikalka
- Start date
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
34Update - Dec. 15th, 2018: Recently I attempted a couple of freshest ROM installs (update-kindle-37.6.0.5_user_605485120.bin and update-kindle-37.6.2.6_user_626533320.bin), and the device bootloops with the 5.1.2 bootloaders (cycling through the "Amazon" logo - looks like the newest kernel is incompatible with the older bootloaders). Using recovery, I had to sideload 5.1.2 again (which older bootloaders allowed me to do!), and re-root it using these instructions via Kingoroot. As such, the most recent version that I recommend here is update-kindle-37.5.7.9_user_579279320.bin (FireOS 5.4.0.1).
News : The update file for 5.3.1.0 is posted on the Amazon site, so time to upgrade! Note that you cannot get root by downgrading 5.3.1 to 5.1.2 (& Kingroot), because the 5.3.1.0 bootloaders will brick if rolled back (so stay put for now ...) :
http://xdaforums.com/amazon-fire/help/installing-custom-rom-fireos-5-3-1-0-t3418541
Rootless in Seattle ...
[Updated July 16th, 2016]
Flashfire almost replicates TWRP functionality, thus I've significantly re-written this post to include branches for people who managed to keep TWRP from the old days of 5.0.1, and those who have to use Flashfire because of newer bootloaders (and thus lacking TWRP ...). If you want to quickly upgrade (or downgrade ?) your *rooted* FireOS while avoiding potential bricking issues, the post is for you (if you are not rooted yet, and have stock 5.3.1.0, do not attempt to downgrade, it'll brick the Fire !!!).
Before proceeding, remember these IMPORTANT points :
- Take a note of your current bootloaders, this will be important later on. If you forgot what version you have, please follow this post to identify it:
http://xdaforums.com/amazon-fire/development/identify-bootloader-version-t3424634 - If you disabled the stock launcher via "pm hide", please re-enable it again before the procedure, or install some other launcher as the user app. For example, if you converted Nova or other launcher to a system app, it will disappear upon upgrade, so you need some other launcher operational. Until I fixed Nova, the tablet would freeze at the end of the "optimizing applications" stage because at this stage there was no working launcher (can be fixed by adb command line, but still a bit of a mess)
- Turn on Airplane mode, so that you don't "catch" an update right after this upgrade (and before you have a chance to disable it)
A : TWRP Install instructions [if you still have the "good" 5.0.1 bootloaders]
B: Flashfire Install instructions [Note that you will have 5.1.2 (or 5.1.1) bootloaders after this procedure]
2) reboot to FireOS 5. Verify that SuperSu works.
3) if step 2) fails, you get into working recovery by pressing "Pwr & Vol+". If you still have 5.0.1 bootloaders (getting rare by now ...), then sideload the old 5.0.1 update and root it: http://kindle-fire-updates.s3.amazo...ZjK/update-kindle-37.5.2.2_user_522054520.bin If you have 5.1.2 bootloaders, sideload 5.1.2 instead (the last rootable version as of now) : https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin If you have 5.1.1 bootloaders, sideload 5.1.1 !
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
Want to say thanks by clicking the "Thanks" button ?
4Flawless upgrade
I was on stock 5.01 with root and Google , flashed 5.1.1, then fire_boot, Supersu and Pico (Uni) GAPPS , worked a treat with no problems and i have TWRP access.
I also noticed that when i disabled the app called "special offers" in titanium back up the lock screen ads have stopped, i had read that the old way on 5.01 doesn't work with this build so hopefully this sorts it.
thank you bibikalka for the guide.3
While I understand the disable/hide rational I wouldn't take that chance with the OTA apk. We all know disabled/hidden apps can be coaxed to run which would be highly undesirable with OTAs that can ruin your day. Renaming affords an extra level or protection while retaining easy reversibility. It is not a bullet proof solution as Amazon could find a way to replace/regenerate the file if they really got aggressive about OTAs. Doubt that would happen.
Bottom line: disable/hide/uninstall general purpose apps to your hearts content - but take a few extra moments to rename (or otherwise obfuscate) DeviceSoftwareOTA.apk. You be happy you do not have a sad story to tell following some future OTA that hammers privileges or bricks your device.2copied update to AFH:
https://www.androidfilehost.com/?fid=24269982087012932
MD5: 8dfcc416a0b2c47fe384dd28f2ef18ed - Take a note of your current bootloaders, this will be important later on. If you forgot what version you have, please follow this post to identify it:
