yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] IsolatePlz:
I need help I'm stuck at "USB Transferring..." on my device and "Sending 'brick'" on my Virtual Machine. I'm using Ubuntu on Virtual Box I don't think the Virtual Machine is the problem because this has worked for people in the past.
[Fire HD 8 and HD 10 Original Android Development] renatus_lupus:
I can't vouch for that version personally, my device was 5.3.X.X when I did it
[Fire HD 8 and HD 10 Original Android Development] 12o0n3y:
How did you attached USB to linux? I am using windows 10 with wsl + Ubuntu. Thanks!
[Fire HD 8 and HD 10 Original Android Development] pokemon81:
*del*

wrong Thread
[Fire HD 8 and HD 10 Original Android Development] renatus_lupus:
Are you on a virtual machine? If you're using Oracle VM VirtualBox, as long as the device is plugged into your PC before starting the VM, it should be available under Devices > USB, and selecting it should route it to the virtual Linux instance

you ran the two ModemManager commands the guide told you to do while the device was in recovery/fastboot mode before trying to send the brick, right? (You do that by turning it off and holding the power + left volume button, and releasing the power button once the Amazon logo appears)

Also sorry if you already knew how to do that, I forgot if it would say "sending brick..." when the device wasn't in that mode. The guide wasn't very clear about when you needed to put it in recovery mode
[Fire HD 8 and HD 10 Original Android Development] mopst:
The following worked for me. We kill any running adb servers, run it intentionally on port 5037 on all interfaces, elevate to root in WSL, again kill adb server, and kill any that might be running under any other user, export the socket so ADB looks for it elsewhere, and then run the devices command to see if we can see our device. This is preferable, in my opinion, to connecting via internet, because I really didn't want to risk Amazon auto-updating the device and forcing me to then downgrade it. Using this, I could connect via USB and keep it offline. Hope it helps someone. :)

Windows CMD:

adb kill-server
adb -a -P 5037 nodaemon server

WSL, using sudo to switch to root because the bash scripts need to run with root privileges.

sudo su - root
adb kill-server
killall adb
export ADB_SERVER_SOCKET=tcp:LOCAL_IP_HERE:5037
adb devices

Replace LOCAL_IP_HERE with your Windows IP -- it's likely something like 192.168.1.x. You can find this out by entering ipconfig in the Windows command prompt. If adb devices outputs a device ID string, something like:

List of devices attached
G821GL02845209BP recovery

...then you can proceed by running the bash script as per the OP's instructions.
[Fire HD 8 and HD 10 Original Android Development] kbroh:
It worked 3/9/21 for me on Douglas Fire 2017, 5.6.8.0. Perfectly! Every other tutorial on here did not work, but Opec user was spot on!
[Fire HD 8 and HD 10 Original Android Development] Crono75:
I have a Fire HD 8(7th generation) with OS 5.6.8.0.

I used brick-douglas with the command "sudo ./brick-8920.sh".

But after the command unfortunately the USB came off and now it won't boot into bootloader mode. It seems to be dead, but when i connect the usb to the pc i hear the beep. Do you have any suggestions? Thanks to all!!!!
[Fire HD 8 and HD 10 Original Android Development] Korin67:
What was displayed on the tablet when you issue brick-8920.sh? Did you see like: disconnect the tablet and power off ? If this is the case your tablet is bricked (not dead). Just keep going to the next step.
[Fire HD 8 and HD 10 Original Android Development] skudo101:
I also have the same situation as you, do you have any way to fix it? I do everything but HD8 is still can not reboot, It just black screen :(
[Fire HD 8 and HD 10 Original Android Development] k1ndlef4cker:
Is there any problems if i flash the stock rom from amazon website with twrp? (currently runing lineageos) because i heard from somewhere that it would do something with twrp
[Fire HD 8 and HD 10 Original Android Development] gops75:
I tried the steps posted by @deverro but due to my hasty thinking, I got my fire hd 8 device bricked.

I followed the steps -- reboot to bootloader, and then tried ./brick.sh, and it gave me failed (data write failure) result.

Then I tried ./brick-9820.sh. It actually worked, and I saw that files transferred in the device screen (fire HD 8) which asked to switch the device off (or take the plug off or something similar --- don't remember). But at the same time, my command window (Linux PC) still showing writing 'brick'...

I was thinking I should switch off the device as per the device screen but as soon as I switched it off, the PC command window gave me error saying 'Failed (status read failed No such device).

Now my device seems bricked. Is there a way to get it back to at least factory setting. I tried the (Volume Minus Key + Power), Not helping.

Any suggestions. Please let me know steps to get either Lineage OS or factory set up in my bricked device. Thanks.
[Fire HD 8 and HD 10 Original Android Development] gops75:
Hi All and @deverro:

I continued doing the next step and it worked. Thanks a lot.

Please ignore my previous post.

Regards,

GV
[Fire HD 8 and HD 10 Original Android Development] coffekind:
Git for Windows

We bring the awesome Git VCS to Windows

gitforwindows.org

would windows users be able to bypass using wsl, vm, and/or usb bootables altogether by using this? Asking cause I have no idea about this stuff, and it seems it'd make it way quicker & easier. Also, apologies if this was mentioned earlier in the thread.

Nope it did not work. I'm inclined to say after toiling with it for over a day, the boot unlock process is impossible using windows with wsl, unless I missed something to make adb and fastboot actually work properly with it. bootable drive it is then.
[Fire HD 8 and HD 10 Original Android Development] SamDungUser:
Hi, I bricked the device via modifying partitions. Can someone help? I tried shorting but it seems to refuse booting anything, TWRP or hacked FB. Help please!
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Run gpt-fix.sh
[Fire HD 8 and HD 10 Original Android Development] SamDungUser:
Will it restore the userdata partition because that's what I screwed up
[Fire HD 8 and HD 10 Original Android Development] zacharylam:
It works on my 2017 HD8, Thanks!!!!
[Fire HD 8 and HD 10 Original Android Development] benchpole:
Success using opec's guide on page 32 of this thread with a 2017 HD 8 and 5.6.8.0 firmware. Running LOS 14.1 and it feels like it's about 100 times snappier than the stock amazon fw with the launcher hack. This is also the first android anything I have ever rooted. I used an old laptop and installed Ubuntu. Here is the rundown of the problems and the solutions that worked for me:

Maybe don't use a live linux usb. Ubuntu is my goto linux distro but It froze. It was slow. It froze again right before a step I was sure could brick my tablet. It sucked. I ended up digging up an old hard drive, put it in the laptop and actually installed it. So much better.

After installing Ubuntu:

I started off by copy and pasting the OP of this threads tools to install to ubuntu from the very first post. It worked fine bricking the tablet but I couldn't get it past that. This works better:

sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot

Also this was necessary:

sudo systemctl stop ModemManager
sudo systemctl disable ModemManager

Follow opec's guide:

except use this when it comes time:

sudo ./brick-9820s.sh

I opened and dissected my Fire tablet with no reason, because I didn't know what I was doing and it was the computer not the tablet that was wrong.

I had an SD card ready with LOS and gapps, and just did the install. Download the .zip files, put them on the SD, that's all you need to do. Touch install, make sure you do the LOS one first and hit additonal zips and add Gapps.

LOS 14.1 Fire HD 8 ROM
[Fire HD 8 and HD 10 Original Android Development] sinong:
My tablet is bricked after running brick-9820s.sh. I cannot bring it back to next step. I doubt if I should switch off the tablet according to the prompt on the screen.

Tried to dismantle it but I cannot access the board to unbrick with the short method.
[Fire HD 8 and HD 10 Original Android Development] sinong:
Can you let me know if you turn on the tablet when doing next step? My one is bricked and won't respond to the next command. Thank you!
[Fire HD 8 and HD 10 Original Android Development] benchpole:
Sounds just like what happened to me at first. Mine was also bricked with no screen or response, tried holding the power button, and any other combination of buttons I could think of. Actually bricked. I did take it apart with the battery disconnected and board hanging out of it, but I didn't actually use the short method. I changed my mind and put it back together and started over from where it went wrong.

I'm pretty sure the biggest problem for me was this was the very first bootloader I've ever unlocked on anything, so I made some mistakes that others more experienced probably wouldn't have. I wan't running the scripts with sudo at first. Other than that, I think I forgot to stop and disable ModemManager and that might have caused problems. Maybe disconnecting the battery and reconnecting it did something.

I was hoping to document what I did differently and ended up working but I don't know exactly which one of the things actually made the difference in being able to run sudo ./bootrom-step.sh with success and move on. I hope you figure out a way.
[Fire HD 8 and HD 10 Original Android Development] Drachna:
Hi, I'd just like to say that this guide still works for 5.6.9.0, or at least opec's version of it does. Just keep in mind that the Yes/No commands in the command terminal are case sensitive. That caused me a fair bit of trouble.
[Fire HD 8 and HD 10 Original Android Development] DarkH2O:
Im trying to downgrade but after running the script for brick it sits at "waiting for any device".
[Fire HD 8 and HD 10 Original Android Development] DarkH2O:
Seems like my tablet isn't prompting for authorization. In adb devices it shows as unauthorized. I've tried restarting adb services and removing know authorization in the tablet.

Any answers?
[Fire HD 8 and HD 10 Original Android Development] DarkH2O:
So I finally got past those issues and I'm in TWRP. Im not trying to install Lineage 15.1 from a card in the firehd but as soon as the install starts it restarts TWRP.

Edit * Looks like using a usb stick with an OTG adapter helped.
[Fire HD 8 and HD 10 Original Android Development] mh1983:
I now can't seem to get into TWRP any more on my douglas tablet. I do a reboot/hold vol up and down, nothing. I turn the tablet off entirely, turn back on, then hold vol buttons. Nothing -- I see the Amazon logo for a sec and then a blank screen. Any suggestions? I have Lineage OS 15.1 and it's working well, but was just trying to do a non-destructive/OTA style update in TWRP with a new zip file.
[Fire HD 8 and HD 10 Original Android Development] karl001:
<Ooops, wrong Thread>
[Fire HD 8 and HD 10 Original Android Development] Marko967:
I'm using ubuntu

when starting the first step

sudo ./step-1.sh

an error appear

sudo: ./step-1.sh: command not found

any one can help..please
[Fire HD 8 and HD 10 Original Android Development] Marko967:
when starting the first step

terminal show error

sudo: ./step-1.sh: command not found

any sollution please
[Fire HD 8 and HD 10 Original Android Development] Korin67:
sudo: ?? You do not need to add colon after sudo. What happens if you type:

sudo sh ./step-1.sh

Edit: sudo: is the response from the computer, I understand. Try sudo sh ./step-1.sh.

Or you can do: chmod 555 step-1.sh, then type sudo ./step-1.sh.
[Fire HD 8 and HD 10 Original Android Development] Marko967:
after that this appears

* daemon not running; starting now at tcp:5037

* daemon started successfully

Testing root access...

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

Pushing root files

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

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

bin/busybox: 1 file pushed. 4.4 MB/s (587368 bytes in 0.128s)

Failed critical init step 4

This firmware cannot be supported

Failed critical init step 4

please help

p.s device firmware is 5.3.7.0

and can any one make a video for that

@

Korin67​
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Okay, the shell script now seems working. I do not now how to proceed without bricking the device. In my case, the firmware was newer; I first bricked my douglas, then apply the shell script. Maybe someone else who took the same procedure like your case might help. I have no idea on this point.
[Fire HD 8 and HD 10 Original Android Development] Marko967:
you mean i should short the test point and then try the step-1 script
[Fire HD 8 and HD 10 Original Android Development] Marko967:
can you tell me how to brick the device
[Fire HD 8 and HD 10 Original Android Development] kip_dynamite:
Just read the first post carefully:
[Fire HD 8 and HD 10 Original Android Development] Korin67:
No, if you brick your device, no need to open the device, no need to do the 'short test point action'. Yes, as suggested you might better scan this thread. You find the solution by yourself.
[Fire HD 8 and HD 10 Original Android Development] Marko967:
can you tell me

1-what files should i put in amonet/bin (arm folder or mtksu file).

2- where to find mtk-su to your /data/local/tmp folder.

thank you so much for your response
[Fire HD 8 and HD 10 Original Android Development] kip_dynamite:
Please follow this guide:

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] Marko967:
sudo ./brick.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' (112090 KB)...

FAILED (data write failure (Cannot send after transport endpoint shutdown))

Finished. Total time: 62.362s

when i tried (sudo ./brick-8920.sh)

terminal say

no command found

is there any solution please

p.s I'm using ubuntu is it good or there is another linux distribution better
[Fire HD 8 and HD 10 Original Android Development] FireworksVOBL:
I have a kindle DH8 7th gen, which I use only once per year to help me fire a fireworks display. When I came to use it this year and charged it, it now hangs at the yellow Fire logo.

I'm new to any kind of android hacking, but I thought "how hard can it be to unbrick?". Well now I'm finding out!

I didn't enable USB Debugging in the fire when it was running OK. Boy do I regret that now.

Anyways, everything I've tried "soft-wise" to unbrick it has failed and it seems that is down to the fact that I can't flash anything to it as the bootloader is locked (not sure I'm using the right terminology, but be kind to me, I'm a newbie). I tried adb and fastboot via USB. ADB doesn't see the device. Fastboot will see it when the kindle is in fastboot mode, but I can't flash (or do anything) without being confronted with the message that it can't be done on a locked bootloader.

So I resorted to taking the back off and trying the bootrom-step.sh and shorting TP28 to ground.

But I'm getting nowhere with that either. I get "Waiting for bootrom", but no amount of attempts to short to ground and inserting the USB into my W10 laptop running an Ubunto app, gets me any further.

What am I doing wrong?
[Fire HD 8 and HD 10 Original Android Development] Marko967:
sudo ./brick.sh

[sudo] password for asus:

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' (112090 KB)...

FAILED (data write failure (Cannot send after transport endpoint shutdown))

Finished. Total time: 60.406s

asus@asus-X553SA:~/Downloads/brick-douglas/amonet$ sudo ./brick-9820.sh

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' (111616 KB)...

OKAY [ 4.696s]

Writing 'brick'...

FAILED (status read failed (No such device))

Finished. Total time: 69.549s

and the devices reboots to system

any solution please
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Before you try hardware method (pin shorting method), what happens if you press VolDn+PWR buttons until you see the white amazon logo, then release both buttons? If you find menu that include bootloader reboot, then you can go to the fastboot mode. Is it possible on your tablet?

Edit: VolUP+PWR buttons. The button on the left-most, I mean.
[Fire HD 8 and HD 10 Original Android Development] FireworksVOBL:
Hi Korin67

Thanks for replying.

I can get to fastboot, using the key presses you suggest. I’d been doing this for a few days, whilst exploring adb and fastboot connections.

However, when I try to ADB, my PC cannot see any devices. Fast boot sees it and returns the serial number OK. I can send commands by fast boot but nothing that will allow me to flash anything, as it says the FW is locked. Presumably because I didn’t enable ADB in the settings from the Fire OS when the device was working.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
I think you do not need ADB connection until you install TWRP. TWRP will be installed without ADB connection. What I meant is:

Set to fastboot mode -> brick your device -> apply bootrom-step.sh -> apply fastboot-step.sh

All should work without ADB connection. Actually when I did for my three douglas, I first enabled usb debug on. There is possibility that my suggestion might not work. Anyway, try it. It should be much easier than the hardware method.

I believe you already have read informative posts in this thread. That means you do NOT, for example, try to power on your bricked device.
[Fire HD 8 and HD 10 Original Android Development] KumaVL:
Ok so, my tablet got bricked a few years ago and i didn't wanna open it to try to fix it, so In the i just put it inside a drawer and forgot.

The tablet got bricked because of a bad downgrade, it doesn't show anything on the screen, no charging, no logo no sound no nothing.

When I connect the tablet to a pc nothing happens either adb doesn't find it, now, if I hold the power button for about 10 to 15 seconds I hear the computer detects it (device manager sees it as Mt65xx Preloader) but a second or two after it makes the sound like it was disconnected ans the behavior can be repeated but it never stays.

I did try the steps but nothing happens and the tablet is never recognized. Any idea? Is it just dead? The battery worked perfectly when the tablet was in use and physically doesn't look like it died but well what do I know?.
[Fire HD 8 and HD 10 Original Android Development] Korin67:
If your device is really bricked (not dead), the script bootrom-step.sh might work. Otherwise, the hardware method might help. No more idea. Knowledgeable person might give better suggestion.
[Fire HD 8 and HD 10 Original Android Development] KumaVL:
But my pc won't recognize the tablet nor show on adb, or does it need to be on Linux to work?
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Since your tablet is bricked, it is normal pc does not recognize it. Try bootrom-step.sh. The script is written with python3. Python3 (plus serial module) should be installed in your pc.
[Fire HD 8 and HD 10 Original Android Development] KumaVL:
Got wsl on windows to install Ubuntu and tried the bootrom-step.sh but nothing happened since
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Nothing happens mean the script does not work? At least you find message "waiting for the device" or something like that on the screen. If you see waiting for the device, then plug the USB port to the tablet (connect to PC), then the script request you to type YES, then the data transfer starts. This is the normal procedure for this script. If not, I have no idea, sorry.
[Fire HD 8 and HD 10 Original Android Development] KumaVL:
Only message says waiting for bootrom, nothing else
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
You're the first person I can recall trying this with WSL on Windows, but other people have had trouble trying to get these scripts to work on an emulated Linux.

The host operating system always need to do something to share the USB ports with the emulated OS, and it seems like this often confuses the scripts.

I've seen it happen at least a few times where people have trouble with these scripts when running an emulated version of Linux, and the problems go away when they run Linux (usually Ubuntu) natively by booting from a USB stick.
[Fire HD 8 and HD 10 Original Android Development] KumaVL:
Ok so i could do it without the need to install it on the pc, straight from the usb stick? (not saying it will solve all my problems, but at least better chances?)
[Fire HD 8 and HD 10 Original Android Development] dontpanic-xda:
Yes, I think it's worthwhile to try this from Ubuntu booted from a USB stick. No guarantees! But I've seen people have success going from an emulated Ubuntu to native Ubuntu booted from a USB.

Don't forget to disable modem manager. :)
[Fire HD 8 and HD 10 Original Android Development] FireworksVOBL:
Thanks for all the help. i think the secret was to use a “pure” Ubuntu environment instead of the Windows Ubuntu app. All went fairly straightforward then. I managed to flash a Fire OS image from the Amazon website and get my kindle back up and running. I couldn’t be bothered to root and try a different OS, as Fire does what I need. At least until another update bricks it :)
[Fire HD 8 and HD 10 Original Android Development] Korin67:
Nice to hear that. Well, LOS15.1 might be a good choice (you would be amazed with its speed) even though you are not so much interested in. Anyway, enjoy your tablet.
[Fire HD 8 and HD 10 Original Android Development] Pyrosync:
I think my son let the kindle fire hd 8 go flat during a firmaware update and it bricked it just had a black screen so i'm not sure what firmaware it was on and i have the issue above
[Fire HD 8 and HD 10 Original Android Development] Pyrosync:
Hi is this still active?