yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Ticklefish:
Oh. Tricky.

Er..are there any in system/app or system/priv-app? There shouldn't be but it might be worth looking.
[Android Software Development] deadwolf666:
Nope non.
[Android Software Development] Carotix:
waiting for mm sammy tool ... :(
[Android Software Development] bovirus:
What's mm samy tool?
[Android Software Development] svadev:
Dear,	iBotPeaches

We are looking forward to apktool working for Android M for Samsung ...
[Android Software Development] _alex74_:
yep same here....

i and [MENTION=2739548]tamirda[/MENTION] have tried dirty 2.1.0 but no luck....

there's no hurry, but hope that [MENTION=3924617]iBotPeaches[/MENTION] figures out a solution.( 1RY56669FY626791J just a small help to show that we are here even to support you :D)
[Android Software Development] :
Yeah I noticed Samsung obfuscate their code but are they using dexguard for it. Rather funny since their obfuscation isn't really that obfuscated as dex guard usually is. I guess there's different "levels" of how hard core you can use. Didn't know it also tampered with the xml files. Maybe they are applying something after compile which generates dirty errors[emoji14]I can't tell.
[Android Software Development] deadwolf666:
Cant find any,

Any ideas?
[Android Software Development] Ticklefish:
Sorry, no. Your error says you need to install a framework file. If you've installed all that are available, I've no idea how to resolve this issue. Sorry. :(
[Android Software Development] arteaga323:
Do you guys know what kind of signing Google does to the APKs? I modified Android Wear to not display on the launcher and added a string to my settings apk. Settings is great however the Android Wear app crashes upon launch every time, I tried using ZipSigner on Platform but no luck.

Sorry if it sounds too noob to post here or if I shouldn't have posted here but I couldn't find an answer anywhere else, delete if necessary.
[Android Software Development] plegdroid:
Evening Matey, settings apk shouldn't be signed. ☕?

ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[Android Software Development] arteaga323:
Oh no yeah I know that, apologies if I fail to elaborate, everything settigs-wise is fine, I point to the app, it opens, etc (I've already added SuperSU, TWRP manager to the development options in settings) I'm pretty good with the settings app, my problem is the Android Wear app, all I did was erase the line in the manifest that displays the launcher icon, recompile and sign and install but no luck, it crashes as soon as I open.
[Android Software Development] AL_IRAQI:
Hi

im trying to install huawei framework and i got these errors

apktool if framework-res.apk
Exception in thread "main" brut.androlib.AndrolibException: Multiple resources: spec=0x01040384 string/lockscreen_carrier_default, config=[DEFAULT]
at brut.androlib.res.data.ResType.addResource(ResType.java:66)
at brut.androlib.res.data.ResType.addResource(ResType.java:55)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:252)
at brut.androlib.res.decoder.ARSCDecoder.readTableType(ARSCDecoder.java:212)
at brut.androlib.res.decoder.ARSCDecoder.readTableTypeSpec(ARSCDecoder.java:154)
at brut.androlib.res.decoder.ARSCDecoder.readTablePackage(ARSCDecoder.java:116)
at brut.androlib.res.decoder.ARSCDecoder.readTableHeader(ARSCDecoder.java:78)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:47)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:39)
at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:599)
at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:581)
at brut.androlib.Androlib.installFramework(Androlib.java:683)
at brut.apktool.Main.cmdInstallFramework(Main.java:240)
at brut.apktool.Main.main(Main.java:87)

apktool if framework-res-hwext.apk
Exception in thread "main" brut.androlib.AndrolibException: Multiple resources: spec=0x02020010 string/wifi_switch_to_pdp_title, config=[DEFAULT]
at brut.androlib.res.data.ResType.addResource(ResType.java:66)
at brut.androlib.res.data.ResType.addResource(ResType.java:55)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:252)
at brut.androlib.res.decoder.ARSCDecoder.readTableType(ARSCDecoder.java:212)
at brut.androlib.res.decoder.ARSCDecoder.readTableTypeSpec(ARSCDecoder.java:154)
at brut.androlib.res.decoder.ARSCDecoder.readTablePackage(ARSCDecoder.java:116)
at brut.androlib.res.decoder.ARSCDecoder.readTableHeader(ARSCDecoder.java:78)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:47)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:39)
at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:599)
at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:581)
at brut.androlib.Androlib.installFramework(Androlib.java:683)
at brut.apktool.Main.cmdInstallFramework(Main.java:240)
at brut.apktool.Main.main(Main.java:87)

both of them here
[Android Software Development] iBotPeaches:
Huawei isn't supported currently. Sorry.

I'm a bit behind in fixes, but 2.1.0 has enough fixes for a few of you so going to try and get that out before this month ends.

Yes I know Samsung MM is still broken. I'm working on it.
[Android Software Development] xenreon:
A logcat is needed to know the exact reason here, check this thread to know how to take a logcat if you don't know already
[Android Software Development] jtash01:
Could not decode arsc file with 6.0.1 framework-res.apk

Hello. I have updated the apktool.jar file in my apktool folder. to decompile both the SystemUI and framework-res.apk from a deodexed Galaxy S7 Edge stock ROM. G935FXXU1APC8_G935FBTU1APB2_BTU (marshmallow 6.0.1). The deodexed ROM was generated from SuperR's kitchen with no errors.

I have both the deodexed framework-res.apk and twframework-res.apk files in the folder as well as the deodexed SystemUI.apk.

However, when I try to decompile either the framework-res.apk or SystemUI.apk the "Could not decode arsc file errors" show up and no decompile is generated.

I tested the new ver 2.0.3 apktool.jar with the equivalent apk's from a lollipop Samsung S5 ROM and the decompile ran fine without errors.

Any suggestions?
[Android Software Development] _alex74_:
Thanks mate,

seeing you are still here sounds very good to us :D:D:good::good:

Take your time with MM, i appreciate your har work:D:D

The only suggestion is read well the thread before posting requests like this.

This is well known problem OP is working on it. There is a workaround, but it is wise you learn few pages and find by yourself.:rolleyes:
[Android Software Development] deadwolf666:
Im currently working on V10 MM apk with apktool 2.0.3.

Im not getting any errors on opening or closing the apk but after I put it on phone I get application crush, any ideas why ?

btw I got to the point that I open and close without any modification..
[Android Software Development] :
Happened to me as well don't know why used earlier version solved my issue

We love you :) thanks for keeping apk tool updated even if it takes time we appreciate your work <3
[Android Software Development] deadwolf666:
Thank you for the idea, because we talk about MM my only other option is 202 , I just tried it and same resolt.
[Android Software Development] :
Are you talking about Samsung?

Oh LG try 2.0.0
[Android Software Development] deadwolf666:
Its MM, Does 2.0.0 supports ? Ive tried 2.0.1 and got de-compile error
[Android Software Development] djdarkknight96:
Google protects their apps so resigning 90% of the time breaks it...keeping original signature and placing it in system/app fixes that's......but.......if editing anything in values in Google apps also can have issues like Gmail and Google plus. Hangouts was very close to this as well but we found moving resources.arsc to the apk with the "store" option in WinZip will keep its compression and work. This didn't work on gmail and Google + though.

Hope that helps

DJ
[Android Software Development] gemini16:
I'm just waitting for apktool 2.1 for Samsung M. End of month soon :) :)
[Android Software Development] qubanaso:
Latest doesnt support MM waiting for update on MM, im on sprint note 4 MM and cant do anything
[Android Software Development] iBotPeaches:
A new version has been released!

v2.1.0 (Released March 27, 2016)

On my immediate radar is now

Samsung Marshmallow regression

LG framework bug

Dexguard Enterprise bugs

Null TypeSpec bugs

Download: https://bitbucket.org/iBotPeaches/apktool/downloads/apktool_2.1.0.jar

Details of Release: http://connortumbleson.com/2016/03/27/apktool-v2-1-0-released/
[Android Software Development] sohailhind:
LG tribute 5 lollipop 5.1 settings.apk cannot be decompiled. Tried all the things but failed.

Is anyone here who can help me?
[Android Software Development] Thebear j koss:
Read the post right above you. Probably has something to do with the lg framework bug. And need more details than i tried everything but it doesn't work... Log and as much info as possible would help so much more.

Thebe?r'$ NeXu$
[Android Software Development] gemini16:
Great, apktool 2.1.0 is out, but i still cannot install samsung M framework files.
[Android Software Development] _alex74_:
ahmm...is written beneath changelog...... next version will fix MM regression...

Anyway respect and big thanks to [MENTION=3924617]iBotPeaches[/MENTION], it is great you update apktool, MM this time is pain in the ass for developers and themers.....

;):laugh::good::highfive:
[Android Software Development] lijianjunyonghu:
samsung MM S7 6.0.1

Exception in thread "main" brut.androlib.AndrolibException: Could not decode ars

c file

at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:52)

at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:39)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResource

s.java:607)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResource

s.java:589)

at brut.androlib.Androlib.installFramework(Androlib.java:640)

at brut.apktool.Main.cmdInstallFramework(Main.java:239)

at brut.apktool.Main.main(Main.java:87)

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:292)

at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:224)

at brut.androlib.res.decoder.ARSCDecoder.readTableType(ARSCDecoder.java:

212)

at brut.androlib.res.decoder.ARSCDecoder.readTableTypeSpec(ARSCDecoder.j

ava:154)
[Android Software Development] gemini16:
Oh man, can't you just read?
[Android Software Development] iBotPeaches:
Guess this warrants another response. Yes I know Samsung Marshmallow doesn't work. Yes I know that sucks. Yes I know it used to work and now doesn't. However, 4 months+ between releases is something I agreed I wouldn't do again so it was time for another apktool release regardless if the bug was fixed or not.

It still isn't fixed, but I've spent a good deal of time researching it. So I will list my research and understanding and maybe someone with another pair of eyes can catch my mistake.

This is know as Bug 1131 first reported on Jan 9. The application in question works on the release of Apktool 2.0.0 but breaks on Apktool 2.0.1.

This means that a commit between those two versions (or multiple commits) broke this functionality, thus regression. This link (Takes awhile to load) loads all the changes between those two releases.

If we look at the stacktrace or errors, we see this (image to preserve formatting)

I don't expect anyone to understand that as much as I do, but you can see the failure is really early in the apktool process. Setting the SDK version requires the ResTable to be initiated and to do that we must read the resources.arsc file. Reading this file goes (Table, Package, Type, Config, Entry, Value). This fails on reading Value because the expected header (Set of bytes the same on every value) is 0x01 instead of 0x08.

So a commit or multiple is at fault here. 29 of the 45 commits are smali updates. 2 are version changes, 1 is test related, 1 is the scripts on windows. This leaves us with like 7 commits that might be at fault.

Prevents frameworks from modifying sharedLibrary flag

Catch lookup on internal attributes.

Robust ResFile handler

Read bytes if over KNOWN_BYTES

Implement ResIntBased to all possible types

Handle lib & libs

Handles version information on SDK version

If we look at commits that change the files that the application failed at. That is #3 and #7 from the list above. As obvious, neither of those reverted fixes the problem. This means a combination of commits led to this issue. Though as we've seen this has gotten me no where. Thus here we are researching when free to come to a solution.
[Android Software Development] Thebear j koss:
Gracias Connor. Your tireless work and continued support of apktool is appreciated by all. Sorry some can't read 2 or 3 posts back or check the op to find changelogs or repository for bugs and/or what is still being worked on. No rush on getting the quirks straightened out, if others can't have patience let them do it themselves. Obviously this would be so much less of a headache if you dropped support for these proprietary devices like Lg and samsung, but android is a better place with your continued support. Soon you'll be getting the this doesn't work on android Nougat posts... Lol. Thanks again. ?

Thebe?r'$ NeXu$
[Android Software Development] cerj:
I completely agree brother bear koss, ibotpeaches, and apktool are an invaluable resource to the community and to Android. Thank you ibotpeaches for your continued support to apktool. [emoji106] [emoji4] [emoji106]
[Android Software Development] Crussader:
I don't expect it to understand everything either :P

But... will it be of any help if I build one apktool version from each commit to check ( decompile Samsun MM ) when it breaks? I know this would be a very time-consuming work but YOUR work is invaluable for us and you deserve any help we could provide. Most of us wouldn't be here without Apktool.

[edit]

I don't think this would work... I've tried building from several commits and I always end up with a build error.

[/edit]
[Android Software Development] :
Since version 2.0.0 > 2.0.1 there is 72 files which are different :P

gonna see if i can find a solution

some of them aren't interesting, however there are some things as mentioned breaking it, thought you can import framework on 2.0.0 u can't decompile it

also if you look at the log it comlpains about arscdecoder.java at line 52.

line 52. is: } catch (IOException ex) {

maybe if we trace the logs ;P
[Android Software Development] iBotPeaches:
It should work, make sure you delete the $HOME/apktool/framework/1.apk between builds as apktool will use the internal one at that point which should in theory work if I versioned them correctly. Otherwise we need to dig for older frameworks.

Yes, most are smali changes. Thankfully smali is a dependency now so it will no longer be in the changelogs bloating the differences.
[Android Software Development] :
what if we follow the logs? that is being thrown at us?

as said in ARSCDecoder it is } catch (IOException ex) { on line 52, however it might be not the case at all.
[Android Software Development] iBotPeaches:
That is the error that was thrown at the end, but that was the catch for any IOException. You can see the IOException happened when skipCheckShort didn't match the value it wanted. That method was called ReadValue (line 238 of ARSCDecoder) which is where the real code (not errors or catches) starts. Just follow the stacktrace backwards to see what called what and how it fell apart.
[Android Software Development] :
Ah I see, but looking at the commit changes. Are hard to match since they differ from 2.0.0>2.0.1 on git

I can look trough 2.0.1 & 2.0.0 sources to see the changes. I believe it's as you said 7 commits regarding to arsc decoder and resources.
[Android Software Development] kep2008:
I'm not sure if I did the right thing , but I was able to

here working https://github.com/iBotPeaches/Apktool/commit/2c1226fab88f079df4cbdbdbf68f346afcafdb73

View attachment apktool_2.0.1-2c1226f.jar

but not here https://github.com/iBotPeaches/Apktool/commit/6ee029dd30808a05f842c46672261a27dbb107da

View attachment apktool_2.0.1-6ee029d.jar
[Android Software Development] Crussader:
Hmmm whenever I try to build it I get this error:

org.jf.dexlib2.AccessorTest > testAccessors FAILED
junit.framework.AssertionFailedError: expected:<12> but was:<1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:277)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at junit.framework.Assert.assertEquals(Assert.java:201)
at org.jf.dexlib2.AccessorTest.testAccessors(AccessorTest.java:125)

105 tests completed, 1 failed
:brut.apktool.smali:dexlib2:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':brut.apktool.smali:dexlib2:test'.
> There were failing tests. See the report at: file:///D:/Desktop/Apktools/Apktool-48285bde03a586d7edd064148be82681afa51b74/brut.apktool.smali/dexlib2/build/reports/tests/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 2 mins 0.589 secs

I'm downloading the whole zip from GitHub of each commit I'm testing... the only one that builds successfully is the last commited one.

Maybe I'm missing something?
[Android Software Development] Thebear j koss:
[MENTION=6621711]sohailhind[/MENTION] read my post again, and read the post by ibotpeaches above mine. He is working a fix for that lg framework bug.

Plus i didn't see an errior or that the decompile failed. It just isn't decoding those files listed...

Thebe?r'$ NeXu$
[Android Software Development] sohailhind:
it created com folder into "unknown" named folder

it created com folder into "unknown" named folder
[Android Software Development] sohailhind:
Hello admin can you see no one is answering on that dedicated place?
[Android Software Development] Thebear j koss:
I have told you the problem 3 or 4 times now. Read the post where ibotpeaches posted about the update a page or so back. There is an issue with samsung, lg, and some other bugs that are being worked on. You just have to be patient or learn to build apktool yourself and figure out what the lg framework is doing to break the decompile... Not reading and continually asking and calling administrators is not going to help. Lg and samsung are having issues with apktool. It is on his radar and is hoping to have a fix as soon as possible

Thebe?r'$ NeXu$
[Android Software Development] sgian217:
It will be good when the apktool have a function to sign an apk
[Android Software Development] Thebear j koss:
It does already i believe...

