USB driver installation failed, root password, flashing emmc

Hi,

Having bought a Beaglebone Rev A5C I wanted to flash the latest Stretch LXQT.
In the process of doing so a couple of issues occured.
When first plugging in the BBB USB connection no devices are recognized in the device manager.

Neither COM ports, nor network adapters.
Installing the Drivers did not work either. Also tried

Anyways I went ahead and wrote the image to a micro SD card.
Booting from SD is possible - logging into debian with temppwd.
However sudo for root with a blank password does not work.
Therefore modifying ‘sudo nano /boot/uEnv.txt’ for eMMC is not possible.

When I try to flash whatsover, pressing down SW2, the normal ‘heartbeat’ blinking comes on, not the expected continuous ‘1-2-3-4’

I have also tried to recover the root password in case the previous owner had one set and it’s blocking somehow.
Unfortunately the UART-USB can’t establish a connection - I guess also because USB is not showing up?
Not having used the UART adapter before I cannot verify…

Am I missing a point here?
Is ‘heartbeat’ normal for flashing and I have not waited long enough?

Regards,
Robert

The A5C only has a 2GB eMMC, first thing to double check, did you try
flashing the 2GB LXQT or the 4GB LXQT image?

Because, trying to flash the bigger image on the A5C will leave the
eMMC in a fun un-bootable state... Till you reflash it with a 2GB
image..

Regards,

On Sun, 12 Aug 2018 04:24:50 -0700 (PDT), Robert Julius Worm
<robert.julius.worm@gmail.com> declaimed the
following:

Anyways I went ahead and wrote the image to a micro SD card.
Booting from SD is possible - logging into debian with temppwd.
However sudo for root with a blank password does not work.
Therefore modifying 'sudo nano /boot/uEnv.txt' for eMMC is not possible.

  "sudo whatever" should be asking for the password of the current user,
not for a root password.

  Both the Beaglebone Black and the R-Pi are configured with the default
user have "sudo" privilege (and the R-Pi even nags one to change the
default password -- heck, I may be in trouble; if I did change it for the
last build I don't remember what it is!).

The "blank" password for root was removed a couple years back.. It's
"slightly" more secure by being "root"...

Thanks for the replies.
It took me more than an hour to notice I had to enter ‘temppwd’…
Regarding the drivers, running ‘bcdedit /set testsigning on’ did the trick, also there was a driver certificate I had not seen.
This far things are working now.

Next step is to use the Texas Instruments LightCrafter boost pack.
Some people are using the Stretch lxqt desktop version.

As Dennis noted this is a 4GB version, when connected all LEDs just stay on.
Before I was using the Debian 9.4 2018-06-17 4GB SD IoT image which worked fine.
Is there a way to work around?