yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dr4go:
Huh, you're right. Thanks and sorry for the noise. :)

I had always used pdroid 1.32 before, but obviously switched now to openpdroid. To get it work I needed three additional packages: android-sdk-platform-tools, android-apktool and libxtst. Maybe because of the need to also recompile the mms.apk - that was not needed for pdroid 1.32.

Nevertheless one last question: is it safe to ignore the RILSender.smali.rej reject file?
[Android Software/Hacking General [Developers Only]] mateorod:
I have seen CollegeDev talking about this fix for a while, but I haven't seen what he intends. However, there are some divergences between it and OpenPDroid core (which hopefully, they can rebase soon) and may not be present for 4.2.1. If it is still there, let us know.

Shoot kobik you are as much a part of this as anyone.

The plan is to get one version of the patches to work for all the pdroid versions. However, in the long run, we will probably have to let the original app go. As much as we love it (and trust me, I love it. I used the original Pdroid all through 4.1.2) it is just getting really really old. It can no longer be downloaded to any modern devices in Google Play...etc.

We fixed a reflection attack hole for the 4.2.1 patches and did port that fix back to all of the Pdroid patches as well. We do not want to abandon it. But when svyat abandoned PDroid, he didn't leave provisions for the PDroid app like he did for the patches. He made the patches open-source under the GPL 3, which makes them and their derivations open-source. Including the parts of the Android source code that they did, he probably had no choice.

The app was closed-source and I spent the better part of a year working around the fact I couldn't make simple adjustments to the PDroid app. That is why it is good to have an open-source app like PDroid Manager. If CollegeDev or FFU5y get too busy, or struck by lightening or even just disinterested...we will be able to pick up right where we left off. The original PDroid's spirit is as strong as ever, but we may have to move on from the app itself. I will spend some time seeing if I can't bring it up for 4.2,1 maybe this weekend.

I have it working on the AOKP-jb-mr1 roms I tried, but of course I cannot try them all. Do you have a log I could see?

I have not integrated the evervolv support yet for 4.2.1 yet, I am sorry for forgetting to mention that. I have a couple small things to do to ready the actual patches, and then I will get them to poncik (the evervolv maintainer) and get evervolv brought up to speed. Within a week, sorry for the delay,

Thanks.

Karamelos, I don't know what I would do without you,

Hmmm...libxtst is now needed for 4.2.1 in general I think. You are talking about patching the build, correct? To recompile the Mms in autopatcher, all you need is the bundled tools, I think...unless that had been added as an apktool dependancy and I didn't notice. I built the apktool and smali binaries from source personally this time. The smali binaries are the very latest, 1.5.2 and are noticeably faster.

The ignored hunks are fine, they just mean that anything you needed to have pdroid work is already in that shape. A bunch of the little changes scattered throughout the patches are automatically generated through compile, and aren't critical, or even necessary, for the pdroid framework to function correctly.
[Android Software/Hacking General [Developers Only]] scutworker:
Thanks for letting me know and sorting all this out for me and the other people who use Evervolv.

Ta.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
That escalated quickly

Just wanted to give a big thanks to all the Norton/Symantic users in this thread, who helped with our false detection. This mourning I received the attached email. Kobik77, you shouldn't encounter anymore problems with Norton.
[Android Software/Hacking General [Developers Only]] mateorod:
I am literally blown away. That is seriously strong work there, grayfoxmg1. You are a good friend to the project.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
I can't code, so I try and do my best to help in as many other ways as possible. Whether that be troubleshooting, advice, or spamming a major home Anti-Virus software's server to stop making our tools look like they are bad for us. We know perfectly well that we are addicted to flashing roms, and we like this addiction.
[Android Software/Hacking General [Developers Only]] dr4go:
Then I have to disappoint you: I am really talking about recompiling (please see the log file in my first post above). The patching went fine without a single glitch, but then it failed with the following exception: "brut.common.BrutException: could not exec command: [aapt, p, ...". I honestly didn't realize, that it was a simple file not found exception, because I had not installed the android-sdk-platform-tools. As I am on a x86_64 linux and installing the platform-tools would have needed some lib32 packages, I changed root (-> chroot) into a i686 environment... there the libxtst was missing - that's why I also mentioned it. Thanks for that information, didn't know, that v4.2.1 needs that lib.

After that I got a... "Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml" error - also during recompiling the mms.apk, because the android-apktool was missing (I needed to re-open the shell to get the error fixed - just fyi).
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
That's not exactly true, any issues with McFee, Viper, or any other AV software is still there. If anything you should reflect both the OP and your link to my post to probably say something like this:

Tips for people using/or attempting to use ApG:

1. McAfee, Viper, and some other anti-virus programs WILL NOT allow you to download Apg, they quarantine the file because of an WS.Reputation.1 issue. What this means is that only a small percentage(we are talking less than 1%) use our shareware program that has been lovingly crafted and maintained by our fellow XDA member kobik77(big thanks btw love the program)., thus it is seen as an abnormality and treated as a risk. However, this is not true. ApG(and the whole auto_patcher set-up) are 100% save.You can download the file by disabling your anti-virus/firewall program before clicking the download link(addendum: Everyonce in a while my computer still won't download the file so I have to disable everything Norton related and <gag> use Internet Explorer </gag>).

2.If after running the program you get an error and after closing it see what the error was caused by ApG disappears, your anti-virus tagged the running process and followed it to the program and quarantined/deleted it. Again you must turn of AV and firewall stuff BEFORE running the program.

3. Anytime you preform a virus check, it will tag ApG as malicious software(pfft malicious) and remove it making you re-download it.

NOTES: There are absolutely NO virus, worms, Trojans, Athenians, or Persians in this software(though I think a couple of Spartans might live in it ;) ). Likewise, unless someone has overhauled the entire site(which would be really impressive) There aren't any of the before mentioned items on the file-sharing site we download ApG from. So feel free to disable your AV when downloading or using ApG.

NOTE: This use to be an issue on Norton/Symantic products as well, but by following the instructions that I linked to in THIS post, we were rewarded with the e-mail I received in THIS post less than 24hrs after I first put up the link and instructions on how to report the false detection. So next time ApG is flagged by your A/V program, report the false detection. If enough of you do it than we can get ApG off of everyone's virus list.

This has been a public service announcement provided by Grayfoxmg1, have a good day.
[Android Software/Hacking General [Developers Only]] Flashcry.xt:
Thank you for your detailed explanation. I think ill give a try to pdroid manager next weekend when i update my Galaxy to cm10.1. All i was waiting for was an update for your autopatcher, maybe now its really the time to say goodbye to original pdroid. With one whining and one laughing eye cause the spirit, as you said, lives on in you guys :)
[Android Software/Hacking General [Developers Only]] noonecanhide:
official cm 10.1 nightly for Nexus 4 (mako) failing here, too. tried openpdroid.

http://pastebin.com/fCHdYrLG

looks like the same error as above. i'll try it now with an older version.

thanks for your hard work, i am really happy, that 4.2.1 is now ready :)

Update: All mako-Builds are failing, from 9/Jan.
[Android Software/Hacking General [Developers Only]] karamelos:
Your link report no error (or it's me lot or ....more beer i don't now).
[Android Software/Hacking General [Developers Only]] L30nh4rt:
Hi,

first of all i´d like to thank all of you for your great work!

I´m using autopatcher since a long time and think this is one of the greatest projects on xda with the best support!

I´m really happy to see that it is also now working with 4.2.1! Keep the good work up!

Just one short supplement:

since 2 days Paranoid Android is open source again: https://plus.google.com/107979589566958860409/posts/5omnfNLrLqf

hopefully it will now be included again in AP!
[Android Software/Hacking General [Developers Only]] kobik77:
Tried patching CM10.1 ROM with OpenDroid mod and found out that there was a change in the zip files naming.

This of course caused every successful patch to be falsly recognized as failed, as I'm looking for these files on the auto_patcher script end.

I've uploaded new ApG version 2.5.0.0.

ApG/Windows users please let me know if there are permission denied errors in the build process (Look at ApG.log as they are not printed for some reason in auto_patcher log)

http://codepad.org/iYVBcwvm

patch: **** Can't create file /cygdrive/c/Users/Kobi/AppData/Local/Temp/po22l82q : Permission denied

I've tried manually creating files from Cygwin in this path without a problem.
[Android Software/Hacking General [Developers Only]] karamelos:
Hi kobik77 & mateorod

Make rtfm link :p

On linux
[Android Software/Hacking General [Developers Only]] mateorod:
Something funny is going on here. I tracked down your log. I did not understand what you meant before because those packages (sdk, et. al) are not required for auto-patcher. What is happening here is that the auto-patcher could not find the aapt I have packaged with it and so defaulted to the one that was already in your path. Which did not work because you had not, at that point, updated the sdk from 4.1.2. That is why updating the sdk fixed your problem, the libxtst was probably required for the sdk update.

What I do not understand is why the OS could not find the aapt I package with the autopatcher. It is finding it everywhere elsewhere. i am sure of this because otherwise everyone using it would have to, by chance, have the latest apktool and aapt (just released two weeks ago) in their path, which i am sure it is not so. So what got moved or changed with your system? Anything non-standard you know about?

There is, as karamelos pointed out, no error here. Look for the update.zip, which should have the mods in the title and flash it. I have tried to make these things less and less confusing as time goes on...maybe some more explanation is needed. The point is, when patching those files failed, I asked permission to fix the problem and then did so. If using ApG, then ApG answered yes for you. But either way, the auto-patcher looks to have worked in your case.

I could not go to your pastebin link for some reason, It actually kept crashing my browser. But if you have the same errors as above, those aren't errors. I am pretty sure karamelos just checked a mako build below and it worked. i will add some more messages for when a file fails to patch but I am able to fix the problem. It has been a long-standing area of potential confusion.

yeah, we found out maybe three hours before release. I am building now, shouldn't be long. Glad to see they released so we could finish covering all of the roms we covered for 4.1.2.
[Android Software/Hacking General [Developers Only]] mateorod:
Hmmm...I don't know what is happening here...it looks like the patch command is not getting permission to create a temporary file. That is probably not too big of a problem for us, if that is actually what is happening.

It doesn't create an error for us, because the patching process has to be allowed to go through even with failed patches. We then comb the (mini) JAR.log and APK.log for "failed" and then we can track down any specific file that fails to patch and repair it in other ways. But I guess it could be of services to echo any error message from the actual patch command to our log as well- I just had never seen it needed before.

It is likely still creating a working update.zip, since I think that protection of the temporary files is there to preserve original documents in case of a failed patch. But we delete the smali files after the auto-patcher runs, whether or not the patch is successfully applied. So I think, while we do want to solve the bug, it isn't a fatal error at this time.

Unless the zips aren't working?

Thanks for all the work kobik...I did a ton of improvement to help and error messages, but I don't think anything affects ApG as currently structured except

the Android version folders have been renamed froom 'ics' and 'jellybean' to 4.0 and 4.1/4.2. I doubt that matters

the update.zip name. I didn't know that would affect ApG, sorry.

Let me know if you need anything else...
[Android Software/Hacking General [Developers Only]] noonecanhide:
i uploaded the log to my server, pastebin is working for me :)

http://127null01.info/storage/log.txt

the error is, that there is no error :D ApG reports that patching is failed, and i have no update/revert files.

edit: under linux i was able to patch the latest cm10.1 for mako, maguro and grouper. perfect :)
[Android Software/Hacking General [Developers Only]] dr4go:
Oh well... nothing got changed / moved drammatically. It's just a standard bash shell. [promote]Arch Linux FTW![/promote] ;)

But now I know where the culprit lies... it's as simple as it is: the x86_64 linux. The precompiled "aapt" file in your patch_tools.tgz spits out the following when trying to execute it on an x86_64 environment:

./aapt
bash: ./aapt: No such file or directory

So you would need to also include an "aapt" file for x64 systems. :)

Just to note: My chroot for i686 was a bit messed up - that's why I needed the two packages in the end... I've removed them now and everything seems fine. libxtst is still needed.
[Android Software/Hacking General [Developers Only]] mateorod:
Nope, that's not it. Adapt is not dependent on which bit the system is. And the included adapt works fine on 64 bit systems (including mine). At this point, I bet less people have tried it on 32 bit, since you need 64 for AOSP.