Thebe?r'$ NeXu$
[Android Software Development] sgian217:
it does but why I can't install my app on file explorer even though the app is already uninstalled there?
[Android Software Development] _alex74_:
This are basics not related to discuss here.... apktool does not sign apk, you can do it with cmd using some files in apktool folder(for convenience), but those files are not linked or created by OP as far as i know.

If u need help with this, open a thread in dedicated forums.
[Android Software Development] xdagee:
If you wanna sign apks then you might wanna try autosigner.
[Android Software Development] thereassaad:
Dear iBotPeaches maybe this can help u. It's a older apktool 2.0.1 which does work on some Samsung MM apps 6.0.1 . For example - SystemUI and some other apps can be in decompiled and recompiled correctly & also installing frameworks . Others like SecSettings & SecMms don't work. I hope this can help others Samsung devs as well!

Which already mentioned here by kep2008 but didn't noticed that ? ,highfive , good ,

http://xdaforums.com/showthread.php?p=66082889

?

Link ::

https://mega.nz/#!flo3jaiJ!I4-2sJVdcSXWE0VIl0Jykl-GmVhKGPrwDqYDKaFboxk

?
[Android Software Development] nguyentankiet:
Is it support TW 6.0?
[Android Software Development] DaOldMan:
Exactly! This is for 6.0.1 tw roms [emoji2] .

Phronesis team member
[Android Software Development] enewman17:
Only if you've changed the AndroidManifest.xml then you will need to sign the apk with another tool.

If you haven't then there is usually no need to resign the apk. When you build the apk use -c to copy the original meta-inf and manifest into the newly compiled apk this will retain the original signature of the apk.

apktool b -c
[Android Software Development] kep2008:
Excellent , friend... :good:

But you can give a link to the previous page... :D
[Android Software Development] thereassaad:
Yes

???
[Android Software Development] syntropic:
Humble Question

[deleted]

Syntropic
[Android Software Development] 7odaahmad:
What app do U use to decompile apps cause the apktool.jar you mentioned didn't work for me

and the latest version didn't work neither :/
[Android Software Development] thereassaad:
TickleMyAndroid [emoji3]
[Android Software Development] Bajanman:
+1 to this^^^ ???? ????.

And a new version coming soon..
[Android Software Development] motiam4:
I can't install framework-res.apk samsung marshmallow stock TW using version 2.1.0 ,what's the problem please?

Exception in thread "main" brut.androlib.AndrolibException: Could not decode ars

c file

at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:52)

at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:39)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResource

s.java:607)

at brut.androlib.res.AndrolibResources.installFramework(AndrolibResource

s.java:589)

at brut.androlib.Androlib.installFramework(Androlib.java:640)

at brut.apktool.Main.cmdInstallFramework(Main.java:239)

at brut.apktool.Main.main(Main.java:87)

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:292)

at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:224)

at brut.androlib.res.decoder.ARSCDecoder.readTableType(ARSCDecoder.java:

212)

at brut.androlib.res.decoder.ARSCDecoder.readTableTypeSpec(ARSCDecoder.j

ava:154)

at brut.androlib.res.decoder.ARSCDecoder.readTablePackage(ARSCDecoder.ja

va:116)

at brut.androlib.res.decoder.ARSCDecoder.readTableHeader(ARSCDecoder.jav

a:78)

at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:47)
[Android Software Development] DaOldMan:
Mate don't you read anything at all ? The last 4-5 pages are mostly about this with a great explanation of [MENTION=3924617]iBotPeaches[/MENTION] as well. Come on, don't just ask something without making a thorough examination of the thread first !
[Android Software Development] motiam4:
sorry about that,hope he update us soon with solution.thanking him for his effort.
[Android Software Development] djdarkknight96:
So latest Google apps decompile with string errors killing languages. Funny thing is it builds fine just translations are now missing in the app. Good ole GoOgle must be using new N fw so I didn't post a new issue since we know we can't install N fw yet, but figured id report it here before you get spammed with this. Only reason I think it's related...same errors while installing N fw...I attached the error log of both. No rush...hurry...I'm patient..no I'm not.... Lol A little humour.

DJ

Edit: Patrick "Thyrus" added it to the issue tracker already.