Quick Start Guide ================= This guide will help you get up and running with Sandroid in minutes. Prerequisites ------------- Before starting, ensure you have: 1. **Sandroid installed** (see :doc:`installation`) 2. **Android emulator running** or physical device connected 3. **ADB working** - test with ``adb devices`` Basic Usage ----------- **1. Initialize Configuration**:: sandroid-config init **2. Start Your Android Emulator**:: # List available AVDs emulator -list-avds # Start an emulator emulator -avd Pixel_6_Pro_API_31 -no-snapshot # Verify connection adb devices **3. Run Sandroid (Interactive Mode)**:: sandroid You'll see the Sandroid interactive menu: .. code-block:: text ┌───────────────────────────────────────────────────────────────────────┐ │ Sandroid Interactive Menu │ ├───────────────────────────────────────────────────────────────────────┤ │Frida Server: [Not running] │ │HTTP Proxy: [Not set] │ │Spotlight Application: [Not set] │ │ │ │ === Action Recording & Playback === │ │ * [r]ecord an action │ │ * [p]lay the currently loaded action │ │ │ │ === Spotlight Application === │ │ * set [c]urrent app in focus as spotlight app │ │ * [a]nalyze spotlight app │ │ * [d]ump memory of spotlight app │ │ │ │ === Emulator Management === │ │ * [e]mulator information │ │ * [f]rida server installation/management │ │ * [s]creenshot of device │ │ │ │ * [q]uit │ └───────────────────────────────────────────────────────────────────────┘ First Analysis - Recording User Actions --------------------------------------- **1. Install Frida Server** (required for dynamic analysis):: # In interactive mode, press 'f' f **2. Record User Interactions**:: # In interactive mode, press 'r' r # This will: # - Take a baseline snapshot of the system # - Start monitoring file changes, processes, and network # - Wait for you to interact with the device **3. Perform Actions on Device** - Install an APK - Open apps, interact with them - Browse, use features - When done, press Enter in the Sandroid terminal **4. View Results** Sandroid will analyze the changes and show: - **New files** created during your actions - **Changed files** and their differences - **Network connections** made - **Processes** that ran - **Screenshots** taken during analysis Command-Line Analysis --------------------- For automated analysis without interaction:: # Basic analysis with 2 runs sandroid --number 2 # Network monitoring with screenshots every 5 seconds sandroid --network --screenshot 5 # Complete analysis with all features sandroid --network --sockets --screenshot 3 --hash --apk --report # AI-powered analysis with PDF report sandroid --ai --report --network Configuration Examples ---------------------- **Basic Configuration** Create ``~/.config/sandroid/sandroid.toml``:: log_level = "INFO" output_file = "analysis_results.json" [emulator] device_name = "Pixel_6_Pro_API_31" [analysis] number_of_runs = 2 monitor_processes = true **Security Analysis Configuration**:: log_level = "DEBUG" [analysis] number_of_runs = 3 monitor_network = true monitor_processes = true show_deleted_files = true [features] screenshot_interval = 5 enable_hash_calculation = true list_apks = true Common Workflows ---------------- **Malware Analysis Workflow** 1. **Setup**:: sandroid-config init # Edit config for malware analysis sandroid-config set analysis.monitor_network true sandroid-config set log_level DEBUG 2. **Start Analysis**:: sandroid --trigdroid com.suspicious.app --network --screenshot 3 3. **Install and Run Malware**:: # Use TrigDroid for automated trigger execution # Or manually install and interact with suspicious APK 4. **Generate Report**:: sandroid --report --ai **App Development Testing** 1. **Configure for Development**:: sandroid-config set analysis.number_of_runs 1 sandroid-config set paths.results_path ./test_results/ 2. **Test Your App**:: sandroid --number 1 --screenshot 2 3. **Monitor Specific App**:: # Set spotlight app in interactive mode # Press 'c' to set current foreground app as spotlight Understanding Results --------------------- **Output Files** - ``sandroid.json`` - Complete analysis results - ``results/`` - Raw data and screenshots - ``sandroid.pdf`` - Generated report (with --report) - ``sandroid.log`` - Detailed execution logs **Key Result Sections** - **Changed Files**: Files modified during analysis - **New Files**: Files created during analysis - **Network**: Connections and traffic captured - **Processes**: Applications and services that ran - **Static Analysis**: APK information and metadata **Example Results**:: { "Changed Files": [ {"/data/data/com.app/shared_prefs/settings.xml": [ "- old_value", "+ new_value" ]} ], "New Files": [ "/sdcard/Download/malware_payload.bin", "/data/data/com.app/files/config.json" ], "Network": { "connections": ["192.168.1.100:8080", "malicious-c2.com:443"], "dns_queries": ["api.legitimate-service.com", "tracking.ads.com"] } } Next Steps ---------- Now that you've completed your first analysis: 1. **Learn Interactive Mode**: :doc:`interactive_mode` 2. **Explore Command-Line Options**: :doc:`command_line_usage` 3. **Configure for Your Needs**: :doc:`configuration` 4. **Handle Issues**: :doc:`troubleshooting` 5. **Advanced Features**: :doc:`advanced/custom_analysis` Tips for Better Analysis ------------------------- **Performance Tips** - Use SSDs for faster file system monitoring - Close unnecessary applications during analysis - Use ``--avoid-strong-noise-filter`` for comprehensive analysis **Accuracy Tips** - Run multiple analysis iterations (``--number 3``) - Use clean snapshots as baselines - Allow sufficient time between actions for monitoring **Security Tips** - Use isolated emulators for malware analysis - Enable network monitoring for suspicious apps - Use AI analysis for automated threat detection **Troubleshooting Tips** - Check ADB connection: ``adb devices`` - Verify emulator is rooted for advanced features - Monitor logs: ``tail -f ~/.cache/sandroid/logs/sandroid.log``