yashsingh1/xdaforums huggingface dataset:
[Android Themes] Ticklefish:
Could be. Some virus checkers have a problem with adb, one of the tools in the program
[Android Themes] Tulsadiver:
You definitely need to white list the folder you put it in. Also, after unzipping it, don't leave it in a folder that is in a folder, that is in a folder. Bring it out to be inside one folder that you have white listed in your virus protection.
[Android Themes] ROBERT CM:
Hi [MENTION=4315551]Ticklefish[/MENTION]

Thanks for this great tool..

A good idea would be that every workarea be independent to install the resources ..

Because whenever new frameworks are installed they replace the previous ones or when other apks are decompiled in the other workarea they replace previous frameworks ..

All frameworks are installed in the same directory

Maybe you can fix it on next versions..

Thanks!
[Android Themes] Ticklefish:
Every workarea is independent..or they're supposed to be, certainly.

When you change from one workarea to another, your installed frameworks are stored away. Then when you change back again those frameworks are installed again.

I'll give the code a test to make sure it's happening properly.
[Android Themes] Ticklefish:
I've just tested this on the latest version. I installed a framework in WorkArea1 (which created 1.apk), switched to WorkArea2, installed a different framework (2.apk) and then watched the "AppData/Local/apktool/framework" folder as I switched between the two Areas. The tool definitely changes the frameworks as it should.

Frameworks are installed in the same directory, you're right. But when you change WorkArea, your installed frameworks are taken out of that directory and stored. Then, when you change back to that WorkArea, those frameworks are put back.
[Android Themes] theHari08:
Icon changing doesn't work on touchwiz 4.4.2:(:(

The icons in system ui has changed but doesn't appear after flashing...
[Android Themes] Ticklefish:
Which icons?
[Android Themes] theHari08:
All icons...

But after flashing when i pull out and decompile the flashed system ui it has changed icons... but only the stock icons appear on my device.
[Android Themes] Ticklefish:
All icons? So you changed the pattern lock, lockring, WiFi, signal, battery, emoticons, toggles and softkey icons as well as using the vector icons?

If your stock icons are showing it could be that your rom uses code for the icons instead of image files. More and more roms since KitKat are doing that. The fact that you've replaced every icon and none of the changes are showing is a bit of a puzzle though. I'd expect it with the battery icon and possibly the signal and WiFi icons but not all of them.

Can you share your history.txt please? And a screenshot of your phone with its stock icons would be handy too.
[Android Themes] JonathanRAZ:
[MENTION=4315551]Ticklefish[/MENTION] i still cant see on the menu compile without signature
[Android Themes] Thebear j koss:
Why would you? You need some form of signature for the app to work. Some apps like google apps you need to keep signature and put into system partition and others you can build, sign, install into data. With no signature the app will not work anywhere. If you use 7zip or winrar you can open the apk as an archive and just delete the meta inf folder to get rizd of the signature.
[Android Themes] JonathanRAZ:
Signature v2 scheme
[Android Themes] Thebear j koss:
Ok, i misunderstood your request. I'm not entirely sure how that works yet as i haven't had to deal with that. I don't think building without a signature is the fix as you could just delete the meta inf folder with 7zip to delete the signature. Not sure if the v2 signature has been added yet... I gotta go back and read the changelog in the op.
[Android Themes] JonathanRAZ:
Yeah i have read some posts in here about it and talk about recompiling without sig i was looking to do some test on my own thanks you bro
[Android Themes] Thebear j koss:
I am presuming it means to keep original signature. That just means you are not resigning it.
[Android Themes] Ticklefish:
The option to recompile without a signature does exist at the top of the screen like I said in the PM...

However, that might not be what you're after. With V2 signing on Nougat you currently need to disable signature verification on your device and use the "Recompile App [Android 7..0+]" option. If you're not using Nougat, you don't need to worry about it.

I think I've found a way of putting V2 signing on an APK but I'm still doing some experimenting before I add it to this tool. It's a little tricky when I don't have a Nougat rom to test it on..
[Android Themes] hamxa266:
Can i flash zip file using any other 3rd party app ? Like flashify . because my mtk phone does not have any custom recovery!
[Android Themes] MaFiBoSS:
[MENTION=4315551]Ticklefish[/MENTION]

Thanks for your hard work :good:

You can share again the previous version 14.1.0 or 14.0.0?

I use your app (TMA) for moddify the file "SystemUI.apk" (always without any issue), but today I have a problem with the last version 14.2.0. After modified and put the file in my phone, the backgroud of my phone is black and the SystemUI.apk "can't open".

Please share, for only testing and finding if its my problem (previous version worked very well).
[Android Themes] Ticklefish:
Possibly. I haven't tried them myself but it's certainly worth trying!

Here you go: http://www.mediafire.com/file/fdiz3yru6eusj74/TickleMyAndroid_-_v14.1.0.exe
[Android Themes] hamxa266:
Okay thanks . :good:
[Android Themes] MaFiBoSS:
Thanks :D

I can now give you feedback. Already tested and works fine with version 14.1.0. The apk (SystemUI.apk) modified it's correctly compiled with original signature. No problems found at moment. So maybe there is something wrong in version 14.2.0 (I do not know, but the only difference I see is the version of apktool).
[Android Themes] Ticklefish:
Curious. Did it flash correctly?
[Android Themes] MaFiBoSS:
I did the same steps for both versions (14.1.0 vs 14.2.0).

1 - Flash the stock ROM (full wipes before flashing);

2 - Flash the TWRP recovery;

3 - Flash the last version stable of SuperSU;

4 - Copy the files (SystemUI.apk and framework-res.apk) to my computer;

5 - Install the framework with the TMA;

6 - Decompile the file SystemUI.apk and and edit for example the file in "SystemUI.apk\res\values\dimens.xml";

7 - Compiled the file with original signature;

8 - Put the file on my phone with the correct permissions and restart.

This steps were repeated for both versions and the version 14.1.0 (and previous) I dont have any problem. It's only my feedback. ;)
[Android Themes] Ticklefish:
I'll test it as soon as I can. Are you using the same version of apktool each time? And you're installing your frameworks again each time?
[Android Themes] MaFiBoSS:
The version of apktool it's different in your TMA versions 14.1.0 (v2.2.0) and 14.2.0 (v2.2.1). So, No to first question.

I do not modified nothing on TMA, just unpack and puts the files to need to be edited.

For the second question, Yes, for each file (apk) modification, I unpacked again the TMA (before I removed the frameworks on: C:\Users\User\AppData\Local and others files - "installation clean").
[Android Themes] Ticklefish:
Have you tried using apktool v2.2.1 in v14.2.0?
[Android Themes] MaFiBoSS:
Yes I tried with version 14.2.0 (v2.2.1) but it always has problem when make the recompile with original signature. So I asked you for the version 14.1.0 (v2.2.0), works fine. ;)
[Android Themes] haifish9999:
Hi [MENTION=4315551]Ticklefish[/MENTION], a little off topic I have had to use TMA latest version on my laptop running Windows 10 pro version. But I had a problem: while I had to open TMA exe, it's running and came to Thinking section and it's shutdown by itself immediately. Tried re download and installed the tool twice but no luck....It was fine with Windows 7 in early time. Do you have any clue about this issue?
[Android Themes] Thebear j koss:
There's a file in the tool_files\rewrite\settings folder called DebugOff.

Rename that to DebugOn and try running the tool again. That should hopefully give an idea of where the problem is.

You definitely need to white list the folder you put it in. Also, after unzipping it, don't leave it in a folder that is in a folder, that is in a folder. Bring it out to be inside one folder that you have white listed in your virus protection.

For the 1st time in my life i can't say i am proud to be an american. This country and the people who live here are just despicable. This is a sadder day for america than Pearl Harbor and 9-11 combined. Shameful...
[Android Themes] haifish9999:
I will try it later.Thanks for the information.
[Android Themes] Thebear j koss:
Those instructions are from a post by Ticklefish and another user from the past few pages. May want to just read back a few pages to see if there is more...
[Android Themes] Ticklefish:
I've just tried modding my SystemUI.apk with 14.2.0, using apktool v2.2.1. This was on a completely fresh install. I didn't make any changes, I just decompiled and recompiled with the original signature. The ZIP flashed without any problems at all and without any FC's.

Can you try with 14.2.0 and share your history.txt please? Then I can try to figure out what's going on in your case. :confused:
[Android Themes] MaFiBoSS:
Yes, the logs it's from version 14.2.0. But if I do (same steps) with the version 14.1.0 it works.

I did again, and the apk can't read in my phone.
[Android Themes] Klaus N.:
I've got an Sony Xperia XZ and want to deodex the current MM stock rom using your tool. But I don't find any of those files you specify:

Thanks in advance!
[Android Themes] Ticklefish:
Thanks, I'll take a look and so some investigating.

Sony have done something different again? Sigh..

Do you have any SQSH files in your system folder?
[Android Themes] Ticklefish:
This is very puzzling. I'm wondering if it's caused by something in your APK that's compressed at a different rate...hmm..

I hate to be a pain, but could you possibly share your APK files? I think I need to take a deeper look at what's happening to them when they're recompiled.
[Android Themes] Klaus N.:
At first thanks for your quick reply!

No, there isn't a single sqsh file - neither in /system, nor in any of the subfolders.
[Android Themes] Ticklefish:
Huh, maybe Sony have decided to stop using them after all. I do wish OEMs would make their mind up about how they make their odexed roms. It would make my life so much easier!!

If there's no .SQSH files in your system folder just copy over your framework, app and priv-app folders. Then use option 4 in the deodex menu.

Let me know how it goes!
[Android Themes] Klaus N.:
Ok, I'll give it a try. Just one question: Does your tool recognize the /vendor/app folder, or do I have to move the containing 3 app folders (ChromeCustomizations, imssettings and NativeAudioLatency) into e.g. app?
[Android Themes] tdunham:
Why would you need to modify anything in this location? Unless there is a specific need, I recommend leave it alone.
[Android Themes] Ticklefish:
It doesn't, no. To be honest, I'd never even noticed that the files in there might be odexed. I never modify them and I've never seen any mods for them.

I can make TMA process that folder if it's needed. This tool is for you guys, after all. But is it actually needed?
[Android Themes] nguyentankiet:
Hi Tickle. You will update tool for deodex Nougat base?
[Android Themes] tdunham:
Ok, lets have a realistic conversation on the use and purpose of de-odexing a rom... (Written from a touchwiz perspective by the way, its what I know :) )

Odex is more efficient. The system reads the files more efficiently, read time is faster and so on.

However, since we do not have source, we cannot properly modify the 'java' content of the system files so we rely on tools like apktool to convert the java code to a useable format.

But there is no need to deodex an entire rom or every single apk that resides there (take a look at your data/app folder sometime, the playstore has been installing updated apps for some time now with a 'hybrid' combination of odexed files). In fact, the only necessities are framework and the VERY few files that you want to modify to enhance your android experience. We've gotten used to doing the entire thing because that is what the tools do but in reality, even a heavily modified android custom build can still be left with 95% of the rom odexed, it would make the android system run faster and more efficiently.

I'm not saying to do things that way, I'm just pointing out that just because something is possible doesn't mean you have to do it that way.

Just my two cents :D
[Android Themes] jimbomodder:
Ok so I actually moved the entire folder to c-drive ( it was in c drive but about 4 sub folders to in) and it's working however I get unable to decompile, it's probably something I've missed but would it be the apk decompiler or Java that's most likely the cause. Thanks in advance
[Android Themes] KingRaheel:
No issues with tool. Have u installed framework-res.apk before decompiling the apk? If u use samsung then u will need to install twframework-res.apk as well. Works like a charm for me as usual. I use jdk 8u11
[Android Themes] MaFiBoSS:
Hi, sorry for delay.

