Forum switched to read-only as of 2020/06/01
Latest product reviews |
---|
![]() |
![]() |
Smartphones ![]() |
TV Connect ![]() |
![]() |
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 !

2015/12/14

So a few last questions (between the lines) because I got another Tolino to flash your ROM:
Your decription is ... :
connect your tab to the power supply and to the PC via USB cable
1) installation of the usb-driver (skip if you have the driver installed already)
a) boot your tab and set storage mode to MTP and debugging to USB
b) run DriverInstaller.exe
2) start the tab into flash-modus
a) run RKAndroidTool.exe with admin rights
b) press power button and volume up button and hold for 12 sec
c) release the power button
d) release volume up button when "Found ..." is shown
3) flash the firmware with RKAndroidTool
(you mean the set of images: kernel, boot, system... what is as standard in the flashtool setup ?)
a) untick the loader
b) Run
c) stock recovery will format the NAND
d) wait up to 20 min
After this step the tablet boots normally last time I did this with the bricked one. Now the icons where much smaller.
This is the way it should to be ? Then I do a reboot with the following steps (4) and always untick the loader, too or not ?
4) flash the CWM recovery with RKAndroidTool
a) go to app drawer, open RebootMenue and Reboot to Bootloader
b) untick kernel, boot, system
c) load recovery_CWM
d) Run
e) tab boots into CWM
f) reboot system now (both answers are No)
Can you describe the last part (4) with more details, please ?! I'm very afraid to kill the next Tablet
Thank you !


Moderator

Firmware Guru
2012/10/06

The following users say thank you to Oma7144 for this useful post:
johnkissPer aspera ad astra, we rock the Tablets !
If you like our firmwares, please consider making a donation to support our work.
Thank you!


Moderator

Firmware Guru
2012/10/06

Fine. The update is already included, so ignore it.
- Oma -
The following users say thank you to Oma7144 for this useful post:
johnkissPer aspera ad astra, we rock the Tablets !
If you like our firmwares, please consider making a donation to support our work.
Thank you!

2016/01/20

Hi, this is my first post.
I've probably messed up by leaving the loader checkbox ticked in the RKAndroidTool application. The reason I did this is because I could not flash recovery_CWM from within that tool, though, in retrospect, I should have flashed it with the apk or some other tools.
Anyway, like one user before, the tablet is now dead, erase IDB does not work properly and all flash operations fail with 'download failed'.
However, unlike anyone before, I did manage to get my tablet to boot into maskrom mode, by randomly shorting pins next to the Samsung NAND chip. I've started the refresh tool, tried to flash 1.20 and 1.24 loaders but was not able to get anywhere.
The tools shows this:
******EraseFlash action******
Download boot start
Download boot success
Wait for Maskrom start
Wait for Maskrom success
Test device start
Test device Total(0), Current(0)
The log file shows something similar:
23:19:30 798 Rockchip Development Tool v1.7.1.0 start run
23:19:37 805 <Layer 2-1-3> Download Boot Start
23:19:39 764 <Layer 2-1-3> Download Boot Success
23:19:39 766 <Layer 2-1-3> Wait For Maskrom Start
23:19:40 876 <Layer 2-1-3> Wait For Maskrom Success
23:19:40 878 <Layer 2-1-3> Test Device Start
Then the tool just sits there at 0/0. Not sure what the correct output would be. I've tried erase idb, erase all and download loader in all possible orders. After launching one command, the tool cannot launch another one as it says it's still busy.
Any suggestions?


Moderator

Firmware Guru
2012/10/06

Not really. Only two possibilities left. The NAND is defective or the standard Rockchip loader does not know this type of NAND.
- Oma -
Per aspera ad astra, we rock the Tablets !
If you like our firmwares, please consider making a donation to support our work.
Thank you!

2016/01/20

The tablet was working fine before the flash. I've had one tablet with a bad flash chip and it would just get slower and slower while refusing to copy files or flash. So I assume the chip is still fine.
Unfortunately the tablet is out of warranty since a week so I'm willing to try anything before selling it really cheap or keeping it as a paperweight. Perhaps there are ways to get the loader firmware from someone with a working tablet and flash that. I'm not sure what the recommended action would be.
Is the loader fw made for the flash chip - i.e. the microcontroller embedded in the NAND - or is it for some other parts of the system? I don't fully understand how these systems go together.

2016/01/20

Sorry for the late reply.
I've just randomly shorted pins on the NAND chip since I had nothing to lose. I believe pins 9-10 are the ones triggering maskrom, counting down from the upper left corner:

2016/10/08

Hi folks.
I bricked the tablet trying to flash the rom, rockchipdevtool recognizes the tab only in LOADER mode but cant restore or flash like the others.When i try to get into maskrom mode trying the pins my tab just turned on and i could use it normaly.After that i thought that the problem has gone away i restarted the tab and now its dead again.Can anyone here tell me why this happened and did anyone found way to get it back to life???
Thx in advance and have a good one ,)

2014/11/20

miki123 said
Hi folks.I bricked the tablet trying to flash the rom, rockchipdevtool recognizes the tab only in LOADER mode but cant restore or flash like the others.When i try to get into maskrom mode trying the pins my tab just turned on and i could use it normaly.After that i thought that the problem has gone away i restarted the tab and now its dead again.Can anyone here tell me why this happened and did anyone found way to get it back to life???
Thx in advance and have a good one ,)
Why don't you just buy MY tablet? I don't even use it anymore. :p
Obviously the smart thing would've been to check and replace all your files during that brief period the tablet was working again. But if trying the pins worked for you once... why not just try it again? At this point what do you have to lose?

2017/09/29

пожайлуста обьясните подробно в каком файле менять запись и в какую папку вложить файл.спасибо
Please explain in detail in which file to change the entry and which folder to attach the file to. Thanks
im RKAndroidTool ist als "default" der Pfad zur Recovery aus dem Unterordner "rockdev" eingetragen, diese ist die Standard Recovery ohne CWM.
(Diese wird jedoch beim ersten flashen benötigt)
Danach muss du den Pfad zu der Datei "recovery_CWM.img" (Diese liegt im Rootordner des Zips) angeben und flashen.
Am einfachsten kopierst du die "recovery_CWM.img" in den gleichen Ordner und benennst den Eintrag im RKAndroidTool entsprechend um.
13:16:54 783 RKAndroidTool v1.3.7.0 Start Run
13:16:54 784 Scan thread:1848
13:16:54 788 Info:(thread=3056)IoControlProc-->DeviceIoControl In
13:16:54 792 ProcessID:2168,ThreadID:2396,RefCount:0
13:16:54 792 ProcessID:2168,ThreadID:1848,RefCount:0
13:16:54 907 Info:(thread=3056)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:16:54 917 Info:(thread=4676)IoControlProc-->DeviceIoControl In
13:16:54 917 Info:(thread=4676)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:16:59 876 Info:wait for exiting scan thread start
13:17:00 042 Info:wait for exiting main thread start
13:17:00 049 ProcessID:2168,ThreadID:2396,RefCount:0
13:17:21 963 Load Setting ok
13:17:22 009 RKAndroidTool v1.3.7.0 Start Run
13:17:22 009 Scan thread:3220
13:17:22 015 Info:(thread=2104)IoControlProc-->DeviceIoControl In
13:17:22 017 ProcessID:4436,ThreadID:1452,RefCount:0
13:17:22 017 ProcessID:4436,ThreadID:3220,RefCount:0
13:17:22 107 Info:(thread=2104)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:17:22 118 Info:(thread=3344)IoControlProc-->DeviceIoControl In
13:17:22 118 Info:(thread=3344)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:17:57 219 Info:wait for exiting scan thread start
13:17:57 412 Info:wait for exiting main thread start
13:17:57 418 ProcessID:4436,ThreadID:1452,RefCount:0
13:20:43 814 Load Setting ok
13:20:43 867 RKAndroidTool v1.3.7.0 Start Run
13:20:43 867 Scan thread:6140
13:20:43 871 Info:(thread=5360)IoControlProc-->DeviceIoControl In
13:20:43 875 ProcessID:4368,ThreadID:4248,RefCount:0
13:20:43 875 ProcessID:4368,ThreadID:6140,RefCount:0
13:20:43 989 Info:(thread=5360)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:20:43 999 Info:(thread=4704)IoControlProc-->DeviceIoControl In
13:20:43 999 Info:(thread=4704)IoControlProc-->DeviceIoControl Out,ret=1,err=183
13:21:06 534 INFO:Start to erase IDB
13:21:06 535 INFO:Start to lower format
13:21:07 539 INFO:Lower format OK
13:21:07 541 INFO:Erasing IDB OK
13:21:25 551 Loader Device Path(\\?\USB#VID_2207&PID_310B#5&30124DE0&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}),ThreadID=2320
13:21:25 551 INFO:Start to test device
13:21:25 552 INFO:Start to run
13:21:25 555 INFO:Test device OK
13:21:25 556 INFO:Start to download IDB
13:21:25 558 Flash Chip Information:
13:21:25 558 NO SIZE(MB) Manufacturer
13:21:25 558 ----------------------------------------------
13:21:25 559 0 1447867MB SAMSUNG
13:21:25 560 ----------------------------------------------
13:21:25 560 INFO:BuildFlashStateMap start
13:21:25 564 INFO: FindAllIDB start
13:21:25 699 ERROR: FindAllIDB failed
13:21:25 700 Error:Download IDB failed
13:21:25 701 INFO:LoaderThread failed
13:21:25 703 ERROR:Run failed
13:21:39 214 Image Thread Path(\\?\USB#VID_2207&PID_310B#5&30124DE0&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}),ThreadID=5936
13:21:39 215 INFO:Start to test device
13:21:39 216 INFO:Start to run
13:21:39 219 INFO:Test device OK
13:21:39 221 INFO:Start to download file
13:21:39 224 INFO: Start to download files to flash,backup offset=0x20000
13:21:39 226 INFO:Flash Start to download file to flash
13:21:39 257 Info:RKA_File_Download start,file=misc,offset=0x2000
13:21:39 265 Info:RKA_File_Download start,file=kernel,offset=0x4000
13:21:40 037 Info:RKA_File_Download start,file=boot,offset=0xa000
13:21:40 101 Info:RKA_File_Download start,file=recovery,offset=0x10000
13:21:40 879 Info:RKA_File_Download start,file=system,offset=0x142000
13:22:47 723 INFO: Download files to flash finished,Total(1094256048)B
13:22:47 809 INFO: Start to check data
13:22:47 811 INFO:Start to check download data
13:22:47 812 Error:Compare parameter file failed,Offset(0)
13:22:47 814 Error: Check parameter file failed
13:22:47 815 ERROR:Download file failed
13:22:47 817 ERROR:Image Thread Failed
13:22:47 820 ERROR:Run failed
13:23:08 620 Info:wait for exiting scan thread start
13:23:08 757 Info:wait for exiting main thread start
13:23:08 763 ProcessID:4368,ThreadID:4248,RefCount:0
Most Users Ever Online: 803
Currently Online:
55 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Devices in use: Desktop (51), Phone (4)
Top Posters:
finless: 604
DarthJabba: 551
maikal: 394
mussonero1: 350
alex: 252
damo: 243
DanielVd: 237
Mark06: 222
Newest Members:
Jack81
tdomnic024
otismaibe
Tsuna77
docentik2006
nechey
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