Help needed to identify this Android box

[minorj]

Hi all. I have this Android box called X96, its back labels says RAM 2G and ROM 16G, but as you can see from the pictures CPU-Z shows completely differents specs.

So I was wondering if you can help me to identify the correct model of this Android box and also the correct version of CoreELEC to install (if any).

Link to images: Imgur: The magic of the Internet

Thanks.

[rho-bot]

Looks very fishy… These X96 boxes are well known for fakes. According CPU-Z 1G/4G box.
Checkout also results from AIDA64 and this thread:

Coreelec does not boot in X96 mini

I am running into a second problem. I installed Coreelec successfully on a x96 mini 6 weeks ago. All is working fine. I tried to duplicate the same things with a new x96 mini which I bought recently. Same model. I downloded the recent image onto a USB stick, changed the and tried the toothpick method (like last time) Now all what i get is this [80dd6e4f9bfc1adfd369c8d6f268cf2d90819269] What am I doing wrong? How can I fix this? Thx for your help

[minorj]

Thanks for the AIDA suggestion. Here is some more infos from it:

It currently has atvX intalled. Is there any compatible CE build?

[rho-bot]

Looks like S905W (GXL) with 1GB RAM / 4GB EMMC
You could try CoreELEC-Amlogic-ng.arm-9.2.7 with device_tree
gxl_p281_1g.dtb or gxl_p281_1g_a95xr2.dtb

[minorj]

Thanks, I’ve just tried the 9.2.7 version and the 19.1-Matrix_rc4 too, both using the gxl_p281_1g.dtb

They both seem to work fine. The only problem is that neither of them detects the internal bluetooth. I think I’ll open a different topic for that.

Anyway thanks again!

[Portisch]

Looking for users with no working WiFi or BT

We are looking for users who have devices that doesn’t have working WiFi or BT so we can continue to improve CoreELEC support for all devices. If you have any of the following devices then please do not reply as we are unable to support these devices due to no driver being available. Mecool K1 Plus (S905D) (9028xs) Tanix TX3 Mini (S905W) (9028xs) T95N (S905X) (9082xs) If you have issues with INTERNAL WiFi or BT then please also SSH to your device and enter the following command and paste the…

[minorj]

Thank you for the suggestion, but I think I made myself look like a fool. Even if a boot back to the Android OS the bluetooth doesn’t work for a simple reason: it doesn’t have a bluetooth chip… I guess.

To confirm this, I ran lsusb and it outputted nothing more than:

CoreELEC:~ # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I guess if there had been a bluetooth chip (even not properly configured) it would have appeared on this list, am I right?

[Portisch]

Useless…
And what is about udevadm?

[minorj]

Here it is:

CoreELEC:~ # udevadm info /sys/bus/sdio/devices/*
P: /devices/platform/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
L: 0
E: DEVPATH=/devices/platform/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=SSV6XXX_SDIO
E: SDIO_CLASS=07
E: SDIO_ID=3030:3030
E: MODALIAS=sdio:c07v3030d3030
E: SUBSYSTEM=sdio

[Portisch]

It’s included in 19.1_rc4.
But no bt, sure.