Tickle My Android 14.2 – Decompiling & Deodexing Made Simple!

This is the complete tutorial on Tickle My Android.
In this tutorial i will explain about how to use Tickle My Android 

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. By Using Tickle My Android Users can :

  • change the battery icon

  • change the WiFi icon

  • change the signal icon

  • change the emoticons

  • change the notification toggles

  • change the softkeys

  • change the pattern lock icons

  • change the lockring icons

  • 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

  • deodex apk and jar files

  • resize and change boot animations

  • change fonts

  • create backup-generating flashable zip files

  • create standard flashable zip files

It can 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!

Must Read :- How to Decompile/Recompile Apk using Apk MultiTool

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/down /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:


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” 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.

This is new to Tickle My Android. You can now work on up to six 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.

Inside each WorkArea are four 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.

Also Read :- Build Prop Tweeks For Android (Android 4.3+ Versions)
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.

 Also Read :- How to run muitiple apps on foreground in Android N

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.

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!

Also Read :- How to automatically skip Youtube Advertisements on Android without Rooting

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?

Well..it’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…

Also Read :- Top 5 Boot Animations for Android !

Downloads :-

HOW TO Full Install TickleMyAndroid Decompile, Recompile =BANGLA= Tutorial.. 👇👇

via Blogger http://www.droidadda.org/2016/12/tickle-my-android-142-decompiling.html https://mtkdr0id.files.wordpress.com/2016/12/425f4-images.jpg?w=300


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s