Issues with adb shell, etc. - myTouch 3G, Magic General

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

Related

[SOLVED]Help with ADB, I've tried everything I can think of.

Guys I'm at my wits end. I'm about to give up. I'm trying to get adb working on the nook here on my work computer. I can't for the life of me get it to work. I had no problem on my laptop, but then again I think I caught it before windows installed anything.
I've been using "usbdeview" to uninstall rogue drivers, trying to reel in the problem. However every time I go into device manager, it try's to install "Android ADB interface" which I think means its assigning the wrong driver to it. It should be "Android Composite ADB Interface", no? I know thats what it is on my laptop.
Anybody have any last ditch efforts? I should note that adb works perfectly fine on my Aria on this same machine. I love ADB, hate the setup though.
*****EDIT: Working on different usb port*********
You aren't alone, m8.
I used to have no problem with ADB over USB. But after re-formatting my laptop, I just couldn't get it to work, no matter what I did. I gave up
I'd tried wireless ADB, everybody said it's so easy, me? Couldn't ever get it to work. Gave it also.
At least, for now, I wouldn't think I need it.
I'm now convinced its not driver related. There is something holding my computer back from talking to it. But I'm 99% the right drivers are installed. Mounting disks works fine and it identifies like my android phone does, ADB just won't talk to it.
Try unchecking and rechecking Debugging mode...
Tried that many times. Just for fun I ran the easy adb executable on another machine here, THEN plugged in my nook to it. ADB worked perfect. I'm frustrated, but I really want to figure this thing out. (btw, it identifies with the exact same drivers on both machines)
EDIT: Don't know why or how, but for some reason switching usb ports (which I swear I've done before) worked!!!!!!! It now recognizes and can push/pull/install over adb (usb).
WWW.Ubuntu.com
Enough said.
Love me some Ubuntu, but CMD prompt > Terminal every time.
If you don't mind, can you provide the link to where you downloaded the driver?
Thanks
I used the "combo" pack which installed the drivers and a stripped version of ADB to C: (redundant since I already had ADB installed).
http://forum.xda-developers.com/showthread.php?t=910008
Thanks audio,
I'll give it another try.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
Make sure you're Nook is identifying like this when its plugged in via device manager. If you're unsure how to get here; WINDOWS KEY + R, type without quotes "devmgmt.msc", hit ENTER.
{
"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"
}
Note: You're drive letter's under 'Portable Devices' may vary from mine, that's fine. Just make sure they are there.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
I got all those except the Disk drive list above.
I'll give a try and see what happens.
We may need to uninstall some old drivers before we can get it to install the right ones. You on gtalk or msn? I'll help you troubleshoot it the best I can.
Works like charm.
LOL , without this thread, I would (actually I did) abandon installing ADB over USB.
Thanks audio for providing the correct link.
Gotta love this forum.

[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.

Halp! Windows 8.1 upgrade at war with n4

Hi,
I had win 8 in which I was successfully able to do everything with my n4 (adb connections were good and so was MPT). I updated to win 8.1 and now it's derping out. ADB drivers seem fine. I tested it by simply running adb shell in cmd prompt, but even though my device is connected, it says that it's unable to find device.
Whats more important to me is that the device is not showing up in my computer. Although windows plays the usual usb connection sound. I'm also able to see it has detected my device as Nexus 4 is under the unknown device category. How can I fix this. I relly need to transfer a few things between the comp and phone, and it kinda sucks at the moment.
{
"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"
}
blueren said:
Hi,
I had win 8 in which I was successfully able to do everything with my n4 (adb connections were good and so was MPT). I updated to win 8.1 and now it's derping out. ADB drivers seem fine. I tested it by simply running adb shell in cmd prompt, but even though my device is connected, it says that it's unable to find device.
Whats more important to me is that the device is not showing up in my computer. Although windows plays the usual usb connection sound. I'm also able to see it has detected my device as Nexus 4 is under the unknown device category. How can I fix this. I relly need to transfer a few things between the comp and phone, and it kinda sucks at the moment.
Click to expand...
Click to collapse
Just format it and install Ubuntu!!!
lol, just jocking. if adb is working you don't need it to recognize it. You can just use adb push/adb pull, but anyway.. did u try to enable debugging?
It means something has derped with the mtp driver
Open up device manager
You will see your nexus 4 with a yellow exclamation mark next to it
Right click and update driver
Manually choose
Then you will have to scroll through the list and find the mtp device (I can't remember of the top of my head exactly which headers it is under)
Sent from my Nexus 4 using xda app-developers app
Connect your Nexus 4 in USB debuggin mode and uninstall your current driver in device manager checking the 'delete the driver software' option.
Download Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1379875
Reboot Windows 8 into advance mode and select to disable driver signature: PC Settings -> Updates and recovery -> Recovery -> Advance startup -> select F7 option at the selection menu when you see it
Reconnect Nexus 4 and install it with UND driver.
Thanks all! I just uninstalled the current drivers and reconnected the device. Windows picked up on the right drivers. All ok!

[Q] S5 Device/Android ID

Hi!
Whre can I find the Android ID for my S5 ? Need it for Racoon (updates without playstore installed). Tried device ID app but it shows nothing
michael-oc said:
Hi!
Whre can I find the Android ID for my S5 ? Need it for Racoon (updates without playstore installed). Tried device ID app but it shows nothing
Click to expand...
Click to collapse
What ID do you mean? (Samsung) serialnumber or IMEI?
In an ADB shell:
settings get secure_id
russ18uk said:
In an ADB shell:
settings get secure_id
Click to expand...
Click to collapse
Not working for me. Settings not found error.
michael-oc said:
Not working for me. Settings not found error.
Click to expand...
Click to collapse
Sorry, my bad.
settings get secure android_id
russ18uk said:
Sorry, my bad.
settings get secure android_id
Click to expand...
Click to collapse
Also not working. I have to do this in recovery right? Tried it in downloader mode but got an error "device not found". In windows device manager it´s labeled as modem?!
michael-oc said:
Also not working. I have to do this in recovery right? Tried it in downloader mode but got an error "device not found". In windows device manager it´s labeled as modem?!
Click to expand...
Click to collapse
Boot up normally. Make sure you have enabled debugging. If you haven't, follow the guide here.
After that download ADB:
USB drivers required;
ADB interface.
Install the drivers and ADB. You can find ADB in your Start Menu or you can open CMD and cd to c:\adb
When you connect your phone to the computer in your CMD window type adb shell. You may get a security prompt on your phone to allow or deny. Tap on allow or similar.
Retype adb shell if needed and you should see:
{
"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 good type "settings get secure android_id".
Ask if you get stuck anywhere.
Thanks for all your help! It´s working now. This suggested adb drivers are older than mine and working. Strange

Need Help Manual Fastboot Driver Installation

Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"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"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:

Categories

Resources