Huawei Honor 7 (huawei-aum)
Jump to navigation
Jump to search
![]() AUM | |
Manufacturer | Huawei |
---|---|
Name | Honor 7 (AUM) |
Codename | huawei-aum |
Released | 2018 |
Category | testing |
Original software | Android |
Original version | 8.0 |
postmarketOS kernel | 3.18.68 |
Hardware | |
Chipset | Qualcomm Snapdragon 430 (MSM8937) |
CPU | Octa-core 1.4 GHz Cortex-A53 |
GPU | Adreno 505 |
Display | 720x1440 |
Storage | 16/32 GB |
Memory | 2/3 GB |
Architecture | aarch64 |
Type | handset |
USB Networking |
Works |
---|---|
Flashing |
Partial |
Touchscreen |
Works |
Display |
Works |
WiFi | |
FDE | |
Mainline | |
Battery |
Works |
3D Acceleration | |
Audio | |
Bluetooth | |
Camera | |
GPS | |
Mobile data | |
SMS | |
Calls | |
USB OTG | |
NFC | |
Accelerometer | |
---|---|
Magnetometer |
Unavailable |
Ambient Light | |
Proximity | |
Hall Effect |
Unavailable |
Barometer |
Unavailable |
Power Sensor |
Unavailable |
Keyboard |
Unavailable |
---|---|
Touchpad |
Unavailable |
USB-A |
Unavailable |
HDMI/DP |
Unavailable |
Ir TX |
Unavailable |
FOSS bootloader | |
Contents
Contributors
- Frost_I7 (I'll try to keep the wiki page up-to-date with the available info when I'm active.)
Users owning this device
- Frost I7 (Notes: Unlocked. Stock.)
Information
![]() |
This device has a separate boot (so-called ramdisk) and the kernel partitions. |
![]() |
This device has a locked bootloader. |
Technically, this should work with both AUM and LND models that have MSM89*7 SoC.
How to enter flash mode
Hold Power and Volume Down buttons (while connected to the USB) to boot into the fastboot.
Installation
![]() |
fastboot boot command works on this device, so you can use pmbootstrap flasher boot to boot without flashing. |
![]() |
eRecovery has its own kernel partition, so you can install it there, but you need to flash via TWRP. |
You need to separately flash initramfs as ramdisk and vmlinuz as kernel.
You can flash it to either the system (ramdisk and kernel), to the first recovery (recovery_ramdisk and kernel) or to the second recovery (erecovery_ramdisk and erecovery_kernel).
Use mkbootimg.
Create a ramdisk image:
$ ./mkbootimg --kernel /dev/null --ramdisk /path/to/file/initramfs --cmdline 'androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.bootdevice=7824900.sdhci slub_min_objects=12 unmovable_isolate1=2:192M,3:224M,4:256M androidboot.selinux=permissive buildvariant=user' --base 0x80000000 --kernel_offset 0x00008000 --ramdisk_offset 0x02000000 --second_offset 0x00f00000 --tags_offset 0x00000100 --os_version 8.0.0 --os_patch_level 2019-01 --pagesize 2048 --header_version 0 --hashtype sha1 -o /path/to/file/pmOS_RAMDISK.img
Create a kernel image:
$ ./mkbootimg --kernel /path/to/file/vmlinuz --ramdisk /dev/null --cmdline 'androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.bootdevice=7824900.sdhci slub_min_objects=12 unmovable_isolate1=2:192M,3:224M,4:256M unmovable_isolate2=2:64M,3:80M,4:80M androidboot.selinux=permissive buildvariant=user' --base 0x80000000 --kernel_offset 0x00008000 --ramdisk_offset 0x02000000 --second_offset 0x00f00000 --tags_offset 0x00000100 --os_version 8.0.0 --os_patch_level 2019-01 --pagesize 2048 --header_version 0 --hashtype sha1 -o /path/to/file/pmOS_KERNEL.img
Downstream
hwtest
$sudo hwtest
Category Model Path Status Value
framebuffer mdssfb_80000 /sys/class/graphics/fb0 working U:720x1440p-59
framebuffer mdssfb_a0000 /sys/class/graphics/fb1 working
input huawei,ts_kit /dev/input/event3 working
input gpio-keys /dev/input/event2 working
input fingerprint /dev/input/event1 working
input qpnp_pon /dev/input/event0 working
xrandr
$xrandr
Can't open display
Issues
- Touchscreen stops responding after 5 minutes of inactivity.
- Can't get the Wi-Fi to work.