[kaspar]

Long read. Main point in bold.

So yesterday I was haphazardly attempting to install arm64 Debian .deb packages with Kterm. I was trying to get apt and its dependencies to work. Dpkg was being difficult, so I decided to try upgrading busybox. I wanted to tinker with running things natively instead of through Alpine chroot. I wanted to get bluez or something working so I could pair a keyboard.

Well, I did dpkg -i busybox_1.35.0-4+b3_arm64.deb --force-depends. It appeared to be successful except it said something like "dpkg: can't create backup status file." When I entered "exit" in Kterm, the command didn't work the first time. I did it again, and it brought me to the home screen. Then I went to launch Kual, and the screen went white. I held down the power button and have been stuck in an endless boot loop ever since. I had mntroot rw enabled.

The screen with the Kindle logo and the tree appears, the front light flashes on and off, and the screen goes blank, the back again. It's been going on for about 16 hours now. The battery level was about 50% when this began. It never shows the booting loading bar that I'm used to seeing.

Obviously I know I have made a mistake in tinkering, but is there a way out of this boot loop? I'm used to breaking things while I learn, but some devices are more forgiving than others.

Will letting the battery completely die result in anything different? Or should I have the device charging? Holding the power button for 60s or more does not have any effect (light goes green, light flashes yellow, light goes back to green, and no different screen appears).

I had actually been on a pretty good roll with the Scribe. I was running Alpine chroot with a VNC client and had it working as a second screen for my 2011 Macbook Air for writing outdoors. The latency was completely fine.