yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] SecUpwN:
I did not ask about an ETA, neither do I request that you patch anything for me. If you're not comfortable with what I post - not my problem. I have very deep respect for the people developing Auto-Patcher and APG. My latest question was due to another smali error that did not come up in the previous version of Auto-Patcher/AOKP - it's sad to see people making fun of each other here instead of helping each other. You could as well keep your "pseudo-anger" for yourself, certainly seems like you jumb on the bandwagon of flaming me although I never heard something productive from you (must be your username). How about getting a boxing bag? The way I see it: Everyone will get their proper pay back in life one day. So thanks for nothing, nobody will be able to make me stop loving XDA or give up on Auto-Patcher. Keep rocking, [MENTION=4342828]mateorod[/MENTION] & co! :)
[Android Software/Hacking General [Developers Only]] IRKONIK:
Push! I don't understand what the log says.. Would somebody please be so kind to help me..

Thanks in advance :)

Cheers!

Via Tapatalk
[Android Software/Hacking General [Developers Only]] Caldair:
Sorry, this is Off Topic since its not really development related, but I just wanted to share in case anyone missed the nice writeup on the portal by pulser_g2 yesterday about the current state of Android App Permissions and what you can do about it.

So, what can you do about it? Well in the article the only solution offered by name is OpenPDroid, and it is actually mentioned a couple times! Heres a link to the article,

XDA - Android Permissions: Permissively Insecure?

I recommend you give it a read if you've got a free minute. I just wanted to share this, figured it would be appreciated here.

We are lucky we do have people looking after our privacy/freedom of choice!

Thanks and Kudos to everyone involved with any of the PDroid projects!!:highfive:
[Android Software/Hacking General [Developers Only]] Febby:
Hey [MENTION=4342828]mateorod[/MENTION]

It appears that the patches for AOKP are broken again on the ATT samsung galaxy S3 (I747)

AutoPatcher LOG: http://codepad.org/T9qY6qFg

ROM thread: http://xdaforums.com/showthread.php?t=1766684&page=2701

Take your time, thanks for the great work! =)
[Android Software/Hacking General [Developers Only]] remmian:
Patching error: likely failed to find build.prop

W7-64 created subfolder "auto_patcher" on desktop as stated in OP. (Took down Comodo FW and stopped AVAST.) Ran as admin, still no joy.

