Booting 4.3.2 SSH ramdisk damaged phone on 4.3.5 - how?
I had an iPhone 4 working fine on 4.3.5 tethered JB using redsn0w.
I wanted to test something involving ssh ramdisks, so booted an 4.3.2 ibss/kernelcache/dmg.ssh on the phone using tetheredboot thinking it would be compatible.
This seemed to work fine, the empty progress bar screen came up and the device connected in itunnel. However, the instant I connected to the forwarded ssh port from my mac, the phone rebooted.
It then went into recovery mode no matter what I did. If I tried to boot 4.3.5 tethered again with redsn0w it would show the pwnapple briefly but end up on the 'connect to itunes' logo. I tried running fixrecovery43 and recovery fix in the new redsn0w_mac_0.9.9b1 to no avail.
I then built a proper 4.3.5 SSH ramdisk (using msftguy's recovery ramdisk builder v3, pwnagetool 4.3.3 with added 4.3.5 bundle). This works fine - I am able to ssh in without problems, but in /dev there is only /dev/disk0 and /dev/rdisk0, no partitions are visible.
Trying to dd from /dev/disk0 I just get 'invalid argument' so I can't even access the disk device. What has been scewed up here, and how can I fix it?
Even though I only booted the 4.3.2 SSH ramdisk and did not actually run a restore, something has been screwed up so that a 4.3.5 ramdisk or the normal OS itself booting tethered now seems unable to mount my partitions.
I have a few months of un-backed-up precious photos and other data on this phone so i really don't want to do a full restore and would be grateful for any tips :(