Zip compression, file permissions, some issues with shizuku

[thomasmolover]

Some problems in use
1. The algorithm of zip compression package is outdated. Some compression packages cannot add/delete files and can only be unzipped and repackaged;
2. There are problems with the newly created files in the system directory, such as the .rw path created after using ksu root (with 777 permissions), which cannot be used and will cause a crash, while the path created by the mt file manager is not a problem;
3. The files in the zip package cannot be directly unzipped to special paths such as the root directory, such as /data/adb;
4. Batch renaming is not possible in these special paths, but individual renaming is possible;
5. When the new version requests shizuku, it checks the existence of the application instead of the function, which makes the SUI module (Zygisk implements shizuku) unusable.

[ghisler(Author)]

1. Example please
2. Sorry, I do not understand your report. What are you trying to do which causes a crash?
3. Unfortunately this isn't supported because Total Commander cannot access these folders directly, it has to send commands on a (hidden) root shell, or for Shizuku, in a separate elevated module. I can't call unpack functions from there
4. Sorry, currently not supported (too complex to implement).
5. How can I check for existence of SUI module? I don't have any way to test it myself.

[thomasmolover]

this is the SUI Magisk mod with systemless shizuku, u can flash it to root phone, when some app what use shizuku open, it will pop a tip to confirm. but tc not.
https://drive.google.com/file/d/1-2JRlqR6LETWiqz-hmhF72BQeyDaSa7G/view?usp=drivesdk

this is a zip file that tc could copy files from it but not delele or add.
https://drive.google.com/file/d/1-7l6L823M4cXX5yjLdrx1XCwNe0ZAXNa/view?usp=drivesdk

[ghisler(Author)]

1. I have analyzed the ZIP file: Total Commander for Android doesn't modify it because the files are stored in it out of order.
The file "META-INF/com/google/android/updater-script" comes at position 5 in the central directory, and the data starts at offset 20391859.
The file "customize.sh" comes immediately behind it, but the data starts at offset 27041, in front of the data of the previous file.
There is a risk of damaging the archive when modifying it, so TC refuses to change it.

2. You haven't answered that yet, can you give me more details, please?

5. As I said, I don't currently have any rooted device which can run this.

[thomasmolover]

On the TC settings page, if you want to check the shizuku->Android/data option, you must have the shizuku app installed, otherwise a pop-up notification will appear indicating that the app is not installed. However, the SUI module can actually replace shizuku. Other apps that use shizuku functions do not use the app list to detect shizuku, but may call the shizuku function to have shizuku itself pop up a confirmation box (similar to the confirmation box that pops up when Android calls other apps).

[img]https://i.postimg.cc/ykbwN1Mv/Screenshot-2025-04-14-08-34-33-06-9e8df3d0c7c1f50248b6ee043a653d26.jpg[/img]

[img]https://i.postimg.cc/gxL1L9dd/Screenshot-2025-04-14-08-35-28-76-e66e28f718147b6e7216efe19a1092f5.jpg[/img]

[ghisler(Author)]

I don't want to do this because it doesn't give the user the opportunity to install Shizuku. Also such a call will fail if Shizuku is installed but not enabled. I need to distinguish these two cases.

To check whether Shizuku is installed, I call getPackageManager().getApplicationInfo("moe.shizuku.privileged.api");
I don't know what function to call to check whether SUI is installed, sorry.