I am already rooted and on xposed using a win8.1 laptop. Followed the root guide by Heisenberg (sdk and adb drivers etc), however, on my desktop running windows 7 64 bit, I am not above to get my phone to show up with MTP. The option PTP however has no problem.
ADB is recognized in windows, but fastboot and adb are not recognized when in bootloader mode
Switching over to Win8.1, I have no such problems. Tried searching for win 7 updates and drivers but not much luck there, still cant get device manager to show the nexus 5x.
I prefer using the win7 as it is my main desktop versus the win8.1 which is a laptop that I leave mainly in the office.
Bump for this, Windows 7 users help!
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
alvinhochun said:
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
Click to expand...
Click to collapse
I tried this, now I can fastboot but no adb in bootloader mode. Nexus 5x device still not showing under computer drives.
queerquirks said:
I tried this, now I can fastboot but no adb in bootloader mode. Nexus 5x device still not showing under computer drives.
Click to expand...
Click to collapse
Well, you can't use adb in bootloader mode because that has never been a thing.
adb is available only in Android system and recovery mode.
All you can do in bootloader mode is to use fastboot to unlock bootloader, flash images and wipe partitions.
alvinhochun said:
Well, you can't use adb in bootloader mode because that has never been a thing.
adb is available only in Android system and recovery mode.
All you can do in bootloader mode is to use fastboot to unlock bootloader, flash images and wipe partitions.
Click to expand...
Click to collapse
Ah yes for the adb, i forgot about that. Tried mounting storage in twrp, device does not show up too.
I had a nexus 4 which showed up in win7 but not 8.1. Now nexus 5x is showing up in 8.1 but not 7, wth.
queerquirks said:
Ah yes for the adb, i forgot about that. Tried mounting storage in twrp, device does not show up too.
I had a nexus 4 which showed up in win7 but not 8.1. Now nexus 5x is showing up in 8.1 but not 7, wth.
Click to expand...
Click to collapse
Have you tried "uninstalling" the device in device manager when in TWRP too?
alvinhochun said:
Have you tried "uninstalling" the device in device manager when in TWRP too?
Click to expand...
Click to collapse
Ok just done it. Damm, at least 1 problem is solved
I followed your instruction and uninstalled the Google Adb Interface in device manager (didnt tried it at first as this was installed properly) and reinstalled it pointing the path to the sdk drivers, now I got fastboot in bootloader and adb in recovery respectively. In recovery mode, my nexus 5x shows up as a storage drive in my computer which allows file transfers However upon reboot, adb is not detected in android system and 5x not showing up in computer drive still.
queerquirks said:
Ok just done it. Damm, at least 1 problem is solved
I followed your instruction and uninstalled the Google Adb Interface in device manager (didnt tried it at first as this was installed properly) and reinstalled it pointing the path to the sdk drivers, now I got fastboot in bootloader and adb in recovery respectively. In recovery mode, my nexus 5x shows up as a storage drive in my computer which allows file transfers However upon reboot, adb is not detected in android system and 5x not showing up in computer drive still.
Click to expand...
Click to collapse
How about...
Have you tried "uninstalling" the device in device manager when in Android system? (Are you not noticing something... like... a pattern?)
alvinhochun said:
How about...
Have you tried "uninstalling" the device in device manager when in Android system? (Are you not noticing something... like... a pattern?)
Click to expand...
Click to collapse
What I had was
Android>Google Nexus ADB Interface , this works fine for adb and fastboot
Instead of Portable>Android, I had Unknown Devices with a exclamation instead hence the uninstall and reinstall would not show it as Portable android, only as unknown device.
Solved:
Solution for me would be clicking the notifications in the bottom left. saw that a Nexus 5x was still attached as a hardware even though the storage was not shown under computer.
- Uninstall the unknown device, 5x is still shown as attached in notifications
- Right-click the "safely remove hardware.."> open devices and printers and double click 5x
- Choose Update device drivers and point the path to the universal usb drivers ( android sdk)
5x mtp storage is now showing under computer drives but adb does not work in android system, only recovery. Good enough for me
Thanks alot for your help and time!!
alvinhochun said:
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
Click to expand...
Click to collapse
Just what I needed to do thanked
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.
Hello, as topic title, I have some issues with my nexus 7 2013 wifi model.
I installed official cyanogenmod 10.2. I would like to restore factory image, but i have some serious issues with adb drivers while usb debug is on.
I installed official google adb drivers, drivers from nexus root toolkit (not all toghether), but when i connect my nexus 7 to my pc (running windows 8 64 pro) there is no way to make him recognize my nexus, and all adb commands fail.
If I disable usb debugging and activate mtp, my pc recognizes the nexus 7, but still can't see the nexus itself in 'my computer'.
i need some help please.
You only need fastboot to flash the stock system images.
that does not completely solve my problem
19-2000 said:
that does not completely solve my problem
Click to expand...
Click to collapse
Restore the stock ROM to see if USB Debugging and ADB is working correctly.
19-2000 said:
If I disable usb debugging and activate mtp, my pc recognizes the nexus 7, but still can't see the nexus itself in 'my computer'.
i need some help please.
Click to expand...
Click to collapse
Are you saying your issue is you want adb and mtp to work at the same time and you have them working individually or are you saying you want to restore to factory images? If the latter, the previous poster already gave you the info you need.
Just boot into bootloader using Power Down, then press/hold Power+VolDown
sfhub said:
Are you saying your issue is you want adb and mtp to work at the same time and you have them working individually or are you saying you want to restore to factory images? If the latter, the previous poster already gave you the info you need.
Just boot into bootloader using Power Down, then press/hold Power+VolDown
Click to expand...
Click to collapse
no, not at the same time.
no, not just only to restore factory image
i need debug usb to push updated recovery
i need /would like mtp to access nexus storage for moviing things from/to pc without syncing via dropbox / transfering via usb otg because is a pain in the ass
::EDIT::
OK Problem Solved. Thanks to PKelly517 for pointing me in the right direction.
So I'm on Windows 10 and had all drivers updated. Device Manager showed Pixel C under portable devices and ADB worked BUT when in Fastboot mode it would not recognize the Pixel C and under Device Manager it showed up as Unknown Device. Trying to install drivers resulted in an error stating "The Third-Party INF Does Not Contain Digital Signature Information."
This is the steps I took to get Fastboot working.
1. Hold Shift and Restart PC.
2. In the following screen: Went to Advance Options > Startup Settings > Restart.
3. Upon restarting, chose the options "Disable Driver Signature Enforcement."
4. Reinstall drivers under Device Manager while in Fastboot mode.
Fastboot mode is recognized after that. Hopefully this could help anybody else having similar issues.
______________________________________________________________________________________________
I'm running on Android 7.0.0 NRD90R and I've searched this entire forum on ADB/Fastboot problems not working on the Pixel C and none of the threads seem to solve my problem. I can see my device in ADB but when I go into Fastboot mode the device is no longer recognized and commands cannot be issued.
I have installed all the updated drivers, the Pixel C comes up under Portable Devices in Device Manager, and when I use the Nexus Root Toolkit 2.1.9 to unlock the bootloader it gives me this:
adb devices
5C08000604 device
fastboot devices
Checking OEM Unlockable Status:
+ Status: Allowed
Checking ADB/FASTBOOT Connectivity
adb devices
5C08000604 device
fastboot devices
+ ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
Retrying.. Checking Fastboot Connectivity
fastboot devices
I've tried using SkipSoft Drivers and that too, doesn't recognize my device in Fastboot mode. Any help would be appreciated. I've spent hours trying to get Fastboot working and I've just about had it with this damn device.
@chob0,
Is your Android SDK up to date?
cam30era said:
@chob0,
Is your Android SDK up to date?
Click to expand...
Click to collapse
Yes, I've installed all the updated drivers including the Android SDK but still not recognized in Fastboot.
chob0 said:
Yes, I've installed all the updated drivers including the Android SDK but still not recognized in Fastboot.
Click to expand...
Click to collapse
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
cam30era said:
@chob0,
Is your Android SDK up to date?
Click to expand...
Click to collapse
pkelly517 said:
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
WOW THANK YOU SO MUCH! I can't believe it was something so simple. I checked device manager before and it had shown up as Pixel C but never while I was in Fastboot mode.
chob0 said:
WOW THANK YOU SO MUCH! I can't believe it was something so simple. I checked device manager before and it had shown up as Pixel C but never while I was in Fastboot mode.
Click to expand...
Click to collapse
Glad I could help.
The fact that it was JUST the Pixel C ONLY in fastboot was the weird part.
I think I spent more time trying to understand how to update the driver than I did discovering the problem. It looks like it was the opposite for you. Enjoy the weekend.
Sent from my Pixel C using Tapatalk
You saved me a lot of stress trying to figure this out. Thanks.
pkelly517 said:
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.
inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too
1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10
CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen
CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790
ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.
Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works
I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.
I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.
inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
MrHaPpY66 said:
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
Click to expand...
Click to collapse
Have you enabled oem unlocking from developer options?
I'm having the same problem. After going back to Oxygen OS (now 3.5.4) from MIUI 8 fastboot just doesn't work anymore. ABD works just fine (tried on Minimal ABD and Fastboot on Windows and ABD installed over Android Studio on Ubuntu. Fastboot did recognize the phone on Ubuntu but flashing TWRP resolved in a bootloop (tried the old and the new recovery image).
All drivers are installed on both Windows and Ubuntu (I even removed all drivers on Windows and added them again) and just to make sure everything gets installed I disabled driver signature verification on Windows, but as I said - still no luck.
Edit: Of course USB Debugging and OEM Unlocking is enabled (my bootloader is also unlocked since I already had tried out multiple roms)
Had the same Problem, Win10 is the Problem + the old OP Drivers + the new Update to Win10 etc.
Nothing worked, tryed everything. Created a Thread last week here also...
After that i created a new Partition and installed Win7 on it. All works fine, only thing is while Boot ur System u have to pick ur OS or it waits 30sec to boot up but thats ok.
Now i have Win10 for everything and i reboot to win7 for Fastboot/OP3
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Didnt tryed the last Tip.
KornY10 said:
Win10 is the Problem
Click to expand...
Click to collapse
Can't solve your problem, but OP3 fastboot does work in Windows 10. I did have to disable driver signature verification to install the driver in the first place, and you'll have to leave it off for the driver to stay functional, but it definitely works on Win 10.
I dont tryed ur Way, so yes after disable Driver sign. it works like u Said but i did not Test it.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
Same here
It's driving me crazy. I've updated from a rooted stock OS (incl TWRP) via full OTA directly to 3.2.7, which removed TWRP and root.
I now cannot enter a Fastboot mode which detects the USB connection. Thus I can't flash TWRP again and can't root my phone, making lots of apps unusable.
I've tried every suggestion on every thread but nothing works...
Sent from my ONEPLUS A3003 using Tapatalk
Also got kedacom on my device manager after automatic driver update but my phone still isn't recognised in adb devices, does everyone else's serial number show up?
You guys still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
Good that you found the solution..
Sent from my Xiaomi Mi 5 using XDA Labs
Well I didn't really solve the problem on win 10 so i just decided to use Ubuntu instead. Worked well
SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
I tried that too, but didn't work. What driver did you select in Device manager?
superiscch said:
I tried that too, but didn't work. What driver did you select in Device manager?
Click to expand...
Click to collapse
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
SgtIcetea said:
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
Click to expand...
Click to collapse
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good ?
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Yeah that one. After disabling the driver signature verification you have to re install it, when it's not disabled windows just doesn't install it although it says it does. After I disabled it Windows actually showed a completely new window during installation to install the driver properly
superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Man, had to just do it through my Ubuntu VM. Tried Win 10 Win 7, all gave me troubles.
Started Ubuntu, setup ADB and unlocked in a breeze
i have same problem