asm19, on 12 April 2012 - 04:40 PM, said:
sej7278, did step #8, and has compiled the rom. Now I want to do a patch type your btkernel-signed.zip
for this have to do so: blog
starting from step 4 to 7, right?
In this step 7, is different for cm9 or not?
Edit: Each time we build a rom we have to erase the files in the folder:
Is that for what seemed like if you compile with the old files as he takes these files and does not build new, i am wrong?
just unzip my patch - extract META-INF, delete the CERT and MANIFEST files, replace my boot.img with your boot.img, then zip them up and sign them:
cp /path/to/your/boot.img .
zip kernel.zip META-INF boot.img
java -jar signapk.jar testkey.x509.pem testkey.pk8 kernel.zip kernel-signed.zip
the test keys are in ~/coldfusionx/cm9/build/target/product/security/
and signapk.jar will be in ~/coldfusionx/cm9/out/host/linux-x86/framework/
after you've compiled the rom. i usually keep a copy of signapk.jar somewhere so i don't have to recompile a rom just to get it.
the instructions on my blog are for if you're only compiling a kernel and not a whole rom and want to patch that into an old boot.img, its a bit over-the-top for this exercise.
and yes i recommend deleting out/ for every new compile as every time i don't do it, i get problems. you can do a "make installclean
" but it doesn't do the job really - for instance it won't replace the kernel file in out/, it won't re-read environment variables etc; it just seems to delete the *.img files.
Edited by sej7278, 12 April 2012 - 11:28 PM.
Phone: Gen1/OLED (TPT
-v10'd to Gen2 - 2c/160s/294d), Orange UK San Francisco
ROM: cm-10.1-20130111-EXPERIMENTAL-blade-sej, CWM Touch 184.108.40.206