yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] caporal:
I did it. Got this messages. Then I installed SuperSU but it says. Root Undetected.

Also, my device keeps disconnecting (last few lines)

shell@douglas:/ $ cd /data/local/tmp

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

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

armv8l machine

param1: 0x3000, param2: 0x10000, type: 1

Building symbol table

kallsyms_addresses pa 0x40af3b00

kallsyms_num_syms 67820, addr_count 67820

kallsyms_names pa 0x40b78400, size 815336

kallsyms_markers pa 0x40c3f500

kallsyms_token_table pa 0x40c3fe00

kallsyms_token_index pa 0x40c40200

Patching credentials

init_task VA: 0xffffffc000efaa20

Possible list_head tasks at offset 0x338

0xffffffc0030c8338 0xffffffc00ca125b8 0x000000000000008c

comm offset 0x5a8 comm: swapper/0

Found own task_struct at node 1

real_cred VA: 0xffffffc050403680

Parsing sel_read_enforce

ffffffc0002d8fb8+04: ADRP x0, 0xffffffc001069000

ffffffc0002d8fb8+1c: LDR [x0, 4028]

selinux_enforce VA: 0xffffffc001069fbc

Setting selinux_enforce

Switched selinux to permissive

Trying this again...

Switched selinux to permissive

Trying this again...

Switched selinux to permissive

New UID/GID: 0/0

starting /system/bin/sh

shell@douglas:/data/local/tmp #

C:\Users\jcaporal\AppData\Local\Android\Sdk\platform-tools>adb shell

shell@douglas:/ $ id

uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011

(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),

3006(net_bw_stats) context=u:r:shell:s0

shell@douglas:/ $

C:\Users\jcaporal\AppData\Local\Android\Sdk\platform-tools>adb shell

shell@douglas:/ $

C:\Users\jcaporal\AppData\Local\Android\Sdk\platform-tools>adb shell

shell@douglas:/ $

C:\Users\jcaporal\AppData\Local\Android\Sdk\platform-tools>
[Fire HD 8 and HD 10 General] bigg6987:
well i feel stupid

I can't even get step one to work properly. Is there a version of this for people who are new to linux? I can only assume that's the problem, as I've typed exactly what was in the box, and received

"adb: error: failed to get feature set: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device."
[Fire HD 8 and HD 10 General] dutchthomas:
Check the device status with adb devices. If it shows up as unauthorized, try this

Computer:

-adb kill-server

Device:

-Go to the developer settings

-Toggle USB debugging off

-Revoke USB debugging authorizations

-Toggle USB debugging on

Computer

adb start-server

The device should ask for authorization when you try to connect next time
[Fire HD 8 and HD 10 General] CeticHax:
Updating Fire

Pulled out my Fire HD 8 (2017) and it's on 5.4.0.0, should I update or stay on my current version? I already completed this I just don't know if there's anything I'm missing out on.
[Fire HD 8 and HD 10 General] borissprat:
Have re-downloaded your excellent tool from here

I cant see any difference in the files (md5 checksum), could you post a new link here please to the updated version?

Very grateful for the work you have done btw.
[Fire HD 8 and HD 10 General] diplomatic:
How exactly did you install SuperSU? Did you follow the steps to copy su, libsupol.so, daemonsu, etc?
[Fire HD 8 and HD 10 General] diplomatic:
Release 12

The next release is out. This is the biggest update in years. :) Some of the highlights:

Unify the arm and armv7-kernel binaries into one

Support devices with kernel 4.9.x

Improve speed and possibly reliability

Fix arm64 support for phones on kernel 3.10.65

Fix stack protection workaround for armv7 kernels

Update readme file

This is the fastest and smoothest version yet. Everyone should update to it. As with any update, previously compatible devices could have become not-compatible. Let me know if that's the case.

The file is actually uploaded at the new MTK Temp Root thread. I will keep linking the OP here, but that will be the home of new releases from now on...
[Fire HD 8 and HD 10 General] ahhl:
sorry to jump here, but i have been re read the other side thread again to see what next for me if i successfully flash twrp.

should i follow this steps?
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=548005]ahhl[/MENTION], that procedure has nothing to do with twrp. (Do you even understand most of it?) Your next step is to see if your TWRP boots.
[Fire HD 8 and HD 10 General] THERAJ12:
If my fire HD 8 is already rooted from a previous version should I update to latest release and do I start from scratch to do so? Thanks
[Fire HD 8 and HD 10 General] dutchthomas:
If you're already rooted, there's no benefit from upgrading. The exploit isn't installed/persistent so there's nothing to update
[Fire HD 8 and HD 10 General] THERAJ12:
Thanks... Any reason why diplomatic said everyone should update to the latest version? That's why I was asking.
[Fire HD 8 and HD 10 General] dutchthomas:
It sound like a pretty big improvement, so I assume that people should use the newest version going forward. It's worth downloading in case you need it again, but it won't change anything about the root you already have
[Fire HD 8 and HD 10 General] diplomatic:
Yeah, but it's totally worth it to unroot and redo the whole thing just to experience the sheer smoothness & speed of the new mtk-su shell.... :laugh:
[Fire HD 8 and HD 10 General] Joven21:
My rooted fire hd 8 7gen has automatically updated itself this morning.. Root is gone.. Can i still root again using this?
[Fire HD 8 and HD 10 General] DB126:
Yes. After securing root you can prevent OTA (Over The Air) updates by renaming DeviceSoftwareOTA.apk to DeviceSoftwareOTA.bak or use the "Amazon Fire Toolbox": https://xdaforums.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
[Fire HD 8 and HD 10 General] Joven21:
Thank you
[Fire HD 8 and HD 10 General] amazon007:
successfully executed the root process, but my fire hd 10 2017 is not rooted

SEMIAUTOMATED-ROOT-V2.1.zip - [Click for QR Code] (15.57 MB, 692 views)

So I tried the above file and it says at the end, "Rooted" and rebooted my fire hd 10 2017, but then when I run

adb shell

su

There is no # prompt, nothing came up actually.

Then I run Titanium Backup and it takes very long time and then it says my device is not rooted. "Sorry I could not acquire root privileges...."

I checked supersu logs and it says:

ADB shell: SuperSU Pro is required for this feature

Titanium Backup: SuperSU Pro is required for this feature

I just want to disable those amazon bloatware as per

this post

How can I do that?

Thanks.
[Fire HD 8 and HD 10 General] borissprat:
Assuming you did not investigate supersu settings PROMT/GRANT; you could put supersu into a default of GRANT access, then run TB again to freeze or uninstall your bloatware.

Freezing apps under TB is probably safer, as it essentially keeps a record for you of what you have done, whereas using pm disable will force you to keep records for yourself of what you have done in case you break something and need to re-enable a "bloatapp". On my first Fire HD 10, I went the pm disable route but now I use TB instead.

If you want to proceed the pm disable route:

I ran into a similar problem where I could not get to # over ADB, which prompted me to try the "code" below. Somewhere in the mists of XDA there are more correct methods to obtain correct privileges via ADB once the tablet is rooted but as a newbie I couldn't be bothered finding out ("adb root" might be a thing here - who knows?). I figured simply re-running the exploit was worth a shot;

This worked for me

[*]You already will have mtk-su in the correct location on your device since you followed the OP.

Open an adb shell

adb shell

Change to your tmp directory

cd /data/local/tmp

Re-run the exploit for temp root

./mtk-su

Do not leave your command line window at this point, but run all of your pm disable commands under the temporary mtk-su.

mtk-su -c pm disable <name of package>

Instead of using the above approach, I tried to call the permanent su version as follows.

$ su
# pm disable <name of package>

It worked for me as I say.

If you actually do have permanent root, you could investigate

this post

to fix root access for Titanium Backup by editing the supersu preferences file (as I had to do) so you don't need to leave supersu in a default of granting root access to everthing.

"All Hail K"

