Skip to content

Troubleshooting

official-Arvind edited this page Jun 19, 2026 · 2 revisions

๐Ÿ“‹ FAQ & Troubleshooting

Find quick solutions to the most common configuration and execution issues.


๐Ÿ”Œ Connection & ADB Issues

โš ๏ธ "No device found" / "Enable USB Debugging"

  1. Verify the USB cable is connected securely to both the PC and phone.
  2. Make sure you are using a port on your PC that supports data transfer (avoid power-only charge ports).
  3. If the prompt "Allow USB Debugging" doesn't appear on your phone, run Option 6 in the launcher to restart the ADB server.
  4. Try switching your phone's USB connection mode from Charging to File Transfer / MTP.

๐Ÿ’พ Virtual Drive Cleanup

โš ๏ธ The virtual "Z:" (or other) drive is still visible in Windows Explorer

  • Why it happens: This occurs if the PowerShell terminal was abruptly closed or crashed before it could run the unmount routine.
  • Automatic Fix: Run Jigar_Tools_Setup.bat again. At startup, the launcher automatically runs a mapping scan and unmounts any orphaned drives pointing to your backup directory.
  • Manual Fix: Open cmd/PowerShell on Windows and type:
    subst Z: /D
    (Replace Z: with whichever letter was left mapped).

๐Ÿ”Œ Performance & Speed

โš ๏ธ Backup speeds are lower than expected

  • USB Port: Plug your device into a USB 3.0 port (typically colored blue or labeled with SS).
  • USB Cable: Budgets/older charging cables often only support USB 2.0 speeds (max ~35MB/s). Use the original high-quality cable that came with your phone.
  • Device Controller: Budget Android devices are often hardware-limited to USB 2.0 speeds regardless of your PC port or cable.

๐Ÿ–ผ๏ธ Media Re-Indexing

โš ๏ธ Restored photos and videos are not appearing in Gallery

  • Explanation: Jigar Tools writes files directly to your device storage partition. The Android MediaStore database does not index directories instantly.
  • Auto-Trigger: Jigar Tools triggers a media scan volume call after restore. If files still don't appear, give the phone 1-2 minutes to finish indexing or reboot your device to force a refresh.