|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Jailbreak (S5L8920+)"
(Info from an iPhone 3GS in DFU from System Profiler.) |
m |
||
| (225 intermediate revisions by 29 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]]. 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. |
||
| − | * '''Find a new bootrom exploit''' - After we have the bootrom dumped, we must look for a way to make SecureROM run our patched [[LLB]]. |
||
| + | * Use a bootrom exploit that allows unsigned code execution via USB. |
||
| + | 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''. |
||
| − | == How to check for [[0x24000 Segment Overflow]] exploitability (Mac) == |
||
| − | As the device has not been released yet, and we only know of it's existance because of various references to "iPhone2,1", this might not work for it. But for previous devices, and hopefully this one too, you can do this: |
||
| − | # Put the device in [[DFU]] |
||
| − | # Open Applications/Utilities/System Profiler |
||
| − | # Go to "USB" on the left sidebar |
||
| − | # Click on "Apple Mobile Device (DFU Mode)" |
||
| − | # Look under "USB Serial Number". Among things like the Chip ID, there should be "iBoot Version" |
||
| − | # If "iBoot Version" is "iBoot-240.4", then that means it is most likely still vulnerable |
||
| − | == |
+ | ==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 (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 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. |
||
| − | "Apple Mobile Device (DFU Mode): |
||
| + | There are methods to help keep your downgrading ability, though. |
||
| − | Product ID: 0x1227 |
||
| + | |||
| − | Vendor ID: 0x05ac (Apple Inc.) |
||
| + | * 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. |
||
| − | Version: 0.00 |
||
| + | * 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)]]. |
||
| − | Serial Number: CPID:8920 CPRV:14 CPFM:03 SCEP:01 BDID:00 ECID:000002DBCA0C6D0E SRTG:['''iBoot-359.3'''] |
||
| + | |||
| − | Speed: Up to 480 Mb/sec |
||
| + | == Jailbreak Tools == |
||
| − | Manufacturer: Apple Inc. |
||
| + | {{main|Jailbreak#Jailbreak Tools}} |
||
| − | Location ID: 0xfd100000 |
||
| + | |||
| − | Current Available (mA): 500 |
||
| + | [[Category:Jailbreaking]] |
||
| − | Current Required (mA): 100" |
||
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
