[LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China

[JulesJam]

There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.

Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.

 

[fury683]

There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.

Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.

I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.

I can't imagine the OTA would lock the bootloader, but who knows...

 

[JulesJam]

I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.

But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.

Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.

I can't imagine the OTA would lock the bootloader, but who knows...

I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.

 

[fury683]

These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.

Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.

Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.

Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.

 

[JulesJam]

Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.

The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.

Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.

Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.

 

[JulesJam]

, just that people had the same thoughts when the N6 came out

No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.

and it wasn't a problem

On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.

 

[superkeest]

Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?

 

[Saythis]

Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..

 

[athulele]

Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..

The option only appears when you update to 5.1 with your bootloader locked.

 

[KidJoe]

Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...

Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand

But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.

For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.

So yeah, as you said...

It's an abundance of caution, I get it.

 

[JulesJam]

Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?

Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.

 

[sseuorosal]

it leaves a copy of the fxz on your computer.

 

[JulesJam]

it leaves a copy of the fxz on your computer.

Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.

 

[Icon000]

Any Updates on this situation?

It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.

 

[rjcrystal199]

dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.

 

[KidJoe]

It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.

The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.

The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.

I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.

 

[KidJoe]

Further... I asked in the Sunshine thread...

See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529

 

[breakthestatic]

I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.

 

[-Maverick-]

I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.

Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.

 

[ryusufu]

Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.

How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked