Related
Hi guys, i searched lot, but did not find any proper solution for getting flashable files of smart flash from kdz..
Plz help guys..
Obviously you haven`t searched enough .
I think that you are looking for LGExtract 0.2.1
Tool is in it`s beginning, but from reading I think that it can extract smartflash files from kdz and it is tested on p990 (I haven`t tested it).
k, i tried that, now i got 13 files.
some are img, some fls etc.
but we need only 2 files for flashing with smartflash tool. bin and fls.
how to get them ?
As I said, I haven`t tried to do this, hence I can`t help you. You will must to read and ask for support in original thread, where the author of the tool is present.
If you are trying to flash kdz and since LG have changed their politics, try to read this thread too... http://forum.xda-developers.com/showthread.php?t=1473781
Hi all,
first, thank you Memhis, the tool is excellent. It works under Linux too in Wine environment.
But I have some observations and some questions
- first decrypt/decompile KDZ file only extract a CAB file - this CAB file can be extracted by cabextract utility
- after CAB file extraction, there is WDB file and machine specific DLL - this DLL file must be used for extraction of WDB, I try the newer one without success
- after performing extraction of WDB using DLL there are number of files which can be useful
AENEAS_FW.fls, psi.fls, R375_SIC.fls, slb.fls - these files are the baseband and can be flashed using smart flash tool - it must be flashed all, not only some
#_Split_Data.img - after joining this file to one, it contains Linux filesystem (now EXT3) with all data of /system partition and you can get lge-ril.so from this
The remaining files I don't identify and only speculate what is it
ext3_flashboot.img - this filesystem is used to boot for flashing???
fastboot.bin - ???
recovery.img - recovery partition - this images is used to replace ClockWorkMod I think
Once again, many thanks. I was searching for this similar tool about six moths ago.
can you tel me,how do you extract the split_data.img??
at this point i have no idea what i must do and find nothing about it.
cojo11 said:
can you tel me,how do you extract the split_data.img??
at this point i have no idea what i must do and find nothing about it.
Click to expand...
Click to collapse
+1
........
There is nothing to "extract" from split_data.img. It is a true EXT3 Linux filesystem. You have to use a Linux box or something to allow mount an Linux image to Windows environment. I can only point you to http://www.ext2fsd.com/ site which is free good ext2/3/4 filesystem driver, but I don't know, if it is usable - it can mount a Linux partition under Windows but don't know it can mount a image file as disk. Hope so.
Thanks for the information, but I can't extract Split_Data.img (it's the joined file of 4 .img files).
How can I extract this .img in Linux (virtual machine)?
Flix123 said:
Thanks for the information, but I can't extract Split_Data.img (it's the joined file of 4 .img files).
How can I extract this .img in Linux (virtual machine)?
Click to expand...
Click to collapse
You have to mount it, like it is a whole filesystem. Google it to find out how to mount img file. Once done, you'll open it like a hard drive.
Edit: Forget my question, it works now!
My last question: Is the file "ext3_flashboot" the same as the boot.img files in CWM roms?
OK, I managed to extract the kdz file and I made a rebuild of V20c without flashing the kdz, just with extracting!
I'll upload it in a few minutes!
For those who wants to extract KDZ I prepare a little manual...
Keltek said:
For those who wants to extract KDZ I prepare a little manual...
Click to expand...
Click to collapse
Hi Keltek, thanks for the manual. but i am getting some error, any ideas? I'm using Win 7 32-Bit. This is the error:
C:\>LGExtract -kdz V20F_00.kdz
Extracting:
KDZ: V20F_00.kdz
Failed to create cab file.
Error code: 00000005
Message: Access is denied.
Failed to extract file.
Please report this error with this file.
thanks
NEVER MIND: cmd.exe should "Run as Administrator", it works now.
The last question I have is how to join the 4 extracted baseband files to one file?
Does that work with copy /b command?
What i got from flashing basebands is that youre supposed to flash them one by one from largest to smallest file. so basically what you should be doing to "compress" the procedure is you unpack those 4 files, put the largest one in place and copy the others onto it, replacing duplicates. Then repackage what you merged, and try that, cant think of anything more logical than that.
That sounds logical, but I don't know how to extract the files.
But it's not very important, because it isn't a problem to flash 4 files instead of one.
Please extract Bb from v20h rohan
Sent from my LG-P990 using Tapatalk
If you give me the link to the kdz, I will extract the baseband for you.
spica1234 said:
Please extract Bb from v20h rohan
Click to expand...
Click to collapse
You should specify from which ROM file, coz there are many version with same identification but different content - I don't understand why LG do this - the V20q for Czech Republic is not the same as V20q for Italy...
I take a look at V20h and it contain 1035.21_20110725 BaseBand.
LG BIN/TOT Extractor
This is a tool for extracting LG Bin/Tot Firmware files.
I update the git a lot more than what I update the thread so check there for latest news.
Features
Split Bin file into relevant partitions
Split Tot file into relevant blocks and merge blocks into partitions
Display AP Header
Display GPT Header
Extract Header from Bin/Tot File
Features I like to implement (and probably won't get around to)
Extracting boot img (The tools currently available don't work in all cases and it's very easy to read the header since it's open source.)
Extracting ext4 partitions. So that it's easy to access the file. Theres already other tools that can do this so this isn't essential.
Mergeing tot partitions based on data from partitions itself and not GPT
Inject Alternate Data into partitions. I'll block access to X-loader,U-boot and GPT so that You can't kill your phone.
Source
https://github.com/Xonar/LGBinExtractor
Confirmed to work with
Quite a few phones.
I lost track of which ones work.
To check just run with -daph. You'll get file information if it works and either garbled data or an error message if it doesn't.
If your phones not supported follow the steps on git readme.
Thanks
SnowLeopardJB - for lots and lots of testing
navossoc - his tool that extracts kdz and wdb files
vim1 - D821 support
scotty755 - LGL22 support
tkawajir - L-04E and LG G Flex F340K support
If you feel I forgot to thank you, msg me and I'll add you.
If it can extract BIN files then yes. We believe the nandroid V30* of KU5900 that was supplied was incomplete. So If KDZ is converted to BIN and FLS (which we can), then extract contents of BIN, then you can have complete files without looking for Koreans and Chinese to relay that the nandroid was incomplete and can have untampered files.
xonar_ said:
Question to other Devs
Will you use a tool like this or am I wasting my time?
Is a tool like this allowed or would it be considered reverse engineering? (If its not allowed I'm going to stop IMMEDIATELY)
Click to expand...
Click to collapse
Yes I will. If I myself can build a program to extract this EFI partition..
It is reverse engineering, but I don't know if it's legal or not (in this case), but for me it's legal as I'm considered this to educational purpose
Many others tool was created to have purpose like this, for example http://psas.revskills.de/?q=node/5
-CMIIW-
I've attached an image of the system partition of the V20E_00 for you guys to see.
I am going to download the v30H_00.kdz today. So I'll keep you posted about how the extracting goes. I probably won't have time to check it out until the weekend so please don't hold your breath.
I've only recently managed to find the necessary information about the ext4 file system to integrate the functionality into my tool. For now Ext2Read can extract the ext4 file system just fine. I'll add that somewhere over the weekend (Provided something doesn't come up).
Could you as soon, as you are able to unpack it fully maybe upload a complete backup of the system partition and also system2, cause we think, that in the nandroid there are some files missing and we need those, to probably be able to boot that system. Great job btw
Thanks for the positive feedback.
I am getting the v30h_00.kdz in a few hours (I got a friend to download it for me, I don't have that much cap ).
There is no way I will be able to upload the file since it will be big but if it works I'll post the tool and how to do it.
GitHub is giving me an error : "Page did not respond in a timely fashion". I am going to try again tonight to post the source.
I already tried to extract the bin files, but I didn't see any pattern to know where start or ends a partition.
Some partitions you can identify by it's header and try to extract the file size from there (i did that with recovery.exe).
If you know for sure the partition name and the address, I can improve the recovery.exe to patch always the right partition.
So, what is the trick?
[]'s
navossoc said:
I already tried to extract the bin files, but I didn't see any pattern to know where start or ends a partition.
Some partitions you can identify by it's header and try to extract the file size from there (i did that with recovery.exe).
If you know for sure the partition name and the address, I can improve the recovery.exe to patch always the right partition.
So, what is the trick?
[]'s
Click to expand...
Click to collapse
The first meg of the file contains the names of the data blocks size on file,size on disk and where they start on file. I'll post exactly how it is set out later.
The data blocks aren't only partitions though for example the first one is the GPT header with it's corresponding entries and also some blocks are empty.
I recognized the start the two partitions from your tool.
Sent from my LG Optimus Black
xonar_ said:
The first meg of the file contains the names of the data blocks size on file,size on disk and where they start on file. I'll post exactly how it is set out later.
The data blocks aren't only partitions though for example the first one is the GPT header with it's corresponding entries and also some blocks are empty.
I recognized the start the two partitions from your tool.
Sent from my LG Optimus Black
Click to expand...
Click to collapse
You are talking about the first 1MB from BIN? right?
They are using little endian or big endian to represent the numbers?
The name of the sections I already knew, but never found the initial offset.
I will try to take a look later.
[]'s
navossoc said:
You are talking about the first 1MB from BIN? right?
They are using little endian or big endian to represent the numbers?
The name of the sections I already knew, but never found the initial offset.
I will try to take a look later.
[]'s
Click to expand...
Click to collapse
Yes the BIN. They are using little endian. All the offsets and sizes are in LBA's (512 bytes in this case) with LBA 0 starting at 0x100000.
Sent from my LG Optimus Black
Source of Bin Fls Extractor (So far)
GitHub isn't working out as planned. The client stopped downloading in the middle and I don't want to waste more cap so here is the source as an attachment.
This is still a work in progress and is only confirmed to work with v20E_00 South Africa.
Linux users can just mount the *.img file of system to access it. Windows users have to use a tool like Ext2Read. Mac users I'm not sure : Google it.
EDIT : I wont be able to get the v30 kdz for another day unfortunately. Feel free to try and change my tool to work with it.
EDIT2: These sources are old. I'll upload my fixed ones later. Reads in chunks and works on P970 and KU5900 ( I don't have any other files to test it with but it should work with almost all BIN files extracted from kdz files )
xonar_ said:
GitHub isn't working out as planned. The client stopped downloading in the middle and I don't want to waste more cap so here is the source as an attachment.
This is still a work in progress and is only confirmed to work with v20E_00 South Africa.
Linux users can just mount the *.img file of system to access it. Windows users have to use a tool like Ext2Read. Mac users I'm not sure : Google it.
EDIT : I wont be able to get the v30 kdz for another day unfortunately. Feel free to try and change my tool to work with it.
Click to expand...
Click to collapse
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
Nice! Great job you guys. :good:
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
can you upload system files asap?
George Jetson said:
can you upload system files asap?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=31443301&postcount=270
Thanks to navossoc there
navossoc said:
Nah! The damn trick was the 512 bytes + 0x100000 base.
I never thinked about it...
I take a look at your code, I understand the whole concept now.
I have successfully extracted the system.img and system2.img from the V30H_00.kdz
Nice, maybe later I can do some modifications on recovery.exe, so they can find always the correct partition for recovery.img. (without the user choose one)
[]'s
Click to expand...
Click to collapse
That's good news.
I won't be able to work on the program during the rest of this week. With the system files extracted there's nothing that needs to be urgently done.
Next Step is to to try and build the BIN from other files. I think I can improve on your recovery.exe to add su binary and apk aswel (Might take a bit longer since I need to extract the ext4 partition, add su then put it back together )
Well, it's just a beta, because it use too much ram to write the files.
I need to read the file in chunks, but, for now it's a good prototype, we can using it.
extract.7z
Code:
CRC32: 2199d10f
MD5: 5b8d8031ff5d66ec2832d182e98505be
SHA-1: b6d729a20d4370e25ebc4eddfc27e25673b1d2f2
To use the tool is just run...
Code:
extract.exe filename_AP.bin
It should work on any bin file, tested on P920, P970 and KU5900.
Please report any error.
[]'s
Thanks navossoc its working well on ginger p970 bin file.
Great stuff thanks alot! You to make a great team.
Sent from my LG-P920 using xda app-developers app
Now how can we make a new bin file with that img files?
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
EDIT: If you can't run the script with the ./ command, chmod +x the file
Antonyb1995 said:
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
Click to expand...
Click to collapse
work on gt-i8200n to?
linklusitano said:
work on gt-i8200n to?
Click to expand...
Click to collapse
No reason why not, I'm just not able to test others
Antonyb1995 said:
No reason why not, I'm just not able to test others
Click to expand...
Click to collapse
testing
linklusitano said:
testing
Click to expand...
Click to collapse
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Antonyb1995 said:
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Click to expand...
Click to collapse
how do i run worker.txt?
linklusitano said:
how do i run worker.txt?
Click to expand...
Click to collapse
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Antonyb1995 said:
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Click to expand...
Click to collapse
windows 8.1
linklusitano said:
windows 8.1
Click to expand...
Click to collapse
Ah okay, If you install Cygwin you can run bash scripts in Windows.
LINK: https://www.cygwin.com/
Does such a thing exist? if not i'd be willing to donate to the cause for a tutorial
wrecklesswun said:
Does such a thing exist? if not i'd be willing to donate to the cause for a tutorial
Click to expand...
Click to collapse
It can be done manually, but it's kinda labor intensive.
You mount the old (latest full image without the update) image in Linux, then unzip the update.zip then copy and replace everything in the .zip file to the mounted image.
Just have to make sure you do it for every file and directory and possibly you have to set the file permissions and file owners again...
i am a windows guy so kinda confusing - i start with an img file which i mount using? once mounted, i get the place everything in the zip in the mount commit and unmount. is thi ssimply it? if so what could i use the mount the img? vmware? virtualbox?
wrecklesswun said:
i am a windows guy so kinda confusing - i start with an img file which i mount using? once mounted, i get the place everything in the zip in the mount commit and unmount. is thi ssimply it? if so what could i use the mount the img? vmware? virtualbox?
Click to expand...
Click to collapse
I have both Ubuntu and Windows here at work, and I've been trying to modify Android .img files without much success using Windows.
The problem is that those .img files are in EXT4 filesystem, which Windows doesn't support natively.
There some EXT4 utilities for Windows, but I haven't really had the time to try them yet.
If you have VMWare or Hyper-V on your Windows machine, you could just set a VM with Ubuntu, or you could just use a computer to boot Ubuntu from USB flash drive, without the need to actually install it.
However, because you are not familiar with Linux, it's going to be hard for you...
It basically involves mounting an old .img file, then unziping the .zip and replace everything in the .zip file to the mounted image.
However, you need to pay attention to file permissions and file owenship, when replacing the files.
It's really a lot of work... I'm using my own modified .img files based on ComputerFreek's images but I've never attempted to "patch" an .img with an update.zip... it's just not worth my time..
Here is the link to if you want to learn how to modify an .img file: http://forum.xda-developers.com/droid-turbo/general/tutorial-how-to-modify-turbo-images-t3064595
It's probably easier to just wait for the full .img
how about conveerting a zip to a img?
Hi,
I wanted to mod original firmware.
I managed to extract rom using HuaweiUpdateExtractor_0.9.9.5 & then simg2img, but then i want to mod files inside img archive and repack it to state that allows to install it on phone.
Any good guides or ideas how i can do it?
You can't
The Restless Soul said:
You can't
Click to expand...
Click to collapse
Hi, by now i unpacked, mounted on linux, removed files i needed to remove, and again packed using: img2simg binary. Do You think it won't work?
I wanted to degoogle system file. Will it fail on some hack check or sth?
Kusznier said:
Hi, by now i unpacked, mounted on linux, removed files i needed to remove, and again packed using: img2simg binary. Do You think it won't work?
I wanted to degoogle system file. Will it fail on some hack check or sth?
Click to expand...
Click to collapse
You can't simply modify an update file, thinking it will flash perfectly. It's logic here