Welcome

Here you will find poetry, opinion and prose mixed together in roughly equal measure. Add one man available from specialist suppliers only. Stick everything into a blender for five minutes. Stir gently with a wooden spoon, then pour slowly into tall glasses with crushed ice.

No cherries. No little parasols. No curly straws. Let the drink speak for itself.

Image representing iPhone as depicted in Crunc...

Image via CrunchBase

The latest OS update 3.1 released last week is proving to be a disastrous upgrade for many iPhone owners, myself included. Problems include huge delays in the iPhone responding to touch input and sometimes a failure to respond altogether. There are frequent random crashes and complete shut-downs. Battery life is eaten up even when the device is not being used for calls or data, with or without Bluetooth and Location Services being turned off. Icons on the screen sometimes fly apart, like someone dropped a virtual bomb in their midst, only to then pop back into position. It’s even stupidly slow when trying to access contacts, or calendar, or when wanting to make a call. Even connecting to a network, 3G or Wi-Fi, takes a while.

I’ve tried hard resets. I’ve tried setting up the iPhone as new instead of restoring my data from backup after the upgrade. I’ve tried having no applications on it other than those that are installed by default. I’ve gone through a checking process, adding apps to the device one by one in an attempt to find out if any of them are causing memory leaks and instability. The bottom line is, for many people 3.1 is a shitty upgrade that trashes iPhones indiscriminately and unforgivably. So here’s how to get back to OS 3.0.1…

Don’t expect Apple to apologise for pushing this garbage out. All you can do is rollback from 3.1 to 3.0.1. If—and only if–you’ve got a 3G or original iPhone, this is moderately difficult, actually scarier to read through than it is to do. Apple has, in infinite wisdom, made it near enough impossible to fully downgrade the 3GS model. The fucksters.

Download links for the 3.0.1 software can be found here. Making a backup of your iPhone using iTunes is pointless because you need to do a complete wipe and start from fresh, and the 3.o.1 software won’t allow for anything post-3.1 to be put back under its auspices. Any attempt to restore from a 3.1 backup to a 3.0.1 iPhone will fail.

So. Connect your iPhone 3G or original iPhone to iTunes first of all, and then,

1. Switch of your iPhone and put it in DFU mode by clicking the Home + Power On buttons for 10 seconds exactly.
2. Release the power button and continue to click on Home.
3. iTunes will say it’s detected an iPhone in Recovery Mode and tell you that you need to restore it. Click on “OK”.
4. Now press and hold down the ALT key on keyboard and click on Restore button (Mac). Do both at the same time.

OR

Press and hold down the SHIFT key and click on the Restore button (Windows).

A window will open so that you can select the firmware you want to use instead of the 3.1 upgrade (at which point you can let go of the ALT or SHIFT keys). It doesn’t have to be 3.0.1, but that upgrade didn’t get the deluge of angry responses from end users that 3.1 has had in just a few days.
5. You’ll get an error message at the end of the restore, probably 1015. Ignore it. Under Windows you then need to run quickpwn for Windows and select your device and run through the first 3 or so prompts until your iPhone resets (NOTE ADDED 25.09.09: you are not jailbreaking your iPhone with this procedure—IF IT COMPLAINS IT DOESN’T SUPPORT 3.0.1 OR 3.0, YOU’VE GONE TOO FAR DOWN THE ROAD! FOR JAILBREAKING THIS VERSION OF PWNAGE WON’T WORK WITH 3.1 iPHONES—AND THIS IS NOT JAILBREAKING!). For OSX on the Mac, you need to download iRecovery.

UPDATE 25.09.09: I’ve found a link for a version of iRecovery for Windows but, not being a Windows user, I can’t vouch for it or say it’s to be used with that OS. If anyone checks it out, please share your findings in the comments below to help others. I also found this page with advice on how to use iRecovery for Windows, and suggest questions it get posted there.

OSX only instructions from here on…

6. Extract iRecovery to your Desktop. In Terminal run these commands:

cd ~/Desktop
chmod 777 libusb-0.1.4.dylib
chmod 777 iRecovery

7. Copy libusb-0.1.4.dylib to /usr/local/lib.
8. Run the following commands in Terminal:

defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder
cd ~/Desktop
iRecovery -s

You may need to use the sudo prefix to the iRecovery command to authorise it to run. Or, much easier, I found that you can just drag the Recovery file onto an open Terminal window—but remember to add the -s. You’ll know when iRecovery is running successfully because a modest stream of data appears but if nothing happens, run the command again)

9.  Run command:

fsboot

(I had to do this two or three times, and you’ll know it’s worked when your iPhone reboots and is recognised as a blank iPhone that isn’t running OS 3.1–hurrah!)

If the iPhone remains screwy, just run through all the above steps again. This method does work, I can assure you, I’ve used it myself. Remember, don’t try to restore from backup afterwards.

10. When done, in Terminal you need to run the following commands:

defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder

And now you should be back to iPhone OS 3.0.1 and, like me, making a firm resolution to wait at least seven days after an Apple software update is released before installing it, and not even then without first checking out responses to that update posted in the Apple ‘support’ (I use the term loosely) forums.

Expect either 3.1.1 or 3.2 to be available soon, as Steve Jobs was probably flogging his developers and senior managers over the weekend.

Reblog this post [with Zemanta]

Post to Twitter Post to Yahoo Buzz Post to Facebook Post to StumbleUpon

No related posts.

View Comments to “How to rollback iPhone software 3.1 to 3.0.1”

  1. alexavery says:

    Hey man. Thanks for the post. I followed all the steps listed, however the Pwnage software only supports downgrades to 2.0 software. :( You cant use it to downgrade to 3.0.1 using the steps listed above.

    Any other ideas on getting past the 1015 error?

  2. Hi there. Is this on Windows? You get past the 1015 error by ignoring it on the Mac and running those Terminal commands. There's a video here that explains how to do the downgrade under Windows.

    If it's a 3GS phone then it's much more difficult, as explained above.

    If you've found the Pwnage software supports a downgrade to 2.0 only, that's weird. You could perhaps allow that to happen, and then use shift+click to tell iTunes to restore the iPhone AFTER doing that to 3.0 or 3.0.1, by pointing it to wherever you've got the 3.0 or 3.0.1 software on your hard drive. It's more steps but you will be upgrading from 2.0 so iTunes will happily install as normal. It's downgrading it doesn't like doing. Having told it where to find and which software version to use, it won't need further intervention to successfully upgrade a 2.0 iPhone software install but when you're done it will, of course, go online and find 3.1 and offer to upgrade again. Just don't say yes to that upgrade!

    I hope this helps.

  3. I forgot to add, the 1015 error you can interpret as a complaint from iTunes that you've downgraded and not upgraded. Seeing the 1015 error means you're successfully doing what you set out to do, with just a few more steps to go.

    If you are finding the pwnage tool wants to install 2.0, I'd go for that and then upgrade from the 3.0 or 3.0.1 software on your hard drive.

  4. marc says:

    Hi, I am using windows. I downloaded the 3.01 software to computer. I reset the phone and depressed shift + click while clicking on icon in itunes. Nothing happened and no window opened for me to choose old OS. Please advise

  5. Hi Marc! You don't reset your iPhone, you need to force it to enter DFU mode before you attempt anything else. As I said above, plug your iPhone in via USB and immediately press the Home button and the Power button at the same time. Keep them depressed for 10 seconds, then release the Power button but keep holding down the Home button. iTunes should, if you've managed to enter DFU mode, tell you it has detected an iPhone in Recovery Mode. Okay that, then when you see the screen in iTunes (the same area you use to tick and untick playlists, apps etc) with the Restore button on there, press Shift and click the Restore button in iTunes, which should then open up a window allowing you to locate and use the software update you've downloaded rather than the 3.1 update.

    I wasn't especially clear there, and am amending the post accordingly, so thank you for highlighting a need for clarity on that point.

  6. Hi Marc! You don't reset your iPhone, you need to force it to enter DFU mode before you attempt anything else. As I said above, plug your iPhone in via USB and immediately press the Home button and the Power button at the same time. Keep them depressed for 10 seconds, then release the Power button but keep holding down the Home button. iTunes should, if you've managed to enter DFU mode, tell you it has detected an iPhone in Recovery Mode. Okay that, then when you see the screen in iTunes (the same area you use to tick and untick playlists, apps etc) with the Restore button on there, press Shift and click the Restore button in iTunes, which should then open up a window allowing you to locate and use the software update you've downloaded rather than the 3.1 update.

    I wasn't especially clear there, and am amending the post accordingly, so thank you for highlighting a need for clarity on that point.

  7. marc says:

    spicy
    I got through to the end extracted QP , went through prompts and then it tells me it does not support the firmware 3.01 found on your links page . please help , getting frustrated. I know we are close.

  8. marc says:

    Spicy

    IT WORKED!! Thank you. FYI The QP never got past the 1st page as the file was not compatible. go figure. Syncing now, works great..

  9. Oh, fantastic. Pleased to read that. You don't run pwnage all the way through, just the first couple of steps I think, it's to get the iPhone to reset properly but if it's done it without, that's great. I'm holding back now until the next update has been out a while to see what responses to that are before I take the plunge.

  10. Here's a link for 3GS owners who want to try to downgrade but apparently it's much harder and from what I can gather depends on whether the iPhone has previously been jailbroken or not – whereas the above procedure does NOT jailbreak your iPhone original or 3G model.

  11. Daniel says:

    Thanks a million for this – it worked PERFECTLY and i have re-enabled tethering, etc, all good. thanks so much.
    I know only a little about unix but others might not so i thought i'd mention, im running 10.6.1 and i didn't have a folder called /usr/local/lib, i copied it to /usr/lib instead and it all seems fine.
    Thanks again – you're a legend!

  12. Really glad it worked for you. The kill command for the Finder is, I think – I'm no Unix expert myself – all about revealing/hiding the hidden folders and files including usr and its sub-directories. Normally on my Macs you can't see the usr folder at all.

  13. Daniel says:

    oooh right, i just use the Go to FOlder option in finder – shift+cmd+G

  14. Ah, great. Thanks for the tip! I've found my iPhone still a bit flaky from time to time post-procedure. Whatever 3.1 did, it was nasty. I've had to run iRecovery again today (JUST that, and the fsboot command, none of the other stuff) when I hooked up my iPhone to iTunes before iTunes would recognise it and sync. Didn't lose any data on my iPhone, it was all still there.

    Really, really angry at Apple right now. Especially as the company continues to say bugger all about the issues people are having.

  15. RCProjects says:

    Fantastic – thanks for the clear instructions and links. I didn't seem to need the quickpwn to finish the process – other than following the first instruction to reset the phone. (Hold both buttons for 15 secs, and then the power button for 2 secs.)

  16. Dave says:

    I was actually able to restore 3.01 without using the quickpwn tool, but your steps were invaluable in getting me there. After a little trial and error, I found that after a reset and recovery, when faced with the choice of setting the iphone up as a new iphone or restoring from backup, I could restore to an old backup that I'd made in August '09. I had the choice of restoring it or restoring the backup that was made right after I upgraded to 3.1. I restored the old backup and that put me back at 3.01. I was then able to go back into iTunes and restore the ATT_US.ipcc file that gave me tethering.

  17. The 3GS is much harder to do anything approaching a rollback because Apple has made it so, the company doesn't want people using earlier softwares (of course, the bargain ought to be, that's fine, just make sure the software updates don't trash people's iPhones!). I've come across some jailbreaking sites that offer up methods of ditching 3.1 on the 3GS but as I don't have a jailbroken iPhone and never have had, and have a 3G not a 3GS, I can only suggest you search Google with 'rollback iPhone 3GS 3.1' and similar key phrases. Sorry.

  18. Gaurav says:

    thanks a lot for the instructions. u rule!!!
    it realllllllly sux to have installed 3.1 without knowing how bad it could **** up my life!
    i depend a lot on the iPhone for my office emails…..
    here is what i have:
    iPhone 3G – was on 3.0.1 before i upgraded it to 3.1
    Max OS – Leopard
    iTunes 9

    i tried to do the whole thing as explained – worked perfect and i had rolled back to 3.0.1 w/o any issues and even set up office email w/o a problem.

    now, after all this, my phone died last night as i could not charge it the whole day.
    today mrng – HOLY MOLY, i try to charge the phone n see the same 'USB and iTunes logo' that i saw when the phone is in DFU mode and i thought im goin to have to do the whole process over again and so i did!

    all fine again!
    BUT, this time, i tried to restart and DAMN, it again goes in the DFU mode – but coz this time i had read the comments and figured that spicycauldron also faced the similar prob – so this time i only run iRecovery and fsboot steps and all's again.

    but now, i'm afraid if i ever run into the same prob, im going to have to have my macbook to get it out of the DFU mode, or for tht matter some other comp with internet to download files.

    bottomline – after downgrading to 3.0.1 there is still some finishing touches that need to be done to fix it permanently (so that the phone doesnt go into DFU mode when restarted) – can some1 help me with that :-S
    thanks in anticipation :)
    cheers!

    • It might – and I stress might, I don’t know – be something to do with your mobile phone carrier file that iTunes updates every once in a while when your carrier makes changes to it. But it’s becoming increasingly clear, for many of us 3.1 is the worst update ever from Apple, for any device, in terms of its impact. We should be able to choose what OS version we want to run, damn it, without jumping through hoops. eh?

      What I can’t figure out is, my iPhone’s not entirely the same as it was pre-3.1, either, having gone the 3.1 route and then rolled back. It’s functional now, which is more than it was with 3.1 but it’s hard to pin down what’s changed… It’s like 3.1 really, really upset it! I think there’s something amiss with iTunes 9 as well, come to think of it – it certainly doesn’t always recognise my iPhone when I dock it, or says it can’t read it but then does just fine. I’m wondering how many of us are using iTunes 9 and having post-rollback hiccups? I mean, they were released at the same time, iTunes 9 and iPhone OS 3.1… What if both are basically completely screwy updates?

  19. MaggieAco says:

    I have a 3GS originally running on firmware 3.0 but had to restore due to accidently deleting some Cydia files. To make a long story short. I first restored doing the windows 64 shift key and restored using my own firmware 3.0. But still had issues with Cydia. So I ended upgrading to 3.1.1 But had a hard time downgrading even though my ECID/SHSH was on file in Cydia's server and I changed the iTunes host and everything. I kept getting that 1015 error message everytime, once it was almost downgraded. I did this for two days now without any luck until I accidenlty googled “need to restore to 3.1.1″ Which I meant 3.0.1 since my 3.0 downgrade wasn't working. And with your wonderful suggestion of QuickPwn I found hope. So I followed your directions and like someone else mentioned in comments QuickPwn doesn't work with anything higher than 2.2 so I kept putting my regular 3.0.ipsw then I tried hopelessly with 3G firmware 2.2 and it was rejected. But the MARVELOUS thing was that after I excited out of QuickPwn a bit frustrated and sad my iPhone 3GS rebooted and came back to life on 3.0 firmware and I was able to jailbreak and all. YOU HAVE HELPED ME THIS NIGHT & I DO THANK YOU VERY MUCH!!! THANKS AGAIN.

    OMG THANKS SOOOOOO MUCHHHHHHHHH! IF I WOULD HAVE LISTEN TO YOUR WARNING & NOT TAKEN A CHANCE, WOW. “Any attempt to restore from a 3.1 backup to a 3.0.1 iPhone will fail” BUT FOR SOME REASON IT WORKED FOR ME. MAYBE BECAUSE I DOWNGRADED TO 3.0 NOT 3.0.1 MAYBE?

    THANKSSSSSSSSSSSSSSSSSSS

  20. You've jailbroken your iPhone, that'll be why. You can't put a backup from 3.1 onto a locked iPhone running 3.0.1 or earlier. You'll get a message popping up in iTunes telling you why, that the backup is incompatible with the version of the iPhone software, words to that effect.

  21. Pither says:

    Thanks for the guidance. Everything works as described (one small nit: you might need to do ./iRecovery -s).

    One remaining problem. Now, if I power my iPhone all the way off and then turn it back on, it still thinks it's in recovery mode. I then need to do the iRecovery again. and again. and again. every time i power off. Bummer. Anyone else have this problem?

  22. I've had it a few times, by no means all the time. I just don't understand why, unless the 3.1 software update changed something in the actual phone and not just the OS. It's a bloody disaster, 3.1. I still can't believe we haven't had an apology from Apple and a promise to find fixes quickly. Something this big, this devastating… Early this year, of course, we had extensions of MobileMe subscriptions for a similarly massive cock-up.

    Thanks for the additional advice, that's great!

  23. Gaurav says:

    yes Pither, i have the same problem, read my post above….
    do post it here if you find a solution.
    cheers!

  24. Steve Kim says:

    Fantastic. Thanks for this article! The 3.1 coma was SO frustrating!!!!

  25. Emiliano says:

    thank you so much! it worked like a charm with quickPwn… it's hard to say but apple sucks right now :-/

  26. Neags23 says:

    Wow, so I guess I'm kind of an idiot, but I didn't expect this to completely wipe out my iPhone. I ran a restore from before I upgraded to 3.1, and all of my apps and music are gone.

    Getting the music back is just a nusiance, but losing all my apps is huge. There's no way I'll remember all the apps I had.

    I guess I would've done it anyway to get tethering back, but a disclaimer would've been nice…

  27. You can't lose apps from your iPhone forever because you will have them in iTunes under a section marked, don't be surprised, 'Applications' – and so you can sync them back. You don't need to remember. The advice given does NOT completely wipe out an iPhone if by 'wipe out' you mean destroy. Doing any rollback from 3.1 necessitates a need to restore after from a pre-3.1 backup in iTunes. Inevitably. That sticks your pre-3.1 stuff, music, apps, etc back on the iPhone. If you only have a 3.1 backup and rollback, your only option is to set up as a new iPhone and reload via iTunes.

  28. Neags23 says:

    I didn't ever sync my apps with iTunes. I just used the iphone to download. So my apps weren't in the applications tab.

    I rolled back from 3.1 to 3.0.1, then did a restore of my backup of 3.0.1 from just before I 'upgraded' to 3.1. After the restore, I had all of my phone settings, contacts, text messages, etc…. but no music or apps.

    But you're right, I'd rather have to deal with adding the music and apps back than stick with 3.1.

  29. How did you get your music on there? Did you purchase it on the iPhone? iTunes has many, many failings as a piece of bloatware but one thing you can be sure of, regularly hooking your iPhone up to it and allowing iTunes to backup and keep copies of your playlists, songs, apps etc makes nothing but sense.

    I do hope you're able to quickly restore your apps. If you paid for any, you should be able to find out from Apple what they were, and re-download them if you ask them.

  30. Pither says:

    Just following up my comment from earlier….
    Now, for some mysterious reason, when I power down and back up, everything is happy. I'm still running 3.0.1 and no longer in recovery mode.
    Thanks again, your spiciness, for giving us this info. I promise to be more careful accepting upgrades in the future!

  31. TXCobra1 says:

    Spicy, need help. I was able to put my phone in DFU mode and do the reset, but for some reason quickpwn will not work. It doesn't give me the option to choose which phone model I am using, but it does correctly display a 3G logo on the screen (which is what I have). When I browse to the spot that I have downloaded the 3.0 firmware to, it gives me the following error:

    The IPSW file you selected does not match any firmware version QuickPwn supports. Either the IPSW file is corrupted or the firmware version is unsupported.

    Incidently, I also could not load 3.0.1 during the restore, it told me it was not a good file. I have tried this 3 times and I think I am following your instructions exactly! Please help.

  32. TXCobra1 says:

    OK, I found another version of the firmware from another site and was able to get 3.0.1 to load, but Quickpwn still will not work…same error. Any ideas?

  33. You're not using quickpwn from start to finish, just the first few steps until the iPhone restarts. If you've managed to get 3.0.1 onto the iPhone, you're almost there. I just did a search and found a link on this page for the latest version of pwnage. But don't go the whole way. You're rolling back, not jailbreaking, you see! What happens without pwnage – does your iPhone stay in recovery mode even after you've successfully rolled back using iTunes? Pwnage is used to do the same as Terminal on the Mac for this rollback, which is to kind of kickstart the iPhone back into your familiar screen and functions.

  34. Hi. Yep. I discovered something very similar. First few days I was occasionally finding my iPhone went into recovery mode if I switched it off and then back on, but now it's settled down and that's no longer happening. And yes, I've learned to wait a while before applying updates as well. We're all pretty much in the same boat there!

  35. If it said it wasn't a good file, it might have been corrupted during download. I had that happen and it took me several attempts before I checked, and noticed the file size wasn't quite right. So I redownloaded the 3.0.1 update and watched to make sure I got all of it.

  36. TXCobra1 says:

    Thanks for the response. I knew from what you had posted that I wouldn't go the whole way, but I couldnt even get it to go through step 1. Yes what happens before pwnage is I get the usb logo, then when I manually reset the phone I get what looks to be a wiped, new phone with 3.0.1 but then I can't restore my Itunes profile. I suppose I could create a new profile in itunes, what are your thoughts on that? Also, the link you posted on the latest version of pwnage says it is for Mac only…since I am a windows user, is there another option? Thanks again for all this help.

  37. They're working on a version for Windows, and from past evidence it shouldn't take them long, that's all I know. But I also included a link in the article (see the updated bits, marked) to the version of iRecovery for Windows, no idea how that works but presume it does command line DOS stuff like the Mac version uses Terminal.

  38. Gaurav says:

    All!!!!!
    i have found a resolution to my problem and would like to share with y'all.
    after doing what is mentioned in the post i could downgrade from 3.1 to 3.0.1
    BUT, everytime i have to restart my phone it would get into DFU mode.
    in order to fix that follow the below:
    when you do ./iRecovery -s instead of typing just fsboot, type the below two commands first.
    1. setenv auto-boot true
    2. saveenv

    it will look like below:

    $ sudo ./iRecovery -s
    Password:
    iRecovery – Recovery Utility for 0×1281 and WTF.
    by wEsTbAeR– and Tom3q

    Got USB

    =======================================
    ::
    :: iBoot for n82ap, Copyright 2009, Apple Inc.
    ::
    :: BUILD_TAG: iBoot-596.24
    ::
    :: BUILD_STYLE: RELEASE
    ::
    :: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000002B2AC047D0D IBFL:01 SRNM:[5K9209WNY7K]
    ::
    =======================================

    [FTL:MSG] Apple NAND Driver (AND) RO
    [NAND] Device ID 0xb655d7ec
    [NAND] BANKS_TOTAL 4
    [NAND] BLOCKS_PER_BANK 8192
    [NAND] PAGES_PER_BANK 1048576
    [NAND] SECTORS_PER_PAGE 8
    [NAND] BYTES_PER_SPARE 128
    [FTL:MSG] FIL_Init [OK]
    [FTL:MSG] BUF_Init [OK]
    [FTL:MSG] FPart Init [OK]
    read old style signature 0×43303035 (line:301)
    [FTL:MSG] VFL Register [OK]
    [FTL:MSG] VFL Init [OK]
    [FTL:MSG] VFL_Open [OK]
    [FTL:MSG] FTL Register [OK]
    [FTL:MSG] FTL_Open [OK]
    Boot Failure Count: 0 Panic Fail Count: 0
    Entering recovery mode, starting command prompt
    ] (Recovery) iPhone$ setenv auto-boot true
    (Recovery) iPhone$ saveenv
    (Recovery) iPhone$ fsboot
    HFSInitPartition: 0x180a36c0
    (Recovery) iPhone$

    CHEERS!!!!

    PS – i hope y'all got the MMS thingie done too….
    :)
    keep rocking!

  39. Hi Gaurav. Thanks for that, much appreciated. What is it that those commands in your 1 and 2 steps actually do? I'm assuming you have some idea?

  40. Gaurav says:

    Well, the iRecovery let's u work on ur iPhone os.

    command 1 = set some variable/config to start the os automatically without going to dfu mode.
    Command 2 = save the setting on iphone.
    fsboot = start up the os.

  41. Great, thanks for the info!

  42. heymikeyc says:

    Where can I download iRecovery from? Sorry for the dumb question but I don't was to just download it from a random site I find from a google search.

  43. Check out the section in my article above where I've added UPDATE 25.09.09. A link to iRecovery for Windows is provided, and another link directing you to a page that tells you how to use iRecovery for Windows. Neither page linked to is anything to do with me, the links are just provided to help.

  44. Chris says:

    I'm stuck at the pwnage not supporting 3.0.1 and not being able to restore to anything other than whats on the phone(so no 2.0 either) I was rally happy to see the uddated pwnage file only to find that its mac only……damnit

  45. Chris says:

    and also its now stuck on the plug into itunes screen and itunes is not picking anything up when i plug it in…please help

  46. cartoonboy says:

    For All using Windows.

    I found V3.1 prevented me using my Optus tethering profile even though it was still installed.

    So I did this…

    Download V2.0 and install using iTunes (the steps above) then using using the shift+restore from iTunes update to V3.0.1

    So now I've reversed everything I'm back to V3.0.1 which is perfect, synced my iphone with iTunes and got all my songs/apps back and able to use Optus tethering profile again :)

    The only thing I had to set up again (so far) are my email accounts which is a minor drama compared to what the “update” button did for me a week or so ago !!

    Gotta thank spicycauldron because without your website I was totally stuffed !!

    THANK YOU MATE !!

  47. Thank you for such great and helpful feedback! I still can't believe we haven't yet seen Apple release a new update to fix the horrors of 3.1 but then, it has been busy spreading the iPhone to other networks this week. I can only assume if I were to go buy a brand-new 3GS with 3.1 installed I'd have no problems at all but Apple needs to either release separate updates for 3GS and pre-3GS iPhones, or release a bloody fix and make sure all future updates work on all models!

  48. Try iRecovery for Windows. There's a link added to the article a few days ago.

  49. You can also try cartoonboy's suggestion below.

  50. Name says:

    Tried this and itunes contacts apple at the restore stage and refuses to restore the phone ..
    unplugged the internet so they coundn't and it errored out .
    Stuck !!

  51. When you say you tried this, do you mean you followed the instructions and read through the many comments – because the feedback people have left is important, as many have found alternative ways and workarounds, and many report success either with the method as described in the blog article or by tweaking it for their own circumstances.

  52. When you say you tried this, do you mean you followed the instructions and read through the many comments – because the feedback people have left is important, as many have found alternative ways and workarounds, and many report success either with the method as described in the blog article or by tweaking it for their own circumstances.

  53. Name says:

    tried multiple times to run iRecovery command. Does not work. MAC OS 10.5 either get the message that irecovery does not exist or :

    dyld: Library not loaded: /usr/local/lib/libusb-0.1.4.dylib
    Referenced from: /Users/jryan2/Desktop/iRecovery
    Reason: no suitable image found. Did find:
    /usr/local/lib/libusb-0.1.4.dylib: stat() failed with errno=20
    /usr/local/lib/libusb-0.1.4.dylib: stat() failed with errno=20
    Trace/BPT trap

  54. That's because that file – the library not loaded – needs to be put in the directory it specifies it is missing from. iRecovery DOES work, and reliably but it needs that file which you should find in the package you downloaded that contained iRecovery.

  55. I closed comments on this entry but since its last plugin update Disqus has reopened them without my input and refuses to close them again despite telling me it has when I tick the relevant box in WP admin.

    I've contacted Disqus support to find a fix.

  56. aronin says:

    Thanks… this worked…and as marc said above, you don't require Quickpwn. Once the restore is complete and iTunes is done giving the warnings… just switch off the phone, disconnect it, switch on and reconnect. It should work.

  57. aronin says:

    Thanks… this worked…and as marc said above, you don't require Quickpwn. Once the restore is complete and iTunes is done giving the warnings… just switch off the phone, disconnect it, switch on and reconnect. It should work.

blog comments powered by Disqus

Follow

Facebook Likes

Time Machine

Translate this Page

© 2010 The Spicy CauldronSuffusion WordPress theme by Sayontan Sinha

Switch to our mobile site