yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] E--Man:
UPDATE:

Got it to work.

RedScorpio, here is some additional information to help you with your testing including your debuggers. After it failed, I tried again and it still failed with this:

Found LOADER Rockchip device

Data reading error

Critical error

!!! Test pos #11

!!! Test pos #12

!!! Test pos #13

!!! Test pos #14

On a hunch, I tried to reboot and go back into Bootloader mode and try again and it worked, so it looks like it might have to do with a timeout of some sort.

Here is the success log:

==========================[ 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 fil

)

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" saved (format: ext4 image)

Partition "radical_update" saved (format: unknown)

Partition "userdata" skipped

-- Rockchip LOADER device resetting --

Found LOADER Rockchip device

Command to reset sent successfully

Command to reset confirmed

!!! Test pos #1

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

!!! Test pos #2

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

!!! Test pos #3

!!! Test pos #4

!!! Test pos #5

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

!!! Test pos #6

!!! Test pos #9

!!! Test pos #10

!!! Test pos #11

!!! Test pos #12

!!! Test pos #13

!!! Test pos #14

!!! Test pos #15

RedScorpio, if you want more logging verbosity, let me know and I will PM you.

Just a couple of quick questions:

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

2) Why was the "userdata" partition skipped? Do I need this if I will need to revert back? If this is the standard /data partition, then I think I would want to dump this as well. Is it possible? Edit: I tried using the "/user" option using "rkDumper /user dump" but it still skipped dumping the user partition. Not sure if this is an issue or if I am doing something wrong.

3. If I want to revert and load only 1 partition, can I do that or is it all or nothing?

Thanks.

Best Regards,

E.
[Upgrading, Modifying and Unlocking] E--Man:
Happy Holidays [MENTION=4582467]RedScorpioXDA[/MENTION] and everyone else. Please let me know if you had a second to look over my messages above. Thanks.
[Upgrading, Modifying and Unlocking] E--Man:
Bump
[Upgrading, Modifying and Unlocking] E--Man:
HI [MENTION=4582467]RedScorpioXDA[/MENTION], hope you had great holidays. Did you get a chance to check out my questions above? Thanks in advance!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Yes

I need full log-file with /dump option to check

You can use checkboxes in RKAndroidTool to choose partition
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.01 Windows) ready

! Release;

+ support of RK2928 added;

+ support of RK3126 added;

+ support of RK3368 added;

+ detection of MTP&PTP modes added;

~ some algorithms improved.
[Upgrading, Modifying and Unlocking] Oma7144:
Thank you for your great work! Is it possible to dump the loader, too?

- Oma -
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Sorry, but I haven't any idea how make it
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.02 Windows) ready

~ /user key logic changed;

~ errors handling changed;

+ parm mode added;

+ /pfile key added.
[Upgrading, Modifying and Unlocking] kiko18:
great tool,

hope you will add more supported chip :)

keep it up :D
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I need testers for this
[Upgrading, Modifying and Unlocking] ultradj83:
Images to update.img

Dears,

once all .img files have been dumped (including user), how to create a single update.img?

Thanks a lot.
[Upgrading, Modifying and Unlocking] NEOCRIVI:
Hi

Thanks for the dumper tool,

I try dump fw of eStar 9 Zoom QC MID9054 rk3126 :

Can this tool flash this backup in dead device?

Thanks and best regards!
[Upgrading, Modifying and Unlocking] blakegriplingph:
It's from an RK3326 and I am not sure how to go ahead with it without running the risk of permabricking this thing.
[Upgrading, Modifying and Unlocking] mobifixit:
Always error

C:\rkDump>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 Single Language [build 9200] x64

Real OS: Windows 10 Home Single Language [build 19044] x64

-- Devices enumerating --

USB devices table (found 6 devices):

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

1.2 Device #1: USB Composite Device

VID = 0x174f, PID = 0x243f, REV = 0x0008 (USB 2.0)

1.5 Device #2: Rockusb Device

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

1.6 Device #3: Goodix fingerprint

VID = 0x27c6, PID = 0x55b4, REV = 0x0100 (USB 2.0)

1.10 Device #4: Intel(R) Wireless Bluetooth(R)

VID = 0x8087, PID = 0x0aaa, REV = 0x0002 (USB 2.0)

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

Found: LOADER device (RK3288 2207:320a) #2

--- 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] mobifixit:
now what about the condition when you dont have uBOOT and cant make backups?
[Upgrading, Modifying and Unlocking] fedessgl:
Hello! I have been long reading this thread. I have a RK3528 TV Box (this one) and I'm trying to do a firmware backup. Using rkdumper 1.1.2.0 and different Driver Assistan versions (4.1.1, 4.2, 4.3 , 4.5...) and seems I cannot complete it. As I understand, this may have write protection, I am right?

Edit: For the drivers to work I had to do the following:

1. I used v4.3 but the same worked with other (I tested 4.1 to 4.5). I edited the config.ini files on the following lines:

CUSTOM_VID=0x2207

CUSTOM_PID=0x350C

2. Run DriverInstall.exe and click in Install Driver. Wait for it to finish.

3. Open Windows' "Device Manager", keep it at a side of my display to see for changes (during next step)

4. Connect my RK3528 device in loader mode. In my case to do this, I have to press the reset button with the power and USB cable unplugged, and connect the USB, wait 2 - 3 sec and release reset button. A new device appears in windows' Device Manager, with a "warning" signal. Note: I had to plug the USB only, not the power plug! Also, I had to use the USB 2.0, not working if I use the USB 3.0 port.

5. In the device with the warning, right click and Update Driver. Manually search the folder "\Driver\x64\win8" and click ok, also ok when windows says that driver is not compatible for the device.

6. On a CMD with Admin rights, run "rkdumper.exe dump" command.

This is what rkdumper shows on screen:
[Upgrading, Modifying and Unlocking] fedessgl:
Seems really advanced to me. Would love to do this. As seen in my previous post in this thread, I understand I could completly dump the uboot partition (it does not say "unknown"). Provided the mentioned file, would you kindly guide me on how to do this same hack?
[Upgrading, Modifying and Unlocking] fedessgl:
What about dumping those devices using UART?
[Upgrading, Modifying and Unlocking] mobifixit:
i had to read all pages(driver problems solved) to being able to run and dump a few partitions but

LOADER device (RK3288 2207:320a) #2

--- 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" (0x00004000) saved (format: unknown)

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

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

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

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

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

Partition "rootfs" (0x00408000) saved (format: unknown)

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

-- Rockchip device resetting --

Found LOADER Rockchip device

Command to reset sent successfully

but all the partitions are filled with CC CC except BOOT ,UBOOT AND TRUST and i cant find that magic bytes to patch FD 7B BE A9 someone have a easier method?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
If there is root on the device, try adbDumper
[Upgrading, Modifying and Unlocking] mobifixit:
there is no access to ADB or Recovery its not a TV BOX but have the read protection it reads CCCCCC after 32mb is there any other way?Please help me out i just have windows system

below is the 32mb attached dump please see someone if the uboot can be patched?

@pseudolobster help
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Pay attention to the message
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Although I would do

'49 01 00 54' -> '0a 00 00 14'

(the assumption is purely theoretical, has not been tested due to the lack of a suitable test subject)
[Upgrading, Modifying and Unlocking] mobifixit:
but there is no 49 01 00 54 present in my dump
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Well, let's see your dump
[Upgrading, Modifying and Unlocking] blakegriplingph:
I am also trying to dump the ROM off my LeapPad Academy running on an RK3326 and like many others it spits out CCs. Rooting isn't an option either as I do not have a clean dump of the boot image to begin with anyway so the uboot hacking method is my only hope with this one. I got the uboot file from an OTA update zip which fortunately had the complete uboot and RKloader binaries but not the rest as those are mostly incremental patch files.

If I unpack uboot.img using your tool it spits out a uboot.bin and two other blank files named uboot_1.bin and uboot_3.bin, but if I repack it, the uboot image isn't packed in the same way as stock and thus my tablet either hangs up on the logo or refuses to power on at all unless I force it into maskrom mode and flash the stock uboot back.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I don't know which version of imgRePackerRK you are using. I'm using the latest test version 1.0.7.7

At the same time, there are no additional files

Quite a likely result, 4 bytes appeared in the boot header, the purpose of which is unknown to me (perhaps it does not matter). Therefore, the reverse packaging does not give an exact match (the difference is just for these 4 bytes).

The sequence "81 00 01 8B 24 00 02 8B 9F 40 40 F1 49 01 00 54" is located at 0xfbfc of uboot.bin
[Upgrading, Modifying and Unlocking] blakegriplingph:
I tried it on both the latest stable build and the test build you sent to me last month.

If you compare the stock uboot to a repack of it the other copies of uboot are missing on the repack hence why they're quite different when you load the two img files side by side using a hex editor.
[Upgrading, Modifying and Unlocking] blakegriplingph:
Alright, I can confirm that repacking uboot using the latest test version only results in changing just the four bytes you mentioned. To be doubly sure I also tried hex-editing uboot.bin and repacking it, and it all turned out good. ;)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Is the device being downloaded? Is the firmware being dumped?
[Upgrading, Modifying and Unlocking] blakegriplingph:
I flashed the modified uboot.img back to my LeapPad Academy and it now boots up properly. And yes the firmware's now being dumped correctly too. ;)
[Upgrading, Modifying and Unlocking] mobifixit:
sir Any progress yet ?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
And where is the dump of your device?

uboot is needed
[Upgrading, Modifying and Unlocking] blakegriplingph:
If you can get an OTA update ZIP from your device there's a chance that it has a stock uboot image. That's where I got mine.
[Upgrading, Modifying and Unlocking] lost101:
In case it helps others, I just managed to dump the firmware for my e-reader (Meebook M7 (RK3566/RK3568)) in Windows 10 (22H2) using the 'DriverAssitant v4.5' Win8 driver. Also worth mentioning, I had to use the specific command: adb reboot loader
[Upgrading, Modifying and Unlocking] mobifixit:
i already attached the 32mb dump and uboot start at 7FFFFF TILL 4MB

ANYWAYS i attached the backup which RKdumper readed it has uboot
[Upgrading, Modifying and Unlocking] mrmagicm:
Does Rkdumper support H96 MAX V58 RK3588 4x Cortex-A76 and 4x Cortex-A55 please? (I have this model)

Does a twrp similar tool exists for this box?

​
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Try version 1.1.2.1

Sorry, I don't even understand the question. In any case, you can try it yourself.
[Upgrading, Modifying and Unlocking] mrmagicm:
YES , i'll Test RKDUMPER 1.1.2.1 as soon as I can.

You seems to know about rockchip's device, I have a rockship device that i've installed android 12 new firmware on it, but my stf bravia tv remote isn't detected by box, my previous firmware could detect it, would you have a clue what apk or component to install on a rockchip's device to make a sony remote detected by it?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, no
[Upgrading, Modifying and Unlocking] mrmagicm:
If I have the 2 firmwares, one works with the remotes, and the others doesn't is there a way to decipher from the working one what could be missing or how to analyze from it?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
It is unclear what this question has to do with this utility.
[Upgrading, Modifying and Unlocking] razien:
Hello, any fix with unknown format and response reading error when doing checkings?..

another thing is imgRePackerRK_1077 version is unable to unpack them probably due to this "unknown" thing on every images rkdumper dumped..

please check attached images for versions used, etc..
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I know only one method - to downgrade the drivers (possibly with the addition of the necessary VID/PID)

This is due to read protection - if you look into the obtained files, you will see only 0xCC
[Upgrading, Modifying and Unlocking] razien:
I see those 0xCC on most images, so those dumped files with unknown format made by rkdumper are useless/not good?, how to get the right dumps or fix/remove that read protection?, phone is not bootable to system anymore.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Yes.

I don't know what can be done for this type of firmware (RKFP). And I don't have a RockChip device at all right now.
[Upgrading, Modifying and Unlocking] razien:
okay, that's sad, hoping to get a solution to this soon. Thanks
[Upgrading, Modifying and Unlocking] gusarg81:
Hi,

I´am trying to Dump my tablet partitions (rk3126), but is not working.

With RK Android Tool I can list/read all partitions (just in case).

Attaching logs. Any tip?

Thanks.
[Upgrading, Modifying and Unlocking] timik01:
hello, I'm trying to remove the dumping limit from uboot. I can't understand the scripts for calculating the checksum. Can you help me?

I did it following the post by user flubba86 https://www.ozbargain.com.au/node/842150?page=1#comment
[Upgrading, Modifying and Unlocking] zongzi1021:
If I use Rockchip_DriverAssitant v5.1, I can see the loader device in RKDevTool, but rkDumper (1.08) reports "Can't find RockChip device". If I use Rockchip_DriverAssitant v4.3, RKDevTool reports "No devices found", and rkDumper (1.1.2.1) shows the following message. How can I resolve this issue?

(base) PS C:\Users\haolin\Downloads\rkDumper_1.1.2.1> .\rkDumper.exe dump

rkDumper (version 1.1.2.1)

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 11 Pro [build 22631] x64

-- Devices enumerating --

USB devices table (found 12 devices):

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

1.2 Device #1: USB Composite Device

VID = 0x2f4c, PID = 0x1007, REV = 0x1101 (USB 2.0)

1.11 Device #2: USB Hub (ports: 2)

VID = 0x05e3, PID = 0x0610, REV = 0x6805 (USB 2.1)

1.11.1 Device #3: USB Hub (ports: 4)

VID = 0x05e3, PID = 0x0610, REV = 0x6815 (USB 2.1)

1.11.1.1 Device #4: LIGHTSPEED Receiver

VID = 0x046d, PID = 0xc539, REV = 0x3906 (USB 2.0)

1.11.1.2 Device #5: USB Composite Device

VID = 0x1ea7, PID = 0x0002, REV = 0x0200 (USB 2.0)

1.11.1.3 Device #6: USB Composite Device

VID = 0x054c, PID = 0x0ce6, REV = 0x0100 (USB 2.0)

1.11.1.4 Device #7: USB Composite Device

VID = 0x0d8c, PID = 0x0012, REV = 0x0100 (USB 1.1)

1.14 Device #8: Rockusb Device

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

1.25 Device #9: USB Attached SCSI (UAS) 大容量存储设备

VID = 0x152d, PID = 0x0562, REV = 0x0209 (USB 3.2)

1.26 Device #10: USB Hub (ports: 1)

VID = 0x05e3, PID = 0x0620, REV = 0x6805 (USB 3.2)

1.26.1 Device #11: USB Hub (ports: 4)

VID = 0x05e3, PID = 0x0620, REV = 0x6815 (USB 3.2)

Press any key...

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

--- 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:
No. You can try to use rkAndroidTool
[Upgrading, Modifying and Unlocking] #Vangreen:
Thanks works perfect on windows 10.

If someone hve problem with drivers on w10:

Download and run this

http://download2125.mediafire.com/y8dfxexmsdug/78v4iqynfkny6xt/Rockchip+Win10+Driver.reg

Then download adb and rk drivers(4.4) and install it

http://universaladbdriver.com/category/download/

https://mega.nz/#!volAjIbS!UVwms787ffv_wQYmO-e0jTS_0W_JloQ1o-ttzVMvYL0
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.03 Windows) ready

+ support of RK3229 added;

+ /last key added;

+ RSCE file size correction added.
[Upgrading, Modifying and Unlocking] DZ-DEVELOPER:
Can you Plz profide the SRC "Source Code" to insert in Easy InterFace

I need "SRC"
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Do you mean rksrc?
[Upgrading, Modifying and Unlocking] DZ-DEVELOPER:
Yes
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
http://www.androidtablets.net/threa...for-custom-firmwares-for-rockchip-rk28xx.439/
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Victory Day celebrations

rkDumper

Utility for backup firmware of RockChip's devices

New version (1.04 Windows) ready

+ support of RK3328 added;

~ minor improvements.
[Upgrading, Modifying and Unlocking] DunoCZ:
*deleted*
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Why do you think they are corrupted?
[Upgrading, Modifying and Unlocking] cyt0plas:
Trying to dump an Insignia device (RockUSB Sofia):

-- Devices enumerating --

Devices table (found 4 USB devices):
1 Device #0: USB Root Hub (ports: 18)
1.1 Device #1: Rockusb Device
VID = 0x8087, PID = 0x0912, REV = 0x0100
1.5 Device #2: USB Composite Device
VID = 0x064e, PID = 0x3401, REV = 0x0011
1.7 Device #3: Intel(R) Wireless Bluetooth(R)
VID = 0x8087, PID = 0x0a2b, REV = 0x0010

Can't find RockChip device
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
misc - really unknown for me format

kernel - binary file (nothing to unpack)

kpanic - really unknown for me format

backup - usually short image, but I don't know what is it in your case
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
This is unknown for me VID/PID pair

What is this device? What is the chipset?

Update. Please send me full log

rkDumper /log /debug /test scan
[Upgrading, Modifying and Unlocking] cyt0plas:
Log attached.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I don't see any RockChip device
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
rkDumper

Utility for backup firmware of RockChip's devices

New version (1.05 Windows) ready

+ /load key added;

+ "idb" command added;

+ support of RK3399 added;

+ support of RK2818 added;

+ "chip" command added;

+ "bad" command added;

+ "MASKROM mode" detection added;

~ minor improvements.
[Upgrading, Modifying and Unlocking] Betrayal92:
RK3230 doesn't seem to work, don't know if is a driver thing or what....i tried on USB debug, Vol- and Power show me recovery and Windows doesn't recognize it, i saw somewhere that i had to press Vol+ and Power but it only takes to charge icon...
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please provide log

rkDumper /log /debug /test dump

and name of device
[Upgrading, Modifying and Unlocking] jvercout:
Hi there,

I'm trying to dump a smartwatch, not yet available on the market. The RK chipset is RK6321

I got the following scan result:

VID = 0x8087, PID = 0x0928, REV = 0x0231 (bcdUSB = 0x0200)

You can find below the full scan result view

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

(c) RedScorpio, Moscow, 2014-2017
RedScorpio@land.ru

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

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

USB devices table (found 10 devices):
1 Device #0: USB Root Hub (ports: 15)
1.1 Device #1: Intel Mobil MI
VID = 0x8087, PID = 0x0928, REV = 0x0231 (bcdUSB = 0x0200)
1.2 Device #2:
1.4 Device #3: Intel(R) Wireless Bluetooth(R)
VID = 0x8087, PID = 0x0a2a, REV = 0x0001 (bcdUSB = 0x0201)
1.5 Device #4: USB-Eingabegerät
VID = 0x06cb, PID = 0x7244, REV = 0x0005 (bcdUSB = 0x0200)
1.6 Device #5: USB-Verbundgerät
VID = 0x1bcf, PID = 0x2c79, REV = 0x0004 (bcdUSB = 0x0200)
1.8 Device #6: Wacom Device
VID = 0x056a, PID = 0x00ec, REV = 0x0131 (bcdUSB = 0x0200)
2 Device #7: USB Root Hub (ports: 3)
2.1 Device #8: USB Hub (ports: 8)
VID = 0x8087, PID = 0x8001, REV = 0x0003
2.1.7 Device #9: USB-Eingabegerät
VID = 0x0483, PID = 0x91d1, REV = 0x0035 (bcdUSB = 0x0200)
-- Devices enumerating --

USB devices table (found 10 devices):
1 Device #0: USB Root Hub (ports: 15)
1.1 Device #1: Intel Mobil MI
VID = 0x8087, PID = 0x0928, REV = 0x0231 (bcdUSB = 0x0200)
1.2 Device #2:
1.4 Device #3: Intel(R) Wireless Bluetooth(R)
VID = 0x8087, PID = 0x0a2a, REV = 0x0001 (bcdUSB = 0x0201)
1.5 Device #4: USB-Eingabegerät
VID = 0x06cb, PID = 0x7244, REV = 0x0005 (bcdUSB = 0x0200)
1.6 Device #5: USB-Verbundgerät
VID = 0x1bcf, PID = 0x2c79, REV = 0x0004 (bcdUSB = 0x0200)
1.8 Device #6: Wacom Device
VID = 0x056a, PID = 0x00ec, REV = 0x0131 (bcdUSB = 0x0200)
2 Device #7: USB Root Hub (ports: 3)
2.1 Device #8: USB Hub (ports: 8)
VID = 0x8087, PID = 0x8001, REV = 0x0003
2.1.7 Device #9: USB-Eingabegerät
VID = 0x0483, PID = 0x91d1, REV = 0x0035 (bcdUSB = 0x0200)

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

Could you please check if you can provide an update?

best, jvercout