New Sprint Mogul ROM leaks with Windows Mobile 6.1

News

Hold the presses! Windows Mobile 6.1 (you remember Windows Mobile 6.1, right? Good) has reared its redesigned head. Before you get too excited, it’s worth noting that this is a leaked beta version of an upcoming ROM update, but still…we’re starting to see some forward motion, so we’d rather not jinx it with ill will. The recipient of the update is none other than the Sprint HTC Mogul, which is interesting considering the fact that another, non-6.1, beta ROM for the Mogul leaked just last week, but we assume that Sprint and HTC are thinking this one through, right? It looks like the 6.1 update here is a bit crippled from the one we encountered, with the only notable enhancement being the inclusion of native threaded SMS support. Even so, it’s looking good and a sign of more 6.1 things to come.

UPDATE: It looks like we may have jumped the gun with this one. It’s come to our attention that this is not an official ROM leak, but rather a cooked homebrew ROM put together from an official Kaiser WM6 build.

Read

9 Comments
  • Victor A

    I thought this was a custom rom not a leaked rom. Says its made by No2Chem.

  • Vision77

    All of the chefs at xda-devs have been going bananas with leaked 6.1 roms these last few days. Overall the OS is a little bit faster, it has integrated threaded sms(lackluster in comparison to the hacked treo sms imo) Pocket IE has a zoom feature. I’m pretty sure there’s more to come. Oh and if you get one of these cooked roms make sure that the beta timebomb has been removed or you’ll get a msg saying: Thank you for test WM6.1 beta. This beta has concluded.

  • Vision77

    Oops thats thank you for testing WM6.1 beta…….

    Oh and 1st B!tch3z

  • heh

    first? more like third… heh

  • Scott

    How do you make sure the timebomb has been removed? If this is something you do yourself, where can I find instructions? Also, what bugs does this ROM update have?

  • http://mobile-enthusiast.blogspot.com dishe

    Oh, how I love it when bloggers jump to conclusions without having ALL the relevant information.

    The leaked 3.16 rom from Sprint still had Windows Mobile 6.0, not 6.1 as claimed here. How do I know? I’ve been running it since it was leaked, and have taken it apart and recompiled it with my own customizations many times.

    The problem is that very shortly after 3.16 was leaked, a 6.1 rom was also leaked for the Kaiser/Tilt, which has very similar hardware. With the efforts of seasoned rom cookers (particularly those who go by the names no2chem and DCD on the various message boards discussing this), 6.1 was eventually ported into the 3.16 beta base.

    In fact, from the screen shot shown above, you can clearly see that this is the no2chem release of 6.1, since the build number is “19716.1.0.0 No2″, the No2 being the signature of the user who built this “frankenrom” (official releases are only numeric).

    Many people never tried the original 3.16 beta because the 6.1 roms were up on the ‘net very shortly after.

    BGR, this post is exactly what is wrong with blogger news. Everyone is so excited to be the first to post new information that they sometimes don’t check all their facts and get it wrong. So many other blogs and message boards link to stories like this with innacurate information which causes rumors to fly and hopes to soar only to be shattered when they realize that, for example according to a Microsoft press release, there are NO OFFICIAL PLANS TO RELEASE 6.1 ON THE MOGUL.
    The only confirmed device that I know of to be getting this OS update is the Kaiser.

    Please get your facts straight, if at least for your own reputation!

  • Monorail

    Actually, Sprint’s website confirms the 6.1 release for the Mogul sometime early 2nd quarter. You should try getting your facts straight. It would help that when you’re preachin’ you’re not one of the people you’re preachin’ about.

  • http://eliteeternity.com Elite

    Link for your Sprint.com reference, Monorail?

  • http://eliteeternity.com Elite
blog comments powered by Disqus