Re-lock bootloader without OEM unlocking

[Hyoretsu]

It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"

 

[sd_shadow]

It's been 7 days since I came back to stock already and OEM unlocking is still greyed out. Is there any way to force it true so I can relock bootloader? That happened when I first tried to unlock bootloader, but I could allow it in like 4 days
If you wanna know reasons I tried installing Custom ROMs, and on the one successful installation (AOSP Extended) it's bugged so I returned to stock and kept on trying to install CrDroid, but one day it just stopped recognizing SIMs. (After some time on stock being able to)
・It can't be a number block, since it still works on another Custom ROM+Magisk Phone
・And I'm not sure if an IMEI block would mess with a SIM from another carrier that's never touched a rooted phone. (I tested both SIMs on both slots)
・That same SIM (my original one) stopped working on an unrooted G7 Play too
・Also I can't check any of my 2 IMEIs on settings, though I could retrieve IMEI1 through "fastboot getvar all"

What does getvar all say are the codename and software channel?

Sent from my perry_f using XDA Labs

 

[Hyoretsu]

What does getvar all say are the codename and software channel?

Sent from my perry_f using XDA Labs

I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to

Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though

Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"

 

[sd_shadow]

I didn't find those specifically, but it's ocean XT1955-1 and RETBR (product/board and sku, and ro.carrier) Tried reflashing NHLOS.bin, erasing modem and flashing FSG today, didn't work and I never ran "fastboot erase all" too (by not working I mean the phone doesn't recognize a SIM is in the tray, I don't even have the emergency calls only message)
Re-flashed stock around 4 times a week ago or so, the only thing I didn't do was relock bootloader since I'm unable to

Here's the full output of getvar all if needed. (that's not the actual IMEI that's output'd) Also between those tries I sometimes could get device ID to show up instead of bad key, no idea why though

Brazil also has a site from ANATEL, the organization that manages product quality, authenticity, restrictions, user things and such, (All devices need to pass through a check from them) that allows us to see if IMEI has any restrictions (It shows if the IMEI is blocked, at least "Informed IMEI is banned by loss or theft" on a video I saw), mine has "Until now, the IMEI has no restrictions on use"

Did you check the flashfile.xml
For the official flash commands?

Sent from my Moto E (4) using Tapatalk

 

[Hyoretsu]

Did you check the flashfile.xml
For the official flash commands?

Sent from my Moto E (4) using Tapatalk

https://pastebin.com/X5TD77YS As far as I remember (just downloaded firmware file on phone) they're the same from the eraseandupdate.bat I was using
EDIT: Yeah, aside from it erasing modemst1 and modemst2 after flashing everything as opposed to after flashing FSG and reflashing FSG after that it's the same commands

 

[WoKoschekk]

OEM unlocking is still greyed out.

OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.

 

[Hyoretsu]

OEM unlock toggle is greyed out as long as your bootloader is unlocked, Magisk is not installed and you run the stock rom. That's quite normal. You must relock the bootloader to activate it. On my Moto g6 plus you find an info text there that this option is deactivated because the bootloader is already unlocked.

Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)

 

[sd_shadow]

Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)

Usually that error is caused from using the wrong relocking commands
Are you using

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

 

[sd_shadow]

And mine is greyed out too

 

[WoKoschekk]

Though all my attempts at installing only Magisk lead to a bootloop and Custom ROMs either didn't work or I spent multiple days trying to install, only being successful once. I tried relocking the bootloader, but it says I gotta check that option to do it (mine says it's already unlocked too)

Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.

I red that it's necessary to run the oem lock command a few times to make it work.

 

[Hyoretsu]

Usually that error is caused from using the wrong relocking commands
Are you using

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

I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)

Did you try to install Magisk via TWRP? Maybe older versions will work like v19.3... On my Moto g6 v20.3 leads to a bootloop, too. But v19.3 runs without any problems. Maybe it's worth a try.

Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.

 

[WoKoschekk]

I actually thought this was it, but no, I was using this thread, which has the same commands, and still got the error (2x, then 3x, reflash boot.img and oem lock)

Installing Magisk on TWRP bootable, since installing TWRP would bootloop too. Didn't try older versions though, but I might try re-writing my IMEI first, who knows if that'll work. Being able to successfully relock bootloader without a working SIM wouldn't do much good, since I'd have to format the phone to try anything afterwards.

Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.

