I’ve recently started encountering problems while trying to run my application from Android Studio on my MacOS machine. I tried to run the command from adb myself but I still can’t get it to work, although the error appears different.
The errors I get are as follows;
Android Studio
10/02 09:54:53: Launching app $ adb push /Users/{username}/{path-to-apk}.apk /data/local/tmp/{package}
java.io.IOException: Broken pipe
Error while Installing APK
adb (via Terminal.app)
$ adb push /Users/{username}/{path-to-apk}.apk /data/local/tmp/{package}
adb: error: 65536-byte write failed:
Undefined error: 0
Now I’ve tried a lot of different things, some of which are just stretches because the problem appears to lie in something adb related, but none of this seems to change anything;
- Different applications/apks
- Different Android devices (total of 5)
- Different USB-ports (all 4,
with and without USB-hub). - Different (or no) USB-dongles (USB-C to USB-A)
- Restart/Invalidate Caches (Android Studio)
- Reinstall Android Studio
- Reinstall Android SDK
- New (separate) install of Android SDK through homebrew
- Reset NVRAM/PRAM
- Reset SCM
- Update to MacOS Mojave (and retry all of the above).
At this point I am at a loss. Has anyone encountered these errors before without having any of the above solutions fix it? Next thing on my list is a reinstall of the OS, but that feels like a bit of overkill.
I am running on MacOS Mojave on a 2016 Macbook Pro, but everything appeared to have the same effect on High Sierra.
Edit
Weird update on the behaviour, I can get the installing to work continuously after a restart by doing the following steps;
- Login
- Start Terminal.app
- Manually repeat adb push command
- (Command executes successfully)
- Start Android Studio
- Everything works fine…
However, if I start Android Studio without first manually doing the adb push in Terminal, everything is broken as described above.
Edit 2
Even calling adb start-server in Terminal before starting Android Studio makes everything work. So something appears to be faulty when Android Studio is responsible for starting the adb server..
Hello,
I’d like to mirror my Oculus Go on my MacBook with adb & scrcpy.
MacBookPro 14.2
macOS High Sierra 10.13.6-
For this I set the Oculus Go in the developer mode.
Install adb on my MacBook and go to the directory with the terminal.
Now I enter the following commands:
./adb shell ip route (to get the IP address)
./adb tcpip 5555
./adb connect 192.168.178.49 (to connect the Oculus Go via WLAN)
Now I go with the terminal into the directory where Scrcpy is located and try the following commands:
scrcpy -b 25M
scrcpy -b 25M-c 1000: 1000: 110: 220
scrcpy -c 1000: 1000: 110: 220
scrcpy -s 192.168.178.xx
Then I get the following error messages with each command:
ERROR: «adb push» returned with value 1
Can someone help me here?
Greetings
Maik
I’ve recently started encountering problems while trying to run my application from Android Studio on my MacOS machine. I tried to run the command from adb myself but I still can’t get it to work, although the error appears different.
The errors I get are as follows;
Android Studio
10/02 09:54:53: Launching app $ adb push /Users/{username}/{path-to-apk}.apk /data/local/tmp/{package}
java.io.IOException: Broken pipe
Error while Installing APK
adb (via Terminal.app)
$ adb push /Users/{username}/{path-to-apk}.apk /data/local/tmp/{package}
adb: error: 65536-byte write failed:
Undefined error: 0
Now I’ve tried a lot of different things, some of which are just stretches because the problem appears to lie in something adb related, but none of this seems to change anything;
- Different applications/apks
- Different Android devices (total of 5)
- Different USB-ports (all 4,
with and without USB-hub). - Different (or no) USB-dongles (USB-C to USB-A)
- Restart/Invalidate Caches (Android Studio)
- Reinstall Android Studio
- Reinstall Android SDK
- New (separate) install of Android SDK through homebrew
- Reset NVRAM/PRAM
- Reset SCM
- Update to MacOS Mojave (and retry all of the above).
At this point I am at a loss. Has anyone encountered these errors before without having any of the above solutions fix it? Next thing on my list is a reinstall of the OS, but that feels like a bit of overkill.
I am running on MacOS Mojave on a 2016 Macbook Pro, but everything appeared to have the same effect on High Sierra.
Edit
Weird update on the behaviour, I can get the installing to work continuously after a restart by doing the following steps;
- Login
- Start Terminal.app
- Manually repeat adb push command
- (Command executes successfully)
- Start Android Studio
- Everything works fine…
However, if I start Android Studio without first manually doing the adb push in Terminal, everything is broken as described above.
Edit 2
Even calling adb start-server in Terminal before starting Android Studio makes everything work. So something appears to be faulty when Android Studio is responsible for starting the adb server..
I am trying to push a file to a directory on a physical android device, but I am running into the following error.
>adb push data.db /data/data/com.me.app/databases
failed to copy 'data.db' to '/data/data/com.me.app/databases/data.db': Permission denied
I believe adb has sufficient privileges.
>adb root
adbd is already running as root
Here are the permission details for the path: /data/data/com.me.app/databases
drwxrwxrwx system system 2014-01-14 10:31 data
drwxrwxrwx system system 2015-05-23 16:06 data
drwxrwxrwx u0_a224 u0_a224 2015-05-23 15:26 com.me.app
drwxrwxrwx u0_a224 u0_a224 2015-05-23 15:30 databases
I am not sure what to do here. Perhaps I am going about this the wrong way, but I just want to push the data.db file into the /data/data/com.me.app/databases directory on the device.
Does anyone know what I am doing wrong or what I should consider? Thanks.
In this guide, we will show you a couple of methods to fix the Remote Write Failed: No space left on device error when using ADB Push. There exist quite a few methods of transferring files from your PC to your Android device. These include the likes of MTP [USB], OTG, ADB Sideload, and ADB Push. With that said, I have come across a few instances wherein ADB Push was the only option that I could opt for.
For example, once when I was booted to TWRP and the storage was encrypted, the device’s internal storage wasn’t visible on the PC’s File Explorer. On the other hand, I didn’t have an OTG device and cannot use ADB Sideload because it will end up flashing the file [which is not recommended if you are using TWRP, rather go for its Install option].
But as fate would have it, even the ADB Push wasn’t working along the expected lines as it gave out the Remote Write Failed: No space left on device error. What is surprising to note here is the fact that my device already had over 100GB of storage space, hence this error didn’t made much sense. So I did further research on this issue and managed to find out a couple of methods that should help you rectify this bug. So without further ado, let’s check them out.
It is recommended that you try out each of the below-mentioned workarounds and then see which one spells out success. So with that in mind, let’s get started. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
FIX 1: Transfer to Data Partition
Instead of transferring to sdcard [root directory of internal storage], you should transfer it to the data partition. So for example, if you want to transfer the rom.zip file, then the command for transferring it to the data partition will be:
adb push rom.zip /data
Just make sure that the rom.zip is placed inside the platform-tools folder and then use the above command. And if you want to flash the file via TWRP, then go to Install > Up a Level > Data > select the file from there > flash it.
FIX 2: Format Data After Flashing
In some cases, this issue might also occur if you have performed a factory reset via TWRP and then are trying to perform ADB Push. So in such cases, you should first transfer the file via the ADB Push command [adb push rom.zip /sdcard], then flash that file, and finally do a Format Data at the end. However, this fix is only applicable to those ROMs that don’t ask for format data before flashing.
That’s it. These were the two methods that should help you fix the Remote Write Failed: No space left on device error when using ADB Push. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.
- ADB VENDOR KEYS Not Set: How to Fix
- How to Install Custom ROM on Android via ADB Sideload
- Enable and Use ADB Commands in OnePlus Stock Recovery
- Remove/Uninstall Bloatware Apps from Android via ADB
About Chief Editor
Sadique Hassan
administrator
A technical geek by birth, he always has a keen interest in the Android platform right since the birth of the HTC Dream. The open-source environment always seems to intrigue him with the plethora of options available at his fingertips. “MBA by profession, blogger by choice!”