yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] h0va4life:
FYI I have the latest updated hd10 7th gen and neither of those root options seemed to have worked. kingroot on PC says that a root strategy hasn't been developed and kingoroot gets hung up at 78% where it seems to be checking the root status.

---------- Post added at 11:40 PM ---------- Previous post was at 10:52 PM ----------

Hi Kevin, thank you for your guide. Curious, is this done in all in windows cmd? Or do I still need to have a VM running Ubuntu?
[Fire HD 8 and HD 10 Original Android Development] epeace:
Thanks for responding :) I should mention that I am doing this on a mac (which is running on FreeBSD right?), and the stock Python in MacOS is 2.7 which is probably why I'm getting that (only learning this now as I scramble for answers). There seems to be 2 pythons on my system, and the installs were defaulting to the os version. To use python 3 i have to use the command 'python3' instead of 'python'. Having learned that I went ahead and updated pip and wheel and whatnot using python3 and it was successful. I then installed pyserial again using the updated tools. So I am running the latest pyserial, the scripts ran properly, and I'm all booted into TWRP. All is swell. Thanks for the guidance!
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Don't use a VM...

The scripts for this still need linux.

From the OP

What you need:

A Linux installation or live-system
[Fire HD 8 and HD 10 Original Android Development] h0va4life:
Ok, he also mentioned something about ubuntu as well. How do i run both windows and linux at same time without VM?

Its been a while since i last tried rooting/custom roms on android, used to the days of just using ?fastboot? and im not familiar with navigating the python/linux worlds, i can do windows cmd. Any help or lead to a good guide on running these scripts while still having windows up, if possible, would be greatly appreciated.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Download and make a live disk. Boot from the usb...

https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started

Fastboot is still used, but you have to unlock it to have access to anything usuable in fastboot (it is called the hacked fastboot here)

The scripts are all written for python, you dont have to do anything but run the scripts that are already there.

It isn't that hard, i am a windows person myself and never use linux. The terminal is close to that on a cmd prompt. If you get lost or confused post a question, most people will assist. Just read the whole directions a couple times and the first page of comments.
[Fire HD 8 and HD 10 Original Android Development] h0va4life:
Ok I see! What really helped, just to let you know how much of a noob I am, I didn't realize that python came with the linux, I thought i had to download via their website. I am in the process of opening my fire HD and doing the shorting method since I have the latest version, per the guides I see that the latest updated version of fire hd 10 is not covered.
[Fire HD 8 and HD 10 Original Android Development] jchangarirang:
Where do I short the pin?

I tried searching the tread, and could not find easy description of location of two pin I have to short.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Post #1102 has directions of a recent success
[Fire HD 8 and HD 10 Original Android Development] h0va4life:
Thank you very much! I was able to flash TWRP after successfully shorting after stripping an old micro USB. I kept getting serial protocol issues but disabled per the forum explaining detail for the short method.

I am having an issue now with getting back to TWRP. I did the wipe/factory reset and by the time I got back to my tablet, the system booted into FireOS. I thought that was going to be wiped? How do I get back to TWRP?

Also do I need the magikmanager as well for later on?

---------- Post added at 03:52 PM ---------- Previous post was at 03:44 PM ----------

Sorry I remember how to get into recovery mode, it's all coming back to me, sort of!

But what is the magikmanager for? If you wouldn't mind helping understand. I thought I was already rooted after doing all the steps.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
The process unlocks you allowing access to root and installing custom recovery (TWRP) - Magisk controls that access...

adb reboot bootloader

or

power off completely, then HOLD VOLUME DOWN and POWER ~5seconds it will boot into recovery.

If you flash anything or need root access you need magisk. Magisk is a superuser manager. You don't "need" it, but it will come in useful when needed. I use it on all my devices and every rom that supports it.
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Sorry for the late reply, i do not get any notifications from here for some reason. My tablet was bricked at that point (would not power on at all), so... turned off
[Fire HD 8 and HD 10 Original Android Development] h0va4life:
Go to this thread: https://xdaforums.com/hd8...lback-t3896616

And refer to the picture attached to the main post; the OP highlights the pin required with a blue dot, thats the pin that you need to connect to, it isnt too far from the white square printed on the board.

You can also check out this youttube I found that also shows the location (albiet on a fire hd 7) - https://www.youtube.com/watch?v=Ol4DiDLbClE

I successfully shorted and flashed twrp recovery. I stripped an old mini usb cable for the short.
[Fire HD 8 and HD 10 Original Android Development] h0va4life:
Anybody get pixel launcher to work? I installed the nano or whatever small gapps and then sideloaded the launcher but it keeps stopping after installing and when setting it as my launcher.
[Fire HD 8 and HD 10 Original Android Development] kevin71246:
I strongly recommend in investing in a raspberry pi (3 or 4). Install raspbian on it, and use it for all things hobby, including using it to do Linux commands for flashing ROMs or rooting, like in this guide. That's what I used: connected my raspberry pi USB to my fire tablet, sshd into pi from my windows laptop & ran the commands. The pi also does other things for me unrelated to the guide, multipurpose.
[Fire HD 8 and HD 10 Original Android Development] trancer03:
Does not work!

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

Failed critical init step 4

^C

Stuck on error!!!
[Fire HD 8 and HD 10 Original Android Development] playadru182:
Same error for me, not sure what's wrong. Tablet version is Fire OS 5.6.6.0 (654620420)

Here's the steps I took

1. Running Ubuntu 18.04.4 LTS via Live-USB

2. Followed all steps through #3 (start the step-1.sh script), got the same error.

Any ideas where to troubleshoot?
[Fire HD 8 and HD 10 Original Android Development] DB126:
Read (search) thread; likely related to patched FireOS build.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Are you trying to do the software unlock?

Fire HD 10 7th gen (2017) (thanks bibikalka) -- up to Fire OS 5.6.4.0 build 636558520 only

Anything updated needs to do the hardware unlock. See post #1102 here...

https://xdaforums.com/hd8-hd10/orig...-2017-suez-t3913639/post82274609#post82274609

---------- Post added at 07:33 AM ---------- Previous post was at 07:30 AM ----------

Apparently reading and/or searching is non-essential.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Hey 'bro'; don't tread on my entitlements! Why bother reading when someone else will do the heavy lifting. Rock on XDA welfare! You dudes are AWESOME until you're not ... :rolleyes:
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Does anyone know if this unlock method will work on the new editions of the hd10 specifically the 2019 or 2020 ones (9th gen?)?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Hi there,

If you mean the HD10 2019 (codemaned maverick) it will not work.

Regards.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Root is available if you get the original ones.

Fire HD 10 9th gen (2019) -- up to Fire OS 7.3.1.0 only

I have one rooted and (2) on 7.3.1.1 but has app blocking available...
[Fire HD 8 and HD 10 Original Android Development] RjGunner111:
rooting

i see that i need root in order to do this, what if i use kingroot to do this?
[Fire HD 8 and HD 10 Original Android Development] powaaah:
I use version 5.3.7.0 (650601220)

and i see also "Failed critical init step 4"
[Fire HD 8 and HD 10 Original Android Development] Michajin:
You need to do the hardware unlock. 5.3.7.0 is actually newer than Fire OS 5.6.4.0 . Amazon changed the OS numbering scheme... You dont have root access....

---------- Post added at 02:03 PM ---------- Previous post was at 02:00 PM ----------

kingroot doesnt work on this. You don't need root to do this if you aren't afraid of opening the device up. As for root possibilities, that would depend on the FireOS version you are on...
[Fire HD 8 and HD 10 Original Android Development] BrainlessDude:
Hey guys. I ran the script but it is failing at the GPT check.

I cant seem to find a solution.
[Fire HD 8 and HD 10 Original Android Development] mpontoriero:
Hi, sorry to bother you, i have an Amazon Fire HD 10 7th generation. I dont know what happened, but it wont boot, its in a boot loop on the amazon logo and when i try to enter recovery mode, the amazon logo appears and down on the left it says Recovery Mode and stays like that, it dont give me the recovery options, so what should i do, to fix this? Thank you!
[Fire HD 8 and HD 10 Original Android Development] kgonepostl:
How do I brick it, that's not in the guide. I can't find out how to brick it, since my amazon firmware is currently 5.3.7.0. Help!! :-0
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Run the brick script... But if you dont have root, i think you have to run open the device and do the shorting method anyhow. 5.3.7.0 does not allow MTK-SU to work...

---------- Post added at 04:52 PM ---------- Previous post was at 04:49 PM ----------

I think you have to hit both volume up and down at the same time to to get into the stock recovery menu when you are the recovery screen. This thread is for unlocking and install TWRP custom recovery. You should be able to do a factory reset from there. What were you doing that caused the boot loop?
[Fire HD 8 and HD 10 Original Android Development] mpontoriero:
I was in twrp , and i didnt have fireos installed, so no operative system. And i flashed a boot.img. And after that it restarted, and bootloop, and when i press volume down, it appear recovery mode on the bottom, but it stays there, i cant enter the recovery mode options. Thank you for the reply
[Fire HD 8 and HD 10 Original Android Development] Michajin:
What process did you flash a boot image, and what boot image did you flash? You may have to find a way to get into fastboot and flash recovery. I think you have to open the device and short it?
[Fire HD 8 and HD 10 Original Android Development] DB126:
FWIW - assuming one can get to fastboot and the bootloader is unlocked (or otherwise vulnerable) simply boot a device specific TWRP image vs flashing. Much easier and a whole lot safer.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Agreed. He had TWRP installed before, so he is unlocked. He flashed a boot.img and now TWRP will not boot. He could flash recovery from twrp also. I am curious what boot.img he flashed to cause this...
[Fire HD 8 and HD 10 Original Android Development] DB126:
Message suggests device is having difficulty launching whatever is in the recovery partition. Contents may be intact. Saw this on older (5th gen) Ford devices borked by FkashFire. In those days bootloader remained locked (no extended fastboot command set); inability to access recovery was usually a death sentence if the ROM also failed to boot.
[Fire HD 8 and HD 10 Original Android Development] HagardoVesrozy98:
Can the whole guide be done on Windows without using VM or flashboot Linux via USB?

I have no background in coding btw in case I've done something wrong so I had to ask.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
No it can't be, A live disk is easy, no coding is needed. It will be alot easier if you have access to root (otherwise you have to do a shorting method, whick requires opening the device). What fireOS are you on?

Download a live disk and burn it to a USB and boot from the USB. Linux terminal is very similar to cmd prompt. I have no formal training and got through it fairly easy. The hard work is already written in the scripts you run. Mainly bootrom-step (sets the unlock and exploit) and fastboot-step (flashes TWRP recovery) are the on thing you you have to do.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
I tried to unlock Fire 10HD 7th gen with FireOS 5.6.6.0

mtk-su r2.2 got stuck when it was invoked in step-1.sh.

It gave these messages:

Is there any alternative to mtk-su?
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
To answer my own post, as a working alternative to mtk-su which did not work on the Fire 10HD 7th gen with FireOS 5.6.6.0, I installed the Kingo Root apk to root the device with success. Others may try it.

---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------

Here are the details how I unlock my 10HD.

I denote Step 3 of OP as #3 and break it down into substeps #3A, #3B, #3C etc below for the scenario when soft bricking the device is a necessity:

#3A

sudo ./step-1.sh

Answer "YES" to brick

#3B

software bricking happened (screen does not come on)

disconnecting from usb cable

#3C

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

#3D

sudo ./bootrom-step-minimal.sh

re-connecting to usb cable

#3E

the screen of the Fire device comes back to life and the device boots into fastboot mode (i.e. waiting for the next command in #3F below)

Note: If Fire screen does not come back to life and "sudo ./bootrom-step-minimal.sh" is still waiting for the device to respond, do not panick. (a) Type "<control>Z" on your Linux computer to terminate the bootrom-step-minimal.sh command. (b) Disconnect the Fire device from the usb cable. (c)Press the Fire power button for 20 seconds. (d) THEN repeat from Step #3D above again

#3F

sudo ./fastboot-step.sh <===

this command flashes TWRP and then boots the Fire device into TWRP if all goes well

NOTE - As the device has gone through soft bricking, Step 4 of OP can be skipped.

The above was the sequence I used, as far as I can remember it.

Good luck!
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
My Fire HD 10 (2017 suez) is 5.6.6.0. I tried using Kingoroot, and now the tablet is always stuck at "Fire" logo screen (after the white Amazon logo).

I tried following the steps - disable ModemManager, turn off the tablet (long press 20 seconds), then "sudo ./bootrom-step-minimal.sh".

Then I plug in the USB cable, but there is "serial protocol mismatch" error. Please see screenshot below. I made sure USB cable is connected to the PC directly (and not through USB hub).

So what should I do now? How can I rescue my Fire HD 10 now that it is forever stuck in the "fire" screen. Your help will be greatly greatly appreciated.

Next post includes the embedded image. Sorry for double-posting, as I cannot delete my own post.
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
My Fire HD 10 (2017 suez) is 5.6.6.0. I tried using Kingoroot, and now the tablet is always stuck at "Fire" logo screen (after the white Amazon logo).

I tried following the steps - disable ModemManager, turn off the tablet (long press 20 seconds), then "sudo ./bootrom-step-minimal.sh".

Then I plug in the USB cable, but there is "serial protocol mismatch" error. Please see screenshot below. I made sure USB cable is connected to the PC directly (and not through USB hub).

So what should I do now? How can I rescue my Fire HD 10 now that it is forever stuck in the "fire" screen. Your help will be greatly greatly appreciated.
[Fire HD 8 and HD 10 Original Android Development] toybits:
Hi. I also have fire hd 10 2017 model with 5.6.6.0 the latest one. Can I start with kingo root right away rather than trying mtk-su? If i do the kingo root should it boot back normal to the OS? Then execute your step 3#'s. Im afraid to kingo root it as the above post says that he was stuck in the fire logo. Please help as i want to install twrp and lineage os. Thanks in advance.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
1. Install Kingo Root apk on the device under FireOS 5.6.6.0

2. Run the app and it stopped at 90%.

3. Come out by tapping home page.

4. Run the app again - it will show the device is rooted.

NOTE: Your device is rooted and is still running FireOS 5.6.6.0. DO NOT reboot the device. Someone says his device hung and could not start up again. I did not reboot after rooting and thus cannot verifiy.

5. Now following the steps in the OP to unlock bootloader and install TWRP.

NOTE: You can skip mtk-su in the OP. mtk-su will not be used at all as your device is already rooted.

I have unlocked successfully two Fire 10HD with FireOS 5.6.6.0 using the above method. Both done successfully and are now running Lineage OS 12.1. Other versions of FireOS may have different results, which I cannot tell.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
Did you run "sudo ./step-1.sh" at the Fire logo screen? Your screenshot show you didn't do it. Run it, if it works the tablet would go into soft brick. Just follow the #3A, #3B etc. If #3A doesn't work, you have to do "adb sideload" (in windows with manually installed driver) of a stock ROM to fix the Kingoroot app problem.

Once your tablet is sideloaded with stock ROM, remove Kingoroot app immediately if you want to keep using stock ROM. Only use Kingoroot temporarily in place of mtk-su in order to unlock the bootloader, install TWRP and flash a clean ROM like LOS or a modded ROM.
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
Hi, so i followed your advice and tried "sudo ./step-1.sh" at the Fire logo screen. And there is an MTP error. Please see picture attached. On the left is my HD 10 which is forever at the Fire logo screen.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
It may be possible to try "sudo ./step-1.sh" again after booting into recovery mode, but I'm not sure any harm will happen or even if it'd work.

If you don't want to try that, you still need to boot into recovery mode anyways in order to run adb sideload of a stock ROM to fix the kingoroot bootloop. Boot into recovery mode, select "apply update from ADB", plug USB cable in Windows, manually update device driver to "Android Composite ADB Interface" then run adb sideload of the stock rom you can download from Amazon.
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
Yes. That helps. I downloaded stock rom 5.6.60 from Amazon, booted the device into Amazon recovery. And then use adb sideload to restore the stock rom. Now the tablet is able to boot into FireOS successfully.

Thank you very much!

I guess it is now back to the OP to start all over again my root attempt.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
Glad it works out!

The mtk-su temp root in OP's instruction doesn't work on 5.6.6.0 so you can follow drdtyc's steps in post #1152 and #1148. Also have LOS or modded ROM ready to flash right away once you've successfully unlocked and boot into TWRP, or else you'd see the Fire screen bootloop again.
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
i followed drdtyc's steps in post #1152 and #1148 exactly, and came to the screen of TWRP. but installation of Magisk wasn't successful.

So I rebooted into TWRP again, and trying to install Magisk. This time installation is OK. But after that boot loop again -"fire" logo on the screen.

now i am using TWRP to sideload stock rom again.

So u mean after the first boot into TWRP. i should flash Magisk immediately? I don't intend to flash other OS. As long as the stock-one is rooted, I am OK.
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
TWRP + stock ROM strange behaviour

i think something is horribly wrong. now my suez has TWRP and always boot loop at "fire" logo. i could boot into TWRP, then select adb sideload, and flash back stock rom.

Now i use Kingoroot, followed [MENTION=10542541]drdtyc[/MENTION] steps, and do "sudo ./step-1.sh". i receive the following error (see screen shot).

So how can I root the device again?
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
I don't know if 5.6.6.0 can be rooted yet. Also don't think stock rom will work with a modified bootloader which you've just done with this process. That's why I mentioned LOS or a modded rom (I've never mentioned Magisk). If you don't want LOS, you'd have to flash a version of Fire OS that's already been modded.

Let me know if stock rom works after you flash it with TWRP. If it works, try flashing Magisk then. I don't know if anyone has done that before.

---------- Post added at 04:43 AM ---------- Previous post was at 04:29 AM ----------

Ugh, you've been too quick to flash before even knowing what works or what doesn't work. Slow down a bit and check what recovery is on your device now: stock or TWRP?
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
Now i have TWRP recovery on my device. The reason that I tried Magisk is because the OP says so (after TWRP).

Any advice that you may have now regarding my situation now?

Your help is greatly appreciated.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
The OP said flash Magisk because it would work with mtk-su, but you've used Kingoroot, not mtk-su.

Anyways, you've already got TWRP and don't need Kingoroot or the whole process again (unless you restore everything back to stock including the bootloader). Can you boot normally into Fire OS now?
[Fire HD 8 and HD 10 Original Android Development] mxj_xda:
In TWRP I can select and side load option, then after I successfully side load stock rom, I can successfully boot into fire is.

So my question is how to obtain root access? Does having TWRP mean I already have root access?
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
No root yet. Have you tried yet installing Magisk in TWRP after booting normally into Fire OS? I don't know if it would work though.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
You do not need Magisk to flash Lineage OS unless you want to root the device.

On my two Fire 10HD, I did not install Magisk and thus had not encountered your difficulties.

Try skipping magisk and see how it goes.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
He said he did not want LOS. He was able to boot into FireOS 5.6.6.0 without problem, so without root it's working fine for him. But he wanted root and tried to flash Magisk. From what he said it appeared he flashed Magisk right after unlocking the bootloader and installing TWRP meaning Kingoroot was still there and therefore a bootloop. Then he sideloaded stockrom again and ran Kingoroot again and got stuck because TWRP was still there - this was unnecessary.

For now as he got TWRP and FireOS 5.6.6.0 running fine, he could try flashing Magisk in TWRP, but he hasn't got back about that yet.