I am trying to modify AndroidManifest.xml of settings.apk
But as we all know, if we modify that AndroidManifest.xml, we have to sign the apk so when I modify the AndroidManifest.xml and sign the settings.apk and push it then it doesnt get installed and I get a error in logcat saying there is a mismatch in signatures of the apk and system uid.
Then I tried restoring stock signatures but it still doesnt get installed and in log it says the apk has no signatures because I modified AndroidManifest.xml.
Do anyone have solution for this to sign system apps properly or any other workaround?
I came to know that every system apk and framework apk must be batch signed incase of editing the manifest xml.
I don't think that every apk needs to be re-signed. I've never done this, but my thought was that any apk that has an AndroidManifest.xml with the same original modified dates (you can check the dates with 7-zip) need to re-signed together. Won't it mess up some other apks that don't need to be re-signed if you were to re-sign everything? Please let me know if I am way off..
Also, note that there are other ways to invert the colors in apks besides editing the AndroidManifest... (i.e. edit the /values/styles.xml, /layout/*.xml, etc... can be a pain, but it works) - Sorry, but I guess I am assuming that that's what you are going after by editing the AndroidManifest in the Settings.apk... again, anyone feel free to correct me if I'm wrong on anything here - I am all for learning and sharing!
^^No I dont want to theme it or colorize it
I am adding new functionality for which some new permissions and activity declaration is needed in Manifest file
But if I modify Manifest and use stock signature files it doesnt install and if I resign it then it say signature mismatch with system uid.
Bump!!
I have edited the AndroidManifest.xml in the Settings.apk (for theme color change), and I did not re-sign it after compiling, I retained the originals.
And, it worked fine when I put it on my phone alone (with a flashable zip package), BUT (this is a big but), - it did not get installed when I put it in a ROM package together with all the system files. That's when the signatures become an issue... you need to then re-sign all, or nearly all apps and framework.
At least that's my experience...
Check out this thread.. http://forum.xda-developers.com/showpost.php?p=28475720&postcount=63
Sent from my phone's mind
Oh then I have to sign all system apks
Any other way?
Do you know how to sign with system key which will match system uid?
Only for AOSP ROMs you can resign and apks work. Samsung use closed source.....how could you ever match signatures? Also don't change the Manifest. Leave it. Who says you have to change it?
Note that its via the public.xml that you need to add these listings as to what the apk is now doing. No the manifest. Is it going to market? No so don't change manifest simple. If it is then it shouldn't really be a system app. Also you can disable signature checking within your ROM if that is all you are worried about. I have signed apks from the market that I have themed and then installed them to system and they work fine. Its the apks you use that have dependencies that WON'T work. I.e. apks like Samsung TWiz apks that listen for the system vold boot complete proprietary to Samsung or say an ASOP apk that is trying to chime into something that is framework related in a non-asop ROM.....this then becomes a permissions issue
---------- Post added at 05:09 AM ---------- Previous post was at 05:05 AM ----------
PS: I have edited androidmanifest anyway and apks still work fine.... upgraded the SNS apk to ensure it was fit for use above and beyond SDK 10
varun.chitre15 said:
I am trying to modify AndroidManifest.xml of settings.apk
But as we all know, if we modify that AndroidManifest.xml, we have to sign the apk so when I modify the AndroidManifest.xml and sign the settings.apk and push it then it doesnt get installed and I get a error in logcat saying there is a mismatch in signatures of the apk and system uid.
Then I tried restoring stock signatures but it still doesnt get installed and in log it says the apk has no signatures because I modified AndroidManifest.xml.
Do anyone have solution for this to sign system apps properly or any other workaround?
Click to expand...
Click to collapse
Did you figure out in the end? Still stuck with same problem as you
I love a theme for cm10.1 (10.2) but there are a few little things i would like to personalise such as software keys, settings icon and statusbar pulldown bar, i have tried to decompile the theme's apk in apk manager (5.0.2) then it says there is a problem then tells me to look in the log but before i did that it decompiled, so i looked in projects folder and changed a few of the things i said earlier then compiled it which also said there was a problem but compiled anyway. When i installed the apk it was the same as normal mianogen! what have i done wrong? thanks for reading
Kind of hard to explain...
I have a theme apk that installs to /system/app during source compile in cm-10.2. Works great as does the ROM) if I select it in settings > themes.
However, I want that theme 'activated' , without user intervention, when ROM first boots up.
How would I do that?
Hello people, before we start i am new to android so i am not up to speed with everything yet. I need some help trying to change the settings background from white to either a picture or transparent.
I am using using the Xtrestolite rom for my G925F but would like to change the settings background. I have used various xposed mods to try to achieve this but non seem to work, wanam xposed, xbackground, gravitybox.
Next i used Tickle my Android to decompile the framework, systemui and tw_framework apks from the rom. From the guides i have read i think i should be looking for tw_background_holo_dark.xml but i cant find this file anywhere or a .png version (i guess these guides are for older android versions).
So i have edited various other files that i think relate to the settings background, active_background.xml, active_background_holo_dark.xml to transparent and solid colors and others but nothing affect the settings background. I also tried deleting the xmls and replacing them with .pngs of the same names and in different drawable folders.
I used Tickle my Android to make zips to flash and also put the edited framework apk back in to the rom folder and flashed the full rom but nothing works.
So before i waste a few more hours i will ask for a nudge in the right direction if anyone can help. Thank you
Hola guys. To all of you. Particularly the ones who are familiar with MIUI. I will just stick to the point. If you ARE familiar with miui then you must have come across those flashy themes. You must also have found out the way to bypass the infamous theme policy WSM tools and Xposed and all. But I recently started taking interest in those flashy themes. You know that once you download a theme from the default Themes app the mtz file starts getting downloaded and as soon as the downloading has finished it gets unpacked into bits (com.android.contacts, com.miui.home, icons, lock_wallpaper, locksreen and so on) and gets copied to the MIUI folder in main storage and again into data/system/theme. This is the first problem. I can't copy the whole mtz file to a safe place because it gets unpacked as soon as it has been downloaded which is basically a zip file containing several other zip files that is, the 'bits' I was talking about. Second thing. the default themes app does not recognize mtz files downloaded from the official miui themes website. It declares them as third party themes. What I did was, took some of those 'bits' and replaced some XML files inside them and some png elements and put them back into data/system/theme. But miui has a way to prevent this from happening. As soon as it detects a modified file present in data/system/theme it reverts back to the default plain theme by deleting all files from data/system/theme. My guess is it keeps checking out verifying in regular intervals the checksums that it must have generated earlier. The same thing happens if I just replace a bit in the mentioned directory with a bit from another theme. So my questions are:
1. Is there a way to preserve the mtz file downloaded from within the default Themes app as a whole mtz file?
2. Can I make changes to just the Themes app so that it would apply any mtz file?
3. Is there a way to prevent miui from continuously checking or verifying the checksums that it has generated? (just a guess but I reckon thats what it actually does) because for an hour or so after replacing or modifying the 'bits' everything works fine but the reverting process takes place in an hour or so.
Thats all folks! jk. Any help or suggestion would be really appreciated because I think a thread like this was long since needed here. And dont talk about visiting MIUI's official forums. Most of the guys there don't know half the things that is really worth discussing. Thank you guys.
note- dont want to use WSM tools nor can I find one for miui7.
note2- if I change the permissions of the folder (data/system/theme) to 444 allowing READ permissions only, the phone would just reboot without warning and continue to reboot until the permissions are changed back to normal (755).
seriously guys. no one?
I'm right now at your point.
I want to modify some files or overwrite some files in "data/system/theme" and after a while the theme manager applies the original miui theme .
Does someone have any solution to this?
Damntoosleepy did you get any solution?
Xiaomi doesnt let global phones use unapproved icons, themes, fonts etc. If you changed any of these you will be reverted to default. Only way to design your theme or apply one is becomming a designer in miui website(theres tut at gearbest.com). Or you can adjust your current one in themes \app bottom right corner\ click button/ customize theme. You can mix things there. Take icons from one theme, bg or font from another one and so on. But the themes you must have downloaded from approved miui themes app. I had issue when 3rd party icon pack caused me this problem on a approved theme from miui themes app. Then i changed the pack through the miui themes app and problem solved
Any solution?