Develop Bugs

how to get the update fastest~~ATT focus

首先声明 本文是转载 作者是台湾的jojo0821大哥！！！
步驟如下：
1. 下載 SAMSUNGregistry 軟件並部屬它(手機須先解鎖)~~~ View attachment SamsungRegistry.xap
2. 從手機中啟動該軟體 上面區塊打 "HKLM\System\Platform\DeviceTargetingInfo\MobileOperator"，引號部分不要
3. 打完之後按一下 READ，應該會是 "GetString : ATT-US"
4. 把第二欄的所有信息清除，按下 WRITE
5. 再按一次 READ，應該會出現 "GetString :" 表示清除成功
6. 手機連上電腦，打開 Zune 檢查更新
7. 可以升到 7008 了
現在我們的 AT&T 版變成 Rogers 版本了，而 Rogers 版本的 NoDo 是已經準備派送了

Translated
This article is a reprint of the first statement is Taiwan's jojo0821 brother! ! !
As follows:
1. Download SAMSUNGregistry software and subordinates it (the phone must first unlock) SamsungRegistry.xap
2. from the phone to start the software above the block to play "HKLM \ System \ Platform \ DeviceTargetingInfo \ MobileOp erator", quotes some do not
3. Once on shore, then click READ, should be "GetString: ATT-US"
4. the second column removed all of the information, press the WRITE
5. Press READ, should appear "GetString:" Clear said the success
6. handset connected to the computer, open the Zune check for updates
7. can rise to 7008 by
Now we are into Rogers AT & T edition version, while the Rogers version of the NoDo is ready to dispatch the

Nice! My Dev phone (which is not an unbranded, carrier unlocked phone) is updating to pre-NoDo right now. It is very sad that I have to hack my phone just to get legit updates from Microsoft, and that I"m held captive by carriers.
Also, just to clarify the translation:
1. Download SamsungRegistry.xap software and install it (the phone must be a Developer Unlocked phone, or with the ChevronWP7 Unlock tool)
2. Launch SamsungRegistry and type in "HKLM\System\Platform\DeviceTargetingInfo\MobileOperator" without the quotation marks.
3. Click READ, and the returned value should be "GetString: ATT-US"
4. Tap in the Value field and delete the contents, then press Write
5. Press READ again, should appear "GetString:". No value = success
6. Connect your device to the Zune software and it should detect the Feburary 2011 Update needs to be applied, which will only be version 7008.
MS should be rolling out NoDo to US unbranded phones soon, I hope!

This is already posted in the unbranding thread. Thanks nonetheless.
http://forum.xda-developers.com/showthread.php?t=1004487
Please note that this update can be tricky. My Samsung locked up on me 5 times last night before the update would take. Personally, I wouldn't recommend doing this unless you are really really ansy about the new update. Plus, the PreNoDo is not that amazing. It is snappier and faster, but it doesn't seem like I should have gone through the hell I did. I'm not saying it always happens, or even happens 1% of the time (I could be an anomolous user), but after a plethora of errors I would just be patient...

Ah, thanks for the link. I haven't had any issues since removing the carrier branding, and installing the pre-NoDo update.

NODO jailbreaking，100% sure。

I'M A CHINESE.I hope my experience can help all WP7 fans. If this thread help you,It's my pleasure.
detail steps：
1. MAKE sure your phone has a 7004 or 7008 rom，than used chevronWP7.cer and chevronWP7.EXE to unlock your WP7. (this is step you can find in this forum)
2. After UNLOCK! prevent relocked. (belows is the easy way to edit your registry)
for HTC download xap in http://dl.dbank.com/c0u5q3xic8 and sideload it to your phone and run it ,press the green button.
for Samsung devices,see post #17 in this thread.
3. Update to NoDo via zune and your device still in unlocked state! (for some people cannot get nodo from zune, see below method,100% successful rate.)
methods to get zune nodo. http://forum.xda-developers.com/showthread.php?t=1012189 !!!!
Download USAIP.pbk open it and connect to EUROIP PPTP Hungary with
USERNAME: demo
PASSWORD: demo
Connect your phone to the PC
Disable WIFI in your phone but be sure not to open FLIGHT MODE
OPEN "Use cellular data connection to check for updates" in SETTINGS-UPDATE, AND KEEP YOUR PHONE IN THIS SCREEN
Start Zune and keep it running all the time
Manually search for an update within Zune (setting-phone-update)
After a few seconds (about 20-25 seconds for me) disable "Use cellular data connection to check for updates on your phone" --> WAIT FOR 20-30S,The update shows up! and enjoy it!
I MANAGED TO GET UPDATE BY USING THIS METHOD!!!
HAVE fune!

the update should go via zune. it should be official update。

If it works that's good news.. But is it that easy? I would thing that the update edits the registry...
If you update to 7008 the unlock still works that I know.. Are you sure that's not what happaned.. And you just got the Pre-NoDo update...?

BellPego said:
If it works that's good news.. But is it that easy? I would thing that the update edits the registry...
If you update to 7008 the unlock still works that I know.. Are you sure that's not what happaned.. And you just got the Pre-NoDo update...?
Click to expand...
Click to collapse
the vision is 7390.after 7008，unlock，then prevent unlock， then connect to zune， if you can find update， then you success。many chinese succeed，the only problem is MS，it promise everyone can update，but only very few people receive the notice of update through zune。

March thanks for XDA-DEVELOPERS(xboxmod)!

But I am still waiting the Nodo Version in Hong Kong, if it is true, it is a great job for the user!!!

I am a user of HD2 with wp7 two days ago.but now I have to switch to Android again as the wp7 is not fully developed,I think.anyway...thanks for sharing the good news...謝謝!

It seems to work based on user replies. However, it requires HTC-ProvXml-Deploy to work. What about us non-htc users?

as it was already said, we need to know if it works on non HTC devices?

Can anyone post the xap here?

Registered and downloaded the xap. It's attached as a zip, just change the file extension from .zip to .xap.
Wondering if this will truly be our way to update to NoDo and still keep our devices unlocked...

eternalemb said:
Registered and downloaded the xap. It's attached as a zip, just change the file extension from .zip to .xap.
Wondering if this will truly be our way to update to NoDo and still keep our devices unlocked...
Click to expand...
Click to collapse
thanks! I still cannot update to NoDo from Zune. Though my phone is unbranded

Is it the same with this?
[HTC] Prevent WP7 from Relocking
http://forum.xda-developers.com/showthread.php?t=913748

thats great, im sure this will be very helpfull to get a real JB goin...
too bad ive already updated :/
lemme quote the first post of the site translated (powered by microsoft translator):
http://www.qdppc.com/thread-48290-1-1.html said:
"Frog brothers produced"
---Prevent once and for all small patches of the lock (Prevent Relock:1B)
Simple, perfect, effectively address the WP7 lock problem again!
From then on no longer careful, make you lechery tour ZUNE!
Note: HTC models suitable for
Frog (Wagool) by XDA-DEVELOPERS (xboxmod) information produced by XAP patch (formerly:http://www.qdppc.com/thread-48230-1-1.html), an effective solution to mobile phone unlocking (prison break) is locked again after question!
"Steps"
1, verify that the phone has "escaped";
2, Prevent Relock.xap deployment installation attachment to mobile phone,immediately disconnect the ZUNE connection;
3, mobile Executive HTC-ProvXml-Deploy program, pressGreen(OK) button;
4, after you restart the phone, remove HTC-ProvXml-Deploy, well, everything OK!
"Description"
If the reset system (hard restart, restore factory, brushing machines), you need to "escape" and install this patch!
Reprint please specify the source
March thanks for XDA-DEVELOPERS(xboxmod)!
----------------
1, immediately disconnect the purpose is to prevent before continuing to the next step, have also been locked (in fact, in "flight mode" or under)
2,Deploy delete it or not as you, in fact, at this point the useless
PS: I'm not "boring", is a frog, HA HA ~ ~
Wagool
Click to expand...
Click to collapse

I received this morning notice of NoDO update... but I can wait a few days before to do...

harmoniic said:
Is it the same with this?
[HTC] Prevent WP7 from Relocking
http://forum.xda-developers.com/showthread.php?t=913748
Click to expand...
Click to collapse
+1
Any one plz answer this.

info5i2002 said:
It seems to work based on user replies. However, it requires HTC-ProvXml-Deploy to work. What about us non-htc users?
Click to expand...
Click to collapse
The whole prevent-relock thing essentially does this:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
On Samsung devices you can use the TouchXplorer Registry Editor to do this. Though it has limited access on Samsung devices. It will show an "Access Denied" when you open the DeviceReg registry-key. But it will still allow you to create new values there and overwrite the old values. So, open the DeviceReg-key and create the "portalUrlProd" and "PortalUrlInt" values as empty strings. That will prevent your Samsung from relocking. And as it seems, that tweak will even survive the NoDo-update.

is that only for htc device?

Heathcliff74 said:
The whole prevent-relock thing essentially does this:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
On Samsung devices you can use the TouchXplorer Registry Editor to do this. Though it has limited access on Samsung devices. It will show an "Access Denied" when you open the DeviceReg registry-key. But it will still allow you to create new values there and overwrite the old values. So, open the DeviceReg-key and create the "portalUrlProd" and "PortalUrlInt" values as empty strings. That will prevent your Samsung from relocking. And as it seems, that tweak will even survive the NoDo-update.
Click to expand...
Click to collapse
The xap samsung tools does the job automatically which is easier to use

Marvin_S said:
The xap samsung tools does the job automatically which is easier to use
Click to expand...
Click to collapse
So someone has tried to change these keys and update to nodo to see!!!!

[HOWTO] Update from NoDO to Mango since official Zune 4.8 Update

Hey Guys,
I have been a long time viewer of XDA and found it incredible useful for both Android and WP7 communities.
I have just updated my Samsung Omnia 7 to the 7720 (RTM) build of Mango after the official Zune 4.8 came out. This meant that it took lots of trial and error and basically mashing instructions from a few different tutorials to get the build running.
As I can't find much reference for people who are trying to do this post-4.8 i thought it would be helpful to post what worked for me. I will try my best to link to the original threads for the steps and downloads I used and I take zero credit for the hard work done by those who wrote these tools and scripts.
(MODS: As this is my first post I couldn't put this in the Dev/Hacking forum, if up to scratch and necessary could you move it there?)
So here we go:
You will need:
WP7 Handset running NoDo
MicroUSB Cable
Windows 7 or Vista PC
Patience
A couple of hours to spare
Please note that as per every other tutorial of this kind, you are doing this to your own phone... don't blame me if things go bad!
This method of updating will remove your Chevron Unlock - if your a homebrew fan then i would look for other tut's or wait for official update!
1: Download this "Mango for All 0.3" from here
2: Extract the folders in the zip file to C:/takeonetomango .
3: Download "7720.rar" from here (originally found in this thread)
4: Extract the contents of 7720.rar to C:/ (VERY IMPORTANT! - you should end up with C:/RCtoRTM, C:/Zune etc).
5: If you currently have Zune and the Windows Phone Support tool - UNINSTALL THEM.
6: Open C:/Zune and run "Startzunelocal.exe" to install the (now old) Zune 4.8 Beta.
7: Open C:/Zune/Update and install "UpdateWP.exe" from either the x86 or x64 folder depending on which windows you use. (This is something of an idiot test. If you don't know which you should choose - stop here. Put the down your phone, uninstall Zune and put the official zune back - you should wait for the official mango update as this can seriously damage your phone.)
Explanation: So far, all the tools used to provision the phone and force the updates rely on the version of Zune and the WP Support Tool to match. Since the Zune 4.8 was officially released, there isn't a matching Support tool, which will cause all these bat files to fail their checks. This is why we will be rolling back to the old 4.8 beta a couple of times, just to please those checks.
8: Now you should have Zune Beta and the supplied UpdateWP installed. Now navigate to C:/takesonetomango. Plug in your phone and quit zune (you may need to wait a few minutes for the windows device driver to install). DO NOT UPDATE ZUNE AT THIS POINT. QUIT ZUNE.
9: With your phone plugged in and zune no longer running, right click "Update.bat" and run as Administrator
10: Follow the steps that appear in the command prompt. This will now do a backup of your phone and move it to a safe place (this is because you will need to go back to NoDo to get the official Mango update).
11: Go and put the kettle on. This is now going to take a while depending on how much stuff you have on your phone.
12:When the backup is done, it will move this backup to a safe place. Press any key to start that and finish drinking your coffee.
13: Once the backup is moved the command prompt will now do the interesting stuff. Its going to "Provision your phone" to trick Zune into thinking your a developer. Follow the instructions and be VERY PATIENT.
14: Once its all done, it will launch Zune. Stop any Sync'ing and go straight to check the phone for updates.
15: It should now say an Update is available and welcome to the Mango ISV beta. Hit Update now. You must update to the latest Zune first - this is fine - go for it.
16: When zune has updated, plug the phone back in and check for updates again. Now it will install the Mango 7712 (beta 2) update. Your phone will restart a couple times, be patient and wait until it has done TWO updates to your phone. Another coffee would be good.
CONGRATULATIONS! You now have Mango on your phone. However its not the latest RTM that you have been hearing about. So lets go install that -
17: With your phone unplugged, uninstall Zune again. And make sure you uninstall the "Windows Phone Support Tool" if it shows up in the program removal list.
18: Now go back to C:/Zune and install that old version again.
19: Now install "UpdateWP.exe" from the correct folder in C:/Zune/Update
20: Plug in your phone. Wait for the device driver to install again.
21: If Zune launches, quit Zune.
22: Go to C:/RCtoRTM and run "ISVto7720.bat" as an Administrator
23: This will take quite a while. All those other files in there are actually the RTM update itself. This one doesn't come over Zune, we only went back to the old zune to satisfy the checks in ISVto7720.bat.
24: After you have drank a few more cups of coffee your phone will have rebooted and installed the RTM release.
At this point you will need to unplug your phone and start playing with it. My apps and files and all settings etc stayed in place so yours should too.
Whilst playing with the new features on there you will want to launch zune and get it to update itself to the official 4.8 again otherwise the phone won't sync with it.
It's important to keep the C:/takesonetomango folder as there is a handy file called "Restore.bat" which will use the backup created earlier to put NoDO back on your phone as Microsoft says you will not be able to get the official release unless NoDO is on your phone.
Hope you find this useful. If I have linked to something and not given credit to the original author please let me know and I will change the credit.
Enjoy
Tips:
1. If you have any problems with errors for "prov.cab" users have reported that sometimes rebooting can sort it, otherwise edit the update.bat file with the explicit path to prov.cab. Thanks to everyone in the thread who suggested this to help others!

Is Hidden WiFi feature enabled in this release?

The code is probably there but don't know how to enable it yet! There is a long discussion here:
http://forum.xda-developers.com/showthread.php?t=1233612
There is plenty of other reasons worth updating though!

Help!
Hi.
Trying to follow these directions. At step 9, am getting this error:
"File prov.cab is not accessible. Please double check your file."
Any idea what I might have done wrong? Do I need to uninstall everything and start over again?

Theycallme Tim said:
Hi.
Trying to follow these directions. At step 9, am getting this error:
"File prov.cab is not accessible. Please double check your file."
Any idea what I might have done wrong? Do I need to uninstall everything and start over again?
Click to expand...
Click to collapse
try running as admin.

Im actually stuck at step 16
Zune wants to restart the phone but nothing happens and the phone screen shows a picture that i should plug in the cable, but it is already
zune also consumes 30% of the cpu and that since an hour...
any ideas how to continue ?
/edit
just abort and retry
now running 7720

Was doing that, but that was a good suggestion.
z33dev33l said:
try running as admin.
Click to expand...
Click to collapse

try running not as admin, worked for me...

Just uninstalled everything and am going to start over from step 1.
No disrespect to all of you Mango lovers, but really wish the Pre 3 had made it to market right now. ... I'm sure I'll be more forgiving of some of the Mango shortcomings once I have successfully completed this process.

For what it's worth, i followed the instructions and am now successfully running 7720 RTM Mango.
The only stumbling block i had was going from 7712 to 7720, "ISVto7720.bat" was closing seconds after opening, a quick PC restart later however it worked first time, plain sailing aside from that.
Really enjoying all the new features thus far and i'm sure there's more i've yet to encounter - thanks for the clear and easy to follow instructions to help me get there.

Great to hear at least some success with these instructions!
It is a bit hit and miss, to be honest and each machine seems to have its own little subtle differences in the order that it installs device drivers etc.
If you get the problem with Prov.cab double check you have extracted the folder to the right place, the bat files have explicit paths in them (it doesn't just look for prov.cab in the same folder, it looks specifically for C:/RCtoRTM/prov.cab for example).
Jay

I'm going to try this later on tonight.
I have de-branded my HD7 a few weeks back using the two roms.
RUU_Schubert_O2_UK_1.57.728.02_Radio_5.52.09.16_22.33a.50.10U_Signed_by_ansar
RUU_Schubert_HTC_Europe_1.69.401.01_Radio_5.54.09.21_22.33b.50.10_Signed_SCHUBER*T_RELEASE
I assume this still will work?

dctrdre said:
For what it's worth, i followed the instructions and am now successfully running 7720 RTM Mango.
The only stumbling block i had was going from 7712 to 7720, "ISVto7720.bat" was closing seconds after opening, a quick PC restart later however it worked first time, plain sailing aside from that.
Really enjoying all the new features thus far and i'm sure there's more i've yet to encounter - thanks for the clear and easy to follow instructions to help me get there.
Click to expand...
Click to collapse
Same problem here with a few error messages, but finalli working on LG E900.
Thanks Jay

Just wanted to confirm that it has worked fine. Thanks Jay for putting the guide together.
Sent from my HD7 T9292 using XDA Windows Phone 7 App

Does anyone know if this procedure works for the Verizon Trophy (SparkW), and if not, is there any way to load Mango RTM without developer unlock?

General sanity check question: if one chose to update to Mango via this "unofficial" method, how can he be sure that his phone will be in a "supported" state afterwards? Or, to rephrase, what would be the purpose of updating now just to have to revert to the last backup in order to update officially once the update is released by the manufacturer?

AnnihilatorSC said:
General sanity check question: if one chose to update to Mango via this "unofficial" method, how can he be sure that his phone will be in a "supported" state afterwards? Or, to rephrase, what would be the purpose of updating now just to have to revert to the last backup in order to update officially once the update is released by the manufacturer?
Click to expand...
Click to collapse
As I know, the beta update in 7712 has all 22 Languages, while the RTM update posted here only has 6.
For those who just use one of those 5-6 default languages should have no problem, but the others who enabled other languages in 7661 or 7712 should have found the update is "unfinished" (I hope someone will notice), though the build is 7720.68 which is supposed to be real RTM.
If the update through Zune has all 22 languages available, it should be worth to update officially. As you know, there are always people who don't want to see the "Not for resale" logo in the boot screen while keeping the Mango features, me too.
When someone captures the RTM update files in all 22 languages before the update through Zune, then I will see no point to roll back the update and do once more officially.

henry084 said:
As I know, the beta update in 7712 has all 22 Languages, while the RTM update posted here only has 6.
For those who just use one of those 5-6 default languages should have no problem, but the others who enabled other languages in 7661 or 7712 should have found the update is "unfinished" (I hope someone will notice), though the build is 7720.68 which is supposed to be real RTM.
If the update through Zune has all 22 languages available, it should be worth to update officially. As you know, there are always people who don't want to see the "Not for resale" logo in the boot screen while keeping the Mango features, me too.
When someone captures the RTM update files in all 22 languages before the update through Zune, then I will see no point to roll back the update and do once more officially.
Click to expand...
Click to collapse
Actually, my Trophy only has 5 languages available. I remember that the update will not show all 22 languages, but it will support all of them. Selected languages will only be available on your phone based on the phones firmware region.

Just updated my hd7 and my wife's focus 1.3v to mango. This walkthrough is definitely great. For the focus i used senboston "ISVto7720" instead of the one in rctortm package. It is in the other THREAD post #508 mentioned in the first post here. With your indulgence, could you please enlighten me on how to use the restore.bat. Maybe another walkthrough for this is needed. Thanks again!.

downloaderintruder said:
Actually, my Trophy only has 5 languages available. I remember that the update will not show all 22 languages, but it will support all of them. Selected languages will only be available on your phone based on the phones firmware region.
Click to expand...
Click to collapse
It does support multi-languages shown up since 7004 (cannot said to be support), just not be able to type.
What I mean is the interface languages, which suppose to be a full support, instead of partial support as you have mentioned.
In beta update 7712, language packs will be updated according to your registry settings in NoDo, instead of the ROMs we have. I am just curious if 7720.68 through Zune will update in the same way.

Directions Please - Unlock/Backups/ROM/FLASH/MANGO/NODO/7004/Zune versions

Can someone please simplify all this for me?
The information on this site is so convoluded in terms of methods, some expired , some still valid, and guesses that are plain wrong, and irrelevancies.
I have been reading, installing, and uninstalling for hours into days.
Samsung Focus
1. Can Mango unlock be achieved with unlock from 7004?
2.I was on NoDo unlock and followed some instructions for the Focus that did not work. It went right to Mango LOCKED (as many others have reported).
I made a nice little back up of my NoDo unlock but can't get back to it using any version of Zune or any method, they all result in restore errors.
My back up might as well be on the north pole because I can't get to it.
3.I flashed back to 7004 and couldn't get chevron to unlock again like I used to be able to on XP or WIN 7 with various zune versions back to 4.7.
I'm wondering if the newer Zunes corrupted that somehow because last time it worked was on a fresh zune install on windows 7.
And besides that, they all ask to be upgraded before they do a back up, usually.
4.But even if it is unlocked at ROM 7004, zune updates (if chosen) will send it back to mango and locks it agian right? That's what happened last time , it just kept updating the phone for hours and then it was back to mango.
5.It appears my only option now is Mango locked or 7004 flash Rom with possible unlock.
Hopefully answers here will help others as well.

A few answers, though not compreheensive:
1) You don't have to let WP7 install each update, if you wanted to stop at, for example, NoDo 7392, you could. Just wait untilt he update gets that far, then pull the plug and/or hit Ccancel in Zune. Left to itsself, it will install all available updates.
2) The phone automatically dev-relocks whenever a major update is installed - this happens even to people with legitimate develop-unlock (and it's annoying!) For Samsung, I believe the technique for preserving unlock is the same one used to get interop-unlock on Mango: place an unlock provxml file in \provxml\ on the phone's filesystem (you can either use Heathcliff74's WP7 Root Tools to do this, or you can just install his interop-unlock XAP) and make sure you have a working version of the Samsung Diag app (should allow you to process provxml files). Once you have that, you can install all the way up to the Mango update safely, I think (I don't have a Samsung, but it should work) and use the Diag app to process your provxml file, which will both dev-unlock and interop-unlock the phone.
Not sure what's up with your backups; I can't really help you there without more information. What error do you get? What version of Zune are you using (you probably should use the latest version, 4.8.whatever)? How big is the backup (it's in %localappdata%\Microsoft\Windows Phone Update\)?
As for what guides to follow, starting with the stickies is always a good idea.

Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...

Gyuritzy said:
Hello,
I have a HTC Mozart device wich is momentarily running on unlocked NoDo.
I have followed various guides from xda but I end up running a locked Mango (most of the guides require after Mango update to run HTC Connection Setup to unlock... which I am unable to run (black scren) and all other apps tell me revoked by Microsoft).
is there any latest guide a little more foolproof?
It seems that after 18th October something happened with Zune which prevents Mango unlock...
Click to expand...
Click to collapse
After you install the interop-unlock xap while on nodo then goto mango you reinstall the diag app and in the Diagnosis app dial: *#9908#.. Select "Heathcliff74 Interop Unlock"
then tap Save, tap Close and exit the Diagnosis app

@lucasryan: Those are the instructions for a Samsung phone. They don't work at all on an HTC phone.
@Gyuritzy: Currently, Microsoft is pushing the Mango update and an HTC update together. The HTC update blocks the unlock path used with Mango. If your phone gets that update - which means if it gets Mango through the retail update path - there's no current way to interop-unlock it.
If you can get Mango through an atypical upgrade path (I came from the beta, which worked), or if you use a custom ROM (be *very careful* of the bootloader version if you try this!!), you can get interoop-unlocked Mango on HTC. It's not easy, though.

Ahh i see that i quoted his post now. as alan93 has focus

What solution do I have to load Mango without HTC update? Should I try with RCT2RTM type of packagge?

@GoodDayToDie
#1 - ahh ok, but I'm sure watching the update tentativley is required right? For like an hour and a half.
#2 - now see, there you go again, this is only for dev-unlock people which , i'm not even sure what that is..what? you pay $100 to MS to get it? It needs to be stated more clearly where ever that solution is posted AT THE VERY TOP like this "IF YOU ALREADY HAVE A DEV UNLOCK ....
@ lucasryan - That can't be right, -->"installing interop unlock on NoDo then go to Mango"...STOP RIGHT THERE. when you go to Mango it wipes everything out and you have no more access...unless of course ..YOU ALREADY HAVE A DEV UNLOCK...what ever that is.
I did try the diagnosis trick on update to mango after putting that file on there but the diagnosis version would not go higher than 908 or what ever. Couldn't get 1112 or what ever the one that is needed.
Please, just say there is no way to unlock Mango unless you have a dev unlock and that is low percentage as it is...then I won't expect so much.
Thanks for the replies.

Here is the zune error I get on trying to restore to my NoDo unlock.
http://answers.microsoft.com/en-us/...-restore/3ec7091d-d79d-422c-9995-cfe186e0155b
As you can see nobody is dying to answer it.
I think the code number means "this goon is trying to restore to an unlocked version, don't answer him".

@alan93: Developer Unlock is the term used for the change to your phone made by the Windows Phone Registration Tool (if you have a marketplace developer account), ChevronWP7 Unlocker (possible on pre-NoDo), ChevronWP7 Labs (coming soon), or changing the DeveloperUnlockState registry value located at HKLM\Comm\Security\LVMod to 1 (possible with the LG registry editor, or by using the Samsung diag app or HTC Connection Setup app to process to provxml file). The registry change is actually what matters; the other methods are simply ways to achieve it.
Dev unlock allows you to install XAP files - a renamed ZIP file with some manifest XML files, one or more managed (.NET-based) DLL files, and possibly other files needed by the application. Due to a bug in the application installer, you can also use a XAP to put arbitrary files almost anywhere in the filesystem (the installer can't write to the \Windows\ directory).
One of those manifst files specifies capabilities that the app has, which controls permissions of the app (for example, ID_CAP_ISV_CAMERA allows access to the public camera APIs). As of Mango, including beta versions, it is no longer possible to install apps with the ID_CAP_INTEROPSERVICES capability unless the MaxUnsignedApp registry value (located in HKLM\Software\Microsoft\DeviceReg\Install) is set to at least 300 (the default value is either 10 or 3, depending on the unlock method used). ID_CAP_INTEROPSERVICES is required for interfacing with drivers, a way for applications to run at high permissions (for example, to write to the registry). Each time you install a major upgrade, such as Mango, this value is reset to its default. An app with ID_CAP_INTEROPSERVICES therefore can't be installed (or run, if it was installed before upgrading to Mango) until this MaxUnsignedApp registry value is changed, a process referred to as Interop-unlock (term coined by Heathcliff74 on this forum). Marketplace-installed apps are exempt from this restriction, which is why things like Connection Setup (which has ID_CAP_INTEROPSERVICES) can be used.
For what it's worth, I got my dev-unlock by purchasing a marketplace developer account ($100 from MS). One day I may even submit an app to the marketplace, but so far all the apps I've written use homebrew and wouldn't be acceptable for the marketplace, so I just publish them here.

Thanks great explanation.
I intend to write my own too, I wrote one and have a few more great ideas but didn't want to pay until i made sure I was able to write them completely and testing on the simulator sux. And last I heard, the media player doesn't work with it.
I just think the fee and lockout just hurts development thereby limiting the success of WP7.
If it was $50 or less I would probably pay it.
I mean for crying out loud I'm a certified MCP/MCAD, they should give me a break here.

[FFU|Updated Possibilities|Tango]HTC Mazaa users, read this!

UPDATE 274/2012
Okay. So, Nokser's FFUPartTool extracts the IMGFS partition from the FFU.
Barin's OSBuilder (here) can be used to dump the contents of the IMGFS.
The registry files can then be edited in HVEdit (link), and the IMGFS can be recreated using OSBuilder.
FFUPartTool can then be used to replace the IMGFS partition in the FFU.
This FFU now needs a Mazaa to be flashed on.
If anyone out here is brave enough to flash their phone, please report the results!
UPDATE 17/4/2012
So, as we all know we have a stock mango FFU for the Mazaa (see here if you don't).
And due to recent developments, we also have this: FFUPart Tool v1.3.1
What this means is, we can create a custom FFU for the Mazaa. Now, personally, I have never created WP7 CFW before, but Nokser, the creator of the tool above assures me the creating CFW with this tool is quite possible.
So, what are you guys waiting for? Race to the finish line?
My list of things to be done starts and ends with this: get htc connection setup to run.
That's literally all we need to kickstart the Mazaa scene. Once we have that, we can do the whole shebang.
We need a ROM image for the Mazaa before anything at all can happen.
-------------------------------------------------------------
Here are the ROMs being used by people:
7.1.7649 - Test Rom. Has lots of interesting Microsoft applications (the zApps). But lacks quite a few features and stability.
7.1.7661.wp7_5_trial(mojobld).20110607-1657 - Similar Test Rom.
7.1.7720.68 - Locked bootloader. Phone is recognized as an HTC Device, but Connection Setup doesn't run.
7.1.7720.500 - Is basically the same as .68 but with an unlocked bootloader. Phone is not recognized as an HTC Device.
7.1.7740.16 - Updated via the official CAB [WP7 Cab sender tool]
7.1.8107.79 - via the official CAB [WP7 Cab Sender Tool]
7.10.8773.98 - via the official CAB [WP7 Cab Sender Tool] - 28/06/2012
Firmware revision number: 1600.1502.7720.68
Hardware revision number: 112.1410.2.0
Radio software version: 1.6.00.15.02
Radio hardware version: 8655/DDR2
Bootloader version: 7.27.00
Chip SOC version: 0.75.2.1
If anyone has different details, please post them.
-------------------------------------------------------------
The major problem with all ROMs is the lack of drivers.
1) LED lights don't function
2) SD Card slot
3) Connection Setup drivers
4) Internet Sharing doesn't work
Secondarily, because of the lack of connection setup drivers, there's no interop unlock. Which means no homebrew. Which means this device is pretty much what a technophobe buying a smartphone for the first time needs.
-------------------------------------------------------------
Does anyone know how to edit FFU (full flash update) files? They seem to be .cab files with a signed xml .blob in them.
Is there any way to edit these files?
Alternately, has anyone been successful at obtaining a stock ROM for the Mazaa? Because otherwise the device is extremely crippled.
Once we obtain a stock ROM, it's merely the point of identifying what drivers are missing, appealing to the DFT team to test the Mazaa to check whether HSPL/RSPL works, testing whether HTC Trophy drivers (and maybe other phones' drivers) work, cooking a rom, and flashing it. Once we get the ball rolling, it should all materialise.
-------------------------------------------------------------
Finally, what other problems are people having with their Mazaas?
Here's a list of problems I've noticed across the net:
Low battery life (4 - 6 hours at most).
Inability to connect to CDMA networks
Can't use HTC Connection Setup - hence no 3g/mms on certain networks
Inability to connect to certain GSM networks - lack of a valid IMEI
Frequent restarts/hangs [2 - 3 per day in some cases]
Each of these are frustrating faults.
Here' to hoping that the hundreds of DEVELOPERS with Mazaas can put in a concerted, collective effort and get this going. EVERY other phone has been unlocked/tweaked/improved upon, so why not a limited edition developer-exclusive device?

Thanks for summarizing the various versions. As developers, with a concerted effort, we should be able to resolve the issues and make it work for us.

I think most people sold the device, even if this wasn't allowed, at least for the first batch (not those won, but those requested for mango/gyro dev)
I had hopes battery problems where in a faulty battery...

even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.

abhilaksh said:
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
Click to expand...
Click to collapse
That's right, but they're probably not in dev hands anymore, so chances are not very helpful hands at this, especially since there's no more access to official updates.
All summed up, since not even the gyro works correctly on mine, it's a paper weight for which I'm still waiting for import taxes refunding

As far as issues, in addition to the above:
- I cannot send/receive MMS (SMS works, though)
- No 3G (DO or 2x only)
- 2-3 crashes per day
My build is 7.1.7720.68
Sent from my Mazaa using XDA Windows Phone 7 App

I have HTC Mazaa
I have the HTC Mazaa device that exactly matches all the details given in the original post in this thread.
For me, its working perfectly, no battery problems (works for 2-3 days), no crashes at all, I can't say about 3G support problems because we don't have that in our country. The phone works perfectly fine.
I have dev unlocked the device from App Hub but would love to remove the interop lock as well...in fact thats what I came here for.
Please guide me.
Thanks.

When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App

Please guide me on I can interop-UNlock the device.

How can I update my Mazaa to 7.1.7740.16 build?

Mike48236 said:
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Hello there,
Currently I'm using a Mazaa sent from MS with the 7720.500 fw, It has all the zApps and the internal MS apps like FindSomeone, it has battery issues (but it's not worse than an Omnia 7 with Mango), and there are four annoying things experienced:
- volume is always a bit too loud and MP3 playback is sometimes faltering
- when you press the ON/OFF button, sometimes the screen comes back immediately after turning it off
- when you place a call, sometimes the screen turns off immediately, which can be brought back using the proximity sensor (hold close to head, then move it away)
- cannot receive MMS messages
Exact details:
OS: 7720.WM7_Main(mojobld).20110723-1640
FW: 1600.1502.7720.500
HW rev: 112.1410.2.0
Radio SW: 1.6.00.15.02
Radio HW: 8655/DDR2
Bootloader: 7.27.0.0
Chip SOC: 0.75.2.1
I'm no expert in messing with phones (only using homebrews once they become 99.999999999% safe) but if I can help in any ways I'm not breaking this phone, I can surely do my part provided I'm given step by step instructions.

To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.

abhilaksh said:
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
Click to expand...
Click to collapse
I'm sorry but I'm not going to be of any help in getting an updated ROM, since we are low on the supply chain. Also, the way we get each new build is by getting a new phone. (Send back old one, get one with newer software.)

I have an HTC Mazaa, running 7720. Everything is ok for a dev phone, I have no serious problems with it, except EDGE/GPRS not working and speaker emitting a loud tone when I'm calling a number outside my network. I'm thinking of installing the new updated build. How should I proceed exactly? Should I use the cab sender tool? I also want to mention that the phone is not dev unlocked, I'm still waiting for a student unlock. Thanks.

download the cab sender.
download the cab.
place the cab in the same folder as the cab sender.
run the cab sender.
send the cabs to the phone.
you're done.

I tried to update my HTC Mazaa and I got an error at the first restart. But, after that I typed *#06# on the Phone hub and I get this IMEI: 00A100000794C***.
I did it again, but this time, with my SIM card inside the phone. Unfortunately, I got the old IMEI message: Failed.
***
Even after all could not update my smartphone:
Verificando o status do telefone: Completed in 2,01 seconds
Verificando requisitos do sistema: Completed in 0,11 seconds
Fazendo o download de atualizações: Completed in 2,87 seconds
Verificando requisitos do sistema: Completed in 0,01 seconds
Transferindo atualizações: Completed in 24,65 seconds
Preparando para instalar: Completed in 46,16 seconds
Reiniciando o telefone: Completed in 231,04 seconds
Instalando atualizações: Completed in 70,15 seconds
Verificando o status do telefone: Completed in 0 seconds
Reiniciando o telefone: Completed in 34,28 seconds
Concluindo atualizações: Completed in 20,04 seconds
Error:
Update device 53d261df - cd29c761 - 4fe43c2f - 733020be Complete with error code
: 80180048, error message: Falha ao instalar IU (Image Update) devido a um erro.
■
╚══════» Done

Is there anyone on xda-devs to help us update our HTC Mazaa and also do the interop-unlock?

Mazaa ROM
Hmm...
Here.
http://hotfile.com/dl/135477621/ed2186c/FlashClean.zip.html
That's an FFU.

Which cab should I use? Or which is the recommended one? Thanks.

Thankyou for that FFU
@abhilaksh Thankyou for that FFU file it saved me from alot of messing around. So happy to get my Mazaa back in working order. It broke on me a few months ago and ive been though hell trying to get the bugger fixed. It just got stuck on the mobile operator screen.
imgur(dot)com/oBH9M
Even had it sent off to UK repair center for them to send it back in the same condition (Idiots). I was just about to send it off to a US repair center when i did some more searching. It worked a treat, really straightforward as well.
If anyone else is a noob in the same situation as i way id recommend these simple instructions:
1. Install Zune Beta Client (beta includes the UpdateWP tool)
2. Install the SetupUpdateWp.exe to get the tool
3. Follow these instructions to flash your phone
mobilitydigest(dot)com/ms-instructions-on-how-to-flash-a-windows-phone-7-device/
Thanks again, Rob