yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Come to think of it...I have not heard how well it plays with ApG (if that is what you are using). Maybe just delete the contents of your autopatcher directory (or move to a safe place) and replace with the contents of the 3.1 package. Then run as usual and post log if trouble!

This is working in the 3.1 package, would you try the experimental zip? I am looking to push it to master this week, so testing is needed.
[Android Software/Hacking General [Developers Only]] pawo99:
I downloaded Autopatcher 3.1.3 from your Goo.im. In cygwin console it shows version 3.1.22. Is this OK? :o

It did this error:

!!! error: No patch sets create the proper ContextImpl file.
[Android Software/Hacking General [Developers Only]] docflower:
Thank you again for your response. My patching with 1.6 failed as you saw in the attachment, but it also failed as you mentioned with the framework which agrees with what you experienced.

About the app not starting after applying my patch. Any suggestions from the patch standpoint (log from successful patch above)?
[Android Software/Hacking General [Developers Only]] mateorod:
Well, I am not sure what happened to produce an update.zip, as I said, the patches in 1.5 and 1.6 are identical except for the addition of aokp-jb patches. So any application of cm10 patches should fail in the same way.

My only guess is that, in cygwin as opposed to Linux, when the autopatcher is invoked without a modtype (pdroid in your case) it produces an update zip of unpatched source. So you just reflashed an update containing the same jars you had before. I am working on the script right now, I will continue to address your time issue.

My real question is what is up with that image? Has anyone else seen that? I haven't tried pdroid without the patches enabled in a long time, but I have never seen it implied that ICS is supported.

Did svyat release a new patcher? Maybe that was the default screen for unknown versions of android, but I have never seen it imply that ICS was supported. AFAIK, this patcher is the only method to have pdroid above GB. Interesting.
[Android Software/Hacking General [Developers Only]] docflower:
At computer again... First attached is a new failed 1.6 patch (framework.patch error) using the command "./auto_patcher rom.zip pdroid cm10."

Second attachment is same command ver 1.5. Thanks for your help.

BTW the apk was from theh pdroid xda page... under cant access market. Its a direct apk download from dropbox.

http://goo.gl/DTg31
[Android Software/Hacking General [Developers Only]] measel:
Motorola Defy, Jordan, CM7

Hi,

tried unsuccessfully patching a cm7-jordan.zip. Stops on the framework.patch.

Used Ubuntu for patching and tried all v1.3, v1.5, v1.6.

Tried this CM7 fork: https://github.com/maniac103/android_device_motorola_jordan/downloads

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed framework.patch
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /home/johndoe/Desktop/ap/log20120815150648 for any debugging

! patching failed.
! it may be possible to patch /home/johndoe/Desktop/ap/cm-7-20120809-UNOFFICIAL-jordan-signed.zip using other patch version

smali auto patcher v1.5.0
pdroid 1.32 patches 2012.08.06.
v6supercharger 0.00 patches 2012.08.06.

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

Thanks for any help.

Searches I tried: jordan, defy, cm7

/edit: WORKED WITH PDROID PATCHER v1.27! (not this autopatcher!!)
[Android Software/Hacking General [Developers Only]] topsign:
is it workable with sense based rom?

i tried with no success.

here is the log.
[Android Software/Hacking General [Developers Only]] Hotfingers:
Hi there,

I tried to get it to work for an XPeria ARC Rom - the JJ Hybrid rom (based on stock ICS, but with lots of AOKP functionality).

I ran the auto-patcher with "-h" and attached the result as "a-patcher-h.txt"

After that I tried all the pdroid versions suggested, and attached all the log files.

Please have a look and let me know if you can support jjdoctor's excellent Hybrid rom.

Thanks.

P.S. This rom is recognised by the supercharger auto-patcher - so I've super-charged it OK.

I'm hoping to use your auto-patcher to enable pdroid on the rom.
[Android Software/Hacking General [Developers Only]] mateorod:
I am going to have to try and respond kind of quickly, I am away from my desk today...but I will be revisiting as many of these problems as I can address.

-We do not have Sense patches yet. I am gong to continue to work on JB and tty and support as wide a group as possible for 4.1. But I will not be personally revisiting ICS except to continue to update the current patch sets. Aosp support should be done any day, then I can look at broadening to OEMs.

-Good catch with the johndoe path.

Try and ensure that there aren't spaces in your path for now

. Pastime has an update to the script he is working on that should mitigate these problems.

My quick guess is that your ROM is odexed? Have you looked inside the services.jar? Simply renaming it won't work for us, you need to decompile the jar for pdroid to work.

-I haven't forgot about the S2, either, I should have some builds on my computer tonight that will let me know more.

For those of you with custom hybrids or device-specific Roms

In this update or the next, we will have an add-on zip that you can download separately from the Auto-Patcher that will contain user submitted patches. If you would like to get support for your favorite hybrid, you can take the first step by setting up a build environment (Assuming you have source, of course). There are countless walk-throughs on XDA, I wouldn't call it an advanced operation. We will be available for help, and you will be giving back to the community. Plus becoming an android ninja! Who doesn't want that? (Besides my wife, who finds all this quite silly...which, like, whatever!)
[Android Software/Hacking General [Developers Only]] Feareilo:
Derp... I don't know why I assumed this auto-patcher would work on odexed roms. I feel like an idiot now. I did read on the pdroid thread that only deodexed ROMs work right now but I assumed that your auto-patcher magically worked with odexed ROMs.

By the way, reading up on your tool was not a wasted effort: I ****ing hate having to switch to Windows so a patcher that works natively on Linux is awesome.

Anyway, I'll try to deodex MiniCM7 tonight and I'll let you know if I have any luck using this tool.
[Android Software/Hacking General [Developers Only]] Theraze:
Trying to use autopatcher20120809v1.6.0 using Cygwin. I appear to get the same extraction error message that mj084 had back in post 195. Specifically:

The log file contained:
[Android Software/Hacking General [Developers Only]] pastime1971:
tar: smali.jar: Cannot change ownership to uid 1000, gid 1000: Invalid argument
baksmali.jar
tar: baksmali.jar: Cannot change ownership to uid 1000, gid 1000: Invalid argument
tar: Exiting with failure status due to previous errors

it is something with a permission issue.

reading man page of tar, it only tries to preserve ownership when you are running it as superuser. are you running it as root or something ?

1. try to set up a normal user and run it as a normal user.

2. try to change tar xvzf to tar --no-same-owner -xvzf inside the auto_patcher script. note that with the second form, xvzf needs -

edit: i changed "tar" part in the script, and attached it here as auto_patcher.txt. try to rename it to auto_patcher and replace the old script with it.
[Android Software/Hacking General [Developers Only]] Theraze:
Thanks pastime1971... that did make it actually give me patch files. PDroid still complains about ICS not working, but that might just be PDroid. Now I need to consider V6...
[Android Software/Hacking General [Developers Only]] Feareilo:
While reinstalling the odexed ROM I was previously using, I notice that it not only wipes data/factory resets. It also wipes cache, sd-ext, dalvik and some other stuff. Shall I try doing that?

It's weird. The dodexed & patched ROM took barely a second to install while the odexed version (nAa's) took like a minute.
[Android Software/Hacking General [Developers Only]] pastime1971:
@ Feareilo

the below is the correct syntax.

./auto_patcher DeodexedMiniCM7.zip pdroid cm7

the below is missing pdroid before cm7

./auto_patcher DeodexedMiniCM7.zip cm7 20120718

it creates log* file whenever you run patcher.

unfortunately, it looks like your rom is not supported because even though it is based on cm7, some changes were made (probably to make it smaller) and that broke the compatibility. or it could be that your rom is based on the old source of cm7 and therefore it is not compatible with the latest cm7 patch. as you can see from running "./auto_patcher ROM.zip pdroid cm7 -h" there are many dates of patches because whenever they change something in the source, it may affect smali, and we need to build a new patch accordingly. (this could the limit of baksmali process, but it is what we have.)

if you can find out that the source of your rom is up-to-date with the current cm7, we are out of luck. if you can find out that it is based on the older source of cm7, and which date, we can try to use the older patch.

---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------

@ Theraze,

try to check md5sum of /system/framework/framework.jar and compare it to that in update.zip (unzip and run md5sum)

if they are same, pdroid app

should

recognize pdroid.

