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
It's impossible to please everyone and everyone has their personal preferences. This tutorial is for when rom devs don't make what you want! As the title says it's just for battery mods but you can apply this to almost anything to get what you want. I'm going to try and make this as easy as possible. From start to finish. Please read the whole post! I hope this helps at least someone~
First things first. You need to go and download 7zip. Ok.
Now you need to go and find which battery icon images you'd like. For this example, we're going to download the Trigger theme kit. Click here to download. In the kit, I have 3 sets of battery images you can choose from. Let's do it with the semi-accurate batteries.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Conveniently, I have already named them properly for you! These names are pretty consistent throughout all the Vibrant ROMs I believe, but just be aware that it depends on the framework and the accurate battery mod built into the framework.
Next we need the framework to place these in. I'm going to use Trigger as an example. But you can use any ROM or framework. So if you are using it from a ROM, you need to first open it.
I'd suggest you familiarize yourself with this structure if you already don't know it! Just poke around and see what's where.
Next navigate to the system directory, then framework. Here's what you should see.
The images for the batteries (along with most other system related images) are in framework-res.apk. Pull it out to a new directory. I've got it in the same directory as my theme kit.
After that, you need to right click on the APK and go to the 7-zip option and click open archive.
Many of you probably already know this, but too much information never hurts! APKs are basically renamed zip files. When they are compiled all the files inside are compiled into binary format so you cannot edit them unless you decompile the framework. The exception are images. This is why we can do this and edit them without having to make a new file. We can just open it and replace what we want and replace it back!
Ok so next, after you open it you'll see a couple directories. You need to go to the res directory. In here are more folders! You want to find one that is named drawable-hdpi or drawable-hdpi-v4. In here is the jackpot. You will find the battery images in there, too.
Now here's the magic! Select all the images from the batt_semi-accurate batteries folder and drag them into the opened zip archive (into the res/drawable-hdpi folder)!
7zip will pop up a dialog asking if you want to overwrite or something. Click yes.
Now your framework is ready to be put on your phone!
You can do this one of two ways. Either make a flashable for your phone. Or transfer it via adb in recovery. I like doing method b but I'll briefly go over both.
method A:
I've attached a flash.zip. It contains the new framework I've gone over how to make in this tutorial. Only it is flashable. You can either use it (but replacing the framework-res.apk with the one you're working with) or you can take some time to learn how it's made!
*I made this flashable zip with my ACS tool (link in sig). You can do the same! Open the tool, go to options, make sure you click the checkbox next to system, close options. Click generate zip. You now have an empty flashable zip. You needed to click the systme checkmark because now it knows to transfer anything in the system directory in the zip file to the system directory on your phone. So basically you need to replicate the directory structure. If you open my zip you can see I've done so.
method B:
You need to know how to use adb and command line somewhat to do this. This isn't an ADB guide so please google one to brush up.
Boot your phone into clockwork recovery. And open up a new command line. You need to get into the same folder where your new framework-res.apk is.
commands are pretty basic, cd to change directory.
next you need to run the command to push the file onto the right place on your phone
Code:
adb push framework-res.apk /system/framework/
that should do the trick. it should say transferred in x seconds blah blah. once that's done. reboot. done.
Hi,
Thank you for the info. I have tried this method with original ROM framework-res.apks and THEME framework-res.apks. The only one that I got to function was Glasstopia. The other ones have always caused a boot-loop after getting to the main screen. Some people have responded that it was maybe faulty png files and some say that it was caused by something in the xmls. I just thought this was important to mention.
This is exactly what I wanted but I have a few questions. I have created a theme but when I added the battery images that wanted in there I found that it only decreases in 20% intervals and I want it to decrease in 1% intervals. Im assuming that the theme I based it off of had it in that interval. Any help is greatly appreciate it.
Sent from my SGH-T959 using XDA App
MeximCivic said:
This is exactly what I wanted but I have a few questions. I have created a theme but when I added the battery images that wanted in there I found that it only decreases in 20% intervals and I want it to decrease in 1% intervals. Im assuming that the theme I based it off of had it in that interval. Any help is greatly appreciate it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
You'd need to modify Stat_Battery.xml and Stat_Battery_Charge.xml in /res/drawable/
In order to do this you must first decompile (not unzip) the framework.
MWBehr said:
You'd need to modify Stat_Battery.xml and Stat_Battery_Charge.xml in /res/drawable/
In order to do this you must first decompile (not unzip) the framework.
Click to expand...
Click to collapse
Correct me if I'm wrong, but I believe entries need to be made to the public.xml to account for the new images added to the framework as well. Thats been my biggest hindrance in brining an accurate battery to loki, I always borke the public.xml entries. Ive booted without adding those lines and had no battery at all. Again, I may be wrong but I think those entries are necessary.
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
Correct me if I'm wrong, but I believe entries need to be made to the public.xml to account for the new images added to the framework as well. Thats been my biggest hindrance in brining an accurate battery to loki, I always borke the public.xml entries. Ive booted without adding those lines and had no battery at all. Again, I may be wrong but I think those entries are necessary.
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
Not if you're compiling it. Public.xml (or realistically resources.arsc) is updated automatically with any new additions to the drawable folders.
MWBehr said:
Not if you're compiling it. Public.xml (or realistically resources.arsc) is updated automatically with any new additions to the drawable folders.
Click to expand...
Click to collapse
I never knew that, I thought it had to be edited prior to compiling. (Facepalm) Behr, I may end up picking your brain on a couple more framework questions one of these days. And never officially said it, welcome to the team!
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
I never knew that, I thought it had to be edited prior to compiling. (Facepalm) Behr, I may end up picking your brain on a couple more framework questions one of these days. And never officially said it, welcome to the team!
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
Thanks I feel I should clarify, if you're needing to reference these new pngs in the classes.dex, then it would become neccessary to make the addition.
That brings up an interesting question I ran into a couple versions back. I took my framework, still compiled, added in the pngs I wanted to use for my battery, both necessary battery xmls provided by the creator of that particular mod, and pushed, when I rebooted I had no battery image at all. Booted without error, and the best battery mod ever, infinite! I almost released it as a joke. Then grumbled back to the lab in a vain attempt to fix it. I figured the only thing that could have been amiss was the public.xml entries. Could there have been a more obvious culprit that I overlooked?
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
That brings up an interesting question I ran into a couple versions back. I took my framework, still compiled, added in the pngs I wanted to use for my battery, both necessary battery xmls provided by the creator of that particular mod, and pushed, when I rebooted I had no battery image at all. Booted without error, and the best battery mod ever, infinite! I almost released it as a joke. Then grumbled back to the lab in a vain attempt to fix it. I figured the only thing that could have been amiss was the public.xml entries. Could there have been a more obvious culprit that I overlooked?
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
It's an issue with the compiled xmls themselves I believe. Pushing xmls from another framework has always been hit and miss in my experience, and abandoned the proccess altogether awhile back. A guarantee you, however, that if you decompile both, copy over the xmls and pngs, and recompile, that you'll have no issue what-so-ever.
MWBehr said:
It's an issue with the compiled xmls themselves I believe. Pushing xmls from another framework has always been hit and miss in my experience, and abandoned the proccess altogether awhile back. A guarantee you, however, that if you decompile both, copy over the xmls and pngs, and recompile, that you'll have no issue what-so-ever.
Click to expand...
Click to collapse
Its the recompiling I can never seem to get, never boots when I do and leaves out the compiled xml every time I try. We'll have to jump on Gtalk or pm, so we dont hijack birgers thread here, sorry roman. if you use Gtalk feel free to add me from my addy in my profile, its always on on my phone.
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
Its the recompiling I can never seem to get, never boots when I do and leaves out the compiled xml every time I try. We'll have to jump on Gtalk or pm, so we dont hijack birgers thread here, sorry roman. if you use Gtalk feel free to add me from my addy in my profile, its always on on my phone.
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
Don't see an address in your profile
Anyway, here's the trick to get it to compile for ya:
1. Use APK Manager
2. Make sure all .9.pngs are ok (easy way to check this is scroll through and make sure you have a thumbnail for every image).
3. When compiling, hit "y" when it asks if it's a system apk and then "y" again to build the "keep" directory.
4. Go to the "keep" directory and delete ONLY what you changed (you also must delete resources.arsc if moddifying xmls, classes.dex if moddifying smali, and Meta-INF folder if modding AndroidManifest.xml)
5. Don't sign unless you modified AndroidManifest.xml
That's it, should work with uncommon exceptions. Let me know if those exceptions come up
Battery Indicator Decrease Intervals
I'm sorry but I'm still having trouble getting my theme to decrease in 1% intervals rather than the 20% intervals the ROM came with. I know they mentioned decompile the theme first then what?
I decompiled it with apk manager then i replaced the stat_sys_battery.xml and stat_sys_battery_charge.xml and recompiled it and signed it but when I flashed the theme now I don't have a battery indicator on my status bar lol!
Any help is greatly appreciate it! if it makes it easier my gtalk is shadow3166. Thanks!
MeximCivic said:
I'm sorry but I'm still having trouble getting my theme to decrease in 1% intervals rather than the 20% intervals the ROM came with. I know they mentioned decompile the theme first then what?
I decompiled it with apk manager then i replaced the stat_sys_battery.xml and stat_sys_battery_charge.xml and recompiled it and signed it but when I flashed the theme now I don't have a battery indicator on my status bar lol!
Any help is greatly appreciate it! if it makes it easier my gtalk is shadow3166. Thanks!
Click to expand...
Click to collapse
First, never resign.
Second, assuming you were following the steps I outlined above, are you sure you deleted the xmls from the keep directory?
Third, did you copy over the 120ish pngs for the battery icons?
If you did all that, upload your framework and let me have a look.
MWBehr said:
Don't see an address in your profile
Anyway, here's the trick to get it to compile for ya:
1. Use APK Manager
2. Make sure all .9.pngs are ok (easy way to check this is scroll through and make sure you have a thumbnail for every image).
3. When compiling, hit "y" when it asks if it's a system apk and then "y" again to build the "keep" directory.
4. Go to the "keep" directory and delete ONLY what you changed (you also must delete resources.arsc if moddifying xmls, classes.dex if moddifying smali, and Meta-INF folder if modding AndroidManifest.xml)
5. Don't sign unless you modified AndroidManifest.xml
That's it, should work with uncommon exceptions. Let me know if those exceptions come up
Click to expand...
Click to collapse
Sorry bout that I forgot I hid it in my profile. I'll pm you.
Those are my steps, I use apk manager and do remove the resources.arsc when editing the xmls. Compile without errors. If I decompile again, the edited xml is just not there. I'll figure it out sooner or later, other apks give me no issue, just framework.
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
Sorry bout that I forgot I hid it in my profile. I'll pm you.
Those are my steps, I use apk manager and do remove the resources.arsc when editing the xmls. Compile without errors. If I decompile again, the edited xml is just not there. I'll figure it out sooner or later, other apks give me no issue, just framework.
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
But you're also deleting the individual xmls right?
MWBehr said:
But you're also deleting the individual xmls right?
Click to expand...
Click to collapse
Yes, from the keep folder when compiling, and also deleting the resources when the xml that was edited is in there.
Got ya added to gtalk. Thx.
Sent from my Loki powered Vibrant on the XDA App
Sending Log.txt and Framework
Ok so I continued to use this procedure but keep getting errors on the 9.png there's errors that appear constantly. below is my log file and my framework-res.apk let me know what I'm doing wrong I just want to be able to recompile the .apk with the new status_sys_battery.xml and status_sys_battery_charge.xml
Thank You!!!!
MeximCivic said:
Ok so I continued to use this procedure but keep getting errors on the 9.png there's errors that appear constantly. below is my log file and my framework-res.apk let me know what I'm doing wrong I just want to be able to recompile the .apk with the new status_sys_battery.xml and status_sys_battery_charge.xml
Thank You!!!!
Click to expand...
Click to collapse
are you using the bionix framework as a base?
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime."
Thanks for the tutorial, in other words.
I've been trying to make a couple of modifications to framework-res.apk and I've been having a lot of trouble. I've bootlooped the DX2 more than a few times (and was able to recover with the recently released SBF).
I've tried making one change, I've tried signing the file, I've tried not signing it, I've tried different compression levels on the zip, all with no luck. The one time I got my apk into the phone with my change on board (I verified that it was there) my change was ignored by the phone. (I've been trying to replace /res/drawable-hdp/zz_moto_list_texture_bg.png to change the default list background from the light gray to black.)
Has anyone been successful making modifications to this file in a DX2? If so, how did you do it?
What did program did you zip it with?
What was the compression set to?
Did you sign the file? If so, with what program and key?
What method did you use to drop framework-res.apk back into the phone?
Are there any files that should not be modified? (I've heard to leave the ".9" files alone.)
Thanks,
Chris
I've been trying to do the exact same thing and haven't got too far. I'm doing dev stuff thru Ubuntu and it seems to be very friendly along with gimp. I've actually been able to drag and drop replacement files without extracting the apk but haven't been able to flash it inside a theme. I haven't actually tried just replacing the framework.
Staying tuned...
Sent from my DROID X2 using XDA App
You can make a theme at uot.dakra.lt and flash the .zip file to your phone.. jus upload your framework-res.apk to the site once you make it, but anyway, they modify the file and it worked for me.
Peperm1nt said:
You can make a theme at uot.dakra.lt and flash the .zip file to your phone.. jus upload your framework-res.apk to the site once you make it, but anyway, they modify the file and it worked for me.
Click to expand...
Click to collapse
Yes I've been using this but it's not really set up for blur. we're talking about going deeper than UOT can reach with current software.
Sent from my DROID X2 using XDA App
You can recompile and decompile with apkmanager, but its not without some hiccups. First, it compresses the resources.arsc which unlike the rest of the apk needs to be decompressed. To fix this I pull it out then with 7zip I add it back to the framework-res archive with zip as the format and store as compression. That fixes the boot-loops. Even after that there's been some minor problems with it recompiling certain .xml a little goofy.
But at least it doesnt cause a boot loop.
Posted it here because i need a dev.
I pulled my Framework-res.apk and modified all the icons for everything. I decompiled using apktool.
My question is what steps do i take now (do i need to sign it, what a good tool to recompile it as apktool does and gives me a framework-res.apk but caused my phone not to boot up)..also someone said seomthing about resources.arsc or something..not sure where to go...thanks for your help.
Open ur new apk using 7zip (righr click>7zip>open archive) and do the same with ur old one. Delete the resources.xxxx(i dont know the name by heart lol) and drag and drop the one (by one i meant the resources.xxxx file) from the new zip to the old zip and adb push ur old frameworkres apk and reboot
Sent from my PG86100 using XDA App
kpkimmel said:
Posted it here because i need a dev.
I pulled my Framework-res.apk and modified all the icons for everything. I decompiled using apktool.
My question is what steps do i take now (do i need to sign it, what a good tool to recompile it as apktool does and gives me a framework-res.apk but caused my phone not to boot up)..also someone said seomthing about resources.arsc or something..not sure where to go...thanks for your help.
Click to expand...
Click to collapse
sounds more like a question. Use apk manager and or 7zip
how does just that one file carry over all the new pics and stuff i changed...
edited......
What exactly have you edited? If you just change non patch9 images... then you can just drag and drop the new images into the apk (may have to rename apk to zip).
If they are patch9's... you need to..
decompile framework-res.apk (apktool d framework-res.apk)
swap out images
recompile (apktool b framework-res)
Now take the newly compiled apk (in the /dist folder). Open it up and take the edited images (only the ones you need changed) and put them into your original apk.
No need to resign just push it to your phone and verify that it works
If you are editing xml files in /values* or /layout..
do the same as above, except after re-compiling, you're going to swap over the resources.arsc file to the original apk.
This is using apktool... in my experience apk manager doesn't do the job to my expectations... so i just do it manually with apktool.
Lemme know if u need anything more, or if i didnt touch on a specific situation.
Btw, maybe to combat the retarded comments about q&a and being in the right section... maybe turn the OP into a How-To?
preludedrew said:
What exactly have you edited? If you just change non patch9 images... then you can just drag and drop the new images into the apk (may have to rename apk to zip).
If they are patch9's... you need to..
decompile framework-res.apk (apktool d framework-res.apk)
swap out images
recompile (apktool b framework-res)
Now take the newly compiled apk (in the /dist folder). Open it up and take the edited images (only the ones you need changed) and put them into your original apk.
No need to resign just push it to your phone and verify that it works
If you are editing xml files in /values* or /layout..
do the same as above, except after re-compiling, you're going to swap over the resources.arsc file to the original apk.
This is using apktool... in my experience apk manager doesn't do the job to my expectations... so i just do it manually with apktool.
Lemme know if u need anything more, or if i didnt touch on a specific situation.
Btw, maybe to combat the retarded comments about q&a and being in the right section... maybe turn the OP into a How-To?
Click to expand...
Click to collapse
Thank you very much..finally...one last question, where do i put the wallpaper so when the system is fully booted it shows the wallpaper i want? Thanks.
kpkimmel said:
Thank you very much..finally...one last question, where do i put the wallpaper so when the system is fully booted it shows the wallpaper i want? Thanks.
Click to expand...
Click to collapse
There's an xml edit for it... but forgot it off the top of my head... quickest way is to replace system/customize/resource/shows_over.jpg with your image.
preludedrew said:
There's an xml edit for it... but forgot it off the top of my head... quickest way is to replace system/customize/resource/shows_over.jpg with your image.
Click to expand...
Click to collapse
Thanks you, sorry about the stupid framework-res question...i knew the answer but had been so long forget the simplest of steps....instead of normal compression i was using store instead.....duh.......thank you though for the reminder because 7zip will automatically restore the same it was decompressed with, unlike that crap winrar. Have a good one man and thank you again.
I tried to decompile, modify 1 xml file and recompile the framework-res.apk.
But everytime I do it, I either get into a boot loop, or when In succeed it displays glitches (like notification bar, and messed up lock screen, and settings)
This is for AURORA ICS 4.0.3 and I do have the latest aapt.exe file .. so I don't know what is wrong!
I tried to use the original framework-res but replace the resources file inside, stored and compressed methods.
Tried to get the compiled framework-res but add the META-INF and Manifest file (again, both with compressed and stored resources file) and always.. it just glitches or bootloops.. and the mod that I tried (ICS on screen buttons or the CRT effect when you switch off the screen, mainly used in Oxygen roms, but it's available in all ROMs).. it never works.. only glitches the lock screen, notification bar etc..
Any help?
Thanks.
I might know the answer to this..
Which files are you modifying in framework-res? And how are you pushing it back to your phone?
Sent from my U20i using xda premium
Would be great
I am modifying some files in the values folder, bools.xml, arrays.xml .. but even if I edit bools.xml alone, it still glitches.
To push it back: I go to recovery mode on my phone, plug it into my linux machine (the system partition mounts), paste the new framework-res.apk to replace the old one, fix permissions (otherwise it boot loops), and restart the phone. This method works for other files and never had any problems, like the android.policy.jar
Would be great if you can help me. Thanks
Well, the XML files you're editing are all part of resources.arsc so it's something to do with that which is causing the problem. I used to get all sorts of annoying bugs when I edited anything in resources.arsc and I eventually found out that I was pushing the final apk back to the phone incorrectly.
I use a Windows PC, not Linux, so I might not be that helpful but this is what I do to modify and replace framework-res.apk. Hopefully it'll help. What I do is..
Decompile framework-res.apk
Make my changes
Recompile the file
Use a program like 7zip to open the old and the new files
Drag and drop the "res" folder from the new file into the old
Extract resources.arsc from the new framework-res.apk and add it to the old one in "STORE" mode, so it's not actually compressed
Go into recovery, mount the system partition and push the old file
..and that's it. Works a charm every time.
I would have thought that you would need to do the same thing on Linux but with the additional step of correcting the permissions. If you do all that and it still doesn't work, then there has to be a problem with the actual mod you're trying to do.
Thank you very much, I actually tried that method. It sort of worked, but everytime it breaks the notification bar. It becomes like double the size and I'm not sure why.
Thanks.
Then the issue must be with the modification itself. What exactly are you changing to what?
Sent from my U20i using xda premium
I tried different ones.. but even a simple one.. enable CRT animation.. which is pretty much open bools.xml and edit one true to false.. it breaks it :/