Posts tagged Apple

Apple Seeds iOS 5 Beta 3; Jailbreak Confirmed Using RedSn0w 0.9.8b1

0

Apple recently started seeing iOS 5 beta 3 and iTunes 10.5 beta 3 for developers today. The following devices are supported for iOS 5 beta 3:

  • iPad 2
  • iPad 2 Wi-Fi + 3G (GSM)
  • iPad 2 Wi-Fi + 3G (CDMA)
  • iPad
  • iPhone 4 (GSM)
  • iPhone 4 (CDMA)
  • iPhone 3GS
  • iPod touch (4th generation)
  • iPod touch (3rd generation)

As you may have already figured out, in order to sync iOS 5 beta 3 devices with your computer, iTunes 10.5 beta 3 has to be installed. You also have to be a registered developer to access these files from the Apple iOS Developer Program website: Apple iOS Developer Program

The changelog on iOS 5 beta 3 is as follows:

Notes and Known Issues

The following issues relate to using the 5.0 SDK to develop code.

Accounts

  • When creating an iCloud account you can use any Apple ID provided it is a full email address and not a MobileMe account. If you have a MobileMe account, you can copy data from that account to an iCloud account to use during testing. You can find more information on iCloud at: http://developer.apple.com/icloud
  • When setting up an iCloud or MobileMe account using the setup assistant and leaving Find My iPhone on, it might actually turn Find my iPhone off after the setup. Please verify in Settings/Mail, Contacts, Calendar/YourAccount that Find my iPhone is toggled On after leaving the setup assistant.
  • There is a problem finding a device using Find My iPhone on the MobileMe website (www.me.com) when switching from iCloud back to MobileMe. To workaround this issue:
    • On the device go to Settings->Mail, Contacts, Calendar-><your_account>@me.com and Toggle Find My iPhone off and back on. Now the device should show up on MobileMe website.
  • It is recommended that you disable Bookmarks on multiple accounts. If they are enabled, the results might be undefined.
  • NEW: In this beta the option of “Choosing a security question” is not working during an iCloud account setup.

AirPlay

  • Starting in iOS 5, video content in applications and websites are AirPlay-enabled by default.
  • iOS 5 supports AirPlay of video via AV Foundation.
  • FIXED: The Apple TV screen saver may degrade mirroring performance over AirPlay. The screen saver can be disabled in Apple TV settings.

Apple TV

  • Apple TV Software beta enables users to mirror the contents of an iPad 2 to an Apple TV (2nd generation) using AirPlay. This beta software also enables Photo Stream on Apple TV so users can access photos stored in iCloud. Apple TV Software beta is being provided to test the latest AirPlay functionality with your iOS 5 apps and web sites. If you wish to install Apple TV Software beta on your device, you must first register your device UDID in the iOS Developer Program Portal.

Audio

  • Using voice chat in iOS 5 requires setting the kAudioSessionMode_VoiceChat mode on the Audio Session, or setting the AVAudioSessionModeVoiceChat mode on the AVAudioSession object.

CalDav

  • FIXED: After creating a recurring event locally on the device, the device stops syncing after hitting an error on merge. Removing and re-adding the account acts as a workaround for this.

Calendar

  • All MobileMe calendars were duplicated after turning calendar syncing off and back on.
  • If you launch or manually refresh Calendars on an iPad, your calendars might disappear and you will have to tap “Show All Calendars” to display them again.
  • NEW: Restoring from a Seed 1 backup or earlier will cause MobileMe/iCloud calendars not to sync. Subscribed calendars will show up in Calendars but none of your event calendars will appear in MobileCal. To workaround the problem please remove and re-add the account.

GameKit

  • Match data for turn based matches is currently limited to 4 KB of data.

GameCenter

  • If you have an existing Game Center account which has not yet gone through the first-time Game Center flow in iOS 5, you will encounter a crash when signing into a game’s login alert directly. The workaround for this is to launch Game Center to complete the first-time flow.

iBooks

  • iBooks 1.2.2 may fail to display some text or images in books. Please update to iBooks 1.3 in the App Store.

iCloud Backup

  • As this is beta software, it is recommended that you do not use the iCloud services to store any critical data or information. If you enable iCloud Backup, automatic backup with iTunes when syncing will be disabled. We suggest you also manually back up your device with iTunes.
  • In the iOS 5 beta, support for data protection in iCloud Backup is unavailable. Apps that have protected files will not have any of their data or metadata backed up as a result.
  • After restoring, you may not be able to back up again because the device still thinks it’s restoring. To workaround this issue try syncing apps or media that are missing form iTunes or try deleting your iCloud account and adding it back.
  • If you delete your backup, the feature will be disabled but settings may still indicate that it is enabled and you will have to toggle the BackUp to Cloud switch in Settings.
  • For compatibility reasons, this version of the iOS 5 beta requires that all files be backed up again, instead of only those files that have changed since your last backup. This may cause a warning that your account is over quota. In case the warning occurs, you can delete your oldest backup to free up space and then initiate a backup.

iCloud Storage

  • During the iOS 5 beta period, any documents stored on the servers might be purged periodically before GM. Therefore, it is highly recommended that you do not store any critical documents or information on the servers.
  • If your application is using the NSMetadataQuery class, you must set a predicate, even though the predicate itself is ignored.
  • The Foundation framework doesn’t include the team ID when looking for an app’s mobile documents container. The Team ID must be included at the beginning of the identifier string passed to theURLForUbiquityContainerIdentifier: method.
  • In this beta, the setSortDescriptors: method of NSMetadataQuery is not supported.
  • In this beta, if you want to use iCloud, you have to manually specify various container identifiers (your application’s Display set) within an Entitlements file for both of your Mac OS X and iOS projects.
  • There are issues using the Cloud Storage document API in conjunction with protected data which can lead to data corruption.
  • In this beta, document-based applications cannot always detect when files change, move, or are deleted out from underneath them.
  • NEW: In this beta, file presenters (objects that adopt the NSFilePresenter protocol) do not receive some of the messages that they’re supposed to receive, especially:
    • presentedItemDidChange
    • presentedSubitemDidAppearAtURL:
    • presentedSubitemDidChangeAtURL:

    You can workaround this by implementing the relinquishPresentedItemToWriter: method and checking to see if the writer actually wrote when your file presenter reacquires. You can also use FSEvents to observe file system changes

  • In this beta, messages about changes to files in a directory are not getting delivered to objects that adopt the NSFilePresenter protocol.
  • While reporting a bug related to the iCloud storage interfaces, please include the logs collected during your debugging session. To generate these logs, you must install a special debug profile on your device.The debug profile can be obtained from http://connect.apple.com. This profile enables the generation of debug logs that are needed to diagnose any problems using iCloud storage. The instructions to collect the logs are:
    1. Install the profile. (The easiest way to do this is to mail it to yourself and open the attachment on their device.)
    2. Reproduce the bug.
    3. Sync with iTunes to pull the logs off your device.
    4. Attach the logs to your bug report. You can find the logs in ~/Library/Logs/CrashReporter/MobileDevice/DeviceName/DiagnosticLogs.

    These logs can grow large very quickly, so you should remove the profile after you have reproduced the problem and pulled the logs for the bug report.

iMessage

  • NEW: iMessage beta 3 will be unable to communicate with iMessage users on beta 1. It works between beta 3 and beta 2.
  • NEW: Modal alerts don’t appear for iMessages.

iTunes

  • The version of iTunes that comes with beta 3 cannot sync devices that have the beta 2 software installed. To avoid this problem, do the following:
    1. Sync any devices that have beta 2 installed to the version of iTunes that came with beta 2.
    2. Upgrade iTunes to the version that comes with beta 3.
    3. Connect the device and install the beta 3 software. (Understand that you might see a failure to sync error when you first connect the device.)
    4. After installing the beta 3 software, restore from your the backup you made in step 1.
  • Videos purchased from the iTunes Store do not play on a 2nd generation AppleTV over AirPlay with iTunes 10.5.

MMS

  • Sending an MMS of large videos does not work.

Photo Adjustments

  • If you apply red-eye adjustments in iOS, and import your image into the iPhoto seed build, the red-eye adjustments will not appear on that image in iPhoto. As a result, subsequent syncing of your image back to the iOS device from iPhoto will not show the red-eye adjustments.

Reminders

FIXED: The Reminders application does not send notifications for reminders that are based upon the entry (and/or exit) of a location if there is no date associated with the reminder.

Settings

  • The “Back Up Now” button is enabled without the backup data class being enabled for the account.
  • FIXED: If you bring up the keyboard of the terms in Settings->General->Software Update, you cannot dismiss it. You have to force quit Settings to get out.
  • NEW: In this beta FaceTime icon is missing in Settings on the iPhones.

Simulator

  • NEW: Location services are not functional in iOS 4.3 simulator running on Mac OS 10.7 with Xcode 4.2.

Springboard

  • Push and local notifications for apps appear in the new Notification Center in iOS 5. Notification Center displays notifications that are considered “unread”. In order to accommodate push and local notifications that have no “unread” status, developers can use their application badge count to trigger a clearing of notifications from Notification Center. When an application clears its badge count (by setting it to zero), iOS 5 will clear its notifications from Notification Center.

Twitter

  • NEW: When tweeting your location from Safari and exiting before the location can be established, the location arrow will stay in the status bar. The arrow can be removed by killing Safari from the task switcher.

UI Automation

  • NEW: In iOS 5 beta 3, the first execution of a script after a reboot or erase install will likely fail. Subsequent attempts should succeed until the device is rebooted again.
  • The play and record buttons in the Automation instrument script editor may not work properly after targeting an application that was launched by a trace session and has ended. They may also not work if you target an application that was suspended. If you run into this problem and it persists, you may need to close and reopen the trace document to get back into a functional state.
  • When capturing actions into a script using the Automation instrument, interfaces with web views or table cells that contain a high number of off screen elements may take an extremely long time before returning with an expression.
  • The lock() and unlock() functions of UIATarget have been replaced with the lockForDuration(<seconds>) function.
  • Instruments overwrites the loaded automation script, even if another program is editing it.
  • Starting iOS 5 beta 2, you can now trigger the execution of an UI Automation script on an iOS device from the host terminal by using the instruments tool. The command is:
    • instruments -w <device id> -t <template> <application>

UIKit

  • NEW: Starting in iOS 5 beta 3, the exclusiveTouch property of UIControl has returned to its original default value of NO.
  • Returning nil from the tableView:viewForHeaderInSection: method (or its footer equivalent) is no longer sufficient to hide a header. You must override tableView:heightForHeaderInSection: and return0.0 to hide a header.
  • In the iOS 5 beta, the UITableView class has two methods to move one cell from one row to another with defined parameters. These APIs are:
    • moveSection:toSection:
    • moveRowAtIndexPath:toIndexPath:
  • Using the UIWebView class in Interface Builder, setting transparent background color is possible in iOS 5. Developers compiling against the new SDK can check their XIB for the UIWebView transparent setting.
  • In the iOS 5 beta, the UINavigationBarUIToolbar, and UITabBar implementations have changed so that the drawRect: method is not called on instances of these classes unless it is implemented in a subclass. Apps that have re-implemented drawRect: in a category on any of these classes will find that the drawRect: method isn’t called. UIKit does link-checking to keep the method from being called in apps linked before iOS 5 but does not support this design on iOS 5 or later. Apps can either:
    • Use the customization API for bars that in iOS 5 and later, which is the preferred way.
    • Subclass UINavigationBar (or the other bar classes) and override drawRect: in the subclass.
  • The indexPathForRow:inSection:section, and row methods of NSIndexPath now use NSInteger instead of NSUInteger, so that these types match with methods defined on UITableView.
  • There is a known issue with presenting a UIVideoEditorControllerobject where it doesn’t show the selected video, which appears blank instead. In certain cases it may also crash.
  • Touch events are not getting forwarded to the view in the cameraOverlayView property of UIImagePickerController.
  • The imagePickerController:didFinishPickingMediaWithInfo: method of UIImagePickerController is not returning a URL to the video when recording is complete.
  • NEW: When creating a new appointment in calendar app on a device using 24 hr clock, you cannot select an hour value greater than 12. The date-time picker value sets current weekday to be the same as previous day (e.g: a An appointment on Tuesday will be set as Monday).
  • FIXED: We have changed the behavior of scrollToRowAtIndexPath:atScrollPosition:animated: such that UITableViewScrollPositionTop and UITableViewScrollPositionBottom now adjust for the top and bottom portions of the contentInset property.

WebKit

  • NEW: In iOS 5 beta 2, a new inherited CSS property, -webkit-overflow-scrolling: value, is available. The value touch allows the web developer to opt in to native-style scrolling in an overflow:scrollelement. The default value for this property is auto.
  • The WebKit framework has picked up a newer WebKit engine, which closely matches Safari 5.1. Some areas to be aware of with the new WebKit framework on iOS:
    • There is a new HTML5-compliant parser.
    • Text layout width may change slightly because word-rounding behavior now has floating-point-based precision.
    • There is improved validation of the <input type=number> form field, which includes removing leading zeros and number formatting.
    • Touch events are now supported on input fields.
    • window.onerror is now supported.
    • There is a new user agent that does not have locale information in the User Agent string.

