Help identifying S905X device?

[ADB]

I purchased an 'OVERBOX 4K A3X' Android TV box a while ago. I would like to replace the stock firmware for a more Google stock Nexus-like ROM if possible.
I am fairly familiar with Android and have a few phones and tablets all with custom ROMs and recovery images, but I am not too hot on the TV box side...
It seems a bit of a minefield on what actual model I have or even if its a clone? Therefore I would like some help in identifying what I actually have so I can select the correct ROM.
In the 'About' screen it says it is a 'A3X' with a bogus '0123456789abcdef' serial number and the build is 'p212-userdebug 6.0.1 MHC19J 20170213 test-keys'
Physically it appears to be this one for sale on Amazon - https://www.amazon.co.uk/dp/B06XWN7QDQ , however it is quite possibly a clone.

Thanks
Andy

[neomode]

Hello and Welcome to FT!

The best way to give you a hint would be to Open Up the Box and look inside.
Then take a Photo from both Sides of the PCB then we can see what we have.

Neomode

[ADB]

Hello and Welcome to FT!

The best way to give you a hint would be to Open Up the Box and look inside.
Then take a Photo from both Sides of the PCB then we can see what we have.

Neomode

Its a Mini M8 SII variant... I tried flashing the wrong firmware to it earlier and soft-bricked it... After some frantic reading and a makeshift USB OTG cable I have managed to recover it and have put Magendanz's TVStock firmware onto it (MINIM8SII_rv109_TVStock-20170226.img). I had already backed up the 'remote.conf' file so have got the remote working as well.

[neomode]

Sounds great!
Good Job!

Neomode

[Guest]

For future reference, you can look up the chipset in our list of Amlogic reference boards, which for this box is "p212". It's not 100% complete, but in this case it might have saved you from cracking the case to look.

[ADB]

For future reference, you can look up the chipset in our list of Amlogic reference boards, which for this box is "p212". It's not 100% complete, but in this case it might have saved you from cracking the case to look.

I think I got confused over the naming in the sub forums. Mini M8 SII seems to cover a few devices I think? You have ROMs that seem to cover both Mini MX3 II and Mini M8 SII and it was one of these that soft-briced my device (MINIMXIII-II_111M0_TVStock-20170523.img). I initially recovered it with this ROM 'update_MINIM8SII_rv112_megabox_20170320.img' and then after reading the naming of the ROM I found this on your onedrive 'MINIM8SII_rv109_TVStock-20170226.img' which I then used which is what is currently running on it. One thing that is missing is the clock on the front of the device is not displaying anything. With the stock firmware it was shipped with this displayed the current time. Is there an .apk to enable this?

The P212 reference board seems different from what my device has - mine has 1GB DRAM and no Bluetooth. I would like to get the factory ROM for my device, although I am not sure where I would find it. The vendor I purchased it from was merely an importer from China.

Cheers
Andy

[ADB]

Actually on re-reading the sticky '[ROM] Beelink Mini MX3 II / M8S II TVStock Nexus ROM (Android TV)' it seems this ROM should have probably worked?
I am assuming the release from 20170226 is the file I used to recover my unit - MINIM8SII_rv109_TVStock-20170226.img. The later releases are rebased from the Beelink ROM but should still be applicable for the Mini M8 SII? I wonder if installing the latest OTA update will work for me?
When I tried to recover the unit with the latest full burn package (MINIMXIII-II_111M0_TVStock-20170523.img) it started but failed at 4% each time. When I used the older full burn package it worked first time?

Am I doing something wrong or is my hardware incompatible with the latest ROM?

EDIT: I am obviously going to break this box at some point. I managed to install the latest update .zip (update_MINIMXIII-II_111M0_TVStock-20170523.zip) and hit some odd issues with it rebooting. After some more re-flashing and resetting I realised I was using the wrong PSU... Anyway I managed to install the latest .img (MINIMXIII-II_111M0_TVStock-20170523.img) this time without any issues with the USB_Burning_Tool, I have no idea why this didn't work last time and I did try it a few times.
Ho hum. All seems to be working now though. I had to install the AMPAK update to get the wireless working (I am using wired anyway..).

Andy