Morning news:
iPhone Dev-team has just posted a new blog post showing closely the progress of iPhone 4S and iPad 2 untethered jailbreak. The post confirming that the Dream Team (MuscleNerd, Pod2g and p0sixninja) are nearly ready for the general release of iPhone 4S and iPad 2 jailbreak, and it's now all about making the jailbreak as bug free as possible. We picked up the important paragraphs in the below quotations, please read them carefully.
Jailbreak programs :
To be as flexible as possible, the A5 version of the corona jailbreak will take multiple forms:
Chronic Dev have incorporated the overall flow into a GUI that runs on your Mac or PC
iPhone Dev have incorporated the exact same flow into a command-line interface (CLI). This will allow us to help users through individual steps of the jailbreak manually, to both help the user and help improve the overall flow. Although the CLI will also allow the user to perform the entire jailbreak from beginning to end, we anticipate it will be more useful in debugging the occasional errors. The CLI currently has over 20 individual options (in addition to the single “jailbreak” option) that should be useful during debug after the GUI release.
Once all the bugs in the flow are worked out, we’ll also incorporate it into the redsn0w GUI (but still leave the CLI freely available too). In order to maximize the chances of the jailbreak working for everyone, the redsn0w GUI will use native Apple iTunes libraries — this technique is slightly different than how the Chronic Dev GUI handles communications, and should provide nice combined coverage for all the odd computer configurations out there.
-What the above quotation means that we will see Pod2g's Corona exploit in multiple forms, as we told you before that iPhone 4S and iPad 2 jailbreak will be released via Redsn0w (iPhone Dev team), Greenpois0n (Chronic Dev-team), Sn0wbreeze (ih8sn0w) and maybe Ac1dsn0w.
What will be the jailbreakable fimwawares:
iPhone 4S: 5.0 (9A334), 5.0.1 (9A405) and the “other” 5.0.1 (9A406)
iPad 2: 5.0.1 (9A405)
If you do intend to unlock your iPhone 4S :
iPhone4S owners looking to maximize their chances of achieving an eventual software-based carrier unlock should be staying at 5.0.
Everyone else should be at 5.0.1. If you’re an iPhone4S owner who already updated to 5.0.1, it’s too late to go back down to 5.0, but if you’re on 9A406 it is possible to downgrade the BB by going to the 9A405 version of 5.0.1 while the window is still open.
Important notes before jailbreaking your iPhone 4S and iPad 2:
The overall flow used by the GUI and CLI to inject the A5 corona jailbreak has never been done before, and there may be unforeseen problems once it’s released to the public. It’s very important for you to sync your data, photos, and music before attempting any version of this jailbreak.
iPhone Dev-team has just posted a new blog post showing closely the progress of iPhone 4S and iPad 2 untethered jailbreak. The post confirming that the Dream Team (MuscleNerd, Pod2g and p0sixninja) are nearly ready for the general release of iPhone 4S and iPad 2 jailbreak, and it's now all about making the jailbreak as bug free as possible. We picked up the important paragraphs in the below quotations, please read them carefully.
Jailbreak programs :
To be as flexible as possible, the A5 version of the corona jailbreak will take multiple forms:
Chronic Dev have incorporated the overall flow into a GUI that runs on your Mac or PC
iPhone Dev have incorporated the exact same flow into a command-line interface (CLI). This will allow us to help users through individual steps of the jailbreak manually, to both help the user and help improve the overall flow. Although the CLI will also allow the user to perform the entire jailbreak from beginning to end, we anticipate it will be more useful in debugging the occasional errors. The CLI currently has over 20 individual options (in addition to the single “jailbreak” option) that should be useful during debug after the GUI release.
Once all the bugs in the flow are worked out, we’ll also incorporate it into the redsn0w GUI (but still leave the CLI freely available too). In order to maximize the chances of the jailbreak working for everyone, the redsn0w GUI will use native Apple iTunes libraries — this technique is slightly different than how the Chronic Dev GUI handles communications, and should provide nice combined coverage for all the odd computer configurations out there.
-What the above quotation means that we will see Pod2g's Corona exploit in multiple forms, as we told you before that iPhone 4S and iPad 2 jailbreak will be released via Redsn0w (iPhone Dev team), Greenpois0n (Chronic Dev-team), Sn0wbreeze (ih8sn0w) and maybe Ac1dsn0w.
What will be the jailbreakable fimwawares:
iPhone 4S: 5.0 (9A334), 5.0.1 (9A405) and the “other” 5.0.1 (9A406)
iPad 2: 5.0.1 (9A405)
If you do intend to unlock your iPhone 4S :
iPhone4S owners looking to maximize their chances of achieving an eventual software-based carrier unlock should be staying at 5.0.
Everyone else should be at 5.0.1. If you’re an iPhone4S owner who already updated to 5.0.1, it’s too late to go back down to 5.0, but if you’re on 9A406 it is possible to downgrade the BB by going to the 9A405 version of 5.0.1 while the window is still open.
Important notes before jailbreaking your iPhone 4S and iPad 2:
The overall flow used by the GUI and CLI to inject the A5 corona jailbreak has never been done before, and there may be unforeseen problems once it’s released to the public. It’s very important for you to sync your data, photos, and music before attempting any version of this jailbreak.
.
