yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Ahh, that is probably the problem above. You are using a mismash of the instructions I have given people over the last few days, which is totally my fault. I should be rescinding information and reposting the current best instructions. Most of what you did above is no longer needed...I just had introduced a bug when trying to fix a workaround, etc.

No matter. Go to your autopatcher directory, and enter the following commands:

git fetch
git checkout 3.1
./batch.sh

If it will not let you swicth to 3.1 branch, then use

git checkout -t origin/3.1

instead of the 'git checkout' line above. That should square you away. I feel pretty confident this will work, so I am not going to bother uploading the zips...if you have any problems, I will upload them right away. I don't want you to have to be unprotected as a consequence of helping test the program :)

Edit: You can reenable the auto-update as well, that was, again, just a momentary thing to get working software out there. The auto-update thing has saved us hundreds of hours, but it can be hard to navigate when a bug or testing zips are out there.
[Android Software/Hacking General [Developers Only]] IRKONIK:
It works! Both ways. I feel a little dumb for not checking the md5sum of the downloaded zip. goo.im is under so much "fire", that either I dropped them or they dropped me. But yeah, nevermind.

Right now I am going to flash my SGS3 first. (So I have a device as backup) and will report back.

Cheers!
[Android Software/Hacking General [Developers Only]] Penman:
Build 20130821
PA 3.98 & CM latest changes ( check their github )
Odexed for better performance
Fiexed Advance option FC in setting
[/quote]

Jep odexed.
I have two new logs for you. I redownloaded all packages via ApG and replaced the Auto Patcher files.
Do you think, the chance of success would get higher, if I'm using Linux?
I could run it on an other machine.

Ap v3.1.0:
http://codepad.org/egCcoPkC

Ap v3.1.4
http://codepad.org/0eCXrm7o
[Android Software/Hacking General [Developers Only]] mateorod:
I would try running it on another machine...something is wrong/not working with your environment, and it is something we haven't seen before. I have had lots and lots of people submit Cygwin logs and not seen this before...what it is saying is that it is looking in the jars (framework.jar, core.jar etc) yet cannot find a classes.dex inside of them. That means one of several things, some of which could be:

Odexed rom (but it is not odexed, is it?)

Jdk installation is corrupt/imcomplete (we extract the jars and their contents with jar utility from jdk. You do have it installed, but is it working?)

Some sort of PATH issue I don't know about (spaces in file names are supposed to be okay, gut have caused issues before, for instance)

We could go in circles trying to find the problem, we may even succeed. We may even find out it is a heretofore undiscovered flaw in Autopatcher, that happens kind of a lot. But mostly this program works as intended, and has for over a year now. So new problems are unlikely to be easy to solve, at least. And several of those potential issues I listed are well outside the scope of the thread here.

If you have another machine, especially a linux box, I would try it. I develop for Linux, the Cygwin and OSX support is a secondary thing that basically causes me massive and regular grief now that the maintainers have moved on. The regular 3.0 branch is more reliable, but patches less roms. I am working to bring the 3.1 up to speed. As of right now, it seems to be working for most people. Good luck!
[Android Software/Hacking General [Developers Only]] DualJoe:
No problem, attached below.

If one day this binary doesn't work anymore you could still pre-process the patch diffs with something like 'dos2unix' text processors (EOL = CR > CR/LF) so they match up to the windows generated baksmali code.

Edit: Not sure if 'dos2unix' is capable of 'unix2dos' though.
[Android Software/Hacking General [Developers Only]] Christoph21x:
ApG with Autopatcher Test 3.1.0 - small issue

Dear Friends

Under Windows using Auto_patcher Test version 3.1.0 under ApG there's just a small issue to avoid successful patching for at least some ROMs:

auto_patcher tries to refer to various backup/restore/creation paths - example: "create update-openpdroid-W:\INSTAL~1\PDA\Android\Desire\ROMs\CHROMI~3.ZIP" which are not suitable under Windows due to the ":" in the file / folder name.

Would there be a way to adjust this?

The according log is attached. Building was successful but files were not able to be saved.

Greetz - Chris

PS/EDIT: Similar result with manual patching under cygwin
[Android Software/Hacking General [Developers Only]] Penman:
Tried it with OpenSuse. Same result

http://codepad.org/CkfHyfPm

It is odexed. Is that a problem? If yes, I'll redirect my complaints to the dev. ;)
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah...I have played with it some,...but it seems like it is a bit of a triple-bind. Supporting all the platforms gets very sticky here. I could process the patches within the script, but it would be extremely, extremely slow. We will see, thanks for the binary, i will experiment with it.

Ok. I tried parsing this information and got rid of this result most, but I guess not all, of the time. I removed the ROMTYPE info from the zip name to reflect that we had moved past needing to worry about ROMTYPES. I was trying to use the ROM name in order to make it more identifiable. But it has become more headaches than it was worth.

I have changed the name of the outputted zips to just have the name of the MODS and the build date of the original rom. You should be okay now, thanks for the info.

Yes, that is the problem. I went and looked at the ROM thread, and it is buried in the changelog "Odexed for performance" which is of negligible truthiness. You can deodex it yourself or find another build.

I have long considered putting in a more descriptive message when encountering an odexed rom, but it comes up so rarely. I guess I should spend the time, could have saved us both some trouble.
[Android Software/Hacking General [Developers Only]] Christoph21x:
Dear mateo

No update available so far... where do I get it to try out?

Greetz - Chris
[Android Software/Hacking General [Developers Only]] w181448680:
Who can help me?

Hey, guys. I found a mistake I do not know where the problem lies. Who can help me? ...

I use VM ubuntu system

use The Auto-Patcher v3.0.295

Then enter the command:

. / auto_patcher N7100.zip pd2.0 aosp

Also tried using the parameters "opempdroid"

Also tried using the parameters "PA" "CM" "AOKP"'s rom, but get the error is the same

But there is a error message:

error: failed android/app/BackStackRecord.smali in framework.jar cannot be remedied

Complete log
[Android Software/Hacking General [Developers Only]] 0.0:
since the ROM sources got updated, I am receiving the same error again. log attached

error: ServerThread.patch in services.jar cannot be remedied
[Android Software/Hacking General [Developers Only]] beginnerteur:
Hello guys,

I tried to patch the last four/five CyanogenMod nightlies for my i9300. I tried on different computers und reinstalled the ApG many times, but I always get the error:

error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied

Any idea? :confused:

Thank you very much!

PS Log is attached.
[Android Software/Hacking General [Developers Only]] beginnerteur:
Thank you very very much!!! :good: You guys are fantastic!
[Android Software/Hacking General [Developers Only]] n00b42:
Hi, i would like to know if you could support RootBox ( http://xdaforums.com/showthread.php?t=1806401 ).

It is a great ROM which uses AOKP,CM and PA features.

Sources are available ( https://github.com/Root-Box )

Tried autopatcher with all ROM Types with same error, see Log file ( http://codepad.org/qq686FmR )

I used to build RootBox myself to include the openpdroid patches.

But as there are no snapshots (of stables) available i have to sync the latest codebase which is often not working / not working at the moment.
[Android Software/Hacking General [Developers Only]] mateorod:
Go ahead and patch...RootBox for Android4.2 is now supported in Autopatcherv3.1.53. Let me know if they end up porting it forward to 4.3.
[Android Software/Hacking General [Developers Only]] Christoph21x:
You all are simply... awesome! Thanks! 3.1.x is a huge step ahead, its granularity increased significantly - so great
[Android Software/Hacking General [Developers Only]] Christoph21x:
[solved] Endless loop 3.1.5 w/ CM 10.1.3 RC2

Dear mateorod

Looks good, but I encounter a problem with CM 10.1.3 RC 2 of Samsung P3110 (download: http://www.get.cm/get/jenkins/40543/cm-10.1.3-RC2-p3100.zip)

The patching runs fine and after (while?) rebuilding MMS.apk, suddenly an endless loop of "yes" encounter on the screen. Seems as if you would set an anser. I waited approx. 3 minutes and cancelled it through CTRL-C.

Screenshot and log attached.

Thanks in advance & greetz from Switzerland - Chris

Edit: solved - see post as per 2013-09-08
[Android Software/Hacking General [Developers Only]] mateorod:
Hmmm...I was just able to patch this on my machine. I did encounter some trouble when aI switched users from 3.1 to master branch. You could maybe try

git checkout master

./batch.sh

I will think about what sort of debugging info I might need to diagnose this problem...that was one of the main challenges of an update this size...all the other parts (help, domain structure, everything) had to be brought in line and is still a work in progress.

Thanks for the report, I will post when I have added some debugging.
[Android Software/Hacking General [Developers Only]] 0.0:
I still have the same error. my ROM is here: http://d-h.st/wqM. log attached
[Android Software/Hacking General [Developers Only]] mateorod:
I think that my attempt to migrate user of the 3.1 experimental branch back to master automatically is failing somewhat. Sorry for that being an issue. You can either migrate to master using git commands, or you can download the 3.1.5 package from goo.im and start again. You will not have to keep doing that, it was just a short-term thing to allow willing testers to try the new branch.

I just downloaded your rom from your link and it works for me, so if it fails for you after we are sure you have migrated to master, then something larger is afoot, because the patches are there. Try once more please, and sorry for the inconvenience.

through git:

git checkout master; git reset --hard; git clean; ./batch.sh

Download 3.1.5 and start fresh
[Android Software/Hacking General [Developers Only]] 0.0:
I am on OSX, so how would I do the git commands?

edit: I think it is working now
[Android Software/Hacking General [Developers Only]] mateorod:
http://git-scm.com/book/en/Getting-Started-Installing-Git

Jeez...I want to say up front that our OSX compatibility is usually a bit behind the rest. Eventually [MENTION=3734621]txoof[/MENTION] gives it a shot and debugs for us. I try and be mindful, but there are a bunch of tiny differences between OSX, Cygwin and Linux shells. I only have a Linux machine, sometimes the others lag.

But it seems like the 3.1 branch was working for you before and I haven't added anything too hard core since yen, I don't think. There is a graphical installer for git on OSX, you can read about it here (the top link, sorry for bad placement.) Once you have git installed, the git commands should be the same. You will need git to get automatic updates, it is pretty much an unofficial requirement at this point.

If you install git, you can delete your old auto-patcher directory, and just start fresh.

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

./batch.sh

And patch as usual.

If you have trouble again, I can upload the patch so you can have protection while we debug, okay?
[Android Software/Hacking General [Developers Only]] 0.0:
it's working now. Idk why git couldn't start. It must be that my brew was outdated. I can now see the .git directory when doing "ls -a." before, I couldn't. everything works now! :)
[Android Software/Hacking General [Developers Only]] w181448680:
I try to update automatically patch

Upgrade to Auto-Patcher v3.1.53

Tried the following code

./auto_patcher WORKING_7100.zip pd2.0

./auto_patcher WORKING_7100.zip openpdroid

都是提示:

error: No matching patches!!

logfile
[Android Software/Hacking General [Developers Only]] mateorod:
As I said above, I would not count on getting pd2.0 support back, I will probably just take it out officially to avoid this confusion. But also, and I just discussed this with someone else the other day, we only support deodexed roms, and I need to go ahead and code in a helpful message to that effect.

It won't be able to diagnose what is going on unless you post the openpdroid attempt. But better yet, could you post a link to the rom you are trying to patch?
[Android Software/Hacking General [Developers Only]] w181448680:
Thanks for your reply ..

I would like to add a ROM N7100 patch Pdroid

This ROM download link:

http://www.hotfile.com/dl/238412305/0edf5e8/N7100ZCDMG1_N7100CHNDMG1_CHN.zip.html

Please help me to check why this ROM cause patches to fail. Extremely grateful
[Android Software/Hacking General [Developers Only]] kanyazsombor:
Patching fails

Hello,

I am so happy that pdroid support is available above 2.3 with your tool!!

Just there is some problem. Somehow it always fails.

Here is my log

my rom's xda thread.

download link to the rom. I am using the Slim-mb526-4.2.2.build.8.1-UNOFFICIAL-20130901-1120.zip

I've set openpdroid mod, and AOSP for rom type.

Thanks for the help!:)
[Android Software/Hacking General [Developers Only]] hanspampel:
Open PDroid Patch didnt work with latest 10.2 nightly for nexus 10.
[Android Software/Hacking General [Developers Only]] flawedkaos:
I have been trying to patch the new CM10.2 nightly and it fails before it even gets started. I get the below error:

Setting new path variable
./auto_patcher: line 2: $'\r': command not found
./auto_patcher: line 4: $'\r': command not found
./auto_patcher: line 7: $'\r': command not found
./auto_patcher: line 11: $'\r': command not found
./auto_patcher: line 155: $'\r': command not found
./auto_patcher: line 156: $'\r': command not found
./auto_patcher: line 160: $'\r': command not found
./auto_patcher: line 165: $'\r': command not found
: invalid optionline 167: set: -
set: usage: set [--abefhkmnptuvxBCHP] [-o option-name] [arg ...]
./auto_patcher: line 168: $'\r': command not found
./auto_patcher: line 172: $'\r': command not found
': not a valid identifier declare: `MODS_LIST
': not a valid identifier declare: `PATCH_DATE_LIST
./auto_patcher: line 178: $'\r': command not found
./auto_patcher: line 182: $'\r': command not found
./auto_patcher: line 187: $'\r': command not found
./auto_patcher: line 201: syntax error near unexpected token `$'{\r''
'/auto_patcher: line 201: `colorize () {

I have the latest from github, well 9/6 is what it says. I have done a reset and pulled the master and still get this error. I am trying to patch openpdroid. I also can't post a log as it says "Error locating log file." Both errors happen regardless of the rom or patch.
[Android Software/Hacking General [Developers Only]] Christoph21x:
I'm not using Git, simply download version...
[Android Software/Hacking General [Developers Only]] 0.0:
I am having the same error as above, but with this ROM, crDroid http://xdaforums.com/showthread.php?t=2395744

I'm using the latest version

sent from my Nexus 4
[Android Software/Hacking General [Developers Only]] wkwkwk:
Hi,

I patched using the latest autopatcher the latest CM10.2 nightly. I see that Llama is still broken.

I'm fairly sure it worked at some point in CM10.1 by using an odd workaround, manually specifying that Phone and Llama are trusted. I see it no longer works.

Has the Llama bug been abandoned or is there a chance it will be fixed?

Thanks.
[Android Software/Hacking General [Developers Only]] Christoph21x:
I think this should rather be Llama's task, don't you think?
[Android Software/Hacking General [Developers Only]] wkwkwk:
Not really. "Llama bug" became a generic name for the cell tower location being blocked, please see bug #1 for openpdroid

https://github.com/wsot/openpdroid_support/issues/1

The bug seemed to have been resolved by CollegeDev but seems to still exist in openpdroid.
[Android Software/Hacking General [Developers Only]] Christoph21x:
Excuse me & thanks for your explanation - Greetz, Chris
[Android Software/Hacking General [Developers Only]] Christoph21x:
[Solved]

Dear Mateorod & All encountering a similar issue:

Mateorod was right: probably an issue coming from AP 3.1.0 TEST (most probably only under Windows)

NO SOLUTION:

- a simple reinstallation in the same directory

SOLUTION:

- reinstall AP completely in another directory

--> probably a registry issue under ApG / Windows

Greetz & thanks to Mat & Co.

Chris
[Android Software/Hacking General [Developers Only]] flawedkaos:
This solved my issues! Deleted the entire directory, downloaded it all fresh, and installed in a new directory at the root of the drive. No errors since. The simplest solution is usually the right one.
[Android Software/Hacking General [Developers Only]] mateorod:
I have seen several of you file bug reports on github for 10.1-RC3. I know that patches with the current autopatcher, and fear that the wrangling moving testers from 3.1 to master broke the autoupdater and packager. I am working on a more institutional fix, but for now, could you try Christophe suggestion, and simply delete the autopatcher directory, then reinstall? I have a new 3.1.6 package up at Gooll.

Okay, this rom is not going to be supported, sorry. It is a odexed stock rom. At one point, I really hoped to start supporting stock, but I can at the very least say that it isn't coming soon.

You need an open-source deodexed rom like CyanogenMod, ParanoidAndroid or others. That rom is over a gig in size, meaning it comes from the phone manufacturer and so I cannot patch it. Sorry.

I rebuilt the 4.2.2 slimrom patches but your rom still failed to patch. But it does not look like your device is supported by SlimRom, this is likely a kang by an outside dev. I can still support it, but you will have to ask the developer to give you a link to his source code.

That is a funny thing...I think I have introduced a bunch of problems by trying to habdle the switch from 3.1 back to master branch. That report is failing because your rom does not have an Mms.apk. But neither does "flo" (new nexus 7) and that patches just fine. There is handling in the script for this scenario.

I would suggets that you nuke your auto-patcher directory, just delete in entirely like Christophe suggests. Then either git clone from github, use ApG if on Windows, or install a new package from our goo download page. Use the new 3.1.6, I think that I fixed the problems with auto-update that I introduced the other day.

glad Christophe's fix helped you, that was an ugly error!

I need a link to the source code to support new roms, even if the error looks identical, the cause if likely that we just need to build new patches for it. My hope is that building up this patch library will soon allow us to be patching these roms automatically- once I build the patches for it, those patches are available for all roms.

It hasn't been abandoned...but some other things took priority. I had to take over all 3 arms of the project and it has been a lot to keep up with. I have some work done towards that end, but not tested or implemented. The everyday work of maintaining and fixing the autopatcher somewhat took over, along with taking over PDroidManager and vetting the OpenPDroid/PD2.0 stuff...you can get easily behind. Coding contributions always welcome.
[Android Software/Hacking General [Developers Only]] Christoph21x:
Dear Mat - I have patched also ROM's without Mms.apk - without any problem. I don't think you re-introduced known issues...

GReetz - Chris

---------- Post added at 08:22 PM ---------- Previous post was at 08:11 PM ----------

Dear All

If I see how much Mat & Urinophria and the rest of the team struggles with issues, and if I see, how easy I solved my own one, I suggest to procede as follows:

Make sure you checked the following things before uploading or reporting an issue:

Make sure, your ROM is DEodexed, not odexed

Try the following procedure and re-patch the ROM - only if THIS second fails, report an error:

Delete the entire AP / ApG directory

Downloaded from fresh (see post #1 ff.)

Create a NEW and DIFFERENT directory with a DIFFERENT path

Install AP/ApG in this new directory

Run & download cygwin/ap/... by running AP/ApG for the first time

Make sure, the Git sync took place

Re-run your patch

Report back, if your build was successful --> and thus your report is obsolete by describing your case in here, so that other users can read through it and compare it with their case.

Report from new, if your problem persists

I suggest, if I see the workload for the team, that we start from scratch and dismissing all reports so far until we get new ones which were following the steps mentioned above

Please excuse me for this proposal, I see Mat & the Team every night working here, answering questions, struggling... now WE should contribute and make sure, our claim hasn't just been solved by simple steps, before reporting.

Hope you can see it the same way... we need the Team back in the DRIVER's seat... not caring for maybe obsolete issues?

I know, you won't like to read what I write, but every developer would practice this with his/her own development as well this way.

This post shall just support..

Greetz - Chris
[Android Software/Hacking General [Developers Only]] Penman:
Next Try with an deodexed ROM

Still Paranoid Android 3.99

Image: pa_i9100-3.99-20130909-deodex.zip

AP: 3.1.6

OpenSuse 12.3 x64

Log: http://codepad.org/mTbthmwf

### jar patch openpdroid/4.3 ###

... apply framework.patch ...
Matching the created file: ContextImpl$42

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

!!! error: No patch sets create the proper ContextImpl file. Please upload log!

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

Any suggenstions?
[Android Software/Hacking General [Developers Only]] Christoph21x:
Tried to patch it here under ApG Win7-x64: same result

Same with build of 2013-09-10.
[Android Software/Hacking General [Developers Only]] psyoptix:
Auto-Patcher, OpenPDroid, CM10.1.3 patch ok but flash fail

I've been trying to get CM10.1.3 (RC2) working with OpenPDroid but have so far failed.

I used auto-patcher (v3.1.56) on cm-10.1.3-RC2-i9100.zip and the patching process seems to have worked OK (see attached log). in particular although there were some fishy messages in the log such as:

and

the script ended with

and produced the 2 files:

update-openpdroid-20130905.zip (1.2KB)

restore-from-openpdroid-20130905.zip. (1.3KB)

So next I put them on the sdcard of my i9100 and rebooted into recovery. (At this point i was already running a nightly CM10.1 with openpdroid patched using autopatcher (but a 4.2.1 based nightly i think, not 4.2.2. like the RC2) and CWM Recovery 4.0.1.5 with only minor bugs since a couple month.) I flashed cm-10.1.3-RC2-i9100.zip without a problem. I also cleared the cache partition and Dalvik cache for good measure.

The problem is when i try to flash the update-openpdroid file I get the following:

Finding update package...

Opening update package...

Installing update...

Installation aborted.

with no further indication of why. Flashing other updates such as CM10.1.3 RC2, Dorimanx kernel and Google Aps all work with out a problem. I even tried flashing the update-openpdroid file using the Dorimanx recovery but i get pretty much the same "Installation aborted" message.

Any ideas what i'm doing wrong, how to fix the problem, or at least how I can find out more information about what's going wrong to help with debuging?