yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Flareonz:
I have an RKNanoB chip, but the program said it's not tested. I want to be able to extract, modify and upload the firmware, what can I do?

thx in advance.

ps: here my scan: (I put the device in firmware update mode)

rkDumper (version 1.1.1.0)
Utility for Rockchip's firmware backup

(c) RedScorpio, Moscow, 2014-2022
RedScorpio.lab@gmail.ru

Application "updater.exe" don't found
==========================[ START ]==========================

Detected OS: Windows 8 Pro [build 9200] x64
Real OS: Windows 10 Pro [build 17134] x64
-- Devices enumerating --

USB devices table (found 7 devices):
1 Device #0: USB Root Hub (ports: 12)
1.7 Device #1: Dispositivo compuesto USB
VID = 0x1871, PID = 0x0141, REV = 0x000c (USB 2.0)
1.10 Device #2: Rockusb Device
VID = 0x071b, PID = 0x3226, REV = 0x0100 (USB 1.1)
1.11 Device #3: Dispositivo de almacenamiento USB
VID = 0x04cf, PID = 0x8819, REV = 0xa213 (USB 2.0)
Disk #1
2 Device #4: USB Root Hub (ports: 6)
3 Device #5: USB Root Hub (ports: 6)
3.2 Device #6: Dispositivo compuesto USB
VID = 0x0458, PID = 0x0186, REV = 0x2458 (USB 1.1 Low Speed)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
As far as I know, devices with RKNano have a completely different firmware structure. The utility was not designed for such devices and has never been tested with them (for lack of devices and desire).

Of course, I can try to make a test version. But I can't give any guarantees in any case.
[Upgrading, Modifying and Unlocking] Flareonz:
Ok, anyway, I would like to test it. I found some programs for editing and uploading firmware files on those RKNano chips, but I'm not able to dump it, and most of the websites of the manufacturers are down (my chip is 10 years old at least) and therefore I don't have any manual, datasheet or firmware updates for that chip.

Any idea what can I do next?

thx
[Upgrading, Modifying and Unlocking] speedgamer21:
Hello, I am having problems with backing up the rom of my chinese knock-off MXQ pro 4k 5G TVBox (RK3228A Chip inside it) it always gives an error command read failed. I tried several Driver Assistant and verrsion of rkDumperr and still no luck
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, I can't help you
[Upgrading, Modifying and Unlocking] vjy9193:
Is there any way to get RK3566 working? I have tested every single DriverAssistant version, even on different PCs and systems (windows 10/11) without luck. Either there is a "Command to read failed" or "Can't open device """ or "Unknown command" error, despite the device being detected.

The device has a USB-Serial CH340 driver

==========================[ START ]==========================

Detected OS: Windows 8 Pro [build 9200] x64
Real OS: Windows 10 Pro [build 19045] x64
-- Devices enumerating --

USB devices table (found 9 devices):
1 Device #0: USB Root Hub (ports: 25)
1.2 Device #1: USB Hub (ports: 4)
VID = 0x05e3, PID = 0x0610, REV = 0x6060 (USB 2.0)
1.3 Device #2: USB Input Device
VID = 0x046d, PID = 0xc077, REV = 0x7200 (USB 2.0 Low Speed)
Driver version = 10.0.19041.2251 (6-21-2006)
1.7 Device #3: Rockusb Device
VID = 0x2207, PID = 0x350a, REV = 0x0223 (USB 2.0)
Driver version = 5.11.0.0 (11-10-2020)
1.8 Device #4: USB-SERIAL CH340
VID = 0x1a86, PID = 0x7523, REV = 0x0264 (USB 1.1)
Driver version = 3.5.2019.1 (1-30-2019)
1.9 Device #5: USB Composite Device
VID = 0x046d, PID = 0xc31c, REV = 0x6400 (USB 1.1 Low Speed)
Driver version = 10.0.19041.1949 (6-21-2006)
1.12 Device #6: USB Hub (ports: 4)
VID = 0x14cd, PID = 0x8601, REV = 0x0000 (USB 2.0)
1.12.4 Device #7: Silicon Labs CP210x USB to UART Bridge
VID = 0x10c4, PID = 0xea60, REV = 0x0100 (USB 1.1)
Driver version = 6.7.4.261 (9-19-2016)
1.13 Device #8: USB Composite Device
VID = 0x0b05, PID = 0x19af, REV = 0x0100 (USB 2.0)
Driver version = 10.0.19041.1949 (6-21-2006)

Found: LOADER device (RK3566 2207:350a) #3
Command to read failed

Idk why the detected OS is windows 8?

Program worked fine for me on another device with RK3288 chip.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This error occurs if the drivers do not allow the utility to read the device memory.

This error occurs if the drivers are not installed.

This is how the Windows version responds to the request. In order to find out the real version of the OS, you have to use additional techniques.

I can't answer for sure - I don't have such devices, but I did the opportunity for Russian users, there were no complaints

And this - I didn't understand why it was necessary at all. Perhaps this is the reason.
[Upgrading, Modifying and Unlocking] vjy9193:
The device comes with the debug UART on the microUSB port. Without the CH341SER driver it is detected incorrectly as USB Serial in Windows and is unusable. ADB over USB seems to be not working, only way to detect the device for flashing (LOADER) is by entering the recovery with a USB A<->A cable plugged into one of the USB ports, but without recovery it is simply not detected at all in Windows.

Rockusb device

USB\VID_2207&PID_350A\62F759628C511243
USB\VID_2207&PID_350A&REV_0223

Is this really a driver issue though? I can read all the stuff correctly using RKDevTool v2.84 and DriverAssistant 5.1.1:

Get FlashInfo Start
Manufacturer: SAMSUNG
Flash Size: 7456MB
Total Sector: 0xe90e80
Block Size: 512KB
Page Size: 2KB
ECC Bits: 0
Access Time: 40
Flash CS: 0
Get FlashInfo Success

Get ChipInfo Start
Chip Tag: 33 35 36 38
Image Chip Flag: -RK3568
Get ChipInfo Success

Get Capability Start
Capability: 15 03 00 00 00 00 00 00
DirectLBA: Enable
VendorStorage: Disable
First4M: Enable
ReadLBA: Disable
ReadComLog: Disable
ReadIDBConfig: Disable
ReadSecureMode: Disable
NewIDB: Enable
SwitchStorage: Enable
Get Capability Success
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Yes, It doesn't matter

In this case, to downgrade the version, you need to do a little trick: register the VID/PID of your device in the old drivers. Unfortunately, I don't have devices with new processors for which the utility can't confidently read memory and I can't offer anything else.

If you have root rights for your device, then you can use adb to get a dump. Perhaps I'll take up writing a utility using this method (something like adbDumper)
[Upgrading, Modifying and Unlocking] drggong:
Thanks for your kind reply.

How can I register the new VID/PID of RK3568 to the old drivers?

Can you explain me about this?
[Upgrading, Modifying and Unlocking] saad.akh:
Hi,

i am seeing the same exact issue for my RK3566 as the few others who have posted right above this. I was trying with the latest 5.1.1 driver, downgrading to 4.8 via driver assistant and will post results here.
[Upgrading, Modifying and Unlocking] 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

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
[Upgrading, Modifying and Unlocking] dbzdivik:
Hi @RedScorpioXDA And All

I'm in serious trouble. I'm having RK3288 rock chip-based Tablet running android OS 4.4.4. I had the original ROM out of which I tried to create Custom ROM, but now my device is not even booting up. I'm having only One power button and when I press nothing is happening.

Please can you help me out.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, I do not know how to help you
[Upgrading, Modifying and Unlocking] Dogshome:
Hi All, are there plans to add the RK3588S?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Who are you asking a question to?
[Upgrading, Modifying and Unlocking] Dogshome:
Now I remember to be polite, I should have directed the question to yourself 😎
[Upgrading, Modifying and Unlocking] Dogshome:
VID = 0x2207, PID = 0x350b, REV = 0x0100 (USB 2.0) Rockusb device

Orange Pi 5, 8GB RAM RK3588S (SBC).
[Upgrading, Modifying and Unlocking] rmghrr:
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

Found: LOADER device (RK3318/RK3328/PX4 2207:320c) #1

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

Command to read failed

-- Rockchip device resetting --

Found LOADER Rockchip device

Command to reset failed
[Upgrading, Modifying and Unlocking] 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:
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
In this mode, the memory is not available for reading

Again, we need to return to the issue of driver selection (try 4.3)
[Upgrading, Modifying and Unlocking] 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 ?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This entry means that the drivers are not installed
[Upgrading, Modifying and Unlocking] 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
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I believe. Record

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

But record

means that the drivers are not installed
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I expect feedback
[Upgrading, Modifying and Unlocking] Dogshome:
(y) Working on it!
[Upgrading, Modifying and Unlocking] 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.
[Upgrading, Modifying and Unlocking] 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.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, I can't help in this case
[Upgrading, Modifying and Unlocking] t-mobile_mda:
hey guys..

how can i dump from RK3326 device..?

info;
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What prevents you from trying?

And in general, report the VID/PID
[Upgrading, Modifying and Unlocking] t-mobile_mda:
hey..

catually i did but not success.. i just wanna format frp area.. so i need to find that area.. can we find it..?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What is "frp area"?
[Upgrading, Modifying and Unlocking] t-mobile_mda:
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:

0x00002000@0x00002000(uboot),

0x00002000@0x00004000(misc),

0x00008000@0x00006000(resource),

0x00006000@0x0000E000(kernel),

0x00006000@0x00014000(boot),

0x00010000@0x0001A000(recovery),

0x00020000@0x0002A000(backup),

0x00040000@0x0004A000(cache),

0x001FE000@0x0008A000(userdata),

0x00008000@0x00288000(metadata),

0x00002000@0x00290000(kpanic),

0x00200000@0x00292000(system),

0x00020000@0x00492000(radical_update),

-@0x004A2000(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
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Usually this information is contained in a file parameter.txt. But there is no such information in the latest firmware (RKFP)
[Upgrading, Modifying and Unlocking] t-mobile_mda:
can i use dump for another same device..? another is dead becasuse of bad fw and i dont fin the correct fw.. but i have working device for recover it..

# This is only part of the command line generated by the utility rkDumper

CMDLINE: mtdparts=rk29xxnand:

0x00004000@0x00000000(EFI_part),

0x00002000@0x00004000(uboot),

0x00002000@0x00006000(trust),

0x00002000@0x00008000(misc),

0x00002000@0x0000a000(dtb),

0x00002000@0x0000c000(dtbo),

0x00000800@0x0000e000(vbmeta),

0x00010000@0x0000e800(boot),

0x00030000@0x0001e800(recovery),

0x00028000@0x0004e800(backup),

0x00002000@0x00076800(security),

0x00070000@0x00078800(cache),

0x00340000@0x000e8800(system),

0x00008000@0x00428800(metadata),

0x00070000@0x00430800(vendor),

0x00020000@0x004a0800(oem),

0x00000400@0x004c0800(frp),

0x0181f3df@0x004c0c00(userdata)

dump info;

Found: LOADER device (RK3308/RK3326/RK3388/PX30 2207:330d) #17

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

"EFI PART" sign found (RKFP FW dump)

Configuration file for RKAndroidTool v.1.xx (8-bit) created

Configuration file for RKAndroidTool v.2.xx (16-bit) created

Partition "EFI_part" (0x00004000) saved (format: RockChip RKFP dump)

Partition "uboot" (0x00002000) saved (format: Rockchip uboot image file)

Partition "trust" (0x00002000) saved (format: unknown)

Partition "misc" (0x00002000) saved (format: unknown)

Partition "dtb" (0x00002000) saved (format: unknown)

Partition "dtbo" (0x00002000) saved (format: unknown)

Partition "vbmeta" (0x00000800) saved (format: unknown)

Partition "boot" (0x00010000) saved (format: Android boot image)

Partition "recovery" (0x00030000) saved (format: unknown)

Partition "backup" (0x00028000) saved (format: unknown)

Partition "security" (0x00002000) saved (format: unknown)

Partition "cache" (0x00070000) saved (format: unknown)

Partition "system" (0x00340000) saved (format: unknown)

Partition "metadata" (0x00008000) saved (format: unknown)

Partition "vendor" (0x00070000) saved (format: unknown)

Partition "oem" (0x00020000) saved (format: unknown)

Partition "frp" (0x00000400) saved (format: unknown)

Partition "userdata" (0x0181f3df) saved (format: unknown)

-- Rockchip device resetting --

Found LOADER Rockchip device

Command to reset sent successfully
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
It depends on many conditions

1. Was there the same firmware on the second device

2. Is the bootloader not corrupted on the second device

3. Is config.txt formed correctly

...

etc.

Of course, I can't give any guarantees (especially considering. that the device was flashed with the "wrong" firmware - most likely the bootloader is damaged).
[Upgrading, Modifying and Unlocking] roland deschan:
Rockchip Andoer Z4 rk3368 dump ok. Tx..
[Upgrading, Modifying and Unlocking] seaky77:
On Windows 10 or above you can't simply install a modified driver beacuse all the driver has issuer signature protection so if you modify the driver you just brake the signature check.

You have to install it in special boot mode:

- press win+X navigate to "Shutdown" and "Shift+left click" on "restart" options

- in advanced boot menu select "Troubleshoot" option

- in Troubleshoot section select "Advanced options"

- and select "Start-up Settings"

- click restart

- In Startup Settings select "Disable driver signature enforcement" (F7)

Your system will boot into Windows and enables to install unsigned drivers such as this modified usb driver.

Notice:

Every reboot revert back to normal protected state so if you want to install a modified driver you have to boot into special mode as described above.

Good luck,

Seaky
[Upgrading, Modifying and Unlocking] ExplodingLemur:
Hi, I'm having some trouble extracting the flash contents from an RK3566 device. I've tried a few different versions of the Rockchip Driver Assistant: 4.5 (which did not recognize the RK3566), 4.8, 5.0, and 5.1.1. I'm using rkdumper 1.1.1.0. I've tried connecting to different USB ports on my PC and using different USB cables, but I always get the error "Command to read failed"

I'm attaching debug output from rkdumper as well as the serial console output from the device. Any assistance would be appreciated, thanks!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Variants:

1. Try adding to 4.5 drivers VID/PID for rk3566 (0x2207/0x350A, if I'm not mistaken). And you can also try a lower version of the drivers

2. If there is a root, try adbDumper (it should work flawlessly)
[Upgrading, Modifying and Unlocking] ExplodingLemur:
Edited the config.ini in the Rockchip_DriverAssistant_v4.5 folder to:

[System]
#自定义VendorID和ProductID,值十六进制表示,例:CUSTOM_VID=0x0BB4,CUSTOM_PID=0x0C01
CUSTOM_VID=0x2207
CUSTOM_PID=0x350A
ADVANCED_OPTION=

The board shows up as "Unknown Device" in Device Manager.

If I edit any of the .inf files then the driver won't install (likely due to failing signature checks).

This board is not running Android so I don't think adbDumper will work. For some reason the rkdumper.log file would not attach to my last post, here's the latest log using v4.5 of the driver.

Edit: Ok, it seems I can't attach that at all. Here it is in Pastebin: https://pastebin.com/Tq0qt6Ut
[Upgrading, Modifying and Unlocking] lukipl666:
Hello RedScorpioXDA

I have RockChip RK3308B with VID 2207 and PID 330E

Can't find RockChip device

PID is 330E not 330D

Pls help me :)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
RT3308B or RK3308B?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, I can't help you. I don't have devices with similar problems to simulate
[Upgrading, Modifying and Unlocking] lukipl666:
Sorry :) my is RK3308B
[Upgrading, Modifying and Unlocking] lukipl666:
THX RedScorpio,

This version see my chip. Found: MASKROM device (RK3308B 2207:3330e)

Unfortunately, a message is: Rockchip device is not in MSC or Loader mode

The motherboard is from a Xiaomi vacuum cleaner, and the bootloader is locked

Option swt and rst not work
[Upgrading, Modifying and Unlocking] ExplodingLemur:
Is there some other way to add the VID/PID pair to the Rockchip driver installer? Like I said, adding it to the config.ini file doesn't do anything, and editing the INFs prevents the driver from installing at all.
[Upgrading, Modifying and Unlocking] seaky77:
Did u read my comment?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Alas, all the commands with which the utility works can be processed by the device only in the MSC or Loader modes
[Upgrading, Modifying and Unlocking] lenco2001:
I first installed the 4.5 driver in win10, then on the unknown device I manually selected that modified file with added VID/PID. Got some warnings but installed. Rkdumper is dumping a rk3566 right now
[Upgrading, Modifying and Unlocking] Pandoriaantje:
Doesn't seem to work for me.

