- FRESH DOWNLOAD UNINSTALL SKIN
- FRESH DOWNLOAD UNINSTALL ANDROID
- FRESH DOWNLOAD UNINSTALL SOFTWARE
- FRESH DOWNLOAD UNINSTALL MAC
FRESH DOWNLOAD UNINSTALL SKIN
It’s advisable that you revert to the default skin so that the steps will be the same. But since Kodi has a lot of different builds, chances are your screen will look a little different. Although this method might work fine on older Kodi versions, we weren’t able to verify it. The steps below were tested on Kodi 17.4. Universal Method: Removing Builds and Add-ons from Kodi 17.X
FRESH DOWNLOAD UNINSTALL ANDROID
But just in case, we have also included a second method that is effective on Android devices.
FRESH DOWNLOAD UNINSTALL MAC
The following steps are universal and should work on any platform that runs Kodi ( Windows, Mac OS, Linux, Raspberry Pi, etc.). This is also effective in solving the common dependencies error. If you can’t wait to get rid of an add-on, or you simply installed the wrong build, follow up with the methods below. By following one of the methods below, you will be able to fresh start Kodi. Luckily, there is a way to remove any build or add-on you might have installed on Kodi.
Even more, this is especially true on Smart TVs, Android boxes and similar devices that work with limited specifications. But from my personal experience, some of them will beautify some things at the expense of performance. Some add-ons and builds will add to the already great functionality that Kodi has.
FRESH DOWNLOAD UNINSTALL SOFTWARE
However, sometimes such changes are undone by uninstalling the package (whether or not it's a purge rather than a remove).If you use Kodi, chances are you already experimented with the various builds and add-ons that the software has to offer. Using purge or -purge remove instead of remove does not reverse changes to existing systemwide configuration files provided by other packages or created manually by the user. It does not remove new gconf or dconf keys, or reverse any gconf or dconf configuration changes. It does not reverse changes made to existing user-specific configuration files. Either way, you can see them with ls by using the -a or -A flag, and you can see them in Nautilus and most other file browsers/managers by pressing Ctrl+ H or going to View > Show Hidden Files.