Seems N79, N85 and and 55 30 got Firmware updates

http://www.intomobile.com/2009/12/17/nokia-n79-n85-and-5530-get-firmware-updates.html
Nokia (NYSE: NOK) has released updates for three of its Symbian S60 smartphones. Without further ado, here they are:
Nokia N79 – after the update, the N79’s firmware reaches version 32.001. Details on what’s new are unknown at the stage, as we still haven’t seen the full change log. However, that doesn’t mean you shouldn’t hit the “Update” button – quite the contrary.
Nokia N85 – firmware version jumps to 31.002. According to AllAboutSymbian, this is mostly a bugfix release with tweaks on streaming and naming convention of GMail (Googlemail in the UK and Germany). I’m guessing, the N79 got a pretty much similar update.
Nokia 5530 XM – once updated, the low-end all-touchscreen device’s firmware is in version 20.0.080. The 140MB heavy download updates Nokia’s Ovi apps (Maps, Store), Nokia Music widget, and so on. In addition, it’s fair to add some known bugs are fixed here as well.
As usual, we advise you to backup your device prior to performing any updates, just in case…

The N79 firmware listed there has not been released. It's only presented for a small number of product codes and is likely experimental at Nokia.
Help I'm trapped in a sig factory.

Similar Messages

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!

Nokia N86 and Three (Network) Firmware Updates

When will we see a firmware update for the N86 on Three network? I got it yesterday as an exchange for my N85 and though i like the phone, the phone does freeze and crash on simple things like opening the inbox for messages and loading music.
Checked for updates, there were none, seems to be stuck on v11

That's up to Three. When they approve the update and add their customisations, Nokia will post it.
Help I'm trapped in a sig factory.

Macbook 2008 4,1 serious problems after 10.6.8 and 1.4 firmware update

I'm having a problem with my 2008 2.4Ghz Macbook. After doing a fresh install of 10.6.0 with a Retail DVD, the MB was working perfectly, absolutely no problems at all. I then ran Software Update and installed all the recommended updates to 10.6.8, and I only noticed in passing that there was a Firmware update to do too, as reported by Software Update. I ran that as well and, IIRC, it was applied after fully updating to 10.6.8 and after rebooting twice. The MB rebooted, ran the Firmware update (which seemed to complete fine, as the progress bar completed normally against the grey screen), then rebooted. Again, IIRC, after running the Firmware update, and I'm now at 10.6.8, I started a Repair Permissions and left the MB for a while. It was the next day, maybe 15 hours later, when I went back to the MB and it was in Sleep. I pressed a key to wake it and this is when the weirdness started.
The screen was "fuzzy", sort of out of focus, though I could see the desktop, and what I could see was: the Disk Utility window open on Repair Permissions (which had completed normally) and several Vertical Segmented Bars running across the bottom part of the screen, at about the height where the Firmware Update progress bar was. These bars were filling in from left to right. IIRC, it may have looked a little like when you wake from Deep Sleep (or Hibernate, or whatever it was called). Like when you Wake from Sleep after the battery has run out and then you plug the AC adapter in.
Anyway, before the Vertical Segmented Bars progress was completed, the screen went black. Pressing keys didn't bring the desktop back.
I did a forced shutdown, reset the SMC, then rebooted. No startup chime. The Superdrive, hard drive and fans spun up, but the screen remained black. After a few reboots, I got a desktop back, and tried to reinstall from both an external HD (with Restored disk image) and the Retail Snow Leo DVD. Both times, the MB booted to the startup screen: with the external HD, I held down Option and chose the Snow Leo install; with the DVD, the MB started normally while I held down the C key. The boot started from the HD and the DVD, but after about 60 seconds, with Apple logo and the spinning "cog wheel", the screen went black. And seemed to shut down. With the external FW hard drive, the drive made a loud click, its LED went off, then it came back on after a few seconds, as if it had lost all power to it, then the LED lit up when power returned to it from the shut down MB. Anyway, the installs failed.
I then attached the 2.4 MB to another MB (2.1) in Target Disk Mode and it booted fine into TDM. It showed up on the 2.1's desktop, I ran Check Disk and it checked out okay. I then looked under Startup Disk and the 2.4's disk was listed there, with 10.6.8.
I then booted the 2.1 from the 2.4's disk and it booted fine. I ran check Permissions, and a huge list of permissions to repair came out. At this point, I've left things as they are. The 2.1 is booted from the 2.4, the latter used as external boot HD.
I then replaced hard drive and RAM. Tried to boot from DVD and install, got to Apple logo and spinning cog wheel, but after about 2 minutes the screen went black.
I then connected an external monitor and rebooted from the DVD. The external display received a video signal and I got to the Snow Leopard install screen. All this time the Macbook display has remained BLACK.
I went to Disk Utility and reformatted the new drive, then started the installation, which completed fine. The Macbook runs normally connected to the external display.
Any thoughts?
Why would the Macbook display work fine at boot (Apple logo, etc.), but then cut out after about 2-3 minutes?
Why would the Macbook screen remain black while I got a video signal on an external monitor?
Does this sound heat-related in some way? I should note that while booting from the DVD and now installing Snow Leopard, the fans are going pretty fast.
I just want to point out that this was an absolutely pristine, impeccable Macbook until these recent problems. It is in fantastic condition, none of the usual chips out of the top case and trackpad area. After the latest fresh install of 10.6.0 it was perfect upon reboot. Fast, perfect Airport and Bluetooth, FW and USB worked perfectly with a FW drive and USB mouse I hooked up. The update to 10.6.8 via Software Update seemed to complete fine.
Then all the problems started AFTER THE FIRMWARE UPDATE.
I don't know how much stock can be put in the firmware update being the cause of the problems, but the sequence here would bear that out. These are also somewhat unusual problems, at least in my experience.
One of the odd things was when I first went to wake the Macbook after the firmware update: the "fuzzy", out-of-focus screen and the segmented progress bars. And it was just before the segmented bars completed progress from left to right that the display cut out and went black. And from that time on, I've had the aforementioned problems.
Any ideas or links to similar problems would be greatly appreciated, e.g. possibly firmware related, or where the Macbook screen works but goes black after a couple minutes. And now that I've been able to connect to an external monitor, it would seem that the video signal is okay too.
Thanks.

Just to update.
After leaving the Macbook unplugged and without battery for a few days. I reset the SMC and, with no battery installed, I've just now rebooted and:
1) the first time, it booted, but no chime, and when the display turned on, once again I got the "out of focus" desktop AND the segmented vertical bars on the desktop (and the bars were filling in from right to left); the display went black after about 10-15 seconds;
2) I shut down and swapped some different RAM, then reset the SMC again and booted without battery. This time I got the boot chime and the Macbook booted to the Apple logo screen and spinning cogwheel. After about 2 minutes, the cogwheel stopped spinning, as if to boot to the desktop, but then the display went black. The front light started to pulse after about 10 seconds, and the Macbook appeared to be in Sleep.
3) I woke the Macbook from sleep by hitting a few keys and this time it went to the desktop. This is the first time it's gone to the desktop since the problem started.
I had enough time to see that everything appeared normally on the desktop, such as the time and date, Airport was connected, etc. And then the display went black again, after about 10 seconds.
At this point, I can now always get to the desktop, but the display goes black after about 10 seconds. I have just enough time to press a few keys and the Macbook does respond.
4) I shut down and reinserted the battery. Here's where new problems show up.
With the battery inserted, and the Macbook in sleep, if I hit a key, the DVD spins up as the Macbook is waking, BUT now the front sleep indicator light FLASHES (blinks) 5 TIMES. No beeps.
The Macbook still gets to the desktop, like before, and the screen goes black after 10 seconds.
I found some info on the Apple site re. 5 flashes (Article 21502):
If you don’t hear beeps, but the sleep indicator light flashes five times when you start it up or wake it from sleep, its battery may need service. Take the battery to an Apple Authorized Service Provider, such as an Apple Retail Store.
For more information, see the Apple Support article below.
You can continue using your computer before you service the battery. Use a different battery, or connect the computer’s power adapter and plug it into a power source.
Note:If you use your computer without a battery or with a faulty battery, you could lose all unsaved changes if it’s unplugged while it’s on.
BUT, the battery is not defective, as it works okay in another Macbook.
I should also point out that the problem with the 5 indicator light flashes or with the battery did not exist before the 10.6.8 and the Firmware 1.4 updates.
Any ideas?

Computer died and interrupted the Firmware update, now I'm stuck

Not sure what to do, the computer won't start up, but the light is on... no keyboard functions will work, and the screen is black...

If a firmware update has failed during installation and the firmware becomes damaged as a result then there is a way to restore the computer's original firmware.
It's necessary to download certain software from Apple and burn it to CD. Of course this means another Mac (in working order) is required.
Details here: Firmware Restoration CD 1.2
Note there is a small error in instructions 7 & 8. A correct version can be found here: artnum 303469
MacBook (OS 10.4.8); iMac G4 (OS 10.3.9); iMac G3 (OS 10.2.8); etc

Airport Utility and AEBS DB firmware updates question

I have an AEBS DB2 version set up with a MBP Airport Utility which came from the install cd of the AEBS, which was Airport Utility 5.5 and the AEBS DB2 had firmware 7.5. I did update to 5.5.1 and 7.5.1, respectively and all is fine. However, I have another MBP that is just set up to use the wifi signal. I noticed that it also wanted to pull in the AU 5.5.1 update even thought I never installed the AU from the AEBS cd. I am wondering if 5.5.x, which could only be gotten on the cd, is now just the standard and it doesn't matter. Or, did the other MBP just know it was using a wifi AEBS and thus Apple set it up to find that newer update..after all, It never found a 5.5 before...it was just using whatever upto 10.6.2 had installed.

I noticed that it also wanted to pull in the AU 5.5.1 update even thought I never installed the AU from the AEBS cd. I am wondering if 5.5.x, which could only be gotten on the cd, is now just the standard and it doesn't matter.
Interestingly, when 5.5.1 became available via AU, it also showed up for Macs & PCs via a download from Apple Support - Downloads site as well ... and you're right, v5.5 is only available from the CD.

Tried to Restore Shuffle,then got"Firmware update failure.Disk write error"

I tried to restore my ipod shuffle and this is the message I got. Any thoughts?

FIrst try this artical http://docs.info.apple.com/article.html?artnum=301267
Also try putting the ipod into "Disk Mode" http://docs.info.apple.com/article.html?artnum=93651 THEN connect it to the PC and restore it

Motion crashes - Macbook Pro Software update and Firmware update

