yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] mark1holland1:
Hi,

I was wondering if anyone could help me - I have a Fire HD 8, 7th gen - this is correct model as I checked before I started.

I used this thread (https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846) and the read the first posts before I started but obviously made some kind of error.

I unlocked dev options on the tablet then put ADB debugging on. I updated all the required packages on my chromebook (running gallium OS) and confirmed the tablet was attached with adb devices. I downloaded the 1.2 douglas zip file and brick douglas zip files. I also downloaded the mkt-su and placed the AMD 64 file in the extracted douglas files (brick files also in this folder).

The tablet was running the most recent firmware - i tried to brick with one file but it would not work so i tried the file 9820 file and this worked.

The problem is I stupidly then ran the 'bootrom-step-minimal.sh' and not the bootrom-step.sh. Please excuse my stupidity - I had 3 children harrasing me at the time!

The tablet is not hard bricked - it boots up to the amazon logo and sits on this screen then restarts. It will also power off and on - returning to the amazon logo each time.

Could anyone advise what is the most efficient thing to do from this point?

- Can I root etc from here?

- Or do I need to go back to stock and start again

If people could advise of what I need to do with a point by point I would be greatly appreciative.

Thanks in advance,

Mark
[Fire HD 8 and HD 10 Original Android Development] navin23:
I think i bricked my device and now i have a black screen all the time. If i remove the battery connector from the pcb board and connect the tablet to the laptop after 18 seconds i saw the amazon logo flash for a second and then the screen is completely black. I'm also getting the error below. The software is FireOS v5.6.4.0. Let me know if there is a way to revive this tablet. Thanks

dell@dell-Latitude-E5510:~/Desktop/FireHD8_2017_douglas/amonet$ sudo ./step-1.sh[sudo] password for dell:

Testing root access...

Trying to use mtk-su to get temp root...

No mtk-su found, you can get it here: https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595

dell@dell-Latitude-E5510:~/Desktop/FireHD8_2017_douglas/amonet$ sudo ./bootrom-step-minimal.sh

[sudo] password for dell:

[2020-05-07 12:38:13.237535] Waiting for bootrom

[2020-05-07 12:38:29.156157] Found port = /dev/ttyACM0

[2020-05-07 12:38:29.186377] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

b''

b'\x00\x01'

Traceback (most recent call last):

File "main.py", line 256, in <module>

main()

File "main.py", line 129, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/dell/Desktop/FireHD8_2017_douglas/amonet/modules/load_payload.py", line 123, in load_payload

dev.write32(0x10007008, 0x1971) # low-level watchdog kick

File "/home/dell/Desktop/FireHD8_2017_douglas/amonet/modules/common.py", line 163, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/home/dell/Desktop/FireHD8_2017_douglas/amonet/modules/common.py", line 90, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Check to see if you are in preloader or bootrom
[Fire HD 8 and HD 10 Original Android Development] navin23:
How do i check those state? I was able to get the tablet to boot again by unplug the battery connector and press the power button down for 20 seconds, then reconnect the battery connector and then connect the tablet to the laptop.
[Fire HD 8 and HD 10 Original Android Development] o0Scope0o:
Thank you so much for this, followed your instructions and unbricked on the first attempt! :good:
[Fire HD 8 and HD 10 Original Android Development] navin23:
The only way was to use the hardware unlocking and it worked the second try. Wasted 6 hours trying the soft unlocking. The hardest part was removing the pcb board from the case because it was glue on there real nice.

If you are staying on Fireos

20. When in TWRP wipe data, reboot tablet and setup tablet again.

21. Enable Developer mode and usb debugging

22. Reboot into TWRP and install Magisk. Then you can block updates

Hardware unlocking

https://xdaforums.com/hd8-hd10/orig...17-douglas-t3962846/post80287339#post80287339
[Fire HD 8 and HD 10 Original Android Development] Nittola:
I was using the softbrick method, because my tablet was update with the latest software, but then when I ran sudo ./bootrom-step-minimal.sh, there was a blackout at my home. Now my Fire 8 HD opens up, show the Amazon logo for seconds and then reboot. I can't access in recovery by pressing Vol+ and Power. What can I do?
[Fire HD 8 and HD 10 Original Android Development] micmc23000:
fire hd 8 (2017) twrp installed fire os 5.3.7 no root- ./step 2 not working

I am using a fire 8hd running fire os 5.3.7

I have followed the steps above on my fire hd 8 (7th gen) i have managed to get twrp installed through the bricking the device then gotten to the stage where the device is reset and twrp is installed. my problem is that now when i go to run the --" sudo ./step-2.sh " script it doesnt seem to run. My question is fromm here can i manually install supersu as a zip and install through twrp or would this brick the device. The device is showing fireos 5.3.7 after completing the temporary brick stage. It is possible I am trying to run this on the wrong screen what screen should these steps be run on?

Thank you for any help :)
[Fire HD 8 and HD 10 Original Android Development] dishguy05:
not sure what i'm missing, but when running

sudo ./bootrom-step.sh

i get the following error

user@host amonet-douglas-v1.2 % sudo ./bootrom-step.sh
Traceback (most recent call last):
File "main.py", line 8, in <module>
from common import Device
File "/Users/am/Downloads/FireHD8 - root/amonet-douglas-v1.2/modules/common.py", line 6, in <module>
import serial
ModuleNotFoundError: No module named 'serial'
user@host amonet-douglas-v1.2 %

Edit: FYI, i'm on MAX OS X 10.15.2
[Fire HD 8 and HD 10 Original Android Development] dishguy05:
switched over to a Windows PC, installed WSL and finally got it to work after hours of troubleshooting ADB bridge version issues
[Fire HD 8 and HD 10 Original Android Development] arima0k:
if it keeps showing MT65xx Preloader, then is it completely bricked?
[Fire HD 8 and HD 10 Original Android Development] poker94:
Stuck at "This firmware cannot be supported"

Hi,

When I run

sudo ./step-1.sh

I get the following output:

Testing root access...

Trying to use mtk-su to get temp root...
Pushing root files
bin/mtk-su: 1 file pushed. 5.0 MB/s (65216 bytes in 0.012s)
bin/minisu.img: 1 file pushed. 7.2 MB/s (1048576 bytes in 0.139s)
bin/busybox: 1 file pushed. 8.1 MB/s (587368 bytes in 0.069s)
Failed critical init step 4
This firmware cannot be supported

The last two lines keep repeating every second.

My Kindle is on version 5.6.6.0

If I understand it correctly, I would downgrade my device during this process.

But now I don't get further, because I am not even asked to accept bricking my device.

Does anyone know, what I have to do?
[Fire HD 8 and HD 10 Original Android Development] WascalyWabbit:
Hi all

First time poster so apologies in advance if in the wrong place or wrong format.

I'm looking to use the above to unlock my HD Fire 8 HD 7th gen and then install lineage but I'm a little unclear on the order of the steps above when having to downgrade first.

My device is HD8 7th gen, running Fire OS 5.6.6.0 (not rooted)

I have done the following

Installed python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu

Extracted the attached zip-files so that I can open terminals in the directories.

Got mtk-su by [MENTION=8132642]diplomatic[/MENTION] and placed (the unpacked binary) into amonet/bin folder

Enabled ADB in Developer Settings

If I am downgrading the fire OS, do I follow the Going Back to stock process below before running steps 3 & 4? or do I do this somewhere between the two?

Also the hidden content between steps 3&4 is a little confusing. Is this just needed when downgrading or is it part of the main process?

Thanks In Advance.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
This is a belated reply. But would be useful to others whose device is on FireOS 5.6.4.0 or newer.

Sure enough, mtk-su to temporary root the device is not working on these FireOS versions.

There is a working alternative.

Install Kingo Root apk onto the device and run it.

The device is now rooted.

You can then use ./Step-1.sh according to OP without the need to use mtk-su anymore.

This alternative worked on two 10HD 2017 devices. It may work on 8HD 2017 devices too.
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
Have you tried Kingo Root on the HD 8, 2017? There is a specific vulnerability on the HD 10, 2017 which Kingo Root exploits. AFAIK other models (e.g. the HD 8, 2017) cannot be rooted in this way.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
Kingo Root apk worked on two 10HD 2017 with FireSO 5.6.6.0 which is even newer than FireOS 5.6.4.0 that was the threshold version such that mtk-su has stopped working.

I do not have a 8HD as yet. Waiting for a used one from eBay. I will report back if this device has FireOS 5.6.4.0 or newer. Othewise, I have no relevant device to test.

Actually, anyone with a 8HD 2017 can download, install and run the Kingo Root apk. It will tell you the state of the device the 2nd time you run the apk, after using it to root the device in the 1st run.
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
Does not work. Gets stuck at 90% forever

Edit: I should mention im on 8HD 2017 with 5.3.7.0
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
That happened also to on both of the 10HD 2017 devices that I unlocked.

Just come out and tap the apk again.

The second time, it shows you the device is rooted already.
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
Nope, doesnt make a difference

Edit: I tried again, letting it just sit at 90 until something happened. Eventually it pops up saying root failed and to try the pc version
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
My 10HD ran ait FireOS 5.6.6.0

Your 8HD runs at FireOS 5.3.7.0

There are many hardware and software differneces.

Good luck with your PC version of Kingo Root, if you go down this route.
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
I mean you are the one who keeps claiming that it will work on HD8 2017. Another poster even responded to you saying that it likely wont work because the exploit doesnt apply to the douglas model. I went ahead and tested it and can confirm

No, it is does NOT work.

Im not planning on trying the PC version, just gonna use the methods described elsewhere in this thread
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
I am suggesting it may work and not claiming it WILL work.

Good that you confirm that it does not work.:good:

I checked mtk-su thread.

It says

Thus 5.3.7.0 on your device (which is newer than 5.6.6.0 on my device) may have already closed the exploit to allow Kingo Root apk to root the device.

I am also suggesting here. I am not expert in such area.
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
Yes its definitely the newer firmware that is the issue. Currently installing linux to test the approach detailed in post #472
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
Please report back if post #472 works for you or not.

If possible, some step by step description of your process will help others too.

I will read your post with interest. This is because I am waiting for a 8HD 2017 from eBay to arrive. I have every intention to unlock it and flash Lineage OS.
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
Looks like #472 is a winner. I was able to successfully brick using the -9820 file and and install TWRP. Not sure what my next step is to install root/custom os so now Im gonna go look into that.

The only thing I had to do differently was at the beginning when downloading the android tools

sudo apt update

sudo add-apt-repository universe

sudo apt install python3 python3-serial adb fastboot dos2unix

I had to run "sudo apt-get update" before the last step, because it was not finding adb fastboot or dos2unix

edit: I must be having a brain fart. How do i get back into TWRP after a reboot? HOlding down power + volume down doesnt seem to work
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
The device is in power off state

Press VOLUME UP + POWER buttons simultaneously.
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
Got it. Successfully installed Lineage OS now. So glad to have this thing rooted
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
May I ask which version of Lineage OS is compatibe with Fire 8HD 7th gen (2017)?
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
This one. It's pinned in the forum this thread is in. I also had to use pico gapps to get it working
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
I think it is Gapps pico for ARM and not ARM64.

Am I right?
[Fire HD 8 and HD 10 Original Android Development] ModuRaziel:
I used 64 and it seems to work
[Fire HD 8 and HD 10 Original Android Development] carlosmessala:
Many thanks!

Firstly, I want to thank you for the great work! It worked like a charm!

I was at 5.6.6.0 and I had to use the brick-9820.sh brick version command (brick.sh do all upload to the device and just reboot FireOS as if nothing changed).

I would add to the lowly mortals like me, that you need to reboot to booloader before you run the brick command (brick.sh or bick-9920.sh).

adb reboot bootloader

Again, thank you, [MENTION=7104332]k4y0z[/MENTION]! Amazing job!
[Fire HD 8 and HD 10 Original Android Development] adityashah0098:
[MENTION=5131994]carlosmessala[/MENTION], I am on 5.6.6.0 too (received an update just a day back). Is it possible for you to recollect if your build was 654620620?

Also, to simplify the instructions, you followed these steps?

sudo ./step-1.sh

adb reboot bootloader

sudo ./brick-9820.sh

sudo ./bootrom-step.sh

sudo ./fastboot-step.sh
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
I also want to know the details.

My impression is very similar to yours, except I would skip running sudo ./step-1.sh

Let us wait for clarification from other experienced users.

EDIT: I think sudo ./step-1.sh would not work. This is because it would invoke mtk-su if your device is not rooted. But FireOS 5.6.6.0 cannot be rooted by mtk-su. Thus I would deduce that you may skip sudo ./step-1.sh
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
Dear Friends

When i try to root my hd8 2017 (douglas) by bootrom-step give me this error

[2020-06-11 02:27:33.218732]

[2020-06-11 02:27:33.218958] Check boot0

[2020-06-11 02:27:33.511356] Check rpmb

[2020-06-11 02:27:33.736158] Clear preloader header

[8 / 8]

[2020-06-11 02:27:34.323531] Downgrade rpmb

[2020-06-11 02:27:34.338328] Recheck rpmb

Traceback (most recent call last):

File "main.py", line 216, in <module>

main()

File "main.py", line 175, in main

raise RuntimeError("downgrade failure, giving up")

RuntimeError: downgrade failure, giving up

My tablet now not work please help me
[Fire HD 8 and HD 10 Original Android Development] Stevohen:
Okay so I had to scour these posts like a rabid dog looking for scrap meat to figure how to do this. I'll share what I did and hopefully this will be of help someone. I was on, as far as I could tell, the newest Fire OS version. Think it was 5.6.6 prior to doing this

0. Download the newest amonet-douglas, download brick-douglas from the first post. Copy the amonet folder from brick-douglas so everything is together

1. Follow the install instructions from that post (sudo apt install etc). Also run the stop ModemManager and disable ModemManager

2. Enable developer settings and ADB on tablet

3. Plug in tablet

4. run in terminal: adb reboot bootloader

5. Tablet should reboot into bootloader

6. run in terminal: sudo ./brick.sh

7. confirm the bricking by typing "YES" in capital letters

7. This will take a while. When the terminal is done, the tablet should display a cool message when everything worked

8. Power off the tablet but DO NOT ATTEMPT TO POWER IT BACK ON. If you do, you will have to find a way to repeat the bricking process because this resulted in constant "Serial protocol mismatch" errors for me

9. Run in terminal: sudo ./bootrom-step.sh

10. This will also take a while. Once done, the tablet is suppose to boot into hacked fastboot mode. This did not happen for me

10.1. If hacked fastboot does not happen for you, I had to power down the tablet and hold vol_up + power to get to a Fire logo screen showing HACKED FASTBOOT

11. Plug in tablet. I was stuck here because sudo fastboot devices would just show "undefined symbol: _Z15ErrorCodeStringi" even though the tablet is obviously in fastboot mode. But I realised the fastboot binary in the included bin folder works. Running sudo ./bin/fastboot devices showed my device.

11.1 If sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot

12. Run sudo ./fastboot-step.sh and watch as TWRP graces your tablet screen

Tips:

- You do NOT need to run ./step_1.sh or ./step_2.sh with the above instructions

- if sudo ./brick.sh does not seem to get you into hacked fastboot, try the other sudo ./brick(-9820).sh script BUT, then you need to run sudo ./bootrom-step-minimal.sh in step 9

- I found it helped to disconnect the battery at one point when holding the buttons would not do anything. Hold the volume and power buttons really long and try Volume_down/Volume_up to before going this far
[Fire HD 8 and HD 10 Original Android Development] islender137:
I read that "If you are on a firmware newer than 5.6.4.0, a downgrade is necessary, this requires bricking the device temporarily." My firmware is below this (5.3.7.0) yet the step-1.sh script (with the mtk-su binary included) refuses to work (I get an Unsupported Firmware error). Does the build number have something to do with this? My build number is 650601220. I assume I needed to downgrade somehow and since the above step didn't work I tried the brick.sh script. I'm pretty sure I set up everything correctly, yet, when I run brick.sh it prints a few lines then I get a "< waiting for device >" prompt. And yes, my device is connected and in fastboot mode. ADB also works correctly, fastboot doesn't seem to however. Anyone have any ideas?
[Fire HD 8 and HD 10 Original Android Development] xenonrider:
Hi, my Fire HD 8 is rooted and the firmware is below 5.6.4.0. Can I just skip to step 4 and run sudo ./step-2.sh ?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You still need to start with step-1.sh
[Fire HD 8 and HD 10 Original Android Development] bentley4me:
"9. Run in terminal: sudo ./bootrom-step.sh

10. This will also take a while. Once done, the tablet is suppose to boot into hacked fastboot mode. This did not happen for me

10.1. If hacked fastboot does not happen for you, I had to power down the tablet and hold vol_up + power to get to a Fire logo screen showing HACKED FASTBOOT"

I followed these instructions, ./brick did not work, so I used ./brick-9820.sh, which worked. I then followed the footnote and used step-minimal, received the PWNED message, but now the reboot just loops the amazon logo (no hacked fastboot on reboot). I held down the power and volume + (as well as power and volume -) for like 3 minutes each...nothing seems to work. Any ideas how to proceed from here? I'm fairly novice.
[Fire HD 8 and HD 10 Original Android Development] xenonrider:
Thanks for the reply. Do I also need to run these commands in #3 ?

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

sudo ./bootrom-step-minimal.sh

sudo ./fastboot-step.sh
[Fire HD 8 and HD 10 Original Android Development] Roflox2002:
Tks. Totally noob here.

I think that post #513 is inducing the use of the wrong file: "if sudo ./brick.sh does not seem to get you into hacked fastboot, try the other sudo ./brick(-9820).sh script BUT, then you need to run sudo ./bootrom-step-minimal.sh in step 9"

Just as poster #518 I'm also on the Amazon logo loop.

Can anything be done on this scenario?
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
brick my device

my device was brick after root when i try to use the brick.sh or brick-9820.sh i get this massage

Failed (status malformed (0 bytes)

( now my device in fastboot mode with black screen and locked hw)

what can i do please
[Fire HD 8 and HD 10 Original Android Development] CoolestTester41:
Is there any clear instructions to downgrade from FireOS 5.6.6.0 to 5.6.4.0. After downgrading, which scripts should I run to get into TWRP. Thanks in advanced! :D

I'm new to the whole flashing thing with the kindle fire. Hope you understand
[Fire HD 8 and HD 10 Original Android Development] m0000:
can someone please share direct link to 5.6.3.0 for douglas? im struggling to find it. i found it for hd 10 but not hd 8

Thank you.
[Fire HD 8 and HD 10 Original Android Development] sugarwater:
a little question about serial numeber

[MENTION=7104332]k4y0z[/MENTION] Thank you very much. As a rookie in China, I bought an HD8 2017, the original Amazon system is not working well. Always wanted to change the system, but no way, until I saw this post. Thank you very much for your hard work and deserves my respect. And I noticed a file called GDT-D01eb0a014660Q99 in a subfolder called Amonet-Douglas-V1.2. This filename happens to be the same as my HD8 Serial number and I wonder if it is possible to restore the original serial number. Because when I bought it, I was told that the serial number had been swiped. Thank you very much for your efforts, thank you!:D
[Fire HD 8 and HD 10 Original Android Development] adityashah0098:
Thank you for the detailed instruction, [MENTION=10911591]deverro[/MENTION]. Can you help me with two questions?

1. Did you try with brick.sh or brick-9820.sh on your first try? Which one worked?

2. Is it necessary to format to ext4?
[Fire HD 8 and HD 10 Original Android Development] deverro:
1. On first try, brick.sh didn't work for me (can't write permission), so I used brick-9820.sh. But take note on point no 2.

2. My thought, it's necessary.

When I rooted other tablets and phones, usual guide was to format it to EXT4. So I still abide by that and haven't had any errors.

As I use linux and EXT4, seems logical that Android (which is linux) would run best on that type of partition.

At first when i was in TWRP, I didn't format, I just wiped, and upon reboot, original installation mount (or something) activated and started reinstalling FireOS.

I then thought, it was all over and I won't be able to redo it again. Tried again with brick-9820.sh but failed.

Then tried with brick.sh and it worked.

So, when I was in TWRP again, I immediately formated and wiped partitions mentioned in my original post.

That way I wiped even the original FireOS backup and if I rebooted it couldn't reinstall FireOS anymore.