As the title suggests, is it possible to unpack and recompile the System.img.ext4.lz4 found within the stock system image? I'd like to poke around with stuff and see what happens. I know it probably won't accomplish anything but let a boy dream I can't fine any guides out there that work for this but hopefully a dev will bless me with his magic.
If you go to android software and hacking forum here on xda you might see what you're looking for. It's a devs section.
Nathamio said:
As the title suggests, is it possible to unpack and recompile the System.img.ext4.lz4 found within the stock system image? I'd like to poke around with stuff and see what happens. I know it probably won't accomplish anything but let a boy dream I can't fine any guides out there that work for this but hopefully a dev will bless me with his magic.
Click to expand...
Click to collapse
Use 7zip lz4 to extract img then mount img in Linux and then you can access raw system. I can extract and upload it for you if you want to give me the file name for the firmware.
VICosPhi said:
Use 7zip lz4 to extract img then mount img in Linux and then you can access raw system. I can extract and upload it for you if you want to give me the file name for the firmware.
Click to expand...
Click to collapse
If I mount it in linux can I modify it without having to write it to a new img? I tried mounting it and it won't work. Is there some special tool I need to install?
You extracted the xxx.ext4.lz4 to xxx.ext4 then again extracted xxx.ext4 to xxx.img using 7zip LZ4 before mounting to Linux, correct?
VICosPhi said:
You extracted the xxx.ext4.lz4 to xxx.ext4 then again extracted xxx.ext4 to xxx.img using 7zip LZ4 before mounting to Linux, correct?
Click to expand...
Click to collapse
I am also having an issue repacking the image as odin says invalid lz4.
I'm trying to but I get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I haven't tried modifying and repacking the file yet, but what I did was extracted the lz4 to ext4 and then ext4 to img using 7zip LZ4. Then I mounted the img in CentOS and copied the /system folder over to get it Deodexed. Someone posted the other day that you can repack an IMG file and just flash it as IMG without having to convert to EXT4 or LZ4 on an S8 with v2 bootloader. I don't think this has been tested on a newer or v3 bootloader like S9.
Micro-instruction for unpack lz4 formats
-Download lz4 programm in attach. Extract in any folder.
-Put in lz4 folder system.img.ext4.lz4
-Open CMD line for lz4 folder and write:
lz4.exe -d system.img.ext4.lz4 system.img.ext4
-wait
-Done. We have system.img.ext4.
Now we can unpack this with SVAImgUnpack or any tool
mahotlov said:
Micro-instruction for unpack lz4 formats
-Download lz4 programm in attach. Extract in any folder.
-Put in lz4 folder system.img.ext4.lz4
-Open CMD line for lz4 folder and write:
lz4.exe -d system.img.ext4.lz4 system.img.ext4
-wait
-Done. We have system.img.ext4.
Now we can unpack this with SVAImgUnpack or any tool
Click to expand...
Click to collapse
nope decoded but linux reader not work, svaimg not work is oreo
bleros said:
nope decoded but linux reader not work, svaimg not work is oreo
Click to expand...
Click to collapse
I just converted the S7 Oreo Image (BTU-G930FXXU2ERD5) on my debian linux machine. To convert the android sparse file to the raw ext4 image, both worked simg2img and SVAImgUnpack.exe.
Which step does not work? The lz4 decompression? Or the conversion of the android sparse file to an raw ext4 image? Or the reading of the raw ext4 image?
By the way, I'm wondering if the S9 image is using ext4 or f2fs. Maybe that is the problem.
wernerwa said:
I just converted the S7 Oreo Image (BTU-G930FXXU2ERD5) on my debian linux machine. To convert the android sparse file to the raw ext4 image, both worked simg2img and SVAImgUnpack.exe.
Which step does not work? The lz4 decompression? Or the conversion of the android sparse file to an raw ext4 image? Or the reading of the raw ext4 image?
By the way, I'm wondering if the S9 image is using ext4 or f2fs. Maybe that is the problem.
Click to expand...
Click to collapse
i treid on windows , s7 oreo , no worry i have tried on vmware machine with debian and superr kitchen work fine
End of day you will find out that once you modify the stock image, it's no longer "stock" and probably fail when you try to flash it. Integrity verification wont let you. Unless you OEM unlock and flash a custom recovery, which WILL certainly trip your knox. There is no way back. For now. (I hope.)
wernerwa said:
I just converted the S7 Oreo Image (BTU-G930FXXU2ERD5) on my debian linux machine. To convert the android sparse file to the raw ext4 image, both worked simg2img and SVAImgUnpack.exe.
Which step does not work? The lz4 decompression? Or the conversion of the android sparse file to an raw ext4 image? Or the reading of the raw ext4 image?
By the way, I'm wondering if the S9 image is using ext4 or f2fs. Maybe that is the problem.
Click to expand...
Click to collapse
i tried again work fine was my mistake first lz4 used then droped into svaimgunpack then ext4explorer :highfive:
mahotlov said:
Micro-instruction for unpack lz4 formats
-Download lz4 programm in attach. Extract in any folder.
-Put in lz4 folder system.img.ext4.lz4
-Open CMD line for lz4 folder and write:
lz4.exe -d system.img.ext4.lz4 system.img.ext4
-wait
-Done. We have system.img.ext4.
Now we can unpack this with SVAImgUnpack or any tool
Click to expand...
Click to collapse
Hi,
I used 7zip to decompress firmware downloaded from sammobile (s7 edge). But the boot and recovery img I got were boot.img.lz4 and recovery.img.lz4.
I used your tool to get the .img directly without going into .ext4. Did I miss something in the steps I took? Thanks
dknight178
Hi. This instruction I wrote for s8/s9 (+)
Their images in firmware have ext4 extension.
You're doing everything right.
dknight178 said:
Hi,
I used 7zip to decompress firmware downloaded from sammobile (s7 edge). But the boot and recovery img I got were boot.img.lz4 and recovery.img.lz4.
I used your tool to get the .img directly without going into .ext4. Did I miss something in the steps I took? Thanks
Click to expand...
Click to collapse
Only certain partitions , like system and userdata, will have images that include the ext4 extension. Possibly cache, as well. Basically just the main partitions that are always mounted and regularly interacted with when the system is booted up and running.
Nathamio said:
I am also having an issue repacking the image as odin says invalid lz4.
I'm trying to but I get this error:
Click to expand...
Click to collapse
The tar archives used by odin aren't the basic version that 7zip is capable of making,. You need to use an actual tar excutable, and include certain argument. On windows, your tar command should look something like this:
Code:
tar.exe --create --format=gnu -b20 --quoting-style=escape --owner=0 --group=0 --totals --mode=644 -f yourFW.tar boot.img.lz4 recovery.img.lz4 system.img.ext4.lz4 userdata.img.ext4.lz4
That would make a basic AP odin-ready tar package. Then just use md5sum to finish it off, though I don't believe its necessary Something like this:
Code:
md5sum.exe -t yourFW.tar >> yourFW.tar
move yourFW.tar yourFW.tar.md5
I attached d a zip with windows version of tar, md5sum, mv, and ls.
I f I want to make a flashable zip, what steps would I take to extract stock firmware to do so?
up
mahotlov said:
Micro-instruction for unpack lz4 formats
-Download lz4 programm in attach. Extract in any folder.
-Put in lz4 folder system.img.ext4.lz4
-Open CMD line for lz4 folder and write:
lz4.exe -d system.img.ext4.lz4 system.img.ext4
-wait
-Done. We have system.img.ext4.
Now we can unpack this with SVAImgUnpack or any tool
Click to expand...
Click to collapse
i had error
lz4.exe : The term 'lz4.exe' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ lz4.exe
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (lz4.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
hochocnua said:
i had error
lz4.exe : The term 'lz4.exe' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ lz4.exe
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (lz4.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Click to expand...
Click to collapse
wrong path and dont use powershell use cmd as admin
Related
Hi, for those interested I wrote following steps (ubuntu 10.10 32b):
(based on excellent http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images )
I included compiled tools mkbootfs , mkbootimg and perl scripts unpack-bootimg.pl and repack-bootimg.pl.
Repack-bootimg.pl is edited and the needed parameters for our folio are included ([email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 boardtype=PR)
1) unpack attachement mytools.tgz into your home, in your home the folder ~/mytools is created:
tar -xzf mytools.tgz
2) copy existing boot.img into ~/mytools (from foliomod update.zip)
3) ./unpack-bootimg.pl boot.img
- old kernel from boot.img is extracted: boot.img-kernel.gz
- content of contained ramdisk is extracted in folder: boot-img.ramdisk
4) copy new compiled kernel (zImage) into ~/mytools (from <source>/kernel/arch/arm/boot/zImage , you have to compile yourself with the weeds2000 quide http://forum.xda-developers.com/showthread.php?p=10331797#post10331797)
5) make all desired changes into ramdisk folder
6) repack new boot.img with a new kernel and changed ramdisk
./repack-bootimg.pl zImage boot.img-ramdisk boot-new.img
7) new boot image is created as boot-new.img
8) if you want just to experiment, you can take any full foliomod dexter's update.zip (1.3d), put the new boot image inside instead original one.
It is possible to remove the other 2 images (recovery and system) if you want just to flash kernel. NOTE! But you have to remove the extrating command for recovery and system from update.zip/meta-inf/com/google/android/update-script.
p.s. Feel free to correct me, if something wrong with the steps. It's my first attempt to compile kernel
I am on FolioMod 1.3d and I use the kernel built without patches from http://tegramid.com/wiki/Main_Page(Full GPL source bundle including framework) for a day without problems. I had to do a full wipe. It's meant for testing, I don't say that kernel from source is better or worse.
Many thanks to Dexter because everything is based on his release, weeds2000 because of his kernel compile quide and tsh who placed the sources on the git and to all who try hacking our folio
thx for this, that 'll be usefull
thanks for the guide.
i have managed to do every thing up to the repack
when i type
Code:
perl repack-bootimg.pl boot.img-kernel.gz boot.img-ramdisk.gz boot.img
i get error
Code:
boot.img-ramdisk.gz Not a directory at repack-bootimg.pl line 13.
even though it is definatly in their. any idea how to get it to work?
You don't have to provide the folder instead of the packed Ramdisk-File!
Because this script is made doing changes in Ramdisk and kernel..
So you can change the scripts inside the boot.img-ramdisk folder and the script will repack and add it to the new boot.img!
permission denied
i have done everything as you said, but while using split_bootimg.pl i got "permission denied". please suggest me what to do?
1. Enable read/write permissions for that file.
2. Tobr, you made a mistake in repack-bootimg.pl. You forgot to add " ./ " before mkbootimg.
Jon2555 said:
1. Enable read/write permissions for that file.
2. Tobr, you made a mistake in repack-bootimg.pl. You forgot to add " ./ " before mkbootimg.
Click to expand...
Click to collapse
The script was downloaded from internet not written by me. And it worked for me just fine. I can not verify now that you are right (probably you are). If it works for you with ./ then either I can put fixed version for download for others (if there is anybody) or it can be here just as a notice for other users, if not working.
I have ./ defined in my path variable in my profile so that i don't need it.
eror when repack
tobr said:
Hi, for those interested I wrote following steps (ubuntu 10.10 32b):
(based on excellent http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images )
I included compiled tools mkbootfs , mkbootimg and perl scripts unpack-bootimg.pl and repack-bootimg.pl.
Repack-bootimg.pl is edited and the needed parameters for our folio are included ([email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 boardtype=PR)
1) unpack attachement mytools.tgz into your home, in your home the folder ~/mytools is created:
tar -xzf mytools.tgz
2) copy existing boot.img into ~/mytools (from foliomod update.zip)
3) ./unpack-bootimg.pl boot.img
- old kernel from boot.img is extracted: boot.img-kernel.gz
- content of contained ramdisk is extracted in folder: boot-img.ramdisk
4) copy new compiled kernel (zImage) into ~/mytools (from <source>/kernel/arch/arm/boot/zImage , you have to compile yourself with the weeds2000 quide http://forum.xda-developers.com/showthread.php?p=10331797#post10331797)
5) make all desired changes into ramdisk folder
6) repack new boot.img with a new kernel and changed ramdisk
./repack-bootimg.pl zImage boot.img-ramdisk boot-new.img
7) new boot image is created as boot-new.img
8) if you want just to experiment, you can take any full foliomod dexter's update.zip (1.3d), put the new boot image inside instead original one.
It is possible to remove the other 2 images (recovery and system) if you want just to flash kernel. NOTE! But you have to remove the extrating command for recovery and system from update.zip/meta-inf/com/google/android/update-script.
p.s. Feel free to correct me, if something wrong with the steps. It's my first attempt to compile kernel
I am on FolioMod 1.3d and I use the kernel built without patches from http://tegramid.com/wiki/Main_Page(Full GPL source bundle including framework) for a day without problems. I had to do a full wipe. It's meant for testing, I don't say that kernel from source is better or worse.
Many thanks to Dexter because everything is based on his release, weeds2000 because of his kernel compile quide and tsh who placed the sources on the git and to all who try hacking our folio
Click to expand...
Click to collapse
hi
when do this in ubuntu 11.4
get eorr below
[email protected]:~/Desktop/untitled folder$ ./unpack-bootimg.pl boot.img
kernel written to boot.img-kernel.gz
ramdisk written to boot.img-ramdisk.cpio.gz
463 blocks
extracted ramdisk contents to directory boot.img-ramdisk/
[email protected]:~/Desktop/untitled folder$ ./repack-bootimg.pl zImage boot.img-ramdisk boot-new.img
gzip: folder/ramdisk-repack.cpio.gz: No such file or directory
sh: mkbootimg: not found
No such file or directory at ./repack-bootimg.pl line 21.
[email protected]:~/Desktop/untitled folder
can any one help me?
any tools for windows ?
nguyenhonganh said:
any tools for windows ?
Click to expand...
Click to collapse
Same request!
repack problem
Can somebody tell me is it possible to repack kernel and ramdisk using just hex editor? Without this scripts and unmkbootimg and mkbootimg. What does not work for me cos im using i9100 Philz root. I know how to unpack it and change init.rc and pack it back again. So can i just put my (kernel+ramdisk) ramdisk.cpio.gz file inside mmcblk0p5 in exac location. Will that work out? I dont know what this is doing:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x20000000
--cmdline 'no_console_suspend=1' -o new_boot.img
this address thing and cmdline but if i replace just ramdisk i dont need to set up addres again cos everything will be in same place. And one more question if something goes wrong can i boot to recovery or download mode?
New kernel copied itself to mmcblk0p5
and i have new CWM now. So it seems to me recovery is inside mmcblk0p5 as well and my phone never use mmcblk0p6
@tobr, I cannot open the archive of boot.img-kernel.gz. When I try to open it with terminal, it says: Not a valid gzip file. What to do?
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
ip2op01 said:
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
Click to expand...
Click to collapse
http://stackoverflow.com/questions/3879717/what-is-purpose-of-using-system-img-in-android
http://en.wikipedia.org/wiki/Disk_image
http://en.wikipedia.org/wiki/Boot_image
these may help, or may not. But hopefully so, if not try looking around stackoverflow a bit more.
ip2op01 said:
Someone please tell me some basic of data.img system.img boot.img files
their use
and how to edit them ?
Or post some links explaining these.
Click to expand...
Click to collapse
1.
boot.img : be similar with bootstrap in the PC's BIOS,aim to boot the android OS;
data.img : this file includes some user data and system data;
system.img : this file includes some packages and some lib file.
ramdisk.img : emulator's FS(file system)
2.
when the android OS start, emulator loads those image file to ramdisk FS, create "system" file directory and "data" file directory.so you should think that those are android OS component.
3.
(1)unpack:
a. tool-------"unyaffs" download link : http://code.google.com/p/unyaffs/downloads/list
b. command------./unyaffs system.img
(2)pack:
a. tool-------"mkyaffs2image" location:android/out/host/linux-x86/bin or search internet
b. make this tool
c. command------ ./mkyaffs2image <directory> <out_file>
I know this, try myself
Thanks guys
ip2op01 said:
Thanks guys
Click to expand...
Click to collapse
My English is poor,it's my pleasure,you can understand it.
enyblock said:
1.
boot.img : be similar with bootstrap in the PC's BIOS,aim to boot the android OS;
data.img : this file includes some user data and system data;
system.img : this file includes some packages and some lib file.
ramdisk.img : emulator's FS(file system)
2.
when the android OS start, emulator loads those image file to ramdisk FS, create "system" file directory and "data" file directory.so you should think that those are android OS component.
3.
(1)unpack:
a. tool-------"unyaffs" download link : http://code.google.com/p/unyaffs/downloads/list
b. command------./unyaffs system.img
(2)pack:
a. tool-------"mkyaffs2image" location:android/out/host/linux-x86/bin or search internet
b. make this tool
c. command------ ./mkyaffs2image <directory> <out_file>
I know this, try myself
Click to expand...
Click to collapse
So, if I have a ROM with the .img file extension I should flash it as "System" (In TWRP)???
Tutorial in Spanish [TUTO] Como desempaquetar un KDZ y un DZ [LG E610 L5]
Click to expand...
Click to collapse
In LG phones L7/5/3 to opted for DZ format, if we unpack one ROM KDZ we find a CAB, and if you unzipped the CAB seems the DZ.
DZ files are tablets that can be flashed directly, and as always, you can unpack to extract the ROM in BIN format.
NECESSARY TOOLS
Unpack KDZ = LGExtract.exe by navossoc.
Unpack CAB = any decompressor, on Windows, eg. WinRAR.
Unpack DZ = DZDecrypt.exe DZ_Creator.exe by copsfrance
And of course a ROM format KDZ or DZ.
PROCEDURE
The first thing to do is to unpack the KDZ, so copy the file LGExtract.exe on the route where we have the ROM format KDZ and from the console (which previously must be located on the route of the ROM) type:
WINDOWS
Code:
LGExtract.exe -kdz V10X_xx.kdz
LINUX
Code:
wine LGExtract.exe -kdz V10X_xx.kdz
Click to expand...
Click to collapse
and you press Enter
NOTE
Where it saysV10X_xx.kdz must be the name of the ROM, for exampleV10A_00.kdz
When the process is complete will see a file with the same name as the ROM, but with the extension .cab, for example, V10A_00.cab
Unzip it and will the DZ and a DLL file
To unpack the DZ type this:
WINDOWS
Code:
DZDecrypt.exe LGE610AT-xx-VxxX-XX-XXX-xx-xx-20xx+x.dz
LINUX
Code:
wine DZDecrypt.exe LGE610AT-xx-VxxX-XX-XXX-xx-xx-20xx+x.dz
Click to expand...
Click to collapse
And you press Enter
NOTE
Where it saysLGE610AT-xx-VxxX-XX-XXX-xx-xx-20xx+x.dz should be the name of the DZ, for example:LGE610AT-00-V10b-EUR-XXX-MAY-23-2012+0.dz
We already have the ROM in BIN format, now you have to concatenate the files SYSTEM, so we use the console and...:
WINODWS
Code:
copy /b "system.img.ext4_
[*]" "system.img"
LINUX
Code:
cat system.img.ext4_* > system.img.ext4
Click to expand...
Click to collapse
And you press Enter and you can delete the files system.img.ext4_0, system.img.ext4_1,..., system.img.ext4_6 (version DZDecrypt.exe v1.0c+ does this job automatically)
Now we'll have a list like this:
Code:
amss.bin
boot.img
boot_logo.bin
emmc_appsboot.bin
oemsbl.bin
partition.bin
persist.img.ext4
qcsbl.mbn
qcsblhd_cfgdata.mbn
recovery.img
system.img.ext4
Click to expand...
Click to collapse
Files .ext4 are you can rename to .img and mount as one drive in Linux or WIndows with Winimage manipulate its contents
LINUX:
Code:
mkdir system
sudo mount system.img.ext4 system -oloop
To disassemble
Code:
sudo umount system
Click to expand...
Click to collapse
With this I believe that we have done, if something is missing or you have any questions to ask without fear.
very useful for stock rom modding... I was looking for this a month ago, so thanks man!
I cant open with WinImage my system.img extract from L3 e400 V10O_00.kdz
Ygreck said:
I cant open with WinImage my system.img extract from L3 e400 V10O_00.kdz
Click to expand...
Click to collapse
for .img (from .kdz) u have to use ext2explorer
google it or try this link
http://d-h.st/nRw
i've tried to add it as attachment but failed for unknown reasons.
All this procedure will not work for E435.
i've got 1gb .dz file but unable to extract it.
any ideas?
Sudeep Duhoon said:
... All this procedure will not work for E435.
i've got 1gb .dz file but unable to extract it.
any ideas?
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showpost.php?p=38748031&postcount=43
Homero2 said:
Try this http://forum.xda-developers.com/showpost.php?p=38748031&postcount=43
Click to expand...
Click to collapse
i tried this, no change
Homero2 said:
In LG phones L7/5/3 to opted for DZ format, if we desempaquetamos one ROM KDZ we find a CAB, and if you unzipped the CAB seems the DZ.
DZ files are tablets that can be flashed directly, and as always, you can unpack to extract the ROM in BIN format.
NECESARY TOOLS
Unpack KDZ = LGExtract.exe by navossoc.
Unpack CAB = any decompressor, on Windows, eg. WinRAR.
Unpack DZ = DZDecrypt.exe DZ_Creator.exe by copsfrance
And of course a ROM format KDZ or DZ.
PROCEDURE
The first thing to do is to unpack the KDZ, so copy the file LGExtract.exe on the route where we have the ROM format KDZ and from the console (which previously must be located on the route of the ROM) type:
and you press Enter
NOTE
Where it saysV10X_xx.kdz must be the name of the ROM, for exampleV10A_00.kdz
When the process is complete will see a file with the same name as the ROM, but with the extension .cab, for example, V10A_00.cab
Unzip it and will the DZ and a DLL file
To unpack the DZ type this:
And you press Enter
NOTE
Where it saysLGE610AT-xx-VxxX-XX-XXX-xx-xx-20xx+x.dz should be the name of the DZ, for example:LGE610AT-00-V10b-EUR-XXX-MAY-23-2012+0.dz
We already have the ROM in BIN format, now you have to concatenate the files SYSTEM, so we use the console and...:
And you press Enter and you can delete the files system.img.ext4_0, system.img.ext4_1,..., system.img.ext4_6 (version DZDecrypt.exe v1.0c+ does this job automatically)
Now we'll have a list like this:
Files .ext4 are you can rename to .img and mount as one drive in Linux or WIndows with Winimage manipulate its contents
With this I believe that we have done, if something is missing or you have any questions to ask without fear.
Click to expand...
Click to collapse
yes
slarkpro said:
hi pro i have added root file into dz file now i join dz file and dll file via uptest marwin but have an error i don't undestand pls help me!!
Click to expand...
Click to collapse
Bạn bên tinhte.vn à:thumbup:
Gửi từ LG-Optimus L7 của tôi bằng cách sử dụng Tapatalk2
is there a kdz extractor for linux???
ensarman said:
is there a kdz extractor for linux???
Click to expand...
Click to collapse
afaik no
but as the thread explain you should use wine
I used it but my cellphone is a LG L3 II
and I cannot extract the DZ file. I cannot find how to extract my kdz : (
But the kdz updater software can do it but I don't know where that software extract the kdz
Homero2 said:
In LG phones L7/5/3 to opted for DZ format, if we unpack one ROM KDZ we find a CAB, and if you unzipped the CAB seems the DZ.
DZ files are tablets that can be flashed directly, and as always, you can unpack to extract the ROM in BIN format.
NECESSARY TOOLS
Unpack KDZ = LGExtract.exe by navossoc.
Unpack CAB = any decompressor, on Windows, eg. WinRAR.
Unpack DZ = DZDecrypt.exe DZ_Creator.exe by copsfrance
And of course a ROM format KDZ or DZ.
PROCEDURE
The first thing to do is to unpack the KDZ, so copy the file LGExtract.exe on the route where we have the ROM format KDZ and from the console (which previously must be located on the route of the ROM) type:
and you press Enter
NOTE
Where it saysV10X_xx.kdz must be the name of the ROM, for exampleV10A_00.kdz
When the process is complete will see a file with the same name as the ROM, but with the extension .cab, for example, V10A_00.cab
Unzip it and will the DZ and a DLL file
To unpack the DZ type this:
And you press Enter
NOTE
Where it saysLGE610AT-xx-VxxX-XX-XXX-xx-xx-20xx+x.dz should be the name of the DZ, for example:LGE610AT-00-V10b-EUR-XXX-MAY-23-2012+0.dz
We already have the ROM in BIN format, now you have to concatenate the files SYSTEM, so we use the console and...:
And you press Enter and you can delete the files system.img.ext4_0, system.img.ext4_1,..., system.img.ext4_6 (version DZDecrypt.exe v1.0c+ does this job automatically)
Now we'll have a list like this:
Files .ext4 are you can rename to .img and mount as one drive in Linux or WIndows with Winimage manipulate its contents
With this I believe that we have done, if something is missing or you have any questions to ask without fear.
Click to expand...
Click to collapse
Is there a way to get to the totc.cfg file and edit it?
Hello,
I was able to unpack the image simply by using the command
Code:
unrar x system.img
Now that I have made my modifications (literally only changing the build.prop to start) I need to repack the system file folder back to an "x-raw-disk-image". Does anybody know how I may do this? Thanks everyone!
After lots of search i found a way to extract those img file from super.img
What is need?
1.Computer with linux os.
extract zip file from this post and place your super.img in same location where you extract..
then run below cmd...
simg2img super.img super.img.raw
To extract system.img run below cmd
./lpunpack --partition=system super.img.raw
To extract vendor.img run below cmd
./lpunpack --partition=vendor super.img.raw
To extract product.img run below cmd
./lpunpack --partition=product super.img.raw
Shas45558 said:
After lots of search i found a way to extract those img file from super.img
Click to expand...
Click to collapse
It is better to let other also know where you have found this. https://github.com/AndroidDumps/Fir...20a9a111b44f79da89b8/tools/Linux/bin/lpunpack from https://github.com/AndroidDumps/Firmware_extractor
HemanthJabalpuri said:
It is better to let other also know where you have found this. https://github.com/AndroidDumps/Fir...20a9a111b44f79da89b8/tools/Linux/bin/lpunpack from https://github.com/AndroidDumps/Firmware_extractor
Click to expand...
Click to collapse
Tnx for suggestions....and right i found it from those source.i want to simplify the hole process....
Shas45558 said:
After lots of search i found a way to extract those img file from super.img
What is need?
1.Computer with linux os.
extract zip file from this post and place your super.img in same location where you extract..
then run below cmd...
simg2img super.img super.img.raw
To extract system.img run below cmd
./lpunpack --partition=system super.img.raw
To extract vendor.img run below cmd
./lpunpack --partition=vendor super.img.raw
To extract product.img run below cmd
./lpunpack --partition=product super.img.raw
Click to expand...
Click to collapse
how to repack after modeficatiom
mohacraft8 said:
how to repack after modeficatiom
Click to expand...
Click to collapse
Sorry i do not know...
But you can flash then via fastbootd mood..
Remember do not use fastbootd if you are custom recovery...it must brick your device...
So flash stock recovery..go fastbootd mood and flash system, vendor and product..
Tnx for understanding.
mohacraft8 said:
how to repack after modeficatiom
Click to expand...
Click to collapse
You have to use lpmake for it.
See https://forum.xda-developers.com/t/gsis-on-a51-5g.4114349/ and https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/ for more info.
.......
Bro can we get modem.img by this
So let say if we flashing super.img , does it automatically flashed product.img ? or need to manually flash the product.img ?