Vero 4k reboot loop (can't recover- help!)

Help and Support Vero 4K / Vero 4K +
1

Reboot loop was noticed when I woke up this morning.

Had no idea what was going on, so I figured I would just wipe it and start clean to be certain nothing was corrupt with my kodi setup (had some weirdness recently, videos would take a minute to start with no indicator that it was going to play or not.)

Used this guide. And, I’ve tried both the March and the January image.

Example of the install.log that is left on my usb drive after:
Thu Jan 1 00:00:14 2015 Starting OSMC installer
Thu Jan 1 00:00:17 2015 Detecting device we are running on
Thu Jan 1 00:00:17 2015 Mounting boot filesystem
Thu Jan 1 00:00:17 2015 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:17 2015 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Thu Jan 1 00:00:17 2015 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:17 2015 Using device->boot: /dev/sda1 and FS: fat32
Thu Jan 1 00:00:17 2015 Filesystem defined by /mnt/boot/filesystem.tar.xz
Thu Jan 1 00:00:17 2015 No preseed file was found
Thu Jan 1 00:00:17 2015 Flash looks OK
Thu Jan 1 00:01:23 2015 Creating root partition
Thu Jan 1 00:01:24 2015 Calling fmtpart for partition /dev/vero-nand/root and fstype ext4
Thu Jan 1 00:01:34 2015 Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=2 blocks, Stripe width=1024 blocks
936560 inodes, 3745792 blocks
187289 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3837788160
115 block groups
32768 blocks per group, 32768 fragments per group
8144 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: 0/115 done
Writing inode tables: 0/115 done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: 0/115 done

Thu Jan 1 00:01:34 2015 From a root partition of /dev/vero-nand/root, I have deduced a base device of /dev/vero-nand/roo
Thu Jan 1 00:01:34 2015 Mounting root
Thu Jan 1 00:01:34 2015 Trying to mount to MNT_ROOT (/mnt/root)
Thu Jan 1 00:01:34 2015 Using device->root: /dev/vero-nand/root
Thu Jan 1 00:01:34 2015 Extracting files to root filesystem
Thu Jan 1 00:01:34 2015 Starting extract process …
Thu Jan 1 00:01:34 2015 Extracting from /mnt/boot/filesystem.tar.xz
Thu Jan 1 00:02:49 2015 Extraction of root filesystem completed
Thu Jan 1 00:02:49 2015 Configuring bootloader
Thu Jan 1 00:02:49 2015 Boot changed. Re-mounting the real /boot
Thu Jan 1 00:02:49 2015 Trying to unmount MNT_BOOT (/mnt/boot)
Thu Jan 1 00:02:49 2015 Using device->boot: /dev/sda1
Thu Jan 1 00:02:49 2015 Could not unmount old boot partition
Thu Jan 1 00:02:49 2015 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:02:49 2015 Using device->boot: /dev/sda1 and FS: fat32
Thu Jan 1 00:02:49 2015 Could not mount new boot partition
Thu Jan 1 00:02:49 2015 Configuring bootloader: moving /boot to appropriate boot partition
Thu Jan 1 00:02:54 2015 Configuring boot cmdline
Thu Jan 1 00:02:54 2015 Configuring /etc/fstab
Thu Jan 1 00:02:54 2015 Successful installation. Dumping log and rebooting system

After it reboots a dozen or so times it will land on the language selection screen and I am able to get to the networking part - choose manual, but as soon as I enable the wireless it will reboot.

No idea what to try next.

2

Can you attach an Ethernet cable instead, or not set up WiFi and see if this helps?

Sam

3

Started the process from scratch. New USB with freshly downloaded image, but this time with the device plugged into an Ethernet cable from the start.

HDMI,USB keyboard, Ethernet, and USB drive then added power.

Going to live document what it does… excuse the format:

Installed Successfully screen… reboot and please stand by, repeat x20 gave up… I think it actually won’t load this way at all - so different experience suggesting progress of some kind.

Unplug vero, remove usb drive, replug device… same stand by loop half a dozen or so times then shifted to a sad face, which reboots to another sad face. - another different / progress?

Unplug vero / replug - boot text scroll to sad face reboot loop.

Took a video of the boot text, so I could see what was happening…

“failed to start load kernel modules” is the error - everything else says “OK”

4

Install log on usb drive looks identical, except timestamps are sometimes different by a couple seconds.

5

Try another power supply (5V, 2A) or powering the device via a USB-A cable.

1 Like
6

I’ve no other device that shares the same plug type matching that power requirement (closest I found was 5v 1.5a - it did nothing, but was in my box of cables and very well could be 20 years old, so no telling if it even works.)

I have a ton of USB-A to C cables for charging phones, tablets, etc. and I have C to C, but plugging an A to C into a C outlet with the A side in the vero results in nothing I don’t know if this is by design for the cables, or because the result is nothing (tried both USB slots on the vero.)

7

It would need to be USB-A to USB-A.

When you say the 5V 1.5A does ‘nothing’ - does the device start at all?

8

Yeah. 5V 1.5A - no front red light blink, no HDMI output, seemingly nothing at all.

I don’t have an A to A.

Went to Target and Walmart for either an A to A or a 5v 2A. No go for both options.

I ordered a new power supply from Amazon - Will be here Saturday. Will update after testing.

9

Power supply came early.

It was 100% a power supply issue.

10

I am glad this is now resolved.