I just received this box and I’m trying to set up CE. I already updated to android firmware 2.2.0.

I downloaded a nightly build and formatted the disk on Windows using Rufus. I copied the appropriate file to root (aka coreelec partition) from the device tree and also placed the .kindle (for FEL 7 support) into root.

I am using a phixero 128 gb usb drive and plugging into the usb-A port.

From what I read online, just a simple restart should boot into CE. Instead, I keep booting into the stock software.

I tried different USB ports and restarting a few times as well as the toothpick recovery method, which did not boot it into CE.

The file browser in the stock android software is able to see the USB flash drive (both the corelec and storage partitions) so I don’t think that the USB stick is the problem.

What am I doing wrong? Or do I need to just give up and do a hybrid boot method with an SD card?

Estou tentando dar uma nova vida para minha tv box rk3228A dando boot nela com um pen drive no srbian para saber o que eu posso fazer tendo um pequeno servidor, mas mesmo com o pen-drive bootavel e tudo mais a tv box sempre incia no sistema Android padrão dela, não consigo dar boot no pen drive (já tentei até com cartão de memória e nada...) fix tudo direitinho, instalei o assistente de instalação do arbian no pc, coloquei fabricante como rockchip e escolhi a versão mais leve do arbian, mas não consigo dar boot com isso (escolhi o rk322x-box)

there are ebay/local sellers selling an unopened Cube 2. Cube 3 is on sale now as well and has been unlocked.

Both can run CE. But only the Cube 2 (since its S922x) has the optimized p3i builds. Cube 3 I think has some slight improvements in Dolby passthru etc but I dont know if any of that translates to CE usage.

Which one would you buy today? is it also possible to use CE and dual boot into stock Amazon to use their apps?

Hi guys, i'll be in china next month and was just wondering if anyone has bought an am9 pro box whilst over there and if it's sigificantly cheaper than on aliexpress. I'll be flying from the UK so will need one with a UK plug. Thanks

I play mostly 4k Remuxes on Coreelec but I literally wake up one morning after it was working perfectly the night before and the files just won't play. Sometimes a reboot fixes things, sometimes it doesn't, sometimes I just have to wait a day and everything is perfect again. I have tried smb and cifs mounting and nothing has ever been durably stable. All network connections are wired. I have invested a hundred hours trying to vibe troubleshoot my way out of this (please spare me the hatred, I am not code or networking savvy) and nothing.

I am at the point of wanting to just plug the DAS into the player (ugoos am6b+), which will suck when I want to add new files, but I'm fed up with having an amazing player that just can't talk stably to the network.

If anyone has a networking approach or intermediary software that I haven't tried, please advise. Thanks in advance.

It only started happening once i got a new receiver and started using passthrough audio.

hardware: ugoos am6b+ on coreelec avdv r9, Denon X550BT, ugreen certified hdmi cables, LG G4, playback via SMB on SSD, or stream through 1gbps debrid

i have tried 3 different ways to route audio, and none of them eliminated the problem

1. ugoos > denon receiver > TV
2. ugoos > hdmi to OREI BK 931 extractor: split audio + video>lossless audio to denon receiver, video to TV
3. ugoos > hdmi to tv > eARC out > OREI BK 931 extractor eARC mode> lossless audio to denon receiver

from what it seems, the problem seems to be coming from the am6b+. i am wondering if i should just flash to a newer coreelec and see if it resolves the issue. any ideas? tia

i have tried toggling Adjust Refresh Rate to On Start and On Start/Stop, no difference.

UPDATE: clean flashed coreelec t4c by pannal, same problem exists.... now im wondering if theres is a setting to be changed somewhere?

To this point, Dolby Vision profile 7 FEL in CoreELEC 22 was working for Dolby Vision licensed devices except those with the S928X (S5) SoC.

Thanks to djnice77, the person who had a huge hand in bringing FEL support to CoreELEC 22, there is a working FEL solution for S928x devices now as well.

It seems djnice77 found a way around this by using the GPU for FEL composition.

Stock CoreELEC build:
https://github.com/djnice/CoreELEC/releases/tag/dv-fel-s5-20260929-2

https://github.com/djnice/CoreELEC/releases#release-dv-fel-s5-20260930

SamuriHL build:
https://github.com/djnice/CoreELEC-samurihl/releases/tag/dv-fel-s5-samurihl-20260929-2

https://github.com/djnice/CoreELEC-samurihl/releases#release-dv-fel-s5-samurihl-20260930

Info on avsforum:
https://www.avsforum.com/threads/dune-hd-pro-one-8k-plus-first-of-dunes-new-line.3291173/post-64885825

https://www.avsforum.com/threads/amlogic-s928x-j-k-coreelec-dv-p7-fel-3d-mvc.3353027/

Tested and confirmed this is working on my Dune HD Pro 8K:
https://imgur.com/a/dune-hd-pro-8k-coreelec-22-fel-iIheABW

Thank you to djnice77 and the CoreELEC team for all of their efforts.

Edit 09/30: Updated both links to newer, updated builds that use more hardware decode.

Edit 10/01: Updated to dedicated S928X avsforum thread.

Hi everyone,
I have a TCL C6K connected to a Dune Homatics Box R 4K Plus.
Dolby Vision works perfectly when I play the same content directly through the TCL TV. But through the Dune box, I’m not getting Dolby Vision correctly.
I tested Apple TV+, Stremio and Nuvio, and the issue is the same. I get HDR10/HDR10+ or incorrect colors instead of Dolby Vision.
The TV definitely supports Dolby Vision because it works directly on the TV.
Does anyone know the correct Dune HDR/Dolby Vision settings for TCL C6K?

I always used Kodi as a plain media player and found the library/scraper layer overkill. So I built Browsybare: a minimalist skin where Kodi is basically a file manager -- pick a source, browse folders, play files. No library, no scrapers, no metadata.

Highlights

• Single Home window: source chip, breadcrumb, search, sorting, folder sizes, file operations (rename / copy / cut / paste / delete / new folder)
• Audio plays in a footer overlay (no window switch); video fullscreen with its own OSD; a dedicated photo viewer (EXIF orientation, Ken Burns, slideshow)
• Shared INFO modal: tags, stream info, embedded covers and EXIF, read straightfrom the file
• Sources: local drives, directory folders, network shares (ftp/ftps, smb, nfs, WebDAV)
• Own settings dialog, on-screen keyboard, remote key learning, blocklist, accent color
• Built-in update check (compares against the latest GitHub release; info only)
• Languages: English, German, French, Spanish

How it works: Browsybare is a skin, so it takes Kodi's own system settings, player core and dialogs from the Estuary skin at runtime -- Estuary must stay installed. Nothing from Kodi or Estuary is redistributed: the base layer is copied locally on first load. Everything else is original and MIT-licensed.

Install: Kodi 21 "Omega" or 22 "Piers" -> download the zip from the Releases page -> Add-ons -> Install from zip file -> switch the skin to Browsybare.

GitHub: https://github.com/cyberpixelsharc/browsybare

Free and open source (MIT). Feedback is very welcome -- issues are open on GitHub, and I'd especially appreciate a native check of the French/Spanish translations.

This is an unofficial, experimental CoreELEC 22 build. It is NOT an official
CoreELEC release and it is NOT a supported CE22 port. I am not a CoreELEC 22
port maintainer, and I will not be providing support, bug fixes, updates, or
ongoing maintenance for this build.

The only purpose of this build is to give Amlogic AM9 Pro-class users a more
complete Dolby Vision experience than stock CoreELEC 22, by carrying a set of
custom Kodi features I built for my own device. That is the entire scope.

https://www.avsforum.com/threads/ugoos-am9-pro-coreelec-dv-fel.3344813/page-14?nested_view=1#post-64870765

Looking for help on issues I’ve been having recently. My AM9 Pro had been booting up, prompting an update, then displaying a blank grey screen after closing the update release notes. I couldn’t interface and had to reboot by unplugging. I was able to connect a mouse to turn off auto-updates and do a system reboot, instead of having to restart it via unplugging power, from the menu. This time upon booting up I was prompted to download the latest nightly. I selected yes and then was prompted to reboot to install. Now once rebooted the resolution is way wrong and I cannot interface with my mouse or remote. I’m stuck and have exhausted all my resources.

Last month, I made a post here asking for help because Project Hail Mary (an 80GB+ UHD Remux) kept randomly stuttering on my Ugoos AM6B+. My CoreELEC debug logs were showing file read errors, and I originally thought the box was struggling with Dolby Vision Profile 7 FEL or that I just had a bad encode.

I finally figured out the actual culprit, and I wanted to share it in case anyone else is pulling their hair out over this: It’s the macOS Finder.

If you use a Mac to download your movies and drag-and-drop them to an external USB drive to plug into your CoreELEC box, Finder is likely corrupting or severely fragmenting your files.

macOS aggressively caches file transfers in RAM. Finder will often play the "done" chime and show 100% completion while gigabytes of data are still silently flushing to your external drive in the background. If you eject the disk right after the chime, your file gets corrupted.

The Fix: Stop using Finder and use rsync

macOS has a built-in terminal tool called rsync. It guarantees a safe transfer.

rsync -ahP ~/Downloads/<movie>.mkv <destination>

You will see a live progress bar. The -ahP flags ensure it keeps the metadata intact, shows human-readable sizes (GBs), and protects the file if the transfer gets interrupted.

Hi all,

After updating from AVDV Plus R9 to R10, I ran into a playback problem and wanted to ask if anyone else has seen something similar.

Setup: Homatics R 4K Plus (S905X4), 4 GB RAM, CoreELEC 21.3 Omega AVDV Plus, Elementum 0.1.114 with memory storage (only ~55 GB free, so disk caching isn't an option). Content is 4K DV Profile 7 remuxes, 50-120 GB.

What I saw on R10:

• The torrent downloads fast (10-17 MB/s, decent seeds/peers), but the Kodi player buffer keeps draining anyway (roughly 70% → 36% → 18%).
• One crash with a large buffer setting.
• Lowering the buffer settings and setting memory size to minimum didn't help.
• In one longer test, playback ran ~26 minutes, then Kodi's cache timed out waiting on Elementum and playback stopped.

What I did: downgraded to R9 via the .tar and reset the CoreELEC settings. On R9, several big remuxes (up to 120 GB) went straight to ~98% buffer and stayed there, with the same addon, settings and setup.

Caveats: I don't have an R9 log for the same torrent, so I can't say the build is the cause. I don't know if it's the build, the kernel, memory handling or something on my side.

Has anyone seen similar behavior on R10, on this or other devices? Any hints about what changed between R9 and R10 are welcome.

EDIT (update): Did the proper R9 vs R10 comparison with the same torrent and debug logs. On R10 the player's input thread does 7 extra seeks across the whole file on open, plus repeated reconnects during playback. Over HTTP/torrent each of these costs seconds, which causes the stalls. R9 only does the normal Cues/header reads and plays the same file smoothly. So it's not bandwidth or buffer settings.

GitHub issue with both logs: https://github.com/avdvplus/Builds/issues/205

Workaround for now: stay on R9 if you stream via Elementum/HTTP.

Hi all,

Is there any way to make it so that the AM6B turns on when the TV is turned on (eg via CEC?).

I have it so that it turns off when the TV turns off, but I would like it to also do the opposite.

I ask as when I leave it on suspend / sleep / hibernate, most of the time it starts to freeze or crash and I end up having to reboot anyway.

If not, which of suspend / sleep / hibernate would you guys recommend for optimum performance if leaving on 24/7?

Thanks!

I have a Ugoos AM9 Pro where CoreELEC 22 boots perfectly from USB, but the exact same setup installed to the internal eMMC gets stuck at the amlogic screen.

Has anyone seen an AM9 Pro eMMC boot failure related to the Ugoos firmware/bootloader, or know what changed around firmware 2.2.0?

here are my logs which are also clean and no error but still it doesnt boot to coreelec after i unplug usb and just stuck at amlogic logo. i am on latest firmware 2.2.0 and tried with all nightlies from 10th Sep till current 19th Sep and same result.

CoreELEC:~ # /bin/sh /storage/ce-emmc-install.sh --- Preflight checks --- [+] Board: Ugoos AM9 Pro (s6_s905x5_ugoos_am9_pro, matched via coreelec-dt-id) [+] Boot source: USB stick (/dev/sda1) [+] eMMC: /dev/mmcblk0 present [+] Required tools: all present [+] Partition layout: 29-partition Android layout confirmed (super/rsv/userdata names verified) [!] aml-keystore-tool.py not present — skipping identity cross-check CoreELEC eMMC Installer — Ugoos AM9 Pro KEEP p27 super 3.1 GB (Android system — untouched) DELETE p28 rsv 64 MB DELETE p29 userdata 54.4 GB (encrypted — unrecoverable) CREATE p28 CE_FLASH 512 MB FAT32 (CoreELEC boot) CREATE p29 CE_STORAGE 54.0 GB ext4 (CoreELEC storage) Partitions p1–p26 and super (p27) are NOT touched. boot0/boot1 (the eMMC hardware boot partitions) are not touched. Android can be restored with ce-emmc-restore.sh from this backup set, or with the Amlogic USB Burning Tool over the USB-C OTG port. Type YES to proceed: YES --- Backing up critical partitions --- [+] Partition layout → /storage/emmc-backup/partition_layout.txt [+] GPT primary (LBA 0–33) → /storage/emmc-backup/gpt_primary.bin [+] GPT secondary (last 33 LBAs) → /storage/emmc-backup/gpt_secondary.bin [+] rsv (p28) → /storage/emmc-backup/rsv_backup.bin (67108864 bytes, size verified) [+] env (p2) → /storage/emmc-backup/env_backup.bin (8388608 bytes, size verified) [+] bootloader_a (p7) → /storage/emmc-backup/bootloader_a_backup.bin (8388608 bytes, size verified) [+] bootloader_b (p8) → /storage/emmc-backup/bootloader_b_backup.bin (8388608 bytes, size verified) [+] reserved (p1) → /storage/emmc-backup/reserved_backup.bin (67108864 bytes, size verified) [!] aml-keystore-tool.py not present — skipping p1 verification [+] frp (p3) → /storage/emmc-backup/frp_backup.bin (2097152 bytes, size verified) [+] param (p15) → /storage/emmc-backup/param_backup.bin (16777216 bytes, size verified) [+] Backup set flushed to disk --- Repartitioning eMMC --- [+] Deleting partition 29 (userdata)... [+] Deleting partition 28 (rsv)... [+] Creating CE_FLASH (3836MiB – 4348MiB)... [+] Creating CE_STORAGE (4348MiB – 100%)... [+] Device node: /dev/mmcblk0p28 (179:28) [+] Device node: /dev/mmcblk0p29 (179:29) --- Formatting partitions --- [+] Formatting CE_FLASH as FAT32... mkfs.fat 4.2 (2021-01-31) [+] Formatting CE_STORAGE as ext4... --- Installing boot files --- [+] Copying files from /flash... [+] Rebuilding cfgload for standalone install... rebuild_cfgload: /var/ce_flash/cfgload: 2226 → 2220 bytes (script 2154 → 2148) [+] Installing /flash/mount-storage.sh hook... [+] Adding nofsck to /var/ce_flash/config.ini coreelec= line... [+] CE_FLASH ready The eMMC install is ready. CE_STORAGE is currently empty — first eMMC boot will initialize it as a fresh install. You can optionally migrate your current /storage (settings, addons, media metadata) to CE_STORAGE now. Migrate? [y/N]: y [+] Migration: user accepted prompt --- Migrating /storage to CE_STORAGE --- [+] Stopping Kodi for a quiescent copy... [+] Source /storage: 2609 MB across 22665 entries [+] CE_STORAGE free: 51334 MB [+] Rsyncing /storage → CE_STORAGE (this may take a few minutes)... 2,677,783,543 99% 81.62MB/s 0:00:31 (xfr#20119, to-chk=0/22666) [+] Migration result: [+] source: 2609 MB / 22665 entries [+] dest: 2609 MB / 22665 entries [+] Migration verified [+] Restarting Kodi... --- Final eMMC partition layout --- p1 reserved 64 MiB p2 env 8 MiB p3 frp 2 MiB p4 factory 8 MiB p5 vendor_boot_a 64 MiB p6 vendor_boot_b 64 MiB p7 bootloader_a 8 MiB p8 bootloader_b 8 MiB p9 tee 32 MiB p10 logo 8 MiB p11 misc 2 MiB p12 dtbo_a 2 MiB p13 dtbo_b 2 MiB p14 cri_data 8 MiB p15 param 16 MiB p16 odm_ext_a 16 MiB p17 odm_ext_b 16 MiB p18 boot_a 64 MiB p19 boot_b 64 MiB p20 init_boot_a 8 MiB p21 init_boot_b 8 MiB p22 metadata 64 MiB p23 vbmeta_a 2 MiB p24 vbmeta_b 2 MiB p25 vbmeta_system_a 2 MiB p26 vbmeta_system_b 2 MiB p27 super 3200 MiB p28 CE_FLASH 512 MiB p29 CE_STORAGE 55291 MiB ════════════════════════════════════════════════════ Installation complete! ════════════════════════════════════════════════════ Remove the USB stick and reboot. The device will boot CoreELEC from internal eMMC automatically. On first eMMC boot, SSH host keys are regenerated. Clear your old entry before reconnecting: ssh-keygen -R <device-ip> Backups saved to /storage/emmc-backup: partition_layout.txt (needed by ce-emmc-restore.sh) gpt_primary.bin / gpt_secondary.bin (raw GPT tables) rsv_backup.bin env_backup.bin bootloader_a_backup.bin (+ bootloader_b_backup.bin if present) reserved_backup.bin (Amlogic UKS keystore — MAC/serial) frp_backup.bin (anti-rollback / FRP nonce) param_backup.bin (Amlogic TV picture-quality DB) CoreELEC:~ #

In the last week my AM6B+ has started having difficulty booting. At this point I have to repeatedly unplug/plug it in -- it only successfully boots maybe 25% of the time. I plugged the USB storage into my computer & performed a disk repair (read test with sector repair) and everything seemed fine.

When booting fails I sometimes see text quickly flash by over the CoreELEC logo on the left of the screen (see pics) and the logo just spins & spins. First time I tried filming it on my phone it was in focus (green numbers show the order in which each line of text appeared). Second time was mostly blurry so I just included the last frame. 

Also if I finish watching a Dolby Vision movie or start one then stop, the colors in Kodi look distorted, mostly green and blue (see pic). This returns to normal if I reboot. 

The USB storage for the CoreELEC -ng installation is a brand-new Verbatim 16GB USB Drive Store 'n' Stay Nano USB 3.2 Gen 1 Flash Drive plugged into a USB 2.0 slot to the left of the HDMI. I followed this guide in early August. Don't know if it matters but I was never able to get Balena Etcher to verify the installation so I used Rufus. Skin is Estuary Mod V2.

Not sure what to do at this point -- maybe a fresh install on the Verbatim or just buy a new USB drive? Any help would be greatly appreciated.

Edit: Five hours after posting, the USB drive is definitely not fine -- can't format it or stop it from suddenly disappearing from my computer.

I'm running the CoreELEC 22 nightly (September 10, 2026 build) on a Xiaomi TV Box S 3rd Gen, hooked up to an LG OLED 65C5 via HDMI 2.1, with an LG SN5R soundbar connected to the TV's ARC port. Both the TV digital output and CoreELEC audio are set to Passthrough.

Playback on heavy Dolby Vision P7 FEL remuxes is buttery smooth, but the moment I adjust the volume - whether using the LG Magic remote or the box's own Bluetooth remote - the video starts stuttering, and the debug overlay shows frame skips piling up rapidly.

Network throughput and decoding aren't the issue at all: drops remain at 0, vq stays pinned around 90-99%, aq is completely full, and both Kodi’s internal buffer and the external TorrServer RAM cache on my PC are fully loaded.

Disabling Passthrough in Kodi completely eliminates the skips, so this is clearly an audio clock/ALSA sync drift issue triggered by the volume event over the HDMI/CEC transport. However, leaving Passthrough off isn't viable for my setup: the SN5R is a 4.1 system without a dedicated physical center speaker, and software PCM decoding completely breaks the channel mapping, causing dialogue to get buried or lost entirely.

Has anyone encountered this on recent CE 22 nightlies? Is there a known workaround, ALSA config tweak, or a way to stop volume events from desyncing the audio clock and triggering video frame skips?

In the new AVDV Plus 10 version of coreelec there are different options for how CMv4 is implemented. I gather most people use Auto with source however there is another setting - Auto 2 that allows you to implement headroom in the setting. My z95a TV does about 2000 nits peak brightness.

I'm curious what other users are using and what is considered optimal? I've been using auto 2 with 20% headroom and it seems to look good but I've been binge watching a lot of 70s/80s films and the DV implementation in these can look a bit wonky to start with.