Difference between revisions of "HTC Droid DNA (htc-monarudo)"

From postmarketOS
Jump to: navigation, search
(Added infobox.)
Line 1: Line 1:
 
[[Category:Unsupported Devices]]
 
[[Category:Unsupported Devices]]
=== Contributors ===
+
[[Category:Devices]]
 +
{{Infobox device
 +
| manufacturer = HTC
 +
| name = Droid DNA / Butterfly
 +
| codename = monarudo
 +
| image = File:HTC Droid DNA.jpg
 +
| imagecaption = HTC Droid DNA
 +
| releaseyear = 2012
 +
| originalsoftware = Android 4.1 on Linux 3.0.31
 +
| cpu = Qualcomm APQ8064 Snapdragon S4 Pro
 +
| gpu = Adreno 320
 +
| storage = 16GB
 +
| display = 1080x1920
 +
| memory = 2GB
 +
}}
 +
== Contributors ==
  
 
* Ross Schulman
 
* Ross Schulman
  
=== Current Status ===
+
== Current Status ==
  
 
* Kernel builds
 
* Kernel builds
Line 10: Line 25:
 
* Trying to flash the kernel with <code>pmboostrap.py flasher flash_system</code> or <code>flash_kernel</code> results in a <code>remote:not allowed</code> error, although this may be related to a corrupted partition table on my particular device.
 
* Trying to flash the kernel with <code>pmboostrap.py flasher flash_system</code> or <code>flash_kernel</code> results in a <code>remote:not allowed</code> error, although this may be related to a corrupted partition table on my particular device.
  
=== What works ===
+
== What works ==
  
 
* Nothing yet
 
* Nothing yet
  
=== Links ===
+
== Links ==
  
 
* [https://github.com/postmarketOS/pmbootstrap/tree/device-htc-dlx Working branch]
 
* [https://github.com/postmarketOS/pmbootstrap/tree/device-htc-dlx Working branch]
Line 20: Line 35:
 
* [https://github.com/rschulman/pmbootstrap-htc-dlx-debug Working CM boot.img and non-working pmOS kernel binaries]
 
* [https://github.com/rschulman/pmbootstrap-htc-dlx-debug Working CM boot.img and non-working pmOS kernel binaries]
  
=== Partition layout ===
+
== Partition layout ==
  
{|
+
{| class="wikitable"
 
! device
 
! device
 
! size
 
! size
Line 64: Line 79:
 
|}
 
|}
  
=== What have I tried so far ===
+
== What have I tried so far ==
  
 
* Pulling flash offsets from two different dlx ROMS. Both match each other and what we're using.
 
* Pulling flash offsets from two different dlx ROMS. Both match each other and what we're using.
Line 70: Line 85:
 
* Reflashing CM-12 just to be sure that the phone isn't totally bricked, but CM installs just fine and boots properly.
 
* Reflashing CM-12 just to be sure that the phone isn't totally bricked, but CM installs just fine and boots properly.
  
=== Some theories ===
+
== 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)
 
* 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)

Revision as of 23:57, 4 September 2017

HTC Droid DNA / Butterfly
HTC Droid DNA
HTC Droid DNA
Manufacturer HTC
Name Droid DNA / Butterfly
Codename monarudo
Released 2012
Original software Android 4.1 on Linux 3.0.31
Hardware
CPU Qualcomm APQ8064 Snapdragon S4 Pro
GPU Adreno 320
Display 1080x1920
Storage 16GB
Memory 2GB
Features
USB Networking
Flashing
Touchscreen
Display
WiFi
Xwayland
FDE
Mainline
Battery
3D Acceleration
Accelerometer
Audio
Bluetooth
Camera
GPS
Mobile data
SMS
Calls
USB OTG


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_system 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)