Hello, I am a developer for the Evo and i was curious how i would install a custom kernel (Netarchy-Toastmod) into my rom (Tha Boss Rom. So far i copied all the files into the appropriate folder but what do i do with the boot image. I tried flashing with the files in place but it did not take. Any advice?
KyleCole90 said:
Hello, I am a developer for the Evo and i was curious how i would install a custom kernel (Netarchy-Toastmod) into my rom (Tha Boss Rom. So far i copied all the files into the appropriate folder but what do i do with the boot image. I tried flashing with the files in place but it did not take. Any advice?
Click to expand...
Click to collapse
You probably should ask this in the EVO Android Development forum. However, since I'm here, I'll do my best.
The boot.img should be at the root of the folder structure.
../NewFolder/system
../NewFolder/META-INF
../NewFolder/boot.img
You then have to zip the CONTENTS of ../NewFolder and sign the resulting zip with something like EasySign (http://android.grdlock.net/index.php?&direction=0&order=&directory=Extras).
Or you can just load the original ROM into dsixda's kitchen in the original_update folder (http://forum.xda-developers.com/showthread.php?t=633246), select '1' to create a work folder, copy the files into the correct locations, and then select '99' to zip and sign the ROM. It will then be in the OUTPUT_ZIP folder. The kitchen walks you through these steps really well, if you read the prompts.
Then flash the ROM.
I have smoki rom(for example). I'm open it in winRAR, and extract updater-script file. I'm edit comments and save changes. If I copy modified updater script file to smoki rom will it works correctly?
your using windows so you need to edit it in notepad++ otherwise it fails
So, if i use notepad ++ for this all will works?
yes it should
E:Wrong digest:
META-INF/com/google/android/updater-script
E:Verification failed
I'm only delete some lines ui_print.
did you resign the rom? you need to do that
How i can sign the rom(or another update file)? In occasion ask: have I to perform Partitioning HOW TO REVERT BACK TO STOCK when I want to upload the rom other than smoki(rcmagic v4.2 for example)?
sign the rom with auto-sign, you can search it in the g1 forum, i cant remember which thread
i like update zip packager 2 better
auto sign doesnt work for me on cm6
here:
http://forum.xda-developers.com/showthread.php?t=717437
well i only knew of the other hehe, but just something to sign it
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
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
i am very much concerned about using perfect things, i used alot of different ROMS both with .32 and .35 kernel, none was perfect even all the stock ROMs available does have something to hate about,
my question is Cant we manually edit Stock ROMs (Update.APP) and Custom ROMs and select few important and better apps and replace with unwanted apps in roms?
in this way we can manage to create a new ROM as per our requirements....
Can't do it with stock roms unless you install, root, delete apps from /system/app.
With custom rom, just use 7-zip in windows to open zip file and delete apps you don't want from /system/app and /data if it is there. Copy your own apps in and then install.
There is a perl script to extract system.img from update.app, but i dont think there is a way to pack again