Database Users

I cannot get adb shell to work in recovery mode help!

i have done everything correct i have been at this all day! in cmd it says device not found and i have tried adb kill-server > adb start-server > adb devices and i get nothing

Install pda net on pc with nexus hooked to usb and it will install drivers for u.
Sent from my Nexus 7 using xda premium

Problems with ADB and Terminal on Macbook.

Hi guys I followed the instructions to root the Verizon G2 on my Mac. I installed adb and have an android folder but when I access terminal and type ./adb devices it detects the phone but says device offline. I'm wondering how to fix this? I feel like I've done every step right up to this point if I can get it to recognize adb commands I'm just stuck. Thanks for the help.
Sent from my VS980 4G using XDA Premium 4 mobile app

[Q] Working with ADB & Fastboot

Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?

Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!

feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly

After unlock/recovery/root, cannot use adb commands in Terminal Emulator

Hi all,
After unlocking/recovery/rooting via Heisenberg's guide, I then tried to connect to my Amazon FireTV via Terminal Emulator, but when I try any adb command from it, it says:
/system/bin/sh: adb: not found
What am I missing or forgetting to do? Thanks.

adb is computer -> phone connection. Adb cannot be used in terminal emulator.

zephiK said:
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
Click to expand...
Click to collapse
I've been using the same ADB commands in Terminal Emulator on my Android phones for years...
Anyone?

Anyone? Would really like to be able to connect to all my Android devices...

Can anyone help me with this? I can't find anything online and surprised no one else is asking about the issue...

Same issue was posted here on reddit FYI: https://www.reddit.com/r/AndroidQue.../adb_tool_no_longer_available_on_marshmallow/
How can we connect to other Android devices via Android 6.0 devices if this no longer works?

Anyone had luck with ADB on ChromeOS?

I'm not able to see my PH-1 in ADB on my new Chromebook, and I'm hoping there's a fix available.
I'm in Dev mode, open a terminal, get into shell, type "ADB devices," and the list of devices is blank. No unknown devices, nothing.
I can see it in ADB on the Windows laptop I'm trying to replace, just not on the Chromebook, in Chrome OS, or by using Crouton.
Anyone overcome a similar issue?