I am making a ROM for personal use(I probably won't release it). I want to integrate the LagFree script into it...I don't think it's just a matter of copying the script from one zip to another, since there is the META-INF folder that contains updater-script and such...how do I integrate the script into my ROM?
If you want to modify The updater-script use notepad++ and change whatever you want in it beside phone info of course
Related
Hi,
I have a ROM, for example Enomther's. and I also have the arabic language libs. how can I integrate the arabic libs into the ROM's zip file so I don't have to flash another zip for arabic libs? I have attached the arabic libs.
Bump! anyone?
Come on, what kind of answer do you expect?
Here's the answer: you need to substitute the files in the original ROM zip and resign it - that's it.
Now you're going to ask, how to do it, because you have no clue - and the explanation is a lot of work to try and put in one post, and setting up signing applications involves installing Java SDK and some knowledge. If you're asking the question you're asking - it seems like you're far from being skilled enough in Android depths to do what you're asking to do, and that's why you see no answer. After all, if you'd want to do it - you'd have to search anyway, Google "sign apk zip" and here you go, a lot of tutorials show up. And if you didn't search and posted instead - it speaks for itself.
By the way, there's no good reason to integrate the libs into a standard ROM, moreover - it's a bad idea. ROMs tend to be updated, and the work that needs to be done setting up the environment for signing APKs and ZIPs is way more than flashing one update right after updating the ROM to a newer version. And ROMs are updated quite often.
Yeah i'm not skilled. I'm trying to learn... I am trying to make my own customized ROM for my country's users. And I didn't mean editing ROM files, I was saying how to push the lib into the ROM zip so people don't have to flash the arabic zip lib when they flash my customized ROM. So I hope you haven't missunderstood my question...
Ah, I see, you want to customize and share the ROM. In that case, you have to have the setup I'm talking about. The update.zip contains folders and files, which directly replace the files in the same folders in ROM, so if you have a ROM zip - you need to replace those files. The easiest way would be just extracting your update.zip, opening a ROM zip in 7zip / WinZip / WinRar / etc, putting those extracted files from update.zip in the right place into ROM zip by drag-and-drop, and then resigning the ROM file.
Please do some googling as to how to sign ZIP and APK files. There are some pretty good tutorials.
I have done that before, and I replaced the lib file with the ROM default lib. it's libskia.so, but I think because I didn't know I have to sign it it gave me an error while flashing through recovery. so after I replace the lib I have to re-compress the file and then sign the zip right?
You don't have to re-compress if you replace the file without decompressing the original ROM archive, by dragging-and-dropping the file into the archive.
And yes, you have to re-sign the ZIP after any changes you make to anything inside it.
Did anyone has tried the dsixda Android Kitchen to make a custom rom for OB ? Is it working ?
http://forum.xda-developers.com/showthread.php?t=633246
or just give me a link to very helpful site about how to make custom rom for OB
For starters, yes it works. but nothing compares as to compiling and building from source (Linux).
What you need is a mere system dump or backup from CWM.
That backup will be saved in your CWM folder in SD
Grab the boot.img & system.ext3.tar
unpack the .tar with a zip/RAR propgram
grab a base upater script from the many ROMs around here
Now for a start:
your base ROM like Zeus etc.
Delete the system folder and boot.img from that zip.
Replace files.
Use dsixda kitchen via cygwin (windows)
Now do as you please... it can unpack boot.img and add features like init.d etc.
Adding apps:
Apps can be added together with som libs (system/lib). Example: Terminal Emulator. the lib is some "jackpal" or something. .
When you download an app, apk will be saved in data/app in your phone. The lib or added files will be saved in data/data/(app name folder)/lib. Grab the apk and insert in system/app (kitchen's working folder). Grab the lib and insert it in system/lib (kitchen's working folder).
gabwerkz said:
For starters, yes it works. but nothing compares as to compiling and building from source (Linux).
What you need is a mere system dump or backup from CWM.
That backup will be saved in your CWM folder in SD
Grab the boot.img & system.ext3.tar
unpack the .tar with a zip/RAR propgram
grab a base upater script from the many ROMs around here
Now for a start:
your base ROM like Zeus etc.
Delete the system folder and boot.img from that zip.
Replace files.
Use dsixda kitchen via cygwin (windows)
Now do as you please... it can unpack boot.img and add features like init.d etc.
Adding apps:
Apps can be added together with som libs (system/lib). Example: Terminal Emulator. the lib is some "jackpal" or something. .
When you download an app, apk will be saved in data/app in your phone. The lib or added files will be saved in data/data/(app name folder)/lib. Grab the apk and insert in system/app (kitchen's working folder). Grab the lib and insert it in system/lib (kitchen's working folder).
Click to expand...
Click to collapse
many thanks gabwerkz. I had been searching ebook The Complete Idiot's Guides to custom rom, but I think the book has not published yet.
I only once tried to cook with kitchen, but that's waaaaay back and there I simply had no clue, of what I am doing and those days, the cust ROM I made, didnt work, but I simply randomly applied mods/tweaks and also had no clue of how things like updater-script work, but now I do and maybe as soon as I got some time again (in about 2 months ) I'll give it another shot and also read a lot about deving on my own and all the stuff related to it. Then maybe I'll be able to help all the cookers here out in a better way, cause until now, I only got the basics
You can start with simply things, like extracting the files with a packer, remove LG bloatware, add files/patches, you can find in dev section, add apps you like and think others might like as well, change lockscreen, launcher, keyboard,...
Remember to always do this step by step and make a changelog for yourself, so you know, where you might have made a mistake (also important for others to be able to help you). Then repack your ROM, sign and test it, if it works properly, use kitchen, to zipaligne, deodex, change filesystem,... And as soon as you are satisfied, post it/PM the good ones in here, to test it and ask for opinions, what you might change next. Custom kernels are always cool, cause you can change way more, like governors, iosched,... But that will take more time to dev and a lot more time to test for errors
Hope this helps you out a bit
N00BY0815 said:
I only once tried to cook with kitchen, but that's waaaaay back and there I simply had no clue, of what I am doing and those days, the cust ROM I made, didnt work, but I simply randomly applied mods/tweaks and also had no clue of how things like updater-script work, but now I do and maybe as soon as I got some time again (in about 2 months ) I'll give it another shot and also read a lot about deving on my own and all the stuff related to it. Then maybe I'll be able to help all the cookers here out in a better way, cause until now, I only got the basics
You can start with simply things, like extracting the files with a packer, remove LG bloatware, add files/patches, you can find in dev section, add apps you like and think others might like as well, change lockscreen, launcher, keyboard,...
Remember to always do this step by step and make a changelog for yourself, so you know, where you might have made a mistake (also important for others to be able to help you). Then repack your ROM, sign and test it, if it works properly, use kitchen, to zipaligne, deodex, change filesystem,... And as soon as you are satisfied, post it/PM the good ones in here, to test it and ask for opinions, what you might change next. Custom kernels are always cool, cause you can change way more, like governors, iosched,... But that will take more time to dev and a lot more time to test for errors
Hope this helps you out a bit
Click to expand...
Click to collapse
Your post help me a lot... thanks... I will try what you told me todo...
And If your rom need a bootanimation just PM me right...
I was always kinda crazy about update-script, if it is really correct while setting permissions and symlinks, so I took the one from wanam's ROM and fixed the wrong lines. It needed just some tweaks, by removing and adding some toolbox symlinks, and removing inexistent files lines. The result is very similar or even the same comparing to the structure when you flash the ROM from odin. I also organized the whole thing, removing useless stuff and making kernel/modem flashing faster.
- This is the META-INF folder used to install full ROMs.
It already comes with su binary and busybox. Delete init.d folder and update-script line if you are not going to use init.d.
I made the changes based on the new XXELKC-4.1.2 firmware.
As you may or may not have found out, while the Paranoid Android GAPPS package is by far the most comprehensive GAPPS package, preinstalling all of the Google apps found in the stock image, it does remove the stock Mms.apk/Browser.apk that comes with the ROM. For example, on Cyanogenmod, which is compiled from AOSP source plus improvements, it will remove the AOSP Messaging app/AOSP Browserand put in Hangouts/Chrome.
There are two ways of getting around this- put the Browser/Mms.apk back in the ROM after PAGAPPS has finished installing, or prevent PAGAPPS from removing it altogether, which is quite useful if you switch ROMs frequently. This tutorial will cover the latter.
Method 1 (the let someone else do it method): Lucky for you, I've already modified the script. Simply open up the .zip file using your favorite zip viewer (7zip/WinRAR/etc) navigate to /META-INF/com/google/android, and delete updater-script. Then, simply click and drag the updater-script I provided that matches your PAGAPPS version (unzip and make sure to rename it updater-script!) I provide into the zip viewer window. Let it rearchive and do its thing. There ya go! The downside to this method is that I may or may not have the most current version of the script ready, as it may vary between PAGAPPS releases.
Method 2 (the DIY method): Open up the PAGAPPS file and navigate to /META-INF/com/google/android using your favorite zip viewer (7zip/WinRAR/etc). Copy the updater-script file into your desktop. Using Notepad++ (the Notepad that comes with Windows will more than likely NOT work, as there is special formatting in script files such as these) to open up the updater-script, go to line 115-119, or where it mentions the Mms.apk/Browser.apk, as the line numbers may change in future distributions of the PAGAPPS package. Change these lines to the code below:
Code:
# Keeping the stock AOSP Mms.apk because it's AWESOME
ui_print("Mms.apk is preserved!");
# Keeping the stock AOSP Browser.apk because it's AWESOME
ui_print("AOSP Browser is preserved!");
Save and close out of the editor. Next, delete updater-script out of /META-INF/com/google/android and then drag and drop your updater-script into the same location. Let it rearchive and it should be ready to flash! If it works successfully, while flashing, it should output the lines "Mms.apk is preserved!" and "AOSP Browser is preserved!".
Note, since this simply prevents PAGAPPS from deleting the AOSP apps, it will not install them. For example, if you are using a ROM that does not include AOSP Browser.apk (such as Purity), it will not be installed.
Helpful tip if you want to put the apks back in after PAGAPPS has finished installing normally- the Mms.apk is located in /system/priv-app.
Hopefully this helped somebody!
ok so im trying to put together a modded stock ROM
so I've pulled and extracted the /system folder and the boot.img
I've added root to the system.
removed some bloat
anyway I need a updater script, I've read about how to write one but I think it may be easier to call on some help.
I want to put together a solid base to port off
meer_mortal said:
ok so im trying to put together a modded stock ROM
so I've pulled and extracted the /system folder and the boot.img
I've added root to the system.
removed some bloat
anyway I need a updater script, I've read about how to write one but I think it may be easier to call on some help.
I want to put together a solid base to port off
Click to expand...
Click to collapse
Yank one from an existing ROM. That's about the easiest route. This way will also give you an idea of the layout of a zip ROM. The updater-script and updater-binary are located in /META-INF/com/google/android. If memory serves. LOL.