Related
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.
VillainTheme System 0.3.5 for the TF101
http://www.villainrom.co.uk/forum/showthread.php/4971-About-VillainTheme-System
pulser_g2 said:
OK, so I think it's time to explain what this is about. It's born from the idea that came about on IRC, for a way to make a theme once for a ROM, rather than have to adjust it for each incremental update for a given ROM or ROMs.
As a user, you don't need to know much - just flash this zip like a regular zip, and you'll get your theme running. But you should be able to apply themes to any device, ROM, and version of the ROM, without it causing adverse effects. That means less time spent by themers making the original theme, and less time spent modifying it constantly for new versions of ROMs.
As a themer? Well, here is the information:
Inside the zip, in the vrtheme folder, you can create a folder called "system" and "data". The former is required, the latter is not required unless you wanted to theme a data app (strongly not recommended, unless you know the app will be there on every phone)
Inside the system or data folder, create a subfolder "app", and in these, make subfolders named EXACTLY after the APK name. For example, to theme the Browser, you need a folder called "Browser.apk". It must be correctly capitalised.
Within there, place the files you require for your theme, in the relevant locations. So most PNGs will be in res/drawable-hdpi/. You can put in xml files too (those which are not in resources.arsc), if you compile them via apktool, and extract them with a zip tool.
In the vrtheme folder, as well as system and data folder, one called "raw" can exist. Within here, you can place files to be copied verbatim to the ROM (for example, modified JAR files). Note that using this may make the theme device dependent (read WILL make it device dependent)
And that's about it.
Features
Will modify APKs in a ROM, without changing signatures, and can be used on any ROM where the filenames of themed files is the same.
Should not need updated between versions of a ROM
Zipaligns all APKs before installation
Stores a backup of all files being modified in /cache/vrtheme-backup/
Requires no coding abilities or editing of files - just drag and drop
Can copy "raw" files, though at risk of not working on other devices (well, let's face it, it won't work on likely a slightly different ROM, so this feature is not recommended or encouraged)
Credits
Doctorcete for the original idea in a discussion on IRC
Stericson for the original idea of metamorph. While totally different, it's a shared goal to separate themes from ROMs
Matt from the Metamorph team, for the zip binary compiled for Android
Seshy, for testing
EULA
Click to expand...
Click to collapse
Nothing evil or complicated - just a few little things. You should not charge for access to this code. That includes a zip containing this, or a derivative of it. So please don't sell themes using it. That's not particularly cool. If you want to use it commercially for some reason, get in touch with us.
If you spot a bug or error, and find a fix, please reply in this thread and let us know, or post the changes you made. If you're going to distribute the changed version, it is expected that you share the change made by contacting us, or posting it here.
Finally, don't be a douche - don't rip this off or call it your own, and leave all headers and comments identifying the origin of the code in place. Don't rename this to match your ROM or "team" name - it's not cool, and it's not yours to go and adjust. I chose to make this a readable "plain" script, but can easily obfuscate and encrypt it if you want to be a douche.
Copyright VillainROM (2011). All rights reserved
Click to expand...
Click to collapse
Now this project was created around the SGS2, and as such it did not work on the TF101 at first, however me and Pulser have spent the day looking for solutions and finally got it working for the TF101.
IMPORTANT: DO NOT USE THE SGS2 TEMPLATE FROM THE VILLAINROM WEBSITE.
Download:
0.3.6 experimental
Clean template without theme included: http://www.mediafire.com/?5bs9srz88i4wdq4
Asus Eee Pad TF101 VRTheme template: http://www.mediafire.com/?5gyr1g0xgd05t70
Note: for now the template is my windows phone 7 theme since it shows you where everything goes really well
If you find any issues or bugs PM me with as much info as you can and if possible a recovery log (found in /cache/recovery/) so I can try and find a solution to your problem.
Changelog
0.3.5
Fixed ASCII art in updater script.
Minor clean up of installtheme.sh
Added preview.png to template.
0.3.3
Modified installtheme.sh as it was giving possible problems.
0.3.2
Fixed a problem with raw folder copying. Put contents of /raw in /system now on the root of the .zip
Fixed some status 0 errors.
Currently known bugs:
You may have issues trying to flash framework files and app files in the same .zip (code 0 error).
Temporary solution: Flash the framework folder and the app folder in seperate .zip files.
hello,
is that you can see screen pls ?
And this theme is compatible with any rom ?
wallah said:
hello,
is that you can see screen pls ?
And this theme is compatible with any rom ?
Click to expand...
Click to collapse
If you had taken 3 seconds to read the post you would know it's not a theme.
This is for themers only.
yes I have read and I have not really understood ...
sorry I disturb
For any themers who want a better example of how it works, I just updated my own theme to use this method:
http://forum.xda-developers.com/showthread.php?t=1120525
Hey seshmaru,
This is definitely a great method! As soon as I get a chance, I will experiment with adapting PCB Blue to use the VillainROM theming method (with leaving all credit intact of course )
If someone wants to uninstall any themes applied this way, what would be the best method though? Just reflash their ROM?...(is what I'm thinking).
Thanks for working on this with the Villain Team, and if there's anything I can do (help/test/etc.), please don't hesitate to PM me.
Thanks again, and cheers for now!
scar45 said:
Hey seshmaru,
This is definitely a great method! As soon as I get a chance, I will experiment with adapting PCB Blue to use the VillainROM theming method (with leaving all credit intact of course )
If someone wants to uninstall any themes applied this way, what would be the best method though? Just reflash their ROM?...(is what I'm thinking).
Thanks for working on this with the Villain Team, and if there's anything I can do (help/test/etc.), please don't hesitate to PM me.
Thanks again, and cheers for now!
Click to expand...
Click to collapse
Well seeing as the current .zip makes a backup of the original files, in the future there will probably be a script made to restore the back up.
Till then the easiest way is to just reflash your ROM without a wipe or to reflash whatever theme you had before.
If you want to help with testing (constantly fixing things since pulser is away so it's my task to keep the SGS2 template and TF101 template as identical as possible) or have any questions you can pop by the VillainROM IRC since I'm generally in there.
Hmm... I can't quite figure out why, but it is not working right for me.. My framework-res.apk file is exactly the same after flashing....
I managed to do some debugging, and i found out that the file file is actually created, but it doesn't copy it over for some reason...
within the VRTheme folder (which i prevented from being deleted so i could check out the contents) the framework-res.apk file is in apply/system/framework/framework-res.apk...
So i tried editing the install script, all the way down at the bottom, and i changed the code from from cd /cache/vrtheme/apply/system/framework/aligned/ to cd /cache/vrtheme/apply/system/framework/ and it worked!
All i can guess is that the file isn't getting aligned for some reason, so that folder/file is never created, but the script is still calling for it...
Can you please let me know if my fix is acceptable, or if there is something off with it that can be fixed and would allow it to be aligned therefore creating the folder and the file?
-trailblazer101
I just want to confirm this. I made some xml edits for the framework, finsky, and gmail were I change the color of the text. Those are in the values folder in the colors.xml file. After you compile the apk you cannot see that folder so I am guessing that you cannot use this to flash that xml correct?
went toflash the theme i get error 0
MetAloid said:
went toflash the theme i get error 0
Click to expand...
Click to collapse
just try the new version now i get error 6
MetAloid said:
just try the new version now i get error 6
Click to expand...
Click to collapse
I got error 6 as well.
Error 6
I'm gettting same error ^ as cescribed by others.
I have been wanting to get into the Honeycomb theme arena and this looks like a good place to start, thanks for your work and I hope I can figure it out. Would it be ok to drop by IRC if I have any questions?
Hi all, just looking for confirmation that the VillainTheme flasher is able to apply .XML files (specifically in framework-res/drawable)?
Thanks in advance!
It should be able to, although it's had some issues at times.
Anyone getting status 6, try this new updated template: http://www.mediafire.com/?5bs9srz88i4wdq4
seshmaru said:
Anyone getting status 6, try this new updated template: http://www.mediafire.com/?5bs9srz88i4wdq4
Click to expand...
Click to collapse
That 0.3.6 template works for me
Regards, folgui.
I'm having a problem with Recovery giving "E:Error in... / Error 0" with my theme for the TF101 below.
Can someone please test it and report their findings? Note that you should do a Nandroid backup first!
Thanks in advance...
** EDIT ** - Found the problem and fixed it...sorry for the post!
So I been playing with this and some help as some things I was able to manage to work and some not. Tried coping and pasting some of the files using root explorer as well some worked some didnt. I read that I needed the deodex rom to use kitchen so... I Flashed that with oden as well. Still the same problems occur. I really like to customize my phone but, it seems I can get some things to work right some not. If somone would be so kind to help me out get this straighten out I would HIGHLY appericate it. Im using the EP1W debloated rom with TW4 Launcher. Im missing a few widgets but, the only I really would like to get on there is the Feeds & Updates (preferly not pink header) which seems to be the only one around I can find. In the kitchen I was able to get the battery icon changed and with some copy paste I was able to change the boot animation. The Icons themselfs on the top like time,date etc... didnt take. Thanks in advance if someone can lend me there expertise.
Honestly, UOT I really only find useful for the battery icons. Yeah it can do other things, but its so much easier to just modify the files yourself. I use apk manager and it works great for me. Here is the thread for it http://forum.xda-developers.com/showthread.php?t=1100696 My suggestion, if you want to modify the appearance of your phone is to do it manually via apk manager.
stranula said:
Honestly, UOT I really only find useful for the battery icons. Yeah it can do other things, but its so much easier to just modify the files yourself. I use apk manager and it works great for me. Here is the thread for it http://forum.xda-developers.com/showthread.php?t=1100696 My suggestion, if you want to modify the appearance of your phone is to do it manually via apk manager.
Click to expand...
Click to collapse
Sounds a bit complicated ill look more into it but im no expert for sure. I got some some stuff working I guess I should be happy with that lol. Ill look into it thanks. Im confused on this deodexed stuff thats probally when i need to figure out first
babyjake said:
Sounds a bit complicated ill look more into it but im no expert for sure. I got some some stuff working I guess I should be happy with that lol. Ill look into it thanks. Im confused on this deodexed stuff thats probally when i need to figure out first
Click to expand...
Click to collapse
Its actually very easy. I'll help you out. Go on uot and go to the kitchen. Select all the tweaks/themes/icons/boot animations you want. When you are done go to the file upload tab. From here, open up your rom using winrar. Go to framework and drag and drop your framework-res.apk and twframework (something along that line, youll see it.) Then look for systemUI.apk. I think its under the app folder right when you open up your rom with winrar. After you got these files out of the rom then upload them to uot by clicking file upload and then click on system files. When this is done uploading click on summary and if everything is highlighted in green then your good to go, submit the work to the kitchen. It will give you a pickup number, copy that number and click on the pickup tab... From there, just wait for your order to come up. Download the file and flash in recovery. Profit? Yes. I hope this helps.
And if your rom is deodexed,then your good to go. Dont over think things, itll give you a headache.
ForeverSupra said:
Its actually very easy. I'll help you out. Go on uot and go to the kitchen. Select all the tweaks/themes/icons/boot animations you want. When you are done go to the file upload tab. From here, open up your rom using winrar. Go to framework and drag and drop your framework-res.apk and twframework (something along that line, youll see it.) Then look for systemUI.apk. I think its under the app folder right when you open up your rom with winrar. After you got these files out of the rom then upload them to uot by clicking file upload and then click on system files. When this is done uploading click on summary and if everything is highlighted in green then your good to go, submit the work to the kitchen. It will give you a pickup number, copy that number and click on the pickup tab... From there, just wait for your order to come up. Download the file and flash in recovery. Profit? Yes. I hope this helps.
And if your rom is deodexed,then your good to go. Dont over think things, itll give you a headache.
Click to expand...
Click to collapse
Did all that thast the problem some of things will work some wont which is why im wondering why certain things take and the others do not
By any chance could someone tell me the best way to make a rom, I have a droid 3 and really want to make a rom but I don't know where to start, thanks in advance
Sent from my DROID3 using XDA App
The best roms start with 3 eggs and little bit of milk to make them fluffy. Whisk briskly!
If you want to jump in, this is a good place to start http://source.android.com/source/index.html
If you just want to dip your toe in the water, then you could start with modding roms, such as adding/removing apks, theming, writing update scripts.
Find a rom and unzip it. Look inside, poke around. Don't be shy-take things apart. Peel back the layers until you find xml and png files. Then, put it all back together and see if you can get it to flash.
Thanks
Sent from my DROID3 using XDA App
thanks so much for the info!
If you download a rom and unzip it, there will be a META-INF folder- look in here- there will be some crypto certs and a com/google/android/ folder which will have the updater-script and update-binary. The script is how the phone knows what to do with the rom. Read through the script and try to decipher what it is actually doing. It will be different for some roms. For example, the cyanogen roms will back up some system apps and replace them after flashing.
You might also come across a boot.img in the root directory of the rom. If you do, there will be some instructions in the updater-script for what to do with it.
Next look in the system/app directory- you'll find a bunch of apk files. These are actually in zip format, so you could unzip them to see what is inside.
A basic test would be to add or remove an apk to the system apps and then get it to flash. Of course you'll need a rooted phone and maybe jarsigner or signapk. Signing a rom will put all those CERT.RSA files back into the META-INF/ folder, which contain crypto hashes of all the files and the names of the files. Some recoveries will allow you to flash an unsigned rom, but you might as well figure out how to sign them. It's in the android link I posted earlier.
Good luck!
Thank you for that also this is very helpful I was kinda confused on where to start with aosp, also that the droid 3 has a locked bootloader
Sent from my DROID3 using XDA App
By any chance would you know how to do some theming? If I understand right it has to do with decompiling the framework-res and systemui apks, and replacing some pngs and xmls with others right?
Sent from my DROID3 using XDA App
I just got started with this so I am by no means an expert. I think you'll want to start by deodexing a rom so that you can make changes to the res, xml, etc. I think most stock apps come as a two part package- an .apk file and an .odex file, both with the same names. Find a stock app and look in the framework and app folders. De-odex-ing takes the odex file, de-compiles it, and then recompiles it into a classes.dex file that is put back into the apk or jar file. This configuration will should allow you to make changes without having to compile the rom from scratch... at least that is my understanding.
Find an apk that doesn't have an odex file and look for the classes.dex file inside. Then take a peak in the res folder in the apk. In the res folder you'll find all sorts of xml and png files.
To get started with decompiling, you'll want baksmali http://code.google.com/p/smali/wiki/DeodexInstructions
Take a look at the issues. JesusFreke wrote some interesting comments in issue 61.
I think there are a few other packages that will do the same thing, and there are certainly a few scripts that will work too.
I ran into some issues with deodexing honeycomb- I outlined the process here http://forum.xda-developers.com/showthread.php?t=1324653.
This is also a good source http://wiki.sdx-developers.com/index.php/How_to_deodex_a_ROM
Good info, thanks.
thank you you have been extremely helpful, im gonna try to get my rom out by sometime this week thank you
I just did some mini-theming. I have an ASUS Transformer- the stock rom has it's own back/menu/home buttons. I wanted a more complete honeycomb look, so I grabbed the stock honeycomb versions from a xoom rom, and added them into my deodexed stock ASUS SystemUI.apk. Oddly enough, if I signed the apk, it wouldn't work, but if I left it unsigned, it works fine.
thats odd, i thought you needed to sign it for it to work