Hello all,
I was getting that stupid 80180048 error trying to update to the mango beta. I'm on a student developer account and have never used Chevron yet still getting this error. After many frustrating hours trying everything I could think of I finally found this advice on the apphub forums.
1) Flash your phone back to its stock form... I simply search for "flashing rom focus" here and I found my rom at
http://forum.xda-developers.com/showthread.php?t=1131022
2) Start Mango process over
This removed whatever was causing me the problems that resulted in the 80180048. It's a pain to re-install my apps and settings but my phone is now updated to Mango Beta.
Hope this helps if you were stuck as I was.
This worked perfectly for me! Thank you.
for those who did "Walsh" their phones to get NoDo early...
ATT Focus in the US - not dev unlocked and no other modifications
I had originally used the "Walsh" updater to get NoDo early.
I used the "unwalsh" tool when it first showed up (well before the Mango beta was available), but I learned yesterday I used it incorrectly. Instead of selecting all keyboard languages present on the device, I selected only the active language.
I had the same "80180048" error when the 4.8 Zune software was trying to install the first of the two Mango-related updates.
I re-used the "unwalsh" tool, this time selecting all of the keyboard languages present, and the Mango Beta update installed successfully.
I did NOT need to flash back to stock 7004, thankfully.
unwalsh tool:
http: slash slash blog DOT walshie DOT me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track -- see my comment at the end of this post about an updated version of this tool floating around, though.
The info about re-using the tool came from an apphub thread:
http: slash slash forums DOT create DOT msdn DOT com/forums/t/85769 DOT aspx
Make sure you read that thread before updating, look for posts from Rafael, specifically. He also links to an updated (June 29, I think) version of the "unwalsh" tool.
I had the same experience.
Sent from my Windows Phone Mango Focus using Board Express
reflashed and done everything from the beginning but still get the same error. Ive tried everything thats been said.
My sister had a brand new Omnia 7 that I went through the updating process a few weeks, and I actually got this error when trying to install Mango for her. Tried everything I could (such as using the WP Support tools, Samsung Omnia 7 tools), but nothing could get Mango to install.
Decided to take the plunge and try flashing and now the phone is better than ever and happily running Mango. I think it's possible that there was an issue with the firmware or bootloader (it was an earlier version number than mine, and I was using XXJID).
After seeing how easy it was I decided to take the plunge and flash mine to the latest firmware available too, and it actually fixed up a few problems/bugs I've always had with the phone. So yeah, if you don't care about losing your texts/settings/game saves and you're feeling brave, I'd definitely recommend flashing your phone to the latest available rom
Neither I nor my buddy could update our Samsung Focus' to Mango without getting this error.
My buddy even spent an hour last night trying to get his phone to upgrade and always came up with the above error message.
Now today, BOTH of our phones were able to update to Mango via Zune without doing/changing anything.
It seems like MS was true to their word when they said they would have a fix for this issue.
I hope that everyone can now upgrade hassel free because Mango is beautiful.
This was my only work around. http://forum.xda-developers.com/showthread.php?t=1174848
fluffedup2 said:
ATT Focus in the US - not dev unlocked and no other modifications
I had originally used the "Walsh" updater to get NoDo early.
I used the "unwalsh" tool when it first showed up (well before the Mango beta was available), but I learned yesterday I used it incorrectly. Instead of selecting all keyboard languages present on the device, I selected only the active language.
I had the same "80180048" error when the 4.8 Zune software was trying to install the first of the two Mango-related updates.
I re-used the "unwalsh" tool, this time selecting all of the keyboard languages present, and the Mango Beta update installed successfully.
I did NOT need to flash back to stock 7004, thankfully.
unwalsh tool:
http: slash slash blog DOT walshie DOT me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track -- see my comment at the end of this post about an updated version of this tool floating around, though.
The info about re-using the tool came from an apphub thread:
http: slash slash forums DOT create DOT msdn DOT com/forums/t/85769 DOT aspx
Make sure you read that thread before updating, look for posts from Rafael, specifically. He also links to an updated (June 29, I think) version of the "unwalsh" tool.
Click to expand...
Click to collapse
This is the key exactly. Got look at the languages listed as available on yourdevice under keyboard. Chec the all on the Walsh App. It fixed mine!
Related
**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
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?
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!
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
Hi every one , please help .
I can't update my samsung focus further than feb 2011 updates , I'm using zune 4.8 and I live in lebanon .
please , guide me how to upgrade to mango . my software version : 7.0 ( 7008 )
thanks .
you can try this guide that was confirmed to be working http://www.wpcentral.com/force-mango-update-early-through-zune-software
good luck
thanks for replying but I still get the same message :
your phone is up to date
current phone software version : 7.0 ( 7008 )
machhho said:
thanks for replying but I still get the same message :
your phone is up to date
current phone software version : 7.0 ( 7008 )
Click to expand...
Click to collapse
I had the same problem with an OMNIA 7.
Solution:
Use ChevronWP7.updater (google) => will install Nodo 7390
After that use the by Chris Walsh provided repair tool for being able to recieve updates via zune.
After that use mangoforall V0.2 for provisioning your phone.
=> zune will update your phone to 7403 and finally to 7720.
Cheers
contable
Edit:
Before using ChevronWP7.updater make sure that you have installed Windows Phone Support Tool.
Microsoft Not Pushing Samsung Focus 7390 Update Anymore
I restored mine to 7008 and got the same problem. I did some snooping around and found this: http://answers.microsoft.com/en-us/...s-update/cbd79f58-36cf-457e-babe-134497ca6292
I also submitted my own question regarding the issue, but basically they are saying that you won't expect any updates for Focus rolling out from 7008 to No-Do. It has to be from 7390 to No-Do, otherwise nothing.
This issue may be fixed in the future once Mango has been distributed and celebrated, but only as an afterthought. What you can do is to force a Mango update on your phone. It will forego 7390,7392, and 740(see my post below). I'm still updating mine, so I'll get back at you for any news, issues, or developments.
denizen08 said:
I restored mine to 7008 and got the same problem. I did some snooping around and found this: http://answers.microsoft.com/en-us/...s-update/cbd79f58-36cf-457e-babe-134497ca6292
I also submitted my own question regarding the issue, but basically they are saying that you won't expect any updates for Focus rolling out from 7008 to No-Do. It has to be from 7390 to No-Do, otherwise nothing.
This issue may be fixed in the future once Mango has been distributed and celebrated, but only as an afterthought. What you can do is to force a Mango update on your phone. It will forego 7390,7392, and 7402. I'm still updating mine, so I'll get back at you for any news, issues, or developments.
Click to expand...
Click to collapse
After you get to Mango, if you don't get the Samsung Update, use this
http://forum.xda-developers.com/showpost.php?p=17917562&postcount=46
snickler said:
After you get to Mango, if you don't get the Samsung Update, use this
http://forum.xda-developers.com/showpost.php?p=17917562&postcount=46
Click to expand...
Click to collapse
This is amazing! But I want to keep the back up feature of Zune as restore points. I don't know how to manually do this with the Support Tool. I'll look it up later though. Thank you.
But I just realized I was wrong about my earlier post. If you force the update it will forego any other update between 7008 and NoDo. You'll jump straight to the normal course towards Mango.
denizen08 said:
This is amazing! But I want to keep the back up feature of Zune as restore points. I don't know how to manually do this with the Support Tool. I'll look it up later though. Thank you.
But I just realized I was wrong about my earlier post. If you force the update it will forego any other update between 7008 and NoDo. You'll jump straight to the normal course towards Mango.
Click to expand...
Click to collapse
use this http://forum.xda-developers.com/showthread.php?t=1103011
I have the same problem in HTC Mozart. I stuck on 7008 and my phone says that it's up to date. I have unbranded phone.
thanks a lot, I managed to update my phone to 7403 but when I try to update it to 7720 I get the Error Code : 801811A3
thanks
snickler said:
use this http://forum.xda-developers.com/showthread.php?t=1103011
Click to expand...
Click to collapse
I'll be posting 7008-Mango cabs from my other Focus that I'm updating soon.
Finally I got the mango on my phone , and for the Error Code : 801811A3 , I had to apply this patch MicrosoftFixit50581.msi
link to the patch = http://go.microsoft.com/?linkid=9758089
or
direct patch download link = http://download.microsoft.com/downl...13F-BAF2-A708DD4911D8/MicrosoftFixit50581.msi
same thing happened to me when I decided I was bored and wanted to unlock mango. Reverted all the way down the line and it said I was up to date, so I just forced the update each time till no-do rev2. just get on zune search for update and when it says no update found, click linking, and get ready cuz you got to be fast, but click update again and turn off your connection to the internet on your pc. Zune will then show your next update, turn your connection back on and update. Keep doing this till your at the update of your choice. at No-do rev2 it finally found the next update on it's own.