yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Dumhed:
Aw snap. I should have checked that to begin with. Too bad, 'cuz I liked that rom quite a bit.

I'll give the link a try, then try the patch again. And of course, I'll report here how it goes.

---------- Post added at 04:32 PM ---------- Previous post was at 04:22 PM ----------

Hmm... actually, I checked again at the ROM's site and it is deodexed... checked the rom zip and there are no odex files in there.
[Android Software/Hacking General [Developers Only]] mateorod:
Hard to say. Try CM9 first, and then move onto AOKP. Try the various patch dates. You can see which patch dates are available by entering

./auto_patcher <ROMNAME.zip> -h

and try the various sets by trying

./auto_patcher <ROMNAME.zip> v6supercharger,pdroid cm9 2012<etc>

For device-specific roms (not-cm9, aokp, etc) the only way to find out if it is supported is to try it yourself, we don't know any more than you do.
[Android Software/Hacking General [Developers Only]] pastime1971:
even though it is based on AOSP, it is not AOSP

DjSound must have made quite a few changes.

you can invite him to my thread, http://xdaforums.com/showthread.php?t=1554960

and encourage him to include PDroid in his rom.

it would be a piece of cake to include PDroid to his source.
[Android Software/Hacking General [Developers Only]] Dumhed:
I'm realizing that the rom I'm using, Eclipse ICS for Droid Razr, is device-specific and not cm9 or aokp. (See a few posts back for my errors).

Other than testing out various commands is there anything else I should try? I have tried adding the pdroid to the command line, etc.. (don't know what to put for date)... either way, it just can't seem to extract the stuff.

I'm on the current ROM because out of the various ICS roms for the Droid Razr, Eclipse seems like the most stable with everything working, while the other roms have a few things here and there that don't work. But if I can't get this to work with Eclipse, I may need to jump to something else. :(
[Android Software/Hacking General [Developers Only]] Devo7v:
I've been trying to get this patch working on Fuison ICS Beta for the Samsung Captivate. I've installed JDK and Cygwin on a Win7 64-bit machine and have been able to get Auto Patcher to run. It seems like it's working but for some reason fails when it tries to patch the framework.

I'm not completely sure why it's failing, but hopefully somebody might know why. I know its been mentioned that Auto Patcher might not work with all ICS roms, but hopefully it's something I'm doing wrong and pdroid will work with Fusion ICS. Any help would be appreciated. Below is the log file.
[Android Software/Hacking General [Developers Only]] Shano56:
shouldn't this be

sudo apt-get install openjdk-7-jdk openjdk-7-jre
[Android Software/Hacking General [Developers Only]] pastime1971:
i assumed it was openjdk-7 since i don't have an ubuntu around me. didn't know it was -jre. thanks for the correction.
[Android Software/Hacking General [Developers Only]] mateorod:
I don't know. Post the log generated when you ran the auto-patcher and we'll know more.

Thanks to both of you guys for tipping me to that. A trivial error to an unused (at the moment) portion of the code, so any update.zips made are fine. But it is now fixed.

Auto-patcher 2.4.5 is up to the download page.

Improvements include:

Mostly bugfixes. Those include aosp and Evervolv for pd2.0

Hopefully, a net to ensure we never have the method cap issues again

As always, if the auto-patcher is already doing what you want, no rush to update.
[Android Software/Hacking General [Developers Only]] Hotfingers:
Hi all, the auto patcher works with the latest cm10 for xperia arc.

Tested pdroid and pdroid2.

Thanks @materoid for this tool.
[Android Software/Hacking General [Developers Only]] m0d:
Is it possible to add this mod to autopatcher ?

http://xdaforums.com/showthread.php?t=1920612

Is there a template to follow in order to add it ( i.e. in patches folder ) ?
[Android Software/Hacking General [Developers Only]] m0d:
Two people who have worked on mentioned MODs are gangsterjoop and Goldieking

In gangsterjoop devhost he has the modded files http://d-h.st/FdT

and to revert back from it: http://d-h.st/Rrz

Found here:http://d-h.st/users/gangsterjoop/?fld_id=7114#files

As for smali,

Hope they can help you incorporate MODs to the project

Best of luck
[Android Software/Hacking General [Developers Only]] Revionion:
log Aurora ICS(Elora)

Here is the error log,

thank you in advance
[Android Software/Hacking General [Developers Only]] mateorod:
You are actually using a deprecated ROMTYPE. We dont have aosp-mod anymore. I managed to pare it down to just four ROMTYPES: {pa, cm, aokp and aosp}.

We still use those aosp-etc demarcation internally, but users dont have to worry about it anymore.

Try just aosp as the rom.

We do not support skinned Aosp right now, as an aside. So if that Rom is Sense or TouchWiz based it won't patch.

I have error checking for the aosp ROMTYPE for jellybean, i will try and add it for ICS.
[Android Software/Hacking General [Developers Only]] herpehancock:
Running LiquidSmooth RC7 for d2tmo and keep getting this error. Can't figure it out :/ Any help would be greatly appreciated.
[Android Software/Hacking General [Developers Only]] mateorod:
Looks like a big amalgam of cyanogen, aosp and aokp. Try adding 'cm', and then if that doesn't work try adding 'aokp'.
[Android Software/Hacking General [Developers Only]] herpehancock:
No dice. I tried manually setting the patch date to the latest patch date and still the same error as posted before. Thanks.
[Android Software/Hacking General [Developers Only]] WJThomas:
The Nook appears to be unique in that it has both the sdcard0/sdcard1 and emmc/sdcard mount points implemented. My Atrix 4G just has the sdcard0/sdcard1 and a legacy sdcard. This change has broken some old but useful utilities.

I've always felt that the emmc/sdcard model was backwards due to the app2sd capability. If I swap out my sdcard for one with a different movie/music selection, I break some apps. That is why I always do the swap, but recent CM builds don't have that option.

For the near term, my Nook will have to live with the backwards default setup because of a CM10 Bluetooth issue with my GPS receiver. I have gone to a dual boot from emmc, and the shared 2gb emmc partition is just too small for my needs. I'm sure others will benefit from the update though.
[Android Software/Hacking General [Developers Only]] drich2020:
CM7

I dropped the 3 jar files from update to full Rom, then flashed with no success. Please see attached logcat file
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I am willing to go at this until I am out of ideas if you are willing to keep at it as well.

I have three zips for you to test, and a change I made to the auto_patcher is involved, so maybe this will give us some answers. If you would flash them in the numbered order, you can stop as soon as one doesn't work. So if the first one bootloops, don't bother with the others. If not, proceed to number two.

The first zip is meant to test the updater-script. It contains stock system.jars, lifted directly from the CM build. Since the restore.zip is working I expect it to work.

The second zip contains stock jars as well. But these have been decompiled and then recompiled w/o change. Let's see if the decompiling process is at fault.

The third zip has been auto-patched, but with some more gingerbread specific command-line arguments. If this works, test pdroid.

I am including a restore, but you can just flash the rom as well. I took these from the Nov.11 build for buzz, which I believe to be correct for you.

I was all set to test myself, but when I went to pick up my Nook tonight, the screen won't turn on. Even with a bootable sdcard. With two Nexus 7 screens having cracked within a week of ownership, I am officially no longer an Android owner. Not happy...
[Android Software/Hacking General [Developers Only]] seancojr:
I just tried this a couple of times with the Paranoid Android port by strapped365 but it failed each time. Any ideas?

http://codepad.org/i6juYrmJ
[Android Software/Hacking General [Developers Only]] coolnameless:
ly-f1 cm9
[Android Software/Hacking General [Developers Only]] MordyT:
Hi,

So I used CWM to make a image.zip of my current ROM. Tried running it through ApG only selecting pdroid.

Pulling latest changes of autopatcher from GitHub...

*** Please tell me who you are.

Run

git config --global user.email "you@example.com"
git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident <@.> not allowed
Cannot save the current index state
Already up-to-date.
Running autopatcher with the following arguments:
ROM_PATH: /cygdrive/c/Documents and Settings/name/My Documents/Downloads/image.zip
PATCH_TYPE: pdroid
ROM_TYPE:

The Auto-Patcher v2.4.5

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
### probe rom type ###

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: unknown ROM version
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /cygdrive/c/Documents and Settings/name/My Documents/Downloads/ApGPackages/ap/log20121113100353.txt for any debugging

! patching failed.
! it may be possible to patch /cygdrive/c/Documents and Settings/name/My Documents/Downloads/image.zip using other patch version

The Auto-Patcher v2.4.5

usage: ./auto_patcher [ROMNAME].zip [MODS] [ROMTYPE] [PATCHDATE]

* [MODS] can be pdroid, pd2.0, v6supercharger, tabletUI, etc...
MODS can be combined by separating them with a comma and NO SPACES!!!

* [ROMTYPE] can be cm, aokp, aosp or pa [recommended]
* [PATCHDATE] will select older patch versions, e.g 2012103 [optional]

try "./auto_patcher ROM.ZIP -h" to see what is available

Ideas

Sent from my Google Nexus
[Android Software/Hacking General [Developers Only]] mateorod:
You are using the patcher correctly. I guess this rom is a port of something from the HTC sensation? I couldn't speculate as to what system files make up this rom. If it is built from PA sources, we can patch it. Perhaps there are some CM system files in there. The best thing I can suggest is to try the other ROMTYPES, specifically cm. But while we support most roms at this point, winzipping (if that is indeed what this is) will always be troublesome.
[Android Software/Hacking General [Developers Only]] MordyT:
Newer CWM Recovery's allow you to make a "nandroid" in a update.zip format. This allows a person to flash a rom, mod the system partition to their liking, make the "nandroid", and have a update.zip that includes system, boot, and recovery (data is not in it). Then they can share away.

What I am trying to do is patch a stock ROM. I happen to like the stock ROM for the Toro (available from google factory images). I can't patch the factory image (see my post in this thread from before), so I figured I will flash and then turn it into a flashable zip... hahahaha, I have no luck.

Not only does the zip have a system.img, but I assume it is odexed as well.

If there is any other way for me to patch a nexus factory Image please let me know. Otherwise I will have to say goodbye to my privacy... or switch to a custom ROM (I would love to switch to CM, just as soon as they have a stable current build for Toro.. they never had stable cm9 when ICS was the latest and they don't have a stable CM10 yet... frustrating...)
[Android Software/Hacking General [Developers Only]] drich2020:
I'll test them and keep you posted
[Android Software/Hacking General [Developers Only]] MordyT:
I am just having no luck, like 0 for 6.

Using CM10 Stable for Toro:

Log: http://codepad.org/GHY0qQuL
[Android Software/Hacking General [Developers Only]] mateorod:
You ran it correctly.

There should have been an output that said this:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! 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!

Although if you are using ApG, I don't know how it handles our error messages...

There is no support for factory images, as I said, although you almost certainly can find a deodexed version of the Nexus AOSP in the forums..I am sure people are building and releasing that.

But just run the patcher exactly as you did before, it patched fine, but periodically the smali binaries we use to recompile the system.jars craps out on us. I am hoping that will be fixed when JesusFreke releases his next build.
[Android Software/Hacking General [Developers Only]] marcogtt:
Please devs support custom ROMs based on stock base for Samsung gs3.

Please. I want my privacy back

Inviato dal mio GT-I9300 con Tapatalk 2
[Android Software/Hacking General [Developers Only]] MordyT:
I reran it and it worked fine this time. Now to flash cm10 and test....

Awesome work!

Sent from my Google Nexus
[Android Software/Hacking General [Developers Only]] mateorod:
Android 4.2
​

As you are probably aware, Android 4.2 has begun to roll out. AOSP has it already, CM and the rest are merged already or soon to do so. Edit: It looks like they are perhaps going to roll this out slowly, idk. I guess we'll just have to see when it drops. Oh yeah, I wish they had done this awhile ago...

It will probably, in the best case, take us several days to update all of our pdroid/pd2.0 patches. We have to make multiple builds of each rom before I can even begin to make the patches. It is a time-intensive process.

The maintainers (poncik, wbedard, FFU5y and I) will be doing the best we can.

Please be patient with us as we move towards the update. You will know that all mods and roms we usually cover are again supported when I release Auto-Patcher 2.5 (or maybe 3.0). I will not be responding to each and every error report about this issue. If you see someone struggle, update them on the situation please. A link to this post will be at the top of the OP, so hopefully the word will get out.

We need a maintainer for stock Samsung. Try and find someone in your device forums who wants pdroid support and is ready to build stock roms. I can walk them through the process, but I cannot take it on myself.

Great! I have really worked on the error catching, I am hoping the auto-patcher will walk users through any problems. But as of now, I don't know exactly how ApG handles those function returns. I will look into it...
[Android Software/Hacking General [Developers Only]] drich2020:
I havent had time to go to the boot process because I got: " Error in E:/sdcard/1updatestock.zip (Status 0) Installation aborted". I'm not sure that I need to flash the second one.
[Android Software/Hacking General [Developers Only]] karamelos:
It's an incompatible update-binary in ZIPs, replacing it with a compatible one will usually fix this error
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
FAILED on the PA nightly

EDIT: looks like it was the tabletUI patch that did it too me
[Android Software/Hacking General [Developers Only]] mateorod:
No need for tabletUI on Paranoid Android. Good looking rom, though.;)

@karamelos

Thanks for the catch with the updater-binary...i will look into what i did to cause that...

@Cm7 tester (sorry, dont have your name in front of me) I hope I have the right device. Buzz, right?
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
err...mate hope that was sarcasm cuz this is your PA rom i'm running on the nook color.
[Android Software/Hacking General [Developers Only]] mateorod:
Oops...that part of the reply was directed at karamelos above you. Probably should have said so.

Your patch attempt failed because you tried to apply tabletUI on a PA rom. PA has tabletUI built into the framework. I will add an error catch to that. We need to institute a conflicts/depends structure anyway.
[Android Software/Hacking General [Developers Only]] kobik77:
ApG checks the bottom line, was an update.zip created or not.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] drich2020:
Since flashing this file was part of a test protocol, I can hardly replace it because I don't know what I would be doing.
[Android Software/Hacking General [Developers Only]] mateorod:
That's no problem...I can remake them. Would you post a link to the rom you are currently using so I don't make the same mistake twice?

