T9 TV box : Not sure about my chip version

    Hi :) For a noob with TV boxes hacking, I have a T9 box running Android with Kodi,mdlna... But i'd like to add my own things on a lightweight OS.



    The case, labels... look identical to this one in this video

    I did a backup using multitools

    I followed some topics here, armbian and even on dietpi.

    I hesitated when I wasn't sure about my chip version because cpuz (on android) and cpuid gave me different results !


    Which safe safe image I could start with to test libreelec from SDcard?

    Thank you

    Yeah sorry I didn't mentionn it ... I wasn't sure if it's a RK3328 or RK3318
    And cpuz showed RK3066 !! (that sounds weird :-/ )



    I'd go for a RK3328 stable release then...
    I found a nice tutorial posted here but I can't manage to find the appropriate links.
    May be someone had an experience with such board. Thank you

    Two comments:

    a) It's not unheard of for Android boxes to hard-code CPU identifiers in their software so that less scrupulous manufacturers can pass off older or cheaper SoC chips for something more expensive, or even chips from a completely different SoC vendor, if that helps to sell more boxes and/or clear stock. Hence you might find different SoC chips being reported in different places. The best way to check what's physically inside the box is to open it and literally see what's under the heatsink (if one is present). NB: Even that's not infallible, as we've also seen chips silk-screen reprinted to hide what they are, but that's not common.

    b) There is currently a single LE image for an RK3328 based Android box, the "a1" image. If this works, great. If not, there are no plans to add more images for Android set-top boxes. As a general rule, trying to support them is a challenge. Boxes are typically based on reference designs so there is enough in-common to easily boot an image, but booting is no guarantee of reliability and there is enough variation in designs (combined with selection of cheap low-bin components) to ensure reliability always remains slightly beyond reach; whether that's due to electrical or thermal or other reasons.

    I'll open the case and see.. I avoided it while thinking that the multitool was compatible only with those chips.

    Next if ok, i'll try LibreELEC-RK3328.aarch64-12.90.1-a1.img.gz


    Thank you sir!

    Quote from bilel

    I'll open the case and see.. I avoided it while thinking that the multitool was compatible only with those chips.

    Next if ok, i'll try LibreELEC-RK3328.aarch64-12.90.1-a1.img.gz

    Why don't do it in reverse order?

    Try the LibreELEC-RK3328... image and if isn't working open the case?

    If a heatsink is glued to the CPU, sometimes isn't a simple task to remove it without the risk to be damaged something... and will need to be glued back too... with a heat resistent glue...

    VLouis That's a great advice .. Thank you!
    If I understood well Libreelec image' bootloader would be recognized so I can test it from SDcard before flashing to the emmc and risk breaking a cloned chip.