MobileRead Forums - View Single Post

NiLuJe · 01-08-2012, 11:03 PM

@geekmaster: Yep, there's yifanlu's jailbreak, and mine. When I started that thread (a while ago now, sometime after the 2.5 update, if memory serves me correctly), everything was based on/forked from something already existent, so I went with the '.N' version suffix to try to differentiate my fork from the originals. It was mostly cosmetic at the time, but became useful again with yifanlu's jailbreak, which uses a classic x.y.[z] versionning scheme

.

From what I understood (mostly from post #19), the OP tried to install my jb, but didn't use the -3.2.1 build, so that failed, and he then switched to yifanlu's jb.

As to why everything's borked, well, you got me ^^. My best guess would be something wonky with the whole userstore chain of mounts (because it vaguely reminded me of some of the weirdness I encountered when dealing with volumd/the userstore during some usbnetwork tests), which is why I've been rambling about it, but it very well could be something else... Logs would probably help (but with a broken userstore, that seems impossible :/). I'm not sure if getting into the diagnostics mode would be of use, as I'm not familiar with it, and I don't even know if it's doable with a broken userstore and no means of executing code on the device... :/.

01-08-2012, 11:03 PM	#34
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@geekmaster: Yep, there's yifanlu's jailbreak, and mine. When I started that thread (a while ago now, sometime after the 2.5 update, if memory serves me correctly), everything was based on/forked from something already existent, so I went with the '.N' version suffix to try to differentiate my fork from the originals. It was mostly cosmetic at the time, but became useful again with yifanlu's jailbreak, which uses a classic x.y.[z] versionning scheme . From what I understood (mostly from post #19), the OP tried to install my jb, but didn't use the -3.2.1 build, so that failed, and he then switched to yifanlu's jb. As to why everything's borked, well, you got me ^^. My best guess would be something wonky with the whole userstore chain of mounts (because it vaguely reminded me of some of the weirdness I encountered when dealing with volumd/the userstore during some usbnetwork tests), which is why I've been rambling about it, but it very well could be something else... Logs would probably help (but with a broken userstore, that seems impossible :/). I'm not sure if getting into the diagnostics mode would be of use, as I'm not familiar with it, and I don't even know if it's doable with a broken userstore and no means of executing code on the device... :/. Last edited by NiLuJe; 01-08-2012 at 11:11 PM.