Related
I updated my HD7 (UK O2 16GB) to NoDo on Friday 18th March and it appeared to update correctly. However i do not appear to have Copy & Paste!!!
The system info states;
OS 7.0.7008.0
FW 2250.09.11902.206
When I access a website (bbc.co.uk), select a text/sms or a Word Mobile 2010 document, i do not get the option to copy any text!!
If i search the market place for "Frogger" which was one of the diferrences highlighted in the WinRumor video on the Internet , I DO get the Frogger app listed FIRST in the search results (i did not get this before the NoDo update).
When i connect to Zune it tells me the device is up to date and there is no update for it.
How do i prove the NoDo update was successful or force the update again?
You didn't update to NoDo
You've updated with the pre-NoDo update (7008), which essentially does nothing visible to your phone. NoDo isn't officially out yet (though you can flash it, have a look in the HD7 forum).
Casey
That is not the NoDo update you have only install the pre-update, NoDo is still not out for most of the phones, the firmware versions should be 7336 instead of 7008
I updated my hd7 to the Nodo update. My Version is 7.0(7389)
Bye
I carried out the pre-NoDo update a couple of weeks ago, then on Thurs 17th (i was out celebrating St Patricks day!!) it advised me another update was available.
Zune connected and it went through a 9 stage update and rebooted the phone a couple of times.
A couple of times during that process i had a black and white picture of a phone and PC connected via a cable with a red warning saying do not disconnect on the phone screen.
Which is the correct NoDo update version 7336 or 7389 or is the version carrier specific?
Hi, I just receieved my Samsung Omnia 7 sim free phone and it came with 7.0.7355.0
This has Copy and Paste in it already so has my phone shipped with the NoDo upgrade as I have a different firmware number to those quoted...
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'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.
After hearing T-Mobile finally roll out Final Mango for Schubert, i decided to roll back 7008, my old back up before, but after i did that, everything i have until now is "your phone is up to date (7008) "
Okay, that suprised me, i take out ANSAR old 7004 ROM and flashed it back to 7004, and then Zune got update to 7008 to me and same thing happen all over agian.
Try to Update to mango beta, no work, try the shutting down network card = failed, i am stuck at 7008.
So, my question is , does T-Mobile stop supporting Nodo or something happen with my phone?
Anyone here facing the same problem?
Nevermind, quick Emails with T-Mobile support and they have solved it.
Sever issue.
Request mod to close thread.
hmm interesting because I have unbranded HTC Mozart and have the same issue.
so i twas t-mobile problem or global server issue?
majkeljj said:
hmm interesting because I have unbranded HTC Mozart and have the same issue.
so i twas t-mobile problem or global server issue?
Click to expand...
Click to collapse
That guys said nothing about international. He just said that if i have to roll back to 7008 next time, i should wait for couple hours, since, you can't get a one-all the way update from 7008 to 7720 yet.