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?
Related
This guide will help you in porting ROM's to different devices. Although it my not work 100% of the time, it should you show the steps involved in porting a ROM but also which files are important to a device's functionality.
Some handy tools to have before starting:
- The Android SDK, this contains ADB logcat which is a hugely important tool in ROM development. It lets us know what is perhaps causing an app to F/C or a ROM to bootloop. See our guide on how to set this up HERE
- Notepad++ , very useful for altering scripts.
- Patience, getting ports to boot can sometimes take a lot of effort and time but hopefully this guide will show you the quickest and easiest way to get your ported ROM booting.
Okay first decide which ROM you would like to port, don't port HDPI ROM's to MDPI devices or vice versa it just won't work.And it's best to start with the easy and simple ports to get some experience behind you before you go off porting Sense 3.0 to your X10.
Let's get started...
Porting is fairly easy and requires only some folders, files and a boot.img to be replaced.
Now because this is a universal guide I can only tell you how to get the basic hardware working on your port. AOSP ROMs are fairly easy to figure out so you won't have much trouble figuring out what needs replacing. Manufacturer specific ROMs such as Sense 3.0 ROMs are bit more difficult to figure out but the basic skills you will be taught here can be applied in principle to those ROMs.
1. First off lets start with the biggie, the kernel. Those of you familiar with linux will know how important the kernel is a to system, I won't go into detail here but if your kernel isn't specific to your device then your ROM won't boot. The kernel is contained within the boot.img of your ROM's zip (or zImage if it's a Samsung). During flashing it is unpacked and wrote to the system.
To replace the kernel we need to decompile it and no this isn't as easy as opening it winzip. The best way to do this is using Linux; we can use a combination of both perl scripts and terminal commands.
In order for us too see the kernel files contained within the boot.img, we need to first unpack it and this will extract the kernel binary and the ramdisk. What you need at this point is the split_bootimg.zip. This contains a perl script which will extract both files and display the boot.img header, the kernel command line and the board name (if specified).
An example of the output would be:
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1
So how to use this perl script you ask? Well...
First open a terminal and cd to the directory which contains the perl scripts you just downloaded. Next, type this command: "perl split_bootimg.pl boot.img" and that will extract the kernel to your current directory.
Now, we need to extract the ramdisk, the ramdisk has been unpacked from the boot.img and is sitting your current directory with the file name "boot.img-ramdisk.gz", at the moment this still isn't useful to us so we need to un-gzip and then un-cpio it.
So for that we need the Linux terminal. So again from the terminal or using the same terminal enter these commands:
mkdir ramdisk < Creates a directory where we can store the ramdisk
cd ramdisk < Changes our current directory to that of the ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i < Will un-gzip and un-cpio ramdisk
Okay so now we can see all the ramdisk files:
./init.devicename.rc
./default.prop
./proc
./dev
./init.rc
./init
./sys
./init.goldfish.rc
./sbin
./sbin/adbd
./system
./data
So what's important here is the "init.devicename.rc" and "unvented.device.rc". This is the target devices .rc files contained within the ramdisk, now all we have to do here is rename this .rc file to that of the device you are porting to, e.g: "init.trout.rc" > "init.hero.rc"
Some devices ramdisk differ and may not contain "unvented.device.rc" so if this is case for you,then begin by renaming the init.device.rc to your model id and leave it at that. If you get problems well.. that's what the live support is for.
The other file which may be of use to us here is "init.rc", this contains all the system wide kernel properties which we can change to our liking but we'll leave as it is for now.
So now we've edited the ramdisk, we need to change the kernel so that the one the ROM uses is actually specific to our device, when we used the split_bootimg perl script it also unpacked the kernel and that is also in our current directory with the filename "boot.img-kernel".
Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
Okay, now that's all done, we need to pack this back up into something that android can understand when it's being flashed. So we need to make a new boot.img from the files we have in our current directory.
First, we need to pack the ramdisk back up into it's original state, so again we need to use the Linux terminal. The command that will do this is this:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Remember the ../ is the path to the directory of your ramdisk, remember to remove anything that won't be used by the kernel as cpio will include EVERYTHING in the working directory.
Okay now that the ramdisk is back in it's original format we need to repack the kernel and ramdisk into the boot.img.
So back into the terminal we go and this time we're going to use the "repack-bootimg" perl script (as if that wasn't obvious enough). The command you will ise here is esentially the same to the one we used to split it, so:
"perl repack-bootimg.pl ../path to kernel ../path to ramdisk directory ../path to outfile"
And the boot.img is complete!
So if we look back to the ROM we are porting we can see that we need to put the boot.img into the root of the zip, this will hold true for almost every Android ROM. Next we need to replace some of the files which allow the hardware and keys to work. This is the easy part.
Go into the root of the zip and follow this path to the kernel modules; "/system/lib/modules" Delete all the files you find here.
Now take the kernel modules which came along with the kernel you added to the boot.img and copy them there. Next follow this path to the propietary hardware files;
"/system/lib/hw" Delete all the files you find here.
Again this as simple as taking the files from a ROM meant for your device and copying them into this directory. So what we've done there is added the kernel modules that we can set symlinks to in the updater-script and contain the modules needed for things like WiFi, bluetooth etc. The "/hw" directory as you can see contains the files which control the sensors and lights such as GPS and the accelerometer.
Next, we can look at making sure the hard and soft keys work, the files which contain the layout of your device keys can be found in;
"/system/usr/keylayout" and "/system/usr/keychars"
Touch only those 2 directories.
Delete all the files in here and copy the ones from your device (following the same directory) here.
Okay now to finish off we need to copy over the mount point information for your device and the WiFi drivers.
Follow this path; "/system/etc" and delete only these files and directories.
- vold.fstab
- /wifi
- /ppp
Now follow the same path in a ROM for your device and copy over these files.
Okay we're done!
Before flashing take a look and some guides which show you how to write updater-scripts, incase you need to create important symbolic links.
Happy Porting!
**mod edit** credits to JieeHD from the VillainROM team for this guide! original thread here: http://www.freeyourandroid.com/guide/porting-android
reserved for future......
Hey,how did i help in this?
PS:i m thinking of buying this phone.....is it any good?
i have both the galaxy sl and spice mi 410 i copied from your thread so had to give you credit even though you are not the original poster
spice mi 410 competely outshines galaxy sl so much so that i hardly use sl hooked to this at i.6ghz its lightning fast great plays any game hardly random reboots though average camera galaxy sl better
side note :if you could build succh a nice rom with sl god knows what good you can do with mi 410 please buy it haha
cranium rocks
oh cool............i had forgotten about that thread
2nd hand for 9999 only.................
Hey that's my tutorial... Hope it helps someone....
Sent from my SAMSUNG-SGH-I777 using xda premium
rdannar said:
Hey that's my tutorial... Hope it helps someone....
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
than credit to you i am just sharing with everyone "hope it helps someone"
Thank you!!! Will try too port a gt-I9100 rom to a gt-I9100G.
Hope it will be easy with this guide.
Dear Preyesh1.... Could you add the credit to the creator of this guide or at least you mention the url source because I've seen this guide just exactly as in this thread somewhere in the internet.
Except if this guide is pure of yours.
Just to remind...
Edited: Never mind... The creator has been here after all...
I have some questions:
so this means you can take the U9000 android 2.2.2 kernel and merge with ICS?
or does this only works with kernel coming from a GB build to another GB build?
It will help me cause I'm gonna use it soon
Sent from my Triumph using XDA
ziggy46 said:
It will help me cause I'm gonna use it soon
Sent from my Triumph using XDA
Click to expand...
Click to collapse
Hey are you going to port your rom to your device this will be great...!!
I wanna try this great tutorial
Sent from my Droid using Tapatalk
Nice plagiarism.
I mean look at that OP. You've selected the entire article, hit copy, hit new post here, hit paste then hit submit. That's plagiarism of the laziest kind you could have at the very least put some effort in, formatted the text, used code blocks etc.
My word.
edit:
preyesh1 said:
See our guide on how to set this up HERE
Click to expand...
Click to collapse
Hahahahaha.
[TOOL] LGExtract 0.2.1 + 0.3.0 (beta)
Updated instructions will be here in post #1 or #2, stay alert
Description:
Hello everyone, in the last two weeks I was developing a command line tool to extract the firmware of LG phones. (different models)
For now, this tool is able to successfully extract *.kdz and *.wdb files. The tool don't dump the firmware from the phone.
I would like to receive feedback about this tool, if it works or not with the files you have.
Please report any kind of error too.
Remember, this software aims to help the community of users of mobile phones from LG to change their roms in a fast and easy way.
I can't provide any guarantee that the extracted file is 100% correct. So stay tuned in what you are doing, don't blame me.
Basic usage:
Open a command prompt. (cmd.exe or powershell)
Browse to the directory where is located the LGExtract.
Run LGExtract for more information (help).
Guides: (more detailed)
P920 / P970
P990 - Thanks Keltek
Other phone models have different files. I don't have any idea on how you can use it! BE CAREFUL!
Automated tools: (based on LGExtract)
LG-P970 ROM CONVERTER - Thanks jes0411 (if you are noob, this if for you )
Other tools: (to use with files extracted by LGExtract)
replace recovery
Current features:
Extract KDZ files.
Extract WDB files.
Features to be implemented:
Merge extracted files automatically. (if file needs it)
Graphical User Interface.
Extract DZ files.
(none of these, sorry, the development is dead)
Note: You don't need install any additional software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Click to expand...
Click to collapse
LGExtract.exe 0.2.1 - Hashes:
SHA-1: 2ef469162aa546ec7c1368d45bcbd0affd86e474
SHA-256: fa54a755a0aa2b15b622e44a183c491885a79ecf02d799c42c733e429dd16c3d
LGExtract.exe 0.3.0 BETA - Hashes:
SHA-1: e108c9e7d17b40d33152332d3e1775fd4aa48b92
SHA-256: ca66781f98498b80f59398a5c4538589262a1716d0788b18cea62e99c6eac5dc
Thanks to:
miniz - zlib compression
SimpleOpt - cmd line parser
Sephirothrx7 - for beta testing
Extracted KDZ/WDB from: (tested models)
KP500, KS360, LGP500, LGP920, LGP925 (confirmed by E:V:A)
LGP970, LGP990, LGP999, LU620128, SU640, SU660 (confirmed by kitty's_daddy)
Should work with any kdz/wdb file.
Changelog:
03/03/2020 - 0.3.0 BETA
* Fixed wdb password for larger dll files (up to 9.999.999 bytes).
(I was adding support for the DZ format, but I gave up, this tool seems no longer relevant.)
31/03/2012 - 0.2.1
* Improved error handling for kdz format.
* Fixed cryptographic service initialization failed.
28/03/2012 - 0.2.0
* Second release, extract wdb files.
26/03/2012 - 0.1.0
* Initial public release, extract kdz files.
Supported Operational Systems:
Windows:
Windows XP SP3 x86 (confirmed by kitty's_daddy)
Windows 7 SP1 x86/x64
Windows 8 x64 (confirmed by johnw230873)
Windows 8.1
Windows 10
Should work on other versions of Windows too.
Linux:
Red Hat Enterprise v6.2 x64 with Wine v1.4 i686 (Reported by Keltek)
Should work on other linux distributions too with Wine.
nothing happens when I try to run it, even if I put it in a same dir where a fw is.
What if you drag and drop over the app icon?
I'm not at my PC so i can't test this.
Trolling in the deep
Hi navossoc,
Just tried your tool - extracted V20o kdz to a cab file, containing lgp970.dll and v20o.wdb
1 suggestion / 1 question
- would be nice to have a graphical interface, instead of command line
- what to do with the wdb file ?
Ok, another tiny suggestion - how about trying teamwork with the other devs and create a super flash/backup tool, that can backup a phone via PC and flash stock/custom ROMs, while providing a choice of what packages from the ROM to flash
Congrats for the software
If this tool is only intended to extract .wdb file from .kdz it makes nothing new... I archieved this a lot of time ago but is useless.
Ilko said:
nothing happens when I try to run it, even if I put it in a same dir where a fw is.
Click to expand...
Click to collapse
Did you tried run something like:
LGExtract -kdz file.kdz
What is your operational system?
re4lsk said:
What if you drag and drop over the app icon?
I'm not at my PC so i can't test this.
Trolling in the deep
Click to expand...
Click to collapse
Yeah, it's on my plans, for now I wanna extend the support first.
megaurs said:
Hi navossoc,
Just tried your tool - extracted V20o kdz to a cab file, containing lgp970.dll and v20o.wdb
1 suggestion / 1 question
- would be nice to have a graphical interface, instead of command line
- what to do with the wdb file ?
Ok, another tiny suggestion - how about trying teamwork with the other devs and create a super flash/backup tool, that can backup a phone via PC and flash stock/custom ROMs, while providing a choice of what packages from the ROM to flash
Congrats for the software
Click to expand...
Click to collapse
1. I agree, I will in future.
2. If you extract wdb files you got the .bin and .cps file! Yeah!!!! You can flash it directly with smart flash tool.
Huexxx said:
If this tool is only intended to extract .wdb file from .kdz it makes nothing new... I archieved this a lot of time ago but is useless.
Click to expand...
Click to collapse
How can you say that? we can flash you p970 with smart flash tool as-is and root in seconds in with this tool (properly finished!)
I need go now, I will post more details later.
Who is having errors, please, more details, operational system?
[]'s
If that's correct, then I retire what I've said...
Can U extract .bin and .fls from .wdb file?
@navossoc
Look into my Mediafire ShareFolder maybe you`ll find some source code into those programs leaked from LG india website.
Huexxx said:
If that's correct, then I retire what I've said...
Can U extract .bin and .fls from .wdb file?
Click to expand...
Click to collapse
Yes, I have helped him to test the application and it was working properly.
Sent from my LG-P500h using Tapatalk 2 Beta-4
Ilko said:
nothing happens when I try to run it, even if I put it in a same dir where a fw is.
Click to expand...
Click to collapse
Not working on me eighter. When i want to open, it opens for just half a second and after that it dissapear.
You guys need to use command line. Open cmd and type: LGExtract -kdz "path to kdz file"
Did you try LG Utils ?
It can extract wdb and kdz both.
I'm having problem while extracting .wdb bcoz it asks for FW ver. and dont know which ver I have maybe someone else knows his FW ver so he'll be able to successfully extract wdb
omr911 said:
Did you try LG Utils ?
It can extract wdb and kdz both.
I'm having problem while extracting .wdb bcoz it asks for FW ver. and dont know which ver I have maybe someone else knows his FW ver so he'll be able to successfully extract wdb
Click to expand...
Click to collapse
LG utils cant extract the new wdb, even if you pass the correct fw version. The dll that come in the new kdz files dont have the needed functions that lg utils use. And the kp500 dll obvously cant be used to extract other wdb files.
Sent from my LG-P500h using Tapatalk 2 Beta-4
Huexxx said:
If that's correct, then I retire what I've said...
Can U extract .bin and .fls from .wdb file?
Click to expand...
Click to collapse
Yes, I can, but just as I said, I need a little more time to do all the error handling at the code. I don't wanna brick anyone phone.
I successful extracted the .wdb from LGP970 and got a .bin and a .fls file.
Then I used the SmartFlash Tool and flashed it at my phone. Works perfect.
The sha1 I got from the file was the exactly same as the "leaked" V10b-724-xxx bin/fls that we got available on the web.
I can extract any version, v10a, v10b, v20a, v20b, whatever
You can get any kdz from here and extract it to bin/fls.
Some phones has different file structures, but 920 and 970 has the same files bin/fls.
scamex said:
@navossoc
Look into my Mediafire ShareFolder maybe you`ll find some source code into those programs leaked from LG india website.
Click to expand...
Click to collapse
I will take a look, if you tell me the name of the file, I can find it quickly
Sephirothrx7 said:
Yes, I have helped him to test the application and it was working properly.
Sent from my LG-P500h using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Yeah, he was my test subject
Sephirothrx7 said:
You guys need to use command line. Open cmd and type: LGExtract -kdz "path to kdz file"
Click to expand...
Click to collapse
He is right, you can't run it with double click.
You need to open a console first (cmd.exe or power shell for ex.)
omr911 said:
Did you try LG Utils ?
It can extract wdb and kdz both.
I'm having problem while extracting .wdb bcoz it asks for FW ver. and dont know which ver I have maybe someone else knows his FW ver so he'll be able to successfully extract wdb
Click to expand...
Click to collapse
Yes, I already see LG Utils, I got the idea from there.
But, LG Utils can extract only KP500 and KS360.
I spent some time studing how they do that and I get it...
Now I can use the same idea in all .wdb files
For now it's useful for P920 and 970, because bin/fls can be flashed with SmartFlash Tool.
Others phones has different file structures, for example: LU620128 (I think P930) got a "firmware" file .tot with almost 1,3gb!
[]'s
I tried to extract using cmd but it only gives .cab (.wdb and .dll)
How to get bin/fls
Any tutorial ??
omr911 said:
I tried to extract using cmd but it only gives .cab (.wdb and .dll)
How to get bin/fls
Any tutorial ??
Click to expand...
Click to collapse
+1
how convert .wdb in .bin
what about adding a tutorial on how to use this tool? i already extracted the cab, but now i guess i can extract *.wdb from the cab then use the tool again to extract the bin/fls using: LGExtract -wdb *.wdbpath? is that correct?
nope it doesnt work that way
navossoc have already said that the tool is only extracting kdz for now, the wdb functionality is being revised so he can release a stable tool.
Today, I'm releasing version 0.1.0 of the software that extracts only files *.kdz
I will try release the WDB support as soon as possible, but first, I have to review the code. (I don't wanna brick anyones phone )
Click to expand...
Click to collapse
Sephirothrx7 said:
navossoc have already said that the tool is only extracting kdz for now, the wdb functionality is being revised so he can release a stable tool.
Click to expand...
Click to collapse
well extracting WDB works...
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.
Hey,
After a lot searching i have extract my .kdz file to 2 different files. a .dll and a .dz file. I am searching how can i get those files working in the Smartflashtool. Sow i need a app bin and a CP bin, On this moment i need to know how can i get those files?
- Can i extract a .kdz to a .wdb and .dll sow after that i can extract those to app bin and cp bin?
- Can i extract a .dz file after that compile it to .wdb and do the first step again?
- Is it possible to get from the .dz file also the app bin and the cp bin?
Wrong section sorry
Johrans said:
Hey,
After a lot searching i have extract my .kdz file to 2 different files. a .dll and a .dz file. I am searching how can i get those files working in the Smartflashtool. Sow i need a app bin and a CP bin, On this moment i need to know how can i get those files?
- Can i extract a .kdz to a .wdb and .dll sow after that i can extract those to app bin and cp bin?
- Can i extract a .dz file after that compile it to .wdb and do the first step again?
- Is it possible to get from the .dz file also the app bin and the cp bin?
Wrong section sorry
Click to expand...
Click to collapse
1)
kdz is a archive format, you can't choose what you get out of it. (It's like saying I want a image out of that random zip file)
Click to expand...
Click to collapse
2)
Ask novassoc He said some time ago he's working on dz files.
It should already be possible to extract dz file though, Check on the Optimus G forum.
I don't know to what it extracts possible bin/fls.
Click to expand...
Click to collapse
3)
Again I don't know to what it extracts and if or if not it's possible to revert to dz format. Should be possible.
Click to expand...
Click to collapse
I can give you lot more info about bin files if your interested, but you'd have to ask novassoc about kdz and wdb.
If dz decompiles to bin/fls then you should be able to create the dz file again, but after extracting the bin/fls file you should not create a bin/fls file again. It's possible, but it could kill your phone since emergency recovery usually relies on first or second stage bootloader and the bin/fls files overwrites it when flashing it on your phone and if something goes wrong.
xonar_ said:
1)
2)
3)
I can give you lot more info about bin files if your interested, but you'd have to ask novassoc about kdz and wdb.
If dz decompiles to bin/fls then you should be able to create the dz file again, but after extracting the bin/fls file you should not create a bin/fls file again. It's possible, but it could kill your phone since emergency recovery usually relies on first or second stage bootloader and the bin/fls files overwrites it when flashing it on your phone and if something goes wrong.
Click to expand...
Click to collapse
Thanks, Let we say we have the next files from different phones like the lg L5 e610 it has as firmware files a .dz and a .dll i know the .kdz files haves those files from those firmware. and also when it isnt a .kdz file its possible to encrypt it to .kdz
You know a lot about bin files. What contains a App.bin and a CP.bin when you use it for the SmartFlashTool. Because i wanne try to get from the Firmware files like ( .kdz or .dll or .dz) a app.bin and cp.bin,
Johrans said:
Thanks, Let we say we have the next files from different phones like the lg L5 e610 it has as firmware files a .dz and a .dll i know the .kdz files haves those files from those firmware. and also when it isnt a .kdz file its possible to encrypt it to .kdz
You know a lot about bin files. What contains a App.bin and a CP.bin when you use it for the SmartFlashTool. Because i wanne try to get from the Firmware files like ( .kdz or .dll or .dz) a app.bin and cp.bin,
Click to expand...
Click to collapse
Yes. There is already a tool somewhere to create kdz archive (One of LG's ones, you just have to use WindowsEnabler to get the option)
The bin file (AP) is basically a collection of data blocks and each data blocks usually correspond to partitions on the device.
The first meg is the header which contains the info about all the data blocks
like size on file,offset on file,size on device,offset on disk etc.
The layout of the header seems to be different for each phone. You can identify what type of bin file it is from it's magic number.
Then after the header the data blocks are just appended to the file. Doesn't have to be since the header allows there to be gaps and overlapping data blocks, but thats not practical so it will probably never be any other way.
You can check my tool for extracting bin files here. You can get alot more info on exactly how it's set out in my git by reading the sources.
I don't know to much about the fls file (CP) besides that it does a raw write of everything after what appears to be the header to somewhere in my phones nv partition and contains baseband information.
xonar_ said:
Yes. There is already a tool somewhere to create kdz archive (One of LG's ones, you just have to use WindowsEnabler to get the option)
The bin file (AP) is basically a collection of data blocks and each data blocks usually correspond to partitions on the device.
The first meg is the header which contains the info about all the data blocks
like size on file,offset on file,size on device,offset on disk etc.
The layout of the header seems to be different for each phone. You can identify what type of bin file it is from it's magic number.
Then after the header the data blocks are just appended to the file. Doesn't have to be since the header allows there to be gaps and overlapping data blocks, but thats not practical so it will probably never be any other way.
You can check my tool for extracting bin files here. You can get alot more info on exactly how it's set out in my git by reading the sources.
I don't know to much about the fls file (CP) besides that it does a raw write of everything after what appears to be the header to somewhere in my phones nv partition and contains baseband information.
Click to expand...
Click to collapse
Thanks, but still i am thinking why are there extractors for the kdz-> to cab -> to.wdb and .dll -> to App bin and CP bin but not from the kdz-> to cab -> .dz and .dll -> to App bin and CP bin.
is there sow big difference between the .dz and .wdb
I don't know much about what your talking here. I know that the complete firmware from LG comes in a v....kdz package. I know that ...cab containers are Microsoft's preferred format (something like ...zip or ...rar). I know ...bin stands for a lot BINary data files. I know that ...dll stands for Dynamic Data Library. That APPlications are often called app ...
... and I have the feeling that a lot different things are mixed together here. Sure xonar knows what he is talking about but the rest sounds like not much clue and the rest filled up with things you heard somewhere.
Sent from my LG-P970 using xda app-developers app
SaschaKH said:
I don't know much about what your talking here. I know that the complete firmware from LG comes in a v....kdz package. I know that ...cab containers are Microsoft's preferred format (something like ...zip or ...rar). I know ...bin stands for a lot BINary data files. I know that ...dll stands for Dynamic Data Library. That APPlications are often called app ...
... and I have the feeling that a lot different things are mixed together here. Sure xonar knows what he is talking about but the rest sounds like not much clue and the rest filled up with things you heard somewhere.
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Let me try to explain a litle for y.
You know that a kdz file contains a cab file. Every cab file contains a .dll file.
But not every cab file contains a wdb.
Sow what i need is a wdb file from a cab what doesnt have a wdb file. Or i need a extractor what makes from a .dz file and a .dll file a cp Bin and Ap bin. ( .dz file is the other file what could be in the cab without a .wdb,)
For some more information: When you use the SmartFlashTool. You need 2 files the CP Bin and AP bin.
You can use a extractor to get from a KDZ file a wdb and .dll file. ( From those its possible to create the CP Bin and AP bin)
But when you dont have de WDB file but you have a .DZ file then i cant create a CP bin and AP bin.
thats the problem. Sow now how can i fix that
Johrans said:
Let me try to explain a litle for y.
You know that a kdz file contains a cab file. Every cab file contains a .dll file.
But not every cab file contains a wdb.
Sow what i need is a wdb file from a cab what doesnt have a wdb file. Or i need a extractor what makes from a .dz file and a .dll file a cp Bin and Ap bin. ( .dz file is the other file what could be in the cab without a .wdb,)
For some more information: When you use the SmartFlashTool. You need 2 files the CP Bin and AP bin.
You can use a extractor to get from a KDZ file a wdb and .dll file. ( From those its possible to create the CP Bin and AP bin)
But when you dont have de WDB file but you have a .DZ file then i cant create a CP bin and AP bin.
thats the problem. Sow now how can i fix that
Click to expand...
Click to collapse
Have you tried
DZ-Creator / DZ-Decrypter
or
DZTools
If that fails then you have to reverse engineer your dz file yourself.
The DZ file can't be converted to bin/fls from the looks of it. That is if your dz file is similar to the dz file in the KS20.
That dz file is a collection of data blocks much like the bin file, but they aren't interchangable and I don't think SFT will work with them.
xonar_ said:
Have you tried
DZ-Creator / DZ-Decrypter
or
DZTools
If that fails then you have to reverse engineer your dz file yourself.
The DZ file can't be converted to bin/fls from the looks of it. That is if your dz file is similar to the dz file in the KS20.
That dz file is a collection of data blocks much like the bin file, but they aren't interchangable and I don't think SFT will work with them.
Click to expand...
Click to collapse
OKey sow if i understand this correctly is the .dz a kind of like the bin file. If i read correctly on this forum the wdb is also a collection off files like a zip file.
I think your are right it isnt possible to replace the .dz for a .wdb sow i can flash it in the SFT
Johrans said:
OKey sow if i understand this correctly is the .dz a kind of like the bin file. If i read correctly on this forum the wdb is also a collection off files like a zip file.
I think your are right it isnt possible to replace the .dz for a .wdb sow i can flash it in the SFT
Click to expand...
Click to collapse
Yes.
I don't think it's possible to flash dz file to your phone with SFT.
xonar_ said:
Yes.
I don't think it's possible to flash dz file to your phone with SFT.
Click to expand...
Click to collapse
Thanks for the answers, i know its possible with the kdz flasher but that tool isnt real stable and doesnt do a factory reset after the flash. it must be manual then.
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check
gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue
Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:
This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.
If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:
Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?