Nokia 6500c Firmware Issue

Just flashed to latest firmware and what a shock ive got a problem here is what happend - its a new phone all working ok with all default codes i upgraded and now in the call duration to reset the timers will not accept the default code as it did before all other security codes are off at the moment but i would like to use them but if changing the codes requires me to input the default one then im reluctent its going to work and lock me out altogether all i can say is what a pile of po? this firmware must be the only saving grace is my contacts are still intact anybody know what to do except take it to a center which is a joke cos on this site mine is the o2 shop and they have said they cant fix it im going round in circles please help?

I have been on the phone to nokia today and told them my problem as above on my 6500c and slide guess what the first thing he said was YES there is a problem with the firmware on this model of phone ie DO NOT flash it if its new and working ok leave it well alone.
The out come is this for me the phones are only 3 months old and are covered by the warenty so he told me i will have to take it to one of there repair centers and have the phone flashed with software that the general public have not got access too and this will be done free of chage and will take a couple of hours to do depending on how busy the center is.
Ok so far so this is what ill do so i got the details eventually after finding out they had moved the center to another town and rang them no problem he said just drop by anytime and we will fix it?
hmm this sounds to easy so i will update you all later this week when ive been to the shop??
If you live in the s midlands/ n worcestershire area then here is the details of where to get your 6500 re-flased -
Please note i have flashed my phone twice to the latest version which is V4.84 and from v4.80 and when i had the phone new it was 3.6 so the latest 6500 version is v4.84 but it has bugs in it so DO NOT USE THIS UPGRADE it causes more problems then it fixs you have been warned.
I think when my contract is up i am going to change to something better hi hi.
I hope this will help some of you who are having issues with the 6500 and the phon DOES have default passwords to reset the counters its 12345 its in the **bleep** manual and confirmed from nokia so not sure where this idea that this phone does not have passwords on it - IT DOES thats why its broke?
Have fun dont get too wet and watch this space?
Message Edited by zipper19 on 28-May-2008 08:56 AM

Similar Messages

  • Nokia 6760s firmware issue

    Can somebody help? I tried to re-install the nokia 6760s firmware but unfortunately ran of battery charge midway. I now have a dead phone and would like help in flashing it. I tried taking the phone to Midcom in Kenya but they couldn't flash it. Is there a way I can ship it overseas or get  support from nokia. The RM make is MEA black

    Hi, jamhuri. Thanks for posting your concern and welcome to our forum. You may try using the Nokia Software Recovery Tool for you to recover the phone's software. Note that your files will be deleted, so make sure that there's a backup. 
    Let us know the outcome. 

  • Nokia 6500c (RM-265) Firmware version 9.48

    Trying to update my Nokia 6500c but got this error message.
    This happens after the Nokia Software Updater was upgraded to v1.4.98en.
    I think the NSU has bugs in it.
    Message Edited by gbabia on 14-Mar-2009 03:53 PM
    Nokia C7-00 V 024.001
    Nokia E52-1 V 081.003
    Nokia 6700 classic V 13.10
    Solved!
    Go to Solution.
    Attachments:
    N6500c Update error.jpg ‏46 KB

    Did a hard solution as follows:
    Settings > Rest.factory.sett. > Restore all
    A few minutes phone re-started and DELETED all personal information (including installed applications)
    Did the NSU and finally it was successful.
    Nokia 6500c
    V 09.48
    26-01-09
    RM-265
    (c) Nokia
    Variant: 00.00
    Virtual Variant:
    No virtual variant
    Language:
    V 09.48
    26-01-09
    RM-265
    (c)Nokia
    M1
    Nokia C7-00 V 024.001
    Nokia E52-1 V 081.003
    Nokia 6700 classic V 13.10

  • Nokia 5610 firmware update....................

    im having a little problem with my nokia 5610 firmware update.
    The problem is that after updating my phone with version 8.30 the slide animation feature of my phone is not working. On slide open\close the picture set in the theme is supposed to appear but nothing appears.
    Before the update this feature was working perfectly fine. i reported about this issue to nokia customer care also but they just advised me to wait for the next firmware i.e. v9.40 . As the new firmware released on my product code i again updated my phone's firmware and this time with version 9.40. Still it did not help me. The same problem persists . Please note here that nothing went wrong during the update . All other features of my phone are working perfectly fine .
    Can anyone please help me on this issue??????

    Hi there,
    The version 10.00 for the Nokia 5610 has been around since early July, so certainly it would be available for all countries in the APAC region.
    Just make sure the phone is fully charged and backed up and you're set to update.
    Cheers and Good Luck
    Message Edited by nj15 on 11-Oct-2009 03:26 PM

  • Error with "Sync calendar and tasks" - Nokia 6500c

    I'm having trouble with "Sync calendar and tasks" - all other sync is fine.
    It all worked OK with PC Suite beforehand. 
    I've auto upgraded to Ovi on last connection.
    Can anyone help?  
    Error message when trying to sync is:
    "Not enough space in device
    First remove some files from your device and then sync again.
    8393f01e"
    Phone status:
    Device memory - 910MB of 940MB fee 
    Phone version:
    Nokia 6500c
    V 09.48
    26-01-09
    RM-265 
    Ovi version:
    Nokia Ovi Suite 2.0.1.35
    Nokia PC Suite 7.1.40.1
    Nokia Music 1.3.20722.1
    PC Connectivity Solution 9.44.0.3
    Connectivity Cable Driver 7.1.22.0
    Nokia Ovi Suite Software Updater 2009.40.0.60128
    Maps Service API 3.0.35.0
    Nokia Platform 2.5.195
    Ovi Desktop Sync Engine 1.0.0.684
    Operating system:
    Microsoft Windows XP 32-bit Edition, Service Pack 3
    Language: English
    Detected internet browsers:
    - Microsoft Internet Explorer 6.0.2900.5512
    - Mozilla Firefox 3.5.5
    Detected Bluetooth stacks:
    - Microsoft (Version: 5.1.2600, Build: 5512)
    - Toshiba (Version v4.00.22(D))
    Thanks.
    Cheers,
    Jason. 

    Hi,
    Really **bleep** off with this issue in synchronizing , I move back to my old PC suite that worked fine .
    I expect our NOKIA provider to be back on their code and solve this issue.
    At least, one mail to me warning me of corrections with this issue and improved performances would not be considered by me as spam but as consideration to users .
    Sorry dear developpers but either your specs were uncomplete, at least performance criterias were undefined and you businees acceptance test were unproperly managed. I would not like to be the project manager in charge of ! Just before Christmas, providing such a release will make Santa Klaus quite unhappy top him .
    BR

  • What is new in Nokia 6300 firmware v07.00

    Hi I have just upgraded my Nokia 6300 to firmware v07.00. I can't notice any visible change with this new firmware. Can anyone put some light on what is new in Nokia 6300 firmware v07.00
    Hyp3rion

    After updating mine yesterday...da screen refreshes or so flickers every say 5 seconds...plz any help
    i have reinstalled it three times... ..still no solution
    Message Edited by prubyholl on 04-Dec-2008 07:20 PM

  • Beige G3 boot from **** problem; open firmware issues; bad motherboard?

    Dear all,
    I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
    To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
    All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
    Here are some of the things I've done.
    --repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
    --removed all add-on PCI cards.
    --removed additional VRAM
    --removed all memory cards and tried replacing one at a time.
    --disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
    --unplugged floppy drive
    --disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
    --regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
    --using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
    --regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
    --when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
    --even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
    --the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
    So I think it's a bad motherboard or ROM. Thoughts?
    Thanks.

    The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
    A few things I've learned along the way that hopefully may be useful:
    --remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
    --at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
    Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
    If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
    After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
    Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
    If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
    If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
    One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
    All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
    Regards to all,
    Graham

  • Happy on Leopard, hangs on sleep with Tiger: Firmware issue?

    I have an early 2005 G5 dual 2.0 that I bought new. It has 2.5GB of RAM and two drives: a 1TB and a just-recently-reinstalled original 160 GB drive.
    I've updated it through the years and recently it's been running Leopard 10.5.8 on the 1TB drive.
    I've just replaced it with a Mac Pro as my main machine, and wanted to set up the G5 to run Classic apps, so installed the original 160GB drive, wiped it clean with Drive Genius, and did an erase and install from my original 10.4 CD, followed by a bunch of Software Update runs to get it to 10.4.11.
    Trouble is, when booted in 10.4.11, every time it sleeps, the fans go into high gear and the system hangs, so I have to press the power button to shut it down.
    I cleaned off the disk and reinstalled.
    I zapped the PRAM/NVRAM.
    I booted in Open Firmware and did a reset.
    I disconnected the 10.5 disk.
    I ran Apple Hardware Test.
    I disconnected all cables and pressed the PMU/SMU reset button.
    Had a very nervous day when reconnecting the power cord gave me a solid power LED and a non-operational power button, until I got brave and reset the PMU again with the power cord plugged in (against Apple advice, but some folks said it worked). That got me booted again.
    Ran through several cycles of circle-with-bar gray screen boots, hang with loud fan boots, safe boots, etc.
    None of these steps indicated anything unusual or stopped the loud fan/dark screen/hang under 10.4.11.
    I'm now at the point where the machine boots fine, sleeps fine, and is generally happy as a clam when booted on my tried-and-true 10.5.8 disk, but does the loud fan/dark screen/hang when booted under 10.4.11, most consistently around sleep time, but sometimes just trying to boot.
    Other possible useful debugging info:
    Right now, the only things plugged in are Ethernet, Apple Keyboard, Apple Mighty Mouse, and VGA monitor with DVI adapter.
    Internal speaker no longer works, but headphone jack does.
    I did try during this process to get my old Thrustmaster ADB joystick running via a Griffin iMate, but those experiments are on hold until I get the base system stable.
    Most posts about similar behaviors (for example, http://discussions.apple.com/thread.jspa?threadID=2444469&start=0&tstart=0) point to a hardware issue, but that doesn't make sense to me because there aren't any issues under 10.5.8.
    My current thinking is that it may possibly be a firmware issue, that I have a version installed that requires 10.5.x and is not compatible with 10.4.x. System Profiler lists
    Boot ROM Version: 5.2.4f1
    However, I can't find much info about this version.
    Even if I found a 10.4-friendly Firmware Update, I'm not sure the machine would let me install an older version.
    So, does my thinking seem sound, or are there other avenues I should pursue?

    No PCI cards other than stock video card.
    No 3rd party kexts running. Just a fresh install of 10.4, then everything Software Update fed me to get to 10.4.11.
    Safe boot does not change the behavior.
    I ran several more experiments and have some more results to share.
    Booting from the Tiger disk reliably caused the machine to become unresponsive when going into sleep mode, after which the fans would go to full speed after a couple of minutes. Occasionally, upon power down and power up, I'd get the gray screen with the circle/slash graphic. Powering down and powering up would then result in a successful reboot.
    Booting from the Leopard disk would not cause the machine to hang when going in to sleep. However, I did notice that the machine wasn't really sleeping, either. The screen would blank, but I never heard hard disks park (the option to "put hard disks to sleep when possible" is checked in the Energy Saver System Preference), and the case fans continued spinning at low (normal) speed. Wake up took no time at all and made no sound except from the monitor. It may not be sleeping, but at least it's not crashing, either.
    Perhaps there really is a hardware issue, and Leopard is handling it more gracefully than Tiger. Unfortunately, Apple Hardware Test isn't finding it, and I see nothing indicated in the logs.
    It's less than ideal, but unless I find a solution, I may just put the machine in never sleep mode to keep it from crashing.

  • 24" iMac firmware issue

    I have a 24" iMac (Early 2009) that has what I believe to be a firmware issue.  The computer boots up to show the grey Apple logo, with a spinning gear and progress bar showing up pretty quickly.  The progress bar fills maybe 5%, then goes away, leaving the Apple logo and spinning gear.  The computer doesn't boot any further, with the gear continuing to spin.  It won't boot from an external drive, an install disc, or netboot.  I'm unable to clear the PRAM (holding the keys down does nothing).  I've removed and re-installed the RAM, and I've removed the CMOS battery on the logic board and put it back in after a couple minutes.  Nothing has changed.  I'm guessing a firmware update was installed and power was shut-off mid-update, causing to be stuck in this loop.  Am I missing something?  Is there anything I can do to clear this EFI update or reset the firmware somehow?

    Hello All
    As a 'newbie-switcher' (think that's right!?!), I am already on my second iMac in three months, with the first being returned within a week due to it restarting on it's own a couple of times a day and reporting no error at all! My current iMac has worked flawlessly until around a week ago when the restarting behaviour returned but as often as before, maybe once every couple of days. I reset the PRAM & SMC and checked\repaired permissions and all seemed ok until I then updated the EFI firmware a couple of days ago. I am now having similar problems, if not identical to those described here with the iMac not waking from sleep, shuting down or restarting again on it's own. And once I found it would not start at all, the screen stayed black but the fans were running on full speed! I have again reset the PRAM and SMC and will now wait and see!
    During my investigations to these problems I was able to cause the iMac to instantly shutdown and restart by simply touching the cables at the rear, Power or Keyboard, and last night I shut it down by simply putting my cup of coffee down next to the iMac!!! So you would think that a loose connection on the power cord could be to blame, but flexing and bending the cables and conectors will not re-create the problem!?!
    Do you guys think that I should be looking to swap it for iMac number three (third time lucky?), do you think it sounds more like a hardware problem with the power supply or the firmware?

  • Firmware Issues / BUG Report for WRT54GS v1.1

    Hi all,
    Router = WRT54GS (version 1.1 as printed on the bottom of the router)
    My current firmware (most up to date) = v 4.71.4
    I have found a few issues when using the following:
    QoS related issues:
    When using QoS, if users wish to disble it tempermentally (or change any other option), then re-enable it, any wireless device cannot access the LAN or WAN. This is regardless of static or DHCP IP. In order to fix this the user must reset the wireless security after re-enabling the QoS (disable the wireless security, save settings, set the security options again, and save settings)
    If a user changes the routers IP to something other than the default when using QoS wireless devices are unable to connect using either static or dynamic IP.
    Other issues I have encountered: 
    When setting wireless security up I chose WPA2-Personal (TKIP+AES). I also use MAC filter as well and only allow those that I specify to connect to the router. This works no problem. My problem is that if I disable SSID broadcasting my wireless devices will not connect regardless of static or dynamic IP. I have made sure there is sufficient strengh of the network (by sitting only a few feet from the router with my laptop to test this).
    How do I report these issues? Will they be addressed in the next future release of firmware?
    Thanks,
    Pete

    Hi, just to let you know. Reset, then re-configured and it is still having the issues as I have posted above. So deffiantly a router firmware issue I would say.
    New Firmware version upgraded to: v4.70.8
    Pete
    Message Edited by aniceguy on 05-01-2009 01:58 AM

  • NOKIA n80 firmware update version v5.0725.0.1 APAC

    buddy i update my nokia n80 firmware from v5.0719.0.2 to v5.0725.0.1 APAC
    guys the new firmware has small fonts it is not good.further iam looking for other changes in log
    any news regarding EMEA version.hope nokia corrects this problem
    Solved!
    Go to Solution.

    buddy they have improved the bluetooth. its nice.
    LT font router is also not working so u have to remain with small font but psiloc font magnifier works

  • MAJOR EWS ACCESS FIRMWARE ISSUE IN "MADE IN THAILAND" HP 7520 PRINTERS

    MAJOR EWS ACCESS FIRMWARE ISSUE IN "MADE IN THAILAND" HP 7520 PRINTERS
    I've borrowed 2 "Made in China" HP Photosmart 7520's. Both have a fully working EWS. (Serial Numbers begins with CN)
    I've purchased 2 "Made in Thailand" HP Photosmart 7520's. EWS does NOT respond in either one. (Serial Number begins with TH)
    This same finding is reported by numerous other users.
    The bad news is that I cannot locate "Made in China" 7520's in any of the large electronics stores to purchase.  Apparently HP has shifted their 7520 production to Thailand and in doing so has introduced a very significant bug that results in an ability to access EWS in the Thailand 7520's.
    HP- Are you working to remedy the firmware bug in the "Made in Thailand" 7520's that results in a total inability to access EWS? (I'm not interested in a work-around solution.  I want to be able to directly access EWS as per the specs and software)

    Hi mlrobins,
    I just sent you a private message. If you are not sure how to check your forum messages, this post has instructions.
    Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
    Jamieson
    I work on behalf of HP
    "Remember, I'm pulling for you, we're all in this together!" - Red Green.

  • Nokia 6500c Problem!

    my nokia 6500c doesn't seem to be getting any signal at all! i turn the phone on and i get signal for like 2 mins and then it just keep saying '' sim card registration failed '' or '' check info service '', does anyone know how to fix this
    thanks in advance

    Contact your network and request a new sim card.
    If the problem persists with a new sim take your phone to a nokia care point as it may have a faulty sim reader.
    Care points/service centres and repair info:
    UK • Europe • Asia-Pacific • USA •
    Canada • Middle East and Africa
    Elsewhere: Click here, select your country, go to the support section, then select repair. 

  • Firmware Issue after RAM upgrade?

    I have been able to reproduce a possible firmware issue:
    Upgrade to 4 x 2GB plus something else (another 2 x 512MB will do).
    Go to sleep mode and wake up again: fans will go mad, but they will slow down after 1-2 minutes again.
    Is anybody able to confirm this? Anybody with this configuration not having this issue? (What type/manufacturer of the 2GB modules do you use?)
    (several configs have been tested, it's not a matter of total memory)

    This can be ruled out. It happens when the computer is at low temperature too (modules will go to about 48-54oC when running under maximum load with distributed.net-client plus Rember - no sign of additional fan activity there); when turned on and sent to sleep, the modules are at less than 30oC, same when going out of sleep mode a couple of seconds later.
    AHT comes out fine, will try the SMC reset (I forgot about that - but I doubt it will help, as I tested several combinations.)

  • Nokia 6555b Firmware Update

    Is there an update for the Nokia 6555b firmware?
    Thanks,
    Pat

    Very odd, not known a phone to be missing it's product code from the label under the battery before.
    Have you tried connecting your phone to the computer and running the Nokia Software Updater?
    This will tell you if there's an available update.
    Be aware if your phone is network branded then it's highly unlikely that an update will be available. Most networks don't like approving new updates.

Maybe you are looking for