yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Flashcry.xt:
Hey Guys, i need some help here.

Im trying to patch pdroid2.0 to my cm10.zip file, but it doesnt work. Strangely pdroid1-patch with autopatcher is working fine with the same .zip. Heres my logifle, any tipps what im doing wrong?

$ ./auto_patcher cm-10-20121216-NIGHTLY-i9100.zip pd2.0 cm10

The Auto-Patcher v2.4.7

### verify tools ###

### verify ROM ###

### unzip patch tools ###

### unzip patch patches ###

\vergr▒▒ert: system/build.prop

... result of ROM check: RIL= Smdk4210RIL

### probe rom type ###

... result of ROM check: version= jellybean rom= cm ...

... Using cm10 patches ...

ls: Zugriff auf patches/pd2.0/jellybean/generic/ nicht möglich: No such file or directory

... pd2.0 patch date has been set to: 20201231...

### unzip rom ###

\vergr▒▒ert: system/framework/core.jar

\vergr▒▒ert: system/framework/framework.jar

\vergr▒▒ert: system/framework/services.jar

### create updater script ###

\vergr▒▒ert: META-INF/com/google/android/update-binary

\vergr▒▒ert: META-INF/com/google/android/updater-script

... using Clockworkmod installer ...

\vergr▒▒ert: system/app/Mms.apk

### create restore.zip ###

### decompile system files ###

... decompile framework.jar ...

... extract preloaded-classes ...

... decompile core.jar ...

... decompile services.jar ...

### copy patch pd2.0/jellybean/generic/latest ###

... copying system/app/Mms.apk ...

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

!!! error: system/app/Mms.apk is missing in the patch

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

! please refer to /home/Tayris/log20130110225122.txt for any debugging

! patching failed.

! it may be possible to patch /home/Tayris/cm-10-20121216-NIGHTLY-i9100.zip using other patch version

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
[Android Software/Hacking General [Developers Only]] Febby:
thanks for this amazing patcher. I hope it works when I try it out soon. :)
[Android Software/Hacking General [Developers Only]] pro.aggro:
Any news for 4.2.1?

Sent from Nexus 4 powered by PARANOIDANDROID
[Android Software/Hacking General [Developers Only]] Febby:
using APG GUI app I can't seem to patch any ROM. I tried a CNA 4.1.2 based rom, CM9 stable, and CM10 ROM. It always says failed to patch. I've uploaded 2 log links. How do you guys get this to work?

http://codepad.org/zZwX2BDy

http://codepad.org/QlsZPC0d
[Android Software/Hacking General [Developers Only]] karamelos:
hi,

in your command

auto_patcher cm-10-20121216-NIGHTLY-i9100.zip pd2.0 cm10

only this option: cm, aokp, aosp, pa

I trying to patch your rom (curiosity)

download here http://goo.im/devs/cm/i9100/nightly/cm-10-20121216-NIGHTLY-i9100.zip

For exemple:

link with patch & log for cm-10-20121216-NIGHTLY-i9100.zip

Update coming in February
[Android Software/Hacking General [Developers Only]] Flashcry.xt:
Thank you for the Patch and your advice karamelos.

I used the same command for the pdroid-patch, cm10 in commandline. Worked fine.

But ill try if it works when i use only cm fpr pd2.0 when im at home. Want to fix this to patch future Roms by myself :)

