View Single Post
Old 04-24-2017, 11:48 AM   #1751
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Antinoos View Post
Another Point:

I can't confirm the following statement in posting #1 step 8:


As for my KT3 (included that of a friend of mine) this is not (longer) true generally any more (at least since "basic version" 5.8.3 or so). I could jailbreak these devices and treat them like "other devices" in the list, i.e. simply use the "document style" KUAL-KDK-2.0.azw2 file in the document folder without even starting MRPI for this reason. It starts without any problems. The same ist true, btw, for the Vlasovsoft tools etc., they also may be launched alternatively via their respective *.azw2 document.

But of course you may also use the MRPI method. This has a big advantage: You not only have all your hacks in one neat interface - but you can additionally rename the *.kual "document" (empty file, any name possible, just the extension ".kual" matters) to whatever you like. In my case I used "(1) KUAL (Kindle Unified App Launcher).kual" that brings this on top of the alphabetically sorted document list.

HTH.
Then you have discovered a firmware specific (version & build) variation.

Amazon policy on the 8th. generation devices was to ship without active document support.

And my KT3 (still on its original 5.8.5) is consistent with that policy.

BUT - -

It is only a single enable/disable flag in the firmware, it may be getting overlooked in some builds.
It is not like they removed all of the code.

And it was still disabled in 5.8.8 (by inspection, not by test execution), if you are running something different ....

Last edited by knc1; 04-24-2017 at 11:50 AM.
knc1 is offline   Reply With Quote