Database Info

[Q] Padlock icon at bottom of Google screen at start up?

Hello:
I sent my NEXUS in to SAMSUNG for a touch screen non-responsive on the left side issue. The tech stated there were no problems with my NEXUS S!
Upon turning it on, there is a padlock on the botton of the Google splash screen.
I called Samsung and the "level 3" tech said that my phone was now locked to T-mobile. I though that was BS.
Anyway what is it and, can I get it back to normal? My wife has the same phone and here does not have any problems so far.
I've attached a pic of the screen that shows the padlock. Thanks for the help.
Chiefdroid

that means your phone is unlocked as far as I know. I did my first unlocking and rooting of my nexus last night. When I went through the unlocking process, the "unlocked padlock" started to appear on my startup. If you hold "volume up" and the power button and turn the phone on. it should say unlocked on the fastboot screen...

You have unlocked the bootloader my young Jedi.
Sent from my Nexus S using XDA App

yup, unlocked bootloader.
thats not a bad thing, its a wonderful thing!

lol you rooted your phone and unlocked the bootloader. that is what that lock symbol means. did you forget, or not do this on purpose?

Thanks to all that replied!! I kinda figured that is what it was.. Like I said I didn't do it, the Samsung repair facility in Texas unlocked it. I called the Nexus S support line and the Level 3 tech said " When we reflashed your software, it locks your phone into the T-mobile network" and that was after she went down the hall and consulted with the "developers", Samsung tech support is a Joke. One day I'm gunna root this thing!
Thanks Again Guys.
And to the XDA moderator, sorry I posted in wrong section initially, rookie mistake..

Anybody know how to remove this lock symbol? How to re-lock the bootloader again?

soulja786 said:
Anybody know how to remove this lock symbol? How to re-lock the bootloader again?
Click to expand...
Click to collapse
fastboot oem lock
about op, what sensitive issue did you notice in your screen?

thiagodark said:
fastboot oem lock
about op, what sensitive issue did you notice in your screen?
Click to expand...
Click to collapse
Ive tried that but it doesnt work, I can reboot the bootloader via cmd but the above command has no effect? Any ideas why?
Thanks

soulja786 said:
Ive tried that but it doesnt work, I can reboot the bootloader via cmd but the above command has no effect? Any ideas why?
Thanks
Click to expand...
Click to collapse
several ideas, what error did it show? what is shown in device manager when you plug your phone in the pc in bootloader?
edit: how did you unlock it?!

Try this, these guys do a great job if breaking things down.
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Sent from my Nexus S 4G using XDA Premium App

thiagodark said:
several ideas, what error did it show? what is shown in device manager when you plug your phone in the pc in bootloader?
edit: how did you unlock it?!
Click to expand...
Click to collapse
When I go type in 'fastboot devices' or 'Adb devices' it says
"list of devices attached:" and nothing underneath it .....
I have tried updating drivers via PDAnet .... still nothing.
the drivers I have are 'ADB interface'.
Am I missing drivers specific for bootloader or something??
Basically, the phone wouldnt restore or factory reset, so I decided to root it? so I found a new '1 click root and recovery'.
Once I run the script, it unlocked bootloader and also reset my phone which worked great. Only thing I want to do now is remove the open padlock icon on the google screen (which I think is by re-locking bootloader) but when I put in the typical 'fastboot oem lock' nothing happens .....
Much appreciate the help, thanks.

You got to remove everything "custom" (cwm recovery, user roms etc) from the device before you can lock the bootloader again.
When you are trying to lock your bootloader it doesn't do anything because your device isn't correctly recognized by windows, this is prolly due to missing/wrong drivers (try uninstalling old ones and then follow the unlockr guide to rooting your phone/installing adb, http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/).

rentaric said:
You got to remove everything "custom" (cwm recovery, user roms etc) from the device before you can lock the bootloader again.
When you are trying to lock your bootloader it doesn't do anything because your device isn't correctly recognized by windows, this is prolly due to missing/wrong drivers (try uninstalling old ones and then follow the unlockr guide to rooting your phone/installing adb, http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/).
Click to expand...
Click to collapse
are you positive sure that i can't lock my bootloader with customs kernels, roms or recoveries? i don't think that's entirely true!

soulja786 said:
When I go type in 'fastboot devices' or 'Adb devices' it says
"list of devices attached:" and nothing underneath it .....
I have tried updating drivers via PDAnet .... still nothing.
the drivers I have are 'ADB interface'.
Am I missing drivers specific for bootloader or something??
Basically, the phone wouldnt restore or factory reset, so I decided to root it? so I found a new '1 click root and recovery'.
Once I run the script, it unlocked bootloader and also reset my phone which worked great. Only thing I want to do now is remove the open padlock icon on the google screen (which I think is by re-locking bootloader) but when I put in the typical 'fastboot oem lock' nothing happens .....
Much appreciate the help, thanks.
Click to expand...
Click to collapse
what is your phone 4g or gsm?!

[Q] Correct unroot and bootloader lock procedure?

Hi, my powerbutton on my sns got stuck in the "on" position. So i need to unroot the phone and lock the bootloader in order to send it to warranty repair. I would do it this way
1) reboot to bootloader
2) flash stock images via fastboot
3) issue fastboot oem lock command
4) done?
Im not really sure so im asking first.
Thanks

cahir_cz said:
Hi, my powerbutton on my sns got stuck in the "on" position. So i need to unroot the phone and lock the bootloader in order to send it to warranty repair. I would do it this way
1) reboot to bootloader
2) flash stock images via fastboot
3) issue fastboot oem lock command
4) done?
Im not really sure so im asking first.
Thanks
Click to expand...
Click to collapse
Seems about right

kwibis said:
Seems about right
Click to expand...
Click to collapse
Thanks for confirming. However when i reboot my phone into bootloader my computer cant detect it, thus making fastboot flashing impossible. Any idea what to do?

You need to make sure you have fastboot drivers installed on your computer. Search o the forum, loads of info, I cannot search now as I'm on the phone. Good luck :thumbup:
Sent from my Nexus S

cahir_cz said:
Thanks for confirming. However when i reboot my phone into bootloader my computer cant detect it, thus making fastboot flashing impossible. Any idea what to do?
Click to expand...
Click to collapse
some pics step by sptep to help!!!! (at the 6 step it appear "asus android device" but dont care about that, just search for the words "android devices", nexus devices are universal they work with all drivers)
download drivers (unzip first): http://www.4shared.com/rar/Udv-0weq/usb_driver.html

You're going to have a problem if the power button is not working.
Not going to be able to issue any commands if you can't move the cursor up and down with the volume keys in fastboot. Basically get where it says fastboot USB int...

Bricked after unlocking bootloader

Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...

Did you have all the drivers?
Can you get to bootloader?

pert_S said:
Did you have all the drivers?
Click to expand...
Click to collapse
Up to my knowledge, no driver is required on a mac.
pert_S said:
Can you get to bootloader?
Click to expand...
Click to collapse
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.

sylar12 said:
Up to my knowledge, no driver is required on a mac.
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
Click to expand...
Click to collapse
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?

Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.

pert_S said:
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Click to expand...
Click to collapse
Yep. No response so far, but the problem appears a few hours ago only.
I'm pretty sure my bootloader is corrupted. But does that prevent the device to power on?

Any other idea?

sylar12 said:
Any other idea?
Click to expand...
Click to collapse
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.

abaaaabbbb63 said:
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
Click to expand...
Click to collapse
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem

sylar12 said:
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Click to expand...
Click to collapse
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.

sylar12 said:
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
Click to expand...
Click to collapse
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.

Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.

gee2012 said:
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
Click to expand...
Click to collapse
This is not "directly" required on mac. And the fastboot binay has been recognized by the shell, since the unlocking procedure started (my phone asked me if it was ok for unlocking the bootloader).
abaaaabbbb63 said:
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Click to expand...
Click to collapse
I already tried this: nothing happens... I guess the phone is really bricked.
eddie_gordo said:
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
Click to expand...
Click to collapse
It should be the same, yes. Fastboot is very easy to use usually, it's the first time I have such a problem. And I have no idea why the unlocking has got wrong. 2 solutions imho:
- a phone harware problem which only reveals during the unlocking process;
- a fastboot problem/mac related problem.
Just trying to figure out which one is the correct answer.

El Daddy said:
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
Click to expand...
Click to collapse
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.

sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.

sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
I think you got really unlucky. Possibly a bad cable or USB port but some connection got lost while you were flashing. RMA is your best option right now. Sorry bro

abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their phone.
Click to expand...
Click to collapse
Yessssss, I did it!
...
:crying:
abaaaabbbb63 said:
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).

sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't they will).
Click to expand...
Click to collapse
You'll be fine on the rma. Been there done that on another device

sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
Click to expand...
Click to collapse
Maybe the XDA award for the1st N5 bricker is a new Nexus 5 32GB

abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
Sorry to disappointed you but I was the first one. Last week I bricked mine

Oneplus 6 stuck in fastboot mode

Hello everybody,
I was glad to receive my OnePlus 6 3 days ago. But this morning, the phone rebooted itself and I am now stuck into fastboot mode.
So just to be clear, I already tried the following things :
- Rebooting into system by pressing "Power" while fastboot mode is selected on "START"
- Rebooting into system by using fastboot.exe utility "fastboot.exe reboot"
- Rebooting into recovery by selecting the option in fastboot menu and pressing "Power"
- Trying to unlock the bootloader by using fastboot.exe utility "fastboot.exe oem unlock" (Can't do it since I didn't turn on the option in Developer Settings)
At this point, my phone is just a brick rebooting into fastboot and I'm thinking about sending the device back to OP. Would someone have an idea what could I do to boot the phone or at least access the recovery ?
Thanks.

Is it still stock? Have you done anything to it? If you haven't unlocked it, I don't think the unbrick tools will work for you, and you should contact OP.
You might give this a try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

iElvis said:
Is it still stock? Have you done anything to it? If you haven't unlocked it, I don't think the unbrick tools will work for you, and you should contact OP.
You might give this a try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Hi, Thanks for your reply. I didn't do anything to the phone. It was 100% stock. I'm now trying some tools I can found on xda but with no luck :/
I'm gonna try the tool you linked right now. Will keep updated.

Gr8man001 said:
Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That tool requires an unlocked bootloader, which the OP does not have.

Gr8man001 said:
Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Thanks for your reply.
Yes I tried it like 15 min ago, and I get an error because my bootloader is locked ... I can't unlock because it has to be done in the system.

So, if you don't mind losing your personal data on the internal storage, you might try unlocking the bootloader. This will wipe the internal storage. I had an issue where I was caught in a bootloop and I locked and then unlocked the bootloader and it got me out of the bootloop.
If you are stuck in fastboot, you should be able to unlock the bootloader via adb cmd line from your computer. I believe it's "fastboot oem unlock".

azsl1326 said:
So, if you don't mind losing your personal data on the internal storage, you might try unlocking the bootloader. This will wipe the internal storage. I had an issue where I was caught in a bootloop and I locked and then unlocked the bootloader and it got me out of the bootloop.
If you are stuck in fastboot, you should be able to unlock the bootloader via adb cmd line from your computer. I believe it's "fastboot oem unlock".
Click to expand...
Click to collapse
Thanks for you reply.
Unfortunately, the bootloader can't be unlocked. I have to check "OEM UNLOCK" in developer settings and since and I can't boot into the system ...

Krysou said:
Thanks for you reply.
Unfortunately, the bootloader can't be unlocked. I have to check "OEM UNLOCK" in developer settings and since and I can't boot into the system ...
Click to expand...
Click to collapse
Forgot about that setting...sorry. You might try and give OP Support a call. I have heard that they can remote into your phone and resolve issues like this one.

