Hi there,
How can i replace a base rom file while cooking my own rom? I want to replace the browser.dll, but not afterwards when the image is on my phone, i want to include it into my rom. My problem is after i build my own rom i got the "patched" browser.dll replaced by the original one.
I understand that i have a imageinfo.txt and imageinfo.bin along with the 5 files s000, s001, s002, s003, s004 and i guess the browser.dll is build from these files. But how can i generate those files or modify them to that my patched browser.dll is included into the cooked rom. Or isn't that possible at all?
regards,
nEUTRon
if browser.dll is a module (it's in a folder in the dump dir whose name is also browser.dll) then just remove the folder and replace it with your own dll.
The actual technique required to do this depends on the kitchen you're using. With Tadzio's tools, I simply remove the folder then move my new dll to the dump directory. Tadzio's tools rebuild imgfs from the dump dir and then merges it back into the XIP section.
Hi....I have the same problem....
What's wrong??
1) I split a .NBH to some .NB
2) Put in the same folder, Tadzio's Tools and OS.nb
3) Make the payload using the string "NBSplit -hermes OS.nb"
4) Make the imgfs.bin using the string "Imgfsfromnb OS.nb.payload imgfs.bin"
5) Extract all files to dumpfolder using the string "ImgfsToDump imgfs.bin"
Ok....now I would want to replace the "MsgStore.dll" and the "cespell.dll"....
Both are MODULEs (in the dump folder I have two folder named as, contain the dll e few other files)
So, I'll delete this two folder from Dump folder, and put in this my two DLL as they are
(note: original MsgStore size: 151 kb / My MsgStore size: 152 kb
note2: original cespell size: 7kb / My cespell size: 8 kb)
6) Make a new imgfs.bin using the string "ImgfsFromDump imgfs.bin imgfs-new.bin"
7) Make the new payload using the string "ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload"
8) Make the new OS.bin using the string "NBMerge -hermes os-new.nb"
What's WRONG ????
Tnks,
Hello all I tried to cook a rom with Kitchen program but I have a problem while checking the file Boot.img the program reports the following errors
Code:
Checking boot.img
Working Folder Found
Android 'magic' header not found at start of boot.img
Checking if it exists elsewhere...
Warning Android Header not found in boot.img ( unsupported format)
Kernel found at offset775040367 in boot.img
Making folder BOOT-EXTRACTED...
Extracted kernel
Error. Zimage is Emply!
Extracting ramdisk...
Error: No Ramdisk folder found!
Warning: init.rc not found in boot.img
I have tried flash the phone but the installation is aborted
Hi guys!
I have cooked my rom!
Deodexed - rooted and zipaligned!
I have tryed flash with recovery.. it's OK!
when the phone starts I get an error
"the application has stopped working "
what is the APK name of message?
How to solve this error?
I have Galaxy S3
Only thing I can suggest is grabbing a logcat and seeing what is crashing, you aren't giving a whole lot of info there.
how do I view the logcat?
After you have recorded it then just open it in a text editor.
Sent from my SCH-R760 using Tapatalk 2
how do i view logcat?
Click to expand...
Click to collapse
not sure if you ment how to open the logcat file
or how to actually get the logcat file.
heres how to get it.
use adb
best way to do it.
you need to have adb setup on your computer
connect device to computer
open terminal or cmd
Code:
adb
this will give you usage info about adb if not adb needs to be added to PATH
Code:
adb logcat -d > path/to/ desktop/logcat.txt
you can find market app that will save logcat to your sd card
if I remember correctly "alogcat"
This is my logcat
App "Message" crashed!
http://paste.ubuntu.com/1062350/
line 7777
Help please :'(
Did you remove CSC folder?
I never had a folder csc
Code:
[email protected]:~/Scrivania/ROM/WORKING_062512_024231/system$ ls
app cameradata framework media usr vsc
bin etc hdic preloaddata vendor wakeupdata
build.prop fonts lib tts voicebargeindata xbin
roxdragon said:
I never had a folder csc
Code:
[email protected]:~/Scrivania/ROM/WORKING_062512_024231/system$ ls
app cameradata framework media usr vsc
bin etc hdic preloaddata vendor wakeupdata
build.prop fonts lib tts voicebargeindata xbin
Click to expand...
Click to collapse
You didn't extract it , it's included on the "cache.img", we can work without it on sgs2 but it's a must on sgs3.
Code:
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous options / Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
Enter option: 0
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Add wireless tethering
6 - Zipalign all *.apk files to optimize RAM usage
7 - Change wipe status of ROM
8 - Change name of ROM
9 - Check update-script for errors
10 - Show working folder information
0 - ADVANCED OPTIONS
99 - Build ROM from working folder
u - Update/About kitchen
x - Exit
Enter option:
How to extract cache.img?
with kitchen?
i have execute this:
Code:
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
? s
----------------------------------------------------------------------
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)
Other formats:
Samsung Galaxy S:
- factoryfs.rfs + optional cache.rfs/zImage
- PDA.tar.md5 + optional CSC.tar.md5/PHONE.tar.md5
- PDA.tar + optional CSC.tar/PHONE.tar
- TAR/ZIP file containing factoryfs.rfs + more
- TAR/ZIP file containing PDA.tar.md5/PDA.tar + more
Samsung Galaxy S Plus:
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing system.img.ext4 + more
Samsung Galaxy SII:
- factoryfs.img + optional cache.img/zImage
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing factoryfs.img/system.img.ext4 + more
- system.ext4.tar + optional boot.img (Nandroid backup)
Huawei:
- APP file from Huawei software update (e.g. UPDATE.APP)
----------------------------------------------------------------------
Press Enter to continue, or type 'x' to abort:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_062712_171010
Change the name (y/n)? (default: n):
Creating working folder WORKING_062712_171010 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
"system.img" -> "../system.img.ext4"
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img successfully compiled
Converting system.img.ext4 into a format for unpacking ...
computed crc32 of 0xb9d9b0e7, expected 0x00000000
Mounting ext4_system.img to loopback device and then extracting files ...
..............
..........
...
N.B
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
into my original_update have:
Code:
[email protected]:~/Scrivania/ROM/original_update$ ls
boot.img cache.img hidden.img modem.bin recovery.img system.img
Can you help me please? Thank u
roxdragon said:
Code:
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous options / Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
Enter option: 0
============================================================
Android Kitchen 0.196 - by dsixda (xda-developers.com)
============================================================
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Add wireless tethering
6 - Zipalign all *.apk files to optimize RAM usage
7 - Change wipe status of ROM
8 - Change name of ROM
9 - Check update-script for errors
10 - Show working folder information
0 - ADVANCED OPTIONS
99 - Build ROM from working folder
u - Update/About kitchen
x - Exit
Enter option:
How to extract cache.img?
with kitchen?
i have execute this:
Code:
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
? s
----------------------------------------------------------------------
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)
Other formats:
Samsung Galaxy S:
- factoryfs.rfs + optional cache.rfs/zImage
- PDA.tar.md5 + optional CSC.tar.md5/PHONE.tar.md5
- PDA.tar + optional CSC.tar/PHONE.tar
- TAR/ZIP file containing factoryfs.rfs + more
- TAR/ZIP file containing PDA.tar.md5/PDA.tar + more
Samsung Galaxy S Plus:
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing system.img.ext4 + more
Samsung Galaxy SII:
- factoryfs.img + optional cache.img/zImage
- system.img.ext4 + optional cache.img.ext4/boot.img
- TAR/ZIP file containing factoryfs.img/system.img.ext4 + more
- system.ext4.tar + optional boot.img (Nandroid backup)
Huawei:
- APP file from Huawei software update (e.g. UPDATE.APP)
----------------------------------------------------------------------
Press Enter to continue, or type 'x' to abort:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_062712_171010
Change the name (y/n)? (default: n):
Creating working folder WORKING_062712_171010 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
"system.img" -> "../system.img.ext4"
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
Analyzing system.img.ext4 ...
Compiling simg2img ...
simg2img successfully compiled
Converting system.img.ext4 into a format for unpacking ...
computed crc32 of 0xb9d9b0e7, expected 0x00000000
Mounting ext4_system.img to loopback device and then extracting files ...
..............
..........
...
N.B
Code:
Warning: No cache.img.ext4 found. You can unpack this file separately
by running the plugin script in the kitchen's Advanced menu options.
If your device doesn't use a CSC, then just ignore this message.
into my original_update have:
Code:
[email protected]:~/Scrivania/ROM/original_update$ ls
boot.img cache.img hidden.img modem.bin recovery.img system.img
Can you help me please? Thank u
Click to expand...
Click to collapse
Use "24" option on Advanced options then "Extract_SGS2_CSC_from_cache.img", i think cache.img must be the root working folder, it will convert it to ext, then follow the displayed steps.
wanam said:
Use "24" option on Advanced options then "Extract_SGS2_CSC_from_cache.img", i think cache.img must be the root working folder, it will convert it to ext, then follow the displayed steps.
Click to expand...
Click to collapse
Code:
PLUGIN SCRIPTS
--------------------------------------
(1) Extract_SGS_CSC_from_cache.rfs
(2) Decompile_and_Compile_Deodexed_File
(3) Install_SGS2_CWM_Manager
(4) Batch_Deodex
(5) Sample
(6) Extract_SGS2_Kernel_Initramfs
(7) ReadMe
(8) Extract_SGS2_CSC_from_cache.img
--------------------------------------
0 - Exit r - Refresh list
Enter an option: 8
Samsung Galaxy S2 CSC Extractor
-------------------------------
This script will extract the CSC (Customer Software Customization)
from the cache.img of a stock Samsung Galaxy S2 firmware. The CSC
comes in a file called 'sec_csc.zip' which contains location and
carrier-specific configurations and software.
Proceed (y/n)? (default: y):
Creating folder /home/gianni/Scrivania/ROM/csc_062712_205036 ...
---> Place stock cache.img or cache.img.ext4 into the folder mentioned above <--
Press Enter to continue
Compiling simg2img ...
simg2img successfully compiled
Unpacking cache.img into a format for unpacking ...
computed crc32 of 0x20453d0a, expected 0x00000000
Mounting ext4_cache.img to loopback device and then extracting files ...
[sudo] password for gianni:
Finished! Your file is at csc_062712_205036/sec_csc.zip.
You can unzip this file and copy the contents of the 'system'
folder to your ROM's system folder.
I have a package "sec_csc.zip"
I have extracted sec_csc.zip and i have into *.zip
META-INF
system
i need copy all files into system to /WORKING_FOLDER/system? and META-INF?
now??
Solved thank u
Another quesyion..
How to remove default app during installation of custom rom?
MyTaxy.apk, videohub, rhs hotel .... etc...?
Sent from my GT-I9300 using xda app-developers app
hello
i want to create custom boot image.i am using cygwin bash shell and android kitchen.
i extract boot.img with Android Kitchen 0.194 Tools for boot images <unpack/re-pack/etc.>
it show like this
Working folder found
Kernal found at offset 2048 in boot.img
Making folder BOOT-EXTRACTED ....
Extracting kernal ...
Extracting ramdisk ...
Error : NO ramdisk folder found!
Press Enter to counting
How i solve Error:NO ramdisk folder found.
Are you have trouble extracting from the phone or extracting the .img file into something editable? I see at the top of the first page here that there is an update to the Kitchen. Maybe the newer version supports your phone better?
Hello,
I was searching the web to get a solution to extract KDZ LG G3 firmware and finally I got a way to achieve it properly and easily and am sahring with the community.
1st of all thks and credits for @thecubed and @bullghost
all credits to @thecubed for the KDZ Tools here : http://forum.xda-developers.com/showthread.php?p=46458839
WHAT YOU NEED
- Python 2.7 : https://www.python.org/download/releases/2.7/
- Modified PY tool scripts (KDZ Tools) : http://downloads.codefi.re/thecubed/androidtools/Compressed_KDZUtils.zip
HOW TO DO IT
Extract the downloaded file (G3_KDZ_Extractor.rar)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1- Install Python27 (run python-2.7.msi)
2- Copy both PY files (scripts) to "C:\Python27"
Copy your KDZ file to "C:\Python27"
3- Open Command prompt (cmd) and run the following commands
cd C:\Python27
python.exe KDZFileTools.py -f D85510L_00.kdz -s 0
Click to expand...
Click to collapse
After running the command you should see somthing like this
Wait for a moment and it is done.
Now, go to "C:\Python27" a new folder named "kdzextracted" is created : the DZ and the DLL file are extracted there.
4- Use the LG G2 tool by bullghost to extract the DZ file normally : http://forum.xda-developers.com/showthread.php?t=2600575
Great work man. Thanks
Ha! G8!
Thank you so much! I tried following the guides in the various threads but for someone with 0 Python knowledge I couldn't seem to get anywhere useful. This is a great step by step guide, will be trying it tonight with my v10L KDZ.
Thanks again!
S3V3N said:
Ha! G8!
Click to expand...
Click to collapse
CHeck PM plz
to avoid getting that error you have in your image just need to add -s 0 and it will on extract the .dz file
after that you can use the dztool.py to extract the partitions.
I.E
:~$ python KDZFileTools.py -f D85510L_00.kdz -s 0
[+] Extracting single partition!
[+] Extracting D85510l_00.dz to kdzextracted/D85510l_00.dz
[email protected]:~$
~/kdzextracted$ python ../DZFileTools.py -f D85510l_00.dz -x
[+] Extracting all partitions!
[+] Extracting PrimaryGPT_0.bin to dzextracted/PrimaryGPT_0.bin
[+] Extracting modem_32768.bin to dzextracted/modem_32768.bin
[+] Extracting sbl1_163840.bin to dzextracted/sbl1_163840.bin
[+] Extracting dbi_165888.bin to dzextracted/dbi_165888.bin
[+] Extracting aboot_167936.bin to dzextracted/aboot_167936.bin
[+] Extracting rpm_172032.bin to dzextracted/rpm_172032.bin
[+] Extracting tz_174080.bin to dzextracted/tz_174080.bin
[+] Extracting boot_196608.bin to dzextracted/boot_196608.bin
[+] Extracting persist_229376.bin to dzextracted/persist_229376.bin
[+] Extracting recovery_294912.bin to dzextracted/recovery_294912.bin
[+] Extracting rct_350224.bin to dzextracted/rct_350224.bin
[+] Extracting laf_393216.bin to dzextracted/laf_393216.bin
[+] Extracting factory_655360.bin to dzextracted/factory_655360.bin
[+] Extracting system_720896.bin to dzextracted/system_720896.bin
[+] Extracting system_984136.bin to dzextracted/system_984136.bin
[+] Extracting system_1249088.bin to dzextracted/system_1249088.bin
[+] Extracting system_1508424.bin to dzextracted/system_1508424.bin
[+] Extracting system_1512328.bin to dzextracted/system_1512328.bin
[+] Extracting system_1773376.bin to dzextracted/system_1773376.bin
[+] Extracting system_2032712.bin to dzextracted/system_2032712.bin
[+] Extracting system_2036616.bin to dzextracted/system_2036616.bin
[+] Extracting system_2297664.bin to dzextracted/system_2297664.bin
[+] Extracting system_2557000.bin to dzextracted/system_2557000.bin
[+] Extracting system_2560904.bin to dzextracted/system_2560904.bin
u[+] Extracting system_2821952.bin to dzextracted/system_2821952.bin
[+] Extracting system_3081288.bin to dzextracted/system_3081288.bin
[+] Extracting system_3085192.bin to dzextracted/system_3085192.bin
[+] Extracting system_3346240.bin to dzextracted/system_3346240.bin
[+] Extracting system_3608384.bin to dzextracted/system_3608384.bin
[+] Extracting system_3870528.bin to dzextracted/system_3870528.bin
[+] Extracting system_4132672.bin to dzextracted/system_4132672.bin
[+] Extracting system_4390912.bin to dzextracted/system_4390912.bin
[+] Extracting system_4653056.bin to dzextracted/system_4653056.bin
[+] Extracting system_4915200.bin to dzextracted/system_4915200.bin
[+] Extracting cust_6193152.bin to dzextracted/cust_6193152.bin
[+] Extracting cust_6455296.bin to dzextracted/cust_6455296.bin
[+] Extracting cust_6459544.bin to dzextracted/cust_6459544.bin
[+] Extracting BackupGPT_30776320.bin to dzextracted/BackupGPT_30776320.bin
and voila! u got your partitions
roniez said:
to avoid getting that error you have in your image just need to add -s 0 and it will on extract the .dz file
after that you can use the dztool.py to extract the partitions.
I.E
:~$ python KDZFileTools.py -f D85510L_00.kdz -s 0
[+] Extracting single partition!
[+] Extracting D85510l_00.dz to kdzextracted/D85510l_00.dz
[email protected]:~$
~/kdzextracted$ python ../DZFileTools.py -f D85510l_00.dz -x
[+] Extracting all partitions!
[+] Extracting PrimaryGPT_0.bin to dzextracted/PrimaryGPT_0.bin
[+] Extracting modem_32768.bin to dzextracted/modem_32768.bin
[+] Extracting sbl1_163840.bin to dzextracted/sbl1_163840.bin
[+] Extracting dbi_165888.bin to dzextracted/dbi_165888.bin
[+] Extracting aboot_167936.bin to dzextracted/aboot_167936.bin
[+] Extracting rpm_172032.bin to dzextracted/rpm_172032.bin
[+] Extracting tz_174080.bin to dzextracted/tz_174080.bin
[+] Extracting boot_196608.bin to dzextracted/boot_196608.bin
[+] Extracting persist_229376.bin to dzextracted/persist_229376.bin
[+] Extracting recovery_294912.bin to dzextracted/recovery_294912.bin
[+] Extracting rct_350224.bin to dzextracted/rct_350224.bin
[+] Extracting laf_393216.bin to dzextracted/laf_393216.bin
[+] Extracting factory_655360.bin to dzextracted/factory_655360.bin
[+] Extracting system_720896.bin to dzextracted/system_720896.bin
[+] Extracting system_984136.bin to dzextracted/system_984136.bin
[+] Extracting system_1249088.bin to dzextracted/system_1249088.bin
[+] Extracting system_1508424.bin to dzextracted/system_1508424.bin
[+] Extracting system_1512328.bin to dzextracted/system_1512328.bin
[+] Extracting system_1773376.bin to dzextracted/system_1773376.bin
[+] Extracting system_2032712.bin to dzextracted/system_2032712.bin
[+] Extracting system_2036616.bin to dzextracted/system_2036616.bin
[+] Extracting system_2297664.bin to dzextracted/system_2297664.bin
[+] Extracting system_2557000.bin to dzextracted/system_2557000.bin
[+] Extracting system_2560904.bin to dzextracted/system_2560904.bin
u[+] Extracting system_2821952.bin to dzextracted/system_2821952.bin
[+] Extracting system_3081288.bin to dzextracted/system_3081288.bin
[+] Extracting system_3085192.bin to dzextracted/system_3085192.bin
[+] Extracting system_3346240.bin to dzextracted/system_3346240.bin
[+] Extracting system_3608384.bin to dzextracted/system_3608384.bin
[+] Extracting system_3870528.bin to dzextracted/system_3870528.bin
[+] Extracting system_4132672.bin to dzextracted/system_4132672.bin
[+] Extracting system_4390912.bin to dzextracted/system_4390912.bin
[+] Extracting system_4653056.bin to dzextracted/system_4653056.bin
[+] Extracting system_4915200.bin to dzextracted/system_4915200.bin
[+] Extracting cust_6193152.bin to dzextracted/cust_6193152.bin
[+] Extracting cust_6455296.bin to dzextracted/cust_6455296.bin
[+] Extracting cust_6459544.bin to dzextracted/cust_6459544.bin
[+] Extracting BackupGPT_30776320.bin to dzextracted/BackupGPT_30776320.bin
and voila! u got your partitions
Click to expand...
Click to collapse
thks for this mate
why don't you use
WindowsLGFirmwareExtract
to extract kdz ?
and more important thing is
when we try to flash dz it wont flash
is there any themplate to create flashable zip ?
mlm1102003 said:
why don't you use
WindowsLGFirmwareExtract
to extract kdz ?
and more important thing is
when we try to flash dz it wont flash
is there any themplate to create flashable zip ?
Click to expand...
Click to collapse
why you need to flash DZ file when u have the KDZ :s
LGFirmwareExtract dont work with G3 KDZ files but it works fine with G2 KDZ files
ahmed534 said:
why you need to flash DZ file when u have the KDZ :s
LGFirmwareExtract dont work with G3 KDZ files but it works fine with G2 KDZ files
Click to expand...
Click to collapse
so after all
whats the point of the extracting ?
when we cannt flash dz (and there is not any themplate for making flashable zip ?)
mlm1102003 said:
so after all
whats the point of the extracting ?
when we cannt flash dz (and there is not any themplate for making flashable zip ?)
Click to expand...
Click to collapse
it is for extracting the partitions mate !
mlm1102003 said:
so after all
whats the point of the extracting ?
when we cannt flash dz (and there is not any themplate for making flashable zip ?)
Click to expand...
Click to collapse
ahmed534 said:
it is for extracting the partitions mate !
Click to expand...
Click to collapse
We can actually make flashable zips out of the extracted files using flash2 posted by Autoprime, which actually includes all this tools to extract kdz...
The G2 extraction tool with ui will work after extracting the dz and we can get system.img out of it... =)
Edit: There was actually another guide on the general section, but it's on the middle page closer to last page maybe, was posted long ago... =)
mlm1102003 said:
so after all
whats the point of the extracting ?
when we cannt flash dz (and there is not any themplate for making flashable zip ?)
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
Manual OTA updates, in a word.
Split KDZ, split partitions of DZ, merge system partitions to make system.img/boot/.img/modem.img, then flash using FLASH2 files (from codefire) via TWRP (via Bump)
Ok, so I've done all of this. I'm getting only system.img after using WindowsLGFirmwareExtract. How do I get modem.img, is it simply a matter of renaming the modem*.bin to img?
Furthermore, is the generated system.img supposed to be approx. 2,5Gb in size?
thanks
i hope its work for other lg's kdz files
ahmed534 said:
Hello,
I was searching the web to get a solution to extract KDZ LG G3 firmware and finally I got a way to achieve it properly and easily and am sahring with the community.
1st of all thks and credits for @thecubed and @bullghost
Click to expand...
Click to collapse
Hi, please link to the Compressed KDZ File Tools thread where this came from.
As found in the header of the KDZ tools:
"""
KDZ File tools
by IOMonster (thecubed on XDA)
Please do not distribute without permission from the author of this software.
"""
Please do not redistribute the KDZ tools in your own package. They are already linked on Codefire please direct people there or to the original thread to download those.
Also, please fix screenshot/directions to use proper KDZFileTools.py command:
python KDZFileTools.py -f D85510L_00.kdz -s 0 (on OSX/Linux) or.. python.exe KDZFileTools.py -f D85510L_00.kdz -s 0 (on Windows)
-x is not used with the KDZFileTools.py .. it is used in the DZFileTools.py script when extracting the DZ into individual partitions:
python.exe DZFileTools.py -f kdzextracted/D85510l_00.dz -x for example.
All of these directions.. along with directions for merging the system files can be found in my manual update thread here.
Tolukolvi said:
Ok, so I've done all of this. I'm getting only system.img after using WindowsLGFirmwareExtract. How do I get modem.img, is it simply a matter of renaming the modem*.bin to img?
Furthermore, is the generated system.img supposed to be approx. 2,5Gb in size?
Click to expand...
Click to collapse
Yes, you can just rename *.bin to *.img. And yes, 2.5GB or so is about right for System partitions. Full size of System on your phone is about 3GB.
mlm1102003 said:
so after all
whats the point of the extracting ?
when we cannot flash dz (and there is not any template for making flashable zip ?)
Click to expand...
Click to collapse
no need to make any flashable zips! I have made zip files that easily flash untouched system.img, boot.img(kernel), and modem.img files... simply place my pre-made flash2 zip files on your sdcard along with the .img files and flash away. No need to repack zip files or create a flashable zip each time. My flash2 zips will work with any system, boot, or modem.img file you place on your /sdcard.
Check out my thread here - http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
The reason for promoting updating manually is to preserve root and Bump ability... in case LG tries to patch something in the future. New root methods are not likely to be made after Stump and PurpleDrake are patched... and depending on what LG does in the future with the bootloader updates... Bump could possibly be blocked forever.
Yes! This does indeed work. Took about 6-7 minutes to flash the system, but worked out just as the doctor ordered.
@autoprime thks mate for clarifying this. didnt knew it was codefire team scripts, I got them from a MEGA link I found on the net ! anyway I updated OP with new links and credits.
thks
ahmed534 said:
@autoprime thks mate for clarifying this. didnt knew it was codefire team scripts, I got them from a MEGA link I found on the net ! anyway I updated OP with new links and credits.
thks
Click to expand...
Click to collapse
All of which in his manual update thread as I mentioned in previous post... =)
Okay, so I've got my boot.img, modem.img and system.img, safe to flash all 3 using the FLASH2 stuff from Codefire? I've got a TWRP backup - will I loose anything/data/settings by flashing system.img or does it just update it?