yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] kojam:
Again, a MILLION thanks!

I was thinking that perhaps ModemManager was the culprit to my problems. Realized it hadn't really been disabled using the commands from the guide. Tinkered with it and am certain now that it's been killed but same difference. I'm going to buy a T5 torx screwdriver set from a local hardware store today and do this tonight.

Regards!
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
https://xdaforums.com/showpost.php?p=80287339&postcount=154

See the last image of the above post. That is how shorting is done on a different model, 8HD 2017. Yours is 10HD 2017. Thus the point of shorting on the 10hd 2017 is different. But you will get the idea of what to do.
[Fire HD 8 and HD 10 Original Android Development] kojam:
Thanks dood!
[Fire HD 8 and HD 10 Original Android Development] kojam:
Wow!

All the vids I watched make it seem like it's so easy to disconnect the cables. I had the HARDEST time, and I've done this type of thing before on many devices. It's REALLY cheaply made. The I broke the biggest clip in 2 places as I tried ever so gingerly to remove it. It is like paper, not plastic. FINALLY got them off and had to turn in to bed. Got the black screws out, but the other ones won't budge an inch. Was tying to be sooooo careful once I realized how sub-par the parts are but one of the remaining screws stripped!!! WHT?!?!! I couln't get any of the non black screws out yet. They WILL NOT turn! I'm afraid of stripping them now. I may have to drill out the one that stripped, since the T5 screwdriver no longer works. Of all the things I've opened up to work on over the years....THIS ONE IS THE WORST!

Just had to rant. Sorry.
[Fire HD 8 and HD 10 Original Android Development] kojam:
Well, looks like this journey is over a quick as it began. CANNOT get those remaining screws out! Two are now slightly stripped, even though I was being as gentle as possible. Even Giga-lubed them all but cannot get them to turn. I recently used Giga-lube on some bolts which had completely rusted out and it worked beautifully. I will have to junk this piece of junk tablet and move on.
[Fire HD 8 and HD 10 Original Android Development] ryevick:
Rooting use to be sooo simple. :eek:
[Fire HD 8 and HD 10 Original Android Development] JA1985:
I can’t seem to get the script to work. Keeps giving me an error.

I downgraded my device to FireOS 5.3.7.2

I followed all steps and put the mtk-su file in the bin directory.

But when I run the step-1.sh script it keeps looping on the following error:

Failed critical init step 4

Functions.inc: line 15: /usr/bin/sleep: Input/output error

Does anyone have any ideas what i am doing wrong or how to fix this? My device is not rooted..
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
What exactly are you running there? amonet-suez-v1.1.2.zip does not contain a "Functions.inc" file.

(It does contain a "functions.inc" file, i.e. starting with a lower case "f". Case does matter on Linux.)

Wild guess: Do you happen to have a harddisk error / bad block on your Linux system affecting the

/usr/bin/sleep

binary so that the shell is unable to execute it?

Try running

/usr/bin/sleep 1

at a shell prompt, does it give you an "Input/output error", too? If so, run

dmesg

and have a look at the last few lines.
[Fire HD 8 and HD 10 Original Android Development] JA1985:
Sorry yes it was a lower case f

I was running Ubuntu latest version from live cd. So no install. Maybe that was issue?

But.. this all don’t matter now. I ended up accidentally bricking the tablet. I downgraded the OS to another amazon Os then the device would not switch on. That was after I wiped the user data and cache. So I had no way to switch it back on.

I have now smashed it up and put in the bin ha ha :)
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
Success with 5.6.4.0! Can/should I upgrade now to 5.6.6.0 or even 5.3.7.2?

Sorry to hear that it did not work out. Perhaps you were already heading down the wrong path when you flashed FireOS 5.3.7.2 because on https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595 it says "Note that for Fire OS 5, OS version 5.3.x.x is newer than 5.6.x.x." (does anybody know why?), meaning it probably was an upgrade rather than a downgrade and thus caused mtk-su to fail. That's apparently what the first line of your error message indicated.

