Related
Hi, just have a question regarding modding apks inside /app in odexed roms.
Have read a few threads regarding deodexing and decompiling apks, and just wish to clarify one thing:
For apks which have a corresponding odex file, is it possible to modify them without deodexing the whole rom? Intend to edit some xml files in the Contacts.apk file but wasn't sure of the exact procedure.
Here's what I tried:
1. Used xultimate to deodex
2. Used apktool to decompile apk
3. Edited xml
4. Used apktool to compile
5. Added META-INF and AndroidManifest.xml from original apk using 7zip
6. Deleted Contacts.apk and Contacts.odex
7. Copied Contacts.apk over
Thanks in advance!
ock said:
Hi, just have a question regarding modding apks inside /app in odexed roms.
(...)
For apks which have a corresponding odex file, is it possible to modify them without deodexing the whole rom? Intend to edit some xml files in the Contacts.apk file but wasn't sure of the exact procedure.
Click to expand...
Click to collapse
+1
I am also interested in the answer ...
I would like to theme some widgets and theme the statusbar on a stock ROM. I am not sure is it possible ? And what is the procedure with the odexed files ?
so of you have notice and have been asking about this. i decided i would open up my vault and let the secret out for all.
this is brought to you by myself and the rest of ACS.
Me and dreamsforgoten figured this one out together.
Disclaimer: do not decompile a custom framework and expect it to recompile as it will not work and you'll end up with a list of errors. You can not hold me our anyone at ACS for bricking your phone or any damage that may have occurred by doing this
this how-to is written as if you have a half a brain and know what your doing. if you dont know what your doing please read the themeing how to's written by dreamsforgotten.
1. decompile framework-res.apk
2. open up the values folder
3. locate strings.xml and open with notepad++
4. ctrl+f and search for Sprint. it should be under zz_roamingguard_1 or something simliar. make sure just to edit the roaming guard_1 only
5. rename to w/e you would like. this changes the pull down branding, the aosp lock screen branding, and the network in settings
6.recompile apk. if your building a theme make your other xml edits while decompiled
If you use this mod in your custom themes or roms please give me credit
if you feel as you have benefited from this in anyway please buy me a beer in my signature to keep me motivated on finding more tricks, hacks and themes
Not sure if this will work on other phones or carries.
Thanks for posting this. Is there a way to tell if a framework-res is modded already? Or, more specifically, if trying this on dk28, where's the best place to get a "pure" framework to start with?
also, do you use a specific level of compression when compiling your edited framework?
Thk u.
Sent from the future.
decalex said:
Thanks for posting this. Is there a way to tell if a framework-res is modded already? Or, more specifically, if trying this on dk28, where's the best place to get a "pure" framework to start with?
also, do you use a specific level of compression when compiling your edited framework?
Thk u.
Sent from the future.
Click to expand...
Click to collapse
When I mean a modded framework-res.apk it's one that comes from a theme. They don't compile nicely with the new images added.
I'm personally using the dk28 release from ACS as my framework to modify.
A good way to test is as soon as you de compile the framework re compile it. If it re compiles with no errors you then you can go ahead and use that framework.
I haven't changed my compression when compiling any of my work
Sent from my SPH-D700 using Tapatalk
I know in apk manager 4.9 it saves the file as unsigned_filename.apk but when you chose yes to carry over the signature, it is carried over into the new file in tact. You can skip the last step of resigning the apk after compiling if you choose yes as a system file when you compile. it throws you off being named unsigned but if you open it the meta inf folder is in there.
Sent from my SPH-D700 using Tapatalk
Ok
Maybe i am in wrong thread but here goes.
I installed acs dk28 fro-yo version when it was first released
I have an app i use called privacy star,it no longer will let me use the app
I called privacy star they say my carrier is iroot the original branding acs used for the ROM since iroot isn't a phone company i cannot pay for the app at all.
tell me why, and any suggestions how i can change my carrier back to sprint branding, i have a build prop if anyone can help me.
about phone says sprint as my carrier and i didnt see anything odd in buildprop
http://pastebin.com/92hCixde
humdrum2009 said:
Maybe i am in wrong thread but here goes.
I installed acs dk28 fro-yo version when it was first released
I have an app i use called privacy star,it no longer will let me use the app
I called privacy star they say my carrier is iroot the original branding acs used for the ROM since iroot isn't a phone company i cannot pay for the app at all.
tell me why, and any suggestions how i can change my carrier back to sprint branding, i have a build prop if anyone can help me.
about phone says sprint as my carrier and i didnt see anything odd in buildprop
http://pastebin.com/92hCixde
Click to expand...
Click to collapse
you may basically have to reverse the instructions in the OP. do you understand the instructions? browse the how to theme guides by dreams, you wouldnt be doing all the editing of pngs and compiling in eclipse, but you will need apk manager. basically decompile your framework-res.apk, go to values/strings.xml and change iroot back to Sprint in Notepad++, recompile. you could either drop it in /system/framework with root explorer or replace in the ROM zip and reflash.
Ill get on it right now thanks
Nice post.
Hmm.. I'm curious If that works for you, since you're decompiling and recompiling a "modified" framework.
Sent from the future.
decalex said:
Hmm.. I'm curious If that works for you, since you're decompiling and recompiling a "modified" framework.
Sent from the future.
Click to expand...
Click to collapse
Unfortunadamente, it won't. You can however, take a stock framework-res.apk and copy over the drawable-hdpi folder. But you will lose the battery % mod as well, so make sure to change the battery images back to stock before you copy it.
Sent from my Xtremely Syndicated and Emotionless Epic 4G
Thread cleaned. If something like this happens again, infractions will be handed out to everyone involved.
If you have a member that is trolling/flamming, just ignore them and report the post. I will take care of it.
By saying something to them you are going to get yourself in trouble and start a large fight in a thread that does not need it.
decalex said:
Hmm.. I'm curious If that works for you, since you're decompiling and recompiling a "modified" framework.
Sent from the future.
Click to expand...
Click to collapse
you can reverse the order but there will be extra steps involved. when your ready ro re compile you would have to add in all the stock .9.pngs when re compiling.
Sent from my SPH-D700 using Tapatalk
Thx for your help guys I'll edit this post with results.
Cool-- using both of your recommendations (starting with orig ACS DK28 rom's framework-res.apk, I was able to edit the xml(s), recompile, (delete resources.arsc in the created keep folder), then signed, then dropped in drawable pngs. When you want to do the png edits, do you overwrite All of the folders in your signed framework's res folder? (wouldn't that overwrite the xml edit made)? or just the drawable folders
decalex said:
Cool-- using both of your recommendations (starting with orig ACS DK28 rom's framework-res.apk, I was able to edit the xml(s), recompile, (delete resources.arsc in the created keep folder), then signed, then dropped in drawable pngs. When you want to do the png edits, do you overwrite All of the folders in your signed framework's res folder? (wouldn't that overwrite the xml edit made)? or just the drawable folders
Click to expand...
Click to collapse
you will only loose your xml edits if you replace the xmls
Sent from my SPH-D700 using XDA App
hehe.. come on man. gimme a little more credit than that
in compiled state, the strings.xml (for example) is contained in the resources.arsc file (?). Because, decompiled, obviously, the folder structure is different.
so, I could basically just replace the whole res folder, since the resources.arsc is *not* in that folder? I'll play around with it, but I think I'm getting the gist.
decalex said:
hehe.. come on man. gimme a little more credit than that
in compiled state, the strings.xml (for example) is contained in the resources.arsc file (?). Because, decompiled, obviously, the folder structure is different.
so, I could basically just replace the whole res folder, since the resources.arsc is *not* in that folder? I'll play around with it, but I think I'm getting the gist.
Click to expand...
Click to collapse
When editing xmls you delete the xmls you edited in the keep folder. The hidden xmls like strings.xml is not seen when being built. I delete the resources.arcs when ever I edit a xml even if it is a visable xml. You cannot replace the hole res folder cause of the xmls inside. Some xmls makes changes in the public.xml when compiled. The public.xml is also hidden.
Just decompile the custom framework you wanna edit. Make your changes. Replace all the modified .9 images with the stock ones. Recompile the framework. In the keep folder delete resources.arcs and any xml you can see in the build that you edited. Delete the .9s from the keep folder since you replaced them. Once the file is compiled sign it. Open up the old custom framework with 7zip and your newly created framework with 7zip. Drag and drop the .9s.from the custom framework into your framework
Sent from my SPH-D700 using XDA App
I made a thread in the Android General section, but it must not be getting attention from anyone capable of deodexing an apk, or just nobody wants to do it.
I probably should have created the thread here, so I'm linking to it here.
http://forum.xda-developers.com/showthread.php?t=1504082
Thanks all
bizzump
+10char
There's a few things we need to know first. Why only one apk? Why not deodex your whole ROM? Or if you have a copy of the whole ROM could your send it to me…..I can't deodex just the SystemUI when it has dependencies on the other functions within the ROM i.e. Framework.jar.
Or if you could explain maybe what your hoping to achieve I could probably sort somethingout for you a much simpler way.
What phone do you have and what apks are you using now? If you want to theme or want some sort of function from an apk that’s not yours but is odex version there may be a way of breaking it down to its classes (if I knew what ROM it was from and you had the entire framework folder from the ROM along with the odex file) and then I can decompile the apk you use (I think that’s what your trying to achieve correct?) from your ROM, then bring the classes and/or pngs across, rebuild, re-optimise (not odex btw) and send it back to you maintaining the signature for your apks in your ROM.
The phone and rom it is running are in my sig. I only want the SystemUI deodexed so that I can make the status bar transparent and still enjoy the slightly improved performance of an odex'ed rom, because this is a low-end phone so anything to increase performance helps. I have also tried using the AutoDeo Tool, but I don't know how to figure out what the correct custom bootclass path line input should be.
I asked for some help in that thread this morning and feel that I'm getting closer to having a deodexed SystemUI. I hate having posts in so many places about the same problem, but it seems like not a whole lot of people know how to do it, and even fewer want to explain such a complex process.
Hopefully I'll be able to deodex my entire rom.zip and just replace the systemui that's on my phone with the deodexed one and delete the .odex file and everything will be ok.
Sent from my SGH-T499 using XDA App
So, I'm a themer at heart, and I love MIUI. Sometimes making MIUI themes gets me confused, I have a nice compile script set up for .9.pngs but then the folders and zips and etc etc, sometimes I get a bit overwhelmed and I completely lose myself in what I was doing. So I decided to make a sort of kitchen, resembling dsixda's ROM kitchen.. currently it's still kinda far off, but that is the ultimate goal.
This is not a graphical tool. This is not an image manipulation tool.
Basically, you take the apks you want to theme and put them in their own folder. Using framework-res.apk and framework-miui-res.apk isn't 100% necessary, but if they're not included, there's a chance the apks will not decompile properly. It will install the two frameworks if they exist, and then decompile all the apks in the folder. It goes into the AndroidManifest.xml file to get the package name (ie com.android.mms) and changes the name of the folder to it. It takes colors.xml and turns it into a theme_values.xml. It then deletes all the extra files that are not needed for a theme, and creates a generic description.xml file. It tells you to edit your pngs, description, and theme_values and run the compiler.
The compiler runs in the same directory, and compiles all the .9.pngs in each separate folder, puts the zips of them with no zip extension into a new "theme" folder, then puts it all together into an mtz in that theme folder.
If you understand MIUI theming, I hope this makes sense. I have a little video showing it off:
http://youtube.com/watch?v=Xg6UHzNjrq8
I plan on prettying it up a little bit more and I want to make a menu to use for future versions.
-----------------------------------------------------------------------------------------------------------
How to use it:
Extract v4tk folder somewhere, and add it to your PATH
Create a new folder, copy and paste the apks you want to theme into it.
- framework-res.apk and framework-miui-res.apk from the same build as the apks you're trying to edit is essential unless you already have them installed with apktool
From terminal in this folder, run "mktemplate" - this makes all the magic happen, and it actually creates a description.xml based on your input.
Edit the pngs, delete the ones you don't edit, for .9.pngs make sure to leave the 1px border alone unless you know what you're doing
Edit the theme_values files, remove the lines you didn't make changes to. Make sure no @color:android/red or whatever are in them. Hex argb only.
Go back to your terminal, run "mktheme" - this compiles all the .9.pngs, packages everything up, and creates an mtz based off your input for a filename. The mktheme script also supports lockscreen, wallpaper, icons, and preview folders... The template does not create these, but if you make them, the mktheme script will package them into the resulting mtz.
For linux or possibly cygwin (should run fine in terminal on OSX - untested though) only currently. I'm afraid it's been over a decade since I've messed with batch scripting, and before I go through the hassle of putting together a windows version, I want to have a complete project.
Also, just wanted to say one of the main reasons I'm releasing this tool is because MIUI v4 is changing a lot week to week; sometimes there's new images, sometimes there are new colors in the theme_values. If I made a template, it'd be obsolete in two weeks time
Also, this will work with any* apk for your theming pleasure, not just MIUI apps.
*maybe there's an app it can't decompile. shouldn't be, but be warned
Finally.. Download: http://lz.gd/v4tk
You Sir are a stud! and not to bad a Miui either! lol
This looks very impressive!
Nice cant wait for it!
It looks great, I love it.
Wow, seems impressive!
A Gui intefarce to exploit pngs with preview would be awesome !
Think this is a huge work
Pretty Awesome. Cant wait
Looks really cool, nice job
This is what the MIUI community needed. NICE job.
I've uploaded it with some minor cosmetic changes. It's completely functional, but not quite where I want it to be yet.. OP has been updated with some basic instructions on how to use it, post here or come find me in #miuithemes on irc.freenode.net for any issues
You sir are awesome. Got the beta downloaded. Thanks so much for your hard work and efforts.
Anybody using this? Is it working well for you?
Report any issues please.
I have not used it yet, but I plan to directly after my rom is updated from 2.5.4
Sent from my DROIDX using XDA
About
Eviltheme (Enhanced VillainROM Theme Engine) is an Android system modification platform meant for use with custom Android recoveries.
It allows modification of application resources without the need to replace the whole app or install a new operating system.
Eviltheme is based on the VRTheme Engine from 2011, though versions 3.x.x and up heavily differ from the original VillainROM code.
Disclaimer
Eviltheme is provided to you without warranty. You are free to try it on your device, but you are doing so at your own risk. I will not be responsible for bricked devices, wiped devices, etc.
Features
Automatic systemless mode with version 3.x.x+ (Magisk required, version 13.1+ recommended)
System mode fallback in case Magisk is not present
Supports both Dalvik and ART platforms
Smart bytecode refresh (delete classes.dex/classes.art only if it is replaced by the theme)
Easy uninstallation via automatically generated flashable ZIP or through Magisk Manager (if installed systemlessly)
Delete files (even inside APKs)
Support for pre/post-(un)installation scripts
Support for dual /system partitions
Downloads
Latest beta: 3.0.0-beta4
Last 2.x release (no systemless support): 2.0.6
Changelogs
GitHub
Documentation
Second post
Help
Third post
Credits
The VillainROM team
@djb77
@Spannaa
@topjohnwu
Source code (GPLv3)
Eviltheme main repo
Eviltheme restore ZIP repo
Documentation
Things to remember
Compile your res/smali/etc files first before you put them in your theme! You can use APKtool for that, then just extract the files from the resulting APK.
Theming user apps is not supported, because modifying the contents breaks the signature.
Remember to properly edit .9.png files, or else you might get a bootloop!
You do not need to put theme files in a subfolder inside the main APK folder, e.g. /system/priv-app/SystemUI/SystemUI.apk. EVilTheme automatically does that for you.
Do I need to download the official Magisk module template?Nope! EVilTheme includes post-fs-data.sh, service.sh, and system.prop. Look for them in META-INF/tk/aureljared/magisk-common and edit them to your liking. The module.prop is automatically generated from information you put in eviltheme.prop.
In the event that the official module template is updated, I will update EVilTheme to ensure compatibility as soon as I can.
How do I theme an app (or apps) using EVilTheme?Inside the ZIP, there are three folders that you can modify as needed; namely, data, system, and vrtheme.
Your patches/theme files go in vrtheme, while APK files that you want to install onto the device go in data and system.
For example, you want to theme Settings.apk, which is located in /system/priv-app.
Let's say your theme replaces res/drawable-hdpi/battery_icon_50.png in the APK, and also replaces classes.dex because you changed some smali files.
These are the steps you need to follow to make a flashable theme ZIP:
Ensure you've downloaded the appropriate template ZIP. Make a folder somewhere you can remember and extract the ZIP there.
The folder should now contain the folders META-INF, data, system, vrtheme, and a file called eviltheme.prop.
Open eviltheme.prop in a text editor (please use Notepad++ if you are on Windows!) and add your theme information there.
In the vrtheme folder, go to system and make a new folder called priv-app. Inside it, make another folder called Settings.apk. Make sure you capitalized correctly!
Now make folders as necessary, according to the location of the files you want to theme. For example, battery_icon_50.png is located in res/drawable-hdpi, so make a folder named res inside Settings.apk. Inside it, create a folder named drawable-hdpi, then paste your new battery_icon_50.png inside.
Repeat step 5 until you've placed your theme files in their appropriate locations.
When you're done, go back to the root folder of the theme (the one that contains new, vrtheme, etc.) and put all 5 objects in a ZIP file. You should use Deflate compression method only. Any compression level will work.[/u]
If the recovery that the theme is intended to be used with requires signing, sign the ZIP now.
Test your theme! :victory:
How do I uninstall a theme?If the theme was installed systemlessly, remove it in Magisk Manager.
Otherwise, flash the relevant zip in /data/eviltheme-backup.
How do I delete files inside APKs to be themed?To delete files, add the filenames to a text file named "delete.list" inside the APK theme folder.
This is an example of a delete.list:
Code:
res/drawable-hdpi/ic-launcher.png
res/drawable-xxhdpi/battery_full.9.png
How do I delete files that aren't inside APKs?You will also need a "delete.list". Remember to use full paths:
Code:
/system/app/Bloatware/Bloatware.apk
/system/etc/hosts
Put that in the "vrtheme" folder.
How can I exclude deleted files from being backed up?Eviltheme versions 3 and up will automatically back up files that your theme deletes (in non-systemless mode).
To exclude a file, add "no-backup" to the end of the corresponding line in vrtheme/delete.list.
Code:
/system/app/Bloatware/Bloatware.apk [B]no-backup[/B]
How do I force installation on /system?Eviltheme versions 3 and up will automatically install in systemless mode with Magisk 13.1+, but if you want to force your theme to install to /system, create a file named .eviltheme-force-system (notice the preceding dot) in /sdcard before installing.
I need to execute some commands during the theme (un)installation.Inside META-INF/tk/aureljared/eviltheme, there are files named "pre-install.sh-example", "post-install.sh-example", "pre-uninstall.sh-example", and "post-uninstall.sh-example". Remove the "-example" part from the file name of your desired script, and edit that file in the text editor (please please please use Notepad++ if you're on Windows).
Use the comments in that file as a guide.
Help section
The theme wasn't successful, and I believe that the problem lies in the engine itself.Post here describing the problem. Be as descriptive as possible. I will ignore all bug reports without an attached logcat dump and/or recovery.log. I'll try to look into the problem when time permits.
I am just a student, not a full-time developer. I may not be able to provide a fix for some bugs, so feel free to help me and everyone else out. If you know how to work with Git, an upstream patch to the project would be highly appreciated :good:
The theme was / wasn't successful, but I am stuck in a bootloop.Try wiping your Dalvik cache. If the problem is still there, uninstall the theme and post a bug report in this thread. Include the relevant /cache/recovery.log and the theme you installed.
The theme was successful, but the app I was theming does not reflect my changes.This is a tough one to solve. Try recompiling the APK itself with your theme files. If it works, it's either the problem lies in how you put the theme files in the ZIP, or maybe it's the script that's buggy. Try to make a ZIP again, following the instructions to the letter. If it still doesn't work, you can file a bug report here and attach your logcat dump, recovery.log, and (if you want) the themed APK.
The theme was successful, and now I'm ready to release my theme to the public.All I ask for is some credit and a link back to this thread. :fingers-crossed:
The theme wasn't successful, and I found a problem in your engine script(s).If you're familiar with Git, you can make a pull request to the EVilTheme repository.
If you don't know how to use Git, you can just edit the script(s) you need and send me a PM containing the fixed script(s). I'll add you to the credits list in the first post if your bugfix is effective!
Great work :good:
I particularly like the smart selective dalvik-cache wiping
Maybe it could be even smarter if the script only wipes an apk's dalvik-cache if the apk has had it's classes.dex replaced by the theme...
I'm working on something like this myself but mine is based on the unreleased GS2XFormROM by @hawkerpaul
I'll throw you a link when it's ready
Spannaa said:
Great work :good:
I particularly like the smart selective dalvik-cache wiping
Maybe it could be even smarter if the script only wipes an apk's dalvik-cache if the apk has had it's classes.dex replaced by the theme...
I'm working on something like this myself but mine is based on the unreleased GS2XFormROM by @hawkerpaul
I'll throw you a link when it's ready
Click to expand...
Click to collapse
Let me know if you need any help on the scripting side of things butty.
Sent from my GT-I9505G using XDA Free mobile app
hawkerpaul said:
Let me know if you need any help on the scripting side of things butty.
Click to expand...
Click to collapse
I will - cheers mate
Got it working but I'm sure you'd do a better job - .sh scripting isn't my thing at all.
Apologies to the OP for the OT...
Sent from my GT-I9300...
Spannaa said:
Great work :good:
I particularly like the smart selective dalvik-cache wiping
Maybe it could be even smarter if the script only wipes an apk's dalvik-cache if the apk has had it's classes.dex replaced by the theme...
I'm working on something like this myself but mine is based on the unreleased GS2XFormROM by @hawkerpaul
I'll throw you a link when it's ready
Click to expand...
Click to collapse
Hmm, yes I think I'll implement this in v1.1. Thanks for the suggestion!
Sent from my GT-I8730 using Tapatalk
Version 1.1 released!
v1.1: Link
What's new?
- Even smarter Dalvik wiping: delete dex files only for those apps whose classes.dex were changed (thanks @Spannaa)
- Corrected a typo in the restore script (please delete 'restore-vr' inside your /system/xbin, if any!)
- Removed unused methods in installtheme.sh
Click to expand...
Click to collapse
aureljared said:
Version 1.1 released!
v1.1: Link
Click to expand...
Click to collapse
How about making this TWRP compatible too - then it'd be even more useful
Reference 1
Reference 2
Spannaa said:
How about making this TWRP compatible too - then it'd be even more useful
Reference 1
Reference 2
Click to expand...
Click to collapse
Version 1.2 released!
v1.2: Link
What's new?
- Refinements to Smart Dalvik Wipe
- Switch to Linus Yang's BusyBox 1.21.1, which will hopefully make theming TouchWiz < 4.2 possible
- TWRP compatibility: switch to a static zipalign binary, grep method for OUTFD to look for updater binary
- Cleaner zip hierarchy: new apps to be installed to /system and /data are now in their respective folders in a folder named 'new'
Click to expand...
Click to collapse
Sent from my GT-I8730 using Tapatalk
aureljared said:
Version 1.2 released!
v1.2: Link
Sent from my GT-I8730 using Tapatalk
Click to expand...
Click to collapse
Very good job on this...one thing, in kitkat 4.4.2 touchwiz roms half of the apps that need to be themed are in /system/priv-app. This folder location does not seem to be in your installtheme.sh script. I can manually change everything myself but if you would like other users to take advantage of your work, you may want to consider updating for these users.
deuce_biggins said:
Very good job on this...one thing, in kitkat 4.4.2 touchwiz roms half of the apps that need to be themed are in /system/priv-app. This folder location does not seem to be in your installtheme.sh script. I can manually change everything myself but if you would like other users to take advantage of your work, you may want to consider updating for these users.
Click to expand...
Click to collapse
Oh right... How could I forget Am working on this now.
Thanks for the heads-up!
Version 1.3 released!
v1.3: Link
What's new?
- Support for KitKat's system apps in priv-app
Click to expand...
Click to collapse
Silly me, forgetting this while using a KitKat ROM
aureljared said:
Version 1.3 released!
v1.3: Link
Silly me, forgetting this while using a KitKat ROM
Click to expand...
Click to collapse
Nice work aureljared, the quick response and update is much appreciated :good:
Thank you @aureljared, deuce_biggins pointed me here, and I must say nice work to you.. Thank you
I tried to vrt a data/app, and it may have broke the signature.. It did theme the app, but it was no longer visible/available in my app drawer.. I could see the themed icon in data/app tho.. I don't think the original VRT could theme in data/app either... I did use your new version 1.3 with twrp on my Galaxy Tab 3, so that is good news.. It also made two folders on my internal sd, one was for data/app and one for system/app.. It did make a copy of the apk it themed in data/app, and placed it in the folder on my internal sd . I will test this on my Note 3 with twrp later..Thank you
aureljared said:
Version 1.3 released!
v1.3: Link
Silly me, forgetting this while using a KitKat ROM
Click to expand...
Click to collapse
cerj said:
I tried to vrt a data/app, and it may have broke the signature.. It did theme the app, but it was no longer visible/available in my app drawer.. I could see the themed icon in data/app tho.. I don't think the original VRT could theme in data/app either... I did use your new version 1.3 with twrp on my Galaxy Tab 3, so that is good news.. It also made two folders on my internal sd, one was for data/app and one for system/app.. It did make a copy of the apk it themed in data/app, and placed it in the folder on my internal sd . I will test this on my Note 3 with twrp later..Thank you
Click to expand...
Click to collapse
@aureljared, just curous...to follow up on with what cerj said, have you ever successfully themed an app inside of /data/app with your VRT? Seems to kill the app every time, your thoughts?
deuce_biggins said:
@aureljared, just curous...to follow up on with what cerj said, have you ever successfully themed an app inside of /data/app with your VRT? Seems to kill the app every time, your thoughts?
Click to expand...
Click to collapse
No, I only tried it with the old VRTheme, and it didn't work either (no icon in drawer). I don't think it'll work on EVilTheme either as I haven't changed the process of /data/app.
aureljared said:
No, I only tried it with the old VRTheme, and it didn't work either (no icon in drawer). I don't think it'll work on EVilTheme either as I haven't changed the process of /data/app.
Click to expand...
Click to collapse
Do you even think it's possible?
deuce_biggins said:
Do you even think it's possible?
Click to expand...
Click to collapse
It could be possible, if we can find a way to go around the sig verification. Or perhaps it just needs a Dalvik wipe, I don't really know [emoji26]