yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Urinophoria:
I've been using pac man and manually patching it, is there some way I can help with that?

I've actually got a handful of roms I've been manually patching, so if there's some way I could turn that into support for this project I'd definitely like to know.

I guess, in short, I'm in xda to learn stuff.. So if someone's willing to point me in the right direction, at least tell me what to research, I'd be more than happy to contribute :D
[Android Software/Hacking General [Developers Only]] karamelos:
Hi

For example:

1 | submit your build.

For that:

First build without patching (& save it)

make clobber without repo sycn

re-build with patch.

Upload your build on devhost or dropbox or ..............

Submit link to mateo (2 link with & without patch)

2 | contribute to this thread

3 | submit modification on git

4 | sharing this project & open source work
[Android Software/Hacking General [Developers Only]] Urinophoria:
Wait... Just a before and after flashable zip? If I'd known that I would have been doing it a long time ago.

If that's the case, ****s about to get real in here. I have about half a dozen that I've been diddling around with patching on on my big desktop (benchmarking, lol). I can clean up the directories and probably upload once a week. I can't keep up with dailies (or Task650 when he gets on an update bender) but I can at least produce 1-2 uploads a week for them.

I don't pay extra for bandwidth, so its just cpu cycles to me.

I'll just rm -rf the ones I test regularly, do an unpatched build, patch it, upload it, rinse and repeat?

I'm still working on steps 2-4, right now my biggest interest is in step 3, so anything anyone wants to tell me about git, I'm all ears.

Now I'm all excited :D

Edit: timely information, the latest updates to PAC-man just broke my local repo... Well I got the notice that I needed to commit or stash or my local WOULD break at least.
[Android Software/Hacking General [Developers Only]] karamelos:
Just build when major commits or broken patch

For git (& over) http://xda-university.com/as-a-developer/getting-started-with-git-version-control

Starting build

grouper (nexus7)

http://wiki.cyanogenmod.org/w/Build_for_grouper#Initialize_the_CyanogenMod_source_repository

Search your device & apply how to
[Android Software/Hacking General [Developers Only]] Urinophoria:
Gotcha, so basically I:

1) build from an unpatched repo sync and and save it

2) Patch, and save it

3) send D/L links for both files to Mateo

4) sync repo (edit: I'll probably build too, just to be safe) daily and when I see:

error: Your local changes to the following files would be overwritten by checkout:
core/java/android/provider/Settings.java
Please, commit your changes or stash them before you can switch branches.
Aborting

or something similar

rm -rf the source tree and start with step 1 again?

Sorry, hope this doesn't count as a highjack. Maybe this info will be useful to someone else too. If I had it (or thought to ask) I would have been contributing a long time ago.
[Android Software/Hacking General [Developers Only]] karamelos:
Go to openpdroid or pdroid2 git

https://github.com/mateor/OpenPDroidPatches the command for clean remove are listed
[Android Software/Hacking General [Developers Only]] JustMeToo:
I admit that I didn't read the whole thread, it's just too long. Why does the program re-download and re-install the java and cygwin every time I start it? EDIT: Must have been because I changed the location of the program.

Is there no way to compile the program so that it will not be triggering the AntiVirus?
[Android Software/Hacking General [Developers Only]] Urinophoria:
Yeah, I saw those, I tend to tinker when left to my own devices though, so if I'm actually sharing what I put together I I like to make it super clean.

Now that I'm actually sharing though, I'll probably create a second folder for each rom for just patching and compiling. That way I can follow the clean remove instructions on one copy and tinker till it breaks on the other
[Android Software/Hacking General [Developers Only]] Urinophoria:
Yes I'd totally love to get involved, I have a pretty modern gaming rig (core i7 960 w/12gb RAM) that's pretty much been sitting idle since I started playing Ingress, but it does compile pretty good :) Gotta warn you I'm pretty green, I've only been compiling from source for about two weeks, but the whole reason I'm here is to learn stuff, so I'm definitely in if you can use me!
[Android Software/Hacking General [Developers Only]] mateorod:
Whoops...already found a new mistake in the auto_updater.

So for those of you looking to try it, it is ready to be test on the newly uploaded

Autopatcherv2.9.845

at our download page or from git.

If you get it from the download page, then the script should run the auto-updater almost immediately. Right after I posted the last 2.9.84 release post, [MENTION=4418789]Urinophoria[/MENTION] sent me builds with AOKP patches. Thank him!

So in the next half hour, new AOKP patches will be up on github, and Linux/OSX users should auto-update from the 2.9.845 build to 2.9.85. I just posted the 2.9.845 build to the download page but am going to wait and see if the auto-updater works before uploading 2.9.85.

Everything should now be up to date...if you see a successful update (or unsuccessful) post your log, please. If you are an ApG user willing to test the auto-updater, see my last post.

[MENTION=4418789]Urinophoria[/MENTION], I got your pm and we can definitely work together. I have to get some sleep, I will pm you tomorrow.

Edit: I messed up big time in my haste and did not add a major component to the auto-updater. Iwon't break, but it won't update for the majority of you either. I have it written, but it will havbe to go up tomorrow sometime. Sorry guys. That is life here at old Auto_patcher HQ. The aokp patches have been pushed to github, so most of you will have them already (git clone, ApG etc.)
[Android Software/Hacking General [Developers Only]] Px80:
Great, patching works like a charm!

Rom: saga_PAC_JB_4.2.2-v22.3.0_20130520-050915 (Without Halo!!)

Date: 19.06.2013

patch: Openpdroid

Thanks! So i've only have to wait for the new Openpdroid app to arrive :)
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I solved my problem from yesterday, thanks for the patience.

Autopatcherv2.9.855 is uploading to our download page and already available through ApG.

Auto-updating is now officially enabled, by default for Linux/OSX users.

Changelogs. If the script auto-updates, it will create it's own changelog.txt.

Windows/ApG users can get in on the unattended updates by commenting out line 1064

AUTO_UPDATE=false # CYGWIN AUTO_UPDATE TESTERS COMMENT THIS LINE HERE!

If you try this, let me know how it works for you, okay? It will probably take a couple days to know for sure, because this download enables the auto-updating...it won't start updating until I push some new commits.

I commit a test update tonight or tomorrow...I have a lot of changes coming.
[Android Software/Hacking General [Developers Only]] siavash2death:
excuse me,but could anyone help me? I have downloaded latest version (2.6.0.2). I can't download needed apps(jara,cygwin) automatically from app and I have downloaded needed apps from goo.im,but everything I tried,app doesn't recognize them after extracting them and if I connected to internet, it tries download java and cygwin,again! and if I not connected to internet,it gives me error that it can't download files and after that it force closes! is there any way to get it working? and I'm sorry if this problem mentioned and solved before!
[Android Software/Hacking General [Developers Only]] Px80:
You have to move it to another location linke D:/ drive. Theres a prob with apg on system drive
[Android Software/Hacking General [Developers Only]] siavash2death:
could you please give me instructions step by step? copy apg in a folder in other drive other than C:/ and extract java.exe and cygwin.exe into that folder? that's all?and have you tried this? I mean manually using cygwin and java with agp?
[Android Software/Hacking General [Developers Only]] IRKONIK:
Push, again.
[Android Software/Hacking General [Developers Only]] MadMic:
Yep - can confirm the auto-updating works :)
[Android Software/Hacking General [Developers Only]] Px80:
I haven't opend java or cygwin manually because i didnt need it.

But to run APG, just copy the .exe file into an folder on another drive. When you run the .exe it will download everything you need.

That's a well known problem with this tool on windows but with this workaround on another drive it works pretty well.
[Android Software/Hacking General [Developers Only]] mateorod:
I can't help with ApG problems...ApG was developed by Kobik77, who for all of his contrbutions, was someone who just stopped by the thread one day. He gave us an awesome front-end and maintained it for over a year. But I haven't seen him in while. I can give him a pm if someone else can confirm that codepad indeed no longer works. I do not think that the code ships with the program or we could try and fix it ourselves. But as a non-Windows owner, I haven't looked, either.

The problems with PA that you listed for both roms is the same problem and is explained at the very top of the OP. Patching fails for RIL$RilSender, which was solved by [MENTION=4661001]AuSSiELaMbChOpS[/MENTION]. It will be fixed in 10 minutes of your time. I have spent a good bit of time trying to fix it automatically, but I need to return and look at it, because users hand editing in workarounds will not play very nice with auto-updating.

It derives from PA having two different forks, one that uses CM frameworks/opt/telephony and one that uses AOSP. We support official PA, with the AOSP version. But the fix is easy.

I think that answers your questions.

thanks [MENTION=501387]MadMic[/MENTION] for confirming the auto-updating works. I tried to be mindful about the various ways users could have gotten the script (download, git clone, ApG) and handle them appropriately, checking for network etc. Glad it worked for you, that is a big start. Being able to automatically push bugfixes will be important down the road.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Well, look at the last line. I tried patching it with the modified file (and yes, I used the ./batch.sh command :D), but then a) my S3 can't send/receive SMS and also has problems with connecting to the mobile network by itself, and b) my N10 fail at patching.

I guess I have to install the ApG again and have another try.

But thanks, as soon as xubuntu is running (which could take a while.. Dumb uefi) I will give it another try via terminal.

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] mateorod:
It got pretty hard for me to follow what was what, especially because of the edits. I see the same error over and over, which usually is solved by the trick.

But there is something fishy going on...manta is a Nexus and should be supported by our current PA patches. It is only non-official builds, the ones that use the jellybean-legacy branch, that need the work around.

Because I just went and tested a manta. I was actually just looking for a jellybean-legacy build to take another stab at automating this, but it worked for me. I patched this pa_manta rom sucessfully with no autopatcher modification.

Is there two different PA builds for the Nexus 10? If so, use the AOSPA build until I figure out how to automate this. As for your logcat error, I will keep an eye open, but this seems to be working for people. After I put out the update to OPD, then we can talk about bug chasing. I just don't have the time right now, sorry. I am pretty sure there are multiple roms for that device that play nicely with OPD.

I am going to take another crack at automating AussieLambChops' workaround for PA jellybean-legacy branch. It really doesn't fit into our structure as is, but I would like to wipe that bug out if I can.
[Android Software/Hacking General [Developers Only]] IRKONIK:
The Rom you posted is the exact same one I tried to patch and which failed. :confused: I guess it's my PC's fault. Well f*ck :D Only good thing is that I figured out how to "bypass" my uefi problem. I am going to setup Linux this afternoon. By my knowledge about Linux I hope that by tomorrow I have it all running and some answers.

It weirds me out that it's windows fault. This OS isn't worth jack sh*t. -.-

Even weirder that it took me so long to finally figure that out.

Thank you for all the time you put into this project and into a few people who still encounter problems (like me)

Also, to the next pa version I'll so a full wipe on all my devices. Maybe that helps.

Cheers, and thanks again :)

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] mateorod:
Okay...

Auto-patcher v2.9.87

is up on github and ApG

I have NOT added it to the download page...for OSX/Linux users- if you have network access you should be able to auto-update to the latest version. I will add it to the download page eventually, but I want to see what happens with the automatic updating.

Improvements include:

Fixed ParanoidAndroid Ril$RilSender failures. You should no longer have to edit the patches if you use ParanoidAndroid unofficial builds.

This was as big a pain as any I have had...but it should no longer be an issue *

Updated apktool to a custom build of 1.5.3- this should work much better with SlimRom's and I am hoping perhaps have some impact on the missing Mms.

The missing Mms is the last big bug I am working on before we start on Autopatcher 3.0. I am hoping the recent changes make some impact. Please, please submit autopatcher logs of any disappearing Mms.

The long-threatened obfuscation of provisional use.

If you want to know how the autopatcher handled any errors it encountered, you will have to read the log...but it should now be explicitly obvious whether we believe the program ran to success or not.

for command -line users---color :-o

* Thanks to AussieLampbChops for the original fix and the edits which finally nudged me into figuring out what was going on.
[Android Software/Hacking General [Developers Only]] wafro:
mateo,

I hope this will not declared as spam. Patching with ParanoidAndroid 3.60 for Samsung Galaxy S3 works like a charm now. Even the previous bugs disappeared. I've got an excellent signal strength, can send/receive sms and even make calls :) Will do further researches and report in.

Thank you so much! Will spend you some bucks when returning home!
[Android Software/Hacking General [Developers Only]] MareleSef:
Hey guys, I have a noob question here.

Is it possible to patch a official Samsung ROM from I9505 with this tool? Idd like to be able to have OpenPDroid on my S4 but also Idd like to keep my stock ROM.
[Android Software/Hacking General [Developers Only]] User_99:
Read the OP an you will get the answer...
[Android Software/Hacking General [Developers Only]] IRKONIK:
Would you maybe be so kind to upload the zips and send me the links in a pn please?

Thank you :) zippyshare or uploaded are pretty good and fast hosts

Via Tapatalk

EDIT: For those who have a problem with Linux: Use a virtual machine! VMWare's VirtualBox is free and very good. How to set up p.e. ubuntu, well go watch some youtube videos! :D

But how do you get all the rest? Like Java 7? "patch, tar, cpio, git"?

Well, here is Oracle's Java 7. (Not the OpenJDK, which I did not get running.)

Open the terminal, and type for:

-git:

-patch:

-tar and tar-doc:

-cpio

I guess you see a pattern ;)

Then, if you haven't done that already, download "autopatcherv2.9.87.zip", linked in the first post's bottom, and extract it.

Place the zip files you want to have patched in the extracted folder.

In Xubuntu (or any other *ubuntu fork) open the terminal either via right clicking "open terminal here" or via the classical way and navigate to the "autopatcherv2.9.87" folder.

The rest is perfectly described in the first post. :)
[Android Software/Hacking General [Developers Only]] KingKuno:
@ mateorod:

Did you fix the issue with network location ?

And I use ApG but it is not up to date "2013.05.30. (v2.9.8) Improve apk handling: fix disappearing apks. New opd: evervolv,slim".

When comes the update for it ?

Thanks.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Which issue with network location? I use tasker to turn my wifi on/off based on network location and it seems to work fine. I did find in another thread (I think it was Synergy for the s3) that you have to press and hold on the tasker, secure settings and secure settings helper entries in the PDroid manager, then when the entry is highlighted, hit the extended menu (3 dots at the top right of the screen) and select "allow all".

For some reason, simply allowing everything in the "by permission" menu that you open up by tapping the app doesn't do it. you have to press and hold then hit allow all. I'm assuming you'd have to do the same with Llama or whichever app is looking for network location. But I have a dozen or so apps I use on a regular basis that use network location in some way shape or form and I've had to do that with all of them.

Once that's done, you can go through and set up specific permissions inside the app settings for PDroid manager, barring of course network location, but you have to allow all first, then configure the individual permissions.

Also, APN is very important, depending on ROM/device. I can kill it quick just by picking a different APN.

---------- Post added at 11:28 PM ---------- Previous post was at 11:16 PM ----------

Short answer: No

Long answer: The autopatcher targets 7 specific AOSP based ROMs (including AOSP itself), and happens to work with several others due to compatibilities produced by the targeting of the AOSP ROMs. The official ROM isn't AOSP based (like AOKP, CM, PA, and the like) it's a heavily modified derivative, with major differences the autopatcher can't compensate for.

Its POSSIBLE to manually patch stock based ROMS, but beyond the ken of most. (way the hell out of my level of capability) Your best bet would be to find a stock based ROM that you really like, that the developer of that ROM already patched, then install PDroid Manager. They're very rare though and may not exist for your device.
[Android Software/Hacking General [Developers Only]] blackhawk_LA:
Hi, I'm having problems trying to make a pdroid patch for AOSP 4.1.1 . The phone is Xiaomi M2S (here you can find the ROM: http://miuiandroid.com/community/th...i-m2-2s-latest-is-qdt14-with-changelog.18969/ )

This is the log from ApG

http://codepad.org/6P2qPLmf
[Android Software/Hacking General [Developers Only]] asushtcevo:
please HELP, autopatcher fails!

Hello,

I'm a big fan of the work you guys are doing. However, I can't seem to get the autopatcher to patch openpdroid onto my rom. I am running autopatcher on ubuntu 13.04 and have attached the entire log file. Any help/ fix would be greatly appreciated! The rom I am using can be found here: http://xdaforums.com/showthread.php?t=2098121

direct download link to the rom if you don't want to read through the post: http://d-h.st/G0i

Thanks for the great work and work in ensuring our privacy! :good:

HTC EVO 3D CDMA Sprint S-OFF

Rom: WILD FOR THE NIGHT CM 10.1 CDMA - June 21, 2013

