yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] brashmadcap:
Works perfectly on jb

I used this on a Nexus 7 16GB with Paranoid Android 1.97a which isn't even stock CM10 and I have confirmed it is working. Patch works perfectly, pdroid actually blocks what it's supposed to block (I tested this by blocking everything on ES Task Manager and then went into ES Task Manager and it said that IMEI and phone identity was unknown). Getting ready to fire this up for the Galaxy Nexus too! No weird crashes, no messed up framework. Will continue to test and let you know. THANK YOU!
[Android Software/Hacking General [Developers Only]] mateorod:
Nice! PA supported!

Thanks for reporting your findings!
[Android Software/Hacking General [Developers Only]] wkwkwk:
What a nice thing to see:

$ ap/auto_patcher cm-10-20120803-UNOFFICIAL-n7000.zip pdroid
### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
### probe rom type ###
inflated: system/build.prop
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
### using Clockworkmod installer ###
### create restore.zip ###
### decompile framework.jar ###
... extract preloaded-classes ...
### decompile core.jar ###
### decompile services.jar ###
### patch pdroid/cm10/latest ###
### apply framework.patch ###
... apply preloaded.patch ...
### apply core.patch ###
### apply services.patch ###
### rebuild framework.jar ###
### rebuild core.jar ###
### rebuild services.jar ###
### create updater.zip ###
### finished ###
flash update.zip to install the modified
flash restore.zip to restore the original
$
[Android Software/Hacking General [Developers Only]] tonyp:
Still won't work for v1.5 though *sigh*
[Android Software/Hacking General [Developers Only]] pastime1971:
i can pm him.

we communicated briefly when i fixed pdroid compilation, and also when i ported it to ICS.

even then, he seemed quite busy with his life.

i don't really see a problem of providing a flashable zip of his app.

edit: meanwhile, i have a question. on svyat's thread, there is a link to "PDroid_release.apk". is that somethink you can copy to sdcard and install from ? (sorry about super-newbie question...)
[Android Software/Hacking General [Developers Only]] scourgeofgod:
Playing around with the updater scripts i came up with these two useful files.

PDroid 1.32 App Flashable-signed.zip

PDroidCOMBO(patch+app)- PA1.3 CM10-signed.zip

First one pushes just the PDroid app, while second one pushes both PDroid patch and the app succesively.

I got the second combo file by just merging the first file into the directory structure of the original PDroid patch update zip i got out of autopatcher.

Also copied the content of update script from first zip and appended it to the update script of the PDroid patch. finally deleted all the old junk cert and manifest files and signed the merged Combo zip which can now be distributed as an addon to the ROM.

Or instead of above just simultaneously apply patch and app zips to get the same effect - but then they will be two files :) .

Ofcourse all of this can be done properly when syvat agrees.
[Android Software/Hacking General [Developers Only]] mateorod:
Let me ust point out to people (since I myself had to download it to understand) that the second zip linked above is a patch for the CM10 Galaxy Note ONLY! Don't flash that zip in any old rom, you will break your install.

The PDroid apk flashable.zip could be useful to some people, depending on their preference. I myself use the PDroid-release.apk that pastime mentioned. It just sits on my sdcard. PDroid itself registers as incompatible with my device from Google Play...
[Android Software/Hacking General [Developers Only]] scourgeofgod:
Oops! forgot to mention that.

Basically the second zip was meant to be a pointer/example to *users* who are building patches to their respective ROMs and even distributing them for others in threads. Basically a way to make a single bundle.

But Mateorod, it will be quite cool (and straight forward) if you can modify autopatcher to bundle the app with the patch itself. Hopefully syvat would be opening his PM box one of these days :D
[Android Software/Hacking General [Developers Only]] tonyp:
If he doesn't answer here on the PM, I got his private mail address. I could just ask if it would be okay for him if you bundle it.
[Android Software/Hacking General [Developers Only]] CollegeDev:
He doesn't answer. I wrote him PM, because of question to get source of *.apk from him, but he doesn't answer until now.:(
[Android Software/Hacking General [Developers Only]] Urinophoria:
Can you link the rom and post the log? PAC is sailing right through the auto patcher for me. It's my dd on the i747,so I actually check that one more than the others (usually daily).
[Android Software/Hacking General [Developers Only]] IRKONIK:
Got a problem with the new PA version http://xdaforums.com/showthread.php?t=1745003

Log: http://pastebin.com/22nirU5L

Cheers and thx :)
[Android Software/Hacking General [Developers Only]] mvsroot:
Problem to patch CM 7.2.4 for Motorola Milestone

Hello,

I tried to patch my CM 7.2.4 (download it here: http://d-h.st/3fb) and got the follwing results (I tried it several times):

./auto_patcher cm-7.2.4f-umts_sholes.zip pdroid cm

The Auto-Patcher v2.9.924

### checking for updates ###
Updater: Auto-Patcher is already up to date

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
... result of ROM check: RIL= motow3g
### probe rom type ###
... result of ROM check: version= 2.3.7 rom= cm ...
... Using cm patches ...
*** CM7 roms default to latest patches. If using an older rom ***
*** specify patch date on command line. Use -h to see available patches ***
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
mv: cannot move `preloaded-classes' to `tmp/system/framework/framework.jar.out/': No such file or directory
... decompile core.jar ...
... decompile services.jar ...
### jar patch pdroid/2.3/cm/latest ###
... apply framework.patch ...
patch: **** Can't change to directory tmp/system/framework/framework.jar.out : No such file or directory
... apply preloaded.patch ...
patch: **** Can't change to directory tmp/system/framework/framework.jar.out : No such file or directory
find: `tmp/system/framework': No such file or directory
find: `tmp/system/framework': No such file or directory
... apply core.patch ...
patch: **** Can't change to directory tmp/system/framework/core.jar.out : No such file or directory
find: `tmp/system/framework': No such file or directory
find: `tmp/system/framework': No such file or directory
... apply services.patch ...
patch: **** Can't change to directory tmp/system/framework/services.jar.out : No such file or directory
find: `tmp/system/framework': No such file or directory
find: `tmp/system/framework': No such file or directory
### rebuild jar ###
... rebuild framework.jar ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed compiling framework.jar !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! This error is generally due to an unknown bug in the smali binary!
In our experience, it goes away if you run the patcher a second time.
Please run the Auto-Patcher with the same command once again.

If after the third attempt the same thing happens,
please upload your logfile to our support thread!

Any ideas?

Thanks.
[Android Software/Hacking General [Developers Only]] awillis111:
Not ignoring you. I'll get you a link and log later this evening.

All battery related stats are using a ZeroLemon 7000mah battery.
[Android Software/Hacking General [Developers Only]] mateorod:
e

You are using old version of the auto-patcher...I am guessing that you are using ApG but somehow you need to update. If the update feature is not working, you may need to uninstall and reinstall. Sorry I don;t have beetr debug advice (translated from Russian):) don't have better debug advice, but I don't know ApG very well. But that rompatches with the current autopatcher.

You're the man ;)
[Android Software/Hacking General [Developers Only]] a-id:
I've tried to patch CM 10.1.1 for Galaxy S and got this:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] mateorod:
The RC's and stables are hard on our build query (the code that matches up your romtype and build date) because those builds use code that is older than their build date. To be specific, the code inside RC and stable builds are built from changes that are a couple weeks old. The autopatcher is built on the premise that builds use the up-to-date changes available as of their build time.

If you were patching on the command line, it would be no problem, because I would tell you to use the older patches like this...

./auto_patcher ROMNAME.zip openpdroid cm 20130516

But you are using ApG so I do not know how to specify a patch date. Can you see anyway through the GUI?

An easier solution is just to download the latest nightly build (no CM-10.1.whatever) and patch that (edit; something from here). The RC and stables are not really any more stable than the nightlies...just a designation of where the code base is as a whole, not a indictment of the nightlies' quality.
[Android Software/Hacking General [Developers Only]] awillis111:
ROM thread
[Android Software/Hacking General [Developers Only]] Bad-Pixel:
Up! Someone can help me? :(
[Android Software/Hacking General [Developers Only]] IRKONIK:
No, I am on xubuntu. It's weird that the auto patcher won't update. Is there a command to force him to search for updates?

Thx!

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] mateorod:
Well, the update mechanism is still a work-in-progress. It is hard to universalize because the ApG people need to handled differently. If you have been sdownloading the packages from our download page, the best thing to do is this

sudo apt-get install git git-core
git clone [url]https://github.com/mateor/auto-patcher[/url]
cd auto-patcher
./batch.sh

and then run as normal. The script should update automatically each time you run it from then on. You may have an older package, or git is not in your path or any number of little things. Like I said, it was kind of an anbitious feature and there could still be bugs. You should see a .config file that can have the AUTO_UPDATE variable set to true or false (true by default unless Cygwin).

let me know if that works, if not, post your log and then I will post the latest package to the download page.

[MENTION=4473374]Bad-Pixel[/MENTION]: Carbon rom is likely not supported. The supported rom list is on the OP. Some other kangs are able to patch, but that is only by a luck.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Not sure if this is "right" but its how I do it and it works very well. First, just rm -rf your autopatcher directory. Then open terminal and put in

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

Wait till its done cloning, then

cd auto-patcher/

then

./batch.sh

Once batch.sh is done you should be ready to rock, drop your ROM into the autopatcher dir and go for it. Remember to specifiy the first supported date after the build date if you're running non-nightly releases. If it's a nightly try flagging with "latest"

ex:

./auto_patcher romIwanttopatch.zip openpdroid cm latest

Edit: Lol, looks like I had it right, Mateor beat me to it.
[Android Software/Hacking General [Developers Only]] Bad-Pixel:
Really sorry mateorod, I didn't know that carbon ROMs are not supported. Can I ask you why? Is there something I can do to patch in any way the rom?

Still sorry
[Android Software/Hacking General [Developers Only]] Urinophoria:
Essentially, to be supported; a ROM has to be patched. To build patches for auto patcher, you need to build a pre-patched (stock) copy, and a patched copy (https://github.com/OpenPDroid/OpenPDroidPatches) of the exact same ROM, meaning you have to build each ROM twice to make one patch. Then you take both copies, patched and unpatched and make a patch for the autopatcher (https://github.com/mateor/auto-patcher/wiki/Building-patches).

So, there are a fair number of processor cycles involved every time someone breaks the patches in their ROMs. If no one is making builds for Mateorod and he has to build patches for a big upstream change that breaks all 7 actively supported ROMs, it could very well take him off autopatcher development for a good week. I'd rather (1) build my own patched ROM, or (2) Use one that's supported, than see him dropping development time and cpu cycles in favor of building patches for all available ROMs.

He's got a few of us buildmonkeys helping in that regard, but a line has to be drawn somewhere to keep it sustainable. Since a lot of ROMs are pretty closely related to AOSP, AOKP, PAC-Man, PA (jellybean), Cyanogenmod, Evervolv or SlimROM, some other ground is covered incidentally. Unfortunately, a lot of them are just different enough that they stop (f they ever were) working.

Whether or not they start again kinda depends on how the individual developer is developing his/her ROM, and what changes/commits they're borrowing from which other ROMS.
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
I tried to patch tabletUI into an unofficial CM10.1 Nightly for HP Touchpad and it boot loops after flashing the patch using CWM. I did not do any wiping at first. When it bootlooped, I wiped cache and dalvik cache, but it didn't make any difference.

Log attached, does it offer any clues?

UPDATE: I reflashed the ROM and patch in CWM, it no longer boot loops. However, once it boots up, there is no status bar or wallpaper, and it repeatedly says "Unfortunately, System UI has stopped." When I touch the OK button, the dialog just pops up again.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Yeah, with su, eh?! XD

I'll try.

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] Urinophoria:
I've never had to use su for that. If it requires root permission that would probably explain why you're not updating.

