yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Hello all,

I am not new in this thread. I have successfully unlocked two of my HD8's. I received third one and tried from ./brick-9820.sh. Yes, I could easily finish all the steps and saw TWRP screen on my HD8. Then, trouble starts. The TWRP is always readonly mode. Even if I allow modification, the TWRP starts next time with the same screen asking to make modification. So, fail to mount /cache, /data etc., I cannot install any ROM. When I tried lineage for douglas, TWRP says my system is 'ford', not douglas. It does not accept lineage for douglas. What's more, the system always reboot in recovery mode.

Any clue to solve this situation? Thank you.

Edit: After struggling a couple of hours, I could solve. I suspected that boot-step.sh was incomplete. So I repeat the whole step.

(1) From TWRP, boot to bootloder.

(2) Check with sudo fastboot devices, and run brick.sh (yes, in the second attempt brick-9820.sh did not work. Used brick.sh instead.

(3) run bootrom-step.sh and wait until HD8 reboot. To check reboot completed or not, run sudo fastboot devices.

(4) run fastboot-step.sh and then Surprisingly, FireOS booted.

(5) Turn off FireOS and boot with pressing VOL down(Leftmost key)+PWR. When I see amazon logo, release both keys.

TWRP activated and after that everything went well. Now I have LOS14.1 in my tablet.

My situation might be special, but may happen someone else. Enjoy your HD8 everybody.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
What happens if you do: sudo sh brick.sh ?
[Fire HD 8 and HD 10 Original Android Development] meohmy:
[MENTION=8964576]Korin67[/MENTION]

Thanks for the reply I was following instructions and running sudo ./brick.sh & sudo ./brick-9820.sh in both cases the reply was command not found.

I ran the sudo sh brick.sh command you suggested and the reply was Brick preloader to continue via bootrom exploit - I answered yes and turned the tablet off

I then ran the bootrom-step.sh command and the reply was command not found

The tablet is currently switched off as per the instruction.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
The reason why system says 'command not found' even if the command is actually there is: the command you try to run is not excecutable. To solve this situation there are two ways: as I first suggested you use 'sh' to run the command, or make the command executable. To change the command executable is to use chmod 777 (the target command). This time you can try 'chmod 777 bootrom-step.sh' and then 'sudo ./bootrom-step.sh'. Or you can do again 'sudo sh bootrom-step.sh'. It is all up to you.
[Fire HD 8 and HD 10 Original Android Development] meohmy:
After many days of trying I finally succeeded in completing the task although I did have a few problems that I needed to sort through.

The biggest problem was my usb cable not being original but I finally found a Belkin cable that worked.

Second problem was nothing would work of a live linux usb installation and I tried the latest versions of Ubuntu, Linux Mint and ElementaryOS. I eventually did a Linux Mint install on a spare HDD

Third problem was ME, being a Windows user since Win3.1 I was used to typing y for yes or typing yes without the need for using capitals.

Eventually worked it through and having now lost all my hair through frustration I now have a working tablet with Lineage installed.

Thanks to Korin67 for the prompts and all the people who have contributed to the information contained, I suppose I also need to thank the wife for the endless coffee and chocolate biscuits
[Fire HD 8 and HD 10 Original Android Development] opec:
My FireHD 8 (2017 7.Gen) is running FireOS 5.6.8.0 (659655920).

If i follow the instruction on page one i get:

Trying to use mtk-su to get temp root...
Pushing root files
bin/mtk-su: 1 file pushed. 4.5 MB/s (65144 bytes in 0.014s)
bin/minisu.img: 1 file pushed. 3.8 MB/s (1048576 bytes in 0.264s)
bin/busybox: 1 file pushed. 3.4 MB/s (587368 bytes in 0.164s)
Failed critical init step 4
This firmware cannot be supported
Failed critical init step 4
This firmware cannot be supported
Failed critical init step 4

Is there a trick to get arround this? The instruction says for FireOS newer 6.5.4.0 the Tab needs to be temporary bricked, however if i try the bricking method i get:

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

< waiting for any device >
target reported max download size of 114294784 bytes
Sending 'brick' (112090 KB)...
FAILED (data write failure (Protocol error))
Finished. Total time: 64.421s

I guess because root from step one is missing?

What are my options? Will the Hardware (GND <> CLK) method still work for my FireOS ? Any way to downgrade FireOS to 6.5.4.0 ?

Greetz

Roque
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I have never tried mtk-su. I have successfully unlock three douglas'es so far. Every time I used brick-9820.sh to brick douglas. Have you tired it?
[Fire HD 8 and HD 10 Original Android Development] opec:
Hi , funny think i experimented a bit , with the brick-9820.sh i manged to see the Hacked fastboot message already, but however when the tablet started it asked me for the pin (wich i dissabled earlier today before i started, and also did factory reset and wipe cache partitioin). After entering the pin it told me the pin is correct however my data is corrupted and the device needs to be reset , i only coudl choose reset, after the reset the hacked fastboot was gone again. So i retried but this time i wasnt luck with the brick-9820 anymore. SO i retried several tiems and then was lucky with the regular brick.sh.

I also noticed , that after the bootrom-step.sh it says it should reboot to Hacked Fastboot wich however it didnt do, i gues maybe the screen was still not wokring, so instead manually goign to fastboot i directly fired "fastboot-step.sh" after bootrom-step was finished.

After that the FireHD booted to TWRP. In the frist post it recommends flashign magisk through TWRP , is this needed ? I want to change to LIneage OS.

greetz

opec
[Fire HD 8 and HD 10 Original Android Development] Korin67:
So you are now successfully installed TWRP, right? Then the game is over. You can now do anything you like. What I did first is backup FireHD in TWRP so that you can come back to FireHD anytime you want. Magisk is very optional. You can safely wipe FireHD because it should be already backupped. You might 1st install LOS12.1 (or LOS14.1), then reboot to system. You can check how LOS works. If you feel good impression go to TWRP and install gapps (I prefer to BitGapps now), and then if you want install Magisk. This is the usual sequence after you have TWRP. You need not rush to Magisk.

Have fun.
[Fire HD 8 and HD 10 Original Android Development] willgaj:
Hi, I'm trying to root my Kindle Fire HD 8, Gen 7, 5.6.8.0 and when I try to brick the device for downgrading, the program stalls at . . .

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

YES

Bricking PL Header

Check instructions on device

<waiting for any device>

I have my device plugged in, with a cord capable of data transfer, and turned on. I recieve no message on the tablet. I'm currently running Ubuntu off of a USB if that makes a difference. Any suggestions? Thanks!
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Is your douglas in fastboot mode? I mean what PC says when you type sudo fastboot devices. Your device should be listed on PC screen. Which brick command do you use, brick.sh or brick-9820.sh ? Most likely it should be brick-9820.sh.
[Fire HD 8 and HD 10 Original Android Development] neniu nomo:
I'm looking forward for a video tutorial. It's would much easier to understand. Can anyone do it pls, thanks
[Fire HD 8 and HD 10 Original Android Development] VMGal:
@opec I was having the same issue as @willgaj with the same device and software, everything. The process you described was going smoothly until I tried to run ./bootrom-step.sh. At looked like it was going well, but it suddenly stopped at "Waiting for bootrom". I waited to see if anything would happen for over 5 minutes, but nothing changed. I tried both bootrom-step.sh and bootrom-step-minimal.sh, neither was any different from the other. Obviously it is bricked, so I cannot turn it on or do anything with the Kindle. How exactly can I fix this issue/is it even recoverable at this point?
[Fire HD 8 and HD 10 Original Android Development] Neo3D:
I don't understand the typing "YES" part? there isn't a step that results in the script asking a question that requires a YES answer? Am I missing something or are the instructions missing something?

Thank you!
[Fire HD 8 and HD 10 Original Android Development] Neo3D:
Wow, these steps are so much more detailed, THANK YOU!!
[Fire HD 8 and HD 10 Original Android Development] Neuken6969:
getting this error in my virtual linux im running .. any idea? or help fixing this would be great
[Fire HD 8 and HD 10 Original Android Development] Neuken6969:
AMAZING this walkthrough is flawless and worked perfectly. Hopefully somebody is still following this, is there a kernel or something to speed this little thing up?
[Fire HD 8 and HD 10 Original Android Development] VinceVega1978:
I can't get the brick working on my Fire HD 8 with 5.4.0.0 (is this version already the problem?)

I have tried it with live systems of ubuntu and linux mint on two different PC's.

Also tried different USB cables and ports (USB 2 and 3).

I mostly tried the instructions from

@deverro https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-8-2017-douglas.3962846/post-82921395

and

@opec https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-8-2017-douglas.3962846/post-84047455

The tablet is in Fastboot Mode, this is recognized from the linux terminal.

If i enter the "sudo ./brick.sh" command and continue with "YES", the tablet changes from "fastboot mode" to "USB Transfering...".

After about a minute the tablet display gets dark and restarts to the normal fire os.

The terminal says:

"target reported max download size of 114294784 bytes

Sending 'brick' (112090 KB)...

FAILED (data write failure (Protocol error))

Finished. Total time 61.933s"

If i use the "sudo ./brick-9820.sh" command, it looks a bit different.

The tablet changes from "fastboot mode" to "USB Transfering...".

And a few seconds later "USB Transmission OK Time 5029ms Vel: 22727KB/s"

But then nothing happens after that and also about a minute later the tablet display gets dark and restarts to the normal fire os too.

The terminal says:

"target reported max download size of 114294784 bytes

Sending 'brick' (111616 KB)...

OKAY [ 5.056s]

Writing 'brick'...

FAILED (status read failed (No such device))

Finished. Total time 661.913s"

Any help would be really appreciated.
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
An old version like 5.4.0.0 is vulnerable to MTK-SU. Don't use the brick scripts use the method that employs MTK-SU to get root privileges and then unlocks the tablet etc.
[Fire HD 8 and HD 10 Original Android Development] user5589:
I ended up in exactly the same situation as you. Can you still boot the device or get into fastboot mode? In my case, the screen stays black and I can't do anything. I can neither run 'brick-9820.sh' again nor 'bootrom-step.sh'.

I accidentally removed the CLK contact from the board before, but everything was working find with that. The build is or was above 'Fire OS 5.6.4.0 build 636558520 '.

Any idea? Any help is appreciated :)
[Fire HD 8 and HD 10 Original Android Development] IsolatePlz:
It's not running the script im running ubuntu on a VM and whenever it loads into fastboot it loses the connection to USB sudo ./brick-9820.sh does nothing and it sits on <waiting for any device> can you help
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
The way the USB device is presented to the VM causes confusion in the scripts.

There are lots of people who have trouble getting these scripts to work in a VM.

Did you try adding USB devices to the VM as noted in the post you quoted?

One of usual recommendations I see for this problem is to run a live Ubuntu session off of an USB stick. This will often present the USB device as expected by the scripts.
[Fire HD 8 and HD 10 Original Android Development] IsolatePlz:
"Did you try adding USB devices to the VM as noted in the post you quoted?" I've done that the VM has connection before I go into Fastboot but when i enter it i lose it
[Fire HD 8 and HD 10 Original Android Development] dink-x10:
Fastboot is a different device, you will need to add it to the VM again once in fastboot mode
[Fire HD 8 and HD 10 Original Android Development] IsolatePlz:
I didn't know that ill try it again
[Fire HD 8 and HD 10 Original Android Development] IsolatePlz:
Well I got a bit farther now its sitting at USB Transfering and the terminal isnt doing anything
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Also have a 7th gen running 5.6.8 so looking to downgrade it to 5.6.4.

Okay, installed Unbuntu and went to the folder that I saved brick-douglas in my Ubuntu terminal (i.e., went to /mnt/c/brick-douglas.

But when I type sudo ./brick.sh , I get:

sudo: ./brick.sh: command not found

So stuck at step 1!!

Thx!
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Just to be clear, here's what I did so far on my 7th gen with 5.6.8:

Installed Minimal ADB and Fastboot

Factory reset, then wiped cache

Went into Bootloaded mode (see fastboot bottom right of fire)

Note if I plug the FireHD8 into my PC, I hear the usb being recognized if that matters?

However, if I go into ADB and Fastboot, and type adb devices, nothing is recognized?

Question - should I have the FireHD8 plugged into my PC at this stage, and if so, should it be recognized by Fastboot?

Downloaded the brick-douglas and amonet-douglas and unzipped them into my main c: directory. Unpacked and copied MTK-su from the ARM64 Bit folder to the “bin” folders of brick-douglas and amonet-douglas.

Installed ubuntu v20.

Using Ubuntu, went to cd /mnt/c/brick-douglas

Entered the command sudo ./brick.sh, and get the error message above.

Note: Even though when I enter the ADB Fastloader and type "adb devices", while nothing shows up, I do see the Fire device listed in device manager under Fire Devices and a Android ADB Interface with no exclamation point.

If I type sudo fastboot devices in Ubuntu with my Fire HD8 connected, the command does nothing at all. Doesn't list any devices, simply shows the usual standard prompt.

user@DESKTOP-LH5CI1V:/mnt/c/brick-douglas$ sudo fastboot devices
user@DESKTOP-LH5CI1V:/mnt/c/brick-douglas$
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
I think where things are going wrong might be the step where it says to reset the FireHD 8 to factory resets, wipe the cache, and then enter bootloader mode. Doing so effectively turns off Developer Mode and ADB debugging, so the device can't be accessed or recognized by the PC it is connected to. Is that maybe the issue I am having here?
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Okay, well, that's not it either. Tried going into Developer mode, turning on ADB, the fire device is found by both my PC and a RPi3 that I figured I'd try to use instead of windows.

But again, once I power down and go into Bootloader mode (this time didn't do a factory reset), neither my windows 10 nor my RPi3 recognizes the Fire as attached via USB when it is in Bootloader mode.

Seriously, I must be doing something completely wrong here as this doesn't seem to want to work when in bootloader mode???
[Fire HD 8 and HD 10 Original Android Development] LarsVegas3012:
Hello,

I have a problem with my FireHD 8. I'm stuck in a boot loop after accidentally typing sudo ./bootrom-step-minimal.sh instead of sudo ./bootrom-step.sh.

Now I can no longer get into recovery mode. The buttons don't seem to be working.

Can someone help me out?
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Okay so thanks to @@k4y0z my original issue was that I needed to be using a USB Live installation of Linux. I tried Ubuntu but it was slow as molasses so switched to MXLive which is much quicker.

However, after following the instructions above to enter sudo ./brick.sh from a terminal opened in the brick folder ,I type "Yes" to do the brick exploit...and nothing happens. The device just sits with "FASTBOOT mode" at the bottom of the screen??

Also tried using the sudo ./brick-8920.sh command from the same folder, says command not found (odd as it's right in the folder).

Also tried the sudo systemctl stop ModemManager command, but get "System has not been booted with systemd as init system (PID 1). Can't operate.Failed to connect to bus: Host is down"

What am I missing that must be painfully obvious here??
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You probably unpacked the file on windows and it messed up the permissions.

Try running

sudo bash ./brick-9820.sh

or fix the permissions first:

chmod +x brick-9820.sh

These scripts may not work, depending on your firmware-version.

The instructions are for Debian and Ubuntu, I don't know what the equivalent for MXLive would be.
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
[/QUOTE]

[/QUOTE]

Switched back to Ubuntu, on a USB Live disk and rebooted the machine straight into Ubuntu.

Downloaded the files directly to the USB drive while in Ununtu so not using Windows.

Have opened a terminal in the Amonet directory of the "Brick-douglas" extracted contents after saving the 64 bit MTU file into the bin.

Sudu ./brick.sh does the same thing, which is it says "Brick preloader to continue via bootrom-exploit? (Type "Yes")" ...I type Yes, and nothing happens. Also tried "yes" just in case.

If I try sudo bash ./brick-8920.sh in the same directory, says "no such file or directory", and chmod +x brick-8920 says can not access ... no such file or directory.
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Also, if it matters, when I extract the files using ubuntu, I create a folder called "Brick" to extract the brick douglas one to (it then creates a folder called Amonet in there).

Do the same for the Amonet-douglas-v1.2 file, create a folder for that one to make sure I am keeping both separate (otherwise if I just say extract here both would go into the same "Amonet" folder and over write ****.
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
ubuntu@ubuntu:~/Downloads/Brick/brick-douglas/amonet$ sudo bash ./brick-9820.sh
bash: ./brick-9820.sh: No such file or directory
ubuntu@ubuntu:~/Downloads/Brick/brick-douglas/amonet$ ls -a
. .. bin brick-9820.sh brick.sh

So the file is defintely right there!
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If the USB is FAT formatted, that will also cause issues with permissions.

Best is to extract directly to the Desktop.

Not sure, what you mean by "64 bit MTU file"

It's brick-9820.sh of course (not brick-8920.sh)
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
ubuntu@ubuntu:~/Downloads/Brick/brick-douglas/amonet$ sudo bash ./brick-9820.sh
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
Yes

Same thing, nothing happens after the "yes".

I'm on 5.6.8, following this.... https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-8-2017-douglas.3962846/post-84047455
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Ubuntu tells me I don't have permissions to extract a file to the windows harddrive ("Read-only file system").
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I didn't say anything about your windows harddrive...

Is you device in fastboot mode?

Does it show up when you do

fastboot devices
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Sorry, what desktop did you mean here?

I.e., I'm running Ubuntu on a FAT32 formatted harddrive. I extracted the zip files to the "downloads" folder in Ubuntu (which presumably is on the usb drive??).

No fastboot doesn't detect the device when I follow these steps:

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

Select Facotry Reset then Wipe Cache

Reboot to Bootloader

Even if I reboot the device, turn on adb debugging, fastboot still won't recognize it (it does if i use windows though)

...and thank you btw! Been waiting a few years to get rid of the Fire OS and now it's driving me nuts that I can't get it to work!

ubuntu@ubuntu:~/Downloads/Brick/brick-douglas/amonet$ fastboot devices
no permissions (user in plugdev group; are your udev rules wrong?); see [http://developer.android.com/tools/device.html] fastboot
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Wait...if I reboot and put ADB Debugging as on, then enter bootloader/fastboot mode on the tablet I see the device (have to use sudo fastboot devices).

ubuntu@ubuntu:~/Downloads/Brick/brick-douglas/amonet$ sudo ./brick.sh
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
Yes
ubuntu@ubuntu:~/Downloads/Brick/brick-douglas/amonet$ sudo fastboot devices
G090ME0673XXXPDN fastboot
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Okay, not sure exactly why, but it's working now with the 9820 command. Fingers crossed.
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Hmmmm...well, maybe not. This is what it did:

But it didn't reboot into TWRP, or reboot at all. Powered it back on, and it's asking me for a PIN, and now saying Corrupt Encryption Factory reset required?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
It should have booted to "hacked fastboot" not TWRP.

If it didn't, turn the device off, then run

sudo bash boot-fastboot.sh

followed by

sudo bash fastboot-step.sh
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Perfect, in TWRP. Geez...lol..and to think I have one more of these! Huge thanks.
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Hmm.. Are there instructions on installing Magisk and a Rom?
[Fire HD 8 and HD 10 Original Android Development] kerazee:
You sir are a legend, thanks for the great instructions, rooted and installed without the need to crack open the case.
[Fire HD 8 and HD 10 Original Android Development] pbcsd:
Just trying to revert back to stock on one of my devices. Seem to just hang here at waiting for device?

ubuntu@ubuntu:~/Downloads/Amonet/amonet-douglas-v1.2/amonet$ fastboot flash recovery bin/recovery.img
< waiting for any device >

When I do a sudo fastboot devices, it identifies that my Fire is attached.
[Fire HD 8 and HD 10 Original Android Development] renatus_lupus:
I figured I'd explain what I had to do after spending all day trying to figure it out. If on Linux (I was using a VM), you had to put mtk-su in the bin folder, and running step-1.sh script throws repeated "cannot be supported" errors, you wanna unplug and power the tablet off, hold the left volume key and the power button, let go of only the power button when the Amazon logo shows, and enter bootloader mode. While your Linux install or VM has the tablet in bootloader mode docked, run the ModemManager commands, the brick script (I had to use brick-9820, so mind the red text warning in the OP), then after unplugging and rebooting when the tablet prompts to do so (after saying it's been "Pwned!" by k4y0z), run the bootrom-step script and then the fastboot-step script, and it eventually went into TWRP for me.

I was having issues pushing .zips for Lineage OS and GApps to my device through my Linux VM, so what I did was I plugged the device into my host Windows 10, installed ADB tools on Windows 10, opened PowerShell, changed to the directory where those zip files were ("cd X:\Downloads" in my case), then "adb push .\[zip file name] /sdcard". The file names are long, so the tab key can complete the file name in the command after you type the first few letters of it. Hope this helps someone!
[Fire HD 8 and HD 10 Original Android Development] landmerk7:
does this method still work for the newest version (5.6.8.0)?