My intent is to provide flashable debrick files for myself and others, from dumps. I am using @smitels patched Lgup Tool (check out the G5/v20 threads). I was able to configure and do complete dumps for several lesser developed (but widely used) LG models: Stylo 3 LGLS777, Stylo 3 LG M430, and X Charge LG SP320. The dumps are large, 14.5GB and between 51-61 files. The problem I have, and which will reveal my ignorance, is that the files have no extentions and are listed: Aboot_COM8, Abootbak_COM8, tz_COM8 etc, img files all I'm assuming. I tried several tools Kdz extraction tool, lg extraction tool etc but none worked. Ext2reader/ explorer don't read them. How can I create kdz/tot files from these dumps? Flashable zips? Thanks for pointing the way.
Ablutions said:
My intent is to provide flashable debrick files for myself and others, from dumps. I am using @smitels patched Lgup Tool (check out the G5/v20 threads). I was able to configure and do complete dumps for several lesser developed (but widely used) LG models: Stylo 3 LGLS777, Stylo 3 LG M430, and X Charge LG SP320. The dumps are large, 14.5GB and between 51-61 files. The problem I have, and which will reveal my ignorance, is that the files have no extentions and are listed: Aboot_COM8, Abootbak_COM8, tz_COM8 etc, img files all I'm assuming. I tried several tools Kdz extraction tool, lg extraction tool etc but none worked. Ext2reader/ explorer don't read them. How can I create kdz/tot files from these dumps? Flashable zips? Thanks for pointing the way.
Click to expand...
Click to collapse
I am also interested in knowing how I can extract the contents of these files or how to mount them, I need to recover data from the userdata partition when I see their concern, it came to my mind that this can also be useful for me.
Idk yet. Kdztools, LG firmware extractor tool neither work read the raw files. Nor does appending the _COM8 (or what ever). Nor does renaming .img. Idk if I have the tools misconfigured or the wrong tools. I just need to read more. Let me know if you make progress.
Ablutions said:
My intent is to provide flashable debrick files for myself and others, from dumps. I am using @smitels patched Lgup Tool (check out the G5/v20 threads). I was able to configure and do complete dumps for several lesser developed (but widely used) LG models: Stylo 3 LGLS777, Stylo 3 LG M430, and X Charge LG SP320. The dumps are large, 14.5GB and between 51-61 files. The problem I have, and which will reveal my ignorance, is that the files have no extentions and are listed: Aboot_COM8, Abootbak_COM8, tz_COM8 etc, img files all I'm assuming. I tried several tools Kdz extraction tool, lg extraction tool etc but none worked. Ext2reader/ explorer don't read them. How can I create kdz/tot files from these dumps? Flashable zips? Thanks for pointing the way.
Click to expand...
Click to collapse
Do you have dump for m430?
you have the stock firmware?? usually you just change the file extension to .zip and extract it with winzip after your partition will be extracted such as boot.tar.md5 , recovery.tar.md5, system.tar.md5 after that just rename them .tar remove the .md5 and just download LZMA unpacker and drop them on it and you will get .img
Related
So there are quite a few applications out there that can extract, browse, modify and repackage a KDZ file.
Has anyone had luck or even attempted to try one of these programs?
I know with the program UpTestEX_mod2_marwin that we use with windows enabler gives us the option to decrypt the kdz.
The output becomes a wdb file, but from there I'm lost. Tried LGutils but kept getting errors.
Got a lot of info from here: http://code.google.com/p/arenoid/wiki/KDZExtractPack
Hopefully someone can use this information better than I can.
Jrkoffjonson said:
So there are quite a few applications out there that can extract, browse, modify and repackage a KDZ file.
Has anyone had luck or even attempted to try one of these programs?
I know with the program UpTestEX_mod2_marwin that we use with windows enabler gives us the option to decrypt the kdz.
The output becomes a wdb file, but from there I'm lost. Tried LGutils but kept getting errors.
Got a lot of info from here: http://code.google.com/p/arenoid/wiki/KDZExtractPack
Hopefully someone can use this information better than I can.
Click to expand...
Click to collapse
The only cab L9 KDZ file WDB bin and fls can be extracted from the DZDrecyte need to be able to take out a dz file can not be. L7 can KDZ out andthe DZDecrypt dz can be taken apart.
The L9 KDZ out you can not do extract dz
Jrkoffjonson said:
So there are quite a few applications out there that can extract, browse, modify and repackage a KDZ file.
Has anyone had luck or even attempted to try one of these programs?
I know with the program UpTestEX_mod2_marwin that we use with windows enabler gives us the option to decrypt the kdz.
The output becomes a wdb file, but from there I'm lost. Tried LGutils but kept getting errors.
Got a lot of info from here: http://code.google.com/p/arenoid/wiki/KDZExtractPack
Hopefully someone can use this information better than I can.
Click to expand...
Click to collapse
For LG L9 also (tested ok), Anyone can create FLS+BIN from KDZ with this Amazing Tool by SpyRosk...
[TOOL] All-In-One ToolKit v5.0 |KDZ FLASH|ROOT|Repartitioning|SmartFlash|DualBoot
Have tested this perfectly on all KDZ of L9. And if you could figure out the code in Batch File, you can easily create wdb file.
If you are talking about decrypting KDZ, that is possible on Linux machines only, I may be wrong about that.
cmahendra said:
If you are talking about decrypting KDZ, that is possible on Linux machines only, I may be wrong about that.
Click to expand...
Click to collapse
I extracted KDZ file (on win7) into two files:
LGP765_V10E_00_AP.bin - firware itself
LGP765_V10E_00_CP.fls - baseband file (AFAIK)
So my question - if exists any possibility to modify .bin file? I can extract from there boot and recovery partitions, but i want to modify system
AngryWolf80 said:
I extracted KDZ file (on win7) into two files:
LGP765_V10E_00_AP.bin - firware itself
LGP765_V10E_00_CP.fls - baseband file (AFAIK)
So my question - if exists any possibility to modify .bin file? I can extract from there boot and recovery partitions, but i want to modify system
Click to expand...
Click to collapse
what exactly u are upto?
cmahendra said:
what exactly u are upto?
Click to expand...
Click to collapse
Root for V10F... as example
AngryWolf80 said:
Root for V10F... as example
Click to expand...
Click to collapse
you mean to say if you can extract bin/wdb file you will be able to root it and make kdz again?
cmahendra said:
you mean to say if you can extract bin/wdb file you will be able to root it and make kdz again?
Click to expand...
Click to collapse
That's pretty much what I've been trying to accomplish but gave up as I couldn't get past extracting the BIN/FLS files..
Jrkoffjonson said:
That's pretty much what I've been trying to accomplish but gave up as I couldn't get past extracting the BIN/FLS files..
Click to expand...
Click to collapse
I'm find out what .bin file contains all partitions of phone. And all this partitions signed with RSA key. So to modify we must know this key
As example - http://and-developers.com/partitions:isw
AngryWolf80 said:
I'm find out what .bin file contains all partitions of phone. And all this partitions signed with RSA key. So to modify we must know this key
As example - http://and-developers.com/partitions:isw
Click to expand...
Click to collapse
That site is about motorola phones if i am no mistaken.
Seems this tool made for KP500 for device of 2010 does not work on latest JB KDZ. Tried with no success.
I have a Huawei Y536A1 US version. I am attempting to port the Y536A1 Canada Rogers version as it appears to have no carrier apps within it. I installed Cygwin and dsixda' Android Kitchen but the optiuon to extract the system.img file (ext4) does not work. I found the post for installing perl, split_update, ext4 unpacker exe, and huawei finder. Following the steps, I can unpack the system.img and extract the build.prop file. However I am totally lost at how to either edit the Canadian build.prop or how to replace it with the US version. It is simple enough to replace any .img file within the output folder, but I can't figure out how to replace or edit files inside the .img files once they are unpacked into the EXT4 unpacker. Any help would be greatly appreciated. Also, if I am going about this incorrectly, any info on redirecting my efforts to be used with a different tool would also be appreciated.
In the past there was a tool to extract tot files from kdz known as lgextract this toolno longer works on new kdz Does anyone know about any tool to convert .kdz files to .tot.And i have seen some custom tot made by some people on xda how they made them?
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
I am trying to extract an OEM LG V600TM kdz file using an LG Firmware Extract tool. I have tried four different ROMs, and each has a file like "V60010x00user-signed-ARBONA2" file where the .dz file should be. If I try to extract the ARBONA2 file as if it were a .dz file, the program immediately aborts and the entire window closes.
I have searched for hours for "ARBONA2 file" with no results, but I can't believe I'm the only one who has run into this. I've added the ".dz" suffix to the file name with the same results. Does anyone here know what this ARBONA file is, why it is in the .dz file location, and/or how to work with it to extract the rest of the ROM?
Thanks for your help.
Cirrus9 said:
LG Firmware Extract tool
Click to expand...
Click to collapse
is outdated. Try using some python scripts out there for the newer firmware.
Basic LG KDZ & DZ extractor - The Bootloader Locksmiths
Android modding community, we're here to support you!
tbl-locksmiths.com
Edit : Link outdated, lol... try this..
A guide to extracting LG KDZ firmware update files in order to unpack the super.img held therein.
A guide to extracting LG KDZ firmware update files in order to unpack the super.img held therein. - kdzextraction.md
gist.github.com