Android Recovery "No such file or directory" Error During USB OTA Installation
Applies to: Elo Android Backpack & I-Series | Article Type: Technical Support FAQ
When attempting to install an OTA update on an Elo Android Backpack or I-Series device using a USB flash drive, Android Recovery may display a "No such file or directory" error and abort the installation.
This error usually means Android Recovery was unable to detect or mount the USB storage device. It does not necessarily indicate a problem with the OTA update file itself.
Symptoms
After selecting Apply update from U-Disk in Android Recovery, you may see errors similar to the following:
Failed to mount /usb: No such file or directoryFailed to mount /usb2: No such file or directoryCouldn't mount /usb or /usb2Installation aborted
Example Recovery Error
What Does "No Such File or Directory" Mean?
Android Recovery expects the USB storage device to be available at specific mount locations, such as /usb or /usb2.
If Recovery cannot detect or mount the USB flash drive at those locations, it reports "No such file or directory" and cannot access the OTA update package.
In this situation, the error is referring to the USB storage mount location, not necessarily to the OTA ZIP file itself.
Cause
This condition is typically caused by Android Recovery being unable to properly detect, recognize, or mount the USB flash drive.
Possible causes include:
- The USB flash drive was not detected by Android Recovery.
- The USB drive's filesystem format or partition layout is not recognized by the recovery environment.
- The USB drive is connected through a hub, adapter, or other connection method that prevents it from mounting correctly.
- The specific USB flash drive is not being recognized correctly by the recovery environment.
Resolution
If the OTA update fails from USB with a "No such file or directory" or USB mount error, use an SD card to install the OTA update instead:
- Copy the OTA update ZIP file to a supported SD card.
- Insert the SD card into the Elo Android Backpack SD slot.
- Boot the device into Android Recovery.
- Select Apply update from SD card.
- Select the OTA update ZIP file.
- Allow the update to complete.
- Select Reboot system now after the installation finishes.
Alternative Troubleshooting: Retrying the USB Drive
Before retrying the OTA update from a USB flash drive, perform the following troubleshooting steps:
- Remove and reinsert the USB flash drive.
- Connect the USB drive directly to the device without using a hub or adapter.
- Try a different, standard USB flash drive (FAT32 filesystem is highly recommended).
- Place the OTA ZIP file in the root directory of the USB drive.
- Verify that the USB drive uses a simple partition layout (e.g., MBR master boot record rather than GPT partition style).
Alternative Media: Try using SD Card
If verification errors persist across multiple USB drives, attempt the update using an alternative physical medium. Cleanly format a high-quality MicroSD card to FAT32, copy the update.zip to its root directory, and select the option to apply the update from the SD card in the recovery menu.
💾 1. Selecting the Right SD Card Size
- To ensure a seamless update process, we highly recommend using a Micro SD card with a capacity of 32GB or smaller.
- Cards ≤ 32GB: Can be formatted to FAT32 quickly and directly using the native Windows Formatting Tool.
- Cards > 32GB: Native Windows formatting tools do not support partitioning volumes larger than 32GB into FAT32 (Windows defaults larger cards to exFAT or NTFS, which are unsupported by the bootloader).
🔧 2. Formatting Instructions
- Option A: Using Standard Windows Tools (For SD cards 32GB or smaller)
- Insert the Micro SD card into your computer's card reader.
- Open File Explorer and navigate to This PC.
- Right-click on your SD card drive and select Format...
- Under File System, select FAT32 from the dropdown menu.
- Leave allocation unit size at default, check Quick Format, and click Start.
- Option B: Using Third-Party Utilities (Required for SD cards larger than 32GB)
- If you must use an SD card larger than 32GB, you will need to utilize a third-party utility to bypass native Windows volume limits and force a FAT32 format:
- Download and open a trusted formatting utility such as Rufus or the FAT32 Format GUI.
- Select your target SD card device carefully.
- Ensure the target boot selection is set to "Non-bootable" or "FreeDOS" (depending on the utility layout) and set the file system output to FAT32.
- Click Start / Format to apply the changes.
Related Article: What is causing a Signature verification failed error 21 during a USB OTA update?
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article