Remove All Ads from XDA

[TOOL] Tickle My Android - Decompile & Deodex With Ease

6,576 posts
Thanks Meter: 8,348
By Ticklefish, Recognized Themer on 3rd May 2012, 04:15 PM
Post Reply Email Thread
Announcement from Ticklefish: Now Updated With Apktool 2.4.0!

Now in its 6th year, Tickle​ My Android is the only decompiling and deodexing tool you'll ever need!

Download Version 15.5.0 From Here:
(Please remove any existing previous versions of TMA from your PC before installing.)

Click The Box Below For The Changelog:
Version 15.5.0 - Icon Replacement Option Removed, Fixed Multiple Recompiling, Deodex Option Hidden

Version 15.2.0 - Added An Option To Keep A Modified Manifest When Recompiling With Original Signature

Version 15.1.0 - Improved Deodexing Options, Faster WorkArea Changing, De/recompiling Without Framework Warning

Version 15.0.0 - Improved Deodexing, WorkArea Renaming, Improved Framework Installing, Assorted Changes

Version 14.4.0 - Updated Pull Menu, Nougat Deodexing, Bug Fixes

Version 14.3.0 - Dynamic Deodexing, ZIP Creating Fix, Improved De/Recompile Logs

Version 14.2.0 - Corrected V2 Signature Handling, Improved & Updated Deodexing, Compatibility With Apktool Improved

Version 14.1.0 - V2 Signature Handling, Improved Deodexing

Version 14.0.0 - Faster ZIP Creating, Vector Icon Compatibility, Debug Mode, Multiple Code Changes

Version 13.30 - Marshmallow Deodexing, Marshmallow Xperia Sqsh Processing

Version 13.2.0 - Dalvik Cache Wiping Options Available In Advanced ZIP

Version 13.1.0 - Improved Icon Changing, Greater Flexibility In Selecting apktool Versions, Two New apktool Versions, Updated Indonesia Strings

Version 13.0.0 - Batch Decompiling And Recompiling, Small Code Changes

Version 12.0.1 - Spanish Language, New apktool, New Smali, New Baksmali, New oat2dex

Version 12.0.0 - Completely Rewritten Deodexing Menu, Verbose Option Added, Theming Menu Layout Changes, Improved History Logging, Apktool 2.0.2., New Versions Of adb, aapt, smali, baksmali, oat2dex

Version 11.1.1 - Deodexing Improvements, 'Dirty' Apktool

Version 11.1.0 - Removed Quick Menu Option, Fixed Boot Animation Resizing, New Theming Menu Layout

Version 11.0.0 - New Quick Menu Option, Corrected Thinking Display, Experimental APKTool, Minor Fixes

Version 10.4.4 - Small Bug Fixes

Version 10.4.3 - Minor Update With Improved Logging And Corrected APK Install Feedback

Version 10.4.2 - Improved History Logging

Version 10.4.1 - Improved Icon Changing

Version 10.4 - Improved Lollipop Deodexing

Version 10.3 - Added ability to generate logcat files

Version 10.2 - Improved Lollipop deodexing, bug fixes

Version 10.1 - Extra theming menu options

Click The Box Below To See The Credits:
(All The People I Have To Thank)
Big thanks go to these people, without their hard work none of this would be possible:
@Brut.all, @iBotPeaches, @scrosler and @JesusFreke.
I actually have a lot more people to thank than that.
So many, in fact, that it now crashes the website if I try to list them all!
So thank you so much to everybody who's helped over the years. You're all amazing people!

Click Here For Frequently Asked Questions And Help

TMA is a quick, powerful and easy-to-use tool that can pull apps from your phone or tablet. It can then use a very clever bit of java called apktool to decompile them and recompile them.
Which is cool, but it do so much more. Tickle My Android can....
  • decompile and recompile multiple files in a batch,
  • unzip image files from apk files,
  • zipalign apk files,
  • sign recompiled apk files in the same way as the original,
  • create backup-generating flashable zip files,
  • create standard flashable zip files,
  • take screenshots of your device,
  • let you choose between which version of Apktool you want to use,
  • lets you theme up to six different roms or devices at the same time,
  • generate logcat files,
  • come in several different languages
  • ..and can be controlled by keyboard or MOUSE!

To use Tickle My Android, you will need:
  • - a rooted Android phone or tablet with USB Debugging enabled and a recovery installed (either ClockworkMod or TWRP) ,
  • - any version of Android on that device,
  • - a Windows PC (XP or above) with the phone or tablet's drivers installed,
  • - Java Runtime Environment 8.0 or above installed to your PATH (http:​//www.​java.​com/en/download/help/path.​xml​),
  • - a USB cable to connect your device to the PC,
  • - patience and a little common sense
If you're running Android 4.3 or above, you'll also need to give USB Debugging permission on your phone when this sort of message pops up on the screen:

(Thanks to @carl1961​ for the picture)

Download the tool to the root of 'c:' from the link at the top of this post and run it. This is a self-extracting archive which, once it's extracted everything, will put on your PC a new folder called "Tickle My Android". This is where the tool runs from.

The "_WorkArea1", "_WorkArea2", "_WorkArea3", "_WorkArea4", "_WorkArea5", "_WorkArea6", "_WorkArea7" and "_WorkArea8" folders we'll talk about later.
The "tool_files" folder contains various files Tickle My Android needs to run. Don't touch these!
The "user_files" folder will hold your icons backups, boot animations and fonts. In here are your log files as well, you might need those later.

And the "Tickle My Android" exe file starts the tool. Double click on that and away we go!

How To Decompile An Application

The very first thing you need to do is backup your device. If you don't know how to do this, it's worth finding out first before going any further. Tickle My Android lets you change the very workings of your device and if you don't know what you're doing, it's possible to get things wrong. If you haven't made a backup, you could lose everything.. And that would be bad.

Next, you need to install your resource apks.

No idea what this means? Files with the '.apk' extension are the actual Android app's and some apks contain information that TMA will need before it can decompile any others.

Those apks are known as "resource" or, sometimes, "framework" files. The most common resource file is "framework-res.apk" but there are others.

First pick your WorkArea.

There are eight WorkAreas in total, which means you can easily work on up to eight different rom's or devices without having to reset the tool everytime you want to change from one to the other.
Each WorkArea is completely separate from the others and you can easily change which one you're using in the Settings Menu.
You can even rename them! Click below to find out how..
To rename a WorkArea, just rename it in Windows Explorer as you would normally. Start Tickle My Android and choose which WorkArea you want from the Settings Menu. Easy!
Just make sure you don't use any spaces in the name, don't make the name too long and make sure it starts with an underscore or TMA won't recognise it.

Inside each WorkArea are five folders. The '_deodex' folder is used for deodexing files (this is covered in the next few posts), the '_in' folder is where files about to be decompiled go, the '_working' folder contains the results of that decompiling and the '_out' folder contains the recompiled files. There's also a "Frameworks" folder, which will contain the framework files you've installed. You can pretty much ignore that most of the time.

For now though, you can actually ignore all this. When you first use TMA,​ you'll be in WorkArea 1 by default and we'll cover the other folders later.

So, to begin decompiling your application, go to the Theming Menu.

Next select the Pull Menu.

This gives you the option of pulling (copying from your Android device to the PC) one of the most commonly modified system files, or any other file you wish.

Pull and install 'framework-res.apk'. This is the most common resource apk. Depending on your device or rom, you may need to install others as well. You'll normally find these in your framework folder with "resources" or "res" in the filename, and I've listed the most common ones.

If in doubt, use the 'ADB Shell' option in the Title Menu and enter the command 'ls system/framework' to see what files you actually have in the framework folder.


Once you've installed the relevant resource apks, you'll need to decompile some apks. Which ones? Well, that's the tricky bit as it all depends on what sort of mod you want to do. If you're on Gingerbread (Android 2.3) or higher, the chances are you'll need to pull and decompile SystemUI.apk.

Once a file has been decompiled, have a look in the "_WorkArea1_working" folder. You'll see a folder with the same name as that file, this contains all the various files (images, xml, smali, etc) that the file you pulled actually consists of. Now you can make all the changes you desire.

How To Recompile An Application

Once you've finished changing things, go back to the Theming Menu and select the Recompile Files option and put everything in that folder back into a single file.

You'll have the option to recompile with the original signature, new signature or no signature. For most mods you'll want to use the original signature.

Only use a new signature if you've changed the Android manifest. If you have no idea what that means, don't worry about it and just use the original signature.
If you do use the original signature, TMA will ask you if you want to keep the modified AndroidManifest.xml. For now, unless you are changing that file, just say no. This is something you may find useful when you do more modding.

If you're using "apktool_2.3.2.jar" or above, you'll be given to recompile with aapt2 support. Some new APK files are being constructed with aapt2 and you may need this for those. Or you might not.
If your APK doesn't recompile properly, or it does and it doesn't work, try changing this option first. You never know, it might just be what you need to get your app to work..

You'll next be presented with this screen:

Don't worry about it for now, just enter "n". This is a useful shortcut for when you've used TMA a few times. But, for now, we'll ignore it.

The recompiled file will now be in the "_WorkArea1_out" folder. From there you can push it back to the device.

How To Put A Recompiled Application Back On Your Device

This is where your recovery comes in. Select the Create Flashable Zip File option to create a flashable zip. There are two types available:

The 'Advanced Zip' and 'Advanced Zip [Android 4.1+]' use the Universal Flashing Tool by JRsoft and Intronauta. This is an absolutely incredible tool and full credit goes to them.
These zips can do a lot of cool things but the bit that I like most is that they create a flashable backup of every file you've changed.
Don't like what you've changed? Just flash the backup!

However, the advanced zips don't work with all versions and ports of every recovery program. If you find yourself faced with an error message saying that "we need at least one sdcard mounted", the advanced zips aren't compatible with your recovery. That's where the 'Standard Zip' comes in. This doesn't generate a backup, it's just an ordinary flashable zip file.

Just select the option to use files from the "_out" folder. If you've recompiled 'framework-res.apk', put it into 'system/framework'. If you've recompiled 'SystemUI.apk', put it into 'system/app'. Any other files, make sure you took note of where they were pulled from.

Simple, no?'s supposed to be. But if you're having trouble, here is an awesome video by Tomsgt123 on Youtube, showing you what to do.
It's for v5, but the general principles will apply to the later versions as well. Check it out!


What is Tickle My Android compatible with?

Tickle My Android's decompiler function always uses the very latest apktool files, as well as the very best aapt files, available. But, because Android is an open-source OS, there always be some implementations of it that TMA​ will not be fully compatible with. Click the box below to see the current setups that are causing trouble:
  • MIUI apk files are often constructed in a different way to the Google standard..and MIUI aren't sharing how they're made. Which means apktool might struggle to decompile those apk files.
  • Apktool also struggles to decompile files from HTC Sense v4.0+ for exactly the same reason.
  • And apktool has trouble with Huawei's apks as well.
  • Samsung make some amazing phones and tablets and they deserve to be one of the big Android OEM names. However. .they don't like Android very much. It's no secret that Samsung want to get away from Google and use their own software. Until they get to that stage though, they seem determined to make their Android rom's as non-stock as possible. And one of the ways they do this is by having different filenames and even different formats for their image files. As far as I can, I've tried to keep TMA​ compatible with all of the different Samsung variations but there's always a chance that you won't be able to automatically change the icons on some Samsung rom's.

It is very frustrating that some companies take an open-source OS and use it to make a closed-source rom.

If you can't decompile an apk and all you want to do is change some of the icons, you now have the option to 'Unzip Image Files'. This will take just the image files from an apk and put them into the '_working' folder. Be aware that this option is really for experienced themers only.

What happens if it goes wrong?

Tickle My Android has been designed to be easy to use but the very nature of Android means that things might not always go smoothly.

If you're having problems, look at the 4th post in this thread: http:​//forum.​xda-developers.​com/s...tcount=​4​ This is the FAQ post which should hopefully be able to help you out.

If you're still having trouble, please feel free to post in here. Include your "history.txt" which you'll find in the "user_files/LOGS" folder and I'll try to get to back to you as soon as I can!

How To Say "Thanks"..

TMA is free and always will be. You can use it as much as you like, you don't owe me anything.

But, if you want to give something back, you can help me promote this. Please consider placing one of the banners below somewhere in your signature. Your support lets me know I'm doing something useful and it keeps this tool alive!! Spread the word!

XDA:DevDB Information
[TOOL] Tickle My Android - Decompile & Deodex With Ease, Tool/Utility for the Android General


Version Information
Status: Stable

Created 2018-11-30
Last Updated 2019-03-04
The Following 681 Users Say Thank You to Ticklefish For This Useful Post: [ View ] Gift Ticklefish Ad-Free
3rd May 2012, 04:16 PM |#2  
Talking How To Change Your Icons
If you'd like it reinstated, please let me know.

Changing Icons

Yes, Tickle My Android is an absolutely incredible de/recompiler but did you know that you can also use it to change the icons on your phone or tablet? can!

TMA can change your battery icons, WiFi icons, signal icons, toggle icons, softkey icons, pattern lock icons and even your emoticons!!

And it's so incredibly easy..

This is how to change your battery icons (the process is very similar for the other icons):
  1. First, start the tool and select the Theming Menu option

  2. Then the Pull Files From Device option

  3. Now pull, backup, decompile and install the relevant files
  4. This is the tricky bit, to be honest. In most roms and Android versions, battery icons are stored in framework-res.apk and/or SystemUI.apk. But you may need to install certain resource files before you can decompile those.

    If you're on a Sense(HTC)-based rom, you might need to decompile and install
    If you're on Touchwiz(Samsung), it could be that you need twframework-res.apk.
    If it's LG, then it might be lge-res.apk.
    It it's Motorola, then moto-res.apk and/or blur-res.apk.
    If it's Sony, it could SemcGenericUxpRes.apk.
    If you're on MIUI, maybe it's framework-miui.res.apk.
    Or it could be something else. Search your system/framework folder and make sure you pull and install every apk with "res" in the title.
  5. Now, after all that, go back to the Theming Menu and choose the Change Battery Icons option.

    As of right now, TMA comes with 77 different battery icons to choose from.

    That's a lot.

    That's so many in fact that I can't show them all in one post so, to help you choose between them, you'll find small previews of each one in the 'user_files\ICONS\BATTERY\_previews' folder.

    The icons are fairly varied.. have a look and pick which one you like best

  6. Or why not use your own? Tickle My Android can support up to 100 different icons in each category so you can easily add more. Just create a folder in the 'user_files\ICONS\BATTERY\' folder and fill it with your images and xml.
    Please note, it is your responsibilty to make sure any images and xml you use will work. If your battery icon currently changes every 10% and you add enough images for a 1% icon, it will still change at every 10% unless you add some new xml files as well.

    When you're done, run the tool and TMA will automatically add your icons to the ones you can choose from.

    If you're really proud of your creation and you'll like it to be added to the icons that TMA comes with, just let me know!
  7. Once you know which icon to use, select it and Tickle My Android will work out where it needs to put the relevant files and gets to work.

    This is set up to cope with icons that change every 1%, 5%, 10%, whatever% so you don't need to worry about that. Please note that every battery icon will work on every device, but some may look better on higher resolutions.

  8. Once the icons and animations have been added, go back to the Theming Menu and choose the Recompile Files option. You only need to recompile the files that Tickle My Android said it was adding battery files to.

    Make sure you choose to recompile with the original signature. Otherwise your apk might not work!
  9. Now go back to the Theming Menu and select the Create Flashable Zip File option to...create a flashable zip file.

    You can create an 'advanced' zip or a 'standard' zip.

    'Advanced' zips create a flashable backup on your sdcard which is very handy if you don't like the new icons you've come up with. These don't work on every recovery though so you might need to use the 'Standard' option instead.

    If you've changed the battery files in 'framework-res.apk', or any other of your resource apps, you'll need to put that app into the 'system/framework' folder.

    If you've changed the battery files in 'SystemUI.apk', that app needs to go into the 'system/app' folder

  10. Zip files are created in the 'c:\temp' folder by default, but you can change that to whatever you wish.
  11. Copy the zip over to your device (if TMA didn't put it there directly) and reboot into recovery
  12. Flash the zip
  13. Wait a little while for it to load the new info
  14. The device reboots and...there's your shiny new battery icon!

And that's about it. If you don't like the icon, you can try another by repeating the above steps. Or you can make a flashable zip with your backed-up apk files to get back to normal.


Changing WiFi Icons, Signal Icons, Notification Toggles, Emoticons, Softkeys And Pattern-Lock Icons

You can also use the same process to change other icons on your device. There are a few slight differences but it's still the same idea.

All the icons can be found in the 'user_files\ICONS' folder. Some are designed to match certain battery icons, some are a little..odd, but all should work with your phone or tablet.

It's worth mentioning that different roms use icons in different ways. It's possible that the icons you've selected won't work quite the way you'd want. That's why it's so handy having a backup!

Try them out, see which one works for you and let me know how it goes!
The Following 188 Users Say Thank You to Ticklefish For This Useful Post: [ View ] Gift Ticklefish Ad-Free
3rd May 2012, 04:17 PM |#3  
I'm working on a dedicated, standalone, deodexing tool which will be released soon. If you'd like to try TMA's deodexing function, please enter "deodex" at the title menu. But please be aware that it might not work!


Sometimes you'll find that you need to DEODEX an APK or a JAR file before you can make the mod you want. This process has gotten more complex and more complicated with every version of Android, but you don't need to worry about that....because TMA can do it all for you! Read on to find out how..

First, some FAQ's:

- What Is The Difference Between An "Odexed" And "Deodexed" File?
Android app's are written in Java. When they're compiled, the java code is amalgamated into one file called "classes.dex". Before the app can run on your phone or tablet, Android has to extract that file, convert it into a language called "Dalvik" and insert that Dalvik code into a section of memory called the "Dalvik Cache".
This happens at different times, depending on which version of Android you're using, but it has to be done to every app and Java file in your system memory the first time you turn your device on. Which can take a lot of time. So, to make things quicker, OEM's have the option to put the classes.dex file into a separate file. This new file has the extension ".odex". So you could have a "SystemUI.apk" and a "SystemUI.odex", for instance.
It's possible to mod this odex file, but it's a pain to do so, so sometimes we want to put the classes.dex file back into the app. That is what deodexing does.

- Will Deodexing Make My Rom Any Faster/Slower?
Deodexed files take longer to convert into dalvik than odexed ones. This only happens if you reboot your device after wiping the Dalvik Cache. If your rom is fully deodexed, it will take noticeably longer to start back up but it's rarely an issue. It's just longer to wait, that's all.
Otherwise, the performance of your device is not affected in any way.
At all.

Right, let's get to business. It's time to start deodexing!

First, go to the title menu and select the "deodexing menu" option:

Before you can deodex anything, you'll need all the right files in your "_deodex" folder. You can use the "Pull Relevant Files From Your Android Device" for TMA to get all the files it needs automatically.
Or you can do it yourself by copying your "system/app" and "system/framework" folders to the "_deodex" folder. You'll also need your "system/build.prop" file as well.

If you're using Android 4.0 or above, you'll also need to provide your "system/priv-app" folder.

Once all the files are in place, pick the "Deodex Rom" option that matches the version of Android you're using and confirm that you're happy to go ahead.

Tickle My Android will now start processing all the files and turning them from "odexed" to "deodexed".

This can take some time. The bigger the rom is, and the more files in those folders, the longer it will take for them to all be processed. Hopefully the program will be able to process all of them but, occasionally, it might encounter a file that can't be deodexed.

This could happen for a lot of different reasons so have a look in "history.txt", which you'll find in the "user_files/log" folder. That should tell you what the problem is.
Sometimes it's not a problem that can be easily resolved so you might be better off just deleting the troublesome app from the relevant folder and installing it later. My stock MM rom had a copy of Play Music which couldn't be deodexed for some reason..

Once everything's been processed, TMA will create a flashable ZIP that can be used in either CWM or TWRP to deodex your rom.

PLEASE MAKE SURE YOU'VE BACKED UP YOUR DEVICE BEFORE FLASHING THIS ZIP! In theory there shouldn't be any problems but it's always a good idea to play it safe.

Flash the ZIP, wipe the Dalvik Cache, reboot and...that's it. It's as simple as that. Hopefully your rom should now be fully deodexed and you can start doing some serious modding to it. But, as always, if you have any problems, let me know!
The Following 127 Users Say Thank You to Ticklefish For This Useful Post: [ View ] Gift Ticklefish Ad-Free
3rd May 2012, 04:18 PM |#4  
Cool Frequently Asked Questions

Having trouble using Tickle My Android?

Something not making sense?

Something not working the way it should?

Read on..

Q. I can't de/recompile something!

A. With Android being open-source, more and more companies and developers are putting their own spin on the OS and it's not unusual to find that something won't compile even when there's no obvious reason why it should.

I can help..but you need to do something for me first.

In your 'user_files\LOGS' folder, you'll find various decompiling and recompiling well as 'history.txt'.

Share that file with me, ideally by copying and pasting it into the post, and let me know a little bit about what's going wrong.

That should give me enough information that I will be able to fix your problem.

Please be aware that I won't be able to help you without this information.

Q. I've Used Apktool 2 And I'm Getting An Error When I Try Adding Smali Files!

A. I've encountered this a lot lately so I thought I'd best make a FAQ about it.

So you've decompiled an apk with a version of apktool 2 (like apktool 2.0.0b9), you've added some smali files, tried to recompile get errors that look a little like this:


Recompiling "LenovoSystemUI.apk" With Original Signature,
using "apktool_2.0.0b7.jar"

With Tickle My Android


..\_working\LenovoSystemUI.apk\smali\fx\dzolcp\Spe ed$1.smali[24,4] Error for input '.parameter': Invalid directive
..\_working\LenovoSystemUI.apk\smali\fx\dzolcp\Spe ed$1.smali[40,4] Error for input '.parameter': Invalid directive
..\_working\LenovoSystemUI.apk\smali\fx\dzolcp\Spe ed$1.smali[41,4] Error for input '.parameter': Invalid directive
..\_working\LenovoSystemUI.apk\smali\fx\dzolcp\Spe ed$1.smali[40,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE
Exception in thread "main" brut.androlib.AndrolibException: Could not smali file: fx/dzolcp/Speed$1.smali
at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuil
at java:56)
at java:41)
at brut.androlib.Androlib.buildSourcesSmali(Androlib. java:337)
at brut.androlib.Androlib.buildSources( 298)
at brut.apktool.Main.cmdBuild(
at brut.apktool.Main.main(


Recompile Not Successful!

(thanks to @zant76)

This 'Error for input '.parameter': Invalid directive' error is caused by a difference in the davlik assembler/disassembler used in apktool 1 and the one used in apktool 2.

Apktool 2 uses smali/baksmali v2, which doesn't like smali files generated by smali/baksmali v1.

Basically, if you're seeing this error, you need to use apktool 1.5.2 to decompile and recompile your apk. Once the apk's been recompiled, you can use apktool 2.0.0b9 to decompile it again.

(If you're feeling nice, once you've decompiled your apk with apktool 2, why not share your new smali files with the thread you got the original files from? Just like this nice guy here:
You never know, you just might help somebody else who had this error. )

Q. How Do I Use My Own Version Of Apktool?

A. Apktool is a great piece of software that makes it possible to decompile and recompile almost any Android application. The trouble is that Android is open-source and some roms are made a little differently from the Google norm. Which means that stock apktool might not be able to do anything with those apps.

In some cases, clever people have been able to mod apktool itself so it works on those roms. If you've got a rom that needs a custom apktool, it is possible to use it with TMA. And very easy too!

Have a look in the 'user_files/apktool' folder:

At the time of writing Tickle My Android comes with four different versions of apktool to choose from and they're stored here.

If you want to use your own modded version, just copy it into this folder.

If it's a version of apktool 1, give it a name that starts 'apktool_1' or 'apktool-1'.

If it's a version of apktool 2, give it a name that starts 'apktool_2' or 'apktool-2'.

This will ensure that Tickle My Android can use the file correctly. Just be sure not to use any spaces in the name!

Then just run TMA, go to the Settings Menu, select your apktool and use it. It's that simple!

Q. I'm getting a 'Java Not Installed" error...but I do have Java installed!!

You may have Java installed...but you probably don't have it in your PATH.

TMA is a batch file, which runs in a command-line environment. If you don't have Java in your PATH, the tool won't be able to access it and won't be able to do any decompiling or recompiling at all.

Adding Java to your PATH is actually a lot easier than it seems. Have a look at the official guide here:

(Big thanks to @carl1961 for the pictures!)

The Following 106 Users Say Thank You to Ticklefish For This Useful Post: [ View ] Gift Ticklefish Ad-Free
3rd May 2012, 04:32 PM |#5  
si_bolang's Avatar
Senior Member
Thanks Meter: 26
required SDK &other tools?

Sent from my GT-S5660 using Tapatalk 2
The Following User Says Thank You to si_bolang For This Useful Post: [ View ] Gift si_bolang Ad-Free
3rd May 2012, 04:46 PM |#6  
Originally Posted by si_bolang

required SDK &other tools?

Sent from my GT-S5660 using Tapatalk 2

Nope, everything that's needed is included. You do need to have the right drivers installed but that's about it.
The Following 24 Users Say Thank You to Ticklefish For This Useful Post: [ View ] Gift Ticklefish Ad-Free
4th May 2012, 10:53 PM |#7  
Cach123's Avatar
Senior Member
Flag Ålesund
Thanks Meter: 17
Originally Posted by Ticklefish

Nope, everything that's needed is included. You do need to have the right drivers installed but that's about it.

Hey, how do i get transparensy statusbar? i use cm 7.2 can it work then ?

Edit: Great tool btw
5th May 2012, 12:05 AM |#8  
Decompile your framework-res.apk and SystemUI.apk, then use the Change Status Bar Color option. :)

It should work on your rom but not every launcher supports transparent statusbars. Let me know how you get on!

Oh,and thanks!

Sent from my SK17i using xda premium
The Following 16 Users Say Thank You to Ticklefish For This Useful Post: [ View ] Gift Ticklefish Ad-Free
5th May 2012, 07:56 AM |#9  
X-Droidinary's Avatar
Senior Member
Flag Wyong, NSW
Thanks Meter: 31
Donate to Me
Just wondering if you could make these for me with your tool cos i'm likely to do something wrong if I try it myself lol.

I don't want on screen buttons.

5th May 2012, 10:51 AM |#10  
tarekh020's Avatar
Senior Member
Thanks Meter: 181
How to change status bar in cm7.2 to make look like miui status bar

Like This :
5th May 2012, 04:50 PM |#11  
Senior Member
Thanks Meter: 310
First off, thank you! This seems like a great useful tool. The problem im having is that following the steps above, whenever i get to where i decompile the apks and its says the files are placed in the "working" folder, nothing is in there? What could i be doing wrong?
Thanks for your help
Post Reply Subscribe to Thread

apktool, decompile, recompile, smali, xml

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes