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

Search This thread

marchnz

Senior Member
  • Nov 26, 2012
    3,297
    671
    wombleton
    Hi @RedScorpioXDA,
    I've successfully used your tool in the past to backup MTCD PX5 Android head units (android 6 to 8) on Windows 10.
    The tool fails to read from the device. I suspect this may be due to Windows 10 releases?

    I get the same error [Command to read failed] as @ms_may, and have tried:
    - Different USB Ports
    - Resetting device, powering on/off
    - Loader and MASKROM modes
    - Earlier and latest Rockchip Driver 4,7, 4.91.
    - Earlier and latest version of your tool, all which produce the same result:

    Code:
    2020.07.05 12:30:15	rkDumper (v.1.08)
    2020.07.05 12:30:15	(c) RedScorpio, Moscow, 2014-2019
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	Command parameters: "/debug" "/log" "/test" "dump"
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	Run parameters:
    2020.07.05 12:30:15		log		= 1
    2020.07.05 12:30:15		debug		= 1
    2020.07.05 12:30:15		quiet		= 0
    2020.07.05 12:30:15		mono		= 0
    2020.07.05 12:30:15		includelist	= ""
    2020.07.05 12:30:15		excludelist	= ""
    2020.07.05 12:30:15		last		= 0
    2020.07.05 12:30:15		part		= 0
    2020.07.05 12:30:15		nrst		= 0
    2020.07.05 12:30:15		load		= 0
    2020.07.05 12:30:15		memsize		= 134217728
    2020.07.05 12:30:15		basecfgpath	= ""
    2020.07.05 12:30:15		loadername	= ""
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	==========================[ START ]==========================
    2020.07.05 12:30:15	
    2020.07.05 12:30:15		.DEBUG.	Windows version	= 6.2.9200
    2020.07.05 12:30:15		.DEBUG.	PlatformId	= 2
    2020.07.05 12:30:15		.DEBUG.	_isWOW64()	= 1
    2020.07.05 12:30:15		.DEBUG.	ProductType	= 48
    2020.07.05 12:30:15	Detected OS:	Windows 8 Pro [build 9200] x64
    2020.07.05 12:30:15		.DEBUG.	RtlGetNtVersionNumbers	= 10.0.19041
    2020.07.05 12:30:15		.DEBUG.	Compatibility mode detected
    2020.07.05 12:30:15	Real OS:	Windows 10 Pro [build 19041] x64
    2020.07.05 12:30:15	
    2020.07.05 12:30:15		.DEBUG.	Version of OS is later of Windows XP (need to check rights)
    2020.07.05 12:30:15		.DEBUG.	TokenElevationType: Full (2)
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	-- Devices enumerating --
    2020.07.05 12:30:15	
    2020.07.05 12:30:15		.DEBUG.		Devs.TypeMask = 3
    2020.07.05 12:30:15	USB devices table (found 10 devices):
    2020.07.05 12:30:15	1	Device #0: USB Root Hub (ports: 3)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\.\USB#ROOT_HUB20#4&de69eb3&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}"
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	1.1	Device #1: USB Hub (ports: 6)
    2020.07.05 12:30:15		VID = 0x8087, PID = 0x8008, REV = 0x0004 (USB 2.0)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\.\USB#VID_8087&PID_8008#5&4a52522&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}"
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	2	Device #2: USB Root Hub (ports: 21)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\.\USB#ROOT_HUB30#4&35f5195e&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}"
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	2.4	Device #3: Synaptics FP Sensors (WBF) (PID=0050)
    2020.07.05 12:30:15		VID = 0x138a, PID = 0x0050, REV = 0x0060 (USB 1.1)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\?\USB#VID_138A&PID_0050#C416FFA0D49B#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
    2020.07.05 12:30:15		.DEBUG.	DriverKeyName	= "{53d29ef7-377c-4d14-864b-eb3a85769359}\0000"
    2020.07.05 12:30:15		.DEBUG.	Driver version	= 4.5.350.0 (5-24-2018)
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	2.8	Device #4: Intel(R) Wireless Bluetooth(R)
    2020.07.05 12:30:15		VID = 0x8087, PID = 0x07dc, REV = 0x0001 (USB 2.0)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\?\USB#VID_8087&PID_07DC#5&8F97EA0&0&8#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
    2020.07.05 12:30:15		.DEBUG.	DriverKeyName	= "{e0cbf06c-cd8b-4647-bb8a-263b43f0f974}\0000"
    2020.07.05 12:30:15		.DEBUG.	Driver version	= 20.100.3.1 (1-8-2019)
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	2.9	Device #5: Rockusb Device
    2020.07.05 12:30:15		VID = 0x2207, PID = 0x330a, REV = 0x0100 (USB 2.0)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\?\USB#VID_2207&PID_330A#5&8F97EA0&0&9#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
    2020.07.05 12:30:15		.DEBUG.	DriverKeyName	= "{79dfc2a8-2574-493c-ae71-52958e41dd00}\0000"
    2020.07.05 12:30:15		.DEBUG.	Driver version	= 4.90.0.0 (4-25-2019)
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	2.11	Device #6: USB Mobile Broadband Network Adapter Module
    2020.07.05 12:30:15		VID = 0x1199, PID = 0x9041, REV = 0x0006 (USB 2.0)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\?\USB#VID_1199&PID_9041#5&8F97EA0&0&11#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
    2020.07.05 12:30:15		.DEBUG.	DriverKeyName	= "{36fc9e60-c465-11cf-8056-444553540000}\0007"
    2020.07.05 12:30:15		.DEBUG.	Driver version	= 10.0.19041.1 (12-6-2019)
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	2.16	Device #7: USB Attached SCSI (UAS) Mass Storage Device
    2020.07.05 12:30:15		VID = 0x0080, PID = 0xa001, REV = 0x0204 (USB 3.0)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\?\USB#VID_0080&PID_A001#MSFT30201503310007F#{a5dcbf10-6530-11d2-901f-00c04fb951ed}"
    2020.07.05 12:30:15		.DEBUG.	DriverKeyName	= "{4d36e97b-e325-11ce-bfc1-08002be10318}\0001"
    2020.07.05 12:30:15		.DEBUG.	Driver version	= 10.0.19041.1 (6-21-2006)
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	3	Device #8: USB Root Hub (ports: 3)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\.\USB#ROOT_HUB20#4&1a0d769d&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}"
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	3.1	Device #9: USB Hub (ports: 8)
    2020.07.05 12:30:15		VID = 0x8087, PID = 0x8000, REV = 0x0004 (USB 2.0)
    2020.07.05 12:30:15		.DEBUG.	SymLink		= "\\.\USB#VID_8087&PID_8000#5&d0fe1eb&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}"
    2020.07.05 12:30:15		.DEBUG.	
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	Found:	LOADER device (RK3368 2207:330a) #5
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	--- Firmware dumping ---
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	Found LOADER Rockchip device
    2020.07.05 12:30:15	
    2020.07.05 12:30:15		.DEBUG.	Run command 'MkDir("Output")'
    2020.07.05 12:30:15	First 0x0010 NAND blocks reading
    2020.07.05 12:30:15	
    2020.07.05 12:30:15		.DEBUG.	(PartRead) Offset    = 0x0000000000000000, iDataSize = 0x0000000000002000
    2020.07.05 12:30:15		.DEBUG.	(PartRead) iBlOffset = 0x00000000, iBlCount  = 0x00000010
    2020.07.05 12:30:15		.DEBUG.	(DevRead)  BlOffset  = 0x00000000, iBlToRead = 0x10
    2020.07.05 12:30:15		.DEBUG.		Command to read NAND: iBlToRead = 0x00000010 (16)
    2020.07.05 12:30:15		.DEBUG.		WriteFile():	iRet = 0; iRetSize = 0x00000000 (0)
    2020.07.05 12:30:15	.ERROR.	Command to read failed
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	-- Rockchip device resetting --
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	Found LOADER Rockchip device
    2020.07.05 12:30:15	
    2020.07.05 12:30:15		.DEBUG.		Command to reset device
    2020.07.05 12:30:15		.DEBUG.		WriteFile():	iRet = 0; iRetSize = 0x00000000 (0)
    2020.07.05 12:30:15	.FATAL ERROR.	Command to reset failed
    2020.07.05 12:30:15	
    2020.07.05 12:30:15	==========================[ STOP  ]==========================
     

    RedScorpioXDA

    Senior Member
    Apr 6, 2012
    364
    247
    The tool fails to read from the device.
    This happens as a result of "unsure" reading.
    Try
    - change the cable (preferably short and thick)
    - exclude USB hubs (if used)
    - change the USB socket (preferably on the back of the computer)
    - change the USB version (2.0 instead of 3.0)
    - use a different computer
    I suspect this may be due to Windows 10 releases?
    No
     

    marchnz

    Senior Member
  • Nov 26, 2012
    3,297
    671
    wombleton
    This happens as a result of "unsure" reading.
    Try
    - change the cable (preferably short and thick)
    - exclude USB hubs (if used)
    - change the USB socket (preferably on the back of the computer)
    - change the USB version (2.0 instead of 3.0)
    - use a different computer

    No

    Hi,
    Thanks for your reply.

    Note that using the same USB cable/Jig with Rockchip Android tool, I was able to extract/dump each partition, calculated from first dumping the parameters (start 0, size 2).

    I was also able to then upload these partiton .imgs 'backups' to another PX5 SOM with success.

    So its not a problem with hardware. I was also unable to download your 'test version' to try that.

    Thanks,
    Marc
     
    Last edited:

    RedScorpioXDA

    Senior Member
    Apr 6, 2012
    364
    247
    Note that using the same USB cable/Jig with Rockchip Android tool, I was able to extract/dump each partition
    I do not exclude that other utilities may use some other algorithms (for example, increase the latency of waiting for a response from the device). Unfortunately, I don't have any "problem" devices for modeling. But I know for sure that the problem was solved by one of the suggested options by other users.
    I was also unable to download your 'test version' to try that.
    I'll check when I have some free time
     

    marchnz

    Senior Member
  • Nov 26, 2012
    3,297
    671
    wombleton
    This happens as a result of "unsure" reading.
    Try
    - change the cable (preferably short and thick)
    - exclude USB hubs (if used)
    - change the USB socket (preferably on the back of the computer)
    - change the USB version (2.0 instead of 3.0)
    - use a different computer

    No

    Hi @RedScorpioXDA,
    Thanks again for your reply.

    I have confirmed the issue is not hardware, the issue is rkdumper is incompatible with rockchip driver greater than 4.5 - 4.91 is latest as of writing.


    • By installing driver version 4.3. - Rockchip_DriverAssistant_v4.3 - was able to dump images with rkdumper v1.08.
    • Just to clarify - Rockchip Driver assistant version 4.5 on do not work with Rkdumper.

    This was first identified by @nalor in post 85 (thanks @nalor!) here: https://forum.xda-developers.com/showpost.php?p=78805354&postcount=85

    Would you please update your first post with this information - known bugs?
     
    Last edited:
    • Like
    Reactions: raz0r9111

    dcxx20

    New member
    Mar 10, 2007
    3
    1
    thanks for the tool. I am trying to dump an IoT device with rk3128, I think. The device (#9 below) has the rock chip USB id but a weird device ID (faked?). Is there a way to force dumping from an unrecognized device id?


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

    (c) RedScorpio, Moscow, 2014-2019
    [email protected]

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

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

    USB devices table (found 10 devices):
    1 Device #0: USB Root Hub (ports: 4)
    1.1 Device #1: USB Hub (ports: 5)
    VID = 0x1d5c, PID = 0x5012, REV = 0x0100 (USB 2.1)
    1.1.5 Device #2: Billboard Device
    VID = 0x1d5c, PID = 0x5100, REV = 0x0100 (USB 2.0)
    1.3 Device #3: USB Hub (ports: 4)
    VID = 0x1d5c, PID = 0x5002, REV = 0x0100 (USB 3.1)
    2 Device #4: USB Root Hub (ports: 26)
    2.2 Device #5: USB Composite Device
    VID = 0x045e, PID = 0x07a5, REV = 0x0777 (USB 2.0)
    2.4 Device #6: USB Input Device
    VID = 0x187c, PID = 0x0530, REV = 0x0000 (USB 0.0)
    2.5 Device #7: Qualcomm Atheros QCA61x4 Bluetooth
    VID = 0x0cf3, PID = 0xe301, REV = 0x0001 (USB 2.0)
    2.7 Device #8: USB Composite Device
    VID = 0x0bda, PID = 0x58c2, REV = 0x6202 (USB 2.0)
    2.8 Device #9: USB Composite Device
    VID = 0x2207, PID = 0x0018, REV = 0x0404 (USB 2.0)
    Disk #3

    Can't find RockChip device
     

    tryingtohack

    Member
    Dec 29, 2014
    13
    4
    Hi,

    Trying to dump my H96 Max (rk3318) device with version 1.08 but I get: "response reading error". Tried different USB cable, port, driver (v4.3 - 4.8) but still no luck. Tried to download 1.09 test (http://ge.tt/9VFDyb23) but was not able to (registered and tried different browsers). Can someone send me this file?
     
    Last edited:

    tryingtohack

    Member
    Dec 29, 2014
    13
    4
    Hi,

    Trying to dump my H96 Max (rk3318) device with version 1.08 but I get: "response reading error". Tried different USB cable, port, driver (v4.3 - 4.8) but still no luck. Tried to download 1.09 test (http://ge.tt/9VFDyb23) but was not able to (registered and tried different browsers). Can someone send me this file?

    Found v.1.09a_test on 4pda.ru :) A bit older than http://ge.tt/9VFDyb23 (v.1.09b_test) but it did the job!
     

    Attachments

    • RKFP_test.zip
      111.5 KB · Views: 204
    • rkDumper.zip
      1.2 MB · Views: 236
    • Like
    Reactions: ssota and marchnz

    ssota

    New member
    Jan 1, 2021
    4
    1
    Hello,
    I have Android 9, 4G + 64G, RK3368 / PX5 module HCT-PX5-REV13 (LPDDR-221) 20190619.
    I tried to make a backup with the rkDumper_108.zip software but it was not received. Then I tried to use the rkDumper software (version 1.09a_test) and I succeeded.
    I would like someone with experience to check if I made and received the backup for all sections.
    Here's what I got
    Thanks for the help and understanding.
     

    Attachments

    • 1.jpg
      1.jpg
      123.5 KB · Views: 81
    • 2.jpg
      2.jpg
      198.9 KB · Views: 84
    • Log_BackUp_HCT-PX5-REV13(LPDDR-221)_20190619.txt
      3.6 KB · Views: 23
    • 2020-12-29 21-14-34.JPG
      2020-12-29 21-14-34.JPG
      3.4 MB · Views: 77

    ssota

    New member
    Jan 1, 2021
    4
    1
    Hello,
    I have Android 9, 4G + 64G, RK3368 / PX5 module HCT-PX5-REV13 (LPDDR-221) 20190619.
    I tried to make a backup with the rkDumper_108.zip software but it was not received. Then I tried to use the rkDumper software (version 1.09a_test) and I succeeded.
    I would like someone with experience to check if I made and received the backup for all sections.
    Here's what I got
    Thanks for the help and understanding.


    Hi @marchnz I added the file with Log backup and print screen the files that were saved. Tell me if all the partitions were saved for recovery in case of need or not?
    Thanks
     

    ssota

    New member
    Jan 1, 2021
    4
    1
    Nice one, from the logs and files/sizes looks OK to me.

    I am unable to download 1.09atest - are you able to share it with me.

    Thanks for checking my backup. I am attaching the file rkDumper_109_test, Rockchip_Driver_Assistant_4.5, Rockchip_driver_USB_fix.
    It works great in such a bundle. (Win 10 x64)
     

    Attachments

    • rkDumper_109_test.zip
      111.5 KB · Views: 205
    • Rockchip_Driver_Assistant_4.5.zip
      9.4 MB · Views: 129
    • Rockchip_driver_USB_fix.zip
      687.2 KB · Views: 158
    • Like
    Reactions: marchnz

    Sdpuk2020

    Member
    Dec 10, 2020
    13
    2
    Has anyone managed to upgrade a Sharp rz-e302 point of sale 10” tablet?

    currently on Android 4.4 but need a minimum of 5.5 for the app I wish to run.

    it’s an rk3188 device.

    can anyone help? Or give me advice how to back up the rom to make a custom rom?

    thanks
     

    wwwryan

    Member
    Jun 27, 2012
    35
    7
    Trying to pull image from this rk3399 device but doesn't seem to pick it up. Any ideas? Maybe I need custom version?

    Code:
    1.5     Device #7: Android ADB Interface
                    VID = 0x2207, PID = 0x0006, REV = 0x0310 (USB 2.0)
     

    Top Liked Posts

    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone