Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
I know this is an older post but I've been unable to find the instructions for re-locking the bootloader. Any help would be appreciated.
I had the electrify m, the RAZR m for us cellular, and I unlocked it through Motorola. I was giving it to someone else and wanted to relock it and never found any instructions to do so. I contacted Motorola and they said once it was unlocked the was no way to relock. I would guess it's the same with the moto x.
Sent from my XT1055 using Tapatalk
fastboot oem lock doesn't work?
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Sent from my XT1058 using xda app-developers app
I tried it with my electrify m and it wouldn't work.
Sent from my XT1055 using Tapatalk
https://plus.google.com/110773150384694258853/posts/XUF8UP9iVfi
Here's how from p3droid
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
mschumacher69 said:
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
Click to expand...
Click to collapse
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Sent on my Moto X
flashallthetime said:
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Click to expand...
Click to collapse
Even if u re-lock the bootloader?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
planktoid said:
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Click to expand...
Click to collapse
Has anyone tried re-locking the bootloader of their Moto X??
mschumacher69 said:
Has anyone tried re-locking the bootloader of their Moto X??
Click to expand...
Click to collapse
Does not work for me. I get:
No valid PIV block in SP for system
chaoslimits said:
Does not work for me. I get:
No valid PIV block in SP for system
Click to expand...
Click to collapse
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
mschumacher69 said:
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
Click to expand...
Click to collapse
Went back to stock 4.4 via RSD Lite then tried to relock.
chaoslimits said:
Went back to stock 4.4 via RSD Lite then tried to relock.
Click to expand...
Click to collapse
Which model/carrier do u have?
mschumacher69 said:
Which model/carrier do u have?
Click to expand...
Click to collapse
Vzw Dev Edition
chaoslimits said:
Vzw Dev Edition
Click to expand...
Click to collapse
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mschumacher69 said:
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
chaoslimits said:
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
Click to expand...
Click to collapse
Weird. So is ur phone bricked now or it just did not lock?
Related
I HATE the unlock warning message and want it gone but don't want to relock.
I have an unlocked and rooted Verizon Dev Ed Moto X running stock 4.4. I downloaded and unzipped the 4.4 factory images and tried flashing logo.bin using:
mfastboot flash logo logo.bin
It flashed, but I still have that bleeping warning message. Is there a known way to get rid of it without relocking?
Can I delete the file that has the warning message somehow? Anyone know what it is called?
Cozume said:
I HATE the unlock warning message and want it gone but don't want to relock.
I have an unlocked and rooted Verizon Dev Ed Moto X running stock 4.4. I downloaded and unzipped the 4.4 factory images and tried flashing logo.bin using:
mfastboot flash logo logo.bin
It flashed, but I still have that bleeping warning message. Is there a known way to get rid of it without relocking?
Can I delete the file that has the warning message somehow? Anyone know what it is called?
Click to expand...
Click to collapse
i think the only way to remove that is the change the boot animation
dray_jr said:
i think the only way to remove that is the change the boot animation
Click to expand...
Click to collapse
Can you point me to anything that would tell me how to do that? thanks!
Cozume said:
Can you point me to anything that would tell me how to do that? thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2417961
http://forum.xda-developers.com/showthread.php?t=2590034
http://forum.xda-developers.com/showthread.php?t=2445150
dray_jr said:
http://forum.xda-developers.com/showthread.php?t=2417961
http://forum.xda-developers.com/showthread.php?t=2590034
http://forum.xda-developers.com/showthread.php?t=2445150
Click to expand...
Click to collapse
thanks again, off to read!
I hit the thanks button too many times last night and now I am not allowed to do it today any more. I will come back and thank you tomorrow!
hi everyone,
so i flashed the twrp recovery image and then my phone got stuck in a bootloop. So stupidly I relocked the bootloader and now i can't do nothing. any ideas?
No you NEVER relock the bootloader. (unless everything is fine)
There is another thread here where they were close to a solution but I didn't see the final outcome.
Sorry man. Good luck
Sent from my Google N6 on VZ
fastboot
valapsp said:
hi everyone,
so i flashed the twrp recovery image and then my phone got stuck in a bootloop. So stupidly I relocked the bootloader and now i can't do nothing. any ideas?
Click to expand...
Click to collapse
Boot to boot loader...fastboot OEM unlock confirm unlock..let the spinning android wipe your sdcard..good to go
jamescable said:
Boot to boot loader...fastboot OEM unlock confirm unlock..let the spinning android wipe your sdcard..good to go
Click to expand...
Click to collapse
u cant fastboot oem unlock when the "allow oem unlock" box hasnt been checked.
DebianDog said:
No you NEVER relock the bootloader. (unless everything is fine)
There is another thread here where they were close to a solution but I didn't see the final outcome.
Sorry man. Good luck
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
ya i know. i was drunk!
valapsp said:
ya i know. i was drunk!
Click to expand...
Click to collapse
Did you ever ticked Allow OEM Unlock before re locking?
Check this post.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/page16
There is a FIX.
sotnasnauj said:
Did you ever ticked Allow OEM Unlock before re locking?
Check this post.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/page16
There is a FIX.
Click to expand...
Click to collapse
That's not what is being said. He is saying there *may* be a link. But only 2 people have managed to fix it with that thread and 1 of them was actually bricked first, not like this but with a broken bootloader... So actually only 1 person may have fixed it with that thread.
valapsp said:
ya i know. i was drunk!
Click to expand...
Click to collapse
LOL I have been there
Sent from my Google N6 on VZ
hello guys ) i just wanna ask if its possible to flash android m with nexus root toolkit or no ??
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
jj14 said:
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
Click to expand...
Click to collapse
thank you for the fast reply
Yes I followed those steps and flashed it perfectly.
BossJ said:
Yes I followed those steps and flashed it perfectly.
Click to expand...
Click to collapse
yeah same here, everything went more then well.
Should I relock the bootloader after flashing M ?
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
NOOO!!!!
To many folks have encountered an issue that soft-bricked their device afterwards.
You will still receive OTA with an unlocked bootloader.
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
stricker said:
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
Click to expand...
Click to collapse
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
danarama said:
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
Click to expand...
Click to collapse
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
danarama said:
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
Click to expand...
Click to collapse
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you like.
Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.
May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095
I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.
Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095
Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?
Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..
The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png
Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.
Hello everyone, everything good?
How do I access EDL mode on the moto z3 play, please?
Thank you,
Josenil Santana
josenilsantana said:
Hello everyone, everything good?
How do I access EDL mode on the moto z3 play, please?
Thank you,
Josenil Santana
Click to expand...
Click to collapse
Is the bootloader unlocked?
Sent from my Moto E (4) using Tapatalk
Unfortunately not, I made a mistake when flashing the rom stock, the script contained the command to block the bootloader before the rom stock ended the process.
sd_shadow said:
Is the bootloader unlocked?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
josenilsantana said:
Unfortunately not, I made a mistake when flashing the rom stock, the script contained the command to block the bootloader before the rom stock ended the process.
Click to expand...
Click to collapse
if you have stock boot (unaltered by Magisk) try LMSA.
I just went through a nightmare, and LMSA saved my phone. But it would only work if my bl was stock.
considering how your BL is locked, I think you can recover your phone in LMSA, then unlock it and chew bubblegum.
Unfortunately not. The LMSA recognizes the cell phone but does not flash stock ROM. I will have to send for technical assistance. Crying. Thanks for listening.
kewlzter said:
if you have stock boot (unaltered by Magisk) try LMSA.
I just went through a nightmare, and LMSA saved my phone. But it would only work if my bl was stock.
considering how your BL is locked, I think you can recover your phone in LMSA, then unlock it and chew bubblegum.
Click to expand...
Click to collapse
josenilsantana said:
Unfortunately not. The LMSA recognizes the cell phone but does not flash stock ROM. I will have to send for technical assistance. Crying. Thanks for listening.
Click to expand...
Click to collapse
can you sideload the firmware?
I don't have stock recovery working
kewlzter said:
can you sideload the firmware?
Click to expand...
Click to collapse
Did you get into EDL mode? I have my moto z3 play XT1929-6 with the booloader of the XT1929-4 and I get an error when trying to update it with LMSA or fastboot
YggCraft said:
Did you get into EDL mode? I have my moto z3 play XT1929-6 with the booloader of the XT1929-4 and I get an error when trying to update it with LMSA or fastboot
Click to expand...
Click to collapse
I had to flash bootloader and recovery from the downloaded LMSA firmware zip, then LMSA worked fine.