The cable I got has a USB-A on both ends. While mine was I don’t know if it has to be USB 3.0. I only got the USB 3.0 one because I knew it would work still with USB 2.0 and it didn’t cost much more. Did your cable at least have USB-A on both ends? The initial connectivity iirc was a bit fiddly. Usually had to try the recovery mode sequence a few times before Windows and the Amlogic utility would recognize it.
Btw you shouldn’t need the cable to initially install CoreELEC. I only had to use it to restore to factory in order return a defective unit (bad Ethernet port). Or if I borked it badly.
my 2nd AM6b+ unit has the 0.5.4n preinstalled. I asked ugoos and they told me that’s it’s the same as original 0.5.4, but for newer device batches (probably ‘n’ stands for ;new’). Nothing was added/removed/fixed functionality-wise. Most likely they changed something on the board that required kernel/image tweaks or vendor module updates and FW recompilation. CE seems to work just fine from initial tests, but I wonder if anything is needed to be adjusted on CE side for the new revision…
from my amateur view I can tell you they are the same and no adjust is needed. at least for me. I have an older one and I put the complete backup on SD card to install it on the new box and it worked perfectly
great, thanks for the feedback. probably just something android-related need an update then. I will double check with Ugoos sometime later if they are willing to share the details of the change.
After Visionning Dolby Vision video, Coreelec stays in that mode until I reboot the device. Is there a way to force a return to normal mode and bring back the normal GUI colors. Using the UgoosAm6B+ with LG C6 oled TV and Marantz receiver.
If you are not using it currently, you should try cpm’s version (below) and set it to “On Demand” to see if this works for you. Besides potentially fixing this issue for you, cpm’s version also has fixes for the ATEME video files and the integration of the VS10 engine and injecting VSVDB block and HDR InfoFrame metadata.
I have an issue with Dolby Atmos/Dolby surround not being triggered (Soundbar connected via eARC). Out of all the MKVs I’ve tried, they all just play sound via PCM, and only ONE file triggered ‘Dolby Surround’ on my soundbar (and I can’t tell what’s different for that file from the others).
Can you tell me how to update it. Do i only need to copy your g12b_s922x_ugoos_am6b.dtb to my root and rename to dtb.img ? Or is there more file to copy ?
