0
Seppppx said:
Hi.
I have tried everything to get adb working, even tweaking bios settings.
I have tried multiple adb drivers, including the XZ2 driver but none of them have adb working. I have tried minimal adb/fastboot environment and googles's own adb/fastboot environment, but none works. Fastboot works just fine. I have had multiple phones, but I don't remember adb working on any of them (only fastboot worked). Maybe it's a PC specific error? The only think I can think of only one thing that could have caused it and that is the lack of virtualization. Even with it enabled in my bios apps like Virtualbox still say I need to turn it on. Is there any fix to this?
Thanks in advance.
Click to expand...
Click to collapse
Hi, I had the same problem.
I assume your opreating system is windows?
Does your system recognize the phone if connected vai USB? It should be shown.
Try using zadig. This tool tells you wether your driver is ok.
I could fix the problem by using a differt driver.
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 need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
sergei pan said:
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
Click to expand...
Click to collapse
Ustonovlena? What is that? Serbian? Nevertheless. Even when Windows says the drivers are installed, if adb doesn't connect, it's a driver issue. Uninstall and delete your current drivers then reinstall with the device turned off. When you turn the device back on, KFU should recognize it.
If not, try to issue the command you need anyway. Sometimes it will work anyway. Either way, it is a driver issue. Keep working at it. You may have to reboot your computer to get it to work but as long as you understand that it's the drivers causing problems, you should be able to get it working.
try to change to another user,or worst still use another pc.
Not sure if this can work,but its worth a try since mine work this way.
Sorry. I am writing through Google. Russian. Already endured, and once again put the driver. It did not help.
What rom are you using?
Rom?
If I understand you correctly, a native Amazon 6.3.
The reason I ask is that some custom roms have USB debugging turned off by default and others have trouble with adb to begin with.
But, considering that is not the case, it is a driver issue, plain and simple.Just keep trying. Uninstall/delete/reinstall your drivers. It may help to get the Android SDK and configure them yourself.
It has been repeatedly reinstalled the driver. It does not help. Tried on two computers (XP and Vista). The result is the same. The question-whether the Kindle can be seen in My Computer? I have Windows does not see it.
Programmes at the request of the developer to KFU (Vashypooh) to help. Write in the subject can not have enough rights-http://forum.xda-developers.com/showthread.php?t=1399889.
I beg to inform him of my request for help.
Im having the same issue
I cant tell you how many times i have re installed the drivers. Reboots in between.. u name it
One time i did get adb to see my device. But it still wouldn't fast boot
Im on 2.2.. its a brand new refurb..got it today
Sent from my DROID RAZR using XDA
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Bump - anyone? Bueller? Bueller?
B
finnfather said:
Bump - anyone? Bueller? Bueller?
B
Click to expand...
Click to collapse
If you're trying to root then see the method I added to the end of the ROOT thread (can't post link, new account).
In short, you can get directly into the flashed recovery without it going back to normal and getting over written first without needing to use ADB to send it back to recovery mode.
Just take the back off, then once you have flashed the crackling recovery: pull the battery.
Plug it back in with the volume down held and power the device on, holding volume down.
You'll get into the recovery and can install superSU.
Hope that helps.
finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
I had the same problem on my Windows 10 that was upgraded from 8.1.
To fix it, I removed completely Android SDK and reinstalled it. For some reason this was the solution for me.
I tried the same things as you before that (except factory restore as it is a pain) and got the same results - no device listed.
As for Linux and OSX, the Swift got recognized without a problem.
finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
Hi everyone,
@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the atock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev
Hi
Windows 10, android sdk installed and google drivers.
Fastboot shows 8bce440 fastboot when fastboot devices is tried in cmd (admin priv) and "waiting for any devices"
ADB list devices is also empty.
Any help appreciated.
Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?
Pak0St said:
Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?
Click to expand...
Click to collapse
Hi Cheers for replying.
I have now tried it on Win 10 (clean install) win 8.1 (clean install) and windows 7 (clean install)
Reinstalled sdk on 8.1 and 10 twice but no joy. I cant see anything under device manager for it (in fastboot)
Under devices and printers it shows Android
Any help appreciated.
---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------
adb_usb.ini could this help? I have tried creating a file manually. But no joy
In fastboot mode, it should come up as Marshall London Bootloader Interface under Device Manager. From Devices and Printers you can check what driver is currently installed when it's displaying "Android".
Windows 8/10 is very insistent on using verified drivers. You could try to uninstall the current driver and re-connect the device so that Windows can try to find the verified ones.
For me it automatically installed the fastboot drivers, although it wasn't fast enough and the Swift rebooted before the drivers were finished with installation.
I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
xda163fm said:
I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
Click to expand...
Click to collapse
Think fast boot only works in bootloader mode see here for unlock instructions
http://https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
If I am using windows what drivers should I install? Adb works but does fastboot need drivers also? I have tried fastboot both with phone in and out of the fastboot screen - I have to pull battery to get out of fastboot mode! Thanks
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
xda163fm said:
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
Click to expand...
Click to collapse
I can't get fastboot working either. Really annoying me.
I have got this sorted. I will post details in the morning. I used a live USB of Ubuntu 15.10.
I recently upgraded from a prebuilt to my own i5-6500 and 1070 build, and everything was going great until I needed to use fastboot to flash Pixelrom. To my surprise my device was not found. ADB works perfectly fine, and I've tried the regular SDK Dev Tools, the Universal ADB/Fastboot Drivers, and even the Pixelrom's inbuilt fastboot to no avail. I'm not really sure what could be causing this issue because I installed the SDK and drivers the same as my original computer ( Which I have to switch to now if I want to use fastboot ). I've tried multiple ports on my computer with no change.
Feel free to make some suggestions or ask for logs, etc.!
StevelyTM said:
I recently upgraded from a prebuilt to my own i5-6500 and 1070 build, and everything was going great until I needed to use fastboot to flash Pixelrom. To my surprise my device was not found. ADB works perfectly fine, and I've tried the regular SDK Dev Tools, the Universal ADB/Fastboot Drivers, and even the Pixelrom's inbuilt fastboot to no avail. I'm not really sure what could be causing this issue because I installed the SDK and drivers the same as my original computer ( Which I have to switch to now if I want to use fastboot ). I've tried multiple ports on my computer with no change.
Feel free to make some suggestions or ask for logs, etc.!
Click to expand...
Click to collapse
Try the nexus root toolkit. In it there is a way to check for fastboot connection and how fix it. I believe it will be easier if you do it that way
StevelyTM said:
I recently upgraded from a prebuilt to my own i5-6500 and 1070 build, and everything was going great until I needed to use fastboot to flash Pixelrom. To my surprise my device was not found. ADB works perfectly fine, and I've tried the regular SDK Dev Tools, the Universal ADB/Fastboot Drivers, and even the Pixelrom's inbuilt fastboot to no avail. I'm not really sure what could be causing this issue because I installed the SDK and drivers the same as my original computer ( Which I have to switch to now if I want to use fastboot ). I've tried multiple ports on my computer with no change.
Feel free to make some suggestions or ask for logs, etc.!
Click to expand...
Click to collapse
While in fastboot, go into device manager, and manually install an older version of the drivers, mine had a few versions to list from
On windows 10 disabled drivers usb vérification signed if it's necessary and try again