Related
When i try typing " adb devices" in CMD.
I get
"list of devices attached"
what am i doing wrong?
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
did as u said still the same thing "list of devices attached"
i downloaded latest sdk2.0
and did all as the google page says. its weire why it doest read ADB
fastboot read fine when i write fastboot devices, it show the serial of the phone...
can i add applications through fastboot? instead of adb?
I have the exact same problem. Did you ever figure it out?
What directory are you working out of? If you did the default install of the Android SDK. Try this:
Code:
cd c:\android-sdk-windows\tools
Then:
Code:
adb devices
You have to open the command prompt from within the tools folder from sdk folder.
Also, its never worked for me while my phone is in the bootloader, i run abd commands while my phone is booted normally (with debugging enabled).
I use adb shell stop, adb remount, whatever commands you wanted to do originally, adb shell reboot.
Hope that helps, good luck man.
Sounds like maybe the driver isn't installed correctly. Check your device manager and see if the N1 shows up in there and what it's named.
tamarian said:
You need to be in bootloader, turn off, then turn on while pressing and holding the trackball. Make sure USB debug is enabled in the N1 Applications setting.
Click to expand...
Click to collapse
That is fastboot, fastboot for the bootloader, ADB for everywhere else
Are you on windows or linux?
Also try "adb remount" when you are in the /tools folder, then try "adb devices"
Make sure USB Debugging is on..that could be it
Hello, I install the android SDK correctly and install all correct drivers, all correct files from the google repository, and reading on unlockr, you need to type CMD and enter a few commands, the final one being ADB devices, which is meant to bring up your device serial/id but doesnt show nothing for me, i deleted all drivers with a program, and it re-installs them, I put the phone into debug mode too, but whatever i try, i cant root my magic (32B), please help!!!!
i have followed every single guide but cant blooming root my phone!!!
HELP!!!!!!!!
Install the HTC Sync software first. If this connects correctly and recognizes your phone, then the ADB will find it too. I use it as a test, whether the drivers are installed correctly or not.
To start the ADB, you have to navigate to the folder where the SDK was extracted using the CMD Prompt, and then into /tools. There you type ADB and the command you want to execute.
done that mate, going to /tools and then adb devices and its meant to say a device serial, but on mine it shows nothing
As far as I know, you have to have a recovery installed to access adb.
Write "fastboot devices" while in /tools to see if the drivers are OK. When you install a recovery, adb should be accessible.
I've seen a few posts mentioned how easy using adbWireless app, instead of using USB. However, I've tried and never work. I don't now why people saying it's easy or simple to use, based on different of definition of "easy"
On the NC side, it asked to "adb connect 192.168.xx.yyyy:5555"
I typed that on the Command Prompt on PC running W7, always get "adb is not recognized as an internal or external command, operable program or patch file."
Am I missing something here?
Thought I must need to get the SDK installed, I follow this link:
http://www.androidcentral.com/sdk-driver-root-oh-my
In that instructions of Step 1, the author said "Unzip the download with your favorite archiving tool and drag the folder you extracted into your Workspace. Don't open the folder, just drag the whole thing over. That's it. The Android SDK is now installed."
Is that true? That's it? no need to run any executable file? just drag the folder over and SDK suddenly get installed somehow? Really?
Any input is welcomed.
Ended up installing both SDK and usb driver.
Using adbWireless, cannot connect to it then suddenly it does, don't even know why or what I have done.
I'm start thinking the culprit is my laptop.
"adb devices" always returns with no devices regardless using adbWireless or USB cable.
Gotta tried on different computer.
Sounds like you need to CD to your tools folder in the sdk.
Sent from my LG Optimus V using Tapatalk
You bet.
I CD'ed to the "platform-tools" directory where the adb.exe resided.
Still nothing, even though trying on a different PC.
I guess I've followed the incorrect instructions or at least, an out-dated one.
votinh said:
You bet.
I CD'ed to the "platform-tools" directory where the adb.exe resided.
Still nothing, even though trying on a different PC.
I guess I've followed the incorrect instructions or at least, an out-dated one.
Click to expand...
Click to collapse
If you use adb connect ###.###.###.### (you only need ": port" if you change from default of 5555) then issue adb devices it should list the nook with its ip address as the device id after it is connected.
One thing to be aware of with adb wireless... if the nook is rebooted with it enabled... you will have to cycle adb wireless for it to work.
I actually tried to connect both with and without xx:5555
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
Hello,
I have a problem with my Nexus 4. I tried to flash CM10.1 on it. But doing this I formatted my internal storage. Now I have no way of mounting my device as e storage device on my PC.
The phone is rooted by the way. Is there anyone who can tell me what to do so I can flash a stock android or CM10 on it?
Thanks in advance
Move the rom to the directory where you have adb on your PC. Open the command prompt in that directory (hold shift and right click, then select open command window here)
Boot into recovery.
Then type: adb push [name of rom} /storage/emulated/0/
Flash
El Daddy said:
Move the rom to the directory where you have adb on your PC. Open the command prompt in that directory (hold shift and right click, then select open command window here)
Boot into recovery.
Then type: adb push [name of rom} /storage/emulated/0/
Flash
Click to expand...
Click to collapse
Thank you for your information. Now I get the message (error: device not found). Is this becaus usb debugging is not enabled? Not that I can change this I think.
stefan85sh said:
Thank you for your information. Now I get the message (error: device not found). Is this becaus usb debugging is not enabled? Not that I can change this I think.
Click to expand...
Click to collapse
Do you have your drivers installed correctly?
El Daddy said:
Do you have your drivers installed correctly?
Click to expand...
Click to collapse
Sorry, I made a mistake. I did not entered recovery. This solved it for me. Although I pushed it to /sdcard/ and not your directory. This worked for me. Thank you so much, now I can go to bed
Yep /sdcard/ will work fine too!