** Guide to DOWNGRADE BETA 3.0 -> 2.2.X **

Discussion in 'iPhone' started by OriginalMasta, Mar 18, 2009.

  1. OriginalMasta macrumors member

    Mar 18, 2009
    How to downgrade 3.0 beta firmware to 2.X.X:

    If you have upgraded from 2.2.X to firmware beta 3.0, you are going to be expecting bugs and lag all over the place especially NOTES and MESSAGES - mms doesn't work at all on AT&T right now either. So unless you are hard core about the new API's and want to get a head start on your new 3.0 apps, I see no reason to even deploy this beta 3.0 on your iPhone over 2.2.1 which is really stable release IMO. I did notice safari in 3.0 beta being FASTER than in 2.2.1. I really want the MMS to work but it's not worth the sluggishness and a few of my paid 3rd party apps crashing in 3.0 beta.

    To downgrade, here is what you will expect to see and this is how to counter it (these steps may vary but I will explain my encounters):

    1) Doesn't matter if you have itunes 8.1 (the newest build). IF YOU GET error 1600 or error 2100; error 1600 being a good sign ;-)

    2) First thing: Get a hold of the older firmware, say build 2.2.1 (via pwnagetool - it doesn't even matter regarding the yellowsn0w unlock anymore cause your baseband is no longer
    2.28.00 if you installed 3.0 beta)

    3) Ensure iTunesHelper process is terminated. Check it in activity monitor. Kill it if it's running. You can have itunes up and running if you want doesn't matter

    4) IF YOUR PHONE IS OFF start step 4a (if it's ON, TURN IT OFF *AFTER YOU CONNECT TO YOUR COMPUTER VIA THE USB CABLE* start at step 4b):

    4a) CONNECT YOUR IPHONE via usb cable then connect to the computer. It will start up with apple logo. Let it boot then when it's completed, TURN OFF PHONE (hold on/off button at top until slide to power off is seen; then power off)

    4b) wait 5 seconds after phone is OFF. THEN HOLD DOWN HOME BUTTON and ON/OFF BUTTON at the SAME TIME. Hold for 5 seconds. Count 1 beeeep, 2 beeeep, 3 beeeep, etc.

    4c) RELEASE THE ON/OFF BUTTON and WHILE STILL HOLDING THE HOME BUTTON, count to 9 seconds. 1 beep, 2 beep, 3 beep, etc.

    4d) iPhone should remain black AND if you haven't already done so, load up iTunes. It will immediately prompt you that your iPhone needs to be restored. If this doesn't happen, simply repeat steps 4b - 4d BUT this time hold down the HOME and ON/OFF button on iPhone for TEN seconds in step 4b.

    5) When in DFU restore mode, the iPhone's screen is black. You can then click the alt/OPTION button (on your keyboard) and the restore button in iTunes bringing up a custom firmware load dialog window. Find that 2.2.X firmware you made with pwnagetool.

    6) Click OPEN in the dialog window then the firmware will load into the iPhone.

    ERRORS: If you get an error 1600, this is actually ok. Just do the following:
    * With iTunes still up (and your iPhone no longer showing up in iTunes), HOLD DOWN the HOME BUTTON AND ON/OFF BUTTON on iPhone. count to TEN. Then let go the ON/OFF BUTTON but still hold down the HOME button on the iPhone. iTunes should redect your iPhone and it's state is in RESTORE mode again.

    Let go the HOME button on iPhone after the "you need to restore your iPhone dialog box" appears. Then hold down the ALT/Option keyboard button and then click the RESTORE firmware button in itunes. Go thru the dialog screen and you should be able to load up your custom firmware 2.2.X.

    Now the above steps was what I found out after trying to downgrade and having failed 20 times in a row. Here's what I did originally:

    Alternative steps that didn't work:
    1) Put phone in DFU mode. Start up iTunes. It detected iPhone in restore mode. I tried to downgrade with ORIGINAL unmodified APPLE 2.2.1 firmware and 2.2 (after 2nd attempt) but I came across same error 1013 and error 21. It would load the firmware then crash half way giving me those iTunes errors (you can see the iPhone loading meter almost halfway full).

    2) Next I tried to use a HUB between the iPhone and the computer...but still resulted in error 1600 and sometimes error 2100. So no go on that

    3) When the original unmodified apple firmware 2.2.1 tried to load and died half way, the phone rebooted itself and went into the usb cable -> iTunes screen (which is called the RESTORE MODE - NOT DFU MODE)

    4) Then I realised that error 1600 has something to do with the DFU mode. I turned off the phone (by holding down the on/off button on iPhone while the USB->itunes screen was on the iPhone). Then I just held down the HOME and ON/OFF buttons on the iPhone for ten seconds; then i let go the ON/OFF button after ten seconds counting out loud WHILE STILL HOLDING THE HOME BUTTON DOWN. Itunes detected the iPhone again in restore mode. I alt/option clicked the restore button in itunes and loaded my custom pwned 2.2.1 and this time, it installed 100%

    I hope this will help others. So if you see error 1600, don't fret. Simply hold down the HOME button and ON/OFF button on iPhone for ten seconds then release on/off button on iPhone while still holding the HOME button - count to ten again or whenever iTunes redetects your iPhone. It should work flawlessly.

    I've tried this TWICE and it works!
  2. Tokiopop macrumors 68000


    Dec 6, 2008
    West Yorkshire, UK
    Basically a normal DFU restore to a Pwned Firmware? :p
  3. OriginalMasta thread starter macrumors member

    Mar 18, 2009
    Not really - because 3.0 firmware with itunes 8.1 doesn't allow you to downgrade. It fails half way but I guess I wasn't fully in DFU mode even though it detected the iPhone being in restore mode.

    Quite confusing but you just simply redo the DFU steps WHILE the iPhone is still connected and screen is still BLACK.
  4. PaThKu macrumors member

    Oct 28, 2007
    This works on 3G? I'm going to try this in a few, if it works, I'll let you all know.

    OP- This looks fantastic, if it works (which I believe it will!) than many many many thanks to you my good man!!! :D

    3.0 is waaaay to buggy and MMS and Group/mass texts are dead :(
  5. OriginalMasta thread starter macrumors member

    Mar 18, 2009
    I almost gave up - because I said it just won't work...just keep at the DFU mode, it will work!
  6. wil49 macrumors member

    Mar 18, 2009
    Chester, UK
    Well done, hopefully this will cut down on the threads. Maybe this could get put to the top of the forum.
  7. PaThKu macrumors member

    Oct 28, 2007
    Uggh, no 1600 or 2100 errors for me. I get 1203 and 9 (or something like that, I don't remember).

    I wish I had read the pre-install notes more closely :eek:
  8. lOUDsCREAMEr macrumors regular


    Mar 30, 2006
    Safari desert
  9. garethjs macrumors 6502a

    Nov 11, 2008
    just stick with 3.0 and wait for a new beta to be released. I'm sure Apple will be working real fast with betas. They literally have just 2 months before a final product is due. I dare say we will see another one within 2 weeks.
  10. Benjic macrumors regular

    Dec 7, 2007
    Madison, WI
    This is actually great news, I upgraded without having my UDID reg'd and now my phone is out of commission until i do this.
  11. pandemik macrumors newbie

    Mar 19, 2009
    OP, thank you for posting this!

    The problem was that my iPhone wasn't actually going into DFU, but merely restore mode. I did this on a PC (From the USB -> iTunes screen): Hold Home and Power for ten seconds and release power. Then XP detected the iPhone DFU driver (the tooltip in the bottom right came up).

    Once XP detects the DFU driver, you should be able to restore like normal. I did, and it works!

    Thanks again.
  12. Taylor C macrumors 6502a

    May 27, 2007
    I've successfully reverted to 2.2.1 with a custom firmware, but does anyone know if it's possible to get back to the stock 2.2.1 firmware? I've tried and keep getting errors.
  13. koobcamuk macrumors 68040


    Oct 23, 2006
    I also keep getting errors. Hopefully someone can solve this one...
  14. koobcamuk macrumors 68040


    Oct 23, 2006
    Didn't work for me, want to give some more advice please??! :eek:
  15. koobcamuk macrumors 68040


    Oct 23, 2006
    thank god, back to 3.0b now.

    I managed to get to pwned firmware, but I wanted official. Was a real problem though!

    Going to just sit out the betas I think :)
  16. JGrau macrumors newbie

    Apr 3, 2009
    Error 21

    It is unclear exactly what to do after encountering error 1600. Do I go back into DFU mode, or do i do something else?
  17. renewed macrumors 68040


    Mar 24, 2009
    Bemalte Blumen duften nicht.
    Just to let some of you guys know. DFU mode was disabled by Apple in the 10.5.6 Mac OSX update.

    If you have updated you are going to have to revert back to the 10.5.5 file.

    This can be done numerous ways.

    The best way to do this is to sign up free at the ADC

    Just scroll down to where it says sign up Free.

    Fill in the info. Sign into your account.

    Okay now you need to go to downloads.

    Go to the right and click Mac OSX.

    Then scroll down to IOUS build for 10.5.5 its like the 315 one.

    Download this. Unzip. Install. It will restart your comp.

    Now you can go into DFU mode properly. Pwnage will pick your iPhone up and put 2.2.1 custom on it. If you don't want custom just go to iTunes and restore it from a 2.2.1 backup after putting the custom 2.2.1 from pwnage on it.

    When you are done. Repeat but dl the 10.5.6 build and install. Comp will restart. Now you are back to normal.
  18. CuriousCat macrumors newbie

    Apr 3, 2009
    ramifications for developers

    will Apple detect a jailbroken device that is registered for development? ;)
  19. pprshell macrumors member


    Apr 5, 2009
    OMG...I worked on this for-ev-er...but after doing pretty much everything everyone posted...I Finally got it to work and re-activate itself.

    I agree with everyone, don't do anything, unless you fully understand what you are doing...lesson learned, sorry iPhone
  20. mavis macrumors 68040


    Jul 30, 2007
    Tokyo, Japan
    If so, they don't seem to care. I called AppleCare while using 3.0b2 on a previously jailbroken iPhone 3G to get it replaced under warranty. The lady knew I was using 3.0 when I gave her my serial number, but it wasn't a problem. Nor was the fact that it was previously jailbroken, apparently. Otherwise I wouldn't be sitting here looking at a shiny new iPhone. ;)

Share This Page