Problem after failed update

Hi everybody,
today after a failed update my Z3 Dual D6633 doesn't restart.
The message 'The software update failed. Make sure that your phone is connected to the computer and try again.' blinking on my screen.
The issue is that PC companion doesn't find my phone. I've tried all my USB ports but still doesn't work.
Have you any suggestion ?
Thank you
Solved!
Go to Solution.

You may need to perform a software repair using PC Companion.The process will erase all internal memory.You might need to charge your device for about 1-2 hours before so the device has at least 60% battery.
Make sure the device is not connected to computer or laptop and turned off (sometimes you have to press power button and volume up until the device vibrates 3 times or on some devices you have to press the small button near the SIM tray or on the back of the device).
Open PC companion->support zone->phone/tablet software update->repair my phone/tablet blue highlighted.Follow the steps given,do not connect your phone until prompted to press volume down while plugging USB cable. If PC companion does not start the repair process, you might need to run it in compatibility mode with Windows 7 (in some cases XP).
All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

Similar Messages

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

My Sony Xperia Z won't start /turn on after failed update attempt

Try this connect your phone to the wall charger > press andhold power & volume up > let it charge for 1 or 2 hours > after 2 hours > repair your phone with SUS Update Service (SUS) http://www.sonymobile.com/gb/tools/update-service/ http://www-support-downloads.sonymobile.com/Software%20Downloads/Update_Service_Setup-2.11.12.5.exe PC Companion (PCC) Bridge (for Mac) Alternatives on How to backup Xperias http://talk.sonymobile.com/thread/36355

A similar problem to the other posters, my Sony Xperia Z won't start after a failed update attempt. Following the support suggestions on the Sony website (http://www.sonymobile.com/sg/support/faq/w8-walkman-phone/update-software/software-update-failed-ps101/) failed. Solutions posted on this forum thread (http://talk.sonymobile.com/t5/Xperia-Z-ZL-ZR/My-Sony-Xperia-Z-won-t-start-turn-on-after-failed-update-attempt/m-p/401787#M20133) have also failed. When I plug the phone into the wall charger, the LED comes on red, the SONY logo appears on my screen, followed by a message indicating that "The Software update failed. Make sure that your phone is connected to the computer and try again.", and then the phone turns itself off. The cycle repeats itself with no indication that my phone's actually being charged. Since it is unable to charge, plugging the phone into my computer does not trigger the update process to start, so I can't "try again", as the message so helpfully suggests. The computer also does not recognise my phone as being connected despite following the PC Companion's instructions to 1) unplug the device, 2) remove and replace the battery (which I can't do, because the battery is built in), and 3) turn it back on (which, again, I can't do, because the phone won't charge in the first place), before 4) plugging it back into the computer. Please help... Thank you.

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

HT1925 After failed update of itunes yesterday, now will not run with error message "MSVCR80.dll can't be found, APSDaemon.exe not running". Windows 7.

After failed update of itunes yesterday, now will not run with error message "MSVCR80.dll not found" APSDaemon.exe will not run. itunes will not now run.

Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
Remove all of these items in the following order:
iTunes
Apple Software Update
Apple Mobile Device Support (if this won't uninstall move on to the next item)
Bonjour
Apple Application Support
Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
Please note:
Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
tt2

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

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>

I-tunes does not recognise ipad to restore after failed update to ios 5

i-tunes does not recognise ipad to restore after failed update to ios 5. Connected i-pad to update to new ios 5. Back-upp went fine but update failed and now i-tunes does not recognise the devise and i-pad will not work so I have no known way to restore.

Copied from that article.....
4. Continue holding the Home button until you see the "Connect to iTunes" screen. When this screen appears you can release the Home button:
Are you releasing the home button when you see the connect to iTunes screen? Does iTunes start on its own? If it doesn't - start iTunes yourself.
Also copied from the article.....
5. If necessary, open iTunes. You should see the following "recovery mode" alert:

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.

Start up problems after security update 2014-002

Hi, after this update sometimes my Mac does not start up like it should: the Dock is not appearing and the screen is flashing between fully grey and thenormal background. The only cure seems to be to restant a second or third time. Already resetten PRAM, used disk utility (no problems) and repaired permissions. Does anyone else has encountered this problem? Thanks

I have always had good luck with DiskWarrior. I've had serious issues and DiskWarrior has always come thru .
Are you nervous because you have never used DW before, or are you afraid it will hose your system?
By your report, it kinda sounds as if your hard drive has either failed or on it's last leg.
I'm guessing you had issues with the drive before installing the update and you did not know it. Updates tend to point out problems in a big way sometimes.
I run repairs on my hard drive before installing any updates.
I don't remember, does Jaguar have S.M.A.R.T. status in Disk utility? If so, what does it say about your drive?
Dale

Blocked after failed update

Hello, Hope you are doing well,
5 or 6 days back i shut down my windows 8 laptop and it started updating. the update went on for about 8 to 10 hours and the machine restarted. on restart it said failed to update and it 'restored.'
the issue is that after this failed update i see a watermark on the left bottom corner that says Activate Windows. i ignored it for a few days, even went to 'PC settings' from the start menu but did not find a way to 'Activate' windows. I hope you are aware
that the windows 8 series isn't very user friendly when it comes to settings menu. so i went through a couple of threads and learnt that my key was blocked.
Help restore or update windows to an active version.
P.S.: I have brought a genuine windows 8 with the laptop from an HP certified dealer in Mumbai. the key was accepted by Microsoft on various occasions until this happened.
also the system was infected by a trojan and malware for about a month. which was removed by running bit-defender. Need any more info? please solve this issue.

Please repost your problem to the more appropriate Windows 8 Community Forums here...
http://answers.microsoft.com/en-us/windows/forum/windows_8?tab=Threads
Noel Paton | Nil Carborundum Illegitemi
CrashFixPC |
The Three-toed Sloth
No - I do not work for Microsoft, or any of its contractors.

IMessage problems after iOS6 update

Hi All,
Is anyone getting similar problems to this after iOS6 updates?
My iPad is used on 2 wifi networks, my home network and work wifi, I pick the pad up on a morning, shove it in my bag, go to work and pick up the wifi there, carry on as normal, repeat in reverse when heading in the opposite direction.
On iOS5, my iMessages would simply carry on the conversation when rejoining either network *there is no 3g connection on this ipad*
Since updating, I leave for home, get to work and iMessage refuses to resume, messages stick at about 90% sent, then fail, I head home , rejoin the home network and boom, it just picks up where it left off
When at work, occasionally it might start working after 10 minutes or so, but today i've been sat about 5 hours so far, no dice
I have tried just about every combination of restarts, resets, updates I can think of, including, changing the DNS on my device to the same one I use at home *8.8.8.8* , shutting iMessage down, renewing the DHCP lease, Hard resets, soft resets , forget wifi network, restore network setting you name itI've tried it
Under iOS5 I had used the device for months without doing so much as a power down and not had one single 'not delivered' failure on an iMessage, since iOS6 I've probably had abotut 50% service from this.
As far as I know, nothing has changed on either wifi networks, everything else works fine on the works network, browings, itunes, app store, skype etc etc.
I'm at a loss as to what to do next, and yes, I've also done a full device restore as well for good measure, with a iCloud back up, again, it restored, went to messages and it just sat there doing nothing until I got home , where the messages just sent first go.
Massively frustrated in what I can only see as something that's been introduced as a result of this iOS6 upgrade.

I may have found my own answer... it seems that anything less than 3 bars of wifi signal after rejoining a network and the message wont send, I switched my device off, moved closer to the wifi router, tricky as it's in another building, rebooted, managed to get two bars of wifi, still wouldn't send, moved even closer to the router manged to just get 3 bars and pow, the message sent right away!
Moved away back to my normal desk at work, signal dropped to 2/1 bars of wifi, however now, messages continue to send now.
Clearly when I'm at home I'm only ever a few feet away from my wifi router and always have solid 3 bars of signal, not the case at work.
However, this still only appears to be something that's been introduced at the iOS6 update as this was never an issues prior to this, but has been an issue right from day one after updating!

Keyboard and Contact Problems after Iphone Update to 4.2.1

Hey Guys, after i updated my brand new Iphone 4 I got a few Problems with my contacts... some Contacts were deleted (only the numbers, not the names). And I can not write ß, é, è and so on...
All Settings set to German. But these letters are not available while holding e or s...
Can somebody help me?

if you dont have your contacts backed up on a computer then they very well could be gone
this wont fix your contact issue but this is what I would try for your other issue
to be honest these are the solutions that may or may not work..
first thing I would try is rebooting the phone by holding the sleep/wake button and home button for 15 seconds until you see the white apple logo
if that doesn't work I would restore from backup and if that doesn't work I would restore as new if all else fails take it to your closest apple store they may replace the phone for a working one..

IPhone 4 in recovery mode after failed update with most recent software (3/25/13), I only have the past 30 days worth of photos and my contacts in iCloud, how do I get the rest of my pictures off of my phone? I have read the apple article already.

Basically headline says it all, my phone is in recovery mode following a failed update through the phone and I want all my photos back. I have already read the "iOS: Unable to Update or Restore" and it indicates that when restoring through iTunes, you lose all data on the phone. I have checked my iCloud (I am a Windows7 user so uploading does not happen automatically, as I unfortunately just figured out) and it only will upload my past 30 days of photos and contacts, inline with what I've read about the cloud only storing 30 days of your past data. I really would like to get all of my photos off of my phone, I had photostream activated and most were in that stream. Is there anything I can do? I don't know what operating system is on there currently, but I have always updated my phone succesfully until today when this happened, so I'm assuming whatever is most up to date until today is the OS it has. Thank you!

When your phone is in recovery mode, it's like it crashed. The only way that you can get it out of recovery mode is by restoring, and this erases all your data as well.
You can believe what you wish by "reading all over the internet". This is Apple's technical support forum. We do know what we're talking about.
since you have very important photos on your phone, why haven't you been importing them to your computer as soon as possible after taking them? This is how the phone is meant to be used. Keeping critical data on only a device which can be easily stolen, dropped and broken is just plain foolish. Also, did you not back up your phone (as you should be doing with any computer) before attempting any operating system update? As you've now just painfully learned, updates do not always go as planned.
I'm sorry for your data loss, but let this be a very important lesson. BTW, when was the last time you backed up your computer? I'm sure you have important data on your computer. Hard drives WILL fail.

Problem after failed update

Similar Messages

Maybe you are looking for