[LG Optimus 2x] mateorod:
Ok, I can help you with the manual patching, but I am a little confused about what else you are asking for. Are you still using the builds from alroger? Those have been patched already. Or is this a nightly that you are trying to flash for?

I'll tell you what, if you're willing, I will have you go the whole nine. I will patch these for you and also make a Botbrew package for your device. If you haven't seen, Botbrew is an app that will use these files to enable PDroid on every nightly you flash for as long as the files don't go out-of-date in the CM repo. Here is the run-down, and directions.

We can also get you up to speed on how to manually patch. That way, when the package finally breaks, you could patch them and get them to me and I could create a new package for your device. Or, should you really want to learn, I could help you create your own Botbrew packages, which would give you your own space to offer your own software to anyone.

But that isn't necessary to take on all at once. You are working in Windows, right? I am really only going to be able to tell you how I do this in Linux, I know that tools like patch and apktool operate differently in DOS sometimes, and I don't know if this is one of those times. But I will tell you what I do, maybe you could look at a DOS man page and see if it changes any.

The files you will need to manually patch are here.

Decompile an app with apktool. For these purposes, I am using framework.jar

apktool d core.jar

This will give you a framework.jar.out folder in whatever directory you are working in.

Patch it

patch -N -p2 -d ~/path/to/file/framework.jar.out -i ~/path to patch/encore-framework.patch

The -N command is used to automatically skip all reversed hunks in the patch. Think of it as filtering the garbage out of the patches, which I haven't cleaned up yet. The -p2 is stripping away two directories from the patch header. It is related to which directory I was working in when I made the patch. -d is the directory where the file to be patched is, -i the directory containing the patch. Hopefully windows is similar.

Note:I decompile all the jars in a row, and then patch them. I then put all my original system.jars in a sub-folder named stock so I won't get confused when I recompile, and because you still need files from them and don't want them to get over written.

Recompile the jar

apktool b framework.jar.out core.jar

Now I used framework.jar as an example because it is a special case. You will need the preloaded classes file from the patches.zip. Open up your new framework.jar and put that file inside.

Repackage the new system.jars

In addition to the preloaded classes, each jar file you compiled is still missing components. Open up your new and old framework.jars in an archive manager. You see how they both have classes.dex and now preloaded classes files? You need to copy over the meta-info from your stock jar into your new framework.jar. You've done this sort of thing with the smali binaries, apktool just packages the classes.dex for you. Do the same for the services.jar (just meta-info) and the core.jar (meta-info, java and org).

That's it. Now I put them in packages, and distribute. I will make a package for your device here in a minute and then you can download Botbrew from Google Play (for free) and have PDroid in your nightlies!

Now, PDroid seems to work with a stock preloaded classes file, but since it is patched when building, I wanted those changes available in case they would cause PDroid to leak.

Let me know if I can offer any more help.

Edit Wait, this isn't a CM9 Rom. This patch isn't working for anything but CM9 derivatives at the moment. You're gonna have to wait until someone builds a PDroid enabled ROM before I can make a patch for it. I am looking at manually applying the hunks now, though. I still haven't figured out the problem. I may have something for you to test later, but it we'll have to see.