HTC Droid DNA (htc-monarudo)

From postmarketOS


Note This device is still running on armhf, although the processor supports armv7. If you own it, change it and test it that way.


Icon WARNING: This device is not recommended for future use with postmarketOS due to its armhf architecture. Alpine Linux (the distribution that postmarketOS extends) has been considering dropping it.
In some cases, the processor of the device may support the armv7 architecture. If so, you can modify the device package and change the architecture accordingly.
HTC Droid DNA /
Butterfly
HTC Droid DNA
HTC Droid DNA
Manufacturer HTC
Name Droid DNA /
Butterfly
Codename htc-monarudo
Released 2012
Category testing
Original software Android
Original version 4.1 (Linux 3.0.31)
Hardware
Chipset Qualcomm Snapdragon S4 Pro (APQ8064)
CPU Quad-core 1.5 GHz Krait
GPU Adreno 320
Display 1080x1920
Storage 16 GB
Memory 2 GB
Architecture ARMhf
This device is marked as not booting.
Features
USB Networking
Flashing
Touchscreen
Display
WiFi
FDE
Mainline
Battery
3D Acceleration
Audio
Bluetooth
Camera
GPS
Mobile data
Internal storage
SMS
Calls
USB OTG
NFC
Sensors
Accelerometer
Magnetometer
Ambient Light
Proximity
Hall Effect
Barometer
Power Sensor
Misc
Built-in DVB
Camera Flash
Keyboard
Touchpad
USB-A
HDMI/DP
Ir TX
Ir RX
Stylus
Memory Card
Haptics
Ethernet
FOSS bootloader
This device is based on the Snapdragon 600.
See the SoC page for common tips, guides and troubleshooting steps

Contributors

  • Ross Schulman

Current Status

  • Kernel builds
  • Trying to boot the kernel with fastboot boot ... freezes the phone, as does using pmbootstrap.py flasher boot
  • Trying to flash the kernel with pmboostrap.py flasher flash_rootfs or flash_kernel results in a remote:not allowed error, although this may be related to a corrupted partition table on my particular device.

What works

  • Nothing yet

Links

Partition layout

device size filesystem description
mmcblk0p16 25 MiB vfat ~
mmcblk0p17 5 MiB vfat ~
mmcblk0p24 10 MiB ext4 ~
mmcblk0p31 48 MiB vfat ~
mmcblk0p32 928 MiB ext4 android system
mmcblk0p33 320 MiB ext4 android cache
mmcblk0p34 5.8 GiB ext4 android userdata

What have I tried so far

  • Pulling flash offsets from two different dlx ROMS. Both match each other and what we're using.
  • adb pushing the .img file and attempting to use dd to write into the system partition. Only succeeded in mangling the partition.
  • Reflashing CM-12 just to be sure that the phone isn't totally bricked, but CM installs just fine and boots properly.

Some theories

  • Ross Schulman's particular HTC Droid DNA is individually broken and/or not unlocked properly (but see the ability to flash and boot multiple different CyanogenMod versions)
  • Somehow the offsets are incorrect (haunting feeling this is it, but numbers were taken from previously mentioned CyanogenMod boot.img)
  • The dlx doesn't actually use the m7's kernel at all (this doesn't seem plausible given the number of places that have indicated it is true)
  • Ross is just mis-executing commands in some fundamental ways (the most likely of the bunch)