yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Urinophoria:
[MENTION=3040425]takota6[/MENTION] Did any of that work out for you? If you tried something else and it worked, please share. No character assassination or judgement here; the whole point is to put these tools in everyone's hands. If it's working for you, please let us know-with as much detail as possible. The words you write may help the next guy; by either 1) helping us make it easier or 2) illuminating a functional process that has little to do with actual development, but provides valuable insight as to how the end-user interacts.

And thanks in advance for spending the time, it's much appreciated.
[Android Software/Hacking General [Developers Only]] wurzel555:
Hi,

unfortunately the patch file produced for the Samsung Galaxy 10.1 P7500 does not work. it flashes fine but once the system is up the SystemUI stops working and all you get is the constant popup telling you so. everytime you press OK it pops up again and the only way to get rid of it is to reflash the ROM zip file or the restore file also created.

I used these versions to create the tabletUI patch.

cm-10.1-20130812-NIGHTLY-p4.zip

cm-10.1-20130813-NIGHTLY-p4.zip

and got this output from the patcher which I flashed.

update-cm-p4-20130812-tabletUI.zip

update-cm-p4-20130813-tabletUI.zip
[Android Software/Hacking General [Developers Only]] DualJoe:
[MENTION=4342828]mateorod[/MENTION]:

I've successfully created the diff patch for latest Temasek rom (cm-10.2-20130814-UNOFFICIAL-i9300-V10.1.zip) following your instructions. Thanks for that. Do you want to implement it into global patchset or should we keep it internally? File is attached nevertheless.

Like you've noticed already its a different patch atm. Temasek pulled the first cherry-pick (disabled wallpaperservice - services.jar) in favor of PDroid but new errors arised (but all handled now - framework.jar). I guess he will re-implement the first cherry-pick again now so there's coming at least one more file (services2.jar) in the future (in case you want it for global patchset).
[Android Software/Hacking General [Developers Only]] mateorod:
Okay thanks. My best advice is just to stick with the slightly earlier rom that works for right now, development on 10.1 has slowed way way down so you won't be missing much.

TabletUI is maintained by Caldair, who is currently on vacation. When he gets home, I am sure he will get it up again.

No I can add it globally for now. I am working on a major update for the Auto-patcher ( I wanted to get it in for 3.0.0, but there was just too much going on) that splits the diffs up into smaller patches and will give us fine grained control over situations like this. I hope that it will basically lead to universal patches, although the jury on that is still way, way out. Later tonight I will add it to the upstream auto-patcher. Thanks for building the patch, [MENTION=4293606]DualJoe[/MENTION].

And send me whatever you guys need to get your rom working. Before auto-update, file size was a major consideration, but is less of an issue now that people only need to download it once. That leaves creating the patches as the only real limiter, and since you have made them, I am happy to just add it to the package.
[Android Software/Hacking General [Developers Only]] Mika83AC:
Out of Thanks for today, so: THANK YOU!!!
[Android Software/Hacking General [Developers Only]] DualJoe:
[MENTION=2180974]materod[/MENTION]:

Pull the temasek patch. Something's wrong with it (bootloop). I just handled framework.jar/android/provider/Settings$Secure.smali in 'framework2.patch'. After that auto-patcher runs completely but it doesn't work. I will try again.

Edit: I guess if 'framework.patch' is skipped and 'framework2.patch' is used the whole 'framework.patch' patches are not applied so i have to provide all differences of framework.jar in 'framework2.patch'. If so, no wonder it bootloops...

Edit2: I give up. I have no clue why Auto-Patcher rejects 26 out of 32 hunks even though manually patching works properly. The above patch is probably wrong due to missing first two lines (diff -Npru...) and wrong filenames in line 3+4 but i'm not sure.

I tried several other things like replacing the 'Settings$Secure.smali' part in 'framework.patch' or placing the whole framework diff (10.5MB) in 'framework2.patch' like you said but nothing worked. It seems like the file gets prepatched rendering the new patches invalid. I don't know...

In case you want to take a look i've attached the two framework.jars. The patched one is manually forged and works properly so far. Rom link and short description is included.

Maybe it doesn't make sense to support kang builds at the moment if it brakes again with every custom patch.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, that looks frustrating. I will take a peek. Generally speaking, I don't support kang builds in an Official sense, but practically they are so often barely different from upstream that we do support them. Temasek is an exception, a conscientious contributor who produces real change on his builds. So the fact that his can break is a little more likely. But I am willing to take the extra time to support his builds because he has long been a supporter of the project (he was actually working on the original thread before I even got there!) and has always taken the time to expose his users to the project.

I don't really know what you mean by "manually produced"...I actually have two different options for workarounds, one is called INCREMENTAL and that is simply a small change that is applied universally for that patch date. ALTERNATE, which is the framework2.patch structure, is applied only if detected, and is only tried if the "framework.patch" fails all of our various workarounds (too too many to list). So the framework2.patch has to contain all of the same changes as the original framework.patch.

I use this for PA telephony-common.patch, because they have the AOSPA fork as well as a "jellybean-legacy" fork they support, and the telephony patches for one are incompatible with the other. So when someone patches a PA rom, it assumes it is AOSPA and tries that patch. If it fails, it then moves on to trying the "telephony-common2.patch" instead, which was made from a "jellybean-legacy" build.

Both of those patches, telephony-common.patch and telephony-common2.patch, contain the entire OpenPDroid code set. One is simply a fallback position.

The way to see for sure if your patches are working is to try replacing the framework.patch with your patch made from temasek's build. If it patches, then it should work as a fallback if titled framework2.patch. I am using this somewhat obscure schemes as a part of my efforts to obscure all the ROMTYPE and patch date parsing from the user. I try and make all the behind-the-scenes matching be as easy as possible.

I have been working pretty hard on the new update which should make all this even easier...but we would still need a working patched and unpatched build. Are temasek's builds available to be built by me? Point me toward the manifest, if it is available. I believe we can get this licked.
[Android Software/Hacking General [Developers Only]] DualJoe:
How i patch the builds:

If i run the rom through auto-patcher it brakes with framework.jar error in android/provider/Settings$Secure.smali so i replace the smali file with the original CM10.2 nightly file taking a quick peek beforehand if it differs indeed by just the custom patches. Then i put it back into the rom and let it run again through auto-patcher. This time it finishes successfully. From the auto-patcher created file i extract/baksmali 'framework.jar' again and manually re-inject the custom patches (mostly copy&paste) and put it back into the update.zip. The resulting file/patch is linked below.

I baksmali'd and diff'ed both framework.jar's (Temasek original <> Temasek auto-patcher patched + custom Settings$Secure.smali patch) and it resulted in a 10.5MB diff file. Much more than the original framework diff (1MB). But it neither works as 'framework.patch' or ''framework2.patch'.

I took the original 'framework.patch' and replaced only the 'Settings$Secure.smali' diff part with my (Temasek-original <> Temasek auto-patcher patched + custom Settings$Secure.smali patch) diff but it rejects 26 of 32 hunks. If i manually do the 'patch' command on the smali file it works properly.

That's what i don't understand. It's only the 'Settings$Secure.smali' part that brakes the patcher and i replaced that with a valid diff but it doesn't work. These 26 of 32 rejected hunks highly remind me on the EOL issue but i tried all kind of possibilities to cover that.

That's his Github.

Thats the V11.1 rom (Mirror1, Mirror2)

That's the corresponding V11.1 OpenPDroid Patch.

Edit: I attach my work files. Not sure if they might help in any way...
[Android Software/Hacking General [Developers Only]] mateorod:
I was hoping temasek had a default.xml or a manifest to sync to...but I guess I can just use whatever frameworks I see, the rest doesn't matter so much.

Ending up with a 10.5 diff is exactly what happened to me when I was comparing your earlier 10.2 services.jar with the the 10.1...it looks to me like possibly your diff is trying to patch over every single line in one of your frameworks. If you look inside, you should see lines with plus, minus and blank line beginnings, if the diff was done right. I set up my files like this: stock-services/services-jar, opd-services/services.ajr, etc. and diff it from that level.

diff -Npru stock-services/services.jar opd-services/services.jar > services.patch

The size and text should be basically identical to all the other patches. But I will do what I can overnight. Like I said, we WILL get there.
[Android Software/Hacking General [Developers Only]] mateorod:
[MENTION=4293606]DualJoe[/MENTION], temasek framework2.patch has been built and pushed.

I think that should work for you guys. If it works and you have any questions, let me know. But all I did was quickly build the rom, then patch the source with OpenPDroid 4.3 patches. Then I decompiled and diffed, pretty quick work. The work has all gone into the autopatcher script and domain work, so it was easy (since I wrote it and know all the quirks, lol).

Autopatcherv3.0.212

Edit: I tested it before I posted, and it DOES patch V116, which is the latest temasek rom I have on hand. Whether it runs I cannot say, but we do;t really get boot loops around here.
[Android Software/Hacking General [Developers Only]] karamelos:
In your log

In your terminal see:

git pull
./batch.sh

and

./auto_patcher cm-10.2-20130815-NIGHTLY-i9100.zip openpdroid cm
[Android Software/Hacking General [Developers Only]] DualJoe:
No, sorry. Doesn't work. One hunk still fails on 'android/provider/Settings$Secure.smali' (framework.jar).

You cannot take the V116 (CM10.1). You have to use the V11.1+ (CM10.2) releases.
[Android Software/Hacking General [Developers Only]] mateorod:
Hmmm...I will look. But I am wondering if that source is available. The patches I made were made with from CM10.2 sources, changing frameworks/base, frameworks/opt/telephony, MMS and frameworks/native to temasek's CM-10.2 branches.

Edit- sorry I misspoke before. I just successfully patched cm-10.2-20130812-UNOFFICIAL-i9300-V8.zip with autopatcherv3.0.212. Could u post a log?

Edit2: I will download and test 11 and 11.1

Update: V11 and V11.1 from here are both patching perfectly with my existing autopatcher3.0.212. Are you running batch.sh if you are changing anything?

Any other temasek users want to try?
[Android Software/Hacking General [Developers Only]] DualJoe:
At least one other user [MENTION=4580014]Mika83AC[/MENTION] tested it as well but i'm on v3.0.21 only not v3.0.212 (??). I'm updating github directly (git fetch upstream, git merge upstream/master). Will look into that.

I checked my patches/rejects and it came out that the auto-patcher original smali file differed in parts from my original. I noticed that auto-patcher is using baksmali.1.4.2 whereas i use 2.0b5 :o. That's why i got 26 of 32 hunks rejected. Paid hard with wasted hours...

That should be resolution. Not tested entirely yet but will check your version first.

We are close...

Edit: Looks like you haven't updated github yet? Auto-patcher is still 15.Aug.2013 (v3.0.21) there.
[Android Software/Hacking General [Developers Only]] mateorod:
That would do it...I mistyped my password and hadn't checked that terminal again since. Sorry for all the time that wasted. It is pushed now.

Update: I thought I had updated smali binaries to 1.53...but maybe not. But I am interested in why or what is incompatible...were you making the patches in 2.0 and then plugging them into the auto-patcher with it's existing 1.4 binaries? I had a similar experience experimenting with the "-s" flag...the patches just wouldn't reliably patch, at least not as reliably as they do with the current patcher setup.
[Android Software/Hacking General [Developers Only]] IUnga:
Thanks a lot!

Now my experiments in progress.

I created patches for [MENTION=2332422]temasek[/MENTION]'s v12, v14 and ArchiDroid v2.1 without any problem. I don't have installed Android 4.3 on my phone (I don't want to use phone without OpenPDroid) and I did not tested these patches yet. Today - experimental day, I plan to test some new ROMs with new patches :)

UPDATE:

Tested.

Works perfect with [MENTION=2332422]temasek[/MENTION]'s build 14!

With ArchiDroid 2.1 don't work :(
[Android Software/Hacking General [Developers Only]] DualJoe:
Not your fault at all. Its more about playing with too many tools and versions especially baksmali binaries. I should have gotten my toolchain sorted right from the beginning.

Baksmali jumped from 1.4.2 right to 2.0 beta. Its not final yet though. I guess you updated something else (maybe aapt or apktool).

Here are some differences of generated smali code (1.4.2 <> 2.0.b5):
[Android Software/Hacking General [Developers Only]] Mandelbrot.Benoit:
I downloaded and successfully ran the auto_patcher tabletUI on a CM10.1 build for Xoom. I then went to run it on a CM10.2 Unofficial kang for N7(2013) and got the following error:

"error: failed com/android/internal/policy/impl/PhoneWindowManager.smali in android.policy.jar cannot be remedied"

I was just trying to do the tabletUI on the N7(2013).

Sorry if this has been brought up or is known. I went a few pages back but didn't see anything. The auto_patcher almost made it to the end then threw the error.

Edit: Looks like only things working for 4.3 is OpenPDroid (I shoulda read OP closer!). I'll wait for it to be updated for tabletUI. If I can help please let me know.

I guess kangs aren't supported and I totally understand. It worked on official CM nightly 10.2 and I think thats the best I can hope for. Thank for your hard work
[Android Software/Hacking General [Developers Only]] pawo99:
Hi, I was trying to patch AOSP ROM CARBON Nightly build based on Android 4.3

ROM link: http://carbon.mattman.org/mako/CARBON-JB-NIGHTLY-20130818-0235-mako.zip

I got this error log:

... apply preloaded.patch ...

!!! PATCHING FAILED FOR android/hardware/Camera$EventHandler.smali' android/hardware/Camera.smali android/os/SystemProperties.smali android/provider/Settings$Secure.smali' !!!

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

!!! error: failed android/hardware/Camera$EventHandler.smali' in framework.jar cannot be remedied
[Android Software/Hacking General [Developers Only]] IRKONIK:
Hey, me again. New Rom version of Gokussjx' PA, based on 4.3. It fails patching (who would've thought :D) but I thought that a log could be helpful, so here you go.

http://pastebin.com/d0dcPC4f

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

Cheers.

Ps: found a PC, took ages to patch. Still no luck running any distro on my phone/tablet.

Via Tapatalk 4 BETA, that, surprisingly, is free.
[Android Software/Hacking General [Developers Only]] karamelos:
Humm you omitted some part's in your command

### running ./auto_patcher pa_i9300-3.97-20130818.zip

i have same error

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

incriminate file attached smali is a torture for me
[Android Software/Hacking General [Developers Only]] IRKONIK:
Lol, actually not :). The autopatcher automatically chooses OpenPDroid, when you don't specify a patch. Also, I let the patcher choose the rom type, because it was the identical log (aosp and PA have the same error). I know, I'm lazy :D

Cheers!

Via Tapatalk 4 BETA, that, surprisingly, is free.
[Android Software/Hacking General [Developers Only]] karamelos:
oups i omitted this feature sorry for disagreement
[Android Software/Hacking General [Developers Only]] hitu:
Permission Denied

I get permission denied for almost any CM & PA/PAC ROMs. No errors are logged in the logs. Patch files when applied on the ROM, don't work. PDroid still complains about PDroid core missing from device.

Attached a screenshot of what I see during the patching process.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
You will need to run ApG as admin. I had that same problem and that was the advice I was given and all patched well.
[Android Software/Hacking General [Developers Only]] hitu:
Am on .. Windows XP .. sadly
[Android Software/Hacking General [Developers Only]] dirtyreturn:
I had gotten help from [MENTION=4418789]Urinophoria[/MENTION]. He is on win xp maybe he would help. I don't know if it would help, a couple pages back is the quick reply back and forth. Maybe.. they would help you?
[Android Software/Hacking General [Developers Only]] hitu:
I did search through the forum and I did try all the possible solution, re-creating the ApG directory, re-creating ApG in a different Drive. Everytime I get the same errors. The ROMs which did get patched earlier are also giving the same problem.

Please help..

Here are the logs: http://pastebin.com/hXy49L2H
[Android Software/Hacking General [Developers Only]] mateorod:
We don't have Carbon on our supported list. I am almost to a working copy of my next big update though, which should hopefully allow us to support just about all custom roms, at minimum. Keep your eyes here over the next week or so for when I post a test-script.

I updated the pa jellybean-legacy patches (framework2.patch.). But in between your builds and when I updated my patches, PA added another commit that broke the patches. So my patches are current, but you will have to wait until the 0819 builds from jellybean-legacy go live to use them. Whenever that guy pulls from upstream again...hopefully his next build.

Okay, I updated the patch.exe.manifest which controls what has permissions to execute the "patch" command. This is pretty hard for me to debug, I don't have a windows box. I had some super helpful users ick in time and get it working for most people with Win 7 and 8, but it might take some work from you to get XP support rolling again.

Update the scripts, then go to manual cygwin terminal and enter

./batch.sh

then try again. If that doesn't work, then enter

patch -v

and post your logs and output again.
[Android Software/Hacking General [Developers Only]] hitu:
That fixed it! Thank you!

Edit: Spoke to soon, Patching was successful however Rebuild failed. Logs: http://codepad.org/sRWk2T3b

Edit2: Well, Permission Denied again. I pulled the latest from GIT, just to identify if it fixes the above issue. Logs: http://codepad.org/zs8D8daO
[Android Software/Hacking General [Developers Only]] IT_Fan:
Hi, I use stock rom Jelly bean 4.1.2 of Note 2 N7100, which Rom type should I choose ? Thanks
[Android Software/Hacking General [Developers Only]] m3adow:
Hi guys,

i tried to patch the Chromium Rom build 8 which is basically a CM10.1. But I get an error while patching:

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

What to do? Since the Chromium ROM is slightly modded, I suspect that's the reason for it.

Thanks in advance for every answer.
[Android Software/Hacking General [Developers Only]] matrixzone:
Great
[Android Software/Hacking General [Developers Only]] karamelos:
stock ROM are not supported by auto-patcher

But look pdroid2.0 (stock support for n7100) or change ROM type
[Android Software/Hacking General [Developers Only]] IT_Fan:
ok, AOKP JB not stock JB ...
[Android Software/Hacking General [Developers Only]] karamelos:
Aosp= Android open source project

Aokp= Android open kang project

Stock if your ROM is maniples by your operator autopacher not work.

So what your ROM ?
[Android Software/Hacking General [Developers Only]] IT_Fan:
Stock Jelly Bean 4.1.2 from Samsung and yes it's not in the list so I am looking at Proid 2.0

---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------

Anyway, is it really not possible to use OpenPdroid with stock rom at this moment ?
[Android Software/Hacking General [Developers Only]] karamelos:
Nop

Sent from my .....
[Android Software/Hacking General [Developers Only]] SecUpwN:
Have a look at the alternative XPRIVACY. Maybe you find what you're looking for. :cowboy:
[Android Software/Hacking General [Developers Only]] Urinophoria:
There are very rare tw based Roms that incorporate it, but I haven't looked at one in quite some time. Should be under s3 development. It's possible but takes a helluva lot of work and a good developer.
[Android Software/Hacking General [Developers Only]] pepelillo:
Hi All.

Been using AP several months and for several ROMs in several devices, Hannspad, Ainol Aurora 2, Galaxy Nexus, and several android versions from 4.1.2. Always worked perfectly, (pdroid2 patch CM roms), but now I'm trying to patch a CM 10.1 (4.2.2) rom (openpdroid), everything goes fine till CWM recovery update install, in this step I get an error (status 7).

Also I try to patch a 4.3 rom for the same device (also openpdroid), but in this case the patching step fails and throws:

... apply framework.patch ...

Reversed (or previously applied) patch detected! Skipping patch.

3 out of 3 hunks ignored -- saving rejects to file 'smali/android/service/wallpaper/WallpaperService$Engine.smali.rej'

... apply preloaded.patch ...

GARBAGE= tmp/system/framework/framework.jar.out/smali/android/net/wifi/WifiStateMachine.smali.orig

GARBAGE= tmp/system/framework/framework.jar.out/smali/android/service/wallpaper/WallpaperService$Engine.smali.rej

... apply core.patch ...

GARBAGE=

GARBAGE=

... apply services.patch ...

... apply services-gps_fix.patch ...

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

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

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

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

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

Can anybody help in whatever this 2 cases?
[Android Software/Hacking General [Developers Only]] IRKONIK:
Another log: http://pastebin.com/KPYqbrcE

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

I hope that it helps in any way, but I am not really sure. I am just patching whatever I can find :D

Cheers!
[Android Software/Hacking General [Developers Only]] hitu:
AP from Win7

So I got Win7 installed on my Netbook.

Patching went fine, failed during .APK creation I guess. Logs: http://codepad.org/3izNfwTh

http://codepad.org/6BjeLiw4
[Android Software/Hacking General [Developers Only]] zurpher:
How to upgade ApG's Java package?

The Java version installed with my ApG installation is 7.0.60.24

The current Java version with the latest vulnerability fixes is 7.0.250.16

I hoped that ApG would automatically update to the latest Java version when it is released but this does not seem to be the case. Therefore, I would like to know how I can update the Java version installed with my ApG installation.