yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] vjy9193:
Does this software even work for anyone? I tried it multiple times already with various boards (rk3566, rk3288) and I'm unable to get any single thing working.

Or is it a problem that the boards are running Linux distros and not Android (hence why I cannot use adbDumper)?

Dumping via RKDevTool works, but produces only 32MB. Same as reading chip info and everything else.

Cable works too because I can flash the devices, but I would like to dump my fw after doing some changes so I can restore it easily.

I have tried every single driver version there is available on the internet, either the device is not detected at all or there is a "Command to read failed" error.

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 19045] x64
-- Devices enumerating --

USB devices table (found 8 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.7 Device #2: Rockusb Device
VID = 0x2207, PID = 0x320a, REV = 0x9999 (USB 2.0)
1.9 Device #3: USB Hub (ports: 4)
VID = 0x14cd, PID = 0x8601, REV = 0x0000 (USB 2.0)
1.9.4 Device #4: Silicon Labs CP210x USB to UART Bridge
VID = 0x10c4, PID = 0xea60, REV = 0x0100 (USB 1.1)
1.11 Device #5:
VID = 0x046d, PID = 0xc077, REV = 0x7200 (USB 2.0 Low Speed)
1.12 Device #6:
VID = 0x046d, PID = 0xc31c, REV = 0x6400 (USB 1.1 Low Speed)
1.13 Device #7:
VID = 0x0b05, PID = 0x19af, REV = 0x0100 (USB 2.0)

Found: LOADER device (RK3288 2207:320a) #2
Command to read failed

I have also tried the 1.1.1.7 version and it's the same.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Install other (old) drivers
[Upgrading, Modifying and Unlocking] vjy9193:
I have already tried v5.1.1, v4.8, v4.5, v4.4, v4.3 and probably more. Its the same or worse on every one, while RKDevTool works perfect and allows me to flash & read everything pretty much no matter what driver version... rk3288 is an old chip so I guess most of the drivers support it.

What's even funnier is that I have tried to use the rkflashtool ( https://github.com/linux-rockchip/rkflashtool ) which also failed to work in every way I could think of. It either couldn't read the flash info or if it did, the flash ID was all 00 and nothing else worked.

I have tried it on my Windows 10, on another Windows 7 all with different drivers, on Linux Ubuntu x64 and also on Xubuntu x32 running in a virtual machine.

Everywhere it failed, while RKDevTool worked okay.. so I guess there's something more that RKDevTool does that your and other apps don't

It's not a single device, I have tried a RK3566 board, a RK3288 board and another RK3288 board of entirely different manufacturer. I'm able to flash all of them with RKDevTool. RK3566 works only on 5.1.1 driver though.
[Upgrading, Modifying and Unlocking] vjy9193:
I got some (partial) success finally by using a different, clean Windows 10 machine. 4.1, 4.2, 4.3, 4.4 and 4.5 driver worked too, on 4.8 I start getting "Command to read failed" while it still works fine in RKDevTool.

rkDumper reads the flash info, but not correctly (see RKDevTool v2.58 output in separate window) and returns "Response reading error".

The eMMC is an 8GB Samsung chip.

ReadChipInfo in RkDevToool returns 33 32 30 41

Another RK3288 device with 15028MB Samsung eMMC returns the same invalid values in rkDumper.

Can I somehow "sniff" the commands sent by RKDevTool and rkDumper to compare them? I don't see how this is a driver issue if RKDevTool works with all of them, and rkDumper doesn't.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
It will be very interesting. I don't have devices for experiments.
[Upgrading, Modifying and Unlocking] vjy9193:
I have captured the traffic using USBPcap plugin for Wireshark. I'm not familiar with diagnosing USB captured traffic, but I have confirmed there is some correct data, although in reversed order in the packets when executing actions in RKDevTool.

ReadFlashID -> 45 4D 4D 43 20

ReadFlashInfo

ReadChipInfo -> tag 33 32 30 41

I unfortunately wasn't able to test rkDumper's traffic as it simply stopped working (again). I think installing the 5.1.1 driver or USBPCap completely broke rkDumper. It just returns "Unknown command" no matter what driver I use or USB port. It doesn't even try sending any USB commands, Wireshark is empty.

/debug reports correct driver, which "worked" earlier. I'd probably need to reinstall Windows to get it working again.

I'm attaching the pcap file, it's just the few packets from that specific port. Commands in the order as above: ReadFlashID -> ReadFlashInfo -> ReadChipInfo
[Upgrading, Modifying and Unlocking] pseudolobster:
Hi everyone!

I've made a breakthrough on dumping devices that have a 32mb limit or dump `CC` `CC` `CC`. It turns out this "read protect" function is actually implemented in uboot. The uboot partition is typically in the first 32mb, so you should have no problem dumping it and it is possible to edit out the 32mb limit and flash the uboot partition back.

Here's how I did it:

First of all, I could not have figured this out if it weren't for DorianRudolph on github, who documented installing linux on a PineNote, which happens to have the same RK3566 chip I've been struggling with. They figured out where in the source code rockchip implements this, so they unpack the uboot.bin from uboot.img, disassemble it, and find that function. They patche it to always jump to a certain location instead of spitting out `CC`. The result is the chip behaves like all rockchip socs before it.

After looking at my uboot.bin versus theirs, I figured out we're running different versions of uboot, and I couldn't use their uboot image, or their scripts without modification. I dumped as much as I could with rkdumper, then took uboot.img, edited uboot_img.py to point to my img file and ran it. It spit out uboot.bin.

I downloaded and installed ghidra, created a project, imported uboot.bin, set its language as AARCH64 V8A little-endian. Double click to decompile, then go looking for something that looks like this picture, or in my case, like this. Then patch the `b.ls` instruction to be a `b` instruction. I found the easiest way to find the correct function was to search for `FD 7B BE A9 FD 03 00 91 ?? 18`. There were a ton of functions that started with the same 8 btes, which is probably like "push the stack" or something, but there were only two that used `0x18` as the parameter for the `ldr` instruction.

After patching it with ghidra I took the uboot.img, put it in a directory with uboot_img.py, edited it to comment out `check_hash_and_dump()` and run patch();, edit lines 29 and 30 to match the size and positon of uboot.bin. The `sz` is the size in bytes, in hex. The `pos` can be found by running `dtc -I dtb -O dts uboot.img`

That's pretty much it. I used RkDevTool to flash the modified uboot, by right clicking the first screen, hitting load config, choose the config output by rkDumper, hit dev partition, then check the checkbox to the left of uboot, click the blank space to the right of uboot, choose your uboot.img, and hit Run.

Next time you boot into LOADER mode, you'll be able to dump all partitions!
[Upgrading, Modifying and Unlocking] sajati:
Hello, i came here from a youtube tutorial using old version which doesn't have "updater.exe", i tried that same version and it doesn't work.

latest version does work but i have red line in terminal

Application "updater.exe" don't found​

is it ok ?

what is this "updater.exe" for ?

and how to use it ?

should i just extract the "updater.exe" from the zip to the rkdumper folder ?

is it important ?
[Upgrading, Modifying and Unlocking] TBM 13:
Wow, that's an awesome discovery! I have one rk3368 device with the same issue. I knew that I could dump uboot as it was inside that 32MB barrier but I would have never thought that the issue was inside it and I could modify it
[Upgrading, Modifying and Unlocking] noki severgun:
Hi there,

I'm kinda newby here and having similar issue as some of you, based on the posts that I've read.

My goal is to extract a copy of a previously staged Android TV box and apply that image to the the rest of the boxes. I've started working with H96max v11 with RK3328 chip inside.

I've tried installing the RKDevTool and the RkDumper but the box hasn't been recognised by the Dumper even though the DevTool recognises and reads the info of the box. I've also heard about the TWRP and I tried searching for the software for that chipset but no luck.

I have 3 questions:

1. When I checked the ReadChipInfo on the RKDevTool, it said that the box's chipset is RK332H. Is that RK3328 or it is something different as the internet doesn't know about the RK332H chipset

2. Can someone guide me which TWRP file will work with the above mentioned chipset/box and point me to the download folder/location?

3. If there is a better method for extracting the complete image and re-applying to the other boxes, would appreciate the info.

Thanks!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What kind of VID/PID does the device have?
[Upgrading, Modifying and Unlocking] noki severgun:
Hi there,

Here are the USB\VID_2207&PID_320C of the device that I'm working on, based on the Windows Device Manager.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
These VID&PIDs have been supported by the utility for a very long time. Provide a log file
[Upgrading, Modifying and Unlocking] noki severgun:
Hi RedScorpioXDA,

I guess you are referring to the logs from the rkDumper? If so, here they are:

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 Home [build 9200] x64

Real OS: Windows 10 Home [build 19045] x64

-- Devices enumerating --

USB devices table (found 6 devices):

1 Device #0: USB Root Hub (ports: 18)

1.2 Device #1: Rockusb Device

VID = 0x2207, PID = 0x320c, REV = 0x9999 (USB 2.0)

1.3 Device #2: USB Mobile Broadband Network Adapter Module

VID = 0x03f0, PID = 0x9d1d, REV = 0x0228 (USB 2.0)

1.7 Device #3: Intel(R) Wireless Bluetooth(R)

VID = 0x8087, PID = 0x0a2b, REV = 0x0001 (USB 2.0)

1.8 Device #4: Synaptics FP Sensors (WBF) (PID=003f)

VID = 0x138a, PID = 0x003f, REV = 0x0104 (USB 1.1)

1.9 Device #5: USB Composite Device

VID = 0x05c8, PID = 0x0383, REV = 0x0106 (USB 2.0)

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

-------------------------------------------------------------

I also read in one of the previous posts that there may be an issue with the Driver version so I've downgraded to the 4.3 from 4.7 and also upgraded to 5.1.1 but same error came up. You've also mentioned that it may be a HW issue so I've replaced the USB cable with a shorter one and changed the USB port but same error occurs.

Any additional advice?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Try to downgrade the drivers again. Unfortunately, I have no other advice.
[Upgrading, Modifying and Unlocking] noki severgun:
Thanks for the advice, it looks like only the driver 4.5 works with that model of box and I was able to extract all files from the master box.

I have another question which I doubt it's belonging to this forum but would appreciate if you can at least guide me to the right direction. As I've mentioned in my previous post, I'm trying to copy the setup that I've done on one box onto many boxes, similar as when you make a windows image with all the apps preset and then install it on many PC's or laptops. After I broke two of this android boxes I realised that I can't just replace the extracted files from one box and apply (overwrite) them to another one so I was wandering if someone knows what is the procedure for extracting the current apps and applying that (let's call it an) image to the rest of the boxes of the same type.

Thanks.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
You must first check the dumps. The latest uploaders "give away" fake information. There shouldn't be any other problems. At least, maybe I'm not such an expert and I may just not know the obstacles
[Upgrading, Modifying and Unlocking] TBM 13:
I confirm this worked on my RK3368 device too. Since I had built from source an uboot binary similar to the one my device comes with, I modified the source code to allow up to 4 GB reading (which is enough to dump all partitions except userdata), and compared the differences between the two binaries with an hex editor.

Then, I opened my stock uboot.bin in the hex editor, searched for `81 00 01 8B 24 00 02 8B 9F 40 40 F1 49 01 00 54` and in that sequence replaced `40 40` with `00 60`, saved, repacked, flashed and done! I don't know whether this sequence is present in most uboots or just mine. Maybe you could research this @RedScorpioXDA , because if that's the case you could maybe automate this process in your tool.

Also please note that if you use Rockchip's AndroidTool to dump, use an old version like v2.38 as newer ones also deny dumping after 32 MB.

In case it's helpful to anyone, I'm documenting the research of my Rockchip device on GitHub
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I don't want to add a firmware flashing to my utility. There are too many dissatisfied even with such opportunities.
[Upgrading, Modifying and Unlocking] pcwizzy37:
I don't have a PC with Windows on it, just Linux, is there going to be a Linux version of this tool?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I'm not a professional programmer and I don't know how to work with USB in Linux. Therefore, the Linux version is not expected
[Upgrading, Modifying and Unlocking] pcwizzy37:
Ah okay, makes sense, I already found another tool called rkflashtool that works with the maskROM mode I need. Thank you though! Open source the tool on Github though.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Are you sure? Based on my experiments, device memory is not available in this mode.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please, try https://disk.yandex.com/d/NW_dKwRFy0tuNA
[Upgrading, Modifying and Unlocking] deceee:
Thanks, will try after 20th when I get back home and let you know how it goes.
[Upgrading, Modifying and Unlocking] rafawhitee:
Same here, on rk3528 doesn't work and on Scan has a rock device.

2023.09.03 22:28:42 1.10.2.1.3 Device #9: Rockusb Device

2023.09.03 22:28:42 VID = 0x2207, PID = 0x350c, REV = 0x0223 (USB 2.0)

2023.09.03 22:28:42 .DEBUG. SymLink = "\\?\USB#VID_2207&PID_350C#SN23070116242#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"

2023.09.03 22:28:42 .DEBUG. DriverKeyName = "{79dfc2a8-2574-493c-ae71-52958e41dd00}\0003"

2023.09.03 22:28:42 .DEBUG. Driver version = 5.11.0.0 (11-10-2020)

2023.09.03 22:28:42 .DEBUG.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I didn't quite understand the situation. The utility does not write anything to the device's memory - just restart
[Upgrading, Modifying and Unlocking] Tressie:
Have a H96 Max v56 RK3566 8GB DDR4/ 64GB eMMC, and trying to extract a full copy of the firmware, before I brick the device, and find that the factory firmware supplied online isn't appropriate or complete enough to get me out of trouble.

rkDumper_1.1.1.0, both before and after an update, reports:

Found Loader device

Command to read failed

Command to reset failed

Not 100% sure what's going on here?

Believe I may need a specific version of rkDumper, but not sure which one, or where to find it?

Any clues or advice greatly appreciated.
[Upgrading, Modifying and Unlocking] deceee:
I have tried ALL versions of DriverAssistant (1.3, 4.1, 4.2, 4.3, 4.4, 4.5, 4.7, 4.8, 4.91, 5.1.1) and none of them work.

Versions < 4.91 don't recognise device VID=0x2207, PID=0x350C and therefore won't install the rockusb driver.

Versions 4.91 & 5.1.1 will install the rockusb driver but rkDumper gives the 'Command to Read/Reset failed'.

My understanding is that rkDumper only works with drivers < 4.5 (or there about) and since the newer devices rk3528 & rk3566 aren't supported by these drivers, rkDumper won't work.

I have been able to dump the ROMs via adb over WiFi (adb over USB doesn't work) , but of course this isn't a 'clean' factory installed image.

Also since there is no offical firmware image we can't tell if the image will be useable with imgRePackerRK yet...
[Upgrading, Modifying and Unlocking] Tressie:
Illuminating.

What about rkdeveloptool and RKDevTool? Both seem to be able to dump a small number of sectors, but lose interest when asked for the whole ROM.

T.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This is not new information. Just add new VID/PID to the old drivers. I can't offer you anything else.
[Upgrading, Modifying and Unlocking] Tressie:
Yep, gave it a shot with DriverAssistantv4.8, with the VID/PID numbers entered into the config.ini file...

Found: LOADER device (RK3566/RK3568 2207:350a) #3

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

Can't open device ""

-- Rockchip device resetting --

Found LOADER Rockchip device

Can't open device ""

Slightly different output to when using DriverAssistantv5.1.1, though similar outcome, and now the RockChip Android Tool no-longer works.

I'm doing something wrong?

What about rkdeveloptool and RKDevTool? Both seem to be able to dump a small number of sectors, but lose interest when asked for the whole ROM.

T.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This means that the drivers are not installed
[Upgrading, Modifying and Unlocking] Tressie:
Got v4.3 of the DriverAssistant to go on Windows 7, and the Android Tool program recognises the device in loader mode, yet rkDumper v1.1.1.4 yields:

Found Loader device

Command to read failed

Command to reset failed

Never mind. Something to do with RK3568, rather than RK3566, maybe? Dunno.

What's the deal with rkdeveloptool and RKDevTool? Both seem to be able to dump a small number of sectors, but lose interest when asked for the whole ROM.

T.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
1. Perhaps these utilities use a different algorithm. I have some assumptions, but unfortunately I don't have any new devices to test them. My devices are not experiencing any problems with reading.

2. In relatively new firmware, read protection is installed above a certain address and you will receive 0xCC at these addresses
[Upgrading, Modifying and Unlocking] @gigantino:
Please enable support for RK3562.

VID = 0x2207, PID = 0x350d, REV = 0x0223 (USB 2.0)
[Upgrading, Modifying and Unlocking] @gigantino:
Found: LOADER device (RK3562 2207:350d) #3

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

Command to read failed

-- Rockchip device resetting --

Found LOADER Rockchip device

Any idea? Device is Umidigi G1 Tab.

EDIT: Fixed by changing drivers!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Write which version of the drivers you used
[Upgrading, Modifying and Unlocking] RockChipWa:
Found: LOADER device (RK3126 2207:310d) #1

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

Data reading error

-- Rockchip device resetting --

Found LOADER Rockchip device

Command to reset succssfully

Critical error(NAND reading failed)

Hello, can somebody help me with my Problem?

I've tryed rkdumper version 1110 and 1121 and Usb driver 4.3

My Chip is a RK312A.

EDIT: Fixed Downloading everything new,

HINT: for me only USB-Driver 4.3 works
[Upgrading, Modifying and Unlocking] lebossejames:
Hello, I get this message:

Can't find RockChip device

I have a box with RK3528

C:\Users\admin\Downloads\Android_IPTV\rkDumper_1.1.0.0>rkDumper /log /debug /test scan

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

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

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

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

USB devices table (found 7 devices):
1 Device #0: USB Root Hub (ports: 18)
1.1 Device #1: Rockusb Device
VID = 0x2207, PID = 0x350c, REV = 0x0223 (USB 2.0)
Driver version = 5.11.0.0 (11-10-2020)
1.3 Device #2: Alcor Micro USB Smart Card Reader
VID = 0x058f, PID = 0x9540, REV = 0x0120 (USB 2.0)
Driver version = 1.7.46.1307 (12-5-2017)
1.4 Device #3: Périphérique USB composite
VID = 0x046d, PID = 0xc52f, REV = 0x3000 (USB 2.0)
Driver version = 10.0.19041.2546 (6-21-2006)
1.7 Device #4: Intel(R) Wireless Bluetooth(R)
VID = 0x8087, PID = 0x0a2b, REV = 0x0001 (USB 2.0)
Driver version = 22.140.0.4 (4-22-2022)
1.8 Device #5: Périphérique USB composite
VID = 0x04f2, PID = 0xb5ab, REV = 0x0010 (USB 2.0)
Driver version = 10.0.19041.2546 (6-21-2006)
1.15 Device #6: Realtek USB 3.0 Card Reader
VID = 0x0bda, PID = 0x0316, REV = 0x0204 (USB 3.0)
Driver version = 10.0.17134.31242 (7-11-2018)

==========================[ STOP ]==========================
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Use version 1.1.2.1 (above)
[Upgrading, Modifying and Unlocking] lebossejames:
I have this with v.1.1.2.1:

C:\Users\admin\Downloads\Android_IPTV\rkDumper_1121>rkDumper dump

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

(c) RedScorpio, Moscow, 2014-2023
RedScorpio.lab@gmail.com

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

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

USB devices table (found 7 devices):
1 Device #0: USB Root Hub (ports: 18)
1.1 Device #1: Rockusb Device
VID = 0x2207, PID = 0x350c, REV = 0x0223 (USB 2.0)
1.3 Device #2: Alcor Micro USB Smart Card Reader
VID = 0x058f, PID = 0x9540, REV = 0x0120 (USB 2.0)
1.4 Device #3: Périphérique USB composite
VID = 0x046d, PID = 0xc52f, REV = 0x3000 (USB 2.0)
1.7 Device #4: Intel(R) Wireless Bluetooth(R)
VID = 0x8087, PID = 0x0a2b, REV = 0x0001 (USB 2.0)
1.8 Device #5: Périphérique USB composite
VID = 0x04f2, PID = 0xb5ab, REV = 0x0010 (USB 2.0)
1.15 Device #6: Realtek USB 3.0 Card Reader
VID = 0x0bda, PID = 0x0316, REV = 0x0204 (USB 3.0)
Press any key...

Found: LOADER device (RK3528 2207:350c) #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

==========================[ STOP ]==========================
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Use old version of drivers (<= 4.3)
[Upgrading, Modifying and Unlocking] afglode:
read dump failed

rkDumper_1.1.1.0
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Downgrade the drivers version
[Upgrading, Modifying and Unlocking] lebossejames:
I have windows 10 and i try 4.3 driver it don't detect device.