N97 Firmware update went wrong...

This happened to mine yesterday.

You have to do a hard reset to fix it.

Back up all your contacts and whatever else before you do this though.

Are Nokia (the company) falling to pieces? How can a firmware update that has been delayed for a month - for 'testing' - end up removing communication capabilities and require a hard reset. 😮

What exactly did they spend a month doing... playing with the N900?

Nokia are losing the plot, they really are.

Just how dumb are they?

Thank you to everyone on here for warning me about losing settings, i cancelled the OTA download, got home, did a back up of settings, did update and restored settings, that brought all my wifi and internet settings back

Judging from this performance, Nokia deserve to be battered by its competitors, they are pathetic and short-sighted

Which FW update is this, I thought the new v20 / v2.0 wasn't out til next month some time?

Tried my SW Updater and told me all my software was up to date ( and I have sim free handset, so not tied to any network )

nottmbantam wrote:Which FW update is this, I thought the new v20 / v2.0 wasn't out til next month some time?

Tried my SW Updater and told me all my software was up to date ( and I have sim free handset, so not tied to any network )

We are talking about - rather unbelievably - v12!

Nokia have finally got around to releasing it for everyone, except it seems to remove all comms functionality for some people until they do a hard reset.

yeah had the same so i had to hard reset, thanks nokia wait all this time and it buggers up my phone

celios wrote:We are talking about - rather unbelievably - v12!

Nokia have finally got around to releasing it for everyone, except it seems to remove all comms functionality for some people until they do a hard reset.

Oh I see, apologies :redface:

The two upgrades I've done so far, v10 to v11 then v11 to v12, have both gone quite smoothly . Cue the next one to totally bugger up the phone....

nottmbantam wrote:Oh I see, apologies :redface:

The two upgrades I've done so far, v10 to v11 then v11 to v12, have both gone quite smoothly . Cue the next one to totally bugger up the phone....

This upgrade was done by OTA (Over The Air), an option as well nowadays but never to be used again by me !!:icon13:

ok, I'll have to go for the Hard Reset then, wonder what problems that will bring me....

br_elwood wrote:ok, I'll have to go for the Hard Reset then, wonder what problems that will bring me....

Hi

A hard reset will take your device back to factory defaults - i.e - the device state when you recieved it - you will have to reinstall or apps chage personal settings etc - did you back up first? other forum members on other forums are suggesting that a restore from back up will restore connection problems - certainly on the vodafone forum there are post for manually reseting access pionts - other providors may also have same.

Hope this helps

Boothy

Yes the two upgrades I've done have bothe been via the PC and not OTA, going on this thread is perhaps to avoid. Will do the next upgrade via PC Suite.

nottmbantam wrote:Yes the two upgrades I've done have bothe been via the PC and not OTA, going on this thread is perhaps to avoid. Will do the next upgrade via PC Suite.

Hi

From reading post on this and other forums the problems are not form transport method but just seemed to be a bad firmware upload - thats probably why nokia have pulled it.

Boothy

boothy wrote:Hi

From reading post on this and other forums the problems are not form transport method but just seemed to be a bad firmware upload - thats probably why nokia have pulled it.

Boothy

I'm inclined to agree with you boothy.

The first batch of v12 updates for generic phones that was released about 4 weeks ago seemed to go, more or less, to plan.

It only appears to be the next tier of v12 firmware updates released yesterday that caused problems. I wonder what firmware version 12 they were?

My firmware update, v12.0.024 for product code 0570817: RM-505_EMEA_EURO_QW1 Black went OK. 😊

HI Ian

I think yesterdays was v12.0.026
I was lucky - I was too late to update - there is a lot a chatter on voadfone forum but no confirmation \ official comment on if it was pulled for connection settings problem or when it will be re released.

It seems that most problems are easily resolved if device is backed up first - still not clever though with such a late firmware release - you would of thought they would have had plenty of time for testing prior to release.I bet this little episode will push V20 even further back.

Boothy

It was a Vodafone branded/authorised firmware update it would seem.

My understanding of operator based updates is that Nokia release their generic updates to the various operators who then "muck" them about, adding their own branding or removing certain applications and adding others of their own, and in due course return them to Nokia for use in updating on NSU or FOTA.

It would appear that this update was too "mucked" about with.

Hopefully, for those who are waiting, it shouldn't take long to sort out. It makes me think that operator firmware may take a little longer to be released in future as I'm sure Nokia will not want a repeat of this fiasco.

br_elwood wrote:ok, I'll have to go for the Hard Reset then, wonder what problems that will bring me....

Update : When I got the phone and after I made the first changes I made a Full Backup with the OVI Suite. I thought of that just now and looked at the restore options.
I found that one could also only restore "settings". I did this, and suprisingly I got everything back.
Looks "ok" now, but don't now if all works again....

The firmware still tells me I have V12.0.026.....

So it sounds like that was the fault of Vodafone's not Nokia. Which figures since V12 has been out in the wild and working (more or less) for about a month.

Just one more reason to debrand and change that product code I guess.

celios wrote:So it sounds like that was the fault of Vodafone's not Nokia. Which figures since V12 has been out in the wild and working (more or less) for about a month.

Just one more reason to debrand and change that product code I guess.

That would be my conclusion also.

As for debranding... Amen to that. 😊

I had the exact same problems after updating this morning.
Unfortunately didn't have a backup, and had to do a hard reset!!😡

Anyway, after playing with the phone for a an hour, it seems to be as it should but running V12 now.