Update: It worked with the cm command, thanks again for your help karamelos. Such a simple mistake :(
[Android Software/Hacking General [Developers Only]] mateorod:
^^^^^

That.

Very important! And a pretty cool side effect. Because we are breaking down and changing roms at a base level...and yet no risk as long as you have custom recovery and know how to use it.

I can only assume that you are using such an old rom because there is nothing newer for your device? When devices are not able to make nightlies on a regular basis, that usually means that somebody had to put a bunch of work to make builds at all, which lots of changes. You see this also with the defy. Sometimes those changes are incompatible with the patches we put in autopatcher. Our patches are based on stock builds of the various (cm, aokp, aosp, and pa) rom types. If a device has to deviate too far from the official upstream tree, it can break the patches.

It isn't even really a question of it being old, we have patches that covers basically the last year for most devices. it is just what that usually means when devices are no longer getting updates for their roms.

Unless you are using an older rom just because? I don't see a lot of toro logs, I am not very familiar with what works or doesn't for that device. For the cm roms, try it simple

./auto_patcher ROM.name pd2.0 cm

I have added even more error-catches for situations like this in the update. The help menus have also been completely redone. I think you guys will like it and some of these little frustrations will subside.

Thanks to karamelos and grayfoxmg1!
[Android Software/Hacking General [Developers Only]] Magissia:
I have problem with patcher gui for windows, mod type and rom type list are empty ...

Logs says

Pulling latest changes of autopatcher from GitHub...

No local changes to save

Already up-to-date.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
from the logs, and feel free to correct me if I'm wrong, it looks like you have ApG installed on your desktop. It won't work from there, now if you wanted to make a floder on your desktop called auto_patcher and put everything in there it should work. I don't know why ApG doesn't run on desktop, but it never has and probably never will. It's a small mistake that can lock up the whole program.

/c/Users/iFebby/Desktop/ApGPackages

^^^^this line is what gives me that impression. Now if it was moved one directory in either direction it should work. so try putting it in

/c/Users/iFebby/Desktop/Auto_Patcher/ApGPackages
[Android Software/Hacking General [Developers Only]] karamelos:
With ..... Marabout mode : windows 95 :p
[Android Software/Hacking General [Developers Only]] Febby:
Thank you! I have a spare partition D: for my linux. If I place the program there should it hopefully work? =) I'll try as you said
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
dude all you need to do is make a folder on your desktop and install ApG inside of it.
[Android Software/Hacking General [Developers Only]] Febby:
Yes I got that once I read it. It worked for CM9. Quite a lot of the most recent 4.1.2 ROMs for the galaxy nexus still fail though. Must be a nexus thing.

Edit: I got to work with an older pure aokp ROM. I guess some of the aokp roms devs made have different custom files that make it hard to patch. :)
[Android Software/Hacking General [Developers Only]] karamelos:
Hi,

Read @grayfoxmg1 & @kobik77 post for config apg

I dont have your device

auto_patcher work fine on linux for exemple:

cm-10.0.0-maguro.zip ---- Google Galaxy Nexus (GSM)

md5sum: 5c9047449c0cd589df9162bf2aaabb4c

Short URL: http://get.cm/get/4LY

pdroid2 log/patch (up-re): http://d-h.st/wgx
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.5 (Copper)

The Auto-Patcher 2.5.0 release is out.

Pleased to announce a new mod...OpenPdroid. Works for 4.1.2 and 4.2.1! This is a fork of the open-source PDroid framework written by Syvat and expanded upon by pastime1971, me, FFU5y and especially CollegeDev.

You will need the PDroid Manager app from here. But 4.2.1 support, amirite?

./auto_patcher <YOURROMSNAME>.zip openpdroid

Improvement include:

'openpdroid' support for 4.1.2 and 4.2.1 (aokp, aosp, cm for now)

Big security hole in 'openpdroid' and 'pdroid' fixed. (Not in 'pd2.0' yet, but the fix has been sent to CollegeDev as well).

Help and error-catching reworked

"Specific auto_patcher script options"
./auto_patcher -h [mods] Lists mods"
-h [<MODNAME>] Specific <MOD> info"
-h [advanced] Advanced usage+lists all available patch dates"

"Perfect" Build Date matching. - No matter how many mods you apply, the Auto-Patcher will choose the best patches for your build date.

"Nearly Perfect" Romtype matching.

I can't get "Perfect" ROM type matching until they get their act together and standardize build.props. But I will keep trying.

OpenPDroid

is built on the back of the work of people like Svyat, Pastime1971 and CollegeDev but looks to leverage the open-source community that has maintained and dragged PDroid from Gingerbread, where it was abandoned, to Jellybean and beyond.

We are launching a thread strictly for the discussion of the framework patches and their security. Newest patches will always be available in the Auto-Patcher. The OpenPdroid patches have only been tested heavily with the open-source Pdroid Manager, an alternative to the privately Pdroid2.0.

The PDroid2.0 app has not been heavily tested with the openpdroid core, but FC's were reported for 4.2.1 at minimum. Best to use PDroid Manager until we hear from CollegeDev. The goal with OpenPdroid is to have the PDroid framework patches (always open-source since Svyat published the original patches under GNU GPLv3) become universal for all of the versions of PDroid.

Our goal is to use the time-tested security benefits of open-source software. The Linux Kernel is one of the most secure programs ever written, despite it's scope. That is due to the quality and quantity of eyeballs on the code on a regular basis.

'openpdroid' has support for 4.2.1 for all of our supported roms except for ParanoidAndroid. They just released their 4.2.1 source the other day, so I will add them this week.

OpenPdroid team= FFU5y, wbedard, mateor and the contributions of many others. Thanks to karamelos and KicknGuitar for testing!

Edit: All mods have been updated to 4.2.1 except for pd2.0 (that can only be done by CollegeDev) and tabletUI. I quit tabletUI b/c no one is using it and it is a pain to maintain. If significant demand ensues, I may reconsider.
[Android Software/Hacking General [Developers Only]] Finitesimal:
Great work; fantastic timing.

I look for the update to support my 4.2.1-based ParanoidAndroid...BOOM! Five minutes earlier it was released.

EDIT: The only question now: from where to download?

EDIT2: The OP has now been updated.
[Android Software/Hacking General [Developers Only]] liebowa:
I have a Nexus 7 and would really like you to re-consider adding the TabletUI update.

I KNOW there is a demand over in the Nexus forums, but I'm not sure if people knew where to look for it. I'll make sure that there is an updated thread over there and that this gets the attention it deserves.

Thanks.
[Android Software/Hacking General [Developers Only]] mateorod:
The file has been uploaded, maybe 30 mins ago. So it should be available soon. However, we don't have support for ParanoidAndroid (only) because they were closed source still for 4.2.1 until just the other day. Now that this has gone up, I will add it ASAP, perhaps as soon as tomorrow but not much further than that.

I added a BUNCH of improvements/changes/refactors to the program. So there will be some updates coming out as little quirks and bugs get discovered. Nature of the beast.

TabletUI is not dead unilaterally, but I will have to see the demand. If the thread you makes gets some interest, I will add it again. I was pretty happy with it when we first released it, yet it sank like a stone. Why people would want to wait for flashable zips (that would die within a week) was beyond me. But we'll see.
[Android Software/Hacking General [Developers Only]] anomalya:
It's up! Oh man. Feels like Christmas all over again!

(Though ApG does not sync with these latest GitHub updates.)

Edit: Manually updated autopatcherv2.5.0 files into \ApGPackages\ap to patch CM10 4.2.1 ROM with (opendroid) and (v6) mods:

Resulted in SystemProperties.smali error: http://codepad.org/LqPNThsy
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
Information reguarding ApG, virus detection, and you

So I finally got tired of losing ApG everytime my anti-virus does a scan, thus I have tracked down a few things. First HERE is a link to the latest ApG, be sure to give thanks to Mateorod and Kobik77. Next before you read further, note I have a version of Norton 360 v5 installed on my computer, so any restoration steps I link to are for that, however the steps should (stressing should) be similar on all AV software. What I did was download ApG without deactivating my AV stuff (i know I went against my own instructions, shocking).

As you can guess ApG was tagged and bagged by my AV, so I went rooting around in my quarantine folder for it and it's details. ApG gets flagged (at least this is the reason from Norton/Symantic) because of an WS.Reputation.1 issue. Click the link if you want more info. But I will summarize the issue. It breaks down to, being caused by only a small amount of users having both this software (ApG) and Norton installed. Thus they flag it for having a bad community reputation. What does that mean for you, the average user? It means that out of all the hundreds of millions of people that are connected to the internet and possess an AV software, the only people using ApG or those of us from XDA. Now before you go off thinking, "Well no $^%# Sherlock," think about how that looks to their automated databases. At my last check the file-hosting site counted 238 downloads, that is probably less than 0.0000001% of the users that possess both ApG and an anti-virus program. Thus it is seen as odd, an abnormality that the grand majority of their users don't have and don't need. So they flag it has a virus/trojan/worm that is trying to steal your information. So be happy that your AV software is that thorough in protecting your machine.

How do I fix it? Well you don't. STOP, put down the flame throwers and listen first. YOU can't fix it, but maybe WE can. If you click on this LINK you should see a section called 'Disputes.' If you are a Norton user go ahead and fill that out and help us tell Norton, that this is just a freeware program created by one user on XDA-Developers for the use in patching roms for rooted android devices. If you are not a Norton user, than please take the time to find the relevant information for your AV client. If we all do this, maybe we can get them to make an exception for this program and future versions. I've already done it, but that won't matter if I am the only one that does.

