[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)

[Klaus R]

Hi everybody. I´m almost running suez with twrp and lin16. Is it possible to flash FireOS by twrp as well? If so, is a special version recommended?
Thanx in advance!

 

[smithbill]

How do you downgrade?
I have downloaded update-kindle-Fire_HD10_7th_Gen-40.6.5.9_user_659662020 yo PC but how do I install it?

My post here should give you basic instructions (assuming you have TWRP & root?)

 

[Klaus R]

My post here should give you basic instructions (assuming you have TWRP & root?)

Thanx a lot, just what i was looking for.

There are links in this forum to newer versions, all from https://fireos-tablet-src.s3.amazonaws.com, up to v5.6.3.0. Do you think i can flash them also? Or should i stay with (v 5.3.7.3) you mentioned?

 

[smithbill]

Thanx a lot, just what i was looking for.

There are links in this forum to newer versions, all from https://fireos-tablet-src.s3.amazonaws.com, up to v5.6.3.0. Do you think i can flash them also? Or should i stay with (v 5.3.7.3) you mentioned?

I think (but can't recall the exact version numbers) that v5.3.7.3 = v5.6.3.0. Amazon screwed up the version numbers at some point and caused massive confusion about which version was which & which version was the latest.

As far as I'm aware, the version for download on the Amazon website (which is presumably v5.3.7.3 still) *is* the latest. Those versions you find elsewhere with later version numbers, are most likely BEFORE they changed the numbering and so are actually *older* than the one on the Amazon website.

Providing you have TWRP & are rooted, you can flash the FireOS version from Amazon. I strongly suggest that after flashing, you wipe Caches, reboot to TWRP Recovery (not to System!) then finally reboot again but to System - this may help ensure Amazon doesn't do something to overwrite your TWRP Recovery partition.

You can then flash Magisk (I think I included details of how to do that in my post). And then use Fire Toolbox to debloat (don't OVER debloat as removing some essential process can stop your FireHD10 booting & you will then have to start over by reflashing FireOS again).

 

[Klaus R]

As far as I'm aware, the version for download on the Amazon website (which is presumably v5.3.7.3 still) *is* the latest.

Ah, ok. Mine is on 5.7.0.0, with 659662020. That's exactly the number of that one linked by you to amazon website (v5.3.7.3).

This version seems to have patches by amazon to avoid bootloader cracking. k4yOz link deals with mtk-su to gain root temporarily, won`t work anymore. Retyre's approach link is with SuperSU, ran the script but no su possible. So i have to look for a different approch to get root. No root, no twrp

I succeeded with this post by @smartypantsuk to gain root. Now going up to twrp ...

 

[Klaus R]

My post here should give you basic instructions (assuming you have TWRP & root?)

May I ask why you chose that way to install magisk? Is there any problem with installing the usual way (zip in twrp & apk in running system)?

 

[smithbill]

May I ask why you chose that way to install magisk? Is there any problem with installing the usual way (zip in twrp & apk in running system)?

I tried Zip in TWRP & apk which all seemed to work, but when I then launched Magisk app, I think it told me Magisk wasn't installed & when I chose to install Magisk from within the Magisk app, the only method presented was to patch the boot.img

Anyway, patching the boot.img using the latest Magisk worked flawlessly & gave no problems - so seems like a good solution to me.

 

[smithbill]

Now going up to twrp ...

I'm not sure upgrading TWRP to the very latest version is a good idea, I'm sure I've read that it causes problems. I recommend sticking with a working version (I can't recall what version mine is, but 3.6.9_1.2 seems familiar, or is it 3.6.1_9.2? sorry, can't recall the right version number).

If your TWRP isn't broken then don't try fixing it by upgrading to a newer version.

 

[Klaus R]

I tried Zip in TWRP & apk which all seemed to work, but when I then launched Magisk app, I think it told me Magisk wasn't installed

I flashed Magisk zip in Twrp, then renamed it with twrp file manager to apk and copied it to /system. After system boot Magisk Manager App was not installed completely, but starting it downloaded some missing files. Afterwards it runs without probs.

 

[cRaZy-bisCuiT]

When trying to temporary bricking the device I get the following error. Which version is required?

sudo ./bootrom-step-minimal.sh
[2023-07-09 22:36:36.674250] Waiting for bootrom
[2023-07-09 22:36:47.738967] Found port = /dev/ttyACM0
[2023-07-09 22:36:47.776022] Handshake
[2023-07-09 22:36:47.796982] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
  File "/home/laurens/Dokumente/suez/amonet/modules/main.py", line 192, in <module>
    main()
  File "/home/laurens/Dokumente/suez/amonet/modules/main.py", line 82, in main
    handshake(dev)
  File "/home/laurens/Dokumente/suez/amonet/modules/handshake.py", line 11, in handshake
    dev.write32(0x10007000, 0x22000000)
  File "/home/laurens/Dokumente/suez/amonet/modules/common.py", line 163, in write32
    self.check(self.dev.read(2), b'\x00\x01') # arg check
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/laurens/Dokumente/suez/amonet/modules/common.py", line 90, in check
    raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

 

[CFKod]

When trying to temporary bricking the device I get the following error. Which version is required?

    raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

Could simply mean the short was not applied correctly, you will have to keep pressing the power button to turn on then turn off the tablet and start again.

 

[foysal105]

Hello everyone,
I don't know if my question is relevant or not. I have a windows based system and the codes here are for Linux user. Can anyone tell me how to use this process using windows 10??

 

[badbob001]

If I want to go back to stock, can I just download FireOS 5.6.2.0 bin file and use twrp to flash it?

Or do I really need to first flash back the original recovery image? I tried this: fastboot flash recovery bin/recovery.img, but it says my bootloader is locked.

 

[smithbill]

If I want to go back to stock, can I just download FireOS 5.6.2.0 bin file and use twrp to flash it?

Or do I really need to first flash back the original recovery image? I tried this: fastboot flash recovery bin/recovery.img, but it says my bootloader is locked.

Bit late answering, but my post #1622 should answer your question.

 

[Brixbuster]

Hello,

Revisiting hacking my Fire HD 10 after giving up in 2020 (I thought I killed it during the downgrade brick). Turns out I didn't and the tablet now displays the Amazon logo and the text "=> HACKED FASTBOOT mode: (0) - xyz, k40z" on screen. Where should I go from here?

Edit:
Gonna add some important info I forgot. I remeber the last thing I did years ago was being able to root, then perform the brick. My VM lost connection with the device, which lead me into thinking I killed it. Decided to try it out again, starting at the step where you type "sudo ./bootrom-step-minimal.sh." and the following step.

Thanks!

 

[psi78]

Hello,

Revisiting hacking my Fire HD 10 after giving up in 2020 (I thought I killed it during the downgrade brick). Turns out I didn't and the tablet now displays the Amazon logo and the text "=> HACKED FASTBOOT mode: (0) - xyz, k40z" on screen. Where should I go from here?

Edit:
Gonna add some important info I forgot. I remeber the last thing I did years ago was being able to root, then perform the brick. My VM lost connection with the device, which lead me into thinking I killed it. Decided to try it out again, starting at the step where you type "sudo ./bootrom-step-minimal.sh." and the following step.

Thanks!

I guess i'd install adb and fastboot on a pc if you already haven't, connect the device with usb, then flash the recovery of the tablet with twrp by entering these commands in a command prompt:

fastboot flash recovery /path/to/twrp.img

You can get twrp for suez from ggow's lineageos 16 thread.

If you manage to flash twrp then you can go on with installing LOS 12/14/16 by booting into twrp. To boot into twrp recovery turn the tablet on, and keep holding the power button + the Volume key next to the headphone jack until it boots into recovery.

 

[Brixbuster]

I guess i'd install adb and fastboot on a pc if you already haven't, connect the device with usb, then flash the recovery of the tablet with twrp by entering these commands in a command prompt:

fastboot flash recovery /path/to/twrp.img

You can get twrp for suez from ggow's lineageos 16 thread.

If you manage to flash twrp then you can go on with installing LOS 12/14/16 by booting into twrp. To boot into twrp recovery turn the tablet on, and keep holding the power button + the Volume key next to the headphone jack until it boots into recovery.

So I've installed adb and fastboot, and i tried this command but it just says "waiting for device." Using lsusb does see a device called "Device 007: (ID no.) MediaTek Inc. Wireless_Device. I'm now out of the brick but if I recall I had to go that route because my OS version was too new. I don't recall ever completing the downgrade or installing twrp either.

 

[psi78]

So I've installed adb and fastboot, and i tried this command but it just says "waiting for device." Using lsusb does see a device called "Device 007: (ID no.) MediaTek Inc. Wireless_Device. I'm now out of the brick but if I recall I had to go that route because my OS version was too new. I don't recall ever completing the downgrade or installing twrp either.

seems the tablet isn't connected in fastboot mode then. You can check with "fastboot devices" command too. Or try "adb devices" and if it shows up there use "adb reboot bootloader".

I think the kay0z scripts install a twrp version too, you could try to retry to execute some part of the script, maybe the second step, but i'm not sure, did this too long ago

Edit: Reread the first post i'd say. It says to use hacked fastboot mode just for flashing recovery with twrp by:
fastboot flash recovery bin/recovery.img

 

[coolcorner]

I have a weird situation, let me explain.

[Please refer to EDIT 3]
[Please refer to EDIT 1 and EDIT 2 as well]

1. I executed the script provided here https://forum.xda-developers.com/t/...ck-fire-hd-10-2017-suez.3913639/post-79169422 by k4y0z everything went fine, without any issues

2. I installed Lineage OS 16 from TWRP (have not flashed gapps or magisk yet), after installing Lineage OS I was trying to execute cleanup script by psi78 but it was not recognizing the script by giving file not found error. Even after trying to mount system, it failed to execute the script. At this point I thought the issue is with TWRP (as I could not even see the external SD card/storage), so I decided to flash TWRP again.

3. I downloaded TWRP_suez-180918 and flashed this img to recovery from Install option in TWRP, which messed up my TWRP recovery and my device now is not able to get into TWRP. (I select flash image, then selected the img file and selected recovery from the two options we get boot/recovery).

4. After flashing TWRP as in step 3, it rebooted and showed on the bottom left corner "recovery" but would not enter the TWRP. It kept boot looping between booting up and trying to enter TWRP recovery and would failed to do so.

5. Luckily as I had flashed Lineage OS I am able to boot into Lineage OS. Here I enabled USB debugging and tried to enter bootloader mode to flash recovery. While being in the Lineage OS, I can see my device under "adb devices" and I could issue "adb reboot bootloader" and the device was in bootloader mode (on the left bottom corner I can see "bootloader" mentioned), however when I try "fastboot devices" it would not show any device. [Please refer Edit 1 below]

Questions:

a) I am not sure if I am getting into the right bootloader, from what I searched I need to be under hacked bootloader to flash TWRP?
b) If yes, please let me know how can I get into that bootloader to flash TWRP again.

Or

Please let me know how can I fix my situation to flash TWRP.

Note: Currently, the device is able to boot normally into Lineage OS, which is without Gapps and does NOT have root access

EDIT 1: Seems like there was some issue with my USB drivers, had to reboot my PC a couple of times for device to get recognized in fastboot mode.
Now, when I try to flash twrp in fastboot, it says "FAILED (remote: the command you input is restricted on locked hw)"

EDIT 2: Did some more search in this thread and found out how to enter hacked bootloader, basically we need to use the script "boot-fastboot.sh" run the script while the device is off and connect the device to the PC which would boot the device and put the device into hacked bootloader mode. In this mode I did flash the TWRP image with "fastboot flash recovery_x twrp.img", then I issued the command "fastboot oem reboot-recovery", it seemed it tried to enter the TWRP recovery but it failed and booted into Lineage.

EDIT 3: After some more searching I figured I need to execute "boot-recovery" script, I ran that script and finally entered TWRP with that, and I was all happy about it and then......... However, after the reboot from TWRP, all I am seeing is a boot loop, now both scripts "boot-fastboot" or "boot-recovery" are not useful, neither its entering recovery or hacked bootloader, also it is NOT able to go past Amazon logo and boot into Lineage OS, I do not know what happened suddenly, it is basically in a boot loop. How do I fix this, please let me know?

 

[oryx.callotis]

I was on 5.6.8.0 Suez and got this to work, much obliged.

The mtk-su trick to get root didn't work though, so I followed this first;

HD 10 (2017): Offline rooting

Update: While this still works, there's an easier method here. Please try that first. Disclaimer #1: KingoRoot, dr.fone, and most other one-click rooting tools are characterized as malware. Should you use these tools? That decision is yours and...

forum.xda-developers.com

Then I went back to here from step 3 and eventually got Lineage 14.1 installed and working, with all the play store stuff installed. It worked fine, but video wasn't playing in anything except the Chrome browser.

Afterwards, I upgraded to 16.0 Lineage and then had to install google apps with NikGapps Core, as the Open Gapps package didn't work due to some system storage bug. Everything seems to work, video plays everywhere. I use Firefox Beta as my browser with uBlock, and youtube works. Revanced YouTube presumably works as this is Android 9 as well.