WP8 ported to the HD2


Recommended Posts

So Microsoft's claim about current WP7.x devices 'not having the required hardware' is essentially nonsense. According to them WP8 requires a TPM chip or some kind of encryption at the hardware level but that's not the issue. They just fabricated lame excuses because they're just too lazy. Even if WP8 truly required 'things' not present in current devices they could still have figured out a workaround and provide users with something better. Their greed is pretty much comparable to Apple's, always seeking to push users into buying newer devices in order to have a newer OS

Just to clarify for everyone...the hardware claims are not nonsense. This is a PoC from the dev who (from what I've read) is using an emulated UEFI implementation that then kicks in a bootloader that allows it to load.

From what I've read it emulates the hardware functionality at initial boot, then kicks off a chain to load the OS once it has faked the necessary hardware requirement.

This sort of solution would NOT work properly for phones sold at retail. Just because something is possible doesn't meant that it can be done for the devices at market.

There's a difference between something being possible in the sense that it can be done, and it being possible in the sense that it can be done properly.

When I was in Hong Kong a few years back I wanted to buy an HTC Tattoo, and I was almost sold an HTC HD2 because the shop keeper misheard me and wanted a bit of extra money for it. I should have paid the little bit extra if only I knew what a beast it would be past WM6 :pinch:

My dad has the HD2 and the screen is not respawning that well anymore. It was a really good phone at the time but it's out dated with the spec. WP OS is a very well OS which is why it was the best thing for Microsoft to start over from 6.5

Just because someone was able to get it running once on an HD2 doesn't mean it's actually usable - it's not a question of whether or not Microsoft "lied" but more an example of getting code to run efficiently on a given platform device.

Hell, you can run Windows Phone 8 in the emulator on a PC - so technically it DOES run in that emulator, but the experience is so slow, laggy, and generally useless that it's nothing like actually running it on an actual Windows Phone 8 certified device.

See the difference there?

I've owned several HD2 smartphones in the past few years, when I find one on the cheap I usually grab it because I know how awesome it is, but putting Windows Phone 8 on one is an exercise in futility for someone like me 'cause I can't stand Windows Phone at all.

Just because it can be done doesn't necessarily mean it should because of the lack of performance it'll have if and when they actually get a solid working ROM they can distribute.

Also, the HD2 has two versions: the International one with only 512MB of RAM and the T-Mobile US version that has 1GB of RAM - both have 1GB of internal ROM space but, for more current OSes, the amount of actual RAM in them matters. I doubt Windows Phone 8 would run worth a damn on the International version, and only slightly better on the T-Mobile edition.

As Cotulla has pointed out in posts since this info was posted, it was basically an experiment to see if it was possible at all, he really never had intentions of making it a serious project to pursue.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!