Quote:
Originally Posted by Cinisajoy
Your jailbreak should have held.
Reinstall MRPI and all the hacks you had on it.
|
Looks like it was this.
Quote:
Originally Posted by knc1
Why not try the "test" package attached to the <5.8.8 post?
|
I didn't have a /mrpackages directory, so I figured I'd ask first. I started by making /mrpackages and attempting the
;log mrpi command, but it failed. On Cinisajoy's suggestion I proceeded with installing KUAL and MRPI as if I were jailbroken (I had forgotten KUAL was an app and not an added extension of the OS). The test worked through KUAL.
Seeing how
;log mrpi failed, but KUAL worked, it looks like I'm missing the survival code. The log file shows I've got 3 keys installed, but I'm not seeing anything to help identify which jailbreak I'm running (which I'm guessing would be in the JB file that looks to have been removed at some point).
Quote:
Originally Posted by knc1
It is not unusual for older devices to fail to update OTA - Don't complain, its a feature not a bug.
|
In case this wasn't sarcasm, I wasn't complaining. I was interested about the mechanics. I wasn't certain if I may have had a different OTA block method installed, or if I was just lucky. I created the update.bin.tmp.partial directory regardless as a failsafe.
====
So from here, it looks like I've got an unknown version of a jailbreak. To get to a known state and ensure the survival code is installed, should I run through the full downgrade process (as knc1 suggested) or would the bridge update process be enough?
Edit: In case it matters, I plan on updating to 5.8.8 once I get everything in order.