yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] seancojr:
I tried patching 'cm-10-20121103-UNOFFICIAL-doubleshot' with ApG 2.0.0 and failed. Here is my log: http://codepad.org/sBLPHJar

Update: Now testing the latest autopatcher 2.4.0, so this report may become irrelevant.
[Android Software/Hacking General [Developers Only]] mateorod:
Could you post your log files please? I have not checked the system reporting info. But I would like to see your log if I could.

Edit: I just looked [briefly] at the build patches, and they do indeed look like they update the patch version. So please post your log and we will see what we can see.

This has happened a couple times lately. It has resolved itself by simply running the patcher again. It is a bug with the smali binaries. Not one that is seen too often, but at this point I believe we are by far the most regular users of that tool. I have forked the binaries source, and intend to get with JesusFreke, should he have the time.

Point is, try running the patcher a couple times. That error is simply the binaries hiccuping.

Good man. I am out of thanks, but thanks.
[Android Software/Hacking General [Developers Only]] tsatomas:
thank you auto patcher. i apply it (apg) on helly bean for pdroid2. everything went ok with this cool patcher. great job, i ll try and other patches with this,

Just one question. Iam using inverted gapps and mms but after applying the patch the mms changed to normal. I dont know why, but I would like to know if it would be ok to flash again my inverted mms or there will be problem with pdroid2 or else? and something more, whenever I update my rom (without wipe) should I have to apply the path again?
[Android Software/Hacking General [Developers Only]] marcogtt:
Fast question for a fast answer.

This is still not compatible with patching a Samsung based stock ROM isn't it? Only aokp aosp cm right?

Inviato dal mio GT-I9300 con Tapatalk 2
[Android Software/Hacking General [Developers Only]] tsatomas:
Try it writes for many ROM, it is easy but you must have

the ROM zip and cwm to flash the update
[Android Software/Hacking General [Developers Only]] mateorod:
The answer is, you can. But you will lose the Mms functions of Pdroid2.0. But the program WILL still function w/o it. And yes, each time you upgrade your rom, you will need to rerun the autopatcher.

Flashing overwrites the PDroid files. There are methods that can stop that overwriting, but they are ultimately insufficient, as they will very quickly break your install when they become incompatible with the update.

Sorry, no. We could, we just do not have a maintainer for that right now.
[Android Software/Hacking General [Developers Only]] m0d:
it workeD - path error does not work in desktop tree

I found the problem.

It was not syncing to github because I saved the exe in desktop folders.

Moved it to c:\ApG, and now I see mods and everything,

Thank you for your time

[ I also needed to move the zip file from desktop\folders to C:\ApG ]

This can be misleading, as I had downloaded the exe into a folder on desktop, which is why it did not sync with github, I believe

When I tried again, this time moving EXE to C:\ApG\ it synced

Maybe rewording the above statement can help future users new to using ApG and autopatcher

[ maybe, Do not run ApG_xx.exe on c:\ copy it to new folder first, i.e. C:\ApG\ApG_xx.exe ]
[Android Software/Hacking General [Developers Only]] drsood:
Is it possible to have pd2.0 on cm gingerbread?

Edited: NEVERMIND
[Android Software/Hacking General [Developers Only]] kobik77:
Hey guys if you have any problems syncing ApG with GitHub, try deleting ApGPackages\ap folder and run ApG again.

If you still having problems contact me on PM as it's kinda hard to extract ApG related issues for there are at least 10 pages to read through here every time I visit here.

BTW, patch of CM10-20121107 using ApG went smooth for me.

BTW2, @mateo, is this line is right for 2.4.0?

pd2.0 patch date has been set to: 20121017...
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
I can confirm this work around. I was having issues with Cygwin so decided to install ApG. Saved to desktop and would not sync with github servers if my life depended on it. Moved it to my Auto_patcher folder in my documents and it synced the first time.
[Android Software/Hacking General [Developers Only]] mateorod:
As always, thanks Kobik.

In short, yes the patch date selection is correct.

I struggled with how to handle this. Because these new patches are being released because of a software update by CollegeDev, not because of broken patches.

With our new (mostly) automated rom probing, the best match for your rom is determined by build date. But these new patches will technically work for any 4.1.2 roms, since they are just a bug fix. So if I made the new patches have the date 20121106, then all new roms would be set. But what about someone with a rom from, say, October?

They would have automatically gotten the older patches, even though the new ones would work on their rom and would perform better.

Not a situation that occurs in any other mod, where one patch fits all and I could deprecate the old patches in this situation.

I wanted to keep the old patches available, since these new ones are just now being tested by you guys. If there was a new bug, I wanted the original patches to remain available.

So what I did, through symlinks, is make it so that all roms would get the new patches, by setting the new patches to have all dates EXCEPT 20121016. So if someone wanted to roll back, they would have to specify that exact date.

Does that make sense? Sometime it is hard to know if I am being clear about the inner-workings of the program, I spend so much time shoved in its guts.
[Android Software/Hacking General [Developers Only]] Gargantuantua:
I wiped and retried patching. This time pdroid says patch 1.51 and seems to be working great. Not sure what I did wrong, but thanks for the help and work!
[Android Software/Hacking General [Developers Only]] drich2020:
Definitely need help

After a few weeks of fiddling, I came to the conclusion that asking for help is mandatory now. Besides lurking into the forum, I have been using/learning cyanogenmod for a while and have been steadily improving the performance of my phone. I hit a roadblock while trying to patch my CM 7.2.0 on HTC wildfire (Buzz) with pdroid & v6supercharger. Manual patching and restore did not give the expected results and luckily (I thought) I encountered the autopatcher. I tried so many times ( multiple versions, multiple MODS patchdate) with no success, even a failure to restore, which lead me t understand the real meaning of nand backup (I didnt do it). Here is my situation:

Phone: HTC Wildfire (buzz)

Rom: CM 7.2.0 nightly build november 4

Kernel: Sempfinity 4.1

Goal: better performance & privacy (hence the mods chosen)

Need: a working CM 7.2.0 patched with pdroid & v6 supercharger

Could someone provided download link ( if it exists) or step by step instructions to a

proven solution

?

Thanks in advance
[Android Software/Hacking General [Developers Only]] mateorod:
I can understand the frustration here, There is some information about this problem here, but perhaps buried in the thread. There aren't that many people left who are trying to patch CM7 for pdroid.

First, let me tell you that you can reflash your original rom over any update.zip. If the restore fails, that would have brought your setup back. I guess that doesn't help you now, and I am sorry for that.

You have provided me with a clue to the problem, maybe.

Here is what I now believe the issue to be: At some point (and I do not exactly know when) something has changed with the CM7 install process and the update.zip is not installing correctly anymore. That must be the problem, since the patching is going through fine, and yet the restore doesn't work. That is something I didn't know until you posted.

If you could try something for me, I think it might work.

Make a

copy

of your rom, and then replace the services,jar, framework.jar and core.jar with the ones inside the update.zip created by the auto-patcher. Then flash the entire rom with those files replaced.

Keep the original (just like you downloaded it originally) available as well, so you can flash it if this process doesn't work.

Let me know what happens. If you have access to adb a logcat would be helpful as well.

I believe the problem to be related to the updating process. This may provide a solution for you as well as a clue to us.

Update: That should for work you. Please let me know if you try it.

Update2: Okay, I have put in a fix that hopefully resolves the issue. If you are using the Windows GUI, you can sync to Auto-Patcher 2.4.1 and try that. If not you will have to wait until I put out an update tonight. It will essentially do exactly what I described above, so you can try that as well.

Please note, that patching for V6 won't do anything, as there are no V6 patches needed for gingerbread.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.4.2 has been pushed to ApG and should be available on our download page imminently.

As always, if it is already working for you as is, no rush to update,

Improvements include:

Minimum Android version check;

The script will now display an error if you attempt to patch 4.1.1 for pd2.0, or v6supercharger for gingerbread, for instance

Evervolv support for pd2.0 1.5.1 (Thanks to maintainer poncik!)

Added device-specific scripts

In the first use, adding support for Nook Color (encore) sdcard installs

Other uses may suggest themselves

Fix for patching CM7

This has plagued us, in one form or another, since the day we released this second project. But I think we have it fixed.

The fixes for several of these things involved some jimmying with the edify scripting of the original updater-scripts. Almost none of you that use this program should be affected by this. But that is the funny thing about passing several thousand instructions to a computer at once, things slip through.

As for the CM7 patching, we used the original PDroid-patcher to patch for Gingerbread for months. But on the first day of release, 7.2 final broke our patches, and it has been a serious struggle ever since (take a look at our changelog and you'll CM7 all over the place). I think I have it licked, but I do not have a device to test it on.

So let me know if this breaks something weird for you, okay? Remember, in the very worst cases, the only thing needed to restore your rom to how it was before you used the auto-patcher is to reflash the original rom.

No wiping of anything except caches is EVER necessary. Ask for help if you need it.
[Android Software/Hacking General [Developers Only]] alen1901:
Any news about implementation of evilisto mods? :)
[Android Software/Hacking General [Developers Only]] scutworker:
More Evervolv woe

OK, I've tried the latest Evervolv patch and I have a problem of not having any mobile phone signal (wifi works though).

I always use the autopatcher and when the last patch was created it worked fine except that apps that start on boot didn't start up.

Now I'm using version 1.51 of the app and the patch and apps all start on boot, but the mobile phone signal never connects. Normally I am connected to EE (Everything Everywhere, the UK mobile phone operator) but now it shows as 'Unknown:0',

I've tried deleting the privacy folders and rebooting, but it's always the same. It's also the same if the patch is installed, but not the pdroid app.

One thing: I do use an app called Call Master which does intercept calls but it has full permissions in Pdroid.

I'm using this Evervolv rom on an HTC Desire: http://xdaforums.com/showthread.php?t=1766550

I've attached two logcats, the first is the full logcat from boot up, the second is the same but filtered for errors only.

The output log of The AutoPatcher seems to be OK, but I've posted it here:

http://codepad.org/CGlZ3Dfm

I've taken a Nandroid of when it wasn't working, so if you need any other files posted here to diagnose the problem, then let me know.

Thanks for any help you can provide and your continual work on this project.
[Android Software/Hacking General [Developers Only]] mateorod:
I sent evilisto a PM about it a while back, but that was it. But lots of people don't use their message box. I think I will make a proof-of-concept for one of them and see how it goes. If it works I will post it in one of his threads and see what he thinks.

Thanks for reminding me, I sent the pm and then forgot about it...

This is an excellent error report. However, I think you should bring this to the PDroid 2.0 thread. I know he had a fix for some Boot receiver issues, maybe there are still a couple problems. But your patching looks okay to me. I would post the same info you posted here, over there.

Thanks for the well put-together info!
[Android Software/Hacking General [Developers Only]] scutworker:
Thanks! I've posted it here
[Android Software/Hacking General [Developers Only]] alen1901:
He is busy, and not here regulary, but he wouldnt mind if you implement that, im sure.
[Android Software/Hacking General [Developers Only]] drich2020:
Not done yet

Thank you for your prompt assistance. Now, cm7.2 patches but phone hangs on boot. The good thing is that the restore file works ok. Please look at my logfile.
[Android Software/Hacking General [Developers Only]] RuffBuster:
I'm trying to patch PDroid to a jellybean ROM which is 4.1.2 CNA based. I've tried using all the options provided but it keeps failing. I have provided a log using the CM option. Cheers!
[Android Software/Hacking General [Developers Only]] mateorod:
Hmm. Okay, well, if the restore works, then we have solved at least one major problem. Which is good, I had to institute a entirely new method to create the updater-script.

Did you ever try just dropping the jar files in the update zip into an entire copy of your rom and then flashing that? That tell us more. A logcat of the install, if you have ADB would also be helpful.

We were able to patch cm7 for quite some time. But I didn't find out it had broken until it was borken for awhile, so it has been difficult to track down. I am willing to keep looking at it if you are willing to report.

