Develop Bugs

[Q] Enter Fastboot mode with scrapped volume button, to relock the bootloader

Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!

adb reboot bootloader.

I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?

I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.

cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place

cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.

Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!

martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...

Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium

cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.

Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!

Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:

[Q] need help in unlocking Bootloader for HTC One V

Hi,
I am trying to unlock the boot-loader for HTC one V using the steps given on their official website
followed all the steps, but when i reach step 8: and type in
>fastboot oem get_identifier_token
It just shows waiting for devices, whereas my device is already connected. and in the FASTBOOT mode
When I type
>fastboot devices
It shows nothing (should'nt It show the device which is already connected?)
I have the Android SDK installed and copied the 3 required files from the Platform-tools folder.
ie -
adb.exe
AdbWinApi.dll
fastboot.exe
I have the USB debugging turned on,
HTC sync manager is installed and it also shows that the Driver is up-to-date.
Though, when I plug in the Phone in Fast Boot mode it shows USB device not recognized.(I am using Windows 8 Pro )
This Is the first time I am trying this
What am I doing wrong? any help would be appreciated.
TIA.

srivassumit said:
Hi,
I am trying to unlock the boot-loader for HTC one V using the steps given on their official website
followed all the steps, but when i reach step 8: and type in
>fastboot oem get_identifier_token
It just shows waiting for devices, whereas my device is already connected. and in the FASTBOOT mode
When I type
>fastboot devices
It shows nothing (should'nt It show the device which is already connected?)
I have the Android SDK installed and copied the 3 required files from the Platform-tools folder.
ie -
adb.exe
AdbWinApi.dll
fastboot.exe
I have the USB debugging turned on,
HTC sync manager is installed and it also shows that the Driver is up-to-date.
Though, when I plug in the Phone in Fast Boot mode it shows USB device not recognized.(I am using Windows 8 Pro )
This Is the first time I am trying this
What am I doing wrong? any help would be appreciated.
TIA.
Click to expand...
Click to collapse
Run the SDK Manager, do you have the Google USB Driver installed (it's under extras). I'm not 100% certain but I think you need to install that to recognize the phone in Fastboot mode.

-Duir- said:
Run the SDK Manager, do you have the Google USB Driver installed (it's under extras). I'm not 100% certain but I think you need to install that to recognize the phone in Fastboot mode.
Click to expand...
Click to collapse
Hey, Thanks for your reply, I had the Driver installed already, but there was some problem with Usb3.0 i guess
I plugged the device in Usb2.0 port and followed the steps and It worked Fine.
:good:

Unlocking Is easy

I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Note For Clarification: you CANNOT do this over Bluetooth.
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...

Yeah its like a nexus in that regard. And no I don't have the watch yet but have ordered it today.

I would unlock mine but there's no reason to yet. I always unlock my Nexus devices first thing yet with the watch I would like to keep it stock for now.

No reason to unlock, until someone creates twrp, and root.

suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
I agree, a factory reset on it only takes 2-3 minutes so its not like a phone where it takes forever to set up again.

ApoKyla said:
I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...
Click to expand...
Click to collapse
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)

Carlossianz0815 said:
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)
Click to expand...
Click to collapse
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock

brizey said:
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock
Click to expand...
Click to collapse
Hi,
no, the fastboot command does not work,it stops with the message < waiting for device >

Cannont get USB drivers to work
I tried bith google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
I tried both google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.

I still use the old pdanet drivers...they seem to work with everything.

Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!

Carlossianz0815 said:
Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!
Click to expand...
Click to collapse
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app

Thanks for replay,
last night i got it, via Bluetooth.
Thanks all, now i have the new kernel and recovery.
I think the new kernel works faster and need less power then the orig one.
best Regards

Thank you !

az93civic said:
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app
Click to expand...
Click to collapse
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
---------- Post added at 03:27 AM ---------- Previous post was at 03:04 AM ----------
wookie_666 said:
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
Click to expand...
Click to collapse
just realised i should probably be using the magnetic charger, because when i reboots it looses bluetooth connection
ill try when i get home

az93civic said:
...
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Click to expand...
Click to collapse
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.

Trejkaz said:
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.
Click to expand...
Click to collapse
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.

dbroer91884 said:
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.
Click to expand...
Click to collapse
Actually, it has been a bit of a ride.
I knew of adb already from my watch face development so I had initially wondered whether fastboot was a subcommand of that. I didn't expect it to be another command in the SDK at all for some reason. But yep, it's in the same place as adb, and it works, and now everything flashed fine. I don't know why I didn't search my computer for a file with that name, since that would have located it.
Un-hiding the development options is mentioned on the wear developer site so that was fairly easy to set up. The only hard part was that they gave a text-only explanation, but this watch came set to Chinese, so it was a bit fun to figure out which button to press to "confirm" a dialog. I recognised the first option as the "no" and the second option turns out to have been the "yes", but there are more options below that I still don't know what they are, lol.

suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2

janjan said:
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2
Click to expand...
Click to collapse
You are quoting me from 4 mos ago? LMFAO!

Problem with fastboot flashing

I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
FAILED (command write failed (No such device or address))
Click to expand...
Click to collapse
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?

_Raziel666 said:
I have somehow installed the fastboot drivers for my Pixel C (although ADB still doesn't work), and have successfully (?) unlocked the bootloader.
If I try to flash either the newest bootloader in order to install the N Developer Preview or a TWRP image, I get the following message:
I tried different USB ports but the result was the same. I found somewhere about fwtool, but in order to use that I have to be rooted (if I understood correctly).
Any other ideas?
Click to expand...
Click to collapse
I'm assuming that since you were able to "successfully" unlock the bootloader that you can do this to check and see if your PC still recognizes your device. So, while you have you're Pixel C in fastboot and have it connected to your PC, open a command prompt and type the words fastboot devices and see if it returns your device serial number. Normally the command prompt will show that message when your device is not properly connected with the correct drivers installed. Also, if you have the correct drivers installed your ADB should work if you have enabled USB Debugging in developer options.
Sent from my Nexus 6 using XDA-Developers mobile app

Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.

_Raziel666 said:
Well, fastboot devices (and all fastboot commands) works. As for ADB it shows my device, but says unauthorized and never asks for my authorization.
But the thing is that I cannot flash anything.
Click to expand...
Click to collapse
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Okay. If it will recognize fastboot commands let's start over from the beginning. Go to developer options and verify OEM Unlocking is checked and USB Debugging is checked. If you have the correct ADB drivers installed you will receive a pop-up message that says "This computers RSA key fingerprint is xxxxxxxxx. Check the box to always allow. Next, boot to the bootloader and type fastboot devices in a command prompt window. If it returns your device serial number then we are good to go.
Next, open a command prompt window and type fastboot flashing unlock. (may have to use fastboot OEM unlock) I've seen both work for some reason. If you are successful your Pixel will give you a message saying the bootloader is unlocked and OS verification is off. Once it's complete it will boot into the bootloader again. Once this happens, boot normally and hurry through the setup wizard so you can enable developer options and enable USB Debugging.
Now, once this is done boot to the bootloader and open another command prompt window and type fastboot devices to verify you are connected. If you are connected then you can fastboot flash the Android"N" bootloader and install the developer preview. Lemme know how you make out.
If you want to chat over Hangouts my email is [email protected].
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the very descriptive post. The thing is that I have already done all that, with the exception of using ADB, the pop-up never appeared and my Pixel C appears as unauthorized in adb devices.
I know for a fact that the bootloader is unlocked, because everything got wiped afterwards, and I also get the message saying that the bootloader is unlocked in every boot.
The thing is I cannot flash neither the developer preview nor the TWRP image. I read somewhere about a similar thing some users had on Pixel C, but the solution was to either do something via TWRP or use fwtool that needs root. And I can do neither.
So that's why I started this topic to see if anyone can think of anything else.
Sent from my A0001 using Tapatalk

On thing to try is to go into the settings Developer Options and "revoke USB debugging authorization". Connect to PC and you should then be asked to allow the "fingerprint". Hopefully that will fix it. I assume you've tried changing the connection type - charging, File transfer etc. If you are using W10 Pro then you may have driver issues. There are many posts on the net about that os and Google's driver but I've yet to find a definitive answer, I now use a USB C card see http://forum.xda-developers.com/pixel-c/help/windows-10-pixel-c-type-c-ports-t3414423

USB debugging

Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance

Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?

RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.

edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....