For some reason I cannot for the life of me connect the phone to ADB. It, ADB nor Fastboot can ever recognize that my XZP is there. I've done this many times with other phones. I'm positive I have the correct drivers. I'm on a PC with Windows 10. Any suggestions?
You should not be that positive regarding Windows 10 drivers???
Try manually delete the drivers then try again.
droidnew said:
For some reason I cannot for the life of me connect the phone to ADB. It, ADB nor Fastboot can ever recognize that my XZP is there. I've done this many times with other phones. I'm positive I have the correct drivers. I'm on a PC with Windows 10. Any suggestions?
Click to expand...
Click to collapse
I know it sounds stupid, but do you have usb debugging on in developer settings?
Beetle84 said:
I know it sounds stupid, but do you have usb debugging on in developer settings?
Click to expand...
Click to collapse
No it doesn't sound stupid. I actually forgot to do that in the past. However, this time it is on...
Beetle84 said:
I know it sounds stupid, but do you have usb debugging on in developer settings?
Click to expand...
Click to collapse
droidnew said:
No it doesn't sound stupid. I actually forgot to do that in the past. However, this time it is on...
Click to expand...
Click to collapse
I still haven't figured this out if anyone has an idea...
Would factory reseting help at all?
droidnew said:
I still haven't figured this out if anyone has an idea...
Would factory reseting help at all?
Click to expand...
Click to collapse
You can try, but I don't think a factory reset would help. I mean, fastboot should work regardless if you have the drivers installed (drivers will automatically install anyway). Does the blue led light up when you attempt to connect your phone via fastboot?
If you are trying to access ADB via Powershell in Windows 10 it doesn't work. It works with CMD prompt(Admin).
If you have tried with CMD and it didn't work, you may have to try reinstalling the drivers after booting to "Disable Signed Driver Enforcement" in Windows 10.
gowthamachandran said:
If you are trying to access ADB via Powershell in Windows 10 it doesn't work. It works with CMD prompt(Admin).
If you have tried with CMD and it didn't work, you may have to try reinstalling the drivers after booting to "Disable Signed Driver Enforcement" in Windows 10.
Click to expand...
Click to collapse
iArvee said:
You can try, but I don't think a factory reset would help. I mean, fastboot should work regardless if you have the drivers installed (drivers will automatically install anyway). Does the blue led light up when you attempt to connect your phone via fastboot?
Click to expand...
Click to collapse
The blue light does come on when I connect. I have also booted the computer and did the "Disable Signed Driver Enforcement" but I will try again...
gowthamachandran said:
If you are trying to access ADB via Powershell in Windows 10 it doesn't work. It works with CMD prompt(Admin).
If you have tried with CMD and it didn't work, you may have to try reinstalling the drivers after booting to "Disable Signed Driver Enforcement" in Windows 10.
Click to expand...
Click to collapse
I wound up doing this again, and the drivers installed. Maybe they didn't install last time, or I installed more drivers and got the right one in this time.. But, I am now able to connect to ADB and FASTBOOT. Thanks for the help guys!!
I can't unlock bootloader any one have tips to do it..
I got messages att i must install usb drive.. But i don't know how i will this.. I road in sony website but its don't resolve the problem.
Qusay86 said:
I can't unlock bootloader any one have tips to do it..
I got messages att i must install usb drive.. But i don't know how i will this.. I road in sony website but its don't resolve the problem.
Click to expand...
Click to collapse
If you are struggling to find the Google USB drivers for ADB then perhaps unlocking your bootloader is not for you.
Didgesteve said:
If you are struggling to find the Google USB drivers for ADB then perhaps unlocking your bootloader is not for you.
Click to expand...
Click to collapse
Is this the problem?
I would suggest to use a live Linux box, things will be much easier.
uzerzer said:
I would suggest to use a live Linux box, things will be much easier.
Click to expand...
Click to collapse
Absolutley, if he can't fanid any USB drivers then building a Linux box will be a doddle:laugh:
droidnew said:
I wound up doing this again, and the drivers installed. Maybe they didn't install last time, or I installed more drivers and got the right one in this time.. But, I am now able to connect to ADB and FASTBOOT. Thanks for the help guys!!
Click to expand...
Click to collapse
May i know which driver you use?
Related
The phone is in bootloop. I believe that the partition for system and other things were formatted. I can access the bootloader, however when I plug into PC it is not detected. (I have reinstalled drivers to make sure there is no issue) My PC recognizes my nexus 5x just fine. I can boot into recovery as well but pc does not detect the device even when I go to ADB side load. If the phone is off and I plug into the PC phone shows charging but nothing happens on the PC. Any ideas or help would be appreciated. $25 bounty the person with the magic answer.
What does the CMD output when you type in "fastboot devices", while your device is connected in bootloader mode?
P.S. You might want to remove the bounty. There is no need for that. People here can and will help you for free. :good:
DJBhardwaj said:
What does the CMD output when you type in "fastboot devices", while your device is connected in bootloader mode?
P.S. You might want to remove the bounty. There is no need for that. People here can and will help you for free. :good:
Click to expand...
Click to collapse
It looks for the devices, then a blank space then back to the cmd prompt.
ppbatman said:
It looks for the devices, then a blank space then back to the cmd prompt.
Click to expand...
Click to collapse
Just to confirm, while you do this, your device is in bootloader mode?
Also, have you tried it on another PC?
DJBhardwaj said:
Just to confirm, while you do this, your device is in bootloader mode?
Also, have you tried it on another PC?
Click to expand...
Click to collapse
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
ppbatman said:
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
Click to expand...
Click to collapse
While your device is connected, do you see anything unusual in Control Panel > Device Manager?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
ppbatman said:
Yes sit, in bootloader mode. Have tried 3 PC's all the usb ports and 2 usb cables. Im stumped.
Click to expand...
Click to collapse
Also, have you tried a factory reset from within the stock recovery?
DJBhardwaj said:
While your device is connected, do you see anything unusual in Control Panel > Device Manager?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Also, have you tried a factory reset from within the stock recovery?
Click to expand...
Click to collapse
I can't see anything come up in device manger at all. There is no stock recovery it has cyanogen recovery, I did factory reset from this recovery multiple times to no avail. I
ppbatman said:
I can't see anything come up in device manger at all. There is no stock recovery it has cyanogen recovery, I did factory reset from this recovery multiple times to no avail. I
Click to expand...
Click to collapse
That drives me clueless too. It most probably seems like a driver issue. You might want to dig in more?
DJBhardwaj said:
That drives me clueless too. It most probably seems like a driver issue. You might want to dig in more?
Click to expand...
Click to collapse
I appreciate the help. I have tried multiple different drivers with multiple tools. I might try it on a mac to see if I can get it to recognize the phone. Could it be something where the phone was not put into debug mode and not stuck that way?
ppbatman said:
I appreciate the help. I have tried multiple different drivers with multiple tools. I might try it on a mac to see if I can get it to recognize the phone. Could it be something where the phone was not put into debug mode and not stuck that way?
Click to expand...
Click to collapse
Also, I have access to an Octobox through a friend of mine. I wouldn't know where to begin but, I know these are used in some cases to recovery phones.
I suggest you to try with a Linux or Mac machine, as drivers are not required in such cases.
Are you sure you don't have a defective cable?
Cero92 said:
I suggest you to try with a Linux or Mac machine, as drivers are not required in such cases.
Are you sure you don't have a defective cable?
Click to expand...
Click to collapse
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Can you remove all drivers and what not that you've installed, all tools and everything, reboot your PC.
Install this: http://forum.xda-developers.com/showthread.php?p=48915118
Say YES to all options, install the drivers it asks you too.
Reboot your PC again.
Plug device in, while in bootloader mode, try "fastboot devices" again. If nothing happens, reboot-bootloader again from the phone, while keeping the device plugged in.
ppbatman said:
Also, I have access to an Octobox through a friend of mine. I wouldn't know where to begin but, I know these are used in some cases to recovery phones.
Click to expand...
Click to collapse
I would say, first check on a Mac or other Windows machines. See if Device Manager shows anything?
Wiltron said:
Can you remove all drivers and what not that you've installed, all tools and everything, reboot your PC.
Install this: http://forum.xda-developers.com/showthread.php?p=48915118
Say YES to all options, install the drivers it asks you too.
Reboot your PC again.
Plug device in, while in bootloader mode, try "fastboot devices" again. If nothing happens, reboot-bootloader again from the phone, while keeping the device plugged in.
Click to expand...
Click to collapse
I will definitely try this tonight when I get home from work. Thanks very much for the suggestion.
tech_head said:
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Click to expand...
Click to collapse
I don't think the cable is defective, I've tried 3 cables not so far and they all work with other devices.
ppbatman said:
I will definitely try this tonight when I get home from work. Thanks very much for the suggestion.
Click to expand...
Click to collapse
If it does work, I don't want the $25.
I want you to donate the $25 to @BeansTown106 - preferably under my name, but that last bit isn't required
For those who are unaware, Beans is the developer of PureNexus ROMs.
Wiltron said:
If it does work, I don't want the $25.
I want you to donate the $25 to @BeansTown106 - preferably under my name, but that last bit isn't required
For those who are unaware, Beans is the developer of PureNexus ROMs.
Click to expand...
Click to collapse
No problem at all, it will be the best $25 I even spent. Not having this phone work is major butt hurt
tech_head said:
I agree.
Sounds like a defective cable.
I have a Mac so I never worry about drivers and such.
Click to expand...
Click to collapse
Plugged it in to the mac and still nothing. Mac has fastboot and adb installed, confirmed it working with nexus 5x. Im at a loss here.
ppbatman said:
Plugged it in to the mac and still nothing. Mac has fastboot and adb installed, confirmed it working with nexus 5x. Im at a loss here.
Click to expand...
Click to collapse
You might wanna take it to the service center. Of course, tell them that it just didn't reboot after an OTA installation.
I'm running win 10, and out of the blue my comp. can't see my phone. Yes, I have debugging enabled, so I deleted the usb driver to start over. Well, seeing how there is no .exe on driver installs, how do I reinstall the google driver? Windows 10 blows in some ways. This is one of the ways. Thanks
When you say your PC can't see your phone - do you mean nothing appears in device manager? Or ADB can't detect your phone?
wily5150 said:
out of the blue my comp. can't see my phone.
Click to expand...
Click to collapse
I know what you're going thru... It's very frustrating it happened to me a week ago.. I deleted every single driver and installed everything back and nothing.. tried all the things you can imagine and nothing made my pc recognize my phone.. tried fastboot unlock bootloader to factory reset ( I wanted to unlock it anyway ) thru adb folder and then it worked.. so I suppose a factory reset could solve your problem.
elfrosto said:
When you say your PC can't see your phone - do you mean nothing appears in device manager? Or ADB can't detect your phone?
Click to expand...
Click to collapse
Yes, There is nothing in the device manager. There has to be another way other then a hard reset. Thanks.
wily5150 said:
Yes, There is nothing in the device manager. There has to be another way other then a hard reset. Thanks.
Click to expand...
Click to collapse
Does it appear in device manager when you boot into bootloader?
elfrosto said:
Does it appear in device manager when you boot into bootloader?
Click to expand...
Click to collapse
I didn't try that. I just figured that if it couldn't see the phone normally that it couldn't see it bootloader mode.
I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help
Hello
I tried a Nougat rom for the Nexus 4 which was available as a full update package (including system bootloader rom etc) and installed it with the update command from adb instead of from custom rom.
now my phone is bricked and I cant seem to get it fixed.
It either gets stuck in a bootloop, or i can force switch it to bootloader mode. From there I can go to recovery but the stock recovery is useless.
Problem is when i connect this to my windows 10 pc, it shows no sign of being detected. I installed drivers over and over including the universal ADB and fastboot drivers available here on XDA. it doesnt show up under adb devices command and even the Nexus 4 rootkit doesnt detect it as a phone.
I wanna make this phone working again. I'm guessing the way is to go back to stock image and then re-root and re-flash custom recovery and ROM. but even for this, it should be detected by the PC and adb command and rootkit right? Is there something I'm overlooking here?
This is the ROM I tried
https://forum.xda-developers.com/nexus-4/development/fake-nexus-rom-nexus-4-t3230268
The way to install it is also mentioned there and that is exactly what I did.
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
nitin.chobhe said:
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
Click to expand...
Click to collapse
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
BluTheCool said:
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
Click to expand...
Click to collapse
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use adb on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
nitin.chobhe said:
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use abd on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
Click to expand...
Click to collapse
i tried the installer but it made no difference. i tried it my win 7 partition as well but it didnt show up in the device manager.. i think usb debugging must have been disabled with my new rom flash. but even then i dont get why it wont show up as anything in devman...
any command i try ends with waiting for device and since i cant find the device in devman I cant even update the driver manually. I guess I could give linux a shot
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
BluTheCool said:
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
Click to expand...
Click to collapse
Glad that it helped, hope you get it revived soon :fingers-crossed:
Nitin
BluTheCool said:
Hey I finally figured out the problem. It's unbelievable. The USB port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now it's being detected as fast boot. The drivers you provided work like a charm now. Thanks for all the help!
Click to expand...
Click to collapse
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
sandy7874 said:
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
Click to expand...
Click to collapse
Tell me one thing - can you boot to fastboot mode?
Nitin
nitin.chobhe said:
Tell me one thing - can you boot to fastboot mode?
Nitin
Click to expand...
Click to collapse
Yes I m able to boot to Fastboot mode.
sandy7874 said:
Yes I m able to boot to Fastboot mode.
Click to expand...
Click to collapse
Ping me on hangouts. My email ID is in my signature.
Nitin
Windows 10 laptop.....ADB and fastboot are installed, ADB recognizes device. Fastboot will not, Googled this problem and tried several things still no fastboot... any help will be greatly appreciated.
TENlll423 said:
Windows 10 laptop.....ADB and fastboot are installed, ADB recognizes device. Fastboot will not, Googled this problem and tried several things still no fastboot... any help will be greatly appreciated.
Click to expand...
Click to collapse
What device? which oos version? What steps did you take exactly? Did you tried switching firewalls off? Did you tried other pc? Did you follow this guide https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and use the drivers provided there? Can you reboot your device to fastboot mode? Is your bootloader unlocked already or never?
OnePlus 5... Nougat custom rom... Encrypted.... Rooted.... ADB fastboot from Snoop on windows 10... I'm going to disable firewall and uninstall ADB and reinstall. Then see if that helps.
ADB recognizes device... Fastboot does not.. my phone is unlocked and I can get it into fastboot by doing the power and volume up..
I reset my computer last night so I work nights when I get home this morning I'm going to give it another whirl .....thanks for the help.
TENlll423 said:
Windows 10 laptop.....ADB and fastboot are installed, ADB recognizes device. Fastboot will not, Googled this problem and tried several things still no fastboot... any help will be greatly appreciated.
Click to expand...
Click to collapse
I had similar problem I was able to fix it by following below steps,
Go to fastboot
Connect phone to pc
Open device manager
Find your device and uninstall device
Click scan for hardware changes in device Manger
Then it will again show your device in device Manger
Now right click device and select update drivers
Device Manger will automatically download and update drivers for device.
Chamaka said:
I had similar problem I was able to fix it by following below steps,
Go to fastboot
Connect phone to pc
Open device manager
Find your device and uninstall device
Click scan for hardware changes in device Manger
Then it will again show your device in device Manger
Now right click device and select update drivers
Device Manger will automatically download and update drivers for device.
Click to expand...
Click to collapse
thanks. I'm going to give it a try.
Chamaka said:
I had similar problem I was able to fix it by following below steps,
Go to fastboot
Connect phone to pc
Open device manager
Find your device and uninstall device
Click scan for hardware changes in device Manger
Then it will again show your device in device Manger
Now right click device and select update drivers
Device Manger will automatically download and update drivers for device.
Click to expand...
Click to collapse
Thank you so much... Your instructions solved my issue..