WiFi Syncing

  • In iOS 5 beta 2, wireless syncing is available for the Mac. It requires iTunes 10.5 beta 2 and OS X 10.6.8 or Lion. You will see an option to enable wireless syncing when you connect your device to iTunes with the USB cable. It is recommended you perform your initial sync with a cable after restoring your device.
    • Wireless syncing is triggered automatically when the device is connected to power and on the same network as the paired computer. Or, you can manually trigger a sync from iTunes or from Settings -> General -> iTunes Sync (same network as paired computer required). Be sure your device is plugged into a power source when performing wireless syncs.
    • If you find issues with apps, media and/or photos synced to your device, you can reset then resync. From Settings -> General -> Reset, choose Erase all Content and Settings. Then reconnect to iTunes and sync again.
  • FIXED: In this beta, iTunes may incorrectly report Photos as “Other” in the capacity bar. Photo syncing otherwise works as expected.
  • NEW:In some cases, your device may fail to sync contacts, calendars and account settings, or back up to iTunes. If this happens, reboot your device and re-sync.
  • NEW:In some cases, syncing photos may result in only thumbnails on your device. If this happens, unsync Photos then re-sync again.

Xcode

  • In this beta, device restores using XCode are disabled. Please use iTunes only to back up and restore your device.
  • In some cases, Xcode 4.2 Organizer does not display a device that is in restore mode. As a workaround you can use iTunes to restore.
  • FIXED: On some desktop machines, Xcode’s memory usage inflates incredibly fast while restoring a device or copying an IPSW. As a workaround use iTunes to restore.
  • FIXED: In this beta, crash logs (either unsymbolicated or symbolicated) do not appear in Xcode Organizer. To make them appear in the Xcode Organizer, you will have to rename the device.
  • In iOS 5 beta 2, the iOS Simulator is not compatible with previous releases of the iCloud Developer Seed for OS X. It is highly recommended that you update to the latest iCloud Developer Seed to ensure compatibility.

iOS 5.0 SDK supports both iOS 4.3 and iOS 5.0 simulators.

MuscleNerd from the iPhone Dev Team recently also posted a message on Twitter saying that the RedSn0w beta version for iOS 5 can still jailbreak iOS 5 beta 3. You will need to point the beta 1IPSW (when you select the IPSW file, you have to select the iOS 5 beta 1 file instead).

Today’s 5.0b3 can be jailbroken with last month’s redsn0w http://is.gd/6eek4Y (point it at 5.0b1 IPSW..devs only please!)

If you are interested in downloading RedSn0w 0.9.8b1 to jailbreak iOS 5 beta 3, click on the following links based on the OS you are running:

Please keep in mind that this is a tethered jailbreak and this version of iOS 5 is a beta where some things might not work. Upgrade and jailbreak at your own risk.

 

Comex’s JailbreakMe 3.0 Jailbreaks Surpass One Million On First Day

0

Recently comex with the help of chpwn and saurik released JailbreakMe 3.0 to support devices running iOS 4.3+ including the iPad 2. The full list of compatible devices for the jailbreak can be found below:

  • iPad 1: 4.3 through 4.3.3
  • iPad 2: 4.3.3
  • iPhone 3GS: 4.3 through 4.3.3
  • iPhone 4: 4.3 through 4.3.3
  • iPhone 4-CDMA: 4.2.6 through 4.2.8
  • iPod Touch 3G: 4.3, 4.3.2, 4.3.3
  • iPod Touch 4G: 4.3 through 4.3.3

JailbreakMe 3.0 has been reported to work well and has had a ton of positive reception. For this exact reason, it’s been a hit for all iDevices, however most popular with the iPad 2. chpwn recently tweeted that JailbreakMe has surpassed 1,000,000 jailbreaks already. A pretty impressive feat if you think about it considering the jailbreak tool was leaked earlier this week. We already know that Apple plans to patch the exploit utilized by the jailbreak tool in a new version of iOS 4 (most likely iOS 4.3.4) but its also nice to know that the easy to use jailbreak tool has helped so many users out there in such a short period of time.

If you haven’t jailbroken your iPad 2 (or your other iOS devices), try JailbreakMe 3.0 out. You can do so by going to http://jailbreakme.com and following the directions. If you do, make sure to save your SHSH blobs with TinyUmbrella or some other tool to ensure that you are safe when iOS 4.3.4 releases. Afterwards, be sure to also patch the PDF exploit hole by downloading PDF Patcher 2 from Cydia.

JailbreakMe 3.0 Pre and Post Jailbreak Recommendations

0

First and foremost, everyone knows by know that JailbreakMe 3.0 was released by Comex recently. It is a userland jailbreak, which requires no USB connection, software installation, IPSW download, or any of the other things some people consider to be tedious. This specific jailbreak tool is one of the easiest for many beginners to use to jailbreak their device but it is these users who don’t follow other advice recommended from the jailbreak community to help secure their iOS device from vulnerabilities left open to exploit.

It is important for people to know to save their iOS 4.3.3 SHSH blobs to allow for the option to downgrade after Apple releases iOS 4.3.4 (which is bound to be released very soon). To do this, it is recommended that users download the Tiny Umbrella software released by notcom and save their SHSH blob. When doing this procedure it is important to note that the ‘Request SHSH from Cydia’ must be unchecked under the Advanced settings. For iPad 2 users, the iPhone Dev Team mentioned the following in their blog post:

But if you have the GSM or CDMA iPad2, you won’t be able to restore to 4.3.3 or lower once Apple stops signing its baseband.  There are a few ideas that might work to get around this limitation, but for now it’s best to assume there’s no going back to 4.3.3 once 4.3.4 is out for iPad2 GSM or CDMA owners.

Official Site: Tiny Umbrella

The other thing to know for users who have used JailbreakMe 3.0 is that the devs recommend patching the PDF exploit used in the jailbreak. This can be done by downloading and installing “PDF Patcher 2″ from Cydia after utilizing JailbreakMe 3.0. This will patch the exploit leaving your device secure and insusceptible to further exploits using the same hole.

Don’t be like the many clueless jailbreakers out there and spread the word to as many people so they have a more secure iOS device.

Our JailbreakMe page has been updated accordingly.

JailbreakMe 3.0 Released By Comex!

2

The much anticipated JailbreakMe 3.0 has finally been released by Comex. Due to the leaks over the past weekend, the kernel drivers are still buggy, but Comex wanted to release the jailbreak tool before Apple patched with iOS 4.3.4. The devices that are currently supported include:

  • iPad (4.3-4.3.3)
  • iPad 2 (4.3.3)
  • iPhone 3GS (4.3-4.3.3)
  • iPhone 4 (4.3-4.3.3) & CDMA (4.2.6-4.2.8)
  • iPod Touch 3G (not 4.3.1)
  • iPod Touch 4G (4.3-4.3.3)

If you have one of the devices mentioned above and you want to jailbreak he easier way, head on over to JailbreakMe.com on your iOS device and follow the instructions!

Our JailbreakMe page has been updated accordingly.

Stay tuned for any updates!

Buggy Version of JailbreakMe 3.0 Leaked

2

Earlier this morning, one of the JailbreakMe 3.0 beta testers leaked the pdf files for the jailbreak tool. @Paulpols was amongst the first to discover and tweet about it. He mentioned the following on Twitter:

The iPad 2 jailbreak for iOS 4.3 was leaked. Possibly Wi-Fi only. Not recommended & use at your own risk. • Available @ ipad2jailbreakpdf.weebly.com

Shortly after this incident, the whole set of unverified files for the iPad, iPhone, and iPod on different iOS versions were released. Many users were ashamed of the release as it really hurts the jailbreak community. @veeence mentioned that the person to leak the files was @MultiMediaWill. Ryan Lobbins was the one to originally host it on his site and then Will specifically hosted the iPad 2 file on his site and leaked it, according to what the word going is stating. @chpwn further mentioned that the leaked version of the iPad 2 pdf (which is to jailbreak the iPad 2) was so broken and unstable that @saurik told @comex to tell everyone to not use it if it was released. @i0n1c mentioned how the tool is probably being patched by Apple already and iOS 4.3.4 is probably going to be released soon to avoid people from jailbreaking their devices. This was mentioned in the following tweet:

An iPad2 4.3jB via PDF was leaked to the masses.that means Apple will reverse the xploit tonight and 4.3.4 will kill the jb before it is out

Apple is said to be more worried about the PDF crash as it crashes Safari on iOS 4.3.3, meaning that the vulnerability is still valid and is the same one used in the jailbreak. Furthermore, it shows that all their iDevices can be rooted remotely, hence iOS 4.3.4.The Apple employees are probably hard at work dissecting the code used behind @comex’s jailbreak method. It has been said that Apple has been anticipating the release of JailbreakMe 3.0 for weeks and has the appropriate teams (PDF Dev Team, Kernel Team and Exploit Reversers) ready to help patch the exploit involved. @comex was obviously not happy about the situation when he found out someone used a dictionary attack and leaked a buggy version of his jailbreak, putting him on what he felt was a useless time limit. He is hoping that the time limit he is put on isn’t too short and that he can work on a functional release candidate for his JailbreakMe 3.0 tool before Apple patches it. It is advised that if you are seeking to utilize the tool to jailbreak your iOS device, that you save the SHSH blobs for 4.3.3 using the TinyUmbrella software:

If you are waiting on the official JailbreakMe.com: save your iOS 4.3.3 SHSHs regardless of your current iOS version: thefirmwareumbrella.blogspot.com

Leaks are mentioned to be worse in the iOS 5.0 days but what is most important is what @iH8sn0w said best in his tweet that mentioned the following:

Blogs should NOT be posting information about leaked material. Its only giving Apple more of an advantage and a heads-up.

It really is a shame that someone leaked materials regarding the JailbreakMe 3.0 jailbreak tool as now it is forcing @comex to work at a faster pace to get his tool out before Apple patches it. The leaker not only didn’t have the right to release someone’s hard work but also didn’t think very carefully about how he is jeopardizing all the hard work and putting a countless number of users at risk of being unable to jailbreak their iOS device due to Apple working on a patch for the exploit used. Reasons such as this is why developers and hackers get frustrated and deterred from the scene.

Stay tuned for more news and info on the topic by following us on Facebook, Twitter, and/or subscribing to our RSS feed.

You can also stay up to date by checking out our JailbreakMe page.

Jailbreak Tweak – Polyonix – Allows Multiple iPhone Apps On iPad

0

Recently the iOS hacker and developer Aaron Ash (@aaronash), recently revealed “Polyonix.” A tweak that is exclusively for the iPad, which allows multiple iPhone application windows to be run simultaneously. This comes in very handy for a variety of different applications that you may use on a daily basis. The tweak is currently in its early stages but we believe it has a ton of potential in the future. Amongst the features that are currently available is the “edit mode” in the bottom right, which allows one to re-arrange the windows on the screen and even rotate the windows from portrait to landscape, and the other being the Close Polyonix button which is assumed for closing the overlay within the windows. There is currently no planned ETA or any other information that was given in Aaron’s blog post.

 

It has been mentioned that Aaron may allow some people to give it a test for those of you who  may be attending the jailbreak meet-up in New York.

Joshua Tucker from ModMyI had the chance to interview Aaron regarding the new tweak (named Polyonix):

JOSH: How’d you come up with this idea?
AARON: The idea has been floating around for a while. I’d been wanting to work on but I’ve had very little time available to work on it. I’ve found some time to hack on it a lot more recently and I’ve made some good progress.

JOSH: How long have you been working on this project?
AARON: My first git commit was on April 9th this year.

JOSH: Do you have any implementations that you’re looking to try to incorporate?
AARON: The exact details of implementation are up in the air still.

You can follow Aaron Ash (@aaronash) on Twitter for more information about his upcoming iPad tweak “Polyonix” and his other projects.

Source: ModMyI

iOS 5 Beta 2 Confirmed To Be Jailbroken Using Redsn0w 0.9.8b1

0

The iOS 5 beta 2, which was recently seeded to developers of the iOS developer program has been confirmed to be jailbroken using Redsn0w 0.9.8b1. A few weeks back, the iPhone Dev Team released Redsn0w 0.9.8b1 to the iOS 5 beta firmware file. MuscleNerd of the iPhone Dev Team confirmed it on Twitter by saying the following:

5.0b2 can be jailbroken w/redsn0w from 2 wks ago (must point redsn0w at 5.0b1 IPSW)..devs ONLY please

the “keep pointing at beta1 IPSW” trick should work for all the betas, due to the way redsn0w works. Unlockers stay away!

Redsn0w 0.9.8b1 supports the following iOS 5 devices:

  • iPod Touch 3G
  • iPod Touch 4G
  • iPad
  • iPhone 3GS
  • iPhone 4 (CDMA)
  • iPhone 4 (GSM)

Redsn0w 0.9.8b1 supports a tethered jailbreak as of right now, which means you will need to connect your iOS device to the computer on every reboot. You can download RedSn0w 0.9.8b1 and stay up to date on all news regarding RedSn0w by checking out our RedSn0w page.

Go to Top