yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] IRKONIK:
Err... quick little question: How does this vulnerability affect ApG? It's for ApG only, and not for the system, so I don't think that it has any effect on the system.

Cheers!
[Android Software/Hacking General [Developers Only]] Mandelbrot.Benoit:
I can patch the most current official CM10.2 nightly (from the 21st) for N7 (flo) but NOT when I run the tabletUI patch. It keeps giving an error when patching the framework-res.apk.

I attached log, not sure if it will help?

Edit: same error for nightly from 23rd. Just tried it
[Android Software/Hacking General [Developers Only]] IRKONIK:
If you would've read the OP you might know why ;)

The only mod for 4.3 is OpenPDroid. More a coming soon, AFAIK.

Cheers!

PS: Doesn't ParanoidAndroid use a layout switcher, so that you can use the tabletUI? Might worth checking out :)
[Android Software/Hacking General [Developers Only]] Mandelbrot.Benoit:
Lmao! Thanks. I'm one of those a-holes that need to be told no matter how many times I read OP.

What throws me off is that it worked on the 16th build and hasn't since.

I will wait for the OP to be updated.

P.S. I will try PA. Team EOS was my sole ROM for tablets but looks like they dropped off.
[Android Software/Hacking General [Developers Only]] IRKONIK:
I wouldn't say a-hole, but a little lazy. :P

PA is the rom to go. I use it on all of my devices, since all their features perfectly suite my needs. Also I can make both devices look exactly the same, which adds a nice touch. (nerdgasm)

With a little patience, life gets so much easier. :D

Cheers!

Ps: I really need a new phone. But all new ones are sh!t. Anybody "knows" any upcoming devices?

Via Tapatalk 4 BETA, that, surprisingly, is free.
[Android Software/Hacking General [Developers Only]] Caldair:
Thanks for the report!

And, despite what you've been told, CM10.2 is patchable for tabletUI. It was just temporarily broken. Thank you for posting the log and making it easy for me to see where.

It should be fixed now if you want to try again. Just make sure your patcher updates with today's commit.
[Android Software/Hacking General [Developers Only]] Mandelbrot.Benoit:
But like I had stated I have read the OP many many times and Lazy is something I am not!

I flashed PA for flo and it looks like there is only one build that is flashable with a few bugs and little support yet. I do like the tablet integration compared to what the auto_patcher does so I may stick with it until EOS gets a 4.3 ROM out.

And I don't like the tablet look on my phone. Euroskank CM10.2 kangs run great on my phone!

The only up coming phone is the LG G2 which should be Nexus 5 base or Nexus 4 by Moto.

Glad I could help! I'll try it on the next release. To much flashing for one day.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Lol, couldn't help it :) all in fun :angel:

Broken at my end too, I'll build a new patchset and have them on Mateorod's desk for him to pull when he wakes up in the morning.
[Android Software/Hacking General [Developers Only]] flat__line:
sorry for blindness but

I cannot find a download link for version 3.0.0 supporting CM10.2 in th OP: can someone help me?
[Android Software/Hacking General [Developers Only]] karamelos:
https://github.com/mateor/auto-patcher
[Android Software/Hacking General [Developers Only]] Urinophoria:
20130824 patches are up for Slim. Go ahead and update and patch away.
[Android Software/Hacking General [Developers Only]] zurpher:
How does Java vulnerability affect ApG?

Are you sure? I am not. Therefore, I want to get an opinion about this vulnerability by someone who knows how ApG interacts with Java and whether this vulnerability applies.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Well, I hope you did not try to insult me here, but nevermind.

When I used ApG for the first time, it downloaded cygwim, java, etc. and installed it into the ApG-folder. (~ApGPackages/Java/ and ~ApGPackages/cygwin/) The java version I was using at that time did not change, the files in the ~Program Files/Java/ did not change, aswell as the settings. So I took myself the freedom of thinking that ApG does not use the files in the system, but the specifically downloaded ones.

If I am wrong on this point, I am truly sorry, but then I would like to have an explanation why ApG needs to download those files :)

I am smart enough to preceive an error and I would love to get it explained, if the way I thought it worked is wrong.

Thanks :D
[Android Software/Hacking General [Developers Only]] theCroh:
I get this error http://codepad.org/Lb18Es9K when trying to patch today's CM Nightly for GT-i9100 (cm-10.2-20130826-NIGHTLY-i9100).
[Android Software/Hacking General [Developers Only]] pawo99:
Hi, I got error when I wanted to patch latest CM 10.2 from 08/26 for mako - nexus 4.

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

ROM URL: http://get.cm/get/jenkins/39490/cm-10.2-20130826-NIGHTLY-mako.zip
[Android Software/Hacking General [Developers Only]] Aaron Camp:
I am trying to add TabletUI to the nightly's (10.2) for my Nook HD+ (Ovation). I have ensured that I have gotten the latest updates with APG. I am still getting a successful run of APG but the patch gives me the dreaded systemUI error if I apply it.

I did note your above post and noticed that the last item in the CHANGELOG for APG is from 2013.08.12. Is there something I am missing to get the updated commit you mentioned?

Thanks
[Android Software/Hacking General [Developers Only]] SirGeraint:
+1 (on a CM10.2 based ROM on the Samsung GS3).
[Android Software/Hacking General [Developers Only]] fierogt42:
+2 ib CM 10.2 for the Pyramid (Sensation 4G).
[Android Software/Hacking General [Developers Only]] Caldair:
Thanks for letting me know! Things are happening fast in the CyanogenMod world these days and that makes it hard to keep up with patching their work.

It should be fixed now, if you want to try again. I have made a little change to this particular part of the patch which will hopefully prevent the very frequent breakages that have been happening over the last month or so.

Make sure ApG updates, I didn't add to the changelog, so the most recent item is still the one you mention above. To be sure, you can open up the auto-patcher script itself and look at the lines immediately after CHANGELOG. The item, PATCHES_VERSION should be ="20130826". If not then you're not up to date.
[Android Software/Hacking General [Developers Only]] Aaron Camp:
That worked!! Thank you solo much. Been waiting over a week to get this working! I love the cm community and the quick responses!!!
[Android Software/Hacking General [Developers Only]] Urinophoria:
I see the broken CM openpdroid patches, working on it now. I'll post up when they're in and ready. Thanks all!
[Android Software/Hacking General [Developers Only]] SirGeraint:
Thank you!!!
[Android Software/Hacking General [Developers Only]] Urinophoria:
He already had some built, pushed his about 5 minutes before I pushed mine, lol!

Any road, CM10.2 should be patching fine now, update and hit it guys!
[Android Software/Hacking General [Developers Only]] SirGeraint:
Hmmm, not sure about everyone else but it didn't work for me. I have attached the log file.

I hope this isn't off topic but how hard is it to build openpdroid into a CM10.2 ROM? Like if I were to get everything set up to build CM10.2 ROMs?
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry for the long gap between posts...I have had my head up the next big update for the Autopatcher.

I am uploading a test package...if you are willing to test POSSIBLY NON-WORKING alpha-software, this can replace your current auto-patcher directory Just delete the existing auto_patcher and place this one in its place. This will probably only be useful to those patching on the command line. If you use ApG, you can try, but you will break the ApG updater and may have to delete your entire autopatcher directory to get back on the "master" branch. Which is fine too, I guess. Let me know.

If you use this package, you will still be able to get auto-updates, but it will be updating the experimental '3.1' branch. Okay?

Autopatcherv3.1.0

(only supporting OpenPDroid right now as we test)

ROMTYPES (cm, aokp etc) are DEPRECATED. No more worrying about the romtype.

Change from JAR.patch to SMALI.patch

All patches use new EXHAUSTIVE, the patches will try every patch we have when encountering failure

Looks like all SlimRom, ParanoidAndroid and CM roms are patching, at least. Let us know what happens and if you want support, ask your rom's developer for a default.xml.

Essentially, we are switching from "framework.patch" to "CdmaServiceStateSmali.patch", trying to patch smaller units than just entire decompiled jars. And every patch is available for every rom. Forcing ROMTYPES on the command-line is still possible, but now, if you try and patch a CyanogenMod rom with AOSP patches. it will still work.

This adds a couple of really big changes for us. I contend that there are not too many actual changes to these low-level files floating around. And now that every patch is available to every rom, I am willing to try some things to see if I am right.

So for this experimental time period, we are going to try to support EVERY OPEN-SOURCE rom. If your rom fails to patch, please upload your log file, a link to the rom, and VERY IMPORTANT, I need a link to the rom's sources. If it is hard to build or a pain to find, I will probably not be able to help. Ask the ROM's developer to help you, ask for a default.xml or manifest. If they won't/can't give you one, then they are not open-source and we cannot help you and you should get a new rom dev!

