Related
So, i need some help from you.
Everytime I put some statusbaar icons into the framework-res.apk and resign it, it stucks in a boot loop.
In ddms it says me that the package android (i think its a file in the framework-res, or the framework-res) isn't signed correctly.
I attached the statusbaricons and the WORKING framework-res.
Could someone please integrate the files in the res/drawables folder and sign it correctly for me?
Thank you..
You would get a credit in my rom ;-) (Yes, i know, it's not very well known :-D , my roms name is MaxismaR, just search for it here..)
P.S: I'm on Windows 7, maybe that affects the signing process..
maxisma said:
So, i need some help from you.
Everytime I put some statusbaar icons into the framework-res.apk and resign it, it stucks in a boot loop.
In ddms it says me that the package android (i think its a file in the framework-res, or the framework-res) isn't signed correctly.
I attached the statusbaricons and the WORKING framework-res.
Could someone please integrate the files in the res/drawables folder and sign it correctly for me?
Thank you..
You would get a credit in my rom ;-) (Yes, i know, it's not very well known :-D , my roms name is MaxismaR, just search for it here..)
P.S: I'm on Windows 7, maybe that affects the signing process..
Click to expand...
Click to collapse
What are you using to sign? Keytools/Jarsigner?
I'm using the autosign.exe.
Ahh, Try my attachment.
Ok, tried and it gives me this :
06-18 21:52:40.797: ERROR/PackageManager(77): Package android signatures do not match the previously installed version; ignoring!
have you tried deleting the META-INF folder before you sign?
maxisma said:
Ok, tried and it gives me this :
06-18 21:52:40.797: ERROR/PackageManager(77): Package android signatures do not match the previously installed version; ignoring!
Click to expand...
Click to collapse
I've come across that error before, it's just telling you the current installation of framework-res doesn't match the signatures with the one you're trying to reinstall. I believe this framework jar file is located only in /system/framework so you would first have to remove any reference to the file (basically uninstall it). I know you can't uninstall a jar but basically you need to remove references to the file and signature of the file before you can replace it. It's possible you only need to remove /system/framework/framework-res.jar and /data/dalvik-cache/*framework-res*
I can't guarantee that if you remove this file that android will still boot up without errors. Be prepared to have to wipe and reload
why not take a full ROM update and put your images into that and then sign it. also make sure your images aren't too big. if you are using linux you can use pngcrush otherwise i'm no help
But there's no framework-res.jar in there.
But will try wiping after installing the new framework-res ;-)
If u r including icons like battery, check the number of icons in the framework of hero & that of ur rom, if it dosent mach, try removing or incliding some more or ger the source cod & insert those hero stuff inor source code & rebuild rom then get both framework res apk & the jar file....
thats the way i had implemented the percentage battery statusbar icons into 1.5
I know your always supposed to resign the apk's but the only workaround I have found for the exact same problem is to put.zip at the end of framework-res.apk.Right click on it explore to what directory im inserting my images in and paste em while leaving it zipped,when done take .zip back off dont sign it and it works then in the update.
THX to crotalusfreak! That fixed it! You'll get a credit in my next upload ;-)
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!
As the subject line states: I've signed (successfully?) my custom ROM zip file using various programs/methods. Each of them claims a successful signed zip at the end. However, when I try applying my ROM via CWM, I get the standard E:sig verification failed error msg. (Of course, disabling the verification check in CWM allows my ROM to be installed, error-free).
Yes, I've been through all the signing tutorials (that I could find) on this board. A couple were quite useful, but all they did was confirm I was doing the procedure correctly.
Here's a bit of background on my ROM:
It's actually a collection of 4 types of APKs:
some stock, Sense stuff... presumably signed by HTC
some 3rd party (Market) APKs... presumably signed by the appropriate author
some of my own APKs (signed by me, with my own SSL key)
some of my own APKs (not signed at all)
I've also gone in and modified some existing stock HTC APKs.
I tell you this info because I think this is where the problem might be.
Is it possible to sign a ROM file only at the ZIP level (and thereby encompass all the APKs within it)?
If not, do I have to go inside the ROM and sign each APK individually? Do I need to sign them all, or only those that have changed? And which key do I sign it with? (mine? generic test?) Is there ever a scenario where I have to remove/replace an existing signature from an APK with my own signature? Do I need to remove any existing META-INF folders before attempting to sign anything?
These are the questions to which I could find no answers.
Any help would be greatly appreciated.
Thanks,
- Anthony
Tigger31337 said:
As the subject line states: I've signed (successfully?) my custom ROM zip file using various programs/methods. Each of them claims a successful signed zip at the end. However, when I try applying my ROM via CWM, I get the standard E:sig verification failed error msg. (Of course, disabling the verification check in CWM allows my ROM to be installed, error-free).
Yes, I've been through all the signing tutorials (that I could find) on this board. A couple were quite useful, but all they did was confirm I was doing the procedure correctly.
Here's a bit of background on my ROM:
It's actually a collection of 4 types of APKs:
some stock, Sense stuff... presumably signed by HTC
some 3rd party (Market) APKs... presumably signed by the appropriate author
some of my own APKs (signed by me, with my own SSL key)
some of my own APKs (not signed at all)
I've also gone in and modified some existing stock HTC APKs.
I tell you this info because I think this is where the problem might be.
Is it possible to sign a ROM file only at the ZIP level (and thereby encompass all the APKs within it)?
If not, do I have to go inside the ROM and sign each APK individually? Do I need to sign them all, or only those that have changed? And which key do I sign it with? (mine? generic test?) Is there ever a scenario where I have to remove/replace an existing signature from an APK with my own signature? Do I need to remove any existing META-INF folders before attempting to sign anything?
These are the questions to which I could find no answers.
Any help would be greatly appreciated.
Thanks,
- Anthony
Click to expand...
Click to collapse
Here is something that works if you decompile and recompile a apk take the res folder out the part you tweaked and throw it in one that wasn't tweaked or extracted and the Sig will be good.
Sent from my PG86100 using xda premium
reaper24 said:
Here is something that works if you decompile and recompile a apk take the res folder out the part you tweaked and throw it in one that wasn't tweaked or extracted and the Sig will be good.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Okay, so you're saying that signing at the level of the ROM ZIP simply isn't enough. (I wish the guides would say that).
You're saying, I will need to preserve the sigs on the original APKs? I get that. But now that raises more questions:
- when you say "decompile" an APK, I assume this is a simple unzip/extract? That's all I've been doing so far (I use 7-Zip).
- Say I now have an extracted APK (assume it was an HTC stock), I can inject my modified files. Piece of cake. I now have an HTC APK with my own data in there. But what about all the other APKs that make up my entire ROM? Do they ALL have to been signed the same way? (In this example, do they ALL have to be HTC signed?) I'm guessing NO, because there are apps in the data/apps directory from the Market, with their own vendor sigs. I can't see why I would have to re-sign those APKs using the HTC sig.
- So, we're back to my original question: can't you sign a ROM at the ZIP level, or do I have to go back into each individual APK inside that ROM and re-sign them all? Why would the original signature work, but not my own? I have generated my own SSL keys, so in theory I should be able to unzip a APK, tweak it, and re-sign it as my own.
Why does my ROM keep failing the signature test in CWM? I am looking for the necessary and sufficient conditions to allow my ROM (any ZIP file, really) to pass the signature verification check.
No one on this board has been able to answer that, so far.
Thanks so much,
- Anthony
Here's the deal...I downloaded youtube v2.4.4 from here. I opened it in 7zip and extracted the res folder so I could re-theme it. I made my changes then put the res folder back into the original apk. Now this is where the problem occurs. I can't for the life of me figure out how to re-sign the .apk! I have tried every single apk-signer out there to no avail. I have put it in apkManager then decompiled it optimized PNGs recompiled then signed then zipaligned but EVERY time I install it on my phone I get either "Application not installed." or "There is a problem parsing the package." I have uninstalled all versions already on my phone through Titanium Backup prior to installing my themed one. I have manually put it in /System/app and changed permissions and rebooted. NOTHING I do works. I have adb and java installed and in the PATH. I have tried every possible solution I have found on the internet and none work. Any help would be appreciated. Thank You!
P.S. I have an HTC Thunderbolt running the latest build (3/17/12) of ThunderStick Full Blown Sense 3.0 (Thread for this ROM here)
Here is the edited res folder - Maybe someone can look at or use it for troubleshooting.
Thanks again for any input on this problem.
go to market and search and download zipsigner2. open it and navigate to the app and then chose and output and save it as an .apk file and it should install like normal
I found out how to do so and I'll be answering myself once more :
In order to add only the files you want to replace in a zip (or apk) sub-directory and choose what compression method used with 7-zip, we simply do as we do with flashable zips:
- you create a folder named "res" on your desktop;
- you crete a folder named "raw" on your desktop;
- you drag the folder "raw" into the "res" folder
- you choose the sound files [of your choice] [in wav format] and rename them to match which ever one(s) you want to replace in the apk and add them in that "raw" folder;
- you right-click on the "res" folder on your desktop and select: 7-zip/"Add to Archive..."
- you select you new Swiftkey apk (rename it first);
- you make sure that "Store" is selected in the "compression level" field;
[see pic - I've changed spacebar and normal key sound in that example]
- Re-sign the apk
cqfd
Click to expand...
Click to collapse
Hi.
I am totally new to this site and app developing in general. I used the above method (ty AL) to modify the Swiftkey Keyboard app and now just need to re-sign the apk and install it on my device ( ZTE Blade Z Max) I googled how to and found Android Studio, i just am having trouble using it I guess. Im just starting to learn how to modify/develop android apps.
If anyone knows how or can offer up another method for re-signing please help! Much appreciated and tyvm.
Amante
Amante10101 said:
Hi.
I am totally new to this site and app developing in general. I used the above method (ty AL) to modify the Swiftkey Keyboard app and now just need to re-sign the apk and install it on my device ( ZTE Blade Z Max) I googled how to and found Android Studio, i just am having trouble using it I guess. Im just starting to learn how to modify/develop android apps.
If anyone knows how or can offer up another method for re-signing please help! Much appreciated and tyvm.
Amante
Click to expand...
Click to collapse
Try the file explorer MiXplorer found here on xda. It has an apk signing add on feature. It is the my favorite and 1 of the best file managers available. Easily the best for free.
Thebear j koss said:
Try the file explorer MiXplorer found here on xda. It has an apk signing add on feature. It is the my favorite and 1 of the best file managers available. Easily the best for free.
Click to expand...
Click to collapse
Tyvm ill try it out.
Thebear j koss said:
Try the file explorer MiXplorer found here on xda. It has an apk signing add on feature. It is the my favorite and 1 of the best file managers available. Easily the best for free.
Click to expand...
Click to collapse
So I installed MiXplorer (totally awesome app btw) and MiX signer but how exactly do you use it to sign, doesnt seem very straight forward and cant find a how to on google.
Amante
Amante10101 said:
So I installed MiXplorer (totally awesome app btw) and MiX signer but how exactly do you use it to sign, doesnt seem very straight forward and cant find a how to on google.
Amante
Click to expand...
Click to collapse
You need to install the Signer add on. Settings--->add one. After that, long press your apk you want to sign hit settings button, then scroll to sign. Choose with automatic i believe. Refer to the MiX FAQ thread. Link located in OP of MiX thread.
Thebear j koss said:
You need to install the Signer add on. Settings--->add one. After that, long press your apk you want to sign hit settings button, then scroll to sign. Choose with automatic i believe. Refer to the MiX FAQ thread. Link located in OP of MiX thread.
Click to expand...
Click to collapse
Im a retard lol, never occured that i could scroll the elipsis menu. Thanks a ton bro.
Amante10101 said:
Hi.
I am totally new to this site and app developing in general. I used the above method (ty AL) to modify the Swiftkey Keyboard app and now just need to re-sign the apk and install it on my device ( ZTE Blade Z Max) I googled how to and found Android Studio, i just am having trouble using it I guess. Im just starting to learn how to modify/develop android apps.
If anyone knows how or can offer up another method for re-signing please help! Much appreciated and tyvm.
Amante
Click to expand...
Click to collapse
Signing worked! fantastic.
Decided I wanted to change more of the sounds in swiftkey to have a couple more themes with the original one i modified so I went through the 7zip process described in an earlier thread, except this time when i did it it didnt replace the mp3 sound files in the apk with the waves I wanted to substitute. This time it just added the .wav(s) to the apk while leaving the .mp3(s) there along with them. seems wierd. I changed the names of the .wav(s) to the same as the ones i wanted to replace, right clicked folder and hit add to archive. Selected drop down menu and selected apk and made sure store was the option selected and zip was the method selected. No go. Any suggestions?
Amante10101 said:
Signing worked! fantastic.
Decided I wanted to change more of the sounds in swiftkey to have a couple more themes with the original one i modified so I went through the 7zip process described in an earlier thread, except this time when i did it it didnt replace the mp3 sound files in the apk with the waves I wanted to substitute. This time it just added the .wav(s) to the apk while leaving the .mp3(s) there along with them. seems wierd. I changed the names of the .wav(s) to the same as the ones i wanted to replace, right clicked folder and hit add to archive. Selected drop down menu and selected apk and made sure store was the option selected and zip was the method selected. No go. Any suggestions?
Click to expand...
Click to collapse
Nvm I got it, some of the sound files for sound themes in apk are .wav some are .mp3. Just made them mp3 and it worked
someone must have got lazy/didnt need to organize w/e when creating the app. lol.
My first app project complete. yeah!