For some reason I can not get my ASUS Nexus 7 to connect to my Windows 7x64 in ADB mode. It connects up find in Fastboot mode, reads the serial number etc. No ADB mode tho.....
How do I fix this?
gregorywest said:
For some reason I can not get my ASUS Nexus 7 to connect to my Windows 7x64 in ADB mode. It connects up find in Fastboot mode, reads the serial number etc. No ADB mode tho.....
How do I fix this?
Click to expand...
Click to collapse
Just to double check, you are not in bootloader mode when trying to use adb? And you have USB debugging switched on?
ADB not working
kilometers4 said:
Just to double check, you are not in bootloader mode when trying to use adb? And you have USB debugging switched on?
Click to expand...
Click to collapse
Correct USB Debug is enabled, and I am at my default desktop.
Related
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
What does this mean? Bricked beyond repair?
- dd
ddbug said:
I'm trying to debrick A500 with a WinXP PC.
It can be detected by the PC as "MTD device". Installed the Acer driver for it (not sure what it does).
Click to expand...
Click to collapse
I'm assuming that you mean MTP (Media Transfer Protocol)?
I'm assuming this means that you are booting Android as I'm not aware of the device being represented as anything but an APX device (0955:7820) if you do not.
What is the problem?
ddbug said:
It can enter the APX mode, detected by the PC correctly, and installed the APX driver "Universal_Naked_Driver_0.72".
But, adb devices does not detect it, so cannot move further to PBJ20upgrade.exe and so on.
Click to expand...
Click to collapse
When in APX mode Android is not loaded so you cannot use ADB (Android Debug Bridge). It should not really matter as, from what I recall, PBJ20upgrade will only use ADB to reboot the device into AXP mode.
Thank you eppeP,
Yes, it was MTP.
So I'll try to proceed with PBJ20upgrade.
(am away now for a week or so ... )
-- dd
I'm running into a problem that I've seen others have. I have a US996, USB debugging is on, OEM unlock is on, and the LG USB drivers are installed.
I can do "adb reboot bootloader" and the phone will reboot into Fastboot with no problems.
But once I'm there, commands don't work. In my Device Manager (Win 7), in fastboot mode, the device is showing up as "Other devices\Android", with no driver attached to it. Okay, so we know where the problem is.
But trying to update the driver in Auto mode doesn't work. Pointing it to the LG directory doesn't work. Pointing it to a directory with the Google USB drivers doesn't work.
How can I fix this?
Haphim said:
I'm running into a problem that I've seen others have. I have a US996, USB debugging is on, OEM unlock is on, and the LG USB drivers are installed.
I can do "adb reboot bootloader" and the phone will reboot into Fastboot with no problems.
But once I'm there, commands don't work. In my Device Manager (Win 7), in fastboot mode, the device is showing up as "Other devices\Android", with no driver attached to it. Okay, so we know where the problem is.
But trying to update the driver in Auto mode doesn't work. Pointing it to the LG directory doesn't work. Pointing it to a directory with the Google USB drivers doesn't work.
How can I fix this?
Click to expand...
Click to collapse
Had the same problem, once you're in fastboot go to device manager and go to your device. You should see
Still_living714 said:
Had the same problem, once you're in fastboot go to device manager and go to your device. You should see
Click to expand...
Click to collapse
Your reply had a cliffhanger...
Haphim said:
Your reply had a cliffhanger...
Click to expand...
Click to collapse
)
Lmao ?, sorry was at work. Here's the link ? it's for the G5 but for the drivers it's the same process. It's about the 430 mark
ADB detects my 6P but cannot detect any devices after restarting into the bootloader menu. When this kind of thing used to happen before I just removed and replaced the USB connection to fix. No more.
Mac is seeing "Nexus 6P" in System Report under USB when 6P is booted and "Android" when 6P is in bootloader menu. I am using Google Platform-Tools. I also tried with another super-clean Mac (both are running Sierra) and got same result.
Trying to flash to Oreo OPR 17 from stock 7.1.2. Device is unlocked. USB debugging is enabled. Just says "Connect USB Data Cable" in bootloader screen. I have never had trouble doing this before. Please help. It's driving me nuts.
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
wizardwiz said:
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
Click to expand...
Click to collapse
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Calico007 said:
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Click to expand...
Click to collapse
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I knew I was doing something stupid. Much appreciated.
Hello Everyone!
Can somebody inform me on how to activate USB debugging when the screen is locked with a pin and the phone has stock software? Samsung phone with Nougat SW.
...
I have gotten this far with my windows 10 laptop which has adb tools installed:
Boot the phone the phone into Recovery Mode.
Select System Mount
Connect to PC and open CMD and change folder path where adb tools is located.
type adb devices in terminal
Now, the issue is that I see is a number followed by "unauthorized". I am trying to use commands such as adb shell, but seems like I am not allowed? I'm assuming it's because the phone is not USB Debug Enabled. I have a different phone which has USB Debug Enabled and adb shell commands are working perfectly. Any way to use shell commands or work arounds? Thanks in advance!
It is not possible to activate Debugging Mode with a locked screen. AFAIK it never was and it never will. And this is good as it is.
RossTeagan said:
3. Boot your phone into ClockworkMod Recovery, by pressing and holding the Power Button + Home Button + Volume Up or Down, depending on your phone
[/url]
Click to expand...
Click to collapse
Why or even HOW should he have ClockworkMod installed? your guide also is for making a Backup out of cwm when the touch is broken and not for activating debug mode
jaannnis said:
It is not possible to activate Debugging Mode with a locked screen. AFAIK it never was and it never will. And this is good as it is.
Why or even HOW should he have ClockworkMod installed? your guide also is for making a Backup out of cwm when the touch is broken and not for activating debug mode
Click to expand...
Click to collapse
Sorry, I thought it would help you...
I want to install the AOSP on the x compact.
I unlocked the bootloader but when I type
Code:
adb devices
no devices is recognized. I installed the fastboot tool too. I booted into fastmode with holding the volume up button when connecting but no device is recognized. I also factory reset the phone without luck to run the
Code:
fastboot
Maybe you need to allow your computer when it's asked on the phone.
evilorb said:
Maybe you need to allow your computer when it's asked on the phone.
Click to expand...
Click to collapse
what you mean when is phone is fast boot there has no display controls
Do it when the phone is ON, just after the USB debugging option is ticked, put your cable and the box for computer authorization will appear on the phone.
Don't know the way to do it when a phone is off.
evilorb said:
Do it when the phone is ON, just after the USB debugging option is ticked, put your cable and the box for computer authorization will appear on the phone.
Don't know the way to do it when a phone is off.
Click to expand...
Click to collapse
I authorized the phone but still not able to run fastboot commands when I go into fastboot mode with the blue led
But now you see your phone in terminal when you type "adb devices" ?
evilorb said:
But now you see your phone in terminal when you type "adb devices" ?
Click to expand...
Click to collapse
in the normal system mode then I can see it but not in the fastboot mode
Adb won't work in fastboot mode. Try "fastboot devices" when in fastboot mode.
When phone is turned off and connected via usb (vol+) to pc then type:
fastboot devices
When phone is turned on and connected via usb to pc (usb debugging on) then type:
adb devices