Can't mount data partition

[GoogleCodeExporter]

First of all, the tools I'm using work flawlessly because I used them on a 
working iPhone and I didn't get any error.

I want to recovery some files from my iPhone 4 GSM ( iOS 5.1.1 ). The problem 
is it can't mount the data partition.

What I noticed: 

1) when running device_infos, dataVolumeOffset = 0 and dataVolumeUUID = 
0000000000000000 .
2) when runnning ./mount_partitions.sh, it asks me to try it manually. Then I 
checked for /dev/disk0s1s1 and /dev/disk0s1s2 and it appears they don't exist.

Am I really that screwed up ?

Original issue reported on code.google.com by Dja...@gmail.com on 23 Sep 2012 at 4:46

[GoogleCodeExporter]

does the device still boots normally or is it "bricked" ? 
is /dev/disk0 present ?
you can try ios_examiner.py (you need a recent build of the tools), it will try 
to access the raw nand directly, it will probably fail but it could help to 
figure out why the partitions do not appear.

Original comment by jean.sig...@gmail.com on 23 Sep 2012 at 5:42

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It boots normally and gets stuck in recovery mode (I can't get any output from 
irecovery). 

When booting the ramdisk without boot-args:

1) I get on the screen the error " GetMasterBlock; Error 16 opening /dev/md0"
2) /dev/disk0 is present

when booting with the bootargs ("-v rd=md0 nand-disable=1"):

1) I get on the screen the error " GetMasterBlock; Error 16 opening /dev/md0"
2) /dev/disk0 is not present
3) After running ios_examiner.py I get this in Terminal: 
http://pastie.org/private/ogxn7st4wpcur6wydvs1q
and "FAIL: could not get AppleEffaceableStorage service
"IOConnectCallMethod on  AppleEffaceableStorage selector 1 returned 10000003 " 
on screen

Original comment by Dja...@gmail.com on 23 Sep 2012 at 6:26

[GoogleCodeExporter]

ok, it looks like the partition table is missing, try dumping /dev/disk0 (the 
nand-disable boot arg prevents it from appearing, this is normal). Try looking 
with an hex editor at the beginning of /dev/disk0 to see if its all 00s or not, 
and also at about 1Gb offset if the data partition is still there (both system 
and data are encrypted). If disk0 is not all 00s, and assuming only the 
partition table was messed up, it should be possible to recover the data 
partition from the dump (you'll need the plist with the encryption keys from 
./device_infos)

Original comment by jean.sig...@gmail.com on 23 Sep 2012 at 6:58

[GoogleCodeExporter]

hum however this line
"YaFTL context OK, version=CX01 maxIndexUsn=1 context usn=1"
doesnt looks too good, the context should be a high number.
what exactly happened before the device got stuck in recovery ?

Original comment by jean.sig...@gmail.com on 23 Sep 2012 at 7:01

[GoogleCodeExporter]

Dumping disk0 failed ( invalid argument error) so I'm dumping rdisk0, I will 
keep you updated.

Also I was testing a framework Im writing by beginning a restore through iTunes 
and by stopping it as soon as the ramdisk has booted (before NAND is even 
touched )

Original comment by Dja...@gmail.com on 23 Sep 2012 at 9:51

[GoogleCodeExporter]

Any updates ? i suspect the ramdisk was booted with the nand-enable-reformat 
boot arg and somehow restored formated the nand, even without receiving any 
command from itunes.

Original comment by jean.sig...@gmail.com on 6 Oct 2012 at 1:15

[GoogleCodeExporter]

So the dump contained only 00's, so I ended up restoring it.  Still thank you 
for these awesome tools ! Do you have an email where I can contact you about a 
feature implementation ? 

Original comment by Dja...@gmail.com on 6 Oct 2012 at 7:46

[GoogleCodeExporter]

name.lastname@gmail.com

Original comment by jean.sig...@gmail.com on 7 Oct 2012 at 10:12

[GoogleCodeExporter]

Original comment by jean.sig...@gmail.com on 26 Jan 2013 at 10:58

• Changed state: Done