I loose my IMEI on my Moto g6 plus, too. You won't be able to overwrite it because it is linked with your device and encrypted by Motorola. The location of these files is /persist/rfs.
If your IMEI is broken or corrupt you won't be able to restore it. Except you have a backup of your persist partition.

---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------

Try to relock your bootloader with the command provided in the screenshot (source: https://source.android.com/setup/build/running)

Screenshot
https://ibb.co/f2LzMzS

 

[Hyoretsu]

Did you try to install TWRP with the .zip provided by twrp.me? This .zip flashes the ramdisk inside the boot.img as Magisk does. So first you must install TWRP and after that you must install Magisk. Ignoring this order causes a bootloop because the twrp.zip overwrites Magisk! The twrp.zip flashes a complete new ramdisk while Magisk patches only some parts of it.

I get a bootloop when I install TWRP alone and when I install Magisk from bootable TWRP, been using the official one from twrp.me this whole time since the screen is bugged on unofficial one. I only ever installed both (in that order) when I was still trying to install Custom ROMs, but I kept getting bootloops for other reasons.

 

[MrCamby]

Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.

So install Magisk Manager

Copy the boot image from the firmware that you installed to your phone.

Run Magisk Manager, click update Magisk and Select patch boot.img

Navigate to the folder on you phone that you copied the boot image to

Wait until Magisk Manager patches it

Copy Patched_boot.img to your adb folder on your PC

From your PC command prompt:
adb reboot bootloader

Then

fastboot devices

If your phone serial # shows, then:

fastboot flash boot patched_boot.img

fastboot reboot

You should now have root and the unlock bootloader option in developer settings will not be greyed out.

There is another thread with these same instructions. That is what allowed me to relock my bootloader.


Sent from my moto g(7) power using Tapatalk

 

[MrCamby]

Also,

Now that you are able to relock your bootloader, you could hold off until 10 is out.

If you don't like the unlocked bootloader message on startup, flash the attached logo.img fileView attachment BootLogo_mg7p.zip

Sent from my moto g(7) power using Tapatalk

 

[Hyoretsu]

Do t even use twrp. Just install Magisk Manager and then patch a copy of the boot image from the firmware you installed.

So install Magisk Manager

Copy the boot image from the firmware that you installed to your phone.

Run Magisk Manager, click update Magisk and Select patch boot.img

Navigate to the folder on you phone that you copied the boot image to

Wait until Magisk Manager patches it

Copy Patched_boot.img to your adb folder on your PC

From your PC command prompt:
adb reboot bootloader

Then

fastboot devices

If your phone serial # shows, then:

fastboot flash boot patched_boot.img

fastboot reboot

You should now have root and the unlock bootloader option in developer settings will not be greyed out.

There is another thread with these same instructions. That is what allowed me to relock my bootloader.


Sent from my moto g(7) power using Tapatalk

Ty, this was the only way in which I could get root in stock. Although the Allow OEM Unlock is still greyed out it now has the same message as before I unlocked the bootloader for the first time, though if it acts the same way it'll be available in a few days. IMEIs and SIMs still aren't working though, but eh. At least I can try testing the locking bootloader theory to get them working again (IMEI not working = can't even see any of them in settings)

Also, now that you are able to relock your bootloader, you could hold off until 10 is out.

Also Motorola still allows unlocked users to receive OTA for some reason, my device updated and it's still working

 

[MrCamby]

To repair your IMEI on a G7 power, this is what worked for me:

Remove your sim card.

Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.

Startup in bootloader mode:

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.



Sent from my moto g(7) power using Tapatalk

 

[Hyoretsu]

To repair your IMEI on a G7 power, this is what worked for me:

Remove your sim card.
Pull NON-HLOS.bin and fsg.mbn from the firmware that was flashed on the phone.
Startup in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot phone. Once it is back up, powerdown, put sim card back in and start back up.

No luck unfortunately, still don't have IMEI/SIM. Once I can I'll try relocking bootloader and maybe sending it to warranty, since apparently using a tool to re-write IMEI won't work on this phone. (Followed to the T, unless unlocking it after flashing and waiting for microSD messes it up)

 

[MrCamby]

Did you try the LMSA software to try and fix it. There are two options: update and repair.



Sent from my moto g(7) power using Tapatalk

 

[Hyoretsu]

Did you try the LMSA software to try and fix it. There are two options: update and repair.

I tried using it back when I was trying to go back to stock "the right way" (to try and solve the lost IMEI, go back stock and re-lock bootloader) but it couldn't even recognize my phone so that I could download anything