Yep here they are. If it makes a difference its a ZTE Axon 7. trying to add 3minit and change signal icon to steel blue.
SystemUI too big to upload here is link https://www.dropbox.com/s/m9ba3t1ocacqy27/SystemUI_ZTE.apk?dl=0
Yep here they are. If it makes a difference its a ZTE Axon 7. trying to add 3minit and change signal icon to steel blue.
SystemUI too big to upload here is link https://www.dropbox.com/s/m9ba3t1ocacqy27/SystemUI_ZTE.apk?dl=0
@Ticklefish,
I think there is an inversion for recompil between option 2 and option 4 (7.0+).
I have mod my SystemUI (6.0.1 Samsung base) with option 2 and at the end of compilation, there is a lot of files witch are copy (ressources.arsc, qmg...). It result that it break something on my phone into data/system/users/0/runtime-permissions.xml. Then if i flash a vrtheme for change some png into my systemUI, statusbar disappeare, SystemUI is broken.
If i recompil with option 4 (7.0+), no files are copyed at the end of compilation, no problem, everything working, even if i flash my vrtheme.
I think there is an inversion for recompil between option 2 and option 4 (7.0+).
I have mod my SystemUI (6.0.1 Samsung base) with option 2 and at the end of compilation, there is a lot of files witch are copy (ressources.arsc, qmg...). It result that it break something on my phone into data/system/users/0/runtime-permissions.xml. Then if i flash a vrtheme for change some png into my systemUI, statusbar disappeare, SystemUI is broken.
If i recompil with option 4 (7.0+), no files are copyed at the end of compilation, no problem, everything working, even if i flash my vrtheme.
This is why your APK won't recompile:
Code:
W: res\drawable-v19\stat_sys_signal_0.xml:0: error: Resource entry stat_sys_signal_0 is already defined.
W: res\drawable-v19\stat_sys_signal_0.png:0: Originally defined here.You have a lot of these sort of errors in the recompile log. This is because your APK uses XML files to draw the signal icons (these are known as 'Drawable Vectors') and you've used TMA to add a load of PNG files with the same filename. Apktool doesn't like it when two or more files have the same filename in the same folder and that's why the recompile fails.
All you need to do is go into your "drawable-v19" and "drawable-v21" folders and delete all the "stat_sys_signal_*.xml" files that you have a matching PNG file for.
Option 2 creates a copy of the original APK and then copies the res folder into it, along with the manifest and the classes.dex. This is to keep the signature the same.
With Option 4, you can't keep the signature the same as Nougat won't accept it. So TMA deletes the SEC-INF folder (if it exists) in the new APK and signs it with a new signature.
It sounds like some files in your original APK aren't being put into the recompiled one. This sadly has happened before and was discussed here: http://xdaforums.com/showpost.php?p=69671411&postcount=5854
I've reported this bug to apktool's developer here: https://github.com/iBotPeaches/Apktool/issues/1366
Have a look at the number of files in your original res folder and the recompiled one. If there's a difference that's probably what's causing the problem.
Thanks for theses explanations !
Yes its that, recompiled files with option 2 are less than with option 4.
Anyway it working with option 4 so maybe my SystemUI needed to use N recompil instead of normal one [emoji4]
I tried recompiling it with the 3minit mod and it worked without any trouble at all. It's up to you whether you put a new signal icon on or not. Yes you have to delete some files but there's only a few to deal with.
I can link to the previous version if you want, just let me know if you have any recompiling trouble. The previous versions will all do the same thing though...
It's more that Samsung need to stop messing around and making weird APK files..
Can you share your files please? I'll add them to my bug report on the apktool github and it should help get this fixed. :highfive:
Last edited:
I have no problem deleting files, its just that 3minit is the priority for me at the moment. And i had same issue with just 3minit mod.
izarcc crash and failure. Now i should mention I am attempting to recompile with original signature. As i am under the assumption systemui with different signature would fc continuously or something like that.
It will recompile with new signature for me no problem. But although i have added 3 files it comes out slightly smaller then original. 53.3mb orig and 52.9 on new sig apk.
I have not dared test it yet.
Last edited:
Thank you!
I was able to recompile with original signature without any problem. Izarcc didn't cause any trouble. Odd. Are you able to share a screenshot of the error at all?
It's not unusual for the recompiled APK to be smaller than the original one. The smali files aren't that big. It's just the way it's compressed.
You can test the new file. Just, as always, make sure you have a backup in case it doesn't work. I generally always have a ZIP file with a stock SystemUI.apk on my SDCArd just to play it safe.
had to do 2 shots to get details but here ya go.Thank you!
I was able to recompile with original signature without any problem. Izarcc didn't cause any trouble. Odd. Are you able to share a screenshot of the error at all?
Attachments
Think I will try it on my windows 7 machine later today see what happens.
Update: worked fine on win 7 machine,:victory: so guess problem with my laptop. Think i should check the memory on there. maybe bad stick or something.
Just waiting on answer from Gharrington about 3minit before I test it.
Thank you for all your help. And this great tool. Get to try stuff I had to ask others for.
Update: worked fine on win 7 machine,:victory: so guess problem with my laptop. Think i should check the memory on there. maybe bad stick or something.
Just waiting on answer from Gharrington about 3minit before I test it.
Thank you for all your help. And this great tool. Get to try stuff I had to ask others for.
Last edited:
I'll be honest..I'm completely perplexed by this. I don't know why the APK made by v14.2 doesn't work and the one made by v14.1 does..
Recompiling with the original signature works a bit differently in each version. In 14.1, apktool 2.2.0 has the ability to copy the original META-INF and SEC-INF folders into the new APK so TMA just uses that. Apktool 2.2.1 removed that ability so the v14.2 instead creates a copy of the original APK in the _out folder and copies the res folder, classes.dex and resources.arsc into that.
I did wonder if your issue could be caused by a different compression rate. Maybe v14.2 compressed a certain file in a different way to v14.1 and it's causing a FC. But all the obvious candidates seem to be compressed correctly. There are a few differences but nothing that should cause a problem.
Hang on a second...
Your original APK has more files in the "drawable" folder than the recompiled v14.2 APK. All your stat_sys_wifi_captive*.pio files are missing in the new app. It looks like apktool is completely ignoring them.
I think we may have a genuine apktool bug on our hands here, which may well explain why the new file doesn't run.
I'll report this on the apktool thread and we should hopefully have a resolution soon. :good:
Oh, I'm also seeing a lot of Touchwiz files in here. Should have known that it would be Samsung causing trouble again..lol
Ok, thanks again for your support in trying to explain this "bug" :highfive:
and a lot of patient to Touchwiz of Sam .
Ok, thanks again for your support in trying to explain this "bug" :highfive:
and a lot of patient to Touchwiz of Sam .
You have to be patient with Samsung. They do some amazing phones but their roms are horrible..
TMA NEEDS YOUR HELP!
Hiya folks. With the holiday season fast approaching I'm trying to distract myself from the financial ruin I'm facing from buying all these presents...by working on the next version of Tickle My Android!
And I could do with your help. If you're feeling kind, could you guys please share your "build.prop" files?
I'm mainly looking for files from devices with an arm64, x86 or similar processor.
Thanks in advance! :good:
Tomorrow I will send you two build.prop of my S7 Edge, one from Marshmallow and another from Nougat Beta. Today my wife dont let me touch the pc [emoji28] [emoji28]
Ha, that's what wives are for..
I got quite lucky tonight. Mine actually let me touch the remote control for the TV.
It was while I was passing it to her but still...lol
Thanks in advance and thanks to everybody who's already shared. You're all good people!
Here my build prop.
build.prop from Asus ZenFone 2 laser ze601kl arm64 marshmallow 6.0.1
build.prop from Asus ZenFone 2 laser ze601kl arm64 marshmallow 6.0.1
Hey @Ticklefish this is my build.prop.for sony xperia z5 dual
thanks for your great work :good:
thanks for your great work :good:
Here is mine, Xperia Z3 MM http://cloud.tapatalk.com/s/583c1b9144fbf/build.prop.zip
Gesendet von meinem D6603 mit Tapatalk
Gesendet von meinem D6603 mit Tapatalk
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
714
Tickle My Android - Over Seven Years Old And Still Going Strong!
Download version 16.5 from here: https://www.androidfilehost.com/?fid=4349826312261743827
Click The Box Below For The Changelog:
Click The Box Below To See The Credits:
(All The People I Have To Thank)
Click Here For Frequently Asked Questions And Help
TMA is a quick, powerful and easy-to-use tool that uses a piece of java called "apktool" to decompile and recompile Android app's.
Along with that, Tickle My Android offers the ability to:
- decompile and recompile multiple files in a batch,
- sign APK and JAR files
- zipalign APK files,
- create flashable ZIP files,
- let you choose between multiple versions of Apktool
- lets you theme up to eight different roms or devices at the same time,
- use the tool in different languages
- control the tool by keyboard or MOUSE!
To use Tickle My Android, you will need:
- - a rooted Android phone or tablet with USB Debugging enabled and a custom recovery installed,
- - 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
(Thanks to @carl1961 for the picture)
Download the latest version from the link at the top of this post and run it. (Please don't look in the 'Downloads' tab - it's not working right now.) 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 holds different versions of Apktool, as well as the different language files.
And the "Tickle My Android" exe file starts the tool. Double click on that and away we go!
How To De/recompile An App
How To Add An Application To A Flashable ZIP
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/showpost.php?p=25621684&postcount=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" 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, 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 & Recompile With Ease, Tool/Utility for the Android General
Contributors
Ticklefish
Version Information
Status: Stable
Current Stable Version: 16.3
Stable Release Date: 2019-11-30
Created 2018-11-30
Last Updated 2019-12-03
XDA:DevDB Information
[TOOL] Tickle My Android - Decompile & Recompile With Ease, Tool/Utility for the Android General
Contributors
Ticklefish
Version Information
Status: Stable
Current Stable Version: 16.5
Stable Release Date: 2020-03-12
Created 2018-11-30
Last Updated 2020-03-12191How To De/recompile An App
Decompiling and recompiling an Android app for the first time can seem quite complicated and time-consuming, but it really isn't once you know what you're doing.
First you'll need to choose which WorkArea you want to use. 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.
Inside each WorkArea are five folders. 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 last one most of the time.
(When you first use TMA, you'll be in WorkArea 1 by default.)
To decompile an app, you'll first need to put the relevant APK in the "_in" folder. You can either copy this into the folder yourself or you can 'pull' it from your Android device. If you want to pull the file, this next section is for you. If you don't, skip ahead to the one after that.
How To Pull A File
First select the "Pull FileFrom Device" option.
This gives you the option of pulling some of the most commonly modified system apps, or any other file you wish.
Choose which file you want to pull and the tool will try to do that for you. If the pull fails, it could be that you don't have the adb drivers installed on your PC for your particular device, or the file doesn't exist, or any one of a number of things. Have a look in the "history.txt" file that's automatically generated to see what's going on.
That's actually all we need to know about pulling - it's really not that complicated. Once you've pulled all the files you need, you can move on to decompiling them. But you might need to install your frameworks first..
How To Install Framework Files
If you want to modify a system app (like SystemUI.apk or framework.jar) you'll need to install the right framework files. These are files that contain resources that are shared amongst most of the system apps. Those resources need to be made accessible to apktool (the program that does the actual decompiling) or the app won't decompile fully and it won't work.
There are many framework files available. Stock Android only comes with one (so far) and it's called "framework-res.apk". OEM's like to include their own, though, just to make life more interesting. Samsung used to have "twframework-res.apk" in their rom's before replacing it with "samsung-framework-res.apk". Framework files are found in "system/framework" on your devices internal memory and should be an APK file with "res" in the filename. You need to make sure you install every framework file in your rom to ensure a system app decompiles, so make sure they all are put in the "_in" folder.
Select the "Install Framework File" option and choose whether you want to install all the framework files in your WorkArea or some individual ones. You can select up to five individual files to install in one go.
If the tool isn't able to install the files you'll be shown an error, otherwise you'll go back to the install menu. If you've installed all the framework files you need to, go back to the title menu because we're finally ready to do some decompiling!
How To Decompile A File
Select the "Decompile File" option and choose whether you want to decompile all the files in the "_in" folder or individual ones.
Once you've chosen your files, you'll be asked whether you want to decompile with "Standard" or "Advanced" settings. This is new to Version 16 of Tickle My Android. Apktool has a lot of different options when it comes to decompiling and you can now choose which ones you want to use. The standard settings will just make the tool try to decompile the entire file, as it used to in previous versions. The advanced settings let you control the process a little better..
These are the main decompile options available for the latest version of apktool available at time of writing (2.4.0.). Full explanations of each are available on the apktool github here: https://ibotpeaches.github.io/Apktool/documentation/#decode. To give you an idea though, you can use "Don't Decode DEX Files" if you don't want to modify any smali files, which makes the decompile a lot faster!
Choose your options and the tool will try to decompile your file for you. If it succeeds the decompiled files will be in the "_working" folder, if not you'll get an error message. The full details of that error will be in the "history.txt" file.
Once your app is decompiled you will be free to modify it however you like. Change images, alter layouts, add functionality..whatever you want to do. When you're done, you'll need to recompile your app to be able to use it again.
How To Recompile A File
Select the "Recompile File" option and choose whether you want to recompile all the files in the "_working" folder or individual ones.
Once you've chosen your files, you'll again be asked if you want to recompile with standard or advanced settings.
You can find explanations of the first few options on the apktool github again: https://ibotpeaches.github.io/Apktool/documentation/#rebuild. It is very important to know what the options that you've selected but there are two that's worth paying extra attention to..
"Copy Original "AndroidManifest.xml" And "META-INF" Folder" - Modified system apps need to be signed with the same 'key' as the original app, or they won't run. This option ensures that the original key is used on the new app. If you want to change the Manifest file, though, you'll need a different key which involves disabling signature verification. That's a bit more complicated than this tool allows for..
"Use "aapt2" [apktool_2.3.2+]" - More recent apps can be constructed with a newer version of a tool called aapt. If you're trying to modify a file made with the newer version, you'll need to have this option actve for the recompile to work. There's no easy way to tell if this is needed or not so, if you get an error, try again with the option turned off.
(Different versions of apktool will have different options. Selecting an option that isn't available on the version of apktool you're using will cause an error.)
There are also options to sign and zipalign your recompiled apps. Signing uses a generic key and zipaligning can sometimes break V2 signature checks so, if you've no idea what that all means, it's best to leave these options alone until you know you need them.
And TMA has an option to put your recompiled apps into a ZIP file that you can flash in a custom recovery. I'll go into this in more detail in the next post but I always recommend replacing system apps this way. It's much safer than trying to replace them while the phone is running.
Choose your settings and sit back while the tool does its thing.
Once it's finished you'll get a message saying the file recompiled...or one saying it didn't. If it didn't, you can find the full error text in history.txt.
If your file recompiled, you'll find it in the "_out" folder. It's now ready to go back to your phone.
It's up to you how you do that but the route I always recommend above all others is using a flashable ZIP file. Check out the next post if you want to know more!128How To Create A Flashable ZIP File
Once you've got a recompiled app, you need to put back to your phone. If you've modified a system app, I always suggest using a flashable ZIP file in recovery. That way you're replacing part of the system, while the system isn't running. Using a file manager app, or using adb, is asking for trouble. I've broken a tablet that way and nearly a phone as well.
Tickle My Android can create that flashable ZIP for you and it's really easy to do so. You can either tell the tool to do it as soon as the app's recompiled, or use the dedicated option on the title screen.
To start, select the "Create Flashable ZIP File" option from the title screen. You'll then be asked if you want to use files from the "_in" folder or "_out" folder. This can be handy if you want to make a flashable ZIP of the unmodified apps. I normally have at least one of those containing my original SystemUI.apk just in case a mod goes wrong.
Next you'll be asked to choose your files. You can add up to five files to the flashable ZIP. Once you've confirmed which file, or files, you want to use you'll be asked where those files are going in the ZIP.
Make sure your apps go back to the right folder. If you put a modified framework-res.apk in the "system/app/" folder, for instance, those modifications won't be actioned.
Once you've chosen where the files are going, you'll next be asked what filename you want the ZIP file to have. TMA will automatically generate one for you based on the current date and time, but you can have whatever filename you want. Make sure not to use too many special characters or it could confuse the tool and/or the recovery. If you want to use the default filename, just press ENTER.
The tool will now ask you to confirm all the details.
If you're happy, then the ZIP will be made and placed in the same folder as the tool.
Copy this to your phone, flash it in reoovery and enjoy! But always, always, always make sure you have a backup first!!105F.A.Q.
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!
Q. I'm getting a 'Java Not Installed" error...but I do have Java installed!!
28I started this thread on the 3rd of May 2012.
That's 5 years ago.
And that's really shocking. Where have all the years gone??
To mark the occasion, I just wanted to say a big THANK YOU to everybody who's downloaded TMA, helped with debugging and new features, and all the wonderful people who post on here. I know there are other decompiling and deodexing tools out there. Your support means a lot to me, it really does.
TMA is still going. I'm not working on a new version yet, not until Android O means I have to change things yet again, or until I come up with a new feature. But this tool and this thread are still very much live. And everybody who's reading it and this post are automatically the greatest people ever!
