yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dron39:
It seems that pdroid isn't compatible with latest cm7 nightly (2012-10-21)

I think framework.jar not patched.

Part of log:

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
Running autopatcher with the following arguments:
ROM_PATH: /cygdrive/c/test/fw/cm72_ace_21102012.zip
PATCH_TYPE: pdroid
ROM_TYPE: cm7

The Auto-Patcher v2.1.9

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 2.3.7 rom= cm7 ...
... Using cm7 patches ...
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/services.jar
inflated: system/framework/framework.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
### jar patch pdroid/cm7/latest ###
... [b]apply framework.patch ...
Reversed (or previously applied) patch detected! Skipping patch.
5 out of 5 hunks ignored -- saving rejects to file smali/com/android/internal/te
lephony/cdma/EriManager.smali.rej[/b]
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
### rebuild jar ###
... rebuild framework.jar ...
... rebuild core.jar ...
... rebuild services.jar ...

Please update patch to support latest cm7 nightly!

Full log http://codepad.org/cWOqgGdU
[Android Software/Hacking General [Developers Only]] mateorod:
Or, "Please test my work before claiming it is broken!"

That was patched fine. It simply means that file is already in the shape it needs to be for PDroid to work.
[Android Software/Hacking General [Developers Only]] dron39:
I add full log in previous post. Please see it and tell me, all is fine there or not?

Sorry for my bad English. :)

And thank you for your hard work!!!
[Android Software/Hacking General [Developers Only]] karamelos:
You have no error in your log

Backup your ROM

Go in recovery

Flash update.zip

Install pdroid app

If not running or boot loop or your phone catches fire, restore your backup
[Android Software/Hacking General [Developers Only]] dron39:
mateorod,

I test it and it's not working. It's not boot (stuck at htc logo on white background and I don't even see CyanogenMod splash screen).

Also updater-script is a bit strange. Some of the lines in it are repeated.

mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm(1000, 1003, 02755, "/system/bin/screenshot");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
[b]set_perm_recursive(0, 2000, 0755, 0750, "/system/etc/init.d");[/b]
set_perm(0, 0, 0755, "/system/etc/init.d");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/hcitool");
set_perm(0, 0, 06755, "/system/xbin/librank");
set_perm(0, 0, 06755, "/system/xbin/procmem");
set_perm(0, 0, 06755, "/system/xbin/procrank");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 06755, "/system/xbin/tcpdump");
[b]set_perm_recursive(0, 2000, 0755, 0750, "/system/etc/init.d");[/b]
unmount("/system");

If it's need - i may upload broken update.zip
[Android Software/Hacking General [Developers Only]] kobik77:
Hey Mateo,

Patch is succesful for latest CM10-maguro, yet it fails for Pdroid+Extension mods

http://codepad.org/F3QSYMtt
[Android Software/Hacking General [Developers Only]] mateorod:
Updater script is cat from your original ROM, so if it looks funny to you you'll have to ask your Cyanogen maintainer. I will have to look at the gingerbread thing later. I don't have source to update the patches, so if a commit broke the coverage, it will take me awhile to get it back.

But I will look at it.

@kobik77 Jesus that's a pain in the ass. Ok, I will check it out this afternoon, Thanks.
[Android Software/Hacking General [Developers Only]] dron39:
Thank you very much! I will wait for it!:good::victory:
[Android Software/Hacking General [Developers Only]] mateorod:
Oh, wait kobik. I didn't recognize that '+' sign for what it was.

'PDroid' and 'Extension' are incompatible. In fact, if you haven't wiped your privacy.db (there is a link to how to do that on a post from yesterday) then you will get FCs if you try and run the Extension on a rom that you previously used Pdroid on.

I know, the name PDroid Extension is totatally misleading, it's not my product. It is actually 'PDroid REPLACEMENT'.

try just extension. I will perhaps add some error checking, I am working on a BIG update that should cut down on user error a BUNCH, and perhaps that would be a good add.

Edit:: You will have to replace your GsmServiceStateTracker.smali, which I haven't tested yet, so let me know ho it goes...
[Android Software/Hacking General [Developers Only]] karamelos:
There have not marabout here

Post boot log
[Android Software/Hacking General [Developers Only]] kobik77:
Thanks man.

This is the result of failed extension (only) mod

http://codepad.org/rhYUisIA

As you anticipated it fails on GsmServiceStateTracker.smali so how do I replace it?
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry, I hadn't pushed that provisional somehow. Pushed now, so please test it for me since I can't test it myself. If it doesn't work let me know. Please delete the privacy.db and I think that CollegeDev has a new apk in his thread, maybe.
[Android Software/Hacking General [Developers Only]] kobik77:
Haven't flashed it yet but patching looks fine now :good:

http://codepad.org/mJkf1Ygk
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
failed attempt to patch CM10-20120924-NIGHTLY-mb525

i'm attempting to use the auto-patcher in order to enable pDroid on my Motorola Defy which is running CM10. things have failed for me, however, and i'm a little out of my league in terms of interpreting what the errors are. i've pasted the results here...

http://codepad.org/cl4SoW7L

...for those who can't view the link (or if that page expires for some reason) i'll paste the final details here...

... apply framework.patch ...
1 out of 1 hunk FAILED -- saving rejects to file 'smali/android/app/ContextImpl$20.smali.rej'
5 out of 5 hunks FAILED -- saving rejects to file smali/android/content/ContentResolver.smali.rej

... apply preloaded.patch ...

!!! PATCHING FAILED FOR android/app/ContextImpl$20.smali' android/content/ContentResolver.smali !!!
!!! patch error for android/app/ContextImpl$20.smali' !!!

... anyone have any suggestions as to what could be happening?
[Android Software/Hacking General [Developers Only]] mateorod:
Kobik, man, I love that automatic log upload. No one likes to upload the whole log, but we NEED that stuff.

That build is pretty old, you are going to need older patches. Which is okay, we ship every patch we've ever offered with each version of the Auto-Patcher. Try this:

./auto_patcher ROMSNAME.zip pdroid cm10 20120913

If you are using an older build, the trick is to enter the -h flag (./auto_patcher ROMNAME>Zip -h) and then find the patch date from immediately before your build date.

But hopefully this will soon all be a thing of the past. I am almost done with some major updates to the program, which should make it so the only thing users will have to enter is ROMTYPE, i.e. (aokp, aosp, or cm). Everything else should be automatic, no more build dates or aosp-jb/aosp-mod stuff.

The option to manually override the automatic settings will still exist for our more advanced users. But I am pretty happy with the changes so far. Hopefully next update, but in any case, soon.
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
now, i've only been trying to use the internal patches... does the auto-patcher app make use of pastime1971's port for ICS/JB? i have those files separately but using the "Manual Patching" function is a little above me right now.

i sure hope i can make this work somehow, because i really would like to have pDroid functionality. it's a damn shame that permission tweaking was removed from CyanogenMod.
[Android Software/Hacking General [Developers Only]] mateorod:
I find every sentence you wrote progressively more confusing. Pastime's patches (which I made the patches for JB with him, and he is half of the main auto-patcher team, look at my sig) are for patching source code. What are internal patches?

I am guessing that you are using ApG (the auto-patcher GUI) because you uploaded your log. Play around with it until you find a way to use older patches (I don't know how to do that but I am pretty sure there is a way) and use the patch date recommended above.

Or download the script from techerrata and patch them manually. ApG has already set up all the dependecies for you, which is the hard part. All that is left is the one command.

This may look intimidating, but it is very very easy. I already told you the command you need. I am 99% sure you can do this straight from the GUI.
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
manual patching didn't work out, either

so, even the manual environment generates the same errors...

$ ./auto_patcher CM10-20120924-NIGHTLY-mb525.zip pdroid cm10 latest

The Auto-Patcher v2.1.9

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
... result of ROM check: RIL= MotoWrigley3GRIL
### probe rom type ###
... result of ROM check: version= 4.1.1 rom= cm10 ...
... Using cm10 patches ...
### 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/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
### jar patch pdroid/cm10/latest ###
... apply framework.patch ...
1 out of 1 hunk FAILED -- saving rejects to file 'smali/android/app/ContextImpl$20.smali.rej'
5 out of 5 hunks FAILED -- saving rejects to file smali/android/content/ContentResolver.smali.rej
... apply preloaded.patch ...
!!! PATCHING FAILED FOR android/app/ContextImpl$20.smali' android/content/ContentResolver.smali !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/app/ContextImpl$20.smali' in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /cygdrive/c/Users/Deviant/Desktop/ApGPackages/ap/log20121021191633 for any debugging

! patching failed.
! it may be possible to patch /cygdrive/c/Users/Deviant/Desktop/ApGPackages/ap/CM10-20120924-NIGHTLY-mb525.zip using other patch version

The Auto-Patcher v2.1.9
pdroid 1.32 patches 2012.09.13.
v6supercharger patches 2012.08.17.

usage: ./auto_patcher ROM.ZIP MODS [ROMTYPE] [PATCHDATE]

MODS can be pdroid,v6supercharger or pdroid or v6supercharger
optional [ROMTYPE] can be cm9, aokp, etc.
optional [PATCHDATE] can be specified to use older patch versions.
try "./auto_patcher ROM.ZIP -h" to see what is available

... is there a way to load the extra .diff files from another source? drop them somewhere into the ApGPackages folder?
[Android Software/Hacking General [Developers Only]] mateorod:
Unless you show some sign of having read my response, this is the last help I am going to give you.

YOUR ROM IS OLD.

YOU NEED OLDER PATCHES.

USE THIS COMMAND:

./auto_patcher CM10-20120924-NIGHTLY-mb525.zip pdroid cm10 20120913
[Android Software/Hacking General [Developers Only]] RuffBuster:
Is there any support for SlimBean roms?
[Android Software/Hacking General [Developers Only]] socioteq:
I'm a beggar.

I'll probably get blasted for asking, but have you thought about doing a Linux version of your GUI? So far there as been no easy way to patch in Linux, and it would be such a great help to those of us who don't have the time to learn how to decompile/recompile services.jar. Don't know if you program in Linux as well, but those of us who only run Linux systems would very much appreciate it!
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
couldn't you run ApG using wine?
[Android Software/Hacking General [Developers Only]] socioteq:
Actually i just answered my own question... sort of. I arn auto_patcher in terminal and decompiled and recompiled that way. I actually ended up rooting the phone via VMware, and that alone took serious heartache and headaches, so I swore to myself that if there were any way besides the VM way I'd work that route next time. Turns out the auto_patcher via terminal way is actually very simple.

Great work OP you're the ****
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
yeah... i track with you on that, man. i honestly did not realize that there had been any replies (i don't frequent XDA forums, so whenever i make a rare post, i turn on "email notification" and somehow i had neglected to this time around. no notifications made me think no one had replied) and it must have seemed pretty foolish for me to keep posting new comments without acknowledging what you had said.

as far as not seeing the details in your signature... chalk that up to the fact that i (and many others i know across multiple forums) utterly ignore all sig data. yours is a rare case of useful short facts and even a link. but i think you can agree that most signatures on forums have gotten totally out of control, often being longer than the posts above them. lines upon lines of drivel that no one cares about, and god help you if you're on a forum that allows images as part of a signature, ha. they have just become a total blind spot for me when i'm reading on the web.

so, now i know who to is behind this great Auto-Patcher and the recent ICS/JB ports of pDroid, etc etc. (and knowing is half the battle)

i'll keep tuned in here for any updates on the possibility of the Auto-Patcher working with my Quarx ROM. what sort of time line do you have in your head as far as that sort of side-project might be concerned? that was already something you had thought about for future versions, yes? does that include the really significant update future version that you described as already in the works?

fingers crossed.
[Android Software/Hacking General [Developers Only]] trott:
try cm10 20121003 patch
[Android Software/Hacking General [Developers Only]] mj084:
@mateorod

seems that the CM10 build from hashcode (https://twitter.com/Hashcode0f) isn't patchable yet?

http://codepad.org/zzVuFXdq
[Android Software/Hacking General [Developers Only]] nsmart:
cm-10-20121021-NIGHTLY-i9100.zip (Galaxys S2) could successfully be pdroid-patched with APG 1.20 (autopatcher v2.1.9) and is fully functional.
[Android Software/Hacking General [Developers Only]] karamelos:
Hi,

On cm-10-20121022-NIGHTLY-n7000.zip (2012-10-22 08:44:47) pdroid extension patch failed

File for which patching failed:
---------------------------------------------

GsmServiceStateTracker.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

log attached

But Pdroid option work

on last cm-10-20121022-NIGHTLY-n7000.zip 2012-10-22 08:44:47
[Android Software/Hacking General [Developers Only]] D-m-x:
Same for me, expect that I'm trying to Patch PA for the Nexus 7. Seems to be a general Error patching this Rom.
[Android Software/Hacking General [Developers Only]] mateorod:
At some point today, I will put out a new update, version 2.2.0. This will include new CM7 patches (provided they are working, still being made), a fix for PDroid Extension, and adding of 'pa' as a ROMTYPE.

The addition of pa as a ROMTYPE may end up being temporary. They haven't merged their frameworks with CM in awhile, and I was trying to wait them out. But I will pump out some pa specific patches today and then we'll just see.

This update will not, as of this writing, include the improved build querying, because patching for multiple mods is still pretty buggy. It works great for one mod at a time, but I have some major reorganizing of the patches directory to do (remake basically all of the symlinks, ay yi yi) as well as institute patch date arrays, which will take me some more time to design and error check,

But we will have some new patches out today. Once again, the hoped-for fixes include:

Paranoid Android added as a ROMTYPE

New CM7 patches

FIxed Pdroid extension patches

The Extension fix is already pushed to github, for those of you on ApG.

I keep hoping for some time to add an upgrade wrapper script for Linux/OSX users, but the patch maintenance is cutting into that time.

Edit: As for Hashcode and Quarx builds of CM10, unless someone finds out why and how they differ from regular CM10, they will probably not be supported. Intermittent builds by them are patchable, but mostly they are not. I do not know why, but cannot fix that myself.

If someone who runs one of their builds wants to begin building for those devices, then we can talk about supporting them. Until then, it will remain random and mostly frustrating, I suspect.
[Android Software/Hacking General [Developers Only]] pro.aggro:
No new updates found atm :(

Waiting :)
[Android Software/Hacking General [Developers Only]] RuffBuster:
Tried it with SlimBean 2.7 for the galaxy s i9000 and it compiled, but the update.zip causes my phone app to constantly loop crash. Boots up into OS but makes phone unusable. I'm trying all patches for AOSP, AOSP-JB and CM10 from all dates to see if it will make a compatible uodate.zip, but was wondering if this was a waste of time. I use the windows GUI util latest 1.4.0.0 version and I see it recommends AOSP-JB patches. Shouldn't the latest patch work seeing as I'm using the latest 4.1.2 build of this ROM? I follow this topic alot I saw a while ago that Slim roms weren't patched yet, well a while ago. Managed to patch a previously unpatchable ROM with some of your later GitHUBs and was wondering if Slim is officially compatible as it is quite a popular ROM? Cheers!
[Android Software/Hacking General [Developers Only]] mateorod:
I pushed it yesterday. But it isn't a version update, so I don't know how ApG handles it. But I do know if you sync, it will pull the change since kobik himself did it yesterday.

Sync and try patching for extension. It has been failing on GSMServiceStateTracker, and should offer to replace it for you.

I know what the problem is with that FC. I have pushed a change to github, sync and try again with those same 20121003 patches.

I don't know why your rom hasn't caught up with all the changes from 4.1.2 for CM yet. We are in the same boat with PA, I think. Each maintainer forks whichever projects they wish from the main branches, but then they have to check-in any changes manually. Some of them are more diligent and timely about it than others.

The ROM probe checks the build.prop for the presence of 'aokp' or 'cm' or so on. If it doesn't find that, then it defaults to aosp. So it isn't so much that we are recommending aosp as that is the default. Post your build.prop and I will see if I can't improve the probing for slimrom.

But yeah, if you got an update.zip from 20121003, try again, there is a fix in place.
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
i suspect that someone of your stature here on the forums would have more weight when reaching out to Quarx... and if you two were to connect and work to get the patcher working, i'd gladly donate to each of you (do you support any sort of donations?) if it all gets working. pDroid is something incredibly important to me, and seeing it function on my fleet of Defy devices would be a dream come true.

(is it crass of me to ask in this manner? i know that some people get a little upset when offers of money start popping up in exchange for what are, effectively, favors... but i believe that everyone's time is incredibly precious. we all have lots of irons in fires and way too many projects on our plates. people who spend time fixing something that matters more to other people than it does to themselves deserve to be compensated for that effort. if outright donations are frowned upon, i could always just offer you each a big discount in my company's web store, heh.)
[Android Software/Hacking General [Developers Only]] pro.aggro:
I try to sync but nothing happens.

I will wait till you publish v2.2.0 :)
[Android Software/Hacking General [Developers Only]] Px80:
Same to me. Can't find the option for PA.

When i try to patch by hand an error appears while "compiling framework.jar"

. rebuild framework.jar ...

UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: method index is too large.
at org.jf.dexlib.Util.ExceptionWithContext.withContext(ExceptionWithContext.java:54)
at org.jf.dexlib.Item.addExceptionContext(Item.java:177)
at org.jf.dexlib.Item.writeTo(Item.java:120)
at org.jf.dexlib.Section.writeTo(Section.java:119)
at org.jf.dexlib.DexFile.writeTo(DexFile.java:716)
at org.jf.smali.main.main(main.java:231)
Caused by: java.lang.RuntimeException: method index is too large.
at org.jf.dexlib.Code.Format.Instruction35c.writeInstruction(Instruction35c.java:102)
at org.jf.dexlib.Code.Instruction.write(Instruction.java:57)
at org.jf.dexlib.CodeItem.writeItem(CodeItem.java:258)
at org.jf.dexlib.Item.writeTo(Item.java:117)
... 3 more
code_item @0x194e84 (Landroid/accessibilityservice/AccessibilityServiceInfo;-><init>(Landroid/content/pm/ResolveInfo;Landroid/content/Context;)V)
[Android Software/Hacking General [Developers Only]] kobik77:
I'm on 22/10 CM10 nightly, successfully patched and installed using extension mod only.

Deleted privacy.db* but when I try setting app permissions using PD-ext I get FCs.

Any other recommendations?
[Android Software/Hacking General [Developers Only]] mateorod:
Give me a minute. I broke something with APK patching this morning. I will update this post in maybe 15 mins. But after that, I would take logs to CollegeDev, I don't know his program yet, and if it is auto-patcher, he will be able to tell.

I may update the CM10 extension patches later today just in case there is a problem with the GSMServiceTracker copying, but I do know that the patching process works. Just have to get to know the program itself.

Edit: APK patching is fixed, I don't think that would cause FC's though. If you're of a mind to test, you could try the extension on a ROM from 10/16-18 or so, and if it doesn't copy over the GSMServiceStateService then we know what the issue is...but otherwise, maybe take a log to CollegeDev.
[Android Software/Hacking General [Developers Only]] pro.aggro:
Paranoid Android v2.22 successfully patched!

Great job!