Related
HI,
I am trying to get an apk from a KDZ file. I can open up the KDZ but then there are many other files inside. I guess the apks are in one of these other files. Does anyone know how to get the apk from within .img files etc?
Thanks
ballandbiscuit said:
HI,
I am trying to get an apk from a KDZ file. I can open up the KDZ but then there are many other files inside. I guess the apks are in one of these other files. Does anyone know how to get the apk from within .img files etc?
Thanks
Click to expand...
Click to collapse
How you extracted KDZ?
Why don't you get it from the sapps module zip on void's rom?
I need a particular app from the Orange UK ROM - the app is called Signal Boost and it is for UMA calling.
Is that app in the ROM you mention?
What you need is this: http://forum.xda-developers.com/showpost.php?p=6303911&postcount=827
It allows you to decompress system.mbn (where all the files are).
Compile it under linux, or use cygwin.
Remember that official ROMs are odexed. If you want to deodex apks, you can use dsixda's excelent kitchen. It is used to make lots of ROMs you see around here.
For that, take a look here (you can also use it under cygwin):
http://forum.xda-developers.com/showthread.php?t=633246
If you understand portuguese, or use a translator, check these:
http://www.androidpt.com/index.php?option=com_kunena&func=view&catid=97&id=91547&Itemid=30
http://www.androidpt.com/index.php?option=com_kunena&func=view&catid=97&id=97416&Itemid=30
Most info was gathered from xda forums, only translated and organized to portuguese folks.
Many thanks, I will see if I can get anywhere with this.
You just need to compile unyaffsmbn (gcc unyaffsmbn.c -o unyaffsmbn).
Then copy system.mbn to unyaffsmbn folder. Then do:
./unyaffsmbn system.mbn
You'll have all files extracted in few seconds.
Then if you want to use those files in kitchen, do this:
First install kitchen, as explained in link i posted above.
Delete all symlinks in bin/ (i think there are 52)
Then you must create a zip file with this structure:
/boot.img
/system/ (here you put all the files you extracted. You should have 10 folders and 1 file)
Now just copy this zip to PATH_TO_KITCHEN/original_update/
Then run it with:
cd PATH_TO_KITCHEN
./menu
Right I have three system.mbn files named:
system.mbn_0
system.mbn_1
system.mbn_2
I have tried a few tools (under Windows) to extract them. Firstly a windows compiled version of unyaffs which falls over with : Exception: STATUS_ACCESS_VIOLATION at eip=61100F73
I then tried another version which didn't error but also didn't do anything!
A different tool errored with "the header states that its binary is longer than the whole file" which makes me think perhaps these three files need combining into one?
I have tried combining them into one file using the copy /b command in Windows which creates a single large file but I still have the same issues trying to unpack it.
Any more ideas? Thanks
Right have now installed Cygwin and managed to extract the files using unyaffsmbn! Thanks for all your help, learnt a lot today!
Right I have three system.mbn files named:
system.mbn_0
system.mbn_1
system.mbn_2
Click to expand...
Click to collapse
How did you decompress kdz? I use LG Utils to extract to dz, then dzdecryptor to decompress dz to individual files. Then i use the tools i named to do the rest of it.
Also i can see that lg utils finds those system*, but puts them together before it ends. Maybe you used different software.
Anyway, i'm glad you managed to work it out
I have tried a few tools (under Windows) to extract them. Firstly a windows compiled version of unyaffs which falls over with : Exception: STATUS_ACCESS_VIOLATION at eip=61100F73
Click to expand...
Click to collapse
There is unyaffs, and unyaffsmbn. unyaffs also never worked with me.
I've read somewhere that with lg roms we must use unyaffsmbn. Don't remember were i saw it, neither why...
I used LG utils to extract the KDZ, then used DZExtract to expand the .dz file. Then I combined the system.mbn_0,1,2 files using copy /b.
I then used Cygwin and gcc to make unyaffsmbn.exe which then worked on the combined system.mbn file. Managed to get the apk I needed too.
PLease upload unyaffsmbn.exe for me please as i seriously need it.
Here you go...
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.
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.
Hello,
I search to unpack the boot.img to change files but impossible, I tested all, no program can unpack ... could you pleased help me ?
Thank you in advance.
The RAZR I one? Look in the development section. It will extract it very easy.
Sent from my XT890 using xda app-developers app
I don't find thé hex dump tool ans didn't understand the tuto..
Search in the dev section for:
Unpacking RAZR I boot.IMG from turl.
Our boot image isn't the same as others. There is no way u can extract things without the needed files. If u can't do anything with the topic about the boot.IMG in the dev section, I can't help u.
Sent from my GT-P5110 using XDA Premium HD app
I have find this.. But i don't understand what is the ''tool'' when you use...
can you give me all the URL of files and tool and... For editing the boot.img please ?
Thank's..
Up...
The only way (as far as i know) to unpack a boot.img from the Razr I is to use an linux powered PC. The tools in the topic that are provided need to be build first. And for it to build u need a linux (ubuntu) operating system. I will upload (when i have the time) my tools to unpack and repack the boot.img with a description on how to use them, but they only work on linux.
p.s. don't bump the post if it isn't answered in 1 day. Sometimes someone that will reply isn't online or is doing other things and didn't noticed it. If it were 3 or more days, oke. Just my opinion
Hazou
Bootimage tools
Here u go. My bootimage extract and pack package. It only works on linux. See the zip, and extract it somewhere in your linux distribution.
Instructions:
1. Put a boot.img in the root of the extracted bootimage packages (where the folders Ramdisk, Bootimage, Kernel, Tools are)
2. Execute the file extract.
3. Kernel can be found under the map kernel
4. Ramdisk can be found under the map Ramdisk/ramdisk
5. Modify your things
6. Pack the files by executing create.
Notes:
In the map Bootimage is a bootstub (bootold.img) needed for rebuilding the boot.img and some old scripts
In the map Kernel will be the extracted kernel. The file bzImage will always be used for rebuilding.
In the map Ramdisk will be the extracted ramdisk in the map ramdisk. The map 'ramdisk' will always be used for rebuilding,
In the map Tools will be the tools needed for extracting and creating.
If u have some questions about this tool, ask!
Credits to Turl1 for the tools
Hazou
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
eliotargy said:
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Can anyone advise me further?
Click to expand...
Click to collapse
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Snowby123 said:
Usually the file is corrupted if the file comes from an incomplete download. Try downloading a new file before a retry
Click to expand...
Click to collapse
My other implied question was: Did I do everything right?
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
search for lz4 on either xda or google.
( you need to unpack it)
eliotargy said:
I'm trying to install Magisk through the patched method on my N9600. So far I have
1. Downloaded stock ROM
2. Renamed AP file to .tar
3. Extracted with WinRar
4. Located the boot.img.lz4 file
I then tried to extract that with WinRar and got a message saying file was corrupted.
Is the file really corrupted? Becaus eI have in fact flashed my Note 9 via Odin with that particular stock ROM. Can anyone advise me further?
Click to expand...
Click to collapse
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Why are you trying to patch? Please follow my guide for rooting the N9600.
christis said:
Hey friend, did you manage to accomplish this? Do you still trip the knox this way? I am just about to try it on a brand new Note 9, with no previous Samsung rooting experience.
Thanks
Click to expand...
Click to collapse
No luck. Also no response to my post.
zxzxzxzxzxzxzxzxzx said:
Why are you trying to patch? Please follow my guide for rooting the N9600.
Click to expand...
Click to collapse
Where is your guide?
Again, where is your guide that you speak of?
eliotargy said:
No luck. Also no response to my post.
Click to expand...
Click to collapse
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
christis said:
I see. In the meantime I have managed to succeed. Rooted an N960F/D with patching the boot image. I know the N9600 is a different beast, but this is NOT a root guide!!!!!!!!.
For step #5, Winrar is no good. You have to use lz4, but is a pain. Personally I used a special version of 7z which includes lz4 codec and is easier and very usefull in all the steps. The link is
https://github.com/mcmilk/7-Zip-zstd/releases (choose x64 or x86 depending on your Windows version).
After this, I cannot remember the exact steps. As far as I can racall, I think I patched it with Magisk (follow the Magisk guide) first, and then I had to retrieve the patched image and compress it again (to .tar???) with the same version of 7z.
7z itself can fully replace Winrar in the whole process. In the initial firmware zip file extraction, in the extraction of the AP md5 file (no renaming necessary), in lz4 extraction of the boot file, and finally in the patched img file compression back to tar. One for all tool (use the 7zFM (file manager) shortcut and the Add or Extract buttons).
And to answer my own question: Finallly, in order to install the final patched boot image via Odin, the bootloader HAS to be unlocked, so Knox is tripped anyway. No problem for me though, since I managed to run SHealth, Gpay and Spay (the latter via the phone - watch (Gear S) connection though, not as a stand-alone). And I ensured that where I live, it is not going to affect my warranty as long as is a hardware problem.
CAUTION: That was for N960F/D and is NOT a root guide anyway.
Click to expand...
Click to collapse
Mine falls at patching with Magisk. N9600.