[Upgrading, Modifying and Unlocking] privatezs:
Thank you for replying

Now i could successfully dump the firmware images from the working device with only one red message at the system dumping process:

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

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

USB devices table (found 10 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: Realtek USB 2.0 Card Reader
VID = 0x0bda, PID = 0x0138, REV = 0x3882 (USB 2.0)
1.1.3 Device #3: USB Composite Device
VID = 0x04f2, PID = 0xb326, REV = 0x3554 (USB 2.0)
2 Device #4: USB Root Hub (ports: 8)
3 Device #5: USB Root Hub (ports: 2)
3.1 Device #6: USB Hub (ports: 4)
VID = 0x8087, PID = 0x0024, REV = 0x0000 (USB 2.0)
3.1.1 Device #7: Rockusb Device
VID = 0x2207, PID = 0x330c, REV = 0x0100 (USB 2.0)
3.1.2 Device #8: USB Input Device
VID = 0x1ea7, PID = 0x0064, REV = 0x0200 (USB 1.1)
3.1.3 Device #9: Realtek Bluetooth 4.0 Adapter
VID = 0x0930, PID = 0x021d, REV = 0x0200 (USB 2.0)

Found: LOADER device (RK3399/PX6 2207:330c) #7

--- Firmware dumping ---

Found LOADER Rockchip device

First 0x0010 NAND blocks reading

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

FlashInfo
Manufacturer: Samsung (0x00)
Flash size: 15028MB (0x01d5a000)
Full size: 15028MB (0x01d5a000)
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: unknown)
Partition "kernel" (0x0000c000) saved (format: unknown)
Partition "boot" (0x00020000) saved (format: Android boot image)
Partition "recovery" (0x00020000) saved (format: Android boot image)
Partition "backup" (0x00038000) saved (format: unknown)
Partition "cache" (0x00040000) saved (format: ext4 image)
Partition "system" (0x00600000) Filesystem file size is not equal partition size
saved (format: ext4 image)
Partition "metadata" (0x00008000) saved (format: ext4 image)
Partition "verity_mode" (0x00000040) saved (format: unknown)
Partition "baseparamer" (0x00002000) saved (format: unknown)
Partition "frp" (0x00000400) saved (format: unknown)
Partition "userdata" skipped

-- Rockchip device resetting --

Found LOADER Rockchip device

Command to reset sent successfully

Partition "system" (0x00600000) Filesystem file size is not equal partition size

saved (format: ext4 image)

Now i booted into MASKROM on the bootlooping device and using Android Tool 2.58

Notice: I noticed that the parameter mentioned the files path in Linux/Mac format, for example "Image\uboot.img" while manually selecting the file reference it as "C:\folder\uboot.img" and that's why loading parameters file showing errors cannot find images.

First i tried Upgrade section in the app and the log was:

Downloading Boot ....

Failed Downloading Boot

Then i tried to send the Firmware but got the same error.

after some digging i could found the Loader mode trigger and i could boot the device into LOADER mode

tried reading Flash ID and got readings

tried flashing the firmware but got the following:

Start Test Device

Testing Device(100%)...

and it will stuck here forever

is it some sort of hardware issue (like bad eMMC) or am i doing something wrong?

Thanks again for your help