FORUMS

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

343 posts
Thanks Meter: 237
 
By RedScorpioXDA, Senior Member on 5th July 2012, 08:21 PM
Post Reply Email Thread
30th July 2013, 09:54 AM |#81  
OP Senior Member
Thanks Meter: 237
 
Donate to Me
More
Quote:
Originally Posted by pogodancer

When unpacking with imgRePacker, do I have to choose an option ? I did not use an option last time.

It does not matter

PS. You can set all options in the configuration file
The Following User Says Thank You to RedScorpioXDA For This Useful Post: [ View ] Gift RedScorpioXDA Ad-Free
30th July 2013, 11:03 AM |#82  
pogodancer's Avatar
Senior Member
Thanks Meter: 152
 
More
Thanks RedScorpioXDA.

I made another try:

1. Extract the A10HD-firmware.img with imgRePacker in Win7-32bit
2. Copy the sparse system.fex into the VirtualBox with Ubuntu 12.04-32bit.
3. Change sparse system.fex into ext4 system.img with simg2img in Ubuntu.
4. Mount ext4 system.img in Ubuntu and delete only 1 apk (4K-player) for test purposes.
5. Change back the ext4 system.img into sparse system.fex with make_ext4fs in Ubuntu.
6. Copy the new system.fex into the firmware-dump-folder in Win7.
7. Create a new firmware.img with imgRePacker with /noiso option.
8. Flash the firmware with PhoenixSuit.

=> System cannot boot. It hangs on the Teclast-bootscreen (not bootanimation).

So it seems that the error occurs in step 5. Maybe the make_ext4fs-tool from the ext4_utils do not work correctly in my virtual 32bit-Linux-machine.

Did anybody successfully change a sparse firmware image for an A31 tablet ? If so, how did you do it ? Did I do something wrong ?
31st July 2013, 11:34 AM |#83  
OP Senior Member
Thanks Meter: 237
 
Donate to Me
More
pogodancer,

I think you need ask simg2img/img2simg autors

PS Try to make whole procedure without step 4
1st August 2013, 03:21 PM |#84  
pogodancer's Avatar
Senior Member
Thanks Meter: 152
 
More
Quote:
Originally Posted by RedScorpioXDA

I think you need ask simg2img/img2simg autors

I posted my problem in the Samsung ext4_utils-thread here also. But no answer at the moment. Thanks.



Quote:
Originally Posted by RedScorpioXDA

PS Try to make whole procedure without step 4

I tried that, but no success. I think the problem is that I have a windows-32bit-system which causes problems with the ext4_utils in my virtual linux-32bit-system. As I spent a few days now for trying around, I will give up.
3rd August 2013, 09:14 PM |#85  
tragidy's Avatar
Junior Member
Thanks Meter: 0
 
Donate to Me
More
Battery Low
Quote:
Originally Posted by RedScorpioXDA

imgRePacker
LiveSuit's & PhoenixSuit's firmware images (*.img) unpacker/packer


Linux

Supported firmware images (known):
- Allwinner A31 (PhoenixSuit).

In Linux,

With Momo19 Momo19HD Allwinner A31 .img dump does not pass imgrepacker properly to handle new SDK 2 and SDK 3

Output;
Code:
[email protected] ~/tools $ ./imgrepacker momo19hd.img

	imgRePacker (version 2.04 linux)
	LiveSuit's & PhoenixSuit's firmware image unpacker/packer

	(c) RedScorpio, Moscow, 2012-2013
	    [email protected]

	==========================[ START ]==========================
	
	--- Firmware unpacking ---
	Modified old method
	PhoenixSuit image format detected
	Img file seems corrupted (try to use /skip option)
	
	==========================[ STOP  ]==========================
download.ployer dot cn for images.

Problem is with /skip the system and other fex are not correctly extracted, will you fix this in 2.05 ?
5th August 2013, 04:30 PM |#86  
OP Senior Member
Thanks Meter: 237
 
Donate to Me
More
Quote:
Originally Posted by tragidy

Problem is with /skip the system and other fex are not correctly extracted, will you fix this in 2.05 ?

What do you mean?
I have downloaded "MOMO19HD 4.2.2 V1.img". All extracted correctly:
Code:
boot.fex	Android boot image
bootloader.fex	FAT16 image
diskfs.fex	512b of zeros
env.fex		text file
recovery.fex	Android boot image
system.fex	sparse image
7th August 2013, 10:19 PM |#87  
Junior Member
Thanks Meter: 0
 
More
same problem
Quote:
Originally Posted by tragidy

In Linux,

With Momo19 Momo19HD Allwinner A31 .img dump does not pass imgrepacker properly to handle new SDK 2 and SDK 3

Output;

Code:
[email protected] ~/tools $ ./imgrepacker momo19hd.img

	imgRePacker (version 2.04 linux)
	LiveSuit's & PhoenixSuit's firmware image unpacker/packer

	(c) RedScorpio, Moscow, 2012-2013
	    [email protected]

	==========================[ START ]==========================
	
	--- Firmware unpacking ---
	Modified old method
	PhoenixSuit image format detected
	Img file seems corrupted (try to use /skip option)
	
	==========================[ STOP  ]==========================
download.ployer dot cn for images.

Problem is with /skip the system and other fex are not correctly extracted, will you fix this in 2.05 ?

hello
I have the same problem with this firmware S1A-20130522.1.0.8-S738-dou0308.img is a Chinese tablet,
productor SHENZHEN LYRIC PIONEER CO., LTD-LYXF TABLE PC
of the tablet in question, the version that I have and 1024 * 600
how can I fix? I have to eliminate the gapps and create a microsd to install it on 20 tablets.
please help
8th August 2013, 12:24 AM |#88  
Junior Member
Thanks Meter: 0
 
More
1 step ok
hello
ok I managed to extract the file.img, now how do I delete google apps, the extracted firmware?
thanks
8th August 2013, 11:11 AM |#89  
OP Senior Member
Thanks Meter: 237
 
Donate to Me
More
Quote:
Originally Posted by madfox76

now how do I delete google apps, the extracted firmware?

I don't know structure of all firmware images. Usually need to modify system.img/system.fex[.iso] (for A31s SoC)
8th August 2013, 01:34 PM |#90  
Junior Member
Thanks Meter: 0
 
More
tablet lyric ly-S1A
Quote:
Originally Posted by RedScorpioXDA

I don't know structure of all firmware images. Usually need to modify system.img/system.fex[.iso] (for A31s SoC)

HI sorry
my tablet is a LY-S1A of SHENZHEN LYRIC PIONEER CO., LTD-LYXF TABLE PC
A20 is there a way to eliminate the firmware from the Google app?
I installed Ubuntu 4.13, I managed to extract the firmware.img PhoenixSuit now I can not edit the file system.fex.iso.
please help
8th August 2013, 02:09 PM |#91  
OP Senior Member
Thanks Meter: 237
 
Donate to Me
More
Quote:
Originally Posted by madfox76

A20 is there a way to eliminate the firmware from the Google app?
I installed Ubuntu 4.13, I managed to extract the firmware.img PhoenixSuit now I can not edit the file system.fex.iso

What the format of system.fex.iso? It can be sparse image or something else. In this case need to additional processing
Post Reply Subscribe to Thread

Tags
allwinner, imgrepacker, livesuit, phoenixsuit

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes