yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] KonigTX:
oh.. saw this "Fire HD 8 7th gen (2017)" thought it would work with mine. Bummer.

Don't really keep up with the 100 different versions of fire tabs.
[Fire HD 8 and HD 10 General] k4y0z:
Already figured it out ;)

https://xdaforums.com/showpost.php?p=80239662&postcount=830

Just hasn't made it to the OP yet.
[Fire HD 8 and HD 10 General] vendo:
team

I`m getting this msg

shell@douglas:/data/local/tmp $ ./mtk-su

Failed critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

shell@douglas:/data/local/tmp $ ./mtk-su

Failed critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

shell@douglas:/data/local/tmp $ ./mtk-suUID: 2000

What can I do?
[Fire HD 8 and HD 10 General] k4y0z:
[MENTION=541852]vendo[/MENTION]: can you please check your exact firmware version in settings (including the build)

[MENTION=8132642]diplomatic[/MENTION]: looks like douglas (Fire HD8 2017) has also been patched
[Fire HD 8 and HD 10 General] Rortiz2:
Huh... Amazon patched all devices then?

This was expected but... ¿How?

I mean, if diplomatic doesn't released source code?
[Fire HD 8 and HD 10 General] k4y0z:
They don't need the source code, they can still analyze what it does...
[Fire HD 8 and HD 10 General] Rortiz2:
Huh.. End of line...

Well it has been a good root exploit while it was pathced..:(

The good thing is that you can still unlock it by hardware method.

Also is HD8 2016 patched too?

EDIT: Seems that no, in amazon page latest it 5.3.6.4 but soon... You already know what will happen.

What's your idea for unlock now? We can brick it in other way?
[Fire HD 8 and HD 10 General] diplomatic:
Yeah, it clearly has. The compatible versions have been updated on the OP. It might be possible to downgrade the FW via recovery on ones where the OS version is the same (HD8 - 2017, HD10, Fire 7 2019). Anyone want to test?
[Fire HD 8 and HD 10 General] k4y0z:
True, it should be possible. At least on suez they didn't change LK/PL or TZ.
[Fire HD 8 and HD 10 General] Rortiz2:
So, I analyzed the images in 5.6.4.0 (douglas) and extracted this:

md5sums:

[COLOR="Red"]1918f4ff50d1d3130c3017a960741063[/COLOR] lk.bin
[COLOR="red"]78243d84f06c68786eb06830707ea816[/COLOR] preloader.bin
[COLOR="red"]8ef75c1b4904630eb065cfd4c856a982[/COLOR] preloader.hdr0
[COLOR="red"]9b12892bf0c00747a1a304db4e3c321a[/COLOR] preloader.hdr1
[COLOR="red"]8c9bf9c5d3a4ce94fcf4d5457565c4c7[/COLOR] tz.img

First 12 bytes. Use them for reference:

[COLOR="red"]88 16 88 58 64 68 07 00 4C 4B 00 00[/COLOR] lk.bin
[COLOR="red"]4D 4D 4D 01 38 00 00 00 46 49 4C 45[/COLOR] preloader.bin
[COLOR="red"]45 4D 4D 43 5F 42 4F 4F 54 00 00 00[/COLOR] preloader headers
[COLOR="red"]88 16 88 58 00 B4 00 00 41 54 46 00[/COLOR] tz.img

This info may be useful for check if it's safe to downgrade.
[Fire HD 8 and HD 10 General] vendo:
the version is 5.6.4.0 (636559820) INstalled on Sep. 13

---------- Post added at 07:27 PM ---------- Previous post was at 07:08 PM ----------

How can you unlock HD 8 7th DOuglau using HW method?
[Fire HD 8 and HD 10 General] Rortiz2:
Oh.. Sorry I just looked at hd8 unlock thread, and there's no hardware method as suez.. Sorry.

Well you can downgrade preloader, lk and tz tought amonet and flash rootable boot.img and system.img
[Fire HD 8 and HD 10 General] k4y0z:
So which build of 5.6.4.0 is this?

It will likely be the same for all of them, but that's exactly what we need to know.

There is a hardware-method, all the scripts are included in amonet. I just didnt't include the instructions yet.

It requires disassembling the device as the point to short is on the back of the board.

You can follow the instructions here how to get to TP28
[Fire HD 8 and HD 10 General] Rortiz2:
Extracted from update-kindle-50.6.3.6_user_636558520.bin douglas.

version_name=Fire OS 5.6.4.0 (636558520)
[Fire HD 8 and HD 10 General] vendo:
Have you seen guys 7th gen picture of the TP28 pad? I can`t find it
[Fire HD 8 and HD 10 General] k4y0z:
https://imgur.com/9ThIUqK
[Fire HD 8 and HD 10 General] Korin67:
I just have received hd8 7th of this version. Do you plan to modify mtk-su to cover up to this version?

My hd8's version number is 636559820, sorry. A bit newer than this.

When tried I got:

shell@douglas:/data/local/tmp $ ./mtk-su

Failed critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

shell@douglas:/data/local/tmp $ ./mtk-su -v

Failed critical init step 4

setns failed: Permission denied

starting /system/bin/sh

UID: 2000 cap: 0000000000 selinux: enforcing
[Fire HD 8 and HD 10 General] Rortiz2:
1- I'm not mtk-su developer

2- It's impossible I think

Enviado desde mi WAS-LX1A mediante Tapatalk
[Fire HD 8 and HD 10 General] NFSP G35:
From the developer (one page back)
[Fire HD 8 and HD 10 General] TraderJack:
Does anyone know where I can find a copy of the 636558520 ROM?

I assume that if I install the first 5.6.4.0 (or earlier release) that an OTA would update me too far.

I'd like a one flash version of 636558520.

thanks.

EDIT: Looks like this version is still on Amazon:

https://www.amazon.com/firehd87thgensoftwareupdate

Proper filename is "update-kindle-50.6.3.6_user_636558520.bin" in case you need to google to download from other sources (and Amazon updates).
[Fire HD 8 and HD 10 General] diplomatic:
Don't do it.

I believe someone reported that flashing the previous 5.6.4.0 ROM bricked his tablet. It's not safe to roll back any Fire HD firmwares, even if it's the same Fire OS version. You will have to open your tablet to recover it if you've done it.
[Fire HD 8 and HD 10 General] TraderJack:
Sorry, I'm not clear on exactly what you are saying. I can't even flash the same ROM I'm already using (636558520)?

So even if I flash to LineageOS and want to go back to FireOS, I can't do it?

This would seem to be in direct contrast to waht [MENTION=7104332]k4y0z[/MENTION] is stating:

https://xdaforums.com/showpost.php?p=80302279&postcount=160

To be clear, I would be doing this from within TWRP.

Thanks.
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=1258954]TraderJack[/MENTION], I thought you were trying to downgrade/roll back the firmware on a locked tablet to be able to use mtk-su. If not, then why are you quoting the OP where it says which version mtk-su will work on? That quote made it seem like that's what your goal was. And what does your question have to do with mtk-su in general (i.e. this thread)?
[Fire HD 8 and HD 10 General] TraderJack:
I apologize that I was unclear regarding my intent/situation. I followed various links/searches through which landed me here where there was talk about mtk-su not working past 636558520. [MENTION=7104332]k4y0z[/MENTION] procedure on his thread has us using your mtk-su as part of the process and so therefore it seems the two are linked.

Specifically meaning that his process won't work now either if you have upgraded past 636558520 and this *appears* to be based on the dependence of getting that first temporary root with your mtk-su. This is my understanding, but perhaps I am mistaken.

In any event, I am already unlocked having used mtk-su with [MENTION=7104332]k4y0z[/MENTION] procedure on my device. Since I am unlocked already, [MENTION=7104332]k4y0z[/MENTION] seems to believe that I can change versions at will now via TWRP and even the latest FireOS should be rootable after flashing Magisk (even though they patched the mtk-su exploit).

I was/am simply chasing down all available leads to be sure of the answer.

Appreciate your time.
[Fire HD 8 and HD 10 General] dasbooter:
posted in error
[Fire HD 8 and HD 10 General] 4g1harrison:
Hello, I have a Fire HD 8 OS 5.6.4.0 build 636558520 - which is exactly what the thread says is supported.

However I get this error (which is different from others people have talked about here recently:

Failed critical init step 4

This platform is not supported

I can't find anyone even talk about this error. Any ideas?
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=10236511]4g1harrison[/MENTION], that error message is new for R19, which was just posted. It specifically means the firmware is not accessible to mtk-su for getting root. Check your build number again. There's only a 3 or 4 digit difference between the last supported one and the patched one.
[Fire HD 8 and HD 10 General] AkoSI Godsent:
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
[Fire HD 8 and HD 10 General] Supersonic27543:
Are you sure that your device is Fire HD 8 (2017)? Which software version?
[Fire HD 8 and HD 10 General] Qiz:
Is There way to the root the amazon fire 7 9th gen?
[Fire HD 8 and HD 10 General] diplomatic:
I heard this thread might have a way.
[Fire HD 8 and HD 10 General] kquade:
1. I've got a Fire HD 8 8th generation ... among many others ... that happens to be running Fire OS 6.3.1.2. It's the only one. How can I get this same result?

2. Did this on my Fire HD 8 8th generation running Fire OS 6.3.0.0. After all of the disabling, when I go to set the Accessibility services for "to detect home button press" and "Nova launcher," they both have nothing listed. All others showed Nova Launcher as a choice. Any ideas?

2b. Same tablet: Google Family Link for Children keeps "Checking for updates ..." during setup. Is a Google service missing or what?
[Fire HD 8 and HD 10 General] Mr Bigglesworth:
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
[Fire HD 8 and HD 10 General] DB126:
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.
[Fire HD 8 and HD 10 General] Mr Bigglesworth:
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?
[Fire HD 8 and HD 10 General] DB126:
Fail; no brick risk.
[Fire HD 8 and HD 10 General] Mr Bigglesworth:
Thanks. In that case I'll give it a go at some point and update then.
[Fire HD 8 and HD 10 General] Mr Bigglesworth:
So I tried it and hopefully I followed the instructions ok, but I got "Failed critical init step 4 This platform is not supported message"
[Fire HD 8 and HD 10 General] DB126:
Yep, see: https://xdaforums.com/hd8-hd10/orig...oftware-root-hd-8-hd-10-t3904595/post81031035
[Fire HD 8 and HD 10 General] ///Manuel:
wrong thread, apologies.
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=8060082]///Manuel[/MENTION], why do you need Ubuntu for adb? Windows editions work just fine for me.
[Fire HD 8 and HD 10 General] ///Manuel:
Wrong thread sorry!!! Please delete.
[Fire HD 8 and HD 10 General] RagManX:
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.
[Fire HD 8 and HD 10 General] jhford:
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?

Thanks
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=263313]jhford[/MENTION]: no... I was only talking about temp root.
[Fire HD 8 and HD 10 General] smashedpumpkins:
I'm on the same update 636559920. I should have rooted sooner. All these updates have turned my HD 10 7th generation into garbage.
[Fire HD 8 and HD 10 General] Stbennet:
I was able to get root for a 7th gen on 9920 by following this post: https://xdaforums.com/showpost.php?p=81166313&postcount=337
[Fire HD 8 and HD 10 General] diplomatic:
Fire HD 10 2019

Here is a version of mtk-su that may work with Fire OS 7.3.1.0 on your HD10 2019 (maverick). Use the arm build for this device. Magisk can be loaded by following this guide.

Thanks to [MENTION=8247486]dr_docdoc[/MENTION] for all the tests.

EDIT: File removed. Get the latest release from the OP.
[Fire HD 8 and HD 10 General] deadman96385:
I can confirm this works, just tested it on my unit and was able to dump all the partitions from the root shell generated good work!
[Fire HD 8 and HD 10 General] TheFool131:
Drats I've upgraded to 7.3.1.1... any way we can work on the upgraded version as well [MENTION=8132642]diplomatic[/MENTION]
[Fire HD 8 and HD 10 General] peachpuff:
So i think i did everything right but root checker says no root? :eek:

maverick:/data/local/tmp $ ./mtk-su -v
armv8l machine
param1: 0x1000, param2: 0x8040, type: 17
Building symbol table
kallsyms_addresses pa 0x40de7300
kallsyms_num_syms 48658, addr_count 48658
kallsyms_names pa 0x40e46500, size 618621
kallsyms_markers pa 0x40edd600
kallsyms_token_table pa 0x40eddc00
kallsyms_token_index pa 0x40ede000
Patching credentials
Parsing current_is_single_threaded
ffffff80083a8c54+44: ADRP x8, 0xffffff80096bd000
ffffff80083a8c54+48: ADD xd, x8, 1024
init_task VA: 0xffffff80096bd400
Potential list_head tasks at offset 0x480
comm swapper/0 at offset 0x758
Found own task_struct at node 1
cred VA: 0xffffffc00d5fdf00
securebits were 0x2f
Parsing avc_denied
ffffff800833735c+10: ADRP x11, 0xffffff80098e7000
ffffff800833735c+14: LDR [x11, 2168]
selinux_enforcing VA: 0xffffff80098e7878
Setting selinux_enforcing
Selinux is already permissive
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
[Fire HD 8 and HD 10 General] cybersaga:
This gives you temporary root (only for that shell session), not permanent.
[Fire HD 8 and HD 10 General] peachpuff:
I thought it was until I reboot? Not too familiar with temp root. Good to know, I'll try again later.
[Fire HD 8 and HD 10 General] cybersaga:
Not even that, no. It's just that shell session that is running as root. No other app can use the root permissions.

The original post in this thread mentions an automated Python script built by Rortiz2 that you can run from Windows or Linux: https://xdaforums.com/hd8-hd10/orig...hd-8-hd-10-t3904595/post80192896#post80192896

It uses mtk-su to install permanent root.

Take note of the prerequisites: https://github.com/R0rt1z2/AutomatedRoot
[Fire HD 8 and HD 10 General] newnewcomputer:
OP also provided a link to his guide on how to install Magisk with temp root in his post. just be VERY careful on granting root access in Magisk as the BL is still locked n partitions are protected by dm-verity.
[Fire HD 8 and HD 10 General] wings516:
Can someone help me understand what I am doing wrong here?

I copied the mtk-su file to the internal storage of my fire, downloaded termux on my fire, but I can't seem to even get to the internal storage path....

I try cd and cp but it either cays no such file or directory, or too many commands... I'm new to using linux so any advice is appreciated.

Most of the time I get chmod: changing permission of "mtk-su" : Operation not permitted
[Fire HD 8 and HD 10 General] Rortiz2:
Thanks to point my automated-tool :)

Anyway DON'T USE IT WITH MAVERICK. If you modify the /system partition you will end in a nice brick. If someone tried, no worries, the tool checks for dm-verity before doing the root process so there's no brick.

In this case, the best thing you can guys do, is DISABLE OTAS and get Bootless ROOT.

Regards.
[Fire HD 8 and HD 10 General] Ortiz.jr:
./mtk-su Problem

So I've done all the steps up to the point where you have to type in ./mtk-su

I do this, then receive this:

Failed Critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

I'm unaware as to what this means.

I saw someone get the same thing, and that there was no resolution other than the Hardware method.

Now that a few months have passed, is there a way for me to bypass this? or some fixed method?

This is a lot of work just to install Android onto my Fire Hd8

II should note this is on a Fire HD 8 (7th Generation) OS 5.6.4.0 (636559920)

(Late 2019 Update)
[Fire HD 8 and HD 10 General] LivinOne:
That doesnt work. I installed Python (and told the installed add PATH) and ran the BAT. error sayisn cant find Python3... changed that to Python, still not working.

you MUST change in the BAT file, "Python3" to ... C:\Users\<USERNAME>\AppData\Local\Programs\Python\Python37\python.exe

---------- Post added at 05:43 PM ---------- Previous post was at 05:30 PM ----------

Why isnt the SH file being copied to the folder? I opened ADB shell, folder exists MTK-SU file is there but ROOT.SH file is not?

Detecting device information....

--------------------------------------

Device: KFGIWI

Brand: Amazon

ARCH: arm64-v8a

Platform: mt8163

Android: 5.1.1

SELinux status: Permissive

Root: no

--------------------------------------

Detected arm64 arch.. Pushing arm64 mtk-su & files

failed to copy 'arm64/mtk-su' to 'arm64/root.sh': No such file or directory

--------------------------------------

Pushed files succsefully!

--------------------------------------

'grep' is not recognized as an internal or external command,

operable program or batch file.

Installing SuperSU...

7037 KB/s (6352735 bytes in 0.881s)

pkg: /data/local/tmp/SuperSU.apk

Success

--------------------------------------

Starting Root Process...

Unable to open /data/local/tmp/root.sh: No such file or directory

exec: No such file or directory

--------------------------------------

PRESS ENTER TO CONTINUE.
[Fire HD 8 and HD 10 General] Rortiz2:
How you exactly set the python path? See here: https://geek-university.com/python/add-python-to-the-windows-path/

Did you extracted all the contents of the tool? See how works here:

Detecting device information....
--------------------------------------
Device: Aquaris M8
Brand: bq
ARCH: arm64-v8a
Platform: mt8163
Android: 6.0
SELinux status: Enforcing
Root: no
--------------------------------------
Detected arm64 arch.. Pushing arm64 mtk-su & files
arm64/mtk-su: 1 file pushed. 1.0 MB/s (42832 bytes in 0.043s)
arm64/root.sh: 1 file pushed. 0.1 MB/s (1035 bytes in 0.013s)
arm64/su: 1 file pushed. 4.8 MB/s (108480 bytes in 0.021s)
arm64/supolicy: 1 file pushed. 3.3 MB/s (42712 bytes in 0.012s)
arm64/libsupol.so: 1 file pushed. 2.8 MB/s (334744 bytes in 0.115s)
5 files pushed. 2.4 MB/s (529803 bytes in 0.209s)
--------------------------------------
Pushed files succsefully!
--------------------------------------
SuperSU already installed... Skip the install
--------------------------------------
Starting Root Process...
Starting: Intent { act=android.intent.action.MAIN cmp=eu.chainfire.supersu/.MainActivity }
Now update the su binaries from SuperSU app.

(See attached photo)

I updated a few stuff, download it from here: https://github.com/R0rt1z2/AutomatedRoot/archive/master.zip and try again.

Also, looks like you have Amazon Fire HD8 6th gen aka giza. If your firmware is at the latest version mtk-su will not work...

Regards.
[Fire HD 8 and HD 10 General] LivinOne:
I downloaded your latest from this link.

Your BAT file will not work for windows... PYTHON3 does not exist. You must call 'python.exe' :: I change your BAT to call it directly and it worked... C:\Users\<USER_NAME_HERE>\AppData\Local\Programs\Python\Python37\python.exe mtk-su.py

Also, I suggest you add to your README... BOTH Python & ADB must be in PATH (you can verify by typing 'path' at any windows command prompt)

thx for the great work!
[Fire HD 8 and HD 10 General] Rortiz2:
Re-read the README, it's already advised...

Anyway, the latest version that I asked you to test doesn't calls python3, it calls python. IMO win is pretty weird, let's say it's more special than Linux in path terms.

Glad that you got it working with the direct path.

Regards.
[Fire HD 8 and HD 10 General] rlrevell:
Trying to perma-root LG Xpression Plus 2 fails (strace included)

Edit: SUCCESS! I tried it with Magisk 17.1 and Magisk Manager 5.9.1 and all is working.

So Tecknight pointed me over here, and this seems to work fine all the way up to where I attempt the su again as an unprivileged user, which dies with:

130|mmh4x:/data/local/tmp $ su

read (4 != -1) failed with 104: Connection reset by peer

I've attached an strace. Tried it with latest Magisk and 17.1 with about the same results, only difference was the older one complained about some selinux policies it didn't know about that looked unrelated.

Thanks very much for your work, great stuff.

p ast ebin.com / ZfYjFm5u

Edit: this is the issue. But I then found your more recent post about bootless root so am trying that as well. This is Android 9 btw

mmh4x:/data/local/tmp # cat /data/cache/magisk.log

--------- beginning of system

--------- beginning of main

12-27 12:07:22.340 29886 29886 I Magisk : Magisk v20.1(20100) daemon started

12-27 12:07:22.343 29886 29886 I Magisk : * Device API level: 28

12-27 12:07:22.343 29886 29886 E Magisk : fopen: /sbin/.magisk/config failed with 2: No such file or directory

12-27 12:12:16.198 30037 30037 I Magisk : Magisk v20.1(20100) daemon started

12-27 12:12:16.199 30037 30037 I Magisk : * Device API level: 28

12-27 12:12:16.199 30037 30037 E Magisk : fopen: /sbin/.magisk/config failed with 2: No such file or directory

12-27 12:13:18.044 30067 30067 I Magisk : Magisk v20.1(20100) daemon started

12-27 12:13:18.044 30067 30067 I Magisk : * Device API level: 28

12-27 12:13:18.044 30067 30067 E Magisk : fopen: /sbin/.magisk/config failed with 2: No such file or directory

12-27 12:41:57.070 30772 30772 I Magisk : Magisk v20.1(20100) daemon started

12-27 12:41:57.071 30772 30772 I Magisk : * Device API level: 28

12-27 12:41:57.071 30772 30772 E Magisk : fopen: /sbin/.magisk/config failed with 2: No such file or directory

12-27 12:42:48.514 30772 30802 E Magisk : su: cannot find manager

12-27 12:42:48.514 30772 30802 W Magisk : su: request rejected (2000)

12-27 12:43:11.451 30772 30815 E Magisk : su: cannot find manager

12-27 12:44:22.354 30772 30853 I Magisk : ** late_start service mode running

12-27 12:44:40.204 30772 30873 E Magisk : su: cannot find manager

12-27 12:46:56.249 30772 31054 E Magisk : su: cannot find manager

12-27 12:46:56.250 30772 31054 W Magisk : su: request rejected (2000)
[Fire HD 8 and HD 10 General] votemarvel:
I have a Fire HD 8 2018 which is running FireOS 6.3.1.2 The terminal gives me the response of "Failed Critical init step 4. This platform cannot be supported."

I'm guessing this isn't working because of the FireOS version I am running. Is there anyway to make it work or if not downgrade the FireOS version so it will. Sorry if this has already been covered but 90 pages is a lot of try and read.

Edit: I found the info after posting. SAdly it seems that unless I open up my tablet I'm not going to be able to get root running, which is a real shame. I don't mind messing with software but hardware is beyond me. Hopefully someone will find a way to root the latest FireOS version with just software.
[Fire HD 8 and HD 10 General] LivinOne:
I have a HD8 2017 in the same situation and the dev's created a way to Brick it (download the amonet files from the thread for your tablet), and then you can install TWRP & Root. But, I have tried for 3 hours and cant get it to work... I'm stuck where you put the tablet into Fastbook mode, at that point, my terminal (tried both Ubuntu and Windows) is not 'seeing' the tablet at all... so it just waits for the tablet to show up. I've posted my issue here... https://xdaforums.com/showpost.php?p=81322541&postcount=15
[Fire HD 8 and HD 10 General] decian1984:
im trying to root my fire hd 10 2019 im running the right fire os i get stuck after chmod 755 when i enter ./mtk-su i get file not found help?
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=10431729]decian1984[/MENTION], try the arm version and make sure you meet all the requirements.