Add support for apks with different resources package and manifest package (--rename-manifest-package) about android-apktool HOT 18 CLOSED

Yep, need to fix this for 4.2. It seems lots of APKs are starting to do this. 

It's already there in 4.1.2 APKs. Eg. I just tried to decode 
GalleryGoogle.apk+GalleryGoogle.odex. So far so good, it didn't produce any 
errors. Then I tried to build it back into an APK and got tons of the "No 
resource identifier found for attribute '...' in package '...'" errors.

The suggested workaround/fix worked though.

I had to run the following to replace in the resource XML files the 
"com.android.gallery3d" resource package name with the actual package name 
(from the manifest), which is "com.google.android.gallery3d":

find res -type f | xargs perl -pi -e 
's/http:\/\/schemas\.android\.com\/apk\/res\/com\.android\.gallery3d/http:\/\/sc
hemas.android.com\/apk\/res\/com.google.android.gallery3d/g'

I can confirm this will work.
Only thing I had to do also is add:

parent="@*android:style/TextAppearance.Medium"

to line 168 of the styles.xml file of the GalleryGoogle output.

Issue 227 has been merged into this issue.

My previous statement was a bit premature. The search&replace in the decoded 
resource XML files works only as far as apktool's build command is involved. 
I.e. the "apktool b GalleryGoogle GalleryGoogle.apk" command completes 
successfully, but putting the rebuilt APK on the phone and launching the camera 
app, it crashes, when I switch to camcorder mode.

However grabbing classes.dex from the rebuilt APK and putting it into the 
factory APK (i.e. unzipping the original APK, putting the classes.dex -that I 
took from the rebuilt APK- into the unzipped folder, rezip the contents of the 
folder into a new APK and sign the APK) works indeed.

So I guess I'll have to wait for Brut.alll's proper solution. Until then I'll 
have to manually do the APK rebuild so I can add the --rename-manifest-package 
option to the aapt commandline. I just checked the current state (from the GIT 
repo) and it seems the fix is not yet there. Hopefully it'll make into the 
1.5.1 version. :-)

Issue 357 has been merged into this issue.

About 70% with this little patch. All is going well currently. Just lost a bit 
of time tracing down an AXmlPullParser problem, which ended up being the fact 
that the namespace isn't attached to the package name in AndroidManifest.xml 
which made it quite difficult to grab. Slight oversight on my part.

All that aside. Things are going well. Haven't had as much time as I wish.

Just a quick question, is there any support yet, or fix/workaround for 
decompiling android 4.2 framework-res.apk? I posted issue 357 in comment 7 so 
you can find the errors. It simply errors at "decompiling sources" and thats 
it. 

Thanks!

Apktool correctly grabs the renamed and original package name and stores it in 
apktool.yml

packageInfo:
  cur_package: com.android.inputmethod.latin
  orig_package: com.google.android.inputmethod.latin


Now, we simply rename the manifest to cur_package, but during build use 
--rename w/ orig_package.

Should have a Apktool v1.5.1 Pre Release 2 ready in a few days.

I believe I have finally fixed this, testing continues but otherwise its Fixed.

may i get my hands on it? i would like to do some testing as well :)

http://miui.connortumbleson.com/other/apktool/test_versions/apktool_1.5.1PR2.jar

Apktool v1.5.1 PR 2

:o OMG it worked! No errors!! :D OMG i love you BEST CHRISTMAS PRESENT EVERR! 
:D thanks so much you seriously are amazing!!! :)

So I managed to decompile, change /res/values/colors.xml, then doing find res 
-type f | xargs perl -pi -e 
's/http:\/\/schemas.android.com\/apk\/res\/com.touchtype/http:\/\/schemas.androi
d.com\/apk\/res\/com.touchtype.swiftkey/g' and finally compile, sign and 
install. But everytime I want to open SwiftKey's design settings, I get an FC. 
Anyone knows why? :(

I tried to use new version Apktool v1.5.1 PR 2. But I didn't understand where I 
need to put this string "--rename w/ orig_package".
I used this command:
C:\Users\admin>apktool b --rename w/ com.touchtype.swiftkey c:\1\6

If I build an app as usual (with this command: C:\Users\admin>apktool b c:\1\6) 
but with new version of apktool, the command works, but there are still errors.

Example:
c:\1\8\res\values-v14\styles.xml:4: error: Error retrieving parent for item: 
Noresource found that matches the given name 
@*android:style/Theme.DeviceDefault.Dialog'.

P.S. packageInfo:
  cur_package: android
  orig_package: com.touchtype.swiftkey

That has nothing to do w/ the --rename. Its automatically done. Thats just a 
bug according to styles.xml.

Post a new bug with apk and full error log.

OK, I've attached the log and the folder, which I want to build.
P.S. I zipped the folder for attaching.