A GUI tool for flashing rk3066/rk3188 kernel image under Linux

[linuxerwang]

I created a GUI tool for flashing kernel images (or any image files) to rk3066/rk3188 base devices under Linux. It provides no more function than the existing rkflashtool_rk3066 program except that it's GUI based.

https://github.com/linuxerwang/rkflashkit

Features
- Programmed with python, GTK2 and libusb1.
- Automatically detect device connection.
- Reboot device.
- Flash kernel image file to specified partition.
- Erase partition.
- Backup partition.
- Compare a partition with a image file.

[leolas]

Re: A GUI tool for flashing rk3066/rk3188 kernel image under Linux

I created a GUI tool for flashing kernel images (or any image files) to rk3066/rk3188 base devices under Linux. It provides no more function than the existing rkflashtool_rk3066 program except that it's GUI based.

https://github.com/l...wang/rkflashkit

Features
- Programmed with python, GTK2 and libusb1.
- Automatically detect device connection.
- Reboot device.
- Flash kernel image file to specified partition.
- Erase partition.
- Backup partition.
- Compare a partition with a image file.

WOW, this one is really great. The previous version was good, this onw is excellent.

Great work.

leolas

[abdul_pt]

Great job. Thank's for sharing it with us.

[rbees]

I created a GUI tool for flashing kernel images (or any image files) to rk3066/rk3188 base devices under Linux.

I have installed the updated version but I can't get it to detect my PiPo M9

I have tried with usb-debugging turned on and turned off

I have tried with usb storage turned on and off on the tablet

I did not try with the tablet actually mounted by the Debain64 Jessie system

I do have an entry in lsusb Bus 002 Device 009: ID 2207:0000 but the device is not identified.

Thanks
Randy

[leolas]

I have installed the updated version but I can't get it to detect my PiPo M9

I have tried with usb-debugging turned on and turned off

I have tried with usb storage turned on and off on the tablet

I did not try with the tablet actually mounted by the Debain64 Jessie system

I do have an entry in lsusb Bus 002 Device 009: ID 2207:0000 but the device is not identified.

Thanks
Randy

It is yur tablet in bootloader mode?

[linuxerwang]

I have installed the updated version but I can't get it to detect my PiPo M9

I have tried with usb-debugging turned on and turned off

I have tried with usb storage turned on and off on the tablet

I did not try with the tablet actually mounted by the Debain64 Jessie system

I do have an entry in lsusb Bus 002 Device 009: ID 2207:0000 but the device is not identified.

Thanks
Randy

The current rkflashkit recognizes:

RK_VENDER_IDS = set([
0x2207,
0x3207,
])
RK_PRODUCT_IDS = set([
0x290a,
0x281a,
0x300a, # RK3066
0x310b, # RK3188
])

You can change file rktalk.py and add 0000 to RK_PRODUCT_IDS.

[Mmurdo]

linux flash

I have an mk808b, tool seems to work but have to be in flash mode (IE pressing down with paperclip and then connecting usb to rear usb port of computer in Ubuntu). lsusb will tell the tale I get 2700:0000 or 2700:0001 in normal running modes but
2207:300a in flash mode.

[neomode]

AW: A GUI tool for flashing rk3066/rk3188 kernel image under Linux

Is there a way to port it to OS X ?
It is also Unix based and we have no flash tool for it.

Neomode

Gesendet von meinem GT-I9305 mit Tapatalk 2

[abdul_pt]

Is there a way to port it to OS X ?
It is also Unix based and we have no flash tool for it.

Neomode

Gesendet von meinem GT-I9305 mit Tapatalk 2

See this post, it might help you.

[rbees]

leolas said,

It is yur tablet in bootloader mode?

I am not sure how to put it in bootloader mode. After my last post I tried holding the esc and power at the same time to boot and came to what I think is the bootloader screen but the tablet was still not recognized, although it did have a different usb id. I did not record it, sorry to say.

There are 2 usb ports on the M9, I am currently using the one labeled "usb". I have tried the one labeled host, but the tablet was not recognized with that one either.

Thanks leolas

linuxerwang,

I have Bus 002 Device 011: ID 2207:0010

So if I am understanding correctly my rktalk.py have this entry

RK_VENDER_ID = 0x2207
RK_PRODUCT_IDS = set([
0x290a,
0x281a,
0x300a, # RK3066
0x310b, # RK3188
#######################
0x0010, # PiPo M9
#######################
])

I Think I posted the usb-id incorrectly before.

******************

So trying again connected to the port labeled "usb". Still running the factory rom. Before the change above.

1. turned off usb debugging on tablet
2. turned on usb storage on tablet
3. did NOT mount the tablet
4. launched rkflashkit
5. tablet not detected

And again connected to the port labeled "host". The tablet does not give me the option to turn on usb storage, and is not recognized by rkflashkit

Rebooting the tablet by holding the esc and power buttons, I got a PiPo logo screen and then a screen with the android logo with it's side open and a red triangle with ! in it. Connecting usb cable does not bring up my usb correction option. It seams that the tablet was on a timer, after waiting a little bit it went and completed it normal boot. Rebooting again, launching rkflashkit, tablet not detected. Still in "host" port, changing.

The tablet is detected with this id when booted by holding both buttons.
Bus 002 Device 013: ID 18d1:d001 Google Inc.

