Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[SOLVED] H96 MAX H2 Bricked

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

    [SOLVED] H96 MAX H2 Bricked

    Hello Everyone!

    I recently got a H96 MAX (RK3328) which was "kind" of working, I mean besides the overheating problem (which I just placed a fan on the box and solved the problem) it was working correctly, but I needed to update it in order to attempt to install Magisk on it.

    Basically I got the newest firmware for it (yes, the correct one) and tried to flash like this:
    0- Installed the drivers (Rockchip_Driver_Assistant_4.5)
    1- Press the reset button
    2- Plug in OTG USB cable
    3- Device showed up (Loader) in the RK Android Tool
    4- Pressed install, it failed immediatly
    5- Not profit (bricked!)

    I started the device, nothing, it was dead, even the remote doesn't work anymore.

    Connecting to PC shows no device anymore.

    After that, I opened the device and tried to find the two contacts I needed to get the device to appear again in the software (not really sure if they are the correct ones, check the picture attached, anyway the device shows up again, not as Loader any more but as MASKROM).

    Problem is, no matter what I do, it just says "Download Boot Fail".

    Tried the following software, although with the same result:
    RockChip_Batch_Tool_v1.8
    FactoryTool-v1.45e
    RK_Android_Tool_2.3.9

    Anyone has any idea on how to recover this box?

    Thanks!!

    Click image for larger version  Name:	IMG_20180624_123931.jpg Views:	1 Size:	110.6 KB ID:	732788
    Click image for larger version  Name:	IMG_20180624_124002.jpg Views:	1 Size:	104.5 KB ID:	732789Click image for larger version  Name:	IMG_20180624_124012.jpg Views:	1 Size:	95.9 KB ID:	732790Click image for larger version  Name:	IMG_20180624_004528.jpg Views:	1 Size:	119.7 KB ID:	732791Click image for larger version  Name:	IMG_20180624_123941.jpg Views:	1 Size:	125.5 KB ID:	732792
    Last edited by Mywk; 06-28-2018, 17:38.

    #2
    Hi ,

    did you eraseFlash , before flashing with AT ???

    i think your Box only runs with the right Bootloader in Rom , looks like many of this new

    cheap RK Boxes are only can be flashed with the right programmed Bootloader Version .

    good luck / gefattern

    Comment


      #3
      Originally posted by gefattern View Post
      Hi ,

      did you eraseFlash , before flashing with AT ???

      i think your Box only runs with the right Bootloader in Rom , looks like many of this new

      cheap RK Boxes are only can be flashed with the right programmed Bootloader Version .

      good luck / gefattern
      I actually forgot to so I didn't, in MASKROM I'm completely unable to do anything (see pic).

      I'm completely new to this so I've just been following guides but can't seem to get anywhere!

      Thank you!

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

      Comment


        #4
        See my response on post #9, here : http://freaktab.com/forum/tv-player-...233#post729233
        Same problem and same shortpin

        Comment


          #5
          Originally posted by Mywk View Post

          I actually forgot to so I didn't, in MASKROM I'm completely unable to do anything (see pic).

          I'm completely new to this so I've just been following guides but can't seem to get anywhere!

          Thank you!
          Hi ,

          think the Link of User "manu_manu4" should help , good luck

          greetings / gefattern

          Comment


            #6
            It seems to be bricked for good..

            Shorting those two pins and leaving them shorted do indeed put the box in MASKROM mode, but no matter what I do I always get a "Download Boot Fail"

            Tried with Windows 10, Win 7, Win XP, DriverAssitant v4.4, v4.5 and v4.6, AndroidTool 2.52 and Batch Tool 1.8, nothing, I think the box completely died.

            -- Edit: Also tried different cables

            Comment


              #7
              Originally posted by Mywk View Post
              It seems to be bricked for good..

              Shorting those two pins and leaving them shorted do indeed put the box in MASKROM mode, but no matter what I do I always get a "Download Boot Fail"

              Tried with Windows 10, Win 7, Win XP, DriverAssitant v4.4, v4.5 and v4.6, AndroidTool 2.52 and Batch Tool 1.8, nothing, I think the box completely died.
              Hi ,

              i have the same with my UT3 , i think , a part of the Bootloader is

              bricked and can not communicate with the Tools , but there must

              ways to get it right , i found Info , online and PDFs about it , but i am

              no Dev. or Electronic Genius , RK Boxes can be booted over different

              Method , good luck / gefattern

              Comment


                #8
                Somehow I got it to get past the "Boot Failed", now when I try to "Erase Flash" I get a "Prepare IDB Fail"
                Click image for larger version

Name:	
Views:	0
Size:	3.8 KB
ID:	733332

                -- Edit: Log attached

                Code:
                19:22:00 738    Layer<1-4>:Download Boot Start
                19:22:03 401    Layer<1-4>:Download Boot Success
                19:22:03 403    Layer<1-4>:Wait For Maskrom Start
                19:22:03 796    Layer<1-4>:Wait For Maskrom Success
                19:22:03 797    Layer<1-4>:Test Device Start
                19:22:03 801    Layer<1-4>:Test Device Success
                19:22:03 803    Layer<1-4>:Get FlashInfo Start
                19:22:03 805    <LAYER 1-4> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
                19:22:03 806    <LAYER 1-4> INFO:GetFlashInfo-->Emmc storage.
                19:22:03 809    Layer<1-4>:Get FlashInfo Success
                19:22:03 811    Layer<1-4>:Prepare IDB Start
                19:22:03 812    <LAYER 1-4> ERROR:PrepareIDB-->No Found 1st Flash CS
                19:22:03 814    Error:Layer<1-4>:Prepare IDB Fail
                19:25:22 239    Layer<1-4>:Download Boot Start
                19:25:24 903    Layer<1-4>:Download Boot Success
                19:25:24 905    Layer<1-4>:Wait For Maskrom Start
                19:25:25 297    Layer<1-4>:Wait For Maskrom Success
                19:25:25 299    Layer<1-4>:Test Device Start
                19:25:25 303    Layer<1-4>:Test Device Success
                19:25:25 305    Layer<1-4>:Get FlashInfo Start
                19:25:25 307    <LAYER 1-4> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
                19:25:25 308    <LAYER 1-4> INFO:GetFlashInfo-->Emmc storage.
                19:25:25 310    Layer<1-4>:Get FlashInfo Success
                19:25:25 312    Layer<1-4>:Prepare IDB Start
                19:25:25 313    <LAYER 1-4> ERROR:PrepareIDB-->No Found 1st Flash CS
                19:25:25 315    Error:Layer<1-4>:Prepare IDB Fail
                19:25:35 194    Error:ReadIDBProc-->no found any idblock
                19:25:35 849    Error:ReadIDBProc-->no found any idblock
                19:25:36 018    Error:ReadIDBProc-->no found any idblock
                19:25:36 209    Error:ReadIDBProc-->no found any idblock
                19:25:36 546    Error:ExportIDBProc-->no found any idblock
                You may only view thumbnails in this gallery. This gallery has 1 photos.

                Comment


                  #9
                  Originally posted by Mywk View Post
                  Somehow I got it to get past the "Boot Failed", now when I try to "Erase Flash" I get a "Prepare IDB Fail"
                  Click image for larger version

Name:	
Views:	0
Size:	3.8 KB
ID:	733332

                  -- Edit: Log attached

                  Code:
                  19:22:00 738 Layer<1-4>:Download Boot Start
                  19:22:03 401 Layer<1-4>:Download Boot Success
                  19:22:03 403 Layer<1-4>:Wait For Maskrom Start
                  19:22:03 796 Layer<1-4>:Wait For Maskrom Success
                  19:22:03 797 Layer<1-4>:Test Device Start
                  19:22:03 801 Layer<1-4>:Test Device Success
                  19:22:03 803 Layer<1-4>:Get FlashInfo Start
                  19:22:03 805 <LAYER 1-4> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
                  19:22:03 806 <LAYER 1-4> INFO:GetFlashInfo-->Emmc storage.
                  19:22:03 809 Layer<1-4>:Get FlashInfo Success
                  19:22:03 811 Layer<1-4>:Prepare IDB Start
                  19:22:03 812 <LAYER 1-4> ERROR:PrepareIDB-->No Found 1st Flash CS
                  19:22:03 814 Error:Layer<1-4>:Prepare IDB Fail
                  19:25:22 239 Layer<1-4>:Download Boot Start
                  19:25:24 903 Layer<1-4>:Download Boot Success
                  19:25:24 905 Layer<1-4>:Wait For Maskrom Start
                  19:25:25 297 Layer<1-4>:Wait For Maskrom Success
                  19:25:25 299 Layer<1-4>:Test Device Start
                  19:25:25 303 Layer<1-4>:Test Device Success
                  19:25:25 305 Layer<1-4>:Get FlashInfo Start
                  19:25:25 307 <LAYER 1-4> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
                  19:25:25 308 <LAYER 1-4> INFO:GetFlashInfo-->Emmc storage.
                  19:25:25 310 Layer<1-4>:Get FlashInfo Success
                  19:25:25 312 Layer<1-4>:Prepare IDB Start
                  19:25:25 313 <LAYER 1-4> ERROR:PrepareIDB-->No Found 1st Flash CS
                  19:25:25 315 Error:Layer<1-4>:Prepare IDB Fail
                  19:25:35 194 Error:ReadIDBProc-->no found any idblock
                  19:25:35 849 Error:ReadIDBProc-->no found any idblock
                  19:25:36 018 Error:ReadIDBProc-->no found any idblock
                  19:25:36 209 Error:ReadIDBProc-->no found any idblock
                  19:25:36 546 Error:ExportIDBProc-->no found any idblock
                  Hi ,

                  that is exactly the same as on my UT3 same Errors , until now

                  i was not able to restore , i do not know how , or tried not all ,

                  try to read IDB with AT2.35 or higher and report ,

                  Ways , good luck / gefattern

                  Comment


                    #10
                    So lets drop here some more data, just in case someone knows how to help.

                    Drivers: Tried 4.4 and 4.6
                    Android Tool: Tried 2.3.9 and 2.52 (Chinese version)

                    In any of them I get stuck with "Prepare IDB Fail" after trying to "Erase Flash"

                    Code:
                    21:45:14 499    Layer<1-1-2>:Download Boot Start
                    21:45:18 281    Layer<1-1-2>:Download Boot Success
                    21:45:18 283    Layer<1-1-2>:Wait For Maskrom Start
                    21:45:18 700    Layer<1-1-2>:Wait For Maskrom Success
                    21:45:18 702    Layer<1-1-2>:Test Device Start
                    21:45:18 705    Layer<1-1-2>:Test Device Success
                    21:45:18 710    Layer<1-1-2>:Get FlashInfo Start
                    21:45:18 711    <LAYER 1-12> INFO:FlashInfo: 00 00 00 00 00 04 04 00 28 00 00
                    21:45:18 713    <LAYER 1-12> INFO:GetFlashInfo-->Emmc storage.
                    21:45:18 722    Layer<1-1-2>:Get FlashInfo Success
                    21:45:18 730    Layer<1-1-2>:Prepare IDB Start
                    21:45:18 731    <LAYER 1-12> ERROR:PrepareIDB-->No Found 1st Flash CS
                    21:45:18 741    Error:Layer<1-1-2>:Prepare IDB Fail
                    21:46:02 879    Error:ReadIDBProc-->no found any idblock
                    Code:
                    Get FlashInfo Start
                    Manufacturer: Samsung
                    Flash Size: 0MB
                    Block Size: 512KB
                    Page Size: 2KB
                    ECC Bits: 0
                    Access Time: 40
                    Flash CS:
                    Get FlashInfo Success
                    -- Edit: Something funny is happening tho, I no longer need to use the contacts to enter MASKROM, just plugging in the USB goes directly to MASKROM mode.

                    Comment


                      #11
                      Hi ,

                      same as my UT3 , look here :

                      http://freaktab.com/forum/tv-player-...ed-idb-bricked

                      i think it has to do with the "No Found 1 Flash CS" , this are

                      the first few Bytes of Bootloader , i think / AdressArea 0x40 ,

                      or similar , read online something about it .

                      There are Ways to unbrick , but i do not know how to do this .

                      Hopefully a Crack reads this and decided to help , for sure

                      something with the first few Bytes of BLoader ,

                      press thumbs / gefattern

                      Comment


                        #12
                        Hi ,

                        one Question about Magisk , do you know it works & do you

                        wanted to install it on a Stockrom ???

                        greetings / gefattern

                        Comment


                          #13
                          Originally posted by gefattern View Post
                          Hi ,

                          one Question about Magisk , do you know it works & do you

                          wanted to install it on a Stockrom ???

                          greetings / gefattern
                          Hallo (:

                          The ROM I was trying to install was the "MVR9 RK3328 Nougat ROM by mo123" so I could get Magisk to work (it doesn't work on stockrom).

                          I'm getting an H96 MAX H2, hopefully that one won't die on me.

                          --
                          Regardless, I'm still trying to recover the H96 MAX that I have, I have been searching around the forum and recently tried the RKDevelopTool but without success.

                          Click image for larger version

Name:	post1.png
Views:	3233
Size:	6.9 KB
ID:	733426

                          Still "IDB Fail"

                          Comment


                            #14
                            Originally posted by Mywk View Post

                            Hallo (:

                            The ROM I was trying to install was the "MVR9 RK3328 Nougat ROM by mo123" so I could get Magisk to work (it doesn't work on stockrom).

                            I'm getting an H96 MAX H2, hopefully that one won't die on me.

                            --
                            Regardless, I'm still trying to recover the H96 MAX that I have, I have been searching around the forum and recently tried the RKDevelopTool but without success.

                            Click image for larger version

Name:	post1.png
Views:	3233
Size:	6.9 KB
ID:	733426

                            Still "IDB Fail"
                            Hi ,

                            on my Box only a part is bricked , yours is i think fully deleted ,

                            now u need all the different Loaders to test to get one back to

                            Box , did you tested in this state the SD Boot Method ??? , start

                            from SDCard ??? , maybe this works now , good luck ,

                            gefattern

                            Comment


                              #15
                              Hi ,

                              once more , if you post here , you already have the H96Max H2 ,

                              because the H96Max has a RK3399 CPU & Mali864 ,

                              you already have the H2 Model if your CPU is RK3328 , can u

                              please clarify what Box you have ,

                              otherwise the help was nearly useless , because of different

                              shortPins Locations ,

                              The pictures say your Board is MXQ RK3328 and what is this

                              strange blue thing in Picture , while flashing is it important to

                              unplug all , this can brick .

                              greetings / gefattern

                              Comment

                              Working...
                              X