[Android Software/Hacking General [Developers Only]] gaikokujinkyofusho:
Hey, thanks for the in depth explanation (gotta admit "make clean" i kinda understood before but until now i thought "clobber" was something that the playground bully did). As for the date as far as i know it was released on Nov 4th so i will assume your clobber hypothesis is right. I went ahead and tried it manually (thanks for putting the precise command) and it *seems* to have gone well enough, below is the output i got with no apparent errors:

cygwin warning:

MS-DOS style path detected: ApGPackages\cygwin\bash.sh

Preferred POSIX equivalent is: ApGPackages/cygwin/bash.sh

CYGWIN environment variable option "nodosfilewarning" turns off this warning.

Consult the user's guide for more details about POSIX paths:

http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

Setting new path variable

The Auto-Patcher v2.4.7

The Auto-Patcher v2.4.7

usage: ./auto_patcher [ROMNAME].zip [MODS] [ROMTYPE] [PATCHDATE]

* [MODS] can be pdroid, pd2.0, v6supercharger, tabletUI, etc...

MODS can be combined by separating them with a comma and NO SPACES!!!

* [ROMTYPE] can be cm, aokp, aosp or pa [recommended]

* [PATCHDATE] will select older patch versions, e.g 20121030 [optional]

try "./auto_patcher ROM.ZIP -h" to see what is available

Gaiko@Gaiko-PC /cygdrive/d/Downloads/ApGPackages/ap

Gaiko@Gaiko-PC /cygdrive/d/Downloads/ApGPackages/ap

$ ./auto_patcher RR_JB_V3.1.2_AOKP_M1_4.1.2_I9100.zip pdroid aokp latest

The Auto-Patcher v2.4.7

### verify tools ###

### verify ROM ###

### unzip patch tools ###

### unzip patch patches ###

inflated: system/build.prop

... result of ROM check: RIL= Smdk4210RIL

### probe rom type ###

... result of ROM check: version= jellybean rom= cm ...

... Using aokp patches ...

... pdroid patch date set manually to latest ...

### unzip rom ###

inflated: system/framework/core.jar

inflated: system/framework/framework.jar

inflated: system/framework/services.jar

### create updater script ###

inflated: META-INF/com/google/android/update-binary

inflated: META-INF/com/google/android/update-binary-installer

inflated: META-INF/com/google/android/updater-script

... using Aroma installer ...

### create restore.zip ###

### decompile system files ###

... decompile framework.jar ...

... extract preloaded-classes ...

... decompile core.jar ...

... decompile services.jar ...

... overwriting ContentResolver.smali ...

### jar patch pdroid/jellybean/aokp/latest ###

... apply framework.patch ...

Reversed (or previously applied) patch detected! Skipping patch.

5 out of 5 hunks ignored -- saving rejects to file smali/android/content/Content

Resolver.smali.rej

... apply preloaded.patch ...

... apply framework.jar.sh ...

... remove unnecessary 27 files to avoid methods cap ...

... apply core.patch ...

... apply services.patch ...

### rebuild jar ###

... rebuild framework.jar ...

... rebuild core.jar ...

... rebuild services.jar ...

### create update.zip ###

### finished ###

flash update.zip to install the modified

flash restore.zip to restore the original

Gaiko@Gaiko-PC /cygdrive/d/Downloads/ApGPackages/ap

$

I tried it out, flashed update.zip, rebooted, installed "PDroid2.0 user" (anyone got any thoughts on PDroid Manager?), and tried PDroid2.0 and [EDIT:]... crash, it opens up fine but any time i try to do something/anything it crashes "Unfortunately, PDroid 2.0 has stopped". Any thoughts?

I am a bit curious, what ROMs are you guys using? I have been considering trying some other ROMs but there are tons of them out there, i mean a really dizzying array (I just want something fairly light, very stable, perhaps "secure" out'a the box... and hopefully properly clobbered :p)