Vero V Upgrade to 2025.03-1 went wrong, also error during USB install

[Rozz]

Hi all,
I am a long time user of the Vero 4K and the Vero V, using the V as my main, i alway had to update via cli (sudo apt-get update and sudo apt-get dist-upgrade) since the update via my-osmc skin always stays on downloading update for hours.
No problem to update via cli, until now.

Ran the 2 commands, rebooted and spalsh screen stayed on the S905x4 logo, could nog get in via ssh.

Next best thing, download the image and install via USB, but on both the 2025.10-1 and 2025.03-1 i get an error after initial installation:

This is the install.log which is on the usb:
Wed Jan 1 00:00:12 2020 Starting OSMC installer
Wed Jan 1 00:00:13 2020 Detecting device we are running on
Wed Jan 1 00:00:13 2020 Mounting boot filesystem
Wed Jan 1 00:00:13 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:13 2020 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Wed Jan 1 00:00:13 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:13 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:00:13 2020 Filesystem defined by /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:00:13 2020 No preseed file was found
Wed Jan 1 00:01:16 2020 Creating root partition
Wed Jan 1 00:01:16 2020 Calling fmtpart for partition /dev/osmcroot and fstype ext4
Wed Jan 1 00:01:17 2020 Creating filesystem with 7494656 4k blocks and 1875968 inodes
Filesystem UUID: 5e573dd5-af93-4ff4-875e-2426ad476853
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

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

Wed Jan 1 00:01:17 2020 From a root partition of /dev/osmcroot, I have deduced a base device of /dev/osmcroo
Wed Jan 1 00:01:17 2020 Mounting root
Wed Jan 1 00:01:17 2020 Trying to mount to MNT_ROOT (/mnt/root)
Wed Jan 1 00:01:17 2020 Using device->root: /dev/osmcroot
Wed Jan 1 00:01:17 2020 Extracting files to root filesystem
Wed Jan 1 00:01:17 2020 Starting extract process …
Wed Jan 1 00:01:17 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:37 2020 Halting Install. Error message was: tar: corrupted data
Wed Jan 1 00:01:38 2020 Extraction of root filesystem completed
Wed Jan 1 00:01:38 2020 Configuring bootloader
Wed Jan 1 00:01:38 2020 Boot changed. Re-mounting the real /boot
Wed Jan 1 00:01:38 2020 Trying to unmount MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:38 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:38 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:01:38 2020 Configuring bootloader: moving /boot to appropriate boot partition
Wed Jan 1 00:01:38 2020 Vero V family: bootloader to be flashed is u-boot.bin.sd.bin.device.signed
Wed Jan 1 00:01:38 2020 Configuring boot cmdline
Wed Jan 1 00:01:38 2020 Configuring /etc/fstab
Wed Jan 1 00:01:38 2020 Successful installation. Dumping log and rebooting system

Used the windows osmc-installer to download to 2 images, also downloaded the 2 images and used option the use the local build, so all 4 ways give the same error.

[Rozz]

[Rozz]

Used both USB ports, also tried balena etcher to write image to usb, tried 3 different usd drives.
Sooo…i am out of options on my side…HELPPPPP

[sam_nazarko]

Can you give me the checksums of the images you downloaded?

Sam

[Rozz]

Both match as far as i can see…

rozz@uPower:~/Downloads$ md5sum OSMC_TGT_vero5_20250303.img.gz
b9d01f9fe8da82c0dfc39bb49cf29c5e OSMC_TGT_vero5_20250303.img.gz

rozz@uPower:~/Downloads$ md5sum OSMC_TGT_vero5_20241104.img.gz
7fd501da3075ce0a49a8889c087df907 OSMC_TGT_vero5_20241104.img.gz

UPDATE:
Using the Linux usb installer also gives the same error.

UPDATE 2:
Also tried the 2024.08-1, same error.

[Rozz]

@sam_nazarko I have created a support ticket, or do you have anything more i could test or try?
I updated my other Vero 4k without any problems, so nearly 100% sure the problem lies with my Vero V and not any kind of image/install usb.

