Closed GoogleCodeExporter closed 9 years ago
try updating to the latest revision (hg pull -u, then rebuild the ramdisk),
there is one commit ahead of your version that could resolve the issue.
if the panic still occurs, remove this line in build_ramdisk.sh
cp ramdisk_tools/ioflashstoragekit /Volumes/ramdisk/var/root
then rebuild the ramdisk and see if it still crashes (if it doesnt crash then
ios_examiner wont work, but ssh should work).
thanks.
Original comment by jean.sig...@gmail.com
on 27 May 2013 at 4:05
Jean,
Thank you for your quick response. The newest source did not seem to solve my
problem, but removing ioflashstoragekit did. My goal is to get an image of the
NAND storage, so I believe my goal can still be reached without that.
If there's anything else you'd like me to try now or in the future just let me
know. I can test any updates on this device and let you know the results.
One thing that I thought was a little strange - I expected there to be an
encrypted backup password (set through iTunes) in the iPhone keychain, but it
was not revealed by keychain_tool.py. Maybe my assumption that it was set was
incorrect.
Original comment by murdo...@gmail.com
on 27 May 2013 at 5:10
you need ioflashstoragekit to dump the NAND.
can you try the attached patch to see if the crash still occurs ? you'll have
to undo the previous modification in build_ramdisk.sh and then rebuild the
ramdisk.
for the backup password maybe it was once set but then removed ?
thanks.
Original comment by jean.sig...@gmail.com
on 28 May 2013 at 5:14
Attachments:
That did seem to work. I uncommented:
cp ramdisk_tools/ioflashstoragekit /Volumes/ramdisk/var/root
I applied the patch ("patch -p1 < ipt4_nand_debug.patch" from the
iphone-dataprotection directory).
I then ran a "make clean" in the ramdisk_tools directory and went back through
the sequence with the kernel_patcher.py and "sh ./make_ramdisk_n81ap.sh"
The iPod 16GB now boots and does not crash after the OK ASCII display.
Original comment by murdo...@gmail.com
on 30 May 2013 at 1:51
closing old issues
Original comment by jean.sig...@gmail.com
on 11 Feb 2014 at 10:38
Original issue reported on code.google.com by
murdo...@gmail.com
on 27 May 2013 at 6:02