So, I have found a couple other posts on this issue but none of their solutions have worked for me.
Ill start with the set up I am currently on:
-Stock Official Android N (US Unlocked)
-Firmware 2.28.617.8
-T-Mobile with CID changed to run US unlocked
-S-off and unlocked
-Using windows 10 with ABD Fast boot file (not sdk)
So I have the drivers installed. Originally I was just using the HTC sync software drivers but moved to drivers I found in a forum post here, which unfortunately did not work.
USB Debug is checked.
My phone shows as connected and I can run ADB Devices and see it in the list until I ADB reboot bootloader. Once it is booted into bootloader ADB no longer sees the phone. Checking device manager shows that the phone is connected with no exclamation mark or question mark next to it.
I have restarted and reinstalled several times with no luck. I even run a usb bootable copy of Linux Mint hoping that it may just be an MS issue but I have the same problem on Linux whether I sudo or not.
Since I have had the phone ADB has worked whether in fastboot or not. It was only until I ran the official RUU and upgraded to Android N that it has stopped working. If I am not mistaken, in MM there was a popup when you had USB Debug enabled and connected to a pc that asked if you wanted to use that pc (or something like that). I am not seeing that pop in N.
Any help would be greatly appreciated as I would really like to get twrp installed and rooted.
Thanks all.
I have spent the past couple hours fiddling around with this and thought I would add and update.
I downloaded and installed Android SDK, updating everything and adding the Google USB drivers. Unfortunately this did not work. Same result.
I did however just find that if I go to the stock recovery and select the Apply update from ADB option, the device is recognized again in my cmd window.
Am I missing something. Is there a new procedure for flashing things like twrp with command lines? All the forums still show Fastboot as the method.
Anyway, that is it for my feeble brain for the night.
Sometimes it helps to use the usbdeview tool. It removes the link to drivers and gives you a clean start. Worked earlier for me. File is attached.
@Ludolf71
I gave that a try but it doesn't seem to help. Looking through the list of drivers there doesn't seem to be any driver conflicts and the only instances that show up on the list relating to my phone are the vendor drivers and the port that the phone is on.
At this point I am lost. I have spent hours reading forums and searching around for a solution. I am not sure what might have changed between running MM and updating to the current HTC RUU. Prior to installing the current RUU everything worked fine.
Looking though dev options there is an option to revoke USB debugging authorizations, is there a way to see the list of authorized devices? Also, I swear that in MM when I had debug on I had to authorize my pc when I plugged it in the first time after a fresh flash. Is that not the case anymore or is that option somewhere hidden that I am missing?
Has anyone put together an adb zip specific to the HTC 10 and the current firmware? Do to changes in the Android N firmware could this be the cause?
I tried Andoid SDK last night but I have to admit I am not very well versed in their software so I may not done it correctly. I have been modding and flashing custom rom since the poorly name MyTouch but have so far gotten by without having to use Google software suite.
Thanks all for the help.
Tried installing the HTC Sync Manager? That shall provide you with the correct drivers.
Yeah, I have installed and reinstalled the Sync manager several times. Like I said the phone is recognized using ADB devices while booted to OS but the second I adb reboot bootloader it is no longer seen.
I keep coming back to authorizations and i think this may be the issue. I see the option to revoke but I am not getting any options to authorize the PC I am using.
Solved: I was using the wrong command line as pointed out by xunholyx in another thread. Thanks @Ludolf71 for helping as well. Felling pretty dumb about this one
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
---------- Post added at 06:40 PM ---------- Previous post was at 06:40 PM ----------
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
Related
Some video tutorials to help out n00bs as well as confused members:
How to get working ADB and Fastboot, as well as drivers for Windows 8.1 64 bit:
Video embed not working? Click here for a direct link!
How to lock the bootloader and go S-ON:
Video embed not working? Click here for a direct link!
How to go S-OFF and unlock the bootloader with Firewater S-OFF:
Video embed not working? Click here for a direct link!
You are free to link to any of these tutorials or to this thread.
Enjoy these tutorials and leave a reply if you have any suggestions for future guides.
Good to see you over here on the M7 doing your thing like the old days wolf. Keep it up.:good:
synisterwolf said:
Good to see you over here on the M7 doing your thing like the old days wolf. Keep it up.:good:
Click to expand...
Click to collapse
Been so busy in the past few months or so that I couldn't do my helpful stuff. Now I have more free time.
Awesome tutorials! this is where I'm stuck at the moment.
I went as far as to restore my computer to Windows 7 and start over erasing everything. I've tried different USB cables. I know it won't work on my USB 3, i Have one USB 2, I believe I have the drivers installed. I even went as far as to download and install Cyanogenmod on my Verizon HTC One. Enable root, Apps and ADB. allow USB Debugging. I also uninstalled HTC Sync, because another XDA guy mentioned that it can get in the way of things. here is where i am stuck at when attempting to lock my Boot loader.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
So that is where I am stuck. I see my phone reads fastboot usb, and it will do other commands, so i know it is connected, just not recognizing it? Dumb question, but if I RUU to say 4.2.2, because my phone is able to do that, can I do a software update and install 4.4.2, would that LOCK my bootloader and get me on the right software, so that all i have to do is give the command to go from S-Off to S-On? or will that command even work for me because i cant get the command to even open the shell? Also, is there a way to manually install a driver? I go to my device manager in control panel, and I'm not seeing anything that says Other Devices > One.(UPDATE; I found where HTC is in device manager, I tried updating the driver manually, it say's that driver is already up to date.) and I've gone to the start menu > Run > and ran a command to allow me to install unknown drivers to Windows 7. I have also unplugged anything usb on my laptop, including my wireless mouse.
I've been trying really hard to get my phone back to stock to return back to HTC. Probably a solid 10 to 12 hours last night and this morning working on it. lol
Update: Am I supposed to do anything with Android SDK?
Update 2: I can flash Decripted RUU running adb on CMD with commands and have HTC's Official software running with no problem and it recognizes my phone plugged in. So i went back to Cyanogenmod for now. but for whatever reason, adb device and adb shell are not recognizing my phone that is plugged in
Update 3. Re-installed HTC Sync and installed HTC Sync Manager for the fun of it, and now daemon doesn't even show up when doing command adb devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
Update 4: I swear, when we get this working, I'm gonna send whoever a little kickback through Pay pal for helping out with my issues.lol. I feel that maybe it could be my laptop, I'll have to try my 10 year old toshiba.
BygSii said:
Awesome tutorials! this is where I'm stuck at the moment.
I went as far as to restore my computer to Windows 7 and start over erasing everything. I've tried different USB cables. I know it won't work on my USB 3, i Have one USB 2, I believe I have the drivers installed. I even went as far as to download and install Cyanogenmod on my Verizon HTC One. Enable root, Apps and ADB. allow USB Debugging. I also uninstalled HTC Sync, because another XDA guy mentioned that it can get in the way of things. here is where i am stuck at when attempting to lock my Boot loader.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
So that is where I am stuck. I see my phone reads fastboot usb, and it will do other commands, so i know it is connected, just not recognizing it? Dumb question, but if I RUU to say 4.2.2, because my phone is able to do that, can I do a software update and install 4.4.2, would that LOCK my bootloader and get me on the right software, so that all i have to do is give the command to go from S-Off to S-On? or will that command even work for me because i cant get the command to even open the shell? Also, is there a way to manually install a driver? I go to my device manager in control panel, and I'm not seeing anything that says Other Devices > One.(UPDATE; I found where HTC is in device manager, I tried updating the driver manually, it say's that driver is already up to date.) and I've gone to the start menu > Run > and ran a command to allow me to install unknown drivers to Windows 7. I have also unplugged anything usb on my laptop, including my wireless mouse.
I've been trying really hard to get my phone back to stock to return back to HTC. Probably a solid 10 to 12 hours last night and this morning working on it. lol
Update: Am I supposed to do anything with Android SDK?
Update 2: I can flash Decripted RUU running adb on CMD with commands and have HTC's Official software running with no problem and it recognizes my phone plugged in. So i went back to Cyanogenmod for now. but for whatever reason, adb device and adb shell are not recognizing my phone that is plugged in
Update 3. Re-installed HTC Sync and installed HTC Sync Manager for the fun of it, and now daemon doesn't even show up when doing command adb devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
Uninstall the phone in device manager. Disconnect the phone. Disable windows updates to prevent it from auto installing a generic windows driver. Then plug the phone back in and try to manually install the driver from the video.
Okay. I'll try that out here in a little bit. Another thing I found to be odd, is that my OS is showing up as blank. I hope it will show the correct OS that I'm on, when I get far enough to flash an RUU.
Success! I had to disable updates, even after that, it still would update when plugged in. So I uninstalled updates. Then, I had to catch the device drivers before updating by cancelling them. Installed drivers like in the video, followed steps, everything is a success! this post should be stickied, but that's just me. Good job!
BygSii said:
Success! I had to disable updates, even after that, it still would update when plugged in. So I uninstalled updates. Then, I had to catch the device drivers before updating by cancelling them. Installed drivers like in the video, followed steps, everything is a success! this post should be stickied, but that's just me. Good job!
Click to expand...
Click to collapse
Glad you got it working.
Windows update is nice, but it is really annoying when you want to manually install a better driver.
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
wellsheit said:
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
Click to expand...
Click to collapse
It should work. No promises though.
Sticky?
wellsheit said:
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
Click to expand...
Click to collapse
I rooted and got S-Off on Win 8.1. I was stock 4.4.2 at the time and never rooted a smartphone before. The tutorial for the driver was spot on. As for the other 2 tutorials, I didn't use them as I found the rest of the process to be pretty straight forward (using WeakSauce & Firewater to root and get S-OFF).
Vids now viewable in OP.
Link added to roll up in Development
dagrx8 said:
I rooted and got S-Off on Win 8.1. I was stock 4.4.2 at the time and never rooted a smartphone before. The tutorial for the driver was spot on. As for the other 2 tutorials, I didn't use them as I found the rest of the process to be pretty straight forward (using WeakSauce & Firewater to root and get S-OFF).
Click to expand...
Click to collapse
Excellent to hear. Been waiting for this to get sorted out. Will report back when I get time to sit down and run through it all.
I can confirm it works on win 8, got my surface pro adb and fastbooting like a baws in minutes. As above poster mentioned, you either have to uninstall and prevent auto device installation, or if you find it in device manager you can force update the driver , you may have to take the extra step to "Have Disk", manually select the androidusb.inf file from unpacked drivers, then select My HTC
Sent from my HTC6500LVW using Tapatalk
Files are missing from the first video, could you reupload or post another link for the driver?
nekubg said:
Files are missing from the first video, could you reupload or post another link for the driver?
Click to expand...
Click to collapse
Updated.
Thanks for the fast reply!
I am having issues, after following the steps. In ROM and recovery it shows up in ADB devices and device manager. However in bootloader it shows device manager, but not in ADB Devices. Tried multiple cables, including the original. Any ideas?
Plauges said:
I am having issues, after following the steps. In ROM and recovery it shows up in ADB devices and device manager. However in bootloader it shows device manager, but not in ADB Devices. Tried multiple cables, including the original. Any ideas?
Click to expand...
Click to collapse
What version of Windows?
If it is Windows 8 you need to make sure that you installed the drivers while signature enforcement was off. I have also posted an updated video with new drivers, give it a try.
Got my USB-C to USB-A cable today, so I'd like to unlock the bootloader on my Pixel C. The problem is, when I hook it up to my PC, it does recognize it in Windows as the Pixel C - I can see it and browse through the drive and folders - but when I try to run an ADB Devices command, it does not see anything.
I think I have all the latest drivers - I grabbed the Marshmallow and USB drivers from the links on this page:
http://www.androidbeat.com/2015/10/how-to-unlock-nexus-6p-bootloader/
But I'm still not getting anything. I've tried using different USB ports on my computer, both USB 2 and USB 3 ports (although I've always had success with the USB 2 ports in the past), but still no dice. I did notice when I go to Device Manager, that there is an ADB Interface Device that is unrecognized, but I've tried updating the drivers (no luck), as well as uninstalling and then rescanning for hardware changes (just get the same unrecognized ADB device as I started with).
For reference sake, I'm using a Windows 10 Pro 64bit PC.
I'm at a loss as to what to do, so any help I can get here would be greatly appreciated.
Nevermind, I was able to get it straightened out. Used the download/instructions found on this XDA thread to get everything squared away:
http://forum.xda-developers.com/showthread.php?t=2588979
Device is now unlocked and I can go ahead and set it up properly while waiting for root access to become available.
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
regime2008 said:
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
Click to expand...
Click to collapse
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Geese1 said:
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Click to expand...
Click to collapse
Funny thing is, I have tried all of those steps, and still no luck. I have deleted all of the drivers completely. Reinstalled them, and still get code 10. It seems several people are getting this issue in the thread you linked in your second post.
My Pixel C got an invalid pin error so tried to do a factory reset through android recovery but that ended to a bootloop and the tablet is simply useless. Thought I'd try to install OS again see if that would bring it back but I can't even get it recognised in the pc. I've put it in fastboot mode and it won't even acknowledge I've connected anything. Nothing shows up on Device Manager. Am I doing something wrong here? I'm out of ideas
OMG... finally got it working. I installed HTC Sync Manager again and decided to run it and see what happened. While it was scanning for music on my computer windows installed the drivers. More than once it seems.
Now I need to know if I can uninstall Sync Manager but keep the drivers. It keeps opening up and I don't know if it's safe to flash recovery if that's going to happen.
Flashed TWRP successfully and made my back up.
--------------------------
OLD NEWS BELOW:
Here's the deal... I just flashed the 3.x RUU so I'm stock but I'm unlocked and s-off. I'm trying to flash TWRP via fastboot so I can get a custom ROM on here. I turned on USB debugging on the phone.
First of all, that stupid HTC Sync manager keeps trying to install and I don't know how to stop it. Googling has not helped with this.
Second, I can't get the device to be seen in adb, or at least not online. I seem to be going backwards with all the steps I have taken to try to get this to happen.
I'm using dotatt's adb package. When I attach the phone while it is off windows looks for drivers and usually fails. One time it seemed to work and adb saw the device but then when it boots up that Sync Manager wants to install so I decline. Then my phone was seen but listed as offline.
So I tried uninstalling all HTC things on my computer and reattach phone. Didn't help anything. I tried installing the HTC Sync then uninstalling it thinking I would get the drivers, no go.
I grabbed these Universal ADB drivers http://www.koushikdutta.com/post/universal-adb-driver linked to from a twrp page here https://twrp.me/devices/htconem9.html
Nothing lists as a device in ADB at all now.
My windows Device Manager shows "Unkown Device" under "Other Devices" with no driver listed.
Tried this:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
http://forum.xda-developers.com/showthread.php?t=2588979
Still not working.
ACK! Can anyone help me out?
Is there still an issue with using usb 3.0 ports? I feel like I heard something about that way back when.
That's pretty much how it's always been. Best way to get the appropriate drivers is to install HTC sync, let it do its thing, reboot the PC, then uninstall HTC sync without removing the drivers. To the best of my knowledge, been that way since at least the days of the Incredible, if not before. At least it's how I've always gotten the drivers to use adb.
Yeah I remember that from the Rezound, which is why I did that, but it seems that the drivers didn't actually get installed this time until I let HTC Sync Manager start running and scanning my computer. That's when I saw the message that it was looking for drivers and twice it told me it installed them.
I would think it would have them installed during the 'actual' installation process. So I guess I just uninstalled prematurely. Seems weird. But it's working now so all good.
So when I originally got my OP3 and rooted it, installed a recovery and installed SuperSu, I had basically no problems. Installed drivers I found on here and never had an issue. Today I found a guide on the OP forums to disable doze which I apparently need to do since certain notifications aren't working right. I plugged my phone in and tried to follow the instructions, listed here under push notification issues
https://forums.oneplus.net/threads/...3-guide-solutions-e-t-c.448097/#post-14886949
When typing in adb devices, my device shows offline. I have done numerous things to try and fix the issue which I will try to lay out here. Initially I didn't install adb or the drivers as the guide suggests, since I had already done that - but after things not working I did try that and that didn't help. Still receive the "offline" next to my serial number device. The device works fine, and I can see it and transfer files to it just fine in the MTP mode. I have also tried to "revoke" permissions like described in the youtube guide I found here https://www.youtube.com/watch?v=eSApv8NXqD4
However that didn't work either. I should note that even after revoking permissions and turning usb debugging on and off again, the phone never asks me to authorize my computer as it does in that guide. In fact I don't believe it ever asked me to authorize my computer even when I first got the device. I don't know if that is part of the issue or not. I have also used a different adb version since somewhere I found that you needed to use the newest version. The version I had was 1.32 and I found the newest here on the forums here http://forum.xda-developers.com/showthread.php?t=2317790 that it was 1.4 as the newest. That adb returns the same results.
I should also note that the guide I linked from oneplus never actually tells me to put the phone into fastboot mode to execute the command, so I tried it initially booted up, and then in fastboot thinking it was supposed to be executed there, however in fastboot mode the phone is not seen at all. adb devices returns nothing, and booted it returns offline mode. Please help me
Nobody?
Have you tried some of the suggestions on https://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands? I'm not really sure what the situation is like on Windows but first I'd ensure you've installed the latest official Android SDK just to rule out an issue with the version of ADB you're using. You could also try using ADB over WiFi.
Apart from that, you can probably get by without ADB for now. Just run the commands in a terminal emulator on the device and/or create an init script.
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186
Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!
ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.
Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.
I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.
It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs