Database Develop

How to relock the bootloader?

Hello,
Forgive me for my bad English, I'm French, I unlock the bootloader via the Motorola site, it has to work perfectly, but I will wish to reset the lock the bootloader, how do I proceed? On the Motorola site there is not any procedure.
Pierre

If you are doing for warranty purposes it is still voided and they will charge for repair.
But if for some silly reason you need to lock it...
Code:
fastboot oem lock
Sent from my MB886 using Tapatalk 2

Using your code I get the following message appears:
FAIL: run fastboot oem lock Please begin first!
Click to expand...
Click to collapse
What to do?
Code:
C:\sdk\tools>cd..
C:\sdk>cd platform-tools
C:\sdk\platform-tools>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.550s]
finished. total time: 0.550s

pierre144 said:
Using your code I get the following message appears:
What to do?
Code:
C:\sdk\tools>cd..
C:\sdk>cd platform-tools
C:\sdk\platform-tools>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.550s]
finished. total time: 0.550s
Click to expand...
Click to collapse
That's how it was supposed to work... contact Motorola I guess. Why bother locking anyway..?

mattlgroff said:
That's how it was supposed to work... contact Motorola I guess. Why bother locking anyway..?
Click to expand...
Click to collapse
I will contact Motorola, I want to put the bootloader as before for security reasons.

pierre144 said:
I will contact Motorola, I want to put the bootloader as before for security reasons.
Click to expand...
Click to collapse
Won't change a thing in terms of security, except possibly for DRM content. Read what bootloader tells you. I believe the sequence is "fastboot oem lock begin", then firmware flash, then "fastboot oem lock".

Skrilax_CZ said:
Won't change a thing in terms of security, except possibly for DRM content. Read what bootloader tells you. I believe the sequence is "fastboot oem lock begin", then firmware flash, then "fastboot oem lock".
Click to expand...
Click to collapse
I wish to sell on my phone so i want to re-lock it to remove the bootloader warning. Unfortunately the above steps don't work for me either and I cant see any mention of how to lock the phone again on motorolas site?

f1ux said:
I wish to sell on my phone so i want to re-lock it to remove the bootloader warning. Unfortunately the above steps don't work for me either and I cant see any mention of how to lock the phone again on motorolas site?
Click to expand...
Click to collapse
Then can't you use fastboot to put the original boot logo back on instead of relock?
Sent from my rooted XT890 with unlocked bootloader using XDA premium
Past androids: HTC Hero - Sony X10 mini (rooted and running mini cyanogenmod) - Orange Stockholm (rooted to remove orange's skin and bloatware) :3

max choco found a way to relock! here you find the guide:
http://argendroid.com/topic-GUIA-Re...upera-tu-garantía-volver-al-estado-de-fabrica

mercurio. said:
max choco found a way to relock! here you find the guide:
http://argendroid.com/topic-GUIA-Re...upera-tu-garantía-volver-al-estado-de-fabrica
Click to expand...
Click to collapse
I tried following the guide.
I'm on the Retail EU firmware 4.1.2
When I try to flash the system, it shows some error about the file size (the 100MB limit?) and when I try to lock the bootloader without flashing system - but everything else - it tells me that something in my system is wrong...
What (if any) is the fastboot command to MultiFlash the system_signed manually?

Sayuuk said:
I tried following the guide.
I'm on the Retail EU firmware 4.1.2
When I try to flash the system, it shows some error about the file size (the 100MB limit?) and when I try to lock the bootloader without flashing system - but everything else - it tells me that something in my system is wrong...
What (if any) is the fastboot command to MultiFlash the system_signed manually?
Click to expand...
Click to collapse
I have that problem too... 100MB limit comes on screen.
I haven't found JB Retail British, only ICS Retail British. I want to be careful with flashing ... if you flash JB to ICS you will brick..

Any news about that?

mercurio. said:
max choco found a way to relock! here you find the guide:
http://argendroid.com/topic-GUIA-Re...upera-tu-garantía-volver-al-estado-de-fabrica
Click to expand...
Click to collapse
Does not work in "Razr HD" because we do not have the files "bos_signed, gpt_signed, motoboot and radio_signed" in firmware. If anyone can help, I really need. Grateful.

its not possible man

felipe_net said:
its not possible man
Click to expand...
Click to collapse
You tried it?
Enviado desde mi Moto HD

LOCK
fastboot oem lock begin
fastboot flash boot boot.img
mfastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
use this mfastboot View attachment mfastboot.zip for command - mfastboot flash system system.img
system.img must be solid file ! if not and you have multiple files, try renaming the last of them in system.img
Good Luck

borik88 said:
LOCK
fastboot oem lock begin
fastboot flash boot boot.img
mfastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
use this mfastboot View attachment 2546578 for command - mfastboot flash system system.img
system.img must be solid file ! if not and you have multiple files, try renaming the last of them in system.img
Good Luck
Click to expand...
Click to collapse
And all these files? where can i download that? (boot.img, system.img, recovery.img, logo.bin)
Thanks!

Finally, Re-Lock Failed

I am not getting download link of fastboot oem lock for razr i

100% stock, unlocking & relocking the bootloader questions

I have read all of the info about unlocking and relocking the bootloader, but i have a question, if i was 100% stock with a locked bootloader and wanted to flash the latest factory image would i still need to enable developer options and enable allow oem unlock even if i was to run the commands below from fastboot mode.
fastboot oem unlock
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot oem lock
fastboot reboot
The reason i ask is that you are not booting into android until the bootloader is relocked, so in theory the oem unlock option shouldn't have an effect in this scenario?

@d.chatten,
Yes, you have to unlock the bootloader to use fastboot to flash .img files, or to sideload via ADB.

d.chatten said:
I have read all of the info about unlocking and relocking the bootloader, but i have a question, if i was 100% stock with a locked bootloader and wanted to flash the latest factory image would i still need to enable developer options and enable allow oem unlock even if i was to run the commands below from fastboot mode.
fastboot oem unlock
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot oem lock
fastboot reboot
The reason i ask is that you are not booting into android until the bootloader is relocked, so in theory the oem unlock option shouldn't have an effect in this scenario?
Click to expand...
Click to collapse
You really should boot into Android before re-locking. This is where people have run into trouble. Following the re-lock guide is recommended.

Thanks for your reply, much appreciated, but my question wasn't about the need to unlock the bootloader ot flash, my question was, do i still need to enable "allow oem unlock" in developer options if i use the commands listed above when flashing the latest factory image on a Nexus 6 when 100% stock a locked bootloader, this in theory should work as you are not booting into android until the bootloader is relocked?

The main thing to remember, is to remove all security locks and your Google account beforehand. With this device, when fastboot oem lock is issued, the device is wiped again. This is why it is important to be sure you have a working OS before locking. :good:

Evolution_Freak said:
You really should boot into Android before re-locking. This is where people have run into trouble. Following the re-lock guide is recommended.
Click to expand...
Click to collapse
Thanks for that, i will follow the guide, so this option would effect things regardless?

d.chatten said:
Thanks for your reply, much appreciated, but my question wasn't about the need to unlock the bootloader ot flash, my question was, do i still need to enable "allow oem unlock" in developer options if i use the commands listed above when flashing the latest factory image on a Nexus 6 when 100% stock a locked bootloader, this in theory should work as you are not booting into android until the bootloader is relocked?
Click to expand...
Click to collapse
I understand completely. In a sense, you have outlined the process that is shown on the factory image page, by Google. This information needs to be updated as it does not reflect the security changes made in 5.1. I wouldn't risk your device for a few extra minutes needed to verify the OS boots.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
d.chatten said:
Thanks for that, i will follow the guide, so this option would effect things regardless?
Click to expand...
Click to collapse
I can confirm that several people have bricked by trying to do it the way you were thinking of trying. If for any reason, during the flashing process something didn't flash just right, and a bootloop occurred, you wouldn't be able to fix it with a locked bootloader. That's why it's best to ensure your OS boots before locking.

Evolution_Freak said:
I understand completely. In a sense, you have outlined the process that is shown on the factory image page, by Google. This information needs to be updated as it does not reflect the security changes made in 5.1. I wouldn't risk your device for a few extra minutes needed to verify the OS boots.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
I can confirm that several people have bricked by trying to do it the way you were thinking of trying. If for any reason, during the flashing process something didn't flash just right, and a bootloop occurred, you wouldn't be able to fix it with a locked bootloader. That's why it's best to ensure your OS boots before locking.
Click to expand...
Click to collapse
Thank you for clarification, much appreciated, the process is still easy enough even with these extra steps.

How do i restore XT1068 to uk stock rom on mac?

I've searched and searched and the rom i have installed is not the uk version and the phone won't let me lock the boot loader. where can i find the stock uk rooms and how do i do it on a mac? help?

jesus h christ

here have the files on the OP attachments
here have all the ROM's stock
the command are the some as any other back to stock help...
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
if you get a error on the command
fastboot flash partition gpt.bin
try to do without it

thanks man will try now

nah this don't work

when i try to lock it it says sign flash signed images firstly, 2nd command i get an error and the 3rd also an error. every other command other than fastboot oem lock worked, so i think I'm on the uk stock rom(its not in the link you posted btw, i got it else where).
yeah I'm on stock gb and am getting ota updates but my boot loader is still unlocked?

crozbomb said:
when i try to lock it it says sign flash signed images firstly, 2nd command i get an error and the 3rd also an error. every other command other than fastboot oem lock worked, so i think I'm on the uk stock rom(its not in the link you posted btw, i got it else where).
yeah I'm on stock gb and am getting ota updates but my boot loader is still unlocked?
Click to expand...
Click to collapse
the lock is the last command, if you don't flash all the files in order the last command will not work, only exception is the gpt.bim, but is a maybe...
so if you have error principal on line 3, you need to check if the file exist, it command is flashing a file, if the file don't exist will not flash and a error show, and check all the command again, try and make a print screen of the process and the folder with all the file, and put it here...
if you have a full original Motorola ROM it must work, if everything check the rom is the probem.
I know i may have check everything command files it all , but i must try all possibilities.
and way you need to lock it?
i don't use mac, just windows and the PC or MAC is not the problem becouse i use that some order of commnad's last time i lock my phone but i lock just to see if is possible because after you unlocked you never need to change for noting.
bootloader have 3 stats:
Status code 0 =locked with warranty
Status code 3 = unlocked without warranty
Status code 2= re-locked but also without warranty
Status code 1 is unknown.
you can receive and install the OTA if you have the stock ROM no changes no root + stock recovery and boot images, bootloader status doesn't change a ting.
the only uses for re-locked it is to test if you can, or test if the rom is full stock or try to send for repair but in that last depending on the region it will not be repair for free, because it loses the warranty after bootloader unlock, but if yours region don't care for bootloader status, or the help center care but don't notes it you can try and have success.

Turbo firmware?

Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?

http://motofirmware.center/

Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637

Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.

jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse

Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.

Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.

http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1

TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png

dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.

Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.

The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.

TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.

When in fastboot, type "fastboot oem lock" (without the quotations"

Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")

dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope

So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk

dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin

unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?

dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.

Moto G6 Bricked NEED HELP!!!

ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
ibb.co/QmnK1cB)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291

AgentICS said:
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
Click to expand...
Click to collapse
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?

pyschodelicbros said:
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
Click to expand...
Click to collapse
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request

AgentICS said:
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
Click to expand...
Click to collapse
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash boot boot.img
mfastboot oem lock
I did this to lock the bootloader, not knowing my OS wasnt installed properly so theres no OS and my bootloader is locked.
"fastboot oem unlock"
says bootloader feature disabled
Picture of my bootloader log
[Copy link and past without the )]
ibb.co/QmnK1cB)

Ragarianok said:
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Lenovo Moto Smart assistant says device isnt recognize, it might be USB debugging due to not being able to get into the OS.
I tried getting the unique key using "fastboot oem get_unlock_data" but i get this in my CMD
[Copy link and past without the )]
ibb.co/QHD0ZcS)
I do have my orginal unique key saved in a file from when i first unlocked my bootloader and when I tried to flash it I get bootloader feature disabled.
[Copy link and past without the )]
ibb.co/0MPsZrp)
I heard that the oem unlock gets disabled for 7 days after relocking wondering if that is true???