What steps will reproduce the problem?
1.Running Ios examiner
2.nand_dump iphone4_nand.bin
3.
What is the expected output? What do you see instead? Plist folders is there
with extracted keys, and a nand.bin folder for the dump. But tools just seem to
freeze after the dump command. Nothing happens, and nand.bin folder remains
empty.
C:\Users\*****>Iphone\iphone-dataprotection-a\python_scripts\ios_examiner.py
Connecting to device : 7522308ac74fbe6d06941eaa57e350a774f59d1c
Device model: iPhone 4 GSM
UDID: 7522308ac74fbe6d06941eaa57e350a774f59d1c
ECID: 1002490645932
Serial number: 7U1202C9A4S
key835:**********************************
key89B: **********************************
Chip id 0x32944845 banks per CE physical 1
NAND geometry : 16GB (4 CEs (1 physical banks/CE) of 4096 blocks of 128 pages of
8192 bytes data, 12 bytes metdata)
NANDDRIVERSIGN not found, assuming metadata withening = 1
Effaceable generation 64
Effaceable CRC OK
Found effaceable lockers in ce 3 block 0 (XXX possibly remapped) page 16
Lockers : BAG1, DONE, Dkey, LwVM
DEVICEUNIQUEINFO not found
Using VSVFL
VSVFL context open OK
YaFTL context OK, version=CX01 maxIndexUsn=2989729 context usn=2989729
LwVM header CRC OK
cprotect version : 4
iOS version: 7.1.2
Keybag state: locked
(HomeÔÇÖs iPhone-data) / bruteforce
Passcode comlexity (from OpaqueStuff) : 4 digits
Enter passcode or leave blank for bruteforce:
Passcode "" OK
Keybag state: unlocked
Save device information plist to [7522308ac7.plist]: iphone4.plist
File already exists, overwrite ? [y/n]: y
(HomeÔÇÖs iPhone-data) / nand_dump iphone4_nand.bin
Here everything just seems to hang (I've waited up to 45 minutes for something
to happen.) And when I click out of the cmd prompt I get a "dump aborted"
message on my phone.
I am running a prebuilt ramdisk for ios 7.1.2 on a windows 7 64 bit machine.
Phone is Iphone 4, 7.1.2 with no passcode set. Ramdisk loads as expected. Can
copy files individual files through WINSCP, run demo_bruteforce and plist and
keychaindb download. Did get an ios_examiner error initially and added the
"utf-8" as per instruction and I was able to type into shell. Anyway complete
newbie here so maybe the answer is obvious:) But any guidance is much
appreciated.
Original issue reported on code.google.com by mathiasg...@gmail.com on 23 May 2015 at 5:17
Original issue reported on code.google.com by
mathiasg...@gmail.comon 23 May 2015 at 5:17