yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks for the log. I can probably resolve this for you this weekend. Look for the next update to address this.

Seriously?

Well, if you would have read the last page or so the answer is there. You would also see that i am out of town, and took my vacation time to update the program for y'all. I didn't have time to update OP, but I would have thought it could have been figured out by anyone willing to read back some, or merely extrapolate from extant data.

No, it simply means that those files are already in the shape they need to be in for PDroid to work. Not an issue. I will try and add a FAQ this weekend.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks for the log. I can probably resolve this for you this weekend. Look for the next update to address this.

Seriously?

Well, if you would have read the last page or so the answer is there. You would also see that i am out of town, and took my vacation time to update the program for y'all. I didn't have time to update OP, but I would have thought it could have been figured out by anyone willing to think or read back some.

No, it simply means that those files are already in the shape they need to be in for PDroid to work. Not an issue. I will try and add a FAQ this weekend.
[Android Software/Hacking General [Developers Only]] Sec0nd:
ApG CM10 failed

I tried to patch pdroid to cm10, but it failed here is the log:

What should I do?
[Android Software/Hacking General [Developers Only]] kobik77:
ApG 1.2.0.0 is up
[Android Software/Hacking General [Developers Only]] KicknGuitar:
Cheers! Thank you.

I have a question about the patches since I'm pretty new to this whole realm. Once a zip is "auto patched" does that make the patch file universal for all of the same zips? For example, when cm-7.2.0-jordan.zip is ran through the auto patcher, anyone who has cm-7.2.0-jordan.zip installed can use the patch just created by the auto_patcher? If this is true, is there a database with patches available for download, as to avoid running a patcher?
[Android Software/Hacking General [Developers Only]] mateorod:
You appear to have run the program correctly. There are a bunch of failed patches. I will be back home Thursday and can look into that further then. I find it hard to believe that many files went out- of- date at once. The ServerThread.smali usually fails to patch when the wrong ROMTYPE is chosen, which doesn't seem to apply in your case. Try aosp-mod and post results, is the best i can do right now.

Yes, they would work for that build for that device. At one point we thought about hosting a PDroid patch repo. But as the list of offered mods grew the tool grew as well. Lots of the power of the auto-patcher derives from its ability to "layer" mods. There are now thousands of combinations when you consider all the variables.

Plus, the reason the patcher is needed is that the zips go out of date quickly due to nightly development cycles. For instance, an update.zip repo,for CM10 for one device would have at least 10 zips,for PDroid alone. The management and maintenance for such a project would be unreal. Trust me when i say that the upkeep of the universal patches is nearly unmanageable.

I could see someone hosting such a repo for one device however, with the number of ROMTYPES depending on the maintainers commitment level. But from our end, we are working on developing the most versatile and solid platform we can. The next steps is our GUI for Linux, Mac and the granddaddy, Android.

When the Auto-Patcher becomes a proper apk, then it will hopefully be easy enough that people can run the,program with ease.
[Android Software/Hacking General [Developers Only]] KicknGuitar:
Ahhh, I was a little too narrowly focused, thinking of only my "collection" of ROMs (CM7... and... um.. CM7) Now that I think about it, that's a lot more manageable than the whole Android Universe. Looking forward to you guys developing this one, especially I don't have any Windows/Linux machines and I am finding Windows harder to come by as Apple aims for fashion and finds it... Cheers.
[Android Software/Hacking General [Developers Only]] Sec0nd:
Thank You for your response, I have tried that, but failed again.

Here is the log:
[Android Software/Hacking General [Developers Only]] kd-:
Great work! Just used this to patch a CM9 ROM for my Rezound and it worked flawlessly. Although, I did already have the JDK and Cygwin installed on my computer for other reasons - maybe you could check the PATH variable before downloading the packages? Just a suggestion - thanks again :)
[Android Software/Hacking General [Developers Only]] Kiwyxda:
Hello it's sush a great work you do,

I'm using it to patch pdroid on cm10 on my xperia pro mk16i, but when I want to limit acces to localisation to browser or google maps it just doesn't work at all.

I'll post it also in the pdroid jb port thread.

btw you do such a great job please continue that way
[Android Software/Hacking General [Developers Only]] scutworker:
Hi,

Has there been any progress on patching Evervolv roms? I have just tried the latest patcher under cygwin for Pdroid only and get the error:

"error: failed android/app/LoaderManagerImpl$LoaderInfo.smali' in framework.jar cannot be remedied"

I'm using this ROM on an HTC Desire:

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

The log is attached to this email.

Once before you kindly provided me with a test zip to flash and it worked except the file managers then failed as did some other apps. I reported this and attached the logcats here:

http://xdaforums.com/showpost.php?p=31477234&postcount=653

Any help in getting Pdroid up and running would be great.

Cheers.
[Android Software/Hacking General [Developers Only]] mateorod:
The code to check this is already in the auto-patcher kobik, may e you could have those packages downloaded if they result in the error messages. Or just check them in the same manner we do on your own.

Thanks for the kind words. Please do post that in the port thread so we can look at it, and please some more specifics (logs too?) so we can see what we are working against.

The zip I had you test was done by the aosp-mod method. I haven't added it to the OP because I was out of town. Try that ROMTYPE and let us know.
[Android Software/Hacking General [Developers Only]] scutworker:
Thanks. I gave it a go with ROMTYPE set as aosp-mod and it failed with the same message as before :crying:

The log's attached...

Cheers.
[Android Software/Hacking General [Developers Only]] MordyT:
Hi fellows.

Auto-patcher failed.

http://codepad.org/Oz0oGl11

In what format is the .zip file supposed to be?
[Android Software/Hacking General [Developers Only]] mateorod:
hey all. I am back at my computer today. I have started some builds and will begin sorting out any lingering issues that arose once I was on vacation, including:

CM7- we have the infrastructure in place that should allow us to handle this from now on

The recent Cm10 ServerThread fails that have been scattershottedly reported.

Whoever posted the log attempting to patch a system.img, we don't support that now. The methods of unpacking and mounting system.imgs vary pretty widely from device to device, and we don;t have anyone on the team building those images or their patches. I am not saying never, but we don't support system.imgs right now.

I will be looking at these issues tonight. Please report any successes or failures in the thread, we need the data points.
[Android Software/Hacking General [Developers Only]] kobik77:
Hey Mateorod,

Did you get my PM with about phone hanging in boot animation?

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, but I forgot about it, as I got it late during my vacation. I will look into that as well, and may ask for more info. Thanks kobik.
[Android Software/Hacking General [Developers Only]] MordyT:
That would have been me. How do I build a patch for a stock toro jro03o ROM then? What needs to be in the zip file?

Sent from my Google Nexus
[Android Software/Hacking General [Developers Only]] kobik77:
I prefer not to rely on an already installed packages as they may not contain what's needed for autopatcher to run.

This way I have a complete control on what packages users get and don't need to debug why things aren't working as intended.

This also eliminates posts such as "Why do I get an error message 'missing diff tools'".

Overall, ApG isn't only about GUI.

It's intended to bring its users a complete automation envelope for using autopatcher in a simple, strait forward way without the hassle of configuring and installing stuff by themselves.
[Android Software/Hacking General [Developers Only]] SecUpwN:
The latest autopatcher does not recognize the new DisarmedToaster 0.2-ROM. Anything I can do other than trying to specify manually? Can I trick the patcher somehow? :p
[Android Software/Hacking General [Developers Only]] mateorod:
Huh? I can see from your sig that you usually patch this rom. What do you mean it doesn't recognize it? Are you using ApG or the command-line version and in either case could you post the generated logfile so we can all see what is going on?

The curated selections from your logfile show that you are trying to patch an older build, one from 09/04, correct? The ServerThread failures are generally due to selecting the incorrect ROMTYPE (aosp-jb instead of cm10 or similar issue), although a deprecated PATCHDATE could certainly fail in this manner as well.

But in your case the best command to run would be

./auto_patcher CM10-120904-NIGHTLY-Defy.zip pdroid cm10 20120901

The PATCHDATE argument is best passed as the PATCHDATE that is immediately before your actual build date. We are working on making the build.prop querying of this argument more precise.

If you look in your posted log, you will see this:

### probe rom type ###
# VER= Auto-Patcher v2.1.2
# OS= darwin10.0 64bit
# VID= 4.1.1
# MID= cm_mb525-userdebug
# RID= cm10
# BDID=
# DID= umts_jordan
# BID= latest
# PID= pdroid

This is the result of your build.prop query. There is a blank section on yours for BDID which is where the build date of your rom is calculated from the UTC time. I would have noticed your problem earlier if the querying of this parameter hadn't failed. Could you do me a favor and post your build.prop regardless of the success/failure of my suggested command? I would like to see why that section of the rom probe failed, and try to make it better.

If you would ever like to see the PATCHDATES available for each mod, run

./auto_patcher ROMSNAME.zip -h

It isn't the prettiest of printouts, as it has outgrown its original format. I have some plans to run it through awk sometime soon and clean it up, but I haven't had the time yet.

edit

Sorry, missed this somehow.

I have personal experience building AOSP, AOKP and Cyanogen. I haven't built any stock roms, so I am not sure how one goes about it, or if the source for home building is even available.

I had a grouper device, and for that device deodexed stock zips were available from a couple places. Your first thing to try would be to look for one of those. The zips need to be deodexed at this point. Then you can try patching with the aosp-jb patches. If that fails, then the next step would be trying to locate source and build the rom. If you can find a way to successfully build, then you can add the build patches and we can see about adding support for your rom that way.
[Android Software/Hacking General [Developers Only]] SecUpwN:
Tried by command line using the latest patcher. It just tells me "ROM not recognized" - right after analyzing the framework. Not more. This is probably due to the fact that the ROM has been restructured to use the AROMA-Installer, letting one select build (AOKP, CM or ParanoidAndroid) as well as the kernel. The first of its kind here on XDA. The log doesn't say ANYTHING.

Could you try to create a PDROID + v6SuperCharger-Patch for DisarmedToaster 0.2.0 (shooteru), please?
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Is this useful? I don't know. The GSM galaxy nexus CM10 v20120929 gives a FC when trying to restore settings from backup. I had backed up to sdcard and internal storage. I was not really sure where to look in internal storage. On the 'sd card' there is definitely a restorable settings file. Maybe I should update? With Pdroid I'm a little anal.
[Android Software/Hacking General [Developers Only]] KicknGuitar:
I can't believe I missed trying the patch dates... unfortunately it was a no go too.

Sorry, mind helping me find where/which "build.prop" I am trying to find? Cheers.
[Android Software/Hacking General [Developers Only]] mateorod:
I have made a bunch of builds, and will be checking and testing them tonight. Evervolv is working my nerves, let me tell you that up front. On to the questions...

I responded to your pm. Please upload the log. Even if it doesnt look like it has much of any use, where it fails tells me a lot. I try to avoid specifically downloading every rom with reported faults. Especially since the logs solve 85% of problems. Although i probably download 7-10 roms a week to check. That is already a lot, so please post log and the link to the roms OP again, so i can keep the info straight.

Did you mean to attach something here? It sounds like you are reporting a PDroid FC. Is this your first time with the auto-patcher? We patch for 1.32 and if you backed up those settings with an earlier version i am pretty sure there are incompatibilities.

Look in your rom, it is in /system. A small text file with info and base settings for your rom. And please attach the new logfile with the adjusted patch dates, and a link to your rom. Those patches work, so we need to look deeper.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
No, sir. I've used the autopatcher and have the last update of the app. Restoring settings from the apps backup has not been a problem in the past. I had saved the settings previously and had wanted to restore them. In the actual app I had clicked restore from SD card. By doing that it had sent the app into a FC loop. I am posting what had happened here because the original development thread is no longer active. If attaching a logcat would do anything tell me to post one, please. Thanks for continuing this project.
[Android Software/Hacking General [Developers Only]] kobik77:
It's really of topic but I never had luck with restoring pdroid settings.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] anomalya:
I think it's awesome that we get PDroid ported for mass usage but the restore feature otherwise seems hopelessly broken.

