Related
ok, so I am working on reskinning sense, I'm using DamageControl 2.1 right now and I was able to edit some of the files used in com.htc.resources.apk without problem.
The problem I am having right now is whenever I try and modify a file in rosie, repack and resign and adb push it back to the phone, sense force closes until I revert back to the orginial file, has anyone run into the same issue?
I am going to download the latest framework to see if there might be an issue with signing caused by not having the latest one. I really can't remember which version I'm running.
i give you credit, i wouldn't even attempt to try this on my phone.
Quick question, is there a reason why you're resigning the .apk? There is no need too.
I was under the impression, perhaps uneccesarily, that whenever you modify an apk it needs to be resigned to prevent problems.
I've always done this, I have never had a problem with that practice in the past which is why it perplexed me now. As I already stated, there was no problems when I modified com.HTC.resources.apk
I'm drunk
obelisk79 said:
ok, so I am working on reskinning sense, I'm using DamageControl 2.1 right now and I was able to edit some of the files used in com.htc.resources.apk without problem.
The problem I am having right now is whenever I try and modify a file in rosie, repack and resign and adb push it back to the phone, sense force closes until I revert back to the orginial file, has anyone run into the same issue?
I am going to download the latest framework to see if there might be an issue with signing caused by not having the latest one. I really can't remember which version I'm running.
Click to expand...
Click to collapse
There is images where the name is yadayad08.png, well the number might not be 08 it might be another number and i really dont feel like diggin into it right now, but the images with that number in the end have scripts attatched to the or it written into the image. Have you looked into that. Sorry if I have been %100 clear but ther is images with scripts actually written inside of them......... if you can follow what i'm sayin...:\ I'm drunk......... anyway i'll look into it right now and be back so I dont look like a complete douchebag
So some images have a script stored in the same file? I have never heard of that before. I'd like to see some examples if possible, and how exactly do you modify them?
Time to put my Google-fu to good use.
Edit: whatcha drinking?
The file I am trying to modify is common_mainnav_scroller3.png. maybe that will help. I'm not at my laptop right now, so I am not able to try modifying it without resigning.
I also found some info about the images with scripts attached to them. I have a utility now to modify that stuff, however looking around some more I also think the files with a filename.9.png are the applicable files. I'm not modifying them right now.
obelisk79 said:
The file I am trying to modify is common_mainnav_scroller3.png. maybe that will help. I'm not at my laptop right now, so I am not able to try modifying it without resigning.
I also found some info about the images with scripts attached to them. I have a utility now to modify that stuff, however looking around some more I also think the files with a filename.9.png are the applicable files. I'm not modifying them right now.
Click to expand...
Click to collapse
yea i know forsure the.9 files have scripts attached however if your just changing something as small as an icon I don't think it should matter. Not sure though, i was trying to port a theme and i ran into this situation im not a linux guru so I kind of gave it up
I do not resign the .apk after modifying them If you are only changing images just make sure the new image has the same name and just open the .apk and drag n drop the image into the folder where it needs to be it will over write the old image and store the new one.
I have modified the Rosie.apk and com.htc.resources.apk many times to change things in the taskbar change over to Espresso etc
if you are only changing .png files just drag and drop.
Also like cheyne1 said files or .png's with xxxx.9.png etc in them are more than just .png files and replacing them will cause all sorts of issues if the new file is not made correctly
well, lesson learned... drag-n-drop worked. didn't think rosie apk was going to be so testy. thanks for the help.
Please delete this thread.
Im keeping this on my phone forever!
how do you get this to work it aborted when flashing in recovery??
Okay here's the thing. It's not flashing in recovery because you are missing the update-script (usually found under a few subfolders within the meta-inf folder. take a look at someone elses update.zip (for anything, theme, rom, some of my keyboard themes etc) and you should find what I'm talking about.
Second problem, the framework-res.apk you provided contains only your changes. Had this successfully flashed, you'd now be boot looping as your framework-res.apk would be jacked up.
I took your images and made them into a morph (hope you don't mind, I put your name on the "author" line). I just applied it via metamorph and it's working great!
Benefit to this is it *should* be cross rom compatible, and shouldn't need any updates (whereas if you built a true update.zip that contained all of framework-res.apk, you'd have to update it every time it changed and release different versions for different roms).
Feel free to grab this attachment and throw it on first post!
remember, it's a metamoprh, you must have metamorph from the market to apply it!
kamikazimonky said:
how do you get this to work it aborted when flashing in recovery??
Click to expand...
Click to collapse
Right now unfortunately you can't flash through recovery yet.
I am hoping to have a fix for that later tonight.
See post above. You can now use this with Metamorph thanks to gIMpSTa.
LOL....
This is great!
One thing though, can you make it a bit more discernable for us colour blinds?
hmmm I posted this on the MORPH thread yesterday!
http://forum.xda-developers.com/showpost.php?p=6056140&postcount=7
If you want to get a mod to delete my post and put yours in there that would be fine by me.
I have no idea how to delete this off my captivate. I reset my phone, format internal sd and reflashed the unleashthebeast rom. Please help me. Its still there! I want the original battery icon back
Link to apk file:
forum.xda-developers.com/showthread.php?t=624416
I'm running rooted stocked 2.1...5 with this mod installed. I tried to put it in the system/app folder because there is some room in there, since I removed some apps, but it did not like it. It just kept foreclosing it.
Any idea how to put it in there or even replace the original HTC_IME?
could have something to do with it being made for the nexus one
obsanity said:
Link to apk file:
forum.xda-developers.com/showthread.php?t=624416
I'm running rooted stocked 2.1...5 with this mod installed. I tried to put it in the system/app folder because there is some room in there, since I removed some apps, but it did not like it. It just kept foreclosing it.
Any idea how to put it in there or even replace the original HTC_IME?
Click to expand...
Click to collapse
i've made one from there, and installed it. I didn't push it to /system/app.
try doing that.
also make sure you are using the low res option.
obsanity said:
Link to apk file:
forum.xda-developers.com/showthread.php?t=624416
I'm running rooted stocked 2.1...5 with this mod installed. I tried to put it in the system/app folder because there is some room in there, since I removed some apps, but it did not like it. It just kept foreclosing it.
Any idea how to put it in there or even replace the original HTC_IME?
Click to expand...
Click to collapse
First make sure you downloaded the "lo" version, since Hero is low-res. And unpack the ZIP. It's not flashable, it's just zipped for convenience.
And then you can just install HTC_IME_lo.apk from your file manager by clicking it. There's no need to manually push it into /system/app. (It's registered differently from the default HTC_IME, so it can be installed like any normal application.) If you removed Clicker.apk while you were removing junk from /system/app, you'll need to reinstall that as well.
If you really want to replace the original HTC_IME, just rename HTC_IME_lo.apk to HTC_IME.apk and push it to /system/app. I think that's what you were trying to do before.
Hope this helps!
Oh, sorry I guess I forgot to mention that it is running fine in the user folder after installing it. It's just that I wanted to put in the system/app folder to save some space. I'll try renaming it and replacing with the stocked file. BTW, I'm typing on it now and its way better than the stocked because of how much customization you can do.
I finally tied this and it's a no go. Still get FC messages. However, all seems fine when I install it as an app. I think it's because the HTC_IME.odex file which is tied to the original. Even after rebooting it didn't work.
Anyone know how to get that odex file from the new HTC_IME I'm trying to install in the system/app folder?
Edit: I was looking for a zipped, rooted version of 1.47.651.1 and didn't find it, so I made one and posted it. Turns out I had just missed caulkin's post, so my post is now pretty pointless. If a mod wants to delete the thread, that is fine. I apologize for clogging things up, I was intending to provide a resource to make things easier for other people.
Here is caulkins: http://forum.xda-developers.com/showthread.php?t=712695
#######################################################
I haven't seen a rooted stock of the latest OTA ROM (1.47.651.1) so I made one. I added superuser, busy box, and left everything else the same. I'll probably add a deodexed version and stripped version soon.
odex-1.47.651.1
I'm pretty new to the Android world, but I think no one had put this up yet because it is pretty easy to do, but a pain to upload. Let me know if there are any issues, but in my testing it has been fine, market works, etc. Also, if this is out there, let me know, or delete the thread, but the only post I saw with this had a dead link.
This is just the images from whitslacks expanded into the more familiar zip package like most of the cooked roms are distributed. If you are running whitslacks this would be no different.
Thanks to:
dsixda for the kitchen
whitslack for the one shot image I pulled this out of
community in general
So u rooted the evo with the update?
Sent from my PC36100 using Tapatalk
laydros said:
I haven't seen a rooted stock of the latest OTA ROM (1.47.651.1) so I made one. I added superuser, busy box, and left everything else the same. I'll probably add a deodexed version and stripped version soon.
odex-1.47.651.1
I'm pretty new to the Android world, but I think no one had put this up yet because it is pretty easy to do, but a pain to upload. Let me know if there are any issues, but in my testing it has been fine, market works, etc. Also, if this is out there, let me know, or delete the thread, but the only post I saw with this had a dead link.
Thanks to:
dsixda for the kitchen
whitslack for the one shot image I pulled this out of
community in general
Click to expand...
Click to collapse
Here is whitslacks rooted 1.47 ROM:
http://forum.xda-developers.com/showthread.php?t=715915
Works perfectly, I haven't had any issues with it and I flashed it about 3-4 days ago.
vballboarder said:
Here is whitslacks rooted 1.47 ROM:
http://forum.xda-developers.com/showthread.php?t=715915
Works perfectly, I haven't had any issues with it and I flashed it about 3-4 days ago.
Click to expand...
Click to collapse
Yes, this is actually based on whitslack's. His work may be more useful, but his is a full package that replaces everything (radio, recovery, etc), and requires another flash to root.
This is just a standard rom that can be installed via clockwork or RA and doesn't change any of the other pieces.
More than anything it may be a building block for other roms, especially once I get a deodexed version up.
Caulkin also has a rooted stock Rom as well odex and deodexed in this forum. He was the first to put it out like the day the ota was released
xxbabiboi228xx said:
Caulkin also has a rooted stock Rom as well odex and deodexed in this forum
Click to expand...
Click to collapse
You are right. I looked quite a bit for this, but it didn't get a lot of posts in the last few days so it hasn't been in the top often.
laydros said:
Yes, this is actually based on whitslack's. His work may be more useful, but his is a full package that replaces everything (radio, recovery, etc), and requires another flash to root.
This is just a standard rom that can be installed via clockwork or RA and doesn't change any of the other pieces.
More than anything it may be a building block for other roms, especially once I get a deodexed version up.
Click to expand...
Click to collapse
Okay, I've spent quite a bit of time trying to figure this whole root thing out and I've got a pretty good handle on rooting and flashing ROM, but can't find what's the deal with odexed versus de-odexed? I imagine there's a different thread with this info and a little off topic from the original intent of this thread. If anyone has a link, I'd appreciate it.
Now that I've already done whitslacks 1.47 rooted rom, I should be fine with that, correct? What you're doing here doesn't necessarily apply if one has already done whitslacks and is happy with it?
Thanks, still learning this stuff.
vballboarder said:
Okay, I've spent quite a bit of time trying to figure this whole root thing out and I've got a pretty good handle on rooting and flashing ROM, but can't find what's the deal with odexed versus de-odexed? I imagine there's a different thread with this info and a little off topic from the original intent of this thread. If anyone has a link, I'd appreciate it.
Now that I've already done whitslacks 1.47 rooted rom, I should be fine with that, correct? What you're doing here doesn't necessarily apply if one has already done whitslacks and is happy with it?
Thanks, still learning this stuff.
Click to expand...
Click to collapse
I'm quite new and may have some of this wrong, but I think I'm close:
When a developer makes an application file, it is an apk. The apk is actually a zip file with information inside on how to install, name of the file, and resources used in the application, like pictures used for buttons. If the file is not odexed, then there is also a .dex file contained which has the actual program code used by the virtual machine. If a file is odexed then there is a separate file with the same name as the apk, but has the extension .odex. This is done by htc to the system files to make things (arguably) a little faster.
Dev's then deodex the files to put the odex file back into the apk as a .dex file, if this is desired. The reason for this is so that they can be changed later to do something like theming.
Yes, this is the same as whitslack's. If you wanted a de-odexed ROM you could now grab the one caulkin posted and flash it.
laydros said:
I'm quite new and may have some of this wrong, but I think I'm close:
When a developer makes an application file, it is an apk. The apk is actually a zip file with information inside on how to install, name of the file, and resources used in the application, like pictures used for buttons. If the file is not odexed, then there is also a .dex file contained which has the actual program code used by the virtual machine. If a file is odexed then there is a separate file with the same name as the apk, but has the extension .odex. This is done by htc to the system files to make things (arguably) a little faster.
Dev's then deodex the files to put the odex file back into the apk as a .dex file, if this is desired. The reason for this is so that they can be changed later to do something like theming.
Yes, this is the same as whitslack's. If you wanted a de-odexed ROM you could now grab the one caulkin posted and flash it.
Click to expand...
Click to collapse
Thanks, been wondering wtf deodex'd, etc meant.
laydros said:
I'm quite new and may have some of this wrong, but I think I'm close:
When a developer makes an application file, it is an apk. The apk is actually a zip file with information inside on how to install, name of the file, and resources used in the application, like pictures used for buttons. If the file is not odexed, then there is also a .dex file contained which has the actual program code used by the virtual machine. If a file is odexed then there is a separate file with the same name as the apk, but has the extension .odex. This is done by htc to the system files to make things (arguably) a little faster.
Dev's then deodex the files to put the odex file back into the apk as a .dex file, if this is desired. The reason for this is so that they can be changed later to do something like theming.
Yes, this is the same as whitslack's. If you wanted a de-odexed ROM you could now grab the one caulkin posted and flash it.
Click to expand...
Click to collapse
So, essentially caulkin's rom is deodexed, whitslacks is not? Which means, whitslacks rom is exactly like a non-rooted 1.47 ota but with root permissions, while caulkins is exactly like whitslacks, but with the ability to change some files around later.
Like I said, I'm still learning, and it appears whitslacks is sufficient for me since I don't even know what files I could manipulate with caulkins (or your) version nor how to do it even if I wanted to.
Thanks again, learning a little more every day. I've spent about 5 full days on this forum. slowly but surely, right?
Pretty cool
This is a very basic guide to beginning themeing. It is not meant to be all-inclusive, just some simple steps that can be taken to make your own custom theme fairly easily. This guide should allow anyone to be able to grab images they like from any ROM and incorporate them into their own.
I SUGGEST YOU ALWAYS MAKE A BACKUP OF ANY FILE BEFORE YOU THEME IT AND NANDROID FIRST BEFORE FLASHING
Here is a basic overview of changing images in an apk:
1. Get your base file to theme – framework-res.apk, com.htc.resources.apk, phone.apk ect.
2. “Open” apk archive with 7-zip (don’t unzip!) and drag and drop the new images into the appropriate folder.
3. Flash new file.
Now some details:
1. The first step is to obtain the file you are going to theme. The file you are themeing ( i.e. going to flash to your phone) must come from the ROM you are currently running. Always use files from your current ROM as a base, however the images you want to change can come from other ROMs, or you can edit existing ones or make your own from scratch. You can obtain your theme base through an ADB pull of the files from your phone, or simply downloading the ROM zip file and extracting the files you need.
2. Now that you have the file to theme, don’t touch it! OK, more specifically, you won’t unzip or do anything to this file except “open” it with 7-zip (unless this is a market app, but more on that later). You are going to drag and drop the new icons into this file by “opening” it and navigating to the appropriate folder. The images you want to change are stored in the apk under /res/drawable-hdpi. Once you have your new icons from other sources, open your base file and navigate to this folder and drop them in.
3. Now you can flash this new file. I have provided empty zip files that you can place your themed files into and flash in recovery. Place your framework-res.apk and/or com.htc.resources.apk into the /system/framework folder located in the zip file provided. Now highlight the META-INF and system folders and zip them up. You can now place this file on the root of your SD card and flash. System apps can be placed under /system/app in the zip file.
Some more info on common themeable files:
Framework-res.apk – this is the meat and potatoes of a theme. On an AOSP ROM it will contain almost everything you want to theme aside from individual apps themselves. Sense ROMs have another file com.htc.resources.apk, as well as framework-res.apk. Both of these files are located in a ROM under /system/framework.
System apps: These apps come packaged in a ROM under /system/apps. They can be themed in the same manner as a framework apk. Some of these apps include Gmail, browser, camera, ect. Place them in your flashable zip under the folder /system/app.
Market apps: These apps are downloaded from the market and are can be pulled from your phone from /data/app. These files require a bit more to theme. They don’t share the same signature as the system apps and you must resign them using a program such as apkmanger. Place them in your flashable zip under /data/app.
If there are any errors, or if anyone has suggestions please let me know. I may have over looked some details, ect.
Thanks to everyone on XDA who has shared their knowledge and made this a great community!
Thanks that will be helpful
Sent from my PC36100 using XDA App
so using this guide we can pull parts and what not from other elements of themes we like and create our own framework to push back? Also, based on what you have, shouldn't it be easy to put this up on bid for hire (?) website to create a program to automate that?
xlGmanlx said:
so using this guide we can pull parts and what not from other elements of themes we like and create our own framework to push back? Also, based on what you have, shouldn't it be easy to put this up on bid for hire (?) website to create a program to automate that?
Click to expand...
Click to collapse
Yes the idea of this guide was to help people pick and choose icons they like in other ROMs and add it to their own. I'm not sure what bid for hire is?
its a website where you can load your requirements and folks can bid to do your work
linky
nukedukem said:
Yes the idea of this guide was to help people pick and choose icons they like in other ROMs and add it to their own. I'm not sure what bid for hire is?
Click to expand...
Click to collapse
xlGmanlx said:
its a website where you can load your requirements and folks can bid to do your work
linky
Click to expand...
Click to collapse
Interesting. Didn't know anything like this existed.
Sent from my EVO (CM6.1) using XDA App
Thank you, thank you!!!! I've been looking for something like this for a while.
evolishesh said:
Thank you, thank you!!!! I've been looking for something like this for a while.
Click to expand...
Click to collapse
No prob. Let me know if it works for you.
I couldn't get the auto signing to work, but the manual way of doing it worked.
Hmm, I got a boot loop on first try and doing this. Does that mean something went wrong with the signing, or that what I created for the theme was wrong? I used the empty .zip folder and re-zipped it, so I don't think that is the issue.
JasonK75 said:
Hmm, I got a boot loop on first try and doing this. Does that mean something went wrong with the signing, or that what I created for the theme was wrong? I used the empty .zip folder and re-zipped it, so I don't think that is the issue.
Click to expand...
Click to collapse
The signing should be ok. If you are using Amon_ra recovery it wont let you flash an unsigned zip I believe. Are you on sense or AOSP? Are you editing images or just copying from other ROMs?
What you might want to do is just create a simple test file. Change just one image and then flash that. That should let you know that your process is correct.
I using Amon Ra and using AOSP. I was moving some items out of a sense ROM so I guess that is where I might have went wrong. I think I'll take your advice and move just a single image and see how that works for me. Thanks!
I tried again this time I ended up stuck at the EVO white screen. I'm guessing it doesn't like the sense part I'm trying to throw in there. I'll have to try again with a AOSP theme instead.
Sent from my EVO (CM6.1.1) using XDA App
A couple things to look out for when swapping sense/CM icons - some file names are slightly different between sense and AOSP. Rename any sense icons to their AOSP counterparts and vice versa. Also, double check the image size of the icon is the same in both, i.e. 70x70 pixels, ect. and make sure you are not adding images that don't exist normally in the framework. For example there wont be any 4G icons in CM framework.
Also, make sure you aren't unzipping the new framework-res.apk you want to theme and flash, or trying to resign it. Only sign the flashable zip, not the individual files inside. The only thing you want to do with the framework-res.apk you will package and flash is open (not unzip) with 7-zip and navigate to the res/drawable-hdpi folder so you can drag and drop the new icons into it, overwriting the old.
I hope that helps!
How important is it to re-sign? I have modified the Framework and Resources apks with 7zip by switching images out. I have also modified the Rosie.apk. I put everything back where it was supposed to go, backed out of 7-zip and flashed. I have never had an issue with it, nor have I re-signed it. Just wondering.
spence341 said:
How important is it to re-sign? I have modified the Framework and Resources apks with 7zip by switching images out. I have also modified the Rosie.apk. I put everything back where it was supposed to go, backed out of 7-zip and flashed. I have never had an issue with it, nor have I re-signed it. Just wondering.
Click to expand...
Click to collapse
AFAIK if you are on clockwork recovery, I don't think it checks for signatures. I think Amon_ra requires a signed file to flash. I think it's just added protection against flashing any old junk. If you can flash in amon_ra without a signature and you don't have problems then I wouldn't worry about it. It's the signature of the framework-res.apk ( or com.htc.resources.apk) that's important. That's why you don't unzip it.
I think that
1.7.0.2 = yes
1.8 = no
nukedukem said:
AFAIK if you are on clockwork recovery, I don't think it checks for signatures. I think Amon_ra requires a signed file to flash. I think it's just added protection against flashing any old junk. If you can flash in amon_ra without a signature and you don't have problems then I wouldn't worry about it. It's the signature of the framework-res.apk ( or com.htc.resources.apk) that's important. That's why you don't unzip it.
Click to expand...
Click to collapse
nukedukem said:
A couple things to look out for when swapping sense/CM icons - some file names are slightly different between sense and AOSP. Rename any sense icons to their AOSP counterparts and vice versa. Also, double check the image size of the icon is the same in both, i.e. 70x70 pixels, ect. and make sure you are not adding images that don't exist normally in the framework. For example there wont be any 4G icons in CM framework.
Also, make sure you aren't unzipping the new framework-res.apk you want to theme and flash, or trying to resign it. Only sign the flashable zip, not the individual files inside. The only thing you want to do with the framework-res.apk you will package and flash is open (not unzip) with 7-zip and navigate to the res/drawable-hdpi folder so you can drag and drop the new icons into it, overwriting the old.
I hope that helps!
Click to expand...
Click to collapse
Thanks, any advice does help.
I did make sure the the icons I was swapping out were named the same thing in the CM ROM, but I didn't check the size of it at all.
I didn't unzip the famework-res.apk but instead just went into it with 7-Zip and dragged the icons into that. Then I backed out of 7-Zip so that it would save and close everything properly - know that does work because that is how I add the Fold transistions to the ROM - and then I put the famework-res.apk into the folder and zip it up per your instructions above. Then I manually sign it (still haven't been able to get the auto-signing to work) and then flash.
I'll have to try again moving a CM theme to the CM framework-res.apk and see if it is working. What I was attempting to do was take, from the Batman Theme for sense, the drop down notification shade with the Bat Icon and put it into the CM ROM. I don't know if you have time to try it yourself to see if it works, or if you get the same issues that I had.
Either way, thanks for the help! I know I'll get this theming down at some point!
nukedukem said:
No prob. Let me know if it works for you.
Click to expand...
Click to collapse
Hey buddy.
I’m stuck. I had to download and install Eclipse with the sdk plus java. I don’t know where to go from there. Every time I open the rom that I want to theme and get the framework.apk and edit the PNG’s , how do I go about saving them? Do I just used the same name as the old ones or I have to save them with a new name.
Or pm Me.
xlGmanlx said:
I think that
1.7.0.2 = yes
1.8 = no
Click to expand...
Click to collapse
So the new amon_ra doesn't require a signed file to flash? I'll make a note off that. Thanks.
JasonK75 said:
Thanks, any advice does help.
I did make sure the the icons I was swapping out were named the same thing in the CM ROM, but I didn't check the size of it at all.
I didn't unzip the famework-res.apk but instead just went into it with 7-Zip and dragged the icons into that. Then I backed out of 7-Zip so that it would save and close everything properly - know that does work because that is how I add the Fold transistions to the ROM - and then I put the famework-res.apk into the folder and zip it up per your instructions above. Then I manually sign it (still haven't been able to get the auto-signing to work) and then flash.
I'll have to try again moving a CM theme to the CM framework-res.apk and see if it is working. What I was attempting to do was take, from the Batman Theme for sense, the drop down notification shade with the Bat Icon and put it into the CM ROM. I don't know if you have time to try it yourself to see if it works, or if you get the same issues that I had.
Either way, thanks for the help! I know I'll get this theming down at some point!
Click to expand...
Click to collapse
OK I'll try and do what you are trying to do and see if it works...
evolishesh said:
Hey buddy.
I’m stuck. I had to download and install Eclipse with the sdk plus java. I don’t know where to go from there. Every time I open the rom that I want to theme and get the framework.apk and edit the PNG’s , how do I go about saving them? Do I just used the same name as the old ones or I have to save them with a new name.
Or pm Me.
Click to expand...
Click to collapse
So now you have an unzipped framewor-res.apk with a bunch of images. This framework should be the one that you want to take icons from. If not, start over with the ROM you want to copy images from. You will want to copy the images you want to put into another ROM so that you can dump them into the new framework-res.apk. After you figure out what icons you want to bring to your new framework, get a clean version of framework/com.htc from the ROM you are actually running - i.e. if you are running myn ROM on your phone, download the myn ROM and pull out the framework-res.apk or com.resources.apk that you are going to theme.
Now with this fresh clean framework you will "open" it with 7-zip to navigate to the /res/drawable-hdpi folder so you can now drag and drop the images you want to copy over into it. Then the close the 7zip window and your framework-res.apk is all set to flash. You don't need to rename if the file names are the same, you can just drag and drop and the files will be overwritten in the new framework.