The console is never found
Use a cable that carries data. Hold the tweezers on both pads while you plug it in, not after. On Linux, run the script with sudo. On Windows, if Device Manager shows an unknown device, give it the WinUSB driver with Zadig (device 0BB4:0C01) or install Google's USB driver, then try again.
Zadig
The script refuses the image
A kernel image is exactly 8 MiB and starts with a FIT header; anything else is refused before the console is even looked for. Sony's kernel is recognised by its checksum, Lumen's backups by the .md5 or MANIFEST file next to them: keep those files together.
It was written but the console still does not start
Then something other than the kernel is damaged. Lumen's full firmware backup (lumen/backup/firmware) has every system partition of your console; open an issue on GitHub with what you see and we will look at it with you.
GitHub issues
Fastboot mode never appears
The bootloader lives in its own area of the memory, which nothing in Lumen ever writes, so fastboot should always be there. If it is not, the remaining way in is MediaTek's own USB download mode, which needs specialised tools: ask on GitHub before trying anything.
Fastboot mode on the PlayStation Classic was documented by CyberCX.