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.
Related
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
No bootloader interface is found !
ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.
Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.
According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.
How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?
Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.
Hi,
Thank you for using XDA assist.
I suggest you ask your question here http://forum.xda-developers.com/android/help where user with the similar experience might be able to assist you well.
Good luck
Vivek_Neel said:
Hi,
Thank you for using XDA assist.
I suggest you ask your question here http://forum.xda-developers.com/android/help where user with the similar experience might be able to assist you well.
Good luck
Click to expand...
Click to collapse
Thank you for the info.
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.
My phone "POCO x2" has somehow got "bricked" and Now when i try to get it unbricked it does not connects to my pc . Phone is in "fastboot" mode but when I connect's that through cable I can not even see it in "device manager" in "Android" or in "Other devices" please help anyone
Beonder said:
My phone "POCO x2" has somehow got "bricked" and Now when i try to get it unbricked it does not connects to my pc . Phone is in "fastboot" mode but when I connect's that through cable I can not even see it in "device manager" in "Android" or in "Other devices" please help anyone
Click to expand...
Click to collapse
Open device manager and verify whether or not it is loading the proper driver. The correct driver should be something like "Android Bootloader Interface". You may need to download and manually install the full set of drivers for your device manufacturer. After installing the driver's, you may need to manually select the bootloader interface driver.
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?