Importing .den Files

Learn how to import .den files when creating new profiles to use predefined spoofed values.

What are .den Files?

.den files are configuration files created by the Device Emulator and Device Emulator Pro apps that contain predefined spoofed values for Android device identifiers. Geergit supports importing these external app configuration files directly when creating new profiles, allowing you to reuse device configurations from Device Emulator without manual re-entry.

This is useful when you want to:

  • Import device configurations from Device Emulator or Device Emulator Pro
  • Reuse existing device emulator configurations within Geergit profiles
  • Transfer specific device identifier setups between different apps
  • Create profiles with predetermined values from trusted sources that must remain consistent

How Values Are Handled When Importing .den Files

When importing a .den file from Device Emulator or Device Emulator Pro during profile creation, Geergit processes the values in a specific way:

Values Present in .den File

When you import a .den file during profile creation, all values explicitly defined in the file are used as-is:

  • No randomization applied — The exact values from the Device Emulator .den file are preserved
  • Exact reproduction — If the .den file contains specific IMEI, Android ID, or MAC address values, those exact values will be used
  • Consistency maintained — The spoofed values remain identical to the source Device Emulator configuration

Values Not Present in .den File

For any identity fields that are not included in the .den file:

  • Automatic randomization — Missing values are automatically generated and randomized
  • Realistic fallback — Geergit creates random but valid values for all empty fields
  • Complete profile — The resulting profile contains both imported values and randomly generated values, forming a complete identity

Steps to Create a Profile with .den File Import

1. Open Geergit App

Start by opening the Geergit app on your device.

2. Select Your Target (App or Group)

Choose whether you want to create a profile for:

  • Individual app — Select a specific app from your installed apps list
  • Group — Select a group to apply the profile to multiple apps

3. Navigate to Identity Section

The Identity section opens automatically after selecting your target.

4. (Optional) Review Current Values

You can review the current spoofed values before proceeding. This is helpful if you want to compare them with your .den file values.

5. Tap Get New Profile

Tap the Get New Profile button at the bottom of the Identity section to begin creating a new profile.

6. Enter Profile Details

A profile creation dialog appears where you need to:

  • Profile Name — Enter a descriptive name (minimum 3 characters required so it appears in search)
  • Folder — Choose or create a folder for organization

7. Upload .den File

This is the key step for importing values:

  • Look for the Upload button next to the "Create New Profile" headline
  • Click the Upload button to open the file browser
  • Navigate to and select your .den file
  • The file will be processed and its values will be loaded

8. Tap Create

Once you're satisfied with the profile details:

  • Tap Create to finalize the profile
  • Geergit processes the values and creates your new profile
  • Your previous profile is automatically backed up to cloud storage

9. Confirm Profile Creation

Verify that the new profile appears in the Identity tab to confirm it was saved successfully.

What Happens During .den File Import

Processing Flow

  1. File validation — Geergit validates the .den file format and reads all contained values
  2. Explicit values preserved — Any values explicitly defined in the .den file are extracted and marked for use
  3. Gap filling — Geergit identifies which identity fields have no values in the .den file
  4. Value generation — For each missing field, realistic randomized values are generated
  5. Profile creation — The profile is created with imported + generated values
  6. Cloud backup — Your previous profile is backed up, and the new profile is synced to your cloud library

Result

Your new profile contains:

  • Exact values from the .den file (no randomization)
  • Generated values for any fields not in the .den file (realistic and randomized)
  • Complete identity that can be immediately applied to apps or groups

Practical Examples

Example 1: Complete Device Configuration

You have a .den file with a complete device configuration including all Android IDs, MAC addresses, and IMEI numbers.

Result when imported:

  • All specified values from the .den file are used exactly as-is
  • No fields are missing, so minimal randomization occurs
  • The profile is an exact replica of your saved device configuration

Example 2: Partial Configuration

You have a .den file with only core identifiers (Android ID, IMEI, MAC address) but no SIM information or hardware serial numbers.

Result when imported:

  • Android ID, IMEI, and MAC address use the exact values from your .den file
  • SIM details and other missing fields are automatically randomized
  • The profile has your specific core values plus realistic filler data

Example 3: Sharing Device Emulator Configurations

You have a Device Emulator configuration saved as a .den file that you want to use as a Geergit profile.

What happens:

  • All device identifiers from the Device Emulator .den file are imported into your Geergit profile
  • The exact values from Device Emulator are preserved in your new profile
  • Any missing fields are automatically randomized
  • You now have a Geergit profile matching your Device Emulator configuration

Manual Editing After Import

After creating a profile with imported .den values, you can still manually edit individual identity fields:

  1. The new profile is now active in the Identity section
  2. Tap any identity field to modify it
  3. Changes are automatically backed up to the cloud when you leave the Identity section
  4. Your customizations override the imported .den values

This allows you to use .den files as a starting point and then fine-tune specific values as needed.

Key Differences: .den Import vs. Manual Creation

AspectWith .den ImportWithout .den File
SourceDevice Emulator/Pro configurationGeergit generates new values
Core valuesExact from Device Emulator fileFully randomized
Missing fieldsAuto-randomizedAll fields randomized
ConsistencyPreserved from external configAll values random each time
Use caseReusing Device Emulator configurationsFresh random identity
CustomizationStart with Device Emulator values, edit from thereStart from scratch

Troubleshooting

.den File Upload Not Working

  • Verify file format — Ensure the file has a .den extension
  • Check file integrity — The file may be corrupted; try exporting a new .den file
  • File permissions — Ensure the app has permission to read files from your device storage
  • File location — Try moving the .den file to a more accessible location (like Downloads folder)

Some Values Not Imported

  • Check file contents — The .den file may not contain all identity fields; missing ones will be randomized
  • Review preview — Check the preview step to see which fields were imported vs. generated
  • Re-export if needed — If values are missing, re-export the profile from your profile library

Profile Looks Different Than Expected

  • Randomized fields — Remember that fields not in the .den file are automatically randomized
  • Compare carefully — Review which fields came from the .den file vs. which were generated
  • Manual adjustment — Edit specific fields after creation if they don't match your requirements