-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(No resource found that matches the given name) decompiling / recompiling ,without any changes. #1361
Comments
The same to my situation. https://play.google.com/store/apps/details?id=com.felink.clean2&hl=en |
Same issue here, trying to decode & rebuild this apk. |
This is interesting. The original application obviously had some build procedure which obfuscated resource names, looks like AndroResGuard. Every resource is alphabetical like So take an offending line
Now the So we can leverage aapt to dump the above file
So we can see the attribute That human readable name is just copied onward, but guess what. It doesn't exist. If we follow the resource ID once again with aapt we get.
The correct resource was
Apktool should be updated to follow |
when dude |
@iBotPeaches fix it please |
So I spent a lot of time trying to understand this and just tabulating my research. Apktool currently decodes this to
So the
We know the key is
So our decoder is really messing up. So lets check for this old resource (
So wow. The application has the old attribute in the smali R class. Lets check the
Ugh same resourceId. Two different resource names. What is correct? What shouldn't be there? No idea yet. |
I have a trouble with the same thing. Haven't it fixed yet? |
@iBotPeaches Dear Owner/Developer, thanks for advise the aapt method... I got it all and successfully completed recovered all strings... Of course it must be one by one, and need some critical accuration... Tools :
You can download the build tools from here : |
Is it fixed ??? |
seams not fix yet |
any solution? |
@Gintasz, If you had checked out the following reference to this issue... ... @iBotPeaches posted something there 12 days ago because the underlying issue there is similar/same as this issue in regards to the namespace (possibly connected to the aapt as well). What this tells me is very positive because it reflects that iBotPeaches hasn't forgotten about the issue at hand. Just be patient... 👍 ~Ibuprophen |
I really appreciate all the tough work you've done, only by which we could be able to gain more insights about this issue and so many other things as to Android reverse engineering. I've recently encountered some similar troubles in the rebuilding phase.
As you can see, these problems are caused by custom attribute in a private namespace of a resource file. I've found that xml attribute names or values in a private namespace will be incorrectly refered to something that is exactly a system attribute resource as guys have mentioned in historical comments. These errors seem to be widespread as occurring in a large number of issues. I've got digging into the source code of apktool and have tried to tweak two files relating to the xml parsing phase.
The basic ideas:
Then I utilized the modified code to re-decode the apk. At last, it worked and rebuilt the resource folder successfully. The originally falsely-referenced attribute had been corrected into an entity which is an obfuscated name. It's too sad to file a pull request as I've got some network troubles in cloning no matter my forked branch or even the master branch. Forgive me that I can't publish the apk I cracked here since it's a business production which is not owned by myself. But if @iBotPeaches you need it, tell me and I'd be pleased to mail it to you. The whole of experience of analysis and tweaking process has been posted in my blog. Please let me know if you guys come up with any ideas or suggests. |
@ljysdfz any chance you could share your solution so I can try rebuilding my APK? Thanks! |
Sure of course. --- Info for integrity & consistency --- |
Thanks, it works for me. |
Hello @ljysdfz thanks for the patch. Hi @iBotPeaches the patch is still on version 2.3.4. Is it possible to check and merge the changes into 2.4.0 version or maybe a new release with other fixes? Thanks |
Sorry for delay. Lots of changes for attribute/namespace decoding in v2.5.0. PRs for code changes in future won't be missed as easily :) Apk is not findable anymore.
So closing as there is nothing really I can do here, trying to clean backlog. |
I met this problem too, just using @ljysdfz 's method solve my problem! Here is my build of apktool, just do what @ljysdfz reply. The target apk link is here. I just tried decode and compile back. |
@iBotPeaches yes, fix by @ljysdfz wok fine on apk with confused resources. |
Don't be that guy, he works his ass off, seeing stupid comments like this is garbage. Great work iBotPeaches |
I decompile SHAREit_3.6.68_ww.apk then recompile it again without any changes.
download link:
SHAREit_3.6.68_ww.apk
But the following error occurs:
deompile :
recompile :
Information
apktool -version
) -2.2.1Questions to ask before submission
apktool d
,apktool b
without changing anything? YESThe text was updated successfully, but these errors were encountered: