[TOOL] imgRePacker (LiveSuit's & PhoenixSuit's firmware images unpacker/packer)

Search This thread

RedScorpioXDA

Senior Member
Apr 6, 2012
364
247
imgRePacker
LiveSuit's & PhoenixSuit's (Allwinner) firmware images (*.img) unpacker/packer


Version 2.06 Windows & Linux

Supported firmware images (known):
- Sochip SC8600/SC9800 (LiveSuit/zdisk);
- Boxchip F10/F15/F16/F20 (LiveSuit/zdisk);
- Teclast T7200/T8100 (LiveSuit/zdisk);
- Allwinner F10/F13/F18 (LiveSuit/zdisk);
- Allwinner F1C100/F1E200 (LiveSuit);
- Allwinner A10/A13/A10s (LiveSuit);
- Allwinner A20/A31/A31s (PhoenixSuit);
- Allwinner A80 (PhoenixSuit).

Supported second layer file formats:
- Android boot image;
- gzip/cpio archive file;
- cpio_ascii_new archive file;
- sparse image (unpacking).

Old versions:
 

Attachments

  • imgRePacker_206.zip
    192.4 KB · Views: 22,228
Last edited:

cis.snakeman

Senior Member
Jul 29, 2008
103
8
Hi RedScorpio :)

Unfortunately with this version I can't obtain a proper ext4 iso file.
With an extract of ICS img rom (G18N from yinlips) (mirror here: http://dl.dropbox.com/u/67207175/ROMS/YDPG18.rar)
just a "data" type:

Code:
system.fex.iso: data
instead of:
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)
Do you have idea of what happened ?
 
Last edited:
  • Like
Reactions: ivancorpiz

RedScorpioXDA

Senior Member
Apr 6, 2012
364
247
Code:
system.fex.iso: data
instead of:
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)

These two strings are not the result of the work of any version of the program. Please describe the problem more precisely.
 
Last edited:

cis.snakeman

Senior Member
Jul 29, 2008
103
8
These two strings are not the result of the work of any version of the program. Please describe the problem more precisely.

Sorry for late answer, it was the "file" command on the iso files generated by imgRepacker. (especially system one)
In fact the iso files are not ext4 filesystem, in fact there is no filesystem defined :/

I'll try with the latest version this afternoon.
 

RedScorpioXDA

Senior Member
Apr 6, 2012
364
247
Sorry for late answer, it was the "file" command on the iso files generated by imgRepacker. (especially system one)
In fact the iso files are not ext4 filesystem, in fact there is no filesystem defined .

Actually, the program does not modify files in the firmware (saves them as-is). So inform me, in which case you got
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)
 

cis.snakeman

Senior Member
Jul 29, 2008
103
8
Actually, the program does not modify files in the firmware (saves them as-is). So inform me, in which case you got
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)

I have it with an iso extracted from an older version of the img I used. (one of Android 2.3)

The one wich causing these issue is an Android 4.0 one

This is the files from "YDPG18 Upgrade" android game handled console
http://www.yinlips.com/en/services/downs.aspx
 
  • Like
Reactions: ZenithLM

booroondook

Member
Nov 3, 2009
49
4
Moscow
www.booroondook.ru
ImgRepacker builds incorrect image

Help me please.
I use ImgRepacker 2.1 with Allwinner A10 ROM for chinese "noname" tablet with Android 4.0.3 ICS.
ImgRepacker unpacks ROM correctly but then repack ROM incorrectly.
I made an experiment.
I unpacked ROM and then repacked it without any changes.
Tablet doesn't boot with the re-assembled ROM.
I compared the old and the new ROMs. Both files are the same size but they contain 81 differences. These differences are:
1) One big block from offset 0050 to 03FF (944 bytes)
2) 40 blocks of 48 bytes. The 1st of these blocks begins at offset 0430 and the others repeated every 1024 bytes.
3) 40 blocks of 720 bytes. The 1st of these blocks begins at offset 0530 and the others repeated every 1024 bytes.
 

RedScorpioXDA

Senior Member
Apr 6, 2012
364
247
The IMG file for the ProTabXXLV2 here gives a corruption error when trying to unpack with imgRePacker. I know the file works in LiveSuit as I have flashed it a number of times.
This is the result of improper packaging firmware. In the next versions of the program will be key to disable the checking size of the firmware. The new version is being tested and will be published in the near future.
 

RedScorpioXDA

Senior Member
Apr 6, 2012
364
247
I compared the old and the new ROMs. Both files are the same size but they contain 81 differences. These differences are:
1) One big block from offset 0050 to 03FF (944 bytes)
2) 40 blocks of 48 bytes. The 1st of these blocks begins at offset 0430 and the others repeated every 1024 bytes.
3) 40 blocks of 720 bytes. The 1st of these blocks begins at offset 0530 and the others repeated every 1024 bytes.
These blocks belong to the titles of files and is unlikely to affect the flashing crash. If the new firmware can unpack, look for the problem in a different place.
 
Last edited:

RedScorpioXDA

Senior Member
Apr 6, 2012
364
247
I use ImgRepacker 2.1 with Allwinner A10 ROM for chinese "noname" tablet with Android 4.0.3 ICS.
ImgRepacker unpacks ROM correctly but then repack ROM incorrectly.
I made an experiment.
I unpacked ROM and then repacked it without any changes.
Tablet doesn't boot with the re-assembled ROM.

Please provide links to both firmware images
 

Top Liked Posts

  • There are no posts matching your filters.
  • 49
    imgRePacker
    LiveSuit's & PhoenixSuit's (Allwinner) firmware images (*.img) unpacker/packer


    Version 2.06 Windows & Linux

    Supported firmware images (known):
    - Sochip SC8600/SC9800 (LiveSuit/zdisk);
    - Boxchip F10/F15/F16/F20 (LiveSuit/zdisk);
    - Teclast T7200/T8100 (LiveSuit/zdisk);
    - Allwinner F10/F13/F18 (LiveSuit/zdisk);
    - Allwinner F1C100/F1E200 (LiveSuit);
    - Allwinner A10/A13/A10s (LiveSuit);
    - Allwinner A20/A31/A31s (PhoenixSuit);
    - Allwinner A80 (PhoenixSuit).

    Supported second layer file formats:
    - Android boot image;
    - gzip/cpio archive file;
    - cpio_ascii_new archive file;
    - sparse image (unpacking).

    Old versions:
    4
    Victory Day celebrations
    imgRePacker
    LiveSuit's & PhoenixSuit's firmware image (*.img) unpacker/packer

    New version (2.06 Windows & Linux) ready

    + added /symb key;
    + added /rmd4 key;
    + added OS detection;
    ~ optimized some parts of code;
    ~ WinAPI using to create directory (Windows);
    3
    I spent the last couple of weeks trying to amend one little parameter and finally worked out exactly this u-boot.fex changes need a new CRC.

    Is there any tool or guide available that will allow me to recalculate the checksum? Or can a kind soul make the amendment for me if the method is private?

    Any help appreciated.

    Please share results of your research

    OK, I think its time to share my tool which updates config.fex and uboot.fex CRC.

    https://github.com/lolet/update_uboot_crc

    I put executable into repo because ASM function won't compile without changes under gcc

    Usage is
    Code:
    update_uboot_crc uboot.fex  - recalculates CRC
    update_uboot_crc uboot.fex config.fex - writes config.fex into uboot.fex and recalcs CRC
    3
    imgRePacker
    LiveSuit's & PhoenixSuit's firmware image (*.img) unpacker/packer

    New version (2.03 Windows & Linux) ready

    PS. Not fully tested
    3
    imgRePacker
    LiveSuit's firmware image (*.img) unpacker/packer


    New version (2.02 Windows & Linux) ready