yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
fastboot reboot should not have even worked if brick went through.

What did the device display after running brick?

You need to make sure the device is powered off (Try holding the power button for 30 seconds).

Do you get anything displayed currently or does you display stay dark?

Check with lsusb or dmesg that the device you see is:

Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone

and not

Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

Also make sure you have ModemManager disabled:

sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
[Fire HD 8 and HD 10 Original Android Development] layjn:
It does show the MT65xx Preloader when I check dmesg, so it's not getting past preloader as you assumed. The device is currently in a bootloop at the Amazon logo. ModemManager has been disabled. After I ran the 9820 brick, the device displayed what I thought was the "successful" message so I think I (I have a terrible memory and this was yesterday) unplugged the and tried to move on to the bootrom step. I must have misread the tablet after the brick ran and pulled the plug too quickly so the brick never completed and now I'm stuck on the preloader with my bootloop. I'll give the HW steps a go later this week - I appreciate the help.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If it shows MT65xx Preloader, then brick definitely didn't go through, since all it does is wipe preloader.

If it still displays the amazon-logo, that's another good sign that brick didn't go through.

Not sure how you ended up in that bootloop, either recovery or normal boot should still work.

If you cannot access recovery, fireos or fastboot mode then you will have to use the hardware method.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Hey [MENTION=7104332]k4y0z[/MENTION], hoping you can shed some light on this issue.

The thing is I can no longer install gapps pico due to "Insufficient storage available in System partition."

I read that 16GB Kindle's have this issue, but I'm on 32GB so I'm wondering is something has gone funny with my partitions due to some flashing?

Has TWRP somehow modified my partitions to look like a 16GB device?

This is what has happened:

- I initially unlocked my device which was running 8520 with your OP. This went fine. I rooted with Magisk, disabled some packages (pm disable), installed some apps, including manually install Play Store and the supporting GSF/Account apps. I then decided to install via gapps instead so I manually removed the Google Apps I put on and then flashed gapps pico from TWRP without issue.

- HOWEVER, since then I have been experimenting upgrading from 8520, both to 8720 and 9820. I have copies of the full bin update files and am able to flash these via TWRP. I wanted to have a completely clean 9820 install so I flashed this after a wipe, but when I tried to install gapps I am getting this issue with space. I have gone ahead an totally wiped again and gone back to 8520, but I continue to get this error when I try to install gapps.

This doesn't make much sense to me because I was able to install gapps on 8520 after unlocking initially, but after flashing with TWRP it seems I am unable to.

Please let me know what data I can give you that might help answer what is now wrong. I have upped the gapps installer log here which has some info regarding the space.

Thanks!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
TWRP doesn't change anything about the partitions.

Also the system partition is the same size on 16 and 32G version.

Just userdata is smaller on 16G.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Well, do you have any idea of an explanation?

With 8520 installed prior to me doing any additional update or changes (short of installing your unlocker), the gapps-pico install worked.

But, once I upgraded past 8520, even if I go back and flash the 8520 ROM, the gapps-pico app will fail to install due to insufficient space.

I am 100% sure I am using the same gapps installer both times as well, so no other variables have changed.

Can you think of anything that post-8520 might have done to alter the available space even when re-flashing 8520 again?

This makes no sense to me.

Thanks.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I have no idea, make sure to wipe system before trying.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Yup, been wiping it all. Really strange...maybe I'll start a new thread in the main Fire HD thread to see if anyone else has any experience with the gapps installs.

Thanks for your time!
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
It seems it's worth a shot to try to grab the Fire in the fastboot mode, kind of how I did it when it was bootlooping with Amazon logo. See this and a few posts up and down:

https://xdaforums.com/showpost.php?p=80217872&postcount=34
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If I'm not mistaken, the douglas doesn't fallback to fastboot, like the karnak does, if it can't load boot/recovery.

It's worth a shot though.
[Fire HD 8 and HD 10 Original Android Development] layjn:
I'll give this a shot and report back - thanks!
[Fire HD 8 and HD 10 Original Android Development] OnoSendi:
What are the full instructions for the brick-douglas method? I can't get past mtk-su, I'm getting 'critical init step 4' error.
[Fire HD 8 and HD 10 Original Android Development] vendo:
here is what I did and it worked on 16 and 32

1. Install Lineage 12 from TWRP

1.1 Wipe Galwick and Cache

2. boot into Lineage 12 and go through the setup

3. restart to TWRP

4. install nano GAPPs and Magisk.

4.1 wipe Galwick and Cache

5. boot and finish Google Apps setup.

good luck.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
You are likely to have version 636559820, the latest version. In this case mtk-su does not work. You need to use brick-9820.sh, a different approach from the opening page. Dear OP, it is the time rewrite the first page for 9820 users. Otherwise, you need to answer to the same question again and again.
[Fire HD 8 and HD 10 Original Android Development] TraderJack:
Thanks, that's not really an answer/solution - I'm not looking to run Lineage until the fix the headphone issue.

For now I've just gone ahead and removed some non critical system apps to free up space and can install.
[Fire HD 8 and HD 10 Original Android Development] OnoSendi:
I got that far, that brick-9820.sh may be the solution, but I couldn't find any step by step instructions using this method. I thought I read through all the comments, and couldn't find anything.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Okay then briefly. You seem tried brick-9820.sh. What happened then? What I did is apply in fastboot mode (after you issue adb reboot bootloader), sudo ./brick-9820.sh. Then on the tablet screen there will appear three small letter lines. If you find unplug adb cable, power off, then you are done. Whatever PC screen says, FAIL or something, you are succeeded. Then just follow the innstruction, unplug the USB cable and power off the tablet (by pressing the PWR botton nearly 30 secs). Then, you should NOT power ON the device. Your tablet is now bricked. After this point you can follow the HW method (bootrom-step.sh and boot-fastboot.sh). When you brick your tablet it is equal to the state in HW method, short the test point. Before you start you should read the HW method. And correct all shells requied in one Folder (amonet). Good luck.
[Fire HD 8 and HD 10 Original Android Development] OnoSendi:
"should NOT power on device. Follow HW method (bootrom-step.sh and boot-fastboot.sh)" - How do you apply *.sh if I'm not supposed to power on the device? Regardless, when I:

$ adb reboot bootloader

$ fastboot flash brick bin/brick-9820.img

I get:

Invalid sparse file format at header magic

Sending sparse 'brick' 1/1 (12 KB) OKAY [ 0.019s]

Writing 'brick' FAILED (remote: 'the command you input is restricted on locked hw')

fastboot: error: Command failed
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
There is a reason the ZIP includes a fastboot-binary...

Just use the script that is contained.
[Fire HD 8 and HD 10 Original Android Development] OnoSendi:
Ah, the binary it came with wasn't working either because I'm in zsh or on a mac. I ran it in Ubuntu and it worked. However, now the device is dead, and won't turn on.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Well duh, that's the point of it.

Did you read what [MENTION=8964576]Korin67[/MENTION] wrote?

Allthough it should be fastboot-step.sh instead of boot-fastboot.sh.
[Fire HD 8 and HD 10 Original Android Development] OnoSendi:
I did, and tried ./fastboot-step.sh. It says "Waiting for device"

fastboot devices shows nothing. I'm confused how you fastboot to a device that is off?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Well, did you run bootrom-step.sh first, as he also mentioned?
[Fire HD 8 and HD 10 Original Android Development] OnoSendi:
I got Lineage installed. When I intalled GApps it broke everything. Maybe I installed the wrong one? I installed the 5.1.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I came back a little bit late, it is early morning in my time zone. The step I wrote is to introduce TWRP. It seems you already installed LOS, you successfully install TWRP, is this correct? If this is the case, the story has finished. The correct sequence after you have installed is:

Reboot FireOS from TWRP.

Backup your FireOS with TWRP.

Format, wipe cache etc. (as written in LOS12.1 thread).

Install LOS.zip,

Optionally Install gapps (arm64),

Optionally Install Magisk.

Then reboot.

Did you do that?

Edit: version 5.1 is correct.
[Fire HD 8 and HD 10 Original Android Development] XDA_h3n:
Like [MENTION=5823499]layjn[/MENTION], my device also got bricked like this following your guide for the update firmware brick.

Definitely got the successful message on the fastboot and then unplugged as it said and replugged and it won't boot into fastboot. It get stuck on amazon white splash screen and none of the former commands work.

bootrom-step.sh did work but stuck on this white amazon preloader mode bootloop.

Trying to boot recovery or fastboot doesn't work either :/ Preloader is the only thing which gets detected.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I'm not following you, either brick.sh didn't work, then bootrom-step.sh could not have worked.

Or it worked and would have displayed so on the device.

If it worked, are you sure you ran bootrom-step.sh and not bootrom-step-minimal.sh?

What output did you get?
[Fire HD 8 and HD 10 Original Android Development] wessi86:
I've got the same problem, but I used "sudo ./bootrom-step-minimal.sh", because that's what is mentioned in the first post.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Using bootrom-step-minimal.sh does explain the issues described.

You should only use bootrom-step-minimal.sh when you bricked using step-1.sh.

If you used brick-9820.sh you need to use bootrom-step.sh as it also tells you on the display of the device after running it.
[Fire HD 8 and HD 10 Original Android Development] wessi86:
Yeah, that's what I did. I used brick-9820.sh, then bootrom-step-minimal.sh. I guess I didn't pay close enough attention and assumed the text appearing after the brick also says bootrom-step-minimal.sh as said in this guide. Even though it's my fault I think the guide needs some rework.

Anyway, is there a way to unbrick my tablet?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I'm sorry about that, the brick-9820.sh was only recently added and isn't yet part of the guide.

I will update the guide and make it more clear, when I get a chance.

In the meantime, if you cannot access fastboot, you can follow these instructions by [MENTION=541852]vendo[/MENTION] to unbrick.
[Fire HD 8 and HD 10 Original Android Development] wessi86:
All good. Thanks for your help and your guide in the first place :)
[Fire HD 8 and HD 10 Original Android Development] Colossus96:
Wait so fire hd 8 7th gen had twrp & los? Can anyone pls link me?
[Fire HD 8 and HD 10 Original Android Development] wessi86:
You can find everything you need in the master thread here: https://xdaforums.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
[Fire HD 8 and HD 10 Original Android Development] wessi86:
I managed to unbrick it with this method, thanks again!

Instead of a wire I used metal pliers and instead of plugging in the cable I used an USB hub with a switch so the process was really easy to do.
[Fire HD 8 and HD 10 Original Android Development] Colossus96:
okay i have a weird problem, i hope someone can help me. i have fire os 5.6.0.1. i was rooted with software method with supersu. i deleted a lot of system app to make the tab fast. now i had adb enabled before so no problem. after i ran step-1.sh my device got reset perfectly. but now after booting i can't enable dev option again as serial number is grayed out. i can't flash gpt either to flash the stock rom via sideload. will my tab brick if i flash stock fireos via sideload when step-1.sh was successfull?

edit: i can access stock recovery [MENTION=7104332]k4y0z[/MENTION] pls reply
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just flash stock ROM via amazon recovery.

Shouldn't cause any issues.

Just make sure not to use a version older than the one you have installed.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yes, you need to run step-2.sh
[Fire HD 8 and HD 10 Original Android Development] spinn9000:
HD 8 7th gen stuck in bricked state

Greetings all, have been following this thread since the instructions were given about rooting the hd 8.

I previously had root on it and lost it when it updated to 9820. I tried to downgrade by sideloading and

I bricked the tablet. Have been trying to unbrick by using the hardware method and I keep on getting

the serial protocol mismatch error when trying to run the bootrom-step.sh. I can tell that the tablet is stuck

in PL due to it showing up as a device in dmesg. Not really sure what to do now, I fear I have totally botched

this up. Any advice would be appreciated.

TIA
[Fire HD 8 and HD 10 Original Android Development] layjn:
After my tablet went to bootloop, I successfully performed the HW method per the post by [MENTION=541852]vendo[/MENTION] but my screen isn't turning on and didn't turn on at all during the procedure. Is there anything hardware-related that I should look for that would affect the display? I thought I did something wrong so I did the HW method again and got through the whole process successfully a second time, but still nothing on the display. Any ideas?
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I also had that problem. You should check LCD cable first. There is a possibility when you lift up the motherboard, the cable became loose. Actually I failed to do the HW method. How do you decide your HW method is successful? TWRP screen should be on the display, right? In my case, I failed to operate the HW method. The system returned to FireOS. I connected my tablet to PC. Luckily my tablet could be recognized as an ADB device. 'adb reboot' solved my problem.
[Fire HD 8 and HD 10 Original Android Development] layjn:
Looks like I was a little rough when I lifted the motherboard - the cable itself has a split in it, so now I'll be searching for a replacement cable online. Hopefully something is available.

As far as the HW method, there are prompts after each step about whether or not you succeeded. After you've run the bootrom and fastboot steps outlined in the guide, the device should reboot to TWRP. The terminal should also state that the procedure was successful and that the device will reboot into TWRP.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Hopefully you find substitute cable. In my case, cable connection was okay. The problem was that the tablet was in screensaver on. Usually, screensaver be disabled touching screen or PWR button. My case both did not work. Only 'adb reboot' could disable screensaver, the tablet shows when it rebooted. Anyway, next time you might avoid HW method. Using brick-9820.sh gives the same effect grounding the Test Point; you do not need to open the tablet. I was rescued by brick-9820.sh.
[Fire HD 8 and HD 10 Original Android Development] LanceLot9980:
Thanks a lot! I've been waiting for this for literally months
[Fire HD 8 and HD 10 Original Android Development] klister:
Layjn, did you break the LCD cable at the bottom of the board or the digitizer cable at the top? I have an extra LCD cable available.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Layjin is already in LOS12.1 thread, now he seems struggling install LOS. Anyway, it seems he already installed TWRP; he solved the cable problem somehow, I hope.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
It seems your case is the same as Layjn's. It is best he answer how he managed the problem. As I wrote I also tried the HW method (and failed). You seem successful with HW method. So I cannot comment correctly. What I can suggest is connect your tablet to PC (raspberry in your case?). Then type

adb devices. If you can see your tablet recognized as adb device, your tablet is ON, so you can issue

adb reboot

that should boot to FireOS. Or you can test

sudo fastboot devices

If your tablet appears as fastboot device, then you are in bootloader mode. You can try

sudo fastboot reboot

to go back to FireOS. If both of them does not work, your tablet is likely to be OFF. Press PWR button to turn it ON. If you did not damage LCD cable, you should see something on your display.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Comprueba el cable LCD;)

It can be the problem.

Regards.
[Fire HD 8 and HD 10 Original Android Development] Cobraroja:
Tablet not recognized after bootrom-step.sh

Hi, thanks for your guide and amazing work.

I'm having a problem that I'm not able to fix, I executed fine brick9820.sh and bootrom-step.sh, however hacked fastboot didn't come up, now I'm stuck without being able to turn on device (not show in adb devices nor adb fastboot devices) . I have tried using wired method unsuccessfully. lsusb doesn't show anything, and this is the output of dmesg: https://pastebin.com/vQ7AaNsk

Edit: Tried to connect device in windowd and got "Unknown USB Device (Device Descriptor Request Failed)".

Edit2: After restart, I tried to connect the usb in ubuntu again, I got this log from dmesg: https://pastebin.com/aRdMDeRZ

Edit3: Tested again the wired method without battery and worked, however the fastboot-step.sh is stuck on waiting for device.

Edit4: Entered recovery, sideloaded stock 636558520, executed step1.sh and step2.sh "successfully" , but now I'm in bootloop not able to enter recovery.
[Fire HD 8 and HD 10 Original Android Development] whodfkcares:
This time i connected it to my PC with Windows, to hear the sound when it is plugged on or 'unplugged'. I opened a CMD with the ADB files, and, for my surprise this appeared:

List of devices attached

G************** recovery

i run 'adb reboot' And heared that sound of 'unpluged' and re-pluged like it is rebooting. Now i run again ADB devices and only appears List of devices attached and nothing shows on.

And not justg only that, i can hear that sound of plugged and unplugged now, like, it is on a reboot loop.

The LCD cable is in the left under the battery, right? i didnt touch it, could be the other extreme disconnected?
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Definelety you LCD cable it's not correct connected. Yeah, check two extremes.
[Fire HD 8 and HD 10 Original Android Development] alivan:
fastboot low power

Hello, thank you very much for the guide. I followed the hardware method, since I bricked the devices previously by trying to downgrade. It is successfully loaded into the hacked fastboot (displays "...xyz, k4y0z...") but when I try to run the fastboot-step.sh getting the next error:

Your device will be reset to factory defaults...

Press Enter to Continue...

target reported max download size of 113246208 bytes

sending 'recovery_x' (13196 KB)...

FAILED (remote: low power, need battery charging.)

finished. total time: 0.006s

How can I fixed that? Now it is not charging when plugged in to the cable, nor to the computer, nor to the network. Thanks.
[Fire HD 8 and HD 10 Original Android Development] whodfkcares:
To see the other extreme, i have to remove the battery?
[Fire HD 8 and HD 10 Original Android Development] Korin67:
At least your tablet is NOT dead. It seems working. I do not know the problem is with LCD cable or not, you can try adb method. The tablet need quite some time before it actually boots. Leave your tablet a couple of minutes then plug the cable to connect with your PC. Try 'adb devices' or 'fastboot devices'. If your tablet does not recognized for both commands, your tablet is OFF. Press PWR button around 30 seconds and see what happens. If you see Amazon logo, you are done.

Edit: You also need to check buttery is charged enough or not. If not you need to charge before doing any experiment.
[Fire HD 8 and HD 10 Original Android Development] theOriginalSuperl2:
I'm on exactly 5.6.4.0. Do I do the downgrade?
[Fire HD 8 and HD 10 Original Android Development] Sjd08:
Had an un-loved Fire HD 8 7th edition on 5.6.4.0 build 636558720. Discovered this post, followed instructions in OP and it worked perfectly! Then installed lineage OS 12.1 Tablet now loved again by child and parent. So BIG thanks!!!
[Fire HD 8 and HD 10 Original Android Development] rootbeer007:
Hi, can someone give me the complete instruction for rooting the fire hd8 2017 Fire OS 5.6.4.0 - Version ... 820 . If possible a method without opening the tablet or maybe its only possible to do it the hardware way for my version of fireOS (...820) I need assistance before attempting to root it. Thanks in advance
[Fire HD 8 and HD 10 Original Android Development] dkthinh1:
:crying::crying: same here, I check this thread everyday, but it's still no hope. I tried bootrom-step.sh but nothing happened.
[Fire HD 8 and HD 10 Original Android Development] spinn9000:
Hello all,

I'm having an issue with the device such that it momentarily comes on as I try to execute the bootrom-step.sh (preloader) but then shuts off/disconnects such that the script finishes with the serial protocol mismatch error. The tablet is charged and again there is no display on at all (per what is mentioned in bricking) Is there someway to keep it in the preloader such that the script can execute? Does it possibly have anything to do with the shorting of TP28?

TIA
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If you are on the 9820 build, you can use the brick-douglas.zip from the OP to brick your device and then use the bootrom-step.sh

Preloader isn't the mode your device needs to be in for running bootrom-step.

If your device is currently bricked in preloader-mode you will have to open the device and short TP28.

Follow these instructions by [MENTION=541852]vendo[/MENTION]
[Fire HD 8 and HD 10 Original Android Development] spinn9000:
Thank you for your patience and guide!

I followed your instructions but I know I must have goofed something......
[Fire HD 8 and HD 10 Original Android Development] alivan:
Hello, is there any way to deal with low battery complain when trying to execute fastboot step in the hacked mode? Thanks.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I haven't seen that before, but I would say try to charge it.

Don't try to boot recovery before you ran the fastboot-step sucessfully, as that will reset the flag that tells it to boot into hacked fastboot.
[Fire HD 8 and HD 10 Original Android Development] Supersonic27543:
Just checking in here to update my master thread: what is the recommended way to unlock the updated devices? Reading through it looks like the temp brick one but would be great if someone could confirm. :)