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???
Related
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
alexhdkn said:
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
Click to expand...
Click to collapse
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Why would you want to relock the bootloader just to get back to close as stock as possible?
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
TechSavvy2 said:
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Device: VZW Moto X
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
Code:
fastboot oem fb_mode_set
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
KidJoe said:
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Click to expand...
Click to collapse
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
nhizzat said:
Why would you want to relock the bootloader just to get back to close as stock as possible?
Click to expand...
Click to collapse
So i can get Lollipop official!
TheBoiledDogs said:
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Already done this but it won't relock the bootloader.
alexhdkn said:
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
Click to expand...
Click to collapse
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
alexhdkn said:
So i can get Lollipop official!
Click to expand...
Click to collapse
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
edit:canceled
KidJoe said:
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
Click to expand...
Click to collapse
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
alexhdkn said:
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
Click to expand...
Click to collapse
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
KidJoe said:
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
Click to expand...
Click to collapse
I know it's an entire process and I did it last night to go back to stock 4.4.4. But I just feel safer (thieves) with the bootloader locked.
Thieves? How will having a locked bootloader protect you from thieves?
I have the XT-1052 version of Moto X and its running the Asia Retail firmware. I had unlocked the bootloader and flashed CM12 but returned to stock rom through this guide http://forum.xda-developers.com/moto-x/general/retail-firmware-uploaded-xt1052-t2976596. I will be selling the device and want to re lock the bootloader. Can i type the ''fastboot oem lock'' command in mfastboot tool and re lock the bootloader? Also, will it erase the whole data on the device?
KD25 said:
I have the XT-1052 version of Moto X and its running the Asia Retail firmware. I had unlocked the bootloader and flashed CM12 but returned to stock rom through this guide http://forum.xda-developers.com/moto-x/general/retail-firmware-uploaded-xt1052-t2976596. I will be selling the device and want to re lock the bootloader. Can i type the ''fastboot oem lock'' command in mfastboot tool and re lock the bootloader? Also, will it erase the whole data on the device?
Click to expand...
Click to collapse
Yes, fastboot oem lock will lock it, and no it will not wipe data. Only unlocking wipes data.
But you status code will show relocked you can never get status code back to locked once unlocked.
Travisdroidx2 said:
But you status code will show relocked you can never get status code back to locked once unlocked.
Click to expand...
Click to collapse
Correct. Whoever has the phone will be able to see the "tamper seal" that shows the bootloader was previously unlocked, but is now locked again.
I would provide whoever you sell the phone to the bootloader unlock code so they can unlock in the future if they so desire. Not sure if they can request the code from Motorola again or not.
fury683 said:
Correct. Whoever has the phone will be able to see the "tamper seal" that shows the bootloader was previously unlocked, but is now locked again.
I would provide whoever you sell the phone to the bootloader unlock code so they can unlock in the future if they so desire. Not sure if they can request the code from Motorola again or not.
Click to expand...
Click to collapse
I tried it but it asks me to flash the signed images. The link i mentioned above comes with an XML file which dictates the steps RSD should be following, right? So if i upload the XML file can you edit the command line and add the command? I am not an expert in this stuff.
i have relocked flashing manually with fastboot, not sure if you add the oem lock cmd to the xml will work.
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
hbenz2008 said:
i have relocked flashing manually with fastboot, not sure if you add the oem lock cmd to the xml will work.
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
Click to expand...
Click to collapse
The files that are present in the rom folder are boot.img, fsg.mbn, gpt.bin, logo.bin, motoboot.img, NON-HLOS.bin, recovery.img and system.img. Can you modify the list of commands to add the aditional files. Thanks.
just flashing the above is enough to relock. Flash away
Wireless...
hbenz2008 said:
just flashing the above is enough to relock. Flash away
Wireless...
Click to expand...
Click to collapse
Thanks man. Will update about how it goes.
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.
Hey guys
I have a Moto X XT1052- The Indian Version.
I rooted my phone a few weeks back and I've decided that I don't want root access anymore.
I have unrooted my phone from the SuperSU app by clicking the clean up button.
Now I can't find anything as to how to relock the bootloader. I don't really need the warranty to be active again but if there is a way to do that it would be appreciated.
Also I need help to remove the bootloader unlocked warning message to be removed as well.
Please be clear in your explanations as I'm new to all this.
I have attached details about my phone to this post.
Thanks in advance
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
bronko15344 said:
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
Click to expand...
Click to collapse
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as you are re-flashing the EXACT same rom that is on your phone, and your battery is 100% charged before starting. In other words,as always, if the battery goes dead during the process, there is a potential to brick, and DOWNGRADING your ROM is not good.
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
KidJoe said:
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as your battery is 100% charged before starting. (in other words,as always, if the battery goes dead during the process, there is a potential to brick)
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
Click to expand...
Click to collapse
Thank you so much
RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
If you used the "Full Unroot" option in the app it should revert all changes which are made during the root process. To be sure that your system partition is completely stock you can flash it with fast boot (this won't delete your installed apps and data)
To do this look into this guide
guide-moto-x-return-to-100-stock
Short version:
1.
Download and extract the sbf flies matching your phone and carrier from here:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
To decide which file you need to download:
info-tip-web-sites-official-leaked-roms
2. (this step is necessary to remove your warning message)
ghost-original-bootanimations-unlocked
download the standard boot animation and extract the logo.bin and overwrite the logo.bin from the sfb files.
3.
now flash the system partition, kernel, recovery and the new logo (without the warning) with the following commands: (Note: For flashing system.img you MUST use mfastboot instead of fastboot. It's to big for the normal fast boot. So no typo here)
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
Don't execute the following command as this will delete all your data/installed apps etc.
Code:
fastboot erase userdata
That should be sufficient to revert everything what was changed during the root process. Check if everything looks like it was was on stock rom (including the recovery and the bootlogo)
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
But actually I would not relock your boot loader since you gain nothing and if you want to unlock it again all your data will be erased during the unlock process. and since you are not rooted you can't backup everything before...
Edit: Like @KidJoe said. If you accepting an OTA than the warning comes back. so if you relock your bootloader you can't hide that message without unlocking (and loosing all your data) again. Just stay on the unlocked bootloader
bronko15344 said:
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
.
Click to expand...
Click to collapse
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
KidJoe said:
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
Click to expand...
Click to collapse
Oh wasn't aware that you directly have to flash a firmware to relock the bootloader. Thank you
hey how u do u unlock ur moto x t1052 .
Hello mens,
i need a little help with locking bootloader on my Moto G6 (and flash stock rom). I try some treble rom and after that i want to go on stock, so i want to follow this tutorial https://animetrick.com/flash-stock-rom-moto-g6-plus-locked-bootloader-2018/ but without succes. My problem is that i cant swich off "enable oem unlock" from developer setting (it is grey and untouchable) and cant lock bootloader before flashing stock rom. Anybody know some solution ?
I don't think you can lock the bootloader before flashing stock. With a locked bootloader you can't modify system partition. Forget about the switch. Just install stock rom and then relock your bootloader using the guide. When you follow the guide, which doesn't mention the switch, you will reflash stock via fastboot commands, and relock the bootloader via fastboot. Pretty sure the switch will rest itself.
Sent from my moto g(6) plus using Tapatalk
Solves
So, i decide use mobile with root and Magis, so I flash Rom, patched boot image and use phone in this status. Now I look into settings and OEM unlocking button is available. WTF ?
Just saying if your attempting to relock the bootloader to do a warranty replacement you cant. The bootloader can be unlocked and Moto even tells you how to. But once you unlock the bootloader once the warranty is void weather you relock it or not. In fact even requesting the unlock key can void the warranty.
To block the bootloader you need to re-authorize unlocking it in the developer options with the OEM unlock button. If the OEM unlock button is gray and unavailable you need to install root and then the button will unlock. Sam had such a situation and write what I did to make everything went without error.
Of course, USB and ADB drivers must be installed.
- Install ROOT, start the device
- Go to the developer options on your phone
- Enable authorization to unlock with the OEM unlock button
- Enable USB debugging
- Unpack the system files to a folder with ADB
- Unpack the file "FLASH_OEM_LOCK.zip" to the same folder (download below)
- Start the phone in bootloader mode and connect to the computer
- Click on the file "FLASH_OEM_LOCK.bat"
- After the procedure the phone will boot, the bootloader will be blocked, and in the developer's options the "OEM unlock" button will be available
Note: The procedure erases all data, the phone will start up as "New" with a clean system.
I did it for my own needs but maybe it will help someone.
Tested on my Moto G6 (XT1925-5)
I try to relock my Moto G6plus xt1926-3 also with stockrom flashed (after trying lineageos) but have some problems.
I cant flash something after the two "fastboot flash oem lock". It gives "remote failure" (bootloader flash permisson...) error.
After relock with oem lock, a message "incompatible operating system" is displayed before boot.
But I can unlock it again without problems. (and install magisk for example or boot twrp).
I can switch the oem unlock in dev settings to on too (in unlocked boot), but the script gave me same error.
I want only to revert to stockrom (-89 or older) and locked bootloader.
What am I doing wrong?
I could flash with locked bootloader (magisk, enable option in dev and proper fastboot version)
But I get the message "your device has loaded a different operation system"... I have flashed complete stock
*weird*
EDIT: unlocked, flashed bootloader again and relocked, but message keeps.
Have the same issue. I tried to relock my Moto G6plus xt1926-3 Android Pie also with stockrom flashed (after Ressurrection) but had some problems.
I couldnt flash anything after the two "fastboot flash oem lock". It gives "remote failure" (bootloader flash permisson...) error.
After relock with oem lock, a message "incompatible operating system" is displayed in boot.
---------- Post added at 09:53 PM ---------- Previous post was at 09:34 PM ----------
Garfield9992003 said:
I try to relock my Moto G6plus xt1926-3 also with stockrom flashed (after trying lineageos) but have some problems.
I cant flash something after the two "fastboot flash oem lock". It gives "remote failure" (bootloader flash permisson...) error.
After relock with oem lock, a message "incompatible operating system" is displayed before boot.
But I can unlock it again without problems. (and install magisk for example or boot twrp).
I can switch the oem unlock in dev settings to on too (in unlocked boot), but the script gave me same error.
I want only to revert to stockrom (-89 or older) and locked bootloader.
What am I doing wrong?
Click to expand...
Click to collapse
Garfield9992003 said:
I could flash with locked bootloader (magisk, enable option in dev and proper fastboot version)
But I get the message "your device has loaded a different operation system"... I have flashed complete stock
*weird*
EDIT: unlocked, flashed bootloader again and relocked, but message keeps.
Click to expand...
Click to collapse
Hi? have you tried this https://forum.xda-developers.com/g6-plus/how-to/2-returning-to-stock-t3854243 ?