I navigate to c:\android-sdk\tools and entered adb shell then I get device not found.
so I used UsbDeview to remove the drivers and I plugged the phone with usb debugging enabled, I get the popup and I point to the directory Windows look for the drivers but find nothing.
but when I switch the phone to recovery mode and plug the phone to pc I am able to install the drivers but still get device not found
I have never used adb before
what I not doing rite here
HTC hero
villainrom 12
flykernel 11 smartass
solved
k guys I manage to solve it
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.
The cable was the culprit. I tried another and it worked. Thanks so much!
I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.
Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.
Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit
make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine
I am wondering around the internet to learn any method to disable MTP/PTP/all usb stuff except charging.
So, why i want this?
Because i want my device to be secure.
I don't anyone to sneak around and try to go into bootloader or recovery/connection to a pc etc to set my device to make a fresh start/copying data and end my privacy up.
So is there a way to disable those functions?
And if it is possible then what? Will it be secured?
And the big question is that can i enable it through recovery (from adb or moving mobile files) as you know if one has a messed up rom then he/she should have those functions workable.
.
@LGaljo?
@nik60?
@MAXSIMUS96?
@adityaupreti?
@Ciro?
@Renix63?
@sev3n1985?
delete mtpApplication.apk in syste/priv-app and in dev options..deflag debug usb
anyway ...not tried because i don't use pin in LS--but in S6 when phone is locked with pin is not recognized with PC
So will it disable the mobile to connect to a pc through bootloader?
I found this on a web:
.
The most device-compatible way to disable everything is to run this command at startup or set this in your build.prop:
Code:
setprop persist.sys.usb.config none
which is equivalent to charge-only on all Android devices.
That also disables adb. If you use adb regularly, then:
Code:
setprop persist.sys.usb.config adb
will allow adb when developer options are turned on/checked. If you don't use ADB often, I would not recommend it, because setting adb causes my S5 to still recognize in device manager, even when it is locked.
To restore original functionality,
Code:
setprop persist.sys.usb.config mtp,ptp,adb
allows all USB protocols.
Hi
I have a Galaxy Note 4 (SM-N910G) and don’t normally muck around with the system. I have limited experience with Android.
My phone is locked (with important data stored in it)– a couple of days ago (presumably after a system upgrade) it suddenly would not recognise my fingerprint nor backup password.
I tried unlocking the phone using Android Device Manager but although I could get my phone to ring or display text, I could not change the password after locking the phone.
I called Google who said that Android Device Manager only works on earlier Android Versions - ?4 and below and most likely my phone would be running Marshmellow.
I called Samsung who said my only option is to restore to factory settings.
I wanted to use ADB
(to enter: adb shell
cd data/system
su
rm *.key) and downloaded it and tried to use it from the c:\ prompt but I don’t have USB debugging enabled. No device was recognised when running ADB.
I had not registered for a Samsung account so I could not use Find My Mobile.
I tried to apply an update via external storage in recovery mode (I downloaded files such as Lockscreen_Security_bypassV1.1.zip or Pattern-Password-disable.zip) but unfortunately when I tried to apply them, it came up with E:footer is wrong, E: signature verification is required.
(I also tried “Android Multi Tools”).
I do not have CMN recovery loaded nor Aroma+File+Manager
My question is: should I try and use Odin (have downloaded odin3_v3.11.2.zip) and TWRP to try and enable USB debugging or try to disable footer/signature verification??
Any other suggestions to try and unlock my phone???
At the minimum this has been an education!
Thank you for your help!
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I am having the same issue. ADB will not work at all with this tablet
Same here
I have the same problem; enabling USB debugging in the Developer Options menu does not seem to have any effect. Closing the settings app and restarting it results in the option being switched "off" again.
This on an unrooted, locked stock device with EMUI version 5.0 / Android 7.0
Weird ....
shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I work around this by enabling usb debugging, going into another setting menu option, then back to developer options, disabling it, enabling it, adb kill-server, adb devices, trying different combinations and eventually it works.. It's a real pain but eventually it works. Once the computer is trusted I don't need to do this anymore.