Database Info

Relock the Bootloader

Hi,
I want to give my unlocked Moto G to a family member - and I'd like to relock the bootloader again, for security reasons.(I don't care about the warranty)
is there a way to do that?

RazorHail said:
Hi,
I want to give my unlocked Moto G to a family member - and I'd like to relock the bootloader again, for security reasons.(I don't care about the warranty)
is there a way to do that?
Click to expand...
Click to collapse
open FAQ
ctrl+f : "relock"

matmutant said:
open FAQ
ctrl+f : "relock"
Click to expand...
Click to collapse
thanks,
I've already tried that.
But when I enter "fastboot oem lock", I get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Click to expand...
Click to collapse
when I enter the suggested "fastboot oem lock begin", I get:
(bootloader) Ready to flash signed images
Click to expand...
Click to collapse
I'm not sure what that's suppose to mean.....I already downloaded the official firmware images and flashed those immediately after I get this message........but it still says that the bootloader is unlocked.
And immediately returning back to the bootloader and typing in "fastboot oem lock" still won't work - same message as before...
am I missing something?

RazorHail said:
thanks,
I've already tried that.
But when I enter "fastboot oem lock", I get:
when I enter the suggested "fastboot oem lock begin", I get:
I'm not sure what that's suppose to mean.....I already downloaded the official firmware images and flashed those immediately after I get this message........but it still says that the bootloader is unlocked.
And immediately returning back to the bootloader and typing in "fastboot oem lock" still won't work - same message as before...
am I missing something?
Click to expand...
Click to collapse
Yup, this "unlock-relock" is WIP yet ..

i done a relock last week and this works for me.use adb command "fastboot oem lock begin" go through the routine to flash factory firmware image and use "fastboot oem lock" command to finish after you flashed factory firmware.

akaygee said:
i done a relock last week and this works for me.use adb command "fastboot oem lock begin" go through the routine to flash factory firmware image and use "fastboot oem lock" command to finish after you flashed factory firmware.
Click to expand...
Click to collapse
So, steps are these:
1: fastboot oem lock begin
2: flash stock firmware
3: fastboot oem lock
And BL will be locked again. Correct me if i'm wrong.
Problem is that for "unlocked" we need always of a code by motorola atm.

denzel09 said:
So, steps are these:
1: fastboot oem lock begin
2: flash stock firmware
3: fastboot oem lock
And BL will be locked again. Correct me if i'm wrong..
Click to expand...
Click to collapse
thats how it works on most motorola android phones i have used ,it works fine on my moto g so yes that is right.
like so
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock

akaygee said:
thats how it works on most motorola android phones i have used ,it works fine on my moto g so yes that is right.
like so
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Click to expand...
Click to collapse
for me not working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danger2u said:
for me not working
Click to expand...
Click to collapse
you didn't flash factory firmware in between

akaygee said:
you didn't flash factory firmware in between
Click to expand...
Click to collapse
i have some problem when i try to flash the system img

this is just a quick howto am at work....
the files you need and will use are in moto g section of this forum.
firmware's here
http://forum.xda-developers.com/showthread.php?t=2546251
relock bootloader
=============
keep in mind this will remove any and all personal files and settings
like any self respecting android user you have made backups right....!!!! GOOD
download adb and fastboot extract or place into a directory.
now download the factory firmware image of your phone extract zip/rar and place into the same directory.
download "relock bootloader.txt" rename to "relock bootloader.bat" place this in the same directory as the files and double click it ,this would save you typing in all the commands from below in by hand and does it all for you.recap....if you did download and run relock bootloader.bat you dont need to type anything form below
open a command prompt as administrator ,navigate to the directory where you placed all the files we are working with and type as follows giving time for each command to finish.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock

When we ask the motorola unlock code, this does not imply that we actually unlock the bootloader.
I mean, i can ask to motorola to unlock code but i can decide to unlock also after sometimes, who stops me.
So, i think that when we relock bootloader, also if previously we asked an unlock code, we are ok, for what i writed above. How can they to be sure that bootloader has been really unlocked in case of brick or hardware failure ?

denzel09 said:
When we ask the motorola unlock code, this does not imply that we actually unlock the bootloader.
I mean, i can ask to motorola to unlock code but i can decide to unlock also after sometimes, who stops me.
So, i think that when we relock bootloader, also if previously we asked an unlock code, we are ok, for what i writed above. How can they to be sure that bootloader has been really unlocked in case of brick or hardware failure ?
Click to expand...
Click to collapse
the boot loader has a status indicator.phone shops/retailers probably won't check it but motorola will.

akaygee said:
the boot loader has a status indicator.phone shops probably won't check it but motorola will.
Click to expand...
Click to collapse
Understood, i had read something in an other post, so to complete the "opera" we need to 'something' to reset that count/status? Like on samsung device, s2 et similia?

denzel09 said:
Understood, i had read something in an other post, so to complete the "opera" we need to 'something' to reset that count/status? Like on samsung device, s2 et similia?
Click to expand...
Click to collapse
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.

akaygee said:
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
Click to expand...
Click to collapse
wth i just doing wrong???
the firmware is Blur_Version.14.91.11.falcon_umts.Retail.en.DE
he gives me this error and on the phone says failed to validate system image

akaygee said:
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
Click to expand...
Click to collapse
Motorola talked about a fuse that is "burned" when unlocking, that's why they know, even after relocking
_________________________
i need to update FAQ about relocking (i never ever needed to relock a bootloader myself )
So for relocking, i would like to directly link your post @akaygee, please duplicate it in FAQ thread . then, i'll ask the current thread to be moved to Q&A.

@danger2u
interesting ,are you using a carrier branded phone.? that or the bootloader is locked
i used this method on a uk retail moto g and never run into any problems

akaygee said:
interesting ,are you using a carrier branded phone.?
i used this method on a uk retail moto g and never run into any problems.
Click to expand...
Click to collapse
no is not branded
i bought from italian retail store
now i will try to flash with uk firmware

matmutant said:
Motorola talked about a fuse that is "burned" when unlocking, that's why they know, even after relocking
_________________________
i need to update FAQ about relocking (i never ever needed to relock a bootloader myself )
So for relocking, i would like to directly link your post @akaygee, please duplicate it in FAQ thread . then, i'll ask the current thread to be moved to Q&A.
Click to expand...
Click to collapse
So it will be impossible to reset that status ?

How to Re-Lock GPE?

Like an idiot i bought a GPE and didnt realize its not 4g, and has issues w/ tmobile. Then unlocked it soon as I got it.
How do I re-lock it? The command does not seem to work
I am always Given "Failed to validate system image"

Anyone? Beuller?

You'll have to first start by issuing the command 'fastboot oem lock begin' while booted to the bootloader.
Then find the procedure to flash the stock firmware to the GPE and do that.
Then after that is finished issuing the command "fastboot oem lock' and it will relock your bootloader.
However once the bootloader is unlocked it is not set back to 'locked' once relocked; It is set to 'relocked', so they could possibly still tell the difference if they are paying attention.

CodyF86 said:
You'll have to first start by issuing the command 'fastboot oem lock begin' while booted to the bootloader.
Then find the procedure to flash the stock firmware to the GPE and do that.
Then after that is finished issuing the command "fastboot oem lock' and it will relock your bootloader.
However once the bootloader is unlocked it is not set back to 'locked' once relocked; It is set to 'relocked', so they could possibly still tell the difference if they are paying attention.
Click to expand...
Click to collapse
I tried that, thats when I get the error I mentioned above.

You'll probably need to use mfastboot.exe instead of fastboot.exe. Which one are you using?

CodyF86 said:
You'll probably need to use mfastboot.exe instead of fastboot.exe. Which one are you using?
Click to expand...
Click to collapse
mfastboot.
Is it possible it has to do with the fact it got the 4.4.4 update?

Any help would be great. If not then I'll just try and resell it.

Someone must have something I can try.

WHen i to to restore I get this message on these files
mfastboot flash partition gpt.bin - Version downgraded for primary_gp
mfastboot flash motoboot motoboot.img - Version downgraded for tz
mfastboot flash boot boot.img - Version downgraded for boot

I'd love any input at all.

guess not

[HELP] XT1563 Bricked after trying to root it

After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?

If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.

TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?

MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:

TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.

Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)

Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB

Downgrading Firmware and Locking the Bootloader

I am trying to lock the bootloader while restoring all the stock images.
These are the commands I used:
fastboot devices
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
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
"fastboot flash partition gpt.bin" failed giving me "preflash validation failed".
After some research I found out that it was because I was trying to flash older firmware, and downgrading of firmware wasn't possible.
So, what's the solution here? How do I lock the bootloader and restore the stock images and firmware, and downgrade properly?
I was previously on Lineage OS Nougat 7.1.2.
I downloaded the correct stock images from https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639.
Specifically XT1541_OSPREY_RETEU_2GB_6.0.1_MPIS24.107-55-2-5_cid7.

I'm afraid you'll have to wait till a newer stock firmware is released. The bootloader cannot be locked if the system is not 100% stock.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
I'm afraid you'll have to wait till a newer stock firmware is released. The bootloader cannot be locked if the system is not 100% stock.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I had Nougat 7.1.2 with Lineage OS. I don't think Motorola is ever going to update the firmware of the Moto G 2015 to anything above 6.0.1. Does that mean that there is nothing I can do?
Is there any other way I can downgrade and lock?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
"I get a 'Preflash validation' error when flashing a Firmware Image
The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip."
Can anyone explain the parts in bold? I have an unlocked bootloader. If I flash a ROM zip will it downgrade? Can I flash the stock images and lock afterwards?

nomuzephyr said:
I had Nougat 7.1.2 with Lineage OS. I don't think Motorola is ever going to update the firmware of the Moto G 2015 to anything above 6.0.1. Does that mean that there is nothing I can do?
Is there any other way I can downgrade and lock?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
"I get a 'Preflash validation' error when flashing a Firmware Image
The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip."
Can anyone explain the parts in bold? I have an unlocked bootloader. If I flash a ROM zip will it downgrade? Can I flash the stock images and lock afterwards?
Click to expand...
Click to collapse
Well, there are some TWRP flashable stock rom available in a separate post. I think lost101 was referring to them. Still, I can't say for sure if they would work for locking.
You can still downgrade safely, just ignore the preflash validation for gpt.bin and bootloader.img. But you can't lock it that way.
Broadcasted from Zeta Reticuli

bump
Anyone else have more info?

nomuzephyr said:
bump
Anyone else have more info?
Click to expand...
Click to collapse
1st
Relocking bootloader will not restore the warranty.
2nd
Flash as you wrote without oem lock... commands, repeat any command if error. Don't reboot.
3rd
Flash as... with oem commands.
It works for some Moto models.

HELP! I Still Cant Re-Lock bootloader

i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
Code:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot oem lock begin
fastboot oem lock begin
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot.exe erase carrier
fastboot.exe erase userdata
fastboot.exe erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
pause
when i run
Code:
fastboot oem lock
the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?

MadMan29729 said:
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
when i run the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
Click to expand...
Click to collapse
(coming from flashing stock)
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock

vinoxflame said:
(coming from flashing stock)
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
that worked! Thanks!

that didn't lock mine
C:\ADB>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.993s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.763s]
finished. total time: 1.760s
C:\ADB>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.014s

your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..

MadMan29729 said:
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
Click to expand...
Click to collapse
So have to to root it first, then lock the bootloader?

endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
Yeah that doesn't sound like a good idea.
Sent from my mata using XDA Labs
---------- Post added at 05:58 AM ---------- Previous post was at 05:56 AM ----------
Make sure you have the correct software channel
Sent from my mata using XDA Labs

yes cause that's what I had to do cause motorola won't let you relock it unless you flash the factory firmware along with the lock command but you can't lock it without checking allow oem unlock

endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
its the only way to get rid of the bootloader error that says you need to enable Allow OEM Unlock.. rooting with magisk just forces the allow oem unlock to be enabled.. so you can check it..
as far as locking.. once you run the lock commands you have to flash the factory images then run the lock command again.. therefore you won't be rooted in the end!

Question for anyone who may know ..
So if we're already rooted and we would like to lock our bootloader we have to flash our factory image and type in the bootloader lock command as well?
Anyone successfully locked there bootloader?
If we have an unlocked bootloader and we lock it can we return back to unlocked bootloader immediately afterwards? Has anyone done this? Do we use same method as we initially did to unlock our bootloader? I only say that because I do not have my original code for my bootloader unlock that I used. If we go about it same way will Motorola give us the code again or do we need to still have those #s that we originally used?
I'm on a mission now. Soon as I comment this I'll search my butt off for a while and see what all I can figure out. If I get any good solid information I shall return here and share it for sure. Good day to everyone.
---------- Post added at 07:21 PM ---------- Previous post was at 07:08 PM ----------
Credit to @smokinu from motp G7 River forum. I'm pasting the comment here below.
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Above is from post #34 here: https://forum.xda-developers.com/mo...are-29-114-t3913673/post79305396#post79305396 And I'm quite sure the same method will work for Power although I have not tested this. Pretty sure it will though.

In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Sent from my moto g(7) power using Tapatalk

MrCamby said:
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Click to expand...
Click to collapse
Thanks for the info! I always just assume on any device that bootloader can't be downgraded. When I first get the device anyway.. thanks!

can you help me relock bootloader of motorola one p30 play? i am having same issue even after typing
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
it still says "still require signed boot.img"
also i have a dual slot partition slot phone