Related
Any updates on getting closer to an unlocked boot loader?
danielpat89 said:
Any updates on getting closer to an unlocked boot loader?
Click to expand...
Click to collapse
Zero lg refuses to comment
Dreamlogix said:
Zero lg refuses to comment
Click to expand...
Click to collapse
LG should be offering the option like HTC Dev and Moto Dev to be able to manually unlock the bootloader. I am not sure if Samsung offers an option to manually unlock the bootloader but all the OEMs should give the customers a chance to manually unlock the bootloader.
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.
JulesJam said:
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.
Click to expand...
Click to collapse
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...
fury683 said:
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.
Click to expand...
Click to collapse
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.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
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.
JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
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.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
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.
fury683 said:
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.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.
fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
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.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
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.
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
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...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse
superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.
it leaves a copy of the fxz on your computer.
sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.
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.
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.
Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
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.
Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529
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.
breakthestatic said:
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.
Click to expand...
Click to collapse
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.
Maverick-DBZ- said:
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.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked
Droid turbo "OEM unlocking allow the bootloader to be unlocked" option under develope
I have a screenshot but I don't know how to upload it srry. But it is there. Is this for real?
The thread was supposed to say under developer options. My bad.
nils39 said:
I have a screenshot but I don't know how to upload it srry. But it is there. Is this for real?
Click to expand...
Click to collapse
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
tgambitg said:
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
Click to expand...
Click to collapse
I had a feeling that's what it was. But we can always hope.
I tried to unlock it just for shiggles, and of course it didn't work. It even gives you a finished response, but alas, was still locked.
Sent from my Droid Turbo
thats for device protection, a function like apple iphone lock,
http://www.greenbot.com/article/290...ow-about-device-protection-in-android-51.html
http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
if you disable that option, you can flash things on the phone leaving the phone unlocked and open.
Here's a screenshot from mine. It's kind of strange to me that they're talking about security and locking features but it clearly says allows bootloader to be unlocked. But I'm skeptical, unlocking a bootloader in my experience has never been as simple as a flick of a toggle.
Sent from my XT1254 using XDA Free mobile app
It's like we're repeating threads from a week ago.
matt30 said:
It's like we're repeating threads from a week ago.
Click to expand...
Click to collapse
Welcome to XDA, where the people can't read and the search button doesn't matter. :silly:
A mod needs to close this thread.
tgambitg said:
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
Click to expand...
Click to collapse
My Moto Maxx/Moto Turbo XT1225 has unlocked bootloader, as does the U.S. Moto Maxx XT1250, which is the device IDENTICAL to the Droid Turbo XT1254 (same FCC ID). The XT1250 runs just fine on Verizon with Verizon LTE SIM card (like a non- Verizon Nexus 6).
Speaking of which, the Motorola Nexus 6 has unlocked bootloader.
My point is, it's Verizon that is obsessed with locked down bootloaders, not Motorola.
Sorry, but
tgambitg said:
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
Click to expand...
Click to collapse
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
NapoleanSolo said:
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
Click to expand...
Click to collapse
Sorry, I don't believe you.
Install TWRP and root and post screenshot. If your bootloader is unlocked, that will take 5 minutes.
Another reason I don't believe you is because if this were true it would be all over the Droid Turbo 2 forum and over there they are still complaining about locked bootloader and no root. So, you really don't know what you are talking about.
_____
The Moto X Force (KINZIE) is the International version of the Droid Turbo 2 (KINZIE). It does have unlock-able bootloader, and has TWRP and root. When the Droid Turbo 2 bootloader actually is unlocked TWRP and root for KINZIE will work on it, just like TWRP and root for QUARK works on the Droid Turbo XT1254 (Quark) with all the other Quarks.
And over there, they are still ONE forum, just like all Quarks were one forum until a couple of months ago. So, it's easy to keep track of what's happening with all Kinzies.
NapoleanSolo said:
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
Click to expand...
Click to collapse
No it doesn't, what would make you think this would work, have you actually tried it?
Sent from my DROID Turbo using Tapatalk
Let's keep piling on...
NapoleanSolo said:
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
Click to expand...
Click to collapse
Sorry to bust your bubble, but that slider...yeah, it was on the Turbo when we got the 5.1 update. I could slide it to the "Unlock" position until I was blue in the face, but it had about a snowball's chance in hell of actually unlocking the bootloader. As @ChazzMatt suggested, try to flash TWRP and if you can, I'll eat my words. But the days of an easy unlock on VZW phones are long gone.
So, I just bought a Moto X Style.
And on the Developer options, also have the slide saying OEM Unlock.
It said that, meaning, during the process, the system/ tool will need the permission to unlock
and that slide allows that to happen
hieutrinh85 said:
So, I just bought a Moto X Style.
And on the Developer options, also have the slide saying OEM Unlock.
It said that, meaning, during the process, the system/ tool will need the permission to unlock
and that slide allows that to happen
Click to expand...
Click to collapse
Not relevant whatsoever for the Verizon locked down bootloader Droid Turbo XT1254. I wish people wouldn't keep digging up old threads that have been refuted.
The only thing that works with the XT1254 is paid Sunshine fueled exploit. Other Quarks (XT1225/XT1250) can be unlocked via Motorola website for free.
I've wanted to know if rooting the Droid Maxx 2 has become possible yet. I currently own a Droid Maxx 2, which is a Verizon one. It did come with the OEM unlock option, but even with it enabled, the bootloader isn't unlocked. I tried the Motorola Bootloader Unlock service, but it does not support this phone. I have tried several rooting apps, and just about none had worked. Is there any other way to do this? Thanks!
This forum is so dead, ugh. If you're on MM, then that would be a definite no as of right now, LP and lower have a better chance of being rooted, but none exist at the moment. This new quadrooter app has exposed some vulnerabilities that could lead to root escalation in most, if not all, vulnerable devices, but we would need to wait on someone to develop a tool/method for exploiting those vulnerabilities. That is the basket I'm putting all my eggs in at the moment, because this phone is far too unpopular for somebody to come along and put effort into a standalone rooting method.
Cross your fingers on the quadrooter exploits, it's likely our only hope for root.
MidnightLocke said:
It did come with the OEM unlock option
Click to expand...
Click to collapse
What's the OEM unlock option? Can I use it to remove the bloatware?
Just bought a VZW variant which was supposed to be unlocked. Unfortunately it clearly isn't. FIne, so i gotta do some work. Not a big deal, but I have no oem unlock option and none of the solutions I've found online seem to work. Sunshine also doesn't work. My goal is to s-off, unlock bootloader, sim unlock and hopefully get a stock unlocked ROM that will accept OTAs. The issue I'm having now, is that I simply can't start any of this process without being able to unlock the bootloader. Does anyone have a solution? I'd really love a bit of help here.
vijn said:
Just bought a VZW variant which was supposed to be unlocked. Unfortunately it clearly isn't. FIne, so i gotta do some work. Not a big deal, but I have no oem unlock option and none of the solutions I've found online seem to work. Sunshine also doesn't work. My goal is to s-off, unlock bootloader, sim unlock and hopefully get a stock unlocked ROM that will accept OTAs. The issue I'm having now, is that I simply can't start any of this process without being able to unlock the bootloader. Does anyone have a solution? I'd really love a bit of help here.
Click to expand...
Click to collapse
Only option at this point is mailing your device to jcase or beaups from Sunshine team for S-OFF,.
andybones said:
Only option at this point is mailing your device to jcase or beaups from Sunshine team for S-OFF,.
Click to expand...
Click to collapse
That's really annoying but hey, is what it is. Thanks for your help.