Unbrick or fix NAND on the MK808

[fratello]

New ideea : You used "ROM Flash tool" (or "RKBastchTool.exe") as admin ?!?

[periandros]

Thanks for your help.

I think all of us appreciate your efforts and work.

Jose Ignacio.

As Jose said, once again thanx....

[elezeta]

Tnx, but I tried everything... Changed three cables and four PC, and always I got same result: "Download boot fail" or "Erasing IDB failed". I give up

Same here. I bought it from DX and was dead from the beginning. I did everything I found and nothing. I guess I had bad luck. Not sure if I would take the chance to order another one even if it looks one of the best out there.

Thanks much to Finless though.

[dabadon]

Tnx, but I tried everything... Changed three cables and four PC, and always I got same result: "Download boot fail" or "Erasing IDB failed". I give up

[fratello]

Try harder ! Did you changed the cable ? Did you verified the solders of USB (OTG) port ?

[dabadon]

I think the device is dead!

[dabadon]

Maybe DX made mistake... I ordered MK808! I will try with ROM for MK808 B.

[fratello]

Maybe your device is different ?! (MK808 B)

[dabadon]

I tried this method without success . Application and PC recognize the device, but still doesn't work. You can see log: Log2013-01-09.txt

[fratello]

I suggest to use :
- RKBatchTool 1.5
- original FW.
For both, use this link : http://blog.geekbuying.com/index.php...mware-release/
Use "Restore" button !
If you succeed in this way, you can after that re-flashing with any ROM (I recommend Mr.Finless version, of course - It's better ! )
Regards !

[dabadon]

Mr.Finless say :
"Notes:
If you got errors using the PC flash tool, then you have some kind of USB problem.
Some things to check:
1) Make sure you connect to a real USB port from the PC. NOT a USB hub or maybe even front panel USB ports!
2) Some older BIOS have a setting called "high speed USB". You may have to go into the BIOS and turn that off.
That was a crappy implementation of USB 3.0 that is not reliable.
3) Try connecting to USB 2.0 ports instead of 3.0 if you have them.
4) Try unplugging any other USB devices like removable disks, hubs, media readers, etc.
5) All else fails, try another PC."
Change the USB cable too ...
Good luck !

Really appreciate that you're trying help us to recover devices.


I've tried all of the above. I even changed 4 PC and the situation is the same. Is there another way to erase NAND? I mean, if I wipe data from it, it will be easy to install another ROM.

[fratello]

Mr.Finless say :
"Notes:
If you got errors using the PC flash tool, then you have some kind of USB problem.
Some things to check:
1) Make sure you connect to a real USB port from the PC. NOT a USB hub or maybe even front panel USB ports!
2) Some older BIOS have a setting called "high speed USB". You may have to go into the BIOS and turn that off.
That was a crappy implementation of USB 3.0 that is not reliable.
3) Try connecting to USB 2.0 ports instead of 3.0 if you have them.
4) Try unplugging any other USB devices like removable disks, hubs, media readers, etc.
5) All else fails, try another PC."
Change the USB cable too ...
Good luck !

[dabadon]

Hi everybody!

I bought two weeks ago mk808, and after a few days it stopped working. I read almost all the posts and threads but I did not solve the problem. I installed drivers, start the program, shorted pins 8/9, and Finless ROM Flesh Tool changed to "Found RKAndroid MaskRom Rock Usb" but when I pressed any button ("Reboot to flash Mode" I got "Device can not do Flash Mode,because it is not msc device."); (Erase NAND (IDB) -> Erasing IDB failed); In attached the printscreens and log file.

Please, can anyone give me a suggestion to try something else or to give up mk808?Log2013-01-08.txt

[fratello]

Just one (new) advice ... http://www.armtvtech.com/armtvtechfo...php?f=13&t=965
Good luck !

[mpekv]

Hi again,

here I am after few days of tryouts to unbricking my mk808. I tried 4 different USB cables, in total 16 USB ports on 2 PC-s, every combination, but still without success.

Furthermore, I investigated a little and find tool rkflashtool for linux which can read and write flash memory for specified locations. I tried this tool to read my memory, and every times it gives me all zeros. If I try to write back to flash nothing is written.

I tried to write parameters, boot.img, system.img, recovery.img with offset and sizes specified for rk3066, but nothing will be written.

With this situation I am pretty sure that my device is not bricked, but tottaly dead :-(

Am I wrong in something, or it still can be saved?