Related
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
kinglime said:
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
Click to expand...
Click to collapse
I just experienced the exact same issue following the same steps on my laptop also running 8.1
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
gzbrambila said:
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
megaorange1 said:
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
Click to expand...
Click to collapse
From all of my research, you're the first person I've heard of having it working. Any specific drivers used? I'm very curious (currently, I have to use a backup machine to push TWRP updates to my VZW One)
Same thing here. 8.1 broke fastboot. Is this a Microsoft problem specifically because if it is I seriously doubt they will be in a hurry to patch it.
Sent from my HTC One using Tapatalk
I have found out something based on the VMware experience. Can somebody try it out and report back???
I feel that the fastboot problem in windows 8.1 is related to the USB port.
For those people that having problem, are you guys using USB 2.0??? If yes do you have USB 3.0 port in your computer??? The real problem maybe is that fastboot only works with USB 3.0 but not USB 2.0 in windows 8.1...
I tried both USB types, and half a dozen drivers and workarounds, and nothing.
I don't believe the dude above got it working. He is probably thinking Win 8, not 8.1. I have it working on 8.
Flash Image GUI will probably do everything you need to do in fastboot without the need for a computer. I just threw 8.1 on one of my extra PC's, I'll see if I can get the drivers going. I feel like this was answered in another thread though, I think it is in the rumrunner thread...
Just another reason why 8 is bad
cgskook said:
Just another reason why 8 is bad
Click to expand...
Click to collapse
fastboot was working on windows 8 and adb !!!
so the update win 8.1 have change sometihng but the question is what
and i try different drivers (from google,intelandroiddrv) and noting work
why have micro change something with drivers pffffff
kaverorzi said:
yep,definitely not working on Win8.1x64
Rooted a couple weeks ago on Win8x64, no issues.
Only noticed this issue today after I couldn't flash a different splash screen for my NuSenseOne.
Click to expand...
Click to collapse
I don't have the link on hand but there is a driver update to support 8.1 I have it working fine.
Sent from my HTC6500LVW using Tapatalk
i just used http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ and fastboot works on a 3.0 port on 8.1
I've just had this problem last week, and now got a solution...
Hi guys,
For anyone interested, due to something DreamerTKM said - I tried both USB 2 & USB 3 sockets on my Dell L701X laptop and both failed:
ERROR: Unknown USB Device (Device Failed Enumeration)
I did a clean install of Win 8.1 Pro and it still failed...
Anyway, I was using Windows 8.1 Pro default drivers for my system when this issue came up last week - default as in Microsoft's own out of the box drivers (drivers on the install DVD and Windows Updates) for my CPU chipset, USB chipset, etc... - my entire system (except for my nVidia graphic card!)
My laptop is now a few years old and my official "Dell" CPU chipset drivers are not compatible with Win 8.1, so I need to rely on Microsoft for these, but my USB 3 originally had Dell supplied "Renesas USB 3" drivers which I hadn't installed or even thought about installing as my USB 3 socket worked - and worked well...
...anyway, after installing the original Renesas USB 3 drivers the fastboot commands work once plugged into a USB 3 socket! USB 2 still wouldn't work though, but now my Win 8.1 laptop can do fastboot commands through a USB 3 socket.
I understand not everyone will have a Dell L701X laptop but the moral here is before blaming Microsoft and their Windows 8.1 O/S (which is truly awesome), try installing the correct drivers first!
DreamerTKM - thank you for putting me on the correct path with this!
Hopefully this post may help some of you!
solution
guyz if u r working on win8.1 just plug it in ur usb 3.0 then it will wrk...if u put in usb 2.0 it wont!
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
wex28 said:
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
Click to expand...
Click to collapse
Full fastboot and ADB support is available in windows 8.
Watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
morrowa2 said:
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
Click to expand...
Click to collapse
Also, there is this: http://forum.xda-developers.com/showthread.php?t=2703585
Has anybody gotten the Sony's official usb drivers to work? Its somewhat mandatory for xperifix et all.
I tried it on 2 completely different machines.
On win7 x64 box the driver complains about Error 10 - This device cannot start.
On a win10 enterprise thinkpad the error is similar:
"This device cannot start. (Code 10)
The specified request is not a valid operation for the target device."
I am starting to suspect that the drivers are faulty. FWIW the thinkpad has NEVER seen *ANY* adb/android/sony drivers before.
This is the "Sony sa0118 ADB Interface Driver" btw. Installed as a legacy device as per Sony's instructions. Driver is already not working before a device is connected. Device is subsequently also not recognized. Device works perfectly fine in flash mode on my Linux notebook, just not both windows boxes Ive tried (sadly Windows is required for Xperifix)
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
juandiazmora said:
You use the drivers that comes with flash tool? Those are working for me without any trouble on Win10
Click to expand...
Click to collapse
tried these and they got me a little further - but not very. On first connect of the xz2c in "blue" mode Windows said something along the lines of configuring new device: Android. So far so good. Then started xperifix, which found the device and started to get device information during which it crashed (program got stuck, no .NET exceptions or anything). Now even 2 reboots later the phone is no longer recognized, I assume xperifix somehow borked up the fastboot drivers?
PS: the constant more often than not non-working recaptchas are getting a little annoying..
The drivers have to be installed in testmode on Windows 8-10. In Windows 7 it should work "out-of-the-box". And yes, I know I'm answering to one year old question, but it could be helpfull to someone one day. Maybe.
Ok - I'm looking for a top to bottom guide on how to get this working with my phone.
I'm wanting to install a new ROM on it to hopefully breath a new lease of life into my phone.
As I understand it, to do this I need to unlock the bootloader - and so on - and to do this using the official method I need to use the Android Debug Bridge.
I've downloaded the Android SDK - and run ADB.exe - but when I do "adb devices" nothing is returned.
I've tried assorted cables - assorted USB drivers and so on - but nothing seems to work.
So - I want to start from scratch - what do I need to do, to get a blank slate, to try again to do this.
What drivers do I need to uninstall to start again - and what should the process be, top to bottom to do this?
I assume the SDK files I downloaded is fine and working. (I've tried doing this on two different PCs - both Windows 10 though) and had the same results so I'm assuming the SDK is ok.
I've got a european H815 - which was updated to the most recent update available for the phone.
I've got Dev mode initiated on the phone with USB Debugging ticked.
Is there a specific order to do things?
Is there a specific order to initiating debugging so that it "catches"?
Does it matter whether it's on MTP or PTP or USB Tethering?
Any help would be greatly appreciated.
I think once I get this ADB thing sorted out, I should be ok, as I managed, back in the day to install several different ROMs on my old HTC Desire - and I never had this issue with that phone.
Please help!!!
PS - my PC is totally up to date with Win 10 updates too (which may well be a problem in itself)
So - I have tried the following LG Driver packages and none seem to work.
LGMobileDriver_WHQL_Ver_4.0.4.exe
LGMobileDriver_WHQL_Ver_4.4.2.exe
LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1.zip
UniversalAdbDriverSetup.msi
When I "Inspect Devices" via Chrome - the phone shows up ok too.
The phone is recognised as being attached to the PC and can be seen on the PC in the various modes (MTP, PTP, Midi and when USB tethered I think).
When the phone is connected by USB and a disable and re-enable USB debugging, I am asked if the PC cccess my phone data and I click "Allow".
I'm stumped.
Had another go on a different machine - and again the same things were happening.
Ditched another driver - not even sure if I even installed a different driver - I wasn't taking notes thinking that nothing was going to work anyway.
It just would not catch on the ADB.
But then I tried switching between modes whilst connected and somehow it worked!!!!!
Bish bash bosh - now I've got an unlocked bootloader!!!
Now for the next steps to getting some custom ROMs installed.
Note: I think the biggest issue was the screen asking to always trust the computer - when I did the bootloader unlock - it wiped everything (which I'd forgotten about!!!).
Anyway - as it was like plugging a new phone when I just connected to my home PC - it wanted to install PC drivers, and when I activated debugging, it flashed up the screen with a certificate??? ie a load of letters and numbers - asking if I want to trust the computer. (I can't remember the proper name for the screen - but have seen some people refer to it on other posts on here).
I said yes - and bang - first try - ADB works.
My advice - for anyone trying to do something similar and having problems with ADB - get everything backed up to begin with - and then do a factory reset.
That'll most likely reset stuff on the phone, and make things smoother...
Hi all,
I purchased a gemini wifi recently, but a 4g version arrived! I'm now trying to flash Linux on there, but I cannot get the flash tool to do anything.
I'm pretty sure that this is a driver issue, but I'm not sure what to do about it. I've tried windows 11 and 10, as well as ubuntu 20.04 to flash this thing and nothing is working.
On the windows 11 host I even disabled memory protection to allow the drivers to work correctly, but that made no difference.
Following the guides on planet computer, it's not clear what state the device should be in, but I've tried normally booted into android as well as in recovery mode (booted with Esc and side button depressed on boot}
What am I missing here? Does flashing this device just no longer work?
Thanks in advance for your help!
it still works presuming you are referring to this guide: https://support.planetcom.co.uk/index.php/Linux_Flashing_Guide
I unfortunately don't think I am able to help you debug the situation from the information you provided.
I am not sure where most of the users congregate, but I have seen some sporadic recent activity here: https://www.oesf.org/forum/index.php?board=192.0
From my own experience, windows 7 and windows 10 have worked flawlessly, ubuntu worked for me in the past, but had trouble recently. win7 and win10 in virtualbox requires delicate usb device setup adding device during gemini reboot, and still gives some trouble.
I haven seen any updates or security patches from planet on neither android nor debian, so got myself a sailfish X license to support their development, it looks like a lot of updates (most recently yesterday: https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0-72/ )
good luck
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Try on Windows
ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.
limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.
limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...
simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.
Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.
TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.