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

Search This thread

pkgingo

Member
Jan 11, 2010
24
7
Can someone please post their GPT data?
k4y0z said:
script for hd 10 7th generation
I ran the script posted in the OP but it never saved out any gpt data and now twrp has loaded and I loaded a rom but I have no other partitions. I cant authorize adb in the rom to dump the partition table properly.

TIA!

Update: I managed to finally figure it out. It looks like the lineage 14 scripts do NOT have the mkfs commands that lineage 12 does, so you must first flash lineage 12 before you can use another distribution.
 
Last edited:

KingLeaf

New member
Dec 16, 2015
3
0
Confirm this worked for me as well for FIreOS 5.6.8.0! Moved to Lineage 12.1 (need working camera).
Just a small tip. Don't waste your time with Windows Subsystem for Linux. Better use normal installation or live-system instead.
How? I can't retain root after reboot on 5.6.8.0.
 
Aug 13, 2014
8
0
Hi guys,

I need your help! I try to return back to stock, because I want to sell my Fire HD tablet.
I try to run the return script on a linux live system.
However I get two errors
./return-to-stock.sh: line 7: dos2unix: command not found
This is only for the "suez" (Amazon Fire HD10 (2017)), your device is a ""

The second line is kind of funny, because when I run adb shell getprop ro.product.name it shows me suez....
Ive installed the latest fire os update via TWRP, so there shouldnt be a problem.

Maybe you have an idea and can help me?
Thanks in advance for your help :)
 

Attachments

  • Untitled.png
    Untitled.png
    48.6 KB · Views: 67

rG-

Senior Member
Sep 20, 2010
72
6
so i found my old fire hd 10 and decided to try this out! workes very well! GJ!

PS: i had to use the "bricked version" without step 2.sh!
 

smithbill

Senior Member
Jun 24, 2007
207
48
Liverpool
I've been using my rooted Fire HD 10 on FireOS for months and it's been working well. However, I just got the notification that a new Magisk was available (I had been on Magisk 20.4). So I downloaded the new Magisk zip (v21.3) and went into TWRP and wiped Cache/dalvik, flashed Magisk zip, wiped Cache/dalvik again and rebooted.

It crept through the Fire "Optimising system storage and applications" screen and is stuck at the end. I tried power down & reboot, it was then just stuck on the Fire screen. I tried rebooting to TWRP and wiping caches again, but the same happens - it's now been sat on the "Optimising system storage and applications" screen for an hour.

So it would appear that Magisk 21.3 does not work with Fire HD 10 (2017) on FireOS 5.6.8.0.

Anyone got any ideas how to resolve this?
 
Last edited:

sga999

Senior Member
Mar 13, 2012
809
112
I've been using my rooted Fire HD 10 on FireOS for months and it's been working well. However, I just got the notification that a new Magisk was available (I had been on Magisk 20.4). So I downloaded the new Magisk zip (v21.3) and went into TWRP and wiped Cache/dalvik, flashed Magisk zip, wiped Cache/dalvik again and rebooted.

It crept through the Fire "Optimising system storage and applications" screen and is stuck at the end. I tried power down & reboot, it was then just stuck on the Fire screen. I tried rebooting to TWRP and wiping caches again, but the same happens - it's now been sat on the "Optimising system storage and applications" screen for an hour.

So it would appear that Magisk 21.3 does not work with Fire HD 10 (2017) on FireOS 5.6.8.0.

Anyone got any ideas how to resolve this?

I am also having problems with 21.3. (The difference is that I have a custom rom installed). I also tried 21.2 and that fails. But 21.1 does work (and 20.4).

I'm not that familiar with GitHub, but it looks like someone reported a similar problem #3636, 15 days ago on a Sony Z1C. It's about 9 down from your report on that site. Let's hope someone gets around to addressing this problem soon.

By the way, the newest Magisk Manager 8.06 seems to work fine with 20.4 or 21.1.
 

smithbill

Senior Member
Jun 24, 2007
207
48
Liverpool
I am also having problems with 21.3. (The difference is that I have a custom rom installed). I also tried 21.2 and that fails. But 21.1 does work (and 20.4).

That's interesting, I tried Magisk 21.1 but it also left me unable to boot FireOS 5.6.8.0. But I could easily enough revert back to Magisk 20.4 and it booted back up with no problems. I didn't bother trying 21.0 as I assumed it would also fail.

The Magisk Manager update works fine, just Magisk itself doesn't.
 

Korin67

Senior Member
  • Feb 24, 2018
    174
    90
    I am new to suez. Sorry if his is a FAQ. I got suez recently, and the firmware is 5.6.8.0. OP says that I need to downgrade (brick). This means: set suez in fastboot mode (adb reboot bootloader) and run brick.sh?
    When I did it, brick seems fail and FireOS reboot. Is there newer version of brick.sh?? I have experience with douglas and karnak, but new to suez.
    Thank you for your advice.
     

    Korin67

    Senior Member
  • Feb 24, 2018
    174
    90
    I am new to suez. Sorry if his is a FAQ. I got suez recently, and the firmware is 5.6.8.0. OP says that I need to downgrade (brick). This means: set suez in fastboot mode (adb reboot bootloader) and run brick.sh?
    When I did it, brick seems fail and FireOS reboot. Is there newer version of brick.sh?? I have experience with douglas and karnak, but new to suez.
    Thank you for your advice.
    Sorry guys, this is a response to myself. I should have to search more before posting this. I found that brick.sh is no more useful (for newer firmware). We have to use Kingo Root approach instead to brick the tablet.
    Thank you for your time.
     

    Korin67

    Senior Member
  • Feb 24, 2018
    174
    90
    Succeeded but need your help. By following the @ajvasudhar method. I could successfully install TWRP from FireOS 5.6.8.0. I installed LOS14.1 and reboot. But boot animation repeats endlessly. What I noticed is in TWRP /data was not mounted. I can turn off the tablet by pressing PWR button nearly 30 secs. But I cannot enter TWRP. The key sequence is VolDown+PWR?? The tablet always go into LOS14.1 animation that does not boot now. Please help.

    Edit:
    After root the tablet. I did ./step-1.sh to brick. Then, ./bootrom-step-minimal.sh, lastly ./fastboot-step.sh all from amonet version 1.1.2

    Edit2:
    Okay, I can find how to enter twrp. It is VolUP(or Dn, the key closer to PWR)+PWR. I cannot mount /data with this version of TWRP (3.2.3-O). Is there newer version for suez? With this version I always see Keep System Read only? message. And I can mount System and Cache. I cannot not mount Data.

    Edit3:
    Solved. I had to do Format Data partition in TWRP. After this everything is okay. Thank you for all the informative articles in this thread.
     
    Last edited:
    • Like
    Reactions: M. Allison

    fuzzynco

    Senior Member
    Oct 29, 2008
    581
    32
    HTC One Max
    Samsung Galaxy S9
    I did the software install on a usb live xubuntu 20.4 (lte).
    I setup adb on the tablet and got them connected ok.
    I do now see 'serial-number device' reply to 'adb devices'.

    Running step-1.sh says its using mtk-su and then pushes the 3 files okay.

    error message:
    Failed critical init step 4
    This firmware cannot be supported

    error just keeps repeating.

    The tablet is Fire HD 10 2017
    OS: 5.6.4.0 (636559820)

    It's never connected to the internet.

    I thought it was supposed to ask permission for the workaround for the 5.6.4.0 issue.
    It didn't. I did download 'brick-suez' and 'return-to-stock' zips and unzipped them.

    What should I do?

    Fuzzy
     

    Korin67

    Senior Member
  • Feb 24, 2018
    174
    90
    I did the software install on a usb live xubuntu 20.4 (lte).
    I setup adb on the tablet and got them connected ok.
    I do now see 'serial-number device' reply to 'adb devices'.

    Running step-1.sh says its using mtk-su and then pushes the 3 files okay.

    error message:
    Failed critical init step 4
    This firmware cannot be supported

    error just keeps repeating.

    The tablet is Fire HD 10 2017
    OS: 5.6.4.0 (636559820)

    It's never connected to the internet.

    I thought it was supposed to ask permission for the workaround for the 5.6.4.0 issue.
    It didn't. I did download 'brick-suez' and 'return-to-stock' zips and unzipped them.

    What should I do?

    Fuzzy

    I am new to suez, just finished my TWRP job. If incorrect, more knowledgeable people might correct.

    I think in your case, you need to brick your tablet first. If the 'brick.sh' works, it is simple. Otherwise, you first need to root your tablet. Be sure in this case, 'su' command in adb shell environment guide to superuser. Under this environment you can use step-1.sh guides you to brick your tablet. Once your tablet be bricked, bootrom-step.minimal.sh will guide to fastboot mode.
     

    KingNeox

    New member
    Feb 12, 2021
    1
    0
    I need youre help please. i tried to root my fire hd 10 (2017) as it was described in the first post here. After the step

    "sudo systemctl stop ModemManager
    sudo systemctl disable ModemManager"

    the Tablet didnt start again and now when it is connected to the computer there is only a connect and disconnect sound after 20 seconds in an endless loop. No reactions on the tablet, the screen stay black. Because it stay black i also cant acess to the recovery mode. Can i rescue my tablet with any steps?

    Thanks for youre help.
     

    fuzzynco

    Senior Member
    Oct 29, 2008
    581
    32
    HTC One Max
    Samsung Galaxy S9
    I did the software install on a usb live xubuntu 20.4 (lte).
    I setup adb on the tablet and got them connected ok.
    I do now see 'serial-number device' reply to 'adb devices'.

    Running step-1.sh says its using mtk-su and then pushes the 3 files okay.

    error message:
    Failed critical init step 4
    This firmware cannot be supported

    error just keeps repeating.

    The tablet is Fire HD 10 2017
    OS: 5.6.4.0 (636559820)

    It's never connected to the internet.

    I thought it was supposed to ask permission for the workaround for the 5.6.4.0 issue.
    It didn't. I did download 'brick-suez' and 'return-to-stock' zips and unzipped them.

    What should I do?

    Fuzzy

    Should I run brick.sh, then bootrom-minimal.sh?

    I'm a little lost as I thought if it tested for > 5.6.3 and failed it would ask for
    permission to do the brick and then continue the script? Instead it continues without
    asking and then fails with 'critical init step 4' error message.

    It appears to have pushed the 3 three files to the tablet successfully, using mtk-su.

    Fuz
     

    Korin67

    Senior Member
  • Feb 24, 2018
    174
    90
    Should I run brick.sh, then bootrom-minimal.sh?

    I'm a little lost as I thought if it tested for > 5.6.3 and failed it would ask for
    permission to do the brick and then continue the script? Instead it continues without
    asking and then fails with 'critical init step 4' error message.

    It appears to have pushed the 3 three files to the tablet successfully, using mtk-su.

    Fuz

    Unfortunately, brick.sh does not work. bootrom-minimal.sh only works if your tablet is bricked. That means you first have to brick your tablet. To brick your tablet without using brick.sh (now it is useless), you need to root your tablet first. Article #1321 (the original article it refers) gives you the clue.
     

    Robi2003

    Member
    Mar 30, 2020
    7
    0
    3D
    sudo ./bootrom-step-minimal.sh
    re-connecting to usb cable
    At this point i had to hold the power button for 20 seconds. and a message came up asking me to press enter after removng the short (no short was applied, so just press enter)
    anther message came up asking if i had bricked the device, press enter. at this point it began injecting the payload.

    I cannot make this step, I get this error:

    Bildschirmfoto von 2021-02-17 12-53-56.png
     

    fuzzynco

    Senior Member
    Oct 29, 2008
    581
    32
    HTC One Max
    Samsung Galaxy S9
    Unfortunately, brick.sh does not work. bootrom-minimal.sh only works if your tablet is bricked. That means you first have to brick your tablet. To brick your tablet without using brick.sh (now it is useless), you need to root your tablet first. Article #1321 (the original article it refers) gives you the clue.

    The tablet is as it came from Amazon with Fire OS 5.6.4.0. mtk-su does still work.
    Which version (fire os) was brick.sh written for?

    Fuz
     

    Korin67

    Senior Member
  • Feb 24, 2018
    174
    90
    I have no idea. I also tried with OS 5.6.4.0. When I tried brick.sh, the tablet just rebooted to FireOS as if nothing applied. It could not bring the tablet into brick.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 1
      Just one more question... Where can I find the latest magisk canary zip file version 23001? Can someone link me up, please? Thank you!!
      the apk is flashable, just rename it to a zip....

      1
      the apk is flashable, just rename it to a zip....

      I always rename canary apk to canary.zip and flash or I patch my boot.img on my phone, pixel 4xl, but I saw the other day a few people posted that they flashed the APK in twrp. I was like "WTF!!" 😂🤣😁 Android has come a LOOOONG way!!! I'm grateful we still have the creater and maintainer of magisk, topjohnwu, still around and doing all he does, especially after he was recently hired on to Google on the development team. I always laugh a lil because he is an Apple developer as well. I remember all the fuss back in the day about people hating Apple.. topjohnwu is definitely a top notch dev and we are blessed to have him as we are blessed to have everyone who participates in development. 🙏✌️❤️
      1
      Touch screen not working. I strongly believe the digitizer is intact.
      You previously stated that you opened it up to do the short, so my first guess would be that you damaged the ribbon cable for the screen, or did not seat it in properly. I would open it back up and try reseating the cable, making sure that it is inserted all the way, etc. Beyond that IDK, maybe whatever version of FireOS you installed does not have the correct drivers, I would try reinstalling whatever version (specifically for this tablet) was previously working. You could also try a USB keyboard to see if it will allow you to interact with the setup screens, but I do not think that is gonna fix anything related to the touch screen.
    • 77
      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.
      12
      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
      10
      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
      9
      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