[Q] Help needed for merging of different MODs - Galaxy S III Q&A, Help & Troubleshooting

Hello all,
does somebody have a instruction/faq how to merge different MODs into onw ZIP.
Why? Because i am flashing round about 4 MODs after a Custom firmware update.
I want to Merge the following MODs:
- 12_headphone_shortcuts_mod_v0.1.zip
- Camera_HX-MOD_1.52_CWM.zip
- CWM_SecLauncher2_Mixed_5x5_5x6_SCR_on.ELKC.zip
- XXELLA SystemUI.zip
- SGS_3.zip (Picture for XXELLA SystemUI.zip
- Sihay Kernel
I have already taken a look into the ZIPs, but have a problem in understanding the structure of the ZIPs.
In some zips i have a different update-binary file.
The updater script is different to each other. Seems for me that this is the file with the commands which have to be used for updating process.
The Manifest.MF and CERT.SF file seams to have hashs of the files (SHA1-Digest). These differ from Zip to Zip even when the same filename is used.
Read here something about a signing of the Zip.
Is this need for/after merging the Zips?
Could somebody help me with the steps which have to be done to merge the Zips.
I want to learn how it has to be done. I donĀ“t want a ready to use Zip file.
I already searched for instructions but have not found a concrete instruction/faq for the merging of ZIPs.
Best regards
Jake555

PUSH

Related

Making CWM flashable files

I would like learning to make flashable files for executing various tasks.
For example:
- to move some files from for example sdcard to system directory and rewrite existing one
- to execute already made .zip file
And all that in one file...
Can you point me some good resources for this, and everything needed to know...
Thanks
TwinHeadedEagle said:
I would like learning to make flashable files for executing various tasks.
For example:
- to move some files from for example sdcard to system directory and rewrite existing one
- to execute already made .zip file
And all that in one file...
Can you point me some good resources for this, and everything needed to know...
Thanks
Click to expand...
Click to collapse
Here you go:
- [GUIDE] how to make a flashable package (update.zip)
- [GUIDE] How to make a cwm recovery flashable zip
And there should be even more resources. Use a Google search.

[Q][REQ]Porting roms among different devices

Hey there XDAians....
Can someone here point me to a walkthrough or tutorial on porting roms from and to devices of different manufacturers,resolution(mdpi,hdpi etc.) etc.I am familiar with the zip method of porting roms from same manufacturer(sony in my case,xperia U to Sola)but i want to know about porting roms from others like htc,samsung etc and Tools/apps needed to accomplish this.Most of the tutorials i found on XDA are based on the same method of zip porting.
Please help me with this,i really want to learn more about porting.
In the minimum, you must learn how to create a boot.img for your new device based on the boot.img (especially the ramdisk) from the old device.
To do this, you must extract the boot.img of your old device, edit the ramdisk (As there are lots of files named like the device, and those must be renamed to match the new device's name) Probably you must also change the content, to match the needs or to update references to some files, where the name changed.
After this, you can recreate the ramdisk.
Than extract a boot.img of your new device to get the kernel. Take the new Kernel and the new Ramdisk and make a new boot.img
Extracting and recreating a boot.img is described in the later part of this article: How to build a custom kernel
Recreating a ramdisk is described in this article: Create/Modify ramdisk
This might be the first step of a lot of steps...
Kind regards Uwe

How to generate update-binary for flashable zip?

Hi all, almost always after installing new CFW i have to delete annoying stock apps, so i think, that with flashable .zip that would be easier. I have created updater-script, but i need update-binary for it's work, right? So, anybody knows, how to generate it or smth? Thank you

[SOLVED] Build/development question - CM13 - missing ROM ZIP but imgs are built

I pulled the CM13 source from github and successfully completed a build. Set up all the tools, got the right java version set up, then did the actual build (envsetup, breakfast surnia, then used make) which took a few hours to complete.
However, I cannot seem to find the ZIP file which contains the flashable ROM. My build works well when I fastboot flash things (recovery, boot, cache and system). But I really would like to get a ZIP version of the ROM which can be ADB sideloaded.
I searched around and most of the posts I see related to this kind of stuff are old posts, and all of them indicate that the ZIP file will be created with the build. Is this not the case anymore? If not, can anyone help point me in the direction of how to make proper flashable zip created from a set of properly built .img files?
Asked too soon. Found how to get the zip file - ran "brunch surnia" instead of breakfast and a manual make, and now the ZIP file is generated.
You should try
make otapackage
Command instead of make surnia

How to use update-binary to change things?

The Pixel XL cannot use the typical TWRP flashable zip. It needs heavy modding.
I'm using Chainfire's TWRP flashable zip to do things to my phone.
But he doesn't use updater-script, he uses update-binary to make changes on the phone.
I need to edit the update-binary to copy some files to the phone, change their permissions and then also update the build.prop a little.
Could someone link me to a guide for editing update-binary to make changes to the phone?
I'm finding tons of info on updater-script but none of those mods work in update-binary.

Categories

Resources