I've not had to su or sudo anything beyond installing git-core. Once that's done it should all be normal user permissions.
[Android Software/Hacking General [Developers Only]] IRKONIK:
The joke is that it would erase your root directory xD

It's a joke people do so beginners crash their system irreparably :P

But yeah, as soon as I'm not too lazy to start my vm I'll give it a shot, so I can use openpdroid on my S3. This XPrivacy thing is such a half hearted tool. It can't block system apps. I always block Googles kraken. F*ck the play store, why on earth do they want to send sms and mms?! Why do they want to know my phone number, IMEI etc?! That's none of their business.

Cheers, and pardon me for ranting about gergle

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] noonecanhide:
It can be patched via ApG really easily. Just hit the "Manual Patching" Button. After the terminal window has opened, just enter the following command to patch a CM 10.1.1 Stable release with openpdroid.

replace X:/YYYY with the drive letter and path where the ROM-file is located (e.g.: C:/downloads) do not use backslash, only slash.

replace Z with your device name.

./auto_patcher X:/YYYYY/cm-10.1.1-ZZZZZ.zip openpdroid cm10 20130516

the update and restore files to be flashed are located in the subdirectory ApGPackages/ap in your ApG installation location.

Tested with the latest stable build of maguro, mako and grouper.
[Android Software/Hacking General [Developers Only]] Caldair:
GnatGoSplat, you need to update Auto-patcher to the latest version. There have been 2 fixes for tabletUI since the version that you are using. Using the updated patches should fix your problem.

Whookid, the build you are trying to patch is a second stable release of CM10.1.0. This is what mateorod was talking about a couple pages back, it uses the CM source as it was a few weeks ago and does not have all the new code which has been added since. Because of that you need to have Auto-Patcher use the old patches on it.

Run this command instead:

./auto_patcher cm-10.1.1-p5110.zip tabletUI cm 20130403

and you should have success, I hope.
[Android Software/Hacking General [Developers Only]] mvsroot:
Thanks. Yes you are correct. I've contacted the author and asked for an deodexed version. This is the only custom ROM for the phone as far as I know.
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
I'm sure it's right under my nose, but I can't seem to find the correct link to download the current version. I went to the "Download" link which is bold and in larger type that took me here http://techerrata.com/browse/mateorod/pastime1971, but newest version there is the one I had (2.9.89). I saw there is a newer version at the github, but I didn't find a binary and I don't know how to compile it myself. Is there a link to a newer pre-compiled binary I'm missing?
[Android Software/Hacking General [Developers Only]] Whookid:
This worked like a charm! Thanks!
[Android Software/Hacking General [Developers Only]] gps3dx:
Run ApG as "Administrator" ( right click then "run as..." ):cool:
[Android Software/Hacking General [Developers Only]] freddysam:
That didn't change anything for me. These are the lines that it is referring to:

red=$(tput setaf 1) # red
grn=$(tput setaf 2) # green
cyan=$(tput setaf 6) # cyan
txtBold=$(tput bold) # Bold
txtReset=$(tput sgr0) # Reset
[Android Software/Hacking General [Developers Only]] mvsroot:
Problem to patch CM 10.1.1 for Nook Color

I've got a problem to patch the latest stable cm 10.1 for Nook Color (cm-10.1.1-encore.zip)

cm-10.1.0-encore.zip works fine:

./auto_patcher /home/al13808/Downloads/cm-10.1.1-encore.zip openpdroid cm

The Auto-Patcher v2.9.924

