View Single Post
Old 02-15-2025, 03:48 PM   #14
shamanNS
Wizard
shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.
 
Posts: 1,125
Karma: 12345678
Join Date: Feb 2010
Location: Serbia
Device: Kindle PW5, Kobo Libra 2, Kindle PW1
Maybe you could try adding shell script code to rename those 2 ota files ( = undo the rename) back to original names into file named "emergency.sh" and copy it to top level of exported Kindle drive over USB cable? And then force a reboot by holding the power button on Kindle for >15 seconds.

I'm not sure what would be the state of the "bridge" Upstart job after doing a factory reset on device with firmware 5.17.1 or newer. If it still runs that job it should check for the existence of "/mnt/us/emergency.sh" and execute any code you put there.

What did you use originally to rename ota binaries? KUAL extension "renameotabin" or @Marek's "scriptlet" from Discord severe or that thing that does both OTA rename and disables sending logs to Amazon?
shamanNS is offline   Reply With Quote