Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

MK802 iii bricked - Error:Download IDB failed

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

    MK802 iii bricked - Error:Download IDB failed

    Hello!

    Ok, I think I bricked my MK 802 iii. My last hope is that you guys have the ultimate advice for me

    What did I do?
    I tried to install a different Linux ROM on a SD-Card, where I wanted the MK802 to boot from. It is the following one:
    Pre-Alpha 0.2 Ubuntu Linux for MK802 III / UG802 / MK808
    http://www.slatedroid.com/topic/41453-pre-alpha-02-ubuntu-linux-for-mk802-iii-ug802-mk808/
    Title says it all. No hand holding at this stage as this is really for people who know what they are doing. In a few days I'll post a proper Alpha with more/some support! Folks, I can't stress this enough: these pre-Alpha releases are only for people who have already cross-compiled the Linux...


    There is a recovery.img, which has to be flashed. I did so, booted the device to android and did a "reboot recovery" command but the boot process to Linux didnt work. I could boot to the stock android anyway, no real problem so far.

    But now I think i did a terrible mistake:
    I thought if i flash the recovery.img into the boot partition, it should boot straight from the sd-card, without booting android at first. I just wanted to try if this works. And from there the device doesnt boot anymore.
    It always starts in "mask rom" mode directly. So i tried to recover my device by flashing a stock rom with RKBatchTool (v 1.7.) but it ended up with an error: Download IDB Failed.
    And now this Error is what every try to recovery my device ends with.

    What did I try?
    I tried to flash many different ROMs with many different Tools: FinlessROM 1.7c and Finless 1.4a with ROM FlashTool. Stock ROM old version and new version with RKBatchTool (v 1.7. & v 1.5.).
    I googled like hell, found different hints to short circuit different pins: 6&7 (which brings the device in mask rom, no help, my device starts in mask rom anyway). 8&9, the peds next to the nand, i even tried to study the datasheet of the nand chip (toshiba TC58NVG6D2GTA00), but im not really an expert so it wasnt a help really.
    I tried different USB ports, different USB cables, a different PC with WIN 7 (im using win 7 on my too), even a different pc with win 8. No help...

    The Error in the logs of RKBatchTool:
    Code:
    22:03:28 010	<Layer 1-2> Download IDB Start
22:03:28 023	<LAYER 1-2> ERROR:WriteIDBlock-->memcmp failed
22:03:28 038	<LAYER 1-2> ERROR:WriteIDBlock-->memcmp failed
22:03:28 053	<LAYER 1-2> ERROR:WriteIDBlock-->memcmp failed
22:03:28 055	<Layer 1-2> Download IDB Fail
    The Logs of ROM Flash Tool:
    Code:
    22:02:53 462	INFO:Rewrite IDB£¬times(9)
22:02:53 462	INFO:MakeIDBlockData start
22:02:53 462	INFO:MakeEccSpareData start
22:02:53 468	INFO:WriteXIDBlock start
22:02:53 469	INFO:Writeing the 1th ID Block£¬Pos£º00009216(SEC)
22:02:53 470	INFO:Writing sector 00009216 ~ 00009231 ... 
22:02:53 473	INFO:Reading sector 00009216 ~ 00009231 ... 
22:02:53 476	INFO:check start
22:02:53 476	ERROR:WriteXIDBlock-->Check failed
22:02:53 477	ERROR:WriteXIDBlock failed,Errcode(1)
22:02:53 478	INFO:Rewrite IDB£¬times(10)
22:02:53 478	ERROR: WriteXIDBlock failed,Errcode(1)
22:02:53 478	Error:Download IDB failed
22:02:53 480	ERROR:MaskRomThread failed
22:02:53 481	ERROR:Run failed
    RKAndroidTool:
    Code:
    21:36:33 183	INFO:Rewrite IDB£¬times(9)
21:36:33 183	INFO:MakeIDBlockData start
21:36:33 183	INFO:MakeEccSpareData start
21:36:33 183	INFO:WriteXIDBlock start
21:36:33 183	INFO:Writeing the 1th ID Block£¬Pos£º00018432(SEC)
21:36:33 183	INFO:Writing sector 00018432 ~ 00018447 ... 
21:36:33 183	INFO:Reading sector 00018432 ~ 00018447 ... 
21:36:33 199	INFO:check start
21:36:33 199	ERROR:WriteXIDBlock-->Check failed
21:36:33 199	ERROR:WriteXIDBlock failed,Errcode(1)
21:36:33 199	INFO:Rewrite IDB£¬times(10)
21:36:33 199	ERROR: WriteXIDBlock failed,Errcode(1)
21:36:33 199	Error:Download IDB failed
21:36:33 199	ERROR:MaskRomThread failed
21:36:33 199	ERROR:Run failed
    Does anyone have another idea what to try??
    Tags: None
    #2
    If it is not S model you should try short circuit method (there is doc file in stock firmware)

    Comment

      #3
      I had http://www.FreakTab.com/showthread.php?t=9607 but it was bit different

      Comment

        #4
        hello dmukhin, thank you for your answer!

        Yes its correct, i dont have the S model, so there is no revocery button. I tried the short circuit method, but in the doc found in stock firmware they short 6th & 7th pin. you are talking about the 7th and 8th pin in your thread. perhaps because you have the S model?

        anyway: your solution was getting into mask rom mode. my stick is in mask rom mode every time i start it (blue box in batch tool).

        any other ideas?

        Comment

          #5
          i dont have the S model, so there is no revocery button
          Actually MK802III (not S) has recovery button - there is small hole to access it!

          in stock firmware they short 6th & 7th pin. you are talking about the 7th and 8th pin in your thread
          Really? I think I mentioned 6 and 7, check again

          anyway: your solution was getting into mask rom mode. my stick is in mask rom mode every time i start it (blue box in batch tool)
          Yes, this is what I meant by "it was bit different"

          Did you try to flash latest "MK802III Android 4.2 FW(131108)" from http://www.rikomagic.com/en/download/download_20_1.html? Did you try to erase IDB before flashing (I'm sure it was one button in RKBatchTool that does this)?

          Comment

            #6
            Actually check other tools for "Erase IDB", it could be in ROM Flash Tool

            Comment

              #7
              Originally posted by dmukhin View Post
              Actually MK802III (not S) has recovery button - there is small hole to access it!
              Are you sure? I cannot find a hole anywhere. i thought the missing recovery button is the reason why we have to short pins to get into flash mode...
              i made some pics of my model, see them below.

              Originally posted by dmukhin View Post
              Really? I think I mentioned 6 and 7, check again
              Okay, perhaps i was not reading correctly
              anyway i have no need for short circuit method for getting into mask rom because as i mentioned my stick always starts in that mode.

              Originally posted by dmukhin View Post
              Did you try to flash latest "MK802III Android 4.2 FW(131108)" from http://www.rikomagic.com/en/download/download_20_1.html? Did you try to erase IDB before flashing (I'm sure it was one button in RKBatchTool that does this)?
              ctually check other tools for "Erase IDB", it could be in ROM Flash Tool
              I tried Erase IDB with RKAndroidTool v.1.37: successful!
              Flashing the stock ROM (MK802III Recovery20130511) ends up with "Download IDB failed" again.
              Trying the latest "MK802III Android 4.2 FW(131108)" ends up with "Get FlashInfo Fail".

              Log of RKBatchTool with latest "MK802III Android 4.2 FW(131108)":
              Code:
              11:11:42 015    **********Restore Start Total<1>**********11:11:42 015    <Layer 1-1> Download Boot Start
11:11:44 682    <Layer 1-1> Download Boot Success
11:11:44 684    <Layer 1-1> Wait For Maskrom Start
11:11:45 224    <Layer 1-1> Wait For Maskrom Success
11:11:45 224    <Layer 1-1> Test Device Start
11:11:45 234    <Layer 1-1> Test Device Success
11:11:45 234    <Layer 1-1> Check Chip Start
11:11:45 234    <Layer 1-1> Check Chip Success
11:11:45 234    <Layer 1-1> Get FlashInfo Start
11:11:45 234    <LAYER 1-1> ERROR:GetFlashInfo-->RKU_ReadFlashInfo failed,pagesize or blocksize is zero
11:11:45 234    <Layer 1-1> Get FlashInfo Fail
11:11:45 244    **********Restore Done Success<0> Fail<1> Time<3229>ms**********
              Log of RKBatchTool with old stock ROM "MK802III Recovery20130511":
              Code:
              11:10:56 005    **********Restore Start Total<1>**********
11:10:56 005    <Layer 1-1> Download Boot Start
11:10:58 682    <Layer 1-1> Download Boot Success
11:10:58 682    <Layer 1-1> Wait For Maskrom Start
11:10:59 054    <Layer 1-1> Wait For Maskrom Success
11:10:59 054    <Layer 1-1> Test Device Start
11:10:59 054    <Layer 1-1> Test Device Success
11:10:59 054    <Layer 1-1> Check Chip Start
11:10:59 070    <Layer 1-1> Check Chip Success
11:10:59 070    <Layer 1-1> Get FlashInfo Start
11:10:59 070    <LAYER 1-1> INFO:FlashInfo: 0 0 0 1 0 4 8 0 32 0 1
11:10:59 070    <Layer 1-1> Get FlashInfo Success
11:10:59 070    <Layer 1-1> Prepare IDB Start
11:10:59 070    <LAYER 1-1> INFO:CS(1)        (8192MB)        (SAMSUNG)
11:10:59 179    <LAYER 1-1> INFO:FindBackupBuffer-->No Found Tag
11:10:59 179    <LAYER 1-1> INFO:FindBackupBuffer-->No Found Tag
11:10:59 179    <LAYER 1-1> INFO:FindBackupBuffer-->No Found Tag
11:10:59 195    <LAYER 1-1> INFO:FindBackupBuffer-->No Found Tag
11:10:59 195    <LAYER 1-1> INFO:FindBackupBuffer-->No Found Tag
11:10:59 195    <Layer 1-1> Prepare IDB Success
11:10:59 195    <Layer 1-1> Download IDB Start
11:10:59 210    <LAYER 1-1> ERROR:WriteIDBlock-->memcmp failed
11:10:59 226    <LAYER 1-1> ERROR:WriteIDBlock-->memcmp failed
11:10:59 257    <LAYER 1-1> ERROR:WriteIDBlock-->memcmp failed
11:10:59 257    <Layer 1-1> Download IDB Fail
11:10:59 351    <LAYER 1-1> INFO:BufferWriteBack-->Crc is zero
11:10:59 351    **********Restore Done Success<0> Fail<1> Time<3339>ms**********
              really really complicated...
              Attached Files

              Comment

                #8
                Originally posted by dmukhin View Post
                Actually check other tools for "Erase IDB", it could be in ROM Flash Tool
                Try a different pc and make sure you install all the drivers ......1 driver is to recognise your stick and the other driver is to patch your stick.
                try a pc with win xp on it. cheers hope it helps

                Comment

                  #9
                  Hello dartman22, thanks for your answer!
                  I tried to uninstall and reinstall all drivers on my Win 7 PC. I used the "DriverInstall.exe", which is in BatchTool 1.7 package. Same result as described above.

                  So i installed Win XP on an old HDD, after i finally found an installation cd...
                  I installed the drivers with DriverInstall.exe and tried to Restore again. No happiness, still the same result.

                  its really frustrating...

                  Comment

                    #10
                    Short pins 6-7 and change cables/ports used

                    I thought mine was bricked but then I read a comment by Finless saying "Rockchip devices are hard to permabrick" so I tried and tried almost for an entire day, having "IDB errors" and other s*it, and after all of that I finally found the problem: it seems that the flashing process, whether the device or the Flashing tools, are very sensitive about the USB ports and the cable used. I changed the one I was using for a better USB cable and chose a front port; it almost worked, flashing was almost 99%, then it failed. Then I tried again but it didn't want to work so I changed the port used, nothing, then I used USB3.0 and it finally completed the process. I had to short pins 6-7 first.


                    If you are using Win8.1 you have to go to devices manager and disable "PCI to USB Enhanced Host Controller", otherwise the device won't be recognized by the Flashing tools.

                    Comment

                      #11
                      I cannot find a hole anywhere. i thought the missing recovery button is the reason why we have to short pins to get into flash mode...
                      Your revision according to label is older than mine, seems recovery button added to later versions of the same model. But it doesn't matter, as we discussed above you already get to MaskROM. BTW: that button not always boot to MaskROM mode, this what I discovered, this is why shorting pins required in some cases

                      Your error seems to be because of broken flash or USB communication. I found micro USB slot on stick very sensible to any cable movements and it is getting worse with new flashings (because of slot disturbance). In this case cable length and quality could be very important and while device is detected and connected intensive data transfers could fail

                      Comment

                        #12
                        I have successfully un-bricked my MK802IIIS (Mediatek Wifi+BT) with shorting 6/7 pins.
                        I have found it here:
                        http://www.rikomagic.co.uk/forum/viewtopic.php?f=9&t=3300

                        Also this video was very helpful:
                        https://www.youtube.com/watch?v=t_SmDsWCsPo


                        I am struggling to find working ROM for it though:-(
                        I bricked it by flashing older Finless 1.7, which has Loader 1.16...most probably too old loader for MK802IIIS.

                        The only ROM that works for me so far, is the newest one downloaded from Rikomagic (S4_S8_131107), which is horrible and even do not show BT in the settings:-O

                        I tried other ROMs, like Finless 2.1 or KitKat, but none has working Wifi together with BT.

                        Comment

                          #13
                          Now I wonder how to root MK802 III. There's already rooted custom ROMs but they don't work good, I am using official last rom.

                          Comment

                            #14
                            It should be already rooted, just install SuperSU from Market

                            Comment

                              #15
                              Originally posted by dmukhin View Post
                              It should be already rooted, just install SuperSU from Market
                              Yes, it just needed SuperSU. I have the last ROM from Rikomagic but it' not stable. It got hot and crashed so I installed a little heatsink but still it got hot and crashed so I had to attach a cooler and then it worked stable and there were no more crashes. The thing now is that I was watching XBMC and it don'est play well 720p and 1080p videos with the default HW acceleration, so I've set SW decoding and then it played 720p video very well but it couldn't do it with 1080p.

                              Now I wonder how can I overclock it since it's locked to a maximum of 1.4GHz, maybe this way it can handle 1080p videos. Or maybe I can do achieve that by overclocking the GPU and turning back to HW decoding, I don't know.

                              Comment

                              Previous 1 2 template Next

                              What's Going On

                              Collapse

                              There are currently 2470 users online. 0 members and 2470 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