yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] noonecanhide:
With the latest ApG.exe (1.0.0.6) the patching works now with latest pdroid.

Galaxy Nexus CM10 nightly of 17th September.

flashing now.

the errors in the log are normal ?

log here

regarding pdroid: if i patch the cm10 rom file, can i later swap kernel without losing functionality of pdroid ?
[Android Software/Hacking General [Developers Only]] mateorod:
Arggh. I have been getting pm's to this effect as well. pepcisko created a separate tool, one that only patches for the V6. I spoke with him and he kindly removed the "Auto-Patch*" portion of his thread, to hopefully cut down on the confusion.

The Auto-Patcher (our tool, here) is totally unique and separate development. pepcisko has a script that operates somewhat as an adjunct to the V6 script itself, accomplishing the same task as our tool but keeping somewhat more current with zep's test releases. I update our V6 patch every month or so, once his edits get settled.

The "errors" are fine and are here for the foreseeable future. I have explained it eslewhere, but the CM official builds have a difference of undetermined origin with Unofficial builds, the ones I make the patches from. We get around that by importing a prepatched ContentResolver file, which is what you are agreeing to with the "yes"'s after the intial patching errors, although I guess that the GUI agrees to the method for you, automatically.

I used to automatically copy that file over, since I knew it would consistently fail. That was removed in favor of the completely interactive approach, but I am considering reinstating the automatic copy. I think this method is causing some unnecessary confusion and concern.

We added the copy file menu because we found that importing pre-patched copies of certain files allows the Auto-Patcher to work on a bunch of roms we used to have to turn away. Evervolv is able to be patched this way, much of the time, and certain PA builds as well.

As for the kernel question, we have given that some thought. For CM10 or AOKP Pdroid, you can flash any kernel anytime. And if your kernel dev uses the AnyKernel method, from Koush, then

all

of our mods will survive a kernel flash.

Some devs just distribute a boot.img though, usually the ones adding insecure boot.imgs and "ramdisk optimizations" whatever that means. For those boot.imgs, you will have to put them into your rom manually before patching ONLY if you patch for:

pdroid-aosp

[*]secure or insecure

[*]3gdongle

We discussed adding a function allowing you to designate outside boot.imgs on the command-line, but there are currently no plans to add this feature, at least not until the GUI's get made.
[Android Software/Hacking General [Developers Only]] noonecanhide:
Thanks for that comprehensive explanation and your patience with an autopatcher "noob" like me :)

As suggested i bought the guys at techerrata a few beers (9MY98903LU284280L) and mentioned from where ;)
[Android Software/Hacking General [Developers Only]] mssngr:
Not sure why, but I keep getting a completely blank page when trying to open your link's. :confused:
[Android Software/Hacking General [Developers Only]] kobik77:
Try disabling your antivirus or firewall.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] curodot:
I'm trying to patch ParanoidAndroid v2.13 for pdroid but, it fails.

Can you tell me what should I do?

Link of log, here.
[Android Software/Hacking General [Developers Only]] kobik77:
Funny thing that I tried patching it just now successfully.

You are not updated to the latest autopatcher version, try hitting manual update button to get the recent changes.
[Android Software/Hacking General [Developers Only]] mateorod:
I was just coming to say the same thing. For the next auto-patcher version I will try and have an auto-update for those of you not using kobik77's GUI.

I also try and keep the thread title and OP up to speed with the latest version in the name. You see where it says 2.1.0 up there? Not saying I haven't forgotten periodically, but I do that so people won;t have to read the whole thread to know it is time to update.

The Auto-Patcher has to keep up with the CM and AOSP changes, so if you plan to keep patching nightlies you will have to be on the lookout for updates. We have many long and short-term plans to make this process easier as time goes on.
[Android Software/Hacking General [Developers Only]] curodot:
I downloaded ApG v1.0.0.7(clicked the update button and tried manual patching as well) and autopatcherv2.1.0(using cygwin) but, it's still not working for me.

