I use win7 64 bit
Adb drivers are properly installed ...
Using stock recovery.
When i connect and check adb devices ,my device is listed
And getting connected.
But when it goes to sideload mode then error pops
up showing drivers are not properly installed.
Cannot execute adb sideload command.
Where can we find the driver for 64 bit to cure this
Problem.....
Pls help
Google? Its not so hard to find 64bit adb drivers. Anyways why dont you install TWRP? Its way easier and the stock rwcovery might give that error.
CE 354 cannot be flashed via twrp.It shows error.
Thus I changed to stock to sideload it.
Even in Twrp sideload ,the same issue remains
Related
I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
I have my watch unlocked and TWRP is installed on it but I am not able to push files to it because it seems to lose connection while in fastboot... it seems all I need to do is figure out how to push the ROM.zip to the watch then I can go into TWRP and install it but after i reboot into the bootloader it loses the connection and I get a "no devices/emulators" message. I installed PDAnet to get the proper drivers and tried to follow a tutorial to install the naked drivers but it is not working... is there anyone out there who can assist me in getting the drivers installed properly?
Any suggestions would be greatly appreciated!
Thanks!
i just used my linux box to push the files and it worked, thanks anyways.
Hi friends,
I recently installed a fresh windows 10 latest build (16299).. I have 64 bit windows 10.. The problem is i cant install moto z play drivers on this build. I was able to install drivers on the previous build of windows 10 but on this build i failed... Motorola Device Manager is stuck at step 2 (Installing USB drivers)... I waited for hours but it is stuck... I tried closing and opening the app but still no luck... Tried restarting and then installing drivers but still no luck.. Everything else is installed perfectly including adb but i am unable to install moto drivers.... Can someone help... Without drivers i wont be able to even flash my device
Anyone??? I need to flash my device...please help
1) Install drivers from this topic https://forum.xda-developers.com/showthread.php?t=2588979
2) After that you will be able to manually assign Android ADB Interface driver to your phone in Device Manager
freeman_g said:
1) Install drivers from this topic https://forum.xda-developers.com/showthread.php?t=2588979
2) After that you will be able to manually assign Android ADB Interface driver to your phone in Device Manager
Click to expand...
Click to collapse
I already have adb installed and it worls fine...its just i am unable to install moto drivers on my pc... I even tried after disabling driver signature bull**** that was introduced in windows...
Those pack also contains proper ADB driver. You do not need separate Moto drivers, original ADB driver from Google will work fine too.
After installation connect your phone in fastboot mode to PC and go to Device Manger. Then update the driver of your phone in manual mode (when you have to choose from the drivers already installed on your PC) and choose Android ADB driver from the list.