Related
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
cropythy said:
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
flashallthetime said:
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
Click to expand...
Click to collapse
I tried manually entering it (3 times) i have tried copying it directly, and I have tried copying into notepad and making sure there are no spaces, but it still says my devices is not eligible for a bootloader unlock. Guess I'm calling motorola after work tomorrow.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
I just tried unlocking a Rogers Canada phone and it told me the phone isn't eligible. It certainly should be and I know I'm doing everything correctly as I unlocked a different one a few days ago.
So being you're seeing the same thing my conclusion is that the backend server which the website communicates with to manage the unlocking is broken at the moment.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
Try it again today, so far from my testing the unlock website is working again.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
As others have said, you need a code. The reason is you have to see like five warnings that the warranty will be voided before you get the code. They want to make sure people can't use the "I didn't know it would void the warranty" response if something goes wrong.
GSM Dev Can't go into CWM recovery
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
hondamarlboro said:
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
Click to expand...
Click to collapse
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Volume UP is the "select"
lensgrabber said:
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Click to expand...
Click to collapse
Thank you!!! This is my first moto device and I don't know this manner. Successfully recovery into CWM. Thank you again!
Welcome.
Sent from my XT1053 using Tapatalk
Is possible, Lock bootloader ?
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
I'm trying to figure out the same thing. I followed motorola's instructions on reflashing https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images but it does not re-lock. It tells me "No valid PIV block in SP for userdata"
edit - deleted userdata and it locked, but i still get the warning screen on boot
warranty
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
vespadaddy said:
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
Click to expand...
Click to collapse
Anyone knows anything about that?
Also, is the image altered in any way after a unlock? or is it exactly the same as a factory reset?
---
edit:
apparently it is all fine
Requesting an unlock code will no longer void the device’s warranty
We will start posting return-to-factory software images
Click to expand...
Click to collapse
-- http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html
Why really lock?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
Why would you unroot and/or unlock?
If it is a dev edition, it will not hurt the warranty.
The reason for this phone is for unlocking, rooting, flashing and roming.
Once you have saved a nandroid with a custom recovery (TWRP) you can't mess anything up. Go crazy and have fun
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
The toggle is a new feature of Android 5.0 and up. The toggle does not unlock your bootloader, rather it allows the process to happen. You need to use fastboot to OEM unlock. Click the top link in my signature for more info. Also, I suggest you read the beginners guide in the general forum.
RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
After you toggle enable OEM unlock you need to reboot into boot loader and run the command "fastboot OEM unlock"
Everything is here
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Sent from my Nexus 6 using XDA Premium HD app
RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
It is a security feature. All "enable oem unlocking" does is allow you to unlock the bootloader by fastboot. It doesnt actually unlock it.
RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
When you toggle "allow bootloader unlock" in developer options, it does just that; it allows you to unlock the bootloader.
Then you boot to bootloader and type "fastboot OEM unlock".
Assuming you have the android SDK on your PC, and device connected by USB cable. Look in the sticky roll up thread in general section for specific directions.
Intub8 said:
After you toggle enable OEM unlock you need to reboot into boot loader and run the command "fastboot OEM unlock"
Everything is here
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
That's what I'm doing. However, the issue is that it relocks itself. Hence the "device is locked - status code 2". You shouldn't unlock the bootloader when it's locked, or else you could cause a bootloop.
RootTheWorld said:
That's what I'm doing. However, the issue is that it relocks itself. Hence the "device is locked - status code 2". You shouldn't unlock the bootloader when it's locked, or else you could cause a bootloop.
Click to expand...
Click to collapse
Are you sure its relocking? Are you sure you're unlocking it?
So you go into settings > developer options
You tick "allow OEM unlock"
You boot into bootloader
Connect USB to computer
Open command prompt
Type "fastboot OEM unlock"
Does it unlock and change to status 3?
When does it change back to 2?
rootSU said:
Are you sure its relocking? Are you sure you're unlocking it?
So you go into settings > developer options
You tick "allow OEM unlock"
You boot into bootloader
Connect USB to computer
Open command prompt
Type "fastboot OEM unlock"
Does it unlock and change to status 3?
When does it change back to 2?
Click to expand...
Click to collapse
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
RootTheWorld said:
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
Click to expand...
Click to collapse
and you misses a step.. You need to get ur ass in dos or terminal and run the fastboot oem unlock command
Robert_W said:
and you misses a step.. You need to get ur ass in dos or terminal and run the fastboot oem unlock command
Click to expand...
Click to collapse
I thought I'd put my phone into a bootloop if I did that with a device is locked - status code 2 message.
I'll report back shortly
RootTheWorld said:
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
Click to expand...
Click to collapse
You are not doing it correctly. Go here and follow the directions
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
cam30era said:
You are not doing it correctly. Go here and follow the directions
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
I was doing everything correctly, but I didn't realize that it was okay to proceed on the "device is locked" message.
One thing that's not covered in the guide however: Is it okay to use the Chainfire root on a 5.1 device? The Chainfire website lists the tool as compatible with 5.0, but could I proceed anyway?
RootTheWorld said:
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
Click to expand...
Click to collapse
As we've said multiple times, ticking the OEM unlock box only allows you to unlock. It doesn't actually unlock. There is only 1 way to unlock and that's with the fastboot commands.
---------- Post added at 03:22 AM ---------- Previous post was at 03:20 AM ----------
RootTheWorld said:
I was doing everything correctly
Click to expand...
Click to collapse
Yes the half of it you did, you did correctly
RootTheWorld said:
I didn't realize that it was okay to proceed on the "device is locked" message.
Click to expand...
Click to collapse
What did you expect it to say? You cant unlock it if its not locked.
rootSU said:
As we've said multiple times, ticking the OEM unlock box only allows you to unlock. It doesn't actually unlock. There is only 1 way to unlock and that's with the fastboot commands.
---------- Post added at 03:22 AM ---------- Previous post was at 03:20 AM ----------
Yes the half of it you did, you did correctly
What did you expect it to say? You cant unlock it if its not locked.
Click to expand...
Click to collapse
Yes, I know. The problem was that the OEM unlock box kept unticking itself, which I had assumed led to the message I saw in the bootloader. Do you understand what I am trying to say? I don't think it was clear.
RootTheWorld said:
Yes, I know. The problem was that the OEM unlock box kept unticking itself, which I had assumed led to the message I saw in the bootloader. Do you understand what I am trying to say? I don't think it was clear.
Click to expand...
Click to collapse
That box un ticks it self on each boot. I also have a Verizon nexus. You check it and USB debugging. Then use wugfresh tool kit to unlock. Or just power down to boot loader mode & use terminal. Its only used to reboot to allow unlock. My phone is a flash whore & that box always off.
RootTheWorld said:
Yes, I know. The problem was that the OEM unlock box kept unticking itself, which I had assumed led to the message I saw in the bootloader. Do you understand what I am trying to say? I don't think it was clear.
Click to expand...
Click to collapse
Yes the box keeps unticking. That's a security feature to stop a thief unlocking your bootloader and using your phone.
i run above method in my lenovo vibe shot z90a40, it gives below error msg: (failed: unknow remote command)
aicts said:
i run above method in my lenovo vibe shot z90a40, it gives below error msg: (failed: unknow remote command)
Click to expand...
Click to collapse
We can't help you. We have nexus 6.
same thing happens with me just mine would untick immediately after i press it oem unlocking in developer settings
Good lord man read the thread.
ON THE NEXT BOOT OF ANDROID, ALLOW OEM UNLOCK IS TICKED BACK OFF AUTOMATICALLY, THIS IS NORMAL AND CORRECT.
The reason it says allow unlock, and not unlock... Is because this command only ALLOWS unlocking to happen.
As a security measure, you need to allow unlock, then immediately do it... YOU CANNOT ENABLED ALLOW OEM UNLOCK FOR USE AT A LATER DATE.
This toggle simply passes the message to your bootloader that you it can be unlocked via the unlock command.
The point is, that if your phone is password protected and locked... No one can flash anything to it. If you could simply boot the phone to bootloader and unlock, it would not be as secure. You need to enter the password to gain access to the running phone, then choose to allow the unlock, then reboot. If you could simply toggle on allow unlock and leave it through reboots it would negate the whole idea that if someone gets your phone they cannot unlock the bootloader with out the phones password.
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
what happens if you do a factory reset from the bootloader? Also can you flash a factory image?
returns to the fastboot , and I can not flash factory image
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
miketoasty said:
Interesting, I didn't think that RSD would be able to modify the recovery partition on a locked device. Nonetheless if anything is going to work I believe what you have outlined is it St33v, best of luck to you OP.
Click to expand...
Click to collapse
Yep. As long as it passes the signature check, it flashes.
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
Let's be clear -- it was the Droid Turbo. Leave off the Moto Maxx part, OK?
You can lock/unlock a Moto Maxx (XT1225/XT1250) or even Moto Turbo (XT1225) all you want. In fact, the U.S. Moto Maxx XT1250 is IDENTICAL in every way to the Droid Turbo XT1254 -- radio bands, even the same FCC ID. Of all the Quarks, only Verizon's "Droid Turbo" has a carrier-locked down bootloader. All the others can be unlocked via the Motorola website. Whereas, the Droid Turbo bootloader unlock is a hack (Sunshine) that relies upon a vulnerability present in devices with Snapdragon 805.
miketoasty said:
Why did you relock the device in the first place? Not sure there is anything you can do at this point, I'm guessing you still had TWRP on the device which I believe would be the issue, but you can't remove that since your device is now locked and cannot be unlocked.
Click to expand...
Click to collapse
Yes, WHY would you do that? Devs went through all the trouble to find a vulnerability to UNlock the Droid Turbo, and you lock it back? Been posted MANY, MANY times with the Droid Turob it's a one-time unlock only, through Sunshine.
TheSt33v said:
Incorrect. With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to to flash all of the stock images with a locked bootloader. See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
While you can flash stock again with a locked bootloader and it can work, over in the Moto Maxx section many people did brick their phones because they refused to unlock their bootloaders first. They were more worried about their silly "warranty" than having a functioning device. We kept stressing, FIRST unlock your bootloader. If you mess up, it's an easy fix if a flash goes wrong. With a locked bootloader, a bad flash is a recipe for disaster.
Over in the Moto Maxx/Moto Turbo section was a write up about flashing images, similar to your write up:
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724
Usually people wanting to downgrade back to KitKat or flash a Quark image from another region (India Moto Turbo XT1225) got Lollipop first before Latin American Moto Maxx XT1225).
And people were able to do it with a locked bootloader -- but you have to do everything just right. In my case, first time I flashed from Moto Maxx image to Moto Turbo image, I messed up. I was looking at the example picture more than reading the instructions. But, since I had an unlocked bootloader, so what? Just did it again the correct way, the second time.
In the case of Moto Maxx brick people trying to flash to Moto Turbo, those people had to wait until Lollipop was released for their phones then try to re-flash an image made for their phones -- and HOPE it worked.
Re Unlock
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
I tried what you said and I could not, Recovery does not work
A failure occurred when the step system.img_sparsechunk
How did you re-lock your bootloader? What did you do?
pedro_maciel said:
Relocked the bootloader on Droid Turbo/Moto Maxx and again try to unlock the bootloader
C:\adb>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
Now this time there is no notification on the phone screen and phone reboots automatically. Now flashing the Android logo from last 5 minute.
Not able to boot in recovery mode. Only fastboot mode is working.
Click to expand...
Click to collapse
tvlovers said:
How did you re-lock your bootloader? What did you do?
Click to expand...
Click to collapse
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
TheSt33v said:
Before I answer this question, I have to make one thing clear: DON'T EVER DO THIS!
Verizon will still replace your phone under warranty with an unlocked bootloader as long as there is no physical damage. Motorola will do the same. Even if they do decide to get picky about bootloaders, re-locking your bootloader does not erase all traces of it ever being unlocked. Your bootloader will show status code 2, which indicates that it has been unlocked and re-locked again. If you lock it before you sell it to someone else, and they try to unlock it again, the phone will be ruined. There is absolutely no reason to do this.
With that out of the way, the command is "fastboot oem lock"
Don't ever use it.
Click to expand...
Click to collapse
tvlovers said:
Thank youfor the warning. I should make it clear before. The reason I was asking was to make sure that no one would accidentally do it as I see no reason to lock it again once unlocked.
Besides that fastboot command is there any other way to accidentally lock it? New VZW OTA software or OEM unlocking under developer options in settings?
Please advise.
Click to expand...
Click to collapse
A verizon OTA probably will not, but it's best to wait until someone here confirms that. In the past, they have not, but you never know what they'll try next. The OEM unlock setting in developer options does nothing on a Turbo. It's intended for true dev phones (or phones designed for carriers less tyrannical than Verizon) that can be unlocked and re-locked easily. It disables the "fastboot oem unlock" command that someone with a dev phone would normally use to easily unlock the bootloader. There are no other ways to lock the bootloader that I know of.
bubblesd306 said:
I did the same thing on my xt1254 this is what Beaups told me from sunshine and it worked for me. I did it from terminal emulated on the device and then was ablebto reflash twrp
Beaups (TheRootNinja Support)
Dec 29, 17:10
tested this on my device and it worked. Keep in mind we can't guarantee it will work for you and also can't guarantee it won't kill your device (but I don't see why it should). Copy paste this command, do NOT make any errors.
From a ROOT adb shell (if you don't have root you'll need to figure out how to get it, kingroot, etc):
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/sp bs=1 seek=8
It should hang for a few seconds and then you should see something like:
dd: /dev/block/platform/msm_sdcc.1/by-name/sp: No space left on device
1048569+0 records in
1048568+0 records out
1048568 bytes transferred in 7.203 secs (145573 bytes/sec)
At that point reboot to bootloader and hopefully your problem is solved. Do NOT relock that device again in the future.
--beaups
Click to expand...
Click to collapse
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
richii0207 said:
Has anyone that has unlocked using this method been able to flash CM or a CM-based ROM?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
This isn't unlocking for a first time. This is unlocking for a second time.
Typically when you unlock a bootloader you can relock and unlock easily in adb.
For our device this is not the case and it should never be relocked.
A few have and have always succeeded with those commands.
Again this is only for a previously unlocked boot loader.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
richii0207 said:
Ya. I did unlock, relock, then unlock again. I am able to install TWRP, and use CF ROM with no issues but if I install CM, I get data but NO voice which is very odd.
Reflashing radios and messing with the network configurations did not help.
I've seen people that have unlocked twice and are able to run CM without any issues.
I've tried reflashing firmware, Reflashing SU38 and OTAing to 44 to no avail. I used to run CM before I relocked without a problem.
Although I do get errors flashing GPT partition, it says that it flashes backup GPT instead of primary.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
Is it possible you're not doing a full wipe? What version of twrp are you flashing with?
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
I realized that I can only make calls when VoLTE is enabled on stock. If I turn it off, I cannot make any phone calls but can access data still. I went into diagnostic mode and it showed " Phone ICCID compare with sim CCID error" with "UNKNOWN" under Phone ICCID. Hmmm..
Hey XDA,
So today I got my N Preview 2 OTA update and everything is fine and great. However I went into dev settings today to make sure I had debugging and OEM unlocking on but, if seems the Allow OEM unlock button is grayed out. Is anyone else seeing this? It may even be stuck on the Allow setting but, I really can't tell and it's a bit concerning. Any help would be appreciated thanks!
http://imgur.com/YeWFcO0
I have to ask the obvious question. Is your device already unlocked?
dahawthorne said:
I have to ask the obvious question. Is your device already unlocked?
Click to expand...
Click to collapse
Nope, status code 2 'locked' according to my bootloader.
He's right, I'm unlocked already and on np2 and I don't see OEM unlock in dev options either. They must be moving it to another location or something
Edit: I do see it now but you can't toggle the switch anymore
Sent from my Nexus 6 using XDA-Developers mobile app
looks like after the fiasco of the 1st preview that bricked phones during OTA & most of them have the bootloaders locked & OEM unlock in off position, this preview has put the oem unlock in default on position.
so if I am already unlocked and I flash the 2nd preview- am I OK? will the bootloader stay unlocked?
i believe so
looks like after the fiasco of the 1st preview that bricked phones during OTA & most of them have the bootloaders locked & OEM unlock in off position, this preview has put the oem unlock in default on position.
Click to expand...
Click to collapse
That makes sense...the op screen shot shows the button slider to the right (on position), even though grayed out.
LittleJakub said:
so if I am already unlocked and I flash the 2nd preview- am I OK? will the bootloader stay unlocked?
Click to expand...
Click to collapse
Yea, you're good. As long as you don't run the "fastboot oem lock" command through fastboot, your bootloader should always remain unlocked. Even if the "OEM Unlocking" toggle is switched off, an unlocked bootloader should remain unlocked.
I'm on NPC91K with a Nexus 6 and the "Allow OEM Unlock" option is grayed out and disabled for me. My phone is currently locked and Fastboot oem unlock does not work.
Griff Ellis said:
I'm on NPC91K with a Nexus 6 and the "Allow OEM Unlock" option is grayed out and disabled for me. My phone is currently locked and Fastboot oem unlock does not work.
Click to expand...
Click to collapse
Thanks for checking that out. Officially concerned now
I tried out NPC91K yesterday and the "Allow OEM Unlock" option was also grayed out , but the button was in the enabled position. After a while i out back backup and bootloader is still unlocked. In Bootloader it says Device is Unlocked Status code 3.
I am in the same situation, my phone is locked and N preview 2 now oem unlock is greyed out and disabled, anybody can suggest a way to enable this, TIA.
droidguy22 said:
I am in the same situation, my phone is locked and N preview 2 now oem unlock is greyed out and disabled, anybody can suggest a way to enable this, TIA.
Click to expand...
Click to collapse
Check out my post here on how to get around the oem unlock problem, and get back to marshmallow.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
Hello I have a new Moto G6. I have enabled developer options and I've enabled OEM unlocking. But it doesn't seem to stay enabled between reboots? I just bought this yesterday. I'm trying to unlock the bootloader, but I can't unless OEM unlocking stays enabled. Am I missing something? I know there's currently no root for the G6, but still I think I should be able to unlock it, or am I mistaken?
jloh1963 said:
Hello I have a new Moto G6. I have enabled developer options and I've enabled OEM unlocking. But it doesn't seem to stay enabled between reboots? I just bought this yesterday. I'm trying to unlock the bootloader, but I can't unless OEM unlocking stays enabled. Am I missing something? I know there's currently no root for the G6, but still I think I should be able to unlock it, or am I mistaken?
Click to expand...
Click to collapse
That just allows the bootloader to be unlocked. You still would need to actually unlock it following the unlocking guide thread in the guides section
dejello said:
That just allows the bootloader to be unlocked. You still would need to actually unlock it following the unlocking guide thread in the guides section
Click to expand...
Click to collapse
Yes I know this is not root, this is just unlocking the bootloader, yes I do have a key from motorola. But I can't do anything if OEM unlocking will not persist between reboots. I'm just trying to unlock the bootloader. And yes it is unlocked for sims.
jloh1963 said:
Yes I know this is not root, this is just unlocking the bootloader, yes I do have a key from motorola. But I can't do anything if OEM unlocking will not persist between reboots. I'm just trying to unlock the bootloader. And yes it is unlocked for sims.
Click to expand...
Click to collapse
I said nothing of root. Unless I am missing something from your original post, "Allow OEM unlocking" just allows the bootloader to be unlockable. After you tick it, reboot directly into fastboot mode (not back into android, that'll untick it again).
[GUIDE] Unlock Bootloader - This states after enabling OEM Unlock in settings (from within Android) to reboot into the bootloader (This guide says power off and then power back on while holding volume down, if you have debugging on you can just "adb reboot bootloader"). Rebooting back into Android with the bootloader still locked I believe does untick the OEM Unlock option.
ok thanks, I'll try again.
I have the XT 1925-6 US unlocked version. One of the first things I do with a new phone is to enable Developer Options and toggle OEM Unlock even though I may not Unlock the Bootloader right away.
The OEM Unlock toggle has stayed persistently on through numerous reboots with the Bootloader still locked.
Hmm.. Well I could have sworn I had seen what was described before, however it has been a while. I unlocked mine all in one go so I can't say. If it's supposed to stay on then I'd really be curious why it isn't for jloh
dejello said:
Hmm.. Well I could have sworn I had seen what was described before, however it has been a while. I unlocked mine all in one go so I can't say. If it's supposed to stay on then I'd really be curious why it isn't for jloh
Click to expand...
Click to collapse
I tried it again and it worked, thanks. I guess I rebooted android at first. Thank you.