Database Users

[How To] Install TWRP on OS 4.5.3 and Boot Recovery (newbie friendly)

TWRP (Team Win Recovery Project) replaces a device's stock recovery and provides, among other options, the ability to install img (image) and zip files. TWRP for the Fire HDs was developed by JMZ and is described here.
How to install TWRP
These steps are for a first-time install on a rooted Fire HD running OS 4.5.3 with stock bootloader and recovery.
At this time, 4.5.3 bootloader is required. You're welcome to try to get it onto a different OS, but you need the 4.5.3 bootloaders and I'm not getting into that. So, if you're running a different OS, have messed with partitions or done something that requires a TWRP reinstall (other than reinstalling 4.5.3 and rerooting), you risk being unable to boot recovery or bootloop/brick.
OK, that doesn't sound so "newbie-friendly" but this really is a simple process that should always go smoothly on a "clean" OS 4.5.3.​
You can easily install TWRP with either TWRP Manager (also by JMZ) or Flashify from the Play Store.
If you don't have Play Store access:
- Flashify - v 1.9.1 from APKMirror
- TWRP Manager - Download from JMZSoftware​For installing TWRP, the only difference between the two is that TWRP Manager auto-downloads the correct TWRP version while Flashify requires you download it yourself.
[EDIT 8/16/2015] At this time, TWRP Manager doesn't seem to be working. Use Flashify, instructions below. Steps for TWRP Manager are at bottom of post.
Install TWRP with Flashify
Download JMZ's ariel TWRP image (https://www.androidfilehost.com/?fid=24052804347756852) to the Fire's download folder.
Install and run Flashify (download link above) and give it superuser access when prompted. It probably will also prompt to apply loki patch for Kitkat. Say yes.
Tap Recovery Image and then Choose a File.
Navigate to download folder, tap the TWRP file, and when Flashify asks if you are sure, tap Yup!
If install succeeds ("Flash Complete"): (a) Tap Reboot now. (b) When back in Fire OS, boot to recovery (below) and confirm you're in TWRP. Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), first take a screenshot. If you can determine the problem, fix it and try again or try TWRP Manager. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.
How to Boot to Recovery
Manual: (a) Power off tablet. (b) Hold down power and volume-up buttons at same time until you see "Amazon," then release. (If you just boot back into Fire, you didn't power off first or didn't hold buttons long enough.)
adb command from computer: adb reboot recovery
- If you see TWRP, great! Check it out and then press Reboot and System to go back to OS.
- If you get stock recovery screen ("reboot" and "factory reset"), TWRP didn't install. Reboot should be highlighted. (If it's not, use volume-up or -down to select it.) Press the power button to click reboot and when back in Fire OS, try the other app.
[EDIT 1] For simplicity, install TWRP Manager on the Fire and follow these steps.
Install TWRP with TWRP Manager
Install and run TWRP Manager and give it superuser access when prompted. It will also prompt to apply patch for Kitkat. Say yes.
Tap top-left of screen for slide-out menu and select Install TWRP.
Confirm Device Name shows "ariel" and then tap Install Recovery. [download begins]
At warning screen, tap yes.
If install succeeds ("Flash Successful"): (a) Go to slide-out menu and choose Reboot Options and then Reboot Device. (b) When back in Fire OS, boot to recovery (above) and confirm you're in TWRP.
Note: If tablet bootloops, post the problem in one of the bootloop threads.
If install fails (error messages displayed), take a screenshot in case you need to post the problem and then look at comments here for a solution. If you can determine the problem, fix it and try again or try Flashify. If you don't understand the error or can't resolve it, post in a "TWRP install failure" thread.

After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?

Po069 said:
After step 5 a) only puts on the screen "Kindle Fire" and I can not make the "Power and Volume up buttons reboot".
Could you help me please?
Click to expand...
Click to collapse
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350

DoLooper said:
I'm sorry I can't help you. This guide is for the 2014 Fire HD tablets. The Kindle Fires are ealier models. Look here to figure out which tablet you have and then post the problem in the forum for your tablet:http://forum.xda-developers.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
Click to expand...
Click to collapse
Thank you very much for your answer.
Kind regards.

Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Thanks for your help!

SpaceBananas said:
Sorry if this is a stupid question, but if I update the Fire OS after successfully rooting/installing TWRP will I mess up anything?
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates). If I update the OS now will it brick it or mess up TWRP in any way?
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
If you update now without following that guide you will lose root and TWRP. You may not be able to root with Kingroot and you won't have the "friendly" bootloaders that can boot TWRP. Don't do it.
I'll have to get back to you about updating. Maybe bibikalka will jump in. Look around for a KitKat version of pico-uni Gapps, which you could install in TWRP now. There will be link in an old guide for OS 4.

SpaceBananas said:
I rooted everything and installed TWRP succesfully on my Fire HD 6 running 4.5.3 (it was fresh out of the box and I didn't allow any OTA updates).
. . .
Also, ultimately I'm just trying to get Google Apps on my HD 6 (it'd be nice if I could get lollipop on it but I bricked the last HD 6 I had so I'm starting with the low-hanging fruit haha). However, I can't really find a guide to do this starting from 4.5.3 Fire OS... Could you point a noob anywhere to either a) install GApps or b) get lollipop installed?
I was trying to follow this tutorial but it's not really noobie-friendly and I think it's meant to start from 5.0.n which is why I'm asking if I can update without screwing anything up.
Click to expand...
Click to collapse
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.

