Difference between revisions of "Symlinks"

From The iPhone Wiki
Jump to: navigation, search
(New page: Before the discovery of the Ramdisk Hack, this was used after 1.1.1 to jailbreak. It involved either symlinking the directories to a sandbox or symlinking the NAND block device, in...)
 
m (Exploit: Updatign)
 
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
  +
== Credit ==
Before the discovery of the [[Ramdisk Hack]], this was used after 1.1.1 to jailbreak. It involved either symlinking the directories to a sandbox or symlinking the [[NAND]] block device, in order to retain the jailbroken state.
 
  +
[[iPhone Dev Team]]
  +
  +
== Exploit ==
  +
Before the discovery of the [[LibTiff Exploit]], this was used on 1.1.1 to jailbreak iPhones from 1.0.2. However, this only worked for [[List of iPhones|iPhones]], as the new [[List of iPod touches|iPod touch]] could not run 1.0.2 and therefore could not use this jailbreak method. The symlink method involved symlinking [[/private/var/root/Media]], the "jailed" directory that could be accessed via iPHUC, to [[/]], and then downloading, jailbreaking, and reuploading the entire system partition from <code>/dev/rdisk0s1</code>.
  +
  +
This exploit was fixed in 1.1.2, when Apple introduced a check in the update ramdisk that prevented this from happening. Note that this is not the 1.1.2 [[mknod]] exploit.
  +
  +
[[Category:Jailbreaks]]
  +
[[Category:Jailbreaking]]

Latest revision as of 10:57, 14 November 2015

Credit

iPhone Dev Team

Exploit

Before the discovery of the LibTiff Exploit, this was used on 1.1.1 to jailbreak iPhones from 1.0.2. However, this only worked for iPhones, as the new iPod touch could not run 1.0.2 and therefore could not use this jailbreak method. The symlink method involved symlinking /private/var/root/Media, the "jailed" directory that could be accessed via iPHUC, to /, and then downloading, jailbreaking, and reuploading the entire system partition from /dev/rdisk0s1.

This exploit was fixed in 1.1.2, when Apple introduced a check in the update ramdisk that prevented this from happening. Note that this is not the 1.1.2 mknod exploit.