I have not had time to really scour your log, and it is possible that the answer to this question is not in the log. I am going to keep my eye on the issue and see if it pops up anywhere else. But we have had over 25,000 downloads since I last changed how that behaves...this is the first report. Doesn't mean that it isn't a bug...just that I am not going to assume it is one quite yet. Did you check the md5 by any chance?

And thanks for the report, the feedback is valuable.
[Android Software/Hacking General [Developers Only]] 4ndr0x:
RootBox is - in my opinion - the best rom available for S3 and S2. It's an AOKP/CM hybrid. All 4.1.2 releases of RootBox could be patched without problems while choosing AOKP in the patcher.

When i try to patch "pdroid", i get an error like "pdroid is not yet available for Android 4.2.1". When i try to patch "openpdroid", i get the error stated above. Haven't tried pd2.0 yet.

Is the pdroid error framework- or patch-related?

Maybe you could take a look into it? Would be nice :)
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
Are you using ApG? if so try again without selecting the ROM type and let auto-patcher automagically pick the best match. If you aren't using ApG, try selecting CM instead of AOKP. The problem with hybrid builds like this when patching, is that if they have been statistically pulling from one tree more than the other, they will register as that try(AOKP), however if the next update features more of the OTHER tree(CM), the old classification won't work. If it turns out to be a 50/50 split(doubtful but possible) auto_patcher doesn't have an AOKP/CM setting so trial and error would be best to find the right setting. If none work than, I would post links to logs for Mateorod, Kobik77, and the rest of us to go over to see what we can figure out. YOu probably aren't the only one with this issue, your just the only one to bring it up.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay...kobik just posted about that this morning. I had retitled the update.zips to reflect which mods were selected and ApG couldn't find them. Kobik uploaded a new version (2.5.0) today. That should fix those problems...

I don't know...a ServerThread issue usually means the wrong ROMTYPE has been chosen. That is not necessarily so, but whatever is causing it, it means we are not close.

If none of the current ROMTYPES work, then I don't have anything I can do without someone being willing to build from source and maintain the rom. But I would try the cm and aosp patches and see what happens. Adter 4.2 gets stable, we are turning our attention to expanding the amount of roms we support, and in a big way.
[Android Software/Hacking General [Developers Only]] pro.aggro:
:good::D
[Android Software/Hacking General [Developers Only]] mateorod:
Since you brought it up...ParanoidAndroid patches have been pushed to my github site. ApG users can sync them down right now.

Any OSX or Linux users can either get it manually or wait until later tonight when I release 2.5.1 (which I have a couple things to do before then).

To manually pull an update, just install git-core. Then:

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

And run the auto_patcher as usual. Anytime you wanted to make sure you had the latest files:

git pull

But I will release the update soon if that sounds daunting.
[Android Software/Hacking General [Developers Only]] pro.aggro:
Will try it instant :D
[Android Software/Hacking General [Developers Only]] nachod0g:
I tried to patch cm-10.1-20130113-NIGHTLY-i9300.zip with OpenPDroid, it patched successfully but after flashing I'm missing the Messaging (Mms.apk) app. I still have the apk in /system/app/ but it's not showing at all in Android.

I've noticed that both autopatcherv2.5.0.zip\patch_patches.zip\patches\openpdroid\4.2\cm\20130109\Mms.apk.patch and openpdroid_1.51_cm-10.1.tar.gz\pdroid_1.51_cm-10.1\JB_mms.patch (from the source patches) are 0 byte files. Is this a problem and could it be the cause? Thanks.
[Android Software/Hacking General [Developers Only]] mateorod:
Haven't heard that before. Can anyone else confirm missing/not-missing Mms.apk for a phone ?(not a tablet, please).

The 0 byte empty file in the Auto-patcher is a symlink, there is over 3 million lines of code shipped with every update of the auto-patcher, if I didn't use symlinks to cover duplicates it would get REALLY insane. You can see where it points to here and then see the patch itself here. But it looks like the cm build patches are missing the Mms.patch, so thanks for spotting that.

I will be looking at this as I wait to hear more.
[Android Software/Hacking General [Developers Only]] karamelos:
+1

mms.apk is MISSING on N7000 .

Just extract it from rom.zip & install it . Openpdroid detect it & notify access

Attached extracted Mms.apk from cm-10.1-20130113-NIGHTLY-n7000.zip
[Android Software/Hacking General [Developers Only]] mateorod:
Okay thanks karamelos. I will get down on that issue tomorrow. When it is fixed, I will update the program, and that will include openpdroid support for Evervolv and the PA support that ApG users already have.
[Android Software/Hacking General [Developers Only]] nachod0g:
Thanks for the explanation, symlinking in those circumstances makes sense. I was going to try patching the source and building manually to see if it helped but I'll wait until the Mms.patch gets added for cm.

I've used autopatcher to patch for pdroid many times before so I don't think I messed up the process. Let me know if you need any more info, and I'll wait to see if others have the same problem.

By the way, when building from source, do we have to manually add the PDroid.jpeg file to \system\media still? Thanks.
[Android Software/Hacking General [Developers Only]] wkwkwk:
+1 - Galaxy Nexus (maguro) on CM10.1

App shows in /system/app but not in the app menu.
[Android Software/Hacking General [Developers Only]] mateorod:
I am not sure about the pdroid image to be honest. It isn't necessary to make the patches, so I don't bother with it. You'll see after the first build. As for the Mms patch, unless it is empty in the other build patch tar balls, you shouldn't have to wait. That patch is the same for all Roms, just pull it out of Aosp.
[Android Software/Hacking General [Developers Only]] dr4go:
You're very welcome. And just to be clear: I have to say thanks for your excellent contribution - not vice versa. :)

I am nearly sure, that is has something to do with it (and just to state that: my x86_64 linux is clean in terms of... I don't have a single lib32 installed on the system. That is why I have the chroot for, which is pure i686):

drago ~/android/pdroid/auto_patcher_2.5.0 $ md5sum autopatcherv2.5.0.zip
dcf96f3c9bfce07243eeabe46555be27 autopatcherv2.5.0.zip
drago ~/android/pdroid/auto_patcher_2.5.0 $ unzip autopatcherv2.5.0.zip
Archive: autopatcherv2.5.0.zip
inflating: auto_patcher
inflating: patch_tools.tgz
inflating: patch_patches.tgz
drago ~/android/pdroid/auto_patcher_2.5.0 $ tar -xf patch_tools.tgz
drago ~/android/pdroid/auto_patcher_2.5.0 $ cd linux/
drago ~/android/pdroid/auto_patcher_2.5.0/linux $ ./aapt
bash: ./aapt: No such file or directory
drago ~/android/pdroid/auto_patcher_2.5.0/linux $ uname -a
Linux bl4hf453lv13h.FPS 3.6.11-ck1+ #25 SMP PREEMPT Mon Jan 14 00:00:12 CET 2013 x86_64 GNU/Linux
drago ~/android/pdroid/auto_patcher_2.5.0/linux $
[Android Software/Hacking General [Developers Only]] Didgesteve:
Thanks grayfoxmg1 for that help and advice.

It's good to see people on the thread helping and contributing.

I have had excellent results with autopatcher in the past, but my latest 4.2 build is refusing to play.

I have been a big fan of Pdroid since it came out, but understand that it needs modifying to be kept up to date.

I would like to try Opendroid, it looks great, but I'm failing to build a patch.

Tried patching with all the different rom types, but get the same error.

I am using Slim 4.2 available here

grayfoxmg1 mentioned having trouble with Slim builds in the past, but have successfully built patches for versions 2.9, 3 & 3.1, it's just this one that is giving problems.

Attached is the error, the same for whichever rom type I choose.

What can I do to fix it?
[Android Software/Hacking General [Developers Only]] kobik77:
I'm uploading a fix for ApG, there was a bug in moving the zip file to the rom's path.

Strangely no one complained so far about it.
[Android Software/Hacking General [Developers Only]] pro.aggro:
Patching PA works!! THANKS

I noticed that, but then i patched again and both zips were saved in the apg/ap folder.