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
Rom request for Tolino Tab 8.9
CM 10 or better Kitkat would be nice
Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
106
2015/01/15 - 09:50
sp_Permalink sp_Print sp_EditHistory

Fine. Documented here: http://crewrktablets.arctablet.com/?p=3626

- Oma -

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
107
2015/01/15 - 09:59
sp_Permalink sp_Print

2aladin said
Hi there

I have got the same problems like fraggy:

i have do all steps like in your guide.

the step with the eraseIDB worked but after that if i try to click on RUN just a few seconds later i get an error message in red letters

“Error Download File failed"

and

"Error Run failed” .

(If i change the parameter files it doesn`t work as well as Omni )

The tablet can not even boot.

i only get a black screen! NOTHING ELSE. the tablet is marked found when i connect it but nothing else

Hope you can help me!

This indicates that the images won't fit to the partition layout.

The parameter file defines the partition layout on the NAND. EraseIDB will wipe it.

So make sure you do NOT use other parameter files and to execute eraseIDB properly (in the right window current should count up).

Other typical problem could cause such kind of error are not properly installed usb driver. Best is to use a Win7 PC. Do not use usb3.0 ports.

Here is a Driver Assistant: http://crewrktablets.arctablet.com/?wpfb_dl=1187. Make sure it is in C:. Unisnstall driver first, then install.

- Oma -

Avatar
2aladin
Member
Forum Posts: 11
Member Since:
2015/01/14
sp_UserOfflineSmall Offline
108
2015/01/15 - 18:18
sp_Permalink sp_Print

Dear Oma,

thanks for replying.

- I have the correct USB driver installed. I've reinstalled the one you've linked in case something went wrong.

- I have a Windows 7 PC with no USB 3 at all

- I've erased IDB several times 

- I've used all that is in your package (original parameter - nothing changed)

I am unable to flash anything. and the tab doesn't even boot anymore. It stays black.

 

Please see attached screenshot.

bild.pngImage Enlarger

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
109
2015/01/15 - 18:45
sp_Permalink sp_Print

Zip the log folder (RKandroidTool/log) and attach it here.

- Oma -


Avatar
2aladin
Member
Forum Posts: 11
Member Since:
2015/01/14
sp_UserOfflineSmall Offline
110
2015/01/15 - 19:00
sp_Permalink sp_Print

here's the log

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
111
2015/01/15 - 19:15
sp_Permalink sp_Print

16:41:45 294    Error:Compare parameter file failed,Offset(0)
16:41:45 305    Error: Check parameter file failed
16:41:45 306    ERROR:Download file failed
16:41:45 310    ERROR:Image Thread Failed
16:41:45 319    ERROR:Run failed

I guess your NAND is corrupted somehow. Is this build v1.0 or v1.1? Did you change something on the pack?

- Oma -

Avatar
2aladin
Member
Forum Posts: 11
Member Since:
2015/01/14
sp_UserOfflineSmall Offline
112
2015/01/15 - 19:24
sp_Permalink sp_Print

 I had actually your build 1.0 installed, this worked fine.

Then I tried to update to the KitKat Version you've offered here, changed the kernel and the parameter as required and then stared but this happened. after EraseIDB and pressing run this error and then Black Screen with no more function.

Then I've tried to redo the steps of Build 1.0 but don't work anymore. Also Build 1.1 don't work. I've tried and tried ... I got always the same ERRORS.

This log is actually from build 1.1 as I've tried today once again after your post ...

Is there anyway to get the NAND uncorrupted or another way of flashing back the original or recover firmware?

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
113
2015/01/15 - 19:30
sp_Permalink sp_Print

You can try this: http://crewrktablets.arctablet.com/?wpfb_dl=1631

Instructions (picture) are included. Use the v1.24 loader. After the procedure start directly with the RKAndroidTool, usually procedure.

- Oma -

Avatar
2aladin
Member
Forum Posts: 11
Member Since:
2015/01/14
sp_UserOfflineSmall Offline
114
2015/01/16 - 01:59
sp_Permalink sp_Print

Thanks Oma for your patience and your support.

Unfortunately this didn't help either.

I got Fails and errors.

I've also tried several usb ports and another even another PC. Any other idea?

Here's the log.

Avatar
2aladin
Member
Forum Posts: 11
Member Since:
2015/01/14
sp_UserOfflineSmall Offline
115
2015/01/16 - 10:21
sp_Permalink sp_Print

do i need to reset the nand somehow or is my tablet completely bricked?

Avatar
Astralix
Germany

Firmware Guru
Forum Posts: 27
Member Since:
2012/12/27
sp_UserOfflineSmall Offline

Thanks Received: 7
116
2015/01/16 - 10:31
sp_Permalink sp_Print sp_EditHistory

Hi 2aladin,

it is quite hard to recover devices with windows as there are mostly fully-automatic tools available. You cannot do singe steps and you can only guess why they failed, after they failed. So the preferred way of recovering devices step by step is to use linux.

For a rockchip device, you can boot from a linux USB stick that you prepared as described here:
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
Before clicking "Create" in Step 3, pull the lever of "Step 4: Set a persistent file size for storing changes (Optional)" to the right.
This is needed to run linux just on the stick without installing it anywhere else and beeing able to store some additional files wen need.

Now, boot into linux by booting from the stick. Most modern bios allow to select the boot device by pressing F12 in the BIOS startup screen. So you don't have to alter your BIOS settings.
In the boot menu from linux select "Try Ubuntu without installing".

As you might see, the bar on the right shows your local disks so you might directly access your downloaded images for you tablet. What we additionally need is the linux tool to flash:
Press Ctrl-Alt-T to open a terminal window, then...
- Download the upgrade_tool at http://crewrktablets.arctablet.com/?wpfb_dl=2007
- Extract the zip file
- add the tool to the PATH so we do not have to take care of where it is stored

wget http://crewrktablets.arctablet.com/?wpfb_dl=2007 -O Linux_Upgrade_Tool_v1.21.zip
unzip Linux_Upgrade_Tool_v1.21.zip
export PATH="~/Linux_Upgrade_Tool_v1.21:$PATH"

Now we use nautilus (the "explorer" used in Ubuntu linux) to find our images, so use the mouse to click on the drives on the left side and search your drives for the images...
You need to click you right through to the "rockdev" directory, but do not dive into "Images".

Now we can try to flash, but the flash requires root access to the USB system. So we prepend a "sudo" before each command.

sudo upgrade_tool

if you start this, there is either a red line telling you that no device is found. In that case, your tablet is not connected or not in any bootloader mode. Try again until it shows you an indexed line 1. blablabl rockdev. .... press number or "Q" to quit.
We press "Q" here as we only want to check, if there is a device in LOADER or MASK ROM mode.

However you pretty killed your flash content, so we start from the beginning.
In the console window, change to the directory containing your images... For that in the nautilus window you see the complete directory name. Press "Ctrl-L" and the path line on top will becomes a normal input line. double or tripple click it to mark it completely, change to the console window, write "cd " and then middle click with your mouse to paste the marked path. Press enter. If this doesn't work, mark the line, press Strg-C, switch to console and then write "cd " and press right-klick Insert or "Strg-INS", then press Enter to change the directory.
if you then enter the command "ll" you should see the following files:

astralix:/media/ARCHIVE/Android/iron/rockdev$ ll
total 424
drwxrwxr-x 3 astralix users 4096 Jan 13 00:54 ./
drwxrwsr-x 5 astralix users 4096 Jan 14 00:27 ../
drwxrwxr-x 2 astralix users 4096 Jan 13 11:37 Image/
-rw-rw-r-- 1 astralix users 363 Jan 11 20:10 package-file
-rw-rw-r-- 1 astralix users 627 Jan 13 00:54 parameter
-rw-rw-r-- 1 astralix users 611 Jan 11 20:32 parameter.bak
-rw-rw-r-- 1 astralix users 266 Jun 5 2013 recover-script
-rw-rw-r-- 1 astralix users 194738 Aug 29 2013 RK3188Loader(L)_V1.24.bin
-rw-rw-r-- 1 astralix users 201038 Jul 22 14:30 RK3188Loader(L)_V2.16.bin
-rw-rw-r-- 1 astralix users 933 Jun 5 2013 update-script

In the above example I have two loaders, but you will only have one, so you need to exchange the name with yours in the following examples:

sudo upgrade_tool ef "RK3188Loader(L)_V2.16.bin"
sudo upgrade_tool ul "RK3188Loader(L)_V2.16.bin"
sudo upgrade_tool lf
sudo upgrade_tool di -p parameter
sudo upgrade_tool di -k Image/kernel.img
sudo upgrade_tool di -b Image/boot.img
sudo upgrade_tool di -r Image/recovery.img
sudo upgrade_tool di -m Image/misc.img
sudo upgrade_tool di -s Image/system.img

After that, your device has Loader and other images flashed. Only one command is missing:

sudo upgrade_tool rd

what reboots the device.

If you get stuck at any stage of this, just respond and ask your question.
I did not explain special options in the upgrade_tool as first I need to know if it get stuck and then where. If everything works fine, just leave a note.

Edit: Added sudo as we did not add the rockchip VID/PID to the udev rules.

Good luck and success
Astralix

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

admin
Avatar
bloedack
Member
Forum Posts: 13
Member Since:
2014/12/03
sp_UserOfflineSmall Offline
117
2015/01/16 - 10:48
sp_Permalink sp_Print sp_EditHistory

I have successfully flashed omas kitkat rom to rolino tab 8.9.

Maybe it is to hard to read the whole thread to get the hints how to do it...

so here is a short howto:

i assume that you know how to install the usb driver, boot into bootloader and use the RKAndroidTool. Instructions are included in kitkat rom.

what you need: Omas JB Rom for tolino tab http://crewrktablets.arctablet.com/?wpfb_dl=1850 , the kitkat rom http://crewrktablets.arctablet.com/?wpfb_dl=2035 , the dynamic parameters file http://crewrktablets.arctablet.com/?wpfb_dl=2043 , the jb kernel http://crewrktablets.arctablet.com/?wpfb_dl=1736 and the model fix http://crewrktablets.arctablet.com/?wpfb_dl=2289

unpack all files.

copy recovery.img from "JBImage"
ockdev\Image to "KKImage"
ockdev\Image and overwrite the existing one.

copy recovery_cwm.img from "JBImage"
ockdev to "KKImage"
ockdev\Image.

copy kernel.img from jb kernel to "KKImage"
ockdev\Image and overwrite the existing one.

copy dynamic parameters file to "KKImage"
ockdev and overwrite the existing one.

start RKAndroidTool from "KKImage"\RKDevelopTool_v1.37

do a EraseIDB.

flash the rom. after flashing tab boots in stock recovery and formats data and cache.

when tab is booted up, reboot to bootloader again.

In RKAndroidTool untick all except recovery and change path to ..
ockdev\Image
ecovery_cwm.img.

flash the cwm recovery.

after reboot transfer the model fix zip file to tab.

reboot tab to cwm recovery and install model fix.

do oma's recommended perfomrance settings.

you're done.

Avatar
Astralix
Germany

Firmware Guru
Forum Posts: 27
Member Since:
2012/12/27
sp_UserOfflineSmall Offline

Thanks Received: 7
118
2015/01/16 - 11:34
sp_Permalink sp_Print

Thank you blodack,

but if someone already sent logs of this procedure and the logs show that this doesn't work, it doesn't help to repeat the same procedure over and over. As I told, the windows tools do everything automatically and if the automatic mechanisms fail, the windows tools bring you nowhere. In that case you need linux and we should not bloat the thread by just repeating the procedure of the windows tools.

But thanks again
Astralix

Avatar
rainless
Active Member
Forum Posts: 32
Member Since:
2014/11/20
sp_UserOfflineSmall Offline
119
2015/01/16 - 11:54
sp_Permalink sp_Print

Astralix said
Thank you blodack,

but if someone already sent logs of this procedure and the logs show that this doesn't work, it doesn't help to repeat the same procedure over and over. As I told, the windows tools do everything automatically and if the automatic mechanisms fail, the windows tools bring you nowhere. In that case you need linux and we should not bloat the thread by just repeating the procedure of the windows tools.

But thanks again
Astralix

Actually the windows tool works just fine... with two notable exceptions so far.

Also you don't need to overwrite any files. All you have to do is  click the line to the right of the files and point to where you have the other files stored.  Copying and renaming them all is time-consuming and unnecessary.

 

I've flashed all roms with the Windows tool with absolutely no problem at all. (Though I could've also done it in Linux if I really wanted to.)

Avatar
Astralix
Germany

Firmware Guru
Forum Posts: 27
Member Since:
2012/12/27
sp_UserOfflineSmall Offline

Thanks Received: 7
120
2015/01/16 - 13:37
sp_Permalink sp_Print

Hello rainless,

thank you for explaining how to use the windows tools in a good way. Unfortunately if the Loader is bricked, the windows tools cannot recover this situation in an easy way, especially the RkAndroidTool is not capable to use the MASK ROM interface of the SOC. For that you need to use the RkBatchTool. But the RkBatchTool requires an upgrade.img to be available what is most times not the case with CROMs.

So... You can continue to explain people who bricked their devices how they should have used their windows tools, but you will not make their devices work again. If you need to recover from a broken Loader or a NAND with erased BBT, you need to use linux and go step by step.

Depending on the cause of the failure you might get the device working with windows tools in two or three hours, but you can get it to work again in 20min with linux if you try it for the first time. If you know how, you can do it in 3min.

Astralix

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online:
89 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (76), Phone (13)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

swan12

fansosagelos

Snowm

andrewbest

heftpflaster

ruta6

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