• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread
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. 🙏✌️❤️
 

jaagoodall

New member
Jun 4, 2021
3
0
Hi, I am completely new to this and I ran into a problem immediately. After I downloaded the zip files and extracted them, copied the binary to the required folder and then opened the command line I ran the command
Code:
sudo ./step-1.sh

but got the error:

Code:
sudo: ./step-1.sh: command not found

I enabled ADB, have everything installed, connected my tablet via usb, etc. Can anyone let me knw what I'm missing?

Edit: Just moved to amonet folder and it started working... must be tired

Thanks
 
Last edited:

koad1226

Member
Nov 3, 2014
16
0
I
Hi, I am completely new to this and I ran into a problem immediately. After I downloaded the zip files and extracted them, copied the binary to the required folder and then opened the command line I ran the command
Code:
sudo ./step-1.sh

but got the error:

Code:
sudo: ./step-1.sh: command not found

I enabled ADB, have everything installed, connected my tablet via usb, etc. Can anyone let me knw what I'm missing?

Edit: Just moved to amonet folder and it started working... must be tired

Thanks
I can't enable ADB since I can't go beyond the first set up screen. Is there any hope for me?
 

jaagoodall

New member
Jun 4, 2021
3
0
I

I can't enable ADB since I can't go beyond the first set up screen. Is there any hope for me?
Why cant you go past the first set up screen? If you are trying to prevent amazon automatically upgrading then I think it's been mentioned that you can skip setting up wifi by doing something along the lines of "set up WiFi" then selecting the "skip" option.
 

gRooster

Member
Feb 25, 2020
11
5
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.
 
Last edited:
  • Like
Reactions: Michajin

koad1226

Member
Nov 3, 2014
16
0
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.
Thank you. I will try both suggestions
 

gRooster

Member
Feb 25, 2020
11
5
Thank you. I will try both suggestions
Good luck, I hope it works out for you. Regarding the ribbon cable, it has been a little while since i did mine, but I seem to recall that it is fairly short, making it a little tough to line up with the socket. Just make sure it is in all the way and straight (IIRC there are tiny little tab stops on the side of the cable that should be right up against the socket). And make sure push the little black lever on the socket (that you lift to remove the cable,) back down to lock it in place.

Assuming that the FireOS version that you tried to install was for this tablet (HD 10 2017) and you got it from official sources, then I see no reason the touch screen should not be working, beyond the hardware (cable, etc)
 

koad1226

Member
Nov 3, 2014
16
0
Good luck, I hope it works out for you. Regarding the ribbon cable, it has been a little while since i did mine, but I seem to recall that it is fairly short, making it a little tough to line up with the socket. Just make sure it is in all the way and straight (IIRC there are tiny little tab stops on the side of the cable that should be right up against the socket). And make sure push the little black lever on the socket (that you lift to remove the cable,) back down to lock it in place.

Assuming that the FireOS version that you tried to install was for this tablet (HD 10 2017) and you got it from official sources, then I see no reason the touch screen should not be working, beyond the hardware (cable, etc)

Good luck, I hope it works out for you. Regarding the ribbon cable, it has been a little while since i did mine, but I seem to recall that it is fairly short, making it a little tough to line up with the socket. Just make sure it is in all the way and straight (IIRC there are tiny little tab stops on the side of the cable that should be right up against the socket). And make sure push the little black lever on the socket (that you lift to remove the cable,) back down to lock it in place.

Assuming that the FireOS version that you tried to install was for this tablet (HD 10 2017) and you got it from official sources, then I see no reason the touch screen should not be working, beyond the hardware (cable, etc)
☹☹ Sadly, I would have to resign myself to an unusable tablet. It is left with the external keyboard thing which I will try. But for now, it is sadness. My first ever tablet. Was going to treasure it like Jolly's Coat of many colours. And it was a gift. Hmmmmmm
 

RodMcKay

New member
Jun 25, 2021
1
0

gRooster

Member
Feb 25, 2020
11
5
Good evening everyone. I have a question regarding the available ROMs which can be flashed after I conducted this guide.

Are these the available ROMs for suez or am I missing something?

[discontinued][ROM][unlocked][suez] Lineage-12.1 [05 MAY 2020]
[discontinued][ROM][unlocked][suez] Lineage-14.1 [26 SEP 2019]
[ROM][testing][suez] Lineage-16.0 [12 FEB 2021]

I ask because I need at least Android 6 on my suez device. I am looking for the most stable >= Android 6 ROM I can find.

Thank you!
Those are the only ROMs that I know of. Lineage 14.1 is Android 7.1.2, and I have not had any stability issues with it, however, you would have to look to see if anything that you absolutely need is working. e.g. cameras do not work, so if you need the cameras, then it is not an option, etc.
 
  • Like
Reactions: RodMcKay

Top Liked Posts

  • There are no posts matching your filters.
  • 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