I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
download minimal ADB and Fastboot and turn on usb debugging from developer options. Also accept the popup on screen when you connect phone to PC after this
I have the same problem, have you succeeded ?
Thank you
I have the same issue with my Note 8T
i had the same problem with my note8. try to google around 1 hour. & that's the ones topic about it. unfortunately it has no answer poor me
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
Try downloading the Xiaomi unlocking tool, I didn't have problems with drivers, but I saw a messages about downloading drivers and "Driver already installed" for my phone within the application log.
Give that a try!
But problem with Note 8. I don't remember when it started, but on crDroid 6 it definitely worked.
After that I notice in device manager what it determinate as some SAMSUNG Adb Device with Clock World driver. I had ADB Universal Driver installed, after uninstalled everything start work fine.
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
scarlos89 said:
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
Click to expand...
Click to collapse
Use W7
W10 always have problems with some driver signature
loopypalm said:
Use W7
W10 always have problems with some driver signature
Click to expand...
Click to collapse
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
scarlos89 said:
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
Click to expand...
Click to collapse
you have to wait
Related
Hi friends, I follow you every day and I love you!
I have a very big problem with my Note 10.1 2014 edition, that I can't solve. When I connect it to the computer (I tried 5 computers with different windows versions) it only charge the battery, but it's not recognised by kies or Odin. In Windows 8.1 it is shown as "unrecognised usb driver", in windows 7 too and it isn't seen at all in windows xp. I tried reinstalling kies, factory reset the tab, but without success. What can I do? I'm thinking about sending it in assistance.
Thank you and excuse me for my bad English!
Rick080194 said:
Hi friends, I follow you every day and I love you!
I have a very big problem with my Note 10.1 2014 edition, that I can't solve. When I connect it to the computer (I tried 5 computers with different windows versions) it only charge the battery, but it's not recognised by kies or Odin. In Windows 8.1 it is shown as "unrecognised usb driver", in windows 7 too and it isn't seen at all in windows xp. I tried reinstalling kies, factory reset the tab, but without success. What can I do? I'm thinking about sending it in assistance.
Thank you and excuse me for my bad English!
Click to expand...
Click to collapse
When you plug in the tablet does it ask you (on the tablet screen) if you want to connect as a media device or charge only? Check your developer settings that you don't have debug mode set.
No, it doesnt ask anything...
Rick080194 said:
No, it doesnt ask anything...
Click to expand...
Click to collapse
Have you confirmed that you are NOT in USB debug mode?
Also make sure drivers are installed on computer. Sometimes it can take a few minutes to install drivers. When I first put mine on computer at work I had to manually install driver's.
mikep2323 said:
Also make sure drivers are installed on computer. Sometimes it can take a few minutes to install drivers. When I first put mine on computer at work I had to manually install driver's.
Click to expand...
Click to collapse
Yes, i reinstalled drivers through kies application, but nothing
I have the same issue. I have been searching for a fix. I want to root but PC will not recognize it or pop up with anything, tablet only charges nothing else up on tablet. I have search and searched but nothing. I am also running windows 8.1.
*****
I have now tried a 2nd PC using all USB plugs. Installed Kies nothing, uninstalled and installed only driver still nothing. Clicked version 6 times on build number to get Developer options. I enabled USB debugging.
I am starting to get upset, I just want to Root for a few functions. It shouldn't be this difficult.
Anyone have any thoughts? It could be a simple thing we are over looking.
Change cable
Also try rebooting your PC .
My laptop stops finding USB devices after about 2 weeks.
Solved
I solved selling the tablet for 430$!
For those who are still having the problem, this solution worked for me on Windows 7.
I installed the first "Download" Link from here.
http://forum.xda-developers.com/showthread.php?t=961956
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
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Evnul000 said:
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Click to expand...
Click to collapse
Windows drivers 100%.
null0seven said:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Click to expand...
Click to collapse
I have tried it on both my PC and laptop with both windows 10. Does not work. My PC also has windows 7 still seems to not work. Are there any other drivers i might be missing?
i have also done some research that you should update your drivers from device manager. I dont see anything related to my device. i went to portable devices nothing and i dont have a other devices section in device manager. Any help?
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
null0seven said:
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
Click to expand...
Click to collapse
i am on the latest twrp. will blu-spark help fix it?
ive also found out theres no kedcom driver when i go to fastboot. i even reinstalled adb drivers to insure its there but it does not pop up.
You'll need to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
I once have kind of youre problem connecting to my laptop (win.10). But, at work, on that laptop, connection was ok (win.7).
I reinstal windows 10 and connection works fine, since.
I allways use latest TWRP & version of rom. I can't tell for sure what it's goin on with youre phone.
If i was in youre situation i format my phone (this will erase ALL in youre phone). And if PC still does not see the phone reinstall windows.
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
dentman said:
You'll bed to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
Click to expand...
Click to collapse
What are the driver links if you have? I already installed the OnePlus drivers.
ninjeratu said:
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
Click to expand...
Click to collapse
I used the OnePlus cable and another cable.
Driver issues win 10
Find the excellent tutorial here on drivers.
For some reason my phone didn't show up but was able to receive commands. It was frustrating because I wanted to use the all in one XDA product but couldn't.
Even if you installed drivers they can be broken!
Do drivers from scratch per xda tutorial. Don't forget reboot!
Try different cables and usb ports! My front ones never seem to work!
Don't just try fastboot commands also try adb. Like I said mine wasn't seen properly yet it took the commands.
Unless your windows is a years old install it shouldn't require reinstall.
Factory phone reset might help.
Best of luck!
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Anyone?
no one?
bigd19888 said:
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Click to expand...
Click to collapse
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have minimal adb and fastboot installed
device is h811 20v
bootloader is already unlocked
and yes I'm using LGMobileDriver_WHQL_Ver_4.2.0
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
RuedasLocas said:
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
Click to expand...
Click to collapse
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
Don't allow Windows 10 to update your drivers - you can set that up in Windows. Google it for the how-to.
bigd19888 said:
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
Click to expand...
Click to collapse
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
RuedasLocas said:
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
Click to expand...
Click to collapse
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Your device should be seen as "LGE Android Phone" (if your lg drivers are good).
Now gonna be tricky because my OS is in Portuguese, I don''t know exactly the path name in English... use your imagination
Connect the device on a USB 2 Port !!!
In windows device manager, select "update driver", "search software on the computer", "allow to choose from a list of avalable drivers". unmark the "compatible hardware" and find on the list the needed drivers. If the "LGE" drivers don't work, try to download Universal ADB Drivers, maybe it works.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
I'm thinking it could be a corrupted LG driver. Download another from the LG US site, ONLY. Uninstall the one you have installed now, reboot and install the newly downloaded one. Then connect your phone and see if it is recognized and shown correctly in Windows Device Manager. Also, in adb type lsusb and see if the phone is listed in the output.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Boss, no need to struggle with this ADB anymore.. there is a tool called FWUL which was created for people who have driver issues... Check it out here:
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
:good:
Sorry if this is the wrong thread.
Hello guys, I have a Redmi Note 5 (Global Version) with Snapdragon 636, and this phone is really amazing. I'd like however to unlock its booloader so I can install Pixel Experience on it, as I'd like to use other roms than MIUI. The issue is, well, I can't.
Something really strange happens: if I connect my phone via USB 2.0 to my computer, it is recognized as usual. It appears in Device Manager, is recognized by ADB, no problem. Then I reboot in fastboot mode and the device is still there. However, the EXACT moment I open Mi Unlock Tool, without clicking anything (Agree or logging in to my mi account) the phone is instantly disconnected and the "Press any key to shutdown" message appears on the top-left of my phone's screen.
Stuff I've tried:
- made sure OEM unlocking and USB debugging are on
- installed Mi Unlock tool in C:
- installed the ADB drivers in C:/Program Files
- disabled integrity checks from CMD
- installed and checked the MiUSBDriver umpteen times
- used 4 different versions of Mi Unlock Tool (1.0, 2.2, 2.3, and 3.3 - 1.0 halts at 50%, the other 3 won't detect my phone at all)
- made sure the device is bound to my Mi Account
I've tried using Hexerus' guide here (post #18) and everything seems to work fine, until step 6 when my phone instantly disconnects when opening Mi Unlock Tool.
Do you guys have any ideas? Thanks.
use usb 2.0 cable and port
devcon69 said:
use usb 2.0 cable and port
Click to expand...
Click to collapse
Used USB 2.0, didn't work
Happened with me before, and I looked Google and found some solutions like installing the drivers again and using old miunlock tool and using different USB Socket however, none of theme worked,
Next day I opened the laptop to try again and suddenly it worked!
I didn't know what exactly fixed it
After the 720 hours period, I have spent literally weeks of trying to unlock my device's bootloader and what I would add is to switch between computers. I'm running Windows 10 on my room computer and all I had with MiUnlock were errors such as device disconnecting once in fastboot, "Couldn't unlock" messages, chinese characters... Until I decided to use my 2005 Windows 7 desktop and wow !, device unlocked at first try ! No need any other trick
just uninstall Previous drivers or use Windows 7 PC,with latest drivers of ADB ,i also faced same problem:angel: