[IDE][3.6.30.14100] Virtuous Ten Studio - Advanced Reverse Engineering Solution
- Thread starter Diamondback
- Start date
S
sawdoctor
Guest
Any log? Did you install framework-res.apk and update apktool to the latest version?
Sent from my SM-N920C using Tapatalk
S
sawdoctor
Guest
Yes VTS needs an update but it's still working great. It is an amazing piece of work! I wish it could be further developed and updated. Nothing else compares to this set of tools. I've been using it for years and I'm very fluent with it. Things that are very important with the current apktool, devices and Android versions of today are as follows:
1. You MUST set the "disassemble dex file" option to KitKat when decompiling apk's and jar files. (Template for API 20 doesn't work right. Also with the new apktool and smali/baksmali, API's will be handled within the apktool & smali java apps so VTS API setting just needs to stay set to KitKat)
2. ALWAYS ALWAYS ALWAYS delete current imported frameworks whenever you update apktool!!! Do not overlook this and if you don't do this then you WILL have bad decompiles/builds for new apk's/jars, period. So the rule of thumb is... if you replace apktool then you MUST delete then re-import all of your frameworks if you plan to do any work using the new apktool version.
3. You will need to continually monitor and delete the temp files that VTS creates in C:\Users"YOUR NAME"\AppData\Local\Temp
these temp files will continue to use up space on your hard drive and they do not get removed by VTS upon each successful build. You will easily use up 5, 10 or 20 Gb of space if you use VTS regularly like i do. So delete these files often! There is absolutely no harm in deleting them. Your project will continue to build just fine as they will be recreated as needed automatically.
4. If your device uses multiple frameworks then you should use the "multiple frameworks" option when importing your frameworks instead of adding them independently. Trust me on this one.
5. To make life easier on yourself, always name your imported frameworks to coincide with the software version in which they are from. Use the last three digits of the software version in the name of your imported frameworks. EX. "N5-PC3-multi-frameworks"
This will keep all of your frameworks in a nice orderly fashion and will make switching between frameworks a simple and pleasant experience allowing you to be more productive from not having to fumble around looking for the correct frameworks.
6.ALWAYS make it a habit to refresh the project before you build!!! Why? Because often you will make edits to smali or resources outside of VTS such as Photoshop or Notepad++ and these changes can sometimes slip through unnoticed by VTS and the build will not include these recent changes. Normally VTS will catch changes outside of it's working environment and prompt you to update/refresh the project... but not always. Save yourself time and confusion by rememberring to refresh before each build as a habit.
7. if you need help or have questions about current issues with VTS and modern android/apktool, ask here in this thread and I will offer what i know at this time.
1. You MUST set the "disassemble dex file" option to KitKat when decompiling apk's and jar files. (Template for API 20 doesn't work right. Also with the new apktool and smali/baksmali, API's will be handled within the apktool & smali java apps so VTS API setting just needs to stay set to KitKat)
2. ALWAYS ALWAYS ALWAYS delete current imported frameworks whenever you update apktool!!! Do not overlook this and if you don't do this then you WILL have bad decompiles/builds for new apk's/jars, period. So the rule of thumb is... if you replace apktool then you MUST delete then re-import all of your frameworks if you plan to do any work using the new apktool version.
3. You will need to continually monitor and delete the temp files that VTS creates in C:\Users"YOUR NAME"\AppData\Local\Temp
these temp files will continue to use up space on your hard drive and they do not get removed by VTS upon each successful build. You will easily use up 5, 10 or 20 Gb of space if you use VTS regularly like i do. So delete these files often! There is absolutely no harm in deleting them. Your project will continue to build just fine as they will be recreated as needed automatically.
4. If your device uses multiple frameworks then you should use the "multiple frameworks" option when importing your frameworks instead of adding them independently. Trust me on this one.
5. To make life easier on yourself, always name your imported frameworks to coincide with the software version in which they are from. Use the last three digits of the software version in the name of your imported frameworks. EX. "N5-PC3-multi-frameworks"
This will keep all of your frameworks in a nice orderly fashion and will make switching between frameworks a simple and pleasant experience allowing you to be more productive from not having to fumble around looking for the correct frameworks.
6.ALWAYS make it a habit to refresh the project before you build!!! Why? Because often you will make edits to smali or resources outside of VTS such as Photoshop or Notepad++ and these changes can sometimes slip through unnoticed by VTS and the build will not include these recent changes. Normally VTS will catch changes outside of it's working environment and prompt you to update/refresh the project... but not always. Save yourself time and confusion by rememberring to refresh before each build as a habit.
7. if you need help or have questions about current issues with VTS and modern android/apktool, ask here in this thread and I will offer what i know at this time.
Last edited:
I need help decompiling an apk with VTS, but I am a complete noob. I don't understand why you need a framework that is specific to your device since vts is running on the computer. I used the latest apktool to decompile an apk to test and it installed the 1.apk framework file to c:\users\<localuser>\apktool\framework\1.apk. how do I decompile in vts with this framework file? I went to settings but it would not let me type anything into the framework tag field. I tried following the documentation on the VTS site but it did not help. Any help for this noob would be very much appreciated. Also, where do I find "disassemble dex file" option in VTS. I can't find it.
By the way, the java file code was messed up in some places when I used the apktool. I am hoping this won't be the case with VTS.
Thanks for your help in advance.
S
sawdoctor
Guest
Ok vts is using apktool to decompile apks. Apktool reverse engineers to decompile the apk. Without the framework installed apktool won't be able to find some of the resources it needs to decompile the apk. Some apks won't need a framework some will need 2 especially Sammy apks they normally need tw framework-res.apk as well as the normal framework-res.apkI need help decompiling an apk with VTS, but I am a complete noob. I don't understand why you need a framework that is specific to your device since vts is running on the computer. I used the latest apktool to decompile an apk to test and it installed the 1.apk framework file to c:\users\<localuser>\apktool\framework\1.apk. how do I decompile in vts with this framework file? I went to settings but it would not let me type anything into the framework tag field. I tried following the documentation on the VTS site but it did not help. Any help for this noob would be very much appreciated. Also, where do I find "disassemble dex file" option in VTS. I can't find it.
By the way, the java file code was messed up in some places when I used the apktool. I am hoping this won't be the case with VTS.
Thanks for your help in advance.
Sent from my SM-N920C using XDA-Developers mobile app
I decompiled an apk using the apktool at the command line. when I opened up the .java files, I saw a lot of errors in the code and there would be single letters for class names and such. why is that? would the same thing happen even if I use VTS to decompile? So, how do I set the framework file for the project? Under "Decompile Resources", when I try typing in the tag, nothing happens. Nothing is typed into the text field. ???
Last edited:
I decompiled an apk using the apktool at the command line. when I opened up the .java files, I saw a lot of errors in the code and there would be single letters for class names and such. why is that? would the same thing happen even if I use VTS to decompile? So, how do I set the framework file for the project? Under "Decompile Resources", when I try typing in the tag, nothing happens. Nothing is typed into the text field. ???
ok ok im sorry if I seemed like a jerk, but why is VTS better than the rest? where do I get these frameworks? from the phone? how do I setup VTS to work? I followed the official guide but can't figure it out. thanks.
Last edited:
Trust me, VTS is hands down the best set of tools. however there is a learning curve especially for people with limited knowledge on this stuff. Your frameworks come from the stock software for your device. The best way to acquire these source files, including framework files, is to download a stock deodexed rom for your specific device model. Also keep in mind that there are different software revisions so you will need to make sure you download the version of software that you plan to be working with and use the framework files from that rom/software.
As for how to setup vts properly, it's a lot to go over in a single post. I had to learn the hard way and it's the best way to learn. i didn't have anybody to hold my hand and answer technical questions when i first started using it. But I knew right away that this software was absolutely my first choice and was worth devoting countless hours learning the in's & out's of it all. You will just have to figure things out take the advice i posted above once you understand how to apply those tips in VTS.
If you have the passion for this sort of stuff then you will be as determined as i was and learn on your own which is the best way. Sorry, i can't offer any other specific steps for setup but you first need to follow the setup instructions on the VTS homepage if it's still available. This involves installing java, java jdk and then going into VTS settings and click on auto detect for java detection. Do that first. Next you will need to learn how to import your frameworks and use the "multi-frameworks" import option if your software uses more than one framework-res.apk such as htc and samsung devices. VTS will automatically detect them if you just point it to the framework folder of the extracted rom on your pc. This stuff is fairly simple actually. VTS can seem very confusing at first but you just have to keep digging and learning what does what. It's the only way you will truly learn how to use this set of tools. nob amount of tips and advice can prepare you to be proficient with this stuff. Good luck.
Hey Dean, do you know if VTS will decompile , system ui , on Note 5 MM PC3 build on sprint, I'm trying to add 3minit and have been unsuccessful in decompile. I have been using the latest ApkTool 2.1
What do you mean by been unsuccessful in decompile? What error, warning, problem? Be a little more specific... Also it would be helpful if you upload the apk and framework you are using.
No. The official Apktool v 2.1 will not work on samsung marshmallow apk's. the resources will not decompile and will throw arsc decode errors. I have a private build of Apktool that mostly works on Samsung MM files. However not all apk's will decompile without errors. Ont the Sprint N5 InCallUI.apk will not decompile but systemui seems to do fine. I have been working on the N5 software for several days and this is what i know right now. Give this apktool a try. It's specifically for samsunng MM so delete all your current frameworks and re-import them once you replace apktool and you should be in business.
This is on my afh account... https://www.androidfilehost.com/?fid=24459283995309527
Edit: Another thing. You need to only use one apktool in vts when using this test build of apktool. Normally you can have several different versions in the External/apktool folder but for some reason if you use multiple versions at once then select the test build when decompiling it still throws errors. So delete all other apktool jars in the Apktool folder and place only the version i posted above. then when you go to decompile you will need to click on the dropdown menu and manuallyselect the apktool v2.0.1 as it will still say the previous version untill you do this. Then you can continue to decompile with success.
Last edited:
Have u try this i posted somewhere on many thread by using apktool v200 , just install framework-res.apk & twframework-res.apk then dec/rec framework-res.apk with apktool v200 then install it with v2.0.3 or v2.1 then u can dec/rec incallui as i did it here many times , its working fine , i don't know if ur attached apktool its as this one but i will leave it here too thats working with my end used
http://xdaforums.com/showthread.php?p=66156789
For dec/rec secsettings see my post on S6 unified thread ,
Good luck ,
Thanks for that info. Very creative technique. i like it! I have not trusted apktool due to these problems. hopefully it works with no problems with the decompiles with the method you mentioned. Now to get a proper convertor for the latest .9.qmg images. current convertor doesn't properly convert the .9 images, only regular images are produced. Thanks again.
Hi again dean so I need the Vts download I went to vts.com and all links are dead
If the links are dead on the official VTS site then somebody will have to upload it. i'm not sure if this is something that would not be approved by diamondback and the dev team of VTS. Try searching for it with google. Maybe somebody has already uploaded it elsewhere.
Couldn't find it but I did find v4.0 coming soon.
Sent from my SM-N920P using XDA-Developers mobile app
Sent from my SM-N920P using XDA-Developers mobile app
Scroll back a few pages in this thread. A few people have posted Dropbox links for it relatively recently.
Sent from my unknown using XDA-Developers mobile app
Top Liked Posts
-
There are no posts matching your filters.
-
527
Screenshots
XDA Portal posts
Main Features
User feedback
Diamondback and everyone involved in this project - thank you! I just started learning (this morning) and
I am already pushing out some alpha mods to the lockscreen thanks to your tool!!
It is a great tool, and I will be using it more as I learn more.
Thank you for the effort you put into this for free, it is amazing. Keep it up!
Featured Projects
These projects were created with the help of VTS, check them out :good: (alphabetical order)
XDA:DevDB Information
Virtuous Ten Studio, Tool/Utility for the Android General
Contributors
Diamondback
Version Information
Status: Stable
Current Stable Version: 3.6.30.14100
Stable Release Date: 2014-06-30
Created 2013-11-14
Last Updated 2014-10-31140403331Okay, everyone, we are getting ready for release. :highfive:
However, there are a few points everyone has to understand, so I'll publish them prior to the official launch to get a bit more attention. :silly:
First of all, a huge thanks to my beta testers and tutorial authors: (alphabetical order)
- Dunc001
- eg1122
- Fernando sor
- fisha21
- Gumby63
- il Duce
- jeffsanace
- mcluvn
- memnoc
Let's have a look at the new key features being added in this release:
- VTS is now able to decompile m10 images. This means everyone can do skins for HTC Sense devices
- Navigatin in XML documents is much easier now. Simply hold CTRL and click on any reference inside a XML document to jump to the source
- The content of smali documents gets automatically checked for syntax errors now. Live. And in color.
- We worked hard to provide you useful guides and tutorials on the new website. Additionally, VTS has a (little) help system built in. These are short explanations for a few key features. You can find everything related to "Help" in the new Help tab.
- It seems nobody saw the potential of the old "Backup" feature, so in this version I added an additional window to easily compare different projects, folders and files. This comes in super handy when porting all kinds of stuff to new apk/jar versions for example.
Okay, so, this is only a super short list of new features, the full list of changes (almost 2 pages long) can be found (as always) here:
VTS Changelog
A few additional notes:
- I changed the license system a bit to help those that had to start VTS with admin rights to find the license. However, to fully use that fix, you need to activate your license in VTS again. Have a look at your license email if you don't remember anymore how to do that.
- This release should fully support Windows 8. There's a little glitch in the "View tab" where one checkbox is a bit cut off, but I'll fix that with the next version.
- Speaking of the next version.... This is the last release with support for Windows XP. The next version (the one after the the one that will be released shortly ) won't suppor XP anymore. So if you are still using XP (shame on you ), remember to not update after this release.
- Despite having fixed the admin issue with licenses, it still seems that VTS needs admin rights for certain other things. If something goes weirdly wrong, try restarting VTS with admin rights.
