Database Users

Issues with adb shell, etc.

So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)

I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.

i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.

I've tried both things.
Same issue.

What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.

Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize

How do I know that my phone (legend) is rooted or not?

hi firends
How do I know that my phone (legend) is rooted or not?
what are Symptoms for a rooted phone?

Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.

Liquid211 said:
Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.
Click to expand...
Click to collapse
1- how to install driver?
2- please see this picture and tell me what is wrong...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you haven't even installed ADB I don't know how you would think your phone is rooted? Did you buy it used?
Anyways. Download this ADB. Unzip to c: and run adb.exe shell from a cmd in c:\android-sdk-windows\tools
But make sure you install the driver first.
Go to Settings, Programs, Development and Tick Off "USB Debugging". Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.

thanks Liquid211 very much!

Liquid211 said:
... Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.
Click to expand...
Click to collapse
I have no such folder under "android-sdk-windows". I only see "add-ons", "platform" and "tools"...

just try a app that needs root rights.
for example many screenshot apps need su.
another way would be to look if u ve got the superuser app in ur app menu.
and ofcause a terminal like program could help to indicate if uve got root rights.

Simply download a terminal emulator from market and type 'su'...
Sent from my Legend using Tapatalk

[SOLUTION] How I got ADB to communicate with my Kindle Fire HD!

Originally when I tried rooting my Kindle Fire HD on 7.2.3, ADB Devices wasn't showing my Kindle Fire HD device. So, a solution to my problem was installing the Google USB Driver from my Android SDK Manager. After the installation, I was able to open up CMD (Administrator) and see if ADB Devices would show my Kindle Fire HD. Bingo! It appeared!
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After:
-
I'll probably be asking what method I used, and I was using this thread:
http://forum.xda-developers.com/showthread.php?t=2049288
My computer is:
WINDOWS 7 X64
--
Proof of my root:

ADB Server Out of Date
Great post. I If updating the driver does not do the trick, update the ADB daemons. Here are the latest versions:
https://dl.dropbox.com/u/54456659/ADB%20Update.zip

if updating adb doesn't work...
prokennexusa said:
Great post. I If updating the driver does not do the trick, update the ADB daemons. Here are the latest versions:
https://dl.dropbox.com/u/54456659/ADB%20Update.zip
Click to expand...
Click to collapse
And if updating ADB daemons doesn't work try this -> (this is the problem I had)
I was also having trouble getting adb to see the device, even though Composite ADB Interface was there in the Device Manager. After much searching, I found that I needed to put 0x1949 in C:\Users\<my name>\.android\adb_usb.ini. Neither the file nor the directory existed on my system, so I created them both and put that number on a line by itself, saved the file, unplugged/replugged the Fire, and it worked!
found here: http://androidforums.com/kindle-fir...6683-root-kindle-fire-hd-7-a.html#post5363515

ADB Communication Issues
bbanghyung said:
And if updating ADB daemons doesn't work try this -> (this is the problem I had)
I was also having trouble getting adb to see the device, even though Composite ADB Interface was there in the Device Manager. After much searching, I found that I needed to put 0x1949 in C:\Users\<my name>\.android\adb_usb.ini. Neither the file nor the directory existed on my system, so I created them both and put that number on a line by itself, saved the file, unplugged/replugged the Fire, and it worked!
found here: http://androidforums.com/kindle-fir...6683-root-kindle-fire-hd-7-a.html#post5363515
Click to expand...
Click to collapse
bbanghyung,
Great work and informative, thank you.
I love this community, we work together
for everyone's benefit. Keep up the great
work.

[Q] ADB: Device Unauthorized Error

Hello,
I just recently purchased a new Samsung Galaxy Note 3 (N900T) and I am having problems with adb. Whenever I launch adb shell .... It says "Error: Device Unauthorized. Please Check the confirmation dialog on your device." However, this is no confirmation dialog. There has never been one. I do have USB Debugging Enabled, and I have tried disabling it and re-enabling it and it still does not ask me to authorize the device on my phone. I have also restarted the phone, and the computer. Nothing seems to work, and I can not use adb due to this issue.
There is also no "adb_key" file located in /data/misc/adb/ or in the .android folder on my pc.
Can anyone tell me how to authorize my device so I can use adb?

Hi.
Don't know if you found an answer on your problem but I have an Note 3 SM-N9005 an what i have done was to delete the adb folder in /data/misc and then the authorise popup poped up assoon as i plugged my phone into the pc. But just extra info on adb If you want to use adb debugging shell on pc, get the latest version from goolge.
Hope this helped. This worked for me.

how if phone on bootloop, so we can't see pop up confirmation.
any idea?

Clear Auth first, then retry.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T

toastido said:
Clear Auth first, then retry.
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T
Click to expand...
Click to collapse
i repeat, how if phone on bootloop, so we can't see pop up confirmation.
just stuck at logo.

monkey_kungfu said:
i repeat, how if phone on bootloop, so we can't see pop up confirmation.
just stuck at logo.
Click to expand...
Click to collapse
This has nothing to do with adb. i wasn't even replying to you, i was replying to OP, so lose the attitude.
Edit: i now see this was an old thread. That's what you get for posting in a dead thread.
Sent from my leanKernel 3.3 powered stock 4.4.2 (NF1) SM-N900T

oh... i'm so sorry.
can u help me, with that my problem?
edit : i just want a solution

Instruction with Windows PC:
1. Make a copy from C:\Users\User\.android\adbkey.pub
2. Rename it to adb_keys
3. Paste it in your smartphone under /data/misc/adb/adb_keys
4. Restart the smartphone and adb with "adb kill-server" and "adb start-server"

[HELP] TWRP One Plus 5 Not working

SOLVED UPDATED TO LAST OTA AND DID THE WHOLE TUTORIAL AGAIN.
Tried different USB ports. ( 3.0 / 2.0 )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Tried in 2 different PCs and 6 usb ports 2.0 and 3.0
Windows 8 and windows 10.

Have you tried using cmd (administrator) istead of PowerShell?

Lamizure said:
Have you tried using cmd (administrator) istead of PowerShell?
Click to expand...
Click to collapse
Yes

It's really strange... Have you unlocked the bootloader?

Yes " Device State - Unlocked "

It's due to the filename being too long. I found a different fastboot which allowed long filenames. Rename it to one letter like r.img or something and see if it works.

Had exact the same problem under Linux
People mention to change to another USB port but that did not help
What helped... if all stuff is correctly installed (adb, root rights, etc.)
1. Reboot into the bootloader (even if you are in already)
adb reboot bootloader
Click to expand...
Click to collapse
2. Then directly (use the arrow up key to really be fast enough) send the command for flashing (my file was called twrp.img)
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
If this doesn't work you could try (under Linux) to write a little script with just the two above commands or try
adb reboot bootloader && fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It seems to be a timing problem... One might need to play around with the time between this two commands. E.g. wait until the bootloader screen is on the phone and directly issue the flash command. Sorry after it worked for me I did not bother to investigate it in more detail.