Database Users

help needed modifying ROM pre-flash

i attempted to replace most of the .apks in the system app folder with the same .apks from an ealier version of the rom (because i prefer black to blue/black). i replaced them in the .zip before i flashed it, hoping it would work.. but it didnt.. in the recovery menu it says:
....
verifying update package...
e:wrong digest:
system/app/browser.apk
e:verification failed
browser was one i replaced. how do i make this work? i dont want to use root explorer to manually replace each ****ing thing, and i have no patients for adb. i must need to sign the package or something? i never unpacked anything, just replaced some contents.. thought id be fine..
on a related note there may be more issues to come. unzipped the framework-res.apk to my computer, renamed it .zip, went inside and replaced the battery icons, renamed it back to .apk and replaced the modified file in the rom. who knows what chaos i might have caused there.. if you know what to expect and how to fix it please feel free to help!
if it matters at all, the rom im modifying and flashing is nonsensikal 9.5 black/blue, the system apps came from version 8.2 black, and battery icon .pngs came from 5.4 black.

Id try and resign the whole rom after you make your changes it should be just fine

you cannot simply replace the apks in the zip, then flash. after replacing, use one of the following methods:
if you use linux, use EasySign (http://android.grdlock.net/index.php?&direction=0&order=&directory=HTC Droid Eris/Extras) or the Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246).
if using Windows:
Use AutoSign (http://androidforums.com/developer-101/8665-how-signing-roms.html).

Thanks. I'll get on the computer and give it a shot.
Sent from my nonsensikal froyo using XDA App

if you've unzipped the framework-res.apk then none of this will work anyway. You need to pull the images out of the old framework-res.apk and drag and drop them back into the new framework-res.apk without unzipping it. You shouldn't even need to rename it to zip. Just open it with a program like 7zip without unzipping and drop the png's in the correct folders. Then you can put the .apk back in the rom and resign from the links directed above.

Oh it all worked fine. I never unzipped framework, just extracted it from the Rom and renamed it, then replaced files, renamed back to apk, and replaced in original .zip. it worked great.
To achieve full 9.5 black I have to copy all of the previous versions (black) framework .pngs to the new Rom though.
I think the file is like, drawable-mpdi or something. Not landscape or non. I don't really know.. not in right frame of mind
Sent from my nonsensikal froyo using XDA App

Looking for a tutorial: how to cook a ROM?

I'm looking for a guide which tells how to make a own custom ROM from another one
I mean:
1. How to add/replace/remove apps in /system/app/?
1. a) Do they need to have special permission?
2. How to replace boot screen?
3. How to add custom kernel?
4. How to add Desire lockscreen/flip clock?
5. How to add transparent notofication area?
6. How to add Power menu?
I've been serching forum, but didn't find such tutorial. Would be very thanful to get this knowledge.
I think that will be very useful for maaaany android maniacs

1. Simple delete/copy apks in .zip file using 7-Zip or any other.
2. I belive you need to put bootanimation.zip in /data/local/ folder.
3. Idk
4. For Desire lockscreen you need edited HtcLockScreen.apk; for flip clock - HtcClockWidget.apk
5. Edited /system/framework-res.apk or /system/framework/com.htc.resources.apk. I'm not sure
6. You need edited /system/framework/android.policy.jar
69. Resign your zip file using Auto Sign

Attachment doesn't load, but I know about resigning ROM after everything is done
Ad. 1. As I thought, but do the need special permissions? And I also wonder one thing. Are they installed while flashing? Cuz they need to be in system registry, I think...

I have found this: http://wiki.android.com.pl/wiki/Kon...iana_instalowanych_aplikacji_razem_z_systemem
No any permissions etc.

Found this, too. Thanks.

to add a custom kernel you have to unpack the boot image and edit the ramdisk manually, although i think there is an option in dsixda's kitchen to unpack and repack the boot.img

I've got two more questions:
1. When signing, three files are created in folder META-INF: CERT.RSA, CERT.SF, MANIFEST.SF. But in other packages I see also com/google/android/update-script in META-INF. How to make it? Is it necessary?
2. If I want to make only flashable update file which changes one app or another file, eg. framework-res.apk, I have to create folder structure: system/framework/framework-res.apk, add it to zip archive (no compression?) and sing using Auto-sing. Am I right?
Edit:
Found nice guide there: update-script syntax

tomekk_nt said:
I've got two more questions:
1. When signing, three files are created in folder META-INF: CERT.RSA, CERT.SF, MANIFEST.SF. But in other packages I see also com/google/android/update-script in META-INF. How to make it? Is it necessary?
2. If I want to make only flashable update file which changes one app or another file, eg. framework-res.apk, I have to create folder structure: system/framework/framework-res.apk, add it to zip archive (no compression?) and sing using Auto-sing. Am I right?
Click to expand...
Click to collapse
The most important part of a recovery update zip is the update script. It will tell the recovery what to do. If you want an example of a basic update package, which replaces one file in the /system/framework (although a different one) can found here. Open this and read the META-INF/com/google/android/updater-script (or whatever its called). The syntax is pretty straight forward and I think its easiest to learn from the examples of updater scripts found here on XDA. For the simple case, of only replacing/adding files to the /system partition you can leave the updater script from the above example as is and only change the files under the /system directory in the zip.
Note, that the above example uses the newer upader-script (I hope I am writing this correctly, I am writing from memory) which also has a binary file in the same directory. Some update zips use the older "update-script" lone text script. For these kind of scripts, you can find a guide here.
Personally, I use RA recovery, and for this recovery you need to sign the update zips (last thing you do of course). At least for RA recovery, both the older "update-script" and the newer "updater-script" work fine, so its up to your personal preference which do you prefer.

Thanks. Found a guide you mentioned a couple of minutes ago and read it.
The more I know, the more questions it brings So one more thing. If I'd like to use the newer version of syntax: "updater-script", I need also to put this binary file in this folder. But I create/edit only "updater-script", binary file is the same for all packages, or do I need to edit it, too?

I built a kernel tool long time ago, very easy to use (only for linux)
1: unzip the file, place it where you want it eg your desktop
2: place boot.img in the working directory
3: double-click the menu icon or launch from terminal
4: it creates a new directory named BOOT-EXTRACT,edit what you want in there or change the kernel etc.. and repack it again via the kernel tool
see screenshot. here for those how want the tool >>> http://www.elelinux.se/tools/kernel_tool.zip
Edit: Only for Hero

tomekk_nt said:
Thanks. Found a guide you mentioned a couple of minutes ago and read it.
The more I know, the more questions it brings So one more thing. If I'd like to use the newer version of syntax: "updater-script", I need also to put this binary file in this folder. But I create/edit only "updater-script", binary file is the same for all packages, or do I need to edit it, too?
Click to expand...
Click to collapse
Only the updater-script. The binary is a replacement of the script-interpreter I think, but thats just an assumption.

elelinux said:
I built a kernel tool long time ago, very easy to use (only for linux)
Click to expand...
Click to collapse
And that's a good reason to install newest Ubuntu Thanks!
riemervdzee said:
Only the updater-script. The binary is a replacement of the script-interpreter I think, but thats just an assumption.
Click to expand...
Click to collapse
That's mine assuption, too, but would like to know it for 100%
Edit: I see you use it in your kernel update package. So you write only updater-script and place also update-binary next to it?

LOL, you've got help from every well known hero dev on xda, I'm sure you'll have all the info you need now to start building rom's. Good Luck!

Found an app called Easy Flashable zip Builder on this thread. Will test it soon.

tomekk_nt said:
Found an app called Easy Flashable zip Builder on this thread. Will test it soon.
Click to expand...
Click to collapse
But it is for MS Windows, or saw I wrong ? I have also built a tool to javasign files,but should probably write a manual first,it is easy to use but some dependencies maybe not so easy for a beginner with Linux.

tomekk_nt said:
That's mine assuption, too, but would like to know it for 100%
Edit: I see you use it in your kernel update package. So you write only updater-script and place also update-binary next to it?
Click to expand...
Click to collapse
Correcto

[Q]Remove kernel installation from roms

Is there a way to remove kernel installation from a rom? Id like to try installing some fascinate GB roms over our Froyo kernel but most of the Fascinate GB roms include a kernel installation which I would like to avoid (for obvious reasons).
Basically what I want is a ROM only install no kernel.
Or better yet does anyone have our 2.2.2 kernel (just the kernel) in a flashable odin package?
Im only experimenting so no flaming..
Thanks

Yup, there is for either option too xP
Which option do you choose?
Sent from my SCH-I400 using xda premium

If you have the 2.2.2 kernel in an odin package I'll take that.. But for the sake of education I'll take both if you have the time to explain..
+1 for you
Thanks!

Alright, here is the 2.2.2 kernel only Odin Package Can you check now as a test to make sure it works? haha I didn't test it myself
http://www.mediafire.com/?qgkh35439o79sjl
and alright, here is how you can remove flashing the kernel in those packages...
First, open up the package in 7zip...
Delete the Kernel_Update folder, or something named closely to such, on the root of the zip
Then go to META-INF\com\google\android, and copy the updater-script to your desktop
open it up with Notepad++ or another advanced text editor (*Important!) and delete all the lines that look connected with the kernel...
The most important lines are "package_extract_dir("kernel_update"" and "run_program("/tmp/kernel_update/bmlwrite"" lines

K ill give it a try and let you know.
Sent from my SCH-I400 using XDA App
*Edit* Kernel works just fine.
I deleted the "updates" folder which contained a zImage file, redbend.ua, and modem.bin file. However in the META folder there were no instances of the word 'kernel' found. Just references to run the installer for the formentioned 'updates' folder which I deleted.
Should I just delete the 'zImage' file which I'm assuming is the kernel and leave the script to install the redbend.ua and modem.bin files?

Much Appreciated! :highfive:
trailblazer101 said:
Alright, here is the 2.2.2 kernel only Odin Package Can you check now as a test to make sure it works? haha I didn't test it myself
http://www.mediafire.com/?qgkh35439o79sjl
and alright, here is how you can remove flashing the kernel in those packages...
First, open up the package in 7zip...
Delete the Kernel_Update folder, or something named closely to such, on the root of the zip
Then go to META-INF\com\google\android, and copy the updater-script to your desktop
open it up with Notepad++ or another advanced text editor (*Important!) and delete all the lines that look connected with the kernel...
The most important lines are "package_extract_dir("kernel_update"" and "run_program("/tmp/kernel_update/bmlwrite"" lines
Click to expand...
Click to collapse

[Q]

Hi. I've always thought about this. Some people say something like this
Copy the file aroma-config and updater-script from META-INF\com\google\android\ from 3.1.1 rom.zip to 3.1.2 zip to the same path. He will say v3.1.1 during installation, but he will install 3.1.2 and you can select CLK again.
Click to expand...
Click to collapse
And what does it mean? When I edit zip file, it doesn't work. Is there a program for this?

kubekpop said:
Hi. I've always thought about this. Some people say something like this
And what does it mean? When I edit zip file, it doesn't work. Is there a program for this?
Click to expand...
Click to collapse
Looks like the update (the zip) mentioned in the quote disables a feature on the HD2 that was present before that update. See here - shouldn't you have included that link
hxxp://forum.xda-developers.com/showthread.php?t=1166948&page=1286
To prevent disabling the feature, the quote-poster advises to run the update with the updater script (the script that does the actual updating) replaced by an old version. To do that, download both update versions and replace the mentioned files mentioned in the post in the newest version. Rezip and apply the update.
Not sure if this is a wise thing to do if you don't know more about updating, restoring etc... At least backup your data.

No, it's just when I zip it after update, cwm doesn't want to install this and sees as damaged rom.
But 7-zip can change files in archive no need to unzip all. So it works

[Q] Understanding Meta-Inf folder

So i pulled stock system folder and deodexed, zipaligned and signed.
Wanted to try flash it by twrp. So i copied one of custom roms meta inf folder but i get sysmapfile error.
Created certificates with signapk but there is no update-binary and update-script file. So i searched and learnt sth about update-script but what is exactly update-binary do? How can i edit for my rom or create one? can i use one of them with all devices rom?
Btw editing update-script didnt solve my sysmapfile error. Can someone guide me about meta-inf folder? All other articles just tells using another roms meta inf but it simply didnt work for me.

The update-binary file is different from one ROM to the next. For example, a CyanogenMod binary will be different from one in a custom ROM based off stock. In general, look at http://wiki.cyanogenmod.org/w/Doc:_About_Edify for an explanation of what the binary is. You will need to pull a binary from a custom ROM based off stock, preferably from the same version of Android.