​​​​​​​https://github.com/loerting/dalvikus

MT Manager is a sophisticated Android application that functions as both a high-performance file manager and a powerful APK editor. Developed by Lin Jin Bin, it is widely recognized among developers and advanced Android users for its robust feature set, including the ability to decompile, modify, recompile, and sign APK files directly on a mobile device—eliminating the need for a PC.

In addition to APK editing, MT Manager offers a full suite of file management tools:

    Support for various archive formats such as ZIP, RAR, and TAR

    Built-in text and hex editors for direct file editing

    Cloud storage integration (e.g., Google Drive, Dropbox)

    Dual-pane interface for efficient file operations

    Optional root access, allowing deeper control of the Android file system

    Powerful search, batch operations, and permission editing

Dalvik opcodes represent the low-level instructions used by the Dalvik Virtual Machine (DVM), which was the runtime environment for Android applications prior to Android 5.0 (Lollipop). While modern Android uses the ART (Android Runtime), a significant number of legacy applications and malware samples were built for or executed within the Dalvik environment.
Why Dalvik Opcodes Still Matter

In professional reverse engineering and security research, understanding Dalvik opcodes remains relevant due to the following reasons:

    Legacy App Analysis: Many organizations still rely on legacy Android apps that haven’t been updated to ART. When analyzing these apps—especially in enterprise environments—it’s essential to interpret Dalvik bytecode accurately.

    Malware Research: A substantial portion of Android malware found in the wild, particularly older samples or those targeting devices running outdated OS versions, use Dalvik opcodes. Recognizing opcode patterns is crucial for behavioral analysis and detection.

    Static Analysis Tools: Tools like Baksmali, Apktool, and JADX disassemble APK files into Smali code, which is essentially a readable representation of Dalvik opcodes. Security analysts and reverse engineers use this output to understand app functionality without executing it.

    Forensic Investigations: In digital forensics, investigators may need to examine an APK’s behavior by analyzing the underlying Dalvik bytecode, especially in environments where dynamic analysis is impractical or restricted.

    Custom Emulator/Hooking Work: When building custom analysis tools or emulators for Android apps, a solid grasp of Dalvik instructions is necessary to emulate app behavior faithfully.

Typical Use Cases

    Decompiling APKs for vulnerability analysis.

    Tracing suspicious API calls and obfuscated control flow.

    Detecting hidden functionalities or backdoors.

    Reconstructing missing or obfuscated high-level code.

إقتباس : Features

• Mobile scan code connection: no need to manually configure WiFi proxy,
  
• including configuration synchronization. All terminals can scan codes to connect and forward traffic to each other.
  
• Domain name filtering: Only intercept the traffic you need,
  
• and do not intercept other traffic to avoid interference with other applications.
  
• Search: Search requests according to keywords,
  
• response types and other conditions
  
• Script: Support writing JavaScript scripts to process requests or responses.
  
• Request rewrite: Support redirection, support replacement of request or response message,
  
• and can also modify request or response according to the increase.
  
• Request blocking: Support blocking requests according to URL,
  
• and do not send requests to the server.
  
• History: Automatically save the captured traffic data for easy backtracking and viewing.
  
• Support HAR format export and import.
  
• Others: Favorites, toolbox, common encoding tools, as well as QR codes,
  
• regular expressions, etc.
  

<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
  <base-config cleartextTrafficPermitted="true">
    <trust-anchors>
      <certificates src="system" />
      <certificates src="user" />
    </trust-anchors>
  </base-config>
</network-security-config>

<?xml version="1.0" encoding="utf-8"?>
<manifest>
<application android:networkSecurityConfig="@xml/network_security_config">
...
</application>
</manifest>

wx C0820091C0035FD6

• Official Book: Read about r2 usage
  

• asm/* libapp assemblies with symbols
  
• blutter_frida.js the frida script template for the target application
  
• objs.txt complete (nested) dump of Object from Object Pool
  
• pp.txt all Dart objects in Object Pool