yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (0.94 Windows) ready

! pre-Release #4;

+ support of RK3288 added;

+ manifest file added;

+ detection of device revision added;

~ administrator's rights checking algorithm changed.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (0.95 Windows) ready

! pre-Release #5;

+ support of RK3128 added;

+ /user key added;

+ ROM size/vendor/ID determinetion added ("info" command);

~ bug of incorrect determination of disks in multi-CD systems fixed.
[Upgrading, Modifying and Unlocking] Tigrouzen:
Just thank you ! :)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.00 Windows) ready

! Release;

+ /incl key added;

+ /excl key added;

~ some algorithms improved.
[Upgrading, Modifying and Unlocking] dying_sun:
Hello, one question, is possible to use this tool with Rockchip/Intel sofia platform? Thanks in advance
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What the name of device?

rkDumper 1.09d test

Note that the latest versions of devices give fake data instead of firmware after a certain address.
[Upgrading, Modifying and Unlocking] zeroprobe:
I think you are right. I dumped using rkdeveloptool and a lot of the partitions were just filled with hex CC.

Probably no solution then.

Your program I had an issue with any command.

Android\RockChip\rkDumper_109d_test>rkdumper /log /debug /test

rkDumper (version 1.09d_test)

Utility for Rockchip's firmware backup

(c) RedScorpio, Moscow, 2014-2021

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

Detected OS: Windows 8 Pro [build 9200] x64

Real OS: Windows 10 Pro [build 19042] x64

-- Devices enumerating --

USB devices table (found 12 devices):

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

2 Device #1: USB Root Hub (ports: 8)

3 Device #2: USB Root Hub (ports: 8)

3.5 Device #3: Genesys Logic USB2.0 Card Reader

VID = 0x05e3, PID = 0x0745, REV = 0x0903 (USB 2.0)

Driver version = 4.5.4.2 (7-15-2019)

3.8 Device #4: USB Composite Device

VID = 0x046d, PID = 0xc52b, REV = 0x1203 (USB 2.0)

Driver version = 10.0.19041.488 (6-21-2006)

4 Device #5: USB Root Hub (ports: 4)

4.3 Device #6: USB Hub (ports: 2)

VID = 0x0424, PID = 0x2532, REV = 0x0182 (USB 2.0)

4.4 Device #7: USB Composite Device

VID = 0x046a, PID = 0x0023, REV = 0x0220 (USB 2.0 Low Speed)

Driver version = 10.0.19041.488 (6-21-2006)

5 Device #8: USB Root Hub (ports: 22)

5.11 Device #9: Rockusb Device

VID = 0x2207, PID = 0x350a, REV = 0x0223 (USB 2.0)

Driver version = 5.0.0.0 (9-1-2020)

5.12 Device #10: USB Composite Device

VID = 0x062a, PID = 0x5918, REV = 0x0102 (USB 1.1)

Driver version = 10.0.19041.488 (6-21-2006)

5.22 Device #11: ASUS USB-BT400

VID = 0x0b05, PID = 0x17cb, REV = 0x0112 (USB 2.0)

Driver version = 12.0.0.7820 (8-30-2013)

Found: LOADER device (RK3566 2207:350a) #9

Unknown command

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

==========================[ STOP ]==========================
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
May be it:

"rkdumper /log /debug /test dump"?
[Upgrading, Modifying and Unlocking] mitchell4you:
Rkdumper /log /debug /test dump

Found Loader device ( rk3566 2207:350a) #13

Command to read failed

Command to reset failed

Unit: rk3566 h96max 8/64 version / using rkdumper 109d

Trying to backup units firmware
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Try to use another drivers (need to downgrade the version)
[Upgrading, Modifying and Unlocking] mitchell4you:
Hmm.. Problem solved by user xmannv In the "imgRepackRK" thread

Hey thankfully upload a full backup image

- that I unpacked and boot patched with magic and flashed

All worked fine

Thanks for great support and amazing tools

Cheers
[Upgrading, Modifying and Unlocking] Justinmbenedict1:
Hey buddy, from what i can tell, you are the most talented rockchip developer around.

