I'm trying to unroot my stock moto g 2014 (XT1068) so i can update it to lollipop (currently on 4.4.4.) I have the motorola drivers installed and i have adb and fastboot but im running into to countless problems, i'm stuck on 'waiting for device' after typing 'mfastboot.exe flash partition gpt.bin' into the command window. please help I have tried pretty much everything.
curtisk123 said:
I'm trying to unroot my stock moto g 2014 (XT1068) so i can update it to lollipop (currently on 4.4.4.) I have the motorola drivers installed and i have adb and fastboot but im running into to countless problems, i'm stuck on 'waiting for device' after typing 'mfastboot.exe flash partition gpt.bin' into the command window. please help I have tried pretty much everything.
Click to expand...
Click to collapse
Is USB debugging enabled?
try different usb port
try launching cmd with administrator rights
bhavin192 said:
Is USB debugging enabled?
try different usb port
try launching cmd with administrator rights
Click to expand...
Click to collapse
usb debugging is on and my phone is in the bootloader mode, and ive tried every usb port on my laptop. and i am launching cmd with administrator rights
Try "adb devices" to see does phone communicate with the pc.
Sent from my XT1068 using XDA Free mobile app
Related
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
tjsas1 said:
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
Click to expand...
Click to collapse
If your phone is running Android 4.2.2, and you are sure that you got the updated Android SDK tools for this particular version, then on enabling USB debugging, you should get a prompt on your phone "Allow USB debugging?" after connecting and running "adb devices", to which you need to answer "Ok"
If you are not running Android 4.2.2, try using ADB through wifi
rugglez said:
If your phone is running Android 4.2.2, and you are sure that you got the updated Android SDK tools for this particular version, then on enabling USB debugging, you should get a prompt on your phone "Allow USB debugging?" after connecting and running "adb devices", to which you need to answer "Ok"
If you are not running Android 4.2.2, try using ADB through wifi
Click to expand...
Click to collapse
Hi,
Thanks for you reply. The phone is on Android 4.0.4, also tried enabled USB Debugging but no popup is showing.
Hope you can help me
God Bless!
Thanks,
Thomie
Try the following:
1. A different port (are you using a USB 3.0 port? If so, try a USB 2.0 port). Try changing the port anyway even if you were using 2.0 too. You may need for windows to install the driver after changing the port.
2. Restarting adb service by executing "adb kill-server" and "adb start-server"
3. Uninstall the driver from device manager and restarting, and letting windows install the driver on its own
4. If none of these works, reinstall the SDK Tools and in that make sure that "Google USB Driver" is installed.
Lets hope one of these works
tjsas1 said:
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
Click to expand...
Click to collapse
Try this one http://forum.xda-developers.com/showthread.php?t=1752074
Maybe your adb is out of date,get a new version
Sent from my XT875 using XDA Premium 4 mobile app
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.
Yesterday i got new z1 after replacement.
previously i had rooted, unlocked bootloader and much more in my phone.
but now with the new phone i m always getting msg to connect with USB debugging even when the usb debugging is ON.
i m unable to root my phone.
plz help me with this
vshainky08 said:
Yesterday i got new z1 after replacement.
previously i had rooted, unlocked bootloader and much more in my phone.
but now with the new phone i m always getting msg to connect with USB debugging even when the usb debugging is ON.
i m unable to root my phone.
plz help me with this
Click to expand...
Click to collapse
Hey..
Could you please elaborate your issue a bit? Have you enabled USB debugging? What happens when you run adb devices on your computer?
Untouchab1e said:
Hey..
Could you please elaborate your issue a bit? Have you enabled USB debugging? What happens when you run adb devices on your computer?
Click to expand...
Click to collapse
yup i have enabled the usb debugging. when when i use any thing related to it i get this message - please connect Device with enabled USB-Debugging to your computer
Revoke usb debugging authorisation in developer options
gregbradley said:
Revoke usb debugging authorisation in developer options
Click to expand...
Click to collapse
nothing happens..
actually in previous phone, when turned on debugging for first time it asks something which is not appearing in this phone. i tried flashing 4.2.2 stock and tried again. I got the same result. i reverted back to stock 4.4.4 and still facing the problem
no one to help me :'(
Check any antivirus is not blocking anything
Please run a command window from adb and run this
Code:
adb devices
Make sure you do not have any other adb devices running (Bluestacks etc)
Try a differetnt PC to check if its the phone or PC
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...
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
jm_sanders said:
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
Click to expand...
Click to collapse
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
riyan65 said:
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
Click to expand...
Click to collapse
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
jm_sanders said:
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
Click to expand...
Click to collapse
To get adb device, you need to enable adb debugging and enable for your pc on phone
riyan65 said:
To get adb device, you need to enable adb debugging and enable for your pc on phone
Click to expand...
Click to collapse
Of course enabled as stated in my first post.
Regards