View Single Post
Old 09-25-2022, 04:16 AM   #2
Kusuri
Connoisseur
Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.Kusuri ought to be getting tired of karma fortunes by now.
 
Posts: 99
Karma: 909418
Join Date: Aug 2021
Location: Germany
Device: PW4+Fire 7", Onyx Boox Nova Air
i'm not really experienced that much in kindle hacking, but i know a bit of javascript (the code you posted here is js). and my guess is that window.kindle gets defined inside the application self (main kindle UI?), so if you try to access it outside of that context of the application where it is used, it isn't defined as a variable (window.kindle).. so it's undefined.

if i where you, i would try if i somehow could inject code into that main application where that code you posted is used to learn more about window.kindle and what exactly it contains. on a windows pc i would do something like "console.log(window.kindle);" but on a kindle you would need to save it somehow in a logfile i guess.

edit: maybe you could use the KindleTool to extract a kindle update to maybe find more of the code of the main application where the window.kindle gets defined that you can't normally access (in the filesystem of the kindle)?

Last edited by Kusuri; 09-25-2022 at 04:26 AM.
Kusuri is offline   Reply With Quote