Unbrick or fix NAND on the MK808

[mrigi]

I think it's verry important to see what model of NAND do you have ... Maybe it's a different model than "usual" and someone can figure out how to proper erase !

I took away the heatsink and here is the chip info:
Line 1: SanDisk
Line 2: P224071991
Line 3: SDTNQGAMA-008G
Line 4: WAC5140066
Line 5: TAIWAN

[fratello]

My oppinion : the NAND chip (H5TQ2G83BFR , 96 Ball Fine Pitch Ball Grid Array) don't allow access to any pins (for "hardware" reset ...) so the only way to unbrick it's software method ! Maybe the way to "access" this NAND it's different ...and the tool software need to be "updated" .

[mrigi]

My oppinion : the NAND chip (H5TQ2G83BFR , 96 Ball Fine Pitch Ball Grid Array)

As I understand H5TQ2G83BFR is not a NAND chip. It is a DDR3 one. No need to fix RAM. The NAND must be SandDisk one.

[fratello]

Yes, you have right ...sorry, I looked to the wrong IC !

[l0ur3nz0]

So, tried linux, result not good, as expected:

$:~/Desktop/RKflash$ sudo ./rkflashtool b
rkflashtool: info: interface claimed
libusb:warning [do_sync_bulk_transfer] unrecognised status code 1
libusb:warning [do_sync_bulk_transfer] unrecognised status code 1
rkflashtool: info: rebooting device...
libusb:warning [do_sync_bulk_transfer] unrecognised status code 1
libusb:warning [do_sync_bulk_transfer] unrecognised status code 1

When reading I only get 0s (i.e., nothing is read).

I was going to try OS X but can't afford to install XCODE...

[MaVe_64]

Re: NEW - Unbrick or fix NAND on the MK808

Yaay! Good news! I never tried the pin 8+9 short method because I thought it only was for getting into mask mode. And mine started in mask mode. But I did the pin 8+9 short, applied USB, and in some way the nand reset himself, and flash worked! I have a working system again!
So everyone with bricked devices do the pin 8+9 short method. Make sure you are really making good contact, took me a couple of times till it worked.

[mrigi]

So everyone with bricked devices do the pin 8+9 short method. Make sure you are really making good contact, took me a couple of times till it worked.

So you kept pins short during whole erase+flash period?

[MaVe_64]

Re: NEW - Unbrick or fix NAND on the MK808

So you kept pins short during whole erase+flash period?

No only when plugging in usb, wait a few secs, then the Nand resets, then try to flash.

[mrigi]

No only when plugging in usb, wait a few secs, then the Nand resets, then try to flash.

Tried like 100 times. Doesn't works. Device appears but doesn't allow to r/w.

[l0ur3nz0]

Tried like 100 times. Doesn't works. Device appears but doesn't allow to r/w.

X2!

[diniscampos]

Last night I tried with my stick but with no success...


I opened the stick and I did this:
1) Start up my ROM flash tool from my ROM kit. NOTE: you must already have the drivers installed etc or this WILL NOT WORK! Here I used the software recomended by Apad.tv , GV-20 Rockchip Reflash Tool 1.5.zip with update_GV20_204j1.zip
2) Hook up the USB cable to the OTG port of the MK808. Its the side port not the rear port.
3) Look between the heatsink and the board and you can see all the pins of the NAND chip. Again pin 1 is at the top. Count down to pins 8 & 9.
4) With a needle or a pin put the pin between pins 8 and 9 and hold it there. You are trying to short these 2 pins so make sure your actually on them.
5) No plug in the USB cable to your PC to power on the unit.
6) If you are shorting the pins the PC should bong and the flash tool should say at the bottom "Found RKAndroid MaskRom Rock USB". If not, then your not shorting the pins properly OR you never had the drivers loaded to begin with.
7) Good! If you have MASK ROM mode then now erase NAND (IDB). Let it finish.
8) Flash the ROM. YOu must have the loader check box checked or it will complain and tell you a loader must be flashed.


