Thankyou, I've re-run all the commands and checked the time, all appear to be good.
Have the same error message, I've got the log file up, and I also have a crash.log file under [developer/KUAL/work/]
[13/10/2019 11:56] KUAL (v. 2.7)
java.lang.RuntimeException: java.lang.NoClassDefFoundError: com.mobileread.ixtab.kindlelauncher.ui.UIAdapter
at ixtab.jailbreak.SuicidalKindlet.<init>(Unknown Source)
at ixtab.jailbreak.SuicidalKindlet.<init>(Unknown Source)
at com.mobileread.ixtab.kindlelauncher.KualKindlet.<i nit>(KualKindlet.java:46)
at com.amazon.kindle.kindlet.internal.kb.zdb(tpb:275)
at com.amazon.kindle.kindlet.internal.kb.KU(tpb:439)
at com.amazon.kindle.kindlet.internal.lifecycle.o.cal l(psb:412)
at edu.emory.mathcs.backport.java.util.concurrent.Fut ureTask.run(fw:491)
at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor.IX(qr:959)
at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(qr:803)
at java.lang.Thread.run(Thread.java:989)
at java.lang.Thread.startup(Thread.java:1066)
Caused by: java.lang.NoClassDefFoundError: com.mobileread.ixtab.kindlelauncher.ui.UIAdapter
at java.lang.Class.runStaticInitializers(Class.java:1 579)
at com.mobileread.ixtab.kindlelauncher.KualKindlet.ge tUI(KualKindlet.java:269)
at com.mobileread.ixtab.kindlelauncher.KualKindlet.<i nit>(KualKindlet.java:152)
at ixtab.jailbreak.SuicidalKindlet.<init>(Unknown Source)
at ixtab.jailbreak.SuicidalKindlet.<init>(Unknown Source)
at com.mobileread.ixtab.kindlelauncher.KualKindlet.<i nit>(KualKindlet.java:46)
at com.amazon.kindle.kindlet.internal.kb.zdb(tpb:275)
at com.amazon.kindle.kindlet.internal.kb.KU(tpb:439)
at com.amazon.kindle.kindlet.internal.lifecycle.o.cal l(psb:412)
at edu.emory.mathcs.backport.java.util.concurrent.Fut ureTask.run(fw:491)
at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor.IX(qr:959)
at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(qr:803)
at java.lang.Thread.run(Thread.java:989)
at java.lang.Thread.startup(Thread.java:1066)
Quote:
Originally Posted by NiLuJe
Check that the date/time is sane on your device, reboot, and if that doesn't help, check the logs (;dm in the search bar).
EDIT: Double-checked, no issues on my end (4.1.3; 4.1.4).
|