New CX-919 owner. Error after reset while flashing ROM.

[Com3ToDaddy]

I can't figure our what I need to do to get past this. I am connecting the device by holding down the function button then plugging in the USB. Windows recognizes the device (I've tried the v2.0 and v3.5 USB drivers at this point.) as does ROM Flash Tool 137 included with Finless 1.6 and the Rockchip Batch Tool v1.6 included in the instructions for the geekbuying.com download of the updated stock ROM.
When I run the ROM FlashTool 137, I click the Erase NAND button and the process completes successfully (0 to 2048, no issues). If I immediately try to click the Flash ROM button, it displays "Start to run" and then "Start to test device", but seconds later shows "Test device failed" followed by "Run failed". If after I Erase NAND successfully, I disconnect the USB cable and reconnect holding the function button, then click on Flash ROM, it will get through the "Download IDB OK", resets the device successfully, and then fails at "Start to test device".
I've tried three different cables, different USB ports and even three different PCs.
Attached is a copy of the last log file.

Please help. I'm starting to panic.
Thank you.

[Com3ToDaddy]

It's been a week and I haven't found a solution.
I've tried two additional cables on two additional PCs and have had the exact same result. That brings the total to five USB cables (one is a Motorola data cable, an LG cable from my smartphone, the cable that came with the CX-919, and I don't know the origin of the other two), and five PCs including: an older Dell tower with Win7, a Dill mini netbook with Win7, a brand new Toshiba Laptop with Win7, a Levnovo Desktop with Win7 and a FrankenPC with WinXP.

When I use the Rockchip_Batch_Tool_v1.6 with CX919-RK3188-4.2-1080P.img, I get:

16:30:11 314 Rockchip Batch Tool v1.6.8.1 start run
16:30:18 914 **********Restore Start Total<1>**********
16:30:18 927 <Layer 1-2> Test Device Start
16:30:18 946 <Layer 1-2> Test Device Success
16:30:18 957 <Layer 1-2> Lowerformat Device Start
16:30:32 023 <Layer 1-2> Lowerformat Device Success
16:30:32 033 <Layer 1-2> Test Device Start
16:30:32 049 <Layer 1-2> Test Device Success
16:30:32 059 <Layer 1-2> Check Chip Start
16:30:32 075 <Layer 1-2> Check Chip Success
16:30:32 086 <Layer 1-2> Get FlashInfo Start
16:30:32 100 <LAYER 1-2> INFO:FlashInfo: 0 0 0 1 0 20 20 28 1F 2 1
16:30:32 114 <Layer 1-2> Get FlashInfo Success
16:30:32 460 <Layer 1-2> Prepare IDB Start
16:30:32 475 <LAYER 1-2> INFO:CS(1) (8192MB) (HYNIX)
16:30:32 558 <Layer 1-2> Prepare IDB Success
16:30:33 157 <Layer 1-2> Download IDB Start
16:30:35 838 <Layer 1-2> Download IDB Success
16:30:35 849 <Layer 1-2> Reset Device Start
16:30:36 867 <Layer 1-2> Reset Device Success
16:30:36 879 <Layer 1-2> Wait For Loader Start
16:30:37 784 <Layer 1-2> Wait For Loader Success
16:30:37 796 <Layer 1-2> Test Device Start
16:30:37 806 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
16:30:38 015 Error:RKU_ClearBuffer-->ReadFile failed,bRet=0,err=31,size=512,read=0
16:30:38 024 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3)
16:30:38 036 <Layer 1-2> Test Device Fail
16:30:38 053 **********Restore Done Success<0> Fail<1> Time<19126>ms**********

As you can see, everything seems to go fine until after the first restart. It even shows that the Loader is still functional, so that means it's not bricked, right?
But then it can't write or read, so it fails the test. Is it possible the device has left flash mode because of the restart? Is the memory defective? Should I return the unit? If I do should I bother trying this again with another unit?

The worst part about this is I had read about the skipping issues before I bought it, so I decided to flash it as soon as I got it! Since I've formatted it, I haven't even had a chance to use the thing!

I would really appreciate any help you could offer.

[Finless]

Try this. In my flash kit is a file called settings.ini
Try changing this value

SUPPORTUSB11=0

Change the 0 to a 1. Close all flash tools and rerun.

Bob

[Com3ToDaddy]

I apologize for the delay getting back to you. I've been ill the last couple days and am just coming back into the real world.
Unfortunately, I've already tried that. I realize now that I left that part out of my original post. I couldn't get any of the computers to show "Found RKAndroid..." without changing that setting first.
Would you have any other suggestions?

Thank you for your time!

[sysmer]

I think the market has lot of bad cx-919,I bought 3 pieces geekbuing cx-919 and one of them is exactly the same problem.
<Layer 1-2> Test DeviceFile
I suffer too,how to solve this problem.

[zik-zak]

I confirm the problem. One of the four devices. I tried to flash the device as a MaskRom mode. "Test Device Fail"

[smithmal]

I'm having similar problems as well. Flashed finless 1.5 and after a couple of days I got the black screen issue and was getting no picture via HDMI.

I then tried flashing the Finless 1.6b and keep failing. I'm noticing two issues with using the RKAndroidTool:

1. Failure to complete an "Erase IDB" command
2. After a reboot, I have success with "Erase IDB" but failure with "Flash ROM." Specifically I'm seeing "Error: Download IDB Failed" followed by a "Error: Run failed"

I never had any issue with flashing ROMs before. Any help would be appreciate as right now, my CX-919 is non-functional.

smithmal

[vipersvcd]

mine fails at the last step the verification/checking data size at (94255)k
ERROR: download file failed
run failed

any ideas ? bought from geekbuying this week .

[smithmal]

I'm beginning to think all these issues that we are seeing during a ROM flash is that we have a corrupted NAND chip (due to some boot loader issues during a flash). From what I've read, they way to fix this is to short out the NAND chip to put it in MASKROM mode, re-erase the NAND and then re-flash the stick.

Bob, I'm assuming the NAND pin short trick is similar to what is done with other tv sticks (i.e. short the chip between pins 8 and 9). Is there anything else we should know about this procedure for the CX-919?

smithmal

[vipersvcd]

I was able to flash ok with no errors using another boot loader .
try boot loader version 1.23 instead of 1.24
some nands are sensitive to the boot loader you use .

though you might need to unpack using the rk3066 image toold the .IMG file
and then use RKBATCH TOOL 1.37 that lets you choose the boot loader seperatly .

[smithmal]

I was able to flash ok with no errors using another boot loader .
try boot loader version 1.23 instead of 1.24
some nands are sensitive to the boot loader you use .

though you might need to unpack using the rk3066 image toold the .IMG file
and then use RKBATCH TOOL 1.37 that lets you choose the boot loader seperatly .

vipersvcd,

Can you provide a step by step on how the bootloader was swapped and what ROM you did this with. I think you mean to use RKAndroidtool v1.37 right? RKBatchtool (now up to v1.7) flashes firmware images while the RKAndroidtool allows you to switch components like bootloader, system, kernel, etc.

smithmal

[leolas]

I was able to flash ok with no errors using another boot loader .
try boot loader version 1.23 instead of 1.24
some nands are sensitive to the boot loader you use .

though you might need to unpack using the rk3066 image toold the .IMG file
and then use RKBATCH TOOL 1.37 that lets you choose the boot loader seperatly .

I bet for this too, maybe certain NAND chips are not supported in certain bootloaders.

leolas

[Finless]

The bootloader in fact manages NAND chip types. Usually a newer version of the bootloader is updated for new or other used NAND chips. It should also be backwards compatible meaning that if NAND chip was support in 1.23 it should also be supported in 1.24. However as we see it might not always be true or maybe has a bug.

Bob

[sysmer]

The bootloader in fact manages NAND chip types. Usually a newer version of the bootloader is updated for new or other used NAND chips. It should also be backwards compatible meaning that if NAND chip was support in 1.23 it should also be supported in 1.24. However as we see it might not always be true or maybe has a bug.

Bob

bob! what is this chip?

GT89F64G08B-TG
and what it needs to bootloader?

[amclean123]

I've had this problem on both of my CX919. I just downloaded an old Finless Rom install and used it to erase my ROM. Once I did that everything worked fine with flashing the newer roms.