Develop Bugs

Glad I didn't jailbreak

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?

Will forced Mango provisioning keep you from receiving carrier firmware updates?

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

Rolled back from 7720 to 7004 and Zune says my software is up to date?!?!

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

Need help updating ancient pre-production software on AT&T G8

Hi guys. I got a G8 from a friend whose friend's dad is a radio tower engineer for AT&T that got this phone early. It's a prerelease phone (says "not for sale") on the back, and it comes with software that is seemingly far behind what shipped with the public version of the device. It's Android 9 with the December 2018 security patch, SW version G820UM04b. This version is pretty buggy and doesn't have some features like air motion. It seems like the initial software release for the public phone was G820UM10g.
Whenever I try updating the device, it just says the software is already up to date. I've done more factory resets and tried more tricks than I can even recount. Got a fresh new SIM card. Called AT&T and got them to manually push the update to my IMEI (which is correctly registered), waited a day for the update. Tried LG Bridge but it's incompatible with AT&T devices. Looked for kdz files online for the AT&T version that I can flash using LGUP, but there's no AT&T files available (pls tell me if anyone knows of any out there).
I'm at my wit's end guys. Anyone have any ideas as to how I can get this phone updated? I'm realizing that I really took the ability to just unlock and flash my old OnePlus for granted

Where do you live ?
Mobile AT&T only support to update OTA if you live in US !

minhthien0711 said:
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
Click to expand...
Click to collapse
Sorry, forgot to clarify that. I live in the USA and I use AT&T.

On the face of it it's not looking good. There aren't any KDZs for ATT as standard, and you can't update OTA - one thing to check here is the S/N field, pre-production LG phones are usually missing this, which is usually why OTAs don't work.
However, pre-production devices can, sometimes, be cross-flashed. You could try using LGUP to flash a more recent US unlocked build. It is likely to give you the IMPL lock / mismatch / crossflashing not allowed error, but it's worth a shot.
If that doesn't work, your best bet will be to ask your friend's dad to take it in to work (when he can...) for whoever looks after devices for his team to flash it to production as a favour.

Question LE2125 in US still waiting on update?

I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?

ptmuldoon said:
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
Click to expand...
Click to collapse
I also haven't received on the same device and version. So, it's seems like a slow rollout

If you manually check for updates in settings does it tell you you're up to date? If so, I'd just get the update from Oxygen Updater and do a local install. Some people did have issues with the first release of OOS12 (C36) but those should have all been resolved in the next one (C39). I never had any issues with the update personally.

Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.

ptmuldoon said:
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
Click to expand...
Click to collapse
Probably because C36 is the full update. If it won't let you download both C36 and C40 at the same time (before updating), I'd make sure you have access to wifi in case you're one of the lucky few affected by the mobile network issue in C36. But most likely you'll be fine, the other issues were very minor and you wouldn't even notice if you just install the second update right away.

Does Chrome auto fill work for you on 12? I heard that it was broken, but don't know whether it's been fixed with C40? Holding off on updating until someone can confirm. Thx
EDIT: Decided to bite the bullet and upgraded to C40 on my L2125. I actually like it quite a bit, but can confirm that for me, at least, Chrome auto-fill doesn't work. Other nit is you cannot put the battery percentage in the status bar AND remove the icon; either you have both, none, or just the icon. Also, Netflix is pre-loaded, but won't open or uninstall and update and when I go to the Play Store it shows as incompatible with my device?? (bootloader unlocked, but not re-rerooted yet). Also the power menu no longer gives you a recovery or bootloader option in rebooting. Good things include having more gestures (raise phone to answer) and a panel to control apps that auto-start or not. Also, somehow m yreboot sequence no longer includes the danger, your bootloader has been unlocked, screen (which I didn't think was possible to get rid of).
Rolling back to Android 11 for now. Also, many more root options still available there (like Gravity Box and JamesDSP)