Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Android 13 ATV AMLOGIC S912 (Lineage OS 20) LPDDR3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Android 13 ATV AMLOGIC S912 (Lineage OS 20) LPDDR3

    Thought could be a good idea to open new thread for devices using LPDDR3 like TX92, Vontar, H96+ pro....

    Thanks bumerc for the hint!



    Click image for larger version  Name:	IMG-20230415-WA0004.jpg Views:	0 Size:	130.3 KB ID:	832276
    Micron D9TXF >> MT52L768M32D3PU-107 WT:B (part number) max 933MHZ, LPDDR3

    Build by HighwayStar :

    4pda

    Build by bumerc:

    https://forum.freaktab.com/node/8321...824#post833824

    EVERYTHING WORKS




    UART Log



    Explanation



    Thanks bumerc
    Last edited by soldiaz; 20 January 2024, 17:02.

    #2
    Dear bumerc I flashed HighwayStar 's image and it boots up on Vorke LPDDR3 device.

    Unfortunately I cant pass setup since wifi drivers are missing. Vorke uses qca9377 wifi / BT combo. If you could supply proper vendor would be awesome and I will continue testing

    So far 2 suggestions:

    - guess would be good to remove setup assistant 1st step (need to press back + home)

    - lower USB port without function only 1 port working

    + reset button still working !

    Comment


      #3
      soldiaz
      As promised, TX92 build.
      Brief information and notes - CPU S912
      - Platforn GXM, Q200
      - RAM LPDDR3, capacity - 3G
      - ETH 1000Mbit
      - Wi-Fi/BT QCA9377

      Build is only suitable for lpddr3/3g devices and has not been tested by me. Gapps are integrated. Ir-remote debug is activated by default in the driver, you can now take the key codes from the dmesg or from the logcat. Happy testing :-)

      Download
      Last edited by bumerc; 13 April 2023, 17:57. Reason: reuploadet 1st link

      Comment


        #4
        Thanks so much didnt expect it that fast!

        Unfortunately I get
        [0x10105004]Romcode/Initialize DDR/Read initialize status/Error result
        Tried burning tool 2.2 and 2.1.7.3

        Try mixing Highway's and your files ;-)
        Last edited by soldiaz; 13 April 2023, 17:20.

        Comment


          #5
          After mixing box bricked lol....but MASK mode easy....puuh

          I took these files from yours and overwrote Highway's:

          boot.partition
          bootloader.partition
          dtbo.partition
          logo
          meson1.dtb
          odm.partition
          product.partition
          recovery.partition
          system.partition
          vendor.partition

          Guess Ill try system, vendor, product only....

          Comment


            #6
            Originally posted by soldiaz View Post
            After mixing box bricked lol....but MASK mode easy....puuh

            I took these files from yours and overwrote Highway's:

            boot.partition
            bootloader.partition
            dtbo.partition
            logo
            meson1.dtb
            odm.partition
            product.partition
            recovery.partition
            system.partition
            vendor.partition

            Guess Ill try system, vendor, product only....
            You just need to replace the bootloader and dtb. I will send you another u-boot later, 768mhz seems to be too much for your device

            Comment


              #7
              soldiaz
              Oh, I forgot. If you replace the dtb, you have to copy the partition sizes from my dtb to the other dtb, otherwise it won't boot

              Comment


                #8
                Guess Ill wait for your fixed u-boot :-p

                I copied over your system and vendor Partition only but didnt work

                Comment


                  #9
                  Originally posted by soldiaz View Post
                  Guess Ill wait for your fixed u-boot :-p

                  I copied over your system and vendor Partition only but didnt work
                  What is the factory code of your remote control? I'll reupload the IMG right away, with u-boot and ir-remote fix..

                  Comment


                    #10
                    Originally posted by bumerc View Post

                    factory code
                    Cant say...it is not important (for me) since I am using Airmouse anyway. I can provide picture of remote if that helps?

                    Comment


                      #11
                      Originally posted by soldiaz View Post

                      Cant say...it is not important (for me) since I am using Airmouse anyway. I can provide picture of remote if that helps?
                      already included, otherwise please post logcat output
                      Code:
                       logcat -e custom_code

                      Comment


                        #12
                        Tried on H96 Pro+ S912
                        3/32
                        Same wifi

                        No go..
                        Think I have just DDR3

                        Not LPDDR3

                        Many variants of thus China Box.

                        Oh well

                        Happy Testing

                        Comment


                          #13
                          freddy
                          There are different manufacturers and PCB revisions of this device. Feel free to post PCB photos, even better would be a boot log (uart) from the stock firmware

                          Comment


                            #14
                            That is going to be pain due to the many different boards out there, hell even same boards but with different chips...
                            That is why i stop supporting s912 devices, when a chip starts to have to many crap out i stop the support for it.

                            Comment


                              #15
                              Originally posted by superceleron View Post
                              That is going to be pain due to the many different boards out there, hell even same boards but with different chips...
                              That is why i stop supporting s912 devices, when a chip starts to have to many crap out i stop the support for it.
                              It's the other way around for me.
                              Exotics that don't work challenge me

                              Comment

                              Working...
                              X