FORUMS
Remove All Ads from XDA

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

728 posts
Thanks Meter: 800
 
By k4y0z, XDA Ad-Free Senior Member on 21st March 2019, 07:33 PM
Post Reply Email Thread
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).

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.
Attached Files
File Type: zip amonet-suez-v1.0.zip - [Click for QR Code] (16.66 MB, 344 views)
File Type: zip amonet-suez-v1.1.zip - [Click for QR Code] (16.68 MB, 184 views)
File Type: zip amonet-suez-v1.1.1.zip - [Click for QR Code] (16.69 MB, 104 views)
File Type: zip amonet-suez-v1.1.2.zip - [Click for QR Code] (16.69 MB, 2938 views)
File Type: zip amonet-suez-v1.1-return-to-stock.zip - [Click for QR Code] (8.57 MB, 420 views)
The Following 39 Users Say Thank You to k4y0z For This Useful Post: [ View ] Gift k4y0z Ad-Free
 
 
21st March 2019, 07:33 PM |#2  
OP Senior Member
Thanks Meter: 800
 
Donate to Me
More
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 0e8d:0003 MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID 0e8d:2000 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=0e8d, idProduct=0003, bcdDevice= 1.00
The Following 7 Users Say Thank You to k4y0z For This Useful Post: [ View ] Gift k4y0z Ad-Free
21st March 2019, 07:33 PM |#3  
OP Senior Member
Thanks Meter: 800
 
Donate to Me
More
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
The Following 6 Users Say Thank You to k4y0z For This Useful Post: [ View ] Gift k4y0z Ad-Free
21st March 2019, 07:34 PM |#4  
OP Senior Member
Thanks Meter: 800
 
Donate to Me
More
Source code:
https://github.com/chaosmaster/amonet/tree/mt8173-suez
https://github.com/chaosmaster/andro...ce_amazon_suez
https://github.com/chaosmaster/andro...el_amazon_suez
https://github.com/chaosmaster/andro...table_recovery
The Following 2 Users Say Thank You to k4y0z For This Useful Post: [ View ] Gift k4y0z Ad-Free
21st March 2019, 08:25 PM |#5  
Senior Member
Thanks Meter: 961
 
More
First unreserved !!!
The Following User Says Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
21st March 2019, 08:32 PM |#6  
OP Senior Member
Thanks Meter: 800
 
Donate to Me
More
Quote:
Originally Posted by bibikalka

First unreserved !!!

You are quick
21st March 2019, 09:03 PM |#7  
Junior Member
Thanks Meter: 0
 
Donate to Me
More
Now we need custom kernels and/or roms, any advice where to start?
21st March 2019, 10:04 PM |#8  
Quote:
Originally Posted by Murcielagoz99

Now we need custom kernels and/or roms, any advice where to start?

Download Lineage OS Sources, create device tree, create kernel tree, create vendor tree and compile ROM.

---------- Post added at 09:04 PM ---------- Previous post was at 08:58 PM ----------

@k4y0z in the ReadMe of the amonet source code says that the exploit is for the fire hd8 2018.
Is it correct or is it an error?
On the other hand, very good work!
21st March 2019, 10:36 PM |#9  
Senior Member
Flag Michigan
Thanks Meter: 90
 
More
sudo ./step-1.sh
"command not found"
Got the script to run using chmod. But it doesn't reboot,
"PL version 5
LK version 2
TZ Version 263
press enter to continue...
(doesnt reboot)
Dumping GPT
....
Modifying GPT (still hasnt reboot)


What am i am missing?
21st March 2019, 10:52 PM |#10  
GuyInDogSuit's Avatar
Senior Member
Flag Antelope, CA
Thanks Meter: 1,119
 
Donate to Me
More
BRAVO!! Fantastic work, my friend! I'm looking forward to the customization and ROMs that will soon follow.
21st March 2019, 10:59 PM |#11  
OP Senior Member
Thanks Meter: 800
 
Donate to Me
More
Quote:
Originally Posted by Rortiz2

Download Lineage OS Sources, create device tree, create kernel tree, create vendor tree and compile ROM.

Or start with the (minimal) TWRP device tree I linked to.

Quote:
Originally Posted by Rortiz2

@k4y0z in the ReadMe of the amonet source code says that the exploit is for the fire hd8 2018.
Is it correct or is it an error?
On the other hand, very good work!

I just forgot to update the Readme fixed it.

Quote:
Originally Posted by Michajin

sudo ./step-1.sh
"command not found"
Got the script to run using chmod. But it doesn't reboot,
"PL version 5
LK version 2
TZ Version 263
press enter to continue...
(doesnt reboot)
Dumping GPT
....
Modifying GPT (still hasnt reboot)


What am i am missing?

What OS are you using?
Is there no other output?

Try running
Code:
modules/gpt.py
Does that give any errors?
Post Reply Subscribe to Thread

Tags
root, twrp, unbrick, unlock

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes