Quote:
Originally Posted by NiLuJe
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). |
I see. Thanks for telling me. I already tried emergency.sh but not working. So I guess the best way is to disable the WIFI and for the next jailbreak.
Is there actually a way to prevent any system update from Amazon(except using airplane mode)? I still get updated even when I use the renameota and do the update.bin.tmp.partial trick. These methods are not perfect. I don't know if removing the task that automatically updates the system during non-active hours is possible.
Maybe I could help on this in future after I get jb again