[Megathread]Root Fire HD 10 (7th Gen 2017)

Search This thread

oscarcx

Member
Oct 2, 2017
45
16
FOR FIRE HD 10 (7th GEN, 2017) ON 5.6.0.0 ONLY
Seems like this is a tradition so I will put this on here.
Update 4: 2018/1/14, Offline rooting method by retyre (If no new method comes out, this will be the final update)
Update 3: 2018/1/1, Minor text fix
Update 2: 2017/12/31, New rooting method by bibikalka.
Update 1: 2017/12/28, Added more content
Code:
###Disclaimer###
I am not responsible for the potential damage that will be done to your tablet, such as boot looping and bricking.  
Your warranty might be void by doing the following steps. 
YOU are choosing to make these modification.
Looks like these methods doesn't work for Fire HD 8 (7th GEN, 2017)
Reason to start this thread
The topic was started by ztrund in this thread and we ended up with a pretty messy thread, which makes people really hard to locate the exact tutorial post. So I think it should be a good idea to start a new thread.


Note: This thread doesn't work for HD 10 (7th Gen) anymore because root access is temporary and it can't survive after a reboot. As a result, don't follow the exact steps on that thread.

Special thanks to strund, DragonFire1024, Blaiser47, mistermojorizin, UROMEGAX, retyre, bibikalka and countless people who helped, discussed and contributed in the original thread.

By the way, please correct me if there is any problem or mistake.


Some useful posts

1. The first detailed tutorial is located in #221 in the original thread. mistermojorizin provided the method and adb shell history.

2. #233 in the original thread. UROMEGAX provided a detailed guide of the method.

3. #304 in the original thread. I provided a more coherent step by step guide.

4. #248 in the original thread. retyre provided a different way to root the tablet. (Blaiser47 wrote that it's easier for him)

5. Easier Way to Root Fire HD 10 used a different approach by bibikalka. (Looks like new method is easier to do) (For legacy method go to post #2)

6. Offline Rooting Method by retyre


After getting root access
1. Xposed & FlashFire posted by retyre

2. tweaks/apps/modules/hacks/optimizations started by razers7t8
 
Last edited:

oscarcx

Member
Oct 2, 2017
45
16
New method

Easier Way to Root Fire HD 10 by bibikalka.

Offline Rooting Method by retyre

Legacy way
You need the following things in order to proceed:
1) adb (Available Here)
2) Kingoroot PC version (Available Here)
3) Kingo.to.SuperSU.zip (can be found here in the attachment of the post)

Preparation work:
1. Turn on USB debug mode and "allow third party app to install" on fire HD 10
2. Update Kingoroot to the latest version
Note: There will be a small grey box on the update pop up page. It is up to you whether to uncheck that box or not. I don't think that will affect the following process.
3. Connect your fire HD 10 with your PC.
4. Unzip "Kingo.to.SuperSU.zip". Copy the folder to your internal storage on tablet.
Note: In root explorer the directory is /storage/emulated/0