Anyone out there that is working with Motion 3.0.1 on one of the new Macbook Pros (Santa Rosa) and has installed both the Macbook Pro Software Update 1.0 and the EFI Firmware update (for the 15 inch models)???
Motion 3 crashes on the Macbook Pros with the MBP Software update installed (see thread:
http://discussions.apple.com/thread.jspa?threadID=1028746&tstart=45
The solution so far is to wipe the hard drive and reinstall everything from scratch EXCEPT the software update 1.0. However, I'm trying to find out if anyone has installed the Firmware update, which requires the software update to be installed first, and if they are running smoothly.
???

I just restarted then tried to open InDesign again and it let me download a java update that seems to have fixed it.

Freeze at startup after System and Firmware update - Help!

I took the automated system upgrade last Sunday including updates on a bunch of Apple applications, OS X 10.4.6 (it was included if I recall correctly) and a SMC Firmware update. After downloading all files and installing them my iMac restarted. After that the SMC Firmware upgrade started and I followed the instructions ending in another restart.
This is where my problems began. At this startup I got through the grey screen with the Apple logo and got so far as to the blue screen with the Mac symbol saying something like "starting up". The progress bar started moving and froze after reaching about a fifth of its final length.
As this was a firmware update I didn't want to interrupt anything so I left it for the night (no progress in the morning) and for the next day. Still no progress when I came home from work so I shut it down (pulled the power cord).
Efter this I've tried to fall back using the Firmware Restoration CD available at Apple's support page, but this doesn't work. My iMac refuses to start the installation of the old Firmware even though I follow the fallback instructions. (After starting the computer and keeping the power on button pressed I wait for the front light below the screen to first flash rapidly for a while and then do a SOS (three short, three long and three short blinks). The SOS however, never happens, instead the computer proceeds directly to the grey startup screen before it freezes when it reaches the blue screen.
I have no clue to what to do. Any and all help will be greatly appreciated.
Staffan
iMac 20" (Intel) Mac OS X (10.4.6)

minxlj,
It is not my intention to be rude, however, it is my intention to be direct. Do you have a G5 or do you have an Intel Core Duo, or perhaps even both? Because right now your signature says you have a G5, which has PPC chips in it made by IBM, not Core Duo chips made by Intel.
The reason I ask is because, just as in another Discussion here in the Intel forum, you are responding to information that appears to not apply to the computer you say you have and you are giving information that, if you have a G5, does not apply to the computers of the folks here in the Intel forum.
Could you please clear that up by correcting your signature so everyone here knows you are comparing oranges with oranges and not mangos with oranges?
Staffan,
As far as the SMC Firmware update and the Firmware Restoration CD, the two items are not related. The Firmware Restoration CD is only for the Firmware Update that came out in mid-April. It is intended for someone whose computer messed up in the application of the Firmware Update and is intended to bring their computer back to its Firmware state prior to the botched Firmware Update. It will not assist you if you had problems applying the SMC Firmware Update from early May.
If I am understanding your description of your Mac's problem it sounds if if you have successfully installed the SMC firmware update, but now have a possible 3rd party satrtupitem that is not allowing your Mac's OS X to fully boot. You can check to see if both the Firmware Update and SMC Firmware Update have been successfully installed by booting your Mac into safe Mode by pressing the "Shift" key during startup. This boot will take longer than normal because it is verifying and repairing your directory. After the desktop appears, go to Apps/Utilities/System Profiler. In the Contents section, highlight Hardware and Hardware Overview should show; Boot ROM Version: IM41.0055.B03 for the Firmware update and SMC Version: 1.1f5 for the SMC Firmware Update.

2010 Mac Pro Crash and Firmware Update Issue

My 2010 Mac Pro crashes for no apparent reason. I have a couple FCP projects to finish and I cannot rely on this machine. I have the most recent problem report details and a pesky Firmware update that appears corrupted and refuses to install.
I've repaired permissions using Disk utility, applejack, and even used memtest to check that I didn't have a bad RAM module. All tasks ran successfully.
These may be 2 separate problems. I'm not sure at this point.
I'm using only 1/3 of the drive capacity for the OS drive and about on my Final Cut Media drive.
FCP is compatible. Been using it for nearly a year. Using a third drive for a Time Machine Back-up of all FCP media. The firmware update is specifically for the 2010 Mac Pro - Mac Pro EFI Update 1.5

OK, thanks.
So I restored the original firmware, and I got through the update.
Here is what the update instructions should say:
"Once the flashing starts continue holding until the light is steady again."
I thnk my problem was that I released the button too soon.
Bob

Programmer's button and firmware update

This issue is of more general nature, at least B&Ws use similar procedure, maybe all newer Macs. An OS 9 program (firmware updater), a separate firmware image, shutting down, pressing programmer's button... I would really like to understand the mechanism.
What happens when I push the programmers button? Is it just for opening the flash for writing?
Why did my iMac G3 SL chime after the beep and before the progress bar?
Where does the firmware updater place itself and the firmware image and how does open firmware find them? Would it be possible to place them there on another computer? Why is there a requirement that the boot disk is writable? I guess this makes it impossible to build a bootable CD that could make the update?
Is it really the firmware updater that writes the new firmware into the flash? Not some ROM routine?
How does the firmware updater decide its behaviour? When first run inside the OS it initiates the upgrade, then after pushing the programmer's button it does the real job, and when rebooting again it shows the result.
Why did Apple not make a version for OS X?

Have you tried connecting an external monitor to the computer with the black screen? That will sometimes work. Some people have managed to run the firmware update, even with a black screen, by being in a completely darkened room and being able to see just enough on the screen to run the update.
There are lots of tricks for getting firmware installed here.
Below is an excerpt regarding dealing with the blank screen issue:
39. If your iMac is booting up but you can't get a screen display then you have a few options to consider:
40. Some people have managed to do a "blind" firmware update. First of all it will be necessary to update the iMac's OS to 9.1 (unless you already have this or a later version of OS 9 installed) and get the firmware updater onto the HD.
41. There are different ways of doing this - e.g. take the HD out and put it into another Mac (Donna's note- to avoid a common confusion, please be aware that firmware does not "reside" on the HD at all, even though it needs to be run from the HD. For example, once your firmware has been updated, you can put a new hard drive into that iMac without needing to update the firmware again. However, this drive swapping may be a way to get the updater onto the drive and then put the drive back into the iMac and try to install the update - if that makes any sense); or if file sharing is on then you might be able to access the iMac's HD remotely for updating the OS and copying the firmware updater over; or you could try starting the problematic iMac in "FireWire target disk" mode. This allows you to connect to another Mac using a FireWire cable and have the iMac's HD appear as an external disk on the other Mac, allowing you to install OS 9.1 and copy the firmware updater over. You may also find this article helpful: Macintosh: Computer Does Not Enter Into FireWire Target Disk Mode.
42. If you have access to software such as Timbuktu for remotely controlling another machine then this would be a convenient way of seeing the screen of and controlling the problematic iMac.
43. If you really have no way of getting a screen display, then try putting the unpacked firmware updater in the Startup Items folder (contrary to the advice above in para. 35). Then when you boot OS 9.1 (or higher), the updater will automatically start. You will need to dismiss 2 (?) dialogs by pressing <Return>: the first is a licence agreement, and the second is the dialog to shut the iMac down. You will have to use your skill and judgement in determining when the iMac is ready for you to press Enter each time! Once the iMac has shut itself down in preparation for the firmware update you can proceed as per the published instructions.

My Xperia S (LT26i) firmware update problem and slowing problem

Hi, I have Xperia S (LT26i) and i tried to update my phone to 6.2.b.1.96 firmware using PC Companion bu couldn't accomplished. It gave a error after long pressing the volume down button and starting the firmware update process. So i had to turn back to old firmware. Secondly my phone is so slow. Facebook is opening approximately 20-25 secs. and gives "facebook is not responding" messages while using. Same is for telephone and browser. I factory resetted the phone a couple months ago and i dont want to reset the phone regularly. Can you give me an advice? Thanks in advance...

A clean update
Performing a system repair using PC Companion - This will factory reset your phone and erase all data
Switch off your phone and unplug from Pc (Hold volume up and power for around 10 seconds)
Start PC Companion and select Support zone then Update my phone/tablet then in Blue Repair my phone/tablet and follow the on screen instructions - When prompted connect your phone still switched off holding volume down or back button - This should start the repair or reformat process
If you are using Windows 8/8.1 or a 64bit operating system then adjust the settings for PC Companion and run in compatibility mode and chose Windows 7 or XP

HT201272 A book I downloaded using iBooks seems to have frozen and won't finish downloading. What can I do to get it to resume?

It says its downloading but there is no progress what so ever.

Hi Bradyfromidaho,
Welcome to the Support Communities!
The article below should answer your question.
You can click on the link to see more details and screen shots.
I've highlighted the pertinent information for you below.
iTunes: How to resume interrupted iTunes Store downloads
http://support.apple.com/kb/ht1725?viewlocale=it_it
If your download was interrupted on your computer
You will be prompted to resume your download the next time you quit and reopen iTunes. You can also manually restart the download with the following steps.
Resuming downloads from a computer
Open iTunes.
Choose Store > Check for Available Downloads.
Enter your account name and password.
Click the "Check Downloads" button.
Click the Resume or Resume All button, or the resume arrow to resume the download.
If you believe that the item downloaded completely but it is not appearing in the Purchased playlist, click Library on the left side of iTunes to see if the item appears there.
If your download was interrupted on your iPhone, iPad, or iPod touch
You can manually resume the download on your device with the following steps.
Resuming downloads from an iOS device
From the Home screen, tap the iTunes icon.
For iPhone/iPod touch, tap More > Downloads. For iPad, tap Downloads.
Enter your account name and password.
Click the "OK" button.
Click the Resume, Resume All button to start the download.
If you cannot complete the download on your device, you can finish the download in iTunes on your computer and then sync it to your device. For instructions, see the following articles:
iTunes Store: Where can I download and sync my purchases?
iTunes Store: Transferring purchases from your iPhone, iPad, or iPod to a computer
Additional Information
If your purchase does not resume downloading after following the steps in this article, you can also try the following steps to troubleshoot the download issue.
Restart your computer or device.
Check for updates for your Mac or PC and install any software updates. Also, check for and install updates for any security software you may have (anti-virus, anti-malware, firewall, and so on).
If using Wi-Fi for Internet access, try using a different Wi-Fi network when downloading. If you are connecting to a home network, try restarting your Wi-Fi router. Also, check for and install any firmware updates for your Wi-Fi router. (Refer the manufacturer's website for your router to get information on updating its firmware).
If you are on a computer, try using an ethernet cable for wired Internet access instead of using Wi-Fi. If the issue is still unresolved and you're using iTunes for Windows, follow steps in iTunes for Windows: Troubleshooting security software issues.
I hope this information helps ....
Have a great day!
- Judy

Freezing Imacs: Firmware Update 1.0

Could this be the cure?

I found out about the update from the MacUser RSS feed. In fact, I was the anonymous user the author referred to in his piece:
Yesterday, in my "Apple bombs the Mac" post, an anonymous commenter opined:
+Wonderful. Now how about them putting some of their resources towards coming up with an improved iMac video driver to stop all of the **** freezing/blue screen/black screen issues we're having?+
Apple apparently reads MacUser's anonymous comments because--brace yourselves--they today made good on their promise to remedy that issue (which apparently still plagued some users even after a initial attempt at a fix), and released a firmware update for some 20" and 24" aluminum iMacs. Apple says the patch "updates the graphics firmware on the ATI Radeon HD 2600 Pro to improve system stability."
Anyway, I ran Software Update and the ATI firmware update didn't show up. According to Apple, if your machine needs it, it will show up there. They also said that if you download it yourself and try to install it (and it doesn't need it), the install will come back with an error message.
Well, having nothing to lose (I've been dealing with this s--t since I bought the computer), I downloaded the firmware update anyway and installed it.
No error message. It installed fine.
I've been testing the computer, running every graphics-intensive program flat-out and it hasn't frozen yet. FrontRow. iTunes with visualizer at the same time as I made a movie in iPhoto. iTunes with visualizer at the same time as Medal of Honor on its highest settings. Basically I loaded up everything I could, including Activity Monitor, and so far it's going well.
The irony is that this morning the computer froze when I first turned it on, and that was the last straw. I spent all afternoon on the phone with AppleCare and finally got a Return Merchandise Authorization, and NOW they come out with a fix.
Even with this "fix", though, I'm probably going to return the machine. And those of you who are unsure about whether or not to do a return, let me tell you why I'm going to.
When I was on the phone with the Customer Service guy (the TOP of the AppleCare hierarchy; first, basic rep; then, Product Specialist; then, Sr. Product Specialist; THEN the Customer Service people who can actually authorize returns), he told me something interesting. I said that I wanted to make sure I didn't encounter the same problems with a new machine and asked him if people with new machines seemed to be satisfied.
He said, "Yeah, cause they're getting the ones with the new [graphics] cards in them."
"So there were a few bad cards," I said, playing dumb.
"Yeah," he said. "But you won't have any problems now. What I hear, they pulled them."
I'm not saying the above is gospel. All I'm telling you is what I heard from the Customer Service person setting up my return authorization.
The sense I'm getting from all of this is that they know there are a number of machines out there with bad cards, and the reason why the firmware update doesn't install on all machines is that it somehow tests the card first to see if it's faulty. If it is, it does the firmware update, maybe deactivating part of the card or creating a workaround. Otherwise, why wouldn't the update be mandatory for all computers with that graphics card? It's very fishy to me. I'm going to assume that the update merely put a patch on an otherwise bad card and press forward with the return.
Hope my rambling here helps somebody.

After EFI Firmware update 2.3, MBP Early 2011 will not boot. During restart it all went wrong please help!

Hello,
I've done an ample amount of Internet research to find an answer to this problem however nothing yet found is quite like this. I will start from the beginning.
I am traveling through Europe, and I normally live in California. When I arrived in Ireland my MBP early 2011 15 inch, began crashing constantly when I had several tabs open on Chrome and maybe one or two low CPU/Memory using applications, nothing the 8gb RAM &750gb hard drive can't normally handle. Thus I began trouble shooting. I ran disk utility once started up and repaired both disk and permissions. Still crashing. It didn't seem like it had anything to do with a kernel panic shut down, I never would receive the usual message indicating so. After that I did an SMC reset. It was still crashing. I then upgraded the OSX from 10.8 to 10.8.4 believing it could help. It did momentarily, but then crash again. (When it crashes screen goes black suddenly and upon pressing power button does a regular boot on my single partition). I decided attempting to repair using the Internet recovery option but it appeared my MBP had not yet have it installed, so I downloaded from Apple and began installing. Here I made a mistake, I unplugged the power source as it was restarting. When the gray screen and apple appeared, the loading bar shows up as it says it will when installing the update, but when the bar fully loads it crashes every time. I've tried starting in safe mode, which then loads but never goes further (I let it stand for two hours such as that and nothing). Then I decided to allow the MBP to fully charge overnight to give it time and charge. This morning the problem has stayed the same, even with power source plugged in. Please help I need this to work.
Thank you and please ask any questions!

Your constant crashing problem is probably some type of hardware fault which no update can fix. Doing the 10.8.4 update and then the firmware update just caused further problems. you need to take thr system to a apple store to be diagnosed and fixed if cost effective.

Seems N79, N85 and and 55 30 got Firmware updates

Similar Messages

Maybe you are looking for