Related
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
clairez said:
By the way, this was a completely stock Nexus 6 (5.0.1), no root, no apps other than Google. Before the factory image flash, the "OEM Unlocking" setting in Developer Options was persistent during power on/off. Now, with 5.1 the setting turns itself off during power on/off.
So, should I re-lock the bootloader and satisfy organizational requirements and risk a boot loop or proceed unlocked? Kinda feel like a "deer in the headlights" !
Click to expand...
Click to collapse
Well its your choice. I recommend not locking it. However, if you do lock it and end up bricked, at least we know its the locking that causes the loop and not the flash but.... Is it worth it?
If your organization is supplying the device ( or the money for the device) you have no business unlocking it. At my organization people are fired for such things.
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Sent from my Nexus 6
And if it is the unlocking/locking that causes the boot loop (hard brick) then any flashing operation that requires unlocking the bootloader will require that the system remain unlocked forever. A penalty that will afflict a portion (large?) of the Nexus 6 community. Was this an issue before 5.0? Makes one wonder if this is by design or accidental.
DebianDog said:
If they are not compensating you somehow then I don't see how they can make requirements on your device.
Click to expand...
Click to collapse
Yes we totally can. If you work for my company and decide you would rather use your own device for corporate email and data, that data is ours. You may use your own device but we will manage it. If it gets stolen, we will wipe it. You will adhere the same policies for corporate owned data as you will with a phone supplied by us. You will have lock screen, you will be unrooted. You will keep your bootloaders locked. Or you can use this sh*tty Nokia.
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
This post was not meant to be an organizational ethics discussion, just a request for guidance. If anyone can give me input on the original questions, I would greatly appreciate it. Especially the wipe side effect of the lock operation. Do not want to spend a lot of time configuring the device if it will be erased.
Thanks in advance
clairez said:
My hardware, but if I want to utilize it in the organization, then I must abide by their rules.
Click to expand...
Click to collapse
Yep. Absolutely.
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just a little thinking out loud here. Wouldn't it be safe to have OEM Unlock checked under dev options, lock the bootloader, if you happen to bootloop OEM Unlock is still checked so you could still unlock? And then upon first boot OEM Unlock would get unchecked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
rootSU said:
Safe? No.. The flag resets at boot. Boot loop partially boots and it could be enough to reset the flag "at first boot"
Pretty much everything is an unknown here. We do t even know where the "enable OEM unlock" flag is set. Is it in the BL or one of the various partitions? What effect would setting the flag and wiping the OS have? We just don't know.
Click to expand...
Click to collapse
Good point. That's why more heads are better than one. I still think my theory would work, but yet I wouldn't be willing to risk my N6 on it, wouldn't suggest others do either.
Sent from my Nexus 6 using XDA Free mobile app
clairez said:
Due to organizational requirements the bootloader needs to be locked. So, here go the questions:
After flashing factory image (5.1.0 (LMY47E), is it safe to re-lock bootloader?
And when, after the final reboot and before setup?
And, will the command, fastboot oem lock, wipe EVERYTHING off the phone, like fastboot oem unlock does?
And does the Developer options setting, "OEM unlocking", need to be turned on prior to the lock?
Thanks
Click to expand...
Click to collapse
1. Unsure at this point. If everything is stock (including recovery), I would suspect that it would be OK, but it has not been verified yet.
2. After you flash the bootloader, radio, boot, system and recovery images, and format data and cache, then would be the time to re-lock and then boot into Android.
3. Yes. But based on what I gather, the process of wiping on an N6 (when unlocking or locking the bootloader) is done via the stock recovery. So, if you have a custom recovery when you lock, I suspect that it will give you a boot loop.
4. I don't know.
Update - Success
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
clairez said:
I re-locked the bootloader and the device is working normally, no boot loop. I will continue testing over the next few days and then share what I learned.
Thanks for the help ...
Click to expand...
Click to collapse
Interesting. And you were 100% stock?
Perhaps the loop isn't caused by the lock itself then. Good to know, though still people need to be cautious
androiduser2011 said:
Upgraded to 5.1, booted system OK
rechecked the OEM unlock option and rebooted to fastboot and locked bootloader.
No bootloop or other issues noticed.
Hope this helps.
Click to expand...
Click to collapse
A few question, for understanding:
Rooted?
Stock or TWRP recovery?
Encrypted?
Thanks
rootSU said:
No one has proven that locking the bootloaders does not cause a "brick". We have seen people lock after 5.1 and get a bootloop. This becomes a brick because they cannot unlock to fix it. We don't know if the update causes the loop or the lock does.
Click to expand...
Click to collapse
This happened to me literally tonight. I tried to lock the boot loader which was successful, from there the device would start to root into teamwin recovery. So from there I tired to flash a fully stock rom but the bootloader was locked. And then because you need permission from the OS to unlock the bootloader I was stuck. What I did is from the locked bootloader I ran the stock oem flash from a fresh download and check from wugs with the force flash enabled (make sure everything is right) miracles of miracles it worked and came back to me.
I learned my lesson. Never shall my bootloader be relocked unless my phone is out of my possession. I'm spending the rest of the time making sure that nobody can get to my data. I love the phone, but that data is my life.
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1 per official instructions from Google. If it can be determined that having TWRP recovery installed is the cause of bricks then users can be instructed to be sure stock recovery is installed before relocking. My own thoughts are that this is a bug of sorts with the new security features of lollipop and I'm sure the talented folks here will get it figured out. I'm 100% stock on LMY47D that I sideloaded. Not sure I can afford to risk my 6 but I offer any assistance I can to help get this figured out.
Evolution_Freak said:
So basically, we need to confirm that being 100% stock will safely allow the relocking of the bootloader on 5.1
Click to expand...
Click to collapse
Some of the "bricks" happened after fully flashing stock, i.e they had stock recovery. They had a locked bootloader, an OS that didn't boot and a recovery that couldn't flash anything. If they had TWRP installed, they could format data and flash a rom.zip no problem.
Hey Folks,
I was curious to know if you have unlocked your bootloader, and then locked it again via fastboot oem lock command, if you wanted to unlock the bootloader maybe in the distant future again, would you need to use the same unlock key that was given to you by moto?
Thanks!
alternetconcept said:
Hey Folks,
I was curious to know if you have unlocked your bootloader, and then locked it again via fastboot oem lock command, if you wanted to unlock the bootloader maybe in the distant future again, would you need to use the same unlock key that was given to you by moto?
Thanks!
Click to expand...
Click to collapse
Yes the one you got in your mail.
Take care not to lose it.
I am not sure if they give it again
adity said:
Yes the one you got in your mail.
Take care not to lose it.
I am not sure if they give it again
Click to expand...
Click to collapse
Ah okay great.
Thank you!
I've unlocked my bootloader but have never once considered relocking it. Why would you lock it after unlocking it in the first place? I can't think of a single benefit.
nhizzat said:
I've unlocked my bootloader but have never once considered relocking it. Why would you lock it after unlocking it in the first place? I can't think of a single benefit.
Click to expand...
Click to collapse
I've seen some people claim they want to be as "close to stock as possible" when selling their phone. Unfortunately it doesn't really make a difference.
There are 3 states for the 2013 Moto X bootloader:
LOCKED Status:0
Unlocked Status:3
Locked Status:2
note: Status 2 is also known as relocked.
As users we can toggle it to either Status 2 or Status 3, but we can never set it back to Status 0. On Status 2 or 3, you'll get the Bootloader Unlocked warning message at reboot (where replacing the LOGO.BIN with custom one will hide the message).
alternetconcept said:
Hey Folks,
I was curious to know if you have unlocked your bootloader, and then locked it again via fastboot oem lock command, if you wanted to unlock the bootloader maybe in the distant future again, would you need to use the same unlock key that was given to you by moto?
Thanks!
Click to expand...
Click to collapse
Have you managed to lock it?
alexhdkn said:
Have you managed to lock it?
Click to expand...
Click to collapse
I didn't actually. I just tried right now but got the following message.
(bootloader) FAIL: Please run fastboot oem lock begin first!
The reason I wanted to re-lock it was for purposes of my phone getting stolen. I'm assuming if it was relocked, the person wouldn't get the joy of installing a custom recovery.
Yeah kind of silly. In any case, couldn't get it to lock.
alternetconcept said:
I didn't actually. I just tried right now but got the following message.
(bootloader) FAIL: Please run fastboot oem lock begin first!
The reason I wanted to re-lock it was for purposes of my phone getting stolen. I'm assuming if it was relocked, the person wouldn't get the joy of installing a custom recovery.
Yeah kind of silly. In any case, couldn't get it to lock.
Click to expand...
Click to collapse
There is a process to re-lock which involves flashing the stock rom first, etc. and it does wipe the phone.
So if you re-lock, you'll also lose root. (at least until you unlock, flash custom recovery and root).
KidJoe said:
There is a process to re-lock which involves flashing the stock rom first, etc. and it does wipe the phone.
So if you re-lock, you'll also lose root. (at least until you unlock, flash custom recovery and root).
Click to expand...
Click to collapse
Yeah. I think I realized that I would need to wipe my phone again to re-lock it. I turned it back to stock so I can get the OTA which should hopefully come out soon.
I guess once they allow us to download stock 5.0.2, I'll do a re-lock then.
Thanks though for the info.
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.
AT&T has not released Marshmallow for the Nexus 6 so I'm ready to root and flash my way there, but, I'd like to make sure I get future updates. Can you tell me if there are any flaws in this process I should know about? Is there any way to do this that will not erase user data? Thanks in advance.
1. Unlock bootloader
2. Root phone
3. Install recovery
4. Flash latest factory image
5. Lock bootloader?
If I do this will I then receive future update?
Is your bootloader locked? If it is I'm sorry you can't because when you unlock its going to wipe your device,if you want to do it
1. Unlock bootloader
2. Flash factory image
3. I don't recommend it but if you must relock bootloader only after you verify it boots and operates correctly
Other steps are not necessary
holeindalip said:
Is your bootloader locked? If it is I'm sorry you can't because when you unlock its going to wipe your device,if you want to do it
1. Unlock bootloader
2. Flash factory image
3. I don't recommend it but if you must relock bootloader only after you verify it boots and operates correctly
Other steps are not necessary
Click to expand...
Click to collapse
Are you saying I do not need to root to flash the factory image? Do I need to lock the bootloader in order to receive updates?
jeffery fisherman said:
Are you saying I do not need to Roy to flash the factory image? Do I need to lock the bootloader in order to receive updates?
Click to expand...
Click to collapse
if you root the device then flashing the factory image will unroot it. If you want to preserve ota ability and get to marshmallow then take a adb backup of all your apps and backup your internal storage files to your computer, unlocking your bootloader will wipe out the device to factory condition, flash the latest marshmallow image MMB29S, restore your adb backup to get your apps and data back, drag and drop your other files back into internal storage. DO NOT! relock your bootloader because that will wipe everything again and you don't need to be locked to get an update and if anything were to go wrong down the road with mods or root or whatever having a locked bootloader on nexus 6 or newer is basically an easy way to hard brick your device since you have to enable OEM Unlock inside the OS to unlock your bootloader and whenever you'd need an unlocked bootloader to fix something then the device probably won't boot. If you're worried about security then keep in mind that if you have an encryption password set (booting the phone asks you to put in your lockscreen code), even if someone pulls all your files off your phone they can't access them without your password.
jeffery fisherman said:
Are you saying I do not need to root to flash the factory image? Do I need to lock the bootloader in order to receive updates?
Click to expand...
Click to collapse
correct bootloader does not need to be locked to recieve ota
Excuse me unknown. I have a op3T and I unlocked the bootloader a few days ago. Now I relock the bootloader to use Android pay and still can't use. Give the same error like I have unlock the bootloader. Any advice?
Did you wipe your device after re-locking the bootloader?
Anova's Origin said:
Did you wipe your device after re-locking the bootloader?
Click to expand...
Click to collapse
When I relock the bootloader, the phone makes a full wipe.
Do I must do wipe cache ?