[MENTION=8132642]diplomatic[/MENTION] thanks for this elegant temp-root method
[Fire HD 8 and HD 10 General] diplomatic:
Kind of redundant, isn't it? :) After running mtk-su, you already have a # prompt root shell. So pick one approach or the other...
[Fire HD 8 and HD 10 General] amazon007:
Thanks.

I set supersu into a default of GRANT access, then ran TB again to freeze but not able to because I was using free version.

But I was able to get the # prompt in adb shell.

So I copied the enable.sh file(to disable 32 packages) into data/local/tmp, then ran "sh data/local/tmp/enable.sh" and it worked.

(one error Error: java.lang.IllegalArgumentException: Unknown package: com.amazon.precog, but I will ignore it).

Then rebooted and it took several minutes on "optimizing system storage and applications" but no issue.

I will see if it runs more smoothly.
[Fire HD 8 and HD 10 General] robonxt:
[MENTION=8132642]diplomatic[/MENTION] Thank you so much for rooting this "unrootable" device!

Thanks for making the semi auto root. I spent a few hours trying to get permanent root but just a few clicks and a few code, I got it to work.

Thanks to everyone who help made this happen!
[Fire HD 8 and HD 10 General] fire1951:
Hi, need a little help, here. I have a Fire HD 8 7th gen. I used the Terminal method (no PC) of getting temporary root using r12 version of mtk-su. Every thing OK ,so far (Got the hash mark indicating root). I then used [MENTION=4584276]dutchthomas[/MENTION]' method of installing Supersu. I used the cp command instead of pushing with adb for copying su, supolicy, and libsupol.su to /data/local/ tmp . Other than that , I followed directions. Finished the procedure with no errors. Exited Term inal and started the Supersu app, which complains about not having the binaries.Can someone tell me what I am doing wrong? ( I cannot use a PC to do this). Thanks
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=8844012]fire1951[/MENTION], have you started 'daemonsu --auto-daemon' from root?
[Fire HD 8 and HD 10 General] Mr_Tadakichi:
Will this work on the 2015 hd8? :confused:
[Fire HD 8 and HD 10 General] Rortiz2:
Yes

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] fire1951:
Thanks for responding [MENTION=8132642]diplomatic[/MENTION] . Yes, I did run 'daemonsu --auto-daemon' from root. Just to be sure, I did everything again, but nothing changed....I had the same results as I described in my previous post. Any suggestions? Is there another way to get permanent root other than the [MENTION=4584276]dutchthomas[/MENTION] method? Or something else I could try? (not requiring a PC?) Thanks.
[Fire HD 8 and HD 10 General] howzitnow:
mounting system permission denied

I'm having problems after I get "root@douglas:/ #" and type "sh data/local/tmp/root_fire.sh"

I know you said run several times, but I've run at least eight and I'm getting mounting system read-write...mount: permission denied

Is there anything else I can do? (I did try swapping the mtk-su for version 12 and that kept giving set selinx to permissive errors)

Here's all the contents of the window

[*] Installing SuperSU.apk...

Success

apps\SuperSU.apk: 1 file pushed. 4.8 MB/s (6833108 bytes in 1.361s)

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

Success

[*] Pushing files and removing old files...

arm64/su: 1 file pushed. 2.2 MB/s (108480 bytes in 0.047s)

arm64/supolicy: 1 file pushed.

arm64/libsupol.so: 1 file pushed. 6.8 MB/s (334744 bytes in 0.047s)

3 files pushed. 4.9 MB/s (485936 bytes in 0.094s)

devices\hd8\mtk-su: 1 file pushed.

root_fire.sh: 1 file pushed.

[*] Setting permissions...

[*]Executing exploit...

wait until it finishes... When the exploit finishes, DON'T CLOSE THIS WINDOW

and type: sh data/local/tmp/root_fire.sh

param1: 0x3000, param2: 0x10000

Building symbol table

kallsyms_addresses pa 0x40b07300

kallsyms_num_syms 67971, addr_count 67971

kallsyms_names pa 0x40b8c100, size 817035

kallsyms_markers pa 0x40c53900

kallsyms_token_table pa 0x40c54200

kallsyms_token_index pa 0x40c54600

Patching credentials

init_task va: 0xffffffc000f16a20

Possible list_head tasks at offset 0x338

0xffffffc0030c8338 0xffffffc029675f38 0x000000000000008c

comm offset 0x5a8 comm: swapper/0

Found own task_struct at node 9

real_cred: 0xffffffc03f8ba080, cred: 0xffffffc03f8ba080

New UID/GID: 0/0

Parsing sel_read_enforce()

Found adrp instr at offset 4

ADRP x0, 0xffffffc001086000

Found ldr instr at offset 28

LDR [x0,4092]

selinux_enforce VA is 0xffffffc001086ffc

Setting selinux_enforce

Switched selinux to permissive

starting /system/bin/sh

root@douglas:/ # sh data/local/tmp/root_fire.sh

sh data/local/tmp/root_fire.sh

[*]Automated script.. Thanks to diplomatic!

[*]Mounting system read-write..

mount: Permission denied

[*]Removing old files..

[*]Copying Files..

rm: /system/xbin/su: No such file or directory

rm: /system/xbin/daemonsu: No such file or directory

rm: /system/xbin/supolicy: No such file or directory

rm: /system/lib/libsupol.so: No such file or directory

rm: /system/lib64/libsupol.so: No such file or directory

cp: /system/xbin/su: Read-only file system

mv: /system/xbin/daemonsu: Read-only file system

cp: /system/xbin/supolicy: Read-only file system

cp: /system/lib/libsupol.so: Read-only file system

cp: /system/lib64/libsupol.so: Read-only file system

[*]Setting permissions

Unable to open /system/xbin/su: No such file or directory

chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory

Unable to open /system/xbin/daemonsu: No such file or directory

chcon: Could not label /system/xbin/daemonsu with u:object_r:system_file:s0: No such file or directory

[*]Executing daemonsu..

data/local/tmp/root_fire.sh[23]: daemonsu: not found

Now update su binary and then write: exit

root@douglas:/ #
[Fire HD 8 and HD 10 General] diplomatic:
Is it that Spanish version of April Fool's already? :D

You can check if you have the right permissions/attributes for the files you've copied. For example, run 'ls -lZ /system/lib64/libsupol.so' to see the selinux context of that file. Also, do 'ls -l /system/lib64/libsupol.so' to see the file permissions. Actually, that might be what's missing, as you set the permissions for su & daemonsu but not libsupol.so. Before opening the SuperSU app, you should be able to call su from a regular terminal and get a root shell. You don't need to start daemonsu again until the next reboot....
[Fire HD 8 and HD 10 General] diplomatic:
Is it possible that you can run the procedure manually as described in post 10? That semiautomated tool is, let's just say, not great. It would also be best to install the version of the SuperSU app from the Play store. You said you swapped the mtk-su binary, which was the right move, but your output says otherwise. That tool has multiple versions of mtk-su for some reason--make sure you got the right one.
[Fire HD 8 and HD 10 General] Rortiz2:
Yes!:D Ok no.. I thought the hd8 2015 was the same as the hd8 2017.

And, the semiatuomated script I can tell you, it's ****. Even I admit it.
[Fire HD 8 and HD 10 General] diplomatic:
[MENTION=8978978]Rortiz2[/MENTION], well, then can you improve it? You said you were updating it, but nobody can find an updated version. :confused: If not, maybe you should say it's no longer supported, etc.
[Fire HD 8 and HD 10 General] nikothebarber:
adb push '/home/niko/droid/mtk-su_r12/arm64/mtk-su' /to/mtk-su /Internal%20storage/Android/data/local/tmp

failed to copy '/home/niko/droid/mtk-su_r12/arm64/mtk-su' to '/to/mtk-su': Read-only file system

??? what do i do?
[Fire HD 8 and HD 10 General] Rortiz2:
When I said update I was referring to remove the supersu "bad" But yes, I'm working on a better and no mistakes, and I'm testing it on my Aquaris M8.
[Fire HD 8 and HD 10 General] DB126:
Might want to put this in a dedicated thread or ask [MENTION=8132642]diplomatic[/MENTION] to include a link in the OP. Otherwise it will get lost/forgotten deep inside this thread.
[Fire HD 8 and HD 10 General] DB126:
Yikes - touchy. Appreciate your contributions to the XDA community.
[Fire HD 8 and HD 10 General] fire1951:
Thank you so much, [MENTION=8132642]diplomatic[/MENTION] ! I changed permission of libsupol.so and that took care of it! Supersu updated binaries and I changed permissions to 'grant' and I now have root. I previously 'hid' the safe to hide Amazon apps... will I now be able to uninstall the Amazon apps? Thanks again to [MENTION=8132642]diplomatic[/MENTION] and also [MENTION=4584276]dutchthomas[/MENTION] .
[Fire HD 8 and HD 10 General] howzitnow:
Trying again...I was able to get past the mount remount problem this time, now I get:

cp: /system/xbin/daemonsu: Text file busy

1|shell@douglas:/data/local/tmp # on step 7 of post #10.

I don't know if it matters, but I factory reset the tab this morning, I have re-added google stuff, killed lock screen ads, blocked updates with the Amazon fire toolbox V4, used laucher hijack to put nova launcher on, and download a few apps so I didn't have to use amazon stuff. (ie, firefox, solid explorer)
[Fire HD 8 and HD 10 General] Rortiz2:
Have you tried my automated root v3?
[Fire HD 8 and HD 10 General] howzitnow:
auto root v3

Yes, I tried that first thing. There were errors. I didn't remember what they were so I tried to run it again just now to copy the errors for you. This time tho, everything ran great, no errors. I updated the binaries, rebooted. But a root checker still says no root.
[Fire HD 8 and HD 10 General] Rortiz2:
Please READ! Set SuperSU to grant!

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] howzitnow:
Well that fixed it! Big thanks:good:
[Fire HD 8 and HD 10 General] iamsoinsane:
Thank you all who put in all the work, and sharing your knowledge for these root permissions. I was fine with my unit not rooted but with the launcher replaced. But when I woke up this morning and they disabled my launcher hijack, that was over the line. My device is now rooted. :D
[Fire HD 8 and HD 10 General] howzitnow:
Same here. So instead of me using an Amazon tablet with an alternative launcher, now I have a virtually no Amazon android tablet with a great launcher. Seems like they just shot their own foot.
[Fire HD 8 and HD 10 General] fire1951:
I have a question, if anyone knows. Before obtaining root, I used the 'pm hide' method to effectively disable all of the (safe to disable) Amazon apps. As I understand it, to actually uninstall certain Amazon apps, you run the risk of messing up the Fire's OS and rendering it inoperative. I had hoped to actually remove some of Amazon's bloat and recover some space, which I guess is not possible. (Please correct me if I am wrong!) My question is, what would I gain by 'unhiding' these apps and then freezing or quarantineing them? Thanks.
[Fire HD 8 and HD 10 General] cybersaga:
"pm hide" effectively disables them and prevents them from running. If your tablet still works after hiding those apps, then it'll still work if you completely uninstall those apps.
[Fire HD 8 and HD 10 General] fire1951:
Thank you, [MENTION=9294334]cybersaga[/MENTION] .
[Fire HD 8 and HD 10 General] robonxt:
Thanks for creating this and fixing the previous scripts! Hopefully this one works as well as v1 and definitely better than v2.1 (2.1 didn't work for me at all :p)

Also, I had to run the program twice to make sure SuperSU installs.

---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------

True, but if you try to uninstall some of the system bloatware by changing system app to normal app and uninstall, the lock screen breaks and you'll have to restore the tablet. I don't remember what apps causes this to happen, but it might have something to do with the either the Fire Tutorial or Alexa Cards
[Fire HD 8 and HD 10 General] cybersaga:
But did the lock screen still work when using "pm hide" on an app and then broke after you completely uninstalled that app?

That's what we're talking about: if you "pm hide" an app and the tablet still works, will it suddenly break if you completely uninstall that app? I'm saying no.
[Fire HD 8 and HD 10 General] robonxt:
Yes, it was still working with just pm disable. Yes, it breaks after you try to uninstall it, but I may be wrong since not everything Amazon was disabled and i haven't narrow down which app is causing the problem.
[Fire HD 8 and HD 10 General] fire1951:
So, Am I better off leaving well enough alone as far as the Amazon apps are concerned? I went through and 'pm hid' a bunch of Amazon apps a while back before root was achieved on the Fire HD 8's. Everything is working pretty good now and I don't want to mess anything up and have to start from scratch ! Has anyone actually uninstalled the Amazon stuff.... not just hid or disabled? I am glad to get root on this tablet, and I don't want to seem dense but what does it enable me to do that I could'nt do before? I already had Nova launcher on it, I hid the Amazon apps and disabled the lockscreen. On my older B&N tablet, I installed Marshmallow,etc.... I know I can't do that with the fire yet. , So is there other other optimizations I can do now that I have root? Thanks.
[Fire HD 8 and HD 10 General] diplomatic:
Guys, hate to be a buzzkill, but this is getting pretty off-topic now. Netflix problems and methods to remove apps have nothing to do with mtk-su. Probably better to move that discussion to a new or a more appropriate thread.
[Fire HD 8 and HD 10 General] fire1951:
Sorry about that. I was considering this a 'rooting' thread rather than just a 'mtk-su' thread, I guess... and I thought this the proper place to ask the sort of questions that I was asking.
[Fire HD 8 and HD 10 General] bigrammy:
:good: :good:
[Fire HD 8 and HD 10 General] nikothebarber:
an we please get a .SH too?

C
[Fire HD 8 and HD 10 General] ceffo:
hello, is there a way to get everything back to stock? I need to return my fire hd to amazon because of an hw issue...
[Fire HD 8 and HD 10 General] Kctucka:
Depends on what you've modified, but a factory reset, and flashing the most recent firmware should make previous root unnoticeable. Select firmware based on your device below:

https://www.amazon.com/gp/help/customer/display.html?nodeId=200529680
[Fire HD 8 and HD 10 General] ceffo:
should I run the factory reset from the fire settings or trough some tools in your opinion?
[Fire HD 8 and HD 10 General] Kctucka:
Fire settings will work. No need for other tools.
[Fire HD 8 and HD 10 General] Rortiz2:
[MENTION=8132642]diplomatic[/MENTION] it's time to remove EXPERIMENTAL from the title no?

Or its still Experimental?

Regards.
[Fire HD 8 and HD 10 General] ceffo:
seems like i can't install the original bin file from amazon...i've followed the instructions they gave about the manual installation but the tablet can't find the update...

any suggestion?
[Fire HD 8 and HD 10 General] Kctucka:
Do it from adb sideload in Recovery Mode. It'll be similar to the procedure in this post, but for whatever Fire tablet you have:

https://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire HD 8 and HD 10 General] diplomatic:
No, I guess it's pretty established already. :) But this thread is still going to have "experimental" in the URL if I change the title. Seems you can't get rid of it that easily...
[Fire HD 8 and HD 10 General] smileyint:
good to keep the title as is.
[Fire HD 8 and HD 10 General] Wambaxssss:
Hi team,

Quick question on my HD Fire H. Trying to run mtk-su on Termux. Moved mtk-su to home directory properly but the file system still cant' find it.

cd $HOME

ls

outputs: mtk-su storage

./mtk-su

bash: ./mtk-su: No such file or directory

What am I missing?

Thanks
[Fire HD 8 and HD 10 General] cybersaga:
Sounds like the file isn't where you think it is. Run

ls

and see if you see it. If you don't see it listed, then running

./mtk-su

won't work.