View Single Post
Old 11-04-2011, 05:50 PM   #5
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,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@CaelThunderwing: For this specific purpose (AFAIK), a KSO is strictly identical to a classic Kindle, so it shouldn't be any different. And, unless you have the wireless on, and a pending official update (even then, I'm not so sure about that), the update option shouldn't disappear. And a failed jailbreak install certainly wouldn't jailbreak a Kindle (on FW 3.x), especially not a U004 error [which would more likely indicate that you're trying to run a jailbreak install not targeted at your specific Kindle version [>= 3.2.1], which your first message here confirms).

Since you've been able to install custom hacks since, my best guess would be that, on top of using the wrong .bin file, [and not uninstalling your previous jailbreak if your intent was to update it], your Kindle was already jailbroken anyway.

Last edited by NiLuJe; 11-04-2011 at 05:58 PM.
NiLuJe is offline   Reply With Quote