yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] ironman226:
Oh I see. Sorry I’m new here, I didn’t realize both posts were yours lol. Yeah I spent like a week reinstalling fireOS and pulling out my hair trying to get it working before I finally realized my VM software was causing issues. I’m glad you got it going! I learned my lesson this time. No more VMs when I’m flashing stuff lol.
[Fire HD 8 and HD 10 Original Android Development] finwefeanor:
yeah I spend 1 2 days to figure out most of the issue were coming from VM. I didn't want to mess with my windows installed laptop and creating a bootable usb linux might not work because I read that you need to install linux so. safest way seemed to use VM. But it will be much easier to use Real Linux definitely.

But that automatic usb plugged in / out sound stuff important. Idk if it happens on others to. Once you got bricked your tablet with bricked command (before bootrom command) it was constantly plugged in and out automatically in every 30 secs or so. I didn't see something like this mentioned in this topic.
[Fire HD 8 and HD 10 Original Android Development] Linus X.:
Hello great people of XDA,

after 3 years with a mediocre tablet I finally had the time to root it and install LineageOS yesterday. And it's like a totally new device! :victory:

Big love and respect to [MENTION=7104332]k4y0z[/MENTION], [MENTION=295159]xyz[/MENTION], [MENTION=8132642]diplomatic[/MENTION] and [MENTION=10911591]deverro[/MENTION], the latter for this post that explained it all so I could understand:

Cheers!

Linus X.
[Fire HD 8 and HD 10 Original Android Development] silencery:
Anyone tried this with the latest fireos 5.6.7.0?
[Fire HD 8 and HD 10 Original Android Development] finwefeanor:
I did it with 5.6.6.0 it was the latest 1 2 weeks ago.
[Fire HD 8 and HD 10 Original Android Development] silencery:
thx for the reply. Yes, i'm on 5.6.6.0 now and the unlock is working great. I'm actually quite happy with the tablet on stock firmware (but rooted and debloated).

5.6.7.0 was just released, and it's a major update from android 5 to android 7.1. Pretty exciting for me since many apps I'd like to install or sideload don't even work on 5 anymore.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
ohhh thank you very very much that is very kind from you.

that is mean when i start this method for 32GB must save gpt in new folder and 16GB in other folder??
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I am changing the scripts, so it will use the devices serial-number for the gpt-folder so another mixup won't happen again.

Just give me a moment.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I have uploaded a new version:

Changelog

Version 1.1 (02.09.2019)

Add system_image to TWRP

Add serialno to GPT-folder to avoid mixups between 16G and 32G

Add scripts to fix GPT

[MENTION=7001753]deathlessster[/MENTION]

To fix your device download amonet-douglas-v1.1.zip and amonet-douglas-gptfix.zip.

Extract both into the same directory.

Then run

sudo ./gpt-fix-16G.sh
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
Thank you too much my friend i will test it soon as possible

Good Night
[Fire HD 8 and HD 10 Original Android Development] Axecaster:
Is it important for 32gb devices to update amonet from 1.0 to 1.1?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
The only difference is the support of sytem_image backup/restore in TWRP.

Update can be done by flashing the ZIP in TWRP.
[Fire HD 8 and HD 10 Original Android Development] Axecaster:
Is there an obvious way to know what version amonet was used on a device?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Well, there is only 2 versions currently for douglas:
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You need to run

sudo ./fastboot-step.sh

after running the gpt-fix.

Or if you can still boot your system, just run

sudo ./step-2.sh

When flashing boot.img via fastboot make sure to flash it to boot_x not to boot.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
thanks my friend i send stock recovery.img by dd command and now i get stock recovery but i flash boot.img to boot i will try to flash it to boot_x and try to get twrp by step-2 thanks again
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I am not following you. Why do you flash stock recovery?

Just use TWRP to do everything you need.

Don't ever flash to boot or recovery using fastboot as it will overwrite the exploit.

This is all mentioned in the OP
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
Ok i flash stock recovery because i can not get twrp by step-2 may be i do some wrong steps i will try again thank you for your time
[Fire HD 8 and HD 10 Original Android Development] t0x1cSH:
turns out that there was a problem with ours build,

revert back to Fire OS is completely harmless and won't break your TWRP installation or any future rom you want to install.

using the [MENTION=7104332]k4y0z[/MENTION] unlock method is the safest way to do any modification or restore the tablet.

about the "rare partition", my tablet had the corrupted gpt way before the unlock so i'm 100% shure that the unlock procedure is safe and with it you can fix your hd8 2017 gpt if you have a similar problem
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
So I'll ask again, can you still boot FireOS?

If so, what happens when you run step-2.sh?

If you can't boot FireOS can you still boot hacked fastboot?

If so, what happens when you run fastboot-step.sh?
[Fire HD 8 and HD 10 Original Android Development] Axecaster:
In the case of multiples of the same or different model fire tablets.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Well, no obvious way.

Check the changelogs.

My versioning scheme typically consists of x.y.z

Where a change in x would indicate changes to the exploit itself (lk-payload).

A change in y would indicate an update to TWRP (or possibly PL/TZ).

A change in z would indicate changes only in the scripts/installation procedure.
[Fire HD 8 and HD 10 Original Android Development] deathlessster:
now i thing i get big problem when i use the gpt fix command and the last line say reboot to unlocked fastboot my device boot to amazon logo without hacked BL and go to bootloop

about first time when i fix my device and i boot to fireos successfully after flash boot.img to boot not to boot_x .

when i try to use step-1 to get twrp i get error that i send it before and i try to use step-2 same error coming

that is all

Note: the gpt fix command now not work without sort to tp28
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Why are you even running the gpt-fix again? Your gpt was already fixed.

It's normal that you have to short TP28 because the preloader isn't bricked.

Please describe exactly what state your device is currently in?

What happens when you boot normally?

What happens when you try to boot recovery via the volume-buttons?

In any case you should be able to unbrick by shorting TP28 and running

sudo ./bootrom-step.sh

If you get any errors, you will need to post the output of the scripts, otherwise I can't help you.
[Fire HD 8 and HD 10 Original Android Development] Axecaster:
Does anyone have a link for a stock douglas 5.6.4.0? Current version is 5.6.0.1, but fp indicates 5.6.4.0+ to safely return to stock rom/recovery. What steps to take to properly TWRP flash a fresh stock 5.6.0.1, but keep TWRP unlock intact?
[Fire HD 8 and HD 10 Original Android Development] jakezpeenz:
Hi,

I followed these steps and everything worked well. I currently have TWRP installed. My problem comes in when I try to install lineage-12.1-20200614-UNOFFICIAL-douglas.zip (or anything else from zip.

Anything I try to install fails with exactly the same error - see attached photo.

When rebooting, I just get the white Amazon logo. I've even opened the device to short TP28 and start again with sudo ./bootrom-step.sh and then sudo ./fastboot-step.sh, which worked. But I still end up in TWRP with no way to install anything.

Any advice or suggestions?

Thanks
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
Nice!

Hopefully, the new Fireos release will provide some of the missing bits and pieces needed to get a newer version of Lineage going. :)
[Fire HD 8 and HD 10 Original Android Development] FatalDiskError:
Just a little issue in understanding the right thing

Hi @ll,

in Deverros post he mentioned:

I am stuck with "-allow modifications". What does that mean? I am not able to find such a setting in TWRP.

Can anyone help me understanding? Thanks in advance!

Ben
[Fire HD 8 and HD 10 Original Android Development] FatalDiskError:
I am not sure but can you check the partitions again? I followed the instructions step by step - including the brick 'cause of a higher fireos-version and all went fine.

In TWRP go to "wipe" , then "advanced wipe", then "repair or change file system". You have to select each partition by its own, does not work with all three together. Just check if they are all on "ext4" under "change file system". Do this for data, system and cache. After that mark all three and wipe them again.

And make sure that your system is not read only.

Just guessing, but maybe it helps...
[Fire HD 8 and HD 10 Original Android Development] Eisbaer2:
I tried to root the Fire HD 8 (2017) from my daughter as described in #1.

I have the newest firmware and understood that will work too - I only have to brick the tablet.

Unfortunately after the step "sudo ./bootrom-step-minimal.sh" the tablet is stuck in a bootloop (Amazon logo, reboot, Amazon logo,...). I found no possibility to stop it or get in recovery so far (tried shut down, and then holding Vol+ and Power On several times).

Anyone knows any help?

Thanks in advance!
[Fire HD 8 and HD 10 Original Android Development] FatalDiskError:
First of all you should follow #524 (page 53) from Deverros. It is quoted several times already and he also made my story a success.

did you have had success with the brick.sh or did you had to use brick-9820.sh? If it is the second script, you need to notice the warning: only use bootrom-step-minimal.sh if brick.sh worked, use bootrom-step.sh if you had to use brick-9820.sh.

If you can clarify this, that might be a good starting point to help.
[Fire HD 8 and HD 10 Original Android Development] Eisbaer2:
Thanks for your reply. In fact I follow post #524 because I remember having problems with #1

Here is my terminal history:

1 sudo apt update

2 sudo add-apt-repository universe

3 sudo apt install python3 python3-serial adb fastboot dos2unix

4 sudo ./step-1.sh

5 sudo systemctl stop ModemManager

6 sudo systemctl disable ModemManager

7 adb devices

8 adb reboot bootloader

9 sudo ./brick.sh

10 adb reboot bootloader

11 sudo ./brick-9820.sh

12 sudo ./bootrom-step.sh

13 sudo ./bootrom-step-minimal.sh

14 sudo ./fastboot-step.sh

I remember using brick.sh didn't work, brick-9820 did. Maybe using "bootrom-step-minimal.sh" after using "brick-9820.sh" was the problem? I haven't noticed the warning in #524 (it isn't there, only at #1).

Is there any solution to exit the bootloop?
[Fire HD 8 and HD 10 Original Android Development] TiklMiPickles:
I did the same thing and just managed to fix it on mine. It does require taking the back off and removing some screws/ribbon cables but is still quite easy. First you have to take the back off (any guitar pick or credit card should be able to do this easily) just start at the bottom and work your way around. Next you need to take the camera off the top left (should come right off when you take the tape off) and remove the 4 screws across the top. Once you have done that, unplug the battery in the bottom right (just pops off), the lcd ribbon cable on the bottom left and the touch screen ribbon cable at the top (be very careful with these, the top ribbon cable is to the left of the black square). Once you do that, take an exacto knife or something similarly thin and remove the ribbon cable from the top. Once that is done, you can pry the board up (lots of glue). Once that is done, go ahead and run the sudo ./bootrom-step.sh and plug the device in. Next you need to short the TP28 test point (just used a plain wire and connected it to the USB plug) and once that happens the script will tell you to remove the short, so do that and then press enter. Now you should be able to reassemble and continue after the bootrom step.
[Fire HD 8 and HD 10 Original Android Development] Eisbaer2:
Thanks a lot! I will try that tomorrow.
[Fire HD 8 and HD 10 Original Android Development] jakezpeenz:
Thanks for the response. I managed to get it sorted out. I ended up using the contents of the return-to-stock.sh script (just executing it did not work) to unpatch GPT and flash Amazon Recovery to get me back to stock. Then I ran through the process again, successfully installing LineageOS. I did however skip the 'advanced wipe' instructions. Just doing a normal wipe was sufficient in my case.

So, after a few hours of messing around, I have a 'brand new' tablet for my son. Family link enabled, all his favourite games installed and YT Kids for his favourite videos. And the device is so much faster and smoother. Really feels like a brand new device.
[Fire HD 8 and HD 10 Original Android Development] Eisbaer2:
Just tried:

1) Reassembled the board

2) started sudo ./bootrom-step.sh

3) pluged the Fired HD in

4) Terminal:

sudo ./bootrom-step.sh

[2020-08-26 06:55:25.974442] Waiting for bootrom

=> plugged Fire HD in

[2020-08-26 06:55:31.795448] Found port = /dev/ttyACM0

[2020-08-26 06:55:31.834992] 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 "/media/xubuntu/E2C8C869C8C83D93/temp/d/modules/load_payload.py", line 123, in load_payload

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

File "/media/xubuntu/E2C8C869C8C83D93/temp/d/modules/common.py", line 163, in write32

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

File "/media/xubuntu/E2C8C869C8C83D93/temp/d/modules/common.py", line 90, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

That happens before I'm able to shorten TP28 :(

What can I do?
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
You have to apply the short before connecting the USB lead. For example, plug the micro end of the USB cable to the tablet, short the test point, run the 'bootrom-step' script and plug the other end of the USB cable into the PC. When you get the 'press enter' message on screen (may take a few goes) remove the short and press enter.
[Fire HD 8 and HD 10 Original Android Development] melvinaury:
Does this method work with the Tab already updated to latest OTA from last week?
[Fire HD 8 and HD 10 Original Android Development] Eisbaer2:
Thanks a lot! Worked :)
[Fire HD 8 and HD 10 Original Android Development] dankcuddlybear:
I managed to brick my HD 8 7th gen (32GB model). I’m using Ubuntu 18.05 LTS, I installed the required packages and enabled ADB on my device. I tried to run step1.sh but it said “firmware not supported” (even though I have fire OS 5.3.x.x). I tried both 64 bit and 32 bit mtksu binaries. So then I tried the downgrade steps by running brick.sh and rebooted my device. No change. I then tried brick-9820.sh and rebooted. Still no change. I then realised you had to unplug the micro USB cable after typing “YES” so I ran brick-9820.sh and unplugged the cable, then rebooted. Now my device has been bricked. I tried running both bootrom-step.sh and then bootrom-step-minimal.sh but both scripts gave me a “serial error” exception or something like that.

So now I’m basically f*cked! Does anyone know how to fix this? Do I need to open my device and flash an image to the chip, or can this be done via USB? I do hope to complete the unlocking process or if I can’t, revert back to stock.

BTW, after bricking it I tried to disconnect the battery and reconnect it (wanted to make sure it was powered off completely so I could try and run the exploit again). I ended up stabbing the battery by accident (it didn’t explode or catch fire, just a few sparks and a wisp of smoke). Lesson learned: don’t use metal tools around the battery. I managed to remove the battery but until I can order a replacement I can’t do anything.
[Fire HD 8 and HD 10 Original Android Development] nindustrial:
I can confirm this works for 5.6.7.0 as well (for me using the brick-9820 script)
[Fire HD 8 and HD 10 Original Android Development] Eisbaer2:
Are you able to update the Amazon Prime Video App so you get a newer version with profiles?
[Fire HD 8 and HD 10 Original Android Development] nindustrial:
After unlock/TWRP I installed the CM rom and yes - was able to install the new Prime Video app (with working profiles) from the Google Play Store.
[Fire HD 8 and HD 10 Original Android Development] jesuse1990:
Need help

I have a 2017 gen 7 8 HD tablet on 5.3.6.4 using linux on virtualbox and I have tried to temp root then i got supersu with the automatic loader and i get stuck on sudo ./step-1.sh
[Fire HD 8 and HD 10 Original Android Development] jesuse1990:
Update

GOT IT !! now i installed Gapps for 5.1.1 and the google app store crashing when I try using it.
[Fire HD 8 and HD 10 Original Android Development] compromyse:
help!

