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

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

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:

Forgot pattern and cannot recover- nexus 4 with android 5+ lollipop

Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"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"
}

When you say the USB flash drive doesn't work, do you mean the USB port in the phone?

MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver

I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.

There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse

Problems Running axon7backup.exe On Windows 10

Just got a nice new Axon 7 A2017U. I updated it to B29, which turned out to be a stupid mistake since I now cannot unlock the bootloader. I've been attempting to backup the stock stuff and also flash TWRP using tenfar's axon7backup.exe, but I cannot get it to actually go through. On one of my computers I get the "You cannot run this program in a VirtualMachine" error, and on the other 2 I have tried, the application just sits there with no output beyond "Version 1.10". I am able to make the program output errors when I input the wrong COM port #, but using the one that actually corresponds to my phone in EDL mode just hangs the program until I kill it with CTRL+C. All 3 of the machines I have tried to use are running Windows 10, not sure if that matters.
Has anybody seen this kind of thing and if so, did you find a way around this?
Would it make sense to look at downgrading the firmware on the phone to B27 so I can just use fastboot oem unlock like a normal phone? Also, with the bootloader unlocked do I still have to use the tenfar tool to flash TWRP? For now I'll probably just stick with the stock firmware, but I reeeeeally wanted to run CM13 on this phone.
Here's a screenshot of my cmd output for the curious:
{
"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"
}

Your command is wrong
axon7backup.exe -p 3 -d

CandyFoxJ said:
Your command is wrong
axon7backup.exe -p 3 -d
Click to expand...
Click to collapse
Yes his command was wrong, but the "virtual machine" problem is irrespective of that. I finally used a W7 machine, but certainly like to resolve this.

CandyFoxJ said:
Your command is wrong
axon7backup.exe -p 3 -d
Click to expand...
Click to collapse
There is an AWESOME key on your keyboard that is called PRINTSCREEN. You should try that out sometimes. It takes a screenshot of your screen. You don't even need to take a picture of your screen with a camera!!! :highfive:

Worked fine on Windows 10. Used the compatibility checker and I think it used Windows 7
Sent from my ZTE A2017U using Tapatalk

XblackdemonX said:
There is an AWESOME key on your keyboard that is called PRINTSCREEN. You should try that out sometimes. It takes a screenshot of your screen. You don't even need to take a picture of your screen with a camera!!! :highfive:
Click to expand...
Click to collapse
I'm running Windows on a Chromebook, so no, there's not.

CandyFoxJ said:
Your command is wrong
axon7backup.exe -p 3 -d
Click to expand...
Click to collapse
You mean because I put "COM3" instead of "3"? Because tenfar's documentation explicitly states you can do either, and I have tested both. Please elaborate.

DivinityCycle said:
You mean because I put "COM3" instead of "3"? Because tenfar's documentation explicitly states you can do either, and I have tested both. Please elaborate.
Click to expand...
Click to collapse
That's the only difference I could see between ours. I do have windows in test mode to disable driver signing but I can't imagine that makes a difference

Word, that's what I figured. Not a huge deal, just figured I'd try to get some more info on troubleshooting the application. In the meantime I already set up the stock ROM, and I'm honestly not unhappy with it so far. I disabled all the unwanted apps, and with both 64 GB internal storage AND a micro SD card slot, I can afford to have the extra stuff taking up some space The hardware on this phone is a god damned STEAL for $400 USD!

The tool is not running in virtual machines. You need a physical device with Q10 installed properly in order to run flawlessly. Let it install the drivers and then install the Qualcomm driver. For me it worked fine on first try.
Sent from my ZTE A2017G using Tapatalk