Closed GoogleCodeExporter closed 8 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
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
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
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
Ok, i added the warning in the summary as well.
Original comment by jean.sig...@gmail.com
on 21 Oct 2012 at 12:22
Original issue reported on code.google.com by
r...@pisem.net
on 5 Oct 2012 at 10:54