yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks, i am definitely going to check it out. I am always on the lookout for contributions.

edit: This is a pretty impressive package. It will take me a minute to tinker with it, but thanks for bringing it by. I will be in touch.
[Android Software/Hacking General [Developers Only]] a3955269:
fwiw, I've just tried applying my patches to a few other wanam deodexed 4.0.4 builds. All patches were applied successfully. I didn't flash and test the ROMs though...

I think there might be a good chance they'll work on other S2 stock deodexed ROMs, maybe even 4.0.x as well.

btw, one noteworthy change was that I had to match ContextImpl$xx.

e.g autopatcher had a patch for a new file ContextImpl$34 but that already existed so I checked baksmali-ed tree for the next free available 'index' which was ContextImpl$40. That change i had to reflect in framework_11_ContextImpl.patch ( search/replace ContextImpl$34 -> ContextImpl$40).

Plus some changes had to be applied in different ContextImpl$xx files, e. g. framework_7_ContextImpl$18.patch -> framework_7_ContextImpl$20.patch
[Android Software/Hacking General [Developers Only]] ganggreen30:
Why does my Norton remove the autopatcher when I download it?

Sent from my VM670 using Xparent Pink Tapatalk 2
[Android Software/Hacking General [Developers Only]] scutworker:
Because Norton is ****e.

If you do a search of this thread you'll see that a lot of anti-virus and anti-malware software thinks that The Autopatcher is a virus or some kind of evil-ware. Just suspend Norton while you install it and then run it to create your patch and you will be done. Of course this means you have to trust the Autopatcher but many of us on this thread do....
[Android Software/Hacking General [Developers Only]] ganggreen30:
Appreciate the reply but I truly have to say this about Norton 360 I have both Linux and windows 7 dualboot Norton 360 has been quite amazing trust me when I say this I've put it through hell on malware laden sites its held up its part that's not to say I dont use malwarebytes and emet 3.0 and attack surface analyzer and Firefox with noscript etc.etc... on top of it.

Sent from my VM670 using Xparent Pink Tapatalk 2
[Android Software/Hacking General [Developers Only]] c_shekhar:
Hmmm Intresting....
[Android Software/Hacking General [Developers Only]] mateorod:
I suppose that could be automated, although it would take some thinking. I am going to be swamped up through the weekend, but I will be looking at this thoroughly. I can already tell it is going to require me to learn some new things, which has a value all it's own. We can add deodexing to the project, I know. I haven't done so before because our patches wouldn't work with the roms that are odexed. But I am curious as to how your patches would fare. I do this by hand and see.

Well, I think you mean ApG, not the auto-patcher itself. The script itself won't have any troubles.

Let me take a stab at this; this is my understanding as a non-Windows user and total noob when it comes to anti-virus.

My understanding is that the anti-virus software is alerted by programs that aren't signed with Microsoft certificates. Which developers can get, but they cost money and since someone like Kobik is distributing a free program that he created as an intellectual challenge, there is no reason for him to spend money for this purpose. I believe they are pretty expensive, but to ask him to spend any amount of money would be unreasonable. ApG and the autopatcher only operate on the child directories (with one exception; apktool installs framework files to the rootdir, that is a default behavior of that tool, but it is heavily vetted tool with publicly available source).

The auto-patcher script is open-source and available here. I recognize that not everyone will be able to follow the scripting, but that does mean that many people have looked at the code and can see nothing malicious is done, and at this moment, no network access is used. Soon we will transition to a web-hosted patch repo, but for now no information is transferred through the use of this program.

:D
[Android Software/Hacking General [Developers Only]] kobik77:
Because it's crap.

No, Seriously!

I really though that after dropping upx compression this problem was gone.

Personally, I'm using Microsoft Essentials and it doesn't think ApG is a malicious software.

Besides, ApG doesn't require elevated permissions so it can't do anything serious to your PC in any way.

And one more thing, if you don't trust software that you download from the net try running it under sandboxie so you could see inside a sandbox exactly what changes it does to your PC.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
nah problem never went away, I just have to make sure i disable my norton stuff before I run ApG or Apg just disappears because norton eradicates it immediately. It's like and extra 3 mouse clicks so it never really bothered me.
[Android Software/Hacking General [Developers Only]] zsunsun:
Hi,

I used autopatcher for windows and got a great result.

However the autopatcher installed an outdated version of the Pdriod 2.0 patch (1.48) where most recent version is 1.51

Is there a way for me to manually update the patch version to most recent one?

Thanks
[Android Software/Hacking General [Developers Only]] mateorod:
Could you post the log please? There is only a VERY specific circumstance where you should get the older 1.48 patch, and as time goes by that circumstance becomes less and less likely.

When we updated to 1.5.1, I wanted to keep the 1.48 patches available, in case some people preferred them or 1.51 proved to be less portable. So I kept the original patches in there. But if you use our build query, it should only automatically select for people patching a rom built on 10/16 exactly.

If that was not the case, then perhaps you have revealed a bug. The log is in the out folder, and ApG has an option to automatically upload it.
[Android Software/Hacking General [Developers Only]] zsunsun:
Here is the log file "ApG.log"

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 <Sun@MagNaNux-88M2.(none)> not allowed

Cannot save the current index state

Already up-to-date.

The Auto-Patcher v2.4.7

The Auto-Patcher v2.4.7

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 20121030 [optional]

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

The Auto-Patcher v2.4.7

The Auto-Patcher v2.4.7

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 20121030 [optional]

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

Meanwhile I'll try to make sure I don't have firewall or anything else is causing trouble.

Thanks

EDIT:

This appears when I click 'submit log'

http://codepad.org/RsSXxSjM
[Android Software/Hacking General [Developers Only]] jader13254:
Sorry but...

You made my day! :D:cool:
[Android Software/Hacking General [Developers Only]] ganggreen30:
This one only works on ics and above right?

Sent from my VM670 using Xparent Pink Tapatalk 2
[Android Software/Hacking General [Developers Only]] mateorod:
You are running the latest version, so no network issues are behind this.

Could you give me a link to your rom? I couldn't find it by searching the name. But something funny is going on here, with my tests with the command line version of the patcher, the correct patches are being chosen.

Just don't use the 10/16 patches. I may end up taking them out at some point, but for now, just choose the 10/17 patches and you will get the 1.51 version. On the command-line, what you need looks like this:

./auto_patcher ROM_SHOOTER.zip pd2.0 cm 20121017

You will have to see how that is done with ApG. I do not see why it is picking earlier patches for your rom built on 20121111. Please send me a link so I can get to the bottom of this and fix it.

Depends what mod you want. We offer some mods for gingerbread, secure and insecure boot.img, pdroid and others.

If you are using the command line, the script will tell you if your rom is too old to use any particular mod.
[Android Software/Hacking General [Developers Only]] zsunsun:
I did patch again with command given by you and here's log

http://codepad.org/Hzpf14Ws

I'll report back once I test this out

Thanks!

EDIT

Weird, it still says it's 1.48 and my phone's started to bootloop :(
[Android Software/Hacking General [Developers Only]] kobik77:
First, there is clearly a problem with syncing with GitHub as it requires an email address.

Second, something isn't right in this log as it seems that auto patcher doesn't like the input it gets.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] Gootch@GMX.de:
On Screen Buttons not visible

Hi,

I've now attached the log and two screenshots.

In portrait mode the buttons are available but the properties button (the three dots) is also not visible.

In landscape mode no buttons are available.

The function of the buttons is available if I touch the place where they should be.

I used the cm-10 stable maguro rom with the autopatcher 2.4.7.

When I flash the restore.zip everything is fine with the buttons.

Anyone an idea?

/Gootch
[Android Software/Hacking General [Developers Only]] zsunsun:
You were right!

I assumed that since it's "autopatcher" and all made for windows, it would do everything fine.

I manually cloned git and then replaced 'ap' folder with newly cloned git then patched the ROM file in question. And everything worked as it should!

I'm glad that the problem is found.

