yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Boot to fastboot. Than check with "fastboot devices" in Terminal on PC that you see a device in Terminal showing. If you see your device you done right Till here.

Than after navigate to folder with the brick.sh run "sudo ./brick.sh" than type "YES" all big lettets. That was what i did.

Your fire hd will show that there is incoming data stream.

Here i had the writing failure. And yes you can extract in different folders
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
Ah thanks, go it. :good:

Would running Ubuntu through VirtualBox make a difference?

Edit: Would it work if I ran Ubuntu from a USB flash drive?
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Live usb will work. I tried it with live usb. You have not to forget first to install adb and fastboot an so on before start your try. The commands are in first post.

If it will work with a VM i don't know.

With plugged in device you can always check "adb devices" if fire hd 10 is booted to OS or "adb fastboot" when fire hd is in fastboot mode. Its the first you should check everytime before do something. Its my oppinion.
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
I used the file update-kindle-40.6.3.6_user_636558520.

I did the downgrading in PC. Do I need to use Linux to unbrick?
[Fire HD 8 and HD 10 Original Android Development] cyaclone:
TWRP

Which version of TWRP is best to use on the Fire HD 10 (2017)?
[Fire HD 8 and HD 10 Original Android Development] jawshthegreat:
Can't progress.

Hey there, I've been trying to get this working for awhile now and I'm stuck on the bricking step.

It just pauses at < waiting for any device >

Does anyone have any idea what I should do.
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Yes the steps for unbrick are for Linux. Just make a live usb and go through the steps. Good luck

---------- Post added at 06:06 AM ---------- Previous post was at 06:03 AM ----------

More informations are usefull.

1) Is it waiting when you run brick.sh?

2) Are you in fastboot mode?

3) Adb/fastboot drivers installed?

4) Do you youse a VM for Linux OS?
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
I created a live USB with LiLi usb Creator and an Ubuntu 15.0.4 ISO, and ran Virtualize_This_Key.exe, and Try Ubuntu instead of Install Ubuntu, and it stuck at ata1: EH complete. Am I doing it wrong? Sorry I am a Linux rookie.
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
I dont know how virtualize_this_key.exe work. I restarted my PC and booted from the live usb stick. Than choosed try instead of install.

Than install the drivers through terminal and so in like in first post described and i was ready to start.

Thats how i tried it. But no succsess till now. Have to try it again with other PC and other usb ports. Still have this writing failure.
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
After running sudo ./bootrom-step.sh, I got:

RuntimeError: Error: Serial protocol mismatch

Any idea?
[Fire HD 8 and HD 10 Original Android Development] davekaz:
hey Ive done everything and it worked.But now I just want to return to stock from Lineage rom Im on now. Just so I can backup amazon stock and return to Lineage because im having issues with rom .

davekaz@davekaz-Q405UA:~/Downloads$ sudo ./return-to-stock.sh

./return-to-stock.sh: line 3: functions.inc: No such file or directory

This is only for the "suez" (Amazon Fire HD10 (2017)), your device is a "mustang"

which is crazy. The only thing I've done was run unlock script and put lineage on it. I was on 564 so had to temp brick it and got through that which was a bit hairy. Now I just want to go back to scratch so i can do it over and do a backup in twrp with amazon stock and put lineage back on.. Help. I have a suez of course and never went on mustang rom...Something is really strange
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If you bricked via downgrading to the wrong firmware version, you will have to take the device apart and follow the unbricking instructions in Post #2

Looks like you're mixing up some stuff, also the return-to-stock needs to be extracted into the same directory where you extracted amonet.

That said, to do what you want to achieve, there is no reason to fully return to stock (which will also remove TWRP and restore the GPT)

You can just Install the amazon update file from TWRP if you wan't to just go back to FireOS without losing TWRP.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
Thanks for your quick reply. Andvtwrp don't see SD card either

Yes how do I achieve that. I did not mix up Douglas file. I followed any link that was given. I did extract all in same dir. That's why its strange. I never went to HD 8 link.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
mustang is the codename for the 2019 Fire 7 (9th gen).

The info being displayed is taken from the device:

adb shell getprop ro.product.name

So it might have something to do with the ROM currently installed.

To install stock ROM, just rename the bin file to zip and install it from TWRP.

Should probably wipe first.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
I'm on ggows rom lineage. It states suez in about tablet

Sorry to be a pain. Is there a link to stock bin file? Skip that found it its installed and loading at the moment
[Fire HD 8 and HD 10 Original Android Development] McTea:
step-1.sh errors

FireOS Version

Fire OS 5.6.4.0 (636558720)

temp root working.

shell@suez:/data/local/tmp $ ./mtk-su

UID: 0 cap: 3fffffffff selinux: permissive

shell@suez:/data/local/tmp #

I have already run step-1 but step-2 never worked and I ended up recovering from Fire Recovery. Now I get errors when running step-1. Anybody know what I should try next ?

Output from step-1 below.

Press Enter to Continue...

Dumping GPT

34+0 records in

34+0 records out

17408 bytes transferred in 0.003 secs (5802666 bytes/sec)

/data/local/tmp/gpt.bin: 1 file pulled. 0.4 MB/s (17408 bytes in 0.042s)

Modifying GPT

[2019-09-21 14:28:00.875295] Input GPT:

[2019-09-21 14:28:00.876890]

[2019-09-21 14:28:00.877034] Sector size (logical): 512 bytes

[2019-09-21 14:28:00.877158] Disk identifier (GUID): 331AF87B-C13A-455E-817B-28110D047018

[2019-09-21 14:28:00.877242] Partition table holds up to 128 entries

[2019-09-21 14:28:00.877324] This partition table begins at sector 2 and ends at sector 33

[2019-09-21 14:28:00.877406] First usable sector is 34, last usable sector is 61071326

[2019-09-21 14:28:00.877488] Other partition table is at sector 61071359

[2019-09-21 14:28:00.877568]

[2019-09-21 14:28:00.877707] Number Start (sector) End (sector) Size Name

[2019-09-21 14:28:00.878933] 1 1024 7167 3.00 MiB proinfo

[2019-09-21 14:28:00.880130] 2 7168 16383 4.50 MiB PMT

[2019-09-21 14:28:00.881047] 3 16384 18431 1024.00 KiB kb

[2019-09-21 14:28:00.881851] 4 18432 20479 1024.00 KiB dkb

[2019-09-21 14:28:00.882635] 5 20480 22527 1024.00 KiB lk

[2019-09-21 14:28:00.883407] 6 22528 32767 5.00 MiB tee1

[2019-09-21 14:28:00.884185] 7 32768 43007 5.00 MiB tee2

[2019-09-21 14:28:00.884957] 8 43008 123903 39.50 MiB metadata

[2019-09-21 14:28:00.885819] 9 123904 124927 512.00 KiB MISC

[2019-09-21 14:28:00.886617] 10 124928 141311 8.00 MiB reserved

[2019-09-21 14:28:00.887593] 11 141312 174079 16.00 MiB boot_x

[2019-09-21 14:28:00.888571] 12 174080 208895 17.00 MiB recovery_x

[2019-09-21 14:28:00.889377] 13 208896 3515391 1.58 GiB system

[2019-09-21 14:28:00.890037] 14 3515392 4383743 424.00 MiB cache

[2019-09-21 14:28:00.890683] 15 4383744 60619775 26.82 GiB userdata

[2019-09-21 14:28:00.891326] 16 60619776 60845055 110.00 MiB boot

[2019-09-21 14:28:00.892076] 17 60845056 61070335 110.00 MiB recovery

[2019-09-21 14:28:00.943949]

[2019-09-21 14:28:00.944105] Regenerate primary and backup GPT from input

[2019-09-21 14:28:00.944275] Writing regenerated GPT to gpt/gpt.bin.gpt

[2019-09-21 14:28:00.944509] Writing regenerated backup GPT to gpt/gpt.bin.bak

[2019-09-21 14:28:00.944683] Writing backup GPT offset to gpt/gpt.bin.offset

Traceback (most recent call last):

File "modules/gpt.py", line 323, in <module>

main()

File "modules/gpt.py", line 277, in main

part_list_mod1 = modify_step1(part_list)

File "modules/gpt.py", line 181, in modify_step1

assert partition['name'].decode("utf-16le").rstrip("\x00") == "userdata", "the last partition is not userdata, refusing modification"

AssertionError: the last partition is not userdata, refusing modification
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
But the firmware I used is the right one downloaded from Amazon official website, update-kindle-40.6.3.6_user_636558520.bin.

Does the device must have some battery? I suspect mine ran out of battery. I'm not sure if it's charging when plugged in after the bricking.
[Fire HD 8 and HD 10 Original Android Development] davekaz:
can I edit file back suez ? have no idea how that happened im changing it in build prop it states product board suez

