I'm dumbfounded. I have unlocked bootloaders and rooted for years. Just got my OP8P.
I also have a new Microsoft Surface Pro with Windows 10.
I installed ADB, installed Fastboot.
Unlocked developer options and turned on USB Debugging and Developer Unlock.
Windows device manager shows ADB INTERFACE for the my device in device manager.
I can open can open Power Shell and/or the CMD prompt. I've done both.
I can type adb devices in the command prompt and I CAN see my device.
I can reboot it fastboot from the CMD prompt so I KNOW Wndows sees my phone.
BUT ONCE I'M IN FASTBOOT, the problem starts.
Fastboot does NOT see my device. Commands return the words "Waiting for Device..."
I BELIEVE the issue is with the drivers. When I boot into Fastboot, my device location changes in Device Manager from USB>ADB Interface to Portable Devices>Android.
The Android Device icon has a yellow triangle with an exclamation mark. It's says the driver for this device is not installed. But everything was working fine and the drivers were fine while the device was powered up normally.
If I try to manually install the driver it fails and says "cannot update drivers for your Android".
What heck is going on? What did I do wrong?
I've uninstall and reinstalled the drivers direct from Oneplus. I've uninstall and reinstalled the drivers direct from Google. 'I ve uninstall and reinstalled the drivers direct from Windows.
Why can't device and drivers be recognized in Fastboot. And why can't I update the drivers for the "Android" device?
Related
So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device
When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?
I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.
If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.
Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.
I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.
ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.
I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium
Delete
I am trying to do a full reset in ADB which I have done a few times before. However, when I connect my nexus 4 in fastboot mode to my laptop and open command prompt it says 'device not found'. I have USB debugging enabled and the right drivers but it still won't let me do any adb commands. I am using the fastboot and adb files from the latest SDK but its not working. I have tried reinstalling drivers and rebooting my laptop but it still won't work. If it matters I am running android 4.3, on the latest PA 3.99.
Try clearing your RSA keys from the developer menu, unplug and plug a few times till the phone asks to 'remember this computer' again, try reinstall the ADB driver also
apopberz said:
Try clearing your RSA keys from the developer menu, unplug and plug a few times till the phone asks to 'remember this computer' again, try reinstall the ADB driver also
Click to expand...
Click to collapse
How do you clear RSA keys? I can't see it in developer options
I have attached a screenshot, as you can see, fastboot devices shows but no adb
Anyone??
Not sure if you know, but ADB commands are only allowed when android itself is running, thus the name "Android Debug Bridge".
If your fastboot is working, you should be in bootloader. How are you going to ADB in the bootloader?
I went through the motorola site unlock bootloader process. Installed the Android Studio and the Motorola device manager. ADB saw my device and was able to unlock device. With the phone in normal mode and developer options set ADB sees the device. But when I go back into fastboot adb no longer sees the device.
Windows10 still sees the phone (mot composite ADB interface) in device manager but ADB shows no devices listed.
I'm just trying to get the phone rooted.
Resolved: Was using WinDroid under assumption that it needed to be in fastboot.
I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!
elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?
If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.
You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.
I want to install LineageOS so I closely followed the fastboot and adb instructions on the official site. During my first (failed) attempt, there were some old Google USB and ADB things on my PC, so I deleted everything and started again with a clean slate.
I managed to make ADB work (adb devices detects my device, could authenticate the computer, all seems good there). But if I start the phone in fastboot mode, connect and run fastboot devices, I get nothing back. It doesn't give any sign of the connected device. Windows's "Devices" window lists a device called "Android", but it's under "Unspecified" and has the yellow triangle/exclamation mark on the icon.
1. Am I right to assume that this will stop me from unlocking the bootloader (if I will use the unofficial method) and flashing TWRP and a custom ROM on the device?
2. More importantly: What could be wrong, how can I make fastboot see my phone?
Many thanks for the suggestions!
hi,
first do you have latest ADB and Fastboot
then connect your device and run adb devices. check if it detect the device means from the command prompt run "adb reboot bootloader" (without quotes)
now once after device reboots to bootloader check fastboot devices it will detect now
if not then goto device manager,right click on the device and click on update driver software and choose android fastboot interface
you are done now run fatboot devices,it will detect the device
Solved!
adbdriver com/downloads/