yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] RealPariah:
dunno if this has been brought up, but trying with grouper PA 2.50, and auto psyche (runs fine), the patch for enabling voice falls to apply starting it can't find a framework-res.apk in the Rom after I watched script decompile it without any errors listed and output appears as expected (looks like fully correct decompile output seen listed on other threads for decompile of framework). Submitted log via ApP submit log function. I tried this after using another script it did everything except when framework rebuilt file size was way off (5.77M when original is 9.71M) from my educated guesswork looks like an issue when it says can't find sources on recompile. Not totally sure, but long time computer tech who has tried even updating aapt, and apktool to newer version (1.5.0 on tool) and chasing many many references that all point to I have everything in the right place, version, and steps, I am no deep programming whiz so can't seem to find and fix issue so far.

Trying to enable Voice, pdroid and supercharger appeared totally fine also of interest fresh install newest file listed via Dropbox

Here we go relevant portion of log:

Running autopatcher with the following arguments:
ROM_PATH: /cygdrive/c/Phone-modders/pa_grouper-2.50-.zip
PATCH_TYPE: voice
ROM_TYPE: all

The Auto-Patcher v2.2.0

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= jellybean rom= pa ...
... Using aosp-mod patches ...
... voice patch date has been set to: 20120826...
### unzip rom ###
inflated: system/framework/framework-res.apk
### 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-res.apk ...
... installing framework files ...
I: Framework installed to: C:\Users\user\apktool\framework\1.apk
I: Loading resource table...
I: Loaded.
I: Decoding AndroidManifest.xml with resources...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Done.
I: Copying assets and libs...
### apk patch voice/generic/20120826 ###
No framework-res.apk in your ROM. Not able to patch this file.
### rebuild apk ###
... rebuild framework-res.apk ...
### 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:
Status update--

I have adjusted the aapt permissions, maybe they got fudged during the merge. For the ApG testers you can try it right now. I have also added a script that will go in and fix the permissions for you if you still get apktool errors.

./fix_aapt.sh

This will quickly go in and adjust those permissions and allow you to run the auto_patcher script again. Let me know how this works for you guys, I obviously can only test in Linux. But hopefully that script will not even be needed, I have adjusted the permissions on the aapts themselves.

I have also fixed a major path problem that I BELIEVE is the source of some of these failed patchings.

So I am updating the version on github to autopatcherv2.2.0.1.

Update: Bumped again to 2.2.0.2: Added the '-h' menu back. Please attach logs if you still have problems...it appears to working on my machine, but that is what I said last time....thanks for testing folks.

If you are using ApG and want to help test, go ahead and sync. If you are on Linux/OSX, you can do a git clone, if you have git installed.

git clone https://github.com/mateor/auto-patcher
cd auto-patcher
./batch.sh

That will also pull the fix_aapt.sh script. Remember, we are still trying to get this update up and running smoothly, so if you have trouble, please attach the complete log. I know that it is tempting to just excerpt the error, but please attach the entire thing.

proudfoot wisely noted that to upload the log, you had to rename the extension to .txt. I have changed the program to output log.txt to make uploading easier, thanks proudfoot.
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
On Utacka's Paranoid v2.50 (23OCT)

AP v2.2.0 was patching succesfully but after flashing the update-pdroid zip file, Pdroid app was still showing error (not compatible with ICS/JB error)

AP v2.2.0.2 couldnt even patch this rom. it failed during the patch process.

Here is the log: http://codepad.org/QtLWhpHl
[Android Software/Hacking General [Developers Only]] mateorod:
Edit: you changed the version numbers, huh? OK, look at my next post.

Oh yeah, those are too old. Any AutoPatcher version that you want to use on the latest nightlies will have to be 2.1.9 or later. And for PA roms, 2.2.0 + is your only option for PDroid or extension on 4.1.2.

See, this program is constantly tracking ever-changing source code, with no warnings of what will or will not break our patches. The updates usually contain some script improvements, but usually i have to update because our latest patches no longer work.

So i think that struggling a little through upstream changes can be forgiven. Anyway, for cm10, people can use 2.1.9 for Pdroid and extension. But everyone else is just going to have to help me finish the 2.2.0+ upgrades.

It isnt that those older autopatchers dont work, they work very well. But the patches aren't up to date for the latest roms.
[Android Software/Hacking General [Developers Only]] mateorod:
You arent using the autopatcher correctly yet. You dont need to specify Android version like jellybean.

Only romtype, and many times not even that. Rom types are cm, aosp, aokp or pa. In your case:

./autopatcher ROMNAME.zip pdroid pa

Let me just say that the goal of this last update is to make the above all anyone needs to enter. It has been a bumpy day, but we are getting there. I want to take confusion out as a reason people can't patch roms.

Although i must caution you that Utacka seems to stray pretty far from upstream and sometimes his roms don't patch.
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
Thanks for all of your interest. With 2.0.0 i could patch but didint work and with your latest update i told that i couldnt even patch the rom. I was using ApG 1.5.0 so i thought maybe there is a mistake on ApG. I tried to manual patch and entered the code you have written above, this time it patched succesfully. and just right now i have flashed the update and finally Pdroid app was also able to recognize the patched rom, so i can use it now :victory:

Thank you again and again, dude. I think if that version could even patch Utacka's very fresh nightlie pa's, so this version (2.2.0.2 or 2.2.0.3 i have seen both of these numbers on ApG:) ) seems to be fine for Paranoid :victory:
[Android Software/Hacking General [Developers Only]] sakkath:
This were attempts to make patches with ApG for proid and pdroid extension:

codepad . org/3NUEpB8U

codepad . org/xnow24Tb

Manual patching option was successful for pdroid with nothing suspicious in log at all (haven't tried it out though =))

This is for proid extension:

codepad . org/Mty1E5XF

Process of creating a patch was successful, but with some warnings and errors.

P.S. forgot to report rom name: pa_n7000-2.50-22OCT2012-180756 by imilka
[Android Software/Hacking General [Developers Only]] mateorod:
That extension with the errors is known and is ok. It is just copying over a premade GSMServiceStateTracker.smali. So it will be fine. The other attempts just failed to correctly assess that you were running ParanoidAndroid. But you were able to make it work by specifying 'pa', awesome.

So everything worked for you, great!

Please keep giving reports for 2.2.03 guys. A couple more successes and I am going to bump to 2.2.1 and release the official update for the Linux/OSX users.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
Just patched a One X rom for the first time using this tool, however I had some 'hunks' ignored. WHat does this mean as I never had this issue with a nook rom.
[Android Software/Hacking General [Developers Only]] mateorod:
Ah, looks like that is a Sense rom. All of our V6 patches are for straight AOSP or CM derivatives, including AOKP and the like. This isn't an auto-patcher issue, per se, it is just that we don't have anyone on the team who is building for or making patches for Sense ROMs, of any flavor.

wbedard has been talking about looking into it though, so the time may come, but for now, we don't support any OEM skins. Sorry.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
That's fine, glad I posted and asked before flashing. Do you think I could still run the V6 script on it's own?
[Android Software/Hacking General [Developers Only]] mateorod:
Sure. It won't go to 100% supercharge, though. You should check zeppelin's thread, there are a bunch of stock users there. And his tools use sed instead of patch, so they may work for you.

You probably will have to decompile the the apps yourself, unless the windows gui they recently put out will work. I don't know that it patches any wider than ours does, though. My suspicion is that the auto-patcher has the widest patching ability, since we use the patch tool, which is specifically made for the job. But zep uses sed, and maybe that will work better for your rom. Good luck with it.
[Android Software/Hacking General [Developers Only]] mateorod:
Doubtful. You don't have it quite right. See the bold jellybean up there?

You never have to specify Android flavor. That is, by necessity I swear, read as an aosp rom and since you have a framework2.jar, it uses the aosp-mod patches.

Except you are trying to patch a ParanoidAndroid rom. The portions of your log I excised tell the tale. See RID? That is the patch type you are using. That should say 'pa'. Try this:

./auto_patcher pa_grouper-2.50-23OCT2012-143124.zip pdroid,v6supercharger pa

Profit.

In review: No need for Android flavor {jellybean, any of that.

It is best to try and add your romtype if the patches fail on you. There are only four romtypes: [cm, aosp, aokp and pa].
[Android Software/Hacking General [Developers Only]] mateorod:
Ah, I was wondering why I was seeing that. I need to get with kobik to get that fixed.

By any measure, this is really my fault. I should have thought about how ApG works and realized this update would cause problems for it.

Edit: Just saw your post above. That has recently started happening and I don't know what is causing it. I have a couple of ideas. But I did include a script that should quickly fix the problem...

enter

./fix_aapt.sh

and then run the patcher again.
[Android Software/Hacking General [Developers Only]] mateorod:
No, thank YOU guys for the testing. Only way the program gets better.

Okay, the problem is that you are using a Nexus 7, which does not have an Mms.apk to patch. I have a test for this situation that works on Linux, but apparently was failing on Cygwin. I hope that I have fixed that now.

Sync to 2.2.0.3 with ApG and give it one more shot. If it doesn't work, then I will make Mms.apk a file to be copied over while I investigate further. But this should work now, I think.

also, kobik, when you next have time, I guess it would be best if you could update ApG. Sorry I didn't think to tell you about the reorganization before hand, I didn't even think that it would affect the working of ApG. But it will really confuse and frustrate people if they keep selecting Android flavor, since it breaks the rom probing...so sorry man.
[Android Software/Hacking General [Developers Only]] alharaka:
My first sucess compiling, thanks to mateorod, kobik, and all the other nameless heroes who make this software kickass. So why did I reply to this message.

If you are using ApG, even the current stable 1.5.0 to patch ParanoidAndroid ROMS, click Manual Patching entering the following command:

[COLOR="Red"]./auto_patcher[/COLOR] ../../path/to/your/rom/ROMNAMESHOULDBEHERE.zip [COLOR="Red"]pdroid pa[/COLOR]

A functional example from ApG in Windows (that's right, the path notation is Cygwin, and do not come asking here if you dot get what that means):

[COLOR="Red"]./auto_patcher[/COLOR] /cygdrive/c/Personal/Downloads/pa_n7000-2.50-23OKT2012-002453-Utacka.zip [COLOR="Red"]pdroid pa[/COLOR]

The important part is in red for the kids who did not read anyway, but might be concerned with the parts that are important, and missing them means you cannot read and you will come back here with a silly inquiry. Thanks to one of many PA users who love what you guys do and strive to see the coolest features in their cutting edge ROMS.
[Android Software/Hacking General [Developers Only]] Px80:
done. here is the log but its not well structured.

20854 was manual with extension cm

20615 was done by autpatcher extension.
[Android Software/Hacking General [Developers Only]] TheMatrix2000:
Ok, tried that. Running it 4 times but no luck. I noticed something else though.

The errors are different when i build "pdroid" and "extension" together. Look at the pdf i attached. There are 3 runs in it with Logs and some little comment.

What i did:

- Build "pdroid" ----˃ works, but there is an small issue.

- Build "extension" ----˃ error - doesn`t find a jpeg

- Build "pdroid" and "extension" together ----˃ error - but different - jpeg is found but then comes a different error.

Hope this info is useful. :highfive:
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Hi,

Thanks for your brilliant patching utility, I was initially running it using ApG in Windows but now have my Ubuntu system up and running and have been patching through there.

I pulled the latest version you just updated (2 hours ago or so) and ran it against the CM10 20121023 nightly which I have installed today, patch fails but then successfully applies the replace or copy cant remember the exact wording?? :D

Log is below if that is helpful:

http://codepad.org/0HWg5ctC
[Android Software/Hacking General [Developers Only]] switchgott:
New problem :((

Doesnt work.

With Version from 22.10 it works.

The Auto-Patcher v2.2.03

### verify tools ###

### verify ROM ###

### unzip patch tools ###

### unzip patch patches ###

\vergrößert: system/build.prop

... result of ROM check: RIL= Smdk4210RIL

### probe rom type ###

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

... Using aosp-mod patches ...

... pdroid patch date has been set to: 20121003...

### unzip rom ###

\vergrößert: system/framework/core.jar

\vergrößert: system/framework/framework.jar

\vergrößert: system/framework/services.jar

### create updater script ###

\vergrößert: META-INF/com/google/android/update-binary

\vergrößert: 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/jellybean/aosp-mod/20121003 ###

... apply framework.patch ...

1 out of 1 hunk FAILED -- saving rejects to file 'smali/android/app/ContextImpl$20.smali.rej'

The next patch would create the file 'smali/android/app/ContextImpl$38.smali',

which already exists! Skipping patch.

1 out of 1 hunk ignored

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

1 out of 1 hunk ignored -- saving rejects to file smali/android/net/wifi/WifiStateMachine.smali.rej

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

2 out of 2 hunks ignored -- saving rejects to file smali/android/server/BluetoothService.smali.rej

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

4 out of 4 hunks ignored -- saving rejects to file 'smali/android/service/wallpaper/WallpaperService$Engine.smali.rej'

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

1 out of 1 hunk ignored -- saving rejects to file smali/android/view/inputmethod/InputMethodInfo.smali.rej

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

1 out of 1 hunk ignored -- saving rejects to file smali/android/webkit/WebViewClassic.smali.rej

... apply preloaded.patch ...

!!! PATCHING FAILED FOR android/app/ContextImpl$20.smali' !!!

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

!!! error: failed android/app/ContextImpl$20.smali' in framework.jar cannot be remedied

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] Dreamweaver:
http://codepad.org/Ou8e5Et0

tried to patch latest CM10 of Oct-24 with an error...
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
had the same issue. you have to use "pa" mode, not "jellybean". solution is very easy. on ApG screen there is a manual patch button, push that and try this code:

./autopatcher ROMNAME.zip pdroid pa

of course first you have to path to your roms directory or you can also copy your rom into: "ApGPackages\ap" directory.

with this process i have successfully patched and installed pdroid into my PA v2.50.
[Android Software/Hacking General [Developers Only]] mateorod:
This looks like a completely successful patch.

Okay, until Kobik or wbedard can error check this (or I can get my hands on a Windows machine...) the Mms.apk has been changed to be copied over. Non-phone devices should have no trouble on Cygwin anymore.

This is the same problem EVERYONE who is using ApG is having. ApG will need an update to make this clear, but you DO NOT need to specify Android flavor. It breaks the patching and there isn't any way for me to change that. See the part of your log? That says that you should be using cm patches, but you overrode that by entering the wod 'jellybean' and now it is trying to patch with AOSP patches. try without selecting jellybean or anything like it.

Samr problem. Do not specify Android flavor. Kobik77 will update ApG whenever he has time, he got shafted by me, unthinkingly. I didn't consider that the restructuring would negatively impact ApG. I should have given him a heads up.

So until such time as Kobik can update- do not specify Android flavor (i.e. jellybean, gingerbread, or ics)

Finally to the Mac user who put together that .pdf, thank you. Very helpful, especially adding the screen output. It looks like OSX handles the 'date' utility differently, which is a total pain in the butt. I will look at figuring it out today, but I am working blind with it.

Edit: I meant to tell the Mac user that this breaks our automatic build query-ing, but you can still specify a date from the command line. I don't have your .pdf open in front of me, but use the -h flag to get the various available patch dates. Then just add a 2012* after the pa{ROMTYPE}. That will override the buildquery.

Edit2: I sent you a pm, hope you don't mind. Oh, and pdroid and extension are incompatible, and in fact you need to erase the provacy.db if you are switching from pdroid to extension. On my suiggestion, it looks like CollegeDev is going to retitle his app PDroid2.0, which is good because it is not an Extension so much as a Replacement. We will probably retitle the mod at that point as well...sorry guys.
[Android Software/Hacking General [Developers Only]] TheMatrix2000:
Logs for extension

Sorry , don't know why i can't send it to you as pm.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks, I have actually already pushed two levels of fixes for that problem. You are having a permission problem with aapt. The script now adjusts those permissions automatically.

You got the patcher from github, right?

You can run

./fix_aapt.sh

right now and then run the patcher again and it will probably go through.

If you pull the latest version of the auto-patcher from github, the script now adjusts those permissions automatically. But it is also temporarily fully copying over the Mms.apk binary, because I am having a mysterious problem with a test function on cygwin.

So that problem is double fixed with the 2.2.0.4 version currently on Github.

Please, one favor before you go. will you run these commands in your terminal and tell me if they work? I want to fix this build date query for OSX and then I will release an official 2.2.1 update for everyone.

Just put them in one at a time.

UTC="1350034268"
BDID=`date -r $UTC +%Y%m%d`
echo $BDID

This should output 20121012.

Thanks.
[Android Software/Hacking General [Developers Only]] forumber2:
I'm using Ubuntu 10.04 and auto-patcher v2.2.04. When I try patch a ROM,auto-patcher gives this error;

### verify tools ###
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: patch tool is missing
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Here is the log;

ROOT= /home/forumber/auto-patcher
TOOL= /home/forumber/auto-patcher/patch_tools.tgz
ROM= /home/forumber/auto-patcher/yenib528_14_buyukdegisiklik.zip
ROMX= /home/forumber/auto-patcher/yenib528_14_buyukdegisiklik.zip

### verify tools ###
/usr/bin/patch
/bin/tar
/usr/bin/jar
/usr/bin/java
/bin/cpio

I tried sudo apt-get install patch command but linux gives this;

Reading package lists... Done
Building dependency tree
Reading state information... Done
patch is already the newest version.
The following packages were automatically installed and are no longer required:
libdigest-sha1-perl
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 185 not upgraded.

How can I solve this? Thanks
[Android Software/Hacking General [Developers Only]] Dreamweaver:
with 1.4.0 it worked...
[Android Software/Hacking General [Developers Only]] mateorod:
When you pull it from github, you have to run a prep script first, it is in the README, but I guess I should add it to the OP.

./batch.sh

and then run the patcher again. Tuning the quality of our error messages is slated for a future update, but I may fix that today...

You mean 2.2.0.4, I am thinking? glad it worked, for sure.
[Android Software/Hacking General [Developers Only]] kobik77:
Uploaded ApG 2.0.0.0 that should implement new ap's patches directory structure.

Please let me know how it's going for you with this version.
[Android Software/Hacking General [Developers Only]] blackhawk_LA:
I've made a Pdroid patch for MIUI V4 using ApG. I tried selecting "AOSP MOD" and "AOSP" (as I understand MIUI is based on AOSP source)

The patch is succesfully created, and the ROM boots, but the PDroid app says the patch is not installed.

Any ideas, or simply is not possible to have PDroid on MIUI yet?
[Android Software/Hacking General [Developers Only]] mateorod:
I would like to see the logs on that, for sure. As far as I know, MIUI is completely uncompatible with all of our patches.

ApG literally just got updated, and my guess is that you used the older version and that somehow you had the actual application of the patches get skipped. because I would expect massive patch failure to be honest.

But we don't have anyone on the team who builds for MIUI, so there are no plans to support it.

If anyone builds for MIUI and is will to pump out a couple builds every month, you can contact me.

All ApG users: : Please update ApG, kobik just released a fix.
[Android Software/Hacking General [Developers Only]] Px80:
It succesfully creates the Addon for PACMAN 14.1 but collegedevs prdroid does not run.

Trying with Extension this log comes up.

But with

./auto_patcher romname.zip extension cm

this log comes up
[Android Software/Hacking General [Developers Only]] wbedard:
I'm having a very busy week but I will be spending some "quality time" this weekend with PDE support under AOSP. BTW, I get the Mms.apk error with my own grouper ROM so I think I have everything I need to resolve it.