pod2g goes on to answer more frequently asked questions on his blog post:

• The poll about releasing now or waiting for 6.0 ended with a 64% / 33% to release ASAP. Where is the link ? ETA ? How much % done ? etc.
  As I said earlier in twitter, there's still a lot to do to have a user friendly and well tested tool to install the jailbreak on end users devices. Expect a release in a couple of weeks.
• Will it be compatible with my <any random iOS device> ?
  It will be compatible with any device running iOS 5.1.1 except iPod 3G, iPhone 3Gs and ATV3 (right now, may change in a near future, nobody knows).
• Why is it so slow to release now that the iPad 3,1 has been demoed ?
  There are 16 different devices out there to work on and to test. It takes time.
• May I be a beta tester ?
  No, sorry. Only really trusted people (that can be counted on one hand) could have access to the jailbreak. I don't want any leak to happen.
• What if I offer you 1,000,000$ ?
  That doesn't change a thing.

So it looks like the new jailbreak is right around the corner and it shouldn't be long now! Stay tuned for more info!

DOWNLOAD:
Redsn0w 0.9.11b2 - OSX
Redsn0w 0.9.11b2 - WIN

The first error happens during the downgrade process, iTunes Error 37. I still have not been able to determine exactly what causes this error, but there are a few tips I can give you to try and solve the issue. First of all, if you are a Windows user, make sure you are running Redsn0w as administrator(you should always do this when running Redsn0w on Windows). Another thing you can try is use the opposite SHSH source that you used on your first try. For example, if you used the "remote" Cydia SHSH the first time, try using the local TinyUmbrella SHSH the second time. Finally, make sure you are selecting the firmware in the correct order(first select the 5.0.1 firmware and then select the 5.1.1 firmware).

The second issue is happening to people after they've downgraded and once they've attempted to jailbreak. The error during jailbreaking is Jailbreak Failed: Service Wouldn't Start (642). I have determined that this issue is being experienced by people who restore their device from a backup BEFORE jailbreaking. If you are experiencing this issue, don't worry you do not need to restore. Just go to settings>general>reset and select "Erase all Content and Settings." Once that's done you should be able to jailbreak(if it doesn't work the first time do Erase all Content and Settings again). Once you're jailbroken, then you can go ahead and restore from a backup and you should have no issues!

Thanks to @CovXX for helping me with this post.

If you have any additional issues you would like us to address or you have different solutions to these issues, please respond in the comments section!

Now there is one major downside to this method so please take caution if you are a Gevey unlocker. A more detailed release log can be found at the bottom of the post:

• The A5 downgrade method actually updates to the latest firmware before downgrading to the earlier one.This process updates your baseband to whatever is newest.  DO NOT USE THIS METHOD IF YOU RELY ON UNOFFICIAL UNLOCKS of your iPhone4S.  Those who used the temporary SAM technique to unlock their iPhones to specific SIMs shouldn’t be affected by this baseband update.

DOWNLOAD:
Redsn0w 0.9.11b2 - OSX
Redsn0w 0.9.11b2 - WIN
iOS Firmware - You will need both the firmware you wish to downgrade to and the most current firmware(5.1.1)

Step 1: Download Redsn0w 0.9.11b1 from above. Also download the iOS5 firmware file you wish to downgrade to and ALSO download the latest iPhone firmware available(5.1.1 currently). NOTE FOR 4S USERS: The iPhone-Dev Team forgot to include the 9A406 version of the 5.0.1 firmware in this release, so please download the 9A405 version for now(you will also need SHSH for the 9A405 version). This will be addressed in the next release.

Step 2: Now open Redsn0w(run as administrator if you're on Windows) and go to and select the new Restore utility which can be found under Extras -> Even More -> Restore

Step 3: Now click the "IPSW" button and Redsn0w will ask you to browse for the IPSW you want to restore. The first IPSW you need to select is the one you ultimately want to end up on. In my case I will be restoring to 5.0.1 so I can jailbreak my 4S so I will select the 5.0.1 firmware first. Immediately after selecting the 5.0.1 firmware, I will then select the 5.1.1(most current firmware) that I downloaded earlier. As soon as you select the 5.1.1 firmware, a large warning will pop-up explaining to you the baseband update and how users with an unlocked iPhone using Ultrasn0w or Gevey will lose the ability to unlock, click "Yes" to proceed.

Step 4: After Redsn0w has verified both firmware files you selected, you will then need to select your saved SHSH blob for the firmware you are downgrading to. If your SHSH are saved on Cydia(listed at the top of Cydia) you can simply use the "Remote" option which will pull them from Cyida, otherwise use the "Local" option which allows you to select your TinyUmbrella SHSH blobs directly from your computer.

Step 5: Now this is the great part, after selecting your firmware and your SHSH blobs, Redsn0w will do the rest of the process for you automatically. That's right, no need for iTunes, Redsn0w has the entire restore process built right in. First Redsn0w will install the hacked 5.1.1 firmware and then it will downgrade you to 5.0.1.

Step 6: After Redsn0w has completed, that's basically all there is to it. You should now be on a factory 5.0.1 firmware(or whatever firmware you downgraded to) and you can go ahead and jailbreak with Absinthe or jailbreak with Redsn0w, whichever tool you'd like!

If you have any questions, as always, don't hesitate to ask in the comments section! Below is an entire list of the Redsn0w 0.9.11b1 changelog:

• The new feature is at Extras->Even More->Restore
• You cannot downgrade without the personalized SHSH blobs for your device at that lower firmware.  You need to have fetched those blobs while the signing window was open, using either Cydia’s built-in TSS@Home feature, or with TinyUmbrella.  The new Restore screen of redsn0w lets you choose either the remote blobs or local ones (for the earlier firmware).  If you don’t know where TinyUmbrella put your blobs, TinyUmbrella has a button that will show you (copy them out of that folder and feed them to redsn0w).
• The A5 downgrade method actually updates to the latest firmware before downgrading to the earlier one.This process updates your baseband to whatever is newest.  DO NOT USE THIS METHOD IF YOU RELY ON UNOFFICIAL UNLOCKS of your iPhone4S.  Those who used the temporary SAM technique to unlock their iPhones to specific SIMs shouldn’t be affected by this baseband update.
• This method can be fixed by Apple with a firmware update.  It’s a (pleasant) mystery why they haven’t fixed it yet, because reverse-engineering of the restore ramdisk indicates they do know about it.  It’s possibly too niche to bother to fix right now.
• The least-tested devices with this method are the iPad2,3 and iPad3,2 (because we don’t have those models).  If you do and you feel like experimenting, please let us know how it turns out in the comment section below!
• This update involves a bunch of new redsn0w code.  We recommend sticking to the previous version 0.9.10b8b unless you’re specifically using this new feature, until all the bugs are worked out!  (Note: If redsn0w gets stuck at the “Waiting for device” stage for more than 30 seconds, you’ve hit a pesky GUI bug…that will be fixed in an upcoming version!)

Now that he has jailbroken the iPad3 on 5.1, the next step for him is to see if he can get the jailbreak running on 5.1.1 and to make the exploit more stable. There is still no ETA on the release, but it is good to know he is working hard on it for us!

Redsn0w 0.9.11 is still in beta, but it shouldn't be long before we see a public release and A5+ users who were forced to, or "accidentally," updated their devices to a newer firmware will be able to downgrade back to 5.0.1 using their SHSH blobs in order to be able to jailbreak.

• Improves reliability of using HDR option for photos taken using the Lock Screen shortcut
• Addresses bugs that could prevent the new iPad from switching between 2G and 3G networks
• Fixes bugs that affected AirPlay video playback in some circumstances
• Improved reliability for syncing Safari bookmarks and Reading List
• Fixes an issue where 'Unable to purchase' alert could be displayed after successful purchase

For information on the security content of this update, please visit this website:

http://support.apple.com/kb/DL1521

There have been some interesting articles floating around the web at the moment about the need for Apple to revamp the iOS homescreen in their next major update.

There are both some major positives as well as major drawbacks of changing the so well known homescreen. Hundreds of millions of users already know how to use the iPhone, iPod touch and iPad Home screen, and that’s a huge barrier to change. Maybe not to geeks, but certainly to mainstream users.

It has the fast app switcher, it has folders, it has notification center, it has Siri, but at its core it’s still an app switcher, same as it’s been since 2007. It’s a classic, but as much as everyone loves the classics, sometimes we want something new.

We won't your thoughts, what do you think!? Using the poll section below, share your thoughts.

For example, I recently was organizing and running the sound equipment for a friends wedding. The quickest and easiest way for me to setup dinner and dance music during the practice was to play it through an iTunes playlist. The music they had chosen wasn't exactly my taste in music. After the wedding I found I had a bunch of music in my libary which I didn't actually want to listen to.

Pressing ‘delete’ only solves half the problem – deleting it from your playlist. Deleting the song from your library and computer takes another few steps.

Hold down the Apple key (or hold shift if they are in order) and select the songs you would like to remove. Then enter the 'secret' key combination: Option + Command + Delete

This secret key combination will not only delete a song from your playlist, but also ask if you want to delete the song from your hard drive as well. Problem solved.

Last week, pod2g added a poll on his blog asking the jailbreak community to weigh in on whether he should release the jailbreak as soon as it's ready or if he should wait until iOS6 is released to see if the exploits still exist. Personally, I voted that he should release the jailbreak right away. Reason being that I am an iPhone4S user who is still using 5.0.1 for the jailbreak, but I would really like to update so that I can finally fix the battery issues that have plagued 4S users since it's release. Also, if you remember back to last year, the Chronic-Dev team announced at the first annual JailbreakCon that they had found several exploits in the iOS5 beta which meant that it would be jailbroken soon after public release.

Things did not pan out that way however, between JailbreakCon and the public release of iOS5, Apple managed to independently patch most(if not all) of those exploits they had found. I feel like if pod2g waited until iOS6 the same thing would happen and we would have waited months for something that didn't even matter. The fact that pod2g, i0n1c and other hackers have been very vocal about the exploits they have found leads me to believe that Apple will be putting their team into overdrive trying to find the exploits and will have them patched by the time iOS6 is released publicly.

If you want to voice your opinion, make sure to head over to his blog to vote!