Related
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?!
Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.
Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).
When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.
http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!
Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.
I had flash stock firmware
through PC
I have a Moto G that has gotten "stuck", if that's a good description. If I start it, the initial Moto splash screens go fine and then it becomes a dark screen but backlight On and just stays stuck there for ever. (Is this what is called a boot loop? Not sure)
By using the Power + Down Vol key combo I did manage to get it to the boot menu. Unfortunately the Recovery Option there does not work. Shows a quick Moto bootup splash screen, then Says "Boot up failed" and falls to the boot menu again.
What's my best bet to recover from this?
I did install adb + fastboot on my laptop & then connected the Moto G with a USB Cable. fastboot seems to work. I could get the phone to reboot, and some other basic diagnostics. e.g. "fastboot oem get_unlock_data works". "fastboot devices" also shows my device Serial Number correctly. But I want to be careful before I issue any further erase or flash commands so I thought it best to post on here. What is the logical next step in the debug?
"adb devices" did not succeed.
The phone had the original Google / Motorola software so far and I'd never even attempted to flash it etc. Only whatever automatic updates got pushed by Google / Moto / Carrier over the network. Right before this happened I was in a call and got a bunch of pop ups saying Application xxx was being shut down.
The phone is out of warranty. It is still locked, but when I enter the details on the Moto Website it says it can be unlocked. So I can proceed to get the unlock codes etc. if that helps.
The exact SKU is XT1033. Boot menu says (Version 41.13; Battery OK; Device is locked; Status Code 0) if that is of any help. Was a Dual SIM phone on a GSM Carrier.
Tried issuing the commands
Code:
fastboot erase cache
fastboot erase userdata
Both don't seem to have helped at all.
Any other ideas?
To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.
legolas06 said:
To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.
Click to expand...
Click to collapse
Thanks @Legolas!
I did not realize that. So I guess if I just tried a flashboot flash command it would fail since my phone is not unlocked at the moment.
Luckily I can get the unlock code from the Motorola site. I will proceed to do that then first and subsequently try all the other steps needing flashing.
What happened? Did you manage to boot it up?
@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it
Lucariel said:
What happened? Did you manage to boot it up?
Click to expand...
Click to collapse
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!
ravibhat said:
@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it
Click to expand...
Click to collapse
No luck yet. If you find any ideas let me know!
@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.
ravibhat said:
@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.
Click to expand...
Click to collapse
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?
@carefulcat :
Well,I am on an unlocked unrooted Android L 5.0.2 XT1033 Asia Retail Edition (upgraded via OTA) which has Bootloader version 41.18.
You've just cleared the ROM it seems.
Unlocking the bootloader will wipe off all the data from your device.
It seems yours is still locked,you have the unlock code but didn't use it.
Which OS did you have?Exact version,region and type of upgrade.
And which commands have you used till now?
If you're clear with the basics try stocking a Stock Flash ROM (depending on your bootloader and previous OS) or custom recovery like TWRP or CW.
carefulcat said:
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?
Click to expand...
Click to collapse
carefulcat said:
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!
Click to expand...
Click to collapse
Took it to a repair shop, the said something was wrong with my mother, they fixed that and now the phone enters into recovery, what wont boot.
Will try the "qhsusb_dload" thing this week.
I have used all of my knowledge with past android phones yet to no avail. Every time I issue the command "Fastboot oem unlock", the bootloader returns an error on the phone claiming "Unlock failed... rebooting to fastboot in 3s" and my command prompt returns "FAILED: Error 0x7000". I do not understand as OEM Unlock is enabled, and so is USB debugging. Help would go a long way.
EDIT: Silly me, I forgot that I got this on EE contact. It's sim locked ?
Maybe cause of encryption on 7.0?
Sent from my TA-1032 using Tapatalk
Nikola Jovanovic said:
Maybe cause of encryption on 7.0?
Sent from my TA-1032 using Tapatalk
Click to expand...
Click to collapse
encryption shouldn't be an issue. I've dealt with multiple android N devices and the bootloader unlocks were simple and sweet.
Your reply to my question doesn't answer, except widen the issue.
If it's a matter of encryption, then how do I remove such?
Same issue here!! Any idea?
Still waiting for someone to reply or give a useful answer....
I was under the impression the bootloader was locked by Nokia.
Did you fail to read the post? It's locked.
retr0gr4d3 said:
I have used all of my knowledge with past android phones yet to no avail. Every time I issue the command "Fastboot oem unlock", the bootloader returns an error on the phone claiming "Unlock failed... rebooting to fastboot in 3s" and my command prompt returns "FAILED: Error 0x7000". I do not understand as OEM Unlock is enabled, and so is USB debugging. Help would go a long way.
EDIT: Silly me, I forgot that I got this on EE contact. It's sim locked ?
Click to expand...
Click to collapse
Same happened to me, maybe try to factory reset the phone and then try again.
And my sim is unlocked but still doesn't work.
SkaboXD said:
Same happened to me, maybe try to factory reset the phone and then try again.
And my sim is unlocked but still doesn't work.
Click to expand...
Click to collapse
Fastboot Oem Unlock seems to require an unlock key following this code. Perhaps, maybe a mix or sum.
Hi Guys,
To unlock the access to bootloader on my Nokia 3 I had to plug the charger or have above 70/80% BAT. Activate developer options, go in there and tick the "OEM Unlocking", shutdown the phone. Press Vol Down and Power Button until you see a post message counting some seconds, keep the buttons down ALL THE TIME until you see the bootloader.
Hope it goes well for you too
Glad to help
Johker said:
Hi Guys,
To unlock the access to bootloader on my Nokia 3 I had to plug the charger or have above 70/80% BAT. Activate developer options, go in there and tick the "OEM Unlocking", shutdown the phone. Press Vol Down and Power Button until you see a post message counting some seconds, keep the buttons down ALL THE TIME until you see the bootloader.
Hope it goes well for you too
Glad to help
Click to expand...
Click to collapse
This is false, as the phone just continues to boot after the countdown. Don't try it people, it's a waste of time
retr0gr4d3 said:
This is false, as the phone just continues to boot after the countdown. Don't try it people, it's a waste of time
Click to expand...
Click to collapse
maybe try with miracle box, there is a option to unlock bootloader
SkaboXD said:
maybe try with miracle box, there is a option to unlock bootloader
Click to expand...
Click to collapse
I hadn't even thought of this, I will give it a try asap. Thanks for the suggestion
retr0gr4d3 said:
I hadn't even thought of this, I will give it a try asap. Thanks for the suggestion
Click to expand...
Click to collapse
Download miracle with loader https://forum.hovatek.com/thread-15700.html
SkaboXD said:
Download miracle with loader https://forum.hovatek.com/thread-15700.html
Click to expand...
Click to collapse
Already downloaded and on it ? giving it a try when it's set up
SkaboXD said:
Download miracle with loader https://forum.hovatek.com/thread-15700.html
Click to expand...
Click to collapse
Didn't work ?
retr0gr4d3 said:
Didn't work ?
Click to expand...
Click to collapse
sorry about that, ask @the_laser for help, he unlocked bootloader, just send him imei and serial number and he will give you a key. I tried and it worked.
SkaboXD said:
sorry about that, ask @the_laser for help, he unlocked bootloader, just send him imei and serial number and he will give you a key. I tried and it worked.
Click to expand...
Click to collapse
Ahhhh, I've got a code from him but every time I enter it my adb hangs at <Waiting for Device>
retr0gr4d3 said:
Ahhhh, I've got a code from him but every time I enter it my adb hangs at <Waiting for Device>
Click to expand...
Click to collapse
did you enabled usb debugging and allowed it on your computer?
SkaboXD said:
did you enabled usb debugging and allowed it on your computer?
Click to expand...
Click to collapse
Yeah that all works and the recovery works and all the adb commands work, but issuing OEM key (***) just makes it permanently wait. I've tried on Mac and 2 Windows, it doesn't change. Any chance you can inform me on your setup of adb (drivers used, etc)
So I just got my OP7P (ordered from Oneplus directly, not TMobile branded, though when I get it going I will be using my TM simcard), and I've been stuck trying to get the bootloader unlocked.
So I've enabled USB Debugging, confirmed ADB works while I'm booted up normally. I can issue my commands like "adb reboot-bootloader" or just use the Advance Reboot to reboot to bootloader.
I've also enabled the OEM Unlock option in the Dev section.
So what happens?
Well, nothing really. I reboot to the bootloader, get to where it says "start" and then I fireup "adb devices", and nothing is found. Trying to ignore that fact, doing something like "fastboot flashing unlock" just sits at "waiting for device".
Not really sure what's to miss here.
GM1917
9.5.7.GM21AA
Appreciate any advice/help
uaktim said:
So I just got my OP7P (ordered from Oneplus directly, not TMobile branded, though when I get it going I will be using my TM simcard), and I've been stuck trying to get the bootloader unlocked.
So I've enabled USB Debugging, confirmed ADB works while I'm booted up normally. I can issue my commands like "adb reboot-bootloader" or just use the Advance Reboot to reboot to bootloader.
I've also enabled the OEM Unlock option in the Dev section.
So what happens?
Well, nothing really. I reboot to the bootloader, get to where it says "start" and then I fireup "adb devices", and nothing is found. Trying to ignore that fact, doing something like "fastboot flashing unlock" just sits at "waiting for device".
Not really sure what's to miss here.
GM1917
9.5.7.GM21AA
Appreciate any advice/help
Click to expand...
Click to collapse
Hmm, tried a different PC and was able to get it going this time. Not 100% sure what is different, I installed the drivers and all the same. Oh well. Crisis avoided.
I realized you resolved this, but for future reference and for anyone else who runs across this, the reason "adb devices" wasn't finding anything after going to bootloader is because you need to use the fastboot command instead of adb.
For getting the command that actually unlocks the bootloader, I have always used the command "fastboot oem unlock". Not sure what you entered to make it work, but that command probably would of worked on the original pc.
for anybody not so lucky having spare different PC to try - check here https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/