Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

"SOLVED" H96 Max+ Dead?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    "SOLVED" H96 Max+ Dead?

    Hi
    I am new to these TVboxes and need some help!!
    I have a H96Max+ RK3328 Ram 4G Rom 64 Android 9.
    I accindently removed?  Kodi and after that the TVbox will not start, i only have a black screen in my TV and the box will not connect.
    I have tried to update the firmware, but got some errors, and now the box seems DEAD.
    It will not show on my computer, and when i connect it to my computer eand push the reset button down, a red light shows, but nothing happens.
    Here are some of the errors i got:

    Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
    19:35:17 590? ?  ? <LAYER 1-3-3> ERROR:RKA_SparseFile_Download-->RKU_WriteLBA failed,RetCode(-3),chunk=4
    19:35:17 598? ?  ? <LAYER 1-3-3> ERRORownloadImage-->RKA_File_Download failed(system)
    19:35:17 606? ?  ? [Error] Layer<25,1-3-3>ownload Firmware Fail
    19:35:51 357? ?  ? <LAYER 1-3-3> ERROR:ReadCapability-->RKU_ReadCapability failed,err(-8)
    19:36:20 546? ?  ? <LAYER 1-3-3> ERROR:WriteIDBWithDirect-->RKU_WriteLBA failed,ret(-3),lba(192)
    19:36:20 552? ?  ? <LAYER 1-3-3> ERRORownloadIDBlock-->WriteIDBWithDirect failed
    19:36:20 559? ?  ? [Error] Layer<25,1-3-3>ownload IDB Fail.
    If any have some ideas, Please help!!
    ? 
    Last edited by Sentralfyr; 16 November 2019, 14:50.
    Tags: None
    #2
    Originally posted by Sentralfyr View Post
    Hi
    I am new to these TVboxes and need some help!!
    I have a H96Max+ RK3328 Ram 4G Rom 64 Android 9.
    I accindently removed? Kodi and after that the TVbox will not start, i only have a black screen in my TV and the box will not connect.
    I have tried to update the firmware, but got some errors, and now the box seems DEAD.
    It will not show on my computer, and when i connect it to my computer eand push the reset button down, a red light shows, but nothing happens.
    Here are some of the errors i got:

    Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
    19:35:17 590? ? ? <LAYER 1-3-3> ERROR:RKA_SparseFile_Download-->RKU_WriteLBA failed,RetCode(-3),chunk=4
    19:35:17 598? ? ? <LAYER 1-3-3> ERRORownloadImage-->RKA_File_Download failed(system)
    19:35:17 606? ? ? [Error] Layer<25,1-3-3>ownload Firmware Fail
    19:35:51 357? ? ? <LAYER 1-3-3> ERROR:ReadCapability-->RKU_ReadCapability failed,err(-8)
    19:36:20 546? ? ? <LAYER 1-3-3> ERROR:WriteIDBWithDirect-->RKU_WriteLBA failed,ret(-3),lba(192)
    19:36:20 552? ? ? <LAYER 1-3-3> ERRORownloadIDBlock-->WriteIDBWithDirect failed
    19:36:20 559? ? ? [Error] Layer<25,1-3-3>ownload IDB Fail.
    If any have some ideas, Please help!!
    ?
    Hi ,

    was Kodi a SystemApp ??? or only uninstalled it from Apps ??? , did you use the Stockrom ??? , think you can try it with "shortPins" or maybe better with SDCard Tool , but not sure if it works with RK3328 ,

    good luck / gefattern

    Comment

      #3
      Originally posted by gefattern View Post

      Hi ,

      was Kodi a SystemApp ??? or only uninstalled it from Apps ??? , did you use the Stockrom ??? , think you can try it with "shortPins" or maybe better with SDCard Tool , but not sure if it works with RK3328 ,

      good luck / gefattern
      Thank you for answering.
      It actually seems like Kodi (RKMC) was an system app.
      No i have not tried to shortpin the unit
      I used the firmware found here: https://www.h96tvbox.com/content/6-Firmware-upgrade

      Comment

        #4
        Originally posted by Sentralfyr View Post

        Thank you for answering.
        It actually seems like Kodi (RKMC) was an system app.
        No i have not tried to shortpin the unit
        I used the firmware found here: https://www.h96tvbox.com/content/6-Firmware-upgrade
        Hi ,

        so you are back to life ,

        good luck / gefattern

        Comment

          #5
          Originally posted by gefattern View Post

          Hi ,

          so you are back to life ,

          good luck / gefattern
          i just get prepare idb failed error. it got bricked  after i uninnstalled RKMC. tried to short the pins too but no luck

          Comment

            #6
            Here is the error after last attemt, used shortpin and factory tool.
            How can i try to use a SD card and test if that works?
            19:34:37 744 Layer<24,1-3-2>ownload Boot Start
            19:34:40 780 Layer<24,1-3-2>ownload Boot Success
            19:34:40 794 Layer<24,1-3-2>:Wait For Maskrom Start
            19:34:41 229 Layer<24,1-3-2>:Wait For Maskrom Success
            19:34:41 250 Layer<24,1-3-2>:Test Device Start
            19:34:41 263 Layer<24,1-3-2>:Test Device Success
            19:34:41 271 Layer<24,1-3-2>:Get FlashInfo Start
            19:34:41 315 <LAYER 1-3-2> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
            19:34:41 326 <LAYER 1-3-2> INFO:GetFlashInfo-->Emmc storage.
            19:34:41 340 Layer<24,1-3-2>:Get FlashInfo Success
            19:34:41 360 Layer<24,1-3-2>:Erase Flash Start
            19:34:41 373 Layer<24,1-3-2>:Erase Flash Success
            19:34:41 405 Layer<24,1-3-2>:Test Device Start
            19:34:41 457 Layer<24,1-3-2>:Test Device Success
            19:34:41 542 Layer<24,1-3-2>:Check Chip Start
            19:34:41 574 Layer<24,1-3-2>: Check Chip Success
            19:34:41 587 Layer<24,1-3-2>:Get FlashInfo Start
            19:34:41 595 <LAYER 1-3-2> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
            19:34:41 603 <LAYER 1-3-2> INFO:GetFlashInfo-->Emmc storage.
            19:34:41 614 Layer<24,1-3-2>:Get FlashInfo Success
            19:34:41 624 Layer<24,1-3-2>:Prepare IDB Start
            19:34:41 639 <LAYER 1-3-2> ERROR:PrepareIDB-->No Found 1st Flash CS
            19:34:41 651 [Error] Layer<24,1-3-2>:Prepare IDB Fail

            Comment

              #7
              I have the same problem with one box. I tried everything.
              It always ends Prepare IDB Fail. I think the chip is defective and the box is dead.

              Comment

                #8
                Tested with Rockchip Factory tool, and it ended up like this:
                08:33:27 884? ?  ? LoadExtension-->firmwarekernel.dll file is not exist
                08:33:27 926? ?  ? Got adb device vid:0x2207
                08:33:27 939? ?  ? C:\Users\Desktop\H96MAX+\RockChip_FactoryTool_v5 .3\RockChip_FactoryTool_v5.3\bin\AdbWinApi.dll
                08:34:38 953? ?  ? INFO:Unpacking union image...
                08:34:38 960? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\RKImageMaker. exe" -unpack "C:\Users\Downloads\RK3328_DC_H96_MAX+_noaddon _HS2 734C_9_20190427.2348\RK3328_DC_H96_MAX+_noaddon_HS 2734C_9_20190427.2348.img" "C:\Users\Desktop\H96MAX+\RockChip_FactoryTool _v5. 3\RockChip_FactoryTool_v5.3\Temp"***
                08:34:56 413? ?  ? ********RKImageMaker ver 1.62 ********
                Unpacking image, please wait...
                Exporting boot.bin
                Exporting firmware.img
                Unpacking image success.

                08:34:56 421? ?  ? INFO:Unpack union image ok
                08:34:56 428? ?  ? INFO:Unpacking android image...
                08:34:56 435? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\AFPTool.exe" -unpack "C:\Users\Desktop\H96MAX+\RockChip_FactoryTool _v5. 3\RockChip_FactoryTool_v5.3\Temp\firmware.img" "C:\Users\ALLAN\Desktop\H96MAX+\RockChip_Facto ryTo ol_v5.3\RockChip_FactoryTool_v5.3\Temp\Android"***
                08:35:16 093? ?  ? Android Firmware Package Tool v1.62

                Check file... OK

                ------- UNPACK ------

                package-file? ?  ? 0x0000000000000800? ?  ? 0x0000000000000307

                Image/MiniLoaderAll.bin? ?  ? 0x0000000000001000? ?  ? 0x000000000002D14E

                Image/parameter.txt? ?  ? 0x000000000002E800? ?  ? 0x0000000000000366

                Image/trust.img? ?  ? 0x000000000002F000? ?  ? 0x0000000000400000

                Image/uboot.img? ?  ? 0x000000000042F000? ?  ? 0x0000000000400000

                Image/misc.img? ?  ? 0x000000000082F000? ?  ? 0x000000000000C000

                Image/baseparameter.img? ?  ? 0x000000000083B000? ?  ? 0x0000000000100000

                Image/boot.img? ?  ? 0x000000000093B000? ?  ? 0x00000000017E9000

                Image/dtbo.img? ?  ? 0x0000000002124000? ?  ? 0x0000000000000133

                Image/vbmeta.img? ?  ? 0x0000000002124800? ?  ? 0x0000000000001000

                Image/recovery.img? ?  ? 0x0000000002125800? ?  ? 0x00000000021C6800

                Image/system.img? ?  ? 0x00000000042EC000? ?  ? 0x0000000070C7C0D0

                Image/vendor.img? ?  ? 0x0000000074F68800? ?  ? 0x0000000008D95064

                Image/oem.img? ?  ? 0x000000007DCFE000? ?  ? 0x000000000002704C

                Unpack firmware OK!

                ------ OK ------

                08:35:16 102? ?  ? INFO:Unpack android image ok,Image(Current dir\Temp\Android\Image)
                08:35:16 109? ?  ? INFO:Unpacking kernel.img in boot...
                08:35:16 116? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\unBootImg.exe " "-k" "C:\USERS\DESKTOP\H96MAX+\ROCKCHIP_FACTORYTOOL _V5. 3\ROCKCHIP_FACTORYTOOL_V5.3\TEMP\ANDROID\IMAGE\BOO T.IMG"***
                08:35:16 329? ?  ? unBootimg start...

                unBootimg success.


                08:35:16 336? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\mkkrnlimg.exe " "C:\Users\Desktop\H96MAX+\RockChip_FactoryTool _v5. 3\RockChip_FactoryTool_v5.3\bin\kernel.img" "C:\Users\Desktop\H96MAX+\RockChip_FactoryTool _v5. 3\RockChip_FactoryTool_v5.3\Temp\Android\Image\ker nel.img"***
                08:35:16 748? ?  ? mkkrnlimg finishing.

                08:35:16 757? ?  ? INFO:Unpack kernel.img ok in boot
                08:35:16 765? ?  ? INFO:Unpacking resource.img in boot...
                08:35:16 772? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\unBootImg.exe " "-s" "C:\USERS\DESKTOP\H96MAX+\ROCKCHIP_FACTORYTOOL _V5. 3\ROCKCHIP_FACTORYTOOL_V5.3\TEMP\ANDROID\IMAGE\BOO T.IMG"***
                08:35:16 984? ?  ? unBootimg start...

                unBootimg success.


                08:35:16 997? ?  ? INFO:Unpack resource.img ok in boot
                08:35:17 004? ?  ? INFO:Unpacking boot.img...
                08:35:17 012? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\unBootImg.exe " "-r" "C:\USERS\ALLAN\DESKTOP\H96MAX+\ROCKCHIP_FACTO RYTO OL_V5.3\ROCKCHIP_FACTORYTOOL_V5.3\TEMP\ANDROID\IMA GE\BOOT.IMG"***
                08:35:17 225? ?  ? unBootimg start...

                head.kernel_size = 0128F008.

                head.page_size = 00000800.

                dwOffsetSector = 00002520.

                dwRemain = 00000000.

                unBootimg success.


                08:35:17 233? ?  ? ***"C:\Users\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\bin\UnpackRamdisk .bat"***
                08:35:17 647? ?  ? start to unpack ramdisk
                start to gunzip
                Could Not Find C:\UsersDesktop\H96MAX+\RockChip_FactoryTool_v5.3\ RockChip_FactoryTool_v5.3\Temp\Boot\ramdisk.cpio.g z
                cygwin warning:
                ?  MS-DOS style path detected: ..\Temp\Boot\ramdisk.cpio.gz
                ?  Preferred POSIX equivalent is: ../Temp/Boot/ramdisk.cpio.gz
                ?  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
                ?  Consult the user's guide for more details about POSIX paths:
                ? ? ?  http://cygwin.com/cygwin-ug-net/usin...sing-pathnames

                gzip: ..\Temp\Boot\ramdisk.cpio.gz: unexpected end of file
                start to create ramdisk directory
                start to cpio
                Systemet finner ikke angitt fil.
                start to del data
                Could Not Find C:\Users\Desktop\H96MAX+\RockChip_FactoryTool_v5.3 \RockChip_FactoryTool_v5.3\Temp\Boot\ramdisk.cpio
                Info:unpack ramdisk.img success.

                08:35:17 655? ?  ? ERROR:RunOhterExe-->GetBatCmdResult failed
                08:35:17 663? ?  ? ***"C:\Users\H96MAX+\RockChip_FactoryTool_v5.3\R ockChip_FactoryTool_v5.3\bin\UnpackRamdisk.bat"***
                08:35:18 081? ?  ? start to unpack ramdisk
                start to gunzip
                Systemet finner ikke angitt fil.
                cygwin warning:
                ?  MS-DOS style path detected: ..\Temp\Boot\ramdisk.cpio.gz
                ?  Preferred POSIX equivalent is: ../Temp/Boot/ramdisk.cpio.gz
                ?  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
                ?  Consult the user's guide for more details about POSIX paths:
                ? ? ?  http://cygwin.com/cygwin-ug-net/usin...sing-pathnames
                gzip: ..\Temp\Boot\ramdisk.cpio.gz: No such file or directory
                start to create ramdisk directory
                del ramdisk directory
                start to cpio
                Systemet finner ikke angitt fil.
                start to del data
                Could Not Find C:\Users\ALLAN\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\Temp\Boot\ramdisk .cpio
                Info:unpack ramdisk.img success.

                08:35:18 089? ?  ? INFO:Unpack boot.img ok,boot(Current dir\Temp\Boot)
                08:35:18 097? ?  ? INFO:Unpacking recovery.img...
                08:35:18 104? ?  ? ***"C:\Users\ALLAN\Desktop\H96MAX+\RockChip_Fact oryTool_v5.3\RockChip_FactoryTool_v5.3\bin\unBootI mg.exe" "-r" "C:\USERS\ALLAN\DESKTOP\H96MAX+\ROCKCHIP_FACTO RYTO OL_V5.3\ROCKCHIP_FACTORYTOOL_V5.3\TEMP\ANDROID\IMA GE\RECOVERY.IMG"***
                08:35:18 316? ?  ? unBootimg start...

                head.kernel_size = 0128F008.

                head.page_size = 00000800.

                dwOffsetSector = 00002520.

                dwRemain = 009DCAE5.

                unBootimg success.


                08:35:18 330? ?  ? ***"C:\Users\ALLAN\Desktop\H96MAX+\RockChip_Fact oryTool_v5.3\RockChip_FactoryTool_v5.3\bin\UnpackK ernelRecovery.bat"***
                08:35:19 945? ?  ? start to unpack recovery
                start to gunzip
                start to rename
                Could Not Find C:\Users\ALLAN\Desktop\H96MAX+\RockChip_FactoryToo l_v5.3\RockChip_FactoryTool_v5.3\Temp\recovery\rec overy.cpio.gz
                end to rename
                cygwin warning:
                ?  MS-DOS style path detected: ..\Temp\recovery\recovery.cpio.gz
                ?  Preferred POSIX equivalent is: ../Temp/recovery/recovery.cpio.gz
                ?  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
                ?  Consult the user's guide for more details about POSIX paths:
                ? ? ?  http://cygwin.com/cygwin-ug-net/usin...sing-pathnames
                start to create recovery directory
                start to cpio
                41970 blocks
                start to del data
                Info:unpack recovery.img success.

                08:35:19 957? ?  ? INFO:Unpack recovery.img ok,recovery(Current dir\Temp\Recovery)
                08:35:19 989? ?  ? INFO:Unpacking system.img...
                08:35:20 056? ?  ? ***"C:\Users\ALLAN\Desktop\H96MAX+\RockChip_Fact oryTool_v5.3\RockChip_FactoryTool_v5.3\bin\cramfsc k.exe" -x "C:\Users\ALLAN\Desktop\H96MAX+\RockChip_Facto ryTo ol_v5.3\RockChip_FactoryTool_v5.3\Temp\System" "C:\USERS\ALLAN\DESKTOP\H96MAX+\ROCKCHIP_FACTO RYTO OL_V5.3\ROCKCHIP_FACTORYTOOL_V5.3\TEMP\ANDROID\IMA GE\SYSTEM.IMG"***
                08:35:20 273? ?  ? cygwin warning:
                ?  MS-DOS style path detected: c:\users\allan\desktop\h96max+\rockchip_factorytoo l_v5.3\rockchip_factorytool_v5.3\temp\android\imag e\system.img
                ?  Preferred POSIX equivalent is: /temp/android/image/system.img
                ?  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
                ?  Consult the user's guide for more details about POSIX paths:
                ? ? ?  http://cygwin.com/cygwin-ug-net/usin...sing-pathnames
                /usr/bin/cramfsck: superblock magic not found

                08:35:20 282? ?  ? INFO:Unpack system.img fail,please confirm that partition is NTFS.
                08:35:31 014? ?  ? Exit AdbDeviceDetectThread


                Is there any way to try update by SD card?

                Comment

                  #9
                  SOLVED
                  Yeah, just figuret out and the box is NOT dead.
                  First i tried the shortpin solution without success, and then i tried the reset button method and restore option in FactoryTool and that suddenly worked for me.
                  Then i connected the box to my TV and the first picture came up on my tv



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

                  Comment

                    #10
                    Originally posted by Sentralfyr View Post
                    SOLVED
                    Yeah, just figuret out and the box is NOT dead.
                    First i tried the shortpin solution without success, and then i tried the reset button method and restore option in FactoryTool and that suddenly worked for me.
                    Then i connected the box to my TV and the first picture came up on my tv



                    ?
                    Hi ,

                    can you explain it better , for other Users with same Problems , thanks ,

                    greetings / gefattern

                    Comment

                      #11
                      Originally posted by gefattern View Post

                      Hi ,

                      can you explain it better , for other Users with same Problems , thanks ,

                      greetings / gefattern
                      Ok i give it a try, even if i had no guide myself and iam a newbie, hopfully i can explain myself good enough.

                      1.First of all i tried to use the Factorytool and used the "Restore option" but i always got an error lik IDB Fail (i followed this guide).
                      2.Then i tried the Upgrade option in Factorytool, but no luck there either.

                      3.Then i tried the ShortPin solution, also with no luck several times, but what i did last, was to use the ShortPin option in Factorytool and the Restore Option, and then at last i tried again the 1 option again with NO Shortpin reset only the guide showed in the video and suddenly it worked for me.

                      The best of all with my error and fails with my box, it came a lot faster to start up, just a few seconds,

                      Comment

                        #12
                        Do you have any problems using H96 max? This blog post summarizes 7 common questions, which I think may help you.

                        Comment

                          #13
                          Although the TV box is good, it is easy to have problems sometimes, so you should have a certain understanding before you buy it.

                          Comment

                          Previous template Next

                          What's Going On

                          Collapse

                          There are currently 2390 users online. 2 members and 2388 guests.

                          Most users ever online was 63,956 at 18:56 on 20 March 2025.

                          Working...
                          X

                          We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                          By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                          I Agree