yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] TonytheEE:
Still can't brick

Okay, you win. I had an old PC from work that I installed full on ubuntu 18.04.

I followed everything from OP. Got

Sending 'brick' (112012 KB)...

FAILED (data write failure (no such device))

It reboots. I tried this a few times. No luck. It just reboots to a normal OS.

I even tried mtk-su, since like I said, I'm on 5.3.7.0 (650601220). Anyway, Saw there was an updated Brick.zip from k4y0z. One of the bricks in there produced the same error. The one that was zipped inside that zip produced this:

target reported max download size of 114294784 bytes

Sending 'brick' (112012 KB)...

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

Finished. Total time: 5.813s

Again, I'm nowhere near the 9820 build, so what is the deal? It's literally factory default, with just ADB enabled. Yes, RSA is permitted. Yes, I can see it in Sudo Fastboot Devices.

I've setup a VM, two live-usbs, and a full on install of linux trying to get to this point. ANY advice, or a concise walkthrough would be awesome.

Edit: I started off trying to do step-1.sh per the OP and had mtk-su installed. I was under the impression that v20 still works on my version, but init error 4 pops up, hence the brick guide.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
There's no current known method to brick/root 5.3.7.0. You most likely will need to open the tablet and do the manual way. You can try Kingo Root but I'm not sure if was patched aswell.

Regards.
[Fire HD 8 and HD 10 Original Android Development] jarrah31:
Spent the last few evenings working on rooting my Fire HD10 and all has gone well (wow there's a lot to learn). I now have TWRP installed with 5.6.4.0 stock (I tried LineageOS out too), plus I have the latest Magisk installed.

I would now like to disable OTAs and debloat, but I can't get root access back using the OP method.

Running step-1.sh pushes the root files ok, but it gets stuck on a fail loop when trying to do the following:

mount: mounting /dev/block/loop3 on /system/xbin/ failed: Device or resource busy

Is there anything I can do to fix this please?
[Fire HD 8 and HD 10 Original Android Development] stolirocks:
You need to do the hard brick method by opening it.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
no?

When you open it's for shortCLK with GND with makes the device to boot in bootROM mode allowing to amonet to load it's payload and exploit the fire, but you're not "bricking it".

Yes, it's the only way when you're bricked, but if you can't enter bootROM mode via software mode and the device isn't bricked, only way to do it is short CLK.

Regards.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Trying the fire.iso, I'm booted into it. What's the steps I take now??

Op erase pls
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
I'm rooted on 5.3.7.0 using kingroot method
[Fire HD 8 and HD 10 Original Android Development] stolirocks:
Good luck to you.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Ok hella confused now. Lol I did the take back cover method. Shorted it everything went great. But when I turn it back on it went str8 to Amazon launcher. I was confused on which brick zip to use I was following guide here and the one for the fhd 8. Can someone explain which brick zip to use pls
[Fire HD 8 and HD 10 Original Android Development] CostCost:
The guide from the first post worked for me on rooted stock 5.6.4.0 636559820 without opening the device. Followed steps 1,2,3 , including what's hidden in "CLICK TO SHOW" block for step 3 . After "Then plug the device back in." in step 3 I had to hold the power button for several seconds until the running script "picked up" the device. As OS for ADB I used Ubuntu 19.10 (AMD-x64).

For getting root on stock 5.6.4.0 636559820 as a precondition, I used offline method starting from " -- Type adb shell in an administrative command prompt. You should enter the tablet as a user." until "13. Set SuperSU to Grant as default access.". The rooting script might not work from the first run, in this case reboot the device and re-run the script.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
So you're saying that you rooted the latest firmware (aka 5.3.7.0) with KingRoot method (are you sure it wasn't Kingo root? They're both different things.)

This is pretty amazing because, KingoRoot is using CVE-2016-5195. It's pretty weird to see that Amazon didn't patched the vulnerability in latest software updates but it patched mtk-su :)

So if this is true, we can still unlock the HD10 without opening the case up to the latest version.

Regards.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
My bad sir meant Kingoroot I used. https://xdaforums.com/hd8-hd10/general/tut-fire-hd-10-7th-gen-2017-root-box-t3726443

Man I so lost with trying to unlock this tablet..lol instruction r kind of confusing me.. I tried without opening fail bootrom just sits there.. Ubuntu 18.04 btw.. Did the opening up thought I had success cuz shorting and stuff went fine.. but when i turn pad back on it booted up fine right back into amazon launcher 5.3.7.0.lol i got lil confused on somehting ik. so im unsure.. Would be nice if someone could revamp the thread.. IF I ever figure things out I would redo another thread myself. (with permission of course)

---------- Post added at 06:26 PM ---------- Previous post was at 05:56 PM ----------

Think imma try this. My issue may be Ubuntu 18.0.4 will upgrade to 19.10 and try again. Thx will post a update
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Hi,

If unlock has been successfully with the shorting method you should be able to reboot to TWRP by typing

adb reboot recovery

Or powering off the tablet and powering it on with volume + and power at same time until you see

==> RECOVERY MODE

in the bottom of the screen.

Regards.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Yea I did something wrong. It boot into default recovery.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
My fire never reboots to factory reset I did it manually. I ran the bootrom step this what I get. also updated to Ubuntu 19.10.

Ok guys I did the short for a 2nd time. Went fine once again but now my touch don't won't to work
[Fire HD 8 and HD 10 Original Android Development] DidleDum:
I'm a UNIX/Linux developer but a total noob to Android - which became a must for the latest project I'm working on. Just tried running these scripts but ran into the problem described in this post. Managed to root my Fire 10 via KingoRoot (SuperSU). Then saw this post and tried it. Step-1 worked, the system rebooted and did a factory reset. Step-2 just hung after printing 'Waiting for device...' After closer inspection, I discovered it wasn't waiting for the device, the connection works fine (can execute adb commands and 'adb shell' is also good). Any 'su' command goes out to lunch and doesn't come back! The system boots normally by the way and according to my list of installed apps SuperSU is still there. Tried re-installing it, but no luck. The Popup asking me to GRANT access never appears on the Fire 10 (7 gen).

Any help greatly appreciated - in "Android for dummies" lingo please :)
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Try setting default access to grant in SuperSU app.
[Fire HD 8 and HD 10 Original Android Development] DidleDum:
Yup, that was it - many thanks! It should have been obvious to me I guess. Just discovered this site yesterday - wow, great info here!

Looking at your batch files I can see what you did - even if I don't understand why you seemingly copied the same header and content to both the boot and recovery paritions! Got a tip for me on where I can find details on the makeup, layout and workings of Android? Who knows, once I know what I'm doin' maybe I can help with one or the other projects.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Anyone have any idea what might have gone wrong. Did the short on and everything seem to have agone fine. Butt now I don't have touch. Did factory reset and all still no touch.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
The source-code is all on my github

Sound like you broke or disconnected the flex-cable for the digitizer.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Ok which one is that. Not the one next to battery connection. only mess with the two that was required
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
IIRC, that was at the top of the board next to the USB.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
If my memory is correct I havent fixed a digitizer on one of these in yrs but the one at the bottom is the digitizer. The digitizer is diff from lcd display on top next to battery. Have anyone else tried the short on 5.3.7.0. Maybe its a new issue. Idk the short did go right I got to the remove short and the script ran and finish. Didn't run the bootrom part when I notice touch wasn't working. I instantly did factory rest still no touch. Think I may be doing a return to amazon
[Fire HD 8 and HD 10 Original Android Development] jonathanmoneill:
Sorry if this seems like a n00b response but.......

Hi all,

I attempted the software method last night with my Fire HD8 2017. I had previously rooted the device and installed SuperSu. When I tried this last night using a linux mint live usb, I opened the terminal window in the amonet directory but the script hangs at the first stage (sudo ./step-1.sh). The terminal outputs "Testing Root Access" and just stops there. As (a slightly relevant) aside, I'm not sure what version of the firmware I'm currently running or how to find that out(disabled OTA a while ago). I'd really like to be able to use a custom ROM on this device so any advice on how to get to that point would be greatly appreciated.

Thanks,

Jonny

Edit: Posted in wrong place. Too many Tabs. Apologies, please disregard.
[Fire HD 8 and HD 10 Original Android Development] Squirrlz:
I'm trying the method in the OP right now (from 5.3.7.0) after rooting with Kingoroot. I'm stuck on the step where I have to do a temp brick and then run sudo ./bootrom-step-minimal.sh, the terminal just displays "Waiting for bootrom..." and the tablet now refuses to turn on at all.

I followed all the steps carefully, am I screwed here? When running "lsusb" in Linux, the device will randomly show up as "Bus 001 Device 012: ID 0e8d:0003 MediaTek Inc. MT6227 phone" but appears to drop and reappear from the list repeatedly.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Have you tried to hold the power button, while connected and waiting for bootrom?
[Fire HD 8 and HD 10 Original Android Development] Squirrlz:
Edit, ok so I decided to run the exploit on a virtual Ubuntu box and it completed successfully. I'm at the TWRP screen, what do I do from here?
[Fire HD 8 and HD 10 Original Android Development] Phoenixlink1:
Hey y'all, i figured id try this since i bricked mine trying to rollback.

But my 7th gen doesn't look like the back of OP's

Is there something im missing?

Ive disconnected the battery cable but can't seem to be able to dislodge the other one unless im tugging at the wrong one.

Do I have a different model?

Help is greatly appreciated!
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Lift up tab. Be gentle not to break it. Then pull ribbon connector out
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Take the 11 screws out, lift up that board then u will see. Be care not to pull out those red and black speaker cables
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
After sep 1 my tablet don't do a reboot. I moved to next step type yes unplug run minimal plug back just sits on waiting for bootrom?? Do it suppose to reboot instantly at step 1 or not???
[Fire HD 8 and HD 10 Original Android Development] Phoenixlink1:
Thank you, ill try it when I can.

Also just to confirm, for shorting do I just poke the dot with tweezers while plugging in the usb?
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Lol. nope. Need a wire buddy
[Fire HD 8 and HD 10 Original Android Development] Phoenixlink1:
Heard in some thread a male to male jumper would work?

Like this:

https://www.amazon.com/GenBasic-Sol...ocphy=9027290&hvtargid=pla-569611556760&psc=1

Would one end go to the dot and the other to the usb port?

Again, thanks for the help! :D
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Yea. I used a old headphone wire and spliced it.
[Fire HD 8 and HD 10 Original Android Development] toystory:
Sorry walk though and Google but can't find the answer

I want to detail step on how to downgrade my fire 10 (know would brick)

and use this tools to install two and lineage

Also I don't need to open it or any hardware access ?

Thanks !
[Fire HD 8 and HD 10 Original Android Development] Squirrlz:
Start the minimal script again, wait for the "waiting for bootrom" message, plug in the tablet, hold the power button down for a few seconds. The script should automatically move on to the next step. If this doesn't work, unplug the tablet again, hold the power button down for 20+ seconds, then repeat those steps.

---------- Post added at 06:30 PM ---------- Previous post was at 05:56 PM ----------

Also, just to note, I was able to successfully install LineageOS 14.1 with the omx/headphone patch. It's great. I did this from 5.3.7.0, using Kingoroot (windows app only, the android app doesn't work on the fire) and a VirtualBox installation of Ubuntu 19.10 64bit. Followed the steps in the OP carefully and it worked perfectly. I did not have to open the case.

One thing to note if you're doing this with VirtualBox is that you have to go to USB devices -> Click on the tablet device every time you connect it otherwise Ubuntu can't see it.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Tried that a few time last night, this is what I get every time
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
yea I got the same thing. Mismatch error
[Fire HD 8 and HD 10 Original Android Development] Squirrlz:
You missed a step. You have to disable the ModemManager daemon.

sudo systemctl stop ModemManager
sudo systemctl disable ModemManager

From the Ubuntu terminal, before you run the boot-minimal script.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
I did disable modem. I either get mismatch error are pic below
[Fire HD 8 and HD 10 Original Android Development] FierceDeityLink1:
Thanks for posting this. Worked for me on a HD 10 running 5.6.4.0 636559820. Glad I didn't have to disassemble it.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Ok think imma get this now. I made a mistake and brick my device. Used the wrong bin file lol. Well my device wouldn't come on at all just black screen I could hear a beep when plug into PC connect been followed right by disconnect beep.

So I did the unbrick steps took tablet back off. Everything ran smooth.. this time I got it right yay I'm back on 5.6.0.1. Now imma ready to do step 1-3

I finally did it. YES YES YES OMG u feel so stupid once u do looking back. Lmao thx op. Question anyone care to pm me gapps and magisk link. I'm tired looking

I also recommend if u really having issues just brick ur device then do short pcb.
[Fire HD 8 and HD 10 Original Android Development] Datblkbro:
Bout to start this on a 2nd tablet. I should get it first try. Lol
[Fire HD 8 and HD 10 Original Android Development] sturner83:
This is pretty much exactly what I did and everything worked out. I was on 5.3.7.0. I rooted from Windows and then did the rest in Linux Mint 19.3.
[Fire HD 8 and HD 10 Original Android Development] k1ndlef4cker:
I do the same thing as you except i do the last thing on Ubuntu and im using linage is 12.1 too
[Fire HD 8 and HD 10 Original Android Development] DaSnipe:
Another success, tried Kingoroot and Kingroot, finally got Kingroot to work from inside Android (tried via Windows and got errors) on 5.3.7.0, once I was there scripts worked via Raspbian OS and TWRP is installed, time to install LineageOS14
[Fire HD 8 and HD 10 Original Android Development] spiralspirit:
successful after using the offline root method to get initial root. Once that was accomplished the rest of the script worked. a couple little things noted in the quote text a few posts ago that I also ran into including turning it back on for hacked fastboot. In the end everything worked out.

Did everything through a virtualbox ubuntu vm.
[Fire HD 8 and HD 10 Original Android Development] De-Jot-Ka:
Firstly, thanks to everyone that put effort to make it possible! :)

I just got it working from 5.3.7.0 using offline root method. Both WSL 1.0 and 2.0 work fine, as long as your ADB version match on Windows and Linux side (there is a post in this thread with more details). I almost thought I totally bricked the device but I switched multi-meter (you can use continuity mode to short) and USB cable and it worked fine.
[Fire HD 8 and HD 10 Original Android Development] psi78:
Worked on previously locked/unrooted Fire HD 10/Fire OS 5.3.7.0 (with modifications)

Hi,

i used it on Kindle Fire HD 2017 (suez) with the most current Fire OS 5.3.7.0 using Ubuntu Linux 19.10.

The tablet bootloader was locked before and i didn't have root access before.

step-1.sh didn't work because mtk-su (r20) doesn't work anymore on Fire OS 5.3.7.0 (which is the most current).

It worked when i installed kingoroot Windows app on pc and got root access to the Fire HD 10 with it, then rebooted PC to Ubuntu and executed step-1.sh again.

After following the instructions in step-1.sh and typing yes the tablet screen went blank.

At first i couldn't restart the tablet and couldn't connect to it with bootrom-step-minimal.sh

I pressed the power button on the tablet for over 45 seconds and stuff like that.

Noted i had modem-manager still installed in Ubuntu and deinstalled it, rebooted PC.

After some tries of pressing various button combinations on the tablet bootrom-step-minimal.sh finally got access to the tablet again, don't know what the problem was though :(

Then after bootrom-step-minimal.sh the step-2.sh script worked and i finally got access to TWRP :)

