Migrating Kodi 14 from Pivos to OSMC on Vero 4K+

I currently have an aging Pivos box running Kodi 14. I’d like to buy new hardware and am strongly inclined to order the Vero 4K+.


  1. is Kodi pre-installed on top of this OSMC on the Vero 4K+ and what version?

  2. as new Kodi versions are available, are we going to be able to upgrade or do we have to wait for some custom forked version for OSMC?

  3. Can I move the entire userdata folder over from my Pivos box to the the Vero 4K+ without much issue and…

3b. Does it matter that that userdata folder has been running under Kodi 14?

Note: I know a “fresh start” would be ideal, but organizing my movie/tv collection again would involve so much work that I’d rather stick with the Pivos until it’s totally unusable before doing that.

Well, me too I had a Pivos box before getting the Vero devices (have them all). So to your questions:

  1. Yes - Kodi is pre-installed on all Vero devices.
  2. So far, Sam has always migrated new Kodi versions over, even new debian base. Currently they are working on 18 and will roll it out when kodi 18 will be officialy out of Beta (the way I know them to do it) :slight_smile:
    3.I don’t know. Can’t tell. I moved over a long time ago, and at that time the Kodi versions were the same. So the migration was pretty easy.
1 Like

Yes, Kodi v17 at this moment

New version after reaching stable status are normally provided to OSMC via update within a few weeks. Also beta releases are provided for testing (e.g. There is already a Kodi v18 available for OSMC

An automatic upgrade from 14 to 17 could be tricky

Well you can export and import

1 Like

Thanks for the exteremely quick replies. Follow ups:

I don’t mind waiting but I’m confused. For Pivos, there was a custom build of Kodi they called TOFU. This seems to imply there is a similar situation with KODI on OSMC. One can’t simply run any build of Kodi, nightly or whatever, that one wants, then? Why?

I wonder if I could install 15, 16, 17 on my mac and update them one by one, then transfer that over to OSMC? Any idea bout that?

I’ll research that but if someone is willing to quickly characterize what that involves I’d appreciate it. I suppose what I’m most worried about is retaining all the network file paths to media files, as I’ve got them spread over multiple volumes connected to my Mac, and accessing thru NFS.

That could work, but we need to know more about your current setup. The important thing is are you using a MySQL shared database? Are you sharing media with your Mac?

I don’t think I’m using a MySQL shared databse, almost surely not. All media is connected to Mac over NFS, but on several different physical volumes.

Do you have Kodi on your Mac and share the played status of your media?

First, the fact that Vero runs Kodi v17 shouldn’t stop you buying one. All new devices are going to be running v17.

I would copy the databases from your old box to the vero and see what happens. If that doesn’t work, your idea about going through 15 and 16 on the Mac sounds like a good one. The databases are the same format on all devices but changed a bit with each upgrade.

Hi @redrocklobster

I think everyone has done a good job of answering questions here but just to clarify a few things. OSMC does indeed include Kodi and we always ship the latest stable version. You can however install a test build of Kodi v18 if you’d like to test new features in advance and @gmc produces regular nightly builds. As soon as Kodi v18 reaches its stable release, we’ll have this released via an OSMC update a few days after.

I don’t recommend moving the userdata over, but you can definitely try it. Instead, I’d recommend exporting and reimporting your library.

Our Kodi builds are compiled for our hardware and OSMC (the underlying OS) Similarly, there’s no ‘Kodi’ release for Raspberry Pi. You need an operating system underneath it (i.e. OSMC), which provides its own implementation of Kodi.

We do release regular monthly updates and we will be supporting Vero 4K / Vero 4K + for a long time.

Vero 4K was released in February 2017, and Vero 4K + in July 2018, so we don’t have earlier versions than Krypton (17.0) for this platform.

Hope this helps


I finally received my Vero 4K+. Yay!

I updated Kodi 14>15>16>17 on my Mac and set up a new skin (Xonfluence) also on Mac.

Now how do I get my whole addons, userdata, and thumbnails folders over to .kodi on the Vero? Is FTP the only option? What about via a microSD card? How?

Edit: Moot since I’m now transferring via SFTP (couple hours to go…) Still for academic purposes for info for others…

Other questions, if not answered here will start new threads:

  1. Is there any diagram of the connections on the box itself? I assume that’s a microSD card slot… (there are no labels at all as you know)

  2. What’s the correct power state to be in when replacing the userdata folder? Right now it’s suspended and so far so good…

  3. Can we keep backup folders on microSD card?

  4. how do we return to orginal OSMC set up screen? Or can you?

  5. Since ethernet is working maybe best to shut off wifi?

  6. Confused about remote profiles. See a bunch in MyOSMC, and included remote seems to work, but there is no matching remote selected there. If we select another – for compatibility with a universal remote for example – will the included remote work?

  7. what the heck are all the remote buttons?

  8. really is there a manual for the 4K+ online? That’s one skinny printed manual. :slight_smile:

  9. why the USB dongle for infrared? why not built-in?

  10. where do you plug the extender (there seem to be two matching holes), and does that over-ride the USB dongle?

I will try to answer what I know

Not that I am aware of. But most connectors should be clear. I think the only one that might not be clear are the two 3.5mm connectors. The port nearest the HDMI is the analogue audio out, the port near the edge of the Vero 4K is for the IR receiver.
The SD Card slot is next to the USB Port above the two ventilation slots the one with the notch.

Well ideally you don’t want to have the mediacenter running. You could achieve that by choosing Exit from the Power menu and then login the command line (mediacenter will not restart till you type exit). Or login via ssh and use sudo systemctl stop mediacenter

Yes, even can use the backup tool from MyOSMC

You would need to delete the file \walkthrough_completed

Doesn’t harm to keep it enabled but feel free to disable

Those profiles are for IR remotes. They will work in parallel to the OSMC remote

There are really not much buttons! Which one is not clear to you?

No, but you have the wiki Wiki - OSMC and for everything else please feel free to ask here.

IR is build in the Vero, but the OSMC remote is not IR but RF and therefore you need the USB dongle. Advantage no line of sight needed.

See my earlier replies. The one closer to the edge and no doesn’t replace the RF USB dongle.

1 Like

Thanks for the excellent answers, fzinken.

The main one got lost there – tho still sort of moot, hours later I’m still transferring 3+GB by STFP.

A. How could I copy data from a microSD card to the Vero box?
B. Can the userdata folder be on the microSD card and pointed to it? Like with a symlink? How? Should it?

For me, exit returned to ba blue screen and then just started right back up.

Ok, thanks. I ask for another reason: I just want to determine which IP is ethernet and which is wifi. Ideas on that?

OK, my goal is to program a universal remote, so I suppose I just pick any common remote profile, and plug the IR extender in if necessary. Correct?

Then you’re also saying the USB dongle is used for RF with the included remote. Correct?

There are a couple buttons on that remote that aren’t clear, like a playlist icon, don’t have it in front of me right now. Be nice to have a diagram.

This indicates a network issue (shoulnd’t take longer than an hour). Suggest checking your network speed with iperf3.

Yes the SD Card wild be automount under /media and you simply can copy from there.

Technically yes, but not recommended as the emmc will be 10x faster and reliable than the SD Card.

Sorry, forgot. When the blue screen comes up need to press ESC but anyhow the SSH method is easier.

MyOSMC → Network → Wired/Wireless will show the IP

Yes that is how people do it


I think the chap has covered everything; but do let us know if anything is outstanding,


Thanks again fzinken & Sam. Almost got this up and running as desired. Main remaining problem is acceptable control with Harmony Remote, but as I realize there are other threads here for that, I’ll pick (most of) those up elsewhere. So here are some questions and comments on experience:


  1. Any idea why it’s mounted under media/3333-2222/ (I mean with such a number) and is that path expected to be stable?
  1. How do you press ESC? (If it has to be mapped onto a universal remote, how is that done, pref with the keymap editor addon?)

  2. This is probably a question for Harmony thread, but any idea why a startup action would cause the OSMC to reboot each time? In the action I’m using (based on Phillips SRM 5100), if I switch “activities” and back to OSMC, the box doesn’t reboot. If I power off system and hard power back on, Vero reboots (though it had remained on).


• A migration guide would have been helpful in the Wiki. It could include some of the main things I’ve been asking about in this thread, esp how to transfer an old set up via an SDCard to new Vero box. Best practices, etc, including how to copy, how to quit the mediacenter, etc.

• I found that NFS access on Vero under Kodi 17 is more restrictive than Pivos under Kodi 14. Don’t know where problem cropped up, but with the former I couldn’t access certain directories on NFS shares that I could with the latter. It turned out that I had to set permissions on directories for read access to “everyone”. read/write access for user, system, admin was not sufficient as it was previously. Seems related to this thread.

• Great place to put some diagrams of the box connections and the remote buttons. May seem obvious, and mostly is, but would be good reference…

It’s auto mounted under the “label” of the SD Card. If you want to change that you need to change the label of the SD Card.

Well this only make sense if you have a keyboard attached. Generally I would do all command line operations via SSH as it is much easier.

Feel free to start a Wiki entry, people can contribute.

1 Like

You can rename the drive in Windows to something more unique if you prefer, like ‘redrocklobster card’.

See Accessing the command line - General - OSMC

Not sure – maybe it’s sending a reboot remote code.

To be honest: not a lot of people migrate from such old versions of Kodi. I’m sure we can get something sorted for the near future.

For security reasons NFS is a bit more locked down than it used to be


1 Like

I managed to install iperf3 on my Mac via homebrew. It doesn’t appear to be pre-installed on OSMC, nor is there even a /usr/bin/ruby/ … I’m marginally familiar with unix, and can follow directions, but I have no idea how to install iperf3 on the OSMC. I don’t even know if I’d be looking for a ubuntu or linux binary or what. Suggestions?


sudo apt-get install iperf3

Thanks Tom.

1 Like

awesome. installed. attempted to follow directions here, but can’t connect. I see the server operates on a particular port. Do you need to specify the port on the client? I tried with IP:port, but that didn’t work either. I tried with Mac as server and vice versa. With Vero as server:

osmc@Vero:/$ iperf3 -s
Server listening on 5201

MacPro: user$ iperf3 -c
iperf3: error - unable to connect to server: Host is down
MacPro:user$ iperf3 -c
iperf3: error - unable to connect to server:

with Mac as server, without specifying port it just runs with no output until terminated. with specifying port it errors.

MacPro:doc lryter$ iperf3 -s
Server listening on 5201

osmc@Vero:/$ iperf3 -c
^C- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
iperf3: interrupt - the client has terminated
osmc@Vero:/$ iperf3 -c
iperf3: error - unable to connect to server: No such file or directory