[TUT] ROOT HD10 (2017), HD8(2016-2017) - EASY SuperSu

[Mr_Tadakichi]

Will this work for the 2015 fire hd8?

Update - 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!!!):

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

Update v0.9, 12/29/18 As empasized by shonkin in this post, the method still works for FireOS 5.6.3.4. Enjoy!!! I would never have expected the hole to last his long ...
Update v0.8, 01/26/18 - as first reported by @najoor in this post, FireOS 5.6.0.1 is rootable! Today I verified this myself after a somewhat unsuccessful FlashFire update.
Update v0.7, 01/14/18 - @freaky2xd made a video with these rooting instructions, please follow it if you prefer a visual guide (here or here)
Update v0.6, 01/09/18 - there were reports that dr.fone app seems to be able to root the device as well. I took dr.fone for a spin, and based on its bloatedness and a few other annoying features, my personal recommendation is that you stick with the devil we know - Kingoroot (link)
Update v0.5, 01/04/18 - add a DOS bat file to remove any possible updates to Amazon packages
Update v0.4, 01/02/18 - title update
Update v0.3, 12/31/17 - light clean up; I got into a bootloop, and had to sideload a stock ROM & re-root - a.k.a. "eat my own dogfood" - Everything works fine.
Update v0.2, 12/30/17 - some redundant commands are removed.
Update v0.1, 12/30/17 - the rooting procedure is essentially taken from @retyre (here and here). Except, the instructions below include a lot of details, and handle mostly everything from the PC/ADB side. Try, and report back. GOOD LUCK!



Here is the guide to the painless root (while out of the box FireOS allows it; right now all FireOS versions up to and including 5.6.0.1 - the current OTA - are rootable). The key enabler is the original post by @ztrund (link), great work blazing the trail (and motivating me to get another Fire tablet ASAP, LOL).

Given that the devices will be shipping with the (older) rootable FireOS for the next few months (but beware of the upcoming updates - see below !!!), there is a good window of opportunity to acquire a rootable Fire HD 10, and root it. As of Dec 27th 2017, there are no reports yet of non-rootable OTAs, but those OTAs will be coming soon, count on it!

The utmost goal here is to preserve the earliest FireOS version that you get, and not let it get updated by Amazon on a whim.
I am starting with a recently bought Fire HD 10 2017 (light refurb from eBay, missed the Black Friday mega sale ). I have FireOS 5.5.0.0 (earlier than 5.6.0.0!), version name 5.3.5.1 (591450020)




Part I (avoiding Amazon updating procedure upon the initial Fire setup) - this can (almost safely) be skipped today (end of Dec, 2017), since there are no reports of unrootable OTAs yet

Low tech way (thanks to @Blaiser47 and @retyre for suggestions!):

1. Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
2. Choose any option on that WiFi screen, press cancel, and then skip
3. Once Alexa shows up, swipe down from the top, turn on Airplane mode just to be sure

High tech way:

1. Set up a dedicated slow router, limit upload/download speed to ~25 kbps (this is the trickiest part, I have a dedicated Tomato router which I use to control traffic)
2. Unpack Fire HD 10, turn it on, it will immediately demand a WiFi access
3. Connect Fire to your slow router
4. Once Fire finds Internet, it'll immediately have "Checking for updates" on the screen, this is where the slow router should kick in, and do the trick of forcing the update to give up
5. Wait a bit for updates, hopefully, it won't find them, if found something, do factory reset, and repeat (on my 1st try it did find the update, although, could not download it quickly enough, I did a factory reset via Pwr&Vol+ recovery mode, and tried again - the 2nd time it skipped the update due to the slowness of the connection)
6. Sign in to Amazon account when prompted
7. Once Alexa shows up, swipe down from the top, turn on Airplane mode - no more risk of updates!!!

Part II (rooting via Kingoroot, disabling OTA, and getting SuperSu replacement, as per @retyre recommendations)

1. Take your Fire HD as is, do not do anything dramatic such as "factory reset", Amazon ROM sideloading, etc
2. Swipe down from the top, turn on Airplane mode - to ensure that there are no OTA updates during the procedure
3. In "Settings/Device Options", tap "Serial Number" 7 times, a menu "Developer Options" will appear
4. In "Settings/Device Options/Developer Options", turn ADB debugging to ON (under "Debugging")
5. In "Settings/Security", turn "Apps from Unknown Sources" to ON
6. Download ADB to your PC (link)
7. Setup ADB drivers on your PC, connect Fire to your PC, make sure "adb devices" command shows your Fire device, authorize ADB connection on Fire
8. Download SuperSu 2.79 (this exact version!!!) to your PC from this link, place it into your ADB PC folder. The filename of this apk will be assumed to be SuperSU-v2.79-20161205182033.apk below
9. Download the attached su64.zip to your PC (see the attachment below), unzip to your ADB PC folder
10. Open a CMD window in ADB PC folder (this will be called ADB_cmd window in the following steps), type
    

    adb devices
    adb uninstall eu.chainfire.supersu

    This is a clean up of possible old SuperSu (just in case), ignore any errors you may get (if SuperSu is absent ...)
