yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] nipponsahore:
stuck at 'USB transferring'

Thank you for the post, However I'm facing a peculiar issue. I'm using a Macbook Air and using a Linux VM to run a Debian Image and below is my issue:

I'm able to see my device using 'adb devices' as well as able to reboot into the bootloader.

fastboot is also working and using 'sudo fastboot devices' also shows me my device.

when I run the command 'sudo ./brick.sh' or 'sudo ./brick-9820.sh', my tablet shows me a 'USB Transferring' message and remains stuck. I tried waiting for 30+ min but no success and I'm forced to manually kill the task.

Also, tried to invoke the flash brick command from the shell file but in this case as well without any success and is still stuck at 'USB transferring'.

I'm using 5.6.6.0 with build number - 654620620
[Fire HD 8 and HD 10 Original Android Development] deverro:
Hmm, haven't used it through a VM, so wouldn't know...but if i recall correctly, I think mine froze too, just i didn't touch the terminal, but held power button for as long as needed for the tablet to shut down.

Then on another try, it went OK.

Check (or replace) cable so that it is not loose (breaking connection) during the transfer (maybe through VM takes longer than usual).

If it doesn't work, I would ask a friend with a Ubuntu Linux machine or use a LIVE ubuntu USB, install everything needed an try then.

Keep in mind that with the next update you could lose the possibility of rooting it.
[Fire HD 8 and HD 10 Original Android Development] kojam:
"just wait a bit and watch the terminal, it will soon start displaying the process"

Left it for 30 mins, no code being displayed. Just sat at waiting. Ran it over night and left it. Same thing. Continued on anyways.

Of course it didn't say HACKED FASTBOOT though.

Any ideas?

Thanks for this tute by the way!!!
[Fire HD 8 and HD 10 Original Android Development] adityashah0098:
[MENTION=612460]kojam[/MENTION], did brick-9820.sh complete for you?
[Fire HD 8 and HD 10 Original Android Development] deverro:
First time this happened was when I didn't realise it was not turned off (was on with a blank screen, fooled me btw)...

So I held power btn for 10 secs to be sure it was off.

After that reconnect the tablet, try the script again and see if it works.
[Fire HD 8 and HD 10 Original Android Development] kojam:
Hi bud.

It looks like it may have.

Looking at these pics, the 1st time I went through all the steps...but just realize now that the script failed. The other script had failed immediately so I used th3 secondary script.

I tried the whole procedure twice. The 2nd time, this script hung forever, so I manually interrupted ...

I would love to get this to work. I have the 7" and this 10". BOTH are paper weights! Lag to the point of being unusable. I used the toolbox in both, which made them even worse. I did the restore that comes with the toolbox (a wonderful tool by the way), but they still are worse than before. The restores didn't seem to put things back to normal.

To be clear...I'm trying this on my 10" running 5.6.6.0

Thanks in advance!
[Fire HD 8 and HD 10 Original Android Development] kojam:
Oy vey! Ok. Thanks.

The part of the procedure says that u will start seeing lines of code scrolling by on the screen after a few minutes of nothing seeming to happen.... I never saw any lines of code scrolling by. Sorry. Cannot refer to the exact part right now. I'm in my cell writing this.
[Fire HD 8 and HD 10 Original Android Development] deverro:
I can see now, why you're so eager to jailbreak :cowboy:

---------- Post added at 09:42 PM ---------- Previous post was at 09:32 PM ----------

I see a few things that aren't supposed to be there (by screenshots).

If the brick (any of them) commands give you "FAILED (data write failure (Protocol error)", means it doesn't work.

If both brick commands give you that error, then you're out of luck unfortunately, as any of the following steps won't work.

Secondly, whilst running brick-9820.sh I see that u manually interrupted the script with CTRL+C (by ^C sign). So it wasn't complete and bootrom step wouldnt work.

Third, on the second screenshot seems that brick-9820.sh didn't work as it lost (presumably) the connection to the tablet (check if the cable connector is falling out/losing connection or smth),

as it gave you FAILED (data write failure (No such device).

I too got the first one "FAILED (data write failure (Protocol error)" when i first tried with brick.sh, but after that brick-9820.sh worked.

I never got "FAILED (data write failure (No such device)" err.

Also I don't know if the tut will work for HD10, I did this on HD7'' version.
[Fire HD 8 and HD 10 Original Android Development] Jabbitt:
If I return to stock, will I keep root?

Where do I get stock images from and what's best, use current format or restore the gpt and completely restore?
[Fire HD 8 and HD 10 Original Android Development] kojam:
So, couldn't get it to work. Tried on the HD7 lump of coal that I have. No go. Fails at the same spot. Looks like, in both instances, the device reboots, causing the script to report that it doesn't see any device.

So, I found the 5.6.4.0 HD 10 f/w here on "The X" (trying to make XDA sexy and trendy like Drake did for Toronto by calling us "The 6", since our main area code here is 416. I digress. I DON'T LIKE DRAKE!) and figured that I'll give it a go so I can run mtk-su. It's needed for unlocking the bootloader but is only for 5.6.4.0 from what I saw. I figured even if I brick my HD 10, it's already been almost unusable for me any way. So slow and non responsive that I HATE trying to use it!

Well, the sideload of 5.6.4.0 was done... THEN BRICK. LOL. Good night! It was 3am.

Funny thing's it only works slightly worse now as a brick than before it was bricked. LMAO.

Maybe someday, when I care enough about this P.O.S, which has been a TERRIBLE experience to use right out the gate, I may see about trying to unbrick it.

Honestly, I'm thinking of the satisfaction I would get by hearing the 2 of them crumble as I slowly and methodically drive my car over them ever so slowly, for hours.:silly:

Thanks for your help.

Regards.
[Fire HD 8 and HD 10 Original Android Development] nipponsahore:
Hi All,

Does anyone have a link to downgrade from 5.6.6.0 to 5.6.4.0? None of the 5.6.6.0 methods worked for me :(

Thanks :)
[Fire HD 8 and HD 10 Original Android Development] spandexman:
Need a little help. I ran brick-9820.sh and it the linux machine said WRITING 'brick' and on the tablet its said successful, turn off tablet and unplug USB. So I did, and the linux machine said FAILED (status read failed (no such device)). I tried the bootrom-step.sh but it wouldn't work. Tried opening the tablet and shorting TP28 to ground. That didn't work either. Any ideas on what I can try? Thanks!
[Fire HD 8 and HD 10 Original Android Development] jdelgadocr:
Thanks a lot!

Better skip the brick.sh and straight to brick-9820.sh. Same on 2 tablets we have at home. Other than that... EXCELLENT walk-through [MENTION=10911591]deverro[/MENTION] !!!! and of course thanks to [MENTION=7104332]k4y0z[/MENTION] !!!
[Fire HD 8 and HD 10 Original Android Development] nipponsahore:
Worked for me as well on Fire OS 5.6..6.0 using the file brick-9820.sh

---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------

[MENTION=4065391]spandexman[/MENTION] - I tried brick-9820.sh and it worked for me

Once you use the command brick-9820.sh, let it show as success give it a few seconds to show you the prompt on the terminal.

press the power button to allow it to turn off (Do not Unplug USB cable).

Triggering the bootrom-step.sh will turn the tablet on and patch the necessary files and will finally boot into TWRP.

Once you're in TWRP, you're good to install whatever you want.
[Fire HD 8 and HD 10 Original Android Development] spandexman:
I don't think I let the brick process complete fully. Is there a way to recover from this?
[Fire HD 8 and HD 10 Original Android Development] PamelaGirl:
Hello Good People,

First off a huge thank you for the creation of this thread along with all the supported files to unbrick our devices! :)

My Amazon HD 10 7TH GEN tablet bit the dust after I tried sideloading an older firmware. Now it will not start, it appears to be dead. I have been reading and reading and came across this lovely thread. I have downloaded all the files needed and yet I cannot get past the " sudo ./step-1.sh"

When my tablet is connected to the computer I can see at the bottom right hand of the computer dock an icon that flashing every few seconds, than its gone, this repeats. "Disconnected MediaTek MT65XX Preloader"

Is this normal?

How do I perform step #2. "Enable ADB in Developer Settings"? Is this something I do within Linux?

In terminal I will write "sudo ./step-1.sh" followed by return but nothing happens? Can someone with more experience please assist me?

Gratitude and Appreciation and Thanks :)
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
You need to use the method and files (i.e. amonet) specific to your device: the version for the HD8 (7th gen.) will not work with the HD10 (7th gen.). Also, this is the wrong thread for the HD10.

It is possible, with a functioning device, to brick it in a particular way to enable the device to enter straight into bootrom mode. I think this normally involves overwriting the preloader. Unfortunately, if you have bricked it by installing an earlier Fire OS version you have the wrong sort of brick. It should be possible to resurrect your tablet but you will have to use the shorting method. I think with the Suez (Fire 10, 7th gen) you have to short a point on the rear of the main board: see the main Suez unlock thread for details of how to access bootrom mode and execute the scripts.

The process involves running 'bootrom-step.sh', shorting the point, plugging in the USB cable and pressing 'enter' after removing the short. If this runs correctly, you then reconnect the board (and battery) and run 'fastboot-step.sh'. This should fix your tablet. It will unlock the bootloader and install TWRP recovery. It will also repartition your device so you will loose any files you have on the tablet. I am not sure if there is any way around this.

I have run this method on one Suez tablet. I remember that it is a bit fussy about the version of fastboot you use. On Ubuntu 16.04 (32-bit) the version of fastboot in the repository is too old and it won't work. I had to do it on a PC running Ubuntu 18.04 (64-bit) to get fastboot to work. The flavour of Linux you use is up to you, it does not have to be Ubuntu, but it does need to have the right fastboot version.

Post 2 in the main Suez thread (and the links within) should help explain what you have to do. See here: https://xdaforums.com/showpost.php?p=79169423&postcount=2.

EDIT. Take a look at this thread here: https://xdaforums.com/hd8-hd10/development/2017-fire-hd-10-unbricking-anti-rollback-t3896616. It should allow you to unbrick your tablet without unlocking/ installing TWRP/ wiping the tablet. Also, it only requires one script to run and does not use fastboot.
[Fire HD 8 and HD 10 Original Android Development] PamelaGirl:
Hello MontysEvilTwin,

Thank you for the response and taking the time to assist me with few additional words to help get my device up and running. I knew I was in too deep when it asked me to enable ADB in Developer section.

I feel like I need a nap but I know I must press forward in this quest to fix my device. My knowledge in Linux is limited so the only way I can do this is with detailed steps of how to via in Windows or Linux or Mac.

I will take a look at the links you provided and stay hopeful with getting the device running. All I wanted to do was run Lineage and live happily ever after away from the strong arm of data mining and tracking. The thought that our devices would brick simply by installing an older firmware is a sign of the times of not breaking away from the herd. I usually always break away from the herd, that probably why every device I have is rooted or jail broken. And for that I say thank you to all the supporters and contributors of XDA! :)
[Fire HD 8 and HD 10 Original Android Development] spandexman:
Could anyone explain what the brick-9820.sh does? I'm hoping I can figure out how to unbrick my tablet if I know what it does. Thanks!
[Fire HD 8 and HD 10 Original Android Development] kojam:
You sound like me. LOL
[Fire HD 8 and HD 10 Original Android Development] PamelaGirl:
ehehe

I am now thinking about the Lenovo Tab E10 because it has GPS and a radio as in a radio for FM radio and it may be user to install LineageOS

https://www.getdroidtips.com/lineage-os-14-1-lenovo-tab-10-x103f/
[Fire HD 8 and HD 10 Original Android Development] LKJEFoi234:
My firmware version is 5.3... or 5.5... Is that it? Nothing else can be done?
[Fire HD 8 and HD 10 Original Android Development] LKJEFoi234:
I might piss some people off with this post. But why on earth are OP's not updated with significantly relevant information such as this? It makes absolutely no sense, but is very common on the XDA site:

Create a Guide,

Guide becomes outdated after a very shortly

People continue relying on the "guide" and spend countless hours in confusion not getting it to work.

Isn't there some process that non-OP's can update the OP? This site is mess.

Thank you, deverro and other contributors. I finally got it working with your guide.
[Fire HD 8 and HD 10 Original Android Development] bob_smith:
Can you post a reliable method to do this on WIndows?
[Fire HD 8 and HD 10 Original Android Development] AmznUser444 Dev:
You can unlock and root your Fire tablet using Windows subsystem for Linux.

Your PC running Windows 10 64-bit to setup and run Windows subsystem for Linux on your Windows 10 PC

Here is a setup documentation for Windows subsystem for Linux:

https://docs.microsoft.com/en-us/windows/wsl/install-win10

If your PC running an old version of Windows (i.e. Windows 8.1, Windows 7). You can upgrade your PC to Windows 10:

https://www.microsoft.com/software-download/windows10
[Fire HD 8 and HD 10 Original Android Development] DB126:
Have you actually tried this procedure with WSL2 (didn't work with 1st Gen WSL)? Guessing not and you're just posting stuff you read somewhere.
[Fire HD 8 and HD 10 Original Android Development] LKJEFoi234:
This is the only current method:

https://xdaforums.com/showpost.php?p=82921395&postcount=524

You will need to use Linux, which can be run from your Windows PC using a USB flash drive:

https://linuxmint-installation-guide.readthedocs.io/en/latest/burn.html
[Fire HD 8 and HD 10 Original Android Development] m0000:
selfishly bumping after a month of no replies. if anyone can help. would appreciate it. Thank you
[Fire HD 8 and HD 10 Original Android Development] drynyks:
Thank for your contribution to this thread. I followed these instructions exactly and it worked perfect.

DO THIS :good:
[Fire HD 8 and HD 10 Original Android Development] DetCochese:
Man, this is kicking my ass.

I have a Douglas? 2017 HD8 that was working fine for my kid to watch YouTube Kids, but recently it stopped taking mic input no matter what I do. I've factory reset it. Tried everything I can think of.

Time to root it and Rom it.

Planned on putting whatever the latest Lineage is on it and calling it a day.

The instructions for these Kindles are not as straight forward as I anticipated. I'm not a total moron. I'm almost 40 and I've been screwing with Android phones since they came out. I also have a newer zBook with Win 10 Enterprise running Ubuntu (installed today WSL 1 just for this purpose.) I also have a Dell ChromeBox 3010 running an Ubuntu based linux distro. Ducks in a row and I spent 4+ hours trying to figure this out to no avail.

Is there a simpler more pedestrian walkthrough out there for someone trying to root a 2017 Kindle HD 8 to flash a custom recovery and pure AOSP rom?

I feel like an idiot but I had to walk away before I break something.

I tried this on my Linux machine. I tried it on W10/WSL in terminal and ran I to issues moving files around and into the correct directories.

What an ass kicker. I'd rather not have to buy yet another tablet just to have a working YouTube Kids browser. Plz halp.
[Fire HD 8 and HD 10 Original Android Development] DetCochese:
Well, I'm bricked and not in a good way. Black screen will not power on. Ran sudo ./brick-9820.sh and got a success message telling me to unplug and power down, which I did. Now I cannot get a response in ADB DEVICES. I tried running the bootrom-step.sh command and it sits with WAITING FOR BOOTROM.

It is dead as a doornail. Ideas? [MENTION=10911591]deverro[/MENTION] or [MENTION=7104332]k4y0z[/MENTION] ?

---------- Post added at 10:39 PM ---------- Previous post was at 10:39 PM ----------

Well, I'm bricked and not in a good way. Black screen will not power on. Ran sudo ./brick-9820.sh and got a success message telling me to unplug and power down, which I did. Now I cannot get a response in ADB DEVICES. I tried running the bootrom-step.sh command and it sits with WAITING FOR BOOTROM.

It is dead as a doornail. Ideas? [MENTION=10911591]deverro[/MENTION] or [MENTION=7104332]k4y0z[/MENTION] ?
[Fire HD 8 and HD 10 Original Android Development] DetCochese:
Anyone want to make some money to fix this thing? :D
[Fire HD 8 and HD 10 Original Android Development] turbozapekanka:
These steps worked for me on Version 5.6.6.0 and I used Debian Buster:

Some comments on the steps:

1) sudo add-apt-repository universe - not necessary

2) run sudo adb start-server before using adb comands otherwise adb will not have permissions on the device

3) sudo ./brick.sh - did not work, skip this and use the brick-9820.sh instead
[Fire HD 8 and HD 10 Original Android Development] DetCochese:
Any ideas on how I should proceed from after brick-9820.s? It told me to power down the device and unplug (which I did) and then I was unable to get further. Tablet does not power on and won't recognize with ADB.

I would love for this to succeed to I get get this thing running again.
[Fire HD 8 and HD 10 Original Android Development] turbozapekanka:
run sudo ./bootrom-step.sh

and turn on the tablet.
[Fire HD 8 and HD 10 Original Android Development] daver68:
Just wanted to give my thanks, as this post helped me get TWRP on my 2017 model HD 8, and now I have Lineage OS on it. This tablet is much more responsive, and overall more useful, now that I've gotten rid of the incredibly slow FireOS. I'm genuinely surprised at how much quicker the tablet is without the bloat.
[Fire HD 8 and HD 10 Original Android Development] DetCochese:
I think this might be working!

18th times a charm.
[Fire HD 8 and HD 10 Original Android Development] DetCochese:
Turbo, you got me fixed.

Thanks dude!
[Fire HD 8 and HD 10 Original Android Development] krazyflipj:
I’m stuck I can’t stop modem manager. It says running in chroot ignoring request
[Fire HD 8 and HD 10 Original Android Development] finwefeanor:
hey great people I hope you can help me. I am following deverro's method.

The thing is when I execute " adb fastboot bootloader " , tablet enters in fastboot but terminal in linux can not execute any more comments because in fastboot mode adb commands do not work. I don't know why. They are working before fastboot, but once in fastboot, device isn't even listed on the left pane in linux and " adb devices " command also does not work.

Do you have any idea how to run adb commands in fastboot mode ? I dont think it related with my usb cable.

---------- Post added at 07:45 PM ---------- Previous post was at 07:17 PM ----------

edit: it might relate with my usb cable as some comments in this topic said that it should be original cable not a 3rd party one.

But my original cable has lost ages ago. Is there any quality cable out there to do the work ?
[Fire HD 8 and HD 10 Original Android Development] MontysEvilTwin:
The command to enter fastboot mode from ADB is 'adb reboot bootloader'.

ADB won't work when the device is in fastboot mode but fastboot commands do. If you type 'fastboot devices' in the terminal window of the connected PC you will get the serial number of the connected device. Then running the appropriate fastboot script should copy TWRP to the device and finish the procedure.

You need a fully wired USB A to micro USB cable (both power and data) for this to work, but it does not necessarily have to be the original cable. If you managed to successfully execute 'bootrom-step.sh' then the same cable should work with the fastboot script.
[Fire HD 8 and HD 10 Original Android Development] finwefeanor:
Sorry I meant ' adb reboot bootloader ' yes. And no it does not show my device in fastboot when I type ' fastboot devices '

adb commands only works before fastboot mode. 'adb devices' command works as usual, it shows a serial number of the connected device. Then I type 'adb reboot bootloader' device enters fastboot mode. But once in there, no command works. typing fastboot devices does not show anything.

---------- Post added at 11:40 PM ---------- Previous post was at 11:32 PM ----------

and it also says ' low power charger connected ' every time. Is it related ?
[Fire HD 8 and HD 10 Original Android Development] finwefeanor:
ok I managed to run fastboot devices, then run brick-9820.s , it said success and unplug/turn off the tablet which I did. After that I run 'bootrom-step.sh' , it stuck on ' waiting for bootrom' message. I waited like more than 10 mins nothing happens. I tried to turn on tablet with holding power btn but it does not turn on. Only thing I am hearing sound of usb cable plug in / out like in every 10 secs. Do I need to type something in terminal ?
[Fire HD 8 and HD 10 Original Android Development] ironman226:
Linux VM Issues

I was also experiencing the same issue, with my screen being stuck at "USB Transferring" on Ubuntu 20.04 running in virtual box on a MacBook Pro. I think it has something to do with how virtual box was handling USB devices. Luckily I was able to create a bootable flash drive and boot into Ubuntu and complete the steps outlined by deverro without a hitch.

Hopefully this saves someone a few hours... or days. As a side note, here are some tips from my experience:

- I used brick-9820.sh off the bat, and didn't even bother with the other one. It worked flawlessly.

- When bricking your terminal screen may appear to still be working, but if your tablet screen instructs you to unplug and power off it means the process is done and you can proceed.

- As deverro mentioned, I also had to manually reboot my device after the bootrom step. Follow the instructions in his post.

- When you're formatting the Data, Cache and System partitions in TWRP, select one partition, format it and repeat. I tried selecting all 3 and pressing format, which gave me an error.

- When you go to download Open GApps get the "ARM64 > 5.1 > Nano" version.

These are just some things that I noticed, or that confused me during the process. The post by deverro helped me out a lot since this is my first time doing something like this. :good:

---------- Post added at 08:16 AM ---------- Previous post was at 08:07 AM ----------

This might sound like a dumb question, but did you plug the tablet back in after running that command? It took about 30 seconds to a minute for mine to continue. The tablet won't turn on at this point, the previous step bricked it.
[Fire HD 8 and HD 10 Original Android Development] finwefeanor:
Hey thanx for asking but I explained above. I managed to install lineageOS finally.

The thing is I did this in Oracle VM using Ubuntu so in every step I needed to add USB filters to VM and restart the VM to see my device. After that it worked. But it was a little bit different because USB was automatically turning on and off in every 30 seconds or so, I could hear the usb sound from my laptop. So next step needs to run between that moment that tablet stayed connected. It required lots of timing.