This is a big undertaking, and the first order of business is to simply get this new patching process tested. So please give it a shot and let me know how it goes. Autopatcher3.1.0 is very far from it's current form, but it seems to work for me, now it needs some testing. Anyone want to try it?

Autopatcherv3.1.0-TEST.zip

HUGE thanks to [MENTION=4261245]a3955269[/MENTION] who sent in asome new ideas and scripts that spurred many of the changes in this update. Also [MENTION=1449163]Caldair[/MENTION] and [MENTION=4418789]Urinophoria[/MENTION], who have both been working hard maintaining and improving the Autopatcher and getting me time to work on this. Caldair got featured on the portal the other day, pretty cool!
[Android Software/Hacking General [Developers Only]] karamelos:
Hi [MENTION=4342828]mateorod[/MENTION]

some trouble with test version log is attached

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

With [MENTION=4418789]Urinophoria[/MENTION] git it's ok patch is successfully apply
[Android Software/Hacking General [Developers Only]] mateorod:
I just saw that perhaps my CM10.2 patches were flawed. I switched to the ones that [MENTION=4418789]Urinophoria[/MENTION] built and they seem to work liek a charm! Thanks man.

Both the regular Autopatcher and the test.zip of 3.1.0 should be able to pull the updates through auto-updating, so go to it. If you were having any trouble with PA, I am pretty sure all PA roms are patching well in the 3.1.0 test zip linked above.

Edit: and building your own OpenPDroid rom is easy, if you have already built a rom before. Complete instructions at the OpenPDroidPatches repo README.
[Android Software/Hacking General [Developers Only]] tftd:
I'm having a strange problem with the 20130824 openpdroid patch. When I apply it and reboot my Galaxy S2 i9100 (international) the phone gets to the cyanogenmod boot loader and doesn't continue. It stays at the booting animation forever. If I apply a "restore" or re-flash the original cyanogenmod everything works fine. What may be the cause for this? What info do you need me to provide and how? (I don't know how to get the logs)
[Android Software/Hacking General [Developers Only]] viulian:
I was using 2.6.0.2 version to patch the cm build for my S3 and it worked ok until another build came up : cm-10.1-20130711-EXPERIMENTAL-i9300-MEMCPY.zip where it would fail with error:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I decided to use the version 3.1.0 which correctly generated the build files - I'm about to flash it!

However, one problem in the auto_patcher script, I had to replace the

# ROM_NAME=${ROMX##*/}
ROM_NAME=cm-10.zip

since the update / restore file names ended up looking like:

update-openpdroid-C:\OPENPD~1\CM-101~1.ZIP

So apparently the new code instead of using the rom filename, it is actually expanding it to the full windows path (using antique short names) and generates a new file name which is invalid on Windows 7. I had to put the ROM_NAME to something simple and without the path, and then it worked!

Thank you, trying it now :)
[Android Software/Hacking General [Developers Only]] rockingwing:
Just wanted to patch the 10.1.3 RC1 CM rom for p5110, needed tabletUI but it failed to patch SystemUI.apk

http://codepad.org/wi5syVXu
[Android Software/Hacking General [Developers Only]] takota6:
Big request, Im a past pdroid user but have issues building. But if someone is setup could you build this carbon/cm patch please

http://pio-masaki.com/?dir=DroidDNA/Carbon

I'm needing the 20130826-dlx-CDMA-.zip..

Thank you from high in the rockies
[Android Software/Hacking General [Developers Only]] pawo99:
Hi, I want to add openpdroid patch to carbon, but it finished with issue. I used latest 3.1 autopatcher.

!!! error: Settings$Secure.patch in framework.jar cannot be remedied

link to ROM sources: https://github.com/CarbonDev
[Android Software/Hacking General [Developers Only]] Christoph21x:
Sorry, patching failed in various configurations.

Greetz back from Swiss Alps to the Rockies ;)

Chris
[Android Software/Hacking General [Developers Only]] mateorod:
Sure CarbonRom is a perfect candidate to be patched in the 3.1 update. It mostly uses CM files, so we should have most of the patches already built. I will let you know tomorrow when I upload the patches to the 3.1 branch to test.

