Difference between revisions of "Talk:Firmware Keys"

From The iPhone Wiki
Jump to: navigation, search
(copied from deleted talk page)
m (added sign)
 
(101 intermediate revisions by 12 users not shown)
Line 1: Line 1:
  +
{{Talk Archive}}
== 2.0 beta 8 key? ==
 
   
  +
== iKeys ==
Would anyone, by any chance, have the key for 2.0 build 5A345? For some reason, it's missing on this page. -[[User:Dialexio|Dialexio]] 16:13, 17 August 2008 (UTC)
 
  +
I was wondering if anyone had any info on "iKeys". It's mentioned [http://pastie.org/1161868 here] at the bottom. I'd imagine it's like GenPass but just wondering. Any info is appreciated. --[[User:OMEGA_RAZER|OMEGA_RAZER]]
 
== VFDecrypt error ==
 
 
When I try with the command I get a warning message.It shows that cygcrypto-0.9.8.dll was not found.I've searched this file but it seems I can't find it.Thanks for helping me in advance. {{unsigned|Delstam|14:30, August 1, 2009 (UTC)}}
 
:This DLL is part of Cygwin. You can get it here: [http://www.mirrorservice.org/sites/sourceware.org/pub/cygwin/release/openssl/openssl-0.9.8k-1.tar.bz2/usr/bin/cygcrypto-0.9.8.dll?extract=true] --[[User:Blackbox|Blackbox]] 14:45, 1 August 2009 (UTC)
 
::Thanks {{unsigned|Delstam|14:58, August 1, 2009 (UTC)}}
 
:::Hey, I need this file too, but the link seems to now be broken. I just got it from [http://www.mediafire.com/?wznnyt5izmu here] instead. Just thought I'd make a note in case anyone else needs it. [[User:MaybachMan|MaybachMan]] 13:17, 17 August 2010 (UTC)
 
:::: ...Cygwin1.dll can also be gotten [http://www.dll-files.com/pop.php?dll=cygwin1 here.] {{unsigned|MaybachMan|13:27, August 17, 2010 (UTC)}}
 
:::::I'm working on getting my fork of VFDecrypt running on Windows. Soon as I get it compiled, I'll post the download link to a /native/ Windows binary. --[[User:Dra1nerdrake|dra1nerdrake]] 17:35, 17 August 2010 (UTC)
 
 
==VFDecrypt for Mac link==
 
 
The link in the article is broken, does anyone have a working one? [[User:MaybachMan|MaybachMan]] 11:39, 19 August 2010 (UTC)
 
 
:Use mine from github and build it with 'make linux'. It (should) work. If it does, please post back here so I can update the program. If it doesn't, post back here with the error and I'll try to debug it. --[[User:Dra1nerdrake|dra1nerdrake]] 21:13, 19 August 2010 (UTC)
 
''vfdecrypt.c:42:22: error: byteswap.h: No such file or directory''
 
''make: *** [linux] Error 1''
 
:-[[User:MaybachMan|MaybachMan]] 10:44, 20 August 2010 (UTC)
 
 
==iKeys==
 
I was wondering if anyone had any info on "iKeys". It's mentioned [http://pastie.org/1161868 here] at the bottom. I'd Imagine it's like GenPass but just wondering. Any info is appreciated. --[[User:OMEGA_RAZER|OMEGA_RAZER]]
 
 
== Remove Request ==
 
 
As someone mentioned on the [[Talk:VFDecrypt_Keys:_3.x_BETA#STOP|Firmware 3.x Beta talk page]], I want to request that the whole section "Firmware" on this page here gets removed and all mentioned pages deleted as well. The information there (the VFDecrypt keys) should go into their appropriate firmware page. Or do we still need all VFDecrypt keys (only) together also? If yes, then at least it should be cleaned up and these pages should mention that these are duplicates for the sake of grouping. --[[User:Http|http]] 10:17, 23 October 2010 (UTC)
 
: I think we should just protect the pages [[VFDecrypt Keys:_1.x]], [[VFDecrypt Keys: 2.x]], [[VFDecrypt Keys: 3.x]], and [[VFDecrypt Keys: 3.x BETA]]. And if someone discovers a key for those Firmwares we should add it to the talk page for an admin to add. --[[User:Balloonhead66|Balloonhead66]] 15:03, 23 October 2010 (UTC)
 
 
These pages are really chaotic. For the 1.x and 2.x pages, it is unknown if they are for the iPhone or iPod touch (or for both). We can just assume something, or try. The 3.x pages contain not only vfdecrypt keys, but some ramdisk keys as well. And some have beta mixed within, others not. I assume that all keys are on their respective firmware page already. If not, then we should create the missing pages and link them to the [[Firmware]] or [[Beta Firmware]] page. I'll start with that some time if I find the time - feel free to help. But then, if all keys are available on their firmware page, why would we still need these pages? I still request to delete them. We could add a cross table on this page with firmware vs. device and in each cell a link, so that we easily find the page with the keys. I think I'll add this table right away. Then there's no need for these pages anymore. Please discuss here if you agree to remove them afterwards. -- [[User:Http|http]] 20:14, 29 October 2010 (UTC)
 
 
 
I don't think we should delete the key pages until the table shows all blue links so that way we don't trash any keys on accident. --[[User:Balloonhead66|Balloonhead66]] 15:33, 30 October 2010 (UTC)
 
 
== Download Table ==
 
 
Does everyone link my table in the download section? --[[User:Balloonhead66|Balloonhead66]] 18:09, 23 October 2010 (UTC)
 
:The x86 version of VFDecrypt also works on x64, should note that. --[[User:JacobVengeance|JakeAnthraX]] 01:04, 27 October 2010 (UTC)
 
   
 
== Exploit? ==
 
== Exploit? ==
am i to understand that a low level exploit is needed to get the vfdecrypt key???
+
Am I to understand that a low level exploit is needed to get the VFDecrypt key? --[[User:Shengis14|Shengis14]] 18:50, 8 October 2010 (UTC)
  +
:No, that's not completely true. :P One has to manage to get the key/IV for a ramdisk, and then use [[GenPass]] to get the VFDecrypt key. --[[User:Dra1nerdrake|dra1nerdrake]] 21:27, 8 October 2010 (UTC)
--[[User:Shengis14|Shengis14]] 18:50, 8 October 2010 (UTC)
 
  +
::How would someone like myself go about geting the key/IV for a ramdisk? --[[User:Shengis14|Shengis14]] 22:13, 8 October 2010 (UTC)
  +
:::You would need (at the very least) an iBoot exploit and a payload to upload that is able to access the AES engine of the device. --[[User:OMEGA RAZER|OMEGA RAZER]] 22:16, 8 October 2010 (UTC)
  +
::::It's just that one of the reasons I'm confused is why there is a sudden jump in the number of keys for the iPod touch 3G on 4.0-4.1?
  +
:::::There isn't an exploit that is iBoot level or lower for that device. --[[User:Shengis14|Shengis14]] 22:50, 8 October 2010 (UTC)
   
  +
== New page? ==
No, that's not completely true. :P One has to manage to get the key/iv for an update/restore ramdisk, and then use [[Genpass]] to get a VFDecrypt key. --[[User:Dra1nerdrake|dra1nerdrake]] 21:27, 8 October 2010 (UTC)
 
  +
I think we should make a new page detailing how to utilise [[User:Gojohnnyboi|Gojohnnyboi]]'s AES payload to get the keys including screenies on opening up an img3 in a hex editor and getting the [[KBAG]] etc. Then the keys won't be left to the main devs and [[User:iH8sn0w|iH8sn0w]] to post. Then all these beta FWs can be decrypted faster and more keys can be posted. I myself would definitely be interested in getting the KBAG etc. and if anybody could create such a page then I would definitely be interested in posting keys myself. Once created the page shouldn't need too much housekeeping either since the process won't change until IMG4 comes along which I will dread :P Who's up to it?? [[User:Windows Helpdesk|blackthund3r]] 11:43, 20 October 2010 (UTC)
   
  +
==New table format.==
And how would someone like myself go about getting the Key/IV for an update/restore ramdisk --[[User:Shengis14|Shengis14]] 22:13, 8 October 2010 (UTC)
 
  +
I was thinking, because the tables do not fit into the normal view (7.x beta's for example), maybe we could think of a new design. I had an idea of maybe using device tables, so we could have something like the below (of course we would have a beta and public sections and all devices would be added);
   
  +
iPhone (As a heading, since actually adding this would break the topic, making it two.)
:You would need at least an iBoot exploit and a payload to upload that is able to access the AES engine of the device. --[[User:OMEGA RAZER|OMEGA RAZER]] 22:16, 8 October 2010 (UTC)
 
  +
{| class="wikitable"
  +
|-
  +
! rowspan="2" | Date
  +
! rowspan="2" | Build
  +
! colspan="3" | [[iPhone 4]]
  +
! rowspan="2" | [[N94AP|iPhone 4S]]
  +
! colspan="2" | [[iPhone 5]]
  +
|-
  +
! [[N90AP|iPhone3,1]]
  +
! [[N90BAP|iPhone3,2]]
  +
! [[N92AP|iPhone3,3]]
  +
! [[N41AP|iPhone5,1]]
  +
! [[N42AP|iPhone5,2]]
  +
|-
  +
| 10 Jun 2013
  +
! style="text-align:left;" | 11A4372q
  +
| [[InnsbruckVailPrime 11A4372q (iPhone3,1)|7.0b]]
  +
| [[InnsbruckVailPrime 11A4372q (iPhone3,2)|7.0b]]
  +
| [[InnsbruckVailPrime 11A4372q (iPhone3,3)|7.0b]]
  +
| [[InnsbruckVailPrime 11A4372q (iPhone4,1)|7.0b]]
  +
| [[InnsbruckVailPrime 11A4372q (iPhone5,1)|7.0b]]
  +
| [[InnsbruckVailPrime 11A4372q (iPhone5,2)|7.0b]]
  +
|-
  +
| 24 Jun 2013
  +
! style="text-align:left;" | 11A4400f
  +
| [[InnsbruckVailPrime 11A4400f (iPhone3,1)|7.0b2]]
  +
| [[InnsbruckVailPrime 11A4400f (iPhone3,2)|7.0b2]]
  +
| [[InnsbruckVailPrime 11A4400f (iPhone3,3)|7.0b2]]
  +
| [[InnsbruckVailPrime 11A4400f (iPhone4,1)|7.0b2]]
  +
| [[InnsbruckVailPrime 11A4400f (iPhone5,1)|7.0b2]]
  +
| [[InnsbruckVailPrime 11A4400f (iPhone5,2)|7.0b2]]
  +
|-
  +
| 8 Jul 2013
  +
! style="text-align:left;" | 11A4414e
  +
| [[InnsbruckVailPrime 11A4414e (iPhone3,1)|7.0b3]]
  +
| [[InnsbruckVailPrime 11A4414e (iPhone3,2)|7.0b3]]
  +
| [[InnsbruckVailPrime 11A4414e (iPhone3,3)|7.0b3]]
  +
| [[InnsbruckVailPrime 11A4414e (iPhone3,1)|7.0b3]]
  +
| [[InnsbruckVailPrime 11A4414e (iPhone5,1)|7.0b3]]
  +
| [[InnsbruckVailPrime 11A4414e (iPhone5,2)|7.0b3]]
  +
|-
  +
| 29 Jul 2013
  +
! style="text-align:left;" | 11A4435d
  +
| [[InnsbruckVailPrime 11A4435d (iPhone3,1)|7.0b4]]
  +
| [[InnsbruckVailPrime 11A4435d (iPhone3,2)|7.0b4]]
  +
| [[InnsbruckVailPrime 11A4435d (iPhone3,3)|7.0b4]]
  +
| [[InnsbruckVailPrime 11A4435d (iPhone4,1)|7.0b4]]
  +
| [[InnsbruckVailPrime 11A4435d (iPhone5,1)|7.0b4]]
  +
| [[InnsbruckVailPrime 11A4435d (iPhone5,2)|7.0b4]]
  +
|}
  +
We would also break this down into .x still, so 6.x Apple TV, iPad, iPad mini, iPhone, iPod touch then 7.x and repeat. This would also work well with the new format of listing "iPhone 5 GSM" and "iPhone5,1". Let me know your thoughts. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 7 March 2014 (UTC)
  +
:+1. Could still overflow (that example already occupies over half of a 1024px wide window), but of course still better than the current format. [[User:Thekirbylover|kirb]] ([[User talk:Thekirbylover|talk]]) 02:37, 8 March 2014 (UTC)
  +
::I have taken a screenshot of what it will look like with the current suggestions [http://imgur.com/9UNiwuH here]. This will be completed on the 15th March if nobody objects.--[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 01:12, 9 March 2014 (UTC)
  +
:::This has been completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:11, 15 March 2014 (UTC)
   
  +
== [[Internal Firmware]] Keys ==
It's just one of the reasons I'm confused is how is there a sudden jump in the number of vfdecrypt keys for the iPod touch 3G on like 4.0-1??
 
There isnt a exploit that is iBoot or lower for that device
 
Any thoughts ? --[[User:Shengis14|Shengis14]] 22:50, 8 October 2010 (UTC)
 
   
  +
Should there be a keys page just for SwitchBoard firmwares that also have NOR dumps/are restore bundles, so that people can decrypt these firmwares (if they have them and don't have a device with the same SoC) and explore files themselves? --[[User:Ilikeiphone123|Ilikeiphone123]] ([[User talk:Ilikeiphone123|talk]]) 16:12, 13 March 2021 (UTC)
== New page? ==
 
I think we should make a new page detailing how to utilise [[User:Gojohnnyboi|Gojohnnyboi]]'s AES payload to get the keys including screenies on opening up an img3 in a hex editor and getting the [[KBAG]] etc. Then the keys won't be left to the main devs and [[User:iH8sn0w|iH8sn0w]] to post. Then all these beta FWs can be decrypted faster and more keys can be posted. I myself would definitely be interested in getting the KBAG etc. and if anybody could create such a page then I would definitely be interested in posting keys myself. Once created the page shouldn't need too much housekeeping either since the process won't change until IMG4 comes along which I will dread :P Who's up to it?? [[User:Windows Helpdesk|blackthund3r]] 11:43, 20 October 2010 (UTC)
 

Latest revision as of 16:13, 13 March 2021

Archives
 • 2009 • 2010 • 2011 • 2012 • 2013 •

iKeys

I was wondering if anyone had any info on "iKeys". It's mentioned here at the bottom. I'd imagine it's like GenPass but just wondering. Any info is appreciated. --OMEGA_RAZER

Exploit?

Am I to understand that a low level exploit is needed to get the VFDecrypt key? --Shengis14 18:50, 8 October 2010 (UTC)

No, that's not completely true. :P One has to manage to get the key/IV for a ramdisk, and then use GenPass to get the VFDecrypt key. --dra1nerdrake 21:27, 8 October 2010 (UTC)
How would someone like myself go about geting the key/IV for a ramdisk? --Shengis14 22:13, 8 October 2010 (UTC)
You would need (at the very least) an iBoot exploit and a payload to upload that is able to access the AES engine of the device. --OMEGA RAZER 22:16, 8 October 2010 (UTC)
It's just that one of the reasons I'm confused is why there is a sudden jump in the number of keys for the iPod touch 3G on 4.0-4.1?
There isn't an exploit that is iBoot level or lower for that device. --Shengis14 22:50, 8 October 2010 (UTC)

New page?

I think we should make a new page detailing how to utilise Gojohnnyboi's AES payload to get the keys including screenies on opening up an img3 in a hex editor and getting the KBAG etc. Then the keys won't be left to the main devs and iH8sn0w to post. Then all these beta FWs can be decrypted faster and more keys can be posted. I myself would definitely be interested in getting the KBAG etc. and if anybody could create such a page then I would definitely be interested in posting keys myself. Once created the page shouldn't need too much housekeeping either since the process won't change until IMG4 comes along which I will dread :P Who's up to it?? blackthund3r 11:43, 20 October 2010 (UTC)

New table format.

I was thinking, because the tables do not fit into the normal view (7.x beta's for example), maybe we could think of a new design. I had an idea of maybe using device tables, so we could have something like the below (of course we would have a beta and public sections and all devices would be added);

iPhone (As a heading, since actually adding this would break the topic, making it two.)

Date Build iPhone 4 iPhone 4S iPhone 5
iPhone3,1 iPhone3,2 iPhone3,3 iPhone5,1 iPhone5,2
10 Jun 2013 11A4372q 7.0b 7.0b 7.0b 7.0b 7.0b 7.0b
24 Jun 2013 11A4400f 7.0b2 7.0b2 7.0b2 7.0b2 7.0b2 7.0b2
8 Jul 2013 11A4414e 7.0b3 7.0b3 7.0b3 7.0b3 7.0b3 7.0b3
29 Jul 2013 11A4435d 7.0b4 7.0b4 7.0b4 7.0b4 7.0b4 7.0b4

We would also break this down into .x still, so 6.x Apple TV, iPad, iPad mini, iPhone, iPod touch then 7.x and repeat. This would also work well with the new format of listing "iPhone 5 GSM" and "iPhone5,1". Let me know your thoughts. --iAdam1n (talk) 23:10, 7 March 2014 (UTC)

+1. Could still overflow (that example already occupies over half of a 1024px wide window), but of course still better than the current format. kirb (talk) 02:37, 8 March 2014 (UTC)
I have taken a screenshot of what it will look like with the current suggestions here. This will be completed on the 15th March if nobody objects.--iAdam1n (talk) 01:12, 9 March 2014 (UTC)
This has been completed. --iAdam1n (talk) 10:11, 15 March 2014 (UTC)

Internal Firmware Keys

Should there be a keys page just for SwitchBoard firmwares that also have NOR dumps/are restore bundles, so that people can decrypt these firmwares (if they have them and don't have a device with the same SoC) and explore files themselves? --Ilikeiphone123 (talk) 16:12, 13 March 2021 (UTC)