Mine bricked itself on Android14 upgrade, I had to manually reflash firmware image.
Now with v14.8.7475 it’s not booting Coreelec anymore, already tried 3 different USB sticks, the reboot to corellec app, usb host disabled, long press reset etc. always ends in a boot loop with homematics logo ?
edit: latest 22.0 works
Can you give me a link to the version you wrote? It’s fine: “edit: the latest 22.0 works”, thanks.
Latest 22.0 here
Hi, how did you managed to unbrick it? I tried several howtos, but without any success?
Did you try unbricking using the AML Burning Tool?
thanks, I’ll try it
Thank you for the files my friend, I also got a black screen on all Doby Vision formats after the Android 14 update and after the CoreElec automatically updated to version 21.3, a black screen kept appearing and now after I put one of your files, the larger size which is 1.29 megabytes, the Dolby Vision movies worked again, including profile 7 (fel).
It still doesn’t work for me, I can start CoreELEC but when I close it it won’t start.
What file did you use exactly?
Device & environment
Symptoms
Every time I try to boot CoreELEC, the box lands in the Android recovery menu instead of booting CoreELEC. From recovery, selecting “Apply update from udisk” returns “No command” (expected — CoreELEC is not an Android OTA package). The box never reaches the CoreELEC boot screen at all.
What I have already tried
Question
I have seen post #6264 where a user confirms that CoreELEC 22.0 works on v14.8.7475, but no details were given on how they made it work. Could anyone on the same firmware version share exactly what image, DTB, and boot method worked for them? Any help is greatly appreciated!
Hi there!
I set up an installation exactly like yours this morning, and it worked without any issues, using the USB-A 2.0 port on the box because it didn’t work on the USB-A 3.0.
Could you post a photo/screenshot of what’s at the root of your USB drive?
Normally, in the event of a boot failure, it doesn’t go to Recovery but to the Android TV interface…
Mine :
Do you have the option of trying with a different flashing tool? If you were on Windows, I would have advised Rufus, but maybe there’s a tool other than Balena for MacOS too?
Here’s my usb key after trying to launch coreeelec.
This time i formated the key with windows then I used rufus instead of Balena to create the bootable key. (using a VM) I tried the UBS2.0 but i’m still having the homatics image and then the recovery menu.
By the way, the key is readable on the box, I instlled TV file commander to check it. I tried to boot with the manual approach (reset button) and the reboot to libreelec app. nothing seems to be functionnal…
By the way i used the dtb.img = sc2_s905x4_sei_smb_280
I don’t know how to post an image. Eveytime I copy paste or try to uplaod, I have an error message : An error occurred: Sorry, you can’t embed media items in a post.
At worst, you can upload your image here and copy and paste the link afterwards: https://imgbox.com/
You need to have the same files as me at the root of the USB drive.
And you have the same dtb as me, so the problem isn’t there 
Without a USB drive, it boots well on Android TV but not in Recovery? Just to make sure your box isn’t bricked ^^
I only have a PC with Windows, not a Mac.
Ideally, it would be best to do it from a Windows PC to ensure everything is fine; I’m not sure if it would work properly through virtualization.
Here are the different steps I would follow:
- download the latest available nightly of CoreElec NO for PC, generic version: CoreELEC nightly builds
- do not decompress the archive, it should be placed as is on the balenaetcher or rufus program.
- burn the file onto the USB drive using BalenaEtcher or Rufus.
- once the files are on the USB drive, you need to remove it from the PC and then reconnect it to see the available content on the drive.
- check that the format of the USB drive is FAT (only a small partition of the drive will be in this format, do not touch the rest of the drive, the remaining part will be formatted by CoreElec into Linux Ext4 partitions)
- make a copy of the dtb file present in the device tree folder: sc2_s905x4_sei_smb_280.dtb
- be sure to display the extensions so that “.dtb” is visible.
- paste this file at the root of the USB drive and rename it to dtb.img, so the extension must be changed. If you do not display the extension, you might end up naming it dtb.img.dtb, which is incorrect.
- (optional) if you have a Dolby Vision compatible TV and you have content in that format, you can also add this file (5.15_2.6_dovi_patched.ko) to the root of the USB drive: FEL - Amlogic NO support
- you need to rename it to “dovi.ko,” also ensuring that the extension is clearly visible.
- safely disconnect the USB drive.
- unplug the power cord from the Homatics.
- insert your USB drive into the USB-A 2.0 port
- press the reset button with a small tool while simultaneously reconnecting the power cable
- you should see the fastboot message appear, followed shortly by the message “USB burning mode.” It is only at this moment that you can release the reset button
- if all the files have been successfully copied to the drive and the box isn’t bricked, it should start up
here I am for the image 
I followed every steps you did, but it seems when I arrive on USB Burning, nothing appears. I don’t understand, I tried with 2 usb keys, I’m on port USB 2.0, I enable ADB stuff on android, I boot without any pb on android, but anyway, I didn’t get the solution..
I followed every steps : fat32, burn with rufus on windows, change and remove dtb by the correct mone, and rename as dtb.img (and sure it is not dtb.img.dtb) push the key on usb 2.0. remove the electricty cord, push the reset, until usb burn in appears… and I go back to Android recovery menu…
It works! i took the wrong version.. Altlas instead of generic, i retried everything you said and… I’m on it. many many many many thanks for your precious support.
Cool, that’s great because I was stuck there 
Yet in your first message, you mentioned that you had chosen the Generic version ^^
Have fun! 
Yes I did on mac but on windows I took the first one and I was wrong. sorry. my only trouble now, is to start the box with the remote. I appaired tthe remote on coreelec, and I can navigate, but when I close the application and poweroff, I can’t power on… I don’t know how to proceed, I have to disconnect the wire, and reconnect it to launch the box, and that’s not so accurate. It seems, each rebbot I have to reconnect the bluetooth remote to kodi… weird
You can’t turn on the device with the Bluetooth remote if the device is completely off. This can only be done via IR. The Homatic doesn’t have an IR receiver; you have to solder one. You can also use CEC – set the remote button (on Android) to turn on the TV via IR.
Yes exactly, @adWroc is right
No IR with Homatics R 4k Plus.
But these clones have it: Rocktek G2, Dune HD R4k Plus, Nokia 8010.
It is indeed possible to wake up the box using the source button on the remote control or CEC.
Or solder an infrared module onto the motherboard…
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
