Related
Update5: 4.5.5 is out, and there is no reason NOT to update to 4.5.5. Please use the newer 4.5.5 upgrade instructions in the link below :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Another alternative is Lollipop:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
And these are the earlier (original) 4.5.x upgrade instructions which require modifying the Amazon update file:
Update4: For users with low computer proficiency (a.k.a "newbies"), DoLooper has written a post trying to make the instructions most accessible :
http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10
If you still have questions after that, post here!
Update3: I've uploaded the 4.5.4 update file to Dropbox, now everything is super simple and you can skip steps 1)-4):
https://www.dropbox.com/s/17ngnhmvnkh1cpx/twrp_ready_update-kindle-20.4.5.4_user_454006120.zip?dl=0
md5sum : ab9468126ee7d7ff0b1c38a96313ef20
Use at your own risk (it works for me!)
If the procedure works for you, don't forget to click "Thanks"
Update2: Thanks to DoLooper, this has been established as the simplest and quickest way to get full GAPPS working. The instructions are simplified further to incorporate suggestions.
Update: Looks like the procedure worked for several people, but there is a single pitfall which appears to be common. I added some additional instructions below in red.
### Original post
I am making a separate topic out of this. Tested this yesterday, going from 4.5.2 to 4.5.4
What you need to have before you proceed : unlocked bootloader (according to reports, not really needed, skip), TWRP and rooted FireOS (4.5.3 or below). Also, download jmz tool to somewhere (can skip this too), and SuperSu flashable zip.
Important: If you have anything other than 4.5.3 right now, I recommend that you flash the 4.5.3 bootloader separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip). The other bootloaders are very risky !!! 4.5.1 and 4.5.2 will not let you into TWRP by the "power" and "vol+" button push if you screw up !!!
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Download the latest 20-4.5.4 update to a PC ( https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin ), rename *bin to *zip, unpack, and replace the attached "updater-script" below in 20-4.5.4/META-INF/com/google/android/updater-script
2) Delete the following directories/files :
a) here you remove stuff you will not flash
20-4.5.4/recovery
20-4.5.4/images
b) here you will remove files to make room in /system to flash bigger GAPPS
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
(can delete more if you need space in /system and know what is useless, and a few things could just be moved to /data/app with no issues)
3)Rename (just in case, this will make OTA blocked):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
4) Zip everything into update.zip. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon (QC this carefully!). Put the zip on a USB stick with FAT (if you have an OTG cable). Alternatively, upload it to the device somewhere to the Download folder
Possible pitfall: When you create your update.zip, look into it!!! It should have {system,boot.img,etc} right at the top level, just like the original Amazon update. If you have {yourpath/system, yourpath/boot.img,etc}, you need to re-zip and make sure that "yourpath" is removed.
5) Boot into TWRP, and flash the 4.5.3 bootloader. Reboot. Skip if you already have 4.5.3
6) Boot into TWRP, and flash update.zip from 4) . Then immediately after flash supersu.zip ( https://download.chainfire.eu/396/supersu/ ). Reboot to FireOS. If you choose not to flash supersu.zip here, before you reboot TWRP, it will ask you to root the device, say yes (leaving hooks for later root)
7) Re-boot to TWRP, flash a GAPPS package, such as Pico (Uni) GAPPS for KitKat ( http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html ). Wipe dalvik/cache and reboot to FireOS (Note: The free room in /system is still kind of limited, either remove more stuff in Step 2), or go with the smaller GAPPS. If you download my update package, you'll probably have about ~140 Mb of room in /system for GAPPS). Wipe dalvik/cache, reboot.
8) In FireOS, install jmz tool, and do small tweaks. Important, installing GAPPS via this tool is obsolete !!! Don't do it!!!. Alternatively, skip this tool, and just do it manually or via the scripts, as per here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
The lockscreen ads can be reversibly blocked via this adb command :
adb shell su -c "pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.LockscreenUpdateS ervice"
(as per DoLooper's suggestion)
P.S. 4.5.4 allows the latest GAPPS to work fine, so they will update themselves over time, let them. No need anymore to keep Google Play Services at 7.0.99
kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
link to 4.5.4.
nevermind figured it out, was being dumb and right clicking send to zip on the folder instead of adding the files to a zip
bibikalka said:
4) Zip everything into update.zip, and put it on a USB stick with FAT. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon.
Click to expand...
Click to collapse
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
6) Boot into TWRP, and flash update.zip from 4) . Say yes when it offers to root the device.
Click to expand...
Click to collapse
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
DoLooper said:
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
Click to expand...
Click to collapse
Sorry, I was not clear enough. Indeed, you can put this zip into the internal memory, but not /system (it'll get formatted). Instead, place it into the "Download" folder or something.
Just got done. Everything worked great. I did have to sideload SuperSu and Busybox manually though, but everything is working fine. Thank you.
With an easy way to recover (just re-install 4.5.4), I've been playing with various Xposed modules.
So far has not seen anything very attractive, and most of the system tweaks via Xposed modules don't seem to work.
Easy update 4.5.3 to 4.5.4 -- and working Gapps!!!
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Click to expand...
Click to collapse
Good to hear that you finally did it!
The update formats /system, so nothing survives there. But you could have had supersu in /data/app before, and that survived. You probably did root when TWRP asked about it right after the update? I think SuperSu needs something installed in /system to work properly, and that's what TWRP does.
DoLooper said:
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
Click to expand...
Click to collapse
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked? That'd be really neat if GAPPS could be flashed via recovery, just like in any other Android version. Btw, the latest Play Services provide correct positioning to Google Maps, so now it finds me on the map.
bibikalka said:
The update formats /system, so nothing survives there . . . You probably did root when TWRP asked about it right after the update?
Click to expand...
Click to collapse
If it were the least bit possible that I didn't get the root prompt, I would swear I didn't get it. I think, however, I left the tablet briefly while update.zip finished flashing. Any chance TWRP only gives you a minute or two to respond to root prompt, then defaults to yes?
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
That "see in twrp" is what i saw on screen after "success" with update.zip install. If TWRP always prompts to root and doesn't default to yes when there's no response, I must have done this step and will call a neurologist tomorrow. )
bibikalka said:
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked?"
Click to expand...
Click to collapse
Exactly!
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
...... I installed this Gapps minimal edition instead. ......
Click to expand...
Click to collapse
Thank you a million times for this. I'm on 4.5.4 rooted, and was having a horrible time getting gmail to work. I finally uninstalled framework, services, and playstore from that JMZ tool thing and gave this a shot. Gmail works great now. Only having one issue so far. On Google Play Movies, the movies and shows won't stream. They only play if downloaded first.
DoLooper said:
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
DoLooper said:
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
Click to expand...
Click to collapse
I agree, perhaps TWRP can be flashed and will work without any unlock, but I am just too lazy to test this. Do we have a confirmation for this one? I would update instructions accordingly if this is true.
DoLooper said:
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
Click to expand...
Click to collapse
Another good catch! I was not thinking about this when I wrote the original post, but having GAPPS flash properly is a pretty big deal! I may re-apply update.zip, and try the GAPPS flash, to see if it is indeed so simple.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
DoLooper said:
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
Click to expand...
Click to collapse
As above, supersu.zip flash right away is a nice simplification!
Overall, great help! And the big deal is that GAPPS are easy to flash, work fully, and require no messing around with anything else. This makes flashing 4.5.4 with GAPPS into the fastest way to get fully working GAPPS on this device !!!
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
Click to expand...
Click to collapse
Good question ... At most you'll have to delete a couple of dummy directories in /data/app, one for the play store, and the 2nd one for the play services which prevented the updates. But perhaps the GAPPS zip will remove those itself ... Why don't you try, and post ?
lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Click to expand...
Click to collapse
It depends on what changes you made. Before I flashed update.zip, I did what @bibikalka suggests and found and deleted the following dirs in \data\app :
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
After update and before installing Gapps I searched /system for anything "google." Only found "widevine" and left it.
If you installed Gapps per the original root post, you gave this command:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
I don't know what this does. Shell command effects seem to be preserved with update, though, so would be worth finding out.
---------- Post added at 12:44 PM ---------- Previous post was at 12:23 PM ----------
bibikalka said:
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
Click to expand...
Click to collapse
Exact steps I did:
Flash update.zip, press TWRP "Home," flash Supersu zip, reboot to system.
Go back to TWRP and flash Gapps zip, wipe cache (per instructions at minimal Gapps page), reboot to system.
FWIW, when rebooted after wipe, I got "updating" message again and it took awhile but all was fine.
4.5.4 Update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin (Fire HD 6 and 7 use identical files)
superSU zip: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Gapps minimal: http://forum.xda-developers.com/showthread.php?t=2779598
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
ugcbrian said:
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
Click to expand...
Click to collapse
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
DoLooper said:
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
Click to expand...
Click to collapse
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
lynnux said:
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
Click to expand...
Click to collapse
Okay, if you have to rename the bin file in order to extract the contents, do that. (Maybe double-click will work.) You will see the files and dirs that bibikalka's instructions refer to (excluding the "20-4.5.4," which is just for reference). After doing changes per instructions, make a compressed file named "update" containing what's left (see below). Since the extension will be tar or gz, rename it to "zip" and copy or move it to the Fire's download folder, then do step 6 (assuming you're on 4.5.3).
Your compressed file should contain:
[dir] META-INF
[dir] system
[dir] tools
boot.img
file_contexts
ota.prop
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.
Update : Oct 24, 2015 It looks like the bricking scare is over, and there is an updated guide on how to upgrade to the latest Lollipop without bricking :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
PUBLIC SERVICE ANNOUNCEMENT :
There are now several reports of super hard bricks (not even Amazon logo shows up) when people attempted to load 5.2.2 version via TWRP.
My best guess is that it has something to do with the 5.x update from Amazon that people request before downgrading to 4.5.3. If Amazon is providing a newer 5.x. update, it can be blocking the older 5.2.2 from working after the downgrade-upgrade procedure. When it bricked before, it would at least show "Amazon" logo, but now even the logo is gone.
One would have to capture this current 5.x update, and see what's in it. It's probably updating another partition out of those that were previously untouched :
http://forum.xda-developers.com/fire...idden-t3122246
All the downgrade-upgrade guides are on hold for now ... You are still safe to exist in the 4.5.x space (with root).
bibikalka said:
One would have to capture this current 5.x update, and see what's in it.
Click to expand...
Click to collapse
I assume I can capture file by reversing rename of DeviceSoftwareOTA.apk but leaving OTA updating blocked. Is that the method?
EDIT: Well, just did rename. No download yet. I've got otaverifier blocked. If nothing soon, I'll enable that and block dcp.
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
All that downloaded for me were apk update files, no .data, but device>updates shows:
10.0.42-D-20150925-NA-4 is ready to install
I ran logcat during download and a couple of manual installs (pressing Install button, but I do have updates blocked). I didn't see anything obviously related to update in the logcats, but not sure what to look for. Since I didn't get the .data, will I find anything helpful in logcat? What should I look for? thx
p.s., Or must I unblock updating to capture?
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
Yep, this is weird. I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Another poster indicated that the tablet rebooted about 3 times, and then he got new icons and Amazon launcher :
http://forum.xda-developers.com/showpost.php?p=63116048&postcount=141
bibikalka said:
I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Click to expand...
Click to collapse
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
DoLooper said:
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
Click to expand...
Click to collapse
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
bibikalka said:
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
OK, I'll try this later or tomorrow. Still wonder though, couldn't you--anyone on 4.5.5--leave OTA package blocked but rename OTAsoftware extension back to apk, allowing the update to download but not install?
)':
Hello, I am french sorry for my english
My kindle fire is bricked
how to repair !! :crying::crying:
help me please :/
bibikalka said:
. . . At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks! (Edit: NVM--I see your explanation above.)
EDIT @bibikalka, @everyone Thought the update was out for my region, but guess not: With DeviceSoftareOTA.apk named as originally and otaverifier enabled, Device>Updates just returns "no updates." Disabled otaverifier again and will wait on this.
I believe the update will download with DeviceSoftwareOTA.apk properly named--and hope it won't update with otaverifier disabled. So maybe I can get it. Anyway, I'll check for it over next few days, but maybe someone else will try this method first. (I am west-coast US and it seems always last to get updates.)
DoLooper said:
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks!
Click to expand...
Click to collapse
I think it will prepare to update by staging the required files in /cache, but then it'll try to reboot to apply those files (usually updates are applied in recovery ...). So when reboot fails (as it should with TWRP & 4.5.3 bootloaders which don't boot Lollipop), you intercept the stuff in /cache and see what it has.
Added: If this works, do wipe /cache before leaving TWRP (when you restore 5.2 bootloaders). This way it won't pick up the scripts and run them ...
See edit here. Forgot that I'm always last to get an upgrade. Hope someone who might get it sooner will use bibkalka's method so we can get this show back on the road.
After downloading the 5.0.1 update once I have been unable to get it again. My build number has not updated so its possible they pulled it. Root etc still works so it doesn't look like it applied.
Hello, just wanted to say that I can testify to the fact that after updating to 5.2.2, then downgrading and going into TWRP, flashing all the zips, and then wiping cache before rebooting..... gets you a BRICK!! I've stupidly done it.... to my replacement from Amazon! Hopefully sometime in the future someone can get me out of this one....
hello there recently my rooted fire os 5 with xposed playstore just updated to 5.0.1 by it self and i swear i did have com.amazonotaverifier blocked its weird because it updated when i left my fire hd 6 on charge
it just updated itself to fire os 5.0.1 il stay on that fire os because people are saying you get bricked if you do the whole procedure like downgrade back to 4.5.3 and root and get custom recovery and flash all the zips = brick
2nd try to get 5.0.1 update
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
------------------------
EDIT: NVM below! I'm getting # prompt because I recently set "adbd insecure" app to start at boot <doh> .
Second, I decided to start over and see if there was a different update waiting. So:
1. Went to twrp and flashed 5.2.0_stock_recovery_uboot.zip (for 5.0 stock recovery and bootloaders, i hope), wiped cache, and booted to OS.
2. Got l o o o n g startup. When OS finally loaded, "adb shell" hung CMD. I had to run TASKKILL /F /IM adb* >nul 2>&1 before adb shell was recognized. And when it was, it consistently returned # prompt: ([email protected]:/ #)
I'm definitely rooted, all google works, version still shows 5.0.0, build date July 20, but even after rebooting both tablet and computer, "adb shell" still always returns # prompt.
Can anyone tell me what's going on here? (Sorry this is tldr; hope a few of you slog through.) Thanks.
EDIT: it's late, maybe I'm nuts, but seems "adb shell" should return $ prompt, then "su" returns #.
DoLooper said:
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
.
Click to expand...
Click to collapse
These updates appear to be just individual apps, nothing to do with the system. You can google the version numbers, and it'll find that stuff.
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
bibikalka said:
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
Click to expand...
Click to collapse
Would that mean 5.0.1 would not be rootable?
Hello, I am curious, would it be possible to use "fastboot boot recovery.img" instead of actually flashing it in order to get root in the new 5.2.2 (build date sep 23)? It seems this would solve the hard brick problem with flashing twrp.
I'm on a never-rooted 2014 HD6 with gapps & OS 5.2.2. Very interested in rooting this tablet.
hi,
my Eng is not good, i don't understand the title
Stop !!! Do not upgrade to lollipop via twrp !!!
on today i'm receive Fire HD 7 from my phone provider. This is free.
i was rooted it with kingroot. It was succesfull. But i want setup it with android with vietnames because my boy are 10 age.
it run fire os 4.5.3 now.
can i upgrade to android 5.x?
thank for read
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.
I see a lot of new people showing up on the forum, therefore would like to provide heads up for the 2017 Xmas season. First of all, do not rush this!!! Take a few days/weeks to get comfortable with the Android, if you are a total newbie.
Yes, root is still easily accessible to ANY FireOS version, if you have Fire HD 6/7 2014!
Your options to root are as follows:
1) if you still have FireOS 4.x - use Kingroot directly to get root, install TWRP
2) if you have FireOS 5.x - try Kingroot first, if works - install TWRP (link). If Kingroot does not work, go to the next line
3) if you have any unrootable FireOS 5.x - sideload FireOS 4.5.3 (link), use Kingroot to get root, install TWRP (link).
4) if you have FireOS 5 and want to keep your user data intact (i.e., no factory reset which will have to happen if you go to 4.5.3 and then back to FireOS 5) - try this restore approach (link), it will write TWRP directly into memory. The only issue is that it may not work with the more recent FireOS versions.
Now, once you have TWRP working, proceed to install the latest rooted FireOS 5, as per this link.
My fire hd 6 is on 4.5.4, what's the best way to get root and Gapps? Can I sideload 4.5.3 directly on it, or do I need to get the 5.2.2 development version first?
smasher007 said:
My fire hd 6 is on 4.5.4, what's the best way to get root and Gapps? Can I sideload 4.5.3 directly on it, or do I need to get the 5.2.2 development version first?
Click to expand...
Click to collapse
Good point, any 4.x version can be rooted directly by Kingroot, no need to go to 4.5.3 !
Thank you. Is there a specific (latest) version of TWRP that you recommend?
smasher007 said:
Thank you. Is there a specific (latest) version of TWRP that you recommend?
Click to expand...
Click to collapse
I always used the 2015 version - just for historical reasons. But the 2016 one looks perfectly fine as well!
bibikalka said:
I always used the 2015 version - just for historical reasons. But the 2016 one looks perfectly fine as well!
Click to expand...
Click to collapse
I have successfully rooted with Kingroot. Could you please share the download link for TWRP 2016 version that works with 4.5.4? I cannot find it on the TWRP website.
Sorry for being a noob, the whole guide with so many strikes seems soo confusing!
smasher007 said:
I have successfully rooted with Kingroot. Could you please share the download link for TWRP 2016 version that works with 4.5.4? I cannot find it on the TWRP website.
Sorry for being a noob, the whole guide with so many strikes seems soo confusing!
Click to expand...
Click to collapse
The 2016 TWRP is here :
https://forum.xda-developers.com/fire-hd/development/recovery-twrp-3-0-2-0-t3488768
Instead, I recommend that you put 4.5.3 bootloaders & 2015 TWRP (this will boot 4.5.4 no issues), use this post:
https://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
bibikalka said:
The 2016 TWRP is here :
https://forum.xda-developers.com/fire-hd/development/recovery-twrp-3-0-2-0-t3488768
Instead, I recommend that you put 4.5.3 bootloaders & 2015 TWRP (this will boot 4.5.4 no issues), use this post:
https://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Thank you, I just flashed the files from 453_key_images using ADB and I noticed that all checksums match, however the checksum for mmcblk0p5 doesn't:
3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3
82dbebf3f472a5070da5916f1fae19bf /dev/block/mmcblk0p5
305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7
Since I dont have backups, I guess I am screwed. Would this boot in TWRP?
smasher007 said:
Thank you, I just flashed the files from 453_key_images using ADB and I noticed that all checksums match, however the checksum for mmcblk0p5 doesn't:
3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3
82dbebf3f472a5070da5916f1fae19bf /dev/block/mmcblk0p5
305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7
Since I dont have backups, I guess I am screwed. Would this boot in TWRP?
Click to expand...
Click to collapse
Did you do this :
dd if=453_uboot.img of=/dev/block/mmcblk0p5
?
Most likely, there was some junk (the prior UBOOT was larger), so that it has non-zeros where zeros are assumed.
You can try to run this again, where you first zero out the entire UBOOT partition:
Code:
First:
dd if=453_uboot.img of=/dev/block/mmcblk0p5
(this one makes sure that you have UBOOT image handy, don't want to search for it when you have zeros instead of UBOOT, LOL!)
Then:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p5
dd if=453_uboot.img of=/dev/block/mmcblk0p5
md5sum /dev/block/mmcblk0p5
In any unlikely event where you do mess up, this should be recoverable via aftv-tools, if the device never had FireOS 5.
bibikalka said:
Did you do this :
dd if=453_uboot.img of=/dev/block/mmcblk0p5
?
Most likely, there was some junk (the prior UBOOT was larger), so that it has non-zeros where zeros are assumed.
You can try to run this again, where you first zero out the entire UBOOT partition:
Code:
First:
dd if=453_uboot.img of=/dev/block/mmcblk0p5
(this one makes sure that you have UBOOT image handy, don't want to search for it when you have zeros instead of UBOOT, LOL!)
Then:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p5
dd if=453_uboot.img of=/dev/block/mmcblk0p5
md5sum /dev/block/mmcblk0p5
In any unlikely event where you do mess up, this should be recoverable via aftv-tools, if the device never had FireOS 5.
Click to expand...
Click to collapse
Thanks, zeroing out the block made it work! I used the below command before writing that block again.
dd if=/dev/zero of=/dev/block/mmcblk0p5
So now that I have TWRP finally, do I just go with the below steps?
1) Boot to TWRP
2) Wipe Data except internal
3) Flash this file via TWRP: 5.4.1_1133_stock_recovery_uboot.zip
4) Flash this file via TWRP: update-kindle-20.5.7.9_user_579279320.bin
5) Install JmzFireHDTool_v4.apk and get Gapps
The goal is to get the latest FireOS with Gapps with Root and keep TWRP. Does this seem right?
smasher007 said:
Thanks, zeroing out the block made it work! I used the below command before writing that block again.
dd if=/dev/zero of=/dev/block/mmcblk0p5
So now that I have TWRP finally, do I just go with the below steps?
1) Boot to TWRP
2) Wipe Data except internal
3) Flash this file via TWRP: 5.4.1_1133_stock_recovery_uboot.zip
4) Flash this file via TWRP: update-kindle-20.5.7.9_user_579279320.bin
5) Install JmzFireHDTool_v4.apk and get Gapps
The goal is to get the latest FireOS with Gapps with Root and keep TWRP. Does this seem right?
Click to expand...
Click to collapse
Well, it's a bit different, see this:
https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
If your Fire never had FireOS 5, use this file for everything: 5.2.0_stock_recovery_uboot.zip (earliest is best!)
bibikalka said:
Well, it's a bit different, see this:
https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
If your Fire never had FireOS 5, use this file for everything: 5.2.0_stock_recovery_uboot.zip (earliest is best!)
Click to expand...
Click to collapse
I am finally on 5.4.1 with Gapps, my nephew will be happy! Thank you! :victory:
One last question, is there a specific method to get TWRP working with 5.2.0_stock_recovery_uboot?
smasher007 said:
I am finally on 5.4.1 with Gapps, my nephew will be happy! Thank you! :victory:
One last question, is there a specific method to get TWRP working with 5.2.0_stock_recovery_uboot?
Click to expand...
Click to collapse
5.x bootloaders cannot boot TWRP (so one must keep stock recovery with 5.x). Instead, temporarily replacing bootloaders with 4.5.3 version together with TWRP gets one into TWRP. Then 5.x bootloaders need to get restored or 5.x won't boot. That why that post #2 on TWRP is kind of complicated
But, regardless, it seems that there are still tons of happy customers there !
bibikalka said:
I see a lot of new people showing up on the forum, therefore would like to provide heads up for the 2017 Xmas season. First of all, do not rush this!!! Take a few days/weeks to get comfortable with the Android, if you are a total newbie.
Yes, root is still easily accessible to ANY FireOS version, if you have Fire HD 6/7 2014!
Your options to root are as follows:
1) if you still have FireOS 4.x - use Kingroot directly to get root, install TWRP
2) if you have FireOS 5.x - try Kingroot first, if works - install TWRP (link). If Kingroot does not work, go to the next line
3) if you have any unrootable FireOS 5.x - sideload FireOS 4.5.3 (link), use Kingroot to get root, install TWRP (link).
4) if you have FireOS 5 and want to keep your user data intact (i.e., no factory reset which will have to happen if you go to 4.5.3 and then back to FireOS 5) - try this restore approach (link), it will write TWRP directly into memory. The only issue is that it may not work with the more recent FireOS versions.
Now, once you have TWRP working, proceed to install the latest rooted FireOS 5, as per this link.
Click to expand...
Click to collapse
I tried posting this reply in your original thread, bibikalka, but can't figure out if it actually worked as the supposed page where the post exists won't load. Maybe something to do with newbie posting restrictions. Speaking of, if XDA is going to restrict links posted by newbies, it'd be nice of them to include an easy obvious tool to strip them out after I already typed a long post containing multiple links.
First off, thanks so much, bibikalka, for everything you've done on this topic so far!
So I finally had enough of my Fire's crappy stock file management (somewhat mysterious and ever growing "Miscellaneous Others" category that there is no easy way to reduce) and decided to root. Thought for sure I had all of my bases covered when I started, but didn't realize until getting to the point of flashing back up to latest stock system, recovery, and bootloader that 5.4.0.1 was the last confirmed success and since I was allowing OTAs up until today, I must have been updated all the way to 5.6.0.1 before I flashed down to 4.5.3. Before I go any further, I'm hoping for some guidance on what to flash next.
What I've done so far:
1. Started with stock, relatively freshly factory reset, Fire HD 6, which as I said, should have been 5.6.0.1 (no, I didn't absolutely positively double check this before I started, but I remember an OTA system update pretty recently, so should be latest, which is 5.6.0.1 according to: amazon.com/gp/help/customer/display.html?nodeId=201596860 ).
2. Enabled ADB on Fire and computer (which FWIW, I'm doing all this from my LXLE Eclectica 16.04.2 64bit).
3. Booted to stock recovery using "adb reboot recovery" and entered "Apply update from ADB" state from the stock recovery menu.
4. Sideloaded 4.5.3 rollback using "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (file gotten from: kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin ).
5. After successful sideload, I performed a "wipe data/factory reset" and then a "reboot system" using the stock recovery menu.
6. Completed initial boot setup, skipping getting connected to WiFi.
7. Sideloaded jmzFireHDTool using "adb install JmzFireHDTool_v4.apk" (downloaded from : mega.nz/#F!qswxVQSb!E8NTrib3QYZU3ztlylbgmg ), and then disabled OTAs with it.
8. Sideloaded Kingroot using "adb install NewKingrootV5.2.2_C184_B435_en_release_2017_09_20_20170920220117_105203.apk" (also downloaded from : mega.nz/#F!qswxVQSb!E8NTrib3QYZU3ztlylbgmg , connected to local WiFi, and then let it run it's various system optimizations before requesting root, which didn't seem to even try to work let alone work.
9. Realized there was a newer Kingroot and sideloaded using "adb install -r NewKingrootV5.3.3_C193_B445_en_release_2018_01_23_20180124192653_105203.apk" (downloaded from: kingroot.net ), let it update some optimizations, and then requested root again. This time root succeeded.
10. Sideloaded Flashify using "adb install com.cgollner.flashify_1.9.2-64_minAPI14.apk" (downloaded from: mega.nz/#F!qswxVQSb!E8NTrib3QYZU3ztlylbgmg ).
11. Used Flashify to backup stock recovery and then flash TWRP 2.8.6.0-ariel (downloaded from: mega.nz/#F!qswxVQSb!E8NTrib3QYZU3ztlylbgmg and copied to Fire using "adb push -p openrecovery-twrp-2.8.6.0-ariel.img /sdcard/Download").
12. My Fire then rebooted into TWRP successfully (I didn't explicitly give a command to do so. I'm assuming Flashify defaults to rebooting into a recovery after flashing it.)
13. Started copying zip files needed for next step to Fire using "adb push" command. This is when I realized I wasn't sure what I was doing
What bootloader do I need to flash given my Fire should have taken all OTA system updates to 5.6.0.1?
Does the system version I choose affect that? I honestly hadn't 100% decided if I was going to go back to Fire OS rooted (5.6.0.1, I guess) or try CM11.
Assuming I do stay with Fire OS, can anyone confirm gapps are working with latest 5.6.0.1? If not, what are my other options?
Thanks in advance for any and all help!
thallat said:
What bootloader do I need to flash given my Fire should have taken all OTA system updates to 5.6.0.1?
Does the system version I choose affect that? I honestly hadn't 100% decided if I was going to go back to Fire OS rooted (5.6.0.1, I guess) or try CM11.
Assuming I do stay with Fire OS, can anyone confirm gapps are working with latest 5.6.0.1? If not, what are my other options?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
You should just skip flashing any bootloaders, and just flash recovery only. This way you'll have 5.6.0.1 bootloaders, which are flashed by OTA.
For GAPPS, you don't even need to worry flashing those in TWRP. Just use the SuperTool to install those as user apps, they will work just fine:
https://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
The rest (Xposed,busybox) you can also flash from within FireOS (no need for TWRP).
Hey, quick question, will this work with my Fire 7 (the boxy green one)
I also found that I can root my 6 on 5.x with Kingoroot PC. Just putting that out there so no one bricks while downgrading.
TechNash said:
Hey, quick question, will this work with my Fire 7 (the boxy green one)
I also found that I can root my 6 on 5.x with Kingoroot PC. Just putting that out there so no one bricks while downgrading.
Click to expand...
Click to collapse
Like are you Talking about the Latest Fire OS? Because I thought I could Put a Custom ROM on my Fire HD 6.
LuckyTheCoder said:
Like are you Talking about the Latest Fire OS? Because I thought I could Put a Custom ROM on my Fire HD 6.
Click to expand...
Click to collapse
No way of creating, exporting, or importing ROMS has been made.
Root os 4.1.1 and update to os 5.6.0.1
hi guys, is it possible to root hd6 os 4.1.1 with kingroot and then do the update to fire os 5.6.0.1 without losing the root?