yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
So just to clear this up for me, If my device is on the 9820 build, there is NO WAY I can currently root my device ?

Please someone let me know ..... I cant believe I had a rooted tablet and accidentally turned ON OTA --- now it is stock and no root no way ?? :(

I just read this post up abouve my post .....

Does this mean I CAN downgrade / brick / unlock / root ... ?? What is fire.iso ??? -- I am a bit confused now .. please help :)

.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yes, you can unlock/root. If you are on build 9820 that currently requires opening the device and partially disassembling it. See Post #2 for details.

fire.iso is a live linux system that has all the prerequisites for unlocking.
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Oh ok ... well then I guess I must open it up and then use the fire.iso to start the process of unlocking ...

Are there any plans on updating the script in the near future to work on this build 9820 ??

Thank you
[Fire HD 8 and HD 10 Original Android Development] moleg:
Please tell me: the instructions for installing TWRP or downgrading the firmware version for owners who have upgraded the tablet to 5.6.4 (636559820) are a little incomprehensible
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Ok so do I need to brick my tablet

first

then open it and short it ? ( currently the tab is NOT bricked at all and NOT downgraded only upgraded to that ...9820 firm. )

OR do I just go straight to Post#2 and open case and short it, then start with the instruction's here on the OP ?

Currently my tab is running STOCK FireOS 5.6.4.0 ...9820 after the OTA update from 2 days ago but I want to start over and Unlock / Root / TWRP it again.

Please anyone that can answer my questions let me know :)

Thank you
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just follow the instructions in Post #2

It doesn't matter if it is bricked or not, you will have TWRP afterwards.

Be carefull though with the flex-cables and speaker-cables not to damange anything.
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
I do trust what you are saying, but could you tell me please why it says this in another post ?

Should I just ignore it and continue on with the open fire post. ?

If your device can get to the "amazon" screen or the "Fire" screen, do not waste your time here.

I only ask because my Fire does get to both the Amazon and the Fire screen ... in fact it boots all the way to the OS. One last time I ask, it is necessary to follow post #2

and open the fire first .. I will do that at as soon as you can confirm one last time for me please :) - Thank you !!!
[Fire HD 8 and HD 10 Original Android Development] dasbooter:
In raspbian buster after carefully installing all of the prerequisite packages and watching there output i get

./step-1.sh

Testing root access...

uid=0(root) gid=0(root) context=u:r:init:s0

PL version: 4 (5)

LK version: 2 (2)

TZ version: 262 (263)

Your device will be reset to factory defaults...

Press Enter to Continue...

Dumping GPT

34+0 records in

34+0 records out

17408 bytes transferred in 0.001 secs (17408000 bytes/sec)

adb: error: cannot create 'gpt/gpt.bin': Permission denied

I also put the the arm64 mtk-su binary in the bin folder and chmodded it 755 but im already rooted with supersu

NVM : I just needed to set the proper permissions for all of the contents of folder. Those pesky secure linux permissions ;)
[Fire HD 8 and HD 10 Original Android Development] Marksen_HB:
Unbricking

If Recovery OR FireOS are still accessible there are other means of recovery, don't continue.

If your device shows one of the following symptoms:

It doesn't show any life (screen stays dark)

You see the white amazon logo, but cannot access Recovery or FireOS.

Hi k4y0z, after this symptoms i'm expecting a kind of "then ..." because i have exactly this symptom that KF HD 10 is still dark and no LED charge. So does it mean i have to open it or maybe it was broken?

Thanks in advance

Mark
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Yes I also see that, but from what I can tell I still need to open and short it ... I THINK ? .... I have been waiting for

k4y0z to let me know for sure before I open the device up ... I am still waiting but assume he is busy ATM.

k4y0z if you do get back here, please clear this up for me once and for all. Just so you know my device is

running FireOS 5.6.4.0 (build ...9820) and

it does BOOT and RUN just fine

. No black screens no error's. I want to

unlock / TWRP / Root asap ! If I need to open it then that is no problem, I am fine with that method if needed.

Thank you
[Fire HD 8 and HD 10 Original Android Development] Jimbouser:
Persistence

Sorry, was trying to search, not post!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If it doesn't turn on, there is a small chance you don't have to open it.

But that is very unlikely and only if your device comes up as "MediaTek Inc. MT6227 phone".

See the part about checking USB connection.

I've already told you, when you are on build 9820 you will have to open it.
[Fire HD 8 and HD 10 Original Android Development] sga999:
I think this is the reason that some of us believed the device might not have to be opened up. I certainly could have missed a post where you said you decided not to update brick-suez.zip.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I haven't had the time to look into it yet.

As it stands currently, when you're on 9820 you'll need to open if you want to unlock.
[Fire HD 8 and HD 10 Original Android Development] encephalon9986:
What distro of Linux are you all using to run the commands.
[Fire HD 8 and HD 10 Original Android Development] dannyf1975:
Any ideas on why the shorting method doesn't work? When I short the pin and plug it in it won't come on at all. But as soon as I remove the short it will boot up.
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
The latest Ubuntu (v19.x) works great for me. I use the 'live' version since I only have 1 PC and still want to keep Windows.

.

Good Luck

PS. There is also a special version of a live Linux with all the scripts included for the procedure, posted in this thread somewhere.

I believe it is called fireiso-1.0.0.iso and I 'think' k4y0z created it... If you want to try that just search it.

.
[Fire HD 8 and HD 10 Original Android Development] encephalon9986:
Thank you very much. Made a bootable flash drive with the fireos iso. Ran the commands and then I installed lineage OS and let me tell you it has been long awaited to get a custom ROM on this tablet. It runs 100% better now. No more Amazon crap lol
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Great ! I am glad it all worked out for you :)
[Fire HD 8 and HD 10 Original Android Development] edan13:
sorry in advance for the (probably stupid) question but

how do i find out which firmware i am currently on? I rooted the device ages ago when the exploit was released and blocked all updates but cannot remember which firmware i was on.

in device settings i couldn't find the fw version

:edit found it nvm, please delete not to clutter the thread
[Fire HD 8 and HD 10 Original Android Development] GeneralTweety:
Bootloader unlock

Hi k4y0z,

first i really want to thank you for your work here. It´s amazing what you are doing. :)

I have a Fire HD 10 7th gen with firmware 9820 and i really want to unlock bootloader. Is there in the near future an update from your software possible to unlock it?

Thanks in advance for your help.

Best regards
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
...Ditto :) I am in the same boat you are in with 9820. I will be trying post #2 very soon ( next week ) when I have some free time off. I will also post my results here for anyone in "our" situation to know that it worked out or not. A new updated script would be awesome though :fingers-crossed:

Cheers
[Fire HD 8 and HD 10 Original Android Development] GeneralTweety:
Hi, i did post 2 at the Weekend. Couldn't wait for IT. ? Everything worked Like describet. Only Open the Display and remove the screws from the PCB (because 2 screws stuck and wont Go Out ?) was a a little Challenge. But now a have lineage OS 12.1 working. Really thx to all.
[Fire HD 8 and HD 10 Original Android Development] RieIku:
'ello 'ello.

A little forewarning, I am currently at work but when I get back home later I can retrieve any necessary info.

Basically right now I'm in a little bit of a dilemma as I had some trouble getting step 1 to run due to port issues on my end so I thought, why not just brick manually and recover as that'll allow me to downgrade FireOS at the same time.

Did that, used bootrom-step and then fastboot-step to install TWRP and thought I must be on the home run (as after this point, it was a simple task of installing the rom etc on a friends fathers HD 10).

Instead I'm getting the dreaded "Updater process ended with an error: 255 - could not extract meta-inf blah blah", forgive me but the exact line escapes me currently. I can get this later when home.

I've attempted to rerun step 2 as I noticed was advised earlier in the thread (been poring through it in the hope of finding clues) but have been unsuccessful, this simply appears to reinstall TWRP but nothing else - I still end up with the updater error above.

If anyone has any clues or advice whatsoever I would be so so thankful as honestly, I'm a touch out of my depth on this one. This was hopefully going to be my replacement for my venerable Transformer TF101!

Thanks all in advance!
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
Yep, same here. I'm on 9820 and not confident I can pull off the method in post#2 so I'm gonna wait until k4y0z releases another update to brick-suez. I don't mind waiting longer. No rush, k4y0z. Appreciate what you're doing. Thanks!
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Awesome... I am glad you got it. I'm going to be doing this next few days myself. I hope it goes as smoothly for me ?
[Fire HD 8 and HD 10 Original Android Development] yuera:
I finally took my time and managed to unlock my device. I've never used any Linux based system, VM didn't work, live usb didn't work so I had to fully install on my old HDD.

The procedure was easier than I thought, but I took almost 1 hour trying to change my desktop resolution. Ended giving up and working with a extremely small screen of 1024x768 on my native 2560x1440 :crying:

Thanks for everyone on this thread.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
redacted
[Fire HD 8 and HD 10 Original Android Development] newfirehduser:
Hey, Very quick question

Am I right?

5.6.4.0 build 636559820 - one has to open case to unbrick.

5.6.4.0 build 636558520 - one doesn't have to open the case.

EDIT: I have 5.6.4.0 build 636558520 and I didn't have to open the case, k4y0z You are awesome!
[Fire HD 8 and HD 10 Original Android Development] AJS1986:
Hi all,

First of all I would like to thank everyone who worked on this root. My firmware was too new to use mtk-su but I used the old Kingoroot method before running this one and managed to install Lineage 12.1 on my Fire 10 2017.

Anyhow, whilst I'm happy about most things about Lineage, I'm not keen on the headphone jack not working. Since I now have TWRP on my device, would I be able to just wipe Lineage and flash Fire OS back on and install Magisk from there or would this brick the device?

Thanks
[Fire HD 8 and HD 10 Original Android Development] bales810:
Got this working on my hd10 running 5.6.2. Had a couple issues along the way that may help some other people out.

1) Used the fire.iso which was amazing. Use a program called rufus to put it on the usb

2) Got stuck on step 2 on testing for root...tried everything i could, looked at directory saw root etc. Finally went into supersu on the tablet and opened it played with some settings and it worked...strange\

3) Running Lineage OS 14.1 now. Pretty impressive for a cheap tablet.

Thanks!
[Fire HD 8 and HD 10 Original Android Development] mi7chy:
Amazon just published a new OS update (update-kindle-40.6.3.6_user_636558520.bin) for Fire HD 10 2017 that appears to be an older release. Does this mean one can officially downgrade from 9820 to 8520?

https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
[Fire HD 8 and HD 10 Original Android Development] elgreco93:
Would be interested as well. I dont want to open my device to downgrade.

EDIT: My device upgraded to 5.6.4.0 (636559920) dont knwo if its the one mentiont above
[Fire HD 8 and HD 10 Original Android Development] pcmp:
Well, I'm still on the original 636558520 rom (haven't used it since March) and it stalls at "waiting for bootrom", no automatic reboot. When I manually restarted the tablet it came back bricked and on preloader mode (lsusb). I retried all the steps while on preloader mode and nothing, started at different points and nothing. The only time I got some sign of life was when it got stuck at a handshake (can't remember what step). At least it seemed that it could see something to handshake to.

It came back from being bricked after I pressed the power button for a while and I'm using the latest Ubuntu on a laptop with usb3 ports only.

Any suggestions on what to do next?
[Fire HD 8 and HD 10 Original Android Development] osteohd10:
HD10 screwup

I'm not sure if my HD10 is recoverable.

I will trace my steps:

1) firmware is 5.6.4.0 March 2019

2) latest 64bit mtk-su in bin folder

3) Did sudo ./step-1.sh correctly

4) After typing YES, disabled/uninstalled ModemManager

5) Did sudo ./bootrom-step-minimal.sh correctly

6) Got to hacked fastboot mode

This is then where I screwed up. Got distracted by something important. Came back flustered. Forgetting I'm in hacked fastboot mode.

Instead of sudo ./fastboot-step.sh, I thought something went wrong and thought I had Type 1 brick. I reset the tablet.

7) Did sudo ./bootrom-step.sh

8) The script completed partitioning and writing to the tablet.

Now I have a tablet that boots, but only to "Enter PIN/Password" screen on Fire OS.

The recovery is Fire OS recovery (using right volume button + power).

Any thing I can do to fix the situation?

Thanks.
[Fire HD 8 and HD 10 Original Android Development] abikerider:
5.6.4.0 636559920 Update

My device also updated to 5.6.4.0 636559920. Does anyone know if this changes the rootability of it?
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
U care to share ur steps. I'm on the exact model. But it's freezes at waiting for bootroom
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
. Ik u can still root it with kingroot
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Lil more details. I installed Ubuntu full install on a spare laptop I had. Did all the steps but when I get to sudo .bootrom-step I get waiting on bootrom. One question I unplug after I do yes r after disabling managers?

Running 5.6.4 .0 (636559920)

Nov 12 2019
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Rooting/unlocking is still possible without opening the device

Tried it on fireOS 5.6.4.0 v.9820.

I haven't used/tried mtk.su.

I followed an old guide here, in order to get root/supersu.

With that, the steps 1-3 from OP working fine (i.e. step1 + bootrom-step-minimal).

The fireISO worked fine up to the fastboot-step... but I've got an 'Assertion 'pad >= 0' failed' error, i.e. the flash twrp command in the fastboot script doesn't work due to this fastboot bug. Ubuntu 18.04 worked for me.

If the fastboot-step waits forever for a device, the fastboot version is to old. As I said, ubuntu 18.04 worked fine.
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
.

Please this has been asked now a few times but still no answer. Does anyone know if the very latest build [

Fire OS 5.6.4.0 (...9920)

] is Rootable or able

to install TWRP via the OP in this thread,

with OR without

opening the device. I know that with build ....9820 you had to open the device so I assume

build ....9920 is the same, but would like any clarification if possible ?

Thank you for any info ....

.
[Fire HD 8 and HD 10 Original Android Development] Nosepull:
I am also very interested. The post above yours claims that it is possible even with 9820 to root without opening (differs from OP), so it might be possible with 9920 in the same way?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Like k4y0z said, the root/unlock should always be possible 'with' opening the device, regardless of the OS version, unless a new hardware revision with an revised SOC's bootrom comes out.

Without opening, rooting with OP won't work, since mtk.su is patched.

The step-1.sh from OP needs root, in order to downgrade Preloader, TZ and LK.

But if the device is rooted (as stated in the OP), for example with kingoroot or others, the OP works regardless of the OS version.

That way I 've unlocked a new device on fw 9820 'without' opening two days ago, as described one post over yours.

It depends.

Should work fine if you root your device infront of the OP steps, like described in my posting with 9820.
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
@Sus_i

Thank you for taking the time to reply. You have answered my question and now I can move onto the repair.

Cheers !

.
[Fire HD 8 and HD 10 Original Android Development] gerg004:
[MENTION=2382301]Thibor69[/MENTION]

Can you let me know how your process went? I've recently come across this device on this firmware version and would love to know if downgrading and root is possible.
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Unfortunately I got called out of state for a few days so i can't even attempt this until i return home. I hope to get this done maybe Monday or Tuesday but could be even Thursday or Friday. I will definitely post my results here when i have done it, so if you can wait then you are ok...if you end up doing before me please let me know your results :D
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
being that its NEWER then the builds you can't root or unlock without opening

one would logically except that nothing has changed

its like talking to a wall with you kids

use your fracking brains
[Fire HD 8 and HD 10 Original Android Development] gerg004:
I end up following this (without opening!) and have successfully gained root on my HD 10, 5.6.4.0 9920.

Just got my Linux environment setup last night and haven't had a chance follow the rest of this guide. Guess it's still unknown how unlocking/TWRP will go on this build, but I guess we'll find out!

I'll keep you updated.

See above please. No need for all of the unhelpful, unnecessary, uncalled for comments.
[Fire HD 8 and HD 10 Original Android Development] Legitsu:
root != installing malware
[Fire HD 8 and HD 10 Original Android Development] gerg004:
And what "malware" would that be?
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Who cares about the initial root method!?

Root is needed for the step-1 script from OP to downgrade LK and TZ... as well as zero out the PL a bit, in order to get into the bootrom without opening the tablet. After that the bootrom-step-minimal script does the unlock magic.

Fact one is that with the fastboot step runs a full factory reset after installing TWRP.

Fact two is that with twrp it's easy to wipe the system partition + install a clean rom.

Anyhow, If there was any malware at all, it's gone now :p

Pretty pointless debate in my opinion ;)
[Fire HD 8 and HD 10 Original Android Development] kquade:
I have no recovery or twrp on my Fire 10 HD. I rooted it out of the box and recovery was somehow screwed up. I'm trying to use these steps listed to get recovery and/or twrp, as I was sent here for a solution. Step 3 on the terminal sits while the tablet does absolutely nothing. I can interrupt via ctrl+z, but then I'm still stuck. What now?
[Fire HD 8 and HD 10 Original Android Development] DB126:
You can feign ignorance and pretend KingRoot, KingOroot and similar 'one click' tools are straight from Mama's kitchen but me thinks you're better than that. On the other hand, such tools are not guarenteed malware laced ransomware that will automatically ruin your device, life and extended family for generations to come. In the end it boils down to heeding the disclaimers noted in the thread you linked and deciding whether the risks are acceptable. The zero-sum, highly polarized FUD crowd needs to get over themselves.

On a personal note I have used both and seen good and bad behaviors. Pick your poison wisely.

---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------

Exactly - right on the money if an immediate wipe is in the cards.
[Fire HD 8 and HD 10 Original Android Development] gerg004:
Well don't you need the initial root method to continue here? I was just letting [MENTION=2382301]Thibor69[/MENTION] know that I achieved it on the same firmware he is on.

And there was no malware debate, I've no malware nor was I concerned of any. I was giving him the opportunity to continue to show that he doesn't know what he's talking about..

---------- Post added at 01:22 PM ---------- Previous post was at 01:18 PM ----------

I didn't use any one-click rooting method though. I guess that was my point.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Yeah, that's exactly what i mean... :good:

Thank you for your feedback about rooting the latest OS. I bet the unlock works fine.

Don't worry, I've got it right ;)

I've used kingoroot, running in sandboxed windows 7.
[Fire HD 8 and HD 10 Original Android Development] gerg004:
Haha ok good, sorry if that seemed defensive, it wasn't.

The intentional brick step does make me a bit nervous. But it all comes with the territory I guess.

Will be attempting the process later this evening.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Hmm, I can't comprehend what you did or what you mean. ;)

Can you explain the problem a bit more detailed and what you did until now?

For me anything went fine.

The script checks root access as a first step. Then it checks the PL, TZ and LK versions. After typing YES, the preloader gets bricked, in order to get into bootrom.

If the bootrom-step-minimal script doesn't find anything, you may just holding the power button until the script finds the bootrom. If anything goes wrong, save the terminal log.

Good luck.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Fair enough. I obviously misinterpreted your original post on this topic which is on me. Glad you are finding a satisfactory path forward.

And yeah, there are a lot of folks who don't know what they are talking about even though they are pretty sure they do (salute to the echo chamber).