View Single Post
Old 10-31-2023, 08:12 PM   #200
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
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
First: ;un doesn't have *anything* to do with the base JB/bridge, so it won't really help you suss out anything meaningful. It breaking after a FW update is *completely* normal (assuming you actually had it working in the first place by having installed USBNetwork).

----

If you can't run ;log mrpi nor ;log runme, you are indeed SOL.

I mean, you could try an emergency.sh, but that's usually contingent on the same stuff that ensures ;log works, so, if one's gone, it would follow that the other would be too.

c.f., https://www.mobileread.com/forums/sh...63#post3961863

(Also, modifications to that last approach should only be attempted by a trained professional, as a screwup in a bridge emergency script *will* soft brick your device. People *have* killed their device this way in the past.)

(This is bundled in the "K5 JailBreak" package in my snapshots).

Last edited by NiLuJe; 10-31-2023 at 08:18 PM.
NiLuJe is offline   Reply With Quote