yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] abby_nitewolf:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Is this not compatible with jellybean?
[Android Software/Hacking General [Developers Only]] PnoT:
I'm in the same boat as Pappy because I want to integrate pdroid or pd2.0 into the CyanogenMod 10.1 Nightly Builds but I keep getting an error related to pdroid & pd2.0 not supporting 4.2.1+ (http://codepad.org/dyHOSzVH)

I'm surprised that there have been no builds with such a popular phone / ROM.

Confused at this point is an understatement so please correct me if I'm doing something wrong. :o
[Android Software/Hacking General [Developers Only]] Troj80:
Thanks.
[Android Software/Hacking General [Developers Only]] inchoate:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

I believe you need to use openpdroid.
[Android Software/Hacking General [Developers Only]] mateorod:
Ummm, it says 4.2.1 support in the title of the thread.

No, it is confusing. I have done what I can to make it easy, but the fact is it can be pretty hard to understand. Short version is that only 'openpdroid' is available for 4.2.1. Pdroid (the original) was being ported forward by me, but I stopped when my attention went to OpenPdroid. OpenPdroid came about as a fork of the PDroid2.0 patches, which didn't look like they were getting 4.2.1 support anytime soon.

Hopefully, as far as the patches as concerned, OpenPdroid will be the only patches going forward and can support either of the new PDroid permission management apps: Pdroid Manager or Pdroid2.0. Collegedev (with PDroid2.0) has been in contact so we are hopeful.

But for now, only OpenPdroid is supported in Auto-patcher. You can use the open source PDroid Manager app in Google play to manage the permissions. I know some people have used PDroid2.0 app, but I don't have any data on how well it may or may not work.
[Android Software/Hacking General [Developers Only]] PnoT:
I've flashed OpenPdroid after I wrote the initial post and using the Manager so things look to be working and thanks for the explanation!
[Android Software/Hacking General [Developers Only]] abby_nitewolf:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Oh, well i received an error that it's not compatible with it. But ill try again. Im using AgP auto patcher.
[Android Software/Hacking General [Developers Only]] abby_nitewolf:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Never mind, sorry. I just found out PDroid 2.0 isn't compatible with Jellybean.
[Android Software/Hacking General [Developers Only]] halop2k:
Paranoid Android 2.99 4.2.1 i9100

Hi i get this error if i try to patch the Paranoid Android 2.99 rom for i9100 from this Thread:

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

with ./auto_patcher rom.zip openpdroid pa

I think thats because this version is not the nexus pa version.

Please can anyone help me with that?

http://codepad.org/WI5DllUl

Thanks
[Android Software/Hacking General [Developers Only]] :
Can I get some help here:

http://codepad.org/EJmM1gdG
[Android Software/Hacking General [Developers Only]] baastien:
Hi mateorod

Well...

This feedback was about patching openpdroid for Samsung G Note N7000 and beerbong's [AOSPA 4.2.1] PARANOIDANDROID 2.99 betaNINE.9+ (Feb 5) | PIE, FOURTH BETA RELEASE.

Can't help for now about 4.2 and opendroid patch issue on Touchpad because no 4.2 AOSPA so far on this device.
[Android Software/Hacking General [Developers Only]] karamelos:
Hi @bastien How are you? (Oups rules: il est un forum qui ne dort jamais j'ai bien aimé :good: )

Did you try with 2.6.25 & @AuSSiELaMbChOpS tips ?

You are the dev try with source
[Android Software/Hacking General [Developers Only]] mateorod:
Oh, yeah that is the only mod that has not been updated. But OpenPDroid is a fork/expansion of PDroid2.0 and is open-source. It works for 4.2.1.

Here is a post from AussieLampChop that tells you what to do. I am working on a couple of ways to integrate those findings into the Auto-Patcher.

It may look difficult, but all you have to do is edit one word and zip it back up.

Nothing we can do here I don't think. The Auto-patcher is guessing that your rom is based on AOSP, but from the link to the rom in your sig, it looks like maybe it is a stock rom of some sort? If you know what rom it is based off of (Cyanogen or AOSP or AOKP for ICS) then you can indicate that. But if it is based off of a skinned rom (something based on a manufacturer's stock) then the Auto-Patcher does not support it.

I see that you are the dev of that rom, though. You can patch the source code with our build patches if you want. Look at the OP PDroid description...there is a link to pastime's thread and instructions.

Thanks, glad you responded. I was just trying to see what the commonality for this telephony-common patch error is (So far, all Samsung, if that means anything). I haven't found it in the source code. The official ParanoidAndroid manifest is just using an old fork of Cyanogen's frameworks/opt/telephony. My guess is that there are PA maintainers (not official roms) that are using more Cyanogen base than PA, and have a more recent version of telephony. I haven't investigated that guess too deeply yet.

This was something I have been worried about ever since PA closed their repos to switch to an AOSP base. Since they did not share their AOSP code with their open-source forks, those maintainers just continued to base their 4.2 code off of Cyanogen. Now PA official has released the AOSP-base, but I think that perhaps some maintainers have continued to use Cyanogen projects. In essence, this has resulted in a split of the ParanoidAndroid base. I was maintaining a fork for the Nook Color, some of the PA practices drive me up a tree. Great features, though.

There are some quick and dirty things I could do to include this fix, but it doesn't really solved the base problem. I need to find some practical method to fix this and have it stay fixed, if we update our patches I don't want to have to keep messing with this edit. I am working on it.
[Android Software/Hacking General [Developers Only]] baastien:
My poor understanding with this issue is that devs do not have all the codes and especially exynos chipset drivers to deal with AOSP. CM was obviously a little bit more comfortable with all this.

Take your time man it is already great ! The work around seems to work fine for now. You may just need to talk in your OP about AuSSiELaMbChOpS tip only for Samsung devices.

The longer threads are, the more courage does people have to read the entire OP's !

Hi karamelos,

So you well know that I particularly likes PA ROM which are now AOSP/AOSPA ROM even through as mateorod says its a kind of mess in their repos.

And I know that you are hanging up very often here !! :D

Yes I tried 2.6.25 & AuSSiELaMbChOpS tip.

And by the way, what's up with your site ? It seems to be off. I need some more fresh tips about my favourite distro !

See you later both of you.
[Android Software/Hacking General [Developers Only]] vvolfi:
Download aborted - virus-warning ?

Download-Links:

- d-h.st/users/kobik/?fld_id=5247#files

- goo.gl/7WXGV[/url]

Hi kobik77! First I wanna thank you for your hard work creating the auto-patcher - a really useful tool. In my opinon it's a very important thing to question the permissions that many apps are claiming for. Thinking that, I tried to download your ApG-Tool to patch my Stunner-ROM for PDroid-Usage.

But both download-sites caused a a virus-warning (Win32/DH{LgAgJTU}-Virus). I've the AVG Internet-Security 9.x installed and I update it regularely. Are you sure, the servers are clean or is my AVG mistaken? I'm not able to download the new "ApG 2.5.7.8.exe", because my Scanner deletes the file after downloading. The d-h.st-server asks me to "use virus status as a reference, rescan with your own Anti-Virus", so I'm insecure if I should deactivate my firewall. Please give me a hint. Thanks!
[Android Software/Hacking General [Developers Only]] can0brains:
http://codepad.org/Qccv3ddy

can someone take a look at this for me and help me figure out why i cant patch with openpdroid?... Thanks!
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Would someone please be so nice to provide me with the latest patch for AOKP 4.2.1 by helicopter88?
[Android Software/Hacking General [Developers Only]] karamelos:
Hi,

your link done: aokp_shooteru_unofficial_Jan-28-13.zip

the last build: aokp_shooteru_unofficial_Feb-04-13.zip

http://goo.im/devs/helicopter88/aokp/

With the last auto_patcher & rom

!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied

Yes my site is down, i've no time for blogging

Hi see this post

http://xdaforums.com/showpost.php?p=36732858&postcount=1756

Pdroid2 pre-realese out :)
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Nothing to download? Did you patch that version?
[Android Software/Hacking General [Developers Only]] karamelos:
Same

with 2.6.50

error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

Is that a general Auto-Patcher problem right now?
[Android Software/Hacking General [Developers Only]] karamelos:
With Auto_patcher 2.6.50 your rom is not supported (or broken patch) i see that in this post http://xdaforums.com/showpost.php?p=37655925&postcount=2055

BUT

with 2.6.25 patch work

flash update-aokp-shooteru-20130128-openpdroid.zip to install the patched files

flash restore-aokp-shooteru-20130128.zip to restore the original system
[Android Software/Hacking General [Developers Only]] dombeef:
Nook Color Cm10.1 Alpha bootloop tabletUI

I am trying to create a flashable tabletUI zip with the cm10.1 alpha rom for the Nook Color, but every time I flash the zip, it ends up giving me a bootloop. Could it be that booting off a sd card is causing the problem?
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

This is easy.. I believe grayfox has been at this for some time. Search for a username similar. Helpful stuff for av problems.
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

mateorod, would you please add the NEWEST patches for PDroid 2.0 with 1.54 patch into Auto-Patcher?
[Android Software/Hacking General [Developers Only]] mateorod:
Ah ha. Then it is like I suspected and just related to those Samsung roms. I don't know why they don't just update their fork, then they would have CM''s latest efforts instead of just their best as of two months ago. But okay, that I cannot control.

I will try and put something in for 2.6.7

This log is not opening for me...could you repost it for me? Maybe a problem on my end...but it never loads.

Okay this is getting really frustrating. What is happening here is that I am chasing my tail. I just figured this out thanks to you and karamelos. There is something happening here that is similar to the Samsung PA issue. As in, some AOKP roms are using one repo and others are using another. I was fixing it for the Nexus-type devices, which then broke it for the others, And vice-versa...

This is what I have done for now as I buy some time to investigate. In the NEW Autopatcher 2.6.55, I have added the original AOKP patches, the ones that work for your dspr and the shooteru roms, as patch dates 20130204. That basically means that if an AOKP rom fails, then you should try the other patch date.

I believe that the Nexus-type patches are the default as 20130205 and so you would be needing 20130204 patches. They have all the latest fixes in the. SecUpwN and karamelos, I believe the same goes for you.

If anyone sees someone reporting a broken AOKP patching, will you recommend they try the other patch date? I have been very glad that I was able to remove the patch date process and it saddens me to have to use it...hopefully i can figure a way around this.

for manual patching, if the regular aokp patches fail, enter

./auto_patcher ROM.zip openpdroid aokp 20130204

See above...you should use the 20130204 patches until i figure a better way.

TabletUI needs work...although I had to implement some specific Nook stuff for sdcard installs to work for cm10, maybe the same for 10.1. Could you upload your log, please? I am aiming to have a final fix or solution or at least decision for Auto-Patcher v2.6.7. Your log may help.
[Android Software/Hacking General [Developers Only]] nsmart:
cm-10.1-20130209-NIGHTLY-mako.zip can no longer be patched with openpdroid. I tried autopatcher v2.6.25 and 2.6.55.

error is:

... apply services.patch ...

150 out of 152 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej

!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!

!!! patch error for com/android/server/ServerThread.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] SilentEYE:
5€ donation from me if our Sony Xperia S Device is supported again.

Many of our Community are so sad, because we don't have any Auto-Patcher support at the moment.
[Android Software/Hacking General [Developers Only]] dombeef:
Ok, it may help that I am using mac os 10.8.2

http://pastebin.com/0xBn4heS

I am going to try it on the emmc and see if that was a problem

Oh, and booting off the SD card works for cm10.1, just when i flash the tabletUI zip it causes a bootloop. if i flash the restore zip it boots normally.
[Android Software/Hacking General [Developers Only]] l3ullseye:
I'm having trouble patching the latest version of this ROM, tried it with manual and ApG

http://codepad.org/ATXChCja

ROM: http://xdaforums.com/showthread.php?t=2115520

Thanks
[Android Software/Hacking General [Developers Only]] mateorod:
Okay I got the link open...I don't know anything about baked_grouper blackbean rom. You might try using the 'cm' patches, but if they fail, then the rom just isn't supported. We support 10-12 grouper roms that I know of off the top of my head, so you can get it to work if you want to.

Okay, thanks. I think that the recent merge of the FM radio broke the services. patches. Maybe those AOKP roms that have broken merged that as well? Worth looking into. I hope to have a fix for this really soon, although if the other roms start merging this is will be a real pain.

Funnily enough, this FM patch wouldn't be possible if it wasn't for the commit I sent up to CM to get room in the framework.jar for PDroid. If they hadn't merged it, there wouldn't be space...I wonder if there will be space for OpenPDroid still. I added some contingency plans, so hopefully it will resolve itself automatically.

