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

I had to work with a RK292X chip tablet image, and the opensource tool here (https://github.com/rk3066/rk-tools.git) is not aware with this chip category, like your tool here. So I would like to share with you my finding about this chip.

With ChipId=0x00000051 and rom_header.code=0x01060000 this new chip category is fine with RKBatchTool v1.8.

If you need an image to try, just ask me.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Do you have unpacking/packing problems? If yes send me link
[Upgrading, Modifying and Unlocking] fefifofum:
Is the source code of this tool public? Sorry to ask, but I cannot find it.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
No
[Upgrading, Modifying and Unlocking] silverize1208:
I need help in changin Boot logo for rockchip devices

Good day,

I kind of new in Rockchip devices.. and since im interested mo modifying roms i would like to create my own boot logo. however the available boot log changer ive used so far is only for mediatek devices.. i hope you could share you ideas and expertise of how to do it on rockchip devices..

preferably on PIPO Tablets..

Im currently using PIPO M9Pro 10.1 inch tablet.

current resolution is 1920x1200

any response would be greatly appreciated
[Upgrading, Modifying and Unlocking] ts_firehawk:
Can you please help me? This is the ChipID imgRePackerRK detected. Any guides from there?

Thanks!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please use /cid key
[Upgrading, Modifying and Unlocking] goodoane:
Hi RedScorpio,

Thank you for your wonderful tool.

I used your tool to unpack the backup.img as a curiosity becouse my MINIX NEO-X7 use this partition too. It seems that is contain boot.img, misc.img, recovery.img, loader.bin, parameter. In hexedit the backup.img start with RKAF if I try to pack back first I get an error like it doesn't find the parameter file in /backup.img.dump/image.dump/ then if I put insisde the parameter file it build an image but is like an update.img because in hex I see RKFW. Can you add an option to unpack/repack the backup.img to your wonderful tool?..

Thank you!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please use /rkaf option
[Upgrading, Modifying and Unlocking] goodoane:
I did use rkaf and I get ended with rkfw packed backup.img

But first I get an error about not find parameters file.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Sorry, I don't understand the problem

Please provide link to this firmware
[Upgrading, Modifying and Unlocking] goodoane:
I get it working after I changed the name of parameter file that was in a long form like that parameter_3188_box_x7_r3_4g I changed the name in parameter and copy to backup.img.dump folder because originally was outside folder that's why I get that error

.As you can see the relative path in backup.img is different.

Firmware is from minix.com.hk site:http://www.minix.com.hk/Support/14010120335056.html released for neo-x7 in January. I used that firmware as an example to create a kitkat version from scratch.

Here is what happened when parameter file has a long name:

It seems that even if it read correct the package-file configuration correctly when try to load parameter is looking for a hard coded parameter not for what is described in package-file.

I don't know if I explained well. Can this be fixed?..

In attachment is the backup.img to avoid download a full firmware.

Thank you.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I see. It happened because a nonstandard name of parameter file. I'll check
[Upgrading, Modifying and Unlocking] Astralix:
Hi!

Looks like a nice tool, but isn't it possible to generate an update.img from scratch with this tool?

So after building kernel and android you normally have

out/kernl.img

out/recovery.img

out/boot.img

out/misc.img

out/system.img and finally

out/parameter (The file containing chip/version markers and FLASH layout as kernel command line.)

Add a bootloader to it and you have everything you need to build an update.img. What do you need to add a switch that you can use imgrepackerrk out/ update.img to pack all created images into a single update file with your tool without having something "unpacked" before?

Regards

Astralix
[Upgrading, Modifying and Unlocking] Ollek74:
Repacking Problem / Bug report

Hi RedScorpio (and everybody else),

first of all, thanks for writing this tool :o

I prefer command line tools over GUI stuff when editing ROMs.

However, I had a problem repacking a ROM under Ubuntu Linux 12.04 /64Bit, which works flawlessly under Windows 7/64Bit - using imgRePackerRK version 1.04 in both cases.

Initially, I tried the whole process in Linux; I unpacked the ROM with the "/cid" "/log" parameters, edited the system.img, then tried to repack using the command: #./imgrepackerrk FX2_PAD10_RK3168_RevD_140115.img.dump/

The result was the following error message:

imgRePackerRK (version 1.04 linux)

Rockchip firmware batch image unpacker/packer

(c) RedScorpio, Moscow, 2013-2014

RedScorpio@land.ru

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

--- Firmware unpacking ---

2-nd layer file unpacking

unknown format detected

Unknown format

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

In order to test whether I misunderstood the imgRePackerRK help text and how the tool works, I repeated the same process on Windows:

I unpacked the firmware .img file with the same command, then copied the edited system.img fom my Linux partition into the .dump directory generated by imgRePackerRK, and tried to repack as before. All went smooth, the resulting firmware image was flashable and is working.

Is this a bug or am I doing something wrong ?

Thanks,

best regards,

PADMAN
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I think you need try use #./imgrepackerrk FX2_PAD10_RK3168_RevD_140115.img.dump command (without "/")
[Upgrading, Modifying and Unlocking] ruelox6680:
thank you for the tool, and thanks for english translation :good:
[Upgrading, Modifying and Unlocking] majdi.ahmad:
hi

i don't know if i got it but i have qus..

can i create an image file for android tab lets say for example xtuch v.1.2 and then burn the image with phonenix card to SDcard and flash another xtuch tab v1.2 ?

if thats work its gonna be great ...

plz replay ASAP

BR
[Upgrading, Modifying and Unlocking] AnthonyJohan94:
Hello all

I'm a newbie on this thing and i need a little help

My device based on rk3168 and when i try to unpack the firmware it says my chipID is unsupported

I want to try the /cid key but i don't know what will the command lines be. I'm very blind on this command prompt things

So can anyone show me how it works?
[Upgrading, Modifying and Unlocking] t499user:
On Ubuntu you just have to install lsb, it's so much nicer than having to switch over to windows to run imgrepackerrk.

sudo apt-get install lsb

Best Regards!
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
imgrepackerrk /cid fw_name

or use ini-file
[Upgrading, Modifying and Unlocking] wertzPH:
my device (rk30sdk) contains backup.img partition. i dumped it using AndroidTool2.1. when extracting backup.img using your software, it gives me boot, kernel,misc,recovery,loader,parameter and other cfg but there is no system included. i am able to separately dump system.img using android tool but how can i repack them together to have a complete firmware? thanks.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
1. You can use rkDumper to make full backup of device

2. Backup from p.1 hasn't loader (you can obtain from backup img)

3. You need add some files (like package-file, recover-script. update-script)

4. You need make image.cfg file

After that you can pack firmware to RKFW/RKAF format
[Upgrading, Modifying and Unlocking] wertzPH:
sadly, my device (updated on rkdumper page) is one of those that has no official technical support so no access to official firmware. i am missing recover-script and update-scripts. in image.cfg, system has # in it so meaning line is ignored.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I think you can use recover-script and update-scripts from another similar device
[Upgrading, Modifying and Unlocking] Astralix:
Hi!

Great work!

I do have a little issue with this tool... I want to create linux images with it and these only have Loader, parameter and boot.img, wile other images are skipped and the rest of the memory is used as rootf. But this rootfs must not be in the same memory as the boot.img and therefore not be part of the image. But however there could be a partition called (rootfs) instead of everything else behind (boot).

Unfortunately the readme is mostly russian? and there is no link to any github repo to provide patches or improvements to the code.

Astralix
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
1. Yes, readme is russian (I am russian). You will not find anything new: it is brief history and repetition of information from /help

2. I'm not ready to open the sources
[Upgrading, Modifying and Unlocking] Astralix:
If you're not ready to open sources, I kindly ask for some support:

I unpacked a Rockchip Linux image consisting of

Loader, boot and linuxroot partitions.

- Loader is a usual RK3188Loader(L)_v2.08.img

- boot is a normal rkboot-image, kernel.img and attached initramfs.

- linuxrootfs is an ext4 debian rootfs

Your tool unpacks this image without any failure message: fine!

imgrepackerrk radxa_rock_ubuntu_14.04_desktop_fhd_140823_update.img

imgRePackerRK (version 1.04 linux)
Rockchip firmware batch image unpacker/packer

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

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

--- Firmware unpacking ---

"RKFW" image file detected

Image properties:
Type	RockChip batch image (RKFW)
Version	1.0.0
Date	2014.08.23
Time	17:08:40
ChipID	0x00000070
Code(?)	0x01050000

-- boot.img processing --

-- update.img processing --
Image properties:
Type	RockChip update image (RKAF)
Id	"007"
Model	"radxa_rock"
Manufacturer	"RADXA"
Version	4.2.2

- Files extracting -
Image files count = 9

# (NAME	Relative path)	skipped
package-file (package-file)	extracted (format: unknown)
bootloader (RK3188Loader(L)_V2.08.bin)	extracted (format: RockChip bootloader image)
parameter (parameter)	extracted (format: RockChip PARM signed file)
boot (Linux/boot-linux.img)	extracted (format: Android boot image)
linuxroot (Linux/rootfs.img)	extracted (format: ext4 image)
backup (RESERVED)	skipped
update-script (update-script)	extracted (format: unknown)
recover-script (recover-script)	extracted (format: unknown)

- rkCRC summ of update.img checking -
Stored rkCRC	= 0xe5b92f2b
Calculated rkCRC	= 0xe5b92f2b

- md5 summ checking -
MD5 summ (radxa_rock_ubuntu_14.04_desktop_fhd_140823_update.img.dump/image.md5)	saved
Stored MD5	= "bf258473b2ff46df2616ec0e15853bf0"
Calculated MD5	= "bf258473b2ff46df2616ec0e15853bf0"

- image.cfg creating -
image.cfg created

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

Now I just repack the image:

imgrepackerrk radxa_rock_ubuntu_14.04_desktop_fhd_140823_update.img.dump

imgRePackerRK (version 1.04 linux)
Rockchip firmware batch image unpacker/packer

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

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

--- Firmware creating ---

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

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

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

- Files checking -
# (NAME)	Can't find file "radxa_rock_ubuntu_14.04_desktop_fhd_140823_update.img.dump/NAME"

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

If I do the same thing with a full Android image, it works...

As I know that this linux thing is a new field of action for these image tools and several other mkimg or rkimg or mkboot ... fail too, I asked for some repository acces to offer my help for improvment.

However, would be great if you could take a look and tell me what details you need to get this going.

Astralix
[Upgrading, Modifying and Unlocking] Astralix:
Sorry, yes that would have been helpfull:

here are some images, the third one is the one I tested:

http://dl.radxa.com/rock/images/ubuntu/nand/

What might be helpful for others too is the intention why I am trying your tool.

I wanted to cut out the kernel from boot.img and put in a separate kernel.img. So I removed kernel from boot.img by using your /2nd extention. And yes, I edited the init file and parameter and so on.

This gave the same (NAME) Error as shown above.

So I tried to just exchange the kernel in the boot.img and it failed with the (NAME) error above too.

So I just unpacked the image. modified nothing and repacked the image, as you can see (I copied the command lines too) and it ends with the same (NAME) error.

If I can help you, you find me in IRC freenode #linux-rockchip or #radxa

Astralix
[Upgrading, Modifying and Unlocking] Astralix:
Red,

I have another little complaint that might be the root cause of the problems...

If I see this list

Used codes designating types of files:
-1 - Is not defined;
00 - Unknown;
04 - Android boot image;
06 - ext3 image;
11 - RockChip KRNL signed file;
12 - RockChip PARM signed file;
14 - gzip / cpio archive file;
15 - RockChip bootloader image;
16 - ext4 image;
17 - cpio_bin_odc archive file;
18 - cpio_ascii_odc archive file;
19 - cpio_ascii_new archive file;
20 - cpio_ascii_crc archive file.

I am not sure if you can work with non-kernel boot and recovery images. Rockchip supports kernel in boot and kernel in recovery, in that case the image Type is 11 and the images are signed with KRNL.

But you may have a kernel in (kernel) partiton and no kernel in boot or recovery or both. In that case these partitons carry the header ANDROID!

I packed a simple multi-image system that I know working if I flash it as separate files. I used your tool, build ini and cfg according other images I had testwise unpacked with your tool.

The multi-image has an extra kernel.img and no kernel in boot or recovery. I used a working parameter.

I flashed the created upgrade.img and got CRC error for boot and header error (0x00000000) for recovery.

Then I simply unpacked the single image into an empty directory and found image.cfg listing boot and recovery as of type 11.

I modified image.cfg to use type 04 for these two parts and packed it again.

start_linux=====66051
E:CRC failed!
Load failed!
Begin recover...
GetRemapTbl flag = 1
E:Invaid tag(0x00000000) in backup!

I give it an extra try with tape 11 for these images, but that

returns the same errors. I see that the error is about backup. However the system doesn't boot anything as I have access to serial port and should see at least one kernel coming up...

Just guessing around...

Astralix
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Astralix

After unpacking delete UTF-8 BOM (EF BB BF) from beginning of package-file. This will solve packing problem
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Types description from image.cfg used for detection of needing PARM/KRNL signing only (11/12). In other cases type will be detected from <file_name>.cfg
[Upgrading, Modifying and Unlocking] Astralix:
Wow, that was an ugly thing! Linux' gedit did not show a single UTF sequence. Deleting and writing the 1st line in the file solved that problem. Thanks!

I am currently investigating the problem that I can flash, whatever I want to the tablet, I just stays in the Loader telling "SHA Error" as the problem. This is even happening if I flash images that have worked before. So the above larger post about the CRC Error can be ignored for now.

Thanks anyway

Astralix
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
1. I think this question to RockChip Create Upgrade Disk Tool v1.43 developers

2. I don't understand the sense of this action
[Upgrading, Modifying and Unlocking] ReDetection:
It seems, RK2818 is supported

$ ./imgrepackerrk /cid Update.img

imgRePackerRK (version 1.04 linux)
Rockchip firmware batch image unpacker/packer

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

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

--- Firmware unpacking ---

"RKFW" image file detected

Image properties:
Type	RockChip batch image (RKFW)
Version	0.2.3
Date	2015.02.17
Time	01:07:46
ChipID	0x00000021
Code(?)	0x01050000

-- boot.img processing --

-- update.img processing --
Image properties:
Type	RockChip update image (RKAF)
Id	"007"
Model	"rk2818sdk"
Manufacturer	"RK2818SDK"
Version	0.2.3

- Files extracting -
Image files count = 12

HWDEF (HWDEF)	extracted (format: unknown)
package-file (package-file)	extracted (format: unknown)
bootloader (RK28xxLoader(L).bin)	extracted (format: RockChip bootloader image)
parameter (parameter)	extracted (format: RockChip PARM signed file)
misc (misc.img)	extracted (format: unknown)
kernel (kernel.img)	extracted (format: RockChip KRNL signed file)
boot (boot.img)	extracted (format: RockChip KRNL signed file)
recovery (recovery.img)	extracted (format: RockChip KRNL signed file)
system (system.img)	extracted (format: ext3 image)
backup (RESERVED)	skipped
update-script (update-script)	extracted (format: unknown)
recover-script (recover-script)	extracted (format: unknown)

- rkCRC summ of update.img checking -
Stored rkCRC	= 0x073d059c
Calculated rkCRC	= 0x073d059c

- md5 summ checking -
MD5 summ (Update.img.dump/image.md5)	saved
Stored MD5	= "be0fee6fd87f18da29b491db0a8022c2"
Calculated MD5	= "be0fee6fd87f18da29b491db0a8022c2"

- image.cfg creating -
image.cfg created

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

I did not tested repack yet.

p.s.

device is gmini magic book T6LHD

sad about closed source

hello from Novosibirsk :)
[Upgrading, Modifying and Unlocking] starbuck79:
I´m try to use the tool but don't start in Windows 8!
[Upgrading, Modifying and Unlocking] Tatae33:
redme

realy man???

your read me file.txt i a fuking joke
[Upgrading, Modifying and Unlocking] julio00004:
about a problem with imgRePackerRK

I have a problem with your program,when i try to pack the file .img the program show the follow error:

can´t open file "boot.img.dump\ramdisk.dump\package-file

I believe that is for ext4 file or the file format is other but I not sure

If You known as edit the boot.img,recovery.img and system.img without unpacking send me a mail

Or if you known as edit those files unpacking and packing, please tell me the programs needed.

thanks :D
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
As I understood you have try to pack back boot.img. This is second layer file, so you need use command imgRePackerRK boot.img.cfg

I don't know

imgRePackerRK for unpacking/packing. The rest depends on what you are going to edit
[Upgrading, Modifying and Unlocking] defy_owner:
Does rockchip support sparse images like mtk and allwinner? If not, is there any way to compress image of partition?
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I have never seen such support in the stock firmware
[Upgrading, Modifying and Unlocking] tommo1982:
When unpacking and repacking kernel.img the file got smaller. From 8.6MB to 7.9MB. Is it a bug or something?

I'm also curious. Is it safe to change the kernel to a more recent version? I'd like to replace the stock 3.0.38+ with more recent one from google repository.

PS.

I extracted the *.img files directly from my UNU tablet using "dd". I assume it's possible to write them the same way?
[Upgrading, Modifying and Unlocking] OverBim:
Unsupported ChipID 0x51

Hi. Thanks for the tool. I tried using v104 on the newest image(*1) from here(*2), but got an error message about the ChipID not being supported...

*1 pan.baidu.com/s/1qWIBk6o

*2 cloudnetgo.com/CR-M200S.htm
[Upgrading, Modifying and Unlocking] Pandoriaantje:
Just wanted to stop by and say thanks to RedScorpio for his wonderfull tool.

Also wanted to comment on this old post from szomi:

oversized dumps can easely be truncated. Find the size of the filesystem, and truncate the file. No need to reinvent the wheel, when linux has all the tools needed.

// find the ext3/4 FS size:
$ dumpe2fs -h system.img |& awk -F: '/Block count/{count=$2} /Block size/{size=$2} END{print count*size}'
// truncate system.img with xxx bytes from previous command
$ truncate -s xxx system.img

all done

to grow a system.img to xxx MB (to add apps, etc...):

$ e2fsck -f system.img
$ truncate -s xxxM system.img
$ resize2fs system.img

replace xxx with size in MB (e.g. 595M)

Then you can just mount system.img and go play:

# mkdir system
# mount -t ext3 system.img system
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please use /cid option
[Upgrading, Modifying and Unlocking] raininja:
I am attempting to build a custom ROM for me Asus Zenfone 5 a501cg and I am having issues unpacking the boot images correctly due to Asus' use of a unconventional method of packing them. There is code here that partially solves the issue, there seems to be padding. . . I am asking if you would recommend a method of examination of the Asus boot image to complete this code.

I have attached a boot.img if you are willing to assist.

https://drive.google.com/file/d/0B8fOXGc5Fa8Sa1ljNHNsMDlreFk/view?usp=sharing
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I've seen studies treatment of this format ("$OS$" signature) in Russian forum 4PDA. As far as I know, there no a positive result
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
imgRePackerRK

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

New version (1.05 Windows & Linux) ready

~ using WinAPI to create directories;

+ Rockchip resources image format support added;

+ RK32xxt (ChipID = 0x00000080) suppor added;

+ /symb key added;

+ /bcpath key added;

+ /lname key added;

+ creating configuration files for RKAndroidTool v. 1. xx/xx 2;

+ checking the "intersections" sections and "holes" between them;

+ comparison of the length of the files with the size of the partition.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Please send me link to this FW. I'll check
[Upgrading, Modifying and Unlocking] in_process:
I recently flashed tablet RK3066 with different tablet;s firmware but same mainboard S8_Main_V11-20130104...

everything works like charm but it displays 7"inchs not 8" (mine 8" inchs).

how can use imgRePackerRK to modify the firmware so that's displays 8inchs.. or it's display driver issue? kernel?

any solution please will be very appreciated.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
At first, I will don't discuss old (1.04) version (i think it hasn't sense)

As for 1.05 - caught unexplored case (it new for me)

-@0x00114000(linux)

We have undefined size of partition "linux" (tool set size 0xFFFFFFFE, but it need 0x00000000). I'll make corrections in new version
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
The screen size doesn't matter (only screen resolution).

The purpose of the utility - packing and unpacking and nothing more
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I think so. Please send me link

PS , Linux images are very interesting
[Upgrading, Modifying and Unlocking] debugasm:
This is a link :

hxxps://mmm.olimex.com/wiki/images/5/5f/RK3188_debian_3.0.36_NAND_release1.img.torrent

(replace "xx" with "tt" and "mmm" with "www")
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
I don't know what to do with such files. Comment line in package-file must begin with a "#". Here file (1st line) begins of 0xef 0xbb 0bf (BOM).

May be I'll make opportunity to check of the BOM in future versions

PS. To pack this FW delete first 3 bytes from package-file

PPS. Incorrect file name we can see in FW file table (0x2fbac)
[Upgrading, Modifying and Unlocking] debugasm:
Good idea.

Thanks very much.
[Upgrading, Modifying and Unlocking] RedScorpioXDA:
Doesn't works. Additionally need to add empty files recover-script and update-script or add comment tag (#) for this strings in package-file
[Upgrading, Modifying and Unlocking] luchador:
thank you
[Upgrading, Modifying and Unlocking] lvt213:
Dear all,

In case we unpack the firmware, how can we change the splash boot logo ?

How about Minix

Thanks