yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] mbwd:
I previously (like 2 years ago) rooted my FireHD 10 2017 7th Gen, but then gave it to my wife and it seems to have autoupdated/lost root. It currently says it is running FireOS version 5.7.0.0.

Is it correct that I need to brick it because I am on > 5.6.4.0 (see excerpt from op):

Or is 5.7.0.0 really 5.3.7.3?

@kovren, what did you do - and did it work?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
@Rex218 This might help?
[Fire HD 8 and HD 10 Original Android Development] joseph230:
After bricking, and unbricking my Fire HD10 7th Gen, finally I have TWRP installed. I can go to "hacked fastboot" from TWRP as well.

For next steps, I have couple of quetsions:

- Does this mean I have "Unlocked Bootloader" now? If not, is it possible to unlock? how?

- I want to Insall lineage OS. I see version 18.1 listed in this forum. Is flashing through TWRP is safe even if my bootloader is not unlocked?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
Hey there,

- Does this mean I have "Unlocked Bootloader" -- Yes, its unlocked.

- I want to Insall lineage OS. I see version 18.1 listed in this forum. -- Yes this is how you do it.

In TWRP you select a zip file and install it through TWRP.

look for any one of these files on various sites.

View attachment 5768479

With TWRP installed it makes it so that you can flash on different "Roms/OS's" without fear of bricking the device. If the flash is bad, big deal you can just boot into TWRP and try a different one.

Best of luck.
[Fire HD 8 and HD 10 Original Android Development] joseph230:
Thank you for quick response.
[Fire HD 8 and HD 10 Original Android Development] joseph230:
I installed Lineage 16 successfully but cannot get OpenGapps installed. Even Pico version throws not enough system space error!

Under TWRP I can see that system partition has over 300MB of free space. Gapps pico is 188MB zipped!

How did you resolve that issue?
[Fire HD 8 and HD 10 Original Android Development] likwidchz:
You can use an older version of Lineage, not the latest as it has been confirmed that the Gapps doesnt work. I recall pico working. Search around.

The other option is sideload everything or install a different package manager apkpure or something else.

Older version of lineage is also fine. Just experiment. The more you experiment with things the more knowledge you will have in the end. With forums, you do have to piecemeal it all together. Keep at it though.
[Fire HD 8 and HD 10 Original Android Development] psi78:
for Fire HD 10 2017 aka "suez" there is no LineageOS 18.1 ROM at the moment. Probably you mean the ROM for karnak which isn't for your device

Read the LOS 16 thread for suez/Fire HD 2017, especially the last pages. You can repartition (could break something) or debloat the system partition to make opengapps pico work. Bitgapps (gapps rebuild by @TheHitMan) may also work, it's smaller than opengapps pico.
[Fire HD 8 and HD 10 Original Android Development] amberlink:
I get to step 3, and when I do, it just sits there with nothing happening. What am I doing wrong?

Edit: I get

* daemon not running; starting now at tcp:5037

* daemon started successfully

But that's all it will ever show
[Fire HD 8 and HD 10 Original Android Development] _ck_:
Thanks to everyone maintaining various things for this and adding instructions along the way.

Just to help others in 2022-2023 to the Fire HD10 2017

This has been lost in time on this thread but you CAN still root with 5.7.0.0 you just CANNOT use mtk-su because it's been patched against so the instructions are outdated, hence the confusion when it errors-out.

But you MUST root before you can install TWRP, there is no other way, otherwise you get all the errors.

You need to go to a far more manual exploit, it looks tedious but you only have to do it once and maybe 10-15 minutes tops once you have a working ubuntu live usb or virtual install

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/page-73#post-85824221

This root method is nice because it's all offline, no wifi needed.

Very very hard to brick the HD10 which is nice, I got into a bootloop at first try but even Amazon's own ADB sideload will still take the stock image from their website and recover, just tedious.
[Fire HD 8 and HD 10 Original Android Development] SingleMalt69:
Spoke to soon. Rebooting to system just puts me in a bootloop. Amazon logo shows up for about 40 seconds, screen goes black, and repeats.

Since I can't get to the system, I can't run your return-to-stock script, since ADB is not up and running.

I can get back to recovery however (Power+VolDn), so I tried TWRP's Advanced/ADB Sideload, then pushed my 5.6.0.1 stock image with "adb sideload update-kindle-40.5.9.5_user_595550320.bin", like I normally do with the regular Amazon recovery. The image appeared to take, but the device still just boot loops.

Any ideas on how to recover from this boot loop?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Your firmware is likely to old, just update to 5.6.3.0 through TWRP.
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
I tried running the second script several times, but no go. So I tried that command in my command window. It hangs, but "adb shell" gives me "shell@suez:/ $" and an "ls" gives a list of the root directory.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
No idea, but here's a list of things you can try:

sudo adb kill-server

Try the newest version of adb from platform-tools: https://developer.android.com/studio/releases/platform-tools

Restart and replug the device

EDIT:

Is it possible, you have some broken su-binary installed in system?

Try installing the 5.6.3.0-firmware through adb sideload, so you have a clean system.
[Fire HD 8 and HD 10 Original Android Development] SingleMalt69:
Duh, that did it, thanks. I'm so used to the mantra of "NEVER UPDATE YOUR OS!" with these devices that I didn't even think of it.

- Successfully booted to 5.3.6.4.

- Was able to flash Magisk from TWRP

- Installed Magisk Manager from APK.

Ready for the custom ROM now :) :)
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Not on this one. It's the one I just lost. The only thing it did was shut off after working fine. It might be the battery. I don't know if it charges or not even if I plug it in and hold down the button.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Try replacing modules/common.py with the one attached, but I doubt it will make a difference.

Does the device go into bootrom when you don't short anything?

EDIT:

bootrom-step.sh should still work with a dead battery (it should be disconnected anyway during that step)

It's more likely an issue with EMMC.
[Fire HD 8 and HD 10 Original Android Development] Buzzy42:
Even after reading this thread, I'm a bit confused about where to start given my situation; I have a FireHD 10 that was rooted back with the original Kingoroot (then swap to SuperSU) method back in 2017. I never updated beyond 5.6.0.1 I believe-- whatever the most recent FireOS was at the time of the root. I understand I'll have to wipe it and start over, should I start where I am and flash 5.6.3.0 later from TWRP? or should I factory reset/wipe it now and start this process with the Fire at 5.6.3.0? (or am I overthinking it and it doesn't matter)

Thanks so much for finally unlocking these devices, this is really exciting news!!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Both ways SHOULD work fine, but given that some people apparently had issues with their current root-setup, it's probably better to start with a fresh 5.6.3.0.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
It was in bootrom when it was suggested I check a few days ago. The same error is still happening. Emmc read error. Same as last time. Not that it would make a difference, but I tried the tablet I bricked a while back and it too is coming up with the same emmc error.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You said before, that it was in preloader-mode, not in bootrom.

If it now goes into bootrom without you shorting anything and it never went past "Check GPT", then it's definitely a hardware-issue.

It means that it can't access the EMMC.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I will have to check when I get home. When I plugged it in a few days ago I'm sure it was preloader mode. That's where I got the serial errors. Then when I reset the tablet and short again it's in bootrom. That's why I kept getting errors because it kept reading preloader mode. It gets to get and I haven't gotten past it yet.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Not sure if this matters at all but throwing it out there. In the root directory, fstab.mt8173 doesn't list the system as EMMC, nor is the data partition. They are ext4. The more important ones are EMMC.

https://xdaforums.com/showpost.php?p=78542898&postcount=618
[Fire HD 8 and HD 10 Original Android Development] Phantasy0742:
1.1.2v is awesome! fix it!!! my device reboot twrp recovery

thanks for your help!
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
You say it was working fine before? Then why did you need to short it? If you have adb access, this script takes care of rebooting to bootrom for you.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
No where above or in the last few days did I say anything is "fine". I'm very much aware of what the script is supposed to take care of. Let me clarify: 8 out of 10 times the script runs, as soon as it errors, the tablet goes back to preloader within a few seconds thereafter. Sometimes it stays in bootrom. I just thought of this, but it sounds like the first one I bricked months ago where the PC would only recognize the tablet for 17 seconds before spitting out a convoluted error. I didn't count but I'll bet that's the same amount of time between when the gpt runs and the script lags out. What if when I tested the last rom build the script formatted the system partition something it shouldn't have been? Or any of the other ones.
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
[MENTION=8165603]DragonFire1024[/MENTION], in post 146, you said "The only thing it did was shut off after working fine." That's what I was referring to...

Anyway, if your tablet boots to the preloader, then you probably didn't damage your emmc. I suspect maybe your GPT got corrupted somehow and the script is not detecting a valid GPT. But it wouldn't be through flashing a ROM. The update installer does not resize any partitions. Maybe the script was writing the GPT at one point and your USB got disconnected. In this case, you have to somehow flash a new GPT from scratch. Maybe k4y0z could help you out by making a script for that.

The 17 sec. timeout period is probably related to the watchdog timer. The watchdog is the thing in hardware that reboots the device in case the software (CPU) stops responding. But that's pretty irrelevant.

The other tablet that you bricked by flashing a large file to the "unlock" space, you have to repair your boot2 region somehow. The script here won't be enough to unbrick it. I'd be interested to see what ended up in that region...
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
It isn't ADB as I have the latest versions for both Windows and Ubuntu, but I think I know what the problem is now. There is a "mkt-su" file in /data/local/tmp when I list the contents, but it must be corrupted because I can't remove, copy over or chmod it. I'll try to side load 5.3.6.4 and start over. Thank you for all the help.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I have also wondered what flashing that "unlock" put there too. !ore so because I'm curious as to why it passed anything in the first place. This is also the first time I've had anything go south without actually beating it up in some way. I'm used to knowing why and what i screwed up. So yes it was fine in the sense it was working normally under the circumstances.
[Fire HD 8 and HD 10 Original Android Development] RagManX:
I was in the same situation. I ran this method on that old FireOS. Once in TWRP, I installed the latest FireOS update. Then I installed Magisk through TWRP, rebooted, and installed Magisk Manager to re-establish root. Lastly, I followed this thread to re-install Google Play and now can use my tablet more like what I wanted it to be.
[Fire HD 8 and HD 10 Original Android Development] _ck_:
OH I see another problem here that is silent.

When you manually root the device because MTK-SU no longer works on 5.7.0.0 and install SuperSU

the scripts use "adb shell su"

except SuperSU free version doesn't support that

if you look at the SuperSu logs, the scripts are failing even though the device is rooted

"supersu pro is required" (for ADB SHELL SU)

Have to research that one and how the few people got around it.

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

You know what is strange is I can seem to do "adb shell su -c ls" from Windows CMD box to the tablet but I cannot do it from a Ubuntu virtual window without it stalling

I can do "adb shell" and then "su" separately from Ubuntu but SuperSU doesn't seem to like "adb shell su" even when you do the "pseudo pro version" activation

I'll have to try doing the step-1 brick process by hand or from Windows
[Fire HD 8 and HD 10 Original Android Development] _ck_:
SUCCESS!!!!

5.7.0.0 boot into TWRP !!!

Had to do it piece by piece reading the scripts meant for linux and just do it via Windows/CMD adb instead

Tips for the next people struggling, it is going to take much longer than just running a script for a minute so set aside an hour and don't be afraid to come back to it a little at a time each day, you can do it with patience.

Basically what I had to change:

1. FIRST you must root manually using the offline method, forget any other rooting method, secure the root with SuperSU free version

The reason why you must root is because you cannot BRICK the device without root. It is physically impossible to write to the protected partitions and wipe them out.

2. I had to go through the step-1 script by hand manually through Windows/DOS "adb shell su"

I do not understand why but it refused to work properly under a virtual Ubuntu window, adb shell su did not have the proper permissions so the brick partition copy overwrite would fail. Only the Windows/CMD "adb shell su" worked. This may be because of limitations in the free version of SuperSU even when pseudo-paid features activated.

3. Once you wipe it out and reboot, the tablet will appear bricked. It is not. The HD10 specifically is almost impossible to hard-brick. Once you wipe the paritions out, the way you get back control is to HOLD DOWN POWER BUTTON 10+ SECONDS. I never let it go, keep holding even after "bootrom-step-minimal" begins to run. I did run that one script under Ubuntu because I didn't want to setup python3 on Windows. It worked fine. Keep holding that power button down until it reboots after bootrom finishes unless someone knows otherwise.

4. Then you will see the very very tiny print "HACKED FASTBOOT" on the bottom left. But Windows did not understand the proper device driver to use for the hacked fastboot mode. I had to go manually into Device Manager, select the [x] Android device and force it to install the Google adb driver (version 11)

Once I did that driver update, I could see the fastboot mode via "fastboot devices"

Then manually going through "fastboot-step.sh" through the Windows/CMD worked perfect, sent twrp.img over just fine and rebooted into twrp recovery.

ps. The Fire HD10 2017 is often $25 on woot .com, go get some and enjoy this update, they go out of stock and then they come back "refurbished good condition"
[Fire HD 8 and HD 10 Original Android Development] Syco54645:
Can you please link to an updated offline root method? I am unable to find any that have the files still available.

Edit: found one that worked but now I have the bricked device and bootrom-step-minimal.sh is hanging or crashing at various portions. Currently it is sitting at Clear preloader header. Sometimes it does not make it past the "remove the short and press enter". A lot of times it hangs at Check GPT. I just tried it again and it hang at "Check boot 0" with a read fail error. Tried again just now and it crashed out at "Init Crypto Engine".
[Fire HD 8 and HD 10 Original Android Development] digixmax:
FWIW this post by @smartypantsuk is the only write-up I found that covers an alternate rooting method, and is very well written. I have not rooted by HD10 but would likely use this method in the absence of any more info.
[Fire HD 8 and HD 10 Original Android Development] Syco54645:
I ended up getting it working, just had to rerun the bootrom-step-minimal.sh multiple times and do different combinations of plugging and unplugging.
[Fire HD 8 and HD 10 Original Android Development] digixmax:
Now that you succeeded, can you confirm my understanding of the sequence of relevant steps prescribed in the OP:

Root the device using some offline method

Run "sudo ./step-1.sh"

Run "sudo ./brick.sh"

Run "sudo ./bootrom-step-minimal.sh"

TIA.
[Fire HD 8 and HD 10 Original Android Development] Syco54645:
Yes that is all that I had to do. The last step took multiple tries. Sometimes holding the power button allowed it to get further. But it would just crap out. Not really sure what was going on there. It eventually just worked. I restored a twrp backup from another Kindle and fixed the SD permissions. Been working fine now.
[Fire HD 8 and HD 10 Original Android Development] digixmax:
In reading the innard of the OP's shell scripts, it looks like the "bricking" if chosen when prompted by the step-1.sh script would get executed as part of step-1.sh script itself, so the brick.sh script (which I had thought needed as step #3 in my previous post) would not apply. So, the sequence of relevant steps seems to be:

Root the device using some offline method

Run "sudo ./step-1.sh" & select "Yes" for bricking

Run "sudo ./bootrom-step-minimal.sh"

Run "sudo ./fastboot-step.sh"
[Fire HD 8 and HD 10 Original Android Development] targa:
Worked for me as well, followed a modified "offline rooting guide" and it worked to the book (one of 2 download links worked for sure):

3ch01c.github.io/docs/how-to-setup-amazon-fire-hd10.md at master · 3ch01c/3ch01c.github.io

Tools and guides for doing software development, data analytics, online privacy, and other things. - 3ch01c/3ch01c.github.io

github.com

Now how do I flash Lineage... just via TWRP?
[Fire HD 8 and HD 10 Original Android Development] digixmax:
Yes, put the LineageOS build to your internal storage or SD card then do TWRP "Wipe /system & /data" followed by "Install".
[Fire HD 8 and HD 10 Original Android Development] targa:
Ah, I think I missed to wipe /system (it's not needed with mo

st other devices as it will be overwritten anyay during flash.)

Works now, what is the best Gapps to install ?! arm or arm64 ?
[Fire HD 8 and HD 10 Original Android Development] Icetech3:
A buddy just gave me his Suez to replace my extremely old 10, it's on fireos 5.7.0.0, does this method work with it? if not does anyone know one that does? I did try this a few mins ago and it gave me a "will not work on this firmware" error in linux. So.. i think that answers that part :) thanks guys.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
It will work fine, but you need to root it first via offline root method...

Another method is to open the tablet up and short a special point to ground, while using the scripts from OP (see the second post for details).
[Fire HD 8 and HD 10 Original Android Development] Icetech3:
Thanks much, will do some more research :)
[Fire HD 8 and HD 10 Original Android Development] digixmax:
FWIW -- I recently successfully used the rooting method in this post to root my 2017 HD10 (running FW v5.7.0.0).
[Fire HD 8 and HD 10 Original Android Development] pixatintes:
Hi guys,

I used this fantastic method, and all fine BUT after I used the main post script (step1.sh) to install TWRP, and now I have a beautiful black screen brick.

No connection to pc, and no VOLUME + POWER response..

Then I followed the Unbricking guide and it works.. but it is not the way.
[Fire HD 8 and HD 10 Original Android Development] digixmax:
Is this the Unbricking Guide you followed?

Did you end up having to crack open your HD?
[Fire HD 8 and HD 10 Original Android Development] djacu:
Hey all

I've successfully rooted and installed TWRP thanks to _ck_'s post and digixmax's post. I installed LineageOS from this thread, but cannot manage to install MindtheGapps. I saw this person had success but also installed Magisk. Is Magisk required? I tried installing Gapps using this guide but have had no success. Any advice?
[Fire HD 8 and HD 10 Original Android Development] psi78:
The problem with gapps is the small size of system partition on suez. You don't need magisk to install it.

There are 3 ways possible to do it anyway:

- Repartition as shown by @Kate6

- Debloat the system partition with my script suezcleanapp2.sh

--> See page 34 of the LOS16 thread for suez for both solutions:

https://xdaforums.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/page-34#post-87282103

- Alternatively - instead of opengapps or Mindthegapps - bitgapps or a small version of nikgapps can be installed because they have smaller file size
[Fire HD 8 and HD 10 Original Android Development] djacu:
Thanks for the help! I tried using your script but when I try to sideload MindtheGapps it doesn't show up. The strange thing is that it has never failed to install, but it still doesn't show up.

Here are my exact steps. Let me know if I've done something terribly wrong.

Connect the tablet to my PC with a cable.

Install ROM

On my PC, `adb push lineage-16.0-20220705-UNOFFICIAL-suez.zip /sdcard`

In TWRP, click Install, click the ROM, and swipe to flash.

Prep for clean script

After the ROM installs, in TWRP, go back to home page and click Mount and then click the checkbox for System.

On my PC, 'adb push suezcleanapp2.sh /sdcard`

Run the clean app script. I did have to modify it because it couldn't find `/bin/sh`... oh I just found it's in `/sbin/sh` for me. Doesn't matter; it still runs regardless.

`adb shell`

`cd /sdcard`

`chmod +x suezcleanapp2.sh`

`./suezcleanapp2.sh`

Side load Gapps

In TWRP, click Advanced, click ADB Sideload, swipe to start sideload.

On my PC, `adb sideload MindTheGapps-9.0.0-arm64-20180809_192137.zip`

It gets to about 50% and then finishes which I've read is normal. No errors.

But when I look in `/system/app` this is all I see.

~ # ls /system/app

Bluetooth LineageBlackTheme
BuiltInPrintService LineageDarkTheme
CaptivePortalLogin PacProcessor
CertInstaller PhotoTable
CompanionDeviceManager PrintRecommendationService
ExactCalculator PrintSpooler
ExtShared Profiles
KeyChain SecureElement
LatinIME bromite-webview
LineageBlackAccent
[Fire HD 8 and HD 10 Original Android Development] psi78:
I think Mindthegapps installs to another diretory like /system/ext (don't remember exactly🤔).

What happens when you boot, is Playstore there?
[Fire HD 8 and HD 10 Original Android Development] djacu:
Hmm there doesn't seem to be a /system/ext directory.

~ # ls /system/
addon.d fake-libs64 priv-app
app fonts product
bin framework recovery-from-boot.p
build.prop lib usr
compatibility_matrix.xml lib64 vendor
etc lost+found xbin
fake-libs media

I was able to sideload BiTGApps using BiTGApps-arm64-9.0.0-v1.8_signed.zip from the GitHub repo. Not sure what the difference is between BiTGApps and MindtheGApps. I just was trying MindtheGapps because that is what most people referenced on here.
[Fire HD 8 and HD 10 Original Android Development] psi78:
I guess Bitgapps has some extra features (see here: https://bitgapps.github.io/docs/Features.html - like sideloading...) whereas Mindthegapps is a redistribution of gapps which also integrates its gapps Setup wizard with the LineageOS setup wizard stuff (after first boot) seamlessly.

Instead of sideloading Mindthegapp you could also try to test if installing via TWRP works, see current post in suez LOS16 thread