name mustang

changed buildprop still coming up as mustang
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Step-1 has already succeeded on this device, you need to run step-2.

If your device was bricked due to a firmware downgrade you will have to open it up.

It is a problem with the ROM you have installed, just install stock FireOS and it should be back to suez.
[Fire HD 8 and HD 10 Original Android Development] diplomatic:
Your tablet was probably on the newer 5.6.4.0 build already. The one on the site is older than the current OTA release. You should have checked the build number. These tablets are being updated stealthily and most people don't even notice.
[Fire HD 8 and HD 10 Original Android Development] maxleebo:
Hi [MENTION=7104332]k4y0z[/MENTION], I tried to brick using the second zip you uploaded, after writing "Writing 'brick'...", it failed with error "FAILED (status read failed (No such device))"
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Did you check on the device display?

Also I added a new brick-suez.zip to the op, try again with that one.
[Fire HD 8 and HD 10 Original Android Development] airmark:
Thanks for this. Just to confirm for those that have asked, this DOES work from a Linux VM. You just need to keep re-mounting the USB device as at various points it is recognized as a different one (MediaTek, Amazon, Android device) so the VM doesn't see it. I spent some time waiting for it while the device was bricked before I realized it.
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
I was aware that my tablet had been self-updated to the latest build and lost root. I thought downgrading can help to reclaim root as mentioned in an earlier post.
[Fire HD 8 and HD 10 Original Android Development] wanderso:
Procedure for my unmolested HD 10 - do I have it right?

After sideloading the Google subsystem on my stock HD 10, and watching it fight with the Amazon system, I'm ready to root and fix the situation. Among other things, location is broken, and a host of Google apps really want location, e.g. YouTube TV.

This thread is pretty amazing, and the attention-to-detail, and support from [MENTION=7104332]k4y0z[/MENTION] is nothing short of spectacular. Sincere kudos.

My tablet: HD 10 2017 (suez), with Fire OS 5.6.4.0, build 636559820 (updated OTA)

My goal: custom recovery (e.g. TWRP), root privilege (e.g. Magisk), and a stripped Fire OS / Android system for now, until a compelling alternative is available. I really hate the thought of losing functionality (e.g. headphone codec) with an alternative system, but that's just me.

I've got a live-USB persistent Ubuntu 18.04 system, and I've done the package updates (python, adb, fastboot, dos2unix). I've extracted amonet-suez-v1.1.2.zip, mtk-su and, for good measure, brick-suez.zip. I've also enabled adb debugging on the tablet.

So I'm ready to start, but I've had trouble understanding the Original Post regarding the exact procedure for my situation. My current understanding for the steps are:

Stop and disable ModemManager, and attach tablet with microUSB cable.

Run sudo ./step-1.sh, wait for reboot, and type YES to brick my tablet.

Disconnect my tablet, run sudo ./bootrom-step-minimal.sh, plug the tablet back in and wait for it to reboot in "hacked fastboot" mode.

Run sudo ./fastboot-step.sh, and let the tablet reboot.

Reboot into TWRP (which should be installed) and install Magisk (which is already downloaded on the tablet).

Finally reboot into the rooted, pristine system, stay disconnected from Internet, and disable OTA updates, etc.

Is this even close to the correct sequence? Sorry to be such a n00b regarding Fire OS and the associated tools. The Fire 10 HD is such a nice piece of hardware, it's sad to see it saddled with the Amazon system.

wanders
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
If i understand k4y0z right. You have to run bootrom-step.sh instead of bootrom-step-minmal.sh

And i dont think there is mtk-su for the newest OTA 5.6.4.0, build 636559820.

So you dont need the step-1.sh and should start with the brick.sh. And then the the bootrom-step.sh and after that the fastboot-step.sh like described and like you posted.

Thats how i understand it. But i didnt managed it to root till now with my live usb Ubuntu. With the old brick.sh i had writing failures. I had no time to try with the new one. Maybe next week or so. If you manage it to brick and root your Fire HD 10 please let me know the exact steps you did.

If you are not sure to do it please wait for answer from k4y0z.
[Fire HD 8 and HD 10 Original Android Development] shadowcliffs:
First, can anyone else confirm that the latest non-rootable 5.6.4.0 be downgraded this way? I did this and my device is bricked. It's now in preloader mode. I'm pretty sure I used the right firmware for fire hd 10 7th, update-kindle_user_bin downloaded from the official website and the flash via adb sideload was successful.

Second, for a device in preloader mode cause by this, I have to open the back and short it in order to unbrick it, correct? And the back is actually the case casing the screen and I need to take the screen out from the case, so called back, correct?

Never mind, I opened the back or case with two credit card.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I would suggest to always start with step-1.sh first if mtk-su fails with "Failed critical init step..." then you will have to use the brick.sh and continue with bootrom-step.sh.

The assumption that you could downgrade from one 5.6.4.0 to the other was based on the fact that an upgrade like this typically doesn't change the LK, PL or TZ, which is apparently wrong in this case (who knows why they didn't bump the version number).

But as I've also told you before:
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
I tried with step-1.sh. How i suspected mtk-su failed with the "init step 4 error" Boot to bootloader and tried the brick.sh from first Post. Again "Failed (Status read failed (no such device))"

I tried different usb Ports and different Micro USB cables. Even tried on other PC. Still the same. After this Failure Fire HD boot normally to fire OS.

Dont know what to try next.

Edit:

@ k4y0z: Is the function of brick.sh the same when go through step-1.sh and came to the brick step? Maybe i should try the step-1.sh and delete the Code for try root with the mtk-su.

---------- Post added at 02:08 PM ---------- Previous post was at 01:31 PM ----------

The Failure with Status read failed came after the device starts to reboot. First in Terminal you see "writing brick" and in device you see that some data is recieved.

Than device Starts to reboot and the failure came like described above.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Are you sure you used the current version from OP?

I'll have to check it again, if it doesn't work.

Well it's similar, allthough step-1 would also already flash some parts of the exploit so you would only need bootrom-step-minimal.sh instead of bootrom-step.sh.

There is obviously a reason that mtk-su is used, since you won't be able to brick without having root.
[Fire HD 8 and HD 10 Original Android Development] madc4p:
I can confirm this. Downloaded the brick-suez.zip on the first page. Same behaviour for me.

The device display turn black after some time for a moment, the error appears and then it reboots normally.

Fire OS 5.6.4.0(636559820)

Build date: August 21, 2019, 2:54AM
[Fire HD 8 and HD 10 Original Android Development] wanderso:
device mode for brick.sh?

What mode does the device (Fire HD 10) need to be in to run brick.sh? On my Ubuntu system, adb can see the device:

$ sudo adb devices
List of devices attached
G000N607908605P7	device

but ./brick.sh simply hangs, waiting for the device:

$ sudo ./brick.sh
Brick preloader to continue via bootrom-exploit? (Type "YES" to continue)
YES
Bricking PL Header
Check instructions on device

< waiting for any device >

I've updated adb and fastboot packages, but no joy. Where am I messing up?

wanders
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
For run brick.sh you have to be in bootloader mode. So you have to reboot to bootloader. Just type "sudo adb reboot bootloader" after reboot you see on screen if you are in bootloader mode. I mean there stand fastboot or something like this.

With "sudo fastboot devices" you should see your device like with "adb devices".

Good Luck.
[Fire HD 8 and HD 10 Original Android Development] fchae:
for some reason nothing happen after I run the sudo ./step-1.sh

https://imgur.com/a/YbAuno6
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Type "adb devices" first. The deamon for adb is not started when you start all from the beginning. Start the step-1.sh after you see your device with adb devices.
[Fire HD 8 and HD 10 Original Android Development] fchae:
I typed adb devices, but the device name did not appear in there. what should i do?

I enabled ADB already
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Then there is Problem with connection. Did you mounte the device all through? It seems like you are using a VM. I think you have to pass the connection through to your VM. I tried this all with live usb there you doesnt have such Problems. I never tried it with VM.

Airmark mentioned it with the mounting issue.
[Fire HD 8 and HD 10 Original Android Development] fchae:
so, i did that and I had to brick my device to complete the process. I did and run "sudo ./bootrom-step.sh" and I got "Waiting for bootrom" I connected my device but nothing happened
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
Did you shut down your device after brick? Did you run brick.sh or step-1.sh?
[Fire HD 8 and HD 10 Original Android Development] flipcombedfield:
Problem with sudo ./brick.sh

I can confirm this too. Same build. Did it while in FASTBOOT MODE.

❯ 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' (111616 KB)...
OKAY [ 6.566s]
Writing 'brick'...
FAILED (status read failed (No such device))
Finished. Total time: 41.493s
[Fire HD 8 and HD 10 Original Android Development] wanderso:
brick.sh - me, too...

I'm getting brick.sh failure as well. This is Fire OS 5.6.4.0, (636559820), not rooted. I'm running from an Ubuntu 18.04 live stick. Here's my session:

$ sudo adb devices
List of devices attached
G000N607908605P7	device

$ sudo adb reboot bootloader
$ sudo fastboot devices
G000N607908605P7	fastboot
$ 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' (111616 KB)...
OKAY [ 6.950s]
Writing 'brick'...
FAILED (status read failed (No such device))
Finished. Total time: 39.387s

The device then rebooted to Fire OS without any action by me.

Any help would be appreciated...
[Fire HD 8 and HD 10 Original Android Development] TehBosch:
Same for me also
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
brick.sh currently doesn't work with build 9820.

I will have to update it to make it compatible.
[Fire HD 8 and HD 10 Original Android Development] delbuenno:
Hi, when I try to return to stock with "fastboot flash recovery bin/recovery.img" it just hangs on "<waiting for any device>"

I am in hacked fastboot mode and when I type "sudo fastboot devices" it shows it is connected as:

G000NT05825303NS

Have I missed a step or any other suggestions on what I am dong wrong?

Thanks
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Try with sudo:

sudo fastboot flash recovery bin/recovery.img
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
Oh... I have the same build and running into similar problems.

Thanks for helping k4y0z :good:
[Fire HD 8 and HD 10 Original Android Development] 911medic:
So is it true to say that for now, if you're on 9820, you cannot use this unlock method?
[Fire HD 8 and HD 10 Original Android Development] lovaduck:
EDIT: Found it. :o

https://www.xda-developers.com/how-to-install-magisk/

First I want to thank k4 for this, got TWRP installed in a flash! Fantastic job.

Now I don't want to ask stupid questions and I can search the forum and google... but couldn't find a guide for installing Magisk on the Fire HD 10.

All I find is for phones. Which zip file should I download to TWRP for proper Magisk install?

thanks again!
[Fire HD 8 and HD 10 Original Android Development] ksh0127:
So basically I'm trying to get Lineage OS on my Amazon Fire HD 10 (2017). I currently have Fire OS 5.6.4.0(636559820) and I'm fed up with amazon's stock os. I just want a some custom rom (anything that's not Fire OS). Is using brick.sh the only way right now? Or is there another way to do it?
[Fire HD 8 and HD 10 Original Android Development] thestudentOO:
On the New Update Version that you have brick.sh is not working. No other possibility to downgrade or root at the Moment. Maybe k4y0z have time to modify brick.sh that it will work with the New 9820 Version.

---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------

Downgrade with Amazon recovery will brick your device. Don't Do that. You will have to open your device if brick with Amazon Firmware when you try to downgrade.

---------- Post added at 08:47 AM ---------- Previous post was at 08:47 AM ----------

Downgrade with Amazon recovery will brick your device. Don't Do that. You will have to open your device if brick with Amazon Firmware when you try to downgrade.
[Fire HD 8 and HD 10 Original Android Development] 911medic:
I believe the only way is to use the brick.sh method in the first post of this thread, but if you're on build 9820, you can't right now until the brick.sh is updated to work with that build.

I'm in the same boat as you...waiting.
[Fire HD 8 and HD 10 Original Android Development] stolirocks:
Yes
[Fire HD 8 and HD 10 Original Android Development] ducksoup18:
Moving over to here from here: https://xdaforums.com/showpost.php?p=80551845&postcount=550

Im going to attempt the unbrick method as it mentions that if the screen doesnt display anything i may still not have to open up the device. Does that sound/seem correct?

Also, it seems like my windows box is having issues with this all (including virtualbox and wsl). Would a mac work or do i have to get my hands on a linux machine? i have a pi somewhere that i might be able to configure to do this, otherwise im gonna just return this thing to amazon.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
You WILL have to open the device, since you bricked by downgrading through stock recovery.

Using Windows is not supported and Virtualbox/WSL is not recommended, allthough some have claimed success.

A RasPi will work, but booting a live-Linux would probably be the easiest option.

You can use this ISO, which already has all the required prerequisites installed:

https://github.com/amonet-kamakiri/fireiso/releases