[TUT:Flashfire] Install FireOS 5.4.0.1, ROOT, GAPPS (& keep TWRP if 5.0.1)

Search This thread

bibikalka

Senior Member
May 14, 2015
1,349
1,085
133
Update - 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://forum.xda-developers.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 :
  1. 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://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
  2. 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)
  3. 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]


0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
Code:
adb reboot-bootloader
fastboot boot TWRP_Fire_2.8.7.0.img
1) boot into TWRP and:
  1. do factory reset (skip if don't want to),
  2. flash whatever ROM you want from this post, for example, 5.3.1.0 ( rename *bin to *zip such that TWRP can recognize it):
    update-kindle-37.5.7.9_user_579279320.bin
    (Previous recommendation - update-kindle-global-37.5.5.2_user_552153420.bin)
  3. flash the attached fire_boot_53820.zip . The objective of this file is to overwrite all the problematic bootloaders after 5.1.x update back to 5.0.1 version (53820 variety). This will allow to go into fastboot and then TWRP just like before.
  4. flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
  5. flash Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
    http://forum.xda-developers.com/showthread.php?t=3034811
    (version xposed-vXX-sdk22-arm.zip )
  6. flash Pico (Uni) GAPPS for 5.1 :
    http://forum.xda-developers.com/android/software/tk-gapps-t3116347


B: Flashfire Install instructions [Note that you will have 5.1.2 (or 5.1.1) bootloaders after this procedure]


Given that FlashFire is no longer supported, I recommend version v0.51 with the date hack in order to pass the date check (adb shell; su; busybox date -s "201509221745"). Copy all the necessary files to the local Fire storage, such as /sdcard/upgrade. In Flashfire, chain the following files as ZIP or OTA flashes in one batch (same options in each case, no R/W for /system partition by default):
  1. the OTA file you want renamed to zip, such as this one update-kindle-37.5.7.9_user_579279320.bin
  2. the attached fire_boot_5.1.2-5.4.2_542168620.zip (or fire_boot_5.1.1-5.4.1_541112720.zip). This will replace whatever bootloaders the OTA file has with those from 5.1.2 (or 5.1.1), in order to allow upgrades/downgrades without bricking. Preserving 5.1.2 bootloaders may seem a bit pointless now, but it's still good to freeze these as some hackable bugs may be discovered in the future, so the older bootloaders one has - the higher the chance they have useful bugs ! Again, if you still have 5.1.1 bootloaders, do use fire_boot_5.1.1-5.4.1_541112720.zip here !!! (thanks to Kramar111 for reminding of the rooting trick that works with 5.1.1 bootloaders [fastboot oem append-cmdline "androidboot.unlocked_kernel=true"]
  3. flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
  4. Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
    http://forum.xda-developers.com/showthread.php?t=3034811
    (version xposed-vXX-sdk22-arm.zip )
  5. Pico (Uni) GAPPS for 5.1 :
    http://forum.xda-developers.com/android/software/tk-gapps-t3116347

After you've verified everything, hit the "FLASH" button.

See the screenshot below as an example of how the Flashfire screen should look. Note that Flashfire gives no margin of error because it reboot immediately, so if you are flashing a bricking FireOS (relative to your bootloaders), make sure that fire_boot_5.1.2-5.4.2_542168620.zip (or the 5.1.1 version !) is flashed immediately after !!! I've carefully followed this procedure, and verified that the bootloaders do get restored to 5.1.2 version regardless of what was in Amazon's OTA file.


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 ? ;)
1452654044767407_animate.gif
 

Attachments

  • fire_boot_53820.zip
    11.8 MB · Views: 4,630
  • good_screenshot_2016-07-16-17-55-35.png
    good_screenshot_2016-07-16-17-55-35.png
    129.8 KB · Views: 4,049
  • fire_boot_5.1.1-5.4.1_541112720.zip
    7.6 MB · Views: 940
  • fire_boot_5.1.2-5.4.2_542168620.zip
    7.5 MB · Views: 1,159
  • fire_boot_5.3.1-5.5.2_552153420.zip
    7.6 MB · Views: 946
Last edited:
Dec 7, 2015
15
2
0
For clarity, this is for a person that is currently on 5.0.1, correct? This is to go from 5.0.1 to 5.1.1 while retaining root/TWRP, but this will not allow someone that is on 5.1.1 to access TRWP, right?
 

Pond-life

Senior Member
Apr 7, 2011
369
132
0
So does anyone know what 5.1.1 offers over 5.0.1?

I was wondering that

No i meant even if ota is left enabled, there's no immediate risk.

Yeah but you had that cliffhanger 5.1.2 ending...

I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.

Sounds very useful :)

With the capture of the new FireOS 5.1.1, these the instructions to install 5.1.1 and keep root and TWRP access.

Will this work direct from 5.0.0? I see no reason it shouldn't but just checking.
 
  • Like
Reactions: mike7s

si_na

Member
Dec 5, 2008
10
0
0
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
 
Last edited:

Pond-life

Senior Member
Apr 7, 2011
369
132
0
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?

Seen someone mention on another thread that they've done it.

Which is handy as I've got to talk someone through this on skype later in the week when theirs arrives.
 
Last edited:

87racer

Senior Member
May 5, 2008
79
28
0
With the capture of the new FireOS 5.1.1, these the instructions to install 5.1.1 and keep root and TWRP access.

Install instructions.

0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
Code:
adb reboot-bootloader
fastboot boot TWRP_Fire_2.8.7.0.img

1) boot into TWRP and:
  1. do factory reset (skip if don't want to),
  2. flash the update from this thread (update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip, unpack bin.zip, rename *bin to *zip such that TWRP can recognize it, say thanks to the poster):
    http://forum.xda-developers.com/showpost.php?p=64184649&postcount=46
  3. flash the attached fire_boot_53820.zip
  4. flash Supersu.zip ( https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
  5. flash Pico (Uni) GAPPS for 5.1 :
    http://forum.xda-developers.com/android/software/tk-gapps-t3116347

2) reboot to 5.1.1. Verify that SuperSu works.

3) if step 2) fails, you get into working recovery by pressing "Pwr & Vol+". You can boot TWRP again, and sideload the old update : http://kindle-fire-updates.s3.amazo...ZjK/update-kindle-37.5.2.2_user_522054520.bin

4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?

I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
The new devices seem to be coming with 5.0.1 not 5.0.0.
 

gad42000

Member
Nov 28, 2008
35
1
0
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?


The new devices seem to be coming with 5.0.1 not 5.0.0.
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.

What benefits will I get with an 5.1.1 upgrade?
 

si_na

Member
Dec 5, 2008
10
0
0
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.
 

87racer

Senior Member
May 5, 2008
79
28
0
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.

What benefits will I get with an 5.1.1 upgrade?
From the release notes on a 5.1.1 tablet:
Blue Shade - Makes everything ugly by removing blue (supposed to be better at night)
FreeTime Web Browser - Browser for kids (limits, curated content, tracking, etc)
Activity Center - More kid stalking, track what the are spending their time on
Curfew - Restrict kids from using tablet even when FreeTime is not in use
 

Pond-life

Senior Member
Apr 7, 2011
369
132
0
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_

How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.
Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.

---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------

So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?

Having just done it. Yep, sat in twrp atm.
 

87racer

Senior Member
May 5, 2008
79
28
0
How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.
Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.

---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------



Having just done it. Yep, sat in twrp atm.
interesting so the 5.0.1 preloader and uboot work just fine with the 5.1.1 system image just not the other way around...think I will just RMA that tablet rather than get SP Flash Tools to work.
 

Pond-life

Senior Member
Apr 7, 2011
369
132
0
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.

Well you can as you could download the 5.0.1 and install it through twrp, but if it's not needed it's somewhat pointless.
 

howzitnow

Member
Dec 16, 2013
44
4
0
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?


The new devices seem to be coming with 5.0.1 not 5.0.0.

I received one on October 21st that came with 5.0.0, I received one a week October 26th later that came with 5.0.1. That's from Amazon, I suppose ymmv if you got them at BestBuy or elsewhere.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 34
    Update - 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://forum.xda-developers.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 :
    1. 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://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
    2. 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)
    3. 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]


    0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
    Code:
    adb reboot-bootloader
    fastboot boot TWRP_Fire_2.8.7.0.img
    1) boot into TWRP and:
    1. do factory reset (skip if don't want to),
    2. flash whatever ROM you want from this post, for example, 5.3.1.0 ( rename *bin to *zip such that TWRP can recognize it):
      update-kindle-37.5.7.9_user_579279320.bin
      (Previous recommendation - update-kindle-global-37.5.5.2_user_552153420.bin)
    3. flash the attached fire_boot_53820.zip . The objective of this file is to overwrite all the problematic bootloaders after 5.1.x update back to 5.0.1 version (53820 variety). This will allow to go into fastboot and then TWRP just like before.
    4. flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
    5. flash Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
      http://forum.xda-developers.com/showthread.php?t=3034811
      (version xposed-vXX-sdk22-arm.zip )
    6. flash Pico (Uni) GAPPS for 5.1 :
      http://forum.xda-developers.com/android/software/tk-gapps-t3116347


    B: Flashfire Install instructions [Note that you will have 5.1.2 (or 5.1.1) bootloaders after this procedure]


    Given that FlashFire is no longer supported, I recommend version v0.51 with the date hack in order to pass the date check (adb shell; su; busybox date -s "201509221745"). Copy all the necessary files to the local Fire storage, such as /sdcard/upgrade. In Flashfire, chain the following files as ZIP or OTA flashes in one batch (same options in each case, no R/W for /system partition by default):
    1. the OTA file you want renamed to zip, such as this one update-kindle-37.5.7.9_user_579279320.bin
    2. the attached fire_boot_5.1.2-5.4.2_542168620.zip (or fire_boot_5.1.1-5.4.1_541112720.zip). This will replace whatever bootloaders the OTA file has with those from 5.1.2 (or 5.1.1), in order to allow upgrades/downgrades without bricking. Preserving 5.1.2 bootloaders may seem a bit pointless now, but it's still good to freeze these as some hackable bugs may be discovered in the future, so the older bootloaders one has - the higher the chance they have useful bugs ! Again, if you still have 5.1.1 bootloaders, do use fire_boot_5.1.1-5.4.1_541112720.zip here !!! (thanks to Kramar111 for reminding of the rooting trick that works with 5.1.1 bootloaders [fastboot oem append-cmdline "androidboot.unlocked_kernel=true"]
    3. flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
    4. Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
      http://forum.xda-developers.com/showthread.php?t=3034811
      (version xposed-vXX-sdk22-arm.zip )
    5. Pico (Uni) GAPPS for 5.1 :
      http://forum.xda-developers.com/android/software/tk-gapps-t3116347

    After you've verified everything, hit the "FLASH" button.

    See the screenshot below as an example of how the Flashfire screen should look. Note that Flashfire gives no margin of error because it reboot immediately, so if you are flashing a bricking FireOS (relative to your bootloaders), make sure that fire_boot_5.1.2-5.4.2_542168620.zip (or the 5.1.1 version !) is flashed immediately after !!! I've carefully followed this procedure, and verified that the bootloaders do get restored to 5.1.2 version regardless of what was in Amazon's OTA file.


    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 ? ;)
    1452654044767407_animate.gif
    6
    I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.

    Sent from my KFFOWI using Tapatalk
    4
    Flawless 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
    Thank you. Understood.

    But just to clarify further...So once I update to 5.1.1 through this method staying rooted and still with 5.0.1 bootloader there is no option to hide. You can only rename the apk? Hiding doesn't work? Or hide will work since I still will be on boot loader 5.0.1.

    Because if hiding doesn't work after updating, I might as well hide all apps now since you are telling me that it should remember whatever stuff i blocked. It's just easier than renaming later.
    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.
    2
    copied update to AFH:

    https://www.androidfilehost.com/?fid=24269982087012932
    MD5: 8dfcc416a0b2c47fe384dd28f2ef18ed
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone