Related
Locking... Was it all Zune?
I was wondering, since Chevron was able to work only with Zune, and if you wish to install
a new update on your device, you must update the Zune first.
Is there a possibility that Zune is the one that makes all the problems?
Maybe they altered the ports that Zune uses to comunicate with WP7 device,
and since the chevron used HTTPS, they're not compatible any more,
and therefore, they can not comunicate.
I know it sounds like conspiracy theory, but i was checking protocols and have found some inconsistencies...
Maybe im wrong...
Your opinions?
NoDo doesn't require an extra Zune update, so no.
Arktronic said:
NoDo doesn't require an extra Zune update, so no.
Click to expand...
Click to collapse
Unfortunately, pre-Nodo aksed for Zune to update...
At least it asked me to update it...
That's where my doubts come from
for me, when i couldn't get wp7 unlocked i noticed that either zune or windows was changing the host file just as chevron tried to connect... no matter what i did ie changed values , edit user rights, even tried system with read only rights ,... something kept changing the host file to "my ip.windowsdevelopers.com" now i use a win7 instalation in a virtual drive with no zune or windows updates at all. seems to work for me..
Interesting solution...
I have tried installing Zune on another computer and tried to run Chevron,
but no luck... All I'm getting is error, that Chev. can't make connection with device.
Current state of OS: Build 7008 (That's pre-Nodo right?)
Cheers!
yep 7008 is pre nodo... i unlocked with chevron with that os. used vmware workstation. clean install of win7 (no updates except windows phone 7 usb drivers) then zune. unlocked first time.
you may have to re set your phone?
Well i did hard reset my phone for a couple of times, but had no luck...
I shall wait now... I will probably try some more on other computers, but
if I don't succeed, I will play by MS rules and do the NoDo.
After that, the waiting for a jailbrake shall be waited upon
P.S. A question, bit off topic.
Is there any way to insert custom ringtone to a non-Cheved device?
I can't access My Ringtones folder via Windows Explorer, even though
i changed registry on my computer to be able to access the phone as
a regular usb device...
Tnx up front, for any info provided
not really.... even if you did put them in your music folder zune on your phone doesn't seem to read the id3 tags and calls them unknown without names.
try..... fresh install win7 then connect phone aand get drivers... then zune... then chevron,
Yep, that's the problem with ringtones, or music at all...
I will try that with Win7, because i curently have no other options
Anyway, many thanks for your help!
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.
Instructions:
1. All contents must be extracted to a local disk, not a backup/external disk. I can recommend to put all contents of the extracted Mango folder directly to C:/ (If you got enough available space)
1a. C:/NoDoToRC
1b. C:/RCToRTM
1c. C:/Zune
2. Install the zune beta client version 4.8.2134.0 (comes with the downloaded file)
3. If necessary (usualy is), run the flashing tool "updatewp" from the folder "update tool" install right version for your system, 32 or 64-bit
4. Connect Device via USB to the PC
5. Close Zune software if it opens when connecting
So I have the current version of zune at the moment and I'm on step 2. DO I have to delete the latest version and install the older beta version to continue updating from NoDo to Mango 7720RTM?
Yes, I know the official update is available, but not for me and I read somewhere that if I go to the RTM version I will then get the notification to updae to official mango..
So please answer my question and this can be deleted
Yes, you need to uninstall zune and then install the beta zune as it contains the updatewp files that match accordingly. I saw somewhere on here someone who had an updated updatewp that matches zune 4.8.2345 but I cannot locate it right now.
Have you tried the click update over and over again in zune while disabling and enabling your internet?? I know of 2 HD7s and 3 Trophys that have gotten the official 7720 update doing that!!
Yes I have tried that disconnect trick so many times but no luck I'll delete zune and install the older beta Hopefully I can then continue without problems...
lol another question:
I have made it to the point that my phone is now on 7403. Then it said that there is another update available which I think is 7712? Now it says roughly translated "please wait. Searching for free diskspace required for the update."
It has been like that for 20 minutes now, what do I do now? Wait? Cancel it and start searching for updates again in the settings->phone->update in zune?
I've never seen that error... If you are on 7403, and your phone is accessible by touch, then I would disconnect your phone, reboot PC and phone, and try again.
Good luck!
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.
I've been looking into modding my Lumia 640 WP10, and it seems like most if not all of the apps involved require deploying with Windows Phone Power Tools. When I try to use it, it tells me the phone needs an update, and launches the Phone Tools Update Pack which always results in this message: "The update operation did not succeed. You can press Rescan to try reconnecting to the device. The exception code and error message is: 0x80004003 - Object reference not set to an instance of an object."
I have not been able to find any information about this particular error, and any assistance would be very helpful. I have already set the phone to developer mode and been able to deploy the root tool, but have been unable to do anything else without the power tools.
Same problem
I think the newest update is buggy. I was trying to do the same and keeps getting the same error. This might help you.
I'm not sure why the forum only emailed me for the first reply so I'm a bit late seeing yours, DaRealAce. I am not actually using an Insider build right now but thank you, that link did help. It's definitely not the same problem, but I was able to fix mine by using the Interop Tools app linked in that thread. Since that is an appx I was able to sideload it, making vcREG unnecessary. After going through the unlock settings in that app, I was able to deploy the AdBlocker app (my original goal) using the regular WP 8.1 Deployment Tool rather than WP Power Tools, which did not work previously.
Oddly though, somewhere in the process the phone no longer shows up on the PC as a mass storage device.
the same