Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Unbrick or fix NAND on the MK808

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #76
    Originally posted by l0ur3nz0 View Post
    Has anyone tested this linux tool? (it seems a previous user already posted he did)


    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.

    Comment


      #77
      Originally posted by petrus View Post
      [...]

      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!

      Comment


        #78
        Originally posted by l0ur3nz0 View Post
        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.

        Comment


          #79
          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.

          Comment


            #80
            Originally posted by mrigi View Post
            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.
            Did you configure it correctly by adding RK30 PID to the source code?

            Comment


              #81
              Originally posted by l0ur3nz0 View Post
              Did you configure it correctly by adding RK30 PID to the source code?
              I took the version with RK30 already added.
              Here is the repository: https://github.com/fldc/arnova-tools.git

              Comment


                #82
                This is getting ridiculous - two more PCs (Notebook+desktop) and nothing!

                Comment


                  #83
                  Flashing fail

                  I have flashed my mk808 a couple of times allways with success. Now it fails. The tool says "Found RKAndroid MaskRom Rock USB" but when flashing it says "Error: Download IDB failed". If I erase NAND that goes without error. In the log it says:

                  INFO:Start to erase NAND
                  08:15:06 573 INFOownload USBData OK
                  08:15:07 748 INFOownload USBBoot OK
                  08:15:10 630 Flash(0) - Erasing: 00000000 ~ 00000049 ...
                  08:15:10 635 Good block
                  08:15:10 639 INFO:Erasing IDB OK
                  08:15:14 547 MaskRom Device Path(\\?\USB#VID_2207&PID_300A#6&114B00B3&0&3#{a5d cbf10-6530-11d2-901f-00c04fb951ed}),threadID=7384
                  08:15:14 551 INFO:Start to run
                  08:15:14 577 INFO:Start to download boot
                  08:15:15 113 INFOownload USBData OK
                  08:15:16 291 INFOownload USBBoot OK
                  08:15:16 296 INFOownload boot OK
                  08:15:18 301 INFO:Start to test device
                  08:15:18 307 INFO:Test device OK
                  08:15:18 312 INFO:Start to download IDB
                  08:15:18 317 Flash Chip Information:
                  08:15:18 321 NO SIZE(MB) Manufacturer
                  08:15:18 326 ----------------------------------------------
                  08:15:18 330 ----------------------------------------------
                  08:15:18 334 ERROR: No Found 1th chip
                  08:15:18 339 Errorownload IDB failed
                  08:15:18 345 ERROR:MaskRomThread failed
                  08:15:18 349 ERROR:Run failed

                  "No Found 1th chip", does someone know what that problem is? Tried it on multiple PC's, all the same.

                  PLEASE HELP!

                  Comment


                    #84
                    Originally posted by MaVe_64 View Post
                    I have flashed my mk808 a couple of times allways with success. Now it fails. The tool says "Found RKAndroid MaskRom Rock USB" but when flashing it says "Error: Download IDB failed". If I erase NAND that goes without error. In the log it says:

                    [...]

                    "No Found 1th chip", does someone know what that problem is? Tried it on multiple PC's, all the same.

                    PLEASE HELP!
                    Your case seems a bit different. I recommend you to try the official flash tool; in mask mode you should get a "Blue box"; try the "RESTORE" option with an official firmware/ROM loaded.

                    Please give more info regarding your setup (PC/USB PORTS/CABLES/...); if you try the official tool post the log here.
                    -------------
                    Yesterday I've tried another notebook. Same daunting results.

                    It's weird but in the logs that came with the official tool (latest firmware) we can see that they usually get a usb layer of <1-1> (usb: <hub-port>, it seems). I can never get that arrangement! Not even by plugging directly to the back USB ports of a desktop PC.

                    I'm using branded USB cables (SONY/CANON/LG/...)

                    Comment


                      #85
                      Thanks l0ur3nz0,

                      I'm using 2 PC's, 1 XP and 1 Windows 7, used multiple cables, mk808 OTG directly to USB port on back of PC. As I said, configuration used to work fine. First time I flashed only the new kernel from Kizs v4, all good, then days later I flashed Finless 1.6 (2 times, all good) and this time same flash fails.
                      So I did a succesfull full flash (everything ticked exept backup.img) 2 times, this is the 3rd time.

                      I also tried with the official tool, I get blue box. I get this log, first Restore and then Upgrade:

                      08:15:53 545 Rockchip Batch Tool v1.5.3.0 start run
                      08:17:10 944 **********Restore Start Total<1>**********
                      08:17:10 949 <Layer 2-1-3> Download Boot Start
                      08:17:13 753 <Layer 2-1-3> Download Boot Success
                      08:17:13 758 <Layer 2-1-3> Wait For Maskrom Start
                      08:17:14 269 <Layer 2-1-3> Wait For Maskrom Success
                      08:17:14 273 <Layer 2-1-3> Test Device Start
                      08:17:14 278 <Layer 2-1-3> Test Device Success
                      08:17:14 283 <Layer 2-1-3> Check Chip Start
                      08:17:14 289 <Layer 2-1-3> Check Chip Success
                      08:17:14 294 <Layer 2-1-3> Get FlashInfo Start
                      08:17:14 298 <LAYER 2-1-3> INFO:FlashInfo: 0 0 0 0 80 0 2 0 32 0 0
                      08:17:14 303 <Layer 2-1-3> Get FlashInfo Success
                      08:17:14 308 <Layer 2-1-3> Prepare IDB Start
                      08:17:14 312 <LAYER 2-1-3> ERROR:PrepareIDB-->No Found 1st Flash CS
                      08:17:14 317 <Layer 2-1-3> Prepare IDB Fail
                      08:17:14 322 **********Restore Done Success<0> Fail<1> Time<3370>ms**********

                      08:18:12 872 **********Upgrade Start Total<1>**********
                      08:18:12 879 <Layer 2-1-3> Download Boot Start
                      08:18:14 817 <Layer 2-1-3> Download Boot Success
                      08:18:14 823 <Layer 2-1-3> Wait For Maskrom Start
                      08:18:15 316 <Layer 2-1-3> Wait For Maskrom Success
                      08:18:15 322 <Layer 2-1-3> Test Device Start
                      08:18:15 328 <Layer 2-1-3> Test Device Success
                      08:18:15 335 <Layer 2-1-3> Check Chip Start
                      08:18:15 345 <Layer 2-1-3> Check Chip Success
                      08:18:15 352 <Layer 2-1-3> Get FlashInfo Start
                      08:18:15 357 <LAYER 2-1-3> INFO:FlashInfo: 0 0 0 0 80 0 2 0 32 0 0
                      08:18:15 362 <Layer 2-1-3> Get FlashInfo Success
                      08:18:15 368 <Layer 2-1-3> Prepare IDB Start
                      08:18:15 375 <LAYER 2-1-3> ERROR:PrepareIDB-->No Found 1st Flash CS
                      08:18:15 380 <Layer 2-1-3> Prepare IDB Fail
                      08:18:15 386 **********Upgrade Done Success<0> Fail<1> Time<2511>ms**********

                      Comment


                        #86
                        see if the tips here help:

                        Comment


                          #87
                          Re: NEW - Unbrick or fix NAND on the MK808

                          Thanks. Tried again and again, I guess 1000 times. Not as lucky as the other guy.

                          Comment


                            #88
                            :'(

                            If I have time I'll try the linux tool this weekend (maybe you can too).
                            Also, I have another PC disassembled in parts that I might assemble JUST to try this.

                            Comment


                              #89
                              Originally posted by l0ur3nz0 View Post
                              :'(

                              If I have time I'll try the linux tool this weekend (maybe you can too).
                              Also, I have another PC disassembled in parts that I might assemble JUST to try this.
                              That would be great. If only it was possible to just ram the correct bytes into the NAND....

                              Comment


                                #90
                                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 !

                                Comment

                                Working...
                                X