Sorry about the confusion and thanks for the diligence.
[Android Software/Hacking General [Developers Only]] drich2020:
Here is the link to the ROM: http://download.cyanogenmod.org/get/jenkins/11677/cm-7-20121104-NIGHTLY-buzz.zip

P.S. I am the one who should be thanking
[Android Software/Hacking General [Developers Only]] funkydaemon:
DEX and patch version issues for CM7.2, with solutions

I have successfully used auto_patcher v2.4.5 to create a Pdroid patch for the official CM7.2 (vivow). However it initially failed for two reasons, which I was able to work around.

The auto_patcher generates v36 DEX files, but CM7 can only handle v35. The issue is that smali is called with the "-a 15" option. The end-user fix is to remove "-a 15" from the 3 places where smali is called in auto_patcher. The real fix would be to set smali's "-a" parameter properly for the target ROM.

The auto_patcher selected the 20120514 version of the Pdroid patch. I think it chose this one because newer versions are newer than my target ROM. However, as you say in your changelog, final support for CM7.2 came more recently, so I had to manually choose the latest for it to apply cleanly (still with some "already applied" patches rejected). Anyway, my end-user fix was to specify patch date 20121020 instead.

Many thanks to auto_patcher authors and contributors! :D
[Android Software/Hacking General [Developers Only]] mateorod:
The API level fix has actually already been pushed to github as of maybe a week ago. SO if you are using ApG, that fix will already be in.

The reason the romprobe fails is because I guess CM7 doesn't use the UTC time stamps I use for the probe (I don't know why. I actually wonder if it isn't a mistake they are unaware of. The entry is there, but at zero.)

So if you want to patch CM7, and are on ApG:

./auto_patcher ROMNAME.zip pdroid cm7 20121020

FIXED

An update for our download page will be out later today.

Thanks for your report, I was hoping that that was the problem. Saves me the trouble of making that test suite over again...

Update 11/18

Auto-Patcher 2.4.7 is up to github and our download page.

Improvements include

CM7 is finally working, it seems. Let us know.

Internal improvements to script- make it easier on collaborators

CM7 nightlies can be patched as normal

./auto_patcher ROMNAME.zip pdroid
[Android Software/Hacking General [Developers Only]] a3955269:
I've ported pdroid patches to WanamLite ICS LPZ V12.8 (stock deodexed 4.0.4 i9100 rom) the other day. If there is some interest to include them in auto-patcher let me know.

My patches are based on ics-generic-latest included in auto-patcher. I've (hopefully) removed all patches that were originally not included in pdroid java source patches.

To give you an idea: framework.patch (737,949 bytes) vs. my-framework.patch (474,102 bytes), so my patches should be way easier to port to newer versions:)
[Android Software/Hacking General [Developers Only]] Parafly:
The OP should really be updated with these links. I was getting some sort of calendarprovider.apk file from the link in the OP.

---------- Post added at 07:26 AM ---------- Previous post was at 07:20 AM ----------

Oh I meant this. The link brings me to a DL for calendarprovider.apk?
[Android Software/Hacking General [Developers Only]] coolnameless:
ly-f1
[Android Software/Hacking General [Developers Only]] mateorod:
Just as an FYI, the ICS generic latest patches are actually just symlinks of the aosp latest. Which is what you want, but just in case that wasn't apparent.

I can understand the impetus of wanting to pare down the patch size. Let me tell you why we haven't played with that.

The way we make the patches is through the java patches. We pull source and then build a straight build. We then patch the rom and rebuild a Pdroid build, without repo syncing. So the source is only changed by the addition of PDroid. Then we decompile the files and get the changes. Those changes are our patch.

It can look like we are patching files that aren't included in the java patches, and indeed, factually that is true. But the way that the rom is turned into dalvik code somewhat deseminates those changes to unexpected areas.

For an example, if we change the ROM so that every time a certain method is invoked, the information is sent to a Privacy Catching method we have added by way of patching. Now, every place that method is called, (and that can be difficult to track down) has to be adjusted. The change in those methods is spread throughout the whole rom.

Now we could sit down and decode the smali language ourselves (and that may be what you have done, the method is available) however I reasonably happy with the process as is. We have a really wide range of portability, the problems are only for roms that tend to be device-specific, and even then, those devices tend to be legacy or headed that way.

What it comes down to, is that our smali patches for sure capture all the changes we might need. And at this point, we are able to patch just about everything we want to without much problem. Any troublesome files can usually be resolved by provisional copying (ContentResolver, GSMServiceStateProvider, etc). And what it really comes down to is that some roms are simply too esoteric for us to really dig into and are better handled by the individual. If I see errors in the ServerThread, then that is an unportable error, and we may be seeing what we call a new ROMTYPE. As of now, we use AOSP, CM, AOKP and PA for our users, while internally distinguishing between Evervolv and AOSP kangs as well.

I would certainly be interested to see what you have changed, but I am unlikely to change how we approach patching at this time. I worry that desconstrucing the patches by hand exposes a strong likelyhood of human error. Also, since our range of portability is quite high, I just don't see the need to take the risk.

Definitely worth looking at, though, so thanks.

Hmm. Okay, thanks. I will pm Kobik, as I don't do anything for ApG.
[Android Software/Hacking General [Developers Only]] :
Can anyone explain this to me:

From APG post:

From where do i run it? :confused::eek:
[Android Software/Hacking General [Developers Only]] scutworker:
Anywhere other than the above! I created a folder on C called Pdroid and stuck it in there.
[Android Software/Hacking General [Developers Only]] Gootch@GMX.de:
on screen buttons not visible

Hi,

I flashed the stable CM10 on my Galaxy Nexus and patched it with the autopatcher.

After flashing the Update.zip the on screen buttons not shown any more.

I've testet the 2.1.7 and 2.4.7 autopatcher with both the same result.

Is ther any solution available or I'm the only one who has this problem?

/Gootch
[Android Software/Hacking General [Developers Only]] mateorod:
I have never heard of that happening. Would you post the log generated by the patcher, and a link to the rom you patched?
[Android Software/Hacking General [Developers Only]] drich2020:
It works

Everything works ok. This forum rocks and the members are fantastic
[Android Software/Hacking General [Developers Only]] a3955269:
Well I've took a close look at what those patches do and those are just unneeded label changes introduced by the pdroid code. Java has no IPO optimizations at compile time to my knowledege, one jave file, one class. There JIT but that has nothing to do w/ compiler.

Anyways see attached zip, it also includes 2 python scripts which splits patch/diff file into single patches. Helped me a lot:)