Unbrick or fix NAND on the MK808

[mrigi]

I am running that linux tool now (rkflashtool). It completes all reads, writes and reboots without throwing errors. But any block it reads is filled with zeros. Even if I write something to that block first. So I assume it doesn't really reads/writes anything. Tool simply doesn't checks device response and sends commands blindly.

[petrus]

I imagined it would be like that (in part by looking at RK batch tool logs). The 'hope' is in the 'low-level' part, I guess...
Did you have this problem (MK808 in coma)? If yes, did you tried the windows tools?
Is it too much to ask for pointers on setting up the tool and using it in general (and in particular, on this "recovery" context)?

Thank you in advance!

Sorry, I only have an arnova 10G2 tablet (with a RK29 board) so I won't be really helpful on this particular issue.
Just wanted to share my experience with the linux tool, and explain what it can and cannot do.

If you want a lot of information about rockchip roms, you can look here : http://www.freaktab.com/showthread.p...cks-by-Finless

About setting up the tool and using it, i'll look at what I have and let you know

Edit : in fact, I don't have much more to say than what is on the xda thread. It says how to get the sources, how to compile it, and how to use it.

[l0ur3nz0]

[...]

The linux tool, again is a more low-level command line tool, but basically does exactly the same things the windows tool does, to flash the images.

I imagined it would be like that (in part by looking at RK batch tool logs). The 'hope' is in the 'low-level' part, I guess...
Did you have this problem (MK808 in coma)? If yes, did you tried the windows tools?
Is it too much to ask for pointers on setting up the tool and using it in general (and in particular, on this "recovery" context)?

Thank you in advance!

[petrus]

Has anyone tested this linux tool? (it seems a previous user already posted he did)

http://forum.xda-developers.com/showthread.php?t=1286305

It is quite "old" but it is said somewhere that RK30(66) is also supported with some tweaking.

@finlessbob: could you give pointers on this? At least the writing addresses and sizes for all the stuff needed to be flashed? Or, if possible, at least the one (file, writing address and size) needed for the device to boot again?

Right now i'm overloading with work to investigate and test this shortly...

EDIT:

More info on RKFlash and RK30 platform:
http://valentijn.sessink.nl/?p=382

About linux rkflashtool I'm using it on a regular basis. It is in fact a bit more low level as the tools on windows, as you can only flash an image at a time (like system.img, boot.img, kernel.img)
It's a great tool. But you won't be able to do anything the windows tool can't do.

Something to notice too : rkflashtool doesn't have a "check" option built in. Let me explain ; the windows tool flashes then checks the flashed image. Anyway, you can easily script it with the rkflashtool, by reading (with the r command) what you just wrote (with the w command), and compare the checksums.

The linux tool, again is a more low-level command line tool, but basically does exactly the same things the windows tool does, to flash the images.

[l0ur3nz0]

RKflashTOOL

Has anyone tested this linux tool? (it seems a previous user already posted he did)

http://forum.xda-developers.com/showthread.php?t=1286305

It is quite "old" but it is said somewhere that RK30(66) is also supported with some tweaking.

@finlessbob: could you give pointers on this? At least the writing addresses and sizes for all the stuff needed to be flashed? Or, if possible, at least the one (file, writing address and size) needed for the device to boot again?

Right now i'm overloading with work to investigate and test this shortly...

EDIT:

More info on RKFlash and RK30 platform:

http://valentijn.sessink.nl/?p=382

[snakekiller]

Re: NEW - Unbrick or fix NAND on the MK808

i read somewhere from bob its maybe a locked bootloader.
si for safety always uncheck bootloader in the flashtool.
he is working on it.

Verstuurd van mijn GT-S5660 met Tapatalk

[mrigi]

Finless, we need your help.
Most of us having the same issue and even golden-plated USB cables do not help.
Bring us some more ideas please!

[l0ur3nz0]

"Erasing IDB failed!"

I've been lurking here for a while... mainly to get advice on which device is (would be) better - settled for an MK808.

Finally my MK808 arrived this Tuesday. I have tried the original firmware for the first couple days to see how it was (not bad - expected worse). Then flashed finless 1.6 and the problems started: Lots of hangs and crashes. (I not saying it is 1.6 fault though)

Today it finally stopped working. There's no other way to get it recognized but shorting 8-9 pins.

I'm getting these messages in logs (tried erase and also flash):

00:48:29 581 Load Setting ok
00:48:30 409 Finless ROM Flash Tool - RKAndroidTool v1.3.5.0 Start Run
00:48:30 409 Scan thread:4980
00:48:30 409 Info: (thread=5900)IoControlProc-->DeviceIoControl In
00:48:30 424 Info: (thread=5900)IoControlProc-->DeviceIoControl Out,ret=1,err=183
00:48:30 424 ProcessID: 284,ThreadID:720,RefCount:0
00:48:33 269 ProcessID: 284,ThreadID:4980,RefCount:0
00:48:33 285 ProcessID: 284,ThreadID:5900,RefCount:0
00:48:37 411 INFO: Start to erase NAND
00:48:42 692 INFO: Download USBData OK
00:48:47 755 ERROR: DeviceIoControl failed. bRet=1,err=0,dwReturnByte=4096,nSendBytes=0,dwTota lSended=1635076
00:48:47 755 ERROR: Download USBBoot failed
00:48:47 755 ERROR: Download boot failed
00:49:30 975 Info: wait for exiting scan thread start
00:49:31 022 Info: wait for exiting main thread start
00:49:31 022 ProcessID: 284,ThreadID:720,RefCount:0
00:54:14 425 Load Setting ok
00:54:14 503 Finless ROM Flash Tool - RKAndroidTool v1.3.5.0 Start Run
00:54:14 519 Scan thread:4140
00:54:14 535 ProcessID: 2064,ThreadID:4084,RefCount:0
00:54:14 535 ProcessID: 2064,ThreadID:4140,RefCount:0
00:54:14 550 Info: (thread=4128)IoControlProc-->DeviceIoControl In
00:54:14 550 Info: (thread=4128)IoControlProc-->DeviceIoControl Out,ret=1,err=183
00:54:15 941 INFO: Start to erase NAND
00:54:21 020 ERROR: DeviceIoControl failed. bRet=1,err=0,dwReturnByte=4096,nSendBytes=0,dwTota lSended=1635076
00:54:21 020 ERROR: Download USBData failed
00:54:21 020 ERROR: Download boot failed
00:54:23 956 MaskRom Device Path(\\?\USB#VID_2207&PID_300A#5&1A915965&0&1#{a5d cbf10-6530-11d2-901f-00c04fb951ed}),threadID=2824
00:54:23 956 INFO: Start to run
00:54:23 971 INFO: Start to download boot
00:54:29 034 ERROR: DeviceIoControl failed. bRet=1,err=0,dwReturnByte=4096,nSendBytes=0,dwTota lSended=1634496
00:54:29 034 ERROR: Download USBData failed
00:54:29 034 Error: Download boot failed
00:54:29 034 ERROR: MaskRomThread failed
00:54:29 049 ERROR: Run failed
00:54:51 341 Info: wait for exiting scan thread start
00:54:51 607 Info: wait for exiting main thread start
00:54:51 639 ProcessID: 2064,ThreadID:4084,RefCount:0

Also tried official tool:

00:49:55 976 Rockchip Batch Tool v1.5.3.0 start run
00:50:13 447 **********Upgrade Start Total<1>**********
00:50:13 447 <Layer 4-1> Download Boot Start
00:50:18 527 <LAYER 4-1> ERROR:Boot_VendorRequest-->DeviceIoControl failed,Total(12390),Sended(0),bRet(1),err(0)
00:50:18 527 <LAYER 4-1> ERRORownloadBoot-->Boot_VendorRequest471 failed,index(0)
00:50:18 527 <Layer 4-1> Download Boot Fail
00:50:18 527 **********Upgrade Done Success<0> Fail<1> Time<5079>ms**********

Tried 4 USB cables, 3 laptops + 1 desktop (win7x64+winxppro+win7x32) might not have made all the combinations, though.

I'm lost. You still think it is a USB communication problem?

[blastif]

I did all things from this topic, but when Im flashing device, program gives me error "Download IDB failed". Any idea how to fix this ? Please help.
Log: http://pastebin.com/85gE6LJm

My log says:

13:29:59 562 Load Setting ok
13:29:59 593 Finless ROM Flash Tool - RKAndroidTool v1.3.5.0 Start Run
13:29:59 593 Scan thread:1340
13:29:59 593 Infothread=1488)IoControlProc-->DeviceIoControl In
13:29:59 593 Infothread=1488)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:29:59 593 Infothread=1928)IoControlProc-->DeviceIoControl In
13:29:59 593 Infothread=1928)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:29:59 593 ProcessID:1292,ThreadID:3876,RefCount:0
13:29:59 593 ProcessID:1292,ThreadID:1340,RefCount:0
13:29:59 609 Infothread=2320)IoControlProc-->DeviceIoControl In
13:29:59 609 Infothread=2320)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:29:59 609 Infothread=168)IoControlProc-->DeviceIoControl In
13:29:59 609 Infothread=168)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:30:02 593 INFO:Start to erase NAND
13:30:07 687 ERROR: DeviceIoControl failed. bRet=1,err=0,dwReturnByte=4096,nSendBytes=0,dwTota lSended=1241932
13:30:07 687 ERRORownload USBData failed
13:30:07 687 ERRORownload boot failed
13:30:11 687 Info:wait for exiting scan thread start
13:30:11 890 Info:wait for exiting main thread start
13:30:11 890 ProcessID:1292,ThreadID:3876,RefCount:0

