I just unlocked the bootloader of the Moto X4 and at the start appears the original logo and then the notice that the bootloader was unlocked, how do I remove it?
The other, can you block later?
It's been said throughout this section, Reddit, Lenovo forums, there's no return from unlocking bootloader until Lenovo releases signed factory images. Safety net will trip unless you use magisk and no more official OTAs.
No removing that notice. When you do flash any of these linked stock firmwares, you'll get another notice your firmware is different.
Related
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
STEyeAndroid said:
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
Click to expand...
Click to collapse
I would start here: http://forum.xda-developers.com/showthread.php?t=2536200
I don't know why the unlocked bootloader warning screen would stay set if you relocked it, but you can change that screen to display whatever you want. See here for details:
http://forum.xda-developers.com/showthread.php?t=2417961
Since you have the dev edition, you should be able to unlock, install TWRP, and root without slapmymoto or pwnmymoto. I did it all AFTER installing the latest OTA, and I had no trouble.
I have not used RSDLite, but that is the way I understand it.
STEyeAndroid said:
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
Click to expand...
Click to collapse
Sell or trade your dev edition. Installing SafeStrap on that phone is such a waste of time and energy.
Or read more. There are ways to remove the boot logo screen.
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
STEyeAndroid said:
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
Click to expand...
Click to collapse
It appears to. And the statement about still receiving the unlocked bootloader warning after re-locking the bootloader is correct.
However, since the warranty of the Dev Edition is not voided, just unlock the bootloader, root, and then get rid of the message by replacing the logo.bin
STEyeAndroid said:
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
Click to expand...
Click to collapse
You bought a dev edition, it doesn't matter if the flag is set or not.
So I've just ordered an unlocked black 16gb Moto X from Amazon and would like to update it to 4.4.2 and get root access. I know there are a few guides and threads around but am confused as to which variant I'll have as all the guides seem to be carrier specific, and whether my bootloader will be unlocked or not...
Also, I think it'll come with 4.2.2. Should I go ahead and do the 4.4.2 OTA update, or will that make rooting more difficult? Can I root first then update?
I'm not entirely clueless about this kind of thing, having successfully rooted and installed custom firmware on previous android phones but this seems a little more complicated.
Any help much appreciated. Thanks!
If it's an unlockable bootloader, just take all the updates, unlock the bootloader, mfastboot your choice of recovery, boot immediately to recovery and root. Done.
Since its not a developer edition, unlocking your bootloader will void your warranty. You can request the unlock code directly from Moto's web site for free.
To root after your bootloader is unlocked, just follow this -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
Once you get the code from Moto, you can unlock the bootloader at any point, no matter what rom is on your phone. But you might as well either take the OTA update or flash the 4.4.2 SBF to get to 4.4.2 on your phone, then unlock the bootloader and root. (unlocking the bootloader does factory reset the phone, and erases data and apps, so don't go nuts customizing the phone or installing apps until after you unlock the bootloader).
Thanks for the replies.
How do I find out if my bootloader is unlockable? The Motorola site says that Sprint, USC and TMO phones can be done but nothing about factory unlocked ones...
What if the boitloader can't be unlocked?
seebasso said:
Thanks for the replies.
How do I find out if my bootloader is unlockable? The Motorola site says that Sprint, USC and TMO phones can be done but nothing about factory unlocked ones...
What if the boitloader can't be unlocked?
Click to expand...
Click to collapse
The SIM unlocked version can be bootloader unlocked.
Follow the instructions and steps to request the code at -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth once you hit the final submit button, your warranty will be voided.
Awesome thanks, not as complicated as I had anticipated then...
And once I'm on 4.4.2 and rooted, I won't be able to Do any future OTA updates without losing root right?
seebasso said:
Awesome thanks, not as complicated as I had anticipated then...
And once I'm on 4.4.2 and rooted, I won't be able to Do any future OTA updates without losing root right?
Click to expand...
Click to collapse
Wrong. Rather than my re-typing... see -> http://mark.cdmaforums.com/MotoX-OTA.html
I have a Moto X -Xt1052 in India. I would like to root it and install Xposed framework. I am running kitkat 4.4.4
I would like to know is there any rooting method that wont affect OTA upadtes Because some people say thay if you unlock bootloader and You try OTA you brick your device. is it true???
and is there any way to reverse all this : Bootloader unlocking> getting back stock recovery> unroot complely so that there is no harm when you Update via OTA.
M really confused as there are mixed view over internet..
a few items to clear up....
The ability to root, and how you root vary depending on if you have unlocked your bootloader (or can you) or not, and what rom you have.
Being rooted itself does not impact the ability or inability to take an OTA. Its additional mods like custom recovery (you need to flash stock recovery back on before taking an OTA or you'll be stuck in a boot loop), deleting bloat (common in the USA where carriers like Verizon install a lot of extra apps and stuff as part of their rom), etc. The OTA performs a validation check before it installs. Modify too much on your phone and you will probably touch something that will cause the validation check to fail, and the OTA wont install.
Xposed gets in the way of OTA updates. You need to disable it or un-install it before taking an OTA.
I have never seen an unlocked bootloader be the cause of bricking a phone, taking an OTA or otherwise.
Attempting to down grade your ROM then later taking an OTA can/will brick your phone. But if you've never tried to downgrade your rom, there is nothing to worry about.
Once you unlock your bootloader, there is no need to re-lock it. It wont get in the way of an OTA. There is a process re-lock your bootloader if you want, but there is no reason to. Also keep in mind there are 3 states of the Moto X bootloader. 1. Locked - as it ships from the factory, 2. Unlocked - after you get your bootloader unlock code and use it, 3. Re-Locked - after you follow the process to relock the bootloader. And Once unlocked, we can only toggle it to RELOCKED. We can't set it back to LOCKED.
There are many ways to get back to "stock" after rooting and modifying your phone. I've outlined a few HERE
I've been reading threads and found a bunch of unlock bootloader/root threads. It seems that people could unlock bootloaders, but then lost the ability with new OTA updates. I'm not entirely sure if that's the current latest info.
If I have a carrier locked (VZW) moto X, on 4.4.4 - is there any way to currently unlock bootloader? Do I even need to unlock the bootloader? Goal is to root/put TWRP on it with CM11.
Could I RSDlite to an older rom, and then use the guides?
Thanks!
jellysweep said:
I've been reading threads and found a bunch of unlock bootloader/root threads. It seems that people could unlock bootloaders, but then lost the ability with new OTA updates. I'm not entirely sure if that's the current latest info.
If I have a carrier locked (VZW) moto X, on 4.4.4 - is there any way to currently unlock bootloader? Do I even need to unlock the bootloader? Goal is to root/put TWRP on it with CM11.
Could I RSDlite to an older rom, and then use the guides?
Thanks!
Click to expand...
Click to collapse
If you have the regular Verizon Moto X and not the Developer Edition you'll have to try and get an unlock code via Chinese Middleman.
jellysweep said:
I've been reading threads and found a bunch of unlock bootloader/root threads. It seems that people could unlock bootloaders, but then lost the ability with new OTA updates. I'm not entirely sure if that's the current latest info.
If I have a carrier locked (VZW) moto X, on 4.4.4 - is there any way to currently unlock bootloader? Do I even need to unlock the bootloader? Goal is to root/put TWRP on it with CM11.
Could I RSDlite to an older rom, and then use the guides?
Thanks!
Click to expand...
Click to collapse
People never had the ability to unlock their bootloaders (except through the "middleman") - they were able to disable write protect using an exploit. The exploit was patched in the 4.4.2 update. The exploit never allowed you to flash custom roms. Only "safestrap-compatible, stock-based roms".
As the previous posted suggested - check out the thread in general titled "China Middleman Back??" - it is currently your only hope. Yes, you MUST unlock your bootloader to use TWRP or any custom ROMS.
DO NOT attempt to "downgrade" or use RSD Lite to flash an older version. You WILL brick your device if you attempt this.
samwathegreat said:
People never had the ability to unlock their bootloaders (except through the "middleman") - they were able to disable write protect using an exploit. The exploit was patched in the 4.4.2 update. The exploit never allowed you to flash custom roms. Only "safestrap-compatible, stock-based roms".
As the previous posted suggested - check out the thread in general titled "China Middleman Back??" - it is currently your only hope. Yes, you MUST unlock your bootloader to use TWRP or any custom ROMS.
DO NOT attempt to "downgrade" or use RSD Lite to flash an older version. You WILL brick your device if you attempt this.
Click to expand...
Click to collapse
Disappointing news, but thanks for the info guys!
View attachment 4629305Good evening, since I upgraded my phone to OPSS27-82-87-3 version I have not been able to block the bootloader again, when loading an image it says boot loader error security patch I need someone who has this firmware since I could not block the bootloader of the phone if I do not have this variant, and this link does not work up to 222 Mb and it falls
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so download wherever it always generates the same download error
link of the image https://ibb.co/i2tV5q
I need the September patch security firmware opss27.82-87-3 a link that works, without this I can not go back to relock bootloader
Why are you trying to relock your bootloader? And you are not likely able to relock the bootloader. Sometimes flashing the exact firmware already on the device re locks the bootloader but not every time. There is no reason to relock your bootloader. It will not make the device as it was never unlocked for warranty purposes. It will not stop Motorola from being able to see that it was unlocked.
diegomateus1992 said:
Good evening, since I upgraded my phone to OPSS27-82-87-3 version I have not been able to block the bootloader again, when loading an image it says boot loader error security patch I need someone who has this firmware since I could not block the bootloader of the phone if I do not have this variant, and this link does not work up to 222 Mb and it falls
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so download wherever it always generates the same download error
link of the image https://ibb.co/i2tV5q
I need the September patch security firmware opss27.82-87-3 a link that works, without this I can not go back to relock bootloader
Click to expand...
Click to collapse
You can do it but there is no point. If your thinking relocking the bootloader will get passed a Moto service center and or sending it in will pass there warranty check your mistaken. if you do a logcat and look through it you will eventually find in the logcat it says your warranty is void. Also requesting the unlock code and using it voids your warranty. each phone has a unique unlock code only made for that phone for it's bootloader. For example me and a friend have the same Moto g6 play but his bootloader unlock code is not the same as mine. Long explain short Your warranty is voided the second you unlock your bootloader it doesnt matter if you relock it. And you can't hide it from moto. And as to what @madbat99 said. There's never been an instance where re-flashing stock firmware at least in my experience has relocked a bootloader for Motorola devices. Not saying your wrong I just personally have not heard that or seen it happen yet. it still doesn't matter though because the warranty is still voided from doing it the first time. I've heard of that happening with some Samsung devices but the warranty was still voided. I'm not sure why people think relocking the bootloader is necessary it doesn't affect the phones performance when It's locked or unlocked
ninjakira said:
You can do it but there is no point. If your thinking relocking the bootloader will get passed a Moto service center and or sending it in will pass there warranty check your mistaken. if you do a logcat and look through it you will eventually find in the logcat it says your warranty is void. Also requesting the unlock code and using it voids your warranty. each phone has a unique unlock code only made for that phone for it's bootloader. For example me and a friend have the same Moto g6 play but his bootloader unlock code is not the same as mine. Long explain short Your warranty is voided the second you unlock your bootloader it doesnt matter if you relock it. And you can't hide it from moto. And as to what @madbat99 said. There's never been an instance where re-flashing stock firmware at least in my experience has relocked a bootloader for Motorola devices. Not saying your wrong I just personally have not heard that or seen it happen yet. it still doesn't matter though because the warranty is still voided from doing it the first time. I've heard of that happening with some Samsung devices but the warranty was still voided. I'm not sure why people think relocking the bootloader is necessary it doesn't affect the phones performance when It's locked or unlocked
Click to expand...
Click to collapse
is not to pass it as a guarantee I just want to leave it as it was, also had already been able to block the boot, only for the last update of September I can not block the bootloader for being firmware of July, and the link that there is, the firmware of September does not work download certain part and the connection drops,
Also, with the patch version of July security if I could block the boot loader