nobitakun

Well, I've been tinkering with different dtb's and Armbian versions, matching kernel 4.4 and using H96 Max RK3399 dtb as well, but the device does nothing. In fact, I entered the recovery to see if the SD card could be read and it didn't mount, then turned the device off through the button and now it does not turn on anymore. The red light does not go blue, I can still enter maskrom but if I want to boot Android normaly the device does nothing. I am kind of tired with this crappy TV box, wasting 2 days it's not worth it for something that costed 15€. My time is more valuable. Thank you for the help anyways.

The dtb files I've tried for rk3399 do not work, I've read that Firefly-RK3399 is very similar to this board, but even so it does not start. The small Rockchip chip is very difficult to see through a picture, at least with my phone camera. I tried with this picture: Anyways, I can write it here: RK808-D FAD7P841 1703

I attached some pictures of the device inside, I don't know if they can be of any help. I tried to use te dtb extracted from Android with the Armbian for Firefly-RK3399 and it does not boot. I configure the extlinux.conf file as advised, but the same moment I insert the SD card and turn on the device, the red light never turns blue. I tried that board because I've read in some forum that is similar to this device, but I know that's kind of hit and miss. At least I expected to see something on screen, even if it threw tons of errors, because I assume the dtb file is not the problem so the issue should be somewhere else that needs to be modified. Much appreciated for the help

Finally, I've extracted the dtb file corresponding to the device, from Android. It is for kernel 4.4.16, so I believe it can be done something with it in order to boot Armbian. At least is a beginning

ohh I see. Anyways I can't seem to make it detectable by the Windows RKDevTool, I turn the maskrom mode correctly but then all of the commands fail. It really sucks to have a device this powerful and not being able to do anything because of those crappy dtb files. Thank you anyways!

I have the same Android TV, and I've been trying to boot Armbian but I don't seem to successfully accomplish it. I believe we are all alone with this, and nobody will ever help us. Maybe RK3399 SoC is still problematic after 9 years.

Ok, thank you for the answer. I will have to use a headless distro compatible with secure boot then. Cheers!

Hello, I am trying to install Armbian UEFI-x86 into this very small mini PC, but with secure boot enabled it only shows this screen: Disabling the secure boot isn't an option, because every time I turn it off and then turn it on the next morning, the BIOS settings are being reset, then the secure boot is enabled once again (I believe it is intentional, because the CMOS battery only keeps the clock & date). Moreover, I want to use it as a headless computer, so no keyboard will be attached. Is this fixable or Armbian isn't compatible with secure boot? Thanks in advance.