Speaker problem after an update to windows 8.1 on Nokia lumia 520

After an update to 8.1 my windows phone nokia lumia 520 has encountered a problem with the speaker. I am uable to play any music neither am i able to hear any ringtone of any kind. The phone had no problem till an automatic update took place when i got connected
to an internet acces.
Can anyone let me know if this is an issue of an update or malfunctioning of the speaker without any reason.

As you tried already a reset, did you consider the Nokia Software Recovery Tool on a Windows computer as well?

Similar Messages

Iphone speaker problem after ios7 update

After i updated to ios7 on my 4s the right speaker stopped working instantly. Anyone else have thuis problem? And how can it be fixed?

Perform a "hard reset" on the device by pressing down and holding the home button and the sleep/wake button for up to 30secs. until you see a black screen with the Apple logo, then release.
Then test to see if it solved the problem.

Had a problem after download updated itune, error 7 (window error 126) cant open itune at all

Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.

After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.
This is boot camp problem, because in other normal notebooks (e.g. SONY VAIO, Lenovo with Windows 7) the gadgets are working normally.
I am attaching the screen shot of Desktop Gadgets and Security updates of Windows 7.
Kindly solve this issue ASAP.
Shailendra Gupta
<edited by host>

You are not addressing Apple, but a community of unpaid volunteers. So ASAP won't cut it. Also, you should refrain from posting personal information (like your email address) in the body of your comments, as this is part of the community usage guidelines.
Have you reinstalled the latest Boot Camp Windows 7 drivers, just in case Microsoft overwrote some of them during the Windows 7 security update?
If you want to communicate issues with Apple about Boot Camp and OS X, click on the link. Just don't hold your breath on receiving a response.

Itunes starts extremely slow after an update of windows 8.1.

Itunes starts extremely slow after an update of windows 8.1.
It takes up to 10 minutus.
If I see the appliction log in event viewer then I see the following errors on the Bonjour service.
For instance:
Client application bug: DNSServiceResolve(a8:fa:d8:3a:1e:8f@fe80::aafa:d8ff:fe3a:1e8f._apple-mobdev2._t cp.local.) active for over two minutes. This places considerable burden on the network.
followed by
SendWakeupPacket error: sent -1 bytes: 10065
What can this be?
Already thanks,
John

I did all the step with save mode and that didn't gave the same result.
Then I created a new account and there itunes started up normally.
So I contued with the user section.
I removed the itunes directory from
c:\Users\username\AppData\Local\Apple Computer\iTunes
This gave the same result in not starting up.
Then I removed the itunes directory from
c:\Users\username\AppData\Roaming\Apple Computer\iTunes
The a popup appears that the Bonjour Service has been disabled.
I looked in services and saw that is was still running.
But I tried to restart this service and it took a long time to stop this service.
Even if I selected restart the Bonjour Service didn't start.
Manually starting was not a problem.
Clicking OK on the popup let itunes start quickly. And closing and starting it again was also quickly.
So Matt thanks for your answer.
If it happens again I have to see if it was the removing of the itunes directory from roaming or restarting the Bonjour Service.

Multiple Samsung Stratosphere problems after FF1 update

There have been multiple posts on various issues users have found after the recent Stratopshere FF1 update. Some were replys to older posts and some only touched on a single issue. I wanted to consolodate into one thread, and hopefully get teh attention of Verizon to maybe reply here.
For reference, a lot has been discuss here --> https://community.verizonwireless.com/message/874446
Summary: Verizon and Samsung have finally updated the Stratosphere almost 1 year after release. This updated the phone from Android 2.3.5 to Android 2.3.6. Going by filename, this is known as the FF1 update. This update went live at the end of August 2012, and most users were upgraded before mid September 2012.
There were some noticable changes in this update:
-Lock screen has changed. The puzzle piece and glass lock options have been removed. New options have been added, such as facial recognition unlock.
-Call answering screen has changed, introducing the option to ignore call with a message.
-Camera now has digital zoom ability.
-Ability to uninstall the 2 games the phone comes with (Need for Speed and Lets Golf)
-Phone icon has changed ever so slightly
-Wifi icon now included up and down arrows to indicate data is being sent or recieved
-Wallpaper no longer "stretches" over multiple screens - ie, it no longer scrolls as you move from screen to screen
-The visual voicemail app has been improved (I have personally not used this feature)
-Callback number is now supported in text / picture messages
-Android core OS updated from 2.3.5 to 2.3.6 (both versions are still Gingerbread)
-Update to how the device deals with the end of scrolling. It used to rubber-band bounce back, now it will just give a green bar and expand the bar as you scroll. (I cannot fault Samsung for this change as this was at teh core of an Apple lawsuit and has been changed in newer versions of Android.)
-(I am sure there are more. please list any others you may have noticed)
I have found some problems, and others have confirmed that this is (at least) somewhat widespread:
-The biggest problem is with wifi connectivity. Upon an initial connection to wifi, everything works great. After somewhere between 15minutes and 2 hours, problems start happening. Its as if the wifi keeps hanging or reconnecting. Download speeds (tested with the SpeedTest.com app) slow to about one third of normal. Apps like Facebook that require a constant connection will just time out.
-It appears the signal strength for 3g and 4g connections is lower. There are places where I used to get a 4g connection, and now I only get 3g. Some palces I fall back to just 2g digital.
Another minor issue i found was with text messages. When you reply to a message, it no longer automatically focuses the text in the input box. You have to first click into the box to start typing. Not a huge deal, but one more step to take over and over. Minor annoyence.
At my house, I struggle to get a 3g or 4g signal. I depend on wifi for my data connection. So with the wifi connection problem introduced by teh FF1 update, my phone is somewhat useless to me now while at home. Here are teh troubleshooting steps I have been through so far to attempt to fix the wifi problem:
-Complete factory reset on my phone. (did not help)
-Pull battery and SIM card out of phone for 15 minutes. (did not help)
-Went to a Verizon store. The guy at the store was helpful, and said he also had a Stratosphere and was getting the same wifi problems after the update. He said all he could do was to send me out a replacement phone. I got the replacement phone, and it had the same problems.
-I read in multiple palces that Android 2.3.6 has a bug within wifi and DHCP. Apparently if you have a DHCP lease set to "forever", the phone will keep requesting a new address. Setting the DHCP server on the router to something like 2 weeks, or using a static IP is supposed to solve this. I have a NetGear N900 router, and I can not change teh DHCP lease time. It appears, however, that my router is not sending out "forever" leases. But just to make sure, I gave my phone a static IP. (None of these steps made any difference).
The only thing that temporarily fixes the problem is a reboot of the phone. This will again give you anywhere from 15min to 2 hours of good wifi use before problems start happening.
I have now had this update for over a week, and on 2 phones. I still can't maintain a wifi connection for much longer than 15 minutes without problems starting up.
I am asking Verizon or Samsung to at least confirm this issue if possible. Maybe there are newer revs of the Stratopshere hardware that don't have this problem. Or there is something unique about my (and apparently others) situation. But it seems like Verizon's current stance is to offer a repalcement phone (as currently all Stratospheres are within their 1 year manufacture warranty as the phone has not been ouy for quite 1 year yet).
I am asking for a workaround for this problem, or a true fix adressed by a new software update, or at least allow us to roll back to the original Andorid 2.3.5 software.
I have had my original Stratosphere for almost a year with no wifi problems - then get the FF1 update and have had nothing but problems on 2 different phones.
Thank you for your time.

Thanks for starting a comprehensive thread on problems with this update. I want to add one more.
I have Bluetooth in my car (a 2004 model), and previously the phone has connected to it practically instantly when I start the car. Since the update, I have never been able to connect the phone to the car by Bluetooth. Several times the phone has made a standard notification sound at the moment it should be connecting to Bluetooth, though no notification appears. I have no idea what that could mean.The car's Bluetooth shows up as paired in the list of devices in Settings > Wireless & networks > Bluetooth settings. I haven't seen this widely reported as an update issue, but perhaps some others have experienced it too.
UPDATE: I finally did some testing, and found that the notification was to signal the extremely brief appearance of a dialog indicating that the car's Bluetooth was requesting a connection. Accepting that request let the phone connect with the car, and calls went to the car's sound system as they should. When I turned the car off and back on (just the electrical system; not wasting any gas on this!), the connection was established immediately, so apparently the acceptance only had to be done once. Nevertheless, it did have to be done, and the dialog notification disappears within seconds. I believe it would have been possible to go into Bluetooth settings and accept the connection request there if I missed the notification; but not seeing the notification, I might not know to do this.
One further observation: When I turned the phone's Bluetooth off and back on after a connection had been established, leaving the car on the whole time, the two did not reconnect. I believe that may be different from before the update, but I'm not really sure.
Message was updated by David Rensberger

EFI Problems after last update anyway to downgrade ??

Hello
EFI Problems after last update anyway to downgrade ??
i have updated my MacBook 2010 EFI to MB71.0039.B0E which is 2.1 version
after updating to this version the Boot time become much slower when i want to change boot partition
and shutdown become very much slower and startup too
i tried to install Mac OS X Lion again but it doesnt help
can i downgrade to this version 2.0 ???
or when Apple will release the new version ?
or where can i send a feedback regarding this issues !!!!
Thanks

These are user to user forums. If anyone knows the answer, they will give it.
You can always call Apple support which may charge a fee or you can patiently wait for an answer here, which is free.

Share and save problem after latest update

hello,
i have share and save problem after latest update - i have installed ps touch on nexus 5 about 2 months ago and until yesterday everything was good but after latest update i can't save and share images in ps touch ( i do reinstall this app but problem is still and app doesn't work properly ) how can i downgrade to the old version ? Could you fix this problem quickly ?

i use app which called "aLogcat"
--------- beginning of /dev/log/main
I/dalvikvm(24476): Enabling JNI app bug workarounds for target SDK version 11...
D/dalvikvm(24476): GC_CONCURRENT freed 174K, 2% free 17054K/17264K, paused 2ms+2ms, total 15ms
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
--------- beginning of /dev/log/system
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=2, eventTime=27743080, downTime=27743066, deviceId=4, source=0x1002 }
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=27743086, downTime=27743066, deviceId=4, source=0x1002 }
D/dalvikvm(24476): GC_FOR_ALLOC freed 122K, 1% free 17271K/17428K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 10K, 1% free 17434K/17604K, paused 7ms, total 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 65K, 2% free 17690K/17928K, paused 8ms, total 8ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 17.615MB for 328336-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18010K/18252K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18011K/18252K, paused 9ms, total 9ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 18.073MB for 479536-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18479K/18724K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 18481K/18724K, paused 2ms+1ms, total 10ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 6ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 18.532MB for 479536-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18949K/19196K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 19418K/19668K, paused 1ms+1ms, total 10ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19592K/19844K, paused 8ms, total 8ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 20.049MB for 933136-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 20503K/20756K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 21416K/21668K, paused 1ms+1ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 50K, 2% free 22351K/22580K, paused 7ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 5K, 1% free 23900K/24140K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 1% free 25824K/26084K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 3411K, 14% free 24528K/28204K, paused 12ms, total 13ms
D/dalvikvm(24476): GC_CONCURRENT freed 2814K, 14% free 24256K/28204K, paused 2ms+1ms, total 11ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 9266K, 1% free 17270K/17424K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 15K, 1% free 17575K/17748K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 22K, 2% free 17875K/18072K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 2% free 18195K/18396K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18517K/18720K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18838K/19044K, paused 11ms, total 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19159K/19368K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19480K/19692K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19974K/20192K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 20616K/20840K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 21431K/21664K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 22714K/22960K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 2% free 24004K/24432K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 8478K, 33% free 17593K/26228K, paused 14ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 32% free 17895K/26228K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 31% free 18198K/26228K, paused 11ms, total 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18519K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 29% free 18840K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19482K/26228K, paused 2ms+1ms, total 14ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 10ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 23% free 20297K/26228K, paused 2ms+1ms, total 15ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 19% free 21260K/26228K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22543K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 9% free 23979K/26228K, paused 21ms, total 22ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 8485K, 33% free 17598K/26132K, paused 13ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 25K, 32% free 17894K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 12K, 31% free 18204K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18524K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 28% free 18845K/26132K, paused 8ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19487K/26132K, paused 1ms+0ms, total 9ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 20129K/26132K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 20% free 21091K/26132K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22375K/26132K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 9K, 9% free 24011K/26132K, paused 14ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 2147K, 10% free 23855K/26456K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed 8776K, 35% free 17337K/26304K, paused 3ms+2ms, total 20ms
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=564.0, y[0]=-50.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=28190972, downTime=28190972, deviceId=4, source=0x1002 }
D/dalvikvm(24476): GC_CONCURRENT freed 186K, 31% free 17626K/25476K, paused 2ms+1ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 63K, 30% free 17884K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 3K, 29% free 18201K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 27% free 18696K/25476K, paused 2ms+1ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 25% free 19190K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 19831K/25476K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 19% free 20794K/25476K, paused 2ms+0ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 14% free 22078K/25476K, paused 1ms+2ms, total 14ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 7% free 23855K/25476K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 6% free 24176K/25476K, paused 2ms+1ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 6440K, 26% free 19562K/26216K, paused 9ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 93K, 23% free 20207K/26216K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 11K, 21% free 20935K/26216K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 18% free 21673K/26216K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22499K/26216K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 10% free 23695K/26216K, paused 9ms, total 9ms

Control beats audio settings is not working after i update my windows 8 to windows 8.1

i dont know what just happen after i update my windows. hp support software also not working. hardly i found nvidia driver as well.. Please help me asap.
Notebook Model = HP ENVY 15 - j039tx
Thanks
Tahir

anyone here!!! who can help me??

After bios update, my window media player got hang and headphone clarity is not proper

HP Pavilion g6 after bios update, my window media player got hang and headphone clarity is not proper

Hello mathewstays,
Which model of g6 do you have? Which operating system? I'll be able to better assist when I know this information.
Thanks,
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

IPhone 4s got problem after I update to 7.1.1. Battery drain so fast

iPhone 4s got problem after I update to 7.1.1. Battery drain so fast

The Ultimate Guide to Solving iOS Battery Drain
<http://www.overthought.org/blog/2014/the-ultimate-guide-to-solving-ios-battery-d rain>

Please Read This To Reduce or Eliminate Problems after Software Update

Hi all, I have been reading quite a handful of Mac users here reporting problems ranging from minor ones like slow downs to major ones like application crashes, and many of them blame the new OS and/or Security Updates.
Without learning more from the details of how did they perform their Software Updates and Install, I am making a huge assumption that it maybe something they did or didn't do, one of the key things they did not do is Repair Disk Permission
Below is what I called, the "ritual procedure" needed to perform before and after a Software Update, and also any other major software installation - to help reduce or eliminate "hiccups" afterwards, I cannot gaurantee that all macs all over the world will not suffer any problems after an update, but by doing so, you may help reduce it; I have 4 macs all together and so far I have not encounter any major problems after many versions updates.
Anyway, I didn't come out with this series of procedures, I read it off somewhere in this Discussion quite a while ago, and thought I share it again with all of you:
1.Before starting Software Update, unplug all external devices, FireWire, USB, hubs etc etc, not just turning them off but unplug the cables off your Mac, leave only your keyboard, mouse and internet connection on (unless you are using a wireless keyboard and/or mouse or on wireless internet)
2.Repair Disk Permission
3.Restart the Mac, then start your SU, do not run any other apps.
4.After finishing SU, restart your mac; If you are updating OS or Security Updates, Restart is required.
5.Repair Disk Permission again
6.Shutdown and re-plug in everything and start up your mac as normal.
I know the procedure is pretty long and "troublesome", especially the unplugging and restarting part, but so far it really has done my macs good, so I am going to "swear" by it... my FireWire, USB devices etc still work as normal.
This is really contrary to that "Macs are easy to use", yes, no doubt about it, but the software updates etc is just well, put it this way: The Mac OS when it comes to updates, is very very delicate... so handle with it great care, it will just turn out okay.
Cheers

Thank you for posting that. I posted a similar set of suggestions here:
http://www.macmaps.com/backup.html
Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

Can not turn on Nokia Lumia 520 after Microsoft up...

Hi, I've got Nokia Lumia 520 with Windows Phone 8
before yesterday Microsoft update appeared on display and wanted me to instal. So I clicked on "instal" button and after that there was "restarting..." on the display for a while and phone went off. Since that I can't turn on my phone. I tried keep it on charger for a long time, I tried take off battery for a long time, I tried to hold all buttons combinations, but my phone is still dead. Do you have some advises or there is only one option to send that to Nokia for service?
Thank you for answers
Honza

First try rebooting by ressing and holding the vol down + power button for around 10 seconds. If it works, the phone should vibrate and restart. If this does not work you could try hard resetting, instructions as per link below. Faiuling that, you will need to get it to your local Nokia Care Point.
http://www.nokia.com/gb-en/support/product/lumia520/faq/?action=singleTopic&topic=FA141447

Is Nokia Lumia 520 Windows 10 Ready ?

I want to know that Nokia Lumia 520 is windows 10 ready or not if not then I have to install through phone insider plss tell it is ready or not..

see the below post, especially the "Does that mean that today’s Lumia devices can be upgraded to Windows 10"-part. At the moment there is nothing further we can communicate on the topic, more details will be available later on.
http://lumiaconversations.microsoft.com/2015/01/22/the-lumia-you-love-gets-even-better-with-windows-...
http://www.microsoft.com/en/mobile/nokia-x-updates/
http://www.microsoft.com/en/mobile/nokia-x2-update/
http://www.microsoft.com/en/mobile/asha-software-update/
http://www.microsoft.com/en/mobile/support/software-update/wp8-software-update/
http://www.developer.nokia.com/Community/Wiki/Nokia_firmware_change_logs
https://twitter.com/LumiaSWUpdates

Nokia Lumia 520 saying 'incorrect password' after ...

I downloaded the 'Mobile accessibility' app yesterday, it required a reboot and i agreed . After that i entered my password as usual but it say ' incorrect password'
I kept on trying and it said ''try again in 2 minutes'' and i did. But it said it's incorrect and i must try again in 4 minutes. I then took out the battery and put it band. And now it says '' try again in 12 312 minutes''.
Im using a Nokia Lumia 520, please help! What must i do?
Solved!
Go to Solution.

The app requires diffferent instructions to operate.
You need to double-tap the numbers. So if your PIN is 1234 you need to type 11223344.
guide for using the app http://www.afb.org/afbpress/pub.asp?DocID=aw150303
Guide for accessibility features on the phone http://www.windowsphone.com/en-US/How-to/wp7/basics/ease-of-access-on-my-phone

Speaker problem after an update to windows 8.1 on Nokia lumia 520

Similar Messages

Maybe you are looking for