The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Talk:Jailbreak (S5L8920+)"
(→Decrypt Ramdisk: new section) |
(→Updating versions) |
||
(23 intermediate revisions by 8 users not shown) | |||
Line 12: | Line 12: | ||
Anyone know if this is the case? [[User:Rekoil|Rekoil]] 10:23, 20 June 2009 (UTC) |
Anyone know if this is the case? [[User:Rekoil|Rekoil]] 10:23, 20 June 2009 (UTC) |
||
+ | |||
+ | Is ECID relevant if there's a bootloader hole (24k pwn) -- can't the whole "ECID" business be patched out of llb/iboot? (wherever the check resides) [[User:iemit737|iemit737]] 12:45, 26 June 2009 (UTC) |
||
+ | :In order to use the [[0x24000 Segment Overflow|24kpwn]] hole, you must flash an oversized LLB. And you must have an iBoot exploit in order to flash such LLB. --[[User:Oranav|Oranav]] 16:17, 28 June 2009 (UTC) |
||
+ | |||
+ | |||
+ | |||
+ | Say Apple releases 3.2 and you buy an iPhone 3gs with 3.1. Let's pretend that 3.1's iBoot has been exploited, but 3.2's iBoot has not. |
||
+ | Will it be possible to patch 3.1's iBoot in 3.2's software upgrade through pwnage tool (or similar), in a similar fashion as baseband preservation? [[User:iemit737|iemit737]] 15:40, 28 Jun 2009 (UTC) |
||
+ | :Probably yes. --[[User:Oranav|Oranav]] 16:17, 28 June 2009 (UTC) |
||
== Decrypt Ramdisk == |
== Decrypt Ramdisk == |
||
− | Does anyone know how to go about decrypting the ramdisk found inside the iPhone2,1 IPSW using the keys geohot posted on his blog? I have tried using xpwntool, OpenSSL, etc. but nothing seems to work... |
+ | Does anyone know how to go about decrypting the ramdisk found inside the iPhone2,1 IPSW using the keys geohot posted on his blog? I have tried using xpwntool, OpenSSL, etc. but nothing seems to work...--[[User:Cool name|Cool name]] 20:07, 24 June 2009 (UTC) |
+ | |||
+ | I got it decrypted using img3decrypt. |
||
+ | --[[User:Skierdb526|skierdb526]] 22:04, 24 June 2009 (UTC) |
||
+ | |||
+ | == purplera1n ECID backup == |
||
+ | |||
+ | guys, just get one :P its not that hard, its not like you have to ask "hey, do i need to do this?" if you are unsure, just get one, it takes less than a minute :) |
||
+ | |||
+ | ==ordering of jailbreak tool table== |
||
+ | I see dialexio or whoever took his mad alphabetizing skills to work and ordered them alphabetically by tool name in the table. |
||
+ | I think it would be cooler/less-cluttered if it were ordered by date of tool release. Then it would have a green staircase effect and easy to spot the latest being always at the bottom. Or maybe I should just lay off the drugz.. Idk [[User:Iemit737|Iemit737]] 07:10, 2 August 2010 (UTC) |
||
+ | |||
+ | == Needs a new name. == |
||
+ | |||
+ | It's quite clear that the information on this page no longer applies to ''just'' the iPhone 3GS and iPod touch 3G. Does anyone have a good suggestion for a new article name? --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 15:30, 2 August 2010 (UTC) |
||
+ | |||
+ | "Jailbreak (S5L8920+)"? [[User:Iemit737|Iemit737]] 15:37, 2 August 2010 (UTC) |
||
+ | |||
+ | Sounds good, but if Apple were to make the next processor... say, the "S5L8830," the article would require a new name. (I doubt this will happen, but they ''did'' use the S5L8'''90'''0 in the iPhone 3G and the S5L8'''72'''0 in the iPod touch 2G...) --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 15:54, 2 August 2010 (UTC) |
||
+ | |||
+ | Yep. The touch 2G was kind of a freak product (in all the differences in security that got rolled into future devices) when apple went back to the 8900+ processor scheme. I think Jailbreak S5L8920+ will work well, as it is already in use on the main page. [[User:Iemit737|Iemit737]] 16:01, 2 August 2010 (UTC) |
||
+ | |||
+ | Good point. I'll move the page to [[Jailbreak (S5L8920+)]] then. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 16:05, 2 August 2010 (UTC) |
||
+ | |||
+ | == Apple TV 2G. == |
||
+ | hey guys, in the readme file of greepoisonn is written that support for apple tv 2g will be added in RC6!!! {{unsigned|Umbi98|17:39, February 7, 2011 (UTC)}} |
||
+ | |||
+ | == Updating versions == |
||
+ | |||
+ | What's the point in updating the redsn0w etc versions for old firmware versions? To jailbreak 4.2.1 you don't need rc15 of redsn0w; an earlier version is sufficient. I think it's more interesting what the minimum version must be. Later versions almost always can jb older firmware (unless it gets so old that it's no more of interest). -- [[User:Http|http]] 16:44, 6 May 2011 (UTC) |
||
+ | :It was meant to stop unnecessarily listing multiple versions in each cell. Plus sometimes (not all the time though), newer versions introduce bug fixes. I suppose you could change it to the earliest revision that supports it, if you'd prefer. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 18:31, 6 May 2011 (UTC) |
||
+ | ::I think formatting issues are not a valid argument. But yes, bugfixes are. But usually you use the newest version anyway. Only if it doesn't work you would take an old version. Maybe we should list both (range; oldest and newest it works with)? --[[User:Http|http]] 18:40, 6 May 2011 (UTC) |
||
+ | :::That could work. :) --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 02:44, 7 May 2011 (UTC) |
Latest revision as of 02:44, 7 May 2011
This kind of information should not be here until the release of the iPhone2,1.
Why not prepare early? It is too late for apple to fix anything at this point, not to mention they already know about the segment overflow. None of the information here reveals anyting to apple at all ChronicDev 10:43, 20 May 2009 (UTC)
I agree with Chronic there is no reason to not begin and edit as we get the new devices in our hands
3G S will have the 3.0 firmware OOB, which ships with iBoot-6xx, so probably the segment overflow exploit is gone... --Pjakuszew 13:33, 13 June 2009 (UTC)
3.0 fw is iBoot-59x.xx, but anyway, the exploit is in bootrom, that is why it's likely to stay (hopefully) ChronicDev 19:15, 13 June 2009 (UTC)
Oh, I overlooked that the exploit is in bootrom. :P Is bootrom updateable in any way? I know it's not writable in retail devices, but it can be easily updated by Apple before shipping the final device? --Pjakuszew 21:44, 14 June 2009 (UTC)
Anyone know if this is the case? Rekoil 10:23, 20 June 2009 (UTC)
Is ECID relevant if there's a bootloader hole (24k pwn) -- can't the whole "ECID" business be patched out of llb/iboot? (wherever the check resides) iemit737 12:45, 26 June 2009 (UTC)
- In order to use the 24kpwn hole, you must flash an oversized LLB. And you must have an iBoot exploit in order to flash such LLB. --Oranav 16:17, 28 June 2009 (UTC)
Say Apple releases 3.2 and you buy an iPhone 3gs with 3.1. Let's pretend that 3.1's iBoot has been exploited, but 3.2's iBoot has not. Will it be possible to patch 3.1's iBoot in 3.2's software upgrade through pwnage tool (or similar), in a similar fashion as baseband preservation? iemit737 15:40, 28 Jun 2009 (UTC)
- Probably yes. --Oranav 16:17, 28 June 2009 (UTC)
Contents
Decrypt Ramdisk
Does anyone know how to go about decrypting the ramdisk found inside the iPhone2,1 IPSW using the keys geohot posted on his blog? I have tried using xpwntool, OpenSSL, etc. but nothing seems to work...--Cool name 20:07, 24 June 2009 (UTC)
I got it decrypted using img3decrypt. --skierdb526 22:04, 24 June 2009 (UTC)
purplera1n ECID backup
guys, just get one :P its not that hard, its not like you have to ask "hey, do i need to do this?" if you are unsure, just get one, it takes less than a minute :)
ordering of jailbreak tool table
I see dialexio or whoever took his mad alphabetizing skills to work and ordered them alphabetically by tool name in the table. I think it would be cooler/less-cluttered if it were ordered by date of tool release. Then it would have a green staircase effect and easy to spot the latest being always at the bottom. Or maybe I should just lay off the drugz.. Idk Iemit737 07:10, 2 August 2010 (UTC)
Needs a new name.
It's quite clear that the information on this page no longer applies to just the iPhone 3GS and iPod touch 3G. Does anyone have a good suggestion for a new article name? --Dialexio 15:30, 2 August 2010 (UTC)
"Jailbreak (S5L8920+)"? Iemit737 15:37, 2 August 2010 (UTC)
Sounds good, but if Apple were to make the next processor... say, the "S5L8830," the article would require a new name. (I doubt this will happen, but they did use the S5L8900 in the iPhone 3G and the S5L8720 in the iPod touch 2G...) --Dialexio 15:54, 2 August 2010 (UTC)
Yep. The touch 2G was kind of a freak product (in all the differences in security that got rolled into future devices) when apple went back to the 8900+ processor scheme. I think Jailbreak S5L8920+ will work well, as it is already in use on the main page. Iemit737 16:01, 2 August 2010 (UTC)
Good point. I'll move the page to Jailbreak (S5L8920+) then. --Dialexio 16:05, 2 August 2010 (UTC)
Apple TV 2G.
hey guys, in the readme file of greepoisonn is written that support for apple tv 2g will be added in RC6!!! --The preceding unsigned comment was added by Umbi98 (talk) 17:39, February 7, 2011 (UTC). Please consult this page for more info on how to sign pages, and how to fix this.
Updating versions
What's the point in updating the redsn0w etc versions for old firmware versions? To jailbreak 4.2.1 you don't need rc15 of redsn0w; an earlier version is sufficient. I think it's more interesting what the minimum version must be. Later versions almost always can jb older firmware (unless it gets so old that it's no more of interest). -- http 16:44, 6 May 2011 (UTC)
- It was meant to stop unnecessarily listing multiple versions in each cell. Plus sometimes (not all the time though), newer versions introduce bug fixes. I suppose you could change it to the earliest revision that supports it, if you'd prefer. --Dialexio 18:31, 6 May 2011 (UTC)
- I think formatting issues are not a valid argument. But yes, bugfixes are. But usually you use the newest version anyway. Only if it doesn't work you would take an old version. Maybe we should list both (range; oldest and newest it works with)? --http 18:40, 6 May 2011 (UTC)
- That could work. :) --Dialexio 02:44, 7 May 2011 (UTC)
- I think formatting issues are not a valid argument. But yes, bugfixes are. But usually you use the newest version anyway. Only if it doesn't work you would take an old version. Maybe we should list both (range; oldest and newest it works with)? --http 18:40, 6 May 2011 (UTC)