Let's start:
1.- Install supersu (ver 2.82) on the fire and root file explorer.
2.- Use Kingoroot to root
3.- Open the adb shell and start to type "su" while Kingoroot is rooting (You can also wait until it's done, then type su to proceed)
Code:
Note: Do not type "adb shell su" because you won't be able to type any command once the # appear. The correct way is to type "adb shell" first then start typing "su"
4.- once the # appear i did # mount -w -o remount /system
5.-Uninstall the Kingo super user app normally (Do not choose to unroot in Kingo super user app)
6.- # cd /data/media/0/Kingo.to.SuperSU
7.- # cp ./su /system/xbin/daemonsu (no error was given in my situation)
8.-# chmod 0755 /system/xbin/daemonsu
9.-# daemonsu -d &
10.-# cp ./su /system/xbin/su
11.-# chmod 0755 /system/xbin/su
12.-# rm /system/xbin/supolicy
13.-# rm /system/bin/install-recovery.sh
14.-# rm -rf /system/usr/iku
15.-# rm -rf /sdcard/Kingroot
16.-Open Supersu (and get the Su occupied error)
17.-setting > reinstall (It is not rebooted)
18.-Install Supersu (ver 2.79) and open it
19.-Supersu ask the user to update binary (I tried to update the binary but failed, nothing happened, didn't reboot)
20.-setting > set supersu as a system app (Mine rebooted immediately after doing this step)
21.-Go to google play to launch Supersu (Don't know why the Supersu icon is not shown in the Fire Launcher so this is an alternative way to open Supersu)
22.-setting > set grant as default access
23.-Then (not sure if a reboot is required here) I received a notification from Supersu and it ask me to update binary
24.-Click the notification to update binary and it should work.

Not sure whether it will work or not if SuperSU (ver 2.79) is used in the beginning of the guide.
 
Last edited:

Blaiser47

Senior Member
Sep 18, 2010
490
140
Washington, DC
Personally the method posted here seems simpler and makes more sense to me.

https://forum.xda-developers.com/hd...re-hd-10-7th-generation-t3718629/post74940137

No need to mess with two versions of supersu. After you have root you can just update supersu and binaries to the latest.

I also do not think there is any need to start adb while kingoroot is rooting. It is fine, and maybe better to prevent errors, to just wait until it is done.

I would recommend one always go back to a clean system by sideloading the official Amazon 5.6.0.0 .bin and do not fully set up or connect to the internet until you have rooted. To skip Amazon set up, just select a wifi and enter the wrong password. Then hit back and it will let you skip. May need to do it a few times.

Make sure to say in the op to copy the kingo folder with the files to your SD card storage and clarify that this is the emulated SD. Implied but for newbies just saying you need to have it and not saying where could be confusing.

After you root, if you want the latest updates, at least as of a day or so ago you can still update officially via device options, system updates. But be careful as at some point doing this may remove root if Amazon pushes more updates. To this point I strongly encourage everyone who roots to keep a copy of the current 5.6.0.0 .bin in case you need to recover. If Amazon updates their website with a new updated os, this version may be gone.

Another note, if you are using the fire launcher (default) and new apps are not showing up, just go to manage apps and find the system app called Home Pages. Force stop it and see if that fixes it. If not, go back and force stop and clear data. That should make it work.

I'll add more as I think of things and as this thread evolves.
 
Last edited:
  • Like
Reactions: bakshi

davidinfoman

Member
Oct 1, 2014
15
7
why do I have problems with the :

... cd /data/media/0/Kingo.to.SuperSU command

and the ... cd /sdcard/Kingo.to.SuperSU command

Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
 
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?

Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.

Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.

C:\ADB>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
1|[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy

UZCqGuZ.jpg
 
Last edited:

Blaiser47

Senior Member
Sep 18, 2010
490
140
Washington, DC
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?

Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.

Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
I'll try to answer as much as possible.

First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.

Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.

For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?

---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------

why do I have problems with the :

... cd /data/media/0/Kingo.to.SuperSU command

and the ... cd /sdcard/Kingo.to.SuperSU command

Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Use adb and explore your devices directories. CD to get to a directory, ls to list things in the directory. It shouldn't matter how you get it onto your fire, but it needs to be unzipped. It also doesn't matter where you put it as long as you adjust the commands accordingly. Maybe try the downloads folder?
 
  • Like
Reactions: bakshi
Thanks for your quick reply, I'll do this now!

UPDATE: Your advice worked! Thanks for clarifying that we should do this with a factory reset and should use Kingoroot on the PC.

I'll try to answer as much as possible.

First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.

Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.

For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
 
Last edited:

davidinfoman

Member
Oct 1, 2014
15
7
Part of my problem was seeing written many times ... put files on SD card, and I thought we had to have an external SD card put in the tablet. :) ( I have been running with that "false IDEA" for a couple of days until an hour ago.

No! SD card just refers to location that is on Fire Tablet itself. The ls command helped me a lot. Others should be aware of this.

I thank Blaiser47 for pointing that out. I am getting much further so far, following the advice in this thread.

Thank you oscarcx for starting this thread. Hopefully you can watch over it, and help correct our errors and giving helpful pointers.

Thanks everybody. I feel better now because the roadblock I hit, has been overcome, now for the other steps in the process.
 
  • Like
Reactions: bakshi

manaox2

Senior Member
Oct 1, 2010
387
88
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.

Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:

adb shell
su

3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:

mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su

4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.

5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.

6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.

7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click 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.)

8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
 

davidinfoman

Member
Oct 1, 2014
15
7
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.

Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:

adb shell
su

3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:

mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su

4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.

5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.

6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.

7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click 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.)

8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.

manaox2
Thank You! Thank You! Thank You!
You are the man!
Only those of us that have been frustrated with this process can appreciate your KEEP IT SIMPLE approach to this!

Not sure why the other BIG thread on this couldn't do a step by step like you just did!

You listed the steps that were screwing around with me the last couple of days.

Finally it is ROOTED! Yeah!
 

dusty23007

Member
Dec 28, 2017
6
0
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
 
Last edited:

oscarcx

Member
Oct 2, 2017
45
16
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
1. You can get it from Google Play or get it from any liable third party app store.
2. If you get it from any liable third party app store, place it directly in the internal storage so you can install it in es file manager.
3. I remember seeing a post about how to save the bricked device in this forum. You can try to follow that post if your tablet got bricked.
 
Last edited:

vbound06

New member
Dec 29, 2017
1
0
YEAH!!!

rooted baby!!!! now can i get rid of the home tabs?

never mind... i disabled fire launcher :)
 
Last edited:

mistermojorizin

Senior Member
Dec 21, 2011
853
188
Google Pixel 5
my .02, i like these instruction by @retyre. Easy peasy when I had to re-root. mostly just posting here for my own reference, hope it's ok.

I have done this with success multiple times over the last day, so try this and report:
1. Start with a pristine /system (adb sideload update .bin if you can).
2. Root using KingoRoot as usual; confirm su usage in adb shell.
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps (incl. SuperUser) from the Apps page on your Fire's Settings.
5. Confirm su and daemonsu are in /system/xbin/:
Code:
cd /system/xbin
ls -al
If not, copy them to /system/xbin/ as in step 3.
6. Copy SuperSU 2.79 .apk (other versions might work, but this is the one I have tried) to your tablet and install.
7. Open SuperSU and update binary as Normal. It should complete in a minute or two, but report "Installation failed." No worries. Click 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.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
 
Last edited:
  • Like
Reactions: bakshi

NoSkypeOnCM

Account currently disabled
Mar 6, 2015
51
1
3. #304 in the original thread. I provided a more coherent step by step guide.[/SIZE]

When I use KingoRoot it gets stuck at 90%, nevertheless su binary exists and is working.
The folder /data/media/0/Kingo.to.SuperSU however does not exists.
So I skip steps 7-11.
The folders /system/usr/iku and /sdcard/Kingroot do not exists, so I skip 14 & 15 as well
SuperSU does not show "ocupied", but the update binary pop-up (as in step 19) which seems to be successfull (non-recovery install).
I move SuperSU to /system (SuperSU config) and reboot manually.

afterwards the boot is stuck at the "fire" Logo, a soft brick. I tried this two times using adb sideload to reset the system.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    FOR FIRE HD 10 (7th GEN, 2017) ON 5.6.0.0 ONLY
    Seems like this is a tradition so I will put this on here.
    Update 4: 2018/1/14, Offline rooting method by retyre (If no new method comes out, this will be the final update)
    Update 3: 2018/1/1, Minor text fix
    Update 2: 2017/12/31, New rooting method by bibikalka.
    Update 1: 2017/12/28, Added more content
    Code:
    ###Disclaimer###
    I am not responsible for the potential damage that will be done to your tablet, such as boot looping and bricking.  
    Your warranty might be void by doing the following steps. 
    YOU are choosing to make these modification.
    Looks like these methods doesn't work for Fire HD 8 (7th GEN, 2017)
    Reason to start this thread
    The topic was started by ztrund in this thread and we ended up with a pretty messy thread, which makes people really hard to locate the exact tutorial post. So I think it should be a good idea to start a new thread.


    Note: This thread doesn't work for HD 10 (7th Gen) anymore because root access is temporary and it can't survive after a reboot. As a result, don't follow the exact steps on that thread.

    Special thanks to strund, DragonFire1024, Blaiser47, mistermojorizin, UROMEGAX, retyre, bibikalka and countless people who helped, discussed and contributed in the original thread.

    By the way, please correct me if there is any problem or mistake.


    Some useful posts

    1. The first detailed tutorial is located in #221 in the original thread. mistermojorizin provided the method and adb shell history.

    2. #233 in the original thread. UROMEGAX provided a detailed guide of the method.

    3. #304 in the original thread. I provided a more coherent step by step guide.

    4. #248 in the original thread. retyre provided a different way to root the tablet. (Blaiser47 wrote that it's easier for him)

    5. Easier Way to Root Fire HD 10 used a different approach by bibikalka. (Looks like new method is easier to do) (For legacy method go to post #2)

    6. Offline Rooting Method by retyre


    After getting root access
    1. Xposed & FlashFire posted by retyre

    2. tweaks/apps/modules/hacks/optimizations started by razers7t8
    2
    New method

    Easier Way to Root Fire HD 10 by bibikalka.

    Offline Rooting Method by retyre

    Legacy way
    You need the following things in order to proceed:
    1) adb (Available Here)
    2) Kingoroot PC version (Available Here)
    3) Kingo.to.SuperSU.zip (can be found here in the attachment of the post)

    Preparation work:
    1. Turn on USB debug mode and "allow third party app to install" on fire HD 10
    2. Update Kingoroot to the latest version
    Note: There will be a small grey box on the update pop up page. It is up to you whether to uncheck that box or not. I don't think that will affect the following process.
    3. Connect your fire HD 10 with your PC.
    4. Unzip "Kingo.to.SuperSU.zip". Copy the folder to your internal storage on tablet.
    Note: In root explorer the directory is /storage/emulated/0

    Let's start:
    1.- Install supersu (ver 2.82) on the fire and root file explorer.
    2.- Use Kingoroot to root
    3.- Open the adb shell and start to type "su" while Kingoroot is rooting (You can also wait until it's done, then type su to proceed)
    Code:
    Note: Do not type "adb shell su" because you won't be able to type any command once the # appear. The correct way is to type "adb shell" first then start typing "su"
    4.- once the # appear i did # mount -w -o remount /system
    5.-Uninstall the Kingo super user app normally (Do not choose to unroot in Kingo super user app)
    6.- # cd /data/media/0/Kingo.to.SuperSU
    7.- # cp ./su /system/xbin/daemonsu (no error was given in my situation)
    8.-# chmod 0755 /system/xbin/daemonsu
    9.-# daemonsu -d &
    10.-# cp ./su /system/xbin/su
    11.-# chmod 0755 /system/xbin/su
    12.-# rm /system/xbin/supolicy
    13.-# rm /system/bin/install-recovery.sh
    14.-# rm -rf /system/usr/iku
    15.-# rm -rf /sdcard/Kingroot
    16.-Open Supersu (and get the Su occupied error)
    17.-setting > reinstall (It is not rebooted)
    18.-Install Supersu (ver 2.79) and open it
    19.-Supersu ask the user to update binary (I tried to update the binary but failed, nothing happened, didn't reboot)
    20.-setting > set supersu as a system app (Mine rebooted immediately after doing this step)
    21.-Go to google play to launch Supersu (Don't know why the Supersu icon is not shown in the Fire Launcher so this is an alternative way to open Supersu)
    22.-setting > set grant as default access
    23.-Then (not sure if a reboot is required here) I received a notification from Supersu and it ask me to update binary
    24.-Click the notification to update binary and it should work.

    Not sure whether it will work or not if SuperSU (ver 2.79) is used in the beginning of the guide.
    2
    Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.

    Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
    Code:

    adb shell
    su

    3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
    Code:

    mount -w -o remount /system
    cd /sdcard/Kingo.to.SuperSU
    cp ./su /system/xbin/daemonsu
    chmod 0755 /system/xbin/daemonsu
    daemonsu -d &
    cp ./su /system/xbin/su
    chmod 0755 /system/xbin/su

    4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.

    5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.

    6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.

    7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click 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.)

    8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
    1
    Personally the method posted here seems simpler and makes more sense to me.

    https://forum.xda-developers.com/hd...re-hd-10-7th-generation-t3718629/post74940137

    No need to mess with two versions of supersu. After you have root you can just update supersu and binaries to the latest.

    I also do not think there is any need to start adb while kingoroot is rooting. It is fine, and maybe better to prevent errors, to just wait until it is done.

    I would recommend one always go back to a clean system by sideloading the official Amazon 5.6.0.0 .bin and do not fully set up or connect to the internet until you have rooted. To skip Amazon set up, just select a wifi and enter the wrong password. Then hit back and it will let you skip. May need to do it a few times.

    Make sure to say in the op to copy the kingo folder with the files to your SD card storage and clarify that this is the emulated SD. Implied but for newbies just saying you need to have it and not saying where could be confusing.

    After you root, if you want the latest updates, at least as of a day or so ago you can still update officially via device options, system updates. But be careful as at some point doing this may remove root if Amazon pushes more updates. To this point I strongly encourage everyone who roots to keep a copy of the current 5.6.0.0 .bin in case you need to recover. If Amazon updates their website with a new updated os, this version may be gone.

    Another note, if you are using the fire launcher (default) and new apps are not showing up, just go to manage apps and find the system app called Home Pages. Force stop it and see if that fixes it. If not, go back and force stop and clear data. That should make it work.

    I'll add more as I think of things and as this thread evolves.
    1
    Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?

    Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.

    Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
    I'll try to answer as much as possible.

    First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.

    Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.

    For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?

    ---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------

    why do I have problems with the :

    ... cd /data/media/0/Kingo.to.SuperSU command

    and the ... cd /sdcard/Kingo.to.SuperSU command

    Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
    Use adb and explore your devices directories. CD to get to a directory, ls to list things in the directory. It shouldn't matter how you get it onto your fire, but it needs to be unzipped. It also doesn't matter where you put it as long as you adjust the commands accordingly. Maybe try the downloads folder?