yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] IUnga:
I have a next fault log

fot temasek's build

Any help appreciated
[Android Software/Hacking General [Developers Only]] jahrule:
Any one have this working for 6.8 build of slim?
[Android Software/Hacking General [Developers Only]] Caldair:
Yes. But I had to use Slim's own apktool.jar and aapt from here. Those guys seem to work fine for other roms too, but the aapt is massive for whatever reason (see: "the real dark slim").
[Android Software/Hacking General [Developers Only]] adavit:
Just wondering if there has been a change in CM recently that broke the patch again? I was able to patch flyhalfs previous CM build from 6/21 (I think) and then when I tried to patch today's build it fails. Hopefully I added the log correctly. Log
[Android Software/Hacking General [Developers Only]] synxx:
deleted
[Android Software/Hacking General [Developers Only]] Urinophoria:
Are you trying the 6/24? I don't see one for 6/25 yet, just want to make sure. If you got a 6/25, could you link it so I can get at the one that's not working for you?
[Android Software/Hacking General [Developers Only]] jahrule:
Download the apktool install Linux 1.5.3 from link provided and replaced the tools in zip but still no dice. I replaced after they downloaded as well.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Which OS are you trying to patch from? Ubuntu 12.04, autopatcher worked for me for 6.8 (d2att).
[Android Software/Hacking General [Developers Only]] adavit:
There's a 6/25 build posted in the thread, but here's the link where I got it from, its at the bottom. http://vp-zp.com/snuzzo/roms/flyhalf205/cm10/
[Android Software/Hacking General [Developers Only]] Urinophoria:
Yep, it's broke in the 06-26 official too. Just tested both.

Starting the builds.
[Android Software/Hacking General [Developers Only]] adavit:
Thanks for checking :)
[Android Software/Hacking General [Developers Only]] Caldair:
Weird, I am on Ubuntu 13.04 and for me without the apktool.jar and aapt I linked above the framework files needed by apktool are not properly decompiled and the patcher fails. Or did you need to use the files from Slim's Github as well?

Yes, as Urinophoria asked for, more information would be really helpfull (including logs, etc).

To be more clear on my end, I put the apktool.jar in patch_tools.tgz, and aapt in patch_tools.tgz/linux in my patching directory (not in the autopatcher.zip). And, like you said, after making sure auto-patcher had updated first.
[Android Software/Hacking General [Developers Only]] jahrule:
I am also on 13.04 and even when I replaced apktool.jar and aapt you linked I still can't get it. Could you give a step by step what you did? I have been patching pdroid since gingerbread but yea...
[Android Software/Hacking General [Developers Only]] Urinophoria:
I just downloaded the zip from the website, dropped it into the autopatcher directory and ran it. I left out ROM designation and let it figure it out for itself, but that's about the only thing I did that departed from the instructions.

Maybe run ./batch.sh after it updates? That was the last really good mistake I made with auto patcher. Forgot to run batch.sh and everything was breaking for a while.
[Android Software/Hacking General [Developers Only]] jahrule:
Would it make a difference that I am trying to patch a linaro toolchain built slim?

Did both of what you all said and still get the same error.

Error: failed android/content/AsyncTaskLoader.smali in framework.jar cannot be remedied

Edit: this is the ROM I am trying to patch https://plus.google.com/communities/107891541077154929804
[Android Software/Hacking General [Developers Only]] mateorod:
I need to add this to the OP, but anyone looking for support, Urinophoria has joined the autopatcher team.

Thanks for taking the breakage report, Urinophoria. I am going to do a brief write-up of how to read the logs and will add it to the wiki this week. I am interested in this apktool discussion for sure. Caldair, I just updated the apktool last week with a build I made straight from the apktool source. This included a pull request from the SlimRom team that I believe was sent to make all apktool compatible with their new TRDS2.0 structure.

Some tests are needed, comparing a decompile of some apks with the autopatcher build of apktool and then the SlimRom build.

I did not update the aapts...maybe that is needed? I can look into that personally.
[Android Software/Hacking General [Developers Only]] karamelos:
Hi mateo

i try to patch rootbox for n7000

but fails

The Auto-Patcher v2.9.878

### 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= aosp ...
... Using results of ROM check ...
... openpdroid patch date has been set to: 20130213 ...
### unzip rom ###
inflated: system/app/Mms.apk
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: system/framework/telephony-common.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
... decompile telephony-common.jar ...
... installing framework files ...
Exception in thread "main" brut.androlib.AndrolibException: Could not decode arsc file
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:54)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:40)
at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:611)
at brut.androlib.Androlib.installFramework(Androlib.java:469)
at brut.apktool.Main.cmdInstallFramework(Main.java:260)
at brut.apktool.Main.main(Main.java:81)
Caused by: java.io.IOException: Expected: 0x00000008, got: 0x00000000
at brut.util.ExtDataInput.skipCheckShort(ExtDataInput.java:56)
at brut.androlib.res.decoder.ARSCDecoder.readValue(ARSCDecoder.java:219)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:179)
at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:167)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:133)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:108)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:81)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:49)
... 5 more
... decompile Mms.apk ...
### copy patch openpdroid/4.2/aosp/20130213 ###
... copying system/media/PDroid.jpeg ...
... overwriting system/media/PDroid.jpeg from openpdroid ...
### jar patch openpdroid/4.2/aosp/20130213 ###
... apply framework.patch ...
... apply preloaded.patch ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/content/AsyncTaskLoader.smali in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

So i build it

I make diff patch but not sure for the result (some trouble with telephony-common patch)

Attached some patch file

framework.patch
[Android Software/Hacking General [Developers Only]] bululu:
tried to patch for Samsung Galaxy S Plus i9001

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

but it fails:

http://codepad.org/ea8iB3Rk#comment-F4p5Mq5a
[Android Software/Hacking General [Developers Only]] Urinophoria:
Another 10.1 CM ROM. CM was broken as of 6-25. I just sent Mateorod new builds about 30 seconds ago. :D :cowboy:

---------- Post added at 08:24 PM ---------- Previous post was at 07:57 PM ----------

New patches for CM10.1 pushed. Apg users, use your update feature; 'Nix users, auto update should work.
[Android Software/Hacking General [Developers Only]] adavit:
Got impatient waiting for the new patches to show up in Apg (showed up under patches, but didn't show up in the update plus auto patcher was using patches from 5-16) so I manually patched using the 6-26 patches. Seems to have worked wonderfully. Thanks so much!
[Android Software/Hacking General [Developers Only]] Caldair:
I knew you updated the Apktool, that was why I was so excited to try it out on Slim, which had issues patching since build 6. But no luck out of the box. The errors are different than with Auto-patcher before you updated Apktool, but they still bring patching to a halt.:(

I played around a little with the peices of this puzzle and have attached 4 different Auto-patcher logs, hopefully their names are explanatory enough.

The Apktool which is in Auto-patcher does not decompile any of the framework files at all. If I remove the cleanup commands from Auto-patcher so i can inspect the temp directories, both SystemUI.apk.out and framework-res.apk.out are completely empty. That is why in the 2 logs using the included apktool all the patches fail for those 2 files. Slim build 6.8 patching is only successfull for me when using both apktool and aapt from Slim source.

[MENTION=4576904]jahrule[/MENTION]: I downloaded your rom and it failed with my setup too. But openpdroid patches successfully for the slim for my p3110 from slim's site.
[Android Software/Hacking General [Developers Only]] adavit:
Here is the log provided by the auto-patcher: Log

If there's any other kind of log you would need please let me know (and possibly what I would need to run to get said log). Idk why, but it won't show the update in apg, the last update it shows is from 6/22, but yet if you search in the patches folder it has the patches from 6/26 so idk what's going on lol. Thanks for the great work though :)

Edit: I've also tried changing the patch that gets used in the settings to the 6/26 but it still ran as the 5/16 (I saved after switching this), so I changed it back to the default "latest".
[Android Software/Hacking General [Developers Only]] Caldair:
Thanks Mateor. The tabletUI patches do patch some values in framework-res.apk, most of them are just tweaks to the appearance of the dual pane settings panel, but the one is necessary in bools.xml to enable all rotations. The stupid thing is that in about half the roms I have seen this value is already set to true and the patch is skipped anyway. But for that other half it is necessary to achieve tablet UI.

I was thinking on the weekend about suggesting to you that we switch to the Slim sourced tools, I tested patching almost every rom-type that the patcher supports with them to be sure it worked, and it did. I even wrote you half a pm before i decided against the idea, just because of the size of the aapt, which is over 5 MB (x3!). And because I didn't know if it would even be possible for windows or mac. In the end I just decided to share how I got it to work in the Tab 2 forums so users could patch slim if they wanted, and to take a wait and see approach, to whether slim roms might fall back in line with the rest in future builds.

Whatever you decide is best to do or not do with this is good with me! I wonder how many other slim users are out there anyway...
[Android Software/Hacking General [Developers Only]] jahrule:
Could we get a slim working autopatcher?
[Android Software/Hacking General [Developers Only]] IUnga:
Also today I have a error for this build (temasek)
[Android Software/Hacking General [Developers Only]] Scuppa:
Tried to patch tabletUI to CM 10.1 for p3110 but failed: http://codepad.org/fIcGWNIx

Thanks for your help!
[Android Software/Hacking General [Developers Only]] Finitesimal:
The fix for the error in the latest version (2.9.87) line 1172 is to insert a space between the "&" and the ">>".

EDIT: One other thing: SlimRom support would be absolutely awesome!
[Android Software/Hacking General [Developers Only]] Dexxmor:
Slim Rom is supported, or you mean tablet ui?
[Android Software/Hacking General [Developers Only]] Urinophoria:
Was wondering about that too, I've run several different builds of it through the autopatcher and (at least for openpdroid) it was working fine.

Otherwise I would have been peppering mateorod with more new builds, lol!
[Android Software/Hacking General [Developers Only]] KingKuno:
Hi, i have a big issue.

A friend write me a message (sms) and I want to write something back and I cant do it because there is en error. I go in recovery and flash restore.zip and then it works. So why have I this issue. With PDroid Manager I give MMS.apk all permissions but nothing happend. So now I can flash it without patched mms.apk file but I think this file is important, or ? Help me, please.
[Android Software/Hacking General [Developers Only]] Urinophoria:
Which ROM/device are we talking about here? Links to the relevant threads/downloads would be a massive help. Could you attach an Autopatcher log from when you patched your ROM?

Also, are you using other permission managers as well? do they have any settings relevant to MMS? Did you try press and hold to select MMS, then select "allow all" from the extended menu (3 dots in the upper right corner) in pdroid manager?
[Android Software/Hacking General [Developers Only]] Urinophoria:
Looks like some of the problem at my end was installation method. I was installing auto patcher by downloading the zip and unzipping it.

This last time, I deleted my working directory for auto patcher and just cloned the git to my home folder. Everything works great now
[Android Software/Hacking General [Developers Only]] josteink:
Getting the same thing here for my CM10.1 builds for TF1001:

Let me know if I can help by providing log files or trying additional flags/builds/parameters etc.
[Android Software/Hacking General [Developers Only]] Scuppa:
The manual method given here seems to work: http://xdaforums.com/showpost.php?p=42952610&postcount=281
[Android Software/Hacking General [Developers Only]] josteink:
Doing that, I still get this: :(
[Android Software/Hacking General [Developers Only]] Caldair:
Sorry to all that are having issues with patching tabletUI. There have been so many changes to the patched files in the last week that keeping up has been impossible.

I did just fix the tabletUI patches again today, and submitted a pull request to Mateor. I don't want to completely highjack his auto-patcher with daily CM tabletUI fixes, but that is basically what has been necessary this past week.

Watch for an update and hopefully tabletUI patching will be working again. The latest fix should work for builds since 06-27 through today... Who know's what tomorrow will bring!:laugh:
[Android Software/Hacking General [Developers Only]] KingKuno:
Thanks.

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

Log: http://codepad.org/LPcHkajF

I use no other managers and yes I try to allow all but it doesnt work.
[Android Software/Hacking General [Developers Only]] theCroh:
I'm getting this error http://codepad.org/csawIarw when trying to patch latest CM10.1 i9100 NIGHTLY (= this http://get.cm/get/jenkins/32753/cm-10.1-20130629-NIGHTLY-i9100.zip)
[Android Software/Hacking General [Developers Only]] josteink:
ROM I use is this one: http://nexfiles.kjonigsen.net/tf101/cm10.1/
[Android Software/Hacking General [Developers Only]] Urinophoria:
Does Pdroid.jpeg exist in /patches/openpdroid/4.2/cm/20130626/system/media/?

If not, copying it over from another media folder (for another date) would probably fix your problem, but I'm a little curious as to why it wouldn't be there. Its showing up on my local version.

If it is there, its a problem for wiser heads than mine, lol.
[Android Software/Hacking General [Developers Only]] theCroh:
For some reason the image was indeed missing (actually from /patches/openpdroid/common/system/media/ folder). It seems that for some reason the Git sync wasn't complete. Maybe this has something to do with Panda Cloud Antivirus. I couldn't get it to work even after reinstalling the whole thing. Tried installing APG on another computer and got it working correctly (patched today's nightly just fine).
[Android Software/Hacking General [Developers Only]] DualJoe:
I get massive amounts of hunks rejected on roms i patched successfully before even with old auto-patcher builds. I've completely reinstalled Cygwin but the error remains. It looks like latest version of Auto-Patcher corrupted something outside of cygwin or something.

I deleted 'C:\Users\User\apktool\framework\1.apk' already. Are there any other external ressources? I have no clue whats wrong here. I tried official releases and 'git clone'. Nothing successful anymore on roms that could be patched properly before. Example rom can be downloaded here.

!!! error: failed android/app/ContextImpl$10.smali' in framework.jar cannot be remedied

Any ideas? :rolleyes:
[Android Software/Hacking General [Developers Only]] Lei M:
Stupid question, but would it theoretically be possible to run the patcher on Android?

:S
[Android Software/Hacking General [Developers Only]] Urinophoria:
Looks like it's not updated (update disabled) and using patches for 5-16. I'm mucking around with partitions on my machine, but when I'm done I'll download your rom and give it a shot
[Android Software/Hacking General [Developers Only]] DualJoe:
No, there's no Java SDK and probably other things...

Thanks. I've tested several autopatcher versions. All lead to the same error. Other people confirmed its still working for them (with latest patcher) so it probably works for you as well. I completely deleted the cygwin folder and reinstalled it. Maybe there's some more data in user folders or Windows temp folder. Will check that again. I'm wondering why it doesn't work anymore on my side out of a sudden...
[Android Software/Hacking General [Developers Only]] Urinophoria:
Yep, you're right, just got done fixing my partitions, downloaded the one you linked and ran it on my machine. Worked out just fine here. I haven't messed with the windows version at all, so I don't know much about how that works. One of these days I'll quit avoiding it, lol.
[Android Software/Hacking General [Developers Only]] jahrule:
Slimrom compiled with linaro tool chain don't work
[Android Software/Hacking General [Developers Only]] Urinophoria:
Not sure, but I don't think any Linaro compiled ones will. I had to create a secondary directory for building patches because I was compiling PAC with Linaro for personal use, and the unpatched output of PAC doesn't work with the autopatcher either. I don't know enough to dig in and figure out WHY, but something changes when you do that; it makes it different enough that it won't patch.

(edit: That or I just screwed something up that was unrelated. I'd only been building from source for a couple days when I found that)

Fortunately I figured that out before I gave Mateorod any of those builds, lol!
[Android Software/Hacking General [Developers Only]] josteink:
I've patched both normal builds and linaro ones alike successfully. Until the whole cm breaking tabletui-thing started happening.
[Android Software/Hacking General [Developers Only]] SirGeraint:
Failures after CM adds Privacy Guard

I've been successfully using auto-patcher to patch openpdroid for months now. But ever since CM added Privacy Guard to the ROM I haven't been able to get it to work. I searched the forum and didn't find anyone with this error so I wanted to make sure I wasn't missing something.

Here's the error I am getting. I have attached the full output as well.

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

!!! error: failed android/app/Activity.smali in framework.jar cannot be remedied

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

Thanks a bunch for all the hard work on this.
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, something is very messed up there...everything is failing. That looks to be corruption, but the actual corruption could be several places...maybe in the zipped up patches (which escape the git double-check) or in the .git folder itself. ApG seems to need to be completely erased and reinstalled at times...I ould try that instead of intense debugging. If you can spare the bandwidth, it looks to be the easiest solution.

not a stupid question. Not at all. I have (in my head) the methods to

get rid of the ROMTYPE nonsense, probably forever

use the autopatcher on your android device, probably as an apk

The first I hope to bring out soon, the second will probably take me longer. I know how to do it, but getting it done is another matter. I would much rather be working on that, which is my actual area of expertise, instead of spending my time learning how to debug, merge and maintain the OpenPDroid build patches. But that is where we are. I hope to offer it someday, but trust me it isn't easy. I have seen some very knowledgeable Android engineers say it should be impossible...but it isn't, I have done it :). But it isn't ready for userland yet, not even close.

I am guessing it is the apktool? There is a disconnect between the apktool dev and the SLimRom team somewhere. I will do what Caldair suggested and replace the apktools with the SlimRom builds and that should help.

Caldair, I bet the SlimRom apktool is larger ( I am taking your word on that I haven't looked) because they didn't bother using ProGuard, and shrinker and obfuscater.

Caldair pushed new tabletUI patches yesterday, so it should be working. post a log if it isn't so Caldair can see what is happening. Thanks.

That looks like legitimate breakage...man everything is breaking constantly right now. This is as bad as it has ever been. Thank goodness Urinophoria joined the team and can handle the builds. I will send him a pm.

edit hmmm...I just tried a CM10.1 nightly from 0701 and it patched. Would you try a nightly fro get.cm from today or tomorrow when it comes?

Yeah, we had a lot of problems with the quarx fork for Cm10. but that patched correctly, biut had a problem recompiling. it is something we see very rarely, but is sometimes fixed by trying to run the autopatcher again. try twice more and then let us know if it works. I don;t see anything on it's face that would stop it from working.
[Android Software/Hacking General [Developers Only]] IRKONIK:
ApG.2.6.0.2.exe got deleted by my Bitdefender for being a trojan (Trojan.Generic.9324783), so I checked virustotal.com: 3/47 say it's a trojan.

This is kinda creepy. Any statement by kobik77?

Cheers!
[Android Software/Hacking General [Developers Only]] scutworker:
If you search the thread, you'll see that many virus scanners report the autopatcher as a virus. It's all in the first post, which has a link to this informational post. Fear not, for it is

not

a virus. Just disable your scanner whilst you run it.
[Android Software/Hacking General [Developers Only]] josteink:
At first I attempted just pulling latest sources, but that didn't seem to help.

After failing that, I tried wiping my auto-patcher directory, recloning it from github, re-running ./batch.sh and then process the cm10.1 ZIP-files with tabletUI-mod.

Doing all that the process actually succeeds, both for normal and linaro builds. Thanks :)
[Android Software/Hacking General [Developers Only]] SirGeraint:
I just tried the 07/02 nightly. It failed. Same error. I tried Auto-Patcher v2.9.89 and v2.9.895 (from github). It previously failed on 06/27. 06/28, 06/30, and 07/01 (but some might not have been the same error).

Here's the error. (The same, I know.) and I've attached the full output.

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

!!! error: failed android/app/Activity.smali in framework.jar cannot be remedied

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

Sorry about the trouble. I figured it was mainly from CM adding Privacy Guard. I felt Privacy Guard is a nice addition but not a replacement for openpdroid and I don't really want to run without openpdroid so I will wait for the fix before I upgrade to the nightlies. I wish CM would just add openpdroid to their ROMs.

Thanks again, Mateor and Urinophoria (and anyone else that I don't know about).