DoLooper said:
OK, I looked at the guide again. @bibikalka may have a preferred route, but here's what I suggest: Pretend nothing else is there except steps 1) through 3) and just carefully follow those steps.
Download all the files to the pc first. Get the 5.1.1 update (only because we know it's rootable with Kingroot) and rename the extension from bin to zip. Skip Xposed (step 1-7). Do get 5.2.0_stock_recovery_uboot.zip (step 1-10). Copy or move all the files to the downloads folder on device. (This is the long way and you can download directly to device if you prefer. I just find it easier to download and double check that you have all the right files from the pc.)
Hold Power and volume+ to get into TWRP, then carefully do all the sub-steps under 1) except for step 7. (From what you say, I just don't think you need Xposed.) Just be sure you have the correct file at each step and you'll be fine.
Click to expand...
Click to collapse
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there

bibikalka said:
Any point in using 5.1.1 ? Since SuperSu gets flashed during the update, it does not care which FireOS version it is. Nobody will be running Kingroot since SuperSu is already there
Click to expand...
Click to collapse
No, 5.1.2 is fine. It was just a cya suggestion in case user missed a step and somehow lost root--but OF COURSE no steps will be missed.

TWRP failed to install, now have no recovery
So I'll start by saying I'm an idiot. I wasn't paying attention to which version OS is required and tried to install TWRP using Flashify. It went through the motions and did its reboot, and now I'm stuck with absolutely no recovery at all. I've tried searching these forums for a "TWRP installation failed" thread and have had no luck, at least not for the Fire HD 6 device. Really need help here, I have absolutely no way to get into recovery to flash anything back at all.

[TUT] Install [FireOS 5.4.0.1], ROOT & GAPPS

Update13, Oct 23, 2017: Everything still works with the latest 5.4.0.1, just grab the correct ROM file
Update12, Jul 23, 2016: Upgraded to FireOS 5.3.1, everything went smooth. It's not clear yet if 5.3.1 can be safely downgraded to 5.1.2 in order to get root. Stay put until we get some confirmation! It has been reported that the downgrade from 5.3.1 to 5.1.2 bricks the Fire HD!!! So downgrade to FireOS 4.5.3 instead, root, quickly turn off the WiFi, and then use this guide to go back to 5.3.1 (and do use 5.3.1 bootloaders!):
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Update11, Apr 29, 2016: I installed the new 5.1.2 build from Mar 30, 2016 via the instructions below (using TWRP), and everything worked fine. This version is not rootable by Kingroot (yet). One good option (if you have this version now) is to sideload via the stock recovery the rootable 5.1.2 from Feb 26 https://kindle-fire-updates.s3.amaz...HBV/update-kindle-20.5.4.2_user_542168620.bin , and then run Kingroot. See Update10 for other tips on what to do.
Update10, Apr 8, 2016: According to the reports, the stock 5.1.2 (Feb 26, 2016 build) is rootable via Kingroot (update to 5.1.2 via the standard Amazon procedures, try Kingroot several times). Block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_ . Then you can install GAPPS as per these instructions : http://forum.xda-developers.com/showpost.php?p=65405511&postcount=268 Note that you will still benefit if you follow this guide: install TWRP, and reinstall 5.1.2 via the steps below and get all the Android goodies loaded at once (including Xposed) on an entirely clean /system partition with no Kingroot files.
Update9, Mar 21, 2016: The instructions below are updated for 5.1.2 . Kingroot does not work under 5.1.2, use adb sideload to 4.5.3 to get root! It seems that 5.1.2 has a bug where /sdcard is not visible for root (the issue seems to be this newer SuperSu version, not FireOS 5.1.2 ... I went back to SuperSu 2.46, and now it works as before). To be on the safe side, I modified scripts in post #2 to work with the newer SuperSu as well (but I don't recommend this newer SuperSu version ...) . According to a report, 5.1.1 bootloaders can be run after 5.1.2 without bricking. Regardless, here, all the bootloaders will be kept as 5.1.1 just to be sure
Update7, Feb 13, 2016: Instructions for the latest 5.4.1 update file (FireOS 5.1.1 -Bellini - with "blue shade") - Note that the instructions can be confusing, don't rush if you are not sure what you are doing (and especially if your Amazon warranty already expired) !!!
Update6: Since early Oct, there is a new evil (!!!) update named here as 5.2.2u2 (which bricked a few Fires), but thankfully the update glitches has been worked out!!! Back to business !!! Observe that once you booted 5.2.2u2 bootloaders (either through the Amazon update or the procedure below), there is no going back !!! The only other bootloaders you can run at this point are 4.5.3 as per post #2
Update4: Please do not deviate from the instructions, and do flash GAPPS during Step 1), together with Xposed. JMZ tool for installing GAPPS is not recommended!
For lazy ones I recommend skipping factory reset in Step 1) below if you already have Lollipop.
Install instructions.
Unless you have 4.5.3 bootloaders and TWRP at the moment, your path into TWRP goes via post #2 (and you do need TWRP to proceed!!!). No need to fear, I have made a simple script to flash 4.5.3 bootloaders and TWRP in just one click, see section "101" in post #2 !!!
Before proceeding, please write down your current FireOS version, and its date. To install the latest Lollipop you can pretty much start anywhere, these are rough suggestions how to get TWRP running in the quickest way possible :
unrooted Lollipop, pre-5.1.2 or 5.1.2, root via KingRoot (try several times), use post #2 for TWRP, re-load 5.1.2 from TWRP by following this post
unrooted Lollipop, alternative option, (note the version you have!!!), downgrade to 4.5.3 via stock recovery ADB sideload option (block updates immediately!!!), root 4.5.3, use post #2 to install TWRP
already rooted Lollipop, use post #2 to boot into TWRP, the bat script in section "101" is recommended (and can do a clean re-install of your current Lollipop version with the same procedure if you care)
rooted FireOS 4.5.x (latest Kingroot is known to root either 4.5.3 or 4.5.5.1, perhaps 4.5.4 & 4.5.5 as well) -then post #2 (if the bootloaders are not 4.5.3)
unrooted 4.5.x (>4.5.3 such as 4.5.4 or 4.5.5 but pre-4.5.5.1): disable OTA, run latest Kingroot, report back if failure, use post #2 for TWRP
unrooted whatever - write directly into memory 4.5.3 bootloaders & TWRP (somewhat slow, but can be an attractive option if you cannot root your version of Lollipop directly, and don't want to factory reset the device memore during the downgrade to 4.5.3 in order to root) :
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
0) Before proceeding, ensure that you have a functional non-system launcher (install any as user app), or enable the stock Amazon launcher via adb if it's blocked (pm enable com.amazon.firelauncher) !!! Make sure it works. This will ensure that you can avoid problems later on when the /system partition is overwritten, and your non-Amazon launcher that was installed as a system app is gone. I had Nova as the system app (overwritten by the upgrade!), and Amazon launcher blocked, so after the upgrade to 5.1.2 there was no working launcher. Not good ... Had to do a couple of system resets and TWRP restores until I figured out what was happening ...
1) boot into TWRP, and, in a single session (!!!!!)
(Optional) clear cache/dalvik (to shrink the backup size), run TWRP backup to a USB drive via USBOTG cable for your /data partition
(Optional) do factory reset (can skip if you already have Lollipop),
flash the latest FireOS from this official Amazon link (rename *bin to *zip such that TWRP can recognize it):
https://www.amazon.com/gp/help/customer/display.html?nodeId=201596850
If for some reason you need a different FireOS version, grab the file you need from the links in this post.
flash 5.2.0_stock_recovery_only.zip below. If you kept track of your prior FireOS versions and know what you are doing, you can flash
5.4.1_1133_stock_recovery_uboot.zip from post #2 (this will flash 5.2.0 stock recovery & 5.4.1 bootloaders). Note that if you downgraded from FireOS 5.3.1 to 4.5.3 to root, you must flash 5.5.2_1534_stock_recovery_uboot.zip instead, this will put the required 5.3.1 bootloaders back.
flash the attached make_space_v02.zip (this will remove moffice and weather to make room in /system for GAPPS , can always install this stuff from Play Store)
flash Supersu.zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
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 )
flash Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
clear cache/dalvik in TWRP
Another reminder: If you are absolutely sure that you have never run FireOS 4.5.5.1 bootloaders or Lollipop with anything but 5.2.0 bootloaders, you can flash 5.2.0_stock_recovery_uboot.zip from post #2 here, this way you preserve the well behaved 5.2.0 bootloaders. If you are not sure about any of this, don't do it !!!
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...). Notice that at this point you no longer have TWRP. Since it does not boot with the 5.x bootloaders anyway, TWRP was replaced with the stock recovery that has some useful features, such as adb sideload. Later on it's possible to get back into TWRP from within the rooted Lollipop by following post #2.
3) reboot to Lollipop (takes ~15 minutes), and hopefully, it works.
Bricking warning !!! If you flashed the wrong bootloaders, and you get a black screen upon reboot, there is good news - you can UNBRICK !!! The bad news is that the procedure is quite involved, and may take quite a bit of effort. So measure twice, cut once !!! If unsure about bootloaders, ask here first before flashing, instead of coming back to complain about the brick later.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions (and thank me again for being able to recover so easily !!! )
5) make_space_v02.zip already disabled OTA updates , but please verify that you now have DeviceSoftwareOTA.apk_ block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
6) Consider adding an option to switch from pure Amazon interface to almost pure Android and back on the fly:
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Note: Using JMZ tool for installing GAPPS is not recommended, please flash GAPPS as per Step 1)
The next post discusses how to get into TWRP temporarily with Lollipop installed, and come back to Lollipop
Want to say thanks by clicking the "Thanks" button ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Higher skill level operation - proceed with care !!!
Update3.5 : Updates for 5.3.1 !!! Please use 5.5.2_1534_stock_recovery_uboot.zip if you downgraded from stock FireOS 5.3.1 to 4.5.3 for rooting, meaning that you now have 5.3.1 bootloaders
Update3.4 : Updates for 5.1.2 !!! Please use the new WindowsAutoTWRP_v03.zip with 5.1.2 (backward compatible to 5.1.1 and before). There are tons of verification messages in the new script, please read carefully !!! It appears that in 5.1.2 there is a bug such that root cannot see /sdcard/gscript properly (this was the issue caused by the latest SuperSu I tried). To handle this, I redirected the path to /data/media/0/gscript . If you are using Gscript, delete the flash_453(_stay) scripts in Gscript, and open them again after you run WindowsAutoTWRP_v03 once. This way Gscript will pick up the corrected scripts with the updated path. Pay attention to the checksums !!!
Update3.3 : And now "Newbie Friendly" !!! Just one simple *.bat script under Windows !!! See section "101"
Update3.2 : If you are unsure what bootloader file to use, go with 5.4.1_1133_stock_recovery_uboot.zip
Update2: If you ever booted the Sept 2015 Lollipop (FireOS 5.0.1, called here 5.2.2u2), DO NOT use 5.2.0_stock_recovery_uboot.zip , it will brick!!!
Update1: Instructions are clarified with more detail on how to use "dd" correctly.
Important : do not try to use Flashify!!! Flashify cannot access all partitions that you need to flash !!! Flashify will brick your Fire !!!
Here you get to run TWRP again, and then return to Lollipop.
The steps must be executed with precision (all 3 files must be dd'ed successfully). Keep the 5.4.1_1133_stock_recovery_uboot.zip file from below on the device, in its /images directory you have 3 images for 5.4.1 which you can flash back right away if you need to abort. If something is wrong, DO NOT reboot for as long as it takes. Keep the device without reboots, and come back here for guidance.
To understand a bit what we are doing in this post, read this :
A bit of background. Fire HD boots TEE1 -> UBOOT -> recovery. With 4.5.3, we lucked out that TEE1 & UBOOT accepted unsigned recovery (aka TWRP). No such luck with 5.2.x - TEE1 & UBOOT expect signed recovery (for example, stock one). That's why I had everybody overwrite TWRP with stock recovery in post #1 as the last step in the upgrade. Otherwise after the upgrade to 5.2.x, TWRP would still be sitting in recovery, and being unsigned, it cannot boot !!! A few bricks were created because of this last point. But with the stock 5.2.0 recovery (which it will boot), at least there is an option to sideload another update file.
So, the key to running TWRP while in 5.2.x is to overwrite the 3 key components together (TEE1, UBOOT, recovery), and then return things to 5.2.x once TWRP is no longer needed.
For convenience, before proceeding save all the attached files on your Fire in "/sdcard/gscript"
101 - Automatic installation under Windows !!!
I managed to debug it and not to brick !!! Tested personally (gotta eat your dog food !!!) Heavily inspired by glitch3yf0x in http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804
Save the necessary Lollipop bootloaders zip into /sdcard/gscript on Fire HD, this will get you back into Lollipop
Download WindowsAutoTWRP_v03.zip to your PC with some Windows on it, unpack anywhere
Run the commands below, and make sure you authorize root access for adb when the question pops up on your Fire:
Code:
adb shell
su
exit
exit
Enable apps from unknown sources
Run 1_FIRE_HD_4TH_GEN_TWRP.bat
At the bottom you should see these checksums :
Code:
3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3
d605e31a180652c65d6957b58d2d8501 /dev/block/mmcblk0p5
305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7
Make sure the checksums are correct before rebooting !!! Do not reboot if checksums are wrong, keep the Fire running, and come back here to ask questions !!! I almost bricked under 5.1.2 due to the newer SuperSu version, but managed to catch the wrong checksums, and updated the scripts to have additional verifications.
A possible issue here is that you did not have root access, so the "dd" commands could not succeed. At this point you can go to method A since the script left all the necessary ingredients on the device, so all you need to do is to run the script from Gscript (installed for you!), make sure you click "needs SU". Delete the old flash_453 and flash_453_stay scripts from Gscript, and re-open them again after you run WindowsAutoTWRP_v03 at least once.
Verify again that you have 5.x.x bootloaders zip file on Fire HD which you will access from TWRP (it can also be on a USB drive if you got USB OTG cable) - Out of kindness I've provided the most popular bootloaders zip at the moment - 5.4.1 version, you can find it in /sdcard/gscript, it's TWRP ready, just flash it if 5.4.1 is OK for you (5.4.1 bootloaders will also work with FireOS 5.1.2 )
Type "adb reboot recovery"
In TWRP, after you are done with everything, don't forget to flash the 5.x.x bootloaders zip file in order to boot back into Lollipop!
After the batch file runs, you will have Gscript installed, together with the required script & image files in /sdcard/gscript, so you can head over to the next section (section A), and set up TWRP access without using a PC! You will also have scripts in there to enable/disable Amazon's stuff on the fly, as described in here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
A - Instructions with Gscript.
Due to popular demand (looking at DoLooper here ), the approach is simplified and all the bootloaders are flashed via a script, and this assumes that you have Gscript installed (here : https://bitbucket.org/Equidamoid/gscript/downloads )
Download the attached "453_key_images.zip" to your Fire, create a folder (if does not exist) "/sdcard/gscript", and unpack this zip file in "/sdcard/gscript" (so all *bins sit in this directory)
[*]Download the attached "flash453.zip", copy to "/sdcard/gscript", unpack
Run the bat from WindowsAutoTWRP_v03 in section "101" at least once
Go to Gscript/Add script/Need Su (yes, check)/Load file "flash_453_stay.sh"
From Gscript run this "flash_453_stay.sh", and verify the checksums
If you are using versions prior to FireOS 5.1.2, you can use "flash_453.sh" and you should end up in TWRP (it will reboot automatically)
If unhappy about auto-reboot, use "flash_453_stay.sh" script, it will only do "dd" and exit back to the current OS (no auto-reboot to recovery)
B - Alternative (old) instructions via ADB
Download the attached "453_key_images.zip" to your Fire, create a folder "/sdcard/gscript", and unpack this zip file in "/sdcard/gscript". From the PC side, open ADB and start typing :
adb shell
su
cd /sdcard/gscript
ls
dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_twrp.img of=/dev/block/mmcblk0p7
exit
exit
adb reboot recovery
These are 4.5.3 bootloaders, and TWRP. Just like in the good old days under FireOS 4.5.x
This is a sample log, your output should look similar (typed commands are colored in red) :
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
0000000000000XXX device
C:\Program Files\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cd /sdcard/gscript
cd /sdcard/gscript
[email protected]:/sdcard/gscript # ls
ls
453_key_images.zip
453_tee1.img
453_twrp.img
453_uboot.img
[email protected]:/sdcard/gscript # dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_tee1.img of=/dev/block/mmcblk0p3
6364+1 records in
6364+1 records out
3258876 bytes transferred in 0.543 secs (6001613 bytes/sec)
[email protected]:/sdcard/gscript # dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_uboot.img of=/dev/block/mmcblk0p5
414+1 records in
414+1 records out
212116 bytes transferred in 0.041 secs (5173560 bytes/sec)
[email protected]:/sdcard/gscript # dd if=453_twrp.img of=/dev/block/mmcblk0p7
dd if=453_twrp.img of=/dev/block/mmcblk0p7
14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.103 secs (6500496 bytes/sec)
[email protected]:/sdcard/gscript # exit
exit
[email protected]:/ $ exit
exit
C:\Program Files\Minimal ADB and Fastboot>adb reboot recovery
Click to expand...
Click to collapse
Reboot into recovery, and you should be in TWRP.
C - What am I doing in TWRP ???
-- Well, you tell me
Generally, you want to flash something (Xposed, GAPPS?). Keep flashing whatever else you need! Note that at this point you won't be able to boot into 5.2.x, siegesoldier has established this fact with his early upgrade attempts. 4.5.3 bootloaders will not boot 5.2.x kernel due to some missing parameters !
When you want to go back to Lollipop, in TWRP flash the attached 5.4.1_1133_stock_recovery_uboot.zip (or 5.5.2_1534_stock_recovery_uboot.zip). This will put 5.4.1 (or 5.5.2) bootloaders back, as well as 5.2.0 stock recovery. Note if you are sure that you never had 5.4.1, 5.2.2u3 or 5.2.2u2 bootloaders running (or stock FireOS 4.5.5.1), use 5.2.0_stock_recovery_uboot.zip (this is rare now, be very sure !!!) If you forget to flash the 5.x.x bootloaders, the device will cycle upon reboot with the Amazon logo continuously. This is not a big issue ! Just hold the power button until the Fire shuts off. Then from the turned off state turn it on by pressing power and Vol+ buttons together, and this will get you back into TWRP where you can flash the 5.x.x bootloaders and reboot to Lollipop.
Now reboot to system, and you should have your Lollipop
Want to say thanks by clicking the "Thanks" button ?

bibikalka said:
. . . and finally, when TWRP asks you to install root, say "yes" . . .
2) reboot to recovery, you should see stock 5.2.0 recovery.
Click to expand...
Click to collapse
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]​Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!

Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
DoLooper said:
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]​Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Click to expand...
Click to collapse
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.

Yes! thx! (Can easily get es file explorer from appstore for this.)

Thanks for this bro! I can confirm this process works, and I will show the steps I took here (clarification for people who want to do this).
1. I started on 4.5.4 + Root + TWRP with adb installed on my Mac
2. I connected fire to computer, and did (in terminal window)
adb backup -apk -shared -all ~/Downloads
to save my data before factory reset (this should work on Mac + Linux).
3. Rebooted to TWRP
4. Performed a Factory Reset (the default one under Wipe on TWRP)
5. Installed the 5.2.0 bin file with adb sideload
6. Installed 5.20 stock recovery with adb sideload
7. Went to Reboot page and chose reboot recovery
8. TWRP will prompt you to install root, do it
9. It will then reboot into stock Amazon recovery, choose to reboot your system
10. Mine took forever, but it finally booted into 5.2.0
11. If you're plugged into the computer, it gives you the option to enable usb debugging, do this
12. I completed the setup process
13. Downloaded SupersSU from here on computer
14. Used
adb install -r supersu.apk
(or whatever your's is named)
15. Check you have root by running
adb shell
su
16. You should have root installed!
17. Now run
adb restore backup.ab
which will restore your data (apps)
18. SKIP UNLESS YOU HAD XPOSED INSTALLED If you had Xposed installed, it is not compatible now, so uninstall all of your modules (if you want to save space). I believe the problem with Xposed is that we need to change a build.prop sdk/api value, but that's something for us to figure out later.
19. Install jmz fire tools from here
20. Run it and choose install Gapps, your device will reboot
21. Sucess!!! Lollipop + Root + Gapps
Anyways, good luck to everyone I hope this helps someone in the future!
---------- Post added at 10:33 AM ---------- Previous post was at 10:32 AM ----------
DoLooper said:
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]​Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Click to expand...
Click to collapse
pcrhckyman said:
Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.
Click to expand...
Click to collapse
I fixed this by running
adb install -r eu.chainfire.supersu.apk
or whatever your supersu file is named.

Easy TWRP and Gapps?
bibikalka said:
OK, here the risk is pretty simple - likely brick. On the upside, you get to run TWRP, and then return to 5.2.0.
Click to expand...
Click to collapse
Remolten said:
I fixed this by running adb install -r eu.chainfire.supersu.apk or whatever your supersu file is named.
Click to expand...
Click to collapse
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.

As far as GAPPS, go the lazy way of using JMZs app just worked for me. I'll be removing the modifications that prevent the apps from updating shortly. But the old playstore works fine on lolipop.

DoLooper said:
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
Click to expand...
Click to collapse
I don't think the Flashify method works, but I will try it.
EDIT: Flashify requires custom recovery
EDIT 2: Trying siegesoldier's method
EDIT 3: We have a winner! Thanks siegesoldier and jmz!

siegesoldier said:
As far as GAPPS, go the lazy way of using JMZs app just worked for me. I'll be removing the modifications that prevent the apps from updating shortly. But the old playstore works fine on lolipop.
Click to expand...
Click to collapse
Thx for info, but JMZ's TWRP manager is crashing on me.

DoLooper said:
Thx for info, but JMZ's TWRP manager is crashing on me.
Click to expand...
Click to collapse
This one silly!
http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655

siegesoldier said:
This one silly!
Click to expand...
Click to collapse
lol thx. (Sorry for taking up more space here, but that was funny!)

FYI. Xposed is possible if you downgrade back to 4.5.3/twrp and after flashing lolipop, but before replacing recovery, flash xposed-v67-sdk22-arm-by-romracer-20150716.zip found in http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 and install XposedInstaller_3.0_alpha4.apk once you're back into lolipop found here http://forum.xda-developers.com/showthread.php?t=3034811.

bibikalka said:
OK, fellas, 1st attempt for a reasonably safe journey to rooted Lollipop. The key now is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://forum.xda-developers.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
and finally, when TWRP asks you to install root, say "yes"
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions.
You may be asking about GAPPS - try to install manually, as indicated here :
http://forum.xda-developers.com/showpost.php?p=62008212&postcount=71
More experimental stuff in the next post.
Click to expand...
Click to collapse
Glad I was able to help out and get it working for everyone!

Fantastic effort in a short period of time !!! The sales of HDs and "brick" returns will surely skyrocket
Also, noting the confusion with TWRP, I've updated my post #2 to explain exactly why all that stuff needs to be done to run TWRP :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
Click to expand...
Click to collapse
TWRP is not signed, and will not run with the bootloader from 5.2.0 which expects a signed recovery. That's was the whole reason to do the "circus" with 3 dd's, basically, one needs to flash all the bootloaders in the chain from 4.5.3, together with TWRP to be able to boot into TWRP. After that, one would reflash back all the bootloaders and recovery back to 5.2.0 versions.
Remolten said:
I don't think the Flashify method works, but I will try it.
EDIT: Flashify requires custom recovery
EDIT 2: Trying siegesoldier's method
EDIT 3: We have a winner! Thanks siegesoldier and jmz!
Click to expand...
Click to collapse
See the above answer, to get into TWRP, you have to flash all 3 files together. But itself, TWRP does not boot from 5.2.0 bootloaders, that's why people had bricks before when they did not replace TWRP after flashing 5.2.0
siegesoldier said:
FYI. Xposed is possible if you downgrade back to 4.5.3/twrp and after flashing lolipop, but before replacing recovery, flash xposed-v67-sdk22-arm-by-romracer-20150716.zip found in http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 and install XposedInstaller_3.0_alpha4.apk once you're back into lolipop found here http://forum.xda-developers.com/showthread.php?t=3034811.
Click to expand...
Click to collapse
Ha-ha, love Alex' 3rd Fire! Must have chewed through 2 previous ones Indeed, you can run TWRP, provided it's booted via 4.5.3 bootloaders. And after flashing 5.2.0 in TWRP, that's the last time you see TWRP booted up unless you then "dd" them back as in my post #2.
I will update that post to make these points more clear.

hawkazn said:
Glad I was able to help out and get it working for everyone!
Click to expand...
Click to collapse
Yep, thanks for making the 5.2.0 into a dull flashing experience instead of the nail biting one !!!

I am loving this good-looking and way more customizeable update! Thanks again!
bibikalka said:
That's was the whole reason to do the "circus" with 3 dd's, basically, one needs to flash all the bootloaders in the chain from 4.5.3, together with TWRP to be able to boot into TWRP. After that, one would reflash back all the bootloaders and recovery back to 5.2.0 versions.
Click to expand...
Click to collapse
If one wanted to, the 3 dds circus could still be done any time, right? So if we wanted to slap on TWRP for a quick flash we could do that?
Speaking for myself, getting Gapps turned out to be a priority once I saw lollipop on the Fire. And the "JMZ tool/allow update" method was both expedient and didn't include the phrase, "likely brick"

DoLooper said:
I am loving this good-looking and way more customizeable update! Thanks again!
If one wanted to, the 3 dds circus could still be done any time, right? So if we wanted to slap on TWRP for a quick flash we could do that?
Speaking for myself, getting Gapps turned out to be a priority once I saw lollipop on the Fire. And the "JMZ tool/allow update" method was both expedient and didn't include the phrase, "likely brick"
Click to expand...
Click to collapse
Ha-ha, true, saying "likely brick" is poor marketing. I'll rephrase it to something more benign

Disable ota on rooted 5.20
bibikalka said:
OK, fellas, 1st attempt for a reasonably safe journey to rooted Lollipop. The key now is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://forum.xda-developers.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
and finally, when TWRP asks you to install root, say "yes"
Thanks to Remolten, there is a very detailed write up regarding all of this:
http://forum.xda-developers.com/showpost.php?p=62018692&postcount=6
Note that this is the last time you see TWRP (unless you do what I recommend in post #2), so take an opportunity to flash other stuff such as Xposed, thanks to siegesoldier for pointing this out (not sure about GAPPS yet without at least one reboot into 5.2.0):
http://forum.xda-developers.com/showpost.php?p=62021411&postcount=13
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...)
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions.
You may be asking about GAPPS - install them via JMZ tool, there are reports that everything works just fine:
http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
More experimental stuff in the next post, this is how to get into TWRP again with 5.2.0 installed.
Click to expand...
Click to collapse
Is it necessary to disable ota after upgrading to 5.2.0 with root? If so. How?

Brofreeman said:
Is it necessary to disable ota after upgrading to 5.2.0 with root? If so. How?
Click to expand...
Click to collapse
I'm not sure if it is required, but it is a good precaution just in case. If you install the JMZ tool, the third page has a switch to disable OTA's.

[Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly")

This guide is for never-rooted 2014 Fire HDs. Don't use it on any 2015 (5th gen) Fire. If your Fire has an sd card slot, go here.
Mar 3 Update: This guide is out of date. It could brick you! Don't use it!
Instead, follow one of these guides:
http://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Ignore these hidden text boxes
Feb. 5, 2016 Update: Don't use this to root OS 5.1.1 yet. It needs to be updated!!
Jan. 18, 2016 Update: Don't use this guide if you are running OS 4.5.5.1.
Look at Settings->Device->System Updates. If it says 4.5.5.1, installing the Developer Preview will brick your device.
Before You Begin:
OS 4.5.4, 4.5.5 (NOT 4.5.5.1) - Follow these steps to install the Developers Preview (OS 5):
Here are 2 methods. If you request it from Amazon it could take 24 hours, but if it causes problems you have proof that it downloaded to device. If you don't care about that and want it right now, use method 2.
1/23/16 UPDATE: Developers Preview is no longer available from Amazon. Method 2 is the only option.
Keep in mind, this is your choice. We can no longer blame Amazon for downloading "bad" firmware to device.
1/22/16 UPDATE: Use only method 2 until the risk of OTA updating to 4.5.5.1 is over.
METHOD 1 - From Amazon
Go here and request the developers preview: https://developer.amazon.com/public...campaign=FireOSPreview&sc_ detail=GetPreview]
It could take 24 hours but usually doesn't.
Goto Settings->Device->System Updates and press "Update Now"
If it doesn't download, wait an hour and try again.
METHOD 2 - From device
Turn OFF wifi.
Get update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin from here.
Copy/move the update file to device
Goto Settings->Device->System Updates and press "Update Now"
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go! Be sure to keep wifi off.
Note: If it hasn't booted after 20 minutes--it's stuck at "Fire" logo--hold down Power and Volume-up buttons to get to recovery menu. In recovery, factory reset, wipe cache and then boot to system.
OS 4.5.3 - Keep wifi OFF. Put the tablet into airplane mode immediately.
.
OS below 4.5.3 - Follow these steps to install OS 4.5.3:
Turn OFF wifi.
Download the 4.5.3 update to pc and copy/move it to device.
Go to Settings->Device->System Updates and press "Update Now."
The file will install. [long startup.]
If you haven't installed adb drivers, do that now and you're ready to go!
Install adb device drivers. Here's an illustrated guide for Windows.
* OS 5.0.n: Install driver for both OS mode and sideload mode.
* OS 4.5.3: Install driver for OS mode only.)
.
If you don't know how to drag & drop or copy/paste into the terminal/CMD window, read this.
This guide simply pulls together existing material, almost none of which is original to me. All thanks go to Powerpoint45, who discovered how to downgrade to rootable OS 4.5.3; bibikalka for the ingenious recovery-swap update method that preserves root; seigesoldier, hawkazn and hariiiii for file captures and fearless testing.​
A - Root!
Make sure ADB drivers are installed and adb is enabled in Developer Options.
Turn OFF wifi (airplane mode)
OS 4.5.3 - Download Kingroot (link below), open a terminal/CMD window from the folder you put it in, and go to step 6.
OS 5.0.n - Download to computer:
- 4.5.3 update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
- Kingroot: http://www.kingroot.net/
Downgrade to 4.5.3 (thanks to @powerpoint45):a. Connect to computer and open terminal/CMD window from folder containing bin file and kingroot.
b. Enter: adb reboot recovery
c. On tablet, use volume buttons to select “apply update from ADB” and then press power.
d. If you KNOW you have working adb driver for sideload mode, go to step e. Otherwise, see here:
To see if sideload-mode driver is installed, open Device Manager and see if your adb driver is listed under Android Device.
- If it is, close this text box and continue the steps.
- If it IS NOT and you're on Windows, do the following:
(1) Find KFARWI under "Other devices." NOTE: If you don't see KFARWI under "Other," disconnect/reconnect and look again.
(2) Right-click KFARWI and select "Update Driver Software." [see Update Driver Software screen].
(3) Click "Browse my computer" and then "Let me pick from a list . . ." [see Select your device type . . ."]
(4) Click Android Device. [see "Select the device driver you want . . .]
(5) Select your usual adb driver from the list, press Next, and say yes at warning screen. [see "Windows has successfully updated your driver software"]
(6) In CMD window, run adb devices and confirm you see your device ID and "sideload," like this:List of devices attached
SERIALNUMBER sideload​If you don't see serial number, reboot tablet and computer and repeat "adb reboot recovery" and "Apply update from ADB" steps. Device should now be recognized.
e. From computer, enter: adb sideload update-kindle-20.4.5.3_user_453011120.bin
f. On tablet select "wipe data/factory reset" and then "reboot system" [long startup]​
Enter language in Amazon setup, but skip registration and keep wifi OFF.
On computer, enter commands to block OTA:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Install Kingroot from computer: adb install app_filename.apk
Turn on wifi, run Kingroot on Fire and press "root." If you don't get success (100%), keep trying.Kingroot works over wifi, so do this where signal strength is best.
If the latest Kingroot from the link just won't work, try version 4.0.0 or 4.0.1 downloaded from any safe site.​
On computer, give commands to confirm su access, granting root access on tablet when prompted:
adb shell
su
(In Windows, a # prompt indicates root.)
Type exit two times to get out of su.
B - Install TWRP and Get Files for the Upgrade
Download JMZ's ariel TWRP image to the Fire's download folder (or to computer and move to tablet).
Download Flashify v 1.9.1 to computer folder where you opened CMD window.
Install Flashify from computer: adb install app_filename.apk
Run Flashify on Fire and install the ariel TWRP.
If you have any question, follow the steps here. You must select Recovery image and Choose a File, and navigate to the ariel image.
Boot to recovery and confirm you're in TWRP:
adb command = adb reboot recovery; manual = power off, hold power & volume-up buttons until Amazon logo appears and then let go.
Tap Reboot, then System to boot back to OS.
Delete anything in tablet Download folder and get files for the upgrade.
.
Files for the Upgrade
Please hit Thanks when you pick up a file from an XDA site
Download apks to computer for later install.
- SuperSU: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
- ES File Explorer: http://www.apkmirror.com/apk/es-glo...file-explorer-4-0-2-3-3-android-apk-download/
Download to tablet (or to computer and move to tablet Download folder):
➜ Take care here: Be sure to get the right files and that they all download completely.
- 5.2.2u2 UPDATE BIN (linked in the post) This is update-kindle-full_ariel-20.5.2.2_user_522053520.bin
Confirm downloaded filename matches the above and then rename the extension from .bin to .zip.
- 5.2.0 STOCK RECOVERY ONLY (5.2.0_stock_recovery_only.zip - attached to post) AND . . .
- MAKE_SPACE (make_space_v01.zip - attached to post)
- Latest PICO-uni GAPPS: Get "tk_gapps-modular-pico-5.1.1(uni)-5.1.1-*-signed.zip"
C - Upgrade to OS 5.0.1 and Install Gapps
Bibikalka's Lollipop guide has info about the upgrade (and a Thanks button we all ought to hit!)
The boots into recovery and the OS can take a long time; don't interrupt them (by trying to manually reboot, e.g.)
Turn OFF wifi and connect to computer.
Boot to recovery. (Manually or "adb reboot recovery" from pc).
[TWRP screen displayed on tablet.]
In TWRP, do following exactly and if you have any problem, post immediately and wait for reply :
a. Factory reset (Tap Wipe and swipe "Swipe to Factory Reset." At "Successful," tap TWRP home icon at bottom-left)
b. Install the update-kindle-full_ariel-20.5.2.2 UPDATE zip
. . (Tap Install button, navigate to Downloads folder and tap the UPDATE zip. Repeat for the following zips.)
c. Install the 5.2.0 STOCK RECOVERY ONLY zip
d. Install the MAKE_SPACE zip
e. Install the GAPPS zip
f. Tap Reboot > Recovery and when prompted (top of screen) "install SuperSU?," swipe the slider to install it!
[long startup]
➜ You're now running rooted OS 5.0.1 and TWRP is gone. If you need it again, see here. Do not try to reinstall TWRP with Flashify. (Brick!)
Confirm you see stock 5.2.0 recovery.
If tablet doesn't boot to recovery or is still booting after 30 minutes, post in bibikalka's Lollipop thread
Reboot to system [takes at least 10 minutes] and when prompted on tablet to allow USB debugging, say "yes"
- If you miss "Allow USB debugging" prompt, unplug/replug to see it
- If tablet bootloops or is still booting after 40 minutes, see step 4 in bibikalka's Lollipop thread
At Setup screen, press Exit (or choose language if required). Do not connect to wifi; tap COMPLETE SETUP LATER.
D - Install the Apps, Block OTA and Open Play Store
On computer, open terminal/CMD window from folder containing ES File Explorer and SuperSU apks and install each with this command:
adb install -r app_filename.apk
On tablet:
a. Enable apps from unknown sources in Settings > Security.
b. Run File Explorer and enable Root Explorer (in menu under Tools), granting root access when prompted.
c. Run SuperSU to update binaries and reboot when prompted.
. . [If SuperSU gives choice of "CWM/TWRP" or "Normal," choose Normal]
Block OTA:
a. In the terminal/CMD window, enter these commands granting root access on tablet after the su command:adb shell
su
pm disable com.amazon.otaverifier
pm enable com.amazon.dcp <--(renables dcp from Section A. This block is not needed after you do the next step.)​b. Use File Explorer on tablet to navigate to /system/priv-app/DeviceSoftwareOTA and rename extension of DeviceSoftwareOTA.apk to .apk_
Turn on wifi, open Play Store and sign in.
Register the Fire HD with Amazon.
Whew! Yay! :victory:

Some brave soul still needs to try to flash GAPPS during the 5.2.0 install in TWRP
If that fails, one will have to downgrade to 4.5.3, root, and get back to 5.2.0. So 20 minutes tops, not the end of the world ...

Yes, purposefully didn't put it in cuz untested. I'm thinking about it per your post at other thread. Just need to gird my loins

In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?

ROMAddiction said:
In Section C Step 7 adb returns failure due to the app already existing. When I was in Step 3f TWRP gave me the option to skip root install or to install SuperSu, which it only does the installer and that requires Google Play or TWRP to complete the installation. What should I do there?
Click to expand...
Click to collapse
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."

DoLooper said:
As the first line says, This guide is only for Fire HDs running the unrooted Developer Preview of Lollipop. I will clarify that. Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk." I assume you said yes at step 3f when prompted to root, but I do not understand this phrase, "which it only does the installer and that requires Google Play or TWRP to complete the installation."
Click to expand...
Click to collapse
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root. I did say yes at step 3f and TWRP then installed a SuperSu Installer App. When you tap on the app it says it will install SuperSU but either from the Google Play Store or through TWRP. This is where I'm stuck because I can't install it from the Play Store or from TWRP, nor can I use ADB and install it from there because it says that SuperSu is already on my Fire.
Sent from my LG-H811 using XDA Forums Pro.

ROMAddiction said:
Yeah, I started out with my Fire on the developer's build and have been working my way back to it with root.
Click to expand...
Click to collapse
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
DoLooper said:
. . . Since you had SuperSU installed, at C7 use "adb install -r name_of_your_supersu.apk."
Click to expand...
Click to collapse

DoLooper said:
If you were on 4.5.4 and wanted to get to rooted 5.2.0, this is the guide you wanted: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. But I thought you had done that and that's when you lost recovery. Oh, well, doesn't matter now, as long as you were able to boot to stock recovery at step C4.
Did you reinstall superSU with "adb install -r name_of_your_supersu.apk." as said in my last post? (Notice the -r) Please do that and continue the steps. Let me know if "adb shell" "su" does not show you're rooted. If step 13 insists on Play Store, skip that step, finish the guide and run SuperSU after Gapps is installed. Please let me know if you have to skip step 13, so I can edit the guide. Thank you.
Click to expand...
Click to collapse
Ah, no I had been updated to 4.5.5 the other day and was wanting to roll back and root my Fire to make it much more useful to me. Signed up as a Developer to get it to update me to the 5.2 update and then followed the steps here to get me rooted and back to 4.5.3, etc.
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!
Sent from my LG-H811 using XDA Forums Pro.

ROMAddiction said:
I did the adb install -r with the apk and it loaded, but not in the app drawer. I could find it in Settings under Apps but the App Info wouldn't let me do anything like Force Stop or Clear Cache. Thinking that I may have to start back over from the beginning to fix this. Always make some sort of screw up when I do this sort of thing. Hopefully I won't have to bother you with anything again. I'll check to see if abd shell will tell me if I'm good and get back to you. Thanks for the help!.
Click to expand...
Click to collapse
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.

DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
Alright! When I get home tonight I'll complete the rest of the steps as best as possible.
Sent from my LG-H811 using XDA Forums Pro.

Hint: You can also flash tk gapps in twrp

meganoahj said:
Hint: You can also flash tk gapps in twrp
Click to expand...
Click to collapse
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.

DoLooper said:
Right! Did you do that--flash 5.2.0 UPDATE, RECOVERY then GAPPS before rebooting to 5.2.0 recovery? Bibikalka and I have been wanting to know if that'd been tested yet. thanks.
Click to expand...
Click to collapse
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)

meganoahj said:
Yes i done that, now you have The new lollipop Google Login when you add a Google account
And All works play Services updating and All fine (im on OS 5 with root,tkgapps,xposed framework)
Click to expand...
Click to collapse
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
 @bibikalka will also be glad to hear this! Thanks!

DoLooper said:
Please do "bother" me again. You're first to use this.
Please confirm you got into recovery OK. Also, do step 8 and post result from su command.
Don't worry about the superSU app right now. Just post above, then finish the steps, skipping running superSU. Please do not start back from the beginning.Thank you.
Click to expand...
Click to collapse
When I perform: option: adb shell
su
It returns 1|[email protected]:/ $
I'm going to try "option: adb install -r name_of_your_supersu.apk" here and see if that makes a difference.
Edit: That did it! SuperSu installed, Google Play Store/Services installed, and I'm good to go.

DoLooper said:
Hey, that's great! Couple questions:
You got Gapps from here? http://forum.xda-developers.com/android/software/tk-gapps-t3116347/post60944096#post60944096
Which package?
Do you know how much space you had left in /system after the update (and before you added anything else)?
Any chance you flashed Xposed at same time?
@bibikalka will also be glad to hear this! Thanks!
Click to expand...
Click to collapse
Yes i got gapps from There
Gapps: Pico Modular Package (Proper DPI Play Services)
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!

Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long

meganoahj said:
I flashed xposed after the reboot to fire os 5 (back to twrp method)
but i think you can flash xposed after the gapps!
And i dont Know the space free in /system cuz im installed gapps directly after flashing the Update!
Click to expand...
Click to collapse
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
meganoahj said:
Ah sorry i forget that after i flashed xposed framework anytime my fire boots i got the android is upgrading screen
10 seconds long
Click to expand...
Click to collapse
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)

Other than Kingroot taking forever and Xposed refusing to flash in TWRP everything went great and I was finally able to install all my apps from the Play Store on my wife's tablet following this guide.
Many thanks!

DoLooper said:
I meant how much space in /system after you got back to OS , after the upgrade and before deleting/adding any system apps. So, how much space in /system now?
I got Xposed same way as you and don't get that. Maybe it's a module you installed(?)
Click to expand...
Click to collapse
With gapps + xposed is 49.8 mb free in /system
I had the upgrading screen also without an Module

[How to] Upgrade to 4.5.5.1 (or other 4.5.x) with root in TWRP:

Update2: Updated for FireOS 4.5.5.1. Note that you can root 4.5.5.1 directly via Kingroot. With root, you could get TWRP to work, and re-install any FireOS 4 or 5 with all the goodies. The instructions to get TWRP working are here (you need to flash 4.5.3 bootloaders if you do not start with FireOS 4.5.3 !!!) : http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Update: I had a couple of knee-jerks, but realized that I can make TWRP say "full_ariel" (I've changed the string), which enables the standard Amazon update files to work !!! I did test the modified TWRP (and the attached zips), everything works fine.
This 4.5.5 update provides no perceptible difference with 4.5.4, and everything has been running smoothly for me for the past few weeks. So out of the general principle I do recommend upgrading!
If you are just joining us, and have a pristine Fire HD, head over here to get your fire rooted and TWRP installed [all steps up to and including 3) ] :
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
With TWRP installed, there is a quicker way to install 4.5.5, without changing the update file (in contrast to my earlier instructions for 4.5.4). This is a dirty flash, and will keep all the prior settings and programs (if you have not had GAPPS yet, see additional instructions below):
0) Turn off wireless (airplane mode)
If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Boot into TWRP, flash the attached 4.5.3_twrp_recovery_full_ariel_string.zip. Reboot to recovery (TWRP)
2) While in TWRP (this modified version self-identifies as full_ariel) :
a) flash the respective Amazon ROM 4.5.x update (the latest one?): http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102 (rename to zip before flashing)
b) Must do this (!!!) - flash attached 4.5.3_twrp_recovery_uboot.zip
c) flash attached make_space_v01_fireos4.zip to remove moffice and weather in order to increase space in /system.
d) flash Pico (Uni) GAPPS for KK http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html [if you did not have GAPPS before, skip this for now, and come back after Step 3) ]
e) wipe cache and dalvik
f) before reboot say yes to root
3) Boot into fireOS (wait for it to upgrade)
a) install SuperSu
b) disable OTA updates [in ES Explorer rename /system/priv-app/DeviceSoftwareOTA.apk to *apk_ ] - The script in make_space*zip already renamed this file automatically, so nothing to do here.
c) install Xposed. Note if you are using 4.5.5.1, you'll need to get the Xposed installer from here in order to address SDK version 19 error :
http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
d) install Busybox
Optional 4) : if you did not install GAPPS in 2), boot to TWRP, and install GAPPS
That's it! Whatever you had working before, should be working now the exact same way.
If you prefer a manual way where you repackage the 4.5.5 update file (and perhaps remove some apps from /system), see these instructions (the updater-script is the same) :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648

Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
This package is for "full_ariel" products: this is a "omni_ariel"
E:Error executing updater binary in zip '/sdcard/Download/update-kindle-20.1.5.5_user_455001420.zip'
Click to expand...
Click to collapse

Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...

bibikalka said:
Yep, indeed! I wonder if TWRP could be patched such that the device is being identified as "full_ariel" even when rooted. Otherwise repackaging these ROM zips is a chore ...
Click to expand...
Click to collapse
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...

Sario27 said:
Receiving error updating from 4.5.4 while attempting to flash the update in TWRP:
Click to expand...
Click to collapse
meatwad12 said:
Having said that... is there a version of 4.5.5 that will work with root? I can repackage myself I suppose, but it is a mess to navigate that script...
Click to expand...
Click to collapse
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.

I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.

DoLooper said:
I don't understand new title, "Upgrade to 4.5.5 (or any 4.5.x) with root in TWRP:" Isn't this just for upgrading to 4.5.5? The files are for 4.5.5, so you wouldn't use it to upgrade to 4.5.4, right? (Yes, I'm going to post a pointer to all the guides. The choices are confusing even me, and I practically live here!) Also, if you see fit, could you add [How To] to title so this stands out with other upgrade guides? yr friend, Do consistency-my-middle-name Looper.
Click to expand...
Click to collapse
Wow, you are a hard man to please I've put a few changes in there, trying to make it more clear.
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.

bibikalka said:
The procedure works for 4.5.4 as well, so that's why I try to keep things fairly generic.
Click to expand...
Click to collapse
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx

DoLooper said:
So would you say this supercedes http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613? Is this method "better?' thx
Click to expand...
Click to collapse
Potentially this will supersede this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
The difference is mainly not having to mess around with the update file (which has it's uses, if one wants to shrink the size of "system").

bibikalka said:
I've updated the instructions. As the first step, you flash the modified recovery (which says "full_ariel"). This modified recovery will accept the standard Amazon update file. After the update is done, I have you flash the standard TWRP back (just in case) together with 4.5.3 bootloaders.
Click to expand...
Click to collapse
This worked great for me. I have 4.5.5 running with the stock amazon ROM after following these instructions. Great work thank you!
---------- Post added at 03:19 PM ---------- Previous post was at 02:24 PM ----------
One problem...
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?

meatwad12 said:
I'm having a heck of a time trying to block ads in 4.5.5. I've tried the adb command pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.lockscreenupdateS ervice as mentioned in another thread but with no luck. Did Amazon change something in the structure of 4.5.5 that renders this method unworkable? Is there another way?
Click to expand...
Click to collapse
Did you put a space in "S ervice?" There is none, but it may display that way. So if you did, do it with no space and reboot afterwards if ads don't go away immediately. The other way is JMZ fire tool, but that does a chmod on ad folder and displays the "killed ads" message with every boot.
Please let me know if the pm block pm disable works or not. Thanks!

Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.

meatwad12 said:
Looks like I'm good! I tried it several different ways (block vs. disable; with space and without) and it appears to have taken hold after a reboot. We can chalk this one up to user error. Thanks for the response.
Click to expand...
Click to collapse
Or u can upgrade to lollipop. Ads are disabled by default on lollipop. Here is the thread to lollipop with root. http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950

I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition

mehmehmeh said:
I followed the instructions and tried flashing gapps before the initial boot into 4.54 and also after booting but I get the same error. "insufficient storage space available in system partition"
I am flashing this version
pa_gapps-modular-pico(uni)-4.4.4-20150308-signed.zip it is 39,105kb.
this is on the 8gb model of the kindle hd 7, not sure if the 16 has a bigger system partition
Click to expand...
Click to collapse
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3

flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again

mehmehmeh said:
flashed the newer 4.5.5. Will try later tonight, didn't get the amazon update disabled and woke up to a fire os 5 tablet. So I have to downgrade again
Click to expand...
Click to collapse
Well, as they say, practice makes perfect !
I am surprised it managed to install itself with TWRP present instead of the stock recovery ...

Can you please upload the attachments to a file hoster cause the servers from xda are slow 14 kbps and downloads cancels!

bibikalka said:
Did you flash the older 4.5.4 ? Or the newer 4.5.5 ?
Can you check how much free space you have in /system as is? (DiskUsage app in the store)
In any event, and easy quick hit (20Mb) is to remove something like /system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
You can remove more, as per this :
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
Click to expand...
Click to collapse
Thanks for the tip!
Ran into the same issue while trying to upgrade my rooted 4.5.3 gapps Firehd 7..

Mhm Ok now I'm running into issues when trying to update the google play services, it always fails saying "not enough space available".
http://forum.xda-developers.com/showpost.php?p=61008736&postcount=3
I've moved all the odexed system APKs mentioned in this post to /data/apps and I have 1.5gb free on the "sdcard".
:/
*Edit*
Nvm, found the reason...it's because I allready had gapps installed through jmz's tool and it blocked play services updates from being installed, because back then a play services update would break the entire thing again.
So I had to do these additional steps from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
Click to expand...
Click to collapse
@op maybe include it in your updated guide for ppl who allready had gapps and used jmzs handy tool a couple months ago.

[ROOT] With Kingroot and Tools + Play Store + Launcher (Newbie Friendly)

This explains how to use the Fire HD tools (for Windows) to root and install Gapps and a custom launcher on the Fire HD 6 or 7.
Note: If your tablet has an SD card slot, it's a 2015 Fire. Don't use this guide. Go to the 2015 Fire forums.
TURN OFF WIFI NOW TO PREVENT AN UPGRADE!
BEFORE YOU START
Check out the Root Tut so you know about the alternative to this guide. Once you're rooted, this TWRP method lets you upgrade and install Gapps, Xposed and goodies @bibikalka provides all in one go. This is the only way to get rooted OS 5.1.2.1. If you're already rooted, use that tutorial to upgrade.
[*] Read about rooting and updates so you'll understand how it works when you get to the rooting step, and can decide now if you'd rather root OS 4 and upgrade in TWRP.
An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
OS 5.1.2: There are no commands to prevent an upgrade from installing before you're rooted. Amazon says that upgrades don't install while the device is being used, but be aware that there's some risk. To minimize the risk, be sure your OS is rootable and never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.)
OS 4.5.3: There ARE commands to prevent an upgrade from installing on unrooted OS 4, which the Kingroot tool runs before you turn on wifi to root. This means you can sideload OS 4.5.3 and root without any risk of updating. You can then upgrade with root in TWRP, as explained in the root tut above.
FWIW, Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
HOW TO ROOT AND SET UP THE FIRE HD​
Install ADB Drivers if you don't have them.
Illustrated Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other Options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
[*] Look at OS and build date in Device Settings>Updates and determine if you need to install OS 5.1.2.
OS 5.1.2.1 (shows OS 5.1.2, Build Date: March 2016):
Install OS 5.1.2. (5.1.2.1 can't be rooted.)
OS 5.1.2 (shows OS 5.1.2, Build Date: February 2016):
Install 5.1.2 If tablet is the least bit unstable or if you just want a clean start.
OS 5.1.1 or earlier:
Install OS 5.1.2. to upgrade.
OS LATER THAN 5.1.2.1:
DO NOT install 5.1.2. Downgrades often brick tablets! I'll change this message after someone tests.
You may be able to safely downgrade to OS 4.5.3, root, and then upgrade in TWRP per bibikalka's root Tut, above. Before trying this, make sure the post says it's safe for the OS you're on.
[*] If you need OS 5.1.2, follow these instructions:
TURN OFF WIFI BEFORE YOU START.
OS 4.5.5 and below, read this:
You have 3 choices:
A - Use the root tools to root now and block updates, then upgrade in TWRP (and flash Gapps, etc) per the root Tut
B - ADB Sideload OS 5.1.2 (below)
C - Upgrade From Device to Developers preview then upgrade again to OS 5.1.2.
To Upgrade From Device to Developers preview:
1. Download the Developers Preview here: https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
2. Follow the steps below to "Upgrade from Device" but install the Developers Preview instead of OS 5.1.2.
3. Now repeat the steps and install OS 5.1.2
OS 4.5.5.1 through OS 5.1.1:
You have 2 choices:
A - ADB Sideload OS 5.1.2 (below)
B - Upgrade From Device to OS 5.1.2 (easiest if you don't already have drivers for sideload mode)TO UPGRADE FROM DEVICE
I think this wipes your data, (Sorry, just don't remember). Suggest you copy to PC anything that can't be replaced from the cloud.
Get OS 5.1.2 update here: https://kindle-fire-updates.s3.amaz...HBV/update-kindle-20.5.4.2_user_542168620.bin
Confirm file name: update-kindle-20.5.4.2_user_542168620.bin
Connect to computer so you see the contents of the Fire HD /sdcard dir (Internal Storage) in Windows Explorer
Copy the update *.bin file onto /sdcard. Don't put it inside any folder
Go to Settings/Device/Updates and tap Check for Updates
It should then show that [*.bin file] is ready to install
Tap Update Now
[Wait a long time for installation and reboot]
OS 5.1.2 and 5.1.2.1: ADB SIDELOAD
DON'T DO THIS ON ANY OS HIGHER THAN 5.1.2.1 (March 2016). YOU WILL PROBABLY BRICK YOUR TABLET!
A factory reset is part of the steps. Backup anything that won't reinstall from the Play Store or Appstore. If you're upgrading from an earlier OS 5, you can skip the reset (at your own risk)! If you're downgrading from 5.1.2.1, do it!
NOTE: There's a sideload tool in the FIREHD_TOOLS jobs folder that guides you through this process. It may not run on all Windows, but it'll fail before doing anything so no harm in trying it. To give it a spin, put the OS 5.1.2 bin file into the adb_sideload folder and run sideload.bat. You'll be prompted to install drivers (step 8, below.) but it does most of the heavy lifting. If you try it, please post opinion/result! Thanks!
KEEP WIFI OFF
Get OS 5.1.2 update here: https://kindle-fire-updates.s3.amaz...HBV/update-kindle-20.5.4.2_user_542168620.bin
Confirm file name: update-kindle-20.5.4.2_user_542168620.bin
Put it into your pc folder with adb.exe
Open a CMD window from that folder.
Hold Power and Volume-up buttons to boot to the recovery menu
Use volume key to select Factory Reset and press Power [wait for reset]
Use volume key to select "apply update from adb" and press Power
[See yellow message on tablet screen]
Install drivers for sideload mode just as you did for regular OS mode. See hidden text or this link.
Open Device Manager and:
(1) Find KFARWI (or KFASWI) under "Other devices." (If you don't see KFARWI/KFASWI under "Other," disconnect/reconnect and look again.)
(2) Right-click and select "Update Driver Software." [see Update Driver Software screen].
(3) Click "Browse my computer" and then "Let me pick from a list . . ." [see Select your device type . . ."]
(4) Click Android Device. [see "Select the device driver you want . . .]
(5) Select your usual composite adb driver from the list, press Next, and say yes at warning screen. [see "Windows has successfully updated your driver software"]
(6) In CMD window, run adb devices and confirm you see your device ID and "sideload," like this:
List of devices attached
SERIALNUMBER sideload
If you don't see serial number, reboot tablet and computer and repeat "adb reboot recovery" and "Apply update from ADB" steps. Device should now be recognized.
In CMD window type: adb sideload <name of update bin>
[Wait a long time]
Do another Factory reset
Reboot to OS.
[Long startup]
Confirm Device Settings>Updates shows OS 5.1.2, build date February 26/27, 2016
Download the Fire HD tools using the DOWNLOAD FROM AFH link on this post and extract to desktop
In tablet Security Settings: Allow apps from unknown sources
In Device Options, tap serial number several times to open Developer Options and confirm ADB is enabled
In the Fire HD tools, run RUNME.bat and choose INSTALL KINGROOT
Job prompts you through rooting, blocks OTA and replaces Kingroot with SuperSU.
Run the PLAY STORE tool OR follow the steps below to install Gapps in TWRP.
[EDIT June 1: The Play Store tool suddenly broke. I have the fix and will update in next few days. Until then, use the TWRP method.]
The Play Store tool is easier and the Play Store works fine, but the "Google Settings" app doesn't.
(Force close when you tap gear icon) You can get to everything in Google Settings through in-app settings
or online at your Google account (https://myaccount.google.com) so it isn't required, but if you know and love it, install Gapps in TWRP.
Besides installing Gapps, the TWRP method installs scripts so you can boot TWRP from your device. Read Bibikalka's posts for info.​
HOW TO INSTALL GAPPS IN TWRP
Thanks bibikalka for cooking up the scripts that make this easy!
1. Download Bibikalka's WindowsAutoTWRP_v03.zip to PC, hit Thanks, and then extract zip on PC.
2. Download GAPPS (tk_gapps-modular-pico(uni)-5.1.1-20150920-signed.zip) and put it into WindowsAutoTWRP_v03\gscript folder
3. Confirm folder contains both the gapps zip and the recovery_uboot zip for your OS:
. . Currently s5.4.1_1133_stock_recovery_uboot for OS 5.1.1, 5.1.2, 5.1.2.1
4. Run 1_FIRE_HD_4TH_GEN_TWRP.bat (in WindowsAutoTWRP_v03) and follow the prompts.
. . [1st prompt: If you just rooted, adb debugging is enabled. You have the bootloader pack. You don't need fastboot drivers.]
5. At end of script, look at "Verify checksums !!!" in output and confirm checksums match.
. . If they DON'T match: Leave tablet like it is and post error in bibikalka's thread (the link in step 1).
. . If they DO match: Use ES File explorer to go to sdcard/gscript on device and confirm your 2 zips are there.
. . . . . If they ARE NOT, post the problem in this thread, saying which file is missing. Otherwise . . .
6. Press [Enter] in the script window to close it.
7. Open a new CMD window from the WindowsAutoTWRP folder and enter the command: adb reboot recovery
. . [Tablet BOOTS to TWRP]
8. In TWRP,
a. Tap Install, browse to /sdcard/gscript, tap Gapps zip and swipe to install [Wait for "Successful"]
b. Tap Home, tap Install and install the recovery_uboot zip [BE SURE TO DO THIS!]
c. Tap Reboot System
NOTE: After you sign into Play Store and know it works, you can delete the Gapps zip file from /sdcard/gscript.
Turn on wifi and sign in to Play Store.
Run INSTALL NOVA LAUNCHER to install Nova and disable the stock launcher.
You can install a different launcher later if you want it
If you have ads, run BLOCK/UNBLOCK and choose BLOCK ADS
If the guide and tools helped you, please hit Thanks. ;)
DONE!
.

Wow, thanks a lot, DoLooper! I'll try this when I get home.
The only thing, the before you start section and the sections below that (main process?) state the orders of root, then upgrade to OS 5.1.2, but in the how to root section, it says "You should now be running OS 5.1.2". Contradicting.
FYI it was me, I would just combine the before you start and other sections, making it all part of the process, simply saying "if you haven't rooted, or installed ADB, do this, otherwise go to...". But that's nitpicking.

Slickone_ said:
Wow, thanks a lot, DoLooper! I'll try this when I get home.
The only thing, the before you start section and the sections below that (main process?) state the orders of root, then upgrade to OS 5.1.2, but in the how to root section, it says "You should now be running OS 5.1.2". Contradicting.
FYI it was me, I would just combine the before you start and other sections, making it all part of the process, simply saying "if you haven't rooted, or installed ADB, do this, otherwise go to...". But that's nitpicking.
Click to expand...
Click to collapse
I don't mind the nitpicking. But, Before you Start (at top), says: (2) install drivers, (3) Check your OS and build date in Device Settings and install OS 5.1.2 if needed. Then it lists all OS's and tells you if it needs OS 5.1.2 (which almost every OS does). Is this not clear or easy to miss? Or is step 1 throwing you? That's just so people know there's an alternative with a wider range of options.

DoLooper said:
I don't mind the nitpicking. But, Before you Start (at top), says: (2) install drivers, (3) Check your OS and build date in Device Settings and install OS 5.1.2 if needed. Then it lists all OS's and tells you if it needs OS 5.1.2 (which almost every OS does). Is this not clear or easy to miss? Or is step 1 throwing you? That's just so people know there's an alternative with a wider range of options.
Click to expand...
Click to collapse
I just mean that the order of both sections are root, then upgrade OS. But in the root section, the directions order is upgrade OS, then root.

Slickone_ said:
Wow, thanks a lot, DoLooper! I'll try this when I get home.
The only thing, the before you start section and the sections below that (main process?) state the orders of root, then upgrade to OS 5.1.2, but in the how to root section, it says "You should now be running OS 5.1.2". Contradicting.
FYI it was me, I would just combine the before you start and other sections, making it all part of the process, simply saying "if you haven't rooted, or installed ADB, do this, otherwise go to...". But that's nitpicking.
Click to expand...
Click to collapse
Good suggestions here and in your PM. I reformatted. Think it's better now. Thanks!

Many thanks for the above, worked like a treat.
However I may have over googlified my HD6 as I now have a couple of issues. After installing a bunch of google apps and updating Play Services i have the following issues.
The HD6 wont switch off - not a big issue.
I cannot login to the play store, the circle just keeps spinning round. I can access Google Play Music no issue so I am puzzled.
I have tried to login to the Find My Android app but it keeps rejecting the password which I know is correct, I have installed the google keyboard and I may try and return to the amazon version and see if this error persists.

mykey38 said:
Many thanks for the above, worked like a treat.
However I may have over googlified my HD6 as I now have a couple of issues. After installing a bunch of google apps and updating Play Services i have the following issues.
The HD6 wont switch off - not a big issue.
I cannot login to the play store, the circle just keeps spinning round. I can access Google Play Music no issue so I am puzzled.
I have tried to login to the Find My Android app but it keeps rejecting the password which I know is correct, I have installed the google keyboard and I may try and return to the amazon version and see if this error persists.
Click to expand...
Click to collapse
First try rebooting. If no help,go to recovery (hold power and volume+) and Clear Cache. See if those make a difference. Just wondering: What OS did you start from? Did you install/reinstall OS 5.1.2 AND do a factory reset at start? thanks.
EDIT: For the play store, go to settings/apps/all and scroll to play store. Hit force stop, then clear cache. Clear cache in Google services, too. Try opening play store.

Just to update the Purity app which loaded with Kingroot has purified all the Google apps I had run so I had to unblock each one within the Purity app. Is it safe to install it if you even can.

mykey38 said:
Just to update the Purity app which loaded with Kingroot has purified all the Google apps I had run so I had to unblock each one within the Purity app. Is it safe to install it if you even can.
Click to expand...
Click to collapse
Install what? After rooting you were asked if you wanted to remove Kingroot. Did you say no? That removes Purify, too, so you shouldn't even have it!
EDIT: Guess you meant uninstall. I really know nothing about Purify. You can run the tool to replace Kingroot (and uninstall Purify) now, but I can't say how it will affect your "purified" apps. Worst case, you have to reinstall OS 5.1.2 and start again, which might not be a bad idea.

mine keeps failing when trying to sideload. Im on 5.1.2 i guess later model cause i cant root so i tried to downgrade. it gets to around 50 percent and fails. i get e:failed to verify whole-file signature, E: sigtanture verification failed
instalation aborted. i tried the automatic sideload as well as the manual sideload and same results. Im trying to redownload file and see if thats the issue.
---------- Post added at 05:01 PM ---------- Previous post was at 04:45 PM ----------
after redownloding it did same thing fails right at 47 percent

pitmanr2003 said:
mine keeps failing when trying to sideload. Im on 5.1.2 i guess later model cause i cant root so i tried to downgrade. it gets to around 50 percent and fails. i get e:failed to verify whole-file signature, E: sigtanture verification failed
instalation aborted. i tried the automatic sideload as well as the manual sideload and same results. Im trying to redownload file and see if thats the issue.
---------- Post added at 05:01 PM ---------- Previous post was at 04:45 PM ----------
after redownloding it did same thing fails right at 47 percent
Click to expand...
Click to collapse
Please run the Device Info tool and tell me what device it shows at the top and what it shows for "BUILD number" and "FireOS version"

what is the device info tool

pitmanr2003 said:
what is the device info tool
Click to expand...
Click to collapse
In the tools, when you run RUNME and see the menu, #8 is "Device Info."

ok i see. build number is 542169020 fireos is 5.1.2.1

pitmanr2003 said:
ok i see. build number is 542169020 fireos is 5.1.2.1
Click to expand...
Click to collapse
What tablet? At the top?

this was a previously rooted tablet and i had dissabled ota, but somehow it updated itself. i have 2 tablets and did them both the same way. the other one never ota'd , but this one did for some reason. i have been waiting for a fix and no luck so far downgrading it.
---------- Post added at 06:21 PM ---------- Previous post was at 06:18 PM ----------
hold on i was trying it again. it always fails at 47 pecent.

here is a snipit

pitmanr2003 said:
this was a previously rooted tablet and i had dissabled ota, but somehow it updated itself. i have 2 tablets and did them both the same way. the other one never ota'd , but this one did for some reason. i have been waiting for a fix and no luck so far downgrading it.
---------- Post added at 06:21 PM ---------- Previous post was at 06:18 PM ----------
hold on i was trying it again. it always fails at 47 pecent.
Click to expand...
Click to collapse
If you're sure you've got a 2014 Fire HD (not 2015 Fire), I have no idea why sideload is failing. I'd google it as well as ask in the Q&A forum. Post the messages you're getting any info tablet/rooting history that might assist someone in helping you.

pitmanr2003 said:
here is a snipit
Click to expand...
Click to collapse
OK. The tools are for 2014 Fire HD. You've got the 2015 Fire. Tools will work on the Fire, but you need 5.1.2 update from here: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
The 2015 Fire forums are here: http://forum.xda-developers.com/amazon-fire

yes it is a 2015. i just got it at christmas time. thanks i will try that. didnt realize this was for older gen
---------- Post added at 06:43 PM ---------- Previous post was at 06:40 PM ----------
trying it now. im lucky i didnt brick it i quess
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
woohoo worked that time. rebooting and hopefully i can get root back now. thanks alot bro