|
NiLuJe and knc1,
My Voyage has the squaretrade warranty (and the 5.5.12 update also screwed up page-turns), so I gave it a shot to see what they'd send. Unfortunately the replacement has 5.10.3...just barely not jailbreakable.
Before sending back my original device, I had a few thoughts. While ;log doesn't work, some of the hotfix updates (installed via UYK) aren't rejected entirely. What I mean is that some of them are detected as invalid as soon as they're transferred to the Kindle, but others at least get the device to restart and try to install before triggering Error 007.
Just wondering if there was some way to sneak in KUAL in that process. Or if there are specific builds you recommend that I try before sending back the Voyage that had jailbreak and lost it at 5.12.2.
As far as the reason that I had the 1.14_nomax, there was a point where the most recent hotfix didn't work, but that one did. So I just kept going with it, and all was good as long as I manually updated and stayed on wifi with the folder to prevent auto-updates. So obviously I'm a little bummed with the 5.12.2 update being so stealthy.
Anyway, this is all dumb because the only part of Jailbreak I really used actively was the screensavers hack, which Amazon could just provide if people paid the $20 to remove special offers...so it would be a win win. But they won't so now I'm torn between trying to keep a shred of hope with my old device before sending it back, just using the warranty replacement knowing that at least books will work, or trying the open-and-solder method despite not being very good at soldering.
Sorry for the long post, but really appreciate all your dedication to the Kindle hacking community, and even if there's no hope for me short of surgery on the new Voyage, at least venting here might help me skip a step or two on the stages of grief over the lost jailbreak.
|