Thanks to all.
[Android Software/Hacking General [Developers Only]] mateorod:
I haven't heard of this before, but let me look at it. I have a couple of things I can look at. I am going to look at the Official maguro rom from CM unless you tell me different.

Edit: Well, I remember one earlier report, but I think it was you, right? Anyway, I will check it out this afternoon.
[Android Software/Hacking General [Developers Only]] D-m-x:
Is there any ETA on when the Auto Patcher will Support patching Android 4.2 (for example Paranoid Android 2.99 for the Nexus 7). Would be great.
[Android Software/Hacking General [Developers Only]] mateorod:
No.

As far as I know, none of the build patches have been updated for 4.2 yet. I haven't had a chance to look at them myself. I know CollegeDev is working on new patches, but he hasn't said anything to me about them. If they are for Cyanogen source, like his earlier patches were, they are likely to not work for 10.1, whenever they are released (and by extension Aosp 4.2, PA 2.99+ etc.)

If they are indeed for 4.2, then we will be good when they hit.

We will probably update patches for roms when those patches come out, but since I haven't spoken to him I don;t know what they will be for. I will update the original PDroid patches at one point, I haven't seen how they apply on 4.2 yet.

Edit: PA 2.99 is still 4.12 and is supported by the auto-patcher. try it.
[Android Software/Hacking General [Developers Only]] jordcrk:
hello!

I'm trying to patch some note 2 roms.. but I always get the failed status after :(

revolution rom

http://codepad.org/ry1mkxrr

criskelo rom

http://codepad.org/N70gUxSm

and the same for aroma v7 ... I don't know what I'm missing

could be something wrong in the settings? :)

thanks in advance!
[Android Software/Hacking General [Developers Only]] beginnerteur:
Something else, kobik77, could you add a new feature to your ApG, so that the outputted names of the files include also the mod type? Now it's "cm-10-20121124-NIGHTLY-i9300-update", I would wish to have it like "cm-10-20121124-NIGHTLY-i9300-PDroid-update" and "cm-10-20121114-NIGHTLY-i9300-v6supercharger-restore" etc. Because now I often mistake the two (four) files.

It would be nice :good:, if you could add this. Thank you!
[Android Software/Hacking General [Developers Only]] a3955269:
Fixed a bug in framework_11_ContextImpl.patch.

Should work an all I9100 stock deodexed 4.0.4 ROMs, if not bad luck :P
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
I had this posted in the Nook Color PA thread, but felt I should post it here as well:
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry for the delay, I am working on this tonight.

Well, users do not need to use anything other than the four romtypes [pa, cm, aosp, and aokp]. So when you enter aosp-jb, the patcher is reading that wrong. I thought I had added an exception for that, though, so I will look at it. No guarantees, I don't know these roms, but try just aosp with them. And maybe try CM with the Criskelos (or whatever) one, that patch failure looks familiar.

It has been on the menu, and just needs to be tweaked to be able to accomodate users applying multiple mods. As is, the test version of this features inserts a space.

I have been busy (as warned) but am going to mess with this tonight. I will also add a deodexing function, and see where your stuff leads me. Edit: Although as I get ready to download some roms, there is no imminent plans to support system.imgs, unless I find some standard way of mounting the different types. I have barely messed with them myself, but it was a PITA to learn to do even by hand, and I understand it is different for each manufacturer.

Added a link to this on the OP, thanks Grayfox.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
WHOOOHOOOOO I made OP :D lol
[Android Software/Hacking General [Developers Only]] dirtyreturn:
http://codepad.org/t88G7nny http://xdaforums.com/showthread.php?t=1667418

unknown rom error -xenonHD gsm galaxy nexus

http://codepad.org/EWP9sbrX http://xdaforums.com/showthread.php?t=1801005

context..smali error

latest PA gets an unknown rom version type 4.2

any ideas?
[Android Software/Hacking General [Developers Only]] jordcrk:
thank you so much for your answer! :) I've tried all the options with all three roms, and I got the same error in all three cases. I'll be waiting for a solution, anyway, I'll be following this thread and I'll try all future versions of auto-patcher to see if it works finally.