I will give testing instructions then. If this works for you, we will think about merging 3.1 into master.
[Android Software/Hacking General [Developers Only]] mateorod:
EXPERIMENTAL Autopatcherv3.1.1 is available for DOWNLOAD at my goo.im page

This has Carbon rom support, and looks to work well to me.

Note: This is NOT the master branch. If you have not manually downloaded the 3.1.0 or 3.1.1 package, you will not have these patches.!

Just download the package and either patch manually, or maybe you can replace the autopatcher directory in ApG. I don't know about ApG, I haven't used it yet. But if you run the autopatcher on the command-line this package works. It is set to auto-update as well, so if I push new patches, you do not have to redownload this package...if you are already testing Autopatcherv3.1.0, you do not need to download again, it should update when you run the program.

I am having a conversation with someone on Github who is having an issue with 3.1.0 and the shell expansion. I have not been able to reproduce it. If it affects you, you will know because the script will now error out. Please upload you logs in that case.

If you are using the 3.1 branch with success, please let us know. I would like to begin migrating it to master branch for everyone to use. If you want a open-source rom supported, post a link to the source code!
[Android Software/Hacking General [Developers Only]] bladerunner1964:
Special Thx. It works
[Android Software/Hacking General [Developers Only]] pawo99:
Thank you, I have manually patched latest Carbon, now I'm going to flash it. I'll report later.

BTW: Patching via ApG working only in manual mode...

EDIT: If I've flashed update-openpdroid-CARBON.zip phone stuck at bootanimation. After flashing restore-from-openpdroid-CARBON.zip it works fine. Here is logcat generated via adb when phone was with stucked bootanimation.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks for the logcat. I recognize the symptoms...which is essentially that it thought Carbon was AOSP based instead of CM based. Those ar the two bases we tend to work with at the moment. Could you post the autopatcher log as well please? I will look at this tonight. I have some idea of where we are with it, but you are guys are basically the first people testing the new implementation.
[Android Software/Hacking General [Developers Only]] pawo99:
I've uploaded autopatcher log in my upper post. :fingers-crossed:
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I believe that I have fixed it..turns out Carbon roms were a little more unique than I thought, It should update to 3.1.15 and work now.

Thanks for the logs, they really really help!

I am also uploading a 3.1.15 package to the download page, but hopefully if you have downloaded any 3.1+ package, it should update when you run it :)
[Android Software/Hacking General [Developers Only]] pawo99:
now we have working openpdroid patch on Carbon :good: thank you!
[Android Software/Hacking General [Developers Only]] takota6:
Great work, neat how the intelligent get together to problem solve

.. me I still missing the picture

APG goes on the root of c:? Because the op reads (do not) but something I'm missing.. I'm away from my CPU, so I would request some1to build this for me

http://pio-masaki.com/?dir=DroidDNA/Carbon

* CARBON-UNOFFICIAL-20130829-dlx-CDMA.zip...thanks and no hurries

Æaa.\„/
[Android Software/Hacking General [Developers Only]] pawo99:
Try this:

Here is uploaded update_openpdroid for your ROM: https://app.box.com/s/85axyfvtzam9nhgncxpl

restore: https://app.box.com/s/zbjsht38k8o50glsageu
[Android Software/Hacking General [Developers Only]] bustedwings:
Patching latest slim 4.3 beta 4 for d2att. patch fails. here is the log

http://codepad.org/W5t0bPiL

as always thanks for your hard work and dedication.
[Android Software/Hacking General [Developers Only]] mateorod:
New patches for SlimRom pushed to both the regular Autopatcher and the experimental 3.1 branch.

All systems seem to be working for the 3.1 branch...I intend to finish bring all the mods up for Android 4.3 and finish the 3.1 branch support for apks (to support tabletUI and v6supercharger for instance) and hopefully merge the 3,1 changes into the master branch early this week.

If you are already trying a 3.1 package, I can merge you into the master project through our auto-updater, no need to replace your autopatcher directory again.
[Android Software/Hacking General [Developers Only]] mfc719:
New Slim causes bootloop on Beta-4. Used autopatcher.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks. I will check it out. Which autopatcher...could you please upload the logfile?

Edit: nvm. I think I have found and fixed it on both master and 3.1. Should be fixed now, we had a silently failing issue. TabletUI and v6supercharger may be working for 3.1 branch now as well.
[Android Software/Hacking General [Developers Only]] mfc719:
Thanks... That was quick. Worked fine. Should note as well, when bootlooped, restore file worked perfect. Keep up the good work.
[Android Software/Hacking General [Developers Only]] creedicd:
PA 3.99 Patching Fails

Awesome Product you guys make. Thank you for your time and effort!!!

Similar to the post a few up am also getting an error while patching PA 3.99

Here is the log http://codepad.org/qjke9s4Q
[Android Software/Hacking General [Developers Only]] mfc719:
Quick question, if I flash a different kernel, should I flash the restore zip first to avoid any problems? Or will the patch hold up through the new kernel?
[Android Software/Hacking General [Developers Only]] mateorod:
Okay...it looks like that is patching on the new 3.1 experimental build. If you are feeling adventurous, I would recommend giving it a shot. It won't break anything reflashing your rom won't fix, and it looks like it patches your rom on my test. It will be getting pushed to all the users sometimes early this week, so give it a shot and let me know how it goes, ok? You can get it here.

The only mods that touch the boot.img are pdroid/opendproid/pd2.0 for Android 4.1.2 only and insecure/secure which just change the security level of your boot.img. But even then, most kernel devs use EasyKernel installer, which parses the ramdisk and leaves our mods alone.

So no, it should be fine in almost every situation :)
[Android Software/Hacking General [Developers Only]] IRKONIK:
Log: http://pastebin.com/sbs11z2h

Rom: http://xdaforums.com/showthread.php?t=1745003

I hope it helps :)

Cheers!
[Android Software/Hacking General [Developers Only]] mateorod:
Try the auto-patcher 3.1 linked above. It is a separate branch that I developed exactly for these situations. I am certain your rom will patch...but PA has not generated any feedback yet. I hope to merge this branch to master very soon, perhaps you could download the package and check.it.out for.us.
[Android Software/Hacking General [Developers Only]] IRKONIK:
Argh, I have the feeling like I'm brain dead. I don't get it to work. I just download it and extract it over the auto-patcher folder. Or am I missing something?

Via Tapatalk 4 BETA, that, surprisingly, is free.
[Android Software/Hacking General [Developers Only]] meduza:
[MENTION=3433885]kobik77[/MENTION],

I just used your great fool proved tool to patch a tablet UI at JB 4.3 on my liberty tab(=a500). It worked like a charm!

Thank you very much!!

m.
[Android Software/Hacking General [Developers Only]] xFluffyx:
Galaxy Nexus CM10.2 still an error:

cm-10.2-20130902-NIGHTLY-maguro.zip

http://codepad.org/vbWq3841
[Android Software/Hacking General [Developers Only]] 0.0:
I am unable to update to the latest source. log is attached

I have tried git add auto_patcher and git commit, but that doesn't work. I am using 3.1.0

ROOT= /Users/Micah/Downloads/autopatcherv3.1.0/.
TOOL= /Users/Micah/Downloads/autopatcherv3.1.0/./patch_tools.tgz
ROM= /Users/Micah/Downloads/autopatcherv3.1.0/update
ROMX= /Users/Micah/Downloads/autopatcherv3.1.0/update

### checking for updates ###

... Updater: update found ...

... backing up auto_patcher to auto_patcher.bak ...
auto_patcher -> auto_patcher.bak

... Updating Auto-Patcher ...
error: Your local changes to the following files would be overwritten by merge:
auto_patcher
Please, commit your changes or stash them before you can merge.
Aborting

### Update failed ###

It appears you may have made some changes that prevent automatic updating.

You could run 'git reset --hard' to return the autopatcher to its original form

or set AUTO_UPDATE to false in the .config file to stop getting this message.

If you have a failed patch for your rom, please upload your log to the XDA support thread.

If your rom is not on the supported list and you want it added, please:

- Upload your log to the XDA support thread

- and ask your ROM's developer for:

- manifest (default.xml is the best/quickest)

- or at least a link to their sources

Post both to the (UPCOMING...use thread for now) and be patient, please!
[Android Software/Hacking General [Developers Only]] pawo99:
Hi, I wanted to patch latest cm-nightly for mako with openpdroid, but it finished with error.

!!! error: There was an unhandled error! Please submit your log!

I have used 3.1 branch.of auto_patcher.

ROM: http://get.cm/get/jenkins/40349/cm-10.2-20130903-NIGHTLY-mako.zip
[Android Software/Hacking General [Developers Only]] karamelos:
In terminal (in your directory):

git reset --hard

./batch.sh