View Single Post
Old 07-24-2010, 03:21 AM   #294
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: 5,278
Karma: 5220867
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2; Kobo H2O
Unfortunately, either there's no debug logging in the Journal stuff, or the logging level is reset by the updater, so, nothing new in the latest logs. It's even more cryptic without the books in fact... :/

If someone knows what these Journal*.jar are supposed to do, I'm all ears.

Basically, the update patches the two files (version tags) fine, then launch the Journal-update, which fails, which then makes the update revert the two patches and fail. :/

Not even sure if we could learn anything with a log of a successful update, but it's worth a shot. (Unfortunately, I don't have a K2 US :/. And don't have logs of my 2.5.3 update).

And, no, not sure how to avoid the autoupdate. (Well, leaving Whispernet off ). Or using some of the nasty tricks laying around in some older posts to avoid the todo requests or stuff like that. Or maybe patching version/prettyversion to fake a 2.5.6...

Last edited by NiLuJe; 07-24-2010 at 03:55 AM.
NiLuJe is offline   Reply With Quote