Can be issues when downgrade from 5.15 to NG 21.xxx
Try clean install with formated SD Card/USB Thumb Drive
Place dovi.ko in root of ,same place you rename DTB to dtb.img
Hello, I’ve just received a Kinhank G1 SN starts with 255. I know it is not officially supported, but there are DTBs, and if I succeed opening the bootloader it should be fine.
I’ve already looked at the topic: Kinhank G1 (Start Guide)
Is the ROM currently flashed (including dovi.ko) interesting in any way?
Which Coreelec is recommended for Dolby Vision support and stable use? NG or NE or NO?
If you are success with bootloader
G1 can be used on all 3 branches with Dolby Vision Support, Stable/Nightly does not matter.
If you want FEL PROFILE 7 ,then you will want to use the NG branch 4.9 kernel
Rom currently flased ,interesting???
Do not understand this ??
Good Luck
Happy Testing
Thank you.
I do not know if this box came with Android TV 11 or Android TV 14 flashed in the factory. I also don’t know which kernel versions are under ATV11 or ATV14, hence the dovi.ko that is in the flash may be good only for one version.
There is no “dovi.ko” in the flash partition, nor is it part of any image; you have to put it there yourself. For different CE versions (NG, NE, NO) you have to copy to flash partition different dovi.ko versions.
Hello,
Struggling with the bootloader, there were many failed attempts like this:
sdc_update bootloader bootloader.img
Device: sd
Manufacturer ID: 1b
OEM: 534d
Name: 00000
Bus Speed: 50000000
Mode : SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 7.5 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
[MSG]filesize 0x3ffe00
[MSG]startclust 0x3
[MSG]Down(store) part(bootloader) sz(0x3ffe00) fmt(normal)
[MSG]totalSlotNum = 0, nextWriteBackSlot 64
[MSG]filesize 0x3ffe00
[MSG]startclust 0x3
[MSG]Burn Start...
[MSG][bootloader] CpyNum 3, bootCpySz 0x400000
[MSG]ty 0, en 0
00
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
*** ERROR: Can't read MBR header ***
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
*** ERROR: Can't read MBR header ***
gpt is invalid
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
*** ERROR: Can't read MBR header ***
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x1ff2800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
*** ERROR: Can't read MBR header ***
gpt is invalid
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
emmc: resp timeout, cmd16, status=0x100a800
storage write bootloader failed
00
emmc: resp timeout, cmd6, status=0x100a800
emmc: resp timeout, cmd6, status=0x100a800
emmc: resp timeout, cmd6, status=0x100a800
00
emmc: resp timeout, cmd6, status=0x100a800
emmc: resp timeout, cmd6, status=0x100a800
emmc: resp timeout, cmd6, status=0x100a800
[MSG]Burn complete
BURN bootloader.img to part bootloader OK!
And there was one that seemed to succeed:
sc2_ah212# sdc_update bootloader bootloader.img
Device: sd
Manufacturer ID: 1b
OEM: 534d
Name: 00000
Bus Speed: 50000000
Mode : SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 7.5 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
[MSG]filesize 0x3ffe00
[MSG]startclust 0x3
[MSG]Down(store) part(bootloader) sz(0x3ffe00) fmt(normal)
[MSG]totalSlotNum = 0, nextWriteBackSlot 64
[MSG]filesize 0x3ffe00
[MSG]startclust 0x3
[MSG]Burn Start...
[MSG][bootloader] CpyNum 3, bootCpySz 0x400000
[MSG]ty 0, en 0
00
[MSG]skip not EN cpy0
00
boot_info.rsv_base_addr: 12000
boot_info.ddr.addr:4000
boot_info.ddr.size:0008
boot info: parts 0
boot_info.version:0001
boot_info.checksum:16009
00
boot_info.rsv_base_addr: 12000
boot_info.ddr.addr:4000
boot_info.ddr.size:0008
boot info: parts 0
boot_info.version:0001
boot_info.checksum:16009
[MSG]Burn complete
BURN bootloader.img to part bootloader OK!
=====>Burn part bootloader in fmt normal OK<======
But at the top it says Device: sd and not Device: mmc
Since then, I get only Make your life colorful screen.
I haven’t tried to flash the full firmware, because I don’t yet have an usb a-a cable, but we may create one. I don’t know if data+ and data- must be swapped for that?
I’ve read that this bootloader in itself is not enough to boot coreelec from sd-card.
Success!!! We made an USB A-A cable, flashed hungputho custom firmware, and now I can boot Coreelec!!!
I am sorry Kinhank G1 is not supported, and I understand why. I would have bought another brand if there was one at similar price, but there is none.
So far stayed on NG 21.2, as the previous box had an SD-card configured with all the sources, hyperion-ng, etc. I replaced the dtb, and added dovi.ko. So far, it works. We will test it tonight. I have Rev-D, so I will have the white dots on interlaced material problem, I’ve read about it.
Thank all of you very much for making this possible, and who helped me!
Hi, does anyone have a 1Gbit link speed Ethernet(with old rev box) and WiFi working in CE-NO?
Thanks, yes, now able to get 1Gbit Ethernet, and BT works after applying those changes to the dtb.
Hi all, I use an old rev box and I never had stable WiFi connection on this thing with CE-ng, so I resorted to using Ethernet. The issue with WiFi was that the wlan0 adapter would go down after some time(varies between a few mins to a couple of hours, pretty random) of using the box for playback or downloading add-ons, etc. If it goes down during playback, the box gets locked up completely sometimes and need to unplug the power cord.
But I need to move this to a different location now and I can’t connect it to Ethernet there. Can I use a USB dual band WiFi adapter in that case? Would it be a plug and play situation or do I need to worry about the drivers again? Any advice is appreciated.
The issue is reproducible by running iperf and WiFi gets stopped everytime that happens. If anyone is interested, here is the dmesg | grep dhd log: https://paste.coreelec.org/FamilyCastor
dmesg always ends with the same error each time.
Hello,
I have a new rev Kinhank G1. It worked nicely since the installation a few weeks ago.
Last night it surprised me with a filesystem corruption detected message, I let it do the fsck. I use linux, so I know this usually takes only a few seconds. Here, I let it run, and it displayed alot of numbers, after a few minutes I put back our old X96 box, and let the Kinhank do it’s fsck.
After watching two episodes, I checked the Kinhank G1, and it surely finished the fsck, and welcomed me to the new installation of Corelec, meaning it most likely lost everything from the sdcard, and started new.
The most likely reason for this is that I may have turned the Kinhank G1 off too soon, while it was still writing to the SD Card. The Kinhank G1 has multiple LEDs, but on the front I see only a blue one come on, when I apply power, and that stays on even after I shut down Coreelec, so the only things indicating it is progressing with the shutdown is the hyperion NG lights getting turned off, and the Ethernet link led getting turned off.
I never had such a filesystem corruption with Coreelec before, on the X96 box when the VFD was turned off I knew I can turn off power a few seconds later.
So, how do you deal with this? When is it safe to turn power off?
I’ll check also the backup options.
On my G1 the blue LED turns to red when it’s safe to turn it off. Otherwise, it’s also safe to turn it off when it stops sending HDMI signal to TV.
My is ready to turn off sometimes within 5 sec. and sometimes it takes about 30 seconds…
I never turn off any of my media boxes now as I have had issues on a few brands with on/off actions in the past…
Iam fortunate that my G1 works great/isin sync with CeC default settings in CoreELEC
And TCL Dolby Vision TV
Power down TV/ G1 powers down/yes usb ports also.
Power on TV G1 fires right up
Thank you all for the comments. My box is a new rev 100Mbps LAN, Rev D. SOC, and it seems it acts differently than Sholander’s box, the blue led always stays on. I now check the red or orange LED at the LAN port, which goes off after a few seconds after shutdown. Then I wait a minute or two before turning off power. This worked so far.
Yep this is like girfriend when we let them cool down, then it’s complicated lol
I use an original Kinhank G1 remote control. Every time after boot I have to long press back + home buttons to get my remote working via BT. Before that I see “Connected: No” in Bluetooth settings. How to fix this?
Go to first post ,and download the Homatics R 4K Plus infra red remote conf, is same as G10 Kinhank.
For Bluetooth follow the other link and make sure you have 10-ur01 .hwdb file ,if you haven’t already done this.
I mostly use the ir remote config for thus G10 remote, also on other boxes when using same G10