yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
New AOKP patches are available in Autopatcherv2.9.5 , which should fix any AOKP problems from 0514 onwards. They are available in ApG or github right now. AussieLambChops is going to build new PACman patches tonight and then I will push a release to our downloads page. But I bet many of you can get the new AOKP patches right now through ApG or github.

I just blindly believed you and i wish I had gone back and looked for your post. I spent three+ hours making new patches for ParanoidAndroid but they aren't needed. You do not have the exact same error. Your rom fails to patch in the RIL$RILSender file. look at the very top of the OP, there is a easy fix for you.

paranoidAndroid only officially supports Nexus devices and a few others. All other devices they leave to others and very loudly disassociate themselves from them. those forks need the workaround on the OP. You do too.

Sorry, don't know anything about Liquidsmooth. Have you tried CM patches? If they don't work then I guess no joy.
[Android Software/Hacking General [Developers Only]] Px80:
Still getting this error with latest version.

log

!!! PATCHING FAILED FOR android/provider/Settings$Secure.smali' !!!
!!! patch error for android/provider/Settings$Secure.smali' !!!

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

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

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

On the PACman v. 22.2.0
[Android Software/Hacking General [Developers Only]] Febby:
AOKP by task650 patched fine finally. Thanks a lot [MENTION=4342828]mateorod[/MENTION] !! :)
[Android Software/Hacking General [Developers Only]] mateorod:
As far as I know, PDroid2.0 only supports CM10.1 and a very few stock roms. Maybe CollegeDev pulled my changes that ports to other romtypes, but I kind of doubt it.
[Android Software/Hacking General [Developers Only]] SecUpwN:
I'm starving for PDroid 2.0 on AOKP 4.2.2. :(
[Android Software/Hacking General [Developers Only]] DualJoe:
Tried cm patches. Gives different errors but still no joy.

The rom is a mix-up from different sources indeed (at least aosp/cm).

Maybe it will work in the future...
[Android Software/Hacking General [Developers Only]] wildland:
Thanks! Applied without errors and working on the latest nightly.
[Android Software/Hacking General [Developers Only]] SeeDoubleYous:
Is it possible to patch a Samsung Stock ROM aswell?

I would like to patch http://xdaforums.com/showthread.php?t=2087177

Thanks:)
[Android Software/Hacking General [Developers Only]] Febby:
Not at the moment using autopatcher. :)
[Android Software/Hacking General [Developers Only]] Maddinuser:
Hey I was using temasek's rom for Samsung Galaxy S3.

It provided OpenPdroid Patches for each new version.

How do make those Patches for P.A.C Rom?

Or is it necessary to patch the whole rom?
[Android Software/Hacking General [Developers Only]] sabret00the:
I keep getting

When trying to patch CM10.1 RC2 for the HTC One X. What am I doing wrong?
[Android Software/Hacking General [Developers Only]] Febby:
You got to select the openPdroid patch rather than the pdroid 2.0 patch because you are attempting to patch a 4.2.x ROM.
[Android Software/Hacking General [Developers Only]] swiggs98:
First time apg'er here...

I installed and updated the latest autopatcher. Selected openpdroid and cm. I pointed it to the 5-17 d2spr cm10.1 nightly and started. It then failed stating that 156 of 158 hunks failed. Error: failed... ServerThread.smali in services.jar cannot be remedied.

Also, the openpdroid patches folder was named with a date of 02-19. I thought there were several openpdroid updates since then?

I have gone thru the troubleshooting guides with no luck. No antivirus issues, not located on desktop, etc.

Any help would be appreciated!

Edit: Attached AP Log
[Android Software/Hacking General [Developers Only]] wafro:
So no new patches for ParanoidAndroid? Workaround is not working as reported many times:

http://xdaforums.com/showthread.php?p=39556985#post39556985

http://xdaforums.com/showthread.php?p=39699548#post39699548

http://xdaforums.com/showthread.php?p=40313546#post40313546

Just want to know. If you are not planning anything on this I have to go back to ParanoidAndroid based on Android 4.1.2 ;)

Wish a nice weekend

Cheers
[Android Software/Hacking General [Developers Only]] mateorod:
Those logs show a successful patching, as I feel has been said before. If you are having non optimal experience while the program is tunning, you jus have to wait while I work on the update. But new PA patches aren't going to change anything. I have bug fixes for a couple of the known issues, but time is short. A couple of those (location for instance) are known issues, the others may just be specific to your experience.

But the work a rounds or new patches are only if patching fails...you don't need that.

Edit: [MENTION=4781306]swiggs98[/MENTION]: I do not see why ( I would probably have to download your rom and I am not at home) but it looks like the autopatcher thinks your rom as built several months ago. I see that the build date on the zip says May, so i do not know why that is offhand. it is not something we have had a problem with at all lately.

Anyway, you need to probably select later patches. I do not kno how to do this exactly with ApG. Is there an area that allows you to select date? if you open up a manual patching ( a cygwin terminal would be easy) just enter something like this:

./auto_patcher YOURROMSNAME.zip openpdroid cm latest

And the latest patches should hopefully work for you.
[Android Software/Hacking General [Developers Only]] sabret00the:
Apparently I haven't applied the latest patches, where as I've definitely got v2.6.0.2 anyone know why this ain't working?
[Android Software/Hacking General [Developers Only]] swiggs98:
I tried Cygwin manual patching and I get the following error.

error: No openpdroid patches for cm on latest~!!​

I went a few days back to the CM10.1 RC2 build and it completed with a few interesting observations. It failed on the two patches below, but continued. And second, it still used Openpdroid patches dated 02-19. I have searched high and low and can't find where to get more recent patches... I assume I need more updated patches than that. I again tried the Cygwin approach and got the same error as above.

patch error for com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali !!!

File for which patching failed:

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

CdmaServiceStateTracker.smali

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

askconsent final = yes: for com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali

!!! patch error for com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!

File for which patching failed:

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

GsmServiceStateTracker.smali

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

Anyway, I don't mind flashing something to give it a shot, but I like to have a higher degree of confidence that what I am about to patch will be worth the time.

Any idea on whether these two errors matter or not?

Any idea on how to get the latest patches? The OpenPDroid github has patches that are just as old but the XDA thread seems to have tons of updates with no reference to where they came from. I will probably post this specific question in that thread too.

Thanks a ton already. I love the auto-patcher... it is a beautiful thing.
[Android Software/Hacking General [Developers Only]] jahrule:
That's college dev's app which checks for his patches. And you patched with openpdroid patches so you should use the openpdroid app. Please read the OP (original post aka the first post)
[Android Software/Hacking General [Developers Only]] sabret00the:
Apologies, I was told that OpenPDroid doesn't work with 4.2 (autopatcher) and so to patch with it but use PDroid 2 once it was patched.
[Android Software/Hacking General [Developers Only]] jahrule:
No need to apologize just stating what's going on ;) yea.. Things are a little confusing. Hopefully we will see a merge and everything will be right in the world of phone privacy :)
[Android Software/Hacking General [Developers Only]] elliwigy:
am i missing something? where the heck do i download v2.9.5??

edit: nvm, im noob lol. i figured it out ;)
[Android Software/Hacking General [Developers Only]] SirGeraint:
I've successfully been using autopatcher for CM10.1 (on my Samsung Galaxy S3) for a few months now. It worked for the 20130516 NIGHTLY but not after that. I got autopatcher v2.9.5 but that doesn't help. What's odd is v2.9.4 has "patches/opendroid/cm/4.2/20130322" but v2.9.5 only has "20130219". I see there's a "aokp/4.2/20130514". So I am guessing that new cm patches are needed. I've read the last several pages of this thread but I am not sure if this is currently being worked on. If so, thanks. If not I thought I would let the developers know. If anyone has a solution let me know.

The error I get is:

156 out of 158 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej

!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!

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

!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied

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

Thanks
[Android Software/Hacking General [Developers Only]] owilsky:
patching failed

I also use the autopatcher for some weeks now, it always worked, but not for the last cm 10.1 nightly (I patch openpdroid):

... apply services.patch ...
156 out of 158 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej

!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!
!!! patch error for com/android/server/ServerThread.smali !!!

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

!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] Kimi123:
Autopatcher does't work with M7 nichtly and Pdroid-Patch

same here
[Android Software/Hacking General [Developers Only]] meviox:
The patch error is most likely due to the new mali r3p1-01rel1 blobs merged on 05/17 into the repository:

https://github.com/TheMuppets/propr...mmit/08db5b635b4f294ad63cdc4f492bc53e3d832fbb

https://github.com/TheMuppets/propr...mmit/1e9b984c60e90e7f5ee0163e017a27066327b243
[Android Software/Hacking General [Developers Only]] SimonTS:
Yep, identical error on the LG Optimus 4X HD. Guess we'll just have to sit back and wait for a fix.
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, actually it is the inclusion of the 20130322 patches that was the mistake. Every once in awhile i get reports that the patches are broken and so I spend the time to fix them, but then when testing it turns out they are not needed. The 0322 patches is an example of this, last weeks PA patches are another.

They should have been deleted not accidentally shipped. but they do no harm, they are functionally identical to the ones from February. This last breakage you guys are reporting is likely a result of the new PIE service, there is a small commit to the SystemServer, which is one of the most volatile files in our patches.

I am rebuilding for CM today and will replace those patches ASAP. I had not pushed the 2.9.5 update to our download page because I was still waiting on a new PACman build. I will see what I can do to get both of those out in a timely manner.

Thanks for the reports.
[Android Software/Hacking General [Developers Only]] SirGeraint:
Thanks for the info. And thank you so much for your work on autopatcher.
[Android Software/Hacking General [Developers Only]] poo706:
Would this happen to be /system/bin/system_server? I use a tweak that replaces that file, should I not be?

[poo]
[Android Software/Hacking General [Developers Only]] IUnga:
I also have a next error: log

I want create patch for cm10.1 (Temasek)
[Android Software/Hacking General [Developers Only]] xFluffyx:
Galaxy Nexus CM 10.1 also an error:

my log
[Android Software/Hacking General [Developers Only]] mateorod:
Autopatcher v2.955

has been pushed to Github and ApG (NOT to the download page yet)

If you are on Mac or Linux and you cannot wait until tonight, you will need to get it from Github! I am building new PACman patches right now, when those are done I will push a new download,

Improvements are one:

Fixed broken CM10.1 patches.

No all of the modified files are system jars or apks...dont replace those files. That list is (telephony-common.jar, services.jar, framework.jar, core.jar and Mms.apk). The SystemServer class is a java class inside the compiled binary (in this case services.jar). o that tweak is fine...but if you want the V6 supercharger, only use the autopatcher to apply it. Any other method obliterates PDroid.
[Android Software/Hacking General [Developers Only]] poo706:
I'm using my own slimmed down version of NOS Turbo Shot. It replaces sqlite3, system_server, and libcurses.so. Everything else is added binaries, init.d scripts, build.prop tweaks, and cron support. So I'm pretty sure that I'm not adversely affecting openpdroid. Thanks for the reply.

[poo]
[Android Software/Hacking General [Developers Only]] meviox:
Works for me again, thanks!
[Android Software/Hacking General [Developers Only]] IRKONIK:
This does not help at all, I have still the same error --> codepad.org/a8SIQA2w

Is there any fix?

Via Tapatalk
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry i guess no Team Eos then.

I bet you forgot to rezip the patches. Run the batch.sh script so the patcher will use your modified patches. PA's practices drive me up a tree.

in the terminal (cygwin or otherwise)

./batch.sh

I have something in mind for this for the bigger autopatcher 3.0 update...but the OpenPDroid update has to be completed first.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Ok, let me explain what I did: opened /ApGPackages/ap/patches/openpdroid/4.2/pa/20130213/telephony-common.patch in my notepad++, searched for the 3 lines aussie posted, changed them from 200 to 000, saved, then clicked in ApG "Manual Patching", used the ./batch.sh command to rezip all the stuff, then pulled my rom in, chose openpdroid and pa, clicked start and waited to get the errors posted above.

What did I do wrong? :( this is driving me insaaaane!

Thanks btw for the direct help :)

Via Tapatalk
[Android Software/Hacking General [Developers Only]] mateorod:
I just decided to check this out ( I have written several different methods of automating this process...unfortunately I have yet to figure out an easy way to integrate it without having to add extra options for other users to muddle through...which I am not willing to do.) and I followed the exact steps you list above and it worked for me.

I am not sure what is going wrong for you, it worked like a charm from here...I have taken the additional step of simply uploading the zip file to you, since I went through the edits that is all the time I have for this issue. But the steps you took are correct, i have verified. There is another error in your process somewhere.

here is the zip...
[Android Software/Hacking General [Developers Only]] IRKONIK:
Well, I downloaded everything again, checked all the md5 sums via hashmyfiles, and now.. It worked too. I have NO idea how, but it did.

Thank you for your patience, I will upload the files ASAP, but right now I'm on mobile (download 180kbps, upload 40kbps on a good day), so when I come home I will post a link to my Google Drive or some other filehost. (zippy? Idk)

Thanks again! I will flash it when the battery is full again. 10% are definitely not enough for an experiment :D

Gesendet von meinem Nexus 10 mit Tapatalk 2

Edit: I can't connect to my network anymore. Sh*t. Any solution? :eek:
[Android Software/Hacking General [Developers Only]] mateorod:
Solution for what? i am not sure what you are trying to do. Either the zip you made or the one I posted has everything you need, just flash it.

Autopatcher v2.9.6 is out. It has been posted to the download page, may not appear for 15-20 mins though.

Just has the updated CM, PACman and AOKP openpdroid patches, that is the only change.

If you have experienced new trouble patching any of those roms, the new patches should solve that for you, and the telephony errors seem to have been worked out for those roms as well.
[Android Software/Hacking General [Developers Only]] Px80:
Thank You!

Patching works again
[Android Software/Hacking General [Developers Only]] SecUpwN:
Any news on patching AOKP 4.2.2 for PDroid 2.0?
[Android Software/Hacking General [Developers Only]] IRKONIK:
My problem is that I lose the connection to the mobile network when I turn off the screen the first time after reboot. After that I can not send/get sms and can't do/receive calls. The interesting part is that my mobile connection works, so it's only a problem with the gsm network.

Modem is MC2, ril MB5, if that helps.

Also connecting to the UMTS network takes ages.

Did you ever ran into issues like this?

Btw, the zip you posted, from which rom is it? Gokusjx' ParanoidAndroid 3.15?

Via Tapatalk
[Android Software/Hacking General [Developers Only]] seburton:
You need to use openpdroid, Because pdroid isn't available for android 4.2.

---------- Post added at 12:10 PM ---------- Previous post was at 11:15 AM ----------

Just tried openpdroid with the last PAC nightly for mako, and it work,

Thank's for your powerfull work
[Android Software/Hacking General [Developers Only]] SecUpwN:
I already do. My question was adressed to [MENTION=4342828]mateorod[/MENTION], I would like to know if merged patches are "in sight".
[Android Software/Hacking General [Developers Only]] mateorod:
Yes, that is the rom I used...i can usually see what rom people are working on unless they have renamed it for some reason, that info is in my log for situations just like this one.

Would you try the zip I posted and see if you get the same results? You should only have to dirty flash it over. I have not heard of that problem with the network cutting out upon sleep/screen off before. But PA is a unique case, they have at least four forks of their official rom running around, at that is only counting the fully open source version, not the Halo closed source stuff. It makes reliably patching ParanoidAndroid roms a little tricky.

If you experience it again, you can post a logcat and I will add it to my issues list.
[Android Software/Hacking General [Developers Only]] IRKONIK:
I am on this rom. I don't know why yours is called m0 20130327.

Logcat will come, as soon as it works again. I can't make logcats either. What ever went wrong, it f*cked up a lot. :D

Cheers :D

Via Tapatalk

Edit 1:

My Zips:

pa_i9300-3.15-28MAR2013-gokussjx-openpdroid-20130520-update.zip

MD5: e16d88eafb3a76bdb7470bed6106b7dc

pa_i9300-3.15-28MAR2013-gokussjx-20130520-restore.zip

MD5: d437c567b81ae4dc6d561e8eae38e2f8

Edit 2: Logcat: Nothing works. Neither via Android SDK and Windows, nor via Terminal Emulator. There are just no logs. I have no idea how this could have happened. The log is just empty.

I guess I will have to stomp my whole system and make a fresh one. Maybe that helps, so I can use openpdroid. LBE SM became pretty bad, loses SU, fc's and stuff like this. Behaves like a little child. -.-
[Android Software/Hacking General [Developers Only]] DualJoe:
[MENTION=4342828]mateorod[/MENTION]:

Regarding the cygwin build problems. These errors are a result of the web based ZIP files provided on the github page indeed. I've looked into it and many files like patches/openpdroid/4.2/cm/20130516/core.patch are simply unresolved symlinks (path strings) that get fed directly to DIFF in the end.

Wrong content of 'patches/openpdroid/4.2/cm/20130516/core.patch':

../../.common/core.patch
[Android Software/Hacking General [Developers Only]] mateorod:
Let me just say that the distinction between Windows and unix file formats is not something I know much about. The content of a unix symlink is just what you post, the name of the file it points to. In this case, that points to the proper file. But I guess what you are saying is that somewhere in the conversion to the github server or client and the processing into a download, the EOL and EOF are converted into Windows format, when in reality you would want it to remain unix style for use in cygwin. Am I on the right track here? I am just not sure what you mean by fed directly to DIFF.

But when kobik77 and wbedard were first working on Windows support, I remember there was a lot of frustration (especially for wbedard) on the symlink conversion and file conversions. I just thought it was mostly solved.

It sounds like a bug in Github, to be honest. I am not sure what to do about this. i appreciate the work you did looking into it.
[Android Software/Hacking General [Developers Only]] DualJoe:
You don't have to worry about this. Its all fine on your side. It just comes down to people downloading the repository with the ZIP download button on the Github page. Those ZIP files don't store symlinks properly resulting in "dead" unlinked files when unpacked.

I just wanted to let you know about it in case there will be more people reporting such errors. The patch process might even finish properly (even though it throws errors like hell).

These bugs will never occur as long as the repository was downloaded the way it's meant to be done (via 'git clone'). I can confirm its working properly in Cygwin.

Those Github provided ZIP files are a special case. I'm not sure if they hold the filesystem attributes for symlinks at all. All uncompressors i've tested couldn't unpack them properly (Winrar/Win, 7zip/Win and unzip/Cygwin). Instead of symlinks just files with their corresponding reference path included appear (as simple 24 bytes text files). Looks like Github compressed the files without any symbolic metadata in the first place (the ZIP files are auto-generated on server side. There's nothing you can do about it indeed).

The (additional) EOL/EOF issue occurs only if you use 'Clone in Windows' (you can see that button on a windows browser only or when faking the http referrer). I once used that option as a last resort since everything else failed. But this failed even more. :)

The unlinked files in patch_patches.tgz just hold the target path (as text/string) that will be passed directly to the DIFF binary during final patch process.

... apply framework.patch ...
patch: **** Only garbage was found in the patch input.
patch unexpectedly ends in middle of line
... apply preloaded.patch ...
patch: **** Only garbage was found in the patch input.
patch unexpectedly ends in middle of line
... apply core.patch ...
patch: **** Only garbage was found in the patch input.
patch unexpectedly ends in middle of line
[Android Software/Hacking General [Developers Only]] sudisk:
Hi

Could someone give me the right command line for pacman Rom for openpdroid? I am not sure what method I should use (all failed for me actually with 2.9.6). I'm trying to patch latest N7000 build.

Edit: here is the error I get:

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

thanks.
[Android Software/Hacking General [Developers Only]] Didgesteve:
No ETA's

To just keep asking isn't helpfull
[Android Software/Hacking General [Developers Only]] newb4r9o:
A PACman THANK YOU!

Just patched pac_n7100-22.2.0-rc1.zip with autopatcherv2.9.6.zip and everything just SIMPLY WORKED :)

(the rom has some issues, but FWICT auto-patcher does not)

Thanks!!