7 replies to this topic

[Andrew Lyle]

First let me say, this may not be the best guide or easiest method to follow, but it works and I have tested it twice already.

If you have upgraded to iPhone firmware 3.0 and are having problems and want to switch back to 2.2.1 you can follow this guide.

What you will need:
iPhone firmware 2.0.2
iPhone firmware 2.2.1 (or desired firmware)
iPhone 1st gen
WinPwn 2.5 BETA
QuickPwn 2.2.5
iTunes (I used 8.2)
Bootloader v3.9
Bootloader v4.6

1) Launch WinPwn and find the firmware 2.0.2 (that's why you needed this, it only supports 2.0, 2.0.1 and 2.0.2). Load 2.0.2 and follow the steps. You will come to a point where WinPwn asks to put your phone into DFU mode, follow the steps and this is where your phone MUST show a white screen after it is done.

2) Once in DFU mode, WinPwn will no longer work (maybe crash) but that is fine, load up iTunes and it will show your phone is in recovery mode

3) In iTunes, Hold Shift + click on Restore and select Firmware 2.2.1, your phone should now load up and begin to recover.

4) Once your phone is restored, it will still be unactivated and you won't be able to use it, but load up QuickPwn and find your BL-39.bin and BL-46.bin files and continue.
Note: This is where nothing happened for me, and I had to stay on this screen and restart my phone (Home + Power) until it restarted and I received an error in QuickPwn, After accepting the error this is where the guide started. You may need to restart your phone 1-2 times for this to happen, but once it does, QuickPwn will start the guide to jailbreak the device.

5) You should now have a loaded 2.2.1 firmware on the device and jailbroken.

If you have problems, just contact me and I will try my best to help you rollback your 1st gen iPhone to 2.2.1. You will lose all your information on the phone, but hopefully you have a backup saved in iTunes! I did a backup to my phone and all my contacts, pictures and notes were placed back on. I am sure there are a few steps I could of skipped, but I really tried to find a work around for this, and this is the only method I could get to work!

Hope this helps!

[thefarewellnote]

You should also note that once you upgrade to 3.0 it will update your baseband, which can not be reverted back when you downgrade. This may cause some problems.

It did for me. Often times i found that my iPhone would lose its data connection and only a reboot would bring it back. I was able to make calls still but emails/internet would not work until I rebooted the phone

[+rajputwarrior]

thefarewellnote, on Jun 18 2009, 07:24, said:

You should also note that once you upgrade to 3.0 it will update your baseband, which can not be reverted back when you downgrade. This may cause some problems.

It did for me. Often times i found that my iPhone would lose its data connection and only a reboot would bring it back. I was able to make calls still but emails/internet would not work until I rebooted the phone

there are ways, at least from 2.2.1 to 2.2 in terms of baseband version. I don't know if that same method works for 3.0. And even if you did, there is a unlock tool coming out tomorrow that would fix that issue anyways.

[KeR]

So why downgrade again?

[Shaun]

Why install Windows 7 on 266MHz PC....to see if you can and let others know it can be done. lylesback2 is even good enough to provide a guide.

[Andrew Lyle]

KeR, on Jun 19 2009, 10:11, said:

So why downgrade again?

Because there is still no unlock / jailbreak (as of 10:15am EST) for the iPhone. and during my "upgrade" from 2.2.1 to 3.0, I bricked my iPhone.. twice.

And also, because I can

[X82]

Upgraded to 3.0. Found It was locked.
Shift clicked restore in itunes, pointed it to 2.2 firmware. It done its thing.
Used Quickpwn.
Done.

[Andrew Lyle]

NORR, on Jun 19 2009, 10:22, said:

Upgraded to 3.0. Found It was locked.
Shift clicked restore in itunes, pointed it to 2.2 firmware. It done its thing.
Used Quickpwn.
Done.

Really? You got very lucky than. Mine kept crashing and giving me 1601 errors or said the iPhone could not be restored
It always failed for me, but glad to see that worked out for you