I can tell by your logfile that the ROM is aosp based. Would you attach the logfile from a run with aosp, please?

I also see a bug in the error display I can fix. You have also given me an idea for future error-catching of this issue, so thanks.

Edit: As I was looking more closely, I think I see what is happening here. The same thing that is happening everywhere. This is a CM-based rom that, for some inexplicable reason, has decided not to merge our commit.

You would think that people managing forks, who obviously take almost everything from CM, would merge things they don't understand, relying on their betters for the hows and whys. Instead, they tend to leave bunches of technical merges on the sidelines, opting to theme Nav-bars and whatnot. Frustrating.

I made an mistake with a symlink for Evervolv, so I need to put out an update anyway. Let me think about the best way to handle it, and I will put a solution in 2.4.5
[Android Software/Hacking General [Developers Only]] Uzephi:
I tried patching the new pdroid 2.0 with Pons' CM10 port for the ADR6300 (OG Incredible) paste bin follows, then a link to the rom. original pdroid patches fine though.

pastebin here

ROM here, thread here

edit: anything else you need, I can respond around Tuesday after I am done moving.
[Android Software/Hacking General [Developers Only]] mateorod:
I have actually just fixed a (very small) bug that displays the pertinent error message in a very confusing manner. it should look like this:

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

Try it again. It happens relatively infrequently (maybe 1% of the time or less) but is due to the smali binaries. I have forked the current code and am looking at it, but it is pretty intense stuff, far above my level. JesusFreke ended up getting cherry-picked by Google not long after these originally came out, if that gives you any idea.

Pull down 2.4.5 and try it again...at worst you will get the proper error message, although I bet it just works this run.

I also pushed a fix for you-- your post inspired the fix for the first guy.

Good luck, let me know if it works for y'all.
[Android Software/Hacking General [Developers Only]] mateorod:
Firstly, you are very correct that the restore isn't working. I can at the minimum look to fix that ASAP. Let me use this as an opportunity to remind people that for ANY auto-patcher operation, your rom and set ups are 100% recoverable and savable.

Simply reflash the original rom. Since we ONLY work with framework changes, it is easy to recover, since every rom necessarily comes with all the framework included.

And I am sorry for the delay as well, WJThomas. I got kinda caught up. It looks like this mod, written by pastime1971, was made with the Android 4.1 internal sdcard naming conventions in mind. As in, internal storage is no longer referred to (at least in Nexus and Motorola and several other devices) as 'emmc'

Instead, they use the sdcard0 for internal and sdcard1 for removable sdcards. I have actually seen this used (at least the sdcard) in the Nooks, although I feel like it may have switched back. That is why your build.prop is identical still, the awk operation is looking for sdcard0, and then not finding it.

I can possibly add a fix for this, but it may take a little bit. I have added a bunch of Nook specific stuff to the script already, but there is a bunch of stuff yet to do.

Let me think about some options, and thanks for cluing me into the problem with the restores, I will get that fixed ASAP.
[Android Software/Hacking General [Developers Only]] Uzephi:
Worked like a charm the first time after the fix.
[Android Software/Hacking General [Developers Only]] karamelos:
Hi Pd2.0 work on last

But (damn an error :p ) ,

&
[Android Software/Hacking General [Developers Only]] Revionion:
Hi, i tried to make a patch of 'Aurora ICS' by dzo and it failed. So that means i cannot use proid on Aurora? :s
[Android Software/Hacking General [Developers Only]] RuffBuster:
Thank you. The changes you made worked for me, am now running PDroid2. I did get a "missing line something something" in the compile window at the very end after where it displays the patches made, but it didn't look like an error and the patches were made so I ignored and flashed anyway and all seems to be good. Thanks again for your speedy effort!
[Android Software/Hacking General [Developers Only]] nsmart:
Old pdroid_patcher up to version 0.45 worked fine for me with ubuntu linux.

Since version 0.50 and also with new auto_patcher I get the following error (see attached log file for details):

patches/pdroid/cm9/20120506/core.patch

patches/pdroid/cm9/latest

tar: patches/pdroid/cm9/latest: Kann keine symbolische VerknÃ¼pfung zu â€žâ€ž20120626â€œâ€œ anlegen: Das Dateisystem ist nur lesbar

in english: "cannot create symbolic link, file system is readonly"

As stated above everything was working fine up to pdroid_patcher v.045.

Any ideas ? I am using ubuntu in a virtualbox-vm on Windows.

Edit:

Seems to be a problem caused by virtualbox. I tried the cygwin-method from within windows and it was working perfectly fine !
[Android Software/Hacking General [Developers Only]] kobik77:
This is not how you should that, you should avoid copy Java or any other binaries to System32.

Please paste the result of

echo $PATH

How to edit PATH variable

Windows 7

Select Computer from the Start menu

Choose System Properties from the context menu

Click Advanced system settings > Advanced tab

Click on Environment Variables, under System Variables, find PATH, and click on it.

In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.

Reopen Cygwin Terminal window, and run your java code.

Windows XP

Start -> Control Panel -> System -> Advanced

Click on Environment Variables, under System Variables, find PATH, and click on it.

In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.

Close the window.

Reopen Cygwin Terminal window, and run your java code.

Windows Vista

Right click My Computer icon

Choose Properties from the context menu

Click Advanced tab (Advanced system settings link in Vista)

In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.

Reopen Cygwin Terminal window, and run your java code.
[Android Software/Hacking General [Developers Only]] anomalya:
Thank you for this. Followed exactly as you've written and Cygwin is now able to extract and decompile and so forth.

But when it gets to creating the patch, I get this error: "failed framework.patch"

I've tried different combinations of mods and patchdates with no luck.

Maybe this particular ROM is really just unsupported as it said in the terminal.

In any case, the debug log is here, if anyone is willing.

SIDE NOTE: I noticed in Kobik's post, the path: "C:\Program File\Java\jdk1.7.0_02\bin" is missing the letter, "s."

It might be of relevance to others who might overlook it when they copy & paste.
[Android Software/Hacking General [Developers Only]] kobik77:
Thanks for pointing out the typo, I'll fix that now :good:
[Android Software/Hacking General [Developers Only]] mateorod:
Something is wrong with the XDA servers right now. I keep getting the same 404 not found message as has been happening with the latest version of the Auto-Patcher and I cannot see your log. Would you link to it instead?

I added a link to this on the OP. You have been a fantastic resource for our windows users.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
If this question is nonsense, I don't have any intention of it being so. I have the latest patcher for Linux and running the command "./auto_patcher" .. gives a permission denied. I do have jdk installed and I am not sure how to fix my 'problem'. I am obviously not doing something right.
[Android Software/Hacking General [Developers Only]] Trainer_H:
i use the TiramiSlim ROM http://xdaforums.com/showthread.php?t=1664049&page=143

Which command shall i use?

I try ./auto_patcher TiramiSlim_Final_V_1.0.zip pdroid,v6supercharger but i got some error message.
[Android Software/Hacking General [Developers Only]] anomalya:
Not claiming to be an expert here but I got the same error as you recently, so here's my take:

Firstly, take out MODS in your initial command line and specify it with pdroid or v6supercharger (or both separated only by a comma, no space). Then specify ROM type and patchdate (if it fails the first try).

It'd make more sense if you refer back to the OP for proper formatting.

But that's only half the battle...:D
[Android Software/Hacking General [Developers Only]] Dumhed:
Thanks. I took out MODS and added pdroid (which is what I'm trying to patch for). But alas, same errors. I'm not sure I understand what patchdate to write in. Maybe my problem is the rom that I'm using?

When I try i add "pdroid" to the command, the error says:

error: failed extracting system/framework/framework.jar system/framework/core.jar system/framework/services.jar from /cygdrive/c/ap/Razr-EclipseICS-v1.1.zip
[Android Software/Hacking General [Developers Only]] pastime1971:
it means that your rom is odexed, and patching only works for deodexed rom.

see http://xdaforums.com/showthread.php?t=1600805 for more information, but i've never done it before, so i am not sure about deodexing an odexed rom. :(