|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Talk:Baker 8B117 (iPhone2,1)"
Tavianator (talk | contribs) |
m (IAdam1n moved page Talk:Baker 8B117 (iPhone 3GS) to Talk:Baker 8B117 (iPhone2,1): New format.) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== FS key is wrong == |
== FS key is wrong == |
||
| + | genpass gives the key in the article when run with the update ramdisk, and <tt>59ebcd47de964e5479ce2e2dc583284c863b85fefc0a58d68871a941a76c125367bffd2e</tt> when run with the restore ramdisk. Neither one produces a valid image when using vfdecrypt to decrypt the filesystem DMG. I haven't figured out how to get the correct one; there's talk that genpass fails on ramdisk images that use compression, could that be it? I'm doing all of this on x86-64 Linux. --[[User:Tavianator|Tavianator]] 05:38, 6 January 2011 (UTC) |
||
| − | |||
| + | :Did you decrypt the ramdisk first? The hash is calculated by hashing a decrypted ramdisk dmg. The key on here is valid. --[[User:Ih8sn0w|iH8sn0w]] 17:58, 6 January 2011 (UTC) |
||
| − | genpass gives the key in the article when run with the update ramdisk, and "59ebcd47de964e5479ce2e2dc583284c863b85fefc0a58d68871a941a76c125367bffd2e" when run with the restore ramdisk. Neither one produces a valid image when using vfdecrypt to decrypt the filesystem DMG. I haven't figured out how to get the correct one; there's talk that genpass fails on ramdisk images that use compression, could that be it? I'm doing all of this on x86-64 Linux. --[[User:Tavianator|Tavianator]] 05:38, 6 January 2011 (UTC) |
||
| + | ::Oops, figured it out. Linux doesn't handle compressed DMG images, and the FS image is compressed. dmg2img can be used to decompress it. Sorry for the noise! [[User:Tavianator|Tavianator]] 22:25, 6 January 2011 (UTC) |
||
| − | |||
| − | Did you decrypt the ramdisk first? The hash is calculated by hashing a decrypted ramdisk dmg. The key on here is valid. |
||
| − | --[[User:Ih8sn0w|iH8sn0w]] 17:58, 6 January 2011 (UTC) |
||
| − | |||
| − | Oops, figured it out. Linux doesn't handle compressed DMG images, and the FS image is compressed. dmg2img can be used to decompress it. Sorry for the noise! [[User:Tavianator|Tavianator]] 22:25, 6 January 2011 (UTC) |
||
Latest revision as of 08:39, 6 February 2014
FS key is wrong
genpass gives the key in the article when run with the update ramdisk, and 59ebcd47de964e5479ce2e2dc583284c863b85fefc0a58d68871a941a76c125367bffd2e when run with the restore ramdisk. Neither one produces a valid image when using vfdecrypt to decrypt the filesystem DMG. I haven't figured out how to get the correct one; there's talk that genpass fails on ramdisk images that use compression, could that be it? I'm doing all of this on x86-64 Linux. --Tavianator 05:38, 6 January 2011 (UTC)
- Did you decrypt the ramdisk first? The hash is calculated by hashing a decrypted ramdisk dmg. The key on here is valid. --iH8sn0w 17:58, 6 January 2011 (UTC)
- Oops, figured it out. Linux doesn't handle compressed DMG images, and the FS image is compressed. dmg2img can be used to decompress it. Sorry for the noise! Tavianator 22:25, 6 January 2011 (UTC)
