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
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!
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!
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
I used Nokia Care Suite to get the AT&T Tango update for my cyan Lumia 900. Since then, I've seen a couple of older posts (pre-Tango) that talk about not being able to update your phone through Zune if you used Nokia Care Suite to update a device, but the thing I can't lock down is if that is only if the ROM used was not an official one. Does anyone have any feedback on this issue? Have I hosed myself a little and now I can ONLY update using NCS or since I used the official ROM, am I still good to update through Zune whenever another update is available? Thanks, and sorry if I'm asking a questions that's been answered before .
Relax. If you flashed the official ROM designated for your phone then you're good to go. The Zune update installs the latest ROM in steps (3 in the latest update) file by file and leaving data/settings in place. Flashing wipes the device and replaces everythng with a factory fresh ROM image that already includes both the latest OS and Nokia firmware tweaks.
Cheers
dougthug said:
I used Nokia Care Suite to get the AT&T Tango update for my cyan Lumia 900. Since then, I've seen a couple of older posts (pre-Tango) that talk about not being able to update your phone through Zune if you used Nokia Care Suite to update a device, but the thing I can't lock down is if that is only if the ROM used was not an official one. Does anyone have any feedback on this issue? Have I hosed myself a little and now I can ONLY update using NCS or since I used the official ROM, am I still good to update through Zune whenever another update is available? Thanks, and sorry if I'm asking a questions that's been answered before .
Click to expand...
Click to collapse
One of the great things about xda, things do go untried. Maybe there has been no success in breaking the OS, but the people around here push everything else.
I didn't know for sure if using Nokia Care suite would allow me access to the future updates. So, I used the Suite to downgrade from tango. Plugging into Zune immediately triggered the Tango update packages, all 3 of them.
I figure if it works going backwards, it will work going forwards. So, as the last responder said...Relax, you're good dog.
alodar1 said:
One of the great things about xda, things do go untried. Maybe there has been no success in breaking the OS, but the people around here push everything else.
I didn't know for sure if using Nokia Care suite would allow me access to the future updates. So, I used the Suite to downgrade from tango. Plugging into Zune immediately triggered the Tango update packages, all 3 of them.
I figure if it works going backwards, it will work going forwards. So, as the last responder said...Relax, you're good dog.
Click to expand...
Click to collapse
Excellent news. Thanks for the reply's
dougthug said:
Excellent news. Thanks for the reply's
Click to expand...
Click to collapse
In Nokia Care Suite, if you want to experiment and flash your phone with an update not yet available for your product code, you can rename another ROM with your own code and it will work, but then your phone is "walshed" - ie; won't update through Zune but you can always reflash.
As mentioned before, as long as you use the ROM with name matched to your own product code, Zune will work fine.