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.
Related
This is annoying as heck.
I have had the Droid 1, Droid X, and Charge and have always been able to root the phones and install roms and follow directions with now problem.
I have installed SDK, I have downloaded the adb platform tools. However, I have no idea how to get adb where it needs to be from there.
Does anyone know where I can find an in-depth guide?
try here:
http://developer.android.com/guide/developing/tools/adb.html
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Yeah, I have seen that.
I guess the wall I am hitting is how you actually start adb. I know where the folder is. I might be overlooking something though.
Didn't see your post Mart, ill try that now.
martonikaj said:
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Pacifik said:
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Click to expand...
Click to collapse
Even easier is adding the folder to the system path variable.
That allows you to always run adb, no matter what folder you happen to be at.
Ok, I have effectively managed to get to adb and it is installed.
to root the nexus, do I now start at the 1st step in the "lets begin section" listed here:
http://rootzwiki.com/topic/12013-welcome-to-root-editionstep-by-step-oem-unlock-and-root/
http://wiki.cyanogenmod.com/wiki/ADB
Ohai droidstyle good to see you here
Has anyone seen John Connor?
skynet11 said:
Ohai droidstyle good to see you here
Has anyone seen John Connor?
Click to expand...
Click to collapse
Ya you too skynet! I have no gnex yet, but soon...very soon!!
I am now Bootlooped, the bootloader is unlocked, I flashed the recovery image without a problem, but now i am stuck at the constant flashing of the google logo
Did you flash a new ROM?
this is what I was flashing
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
I was just trying to get root and CWM
I have CWM, but all it does bootloop and I can't get it to detect a sd card.
There are several threads on XDA and elsewhere purporting to explain/help people fastboot while using a Mac as their "host." There is even a utility, Androtility:
http://forum.xda-developers.com/showthread.php?t=914826
that claims to facilitate fastboot, as well as most other platform-tools-like tools. Unfortunately, I have not been able to get this to work for me...has anyone out there got another idea?
I can see my device with "adb devices" but "fastboot devices" just returns me to the command line. The version of the stock utility I have is one downloaded from the CyanogenMod wiki, and with which I (without fastboot) succesfully downgraded and rooted my phone...so most of the stuff there works...just not fastboot.
One thought I had was that of the name collision...the CM utility is called fastboot, as is the one in Androtility. Since I adjusted my PATH in .bash_profile to allow access to the CM fastboot version from anywhere, will it be called _even_ if I invoke fastboot while in the Androtility folder, instead of the version that is right there?
Also, need I change permission on Androtility to make it run...? When I call what seems to be the main Androtility app...my shell says there is no such command.
I tried changing the name of the Androtility version to "fastboot-mac" and "fastboot mac" and each time I also got the "no such command" respond from my shell,maybe chmod to 777 is needed...I admit I haven't looked...
I want fastboot so I can flash my hboot to 0.84...has any DZ/G2 plus Mac user done that?
many thanks and regards,
p-d
You have to boot your phone to fastboot, you haven't said if you actually did so I'm assuming no. Otherwise you probably don't have the driver so the easiest option is install the android sdk and platform tools
If you're getting "no such command" it's because the location of it isn't in path, if you're in the folder it's located in you need to do "./fastboot" to run it
Sent from my HTC Vision using Tapatalk 2
Here's my issue. Trying to put an updated CM on my kindle. Put when I open up cmd prompt from my ADB file location from my desktop it won't let me push files.
I'm able to put in the cmd; adb devices. and can see my device is listed in recovery mod. but every time I run the cmd, adb push filename.zip /sdcard/ filename.zip....It doesn't send instead the cmd prompt returns a bunch of lines of code explaining the different commands that are available.
I've reinstalled the USB drivers for my kindle and am running TWRP v2.6.3.1.
Any help is appreciated
Edit: solved my own issue, sorry
Hi there,
I'm having trouble flashing the latest community build to my OP3 from my mac. I followed the instructions below from the lifehacker website to install ADB;
"Download this zip file containing the scripts.
Extract the zip and place the Android folder on your Desktop.
Open a new Terminal window.
Enter cd Desktop/Android
Enter ./ADB-Install-Mac.sh"
Following this, when entering the ./adb sideload command I get the message "-bash: ./adb: No such file or directory"
Everything I have downloaded has been saved onto my desktop, the command I am using is "./adb sideload Oneplus.crdownload".
Does anyone know how I can get round this? I flashed an update to my nexus 7 years ago from my old windows laptop and didn't come across this problem.
I've tried searching the from for a solution but couldn't find what I'm doing wrong.
Thank you in advance!
"./adb sideload Oneplus.crdownload" looks like an incomplete download file in Chrome. Are you sure the file download was successfully?
Hi there,
Thanks for the quick response, I cant be sure, however just downloaded it again and tried the command "./adb sideload OnePlus3Oxygen_16_OTA_007_all_1610310039_bc5bc09fd 9af4ceb".
I still get the same response.
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>