I am NOT an expert and there are smarter folks on this site who can explain. I had a similar issue with one of my previous phones and someone had suggested to turn off the phone (if you can otherwise just try it in fastboot mode) and hold BOTH volume up and down buttons while pressing the power button (keep it pressed for a good minute or so) and I was able to boot into "limited" OS (I think it's called safe mode or something). Not saying that it will fix the issue but may be worth the try. Just trying to help. Good luck.

Gr8man001 said:
I am NOT an expert and there are smarter folks on this site who can explain. I had a similar issue with one of my previous phones and someone had suggested to turn off the phone (if you can otherwise just try it in fastboot mode) and hold BOTH volume up and down buttons while pressing the power button (keep it pressed for a good minute or so) and I was able to boot into "limited" OS (I think it's called safe mode or something). Not saying that it will fix the issue but may be worth the try. Just trying to help. Good luck.
Click to expand...
Click to collapse
Thanks for your suggestion. Unfortunately, the device reboots into fast boot each time again and again.

time to call OnePlus and have them do a remote session to restore ur phone, get a keylogger and get the passcode for the zip for us lol

Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
https://www.******.com/unbrick-oneplus-6-using-msmdownload-tool/
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.

Krysou said:
Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
https://www.******.com/unbrick-oneplus-6-using-msmdownload-tool/
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.
Click to expand...
Click to collapse
can you give a download link of that tool and some simple instruction, please.

jkyoho said:
can you give a download link of that tool and some simple instruction, please.
Click to expand...
Click to collapse
Hello,
https://www[.]berga-tech[.]com/2018/05/how-to-guide-unbrick-oneplus-6-using.html?m=1
You will find all instructions and download link there.

Return
Krysou said:
Thanks for your reply.
Yes I tried it like 15 min ago, and I get an error because my bootloader is locked ... I can't unlock because it has to be done in the system.
Click to expand...
Click to collapse
Unfortunately sounds like you may have to return the phone. (that sucks)

https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
try the OOS5.1.5 MDMtool from link above. It works for me.
And if you unable to go to qualcomm 9008 mode from fastboot, try connect to pc with cable ,and press and hold power& vol_up, and wait for the connect sound from computer

Krysou said:
Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.
Click to expand...
Click to collapse
I'm experiencing the exact same issue than you Krysou. Thanks a lot for the solution which gives me a hope ! Could you please tell me if you were able to recover your data (photos / videos) after the unbricking procedure ? I'd like to know it before I run the MsmDownload Tool.
Thanks for your reply

groggy8888 said:
I'm experiencing the exact same issue than you Krysou. Thanks a lot for the solution which gives me a hope ! Could you please tell me if you were able to recover your data (photos / videos) after the unbricking procedure ? I'd like to know it before I run the MsmDownload Tool.
Thanks for your reply
Click to expand...
Click to collapse
OOps men, I'm sorry to answer that late to your question, doing it for the others searching for a solution.
So : You won't recover anything after running MsmDownloadTool. You get a pretty much completely stock phone, like when you got it after unboxing

Krysou said:
Thanks for your suggestion. Unfortunately, the device reboots into fast boot each time again and again.
Click to expand...
Click to collapse
try this metod https://forum.highonandroid.com/t/how-to-unroot-oneplus-6-using-fastboot/33

Question OEM Unlock greyed out and device not found in fastboot

I'm trying to unlock bootloader, but OEM Unlock option is greyed out.
Device can enter fastboot but doesn't respond to any commands. For example "fastboot devices" do nothing. Using same computer, fastboot commands work fine with another device.
Any solutions? thanks

Windoors said:
I'm trying to unlock bootloader, but OEM Unlock option is greyed out.
Device can enter fastboot but doesn't respond to any commands. For example "fastboot devices" do nothing. Using same computer, fastboot commands work fine with another device.
Any solutions? thanks
Click to expand...
Click to collapse
Try removing the sim card, or putting another carriers card in there. I seem to remember this popping up before

Beetle84 said:
Try removing the sim card, or putting another carriers card in there. I seem to remember this popping up before
Click to expand...
Click to collapse
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?

Windoors said:
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?
Click to expand...
Click to collapse
Help with unlock OEM no work
Is off and dont put on, say Conect to Internet or call you carrier. Any help please... thanx
forum.xda-developers.com
Have a read of this thread

Windoors said:
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?
Click to expand...
Click to collapse
Also try installing tinyfastboot from the lineage or evo rom threads. Select the recommended moto drivers, fastboot should be fine afterwards.

Fastboot working after installing drivers from: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/