With the first beta of iPhone OS 4.0 released just over a week ago, I think the hot topic topic for many has been the question of jailbreak. While there has not been any doubts that it would be jailbroken in the end (MuscleNerd showed off a jailbreak roughly a day after the initial release), I don’t think anyone actually expected a generally available jailbreak any time before the final summer release.
Guess what, there is one already! The Dev-Team have released a BETA version of their redsn0w 0.9.5 tool capable of jailbreaking an iPhone 3G. At the moment the package works on the following:
iPhone 3G only (for now)
Mac OSX only (for now)
the 4.0beta1 FW only (for now)
I have to make a special emphasis: the jailbreak is aimed at iPhone developers only and REQUIRES a properly-registered developer UDID with Apple to get past the activation screen. For the same reasons it does not support Windows, unlock or hacktivation.
What do we, common users, care? Actually – a lot! The generally available jailbreak means developers can start adapting their jailbroken apps for the new OS immediately (rather than waiting for the official summer release) and should considerably shorten the time we will have to wait to get them fully working on our brand new JB OS 4.0 iPhones!
You can find the full Dev-Team explanation after the gap, as well as instructions on what to do in case you upgraded to OS 4.0 beta 01 already and wish to downgrade.
This is a beta release of redsn0w targeted at developers of jailbroken apps. It uses the same pwnage2 DFU-mode exploit that we’ve been using since the 2.x days. Nothing new is revealed to Apple, and it’s not applicable to the iPad. Don’t go near it if you use yellowsn0w, ultrasn0w, or blacksn0w.
Please not that this beta is not meant for the average end-user. There are many things “broken” with jailbroken apps in the 4.0beta1 environment right now (that’s the real reason we showed “Veency” in the 4.0 jailbreak demo video last week, instead of say MobileTerminal.app, which is broken!). This beta redsn0w allows the developers behind those jailbroken apps (like MobileTerminal.app!) to fix their software before the general public gets iphoneOS 4.0.
Because it’s meant for JB app developers, this beta redsn0w does not perform hactivation. You’ll need a properly-registered developer UDID with Apple to get past the activation screen. For similar reasons, there is no Windows version of this beta redsn0w (since apps are developed on MacOSX). Please don’t pirate Apple software.
Anyone other than developers of jailbroken apps porting their software to 4.0beta1 should still be using our previously-released redsn0ws for 3.0 through 3.1.3
This BETA release supports:
- iPhone 3G only (for now)
- Mac OSX only (for now)
- the 4.0beta1 FW only (for now)
YOU SHOULD STAY CLEAR OF THIS BETA SOFTWARE IF YOU RELY ON A CARRIER UNLOCK. That’s because the beta redsn0w works only if your device has already been upgraded to the stock 4.0beta1 IPSW from Apple, which contains a baseband update. If you installed that IPSW, you’ve already lost the carrier unlock until the next planned release of ultrasn0w and blacksn0w.
If you’re a developer for jailbroken apps and you’ve already updated your iPhone3G to iPhone1,2_4.0_8A230m_Restore.ipsw, the next steps are:
- Make sure you’ve already activated your iPhone3G with iTunes and your developer UDID
- Launch the beta redsn0w 0.9.5
- Select your stock iPhone1,2_4.0_8A230m_Restore.ipsw file (you’ve already used this to update your iPhone3G to 4.0beta1)
- Select “Install Cydia” and click “Next”. Use DFU mode to install the jailbreak.
- When your iPhone3G comes back up, you’ll notice Cydia has a blank white icon (we told you many things were broken right now!) You’ll also notice Cydia has no sources. Go to the Sources panel and add this repo: http://apt.saurik.com/cydia-3.7 (be sure you have a carrier or wifi signal first!). When Cydia restarts, you should see its real logo now, and the standard sources should be ready to use.
If you find that you want to back down from the 4.0beta1 until it’s more useable, here’s how to do it.
- Restore to official 3.1.2 or 3.1.3. Your baseband won’t be downgraded, so you’ll get error 1015 at the end of the restore.
- Use rslite or irecovery to get past error 1015. Using rslite, you’d do:% rslite rslite v0.2 - by the iPhone Dev Team, 2009. --THIS IS AN UNSUPPORTED TOOL-- Connecting... [Recovery] setenv auto-boot true [Recovery] saveenv [Recovery] reboot
Your baseband will still be at 05.13 from the stock 4.0beta1, but FW 3.1.2 and 3.1.3 will work fine with it. The current carrier unlocks will not.
Please send any feedback to MuscleNerd (either gmail or iphone-dev.org).