HTC Droid DNA (htc-monarudo): Difference between revisions
Appearance
No edit summary |
merging Template:Change arch into Template:Infobox device |
||
(15 intermediate revisions by 12 users not shown) | |||
Line 1: | Line 1: | ||
=== Contributors | {{Infobox device | ||
| manufacturer = HTC | |||
| name = Droid DNA / Butterfly | |||
| codename = htc-monarudo | |||
| image = File:HTC Droid DNA.jpg | |||
| imagecaption = HTC Droid DNA | |||
| releaseyear = 2012 | |||
| originalsoftware = Android | |||
| originalversion = 4.1 (Linux 3.0.31) | |||
| chipset = Qualcomm Snapdragon S4 Pro (APQ8064) | |||
| cpu = Quad-core 1.5 GHz Krait | |||
| gpu = Adreno 320 | |||
| storage = 16 GB | |||
| display = 1080x1920 | |||
| memory = 2 GB | |||
| architecture = armhf | |||
| status_usbnet = | |||
| status_flashing = | |||
| status_touch = | |||
| changearch=armv7 | |||
| status_screen = | |||
| status_wifi = | |||
| status_xwayland = | |||
| status_fde = | |||
| status_mainline = | |||
| status_battery = | |||
| status_3d = | |||
| status_accel = | |||
| status_audio = | |||
| status_bluetooth = | |||
| status_camera = | |||
| status_gps = | |||
| status_mobiledata = | |||
| status_sms = | |||
| status_calls = | |||
| status = | |||
| booting = no | |||
}}{{Based on SoC|Qualcomm_Snapdragon_600_(APQ8064)|Snapdragon 600}} | |||
== Contributors == | |||
* Ross Schulman | * Ross Schulman | ||
== Current Status == | |||
* Kernel builds | * Kernel builds | ||
* Trying to boot the kernel with <code>fastboot boot ...</code> freezes the phone, as does using <code>pmbootstrap.py flasher boot</code> | * Trying to boot the kernel with <code>fastboot boot ...</code> freezes the phone, as does using <code>pmbootstrap.py flasher boot</code> | ||
* Trying to flash the kernel with <code>pmboostrap.py flasher | * Trying to flash the kernel with <code>pmboostrap.py flasher flash_rootfs</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 == | |||
* Nothing yet | * Nothing yet | ||
== 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 58: | ||
* [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 == | |||
{| | {| class="wikitable" | ||
! device | ! device | ||
! size | ! size | ||
Line 64: | Line 102: | ||
|} | |} | ||
== 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 108: | ||
* 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 == | |||
* 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) |
Latest revision as of 13:00, 26 August 2024
WARNING: This device is not recommended for future use with postmarketOS due to its armhf architecture. Alpine Linux (the distribution that postmarketOS extends) pmaports#599 has been considering dropping it. |
This device is still running on armhf, although the processor supports armv7. If you own it, change it and test it that way. |
This device is marked as not booting.
![]() HTC Droid DNA | |
Manufacturer | HTC |
---|---|
Name |
Droid DNA / Butterfly |
Codename | htc-monarudo |
Released | 2012 |
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 |
Software | |
Original software | Android |
Original version | 4.1 (Linux 3.0.31) |
postmarketOS | |
Category | testing |
Pre-built images | no |
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 usingpmbootstrap.py flasher boot
- Trying to flash the kernel with
pmboostrap.py flasher flash_rootfs
orflash_kernel
results in aremote: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 push
ing the .img file and attempting to usedd
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)