Trying to patch sgt7_10.1_20130328-acclaim-meghd00t.zip (http://goo.im/devs/meghd00t/sgt7) for Nook Tablet. The error says it's an unrecognized ROM and likely cannot find build.prop. Tried ROM type "cm" then each of the others with same result. Anything more I can do?

http://codepad.org/uxJEb1BT

Also, I noticed the "external_internal" mod was missing from the available choices. ?? Thanks much!
[Android Software/Hacking General [Developers Only]] Urinophoria:
I (manually) patched that for personal use last night, seems to be working on my phone.

If you'd like, and if you promise not to go to that dev with any problems you have with it, I can upload it. The only thing I've found wrong so far is that his OTA updater always thinks you're on the wrong version, and it's right, so you have to shut it off.

Naturally, if you update the rom through OTA or his links, the patches will go away. So, at the rate he releases updates, it's a very temporary solution for you. Pretty much means no chance of timely updates, since I'm doing it the hard way and could barely keep up with him when I was just wiping and flashing.

If nothing else, his development rig makes my laptop look like the weak sister, it probably takes me 5x as long to compile from source as it does him.

I patched a fresh sync of his repos as of about 16 hours ago. But it's absolutely an unsupported version, so you'll have to take it as is.
[Android Software/Hacking General [Developers Only]] starbright_:
Patchin the CM10.1 for Defy (20130610) failed for OpenDroid:

http://codepad.org/1E5Uv8oZ

As advised I tried it 2 times. Hope that log can help. Help is welcome.
[Android Software/Hacking General [Developers Only]] Marmotte51:
Known not to work on Quarx build ...
[Android Software/Hacking General [Developers Only]] remmian:
Was this directed to anyone or just a general statement? I ask because it didn't work for me, but how do I know which ROMs are built on Quarx? (Sorry, total newb...)
[Android Software/Hacking General [Developers Only]] Marmotte51:
CM for defy is made by Quarx and patching with pdroid or openpdroid don't work since CM10 ... It's in the first post at "support" I think. It's directed to the guy who asked one post above mine.
[Android Software/Hacking General [Developers Only]] starbright_:
This is me.

Sorry, now I see the statement about Quarks Roms.

That is bad news - no Privacy on Defy with >CM10. What a pity. Someone knows about background?
[Android Software/Hacking General [Developers Only]] IRKONIK:
Some news about the S3 GT-I9300: CM10.1 works, but aosp and pa (by Gokussjx) don't.

The only way aosp and pa do not fail at patching is aussie's "mod", but if I flash the zips created by this method, I have errors. (logs are a few posts above)

Is there any chance of getting it fixed? Or shall I give up on this project? :(

Via Tapatalk
[Android Software/Hacking General [Developers Only]] Didgesteve:
No one makes fun of people who genuinely deserve help, or are new to the thread. But all you ever do is ask people to do/build/make things for you. I don't really see any helpful contributions in anything you've posted. Why not stop cluttering up the thread asking people to fix stuff for you and get on and build it yourself.

Earn the kudos for being someone who fixed a problem, and get some people on that thanks button.
[Android Software/Hacking General [Developers Only]] raziel23x:
I am trying to patch my Motorola XOOM Stingray

Running autopatcher with the following arguments:

ROM_PATH: /cygdrive/c/Users/Gerald/Downloads/cm-10.1-20130611-NIGHTLY-stingray-tabletUI-20130612-update.zip

PATCH_TYPE: v6supercharger

ROM_TYPE: cm

The Auto-Patcher v2.9.8

### verify tools ###

### verify ROM ###

### unzip patch tools ###

### unzip patch patches ###

### probe rom type ###

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

!!! error: unknown ROM version : generally means cannot find/read build.prop

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

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>

example: ./auto_patcher CM10.zip cm

Use ./auto_patcher -h for the help menu

HERE is my ERROR log

http://codepad.org/G0ZlloXK
[Android Software/Hacking General [Developers Only]] mateorod:
Just as a general note...I am out of town and I have almost no Internet. Sorry to any new comers who may be looking for support due to the portal article. I can barely get signal on the hill I am currently on.

I will be workimg on my local copy of the OpenPdrood update but any experienced users will be appreciated if they can help answer any requests for help...even if that just amounts to "probably not suppprted".

Back on sunday!
[Android Software/Hacking General [Developers Only]] dschense:
CdmaServiceStateTracker.smali

Anybody who can help with this Error on I9300 Samsung Galaxy S3 PA 3.60 Rom ?

I didn't find any soluton.. :(

The Auto-Patcher v2.9.8

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
dekomprimiert: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.2.2 rom= pa ...
... Using pa patches ...
... openpdroid patch date has been set to: 20130213 ...
### unzip rom ###
dekomprimiert: system/app/Mms.apk
dekomprimiert: system/framework/core.jar
dekomprimiert: system/framework/framework.jar
dekomprimiert: system/framework/services.jar
dekomprimiert: system/framework/telephony-common.jar
### create updater script ###
dekomprimiert: META-INF/com/google/android/update-binary
dekomprimiert: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
... decompile telephony-common.jar ...
... installing framework files ...
I: Framework installed to: /home/dschense/apktool/framework/1.apk
... decompile Mms.apk ...
### copy patch openpdroid/4.2/pa/20130213 ###
... copying system/media/PDroid.jpeg ...
... overwriting system/media/PDroid.jpeg from openpdroid ...
... overwriting ContentResolver.smali ...
### jar patch openpdroid/4.2/pa/20130213 ###
... apply framework.patch ...
Reversed (or previously applied) patch detected! Skipping patch.
6 out of 6 hunks ignored -- saving rejects to file smali/android/os/Looper.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/internal/os/BatteryStatsImpl$Timer.smali.rej'
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
... apply services-gps_fix.patch ...
... apply telephony-common.patch ...
27 out of 78 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali.rej
3 out of 9 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/PhoneFactory.smali.rej
1 out of 15 hunks FAILED -- saving rejects to file 'smali/com/android/internal/telephony/RIL$RILSender.smali.rej'
3 out of 20 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/SMSDispatcher.smali.rej
!!! PATCHING FAILED FOR com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali com/android/internal/telephony/PhoneFactory.smali com/android/internal/telephony/RIL$RILSender.smali' com/android/internal/telephony/SMSDispatcher.smali !!!

File for which patching failed:
---------------------------------------------

CdmaServiceStateTracker.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

You only need to report this if running the program gives you problems!!!

Do you want to proceed ? (YES/no)
[Android Software/Hacking General [Developers Only]] karamelos:
For all debugging user:

Auto-patcher generated a log file (look in your folder).

Post or copy pasta all log, no partially please.

& another point (optional but necessary for win time) past link of your rom.

Thank in advance

At this question what you see ?

Sent from my pdroided Nexus 7
[Android Software/Hacking General [Developers Only]] dschense:
Oh, sorry.. forgot to paste the end of the log:

... replace com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali ...

File for which patching failed:
---------------------------------------------

PhoneFactory.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

You only need to report this if running the program gives you problems!!!

Do you want to proceed ? (YES/no) yes
... replace com/android/internal/telephony/PhoneFactory.smali ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed com/android/internal/telephony/RIL$RILSender.smali' in telephony-common.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>
example: ./auto_patcher CM10.zip openpdroid cm

Use ./auto_patcher -h for the help menu
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
seems an attempt to patch the latest CM 10.1 for my Galaxy S3 failed...

Using ApG version ApG.2.6.0.2.exe

attempting to patch cm-10.1-20130612-NIGHTLY-d2tmo.zip

it worked on cm-10.1-20130304-NIGHTLY-d2tmo.zip

log... http://codepad.org/AwJHsc8C ...any thoughts?
[Android Software/Hacking General [Developers Only]] a-id:
[MENTION=4661001]AuSSiELaMbChOpS[/MENTION] can you compile actual Mms.apk from CM 10.1 with OpenPDroid patch? Patched with Auto-Patcher Mms.apk still disappears from the list of installed apps after zipalign.

P.S. I've even so found a way to patch the file so that it does not disappear after zipalign, if someone needs it there is link to Mms.apk from CM 10.1 RC5 here.
[Android Software/Hacking General [Developers Only]] chuSmu:
Hey there,

I have a problem with installing Open PDroid Manager as i posted in this thread:

http://xdaforums.com/showthread.php?t=2303979&page=2

The gist of it is that the installation process itself is running without any errors. Creating the update/restore zip and the flashing process seems to work. The thing is, when i try to run Open PDroid Manager it says: "The PDroid core has not been detected on your device".

But when I install a new app it asks me to configure Pdroid Manager (this little notification in the bar). When i attempt to that and click the symbol the app force-closes.

I am using a Samsung gt I9000. Its rooted and running on the latest CM nightly and Android 4.2.2.

SimonTS was so kind to direct me here and told me to run ApG and post the entire text output from the log.

It's in the attachment. It'd be nice if you could have a look at it.

If there is any information missing I'll gladly provide it.

Thanks in advance, any help is greatly appreciated.

chuSmu
[Android Software/Hacking General [Developers Only]] mateorod:
Top of OP has easy workaround for RIL$Sender errors.

You are using old patches i don't know why. Try deleting your APG folder, running batch.sh, or manually patching with directions on OP. Your ROM needs the cm patches made in May.

Do you have a log? Reports are that is fixed...

That is just the output of the file, not the log. Look a couple of posts above, karamelos tells where the log is. But what I see is that you are running the program wrong somehow. It is unzupping your whole ROM...maybe ApG needs to be reinstalled. It may not be your fault but I cannot know until I get the whole log.
[Android Software/Hacking General [Developers Only]] a-id:
No, it's not fixed, here is my log: View attachment ApG.zip
[Android Software/Hacking General [Developers Only]] dschense:
Found error..

Exact issue is the following part of the patch:

invoke-static {v10}, Lcom/android/internal/telephony/RIL;->access$200(Lcom/android/internal/telephony/RIL;)V

When I modify the telephony-common.patch with the code below and run ./batch.sh again it patches successfully and the update zip applies correctly without causing the phone process to continually crash:

invoke-static {v10}, Lcom/android/internal/telephony/RIL;->access$000(Lcom/android/internal/telephony/RIL;)V

Do ./batch.sh again and run ./android-patcher.sh <Rom.zip> openpdroid pa.

I got the warnings again.

After the warnings I had to do "yes" some times for including static parts.

Update.zip and restore.zip created successfully. Runs great on my i9300

Kaaaaatsching...tapatalked...
[Android Software/Hacking General [Developers Only]] Deviant Ollam:
i deleted the whole ApG folder and let it pull down Java and CygWin and everything from GitHub.

it successfully patched cm-10.1-20130612-NIGHTLY-d2tmo.zip and cm-10.1-20130612-UNOFFICIAL-primoc.zip

i'll be experimenting with CM 10.1 on my Galaxy S3 and my HTC OneV NinjaTel phones tonight. woot!
[Android Software/Hacking General [Developers Only]] IRKONIK:
Ok, the following:

1) ApG can't submit the error logs anymore. --> http://www.isup.me/codepad.org It's down [12:53 Amsterdam]. How about pastebin.com?

2) Patching PA Manta (Nex 10) is suddenly broken. It worked with all versions before 3.6. Bad thing: I can't submit a error log besides this: AP-Log http://pastebin.com/v4M6ChBn

