yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] acocalypso:
Hi

I tried to unpack the image for a95x r3 rk3318 but it seems that the system.img cannot be extracted:

imgRePackerRK.exe /2nd /rkcrc A95XR3-RK3328.img

--- Firmware unpacking ---

2-nd layer file unpacking
sparse image format detected
"C:\Users\Aco\Desktop\Rockchip\imgRePackerRKa\A95XR3-RK3328.img.dump\Image\system.img" (sparse image) unpacking
Processed blocks = 524288
Stored CRC32 = 0x00000000
Calculated CRC32 = 0x9b59d6b0
Stored and calculated CRC32 are not equal
Probably CRC32 don't used
Configuration file"C:\Users\Aco\Desktop\Rockchip\imgRePackerRKa\A95XR3-RK3328.img.dump\Image\system.img.cfg"
created
Unpacked image format: ext4 image (16)

Ext3/Ext4 file properties:

Size: 2147483648
Label: "/"
Blocks count: 524288
Reserved blocks count: 0
Free blocks count: 60086
Block size: 4096
Blocks per group: 32768
Inodes count: 131072
Free inodes count: 127648
Inode size: 256
Inodes per group: 8192
Reserved GDT blocks: 127
"C:\Users\Aco\Desktop\Rockchip\imgRePackerRKa\A95XR3-RK3328.img.dump\Image\system.img" unpacked

or did I do something wrong?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
all unpacked (sparse -> ext4)
[Upgrading, Modifying and Unlocking] Aaaron16:
How does one repack the ramdisk for boot.img using this? I'm getting an error "Can't unpack file", but the boot.img.dump file seems to have contents. Here's the result from

imgrepackerrk boot.img

[COLOR="Lime"]
imgrepackerrk (version 1.07h_test linux)
Rockchip firmware batch/update images unpacker/packer

(c) RedScorpio, Moscow, 2013-2019
RedScorpio@land.ru
[/COLOR]
Detected OS:
Ubuntu 16.04.6 LTS \n \l
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
==========================[ START ]==========================

--- Firmware unpacking ---

2-nd layer file unpacking
Android boot image format detected
"boot.img" (Android boot image) unpacking
Image properties:
Type Android boot image ("ANDROID!")
Version = 0 (0x00000000)
OSversion = 8.0.0/2017.10
KernelSize = 0x012c0808
RamdiskSize = 0x0023258c
SecondFSize = 0x0006da00
Kernel (boot.img.dump/kernel) extracted
Ramdisk (boot.img.dump/ramdisk) extracted
"boot.img.dump/ramdisk" (gzip/cpio) unpacking
[COLOR="Red"] Can't unpack file[/COLOR]
Second file (boot.img.dump/second) extracted
"boot.img.dump/second" (Rockchip resources image file) unpacking
Image properties:
Type: Rockchip resources image file (RSCE)
RSCE image version = 0 (0x0000)
RSCE file table version = 0x0000
Image header size = 0x01 (512)
File table offset = 0x01 (512)
File table record size = 0x01 (512)
File count = 2
"rk-kernel.dtb" extracted (format: unknown)
"logo.bmp" extracted (format: bitmap image file)
BasePath is empty
Configuration file"boot.img.dump/second.cfg" created
"boot.img.dump/second" unpacked

Configuration file"boot.img.cfg" created
"boot.img" unpacked
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Linux version of imimgrepackerrk uses the built-in OS capabilities to decompress gzip/cpio files. So look for reasons on your computer.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I downloaded the ro6hc5.img and did a control repacking. The only difference with simple repacking is the length change (apparently you just copied the entire partition, so the file is longer)

I think - this is the cause of the problem
[Upgrading, Modifying and Unlocking] rickou26:
Hello RedScorpioXDA,

Unpack and Repack System.img works with RK 3318 firmware (imgRePacker test H).

If I don't modify the files, only unparck and Reparck, and compare the original to the new one, I have some small differences.

A small area of ​​binary is different and it is not CRC.

I have not tested the result on my device, it may work.

Do you have any idea where this difference comes from?

Thank you.

Extract and Repack Boot.img work fine (same file if no change)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I think you're talking about Sparse image. Unfortunately, I do not know the real coding algorithm and I use my own (it is tested and workable according to consumers, but I can not give any guarantees)
[Upgrading, Modifying and Unlocking] rickou26:
@ RedScorpioXDA,

Thank you for this information and for your work.

You are right, after unpack / pack the firmware image of my HK1 Max 3318 RK (I made a mistake saying system.img !) .

I flashed my box and everything works fine.

Can you integrate unpack system.img to folder file and back pack folder to img?

Thanks again.
[Upgrading, Modifying and Unlocking] rickou26:
@ RedScorpioXDA,

Thank you for this information and for your work.

You are right, after unpack / pack the firmware image of my HK1 Max 3318 RK (I made a mistake saying system.img !) .

I flashed my box and everything works fine.

Can you integrate unpack system.img to folder file and back pack folder to img (win 10)?

Thanks again.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I am against unpacking file systems when they can simply be mounted
[Upgrading, Modifying and Unlocking] rickou26:
Hi,

I understand your opinion.

On Windows, mount Android partition and extracting the files is easy.

But to modify and save the image partition I have not yet found a simple solution. I think only a virtual machine is suitable.

Do you have a better solution?

Thank you.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I usually use a virtual machine
[Upgrading, Modifying and Unlocking] rickou26:
Hi RedScorpioXDA,

I installed Ubuntu and mounted system.img.iso. Now I have to find out how to modify the permissions to modify some elements and find the right tools to do it (build.prop for example) ...

After modification I just have to unmount system.img or Repack -> sudo make_ext4fs ............ new_system.img /system

I have another question, under windows!

I have unpacked 2 system.img, one is 2,093,666,512 bytes (1.94 GB), the other is 2,074,689,744 bytes (1.93 GB) and yet the sytem.img.iso image has the same weight 2 147,483,648 bytes (2 GB).

Have you set this value or just the hazard?

thanks again for your help

Rickou26
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
To be honest, I didn't understand the question
[Upgrading, Modifying and Unlocking] rickou26:
Hi,

Have you set the size of the blocks or files in your tool code ?

thank's
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Nothing changes
[Upgrading, Modifying and Unlocking] rickou26:
Thank you.
[Upgrading, Modifying and Unlocking] mohy1376:
boot.img

Hi, thanks for this tool.

When I unpack the firmware and after that boot.img and then repack them without any changes, my device gets stuck at boot logo and resets continuously.

how can I solve this? I need to change the boot logo, but it gets stuck even without any changes, only when I unpack the boot.img.

device: N5 Nova (RK3318)

firmware: mega.nz/#!UXRnCYoJ!VwP-010Gd-P4c4UmsUCCRhyrDfOTFhmTHGS0FU3ULEE (RK3318-9.0-MGCTV15020190805.img)
[Upgrading, Modifying and Unlocking] rickou26:
Hi,

work for me (H version)

https://xdaforums.com/showpost.php?p=81206365&postcount=340
[Upgrading, Modifying and Unlocking] aphilgr1:
Dear all,

I have a bricked my Android Head Unit flashing and incompatible rom that won't enter recovery mode. After a lot of research, I managed to go into MaskRom mode and I am ready to flash Stock firmware again. The problem is that my firmware comes in .zip and not update.img format.

I am too much of a rookie to use this tool. Would anyone be kind enough to download my stock firmware from here , repack it in .img format and share a link?

Your help will be much appreciated (and have me get rid of a huge headache!!!)

Thanks in advance
[Upgrading, Modifying and Unlocking] donmega_icecube:
I have the exact same problem, I've been fiddling with this for the past 3 weeks and i never managed to get it passed the continuous boot-loop of the initial logo. but my device is the H96Max TV Box with Android 9.0, i have 2 factory roms for my box and both of them work fine as stock.

firmware: https://wetransfer.com/downloads/9744e09a0802b1e3c8c97c355a20a2e120200221075517/560d29

anyone's help is greatly appreciated, willing to donate
[Upgrading, Modifying and Unlocking] narcorj:
please try this, it worked for me on a docker container running ubuntu:

sudo dpkg --add-architecture i386

sudo apt update

sudo apt install libc6:i386 # GNU C Library: Shared libraries (from apt show)

originally extracted from stackoverflow. (I can't post links here yet, however, search for: bash-no-such-file-or-directory on stackoverflow)
[Upgrading, Modifying and Unlocking] kewuni12:
ok, already got thanks, please pm.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
http://ge.tt/2U5vOF93
[Upgrading, Modifying and Unlocking] Peluz1n:
I was having same issue, version 107_h solved the problem:D
[Upgrading, Modifying and Unlocking] fldc:
Nothing lets me download from this site, nothing is happening when pressing download, sometimes the download start but stalls forever, could anyone upload this file anywhere else?
[Upgrading, Modifying and Unlocking] Soldiaz:
Wow! Really awesome....

Tested with HK1 mini Android PIE firm, have some questions:

I managed to split up into bootloader.img, vendor.img...and so on but could not alter anything

Then I unpacked using imgRePackerRK.exe /2nd which results in boot.img.dump, recovery.img.dump ...BUT none unpacked SYSTEM. Only have system.img and system.img.iso

How do I edit those?

Kind regards
[Upgrading, Modifying and Unlocking] Soldiaz:
German translation...mmh...cannot be uploaded
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
You can mount this disk in Linux (for example, in a virtual machine) and do whatever you need to do with it
[Upgrading, Modifying and Unlocking] Soldiaz:
Ok, Windows not possible?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
You can use virtual machines in the VirtualBox environment (very light and convenient)
[Upgrading, Modifying and Unlocking] spannernick:
I am getting a error. "Can't open file "" for reading" when I am trying to packer the img file...?

It unpacked it OK.

C:\AA MD Flashback 2018\imgRePackerRK>imgRePackerRK.exe sega_update.img.dump

imgRepackerRK (version 1.07h_test windows)
Rockchip firmware batch/update images unpacker/packer

(c) RedScorpio, Moscow, 2013-2019
RedScorpio@land.ru

Detected OS: Windows 8 Pro [build 9200] x64
Real OS: Windows 10 Pro [build 19042] x64
==========================[ START ]==========================

--- Firmware creating ---

- "image.cfg" configuration file reading -
image.cfg was read

- "package-file" configuration file reading -
"package-file" was read

- "parameter" configuration file reading -
"parameter" was read

- Files checking -
parameter (parameter) checked (file size = 0x0000027c, partition size = 0x00400000)
emulator (emulator_scd.img) checked (file size = 0x0062f000, partition size = 0x00800000)
data (data_no_test_sd_on.img) checked (file size = 0x08400000, partition size = 0xfffffc00)
backup (RESERVED) skipped

-- Injecting into "sega_update.img" --
- Image header (RKFW) injecting -
Image properties:
Type RockChip batch image ("RKFW")
Version 4.4.2
Date 2021.04.24
Time 01:23:20
ChipID 0x00000060
Code(?) 0x01050000
RKFWtype 0x00000001
Unknown_1 0x00000000

Image header injected

Can't open file "" for reading

C:\AA MD Flashback 2018\imgRePackerRK>
[Upgrading, Modifying and Unlocking] spannernick:
Trying it on Lunux now.

On Linux its says now... "Can't open file ".img.dump/data_no_test_sd_on.img" for reading"

commodoreos@commodoreos-virtual-machine:~/AA_MD_Flashback_2018/imgRePackerRK$ sudo /home/commodoreos/AA_MD_Flashback_2018/imgRePackerRK/imgrepackerrk / rkcrc sega_update_pico.img.dump

imgrepackerrk (version 1.06 linux)
Rockchip firmware batch/update images unpacker/packer

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

Detected OS:
Linux Mint 20 Ulyana \n \l
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=20
DISTRIB_CODENAME=ulyana
DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana"
NAME="Linux Mint"
VERSION="20 (Ulyana)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20"
VERSION_ID="20"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=ulyana
UBUNTU_CODENAME=focal
==========================[ START ]==========================

--- Firmware creating ---

- "image.cfg" configuration file reading -
image.cfg was read

- "package-file" configuration file reading -
"package-file" was read

- "parameter" configuration file reading -
"parameter" was read

- Files checking -
package-file (package-file) checked
parameter (parameter) checked (file size = 0x0000027c, partition size = 0x00400000)
emulator (emulator_scd.img) checked (file size = 0x0062f000, partition size = 0x00800000)
data (data_no_test_sd_on.img) checked (file size = 0x08400000, partition size = 0xfffffc00)
backup (RESERVED) skipped

-- Injecting into "sega_update_pico.img" --
- Image header (RKFW) injecting -
Image properties:
Type RockChip batch image ("RKFW")
Version 4.4.2
Date 2021.04.24
Time 17:55:09
ChipID 0x00000060
Code(?) 0x01050000
RKFWtype 0x00000001
Unknown_1 0x00000000

Image header injected

Can't open file ".img.dump/data_no_test_sd_on.img" for reading
commodoreos@commodoreos-virtual-machine:~/AA_MD_Flashback_2018/imgRePackerRK$
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please provide link to image
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Is this the original firmware? There is no "package-file" part in it
[Upgrading, Modifying and Unlocking] xmannv:
RedScorpioXDA Can't unpack Android 11 firmware for H96 MAX (Android 11, SoC RK3566)​
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Provide link, please
[Upgrading, Modifying and Unlocking] xmannv:
Thanks reply, link firmware: H96Max RK3566 https://disk.yandex.ru/d/F29OpGlUWmyfKA?w=1 or X88 Pro RK3566 https://drive.google.com/file/d/1Om715LNCj2CHGxXAhDkNQErHpLxKvOUh/view
[Upgrading, Modifying and Unlocking] zeroprobe:
@RedScorpioXDA

I've unpacked H96 Max RK3566 with modified binary to bypass chip id check. If the OP wants to include a bypass option that would be cool.

Seems to work as Boot.img was extracted fine.

Image properties:

Type RockChip batch image ("RKFW")

Version 11.0.0

Date 2021.04.21

Time 21:27:07

ChipID 0x33353638
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I don't understand you. Bypass of chip id check is standard option of utility (/cid option)
[Upgrading, Modifying and Unlocking] cth_72:
Hello

Trying to unpack some arcade1up firmwares that use rockchip boards. I've tried the newest version of the unpacker 1.07h on both on linux and windows and get unsupported format.

Example of the firmware can be found here https://arcade1up.com/pages/ms-pac-man™-4-firmware-update-for-sku-8262 . There is a .img file in the update folder of the archive.

Thank you in advance for any assistance.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Unfortunately, this is a non-standard firmware (the header has been removed)
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please provide log-file (/log /debug options) and (if possible) link to firmware
[Upgrading, Modifying and Unlocking] hurray:
Thank you very much for the tool! :good:

I am able to unpack, modify, repack and flash a Firmware for a Pipo M6 max but I have to use the Windows version for unpacking/packing.

The Linux Version did not run under Ubuntu 10.04 LTS x64.

I extracted the zip-file and make the file "imgrepackerrk" executable via chmod a+x imgrepackerrk.

If I try to open it via ./imgrepackerrk I get bash: ./imgrepackerrk: No such file or directory.

Did I miss something or do it wrong?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I think you forgot to change directory. What the result of ls?
[Upgrading, Modifying and Unlocking] hurray:
I am in the correct directory and the program is executable:
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Sorry. I'm not specialist in Linux :(
[Upgrading, Modifying and Unlocking] hurray:
No problem at all. The windows version works like a charm. Thanks again for the tools and your time! :good:
[Upgrading, Modifying and Unlocking] pogs24ever:
Question

Hi RedScorpion..

I like you tool alot... However...

I have an 16mb recovery.img.. But whenever i repack it it goes to 5mb image even without modifying it

can you help me with this? Thanks!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
What kind of help you need?

Please describe your actions in details (step by step) and provide link to original recovery.img
[Upgrading, Modifying and Unlocking] Shmarkus:
is there a possibility to change the contents (e.g keep only recovery image and delete the rest)?

What can we do with image.cfg?

Thanks in advence! Great work
[Upgrading, Modifying and Unlocking] noyouturn:
someone can help me

I have tab by MID. Is not turning on longer, until i flashing him.

Tab is now worked much quickly! But, unfortunately WiFi by rtl8188etv and touch by zet6223wta not worked at all.

I find drivers for this chips:

I tried all possible ways and I can give him the second life by myself! Can any integrated this in firmware for me?

Or find modules (8188xxx) after copy in system all is turning on...

I would be very grateful and if needed will pay for extra fees. Link on firmware and drivers in attached file. Thanks in advance! http://dl.xda-developers.com/attach...deacec70bef1b/52a9ac06/2/4/5/0/1/9/8/link.txt
[Upgrading, Modifying and Unlocking] rosama:
Image repack error

Hi RedScorpio

First off thanks for this tool, it's great! I am however having issues with repacking a boot.img. I have modified some of the files in the ramdisk and would like to rebuild but I get the following output:

2014.01.20 12:06:32 imgRePackerRK (v. 1.02 linux)

2014.01.20 12:06:32 (c) RedScorpio, Moscow, 2013

2014.01.20 12:06:32

2014.01.20 12:06:32 Command parameters: "/log" "/debug" "ramdisk.dump"

2014.01.20 12:06:32

2014.01.20 12:06:32 Run parameters:

2014.01.20 12:06:32 log = 1

2014.01.20 12:06:32 debug = 1

2014.01.20 12:06:32 quiet = 0

2014.01.20 12:06:32 mono = 0

2014.01.20 12:06:32 md5 = 0

2014.01.20 12:06:32 rkcrc = 0

2014.01.20 12:06:32 rkaf = 0

2014.01.20 12:06:32 skip = 0

2014.01.20 12:06:32 2nd = 0

2014.01.20 12:06:32 memsize = 134217728

2014.01.20 12:06:32

2014.01.20 12:06:32 ==========================[ START ]==========================

2014.01.20 12:06:32

2014.01.20 12:06:32 --- Firmware creating ---

2014.01.20 12:06:32

2014.01.20 12:06:32 - "package-file" configuration file reading -

2014.01.20 12:06:32 .FATAL ERROR. Can't open file "ramdisk.dump/package-file"

2014.01.20 12:06:32

2014.01.20 12:06:32 ==========================[ STOP ]==========================

Could you tell me what it's looking for?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
So use imgRePackerRK.exe ramdisk.cfg command

UPDATE No need to packaging parts of the firmware separately.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
imgRePackerRK

RockChip's firmware images (*.img) unpacker/packer

New version (1.03 Windows & Linux) ready

~ symlink's (with absolute paths) checking bug fixed (CPIO);

+ automatic correction of image size errors for some files added;

+ key /blk added;

+ key /cid added.
[Upgrading, Modifying and Unlocking] Raztan:
Thank you for this tool, I used it to do my first firmware mod, very simple repartitioning.

I have a question though what is image.cfg used for? I googled it but could not find any info.. Im guessing this is specific to this tool? do we need to worry about it at all?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Yes, this is specific to this tool. image.cfg is automatically created during the unpacking and used for packing. You can change FW by changing this file (don't do it)
[Upgrading, Modifying and Unlocking] Raztan:
Ok we'll here's a question

say I want to repackage a firmware as only a partial update like say just the kernel.img.

that file would then have info on OTHER parts of the firmware like system, boot, etc, that aren't going to be in the partial update.

Is that going to be a problem?

EDIT:

Here's an example of a full firmware unpack

Now here's one of someone elses Kernal only update unpacked

Seems simple enough to just eliminate entries referencing stuff that's no longer included in the firmware

however obviously something is going on with package-file type.. it changes from 00 to 01.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Raztan,

Unfortunately, I cannot say anything about "partial" firmware. I have not seen such firmware.

As for the type: 01 means that the file size is less than 256 bytes and the format is unknown
[Upgrading, Modifying and Unlocking] Raztan:
Ah ok.

So I can basically Ignore it then.

Ya I know "kernel only" updates work.. using rkbatchtool and using "upgrade" button, not sure if it works for other things.

Im rather new to android, I did try a edited boot.img + kernel flash tonight and seem to softbricked my device.

Not sure what I did wrong.. maybe you can't include boot.img in a partial, maybe I made a mistake, or maybe it was successful but the changes made are the problem.. not sure.

You need to specify the .cfg file.

When you unpack boot.img it will make a file list file with stats like chmod.

This is so when you goto repack it will know how.

So EX: imgrepackerrk boot.img.cfg

If you add any files/directories or rename anything you'll need to edit that file it's self explanatory but not quite sure what "StartIno" value does or is..
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Have you similar vendor's "partial" image?
[Upgrading, Modifying and Unlocking] Raztan:
Oh, I got it back up and running, I made a new package with the stock boot, I was editing the mali driver initialization to OC the GPU.. I don't think my unit could handle it but anyway ya, partial firmware with boot.img works.. at least on RK3188, It's a JXD 7800.

Partials from vender, no.. But from someone else who put out a modified firmware as well as OC patched kernels.

It's just firmware packed with less then a full set and use "upgrade" with rkbatch tool.

Anyway tool works great pretty sure that wasn't the problem.

Had an experienced Rom developer look at it and told me the structure of the firmware was fine.

http://www.multiupload.nl/2PFPHGWX5I

if you want to take a peak.

I Just messed up on my edit .. or the unit couldn't handle the change not sure which.
[Upgrading, Modifying and Unlocking] DrCarmack:
a big thank you, might just use this to save my tablet from a hard brick
[Upgrading, Modifying and Unlocking] DrCarmack:
its the 21st century, we have things like google translate
[Upgrading, Modifying and Unlocking] dieselnutjob:
Hi RedScorpioXDA

If I want to unpack a file which is an image of the an entire eMMC module is this possible?

Examples are here https://wiki.pine64.org/wiki/Quartz64#Android_11_Production_Test_Build_for_Quart64_model_A_SBC

My understanding is that the first 0x8000 sectors (so 16777216 bytes ?) is the Rockchip loader, uboot.img and trust.img and then the actual Android boot starts after that.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Men can unpack everything that is packed by another person. But this utility is for unpacking firmware files of a certain formats.

If this is a copy of eMMC, then you just need to "slice" the partitions. The utility is not designed for this
[Upgrading, Modifying and Unlocking] chinhhut:
@RedScorpioXDA thank you for great tool.

By the way, I've tried to unpack X96 x6 RK3566 under windows 10 and got the following error. Could you give me the suggestion?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Try /cid option