HBOOT: Juopunutbear 1.50505050
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, the problem with the multiple mods was my fault...I added something late last night that broke it, as Caldair pointed out to me. I have reverted that change and will take it back to the lab, sorry. If you have ApG for Windows, just update the script. If you use linux or OSX, it should update automatically and work if you try again.

Sorry about that...but one question...did you try tabletUI? It looks like apktool was having trouble decompiling your SystemUI.apk. But maybe that was a consequence of the bug I introduced. Try again and let us know, ok?

Sorry, we don't support MIUI. The list of supported roms is on the OP...we only cover those and then very close kangs of those.

Looks like that is a release from the self-styled Tean Hydra of dastin and albinoman. Those roms are almost exact copies of regular CM10/CM10.1, except for one or two changes. One of those changes (I think it is for WIMAX, whatever that is) breaks our patches.

I have had many bug reports from their users...to the point where I went and reported to albinoman exactly what commit was breaking the program. I don't know if he responded, but he did not revert or address the problem. Maybe point dastin to the issue and he can contact me if he wants. Quote my post to albinoman, it has all the info.

Here is where I explain to Autopatcher users

Here is my post to to "Team Hydra"
[Android Software/Hacking General [Developers Only]] blackhawk_LA:
I know, but since this one is not MIUI, but an AOSP rom I thought it could work. Won't be possible to have PDroid on it?

Thank you!
[Android Software/Hacking General [Developers Only]] Magissia:
Hello, works perfectly after updating, thanks you

Regards
[Android Software/Hacking General [Developers Only]] SecUpwN:
The latest Auto-Patcher is giving me headaches on MAC. Log attached. What am I doing wrong?

Network is enabled, trying to patch AOKP 4.2.2 (Release 22.06.2013) by helicopter88.

./auto_patcher: line 1172: syntax error near unexpected token `>'
./auto_patcher: line 1172: ` git fetch origin &>> "$LOG" || no_network_access'

I'd be happy if you would provide a helping hand, [MENTION=4342828]mateorod[/MENTION]. Thanks will be given!
[Android Software/Hacking General [Developers Only]] mateorod:
SecUpwn...my guess is that you are using OSX, right? I just got a report that line is not playing nice with OSX. You can do two things...erase the "&" symbol from that line, which may work but is unfortunately not promised to, as OSX testing is incomplete.

The other thing you can do is easier, just open up the .config file and set AUTO_UPDATE to false. That will skip most of the new code and should make it work as before. Sorry for the trouble...kind of a big feature and it is likely to be a bit rocky, unfortunately. I have already fixed that line in the github version, but I have not released a new package yet as I have some other fixes to work on.
[Android Software/Hacking General [Developers Only]] SecUpwN:
This didn't work, but..

..this did. Thank you for helping out! I think the auto update within the script is awesome, I'm sure you guys figure out a way to detect the OS where the script is run on and let the script automagically initiate the right update process. Keep on groovin'! :cowboy:
[Android Software/Hacking General [Developers Only]] KingKuno:
Hi,

I have the issue with the missing mms.apk file, too.

I use CM10.1: http://xdaforums.com/showthread.php?t=2315448

So which mms.apk I have to use ? These: http://xdaforums.com/showthread.php?p=38695226#post38695226 ?

Where must I copy the file ? Or must I use the default apk ? Or must I only wipe cache and dalvik cache ?

Thanks :).

Edit: Well, I wipe my cache and dalvik. It works. I hope these was the right solution, or ?

Thanks for your gread answer. Not it works. I opened Pdroid Manager and go to "Netzwerkstandort" (Network Location) and allow all, so I allow only "Online Status erzwingen" (Force status online), because that was missing. Was that right ?
[Android Software/Hacking General [Developers Only]] Urinophoria:
I think that would force it on globally, which would have the desired effect as well. Providing you are setting the permissions per app as to what gets access, you shouldn't have any ill effect.

When I get a minute I'll post some screenshots as to what I was talking about, it's a subtle difference to the same end, and not a very intuitive feature of pdroid manager

Sorry, took me a bit. Attached pics, basically the way I've been doing it, I'd press and hold to select the specific app I want to give access to, instead of network location itself. Then I open the menu box in the upper right corner.

Sent from my SGH-I747 using Xparent Green Tapatalk 2