Redsn0w 0.9.8b7 Released - Fixes Minor Issues

[Joshua Tucker]

Using redsn0w on the iOS 5 beta is done at your own risk. Note the consequences and possible issues you may run in to by using redsnow on the iOS 5 beta firmware.

If you recall about a week ago, the iPhone Dev-Team released redsn0w 0.9.8b6 to jailbreak iOS 5 beta 6. Although no new beta for iOS 5 has been noted or released, the iPhone Dev-Team has updated redsn0w again to fix a few issues, according to MuscleNerd (@MuscleNerd)'s recent tweet.



Here are the details to the updated version:

Update #7: Apple updated the iPad1 iOS5b6 IPSW without changing its version number or filename, so we’re releasing redsn0w 0.9.8b7 to handle both the original and changed IPSW. We’ve also added explicit support for a tethered 4.3.5/4.2.10 jailbreak (instead of pointing at the 4.3.4/4.2.9 IPSWs) and fixed a 4.2.10 problem.

Get the scoop:

• redsn0w 0.9.8b7 can handle both the old and new iOS beta 6 IPSW files for the iPad 1 since Apple updated it without changing the version number or filename. Basically it means you can point redsn0w at either one of those IPSW files when jailbreaking or rebooting tethered
• This new version adds full support for a tethered 4.3.5/4.2.10 jailbreak. In the previous version, you had to point redsn0w to the 4.3.4/4.2.9 IPSW file. With this version, you can point it directly at the 4.3.5/4.2.10 IPSW file
• Also, a 4.2.10 problem was fixed

Although this update may not be applicable for you to use now (as you might be already jailbroken on iOS 5 beta 6, 4.3.5, or 4.2.10 without issues), whenever needing to re-jailbreak or reboot tethered for any of these tethered firmwares, use the new updated version. Just remember that you can point the 4.3.5/4.2.10 IPSW when jailbreaking or rebooting tethered on those firmwares. If you are experiencing issues on any of the firmwares supported in this update (especially 4.2.10 users), try out the new version of redsn0w and see if that helps out.

Below are the respective download links:

redsn0w 0.9.8b7 for Mac
redsn0w 0.9.8b7 for Windows

Source(s): MuscleNerd, iPhone Dev-Team Blog

[brianiino]

Patiently waiting for untethered jailbreak.

[Peligro0]

Patiently waiting for untethered jailbreak.

This

[Adayday]

Patiently waiting for untethered jailbreak.

I wouldnt count on an untethered jailbreak seeing as iOS 5 is just around the corner and that it would be a waste of an exploit if they used it on iOS 4. Also, Apple is making it harder and harder to jailbreak and it will be even harder in ios 5 so I wouldnt count on an untether in the near future but that is just my speculation

[iFiend]

Patiently waiting for untethered jailbreak.

Unfortunately you'll be waiting awhile. They aren't going to release an untethered JB until iOS 5 drops. Even then, it will be awhile, like when jailbreakme 2.0 was released about a month after iOS 4.

[bigbaba]

Patiently waiting for untethered jailbreak.

Lol when are you going to start complaining about the iOS 6 jailbreak? Next week?

[Joshua Tucker]

Unfortunately you'll be waiting awhile. They aren't going to release an untethered JB until iOS 5 drops. Even then, it will be awhile, like when jailbreakme 2.0 was released about a month after iOS 4.

Not necessarily - the teams already have the process in the works. It probably won't be as long as you think.

[iFiend]

I wouldnt count on an untethered jailbreak seeing as iOS 5 is just around the corner and that it would be a waste of an exploit if they used it on iOS 4. Also, Apple is making it harder and harder to jailbreak and it will be even harder in ios 5 so I wouldnt count on an untether in the near future but that is just my speculation

This

Not necessarily - the teams already have the process in the works. It probably won't be as long as you think.

Perhaps, yes, but the same thing can be said about iOS 4. I am almost positive they had a "process in the works" then, but the bottom line is it still took a month.

I am just preparing people for the wait, including myself. I would love to be wrong though

[Joshua Tucker]

This



Perhaps, yes, but the same thing can be said about iOS 4. I am almost positive they had a "process in the works" then, but the bottom line is it still took a month.

I am just preparing people for the wait, including myself. I would love to be wrong though

Definitely, it's good to put things in perspective however they have a better head start this time.

[iFiend]

Definitely, it's good to put things in perspective however they have a better head start this time.

How can you say that with such confidence? Not questioning you just to be an ***, I'm genuinely curious

[Joshua Tucker]

How can you say that with such confidence? Not questioning you just to be an ***, I'm genuinely curious

I know and speak with people from both the Chronic and iPhone-Dev Team. Mostly Chronic. I'm not even 100% certain myself but I can be somewhat sure that they have things in process.

[confucious]

The recent untethers have been done by iOn1c and they have patched his exploits - I really don't see any sign of another untether soon.

While I have the greatest of respect for the Chronic team I doubt if they can provide an untether or a JB for the iP5 - assuming it's running an A5 chip.

I look forward to them proving me wrong.

[bigbaba]

Correct me if I'm wrong but doesn't anyone find it suspicious Apple hasn't closed the exploit used to jailbreak iOS 4 in the iOS 5 betas? I hate to say it but I think Apple is holding off on closing this exploit until the final release so the dev team has to start from scratch taking away their apparent head start.

[confucious]

The JB exploit can't be closed by FW - it takes a HW change. A tethered JB will always be available to those that have it now. The untether has been blocked and new HW will block the JB.

[zplit]

Lol when are you going to start complaining about the iOS 6 jailbreak? Next week?

Lol

[Tucnepo]

Chill dude. Its not the end of the world.