[/CODE]bash-4.2# lsusb
Bus 001 Device 011: ID 05c6:6764 Qualcomm, Inc.
Bus 005 Device 002: ID 046d:c50c Logitech, Inc. Cordless Desktop S510
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
bash-4.2#
[/CODE]

Now my device is listed???

I Don't understand:"Just a note, adb will NOT work in the bootloader, just as fastboot will NOT work in recovery or Android. When you are in a mode that supports adb (I'd do both recovery and Android itself)"

bassmadrigal, what path have you set in you bash.rc to your android-tools? Do you have your android-tools installed in /home/user/android-tools? I also have /home/user/.android folder with public & private key?

I don't have a path set up for adb and fastboot, because they are placed in /usr/bin/ which is already in $PATH. You don't need to worry about paths because the command is working. That's why you get the "error: device not found". If you didn't have your paths right, it would say "bash: adb: command not found". So don't worry about adb and fastboot. They are where they should be. You can verify this by typing which adb, which should spit out the location of the adb executable it uses. And instead of trying to type all that out each time to test whether it is working, you can simply run adb devices. It will either show nothing, or it will show the device (see both examples below).

And with adb, you need to have adb in front of the push command. Otherwise, you'll get the error you did stating that the push command is not found.

As to the sentence you didn't understand, fastboot only works in the bootloader. If you are booted into Android or the recovery (TWRP), fastboot won't work. Just like adb won't work in the bootloader, but it does work in TWRP and Android itself.

Now, from your dmesg output, it looks like the computer is recognizing two different devices. One is listed as OnePlus and the other is listed as Android. These are likely different modes in your phone (ie, bootloader, recovery, and/or Android -- each has a separate idProduct number, but I suppose it's possible they have a different idVendor number, which can cause problems). Unfortunately, you cut off the text for the OnePlus entry, so we can't see it's idVendor number.

Can you boot the phone into each mode (bootloader, recovery, and Android) and plug it into the computer each time so we can see the output?

1 members found this post helpful.

bassmadrigal, I've learned from you alot, thanks. I finally got the job done jumping from slackware to dying Vista which I used to place SuperSU, Serpanmod CM12 (Lollipop5.0.2) AK kernel, gapps, & firmware onto internal phone storage.
A0001 is the model number, OnePlus One, OnePlus 2 are product brand model name, under udev rules Qualcom is listed as manufacturer(?), Android is Software. So what is adb using as identifiers?
Now I understand can't be in fastbood mode & use adb as I can't be in android or twarp & use fastboot tool. Don't know what got the tools working. I put the pkgs. I need to push over in tools folder & cd into them but even that wasn't working. adb devices is returning: 4d24f0b8 unauthorized ... whatever that means. Need a little break from this project, I can't even afford a OnePlus one. lol

Ok, if it says you're unauthorized, that means that you haven't granted your computer access from your phone. This should only be there in Android, and should not be present in TWRP. If you boot into recovery (TWRP), you should be able to use adb without a problem.

To try and get authorization, try removing any previous authorizations (or denails) by going to Settings -> Developer Options -> Revoke USB Debugging Authorizations and selecting OK. Now, plug your phone back into the computer and try to run adb devices. There should be something that pops up on your notification bar asking you to grant authorization to the computer. Once you do this, you should have access to your device using adb. You can verify it with adb devices and it should have your serial number and not have unauthorized listed.

Good luck!

1 members found this post helpful.

Thank you bassmadrigal. The OnePlus One got successfully unlocked, rooted, twarp custom recovery app. & installed a great Custom ROM. You were very helpful and I will put this thread in my subscription for future reference.