yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] pug_ster:
Recently there was a sale on this Fire hd 8 gen 7 for $20 at Woot so I brought it so I tried to hack. It is hard to find a one with the firmware 5.6.4.0 or lower so this is how I got it to work. Honorable mention to Opec who actually got the instructions right so I modified his instructions a little to fit everything in.

A) amonet-douglas-v1.2.zip from first Page of this Thread:

https://xdaforums.com/...p.4845269/

Unpack the Archive to a separate Folder.

B) brick-douglas.zip from first Page of this Thread:

https://xdaforums.com/...p.4825253/

Unpack the Archive to a separate Folder.

1) Boot from a live version of linux (I used Ubuntu mate Lts 20.04) or you can install linux in your computer.

2) Run the following commands to install tools;

sudo apt update

sudo add-apt-repository universe

sudo apt install python3 python3-serial adb fastboot dos2unix

3) Disable modem manager

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

4) Reboot FireHD8 to Recovery (Power Off device, then hold VolUp + Power)

5) Select Factory Reset then Wipe Cache

6) Reboot to Bootloader. You will see the black screen with "Fastboot" in the lower corner.

7) Connect your usb cable to the tablet.

8) Open Terminal from "brick-douglas" folder an enter "sudo ./brick.sh (note that you are actually bricking your fire tablet in order to recover)

9) Check Display output for the "Disconnect USB and Powerdown" Message and do so when prompted. Proceed to step 10 if there no problems, but it didn't work for me.

*** Note if you see an error and the FireHD Reboot and do the "Apps and Data Optimization" at the Welcome Install Screen Powerdown the FireHD and enter Bootloader again.

a) repeat steps 4-7

b) Enter "sudo ./brick-8920.sh" instead of brick.sh

c) You should see Display output for the "Disconnect usb and powerdown" message and do so when prompted.

10) Open Terminal from "amonet-douglas-v1.2" foder.

11) Enter "sudo ./bootrom-step.sh"

12) Reconnect USB while your tablet is off.

13) Wait until the bootrom step is finished

14) Enter "sudo ./fastboot-step.sh"

15) You will end up in TWRP

16) Prepare a microsd card with Lineage OS 15.1 or 14.1 with the rom and gapps and install Lineage OS.

https://xdaforums.com/...1.4328503/

https://xdaforums.com/...1.4195349/
[Fire HD 8 and HD 10 Original Android Development] Angus_xda:
Thanks. I was stuck until I found your instructions.

There is a small typo at instruction 9) b) sudo ./brick-8920.sh should be sudo ./brick-9820.sh

Now I'm stuck at 14) :)

< waiting for any device >

I'm doing this in a Mint VM in VirtualBox.

MediaTek MT6277 is shown as attached in the VM.

MediaTek USB port is attached in Windows.

USB\VID_0E8D&PID_0003&REV_0100

USB\VID_0E8D&PID_0003

Got any advice?

UPDATE

Got it. This post covered the fix.
[Fire HD 8 and HD 10 Original Android Development] Drachna:
I ran ubuntu from a USB stick, and it worked like a charm.
[Fire HD 8 and HD 10 Original Android Development] bolidew:
Did you have to open the device when fixing it?
[Fire HD 8 and HD 10 Original Android Development] Angus_xda:
No, I didn't.
[Fire HD 8 and HD 10 Original Android Development] jlim0930:
Found the issue. it had to do with

MT65xx Preloader

Went the hardware route and was able to recover

too bad i broke the screen and the one of the ribbons in the process but the hardware method did work!
[Fire HD 8 and HD 10 Original Android Development] SamDungUser:
try running gpt fix.sh --> bootrom-step.sh --> fastboot-step.sh. GPT Fix is on the first page.
[Fire HD 8 and HD 10 Original Android Development] SamDungUser:
You probably broke it after getting the motherboard off of the case to short TP28.
[Fire HD 8 and HD 10 Original Android Development] hillsomec:
Can I do this on Windows?
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
Forgive my present ignorance, but what is the latest TWRP version for douglas? Does it include the new Samsung exFAT drivers, or some old version of something?
[Fire HD 8 and HD 10 Original Android Development] GoodSoul:
I was stupid enough to upgrade Magisk in the App. The App patched my boot and since this is a special boot my tablet does not boot anymore.

It stucks at the Amazon logo. I still have access to the TWRP recovery. So what do I need to flash where that my tablet is able to boot again?

Thanks in advance for any device! :)
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Flash this to the boot partition (not boot_x) with hacked fastboot or use TWRP (+ ADB) to dd it to /dev/block/platform/soc/by-name/boot_amonet
[Fire HD 8 and HD 10 Original Android Development] GoodSoul:
Thanks for reply @Rortiz2!

I am able to boot to TWRP. Fastboot does not show any devices on my pc. What would be the command to do for adb sideload?

Edit: Tried to flash full.img as img on TWRP. Results in: "Size of image is larger than target device". Tried to flash image on "boot".
[Fire HD 8 and HD 10 Original Android Development] GoodSoul:
Update: Did the command via Terminal in in Recovery (dd if=image of=/dev/block/platform/soc/by-name/boot_amonet). Did not help. Still rebooting to Recovery. :-|

What else could have Masigk 24.1 touched/broken?

Update 2:

I tried to flash an image in TWRP to "boot". That might have broken something else. Any IMG I can flash here?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
I guess you can always clear the PL header with ADB (in TWRP) and run bootrom-step.sh. That should restore the boot/recovery exploit.
[Fire HD 8 and HD 10 Original Android Development] HedraXDA:
Does this also work with fire hd8 5th generation?
[Fire HD 8 and HD 10 Original Android Development] jpsshield:
I have to say all the different instruction were a little confusing. Have done all of this many times over the years so I am familiar with it. One my first Fire HD 8 douglas 2017 I mistakenly unplug it from the PC and could not get it to do anything. So I threw it the garage thinking I have to rip it apart. Second one....did the same thing...dead. So I was defeated. Well guess what, I just pluged the second one back in and ran sudo ./bootrom-step-minimal.sh and held power for 5 sec, then vol up and pwr but its all black...so I tried several times to time it and boom!!!!! Back in business and it also worked for the first one. :D
[Fire HD 8 and HD 10 Original Android Development] techprobalways:
I started the process of working through the steps laid out in this post on my Amazon Fire Tablet 8. The device had newer firmware than 5.6.4.0 I attempted to brick it. I had to use brick(-9820).sh, but when I try to run bootrom-step.sh, it keeps getting hung up on "waiting for bootrom." So I basically have a bricked tablet that won't do anything at the moment. Any tips for troubleshooting?
[Fire HD 8 and HD 10 Original Android Development] techprobalways:
I am trying to read through this whole thread to try to see if someone resolved my issue. Now I am stuck on it rebooting to the Amazon logo repeatedly.
[Fire HD 8 and HD 10 Original Android Development] R2D2_SW:
deleted
[Fire HD 8 and HD 10 Original Android Development] R2D2_SW:
Tried this but I'm stuck on step 9b. Now whenever I type the brick command, it says "waiting on any device" and just stays like this forever. The first time around, it ran fine with brick.sh but that script failed. Since then, I have not been able to connect to the device. Any advice?

Update: Rebooting my machine seems to have resolved the issue.
[Fire HD 8 and HD 10 Original Android Development] DutyThree:
deleted
[Fire HD 8 and HD 10 Original Android Development] DutyThree:
Just managed to get LineageOS 15.1 on my HD8 Gen 7, coming from FireOS 5.7.0.0. Working really good, so much quicker than before. No Gapps, only F-droid on it and for other stuff Aurora Store, that's what I wanted.

Many thanks to all the helpful guides, especially to @k4y0z , @pug_ster and @kingladar with your step-by-step guides!

For me btw the sudo ./brick-9820.sh worked, first one failed.
[Fire HD 8 and HD 10 Original Android Development] robloxboy:
robloxboy1000@desktop:~/Downloads/amonet$ sudo ./step-1.sh

Testing root access...

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

Pushing root files

bin/mtk-su: 1 file pushed. 6.7 MB/s (60840 bytes in 0.009s)

bin/minisu.img: 1 file pushed. 10.6 MB/s (1048576 bytes in 0.094s)

bin/busybox: 1 file pushed. 7.0 MB/s (587368 bytes in 0.081s)

Failed critical init step 3

Failed critical init step 3

Failed critical init step 3

Failed critical init step 3

Failed critical init step 3

what does this mean?
[Fire HD 8 and HD 10 Original Android Development] Johnny1805:
Hi all,

I got FW 5.7.0.0. Hence I need to intentionally brick it.

However, after typing "YES", I get no prompt on the tablet?

What am I doing wrong?

(when attempting to run step-1.sh, I actually get a message on the tablet. The procedure fails with "Failed critical init step 4. Firmware support not implemented". I guess that's because of 5.7.0.0?)
[Fire HD 8 and HD 10 Original Android Development] Jupp69:
Hello,

been using my HD8 for over a year with LineageOS, presently 15.1 from 13. June 2022. Worked quite well for me. Previous OTA updates (2-3) went smoothly, no problems. Update to LOS 15.1 from 14. June 2022 did not work, black screen after reboot, with recovery mode, then fastboot mode indicated at bottom of a black screen.

Reflashing did not work, error HW locked bootloader. Could not get into TWRP, either. Even opened the device to try a hardware short, found out I would have had to desolder a metal screen.

Shell scripts (brick.sh) did not work. Just before giving up I played around with fastboot commands.

This worked for me:

- switch the tab on

- screen says recovery mode, then a few seconds later fastboot mode

- connect to a linux pc with the usual fastboot & adb tools installed

- open a console

- command: fastboot reboot recovery

- tablet reboots into LineageOS 15.1 13. June version.

TWRP no longer works, cannot be accessed neither through extended reboot menu nor through any hardware button combination. So I keep using 13. June version of this rom.

Any suggestions what went wrong and how I can get back OTA or manual updates and TWRP will be much appreciated.

Regards, -Jupp69
[Fire HD 8 and HD 10 Original Android Development] Kararmowfaq:
Hello..8 want a aptaite for amazon.thanks
[Fire HD 8 and HD 10 Original Android Development] cellist:
I faced the same situation yesterday (yes, it is because of 5.7.0.0) and I was able to put twrp on it, and then LineageOS from there by using the steps described here (under "Root the tablet" until step 8. - confirming root) Then I could go on with "sudo ./step-1.sh", and continue along the temporary-bricking-route. It worked like a charm for me!

So I can also confirm the process described in pascal009's post from here (many thanks!)
[Fire HD 8 and HD 10 Original Android Development] doctorbconway:
I have a tablet stuck in a bricked state after brick-9820.sh. Below is the output. I get a similar "bad gpt" error from the gpt-fix-16g.sh script and trying to run the bootrom-step.sh using the hardware method (but it's hard to tell if I did that correctly). I had another Kindle HD 8 Douglas that I did at the same time that is working perfectly with Lineage OS on it now. Any thoughts?

Spoiler content hidden.
[Fire HD 8 and HD 10 Original Android Development] leathan:
This comment here was all I needed, the OP had me a bit confused thanks much.

Its crazy to think that I had this tablet as a paper weight for all these years, all of the sudden it is a rooted android tablet, I was playing a few games perfectly, running extensions in my browser, cant believe how useful it is now! Thanks to everyone!!!

P.S. You should not need one with 5.6.4.0 or lower. I had the firmware from 2019 which was the last time I used it (5.6.4.0) and it would not work for me until I upgraded to the newest firmware then I booted it into fastboot and ran the ./brick-8920.sh as the other did not work. Also I decided to just make a quick USB stick with Ubuntu 20 and do it that way just because it was written that this might not work on wsl.

THANKS!
[Fire HD 8 and HD 10 Original Android Development] xunair:
I'm already rooted kernel version 5.6.2.6

Running Ubuntu lts

Which steps to follow and which to not

OP is confusing

Amonet zip file extracted

Ubuntu update with all the scripts

Now back to Amonet folder opened Linux shell

Sudo ./step-1.sh

Now which step to follow further!

Thankyou!
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
The OP is clear enough if you read it entirety, from top to bottom. The steps to follow depend on the output of the step-1.sh command. If the output mentioned something about a temporary brick, you need to run bootrom-step-minimal.sh, otherwise you can continue with step-2.sh.​
[Fire HD 8 and HD 10 Original Android Development] CuF:
I don't get this. As soon as I connected to wifi, my tablet immediately started downloading a firmware update that it wants to install. No 'cancel' or 'not now'.

Letting it update the firmware seems counter productive, so I've stopped everything and can't go forward or back.

Edit: OOOooh. Select a wifi network, but DON'T log into a wifi network. THEN you can cancel.

Edit 2: And crap. It did install 5.6.4.0. I guess I have to restart and brick it. getting ready to hit this with a brick.

Edit 3: Step-2 worked anyway. Woohoo.
[Fire HD 8 and HD 10 Original Android Development] xunair:
I tried step-1.sh but nothing happens

Running Ubuntu on windows

Updated & installed everything

Adb is enabled
[Fire HD 8 and HD 10 Original Android Development] CuF:
I ran into that as well. If you are using VirtualBox, make sure (in the Manager before launching Ubuntu) that you add your tablet as a USB device.

Then start Ubuntu and connect your tablet and it should become available.
[Fire HD 8 and HD 10 Original Android Development] xunair:
I'll try that

Thanks!
[Fire HD 8 and HD 10 Original Android Development] event_horizontal:
Hi all.

Can I pick peoples' brains, please?

I have a Fire HD8 2017 that's currently running LOS 14.1*

What's the most recent version of Lineage it will run, and what's the best way to update it, please?

TIA; any help gratefully received!

*It says:

# Android version
7.1.2
# LineageOS version
14.1-20210813-UNOFFICIAL-douglas
# Android security patch level
5 June 2021
[Fire HD 8 and HD 10 Original Android Development] FreakyyLike:
Download Lineage 17.1 Douglas Build and Clean Flash the .zip with TWRP
[Fire HD 8 and HD 10 Original Android Development] event_horizontal:
Thank you!
[Fire HD 8 and HD 10 Original Android Development] CuF:
I recently flashed mine to 15.1 which has only a few minor bugs if you have a Douglas and it has been a joy.

There is a v17.1, but it has the added issue of "Front camera and video recording". Since I need Zoom to work, I didn't try it.

v15.1: https://xdaforums.com/t/rom-unoffic...azon-fire-hd8-7-6th-gen-douglas-giza.4328503/

v17.1: https://xdaforums.com/t/rom-unoffic...azon-fire-hd8-7-6th-gen-douglas-giza.4474959/

And, yes, the general consensus is that you need to clear the old OS before flashing the new. I wish that wasn't the case since official upgrades rarely/never ask you to do that.
[Fire HD 8 and HD 10 Original Android Development] event_horizontal:
Hi CuF, and thanks for replying.

That's interesting; maybe I should try 15.1

Q. Does 15.1 get regular(ish) updates/is it maintained?
[Fire HD 8 and HD 10 Original Android Development] CuF:
I'm sure past releases don't guarantee future release frequency, but I see on github:

17.1 was first released July 31 with updates on August 3, 6 and 9.

15.1 last updated Oct 31, 2021... so I don't know if we can expect any more updates or if R0rt1z2 has moved on.

To me the Douglas has 2 less issues with v15.1 so that's how I went. Especially with 17.1 only 1-1/2 months old.

Like I said, 17.1 known issues:

Hardware decoding (OMX)

Deep sleep isn't working

Front camera and video recording

Can't connect to hidden SSIDs

Sound recording is broken

15.1 issues:

Deep sleep (Doze)

Hardware decoding (OMX)

Camera (both photos/videos) isn't working on giza

Can't connect to hidden SSIDs
[Fire HD 8 and HD 10 Original Android Development] event_horizontal:
Ooh, I've just spotted that; that might be a bit tricky... :-(
[Fire HD 8 and HD 10 Original Android Development] abdce:
Hi, fastboot step is not working for me. when doing

sudo ./fastboot-step.sh

, I get this:

Your device will be reset to factory defaults...
Press Enter to Continue...

< waiting for any device >
[Fire HD 8 and HD 10 Original Android Development] spikked27:
I have an HD8 (douglas) with LineageOS 14.1 installed but have lost TWRP, when rebooting into recovery the tablet just restarts all the way to the home screen, when trying to fastboot flash twrp again I get a message that it can't be done on locked HW:

writing 'recovery'...
FAILED (remote: the command you input is restricted on locked hw)

Assumed I had lost unlock so I tried to use the amonet tool but get the message that it only works on "douglas" and I'm "cm_douglas" which comes from LineageOS. Any idea how I can get twrp back??? Appreciate any help!

~/amonet $ sudo ./step-1.sh
This is only for the "douglas" - Amazon Fire HD 8 (2017) - , your device is a "cm_douglas"

I also tried to brick with brick.sh and brick-9820.sh but received the following error on both:

sudo ./brick.sh
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
YES
Bricking PL Header
Check instructions on device

./brick.sh: line 18: bin/fastboot: cannot execute binary file: Exec format error
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Any error if you use boot-fastboot.sh

Does not need a short, only run and connect, should boot into hacked fastboot.

Flashing will only work in hacked fastboot, not in normal fastboot mode.

You can try to edit the step1 and step2 scripts with an editor...

From

check_device "douglas" " - Amazon Fire HD 8 (2017) - "

to

check_device "cm_douglas" " - Amazon Fire HD 8 (2017) - "
[Fire HD 8 and HD 10 Original Android Development] spikked27:
No error with boot-fastboot.sh but also no response from the tablet after 45min or so so I assumed nothing was going to happen.

Changed the step1 and step2 script and received the following:

~/amonet $ sudo ./step-1.sh
Testing root access...
/system/bin/sh: su: not found

Trying to use mtk-su to get temp root...
Pushing root files
bin/mtk-su: 1 file pushed. 10.4 MB/s (60840 bytes in 0.006s)
bin/minisu.img: 1 file pushed. 15.3 MB/s (1048576 bytes in 0.065s)
bin/busybox: 1 file pushed. 14.1 MB/s (587368 bytes in 0.040s)
Failed critical init step 4
This firmware cannot be supported
/system/bin/sh: su: not found

Tried to use mtk-su according to the instructions here: https://xdaforums.com/t/rapid-temporary-root-for-hd-8-hd-10.3904595/

And got the following error:

~/amonet $ adb shell
douglas:/ $ cd /data/local/tmp
douglas:/data/local/tmp $ chmod 755 mtk-su
douglas:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This firmware cannot be supported
1|douglas:/data/local/tmp $
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Try:

sudo ./boot-fastboot.sh

Then connect the tablet in power-off state.

You can try to push the power button too, while connecting.

Another way may be a long press of the power button key while connected, until the script works...

It should boot within seconds to the black screen with the hacked fastboot message in the display corner...

Edit: I guess mtk su won't work on CM / lineageOS.
[Fire HD 8 and HD 10 Original Android Development] spikked27:
No Error on boot-fastboot.sh, readout:

~/amonet $ sudo ./boot-fastboot.sh
[2022-10-12 20:48:29.254243] Waiting for preloader
[2022-10-12 20:48:55.459661] Found port = /dev/ttyACM0
[2022-10-12 20:48:55.496008] Handshake
[2022-10-12 20:48:55.516266] Preloader ready, sending FACTFACT

It let me flash twrp using the command:

sudo fastboot flash recovery bin/twrp.img

But unfortunately it still just hangs up at the amazon screen when trying to reboot into recovery
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Looks good, check:

fastboot devices

if there is a device connected.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
With TWRP you should be able to safely install any version FireOS without loosing TWRP.

OK, this is strange, no idea what's going on.

Please download the attached ZIP-file and extract to the same directory as amonet.

Then run

sudo ./stock-16G.sh

This will restore stock GPT, boot and recovery and then reboot into Amazon Recovery.

It will take some time.

When you are in Amazon Recovery please do a factory reset and then flash stock FireOS via adb sideload:

https://www.amazon.com/firehd87thgensoftwareupdate

Once you're back in FireOS restart the unlock with step-1.sh.

EDIT:

So I was able to reproduce your issue and I think I have an easier fix than fully returning to stock.

Download the attached amonet-fix.zip and extract to the same directory where you extracted amonet.

Then just run the normal bootrom-step.sh.

I will include this fix in the next update, so this won't happen again.

Until then when you have flashed stock boot/recovery to boot/recovery partitions using fastboot do not run amonet again without this fix.
[Fire HD 8 and HD 10 Original Android Development] Mahesar:
Working perfectly! Thank you very much!
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
OHHHH that is great thank you too much this method 100/100 work and my device work again

thank you for your time

But please i have small question. Why step-1 and step-2 can used with linux shell on win10 but bootrom can not just with linux operation system ???
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Did you do the full stock procedure or did you use the fix I posted later?

About your question, step-1 and step-2 only use adb to communicate with the device, while bootrom uses an entirely different protocol.

Also I don't use Windows, so not much else I can say about that.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
I used amonet-fix

and also i flashed my modified system.img by twrp and every thing go ok without problems

thank you
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
Please help me

amonet-v1.1 for 32gb work without problem

But for 16gb not working i test it on 5 devices 1 from 5 just success but the other fail ???
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
What is the issue exactly? You'll have to give more information.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
Ok

First i use this method normally step-1 after the device formated i use step-2 first device 16 gb success then when i try to make another one and after step-1 & 2 the device stock on amazon logo and restar may by bootloader problem in this case i use bootrom-step with tp28 short and then use fastboot-step after this i get twrp and device work again without use gpt16 fix

But for 32gb this method work without problem i used for 20 devices without problem

That is all and thak you again for your answer
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Not sure I follow.

So you're saying on 16G step-2.sh failed?

Can you provide the output of the script?

After step-2 did you try to manually boot into TWRP?

Did you use the amonet-fix I posted before?
[Fire HD 8 and HD 10 Original Android Development] qbikashgurung:
This is great, thank you to everyone who contributed to it!

My Fire HD8 2017 is now rooted... I used to be on 5.3.4.0. After TWRP was installed I downloaded the lastest update from Amazon's site, and flashed it.

Then I flashed Magisk.

My problem:

I also tried to flash opengapps, I select ARM64 as the architecture, 5.1 as the Android version, and I choose 'pico'.

When flashing, TWRP gives me error 64, saying that this is the wrong architecture for my device, that I should use ARM.

But I thought this device was ARM64. Am I wrong?

Thanks
[Fire HD 8 and HD 10 Original Android Development] Crosby87mvp:
Stuck on Testing root access for step 2, any way to fix this?

Edit: Installed stock firmware to fix but now getting stuck after the root files get pushed