it is more likely that cwm flashing didn't work for your device for some reason. please let me know if md5sum match or not, and we will take it from there.
[Android Software/Hacking General [Developers Only]] measel:
No spaces in folder names here. Thanks anyways.

/edit: I think the source is not 7.2 but some 7.1RC... I'll ask the dev. Would it help?
[Android Software/Hacking General [Developers Only]] Theraze:
Yeah, the framework in the original/restore is just over 4mb, the update's framework is 3.2, and the framework.jar in /system/framework is 3.2, so... yeah. Guess this part may possibly be sort of important, comes up when creating the patch.
[Android Software/Hacking General [Developers Only]] Feareilo:
Oh crap, I can't believe it! I am a dumbass!

Ok, I'll try it tonight. I'm not that hopeful anymore but it doesn't hurt to try. Thank you very very much Mr. Pastime. Even if I don't get it to work, it's amazing what you've done here.

By the way, sorry for my rage-induced posts.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I just tested Cyanogen's 8/14 build for the S3, and it patches fine with the Auto-Patcher. There was some sort of rogue commit around the 10th. Whatever it is, the patching now works.

I was able, finally, to reproduce the errors you got where patch could not find the files. These errors are usually due to an incorrect stripping value (the number attached to "-p" in patching commands.) Looks like this:

The text leading up to this was:
--------------------------
|diff -Npru stock-framework/smali/android/webkit/WebIconDatabase$EventHandler.smali pdroid-framework/smali/android/webkit/WebIconDatabase$EventHandler.smali
|--- stock-framework/smali/android/webkit/WebIconDatabase$EventHandler.smali	2012-06-24 14:05:12.860277172 -0700
|+++ pdroid-framework/smali/android/webkit/WebIconDatabase$EventHandler.smali	2012-06-24 14:05:22.776635799 -0700
--------------------------
File to patch:

I just ran the patcher again, and it went back to regular use. I don't know what caused that, but it is something for everyone to look out for.

If you see errors like this please post. My initial guess is that this is a problem with the smali binaries. Now, this could be due to a small corruption, or even just an error in their latest update. If we only see it this one time, then ok, but please let me know if anyone see it.
[Android Software/Hacking General [Developers Only]] docflower:
I had the same error the first night i dl'd 8.14 cm10. I am dl'ing the rom again and I will to patch it one more time. I have attached both logs from two downloads of the same file. Unfortunately, I received the same error.

Thanks again.

Edit: i attache the wrong second file. Either way, I received the same error you mentioned above.
[Android Software/Hacking General [Developers Only]] mateorod:
Shoot! That looks like cygwin is not equipped to deal with one of my commands. Dang, trying to support all these platforms is really a pain. But we are in luck, I think I can use a Windows box for a little while today, and I believe I know where the problem lies. Give me a little while, ok?
[Android Software/Hacking General [Developers Only]] 0.0:
I actually didn't make any changes. The only thing it told me was to either move or remove ap_scripts and commit or stash auto_patcher. it happens the first time I run it. I deleted the ap_scripts but the error still occurs with auto_patcher. I am on OSX

I am trying to patch a cm10.2 based ROM. the source code is here: https://github.com/djl10-2
[Android Software/Hacking General [Developers Only]] mateorod:
I added some debugging info, which should update to your local copy automatically...could you rerun when you get a chance so I can see what I am working with and post the log?

What happens when you run the commands I suggested, git reset --hard; ./batch.sh?

If that doesn't work, then perhaps delete the (possibly) corrupted git repository by deleting the autopatcher directory entirely and re-downloading/re-installing.
[Android Software/Hacking General [Developers Only]] 0.0:
by running git reset --hard; ./batch.sh, the version of auto_patcher is 3.0.295. I would like it to be 3.1+. I have tried deleting it, re-downloading and re-installing. the same error occurs

so, I went on ahead and just stuck with the 3.0.295 version instead, but I get an error when trying to apply the patches. log is attached
[Android Software/Hacking General [Developers Only]] pawo99:
Mateor, here is log from autopatcher 3.1.3 downloaded from your github. Hope it helps :fingers-crossed:
[Android Software/Hacking General [Developers Only]] mateorod:
Those commands fixed the updater, so they worked. You are using the master branch is the issue. Maybe you installed the 3.1 branch over the master directory, I don't know. Pushing the experiemental zip wasn't meant to be too too flexible as it was suppoed to be short-term.

You need the 3.1 package. Either extract the one you downloaded before, or download it again from the experimental downloads page..

Be aware...the last package has a bug in it for some people...if yuo just want it to work your best chance is the second to lasr package, after turing your network off.

Like I said, the purpose of the 3.1 branch is to catch and iron out bugs before I push to master...at the moment it is still slightly buggy.
[Android Software/Hacking General [Developers Only]] 0.0:
Alright, so I tried the latest package without internet. it started, so that's the good thing. the bad thing is that it produced an error. log is attached. the ROM is cm10.2 based, using https://github.com/djl10-2 source
[Android Software/Hacking General [Developers Only]] mateorod:
Oay...that is working for you, although you have not quite the newest source with the bug I am working on now. You just have a regular old failed patch. I will add a "reservoir" patch for your rom later today. That will make it available for you and anyone else who has a file with a similar error.

Keep your eye here, I will include patches for your rom on 3.1.4 if the source is accurate. If you did not include a link to the binary image above, please do so. If it is up there I will find it.
[Android Software/Hacking General [Developers Only]] 0.0:
where would the binary image be located? like where would I look under when at github source?
[Android Software/Hacking General [Developers Only]] creedicd:
This worked!! PA 3.99 is running great!
[Android Software/Hacking General [Developers Only]] IRKONIK:
Nexus 10 aka manta:

- Rom: http://xdaforums.com/showthread.php?t=2390952

- Log: http://pastebin.com/1V5RarCr

SGS3 aka i9300:

- Rom: http://xdaforums.com/showthread.php?t=1745003

- Log: http://pastebin.com/Yx7ftYdb

Yeah, idk wtf I might have done wrong. Deleted the auto-patcher, got him again, put the 3.1.30 files into the directory, used batch.sh to build the auto-patcher, but still running into errors. The question is: is it my fault? (I guess :p)

Cheers!
[Android Software/Hacking General [Developers Only]] mateorod:
I meant an actual compiled zip of your rom...but no matter, I found one by searching the name from your log. I have pushed patches for yyour rom to Autopatcherv3.1.4...you should dbe able to update the patcher like usual and patch if you want.

I did upload a new 3.1.4 package to the experiemental downloads page. Your rom patches to completion on my Linux box, and I spent almost all of yesterday getting it working on Cygwin. Hope it works for you.

Thanks! If anyone is using 3.1+ on Cygwin please let me know how it goes.

Well, in between when I asked you to try and your attempts, I introduced a bug. It took forever to fix, but I had to have the change in there. The only bug I know about now is if you have a relatively new installation of Cygwin, you may have an incompatible 'patch' binary.

But I think I have fixed your problem as of 3.1.4...at least the problem in your logs as of right now. Do you mind trying again? I would like to push this to master soon, it will make us able to patch MANY more roms than before.
[Android Software/Hacking General [Developers Only]] mateorod:
[MENTION=4293606]DualJoe[/MENTION]

Would you mind talking with me about the experiments you did with the Cygwin update to the patch utility? I have really been struggling with that...how did you roll back to patch 2.6.1?

I have compiled a 2.5.9 binary within cygwin, but I cannot seem to use it?
[Android Software/Hacking General [Developers Only]] IRKONIK:
I'm on Linux, so no cygwim. Patch, as the others, is up to date. But I'll give it another shot soon, and will report back :)

Cheers!

Via Tapatalk 4 BETA, that, surprisingly, is free.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, then it will work for you...an easy way to make sure you have the 3.1 branch is just to use git. Since you have the updater, the repo should already be on your local machine.

git checkout -t 3.1
./batch.sh

And you should be ready to go.
[Android Software/Hacking General [Developers Only]] DualJoe:
The Cygwin setup always provides two binaries (current, previous) so i had no problems jumping back at that time. I'm currently not at my desktop pc and cannot post the last working binary but i guess cygwin has an archive somewhere.
[Android Software/Hacking General [Developers Only]] pawo99:
I have patched unofficial linaro build (MinuxBuild) of CyanogenMOD of 9/4/2013 with 3.1.4 autopacher under cygwin :good:

thank you Mateorod :) :good:

Unofficial Slimbeam linaro build 9/4 can be patched with openpdroid, too. Also latest Carbon nightly for Mako can be patched :good:
[Android Software/Hacking General [Developers Only]] IRKONIK:
Nexus 10 aka manta:

- Rom: http://xdaforums.com/showthread.php?t=2390952

- Log: http://pastebin.com/zCr3gE7F

SGS3 aka i9300:

- Rom: http://xdaforums.com/showthread.php?t=1745003

- Log: http://pastebin.com/FQCSFU6c

New version, new error :)

Cheers!
[Android Software/Hacking General [Developers Only]] 0.0:
it worked! thank you so much! :D
[Android Software/Hacking General [Developers Only]] Penman:
Patching Time!

The new PA 3.99 is out for I9100, but the Auto-Patcher Patch is broken again.

Galaxy S2 aka I9100

http://codepad.org/abjHR2rV

ROM: [ROM][AOSPA:Android 4.3] Paranoidandroid 3.99 [Update 31-8-2013] -> pa_i9100-3.99-20130831.zip

System Configuration:

Windows 8 x64

ApG.2.6.0.2 with AP v3.0.295

UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "tmp/system/framework/framework.jar.out/smali"
at org.jf.smali.main.main(main.java:180)

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

!!! error: failed compiling framework.jar !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] creedicd:
Update AP version

Go back a couple of pages. There are links to the experimental builds for AP version 3.1.x. Down load one then extract the content copy to the location where your AP files are stored, and over write them. Rerun the patching process and you should be good to go.
[Android Software/Hacking General [Developers Only]] mateorod:
Hmm...I had to work kind of quickly...it isn't my Windows box. But I did not see a previous binary directory. I downloaded patchv2.5.9 (2.6.1 declined to compile due to a dependency deficiency) but still had problems. If you get to a pc with a working patch utility from 2.6.1 or earlier, could you send upload it? I would think those binaries would be portable between Cygwin installations, as they are all 32 bit environments.

Ah, there we go. So we are very close. The only issue I am seeing on Cygwin is with patch, so probably close to merging, since those issue would be the same for both branches. Thanks so much for testing, I think you guys can see we have improved the process a ton.

Hmmm...this is new. You are getting very close. It is something with the script and your environment. For instance, I was able to patch both of those roms with the 3.1.4 branch on my machine. Could you tell me a little more about your environment? I have some basic info, but something is going wrong for you that is not going wrong for other Linux users.

I don't know how you installed the 3.1 auto-patcher, either. But something went wrong...look at this line from your log:

Current HEAD: 50aac78ee2fd665c08267babd9eeb7823541d774 Fix SlimRom patches

That is from the master branch. Did you just copy over the script, or did you use git pull? This error would be expected if you were using the script from '3.1' and the patches from 'master'. Did you use the commands I gave before"? Maybe download the latest package and extract it into a brand new directory. If this doesn't work for you, I will upload patches for your rom while we figure it out.

This is a new error to me...something we might expect to see if you were trying to patch an odexed rom. Maybe delete the sutopatcher directory and reinstall? That is the common juju I prescribe to weird Cygwin errors, which works more often than not...
[Android Software/Hacking General [Developers Only]] IRKONIK:
Well, I run Linux Mint 15, got everything up-to-date (git git-core cpio patch unzip tar etc.). If you need more info (specific) tell me :)

I did this: I downloaded the autopatcherv3.1.4.zip and unzipped it, deleted the ~auto-patcher dir., then used

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

to get the master branch (since the downloaded stuff did not work on its own; even with the .config file and

AUTO_UPDATE=false

), then put the downloaded content into the auto-patcher dir., used

./batch.sh

to make the patch and then patched the rom.

This is why it does not work.

If you would be so kind to upload the patches, it would be nice :) So I can check (if I get it to work) the md5's (which should be, so the theory, identical, since we create the same file.)

Maybe the downloaded files are corupt (might be). I'll check it. If they are, I am an idiot for not checking in the first place.

Cheers!

Edit:

I'm an idiot. The zip was corrupt. Now it works. But I will use the method below :) Thank you! Also, I got my patches.