yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Ranomez:
APG automatically updates to latest autopatcher and also automatically updates the exe, so you don't need to update it manually, if it's not working it's just not working, post a log and wayt for a fix like i am doing, when you open APG look at the changelog for the latest version 2.9.1 to be up in it.
[Android Software/Hacking General [Developers Only]] lulli1:
Same Problem here! I think the new opd patches for 4.2.2 are not included in the autopatcher patch files.

You have to patch the source directly. Here is the link to the patches...

https://github.com/OpenPDroid/OpenPDroidPatches

In my case, I gave them to the ROM dev, and he put it in his source. Now it works on 4.2.2 - CM10.1.
[Android Software/Hacking General [Developers Only]] mn31pro:
i have a problem with pdroid patch for android 4.0.4 aosp.

here is error;

http://codepad.org/Qt7y5jjG
[Android Software/Hacking General [Developers Only]] dirtyreturn:
delete
[Android Software/Hacking General [Developers Only]] mateorod:
Try deleting ApG and starting fresh. There were some big changes and I have seen that problem solved in this manner. Sorry for the double download. But the 4.2.2 patches are in there and are working for lots of people/

Is there a link to your rom? the AOSP source code has barely changed in the last year for 4.0.4, so I wonder if your rom is actually pure aosp or is maybe a stock rom.

Also:

I had some reports that ParanoidAndroid 3.1+ wasn't working, but I just built to make new patches only to find that it is patching fine for me...anyone having trouble with PA?
[Android Software/Hacking General [Developers Only]] SecUpwN:
Are the new patches for running PDroid 2.0 on AOKP 4.2.2 already included in this version of Auto-Patcher?
[Android Software/Hacking General [Developers Only]] D-m-x:
I have patched the Rom again and strangely this time it worked. If someone still needs the patch for Slim Bean I can upload it later.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] dzel:
slimbean what build?

nexus 4 right?
[Android Software/Hacking General [Developers Only]] mn31pro:
my rom is stock ics 4.0.4.

my tablet is a chiness tablet with a13-b processor.

here is my framework+build.prop: http://d-h.st/gIc

please give me a solution or patch this file for me.

thanks
[Android Software/Hacking General [Developers Only]] lulli1:
Hi mateorod, I downloaded ApG again (it´s V 2.6.0.2), as well as the new patchfiles (it´s V 2.9.2) and got the same error as before.

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

So I thought it must be the patches, that aren´t able to work with CM10.1 - Android 4.2.2.

Maybe you can help me to find the problem?

Here are the log files:

http://www.mediafire.com/?pdcy3rn593hp2

And this is the link to the unodexed ROM.zip

http://pan.baidu.com/share/link?shar...&uk=2902555578

Tanks a lot!
[Android Software/Hacking General [Developers Only]] D-m-x:
Yes, for the newest build for the N4

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] jahrule:
I think this has been mentioned in op and about a million times in the thread,

Patching stock ROMs is not possible with auto patcher.
[Android Software/Hacking General [Developers Only]] jahrule:
Is it supposed to be when you patch with openpdroid but install pdroid2.0 app that app reports you only have version 1.51 installed?
[Android Software/Hacking General [Developers Only]] nerbrume:
FC with Play store confirmed

Hi,

I can confirm having almost the same behavior on my Galaxy S2, running CM9. Play store is crashing when I try to view my apps (and is fine otherwise), closely followed by a FC of PDroid. Google maps seems to be working fine as long as it doesn't need the GPS. When explicitely calling the GPS (I use GPS Status for that), I get FC, of GPS Status, then PDroid.

This behavior is "new" : it appeared suddenly, without having updated CM9 or PDroid. My guess would go to the google framework being updated silently, but I really don't know.

I can also try to provide logs if needed.
[Android Software/Hacking General [Developers Only]] mithrial:
Thank you anyways. Works fine as always.
[Android Software/Hacking General [Developers Only]] pastime1971:
it doesn't look like it is THE CM9 rom.

where did you get it ?
[Android Software/Hacking General [Developers Only]] trephined:
droidforums. net/forum/droid-pro-roms/198354-6-18-12-cm9-ics-droid-pro.html
[Android Software/Hacking General [Developers Only]] mateorod:
When you say you tried all the pdroid patches, does that mean you tried all the dates covered by the Auto-Patcher, which you can see by the -h flag?

If so, then that rom is just probably not supported. You can use the build patches, if you want. Follow pastime's sig.

New Auto-Patcher is up, 20120724v103.
[Android Software/Hacking General [Developers Only]] trephined:
That's correct, I tried all the dates available for CM9 and pdroid.

Would I be able to upload any particular files, such as build.prop or framework.jar to determine what is making autopatcher not work for me?

Perhaps the logging/console output/debugging used to just be different but the older scripts, e.g. 20120508 give me what looks like more insight on the error

### apply framework.patch ###
13 out of 15 hunks FAILED -- saving rejects to file 'smali/android/app/backup/BackupAgent$BackupServiceBinder.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/content/CursorLoader.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file smali/android/content/IntentFilter.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/location/Location.smali.rej
29 out of 36 hunks FAILED -- saving rejects to file smali/android/net/wifi/WifiConfigStore.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
23 out of 23 hunks ignored -- saving rejects to file 'smali/android/server/BluetoothA2dpService$1.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file smali/android/server/BluetoothA2dpService.smali.rej
4 out of 5 hunks FAILED -- saving rejects to file smali/android/view/SurfaceView.smali.rej
[Android Software/Hacking General [Developers Only]] mateorod:
Nope. The patcher deconstructs the ROM building process and applies our patches to known locii.

We only find those locations by patching original source and then porting those changes to similar roms. I guess your ROM isn't similar enough to CM9. Your best bet was probably

./auto_patcher CM9-with-MAC.zip pdroid cm9 20120615

Why do you need this specific CM9 ROM? Because of the mac address? In my device you can edit that in the ROM partitition. Edit: I see. It's a bug-fix. This looks like a mash-up of CM9 and something called EncounterICS. Looks like a work-around to get ICS to an older device, maybe? Either way, without source for this, we can't do anything else.

If you get access to source, you can build adding the build patches. That should work. Or you can ask the dev of the ROM to make a build for you and we can make patches from that.
[Android Software/Hacking General [Developers Only]] trephined:
I'm guessing a few things had to be cobbled together, as my phone is stuck like many motorola phones with a locked bootloader, and stuck with an old kernel. it's a 2nd init device, which is where the parts were pulled from the EncounterICS rom, for Droid X.

I have posted on my rom thread for any support with getting a build tree link or for the developer to patch in the source patches. I thank you for your assistance.
[Android Software/Hacking General [Developers Only]] mateorod:
I do feel your pain on the bootloader. I now take a very close look at all closed-source drivers for chipsets and manufacturer locks on software.

I was spoiled by the Nook Color, but now I know better.

Good luck, I hope the dev can help you out. Even if he just builds one patched build for you, we can make a patch for the patcher from that...
[Android Software/Hacking General [Developers Only]] trephined:
I have the link to my ICS rom on github.

github. com/JackpotClavin/Droid-Pro-ICS/tree/98c704986c81c4aca3a02ce102c2350d661923a7/device/moto/venus2
[Android Software/Hacking General [Developers Only]] explorer-10:
work with stock ICS or JB roms?
[Android Software/Hacking General [Developers Only]] closedcircuit:
CollegeDev's [App/Addon] PDroidAddon Camera and Microphone Permission

Does anyone know if it's possible to use CollegeDev's PDroidAddon with the autopatcher? What the addon does is allow you to set permissions for individual apps for access to the camera and mic.
[Android Software/Hacking General [Developers Only]] pastime1971:
if he can share his source code or smali diff, then yes.
[Android Software/Hacking General [Developers Only]] pastime1971:
he probably added his stuff to framework. i will take a look...
[Android Software/Hacking General [Developers Only]] trephined:
I've downloaded CM9 source, my device sources from above link, setup the android build environment, patched in pdroid stuff, and tried unsuccessfully to compile the kernel. I think perhaps the fact that I don't have access to any computers with more than 4 gigs of ram may have something to do with it. If anyone would be so willing to do a build for me so the autopatcher devs are able to build in support it would be greatly appreciated.

I have finally built a working CM9 build for my device, with the pdroid source patches. I am uploading tonight, will post tomorrow.
[Android Software/Hacking General [Developers Only]] mateorod:
That github has a prebuilt kernel in the tree. You don't need to build it separately. Have you tried just compiling the ROM?

I have all my build time devoted to bringing this stuff to JB, and I know pastime is pretty much the same. You are almost there. Post your issues, and I will continue to try and be a resource for you.
[Android Software/Hacking General [Developers Only]] mastalee:
Hi

i've used the patcher 103 on mac osx and found some problems when the working path contains spaces.

the patch will add quoting to all places where it is needed
[Android Software/Hacking General [Developers Only]] pastime1971:
could you tell me which ?

i guess all of them need to be quoted.
[Android Software/Hacking General [Developers Only]] maeman:
Will OpenPDroid ever support CM9 or CM7?

I am running CM9 (because JellyBean is crap, thanks to Google) and I won't update... actually considering going back to CM7

But Pdroid support for CM9 is unclear,.. i have created a Pdroid patch for my CM9 rom with autopatcher, but I am not sure if it is gonna work or if it is gonna make a mess

do you guys know what is the best way to get Pdroid on CM9?

Thank you
[Android Software/Hacking General [Developers Only]] mateorod:
At one point supporting CM7 and CM9 was discussed, but I can pretty confidently state that there is very little likelyhood of OpenPDroid ever being backported any farther than it already is (Cm10). Someone out in the big wide world may take it up as a project, it is certainly doable, but as it is now dependent on me, I am cutting back on my range of support in hopes of merely being able to keep up with what i have already signed up for.

But the Autopatcher has support for original PDroid for Android 2.3.4 => 4.1.2. So you can follow the link in the OP here to svyat's thread and use the original PDroid app. It still works great for most things.
[Android Software/Hacking General [Developers Only]] Febby:
I had an error when attempting to patch the latest 4-26-13 build by tasker on the sgs3 att.

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

Log: http://codepad.org/d3ujTkEo
[Android Software/Hacking General [Developers Only]] DizzyDen:
I had noticed that Auto Patcher was seeing CM10.1 (Encore) as AOSP... so I modified auto_patcher script's proberom() function as described here. to make it work
[Android Software/Hacking General [Developers Only]] root:
I have a problem with cygwin patch, it looks like it hangs, as it is started but then nothing happens, looks like it waits for stdin input.
[Android Software/Hacking General [Developers Only]] SecUpwN:
Does Auto-Patcher support patching 4.2.2 to use PDroid 2.0 now? Please update me, guys.
[Android Software/Hacking General [Developers Only]] noonecanhide:
Somehow pdroid is broken on the latest cm10.1 nightly for the nexus 7. Patching was okay, but at least randomizing android id does not work anymore... I don't know how to debug that. :-/
[Android Software/Hacking General [Developers Only]] cakruege:
Hi,

maybe a stupid question but is it possible to patch a nexus 4 stock rom?

greetings

Carsten
[Android Software/Hacking General [Developers Only]] Didgesteve:
As far as I know there is no stock rom support, if you look a few pages back Mateorod explains.
[Android Software/Hacking General [Developers Only]] lulli1:
give it a try. must be a pure aosp rom. so it have to work, haven't it?
[Android Software/Hacking General [Developers Only]] cakruege:
Thx
[Android Software/Hacking General [Developers Only]] genderblurr:
I am having issues with ti failing to patch

http://codepad.org/gA2ASdyB

I did modify the telephony patch not sure about running batch.sh It is still failing though.
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, I have noticed this same thing, since at least the CM10-fullofbugs-alpha. I may add your change to the next update for the autopatcher, but probably a more sensible thing would be to have the Nook device tree fall in line with the rest of the CM world. It is an official release from the CM servers, I just bet no one has realized that it fails standard build.prop parsing. I may just send a pull request today.

Edit: While we are discussing it...it has long, long been on my list to completely redo and refactor that section of the code. It is exactly what it looks like, a function that started just with ICS, and then slowly had later (and earlier) android versions tacked onto it. But the concern is the same here as with other refactors, in that each section has little quirks that are actually hard-fought error-catches and bugfixes. So even though it is ugly, and possibly four times longer than it needs to be, it still does (with very limited exception) exactly what it is supposed to do, and as such has escaped revision for now. Someday, like everything else.

Edit2: And. having just looked at the source, an immediate problem jumps out at me. The problem is that encore is the only CM rom where the "ro.cm.version" does not start with "cm". But to fix it, we would come up against the exact problem I just encountered with my latest rom. The verygreen/leapinlar sdcard installer relies upon 'ro.cm.version=10*' to work. Changing this line would require every sdcard user to upgrade their install method as well. That may be asking a lot for a 3 year old script, even if it really should be updated if we are conforming to best practice. Hmmmm.

I might just have to suck it up and add your Nook-specific change. It won't be the first time the autopatcher has had to carry encore-specific code because of bugs in that script.

(which I just saw a bug in, of course. urgghhh.(fixed it a long time ago, awesome) I will (still)probably try and fix all these things at once very soon.)

That doesn't look to be a rom from our supported list, and just by a glance I am guessing it is stock based. maybe? Either way, your only chances are to try the various romtypes as listed in the OP. If none of them patch, then we do not support it, sorry.
[Android Software/Hacking General [Developers Only]] Febby:
Another fail trying to patch CM10.1 nighty 05-1-2013 using openpdroid.

http://codepad.org/bDdmo2I7
[Android Software/Hacking General [Developers Only]] mateorod:
You are trying to use the aosp patches on a CyanogenMod build. That won't work. Try not selecting any romtype, it is only necessary in very rare cases or if you are attempting to patch a kang of some sort.

I just checked an 0501 CM rom and it patches.
[Android Software/Hacking General [Developers Only]] Febby:
Wooops.... I had no idea it was autoselecting AOSP for me. I had it selected under CM but it refreshed after I restarted my computer. It created the patch finally.

Is there an side effect to CDMAServiceStateTracker failing to patch? It just gave me that error but patch zip still worked good. =)
[Android Software/Hacking General [Developers Only]] flat_:
Hi,

I'm stuck at the following error:

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

!!! error: system/framework/framework2.jar is missing in the patch. Please upload your logfile to the support thread!

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

Using ubuntu 12.04 and flashing a rom for Motorola Razr I : Moto JB 4.1.2 with a heavy touch of AOSP

The zip can be found here:

http://haxr.org/omar/android/RaZR i - XT890/OLD/RazRi_JB_EU_Optimized-2013-Apr-15.zip

Log attached. Thanks for your work :D

[edit] I don't know if it has something to do with the problem, but I've noticed the following error on the console:

> gzip: ../boot.img-ramdisk.gz: not in gzip format
[Android Software/Hacking General [Developers Only]] mateorod:
Well, I just saw your edit...I found the bug that was the missing framework2.jar. It is fixed in ApG already. But that outputed error I don't recognize. That may very well impair the ability of the autopatcher to reconstruct your boot.img.

Patching for AOSP in 4.1 is by far the craziest thing we do, and we do a bunch of stuff no one else is trying....If you get any other output errors, let me know and I will look more closely tonight.

But for now, try 2.9.3, it solves the missing framework2.jar for you it is only up on github and ApG for now...
[Android Software/Hacking General [Developers Only]] flat_:
Thanks mateorod,

I tried 2.9.3 but I'm now getting a lot of errors.

It's probably due to "gzip: ../boot.img-ramdisk.gz: not in gzip format"...

As explained on Unpacking RAZR i boot images, it looks like the Razr I has a weird format for boot images.

So I guess it will be more complicated than expected :/
[Android Software/Hacking General [Developers Only]] mateorod:
Well, 99% of those notifications aren't errors, they are there by design. The larger problem now is that you appear to be patching a stock ROM or something based off stock. We don't support that right now because we do not have access to the source code in many cases.
[Android Software/Hacking General [Developers Only]] flat_:
Ok, thanks anyway !

Motorola... never again :p
[Android Software/Hacking General [Developers Only]] genderblurr:
It's Pac In Black aka PA+CM+AKOP all in one. So it isnt stock. I have a E4GT stock would be TW
[Android Software/Hacking General [Developers Only]] mateorod:
Well, my advice still stands, you can be sure one way or another it you just try the major romtypes all in a row. I have written a new feature called 'exhaustive' which runs through all patches (it takes a while) but it is not quite ready, probably for 3.0.

But you might just be in luck, because we have PaCman maintainer, AussieLambChops. Those patches are held under aosp. So try the aosp patches. Better yet, as always, try running it w/o a ROM specified. The ROM probe function is pretty good at matching the patches.

(Did you guys know you used to have to pick ROM type and date as well? It was really hairy. The work to simplify all of this has been losing and is not done yet)
[Android Software/Hacking General [Developers Only]] genderblurr:
Thanks! will do.

Edit: didn't work.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Is this applyable to the Galaxy S3 I9300 PA 3.15 ROM? If so, would you be so kind to patch it for me? (I do not have Linux atm, so I can't do it for myself. Sorry)

Thanks in advance!

Via Tapatalk
[Android Software/Hacking General [Developers Only]] SecUpwN:
[MENTION=4342828]mateorod[/MENTION], does the latest Auto-Patcher support this?
[Android Software/Hacking General [Developers Only]] Febby:
That's a negative. I've been trying to compile from source with the pdroid 2.0 patches but I'm a little confused since instructions from college dev are really outdated compared to latest patch zip...

I sure wish auto patcher would just support it already. :)
[Android Software/Hacking General [Developers Only]] jahrule:
+1000 I hope we can see 2.0 patches as well. I think we should wait till after "the merge" though because maybe we don't need the 2.0 patches ;)
[Android Software/Hacking General [Developers Only]] mateorod:
The reason it isn't done is because I am the only working on it, and it is a big project. I am merging what is essentially three forks, none of which have previously followed portable software methods.

As it stands, the latest Pdroid2.0 patches have just gone back and reintroduced some of the bugs we spent time tracking and fixing for the OpenPDroid. And, since PDroid2.0 still only has empty repos, that is the way it will stay unless I fix it, and present it to the world (following the GPL) in a sane manner so that people with experience and ability can also work on it. This is the same challenge we faced when we decided to port PDroid2.0 to 4.2 in the first place. That also took over a month, you just didn't know we were doing it.

You guys have these small bugs you are worried about fixing. CollegeDev wants me to just forget OpenPdroid and just support PDroid2.0. I absolutely promise you the end game of that choice would be PDroid eventually fading away. This has already happened once, when Syvat disappeared from the project. CollegeDev already mentions he is working 20 hours a day at school...what happens when he graduates and gets a real job? He might not disappear but history (and my long long list of disappeared collaborators) tell us not to count on it.

The original Pdroid code was barley exposed to the world and was only forked and maintained by me until ColegeDev released Pdroid2.0. Pdroid2.0 was never released publicly in any reasonable manner (to this day) and was only forked once, by OpenPdroid. OpenPdroid has every step exposed and all repos available for examination and contribution. We have had major bugs exposed and fixed by many collaborators since then. OpenPdroid was forked 10 times last week. One of those people may be the one who ports to Android 5.0...this is how advance get made.

This is how software stays alive. This is how software gets secure, through eyeballs. This is the only way I am interested in contributing to what is, by Syvat's definition, an open source project. Everything I have ever released or worked on is publicly available. If you are unhappy with the pace, progress or procedure, fork it and get to work. That is why I put it out there.

CollegeDev and I aren't at odds, we just have different priorities at times. He has a new feature and some bug fixes and cannot understand why I am spending my time adding those changes in one at a time. I believe that inremental development and exposed code leads to longlasting and secure projects. The idea is to finish this merge and then allow him to add features and bug fixes in the OpenPdroid way. I think we can get there, but as is, the new PDroid2.0 patches have bugs too. Badgering me about a more timely and better product won't get you anything if all I do is ship different bugs.

Just asking me, every two days like clockwork, whether I have finished it yet won't get it to you any faster. I provide source code and changlogs with my releases...you'll know.
[Android Software/Hacking General [Developers Only]] xelra:
I am telling you. The only thing most of these people care about is that the pdroid manager doesn't look as fancy as the pdroid 2.0 app. :p
[Android Software/Hacking General [Developers Only]] D-m-x:
Honestly, I don't care which Version I use as long as the Functions are almost the same. You are doing a great Job the Auto Patcher and Open PDroid is working fine, so take it easy ;)

Gesendet von meinem Nexus 4 mit Tapatalk 2