-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feature request for automated remapping of resource id in smali files. #244
Comments
Comment #1 originally posted by AdamRosas1972 on 2011-02-06T05:32:11.000Z:
|
Comment #2 originally posted by Brut.alll on 2011-05-03T16:04:30.000Z:
I have some ideas that requires me to remap resIds, but smali files are the worst - I'm afraid simple pattern matching isn't reliable enough. First, you may remap normal literal by accident. Second, you may miss some true resIds. Actually, I can already say you that you miss some of them for sure, because literals ending with 0x0000 are set using const/high16, not const. And every apk has at least few of such resources. Worst thing is: you will never know that modified apk is screwed up, it will run and look normally, but some of its functionalities may fail or work differently. Ahh and you should group resources by type-name pair, not just name. There may be @string/foo, @integer/foo, @bool/foo, @id/foo, etc. - each one with different resId. |
Comment #3 originally posted by AdamRosas1972 on 2011-05-04T05:40:12.000Z:
|
- refs: #244 - Regular expressions are not the way to fix this. Too many situations in smali where patterns won't work. Correct fix would be to hook dexlib
The |
Original issue 133 created by AdamRosas1972 on 2011-02-06T04:30:35.000Z:
so today I prototyped some code to remap the resource id's and thought
that it would make a great addition to apktool. how it works is you
pass it the source public.xml the target public.xml and the smali file
you wish to "port" to the target device and it does all the work and
writes out the file with the remapped resource id's.
I have attached the java source for your consideration.
The text was updated successfully, but these errors were encountered: