That's just a folder. You could name it whatever you want and then extract to it with winrar, winzip or whatever program you want to use. I usually extract the file that I want to push to where my ADB files are. It makes it a whole lot easier.
adb push path/to/your/mtk/folder /data/local/tmpok stupid question , so if i create a folder call "mtk" to desktop ? how do i push the file to data/local/tmp ?
ok i use temp root to disabled firelauncher on my fire hd 8 8th gen and it works and now i am confusing to install superSU on windows 10 , could someone telling me what to do step by step ? willing to donate if someone can help me that , thanks !
Is there any way around setting the Default access to [Grant] in SuperSU? That was the only way I can get it to work.Awesome! I just rooted my HD8 2017
For anyone that is confused by the process of manually installing SuperSu, I did the following:
- Install SuperSu from Playstore
- Download SuperSu and unzip somewhere
- adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
- 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
- mount -o remount -rw /system
- cp /data/local/tmp/su /system/xbin/su
- cp /data/local/tmp/su /system/xbin/daemonsu
- cp /data/local/tmp/supolicy /system/xbin/
- cp /data/local/tmp/libsupol.so /system/lib/
- cp /data/local/tmp/libsupol.so /system/lib64/
- at this point, running su should work and show a root shell
- daemonsu --auto-daemon
- 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 like a less error-prone middle ground.
Edit:
missing steps to fix permissions before su works. Without having the tablet in hand, the commands should look like this
Code:chmod 0755 /system/xbin/su chcon u:object_r:system_file:s0 /system/xbin/su chmod 0755 /system/xbin/daemonsu chcon u:object_r:system_file:s0 /system/xbin/daemonsu
Is there any way around setting the Default access to [Grant] in SuperSU? That was the only way I can get it to work.
Is this just how it is? I'd obviously much rather be prompted to allow per app or even be able to manually add apps to the allow list.
Thanks for this! I'm not sure if I'm doing it correctly, but everything works fine until I get to #11. Do I just type su? When I do, it says permission denied.
EDIT: Just tried the new commands you edited and it worked. My FireHD 8 7th gen is now rooted.
Thanks, this is is to confirm root in HD8 2016. For all noobs as me @diplomatic @dutchthomas allow me to resume ADB commands/steps. Thanks again.
Code:>>> Install SuperSu from Playstore >>> From OP download/extract mtk-su and superSu (arm64 folder) in your ADB folder (easy to reach) adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp adb push mtk-su /data/local/tmp/ adb shell cd /data/local/tmp chmod 755 mtk-su >>> keep your tablet screen on and don't let it go to sleep ./mtk-su -v chmod 0755 /system/xbin/su chcon u:object_r:system_file:s0 /system/xbin/su chmod 0755 /system/xbin/daemonsu chcon u:object_r:system_file:s0 /system/xbin/daemonsu mount -o remount -rw /system cp /data/local/tmp/su /system/xbin/su cp /data/local/tmp/su /system/xbin/daemonsu cp /data/local/tmp/supolicy /system/xbin/ cp /data/local/tmp/libsupol.so /system/lib/ cp /data/local/tmp/libsupol.so /system/lib64/ daemonsu --auto-daemon >>> Open SuperSu app and allow it to update
I made a Semi-automated-root method using this exploit.
You can try it if you want.
Unpack the attatched zip, execute root-fire.bat and follow the directions.
thanks for your help but mine is fire hd 8 8th gen 2018 version
There's something odd about this. You're setting permissions (chmod and chcon) before copying the files. Those are file paths that don't exist yet. First do the cp group, then your chmods.Thanks, this is is to confirm root in HD8 2016. For all noobs as me @diplomatic @dutchthomas allow me to resume ADB commands/steps. Thanks again.
Code:>>> Install SuperSu from Playstore >>> From OP download/extract mtk-su and superSu (arm64 folder) in your ADB folder (easy to reach) adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp adb push mtk-su /data/local/tmp/ adb shell cd /data/local/tmp chmod 755 mtk-su >>> keep your tablet screen on and don't let it go to sleep ./mtk-su -v chmod 0755 /system/xbin/su chcon u:object_r:system_file:s0 /system/xbin/su chmod 0755 /system/xbin/daemonsu chcon u:object_r:system_file:s0 /system/xbin/daemonsu mount -o remount -rw /system cp /data/local/tmp/su /system/xbin/su cp /data/local/tmp/su /system/xbin/daemonsu cp /data/local/tmp/supolicy /system/xbin/ cp /data/local/tmp/libsupol.so /system/lib/ cp /data/local/tmp/libsupol.so /system/lib64/ daemonsu --auto-daemon >>> Open SuperSu app and allow it to update
Trying to run this on my 2015 amazon fire tv, this is what i continuously get, can it really take 2 dozen times to get the uid 0??? Dont know if it makes any difference but im adb connected to my fire tv through network
C:\adb>adb shell
shell@sloane:/ $ cd /data/local/tmp
shell@sloane:/data/local/tmp $ chmod 755 mtk-su
shell@sloane:/data/local/tmp $ ./mtk-su -v
Building symbol table
kallsyms_addresses_pa 0x40aae000
kallsyms_num_syms 63062, addr_count 63062
kallsyms_names_pa 0x40b29400
Size of kallsyms_names 776235 bytes
kallsyms_markers_pa 0x40be6d00
kallsyms_token_table_pa 0x40be7500
kallsyms_token_index_pa 0x40be7900
Patching credentials
init_task va: ffffffc000df7b40
Possible list_head tasks at offset 0x338
0xffffffc066868348 0xffffffc066868d88 0xffffffc000df7e88
comm offset 0x4d0 comm: swapper/0
Did not find own task_struct (2)
New UID/GID: 2000/2000
Setting selinux permissive
Found adrp at offset 4
ADRP x0, base is 0xffffffc00102b000
Found ldr at offset 28
LDR [x0,2316], selinux_enforce VA is 0xffffffc00102b90c
Selinux is already permissive
starting /system/bin/sh
shell@sloane:/data/local/tmp $
This script will root your fire. ONLY HD 8 2017 OR HD 8 2016
Do you want to continue?y/n:y
-------------------------------------------------------------------------------
[*] Pushing files and removing old files...
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
arm64/su: 1 file pushed. 13.0 MB/s (108480 bytes in 0.008s)
arm64/supolicy: 1 file pushed. 8.1 MB/s (42712 bytes in 0.005s)
arm64/libsupol.so: 1 file pushed. 18.6 MB/s (334744 bytes in 0.017s)
3 files pushed. 11.3 MB/s (485936 bytes in 0.041s)
mtk-su: 1 file pushed. 7.1 MB/s (22136 bytes in 0.003s)
[*] Setting permissions...
[*]Executing exploit...
wait until it finishes... When the exploit finishes, DON'T CLOSE THIS WINDOW
AND FOLOW THE INSTRUCTIONS2.txt
/system/bin/sh: ./data/local/tmp/mtk-su: No such file or directory
Press any key to continue . . .
No such file or directory
WARNING FOR FIRE HD 8 2018 AND OTHER FIRE OS 6 DEVICES: If you have achieved root on such device, do not remount the system partition as read/write. Doing so will trigger dm-verity and will make your tablet inoperable. Make sure that you have somehow disabled dm-verity before remounting or modifying /system.
OK, don't run this anymore. It's not compatible with that device yet. The line "0xffffffc066868348 0xffffffc066868d88 0xffffffc000df7e88" tells me that it's not parsing some kernel structures correctly. This will have to be addressed.
There's something odd about this. You're setting permissions (chmod and chcon) before copying the files. Those are file paths that don't exist yet. First do the cp group, then your chmods.
OK, don't run this anymore. It's not compatible with that device yet. The line "0xffffffc066868348 0xffffffc066868d88 0xffffffc000df7e88" tells me that it's not parsing some kernel structures correctly. This will have to be addressed.
Download from here: https://xdaforums.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/
adb push path/to/mtk-su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
$ ./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
#