Amazon Fire HD 10 (amazon-suez)

From postmarketOS
Jump to: navigation, search
Amazon Fire HD 10 (7th gen)
Fire HD 10 booted and running weston.
Fire HD 10 booted and running weston.
Manufacturer Amazon
Name Fire HD 10 (7th gen)
Codename amazon-suez
Released 2017
Category testing
Original software FireOS 5.3.7.0
Hardware
Chipset Mediatek MT8173
CPU Quad-core (2x1.8 GHz Cortex-A72 & 2x1.4 GHz Cortex-A53)
GPU PowerVR G6250
Display 1200 x 1920 IPS LCD
Storage 32GB or 64GB
Memory 2 GB
Architecture aarch64
Features
USB Networking
Works
Flashing
Partial
Touchscreen
Works
Display
Works
WiFi
Broken
Xwayland
Works
FDE
Mainline
Battery
Broken
3D Acceleration
Broken
Accelerometer
Broken
Audio
Broken
Bluetooth
Broken
Camera
Broken
GPS
Broken
Mobile data
Unavailable
SMS
Unavailable
Calls
Unavailable
USB OTG



Contributors

  • Hadi Charara <hadicharara@ymail.com>

Maintainer(s)

Users owning this device

How to enter flash mode

You have to have your bootloader unlocked through this method: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639

Entering fastboot through normal methods will not work as we need to access the hacked bootloader. Normal fastboot doesn't let us flash in the required partitions.

Simply hold volume up while powering it up to access TWRP. From TWRP you can reboot into the hacked bootloader as needed.

Installation

From TWRP, you have access to ADB sideload, which you can use to install the recovery zip exported from pmbootstrap, or you can reboot into the hacked bootloader to access fastboot. You have to take the following things into consideration:

- fastboot has a limit on the filesize of files to be flashed. rootfs cannot be flashed from fastboot. Only boot can be flashed. To flash rootfs, use ADB sideload.

- Since the unlocking of the bootloader modified the paritition scheme of the device, to flash into it, you have to execute: fastboot flash boot_x FILE_TO_BE_FLASHED

- The default recovery zip generated by pmbootstrap flashes boot.img into the paritition named 'boot'. This won't work as the hacked bootloader resides there. Instead, we have to unpack the zip file, modify line 5 of chroot/install_options and lines 69 and 70 of chroot/bin/pmos_install_functions to replace boot by boot_x. Repack the zip file afterwards and it should be good to go.

See also