Thats it! You should be unbricked and hopefully your ROM flash problems should be gone. If not, you can try to repeat the proceedure but if you still have issues, alas, you may have a failed NAND chip.


This was my operation LOG... everything went OK but the stick still dead....
Loading firmware...
Loading firmware Finished.
Loading firmware...
Loading firmware Finished.
**********Restore Action**********
**********Restore Start Total<1>**********
<Layer 5-8> Download Boot Start
<Layer 5-8> Download Boot Success
<Layer 5-8> Wait For Maskrom Start
<Layer 5-8> Wait For Maskrom Success
<Layer 5-8> Test Device Start
<Layer 5-8> Test Device Success
<Layer 5-8> Check Chip Start
<Layer 5-8> Check Chip Success
<Layer 5-8> Get FlashInfo Start
<Layer 5-8> Get FlashInfo Success
<Layer 5-8> Prepare IDB Start
<Layer 5-8> Prepare IDB Success
<Layer 5-8> Download IDB Start
<Layer 5-8> Download IDB Success
<Layer 5-8> Reset Device Start
<Layer 5-8> Reset Device Success
<Layer 5-8> Wait For Loader Start
<Layer 5-8> Wait For Loader Success
<Layer 5-8> Test Device Start
<Layer 5-8> Test Device Success
<Layer 5-8> Lowerformat Device Start
<Layer 5-8> Lowerformat Device Success
<Layer 5-8> Test Device Start
<Layer 5-8> Test Device Success
<Layer 5-8> Check Chip Start
<Layer 5-8> Check Chip Success
<Layer 5-8> Get FlashInfo Start
<Layer 5-8> Get FlashInfo Success
<Layer 5-8> Prepare IDB Start
<Layer 5-8> Prepare IDB Success
<Layer 5-8> Download IDB Start
<Layer 5-8> Download IDB Success
<Layer 5-8> Reset Device Start
<Layer 5-8> Reset Device Success
<Layer 5-8> Wait For Loader Start
<Layer 5-8> Wait For Loader Success
<Layer 5-8> Test Device Start
<Layer 5-8> Test Device Success
<Layer 5-8> Download Firmware Start
<Layer 5-8> Download Firmware Success
<Layer 5-8> Reset Device Start
<Layer 5-8> Reset Device Success
**********Restore Done Success<1> Fail<0> Time<137188>ms**********
Everything - Success. Result - Still dead


Now I thing this message applies to GV-20:
http://www.freaktab.com/showthread.p...ers-showing-up!


I bought this stick because the vendor site gadgetgreats.com says in "Primal GV-20 Mini PC - Android 4.1 Dongle Stick Description:" : Primal ensures the quality of each dongle stick as Primal stringently tests each unit before shipping. In addition, there will be a custom Primal GV-20 compatible ROM released shortly. Later firmware uprades will be free to Primal customers.


I could buy "MINIPC ANDROID 4.1.1 DUAL CORE RK3066 1GB+4GB (UG802)" at my country (Portugal) buy I decided to by GV-20 directly from China because High expectations...Now I'm sorry about that.


Tonight I'll try another solutions, but no hope.
I think I will have to buy another stick, but now from a seller that cares about his product.


Dinis Campos
Portugal

[l0ur3nz0]

Your problem seems different try flashing: a custom rom. But, beware of the (possible) locked bootloader issue in clone units.

[diniscampos]

My mistake was flashed the rom with Finless 1.5 Custom ROM

All the process went with no errors, but the stick did not boot anymore....

[l0ur3nz0]

did you use finless flash tool or apadtv's tool? if you didn't use finless' tool it might be your problem...

[diniscampos]

I used finless flash tool and all the process went with no errors...

I'm trying several ROM's and tools with the same result... always OK but the stick remains with no response.

My big problem is identify GV-20 type of stick....there are a lot of different types...clones of clones...fake clones etc...
This tv stick world is an anarchy....