I'm shocked nobody here is talking about the Mango Beta 2 leak.

Here are the download links if you want to flash it yourself. It's device agnostic so all can flash.

www.megaupload.com/?d=WGHWO7DM
www.megaupload.com/?d=PL7H6FKJ
www.megaupload.com/?d=9Q3LBQ4J
www.megaupload.com/?d=KY8J8SIY
www.megaupload.com/?d=WNKD3G9U

As long as your device is unlocked and you follow the instructions in the pdf in the last link, you shouldn't have too much trouble. It does take a LONG time though as there are 2 pre-Mango flashes that have to happen and the Mango flash itself takes about 15 to 20 minutes.

 

How to deploy now in mango?

It seems that currently only LG models due to the registry editor in the MFG app can be dev unlocked and get xaps deployed.

Nevermind.. My fault. My phone is dev unlocked. But when I installed mango it has relocked.

Just unlocked again and everything is fine. Thanks anyway (:

Man I was looking for the Zune 4.8...thanks a bunch you saved me. I did mine the non-official way and it's much easier and faster. But now the current zune 4.7 cannot sync to mango and need 4.8. Thanks again!

I successfully update to mango beta thru mangoforall but now I cannot deploy any xap files and all my homebrew apps not working. Anyone got this problem or solution will be helpful?

Thanks in advance.

This is a very well known issue and there is no solution. Mango breaks all homebrew and unless you're on an LG, you can't unlock your phone.

I am on LG still can't unlock my phone despite the MFGapps routine .

for me it works! mango beta and unlocked my lg optimus 7! best phone ever!

Well I am running Mango beta too but I could not deploy xap anymore

because you have to UNLOCK your LG with the MFG TOOL _AGAIN_!

Before anyone jumps on this, you guys need to know that You can't upgrade to the final Mango from this build, so you MUST back up your current build. If you loose your backup, your phone is permanently in preview-Mango mode--no going back, no going forward

I am not sure why anyone aside from a developer would want to deploy this beta build. There is too much risk involved and this is not a complete build, i.e still missing quite a few features that wont become available until closer to the official release date. I was speaking with a dev who went the route of the beta officially and he said he had to check off so many waivers and risk acknowledgments that there is no way I would do this unofficially. MSFT seems very serious about following directions carefully and this being dangerous.

Of course we will be able to update from the beta to the final. Its just not intended by Microsoft. All what the Mango-Update-Tool does is that it "provisions" (changes...) the update-regkey on the phone to get the new update. Once the final is out we can switch back to the official branch.

Then the thing with "danger" etc...etc.. there is no real danger involved. The beta in fact is stable and pretty featurecomplete. About the waiver and risk aknowledgements...there are just the standard "void warranty" ones and that you should read the manual before flashing (which should be a MUST).

Then deploying: Only the interop-services were disabled. So we lost the direct registry access. File Explorer and every other homebrew app still works
So we only miss registry-editing (which still can be done with the provxml-trick on HTC or the MFG on LG).

Deploying is still possible if you have unlocked your device in nodo-state...

to make your htc phone to be able to unlock just copy this to windows dir and run htc connection setup:

<wap-provisioningdoc>
<!-- *** COMMENTO *** -->
<characteristic type="Registry">
<characteristic type="HKLM\Software\Microsoft\TaskHost">
<parm name="DehydrateOnPause" value="0" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Comm\Security\LVMod">
<parm name="DeveloperUnlockState" value="1" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg">
<parm name="PortalUrlProd" value="" datatype="string" />
<parm name="PortalUrlInt" value="" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
<characteristic type="HKLM\ControlPanel\Themes\1">
<parm name="ChromeColor" value="#AA000000" datatype="string" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

including semi-transparent bars and dehydrate-hack (which still works )

This is a well known and there is no solution. Mango beats all home and unless you are in an LG, you can not unlock the phone.

Build 7720 is out, RTM....get it on XDA...

http://forum.xda-developers.com/showthr ... ?t=1215501

Follow the directions (assuming your unlocked) there is a method for HTC devicesto use the provxml-trick along the upgrades to keep unlocked, dont worry about the language packs if you dont need them follow the rest of the directions.

7720.68 is the final version from MS, there will be one coming out from your carrier, so you want to backup if you can (read, read, read)

Donate some wrz to me if you can...