adb error:device not found - Hero CDMA General

I saw a quick cmd fix for this recently, but cannot find it now anywhere in the forums. Anybody remember how to reconnect the device to adb?
Thanks in advance,
Rugger

sudo -i //makes you super user
cd /dir/of/androidSDK/tools
./adb remount
./abd shell

I guess I should mention that I'm running through windows, and don't have ubuntu

Ensure USB Debugging is enabled:
Settings -> Applications -> Developement -> USB Debugging

Windows what, what OS r u running? If its win7 use vista drivers to update. Worked for me
-------------------------------------
Sent via the XDA Tapatalk App

Related

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

ADB over Android Wear

I tried installing multiple drivers to my LG G Watch but always appears offline on ADB (cmd)
I made sure I enabled adb debugging and bluetooth and I tried both methods and I cant get it to work....
can anyone help me? I really want to install wear messenger :fingers-crossed:
Are you using adb.exe from the latest SDK?
Have you already forwareded with the adp ?
If not just type this in the console
adb forward tcp:4444 localabstract:/adb-hub
After that type this:
adb connect localhost:4444
It should work on this way to set the state to online
Sent from my SM-N9005 using XDA Free 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

[Partialy Solved] G5 plus rooted, and now cannt use ADB.

Phone is rooted, TWRP installed, (almost) everything is OK.
What is not OK is that now I cannt ADB connect. The "Allow USB debugging" window with the RSA key does not open at all.
Another thing I've noted - the "Revoke USB debugging authorizations" option in the Developer options - does not exist.
Any ideas as to how to solve this ?
I'm using linux (Arch, 64 bit). Another phone (an older, stock Moto G2) connect with ADB without any problem - so this is not a problem on the computer side, nor a USB cable problem.
Thanks.
Ben
Solved (almost).
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
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!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
ben-moto said:
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
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!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
Click to expand...
Click to collapse
+1 to this solution. I have a very similar problem on my HTC One M8. No prompt, also missing the "Revoke USB debugging authorizations" option.
Between this thread, a few others, and that same stackoverflow answer, I was able to come up with a couple of solutions:
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
I'm experiencing this now, except I still have my "revoke USB auth" option under Dev Options.
I'll try the adb push method now...

Driver installer does not start/ no device in fastboot and ADB

When I start the setup file from the Nokia drivers I get an adminstrator prompt and thats it. When I go to downloading mode the device is listed as ADB in device manager but is not listed when I enter ADB devices. USB debugging is active.
Any ideas where to get working Nokia 6.1 plus ADB driver? I am on Windows 10.
Minimal ADB drivers do not work with this device. You need to download Google's ADB from their website.
Sent from my Nokia 6.1 Plus using XDA Labs

Categories

Resources