I am trying to unlock the bootloader of my g5S+ se
Installed drivers
Turned on USB debugging
OEM unlock
Right click and type adb devices in the command prompt window nada. Devices found
Downloaded the USB drivers from the unlocking page at Motorola. In device manager checked no issues with the driver so what am I missing guys
Have you installed adb?
pradeeppk said:
Have you installed adb?
Click to expand...
Click to collapse
Hey sorted it out via YouTube all good
stevegtrlmk said:
I am trying to unlock the bootloader of my g5S+ se
Installed drivers
Turned on USB debugging
OEM unlock
Right click and type adb devices in the command prompt window nada. Devices found
Downloaded the USB drivers from the unlocking page at Motorola. In device manager checked no issues with the driver so what am I missing guys
Click to expand...
Click to collapse
Fastboot devices
stevegtrlmk said:
Hey sorted it out via YouTube all good
Click to expand...
Click to collapse
How did you sorted bro?
I can see fastboot devices but not adb devices
Related
I think I have a driver problem. I downloaded the most recent drivers for the Moto X from motorola. But when I am connected to my Windows 7 PC, it doesn't recognize my Moto X in bootloader mode.
This is what it shows in Device Manager when my phone is in bootloader mode connected to my Windows 7 PC.
Also, I have PDANet installed, so not sure if that causes a conflict. What can I do to correct this driver problem?
Thanks!!
Cozume said:
I think I have a driver problem. I downloaded the most recent drivers for the Moto X from motorola. But when I am connected to my Windows 7 PC, it doesn't recognize my Moto X in bootloader mode.
This is what it shows in Device Manager when my phone is in bootloader mode connected to my Windows 7 PC.
Also, I have PDANet installed, so not sure if that causes a conflict. What can I do to correct this driver problem?
Thanks!!
Click to expand...
Click to collapse
Did you try getting the Motorola Drivers from Motorola?
Cozume said:
I think I have a driver problem. I downloaded the most recent drivers for the Moto X from motorola. But when I am connected to my Windows 7 PC, it doesn't recognize my Moto X in bootloader mode.
This is what it shows in Device Manager when my phone is in bootloader mode connected to my Windows 7 PC.
Also, I have PDANet installed, so not sure if that causes a conflict. What can I do to correct this driver problem?
Thanks!!
Click to expand...
Click to collapse
Have you made sure USB Debugging is enabled?
SwiftLeeO said:
Did you try getting the Motorola Drivers from Motorola?
Click to expand...
Click to collapse
yes, I downloaded and installed the Motorola Device Manager as instructed and I have USB debugging enabled. When I am not in bootloader mode and my Moto X is connected, this is what i see - Mot Composite ADB Interface, which I believe is the correct driver.
But in bootloader, it is the Mot Single ADB Interface. I am wondering if that is the issue?
When I type adb devices, it says list of devices attached but it does not list any devices. If I type fastboot devices, it lists my device. So fastboot works but adb doesn't.
DuvelDroid said:
Have you made sure USB Debugging is enabled?
Click to expand...
Click to collapse
yes
Cozume said:
yes, I downloaded and installed the Motorola Device Manager as instructed and I have USB debugging enabled. When I am not in bootloader mode and my Moto X is connected, this is what i see - Mot Composite ADB Interface, which I believe is the correct driver.
But in bootloader, it is the Mot Single ADB Interface. I am wondering if that is the issue?
When I type adb devices, it says list of devices attached but it does not list any devices. If I type fastboot devices, it lists my device. So fastboot works but adb doesn't.
Click to expand...
Click to collapse
Okay so this isn't the same exact phone but maybe it will help:
http://forum.xda-developers.com/showthread.php?t=1322323
SwiftLeeO said:
That is interesting. Have you installed SDK Tools for Android? It's a long shot but it got my Nexus 7 to be recognized. Then again I believe those were google specific drivers but you can try that... Otherwise, you shouldn't be having any issues.
Click to expand...
Click to collapse
no, what is it?
I have tried 2 USB cables, one is a brand new USB cable and I have used both USB ports on my laptop. There are other people online I can find who had this same issue, but not much info on how to resolve it.
I have uninstalled and reinstalled the Motorola Device Manager, which installs the drivers, 3 or 4 times now. Rebooted my laptop and my phone several times. Uninstalled PDANet in case that was an issue.
Fastboot works, adb doesn't.
I would like to manually install the Mot Composite ADB Interface driver while in the bootloader mode, but I can't seem to find where it is on my computer.
Cozume said:
yes, I downloaded and installed the Motorola Device Manager as instructed and I have USB debugging enabled. When I am not in bootloader mode and my Moto X is connected, this is what i see - Mot Composite ADB Interface, which I believe is the correct driver.
But in bootloader, it is the Mot Single ADB Interface. I am wondering if that is the issue?
When I type adb devices, it says list of devices attached but it does not list any devices. If I type fastboot devices, it lists my device. So fastboot works but adb doesn't.
Click to expand...
Click to collapse
right click on the Mot Single ADB and uninstall then move the usb cable to a different port and let it reinstall then try again i know you dont have to have the SDK installed because i dont and my phone works fine. also try using a different cable some phones are really picky when it comes to what cable you are using
SwiftLeeO said:
Okay so this isn't the same exact phone but maybe it will help:
http://forum.xda-developers.com/showthread.php?t=1322323
Click to expand...
Click to collapse
the only motorola program I have on my computer is the motorola device manager and I uninstalled it and reinstalled it several times now. For some reason, Windows uses the wrong driver when I am in bootloader mode.
dray_jr said:
right click on the Mot Single ADB and uninstall then move the usb cable to a different port and let it reinstall then try again i know you dont have to have the SDK installed because i dont and my phone works fine. also try using a different cable some phones are really picky when it comes to what cable you are using
Click to expand...
Click to collapse
When I did that, I removed the Mot Single ADB Interface software from my computer and then it failed to install Fastboot ghost s. I need to find out where the Mot Composite ADB Interface driver is on my PC so I can manually install it. Where should I look for it?
when I put the phone in recovery TWRP 2.6.3.1, adb will recognize my device but it thinks it is my Samsung Galaxy Nexus.
Cozume said:
when I put the phone in recovery TWRP 2.6.3.1, adb will recognize my device but it thinks it is my Samsung Galaxy Nexus.
Click to expand...
Click to collapse
Uninstall everything on your USB ports/drivers restart let windows redownload the USB ports/drivers and run the Motorola drivers install
MOTO X Slapped
[email protected] said:
Uninstall everything on your USB ports/drivers restart let windows redownload the USB ports/drivers and run the Motorola drivers install
Click to expand...
Click to collapse
yeah, that is looking like what I am going to have to do
I hit the issue earlier and fixed it with the steps. hope will help you too.
1. connect your phone with computer
2. go to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\
3. run Motorola Driver Installer.exe, choose clean and Reinstall.
Hi all I have just bought my xz and I'm trying to root 4.3 but my computer won't see usb debugging the root tools just says device not connected even though I can browse through my address cards I have installed flashtool drivers and adb drivers that. Way because the prompt never popped up when I first connected my phone but still can't see usb debugging. Any ideas. Thanks
Unplug the device from the computer
Download latest adb, which is most likely outdated
Turn off USB debugging and turn on again
Connect it to the computer
Accept the key popup
Run adb
Google will help you more than me, as I did this from memory and used Google a few days ago with the same problem.
antonio1475 said:
Unplug the device from the computer
Download latest adb, which is most likely outdated
Turn off USB debugging and turn on again
Connect it to the computer
Accept the key popup
Run adb
Google will help you more than me, as I did this from memory and used Google a few days ago with the same problem.
Click to expand...
Click to collapse
Thanks Bro I did a Google search first but didn't find anything related to my problem
gavster26 said:
Thanks Bro I did a Google search first but didn't find anything related to my problem
Click to expand...
Click to collapse
Download the latest version of flashtool from http://www.flashtool.net/download.php
navigate to the driver folder and install the fastboot and flash mode drivers.
open flash tool put your phone is fastboot it will install the latest drivers automatically.
after that try rooting following the below procedure
http://techbeasts.com/2014/02/21/ro...-latest-10-4-1-b-0-101-firmware-how-to-guide/
androidtweaker1 said:
Download the latest version of flashtool from http://www.flashtool.net/download.php
navigate to the driver folder and install the fastboot and flash mode drivers.
open flash tool put your phone is fastboot it will install the latest drivers automatically.
after that try rooting following the below procedure
http://techbeasts.com/2014/02/21/ro...-latest-10-4-1-b-0-101-firmware-how-to-guide/
Click to expand...
Click to collapse
Sorry already sorted it out Bro I ran adb kill-server adb start-server and accepted the prompt on my z now all well but thanks anyway
gavster26 said:
Sorry already sorted it out Bro I ran adb kill-server adb start-server and accepted the prompt on my z now all well but thanks anyway
Click to expand...
Click to collapse
:good::highfive:
Hi,
I've an issue with ADB? driver?
When my phone is boot on android adb show my device, after "adb reboot bootloader"
I see that on my device manager when I'm in the bootloader so I've tried to install google usb drivers but with no success
Thanks in advance
Do you have USB debugging turned on?
Gabboplano said:
Do you have USB debugging turned on?
Click to expand...
Click to collapse
yes
plopingo said:
yes
Click to expand...
Click to collapse
I've sucess to install driver, android device => Motorola ADB interface but "adb device" still return nothing
So, my MI3W won't show up on fastboot devices command , neither does it show in MiFlash.....
I have installed minimal adb and fastboot also i have installed latest MiPcSuite . Even it doesn't show in device manager . I am runnig windows 10 with driver enforcement disabled .
gauravbhakuni90 said:
So, my MI3W won't show up on fastboot devices command , neither does it show in MiFlash.....
I have installed minimal adb and fastboot also i have installed latest MiPcSuite . Even it doesn't show in device manager . I am runnig windows 10 with driver enforcement disabled .
Click to expand...
Click to collapse
try this
en.miui.com/thread-73348-1-1.html
smh.saad said:
try this
en.miui.com/thread-73348-1-1.html
Click to expand...
Click to collapse
My phone is running fine. Its just that it is not showing up on PC device manager.And I can't use fastboot commands. ADB commands are running fine.
gauravbhakuni90 said:
My phone is running fine. Its just that it is not showing up on PC device manager.And I can't use fastboot commands. ADB commands are running fine.
Click to expand...
Click to collapse
might be windows drivers problem or USB FLex need to be replaced
or a bad USB cable
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Quaczi said:
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Click to expand...
Click to collapse
I had this problem in my Nokia 7 Plus, then i used and installed "minimal adb and fastboot" file which detected my phone in fastboot. It installs in program file with a folder named "minimal adb and fastboot"
Sent from my Redmi K20 Pro using Tapatalk
You need to enable "USB debugging" in the developper options
ImEraaz said:
You need to enable "USB debugging" in the developper options
Click to expand...
Click to collapse
It is enabled.
And ill try with the minimal adb option
Update:
Still not working
I have same problem, there is no way to recognize my 9t pro in fastboot mode... i cant do anything
First it should be intel pc
Try to install Xiaomi drivers and adb
Boot to recovery and fastboot while connecting to usb to install the drivers
Then check again
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
simpn said:
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
Click to expand...
Click to collapse
Try changing ports / connect to another pc
Install proper drivers .
Is your bl unlocked now ?
Got it to work under win7 with great help from this post.
What I did was:
Update to the latest miui version (to MIUI Global 11.0.3, as prompted in system settings, I hadn't bothered to update because I just want to throw miui out)
Disable OEM unlock
Reboot
Enable OEM unlock again
Reboot into fastboot
Then the phone showed up as an unknown device in Device Manager
Right clicked the device and updated the driver, chose to search for drivers in the miflash_unlock-en-3.5.1108.44\driver\xp-win7-win8 folder
The device now lists as an Android Bootloader Interface device
And now:
$ fastboot devices
e150445 fastboot
MiFlash unlock detects the phone, and I could proceed with unlocking. Still have to wait though. Tried the older-version-trick as suggested here, but that just told me to update to the latest version. Guess I'll have to wait a week then...
Hope this helps someone. This is the most tedious unlocking procedure I've encountered so far...