Develop Bugs

Report Walsh + 7392 status

**MOD EDIT**​The team behind the development of this tool have stated that this tool may indeed prevent you from being unable to update your device in future. Links to the tool have been removed.​
WithinRafael said:
STOPPPPPPPPPPPPPPPPPPPPPPPPPPPP. We're actually going back and forth with Microsoft on this to prevent a Super Walshed phone (one that cannot be fixed without flash). Please wait
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------
If you Walshed your phone and received notification for the 7392 (ssl certificate) update, please chime in here with your phone make/model/MO. Immensely appreciated! (Please refrain from "not me" posts.)

Hello All,
I have an HTC 7 Pro that I "walshed".
I have today received the message to get the latest update to 7392.
I am in the process of doing the update. Should it fail, I will let you know.
I also have a Omnia7 that was updated to 7390 using this method. I will check to see if it has the update an let you know.

I have got one HTC 7 Pro "walshed",the second one HTC 7 PRO no"walshed"
Upgrade for 7392 was going well.

Sadly, update failed!!
Am about to try going back to original ROM and trying again.

What was the error?

It simply gives me an error code: 80180048
Any ideas what I can do to sort this problem?
Thanks

o2 UK HD7, Walshed update, then the HTC update. 7392 fails after completing a backup.

And another o2 UK HD7, Walshed updated.
7392 fails after completing a backup.

Walsh'd to NODO and my phone updated fine.
HTC Surround US AT&T.

I didn't walsh but instead used this pre-existing hack. Confirmed that the ability to sideload is still functioning by installing the default email hack xap. I hope posting this accomplishment doesn't mess with the overall aim of this thread.

blindpet said:
I didn't walsh but instead used this pre-existing hack. Confirmed that the ability to sideload is still functioning by installing the default email hack xap. I hope posting this accomplishment doesn't mess with the overall aim of this thread.
Click to expand...
Click to collapse
You did. The focus of this thread is to gauge MS's claim that Walshed phones won't get any future updates pass NoDo. It has nothing to do with jailbreaking, side loading etc.

sorry i want to ask those with an HTC 7 PRO, What do you mean you walshed your phone? didnt it already come with nodo?

foxbat121 said:
You did. The focus of this thread is to gauge MS's claim that Walshed phones won't get any future updates pass NoDo. It has nothing to do with jailbreaking, side loading etc.
Click to expand...
Click to collapse
Updating via Zune tricks isn't Walshed. Looking just for folks that specifically used Chris Walsh's update tool. Thanks though

I agree with you. Hence I updated my post to highlight what I was talking about.

Walshed, followed by HTC update.
Got the 7392 notification yesterday, but update fails after backup (error 80180048). I have tried multiple times to no avail.
After hard reset, still fails.

Same error
Walshed, T-Mobile Germany. Got the same error, tried several times. What can I do, to get the update?

I get update 7.0.7392.0. on my Optimus 7 works without problems, phone was not walshed.

For those getting error 80180048:
can you confirm whether your phone was flashed one of Ansar's roms?
I have a HTC trophy that I can't update coz of the rom I flashed it with. from what i understand it's a problem with the bootloader.
see my thread about error 80180048 here

Just walshed
Hi, I just used the chevronWP7 to Update to NoDo. No other flashs or changes.
The Upgrade worked from 7004 with 2 reboots and no errors.
Now im getting 80180048 after Backup.
Does this Info help?

I updated Mozart 7, walshed, dev unlocked, Telstra branded, ansar signed, 7004, Walsh 7008, walsh Nodo, Microsoft 7392, normal update, through Zune. Even backed up the phone fine

Glad I didn't jailbreak

Those who were too impatient to wait for the official update and took matters into their own hands are paying for it.
http://www.dailytech.com/WP7+Users+...+Stuck+MS+Says+We+Warned+You/article21550.htm

i forced my phone to 7930 build and according to that site microsoft wouldn't allow the forced update phones to receive furthur updates. well this is not guarenteed. i forced my phone to 7930, my htc surround. and i recieved this morning the 7932 update. so the article posted on your link could very well be true but its not 100%

If they had kept their word and kept the Carriers out of the equation, they wouldn't have had to worry about this ****...

I used the debrand + VPN method for 7390, then rebranded for Samsung firmware update. Debranded again for 7392. All of them were successful.
Samsung Focus.

I'm restoring my phone to see if I get the supported firmware update. Wow... I can't believe this. I got it through Zune, too...
EDIT: Got an instant update notification after restoring for March 2011 update. Will install it and see which version it sent. Apparently you cannot see this from the update screen to make sure you're getting the correct version...

note that this is referring to a specific update tool that was used and prevents users from getting further updates. The author of that tool is coming out with a fix.
http://www.neowin.net/news/did-you-hack-on-the-wp7-update-no-more-updates-for-you
not everybody who 'hacked' their phone to obtain the update sooner is affected.

I wiped my phone to pre-nodo factory settings and got an update, but it was 7390...
The article states that 7390 was an unofficial pre-release build and inferred that 7392 was the official update.
What gives?

7390 was only unofficial if you used the chevron updater. It was an official release if you used Zune. Not all phones have been updated to 7392 in the US yet, especially T-Mo users. Just be patient if you used Zune....you'll get it.

yes.. all who used the vpn method are considered official back then... i confirmed my self that i used the hungary vpn method and updated mine yesterday

N8ter said:
I wiped my phone to pre-nodo factory settings and got an update, but it was 7390...
The article states that 7390 was an unofficial pre-release build and inferred that 7392 was the official update.
What gives?
Click to expand...
Click to collapse
yep,
7390 is official not a pre-release. 7392 is official as well. if you used any method other than Zune to update then your 7390 is 'unofficial'. The article talks specifically about the Walsh method to update to 7390 'unofficially' as it bypasses Zune and uses MS's own support tools. Apparently users who used said method have problems updating to 7392 through Zune. If you are in the US you might be able to get 7392 by debranding, obtaining 7392 and then rebranding again. Best to just wait until ATT gets this through though.
ps: if you used debranding to get your nodo early you may not have gotten the latest firmware, bootloader. if you rebrand your phone then you will get the 7390 again and it will now also update firmware, bootloader, radio etc.

Versions
On my Focus, the ChevronUpdater NoDo gave me 7390 but did not change Firmware, Radio Software or bootloader versions. I subsequently received the official Samsung Update for NoDo through Zune and these did change. I have not received the 7392 update yet. I am waiting for Walshes fix to come out to allow for future updates. I am glad I forced the NoDo update through the ChevronUpdater. I knew Walsh would find a solution that would be supported by MS (at the very least, reviewed and commented on).

The reception on my HD7 is still crap after this update so even if those did change I guess there weren't any factorable changes in it...
Maybe 7392 will improve that when it comes...

I forced NoDo, but I got the 7392 update perfectly fine.
HTC Surround, walsh'd twice, then updated to 7392 yesterday.

amtrakcn said:
I used the debrand + VPN method for 7390, then rebranded for Samsung firmware update. Debranded again for 7392. All of them were successful.
Samsung Focus.
Click to expand...
Click to collapse
the update geek speak of this post smells oddly familiar of android rom flashing geek speak... hmm....
i'm standing on my head and stacking greasy marbles with my elbows to ensure the planets align and my alarm clock works (apple jab) in the morning too

I really don't understand the point of this thread. The "article" linked in the OP is filled with inaccuracies and a few outright falsehoods.
Besides, there was no "jailbreaking" involved in the Chevron Updater (unlike some of the other tricks people used to get NoDo early), and Chris Walsh is working (with Microsoft's help) to get a fix ready that will restore all of the phones to an update-friendly state.
Next case.

its nothing to do with jailbreak.... only chris walsh method of NODO update phones are having issue....
i forced my update with the second method, where i have to turn off my wifi/internet connection on the PC or notebook.... it worked for me and i updated my phone yesterday with 7392 as well...
if i am not wrong the VPN way of getting NODO update was alright as well... only chris walsh way u will not have a restore point. anyway there is a small patch is been issued by chris walsh and its been checked and verifyed by MS right now, but i beleive this will be the last time MS will help Chris Walsh, next time uses will have to bring the device to telcos or the OEM's and warrenty will be voided and need to pay to fix the issues..

Looks like there might be hope for jailbroken phones after all:
http://pocketnow.com/windows-phone/microsoft-validating-fix-made-by-chevron-to-fix-stuck-phones

i haven't walshed or forced NoDo and can't update, maybe its the prevent relock hack thats blocking the update. I debranded using official HTC Mozart rom(gold card), unlocked, prevented relock and updated with zune. Any ideas?

MartyLK said:
Looks like there might be hope for jailbroken phones after all:
http://pocketnow.com/windows-phone/microsoft-validating-fix-made-by-chevron-to-fix-stuck-phones
Click to expand...
Click to collapse
Chevron update method has nothing to do with jailbroken. It doesn't not jail break your phone. So, stop refer to this as jailbreak.

N8ter said:
If they had kept their word and kept the Carriers out of the equation, they wouldn't have had to worry about this ****...
Click to expand...
Click to collapse
when did they say that?

***A Warning Concerning The Walsh Update Tool***

WithinRafael said:
STOPPPPPPPPPPPPPPPPPPPPPPPPPPPP. We're actually going back and forth with Microsoft on this to prevent a Super Walshed phone (one that cannot be fixed without flash). Please wait
Click to expand...
Click to collapse
Pretty much says it all........
Probably best to stay away until theres more news on this.
When there is I will update this post.

If you’ve used the unofficial ChevronWP7 updater tool and then received a 80180048 error message in Zune, you have a very easy solution for that, at least if you are a HTC HD7 owner.
I recieved this error when I tried to install security update 7392. So I downloaded the latest official image for my phone from this site and flashed it to my O2 DE HD7. After that there was no 80180048 error during the update process and phone has now 7392 build.
You can find at leas 16 branded ROMs for HD7 right here: http://forum.xda-developers.com/forumdisplay.php?f=783

I Walsh'd my HTC Surround and everything worked fine for me...
I'm guessing there is a chance that the update will work for anyone. If you wanna risk it.

Chris has released a tool that should fix any problems that can't update. It's also been tested by MS.

i have a walshed hd7 and encountered the same problem when updating to build 7392.
i was dumbfounded when the update worked on my other laptop.
just sharing guys.

keyboardP said:
Chris has released a tool that should fix any problems that can't update. It's also been tested by MS.
Click to expand...
Click to collapse
I had used the Chevron update tool to get NoDo initially (then weirdly got it again!) - and The 'De-walshing tool' worked great for me too....

good thread

good thread

So good it had to be spammed twice

I still can't update my Omnia 7. Still on 7008. Damn!

Will forced Mango provisioning keep you from receiving carrier firmware updates?

I've been trying to find an answer for this to no avail. I had unlocked my phone using the methods described here (really in ansar's thread http://forum.xda-developers.com/show....php?t=1101344). My problem is, I rolled back to Nodo hoping to get the Tmob firmware update without having to flash the phone and wipe everything. I also rolled back Zune to 4.7. But, the only thing I get prompted to update to is Mango 7403. Which I thought would only happen if 1. You had the UpdateWP.exe to point your Zune client to the MS test servers and 2. There was a file to initiate on the phone that allowed it to get the Mango update. So, after completing deleting the Zune client and reinstalling, I still only get the Mango beta update message, which leads me to believe there is something with the phone that is keeping it from seeing the updates from Tmobile. And maybe it has to do with the Update_Mango.xap that alters something on the phone. I guess my question is, by using the methods in this thread and Ansar's, would that keep your phone from receiving firmware updates from the carriers? Or has anyone who has unlocked up to Mango beta, then went back to Nodo on Tmob, received the firmware update? Thanks a lot!
Also, wasn't sure if this should be in General, Q&A or what. Chose this section since it stems from the use of hacks in Development section. Please feel free to direct me accordingly.

kwill said:
I've been trying to find an answer for this to no avail. I had unlocked my phone using the methods described here (really in ansar's thread http://forum.xda-developers.com/show....php?t=1101344). My problem is, I rolled back to Nodo hoping to get the Tmob firmware update without having to flash the phone and wipe everything. I also rolled back Zune to 4.7. But, the only thing I get prompted to update to is Mango 7403. Which I thought would only happen if 1. You had the UpdateWP.exe to point your Zune client to the MS test servers and 2. There was a file to initiate on the phone that allowed it to get the Mango update. So, after completing deleting the Zune client and reinstalling, I still only get the Mango beta update message, which leads me to believe there is something with the phone that is keeping it from seeing the updates from Tmobile. And maybe it has to do with the Update_Mango.xap that alters something on the phone. I guess my question is, by using the methods in this thread and Ansar's, would that keep your phone from receiving firmware updates from the carriers? Or has anyone who has unlocked up to Mango beta, then went back to Nodo on Tmob, received the firmware update? Thanks a lot!
Also, wasn't sure if this should be in General, Q&A or what. Chose this section since it stems from the use of hacks in Development section. Please feel free to direct me accordingly.
Click to expand...
Click to collapse
I think if you update to Mango beta, you possibly miss the firmware update of HTC for HTC phones, or people who update to Mango earlier.
Just roll all the way back to 7004 and 7008 if you have HTC device and get the update with New Radio and Firmware.

Strike_Eagle said:
I think if you update to Mango beta, you possibly miss the firmware update of HTC for HTC phones, or people who update to Mango earlier.
Just roll all the way back to 7004 and 7008 if you have HTC device and get the update with New Radio and Firmware.
Click to expand...
Click to collapse
Ok, maybe I will just roll all the way back. I just didn't want to as I have to reinstall EVERYTHING and set my phone back up the way I like it. I assume that you saw the update after rolling back as I saw your other thread?

I rolled back to my NoDo update that I had right before upgrading to the first Mango beta. I still had the beta version of Zune, and the phone prompted me to update the HTC Update, which installed fine, and then I continued to upgrade to beta 2.
Keep in mind that the HTC Update is going out slowly, not all at once, so not everyone will get prompted all the time.

prjkthack said:
I rolled back to my NoDo update that I had right before upgrading to the first Mango beta. I still had the beta version of Zune, and the phone prompted me to update the HTC Update, which installed fine, and then I continued to upgrade to beta 2.
Keep in mind that the HTC Update is going out slowly, not all at once, so not everyone will get prompted all the time.
Click to expand...
Click to collapse
Ok, well that's reassuring. I think my problem is that I didn't do a backup of Nodo before I updated to the Mango Beta. Later on (after provisioning the phone and such to receive the Mango beta), I rolled back to Nodo, set up everything again and then did a backup. You are right though in the fact that I could just not possibly have received the HTC update as of yet.

Did you unbrand your phone? That was my problem. I have mango installed but my phone was unbranded. All I did was rebrand it and got my firmware update from Tmobile for my HTC HD7.

Daily | Daily.com
Thanks man
Regards

[NEWS]MS has totally changed the update process to Mango 7720, by ansar

Dear forum members,
This is to inform you that MS has totally changed the update process from PreNoDo / NoDo to Mango 7720
The process is a chain of updates and after Mango 7720 an hTC update is received
Finally OEM, SYS, Radio and bootloader are all updated and the HSPL is lost
For hTC_Europe the update is:
OS version: 7.10.7720.68
Firmware: 2250.21.40502.401 >> ROM version 4.05.401.02
Radio: 5.69.09.29a_22.50.50.21U
Bootloader: 4.5.2250.0(129185)
I am preparing a new U2M7720 xap in order to preserve unlock
Regards, ansar

will this new one work for all us who have accepted the htc drivers update and cant roll back??

ansar.ath.gr said:
Dear forum members,
This is to inform you that MS has totally changed the update process from PreNoDo / NoDo to Mango 7720
Click to expand...
Click to collapse
I was about to restore my NoDo backup in order to get interop-unlocked when I saw this thread. Thanks for the heads-up. You just saved me the ton of aspirin I'd have needed!
And thanks for all your work.

For the HTC devices, can you package in the required version of Connection Setup to make this work all the way through the final upgrade AND keep 3G alive?
Also, I assume you will need to start from an unlocked pre-NoDo or unlocked NoDo?
Last question - when you get to the final Mango, will you have set the phone to be interop-unlocked and prevent-relock with registry mods?
Sorry for all the questions

great.. i cant wait for this update to hit my device.. hopefully it will repair the bootloader problem.

this sorta scarees me
well this seams sorta scary for hd2 users will thay still beable to use MAGLDR 113 to dule boot wp7 & android on hd2?
i understand the process is quite diffrent from the rest of the wp7 phones and thare bootloaders?

i am going thru this process now. reverting back to NoDO(7392) this morning but tried to force update not working. backup was corrupted as well.
so no choice i have to go abck to factory default ROM. then only it start all the update from 7004 to 7008 to 7392 to 7403 to 7720 to HTC driver update all the way without stopiping.
u have to do ya dev-unlock really fast in order for them to carry on the next update.

ansar.ath.gr said:
Finally OEM, SYS, Radio and bootloader are all updated
Click to expand...
Click to collapse
Is this the firmware update we've been waiting for? Does this mean internet sharing on older htc devices such as hd7 work now? or is this some other kind of update?

The previous official Mango(7720) update only provide Microsoft update. after that Mango(7720) update. by right you should receive another update from HTC. its called HTC driver Update previously.
from today update onward for HTC device. the HTC driver update which come after Mango(7720) update previously will be bundle together with Mango(7720) update.
i did that just now and found my bootloader and firmware was still the original before Mango(7720) update. it has come to the latest one after i check Mango(7720) updated. and there is no need for HTC driver update anymore.

spicemaster said:
Is this the firmware update we've been waiting for? Does this mean internet sharing on older htc devices such as hd7 work now? or is this some other kind of update?
Click to expand...
Click to collapse
Hi,
This must be the final cause includes hTC OEM too, see 1st post for revion numbers
Regards, ansar

i'm not sure if i get it right...
1st we go to 7403....then to final mango(7720)...and then to htc update(again 7720)...3 steps of update....RIGHT???
so if we want to just go to final mango...can we use that old trick or not???
or ms has just put final mango and htc update into one update???i mean ms makes it 2 steps instead of 3...right???

This is nothing new... It has been the case since day 1 of the mango official release through zune....
I did the update (with the internet disconnect trick) on my Trophy and it was a 2 step update:
1st i got the 7403 rom
2nd i got the 7720/HTC drivers COMBINED update (which got installed in 1 go!)
After this, my phone was at 7.10.7720.68 with firmware revision 2250.21.40600.168 , radio 5.69.09.05a_22.50.20.21U and bootloader 4.6.2250.0(129185) and LOCKED!!! (and couldn't unlock as HTC Connection manager did nothing at all!!!)
I had to go back to my nodo restore point (but with spl 4.6.2250.0 which didn't change) and perform the "beta" way(U2B2) to 7403 ISV and then to 7720 ISV which got unlocked by Connection setup, and then return the phone to "normal" mode (DoNotU2b2) and get the HTC driver update (the phone remained unlocked!)
I have preserved all the MANGO/HTC combined update files just before they were deleted by the updater program during the transfering to the phone, and you can clearly see that there is a large cab file ~147Mb which is mango and a second file ~62Mb which contains all the HTC drivers/bootloader/applications ...
Here is the HTC file:
http://www.filesonic.gr/file/2232797321/5D13C8D0-4E9D-4C8C-9E93-9AC2B392B55E_100.cab

fulat said:
i am going thru this process now. reverting back to NoDO(7392) this morning but tried to force update not working. backup was corrupted as well.
so no choice i have to go abck to factory default ROM. then only it start all the update from 7004 to 7008 to 7392 to 7403 to 7720 to HTC driver update all the way without stopiping.
u have to do ya dev-unlock really fast in order for them to carry on the next update.
Click to expand...
Click to collapse
Hi there,
I just cancel the update and apply the dev-unlock and then search for update again, that's how I did with the whole process and it works and I am still dev-unlock.
Hope I Have Been Of Help. PEACE!!!

This might be the exact reason, why am I saying, that provisioning between updates (U2M7200) is working just on some phones. As deliol said earlier, this applies from day one, where my stock NoDo Mozart was updated in one turn with the 7720 install. Provisioning stopped working after that, even if I deployed ProvXML after the 7403 update and on Mango again. I even have higher versions than ansar and deliol.
NoDo > Summer HTC Update for Mozart > 7403 > Mango
OS 7.0.7392.0 > xxx > 7.0.7403.0 > 7.10.7720.68
FW 2250.09.12902.401 > 2250.09.13001.401 > xxx > 2250.21.40600.401
Radio SW 5.52.09.16.22.33a.50.10U > 5.54.09.21_22.33b.50.10U > xxx > 5.69.09.05a_22.50.50.21U
BL 1.28.2250.4(113913) > 1.30.2250.1(117833) > xxx > 4.6.2250.0(129193)
xxx means no change

Ffs overnight either ms or HTC done something all 3rd party apps gone, limit back to my developer 10 and not letting install any 3rd party back on can't retest new 3rd party apps looks like full wipe of phone n restart unless someone works how to hack through mango
Sent from Ant's HTC 7 Mozart using XDA Windows Phone 7 App.

went back to no do unlocked used ansar u2b2 and it went straight to 7720.68? and is fully locked now, please help.

You're not the only one. Just wait until someone finds a way to hijack Mango. As new devices which can not be downgraded are on the market, the interest for this will grow.

Hm, bad news as it seems :/
I tried it yesterday with ansars U2B2 tool and I am running 7.10.7720.68. Only difference to Ansars version number is the firmware revision number: 2250.09.16901.401 with hardware revision number 0002.
I installed the HTC Update when the official Mango update was announced worldwide while I was still running Mango B2 Refresh on the phone.
Right now, applications with the interop capability still run, but they are limited. The Advanced Touch explorer only shows his own application folder and registry is not available. I guess its because of the changed way the HTC DLLs can be used. Lets hope for Ansar or Heathcliff to figure this out

Does it matter what hardware version does one have as long as their mango is unlocked and can do sideloading.just my 2 cents.