[JimKnopf]

How many USB devices have you tried?
Have you tried an SD-card?

[Rozz]

Thanks for the reminder @JimKnopf, i tried it just now and the installs goes through OK!!!

Stupid i did not think of that myself.
Setting it all up as we speak.

This thread can be “closed”

[Rozz]

sooo, here i am again, exactly the same error trying to update to 2025.08-1, but this time i tried all of the above, 2 different usb drives, 2 different sd cards, windows installer, balena etcher and downloaded images, checksums of the different files are correct.

So what do i do now?

Below is the install.log after failed update:

Wed Jan 1 00:00:13 2020 Starting OSMC installer
Wed Jan 1 00:00:14 2020 Detecting device we are running on
Wed Jan 1 00:00:14 2020 Mounting boot filesystem
Wed Jan 1 00:00:14 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:14 2020 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Wed Jan 1 00:00:14 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:14 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:00:14 2020 Filesystem defined by /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:00:14 2020 No preseed file was found
Wed Jan 1 00:01:17 2020 Creating root partition
Wed Jan 1 00:01:17 2020 Calling fmtpart for partition /dev/osmcroot and fstype ext4
Wed Jan 1 00:01:18 2020 Creating filesystem with 7494656 4k blocks and 1875968 inodes
Filesystem UUID: 63578aa1-ea99-4e30-b1cd-26938cfd45a5
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000

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


Wed Jan 1 00:01:18 2020 From a root partition of /dev/osmcroot, I have deduced a base device of /dev/osmcroo
Wed Jan 1 00:01:18 2020 Mounting root
Wed Jan 1 00:01:18 2020 Trying to mount to MNT_ROOT (/mnt/root)
Wed Jan 1 00:01:18 2020 Using device->root: /dev/osmcroot
Wed Jan 1 00:01:18 2020 Extracting files to root filesystem
Wed Jan 1 00:01:18 2020 Starting extract process ...
Wed Jan 1 00:01:18 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:38 2020 Halting Install. Error message was: tar: corrupted data
Wed Jan 1 00:01:38 2020 Extraction of root filesystem completed
Wed Jan 1 00:01:38 2020 Configuring bootloader
Wed Jan 1 00:01:38 2020 Boot changed. Re-mounting the real /boot
Wed Jan 1 00:01:38 2020 Trying to unmount MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:39 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:01:39 2020 Using device->boot: /dev/sda1 and FS: fat32
Wed Jan 1 00:01:39 2020 Configuring bootloader: moving /boot to appropriate boot partition
Wed Jan 1 00:01:39 2020 Vero V family: bootloader to be flashed is u-boot.bin.sd.bin.device.signed
Wed Jan 1 00:01:39 2020 Configuring boot cmdline
Wed Jan 1 00:01:39 2020 Configuring /etc/fstab
Wed Jan 1 00:01:39 2020 Successful installation. Dumping log and rebooting system

[sam_nazarko]

Looks fine - what’s the issue?

Is there a specific reason you chose to reinstall instead of updating?

[Rozz]

Because the update in the my-osmc skin stays stuck on “downloading” and does nothing.

Went the reinstall route because i wanted a fresh start anyway.

But no matter how i try, it fails everytime with the corrupted data error

[Rozz]

Here is the full fault, exactly the same as when i first started this thread, but now not even trying the sd card works.

Install.log:

Wed Jan 1 00:00:10 2020 Detecting device we are running on
Wed Jan 1 00:00:10 2020 Mounting boot filesystem
Wed Jan 1 00:00:10 2020 Trying to mount to MNT_BOOT (/mnt/boot)
Wed Jan 1 00:00:10 2020 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Wed Jan 1 00:00:10 2020 Filesystem defined by /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:00:10 2020 No preseed file was found
Wed Jan 1 00:01:13 2020 Creating root partition
Wed Jan 1 00:01:13 2020 Calling fmtpart for partition /dev/osmcroot and fstype ext4
Wed Jan 1 00:01:14 2020 Creating filesystem with 7494656 4k blocks and 1875968 inodes
Filesystem UUID: 65da30e7-d385-40ad-b2cc-53fda97ea7da
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000

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


Wed Jan 1 00:01:14 2020 From a root partition of /dev/osmcroot, I have deduced a base device of /dev/osmcroo
Wed Jan 1 00:01:14 2020 Mounting root
Wed Jan 1 00:01:14 2020 Trying to mount to MNT_ROOT (/mnt/root)
Wed Jan 1 00:01:14 2020 Using device->root: /dev/osmcroot
Wed Jan 1 00:01:14 2020 Extracting files to root filesystem
Wed Jan 1 00:01:14 2020 Starting extract process ...
Wed Jan 1 00:01:14 2020 Extracting from /mnt/boot/filesystem.tar.xz
Wed Jan 1 00:01:35 2020 Halting Install. Error message was: tar: invalid tar magic
Wed Jan 1 00:01:35 2020 Extraction of root filesystem completed
Wed Jan 1 00:01:35 2020 Configuring bootloader
Wed Jan 1 00:01:35 2020 Configuring bootloader: moving /boot to appropriate boot partition
Wed Jan 1 00:01:36 2020 Vero V family: bootloader to be flashed is u-boot.bin.sd.bin.device.signed
Wed Jan 1 00:01:36 2020 Configuring boot cmdline
Wed Jan 1 00:01:36 2020 Configuring /etc/fstab
Wed Jan 1 00:01:36 2020 Successful installation. Dumping log and rebooting system```

[sam_nazarko]

Please write the following image to a SD/USB drive using the OSMC Installer selecting ‘local image’.

https://collab.osmc.tv/index.php/s/DHK8jdPMawiF5nW/download/december-recovery-image-verov.img.gz

And please take a screenshot of the contents of the media after doing so to ensure it’s correct.

With the Vero powered off, insert the USB or SD card.
Now apply power with the toothpick pressed in for about 10 seconds and release it. The toothpick needs to go in the 3.5mm CVBS port.

After a period of time, Vero V’s blue LED should start blinking periodically.
This means that the device has been re-imaged.

You can now remove the installation media, remove power, wait five seconds and re-apply power.
The device should now boot.

[Rozz]

Thanks Sam, but still no go.
I tried both usb ports and the sdcard slot, with and without all the others cables installed (network, hdmi, optical)
Also used a usb stick with activity led so i could see if it was being accessed.

After pressing and holding the “reset” in the 3.5mm port (nice touch placing it there btw) inserting the power cable, after about 10sec removing the toothpick, no activity shown on the usb, the 10 sec is about the same time when the blue led turns off after powerup.
Also tried different times to let go.
Waited arround 10min after every try

Seems the exact same thing as what “daytooner” had: Vero5 is now a brick

[sam_nazarko]

Daytooner resolved the issue by using another USB.

You could also reinstall OSMC using a USB A to A cable

What do you see on the screen if you try again with HDMI connected?

Sam

[Rozz]

Sam, believe me, i tried lots of different usb sticks and micro sdcards

Just tried a usb-A to usb-A extension cable, i thinks thats what you meant? still no difference.

Thanks to the activity led on the OCZ usb stick, i can see activity, when plugging in the power with the button pressed, i can see it sees the usb, but when the blue led goes out, it doenst read the usb anymore and comes to this screen:

I tried different times in holding down the button, all no difference.

When the hdmi is looped through my receiver is see this screen very briefly and ends with above screen again.

Sometimes it ends with this screen, depends on which usb port i think:

[sam_nazarko]

Sorry, I’m asking if you have a straight USB A/A cable. Then you could flash from a computer.

[Rozz]

huh? ehhh…how?
i maybe have one somewhere.

Anyhow, what programs and or commands do i need to use? and windows or linux? i have both btw.
Willing to try this

[Rozz]

@sam_nazarko Can you please tell me how to flash the V from my computer with the straight usb-a to usb-a
Nearly a week without watching anything kinda sucks

[sam_nazarko]

Sure, do you have the cable?

Sam