I'm glad you mentioned the elephant in the room. I thought I was the only one.
[Android Software/Hacking General [Developers Only]] mateorod:
I have made a bunch of builds and checked the patches. Excepting the CM7 issues (which I will hopefully have fixed today/tonight) I didn't see anything that failed with any regularity.

To save myself from chasing ghosts, I am just ask for current bug reports. As in, if you have a failure starting now, I will look into it, but I am not going to revisit any other issues from when I was gone.

That does not mean that I will not address any concerns, mostly just that I can't keep it straight as is. So if you have a current issue, please repost your logs and info.

Sorry for if any of you have to double post, but I tried to keep my finger on the thread while I was gone and that was likely a mistake as it jumbled things in my mind to the point where I am not sure where we have needs.

Things I know about (i.e. remember) and will be looking at

CM7

Kobik's issue

If you need to file a report, please continue to post logs! Even if you think it has nothing of value, where the failure occurs or when the log is truncated tells us much.

It looks like you are running a non-CM7 version of Gingerbread. We only support CM7 for that android iteration and that will likely not change (unless someone joins the team and decides to focus on that). Sorry.
[Android Software/Hacking General [Developers Only]] HyperCriSiS:
Hello,

just got my S3 and tried to patch Paranoia ROM

The patching aborted. Tried AOSP JB and AOSP MOD.

codepad.org/UX9Mdxfq

codepad.org/ne6qBTJd
[Android Software/Hacking General [Developers Only]] mateorod:
Trying aosp-mod was closer to the mark, but if you look at the content of that link, it states that it is based on ParanoidAndroid and CM10. Try those patches and then let us know.

While technically true that it is based on AOSP (as they claim in their thread title) I can understand the confusion and would have put PA or CM10 there myself.
[Android Software/Hacking General [Developers Only]] HyperCriSiS:
Hi,

thanks. Patched sucessfuly choosing CM10. Lets see if I can get PDroid working now.
[Android Software/Hacking General [Developers Only]] SecUpwN:
Check out the NEW PDROID-EXTENSION by CollegeDev! Simply rocks, you'll love it. :)
[Android Software/Hacking General [Developers Only]] HyperCriSiS:
HELL YEAH !! Autopatching worked!! Thanks so much!! :laugh:
[Android Software/Hacking General [Developers Only]] SecUpwN:
Dear mateorod, as you mentioned I should post my concern here in the thread again. The newest AutoPatcher fails to patch DisarmedToaster 0.2.0 - the coolest ROM I've seen yet. It bundles 3 JellyBean installs: CyanogenMod 10, AOKP and ParanoidAndroid. System type and kernel are selectable through the AROMA-Installer launched when the ROM gets flashed.

AutoPatcher probably fails because this ROM is basically 3 ROMs in 1. It's developer, agrabren, mentioned he will add the framework patches to AROMA, but how to create them if AutoPatcher fails? The LOG just tells it's an unknown ROM. What's next?
[Android Software/Hacking General [Developers Only]] agrabren:
I already got it working. :) Essentially, I have to create the patch files before the combining step. My build system generates full builds for all three ROMs, and saves off the rom.zip files. The installer build takes all of these, decompresses them, re-organizes everything into groups, and makes a final zip. I run the AutoPatcher before the incoming zip files are deleted, and extract out the important bits from the update.zip patch that gets created. I then give AROMA the ability to apply the changes during install, and everyone is happy. :)
[Android Software/Hacking General [Developers Only]] mateorod:
I was just looking at your thread. I am going to have to take a closer look at what you describe here but it sounds really interesting. Thanks!
[Android Software/Hacking General [Developers Only]] nk7:
Anyone got it to patch Resurrection Remix 3.0.9? AOKP-JB...

Error message when I tried here: http://codepad.org/KjIzs3L8
[Android Software/Hacking General [Developers Only]] KicknGuitar:
CM10:

http://defy.wdscript.fr/defy-cm10/

Patch Logs (for each patch) & build.prop from my CM10

https://docs.google.com/folder/d/0By9aWmEAuGQoU3ZJeGU4aHRzWDA/edit

If there's anything else I can do, feel free to ask!

However don't go crazy on this one. If she starts creating headaches, it's alright. I have a feeling CM7 works better for me as a ROM and will end up "downgrading" her. I'd much rather have my CM7's pdroid patch working than CM10. I won't be offended should you put this one on the back burner for eternity.
[Android Software/Hacking General [Developers Only]] TheDrake:
Is it possible to include Toggle 2G/3G patch too?

http://xdaforums.com/showthread.php?t=739530
[Android Software/Hacking General [Developers Only]] SecUpwN:
Will patching for the new PDroid-Extension be included in the next release? :)
[Android Software/Hacking General [Developers Only]] mateorod:
I seem to remember this used to work- I will look into tonight, I have some auto-patcher time scheduled.

Now that is a log report! I am going to fix CM7 tonight and put out an update (early tomorrow morning, most likely) that has more precise aosp-jb mods. I will check this out as well. There is obviously something with your device (unofficial support can take many forms) that is throwing a little trouble at us, but that doesn't mean we don't have a working method already built into the auto-patcher. We just have to find it...

No the auto-patcher is working correctly. That is a new found hole in the CM7 patches, I will add a fix for you guys to test in the next update (sometime in the next 24 hours or so)

I will have to look into how this works. But I think we can pretty much add anything at this point. The limiting factors are whether the mod is available in some other, preferable manner. If this requires porting or editing of code to work on other devices, then it may be a good fit for the auto-patcher. I will look at it tonight as well.

I want to thank you for the tip, we are always on the look out for new mods to add, having users suggest their favorites is the best way to find them.

We have been in contact with CollegeDev and will be supporting his new project, the PDroid extension. It will not be in our next release however. That particular package is going to take some dedicated attention, simply because it, like the original PDroid, is about as big of a framework mod as you are likely to see.

But the framework to add it to the Auto-Patcher is already in our program, so it shouldn't take too long. We will keep you updated here and in the Pdroid extension thread as well, I imagine.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I am going to try and cover all of my bases...If I forgot your issue, go ahead and remind me and I will take a look.

New Autopatcherv2.1.5 has been uploaded to techerrata. If you use ApG you can already get at the features.

Highlights of this version include:

# 2012.10.07. (2.1.5) Final pdroid support for CM7.2 Official Releases
#	Added aosp-mod patches for pdroid patching of AOSP kangs
#	Switched to Chainfire's (f)aapt for speed/space reasons

In order...

I changed how we handle the provisionals some, as a first step in the process to reorganize our patches. CM7.2 should finally be done and have full support as a result. We had supported it for months on the PDroid-port thread, and the day we went live with the Auto-Patcher, those patches broke. I hope to close the book on that as of now.

The pdroid aosp-mod patches are to be used for any rom that is an aosp kang. How do you know if your aosp rom should use the aosp-mod patches? Open her up, and if you have a framework2.jar already in the rom, then you need to use the aosp-mod patches. The long list of ignored hunks will be gone as well, as a cosmetic bonus.

And finally we made the switch to Chainfire's faapt binaries. I have confirmed that they are indeed faster on my Linux box, but I am taking it on faith that they work on the other platforms. If you use a mod that involves apk patching, you should see a speed increase. The overall size of our download went down almost 3mb as well, a huge bonus in my book. The aapt bloated our download size, which I would rather have stay around 10mb or under. (currently fat at ~13mb)

Leftover business

Kobik, are you still seeing bootloops with just pdroid on your device? I have looked at it and I don't see any reason why pdroid would fail but pdroid and v6 work. There are situations I can imagine that might have that result, but none of those qualify here. No other reports of this from any other quarters, either.

If it happens again, could you grab a logcat, please? (Oh, and i was conscious about your changelog needs, let me know if you need any other formatting-type stuff)

nk7

I had a chance to look deeper into your logs, it looks like RevolutionRemix is AOKP based. try passing aokp-jb as the ROMTYPE.
[Android Software/Hacking General [Developers Only]] im-pulze:
I have another wish.

Is it possible to integrate the cerberus app into ApG? There are four different versions for gingerbread and ICS and later, hidden and with the "normal" button in the launcher
[Android Software/Hacking General [Developers Only]] erups:
Luckily for you virtual machines have been invented: install virtual box/parallel/whatever and mod away.