On reboot it finds the tar in the update folder and updates and crashes.
...
I'm getting a supply of SD cards tomorrow.
Good. Maybe your current microSD has errors, and the OS can't expand. I would do full check on it. If you use Windows, you can use this tool.
Is 9.1.002 supposed to update itself to 9.2.0?
No, you have to select the 9.2 branch at the LE settings menu.
If you use Etcher to write 9.1.002 to microSD, what happens when you boot the RPi 4B with it?
Read the thread I mentioned above. It contains several tricks you can try to finish booting.
The bottom line is my suggestion to install LE 9.1.002 first, because I think the settings wizard has trouble to start in LE 9.2.
Please try this, I still don't have feedback from the other user. If you're successful, you can update to LE 9.2 by GUI.
We had a nearly identical question a couple of days ago.
We have some threads like this, but I can't verify the fixes, because I'm an RPi 3B+ guy.
Someone said that audio config affects the issue. Read here.
Go into deeper research by using the search function of the forum, doc.
I am able to flash and boot the Raspbian image fine on the same card.
Maybe, but that's still no check of the storage medium.
Sounds like a bad microSD card. Check the card, there are several free tools available.
I have the YouTube add-on, too, and LE did the update to 6.5.2 automatically.
The setting mentioned by Klojum is at Settings -> System -> Addons.
But is a Python script able to run a bash script?
Yes, google it.
Can you describe that login process a little more? I'm pushing the power button on my RPi, and that's the whole story.
You could use /storage/.profile to execute commands at ssh login time.
I can feel your pain. 
I think it's a lot easier to take a ~1.5mm driller, and physically destroy the LED by drilling in.
Read here about sending commands.
Thanks for the log! Looks like the settings wizard has trouble to start in LE 9.2. Try LE 9.1.002. Update to 9.2 by GUI after the setup.
Put it into .kodi/userdata at the STORAGE partition. The leading point makes the directory invisible for some OS'es.
phob08 :
LE creates a symbolic link (symlink) for every connected (and mountable) external storage medium.
External storage access always has to go over such a symlink.
But that's a problem for JDownloader, it can't access files beyond such a symlink.
The easiest solution for you is not to use an external drive as a destination of JDownloader files. Use internal storage instead.
Thanks for testing a different resolution.
