help i got a problem on the last step when i enter ./mtk-su i got an error which is ./mtk-su not executable: 64-bit ELF file pls help me
Are you sure that your device is Fire HD 8 (2017)? Which software version?
help i got a problem on the last step when i enter ./mtk-su i got an error which is ./mtk-su not executable: 64-bit ELF file pls help me
It is very unlikely this tool will be updated once the MTK vulnerability has been patched by the vendor (after all that's what the patch does). You'll have to use one of the other methods for downgrading and rooting/unlocking your device.I am looking to do this on my HD8 7th Gen, but it is on software ending 9920. Is there an update to being able to use this on that Kindle Fire? Thanks
It is very unlikely this tool will be updated one the MTK vulnerability has been patched by the vendor (after all that's what the patch does). You'll have to use one of the other methods for downgrading and rooting/unlocking your device.
Fail; no brick risk.I don't know if the update to the firmware was aimed to patch this. If I try the instructions on the front page, is it a case if they will just likely fail, or is it a case that it will likely brick the device?
Yep, see: https://xdaforums.com/hd8-hd10/orig...oftware-root-hd-8-hd-10-t3904595/post81031035So I tried it and hopefully I followed the instructions ok, but I got "Failed critical init step 4 This platform is not supported message"
Do you mean that you unlocked the bootloader, rooted the device, and installed a custom Rom using ADB on Windows? Was that Windows 10? If so, where can I find instructions, because I want to do the same thing?@///Manuel, why do you need Ubuntu for adb? Windows editions work just fine for me.
Man, I haven't been to this forum in quite a few weeks. Came by today and saw this thread about rooting the Fire HD 8 (2017), only to discover that the stupid Amazon update 5.6.4.0 (636559920) which automatically installed Saturday night is not supported by this tool. My own fault for not visiting more often. Hopefully someone can come up with another method of gaining temporary root. Thanks to all who provide support in the thread. I'll be back in hopes of a 9920 root soon.
I'm on the same update 636559920. I should have rooted sooner. All these updates have turned my HD 10 7th generation into garbage.
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
#