Hi All
i have “Dune HD Sky 4K” CPU is : S905D + DVB S2 + CI+ Ram 2gb + Flash memory 16 GB + 1000M network …
more info here : http://dune-hd.com/eng/products/full_hd_media_players/56
i try build core but not boot to CoreELEC … i have black screen
here dtb in firmware android 6.0.1
https://dune-hd.com/firmware/sky4kplus/
Which DTB did you use when trying to boot?
p231 2g dvb
Did you follow install instructions correctly and rename the file to dtb.img and move it to the root of your sd/usb?
After use tool LibreeELEC …
i copy file dtb from folder tree to root sd and rename it to “dtb.img”
Have you tried the other dtb’s?
Please provide a copy of the original DTB from your device, this can be obtained in Android using dd if=/dev/dtb > /sdcard/dtb.img.
Dune locked the bootloader.
result info “cat /proc/device-tree/amlogic-dt-id” :
gxl_sx6b7x_2gu0_a49
Try this dtb gxl_p230_dune_sky.zip (10.6 KB)
Unfortunately
not boot
Today I tried the new version (CoreELEC-Amlogic-ng.arm-19.4-Matrix-Generic.img), & gxl_p230_k1_pro dtb for Dune HD Sky 4K
and surprisingly, the system booted successfully
DVB (Availink avl6862 but not found channel) & Lan & Wifi & BT = WORKING
only remote not working …
CoreELEC:~ # dmesg | grep dvb
[ 3.681463@0]- kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.crazycat.conf
[ 3.729926@2]- kernel-overlays-setup: added modules from /storage/.kodi/addons/driver.dvb.crazycat//kernel-overlay/lib/modules/4.9.269
[ 3.730122@2]- kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[ 3.768543@1]- kernel-overlays-setup: added modules from /storage/.kodi/addons/driver.dvb.dvb-latest//kernel-overlay/lib/modules/4.9.269
[ 10.379728@2]- dvb_meson dvb: Found i2c-1 adapter: Meson I2C adapter
[ 10.379738@2]- dvb_meson dvb: ts0: parallel
[ 10.380024@2]- dvb_meson dvb: ts0_control: 0x0
[ 10.380134@2]- dvb_meson dvb: dev_name=dvb
[ 11.595648@0]- dvb_meson dvb: DVB demod detection for i2c-1 (Meson I2C adapter)…
[ 12.811471@3]- dvb_meson dvb: Checking for Availink AVL6862 DVB-S2/T2/C demod …
[ 12.812193@1]- i2c i2c-1: dvb_meson: found AVL6862 family_id=0x68624955
[ 22.642216@0]- i2c i2c-1: dvb_meson: Rafael R912 successfully attached!
[ 22.642227@0]- dvb_meson dvb: Total DVB modules found: 1
[ 22.646381@0]- dvbdev: DVB: registering new adapter (dvb_meson)
[ 22.660392@2]- dvb_meson dvb: DVB: registering adapter 0 frontend 0 (Availink avl6862)…
[ 22.748201@1]- dvb_meson dvb: DVB: adapter 0 frontend 0 frequency 0 out of range (175000000…2150000000)
[ 27.402701@0]- i2c i2c-1: dvb_meson: failed to enter DVBSx mode
[ 47.388261@0]- i2c i2c-1: dvb_meson: failed to enter DVBSx mode
CoreELEC:~ #
Hi Zuma,
I’m really sorry to bother you, but I truly hope you might be able to help me.
I saw your post about successfully booting CoreELEC on the Dune HD Sky 4K, and it honestly gave me some hope. Unfortunately, my Dune HD Sky 4K Plus (S905D) is now completely bricked — the eMMC has been wiped, there is no system, no recovery, and I can’t boot anything at all.
I’ve been trying for quite a long time to reproduce what you did. I used CoreELEC 19.4 and the gxl_p230_k1_pro dtb (and also tried several other DTBs), but I only get a black screen with no signal. I also tried different USB drives and boot methods, but nothing works.
I feel a bit stuck and honestly a bit desperate at this point… so I wanted to kindly ask if you could share more details about your successful setup.
If possible, could you please let me know:
The exact DTB file you used (was it really p230 or something else like p231?)
Whether you modified the DTB or boot files in any way
The exact steps you followed to boot into CoreELEC (from power-off to system boot)
How you triggered the boot (toothpick method, aml_autoscript, etc.)
If there were any special tricks or important details I might be missing
Also, since my eMMC is completely empty now, I’m wondering:
Were you able to boot CoreELEC without any system on eMMC?
Do you know if there is any working Android firmware (.img) available for this device that can be flashed via USB Burning Tool?
Even a small hint from you could make a huge difference for me. I would be extremely grateful for any help or guidance you can offer.
Thank you so much for your time, and sorry again for reaching out like this.
You need to Google about USB burn tool or burn card tool how to recover bricked Amlogic device.
p230 also i try KI Pro and working
for boot must use sdcard slot, not usb port
send command (reboot update) via ssh android
i think you need install system android again
1- copy dune_firmware_tv274a_240619_0210_r22.dff on usb via fat32 format Dune Firmware Zone / Dune HD Sky 4K Plus
2- unplug power
3- connect usb
4- plug power & press (Reset)
5- if not start go to recovey and select “Apply update from USB”
6- it not have recovery you can try Amlogic USB Burning Tool
Hi Zuma,
Thank you so much for your response, and I appreciate the details you shared. However, I wanted to clarify that my situation is a bit more complicated: my eMMC is completely wiped, and I’m unable to boot into Android or CoreELEC at all. Because of this, I cannot use the recovery process you suggested (via USB) or SSH to trigger the system. I also can’t use the DFF file to restore the system since the eMMC is empty, and unfortunately, the official support team is unable to provide low-level recovery firmware.
Given that, I was wondering if there is a way you could assist me by creating a backup of the eMMC contents directly via SSH (using dd or a similar method). Once I have the raw eMMC image, I can try to restore it myself using the Amlogic USB Burning Tool or other methods.
If you’re able to help with this, it would be greatly appreciated. I understand it might be a bit more involved, but I believe this could be a viable solution for me.
Thank you again for your time and help!
Use USB burning tool and Android IMG to recover.
Or make µSD with CE image and burn Android bootloader on the µSD afterwards.
Or move to round bin.
Hi Portisch and CoreELEC Team,
Thank you for your response and the suggestions.
However, I’d like to clarify my situation further, as it seems there is a misunderstanding. My Dune HD Sky 4K Plus (S905D) device has had its eMMC completely wiped, and unfortunately, I cannot use the Amlogic USB Burning Tool or other Android firmware to recover the system. I have already contacted official support, and they confirmed that they are unable to provide low-level recovery firmware or service tools.
I understand the general recovery methods you mentioned, such as using the USB burning tool and Android IMG, or creating a µSD card with CoreELEC and burning the Android bootloader afterward. However, none of these methods work in my case because:
The eMMC is wiped – no bootloader or system is present, so I cannot use recovery.
The USB method does not work – the system does not boot from USB, even when using the recovery key.
CoreELEC recovery doesn’t trigger – I cannot get the system to start, even when attempting to use the recovery button or other methods.
Given these constraints, the usual methods you suggested are unfortunately not applicable. Would it be possible for you to assist in a different way, such as helping me extract the raw eMMC image via SSH, so that I can attempt to restore it manually?
I understand this is an unusual request, but I believe this may be the only viable way forward, and I would greatly appreciate your assistance in this matter.
Thank you once again for your time and support.
And what do you expect now?
It´s no CE issue and You are searching for support in the wrong forum.
No, if the eMMC is wiped, there is no way to extract anything via SSH.
It was a big fault wiping the eMMC
Extracting firmware file dune_firmware_tv274a_240619_0210_r22.dff gives you some maybe useful files.
drwxr-xr-x 3 pvic pvic 4096 Apr 23 14:26 META-INF/
-rw-r--r-- 1 pvic pvic 9562624 Dec 8 2017 boot.img
-rw-r--r-- 1 pvic pvic 1163776 Dec 8 2017 bootloader.img
-rw-r--r-- 1 pvic pvic 88064 Dec 8 2017 dtb.img
-rw-r--r-- 1 pvic pvic 18858 Dec 8 2017 file_contexts
-rw-r--r-- 1 pvic pvic 930208 Dec 8 2017 logo.img
-rw-r--r-- 1 pvic pvic 12489216 Dec 8 2017 recovery.img
-rw-r--r-- 1 pvic pvic 738897920 Dec 8 2017 system.new.dat
-rw-r--r-- 1 pvic pvic 0 Dec 8 2017 system.patch.dat
-rw-r--r-- 1 pvic pvic 686 Dec 8 2017 system.transfer.list
Maybe flashing just the bootloader bootloader.img using USB Burning Tool or fastboot would be enough to start booting from USB or uSD and update with dff file. Or maybe boot CE.
File system.img can also be created
# get sdat2img
wget https://raw.githubusercontent.com/xpirt/sdat2img/master/sdat2img.py
# convert
python3 sdat2img.py system.transfer.list system.new.dat system.img
Seems also update.img can be created.
Did you tried LibreELEC on uSD card?
To boot from uSD search for generic S905D U-Boot for SD card.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice