Pixel: no adb shell? - Google Pixel Questions & Answers

Brand new unboxed Pixel, only installed app "Helium" to restore a backup.
Here's where trouble starts: needs adb, but no matter what I do (OpenSuSE 42.1, udev rule for 0666 permissions) lsusb sees the device (when USB debugging is set to "charging" lsusb says Nexus 4., when I say PTP it lists as "Google Inc") but adb devices says: <empty list> and adb shell won't connect either.
Pointers appreciated.

Update to the newest version of ADB and dev tools from the Google website.
Sent from my Pixel using Tapatalk

yup, 1.0.36 fixed it.

Related

[GUIDE] MTP doesn't work for you on GNU/Linux? Use adb.

In this guide I will show you how to use adb to move files to or from your device. Especially helpful if your device has MTP and you can't get it to work with mtpfs on GNU/Linux.
What do you need?
Computer with GNU/Linux.
Connection to the Internet.
The 32bit adb binary or the 64bit adb binary, they are added as attachment to this post. (1)
An Android phone with USB debugging on.
Steps:
Connect your phone with a USB cable to your computer. Make sure you have USB debugging on! (2) Put the adb binary in a folder where you can open a terminal. With the terminal open type:
Code:
./adb devices
Make sure it says something like this:
Code:
List of devices attached
XXXXXXXXXXXXXdevice
Now you know you properly connected your device type:
Code:
./adb pull /sdcard/
or
Code:
./adb push /sdcard/
More info on adb commands you can find here:
http://developer.android.com/tools/help/adb.html
(1): If you are using the Debian or Ubuntu distro (or another wich allows you to install *.deb files) you can install the 32- or 64 bit adb packages and use adb from every folder. Download them from the attachments. If you use this type adb instead of ./adb.
(2): Don't know how to turn on USB debugging? Go to settings, scroll down to the About phone menu item. Tap it and scroll down again to Build number and tap it many times! Then go to settings, and tap developer options and find the USB debugging option.
I hope this was helpful, but I think not, because I get no replies...
AW: [GUIDE] MTP doesn't work for you on GNU/Linux? Use adb.
http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html
I usually use sftp to transfer files. No cable and shell access included.
Sent from my GT-I9100 using xda app-developers app
If you want to copy lots of files, like your music collection or movies, wireless is not fast enough. That's why I use adb, because it's very fast.

Samsung SM?T230NU 5.0- ADB Shows Unauthorized Device

adb shows Unauthorized device on custom ROM for SM-231
I successfully rooted my SM-230NU and installed the custom ROM provided in this post
http://forum.xda-developers.com/tab-4/development/rom-android-5-0-lollipop-material-t3061873
However, when I connect the device using USB to my Mac and try "adb devices" I get "unauthorized" beside the device ID. I have already tried the following:
a. on the Mac: adb kill-server followed by adb start-server
b. on the Mac: Deleted the ~/.android/adbkey and ~/.android/adbkey.pub
c. on Device: Revoked the USB debugging access to all computers (on the device) and also via terminal emulator app verified that on the device /data/misc/adb/ directory is empty
d. on PC: Repeated all the above on a Windows 7 machine (still shows "unauthorized" beside the device ID)
e. Changed multiple cables and tried the same cable with other devices and they are all detected as valid devices.
Unless I get the device to be recognized I am not able to install some apks using adb install. Any help will be highly appreciated.

ADB not recognizing Pixel on ubuntu 16.10

Pixel just updated to 7.1.2 build 47K, running adb devices is not showing any phone connected. I am able to view and transfer files through the file manager, but none of the adb commands will work. My other older androids will display fine. Any ideas?
I have usb debugging enabled and connection type set to file transfer. Tried 2 different usb ports on ubuntu 16.10. It's the google store version for what it's worth.
adb version: Android Debug Bridge version 1.0.32
lsusb: Bus 002 Device 012: ID 1xxx:4xxx Google Inc. Nexus 4 (debug)
Sorry if there is another post for this, I searched and did not find an answer to this on my own.
@bdre
try to run adb as root
Code:
adb kill-server
sudo adb start-server
sudo adb devices
:good:
Geeks Empire said:
@bdre
try to run adb as root
Code:
adb kill-server
sudo adb start-server
sudo adb devices
:good:
Click to expand...
Click to collapse
so turned out to be just a bad usb cable...
the one that came with the phone of course did not work

issue with adb from TWRP

Getting this while trying to uninstall Google apps from TWRP using ADB:
c:\adb>adb uninstall com.google.android.youtube
/sbin/sh: cmd: not found
Other adb commands like shell, push, pull are working fine.
USB drivers and adb are pretty fresh, not older than 2 months.
adb version:
Android Debug Bridge version 1.0.41
Version 29.0.1-5644136
USB Driver, ver 11.0.0.0 was downloaded from developer.android.com.
Windows 10 recognize device as 'Android Composite ADB Interface'.
I have tried to disable MTP, unmount/mount System, Data - no avail.
What I'm doing wrong?
Pogo said:
Getting this while trying to uninstall Google apps from TWRP using ADB:
c:\adb>adb uninstall com.google.android.youtube
/sbin/sh: cmd: not found
Other adb commands like shell, push, pull are working fine.
USB drivers and adb are pretty fresh, not older than 2 months.
adb version:
Android Debug Bridge version 1.0.41
Version 29.0.1-5644136
USB Driver, ver 11.0.0.0 was downloaded from developer.android.com.
Windows 10 recognize device as 'Android Composite ADB Interface'.
I have tried to disable MTP, unmount/mount System, Data - no avail.
What I'm doing wrong?
Click to expand...
Click to collapse
Actually, it's more likely TWRP limitation. Some shell commands are not working, like pm.
Maybe I should bring this to TWRP thread instead?
First off, update your drivers the very latest. Then use the bootable TWRP image. The permanent TWRP has stripped down functions to fit in the tiny recovery of the Pixel 3a and 3a xl.

Looking for an app to block file transfers over usb android 11 Kruger&Matz device.

Good morning,
This is my first post so please be gentle. This forum was recommended to me by a friend.
I am looking for an application, or someone who could create an application that would block the ability to transfer files from Kruger&Matz tablets via a usb cable. Tablets are used for training purposes and we don't want participants to be able to download files to their computers.
If anyone knows of such an application and could recommend it (it may be paid), I would be grateful. If it doesn't exist, and someone here can create it, we'll pay for it.
If you need any specific details, I'll try to provide them. Unfortunately, I'm not an IT specialist, so it's hard for me to present all the data that may be needed at once.
If tablets are rooted and USB Debugging enabled you simply disable USB services like MTP and ADB by means of ADB:
Code:
adb devices
adb shell "su -c 'setprop sys.usb.config ""'"
xXx yYy said:
If tablets are rooted and USB Debugging enabled you simply disable USB services like MTP and ADB by means of ADB:
Code:
adb devices
adb shell "su -c 'setprop sys.usb.config ""'"
Click to expand...
Click to collapse
We can't root them, have you ever rooted this model?
Of course not because I'm using Google Pixel phones.

Categories

Resources