An apology is in order here. I just went over my notes from years ago and my face is red. I've been playing with x86 builds for so long I lost sight of the differences. Of course what a putz! You can't boot an x86 with an arm build! Sorry for the time wasted here guys. What can I say? When you're 7.4 decades old I suppose my checksums are off a bit.
Forgive me. 
Three full minutes and nothing but blinking cursor. I tried a older usb with LE 9.2x and it boots almost instantly.
Thanks DF. It would be good to have a solution for us with x86 builds but probably more trouble than it's worth. Thanks for asking.
RD
Thanks Da Flex. Trust me I fully understand the creator program and have been using it for years on multiple devices. I simply noticed when I downloaded and ran the creator program to make a bootable usb to prepare the micro sd card it will not boot on my PC. I have two other usb sticks I made over the years that have older LE versions that still boot just fine.
I thought I would get the LE10 install usb ready for a Pi4 and cant make it boot. Multiple attempts and yesterday it reported "locked" or something similar.
Thanks Joe. Using a newer i7-9700k. On the off chance I got impatient I'll run it again and see if maybe some sort of timing issue is the culprit.
Joe,
The short answer is no go. I followed all the steps you provided. Everything completed successfully until boot time and now it says "Error Locked" or something of that nature.
So....I fired up my Linux Mint machine but couldn't download the gz file as a Unicorn invasion was indicated. So I used the file downloaded from the Windows system. Selected make a bootable USB stick in Linux and lo and behold.....same results. Just a blinking cursor. I'm assuming this is not just a windows issue. I have maybe 5 usb sticks and I've tried three of them all with like results.
I would have tried the H2testw but my German is limited to Please and thank you. 
I decided it's time for a shiny new RPi4 so that's my next project and I understand. I'm still stuck on the sd-usb creator issue. I've prepared two different usb sticks of different brands and sizes and neither will boot up on my Windows PC. I have a few other usb sticks with LE9.2 on them which still boot up just fine. What would cause this?
Which of the nightly builds might I try for the Pi3 B? I'm not familiar with the naming conventions. I see RPi2 builds then RK3? A bit confusing to this newbie.
What I'm saying is I never got that far. The install usb would not boot.
I'll give one of those a try and thank you.
Same issue. The usb stick (from the usb creator) will not boot. Only a blinking cursor. It seems odd because I can boot an older version previously installed on another usb stick no problem. I've downloaded the install creator three times and the last try with build suggested and same results. Any thoughts?
Thanks Da Flex I'll try that one as well. The one I downloaded was LibreELEC-RPi4.arm-10.0.1.img.gz from the Download page but the usb stick would not boot as usual. I've never had this issue before.
I thought I might try LE 10 on my Pi3 -B so I downloaded the creator program and the Le10 build for RPi. It completed successfully with no errors. The usb stick refuses to boot on my computer with no screen error just a blinking cursor. I thought maybe something on my PC so I tried booting with an older 6.2 LE build on it with no problem. Humm. Something else wrong here?
Oh sure. Thanks.
I've hit a dead end it seems. I'll have to look in ACME Catalog for a solution.
I apologize for my ignorance here. I posted the results of the "amixer" command using putty in post #38.
This is the output from aplay -L
LibreELEC:~ # aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
hdmi:CARD=HDMI,DEV=0
HDA Intel HDMI, HDMI 0
HDMI Audio Output
hdmi:CARD=HDMI,DEV=1
HDA Intel HDMI, HDMI 1
HDMI Audio Output
hdmi:CARD=HDMI,DEV=2
HDA Intel HDMI, HDMI 2
HDMI Audio Output
hdmi:CARD=HDMI,DEV=3
HDA Intel HDMI, HDMI 3
HDMI Audio Output
hdmi:CARD=HDMI,DEV=4
HDA Intel HDMI, HDMI 4
HDMI Audio Output
default:CARD=PCH
HDA Intel PCH, ALC887-VD Analog
Default Audio Device
sysdefault:CARD=PCH
HDA Intel PCH, ALC887-VD Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
Front output / input
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC887-VD Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
The Kodi audio setting that works with my Sony is:" ALSA:HDA Intel,SNY SONY TV *00 on HDMI#1"
In earlier versions of Chrome I stumbled on hw:0,7 mostly by trial and error. I have no idea what the "7" device is. Maybe you can school
me a bit on what's going on here. Thanks in advance for your patience. 
I understand that I need to find the card name. I'm stumped as to how to find it. At one point in the past before V10 I had to use Custom Audio Device to get any sound at all from Chrome. The settings that worked were hw:0,7 but for some reason I get audio without the custom settings now. So I guess I not understanding where to find the "Card No." When I ran amixer I posted it earlier but it does not show any PCM card numbers just hdmi 0-4. I'm obviously missing something here.
I thought I'd offer an update to this audio issue I've been playing with. I can now watch video without the Chrome crash with
"uh oh something went wrong" error just no audio at this point. Still trying to determine which PCM Chrome is using on my system to move forward Seems a bit more involved than I thought.
I admit I'm clueless here as to which PCM Chrome is using.
I ran amixer with Chrome running and I get this:
LibreELEC:~ # amixer
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',1
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',2
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',3
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'IEC958',4
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Thanks so much Amanda. This issue has been a real bummer for the past few years and I had to create a dual boot system just to deal with this one little bug. Glad to know I'm not alone and thanks again for your hard work as well as the devs who made it happen.
I'll let you know how it works out for me.
RD
I have the same issues described here with my HDMI connection and would appreciate a summary of what was done and steps to fix it. I'm a bit confused as to what was entered and where?
Thanks in advance.
RD
Thanks. I'll give her a try.
