Related
I downloaded and installed the latest mac intel sdk 1.6 to link with my new rogers magic which is running 1.5. I unpacked everything and restarted my computer. I also enabled debugging on my Magic 3g. When I plug my Magic in, I open terminal in su (root) and once inside the folder, i try running the "adb devices" command however it doesnt work. I get "bash adb command not found". Any ideas from the mac users on here?
should I install the 1.5 sdk, not that it will make a difference since I cant even run the command in 1.6?
any ideas?
Are you putting ./adb devices or just adb devices? because the ./ is very important
tristyB said:
Are you putting ./adb devices or just adb devices? because the ./ is very important
Click to expand...
Click to collapse
.... I am a moron. thank you. I was to excited!!!
ryrules1 said:
.... I am a moron. thank you. I was to excited!!!
Click to expand...
Click to collapse
It's fine, it happens to all of us!
The other options is to add your <android_sdk>/tools folder to your path. That way, you don't need to cd into the folder and use ./adb...you can just use adb from anywhere in the prompt.
Google around but I believe you need to add a line like this:
export PATH=<android_sdk_location>/tools:$PATH
to your .profile file in your home directory.
where <android_sdk_location> is where you extracted the sdk.
figured it out thanks for all the help please delete......
my fear said:
ok i downloaded everything that this link tells me:
http://forum.xda-developers.com/showthread.php?t=532719
but when i put in
cd C:\android-sdk-windows\tools
it just stays in that folder i cant do anything past that. when i type adb shell it says 'adb' is not recognized as an internal or external command, operable program or batch file.
i just redid my computer from windows 7 32 bit to now i have 64 bit. am i missing something? when i had 32 bit i had it working but now nothing and i have all the same stuff as before. yes my phone has debugging checked.
any help is appreciated.
thanks,
Stephen.
Click to expand...
Click to collapse
if its saying adb is not a recognized command you are not in the tools folder.
Which directory are you in?
If you do a dir it should list all of the files in the current directory , do you see adb.exe ?
rsfaze said:
if its saying adb is not a recognized command you are not in the tools folder.
Which directory are you in?
If you do a dir it should list all of the files in the current directory , do you see adb.exe ?
Click to expand...
Click to collapse
ok when i start cmd the line says C:\users\Mr. Tarno>
then i put in cd C:\ android-sdk-windows\tools and then it is in that folder then i did what you said and typed dir and yes it shows adb.exe, its the top file.
when i type adb.exe it shows all the possible commands that i could type but when i try it says adb is not a recognized command.
my fear said:
ok when i start cmd the line says C:\users\Mr. Tarno>
then i put in cd C:\ android-sdk-windows\tools and then it is in that folder then i did what you said and typed dir and yes it shows adb.exe, its the top file.
when i type adb.exe it shows all the possible commands that i could type but when i try it says adb is not a recognized command.
Click to expand...
Click to collapse
That would be right.
I think you're trying to type adb -d shell for example instead of adb.exe -d shell. You would need to include the file extension as well when including commands to be done by ADB.
Hi i know that this question is stupid for u guys here.im woundering where do i get tha adb program(u know like a terminal emulator app).please help i need it for instaling an modified framework.sory for bad english and stupid question
My first android phone so im noob at this tings
Do i need to instal ssh droid from market?
Sent from my GT-I5800
anyone here to giv us a tutorial on adb??
thnx in adv
adb is a part of the Android SDK. Installation is described at "Installing the SDK (devloper.android.com)".
After downloading and installing the SDK (let it download the packages too), open command prompt
In vista\7: Press start -> type cmd to the search box
In XP: Press start and click on 'run' and then type cmd there
Then you must cd.. to the directory where adb is installed (which is usually C:\Program Files\android\android-sdk-windows\platform-tools\
Once your command prompt is there, you can use the adb commands. If it says Adb is not a recognizable command then you're most likely in the wrong directory.
cd.. goes backwards a directory
cd goes forwards
For example, the command prompt shows C:\users\administrator, if you type cd.. it goes to C:\users, you type it again it goes to C:\ etc..
Once there, you type cd program files -> cd android -> cd android-sdk-windows -> cd platform-tools and there you are
More info on how to use command prompt: http://dosprompt.info/
edit: sorry for being stupid. Of course you can do straight cd c:\program files\android\android-sdk-windows\platform-tools
I'm trying to install the 4.1.2 update using the adb sideload method from Android Central but my Windows cmd window states a message saying
* cannot read 'sideload' *
Any ideas to what I'm doing wrong?
Sarg92 said:
I'm trying to install the 4.1.2 update using the adb sideload method from Android Central but my Windows cmd window states a message saying
* cannot read 'sideload' *
Any ideas to what I'm doing wrong?
Click to expand...
Click to collapse
Rightclick in the adb window, choose 'open command prompt here' that way you don't have to manually navigate to the right directory. Once the command prompt is open, type:
Code:
adb sideload {name of file}
NOT a developer here, just have some experience with the basics. Good luck to you.
Thanks!
The update is installing now so this thread can be closed!
Sarg92 said:
Thanks!
The update is installing now so this thread can be closed!
Click to expand...
Click to collapse
Awesome, glad it worked out.... edited typos for others, but you obviously figured it out. Good job!
GT-P6800
GT-N8013
Ok. Real noob question. How do you get to the adb window to right click?
rip93 said:
Ok. Real noob question. How do you get to the adb window to right click?
Click to expand...
Click to collapse
You dont. Navigate to your adb platform tools folder, right-click in the window (just anywhere in the empty space), and select "open command prompt here" --in the same folder that adb.exe resides in---
Then you can type (in the command window)
Code:
adb devices
just to make sure you're connecting to your device, if so then type
Code:
adb sideload {name of file}
don't type {name of file}, just type the name of the file you're wanting to sideload, including the file extension (the 4.1.2 update I'm guessing) --make sure the file is in the same folder as adb.exe so you don't need to type the path name...
Hope that helps
GT-P6800
GT-N8013
aletheus said:
You dont. Navigate to your adb platform tools folder, right-click in the window (just anywhere in the empty space), and select "open command prompt here" --in the same folder that adb.exe resides in---
Then you can type (in the command window)
Code:
adb devices
just to make sure you're connecting to your device, if so then type
Code:
adb sideload {name of file}
don't type {name of file}, just type the name of the file you're wanting to sideload, including the file extension (the 4.1.2 update I'm guessing) --make sure the file is in the same folder as adb.exe so you don't need to type the path name...
Hope that helps
GT-P6800
GT-N8013
Click to expand...
Click to collapse
When I do this, I get same result as typing in "adb help." I don't understand since I see the device when typing "adb devices."
http://www.farside.org.uk/200906/adb_no_devices_found
GT-P6800
GT-N8013
I'm having issues as well. ADB recognizes my N7. I have the file in my /android/platform-tools folder. But when I run adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip, it does the same thing as if I use just the command adb.
Any ideas?
I'm in my adb directory and the file is in there as well
What does it say when you type "adb devices" ?
It lists the device serial number.
Does it also say "sideload" next to the device serial number?
janedoesmith said:
Does it also say "sideload" next to the device serial number?
Click to expand...
Click to collapse
No, it says host.
That's a new one on me. Are you using a Mac? I'm using Win7 x64. When in stock recovery and in the "apply update from adb" screen, mine says:
<device serial number> sideload
janedoesmith said:
That's a new one on me. Are you using a Mac? I'm using Win7 x64. When in stock recovery and in the "apply update from adb" screen, mine says:
<device serial number> sideload
Click to expand...
Click to collapse
Win7 here too, LOL
asimons81 said:
Win7 here too, LOL
Click to expand...
Click to collapse
I'm sorry, I've neverhad tis problem. If your device id is showing up in an adb devices query, you should be able to type
Code:
adb sideload {path to file/name of file}
And it should run.... is your device in recovery? Or just plugged in? Have you enabled USB debugging in settings>developer options?
GT-P6800
GT-N8013
aletheus said:
I'm sorry, I've neverhad tis problem. If. Our device I'd is showingup in an adb devices query, you should be able to type:
Code:
adb sideload {path to file/name of file}
And it should run.... is your device in recovery? Or just plugged in? Have you enabled USB debugging in settings>developer options?
GT-P6800
GT-N8013
Click to expand...
Click to collapse
I reinstalled my drivers. I now have serial number / sideload, but using the adb sideload code still runs the same as typing just adb.
------------------------------------------------------------------------
SOLVED: Had to delete my platform-tools folder and reinstall adb. Worked first try. =D
broadwayblues said:
When I do this, I get same result as typing in "adb help." I don't understand since I see the device when typing "adb devices."
Click to expand...
Click to collapse
I'm getting this too. Any advice?
Edit: Ignore this. Reinstalled and works fine.
Great
sikagoon7 said:
You need to cd to your adb directory and type in: adb sideload C:\path-to-ota\ota.zip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That is the solution :laugh::good:
Thanks
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?
ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.
fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:
Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'
I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!
Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"
DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.