### checking for updates ###
Updater: Auto-Patcher is already up to date

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.2.2 rom= aosp ...
... Using cm patches ...
... openpdroid patch date has been set to: 20130626 ...
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: system/framework/telephony-common.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: 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/al13808/apktool/framework/1.apk
### copy patch openpdroid/4.2/cm/20130626 ###
... copying system/media/PDroid.jpeg ...
... overwriting system/media/PDroid.jpeg from openpdroid ...
... overwriting ContentResolver.smali ...
### jar patch openpdroid/4.2/cm/20130626 ###
... apply framework.patch ...
... apply preloaded.patch ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/provider/Settings$Secure.smali' in framework.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

Thanks!
[Android Software/Hacking General [Developers Only]] mvsroot:
Does anybody know if it is necessary to de-odex all apps in a ROM or can I mix odexed and de-odexed apps?
[Android Software/Hacking General [Developers Only]] freddysam:
FYI, manually adding the ncurses package to cygwin fixed the problem:
[Android Software/Hacking General [Developers Only]] mvsroot:
Thanks! cm-10.1-20130711-NIGHTLY-encore.zip works again. I was just surprised that the old cm-10.1.0-encore.zip works and the newer cm-10.1.1-encore.zip doesn't.

EDIT:

This works too:

./auto_patcher cm-10.1.1-encore.zip openpdroid cm 20130516
[Android Software/Hacking General [Developers Only]] IRKONIK:
Okay..I made it all like you said, still errors:

Log_1: http://pastebin.com/r1kz4URb

Log_2: http://pastebin.com/QB6X4SMZ

Rom: http://xdaforums.com/showthread.php?t=1745003

..it's even on a fresh machine :D
[Android Software/Hacking General [Developers Only]] Urinophoria:
Lol, I guess I walked right into that one didn't I?

Don't apologize for the rant, I feel the same way; and frankly the system apps are the ones I'm most interested in blocking. I usually won't install non-system apps if I don't like the permissions (Facebook anyone?) just because I don't want to support that kind of development. I set up a tasker webpage shortcut so I could have an icon for m.facebook.com on the rare occasions I actually use facebook, but their app has been a no-go since my HTC merge was new.

Nice thing about google is that in spite of asking for a lot of unnecessary access, their apps work just fine with the access removed. All I have enabled on G+ for instance is camera access (for obvious reasons) and it works just fine for my usage. They request 5x as many access points as any other app I use, but they don't seem to NEED most of them.

---------- Post added at 07:53 PM ---------- Previous post was at 07:48 PM ----------

Do you mind patching it as aosp for me and tell me what happens? Or just let it autodetect?

ie: ./auto_patcher.sh romname.zip openpdroid

That's the same source I use for my DD but I compile for d2att then use autopatcher, patching as AOSP. I discovered that by accident when I forgot to include the ROM type flag and autopatcher figured it out on its own. I haven't told it what type of ROM to patch since then, unless I get an initial fail.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Yeah, I "know" that google does not "use" all this info, but knowing that they COULD makes me.. uncomfortable ^^ Paranoid user (you see what I did there? Anyone? No? Ok :( )

Well, I did what you want. Both things even: http://pastebin.com/jGqSQftZ is fully auto-detect DERP-mode (no chosen mod and romtype - mateorod you joker :D I lol'd)

Also as AOSP: http://pastebin.com/aQSgxZsK

Thx for your help man :D
[Android Software/Hacking General [Developers Only]] Urinophoria:
I'm sure the APP doesn't use the access permissions it asks for, but I'd be willing to bet that Google does, lol! Narrow distinction but I understand the Paranoia :P

Just tried it on mine, same effect. Gimme a bit, I'm gonne build a fresh one from latest and see if it's still broken. If so I'll make some new patches for Mateorod.

Getting a bunch of stuff coming in on the sync, so it's possible they already broke the patches even though they're only a couple days old.

I'll throw a temporary link up for the patched version so you can have access as soon as I have it compiled. There's always a chance that the maintainer decided to tweak something outside of the official source and broke the patches too, so it'll be a good test.
[Android Software/Hacking General [Developers Only]] xculliber:
PA 3+

Successfully patched latest PA 3+. Will flash and report findings.