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.

OS 5.0 + ROOT + GAPPS + Play Store VIDEO TUTORIAL

Please DO NOT use this guide anymore due to bricks. Instead use an up to date guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
1.Install USB ADB drivers: https://www.youtube.com/watch?v=CyJlmTtLsIg
Download Software version 4.5.3: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
Reboot into recovery: "adb reboot recovery"
Enter sideload mode from recovery
Install v4.5.3: "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
Wiipe data/ factory restet from recovery
Reboot & keep wifi off so that it does not re-update
Disable ota updates with "adb shell pm block com.amazon.dcp" and "adb shell pm block com.amazon.otaverifier"
Turn on wifi
Download kingroot from http://www.kingroot.net/ onto device
Root with app
Test root with "adb shell" and "su"
Download TWRP IMG: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
Check md5sum: 4fefd8b46ca97a2b66e4c8852d4c3396
Push recovery to device with "adb push openrecovery-twrp-2.8.6.0-ariel.img /data/local/tmp"
Go into root shell with "adb shell" and "su"
Go to /data/local/tmp/ directory: "cd /data/local/tmp/"
Install TWRP: "dd if=openrecovery-twrp-2.8.6.0-ariel.img of=/dev/block/mmcblk0p7"
Test TWRP with "adb reboot recovery"
Boot back up
Download 5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Download 5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
Download pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Download make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Move firmware, recovery, gapps, and make_space zip onto Fire internal storage
Rename 5.2.2 firmware to a .zip file instead of a .bin file so TWRP recognizes it
Reboot into TWRP: "adb reboot recovery"
STEPS 28-33 MUST BE DONE IN ONE SESSION
Do another factory reset
Flash 5.2.2 firmware
Flash 5.2.0 recovery
Flash/run make_space zip to clear up system space
Flash Pico GAPPS zip
Choose reboot into recovery from TWRP and tell TWRP that you would like to install superSU
Reboot device and wait for it to boot up (will take about ten minutes)
After booted up, disable ota updates with "adb shell", "su", "pm disable com.amazon.otaverifier", and "pm enable com.amazon.dcp"
Update SuperSU from Play Store, open it and choose to install normally
Root, GAPPS, and Play Store should all be working now
Click to expand...
Click to collapse
Notes:
Do not try to re-flash TWRP the same way you did on 4.4.3. It will not work
Click to expand...
Click to collapse
Links & Downloads:
•XDA Guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
•USB driver tutorial: https://www.youtube.com/watch?v=CyJlmTtLsIg
•4.5.3 software: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
•KingRoot: http://www.kingroot.net/
•TWRP image: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
•5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
•5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
•pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
•make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Click to expand...
Click to collapse

Detailed tutorial
Will try later today.

Thanks a lot for the video. Used it and got everything working no problems!

argrr101 said:
Thanks a lot for the video. Used it and got everything working no problems!
Click to expand...
Click to collapse
Awesome to hear. Enjoy
Sent from my KFARWI using Tapatalk

powerpoint45 said:
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
Notes:
Links & Downloads:
Click to expand...
Click to collapse
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update

2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Sent from my KFARWI using Tapatalk

@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?

2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
powerpoint45 said:
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Click to expand...
Click to collapse
Only that a search turns up lots of hits.

argrr101 said:
@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
I'm using a custom one. If you have root just install your custom Launcher, go into adb shell, type "su", and then "pm disable com.amazon.firelauncher"
Sent from my SPH-L710 using Tapatalk

argrr101 said:
[MENTION=4469251]Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
This is for latest OS 5.0.1 (5.2.2u2). Be sure to install custom launcher first. Need to be in SU.
pm disable com.amazon.firelauncher

Thanks, got Nova Launcher up and working.

cxm170 said:
Will try later today.
Click to expand...
Click to collapse
works like a charm
. thanks

Excellent write-up I didn't even bother watching the video... My hd6 is now working as it should!
One note - I had to register with both Amazon and Google via wifi before I could update SuperSU and disable ota updates through adb. Not sure if I did something wrong, but that's how it ended up working for me.

Hello, I have tried this tutorial but I'm unable to downgrade to 4.5.3
I get a signature verification error when sending the file; the exact error from the recovery logs is:
Code:
I: failed to verify against RSA key 0
E: failed to verify whole-file signature
The installed OS version is 5.0.1 on a Fire 5th generation.
Does anyone have a solution for this problem?

Get the same error :
E:failed to verify whole-file signature
E: signature verification failed
Installation aborted
Can smone help pls?

I followed this guide to root my fire, it worked.
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152

wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours

george9584 said:
wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours
Click to expand...
Click to collapse
Man I am glad I read this post... I have a Gen 4 HD6 that came with 4.5.5, and I would LOVE to get root and GAPPS and make this thing work the way it should, but these tutorials are confusing as hell...
Do we use ADB+Fastboot or do we have to install ADB from the SDK? There is NO mention of this in the video tutorials... I am confused.
Not everyone uses Linux. I am on a Windows box here at work and would love to make this happen... Can anyone shed light?

Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.

user0x80 said:
Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.
Click to expand...
Click to collapse
Ok so first off thank you so much for taking the time to try and help, and forgive me for being needy.
In your post you mention following Imma Wake's video which I tried to do, but the very first step is a brick wall. The YouTube video which supposedly shows how to upgrade to the 5.0 Developer preview has been removed. It is no longer there, so that very crucial first step is one that I cannot take.
Next, in your post, you reference upgrading the Kindle HD6 using both the 5.0 Developer preview AND the 5.01 Developer preview which has me totally confused. I do not see any videos on Imma Wake you tube channel referencing the 5.01 Developer preview. The last thing I want to do is brick my brand new Kindle...
SO, once again, I am back here at square one, stuck. Any chance you can point me to the quick and easy method of upgrading to 5.0 Developer so I can get past that step? I have signed up on Amazon and the developer page indicates that my device will be upgraded within 48 hours, but I am sitting here with time on my hands today and really wanted to give this a shot today.
Thanks.

[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

[Guide]How to Root Your Pixel 3a and Install Magisk - Android 9 - 12

Edit - just an FYI for complete transparency. I have moved from the Pixel 3a XL to the Pixel 6. I no longer own my Pixel 3a XL. While I've been told (thanks @AndDiSa) that the root process for Android 12 is the same as it historically has been, I no longer can test things myself. (The root process for the Pixel 6 is different and more complicated than this phone). If you run into any problems or issues, please post in this thread and someone will hopefully be able to answer them.
I'm assuming you understand how to use ADB on your computer. If you need assistance with installing or using ADB, please refer to this XDA article for more information. However, here are some common issues that people have with ADB if it doesn't work initially for you. 1) Check the Android System Notification that appears in your phone's notifications after you plug in your USB cord. Your phone probably defaults to "No data transfer" and you need to change it to "file transfer" to allow the phone to connect. 2) Make sure you have USB debugging turned on in the Settings/System (advanced)/Developer options. 3) If this is your first time using this phone/computer combination, you will have to accept the connection when it pops up on your phone.
You also need an unlocked bootloader to complete these steps. If you need assistance with unlocking your bootloader, here is decent set of instructions. Those instructions are based on the Pixel 3 phone, but the steps are the same for the 3a devices.
Here are the official Magisk installation instructions. I will walk through them to help everyone understand them. Please note that while TWRP does work with Android 9 (Pie), it does not work currently with Android 10 or 11. If you are still on Pie for some reason you can choose either installation option, but if you have moved to a later Android version, you must use the "Boot Image Patching" installation method.
Custom Recovery Installation Method - (available for Android Version 9/Pie only because TWRP does not work currently with the Android 10/11)
This is the easier installation method IMHO, but it does require using TWRP. If you don't know how to get TWRP for the Pixel 3a, please refer to the official TWRP for Pixel 3a thread
Step 1 - Download and install the Magisk manager app on your phone. (link to the latest stable version can be found here).
Step 2 - Using the Magisk manager app, select "Install Magisk" and select the "Download Zip Only" option. This simply downloads the installation zip to your phone's download folder. It doesn't attempt to install anything.
Step 3 - Boot into TWRP - (because TWRP is not permanent on the stock Pie OS, we must follow these instructions each time we want to boot into TWRP).
Step 3a - Download the latest TWRP image for the 3a to your computer (not your phone) from the official TWRP for 3a thread.​Step 3b - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".​Step 3c - Boot your phone into the bootloader (type the command "adb reboot bootloader").​Step 3d - Boot into TWRP using this command, "fastboot boot twrp-3.x.x-x.img" (where "twrp-3.x.x-x.img" = whatever the name of the TWRP download is). Please note you are not using the "flash" command as we are not permanently installing TWRP.​Step 4 - Once the device boots into TWRP, select "Install" and then find the Magisk.zip download from step 2. Swipe to confirm the installation
Step 5 - After the installation is complete, simply reboot system.
Step 6 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 7 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed under the "Taking an OTA Update" section below
The Boot Image Patching Installation method - (the only method currently available under Android 10, 11 or 12, but it also works with Pie).
Use this method if you are on Android 10 or 11 or you are on Android 9/Pie but you don't want to or can't use TWRP.
Step 1 - Obtain a stock boot.img file for the OS version/update that you are currently on. The easiest method is probably to download the applicable full stock image directly from Google. Unzip the files and unzip the second folder and you should find the boot.img file inside.
Step 2 - Copy the stock boot.img file to your phone's storage - probably to /sdcard or to /sdcard/downloads
Step 3 - Download and install the Magisk manager app on your phone. (link to the latest version can be found here). If you are early in the Android 12 cycle, you probably need to use a Canary build of Magisk.
Step 4 - Using the Magisk manager app, press "Install --> Install --> Select and Patch a File" - select the stock boot.img file that you put on your phone in step 2.
Step 5 - Magisk will modify the stock boot.img file and create a patched boot image file. It will save this modified file at "sdcard/Download/magisk_patched.img"
Step 6 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 7 - Copy the patched boot image from your device to your PC and the adb folder. If you can’t find the file on your phone via MTP or Windows Explorer, you can pull the file by typing the command "adb pull /sdcard/Download/magisk_patched.img" - Please note, I would suggest double checking the "file modified date" prior to moving the file. Be sure to only move the file if it was last modified on the date you are doing this. I've had a strange situation before where the newly modified file didn't immediately show up and the file showed a modified date of the previous month. If you flash an old version, your phone will bootloop.
Step 8 - Boot your phone into the bootloader (type the command "adb reboot bootloader").
Step 9 - Flash the patched boot image to your device using this command, "fastboot flash boot magisk_patched.img"
Step 10 - Reboot (using command "fastboot reboot").
Step 11 - Enjoy your rooted phone and install any Magisk modules that appeal to you
Step 12 - Be sure to turn off the "Automatic System Updates" setting found in Developer settings (Settings /System (advanced) /Developer Options). This will prevent the phone from automatically installing an OTA update and instead allow you to follow the steps listed next.......
Taking an OTA update in the future (if you used this method to install Magisk).
Taking OTA updates is very easy with the Pixel devices because of their A/B partition system. It allows us to uninstall Magisk, take the OTA update, and reinstall Magisk - all from the phone and all without rebooting during the process. Here are the offical Magisk OTA instructions. I will go through the steps to help explain them.
Step 1 - In the Magisk manager app: Click “Uninstall” then “restore images”. DO NOT REBOOT or press the reboot button.
Step 2 - Download and install OTA (in your phone's Settings/System/System Update). DO NOT REBOOT or press the reboot button.
Step 3 - Open the Magisk manager app and click “Install” next to Magisk (usually it says "Magisk is up to date") then “Install to second/inactive slot (After OTA)”
Step 4 - Press the Reboot button in Magisk.
That should be all it takes to install an OTA and keep root.
Please note, we are getting reports that users are getting notifications that an OTA update has been installed even when they have "Automatic Updates" turned off. If this happens to you, don't reboot the phone which is suppose to be the final step in the update process. Instead, follow the above instructions on taking an OTA update, but start in step 3. In other words, you shouldn't have to uninstall Magisk because the update has already been installed. All you need to do is install Magisk to the "second/inactive slot (After OTA)”. After completing that step, you can reboot your phone to complete the update process. Be sure to post your experiences in this thread to let us know if this process works or not.
Just remember that many custom parts (like kernels and Magisk modules) may need to be updated to any new OTA version. Please be sure to check out the forums for each custom kernel or module that you may want to install to ensure it has been updated to the lastest OS version. Don't assume anything or you may find yourself in a bootloop.
If you find yourself in a bootloop after upgrading an already rooted phone
If you find yourself in a bootloop after updating to a new OS version and flashing the magisk_modified boot.img again, it is likely due to an installed Magisk module not being compatible with the new update. To uninstall all Magisk modules to fix the bootloop, follow these steps:
Step 1 - Connect your phone to the computer you use ADB on.
Step 2 - In ADB type the command "adb wait-for-device shell magisk --remove-modules"
Step 3 - Start your phone again or wait for it to go through another bootloop cycle.
Step 4 - as soon as ADB is available (which occurs even during a bootloop) the command will activate, the modules will be removed, and the phone will reboot.
If the normal OTA method isn't working - sideload the OTA update
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on a couple Android 10 images, but most do not require this step.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, while the initial boot is usually pretty quick, it can take longer. I've occasionally seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that sometimes it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take an regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just need be patient and let the phone complete the process.
My rant about using these "Pre-patched Boot image" files
I started this thread during a period of time where there was a another thread on this forum started by pbanj that showed users how to root their phone by using some pre-patched boot image files. This method is not the generally accepted method and while it works, there are major shortcomings with it (see explanation below). Because it was the only root thread available at the time and he only showed the "pre-patched boot image" method, many people blindly followed his directions only to be confused when it came time to update the software on their phones. I wrote this thread in an effort to show people the official Magisk installation method. Pbanj has since updated his thread and it now includes the preferred method as well. With his edits, the two threads are sharing the same information now, although Pbanj thread still offers people the "pre-patched boot image" method (which I don't recommend people using).
EDIT - Yet another thread pushing a pre-patched root method has been started. It suffers the same issues as listed below.
Shortcomings with using the "pre-patched boot image" method.
As I already mentioned, there is a huge shortcoming with using the "pre-patched boot image" method described in the other root thread. Because he provides a pre-patched boot.img file, you skip some normal installation steps. In the end you have the exact same patched file (which is why his method works), but you cripple the system when it comes to taking any future OTA. That's because the first step in taking an OTA update is having Magisk reflash the stock boot.img effectively uninstalling itself. This step fails if you used his pre-patched boot image method because you skip the step where Magisk creates the backup of the stock boot.img that it needs to uninstall itself.
I already used the "pre-patched boot image" method to gain root. What can I do?
First, let me clarify and say that there is nothing wrong with your phone or root privileges. Your phone will work exactly as expected and root and Magisk will work exactly as expected. That being said, in the near future you will want to update your phone to the latest Android update and this is where the "pre-patched boot image" method is much more cumbersome. The best option is to simply undo his root method and re-root using the method described above. To do this, flash the correct stock boot.img file to your boot partition and then follow the steps above to reinstall Magisk. Jbanj has confirmed this method will work. The other option is just wait until you need to take an update and then sideload the OTA update following the instructions above. This will remove root and you can then follow one of the two methods to obtain root as outlined in this thread.
Notes
- Please be sure you are on the latest adb and drivers which can be found here.
- You do not need to keep the stock boot.img file (from step 2 of the Boot Image Patching method) on your phone after completing these steps. Magisk saves the stock boot.img backup at /root/data in a file with the name "stock_boot_XXXXXXXXXXXX.img.gz"
Thanks to.......
@ZVNexus for getting TWRP working on the 3a and 3a XL phones
@topjohnwu for making Magisk what it is today

Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!

You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk

jmtjr278 said:
You know there are more ways to skin a cat, right? This is another method to acquire root. I don't think you need to bash the work that pbanj has done. He provides modified boot.img and also offers help on getting it working. I think acting like your method is the only acceptable way to gain root is extremely pompous and arrogant.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......

sic0048 said:
I don't think that this method is the only way to get root, nor is this "my method". It is however the method spelled out by the Magisk developers and it is the only method that uses Magisk strengths when trying to take an OTA update.. I'll simply leave it at that......
Click to expand...
Click to collapse
Sure. It's the way I do it also. But show some class and don't call out other, helpful members in this fashion and crap all over what they do. I have seen your posts and know your a helpful members also, let's respect each other and be classy.
Sent from my Pixel 3a using Tapatalk

@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?

Bankuu said:
Made it to step 7/8, went to reboot, and entered bootloop. Not sure exactly what happened, gonna fix this and give it another go.
EDIT: Should I be flashing in fastboot or recovery mode?
EDIT 2: Working! Thanks!
Click to expand...
Click to collapse
I've edited the steps and added a few more going into greater detail to try and make it even clearer for users. Let me know if you have any suggestions.

alliance1975 said:
@sic0048
Thank you. I got to admit it was pretty tense for a while. Thanks to you I made it. Had to do a sideload, had to do some stupid things but I made it. Now, I got through all the steps and I have two items; Having done this transition can I now do the magisk-uninstall-restore images for all future OTAs and is step 9 performing the magisk install process a second time?
Click to expand...
Click to collapse
You should be able to use the normal Magisk OTA update instructions for future updates.
I've updated the thread and I think the "step 9" you listed isn't the same anymore, but I think I understand your question. Actually I think my original instructions were inaccurate as far as that step. I've always gone back into Magisk after flashing the modified boot.img and I thought I hit install to install the Magisk framework (if that is the correct term). But after reading some other guides, I think my memory is incorrect and you don't really have to install anything after the flashing portion of the steps.
Once you reboot after flashing, that should be all you have to do. I'll uninstall Magisk here in a while and walk through the steps myself to ensure this is correct howeve.

The OP should be made a sticky.

Cool guide. Can the method be applied to Q beta 4 ?

MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
No root for Android q on our devices yet afaik.
Sent from my Pixel 3a using Tapatalk

@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?

alliance1975 said:
@sic0048
Should we keep the stock boot image copied to the phone storage in step 2? Is this where Magisk will look for it to do an image restore?
Click to expand...
Click to collapse
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"

sic0048 said:
You do not need to keep the stock boot image that was copied over in step 2. Magisk saves the backup of the boot.img at /root/data. It will have the name "stock_boot_XXXXXXXXXXXXXXXXXXX.img.gz"
Click to expand...
Click to collapse
Thanks sic0048. You put up with my dumb questions and helped make my pixel 3a a great phone.
Respect.

Edited - now that jbanj has confirmed we can simply flash the stock boot.img file to the boot partition and start over, the post I originally had here is pointless.
Alliance's question got me to thinking.....
Since Magisk saves the stock boot.img backup at /root/data in a file named "stock_boot_XXXXXXXXXXXX.img.gz" I wonder if we can't simply share a backup file with someone that used jbanj "modified boot image" method and have them copy it to that location. I suspect Magisk will then allow the normal OTA update prceedures to work.
I can share the backup file that I have, but it is for the 3a XL model, Android version 9 (Pie) and the June 5, 2019 security update. That means it will be next month before there will be another OTA update pushed out.
If someone is still on the OEM March update and rooted using the normal directions and is willing to share their backup file, we might be able to try it sooner.
Unfortunately I don't know if Magisk modifies the backup to be some sort of unique file. I doubt it, but I don't know for sure. Of course worse case scenario is that it doesn't work and the person has to flash the OTA manually - which is no different than what they would have to do anyway. So there really isn't much risk in trying this.

MPAI said:
Cool guide. Can the method be applied to Q beta 4 ?
Click to expand...
Click to collapse
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.

Bankuu said:
Wondering the same thing. I know the OTA is rolling out again today IIRC. But I also read something about root not being available on Q yet, so not sure how that would work out.
Click to expand...
Click to collapse
Google has changed the file structure in the Q beta 4 release and root is not possible at this time. This is true across all devices (not just the Pixel 3a). I know John Wu (the Magisk developer) is working on a solution and I would expect to see results before Android 10 is released, but only time will tell.
However, at this time there is no root on the Q beta 4. If you need root, you will have to stick to Pie for now.

@sic0048 I've updated my thread

I'm getting weird behavior here that I've been able to replicate.
Bottom line, if you use the Magisk patch method, upon flashing that boot image, your phone will auto-play music every single time it boots up. That's incredibly annoying.
Uninstall and go back to stock boot.img, and it goes away. Flash again, it's right back.

Guess I'll just wait for TWRP instead of going through those steps again, lol.