Jump to content

Amazon Fire HD 10 (amazon-suez): Difference between revisions

From postmarketOS Wiki
Nooneshsh (talk | contribs)
No edit summary
Exkc (talk | contribs)
No edit summary
 
(15 intermediate revisions by 10 users not shown)
Line 6: Line 6:
| imagecaption = Fire HD 10 booted and running weston.
| imagecaption = Fire HD 10 booted and running weston.
| releaseyear = 2017
| releaseyear = 2017
| originalsoftware = FireOS 5.3.7.0
| originalsoftware = Android
| chipset = Mediatek MT8173
| originalversion = ? (FireOS 5.3.7.0)
| chipset = MediaTek MT8173
| cpu = Quad-core (2x1.8 GHz Cortex-A72 & 2x1.4 GHz Cortex-A53)
| cpu = Quad-core (2x1.8 GHz Cortex-A72 & 2x1.4 GHz Cortex-A53)
| gpu = PowerVR G6250
| gpu = PowerVR G6250
Line 14: Line 15:
| memory = 2 GB
| memory = 2 GB
| architecture = aarch64
| architecture = aarch64
<!-- the following status_* questions should be answered with Y - yes, P - partial, N - no, or left blank (for untested or unknown) -->
| type = tablet
| status_usbnet = Y
| status_usbnet = Y
| status_flashing = P
| status_flashing = P
Line 24: Line 25:
| status_mainline =  
| status_mainline =  
| status_battery = N
| status_battery = N
| status_3d = Y
| status_3d = N
| status_accel =  
| status_accel = N
| status_audio = N
| status_audio = N
| status_bluetooth =  
| status_bluetooth = N
| status_camera =  
| status_camera = N
| status_gps =  
| status_gps = N
| status_mobiledata = -
| status_mobiledata = -
| status_sms = -
| status_sms = -
Line 35: Line 36:
| status = Boots into Weston. XWayland not tested yet. Proprietary WiFi driver available but not tested.
| status = Boots into Weston. XWayland not tested yet. Proprietary WiFi driver available but not tested.
| booting = yes
| booting = yes
 
| pmoskernel = 3.18.19
<!-- you can also use these lines if you need to:
if the device haven't originally ran Android OS, e.g. Nokia N900
| n-android =  ✔
Version of the kernel that pmos is running
| pmoskernel = 3.13.18
see Unixbench page on wiki
| whet_dhry = 0.0
Is OTG available, not used in wiki
| status_otg = -
| status_otg = -
-->
| whet_dhry =
}}
}}


== Contributors ==
== Contributors ==
* nooneshsh
* Hadi Charara <hadicharara@ymail.com>


== Maintainer(s) ==
<!-- Only if this device doesn't run on linux-postmarketos yet! -->
<!-- This person needs to be willing to answer questions from users of this device -->


== Users owning this device ==
== Users owning this device ==
{{Device owners}}
{{Device owners}}
<!-- autogenerated, use {{Owns device|devicepage|notes}} on your profile page -->
<!-- use _ instead of spaces in device page name, e.g. {{Owns device|HTC_Desire_(htc-bravo)|custom notes}}-->
<!-- you may need to purge page cache to see changes (more->purge cache)-->
<!-- you can use {{My devices}} on your profile page to show table with all your devices -->


== How to enter flash mode ==
== How to enter flash mode ==
Line 77: Line 63:


- 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.
- 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.
== Mainline ==
{| class="wikitable"
|-
! scope="col"| Parts
! scope="col"| Components
! scope="col"| In Torvalds tree?
! scope="col"| In chromiumOS-5.4 kernel?
|-
| scope="row"| Chipset
| MT8173
| Yes ([https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/mediatek/mt8173.dtsi mt8173.dtsi])
| Yes ([https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-5.4/arch/arm64/boot/dts/mediatek/mt8173.dtsi mt8173.dtsi])
|-
| scope="row"| GPU
| PowerVR GX6250
| No
| Yes ([https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-5.4/drivers/gpu/drm/img-rogue/ img-rouge])
|-
| scope="row"| Touch Screen
| ft5726NEi
| Yes ([https://github.com/torvalds/linux/blob/master/drivers/input/touchscreen/edt-ft5x06.c edt-ft5x06.c])
| Yes ([https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-5.4/drivers/input/touchscreen/edt-ft5x06.c edt-ft5x06.c])
|-
| scope="row"| Accelerometer
| BMA253
| No
| No
|-
| scope="row"| ALSPS
| STK3X1X/ltr559
| Yes ([https://github.com/torvalds/linux/blob/master/drivers/iio/light/stk3310.c stk3310.c]) / Yes ([https://github.com/torvalds/linux/blob/master/drivers/iio/light/ltr501.c ltr501.c])
| Yes ([https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-5.4/drivers/iio/light/stk3310.c stk3310.c]) / Yes ([https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-5.4/drivers/iio/light/ltr501.c ltr501.c])
|-
| scope="row"| Sound
| rt5514
| Yes ([https://github.com/torvalds/linux/blob/master/sound/soc/codecs/rt5514.c rt5514.c])
| Yes ([https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-5.4/sound/soc/codecs/rt5514.c rt5514.c])
|-
|}


== See also ==
== See also ==
* {{MR|1193|pmaports}} Initial merge request
* {{MR|1193|pmaports}} Initial merge request
<!--
* {{Device package|amazon-suez}}
Link to related GitLab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234):
* {{Kernel package|amazon-suez}}
* {{MR|CHANGEME|pmaports}} Initial merge request
* {{issue|CHANGEME|pmaports}} Some related issue
You can also add normal web links:
* [https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100 Replicant wiki page]
-->
<!--
If you manage to get your device packages merged, uncomment links below and change DEVICE_CODENAME with the actual one.
* [https://gitlab.com/postmarketOS/pmaports/tree/master/device/testing/device-DEVICE_CODENAME Device package]
* [https://gitlab.com/postmarketOS/pmaports/tree/master/device/testing/linux-DEVICE_CODENAME Kernel package]

Latest revision as of 11:43, 4 November 2023

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
Type tablet
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
Software
Original software Android
Original version ? (FireOS 5.3.7.0)
postmarketOS
Category testing
Pre-built images no
postmarketOS kernel 3.18.19
Features
Flashing
Partial
USB Networking
Works
Internal storage
No data
SD card
No data
Battery
Broken
Screen
Works
Touchscreen
Works
Multimedia
3D Acceleration
Broken
Audio
Broken
Camera
Broken
Camera Flash
No data
Connectivity
WiFi
Broken
Bluetooth
Broken
GPS
Broken
NFC
No data
Miscellaneous
FDE
No data
HDMI/DP
No data
Sensors
Accelerometer
Broken
Magnetometer
No data
Ambient Light
No data
Proximity
No data
Hall Effect
No data
Haptics
No data
Barometer
No data


Contributors

  • Hadi Charara <hadicharara@ymail.com>


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.

Mainline

Parts Components In Torvalds tree? In chromiumOS-5.4 kernel?
Chipset MT8173 Yes (mt8173.dtsi) Yes (mt8173.dtsi)
GPU PowerVR GX6250 No Yes (img-rouge)
Touch Screen ft5726NEi Yes (edt-ft5x06.c) Yes (edt-ft5x06.c)
Accelerometer BMA253 No No
ALSPS STK3X1X/ltr559 Yes (stk3310.c) / Yes (ltr501.c) Yes (stk3310.c) / Yes (ltr501.c)
Sound rt5514 Yes (rt5514.c) Yes (rt5514.c)

See also