Related
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?
I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!
tbiwalkar said:
I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!
Click to expand...
Click to collapse
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.
doppelhelix said:
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.
Click to expand...
Click to collapse
I understand but then how am i able to flash logo.bin?
tbiwalkar said:
I understand but then how am i able to flash logo.bin?
Click to expand...
Click to collapse
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.
doppelhelix said:
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.
Click to expand...
Click to collapse
I am locked and still i am able to flash various logo.bin files using mfastboot
tbiwalkar said:
I am locked and still i am able to flash various logo.bin files using mfastboot
Click to expand...
Click to collapse
Interesting. Thanks for the input. learned somthing new..[emoji4]
I have a Nexus 6 that came rooted and with busybox.
how do I know if the bootloader has been unlocked?
You can't root it without unlocking the boot loader, so if its rooted then that's all the evidence you need
caguas56 said:
I have a Nexus 6 that came rooted and with busybox.
how do I know if the bootloader has been unlocked?
Click to expand...
Click to collapse
Also, as soon as you turn on the phone, the black screen with the white Google logo comes up, on the bottom of the screen should show and unlocked padlock. That also means your bootloader is unlocked.
do you see an open padlock on the bottom of the screen while booting? then it's unlocked. also, you can boot into the bootloader, itll say unlocked. but if you already havd root, its probably unlocked, or he relocked it. if you have root, you can use an app to re unlock it.
simms22 said:
do you see an open padlock on the bottom of the screen while booting? then it's unlocked. also, you can boot into the bootloader, itll say unlocked. but if you already havd root, its probably unlocked, or he relocked it. if you have root, you can use an app to re unlock it.
Click to expand...
Click to collapse
you are right, I see the padlock unlocked and the word "unlocked" on the bootloader screen.
thanks.
I'm coming from a Samsung device and have no idea how to flash roms on a Motorola device.
any suggestions you can give me?
caguas56 said:
you are right, I see the padlock unlocked and the word "unlocked" on the bootloader screen.
thanks.
I'm coming from a Samsung device and have no idea how to flash roms on a Motorola device.
any suggestions you can give me?
Click to expand...
Click to collapse
I suggest you start with this, to learn adb fastboot and flashing.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.
Also, give this a read:
http://forum.xda-developers.com/showthread.php?t=2948481
Sent via Tapatalk on Shamu
Davzone said:
I suggest you start with this, to learn adb fastboot and flashing.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.
Click to expand...
Click to collapse
Last question : is there anyway to change the icons colors and shape on the notification bar like wifi, signal etc?
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.
I had a rooted (magisk) X4 (google_fi) with twrp 3.2.1. I removed root and reflashed the stock rom (OPW27.1) and relocked the bootloader.
Everything works fine even the OTA updates (I OTA'd back up to OPWS27.1.3, but there is an annoying yellow startup screen that displays "My device has loaded a different operating system." From what I read it's because the ROM isn't digitally signed? Is that correct?
Any way to remove this screen on startup?
**FYI this is not the unlocked bootloader screen this is something else.
Thanks.
Ok so google pay won't work. It says I have an unlocked bootloader and/or custom software. I have a stock rom, recovery, bootloader, and the bootloader is locked. Shouldn't it work? I never had this problem after flashing stock and relocking my old Moto X Pure.
ptn107 said:
reflashed the stock rom (OPW27.1)
Click to expand...
Click to collapse
I am not able to help with removing the boot message you're seeing, but is that copy of the stock rom you flashed still available and is it for Android One/Fi?
Yes and yes.
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
did you managed to remove the message? I'm having the same problem
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
CypherPotato said:
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
Click to expand...
Click to collapse
Hi, I have the same problem and I have flashed the rom of this post. How could it be solved?. Thanks.
ptn107 said:
Yes and yes.
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Does this help?
jsis83 said:
Hi, I have the same problem and I have flashed the rom of this post. How could it be solved?. Thanks.
Click to expand...
Click to collapse
How have u flashed it?
My payton bootloader is blocked and I can't unlock it.
How did u unlocked your bootloader?
CypherPotato said:
How have u flashed it?
My payton bootloader is blocked and I can't unlock it.
How did u unlocked your bootloader?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-x4/
CypherPotato said:
My theory:
You've flashed an original signed stock rom, but that stock rom signature is not the same of the bootloader.
Click to expand...
Click to collapse
How to solve this?
so are we all mad? I've googled for hours, it seems to be you need a factory image of our phones to correct this problem.
figured it out, you need to supply your own keystore to remove the message in fastboot
https://youtu.be/OfWFmhucWlg?t=15m33s
how do you match rom to the correct bootloader? I've installed the 8.0.0 rom I get the same boot error as stated above. I'm trying to get everything back to stock to get the 8.1 update
we would need a factory image, that Motorola never will provide..
squanchy said:
we would need a factory image, that Motorola never will provide..
Click to expand...
Click to collapse
Isn't this exactly that?
https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
jhedfors said:
Isn't this exactly that?
https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Click to expand...
Click to collapse
if it was a real factory image it would contain a developer keystore in the image, and people wouldn't get the yellow bootloader warning message..
Like I get from all these images posted on this Forum.
If the Keystore doesn't match your original phones Hardware Keystore, it uses the Image's keystore instead. A factory Image, has no keystore or sometimes a universal keystore, and you won't get the mentioned error.
I obtained all this information just watching a Android Developer talk about Verified Booting, but it never goes into detail how to remedy this issue. So unless I spend hours and hours learning how to re-compile an image from source, or figure out where my keystore is located, I'll be stuck with this message.
Because each manufacturer is different, they don't always follow the same Practices.
Hi, is there anyone who fix it finally? I have exactly the same problem. After update on Pie, the message "verity mode is set to disable" is displayed while booting. I'm desperate, I really don't know how to fix it. I tried almost everything
PlaviiCZ said:
Hi, is there anyone who fix it finally? I have exactly the same problem. After update on Pie, the message "verity mode is set to disable" is displayed while booting. I'm desperate, I really don't know how to fix it. I tried almost everything
Click to expand...
Click to collapse
You can't just ignore it? It does not affect functionality.
ptn107 said:
You can't just ignore it? It does not affect functionality.
Click to expand...
Click to collapse
I think it does, Google Pay cannot add my debet card cause it says "Your device is rooted or customized".