by the way, if there is any user that is able to patch any galaxy note 2 rom.. please tell me! I'll be pleased to know what to do :)
[Android Software/Hacking General [Developers Only]] taihox:
Hello,i'm new here I've tried the autopatcher (on cygwin),I kept encountering "Failed to extract build.prop" from whichever ICS Bionic rom i tried to patch pdroid on though,are there any advice on this?
[Android Software/Hacking General [Developers Only]] mateorod:
We do not have build patches for 4.2. So no 4.2 support yet.

I don't know specifically, but I have yet to see a non-legacy device that we don't support in some manner. Do you have a CM10 rom, or a PA rom yet? The roms we have trouble with are the small distribution device=specific stuff and the the OEM skins (i.e. TouchWiz and Sense). Try one of the supported rom types.

Hmmm...do you have a deodexed rom or a system.img? At the moment we only support deodexed roms of the types listed on the OP. I am pretty sure IO have seen bionic users sucessfully patch here before.

Make sure your rom is in the same folder as the auto-patcher stuff, and post a log if you still are having trouble.

Expect an update sometime in the next day or two guys.
[Android Software/Hacking General [Developers Only]] topsign:
failed to patch
[Android Software/Hacking General [Developers Only]] dirtyreturn:
@anybody, or mateorod. Ran four roms through ApG [liquid,CNA,EOS,JBSourcery] I had started off with aosp-mod for all four. All failed with a contextImp%20.smali error {or some similar wording}. Ran all four again with the cm patches - out of the four- liquid and CNA were patched successfully -brought up the method cap ;;;rebuilding framework.jar. EOS and JBS had still failed. I'm pretty sure I had used aokp for one and nothing. Why is it that, atleast for me, that all roms seem to fail with the aosp-mod patches and only a few are compatible with cm patches. NO complaints , .. out of curiousity.
[Android Software/Hacking General [Developers Only]] mateorod:
Yep. doesn't look to be patchable at this point.

Drop some links to the roms you are trying...include the CM one and CNA at least. I will run them and see whats up over the course of the day.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
http://xdaforums.com/showthread.php?t=1767629 EOS, fail. aosp-mod +cm patches.

http://xdaforums.com/showthread.php?t=1965622 Liquid, pass + cm patches. fail, aosp-mod.

http://xdaforums.com/showthread.php?t=1839233 CNA, pass + cm patches. fail, aosp-mod.

http://xdaforums.com/showthread.php?t=1801005 JBS, fail. aosp-mod + cm patches.
[Android Software/Hacking General [Developers Only]] mateorod:
So far I am downloading EOS. But the JBS thread has no download link and following their links just sends me into a frustrating spiral of their own forums. And the CNA thread links to a long list of devices. Do you have some links to the actual roms so we don't chase our tails?

Also, you don't use aosp-mod anymore. That is only used internally. Just use aosp itself if you feel you have to overrule the build query. But the build query is pretty good, I don't think many roms will require any romtype anymore.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
http://www.facebook.com/l.php?u=http%3A%2F%2Fbit.ly%2FW9RWrI&h=MAQEhRx3dAQGCel2jMSHpebNvemoG1b8zisrpc-xAx6BZmg&s=1 ---Liquidsmooth

http://teamsourcery.com/ICSourcery/gnex/releases/JB/3.2/GSM/JBSourcery-GSM-V3.2.zip

http://goo.im/devs/codenamedroid/stable/GalaxyNexus-GSM/Codename-Android-3.8.0-GN-GSM.zip
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
The liquid smooth rom on my HTC thunderbolt is CM based, so isn't that true for all Liquid smooth ROMS?
[Android Software/Hacking General [Developers Only]] mateorod:
You are correct sir, thank you.

Okay, I think we have some sort of misunderstanding here, probably on my side...what are you asking, exactly?

I tested the roms and have come to the conclusions that I now understand is what you already posted. I thought you were saying that all of these roms fail to patch. What you are actually telling me is that a couple of them fail, but the others succeed?

I don't understand the question I guess. Liquid and CNA can be patched because they are based on Cyanogen. JBSourcery and EOS fail because they are not sufficiently similar to any of our supported rom types. They could be supported if someone wanted to build for them, but the user base hasn't warranted it, especially since we can support the generally best working and/or most popular roms for every device, AFAIK.
[Android Software/Hacking General [Developers Only]] @root@:
pdroid patch for the latest cm9 is not working :rolleyes:
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
so upgrade :D, jk could you post the log it gives you detailing why it failed?
[Android Software/Hacking General [Developers Only]] dirtyreturn:
You hit the nail on the head. Thanks for your response. I, on a personal level lack, I guess, the basic understanding of different rom types. The very first time I used pdroid was on sense and I have stuck with sense until i had picked up a gnex. I am generally not a frequent rom flasher and prefer privacy [pdroid] over anything else and figured to try out another rom so long as pdroid is there. So, forgive my ignorance and I appreciate your work. Hopefully you were not banging your head at all with my vague replies, or lack of an easier way to read it I guess.

AFAIK?
[Android Software/Hacking General [Developers Only]] mateorod:
+1 on the log, can't help you without it. I haven't heard about any merges in the Cyanogen repo that would break the patches...not that it isn't possible I guess.

Naaah. You are a long time user, I don't mind. Hopefully i answered your question. If not, feel free to ask more.

Edit: You asking what AFAIK means? It means I spend too much time on message boards. As Far As I Know. Just a douchy way of qualifying myself.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Ha! Awesome, an answer to some of the lingo.

mateorod, from your understanding since the EOS and JBS do not seem to be supported by the patcher and would have to have patches built manually[?] by a maintainer. Like, what kind of build do you think they are? The first sense phone i had used was a mt4g and that did not really involve the different rom types. Running linux on my laptop overheats it/ seems to lack wifi mostly. So I, for the most part stick with the nice point and click windows. ApG gives rom types as cm,aokp,aosp-jb,aosp-mod, and pa,ADD aosp-ever.. To the question of the day - are roms like the EOS or JBS based off of some other-wordly entity?.. Like the user ..fox.. --grayfoxmg1{will edit for proper credit} had mentioned that LiquidSmooth is CM based. What base do they use?

Quick copy/pasted from EOS on xda -EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
[Android Software/Hacking General [Developers Only]] mateorod:
Everything we patch is actually based on AOSP. AOSP is released by Google, and is what the manufacturer's like Samsung use as a base for Sense and so forth. Cyanogen is the main base for all the hardware that is not supported by AOSP. Google really only releases code for things like Nexus and Xoom and other flagship devices. The device trees and other hardware stuff for the other devices almost always comes from Cyanogen.

AOKP and ParanoidAndroid and so on, there has been a recent trend to move away from a CM base, and rebase on AOSP. So more and more custom roms that are popping up in the device forums are claiming AOSP as their base. But those roms still use the CM device trees. They tend to have their own framework 'forks' of AOSP, with their own personal additions.

When they change enough things from whatever base they choose (and for our purposes we have identified the four most popular main ROMTYPES, which are PA, AOKP, CM, and then the root base, AOSP) the patches we make for those types might fail. We can still patch the source code, just not already built roms.

The auto-patcher is used to port mods and functions to roms that have already been built. But these mods have always been available to anyone who compiles the rom from source. But realizing that most people do not have the time/knowledge/inclination to build roms and edit source code yet still want specific features (like PDroid etc.) the auto-patcher is now available.

Basically, without the auto-patcher, users were either forced to edit their own code, or rely on someone putting out a custom rom that integrated the desired feature. Periodically, someone might share a flashable zip with, say, the PDroid files needed for a specific device. But you were at the mercy of someone else to provide it for you, and if you already had something like the V6 Supercharger, flashing the new zip overwrites that mod. With the auto-patcher, you have the choice and ability to combine any source edits you want, without relying on anything or anyone else to do it for you.

If a dev writes an app, they are set, because there is a built-in distribution method in Google Play. For every other hack, we offer the auto-patcher. We just have to see if others see the potential I do...

Did you ask me about that or did I have some sort of seizure? Don't mind me, I can get carried away....hope there is some answers in there.