[Android Q&A, Help & Troubleshooting] Devildog0351:
I know mostly everyone should know this but ...........I have to say it I am sure some new people don't know or someone just forgot but ...

Have you enabled OEM Unlock ? Have you enabled USB Debugging ?

If you have not then of course your commands will not work or will return with error and ect.....

Have you done adb devices and see what comes back?

Dose it come back with your devices ID or is it come back blank for device info?

One reason you Run that command is to know the state of your phone or USB Debugging ect...

Even if you have enabled the OEM and or USB in developers options before you must check it every time always...now if you haven't for one or both then several things will happen....

Your adb or fastboot commands will not work or or will return with errors.Don't be fooled or confused that some adb and fastboot commands do and will work even if you didn't enable the two options or just one option.

I won't explain that you can Google why you may learn something when doing so if you have t already ... ......

Now if your reading this then. You fit in one of 4 catergories In my Opion .

1.Newbie ( Team entire post it will explain a lot you need to know)

2 Lazy and try to cut corners

( Don't know what to tell you.... ..do it right and quit being lazy)

3 Soft Bricked , Hard Bricked , Bootloop ect.

( Something happens by acident or whatever reason maybe sideloading firmware,recovery,bootloader,ect... ** If not a newbie Skip to

*?*?*?* Section

To advoid a lesson on what to do and what not to do as a newbie.

4 Your using incorrect OEM or ADB and Fastboot commands not for your devices .....

Now I won't beat you up to bad about your post or question or whatever you call that what you did I don't know just looked lazy as hell I won't get to worked up over it no one is perfect and we all been a Newbie or rookie in something but you need to know the importance of what is missing or why your post is crappy as hell ok. So you can learn and or not do it aging. The solution or helping is faster for everybody .

Further reference put as much info as possible . Just most will not ask you 100 questions about . What have you done or not done. Ect...

You should let us know how you ended up in the position what did you do before remember it's not my job to ask you 100 questions to find out what's going one with your device its not our phone that is the problem it's yours

So do us the favor and youraelf and everyone else that comes into contact with the same or similar issue and provide as much info as possible.

So I don't know what you have done other that run 2 fastboot commands and honestly I don't even know think they are correct for That device.

Most phones. Use the same or simar adb or fastboot Commands but there are OEM specific commands for certain android versions or devices and that don't work on other devices .

I will let you. Google more about that also maybe you learn something...

*?*?*?*?*?*?*?*?*?*

to restart your phone into fastboot mode or bootloader mode:

adb devices

adb reboot bootloader

fastboot devices ( just like earlier it's important that device info returns after command )

Now when your bootloader / fastboot mode

fastboot oem unlock

This will Unlock the bootloader and delete all user data present on the phone.

If you still having issue then USB Debugging and OEM unlock was not the issue then your problem is not just the bootloader and needs more detailed approach to fix specific to your device.