search

sethkontny / iphone-dataprotection

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

ssh.tar.gz bricks the device #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Get the ssh.tar.gz from the downloads section
2. Feed it into device using redsn0w's "install custom bundle"
3. Get the bricked device that won't turn on
(4.) Retried the steps on another device, and on 1st device with freshly 
restored firmware just to be sure, outcome was the same.

I don't rule out the possibility of me being an idiot, because the file 
ssh.tar.gz could be meant for something else. But there's no description in the 
downloads section, as well as no mention of it in the readme's.

So the question is:
1. What's wrong with the ssh.tar.gz file from the downloads? Is it not suitable 
for iOS 5 (versions 5.0.1 and 5.1.1 were used)? Or did I miss some steps before 
feeding it into the device?
2. And, is there a removal script to clean it out of the the device now, using 
the redsnow's "install custom bundle", or do I need to use the custom bootrom 
and do it manually?

Thanks (and sorry if I'm idiot),
Marat

Original issue reported on code.google.com by r...@pisem.net on 5 Oct 2012 at 10:54

GoogleCodeExporter commented 9 years ago 
ssh.tar.gz is not meant to be used as a custom bundle in redsn0w, it is used by 
the scripts on this repository to create an SSH ramdisk. I'll add a description 
in the downloads section.

To clean the device you can follow the README to create an ssh ramdisk and boot 
it (or you can just use 
http://msftguy.blogspot.fr/2012/01/automatic-ssh-ramdisk-creation-and.html). 
Once you are connected to the ssh ramdisk, you'll have to mount the data 
partition and look at the crashlogs (in /mnt2/logs/Crashreporter) to figure out 
what is crashing at boot, and remove the files that were added by redsn0w.

Original comment by jean.sig...@gmail.com on 5 Oct 2012 at 11:50

GoogleCodeExporter commented 9 years ago 
Thank you for your suggestion and especially the link (I haven't got a Mac 
anywhere near).
That's funny. Mounted the data partition - but Crashreporter dir is empty (I 
emptied it just a couple of days ago while the device was still working).
During the boot, the device does not fall into recovery or anything, just shows 
the apple logo forever and reboots every 10 minutes or so.
Perhaps I could make it boot in verbose?

Original comment by r...@pisem.net on 5 Oct 2012 at 12:43

GoogleCodeExporter commented 9 years ago 
Try looking at /mnt1/etc and see if the fstab file is still there. I think 
redsn0w might use an option when extracting the bundle tar file that erases the 
existing files in the folders that are extracted from the archive.

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

GoogleCodeExporter commented 9 years ago 
Hello again,
Just letting you know I've failed to revive the device and restored it since.
I see, however, that you forgot your promise to add a description to ssh.tar.gz 
file in the downloads section - so that nobody else repeat my mistake.

Original comment by r...@pisem.net on 20 Oct 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
Ok, i added the warning in the summary as well.

Original comment by jean.sig...@gmail.com on 21 Oct 2012 at 12:22