3) SGS3 GT-I9300's PA "works": I can patch it, ApG does not want to send an error script. Also: I can call now, and even end the call. But I can neither send nor receive SMS. Logcat: http://pastebin.com/PR7BhyAF (14 sec. and a b*ttload of info. Sorry)

Yeah, that's all ATM. :(

Cheers.

PS: This didn't work either. -->http://codepad.org/rQQ80tw2 (Codepad works again. Daaaamn!)
[Android Software/Hacking General [Developers Only]] takota6:
I would like to patch for Sense 5 ROMs. could someone with experience point me on the path to learn how on stock.. Txs

Æaaa..\„/
[Android Software/Hacking General [Developers Only]] IRKONIK:
The first post seemed tl;dr huh? Patching stock Rom is AFAIK impossible. CM, AOKP, AOSP, PA. Choose one of them!

Via Tapatalk
[Android Software/Hacking General [Developers Only]] chuSmu:
Hi again. Reinstalling apg did the job. Wow thats kinda embarassing :D. I should have at least tried that. Well anyway ...thanks a lot. :)

I believe the update function didnt work. Either for apg itself or for openpdroid.
[Android Software/Hacking General [Developers Only]] sudisk:
Hello,

I've had the same issue. I dared flash the zip that it produced and I had one single problem. I have a carrier that does not have national coverage and use national roaming with another carrier. I have an app that tells me whether I'm on regular network or roaming.

The app FCs on startup when I flash the update zip. Flashing the remove zip bring things back to normal.

Does anyone know what may cause this issue ?

Edit: I'm an idiot. I did not fully read openpdroid OP stating that cell tower info was always blocked, which must be the cause of my issue. Too bad.
[Android Software/Hacking General [Developers Only]] takota6:
Not true , not true at-toll , I've known 2people to patch t.w..I thought I would ask here first without the S.A. answers

Æaaa..\„/
[Android Software/Hacking General [Developers Only]] IRKONIK:
Push!

Via Tapatalk
[Android Software/Hacking General [Developers Only]] Sh0wt1me:
Hi,

I get an error trying to patch this ROM

Here's the log

Any Help? ):

Thanks in advance! :)
[Android Software/Hacking General [Developers Only]] Keltek:
Hi all,

I detect an issue with AutoPatcher v2.9.8 using CM10.1 (nightly) and OpenPDroid.

I used your autopatcher script for modify nightly builds of CM10.1 for my LG Optimus 4XHD and with latest version I found an issue.

After I install the patch for OpenPDroid generated by autopatcher, the Mms.apk seems to be invalid. Here is output from logcat of installed ROM.

I/PackageManager( 483): /system/app/Mms.apk changed; collecting certs
W/PackageParser( 483): Exception reading AndroidManifest.xml in /system/app/Mms.apk
W/PackageParser( 483): java.lang.SecurityException: META-INF/MANIFEST.MF has invalid digest for AndroidManifest.xml in /system/app/Mms.apk
W/PackageParser( 483): at java.util.jar.JarVerifier.invalidDigest(JarVerifier.java)
W/PackageParser( 483): at java.util.jar.JarVerifier.access$100(JarVerifier.java)
W/PackageParser( 483): at java.util.jar.JarVerifier$VerifierEntry.verify(JarVerifier.java)
W/PackageParser( 483): at java.util.jar.JarFile$JarFileInputStream.read(JarFile.java)
W/PackageParser( 483): at java.io.BufferedInputStream.read(BufferedInputStream.java)
W/PackageParser( 483): at android.content.pm.PackageParser.loadCertificates(PackageParser.java)
W/PackageParser( 483): at android.content.pm.PackageParser.collectCertificates(PackageParser.java)
W/PackageParser( 483): at com.android.server.pm.PackageManagerService.collectCertificatesLI(PackageManagerService.java)
W/PackageParser( 483): at com.android.server.pm.PackageManagerService.scanPackageLI(PackageManagerService.java)
W/PackageParser( 483): at com.android.server.pm.PackageManagerService.scanDirLI(PackageManagerService.java)
W/PackageParser( 483): at com.android.server.pm.PackageManagerService.<init>(PackageManagerService.java)
W/PackageParser( 483): at com.android.server.pm.PackageManagerService.main(PackageManagerService.java)
W/PackageParser( 483): at com.android.server.ServerThread.run(SystemServer.java)
E/PackageParser( 483): Package com.android.mms has no certificates at entry AndroidManifest.xml; ignoring!
W/PackageManager( 483): Failed verifying certificates for package:com.android.mms

By this the Messages application (for SMS and MMS) is unavailable. Did I make something wrong way or is this just an issue of too fresh of Mms.apk application from CyanogenMod?
[Android Software/Hacking General [Developers Only]] Dexxmor:
From the OP If your Mms.apk disappears, you can just erase dalvik cache in recovery and reinstall the apk found here.
[Android Software/Hacking General [Developers Only]] mateorod:
I come back in town tonight and will be looking through the thread when I am back in WiFi range. Unfortunate that the Mms issue is still unsolved but I am thankful that someone was finally able to catch it in a log cat. We will be able to fix it for good I suspect.
[Android Software/Hacking General [Developers Only]] Keltek:
If you read my whole message, you must read there is an error validating certificate of application. I always wipe Dalvik if install new ROM or part of ROM.
[Android Software/Hacking General [Developers Only]] Urinophoria:
..... delete
[Android Software/Hacking General [Developers Only]] mateorod:
Okay I am back in town...I will do my best to try and respond to requests tomorrow. I have another test for the GPS big fix I'm the pipeline and will be looking at the MMs disappearances again. Someone caught it in a logcat which will help greatly.

I saw that some patches are maybe broken...I will check tomorrow and rebuild as I can.
[Android Software/Hacking General [Developers Only]] mateorod:
The answer (as posted several times) is that I have been out of town for a week. Things break upstream, so we fix them when we can. If you constantly use the latest nightly, then your releases will sometimes break when the roms update. This is a non-negotiable cost of doing business when you chase experimental upstream projects. I have supported every single rom in our supported list for over a year. With very limited outliers, if you choose any rom from the last year it will patch. But there is sometimes a lag time in between release and updated patches. That is the cost of porting to binary packages instead of to source code.

Anyone can add OpenPDroid to any rom, you just have to use my source patches.They work for all Android roms 2.3.4+ and have been scrupulously maintained since early-ICS. But I realize some people don't have time/energy/ability/willingness to build from source, so I provide and work on the Auto-patcher as a service. My attention is unfortunately divided as the maintenance and integration of the PDroid core has become my responsibility by default.

Every related project is an open source project. I accept contributions from anyone. I give push access to anyone who wants to regularly commit. The rate of improvements and updates is exactly equivalent to the coding community's willingness to provide them.

Thanks for your report. Use the last release until I get a chance to rebuild for your rom and bring it current. I support PACman roms because a user volunteered to build the patches. But they have disappeared as well. I try and keep it up out of a sense of obligation but when upstream is under major surgery (read: Halo) things break more often.
[Android Software/Hacking General [Developers Only]] XDAcat62:
Thanks so much for your response, I guess I just stepped in at a bad time - again I don't want to make it seem like I'm being super whiny and not thankful about it, it's just confusing for me to see things "magically" break and get fixed so often, as well as the backlog of reports! I'd also like to apologize because weirdly after trying the patch for CM, it worked (!?!). I'd tried every single other kind of rom and then that one just randomly compiled without error and is running fine.

I hope this post can help someone else - yes, try every rom version, even if it's not your rom, before you give up :)
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Hey mateorod, I haven't disappeared mate just been really busy with work and study I have my last exam tomorrow for this session. More then happy to produce a new build tomorrow afternoon so the PACman patches can be updated. :thumbup: