yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] russ.75:
Fire TV 2 Second Gen

Hi guys, I am trying to root my Fire TV 2 Second Gen (5.2.7.0), but I am getting an error message after entering the ./mtk-su command. I get the same result using ./mtk-su -v. Any help would be greatly appreciated. Thanks

C:\Users\Russell>adb devices

List of devices attached

192.168.0.3:5555 device

C:\Users\Russell>adb push D:\Android\FireTV\Root\mtk-su_r15\arm64\mtk-su /data/local/tmp/

4250 KB/s (30464 bytes in 0.007s)

C:\Users\Russell>adb shell

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

shell@sloane:/data/local/tmp $ chmod 755

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

Failed critical init step 1

1|shell@sloane:/data/local/tmp $
[Fire HD 8 and HD 10 General] diplomatic:
Was this a new update? I can't find 5.2.7.0 mentioned anywhere. If it was just released, this may be bad...
[Fire HD 8 and HD 10 General] russ.75:
Thanks for the reply. Yes 5.2.7.0 is the OS version I have on my device. I don't know when it got updated. Looks like Amazon may have patched up the vulnerability with this new release. Unless I'm doing something wrong. I got so excited about the new root method being discovered again, that I'll now have to get another FireTV with an older OS version.
[Fire HD 8 and HD 10 General] bibikalka:
Has there been any work on finding BootRom contacts for this device? It's the same chip as Fire 10 2017, so potentially most components for clearing rpmb and downgrading the bootloaders are already available.
[Fire HD 8 and HD 10 General] diplomatic:
No, you did everything right. It does look like that's what happened. No point in sugarcoating it. I'd like to gather more info to see if anything can be done about it....

I don't think so, but that shouldn't be hard, right? It would be the same process as the HD 10. Just need someone who kind of knows what he's doing to open up that box and try some pins. There are a few people on XDA who bricked their FireTVs. That would give them a chance to recover them too...
[Fire HD 8 and HD 10 General] diplomatic:
Release 16

A new release has been uploaded. This one has the rumored support for the new Amazon Fire 7. It also handles Walmart's new Onn 8" and 10" tablets. It might run a bit faster too.
[Fire HD 8 and HD 10 General] Kctucka:
I'm glad the rumors I helped spread were accurate :o
[Fire HD 8 and HD 10 General] Klibi:
hey gents,

I am trying since hours to understand the concept and the code but I cannot get behind it and I am very disappointed about my own

sillyness... If someone could help me that would definitely make my day.

I am stubling across the root access topic. I did understand that I need to run the script from the "host" linux system.

But now I only get this:

sudo ./step-1.sh
Testing root access...

Trying to use mtk-su to get temp root...
Pushing root files
735 KB/s (30464 bytes in 0.040s)
3908 KB/s (1048576 bytes in 0.262s)
3873 KB/s (989184 bytes in 0.249s)
New UID/GID: 0/0
New UID/GID: 0/0
New UID/GID: 0/0

I do understand that the script checks If it has root access, but isn't that what it tries to achieve with mtk-su? If I do it manually acc. to the linked thread (https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595) it works flawlessly, but I do not understand the concept behind this script.

I tried to debug until where I get to, but I don't know how to move on. The many guides (many of them are old) in the internet about super su and such are really confusing me. I already bricked the device with such an old guideline and I just like to run this script to get rid of the non-unlocking possibility of fully kiosk browser.

If someone could help me, I would really appreciate it ;)

Cheers!!!! :good:
[Fire HD 8 and HD 10 General] diplomatic:
If you're getting repeated "New UID/GID", it means your adb is too old. It does not process the syntax in those scripts correctly. You need to install the right adb package from a recent Linux distro. Or grab Google's platform tools for Linux here: https://developer.android.com/studio/releases/platform-tools
[Fire HD 8 and HD 10 General] Klibi:
You made my day!!! Installed the latest adb and it works, thanks so much!! ;)
[Fire HD 8 and HD 10 General] amazon007:
rooted my fire hd8, disabled OTA, but still updated to fire OS 5.6.4.0

Hi I successfully rooted my fire hd8 at end of April, and disabled OTA & amazon launcher, but my device was updated to Fire OS 5.6.4.0 on 6/11, and fire launcher replaced nova launcher.

Anyone experienced same?

Thanks.
[Fire HD 8 and HD 10 General] Dan_firehd:
You have to give more details on steps you took to "disable OTA" back in April, so that others can advise whether you have made any mistake in "disabling OTA".
[Fire HD 8 and HD 10 General] amazon007:
Thanks.

I ran lots of pm disable command, and this is the one to disable ota:

pm disable com.amazon.kindle.otter.oobe.forced.ota

this one disabled firelauncher:

pm disable com.amazon.firelauncher
[Fire HD 8 and HD 10 General] Dan_firehd:
Well, back in April, did you also disable this even more important one?

pm disable com.amazon.device.software.ota
[Fire HD 8 and HD 10 General] DB126:
If rooted the only action required is to rename DeviceSoftwareOTA.apk. 100% effective on every major version of FireOS since v4.
[Fire HD 8 and HD 10 General] amazon007:
Thank you!

I got the list of packages to disable from somewhere in this forum, and com.amazon.device.software.ota was not included in the list, so I guess I will have to do it again.

Or I will try to rename the file as suggested by [MENTION=5488402]Davey126[/MENTION].
[Fire HD 8 and HD 10 General] DB126:
Rename it. "pm disable..." is easily reversible as evidenced by all those who claim to have disabled OTA updates yet get whacked at a later time. Roll the dice or own the game; your choice.
[Fire HD 8 and HD 10 General] Supermatt01:
Thanks it reduces security, but it didn't give me root rights for apps.
[Fire HD 8 and HD 10 General] Don't Hassle Da Hoff:
I was late to the party I guess. My devices are running the same version and receive the same error at that point.
[Fire HD 8 and HD 10 General] troy_77:
Worked perfectly on the first try with my new HD 8. Thank You! :D
[Fire HD 8 and HD 10 General] Xbgzx:
Missing Notification bar, home bar..

After running this I dont have access to my top or bottom bar on my screens, so no way to switch between apps, or hit a home button. Anything I can do to recover? I've already factory reset and nothing has changed..
[Fire HD 8 and HD 10 General] DB126:
Sounds like you're stuck in expanded desktop mode. Not sure how you toggle that in fire OS, and the method may change depending on V5 or v6 (you didn't identify the device). Typically swiping down from the top or up from the bottom will give you temporary access the status and navigation bars. If all else fails you can always reload fire OS via the stock recovery menu.
[Fire HD 8 and HD 10 General] Xbgzx:
Yea, swiping up or down doesn't work for either, and I had factory reset through the OS -- 5.3.6.4. on a Fire HD8 Is there a work-around maybe an app I can try? Or should I attempt to wipe it and start over with a fresh FireOS install or something else? I'm very new to this so any guides that may help would be greatly appreciated :)
[Fire HD 8 and HD 10 General] DB126:
Factory reset only clears personal data; does nothing to restore lost/altered FireOS functionality. Sounds like you have a 7th gen HD8. There are plenty YouTube vids that demonstrate reloading FireOS. Pretty easy. Alternatively, you can wait to see if another member posts an opinion. Strongly encourage avoiding 'hacks', apps or other BYO solutions that will come back to bite you later. Good luck.
[Fire HD 8 and HD 10 General] AmznUser444 Dev:
mtk-su v16 it's working on my Fire HD 8 2018
[Fire HD 8 and HD 10 General] AmznUser444 Dev:
How to use it
[Fire HD 8 and HD 10 General] DB126:
- line mode commands (eg: sysctl)

- install root manager for perm access: https://xdaforums.com/hd8-hd10/general/tut-root-hd82018-via-magisk-t3906554
[Fire HD 8 and HD 10 General] Vague Rant:
Fire HD 10 2017 here.

I have never done any Android rooting before, so I apologize for my poor understanding.

Does the automated root script by [MENTION=8978978]Rortiz2[/MENTION] give permanent root, or is it temporary and requiring something more to be done after?

