N78 (O2 brand) Firmware Update

I need to update the firmware on my N78 which at present claims to have version 11.043. NSU informs me that this is the latest version and therefore does not offer me the option to update. O2 tell me that the latest version authorised by them is 20.149. I have just spoken to a gentleman at Nokia Care Centre who tells me that although my phone states it has 11.043, this is just a glitch and it does in fact have 20.149. THIS SOUNDS LIKE BS. Can anyone confirm this information. If it is indeed false, how can I update?

Please read this informative article written by one of our senior users Grschinon, which will explain the non-availability of firmware updates for your N78. I have an unbranded N78 and am running v30.011 myself: http://linux.sgms-centre.com/nokiafaq/branded-phones/
Also read the articles on this blog for further clarification on firmware updates: http://techyoddsandends.blogspot.com
For your information also, 30.014 is basically the same as 30.011, except it is only available for a few select product codes (namely Persia, some of Africa).
If you found this or someone's comments helpful or like what that person has to say, please give some Kudos to their post!

Similar Messages

N78 problems after firmware update

I have recently updated my N78 (RM235) firmware to 13.052.231.6.
Before the update the internal GPS worked very well, finding satellites quickly and holding a strong lock. After the update the GPS is very poor, taking a long time to find satellites and loosing signal very easily.
Can anyone help with this problem or tell me how to re-install the previous firmware?

Has everything else stayed the same and only the GPS antenna reception got worse?
If that is the case you are right, but maybe the update made other improvements and for some reason one of them worsened the GPS antenna...just guessing...
By clicking the "Kudos!" or the "Solution?" button on the right you can say "Thank You" and you´ll show the author and others that the post is useful.
The day we stop improving is the day we stop being good.

Nokia N78 When Newer Firmware Update

Hi!
I have a Nokia N78 with v12.046, the last firmware, and this FW have a much bugs. When Nokia release a new firmware for Nokia N78 to solve the much bugs that this version of FW have ?

the new soft ware have huge number of bugs
1- the phne hange at any time and many time in each situation ( play game , open clip, WLAN browsing , and pla pla pal)
2-the power safer just only when i make it 30 sec or 1 min or any time , its start to work after 5 secs only
3- the videwo dont have send option from the gallary , you showld go to photo = all = and after that send the clip
the phone after i turn off need to make turn one 3 tmes or more and may be hanger
and many other bugs
its the most mad phone software
and i reinsttal the soft ware and phormat the memory and every thing still like that
weeeeeeee neeeeeeeeeeeeeeeeed newwwwwwwww softtttttttt wareeeeeeee nokiaaaaaaaaaaaaa

N78 Firmware update to 30.011 fails ("nmwcdnsu.sys...

hi together,
i have still a big problem with updating to the latest firmware from version 21.002 to version 30.011.
while update process is starting a windows pops up and a cd is requested (-> Nokia USB Flashing installation Disk) containing "nmwcdnsu.sys" file, which i do not have!!!
-> please find attachment.
and then everytime update fails, i think due to this missing sys-file.
all this is done with the nokia software update tool and usb data cable connected.
this is the first time for me having such problems with firmware-updates.
and by the way, a firmware-update is not shown or provided when i use the phone asking directly for the latest firmware from the device-manager-info-overview (is not supposed to be available, tells the display me after connected to the nokia server...).
thanks a lot for hints and tips.
regards from germany
sascha
Solved!
Go to Solution.
Attachments:
0728.jpg ‏30 KB

hi guys,
i got the meaning of nsu a few seconds later when i had already posted the reply...
the issue is now solved. but the nsu needs some fixes!
i will inform the nokia carecenter in germany.
i reinstalled the very nice and faulty tool "nsu" (with win xp-restart/reboot) and gave him several times manually the destination-folder from these/some requested specific *.sys-files, which the tool obviously does not know the installation-folder (Connectivity Cable Driver folder). and then it was successful.
thank you very much guys.
greets
sascha

Time Capsule (brand new) needed Firmware update, now issues still

I have just updated my firmware on the Time Capsule, (I did figure out why I was getting an earlier error on my Time Capsule when an error popped up that "Time Machine couldn't complete the backup to my TIme Capsule because the "backup image was already in use". I finally saw the number or exclamation mark (I forget) and it stated it needed a firmware update (wish it would download them automatically). After I did that though, I am backing up my iMac.
I have to take my iMac to Apple today in Tampa and drop it off to replace the HD per the replacement program of a recall so I have to make sure the backup is complete. I also want to make sure my iPHone is backed up and so I was told when I bought Time Capsule that it would also wirelessly sync up all my Apple wireless devices.
I was told to use Airport Utility, but that doesn't seem to work at ALL now and I'm not sure why. As of Feb. 7th, that was updated and it seems to have caused problems for many.
I am in v. 1.2 and just deleted it and added it back in.
How can the Time Capsule allow my iPhone to access it through Airport Utility? Was there a setting I am missing?
HELP with the Time Capsule backup, the iPhone (and then my daughter's iPod, my iPad and that's about it) backing up wirelessly through Airport Utility.

Your idevices do not backup directly to the TC.. nor does the Airport Utility do anything but setup the TC.
Time Machine is the backup for the Mac.
The devices like iphone are backed up to itunes or cloud..
The itunes is then backed up by TM to the TC.. so it is indirect.
See apple doco on back of iphone for instance. http://support.apple.com/kb/ht1766
Let me also suggest you do a disk image of the mac. You will find this is much easier to recover your working mac from.. in fact get a USB drive is even better and download superduper.. you can do free disk images from it, but they can also be done from disk utility. Make a bootable USB drive which is an image of your existing internal drive. That can be easily restored to the Mac when you get it back.

Australian N85 users wanting a Firmware update to ...

Hi there,
As an Australian N85 user on a Virgin Mobile branded handset, I thought I'd share my recent experiences. Both phones were purchased from Telechoice under a Virgin Mobile contract.
I received a Virgin branded N85 (product code 0575031)
My wife received an Optus branded N85 (product code 0576341)
The Optus branded N85 had the dreaded SMS contact names appearing as numbers, and the only fix at the time (about 5 months ago) was to replace the Optus firmware with Generic firmware. As many users know, depending on the Nokia Care Centre, this isn't as easy as it sounds - see this link for details:
/discussions/board/message?board.id=smartphones&message.id=126312#M126312
Anyway, since my wifes phone was updated with Generic firmware, she received V11 & V20 updates within weeks of their release. My handset, however, took an extra 8 weeks for V11 to be released, and as of today still has not had the V20 update released (I just checked at http://europe.nokia.com/get-support-and-software/download-software/device-software-update/can-i-upda...).
I spent the past 4 weeks with Virgin Customer Support trying to get a date of release out of them, and all I would get is it's in Beta test, and would be released soon. I explained that generic handset had received the V20 release already, but it fell on deaf ears. I finally got fed up with the support staff, and rang the Australian Telecommunications Ombudsman and filed a complaint. I cited that Virgin were withholding product updates that rectify some of the handsets faults, and the gentlemen that I spoke to gave me a reference number and a Customer Relations phone number.
I spent another week getting the same **bleep** out of Customer Relations, until I was finally put in to contact with a Supervisor. He advised that the Virgin branded handset would no longer get any updates, and that I'd been given inaccurate information.I asked him if he thought that it was fair that product updates that fix handset problems be withheld from customers, and he said that he did not think it was right but he was powerless to do anything. So he suggested that I go to a Nokia Care Centre and get the Generic firmware installed, as the handsets weren't locked to Virgin. He also sent me a letter in the event that the Nokia Care Centre wouldn't oblige, stating that Virgin recommended that the update be applied and that all warranties would remain in place if the handset were to be updated.
So I went to the Care Centre, explained the issue to them, and they were happy to update the handset to the Generic firmware (they didn't even want to see the letter from Virgin). The only thing is that they installed the Generic V11 firmware, but I was able to immediately update to the V20 firmware OTA (or via NSU if I wanted to).
So, for any Virgin/Optus customers waiting for V20 (and you know that V30 for the N85 has just been released...), I'd advise that you don't waste too much more time waiting, as it may never actually get pushed to your product code. Switch over to Generic legitimately via a Nokia Care Centre, and enjoy timely firmware updates (well, as timely as Nokia releases them, at least you don't have to wait for a Carrier to approve it!!!).
Cheers,
travla
If you found this post helpful, please click on the green "Kudos!" star. Cheers!

operators have always branded their phones Scanorama. its just that some handsets escape the radar and start to brand their handsets. we were lucky here in Australia that they didn't decide to brand the N78, though i also can see that it wasn't promoted that heavily either, hence only Virgin, Optus and Vodafone got the handsets, and not as many operators as i would have thought.
to buy generic handsets, that's a bit tough as i'm not sure if Australia has an online Nokia Store. but i guess buying here would be a matter of say going to a Vodafone shop for example, and checking that the phone doesn't come with Vodafone packaging, check a demonstration model of the handset itself to see it doesn't have custom firmware/Vodafone wallpapers/junk all over it. most cases it is pretty easy to tell if it is branded, since it does have that junk all over it, and on the startup/shutdown screens. a lot of the people count out the eBay method of buying phones, but i actually bought my N78 off eBay. when buying, you just have to be careful that it is a genuine handset, has the appropriate receipts (mine had a receipt from the Vodafone store)/genunine IMEI as mine did. with a little vigilance, you can easily identify the genuine handsets and get yourself a good deal. as with mine, i ended up getting mine for half the RRP Vodafone and Optus were selling the N78 for
please throw some kudos our way, it would mean a lot to us
If you found this or someone's comments helpful or like what that person has to say, please give some Kudos to their post!

WAP4410N wireless traffic locks up even when running latest firmware update

I maintain multiple buildings, and each building has anywhere between 1 and 4 Cisco/Linksys WAP4410N access points. The problem is that at random intervals, the access points just stop sending and receiving wireless traffic. Every day or two, I have to log into every single access point (either via HTTPS or SSH) and reboot them in order for them to start working again.
In short, here are the config details:
They are all version 2 hardware (either WAP4410N-A V02 or WAP4410N-E V02).
They are running IPv4 (IPv6 is disabled) and get static IP addresses via DHCP.
When there are WAPs with overlapping signals, each WAP is on a different non-overlapping channel (1, 6, or 11).
Each WAP has two SSIDs (with spaces in their names). One is secured with WPA2. The other is unsecured.
There are two VLANs on the Ethernet interface. Each of the two SSIDs are assigned to a separate VLAN.
There is a DHCP server on the network, so the WAPs do not actually assign IP addresses to clients.
All of the WAPs are running on PoE switches. However, some are gigabit and some are 10/100 switches. Brands vary (Dell and Linksys) and models vary.
Cisco finally recognized this issue as:
CSCtx62203—In certain environments and traffic model, the WAP4410N may lockup after some undetermined time. Workaround: Reboot the device.
As such, the workaround didn’t really offer anything new. Rebooting every WAP ends up being a very time consuming process. It’s awful. And since you have no control over when this issue surfaces and can’t put any safeguards in place, I get calls about it at various points of the day almost every day.
Supposedly the most recent firmware update (2.0.6.1) claimed to fix the issue, but it only seemed to make it worse. So now instead of a WAP locking up every day or two, it locks up anywhere between every 15 minutes to 4 hours when in use.
The firmware was updated and the following issue was fixed in firmware version 2.0.6.1: CSCtx62203—In certain environments and traffic model, the WAP4410N may lockup after some undetermined time. (A protection mechanism was added to guard against sporadic problems with client association that could occur after six to 24 hours.)
As for troubleshooting, there are no error packets. On access points running firmware 2.0.6.1, these messages appear:
Feb 7 13:42:27 Syslogd start up
Feb 7 13:51:59 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 13:52:01 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 13:52:05 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 14:47:01 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 14:47:02 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 14:47:05 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 15:22:53 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 15:22:56 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 16:15:19 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 16:15:33 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 12:27:25 Syslogd start up
Feb 7 14:06:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 14:06:23 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 14:44:28 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 14:44:31 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 15:09:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 15:09:24 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 15:42:23 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 15:42:25 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 16:52:18 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 16:52:24 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 16:53:05 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 17:20:05 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 17:20:08 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 17:23:34 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 17:23:39 syslog: Found beacon stuck, down and up the VAP interface.
Feb 7 21:21:28 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 7 21:21:30 syslog: Found beacon stuck, down and up the VAP interface.
Feb 8 09:55:23 kernel: ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)
Feb 8 09:55:29 syslog: Found beacon stuck, down and up the VAP interface.
These log messages appear on both WAP4410N-A V02 and WAP4410N-E V02 devices.
I noticed that when the “beacon stuck” message appears, wireless traffic locked up 10-15 minutes prior to the message’s appearance in the log, and the SSID drops for 4-6 minutes after the message appears.
Is there anything that can be done to address the issue?

1) LAN port speed doesn't appear to have any effect
2) Forcing a connection type doesn't seem to have any effect. This is also rather impractical.
3) I don't have that option (though there is a TKIP/AES mixed option). Either way, I'd rather not have to resort to using a weaker encryption method.
4) No effect.
I did manage to find some information about the error message (older versions of firmware didn't even offer that clue).
http://www.dd-wrt.com/wiki/index.php/Advanced_wireless_settings#Beacon_Interval
I ended up increasing the beacon interval from 100ms to 500ms under Wireless > Advanced Settings.
The wifi analyzer app on android seems to keep dropping the SSID when the beacon interval is set that high, so I might have to adjust it to find a good balance.
However, while it was set to 500ms, none of the access points went down for two days.
[edit]: I reduced the beacon interval incrementally down to 300ms. It started locking up at 250ms.

MacBook Pro Won't Boot after Firmware Update

So I just upgraded to a MacBook Pro which came in the mail yesterday. I removed the Apple-installed HD and swapped it out for a bigger, faster HD. I installed OS X from scratch, imported everything from my Time Machine backup during the Setup Assistant, and then started installing updates. Everything was running swimmingly until the last updates.
What happened is when I rebooted my MacBook Pro and logged in after a series of updates, I got presented with both a Bluetooth update and a Firmware update at the same time. Both required a restart so I thought I would kill two birds with one stone. I installed the Bluetooth update, and then when it asked to reset I installed the Firmware update instead. However, the firmware update didn't behave as advertised because instead of shutting the MacBook Pro completely down, it restarted and then started installing the firmware update.
Ever since the firmware update (which I think installed correctly but don't know how to verify), I cannot boot my MacBook Pro. Using the OS X install DVD I can view my firmware version using System Profiler, and the number it is reporting is MBP53.00A.B03.
I have tried booting in verbose mode to try and get a feel for the problem, and it eventually hangs on an infinite loop saying something about not being able to find something on disk0s2.
I also thought I would fix the problem by doing an Archive and Install, but it quit at the very beginning of installing with the error "unknown error".
Also I thought I would format the disk with Disk Utility and then try installing again, but Disk Utility reports that it in unable to unmount the volume.
Any help you can provide would be greatly appreciated. Thanks!
-- Update --
Remember how I'm unable to unmount the drive? I force unmounted it and then used Disk Utility to repair the volume, but still no luck.
I think the key to the problem is this new HD I put in runs at 3 Gbps. I think I read somewhere that the new MacBook Pro's don't support that.
I think next I should try swapping out the new HD in my MacBook Pro with the one it originally came with. What do you think?

I, too, have a brand new MBP 15" that I put an Intel X25 in. At the 1.5 (Prior to Firmware Update) setting, it worked fine. I rant the Firmware Update, all looked fine, but the drive is no longer able to be seen.
Flash the PRAM, per other suggestions to no avail. Boot off of the DVD and disk utility nor Profiler sees the drive.
Replace the drive with the stock that came with the MBP (which I had never even used) and it works.
Put the Intel X25 into a Windows machine and it works fine. Reformatted it (in windows) and put it back into my MBP. Still not able to see it (from the Disk utility after booting off the DVD).
Intel's firmware for the drive says its up-to-date (new drive) and if I attempt to "re-run" the Mac Firmware Update, it says that the machine is already up-to-date.
Seems odd that it worked before an now it doesn't. Also seems odd that the X25 works in other machines. And that my MBP works just fine with the stock Hitachi 7200 320GB drive.
Ideas? Intel says to call Apple Support. Not sure what I can say to them.

10.6.8 Macbook Pro firmware update problem

I installed a couple of updates for my MBP 10.6.8. One was Safari, the other was brand new, released within the last week, I think it was a firmware update, and now the machine will not boot into OSX. I have a Bootcamp Windows 7 partition that starts fine. But if I let it boot, or select the Mac partition, it shows the apple logo, then a little progress bar below it that gets to maybe 5-10%, then starts over, then the computer powers down.
I have tried clearing the flash by holding option+command+P+S. Didnt work.
Is there a way I can boot to a command prompt and clear this update out or something? Or anyway to fix this myself? From the Windows partition maybe?

So...fixed my issue and it was not related to the updates, it was just coincidence.
What I finally did was take a video of the startup screen and was able to see that what was happening was fsck was failing, and then the system just halted. This info presumably makes it to dmesg, but not to system.log (huge oversight IMO). So its not easily discerned.
Once I figured that out I googled around and this guy's page helped me fix the problem:
http://blog.jbheren.com/post/2011/02/09/repair-hfs-volume-on-osx
Specifically I had to boot into single user (command+S at the startup sound)
and issue:
fsck_hfs -ypr /dev/rdisk0s2
Then I did
reboot
and here we are

TS3499 2007MBP, L-shaped adapter, and a firmware update that didn't work.

My replacement L-shaped adapter worked for a day on my 2007 MacBook Pro, then stopped abruptly. I've tried the SMC reset as well as the firmware update. When I tried the latter, I received an alert that my computer does not need the update.
Please help me! This is driving me crazy. The only answer I can get online is to install the firmware update, but it refuses to install. I'm assuming that means I already have the update. What's the next step for someone in my situation?
I appreciate any help you can give me.

Were you ever able to get a resolution to this? I have an 2007 MBP 17" and bought a new adapter that stopped working after 2 weeks. I bought a brand new one today, it charged the battery to about 90% and then went dead. Now the LEDs won't turn on and it will not charge or power the computer. I think the issue is with the laptop but have no idea what it could be. Has anyone heard of this before or have any ideas on how to troubleshoot/fix this? I've checked the SMC firmware to make sure it is up to date, i've reset the SMC. i've left the adapters unplugged for a few hours....nothing has worked. Please help...

All valid disks are read-only after installing UJ-835 firmware update

Hello everyone,
I've just installed the firmware update for my SuperDrive. When I insert a DVD that is blank and writeable, my PowerBook does not ask me to prepare for a Burn as it used to.
When viewing in Disk Utility, the DVD is marked as non-writeable. In an iMac, the Finder will ask if I want to prepare for a burn when I insert the same blank DVD.
I tried other disks of other brands, yet the same problem. The disks are fine on the other Macintosh. The disks should be blank.
What can I do? How do I back out the firmware update?
Thanks in advance!!
Lyndsey
PowerBook G4 12" Mac OS X (10.4.6)

Originally, I was trying to burn with Maxell DVD+R disc. I have since tried Verbatim DVD-R and Kodak DVD-R. All DVDs do not appear in the finder, I cannot use my SuperDrive to back up to DVD! When I insert the DVD, the SuperDrive spins up, then down and then nothing happens.
I am able to back up limited bits onto CDs, they seem to work ok.
Anyone have any advice? How do I pull the firmware update out? Will a System Restore do the trick?
PowerBook G4 12" Mac OS X (10.4.6)

N96 Firmware update

I am aware that a new firmware has been released by Nokia for the N96. However i am not able to get hold of it yet. I have a UK Vodafone phone & contract.
1.Can you advise how i can install this new firmware?
2. Will it address the various problems such as:
a) software crashes and freezing,
b) phone reboots itself for no reason,
c) GPS location is not always possible, but when i use google maps on the phone my location is found
d) Music player will cause the phone to shutdown if you use it for more than 60minutes
e) battery feels warm when several applications are running or you are doing anything continuously for more than 15 minutes
3) is it possible i can download the firmware via your website and install it myself?
4) will i need to unlock the phone to get the update now?
I have had the N95, N95 8GB and now N96 phones. Sadly they all failed to live up to the hype of matching the power of the IPhone, which i am reluctant to buy. If i cant get hold of the firmware and i still have the software glitches then i may be forced to become another Apple IPhone fan.
Like most people here we just want a good phone that can do all that you claim it can do.

hi there Smurph, read this informative article written by one of our senior users Grischnon: http://linux.sgms-centre.com/nokiafaq/branded-phones/ i'm afraid what Post007 was trying to say always comes out rather muddled, so i will explain it in short for you.
Nokia provides the firmware to Vodafone and other operators usually before the generic firmware (or what others call de-branded; unbranded) is released via NSU or FOTA by Nokia. it is then up to Vodafone to modify the firmware to their tastes, or if they don't wish to then they won't. if the firmware is modified by Vodafone it becomes branded firmware and is given back to Nokia who will then distribute it through NSU or FOTA for the specific product codes for that firmware (i.e. product codes will be for the Vodafone variants of the N96). this is why Vodafone tell you to go to the Nokia website to update your phone, no operators actually handle the update processes themselves. another reason they tell you this is to divert the blame to Nokia, and Vodafone not accept resposibility for the laziness/poor attitude taken by their programmers to put out updated firmware for their phones. or excuses for why they firmware is so crippling. so in essence, they're not really being truthful, yes. it's not really Nokia's fault in this case, its often Vodafone's.
i'm unsure if you can get out of your contract as Vodafone probably has all the jargon to cover themselves for their inadequacies. by preying on the customers lack of knowledge, they suck more unsuspecting customers in to make more money. this should answer your question pretty well.
please throw some kudos our way, it would mean a lot to us
If you found this or someone's comments helpful or like what that person has to say, please give some Kudos to their post!

Timescale for firmware updates Lumia 520 ?

Can anyone explain why there is such a varience in which the same update gets released either from a phone supplier or Nokia.
For example I am with O2 in the UK. I asked about the Amber upgrade and the replies varied from "what is that I've never heard of it" to " We are not imformed of release dates so do not know" to a straight "no idea". to " keep checking in settings-phone-update"
AT & T have been selling the Lumia 520 for some time and their version has Windows Phone 8 build 10327 (GDR2) and Nokia’s Amber firmware update already on board.
I can not see Amber for example being different in USA and UK or Swaziland for the same phone.
So why such a delay
A very impatient
Keith
Solved!
Go to Solution.

There is a difference between a sim,free (factory unlocked/unbranded) device and a carrier released version.
your challenge with updates when you have a carrier branded device is that the carrier usually has very few updates to devices. And, their firmware versions are different, which include bloatware.
it is either software they are paid to put in devices, or their own renditions of billing, WiFi calling, mapping, etc stuff. So, before they do any updates of firmware and push it out, they have to do their own version of QC whereas factory unlocked devices get updates when ever the phone manufacturer releases them, which is usually more often.
even,if you get your device unlocked, it will still require that the carrier push the update. So the care reps are usually going to very uninformed unless they truly are involved in the tech side and have genuine interest to learn more. From a corporate perspective, they usually are scripted and clueless, which for the companies sake helps them not to create anymore confusion with the customer base then already is there.
as for the varients of,different countries, good to think about the regulations each country has, as well as some of the functionality of the device. Some countries don't have 3 or 4g service, or MMS is different, or there are frequency differences or regulations on what can be done. This goes far more deeper than just having the language available.
hope that helps

N80 firmware update question...

I think I have read this in other posts but am unsure how valid it is...
I have several N80 handsets 2 of which were Vodafone UK but have subsequently been unlocked by Vodafone.
The firmware versions are both v4.0623.0.41
26/02/06
RM- 92
NOKIA N80 (42.03)
IF I take these to have their firmware updates done, does that then mean that they will revert back to being locked to the Vodafone network or does it stand that once a handset is unlock/network free that it remains as such?
JG
If it isn't fun you are doing it wrong
N95, N80, N73, P990, P910, P900, 6230i, K750i, 8210

hi jg01
There are two issues here:
Firstly once unlocked a BB5 remains unlocked.
Secondly because they have a "Vodaphone" product code (label under battery) if you use Nokia Software Updater it will check which is the latest Vodaphone release software for your phone (not the latest generic software)
Nokia Service Centres used to be happy to upgrade with latest generic (non-operator branded) software, but I am not sure whether they have tightened up procedures now and insist on like for like software. I am sure somebody else will give you the definitive answer!
Happy to have helped forum in a small way with a Support Ratio = 37.0

E61 Firmware update

I've a Nokia E61 product code 0537308 with firmware version 2.**** and I've noticed that a new version (3.0633.09.04) is available. So I've installed the Nokia updater software, made a complete backup of the phone and started to update the firmware of the phone.
Everything went fine until a certian moment the Nokia updater software start complaining that the SIM card was not inserted and give a update failure requesting to insert the SIM card while the SIM card is still in the phone.
Can this be caused by the fact that the SIM 'PIN code request' is on so everytime the phone is switched on the PIN code is requested. Do I have to put this off when a firmware update is performed?
Can someone help me please?
Thanks

Thanks for the responses
As predicted O2 were of no help at all (bear in mind O2 is just a brand for carphonewarehouse)
I dont understand how nokia can provide a firmware update using the Nokia Software Udatater tool and then have it restricted so O2 users can't download the latest. What makes O2 so special (or not in this case) the phones are the same are they not?
Juding by the other forum topics on the same subject I am not the only one suffering the same lack of support.
I went back to my Sony Ericsson in October due to the lack of support....maybe Nokia should start to take ownership of this problem and put pressure on O2 rather than relying on users to do that job from them because O2 is not an easy company to get a repsonse from (although the operator did at least try), they pointed me at carphone warehouse who in turn pointed me to O2...... and so the cycle goes on.
Shame really as the phone as a unit is quite nice, however it's just a nice shiny brick on my desk at the moment ....
Do Nokia read these forums?

N78 (O2 brand) Firmware Update

Similar Messages

Maybe you are looking for