Hey guys,
I was wondering if there was anyone else who had run into this issue, or if anyone had a way that might solve this problem for me.
I have a Samsung Focus through AT&T - back in April (I think) I did the VPN to Hungary method to update my Focus to NoDo. Everything looked fine at the time, but I guess there was something different about the image that got put on my Focus, as now that I have updated to Mango, my phone says that Marketplace is not currently available in my region/country
I believe this is because some part of the phone thinks I am in Hungary, and Hungary is not part of the Mango beta.
Any thoughts on how to fix this? Sadly when I did the Mango update, my phone was syncing with Zune as a guest, which apparently means it does not keep a backup image...would have been nice to know that earlier too unfortunately.
Thanks!
codechinchilla said:
Hey guys,
I was wondering if there was anyone else who had run into this issue, or if anyone had a way that might solve this problem for me.
I have a Samsung Focus through AT&T - back in April (I think) I did the VPN to Hungary method to update my Focus to NoDo. Everything looked fine at the time, but I guess there was something different about the image that got put on my Focus, as now that I have updated to Mango, my phone says that Marketplace is not currently available in my region/country
I believe this is because some part of the phone thinks I am in Hungary, and Hungary is not part of the Mango beta.
Any thoughts on how to fix this? Sadly when I did the Mango update, my phone was syncing with Zune as a guest, which apparently means it does not keep a backup image...would have been nice to know that earlier too unfortunately.
Thanks!
Click to expand...
Click to collapse
I don't know if there's a more convinient solution, but what you certainly can do is flash a stock ROM and then let Zune do all required updates until WP7 is build 7392 again. From that point on you should apply the mango update again and be then able to use the marketplace again.
dkp1977 said:
I don't know if there's a more convinient solution, but what you certainly can do is flash a stock ROM and then let Zune do all required updates until WP7 is build 7392 again. From that point on you should apply the mango update again and be then able to use the marketplace again.
Click to expand...
Click to collapse
Ah awesome! I have not had experience with flashing a stock ROM before - I will take a look around the forums. I assume I will have to download the stock AT&T focus image, and then use Zune to "restore" the image?
Thanks for the advice!
codechinchilla said:
Ah awesome! I have not had experience with flashing a stock ROM before - I will take a look around the forums. I assume I will have to download the stock AT&T focus image, and then use Zune to "restore" the image?
Thanks for the advice!
Click to expand...
Click to collapse
Yeah, you gotta get the appropriate ROM for your device (and if you want to keep the addtional AT&T apps and such, take care of getting an AT&T ROM). I'd start from scratch though, so no rollback of any backup afterwards. Takes more time, but you'll definitely be on the safe side then.
Finally got my Focus working completely with Mango!
For anyone else who has this problem - i went here (http://forum.xda-developers.com/showthread.php?t=1131022) to get the focus ROM - flashed all the way back to 7004 - updated to 7008, had to unbrand (not sure why, Zune wouldn't give me nodo) to NoDo, and then do the regular update process to Mango.
Whew
Related
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
IF anyone can help I would be much apprecitive.
I have a problem where I was on Mango 7720 RTM and I re-flashed ansars 7004 ROM.
Now when I hook my phone up to zune, it says my version, 7004, is up to date. I did this a while back to get my phone out of a "super walshed" mode and it updated just fine. Now I can't update past 7004 because it says I'm already updated. Please help if anyone can, I've been researching this like crazy.
The420Dank said:
IF anyone can help I would be much apprecitive.
I have a problem where I was on Mango 7720 RTM and I re-flashed ansars 7004 ROM.
Now when I hook my phone up to zune, it says my version, 7004, is up to date. I did this a while back to get my phone out of a "super walshed" mode and it updated just fine. Now I can't update past 7004 because it says I'm already updated. Please help if anyone can, I've been researching this like crazy.
Click to expand...
Click to collapse
+1 I'm in the same exact situation. Currently trying to do the unbranding method but it's not working. Might have to try the Hungary VPN method.
The420Dank said:
IF anyone can help I would be much apprecitive.
I have a problem where I was on Mango 7720 RTM and I re-flashed ansars 7004 ROM.
Now when I hook my phone up to zune, it says my version, 7004, is up to date. I did this a while back to get my phone out of a "super walshed" mode and it updated just fine. Now I can't update past 7004 because it says I'm already updated. Please help if anyone can, I've been researching this like crazy.
Click to expand...
Click to collapse
guys i had the same problem i was trying all i could do to solved the problem for almost 10 hrs, yes i said 10 hrs with three computers.
Finally, i ended up using ChevronWP7 Updater. now i have nodo
Don't use the chevron updater it could prevent you from getting future updates.
I just don't understand why it says I'm already up to day when I'm not. It should let me update. I've tried installing different Zune versions but have had no luck. I'm downloading Zune version 4.7 to see if that works. We will see. I will post my results back.
The420Dank said:
I just don't understand why it says I'm already up to day when I'm not. It should let me update. I've tried installing different Zune versions but have had no luck. I'm downloading Zune version 4.7 to see if that works. We will see. I will post my results back.
Click to expand...
Click to collapse
I already tried that, still doesn't work.
When I posted on wpcentral about it, several users posted saying that fresh out of the box devices weren't getting any updates either. They were 7004 too.
Perhaps MS turned off all updates until tomorrow?
Updates are probably all turned off until tomorrow for Mango. They can't get rid of the No-Do updates completely though because I don't want to be in 7004 forever Dx
XboxOmac said:
Updates are probably all turned off until tomorrow for Mango. They can't get rid of the No-Do updates completely though because I don't want to be in 7004 forever Dx
Click to expand...
Click to collapse
I agree, this seems to be the most logical answer. I guess wait until the mango update is released then try again. If it still doesn't work, well I'm sure there are ways lol.
ryude said:
I agree, this seems to be the most logical answer. I guess wait until the mango update is released then try again. If it still doesn't work, well I'm sure there are ways lol.
Click to expand...
Click to collapse
And I've been researching like crazy Dx
The only reason I reverted back to original ROM was to chevron-unlock my Focus, then unbrand it...
Btw, anyone know if unbranded phones get the update first or AT&T phones? Otherwise, I'll just registry edit the mobile operator thing again.
XboxOmac said:
And I've been researching like crazy Dx
The only reason I reverted back to original ROM was to chevron-unlock my Focus, then unbrand it...
Btw, anyone know if unbranded phones get the update first or AT&T phones? Otherwise, I'll just registry edit the mobile operator thing again.
Click to expand...
Click to collapse
AT&T will be the first to get the update, tomorrow. Unbranded phones will probably receive it on the same day.
So glad to see these posts, thought I was the only one, I started on Sunday and all day yesterday I could get it to 7008 but no further, now today I cant get past 7004. Hoping tomorrow will open things back up and I can update to Mango! I have a Samsung Focus on AT&T.
I think it would help a lot if we all kept this thread up to date on when the updates start working again and what exactly you did to get it to update.
i have the same problem reverting my wifey mozart to 7004. at the end i use the unplug cable method and it worked. currently her phone now on 7392(NoDo) with chevron-unlock
hopes this help
fulat said:
i have the same problem reverting my wifey mozart to 7004. at the end i use the unplug cable method and it worked. currently her phone now on 7392(NoDo) with chevron-unlock
hopes this help
Click to expand...
Click to collapse
Unplug cable method?
I guess I'll wait until tomorrow. Don't know if a time frame is planned. I'm on EST so I wonder if they are going by EST or PST. Doubt the updates will be up by 12:01 Am. Guess that's me being too hopefull.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I think its a great idea as well, to keep this thread updated and followed.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I noticed that the versions of my 7004 does not match the versions of the official 7004.
AT&T Original
Total Storage: 7.39 GB
Available Storage: 6.85 GB
OS version: 7.0.7004.0
Firmware revision number: 2103.10.10.1
Hardware revision number: 3.1.0.7
Radio software version: 2103.10.10.1
Radio hardware version: 0.0.0.3
Bootloader version: 4.10.0.1
chip SOC version: 0.36.2.0
Ansars UCJK2 AT&T
Total Storage: 7.39 GB
Available Storage: 6.95 GB
OS version: 7.0.7004.0
Firmware revision number: 2103.10.11.2
Hardware revision number: 3.1.0.7
Radio software version: 2103.10.11.2
Radio hardware version: 0.0.0.3
Bootloader version: 4.11.0.9
chip SOC version: 0.36.2.0
Ryude, do you think that would be making a difference?
Sent from my SGH-i917 using XDA Windows Phone 7 App
The420Dank said:
Ryude, do you think that would be making a difference?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
I honestly do not know, it seems like many people in that thread received the update without problems. I am just making observations, whether they are relevant I cannot say.
I guess the only thing we can do is wait and see if Mano even launches tomorrow or not but when it does, see if we can update and go from there.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I have updated to Mango. and it was running slow so i decided to do a wipe. once i did, i noticed almost all my ringtones i had prior to mango are gone.!! anyone have a zip file of the pre-mango ringtones?
Please post stock WP7.5 Ringtones
Hi, there this is off topic, but do you think you could please upload the stock ringtones from your Samsung Focus in a zip archive here? Thank you!
I assume you are talking about the at&t ringtones. you can get them back if you flash the original factory at&t 7004 firmware which can be found in the samsung focus firmwares and then update your phone to mango via zune. somewhere along the upgrade process they are mucked up in the rom becuase of how mango changed how ringtones can be added to your phone. you could also probably just pull them from the firmware files and then load them on your phone via zune.
voluptuary said:
I assume you are talking about the at&t ringtones. you can get them back if you flash the original factory at&t 7004 firmware which can be found in the samsung focus firmwares and then update your phone to mango via zune. somewhere along the upgrade process they are mucked up in the rom becuase of how mango changed how ringtones can be added to your phone. you could also probably just pull them from the firmware files and then load them on your phone via zune.
Click to expand...
Click to collapse
Anyone else notice this? I flashed to 7004 and performed the update through Zune, and I'm still missing them.
Edit: Actually, I may have wiped due to GPS being broken...
Trying again.
This is so strange...anyone know if it happens to a straight out of the box Focus? (Instead of those manually flashed back to 7004?)
inconceeeivable said:
This is so strange...anyone know if it happens to a straight out of the box Focus? (Instead of those manually flashed back to 7004?)
Click to expand...
Click to collapse
I don't think you can get a Focus with mango shipped on it so I am sure it is the same on all of them, they have probably fixed it with the Focus S though.
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.