Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Downgrade iPhone 3G 3.0 to 2.2.1

sleeptodream said:
after some screwing around it seems to be restoring in itunes just fine :eek:

Yep its restoring. Note that this was with a custom firmware i made in pwnagetool. But I didnt include cydia or any other jailbreak stuff with it. since I dont want a jailbreak.
After this im going to restore it again to the normal firmware.
Click to expand...

This happened to me! It was really scary. I downloaded 3.0 beta legally and then it said that it didnt verify my Developer account somehow. Then it said I had to register my iPhone with the IDP. And I couldn't because it couldn't activate because it didnt verify me. So I was lost trying to go back to 2.2.1 but it didnt let me. And now I think it restored in iTunes to 2.2.1 from 3.0. I'm scared to see the outcome though. :/
 
Having messed with 3.0 (yes I'm developing apps, I wasn't just dicking around) I decided I needed 2.2.1 back for the stability (because of my 'proper' job as a journo).

Followed some of the guides on here and had serious issues getting my new MacBook to actually complete the setup back on 2.2.1, so here's how I did it in the end - and I DID NOT need to jailbreak the phone:

1 - Set the phone into DFU mode.
2 - Restore the phone on my Mac using the official 2.2.1 software - get an error message from iTunes. The iPhone was now 'stuck' on the USB cable + iTunes icon screen.
3 - Boot camp into Windows - run QuickPwn and plug in the iPhone.
4 - Just having QuickPwn open seemed to kick the iPhone past the initial screen. I could then use the iPhone as normal. I DID NOT need to use QuickPwn to actually jailbreak or modify the phone in ANY WAY. Just having it detect the iPhone kicked the iPhone back into a workable state.
5 - Boot back into OSX and sync as before.

So I've got 2.2.1 back without jailbreaking at all - the only thing different is that the baseband is the newer version, but so far I've had no issues with that.

Hope that helps someone!

-Leemo
 
Leemo said:
Having messed with 3.0 (yes I'm developing apps, I wasn't just dicking around) I decided I needed 2.2.1 back for the stability (because of my 'proper' job as a journo).

Followed some of the guides on here and had serious issues getting my new MacBook to actually complete the setup back on 2.2.1, so here's how I did it in the end - and I DID NOT need to jailbreak the phone:

1 - Set the phone into DFU mode.
2 - Restore the phone on my Mac using the official 2.2.1 software - get an error message from iTunes. The iPhone was now 'stuck' on the USB cable + iTunes icon screen.
3 - Boot camp into Windows - run QuickPwn and plug in the iPhone.
4 - Just having QuickPwn open seemed to kick the iPhone past the initial screen. I could then use the iPhone as normal. I DID NOT need to use QuickPwn to actually jailbreak or modify the phone in ANY WAY. Just having it detect the iPhone kicked the iPhone back into a workable state.
5 - Boot back into OSX and sync as before.

So I've got 2.2.1 back without jailbreaking at all - the only thing different is that the baseband is the newer version, but so far I've had no issues with that.

Hope that helps someone!

-Leemo
Click to expand...

Why didn't you just use QuickPwn for the Mac?
 
The instructions in post #57 worked fine for me to revert back to the stock 2.2.1 firmware, except I had to go to a windows PC after iTunes downgraded my firmware because QuickPwn did not recognize the iPhone on my mac. I used VMWare Fusion. :)

I'd like to reiterate that QuickPwn doesn't do anything like jailbreaking your phone or installing anything on it in this case, it just recognizes your phone and that is enough to make your phone come back to life once 2.2.1 is installed.

EDIT:
I'd like to add that I am also a paid developer, but I am also a poor grad student who can only afford one iPhone. I use my phone for development, and as my primary communications device. I was probably dumb to have upgraded to the beta firmware but people like me can't resist trying something new (I'm studying physics and I love messing with things). I went back to 2.2.1 because 3.0 was a bit too slow and buggy for me (though usable). I didn't like the long delays when loading certain preferences or finding directions in maps. I also didn't like the long startup times of 3.0. I might try the next revision of 3.0 that Apple releases though. I did read the Apple note saying you could not downgrade once upgrading to 3.0 and I thought I'd just live with it until I saw this thread.
 
So somehow my phone got stuck in recovery mode, not DFU. When I try to restore to 3.0 in recovery mode, I get error 1013. Any way to go from restore to DFU? Or any ideas on how to get past the 1013 error code to get out of restore mode to get into DFU mode?
 
After the 1013 error, you run Quickpwn to tap on it, and it will then be ok. You don't have to do anything other than let quickpwn identify it, and after that iTunes will see it just fine.

That's how it worked for me. You may need to use a windows machine running quickpwn to do this (or a Mac with bootcamp).
 
danimal99 said:
After the 1013 error, you run Quickpwn to tap on it, and it will then be ok. You don't have to do anything other than let quickpwn identify it, and after that iTunes will see it just fine.

That's how it worked for me. You may need to use a windows machine running quickpwn to do this (or a Mac with bootcamp).
Click to expand...

I thought you had to be in DFU mode for this to work. I am stuck in restore mode.
 
Not sure why people are getting all philosophical about phone upgrades, having the latest and greatest, etc. Don't act like you've never wanted something. Apple makes great stuff---hard to wait sometimes. We're human, we all make mistakes. Maybe someone upgraded not knowing what they were getting into and simply wants a working phone again. There isn't much wrong with that.
 
In the end,....

is there a definitive fix that seems to work for all or many? I personally have not been able to get anything to work. I know I'm in over my head but how discouraging. I've never been stuck like this before.

All the suggestions make sense but QuickPwn does not see my phone is connected, even though iTunes does. So I can never get past that. Also, I think I'm in recovery mode and can not get out of it.

SOS to anyone out there who can help simplify this mess i've gotten into. I just want my life back.....

Thanks in advance.

DDR
 
mocque said:
mac 10.5.6 does not recognozes iphone in DFU mode ( you should read more in this forum)
Click to expand...

Hah! I should read more in this forum? I probably read more than all of you. I know that there is a DFU issue in 10.5.6, but there are 2 easy fixes for this.

Fix #1: Install the USB drivers from 10.5.5 and then use DFU mode
Fix #2: Plug it into a USB hub.

Yes, I read the forums. I figured everyone knew about those 2 fixes.
 
Like other people i was dumb enough to try to upgrade to 3.0 without reading the fine print
so i ran quickpwn as instructed by the first post and now i can use everything except the phone. is there a way to bring back the phone features, and start using it like an iphone again?
 
domwindle said:
Like other people i was dumb enough to try to upgrade to 3.0 without reading the fine print
so i ran quickpwn as instructed by the first post and now i can use everything except the phone. is there a way to bring back the phone features, and start using it like an iphone again?
Click to expand...

dfu to pwnage 2.2.1. i cant explain anymore.
 
3.0 Beta is misleading even to iPhone developers

lftrghtparadigm said:
Please read the documentation available to you inside the iPhone Dev Center, about an inch away from the download link (says "read before installing"). There is clearest, most concise answer to this question available there.
Click to expand...

This is posted on Apple Developer Forum and many developers agree.
--------------------------
On Apple's part, this wasn't really fair. Apple is fully aware that many developers are using their primary devices to develop on. In fact Apple itself touts the fact that the little guy can play too (you know - the guy developing on his own phone). Therefore, it was reasonable to expect all basic functionality to work in this beta, while perhaps their would be a few (or even many) kinks to work out related to the new APIs, etc.

However, this release was clearly NOT beta level. I tried to keep a list of bugs related just to the email to submit, but after finding more than 30 during the day, and realizing that in fact almost nothing works reliably, it was just to overwhelming. In fact I have to completely power off and power back on my device nearly every time I get two new message alerts. It's now about a 4-5 minute process that makes the old days of "soft-resetting" windows mobile every day or two seem like heaven, and has effectively made my primary device useless until.... ????

It's GREAT that you rolled out new features and want us to beta, and many will happily do so (while developing using the new APIs for when the release goes public). But it's not fair to not provide a rollback method AND not meet a basic level of reliability for core features. Yes it's supposed to be beta software, and thus not perfect. But, for at least anything related to the mail application, it's not really beta - it's hardly more than a shell for where things will be and will function correctly some day. And since some of those bugs make the entire phone unusable, nobody could in good conscious consider this a fair Beta. Or at least not while at the same time not providing a rollback method, especially knowing you're doing vast harm to the usability of the primary devices of so many of your developers.
 
axbycz said:
This is posted on Apple Developer Forum and many developers agree.
--------------------------
On Apple's part, this wasn't really fair. Apple is fully aware that many developers are using their primary devices to develop on. In fact Apple itself touts the fact that the little guy can play too (you know - the guy developing on his own phone). Therefore, it was reasonable to expect all basic functionality to work in this beta, while perhaps their would be a few (or even many) kinks to work out related to the new APIs, etc.

However, this release was clearly NOT beta level. I tried to keep a list of bugs related just to the email to submit, but after finding more than 30 during the day, and realizing that in fact almost nothing works reliably, it was just to overwhelming. In fact I have to completely power off and power back on my device nearly every time I get two new message alerts. It's now about a 4-5 minute process that makes the old days of "soft-resetting" windows mobile every day or two seem like heaven, and has effectively made my primary device useless until.... ????

It's GREAT that you rolled out new features and want us to beta, and many will happily do so (while developing using the new APIs for when the release goes public). But it's not fair to not provide a rollback method AND not meet a basic level of reliability for core features. Yes it's supposed to be beta software, and thus not perfect. But, for at least anything related to the mail application, it's not really beta - it's hardly more than a shell for where things will be and will function correctly some day. And since some of those bugs make the entire phone unusable, nobody could in good conscious consider this a fair Beta. Or at least not while at the same time not providing a rollback method, especially knowing you're doing vast harm to the usability of the primary devices of so many of your developers.
Click to expand...

Another developer says
-----------------------------------------------
Well said. I'm very happy that Apple is allowing us to develop for 3.0 now and put it on our development phones but not if I can't restore from a buggy OS. I think it would be more fair to call it a pre-beta and as such, as you've stated, so we MUST be able to remove it.

I'm totally in the single, poor developer boat. I'm a microISV with next to no capitol (compared to even a small development company) so I only have the one phone that's also my main phone. That's just my economic situation right now and it's bound to get worse before it gets better so bricking my only phone isn't an option. And I'm certainly not going to run questionable/illegal software to circumvent something Apple doesn't want us to do. If Apples says if I do X I can't do Y; then I just won't do X.

I want to develop for 3.0 and put it on my phone but as it is I going to wait for a more stable, usable, reversible option is made available.

In the future you MUST offer downgrades from Beta or I just can't install them. As it is I see developers waiting for 3.1 to come out before they even start on 3.0. Why waste all that development time when nothing will work anyway? I would really hate to see this become like the Microsoft world where no one writes to the latest libraries because they are so buggy you'll just end up re-writing your code anyway when they fix them.

So since no one wants to turn their very expensive and useful iPhone in to a virtually useless iCrash we can end up in a little game of catch-22. No developers will write to the beta versions because they are too buggy so we don't find all the bugs until well after the library has been released because not enough people were using it so they remain buggy so no one uses them so they don't improve so no one uses them and so on and so on...
 
Little guy

Go here and watch their presentation. In the beginning of the video, it features a guy with one phone who develops an amazing game. Imagine that he has to get ready for iphone 3.0 so he downloads 3.0 beta and it renders his phone unusable. He knows going in that he can't put 2.2.1 back but he does not expect a 3.0 beta is not a fair beta but just a shell with no actual features.

Hate to say it but no need for Apple to walk the path of Windows Vista.
 
lftrghtparadigm said:
High horse??? This having to hack/downgrade from 3.0 to 2.2.1 is absolute nonsense! This shouldn't even be a topic, because there shouldn't be a flood of people with no idea what their doing and too much throw-away money upgrading to "permanent testing status in 3.0 beta".
Click to expand...

Do you people have this sort of closed mind? I mean really, you sound like a bunch of children.

If you need warranty work on your iPhone, you better bet your butt that you will need to downgrade to 2.2.1, they won't even take it in with 3.0 on it, EVEN if you paid the 99.00 FEE to have the privilege. Sounds like a scam to me, but I really enjoy having the option to downgrade to support two conflicting policies Apple seems to put in place.
 
Apparently downgrading an iPod touch from 3.0 is a breeze. All I did was click restore and I was preparing for the infamous error and not a single error occured. It restored, flashed the "connect to iTunes" screen for a second, then it said "slide to unlock". I was like... huh. Pretty sweet. iPod touch users... if you want to revert back to 2.2.1, it's a piece of cake.

Note: I didn't go into DFU mode.
 
TheSpaz said:
Apparently downgrading an iPod touch from 3.0 is a breeze. All I did was click restore and I was preparing for the infamous error and not a single error occured. It restored, flashed the "connect to iTunes" screen for a second, then it said "slide to unlock". I was like... huh. Pretty sweet. iPod touch users... if you want to revert back to 2.2.1, it's a piece of cake.

Note: I didn't go into DFU mode.
Click to expand...
That's because there's no baseband to upgrade, therefore no mismatch when downgrading.
 
mavis said:
That's because there's no baseband to upgrade, therefore no mismatch when downgrading.
Click to expand...

I spoke too soon I guess. I'm having trouble syncing my iPod touch now. iTunes says "Verifying iPod touch" in the iTunes window... I've never seen that message before. iTunes said there was 14.18GB available on my iPod touch as free space, but when I try to copy 13.84GB of data to it, it says there's not enough room on the iPod... what? All this data fits on my 16GB iPhone, so why wouldn't the 16GB iPod touch hold it?

I'm restoring again as I write this... hopefully this fixes it.

Anyone else get the "Verifying iPod touch" message? This is not the message that appears when you're installing the firmware... this appears in the main iTunes window when I go to plug in my iPod touch... where the song timeline is.

Edit: Simply restoring again solved the problem. It no longer tries to verify the iPod touch and now it's syncing all my data normally... wow, that was weird. If you run into this problem, just re-restore again.
 
I wonder if Apple will let us devs download updated beta builds along the way to the official 3.0 release. I sure hope so. I'll probably try the next build if that was the case. Downgrading wasn't so bad in the end and I'm back to the speedy 2.2.1 OS with no problems.
 
Ok, please help someone...

So, I put it in DFU mode (um, am not clear on this, but I hold down power and menu, wait till it turns off, and then keep holding menu button until I see ipod cable and itunes logo... right?)

Then I plug it into my mac itunes, map to the original 2.2.1 sw, and as it is preparing it for restore, I get an error 21.

Please could someone tell me what I'm doing wrong??

Thanks!
 
macmadandproud said:
Ok, please help someone...

So, I put it in DFU mode (um, am not clear on this, but I hold down power and menu, wait till it turns off, and then keep holding menu button until I see ipod cable and itunes logo... right?)

Then I plug it into my mac itunes, map to the original 2.2.1 sw, and as it is preparing it for restore, I get an error 21.

Please could someone tell me what I'm doing wrong??

Thanks!
Click to expand...
That is not DFU, that is recovery. The phone shows a black screen (appears to be off) when you are in DFU.

After you turn your phone off, wait 5 seconds, then hold down home and power for 10 seconds. Let go of power and keep holding home for 10 seconds and iTunes will pop up saying it's detected it. Do a restore, and then you'll get a 1013 error. Then it varies from here, but what I did was bootcamp into Windows and then ran QuickPwn and it told me to put it in DFU I believe... I don't really remember, but after you get the 1013 error you are on 2.2.1. I think I put it into DFU with Quickpwn (but didn't Jailbreak it) and then switched back to OS X and iTunes recognized it and was fine.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back