11. Download Kingoroot to your PC (link), install, let it update
12. Connect Fire to your PC; launch Kingoroot on PC; before pushing the big "ROOT" button in Kingoroot, uncheck a small box in the lower left corner for "Install recommended app" ; push "ROOT" button; wait for Kingoroot to root
13. Once Kingoroot succeeds, open a 2nd CMD window in ADB PC folder to your Fire (this will be called ADB_root window in the following steps), get a root shell, and disable OTA updates
    

    adb shell
    su
    mount -w -o remount /system
    mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
    ls -l /system/priv-app/DeviceSoftwareOTA/

    ignore any errors you may get while doing this; after 'su', you should see root (#) prompt here
14. Switch to the first ADB_cmd window, type
    

    adb uninstall com.lionmobi.powerclean
    adb uninstall com.kingoapp.link
    adb uninstall kingoroot.supersu
    adb install SuperSU-v2.79-20161205182033.apk
    adb shell "am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity"

15. Skip this step - it is not needed
    Switch to the second ADB_root window (with # prompt), type
    

    cd /data/local/tmp
    mount -w -o remount /system
    cp ./su64 /system/xbin/daemonsu
    chmod 0755 /system/xbin/daemonsu
    daemonsu -d &
    cp ./su64 /system/xbin/su
    chmod 0755 /system/xbin/su
    am start -n eu.chainfire.supersu/eu.chainfire.supersu.MainActivity

16. On your Fire, SuperSu should pop up. Update SuperSu binary as "Normal", it should report "Installation failed." Proceed to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
17. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
18. Uninstall all the junk from Kingoroot on your Fire, thanks to @fstanis for detailed instructions (copied here, executed from PC):
    

    adb uninstall com.nemo.vidmate
    adb shell rm -rf /sdcard/VidMate
    adb shell rm -rf /sdcard/.a
    adb shell rm -rf /sdcard/.DataStorage
    adb shell rm -rf /sdcard/.UTSystemConfig

Some troubleshooting options:

• If you believe you have the correct FireOS, but Kingoroot (or SuperSu) still fail, download the attached no_amzn_updates.zip to your PC, unzip to your ADB PC folder, open a CMD window in ADB PC folder, and type
  

  .\no_amzn_updates.bat

  The script will attempt to uninstall any apk updates to the official Amazon packages. Then repeat the rooting procedure from Step 1 skipping as necessary. See this post for more additional info on what the script does.
• If you mess up your /system too much and get into a bootloop with "Fire" logo - use this post for links to the official Amazon ROM files; these bin's can be sideloaded via "adb sideload" in recovery

Want to say thanks by clicking the "Thanks" button ?

Will this work with the 2015 fire hd8 model?

 

[GuyInDogSuit]

Will this work with the 2015 fire hd8 model?

Don't quote whole OPs like that.

Read the title. There's no mention of the 2015 model, is there?

 

[Mr_Tadakichi]

Don't quote whole OPs like that.

Read the title. There's no mention of the 2015 model, is there?

Oops, I'm new to this. Thanks for letting me know.

 

[GuyInDogSuit]

Oops, I'm new to this. Thanks for letting me know.

There's some stuff on that model here: https://forum.xda-developers.com/am...eos-tutorials-how-to-root-flash-roms-t3254268

It looks like the root process link has been removed, but mostly everything else is intact. You might be able to flash a custom AOSP/CM ROM on it.

 

[DelphinusMinor]

Can anyone confirm if this works on the latest Fire OS, which is 5.6.4.0? Released at the end of March.

 

[DragonFire1024]

Can anyone confirm if this works on the latest Fire OS, which is 5.6.4.0? Released at the end of March.

I think so. I do recall someone saying it's still rootable.

 

[GuyInDogSuit]

Can anyone confirm if this works on the latest Fire OS, which is 5.6.4.0? Released at the end of March.

I don't think this method will. You might need to unlock the bootloader and flash TWRP in order to flash Magisk.

 

[DragonFire1024]

I don't think this method will. You might need to unlock the bootloader and flash TWRP in order to flash Magisk.

He could always try the offline root method. And if not he can always push the required superuser binary is to the system using mtk SU. Root that way and then flash magisk after.

Sent from my Amazon KFSUWI using XDA Labs

 

[DelphinusMinor]

I think I'll just wait a bit longer. I have Nova Launcher and my widgets so I am pretty happy for now.

 

[GinkoGrazioso]

dos this still work for fire 10 7th gen: 5.6.4.0?

also i didnt read this until agter i did the setup. so it says 21 updates are ready but im keeping it open with dev mode so it doesnt start them, and im on airplane mode. can i still do this?

 

[DragonFire1024]

also i didnt read this until agter i did the setup. so it says 21 updates are ready but im keeping it open with dev mode so it doesnt start them, and im on airplane mode. can i still do this?

Do a factory reset and wipe cache. If still concerned, can always reflash your fireOS version.

Sent from my Amazon KFSUWI using XDA Labs

 

[benk81]

this process worked awesomely for me. super easy to follow and accomplish. possibly the easiest time i've had rooting any Android device i've owned. great job and thanks.

 

[remainchaos]

He could always try the offline root method. And if not he can always push the required superuser binary is to the system using mtk SU. Root that way and then flash magisk after.

Sent from my Amazon KFSUWI using XDA Labs

Dr fone worked first time, took about 20min. It Installed supersu. On 5.6.4.0

 

[iammrhappy123]

Hey guys

I have a 2016 HD8 6th gen.


It just automatically updated to 5.6.0.1

I keep getting a failed root at "checking ROOT status"

Is this version able to be rooted?

Thanks

 

[Help_Me_Obi_Wan]

First I would like to thank this tremendous effort, you are awesome!

I have Fire HD 8 6th Gen with the latest version. Which was written wrong on the system and that made me happy as I wanted a downgrade for rooting but it was a false hope..

Anyways; Is there a way to root latest version? I tried the method written even after reseting to factory settings as I had nova launcher and some other stuff installed on the system but with multiple tries, it failed at around %80.

Could you please clarify if the root covers us or not? If so what I am doing wrong?

Thank you

 

[byfgjk]

Does this work with bone stock fire hd suez with 5.3.7 or not, some people are claiming it does, but the instructions here say I need an unlocked bootloader, I don't know what that is.

 

[newnewcomputer]

Does this work with bone stock fire hd suez with 5.3.7 or not, some people are claiming it does, but the instructions here say I need an unlocked bootloader, I don't know what that is.

according to several reports from the bootloader thread, like these:

https://forum.xda-developers.com/hd...ck-fire-hd-10-2017-suez-t3913639/post81840723

and

https://forum.xda-developers.com/hd...ck-fire-hd-10-2017-suez-t3913639/post81838273

this kingoroot method can still give root access to 5.7.3 on HD10 2017. once rooted, u can follow the procedure in that thread to unlock the bootloader. that will give u even more access e.g. installing a custom ROM on ur tablet.

 

[gdroid666]

" 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"
what am i supposed to do here ? there is nothing there in those links , i went to the v2.1 and v1.0 link and there is nothing there,i am not seeing anything but a post but there is no link or file and no script no instructions . after i get selinux permissive UID 0 then what do i do to get permanent root , the post talks about automatic but there is no links there is nothing there

also when i go to shell prompt and try to block updates i get an error


C:\adbLink>adb shell
e-user --user 0 com.amazon.device.software.ota.override <
Error: java.lang.IllegalArgumentException: Unknown package: com.amazon.device.software.ota.override
1|[email protected]:/ $

and

C:\adbLink>adb shell pm disable-user --user 0 com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=5726, uid=2000, package uid=32016

C:\adbLink>

it worked on the 2019 HD 10 no problems

is there a different name for the update packages on the 2017 suez ?
also i went a head pushed the arm not arm 64 version of mtk-su
maybe that could be the problem?

 

[Rortiz2]

" 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"
what am i supposed to do here ? there is nothing there in those links , i went to the v2.1 and v1.0 link and there is nothing there,i am not seeing anything but a post but there is no link or file and no script no instructions . after i get selinux permissive UID 0 then what do i do to get permanent root , the post talks about automatic but there is no links there is nothing there

also when i go to shell prompt and try to block updates i get an error


C:\adbLink>adb shell
e-user --user 0 com.amazon.device.software.ota.override <
Error: java.lang.IllegalArgumentException: Unknown package: com.amazon.device.software.ota.override
1|[email protected]:/ $

and

C:\adbLink>adb shell pm disable-user --user 0 com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=5726, uid=2000, package uid=32016

C:\adbLink>

it worked on the 2019 HD 10 no problems

is there a different name for the update packages on the 2017 suez ?
also i went a head pushed the arm not arm 64 version of mtk-su
maybe that could be the problem?

Hi,

Yes, I removed those links as those are old versions of the tool
If you want to take a look at the latest one see: https://github.com/R0rt1z2/AutomatedRoot
Regards!

 

[gdroid666]

Hi,

Yes, I removed those links as those are old versions of the tool
If you want to take a look at the latest one see: https://github.com/R0rt1z2/AutomatedRoot
Regards!

ok i downloaded the tool but now what do i do with it?

i already rad the mtk-su and have selinux permissive
m tablet is connected to the PC here is what i have so far

i clicked the .bat from the .zip and nothing happened

do i need to run the ./mtk-su over again first?

pretty sure i already have a py installed , how do i check from a cmd prompt though?