Fixing it now. Alright I made you listen/read through all of that information, so let me help you get your quick fix. THIS link will take you to an instruction page on how to restore items from quarantine in a Norton AV program. It should be similar for ALL AV programs. If I've helped you at all, please thank both Mateorod, Kobik77, and the rest of the Auto_patcher team for all of their hard work. Because without them, I wouldn't have a job..........wait, I still don't have a job, somethings not right here <.< >.>
[Android Software/Hacking General [Developers Only]] Finitesimal:
Noooooooooo... *cue epic Star Wars music*
[Android Software/Hacking General [Developers Only]] r0zj0k3r:
Linux auto patcher

Maybe I am missing something here, tried to scour this forum a bit and found nothing...

I am using this linux auto patcher V 2.4.7 but the pathces that are included are for V 1.32 and break functionality with pdroid2.0 and pdroid manager. I ended up copying the extracted files from the windows auto patcher to my nix box and got a successful V 1.51 patch and a working pdroid2.0. Can you update the .tgz patches/tools files for the linux version?

Much appreciation

side note, it feels amazing to have this finally working on my N7...great app
[Android Software/Hacking General [Developers Only]] mateorod:
Without you submitting a log I am just guessing, but i bet you aren't trying to apply the correct mod. And go to the download page and update the Auto-Patcher to 2.5.0, I just updated tonight with 4.2.1 support

For PDroid Manager (4.1.2, 4.2.1)

./auto_patcher ROM.zip openpdroid

For PDroid2.0 (4.1.2)

./auto_patcher ROM.zip pd2.0

PDroid original (2.33->4.1.2)

./auto_patcher ROM.zip pdroid

To see a list of mods

./auto_patcher -h mods

And to get any info about any MOD (including what Android versions it supports, links to any dependencies (PDroid Manager etc..) and credits:

./auto_patcher -h <MOD>

Where <MOD> is replaced by the name of the mod you want info about.

If none of those get you any closer, submit the log generated by running the program and I will look at it.As a sidenote, I am a strict Linux user, I wouldn't leave you guys hanging...Linux is the one it gets tested on.
[Android Software/Hacking General [Developers Only]] anomalya:
Lest my previous post got overlooked, here is my result with your latest and greatest:

http://codepad.org/LqPNThsy

This was my attempt to patch a current CM10.1 (4.2.1) ROM with mods: (opendroid) and (v6supercharger).
[Android Software/Hacking General [Developers Only]] mateorod:
I looked but there seems to be several Cm10.1 builds for the kindle, none of them Official. Which is usually okay, but things like the kindle come so far from stock that they can be harder to support than others. Still, I have some things that I can try.

Could you pick whichever rom you think is probably the closest to Official CM10.1 and post a link? You retitled the rom in your log, so I couldn't find it...
[Android Software/Hacking General [Developers Only]] anomalya:
Sure. Thanks for looking.

You're right. I did rename the rom because it was a lot easier to manually input within the terminal, heh. In any case, the ROM came from here. As far as I know, the ROM is very close to the latest CM10.1 source with a bit of SGT7 flavor. (Though technically, there isn't an official CM10.1 Kindle ROM per se)

Coincidentally, the ROM has just been update to today.

EDIT: I re-read your previous post and this ROM is the closest to the Official CM10.1 source (as per OP's goal: "My top priority w/ the Kindle Fire is getting merged into CM. So I'm posting patches to CM review and adjusting our local_manifest as I can."), though it isn't the ROM that I'm trying to patch.
[Android Software/Hacking General [Developers Only]] r0zj0k3r:
Ok I pieced together what I did wrong, I never deleted the 'bad' patches(must have been the beer)....the ones I made before I read all of the instructions about the different mods, and thought I had. I had a bunch of 'good and bad' patches lying around and was using the wrong ones of course. I just assumed linux support fell by the way side like it does with most projects:angel:

so...thanks for the linux support, I always go for these types of tools before I try anything windows
[Android Software/Hacking General [Developers Only]] mateorod:
I had a package branch in kindle and had some experience with their roms before. Check this thread out for Kindle-related origin of the Auto-Patcher. I never had the device, but somehow maintained a thread there for quite some time.

I tried it on a couple of different Cm10.1 roms but hit the same problems as you both times. I then manually got it past the framework.jar only to have it die on the ServerThread.smali file. And that's the biggie. Errors with that mean that we are not even in the right ball park.

In the Nook forums, I saw riverzhou talk about the Cm10 project for otter and it is somewhat of a Frankenstein, with major pieces from AOSP, CM10 and TI. For now, we are not going to be able to patch it for any PDroid 4.2.1, at least.

But keep tabs on this thread. Once we have 4.2 stable we are going after the real big fish and I hope to do away with romtypes completely. That would enable stock patching and all the rest.
[Android Software/Hacking General [Developers Only]] anomalya:
Yeah, I remember this thread (BotBrew et al), heheh. In fact, it was my first introduction to your auto-patcher that allowed me to use both PDroid and V6 at the same time on multiple Kindle Fire ROMs - - - and all the way to where it's gotten to now: 2.5.0. :good:

I've been able to successfully patch this same ROM before, albeit different iteration (4.1.2). As you implied, 4.2.1 is still very much a work in progress, so I'm not expecting any rush. So for now, I'll be keeping tabs and wait it out.

All the same, congrats to v2.5.0!
[Android Software/Hacking General [Developers Only]] karamelos:
Woww good news for starting the week :p

Good work @mateorod
[Android Software/Hacking General [Developers Only]] wkwkwk:
Can anyone confirm that the Llama bug has been fixed in OpenPdroid?

In PD2.0 there was a bug where Llama wasn't updating the cell information. CollegeDev acknowledged the problem and said he fixed it and it will work fine on the next PD2.0 release (which hasn't arrived yet).

The original PDroid didn't have this bug.

Thanks.
[Android Software/Hacking General [Developers Only]] acultr:
Where can I find the the latest ApG?

I have 2.1.2.0.,but this not supported cm10.1.?
[Android Software/Hacking General [Developers Only]] kobik77:
This is the latest version.

I've just checked and it synced with the latest auto patcher version without a problem so it should be compatible with cm 10.1

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] acultr:
Thanks

I'm stupid.

I used p2,not open pdroid.
[Android Software/Hacking General [Developers Only]] kobik77:
mateorod and the team, you guys are just awesome.

Can't thank you all enough for your hard work on this.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] dr4go:
Definitely +1. :)

I was so excited about the new release, that I wanted to jump to cm10.1 right away. However when trying to apply the openpdroid patch for it, v2.5.0 failed with a reject file (RILSender.smali.rej) and the Mms.apk, which couldn't be rebuilt. Please see the attached log file for further information.

The cm10.1 version I've used for the p990 was the following one: http://get.cm/get/5PK

Again: thanks so much. :)
[Android Software/Hacking General [Developers Only]] Flashcry.xt:
First of all, thanks to the Team for their amazing work.

One short question for my understanding, im running original pdroid 1.32 (and want to keep it) at the moment on cm10.

When i update to cm10.1 now, 4.2.1 is supported for original pdroid with the new autopatcher 2.5.0 ?
[Android Software/Hacking General [Developers Only]] JobSup:
Autopatcher fails with cm10.1

Just found out that the new autopatcher version now supports CM10.1 with openpdroid. Tried to patch a rom, but it fails with:

... apply telephony-common.patch ...
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 !!!
!!! patch error for com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!

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

!!! error: failed com/android/internal/telephony/gsm/GsmServiceStateTracker.smali in telephony-common.jar cannot be remedied

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

Anything I can try here to successfully patch this CM10.1 rom?
[Android Software/Hacking General [Developers Only]] hugoma:
I tried to AOKP JB-mr1 patch openpdroid, but failed.
[Android Software/Hacking General [Developers Only]] scutworker:
Thanks for the update but, alas, it failed to patch my Evervolv based HTC Desire JellyBean rom.

It's this rom:

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

and the logfile is attched.

Thanks.
[Android Software/Hacking General [Developers Only]] mywave:
I'd like to have this feature for the Nexus 7.

Many thanks.
[Android Software/Hacking General [Developers Only]] karamelos:
Yes

I have cm10.1 on my nexus7 with openpdroid
[Android Software/Hacking General [Developers Only]] acultr:
openpdroid works for me on Flinny cm10.1 build 10