Sorry, I remember you bringing this up, but not where things stand. i get a bunch of reports here, every day. Could you attach a recent log please?

I found the problem and fixed it...it was tied to the Nook-specific scripts and the new way I am applying the tabletUI. Please please let me know how it works for you once it is flashed...I am having a lot of trouble with this mod and all reports help. I need to figure out what is going on or cut it entirely for 2.6.7.

It is available for ApG, but I just saw you used a Mac. It will be in the next version of the autopatcher, but that won't be until I fix these Cm10.1 openpdroid errors. Just change line 1126 into these two lines:

FORMATTED_FILE=${FILE:1}
echo "set_perm(0, 0, 0644, \"/$FORMATTED_FILE\");" >> UPDATE.txt

...and run it again.

This is probably the same thing as nsmart, and is a result of upstream breakage, Try a rom from 0207 or earlier and I will try and put out new patches tomorrow...
[Android Software/Hacking General [Developers Only]] JayXon:
I hope that paranoid android 3.0 support will be released soon.
[Android Software/Hacking General [Developers Only]] Uzephi:
I am currently trying to patch a multi ROM (currently made for I_atnt and I_vzw, the LG Nitro and LG Spectrum, very similar devices)

Back in December when we got CM10 support on my device (I_vzw) I used ApG 2.0.0.0 and it patched flawlessly.

After we got support for CM10.1, I updated ApG and every patch I make (all successful, no failed patches) I get an error code 7 when trying to apply the zip. Any way to remove the device check on these multi ROMs?

Link for reference:

http://androidforums.com/spectrum-all-things-root/685391-rom-quattrimus-jb-cm10-1-aokp42.html

If you need a log of the patch, I can make one when I get off work tonight.
[Android Software/Hacking General [Developers Only]] burny:
Hi!

I have been using the Autopatcher with ApG since October 2012, and all went well for my Sony Xperia Ray and Pdroid / Pdroid 2 with the FXP roms. Since FXP204 though, i have not been able to patch these (FXP 204,205, 206 all fail with a similar error) anymore. It might be the same reason as stated in

Here is a log for my last try with Autopatcher 2.6.60 and FXP 206:

http://codepad.org/oxyKBm58

Maybe you can have a look at it and include a fix in one of the future versions?

Thanks for the great work!

Berni.
[Android Software/Hacking General [Developers Only]] murraynt:
I'm trying to patch xylon 18 for my Galaxy Nexus but I keep getting this error code

!!! PATCHING FAILED FOR android/os/SystemProperties.smali !!!

!!! patch error for android/os/SystemProperties.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: failed android/os/SystemProperties.smali in framework.jar cannot be remedied

I have tried using both the terminal in mint and the windows gui.

Any help would be appreciated.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Re: [Utility][2.6.25][2/01] Auto-Patcher (4.2.1)

I have kobik77 s latest release of apg installed and updated. The release information is only available until 11/17 even after in app sync/update. Openpdroid should be included , right? Or is it a patch from pdroid/pdroid2?
[Android Software/Hacking General [Developers Only]] FredFFF:
problem with slimrom 4.2.1 and openpdroid patch

Hello,

First of all, thanks for your great work!

I am trying to patch the latest i9100 slimrom (4.2.1 RC2), but unfortunately there is a problem :

I am using the latest github auto-patcher version (2.6.6)

command line:

./auto_patcher Slim-GT-I9100-4.2.1.RC.2-OFFICIAL.zip openpdroid,v6supercharger

I have also tried

./auto_patcher Slim-GT-I9100-4.2.1.RC.2-OFFICIAL.zip openpdroid,v6supercharger aosp

same result:

1 out of 4 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/GsmServiceStateTracker.smali.rej

!!! PATCHING FAILED FOR com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!

File for which patching failed:

---------------------------------------------

GsmServiceStateTracker.smali

---------------------------------------------​

Here are the slimrom file's info:

./auto_patcher Slim-GT-I9100-4.2.1.RC.2-OFFICIAL.zip -h

The Auto-Patcher v2.6.6

### verify tools ###

### verify ROM ###

### unzip patch tools ###

### unzip patch patches ###

\décompressé : system/build.prop

... result of ROM check: RIL= SamsungExynos4RIL

### probe rom type ###

... result of ROM check: version= 4.2.1 rom= aosp ...

AVAILABLE PATCHES

*******************************************************************

Note: There are ONLY 4 ROMTYPES: [pa, cm, aokp, and aosp].

3gdongle/4.2/generic pdroid/4.0/aokp

3gdongle/4.1/generic pdroid/4.1/pa

external_internal/all pdroid/4.1/cm

insecure/all pdroid/4.1/aosp

openpdroid/4.2/pa pdroid/4.1/aokp

openpdroid/4.2/cm secure/all

openpdroid/4.2/aosp tabletUI/4.2/cm
​

Am I doing something wrong??? Is there a workaround?

thanks for your help...
[Android Software/Hacking General [Developers Only]] vhick:
Another failed in patching after ROM update:

http://codepad.org/ReJAIeUv

Thanks...
[Android Software/Hacking General [Developers Only]] xFluffyx:
here is my log:

codepad org/ivEmKDyZ

i use:

ApG 2.5.7.8
[Android Software/Hacking General [Developers Only]] f0xy:
Latest APG

First time user

CM10.1 nightly i9300

http://codepad.org/0kokEqHg

Trying to patch with openpdroid
[Android Software/Hacking General [Developers Only]] mateorod:
Well considering that PA 3.0 was released yesterday, I guess I will just thank you for your patience.

All the updater-script does is cat the original updater-script really. I have some workarounds that I use for the Nook Color, but that would take a lot of work for me to reliably add as a general protocol and I can't do it right now. Why don't you just remove the device check by hand? I will keep the request in mind, an overhaul of the updater-scripting is perhaps in order, but managing all of the various permissions for various files and various devices could get hairy. I am a little loathe to mess with something that is working for all roms except I guess Multi-roms...I will think about it.

I can't swear I can fix it, but I will look at it.

This is probably not resolvable. When I fixed this error for another galaxy Nexus rom, another error pops up a little later. GNex (toro at least) is not supported by aosp, it leads to a lot of problems for us. Looking to see if there is something I can do for GNEx is on the list, though.

Well,there are bunch of users here who are sucessfully using ApG...I don;t know what to say. Maybe try uninstalliing and reinstalling? I last updated on 2/08 I think,and openpdroid is it's own mod.

Well, a) the second log is pretty clear, I think. It is just a help menu. The first snippet (b) is not a complete log...and that by itself is not an error, it is a step on the path to a patched rom, unless something is wrong. Doesn't it ask you if you want to copy over a prepatched copy of that file? Post your whole log please, I need that info, that is why I add it to the log.

I thought I addressed this in my last post earlier today. CM had a major update, and it broke the patch. It happens from time to time, I can't control when they might update files that we patch and break the autopatcher. When it happens I have to rebuild the patches, which i am doing now. Your options are

use a rom from 2/07 or earlier

wait until new patches are out

The same essentially goes for PA 3.0. I am working on it, shouldn't be long.(hours not days, unless catastrophe strikes...)
[Android Software/Hacking General [Developers Only]] dombeef:
Now I get

dombeefs-Mac-mini:autopatcher dombeef$ ./auto_patcher /Users/dombeef/Desktop/cm-10.1-a1-encore-fullofbugs.zip tabletUI

The Auto-Patcher v2.6.25

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.2.1 rom= aosp ...
... Using results of ROM check ...
... tabletUI patch date has been set to: 20130201 ...
./auto_patcher: line 1126: syntax error near unexpected token `newline'
./auto_patcher: line 1126: `FORMATTED_FILE=${FILE:1}'

And it stops. I changed the right line too. :confused:
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, I believe you,. Maybe I omitted something there. Just copy/paste everything here over the script and you should be set.
[Android Software/Hacking General [Developers Only]] f0xy:
Thank you for this information, I will follow the thread from now on, seems like your doin an excellent job,

p.s i'll wait till you update your patches :D
[Android Software/Hacking General [Developers Only]] Ashcunak:
I seem to be having problems running this for the first time, the java.exe and cygwin.exe's each download and each error near th end of their un-packaging. any ideas? both were CRC error unexpected end of file.

*edit*

weird.. so NOW it works.. 9th times the charm.. looks like the download server feeding them out just sorta fails near the end of the upload to me even RDP'd to a computer on a diff ISP and had the same issue...