yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Probably the simplest thing is to use the Fire Toolbox to install PlayStore & other tweaks.

Be careful not to disable too many apps & services using Fire Toolbox as you can stop your FireHD10 booting properly if you disable certain things.

Always keep a copy of the flashable Lineage ROM and Magisk v20.4 on your installed microSD card, so if it fails to boot for some reason, you can always enter TWRP and clean flash the ROM & Magisk again.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I used the same instructions to root my 5.6.8.0 Suez. But I can't figure out how to install 12.1, I installed TWRP but can't figure out how to use it. (tablet not listed) how did you get TWRP to work?
[Fire HD 8 and HD 10 Original Android Development] smithbill:
TWRP just 'works' - you are holding down the relevant keys (forget what they are without Googling) to boot to TWRP Recovery aren't you?

Once in TWRP it's pretty much the same as always: format data (format, not wipe), copy on ROM zip (you may need to adb push it or sideload it after you formatted data), flash ROM, wipe cache/dalvik, reboot system.

It's basically as written in the Lineage12.1 thread: https://xdaforums.com/t/discontinued-rom-unlocked-suez-lineage-12-1-05-may-2020.3953677/
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
Thanks for writing back, I've been out of town or I would have seen this sooner. For some reason my Fire Tab is not booting into recovery mode. I hold the relevant buttons and it seems like it is moving into recovery mode for a min or so, then shows the amazon logo again and fires up like normal. I think that I'm going to reset the tablet and go through the rooting process again.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I was unable to preform a hard reset, must be blocked by one of the programs that I installed during the rooting process. I was able to reboot into fastboot mode and I'm looking for instructions on how to get into TWRP through fastboot. (if that is even possible)
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Err, I don't think you can enter TWRP from Fastboot mode, not sure though. But it does sound to me that TWRP isn't even installed (TWRP has nothing to do with root'ing per se).

I think you need to re-flash TWRP. I don't recall the exact details but, first you need to find & download the correct flashable TWRP image, then connect your FireHD to a computer, enter Bootloader mode and then use adb to flash the TWRP recovery image to the tablet (it's something like 'fastboot flash recovery TWRP.img') and then use adb to reboot the tablet into TWRP (something like 'adb reboot recovery')

Once the tablet is rebooted to TWRP, *then* you can format data & flash your ROM (you may need to adb push the ROM to the tablet after formatting data). And *before* rebooting, flash the root method (I think Magisk 20.4 works?). So the ROM and Magisk are flashed the first time you enter TWRP and before trying to boot to the system - I think this is necessary because if you don't, then the TWRP recovery image you just flashed through adb can be overwritten & lost, so flashing the ROM & Magisk on the first entry into TWRP should make it permanent.

I'm not sure though as it's been months since I flashed my FireHD10
[Fire HD 8 and HD 10 Original Android Development] gRooster:
How did you install TWRP? Did you follow all of the instructions on the first post of this thread to unlock the bootloader (which is necessary), or did you only root the device? I am guessing that you only rooted it, as (IIRC) it should have automatically booted into TWRP during the final step of unlocking the bootloader. Also, I have no idea if all this works on 5.6.8.0.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
In the amonet zip from OP is a script called boot-recovery.sh, very useful to boot into twrp (works only in case the exploit is in place). You may re-read the OP up to post #3 for details.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I think I should add some context...

I could not use https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/ because my HD 10 is 5.6.8.0, I used the instructions here https://github.com/3ch01c/3ch01c.github.io/blob/master/docs/how-to-setup-amazon-fire-hd10.md instead to get offline root via an exploit followed by installing SuperSU to maintain root. (the authors never meant to install a custom rom, only modify the current Amazon ROM so they did not unlock bootloader)

I proceeded to install the "official" TWRP app and in the "TWRP FLASH" was initially able to reboot into Amazon Recovery, but managed to mess something up so that the tablet won't reboot into recovery at all now (via the buttons or adb) just goes to black and white amazon logo, black screen, back to bw logo and fires up like normal (no recovery)

For a long time if I did "adb reboot bootloader" it would reboot into fastboot but keep disconnecting and reconnecting to the computer, but I think I was able to fix that today by installing the correct USB driver.

I just went into fastboot and tried "fastboot flash recovery twrp.img" and "fastboot flash recovery "TWRP_suez-180918.img"

I got the same error message both times

Booting Failed (remote: 'the command you input is restricted on locked hw')

I tried "fastboot oem unlock" and got the same error

Is there any way to get around this error?

I'm pretty lost at this point, is there any way to get TWRP working?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Solution for all offline/online or whatever tools rooted (i.e. supersu rooted) suez tablets is simple, only need to run this from OP:

sudo ./step-1.sh
sudo ./bootrom-step-minimal.sh
sudo ./fastboot-step.sh

If you can manage to boot the OS and you're able to call su in the shell, then try this.

If the OS won't boot, your tablet is somehow bricked and you have to use the 'unbrick' guide from post #2

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/post-79169423

You will have to open the device/partially take it apart and if you follow the mentioned guide, the 'sudo ./bootrom-step.sh' and 'sudo ./fastboot-step.sh' scripts will get your tablet unlocked/rooted with twrp installed.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Well, I'm not sure what the reason would be for you to not unlock the bootloader & then just flash a Lineage ROM or even flash the latest FireOS ROM from Amazon (5.6.9.0 is available here) so you have FireOS with unlocked bootloader, TWRP installed & rooted so you can use a different Launcher if you want with FireOS. That's what I have on both my FireHD10 so I can use voice commands with Alexa with Nova Launcher as the default.

I think you'll have to try @Sus_i instructions & unlock your bootloader etc.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I want to make sure that I am not missing something obvious with Ubuntu...

Using both a Window's Ubuntu shell and a memory stick booted version of Ubuntu I get the same results with the first three steps sudo ./step-1.sh

adb server version (41) does not match this client (39); killing...

*daemon started successfully And then the curser just blinks indefinitely

if I close the terminal and open it back up to run sudo ./bootrom-step-minimal.sh

it says "waiting for bootrom" I tried rebooting into fastboot with "adb reboot bootloader" but that doesn't help

Tried step sudo ./fastboot-step.sh while in fastboot, says <waiting for any device> in fastboot and after reboot

The pad is still booting, just won't boot into recovery mode at all. When I use adb command "reboot recovery" it boots normally, when I use adb command "reboot bootloader" it boots into fastboot
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Thats good. :)

Doesn't matter. ;)

As a first step, boot the tablet, connect adb and check superuser:

adb shell
su

Check popups on your tablet, enable root access for the shell.

The step1 script from OP works only in case you get # su access via adb shell and if you have done all steps from OP like this:

sudo add-apt-repository universe
sudo apt update
sudo apt install python3 python3-serial adb fastboot dos2unix
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager

If you did this and su is there, run: sudo ./step-1.sh

If you get some errors, maybe copy/paste the terminal output into code tags...
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Googling this error seems to suggest you have two adb servers running or there is some issue with the environment PATH. There is some blurb here which I didn't read all of.

If I recall correctly, I used a Linux Mint environment & didn't have any issues, so maybe that's a simple solution?

And more blurb here:

How To Resolve This ADB Server Version Doesn't Match This Client Error In Android? | The Dark Source

In this thread, we will resolve ADB server version doesn't match this client error, you will face some time while installing and configuring the ADB. Here we

thedarksource.com
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
Thanks Sus_i,

I had a serious set-back, installed Magisk without doing enough research. Now I'm stuck in a boot-loop and no working recovery mode. Planning on trying the brick script instructions.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
Thanks for the advice smithbill. Decided to install a duel boot of Mint to resolve the adb issues. First install of Mint went sideways and broke my laptop. Spent tonight reinstalling Windows and Mint, have both working now on a duel boot. Unfortunately I tried installing Magisk the other night after reading another thread and my tablet is stuck in a bootloop with no accessible recovery mode. The only thing I can think to do is to try and follow the brick instructions.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Always install Windows first, then boot a Linux Live from USB and either allow it to automatically install Linux alongside Windows for dual boot. Or you can use the Windows Disk Manager to 'shrink' your Windows C: partition leaving a block of Unused disk space, then Linux can be installed into that free space.

Presumably your FireHD can still get into Fastboot mode? I'm not sure of everything you can do in Fastboot mode, but this page:

https://www.makeuseof.com/tag/use-adb-fastboot-android/amp/

suggests you can do a lot like flashing new recovery images, wiping the system etc etc. Perhaps you could use 'adb sideload' something? Or uninstall Magisk?

Perhaps following the 'return to stock' instructions is an option, and once back at stock FireOS you could then restart the process to install TWRP etc
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
You could try the boot-recovery script from OP first, but I guess the unbrick solution from OP is the only way to fix it...

Back then I've watched a video on youtube, it's possible to open the tablet a few times without a single scratch :)
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
I believe boot-recovery should still work since he just overwrote the boot payload
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I actually messed up the boot recovery before this by trying to use the "official" TWRP App to flash itself onto the recovery mode. For some reason recovery mode stopped working. I was still able to boot into fastboot, but not now since my computer won't connect to the tablet while it is boot-looping.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
After rooting it intially with offline root instructions I tried installing TWRP with the "official" TWRP App. After flashing a new recovery mode, recovery mode just stopped working on the tablet, I'm not sure why. Fastboot mode was still accessable, but not now with it stuck in a boot loop. (I think)
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Yeah you completely killed it so you have to open it up now.

You can also try the fastboot brick exploit. If you're lucky enough it could work.

Good luck
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Never use updated versions in the initial process. Use only what's given. Once it's all sorted & settled, then you can consider upgrading TWRPs etc

Surely even in a bootloop, you can still force it into Fastboot mode by holding down the relevant keys whilst it tries to boot? If not, then I guess you really have bricked it & you'll have to try the 'opening it up' thing.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I did end up having to open it up. (twice) Didn't install Majisk or new ROM the first time. I re-opened it and have Linage 12.1 installed now. :) GApps failed to install for some reason. I'm going to install the fire toolbox and try to install them that way. Thanks for all of the help!
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Just to help others reading this, could you say a little about the process of opening it up & ultimately installing TWRP & LineageOS.

I found LineageOS 12 to be faster & with less issues than LineageOS 14. Eventually I gave up on both of them & went back to FireOS (but rooted & with TWRP) just so I could use it as an Alexa device with hot-word detection. Am I right in thinking there is an experimental LineageOS 16 for the FireHD10 2017 (suez)?

EDIT: There is a LineageOS 16 (see here) but it seems to have quite a few unresolved issues including camera & headphones.

I think Gapps Pico or Nano are the versions to use with LineageOS.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
So far linage 12.1 has been running fairly smoothly. The only drawback is that my son is not able to us a game that requires a newer version of Android to run. I'm not sure if I should try one of the less stable OS's or stick with 12.1.

Sure thing, I'll follow this post with one containing an in-depth walkthrough.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Well you may as well try Lineage14 - it worked pretty well from what I recall, only not as 'robust' as Lineage12.1. if Lineage14 is no good, you can always re-flash 12.1.
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I'll give 14 a shot, thanks for the advice.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Excellent write up - thank you for helping everyone else by cataloguing all your efforts. I think it's especially helpful to read about your mistakes along the way, as these will help others avoid making the same mistakes.

It's always a good idea to do your first reboot 'to recovery' (ie. TWRP) as sometimes just trying to reboot to system will result in the recovery being replaced by stock recovery.

And I'm pretty sure with TWRP now permanently installed on your FireHD10, you can just hold down the relevant keys on startup in order to boot into TWRP recovery (so you don't need your computer to issue 'adb reboot recovery' command).

And as you can just use the tablet & the relevant keys to reboot to recovery, you can just flash Lineage14 or 12.1 or even FireOS as required without having to resort to connecting up to a PC with adb installed. So it's always a good idea to keep a copy of the flashable zip for Lineage12.1, Lin14 and FireOS on your microSD. And you should keep a flashable TWRP on the microSD as installed TWRP can even flash TWRP itself. Also keep Gapps & Magisk on there, but remember if you flash FireOS 5.6.9.0 then you will have to use Magisk 20.4 as versions after that cause a bootloop - so a good idea to keep a copy of Magisk 20.4 on your microSD as well.

Also, the FireToolbox is useful if you use FireOS on your tablet rather than Lineage. And 'App Freezer' from Wakasoftware is great for disabling lots of Amazon junk (don't overdo it or you can cause your tablet to bootloop) - unfortunately, due to Google PlayStore changes, the version available in the PlayStore doesn't let you disable system services, but the previous version available from Wakasoftware does: http://wakasoftware.com/news/
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
Thanks so much for the advice! I explored installing 14 yesterday so that my son has access to a favorite game. I ran across the "fix" page. (Faster booting, make YouTube work, etc...) Is it still necessary to install all of those 10 or so "fixes" and would I flash them all through TWRP?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
There is a 'fix page' for LOS14?
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
It looks like I was mistaken, this thread is for the ford/austin
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
For some reason I still can't get into recovery mode using the buttons, I'm not sure how I messed that up originally
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Are you pressing the correct buttons?

See: https://www.hardreset.info/devices/amazon/amazon-fire-hd-10-2017/recovery-mode/
[Fire HD 8 and HD 10 Original Android Development] Barron Arrow:
I just tried pushing volume up instead of volume down and it worked!
[Fire HD 8 and HD 10 Original Android Development] k4v7uk:
Hi All

Im trying to unlock a Fire HD 10 2017 using the instructions at the beginning of this thread.

Im using Ubuntu 20.04 on the PC. I have installed the prerequisites. Because it has not been rooted I put mtk- su in amonet/bin. Adb debugging is turned on on the Fire. The Fire is running 5.6.9.0 so i expected this not to go smooth.

When I run step-1.sh I get

Failed critical init step 4

This firmware cannot be supported

I have been away from this stuff for a little while so im a little rusty. im hoping its something simple.

Any help would be appreciated

Thanx
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
You could watch a youtube video about 'opening the tablet' and then do the steps from post #2

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/post-79169423

This way you need no mtk root...
[Fire HD 8 and HD 10 Original Android Development] k4v7uk:
i would rather not tear it apart if im just doing something stupid, The Fire is working fine. Any other ideas?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
You can try the offline root method here:

HD 10 (2017): Offline rooting

Update: While this still works, there's an easier method here. Please try that first. Disclaimer #1: KingoRoot, dr.fone, and most other one-click rooting tools are characterized as malware. Should you use these tools? That decision is yours and...

xdaforums.com

In case you get root access, the OP should work fine, even without mtk-root.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Not sure about that particular error, but @Barron Arrow had issues using Ubuntu (see post #1410 above).

Also, @Barron Arrow write up in #1424 above may be helpful.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
There are a couple of links here that may or may not be helpful:

https://xdaforums.com/t/hd-10-suez-...tep-1-sh-failed-critical-init-step-4.4197463/

How to use MTKsu to root a mediatek android device

This is a quick guide showing how to use MTKsu to root a mediatek android device. This guide will come in handy if you have no other means of getting root i.e locked bootloader, unable to get magisk o

forum.hovatek.com
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Since Amazon stepped back counting the fireOS Numbers (5.6.6.0 is called 5.3.7.0), the error just mean that mtk-su is patched and isn't working anymore...

Good news is that the offline root still works (probably also king/kingoroot) and we can use that instead of mtk-su
[Fire HD 8 and HD 10 Original Android Development] smartypantsuk:
You need a different root method.

I've just put Lineage 12.1 on my Fire HD10 with firmware 5.6.9.0. It was straight forward with no issues but I got the same error you did.

Instead of the root method used in this post, use SuperSu instead then come back here and carry on with the rest of the process.
[Fire HD 8 and HD 10 Original Android Development] k4v7uk:
This sounds promising. Is there any documentation on here to get SuperSu on the Fire? It would be great if i could get this method to work. I really dont want to open the thing. Thanx for your help.
[Fire HD 8 and HD 10 Original Android Development] :
Hi together,

i am new at this forum and trying to bring a lineageos on my Fire HD 10.

But i got stuck at this point:

"NOTE: If you are on firmware 5.6.4.0 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)"

Furthermore i don't understand "After you have confirmed the bricking by typing "YES",

How can i temporarily brick the device to get to the next steps?

Where can i confirm a bricking procedure?

Thanks in advance

Chris
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
IIRC the script will guide you through the whole process. It will determine the FireOS version and, if needed, will suggest to perform the "bricking procedure" which it will ask you to confirm by typing "YES", as it is you who is in charge.

Perhaps you should read the full set of instructions a few times and then it may become a bit clearer.
[Fire HD 8 and HD 10 Original Android Development] :
Thank you!

But if step-1.sh is meant when you talking about IIRC, this script show me the following lines in a loop.

Failed critical init step 4

This firmware cannot be supported

Regards

Christian
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/post-85800165
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
You might be out of luck then and your FireOS version might be too new. Amazon does close such holes eventually. But then again I am not an expert, there might still be a way, but unfortunately I am not up to date regarding this topic anymore as I have already given up on my old 2017 tablets. Sorry!
[Fire HD 8 and HD 10 Original Android Development] yeonwoo1:
This might be a stupid question (I'm a newbie) but I have successfully rooted the device with magisk, now how can I go back to TWRP to flash lineageOS. I'm on version 5.6.9.0
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Try 'adb reboot recovery'
[Fire HD 8 and HD 10 Original Android Development] Deizelds:
Hey what's up, hoping someone might be able to assist. Decided to review my tablet and things were going good but at some point of my travels, I must have messed up the gpt table, because now everytime I boot my tablet, it tells me there's an internal error. I tried going back to rerun the step scripts and when I try to run #1, it tells me the user partition is not the last parittion, and jumps out of the script. I cannot figure out how to look at the gpt to possibly rectify the issue and when I'm in TWRP and I go into format, there are two storage at the end and when I try to wipe them, it says they cannot be formatted.
[Fire HD 8 and HD 10 Original Android Development] digixmax:
Can you please elaborate on what you did to use the SuperSU method, and provide any pertinent links?

TIA.
[Fire HD 8 and HD 10 Original Android Development] smashedpumpkins:
Thanks, this worked perfectly on my fully updated 5.6.9.0.
[Fire HD 8 and HD 10 Original Android Development] mhump711:
Confirmed working on HD10 version 5.6.8.0. FYI for anyone installing Lineage OS, first boot got stuck on the loading screen, going back to recovery mode and doing a factory reset fixed it.

Thanks smartypantsuk and k4v7uk and everyone else who worked on this.
[Fire HD 8 and HD 10 Original Android Development] Pikatch:
Do you have any plans to upgrade TWRP in the future?