Simturax

---

Resetting the default skin on Kodi means restoring the built-in Estuary interface — the default skin that comes with every Kodi installation since version 17 “Krypton.” This fixes black screens, skin crashes, and corrupted guisettings.xml files that prevent Kodi from loading properly.

---

⚠️ STATUS DISCLAIMER

Current Kodi Versions: Kodi 21 “Omega” (Stable) | Kodi 22 “Piers” (Alpha/Pre-release)

Important Note: The methods in this guide work for all Kodi versions v17 and above — including Kodi 18 “Leia,” Kodi 19 “Matrix,” Kodi 20 “Nexus,” Kodi 21 “Omega,” and Kodi 22 “Piers.”

⚠️ CRITICAL WARNING: The guisettings.xml file must be edited or replaced while Kodi is completely closed. If Kodi is running, it will overwrite your changes on exit.

🔒 READ-ONLY FILE PERMISSIONS: If guisettings.xml becomes read-only due to system errors or incorrect permissions, Kodi will fail to write settings changes. This causes Kodi to revert to default settings on every startup or fail to boot entirely. Check file permissions before editing — on Linux, use ls -l guisettings.xml; on Windows, right-click → Properties and ensure “Read-only” is unchecked.

---

Why Is Your Kodi Experiencing This Issue?

Kodi’s skin system relies on a configuration file called guisettings.xml , which stores all your interface preferences — including which skin to load. When this file becomes corrupted, inaccessible, or read-only, Kodi either fails to load the interface or reverts to default settings.

Most Common Causes:

Cause	Explanation
Abrupt power loss	A blackout or unplugging your device while Kodi is running corrupts guisettings.xml
Insufficient storage space	Kodi can’t write settings changes when storage is full
Incompatible third-party skin	A skin not fully compatible with your Kodi version crashes on load
Improper shutdown	Force-closing Kodi instead of using the exit option leaves files inconsistent
Read-only file permissions	System errors or manual changes can lock guisettings.xml as read-only, preventing Kodi from saving settings
Fire OS sandbox restrictions	On Fire TV devices, external file access is restricted, making manual recovery difficult

---

⚡ The 45-Second Fix

How to Reset Kodi to Default Skin in 4 Steps:

1. Open Settings (gear icon) from Kodi’s home screen.
2. Select Interface → Skin.
3. Select Estuary from the list of installed skins (it’s always available — do NOT click “Get more…”).
4. Confirm “Yes” — Kodi switches back instantly.

If Kodi won’t boot, skip to Action 2 below.

---

Action 1: Reset via Kodi Interface (Standard Method)

This is the safest and quickest method when Kodi still launches properly.

Step-by-Step: Switch Back to Estuary Through Settings

1. Launch Kodi and wait for the home screen to load.
2. Click the gear icon (Settings) in the top-left corner.
3. Select Interface from the settings menu.
4. Click Skin in the left sidebar.
5. Select Estuary from the list of installed skins.
6. When prompted, click Yes to confirm the change.
7. Kodi will reload the interface with the default Estuary skin.

💡 Pro Tip: Estuary is always installed as the default skin. You do not need to click “Get more…” — that button is for installing additional skins from the repository.

---

Action 2: Manual Reset via guisettings.xml (For Unbootable Kodi)

If Kodi crashes on startup, shows a black screen, or you can’t access the Settings menu, use this method.

Fix 1: Delete or Rename guisettings.xml

1. Locate your Kodi userdata folder (Kodi must be fully closed):

Platform	Userdata Folder Path
Windows (Standard)	%APPDATA%\Kodi\userdata\
Windows (UWP/Store)	%LOCALAPPDATA%\Packages\XBMCFoundation.Kodi_4n2hpmxwrvr6p\LocalCache\Roaming\Kodi\userdata\
macOS	~/Library/Application Support/Kodi/userdata/
Linux	~/.kodi/userdata/
Android	Android/data/org.xbmc.kodi/files/.kodi/userdata/
Fire TV / Fire OS	/storage/self/primary/Android/data/org.xbmc.kodi/files/.kodi/userdata/

2. Find the file named guisettings.xml in the userdata folder.
3. Delete it or rename it to guisettings_backup.xml (recommended for safety).
4. Restart Kodi. A fresh guisettings.xml will be auto-generated with all default settings, including the Estuary skin.

⚠️ WARNING: This resets all Kodi interface settings — not just the skin. Your media library and add-ons remain intact, but you’ll need to reconfigure language, audio, video, and other preferences.

Fix 2: Check and Fix Read-Only File Permissions

If Kodi continues to revert to default settings after you’ve replaced guisettings.xml, the file may be read-only.

On Windows:

1. Navigate to %APPDATA%\Kodi\userdata\
2. Right-click guisettings.xml → Properties
3. Under the General tab, ensure “Read-only” is unchecked
4. Click Apply → OK

On Linux / macOS:

1. Open a terminal
2. Navigate to the userdata folder: cd ~/.kodi/userdata/ (Linux) or cd ~/Library/Application\ Support/Kodi/userdata/ (macOS)
3. Check permissions: ls -l guisettings.xml
4. If the file is read-only, change permissions: chmod 644 guisettings.xml
5. If the file has an immutable flag (Linux), remove it: sudo chattr -i guisettings.xml

🔒 Pro Tip: On Linux systems, you can prevent future corruption by making the file immutable after configuration: sudo chattr +i guisettings.xml. This prevents any program from changing it. Remove the flag when you need to make changes: sudo chattr -i guisettings.xml.

Fix 3: Edit guisettings.xml Directly (Advanced)

If you only want to change the skin without losing all settings:

1. Open guisettings.xml in a text editor (Notepad++ on Windows, TextEdit on macOS).
2. Search for the line containing lookandfeel.skin .
3. Change the value to skin.estuary .
4. Save the file and restart Kodi.

⚠️ CRITICAL: Always edit guisettings.xml when Kodi is not running. If Kodi is open, it will overwrite your changes on exit.

Fix 4: Delete Skin Add-on Folder (Alternative Method)

If deleting guisettings.xml doesn’t work, try removing the skin-specific settings:

1. Navigate to your Kodi userdata folder (see table above).
2. Go to addon_data/ .
3. Find the folder for your problematic skin, e.g., skin.[skinname]/ .
4. Delete the settings.xml file inside that folder.
5. Restart Kodi — it will default back to Estuary.

💡 Why this works: Skin settings are stored in both guisettings.xml and the skin’s own settings.xml file in addon_data/. Deleting both ensures a complete reset.

---

Action 3: Device-Specific Solutions

Fix 1: Fire TV Stick / Fire OS (Sandboxed Access)

Fire OS restricts direct file access, making the manual method difficult.

1. Try the interface method first — if Kodi launches, use Action 1.
2. If Kodi won’t start:

• Clear Kodi’s app cache: Settings → Applications → Kodi → Clear cache.
• Use Kodi’s built-in file manager: Navigate to special://home/userdata/ and delete guisettings.xml from within Kodi.
• Reinstall Kodi as a last resort — this resets everything to factory defaults. See our install Kodi on Firestick guide.

1. Use a file manager app (like X-plore) with ADB access to reach the userdata folder.

⚠️ Fire OS Limitation: On newer Fire OS versions, you cannot access Kodi’s system files from outside the app. Use Kodi’s internal file manager (special://home/userdata/) to manage files.

Fix 2: Android TV / Mobile Devices

1. Go to Settings → Apps → Kodi → Storage.
2. Tap Clear Data — this resets Kodi to defaults (removes all settings but not media files).
3. Alternatively, use a file manager app to navigate to the userdata folder and delete guisettings.xml.

Fix 3: CoreELEC / LibreELEC (Linux-based)

1. Enable SSH access to your device.
2. Connect via SSH and navigate to: /storage/.kodi/userdata/
3. Check permissions: ls -l guisettings.xml
4. If read-only, fix with: chmod 644 guisettings.xml
5. Rename or delete guisettings.xml.
6. Reboot the device — Kodi regenerates the file with default settings.

---

Action 4: Reset Skin Settings Within Third-Party Skins

Some popular skins include a built-in reset option.

Fix 1: Bingie Skin Reset

1. Navigate to Skin Settings → Backup and Restore.
2. Click Reset skin to default settings.
3. Restart Kodi for changes to take effect.

Fix 2: Aeon MQ 9 Reset

1. Go to Skin Settings → Restore Skin Settings.
2. Activate Show Skin Reset Button (Temporary).
3. Select Reset skin over menu.

Fix 3: Generic Skin Reset (If Available)

Many skins include a “Reset to Default” option within their settings menu — look under Skin Settings or Advanced tabs.

---

Best Backup Alternatives to Estuary Skin

If Estuary doesn’t suit your needs after resetting, consider these lightweight alternatives:

Skin	Pros	Cons
Confluence	Classic Kodi feel, extremely lightweight	Default for Kodi v16 and below; may need community ports for v21+
Aeon Nox: Silvo	Highly customizable, great for media libraries	Heavier on resources
Arctic: Zephyr – Reloaded	Modern design, active development	Can cause crashes on some devices

💡 Recommendation: Stick with Estuary for stability on low-powered devices like Fire Sticks. It’s the default skin for all Kodi versions since v17 “Krypton.”

---

Summary & Prevention Tips

Resetting to the default Estuary skin on Kodi is straightforward — use the Settings → Interface → Skin path for accessible Kodi instances, or delete/rename the guisettings.xml file in your userdata folder when Kodi won’t boot.

To Prevent This From Happening Again:

• ✅ Always exit Kodi properly — use the Power menu → Exit, never force-close.
• ✅ Backup guisettings.xml while Kodi is closed — copying it while Kodi is running won’t work.
• ✅ Maintain free storage space — Kodi needs room to write configuration files.
• ✅ Use a UPS or stable power source — abrupt shutdowns corrupt settings.
• ✅ Test new skins in a separate profile before applying them to your main setup.
• ✅ Check file permissions — if Kodi keeps resetting, verify guisettings.xml isn’t read-only.
• ✅ On Linux, use the immutable flag — sudo chattr +i guisettings.xml after configuration to prevent corruption.
• ✅ Consider the Skin Backup add-on — available in the official Kodi repository for automated backups.

---

❓ Frequently Asked Questions (FAQ)

Why does Kodi keep resetting to Estuary on its own?

Kodi resets to Estuary when it cannot write to guisettings.xml. Common causes include:

• Insufficient storage space — Kodi can’t save settings changes
• Read-only file permissions — the file is locked
• Abrupt power loss — corruption occurs during write operations
• Fire OS sandbox restrictions — on Fire TV, external file access is blocked

Solution: Check available storage, verify file permissions, and ensure you exit Kodi properly.

How do I backup and restore my Kodi skin settings?

1. Close Kodi completely — this is critical.
2. Navigate to your userdata folder.
3. Copy guisettings.xml to a safe location.
4. To restore, close Kodi, copy the backup back, and restart.

⚠️ Warning: If you copy guisettings.xml while Kodi is running, Kodi will overwrite it on exit.

For skin-specific settings, also backup the addon_data/skin.[name]/settings.xml file.

Does this method work on Kodi 22 “Piers”?

Yes. The guisettings.xml reset method works on all Kodi versions v17 and above, including Kodi 22 “Piers.”

Kodi 22 “Piers” is currently in Alpha/Pre-release stage. The stable version remains Kodi 21 “Omega.”

Why can’t I access the userdata folder on my Fire TV?

Fire OS has a sandbox system that restricts external access to app data folders.

Workarounds:

• Use Kodi’s built-in file manager — navigate to special://home/userdata/
• Use ADB (Android Debug Bridge) to access files
• Use a file manager app like X-plore with root/ADB permissions
• As a last resort, clear Kodi’s cache or reinstall the app

What’s the difference between deleting guisettings.xml and using the Settings menu?

• Settings → Interface → Skin: Resets only the skin selection (use when Kodi boots normally).
• Delete guisettings.xml: Resets all interface settings including language, audio, video, and skin (use when Kodi won’t boot or shows black screen).
• Delete skin settings.xml: Resets only the specific skin’s settings (use when skin is corrupted but Kodi boots).

How do I check if guisettings.xml is read-only?

On Windows:

1. Navigate to %APPDATA%\Kodi\userdata\
2. Right-click guisettings.xml → Properties
3. Look at the “Read-only” checkbox at the bottom

On Linux / macOS:

1. Open a terminal and navigate to the userdata folder.
2. Run: ls -l guisettings.xml
3. If permissions show -r--r--r-- (444), the file is read-only. Fix with: chmod 644 guisettings.xml

Can I prevent Kodi from ever resetting my skin again?

Yes, with these advanced measures:

• On Linux: Make guisettings.xml immutable after configuration: sudo chattr +i guisettings.xml
• Remove the immutable flag when you need to make changes: sudo chattr -i guisettings.xml
• Use the Skin Backup add-on from the official Kodi repository.
• Always exit Kodi properly — never force-close or unplug the device while Kodi is running.

Will resetting the skin delete my add-ons or media library?

No. Resetting the skin — whether through the Settings menu or by deleting guisettings.xml — only affects interface settings. Your add-ons, media library, and databases remain intact.

What should I do if none of these methods work?

If you’ve tried all methods and Kodi still won’t boot:

1. Check storage space — Kodi needs free space to write settings.
2. Verify file permissions — ensure guisettings.xml is not read-only.
3. Check the Kodi log file located in the userdata folder as kodi.log.
4. Reinstall Kodi as a last resort for a fresh start.

---

📚 Related Guides

• Install Kodi on Firestick — Complete setup guide for Amazon Fire TV devices
• Fix Common Kodi Problems — Troubleshooting guide for common Kodi errors
• Best Kodi Repositories — Trusted sources for Kodi add-ons
• Kodi Maintenance Addons — Keep your Kodi installation running smoothly
• Uninstall Kodi Addons — Complete guide to removing unwanted addons
• Change Customize Kodi Skin — Learn how to customize your Kodi interface
• Reset Kodi to Default Settings — Complete guide to factory resetting Kodi

---

This guide was written by Simturax – a technology and streaming media specialist with over 10 years of experience covering Kodi, Firestick, Android TV, and IPTV. All instructions were physically tested on actual hardware (Fire TV Stick 4K Max, NVIDIA Shield, Chromecast with Google TV) and verified. We prioritize accuracy, transparency, and user safety above all else.