Recently SwiftKey released a beta version of their keyboard that backs up data to the cloud and installs separately from the market version. In order to have all my previous use data uploaded, I should be able to install this beta as an update to the market version of SwiftKey and the data will be backed up. The market version has package name com.touchtype.swiftkey and the beta is package name com.touchtype.swiftkey.phone.obeta . I tried changing the package name in AndroidManifest.xml and styles.xml , along with replacing every instance of com.touchtype.swiftkey.phone.obeta with com.touchtype.swiftkey within the decompiled apk. Using both APK-Multi-Tool and Virtuous Ten Studio it will not recompile, and I cannot figure out how to fix the issues to build. Attached to this post is a log from Virtuous Ten Studio when trying to recompile, any help is appreciated. Or if there is another easier way to change the internal package name, please let me know. Thank you in advance!
LOG FILE HERE--> https://copy.com/byWYTLWSt8Idf6OI
Also if someone could enlighten me on how to use the aapt command "--rename-manifest-package" it would be very much appreciated, as I think that would be the easiest solution if I just knew what to type!
imaconeheadXD said:
Recently SwiftKey released a beta version of their keyboard that backs up data to the cloud and installs separately from the market version. In order to have all my previous use data uploaded, I should be able to install this beta as an update to the market version of SwiftKey and the data will be backed up. The market version has package name com.touchtype.swiftkey and the beta is package name com.touchtype.swiftkey.phone.obeta . I tried changing the package name in AndroidManifest.xml and styles.xml , along with replacing every instance of com.touchtype.swiftkey.phone.obeta with com.touchtype.swiftkey within the decompiled apk. Using both APK-Multi-Tool and Virtuous Ten Studio it will not recompile, and I cannot figure out how to fix the issues to build. Attached to this post is a log from Virtuous Ten Studio when trying to recompile, any help is appreciated. Or if there is another easier way to change the internal package name, please let me know. Thank you in advance!
LOG FILE HERE--> https://copy.com/byWYTLWSt8Idf6OI
Also if someone could enlighten me on how to use the aapt command "--rename-manifest-package" it would be very much appreciated, as I think that would be the easiest solution if I just knew what to type!
Click to expand...
Click to collapse
Zarboz is beast.
Sent from my HTC6435LVW using xda premium
Bump, anyone?
You need to rename each subdirectory to match the new package name as well
Did you replace all references inside the smali too? As in, a reference to com/touchstone/swiftkey/phone/0beta/Class.smali is now com/touchtype/swiftkey/Class.smali
Sent from my buttered S3
CNexus said:
You need to rename each subdirectory to match the new package name as well
Did you replace all references inside the smali too? As in, a reference to com/touchstone/swiftkey/phone/0beta/Class.smali is now com/touchtype/swiftkey/Class.smali
Sent from my buttered S3
Click to expand...
Click to collapse
From what I could tell I replaced everything, the log is showing errors with aapt so it's not building for me still. Would you happen to know how to use the aapt command "--rename-manifest-package"? I saw this post here but I'm not sure where I type what he mentioned or how it works, if you could enlighten me that would be great (since I know you use Linux, maybe it relates?)
http://forum.xda-developers.com/showpost.php?p=37885462&postcount=14
Related
Source Found
Brut.all of XDA has released the program APKtool which make the process of editing any APK file much easier, especially XML editing. Before you had to use a few different programs (Smali, hex editor, etc) to do the same thing. A future release is going to have the decompiler dump into an easy to import into Javabeans/Eclipse format.. so nice
Program and Usage link;
APKTool 1.2
Setup;
Before you start, download from the link above both the apktool-1.2.0.tar.bz2 and apktool-install-windows-2.2_r01-1.tar.bz2 and extract them to your windows folder.
Usage;
Decoding APKs;
Code:
apktool d <file.apk> <directory to output to>
Compiling APKs*;
Code:
apktool b <directory of decoded apk>
*The compiled apk will be saved to the sub directory "dist", which is in what ever directory you choose to compile.
Output structure;
Smali directory - The output of classes.dex, the code to the apk
Res directory - Your resources, the images and layout/structure xmls
Lib directory - Shared library files
Dist directory - The apk output of the "apktool b" command, if you didn't run it you won't have it.
Build directory - The compiled output of the "apktool b" command, like what you would see if you just extracted an apk file with 7zip. If you didn't run it you won't have it.
General info;
Once you have your edited apk from the Dist directory you'll need to sign it. I use Dave Da illest 1 of XDA's modified script for signing. Just place your apk, this should be the only apk in this folder, in the same folder that you extracted the auto-signer to and execute sign.bat. The script will output your_app_signed.apk, which is your signed and ready to load on your phone apk.
If you'd like to decompile/compile an apk file that doesn't have a classes.dex, like framework-res.apk, just place any classes.dex into the apk and it will decompile. If you don't do this apktool will through up an error. Just remember to pull the classes.dex out before you sign it.
Videos;
Editing an Apk file with APKTool;
http://www.youtube.com/watch?v=XXgYVHTcl6c
Editing a Jar file with APKtool;
http://www.youtube.com/watch?v=VAekeWiqHcY
Why?;
Localization / Translation
Themeing
Adding in features or taking them out
Impressing friends and family, lol
etc..
Issues;
I noticed that while the new version 1.2 works great on the framework-res.apk file, it seems to have issues with other System/app files like Settings.apk,Phone.apk, etc. For these files use version 1.1.1.
Hopefully this is helpful, I tend to ramble.
-Ften @ sdx-developers.com
http://forum.xda-developers.com/forumdisplay.php?f=613
Post it here too, mate.
shokkapic said:
http://forum.xda-developers.com/forumdisplay.php?f=613
Post it here too, mate.
Click to expand...
Click to collapse
Will do, not having a good time at the moment as I can't seem to edit launcher.apk with this tool. Not sure why. basically I decompile, edit then compile but having issues when transferring it back to the phone.
EDIT: I just get a black screen when trying the new modified .apk file.
Why to create new threads, if apktool has its official thread here
http://forum.xda-developers.com/showthread.php?t=640592
andrewb84uk said:
Will do, not having a good time at the moment as I can't seem to edit launcher.apk with this tool. Not sure why. basically I decompile, edit then compile but having issues when transferring it back to the phone.
EDIT: I just get a black screen when trying the new modified .apk file.
Click to expand...
Click to collapse
Do you get any errors in logcat?
Brut.all said:
Why to create new threads, if apktool has its official thread here
http://forum.xda-developers.com/showthread.php?t=640592
Do you get any errors in logcat?
Click to expand...
Click to collapse
I could not find it anywhere else and I did do searches for hours Brilliant tool!
See Attachment, I think it's this line
Code:
E/PackageManager( 138): Package com.android.launcher signatures do not match the previously installed version; ignoring!
However, not sure how to fix it.
andrewb84uk said:
I could not find it anywhere else and I did do searches for hours Brilliant tool!
See Attachment, I think it's this line
Code:
E/PackageManager( 138): Package com.android.launcher signatures do not match the previously installed version; ignoring!
However, not sure how to fix it.
Click to expand...
Click to collapse
Not an expert. But try to uninstall the previous launcher, before installing that one.
shokkapic said:
Not an expert. But try to uninstall the previous launcher, before installing that one.
Click to expand...
Click to collapse
Will try it.
EDIT: Nope, uninstalled re-installed, still black screen.
andrewb84uk said:
I could not find it anywhere else and I did do searches for hours Brilliant tool!
See Attachment, I think it's this line
Code:
E/PackageManager( 138): Package com.android.launcher signatures do not match the previously installed version; ignoring!
However, not sure how to fix it.
Click to expand...
Click to collapse
I think you can't install Launcher just like that, because it's system app. You should do it through update.zip file.
Try to not use apktool, but just unpack Launcher.apk, remove META-INF dir, zip it back, sign and install. If you will get similar problems, then they can't be related to apktool (because you didn't even use it), but to something else.
Brut.all said:
I think you can't install Launcher just like that, because it's system app. You should do it through update.zip file.
Try to not use apktool, but just unpack Launcher.apk, remove META-INF dir, zip it back, sign and install. If you will get similar problems, then they can't be related to apktool (because you didn't even use it), but to something else.
Click to expand...
Click to collapse
If I unzip it, remove META-INF dir, zip it back, sign + install and it works fine. It doesn't work when I edit 1 file by decompiling and compiling, sign, upload it fails but it also fails using APKManager.
EDIT: I have also tried using notepad++ / notepad to edit the xml both to the same issue.
Err... you know, your problem is for sure related to signing/installation and not to apktool. Key error line is here:
E/PackageManager( 138): Package com.android.launcher signatures do not match the previously installed version; ignoring!
Click to expand...
Click to collapse
andrewb84uk said:
If I unzip it, remove META-INF dir, zip it back, sign + install and it works fine. It doesn't work when I edit 1 file by decompiling and compiling, sign, upload it fails but it also fails using APKManager.
Click to expand...
Click to collapse
Could you explain, how is it possible, that you can properly sign rezipped apk, but you can't reapktoold' one? If you get signing issues, then this is totally irrelevant what apktool does. All files could be random binary strings as well cause they aren't even read.
This thread can be deleted or moved to the bin or where ever it needs to go!
idroid84 said:
Usage;
Decoding APKs;
Code:
apktool d <file.apk> <directory to output to>
Compiling APKs*;
Code:
apktool b <directory of decoded apk>
*The compiled apk will be saved to the sub directory "dist", which is in what ever directory you choose to compile.
Click to expand...
Click to collapse
Thank you soooo much!!! It took me hours of searching to find this post and once I did, I had my apk decompressed in under a minute!!! You da man
If your running windows XP here's a right click reg edit I made for making decompiling/compiling quicker-
forum.xda-developers.com/showthread.php?t=935967
Hey guys... really trying to theme for the first time with xml files.
I have done modifying of png which are easy, but just lenghty and detailed.
So now that Gingerbread is out, some of the items have been moved to the xml files.
indeterminate was from 4 and now down to 3. but I want to increase to 8 to mimic honeycomb. Also the progress horizontal was once a png reference file now its in the systemui.apk xml too.
Anyhow short version.... anytime i edit more then 1 line at a time after decompiling, when trying to say it will ask to save as text.
Whats the best file editor for xml? or recommendations.
I use notepad++ on windows, you can also import your decompiled apk into eclipse and use that, it'll also report any errors or mistakes you might make.
Hope this helps.
Yeah I have been using that do and any time I compile and flash it just gives me boot loop.
Question about proper importing to eclips.
Whenever I just flat out decompile ... do my modification, go to recompile, it get errors. In apktool and apkmanager.
Should I extract the resource file and class dex out and then decompile. Cus when I have the resource file in the same directory....at least last nights attempt, apktool finale didn't give me an error and compiled.
I've done a decompile just from apk and imported to eclips and when I try to run, gives error.... "no style availiable" or something like that
Sent from my Droid using XDA App
Thank you!!!
Greetings.
fixing a broken abondon market apk
Could someone fix this app VirginmobileMinuitechecker . I think i found the problem . Virgin Mobile updated there site from logon www1 to www2 . I edited it from the open source and zipped it back up but i cannot get this compile program to run at all . here is the zip master . I made several attempts emailing jay goel but he his MIA .. the app will no longer log in because of the VM website recent changes . TIA
EDIT ,, NEVER MIND . i got it working and fixed that app . works like a charm now pretty good being i don't code for a living.. if you don't mind i posted the fixed app . you may move or delete if it is not proper . thank you for the tutorial .
http://evervolv.turnertechrepair.info/Clark44/Android4.0-System-Dump.zip
Courtesy of Jrbourque
EDIT: Thanks Efrant, Title changed.
EDITED WITH ALTERNATE LINK
link didnt work for me
The correct link http://evervolv.turnertechrepair.info/Clark44/Android4.0-System-Dump.zip
from twitter.com/#!/ts0cha0tik/status/126506123288248320 the correct download link is t.co/MagyJCbm
Thanks! Now to see what I can rip off and put on my incredible.
Is there any confirmed way to deodex the apps and framework? The latest smali/baksmali didn't work for me.
sdk dump. same as before..
Why do people keep posting SDK dumps? We all know where the SDK dump is available...
OP, please change the title to reflect that this is the SDK dump...
I just jumped into their irc channel to check if anyone had analyzed the reason for baksmali failing on the ICS odex files. It seems it was basically a function that had changed syntax, requiring several other changes but HomerSp sent me a working baksmali.jar. Smali then doesn't complain when compiling the result.
Unfortunately he went offline just after that so I'm not sure he would be ok with me posting it here so I won't. I'll write a script to deodex the files instead and upload the results if nobody else does so.
I was actually just curious about why it failed, didn't expect at working version just like that.
EDIT: Done and uploaded. Thanks again to HomerSp for the working baksmali.jar!
framework-deodexed.zip
app-deodexed.zip
NOTE: I just realized I forgot to fix the signatures so for the apps it will probably fail unless resigned. I leave that to someone else though. I have not verified that these are valid but as I said, at least smali didn't have a problem compiling them so they are hopefully ok.
blunden said:
I just jumped into their irc channel to check if anyone had analyzed the reason for baksmali failing on the ICS odex files. It seems it was basically a function that had changed syntax, requiring several other changes but HomerSp sent me a working baksmali.jar. Smali then doesn't complain when compiling the result.
Unfortunately he went offline just after that so I'm not sure he would be ok with me posting it here so I won't. I'll write a script to deodex the files instead and upload the results if nobody else does so.
I was actually just curious about why it failed, didn't expect at working version just like that.
EDIT: Done and uploaded. Thanks again to HomerSp for the working baksmali.jar!
framework-deodexed.zip
app-deodexed.zip
NOTE: I just realized I forgot to fix the signatures so for the apps it will probably fail unless resigned. I leave that to someone else though. I have not verified that these are valid but as I said, at least smali didn't have a problem compiling them so they are hopefully ok.
Click to expand...
Click to collapse
First i will like to say thanks, great work, the APKs will still not install, it keeps saying "there is a problem parsing the package." Is there any fix???
max63094 said:
First i will like to say thanks, great work, the APKs will still not install, it keeps saying "there is a problem parsing the package." Is there any fix???
Click to expand...
Click to collapse
As I said, they are not signed correctly as that would require me to remove the current signature files and resign them. I am currently sick so I didn't feel like doing it since anyone else could fix that if they wanted to.
To fix it, remove the META-INF folder from the apk and then sign it using jarsigner (part of Java JDK) or signapk. If you want to install them as normal apps you would need to make sure you pack any libs needed in the apk in a lib folder and then sign the apk using your own keystore. I mostly posted it in the hope that it would help someone make an SDK port though but use them however you like.
blunden said:
As I said, they are not signed correctly as that would require me to remove the current signature files and resign them. I am currently sick so I didn't feel like doing it since anyone else could fix that if they wanted to.
To fix it, remove the META-INF folder from the apk and then sign it using jarsigner (part of Java JDK) or signapk. If you want to install them as normal apps you would need to make sure you pack any libs needed in the apk in a lib folder and then sign the apk using your own keystore. I mostly posted it in the hope that it would help someone make an SDK port though but use them however you like.
Click to expand...
Click to collapse
Deleted META-INF, signed the launcher via Kitchen & tried to install via ADB, getting error [INSTALLED FAILED - OLDER SDK]..
Any clue?
fshami said:
Deleted META-INF, signed the launcher via Kitchen & tried to install via ADB, getting error [INSTALLED FAILED - OLDER SDK]..
Any clue?
Click to expand...
Click to collapse
Yes, you need to change the minimum SDK version in AndroidManifest.xml to Gingerbread.
Code:
<uses-sdk
android:minSdkVersion="14"
android:targetSdkVersion="14"
>
</uses-sdk>
You need to change android:minSdkVersion="14" to 9 (for 2.3-2.3.2) or 10 (for 2.3.3-2.3.7). I have a feeling it probably won't work completely as it probably uses some ICS APIs.
The problem is that apktool doesn't work since it uses the non-working baksmali. Because of that, I don't know how to convert the file back to it's binary form.
Anyone has yet installed the ICS live wallpapers?
ilbeppez said:
Anyone has yet installed the ICS live wallpapers?
Click to expand...
Click to collapse
The SDK doesn't include any live wallpapers other than a rotating wireframe cube.
So is anyone going to port the apps to gingerbread? I've seen them posted everywhere but so far no ports
Link_of_Hyrule said:
So is anyone going to port the apps to gingerbread? I've seen them posted everywhere but so far no ports
Click to expand...
Click to collapse
I have already explained just a few posts earlier why it's currently not as easy to do as it normally is.
So no one can do it because the apk tool can't recompile it properly?
I would like to add some emoticons into whatsapp
Sent from my GT-I9100 Westcrips ICS using xda premium
RodneyNL said:
I would like to add some emoticons into whatsapp
Sent from my GT-I9100 Westcrips ICS using xda premium
Click to expand...
Click to collapse
You probably wont be able to add any, you can change the current ones by editing the apk, signing it then installing it. Once you open up the apk (with 7zip, winrar etc.) look inside the drawable-hdpi folder. Thats probably where the emoticons are kept.
I can help if you need.
You might want to check out these custom whatsapp's by yorzua :
http://forum.xda-developers.com/showthread.php?t=1543631
Thanks for your reply om gonna try it out i'll let you know of i need your help (probably i will need it xD)
Sent from my GT-I9100 using xda premium
Adding icons to whatsapp
Hey Guys has anyone tried adding new icons into the default whatsapp?
Or do the modded versions allow adding additional GIF'S to be added to the instant messenger?
Thanks
yes i have tried it, but it's useless since the recipient of the emoticon should have the "moded" version too, so that he could see the emoticon
Just wanted to add that Ive noticed the Iphone has new icons and I can view them on my phone which dont have those icons :/
esk02k said:
You probably wont be able to add any, you can change the current ones by editing the apk, signing it then installing it. Once you open up the apk (with 7zip, winrar etc.) look inside the drawable-hdpi folder. Thats probably where the emoticons are kept.
I can help if you need.
You might want to check out these custom whatsapp's by yorzua :
http://forum.xda-developers.com/showthread.php?t=1543631
Click to expand...
Click to collapse
I used 'Formatter' to rename (whatsapp) .apk file into .zip did required changes (replaced one .png smiley file) & again renamed it into .apk
But then, I'm not able to install it (even after uninstalling previous version). An error saying 'Application not installed' shows.
How can I modify .apk files (in terms of replacing only the smiley image files) & repack it into proper .apk file so that I'll be able to install it without any error?
Please help me..
thanks
yogz214 said:
I used 'Formatter' to rename (whatsapp) .apk file into .zip did required changes (replaced one .png smiley file) & again renamed it into .apk
But then, I'm not able to install it (even after uninstalling previous version). An error saying 'Application not installed' shows.
How can I modify .apk files (in terms of replacing only the smiley image files) & repack it into proper .apk file so that I'll be able to install it without any error?
Please help me..
thanks
Click to expand...
Click to collapse
i also want a new smiley, for example a puking smiley
After modifying the apk i think you should resign it to be able to install it
Check zipsigner from the play store
Sent from my GT-I9100G using XDA Premium 4 mobile app
fmardini said:
After modifying the apk i think you should resign it to be able to install it
Check zipsigner from the play store
Sent from my GT-I9100G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so i have to download the whatsapp.apk, unrar it, change the icons in it, and resign it?
Were are the folder?
I am getting a "parsing" error by installing whatsapp
jonny.pl said:
i also want a new smiley, for example a puking smiley
Click to expand...
Click to collapse
That is exactly what I am trying to do here.
I was looking for the same & found these.
http://www.techgyd.com/whatsapp-stickers-free-android-iphone/12739/
Good idea, but not practical
In order to install an apk, it must be properly signed and with a password that only the developers know. If you own the app though, you will still need to to decompile and recreate the apk structure by turning the directories of the zip into an android structure, since the compiling will change pretty much everything.
Worst part of it all, if you somehow manage to change and install the app, only you will be able to see it since only the apk installed on your phone has those custom emoticons.
Cheers :good:
how do I put emoticons on viber /whatsapp for sell
Just get your friends to use wechat, has all the emos in the world. Whatsapp is crap
So I'm currently using a MMS app that is modded with emojis + other useful settings . But I was wondering if anyone could help me add the emojis from ios6 into that application. I took the emojis out of the Handcent Emoji Plugin application and I'll attach it with this post along with the MMS.apk that has the "regular" emojis that I'm using at the moment.
If not, could someone help me with editing/modding the MMS.apk so I can add them myself? I played around with APKtool and also APK manager but I'm unable to "decompile" the application
Edit: Some possibly useful or useless information-Galaxy Nexus running on a rom that is on 4.2.1 (aosp)
:fingers-crossed:
Update!
So i was able to change the public.xml file to add the ios6 emojis. But now, when I recompile the apk, theres an error. Where else should I change the code?
I would also like this
Sent from my Nexus 4 using xda premium
areole said:
Update!
So i was able to change the public.xml file to add the ios6 emojis. But now, when I recompile the apk, theres an error. Where else should I change the code?
Click to expand...
Click to collapse
What error are you getting? Are you defining images in the public XML and not adding the actual image? Anyway a log would help also it's easier to just add the images try to recompile and let the public XML build new resource ids for the new images. I have never looked into this but i would imagine you would need to add something else in styles or strings can't remember which one. Also I'm not sure how well those new icons will play with other phones it might work i just don't know.
Sent from my Galaxy Nexus using xda premium
Beamer9408 said:
What error are you getting? Are you defining images in the public XML and not adding the actual image? Anyway a log would help also it's easier to just add the images try to recompile and let the public XML build new resource ids for the new images. I have never looked into this but i would imagine you would need to add something else in styles or strings can't remember which one. Also I'm not sure how well those new icons will play with other phones it might work i just don't know.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The error I'm getting is "public drawable symbol is not defined"
I added the actual image (.png) files to the folder where all the other drawable images were located. I believe the folder was called drawable-xhdpi (I don't have access the the computer I used to mod the mms.apk at the moment). This was the only folder were the older emojis were in. Could you explain to me the recompiling? Do I not physically edit the public.xml file, and let it update itself?
This is what I did:
1. Extracted new emoji's from handcent
2. Decompiled the mms.apk + added new emojis to drawable-xhdpi folder (I tried recompiling here but when I used the app, there were no new emojis)
3. I clicked around and opened the public.xml file and saw that there were emojis names and id codes so I manually added more coding so that the new emojis would have codes.
4. When I added id codes to all the new emojis, I noticed that the id codes doubled in some misc. picture files so I manually changed those as well so the id codes wouldn't double
5. Save and recompiled it but it wouldn't work.
The .png icons that I extracted from handcent (I believe) are the same ones in the mms.apk currently since they have the same names. So I assumed that it was okay to do, but I might be wrong.
Thank you, sorry for the trouble
Hi,
MMS package ideally has the package name of "com.android.mms". I was able to modify and successfully use the package name as "com.android.sms" and use it as a second app in the phone.
However, some apk does not allow this change and any package name other than "com.android.mms" does not allow to be installed (though signed) and reports only "app not installed".
Does anyone have a clue about this protection? Has anyone been able to figure this out?
Thanks in advance.
josephpatrick said:
Hi,
MMS package ideally has the package name of "com.android.mms". I was able to modify and successfully use the package name as "com.android.sms" and use it as a second app in the phone.
However, some apk does not allow this change and any package name other than "com.android.mms" does not allow to be installed (though signed) and reports only "app not installed".
Does anyone have a clue about this protection? Has anyone been able to figure this out?
Thanks in advance.
Click to expand...
Click to collapse
Hi
For this
First you Should disable signature Checker from service.jar
See this
http://forum.xda-developers.com/showthread.php?t=2198834
After that you Should decompile "secmms.apk"
Then you should drag and drop all secmms.apk folder from project folder in your apktools to not pad and change package to other be Sure in smali file package called "com/android/..."
and in xml file called "com.android....."
Finally compile it and Do sign because you had changed androidmanifest.xml
Goodluck
Armin.
Sent from my GT-I9100 using xda premium
Biftor said:
Hi
For this
First you Should disable signature Checker from service.jar
See this
http://forum.xda-developers.com/showthread.php?t=2198834
After that you Should decompile "secmms.apk"
Then you should drag and drop all secmms.apk folder from project folder in your apktools to not pad and change package to other be Sure in smali file package called "com/android/..."
and in xml file called "com.android....."
Finally compile it and Do sign because you had changed androidmanifest.xml
Goodluck
Armin.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you for the steps, it makes sense to disable signature check. however, had a small doubt though. if few other secmms.apk allow changing of the name and some not, is it not something within the apk itself that is accepting the change. For e.g. i didnt have to patch service.jar to get one particular apk to work after renaming. Your thoughts please.
josephpatrick said:
Thank you for the steps, it makes sense to disable signature check. however, had a small doubt though. if few other secmms.apk allow changing of the name and some not, is it not something within the apk itself that is accepting the change. For e.g. i didnt have to patch service.jar to get one particular apk to work after renaming. Your thoughts please.
Click to expand...
Click to collapse
After you change "androidmanifest.xml"you Should sign that apk
For this you need disable signature checker in services.jar
Goodluck
Armin.
Sent from my GT-I9100 using xda premium
Biftor said:
After you change "androidmanifest.xml"you Should sign that apk
For this you need disable signature checker in services.jar
Goodluck
Armin.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
This still does not explain the problem wherein some mms.apk allows renaming the package name and allowing re-compiling and signing. However, few others do not allow any change to the package name, the re-compiling works, signing works but the app does not install
Please note that i was successfully able to change the name of 1 of the mms. apk and it installs as a separate app. however, there are a couple of others which does not work in this fashion. This is weird, seems to be some sort of locking mechanism within the apk. The fact that it works fine for the one modded mms.apk confirms that i dont need to make changes to signature checker. There is something else preventing the package name change
josephpatrick said:
This still does not explain the problem wherein some mms.apk allows renaming the package name and allowing re-compiling and signing. However, few others do not allow any change to the package name, the re-compiling works, signing works but the app does not install
Please note that i was successfully able to change the name of 1 of the mms. apk and it installs as a separate app. however, there are a couple of others which does not work in this fashion. This is weird, seems to be some sort of locking mechanism within the apk. The fact that it works fine for the one modded mms.apk confirms that i dont need to make changes to signature checker. There is something else preventing the package name change
Click to expand...
Click to collapse
Are you ok????
I said many times you should/must disabled signature checker....because secmms.apk is system app and system app after sign not work until change service.jar...
Anyway maybe you know better than me...
Goodluck
Armin.
Sent from my GT-I9100 using xda premium
Biftor said:
Are you ok????
I said many times you should/must disabled signature checker....because secmms.apk is system app and system app after sign not work until change service.jar...
Anyway maybe you know better than me...
Goodluck
Armin.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I guess there is a communication gap, guess my request is not clear, I will figure this out on my own, thanks.