Database Users

Unlock/Lock Moto X Style Bootloader Multiple Times?

Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you

Why would you want to do this?

psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same

Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk

psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes

Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks

psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.

jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?

psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.

psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.

jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.

iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.

acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry

[ZE552KL] I cannot unlock my bootloader.

I've been reading numerous threads in this forum in regards to rooting but I cannot unlock the bootloader.
Been trying to follow snowwolf's unofficial method to the letter but to no avail. Tried both .bat and manually doing fastboot .raw. https://forum.xda-developers.com/showpost.php?p=69001601&postcount=2.
Currently at the latest update as of today and have NOT rooted or unlocked bootloader prior to this.
USB debugging is also set to on.
I have uploaded screenshots of the error messages and information of the phone.
https://imgur.com/a/XPSDP
Any suggestions/opinions are welcome.

It's possible the unofficial unlock method was blocked in the newer firmware (bootloader) that you have installed. Try flashing the Marshmallow firmware, but you'll probably need to remove the checks in the updater script (first 7 lines or so). I'm not sure it'll work though, but worth a shot. If you can't downgrade though, then the only option is to use the official unlock method.

Yep, that seems to be the case. The official unlock method still works on the latest one and successfully rooted. Thank you for your help.

Sorry for the foolish question but what is the proper way to do a total clean "hard" reset to the latest version when its rooted? Just been messing with a lot of things and wanted to start anew since I'm relatively new to android from iOS.

droidoogle said:
Sorry for the foolish question but what is the proper way to do a total clean "hard" reset to the latest version when its rooted? Just been messing with a lot of things and wanted to start anew since I'm relatively new to android from iOS.
Click to expand...
Click to collapse
Factory reset through settings or in recovery mode

droidoogle said:
Yep, that seems to be the case. The official unlock method still works on the latest one and successfully rooted. Thank you for your help.
Click to expand...
Click to collapse
Will this work on version WW_14.2020.1703.28_20170410? Latest version of nougat. Even if its for marshmallow only? Thanks

NO OEM unlocking with S off

I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.

anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.

Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.

anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.

Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve

anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.

OK will give that a shot tomorrow thanks

If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.

Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.

anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.

Little help need for H910 (AT&T Update)

Hi guys,
I just recently bought LG V20 H910 and its stucked on December 1, 2016 update Now the simple thing i want is to remain on stock and update the software.
The thing that i learned is we need AT&T sim which is not possible for me and the second thing is Bootloader unlock.
Now guide that what should is do, i know dirty santa's FM problem i dont want that also the boot time is longer .
It would be helpful if anyone guide to simple update without further modifications or root.

If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian

runningnak3d said:
If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian
Click to expand...
Click to collapse
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?

runningnak3d said:
If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian
Click to expand...
Click to collapse
If I have AT&T SIM but I am not in the US. Will I get the update?

Mastermind_hassan said:
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?
Click to expand...
Click to collapse
If you use the dirty santa root you'll still have the corrupt warning screen and slightly longer boot time, static on display can be eliminated by flashing a custom kernel

cnjax said:
If you use the dirty santa root you'll still have the corrupt warning screen and slightly longer boot time, static on display can be eliminated by flashing a custom kernel
Click to expand...
Click to collapse
What are other methods for H910 bootloader unlocking that dont have that corrupt warning screen and longer boot time

Mastermind_hassan said:
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?
Click to expand...
Click to collapse
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
nirvikkhanal said:
If I have AT&T SIM but I am not in the US. Will I get the update?
Click to expand...
Click to collapse
I have no idea.
-- Brian

runningnak3d said:
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
I have no idea.
-- Brian
Click to expand...
Click to collapse
okay thank you please give me the link to get started

runningnak3d said:
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
I have no idea.
-- Brian
Click to expand...
Click to collapse
Just one last question, i have completed everything now i just wanted ask like for example if i wanted to sale my phone what things should i do to make that fizzy bootloader screen gone? because when i sell it to seller he will think there is some kind of fault in the screen

Mastermind_hassan said:
Just one last question, i have completed everything now i just wanted ask like for example if i wanted to sale my phone what things should i do to make that fizzy bootloader screen gone? because when i sell it to seller he will think there is some kind of fault in the screen
Click to expand...
Click to collapse
The only way to get rid of the boot screen is to go back to completely stock and locked boot loader, search the v20 forums there are threads around on how to do it.

Back to Stock with Oreo possible?

Hello my friends.
I bought my U Ultra in December 2017.
Now I decided to flash LeeDroid Oreo on my phone.
It works great.
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Now my question.
Is it possible to go for going to stock when I recover it all?
Can I lock the bootloader after that?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
My System Version was 2.21.401.1 and my region is Europe/Germany.
Regards

inFiniTyz_Z said:
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Is it possible to go for going to stock when I recover it all?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
Click to expand...
Click to collapse
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
inFiniTyz_Z said:
Can I lock the bootloader after that?
Click to expand...
Click to collapse
Kind of. You can make OEM lock but it won't be the factory lock. It will be relock. And if you have a custom ROM at that point the phone may not let you boot up.

QDT said:
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
Click to expand...
Click to collapse
In case when I flash the stock recovery too?

inFiniTyz_Z said:
In case when I flash the stock recovery too?
Click to expand...
Click to collapse
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).

QDT said:
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
Click to expand...
Click to collapse
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?

inFiniTyz_Z said:
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
Click to expand...
Click to collapse
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.

QDT said:
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
Click to expand...
Click to collapse
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.

inFiniTyz_Z said:
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
Click to expand...
Click to collapse
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.

QDT said:
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
Click to expand...
Click to collapse
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?

inFiniTyz_Z said:
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
Click to expand...
Click to collapse
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.

QDT said:
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
Click to expand...
Click to collapse
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!

inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.

QDT said:
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
Click to expand...
Click to collapse
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?

inFiniTyz_Z said:
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
Click to expand...
Click to collapse
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".

QDT said:
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
Click to expand...
Click to collapse
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"

inFiniTyz_Z said:
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
Click to expand...
Click to collapse
And to my knowledge it will be like that. You have flashed unlocked (from HTC but always) bootloader and this has to be noted. It is not that drastical as KNOX for Samsung, doesn't influence the phone functioning.

inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
When you say you followed the procedure, which exactly do you mean? Can you please help me by giving me a quick summary of the steps?

I would like to know the procedure as well.

Hi! I've installed a custom ROM, now I would like to go back to the stock ROM, I don't have a nandroid backup, what can I do?