yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] :
Maybe some more information too, like what EXACTLY you were trying to do. How did you end up with a locked bootloader? If the advice given previously didn't work, you are most likely bricked.
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
It's f...ing unbelievable that people still lock their bootloader while having a custom ROM. Just turn it in for repair and blame yourself on this one.

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
If yuour bootloader is locked and you don't have TWRP, there is nothing you can do.
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
OK, here's the assistance you're looking for:

Request an RMA from Google, Motorola, or whomever you bought it from. That is your only option.
[Nexus 6 Q&A, Help & Troubleshooting] Tdeljr:
In wugfresh click return to stock, then click preferences button on bottom make sure to check all 3 boxes to force flash, when finished reboot phone and you should be able to go into settings to check the unlock option.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Are you sure you'e understood the problem? You cannot unlock because you need Android to boot to unlock? Or is this a new magic function that none of us know about?
[Nexus 6 Q&A, Help & Troubleshooting] Tdeljr:
Yes I understand what the op is talking about, I just went through it yesterday. Was rooted and I relocked my boot loader by mistake while trying to flash back to stock. And right now I am responding by using my nexus that has been fully restored back to stock.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
did you have twrp installed still?
[Nexus 6 Q&A, Help & Troubleshooting] Tdeljr:
When I first did it yes. After I was able to get into android I did the steps used wugs unlocked boot loader again and then from there I just fully unroofed and relocked.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
yea, if you have twrp installed, its easy to get out of this situation. all you have to do is is format userdata and cache with fastboot(or use the toolkit). but without having twrp installed, i dont see a way out.
[Nexus 6 Q&A, Help & Troubleshooting] Tdeljr:
The op never said whether he has twrp installed or not. I was sharing my experience but I was in the same boat.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
right.

look at post #2 ;)
[Nexus 6 Q&A, Help & Troubleshooting] Tdeljr:
Post #2 isn't the op. But anyway as I said I was just trying to help.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
absolutely. and as im not with the issue, i still appreciate it :)
[Nexus 6 Q&A, Help & Troubleshooting] :
How does one re-lock their bootloader "by mistake"? I'm very curious.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
type in fastboot oem lock "accidentally"
[Nexus 6 Q&A, Help & Troubleshooting] patmw123:
I think this tends to be more of an issue with the toolkits available as you're always just one click away from potentially damaging/ruining your device and a lot of times people don't even really know what they're even doing. That's why, in my opinion, it's always best for people to learn how to actually use command line to accomplish what they are trying to. Just my opinion though.
[Nexus 6 Q&A, Help & Troubleshooting] Tdeljr:
That's exactly what happened to me. The sad thing is that I know how to use commands, I was just being in such a rush and was being very careless. Which ended up wasting a lot more time and causing a lot more headache.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
i never ever recommend to anyone to use a toolkit. if you use one, you are on your own. if you need help without using a toolkit, i or many others, will be more than willing to help. but with toolkits, its your own choice. sure, that can be really useful on other devices that arent nexus. but for time saving, on a nexus they do not do that. as doing things the peoper way on a nexus is just as fast, if not faster.
[Nexus 6 Q&A, Help & Troubleshooting] tj786:
bricked nexus6.please help