After rebooting tablet it is still not detected by rkflashkit. Holding the power button or both buttons does not cause the tablet to reboot from the "loader" screen. It did the same thing last night when I tried it before. After some time I pushed the power button and it finished booting.

I reconnected the usb cable to the "usb" port to confirm that it was not detected and rechecked the usb id, it is still identified as a google device. When I disconnected the cable the tablet finished booting.

Thanks
Randy

[rbees]

Here is what I know about how the M9 is detected by my Debain Jessie64(testing) laptop.

Bus 002 Device 018: ID 2207:0000 Connected to "usb" port on tablet, usb debugging turned off

When connected to "Host" port on tablet, with usb debugging turned off the tablet is not detected.

Turning on usb debbuging and connected to "Host" port the tablet is not detected by lsusb

Bus 002 Device 019: ID 2207:0010 Again connected to "usb" port on tablet, with usb debbuging turned on.

Booting to bootloader mode as instructed by "First Time Users Guide" by holding the "esc" button and the power button to boot.

Connected to the "usb" port the tablet is recognized by lsusb as

Bus 002 Device 020: ID 18d1:d001 Google Inc.

Not sure that usb debugging is relevant.

Not recognized by lsusb when connected to "Hosts" port.

After the reboot caused by the time-out I enabled usb debbuging again and rebooted to bootloader mode and that did not change the way the tablet was detected by lsusb.

So going back to rktalk.py and looking at the "Vendor" and "Procuct" ID'S and considering how the tablet is recognized when booted in its different modes there does not seem to be a way to actually add both of the "Vendor" and "Product" ID'S that I get.

All of this leads me to believe that I may have an M9 with the old pcb board. So I am asking how I determind if this is so?

It also appers that I may not have the most current version of rkflashkit. From my installed rktalk.py

PART_BLOCKSIZE = 0x400 # must be multiple of 512
PART_OFF_INCR  = PART_BLOCKSIZE >> 9
RKFT_BLOCKSIZE = 0x4000 # must be multiple of 512
RKFT_OFF_INCR  = RKFT_BLOCKSIZE >> 9
RKFT_DISPLAY   = 0x1000

RK_VENDER_ID   = 0x2207
RK_PRODUCT_IDS = set([
  0x290a,
  0x281a,
  0x300a, # RK3066
  0x310b, # RK3188
])

PARTITION_PATTERN = re.compile(r'0x([0-9a-fA-F]*?)@(0x[0-9a-fA-F]*?)\((.*?)\)')

Posted by linuxerwang in a previous

The current rkflashkit recognizes:

 RK_VENDER_IDS = set([
 0x2207,
 0x3207,
 ])
 RK_PRODUCT_IDS = set([
 0x290a,
 0x281a,
 0x300a, # RK3066
 0x310b, # RK3188
 ])

Clearly what I have, and I have redownloaded from github is not what I am suppose to have. I downloaded from https://github.com/linuxerwang/rkfla...aster/binaries

Perhaps the github needs to be updated.

Thanks

Waiting for guidance

Thanks
Randy

[Mmurdo]

rkflashtool

"You can change file rktalk.py and add 0000 to RK_PRODUCT_IDS."

I went to the link he has at the top and went to the right of that page and downloaded the zip file. You get a whole bunch of stuff some of which is just used to install it.
It is not necessary to install it. All you really need is the run.py script below which you should have src/rkflashkit/ and everything in the rkflashkit directory. For running the GUI part pygtk is required which may be difficult in OSX. All I have done so far is back up my nand partitions and reboot.
Depending on whether I am in media device mode or mass storage mode my mk808b gives lsusb of 2207:0001 or 2207:0000 but if I add
RK_PRODUCT_IDS = set([
0x290a,
0x281a,
0x300a, # RK3066
0x310b, # RK3188
0x001,
])
or the corresponding 0000 the rkflashtool gets stuck someplace and the gui never pops up so for me only doing the paperclip thing works. Also In Slackware because of usb permissions I had to run as root
kdesu python run.py.

[fazerg]

For RK3188 the easiest and probably the best way is to start RKFlashKit and run

adb reboot bootloader

from terminal window while having tablet in normal operation mode.

linuxerwang,
I'm trying to compare addresses and sizes of blocks with those I have from /proc/mtd on my Pipo M7pro.
There are only sizes actually which are the same. Trying to get addresses from /proc/mtd by adding sizes of preceeding blocks and can not get the same? the difference in bytes is significant. i.e. for system sum is 2415919104, address from RKFlashKit 2420113408. Difference 4194304 or 40000 hex. What I'm doing wrong? Is there anything else to add? At the same time compared actual recovery block on device with one from unpacked factory ROM, there is no difference except file sizes, recovery.img from original firmware is much smaller which is easy to explain.
Just trying to not brick device while flashing CWM recovery or in future mod system and/or kernel

[rbees]

Thanks All

I have discovered that the key to using the rkflashtool with the PIPO M9 is to get the device booted into flash mode.

For the M7pro U8 M8pro M9 M9pro(android4.2.2)ress the “ESC“&“power” key for a few seconds,no need of pressing reset key. Per RileyRom in another thread.

Thanks

[900supersport]

I find the easiest and safest way to get to flashmode is as follows.

On the tab open a terminal session
Enter su, press enter and confirm root access if prompted
Enter reboot bootloader, press enter

You will need root for this.
If you have not already got a terminal emulator then install from play.