Here's the log. link
[Android Software/Hacking General [Developers Only]] UtCollector@gmail.com:
Seems nice to try this GUI. but i get File Not Found when i try to download.
[Android Software/Hacking General [Developers Only]] ciribaski:
it's possible to add the maximum overdrive mod ?? (always from zep)??

I'm gettin mad tryin manually:eek:

thanks anyway!! and good work
[Android Software/Hacking General [Developers Only]] jelle2503:
GUI works splendid for me. it made a update and restore zip

Which I flashed, and unfortunately got into infinite boot animation. Tried on latest 09/18 nightly of Galaxysmtd (i9000)

Flashing restore.zip got my rom back up and running.

I wish CM would implement a better permission manager again.

I'm so sad this doesn't work for my ROM =( And i'm an auto patching noob who's unable to troubleshoot out why it's stuck in infinite boot animation. So boohoo =( I could probably logcat since boot animation started but I never used ADB to remotely do stuff.

Can I logcat?, so other more knowledgable people can help me with my rom not booting?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
lol

The windows exe will do it fast n easy

Currently trying to add in a hack for Sense 4+.

It has an extra app limit in place... it can only run 8 apps or something ridiculously low even if you have a ton of ram.
[Android Software/Hacking General [Developers Only]] Cirkator:
First of all, thanks for the autopatcher app!!!

Tried the Patch on the newest Quarx CM10 for Motorola Defy+ Rom. Didn´t work, has anyone got it to work yet?

Sorry, but i can´t yet link to outside sites, since i don´t have 10 posts....
[Android Software/Hacking General [Developers Only]] kobik77:
Too bad, patching CM10 from 20120919 fails :(

http://codepad.org/2UqGAHXe

I was already getting spoiled that everything was working flawlessly.

For whomever having troubles downloading ApG I've added a dropbox link to the release post.

Take a look few pages back.
[Android Software/Hacking General [Developers Only]] mateorod:
Which is all well and good if you don't want PDroid or any other mod, zep. The point of the Auto-Patcher isn't to take the place of pepsicko's tool (which came after ours, but edits the files in a totally different way) but to allow our users to use your script. Nothing more.

I have a patch for the maximum overdrive stuff, but I have struggled over how to exactly handle all the edits zep has added lately. Some of them require the use of awk and/or sed, it seems. Which we can handle, no problem. The framework for those types of text edits is already in the Auto-Patcher.

But I may just leave those newer edits to them and just offer the standard supercharge edits. I have considered removing it entirely, to be honest. I have just been getting the feeling that they would rather keep their stuff in-house. And we're not here to compete, the idea of the Auto-Patcher is to be a tool for devs and users. I rearranged this thread to put the devs and their work at the very top of post 1 to make that clear. We'll see. I have had patches for the maximum mods and the newer edits for a little while now, I just have to think about it.

Forgive me if I am wrong, Kobik, but all of the above failures with ApG seem to fail with the ContentResolver. Which we copy over with the menu on the command-line version. Is that happening correctly in ApG? The next update will have that process better documented in the logs. Could you try to patch manually for us?

I won't be able to give the reports a good look until tonight. But I will ssh a build in right now, in case we need new patches.

I also think I will add automatic ContentResolver copying as well, this has been too confusing and since we know it is needed everytime, might as well automate it.

I will give a thorough look into the logs tonight.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
No skin off my nose for any patches you want to keep or add.

I just gave a quick n easy solution to a mod that isn't included in Auto Patcher.

I can see why you may pass on including the maximum overdrive stuff... it was tedious as hell to do... there are at least 3 different variations to look for when doing that mod... plus the Sense stuff that I haven't added yet lol
[Android Software/Hacking General [Developers Only]] mateorod:
I found and tried this, and yeah, it fails. This is an unofficial build by a dev who has added some commits. But it doesn't fail by much, and this is an old build by our standards. When a new build goes up, try again and post a log. I think I can probably do something if the issue hasn't shook out by then.

You can logcat, but easier is pastebin your generated logfile. Maybe we can see something there, although when an update.zip is generated is almost always works...

You have renamed your zip to PA.zip and not provided me with a link, so I don't know what rom you are working on. I am working on automatically getting that info whether you designate a ROMTYPE or not, but for now I need your info. From your logfile, it looks as if you needed to copy the ContentResolver. See the next comment directed to kobik.

I just patched this (you are the one for maguro, right? So many builds...) manually on the command-line and it worked fine after agreeing to copy the ContentResolver. It is going to be a thorn in your side until the provisional thing works well b/c as of right now, 90% of pdroid patchers will be using it. I am looking to make this happen less often.

Everybody I made a new build here, and was able to patch it fine with the current patches. The only build that I have failed to patch was the unsupported defy+ build by quarxx. So you should be able to patch the Cm10 roms still. If you have trouble with ApG, please try it on the command line and see if the result differs. Kobik77 has done a great job with the GUI, this will help give him some data to debug with, and/or locate the fault as originating with the Auto-Patcher proper.

Thanks!
[Android Software/Hacking General [Developers Only]] pastime1971:
all the devs, there is a minor bug in pdroid, found by soccermonster5

please see http://xdaforums.com/showpost.php?p=31738693&postcount=666
[Android Software/Hacking General [Developers Only]] im-pulze:
Where can I find more information to the specific mods?

Most of them are well known - but the "voice" mod as an example I really don't know what it does.

It would be helpful if links to the forumthreads or the dev-webpages are embedded next to the modselection.

EDIT: sry for that dumb question. First post there is everything explained :D
[Android Software/Hacking General [Developers Only]] arko7123:
Tried the patch on today cm10 nighly htc ville with cygwin command line but fails after ContentResolver

http://pastebin.com/8YqizpnF

http://pastebin.com/gPJQEVQd

with ApG everything works fine but after flashing update.zip i get a com.android.phone app crash loop :(

logcat http://pastebin.com/QfMYyvkd
[Android Software/Hacking General [Developers Only]] kobik77:
Suddenly it does work for me :confused:
[Android Software/Hacking General [Developers Only]] Cirkator:
Thx, I will try again as soon as a new build comes out.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, the command-line should be asking you to copy over the ContentResolver. That is what happens when ApG succeeeds. It asks you to type in yes twice. Did you do that and have it fail afterwards?

But for now, I would rather look into your crash. Could you send in build.prop and give me your carrier information? If you would rather, you can send that to me by pm, although know I will share it with pastime1971. There is no reason i can think of to keep that info secret, but just in case...
[Android Software/Hacking General [Developers Only]] pastime1971:
could you upload the log from the successful patching ?
[Android Software/Hacking General [Developers Only]] arko7123:
yes, command line asking me to copy over the ContentResolver and asking me to type yes twice

thank you, this is my build.prop and i'm on Vodafone-IT 3G network 22210

http://pastebin.com/4tW51EAQ

---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------

ApG successful log

http://pastebin.com/ij4cd2TM
[Android Software/Hacking General [Developers Only]] xavisu:
names telnati

I'm using the 1.0.0.8 ApG, choose the rom but I do not see any option to choose
[Android Software/Hacking General [Developers Only]] nsmart:
Same problem here with cygwin/auto_patcher v2.1 or APG on Windows. I am trying to patch cm-10-20120919-NIGHTLY-i9100.zip (Galaxy S2).

I get the ContentResolver error and type yes twice. Then it builds the update.zip, but after flashing it I get a com.android.phone app crash loop.

I tried to patch it with auto_patcher v2.02 and it worked! No ContentResolver error (I had to manually delete unused RILs to avoid method cap errors, because the method cap fix is not included in autopatcher v2.02). Seems the ContentResolver issue is something that began with version 2.1 of autopatcher.
[Android Software/Hacking General [Developers Only]] jelle2503:
Here it is. Program didn't require me to press Y twice, it was done automatically.

http://pastebin.com/pEfSLybF

Build.prop, just in case. Carrier is Vodafone NL

http://pastebin.com/7s1YM5FF

I'd love to get this running on my Galaxy S. I could get logcat during my infinite boot animation if you want.
[Android Software/Hacking General [Developers Only]] mateorod:
OK, thanks for the logs people.

The problem is that when we instituted the deletion of the RIL's, we didn't realize that some carriers/RILs are extensions of another. The posted logcat was what led to that discovery, so thanks. What you are all experiencing is crashing due to the OS looking for a RIL that is deleted, for method cap purposes.

A fix will be out sometime tonight.

The ContentResolver issue has been with us since CM began putting out Official Builds. For some reason, that file is different on the builds produced by them when compared to Unofficial Builds. I have asked many experts, and none of them know anything about it. There is a slight difference between the repo they build with and their public repos. That has been established as fact, at this point.

The only reason that you are all noticing it know is that we changed it from automatically resolving itself through the patching process to asking for input from the users to solve. We may or may not revert to automatically handling that file, still debating that.

But the cause of this trouble is, at it's base, the same method cap issue. This is just an extension of that. But there is a solution, an update will be out tonight which addresses this issue, fixes apktool patching for OSX, and has some refinements to the logging process.

Thanks!
[Android Software/Hacking General [Developers Only]] jelle2503:
thanks, I ran out of thanks. looking forward to an update =D

here's my logcat still, I saw some in logcat about the files needed to be modified for PDroid. I think it doesn't relate to RIL issues but could be wrong

http://pastebin.com/b0P2yLxz

Like said after flashing restore.zip everything working fine again.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, you are correct, it is not RIL issue with your rom. You are having multiple errors, including in ServerThread, a file that is unportable. You only pasted screen output, there is a logfile that is actually made in the main folder after program runs.

I don't see any problems with ServerThreadin your terminal output but that is what kills your boot. There are also problems with ActivtyManagerService. But the ServerThread issue is probably the main problem.

We often see this when people try and patch an aosp-jb rom with CM10 patches and rom mix-ups of that type.

You have flashed the nightly first, and then flashed the update.zip over that, correct? Please attach our log, thanks.
[Android Software/Hacking General [Developers Only]] jelle2503:
Sorry little misunderstanding, I thought I had the right log. I took mine from Cygwin folder :oops:

http://pastebin.com/qVqJyDdS

I was running latest nightly 0918 completely stock already, placed update.zip on sdcard, and went to cmw 6.0.1.3 recovery to flash.

Result, infinite boot anim :(

And I'm pretty sure I didn't mix rom type up, from my screen output file:

Running autopatcher with the following arguments:

ROM_PATH: /cygdrive/c/Users/Jelle/Downloads/cm-10-20120918-NIGHTLY-galaxysmtd.zip

PATCH_TYPE: pdroid

ROM_TYPE: cm10
[Android Software/Hacking General [Developers Only]] dirtyreturn:
:confused:I own a gsm galaxy nexus/galaxy tab 10.1/SGH-t859. For the galaxy nexus the only rom i was able to get patched was cm10 nightly9/10/12. There are two roms I have tried to patch within the past 15 minutes or so.http://xdaforums.com/showthread.php?t=1831501. Liquid 2 beta, first log with pdroid and v6. Second log with pdroid.

http://xdaforums.com/showthread.php?t=1801005 JBSourcery is the third log. I used to autopatcher GUI both with aosp-jb. I had tried with common before, patch failed again. and for the tab the CM9 rom was patched successfully, CM10http://droidbasement.com/galaxy/roms/cm10/p4tmo/ last log. Is ther any gsm galaxy nexus or tmobile galaxy tab users successfully getting this done? I believe i still have dual boot. Do you suggest using the patcher for linux? The nexus roms other than CM are aosp, right? Ideas, suggestions, answers? Last log is using the linux version to patch JBSourcery.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay I am going to have to look into this in more depth. Everything I see leads me to believe that your update.zip should work no problem. I will look into this more tonight, but something you can do for testing purposes for me is to run the auto-patcher for v6supercharger and see if that works for you. You can restore afterwards if you don't want to keep it. I will download and look into this tonight.

There are several things going on here. For the wider educational purposes, I will talk about some of the more advanced issues, but look at the last sentence if you just want an immediate fix.

General Info

AOSP is the source of the method cap problem our cm10 users recently ran into. Google released AOSP with no room for customization in the framework.jar. Cyanogen got around this by taking out classes that weren't required to be found in framework.jar and split them into framework2.jar. Our recent problems with the method cap were because the room Cyanogen cleared out is no longer enough for PDroid, hence the RIL deletion.

Our solution for AOSP was to create the framework2.jar ourselves, adding it whole cloth into AOSP roms. This was a pretty big intellectual leap, in my opinion, to try and do this, and I am pretty proud that it worked. We have created an entire system.jar whole cloth, post-build. Never been done before, to my knowledge.

But with the method cap problem, a bunch of devs making AOSP roms have already cherry-picked the framework2.jar commits from Cyanogen. So for those roms, you would need to have the aosp-jb patches, minus the framework2.jar portions. I have had it on my action list to add this as a feature, but it probably won't make it into the update tonight. I will work on it, I promise,

Your immediate problem with the cm10 patching is that your build is too old for those patches. Don't worry, we include older patches in the Auto-Patcher. Either get a recent build (although you might want to wait for tonight's update, it is causing problems with select carrier's phones) or use the older patches.

Short Solution

I believe your cm10 rom was made on 8/16. So your most likely command for the cm10 rom is:

./auto_patcher cm10-20120816_ETC_.zip pdroid,v6supercharger cm10 20120806

You can see the available patches by entering ./auto_patcher <ROMSNAME>.zip -h

It isn't very pretty- also on the old action list.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
mateorod, patching the cm10 rom was successful. 'Unfortunately, the process com.android.phone has stopped.' Is there anything I guess I could do?:confused:
[Android Software/Hacking General [Developers Only]] mateorod:
Answer, from one post ago.

It will be out tonight.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, Autopatcherv2.1.1 should be available on our download page in maybe 15 mins or so.

Fixes include

OSX should now be fully supported and working (there were issues with apk patching previously. Thanks to rathian, who graciously tested everything we threw at him until a fix was instituted. OSX wouldn't be supported without his time)

Phone FC's are eliminated, all cm10/aokp-jb patches should work for all devices, now.

We added automatic ContentResolver patching back; so those of you tired of seeing that menu, it will no longer be an every time thing.

Logging has been greatly improved. (WIP, but still- better)

I have tested this some, but not as much as I usually get try to. We had some philosophical decisions to make, which between the two of us can go pretty far down the rabbit-hole. But we do it to try and make the platform as stable and versatile as possible.

Please let us know how it treats you.

Jelle, I haven't heard back from the v6 test from you- we can take it up again tomorrow.

Night, all.
[Android Software/Hacking General [Developers Only]] baka2x:
Is anybody else getting a different md5sum? The download page says it's "c60ece4b123e56732d721d7fceebf4cb", but I received "ea7a56ece1f11ded8c1067c6f0fefdf7" a few times.
[Android Software/Hacking General [Developers Only]] arko7123:
cm10 nighlty successfully patched with version 2.1.1 and cygwin command line

thank you ;)
[Android Software/Hacking General [Developers Only]] MENNENN:
Patching of stock [ROM] Ice Cream Saga v1.0 [4.0.4][Sense 3.6] with pdroid fails when using ApG GUI.

Manually patching with old patches fails too.

Log of failed patch:

http://codepad.org/ebRhEUkH
[Android Software/Hacking General [Developers Only]] jelle2503:
I went to bed early last night soz =) , European time.

I have done the test today. It's stuck on boot animation too.

Here's the log from your app:

http://pastebin.com/t990dTcq

Here's the logcat (verbose output of DDMS in Android SDK) .. don't know if you need debug, but i saved it just in case.

http://pastebin.com/wNx2jkhw
[Android Software/Hacking General [Developers Only]] HyperCriSiS:
OMG, this Utility sounds like a dream, to good to be true! :D

WIll try this asap :cyclops: