yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
No, it looks like you have a slightly non-standard build.prop for that device, which is not all that uncommon. The Nook Color is another that does not have the CM version in a standard format. It never mattered before, but now that they release Final builds with old code, I had to initiate a workaround for all the users who want the 10.1.2 builds, or what have you.

Basically, there is a hack in place to make using the autopatcher on Final builds take no thinking, but the consequence has been making up for all sorts of little things like this. In the Nook's case, there is a popular sdcard install script that requires the build.prop to be in this non-standard format. There is perhaps a similar reason for this S2. But either way, it is irritating and really something that should be handled in vendor/cm if you ask me.

Enough whinging, huh? I fixed it for you, it will work as you are accustomed to again.

Also fixed a couple other little bugs, thanks to [MENTION=5357068]gcydtmkq[/MENTION] for sending one (and the fix) in.
[Android Software/Hacking General [Developers Only]] meviox:
Thank you for the answer.

I've just tried version 2.9.9272 but ended with the same error message.

Attached the current log file as well as the log file from the yesterday's patching operation (where the patch process has worked without problems)
[Android Software/Hacking General [Developers Only]] mateorod:
okay...I really thought I patched it, but maybe all I did was make sure that the correct patches were applying and exit. Could be the unlikely confluence of a bug in the autopatcher applying the wrong patches at the exact same time as upstream broke the patches (and on the same file as using old patches breaks???).

Could happen...SEAndroid does have changes in Settings.secure class. I will look at it and we will get new patches out there. I have checked the 0526 and 0626 patches and they both fail, so new patches are lkely needed.

'
[MENTION=4418789]Urinophoria[/MENTION], if you can build let me know....I will start on my machine late tonight if I don't hear from you. Thanks meviox.
[Android Software/Hacking General [Developers Only]] karamelos:
Same here for nexus 7 & n7000

Idem log
[Android Software/Hacking General [Developers Only]] Christoph21x:
Similar here
[Android Software/Hacking General [Developers Only]] mateorod:
New CM10.1 and CM10 patches are up on Autopatcherv2.9.93.

Other bugfixes included. Sorry, my time is short.
[Android Software/Hacking General [Developers Only]] bonanza123:
Thanks! is working now again for me.
[Android Software/Hacking General [Developers Only]] zurpher:
Problem running ApG

I have problems to get ApG 2.6.0.1 on Win7 working. I ran it as administrator in a non-Windows folder as advised here. It does not download Java and Cygwin though. I've downloaded both manually. How can I add it?
[Android Software/Hacking General [Developers Only]] Christoph21x:
Dear Mateorod

Both worked like a charm:

CM 10.1 Nightly on P3100 WITH SIM/Mms.apk and

CM 10.1 Nightly on P3110 WITHOUT SIM/Mms.apk - it reported clearly "can't compile... - not existent in your ROM"

Perfect - thank you!

And this despite you have no time..wow!

Greetz from Switzerland - Chris

---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------

Sometimes you have simply timeout problems.

try it again and again.

Here: NO admin launch required if you have full rights on directory and sub dirs...

GReetz - Chris

PS: Don't try to install the stand-alone download versions of cygwin into this dir - makes no sense, it will not recognize them... (but also will do no harm - just a waste of disk space) :)
[Android Software/Hacking General [Developers Only]] meviox:
Thanks a lot. The new patches work as intended. :good:
[Android Software/Hacking General [Developers Only]] samsungmario:
Can you tell me where to download the recent files? I don't see it in techerrata.com.
[Android Software/Hacking General [Developers Only]] mateorod:
It should be auto-updating. The only place I can think of that doesn't have auto-updating easily is Cygwin without using ApG. What is your environment? I can upload a new package, but I am trying to shake our dependence on those, for lots of reasons.

Could you submit a log from using the latest download on techerrata?
[Android Software/Hacking General [Developers Only]] samsungmario:
Thanks much Mateorod. I downloaded the patches. Trying to patch infected_ cm10.1 for sg2.

EDITED: I stopped using APG and just did a manual patching in Cygwin and patching was all good. But I am getting these lines on the log file:

### delete patch openpdroid/4.2/cm/20130719 ###

### jar patch openpdroid/4.2/cm/20130719 ###

... apply framework.patch ...

... apply preloaded.patch ...

patch unexpectedly ends in middle of line

GARBAGE=

GARBAGE=

... apply core.patch ...

patch unexpectedly ends in middle of line

GARBAGE=

GARBAGE=

... apply services.patch ...

... apply services-gps_fix.patch ...

patch unexpectedly ends in middle of line

GARBAGE= tmp/system/framework/services.jar.out/smali/com/android/server/am/BroadcastQueue.smali.orig

GARBAGE=

... apply telephony-common.patch ...

patch unexpectedly ends in middle of line

GARBAGE=

GARBAGE=

... apply Mms.apk.patch ...

patch unexpectedly ends in middle of line

GARBAGE=

GARBAGE=

### apk patch openpdroid/4.2/cm/20130719 ###

### img patch openpdroid/4.2/cm/20130719 ###

### text patch openpdroid/4.2/cm/20130719 ###

Anything I should be concerned about?
[Android Software/Hacking General [Developers Only]] mateorod:
Well, this is way outside of what I can help you with. I have never seen this error, and it looks to be related to your machine and Java. Did you recently update Java?

... decompile framework.jar ...
Execution protection violation
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x1474ab38, pid=3304, tid=4188
#
# JRE version: 7.0_06-b24
# Java VM: Java HotSpot(TM) Client VM (23.2-b09 mixed mode windows-x86 )
# Problematic frame:
# C 0x1474ab38
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\APG\ApGPackages\ap\tmp20130721085119\hs_err_pid3304.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#

https://www.google.com/search?q=a+f...69i62j69i64l3.3575j0&sourceid=chrome&ie=UTF-8

This was the results when I looked up the error. But it isn't a problem with my program, it is just ruinning into something larger. If you only use Java for ApG and auto-patcher, maybe just nuke the entire set-up and reinstall. Sometimes that is necessary for ApG, I don;t have the knowledge of ApG's inner-workings to better debug.

Sorry I can't help more, but that is some issue between Windows and Java, nothing I can do anything for.

Edit: I see a l;ot of mentions of driver interaction failure. perhaps you need to update your drivers? Sorry, WIndows is a total mystery to me, I don't use it.
[Android Software/Hacking General [Developers Only]] zurpher:
Hm. I tried a couple of times with no luck. I will try again tomorrow.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Hey sorry, I got into sidetrack mode last night and wasn't paying attention. I'm going to go through and check all of them, got PAC building right now, I know for sure that's broken.

Sorry about missing CM
[Android Software/Hacking General [Developers Only]] xFluffyx:
Galaxy Nexus CM10.1 still an error:

my log
[Android Software/Hacking General [Developers Only]] ContactFront:
Hi all

Trying to manually patch a CM10.1 using autopatcher version 2.9.9265 and Cygwin terminal on windows.

Got this error

error: failed android/app/ContextImpl$10.smali' in framework.jar cannot be remedied

Have attached log file. Any help would be greatly appreciated.

Thank you!
[Android Software/Hacking General [Developers Only]] Android-Andi:
try

./auto_patcher flinnycm101_saga_24test2.zip openpdroid cm 20130516
[Android Software/Hacking General [Developers Only]] ContactFront:
Hi thanks for your reply!

tried it but no joy:( still that same error
[Android Software/Hacking General [Developers Only]] Android-Andi:
Ok... maybe my fault :P same date as in the log...

try another date

./auto_patcher flinnycm101_saga_24test2.zip openpdroid cm 20130626

or

./auto_patcher flinnycm101_saga_24test2.zip openpdroid cm 20130719
[Android Software/Hacking General [Developers Only]] mateorod:
Android-andi's suggestion are actually the correct thing to do, but it looks like you have something else going on...there are patches missing in your version of the autopatcher. If you are using ApG, you can delete the autopatcher directory and start again...it sometimes needs to be reinstalled, for reasons unknown to me as I didn't write ApG.

I did download and test your rom, and it all patches except for the Mms.apk. What I would do, if you really want OpenPdroid on that rom, is to take an Mms.apk from a build from get.cm, and replace the one in your rom with the one from a CM10.1 nightly. Then run that through the autopatcher.

We support Official builds always, but some kangs and unofficial builds are somewhat trickier to work with.

That looks like the timestamp was just inside the date needed. Either download the nightly from 7/20 or later, or designate the patch date manually like android-andi showed above:

./auto_patcher ROM.zip openpdroid cm 20130719
[Android Software/Hacking General [Developers Only]] xFluffyx:
cm-10.1-20130721-NIGHTLY-maguro.zip:

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

i use: ApG.2.6.0.2
[Android Software/Hacking General [Developers Only]] mateorod:
I just patched cm-10.1-20130721-NIGHTLY-maguro.zip from get.cm with no problem. I am using autopatcherv2.9.931. Update inside of ApG.

If it still doesn't work when using autopatcherv2.9.931, then you must be suffering from a corrupted file or something. We see some sort of problem with ApG sometimes. Delete the autopatcher folder and try again, is all I can suggest.
[Android Software/Hacking General [Developers Only]] xFluffyx:
THX

i delete the autopatcher folder and it works fine!
[Android Software/Hacking General [Developers Only]] ContactFront:
Tried 0626. Had a different error msg

error: failed android/app/Activity.smali in framework.jar cannot be remedied

like mateorod said, probably something else is wrong as well....

---------- Post added at 08:08 PM ---------- Previous post was at 07:55 PM ----------

Thanks for replying! :)

No I wasn't using ApG. I set up java and cygwin manually on my pc and downloaded autopatcher from http://techerrata.com/browse/mateorod/pastime1971

When you say "patches missing", do you mean it was a bad download? would it help if I try a different version of autopatcher, say 2.9.8x?

Just to double check, I can use Mms.apk from ANY of those nightly builds?

Thanks again for your help!
[Android Software/Hacking General [Developers Only]] mateorod:
Hmm...you are in the distinct minority sir! I don't see your set up very often. For ApG users (and by assumption all Cygwin users) I set the auto-update to off by default, since ApG has a rudimentary (and well-working) update system already. In your cygwin folder, you should find a .config file. There is an AUTO_UPDATE variable. You need to set that to true and install git (easily done by rerunning the Cygwin.exe again, and selecting git, it will only install the new package) and see if it updates.

I did what I suggested to you and checked moving the Mms.apk from a CM nightly (sat i9100 or something that is a phone and has an Mms.apk). Your rom then patches to completion with ./auto_patcher flinny.zip openpdroid. No need to manually select date. If you have trouble after the autopatcher updates, delete your autopatcher directory and redownload.

So to recap:

Install Git in Cygwin

Change AUTO_UPDATE to true in .config

Move Mms.apk into your rom

./auto_patcher flinny.zip openpdroid

If it fails, delete, redownload and retry one more time. You will have to run the autopatcher at least once before the .config file gets made.

If this still fails, let me know and I will get the update zip to you, okay?

I know this is a bit of a hassle, my intentions with all of this is to make it as easy on as many people as possible...every once in awhile that causes a couple extra steps for someone.

Good luck!
[Android Software/Hacking General [Developers Only]] ContactFront:
Thanks for writing me these detailed instructions!

I searched "git" files in cygwin setup and installed everything under "Devel". Is this good enough or there's something else I missed.

I noticed that the auto_update value in the existing .config file in my folder, generated by those previous runs, was already set to True, like this

#!/bin/bash

#Config for Auto-Patcher

AUTO_UPDATE=true

# For potential use in the test suite
PRODUCTION=true

I deleted all the autopatcher files, tried all over again, still had error, and noticed that once the .config file was generated, the value was true already.

Is there any command I can type into the terminal to get everything updated?

It's almost 12am where i'm now. so i'll call it a day and look into this more carefully tomorrow. It's no hassle for me at all :p I patched the CM10 i'm using atm without any incident a couple of months ago. Now i just want to get to the bottom of this lol.Obviously I can't always ask other ppl to patch my rom for me. I would've used ApG if I could but it doesn't seem to connect at all, probably because of the censored internet in my country..

Thanks so much for your help and I'll report back if there's any progress.

Good day:D
[Android Software/Hacking General [Developers Only]] mateorod:
Shoot! I forgot how I actually wrote that part! For Cygwin testers, it is hard-coded into the script. That way I can enable it in the Cygwin user's environment without asking folks to muck abut with .config files and the like. Around line 1163, just comment a line

AUTO_UPDATE=false # CYGWIN AUTO_UPDATE TESTERS COMMENT THIS LINE HERE!

change to this

# AUTO_UPDATE=false # CYGWIN AUTO_UPDATE TESTERS COMMENT THIS LINE HERE!

Then run the script. If it doesn't work, please upload your log and we will fix it! The auto update feature has had almost no testing in Cygwin (although I just got a minor bugfix sent to me I am going to look at) but I am pretty sure we can get it fixed. I will check the new bug out today and then look for your updated attempt tomorrow. Thanks for being willing to check this out for us!
[Android Software/Hacking General [Developers Only]] Christoph21x:
THANKS!

Worked perfectly here on Samsung p3100 (WITH SIM) and p3110 (WITHOUT SIM) latest CM nightly as per 2013-07-22 (before patch of 2013-07-20 wasn't successful)

Thanks a lot & kind greetings from Switzerland - Chris
[Android Software/Hacking General [Developers Only]] Urinophoria:
Checking it out, I'll get back to you as soon as I've done my sniffing

Edit: ok, I tried on my machine using the linux auto-patcher and this ROM: http://xdaforums.com/showthread.php?t=2265417 which I'm assuming is the one you were using? Got the same failure message on my machine, but a clean compile of the official PA went through just fine.

[MENTION=4342828]mateorod[/MENTION] it needs wiser heads than mine, lol. But it looks like AP is geeking out on applying the services patch?
[Android Software/Hacking General [Developers Only]] mateorod:
Well, as we have talked about provisional copying, remember ServerThread is one of the core Android files...this cannot be resolved with any sort of trickery.

PA is a difficult case, because they have purposefully flooded the land with a multitude of forks and unofficial builds. Even in the PA github, they have branches jellybean and jellybean legacy, which are quite different from each other. The jellybean branch is based on AOSP, while the jellybean-legacy is for non-Nexus devices and has much more CyanogenMod in it. Not to mention the fact that they are very picky about which devices get Official builds, yet almost every device now has a PA build. That is a hugely divergent ancestry, and really impacts our work negatively.

My bet is that [MENTION=4418789]Urinophoria[/MENTION] is testing on a Nexus build, and that the users (one I know for sure is Samsung i9100) are using non-Nexus devices, i.e. the difference between Jellybean and Jellybean-legacy branches. [MENTION=4418789]Urinophoria[/MENTION], are you up to build a target from the user logs? I the device is in the log, you can see it at the DID= line.

You can do this with these commands (you most likely know all this already)

. build./envsetup.sh
lunch

The lunch menu brings up the list of available targets, if the device from the log is not an option, just pick a non-nexus device, my advice would be i9100. Then, ./rom-build.sh i9100 should do it.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Yep gimme about 20 minutes and I'll take a run at it. I know it's no joy in 9300 but I haven't tried 9100

Strangely they both show up in the lunch menu, but I've never been able to get the i9300 to work. I've even tried completely deleting the entire local repo and starting from scratch and the i9300 wouldn't fire.

And you're right, I was building for mako, lol. It builds so easy for all the ROMs I'm thinking about getting one. If the damn things had an SD slot I would have stopped THINKING about it a long time ago.
[Android Software/Hacking General [Developers Only]] mateorod:
[MENTION=4956815]ContactFront[/MENTION]

I am interested in hearing what happens when you comment the line I wrote about above, but if the auto-updater does not work (I use ping to test for network access...a user [MENTION=5357068]gcydtmkq[/MENTION] sent in a fix b/c my use of ping does not work on Cygwin. That may stop the auto-updater from working) then I wanted to get in front of that.

I applied gcydtmkq's fix for ping and updated the auto-patcher. I also uploaded a current package to our download page. That should not only work for your rom (as long as you slide in an Mms.apk) but should have the updater working for the future,

Thanks so much for your time, users like you guys is what makes this project go.
[Android Software/Hacking General [Developers Only]] ContactFront:
I commented line 1163 as instructed, then this message appeared on the terminal and the process failed at the end.

Check for update failed, probably because of no internet access.
The autopatcher will continue with current local version: v2.9.9265

I then downloaded the new version but still failed to patch the rom. Tried twice with Mms.apk from a i9000 and a i9300 builds.

Just when I thought I could nail it..#facepalm LOL

I've attached both log files for you. I'm so sorry this is still dragging on.

Thanks so much for your time and patience!

EDIT: I tried with a different CM10.1 rom, seems like same error occurd again. Log uploaded as well.
[Android Software/Hacking General [Developers Only]] IUnga:
I have a error with build v115 from [MENTION=2332422]temasek[/MENTION]

Error log - http://codepad.org/xyp6BKq5

Thanks
[Android Software/Hacking General [Developers Only]] meviox:
Please, please, do not put the logs into a spoiler (or whatever), but rather add the log file as an attachment. It is very annoying when you have to scroll through the entire log in Tapatalk. At least the new Tapatalk version cannot handle the spoiler

BBcode.
[Android Software/Hacking General [Developers Only]] bbernardini:
I can't even begin to thank the team enough for this. I've been trying off and on to use the V6 Supercharger on various devices for over two years now, but was never able to get any higher than 50% supercharged. Last night, I happened on this thread while trying the Supercharger script again, and I've now successfully reached 100% on two devices, and plan to work on a third tonight.

Once again, THANK YOU!
[Android Software/Hacking General [Developers Only]] niteh@wk:
For those still getting errors patching OpenPDroid on AOKP Milestone 2, I found a way to successfully patch Milestone 2. If you still have the prior good update patch, extract the Mms.apk from that patch and replace the Mms.apk in Milestone 2 with it, then run APG to patch. Easiest and quickest to replace the Mms.apk is use Beyond Compare, compare Milestone 2 zip file with the update patch zip file, then move Mms.apk from the patch zip to Milestone 2.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Yup, just saw it. Sorry, I forgot about how lacking Tapatalk still is -.- my bad!

Via Tapatalk 4 BETA, that, surprisingly, is free.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, there are a couple of things here. Firstly, we don;t swear that we support that rom. It looks like a slight kang of CM10.1, which means we may support it, but that is only by happenstance. Our supported roms list is on the OP, anything else is just a bonus.

Okay, disclaimer is out of the way...let's see what we can do. For some reason, the patcher is not applying the patch that is the best match. You can try going to manual patching and entering ./auto_patcher ROMSNAME.zip openpdroid cm 20130719. If that says it cannot find those patches then you have to delete your autopatcher folder and redownload the package. There has been string of corrupted packages in ApG. I don;t have better debugging info than that, but I will say that redownloading it seems to work for most people.

You could also try a rom that is on our supported list, if that doesn't patch then it is almost certainly time to redownload.

Okay, i will make a new Mms.apk.patch for AOKP overnight tonight.

Okay...where did you download that package from? If you downloaded a zip from github (which I hope is what happened) then we have a known issue where github messes with the line ending and has processed them in a way that is non-compatible with Windows. If you are using our techerrata upload, then I have a different problem. I just today got a pm related to this from a user getting similar results. These current failures are for sure related to the line-endings, I hope that the cause is what I am guessing. The different line endings is one of the major differences between the major desktop OSs. It seems small, but is has just been going on too long for anyone to contemplate unifying the standard.

I am attaching the update.zip I made for the flinny rom so you can have OpenPDroid protection while we debug the issue.

Ha! Been awhile since I heard from a V6 user. I assure you, this is the easiest extant way to do this. Zep's process works, but jeez it must be super tedious to bang out 50+ edits using sed. I can't imagine.
[Android Software/Hacking General [Developers Only]] mateorod:
Autopatcherv2.9.935

is up on github and available through your favorite update method (except for our download page. I have not uploaded it there as I am trying to see how well our updaters are working for people....let me know if you are being forced to use an old version and we WILL fix it for you.)

New AOKP patches for Milestone 2

New PA patches for non-Nexus PA builds(jellybean-legacy branch)

Some Cygwin-related formatting and utility bugfixes, sent by [MENTION=5357068]gcydtmkq[/MENTION]

I think that gets us current. I am unaware of any autopatcher related needs...if something I claim we support is not working, please let us know. We have a real good team right now (Thanks [MENTION=4418789]Urinophoria[/MENTION]phoria and [MENTION=1449163]Caldair[/MENTION]!). There is a slight mystery with some non_apG cygwin users and the line endings, I am hopeful that an idea sent in by gcydtmkq will make the difference.

I am finally beginning to work on the big step that will finish off 3.0.0. There are some conceptual challenges, and I am trying to keep an eye on AOSP upstream as well. Thanks for all the great feedback, guys.