Hello,
I have managed to hit an exceptionally esoteric situation (I would say bug) by an unexpected amount of unlucky fumbling.
Device is Volla Plinius plus. The OS is ubuntu touch.
I fastboot flashed vendor_boot.img that contained a broken recovery ramdisk into the phone. I then proceeded into running `fastboot reboot recovery` to test the not-yet-known-broken recovery ramdisk.
However, apparently, this writes the next boot target somewhere in non-volatile memory, causing the bootloader to skip the choice menu (accessed by volume down) every time, since it sees it should boot to recovery. It never clears the recovery-boot flag.
This causes the device to bootloop to broken recovery with no ability to stop it. Removing battery doesnt clear the flag (from which I know it is in non-volatile memory). Plugging in usb in the turned off phone starts the phone / goes into the same bootloop.
Generally, I didn't expect the bootloader to always skip the menu due to a flag in non-volatile memory.
I glanced at viewtopic.php?f=31&t=1042 and it seems there is a potential super-super-screwed-situation tool for fixing the situation. However it seems to need a scatter file for the memory controller(?).
Any help appreciated.