yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] mbskylian:
thks for your jobs, i have rk3399 coreboard , can not dump idb from loader mode .

user rk dump version

NAME=rkDumper

VERSION=1.1.1.4

MODE=0

LINK=https://disk.yandex.ru/d/GOzFTLQe4TXYLQ

LINK=https://1drv.ms/u/s!ApT2PdXy7niKg1rki8wZZFZogR62

CHECK=20231019

dedbug show

IDB (copy #1) reading

IDB (copy #1) is equal with main IDB

IDB (copy #2) reading

IDB (copy #2) is not equal with main IDB at position #84000

IDB sector 0 properties:

Magic = 0x0ff0aa55

Rc4Flag = 0x00000001

BootCode1Offset = 0x0004

BootCode2Offset = 0x0004

BootDataSize = 0x0090

BootCodeSize = 0x0140

CRC = 0x0000

IDB sector 1 properties:

ChipTag = 0x38324b52 ("RK28")

MachineId = 0x00000000

LoaderDate = 12.10.2019

LoaderVer = 01.18

LastLoaderVer = 00.00

FwVer = 0x00000000

MachineInfoLen = 0x0000

ManufactInfoLen = 0x0000

IDB sector 2 properties:

ChipInfoSize = 0x0010

ChipInfo = "C033"

IDB sector 3 properties:

SNSize = 0x00

wifiSize = 0x00

imeiSize = 0x00

uidSize = 0x1e

uid = ROCKCHIP-d20d-a85d-913d-941d-8b6d-8a4e-b68d-cb26-0b7c-5e55-765f

blueToothSize = 0x00

macSize = 0x00

Unknown value of rkIDB_sec0.Rc4Flag = 1. Please send mail with link to this image to RedScorpio.

IDB (copy #3) reading

IDB (copy #3) is not equal with main IDB at position #0000

IDB sector 0 properties:

Magic = 0xf32c266e

Incorrect Magic value

IDB decoding error

IDB (copy #4) reading

IDB (copy #4) is not equal with main IDB at position #0000

IDB sector 0 properties:

Magic = 0xf32c266e

Incorrect Magic value

IDB decoding error

dump all parameter show

FIRMWARE_VER: 7.1

MACHINE_MODEL: Z5

MACHINE_ID: 007

MANUFACTURER: RK3399

MAGIC: 0x5041524B

ATAG: 0x00200800

MACHINE: 3399

CHECK_MASK: 0x80

PWR_HLD: 0,0,A,0,1

#KERNEL_IMG: 0x00280000

#FDT_NAME: rk-kernel.dtb

#RECOVER_KEY: 1,1,0,20,0

#in section; per section 512(0x200) bytes

CMDLINE: console=ttyFIQ0 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0 init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00002000@0x00006000(misc),0x00008000@0x00008000(resource),0x0000C000@0x00010000(kernel),0x00010000@0x0001C000(boot),0x00020000@0x0002C000(recovery),0x00038000@0x0004C000(backup),0x00040000@0x00084000(cache),0x00300000@0x000C4000(system),0x00008000@0x003C4000(metadata),0x00000040@0x003CC000(verity_mode),0x00002000@0x003CC040(reserved),0x00000400@0x003CE040(frp),-@0x003CE440(userdata)

please fix it, thank you
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Alas, I can't. I don't have any similar devices
[Upgrading, Modifying and Unlocking] hackaround:
Any idea what I am doing wrong here? I am using:

DriverAsistant 4.2 and I've tried also with DriverAsistant 4.3

RKDevTool v2.96

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 9 devices):
1 Device #0: USB Root Hub (ports: 18)
1.3 Device #1: Rockusb Device
VID = 0x2207, PID = 0x330d, REV = 0x9999 (USB 2.0)

Found: LOADER device (RK3388/RK3308 2207:330d) #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] mbskylian:
It's okay, thanks for the reply
[Upgrading, Modifying and Unlocking] hackaround:
after installing DriverAsistant 4.4 I was able to dump. my next question, is it safe to flash back all the images with so many format: unknown?

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

--- 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 "resource" (0x00008000) saved (format: Rockchip resources image file)
Partition "kernel" (0x00010000) saved (format: unknown)
Partition "boot" (0x00010000) saved (format: unknown)
Partition "recovery" (0x00020000) saved (format: unknown)
Partition "backup" (0x00038000) saved (format: unknown)
Partition "security" (0x00002000) saved (format: unknown)
Partition "cache" (0x000c0000) saved (format: unknown)
Partition "system" (0x00300000) saved (format: unknown)
Partition "metadata" (0x00008000) saved (format: unknown)
Partition "vendor" (0x000c0000) saved (format: unknown)
Partition "oem" (0x00140000) saved (format: unknown)
Partition "frp" (0x00000400) saved (format: unknown)
Partition "private" (0x00100000) saved (format: unknown)
Partition "logo" (0x00004000) saved (format: unknown)
Partition "userdata" (0x00737bdf) saved (format: unknown)
[Upgrading, Modifying and Unlocking] hackaround:
after few attempts I think I understand why I am getting format: unkown. when I try info this is failing and the info is wrong:

Found: LOADER device (RK3308/RK3326/RK3388/PX30 2207:330d) #1
FlashInfo
Manufacturer: Samsung (0x00)
Flash size: 682058MB (0x53425355)
Full size: 0MB (0x00000000)
Block size: 0KB
Page size: 0KB
ECC bits: 0
Access time: 11
Flash CS: (0x00)
Response reading error

this is the info I am getting from rkdevtool:

any idea what I can try to get the correct info? thanks!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, without such a device, it is impossible to test and make corrections
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
For some time now, the devices on RK have read protection and return 0xCC after some address. Therefore, the file format is not recognized and it is very DANGEROUS to flash the device with the received files - this will lead to complete inactivity of the device. If the device has root, use adbDumper
[Upgrading, Modifying and Unlocking] hackaround:
the problem I have is that the device is bootlooping after replacing su binaries. I was trying to dump the firmware and remove supersu and flash back to fix the issue. if I play with the parameter file, do you think will help? or because the chip is not properly recognized I don't have any chance?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
The parameters file is responsible for splitting the flash memory of the device and you need to play with it very carefully (and it's better not to play).

If the device has been dumped, then the chip has been identified quite enough for this procedure
[Upgrading, Modifying and Unlocking] akeshma:
Try this for my DQ08 Pro

VID = 0x2207, PID = 0x350c

but ask for updater and File "rkDumper.inf" don't found

C:\RockChip_Tools\rkDumper_1.1.2.0>rkDumper.exe dump

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

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

updater
version 1.0.0.4

Copyright c RedScorpio, 2022
RedScorpio.lab@gmail.com

Name "rkDumper"
log = True
debug = True
ask = False
registry = ?

Error: No download links
Fatal error: Failed to initiate update check
==========================[ START ]==========================

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

USB devices table (found 6 devices):
1 Device #0: USB Root Hub (ports: 3)
1.1 Device #1: USB Hub (ports: 8)
VID = 0x8087, PID = 0x0020, REV = 0x0000 (USB 2.0)
1.1.2 Device #2: Rockusb Device
VID = 0x2207, PID = 0x350c, REV = 0x0100 (USB 2.0)
2 Device #3: USB Root Hub (ports: 3)
2.1 Device #4: USB Hub (ports: 6)
VID = 0x8087, PID = 0x0020, REV = 0x0000 (USB 2.0)
2.1.1 Device #5: USB Composite Device
VID = 0x064e, PID = 0xc21c, REV = 0x0110 (USB 2.0)
Press any key...

Found: MASKROM device (RK3528 2207:350c) #2
Rockchip device is not in MCS or LOADER mode
[Upgrading, Modifying and Unlocking] akeshma:
when install the old driver 4.2 the process continue but take long time to backup userdata partition ... how to skip that ?
[Upgrading, Modifying and Unlocking] waldopulanco:
Im using rkdumper_1121, how do I use this command?

I tried this command but there is no file on idb folder

sir do you have an idea how do I backup bootloader for rockchip rk3128? If you need more Info, I will use uart serial console to debug my device. if you need a file to analyze, example mmcblk0, I will dump using dd command. thanks in advance!

PS: this device bootloader is rare, rk3128-d it is different from rk3128a and rk3128. rk3128a bootloader is rare you cannot find bootloader v2.40 on the internet. also rk3128-d is rare too, no bootloader available on internet. that is why I need to backup the bootloader for this rare chip. thanks again!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Set the appropriate device mode (MSC or LOADER). Apparently, you have a MASKROM mode
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Judging by the data on the screen, it is useless to use rkDumper in your case - read protection is installed
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I can't offer anything more
[Upgrading, Modifying and Unlocking] waldopulanco:
thank you so much for your nice offer!
[Upgrading, Modifying and Unlocking] spannernick:
I have a Rockchip RK3128 but not in a mobile device, these are now used in other things too, it in the Atari2600 Plus that loads 2600/7800 Cartridges, I want to find a way of backing up its nand, you can flash a .img to it via its USB-C cable that powers it in Maskrom Mode, it does use the RKDevTool_Release_v2.74 to flash updates to it..?

Link to Beta Update - https://forums.atariage.com/topic/358796-atari-2600-beta-update-11/

Atari2600 Plus on Atari.com - https://atari.com/products/atari-2600-plus

Its PID and VID - USB\VID_2207&PID_310C\7&DC03DFF&0&5

Pictures ...

The second picture shows it main board with the RK3128 on it, it has 256mb ram and 256mb Nand.
[Upgrading, Modifying and Unlocking] spannernick:
rkDumper (version 1.1.2.0)
Utility for Rockchip's firmware backup

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

File "C:\Users\span1\Downloads\rkDumper_1.1.2.0\rkDumper.inf" don't found
==========================[ START ]==========================

Detected OS: Windows 8 Pro [build 9200] x64
Real OS: Windows 11 Pro [build 22631] x64
-- Devices enumerating --

Can't open disk "\\?\USBSTOR#DISK&VEN_GENERIC-&PROD_SD/MMC&REV_1.00#A&EB9AB1F&0&058F63646476&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
USB devices table (found 12 devices):
1 Device #0: USB Root Hub (ports: 2)
1.1 Device #1: USB Hub (ports: 4)
VID = 0x8087, PID = 0x0024, REV = 0x0000 (USB 2.0)
1.1.1 Device #2: USB Hub (ports: 4)
VID = 0x058f, PID = 0x6254, REV = 0x0100 (USB 2.0)
1.1.1.1 Device #3: USB Mass Storage Device
VID = 0x152d, PID = 0x2329, REV = 0x0100 (USB 2.0)
Disk #2
1.1.1.2 Device #4: USB Composite Device
VID = 0x058f, PID = 0x6364, REV = 0x0100 (USB 2.0)
2 Device #5: USB Root Hub (ports: 2)
2.1 Device #6: USB Hub (ports: 6)
VID = 0x8087, PID = 0x0024, REV = 0x0000 (USB 2.0)
2.1.1 Device #7: USB Composite Device
VID = 0x534d, PID = 0x2109, REV = 0x2100 (USB 2.0)
2.1.2 Device #8: USB Hub (ports: 7)
VID = 0x1a40, PID = 0x0201, REV = 0x0100 (USB 2.0)
2.1.2.1 Device #9: USB Hub (ports: 4)
VID = 0x1a40, PID = 0x0101, REV = 0x0111 (USB 2.0)
2.1.2.5 Device #10: Rockusb Device
VID = 0x2207, PID = 0x310c, REV = 0x0100 (USB 2.0)
2.1.2.7 Device #11: USB Composite Device
VID = 0x17ef, PID = 0x6047, REV = 0x0330 (USB 2.0)
Press any key...
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
It looks like the drivers are not installed
[Upgrading, Modifying and Unlocking] snam11:
i came across this x96 mini clone (it has r2339 chip onboard instead of S905W, board no. X9X_R29_LP3)

it goes only in maskrom mode (pressing the button or shorting the 2 inspection pins on the board)

i can't flash anything using android tool or rkbatchtool (due to loader mode not present?), but i can rip/flash using the old androidtool console.

i'ev tested drivers 4.5 and 5.1 (older drivers won't work because the device is not detected anymore)

with rkdumper i get those errors:

rkDumper_1.1.0.0>rkDumper.exe 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 8.1 Pro [build 9600] x64
-- Devices enumerating --

USB devices table (found 8 devices):
1 Device #0: USB Root Hub (ports: 2)
1.1 Device #1: Dispositivo USB composito
VID = 0x203a, PID = 0xfffc, REV = 0x0100 (USB 1.1)
2 Device #2: USB Root Hub (ports: 14)
3 Device #3: USB Root Hub (ports: 15)
3.1 Device #4: Supporto stampa USB
VID = 0x203a, PID = 0xfffa, REV = 0x0100 (USB 2.0)
3.2 Device #5: Supporto stampa USB
VID = 0x203a, PID = 0xfffa, REV = 0x0100 (USB 2.0)
3.3 Device #6: Rockusb Device
VID = 0x2207, PID = 0x320b, REV = 0x0100 (USB 2.0)
3.4 Device #7: Supporto stampa USB
VID = 0x203a, PID = 0xfffa, REV = 0x0100 (USB 2.0)

rkDumper_1.1.0.0>rkDumper.exe dump

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 8.1 Pro [build 9600] x64
-- Devices enumerating --

USB devices table (found 8 devices):
1 Device #0: USB Root Hub (ports: 2)
1.1 Device #1: Dispositivo USB composito
VID = 0x203a, PID = 0xfffc, REV = 0x0100 (USB 1.1)
2 Device #2: USB Root Hub (ports: 14)
3 Device #3: USB Root Hub (ports: 15)
3.1 Device #4: Supporto stampa USB
VID = 0x203a, PID = 0xfffa, REV = 0x0100 (USB 2.0)
3.2 Device #5: Supporto stampa USB
VID = 0x203a, PID = 0xfffa, REV = 0x0100 (USB 2.0)
3.3 Device #6: Rockusb Device
VID = 0x2207, PID = 0x320b, REV = 0x0100 (USB 2.0)
3.4 Device #7: Supporto stampa USB
VID = 0x203a, PID = 0xfffa, REV = 0x0100 (USB 2.0)

Found: MASKROM device (RK3229 2207:320b) #6
Rockchip device is not in MCS or LOADER mode
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What about MSC mode?
[Upgrading, Modifying and Unlocking] snam11:
well i dunno how to trigger it.

On the motherboard you have the standard switch right behind the av plug, and 2 other test point.and in both cases the device goes into maskrom mode.

i even tried to short to ground the dat0 pin on the unsoldered emmc but the device won't even power on as long the short is enabled.

any tips on how to switch into loader or mcs?
[Upgrading, Modifying and Unlocking] blakegriplingph:
I am trying to get this to work on a LeapFrog LeapPad Academy running off an RK3326. It's in loader mode but for some reason I am unable to get it to read. Tried both version 4.5 and 5.1 of the RockChip USB drivers to no avail:

C:\Users\Samantha\Desktop\rkDumper_1.1.1.0>rkdumper info

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

USB devices table (found 8 devices):
1 Device #0: USB Root Hub (ports: 6)
2 Device #1: USB Root Hub (ports: 6)
2.1 Device #2: USB Input Device
VID = 0x093a, PID = 0x2510, REV = 0x0100 (USB 2.0 Low Speed)
2.2 Device #3: USB Composite Device
VID = 0x1c4f, PID = 0x0002, REV = 0x0110 (USB 1.1 Low Speed)
3 Device #4: USB Root Hub (ports: 6)
4 Device #5: USB Root Hub (ports: 12)
4.8 Device #6: USB Composite Device
VID = 0x04b8, PID = 0x1142, REV = 0x0100 (USB 1.1)
4.9 Device #7: Rockusb Device
VID = 0x2207, PID = 0x330d, REV = 0x9999 (USB 2.0)

Found: LOADER device (RK3308/RK3326/RK3388/PX30 2207:330d) #7
Command to read failed

EDIT: NVM, I got it to read now:

EDIT 2: I ran into an issue where the ROM appears to being dumped, but all I got are files filled with CC all over:

I can apparently use the Export Image function in AndroidTool and it does seem to spit out something; it's when I try to dump with RKDumper that it gets rather flaky.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Downgrade the driver version
[Upgrading, Modifying and Unlocking] blakegriplingph:
Alright, noted. I presume I have to patch the uboot first for the dump to work, right?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
It is quite likely
[Upgrading, Modifying and Unlocking] protectivedad:
Is there an option to force using a specific VID/PID combo. It doesn't seem to recognized the newest 2207:310D combination.

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

(c) RedScorpio, Moscow, 2014-2015
[email]RedScorpio@land.ru[/email]

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

-- Devices enumerating --

Devices table (found 11 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Hub
VID = 0x8087, PID = 0x0024, REV = 0x0000
1.1.5 Device #2: Microsoft Mouse and Keyboard Detection Driver (USB)
VID = 0x045e, PID = 0x0745, REV = 0x0663
1.1.6 Device #3: Rockusb Device
VID = 0x2207, PID = 0x310d, REV = 0x0100
2 Device #4: USB Root Hub
3 Device #5: USB Root Hub
4 Device #6: USB Root Hub
4.1 Device #7: USB Hub
VID = 0x8087, PID = 0x0024, REV = 0x0000
4.1.2 Device #8: USB Printing Support
VID = 0x04f9, PID = 0x0027, REV = 0x0100
5 Device #9: USB Root Hub
5.6 Device #10: USB Attached SCSI (UAS) Mass Storage Device
VID = 0x0bc2, PID = 0xab24, REV = 0x0100

Can't find RockChip device

==========================[ STOP ]==========================
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please inform me the name of device and type of SoC
[Upgrading, Modifying and Unlocking] protectivedad:
The device is a Proscan PLT9650G. From the box and looking at the running systems /proc/cpuinfo it says it's a RK3126. I've attached the devices parameters.txt file. The newest windows drivers from RockChip (Driver Assistant 4.3) have the PID listed (it took a while to find them).
[Upgrading, Modifying and Unlocking] E--Man:
Greetings to all. I have a cheap Tablet that uses the same Hardware ID "USB\VID_2207&PID_310D" and I have already soft-bricked it once trying to install TWRP and had to go back to the store to exchange it. This time around, I would like to make a backup before flashing anything so that I can revert back.

RedScorpioXDA, thanks for your efforts on this project thus far. Is there any update on this new HardwareID addition? I would really like to root this device but also have the same Hardware ID as "protectivedad".

Thanks.

rkDumper (version 1.00)

Utility for Rockchip's firmware backup

(c) RedScorpio, Moscow, 2014-2015

RedScorpio@land.ru

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

-- Devices enumerating --

Devices table (found 5 USB devices):

1 Device #0: USB Root Hub

1.1 Device #1: Rockusb Device

VID = 0x2207, PID = 0x310d, REV = 0x0100

2 Device #2: USB Root Hub

2.1 Device #3: USB Composite Device

VID = 0x0e0f, PID = 0x0003, REV = 0x0102

2.2 Device #4: USB Hub

VID = 0x0e0f, PID = 0x0002, REV = 0x0100

==========================[ STOP ]==========================
[Upgrading, Modifying and Unlocking] E--Man:
Anyone?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
protectivedad,

E--Man,

Please, try test version http://ge.tt/5JPvWCU2/v/0?c
[Upgrading, Modifying and Unlocking] E--Man:
[MENTION=4582467]RedScorpioXDA[/MENTION], many thanks! Spaciba balchoi! It worked for me

Just to confirm, if I soft-brick this device by flashing TWRP, can I use what I just "dumped" to "load" back?

Best Regards,

E.

---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------

Spoke too soon. I got a "Critical Error" "Data Reading Erro" while dumping "system.img". Here is the log:

C:\Users\User\Desktop\rkDumper_101g (1)>rkdumper dump

rkDumper (version 1.01g_test)

Utility for Rockchip's firmware backup

(c) RedScorpio, Moscow, 2014-2015

RedScorpio@land.ru

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

!!! Test pos #0

--- Firmware dumping ---

-- Devices enumerating --

Devices table (found 5 USB devices):

1 Device #0: USB Root Hub

1.1 Device #1: Rockusb Device

VID = 0x2207, PID = 0x310d, REV = 0x0100

2 Device #2: USB Root Hub

2.1 Device #3: USB Composite Device

VID = 0x0e0f, PID = 0x0003, REV = 0x0102

2.2 Device #4: USB Hub

VID = 0x0e0f, PID = 0x0002, REV = 0x0100

Found: LOADER device (RK3126 2207:310d) #1

Found LOADER Rockchip device

PARM sign found

FlashInfo

Manufacturer: Hynix (0x02)

Flash size: 8480MB (0x01090000)

Full size: 8480MB (0x01090000)

Block size: 4096KB

Page size: 16KB

ECC bits: 40

Access time: 32

Flash CS: 0 (0x01)

CS0: ad de 14 a7 42

Partition "uboot" saved (format: unknown)

Partition "misc" saved (format: unknown)

Partition "resource" saved (format: Rockchip resources image

file)

Partition "kernel" saved (format: RockChip KRNL signed file

)

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

Partition "recovery" saved (format: Android boot image)

Partition "backup" saved (format: unknown)

Partition "cache" saved (format: ext4 image)

Partition "metadata" saved (format: ext4 image)

Partition "kpanic" saved (format: unknown)

Partition "system" Data reading error

Critical error

==========================[ STOP ]==========================

!!! Test pos #6

!!! Test pos #9

!!! Test pos #11

!!! Test pos #12

!!! Test pos #13

!!! Test pos #14

C:\Users\User\Desktop\rkDumper_101g (1)>