Ok, I modified the file "SystemUI.apk" with both versions v14.1.0 (it works) and v14.2.0 (don't work).

MOD: I just changed the value to "0" in the path: "SystemUI.apk\res\values\dimens.xml".

<dimen name="finder_connect_layout_height">57.0dip</dimen>"
[Android Themes] Ticklefish:
Yes..once there are tools available that can deodex Nougat without any problems.

Why not try using the Marshmallow option and seeing what happens? Nougat isn't constructed that differently and TMA uses the most recent baksmali and smali.

We certainly don't need to deodex everything, that's true. Personally I only mod the smali in two or three files.

There are a few reasons why TMA deodexes everything in framework, app and priv-app..

If you want to deodex one of the 'core' JAR files like framework.jar or similar, and you're running Lollipop or higher, you have to deodex all the other core files as well. Which could then confuse the tool the next time you want to deodex..and blah-blah-blah (I could go into more depth but it'd probably get quite boring..)

Also some OEM's, Sony in particular, have created roms that have to be deodexed in full or the process won't work at all.

Combine that with the fact that I'm trying to make TMA accessible to all, no matter the experience and knowledge level, and that's why the tool processes everything.

I'm forever working on TMA's code and the deodex menu can always change as needed. That's why I was wondering about those vendor apps.

I'll consider adding an option to deodex individual files but it won't be added anytime soon.

Thanks for sharing your files. I'll have a play with them and see if I can spot anything that's causing this issue.

If I can't, I'll contact apktool's developer and let them know. :good:

What version of Android are you running, by the way?
[Android Themes] MaFiBoSS:
You do not need to thanks and good luck to find the problem ;)

The version of Android is 6.0.1 (stock rom).

Note: The framework file It is also ORIGINAL..
[Android Themes] Klaus N.:
[MENTION=4315551]Ticklefish[/MENTION] [MENTION=1042140]tdunham[/MENTION]

Thanks for your replies, I appreciate it!

My question was not be meant to ask for eta; I was only asking :)

And about odex - deodex: There are different meanings what lets android run faster/smoother. The first boot after installing or after wipe cache & wipe dalvik/art an odexed system boots by far faster, but once the cache is loaded, there's nearly zero difference in rebooting time.

Btw., I run this tool yesterday, and it stucked at deodexing the facebook app ("source file name too long"). Nevermind - I don't use that app, I use swipe pro!
[Android Themes] tdunham:
Agreed. I don't think it is really necessary to go as far as adding the ability to deodex individual files. My perspective is from a Touchwiz viewpoint, I suppose you will want to include any other app folders that apply going forward where applicable.

Right on. Yes, with the newer phones the speed difference once cache is built for dex/art is not very noticeable so we see little differences between the two. There are still a few devs that prefer to do it the way I suggested but it is extra work and not really necessary.
[Android Themes] nguyentankiet:
I tried with S7 Nougat rom, but framework.jar error always
[Android Themes] tdunham:
Have you already posted your log for TF to review?

I think he already spoke on Nougat issues may take some time to resolve.

Sometimes you must use a combination of tools to accomplish full deodex when a new operating system comes along too.

I'm not advertising them here but there a some rom Kitchen threads you should try for other results. There are two, one for Ubuntu and one for Windows that are worth a look. The links are in my guide thread/tools category.
[Android Themes] nguyentankiet:
This is framework.jar and my log
[Android Themes] Klaus N.:
[MENTION=4315551]Ticklefish[/MENTION]

I only want to let you know, that I've read in another thread, that at least since the Xperia Z5, there are no more .sqsh files in /system.
[Android Themes] Ticklefish:
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..:confused:

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

I've clustered these quotes together so I can reply to all in one go.

TMA can't currently deodex Nougat. As soon as baksmali and smali are updated to work with it, I'll update the code and we'll be good to go.

However I am concerned how the v2 signature will be affected by the deodex process. In theory the signatures would be rendered invalid on every deodexed APK and JAR file..

I'm still experimenting with a method to make new v2 signatures and that should hopefully sort that out.

I'm also considering rewriting the deodex process again to make it simpler for people. Since it now seems that Sony have given up using SQSH files that option on the menu is just going to cause confusion for a start.

I think I can use the information in build.prop to make the deodex process more automated so that TMA will work out what it needs to do and save you the bother.

As always this is going to involve a lot of typing and a lot of checking which will have to fit in around my work and personal life so don't expect a quick turnaround. This may be something for v14.4.

It's typical really. Every time I think I've got this tool exactly the way I like it it's only a few days before I start to wonder if I need to revisit the code again. I wonder if I'll ever be finished....lol
[Android Themes] ahmed_ais:
I'm having a problem trying to recompile framework-res.apk from Samsung S6 using v14.2 and apktool v2.2.1. I have attached the log maybe I could get some help. Thanks in advance.
[Android Themes] tdunham:
The path is too long is the error, I'm not sure why.

Have you tried with a different version of apktool, full java jdk installed and in the environment path for windows and also did you install necessary framework files too before attempting? Also, simple decompile and recompile without any changes correct?

I haven't tried latest version of this. Reading from the history txt, is the path for the work areas supposed to be with underscores now like this does anyone know?

C:\TickleMyAndroid\_WorkArea1\_working\framework-res.apk\AndroidManifest.xml
[Android Themes] Ticklefish:
The work areas have had underscores at the beginning of their names for ages. Since they were introduced, I think. I used underscores so they would appear first if you were viewing in alphabetical order.
[Android Themes] ahmed_ais:
The recompile (of same apk without change) was successful using apktool v2.0.3 but not with any recent version. However, the apk resulted from using v2.0.3 is not fine as it show black borders for any translucent area (after flashing and booing up). Having 2.0.3 works conclude that my setup is OK though. Thanks for your help.

Update:

I turns out that it is apktool bug that was already reported for v2.1.1 and is still open. It also does not exist when using Unix as hinted by iBotPeaches:

I tried to recompile the apk using apktool v2.2.1 on Mac OS and the process went fine. Until the bug is fixed, this will affect Windows users and of course the tools that run on Windows like TMA and Advanced Apktool.
[Android Themes] ZawZaw:
May be support Android Nougat 7.0 and up?

Please.
[Android Themes] tdunham:
This was already answered.
[Android Themes] Ticklefish:
Oh, I remember this bug. Unfortunately this is due to the way that Windows works so it's going to be tricky to fix.

Hopefully apktool's dev will be able to work out a solution before too long.
[Android Themes] ZawZaw:
OK Sir, so sorry for my question

Thanks you very much.
[Android Themes] nujackk:
Hi trying to use your tool to add 3minit.

everytime i try to recompile izarcc crashes

I'm on windows 8.1, have latest Java SE 8-112 installed

I install both if the framework-res files. prior to decompiling the only systemui file i find

attached one of the many logs. :crying:

Any guidance would be greatly appreciated.

Thank you
[Android Themes] Haze39:
Hello everyone

Who can tell me how to do or find the guide to remove "battery notification charged"

On Note 4 MM

thank you
[MENTION=4315551]Ticklefish[/MENTION] a big thank you for your program and help
[Android Themes] Thebear j koss:
Look in [MENTION=1042140]tdunham[/MENTION] 's profile for his touchwiz mod thread.

All common sense is gone. All that is left is stupidity.
[Android Themes] Haze39:
Hello
[MENTION=4315551]Ticklefish[/MENTION]

On a Galaxy Note 4 N910F Android M 6.0.1 (DPK1)

TMA has well pulled my folders (app, priv-app, framework) and the zip is recompiled in c: \ temp but before flasher I checked the deodex of the files but it did not work too much the three Quarter was still odexer

I used apktool 2.2.1 and method (4) deodexe android 6.0 ....

If you know why

Thanks for your feedback:confused:
[Android Themes] Ticklefish:
Can you share your files please? I'll try them on my setup and see if I can find out what's going on.

Is there a chance you can share your files as well? Deodexing is a tricky process and it's always possible Samsung have introduced something new I need to take into consideration.
[Android Themes] nujackk:
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