The other thread about root on Fire HD 10 talks about how it will restore the device to factory settings, etc., so all files on the device are lost. Does Rortiz2's script do that too? Would I need to go through that to get permanent root?

Thanks for any help! Again, sorry for the very sub-beginner questions. :o
[Fire HD 8 and HD 10 General] DB126:
Best review the opening post that describes this as a temp root solution that opens the door for permanent root or mucking around with privileged 'line mode' commands (my preference). It does not alter the contents of your device... absolutely non-destructive with no advertise side effects. Of course, what you do after securing root is an entirely different matter. Play carefully and always have an exit strategy.
[Fire HD 8 and HD 10 General] Rortiz2:
Yep, it gives permanent root.
[Fire HD 8 and HD 10 General] DB126:
Nope; goes away after reboot or other event that clears permissions. However, it can be used to secure permenant root. Review opening post for details.

Edit: above comment only applies to mtk-su (subject of this thread), not [MENTION=8978978]Rortiz2[/MENTION]'s script. Sorry for any confusion.
[Fire HD 8 and HD 10 General] Kctucka:
I can confirm the script by Rortiz2 gives permanent root, as I've used it on my 2017 HD 8. Only works on Fire OS 5 tablets.

mtk-su will just give temporary root though.
[Fire HD 8 and HD 10 General] DB126:
You are (obviously) correct on both points. Sloppy reading on my part; I was single tracked on the mtk-su solution by [MENTION=8132642]diplomatic[/MENTION].

Apologies to [MENTION=8978978]Rortiz2[/MENTION] for mischaracterizing his script.
[Fire HD 8 and HD 10 General] majeec:
Now that I've used the automatic root to root my Fire HD 8 (7th gen), what can I do with this root access? What is the best way wipe this thing clean and get a nice new launcher/UI with improved battery life for the device? (please respond in layman's terms because I am new to these forums)
[Fire HD 8 and HD 10 General] DB126:
There are no custom ROMs for this device at present so you'll need to make due with tweaking FireOS. Best results for noobs are obtained using the Fire Toolbox. Lots of guidance in these forums too. Advise staying away from aggressive/unusual/unpopular mods until you gain more experience. Usually not worth the headache even for veterans. Good luck.

https://xdaforums.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
[Fire HD 8 and HD 10 General] Athinar:
Parsing avc_denied

When I run the SuperSu, says it is not Rooted

Parsing avc_denied? will this stop the root?

shell@suez:/data/local/tmp # ./mtk-su -v

param1: 0x1000, param2: 0x8040, type: 9

Building symbol table

kallsyms_addresses pa 0x40aa4700

kallsyms_num_syms 66790, addr_count 66790

kallsyms_names pa 0x40b27000, size 832894

kallsyms_markers pa 0x40bf2600

kallsyms_token_table pa 0x40bf2f00

kallsyms_token_index pa 0x40bf3300

Patching credentials

Reading __ksymtab_init_task

init_task VA: 0xffffffc000e3a960

Potential list_head tasks at offset 0x368

0xffffffc020120368 0xffffffc04e86eae8 0x000000000000008c

comm swapper/0 at offset 0x5e0

Found own task_struct at node 0

real_cred VA: 0xffffffc066ee1f00

Parsing avc_denied

ffffffc00027629c+20: ADRP x0, 0xffffffc000f46000

ffffffc00027629c+24: LDR [x0, 2116]

selinux_enforcing VA: 0xffffffc000f46844

Setting selinux_enforcing

Selinux is already permissive

New UID/GID: 0/0

C:\ADB>adb devices

List of devices attached

G000N607810307H7 device

Fire 10 HD 7th Gen

OS. 5.6.4.0 (636558720)
[Fire HD 8 and HD 10 General] SirHappyCatIII:
That script will give permanent root to your device, just make sure you set default app root access to Grant in the SuperSU app after running it! :)
[Fire HD 8 and HD 10 General] idorobots:
mtk-su didn't work for me, here's my output