my device is some obscure android box.

Brand: HDD SAT
Model: HDK100

android reports RK23328, Android HW info app reports RK23318 SOC.

4GB ram 32GB flash.

USB ID from rkdump log:

2023.05.07 09:21:07 2.10.3 Device #12: Rockusb Device
2023.05.07 09:21:07 VID = 0x2207, PID = 0x320c, REV = 0x9999 (USB 2.0)
2023.05.07 09:21:07 .DEBUG. SymLink = "\\?\USB#VID_2207&PID_320C#EA4R1B8R7J#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
2023.05.07 09:21:07 .DEBUG. DriverKeyName = "{79dfc2a8-2574-493c-ae71-52958e41dd00}\0000"
2023.05.07 09:21:07 .DEBUG. Driver version = 5.11.0.0 (11-10-2020)

As you can see, I have RK drivers 5.11 installed.

AndroidTool/RKDevTool 2.84, will happily dump any range I give it, but rkDumper errors out:

2023.05.07 09:21:07 Found: LOADER device (RK3318/RK3328/PX4 2207:320c) #12
2023.05.07 09:21:07 .ERROR. Command to read failed

1MB RKDevTool 2.84 dump:

Chip info:

Flash ID:

Flash info

unfortunately RKDevTool 2.8.4.0 still hits the 32MB limit.

I'dd like to get a full backup of this device, before experimenting with it, upgrading to ATV 12 (factory is android 10) and sharing with the community, for preservation.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Use old version of drivers (4.5)
[Upgrading, Modifying and Unlocking] Pandoriaantje:
Thanks, but could you also explain why? Is there any difference in the driver? Will this also fix RKDevTool limitation? You'dd think an updated driver would offer more support, instead of les... why is RKDevTool working, and not rkdump?

It would be nice to actually get a technical explanation, if possible. No offence intended, just currious.

This is my first RK device.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Yes, there are some differences in the drivers. Unfortunately, I don't have any devices for conducting experiments. I think this is due to the appearance or increase of some delays. How to link old devices with new drivers is described above

I can't know that, but it's unlikely

The developers of RKDevTool have close ties with the developers of the chips themselves, I only once just did experiments. Time has passed...
[Upgrading, Modifying and Unlocking] Pandoriaantje:
I thought as much. So rkdump *could* potentially be adapted to the new(er) drivers, but is currently not feasible.

Driver 4.5 did work though. I was able to get a full backup.

a disclaimer about using older drivers versions could maybe avoid this confusion.

unfortunately all of this is closed source, so we're at the mercy of the tool devs.

But thanks for this wonderfull tool (and your other work).

*EDIT*

Guess I spoke to soon.

most of the files (maybe after the 32MB?)

are just filled with 0xCC
[Upgrading, Modifying and Unlocking] Pandoriaantje:
i'dd root the device, but unfortunately the rkdump boot.img is corrupted after offset 0x300000, and only contains 0xCC.

There is no official download available for the device, so i'm kinda stuck here.

rkdump does not give me a clean dump, and RKDevTool has the 32mb limit..

*EDIT*

Tried rkflashtool on linux and same result, after 32MB its spits out 0xCCCCCC. So yeah... i'm screwed.

*EDIT2*

After Hours of screwing around with different driver and RKDevTool versions I just gave up. I was hoping to dump this fw, for archival purposes, to no avail. I just uploaded a official H96 MAX RK3318 android 11 firmware to the device, and it booted just fine, so that's a relief. Everything works. The front LCD, wifi, etc.. That's that for me.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Now the firmware often has read protection

If there is root, use adbDumper
[Upgrading, Modifying and Unlocking] Pandoriaantje:
I learnt too late that these RK devices support SD boot, and the ARMBian project has a tool called Multitool that should be able to dump the fw. ohwel, i've since given up on this device. It was a nice little project to get to know RK devices, but the device itself is a major letdown. even nes or snes roms run like cr*p on retroarch. on paper it looks like a decent quad core 64bit SOC, but in practice its not much more then a paperweight. I got it to run the H96 MAX RK3318 android 11 firmware (since this just seemed like a clone), and was hoping for a smoother experience, but it proved me wrong. :D I got this device for free from someone who had no use for it anymore, And now I see why. It got my hopes up, to use it as basic emu box, but even that it can not do...