-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
official-Arvind edited this page Jun 19, 2026
·
2 revisions
Find quick solutions to the most common configuration and execution issues.
- Verify the USB cable is connected securely to both the PC and phone.
- Make sure you are using a port on your PC that supports data transfer (avoid power-only charge ports).
- If the prompt "Allow USB Debugging" doesn't appear on your phone, run Option 6 in the launcher to restart the ADB server.
- Try switching your phone's USB connection mode from Charging to File Transfer / MTP.
- 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.batagain. 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:
(Replace
subst Z: /DZ:with whichever letter was left mapped).
- 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.
- 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.