Hello,
trying to root a Nexus S but I have issues with the drivers.
Running "adb devices" properly shows my phone's serial number. However, when the phone is in fastboot mode, the "fastboot devices" command does not show anything and trying to run the unlock command gets stuck in a waiting loop.
I'm at a loss. I downloaded various driver archives and tried PDANet, with no success.
In Fastboot, the phone shows up as "Unknown device" in the device manager (Windows 7 64bit) with a yellow warning sign.
I tried to manually update the drivers and point Windows to the directories of the drivers I downloaded but it won't accept the drivers, insisting they are not compatible.
Any help would be much appreciated!
http://forum.xda-developers.com/showthread.php?t=2277112
See of this helps at all
Related
I am using fastboot with the "Google USB Driver package, revision 4" from the Android SDK. The device is detected just fine when I am booted into fastboot but nothing is ever listed when I run "fastboot devices" from the command line.
I have tried this with my "Android Dev Phone 1" (I got it from ebay!) and my unlocked/rooted Droid Incredible. Both devices do have USB debugging enabled. Adb works just fine when the devices is booted up.
With the dev phone when I boot holding back/off I get the message "serial0". When I connect it to the computer it changes to "fastboot", as expected.
Any suggestions?
Anyone?
waiting device
I have similar problem here. Fastboot cant seem to detect any device plugged to usb. Tried installing all drivers from LG setup, got sdk and ran cmd promt, cd directory, then typed fastboot erase recovery. It just waits for the device. Is there anyone familiar with this prblem. Hope someone can help. THanks!
So I turned on USB debugging and made sure the RSA key fingerprint was remembered on my phone. I connected my phone to my PC with the HTC drivers installed and ran "adb devices" to make sure that my PC and phone are communicating with each other, and the device is online. I do "adb reboot", and the phone reboots, but then my phone appears offline to my PC. I've looked around for an hour and cannot seem to find the root of this issue...
I've found toggling USB debugging will make the PC recognize the device again, but then I have issues when it comes to try to S-Off the device. I think this is the main cause of the problem.
It appears when weaksauce re-roots after boot, adb no longer recognizes my device. Any fixes?
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
anonimazu said:
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
Click to expand...
Click to collapse
Not sure what you expected?
ADB requires the adb binary to be run at boot via the kernel ramdisk.
Neither FASTBOOT(which isn't supported on Samsung devices) nor ODIN(download mode) run the kernel.
In short ADB does not function in download mode.
Hi,
After I run the In-depth Test, and I'm at the stage when I see that the bootloader is locked, when I plug the X50 Pro 5G into a Windows 10 USB port, the device manager shows an "android" generic device, while it shows a "X50 Pro" when the phone is in normal mode.
The adb and fastboot commands can see the X50 in normal mode, but not when it is in In-depth Test mode, all I get is "waiting for any device".
I tried to update the driver of the "android device" with "Realme_USB_Driver" or "latest_usb_driver_windows_2", but Windows answers that the best driver is already installed.
So, I'm stuck, unable to perform a "fastboot flashing unlock" command.
I have enabled the developer options, and OEM and USB debugging.
What am I missing?
Thanks.
I solved the problem!
I ad to install the drivers from this Japanese file:
QcomMtk_Driver_Setup_V2.0.1.1.exe
I'm not allowed to post a link, google it!
and update the "android device with it"
That allowed fastbot to connect.
Hey guys,
I am Currently attempting to unlock the bootloader on my Pixel 6a, but when I attempt to connect via fastboot in the bootloader my PC shows nothing connected? I can push commands through ADB while the device is booted and have full functionality, but as soon as I reboot the device into the bootloader I lose connection to my PC. OEM Unlocking is enabled in the settings and I have toyed with updating it to the latest update and factory resetting the device. It shows correctly in device manager as 'Pixel 6a' while USB Debugging is disabled and as 'android composite ADB interface' while it is enabled.
To clarify as I am sure many have seen this issue before I do not believe it do be a driver issue as the device will not show up at all in device manager, not even showing with the incorrect driver (No ding to indicate a device has been connected). I have tried using 2 different USB C -> A cables in all slots of two entirely seperate PC's (Both running Windows 10). When I enter fastboot with OEM Unlocking disabled it acts no different to when it is enabled.
I appreciate any help or insight any of you folks can give me.
Device is currently running Android 13 Build number TQ2A.230505.002 if you need anymore info please let me know.
The OEM Unlocking toggle does not affect whether USB function works. It is only a "safety" that allows unlocking the bootloader.
Have you ensured you've installed the correct drivers? Google USB Drivers
I have spent a long time looking at drivers, but I have no device to install the drivers to as the connection drops out once I eneter the bootloader. I have used Zadig in the past to install the correct drivers for devices but when I reconnect the device while I have it open it cannot even detect a new device being connected to the PC. (Also no audible tone which would be heard even with incorrect drivers) I actually only recently used Zadig to install the correct WinUSB drivers for my S10e in which I connected it to my PC in download mode (Queue audible ding) and used Zadig to overwrite the incorrect driver with the correct one. It's almost as if the device will not communicate while it is in Bootloader mode?
I assume you have checked with the 'fastboot devices' command to see if your device is connected when in fastboot mode?