i am using a raspberry pi.. and i am getting the error- ./brick-9820.sh: line 18: bin/fastboot32: cannot execute binary file: Exec format error:confused::confused::(:(
[Fire HD 8 and HD 10 Original Android Development] coboye:
stuck after brick

after running ./brick.sh i'm stuck in:

sudo ./bootrom-step-minimal.sh
[2020-09-28 15:33:29.227628] Waiting for bootrom
[2020-09-28 15:34:03.383284] Found port = /dev/ttyACM0
[2020-09-28 15:34:03.383955] Handshake

Any suggestion?
[Fire HD 8 and HD 10 Original Android Development] Roman G:
Old Member

Hey guys I was pretty active back in the hero days and evo and what not.

Now I'm back and into home automation. Wanting to root and install a rom on my fire hd to run the house.

Can this be done without using a Linux system?
[Fire HD 8 and HD 10 Original Android Development] Ungaga:
Does anyone know what would cause hanging on transferring the brick.sh to the tablet? I get "Sending 'brick' (111616 KB)..." in the terminal. and "USB transferring" on the tablet. I left it for 30 minutes and tried the 9820 brick.sh as well.

I'm on Ubuntu 20.04 through VirtualBox. Running 5.6.7.0
[Fire HD 8 and HD 10 Original Android Development] compromyse:
dont use virtual box.. it has error for some reason.. use a bootable live usb
[Fire HD 8 and HD 10 Original Android Development] adahm:
I am not able to connect to my HD8 2017 even after turning on adb in developer Options. Is there something else I need to? I hear the chime on the fire when connecitng the USB cable, but no detection on the pc. I tried changing to PTP for usb connection as well and got nowhere.

My HD8 2018 has a USB debugging option and connects right away as soon as I connect it to the PC.
[Fire HD 8 and HD 10 Original Android Development] BruhIJustBrickedMyStuff:
Oh, No, I just perma-bricked it didn't I?

I went to the step where you soft brick the device and took the usb out of the tablet when it said to, then tried to type in the code, but took too long and now it wont turn on, into recovery, or anything

here is the code before disaster.

sudo ./brick-9820.sh

Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)

YES

Bricking PL Header

Check instructions on device

target reported max download size of 114294784 bytes

Sending 'brick' (111616 KB)...

OKAY [ 3.561s]

Writing 'brick'...

FAILED (status read failed (No such device))

Finished. Total time: 34.677s
[Fire HD 8 and HD 10 Original Android Development] NTGDeveloper:
Shouldn't be a huge deal. Just did two devices today and was able to do bootrom-step.sh right after the failure and everything worked as expected.

Hope this helps!
[Fire HD 8 and HD 10 Original Android Development] BruhIJustBrickedMyStuff:
Hey! Holy crap, i pressed volume down and power and ran the thing!

Holy crap thanks dude i would give you a hug if it wasn't the time of corona, it worked!

---------- Post added at 01:31 AM ---------- Previous post was at 01:12 AM ----------

Do sudo apt update and it may fix it, I want to get a raspberry pi to do stuff like this too, but don't have one. Then in your file manager find where that file is and see if re-downloading the .zip 1.2 package and packing it to the same place helps. You may not have navigated to your right directory, type

cd

and then drag n drop the extracted file into the terminal, press enter and your name@name should also have

name@name ~/amonet

or

name@name~/whateverthefilewhichcontainsyourneededfiles

If using the hd8 2018, follow the guide by xyz`, I forgot the link and i cannot seem to find it again so you will have to find it by yourself. Everything is dependent on your version and year of fire, so keep looking around, you WILL eventually find something. If I find the link again I will reply it to you.

---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
[Fire HD 8 and HD 10 Original Android Development] z28james:
You're trying to run an x86 binary on an arm based processor. Probably what works would be to just install fastboot on the pi so that you have the arm version and then edit line 18 to point to it and see if that helps.
[Fire HD 8 and HD 10 Original Android Development] faekplastik3s:
Hello everyone, need a little help here.

I've got a Fire HD 8 here, no idea about its history or firmware version, but when it came into my hands it was stuck on a hard reboot loop into the Amazon logo, I couldn't get into recovery, it didn't charge, and there was no ADB enabled.

So I used the TP28 bridge to start this process following the guide, and it all seemed to go well, got the hacked fastboot going. The problem is after running fastboot-step.sh and getting the message that it should reboot into TWRP, it never gets there. At boot, the Amazon logo shows up and there is text saying "Recovery Mode...", but it just does that for a while and then reboots into the regular Amazon logo. Same thing happens if I do Vol Up+Power. I tried running the brick.sh script and starting over from there, but the same thing happens. Can anyone help me out? I have no idea what to do next.
[Fire HD 8 and HD 10 Original Android Development] digidude512:
Well I messed up and tried another TWRP but it didn't show any partitions.

I tried flashing the original again with Flashify and now I can't get into recovery.

Any advice on what to do?
[Fire HD 8 and HD 10 Original Android Development] meohmy:
I have followed the instructions to root my 2017 FireHD as far as reboot to bootloader, but when running either of commands sudo ./brick-9820.sh or sudo ./brick.sh I get the command not found message.

As both amonet-douglas-v1.2.zip and brick-douglas.zip have the same folder name when extracted, I first run the commands from the amonet douglas folder then opened a new terminal in the brick douglas folder and had the command not found message so copied all the files into the amonet 1.2 folder with the same result. I have tried running the command in a usb live installation of of Linux Mint and Ubuntu and results are the same, I can't get passed the reboot to bootloader.

I am obviously making a simple mistake somewhere but don't know where, can anyone give me advice please?