Red light on, Vero 4K doesn’t start anymore

I seem to have the same issue on my original Vero 4K (non plus).

It was connected to my secondary tv and hadn’t been touched for a long time (around a year?). It was still on, showing a directory listing of a directory. I tried to navigate to the parent directory, and it froze, with a popup saying something like “Invalid Argument” if I recall correctly. I couldn’t close the popup. Clicking the arrows on the remote I could still hear the “click” sound of navigating between directory items, but the screen was not updating.

I unplugged the device, waited few seconds, plugged it back in, and got the red light and nothing on HDMI output. I tested the PSU of my Vero V (should be compatible, right?), but same thing. I tried creating a reinstallation media to a micro sd card and booting it again, but the light remains red and the HDMI remains dead.

I will try to find a USB-USB cable somewhere, but I don’t think I have one.

Are there any instructions around for trying the eMMC pin short, as a last ditch effort before ordering a Vero V to replace it?

Hi @jkytomak, I split your post from the original months-old topic to prevent necroposting.
Thx for your understanding.

The Vero V PSU will be compatible.

I wouldn’t look at shorting anything yet, and even if you do, you’ll need a USB A-A cable at hand for it to be of any benefit

Sam

Thanks.

I went out and got a USB-A to USB-A cable. Connected it to the white USB connector on my Vero 4K. I get the red light, and using lsusb from homebrew on my Mac, I get the following devices:

Bus 001 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub
Bus 001 Device 003: ID 05e3:0749 Genesys Logic, Inc. USB3.0 Card Reader  Serial: 000000001536
Bus 001 Device 001: ID 05e3:0610 Genesys Logic, Inc. USB2.1 Hub
Bus 001 Device 004: ID 1b8e:c003 Amlogic, Inc. GX-CHIP
Bus 000 Device 000: ID 05e3:0626 Genesys Logic, Inc. USB 3.1 Bus
Bus 000 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Looks like corrupt eMMC?

It’s very difficult to corrupt the eMMC and put it in such a state. It is more likely that it has failed unfortunately.

I’ll send you some instructions via PM

A post was split to a new topic: Vero rebooting