I had rooted device and want to unroot it due to some issues. I search on net and try to uproot with software download from net.i lock at the end own too.But now I can't go recovery .bootloader is locked cannot flash due to locked bootloader.phone automatically restarted again again without showing any thing except android updating apps.please help me if any body can.Thanks
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
If you don`t have a custom recovery installed you`re phone is dead atm. You have to turn it in for repair mate. Ignorance isn`t always a bliss :eek:
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
[MENTION=5302753]Evolution_Freak[/MENTION],

"And another one bites the dust".... :(
[Nexus 6 Q&A, Help & Troubleshooting] EDGRAHAM2.0:
Do we know if Google/Motorola is planning on releasing a way out of this situation? Or has the level of Open Source support dropped just as much as their phone prices have risen?
[Nexus 6 Q&A, Help & Troubleshooting] :
It's not really about a "way out" so much as making the proper steps more visible and well known. The new security is incredible, IMHO, now, if your device is lost or stolen, it's virtually impossible to access your data. This, believe it or not, is a good thing. People just need to be aware, that there are new steps involved with locking the bootloader, and if followed carefully, you're good to go.

If a way around this were found, it could be used maliciously. That would never be allowed on XDA anyway.
[Nexus 6 Q&A, Help & Troubleshooting] EDGRAHAM2.0:
Thats just it. I screwed up and it is telling me to click the "oem unlock" in dev settings. But I am stuck in a boot loop and can only access the fastboot screen. Bricked! wish they would create a way to fix this without having to get to Developer settings.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
That would be a way to circumvent their security, so they're not going to.

Phone price hasn't so much risen. Its just returned to normal nexus phone price after their budget 4 and 5. Nexus was always a premium handset until LG.
[Nexus 6 Q&A, Help & Troubleshooting] Didgeridoohan:
Yes, that is it: you screwed up. I'm real sorry about that, but I think you're missing Evolution_Freak's point. We don't want another solution to this besides "send it in". This feature is awesome!

The problem is the lack of official documentation and information, not the feature itself.
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
Quote: The problem is the lack of official documentation and information, not the feature itself.

This isn`t the problem either, the problem is many users just don`t read up or not enough to prepare themselves to root because they think the Nexus`s are unbrickable. Turns out they are not.

Toolkits in combination with lesser xperienced users make the problem even bigger atm :(
[Nexus 6 Q&A, Help & Troubleshooting] TCPDump:
What happens if you try to unlock the bootloader from that bootloader (in the picture)?
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
you can only unlock the bootloader from the bootloader. but you need to be able to boot up first, to enable oem unlocking in the developer options.
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
How do you unlick something? :D
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
lol, unlock. you can try licking whatever it is in reverse ;)
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
Maybe suck the lick out :p

A dirty mind is a joy forever ;)
[Nexus 6 Q&A, Help & Troubleshooting] Android The Greek:
Less experienced users should never relock their devices unless they are sure they are on a factory image.
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
That would defuse this whole issue, but some don`t know that and thats the problem ;)
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
of all that time ive been using nexus devices(every one), ive never ever relocked my bootloader. if there is no need to have it locked, why go back to lock it?
[Nexus 6 Q&A, Help & Troubleshooting] Android The Greek:
I guess you are right in that sense, but when you unlock your boot loader the idea is to leave it open. Locking a boot loader just because... Is a bad idea on every manufacturer. The only reason I ever locked a boot loader was if I did a full conversion of firmware to a gpe or international ruu. Even then its unnecessary. 2nd mistake is using a mod, hex edit, or fastboot command to change an unlock counter when on a ROM with custom boot loader.
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
Especialy when they wiped their current OS to flash stock and don`t have a custom recovery.
[Nexus 6 Q&A, Help & Troubleshooting] :
The problem I deal with frequently, is that for whatever reason, users think locking the bootloader will fix a soft brick. ??? Time after time, users get stuck in a bootloop and decide to fastboot oem lock.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Well that's just crazy talk.
[Nexus 6 Q&A, Help & Troubleshooting] Mandelbrot.Benoit:
I thought there was a check that would cause a failure when relocking the bootloader if not on stock firmware. Think that was case with Xoom and GNex. I don't remember this being such a problem?
[Nexus 6 Q&A, Help & Troubleshooting] nhizzat:
What I see the most is users relocking their bootloaders because they think, for some unknown reason, it's necessary to receive OTAs. I rarely ever see someone say they relock their bootloader for security reasons.

Only time I've ever relocked a bootloader is when I'm selling a device, unless the buyer requests that I leave it unlocked.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
I used to lock my bootloader for security on my Nexus 5.
[Nexus 6 Q&A, Help & Troubleshooting] playahate:
Well, theres a good reason for this... Many manuals say this thing to the users... If something goes wrong - then make fastboot oem lock then fastboot oem unlock and everything wipes, the system will boot etc...

But it all ends with the Nexus 5. Because N6 and N9 have a new developer option - allow oem unlock

There is A LOT of official documentation. And the main is android.googlesource.com

Then we have DevelopmentSettings.java from the same source:

...
@Override
public void onCreate(Bundle icicle) {
super.onCreate(icicle);
...
if (!showEnableOemUnlockPreference()) {
removePreference(mEnableOemUnlock);
}
...

So the trigger in the settings goes to "off" every reboot, and oem unlock may be performed only after 1st reboot to bootloader, when the trigger is set to "on".

And we know that partitions, as they are located in /system/build.prop

.

private static final String ENABLE_OEM_UNLOCK = "oem_unlock_enable";
private static final String PERSISTENT_DATA_BLOCK_PROP = "ro.frp.pst";
...
private CheckBoxPreference mEnableOemUnlock;
...
static boolean isOemUnlockEnabled(Context context) {
PersistentDataBlockManager manager =(PersistentDataBlockManager)
context.getSystemService(Context.PERSISTENT_DATA_BLOCK_SERVICE);
return manager.getOemUnlockEnabled();.

And the lines from PersistentDataBlockService.java:

Its ro.frp.pst=/dev/block/platform/sdhci-tegra.3/by-name/PST for the Nexus 9

and ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/frp for the Nexus 6

and we know the bit to change from 00 to 01. (N9 - 100%, N6 - must be similar, but we need a rooted live device to get the information before and after the trigger is set)

and i hope [MENTION=4544860]osm0sis[/MENTION] will make a script to test...
[Nexus 6 Q&A, Help & Troubleshooting] EDGRAHAM2.0:
Fix yet?

anyone find a fix for this yet?
[Nexus 6 Q&A, Help & Troubleshooting] bBigBrO:
Why aren't you downloading Google's Factory Images and flashing 'em away with fastboot flash system/boot/recovery?

Sorry if it's a noob question, but i did not see any flashing in this thread. Am I wrong?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
This thread is about being in a bootloop and not being able to unlock the bootloader. You need an unlocked bootloader to flash
[Nexus 6 Q&A, Help & Troubleshooting] bBigBrO:
The ORIGINAL Google Fac' images? Never unlocked the bootloader of a Nexus 5 and i could flash them without any problem

Sent from my SmartWatch 3
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
I promise you, you couldn't. You have to unlock the bootloader on both the Nexus 5 and the Nexus 6 in order to flash the factory images. This is a fact. You are unfortunately mistaken.
[Nexus 6 Q&A, Help & Troubleshooting] bBigBrO:
Weird, because in my experience i could flash them with success...

Anyways can't you do fastboot oem unlock again when you're on that screen? Its actually fastboot mode... But i guess you know it :D

EDIT -- i see you cannot oem unlock... (My eyes are not reading well :D) So what output does it give to you?

Sent from my Sony SmartWatch 3
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
You're quoting me, but I don't have the issue.

You need to fastboot oem unlock from bootloader to flash but it won't unlock unless you enable oem unlocking in settings. This is what the output will say.
[Nexus 6 Q&A, Help & Troubleshooting] bBigBrO:
Okay, that is what i did not understand. Thanks!

Sent from my
[Nexus 6 Q&A, Help & Troubleshooting] carlz28:
Delete this post. Missed a whole page of responses [emoji15]
[Nexus 6 Q&A, Help & Troubleshooting] bBigBrO:
And you, read one message above ? :D

Sent from my Sony SmartWatch 3
[Nexus 6 Q&A, Help & Troubleshooting] carlz28:
You do the same, my friend [emoji23]
[Nexus 6 Q&A, Help & Troubleshooting] loplo:
Well, I'm in the same boat.

Stuck at Google, but I can boot into TWRP. Any chances of pushing a custom ROM or anything else and boot my phone?
[Nexus 6 Q&A, Help & Troubleshooting] wolfen69:
Hook up your phone to your PC and then in twrp select adb I believe. Then your pc should see the phone and you can copy and paste a rom to it.
[Nexus 6 Q&A, Help & Troubleshooting] loplo:
I managed it. I think I had luck, that I didn't delete my recovery.
[Nexus 6 Q&A, Help & Troubleshooting] mikeprius:
I was reading this, how does fastboot format userdata and cache solve a locked bootloader without OEM unlock checked ? You go to the TWRP splash screen and feed the commands ?

---------- Post added at 03:37 AM ---------- Previous post was at 03:17 AM ----------

Or does it allow normal functioning of TWRP so a ROM can be flashed, booted, then OEM unlock can be unchecked ?
[Nexus 6 Q&A, Help & Troubleshooting] totallybeachin:
I read this thread, not because I was having this issue, just that I want to read stuff so I am aware in the event I ever DO have issues......but I am confused by some of these responses. Perhaps I am reading it all wrong, or I need to keep learning.

I've only had my N6 for about a week. The first day I received it, I went ahead and booted it up, let it run all its updates, then proceeded to unlock, install TWRP, and root the following day. Just followed a couple guides here on XDA.

My question....

I unlocked my bootloader when following the guide. But now, when my phone is starting up, with Google on the screen, the little lock is on the locked position.

Under dev. options, my slider is off for 'Allow OEM unlocking'

So, I'm kinda paranoid now.

How did my boot loader lock itself?

Should I unlock it?

I am not having any issues that I am aware of. I can restart system with no problems and restart in recovery......

I haven't flashed anything other than a radio and the initial flashes from the beginners guide (and the repair guide...:facepalm: )
[Nexus 6 Q&A, Help & Troubleshooting] Tenhi:
Don't worry! That lock is shown there when your bootloader is UNLOCKED. When it is locked then you can see only Google logo, without lock icon. I agree that it is somehow confusing to see lock in locked position, but that is how it is :)...
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
Edit: nevermind the first part.(removed)

what I don't get is, you unlock the device to flash your stuf, but after the flash you locked it again? Whit a command? How is that possible but not unlocking it through command? Does not make sense... I get that you can do the unlock in the software, but why would it be able to lock trough command? Why allouw that but not unlock?

How would the repair guys at the service repair this? Would there be a hardware jumper to be set, or a special USB device/cable just like Samsung had? There must be a way.

Also... This is why you DO use toolkits instead of manual commands. Toolkits don't re-lock after flashing. And as far as I know, custom recovery also don't lock after flashing. And if you would chose the optiont to lock the device in nexus tool kit for example, it flashes the stock rom from Google. Don't know about other toolkits, but the nexus toolkit is pretty much the way to go.
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
NO! NEVER relock your bootloader unless you have a warranty case!!!!
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Please don't give bad advice to people that will potentially brick their devices.

Contrary to rootkits, where the "Go back to stock" commands has a checkbox* to lock bootloader, which you can tick accidentally. Or in wugs toolkit it's a button, and they show you how to press it after going stock. You can't accidentally type "fastboot oem unlock" or "fastboot flashing unlock".

* Here: http://www.wugfresh.com/nrt/videos/ It's called "Relock Bootloader + Unroot + Restore Stock"
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
I'm not giving bad advice. If the person used nexus root toolkit he would not have been able to lock his device without flashing a stock build from Google(not being able to brick).

Nexus toolkit only flashes stock images from Google and root. You can't brick your device with that toolkit unless you force it to feed different boot images(this can only be found under advance)

And as far as the comments go's, he did use commands to lock the boot loader.

Did you even read?
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
Well... i'm mean that you are right. I had better quoted the other person.
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
I see, stil doesn't explain why Google would allow the lock comand in adb but not the unlock command. There is no consistency. Just out right not allowing the whole lock command just like the unlock command would have prevented this whole thing.
[Nexus 6 Q&A, Help & Troubleshooting] Witek_M:
It's there to discourage theft. Only owner with correct PIN or password can get into Developers Options and unable oem unlock.

https://support.google.com/nexus/answer/6172890?hl=en
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Yes you can. Flash a stock rom with no wipe, and close the bootloader without checking if it's booting, and you can easily have a brick no matter if you typed it, or played click-click-click.

You totally misunderstand it. Toolkits aren't there to save people from making mistakes, just for the lazy ones, who don't care to look up something by themselves. Something as easy using the search function on xda.

---------- Post added at 02:33 PM ---------- Previous post was at 02:33 PM ----------

There is no lock command in adb.
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
"fastboot oem lock". How can you even say it doesn't exist?

And have you ever used nexus tool kit? You can not use the lock option without flashing a stock Google image(from Google repo) without wipe, you do not get to chose. You can also not flash bad images. So there is no " does not boot". For it not to booit, Google it self first needs to release a incorrect image.

---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------

I don't think you get my point.

You need to enable OEM unlock in dev options.

But you can lock the device trough adb.

That's inconsistent.

Why not also make it so that you need to go in dev options to lock the device again?

This way you prevent such cases like this.

Or at least make it so it can't be locked without a successful boot.

Now it more like you drove over a bridge , the bridge opens behind you and it won't close unles you are at the other side of the bridge.

There is no reason for not having such option/restriction. Not allow OEM unlock without dev options? Than don't allow OEM lock without dev options.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
You say it doesn't exist.

adb and fastboot are too different tools.

https://android.googlesource.com/platform/system/core/+/master/adb/ and

https://android.googlesource.com/platform/system/core/+/master/fastboot/

But that's not the point, just it's better to pay attention to details if you intend to suggest solutions.

Also there are toolkits, plural, and they are made by different people, and while I believe they do their best to make them bug free, do you vouch for them? Do you guarantee there can't be a bug when you can press a button you weren't supposed to?

Then who will tell those who believe downloading toolkits everything is just simple click-click-click, that after every major Android release they should wait downloading them, and running to brick their devices, if they don't even know this is an issue. Because if you checked xda since marshmallow was released, it was all about "I used this toolkit, and now it won't boot, please help" or "I used this toolkit and now its a red triangle, please help!".
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
You can't relock if "OEM unlocking" is disabled AFAIK.
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
I never said it didnt exist. Don't start pulling nonsense out of your butt.

Adb and fastboot are not tools, they are part of the SDK, you can not fastboot without adb. They are dependant on each other.

And yes, I vouch for the nexus root toolkit, its made for nexus only, any nexus owner should have decent knowledge about nexus and any one should at least Google if some thing go's wrong. If you are touching buttons you are not supposed to than you should not even be using any tools nor even be rooting. The encryption message is not even a brick, and as I said many times, you can't brick your device with the nexus root toolkit. And for that matter, the toolkit already supports 6.0 R build.

All you are saying is " if , if ,if".

I do not vouch for other toolkits, that's why I only mentioned 1. I also do not vouch for people that touch stuff they shouldn't. These people who would push the wrong button are the same kind of people who would push a wrong command to the device.

The nexus root toolkit is there to make it less of a hassle for users like me and you, its not there for people that have no knowledge. You can follow every step it takes and it stil requers input from you, its not a one click root tool. You stil have to flash Su your self and reboot the phone.

There is no need to type the commands every damn time if there is a tool that does the commands for you, the exact same commands you would do. It's basically the same as a batch file you setup for a certain android image.

It's pure paranoia to say all toolkits are bad or are full of bugs.

---------- Post added at 02:10 PM ---------- Previous post was at 02:10 PM ----------

Well, OP did.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
1. The language you use is totally unwarranted.

2. You're confusing the two command line tools (adb and fastboot) with the adbd service/daemon. You can't type "adb oem lock"

Well you did softbrick your freshly updated 58R, didn't you? (http://xdaforums.com/showpost.php?p=63880217&postcount=42)

Then started explaining that everybody is wrong who says you need a custom kernel for SuperSU 2.52. Because you only used "the nexus root toolkit" and never looked past what it really did. And I'm sure you didn't google it, when something went wrong.

Your knowledge is superficial at best, and I blame it on these toolkits no matter how easy they make these things look. When they work, and you don't get surprised by a big red triangle.
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
Ok enough of the arguing.

If you like tool kits cool, if you think they are part of a major problem (like me) then that is cool to. Either way it doesnt really matter what anyone thinks.

Now back on topic and the topic is not about tool kits.