By now im sure everyone has updated their OS to 8773 or Tango. Im assuming most of us, especially Rogers Lumias, are still stuck on 8107 for the Firmware software (nokia's software, not microsofts) Is there any way to force update the firmware? especially with the stupid purple screen issue.
OP, please don't confuse people. You are waiting for the Nokia Firmware update: 2175.1003.8112.12085 to fix the purple screen issue.
Firmware updates have nothing to do with OS updates. They sometimes arrive at the same time, but that's only for convenience, not necessity. When Nokia, and or Rogers, are ready to push the Firmware update to you, you will get it. No idea, btw, what's taking them so long.
Sent from my Lumia 900 using Board Express Pro
iphonepimp said:
By now im sure everyone has updated their OS to 8773 or Tango. Im assuming most of us, especially Rogers Lumias, are still stuck on 8107 for the Firmware software (nokia's software, not microsofts) Is there any way to force update the firmware? especially with the stupid purple screen issue.
Click to expand...
Click to collapse
You posted this at 6PM last night... I made a thread early in the afternoon about how to do this (my way doesn't screw up future updates)...
Related
http://www.winrumors.com/exclusive-att-windows-phone-7-nodo-update-due-april-19/
Unless you have a Surround, for some reason?
perhaps some problem with Surround, or AT&T just want to maintain their status...
Could AT&T be testing the HTC-specific update? Or did that go out to branded phones?
about time...
Too bad I updated a month ago...
kdj67f said:
Too bad I updated a month ago...
Click to expand...
Click to collapse
lol me too but who knows maybe there will be a firmware update thrown in..
Sent from my SGH-i917 using XDA Windows Phone 7 App
I have to figure out how to restore back to 7004. bad news is my computer crashed and I had to reinstall my OS and I lost my restore point in zune. Would any restore file work, even if some one sent me one that they did when they updated?
Anyone know?
Sent from my SGH-i917 using XDA Windows Phone 7 App
TOA Duck said:
I have to figure out how to restore back to 7004. bad news is my computer crashed and I had to reinstall my OS and I lost my restore point in zune. Would any restore file work, even if some one sent me one that they did when they updated?
Anyone know?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Other people who used a workaround to update their phones to NoDo said they also received the offical update. So you might not have to restore to 7004
That will be cool
Sent from my SGH-i917 using XDA Windows Phone 7 App
Schismal said:
Unless you have a Surround, for some reason?
Click to expand...
Click to collapse
According to the Windows Phone Blog it's because of an HTC Specific update (not surprising since they always try to add their own touches to phones they make.) that ATT and Microsoft still have to test and approve.
I guess I'll just be waiting a bit more for the update. I'm glad I didn't force the update through, especially if the HTC part of the update brings a more polished experience to my phone.
Curious whether people who already updated to NoDo will see the ATT update in Zune. I would assume the version number is identical and it would just tell me that it is already up to date?
wait and see I guess.
Mid may maybe for surround. I hate att.
Sent from my T8788 using XDA Windows Phone 7 App
Well it's the 19th. For those who have had actual upgrades phones already... can we actually expect the update on the delivery date, or will it most likely still take time to actually send out the update?
cgibsong002 said:
Well it's the 19th. For those who have had actual upgrades phones already... can we actually expect the update on the delivery date, or will it most likely still take time to actually send out the update?
Click to expand...
Click to collapse
Assuming the 19th is correct and they do start delivering it today, it could takes weeks for everyone to get it, some may get the notice today others not.
I rebranded, plugged my phone in, and got a prompt for the update, but I'm not going through with it because those AT&T features are lame, plus, I already used the VPN hack to get NoDo
Oscardog777 said:
I rebranded, plugged my phone in, and got a prompt for the update, but I'm not going through with it because those AT&T features are lame, plus, I already used the VPN hack to get NoDo
Click to expand...
Click to collapse
UPDATES ARE INDEED HERE!!!!
I'm downloading mine right now. I never unbranded or anything so I'm curious to see what kind of differences I will see.
cgibsong002 said:
UPDATES ARE INDEED HERE!!!!
I'm downloading mine right now. I never unbranded or anything so I'm curious to see what kind of differences I will see.
Click to expand...
Click to collapse
Prepare to enjoy much faster app loading and of course copy and paste
Just plugged in phone, got message for "Samsung Update". I had performed the VPN hack and got nodo a while ago, so everyone should be getting something. (at least for the focus)
and its here
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
JustinL01 said:
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
Click to expand...
Click to collapse
Very nice if it turns out to be true
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
From what i understood the O2 phones firmware was the same as the sim frees/all the others, meaning o2 wont even be involved in ANY updates , that they'll all just come direct from Google.(that has to be good news)
Nice to know it's on the way though, although i've yet to experience the problem in "real life" and not having to put another phone 2mm away from it.
rbs_uk said:
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
Click to expand...
Click to collapse
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
oscillik said:
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
Click to expand...
Click to collapse
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
Hmmm I personally doubt it, since the firmware is supposed to be un-tied to carrier tinkering.
If the carriers are aware of what firmware any of it's customers handsets are running, that raises another worrying issue. But I really don't think that they are capable of finding this out.
As an aside, I used to work for the UK's largest pub gaming machine company, and we had the largest network of computer-based touchscreen gaming machines (at the time at least) and they all ran a custom java based software running on top of Windows. When we made updates to the games or anything else, we would always roll out the update to 1000 machines as a preliminary measure.
The difference there however is that we knew exactly which machines had the updates, and could keep track of any issues that popped up. I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
oscillik said:
I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Click to expand...
Click to collapse
could be.. as you'd think atleast 1 of the 1000 would have posted here on XDA
**edit**
post above proves me wrong - although my android version is 4.0.1 and i have had no update
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
The HSPA+ version of the Galaxy Nexus has always had 4.0.1, so you haven't received any update at all.
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
It would likely go to Google, not O2, and is IMEI based, so they will know how many and which handsets have received the update. They will log the IMEIs that the update was sent to and if you call your various support options with a complaint one of the questions will certainly be your IMEI number. Then this can be cross-referenced to see if you have received the update or not (and evaluate 1. it's success 2. other problems it generated).
When the phone's IMEI gets released for the OTA, there is a "whisper" service that checks the software/whatever version and if below the impending OTA it will prompt the notification for the update- if the same it will send no notification and the user will have no idea of/no need for the OTA. At least this is generally how the G1 and N1 both worked in the past.
JustinL01 said:
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
Click to expand...
Click to collapse
He never mentioned what build number he had, as you can see he just mentions Android version:
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
They all say 'Android is updating' everytime you power the phone on ;-)
oscillik said:
He never mentioned what build number he had, as you can see he just mentions Android version:
Click to expand...
Click to collapse
No not the poster I am talking about what I was advised by O2, it is the buildnumber that differed with the update.
drp297 said:
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
Click to expand...
Click to collapse
Ice Cream Sandwich does that. Everyone's phone does that, it's already been raised on here in at least two separate threads.
It doesn't mean you have received an Android update, it is regarding Android getting the home screen and apps ready.
an OTA update would require user intervention to be applied - you would have to first of all agree to the phone downloading and applying the update.
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
gambiting said:
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
Click to expand...
Click to collapse
It was due 5pm yesterday too. Fingers firmly uncrossed, only a single digit is required aimed squarely at sam/goog.
I heard that they are updating the baseband, not the software version...
So I have a Cyan unlocked 900 here in the UK. I am on FW 2175.2101.8779.12201 and Zune shows no updates available.
In NaviFirm there is a 2175.2503.8779.12301. Does anyone have any info on this version and whether it is safe for me to flash it? I am keen to get some of the improvements to the camera that the recent AT&T update supposedly gave.
Thanks
I updated my rm-823 in the UK to the latest 2175.2503.8779.12301, I had 8773, and the phone seems a lot quicker.
I had the screen not brightening up to an appropriate level for some seconds (not good when trying to answer a call etc, the phone took 30+ seconds to start charging and some other weird issues to do with response)
I would recommend to upgrade if you had anything like the above problems, but no idea what this new FW is supposed to sort out.
The Jones said:
So I have a Cyan unlocked 900 here in the UK. I am on FW 2175.2101.8779.12201 and Zune shows no updates available.
In NaviFirm there is a 2175.2503.8779.12301. Does anyone have any info on this version and whether it is safe for me to flash it? I am keen to get some of the improvements to the camera that the recent AT&T update supposedly gave.
Thanks
Click to expand...
Click to collapse
Hi
Update just popped on my White Lumia 900 Uk , seems to be a small firmware update.. dont know what it fixies though
tfn said:
Hi
Update just popped on my White Lumia 900 Uk , seems to be a small firmware update.. dont know what it fixies though
Click to expand...
Click to collapse
I have been using it for a few days. It seems to fix almost nothing. The camera is still sub-par at best and I still have the issue during phone calls where the other party gets echo feedback.
The auto screen brightness is still really slow and dim witted but very slightly improved.
Just got 8779.12228 here in Canada (Rogers). I wonder if the firmware updates might also be carrier specific???
Unlocked RM-823.
Just got an update.
Firmware changed from 2175.2101.8779.12201 to 2175.2503.8779.12301.
Radio changed from 2.1.75.20 to 2.1.75.25.
Not sure what it actually did.
drtolson said:
Just got 8779.12228 here in Canada (Rogers). I wonder if the firmware updates might also be carrier specific???
Click to expand...
Click to collapse
Are you sure it's 12228?
The Jones said:
I have been using it for a few days. It seems to fix almost nothing. The camera is still sub-par at best and I still have the issue during phone calls where the other party gets echo feedback.
The auto screen brightness is still really slow and dim witted but very slightly improved.
Click to expand...
Click to collapse
I got a refurb Lumia 900 to replace my broken LG Quantum. I had a really bad echo problem, and no updates fixed it. Contacted ATT who sent me another refurb, and echo is completely gone even on the highest call volume(old phone had to be no higher than 6). I think it's a hardware problem, look around on Nokia's support forums, seems most could only fix it with replacement. I also had the vibration rattle, and that is gone in the 2nd refurb.
xsever said:
Are you sure it's 12228?
Click to expand...
Click to collapse
Nope, slipped fingers... it's 12224. Sry...
The Jones said:
I have been using it for a few days. It seems to fix almost nothing. The camera is still sub-par at best and I still have the issue during phone calls where the other party gets echo feedback.
The auto screen brightness is still really slow and dim witted but very slightly improved.
Click to expand...
Click to collapse
I had two replacements before this issue was resolved. I was told by the Nokia care manager it was a faulty microphone.
So I would not hold my breath a software update will fix your issue.
As for photos check the link out.
http://mywpstory.com/2012/04/camera...-with-your-new-nokia-lumia-900-windows-phone/
I'm on Rogers and I still don't have 8779. Took forever to get 8773 in fact I only got it last week. Oh and forcing the upgrade doesn't work I tried it a few times as per the instructions. Unless I'm doing it wrong someone correct me here you plug in your phone go into settings and click update then click off then click again and after 3 seconds pull the internet connection ...right?
Double check in settings that the firmware is 8773 or 8779, Reason being is that the wifes Lumia 900 has an 7.10.8773 OS but 2175.2503.8779.12301 firmware whereas my lumia 900 has 7.10.8779.8 OS and same firmware as wifes phone (8779) Weird I know but maybe worth checking.
Indeed you have a point there. My phone has OS 8773 and firmware 8779 but what exactly does that mean.
Why can't they just give us 7.8 as it is and push out the extra updates as they unfold. I would love that. Start with the start screen and every couple of weeks a new feature. maybe even have weekly votes (kind of like what they have going on now) for the next feature.
I'm on to something here people.
Is this a sloooooow rollout or what?
Yeah...
TabGuy said:
Is this a sloooooow rollout or what?
Click to expand...
Click to collapse
I am in Moscow, Russia, still no update.... I tried like 20 times to reset but nothing... This is getting frustrating!
same for me France
Any french did get it ?
Same in Germany (Erfurt)
Still no update to lollipop.
houdini1er said:
Any french did get it ?
Click to expand...
Click to collapse
Troyes, France, nothing...
Nothing in The Netherlands either.
Is there any easy way to push OTA zip without rooting or pogo cabling?. I mean via adb bluetooth, or similar...
nothing here usa
I'm thinking it's nothing to do with country now and possibly serial numbers instead.
nothing also here in Colombia, we're supposed to get it tomorrow 15/12 as someone said it would reach 100% of moto 360 that day. who knows if that's even true
http://phandroid.com/2014/12/14/motorola-moto-360-android-wear-lollipop-lwx48p-december-15/
If it's like their stock we can expect to wait few more weeks.
Begining of september you could read every where moto 360 is out, but no one had it in stock.... Not very serious compagny motorala
still nothing in Moscow....Russia
houdini1er said:
http://phandroid.com/2014/12/14/motorola-moto-360-android-wear-lollipop-lwx48p-december-15/
If it's like their stock we can expect to wait few more weeks.
Begining of september you could read every where moto 360 is out, but no one had it in stock.... Not very serious compagny motorala
Click to expand...
Click to collapse
Hound,
I believe that the rollout of Android Wear is by Google, not Motorola.
It's not like for the smartphone ? Well not very Lucky then...
Still nothing
I STILL have not gotten the lollipop update. This is annoying as fu**. I have tried resetting my watch multiple times and even clean flashed lollipop 5.0.1 from 5.0 to see if that made a difference but still no go. I then reverted back to stock (LG G3 T-mo D851) and reset my watch and wear app and looked for an update but still no luck. I then saw something strange. In the about page on my watch, I clicked on 4.4W.2 under "software version" it opened a page that says:
Android Wear
1.0.1.1526154
Google Play Services
6.1.74 (1511752-534)
On my phone the wear app is on version 1.0.5.1630507 and Google Play Services is version 6.5.99.
This is likely why my watch will not update, it doesnt think that my phone has the latest versions of each which is required to update my watch. I wonder if this is the method that google uses to control the rollout of the newest versions of wear... It would be a quick and dirty way to handle it but is not beyond the realm of possibilities..
Is anyone else having this issue and/or know a work around?
Thanks
there's another thread on this but for those still waiting, there are two builds floating around. some of us have received both builds so that could be the reason for the delay.
Do you need to be on a specific rom or something?
im using moto 360 (i bought in USA) and im using in Mexico and no update i get 5.01 in my gear live tho
I got the upgrade today in SoCal about 1pm.
Got it today in Kabul Afhganistan