I had this problem, too, but fortunately [MENTION=10542541]drdtyc[/MENTION] told us what to do:

This 20 sec power button press did it for me! Thank you so much [MENTION=10542541]drdtyc[/MENTION]!!! (FWIW I used CTRL-C instead of CTRL-Z to quit the shell script.)

So I successfully went through all this on my Fire HD 10 2017 running 5.6.4.0. Does anybody know whether it would be safe for me to adb sideload 5.6.6.0 or am I stuck with 5.6.4.0?

Is this is how you did it [MENTION=10147987]mxj_xda[/MENTION], you booted into TWRP, chose Advanced → ADB Sideload and then ran

adb sideload update-kindle-*.bin

from the PC, right?

The current version on https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE is FireOS 5.3.7.2, where do I download the 5.6.6.0 image? Or should I go for FireOS 5.3.7.2 now that this version is the latest?
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
:eek:
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
Success with 5.6.4.0! Can/should I upgrade now to 5.6.6.0 or even 5.3.7.2?

:eek::eek:
[Fire HD 8 and HD 10 Original Android Development] anon/droid:
Success with 5.6.4.0! Can/should I upgrade now to 5.6.6.0 or even 5.3.7.2?

:eek::eek::eek:
[Fire HD 8 and HD 10 Original Android Development] Cheesethief:
I've updated mine to FireOS 6, which is version 5.3.7.2. I also flashed Magisk right after to make sure I had root. Everything seems to work fine.
[Fire HD 8 and HD 10 Original Android Development] nola mike:
This worked brilliantly, thanks for saving me a bunch of time! For some reason I thought that this device required opening it up, shorting pins, etc. I've been kludging around with the godawful amazon OS, to the point where I thought I was going to have to dump this thing. Managed to install lineage 14.1 without problems after getting TWRP. [MENTION=7104332]k4y0z[/MENTION], any way to include this info in the OP? The mtk exploit doesn't work with newer OS versions, so it would be much easier to see an updated version...
[Fire HD 8 and HD 10 Original Android Development] LearnEnglish:
I want to try LOS14 but dont know how to downgrade from FOS 5.3.7.2 to the older firmware in oder to unlock bootloader. anyone have a solution please tell me how

sory for my bad english
[Fire HD 8 and HD 10 Original Android Development] Marleybop:
Fire HD 10 2017 Running FireOS 5.6.6.0 - Bootloader Unlocker Possible?

Hello, I'm wondering is it still possible to unlock the bootloader for this device. I've tried a few different ways, including the brick method but with no luck.

Thanks in advance! :)
[Fire HD 8 and HD 10 Original Android Development] karldonteljames:
Evening All,

I've read through a number of pages here and I'm slightly confused.

I have two Amazon Fire HD 10 (7th Gen) tablets that i would like to install linageOS 12.1 (due to the fact that the camera doesn't work in 14.1)

I've tried following the instructions here: https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639

I am running Firmware 5.6.6.0, so when i try and run the brick script it completes with a failed error message and the tablet just reboots as if nothing happened. I understand that there was some talk about updating the brick.sh file or the brick.img file, but i'm unsure if that has been done, I'm a little lost in the 128 pages.

I'm not confident in opening the device, but am happy to try and flash them with general guidance using Ubuntu. - Any help here would be really appreciated. - Many thanks.

So i think I've cracked it, I'll make this a little more readable asap.

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.

#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

At this point i had to hold the power button for 20 seconds. and a message came up asking me to press enter after removng the short (no short was applied, so just press enter)

anther message came up asking if i had bricked the device, press enter. at this point it began injecting the payload.

Once the payload had been injected, i removed the usb cable and pressed and held the power button for about twenty seconds. at which point it booted to the hacked bootloader.

#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

once in the TWRP screen:

i went to wipe and format data, typed yes and formatted the device.

then select advanced> ADB sideloadand swipe to start sideload.

ran the command:

adb sideload lineage121.zip

at this point, i selected reboot system, and was up and running in linage 12.1!
[Fire HD 8 and HD 10 Original Android Development] walkingevildead:
What a pain in the butt. Been messing with this for almost 6 hours and still can not get it right. I can get it to root than nothing further. Reboot and it's unrooted again. Any body now of an automated way??
[Fire HD 8 and HD 10 Original Android Development] Marleybop:
I had thought about trying it all with King root. I can confirm that this works perfectly, took me about 10 minutes You are amazing sir, much obliged! :good:

Just to add - I thought the instructions were super easy to follow!
[Fire HD 8 and HD 10 Original Android Development] quess41:
help please with my mistake

I have a kindle fire hd 10 7th gen 2017

I used kingo root to root it. It worked fine and completed root. so I was using amonet-suez to install TWRP

here is where i made the mistake.

i run the following commends:

Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:

Code:

sudo apt update

sudo add-apt-repository universe

sudo apt install python3 python3-serial adb fastboot dos2unix

1. Extract the attached zip-file "amonet-suez-v1.1.2.zip" and open a terminal in that directory.

NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by [MENTION=8132642]diplomatic[/MENTION] from here and place (the unpacked binary) into amonet/bin folder

I was rooted with kingo, so I moved to next step

2. Enable ADB in Developer Settings

3. Start the script:

Code:

sudo ./step-1.sh

Your device will now reboot into recovery and perform a factory reset.

I don't think it performed a factort reset before i moved to next step?

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)

If you chose the brick option, you don't need to run step-2.sh below:

my firmware was 5.3.x.x so I moved to the next step

Make sure ModemManager is disabled or uninstalled:

Code:

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

After you have confirmed the bricking by typing "YES", you will need disconnect the device and run

I DID NOT DISCONNECT THE DEVICES before I run the next code

Code:

sudo ./bootrom-step-minimal.sh

Then plug the device back in.

It will then boot into "hacked fastboot" mode.

It never show any on the screen, so I run the next code anyway

Then run

Code:

sudo ./fastboot-step.sh

so I don't know what to do. i have tried power and volume buttons, nothing

now it has black screen and when plug in to the computer, it is cycling the prompt sound.

It sounds up then about 23 seconds then sounds down about 39 seconds, then just repeats,

thanks for any help possible,

(yes, i'm new at rooting, I was a jailbreaker back in the day)
[Fire HD 8 and HD 10 Original Android Development] PixelCOwner:
5.6.7.0 (657612420)

I'm on 5.6.7.0 (657612420)...is it still possible to root/load TWRP? I tried the steps in the original post but mtk-su doesn't support this firmware version.
[Fire HD 8 and HD 10 Original Android Development] Marleybop:
Try this splendid fellows post. Worked for me on 5.6.6
[Fire HD 8 and HD 10 Original Android Development] PixelCOwner:
This worked for me on 5.6.7.0 (657612420)
[Fire HD 8 and HD 10 Original Android Development] Marleybop:
Brilliant to know. Don't forget to give the guy a thumbs up, he helped us out a lot!
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
He just copied posts 1148 and 1152 by [MENTION=10542541]drdtyc[/MENTION] without thanking or quoting him.
[Fire HD 8 and HD 10 Original Android Development] dasstig:
Mine gets stuck at 29% in Kingo ROOT. I try doing "sudo ./bootrom-step-minimal.sh" and nothing happens.

Kingo ROOT supersu says "Have Root" in green.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
Follow the Note in step #3E in post 1148:

"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"
[Fire HD 8 and HD 10 Original Android Development] MeisterGigi:
Hi,

today i decided to root my Kindle, is this still only possible with linux? no adb or something else? I am not a Linux Crack ^^ I learned it years ago and forgot 99%

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

Hi,

today i decided to root my Kindle, is this still only possible with linux? no adb or something else? I am not a Linux Crack ^^ I learned it years ago and forgot 99%
[Fire HD 8 and HD 10 Original Android Development] Michajin:
yes, still possible. Just follow the commands, make a live disk of ubuntu or your flavor, then run the commands. You don't have to be good with linux or know anything about it to really do this. just open a terminal and follow the steps (every step)
[Fire HD 8 and HD 10 Original Android Development] wjbartlett82:
sudo ./step-1.sh "command not found"

I am having the ' sudo ./step-1.sh "command not found" ' Problem as ive seen in these threads, what exactly can i do to fix this error??
[Fire HD 8 and HD 10 Original Android Development] MeisterGigi:
Tried it, but i got some errors

- Software Brick did not happen

-sudo ./bootrom-step-minimal.sh gave me some errors (error in line...) Unfortunately i saved the log on the ubuntu live stick, then i came back to windows just to realize the saved file is gone ^^

Now my Kindle stucks at the "Fire" , it is possible to go into recovery (see image)

Question:

What to do now, should i try it again to get you the error? I made everything step by step ...
[Fire HD 8 and HD 10 Original Android Development] Parafly:
So, I am replacin gmy daughter's fire hd10 with a new one. Got through all the OP steps just fine and i can get into TWRP. I installed Magisk also via adb. However, I can't get into the OS now, it just keeps boot looping. I'm not sure what version of the OS I am on , I think it said 5.4.something (it was an old one). What do I do next?
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I'm on Fire OS 5.6.7.0 and I could not get anything here to work:

* Kingoroot (either installed .apk or from Win10 PC) says it fails to root

* running step-1.sh just generates error "Failed critical init step4" and "This firmware cannot be supported"

* bootrom-step-minimal.sh generates Python errors

* I can put the Fire HD 10 into Bootloader mode (power Key + volume up) and run brick.sh which 'says' its writing the image and the bootloader screen shows its received, but then it errors out saying "FAILED (status read failed (no such device))" and the tablet reboots back to normal Fire OS 5.6.7.0

So unless someone knows differently, i'm assuming this root/unlock process does not work for Fire OS 5.6.7.0 ??
[Fire HD 8 and HD 10 Original Android Development] Sebaherrer:
Thanks you very much!.

working on fireos 5.6.7.0 Hd10 (7th gen) with this method. i used linux mint (already installed in my laptop) and works without problem at all.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
I also used Linux & followed the instructions you referred to, and could not get my Fire HD 10 on 5.6.7.0 to root or unlock bootloader or brick or anything.

How did you get Kingoroot to work? It just fails at 7% on my Fire HD (tried .apk & Win10 version). Where did you download Kingoroot from?
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
You're nearly there chief - I did a couple of Fire HD 10s a couple of months ago on the sneakily numbered 5.6.7.0 FireOS update and had to fiddle a bit with combining instructions to get it working smoothly. If I remember correctly you want to do this:

1: use the matrix exploit from the other thread you posted in to get initial temporary root

2: pick up with the instructions from here before you reboot and lose root

After that I chose to flash Magisk through TWRP to maintain root on FireOS but you can also just nuke it completely at that point and install lineageos.

There's a summary post just above which is a bit all over the place but does provide some handy hints if you get stuck - the actual process is cleaner than that, and less confused (if you do it properly).
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Well Sir - you have been tremendously helpful! I followed your advice and the instructions in the two 'rooting' threads & it actually worked! I'm now using LineageOS 12 on my Fire HD 10 (which had been on Fire OS 5.6.7.0).

The process was a bit 'hairy' and required a few 'adjustments' as I grappled my way through (including discovering that Fastboot wasn't installed on my Ubuntu laptop), but I got there in the end. The cleverness of the developers on XDA never ceases to amaze me.

Thanks for your help.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Ah - I hadn't realised that on 'standard' Android (eg. LineageOS) that Alexa (or Google) hotword detection with screen OFF simply doesn't work (and most attempted workarounds seem to flop).

Is it possible to revert back to FireOS (to get Alexa working) but WITHOUT losing TWRP or certainly not SU root access? (with root I can disable other assorted Amazon bloatware just leaving Alexa working).
[Fire HD 8 and HD 10 Original Android Development] smithbill:
In that thread you referred to, it says "remove the preloader, tz and lk flash lines in updater-script" - did you do this? Exactly what lines do you remove?

I want to return to stock FireOS (to get a properly working hands free Alexa) but I dont want to lose my current root access & TWRP.
[Fire HD 8 and HD 10 Original Android Development] chairmanmiaow:
Short answer is yes, long answer is slightly more complicated. Please remember that I did this 3 or 4 months back, didn't keep notes and have done countless other jobs since then so you'd want to do your best to double check what I say...

I prefer lineageos on these tablets but there are a lot of compromises to be made that won't suit a lot of users - no camera, headphone jack, gfx acceleration, 1080p video playback is borked, DRM videos won't play, the lineageos version is ancient, buggy and full of security holes. Basically it sucks unless you just want an ultra minimalist handy tablet to run dev tools and terminals, kodi remotes, etc. Which happens to be exactly what I want. For 'normal' users forget it, lineageos is dead on these tablets unfortunately. So for the last two I did a while back I did indeed have to revert them from fully modified back to stock just so the end users wouldn't throw them in the bin. It was confusing and as usual the XDA sources were contradictory and unclear.

So, if I remember rightly, I didn't revert either of them fully back to stock although I have done before - you definitely need the "back to stock" instructions in the first post for that to restore the original partition layout. To finally answer your actual question, in your position you need to:

1: download the same version of the stock firmware you had installed on it pre-hack if possible. don't muck around with trying to find old pre 5.6.whatever versions, big downgrades between stock firmwares can brick it. because the established Matrix exploit + this thread exploit chain works even on the very newest Amazon stock firmware you can just basically grab whatever's on Amazon's download page to use anyway, you'll still be able to compromise it

2: rename the firmware to *.zip as you said and then flash it via TWRP

3: flash Magisk for root

That will get what you want which is the latest Amazon firmware but on a modified system with full access to the hacked downloader mode, TWRP + Magisk. You'll need to do a lot of work afterwards to kill off the Amazon crap and turn it into a semi-useful device but at least all the main features of the tablet will now be operational. I have no idea where you found the "remove the preloader, tz and lk flash lines in updater-script" quote in the previous thread but no, I certainly didn't bother with any of that. Considering I am just a random unknown poster in an XDA thread posting advice this might seem like an ironic thing to say, but be really careful about following random unknown poster's advice on XDA threads, a lot of the replies are from morons :silly:

Don't worry too much either way - worst comes to the worst these tablets are easy to take apart and if you somehow softbrick it then a bit of shorting should resurrect it.
[Fire HD 8 and HD 10 Original Android Development] smithbill:
Thanks again for taking the time to post some very helpful details. However, I'd just like to confirm what you've said before I try it:

1. I was on Fire OS 5.6.7.0 before I rooted & flashed LineageOS, so can I safely go to this thread

https://xdaforums.com/hd8-hd10/general/firmware-update-fire-hd-10-7th-gen-t3926806 and download the 5.6.4.0 img file for flashing (5.6.7.0 doesn't seem to be available).

2. I can just rename it to .zip, boot into TWRP and flash it. It won't restore my partitions to original, but that's of no real consequence if I just want to use it as an Alexa device

3. I flash Magisk right after while in TWRP and reboot

4. I end up with FireOS 5.6.4.0, Magisk & root access, TWRP recovery still intact (in case I ever decide to go back to LineageOS)

5. I spend several hours using SU to debloat the assorted Amazon crap :)

---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------

Sorry - one more question:

On this Amazon webpage

https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE are 'software updates' for Fire OS. Can I just download 5.6.7.0 (Fire HD 10 7th Gen) from there and use that? It appears to be a .bin.jar file - is there an .img file in there somewhere I can just rename to .zip and flash in TWRP?