yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Px80:
could you pls upload your patch?

what option did you take? addon, extension or pdroid?

/edit:

is it for the pdroid extension by collegedev?

this is my log for PacMan v 14.1

### copy patch extension/pa/latest ###

... copying system/media/PDroid.jpeg ...
`patches/extension/pa/latest/system/media/PDroid.jpeg' -> `./system/media/PDroid.jpeg'

### jar patch extension/pa/latest ###

... apply framework.patch ...
Reversed (or previously applied) patch detected! Skipping patch.
13 out of 13 hunks ignored -- saving rejects to file smali/android/app/BackStackRecord.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file smali/android/content/pm/ContainerEncryptionParams.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/location/Location.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
7 out of 7 hunks ignored -- saving rejects to file 'smali/android/opengl/GLSurfaceView$EglHelper.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file smali/android/widget/AppSecurityPermissions.smali.rej
1 out of 77 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali.rej
1 out of 5 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/GsmServiceStateTracker.smali.rej

!!! PATCHING FAILED FOR com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!
!!! patch error for com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali !!!
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Good evening, sir. I have recently com across an app in the store called cyandelta and hope I could get an answer. The app is supposed to download a small file and flashed through a recovery instead of an entire rom. I used APG for pdroid, etc. I am curious to know if using the app/flashing will keep pdroid intact? Or is it required to repatch the rom zip, instead?
[Android Software/Hacking General [Developers Only]] harlequin69:
Success patching pDroid and Paranoid Android 2.23 for Nexus 7!! Thank you very much :)
[Android Software/Hacking General [Developers Only]] KicknGuitar:
Oh god, that was just like stepping on a huge rake. :silly: My apologies. I probably posted that half awake. I understand all the basics now but if I understand you correctly I may be able to patch (this device-specific) ROM trying to select some of the other ROM types in auto_patcher or do you mean using a patch created from a different ROM? It's just a matter of trial and error?

Cheers.

Edit: Jeez, you guys work way too hard on this! I did not expect it so I went to throw you some sixpack money but... So I guess a tip of the hat is all I can do for now. Thanks.
[Android Software/Hacking General [Developers Only]] proudfoot:
I believe you'll need to patch the rom zip (the patched one, after cyandelta patch it). cmiiw What cyandelta does is to create a diff between your current rom zip and the newest zip then patches those diff to your zip to create a new zip.
[Android Software/Hacking General [Developers Only]] XdaProNoob:
any chance to make it work with AOKP JB build 5 Android 4.1.2?

Thanks
[Android Software/Hacking General [Developers Only]] L30nh4rt:
works great with the latest Paranoid Android 2.5

Thanks for your great work and support!
[Android Software/Hacking General [Developers Only]] mateorod:
Hmm. That depends, I guess. What do you want to have work and have you tried yet?

As far as I know, every mod we offer works with the latest AOKP.

./auto_patcher aokpbuild4.zip MOD

And then you'll know...post a log if there are problems and tell us if there ain't!
[Android Software/Hacking General [Developers Only]] alharaka:
Some Small Errors, Not Sure If Significant

I am going to try the first successful build with APG and Autopatcher 2.2.0 on the ParanoidAndroid 2.50 Utacka Nightly Build. But I noticed a few errors in stderr. Just thought I would bring them to your attention, since files appear to be missing in certain places and I am sure that can be important. :)

I will be back to let you know how successful or unsuccessful I was.

UPDATE 1: Had some downtime at work; it appears it did not work, even though flash was successful. When I run PDroid_Release.apk it says my ROM is unsupported, so I guess that means nothing was added. ROM booted fine without issues, so I will reread the first few posts and try again later. Again, I suspect nothing got patched but I will open up the zips and try to determine the difference. Logs forthcoming. Thanks to all you guys for being so diligent!
[Android Software/Hacking General [Developers Only]] dron39:
When i try to download v 2.2.0 from http://techerrata.com/browse/mateorod/pastime1971

it say "Cannot connect to the MySQL Database Server" :(

Please tell me , do i need doing wipe dalvik-cache or cache or something other doings if i want install pdroid.zip from autopatcher on my cm7 nightly?

I flashed it 2 days ago and now i have many installed programs and game and my phone seems to be fully configured. :)
[Android Software/Hacking General [Developers Only]] Px80:
One of the Mods is not shown.. "secure".

I tried to patch my PACman with Extension for Collegedevs Prdoid but there comes only an error.

This time at rebuilding Mms.apk

### rebuild apk ###

... rebuild Mms.apk ...
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 14, --target-sdk-version, 16, -F, C:\USERS\SX125\APPDATA\LOCAL\TEMP\APKTOOL5935684206811853889.tmp, -I, C:\Users\Sx125\apktool\framework\1.apk, -S, C:\Users\Sx125\Downloads\ApGPackages\ApGPackages\ap\tmp20121023110826\tmp\system\app\Mms.apk.out\res, -M, C:\Users\Sx125\Downloads\ApGPackages\ApGPackages\ap\tmp20121023110826\tmp\system\app\Mms.apk.out\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:255)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:324)
at brut.androlib.Androlib.buildResources(Androlib.java:269)
at brut.androlib.Androlib.build(Androlib.java:192)
at brut.androlib.Androlib.build(Androlib.java:174)
at brut.apktool.Main.cmdBuild(Main.java:188)
at brut.apktool.Main.main(Main.java:70)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 14, --target-sdk-version, 16, -F, C:\USERS\SX125\APPDATA\LOCAL\TEMP\APKTOOL5935684206811853889.tmp, -I, C:\Users\Sx125\apktool\framework\1.apk, -S, C:\Users\Sx125\Downloads\ApGPackages\ApGPackages\ap\tmp20121023110826\tmp\system\app\Mms.apk.out\res, -M, C:\Users\Sx125\Downloads\ApGPackages\ApGPackages\ap\tmp20121023110826\tmp\system\app\Mms.apk.out\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:87)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:253)
... 6 more
Caused by: java.io.IOException: Cannot run program "aapt": CreateProcess error=5, Zugriff verweigert
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
at java.lang.Runtime.exec(Runtime.java:615)
at java.lang.Runtime.exec(Runtime.java:483)
at brut.util.OS.exec(OS.java:78)
... 7 more
Caused by: java.io.IOException: CreateProcess error=5, Zugriff verweigert
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:189)
at java.lang.ProcessImpl.start(ProcessImpl.java:133)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021)
... 10 more

patching ADDON does create a update.zip but i get a FC opening Pdroidextension.

Also there is no PA option anymore.

But anyway.. many thanks for the work youre doing!! :good:
[Android Software/Hacking General [Developers Only]] proudfoot:
Not a big deal but, ./autopatcher <rom.zip> -h needs some clean up :)

./auto_patcher cm-10-20121022-NIGHTLY-p5100.zip -h

The Auto-Patcher v2.2.0

### 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 results of ROM check ...
ls: cannot access patches/-h/all/generic/: No such file or directory
... -h patch date has been set to: ...
### supported patch candidates ###
3gdongle :all :generic : latest
ls: cannot access patches/addon/all: No such file or directory
ls: cannot access patches/extension/all: No such file or directory
external_internal :all :generic : vold.fstab.awk build.prop.awk
insecure :all :generic : latest 20120816
ls: cannot access patches/pdroid/all: No such file or directory
secure :all :generic : latest 20120816
ls: cannot access patches/tabletUI/all: No such file or directory
ls: cannot access patches/v6supercharger/all: No such file or directory
voice :all :generic : latest 20120826
[Android Software/Hacking General [Developers Only]] alharaka:
It's usually nice when people read the original post. If you did, you would know you can find the latest updates on their Github mirror. You can even get a tarball or zip archive by clicking here, so you will not need to install git or learn how to use it to pull down the latest version.

Next team, read the OP please.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks for the reports, guys. Like I said, I spent a couple hours moving around symlinks, and I knew that there were going to be a few growing pains. I would have rather tested through the ApG people, but it makes me feel guilty. Like I said, a wrapper script is of highest priority.

Anyway, I will work on tracking down those problems today. If you could all do me a favor and please attach your logs, it tells me where to look for the error. Otherwise I am shooting somewhat blind.

For the person who had trouble recompiling the Mms.apk, that is a permission problem. It only happens for people infrequently, and I don't have a good way to solve it yet. For now, this is what you'll have to do:

tar xvzf patch_tools.tgz
chmod +x (mac or cygwin or linux)/aapt
tar czvf patch_tools.tgz boot cygwin linux mac apktool.jar baksmali.jar signapk.jar smali.jar updatecert.pem updatekey.pk8

That should solve your permissions. Since you didn't upload the log, I don't know if you need to have the which word - mac or linux or cygwin - you need in your command. Use whatever distro you have.

Thanks to the other person for the clean-up with -h, I will do that today as well.
[Android Software/Hacking General [Developers Only]] D-m-x:
Thanks, works good on Paranoid Android 2.23 (Nexus 7)!
[Android Software/Hacking General [Developers Only]] mateorod:
I really can help you best if you attach the whole log. You are using a different command then you used last time, because the first time you had successful patching, it just failed on the rebuild because aapt had lost it's permissions.

The long list of ignored patches is because the program could not tell exactly what ROMTYPE you have, and so defaulted to aosp. Since you already have a framework2.jar, those hunks are ignored. They aren't errors, per se, just think of them as passed checkpoints.

But the patching failure is likely to be that you put in a ROMTYPE last time and did not this time. Try adding "cm" to the end of the command. Unofficial builds (i.e. not from CM directly) sometimes have aosp-looking info in their build.prop.
[Android Software/Hacking General [Developers Only]] chrootz:
@mateorod - You are freaking beautiful! The latest auto_patcher worked beautifully on Synergy_d2vzw ROM (Stock TW ICS). Much better lot easier for noobs like me.

PS. I am gonna donate you some $ for you to grab some beers when I have get paycheck. :D

~/Downloads/ap $ ./auto_patcher Synergy_d2vzw_18Oct12_1047_r77_s.zip pdroid

The Auto-Patcher v2.2.0

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
!!! is not supported yet, trying generic latest !!!
... result of ROM check: version= ics rom= aosp ...
... Using results of ROM check ...
... pdroid patch date has been set to: 20120813...
### unzip rom ###
inflated: system/framework/framework.jar
inflated: system/framework/core.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 ...
### 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
[Android Software/Hacking General [Developers Only]] mateorod:
Ahhhh, that's what I am talking about. I wish I could thank you 20 times, I literally cheered in my kitchen. Some random AOSP ics rom from 2 months ago, and it is all automatically matched.

That is where I am trying to get us all, folks.

Keep posting logs, and I will iron out the random symlink problem.

Now the "-h" flag seems irretrievably broken. and I didn't write it in the first place. So that may be a minute, I will be working from the ground up there...
[Android Software/Hacking General [Developers Only]] Px80:
okay i attached the logfile.

could not upload the .log itself so i had to zip (7z)
[Android Software/Hacking General [Developers Only]] proudfoot:
Tips, rename it to logxxxxxx.txt before upload :P
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
I am on Utacka's Paranoid v2.50 (23 OCT)

I have used kobik's ApG 1.4.0 and it updated Autopatcher 2.2.0 itself. So it tried to patch my rom and it succesfully patched. Everything was fine.

I flashed the update pdroid file and rebooted the phone. it booted also fine. But when i try to launch Pdroid app, it said that my rom wasnt supported it just supports Gingerbread. so it seems like the update pdroid file didnt hack my rom succesfully. since there wasnt any error, what could be the problem with this.
[Android Software/Hacking General [Developers Only]] kobik77:
Uploaded new ApG to deal with aapt permissions issues.

It would take a new update from git or just delete ap folder and run an update to fix permission and tar.

I had a problem patching with extension mod because of this problem, but now it seems fine.
[Android Software/Hacking General [Developers Only]] deepdespair:
Nexus 7 AOKP build 5 failure

Tried the patcher on AOKP build 5 for the Nexus 7. Failed. Attached is my log.
[Android Software/Hacking General [Developers Only]] TheMatrix2000:
Build failed extension

Hello, my ROM is Paranoid v2.50 and i am trying to patch with your autopatcher 2.2.0 under OS X.

Pdroid and v6-supercharger works, but with the extension i get following error at the end:

--------

### copy patch extension/jellybean/pa/ ###

... copying system/media/PDroid.jpeg ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: system/media/PDroid.jpeg is missing in the patch

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /Users/roger/Downloads/autopatcherv2.2.0.zip Folder/./log20121023211239 for any debugging

! patching failed.

! it may be possible to patch /Users/roger/Downloads/autopatcherv2.2.0.zip Folder/pa250.zip using other patch version

The Auto-Patcher v2.2.0

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

-------

I looked in your patch file, but "system/media/PDroid.jpeg" isn`t missing, it's there. Perhaps wrong path to it in autopatcher ??

Log is also attached.
[Android Software/Hacking General [Developers Only]] wkwkwk:
Hi.

I tried patching with auto_patcher 2.2.0 cm-10-20121022-NIGHTLY-n7000.zip with extension mod and:

### copy patch extension/jellybean/cm/20121016 ###
... copying system/media/PDroid.jpeg ...
### jar patch extension/jellybean/cm/20121016 ###
... apply framework.patch ...
1 out of 5 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/GsmServiceStateTracker.smali.rej
!!! PATCHING FAILED FOR com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!

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!!!

Do you want to proceed ? (YES/no)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed framework.patch
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Thank you.
[Android Software/Hacking General [Developers Only]] chrootz:
I have a bigger problem, no problem with the pdroid patch from the auto-patcher however I am having problem with the pdroid app kept telling me that not supported on ICS. Here the screenshot.

I don't know how to fix this problem and I already installed the core.jar, services.jar, and framework.jar in /system/framework and chmod 644 on 3 of pdroid patched files. Any suggest?

Sent from Verizon Samsung Galaxy III
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
That was what i tried to explain. Exactly the same problem even after flashing the pdroid-update zip file on Paranoid v2.50 (23OKT)

Sent from my Galaxy "Paranoid" Note
[Android Software/Hacking General [Developers Only]] dron39:
http://codepad.org/zlxdzZTm

Why it's use patch files from # BID= 20120826 and not from 20121022 for my CM7 2012-10-21 nightly?
[Android Software/Hacking General [Developers Only]] mateorod:
Okay lots of issues. I just got home and saw these things. For those of you that are impatient, there is still the download of 2.1.9 with probably some less bugs. Like I said, I had to redo 200+ symlinks and thousands of lines off code, so some path issues are unfortunately to be expected. But we will get there.

Oh, proudfoot, the "-h" flag fix has been pushed to githubb, thanks for the tip. (edit: unpushed. Bug. But it will be up today, lol)

If I missed your issue, just realize that it is probably the same as one of the below, and that I will continue to hunt these things down.

Update It looks like the Auto-Patcher is decompiling/recompiling for everyone, but is sometimes failing to apply the patches. This is certainly a small error somewhere in the script, help me find it by posting your logs! If you flashed an update.zip but pdroid said that it doesn't support your OS, then you had this problem. I am looking at it now...

But I NEED logs please! I can't fix what I can't see. There is a lot going on in this program, a bunch of matching and arrays. I can't see what is happening if all you say is it doesn't work!

Log, please. Path issue of some sort, I guess...

Thanks, kobik. I don't know why this is randomly happening, but I guess this is why people have to apply permission separately a lot. I am going to package a script or function that does this if necessary, very soon.

If you get an apktool error that references "aapt" look back 10-15 posts for an easy fix.

Did you answer yes? That happens with some of the cm patches for extension, but if you copy that file, it should work. Log please.

Thanks for the report. I have had this happen, and resolved it by rerunning the patcher. I do not know why this is happening, I thought it was a quirk that only happened once. try running it again, maybe twice, and let me know if you still have a problem.

The problem is that you appended gingerbread at the end of your command. You DON"T need to specify Android version, just rom type, i.e. cm, aosp, aokp or pa. When the program saw you had added gingerbread, it matched it to our romtype default, which is AOSP. It then used the patches closest to your build date for AOSP.

We have newer patches for CM7, but I don't think they are working. See y release post for 2.2.0 a page back. I am not sure that they have been working since August or so. Just grab a CM7 from July or August, there is almost no difference. I haven't been able to find out why CM7 won't boot right now.
[Android Software/Hacking General [Developers Only]] chrootz:
I don't know if this would be helpful, Here the autopatcher log and I also include the logcat.txt when I clicked PDroid app then it came out bad news stating No ICS supported etc etc.

:good:
[Android Software/Hacking General [Developers Only]] wkwkwk:
I did but it fails at mms.apk:

### rebuild apk ###
... rebuild Mms.apk ...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed compiling system/app/Mms.apk !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /home/user/Downloads/cm10/log20121024115338 for any debugging

Log:

### rebuild apk ###

... rebuild Mms.apk ...
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 14, --target-sdk-version, 16, -F, /tmp/APKTOOL7487489506910842829.tmp, -I, /root/apktool/framework/1.apk, -S, /home/user/Downloads/cm10/tmp20121024115338/tmp/system/app/Mms.apk.out/res, -M, /home/user/Downloads/cm10/tmp20121024115338/tmp/system/app/Mms.apk.out/AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:255)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:324)
at brut.androlib.Androlib.buildResources(Androlib.java:269)
at brut.androlib.Androlib.build(Androlib.java:192)
at brut.androlib.Androlib.build(Androlib.java:174)
at brut.apktool.Main.cmdBuild(Main.java:188)
at brut.apktool.Main.main(Main.java:70)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, --min-sdk-version, 14, --target-sdk-version, 16, -F, /tmp/APKTOOL7487489506910842829.tmp, -I, /root/apktool/framework/1.apk, -S, /home/user/Downloads/cm10/tmp20121024115338/tmp/system/app/Mms.apk.out/res, -M, /home/user/Downloads/cm10/tmp20121024115338/tmp/system/app/Mms.apk.out/AndroidManifest.xml]
at brut.util.OS.exec(OS.java:87)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:253)
... 6 more
Caused by: java.io.IOException: Cannot run program "aapt": java.io.IOException: error=13, Permission denied
at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
at java.lang.Runtime.exec(Runtime.java:610)
at java.lang.Runtime.exec(Runtime.java:483)
at brut.util.OS.exec(OS.java:78)
... 7 more
Caused by: java.io.IOException: java.io.IOException: error=13, Permission denied
at java.lang.UNIXProcess.<init>(UNIXProcess.java:164)
at java.lang.ProcessImpl.start(ProcessImpl.java:81)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:468)
... 10 more

I wonder what's causing the permission denied, I tried running the autopatcher as normal user and as root as well.