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?
I was playing with my unlocked phone with Build 7712 an hour ago and everything worked fine. Now, my unlocked phone can't run any of the side loaded applications, with the message "**** has been revoked by Microsoft. Please uninstall it".
Anyone encounter this?? Or anyone can highlight what did I do that cause the phone being locked again?? Should I just roll back to the previous build?
Did you include the prevent relock hack in the proxml you used to unlock 7712. If not when you connect it to Zune it will relock.
Sent from my HD7 using XDA Windows Phone 7 App
This has been answer many times. Mango auto-relocks your device (Chevron or Official Dev Unlock). Mango also blocks INTEROPSERVICES, which most homebrew apps use. There are also work arounds using provxml to re-unlock your device depending on what OEM device you have (Samsung/HTC works). Please use the search feature in the future or search on Google & you'll find the answers...
reeg420 said:
Did you include the prevent relock hack in the proxml you used to unlock 7712. If not when you connect it to Zune it will relock.
Sent from my HD7 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
I applied the prevent relock hack in NoDo and build 7660. But did not re-deploy the proxml after upgrading to build 7712. I guess this is the problem and the only way now is to roll back/flash back and start the whole process of chevron unlock again.
Thank you.
For me - on a HTC Mozart - it worked after going back to 7004 and applying all the updates until 7392 (Chevron unlocked/custclear.provxml in Windows-folder) You have to de-install HTC connection setup in 7392 before going on 7712!!!! (7401 and 7403 and after that to 7721) - check, if the provxml is in your Windows-folder and then update to Mango. After that re-install connection-setup (marketplace-search on phone), start connection-setup and... voila - for me it worked this way.
Roll back and re-upgrade to Mango with your device in flight mode and the jailbreak will be kept. (I am using a jailbroken Mango.)
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
So I've been browsing around for days trying to find where to bring in my unlocking endeavors, any help? Links, or anything of the sort. I have an hd7s with mango 7720 if that helps at all. Thanks.
I think you'd have to flash your phone with either a custom rom or a pre nodo rom then use chevron unlock and use ansars or petbede guide to upgrade to mango while retaining the unlocks. I personally have a legit $99 unlock on my pro 7 with nodo and followed petbede guide using ansars u2m7720 1.2 tool to upgrade to mango you also need to have HTC connection setup installed as its been removed from the market place.
Sent from my 7 Pro T7576 using XDA Windows Phone 7 App
sunspark said:
I think you'd have to flash your phone with either a custom rom or a pre nodo rom then use chevron unlock and use ansars or petbede guide to upgrade to mango while retaining the unlocks. I personally have a legit $99 unlock on my pro 7 with nodo and followed petbede guide using ansars u2m7720 1.2 tool to upgrade to mango you also need to have HTC connection setup installed as its been removed from the market place.
Sent from my 7 Pro T7576 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
im in a similar situation except im on nodo trying to go to mango
I can sideload HTC connection setup but it keeps saying that the database does not exist on the device
any suggestions?
@jaygriggs: A sideloaded version wouldn't work anyhow. It need the marketplace signature or you can't run it without already having interop-unlock, which makes it rather useless for the purpose of interop-unlocking your phone.
Ansar claims to have a way to interop-unlock HTC on Mango, but last I saw the mods had locked his thread for breaking the XDA-Devs forum rules (requesting donations before he'd send you the app).
GoodDayToDie said:
@jaygriggs: A sideloaded version wouldn't work anyhow. It need the marketplace signature or you can't run it without already having interop-unlock, which makes it rather useless for the purpose of interop-unlocking your phone.
Ansar claims to have a way to interop-unlock HTC on Mango, but last I saw the mods had locked his thread for breaking the XDA-Devs forum rules (requesting donations before he'd send you the app).
Click to expand...
Click to collapse
i was beginning to think a signature was the issue.
Most apps dont work on a cdma device
I'd have no problem donating if i knew it was going to work
Where would I begin to flash a custom rom? Or roll back to chevron unlock?
I'm having the same questions/issues also. I have an HTC Trophy, was on NoDo, and I have a developer-unlock (student unlock, so I can sideload 3 apps)
I followed these instructions:
Download/Install: TouchXplorer and HTC Connection applications
Download/Install: The App Deploy file (that deploys CustClear.provxml to the My Docs\My Ringtones folder)
I then did this:
1) use TouchXplorer to copy the CustClear.provxml file to the \Windows\ folder
2) Run HTC Connection and click the Checkbox
3) Repeat Step 1 again (to put that file back in the \Windows\ folder)
4) Update to the next version using Zune (one below Mango)
5) Repeat Steps 1 thru 4, which now updates to Mango
After Mango was installed, I am still at the student/developer unlock (up to 3 sideloaded apps). What did I do wrong, and what do I need to do to get Mango with unlimited sideloads?
Thanks in advance.
@Avazee: You have to use an upgrade path which gives you 7720 (Mango) and the HTC Update for Mango in different steps. This used to be done by using the beta upgrade path.
The problem is that 7720 re-locks the device against ID_CAP_INTEROPSERIVES, so you have to use Connection Setup to interop-unlock it. The HTC update doesn't re-lock the device, but it prevents you from using Connection Setup to make changes (it also breaks some other homebrew, like TouchXplorer). If you get them at the same time, which is how MS is currently pushing the Mango update, your phone gets re-locked and you lose the ability to unlock at the same time - very unfortunate.
You could use This, no idea if it works tough. I have been upgrading to Mango with the U2B2 tool
GoodDayToDie said:
@Avazee: You have to use an upgrade path which gives you 7720 (Mango) and the HTC Update for Mango in different steps. This used to be done by using the beta upgrade path.
The problem is that 7720 re-locks the device against ID_CAP_INTEROPSERIVES, so you have to use Connection Setup to interop-unlock it. The HTC update doesn't re-lock the device, but it prevents you from using Connection Setup to make changes (it also breaks some other homebrew, like TouchXplorer). If you get them at the same time, which is how MS is currently pushing the Mango update, your phone gets re-locked and you lose the ability to re-lock at the same time - very unfortunate.
Click to expand...
Click to collapse
Thanks for the reply. What do you mean by HTC Update? I didn't get any HTC update...
How do I use an upgrade path that gives me Mango and this 'HTC Update' in different steps?
Thanks for your help.
Avazee said:
Thanks for the reply. What do you mean by HTC Update? I didn't get any HTC update...
How do I use an upgrade path that gives me Mango and this 'HTC Update' in different steps?
Thanks for your help.
Click to expand...
Click to collapse
I really hope someone can prove me wrong (I have been reading and looking for weeks on this forum and yet to see otherwise). For HTC going to Mango and retaining interop-unlock, all I have seen mentioned that works is starting with a Shubert ROM (spelling?) and using U2B2 method or a cooked ROM.
BUT, this does not work as these ROMs will not work on the CDMA version WP7 phones (which VZW HTC Trophy is one, sprint is another). I have not seen anyone take the stock NoDo CDMA ROM that came on our phones and get to Mango interop-unlocked. There is no pre-nodo CDMA ROM in existence.
Anyone, please prove me wrong as I would really like to be wrong.
I don't currently know of a way to avoid getting the HTC update bundled with the Mango update. The approach used previously was to install the Mango beta, interop-unlock it, then upgrade to 7720 (Mango release), and since that didn't include the HTC update you could interop-unlock it too. You could then install the HTC update if you wished.
For users following the retail update path, the HTC update is simply part of the Mango (7403->7720) update.
e900
how do i know if my phone is jailbrake or not????
Your Phone is unlocked if you can sideload Applications Rom our PC. You are unlocked if you have flashed a preunlocked ROM or if you are a Developer and unlocked it with the Unlock tool OR if you have used the ChevronWP Unlock Tool