How can i fix adb sideload error: "cannot read". i am using adb like this: 1. adb devices-shows my firephone 2. adb sideload filename and then "cannot read "filename", i don't get this error all time, when i try to sideload 4.6.6.1 or 4.6.x fireos, 3.5 works but fails with "signature verification failed". I can't install update from sdcard, just adb. I hope someone can help me, i don't have another phone and sorry for my english
FIX IS DOWN
ozan2 said:
How can i fix adb sideload error: "cannot read". i am using adb like this: 1. adb devices-shows my firephone 2. adb sideload filename and then "cannot read "filename", i don't get this error all time, when i try to sideload 4.6.6.1 or 4.6.x fireos, 3.5 works but fails with "signature verification failed". I can't install update from sdcard, just adb. I hope someone can help me, i don't have another phone and sorry for my english
Click to expand...
Click to collapse
Check if you do it:
1. under Adminstrator account on your Windows
2. your antivirus is deactivated
3. both ADB package and the file you try to sideload are located in the simple directories, better not having any spaces and nationaly characzers in the path. (sometimes this also causes problems)
THE FIX IS HERE: 1. Enable debug tracing for adb.exe so you actually know why it's failing by setting the environment variable 'set ADB_TRACE=all'
2. Once ADB_TRACE is set try the sideload command again: 'adb sideload <filename>'
3. adb should now spit out an error message. If it's the large address problem you'll see something like 'Unable to allocate 13345........ bytes'.
I will point out that adb.exe on Windows is not linked to be "large address aware". If you set the environment variable ADB_TRACE=all and try to adb sideload a large file, you'll see that the call to malloc is failing to allocate enough memory for the file.
The "obvious" fix would be for adb not to try to read the entire file into memory or to be linked with the /LARGEADDRESSAWARE flag on Windows.
https://www.techpowerup.com/forums/threads/large-address-aware.112556/ shows the steps to make adb.exe large address aware.
4. Before you run the large address aware executable, you need to kill adb. If you don't kill the service then the utility will fail (without any error message) because you can't modify a running EXE. Type 'adb kill-server' then run the utility.
5. Now, run the utility and perform sideload using command:
adb sideload <filename.zip>
Related
I'm using Cyanogen Mod 6, the most recent nightly build. I want to push the Sense UI notification sounds to the android notifications folder. I attempted to do this via terminal emulator via the following:
Code:
$ adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
When I did that, I get a "not found" error. I was thinking I didn't have permissions, so I did:
Code:
$ su
# adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
I got the same error.
Then, I decided to copy the files I wanted to push into the tools folder on my computer, in the Android SDK. I did the adb devices command, and I saw my device listed. I did the same code as above, and still get the "Not Found" error. I'm sure it's something very simple that I'm missing. I made sure the directories are correct, even making sure everything was case-sensitive.
tokuzumi said:
I'm using Cyanogen Mod 6, the most recent nightly build. I want to push the Sense UI notification sounds to the android notifications folder. I attempted to do this via terminal emulator via the following:
Code:
$ adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
When I did that, I get a "not found" error. I was thinking I didn't have permissions, so I did:
Code:
$ su
# adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
I got the same error.
Then, I decided to copy the files I wanted to push into the tools folder on my computer, in the Android SDK. I did the adb devices command, and I saw my device listed. I did the same code as above, and still get the "Not Found" error. I'm sure it's something very simple that I'm missing. I made sure the directories are correct, even making sure everything was case-sensitive.
Click to expand...
Click to collapse
You're entering the wrong command(s).
Place your notification sound into your AndroidSDK\tools folder, then run:
Code:
adb push name-of-soundbite.mp3 /system/media/audio/notifications/
This will place a .mp3 called "name-of-soundbite" into your notifications folder. You then need to reboot your phone in order for it to work.
Thanks for the help. I was still having the "not found" error, after your instructions. I figured it out, though. I had to run the "adb remount" command, to make the system partition writable. After I was finished, I ran the remount command again, to make it read only.
So, for anyone who has this error later here's the code I used (I did not need to go into the adb shell to do this):
Code:
adb remount
adb push name-of-soundbyte.mp3 /system/media/audio/notifications/
adb remount
tokuzumi said:
Thanks for the help. I was still having the "not found" error, after your instructions. I figured it out, though. I had to run the "adb remount" command, to make the system partition writable. After I was finished, I ran the remount command again, to make it read only.
So, for anyone who has this error later here's the code I used (I did not need to go into the adb shell to do this):
Code:
adb remount
adb push name-of-soundbyte.mp3 /system/media/audio/notifications/
adb remount
Click to expand...
Click to collapse
Oh? I apologize, I thought you already knew to run that.
pseudoremora said:
Oh? I apologize, I thought you already knew to run that.
Click to expand...
Click to collapse
It's fine. I'm a newb/noob, so my adb skills are almost non-existant, but I when I saw the error about the system partition being readonly, that triggered something I read in the adb wiki. I found the remount code there, which paved the way for my success.
I am running Linux Mint 15 on my compute and want to use adb for rooting/reflashing purposes. I downloaded and ran the script from: https://code.google.com/p/adb-fastboot-install/
I used it several weeks ago without any issues. In the instructions it says to rename a file and put it in the Android-tools folder, then change to that directory and then use: adb push filename.zip /sdcard/.
I used adb several weeks ago and don't remember putting the file anywhere special, simply changing to the directory it is in (android-tools)
or specifying the path of the file I wan't to push to the Android SD card. I looked and can't find any folders named "android-tools."
If I run the command adb devices (with the phone connected via USB) I see that the command runs and it finds the device. However, if I then do the command adb push PC36.zip to /sdcard I get an error stating: "cannot stat 'PC36IMG.zip No such file or directory."
What am I doing wrong???
Never Mind
Never mind!
It was getting late so instead of typing the command "adb reboot bootloader" I thought if I just copied and pasted it from the instructions I was using that I would would avoid typos due to being tired. However, I found the my problem was due to my instructions saying to use the command "ADB reboot bootloader."
Hi everyone. I am experiencing problems trying to flash RR Nougat to my Oneplus 3, currently on CM13 6.0.1. It just won't flash at all. I've wiped cache etc but it doesn't want to execute. I've also tried Lineage OS but failed, I have even tried pushing the file via Unified Android Toolkit and even that didn't work. Phone has an unlocked boot-loader (I'm pretty sure) USB debugging, root access etc. Unsure what the issue is so any help would be appreciated. This is what happened whilst using UAT.
Working out the best location to set for Internal Storage..
Waiting for Adb Mode
Device mode detected [device adb]
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for sdcard
Setting push location to mnt/sdcard and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /mnt/sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for mnt/sdcard
Setting push location to storage/emulated/0 and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /storage/emulated/0/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
An Error Occured
The file did not push to the set location for some reason
Please report this in your device thread with details for more help
Press any key to return to the Main Menu..
Thank You.
I don't really have an answer for you but recently I tried to go back to stock, after I locked my bootloader I was unable to sideload anything with adb, have you tried flashing it with TWRP? Just a suggestion, are you able to use recovery at all, if uat can't find the directory, it could be a PC issue? I'm just throwing out ideas to try to help.
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Make sure you are on the latest firmware that is required.
I would just transfer through mtp or download on your op3, then just flash trough TWRP. That's what I do.
sv2203 said:
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Click to expand...
Click to collapse
Yup follow his method. This issue is somekind of adb sideload bug for huge files, name too long or not run as admin. Restarting PC, reinstall driver OP3 driver is another option if problem still persists.
HI all,
I've been trying to push a ROM to my phone using ADB push and it says that it works, but then it says
"adb: error: failed to read copy response"
I can't find it in the sdcard folder either.
When I have a ROM installed, adb push works, but when I fastboot format userdata it doesn't for some reason.
Anyone got any idea whats going on?
Same problem here with adb - Install
coud install 1 APK with --no-streaming
after this every try for another APK gives Message
1 File pushed with *++*MB/s in ***seconds
---Short brake few seconds and than getin' the error from Above
Install failed! .adb: error: failed to read copy response
I just replied on another adb topic, but I was having adb push issues after years of no problems. I ended up using a different computer. If you have the option, hopefully this works for you.
One additional thing would be to check for updated versions of ADB and Fastboot before switching computers.
I had slow transfers that always stopped with this error on OxygenOS on my OnePlus 9R. I rebooted into TWRP and tried again, and it was much faster and successful.
I have a fairly new windows 10 computer and when trying to sideload the it's I get adb sideload cannot read file. Any suggestions?
You'll likely have to give more details.
Using the newest Platform Tools from Google?
Using the newest drivers from Google?
Give an example of a command you've tried (the whole command line) including the location for where you tell it to sideload the file from.