The iPhone Wiki - User contributions [en]

User:LiNK

2011-04-19T05:29:47Z

LiNK:

I'm a 19-year-old iPhone hacker/developer.

Add me on Game Center: Ltamake

Twitter: [http://twitter.com/ltamake Follow me!]

The iPhone Wiki:Spam

2011-04-19T05:29:25Z

LiNK:

Account signup has been blocked again due to spammers. Captcha didn't fix it

I propose one of three options, invites, account approval, or signup Thursdays. --[[User:Geohot|geohot]] 03:47, 19 April 2011 (UTC)

:I think account approval would be the best option (although the most work for everyone with sysop powers). People that want to sign up may have trouble asking current users for an invite, and it sounds like spammers would have no problem spamming the wiki on signup days. --[[User:Dialexio|Dialexio]] 04:20, 19 April 2011 (UTC)

:I think it's quite strange that the Captcha didn't work. For the current spam the best way would be a regular expression that detects these new pages (all look identical) and automatically denies the page creation and immediately blocks that user. But of course they can change the text and it's not solved anymore. What about their emails? Currently you don't have to provide a valid email. What if you enable the email verification? Maybe they still get around that somehow, but I think they use something highly automated and something that works on all wikis, not just here. If we would add a verification "word" in the verification email that they would have to reenter on the page, then that would be something nonstandard that might not work for them. If they still get around that, we can approve new users (best choice of your ideas), but based on what should we decide? If we just approve every new user, we also risk to approve spammers. --[[User:Http|http]] 05:00, 19 April 2011 (UTC)

::Well, CAPTCHA only does so much. I propose maybe implementing a CAPTCHA that uses a GIF animation since that breaks a lot of spambots. If not that, then maybe just account approval. [[User:LiNK|LiNK]] 05:29, 19 April 2011 (UTC)

===Invite System===
How do we combat this recent spamming of this wiki? I suggest a possible invite system or similar? --[[User:Srts|Srts]] 02:24, 9 November 2009 (UTC)
:I have already blocked account signup, they must have had this account for a while. --[[User:Geohot|geohot]] 02:29, 9 November 2009 (UTC)
::Well if they don't stop, we can't have account creation disabled forever, defeats the purpose of the wiki. People like him are sad. Great work to all the sysops et all. keeping disruption to a minimal :D --[[User:Srts|Srts]] 02:34, 9 November 2009 (UTC)
:::Yea thanks a lot guys for putting up with this. We'll give a bit of time, and if they continue, we'll figure something out. This kid keep trying to reset my password for hosting and the wiki. Too bad he doesn't have a life. --[[User:Geohot|geohot]] 03:10, 9 November 2009 (UTC)
:::An invite system might not be a bad idea actually [[User:ChronicDev|Will Strafach]] 03:16, 9 November 2009 (UTC)
::::feel free to post their IP addresses, lol --[[User:Posixninja|posixninja]] 04:08, 9 November 2009 (UTC)
::::Well, if you need an extra admin to block them (and delete spam pages), I volunteer. --[[User:Dranfi|Dranfi]]
:::::Congrats, you're an admin --[[User:Geohot|geohot]] 13:22, 9 November 2009 (UTC)

===IP ranges, approval system===
How many different IPs are we dealing with? Is it within a specific range? For the time being, it may be possible to blacklist an entire subnet if they are all coming from the same place. But if a botnet is doing this, may be more difficult. Is it possible for MediaWiki to require admin approval of an edit prior to it being commited? Not well versed with MediaWiki administration, just thossing out some ideas. --[[User:Tsuehpsyde|tsuehpsyde]] 17:29, 9 November 2009 (UTC)
:It is not within a specific range. On my wiki, people post almost the exact same stuff as IP's and I get from 64.*.*.* al the way to 96.*.*.* I think it is a botnet --[[User:Balloonhead66|Balloonhead66]] 23:13, 16 March 2011 (UTC)
:We could figure out where they come from and do the same to them. Secondly, we could create a filter that unless your part of a specific group you cannot do more than this many edits in this amount of time. We could try making a period where the admins have to approve the users. Lastly, we could make it so that in the first 12 hours of a user account that user could not edit pages so it would give time for the sysops to ban the users. [[User:Revolution|Revolution]] 00:02, 10 November 2009 (UTC)
::That might not be a good idea as we could get you butts sued. --[[User:Balloonhead66|Balloonhead66]]
:::Why don't we just do this Apple-style and have a group of moderators approve of every comment, page edit or revision? I would love to be a part of such group.
::::The extension for mediawiki [[mediawikiwiki:Extension:FlaggedRevs|FlaggedRevs]] is 1.14 and above. This wiki is running 1.12 :( --[[User:Balloonhead66|Balloonhead66]] 23:13, 16 March 2011 (UTC)

Does this wiki currently take advantage of IP banning capability or would that just be subverted anyways? --[[User:Iemit737|Iemit737]] 03:48, 6 April 2011 (UTC)
:The wiki does indeed employ IP banning. The spambots are getting around it, though. --[[User:Dialexio|Dialexio]] 04:13, 6 April 2011 (UTC)
::IP bans are largely useless anyways as -Most Internet users have dynamic IP's and they could simply use a proxy anyways (It's relatively easy to create a VPN once you know where the option is in your OS). They'll also probably block innocent users. --[[User:Ryccardo|Ryccardo]] 14:54, 6 April 2011 (UTC)

===limitations, whitelistings===

If the ones you refer to as 'they' are the [http://code.google.com/p/pois0nhack pois0nhack] group then 'they' don't really seem to pose much of a threat in my opinion. I agree that for the time being we could impose some kind of 12/24 hr posting limitation (maybe no more than +-300 char changes?), but no more than that since this is, after all, a public wiki. Sorry if I'm intruding on some kind of admin/mod meeting, just figured I should have my say. --[[User:Rekoil|adriaaan]] 00:27, 10 November 2009 (UTC)
:I am in favor of a 12hr limit for new users, but since it's a public wiki, during this time, contributions would have to be approved by sysops. --Untagged
::Personally I think it would be good to have it so that all edits by new users a thrown into a moderation pool, then once a good amount of worthwhile contributions, that user can be "whitelisted".
::Maybe we could extend the Twitter-Service to display more information (i.e. "Main Page (-2,439) http://u.nu/5x2t3 " instead of "Main Page - http://u.nu/5x2t3"). That could allow fast detection (and reversal) of vandalism attempts because large edits by "unknown" would be easy to spot. May also add the username and/or the commit message, but then we'd have to check for anything Twitter might interpret or block. --[[User:CleanAir|CleanAir]] 13:58, 12 November 2009 (UTC)

===Captcha===

Can we add a Captcha to the logon process? I don't think all these recent spam pages are done manually. --[[User:Http|http]] 06:29, 15 March 2011 (UTC)
:Good idea [[User:Http|http]], add a Captcha to the logon process and the sign up process for some time --[[User:Whiteshinyapple|Whiteshinyapple]] 09:53, 16 March 2011 (UTC).
:Uhm better idea [[User:Http|http]], add a Captcha when making new pages. Having to fill in a captcha at every login seems to be a pain in the ass :/ the only thing the spam is doing is making new pages, (at least as far as i see.) --[[User:IMaximusX|IMaximusX]]
::What I meant was for the registration process (new user), not for every login. Only [[User:Geohot|geohot]] could implement that. --[[User:Http|http]] 17:37, 16 March 2011 (UTC)
::[http://recaptcha.net Recaptcha] might work. I requires 1.8+, but only works on the sign in, edits with a new external link (anon only), and passwork cracking. --[[User:Balloonhead66|Balloonhead66]] 23:13, 16 March 2011 (UTC)
::[[User:http|http]] im pretty sure they already have accounts, :p --[[User:IMaximusX|IMaximusX]]

We have all these options but have any of them actually been implemented? Somebodys got to do something, The spam is getting out of control. --[[User:Grisolp|Grisolp]] 03:38, 9 April 2011 (UTC)
:As http said, it's up to geohot to add a CAPTCHA for account creation. IP banning is in use, but it appears futile. --[[User:Dialexio|Dialexio]] 03:52, 9 April 2011 (UTC)

The spam bots are taking overhand. We will continue to clean it manually, but I suggest to add a Captcha to the new user signup process. That should be sufficient. But you might need to update mediawiki. See [http://code.google.com/apis/recaptcha/docs/mediawiki.html]. -- [[User:Http|http]] 11:35, 1 April 2011 (UTC)
:I can help to clean up the mess as well since I'm from a different timezone (UTC+8). -- [[User:nannoid|nannoid]] 11:51, 1 April 2011 (UTC)
::What does time zone have to do with it? --[[User:Balloonhead66|Balloonhead66]] 00:00, 6 April 2011 (UTC)
:This is out of control. The captcha needs to be in place soon or eventually the recent changes will be flooded and me and the other monitors of it won't be able to keep track of it. --[[User:Balloonhead66|Balloonhead66]] 00:00, 6 April 2011 (UTC)

Recaptcha added, SONY sucks ass. --[[User:Geohot|geohot]] 03:55, 14 April 2011 (UTC)
:Sweet! Thanks for the reCAPTCHA addition; the (job) spam was getting tiresome. And... yeah, Sony really needs to lose its dictator mindset and treat consumers better. :\ --[[User:Dialexio|Dialexio]] 04:31, 14 April 2011 (UTC)

:Thanks. And great you got back from this trial stuff without bigger damage. Signup reCAPTCHA seems to be a good way to handle the spam. The spam that came afterwards was probably from accounts created earlier. We still have 1106 existing accounts (including the already blocked ones) with the typical syntax of the spam bot accounts. Hopefully not many of those are sleeping for this purpose. I assume the automatic spam will get much lower after a few days. We'll see. -- [[User:Http|http]] 22:58, 14 April 2011 (UTC)

:Shit. User Gilbberg that was used from this spam bot was created new. It was not in the wiki user list I created an hour earlier. So the spam bot either knows how to read the reCAPTCHA or there sits someone entering these captchas for every spam that gets created in a semi-automated way. This means we need something better or something non-standard. Ideas? -- [[User:Http|http]] 23:15, 14 April 2011 (UTC)

:I cannot see when user accounts were created, as I don't have access to the database. But shortly after [[User:Geohot|geohot]] added the reCAPTCHA to the new user signup process, I created a list of all users and saved this list. I can confirm that all spam accounts since then (Gilbberg, Giacnen, Frengra, Sarmaiz, Lyneelay, Hiruail, Zimemoor, Albuend, Audpep, Furmayt) were created after that. This means that they must use a semi-automated way to spam (or found a way around the reCAPTCHA). New ideas wanted. -- [[User:Http|http]] 08:26, 16 April 2011 (UTC)

::Why don't we add a captcha to the new page / editing submission? Once per session or whatever. Also captcha on signin. It's OTT but there aren't many alternatives =/ --[[User:Windows Helpdesk|blackthund3r]] 13:25, 16 April 2011 (UTC)

The iPhone Wiki:Spam

2011-04-19T05:28:55Z

LiNK:

Account signup has been blocked again due to spammers. Captcha didn't fix it

I propose one of three options, invites, account approval, or signup Thursdays. --[[User:Geohot|geohot]] 03:47, 19 April 2011 (UTC)

:I think account approval would be the best option (although the most work for everyone with sysop powers). People that want to sign up may have trouble asking current users for an invite, and it sounds like spammers would have no problem spamming the wiki on signup days. --[[User:Dialexio|Dialexio]] 04:20, 19 April 2011 (UTC)

:I think it's quite strange that the Captcha didn't work. For the current spam the best way would be a regular expression that detects these new pages (all look identical) and automatically denies the page creation and immediately blocks that user. But of course they can change the text and it's not solved anymore. What about their emails? Currently you don't have to provide a valid email. What if you enable the email verification? Maybe they still get around that somehow, but I think they use something highly automated and something that works on all wikis, not just here. If we would add a verification "word" in the verification email that they would have to reenter on the page, then that would be something nonstandard that might not work for them. If they still get around that, we can approve new users (best choice of your ideas), but based on what should we decide? If we just approve every new user, we also risk to approve spammers. --[[User:Http|http]] 05:00, 19 April 2011 (UTC)

::Well, CAPTCHA only does so much. I propose maybe implementing a CAPTCHA that uses a GIF animation since that breaks a lot of spambots. If not that, then maybe just account approval. [[User:LiNK|LiNK]] 05:28, 19 April 2011 (UTC)

===Invite System===
How do we combat this recent spamming of this wiki? I suggest a possible invite system or similar? --[[User:Srts|Srts]] 02:24, 9 November 2009 (UTC)
:I have already blocked account signup, they must have had this account for a while. --[[User:Geohot|geohot]] 02:29, 9 November 2009 (UTC)
::Well if they don't stop, we can't have account creation disabled forever, defeats the purpose of the wiki. People like him are sad. Great work to all the sysops et all. keeping disruption to a minimal :D --[[User:Srts|Srts]] 02:34, 9 November 2009 (UTC)
:::Yea thanks a lot guys for putting up with this. We'll give a bit of time, and if they continue, we'll figure something out. This kid keep trying to reset my password for hosting and the wiki. Too bad he doesn't have a life. --[[User:Geohot|geohot]] 03:10, 9 November 2009 (UTC)
:::An invite system might not be a bad idea actually [[User:ChronicDev|Will Strafach]] 03:16, 9 November 2009 (UTC)
::::feel free to post their IP addresses, lol --[[User:Posixninja|posixninja]] 04:08, 9 November 2009 (UTC)
::::Well, if you need an extra admin to block them (and delete spam pages), I volunteer. --[[User:Dranfi|Dranfi]]
:::::Congrats, you're an admin --[[User:Geohot|geohot]] 13:22, 9 November 2009 (UTC)

===IP ranges, approval system===
How many different IPs are we dealing with? Is it within a specific range? For the time being, it may be possible to blacklist an entire subnet if they are all coming from the same place. But if a botnet is doing this, may be more difficult. Is it possible for MediaWiki to require admin approval of an edit prior to it being commited? Not well versed with MediaWiki administration, just thossing out some ideas. --[[User:Tsuehpsyde|tsuehpsyde]] 17:29, 9 November 2009 (UTC)
:It is not within a specific range. On my wiki, people post almost the exact same stuff as IP's and I get from 64.*.*.* al the way to 96.*.*.* I think it is a botnet --[[User:Balloonhead66|Balloonhead66]] 23:13, 16 March 2011 (UTC)
:We could figure out where they come from and do the same to them. Secondly, we could create a filter that unless your part of a specific group you cannot do more than this many edits in this amount of time. We could try making a period where the admins have to approve the users. Lastly, we could make it so that in the first 12 hours of a user account that user could not edit pages so it would give time for the sysops to ban the users. [[User:Revolution|Revolution]] 00:02, 10 November 2009 (UTC)
::That might not be a good idea as we could get you butts sued. --[[User:Balloonhead66|Balloonhead66]]
:::Why don't we just do this Apple-style and have a group of moderators approve of every comment, page edit or revision? I would love to be a part of such group.
::::The extension for mediawiki [[mediawikiwiki:Extension:FlaggedRevs|FlaggedRevs]] is 1.14 and above. This wiki is running 1.12 :( --[[User:Balloonhead66|Balloonhead66]] 23:13, 16 March 2011 (UTC)

Does this wiki currently take advantage of IP banning capability or would that just be subverted anyways? --[[User:Iemit737|Iemit737]] 03:48, 6 April 2011 (UTC)
:The wiki does indeed employ IP banning. The spambots are getting around it, though. --[[User:Dialexio|Dialexio]] 04:13, 6 April 2011 (UTC)
::IP bans are largely useless anyways as -Most Internet users have dynamic IP's and they could simply use a proxy anyways (It's relatively easy to create a VPN once you know where the option is in your OS). They'll also probably block innocent users. --[[User:Ryccardo|Ryccardo]] 14:54, 6 April 2011 (UTC)

===limitations, whitelistings===

If the ones you refer to as 'they' are the [http://code.google.com/p/pois0nhack pois0nhack] group then 'they' don't really seem to pose much of a threat in my opinion. I agree that for the time being we could impose some kind of 12/24 hr posting limitation (maybe no more than +-300 char changes?), but no more than that since this is, after all, a public wiki. Sorry if I'm intruding on some kind of admin/mod meeting, just figured I should have my say. --[[User:Rekoil|adriaaan]] 00:27, 10 November 2009 (UTC)
:I am in favor of a 12hr limit for new users, but since it's a public wiki, during this time, contributions would have to be approved by sysops. --Untagged
::Personally I think it would be good to have it so that all edits by new users a thrown into a moderation pool, then once a good amount of worthwhile contributions, that user can be "whitelisted".
::Maybe we could extend the Twitter-Service to display more information (i.e. "Main Page (-2,439) http://u.nu/5x2t3 " instead of "Main Page - http://u.nu/5x2t3"). That could allow fast detection (and reversal) of vandalism attempts because large edits by "unknown" would be easy to spot. May also add the username and/or the commit message, but then we'd have to check for anything Twitter might interpret or block. --[[User:CleanAir|CleanAir]] 13:58, 12 November 2009 (UTC)

===Captcha===

Can we add a Captcha to the logon process? I don't think all these recent spam pages are done manually. --[[User:Http|http]] 06:29, 15 March 2011 (UTC)
:Good idea [[User:Http|http]], add a Captcha to the logon process and the sign up process for some time --[[User:Whiteshinyapple|Whiteshinyapple]] 09:53, 16 March 2011 (UTC).
:Uhm better idea [[User:Http|http]], add a Captcha when making new pages. Having to fill in a captcha at every login seems to be a pain in the ass :/ the only thing the spam is doing is making new pages, (at least as far as i see.) --[[User:IMaximusX|IMaximusX]]
::What I meant was for the registration process (new user), not for every login. Only [[User:Geohot|geohot]] could implement that. --[[User:Http|http]] 17:37, 16 March 2011 (UTC)
::[http://recaptcha.net Recaptcha] might work. I requires 1.8+, but only works on the sign in, edits with a new external link (anon only), and passwork cracking. --[[User:Balloonhead66|Balloonhead66]] 23:13, 16 March 2011 (UTC)
::[[User:http|http]] im pretty sure they already have accounts, :p --[[User:IMaximusX|IMaximusX]]

We have all these options but have any of them actually been implemented? Somebodys got to do something, The spam is getting out of control. --[[User:Grisolp|Grisolp]] 03:38, 9 April 2011 (UTC)
:As http said, it's up to geohot to add a CAPTCHA for account creation. IP banning is in use, but it appears futile. --[[User:Dialexio|Dialexio]] 03:52, 9 April 2011 (UTC)

The spam bots are taking overhand. We will continue to clean it manually, but I suggest to add a Captcha to the new user signup process. That should be sufficient. But you might need to update mediawiki. See [http://code.google.com/apis/recaptcha/docs/mediawiki.html]. -- [[User:Http|http]] 11:35, 1 April 2011 (UTC)
:I can help to clean up the mess as well since I'm from a different timezone (UTC+8). -- [[User:nannoid|nannoid]] 11:51, 1 April 2011 (UTC)
::What does time zone have to do with it? --[[User:Balloonhead66|Balloonhead66]] 00:00, 6 April 2011 (UTC)
:This is out of control. The captcha needs to be in place soon or eventually the recent changes will be flooded and me and the other monitors of it won't be able to keep track of it. --[[User:Balloonhead66|Balloonhead66]] 00:00, 6 April 2011 (UTC)

Recaptcha added, SONY sucks ass. --[[User:Geohot|geohot]] 03:55, 14 April 2011 (UTC)
:Sweet! Thanks for the reCAPTCHA addition; the (job) spam was getting tiresome. And... yeah, Sony really needs to lose its dictator mindset and treat consumers better. :\ --[[User:Dialexio|Dialexio]] 04:31, 14 April 2011 (UTC)

:Thanks. And great you got back from this trial stuff without bigger damage. Signup reCAPTCHA seems to be a good way to handle the spam. The spam that came afterwards was probably from accounts created earlier. We still have 1106 existing accounts (including the already blocked ones) with the typical syntax of the spam bot accounts. Hopefully not many of those are sleeping for this purpose. I assume the automatic spam will get much lower after a few days. We'll see. -- [[User:Http|http]] 22:58, 14 April 2011 (UTC)

:Shit. User Gilbberg that was used from this spam bot was created new. It was not in the wiki user list I created an hour earlier. So the spam bot either knows how to read the reCAPTCHA or there sits someone entering these captchas for every spam that gets created in a semi-automated way. This means we need something better or something non-standard. Ideas? -- [[User:Http|http]] 23:15, 14 April 2011 (UTC)

:I cannot see when user accounts were created, as I don't have access to the database. But shortly after [[User:Geohot|geohot]] added the reCAPTCHA to the new user signup process, I created a list of all users and saved this list. I can confirm that all spam accounts since then (Gilbberg, Giacnen, Frengra, Sarmaiz, Lyneelay, Hiruail, Zimemoor, Albuend, Audpep, Furmayt) were created after that. This means that they must use a semi-automated way to spam (or found a way around the reCAPTCHA). New ideas wanted. -- [[User:Http|http]] 08:26, 16 April 2011 (UTC)

::Why don't we add a captcha to the new page / editing submission? Once per session or whatever. Also captcha on signin. It's OTT but there aren't many alternatives =/ --[[User:Windows Helpdesk|blackthund3r]] 13:25, 16 April 2011 (UTC)

Limera1n

2010-10-30T03:52:13Z

LiNK: Removed the space at the beginning.

{{DISPLAYTITLE:limera1n}}
[[Image:Ra1ndrop.png|right]]
This is [[User:Geohot|geohot's]] latest [[jailbreak]] utility. It uses an undisclosed bootrom exploit and an undisclosed kernel exploit found by [[User:Comex|comex]] to achieve an [[untethered jailbreak]] on newer devices.

* [[N88ap|iPhone 3GS]]
* [[N90ap|iPhone 4]]
* [[N18ap|iPod touch 3G]]
* [[N81ap|iPod touch 4G]]
* [[K48ap|iPad]]
* [[K66ap|AppleTV 2G]] ([http://www.tuaw.com/2010/10/09/limera1n-jailbreak-released-greenpois0n-jailbreak-delayed/ However it's current usefulness is debatable])

It has been demonstrated multiple times by [[User:Geohot|geohot]], using blog posts on his now private blog. [[User:Geohot|Geohot]] [http://1.bp.blogspot.com/_NJ4JFBfr1tY/TDgkAsTQEmI/AAAAAAAAAcw/ZNHDxMNNL4Y/s1600/iphone4.png showed off a high-res picture of Cydia on an iPhone 4]. He [http://www.youtube.com/watch?v=__TR86PLiHw displayed an iPod touch 3G with an untethered jailbreak] that met MuscleNerd's requirements for a good video. In addition, he took a [http://4.bp.blogspot.com/_NJ4JFBfr1tY/S7_OvGMqJMI/AAAAAAAAAcE/R5WLrCizGw0/s1600/ipad_jb.jpg picture of Cydia and blackra1n icons on his iPad's SpringBoard].

'''Release Date:''' October 9, 2010

'''Supported OS's:''' Mac OS X, Windows

'''Supported Operations:''' Hacktivation, jailbreaking

==Release text==
<center>limera1n, 6 months in the making 
iPhone 3GS, iPod Touch 3G, iPad, iPhone 4, iPod Touch 4G 
4.0-4.1 and beyond+++ 
limera1n is unpatchable 
untethered thanks to jailbreakme star '''comex''' 
brought to you by '''geohot''' 
hacktivates 
Mac coming in 7 years 
donations keep support alive 
zero pictures of my face</center>

==Credit==
* '''[[User:Geohot|geohot]]''' - The program itself, and the bootrom exploit.
* '''[[User:Comex|comex]]''' - The userland exploit that allows limera1n to run [[untethered jailbreak|untethered]].

==Changelog==
{| class="wikitable" style="border-collapse:collapse;" border="1"
|-
|<center>'''Version'''</center>
|<center>'''Release time'''</center>
|<center>'''MD5 Hash'''</center>
|<center>'''Change comment'''</center>
|-
|BETA 1
|9 Oct 2010 XX:XX GMT
|2f2b09a6ed5c5613d5361d8a9d0696b6
|First release.
|-
|BETA 2
|10 Oct 2010 XX:XX GMT
|a70dccb3dfc0e505687424184dc3d1ce
|Fixed kernel patching magic. Rerun BETA2+ over BETA1.
|-
|BETA 3
|10 Oct 2010 XX:XX GMT
|81730090f7de1576268ee8c2407c3d35
|Fixed an issue with [[N88ap|iPhone 3GS]] ([[iBoot-359.3.2|new bootrom]])
|-
|BETA 4
|10 Oct 2010 XX:XX GMT
|d901c4b3a544983f095b0d03eb94e4db
|Uninstall fixed, respring fixed
|-
|RC1
|11 Oct 2010 XX:XX GMT
|0622d99ffe4c25f75c720a689853845f
|out of beta! afc2, reliability improvements, no reboot for cydia, 2kb smaller
|-
|RC1b
|11 Oct 2010 XX:XX GMT
|fc6f7d696a57c3baede49bdff8a7f43f
|addresses an install issue, mainly with iPads
|-
|Final
|11 Oct 2010 23:XX GMT
|fc6f7d696a57c3baede49bdff8a7f43f
|(same as RC1b)
|}

==Technical Information==
=== Basics ===
* limera1n uses a different exploit to SHAtter.
* limera1n uses a bootrom exploit to achieve the [[tethered jailbreak]] and unsigned code execution.
* limera1n uses a userland exploit to make it untethered, which was developed by [[User:Comex|comex]].
* limera1n uses a hacktivation dylib to activate, even on devices already activated by iTunes

=== Exploits ===
Details of the exploits to follow.

=== Process ===
The jailbreak appears to execute something like the following (in no particular order):
* In recovery1,
"setenv debug-uarts 1
setenv auto-boot false
saveenv"
* In [[DFU Mode]], it uploads a [[payload]].
* In recovery2, it uploads another [[payload]] and its [[ramdisk]].
"setenv auto-boot true
reset
geohot done"

=== Interesting Messages ===
*
"geohot black is the new purple"
*
"blackra1n start: %d current IRQ mask is %8.8X
usb irq disabled...shhh
fxns found @ %8.8X %8.8X
found iBoot @ %8.8X
i'm back from IRQland...
3g detected, kicking nor
nor kicked
memcpy done
iBoot restored!!!
found command table @ %8.8X
cmd_geohot added
time to pray...%8.8X"
*
"2.2X send command(%d): %s
send exploit!!!
sent data to copy: %X
sent shellcode: %X has real length %X
never freed: %X
sent fake data to timeout: %X
sent exploit to heap overflow: %X
sending file with length: 0x%X Mingw runtime failure:
VirtualQuery failed for %d bytes at address %p Unknown pseudo relocation protocol version %d.
Unknown pseudo relocation bit size %d."

==Controversy==
The release of this jailbreak was specifically designed to pressure [[Chronic Dev (team)]] into not releasing SHAtter, but to instead implement the limera1n exploit into [[greenpois0n]]; after releasing limera1n, releasing SHAtter would uselessly disclose another bootrom exploit to Apple.

[[User:Geohot|Geohot]]'s rationale is that Apple already discovered, through internal testing, the limera1n exploit, making it very likely that it will be fixed in the next bootrom revision. Because [[iBoot]] code is present both in the bootrom and firmware, and because firmware is refreshed much more often that bootrom code, any fix in this code branch would appear first in firmware. [[User:Geohot|Geohot]] observed his limera1n exploit was closed in firmware and concluded that it would almost certainly be fixed in the next bootrom revision, whereas SHAtter still has a chance of remaining useful for an indefinite amount of time.

Limera1n's [[Untethered jailbreak|untethered]] userland exploit for iOS 4.0 and 4.1 was obtained by [[User:Geohot|geohot]] under questionable circumstances from [[User:Comex|comex]]. [[User:Comex|Comex]] did end up fixing the kernel patching code by beta2, so as to not break users' devices.

== Hacktivation ==
Limera1n will copy hacktivation.dylib to /usr/lib and change entries to com.apple.mobile.lockdown.plist, whether it has been activated using iTunes or not. This, while helpful to many, is also harmful to legitimate activators. For a guide on how to remove this hacktivation on iTunes activated devices, see the link below.

==External Links==
* [http://loadingchanges.com/wp-content/uploads/2010/10/limetime.jpg Picture of limera1n in action]
* [http://limera1n.com/ Official domain]
* [http://theiphonewiki.com/limera1n The iPhone Wiki Mirror]
* [http://www.mediafire.com/?5sovoo41rbcdspw Limera1n RC Beta2 Dump on Mediafire provided by iH8sn0w.]
* [http://www.pastie.org/1210054 Veence's explanation for release]
* [http://www.cmdshft.ipwn.me/blog/?p=555 Hacktivation removal guide.]

NOR

2010-10-30T03:50:12Z

LiNK: /* Hardware */

NOR typically refers to the NOR flash chip the application processor boots from. The baseband also uses a NOR flash.

==How to Access==
This can be accessed using a patched iBoot or a kernel hack. It can possibly be dumped using /dev/kmem

==Memory Map==
hope I did this right heh

<table border=1 width=100%>
<tr>
<td width=50%><center>Offset</center></td>
<td width=50%><center>Description</center></td>
</tr>
<tr>
<td width=50%><center>0x0</center></td>
<td width=50%><center>Configuration Data 
'''0x0''': "2GMI" fourcc 
'''0x4''': Block Size (0x40) 
'''0x8''': Images Section Location Offset 
'''0xC''': Images Section Location (In blocks) 
'''0x10''': Images Section Length 
'''0x30''': Checksum of this config data </center></td>
</tr>
<tr>
<td width=50%><center>0x4000</center></td>
<td width=50%><center>[[NOR (SysCfg)|SysCfg]] Section</center></td>
</tr>
<tr>
<td width=50%><center>0x8000</center></td>
<td width=50%><center>[[NOR (Firmware Images)|Images]] Section</center></td>
</tr>
<tr>
<td width=50%><center>0xFC000</center></td>
<td width=50%><center>[[NOR (NVRAM)|NVRAM]] Section</center></td>
</tr>
<tr>
<td width=50%><center>0xFE000</center></td>
<td width=50%><center>[[NOR (NVRAM)|NVRAM]] Section (copy)</center></td>
</tr>
</table>

==Hardware==
* [[M68ap|iPhone]] -- some CFI compliant parallel nor
* [[N82ap|iPhone 3G]] -- 1MB SPI NOR flash
* [[S5L8930|A4]]-based devices -- The NOR is replaced with a dedicated partition of NAND

Timeline

2010-10-28T17:14:55Z

LiNK:

==2010==
===October===
*October 27 -- [[iH8sn0w]] manages to jailbreak the iOS 4.2 beta.
*October 20 -- The [[iPhone Dev Team|Dev Team]] releases [[PwnageTool]] 4.1 which jailbreaks iOS 4.1 and 3.2.2 on every device available at the time of release. [http://blog.iphone-dev.org/post/1359246784/20102010-event (see blog post)]
*October 12 -- [[Chronic Dev (team)|Chronic Dev Team]] releases [[greenpois0n]] after switching its exploit from SHAtter to the exploit [[limera1n]] uses. By doing this, SHAtter remains undisclosed, meaning there is a chance that the 5th generation devices are vulnerable. (The exploit [[limera1n]] uses appears to be fixed in the [[iBoot]] revision found in iOS 4.2 beta 2, which means Apple probably knows about the vulnerability and the next [[bootrom]] revision may have it patched.)
*October 10 -- Following the first [[limera1n]] beta release, [[User:geohot|geohot]] released multiple versions, each fixing bugs affecting previous releases. [[Chronic Dev (team)|Chronic Dev Team]] officialy anounces that, in order to keep SHAtter undisclosed and possibly preserve it for 5th generation devices, [[greenpois0n]] would be delayed in order to incorporate this new exploit [[limera1n]] uses.
*October 9 -- In order to push [[Chronic Dev (team)|Chronic Dev Team]] to change the exploit used on [[greenpois0n]], [[User:geohot|geohot]] rushed out a beta version of [[limera1n]].
*October 8 -- [[User:Geohot|Geohot]] comes back to the scene with a new [[bootrom]] exploit believed to work on all devices, as shown on the resurrected [http://www.limera1n.com limera1n web site]. He prompts [[Chronic_Dev_(team)|Chronic Dev Team]] to use his exploit instead of SHAtter, but, since [[greenpois0n]] is already scheduled to October 10, it may be not possible. [[User:Geohot|Geohot]] ETA'd his [[limera1n]] release to October 11, if [[greenpois0n]] can't be changed to use this new exploit. This decision, however, would burn 2 [[bootrom]] exploits: SHAtter itself and the one used by [[limera1n]], which is patchable and may be a universal one.
*October 6 -- Chronic Dev Team issues expected ETA of [[greenpois0n]] as October 10, featuring the new SHAtter exploit for devices with the [[S5L8930]].

===September===
*September 30 -- [[User:MuscleNerd|MuscleNerd]] of the [[iPhone Dev Team]] posts [http://www.youtube.com/watch?v=adVp-IxcDHI the first video] of an [[K66ap|Apple TV 2G]] jailbroken via SHAtter.
*September 27 -- [[User:MuscleNerd|MuscleNerd]] of the [[iPhone Dev Team]] posts [http://www.youtube.com/watch?v=aoX1Q8ym2J8 the first video] of an [[N81ap|iPod touch 4G]] jailbroken via SHAtter.
*September 20 -- [[User:pod2g|pod2g]] discloses details about the [[usb_control_msg(0xA1, 1) Exploit‎]] here at The iPhone Wiki. It was used in [[redsn0w]] the following day.
*September 9 -- The existence of SHAtter is revealed. Further details were not released, however.
*September 8 -- Apple releases the [[N81ap|iPod touch 4G]], and iOS 4.1, closing the [[AT+XAPP Vulnerability]].
*September 1 -- Apple event. They announced the new [[N81ap|iPod touch 4G]], [[K66ap|Apple TV 2G]], iOS 4.1, and [[iTunes]] 10.

===August===
*August 12 -- [[Saurik]] releases the first version of PDF Patcher, which installs Apple's patch for the FreeType vulnerability (used in conjunction with other exploits by [[Star]]). It works on firmwares as far back as 2.x, and renders iOS 3.2.2 and 4.0.2 useless for jailbreakers. Jailbreaking and installing this patch is currently the only way for users of first generation iPod touches and iPhones to protect themselves against malicious use of the exploit.
*August 11 -- Apple releases iOS 4.0.2 for [[iPhone]]/[[iPod touch]] and iOS 3.2.2 for [[K48ap|iPad]] as a hotfix for [[Star]]'s exploits. [[Ultrasn0w]]'s exploit remains, since there's no [[Baseband Firmware|baseband]] update on those versions.
*August 3 -- Just before midnight in [[User:planetbeing|planetbeing]]'s timezone [[ultrasn0w]] has been released by the [[iPhone Dev Team]] to [[unlock]] the [[N90ap|iPhone 4]].
*August 1 -- [[User:Comex|comex]] releases [[Star]], a [[jailbreak]] for all iDevices with iOS 3.1.2 through 4.0.1.

===July===
*July 30 -- [[N90ap|iPhone 4]] is released in major countries (second wave).
*July 26 -- Jailbreaking is now officially legal in the U.S.A.: [http://www.eff.org/press/archives/2010/07/26 EFF Wins New Legal Protections for Cell Phone Jailbreakers and Unlockers]
*July 15 -- Apple releases iOS 3.2.1 and 4.0.1.

===June===
*June 24 -- [[N90ap|iPhone 4]] is launched.
*June 22 -- [[iPhone Dev Team]] releases [[PwnageTool]] 4.0 and later 4.0.1 for all devices on 4.0 except those with newer bootroms (some [[N72ap|iPod touch 2G]] and [[N88ap|iPhone 3GS]] devices, and all [[N18ap|iPod touch 3G]] and newer devices).
*June 21 -- [[iPhone Dev Team]] releases [[redsn0w]] 0.9.5 to jailbreak 4.0 on [[N82ap|iPhone 3G]] and [[N72ap|iPhone touch 2G]] ([[iBoot-240.4|old bootrom]]).
*June 21 -- [[iPhone Dev Team]] releases [[ultrasn0w]] 0.93, an unlock for baseband firmwares [[4.26.08]], [[5.11.07]], [[5.12.01]], and [[5.13.04]].
*June 21 -- Apple releases iOS 4.0
*June 19 -- [[User:Geohot|geohot]] holds a speech at the [[Nuit du hack 2010|Nuit du Hack]]

===May===
*May 3 -- Windows version of [[Spirit]] has been updated to not require Windows 98 compatibility mode to run and fixed a photo deletion issue.
*May 2 -- [[User:Comex|comex]] releases [[Spirit]], an [[untethered jailbreak]] for all iDevices with iOS 3.1.2 through 3.2.

===April===
*April 3 -- Apple releases the [[K48ap|iPad]].

===Feb===
*Feb 12 -- [[User:sherif hashim|sherif_hashim]] discovers [[AT+XAPP Vulnerability]] and passes it to [[User:MuscleNerd|MuscleNerd]], an elite member of the [[iPhone Dev Team]]
*Feb 2 -- Apple releases iOS 3.1.3, closing [[usb_control_msg(0x21, 2) Exploit|usb_control_msg(0x21, 2)]] vulnerability used by [[blackra1n]], [[redsn0w]], et. al.

==2009==
===November===
*November 3 -- [[User:Geohot|geohot]] releases [[blackra1n]] RC3, a software jailbreak for all devices. Includes a new unlock for baseband [[5.11.07]] called [[blacksn0w]] and is also noticeably faster than previous versions.

===October===
*October 11 -- [[User:Geohot|geohot]] releases [[blackra1n]] RC1, a 30 second software jailbreak for all devices, including a [[tethered jailbreak]] for the [[N18ap|iPod touch 3G]], and [[N88ap|iPhone 3GS]] and [[N72ap|iPod touch 2G]] units with newer bootrom revisions.

===September===
* September 24 -- [[User:iH8sn0w|iH8sn0w]] discovers the [[AT+XEMN Heap Overflow|AT+XEMN]] crash independently.
* September 9 -- The [[N18ap|iPod touch 3G]] with [[S5L8922]] processor is released. [[N72ap|iPod touch 2G]] units continue shipping, but with [[iBoot-240.5.1|a new bootrom]]. [[N88ap|iPhone 3GS]] units also begin shipping with [[iBoot-359.3.2|a new bootrom]]. These are no longer vulnerable to the [[0x24000 Segment Overflow]].
* Apple releases iOS 3.1/3.1.1 (7C144/7C145), closing the [[iBoot Environment Variable Overflow]] and [[AT+XLOG Vulnerability|AT+XLOG]] + [[AT+FNS]] Baseband Exploits.

===July===
* July 14 -- [[User:Geohot|geohot]] releases [[purplesn0w]], a software unlock for the [[X-Gold 608]] using [[AT+XLOG Vulnerability|the same exploit as ultrasn0w]], but handled differently. Minutes later, an explanation and source code was posted.
* July 7 -- The [[iPhone Dev Team]] updates [[redsn0w]] and [[ultrasn0w]] to version 0.8, now with [[N88ap|iPhone 3GS]] support. Saurik also updates [[WinterBoard]] to support the [[N88ap|iPhone 3GS]].
* July 3 -- [[User:Geohot|geohot]] releases [[purplera1n]], a software jailbreak for the [[N88ap|iPhone 3GS]].

===June===
* June 28 -- [[User:Geohot|geohot]] posts pictures on his blog of the first fully jailbroken [[N88ap|iPhone 3GS]].
* June 25 -- It's discovered that [[N88ap|iPhone 3GS]] is vulnerable to the [[0x24000 Segment Overflow]].
* June 24 -- The [[iPhone Dev Team]] releases [[ultrasn0w]], an [[unlock]] for [[X-Gold 608]] thanks to [[AT+XLOG Vulnerability|a new exploit]] discovered by [[User:Oranav|Oranav]].
* June 23 -- [[User:Geohot|geohot]] announces he's found a new exploit in [[iBoot]] he calls [[purplera1n]].
* June 19 -- Release of [[N88ap|iPhone 3GS]] to the public and the release of [[PwnageTool]] 3.0 and [[redsn0w]] for jailbreaking devices running iOS 3.0
* June 17 -- Apple releases iOS 3.0.
* June 8 -- Apple announces the [[N88ap|iPhone 3GS]].

===March===
* March 10 -- Information about the [[0x24000 Segment Overflow]] exploit used for the [[N72ap|iPod touch 2G]] [[untethered jailbreak]] is released thanks to the combined work of [[chronic]], [[CPICH]], [[posixninja]], [[pod2g]], [[ius]], [[planetbeing]], [[User:MuscleNerd|MuscleNerd]], and co. after being leaked and sold by [[NitroKey]]. To prevent users wasting their money on a stolen exploit, the Hybrid DevTeam decided to release it immediately.

===January===
* January 31 -- The [[iPhone Dev Team]] released [[redsn0w Lite]], a [[tethered jailbreak|tethered]] [[N72ap|iPod touch 2G]] [[jailbreak]]. It combines the [[ARM7 Go]] vulnerability with the well-established [[pwnage]] flow for other Apple mobile devices. It was bundled in a way that allowed usage on iOS 2.2.1 by uploading [[iBoot]] from iOS 2.1.1, which is vulnerable to [[ARM7 Go]], to the device while in [[DFU Mode]].
* January 29 -- Apple releases iOS 2.2.1, closing the [[AT+stkprof]] exploit.
* January 25 -- [[0wnboot]] is released to [http://code.google.com/p/chronicdev/ chronicdev google code page], thanks to [[AriX]], [[User:ChronicDev|chronic]], [[CPICH]], [[westbaer]], [[ius]], [[pod2g]], the rest of the iPod devel crew on IRC, and to the #iphone-hax lab rats. Within days, [[AriX]] and the [[Chronic Dev (team)|Chronic Dev Team]] got a ramdisk booting for a [[tethered jailbreak]].
* January 17 -- [[User:MuscleNerd|MuscleNerd]] of the [[iPhone Dev Team]] [https://twitter.com/MuscleNerd/status/1127346766 shows a video demo] of the first jailbroken [[N72ap|iPod touch 2G]].
* January 16 -- [[ARM7 Go]] vulnerability disclosed where else but here on The iPhone Wiki, for developers to poke and prod at.
* January 15 -- The [[iPhone Dev Team]] [https://twitter.com/iphone_dev/status/1120595069 tweets the VFDecrypt key] for iOS 2.2 on [[N72ap|iPod touch 2G]], demonstrating for the first time that unsigned code can now be run on that device.
* January 1 -- The [[iPhone Dev Team]] releases [[yellowsn0w]] 0.9 beta for baseband [[2.28.00]].

==2008==

===December===
* December 27 -- [[25C3_presentation_Hacking_the_iPhone|25C3 presentation "Hacking the iPhone"]]
* December 21 -- [[User:MuscleNerd|MuscleNerd]], of the [[iPhone Dev Team]] does a live demo of the 3G unlock, dubbed as [[yellowsn0w]]: http://qik.com/video/729275

===November===
* November 21 -- Apple releases iOS 2.2.

===September===
* September 9 -- Apple releases iOS 2.1. [[N72ap|iPod touch 2G]], which no longer had the [[Pwnage 2.0]] exploit, is revealed.

===August===
* August 18 -- Apple releases 2.0.2 fimware. [[iPhone Dev Team]] releases [http://wikee.iphwn.org/news:pwnage20announcement QuickPwn], a 2.x [[pwnage]]/ramdisk combination exploit that allows jailbreaking without needing to create custom IPSWs.
* August 4 -- Apple releases 2.0.1 fimware

===July===
* July 22 -- [[TA_Mobile]] hardware dumps the 3G baseband (bootloader 5.8 & FW 1.45.00) by desoldering the [[NOR]].
* July 19 -- [[iPhone Dev Team]] releases [[PwnageTool]] 2.0, jailbreaking and unlocking the 2.0 software on the [[M68ap|iPhone 2G]] and jailbreaking iOS 2.0 on the [[N82ap|iPhone 3G]] and [[N45ap|iPod touch]].
* July 15 -- Apple releases iOS 1.1.5, the last of the 1.x firmwares
* July 11 -- [[N82ap|iPhone 3G]] is released. Apple releases iOS 2.0 and MobileMe on the same date, resulting in server issues.

===June===
* June 9 - [[N82ap|iPhone 3G]] is announced at [[WWDC]] '08.

===April===
* April 3 -- [[iPhone Dev Team]] releases [[PwnageTool]] 1.0, making use of the [[pmdx exploit]] (to patch RSA checks out of the [[kernel]], to write unsigned to [[NOR]])

===March===
* March 12 -- [[iPhone Dev Team|Dev team]] releases dual-boot jailbreak method, only to be silently fixed in 2.0.
* March 4 -- [[User:N000b|George Zhu (n000b)]] releases [[iLiberty / iLiberty+]].

===February===
* February 28 -- [[Cydia Application|Cydia]] is released as an open-source alternative to [[Installer.app]], and prepares to take over the jailbreak application scene upon 2.0's release.
* February 26 -- Apple releases iOS 1.1.4.
* February 11 -- [[User:Zibri|Zibri]] leaks the [[Ramdisk Hack]] in [[ZiPhone]], the first all-in-one unlock, activate, jailbreak solution.
* February 8 -- [[User:Geohot|geohot]] releases software unlock for 4.6. Apple states 25% of phones were never activated with AT&T.

===January===
* January 28 -- [[iPhone Dev Team]] releases [[Soft Upgrade]] jailbreak for 1.1.3.
* January 24 -- [[Nate True]] releases a version of [[iBrickr]] that used the [[Soft Upgrade]] method to jailbreak 1.1.3 for [[M68ap|iPhones]].
* January 18 -- [[User:Geohot|Geohot]] and his friends [http://iphonejtag.blogspot.com/2008/01/112-otb-unlocked.html unlocked 1.1.2 OTB 4.6 by test point], the unbeatable version at that time.
* January 18 -- [[iPhone Dev Team]] posts YouTube video of a jailbroken 1.1.3, which was made possible by the dual boot jailbreak from [[bgm]].
* January 15 -- Apple releases iOS 1.1.3, closing the [[Mknod]] exploit. In addition, everything now runs as "mobile" instead of "root."

== 2007 ==
===November===
* November 15 -- [[Baseband Bootloader|Baseband bootloader]] 4.6 is found on new [[M68ap|iPhone]]s, which initially had no [[unlock]].
* November 12 -- Apple releases iOS 1.1.2, closing the [[LibTiff]] and [[Symlinks]] exploits.
* November 2 -- [[JailbreakMe|AppSnapp]] is released, bringing jailbreaking to the mainstream iPhone user.

===October===
* October 23 -- iPhone-Elite Team releases the [[Virginizer]].
* October 14 -- [[User:AriX|AriX]] releases iJailBreak, the first automated [[n45ap|iPod touch]] jailbreak for the Mac.
* October 12 -- [[User:planetbeing|planetbeing]] releases touchFree, the first automated [[N45ap|iPod touch]] jailbreak.
* October 10 -- niacin, [[cmw]], and dre release the LibTiff exploit to jailbreak the [[N45ap|iPod touch]], which is later adapted for use in [[JailbreakMe|AppSnapp]].

===September===
* September 27 -- Apple releases iOS 1.1.1.
* September 11 -- [[iPhone Dev Team]] releases [[iUnlock]], first free software unlock.
* September 10 -- [[IPSF]] releases first paid software unlock.
* September 9 -- Apple announces the [[N45ap|iPod touch]] at a media event.

===August===
* August 23 -- [[User:Geohot|geohot]] and team release [[hardware unlock]] method.
* August 21 -- [[Installer.app]] is released by Nullriver, first GUI apps are distributed.

===July===
* July 23 -- First phones are used with other carriers by means of [[SIM hacks]].
* July 20 -- nightwatch adapts a [[toolchain]] to the iPhone. The first apps are compiled.
* July 9 -- [[iPhone Dev Team]] releases a [[jailbreak]] method. The first use of this is ringtones.
* July 3 -- DVD Jon first cracks [[activation]]. People can use the apps on the phone without a subscription.

===June===
* June 29 -- [[M68ap|iPhone]] is released. World's most hyped consumer product.
* June 26 -- The [[iPhone Dev Team]] was formed.

Accelerometer

2010-10-28T16:29:35Z

LiNK:

This chip helps detect movement in the [[iPad]], [[iPhone]], and [[iPod touch]]. Newer devices use this as well as a [[gyroscope]], which allows precise motion and 6-axis movement detection.

Talk:/private/var/root

2010-10-26T03:38:33Z

LiNK: New page: I removed the internal link on demo.mov since it doesn't exist. ~~~~

I removed the internal link on demo.mov since it doesn't exist. [[User:LiNK|LiNK]] 03:38, 26 October 2010 (UTC)

/private/var/root

2010-10-26T03:38:03Z

LiNK:

== Summary ==
The [[wikipedia:home_directory|home directory]] of the root user. As of 1.1.3, user data is not stored here, but in [[/private/var/mobile]].

== Parents ==
* [[/]]
* [[/private]]
* [[/private/var]]

== Children ==
=== Files ===
Demo.mov - Used in Apple Stores on iOS 1.1.2 and older to display a video when the device wasn't in use. (1.1.3 and newer use the mobile user, not root.)

=== Folders ===
*[[/private/var/root/library]]
*[[/private/var/root/media]]

Accelerometer

2010-10-25T14:35:07Z

LiNK:

This chip helps detect movement in the [[iPad]], [[iPhone]], and [[iPod touch]]. Newer devices also include a [[gyroscope]], which allows 6-axis movement detection. this chip is a STmicroelectronics lis331DL [http://www.st.com/stonline/books/pdf/docs/14699.pdf]

Talk:/dev

2010-10-24T22:47:18Z

LiNK: New page: Is this page really that important? I think this should be merged into something else (sans the folder structure). ~~~~

Is this page really that important? I think this should be merged into something else (sans the folder structure). [[User:LiNK|LiNK]] 22:47, 24 October 2010 (UTC)

/dev

2010-10-24T22:27:25Z

LiNK: /* Summary */

== Summary ==

[[Device Nodes]] are here, as with any other standard UNIX system. The folder cannot be written to.

== Parents ==

[[/]]

== Children ==

[[/dev/zero]]

[[/dev/vn1]]

[[/dev/vn0]]

[[/dev/urandom]]

[[/dev/uart.iap]]

[[/dev/uart.bluetooth]]

[[/dev/ttyp7]]

[[/dev/ttyp6]]

[[/dev/ttyp5]]

[[/dev/ttyp4]]

[[/dev/ttyp3]]

[[/dev/ttyp2]]

[[/dev/ttyp1]]

[[/dev/ttyp0]]

[[/dev/tty.iap]]

[[tty.bluetooth]]

[[/dev/tty]]

[[/dev/sha1_0]]

[[/dev/rdisk0s2]]

[[/dev/rdisk0s1]]

[[/dev/rdisk0]]

[[/dev/random]]

[[/dev/ptyp7]]

[[/dev/ptyp6]]

[[/dev/ptyp5]]

[[/dev/ptyp4]]

[[/dev/ptyp3]]

[[/dev/ptyp2]]

[[/dev/ptyp1]]

[[/dev/ptyp0]]

[[/dev/ptmx]]

[[/dev/pf]]

[[/dev/null]]

[[/dev/klog]]

[[/dev/io8logmt]]

[[/dev/io8log]]

[[/dev/disk0s2]]

[[/dev/disk0s1]]

[[/dev/disk0]]

[[/dev/cu.iap]]

[[/dev/cu.bluetooth]]

[[/dev/console]]

[[/dev/btwake]]

[[/dev/btreset]]

[[/dev/bpf3]]

[[/dev/bpf2]]

[[/dev/bpf1]]

[[/dev/bpf0]]

[[/dev/aes_0]]

IBoot

2010-10-24T21:49:34Z

LiNK:

{{DISPLAYTITLE:iBoot}}
{{Disambig}}

iBoot can stand for two things, both have names that start with [[iBoot]] and distinct version numbers:
*[[Bootrom]] (version numbers between [[iBoot-240.4]] and [[iBoot-574.4]])
*[[iBoot (Bootloader)|The stage 2 bootloader, called iBoot]] (as of the last update to this page, version numbers are between [[iBoot-99]] and [[iBoot-931.44.21]])
*[[LLB]]
*[[iBEC]]
*[[iBSS]]

IBSS commands

2010-10-24T21:48:09Z

LiNK:

{{DISPLAYTITLE:iBSS commands}}
You can access this command list by typing "help" after [[iBSS]] is uploaded.

bootx boot a kernel cache at specified address
tsys boot into tsys (if present)
diags boot into diagnostics (if present)
setpicture set the image on the display
bgcolor set the display background color
poweroff power off the device
halt halt the system (good for JTAG)
reboot reboot the device
run use contents of enironment var as script
script run script at specific address
go jump directly to address
mws memory write - string
mwb memory write - 8bit
mwh memory write - 16bit
mw memory write - 32bit
mdb memory display - 8bit
mdh memory display - 16bit
md memory display - 32bit
ramdisk create a radisk from the specified address
powernvram Access Power NVRAM.
charge Manage the charger chip.
devicetree create a device tree from the specified address
saveenv save current environment to flash
syscfg flash SysCfg inspection
chunk chunk a file
arm7_stop stop the arm7
arm7_go start the arm7 with a downloaded image
iic iic read/write
usb run a USB command
sha1 SHA-1 hash of memory
crc POSIX 1003.2 checksum of memory
clearenv clear all environment variables
setenv set an environment variable
printenv print one or all environment variables
image flash image inspection
pki PKI
bdev block device commands

==Commands from [[iBoot]]==
An asterisk (*) next to a name means that the command is disabled.

JOB_SPEC [&] (( expression ))
. filename [arguments] :
[ arg... ] [[ expression ]]
alias [-p] [name[=value] ... ] bg [job_spec ...]
bind [-lpvsPVS] [-m keymap] [-f fi break [n]
builtin [shell-builtin [arg ...]] caller [EXPR]
case WORD in [PATTERN [| PATTERN]. cd [-L|-P] [dir]
command [-pVv] command [arg ...] compgen [-abcdefgjksuv] [-o option
complete [-abcdefgjksuv] [-pr] [-o continue [n]
declare [-afFirtx] [-p] [name[=val dirs [-clpv] [+N] [-N]
disown [-h] [-ar] [jobspec ...] echo [-neE] [arg ...]
enable [-pnds] [-a] [-f filename] eval [arg ...]
exec [-cl] [-a name] file [redirec exit [n]
export [-nf] [name[=value] ...] or false
fc [-e ename] [-nlr] [first] [last fg [job_spec]
for NAME [in WORDS ... ;] do COMMA for (( exp1; exp2; exp3 )); do COM
function NAME { COMMANDS ; } or NA getopts optstring name [arg]
hash [-lr] [-p pathname] [-dt] [na help [-s] [pattern ...]
history [-c] [-d offset] [n] or hi if COMMANDS; then COMMANDS; [ elif
jobs [-lnprs] [jobspec ...] or job kill [-s sigspec | -n signum | -si
let arg [arg ...] local name[=value] ...
logout popd [+N | -N] [-n]
printf [-v var] format [arguments] pushd [dir | +N | -N] [-n]
pwd [-LP] read [-ers] [-u fd] [-t timeout] [
readonly [-af] [name[=value] ...] return [n]
select NAME [in WORDS ... ;] do CO set [--abefhkmnptuvxBCHP] [-o opti
shift [n] shopt [-pqsu] [-o long-option] opt
source filename [arguments] suspend [-f]
test [expr] time [-p] PIPELINE
times trap [-lp] [arg signal_spec ...]
true type [-afptP] name [name ...]
typeset [-afFirtx] [-p] name[=valu ulimit [-SHacdfilmnpqstuvx] [limit
umask [-p] [-S] [mode] unalias [-a] name [name ...]
unset [-f] [-v] [name ...] until COMMANDS; do COMMANDS; done
variables - Some variable names an wait [n]
while COMMANDS; do COMMANDS; done { COMMANDS ; }

User:LiNK

2010-10-24T21:47:17Z

LiNK:

I'm an 18-year-old iPhone hacker/developer.

Add me on Game Center: Ltamake

Twitter: [http://twitter.com/ltamake Follow me!]

Accelerometer

2010-10-24T21:45:45Z

LiNK:

This chip helps detect movement in the [[iPhone]], [[iPod Touch]], and [[iPad]]. In the iPhone 4, the chip is aided by the [[gyroscope]], which allows 6-axis movement.

Gyroscope

2010-10-24T21:37:31Z

LiNK:

This is present in the [[N90ap|iPhone 4]] and the [[N81ap|iPod touch 4G]]. It detects movements far more precise than the [[accelerometer]], and creates 6-axis motion sensing combined with the Compass (iPhone-only) and the accelerometer. The chip is a STMicroelectronics AGD1 2022 FP6AQ.

Gyroscope

2010-10-24T21:33:41Z

LiNK:

User talk:Geohot

2010-10-23T19:01:12Z

LiNK:

== Future of this Wiki ==

[[Geohot]] is the founder of this wiki. Now that he has retired (or whatever) I would be interested to know how this Wiki continues. I'm a little scared that he could just turn it off. Maybe we should make some backups now? Or can geohot or a close insider provide some infos about the future of this Wiki? If geohot needs someone to take over this project, I would be happy to do so (and probably many others also). It would be awful to see all our contributions fade away. A clear statement by any insider would help. Thanks. --[[User:Http|http]] 18:58, 13 July 2010 (UTC)

I currently have no plans to shut down this wiki. Rest assured that if I do, I will make a backup available online. --[[User:Geohot|geohot]] 19:17, 13 July 2010 (UTC)

Thanks for clarification. This helps a lot. --[[User:Http|http]] 22:39, 13 July 2010 (UTC)

== Access to [http://iphonejtag.blogspot.com/ blog] archives ==
Will you post the information on your initial iPhone 2G unlock anywhere? This used to be on your blog (in the archives) and was quite fascinating... :( [[User:D235j|D235j]] 01:41, 14 July 2010 (UTC)

== Other ==

You made a rational decision leaving the jailbreak community. After all the crap you had to take from people I dont blame you. Im sorry for ever adding to the BS you deal with on a day-to-day basis. [[User:Leobruh|Leobruh]] 22:42, 13 July 2010 (UTC)!

== Blog ==
Hey mate, do you have any plans to make your blog public again? There was a lot of good information on there and it would be an official source of information and updates from you!

Best! =) [[User:LiNK|LiNK]] 19:01, 23 October 2010 (UTC)

Talk:S5L8930

2010-10-03T22:41:55Z

LiNK: /* New Untethered Kernel Exploit? */

==Merge?==
Should this and the A4 page be merged? They're practically the same in content. --[[User:Dialexio|Dialexio]] 17:18, 6 April 2010 (UTC)
:A4 is just the public name for the s5l8930, no? I say we merge it and make A4 redirect to this page, with a /very minor/ explanation on why it redirects you to this page. ~Drake
::This was from when the pages were separate entities. The problem has since been resolved. :) --[[User:Dialexio|Dialexio]] 04:13, 20 September 2010 (UTC)

==Is there an iBoot exploit?==

Geohot got the iPad to boot verbosely, and the VFDecrypt and other fun keys.

This almost certainly means there is an iboot/llb exploit out there, no? Can the keys be gotten with just a tethered bootrom exploits?

[[User:Iemit737|Iemit737]] 21:39, 25 August 2010 (UTC)

it could be possible he found a bootrom exploit that was pwnage 2 like however the real pwnage exploits the unchecked LLB but apple could have made a mistake with the new shsh check --[[User:Liamchat|liamchat]] 19:20, 29 August 2010 (UTC)

Are we sure that geohot even had an untethered bootrom exploit? He had denied that "pwned4life" or whatever it was was real. [[User:LiNK|LiNK]] 02:07, 20 September 2010 (UTC)

UPDATED:There /is/ a bootrom exploit. It's probably tethered (for now). It's a code-execution exploit, as you can't get keys without executing code. Hope this helps. ~Drake
::A bootrom exploit tethered or untethered can be used to boot verbosely, SIDEBAR: people take tethered/untethered as meaning far too much, all tethered/untethered means is you need to plug in to something to boot, it has absolutely NO bearing on any other capability --[[User:Lilstevie|Lilstevie]] 14:26, 20 September 2010 (UTC)

==New Untethered Kernel Exploit?==
http://blog.iphone-dev.org/post/1197198297/shattered-ipod-touch-4g
If you look closely in this video, upon respring there is some distortion in the top left corner. I'm guessing there is another one of those Spirit/Star type exploits in one of the frameworks that allows some shellcode to get stuck into the framebuffer to provide an untethered jailbreak... Which is awesome... [[User:Iemit737|Iemit737]] 22:59, 27 September 2010 (UTC)

i think it is a problem with [[PwnageTool]] it is not ready for [[Iphone_4]] and [[N81ap]] yet and there where the same problem's with [[Sn0wbreeze]] --[[User:Liamchat|liamchat]] 17:19, 28 September 2010 (UTC)

*That's not correct at all. :/ It has to do with the exploit itself, not the program that is used to jailbreak. [[User:LiNK|LiNK]] 22:40, 3 October 2010 (UTC)

The problem is not really with pwnageTool because they said they got the touch 4G to restore a custom IPSW. The issue is getting a nice exploit for the main boot chain that's not tethered [[User:Iemit737|Iemit737]] 22:08, 28 September 2010 (UTC)

Talk:S5L8930

2010-10-03T22:40:13Z

LiNK: /* New Untethered Kernel Exploit? */

==Merge?==
Should this and the A4 page be merged? They're practically the same in content. --[[User:Dialexio|Dialexio]] 17:18, 6 April 2010 (UTC)
:A4 is just the public name for the s5l8930, no? I say we merge it and make A4 redirect to this page, with a /very minor/ explanation on why it redirects you to this page. ~Drake
::This was from when the pages were separate entities. The problem has since been resolved. :) --[[User:Dialexio|Dialexio]] 04:13, 20 September 2010 (UTC)

==Is there an iBoot exploit?==

Geohot got the iPad to boot verbosely, and the VFDecrypt and other fun keys.

This almost certainly means there is an iboot/llb exploit out there, no? Can the keys be gotten with just a tethered bootrom exploits?

[[User:Iemit737|Iemit737]] 21:39, 25 August 2010 (UTC)

it could be possible he found a bootrom exploit that was pwnage 2 like however the real pwnage exploits the unchecked LLB but apple could have made a mistake with the new shsh check --[[User:Liamchat|liamchat]] 19:20, 29 August 2010 (UTC)

Are we sure that geohot even had an untethered bootrom exploit? He had denied that "pwned4life" or whatever it was was real. [[User:LiNK|LiNK]] 02:07, 20 September 2010 (UTC)

UPDATED:There /is/ a bootrom exploit. It's probably tethered (for now). It's a code-execution exploit, as you can't get keys without executing code. Hope this helps. ~Drake
::A bootrom exploit tethered or untethered can be used to boot verbosely, SIDEBAR: people take tethered/untethered as meaning far too much, all tethered/untethered means is you need to plug in to something to boot, it has absolutely NO bearing on any other capability --[[User:Lilstevie|Lilstevie]] 14:26, 20 September 2010 (UTC)

==New Untethered Kernel Exploit?==
http://blog.iphone-dev.org/post/1197198297/shattered-ipod-touch-4g
If you look closely in this video, upon respring there is some distortion in the top left corner. I'm guessing there is another one of those Spirit/Star type exploits in one of the frameworks that allows some shellcode to get stuck into the framebuffer to provide an untethered jailbreak... Which is awesome... [[User:Iemit737|Iemit737]] 22:59, 27 September 2010 (UTC)

i think it is a problem with [[PwnageTool]] it is not ready for [[Iphone_4]] and [[N81ap]] yet and there where the same problem's with [[Sn0wbreeze]] --[[User:Liamchat|liamchat]] 17:19, 28 September 2010 (UTC)

*That's not correct at all. :/ [[User:LiNK|LiNK]] 22:40, 3 October 2010 (UTC)

The problem is not really with pwnageTool because they said they got the touch 4G to restore a custom IPSW. The issue is getting a nice exploit for the main boot chain that's not tethered [[User:Iemit737|Iemit737]] 22:08, 28 September 2010 (UTC)

Talk:S5L8930

2010-09-20T02:07:36Z

LiNK: /* Is there an iBoot exploit? */

==Merge?==
Should this and the A4 page be merged? They're practically the same in content. --[[User:Dialexio|Dialexio]] 17:18, 6 April 2010 (UTC)

==Is there an iBoot exploit?==

Geohot got the iPad to boot verbosely, and the VFDecrypt and other fun keys.

This almost certainly means there is an iboot/llb exploit out there, no? Can the keys be gotten with just a tethered bootrom exploits?

[[User:Iemit737|Iemit737]] 21:39, 25 August 2010 (UTC)

it could be possible he found a bootrom exploit that was pwnage 2 like however the real pwnage exploits the unchecked LLB but apple could have made a mistake with the new shsh check --[[User:Liamchat|liamchat]] 19:20, 29 August 2010 (UTC)

Are we sure that geohot even had an untethered bootrom exploit? He had denied that "pwned4life" or whatever it was was real. [[User:LiNK|LiNK]] 02:07, 20 September 2010 (UTC)

User:LiNK

2010-09-11T23:36:04Z

LiNK:

An iPhone hacker. Member of f1redev. British idiot with an ugly hairdo.

Add me on Game Center: Ltamake

Twitter: [http://twitter.com/ltamake Here]

User:LiNK

2010-09-11T23:35:42Z

LiNK:

An iPhone hacker. Member of f1redev. British idiot with an ugly hairdo.

Add me on Game Center: Ltamake
Twitter: [http://twitter.com/ltamake Here]

User:LiNK

2010-09-03T07:22:21Z

LiNK: New page: An iPhone hacker. Member of f1redev. British idiot with an ugly hairdo.

An iPhone hacker. Member of f1redev. British idiot with an ugly hairdo.