Related
Hey there,
as it looks like there is now way of going back to ICS without unlocking the bootloader I thought about the following:
Is it possible to unlock the loader, flash ICS with the homemade fastboots, then flash the original ICS fastboot (with rslite) and relock the loader?
The last time I tried to relock it the phone was always complaining that I should start with "fastboot oem begin lock". Was this because I had no original fastboot flashed on the device? Am I right that the fastboots for rslite are the original signed ones?
Thanks in advance!
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 .
I had a stock Nexus 6 onto which I loaded the MarshMallow previews.
I then decided to go back to 5.1.1 on the basis of the final release using the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Once I had entered the final fastboot command I also stupidly entered the command to lock the bootloader prior to rebooting
Some thing went wrong and now the phone sits on the google (while letters on black background) screen on bootup.
What are my options? I can access the bootloader, but its not showing up as a device on the on "adb devices"
Any assistance would be appreciated.
Sorry to say, but you've got a paperweight.
If by some chance you switched out the stock recovery.img with TWRP you're good, but otherwise, nope.
And in bootloader you use fastboot, as in "fastboot devices", not adb.
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
petermuell said:
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
Click to expand...
Click to collapse
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Didgeridoohan said:
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Click to expand...
Click to collapse
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
danarama said:
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
Click to expand...
Click to collapse
Hmm... This got interesting. It should survive a factory flash then.
@mittu1 Did you have OEM unlock allowed prior to locking your bootloader? If so, please, please, please run the command fastboot oem unlock and return with the result.
Yes, if you have stock recovery and can't unlock bootloader (probably because "allow OEM unlock" was not checked, or whatever reason), then you're pretty much stuck. Maybe then try this: http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I think it was intended for people who had downgraded their bootloader accidentally.
There is a zip file for flashing that toggles the "allow OEM unlock" flag (http://forum.xda-developers.com/showpost.php?p=61258590&postcount=352). If you can boot to twrp and flash a zip from the computer, flash that file, then boot to bootloader and unlock BL via fastboot.
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
If you have a custom recovery (TWRP) you can, after running those commands, flash a rom through TWRP and then proceed to boot up, tick "OEM Unlocking", unlock and do whatever you then intended to do.
Edit: Or use the above mentioned zip to toggle the "OEM Unlock"-thingy...
As i understood the OP the recovery is stock also. But somebody wrote the above, and as last resort it could be tried. And if it's false info, then let's have it clarified.
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
They should, but if not, a foctory reset can be done from stock recovery. Select recovery mode, then at the Android press power and then volume up. Then select the factory reset from the menu. See if it boots after that
BUT try fastboot oem unlock first, if you wipe without that and then try to unlock I think it'll fail to unlock
Didgeridoohan said:
Hmm... This got interesting. It should survive a factory flash then.
Click to expand...
Click to collapse
No, it is just my assumption. I am not aware if something in first boot process unchecks that option.
Also, FYI, many of us have noticed that when we bought Nexus 6 and unboxed it, booted straight to bootloader, it would unlock, but after first boot on 5.0, had to enable OEM unlock in settings... so maybe first boot process after a "wipe" resets?
Will try and revert
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 ?