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

Search This thread
By:
Advanced…
S

Sus_i

Senior Member
Apr 9, 2013
1,858
811
ProjectRoot

ProjectRoot

Member
Oct 20, 2022
12
1
Sus_i said:
github.com

GitHub - amonet-kamakiri/fireiso: ISO with patched kernel for kamakiri and amonet

ISO with patched kernel for kamakiri and amonet. Contribute to amonet-kamakiri/fireiso development by creating an account on GitHub.
github.com github.com
Use rufus to flash it to an usb storage stick.

Rufus - Create bootable USB drives the easy way

Rufus: Create bootable USB drives the easy way
rufus.ie
Click to expand...
Click to collapse
i found out that the flashdrive malfunctions and cant properly copy the files, thanks for trying, i dont have another one and unfortunately cant afford another one either
 
  • Like
Reactions: nowaranowara2006
S

Sus_i

Senior Member
Apr 9, 2013
1,858
811
ProjectRoot said:
i found out that the flashdrive malfunctions and cant properly copy the files, thanks for trying, i dont have another one and unfortunately cant afford another one either
Click to expand...
Click to collapse
You can do the same (without an usb storage) in a virtual machine, like VMware, just a few downloads and then boot the live iso image in the VM. Though it's a bit harder to connect the device, since you will need to choose if the device connects to the guest or the host system, but it will work too.
 
ProjectRoot

ProjectRoot

Member
Oct 20, 2022
12
1
Sus_i said:
You can do the same (without an usb storage) in a virtual machine, like VMware, just a few downloads and then boot the live iso image in the VM. Though it's a bit harder to connect the device, since you will need to choose if the device connects to the guest or the host system, but it will work too.
Click to expand...
Click to collapse
I didnt found the software you mentioned but i found another, called Oracle VM Virtual Box, i will give it a try
 
ProjectRoot

ProjectRoot

Member
Oct 20, 2022
12
1
Sus_i said:
You can do the same (without an usb storage) in a virtual machine, like VMware, just a few downloads and then boot the live iso image in the VM. Though it's a bit harder to connect the device, since you will need to choose if the device connects to the guest or the host system, but it will work too.
Click to expand...
Click to collapse
sorry for double post, yes it kinda works but no idea which version of linux to install, theres tons of options, i tried the fireiso part, but the sudo apt, gives errors saying no apt command and stuff like that.....
 
smithbill

smithbill

Senior Member
Jun 24, 2007
262
69
Liverpool
ProjectRoot said:
What you need:
  • A Linux installation or live-system

Where to get that? its not included in the guide
Click to expand...
Click to collapse
Go to Linux Mint at https://linuxmint.com/ download it & burn it to a USB memory stick, then boot your laptop from the USB memory stick & run it as a Live/demo *without* installing it to your laptop.

Last time I tried, Ubuntu wasn't suitable (can't recall the reason) but Linux Mint worked perfectly for the job.

(And VirtualBox is far simpler to use than VMWare)
 
Last edited:
  • Like
Reactions: Sus_i
kovren

kovren

New member
Nov 2, 2022
1
0
I rooted my Suez (or so I thought), tried to install Magisk, and it got stuck in a bootloop. I can access Amazon recovery.

When I try to run the bootrom scripts,
I get the "Serial protocol mismatch" error,
which I assume is from my Fire OS version not being downgraded properly.

I was on Fire OS 5.7.0.0.

Can I adb sideload the 5.7.0.0 update to kinda reset all of this? I tried searching for this update, but 5.6.2.0 or so was the highest I could find. Amazon itself only has up to 5.3.7.3.

At a bit of a loss.

Edited:
Per psi78's comment, I decided to go ahead and just flash the newest firmware on Amazon's webpage. It worked fine. Was then able to reroot and follow this guide to get TWRP installed. Thanks.
 
Last edited:
P

psi78

Senior Member
Feb 22, 2020
205
55
Sony Xperia Z5
Amazon Fire HD 8 and HD 10
kovren said:
I rooted my Suez (or so I thought), tried to install Magisk, and it got stuck in a bootloop. I can access Amazon recovery.

When I try to run the bootrom scripts,
I get the "Serial protocol mismatch" error,
which I assume is from my Fire OS version not being downgraded properly.

I was on Fire OS 5.7.0.0.

Can I adb sideload the 5.7.0.0 update to kinda reset all of this? I tried searching for this update, but 5.6.2.0 or so was the highest I could find. Amazon itself only has up to 5.3.7.3.

At a bit at a loss.
Click to expand...
Click to collapse
Amazon mixed up the version numbers, 5.3.7.3 is actually the newest FireOS for suez, 5.6.2.0 is an older version. So you could adb sideload 5.6.2.0 and root then i think.
 
  • Like
Reactions: mbwd and kovren
mbwd

mbwd

Senior Member
Feb 6, 2014
106
9
psi78 said:
Amazon mixed up the version numbers, 5.3.7.3 is actually the newest FireOS for suez, 5.6.2.0 is an older version. So you could adb sideload 5.6.2.0 and root then i think.
Click to expand...
Click to collapse

I previously (like 2 years ago) rooted my FireHD 10 2017 7th Gen, but then gave it to my wife and it seems to have autoupdated/lost root. It currently says it is running FireOS version 5.7.0.0.

Is it correct that I need to brick it because I am on > 5.6.4.0 (see excerpt from op):

NOTE: If you are on firmware 5.6.4.0 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all).
Click to expand...
Click to collapse

Or is 5.7.0.0 really 5.3.7.3?

@kovren, what did you do - and did it work?
 
J

joseph230

Senior Member
Aug 15, 2010
175
99
After bricking, and unbricking my Fire HD10 7th Gen, finally I have TWRP installed. I can go to "hacked fastboot" from TWRP as well.

For next steps, I have couple of quetsions:

- Does this mean I have "Unlocked Bootloader" now? If not, is it possible to unlock? how?
- I want to Insall lineage OS. I see version 18.1 listed in this forum. Is flashing through TWRP is safe even if my bootloader is not unlocked?
 
L

likwidchz

Senior Member
May 14, 2022
71
16
joseph230 said:
After bricking, and unbricking my Fire HD10 7th Gen, finally I have TWRP installed. I can go to "hacked fastboot" from TWRP as well.

For next steps, I have couple of quetsions:

- Does this mean I have "Unlocked Bootloader" now? If not, is it possible to unlock? how?
- I want to Insall lineage OS. I see version 18.1 listed in this forum. Is flashing through TWRP is safe even if my bootloader is not unlocked?
Click to expand...
Click to collapse
Hey there,

- Does this mean I have "Unlocked Bootloader" -- Yes, its unlocked.
- I want to Insall lineage OS. I see version 18.1 listed in this forum. -- Yes this is how you do it.

In TWRP you select a zip file and install it through TWRP.

look for any one of these files on various sites.
1669222051414.png


With TWRP installed it makes it so that you can flash on different "Roms/OS's" without fear of bricking the device. If the flash is bad, big deal you can just boot into TWRP and try a different one.


Best of luck.
 
  • Like
Reactions: joseph230
J

joseph230

Senior Member
Aug 15, 2010
175
99
likwidchz said:
Hey there,

- Does this mean I have "Unlocked Bootloader" -- Yes, its unlocked.
- I want to Insall lineage OS. I see version 18.1 listed in this forum. -- Yes this is how you do it.

In TWRP you select a zip file and install it through TWRP.

look for any one of these files on various sites.
View attachment 5768479

With TWRP installed it makes it so that you can flash on different "Roms/OS's" without fear of bricking the device. If the flash is bad, big deal you can just boot into TWRP and try a different one.


Best of luck.
Click to expand...
Click to collapse
Thank you for quick response.
 
J

joseph230

Senior Member
Aug 15, 2010
175
99
likwidchz said:
Hey there,

- Does this mean I have "Unlocked Bootloader" -- Yes, its unlocked.
- I want to Insall lineage OS. I see version 18.1 listed in this forum. -- Yes this is how you do it.

In TWRP you select a zip file and install it through TWRP.

look for any one of these files on various sites.
View attachment 5768479

With TWRP installed it makes it so that you can flash on different "Roms/OS's" without fear of bricking the device. If the flash is bad, big deal you can just boot into TWRP and try a different one.


Best of luck.
Click to expand...
Click to collapse
I installed Lineage 16 successfully but cannot get OpenGapps installed. Even Pico version throws not enough system space error!
Under TWRP I can see that system partition has over 300MB of free space. Gapps pico is 188MB zipped!
How did you resolve that issue?
 
L

likwidchz

Senior Member
May 14, 2022
71
16
joseph230 said:
I installed Lineage 16 successfully but cannot get OpenGapps installed. Even Pico version throws not enough system space error!
Under TWRP I can see that system partition has over 300MB of free space. Gapps pico is 188MB zipped!
How did you resolve that issue?
Click to expand...
Click to collapse
You can use an older version of Lineage, not the latest as it has been confirmed that the Gapps doesnt work. I recall pico working. Search around.

The other option is sideload everything or install a different package manager apkpure or something else.

Older version of lineage is also fine. Just experiment. The more you experiment with things the more knowledge you will have in the end. With forums, you do have to piecemeal it all together. Keep at it though.
 
P

psi78

Senior Member
Feb 22, 2020
205
55
Sony Xperia Z5
Amazon Fire HD 8 and HD 10
joseph230 said:
After bricking, and unbricking my Fire HD10 7th Gen, finally I have TWRP installed. I can go to "hacked fastboot" from TWRP as well.

For next steps, I have couple of quetsions:

- Does this mean I have "Unlocked Bootloader" now? If not, is it possible to unlock? how?
- I want to Insall lineage OS. I see version 18.1 listed in this forum. Is flashing through TWRP is safe even if my bootloader is not unlocked?
Click to expand...
Click to collapse
for Fire HD 10 2017 aka "suez" there is no LineageOS 18.1 ROM at the moment. Probably you mean the ROM for karnak which isn't for your device
joseph230 said:
I installed Lineage 16 successfully but cannot get OpenGapps installed. Even Pico version throws not enough system space error!
Under TWRP I can see that system partition has over 300MB of free space. Gapps pico is 188MB zipped!
How did you resolve that issue?
Click to expand...
Click to collapse
Read the LOS 16 thread for suez/Fire HD 2017, especially the last pages. You can repartition (could break something) or debloat the system partition to make opengapps pico work. Bitgapps (gapps rebuild by @TheHitMan) may also work, it's smaller than opengapps pico.
See https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/
Click to expand...
Click to collapse
 
Last edited:
  • Like
Reactions: joseph230
A

amberlink

New member
May 13, 2017
3
0
I get to step 3, and when I do, it just sits there with nothing happening. What am I doing wrong?

Edit: I get
* daemon not running; starting now at tcp:5037
* daemon started successfully
But that's all it will ever show
 
Last edited:
C

_ck_

Senior Member
Apr 9, 2011
383
55
Thanks to everyone maintaining various things for this and adding instructions along the way.

Just to help others in 2022-2023 to the Fire HD10 2017

This has been lost in time on this thread but you CAN still root with 5.7.0.0 you just CANNOT use mtk-su because it's been patched against so the instructions are outdated, hence the confusion when it errors-out.

But you MUST root before you can install TWRP, there is no other way, otherwise you get all the errors.

You need to go to a far more manual exploit, it looks tedious but you only have to do it once and maybe 10-15 minutes tops once you have a working ubuntu live usb or virtual install

forum.xda-developers.com

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

Read this whole guide before starting. This is for the 7th gen Fire HD10 (suez). Current version: amonet-suez-v1.1.2.zip NOTE: This process does not require you to open your device, but should something go horribly wrong, be prepared to do...
forum.xda-developers.com forum.xda-developers.com

This root method is nice because it's all offline, no wifi needed.

Very very hard to brick the HD10 which is nice, I got into a bootloop at first try but even Amazon's own ADB sideload will still take the stock image from their website and recover, just tedious.
 
Last edited:
You must log in or register to reply here.

Similar threads

X
Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root
Replies
1K
Views
336K
jumstec
jumstec
K
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2017 (douglas)
Replies
793
Views
237K
T
Thomas131
K
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3
Replies
981
Views
211K
M
masterpost2004
ggow
  • Locked
[discontinued][ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019]
Replies
801
Views
198K
engloa
engloa
ggow
[discontinued][ROM][unlocked][suez] Lineage-12.1 [05 MAY 2020]
Replies
740
Views
154K
M
Mlinko6

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 81
    K
    k4y0z
    Read this whole guide before starting.

    This is for the 7th gen Fire HD10 (suez).

    Current version: amonet-suez-v1.1.2.zip


    NOTE: This process does not require you to open your device, but should something go horribly wrong, be prepared to do so.


    NOTE: This process will modify the partition-table (GPT) of your device.


    NOTE: Your device will be reset to factory defaults (including internal storage) during this process.


    What you need:
    • A Linux installation or live-system
    • A micro-USB cable

    Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
    Code: 
    sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix

    1. Extract the attached zip-file "amonet-suez-v1.1.2.zip" and open a terminal in that directory.


    NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder


    2. Enable ADB in Developer Settings

    3. Start the script:
    Code: 
    sudo ./step-1.sh

    Your device will now reboot into recovery and perform a factory reset.

    NOTE: If you are on firmware 5.6.4.0 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
    If you chose the brick option, you don't need to run step-2.sh below:


    Make sure ModemManager is disabled or uninstalled:
    Code: 
    sudo systemctl stop ModemManager
sudo systemctl disable ModemManager

    After you have confirmed the bricking by typing "YES", you will need disconnect the device and run
    Code: 
    sudo ./bootrom-step-minimal.sh
    Then plug the device back in.

    It will then boot into "hacked fastboot" mode.
    Then run
    Code: 
    sudo ./fastboot-step.sh



    NOTE: When you are back at initial setup, you can skip registration by selecting a WiFi-Network, then pressing "Cancel" and then "Not Now"
    NOTE: Make sure you re-enable ADB after Factory Reset.


    4. Start the script:
    Code: 
    sudo ./step-2.sh

    The exploit will now be flashed and your device will reboot into TWRP.

    You can now install Magisk from there.


    Going back to stock
    Extract the attached zip-file "amonet-suez-v1.1-return-to-stock.zip" into the same folder where you extracted "amonet-suez-v1.1.2.zip" and open a terminal in that directory.
    You can go back to stock without restoring the original partition-table, so you can go back to unlocked without wiping data.
    Just use hacked fastboot to
    Code: 
    fastboot flash recovery bin/recovery.img

    If you want to go back completely (including restoring your GPT):
    Code: 
    sudo ./return-to-stock.sh

    Your device should reboot into Amazon Recovery. Use adb sideload to install stock image from there. (Make sure to use FireOS 5.6.3.0 or newer, otherwise you may brick your device)

    Important information

    In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
    TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.

    Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)

    Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.

    TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).

    For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).

    It is still advised to disable OTA.


    Very special thanks to @xyz` for making all this possible and putting up with the countless questions I have asked, helping me finish this.
    Special thanks also to @retyre for porting the bootrom-exploit and for testing.
    Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
    Thanks also to @bibikalka and everyone who donated :)
    Thanks to @TheRealIntence and @b1u3m3th for confirming it also works on the 64GB model.
    View
    12
    K
    k4y0z
    Unbricking

    If Recovery OR FireOS are still accessible there are other means of recovery, don't continue.

    If your device shows one of the following symptoms:
    1. It doesn't show any life (screen stays dark)
    2. You see the white amazon logo, but cannot access Recovery or FireOS.

    If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
    1. Make sure the device is powered off, by holding the power-button for 20+ seconds
    2. Start bootrom-step.sh
    3. Plug in USB

    In all other cases you will have to open the device and partially take it apart.
    Follow this guide by @retyre until (including) step 8..
    At Step 6. you will replace
    Code: 
    sudo ./bootrom.sh
    with
    Code: 
    sudo ./bootrom-step.sh
    Should the script stall at some point, restart it and replug the USB-cable (Shorting it again should not be necessary unless the script failed at the very beginning).

    If the script succeeded, put the device back together.
    When you turn it on, it should start in hacked fastboot mode.
    You can now use
    Code: 
    sudo ./fastboot-step.sh
    This will flash TWRP and reset your device to factory defaults, then reboot into TWRP.


    Checking USB connection
    In lsusb the boot-rom shows up as:
    Code: 
    Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone

    If it shows up as:
    Code: 
    Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
    instead, you are in preloader-mode, try again.

    dmesg lists the correct device as:
    Code: 
    [ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
    View
    10
    K
    k4y0z
    Changelog
    Version 1.1.2 (26.03.2019)
    • Fix regenerating GPT from temp GPT

    Version 1.1.1 (26.03.2019)
    • Fix unbricking procedure

    Version 1.1 (25.03.2019)
    • Update TWRP-sources to twrp-9.0 branch
    • TWRP uses kernel compiled from source
    • Add scripts to use handshake2.py to enter fastboot/recovery

    Features.

    • Uses 5.6.3 LK for full compatibility with newer kernels.
    • Hacked fastboot mode lets you use all fastboot commands (flash etc).
    • Boots custom/unsigned kernel-images (no patching needed)
    • TWRP protects from downgrading PL/TZ/LK
    • For the devs: sets printk.disable_uart=0 (enables debug-output over UART).

    NOTE: Hacked fastboot can be reached via TWRP.

    NOTE: Hacked fastboot doesn't remap partition names, so you can easily go back to stock
    View
    10
    S
    smartypantsuk
    k4v7uk said:
    This sounds promising. Is there any documentation on here to get SuperSu on the Fire? It would be great if i could get this method to work. I really dont want to open the thing. Thanx for your help.
    Click to expand...
    Click to collapse
    You'll need a linux distrubution to work from, a live boot cd/usb will work fine.
    Don't use WSL (Subsystem for Linux) on Windows 10 as usb support doesn't work properly, or at all, for anything other than usb storage devices.

    This guide was part of a larger guide on Github, adapted from Retyre's XDA Guide.

    Root on Fire HD10 2017 5.6.9.0 (not tried on other systems)

    1. Download the root exploit code (alternate link SHA256 8bfc3d5c75964e5fa28c8ffa39a87249ba10ea4180f55f546b2dcc286a585ea8) and Super_SU18+ (alternate link SHA256 b572c1a982d1e0baeb571d3bc0df7f6be11b14553c181c9e0bf737cc4a4fbbfd).
      wget -c "http://myphone-download.wondershare.cc/mgroot/20165195.zip" "http://myphone-download.wondershare.cc/mgroot/SuperSU_18+.zip"
    2. Unzip them both to a 20165195 directory.
      unzip -u 20165195.zip -d 20165195 && unzip -u SuperSU_18+.zip -d 20165195
    3. Check the 20165195 directory contains all the needed files.
      $ ls -1 20165195
      Matrix
      Superuser.apk
      ddexe
      debuggerd
      fileWork
      install-recovery.sh
      krdem
      mount
      patch_boot.sh
      pidof
      push_root.sh
      start_wssud.sh
      su
      su_arm64
      supersu.zip
      supolicy
      toolbox
      wsroot.sh
    4. Push the directory to the tablet.
      adb push 20165195 /data/local/tmp
    5. Login to the tablet.
      adb shell
    6. Make the files executable.
      chmod 755 /data/local/tmp/20165195/*
    7. Run the exploit. You should see a lot of output while it runs.
      /data/local/tmp/20165195/Matrix /data/local/tmp/20165195 2
      If the script executes successfully, the final lines of output should display the memory location that was exploited (may be different than 0x7fab64c000) and a value of 0 for <Exploit> and <Done>. If it fails, check the Troubleshooting section:
    8. exploited 0x7fab64c000=f97cff8c
      end!!!!!!!
      <WSRoot><Exploit>0</Exploit></WSRoot>
      <WSRoot><Done>0</Done></WSRoot>

    9. You can verify root with su.
      [email protected]:/ $ su
      su
      [email protected]:/ #
    10. Back on your computer, download SuperSU 2.82 SR5 apk (alternate link SHA256 2c7be9795a408d6fc74bc7286658dfe12252824867c3a2b726c1f3c78cee918b) and install it to the tablet with adb.
      adb install "eu.chainfire.supersu_2.82-SR5-282_minAPI9(nodpi)_apkmirror.com.apk"
    11. Open up the SuperSU app on the tablet, tap Get Started, then tap Continue and select Normal to update the app. Select Reboot after it is done installing to reboot the tablet.
    12. After the tablet reboots, open SuperSU app again, tap on Settings tab, then tap Default access, then choose Grant.
    13. Log in to your tablet.
      adb shell
    14. Switch to superuser and delete directories /data/data-lib/com.wondershare.DashRoot and /data/data-lib/wondershare.
      su
      rm -r /data/data-lib/com.wondershare.DashRoot /data/data-lib/wondershare

    Once rooted, you can start the main guide on here for TWRP installation and skip past the root part.
    Notes: At stage 7, running the exploit, you may find get an error instead of a successful output like above.
    If you get this or similar, try rebooting your Fire HD and try again:

    <WSRoot><Exploit>0x00000332</Exploit></WSRoot>
    check done
    sched_setaffinity: Function not implemented<WSRoot><Exploit>0x00000382</Exploit></WSRoot>
    FAIL : load1 --> /sepolicy
    <WSRoot><Exploit>0x00000341</Exploit></WSRoot>
    <WSRoot><Exploit>0x00000881</Exploit></WSRoot>
    <WSRoot><Done>0x00000172</Done></WSRoot>

    I had to reboot once to get it to work. It's also worth noting that, even though it was successful the second time, i still received a function not implemented error, but it still worked. This is the part that you're looking for to be sucessful:

    <WSRoot><Exploit>0</Exploit></WSRoot>
    <WSRoot><Done>0</Done></WSRoot>
    View
    9
    K
    k4y0z
    Just uploaded version 1.1.
    If you are already unlocked you can just install the zip-file from TWRP to update.

    Version 1.1 (25.03.2019)
    • Update TWRP-sources to twrp-9.0 branch
    • TWRP uses kernel compiled from source
    • Add scripts to use handshake2.py to enter fastboot/recovery
    View

New posts