Just to confirm:
Does this log mean that my NAND is damaged too?

[jamslodki]

Theres no chance for repair it ? When I run it first, I saw android loading logo for long time. I decided to reset device and it never run again :c

[Finless]

I think your other device has a bad NAND chip. A user here sent me a UG802 clone with the same problem. It cannot write low level NAND so it is bad.

Bob

[jamslodki]

I did it and again same error. I have 2 devices. One of them work and I flashed on it new ROM without problems.

[fratello]

Try to uninstall, then re-install RK drivers ...

[jamslodki]

I did all things from this topic, but when Im flashing device, program gives me error "Download IDB failed". Any idea how to fix this ? Please help.
Log: http://pastebin.com/85gE6LJm

[mrigi]

Getting the same issue as others in "MaskRom" mode.
Here is the log:

04:10:31 554 Finless ROM Flash Tool - RKAndroidTool v1.3.5.0 Start Run
04:10:31 555 Scan thread:5528
04:10:31 557 Infothread=5620)IoControlProc-->DeviceIoControl In
04:10:31 559 Infothread=5620)IoControlProc-->DeviceIoControl Out,ret=1,err=183
04:10:31 561 Infothread=2396)IoControlProc-->DeviceIoControl In
04:10:31 562 Infothread=2396)IoControlProc-->DeviceIoControl Out,ret=1,err=183
04:10:31 564 ProcessID:4584,ThreadID:6100,RefCount:0
04:10:31 566 ProcessID:4584,ThreadID:5528,RefCount:0
04:10:31 568 ProcessID:4584,ThreadID:5620,RefCount:0
04:10:31 576 Infothread=5600)IoControlProc-->DeviceIoControl In
04:10:31 578 Infothread=5600)IoControlProc-->DeviceIoControl Out,ret=1,err=183
04:10:31 584 Infothread=7084)IoControlProc-->DeviceIoControl In
04:10:31 679 Infothread=7084)IoControlProc-->DeviceIoControl Out,ret=1,err=183
04:10:31 682 Infothread=2672)IoControlProc-->DeviceIoControl In
04:10:31 685 Infothread=2672)IoControlProc-->DeviceIoControl Out,ret=1,err=183
04:11:28 051 INFO:Start to erase NAND
04:11:33 109 ERROR: DeviceIoControl failed. bRet=1,err=0,dwReturnByte=4096,nSendBytes=0,dwTota lSended=1635076
04:11:33 112 ERRORownload USBData failed
04:11:33 116 ERRORownload boot failed