Fixed a common crash in the Windows application that occurred during the exploitation process.
The only fix was to put the device back into DFU mode and perform a full restore via iTunes (wiping all data). There were no "RootFS snapshots" or "Restore RootFS" buttons in 2011. You lost your data.
To understand the significance of redsn0w 0.9.6rc16, one must understand the environment in which it was released. The year was 2011. Apple had recently released iOS 4.3.3, a minor update that primarily addressed location tracking concerns. While the update was crucial for privacy, it posed a threat to the jailbreak community: it patched the vulnerabilities used by previous jailbreak tools.
Prior to this version, users had to rely on "tethered" jailbreaks. This meant that if the device’s battery died or the user rebooted the phone, they would be stuck on the Apple logo until they connected it to a computer and ran the jailbreak tool again. It was a hassle that turned many casual users away from the scene. redsn0w 0.9.6rc16
This specific version, "Release Candidate 16" (rc16), was a bug-fix update intended to polish the jailbreak experience following earlier iterations like rc15. Its primary achievements included:
Even back then, preserving the baseband (modem firmware) was vital for users who relied on software unlocks (like ultrasn0w) to use their iPhones on carriers other than the approved ones. Redsn0w allowed users to update their iOS firmware without updating the baseband, a feature that saved countless iPhones from being locked to specific carriers.
At the time, the iPhone 4 was the flagship device, sporting the A4 chip—the first Apple-designed system-on-a-chip. While jailbreaking older devices (like the iPhone 3GS) was relatively straightforward due to hardware vulnerabilities in the bootrom (the infamous 24kpwn exploit), the iPhone 4 was much more secure. Fixed a common crash in the Windows application
Version 0.9.6rc16 was a Release Candidate (hence "rc") that brought a critical feature to the masses: an on A4 devices.
When rc16 was released, it faced stiff competition:
Here is where the confusion—and the legend of rc16—begins. Many users with new bootrom devices (or iPhone 4 devices, which never had the old bootrom) downloaded redsn0w 0.9.6rc16 expecting an untethered experience. They followed tutorials that failed to emphasize the bootrom requirement. Consequently, they ended up with a broken, tethered jailbreak, leading to thousands of forum posts titled "redsn0w 0.9.6rc16 stuck at pineapple logo." You lost your data
Your device will show a "Pineapple with legs". Once it reboots, you’re good to go! Today in iOS for the DFU mode process?
But the headline feature everyone downloaded it for was the option.