HTC Droid DNA (htc-monarudo): Difference between revisions
Appearance
m CmdrWgls moved page Htc-monarudo-(HTC-Droid-DNA) to HTC Droid DNA (htc-monarudo) |
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 == | |||
* 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 == | |||
* 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 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 == | |||
{| | {| class="wikitable" | ||
! device | ! device | ||
! size | ! size | ||
Line 64: | Line 79: | ||
|} | |} | ||
== 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 == | |||
* 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 03:57, 5 September 2017
![]() HTC Droid DNA | |
Manufacturer | HTC |
---|---|
Name |
Droid DNA / Butterfly |
Codename | monarudo |
Released | 2012 |
Hardware | |
CPU | Qualcomm APQ8064 Snapdragon S4 Pro |
GPU | Adreno 320 |
Display | 1080x1920 |
Storage | 16GB |
Memory | 2GB |
Software | |
Original software | Android 4.1 on Linux 3.0.31 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | no |
Flashing |
No data |
---|---|
USB Networking |
No data |
Internal storage |
No data |
SD card |
No data |
Battery |
No data |
Screen |
No data |
Touchscreen |
No data |
Multimedia | |
3D Acceleration |
No data |
Audio |
No data |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
No data |
Bluetooth |
No data |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
FDE |
No data |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
No data |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
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_system
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)