The HTC Desire HD has quite the history. With a 4.3-inch screen on the outside and a single core 1GHz CPU on the inside, it became available all the way back in 2010, rocking some truly ancient software that’ll challenge even the most studious of historians—namely Android 2.2 Froyo and HTC Sense 2.0. It was upgradeable to Android 2.3 Gingerbread and Sense 3.0, and was graciously promised by HTC an upgrade to Android 4.0 Ice Cream Sandwhich. Unfortunately, HTC didn’t keep their promise and backpedaled, essentially crushing any hope for Desire HD owners to experience the benefits of later, official releases.
But as we’ve witnessed time and time again, where there’s a will, there’s a way. And in this case, the HTC Desire HD finally sees Sense 5.0 (and Android 4.1.2) running on its screen. The Sense 5.0 port comes thanks to the efforts of XDA Senior Member S.a.M.e.R_d, who managed to port the HTC modified skin and the associated features and improvements such as Blinkfeed, from the HTC Desire 500.
Quite a few functions are working as they should, including the backlight, root access, mobile data and text messaging, but the port is still a work in progress, and this can be seen from the broken camera, audio, WiFi, and SD Card.
If you’re a loyal HTC Desire HD user, or someone who’s simply interested in the development progress of a relatively ancient device, head over to the development thread for more details and discussion.
Update: The port has been discontinued. Nothing to see here folks.
October 24, 2013 By: Will Verduzco
Hardware capacitive buttons seem to be a love-it-or-hate-it affair. While many of us seem to prefer the versatility of the on-screen buttons most commonly seen on modern Nexus devices, others instead favor the increased usable screen real estate made possible by having dedicated keys outside of the display.
If you happen to own an HTC device, you are probably a fan of dedicated hardware buttons. But that’s not to say that you can’t tweak them to make them work better for you. XDA Senior Member denversc created an app called Capacitive Buttons Brightness, which does… Well, you guessed it. It allows you to change the brightness of your capacitive buttons.
Currently, the app officially supports the HTC One X (dual- and quad-core variants), HTC One X+, HTC One, and HTC One S. That said, many users have found that it also works on other devices such as the HTC One V, HTC Desire HD, HTC Evo 3D, Motorola Droid MAXX, and LG Optimus G.
The app allows you to change brightness in 3 steps: dim, bright, and off. The default on most Sense-based ROMs seems to be bright, whereas it is usually set to dim on most AOSP-based ROMs. Please note that the “off” setting does not work if you have the GV Integration app installed. Naturally, root access is required… But who here isn’t rooted anyway?
December 2, 2012 By: Haroon Q. Raja
In the world of smartphones, some devices never cease to amaze us. And while it may not exactly be the HD2, the HTC Desire HD is certainly shows its lineage. HTC may have long declared end of upgrade support for this once flagship, the developer community hasn’t forgotten it at all, and it has been dual booted, made to natively run Ubuntu, given the latest HTC Sense ports, and received working ICS and Jelly Bean 4.1 custom ROMs. The latest in this series of developments for the device is the AOSP-based codefireX Android 4.2.1 Jelly Bean ROM brought to us by XDA Senior Member synergye.
The ROM is completely open-source, and is built with an optimized Linaro toolchain for those who believe this helps performance. All features other than Bluetooth are working, and there are a lot of customization options to tweak it just the way you want. An additional kernel is also available from the same developer that brings several performance enhancements to the device on any Jelly Bean ROM.
With all the new devices being released, or about to be released, some might ask where the love is for older devices. OEMs haven’t been the greatest when it comes to delivering updates. Even if the device is capable of running it. However, that’s when the developers at XDA step in and deliver updates. The HTC Desire HD is one of those devices that just keeps on rolling. Not long ago, Sense 4.0 was more or less made stable. Now, Sense 4.1 has arrived.
XDA Recognized Contributor torxx has released the first Sense 4.1 ROM for the Desire HD. It just goes to show that OEMs really don’t always know what they’re talking about when it comes to what their devices can handle. It’s running full Sense 4.1 on top of Android 4.0.4 and contains a number of features. Some include:
Fully fixed camera
Sense 4.5 skins
Rooted with SuperSU
Extended Quick Settings
Advanced Power Menu
Team Blackout kernel
Excellent battery life
GPU UI Rendering
Better CPU Performance
init.d scripts support
Improved EXT4 System
Removed 3-dot menu
1% stock battery
Many other tweaks! (see tweak package)
While it is stable enough to be run as a daily driver, some users have reported assorted small issues—nothing serious, though. For the most part, it’s some HTC widgets not working, the tweak package causing some force closes, and other miscellaneous issues.
If you’d like to give the latest HTC Sense a shot on the Desire HD, check out the original thread.
We’ve recently posted a number of articles about a hybrid ROM known as PACman ROM. Originating on the Xperia Ray, it was later ported to the Samsung Galaxy Ace and the Sony Ericsson Xperia Pro. PACrom is now making it’s way across a number of other devices on XDA.
PACman merges some of the best features from Paranoid Android, AOKP, and CyanogenMod into one uber-featured ROM. The latest devices to receive a PACman port are the HTC Desire S and the old favorite, the HTC Desire HD, both thanks to XDA Senior member blindndumb.
The Desire S ROM should be considered a test ROM, with a number of known bugs at present, including problems with the front camera, speakerphone, and WiFi Hotspot.
The Desire HD ROM on the other hand is a little more functionally complete, with no known bugs.
If you own either of these devices and want a taste of a bit of everything all at once, this ROM might be the one for you.
The last time we brought you news about TWRP, it was to announce that TWRP 2.2.2 had been released. It had fixed a lot of bugs from the initial release of TWRP 2.2 and added a few new features. Very recently, TWRP has been updated again to version 2.3.
There were a whole bunch of awesome improvements with TWRP 2.2 and a lot of unique and brand new features as well. TWRP 2.3 promises no less. The official change log includes:
Rebased onto AOSP Jelly Bean source code
Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
ADB sideload functionality from AOSP is included in 2.3, see this link for more info
Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
Faster boot times
Added charging indicator while in recovery (only updates once every 60 seconds)
Additionally, XDA Recognized Developer Dees_Troy has reported that there is now support for spaces in backup names. Before, if you added a space to the name of a backup, it would not restore. Now users can use whatever naming convention they want.
One of the biggest changes, though, is all of the TWRP being rewritten in C++ and its move to recovery API 3 instead of API 2. With the code rewrite, it will allow TWRP to update more quickly and with more stability. With the API 3 change, it means that some flashable zip files may stop working because the developer needs to update the update-binary. If you don’t want to wait for the developer, or the developer has ceased working on the project, you can find one to use on TWRP’s official website. To install the latest TWRP, you can use the Goomanager application. Simply open the application, hit menu, and install open recovery.
If you want to check out the latest TWRP recovery for your device, check one of the links below.
Previously in HTC Desire HD development, there had been only one Sense 4 ROM that had camera and camcorder working. It was Virtuous ROM from XDA Recognized Developer chrisch1974. However, to use the same kernel on other Sense 4 ROMs meant losing other features such as WiFi. So, the driving attempt has been to get a kernel for the other Sense 4 ROMs so that they could have working camera and camcorder as well. Now that work has finally paid off.
XDA Senior Member ted77usa recently released a ROM that gives camera and camcorder support to Desire HD Sense 4 ROMs without losing WiFi. The breakthrough came after XDA Forum Member tgeorg was able to figure out the problem with the kernel. As tgeorg puts it:
The problem with the virtuous kernel is, the module for wifi is renamed from bcm4329.ko to bcmdhd.ko and also the firmware files are changed.
So I take one of the virtuous kernel updates for my camera chip and changed the name of the module from bcmdhd.ko to bcm4329.ko but this is not enough. If I insmod the name is still bcmdhd , this must be changed in the module at offset 582E4 from bcmdhd to bcm4329. then lsmod shows “bcm4329 440166 0 – Live 0xbf000000″ and also the firmware files from the virtuous rom must be taken to fully functioning. they are 7 files:
After that, tgeorg gave the proper list of files that needed to be compiled into a flashable zip for users that made everything work. From there, ted77usa released the kernels. Now, all ROMs using Sense 4 have camera and camcorder working without borking anything. With one of the biggest porting issues out of the way, the devs can now focus on fixing the rest of the problems. And HTC said it couldn’t be done. Oh HTC, you’re so silly.
For more info, check out the original thread.
August 16, 2012 By: David Watt
A few weeks ago, we reported on HTC’s disappointing decision not to provide an official Ice Cream Sandwich update for the Desire HD. Not even a petition with over 15,000 signatures was enough to persuade them to change their mind. It did however, force them to release an official statement:
We’ve heard your feedback on our decision not to update the HTC Desire HD to Android 4.0. We completely understand that this is a controversial decision.
For more background, due to how storage on the HTC Desire HD is partitioned – and the larger size of Android 4.0 – it would require re-partitioning device storage and overwriting user data in order to install this update. While technically advanced users might find this solution acceptable, the majority of customers would not. We also considered ways to reduce the overall size of the software package, but this would impact features and functionality that customers are currently using. Even after installing the update, there were other technical limitations which we felt negatively impacted the user experience.
We believe an update should always improve the user experience and carefully evaluate each update based on this criteria. While we are very aware of the disappointment from this decision, we believe the impact to user experience was too great. We recognize this is a change from our previous statement and for that we’re truly sorry.
As we know, the developers here on XDA are never ones to let things lie. XDA Senior member QD2DC and the Team blackout development team have now given HTC a large two fingered salute by releasing the first fully functional Android 4.0.4 Ice Cream Sandwich ROM with Sense 3.6. Ported over from an HTC Incredible S build, the ROM is 100% complete and has no known issues. The ROM also comes with Team blackout’s own custom kernel for additional performance.
If you’d like to give the ROM a try, head on over to the original thread.
July 23, 2012 By: Former Writer
For shame, HTC! Once promised an update to Ice Cream Sandwich, the HTC Desire HD received an update from HTC alright—just not the one everyone was expecting. On their blog, HTC has announced that they believe Desire HD users are better off without ICS. They state:
After extensive testing, we’ve determined that the current version of HTC Sense with Android provides customers with the best experience on the HTC Desire HD. When we consider new versions of software, we weigh a number of factors, but ultimately the customer experience on the product is the deciding factor. We apologize for any confusion this change may have caused our customers.
After a collective sigh, the DHD community has taken to action to get the update released despite HTC’s “extensive testing.” XDA Senior Member max63094 has started a petition. The goal is actually not to get an official ICS with Sense update, but rather something similar to what was done with the HTC Desire. Reportedly, the HTC Desire couldn’t handle Gingerbread with Sense on top of it, so HTC released a pure Gingerbread RUU, complete with source code release for the Desire. Desire HD users are looking for, at minimum, the same deal, as ROMs developed by the community have shown that the Desire HD can actually handle ICS quite well. As such, the petition is worded:
Now anyone over at XDA knows this is not true, ICS runs great on our phone plus it is also a better experience. Now this petition is to get HTC to release ICS for us, if they do not want to give us Sense, then they could do at least what they did for the HTC Desire, and release a pure Android on the HTCDev.com With the HTC Desire, they released a RUU because the phone could not handle sense with gingerbread, so they released a pure Android, and now they need to AT
LEAST do that for the Desire HD with ICS.
Nothing unreasonable, right? At the start of the petition, the goal was around 2000 signatures. The petition, at the time of this writing, has 4000+ signatures, so Desire HD users are really coming out and letting HTC know what they think. Of course, you don’t need to own a Desire HD to sign it. The satisfaction of knowing you’re helping correct an injustice is enough. One would think HTC would have learned by now. Maybe they just love receiving angry feedback from customers.
[Thanks to XDA Senior Member Ditti4 for the original tip and the 25 other XDA and Twitter users for the encouragement!]
Among the newest devices to receive Jelly Bean include the T-Mobile MyTouch 4G Slide, Motorola Defy, and the HTC Desire HD. These devices are all a little older than some would expect to be receiving ports. But if the HTC HD2 can get it, newer devices should be able to as well.
The MyTouch 4G Slide Jelly Bean ROM was developed by XDA Senior Member xmc wildchild22 and is built from source. XDA Senior Member Quarx is responsible for the Motorola Defy ROM, and XDA Recognized Developer randomblame (also responsible for the Iconia A500 JB ROM) brought Jelly Bean to the Desire HD.
For all three ROMs, there’s a comprehensive list of things working and not working. For the MyTouch 4G Slide, here’s what isn’t working:
onscreen keyboard (I have to wait for the patches form CM for our hard keyboard phones)
For the Desire HD, which has a much shorter list:
mic – works in calls but crashes apps
audio routing – in phone calls audio comes out the rear speaker and when headset is plugged in audio comes out of both headset and speakers
There isn’t a running list of what’s not working on the Motorola Defy, but there is a list of things that are working:
Audio (thanks to maniac103)
For the MyTouch 4G Slide a
nd the Motorola Defy, the list of things not working is still pretty long—so they cannot yet be considered daily drivers. They are stable enough to try out, however, to see what Jelly Bean is all about. The Desire HD ROM, on the other hand, seems to be a bit more suitable for every day usage.
For additional information, download links, and more, click the corresponding link below:
Update: Between the time of writing and publishing, the Defy port has made incredible progress, now even featuring hardware acceleration. It is now suitable to many as a daily driver.
July 19, 2012 By: Former Writer
Not too long ago, we brought you news that allowed HTC EVO 4G LTE users to customize their bootloaders. The process was pretty cool, allowing users to make their bootloader look however they want—including making it look unhacked. After the initial project was released, users clamored for this to be made available to more devices. The requests were heard and responded to. Now, the plugin has been made available to make the bootloader customizer for a number of HTC devices.
The process for a developer to port this is not hard. XDA Recognized Contributor regaw_leinad, who developed the application and plugin, takes a time out from the stags (yes, that’s really him) to explain how:
it’s basically all written, they just need to fill in the values for their hboot, and embed the hboot.img into the exe. I already have a placeholder for the hboot.img and android-info.txt so a drag and drop over them should keep it embedded.
Regaw_leinad is also creating the application for the supported devices, but wanted to release the plugin first so users had a chance to get it sooner. The current list of supported HTC devices include:
While the list is quite large, one must keep in mind that not all of these devices have S-Off, and users must have S-Off in order to actually use this application. To get started, visit the original thread.
July 17, 2012 By: Former Writer
We’ve covered various new ways that frequent flashers can back up their applications without using applications like Titanium Backup or MyBackup Pro. However, while the alternative methods may work better in some regards, they just can’t replace the classics in all situations. There is a new method on the HTC Desire HD that looks very promising, though.
The method is known as the Flashaholics Essential Pack. Put together by XDA Senior Member strawmetal, the Pack uses AROMA Installer to allow users to install a plethora of popular applications when flashed in a custom recovery. This, much like the App2Zip program linked above, is flashed right after a ROM flash, so apps are installed before the ROM even boots for the first time.
For now, the Flashaholics Essential Pack is a little light on the goods. It includes a very decent number of applications—including GAPPS—but aside from GAPPS and essential utilities, there isn’t much else. Thus, you’ll still need to use other applications to restore your other apps. That may not be the case forever, as strawmetal has stated that there will be a tutorial written to help users customize their own Pack to install after ROM flashes. However, it is important to note that even if this is done, app data will not be backed up or restored.
For more details, check out the original thread.
[Thanks to XDA Senior Member androidindian for the tip.]
Just about three months ago, we brought you news that the Team Win Recovery Project had received a massive update to version 2.1. April’s release largely heralded the start of a new age in recoveries—where one would no longer have to deal with cumbersome menus, instead interacting with a very user-friendly GUI.
It wasn’t simply about the GUI either. In addition to bringing an unrivaled level of UI polish, TWRP 2.1 offered users many advanced features such as update.zip queuing, a basic file manager, and dual storage support for Nandroid backups. Additionally, TWRP added support for the open source scripting engine OpenRecoveryScript, which works in conjunction with the previously covered GooManager.
How do you follow up something as revolutionary as TWRP 2.1? With TWRP 2.2, of course. That’s how! The new release builds on the previous offering by delivering many recovery “firsts.” For starters, this is the first recovery to feature on on-screen keyboard. Why would you want such a thing? How about naming and renaming Nandroid backups! TWRP 2.2 is also the only recovery to split extremely large backups, allowing users to backup and restore /data partitions larger than the 2 GB FAT32 file size limit.
In the words of XDA Recognized Developer Dees_Troy:
- On-screen keyboard in recovery! — supports long press, backspace repeat, and swipe left deletes everything left of the cursor
– Name new backups and rename existing backups
– Rename files and folders in the file manager
– Pseudo-terminal emulator
– Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
– Backup archive splitting — allows backup and restore of data partitions larger than 2GB
– Simplified XML layout support between resolutions
– Added dual storage selection radio buttons to zip install, backup, and restore pages
– Improved zip install compatibility
– Updated update-binary source code
– Numerous small bug fixes and improvements
Eager to get started? I know I am. Head to the links below to obtain the appropriate version for your device: