The first time i used the latest version of SuperSU instead of the one linked in the tutorial. This time it seems to work.
Thank you and the OP so much!
[TUT] ROOT HD10 (2017), HD8(2016-2017) - EASY SuperSu
- Thread starter bibikalka
- Start date
The first time i used the latest version of SuperSU instead of the one linked in the tutorial. This time it seems to work.
Thank you and the OP so much!
DragonFire1024
Senior Member
Ah yes. You have to use the SuperSU in the OP. But you can update to the latest SuperSU once you're rooted.
Sent from my Samsung Galaxy S4 using XDA Labs
Trying to root my Fire HD Gen5 with 5.6.0.1 and based upon the instructions on p1 it fails on step #12.
Can anyone point me in the right direction?
Thanks,
Can anyone point me in the right direction?
Thanks,
Look in the direction of the title of the thread and realize this method is for the 7th generation HD 10.
I can't update my kindle fire HD 10 after rooting it. I can't check if the device cannot update before or after rooting because the first step I did was trying to root it (rofl), is there anyway for me to update the device to the latest version?
The message is "Check for update failed" btw
The message is "Check for update failed" btw
Last edited:
DragonFire1024
Senior Member
Because you disabled DeviceSoftwareOTA. You do not want your fire to update. You could loose root if you update. It's best to wait and see if the latest version can be rooted. For now you should be on and stay on 5.6.0.1 or lower.
Oh how silly of me not thinking about this
, sittting on 5.6.0.1 with root now, ty so much
DragonFire1024
Senior Member
Oh how silly of me not thinking about this
Heh no problem. Check all forum topics for goodies. There are a few I found myself
Not really sure what that is supposed to mean. a simple yes, no will do. in the OP it says it works for 7th gen but I'm not sure if it works for fire 7 7th gen.
DragonFire1024
Senior Member
At the moment, only the HD 10, 7th generation can be rooted on the current FireOS of 5.6.1.0
Sent from my Moto E4 using XDA Labs
No offence... But just read the Title Of The Thread? As has just been also explained to you?..
I read the title but was asking for clarification. I already searched the thread. A simple answer will do instead of an emoji to further crowd a thread.
After lots of thinking and reading, I realized yes.
However I have a question, I have already set-up my Kindle Fire days ago, what should I do?
---------- Post added at 07:54 AM ---------- Previous post was at 07:45 AM ----------
You know what, that was just about the worst wording I'm so sorry... Better explained here ⬇
Me being completely clueless of this root method, I set up and done the 1st power on with my new 7th Gen Amazon Fire HD 10 a few days ago, it updated and everything (It still is on 5.6.0.1 don't worry
), I now wanna do this root method, I just wanna know if I am going need to do a special step such as Volume Up + Power reboot and resetting and formatting that way.I hope this was a little more easier to understand
I'd set up lots including installing all of the Google services and it rooted fine using this method (from 5.6.0.1).
If you run into problems then look at restarting from a factory reset.
If you run into problems then look at restarting from a factory reset.
Even though I thought I had updates disabled, my Fire updated to 5.6.1.0 last week. For kicks, I tried this process again to root. Worked like a charm. Now to figure out what really has to be moved/renamed to block the next round of Amazon updates. I really lack the expertise to figure it out, but I'll poke around anyway and hope to figure it out.
Just wanted to share in case anyone wonders if KingoRoot still works with 5.6.1.0 - it did for me.
Just wanted to share in case anyone wonders if KingoRoot still works with 5.6.1.0 - it did for me.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
125Update - March 23rd, 2019.
There is now an excellent offline rooting method for HD10 (2017), HD8(2016-2018), all current FireOS versions, thanks to the fantastic effort by @diplomatic - link. This new root is obtained within a few seconds, so it is very fast. To install permanent root after mtk-su for HD10 (2017), HD8 (2016-2017), use the scripts by @Rortiz2 in here: v2.1, or v1.0 (see this link for a Linux script). For HD8 (2018), there is a dedicated full bootloader unlocking and permanent root guide - link. For HD10 (2017) there is also a full bootloader unlocking procedure available - link. The historical Kingoroot rooting procedure for HD10 (2017) is below. As a friendly reminder, once you have a root shell (obtained by any means), ensure that you disable OTA updates as to avoid getting an unrootable update (except for HD8 (2018) - do not run the commands below before you unlock the bootloader!!!):
Code:mount -w -o remount /system mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_ ls -l /system/priv-app/DeviceSoftwareOTA/
The original Kingoroot method for HD10 (2017), all current FireOS versions - EASY SuperSu
Want to say thanks by clicking the "Thanks" button ?
18Fire HD 10 ROM links & misc :
Update: Uploaded modified Supersu 2.82 SR5 ready to be flashed in FlashFire. It really represents the Chainfire's swan song, the last of the true SuperSu versions, the end of the era !!!
Fire HD 10 (7th Gen 2017) ROM links from Amazon (use for sideloading your preferred version in case you mess up). If possible, turn off WiFi before sideloading a bin file - you don't want to catch an OTA while it's loading!
FireOS 5.6.3.0 (reports say that it's still rootable, the downgrade behavior is not clear)
update-kindle-suez-40.6.2.6_user_626533320.bin
update-kindle-40.6.2.6_user_626533320.bin
FireOS 5.6.2.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.1.2_user_612495820.bin
FireOS 5.6.1.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.0.5_user_605485120.bin
System image (restore via FlashFire) link. Unzip files to /sdcard/FlashFire/Backups/5.6.1.0, rename the 2 img to bin extensions. Create md5 sum files (in a shell, type "md5 system.bin > system.md5", same for boot.bin) The system image includes SuperSu, Xposed, Busybox; OTA apk is NOT renamed.
FireOS 5.6.0.1
update-kindle-40.5.9.5_user_595550320.bin
System image (restore via FlashFire v0.24) - link. Unzip files to /sdcard/FlashFire/Backups/5.6.0.1. The system image includes SuperSu, Xposed, Busybox; OTA apk is renamed.
FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457320.bin
FireOS 5.6.0.0
update-kindle-40.5.9.5_user_595457020.bin
FireOS 5.5.0.0
update-kindle-40.5.9.1_user_591450020.bin
In addition, please find attach a SuperSu zip that works with Flash Fire v0.24 (tested with FireOS 5.5.0.0 & 5.6.0.0).
The file was created by taking SuperSu v2.82 zip from this link (file name - SuperSU-v2.82-201705271822.zip).
Then in META-INF\com\google\android\update-binary I replaced one line forcing SuperSu to install armv7 binaries instead of arm64:
with this one:Code:if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=arm64; SYSTEMLIB=/system/lib64; APPPROCESS64=true; fi;
Code:if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=armv7; fi;
Everything else is identical to the official version.
Using the official SuperSu zip will cause a bootloop - it looks like Fire HD 10 is not quite arm64 yet, and needs armv7 version of su binaries to work.7Useful tips & information:
How to install Xposed & Flashfire for easy backups and ROM updates
Follow this post by @retyre (and thank him!!!): link
Note: With stock FlashFire versions, the latest Flashfire version you can use is v0.24 (see the attached v0.24 apk, it needs the date patch which requires Xposed installed). Alternatively, it is possible to replace a library in Flashfire v0.51, and make v0.51 work:
link1
link2
link3
For convenience, I've done this procedure to the free FlashFire v.51 version using free apktool, and attached the file below (the signature will not match with the original FlashFire signed by @Chainfire, so you will need to uninstall other FlashFire packages before installing this one!)
With v0.51, uncheck two options (as per link2):
1) Emulate framebuffer in Settings
2) Mount /system read/write (after you choose the update file).
If you don't do 2), Flashfire v.51 will just sit there and never do anything
How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom).
1) Edit /system/build.prop and change ro.build.version.number to have "9" as the first value instead of "5", as recommended in this link
2) Reboot
3) Enable OTA by ensuring that /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed back to apk from apk_
4) Reboot
At this point the Fire will download a lot of apk packages, and will update Amazon system components (keeping FireOS version the same).
Partition trivia:
7I have been experimenting with various ROMs in order to port one over from another device. So far, without disabling signature verification, there is one ROM that has a lot of promise, the official CyanogenMod for the Amazon JEM (8.9 HD). Assuming flashfire doesn't crap the bed, I believe I can port this ROM to the HD 10. Aside from some obvious system apps needing to be flashed into system, all apps I've experimented with from the CM ROM work. I would be able to get themes working but it requires, I believe, the system ui and framework to be flashed. So far I haven't tried or tested a full port. Then down side: I'm moving back to Florida in a week so I'm not likely to have a full port available to test until after June 25.
Sent from my Amazon KFSUWI using XDA Labs6I'm having better luck and fun modding FireOS. Here's an update of what I got working, mostly working and what I will get to work. Mind you, this is all stock android/AOSP settings that replace Amazon's. All Amazon does is comment out or replace com.android.settings.xxx with com.amazon.xxx. so far I've been able to hunt down and redirect the fragments back to Android/AOSP. Here is what I have working so far:
Stock Android/AOSP settings:
-VPN
-Proxy
-Bluetooth and USB tethering
-Location based services with full control
-Wallpaper settings (lockscreen?)
Almost working:
-NFC/Android Beam
-Original cast screen/screen mirroring
-Full AGPS support (95% complete)
-Misc settings and other possible goodies.
Sent from my Samsung Galaxy S4 using XDA Labs
