Unbrick or fix NAND on the MK808

[TheDuder5123]

ERROR: DeviceIoControl failed.

Hi,

Keep getting the following errors:

ERROR: DeviceIoControl failed. bRet=1,err=0,dwReturnByte=542,nSendBytes=12288,dwT otalSended=1241932
ERROR: Download USBData failed
ERROR: Download boot failed

help anyoune?

Thankyou.
TheDude.

[catalai]

Thanks!

Unbricked! Maybe the USB wire was the guilty of brick the MK808 while updating it.
Now, i used a good wire with antiparasitics.

[Finless]

Please I need a link to the tools

Download ANY of my MK808 ROMs and the flash tool and drivers are in the kit with instructions!


Bob

[asdkgh]

Please where can I get the tools?

Please I need a link to the tools

[norcal618]

You are the bomb finless!!

I am seriously thinking about starting up the finless fan club! lol. All joking aside I just want to say thank you so much for this fix! Im kinda of a tech savy guy but chances are I would have never come up with this on my own. I got my mk808 less than a week ago and my intentions for geting it were to have something inexpensive to tweek and hack on, so thats what ive been doing. I was trying some methods to get JB 4.2 running on my 808 but the only thing I suceeded at was severly bricking the little guy. Wouldn't turn on, wouldn't re-install any firmware wouldn't do anything other than raise my blood pressure.I have to tell you I thought my little android gadget that ive grown to love so quickly was done for good! So I came accross your little trick and it certainly saved the day. It also saved me 65 bucks that I would have spent on another if this one was dead. Not to mention the month or two it takes to get to the USA from China. Thanks Finless Bob!

[asdkgh]

Rom Flash tool

Where can I find this rom flash tool?

Can you please provide a link?

Does this involve the drivers?

Thanks

[roman2025]

It rebooted to flash mode because it could not load recovery.img. So that was a bad flash. YES erase IDB always when trying to recovery from a brick.

Bob

I am starting to think my supplier screwed up and sent me one unit using the older PCBA motherboard (idiots). That is really the only explanation for the really odd behaviour.

-Roman

[Finless]

It rebooted to flash mode because it could not load recovery.img. So that was a bad flash. YES erase IDB always when trying to recovery from a brick.

Bob

[roman2025]

I do not know if the RKbatch tool can be used in this way. The RK Android tool can. It has to say MASK rom mode at the bottom when you do the pin short thing. If you have drivers installed for RKBatch tool then RKAndroid tool should also work as it is the same drivers.

Bob

There is no option to clear IDB in RKbatch, however RKBatch does recognize the MK808 in this mode as it gives a "blue" square instead of the green (firmware update mode), flashing yellow (update in process), red (failure), or purple (device powered on and android booted and connected to USB mode). So it definitely sees this mode as something different. It allows you to start a firmware update process....

Now onto the next ridiculous hurdle. I have 4 M3 tablets here and 1 of them absolutely refuses to go into firmware update mode . Meh... Going to try you tool to see if it can reboot the device.

Regards,

Roman


UPDATE: THANKS THANKS AND THANKS! The older flash tool you use actually got this bloody device to go into firmware update mode. The other 3 M3's I had worked with no problem using the button combination but I had this one unit that just absolutely wouldn't do it. Your "reboot to flash mode" button really saved my hide .

UPDATE 2: Meh... it flashed normally and THEN once it was done, it refused to reboot. Now it appears to be totally dead. This is so odd, I have never had any rk3066 device give me problems like this until this M3.... sigh....

UPDATE 3: Apparently it was still in firmware update mode (this is getting odder and odder) as I just plugged it back in and it was recognized in both tools. I am attempting to flash again. Perhaps I will need to use the "upgrade option again in the one tool or maybe erase the IDB first?

Regards,

Roman

[Finless]

I do not know if the RKbatch tool can be used in this way. The RK Android tool can. It has to say MASK rom mode at the bottom when you do the pin short thing. If you have drivers installed for RKBatch tool then RKAndroid tool should also work as it is the same drivers.

Bob

[roman2025]

ugh...

EDIT: OKAY... SO, here is what I have done that I "think" may have fixed it as it appears to be flashing now... I went into the NEW Rockbatch tool and used the "upgrade" option to flash. It appears to be flashing normally now. Will know in a few minutes...

EDIT2: Helpful tip... I did this with the Heatsink ON as I really didn't feel like making a trip to Radio Shack for heat-sink tape. It was tricking to see though and I was using a needle that is reflective making it even MORE tricking to see. Here is an easy way to figure out where to stick your pin, if you notice in the close up picture, look at the line of copper going around the outside... there is a small "box" outcropping (in cropping?) protruding in towards the NAND chip. If you put your pin straight on and slightly to the left of that you will hit between pins 8 & 9 every time.

Get all the way through the steps, erase the IDB, but when i go to flash a new rom it fails to download the IDB...?

Not sure why?

If I leave the pin in place the whole time it will fail. If I take the pin out before flashing then it just hangs on "start to download IDB" ?

Any idea? I wasn't sure how long to keep the pin in place.

Thanks for your help and kind regards,

Roman

PSS I have tried different USB ports per the other posters comments... still not going...


BTW - Big thanks! Where else in the world would anyone find this information?!

[Finless]

Yes the BathTool also recogonizes MASK ROM mode. The box in the batctool is a different color than green in that mode.. As I recall it is red.

Bob

[mikewolf]

thank you

i had the original firmware and read about your rom that was excellent and decided to flash it, but the 1.5a bricked my device after first reboot (i suppose that this thing is related to the liberation of new space for apps in the nand), i tried to do A LOT of things but it seems that despite mostly in all the times, all those firmware flashed fine, when i booted the device went crazy and stop working and do a lot of crazy things... so after this new method my device was fixed, for that THANK YOU!, now... i dont want that this happen again so.. do you advice me that from now i will stick with your firmware updates and use your tool instead of the rockchip batch tools and their firmwares? because the normal rockchip firmwares has a different file system that might corrupt the filesystem that 1.5a creates (i believe)...

and could i flash my nand by the mask rom method and after of this could flash with the rockchip batch tool?

thank you

[qq7119]

I think all of us appreciate your efforts and work.

[E_Zatopek]

Errorownload IDB failed

EDIT: Issue resolved - Plugging the device into another USB port at my PC turned the trick. Flashing the new ROM then worked like a charm at first try.

Hi Bob,

thank you very much for providing instructions on how to unbrick the MK808.

Unfortunately, they don't seem to work for me - at least not completely. I keep getting error messages
Error: Download IDB failed
ERROR: Run failed

I have opened the box, have short-circuited pins 8 and 9 of the NAND chip, then connected the box to the PC using the OTG port.
Your ROM Flash Tool detects the MK808 in Mask ROM mode and Erase NAND works fine. It's flashing the ROM that fails for me.

Output in the status window reads like this:
INFO: Start to erase NAND
INFO: Erasing IDB OK
INFO: Start to run
INFO: Start to download boot
INFO: Download boot OK
INFO: Start to test device
INFO: Test device OK
INFO: Start to download IDB
Error: Download IDB failed
ERROR: Run failed

I'm attaching the log file for more detail.

I'd appreciate if you could take a look and provide some guidance. For how long is the short-circuit supposed to be maintained? Just until the driver has loaded and the Flash Tool has detected the device or throughout the NAND erase process or through the complete Flash process?

Thank you very much.
E_Zatopek