[TOOL] rkDumper (utility for backup firmware of RockChip's devices)

[RedScorpioXDA]

VID = 0x2207, PID = 0x350b, REV = 0x0100 (USB 2.0) Rockusb device
Orange Pi 5, 8GB RAM RK3588S (SBC).

rkDumper_1.1.1.6.zip

Compressed (zipped) Folder

1drv.ms

 

[RedScorpioXDA]

RKDumper 1.1.1.0 unable to dump H96 MAX H1/H2 Colorful edition. Get below, Tried different drivers only DriverAssitant_v5.1.1 seems to be discovering the box but dump fails

For example, drivers in DriverAssitant_v4.3.zip

Find the rockusb.inf file in the \DriverAssitant_v4.3\Driver\x{bits}\{OS} subdirectory
In the [Rockchip.NTx86] block and/or [Rockchip.NTamd64] block add a string(s) with your VID/PID
For example (for RK3588)
%Rockusb_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_0x350b


PS. Guys, I don't have devices with modern RockChip chips. I can't test them and give specific advice. If you have root rights on your devices, try using adbDumper

 

[Dogshome]

Hi RedScorpioXDA. RKDumper detected the SOC OK, but errored that it was not in transfer mode. It was in MASKROM which is the usual way to download with the RK tool. I'll try the ADB tool as it is rooted.

I saw your note about not having a chip to test with so I'll just keep an eye on the thread now. If I do get an upload from it one way or another - I'll post.



UPDATE. The RECOVERY button puts the OPI5 into LOADER mode. This is what happens in RKDumper:

 

[RedScorpioXDA]

It was in MASKROM

In this mode, the memory is not available for reading

This is what happens in RKDumper:

Again, we need to return to the issue of driver selection (try 4.3)

 

[GaraQuor]

Hi,

Tried 5.1.1, 4.8, 4.3 and no one working. (RK3588S)

5.1.1: Command to read failed
4.8, 4.3: Can't open device ""

Any idea ?

 

[RedScorpioXDA]

Can't open device ""

This entry means that the drivers are not installed

 

[GaraQuor]

I'm sure that the driver was installed (working with RK3399). But whatever I dumped manually the emmc using dd with the correct offset and use RKDevTool to burn using dumped parameter.txt.

Thanks anyway

 

[RedScorpioXDA]

I'm sure that the driver was installed (working with RK3399)

I believe. Record

5.1.1: Command to read failed

means that the drivers are installed, but there are difficulties with reading
But record

4.8, 4.3: Can't open device ""

means that the drivers are not installed

 

[RedScorpioXDA]

VID = 0x2207, PID = 0x350b, REV = 0x0100 (USB 2.0) Rockusb device
Orange Pi 5, 8GB RAM RK3588S (SBC).

I expect feedback

 

[Dogshome]

Working on it!

 

[Dogshome]

Hiya RS, the earlier drivers 4.3 don't detect properly. The Rockchip tool does not see any device. With the 5.12 drivers it responds as expected, but RKDumper gives the error as I posted in the pic above.

 

[RedScorpioXDA]

For example, drivers in DriverAssitant_v4.3.zip

Find the rockusb.inf file in the \DriverAssitant_v4.3\Driver\x{bits}\{OS} subdirectory
In the [Rockchip.NTx86] block and/or [Rockchip.NTamd64] block add a string(s) with your VID/PID
For example (for RK3588)
%Rockusb_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_0x350b

the earlier drivers 4.3 don't detect properly

 

[Dogshome]

Hi RS, I edited the inf file firstly by adding the required PID VID. This produced an error. So, I modified the line for an existing device (86 and 64) sections instead. this produced the same error. I note there is a security catalogue file. I can see the various PID and VIDs in it. I tried manually editing this as well but the same error occurs.

 

[RedScorpioXDA]

I tried manually editing this as well but the same error occurs.

Unfortunately, I can't help in this case

 

[t-mobile_mda]

hey guys..


how can i dump from RK3326 device..?

info;

 

[RedScorpioXDA]

how can i dump from RK3326 device..?

What prevents you from trying?
And in general, report the VID/PID

 

[t-mobile_mda]

What prevents you from trying?
And in general, report the VID/PID

hey..

catually i did but not success.. i just wanna format frp area.. so i need to find that area.. can we find it..?

 

[RedScorpioXDA]

catually i did but not success.. i just wanna format frp area.. so i need to find that area.. can we find it..?

What is "frp area"?

 

[t-mobile_mda]

What is "frp area"?

maybe frp is in another part like config part.. device has FRP and i need to remove it..
can i see/extract the parts like that..?

PARMv FIRMWARE_VER:5.0.2
MACHINE_MODEL:ES724
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 312x
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
#CMDLINE:console=ttyFIQ0 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0
init=/init initrd=0x62000000,0x00800000
mtdparts=rk29xxnand:
[email protected](uboot),
[email protected](misc),
[email protected](resource),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](userdata),
[email protected](metadata),
[email protected](kpanic),
[email protected](system),
[email protected](radical_update),
[email protected](user)
CMDLINE:console=ttyFIQ0 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x0000200

 

[RedScorpioXDA]

can i see/extract the parts like that..?

Usually this information is contained in a file parameter.txt. But there is no such information in the latest firmware (RKFP)