N95 8GB on latest firmware - any point in de-branding?

[wizzywas]

I am using o2 on a branded vodaphone n95 8gb which was unlocked before I brought it. Will the the FW update be certified by o2 or vodaphone before it is released. As currently I cannot update to v20. Which is unfortunate as my phone is geeting slower. I'll wait a couple of weeks as u guys says vodaphone take a couple to weeks to release a update for there branded phones

[Steve Zodiac]

Originally Posted by wizzywas

I am using o2 on a branded vodaphone n95 8gb which was unlocked before I brought it. Will the the FW update be certified by o2 or vodaphone before it is released. As currently I cannot update to v20. Which is unfortunate as my phone is geeting slower. I'll wait a couple of weeks as u guys says vodaphone take a couple to weeks to release a update for there branded phones

Because the 'product code' on your phone is for Vodafone branding, you'll just have to wait for the Vodafone version of the latest firmware to be released; it won't have anything to do with O2.

[Gaz]

I shouldn't worry ,judging by past experiences it will not take long.

[wizzywas]

yep i'll just wait but this Vodaphone branding is annoying, i'm not sure whether to debrand it or not.

[Gaz]

Aye but personally I have found that some of the Voda applications are very good and would rather not lose them .
Not to mention losing my warranty as although I can repair my own phone at work there is always the chance that something will happen that requires higher level repair in which case I'd be stuck

[phil5743]

I'm getting confused now - there seem to be so many posts in other threads saying what a difference debranding has made - has Vodafone now caught up and started providing updates (albeit a few weeks later)? If so are the benefits of debranding not as great as they were a few months ago?

[Steve Zodiac]

Well, I got impatient a couple of days ago and decided to de-brand from Vodafone.

The product code changing with Nemisis was straight-forward enough - once I reverted back to an older version of the Nokia software which was on my laptop (The latest version of Nokia software wouldn't allow Nemesis to read the N95's product code etc.)

Following the product code change I then went on to the firmware update (I was then back on the PC using the latest version of Nokia software). It showed that the N95 was on 15... and the latest version was 20... I then went on to update the phone.

It got to what looked like around 75% of the way through and I then got a message saying something like "Disconnect the power and remove the battery, then reconnect"... you probably know, or can probably guess the rest.

The 'bricked' N95 is now on it's way back to Nokia for repair.

[phil5743]

If the problem occurred during the actual firmware update (and seeing that the first stage was a success), then wouldn't the same thing have happed updating an unbranded phone also or has the updater crashed because of the code change?

[Steve Zodiac]

Originally Posted by phil5743

If the problem occurred during the actual firmware update (and seeing that the first stage was a success), then wouldn't the same thing have happed updating an unbranded phone also or has the updater crashed because of the code change?

The prevailing feeling I have is that it was just bad luck... but, the thought did cross my mind, that perhaps the latest version of the Nokia Software Updater had something to do with it, recognising a product code change and it went into 'auto-brick' mode! Who knows?

It'll be interesting to see which firmware is on the phone when it gets back: The Euro 1, 20... firmware - which is the product code I changed the the phone to, or Vodafone 15... firmware, which is what's on the label under the battery (and what I wrote on the Nokia return paperwork). I expect it'll be the Vodafone firmware.

(...Just an afterthought, I had previously re-installed the Vodafone 15... firmware using the latest NSU after the voice recognition system started playing up - that went without a problem.)

[phil5743]

Originally Posted by Steve Zodiac

The prevailing feeling I have is that it was just bad luck... but, the thought did cross my mind, that perhaps the latest version of the Nokia Software Updater had something to do with it, recognising a product code change and it went into 'auto-brick' mode! Who knows?

It'll be interesting to see which firmware is on the phone when it gets back: The Euro 1, 20... firmware - which is the product code I changed the the phone to, or Vodafone 15... firmware, which is what's on the label under the battery (and what I wrote on the Nokia return paperwork). I expect it'll be the Vodafone firmware.

What did you tell them caused the bricking - did you say you were updating the firmware?