I have a 7 inch rockchip device that i would love to be able to "unlock" the bootloader. I have full root access to the device (ANDROID 4.2.2) . i can pull and flash the stock images (mtdblock) with dd. but if i modify the boot.img at all it will not boot. (I tested by flashing to recovery) . I have bricked several of these trying to figure this thing out. It definitely is not normal rk firmware. I have several of these particular tablets that i would like to be able to upgrade to Android 5.1.1. i can pay you for the job and i can send you a device
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Alas, I'm not a developer at all. It's just a small utility
[Upgrading, Modifying and Unlocking] Justinmbenedict1:
you are a developer my friend.... and i need you. Please take a look at my boot.img? this was pulled from mtdblock2 with dd. if you can help me recreate the signature block at 00000400 i would be willing to pay you substantially. Hell id pay you just to try. please take a look bro and let me know if you need to see anything else
[Upgrading, Modifying and Unlocking] Razorj76:
I am trying to learn how to root a jp5 tablet, if you have any information I would be grateful, I will gladly compensate for step by step instructions, all I have is a broke tablet myself and a data cable with USB otg file manager nexus. Thank you.
[Upgrading, Modifying and Unlocking] JackTors:
Answered my own question.

Here's my story in case it might help someone else later. Booted "tablet device" into recovery mode, and it showed up as 2207:0006 (USB VID/PID). And nothing would touch it. Just for S&G's, rebooted into "normal mode" where it showed up as 2207:320A. Once I did THAT, rkDumper 1.09a_test could see it, and could reboot it into loader mode. And once THAT was done, it was able to start dumping it. (Dumping is in progress currently).

RedScorpio, GREAT piece of code!
[Upgrading, Modifying and Unlocking] dieselnutjob:
Hi, I am trying to use rkdumper on an rk3566 developement board.

Plugged into my Linux laptop I can get adb commands to work if the board is in what I think you call "normal" mode (so a working Android desktop).

In this mode it comes up as

Bus 003 Device 005: ID 2207:0006 Fuzhou Rockchip Electronics Company rk3566_rgo

If I then move the USB cable over to a Windows 7 laptop

The first thing I get is "Android ADB interface" "Device driver software installed successfully"

The I launch a cmd command shell with "run as administrator"

from that if I run

rkdumper test

I get "Can't find Rockchip device"

above that it says

3.2 Device #7: Android ADB interface

VID=0x2207, PID=0x006, REV=0x0310 (USB 2.0)

I have rkdumper (version 1.09d_test) and Rockchip Driver Assistant v4.4.

From the Linux PC I also did adb reboot bootloader

The board did reboot and come back up in what I think is bootloader mode but in that mode it doesn't seem to appear as a USB device at all and nothing works.

What am I doing wrong please?
[Upgrading, Modifying and Unlocking] dieselnutjob:
I found the trick. I have to press the "recover" button (which I think is normally volume up) whilst powering on the board.

Now I get device VID = 0x2207 PID=0x350a REV=0x0223 (USB 2.0)

Found: LOADER device (RK3566 2207:350a) #9

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

Can't opern device ""

-- Rockchip device resetting --

Found LOADER Rockchip device

Can't open device ""

STOP

STOP
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Most likely the device drivers are not installed
[Upgrading, Modifying and Unlocking] dieselnutjob:
Please can you (or others) please advise which is the best version of Rockchip Driverassistant to use for this?

I am on 4.4 but maybe that's too old for a brand new SoC like the 3566.
[Upgrading, Modifying and Unlocking] dieselnutjob:
You were right.

4.4 doesn't recognise device

4.5 doesn't recognise device

4.7 doesn't recognise device

4.8 doesn't recognise device

5.1.1 recognises device but rkdumper doesn't dump
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please provide log (with /debug option)
[Upgrading, Modifying and Unlocking] dieselnutjob:
@RedScorpioXDA

The RK3566 board that I am using is a dev board with a removable eMMC and an SDcard slot. It has no SPI chip fitted on the board. It is effectively impossible to permanently brick because I can always just unclip the eMMC module and re-image it from a laptop.

Therefore if you need to try something dangerous or whatever then I can help you with that because even if you brick my board I can easily unbrick it.

Maybe that's useful to you somehow.
[Upgrading, Modifying and Unlocking] dieselnutjob:
I have been playing with RKDevTool v2.71 on this RK3566.

In loader mode:-

The four buttons (in Advanced Function) ReadFlashID, ReadFlashInfo, ReadChipInfo, ReadCapability produce this output:-

Get FlashID Start
CSO: 45 4D 4D 43 20
Get FlashID Success

Get FlashInfo Start
Manufacturer: SAMSUNG
Flash Size: 59640MB
Total Sector: 0x747c000
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 01 00 00 00 00 00 00
DirectLBA: Enable
Get Capability Success

The button Export IDB produces five files 512KB in size.

The button ExportImage only works if Start + Count doesn't exceed 65536 and with Start=0 and Count=65536 it appears to dump out the first 32MB of the eMMC module.

Pressing ResetDevice results in the device rebooting into normal Android.

Pressing Go Maskrom results in the device going into maskrom mode.
[Upgrading, Modifying and Unlocking] dieselnutjob:
If I attempt to read beyond the first 32MB RkDevTool produces a log file entry saying

Error:ExportImageProc-->device did not support to read
[Upgrading, Modifying and Unlocking] qandres12:
Is there a way to create a full img file instead of the separate img files. Trying to create an img but rkdumper seems to do the separate img files for all partitions and the rkdev tool seems to do the same. I havent been able to do much research but so far it looks like you can only do the separate ones.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unpack manufacturer's firmware (imgRePackerRK), replace original partitions with dumped and pack back
[Upgrading, Modifying and Unlocking] qandres12:
Seems easy enough. This is new territory for me though. Just to verify, replace original partitions with dump means use RKDumper?

Was trying to use it yesterday but when I pressed any key it would just close the prompt. I'll have more time to figure it when I get to work.
[Upgrading, Modifying and Unlocking] AndyYan:
Got a commercial RK3566 device, and I hit almost identical roadblocks as @dieselnutjob - RKDevTool 32MB barrier, rkDumper "Command to read failed"... No way around this @RedScorpioXDA ?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This error is most often related to drivers. Try different driver versions. For some users, the problem was solved with drivers 4.5, for others - 4.2
[Upgrading, Modifying and Unlocking] AndyYan:
And same as the other user, older drivers just won't recognize this new chip.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I don't know any other solution to the problem
[Upgrading, Modifying and Unlocking] r_a_d_:
This happens on a RK3328 system I have. I can dump up to 0x10000 (32MB). Everything else is filled with 0xCC bytes. Any way around this?
[Upgrading, Modifying and Unlocking] r_a_d_:
Thanks for the reply. Let me know if there's anything I can do to test while I still have the devices.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
You misunderstood me. This application will not be able to bypass this restriction in any way - the restriction is done by internal software. You can try use adb to bypass it (but most likely there should be a "live" device and root rights)
[Upgrading, Modifying and Unlocking] andryangouw:
Hi RedScorpionXDA,

Thanks for the tool! I have RK3280 Android boards and RKDevTool somehow refuses to do a full NAND dump while RKDumper works extremely well (I only had to downgrade the Driver Assistant from 5.11 to 4.5).

Question, how do I get RKDumper to dump everything, including "user" partition? It keeps on skipping despite my attempts to use /incl and /excl parameter to get around it.

I have 7 identical boards, 4 are older and 3 are new (purchased as replacement because the 2 out of 4 older ones got burned because of shorting). The funny thing is that I dumped the partitions from the 2 older boards and used RKDevTool to "download" the dumped img files into the 3 new boards, however the 3 new boards remain without audio output in the HDMI port. The reason I used RKDumper is because I thought dumping the NAND and deploying it to the new boards would enable HDMI audio output like the older boards. I guess my hypothesis is wrong.

Could the difference in behavior be caused by something in the "user" partition? What are IDB files? Would it be possible to clone the bootloader (and IDB?) from the older 3280 boards to flash into the new boards to have an exact same software as the one in older boards?

Have anyone else noticed HDMI audio output missing from their RK Android boards?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Try to use /user option

I think - "no"

IDB files - is 2 of 4 parts of loader. I don't know methods to clone loader from RK devices. You need to find full firmware for (old) board and unpack it
[Upgrading, Modifying and Unlocking] PermaNull:
Not confirmed but I think the 65536 is a bug in the Loader that's on the chip, technically we can deploy new loader via the Maskrom mode https://docs.microsoft.com/en-us/cpp/cpp/integer-limits?view=msvc-170 I believe it's an unsigned short used in the firmware for the count/start combined... you can also offset start but you cannot increment past 65535 with start+count.

Meaning somewhere either driver or loader there's a bug where an unsigned short is being used to read this data and we overflow the integer past 65535 or 0xffff. I asked on discord where there was a Rockchip development board but no one had answers for me, so not sure where to go with it from here been using UART to extract data because this doesn't work. I've encountered this issue any time an emmc is in use on newer chips so maybe it's in the part of the software that reads emmc vs nand.

In any case, looks like the loader is also signed in some way, so can't modify it and re-deploy with custom code as far as I know.

RedScorpio - Does your tool use the same method as the standard tool does? Just communicates over the USB protocol the same way? The linux version doesn't 'fail' but it produces 0xCA so empty memory/failed read in which case there is no driver and it's just libusb afaik; so I assume it's the loader binary on the chip and emmc capabilities.
[Upgrading, Modifying and Unlocking] sbarrenechea:
Hey @RedScorpioXDA ! Thanks for the tool! I've been trying to dump all contents from a MK3399-based treadmill, and after trial and error I was able to get something, but not everything.

Here's my log (using driver 4.5 as latest does not work):

Spoiler content hidden.

uboot_a and uboot_b seems to unpack OK with imgRePackerRK. They are the only ones "OK".

If I open all "format: unknown" images on a HEX editor, there's no data, only "CC" values filling the entire image space. Here's an image of userdata (although the contents are the same for all other "format: unknown" images):

Spoiler content hidden.

Also, I opened the EFI_part.img file with disktype and here's the output (not sure if helpful):

Spoiler content hidden.

Any thoughts? I guess the script works well for MBR-based devices, but it has quirks on GPT?

EDIT: Adding the contents on the parameter file as well:

Spoiler content hidden.

EDIT 2: After reading a bit on 4pda, it seems that I'm stuck 😂

- The newer "RKFP" firmware format (containing EFI_part) is partially supported because the dev does not have boards with that format to test with (that's why the app hasn't released a stable "1.09" yet).

- Manufacturers using the newer "RKFP" firmware format seems to have the ability to "encrypt" the contents past the first Mb's. No further reverse engineering has been made to our kind of firmware.

I guess I'm stuck for the time being 😔
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
The work of the utility is based on the fact that the device "gives" the contents of memory to a certain request. But recently (most likely due to new loaders) devices have been "giving away" fake data. This is no longer possible to get around using the old algorithm. You should use adb, but there are limitations there
[Upgrading, Modifying and Unlocking] sbarrenechea:
That's sad. Thank you for all your support in the Rockchip platform so far!
[Upgrading, Modifying and Unlocking] justin bi:
Hello, thank you very much write this tool!

I have a noob question :

hdmi wifi dongle that use rk3036 chip and winbond 25q128 flash memory.

Can i use ch341 usb to read the flash memory to get manufacturer firmware?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I think not
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.1.0.0 Windows) ready

+ version numbering changed;

+ support of RK3566 added;

+ (!) RKFP firmware format support;

~ minor improvements.
[Upgrading, Modifying and Unlocking] mcain5546:
Hi, thanks for your service. Here's my scan of rockchip TX2:

C:\Rockchip Tools\rkDumper_1.1.0.0>rkDumper 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 Home [build 9200] x64

Real OS: Windows 10 Home [build 19044] x64

-- Devices enumerating --

USB devices table (found 5 devices):

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

1.3 Device #1: Rockusb Device

VID = 0x2207, PID = 0x320b, REV = 0x0100 (USB 2.0)

1.6 Device #2: USB Composite Device

VID = 0x064e, PID = 0xc355, REV = 0x0100 (USB 2.0)

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

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

1.8 Device #4: USB Input Device

VID = 0x04f3, PID = 0x2274, REV = 0x5712 (USB 2.0)

Thanks in advance for any and all help. It's an RK3229.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What is the problem?
[Upgrading, Modifying and Unlocking] mcain5546:
C:\Rockchip Tools\rkDumper_1.1.0.0>rkdumper 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 Home [build 9200] x64

Real OS: Windows 10 Home [build 19044] x64

-- Devices enumerating --

USB devices table (found 5 devices):

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

1.3 Device #1: Rockusb Device

VID = 0x2207, PID = 0x320b, REV = 0x0100 (USB 2.0)

1.6 Device #2: USB Composite Device

VID = 0x064e, PID = 0xc355, REV = 0x0100 (USB 2.0)

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

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

1.8 Device #4: USB Input Device

VID = 0x04f3, PID = 0x2274, REV = 0x5712 (USB 2.0)

Found: LOADER device (RK3229 2207:320b) #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

Not sure what I'm doing wrong.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Insecure reading syndrome. Try to choose drivers by downgrading their version
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.1.1.0 Windows) ready

+ autoUpdate;

~ minor improvements.
[Upgrading, Modifying and Unlocking] marol9494:
Hello,

I'm trying to dump the super partition (with offset 0x00614000@0x001d9000 )from my Rockchip board 3566

i always get the error like on the screenshot

with "Command to read failed" as i see some other people have resolved this issue downgrading drivers, but if i try to install an older driver

than the 5.11.0.0, my device is not correctly recoignized,

anyone has an idea on how i can fix this issue?

Thank you
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Do you have root rights?
[Upgrading, Modifying and Unlocking] marol9494:
Yes, i'm invoking the bin on a admin powershell
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
You can try:

adbDumper (new, untested)
[Upgrading, Modifying and Unlocking] marol9494:
Seems that i have no success connecting the device with adb sideload

After i've tried to connect the adb as device instead of sideload, i'm getting this error, seems that the API 30 is not supported?

I'm trying now forcing on the setting the API v29 :)

seems that i'm able to read the partition scheme.

I'll update this post.

Thank you
[Upgrading, Modifying and Unlocking] jotter24:
BRAND: MXQ PRO 4K 5G

CHIP: RK3228A

WiFi Chip: ESP8089

I have the almost the same problem xd. I need help:

I want to do a Backup of my Device, and then, this happens

I'm using the Rockchip Driver Assistant 4.5, because I tried with the lastest version and didn't work.

Any help is well receive xd TY

C:\RockChip Tools\3.rkDumper_1.1.1.0>rkdumper.exe dump

rkDumper (version 1.1.1.0)

Utility for Rockchip's firmware backup

(c) RedScorpio, Moscow, 2014-2022

RedScorpio.lab@gmail.ru

updater

version 1.0.0.4

Copyright © RedScorpio, 2022

RedScorpio.lab@gmail.com

Name "rkdumper"

log = True

debug = True

ask = False

registry = ?

No updates

==========================[ 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: 2)

1.1 Device #1: USB Hub (ports: 6)

VID = 0x8087, PID = 0x8008, REV = 0x0004 (USB 2.0)

2 Device #2: USB Root Hub (ports: 21)

2.3 Device #3: Dispositivo compuesto USB

VID = 0x2a7a, PID = 0x9587, REV = 0x0001 (USB 1.1 Low Speed)

2.7 Device #4: Rockusb Device

VID = 0x2207, PID = 0x310c, REV = 0x0100 (USB 2.0)

2.15 Device #5:

3 Device #6: USB Root Hub (ports: 2)

3.1 Device #7: USB Hub (ports: 8)

VID = 0x8087, PID = 0x8000, REV = 0x0004 (USB 2.0)

Found: LOADER device (RK3128 2207:310c) #4

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

"PARM" sign found (RKAF/RKFW FW dump)

FlashInfo

Manufacturer: Samsung (0x00)

Flash size: 7456MB (0x00e90000)

Full size: 7456MB (0x00e90000)

Block size: 512KB

Page size: 2KB

ECC bits: 0

Access time: 40

Flash CS: 0 (0x01)

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

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

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" (0x00006000) Data reading error

Critical error (NAND reading failed)

C:\RockChip Tools\3.rkDumper_1.1.1.0>
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
1. If you have root rights on device - try to use adbDumper (https://xdaforums.com/t/tool-rkdump...re-of-rockchips-devices.2915363/post-87375019)

2. If not - use RkAndroidTool with created configuration files
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Device memory is unavailable in MASKROM mode,

Try to find drivers for steady reading (it is necessary to downgrade the version)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This is not an error of the program, it is an error marking the permanent memory of the device

To be honest, I didn't really understand your actions. rkDumper does not report such an error