NightMean

  • Content Count

    4
  • Joined

  • Last visited

  1. It depends which box you have, I have two same looking boxes however they both have different CPU, one is S905X and the other is S905 You need to open your box and look at it. For S905 I had luck with meson-gxbb-vega-s95-meta.dtb (Bluetooth doesn't seem to work on any dtb) and for S905X it was meson-gxl-s905x-khadas-vim.dtb or meson-gxl-s905x-p212.dtb. Both worked fine but the screen resolution wasn't FHD out of the box, desktop took forever to load, and Bluetooth wasn't working on any dtb as on S905.
  2. It's not dead, you just don't have the correct dtb. For me it was trial and error until I figured out which worked the best. I don't have your box though. I have 2 identically looking boxes from the outside but the internals were different.In my opinion It's best to open it and see what the CPU is.
  3. if by multi-boot you mean holding the reset button so the box will boot from USB/SD Card then I was doing that as by default it boots to android. I've information about the aml_autoscript.zip but from my understanding it will do the same thing as when I'd hold the reset button won't it?
  4. Hey I'm pretty new to this community. I have Mini M8S II which is running libreelec just fine with the stock dtb. I want to turn it into a small server with armbian but it always fails to boot. The box apparently has S905X which should "translate" into this dtb gxl_p212_2g_kvim.dtb. Libreelec refuses to boot with it but when I used older built of Coreelec it booted with gxbb_p200_1G_1Gbit.dtb which should be S905 not S905X. Armbian and libreelec refuses to boot with that dtb. I've tried most of the included dtb even putting them to main directory and renaming them as dtb.img (Yes I've read