130|shell@suez:/data/local/tmp $ ./mtk-su -v
param1: 0x1000, param2: 0x8040, type: 9
Building symbol table
kallsyms_addresses pa 0x40aa4700
kallsyms_num_syms 66790, addr_count 66790
kallsyms_names pa 0x40b27000, size 832894
kallsyms_markers pa 0x40bf2600
kallsyms_token_table pa 0x40bf2f00
kallsyms_token_index pa 0x40bf3300
Patching credentials
Reading __ksymtab_init_task
init_task VA: 0xffffffc000e3a960
Potential list_head tasks at offset 0x368
0xffffffc020120368 0xffffffc054d7b168 0x000000000000008c
comm swapper/0 at offset 0x5e0
Found own task_struct at node 1
cred VA: 0xffffffc06ce21600
Parsing avc_denied
ffffffc00027629c+20: ADRP x0, 0xffffffc000f46000
ffffffc00027629c+24: LDR [x0, 2116]
selinux_enforcing VA: 0xffffffc000f46844
Setting selinux_enforcing
Selinux is already permissive
New UID/GID: 0/0
starting /system/bin/sh
shell@suez:/data/local/tmp # mtk-su -s
/system/bin/sh: mtk-su: not found
127|shell@suez:/data/local/tmp #
[Fire HD 8 and HD 10 General] k4y0z:
Are you kidding?

It has obviously worked flawlessly.
[Fire HD 8 and HD 10 General] idorobots:
Haha my mistake then, I was in a rush this morning and thought that executing

mtk-su

was essentially an alias for sudo once I had entered the root shell when in reality once I'm in the root shell every command I execute is as root
[Fire HD 8 and HD 10 General] langustino:
I can't mount system as RW, :crying: why?

my output:

C:\adb>adb shell
shell@C708:/ $ cd /data/local/tmp
shell@C708:/data/local/tmp $ chmod 755 mtk-su
shell@C708:/data/local/tmp $ ./mtk-su -v
param1: 0x3000, param2: 0x18040, type: 1
Building symbol table
kallsyms_addresses pa 0x40b4bf00
kallsyms_num_syms 48776, addr_count 48776
kallsyms_names pa 0x40bab500, size 595588
kallsyms_markers pa 0x40c3cc00
kallsyms_token_table pa 0x40c3d200
kallsyms_token_index pa 0x40c3d600
Patching credentials
Parsing current_is_single_threaded
ffffffc0002fd698+50: ADRP x0, 0xffffffc000dee000
ffffffc0002fd698+54: ADD xd, x0, 2576
init_task VA: 0xffffffc000deea10
Potential list_head tasks at offset 0x340
0xffffffc0030d0340 0xffffffc004888340 0x000000000000008c
comm swapper/0 at offset 0x5c0
Found own task_struct at node 1
cred VA: 0xffffffc02ff91080
Parsing avc_denied
ffffffc0002a4af0+20: ADRP x0, 0xffffffc000ef2000
ffffffc0002a4af0+24: LDR [x0, 3836]
selinux_enforcing VA: 0xffffffc000ef2efc
Setting selinux_enforcing
Selinux is already permissive
New UID/GID: 0/0
starting /system/bin/sh
shell@C708:/data/local/tmp # mount -o remount -rw /system
mount: Read-only file system
255|shell@C708:/data/local/tmp # cp /data/local/tmp/su /system/xbin/su
cp: /system/xbin/su: Read-only file system
1|shell@C708:/data/local/tmp # cp /data/local/tmp/su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Read-only file system
1|shell@C708:/data/local/tmp #
[Fire HD 8 and HD 10 General] Kctucka:
What device are you trying to run this on? If it's running android Marshmallow+ it'll have dm-verity enabled, and you won't be able to modify system without issues.

Also, as it's non Amazon, you're better off asking here:

https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
[Fire HD 8 and HD 10 General] AmznUser444 Dev:
What's example of mtk-su -c?
[Fire HD 8 and HD 10 General] Rortiz2:
mtk-su -c "mount -o rw,remount*/system"

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 General] diplomatic:
Almost, [MENTION=8978978]Rortiz2[/MENTION], except it doesn't support quotes:

mtk-su -c mount -o rw,remount /system
[Fire HD 8 and HD 10 General] DoGoXD:
FireStick v2 OS v 5.2.6.9

Status: Failed

:crying:
[Fire HD 8 and HD 10 General] diplomatic:
Well, I guess it doesn't work on the Fire TV Stick then, [MENTION=10060110]DoGoXD[/MENTION] :rolleyes:
[Fire HD 8 and HD 10 General] iammrhappy123:
Hey guys

I'm running the automated v3 mtk-su file

It's been sitting at:

[*] Executing daemon...

New UID/GID: 0/0

for a while now.

What should I do?

Thanks

---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------

Hey guys

I'm running the automated v3 mtk-su file

It's been sitting at:

[*] Executing daemon...

New UID/GID: 0/0

for a while now.

What should I do?

Thanks
[Fire HD 8 and HD 10 General] Drunkpilot:
Try restarting and going through the commands again. Like it says in the op, it doesn't always work the first time. I used an automated script too. I think I remember it either worked when I gave the .bat script administrative priveleges, or I just did the regular double click way. It took a few times when I rooted my HD 8 6th gen.
[Fire HD 8 and HD 10 General] :
Deleted
[Fire HD 8 and HD 10 General] DarraghMUFC:
I've not gotten very far in the process, my MTK-SU binary is on my desktop(in the arm64 folder) as you can see in the code. There was no local/data/tmp folders on my tablet's SD Card(am i even meant to make one myself?) so I made one myself(putting data into local and tmp into data ect). When I get to step 5 and i need to input

chmod 755 mtk-su

i get an error that mtk-su is not found as seen below.. anyone able to figure out why? Thanks! (my device is Fire10 running OS 5.6.1.0 if this is relevant)

ubuntu@ubuntu:~$ adb push /home/ubuntu/Desktop/arm64 /data/local/tmp/
/home/ubuntu/Desktop/arm64/: 1 file pushed. 1.1 MB/s (38736 bytes in 0.033s)
ubuntu@ubuntu:~$ adb shell
shell@suez:/ $ cd /data/local/tmp
shell@suez:/data/local/tmp $ chmod 755 mtk-su
Unable to open mtk-su: No such file or directory
[Fire HD 8 and HD 10 General] Rortiz2:
You push the entire arm64 folder. You need to push only mtk-su:

adb push /home/ubuntu/Desktop/arm64/mtk-su /data/local/tmp
[Fire HD 8 and HD 10 General] DarraghMUFC:
Thank you for your help,it managed to work and i got

ubuntu@ubuntu:~$ adb push /home/ubuntu/Desktop/arm64/mtk-su /data/local/tmp
/home/ubuntu/Desktop/arm64/mtk-su: 1 f...shed. 4.7 MB/s (38736 bytes in 0.008s)
ubuntu@ubuntu:~$ adb shell
shell@suez:/ $ cd /data/local/tmp
shell@suez:/data/local/tmp $ chmod 755 mtk-su
shell@suez:/data/local/tmp $ ./mtk-su -v
param1: 0x3000, param2: 0x10000, type: 9
Building symbol table
kallsyms_addresses pa 0x40aa1f00
kallsyms_num_syms 66739, addr_count 66739
kallsyms_names pa 0x40b24600, size 832223
kallsyms_markers pa 0x40bef900
kallsyms_token_table pa 0x40bf0200
kallsyms_token_index pa 0x40bf0600
Patching credentials
Parsing current_is_single_threaded
ffffffc0002cda0c+50: ADRP x0, 0xffffffc000e36000
ffffffc0002cda0c+54: ADD xd, x0, 2400
init_task VA: 0xffffffc000e36960
Potential list_head tasks at offset 0x368
comm swapper/0 at offset 0x5d8
Found own task_struct at node 1
cred VA: 0xffffffc034085a80
Parsing avc_denied
ffffffc000276104+20: ADRP x0, 0xffffffc000f42000
ffffffc000276104+24: LDR [x0, 2116]
selinux_enforcing VA: 0xffffffc000f42844
Setting selinux_enforcing
Selinux is already permissive
starting /system/bin/sh
UID: 0 cap: 3fffffffff selinux: permissive
shell@suez:/data/local/tmp #

according to the first post in this topic i should have temporary root, I checked with root checker and it didn't detect root, is this normal? I closed the terminal and redid the process to see if that changed anything. Can you help out a silly man?
[Fire HD 8 and HD 10 General] NFSP G35:
You have a temporary root

terminal

.

After running MTK-SU, Any commands you execute from that terminal will be executed as root.

It does not give root access to any other apps, install su, or anything else like that.

Those are the kinds of things you might do from the terminal, though it will vary from device to device, or the goal you're trying to achieve.

---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------

You have a temporary root

terminal

.

After running MTK-SU, Any commands you execute from that terminal will be executed as root.

It does not give root access to any other apps, install su, or anything else like that.

Those are the kinds of things you might do from the terminal, though it will vary from device to device, or the goal you're trying to achieve.
[Fire HD 8 and HD 10 General] DarraghMUFC:
Im following this thread https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639 I'm using MTK-SU temporarily in the process to flash TWRP and to root my fire10. That's my end game basically.
[Fire HD 8 and HD 10 General] acr123:
problems with automated script Fire HD 8 (2018)

Fire HD 8 (2018) using Fire OS 6.3.0.1 . I have tried using the automated script many times ( I used the mtk-su arm version) and get the output below . It " finishes" and brings up SuperSu which says no root so will not open. Any suggestions???

Root script for Fire HD8/HD10 2017 and others MT81XX/MT67XX

based devices.

Thanks to diplomatic for create "MTK-SU".

Press any key to continue . . .

[*] Installing SuperSU...

Success

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

files\mtk-su: 1 file pushed.

arm64/su: 1 file pushed.

arm64/supolicy: 1 file pushed. 2.6 MB/s (42712 bytes in 0.016s)

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

3 files pushed. 7.4 MB/s (485936 bytes in 0.062s)

[*] Copiyng files...

mount: '/dev/block/dm-0'->'/system': Device or resource busy

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/: Is a directory

[*] Setting permissions...

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

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

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

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

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

[*] Executing daemon...

Starting: Intent { act=android.intent.action.MAIN cmp=eu.chainfire.supersu/.Main

Activity }

Completed! Now update the binary!

Press any key to continue . . .

Thanks,

Al
[Fire HD 8 and HD 10 General] Kctucka:
If you read the description for automated root, you'll notice it only works on 2017 HD 8 and below.

If you want permanent root on that device, you'll need to look at one of the unlock threads, that are linked in the OP.
[Fire HD 8 and HD 10 General] 9000RPM:
Thank you, that was easy!
[Fire HD 8 and HD 10 General] bibikalka:
You could enter Bootrom without opening your hd8 2018, as per this post:

https://xdaforums.com/showpost.php?p=78993820&postcount=13

Once in bootrom, do this procedure from the very beginning to unlock the bootloader:

https://xdaforums.com/hd8-hd10/orig-development/fire-hd-8-2018-downgrade-unlock-root-t3894256

If Bootrom hangs, wait for it to die due to battery discharge, that's why I recommend starting the procedure with very low battery charge!

If it comes to worse, and the above steps fail, you will have to remove the back cover to short the contacts.
[Fire HD 8 and HD 10 General] dutchthomas:
Nice! Linked this in post #10 because automated is best
[Fire HD 8 and HD 10 General] plusmce:
Too much work to root for my hd8 8th gen I'm pass for now I will wait for kingoroot method like I rooted my hd10 2017 , The only reason I want root my devices for adaway + disable the firelauncher and I did it I use temp root to disabled the firelauncher and set nova launcher as default and then use adguard premium to block ads now everything works perfect I can even use temp root to remove Amazon bloatware pm disable / pm uninstall for example . But really thanks all of you guys !
[Fire HD 8 and HD 10 General] obvious:
My 2017 hd8 has been switched off for the last year or so waiting for software root so it's deliberately on an older software version.

Is it sensible/recommended to let it auto update to latest version before rooting?
[Fire HD 8 and HD 10 General] my.ads0:
I'm on the same device with the latest software and I rooted without issue.