yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] fezzawinkle:
Edit: solved my own problem by reinstalling APG from scratch.

Can you help me? I am running APG and getting the following output on a CM10.1 Rom for Tilapia Nexus 7. Says that autopatcher is not available for android 4.2.2. What am I missing?

The only thing I notice is that the changelog on APG only updates itself to v2.7 of the autopatcher, but I see that it is up to 2.8.3 on the Github.

thanks

Pulling latest changes of autopatcher from GitHub...

error: could not lock config file /home/Media/.gitconfig: No such file or directory

*** 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 <Media@Media-PC.(none)> not allowed

Cannot save the current index state

error: Your local changes to the following files would be overwritten by merge:

patch_tools/apktool.jar

Please, commit your changes or stash them before you can merge.

Aborting

Updating 0e711ae..b0eaaf9

Running autopatcher with the following arguments:

ROM_PATH: /cygdrive/c/Users/Media/Downloads/cm-10.1-20130228-UNOFFICIAL-tilapia-V49.zip

PATCH_TYPE: openpdroid

ROM_TYPE: cm

The Auto-Patcher v2.6.7

### verify tools ###

### verify ROM ###

### unzip patch tools ###

### unzip patch patches ###

inflated: system/build.prop

### probe rom type ###

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

... Using cm patches ...

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

!!! error: Sorry, openpdroid has not been made available for Android 4.2.2 yet!

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

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>

example: ./auto_patcher CM10.zip openpdroid cm

Use ./auto_patcher -h for the help menu
[Android Software/Hacking General [Developers Only]] karamelos:
I submit new patch to @mateorod today for slimroms (latest patch on github)

try

$git clone https://github.com/mateor/auto-patcher.git
[Android Software/Hacking General [Developers Only]] karamelos:
Re: [Utility][2.7.5][2/10] Auto-Patcher (4.2.2)

@mateorod

Slim patch make with 4.1.2 openpdroid patch

I look on opendroid git last update 25 February

I just rebuild with last patch just that ! I not upoad it if not necessary
[Android Software/Hacking General [Developers Only]] mateorod:
jeez, yeah, this is my fault. I have been busy creating and uploading the project history to github while the merge of PDroid2.0 and OPenPDroid patches is ongoing. Those patches are the same ones I used to make the existing 4.1.2 patches. So while those patches are being newly pushed to github, they are actually the same patches that we had before, the 1.0.1 patches.

The only thing that needs tp be built (to my knowledge) is 4.1.2 PA, but we have some FCs we need to fix in first.

I will for sure explicitly let you guys know what I am doing on github, I am not used to people watching what I push up there! But yeah, I think all the patches are okay for now, but I am going to keep an eye on what happens from the new AOSP device repos, to see if we need to rebuild from that.

Thanks karamelos. I have something else I am thinking about too, look for a pm from me in a couple days, ok?
[Android Software/Hacking General [Developers Only]] Caldair:
I used the same changes to the the autopatcher (i'm still on 2.8.1) that produce working tabletUI mods for Samsung Galaxy Tab 2 7.0, to make this one for Nook Color based on [ROM][BETA] CyanogenMod 10.1 Beta for NookColor [2/27/13]. I had to define the rom type bacause the autopatcher saw this rom as AOSP, not CM. I only changed the version ceiling in auto_patcher and since the autopatcher was crashing on patching Settings.apk I renamed the Settings.apk.patch to *.bak, then remove Settings.apk from the output update zip.

This is the exact same method that is working for Tab 2 7.0, but I can't test this because I don't have a Nook Color.

Dombeef, if you want to try this and see if it works for you I could give more details on how to set up autopatcher to do this yourself. Or, if this zip doesn't work for you I could upload the one automatically produced, using AOSP patches (which don't patch SystemUI.apk).

Let me know if this gets you any closer.:)

Also, FYI, I have used the same method to produce tabletUI updates for my Droid 3 running CM10.1 from 02-26 and they work, but the graphics are all too large for the small screen, at default 240 dpi, but work exactly as expected if I set dpi to 160 (I just need a loupe to see it).
[Android Software/Hacking General [Developers Only]] Px80:
HI guys,

i got ApG working on my win7 notebook.

I tried to patch the latest version of Pacman v.20 for Desire s but i always get the same error message.

I tried pd2.0 and openpdroid with pa, cm, aosp automatic and manual patching.

Nothing worked, ApG tells me everytime " error: unknown ROM version."

but it should be cm10 for 4.2.2
[Android Software/Hacking General [Developers Only]] motisu:
It works perfectly!! I installed it on the encore 10.1 beta and I now have tablet mode!! Great work.
[Android Software/Hacking General [Developers Only]] Caldair:
That's awesome! I am really glad to hear it. The Autopatcher is an incredible tool! And based on Mateorod's commits today, you Nook Color guys should be able to patch that particular rom, no problem. And me too, with my Tab 2!

Thanks mateorod! The level of support here is excellent! Thanks to all.:highfive:
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

Hi Px80, from my understanding of auto_patcher the probe that determines your Rom type and version is failing, this reads parts of your build.prop file to work out what you are trying to patch. Could you possibly paste your build.prop file contents to http://codepad.org then post the link here I am sure that would assist in finding out what is going on.

Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

I can't remember ApG very well can you just select OpenPdroid with no Rom type to let auto_patcher select the PAC patches? Or try manual patching with just OpenPdroid and no Rom type. I don't think you can select PAC itself it is a branch of the aosp patches but not an individual Rom type like cm, pa or aokp.

Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
[Android Software/Hacking General [Developers Only]] abby_nitewolf:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

It worked on ApG without selecting specific ROM type. Thank you.
[Android Software/Hacking General [Developers Only]] dombeef:
It still causes a boot-image loop when I try to boot off the SD with the zip installed. I can't try the internal emmc at the moment due to my nook being used and I can't risk breaking any apps.
[Android Software/Hacking General [Developers Only]] brashmadcap:
Patching with ApG still generates a rom that has mms.apk in /system/app but it's not in the launcher at all. I've tried to push other mms.apk that is patched but no dice. I'm going to try a completely unpatched mms.apk and see how that goes; and if anyone has a cm10.1 mms.apk that is patched and working, can you hook me up plz? thanks!

Confirmed: unpatched mms.apk does work. Something with the prepatched one from ApG is wonky
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Hey brashmadcap, you can try this one I patch PACman rom and compile from the source the Mms.apk is taken from the CM10.1 repo and it works fine for me so you could give it a try.

CM10.1 Patched Mms.apk
[Android Software/Hacking General [Developers Only]] scutworker:
Re: [Utility][2.8.3][03/01] Auto-Patcher (4.2.2)

I have the same problem in that the mms.apk produced by the autopatcher doesn't show in the launcher.

But I just installed your version into my Evervolv based ROM and it works fine.

Thanks.
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Excellent glad it worked for you. :good:

Mateorod - This Mms.apk could be a good candidate to replace the existing Mms.apk as it looks like it may work ok for the users experiencing issues. PACman uses the true cm10.1 repo for the Mms.apk so it shouldn't cause any issues.
[Android Software/Hacking General [Developers Only]] Px80:
Ok,

heres the build.prop from the saga folder.

http://codepad.org/elCXkbll

hope you guys find something useful!

Thx!
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Ok I think I found the problem the auto-patcher is looking for a lower case "pac" to identify PACman rom this is how my build.prop is generated but yours has a capital PAC :silly:

I have attached a slightly modified auto_patcher script that you could try all I have done is extend the check to look for both "pac" and "PAC", extract the attached auto_patcher script and copy it over your current one and re-run the patcher without selecting a rom type. Hopefully it will pick up the rom correctly and patch it for you.

If not sorry mate you will have to wait for the master mateorod to check things out. :good:
[Android Software/Hacking General [Developers Only]] Px80:
Thx for your help but that did not work. Same error as before.

I have to wait
[Android Software/Hacking General [Developers Only]] Flashcry.xt:
I somehow lost the overview, sorry.

Does Openpdroid support CollegeDevs Pdrpid 2.0 now?`

I want to patch cm 10.1 and use pdroid 2.0 on it
[Android Software/Hacking General [Developers Only]] brashmadcap:
Thank you thank you!
[Android Software/Hacking General [Developers Only]] dangerzone:
success: nozomi / xperia S - OpenSEMC-OTA-v0.4

success story: (for xperia S users)

using autopatcherv2.8.3 to patch OpenSEMC-OTA-v0.4.zip

command line used:

$ ./auto_patcher OpenSEMC-OTA-v0.4.zip openpdroid

I had to use a premade copy of 'CdmaServiceStateTracker.smali' (had to type YES once in Autopatcher)

The patches appears to work properly.
[Android Software/Hacking General [Developers Only]] SilentEYE:
Last time I had a big battery drain. What about it now?
[Android Software/Hacking General [Developers Only]] Didgesteve:
I wanted to run Slim 4.2.2 through the Autopatcher again after seeing that karamelos updated the patches.

Now it fails.

It was working on 2.8.1

Thought you should know.
[Android Software/Hacking General [Developers Only]] mateorod:
There is something extra going on with the Nook color...I hav some specific Nook workarounds due to (a bug?) in some of the Nook installer scripts. I really need an autopatcher log and a logcat to help. Did I miss it getting posted?

This will have to be quick...I am working on my wife's engine, her throttle body is laying in the driveway xD.

Autopatcher 2.8.4 is out for ApG and has been uploaded to our download page (it takes maybe 15 mins to appear).

Replaced Mms.apk with AussieLampChop's-( I think the other one just got too old. Let me know if anyone experiences anything funny...if I have to I can easily carry two copies, old and new) Hopefully this fixes the 'missing' Mms.apks.

Removed Settings.apk.patch from tabletUI (I will work on getting this up to 4.2.2, but I need a logcat from FC's on notification bar.)

Commits from AussieLampChop and eMPee584 (thanks for the pull requests!) improving logic.

Issue List

CollegeDev. FFU5y and I are working on the merge between OpenPDroid and PDroid2.0 build patches. I would think we will have a 1.1 release with new build patches and Autopatcher patches ready to be made sometime in the next couple weeks.

I have been looking at the CM10/PA4.1.2. crashes with CollegeDev, hopefully we can get that current soon. For now, stick with 4.1.2 roms from before 0209.

I am waiting on logcats to debug tabletUI and Nook Color.

In a week or so, I think that karamelos and I will check a couple builds and see if things have improved for toro and toroplus with the improved AOSP integration for those devices.

Any other requests or problems with existing features I didn't list?

According to your log, that is still 4.2.1. We were carrying patches that worked for 4.2.1 SlimRom, maybe that rom is just caught in-between the two. It is hard to get complete coverage during upstream merges. Find a recent 4.2.2 and maybe try again.
[Android Software/Hacking General [Developers Only]] mateorod:
QUOTE=raimundo amador;28655390]I've tried different patchers for cm7, all of them gave me same results:

Well, one of the problems looks to be that that is a Gingerbread ROM, I think. There is no v6supercharger patch needed for Gingerbread. You can just run the script in a terminal w/o services.jar edits. trying to apply the patch will result in a non-compile, we are planning to include that in our error checking soon.

Also, you should try and specify a ROMTYPE and, since the build is from early June, a patch set. The best set of arguments for your rom appear to be:

./auto_patcher RSK_S.E.deodex.zip pdroid cm7 20120514

If that still fails to patch, you could try the other available cm7 patches (although really, the above patch set is your best bet). You can see the patch dates available by

./auto_patcher RSK_S.E.deodex.zip -h

We don't have a patch that reliably works for the cm7.2 final. But it does work for most cm7 nightlies, which are the same as the 7.2 final, but with some extra commits. Try and patch the latest nightly for your device.
[Android Software/Hacking General [Developers Only]] domina:
I just tried your best but, unfortunaly it doesnt work. It doenst make sense for me to use a nightly cm7 rom, cause i want to use a sensed based one. Any ideas?
[Android Software/Hacking General [Developers Only]] mateorod:
We only have patches for the ROM types you will see by entering the -h flag. We can only generate patches through having source code. If you have the ability to contact the developer of your ROM this is what you will need.

If source is already available, then you can apply the patches at build time. We can then use that patched build to make patches and hopefully support later updates. But w/o source, it is a no go, unless the ROM is heavily based on one of the existing ROM types in the patcher. Sense is it's own thing, and not likely to be supported at the moment...
[Android Software/Hacking General [Developers Only]] anilrawal:
Patch failed error: failed framework.patch

I am compiling for pdroid for cm9 rom Inspire HD using cygwin, I keep getting the error "error: failed framework.patch"

my syntax is " ./auto_patcher Cm9_DHD.zip pdroid cm9 20120711"

Any suggestions or help be appreciated.
[Android Software/Hacking General [Developers Only]] kaizokan:
If im correct MIUI V4 is based on Android 4.0.4 ICS and CyanogenMod 9 sources. The source is available: https://github.com/MiCode

I am not using this ROM: [ROM] MIUI 2.7.6 - Android 4.0.4 for Locked AND unlocked Bootloaders but would it be compatible with Pdroid?

.
[Android Software/Hacking General [Developers Only]] pastime1971:
it would be better if someone compiles it w/ and w/o pdroid and make a patch.

we've seen many roms that are based on CM, yet patching fails for.
[Android Software/Hacking General [Developers Only]] Boerni83:
premission

$ ./auto_patcher cm9defy.zip pdroid 20120709
### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
### 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 ###
### create restore.zip ###
### decompile framework.jar ###
... extract preloaded-classes ...
### decompile core.jar ###
### decompile services.jar ###
### patch pdroid/generic/latest ###
### apply framework.patch ###
The next patch would create the file 'smali/android/app/ContextImpl$34.smali',
which already exists! Skipping patch.
1 out of 1 hunk ignored
Reversed (or previously applied) patch detected! Skipping patch.
14 out of 14 hunks ignored -- saving rejects to file smali/android/app/Fragment.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file 'smali/android/app/LoaderManagerImpl$LoaderInfo.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/content/CursorLoader.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/content/Loader.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file smali/android/database/sqlite/SQLiteClosable.smali.rej
36 out of 36 hunks FAILED -- saving rejects to file smali/android/net/wifi/WifiConfigStore.smali.rej
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed framework.patch
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /cygdrive/c/cm9/ap/log20120714105355 for any debugging

! patching failed.
! it may be possible to patch /cygdrive/c/cm9/ap/cm9defy.zip using other patch version

premission faild??? how can i set the correct premission under cygwin?? anyone can help me?? thanks :)

i try the Quarx build from this topic

http://xdaforums.com/showthread.php?t=1663613
[Android Software/Hacking General [Developers Only]] CaptHilts:
Galaxy S2 Gt-9100 cm7 stable

hey, first of just wanted to thank you (developers and everyone around) for this awesome forum and help to make the best out of our phones!

now, i've been trying to patch the stable version of CM7 for the galaxy 2 (2012-06-16 00:01:46) with pdroid and tried about everything, with two results:

up to v. 63 (included one or two of the earlier versions) of the auto-patcher i managed to patch the files (meaning no error msg yet reading the log file not sure sth got patched actually) and then i get a bootloop. With all the newer auto-patcher versions i get error messages. I'll include the log file from v. 63. Is there a way to fix this?

As for my system, i'm on Arch with everything relevant installed to patch the files.

Cheers

captn
[Android Software/Hacking General [Developers Only]] CaptHilts:
OK i figured it out: created a working patch for CM7.2 stable for the S2 without bootloop. The problem is PDroidPatcher v.1.32! I booted into windows in a VM and first tried PDroidPatcher v. 1.32 - patching was successful but when applying the patch it created a bootloop. Then tried PDroidPatcher v1.31. Boot time took a bit longer than usual but it actually works. Installed PDroid and everything works as it should (even though i still lie under the impression that it takes a little longer to boot than before).

Hope that helps to sort out the bootloop problems for those interested in CM7.2 stable. Of course it would be awesome if linux users don't have to boot win in a VM ;)

Cheers

Captn
[Android Software/Hacking General [Developers Only]] brashmadcap:
Jelly Bean

Still no Jelly Bean support? Are you looking into it? Please let me know if I can help.
[Android Software/Hacking General [Developers Only]] mateorod:
"Still", huh? Considering my pre-order of the first device with native AOSP hasn't even shipped yet, "still" seems a little presumptuous.

There are some hard-coded challenges to bringing it to AOSP JB. It is not being ignored, but neither does it occur by magic.
[Android Software/Hacking General [Developers Only]] pastime1971:
The number of framework.jar limit is giving me headache when i compile the whole rom.

Will keep trying, but needs someone with a deep knowledge of android system... :(

FYI, source-patching itself seems to work. (Needded a few tweaks) Just rom is not ready.
[Android Software/Hacking General [Developers Only]] brashmadcap:
My bad, not sure why the word "still" went in there. Super presumptuous and likely a result of my valium intake last night. Thanks for all your work, we all appreciate it. Sorry to have put it like that, didn't mean for it to sound like that.
[Android Software/Hacking General [Developers Only]] mateorod:
Jelly Bean update

Ahh...I shouldn't be so touchy. Thanks for the kind words and we are working on it...I want it up as much as you do, but patching AOSP has some serious road blocks in the framework.jar. AOSP is right up against the (arbitrary, from what I can see Edit: pastime says it is a java issue, which would make some more since as well as explain why it seems to require so much work to completely fix it instead) method cap and adding the PDroid build patches pushes it over. Steve Kondik already filed a bug report on it and posted a bit of a hacky temporary patch which will be how CM gets past the cap.

Which is fine, and means that we will likely have no trouble patching CM10 and AOKP. But the patch, if you look, splits the framework.jar into framework.jar and framework2.jar. Which is ok, but I don't think we'll be able to create a framework2.jar out of whole cloth using smali patches.

So as of right now, the only way to patch AOSP would be for us to make some serious executive decisions about which methods in AOSP framework.jar our users could live without. Which would be pretty presumptious of us, not too mention a bunch of hard work we may or may not be up to.

It looks like Google just became aware of the issue the other day (how they could miss this is beyond me, the whole idea of Android is that OEMs and users can expand the code, this effectively prevents a bunch major changes to the tree without the framework split patch) and so we can hope that they push a change for the next update. I would like to think that they will, but it all depends on how much of a hack the OEMs think framework2.jar type solutions are. Some ROMs have obviously done this for ICS, so Google may just let it ride. If they do, we may never have a smali patch for AOSP Jelly Bean.

Unless any of our users have seen any solutions, or have any ideas? Keep in mind that any solution isn't so much the build (although AFAIK we don't have a PDroid JB build yet. I going to work on it today) but that we need a smali patch. We'll see where we are if I can get a build out.

On the positive side, I have a (somewhat) working build of CM10 done, although without the PDroid patch applied. It has all the bugs of the current CM10 tree (along with some extras lol) but we should be positioned to have a patch fairly concurrent with whenever the first zips go out...

Any suggestions welcome.
[Android Software/Hacking General [Developers Only]] bigbadmoshe:
PDroid Patch For Sensation badosp-experimental-1.1.9084

i want to thank you and those who made the cygwin tuts. they worked in the end:)

xdaforums.com/showpost.php?p=28974738&postcount=308
[Android Software/Hacking General [Developers Only]] mateorod:
Looks fine to me. The update.zip outputted by our program simply overwrites a couple system apps. So if anyone flashes an update.zip and gets bootloops or FC's the solution is easy. Simply reflash your ROM, no need to wipe any data or restore anything.

Since it just involves system apps, there isn't really anyway to cause any damage to your install, a reflash with no wiping gets you right back to how it was, data and settings preserved.

But those ignored hunks shouldn't be an issue. That just means you had a couple files that were already in the shape they needed to be for PDroid to work.
[Android Software/Hacking General [Developers Only]] mateorod:
A new version with updated patches for CM7/CM9 has gone up, 20120718v101.

I am actively looking for some new mods to add to the Auto-Patcher. There are some other changes possibly in our future as Pdroid support for Jelly Bean is being worked on.

If you see something neat that involves apktool or and other compliling changes, send us a tip. We can even work with source changes, to a degree, so keep your eyes open.