Database Users

[Tutorial] ADB on (X)ubuntu

You have a problem with ADB on your (X)Ubuntu? "ADB not found", "No Device connected" even you set USB debugging?
I got the same problems when I started to play around with Xubuntu.
So I wrote a tutorial how to get ADB running properly under my Xubuntu installation.
Maybe it helps some people.
ADB on (X)ubuntu

I've enabled "USB debugging" under Settings-->Applications-->Development.
And when I directly connect the USB cable to my Ubuntu machine "lsusb" shows nothing.
I also get no USB icon in notification area on my tablet.
What am I doing wrong?!
Please help!

Worked beautifully
Thanks for the adb tutorial. I am running xubuntu on an old Dell Inspiron 1318.
Some tips I found help:
1. I used leafpad to create the 51_android... File
2. I added both "0x1949" and "1949" vendor IDs
3. As soon as I did this adb recognized my device in TWRP with a regular usb cable.
4. I had to execute each adb command with the "./" prefix, state such as "./adb devices"
5. I side loaded cm10 zip and rebooted in TWRP
6. Then I side loaded gapps zip and rebooted
Voila!
Thanks Hascode, PowerPoint 45, and others!

Can't get RSA Fingerprint dialog to popup

Hi all,
I recently bought a OPT and wanted to root it, but I can't get the RSA Fingerprint dialog to appear.
What I've done:
Installed Android SDK and platform tools and all that stuff according to the guide in the general section
Installed Koush's universal drivers and also specifically installed the Oneplus drivers
Rebooted rebooted rebooted both my computer and phone multiple times
Revoked USB authorization multiple times (according to some this works, but not for me)
Tried both MTP and PTP
Switched off and on developer options and USB Debugging
Factory reset my phone
When I start a command prompt in the platform tools directory and execute "adb version", " Andoid Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android" pops up, so I think my ADB is working properly. But when I execute "ADB devices" the ADB server starts up and then nothing is listed under connected devices.
I'm using Windows 10. Any help would be greatly appreciated. Thanks!

This might work
This didn't work for me, but give it a try.
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332

Note 4 Spell Checker not Working

Hi All,
I have Note 4 AT&T vwrsion and i am currently using beta version of MM.
When i jumoed to MM the spell check was working but after a while it just stoped working and i am trying to turn it back on but no luck so far.
I have found this article explaning the steps to turn on the "Auto Spell Check" but unfortunatily this button do not exist in my phone. http://inside-galaxy.blogspot.com/2016/03/samsung-galaxy-s6-edge-how-to-enable_22.html?m=1
Can any one plz help, Thanks in advance.
P.S: i tried at&t thread, no one seams to reply there
Attached is screenshot of my keyboard settings.

Got it fixed via adb command.
- turn on developer options
- turn on usb debugging
- on your PC downlolad and install minimal adb and fastboot ( http://forum.xda-developers.com/show....php?t=2317790 )
- connect your device via usb to your PC, wait 2 minutes until adb drivers have been installed
- run the installed adb link in your start menu, a cmd window opens op
- enter: adb shell
- enter: settings put secure spell_checker_enabled 1
- close cmd, disconnect phone, spell checking is enabled

Nexus 7 2012 bricked, adb/fastboot connection ok but unauthorized. Can You help?

Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?

Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.

Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.

Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.

Following
I have the same error and like to follow

Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.

thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.

No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.

Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.

ADB access to "Google-screened" Nexus Player from (Crouton) Linux

I'm trying to repair a Nexus Player stuck on the Google screen. Unfortunately, I only have Linux at home, and it seems like most of the tools are designed for Windows. I've used ADB often in the past to connect to phones from Linux, but always after enabling USB debugging. My steps:
1. Download the latest platform tools from https://developer.android.com/studio/releases/platform-tools
2. Reboot into recovery mode by holding the button while inserting power, then selecting recovery mode.
3. Run "./adb devices." This successfully starts the ADB server.
However, at this point, no devices are listed. Using "lsusb," I also don't see a device being added when plugging in the Nexus Player. I've tried a couple USB cables, as well as both a Linux Mint PC and a Chromebook running Xubuntu via Crouton. I also tried the command with sudo which occasionally in the past has been necessary.
Is there another step required to have Linux identify the Nexus Player as a device in ADB?