Forum switched to read-only as of 2020/06/01


Latest product reviews
ARCHOS 50 Diamond
ARCHOS GamePad2
ARCHOS
Smartphones
ARCHOS
TV Connect
ARCHOS 101 XS

A A A
Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?

ClockworkMod (CWM) Recovery easy install for RK3066 and RK3188 -- TWRP/CWM Flash-Tool and root for RK3288

 Please donate to support OMA and CrewRKTablets firmware work, thank you !

sp_Feed sp_TopicIcon
Need help with bricked PiPO M9 pro
Avatar
spaceboy1
Active Member
Forum Posts: 30
Member Since:
2013/06/04
sp_UserOfflineSmall Offline

Thanks Received: 2
61
2013/12/24 - 17:29
sp_Permalink sp_Print

I've done everything and not linked , you people do not know how you did it but I abideth in cwm recovery and do that
I've done all the steps very carefully but there is be associated EDU the computer
The tablet has a serious problem and we will send it for repair in CHINA
Is not the first time I go to rom flashes but it never happened to me sometime in my life

While he and I expect this write me no device connect rock usb
Is there any other solution or send CHINA ;
 
Do not tell me you do not do it right steps, I do like the description but the tablets are BRICK

www.madradio107.net

Avatar
keeshg
Nederland
New Member
Forum Posts: 2
Member Since:
2013/11/22
sp_UserOfflineSmall Offline
62
2014/01/10 - 22:58
sp_Permalink sp_Print

I had my Pipo M6pro bricked. No reaction, not possible to connect to pc. By accident I found a way to reach it.

I noticed a windows connectionsound when holding the powerbutton pressed for a while and again when I released the powerbutton. So I flashed again and I did hold the powerbutton pressed for a long time while flashing in recover modus. Well that worked for me. I never did read about this method. Perhaps someone can use it.

Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
63
2014/05/08 - 11:08
sp_Permalink sp_Print sp_EditHistory

Hi, I had have a problem flashing the rom with the BatchTool in my PIPO MAX M9(non PRO), I think i used a ROM for PRO tablets and in the end of flashing the process give me an error and the tablet didnt restart . Now I am triying do the hard bricked trick but I can´t.

The flash tool indentified the tablet but my PC  discconect the tablet every minute, for one second. then when I am trying to erase nand with the flash tool, doing the low format, when the count reach 15000 of total of 16386, the USB is disconeccted. Even with not flashing software just with the tabled plugged, windows every minute disconect the tablet one second and inmediately indentifying it again.

If I try with the batchtool 1.7, occurs the same during the testing device procees. 

I am using drivers the dirvers 3.5 and I have tried with 3 computers and diferents USB cables but not way.

Sorry for my english.

Any Idea?

Avatar
cracktech
Malaysia

Moderator
Forum Posts: 432
Member Since:
2013/01/24
sp_UserOfflineSmall Offline

Thanks Received: 112
64
2014/05/08 - 13:20
sp_Permalink sp_Print sp_EditHistory

Dont let go of the hardware buttons until the flashing is over. try to do that. Irregardless of any model you have try to use the latest BatchTool v 1.7 and discard the old version from your PC. Are you using the how to reciver from hardbrick procedure outline elsewhere in this Forum (the one with hardware buttons combination before you start to make PC identify the device?)

About Me    LENOVO S939 MTK6592 Vibe 2.0 - 1507,LENOVO A8-A5500 KitKat MTK8382 S029,Lenovo Tab2 A7-30HC MT8382 Lollipop,LENOVO A880  S027 MTK6582 (JB),ONDA V975m V3 AMLOGIC M802 (KitKat)PiPo M9Pro RK3188 KASTY ROM (KitKat # 407 Mod), ZENITHINK ZTPAD:C93 Duo Core AMX CM10.2_rc-3, Z102 And. 4.0.4, C91 And. 4.0.4,AIGO M60 Android 4.04 6" A13 (rooted).Lenovo A369i 4.2.2 S011 ROW

 


Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
65
2014/05/08 - 13:34
sp_Permalink sp_Print sp_EditHistory

cracktech said
Dont let go of the hardware buttons until the flashing is over. try to do that. Irregardless of any model you have try to use the latest BatchTool v 1.7 and discard the old version from your PC. Are you using the how to reciver from hardbrick procedure outline elsewhere in this Forum (the one with hardware buttons combination before you start to make PC identify the device?)

Thanks cracktech, but it doesn´t work. I tell you what i have done, maybe i did something wrong.

I press the esc button for 5 seconds, then i press reset button too without release the esc button, After 5 seconds i press the power botton too, with this 3 bottons pressed i start the erase nand, beging count and when it reaches around 14000 the tablet is disconected for 1 second, the process continue but after several tryes the software says the process it is failed.

 

Same if i folow another buttons combinations i have readed before (realising all buttons before start, realising all except power button before start...)

In pipo documentation says for android 4.1 press just power and reset and when the device is detected release reset but in this way the software dont detect the device. Always i have to press power again or release the reset botton....

I dont have more ideas....

Edited: I have tried already the batchtool, but the same problem when it tested the device. When i do the button process the software already has detected the device but i do anyway.

Avatar
xocolocoxoco
Regular Member
Forum Posts: 54
Member Since:
2013/09/27
sp_UserOfflineSmall Offline

Thanks Received: 1
66
2014/05/08 - 13:55
sp_Permalink sp_Print

select mode flash. And wake, wake, wake. One hour is stabilize.

Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
67
2014/05/08 - 14:05
sp_Permalink sp_Print

xocolocoxoco said
select mode flash. And wake, wake, wake. One hour is stabilize.

Do you mean press "reboot to flash mode" if i press it told me not in MSC mode or something like that. Just now i unplugged the tablet from charger and plug again and the PC dont connect with the tablet 

Avatar
xocolocoxoco
Regular Member
Forum Posts: 54
Member Since:
2013/09/27
sp_UserOfflineSmall Offline

Thanks Received: 1
68
2014/05/08 - 14:10
sp_Permalink sp_Print

yes, sometimes it delay for recognize. 5-10min or 30 too

Avatar
cracktech
Malaysia

Moderator
Forum Posts: 432
Member Since:
2013/01/24
sp_UserOfflineSmall Offline

Thanks Received: 112
69
2014/05/08 - 14:20
sp_Permalink sp_Print

xocolocoxoco said
select mode flash. And wake, wake, wake. One hour is stabilize.

Muttenroi,

Xocolocoxoco is the original "bricked my pad" guy maybe he has better ideas than us on conventinal methods , he did recover eventually from his bricked device.

xocolo you meant to say "waiit,wait,wait" right? instaed of "wake,wake,wake" (Muttenroi at this point is wide "awake" trying to get his pad to flash).

If not try to use the any RIley rom flash method on your device first but after success do come back and use KASTY's ROM (that is just to recover from brick pad, same you have to use button combination first but it breaks down the process into formatting nand, and other partitions,we need to get past the formatting nand part)

But based on your description yours is not hardbricked since the PC can identify the device after USB connection. This is something else the "nand format part". I dont have a clue about what tod o here as I have not come across a device that can be identifed by PC and it is only failure to format nand.

Or another try could be the the most unfavourable which is ty to flash using SDCARD upgrade method. It is the last resort.

About Me    LENOVO S939 MTK6592 Vibe 2.0 - 1507,LENOVO A8-A5500 KitKat MTK8382 S029,Lenovo Tab2 A7-30HC MT8382 Lollipop,LENOVO A880  S027 MTK6582 (JB),ONDA V975m V3 AMLOGIC M802 (KitKat)PiPo M9Pro RK3188 KASTY ROM (KitKat # 407 Mod), ZENITHINK ZTPAD:C93 Duo Core AMX CM10.2_rc-3, Z102 And. 4.0.4, C91 And. 4.0.4,AIGO M60 Android 4.04 6" A13 (rooted).Lenovo A369i 4.2.2 S011 ROW

 

Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
70
2014/05/08 - 14:31
sp_Permalink sp_Print

yes I think it identify see this capture

https://drive.google.com/file/d/0B4GbbGkj78xDWTFySkEtUTZpbW8/edit?usp=sharing 

How i can flash use SDCARD Update? Any Link?

Avatar
cracktech
Malaysia

Moderator
Forum Posts: 432
Member Since:
2013/01/24
sp_UserOfflineSmall Offline

Thanks Received: 112
71
2014/05/08 - 14:49
sp_Permalink sp_Print sp_EditHistory

mutenrroi said
yes I think it identify see this capture

https://drive.google.com/file/d/0B4GbbGkj78xDWTFySkEtUTZpbW8/edit?usp=sharing 

How i can flash use SDCARD Update? Any Link?

I saw your RK Batch tool is version 1.37 and I thought the worst you could do was version 1.6. Discard all those versions from your PC and use only version 1.7 (experince as reported by other users using 1.6 cannot flash successfully M9/M9Pro only success with v1.7) and another is I saw that you are flashing from a RILEY ROM version firmware not KASTY ROM.(Is that true?)

For SDcard update method I cant tell you coz I dont encourage people to use this method (it is copying the firmware and putting all of it on the root of sdcard and press the power button and esc button to start the pad, i.e if I am not wrong)

Please dont use any batch Tool version lower than version 1.7 to flash this model M9/M9Pro, if you dont follow instructions than I dont think we can help you.

About Me    LENOVO S939 MTK6592 Vibe 2.0 - 1507,LENOVO A8-A5500 KitKat MTK8382 S029,Lenovo Tab2 A7-30HC MT8382 Lollipop,LENOVO A880  S027 MTK6582 (JB),ONDA V975m V3 AMLOGIC M802 (KitKat)PiPo M9Pro RK3188 KASTY ROM (KitKat # 407 Mod), ZENITHINK ZTPAD:C93 Duo Core AMX CM10.2_rc-3, Z102 And. 4.0.4, C91 And. 4.0.4,AIGO M60 Android 4.04 6" A13 (rooted).Lenovo A369i 4.2.2 S011 ROW

 

Avatar
xocolocoxoco
Regular Member
Forum Posts: 54
Member Since:
2013/09/27
sp_UserOfflineSmall Offline

Thanks Received: 1
72
2014/05/08 - 15:04
sp_Permalink sp_Print

I belive for sdcard no possible. Use the software original for pipo

 

firmware

http://pipo.cn/En/index.php?m=Product&a=show4&type=2&id=286

program

http://pipo.cn/En/index.php?m=About&a=gujian_show&id=70

Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
73
2014/05/08 - 15:09
sp_Permalink sp_Print sp_EditHistory

cracktech said

mutenrroi said
yes I think it identify see this capture

https://drive.google.com/file/d/0B4GbbGkj78xDWTFySkEtUTZpbW8/edit?usp=sharing 

How i can flash use SDCARD Update? Any Link?

I saw your RK Batch tool is version 1.37 and I thought the worst you could do was version 1.6. Discard all those versions from your PC and use only version 1.7 (experince as reported by other users using 1.6 cannot flash successfully M9/M9Pro only success with v1.7) and another is I saw that you are flashing from a RILEY ROM version firmware not KASTY ROM.(Is that true?)

For SDcard update method I cant tell you coz I dont encourage people to use this method (it is copying the firmware and putting all of it on the root of sdcard and press the power button and esc button to start the pad, i.e if I am not wrong)

Please dont use any batch Tool version lower than version 1.7 to flash this model M9/M9Pro, if you dont follow instructions than I dont think we can help you.

cracktech, It isnt the RK batch,It is RK Android tool, I have see it in the post #20 of this thread, and i am not using the Kasty Rom becouse I dont know if it is ok for the M9 non PRO. This is the only one ROM i have found for old pcb´s. What Kasty ROM can I use?

 

Before this, I tryed with the batch tool 1.7 and the oficial rom but I have the same problem too when it is testing the device: https://drive.google.com/file/d/0B4GbbGkj78xDbkZaS01qMmRYZFU/edit?usp=sharing

Sorry if i am doing something wrong, i am doing my best.

Thank you.

Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
74
2014/05/10 - 04:46
sp_Permalink sp_Print

I dont know if it can help, but i leave here the log of the failed flash. (Sorry it is big)

:57:46 269 **********Restore Start Total<1>**********
16:57:46 274 <Layer 2-1-2> Test Device Start
16:57:46 314 <Layer 2-1-2> Test Device Success
16:57:46 316 <Layer 2-1-2> Lowerformat Device Start
16:59:20 368 <Layer 2-1-2> Lowerformat Device Success
16:59:20 372 <Layer 2-1-2> Test Device Start
16:59:20 384 <Layer 2-1-2> Test Device Success
16:59:20 387 <Layer 2-1-2> Check Chip Start
16:59:20 392 <Layer 2-1-2> Check Chip Success
16:59:20 397 <Layer 2-1-2> Get FlashInfo Start
16:59:20 400 <LAYER 2-1-2> INFO:FlashInfo: 0 0 80 0 0 4 8 18 28 4 F
16:59:20 404 <Layer 2-1-2> Get FlashInfo Success
16:59:20 412 <Layer 2-1-2> Prepare IDB Start
16:59:20 413 <LAYER 2-1-2> INFO:CS(1) (4096MB) (MICRON)
16:59:20 414 <LAYER 2-1-2> INFO:CS(2) (4096MB) (MICRON)
16:59:20 414 <LAYER 2-1-2> INFO:CS(3) (4096MB) (MICRON)
16:59:20 415 <LAYER 2-1-2> INFO:CS(4) (4096MB) (MICRON)
16:59:20 423 <Layer 2-1-2> Prepare IDB Success
16:59:20 426 <Layer 2-1-2> Download IDB Start
16:59:21 050 <Layer 2-1-2> Download IDB Success
16:59:21 056 <Layer 2-1-2> Reset Device Start
16:59:22 060 <Layer 2-1-2> Reset Device Success
16:59:22 061 <Layer 2-1-2> Wait For Loader Start
16:59:23 458 <Layer 2-1-2> Wait For Loader Success
16:59:23 460 <Layer 2-1-2> Test Device Start
17:02:28 655 <Layer 2-1-2> Test Device Success
17:02:28 663 <Layer 2-1-2> Download Firmware Start
17:03:30 278 <LAYER 2-1-2> ERROR:RKA_File_Check-->Memcmp failed,Read(1048576)
17:03:30 287 <LAYER 2-1-2> ERROR:DownloadImage-->RKA_File_Check failed(kernel)
17:03:30 294 <Layer 2-1-2> Download Firmware Fail
17:03:30 299 **********Restore Done Success<0> Fail<1> Time<344029>ms**********
17:04:25 942 Rockchip Batch Tool v1.7.1.1 start run
17:06:10 432 **********Upgrade Start Total<1>**********
17:06:10 442 <Layer 2-1-2> Test Device Start
17:06:10 442 <Layer 2-1-2> Test Device Success
17:06:10 452 <Layer 2-1-2> Check Chip Start
17:06:10 452 <Layer 2-1-2> Check Chip Success
17:06:10 452 <Layer 2-1-2> Get FlashInfo Start
17:06:10 462 <LAYER 2-1-2> INFO:FlashInfo: 0 0 80 0 0 8 8 18 20 7 F
17:06:10 462 <Layer 2-1-2> Get FlashInfo Success
17:06:10 462 <Layer 2-1-2> Prepare IDB Start
17:06:10 462 <LAYER 2-1-2> INFO:CS(1) (4096MB) (INTEL)
17:06:10 462 <LAYER 2-1-2> INFO:CS(2) (4096MB) (INTEL)
17:06:10 462 <LAYER 2-1-2> INFO:CS(3) (4096MB) (INTEL)
17:06:10 462 <LAYER 2-1-2> INFO:CS(4) (4096MB) (INTEL)
17:06:10 492 <Layer 2-1-2> Prepare IDB Success
17:06:10 492 <Layer 2-1-2> Download IDB Start
17:06:11 112 <Layer 2-1-2> Download IDB Success
17:06:11 442 <Layer 2-1-2> Reset Device Start
17:06:12 442 <Layer 2-1-2> Reset Device Success
17:06:12 442 <Layer 2-1-2> Wait For Loader Start
17:06:13 612 <Layer 2-1-2> Wait For Loader Success
17:06:13 612 <Layer 2-1-2> Test Device Start
17:06:13 612 <Layer 2-1-2> Test Device Success
17:06:13 612 <Layer 2-1-2> Download Firmware Start
17:07:18 262 <LAYER 2-1-2> ERROR:RKA_File_Check-->Memcmp failed,Read(1048576)
17:07:18 272 <LAYER 2-1-2> ERROR:DownloadImage-->RKA_File_Check failed(kernel)
17:07:18 282 <Layer 2-1-2> Download Firmware Fail
17:07:18 292 **********Upgrade Done Success<0> Fail<1> Time<67845>ms**********
17:08:58 452 **********Restore Start Total<1>**********
17:08:58 459 <Layer 2-1-2> Test Device Start
17:08:58 461 <Layer 2-1-2> Test Device Success
17:08:58 463 <Layer 2-1-2> Lowerformat Device Start
17:09:17 483 <Layer 2-1-2> Lowerformat Device Success
17:09:17 487 <Layer 2-1-2> Test Device Start
17:09:17 496 <Layer 2-1-2> Test Device Success
17:09:17 500 <Layer 2-1-2> Check Chip Start
17:09:17 504 <Layer 2-1-2> Check Chip Success
17:09:17 507 <Layer 2-1-2> Get FlashInfo Start
17:09:17 511 <LAYER 2-1-2> INFO:FlashInfo: 0 0 80 0 0 8 8 18 20 7 F
17:09:17 513 <Layer 2-1-2> Get FlashInfo Success
17:09:17 842 <Layer 2-1-2> Prepare IDB Start
17:09:17 844 <LAYER 2-1-2> INFO:CS(1) (4096MB) (INTEL)
17:09:17 846 <LAYER 2-1-2> INFO:CS(2) (4096MB) (INTEL)
17:09:17 847 <LAYER 2-1-2> INFO:CS(3) (4096MB) (INTEL)
17:09:17 848 <LAYER 2-1-2> INFO:CS(4) (4096MB) (INTEL)
17:09:17 863 <Layer 2-1-2> Prepare IDB Success
17:09:17 868 <Layer 2-1-2> Download IDB Start
17:09:18 468 <Layer 2-1-2> Download IDB Success
17:09:18 475 <Layer 2-1-2> Reset Device Start
17:09:19 482 <Layer 2-1-2> Reset Device Success
17:09:19 483 <Layer 2-1-2> Wait For Loader Start
17:09:20 454 <Layer 2-1-2> Wait For Loader Success
17:09:20 456 <Layer 2-1-2> Test Device Start
17:09:39 470 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:09:39 471 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:09:59 481 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:09:59 484 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:10:19 498 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:10:19 499 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:10:39 512 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:10:39 512 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:10:59 531 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:10:59 531 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:11:19 545 Error:RKU_Write-->WriteFile failed,bRet=0,err=2,size=31,write=0
17:11:19 746 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:11:19 746 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:11:39 762 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:11:39 764 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:12:20 803 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:12:20 803 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:12:40 823 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:12:40 823 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:13:00 842 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:13:00 842 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:13:20 859 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:13:20 860 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:13:40 881 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:13:40 883 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:00 903 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:00 904 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:20 920 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:20 921 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:40 949 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:40 950 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:41 952 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:41 952 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:42 953 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:42 955 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:14:43 960 <Layer 2-1-2> Test Device Fail
17:14:43 966 **********Restore Done Success<0> Fail<1> Time<345511>ms**********
17:15:06 987 Rockchip Batch Tool v1.7.1.1 start run
17:15:35 937 **********Upgrade Start Total<1>**********
17:15:35 947 <Layer 2-1-2> Test Device Start
17:15:46 987 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:15:46 987 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:16:06 987 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:16:06 987 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:16:26 987 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:16:26 987 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:16:47 003 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:16:47 004 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:17:07 022 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:17:07 023 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:17:27 039 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:17:27 040 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:17:47 060 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:17:47 061 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:18:07 083 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:18:07 085 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:18:27 109 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:18:27 109 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:18:47 125 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:18:47 126 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:19:07 146 Error:RKU_Write-->WriteFile failed,bRet=0,err=2,size=31,write=0
17:19:07 347 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:19:07 347 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:19:27 366 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:19:27 368 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:19:47 385 Error:RKU_Write-->WriteFile failed,bRet=0,err=2,size=31,write=0
17:19:47 586 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:19:47 586 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:07 602 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:07 602 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:27 619 Error:RKU_Write-->WriteFile failed,bRet=0,err=2,size=31,write=0
17:20:27 820 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:27 821 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:47 841 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:47 842 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:48 844 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:48 844 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:49 845 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:49 846 <LAYER 2-1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_310B#6&8057EBE&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:20:50 850 <Layer 2-1-2> Test Device Fail

Avatar
mutenrroi
New Member
Forum Posts: 7
Member Since:
2014/05/07
sp_UserOfflineSmall Offline

Thanks Received: 1
75
2014/05/10 - 14:06
sp_Permalink sp_Print

I did it!!! I am so happy, my tablet is working again...I had to open the tablet and short the pins follow this video.

Thank you so much everybody!!

The following users say thank you to mutenrroi for this useful post:

seno1963
Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online: run2droi
83 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (53), Phone (30), Tablet (1)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

roro17920

anbague

run2droi

iceman14

AnyFox

BAMHAB82

Forum Stats:

Groups: 10

Forums: 185

Topics: 6037

Posts: 60500

 

Member Stats:

Guest Posters: 43

Members: 262194

Moderators: 5

Admins: 1

Administrators: admin

Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech


CrewRKTablets moderators: JochenKauz and Astralix