Related
Hello!
I'm trying to make my own Rom right now. With dsixda's Kitchen it isn't very hard to do so I thought I'd just give it a try. I'm taking a rooted official Update (Version: 2.10.405.2) as my base. Adding busybox runparts, the /data/app functionality, a2sd+, the custom bootanimation functionality etc. isn't a problem. Removing some apps like Maps, Facebook, Teeter (and so on) and adding some like Rom Manager, Neocore or Quadrant isn't a problem, too. But if I want to implement a theme like the Carbon Espresso Mod or a theme I made with the UOT Kitchen I'm getting bootloops at booting the phone. Here's what I do: I unzip the folder (for example a theme made with the UOT Kitchen) and I copy over the framework-res.apk from the unzipped folder to my Working Folder of the Kitchen (to system/framework) and I overwrite the original framework-res.apk.
And NO: I didn't choose a battery mod or a bootanimation in the UOT Kitchen....
Hope you guys can help me
I might be wrong but doesn't the new file have to be signed? I know there is a signing option in the kitchen.
Sent from my PC36100 using Tapatalk
It's a system .apk so it doesn't have to be signed.
I can't shed any light on the subject, but here's a bump.
Are you replacing the whole "framework-res.apk" file? If so then you will need to resign your entire ROM. Why? When you change a system file ("framework-res.apk", "com.htc.framework.apk", "twframework-res", "rosie.apk", etc.) it no longer has a matching "signature" for all the files it serves images to. Plug your phone into your computer and open up "ddms" in your android_sdk > tools folder to watch what happens when the phone boots up.
A workaround (The way I do it, it's more fun IMHO) is to open up your .apk files in 7zip (or if you're on a mac BetterZip) and add the images from the themed .apk to your stock .apk. This way makes it so your original .apk has the same signature as your other system files yet has the new images from the other files that you wanted. I've had a lot of luck with this method. I don't know if it will still work if you change any .xml files as I have not messed with those yet.
I've subscribed to this thread so if you have any questions post back here or you can PM me if you want. I'm on XDA all day, every day so I'll try to help as much as I can.
Thanks for all the answers! Especially to you, mbobino. Is there a way to sign the whole Rom new? When I make my Rom at the End, the Kitchen signs it automatically, doesn't it? The idea with the images is very good, but if I want to implement a theme like Carbon Espresso it isn't that easy, 'cause Carbon Espresso isn't just a few images. There are several .xml's etc.
The reason you boot loop is mis matched resource ID's in the public.xml file. If you decompile the framework using apktool after adding your images using an archiver then recompile apktool will update the public file for you which saves you from pulling ID''s for every image. I have a video tutorial of how to set up apktool and decompile framework in my Rom thread. Changing images in app apk's won't cause you to boot loop just messing with the framework will.
Sent from my ADR6300 using XDA App
DomiKamp said:
Thanks for all the answers! Especially to you, mbobino. Is there a way to sign the whole Rom new? When I make my Rom at the End, the Kitchen signs it automatically, doesn't it? The idea with the images is very good, but if I want to implement a theme like Carbon Espresso it isn't that easy, 'cause Carbon Espresso isn't just a few images. There are several .xml's etc.
Click to expand...
Click to collapse
The kitchen signs the .zip that you flash when you build it. It does not sign any .apks for you on its own. However, there is an option to sign .apks within the kitchen.
In my opinion, taking all of the images and figuring out how it all works is fun. I feel like I've already learned quite a bit from just digging around and moving files around.
As for the .xml files, you can decompile the .apk and edit them and then recompile the .apk. I'm actually looking into this today. It sounds like some work but hopefully I'll get it figured out.
Sounds like fun indeed So, I'll just have to try it. Where can I find the "Settings" for the Notification Bar? Thanks
The variois status*.xml files in the res/layout folder of the framework-res.apk and the status*.smali files in the services.jar.
What? If I want to implement a Theme made with the UOT Kitchen (without battery) I should just copy over those files to my existing res-framework.apk OR copy over the whole res-framework.apk (the new one) and sign it?
EDIT: Just tried it with a theme from the UOT Kitchen and it worked perfectly. I've just signed the res-framework.apk and the htc.com.resources.apk (or whatever) in the Kitchen, flashed it on my Phone and it just worked like a Charm. But I have got a 50% Transparent Notification Bar and all the system icons (Battery and time/date) are still black and not transparent! Has anyone got a idea where to change this? (.xml or whatever)...And does anyone know where I can find the HTC Wallpapers? I want to change them a little bit
HeyItsLou said:
The reason you boot loop is mis matched resource ID's in the public.xml file. If you decompile the framework using apktool after adding your images using an archiver then recompile apktool will update the public file for you which saves you from pulling ID''s for every image. I have a video tutorial of how to set up apktool and decompile framework in my Rom thread. Changing images in app apk's won't cause you to boot loop just messing with the framework will.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
HeyItsLou, I looked up your ROM thread but couldn't locate the video tutorial.... do you mind providing the url? Specifically, I am trying to add to the list of wallpapers in a ROM. (I have setup apktool but not sure where/which folder to add my wallpapers in Framework-res.apk Launcher.apk before recompiling/signing). Thanks.
You COULD use the Theme Porter by daneshm90. It will only port the PNG s for it so things like clock colour n stuff will be lost, but it will get you alot closer...
http://forum.xda-developers.com/showthread.php?t=737526
Sent from my HTC Hero using XDA App
Thanks! But like I've written before in my Edit, I made it. The bigger theme (Carbon Espresso) wasn't a problem, too. I just had to sign the .apk's in system/app and system/framework (the kitchen doesn't do it by itself. You have to choose the option to sign a single .apk and then look, where the system/framework .apk's are...). Works great now!
DomiKamp said:
Thanks! But like I've written before in my Edit, I made it. The bigger theme (Carbon Espresso) wasn't a problem, too. I just had to sign the .apk's in system/app and system/framework (the kitchen doesn't do it by itself. You have to choose the option to sign a single .apk and then look, where the system/framework .apk's are...). Works great now!
Click to expand...
Click to collapse
Isnt that what I said in the 2nd post -.- lol jk. Glad you got it working!
Yes! And that's why I tried it. And it worked! Thanks Husker and, of course, everybody else!
Glad you got it working. Welcome to the development side of android!
Sent from my PC36100 using XDA App
I don't sign system files or apps and apkmanager among other threads I've read say not to. Im on a rooted backflip. I find I only have to sign third party apps to install.
Why do you have to sign YOUR files?
Sorry for answering that late. Had a few things to do, so I wasn't online very often
If you want to cook an App into your Rom (NeoCore for example), then you don't have to sign it. You can just copy it into data/app. But if you want to change the whole framework-res.apk of the Rom, you have to sign it. 'Cause if you don't sign it, you'll get a Bootloop. The framework-res.apk is a very important part of the Rom, so it has to "fit" to the others. There are some ID's which have to match. Otherwise it won't work. That's how I understood it
Another Question: Has anybody got an Idea where to change the things that are coming, when you first start the phone with a new Rom (the "installation" of the Rom)? I wan't to write: "Welcome to DomiKamp's Rom!" Or something like that...
bestialbub said:
I don't sign system files or apps and apkmanager among other threads I've read say not to. Im on a rooted backflip. I find I only have to sign third party apps to install.
Why do you have to sign YOUR files?
Click to expand...
Click to collapse
I was curious about this too. I always edit the framework-res of any ROM I flash using a custom set of images I have and have never signed the apk afterwards and it has always worked. Maybe cause I'm only replacing images? I usually do this with framework-res and twframework-res and they both can sometimes grow by 1MB or more. Just my experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
DomiKamp said:
Sorry for answering that late. Had a few things to do, so I wasn't online very often
If you want to cook an App into your Rom (NeoCore for example), then you don't have to sign it. You can just copy it into data/app. But if you want to change the whole framework-res.apk of the Rom, you have to sign it. 'Cause if you don't sign it, you'll get a Bootloop. The framework-res.apk is a very important part of the Rom, so it has to "fit" to the others. There are some ID's which have to match. Otherwise it won't work. That's how I understood it
Another Question: Has anybody got an Idea where to change the things that are coming, when you first start the phone with a new Rom (the "installation" of the Rom)? I wan't to write: "Welcome to DomiKamp's Rom!" Or something like that...
Click to expand...
Click to collapse
I think that in order to do the "welcome to" thing you'll have to edit the update-script file. I'm not 100% on it though. Look at a cm Rom and see what all is in there.
Sent from my HTC Evo 4G using XDA App
I'm wanting to change the color of the slider when you turn your volume up and down from yellow to another color. I'm running CM7 fascinatemtd ROM by JT, I know which folder it's in and how to do it. My question is, I use Apk Manager to decomplie my framework-res.apk which was pulled from the ROM using 7zip, I've decompiled the apk, edited the XML file, when I went to recompile the framework-res apk using option 11, a error pop up and told me to read the log, I hit enter, answered yes to system question, then went to keep folder and deleted the resources file as instructed, and hit enter, I was left with an unsigned framework-res.apk file, renamed it to framework-res.apk, and pushed it back into ROM with 7zip, rebooted recovery, cleared caches, and installed ROM, but phone wouldn't boot up. So what am I doing wrong...
Obviously not
Sent from my SCH-I500 using XDA App
What color do you want the slider man
Sent from my SCH-I500 using XDA App
Blue would match my theme the HEX code is 11114b...
Sent from my SCH-I500 using XDA Premium App
If apkmanager errors common logic would dictate to read the log and see what is going wrong
Trying to flash a broken apk won't work obviously
I've gotten it to decompile and recompile bit the problem now os the changes I've made don't show up I'm not getting any errors before I was ising a ROM that I themed so I went back and used the original ROM how do I get the changes to stay...
Sent from my SCH-I500 using XDA Premium App
And you're trying to edit progress_horizontal.xml? And changing code to ff11114b leaving the "f's" in?
good day.
Yes
Sent from my SCH-I500 using XDA Premium App
I should rename unsigned framework.res to framework.res right...
Sent from my SCH-I500 using XDA Premium App
And during the compile process, you hit y for "system apk" and hit y for "would you like to copy over any files..............." and from the keep folder delete resources.arsc and continue to compile. And yes rename back to framework-res.apk.
good day.
Answered yes to system app and no to copy over files, didn't delete arsc and changes stayed, but if I install will I get boot loop since I didn't delete arsc....
Sent from my SCH-I500 using XDA Premium App
If I hit y to copy over files the changes don't stay only if I hit n
Sent from my SCH-I500 using XDA Premium App
it worked, by not copying over the files and not deleting the resources arsc file, does anyone know what the XML file name is for the download progress bar color is...and thanks for your help guys...
Here's what I would do if I was on Windows!
Download apktool & dependencies:
http://android-apktool.googlecode.com/files/apktool1.4.1.tar.bz2
http://android-apktool.googlecode.com/files/apktool-install-windows-r04-brut1.tar.bz2
Unpack both archives to your Windows folder. This will make apktool accessible through cmd anywhere.
CD in cmd window to the location of your apk, If you haven't already done so and install the resources by copying or pulling (framework-res.apk, twframework-res.apk for touchwiz) or (framework-res.apk, SystemUI.apk for GB). Once copied to the folder you are cd'd too...
Install the resources
apktool if framework-res.apk
apktool if twframework-res.apk
apktool if SystemUI.apk
Decompile and make your changes..
apktool d framework-res.apk
Recompile when done
apktool b framework-res
If it built succesfully, then make a copy of your framework-res.apk. Then navigate to framework-res/build/apk! Open your copied apk with 7zip and drag n drop res & resources.arsc from framework-res/build/apk inside! Close it up..
Push and test.. On windows you may need to navigate to your sdk directory if not properly setup!
adb push "your_copied_file"/system/framework/framework-res.apk
If you get a failed to write to system, run this first.
adb shell su -c rw
YES got all progress bar colors changed to blue now my CM7 Fascinatemdt ROM is themed all of my drawable hdpi and XML files are complete I might post this as a theme, thank you for your help...
Sent from my SCH-I500 using XDA Premium App
notta said:
Here's what I would do if I was on Windows!
Download apktool & dependencies:
http://android-apktool.googlecode.com/files/apktool1.4.1.tar.bz2
http://android-apktool.googlecode.com/files/apktool-install-windows-r04-brut1.tar.bz2
Unpack both archives to your Windows folder. This will make apktool accessible through cmd anywhere.
CD in cmd window to the location of your apk, If you haven't already done so and install the resources by copying or pulling (framework-res.apk, twframework-res.apk for touchwiz) or (framework-res.apk, SystemUI.apk for GB). Once copied to the folder you are cd'd too...
Install the resources
apktool if framework-res.apk
apktool if twframework-res.apk
apktool if SystemUI.apk
Decompile and make your changes..
apktool d framework-res.apk
Recompile when done
apktool b framework-res
If it built succesfully, then make a copy of your framework-res.apk. Then navigate to framework-res/build/apk! Open your copied apk with 7zip and drag n drop res & resources.arsc from framework-res/build/apk inside! Close it up..
Push and test.. On windows you may need to navigate to your sdk directory if not properly setup!
adb push "your_copied_file"/system/framework/framework-res.apk
If you get a failed to write to system, run this first.
adb shell su -c rw
Click to expand...
Click to collapse
will this work also when trying to decompile/recompile a non system app, like one from the market, that has dependencies
adude247 said:
will this work also when trying to decompile/recompile a non system app, like one from the market, that has dependencies
Click to expand...
Click to collapse
It will work with anything provided you have the resources. Some apk's are picky by means of what you can replace.
The method above is using apktool the way it is supposed to be used. That apkmanager thing sounded crazy with the delete this after that, hit y or n before this. Seems like alot of un-needed steps and confusion!
On linux it's even easier, pretty much fully auto!
notta said:
It will work with anything provided you have the resources. Some apk's are picky by means of what you can replace.
The method above is using apktool the way it is supposed to be used. That apkmanager thing sounded crazy with the delete this after that, hit y or n before this. Seems like alot of un-needed steps and confusion!
On linux it's even easier, pretty much fully auto!
Click to expand...
Click to collapse
yeah, I didn't delete anything just decompiled, edited the XML, and recompiled, that was the only way I could get the changes to stay. Any suggestions on what to use if the above resources don't work to get the apk to decompile, an example of an apk that I want to edit but cant get it to recompile after decompiling and editing the XMLs is....
adude247 said:
yeah, I didn't delete anything just decompiled, edited the XML, and recompiled, that was the only way I could get the changes to stay. Any suggestions on what to use if the above resources don't work to get the apk to decompile, an example of an apk that I want to edit but cant get it to recompile after decompiling and editing the XMLs is....
Click to expand...
Click to collapse
I can't and won't explain getting resources for market apps or generally someone else's work. However there are several ways to approach non-building apk's.
For example aapt has the capability to recompile standalone 9's as well as xml's, which can then be injected into the apk with the 7zip method. Especially useful for minor changes.
Another example for stubborn apk's would be the Eclipse or similar project. This is where you would partially build the files you wanted to change.
Thanks for the advice...
Sent from my SCH-I500 using XDA Premium App
So I'm trying to do a little themeing and I have some questions. For instance, if I modify idlescreen_base.apk, do I have to sign that and then also sign the .zip? I'm trying to do a full on theme, modifying every little part of the ROM. When do you have to sign the .apks and .zips? One thing I don't like is the bubble around the four icons on the lock screen, so I went in to modify that and then found more files to change and so it began. And so while I'm on it, why do some m10s decode and some don't? Gingeritis3D and ShiftS3NS3 v3.0 have a default folder, but others have Blue Sky, etc. The default folder that has sharedm10 will decode but the others don't. Just curious. I'm using ShiftS3NS3 v3.0 as my base ROM to theme, by the way.
TheBeardedMann said:
So I'm trying to do a little themeing and I have some questions. For instance, if I modify idlescreen_base.apk, do I have to sign that and then also sign the .zip? I'm trying to do a full on theme, modifying every little part of the ROM. When do you have to sign the .apks and .zips? One thing I don't like is the bubble around the four icons on the lock screen, so I went in to modify that and then found more files to change and so it began. And so while I'm on it, why do some m10s decode and some don't? Gingeritis3D and ShiftS3NS3 v3.0 have a default folder, but others have Blue Sky, etc. The default folder that has sharedm10 will decode but the others don't. Just curious. I'm using ShiftS3NS3 v3.0 as my base ROM to theme, by the way.
Click to expand...
Click to collapse
I'm not much of a themer, but I might be able to help you with the signing.
You have to sign an APK any time you decompile and recompile it. Alternatively, if you use apktool, build the apk, then take the META-INF folder and AndroidManifest.xml from the original apk and copy them to the /build/app folder of the decompiled apk. Rebuild and your apk is signed. Your essentially taking the signature from the original apk and copying it to the one you recompiled.
If you want the zip to flash, you have to sign it. If you remove anything from an already signed zip, you have to resign it.
orkillakilla said:
I'm not much of a themer, but I might be able to help you with the signing.
You have to sign an APK any time you decompile and recompile it. Alternatively, if you use apktool, build the apk, then take the META-INF folder and AndroidManifest.xml from the original apk and copy them to the /build/app folder of the decompiled apk. Rebuild and your apk is signed. Your essentially taking the signature from the original apk and copying it to the one you recompiled.
If you want the zip to flash, you have to sign it. If you remove anything from an already signed zip, you have to resign it.
Click to expand...
Click to collapse
That makes total sense. I get it now. Thanks!
orkillakilla said:
I'm not much of a themer, but I might be able to help you with the signing.
You have to sign an APK any time you decompile and recompile it. Alternatively, if you use apktool, build the apk, then take the META-INF folder and AndroidManifest.xml from the original apk and copy them to the /build/app folder of the decompiled apk. Rebuild and your apk is signed. Your essentially taking the signature from the original apk and copying it to the one you recompiled.
If you want the zip to flash, you have to sign it. If you remove anything from an already signed zip, you have to resign it.
Click to expand...
Click to collapse
Sorry I seen this thread, and was wondering if you use metamorph to theme if you add the META-INF folder and the AndroidManifest.xml to the respective theme will the .apk be able to be installed into the data/app folder?
Deftoolfinch said:
Sorry I seen this thread, and was wondering if you use metamorph to theme if you add the META-INF folder and the AndroidManifest.xml to the respective theme will the .apk be able to be installed into the data/app folder?
Click to expand...
Click to collapse
Not sure. I don't use metamorph so I can't help you there. Sorry.
Sent from my ADR6400L using xda premium
I don't use metamorph. I modify the .apk then flash in recovery. Meta and ninja morph aren't necessary once you get the hang of flashing .zips.
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
Is it necassary to sign systemui.apk? I made some changes to the file and now when i flash the ROM I get systemui force closes
Sent from my PG86100 using xda app-developers app
kevin130 said:
Is it necassary to sign systemui.apk? I made some changes to the file and now when i flash the ROM I get systemui force closes
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
No, you don't ever want to sign system apps. Are you sure the permissions are correct? and what changes did you make?
I didn't put any permissions. How do I set them in the zip? And I change the 3g icon to 4g because I have virgin mobile so I can't get 4g but I want it to say 4g lol.
Sent from my PG86100 using xda app-developers app
Well if you are installing it with a zip permissions are probably correct. I'm assuming you decompiled the apk changed the icon and compiled it again? If all you want to do is change an icon, just open the apk with 7zip or similar and replace the icon, no need to decompile. That should solve it. Let me know
Okay. I'll try that and if I do decompile it, how do I set the permissions? Cuz i decompiled settings.apk and made a XML change.
Sent from my PG86100 using xda app-developers app
kevin130 said:
Okay. I'll try that and if I do decompile it, how do I set the permissions? Cuz i decompiled settings.apk and made a XML change.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
You would set permissions if you are just pushing the apk to your phone. Better question, how exactly are you installing the apk after you made the changes?
I just replace the old apk in the zip file and flash the ROM.
Sent from my PG86100 using xda app-developers app
ok, then the updater-script in the zip is handling the permissions for you, so you don't need to worry about that.
So there is no need to sign anything at all? Awesome.
Sent from my PG86100 using xda app-developers app
Apps in /system/app/ never get singed, apps in /data/app/ however have to be signed.
Alright. Thanks.
Sent from my PG86100 using xda app-developers app
Android commander... http://androidcommander.com/
great tool you should use when first dealing with androids..
you can delete/pull/push files to your phone there also apk backup which backs up your apps from the play store.. just a great program to have in your PC.
no problem, let me know if you still need help or get it working
Hi I'm also trying to learn modifying systemUI.apk through smali edits
So as a start I just decompiled my systemUI.apk with apktool v1.5.2 with no errors. Then directly recompiled it. No modifications made. The resulting apk didnt have any META-INF folder and thus I suppose is unsigned. But pushing this apk to /system/app doesn't install it.. As a result after reboot I have no installed systemUI.apk
What am I doing wrong? BTW I'm on Sony xperia live with walkman. But I suppose this is a general thing. And yes I have installed all framework files and as a result no errors while de/recompiling
havocgb said:
Hi I'm also trying to learn modifying systemUI.apk through smali edits
So as a start I just decompiled my systemUI.apk with apktool v1.5.2 with no errors. Then directly recompiled it. No modifications made. The resulting apk didnt have any META-INF folder and thus I suppose is unsigned. But pushing this apk to /system/app doesn't install it.. As a result after reboot I have no installed systemUI.apk
What am I doing wrong? BTW I'm on Sony xperia live with walkman. But I suppose this is a general thing. And yes I have installed all framework files and as a result no errors while de/recompiling
Click to expand...
Click to collapse
The best way in case of small edits is to open both your stock and your modified SystemUI.apk with 7-zip, then copy the META-INF and AndroidManifest.xml from the stock to the modded one.
Close both and push back your modded one to the phone.
Guess that work.
pquinqu said:
The best way in case of small edits is to open both your stock and your modified SystemUI.apk with 7-zip, then copy the META-INF and AndroidManifest.xml from the stock to the modded one.
Close both and push back your modded one to the phone.
Guess that work.
Click to expand...
Click to collapse
Well now I use APK Multi-Tool and it works great. From what I have understood it keeps the same signatures as in the original SystemUI.apk and there is no need of any resigning.