mamabun / iphone-dataprotection

Automatically exported from code.google.com/p/iphone-dataprotection
0 stars 0 forks source link

RAM Disk crashes and freezes with iPhone 3G using 4.2.1 #124

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Building the RAM Disk as directed in READ ME (All versions are same as README)
2.M2Crypto install fails because SWIG is not installed
3.SWIG installed with homebrew
4.Load the built RAM Disk onto iPhone 3G

What is the expected output? 
OK ASCII text on iPhone 3G

What do you see instead?
RAM Disk is loaded onto iPhone 3G, Pineapple logo shown, then Boot messages 
display then screen goes black (NO white flash) iPhone 3G reboots displaying 
the Apple logo.

What version of the product are you using? 
Latest
On what operating system?
Lion 10.7.3 (Fresh Install)
OS X version :10.7.3
XCode version :4.3 (iOS SDK 5.0)
Tools revision : 9253cb99a012+ tip

Please provide any additional information below.

Device: iPhone 3G running iOS 4.1
IPSW: iPhone1,2_4.2.1_8C148_Restore.ipsw

Terminal pasted to http://pastebin.com/rC4RXKmK

If I change the following in build_ramdisk.sh
tar -C /Volumes/ramdisk/ -xzkP <  ssh.tar.gz
to
tar -C /Volumes/ramdisk/ -xzP <  ssh.tar.gz
i also commented out this, as I just want to brute force the passcode on the 
device
#cp ramdisk_tools/ioflashstoragekit /Volumes/ramdisk/var/root

and then the RAM Disk is built without any 
"Already exists"
and
"tar: Error exit delayed from previous errors" errors
but the device freezes with Boot message
"[FTL:MSG] FTL_Open    [OK]"
and after around 10 mins more boot messages appear then the screen flashes 
white and reboots to Apple Logo.

Have I completely missed or am doing something wrong. If anybody can help I 
would be extremely grateful.
Thank you kindly

Original issue reported on code.google.com by mwtt...@gmail.com on 11 Jan 2014 at 1:53

GoogleCodeExporter commented 8 years ago
do you have the same problem if you use the original tar command (-xzkP) ? the 
"already exists" messages are normal (not an error) and are actually required 
to build a proper ramdisk for armv6 devices like iphone 3g.

Original comment by jean.sig...@gmail.com on 11 Jan 2014 at 1:49

GoogleCodeExporter commented 8 years ago
Thanks so much for replying.

This is what happens without changing the build_ramdisk.sh and everything is 
built following the README.
RAM Disk is loaded onto iPhone 3G, Pineapple logo shown, Boot messages are 
displayed then screen goes black and never displays OK in ASCII, iPhone 3G 
reboots displaying the Apple logo.

I tried multiple times and have reinstalled Lion from scratch but I get the 
same results.

If it helps I can share a link to a video and the still of final frame of boot 
messages before it crashes and reboots.

Original comment by mwtt...@gmail.com on 11 Jan 2014 at 2:40

GoogleCodeExporter commented 8 years ago
ok, i will test on an iphone 3g next week.
not sure it will help but try with the original tar command but with this line 
commented:
cp ramdisk_tools/ioflashstoragekit /Volumes/ramdisk/var/root

Original comment by jean.sig...@gmail.com on 11 Jan 2014 at 3:34

GoogleCodeExporter commented 8 years ago
on second thought just ignore the above comment, it won't help

Original comment by jean.sig...@gmail.com on 11 Jan 2014 at 3:35

GoogleCodeExporter commented 8 years ago
OK thanks, in the meantime here's the video and still of the last frame before 
crash.

https://plus.google.com/photos/118026201480520038081/albums/5967672312919499889

http://www.youtube.com/watch?v=nCjHBKg7UoQ

I do have a spare iPhone 3G, so I'll try it on that, just to make sure it's not 
a hardware issue.

Original comment by mwtt...@gmail.com on 11 Jan 2014 at 4:24

GoogleCodeExporter commented 8 years ago
ok my bad, change this line in ramdisk_tools/Makefile
ARCH?=armv7
to
ARCH?=armv6
then run make clean and rebuild the ramdisk, should work a lot better ;)

Original comment by jean.sig...@gmail.com on 11 Jan 2014 at 4:52

GoogleCodeExporter commented 8 years ago
That worked a treat! Passcode brute forced in 8 mins.

Thanks a lot, keep up the good work.

Much appreciated.

Original comment by mwtt...@gmail.com on 11 Jan 2014 at 7:41