mikrom dir

In order to facilitate unified management, in mikrom2.0, all implemented functions and file interactions are stored in the directory /data/mikrom. This is a directory configuration that imitates /sdcard and provides a convenient application landing file. Table of contents. Check out the structure in this directory below

adb shell
cd /data/mikrom
ls -all 

# The display results are as follows
drwxrwxrwx  6 shell   shell     3488 2024-02-22 21:55:15.866073420 +0800 .
drwxrwx--x 52 system  system    4096 2024-03-03 20:16:28.189667699 +0800 ..
-rwxrwxrwx  1 root    root    304653 2024-03-05 19:28:09.801062907 +0800 breakClass.txt
drwxrwxrwx  2 shell   shell     3488 2024-02-18 18:55:37.044666688 +0800 cacerts
-rwxrwxrwx  1 root    root       792 2024-03-05 19:41:22.454475203 +0800 config.json
drwxrwxrwx  4 shell   shell     3488 2024-02-26 23:55:48.539722026 +0800 dump
drwxrwxrwx  2 shell   shell     3488 2024-02-18 18:55:37.044666688 +0800 dumpSo
drwxrwxrwx  2 shell   shell     3488 2024-03-05 00:00:00.774921860 +0800 logs
-rw-rw-rw-  1 u0_a267 u0_a267      0 2024-03-05 19:41:22.454475203 +0800 packages

The above files and directories are introduced below.

breakClass.txt

The breakClass.txt file is a global blacklist class file. During the execution of all unpacking functions, the classes in this file will be skipped. The source of this class list is all classes obtained in an empty project. In this way, the purpose of improving shelling efficiency is achieved. You can also add a new global blacklist class to this file yourself. This file may be configured in the miktool adding interface later.

cacerts

The cacerts directory is an extended system certificate directory. Since the system directory is read-only and the system certificate cannot be written without root, a system certificate directory is expanded here to facilitate quick packet capture in versions without root.

config.json

Configuration related to task execution. After configuring the target application, it will be written to this file.

dump

The location of the dex unpacking result. Different applications will create corresponding folders to store their unpacking results.

dumpSo

The location of the so repair result is the same as the above result. The corresponding folder storage is created based on the application package name.

logs

The implementation files of task execution related logs can also be viewed through logcat. If logcat is abnormal, you can view the logs in this directory

packages

The list of target applications that need to be processed has not been processed yet.