Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] "GENERIC" SC v2.0 USER/USERDEBUG - S905x2 / S905x3 - "Normal" Android 9

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Hi, superceleron.
    I got H96max X3 TV box yesterday (https://aliexpress.ru/item/400054225...255033edb5ZjSD). It's worked bad on the own firmware. So I installed this your firmware to my new box. Result: the box is working much better now but not working Wi-Fi at all and also not working katniss. Could you help me sort this issues, please?

    Comment


      #17
      Originally posted by saddas View Post
      Hi, superceleron.
      I got H96max X3 TV box yesterday (https://aliexpress.ru/item/400054225...255033edb5ZjSD). It's worked bad on the own firmware. So I installed this your firmware to my new box. Result: the box is working much better now but not working Wi-Fi at all and also not working katniss. Could you help me sort this issues, please?
      Well on wifi, i bet is a RTL chip... not much i can help you there!
      On katniss what you mean? katniss is Android TV assistant( you need a mic ), here work just fine.

      Comment


        #18
        Hi all!
        Installing a su-APP to my X96max+ with stock-ROM(AIDA64-app showed "rooted"), I bricked it . . .
        No connect with USB-burning-tool and flashing the stock.IMG by micro-SD shows a killed android on screen :-)
        As stock-recovery is still working, I'm in need of i.e. an ota.zip to get the device back to life.
        Problem is: Can't find any zip only stock.img . . .

        @superceleron
        Your rom.zip(correctly signed for X96max+, if needed?) could repair the device. Perhaps You got some time in future to do it?
        THANK YOU!

        Comment


          #19
          Originally posted by Halifax View Post
          Hi all!
          "..... I'm in need of i.e. an ota.zip to get the device back to life.
          Problem is: Can't find any zip only stock.img . . .

          @superceleron
          Your rom.zip(correctly signed for X96max+, if needed?) could repair the device. Perhaps You got some time in future to do it?
          THANK YOU!
          Probably be a loong wait...
          Find ANY device acceptable zipto get back "up".
          Perhaps then you can load twrp and have Some flexibility with flashing a desired rom.
          Did you look at Magendanz ota work? idk ther is compatibles, just a thought. Also you might try to change the updater script to match the oem checking language. Provided hw is a match otherwise.
          ~ Luck 2ya!
          Kris....don't forget my boxes! Okay?

          Comment


            #20
            Thanks for Your speedy answer!

            Originally posted by ClarkKent View Post
            . . . Find ANY device acceptable zipto get back "up".
            zip has to be signed correctly for X96max+ and stock-recovery . . .

            Originally posted by ClarkKent View Post
            . . . Perhaps then you can load twrp and have Some flexibility with flashing a desired rom. . . .
            Workable idea, this one is for X96max, failed for X96max+:

            How to Use? 1. Put the attachment file in SDCard/USB Drive 2. Plug in the USB 3. Plug in the power while holding the reset button(found inside the AV Ports usually) 4. After you get into recovery, use remote to select Apply Update from SDCard 5...


            Originally posted by ClarkKent View Post
            . . . Did you look at Magendanz ota work? . . .
            Link to "Magendanz" ?

            THANK YOU !

            Comment


              #21
              Originally posted by Halifax View Post
              Hi all!
              Installing a su-APP to my X96max+ with stock-ROM(AIDA64-app showed "rooted"), I bricked it . . .
              No connect with USB-burning-tool and flashing the stock.IMG by micro-SD shows a killed android on screen :-)
              As stock-recovery is still working, I'm in need of i.e. an ota.zip to get the device back to life.
              Problem is: Can't find any zip only stock.img . . .

              @superceleron
              Your rom.zip(correctly signed for X96max+, if needed?) could repair the device. Perhaps You got some time in future to do it?
              THANK YOU!
              try AMLogicTools_V6.0.0 CustomizationTool.exe.

              unpack amlogic update img and then repack to the update.zip format.





              You may only view thumbnails in this gallery. This gallery has 1 photos.

              Comment


                #22
                Originally posted by blust0ne View Post

                try AMLogicTools_V6.0.0 CustomizationTool.exe.

                unpack amlogic update img and then repack to the update.zip format.
                Already tried, but failed for missing META-INF(of stock-OTA.zip) . . .

                While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux. I won't go into too many details as I have to assume everyone attempting this did at...


                Method two (I never tested that):
                Take the META-INF folder from an OTA update of a box with identical hardware specs.

                Comment


                  #23
                  Don't work on H96 X2 MAX LPDDR3 4\32.

                  Comment


                    #24
                    Originally posted by kalikimaka View Post
                    Don't work on H96 X2 MAX LPDDR3 4\32.
                    Pitty thks for let all know

                    Comment


                      #25
                      Originally posted by kalikimaka View Post
                      Don't work on H96 X2 MAX LPDDR3 4\32.
                      try system.img only.

                      my h96max x2 4G lpddr3 can run ATV debug image well.

                      unpack the image and you should resize the system.PARTITION image as 0x5c800000 size in linux machine.

                      using update.exe (AMLogicTools_V6.0.0 has the tools on bin foilder) to flash like usb burning tool.

                      http://openlinux.amlogic.com:8000/do...user_guide.pdf

                      Comment


                        #26
                        Originally posted by blust0ne View Post

                        try system.img only.

                        my h96max x2 4G lpddr3 can run ATV debug image well.

                        unpack the image and you should resize the system.PARTITION image as 0x5c800000 size in linux machine.

                        using update.exe (AMLogicTools_V6.0.0 has the tools on bin foilder) to flash like usb burning tool.

                        http://openlinux.amlogic.com:8000/do...user_guide.pdf
                        where I can get system.img? tnx

                        Comment


                          #27
                          Originally posted by kalikimaka View Post

                          where I can get system.img? tnx
                          check your android version and system partition size first.

                          Android 9.0 and system partition larger than 0x78000000 (the SC's image size ) is required.

                          CustomizationTool.exe of AMLogicTools_V6.0.0 can unpack this image on the tmp\level1 folder, system.PARTITION.

                          if you partition is enough to fit this image, AMLogicTools_V6.0.0\bin\update.exe can update the system partition as usb_burning_tools.

                          update bulkcmd "disk_initial 0"
                          update partition system system.PARTITION
                          update bulkcmd "reboot recovery"
                          factory reset at recovery menu and reboot.

                          if you partition is smaller than 0x78000000, using the linux system , resize the system.PARTITON image to fit yours.

                          simg2img (change sparse image to normal ext4 image) -> resize2fs (resize the ext4 image ) and then burn.

                          ----------------------------------

                          my h96max x2 , 4G lpddr3 and 64G eMMC

                          [ 3.639895@2] meson-mmc: [mmcblk0p01] bootloader offset 0x000000000000, size 0x000000400000
                          [ 3.640010@2] meson-mmc: [mmcblk0p02] reserved offset 0x000002400000, size 0x000004000000
                          [ 3.640131@2] meson-mmc: [mmcblk0p03] cache offset 0x000006c00000, size 0x000046000000
                          [ 3.640245@2] meson-mmc: [mmcblk0p04] env offset 0x00004d400000, size 0x000000800000
                          [ 3.640380@2] meson-mmc: [mmcblk0p05] logo offset 0x00004e400000, size 0x000000800000
                          [ 3.640492@2] meson-mmc: [mmcblk0p06] recovery offset 0x00004f400000, size 0x000001800000
                          [ 3.640595@2] meson-mmc: [mmcblk0p07] misc offset 0x000051400000, size 0x000000800000
                          [ 3.640706@2] meson-mmc: [mmcblk0p08] dtbo offset 0x000052400000, size 0x000000800000
                          [ 3.640810@2] meson-mmc: [mmcblk0p09] cri_data offset 0x000053400000, size 0x000000800000
                          [ 3.640922@2] meson-mmc: [mmcblk0p10] param offset 0x000054400000, size 0x000001000000
                          [ 3.641042@2] meson-mmc: [mmcblk0p11] boot offset 0x000055c00000, size 0x000001000000
                          [ 3.641144@2] meson-mmc: [mmcblk0p12] rsv offset 0x000057400000, size 0x000001000000
                          [ 3.641256@2] meson-mmc: [mmcblk0p13] metadata offset 0x000058c00000, size 0x000001000000
                          [ 3.641359@2] meson-mmc: [mmcblk0p14] vbmeta offset 0x00005a400000, size 0x000000200000
                          [ 3.641471@2] meson-mmc: [mmcblk0p15] tee offset 0x00005ae00000, size 0x000002000000
                          [ 3.641583@2] meson-mmc: [mmcblk0p16] vendor offset 0x00005d600000, size 0x000014000000
                          [ 3.641687@2] meson-mmc: [mmcblk0p17] odm offset 0x000071e00000, size 0x000008000000
                          [ 3.641799@2] meson-mmc: [mmcblk0p18] system offset 0x00007a600000, size 0x00005c800000
                          [ 3.641903@2] meson-mmc: [mmcblk0p19] product offset 0x0000d7600000, size 0x000008000000
                          [ 3.642017@2] meson-mmc: [mmcblk0p20] data offset 0x0000dfe00000, size 0x000dafa00000


                          ----------------------------------

                          All amlogic 9.0 firmware's system.img can be run if the partiton size is enough.

                          if the size is small , it is on the boot-loop with the kernel message.

                          [ 5.949485@2] EXT4-fs (mmcblk0p18): couldn't mount as ext3 due to feature incompatibilities
                          [ 5.957642@2] EXT4-fs (mmcblk0p18): couldn't mount as ext2 due to feature incompatibilities
                          [ 5.966305@2] EXT4-fs (mmcblk0p18): bad geometry: block count 475136 exceeds size of device (378880 blocks)
                          [ 5.976918@2] [EXFAT] trying to mount...
                          [ 5.978754@2] VFS: Cannot open root device "mmcblk0p18" or unknown-block(179,18): error -5
                          [ 5.986827@2] Please append a correct "root=" boot option; here are the available partitions:

                          ---
                          Click image for larger version

Name:	update.png
Views:	1716
Size:	15.9 KB
ID:	796074

                          Comment


                            #28
                            blust0ne thank you, I'll try

                            Comment


                              #29
                              Yes, is not that hard to do if you follow blust0ne directions.
                              I use 0x78000000 ( That translates to 2Gb partition size ) size because i like to be prepared to add more stuff in it, without having to mess with DT and sdk configs all the time.

                              Comment


                                #30
                                Originally posted by saddas View Post
                                Hi, superceleron.
                                I got H96max X3 TV box yesterday (https://aliexpress.ru/item/400054225...255033edb5ZjSD). It's worked bad on the own firmware. So I installed this your firmware to my new box. Result: the box is working much better now but not working Wi-Fi at all and also not working katniss. Could you help me sort this issues, please?
                                hello,

                                did you find a solution regarding the wifi?

                                Comment

                                Working...
                                X