Develop Bugs

T-Mobile Nexus 5X Unlock Failing

Code:
X:\Program Files\ANDROID\SDK\platform-tools>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.013s
Any suggestions? My device is recognized by and trusting my PC. I also tried the Device Unlock app by T-Mobile USA which says it isn't compatible with my device.

Go to developer options first then enable oem unlocking. Should work now

Thanks sooooooo much. I feel dumb yet don't remember this step on other devices. Guess I never had to unlock a Marshmallow phone? Also not mentioned in this thread I was searching http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930.
Edit: Nor google.

echardcore said:
Thanks sooooooo much. I feel dumb yet don't remember this step on other devices. Guess I never had to unlock a Marshmallow phone? Also not mentioned in this thread I was searching http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930.
Edit: Nor google.
Click to expand...
Click to collapse
This is a new, surprisingly under-the-radar thing you have to do. It got me at first, too when I tried to unlock it before first boot.

Another question.
I accidentally tapped and disabled Developer Options. When I reenabled it, the OEM Unlocking option was disabled. Did just RELOCK it?
EDIT:
It seems like its still unlocked.

How do I check bootloader status?

Hi.
Just like the title says:
How do I check my LG G3 bootloader status?
Thanks

tarzan2003 said:
Hi.
Just like the title says:
How do I check my LG G3 bootloader status?
Thanks
Click to expand...
Click to collapse
G3 bootloader is locked and there is no unlock method except bump

The G3's bootloader is locked, no matter which variant you have.
The only reason we have TWRP working and all is because of an exploit named Bump!
Basically, it signs the images so the bootloader allows them to be run.

tarzan2003 said:
Hi.
Just like the title says:
How do I check my LG G3 bootloader status?
Thanks
Click to expand...
Click to collapse
Ariac Konrel said:
The G3's bootloader is locked, no matter which variant you have.
The only reason we have TWRP working and all is because of an exploit named Bump!
Basically, it signs the images so the bootloader allows them to be run.
Click to expand...
Click to collapse
@Ariac Konrel well that's bull****. D851 = T-Mobile version is just fine and unlocked.
About the other versions yes they are all locked. Perhaps to verify it if you really want you could go to fastboot and input command: fastboot oem device-info
What I get with the command is this:
< waiting for device >
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.023s]
finished. total time: 0.024s

I'm using a D855 variant (international), I just flashed it, root it, get custom recoveries days ago ..and I'm using CyanogenMod 13 now.. Does that mean its bootloader's unlocked ?!

[Resolved] OEM Unlocking disabled on Google Store purchased phone

EDIT: Resolved: While the OS had said it was up-to-date when I originally checked. It was not. After a bit of time it alerted me that an update was available. After updating the OS the OEM Unlocking option was no longer disabled.
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.

Gregyski said:
(Since this isn't specifically about alternate firmware, I believe this is the correct forum and not the dev forum.)
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Click to expand...
Click to collapse
The command should be fastboot oem unlock

ilatimer1 said:
The command should be fastboot oem unlock
Click to expand...
Click to collapse
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s

Gregyski said:
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Click to expand...
Click to collapse
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.

ilatimer1 said:
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
Click to expand...
Click to collapse
Thanks for your help ilatimer1, but I have resolved it now. I had edited the original post to indicate this but probably should have followed up at the end for your sake. I was just trying to avoid bumping it. At the time I asked the question, I mentioned that that option was disabled.
When I originally setup the phone I didn't enter WiFi data since I knew a factory reset would occur when I unlocked the bootloader. However, as a result of this, I didn't get alerted to the presence of an OS update. Ultimately, I setup WiFi and discovered the availability of an update. I proceeded to update and the OEM Unlocking feature then became enabled. Thanks again.

I unwapped and went stright to fastboot. didn't know update needed. thanks

Same issue unresolved
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?

[email protected] said:
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
Click to expand...
Click to collapse
Where did you buy your Pixel?

Mr. Orange 645 said:
Where did you buy your Pixel?
Click to expand...
Click to collapse
verizon store

[email protected] said:
verizon store
Click to expand...
Click to collapse
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.

Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
so there is no solution if Ive already updated to 7.1.1?
any chance a solution will open up in the future?

No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.

Mr. Orange 645 said:
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Click to expand...
Click to collapse
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?

[email protected] said:
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
Click to expand...
Click to collapse
No. That's for Nexus devices not Pixels anyway.

Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?

integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
Im on Verizon

integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.

Mr. Orange 645 said:
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Click to expand...
Click to collapse
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.

integraGSR said:
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
Click to expand...
Click to collapse
LOL! Glad I could help!

Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
But pixels purchased at Google store with 7.1.1 are still unlockable correct?
Sent from my Pixel XL using Tapatalk

HTC M9 Cannot Unlock Bootloader

Hello everyone,
A friend of mine has given me his phone to fix it as he hard bricked it( that is what I understand). So, I tried first to unlock the bootloader but I get this : (bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.061s]
finished. total time: 0.062s
From what I've read the problem is that he didn't check the OEM Unlocking option before messing things up. Is there any way I can unlock the bootloader now?
Thanks in advance.

Nope. If the option isn't activated then you're stuck.
Beamed in by telepathy.

What happened?
Giannis0197 said:
Hello everyone,
A friend of mine has given me his phone to fix it as he hard bricked it( that is what I understand). So, I tried first to unlock the bootloader but I get this : (bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.061s]
finished. total time: 0.062s
From what I've read the problem is that he didn't check the OEM Unlocking option before messing things up. Is there any way I can unlock the bootloader now?
Thanks in advance.
Click to expand...
Click to collapse
Hi man, Did you find any solution?

jhondav3 said:
Hi man, Did you find any solution?
Click to expand...
Click to collapse
Still not
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
Software status of the phone is ***Modified***
***Locked***
***S-ON***
How can I unlock and S-off now? bootloader and download mode are the only places I can use

If you cannot boot to os there is no other way to tick the "allow oem unlock" in developer settings.
That option is probably the dumbest idea htc have ever had.
Beamed in by telepathy.

shivadow said:
If you cannot boot to os there is no other way to tick the "allow oem unlock" in developer settings.
That option is probably the dumbest idea htc have ever had.
Click to expand...
Click to collapse
HTC isn't the only OEM that uses this option. Therefore, it's probably android-specific and not HTC-specific. (Just like the block-based OTAs. So many blame HTC for using them but it's Google who introduced them with Android 5 and so many other OEM use them, as well.)

Flippy498 said:
HTC isn't the only OEM that uses this option. Therefore, it's probably android-specific and not HTC-specific. (Just like the block-based OTAs. So many blame HTC for using them but it's Google who introduced them with Android 5 and so many other OEM use them, as well.)
Click to expand...
Click to collapse
True but I'm inclined to say it is a collaboration of hardware, manufacturers requirements and android. The first two being the major factors. Mainly to do with businesses purchasing "fleets" of devices that need assurance that they are secure, and everyone picks on knox like its some kind of burden!.
It's better business at the end of the day but for situations where insurance policies won't cover, like the individual consumer, it hinders things like recovery or the dreaded "customisation" of your device. Topped by the fact that a business would only ever buy direct from either a manufacturer or an accredited supplier there is no need to secure their devices this much unless they are trying to shift away from allowing "customisation" completely. I totally disagree with that practice and we should be allowed to mess with what we indefinitely own.
I know I keep referring back to samsung like some kind of fanboy, I honestly favour htc sense over touchwiz any day of the week but Samsung ARE the most simple devices to work with and other manufacturers should learn from them to allow easy access to the device by not locking the bootloader in the first place.
To put this one extra hurdle in place makes absolutely no sense to me at all and there is only one objective to it. Lock us out.
Beamed in by telepathy.

unlockable oem unlock

Hello everyone,
This is my first post, so I apologize for bad English.
I have a problem when unlocking the bootloader of my z2 force, I am not able to enable the oem unlock in "programmer". Has anyone been through this and knows how to solve it ?

Have you got unlock key from Motorola?

robdevil said:
Have you got unlock key from Motorola?
Click to expand...
Click to collapse
May I have the same problem.
I din't go this step yet.
The "Allow OEM Unlock" on my Developer Options appears unavaliabe/grayed, with a message below like: "connect to the internet or contact your carrier".
To be honest, I don't pretend to unlock it now, but I usually make experiences with ROMs and things-like when my device become old and still working after I get a new one.

Leann Bastos said:
Hello everyone,
This is my first post, so I apologize for bad English.
I have a problem when unlocking the bootloader of my z2 force, I am not able to enable the oem unlock in "programmer". Has anyone been through this and knows how to solve it ?
Click to expand...
Click to collapse
Did you get "OEM UNLOCK" tickeable again or is it still greyed out?
Edit: Just wait 7 days... or Change your system date to 8 days ago And search for an update, then restart your phone, fix the date, search for an update and restart again.

I still can not enable the OEM unlock is in gray, as I can enable it since I want to install an official rom and I fear that a poblema

luiguy said:
I still can not enable the OEM unlock is in gray, as I can enable it since I want to install an official rom and I fear that a poblema
Click to expand...
Click to collapse
You don't need to unlock your bootloader to flash stock (official) ROMs, but you can not downgrade without OEM unlock.
Try to change your system date to 8 days ago, restart and search for official updates on config menu. Restart again, change the date for today and search again for an update. Restart third time and see if OEM unlock is tickable... That's what I did..

I already do it and nothing, so I intend to install the manual ROM and I do not know if it can be installed without unlocking the botloader

luiguy said:
I already do it and nothing, so I intend to install the manual ROM and I do not know if it can be installed without unlocking the botloader
Click to expand...
Click to collapse
Are you able to flash a stock official firmware? If so, flash the latest firmware for your variant, do a factory reset afterwards, then check to see if oem unlocking is restored in developer options.

41rw4lk said:
Are you able to flash a stock official firmware? If so, flash the latest firmware for your variant, do a factory reset afterwards, then check to see if oem unlocking is restored in developer options.
Click to expand...
Click to collapse
the truth I have never installed any ROM and that is my doubt, since as I can not enable the unlocking EOM I do not know what ROM is left, my model is 1789-05 and I bring 7.1.1 openmx

luiguy said:
the truth I have never installed any ROM and that is my doubt, since as I can not enable the unlocking EOM I do not know what ROM is left, my model is 1789-05 and I bring 7.1.1 openmx
Click to expand...
Click to collapse
I Didn't understand what you said. Don't you know which rom is installed? Just see the name/version on config/about. If you are on a custom ROM, you already have an unlocked bootloader.
If you want to be sure. Just flash the latest stock version to your model and flash without unlocking your bootloader.

junior_ilha said:
I Didn't understand what you said. Don't you know which rom is installed? Just see the name/version on config/about. If you are on a custom ROM, you already have an unlocked bootloader.
If you want to be sure. Just flash the latest stock version to your model and flash without unlocking your bootloader.
Click to expand...
Click to collapse
I have the official ROM 7.1.1, Software Channel: openmx and the only thing I want is to have 8.0 oreo, only that I do not know which would be the right one for this phone XT1789-05

luiguy said:
I have the official ROM 7.1.1, Software Channel: openmx and the only thing I want is to have 8.0 oreo, only that I do not know which would be the right one for this phone XT1789-05
Click to expand...
Click to collapse
Just use retail from this guide https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6

junior_ilha said:
Just use retail from this guide https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
Click to expand...
Click to collapse
I had already read it, but at the beginning it says that I have to have the boot manager unlocked, will it be necessary for what I want to do?

luiguy said:
I had already read it, but at the beginning it says that I have to have the boot manager unlocked, will it be necessary for what I want to do?
Click to expand...
Click to collapse
No, it's not necessary unlocked bootloader to flash stock ROMs. Locked bootloader's will block a downgrade attempt. If you are flashing the same version or a new one, you are blgoot to go. Nothing to worry. The unlocked bootloader is recommended so you can downgrade or install a custom recovery if something goes wrong.

junior_ilha said:
No, it's not necessary unlocked bootloader to flash stock ROMs. Locked bootloader's will block a downgrade attempt. If you are flashing the same version or a new one, you are blgoot to go. Nothing to worry. The unlocked bootloader is recommended so you can downgrade or install a custom recovery if something goes wrong.
Click to expand...
Click to collapse
ok, thank you very much I will try.
---------- Post added at 03:36 PM ---------- Previous post was at 03:19 PM ----------
junior_ilha said:
Just use retail from this guide https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
Click to expand...
Click to collapse
fail
C:\Users\luiguymm\Desktop\NASH_RETAIL_8.0.0_OPXS27.109-34-7_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Desktop\NASH_RETAIL_8.0.0_OPXS27.109-34-7_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml>flashfile.bat
C:\Users\luiguymm\Desktop\NASH_RETAIL_8.0.0_OPXS27.109-34-7_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml>echo off
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: -0.000s
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.008s
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (206 KB)...

What does your flashfile.bat look like? Maybe you ask in the other thread if someone has a working flashall. Then go from there. I have a suspicion that you have the famous false locked bootloader, but that can only be confirmed by trying to flash an official stock firmware. I have an idea on how to remedy that if that is indeed the case. First though, you should try and find a proper flashall for your firmware, ask in this thread. Someone there should have what you need. That thread deal specifically with your variant, so most anything you need will come from there.

I'm also blocked
I had already unlocked it to root
I was blocked again when I was trying to install Invictrix
one day passed and I unlocked it again with UNIQUE-KEY with fastboot
But, it was blocked again when I tried to reinstall Invictrix
I'll wait until tomorrow to try to unlock again
(I'm sorry for my English)

omnismart said:
I'm also blocked
I had already unlocked it to root
I was blocked again when I was trying to install Invictrix
one day passed and I unlocked it again with UNIQUE-KEY with fastboot
But, it was blocked again when I tried to reinstall Invictrix
I'll wait until tomorrow to try to unlock again
(I'm sorry for my English)
Click to expand...
Click to collapse
If you already unlocked your bootloader, you don't need to unlock it again.. what is write in bootloader? Locked or unlocked? You can't be on a custom ROM with locked bootloader.
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
luiguy said:
ok, thank you very much I will try.
---------- Post added at 03:36 PM ---------- Previous post was at 03:19 PM ----------
fail
C:\Users\luiguymm\Desktop\NASH_RETAIL_8.0.0_OPXS27.109-34-7_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml>fastboot devices
NGRL470061 fastboot
C:\Users\luiguymm\Desktop\NASH_RETAIL_8.0.0_OPXS27.109-34-7_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml>flashfile.bat
C:\Users\luiguymm\Desktop\NASH_RETAIL_8.0.0_OPXS27.109-34-7_subsidy-DEFAULT_regu
latory-DEFAULT_CFC.xml>echo off
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: -0.000s
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.008s
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (206 KB)...
Click to expand...
Click to collapse
This "slots" fails is all about the new a/b slots format present on Oreo ROMs.I believe this fail occurs because you are on nougat ROM.
Anyway.The important files to flash is partition/bootloader/boot/system/modem... Those can't be failed.
If you are struggling with using flashaal.bat, you can do command individually.Try send a message on technical's guide.

junior_ilha said:
If you already unlocked your bootloader, you don't need to unlock it again.. what is write in bootloader? Locked or unlocked? You can't be on a custom ROM with locked bootloader.
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
This "slots" fails is all about the new a/b slots format present on Oreo ROMs.I believe this fail occurs because you are on nougat ROM.
Anyway.The important files to flash is partition/bootloader/boot/system/modem... Those can't be failed.
If you are struggling with using flashaal.bat, you can do command individually.Try send a message on technical's guide.
Click to expand...
Click to collapse
I already tried and I got the first commands wrong and no longer continue, as I could know what original Carrier is my phone, I suspect that it is from Telcel Mexico only that they installed a released ROM.

angelobss said:
May I have the same problem.
I din't go this step yet.
The "Allow OEM Unlock" on my Developer Options appears unavaliabe/grayed, with a message below like: "connect to the internet or contact your carrier".
To be honest, I don't pretend to unlock it now, but I usually make experiences with ROMs and things-like when my device become old and still working after I get a new one.
Click to expand...
Click to collapse
you have to have a sim card installed and also be signed into a google account. once you do that, the option should be enabled.