Difference between revisions of "Jailbreak (S5L8920+)"

From The iPhone Wiki
Jump to: navigation, search
(Undo revision 7734 by Santoyo Drummer (Talk) Info is already supplied (bottom of page). :))
m
 
(183 intermediate revisions by 15 users not shown)
Line 1: Line 1:
When the [[N88ap|iPhone 3GS]] was initially released, Apple did not have enough time to fix the [[0x24000 Segment Overflow]] in the [[S5L8920 (Bootrom)|S5L8920]]. However, in order to flash an exploited [[LLB]] and jailbreak the iPhone 3GS, '''one''' of the following needs to be done:
+
When the [[N88AP|iPhone 3GS]] was initially released, Apple did not have enough time to fix the [[0x24000 Segment Overflow]] in the [[S5L8920]]. However, in order to flash an exploited [[LLB]] and jailbreak the iPhone 3GS, '''one''' of the following needed to be done:
 
* Find a new [[iBoot]] exploit every time a new firmware is out.
 
* Find a new [[iBoot]] exploit every time a new firmware is out.
 
* Find a way to bypass the [[ECID]] checks.
 
* Find a way to bypass the [[ECID]] checks.
* Find another bootrom exploit that allows unsigned code executing via USB ([[Pwnage 2.0]]-like)
+
* Use a bootrom exploit that allows unsigned code execution via USB.
   
This also applies to the iPhone 3GS with [[iBoot-359.3.2|the new bootrom]], [[N18ap|iPod touch 3G]] and later devices, except a bootrom exploit is needed as well.
+
Newer devices (iPhone 3GS with [[Bootrom 359.3.2|new bootrom]], [[N18AP|iPod touch (3rd generation)]], and subsequent devices) are no longer vulnerable to the [[0x24000 Segment Overflow]] exploit. Many of them are susceptible to geohot's bootrom exploit (originally found in [[limera1n]]), which allows unsigned code execution over USB. Even newer devices, starting with the [[iPad 2]], have no bootrom exploits to run unsigned code ''at all''.
   
 
==ECID==
 
==ECID==
Apple added a new tag to the [[IMG3 File Format]] called ECID. The ECID is ''unique'' to each phone, and its signature is being checked. With this method, Apple attempts to block downgrades once newer firmware becomes available, unless you have a dump of your old firmware's unique IMG3 or signed certificate. Therefore, iBoot exploits won't be so useful for tethered jailbreaks, because such exploits will be closed in new firmwares. [http://iphonejtag.blogspot.com/2009/06/ecid-field-downgrades-no-dice.html].
+
Apple added a new tag to the [[IMG3 File Format]] called ECID. The ECID is ''unique'' to each phone, and its signature is being checked. With this method, Apple attempts to block downgrades once newer firmware becomes available, unless you have a dump of your old firmware's unique IMG3 or signed certificate. Therefore, [[iBoot (Bootloader)|iBoot]] exploits won't be so useful for [[tethered jailbreak]]s, because such exploits will be closed in new firmwares. [http://iphonejtag.blogspot.com/2009/06/ecid-field-downgrades-no-dice.html].
   
The issue with this is that, even with the [[0x24000 Segment Overflow]] still in bootrom, an [[iBoot]] exploit is still needed to actually flash the exploited [[LLB]]. If Apple uses this ECID stuff to block downgrades, then a new [[iBoot]] exploit will be needed whenever they fix the last, so that the 0x24000 Segment Overflow can be applied. This is because Apple could choose to not let you upload an older, exploitable [[iBEC]]/[[iBoot]]/[[iBSS]] to the device.
+
The issue with this is that, even with the [[0x24000 Segment Overflow]] still in [[bootrom]], an iBoot exploit was still needed to actually flash the exploited [[LLB]]. Apple uses this ECID stuff to block downgrading iBoot to a vulnerable version. It was resolved when Geohot released his [[limera1n]] tool, which used a bootrom exploit to upload an unsigned iBoot. Still the problem remains with newer devices with the [[0x24000 Segment Overflow]] fixed - tampering with firmware makes such jailbreak tethered unless some other exploit is used.
   
 
There are methods to help keep your downgrading ability, though.
 
There are methods to help keep your downgrading ability, though.
   
  +
* If it receives your ECID, saurik's servers will actively cache the necessary files. [http://www.saurik.com/id/12#howto Instructions] to use the servers are available.
* If it was cached prior to 3.1's release, 3GS owners can save a file which contains the signature of the 3.0 [[iBSS]] containing their [[ECID]], using the [http://purplera1n.com/ purplera1n website].
 
  +
* The [[SHSH]] associated with an ECID can be also saved by running [[TinyUmbrella]]. [[TinyUmbrella]] allows the user to restore to whatever version is associated with that [[SHSH]] file permanently. This is based on the aforementioned service [[Saurik]] provides remotely from [[Cydia Server|his server(s)]].
* Saurik's servers are actively caching the necessary files. [http://www.saurik.com/id/12#howto Instructions] to use the servers are included.
 
* The [[SHSH]] associated with an ECID can be also saved by running [[TinyUmbrella]]. [[TinyUmbrella]] allows the user to restore to whatever version is associated with that [[SHSH]] file permanently. This is based on the aforementioned service [[Saurik]] provides remotely from his server(s).
 
   
==Jailbreak tools==
+
== Jailbreak Tools ==
  +
{{main|Jailbreak#Jailbreak Tools}}
===Firmware 3.0 for iPhone 3GS===
 
There are several possible methods to jailbreak which use the same [[iBoot]] exploit discovered (independently) by [[User:Geohot|Geohot]] and the [[iPhone Dev Team]]:
 
   
  +
[[Category:Jailbreaking]]
* [[redsn0w]] 0.8 (also works with 3.0.1)
 
* [[PwnageTool]] 3.0.1
 
* [[purplera1n]]
 
 
===Firmware 3.1 for iPhone 3GS===
 
Firmware 3.1 can be jailbroken using
 
* [[PwnageTool]] 3.1.3 (Mac only), provided that the device was previously jailbroken on 3.0/3.0.1.
 
* [[blackra1n]]
 
 
===Firmware 3.1.2 for iPhone 3GS===
 
Firmware 3.1.2 for iPhone 3GS can be jailbroken using
 
* [[PwnageTool]] 3.1.4 (Mac only).
 
* [[blackra1n]]
 
 
===Firmware 3.1.1/3.1.2 for iPod Touch 3G===
 
It is currently possible to jailbreak all devices that have/had 3.1/3.1.1/3.1.2 using
 
* [[redsn0w]] 0.9.3
 
* [[blackra1n]]
 
 
===Firmware 3.1.2/3.1.3 for iPhone 3GS and iPod Touch 3G===
 
Firmware 3.1.3 for iPhone 3GS (Both bootroms) and iPod Touch 3G can be jailbroken using
 
* [[Spirit]]
 

Latest revision as of 09:52, 26 March 2017

When the iPhone 3GS was initially released, Apple did not have enough time to fix the 0x24000 Segment Overflow in the S5L8920. However, in order to flash an exploited LLB and jailbreak the iPhone 3GS, one of the following needed to be done:

  • Find a new iBoot exploit every time a new firmware is out.
  • Find a way to bypass the ECID checks.
  • Use a bootrom exploit that allows unsigned code execution via USB.

Newer devices (iPhone 3GS with new bootrom, iPod touch (3rd generation), and subsequent devices) are no longer vulnerable to the 0x24000 Segment Overflow exploit. Many of them are susceptible to geohot's bootrom exploit (originally found in limera1n), which allows unsigned code execution over USB. Even newer devices, starting with the iPad 2, have no bootrom exploits to run unsigned code at all.

ECID

Apple added a new tag to the IMG3 File Format called ECID. The ECID is unique to each phone, and its signature is being checked. With this method, Apple attempts to block downgrades once newer firmware becomes available, unless you have a dump of your old firmware's unique IMG3 or signed certificate. Therefore, iBoot exploits won't be so useful for tethered jailbreaks, because such exploits will be closed in new firmwares. [1].

The issue with this is that, even with the 0x24000 Segment Overflow still in bootrom, an iBoot exploit was still needed to actually flash the exploited LLB. Apple uses this ECID stuff to block downgrading iBoot to a vulnerable version. It was resolved when Geohot released his limera1n tool, which used a bootrom exploit to upload an unsigned iBoot. Still the problem remains with newer devices with the 0x24000 Segment Overflow fixed - tampering with firmware makes such jailbreak tethered unless some other exploit is used.

There are methods to help keep your downgrading ability, though.

  • If it receives your ECID, saurik's servers will actively cache the necessary files. Instructions to use the servers are available.
  • The SHSH associated with an ECID can be also saved by running TinyUmbrella. TinyUmbrella allows the user to restore to whatever version is associated with that SHSH file permanently. This is based on the aforementioned service Saurik provides remotely from his server(s).

Jailbreak Tools

Main article: Jailbreak#Jailbreak Tools