The storage partition exists, but it's ext4 formatted which means Windows cannot "see" the partition (because Windows doesn't support ext4). You can see the partition on any Linux OS.
Boot LE, enable SSH, login using WinSCP and copy the advancedsettings.xml file, or use PuTTY and copy/paste (might be easier and avoids the temptation of Windows users to create incompatible line-ending files in Notepad.exe).
If you have pirate repo's install you are asking for help in the wrong forum.
It would be bBest to ask for help in the add-on support thread in Kodi forums (most add-ons have one) as it's nothing to do with us and we have no idea how it works or what the problem might be.
In 9.2.1 onwards, in the network settings (in the LE settings add-on).
The cifs.sample (renamed as per directions in the file) is for mounting an SMB share to the local filesystem. It's the Linux equivalent of moutning an remote drive in Windows (Z:\ etc.).
ISTR there is some ongoing effort to rework ISO handling in Kodi (using newer libraries) and this is not complete yet.
If you restore bootsector.img to the USB/SD using the Creator app (or any other) it will allow Windows to 'see' an unformatted drive at full capacity again.
There are some things that need to be removed from device-tree and forced via u-boot before you'll get HDMI output on C1. It's very active but also very slow progress.
Original RPi (1) boards are probably the slowest but still stable things that we're still technically supporting. NB: Meson 8* Lives! might dispute your S805/C1 theory but there are no public images at this time.
xfocus29 glad you got there.
Swap things around then. Write the A95XMAX_boot.img to USB and boot from it, and put the restore files on the SD card.
Get a Raspberry Pi 3B+ .. or even the 2GB 4B model. For the sake of $20 difference in price you can have something reliable and not needing to be on the bleeding edge of development. Do you prefer to watch movies or forever chase down fixes?
If you're at the LE serial console "emmctool" will tell you which is the /dev/device for emmc, so connect ethernet and scp the A95X .img to /storage and then write u-boot to emmc with "dd if=A95MAX_boot.img of=/dev/mmcblkX bs=1M" .. this should make the box bootable from emmc again and you free up the SD card for booting some kind of OS image (LE, Armbian, etc.).
What OS do you want to restore to emmc? .. and if you already have some kind of files, what are they called and what format are they? (and where did you get them from).
I said "write the image to USB" e.g. same as you wrote the other image to SD card, not "copy paste the file" so that's why it's not doing anything. Note that once the image is written and the image is mounted, you need to access the USB and edit the uEnv.ini file to set the name of the dtb file to use.
put the A95MAX_boot.img on SD card, use any SD/USB writing app (even ours, you can drag/drop any .img file no the GUI and we'll use it.
put the AMLG12 on a USB stick.
If you're lucky it will boot u-boot from SD and then search/find the LE boot files on the USB.
The "G12A:BL:0253b8:61aa2d;FEAT:F0F831B0:12020;POC:F;RCY:0;EMMC:0" stuff means no bootloader on eMMC. It's actually a better position to be in than having the wrong bootloader (as then you're in pin-shorting territory). If you put A95XMAX_boot.img on an SD card it will boot from the card and start looking for something to boot. If the u-boot environment contains the usual Amlogic bsp garbage it will look for some "autoscript" files or boot.ini or boot.scr .. so I would start with putting LibreELEC-AMLG12.arm-9.80.0-box.img.gz on a USB stick, setting a dtb name in uEnv.ini - pick another G12A device like X96max or U200. If you're lucky it will find the USB and boot, and tthe UART will then give you access to an OS and console where you have more tools to play with. I suck at figuring out all the sector counts, but as a minimum you can then "dd" the A95XMAX_boot.img back to the emmc device, and then you can probably run LE or other distro's from an SD card.
Enable authentication on the LE samba server, set a credential, then use the credential on the Win10 side.
Interface naming is determined by kernel hardware probing order. As a broad rule "internal" hardware normally probes first, but it's not guaranteed, so if the USB device is probed first it will be wlan0, and the internal becomes wlan1, etc.
WiFi has nothing to do with Kodi.
Do a couple of reboots and see if the MAC address of the wlan0 (USB) interface changes with each boot?
