Geergit

Manage Identity

A comprehensive guide to manually editing and customizing individual identity fields in Geergit.

Overview

While Geergit's Generate feature creates randomized identities instantly, the Manage Identity workflow lets you manually customize each field. This guide serves as the comprehensive field reference for all available identity fields, their formats, edit options, and randomization behaviors.

Prerequisites

  • Geergit app installed on your Android device
  • An app selected inside Geergit
  • Root access (required to apply custom identities to the target app)
  • An active internet connection for cloud sync (optional but recommended)

How to Edit a Field

General Steps

  1. Open Geergit and tap your target app
  2. Locate the identity field you want to edit
  3. Tap on the field value
  4. An edit dialog appears
  5. Clear the existing value (if desired) and type your new value
  6. Tap Done
  7. Your changes automatically sync to your profile (requires internet connection)

For Dropdown/Selection Fields (e.g., SIM Operator)

  1. Tap the field to open a selection list
  2. Choose from available options
  3. The field updates automatically

For Device Selection

  1. Tap the Change button in Device Information section
  2. Browse pre-built device models or search for a specific device and select it
  3. Tap a device card to see device-related fields (Manufacturer, Model, Bootloader, etc.) detail view
  4. Optionally fix the device model to prevent device model and brand changes during randomization

Complete Identity Fields Reference

Basic Identifiers

Android ID

  • Purpose — Unique device identifier checked by most apps
  • Edit Type — Hexadecimal text input field
  • Format — Example: 9e5f8c1a2b3d4e5f
  • Randomize Behavior — Generates new unique identifier
  • Notes — Commonly used by anti-fraud systems; changing it can help evade detection

IMEI (International Mobile Equipment Identity)

  • Purpose — Device's hardware identifier
  • Edit Type — Numeric text input
  • Format — 15-digit number (Example: 352015234567890)
  • Dual IMEI Support — Checkboxes for IMEI 1, IMEI 2, or both
  • Randomize Behavior — Two modes:
    • Full Randomize — Generate completely new IMEI values
    • Increment — Increase by 1, 2, or custom number (useful for sequential testing)
  • Notes — Commonly checked by apps; dual IMEI useful for dual-SIM devices

Network & Advertising Identifiers

Advertising ID

  • Purpose — Google's advertising identifier for ad targeting
  • Edit Type — UUID format text input
  • Format — Example: 12345678-1234-1234-1234-123456789012
  • Randomize Behavior — Generates new UUID
  • Notes — Spoofing disables personalized ad targeting; useful for testing ad behavior

Wi-Fi MAC

  • Purpose — Device's Wi-Fi hardware address
  • Edit Type — MAC address format text input
  • Format — Colon-separated hex: 00:1A:7D:DA:71:13
  • Randomize Behavior — Generates valid MAC address format
  • Notes — Used for network identification; must be valid format

Wi-Fi SSID

  • Purpose — Wi-Fi network name the app perceives
  • Edit Type — Free text string
  • Format — Any string (Example: MyWiFiNetwork)
  • Randomize Behavior — Generates random string
  • Notes — Not typically critical for most apps

Wi-Fi BSSID

  • Purpose — Basic Service Set ID; MAC address of Wi-Fi access point
  • Edit Type — MAC address format text input
  • Format — Colon-separated hex: 00:1A:7D:DA:71:13
  • Randomize Behavior — Generates valid MAC address format
  • Notes — Related to Wi-Fi router identification

Bluetooth MAC

  • Purpose — Device's Bluetooth hardware address
  • Edit Type — MAC address format text input
  • Format — Colon-separated hex: 00:1A:7D:DA:71:13
  • Randomize Behavior — Generates valid MAC address format
  • Notes — Used for Bluetooth device identification

Telephony Identifiers

Phone Number

  • Purpose — Device's phone number
  • Edit Type — Phone number text input
  • Format — Any phone number format (Example: +1-555-0123)
  • Randomize Behavior — Generates random phone number
  • Notes — Optional field; some apps check for this

SIM Card Serial

  • Purpose — Unique SIM card identifier
  • Edit Type — Alphanumeric text input
  • Format — Typically a long string (Example: 8901260123456789012)
  • Randomize Behavior — Generates new serial number
  • Notes — Used for carrier identification

SIM Subscriber ID

  • Purpose — Mobile Subscriber Identity (IMSI) identifier
  • Edit Type — Numeric text input
  • Format — 15-digit number (MCC + MNC + MSIN)
  • Randomize Behavior — Generates new subscriber ID
  • Notes — Combined with country/carrier information

SIM Operator

  • Purpose — Telecom provider name
  • Edit Type — Dropdown selection from available operators
  • Country Selection — Select a country to view operators available in that region
    1. Tap the country selector
    2. Choose a country from the available list
    3. The operator list automatically updates to show only operators mapped to the selected country (Example: selecting India shows only Indian operators)
    4. Select your desired operator from the filtered list
  • Lock Country for Randomization — Option to lock a specific country during randomization
    • When enabled, clicking randomize will only shuffle operators within that locked country
    • When disabled, clicking randomize will change both country and operator
  • Auto-Mapping — When you select an operator, the MCC/MNC (Mobile Country Code/Mobile Network Code) values are automatically mapped based on that operator's network configuration
  • Notes — Affects telecom-specific app behavior; country selection determines which operators are available, and locking country ensures operators only shuffle within that region during randomization

Hardware & System Identifiers

Hardware Serial

  • Purpose — Device's hardware serial number
  • Edit Type — Alphanumeric text input
  • Format — Example: FA73K1A03072
  • Randomize Behavior — Generates new hardware serial
  • Notes — Printed on device back; used for device tracking

GSF ID (Google Services Framework ID)

  • Purpose — Unique identifier for Google Play Services
  • Edit Type — Numeric text input
  • Format — Long numeric string (Example: 1234567890123456789)
  • Randomize Behavior — Generates new GSF ID
  • Notes — Required for Google Play Services; critical for app functionality

DRM/Media DRM

  • Purpose — Digital Rights Management identifier
  • Edit Type — Text input field
  • Randomize Behavior — Generates new DRM identifier
  • Notes — Used for protected content verification

Gmail & Account Privacy

Gmail ID

  • Purpose — Spoofs logged-in Gmail accounts
  • Edit Type — Email address or identifier text input
  • Randomize Behavior — Generates random Gmail identifier
  • Effect — Hides actual Gmail account IDs from apps that attempt to read logged-in accounts
  • Notes — Critical for privacy; prevents account tracking by apps like measurement services

Device Grouping & Model Information

Device Selection (Pre-built Models)

  • Purpose — Choose from real Android device models
  • Access — Tap Change button in Device Information section
  • Search Function — Find specific devices by name
  • Fixed Device Model — Toggle to lock device model to prevent changes during randomization
  • Random Button — Randomizes device (respects fixed setting)
  • Auto-populate — Selecting a device automatically fills related fields:
    • Manufacturer
    • Model
    • Product
    • Device Code Name
    • Bootloader
    • Build ID
    • Fingerprint

Manufacturer

  • Purpose — Device brand/manufacturer name
  • Edit Type — Text input field
  • Format — Examples: Google, Samsung, OnePlus, Motorola
  • Auto-populate — Updates when device model selected
  • Randomize Behavior — Updates based on selected device model
  • Notes — Device brand name reported to apps

Model

  • Purpose — Device model name
  • Edit Type — Text input field
  • Format — Examples: Pixel 6 Pro, Galaxy S21, OnePlus 9 Pro
  • Fix Option — Lock model to prevent changes on randomization
  • Auto-populate — Depends on device selection
  • Randomize Behavior — Changes to different model (unless fixed)
  • Notes — User-friendly device name

Product

  • Purpose — Product identifier used by Android internally
  • Edit Type — Text input field
  • Format — Typically model-specific code (Example: oriole)
  • Auto-populate — Updates with device model selection
  • Notes — System-level identifier

Device Code Name

  • Purpose — Internal Google code name for device
  • Edit Type — Text input field
  • Format — Examples: raven (Pixel 6 Pro), bluejay (Pixel 6a)
  • Auto-populate — Sets based on device model
  • Notes — Used internally by Google

Bootloader

  • Purpose — Bootloader version
  • Edit Type — Text input field
  • Format — Version string (Example: raviole-1.0-6433057)
  • Auto-populate — Sets based on device model
  • Randomize Behavior — Updates version number
  • Notes — Related to device security and initialization

Build ID

  • Purpose — Device build identifier
  • Edit Type — Text input field
  • Format — Combination of model and build code (Example: TP1A.220624.014)
  • Auto-populate — Updates with device model
  • Randomize Behavior — Generates new build ID
  • Notes — Identifies specific software build

Incremental

  • Purpose — Build increment number
  • Edit Type — Text input field
  • Format — Numeric (Example: 6433057)
  • Randomize Behavior — Updates increment number
  • Notes — Differentiates between minor software revisions

Device Host

  • Purpose — Build host machine identifier
  • Edit Type — Text input field
  • Randomize Behavior — Updates host identifier
  • Notes — Internal build system identifier

Device User

  • Purpose — Build user identifier
  • Edit Type — Text input field
  • Randomize Behavior — Updates user identifier
  • Notes — User who built the ROM

Fingerprint

  • Purpose — Complete device signature
  • Edit Type — Text input field
  • Format — manufacturer/model/device:android_version/build_id/incremental:build_type/tags
  • Example — google/oriole/oriole:12/TP1A.220624.014/6433057:user/release-keys
  • Auto-calculate — Generates from other device fields
  • Notes — Often checked by apps; defines complete device identity
  • Important — Changes to other device fields automatically update fingerprint

Android Version

  • Purpose — Android OS version
  • Edit Type — Read-only field (cannot be edited)
  • Format — Version number (Examples: 12, 13, 14, 15)
  • Fixed Behavior — Android version is fixed based on the host device's Android version and cannot be changed or spoofed
  • Notes — The OS version is determined by your device's actual OS and cannot be customized; it affects feature availability and app compatibility checks

Advanced Editing Scenarios

Scenario 1: Location-Specific Spoofing

  1. Select SIM Operator and enable Lock Country
  2. Choose your target country
  3. MCC/MNC automatically maps to that country
  4. Optionally update Advertising ID for location consistency
  5. Tap Generate to randomize remaining fields

Scenario 2: Simulating Specific Device

  1. Use Device Selection to choose a device (e.g., Google Pixel 6 Pro)
  2. Enable Fix Device Model to lock it
  3. Manually customize other fields if needed (Bootloader, Build ID, Android Version)
  4. Review Fingerprint for consistency
  5. All related device information auto-populates

Scenario 3: Incremental IMEI Testing

  1. Edit IMEI field
  2. Select IMEI 1, 2, or both
  3. Choose Increment Mode and set increment value (1, 2, or custom)
  4. Each generation increases IMEI by set value (useful for batch testing)

Device Model Fixed vs. Randomize Behavior

When Device Model is NOT Fixed:

  • Device selection changes during randomization
  • All related fields update
  • Useful for testing with diverse device configurations

When Device Model IS Fixed:

  • Device model stays consistent across generations
  • Other fields (Bootloader, Build ID, Android Version) randomize
  • Network and advertising identifiers randomize independently
  • Useful for testing with specific device signature while varying other parameters

Automatic Consistency

When you use device selection or change certain fields, Geergit automatically maintains consistency:

  • Selecting a device auto-populates Manufacturer, Model, Product, Code Name
  • Fingerprint automatically recalculates based on device information
  • MCC/MNC automatically maps to selected SIM Operator
  • Build-related fields (Bootloader, Build ID) auto-update with device selection

Best Practices

  • Validate formats — Ensure each field follows correct format (e.g., IMEI is 15 digits, MAC addresses use colons)
  • Maintain consistency — Keep Android ID and IMEI realistic and aligned with simulated device
  • Use device selection — Leverage pre-built devices to auto-populate realistic values
  • Document profiles — Use clear names when saving for easy identification
  • Test incrementally — Edit a few fields, test app behavior, then iterate
  • Stay online — Keep connected while editing for reliable sync
  • Review fingerprint — Ensure device fingerprint matches other device fields
  • Leverage fixed device — Use fixed device model when you want consistent signature across tests

Next Steps

Generate Identity

A step-by-step guide on how to generate and refresh device identities in Geergit, including two methods to randomize identities and backup app data.