|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Jailbreak"
(→Userland (used for all devices)) |
Guyutongxue (talk | contribs) m (→Versions: add 16.x) |
||
| (812 intermediate revisions by 34 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{float toc|right}} |
||
| − | This is the process by which full execute and write access is obtained on all the partitions of the iPhone. It is done by patching /etc/fstab to mount the System partition as read-write. This is entirely different from an [[unlock]]. Jailbreaking is the first action that must be taken before things like unofficial [[activation]] (hacktivation), and unofficial unlocking can be applied. |
||
| + | The term "'''jailbreak'''" is the process by which full execute and write access is obtained on all the partitions of iOS, iPadOS, tvOS and watchOS. It used to be done by patching [[/private/etc/fstab]] to mount the System partition as 'read-write'. This is entirely different from an [[unlock]]. Jailbreaking is the first action that must be taken before things like unofficial [[activation]] (hacktivation), and unofficial [[unlock]]ing can be applied. |
||
| − | + | Older jailbreaks also included modifying the [[AFC]] service (used by [[iTunes]] to access the filesystem) to give full filesystem access from root. This was later updated to create a new service ([[AFC]]2) that allows access to the full filesystem. |
|
| − | Modern jailbreaks |
+ | Modern jailbreaks now include patching the kernel to get around code signing and other restrictions. These are called [[Kernel Patches]]. |
| + | '''Note''': The legality of jailbreaking your device varies with each country/region. [[wikipedia:iOS jailbreaking#Legality|Wikipedia has a summary of legality for some countries]]. |
||
| − | ==Exploits which were used in order to jailbreak (in chronological order)== |
||
| − | === 1.0.2 === |
||
| − | * [[Restore Mode]] ([[iBoot (Bootloader)|iBoot]] had a command named cp, which had access to the whole filesystem) |
||
| − | + | == Types of Jailbreaks == |
|
| + | When a device is booting, it loads Apple's own [[kernel]] initially, so a jailbroken device must be exploited and have the kernel patched each time it is booted up. |
||
| − | * [[Symlinks]] (an upgrade jailbreak) |
||
| − | * [[LibTiff | libtiff exploit]] (Adapted from the PSP scene, used by [[JailbreakMe]]) |
||
| − | === 1.1.2 === |
||
| − | * [[Mknod]] (an upgrade jailbreak) |
||
| − | === 1.1.3 / 1.1.4 === |
||
| − | * [[Soft Upgrade]] (an upgrade jailbreak) |
||
| − | * [[Ramdisk Hack]] |
||
| + | An [[untethered jailbreak|'''untethered''' jailbreak]] uses exploits that are powerful enough to allow the user to turn their device off and back on at will, with the device starting up completely, and the kernel will be patched without the help of a computer – in other words, it will be jailbroken even after each reboot. |
||
| − | ==Exploits which are used in order to jailbreak 2.0 and above== |
||
| + | However, some jailbreaks are [[tethered jailbreak|'''tethered''']]. A tethered jailbreak is only able to temporarily jailbreak the device during a single boot. If the user turns the device off and then boots it back up without the help of a jailbreak tool, the device will no longer be running a patched kernel, and it may get stuck in a partially started state, such as [[Recovery Mode]]. In order for the device to start completely and with a patched kernel, it must be "re-jailbroken" with a computer (using the "boot tethered" feature of a tool) each time it is turned on. All changes to the files on the device (such as installed package files or edited system files) will persist between reboots, including changes that can only function if the device is jailbroken (such as installed package files). |
||
| − | ===[[Userland]] (used for all devices)=== |
||
| − | *[[MobileBackup Copy Exploit]] + [[Incomplete Codesign Exploit]] + [[BPF_STX Kernel Write Exploit]] (together for [[Spirit]]) |
||
| − | *[[Malformed CFF Vulnerability]] + [[Incomplete Codesign Exploit]] + [[IOSurface Kernel Exploit]] (together for [[Star]]) |
||
| − | *[[Packet Filter Kernel Exploit]] (together with [[limera1n]]'s bootrom exploit or the [[usb_control_msg(0xA1, 1) Exploit]], for [[untethered jailbreak]]) |
||
| + | In more recent years, two other solutions have been created - '''semi-tethered''' and '''semi-''un''tethered'''. |
||
| − | ===[[M68ap|iPhone]] / [[N82ap|iPhone 3G]] / [[N45ap|iPod touch]]=== |
||
| − | * [[Pwnage]] and [[Pwnage 2.0]] (together) |
||
| + | A [[semi-tethered jailbreak|'''semi-tethered''']] solution is one where the device is able to start up on its own, but it will no longer have a patched kernel, and therefore will not be able to run modified code. It will, however, still be usable for normal functions, just like stock iOS. To start with a patched kernel, the user must start the device with the help of the jailbreak tool. |
||
| − | ===[[N72ap|iPod touch 2G]]=== |
||
| − | * [[ARM7 Go]] (used by [[tethered jailbreak]]s) |
||
| − | * [[0x24000 Segment Overflow]] (used on "MB" models for an [[untethered jailbreak]]) |
||
| − | *[[usb_control_msg(0x21, 2) Exploit]] ([[tethered jailbreak|tethered]] for units with the [[iBoot-240.5.1|new bootrom]]) |
||
| − | *[[usb_control_msg(0xA1, 1) Exploit]] (used for a [[tethered jailbreak]] on units with the [[iBoot-240.5.1|new bootrom]]) |
||
| + | A [[semi-untethered jailbreak|'''semi-''un''tethered''']] jailbreak gives the ability to start the device on it's own. On first boot, the device will not be running a patched kernel. However, rather than having to run a tool from a computer to apply the kernel patches, the user is able to re-jailbreak their device with the help of an app (usually sideloaded using [[Cydia Impactor]]) running on their device. In the case of the iOS 9.2-9.3.3 jailbreak, a Safari-based exploit was available, thereby meaning a website could be used to rejailbreak. |
||
| − | ===[[N88ap|iPhone 3GS]]=== |
||
| − | * [[0x24000 Segment Overflow]] (used on older devices for an [[untethered jailbreak]]) |
||
| − | * [[iBoot Environment Variable Overflow]] |
||
| − | * [[usb_control_msg(0x21, 2) Exploit]] ([[tethered jailbreak|tethered]] for newer devices) |
||
| − | * [[limera1n]] ([[tethered jailbreak|tethered]] on its own, [[untethered jailbreak|untethered]] with an additional exploit) |
||
| + | In more detail: Each iOS device has a [[bootchain]] that tries to make sure only trusted/signed code is loaded. A device with a tethered jailbreak is able to boot up with the help of a jailbreaking tool because the tool executes exploits via USB that bypass parts of that "chain of trust", bootstrapping to a [[pwned]] (no [[Signature Check Patch|signature check]]) [[iBSS]], [[iBEC]], or [[iBoot (Bootloader)|iBoot]] to finish the boot process. |
||
| − | ===[[N18ap|iPod touch 3G]]=== |
||
| − | *[[usb_control_msg(0x21, 2) Exploit]] ([[tethered jailbreak|tethered]] only) |
||
| − | * [[limera1n]] ([[tethered jailbreak|tethered]] on its own, [[untethered jailbreak|untethered]] with an additional exploit) |
||
| + | == Jailbreak Tools == |
||
| − | ===[[N90ap|iPhone 4]]=== |
||
| + | Untethered or semi-untethered jailbreaks are shown with a green 'yes'. Tethered or semi-tethered jailbreaks will be stated in a yellow box. [[Beta Firmware]]s are not listed. |
||
| − | * [[limera1n]]'s bootrom exploit ([[tethered jailbreak|tethered]] on its own, [[untethered jailbreak|untethered]] with an additional exploit) |
||
| − | === |
+ | ===Versions=== |
| + | * [[Jailbreak/1.x|1.x]] |
||
| − | * [[limera1n]]'s bootrom exploit ([[tethered jailbreak|tethered]] on its own, [[untethered jailbreak|untethered]] with an additional exploit) |
||
| + | * [[Jailbreak/2.x|2.x]] |
||
| + | * [[Jailbreak/3.x|3.x]] |
||
| + | * [[Jailbreak/4.x|4.x]] |
||
| + | * [[Jailbreak/5.x|5.x]] |
||
| + | * [[Jailbreak/6.x|6.x]] |
||
| + | * [[Jailbreak/7.x|7.x]] |
||
| + | * [[Jailbreak/8.x|8.x]] |
||
| + | * [[Jailbreak/9.x|9.x]] |
||
| + | * [[Jailbreak/10.x|10.x]] |
||
| + | * [[Jailbreak/11.x|11.x]] |
||
| + | * [[Jailbreak/12.x|12.x]] |
||
| + | * [[Jailbreak/13.x|13.x]] |
||
| + | * [[Jailbreak/14.x|14.x]] |
||
| + | * [[Jailbreak/15.x|15.x]] |
||
| + | * [[Jailbreak/16.x|16.x]] |
||
| + | ==See Also== |
||
| − | ===[[k48ap|iPad]]=== |
||
| + | * [[Failbreak]] |
||
| − | * [[limera1n]]'s bootrom exploit ([[tethered jailbreak|tethered]] on its own, [[untethered jailbreak|untethered]] with an additional exploit) |
||
| + | * [[Jailbreak Exploits]] |
||
| + | * [[Kernel Patches]] |
||
| + | [[Category:Jailbreaking]] |
||
| − | ===[[k66ap|Apple TV 2G]]=== |
||
| − | * [[limera1n]]'s bootrom exploit ([[tethered jailbreak|tethered]] on its own, [[untethered jailbreak|untethered]] with an additional exploit) |
||
Latest revision as of 10:55, 13 February 2023
The term "jailbreak" is the process by which full execute and write access is obtained on all the partitions of iOS, iPadOS, tvOS and watchOS. It used to be done by patching /private/etc/fstab to mount the System partition as 'read-write'. This is entirely different from an unlock. Jailbreaking is the first action that must be taken before things like unofficial activation (hacktivation), and unofficial unlocking can be applied.
Older jailbreaks also included modifying the AFC service (used by iTunes to access the filesystem) to give full filesystem access from root. This was later updated to create a new service (AFC2) that allows access to the full filesystem.
Modern jailbreaks now include patching the kernel to get around code signing and other restrictions. These are called Kernel Patches.
Note: The legality of jailbreaking your device varies with each country/region. Wikipedia has a summary of legality for some countries.
Types of Jailbreaks
When a device is booting, it loads Apple's own kernel initially, so a jailbroken device must be exploited and have the kernel patched each time it is booted up.
An untethered jailbreak uses exploits that are powerful enough to allow the user to turn their device off and back on at will, with the device starting up completely, and the kernel will be patched without the help of a computer – in other words, it will be jailbroken even after each reboot.
However, some jailbreaks are tethered. A tethered jailbreak is only able to temporarily jailbreak the device during a single boot. If the user turns the device off and then boots it back up without the help of a jailbreak tool, the device will no longer be running a patched kernel, and it may get stuck in a partially started state, such as Recovery Mode. In order for the device to start completely and with a patched kernel, it must be "re-jailbroken" with a computer (using the "boot tethered" feature of a tool) each time it is turned on. All changes to the files on the device (such as installed package files or edited system files) will persist between reboots, including changes that can only function if the device is jailbroken (such as installed package files).
In more recent years, two other solutions have been created - semi-tethered and semi-untethered.
A semi-tethered solution is one where the device is able to start up on its own, but it will no longer have a patched kernel, and therefore will not be able to run modified code. It will, however, still be usable for normal functions, just like stock iOS. To start with a patched kernel, the user must start the device with the help of the jailbreak tool.
A semi-untethered jailbreak gives the ability to start the device on it's own. On first boot, the device will not be running a patched kernel. However, rather than having to run a tool from a computer to apply the kernel patches, the user is able to re-jailbreak their device with the help of an app (usually sideloaded using Cydia Impactor) running on their device. In the case of the iOS 9.2-9.3.3 jailbreak, a Safari-based exploit was available, thereby meaning a website could be used to rejailbreak.
In more detail: Each iOS device has a bootchain that tries to make sure only trusted/signed code is loaded. A device with a tethered jailbreak is able to boot up with the help of a jailbreaking tool because the tool executes exploits via USB that bypass parts of that "chain of trust", bootstrapping to a pwned (no signature check) iBSS, iBEC, or iBoot to finish the boot process.
Jailbreak Tools
Untethered or semi-untethered jailbreaks are shown with a green 'yes'. Tethered or semi-tethered jailbreaks will be stated in a yellow box. Beta Firmwares are not listed.