Thanks for your work!

Edit: Try to avoid kingoroot or the like because of potential malware. Downgrade the rom instead as noted in the instructions.
[Fire HD 8 and HD 10 Original Android Development] coliny59:
My Fire HD 10 has and orange gradient flickering on the home screen. I can't access settings, but am able to hit the square button (which there are not open apps). Also, the drop down works and I am not able to get to settings through there either. I can still access the stock recovery. This all happened after running the step1 script. What am I able to do to remedy this? It just flickers forever. Since I can't get to settings, I am not able to get to it through adb.

Edit: I am hardbricked, because i downgraded too low of a version of the OS. Oh well, this is the first android device I have ever bricked.
[Fire HD 8 and HD 10 Original Android Development] coliny59:
I ran through the unbrick thread, since my tablet was bricked after doing this. Looks like it is stuck at reading rpmb. What can I do next?

edit: I commented out all the lines that reads rpmb in main.py. Looks like it works now.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Didn't know where else to post this and isn't warranted its own thread. I was messing around and decided to look into the amzn_dha_tool again. Previously I attempted to run the self test command and never got a result. Perhaps it's because I didn't wait long enough. So I waited about a minute or two and it completed and spit out below output:

suez:/ $ su
suez:/ # amzn_dha_tool
[AMZN_DHA_TOOL]: Version v1.4
Usage: amzn_dha_tool [-t] [-d]

-h, --help Displays this help and exit
-c, --create Provisions Amazon DHA onto the device
-t, --test Perform a self-test on the Amazon DHA provisioned
-d, --display Displays the public modulus of the Amazon DHA and its HMAC
--oneline Shortens the output of -d option
-o, --dump Outputs the DHA public key/certificate to standard output
255|suez:/ # amzn_dha_tool -t
[AMZN_DHA_TOOL]: Version v1.4
Error in hardware/amazon_hal/security/amzn_dha/mediatek/amzn_dha_mtk.cpp:386 [Unable to execute TEE command]
amzndha_tool_self_test: Unable to sign data
255|suez:/ #

I do not have one of these tablets on the stock ROM to be able to complete this test and get further output. So I have no idea what comes next. I just thought it interesting enough that maybe somebody who does have one on stock can generate more. [MENTION=8132642]diplomatic[/MENTION] thought you might be interested in this or someone along your line.
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
OK... What is your aim for this? I don't have that tablet either (or any Fire HDs). This commands interacts with Trusted Execution Environment firmware. But it needs high privileges to do that.
[Fire HD 8 and HD 10 Original Android Development] Bryceshaw:
I am new to Linux and rooting/adb but I think I did everything correctly. I had to brick my tablet and when I tried the bootrom-step-minimal.sh my computer just stayed at waiting for bootrom. I am on Ubuntu 19.10
[Fire HD 8 and HD 10 Original Android Development] byfgjk:
5.3.7 owners SOL?

I am trying to root my fire hd 10 on the latest 5.3.7, I tried with both arm and arm64 mtk-su file and i get Failed critical init step 4, but the mtk-su thread says it's only good until 5.6.4 or older (5.3.7 is newer) so am I out of luck here, no way to get root or install lineageos? I know linux/scripts very well from a PC standpoint but mobile devices I have no clue how they work but I was able to follow the instructions correctly.

The part about the downgrade where it says "you must confirm by typing YES", I can't even get to that point due to not getting root. So no luck for me?
[Fire HD 8 and HD 10 Original Android Development] gRooster:
Worked for me on 5.3.7.0. To get root I used the offline method from here as someone suggested previously in this thread (Note: not the easier method mentioned at the very top). As for the unlocking part, I did get stuck on the "sudo ./bootrom-step-minimal.sh" step and had to open up the tablet and do the "short to ground" thing to get beyond that step. Beyond that I did not have any problems, and currently have LineageOS 14.1 running on it.

BTW: I did all this using Ubuntu 19.10.