<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.theiphonewiki.com/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Pody</id>
	<title>The iPhone Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.theiphonewiki.com/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Pody"/>
	<link rel="alternate" type="text/html" href="https://www.theiphonewiki.com/wiki/Special:Contributions/Pody"/>
	<updated>2026-05-06T17:02:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.14</generator>
	<entry>
		<id>https://www.theiphonewiki.com/w/index.php?title=Jailbreak_(S5L8920%2B)&amp;diff=3955</id>
		<title>Jailbreak (S5L8920+)</title>
		<link rel="alternate" type="text/html" href="https://www.theiphonewiki.com/w/index.php?title=Jailbreak_(S5L8920%2B)&amp;diff=3955"/>
		<updated>2009-06-25T21:51:35Z</updated>

		<summary type="html">&lt;p&gt;Pody: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Because of the date the [[0x24000 Segment Overflow]] was leaked by [[NitroKey]], Apple may or may not have had the time to fix the bug in the [[S5L8920 (Bootrom)|iPhone 3G[s] Bootrom]]. If not, the following needs to be done:&lt;br /&gt;
* '''Find a new iBoot exploit''' - This will allow us to decrypt the platform iBoot and other firmware files in it's IPSW, as well as dump the bootrom to examine.&lt;br /&gt;
* '''Find a new bootrom exploit''' - After we have the bootrom dumped, we must look for a way to make SecureROM run our patched [[LLB]].&lt;br /&gt;
&lt;br /&gt;
==ECID==&lt;br /&gt;
Apple added a new tag to the img3 format called ECID. The ECID is ''unique'' to each phone, and is being sigchecked. So no downgrades unless you have a dump of your unique old firmware's img3. Therefore, iBoot exploits won't be so useful for tethered JBs, because such exploits will be closed in new FWs. [http://iphonejtag.blogspot.com/2009/06/ecid-field-downgrades-no-dice.html]&lt;br /&gt;
&lt;br /&gt;
==Geohot's iBoot Exploit==&lt;br /&gt;
Geohot has a new iBoot exploit in 7A341 FW. [http://iphonejtag.blogspot.com/2009/06/no-sn0w-in-summer.html]&lt;br /&gt;
He has also found iv/keys for the ramdisk and for vfdecrypt. [[Planetbeing]] discovered the key for Securerom.&lt;/div&gt;</summary>
		<author><name>Pody</name></author>
		
	</entry>
	<entry>
		<id>https://www.theiphonewiki.com/w/index.php?title=Jailbreak_(S5L8920%2B)&amp;diff=3954</id>
		<title>Jailbreak (S5L8920+)</title>
		<link rel="alternate" type="text/html" href="https://www.theiphonewiki.com/w/index.php?title=Jailbreak_(S5L8920%2B)&amp;diff=3954"/>
		<updated>2009-06-25T21:45:57Z</updated>

		<summary type="html">&lt;p&gt;Pody: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Because of the date the [[0x24000 Segment Overflow]] was leaked by [[NitroKey]], Apple may or may not have had the time to fix the bug in the [[S5L8920 (Bootrom)|iPhone 3G[s] Bootrom]]. If not, the following needs to be done:&lt;br /&gt;
* '''Find a new iBoot exploit''' - This will allow us to decrypt the platform iBoot and other firmware files in it's IPSW, as well as dump the bootrom to examine.&lt;br /&gt;
* '''Find a new bootrom exploit''' - After we have the bootrom dumped, we must look for a way to make SecureROM run our patched [[LLB]].&lt;br /&gt;
&lt;br /&gt;
==ECID==&lt;br /&gt;
Apple added a new tag to the img3 format called ECID. The ECID is ''unique'' to each phone, and is being sigchecked. So no downgrades unless you have a dump of your unique old firmware's img3. Therefore, iBoot exploits won't be so useful for tethered JBs, because such exploits will be closed in new FWs. [http://iphonejtag.blogspot.com/2009/06/ecid-field-downgrades-no-dice.html]&lt;br /&gt;
&lt;br /&gt;
==Geohot's iBoot Exploit==&lt;br /&gt;
Geohot has a new iBoot exploit in 7A341 FW. [http://iphonejtag.blogspot.com/2009/06/no-sn0w-in-summer.html]&lt;br /&gt;
He has also found iv/keys for the ramdisk and for vfdecrypt. Planetbeing discovered the key for Securerom.&lt;/div&gt;</summary>
		<author><name>Pody</name></author>
		
	</entry>
</feed>