• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Rapid Temporary Root for HD 8 & HD 10

Search This thread

Mr Bigglesworth

Senior Member
Jul 23, 2013
if u get from Amazon, u are out of luck. physical stores like BB or Target may have old stock, those MAY be rootable. head over to https://forum.xda-developers.com/t/...otloader-unlock-brainstorming.3979343/page-35 n check ur serial and lot numbers.

best guess is HD10 2019 built before Mar 2020 may be downgraded to n rootable from there. good luck!
It was direct from Amazon unfortunately. Toolbox is good and gets me most of the way to what I need, it's just getting Google family link on it that is missing...


Senior Member
Oct 15, 2014
Oh my, I got a fire 10 (7th gen) tablet for free and I was stupid enough to update it to the latest firmware as I though that it would also update any modem firmware. Damn it! Now I cannot apply @bibikalka 's root >.<

Any other ways to root this thing running (Crying gif goes here)


Senior Member
Oct 23, 2012
Oh my, I got a fire 10 (7th gen) tablet for free and I was stupid enough to update it to the latest firmware as I though that it would also update any modem firmware. Damn it! Now I cannot apply @bibikalka 's root >.<

Any other ways to root this thing running (Crying gif goes here)
The hd10 (2017), device =Suez

Last i knew if was still available to root using the offline rooting method (i think kingo-root also rooted it, but it's adware).

After rooted i would suggest unlocking it, also there is the always vulnerable shorting method to get root...



New member
Jul 4, 2014
I try to start mtk-su (64bit version). I get the error message "No such file or directory" in adb shell.
When I use the 32bit version I get :
armv8l machine
Failed critical init step 3

I use an Fire HD 8 10th
Fire OS


Senior Member
Oct 23, 2012
I try to start mtk-su (64bit version). I get the error message "No such file or directory" in adb shell.
When I use the 32bit version I get :
armv8l machine
Failed critical init step 3

I use an Fire HD 8 10th
Fire OS
It isn't compatible. There is no root method currently for the hd8 (2020). Also the MTK-SU was blocked by amazon about a year+ ago.
I downgraded to and did temporary root. Does temporary root extend any features to the device
Hello, sorry I'm a bit behind on the tablet scene Firetv is more my scene these days.

Yes! if you have a temporary root shell this gives you opportunity to push an su bootstrap which will result in a permanent root, this will allow you to disable and remove bloatware. Install launchers and basically improve your device :

Where it says download supersu apk from Playstore, download it from Web

Post in thread 'Rapid Temporary Root for HD 8 & HD 10' https://forum.xda-developers.com/t/rapid-temporary-root-for-hd-8-hd-10.3904595/post-78996694

Courtesy of DutchThomas

Last edited:
  • Like
Reactions: Khiem Tran

Top Liked Posts

  • There are no posts matching your filters.
  • 144
    Software root method for Mediatek MT816x, MT817x and MT67xx!
    A tool that gives you a temporary root shell with Selinux permissive to do with as you please​

    Confirmed Working
    Fire HD 8 8th gen (2018) (thanks @xyz`) -- up to Fire OS only
    Fire HD 8 7th gen (2017) -- up to Fire OS build 636558520 only
    Fire HD 8 6th gen (2016) (thanks @bibikalka) -- up to Fire OS build 626536720
    Fire HD 10 7th gen (2017) (thanks @bibikalka) -- up to Fire OS build 636558520 only
    Fire TV 2 2015 (mt8173-based) (thanks @el7145) -- up to Fire OS only
    Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS build 0002517050244 only
    Fire HD 10 9th gen (2019) -- up to Fire OS only
    Various phones and tablets up to Android 9.x (see link below for full list)
    Note that for Fire OS 5, OS version 5.3.x.x is newer than 5.6.x.x.

    Amazing Temp Root for MediaTek ARMv8: expanded thread covering all compatible MTK devices

    Anything you do that is described in this thread is at your own risk. No one else is responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.

    Proficiency with the Thanks button under XDA posts
    A Fire HD tablet based on mt8163 or mt8173 (or another MTK ARMv8 device)
    • A PC with ADB installed to interact with your device, or
    • A terminal emulator app
    Familiarity with ADB (if using PC) and basic Linux shell commands

    1. Download the current mtk-su zip file to your PC and unzip it. Inside will be 2 directories: 'arm' & 'arm64' with an 'mtk-su' binary in each. Pick one for your device. Differences between the flavors:
      arm64: 64-bit kernel and userspace
      arm: 32-bit userspace on a 64-bit or 32-bit kernel (will also work in 64-bit userspace)
      The arm64 one is suitable for most devices. The notable devices that need the arm version are the Fire HD 8 2018, Fire 7, and Fire HD 10 2019.
    2. Connect your device to ADB and push mtk-su to your /data/local/tmp folder
      adb push path/to/mtk-su /data/local/tmp/
    3. Open an adb shell
      adb shell
    4. Change to your tmp directory
      cd /data/local/tmp
    5. Add executable permissions to the binary
      chmod 755 mtk-su
    6. At this point keep your tablet screen on and don't let it go to sleep. Run the program
      If the program gets stuck for more than a few seconds, press Ctrl+C to close it.
      The -v option turns on verbose printing, which is necessary for me to debug any problems.
      It will take several seconds, but using the -v option, you should see output similar to this (with id command added):
      $ ./mtk-su -v
      param1: 0x3000, param2: 0x18040, type: 2
      Building symbol table
      kallsyms_addresses pa 0x40bdd500
      kallsyms_num_syms 70337, addr_count 70337
      kallsyms_names pa 0x40c66d00, size 862960
      kallsyms_markers pa 0x40d39800
      kallsyms_token_table pa 0x40d3a100
      kallsyms_token_index pa 0x40d3a500
      Patching credentials
      Parsing current_is_single_threaded
      ffffffc000354868+50: ADRP x0, 0xffffffc000fa2000
      ffffffc000354868+54: ADD xd, x0, 2592
      init_task VA: 0xffffffc000fa2a20
      Potential list_head tasks at offset 0x340
      comm swapper/0 at offset 0x5c0
      Found own task_struct at node 1
      cred VA: 0xffffffc0358ac0c0
      Parsing avc_denied
      ffffffc0002f13bc+24: ADRP x0, 0xffffffc001113000
      ffffffc0002f13bc+28: LDR [x0, 404]
      selinux_enforcing VA: 0xffffffc001113194
      Setting selinux_enforcing
      Switched selinux to permissive
      starting /system/bin/sh
      UID: 0  cap: 3fffffffff  selinux: permissive
      Some other options:
      mtk-su -c <command>: Runs <command> as root. Default command is /system/bin/sh.​
      mtk-su -s: Prints the kernel symbol table​
      If you see any errors other than about unsupported or incompatible platform or don't get a root shell, report it here.

      Important: in rare cases, it may be necessary to run the tool multiple times before you hit UID 0 and get selinux permissive. If you don't achieve root on a particular run, the "UID: N cap: xxxxx...." line will reflect that. If it doesn't say "UID: 0 cap: 3fffffffff selinux: permissive", type exit to close the subshell and try mtk-su again.

    If you succeed in getting temporary root, at that point you might want to install SuperSU for a more permanent root solution. Here is the official guide on which files should be present to kickstart SuperSU from temporary root. They are available in the latest SuperSU zip file. Remember that this only applies to Fire OS 5.

    FIRE OS 5 AND ANDROID 5 USERS: There's an automated SuperSU loader by @Rortiz2 that makes jumpstarting SuperSU quick and easy.

    WARNING FOR FIRE HD 8 2018 AND OTHER FIRE OS 6 DEVICES: If you have achieved root on such a device, do not remount the system partition as read/write. The remount command will probably not work. But forcing it will trigger dm-verity, which will result in a very bad day. Your tablet will become inoperable until you restore the stock system partition. You can accomplish a lot without modifying /system. But if you would like to get persistent root with Magisk by unlocking the bootloader, head on over to @bibikalka's outstanding Unlock/Magisk/TWRP Tutorial.

    Current Version
    Release 23

    Past releases & change log live at Amazing Temp Root for MediaTek ARMv8

    I got the error, "This firmware cannot be supported". What do I do?
    This means that your device's firmware is not prone to the mechanism used by mtk-su. Check the firmware version and build number of the OS on your device. If your version is higher than that next to your device on the list above, then mtk-su will no longer work on your device. There may be other ways to achieve root. Check elsewhere on the forum.

    Will this work on the Fire 7?
    No, it is very doubtful this method can be used on the MT8127 chipset. The same also goes for the Fire TV stick.

    After getting a root shell I'm still getting 'permission denied' errors. WTH?
    It may be that selinux is still being enforced. Having root with selinux enabled is somehow more restrictive than a normal shell user. First, check that mtk-su succeeded in setting selinux to permissive by running getenforce. If it says Enforcing, then exit your shell and run mtk-su again.

    Does this thing unlock the bootloader?
    No, it does nothing to unlock the bootloader. But after running mtk-su, you may be able to use @xyz`'s revolutionary LK exploit or derivative works to achieve what is effectively an unlocked bootloader on some devices. Namely, you should be able to flash the specially crafted TWRP image using dd from Android.

    How does this tool work?
    It overwrites the process's credentials & capabilities in the kernel in order to gain privileges. It also turns off selinux enforcement by overwriting the kernel's selinux_enforcing variable. As for how it accesses that memory, I don't think I should discuss that as of yet.

    Will this work on the Fire TV Stick 4K?
    Unfortunately, no. While it has a 64-bit chip, the required vulnerabilities are not present in its OS.

    Can I include mtk-su in my app or meta-tool?
    Generally speaking, you may not distribute any mtk-su zip or binaries with your software. That includes doing any automatic download of those files into your app. You can still use it with your tools. But you should ask your users to visit this thread and download the current release zip themselves. No apps have been permitted to bundle or auto-download mtk-su.

    Why don't you reply to my post?
    I read every post in this thread, and respond to practically every post that warrants a response. Sometimes I will only click a Thanks as an acknowledgement. The reasons I may not answer your question are:
    • It has already been answered in the FAQ or multiple times in the thread.
    • Your post is unrelated to this project. It may be specific to your device, which would make it off topic for this thread.
    • Your question is extremely vague and you appear to be intentionally leaving out basic information (e.g. fishing).
    • @Supersonic27543 for helping me port it to Fire OS 5 and namely the HD 8 7th gen
    • Thank you to everyone who has donated. You're the best!
    Awesome! I just rooted my HD8 2017

    Try the automated script by @Rortiz2

    Previous instructions:

    For anyone that is confused by the process of manually installing SuperSu, I did the following...

    IMPORTANT: This is for FireOS 5 devices such as HD8 2017. Do not attempt this on HD8 2018

    1. Install SuperSu from Playstore
    2. Download SuperSu and unzip somewhere
    3. adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
    4. Follow directions from OP to get a root shell. You should not get permission denied when running ls. If you see permission denied, run exit and try again. Took me a few tries
    5. mount -o remount -rw /system
    6. cp /data/local/tmp/su /system/xbin/su
    7. cp /data/local/tmp/su /system/xbin/daemonsu
    8. cp /data/local/tmp/supolicy /system/xbin/
    9. cp /data/local/tmp/libsupol.so /system/lib/
    10. cp /data/local/tmp/libsupol.so /system/lib64/
    11. chmod 0755 /system/xbin/su
    12. chcon u:eek:bject_r:system_file:s0 /system/xbin/su
    13. chmod 0755 /system/xbin/daemonsu
    14. chcon u:eek:bject_r:system_file:s0 /system/xbin/daemonsu
    15. at this point, running su should work and show a root shell
    16. daemonsu --auto-daemon
    17. Open SuperSu app and allow it to update the su binary

    My tablet hung at the boot logo when I manually installed SuperSu via the linked instructions. Installing the bare minimum and letting the SuperSu app do the rest seems less error-prone
    ok im noob but i cannot push adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
    plus chmod: /system/xbin/su: No such file or directory

    PS C:\Users\Kenny\Desktop\platform-tools> adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
    error: device '(null)' not found
    PS C:\Users\Kenny\Desktop\platform-tools> adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
    cannot stat 'arm64/su': No such file or directory
    PS C:\Users\Kenny\Desktop\platform-tools> ^C
    PS C:\Users\Kenny\Desktop\platform-tools> adb shell
    karnak:/ $ cd /data/local/tmp
    karnak:/data/local/tmp $ chmod 755 mtk-su
    karnak:/data/local/tmp $ ./mtk-su -v
    Building symbol table
    kallsyms_addresses_pa 0x40baf400
    kallsyms_num_syms 69054, addr_count 69054
    kallsyms_names_pa 0x40c36300
    Size of kallsyms_names 830042 bytes
    kallsyms_markers_pa 0x40d00e00
    kallsyms_token_table_pa 0x40d01700
    kallsyms_token_index_pa 0x40d01b00
    Patching credentials
    init_task va: ffffffc000fcea20
    Possible list_head tasks at offset 0x338
    0xffffffc0030c8338 0xffffffc02f2b53b8 0x000000000000008c
    comm offset 0x5a8 comm: swapper/0
    Found own task_struct at node 0
    real_cred: 0xffffffc0387bf980, cred: 0xffffffc0387bf980
    New UID/GID: 0/0
    Setting selinux permissive
    Found adrp at offset 4
    ADRP x0, base is 0xffffffc00112e000
    Found ldr at offset 28
    LDR [x0,444], selinux_enforce VA is 0xffffffc00112e1bc
    Switched selinux to permissive
    starting /system/bin/sh
    karnak:/data/local/tmp # chmod 0755 /system/xbin/su
    chmod: /system/xbin/su: No such file or directory
    1|karnak:/data/local/tmp # /system/xbin/su
    /system/bin/sh: /system/xbin/su: not found
    127|karnak:/data/local/tmp #
    I made a automated-root method using this exploit.
    USE V3.0: https://forum.xda-developers.com/showpost.php?p=79441935&postcount=629
    Automated Root 3

    In the end I have been able to make everything automatic and do not have to execute any command manually.
    I can assure you that this version:
    • Do not bring the supersu with ads
    • I have tested it and it worked perfectly on my Aquaris M8 (MT8163B)
    • It works with the mtk-su in the arm64 folder

    If you want to make it work on a device that uses the mtk-su from the arm folder, you just have to replace the mtk-su that is in the "files" folder.
    NOTE: If you give permission permission denied, do Cntrl + c and rerun the script.
    --->NOTE: Be sure to put grant in supersu!!<---
    So, sorry for the inconvenience caused in the previous Automated Roots. I will erase them.
    Semi automated root v2

    Hi all,
    I updated the semi automated root:
    What have I updated?
    • All the commands that had to be written one by one, now run in a single command: sh data/local/ tmp/root_fire.sh
    • Removed instructions2.txt and fire2-root.bat
    • Added a menu to choose each device

    Download: REMOVED! USE v3.0: https://forum.xda-developers.com/showpost.php?p=79441935&postcount=629