Database Users

Root vs. Unlocked bootloader

In this thread I intend to give some basic insight about these two concepts, which are closely entwined with our phone's experience. I'm not a tech guy, but I think this little summary might clear some doubts for people who are new to this kind of issues (people who come from other non-Android phones especially). All feedback is welcome, in particular the one of people who can expand the topic with their knowledge.
"Root" is the common way to refer to the fact to the user account which has superuser rights on the device. Superuser rights imply full control over your phone's capacities, which are determined by the software and the hardware of the device. Non-superuser accounts have limitations, usually established for the sake of software security (for example, not allowing a user to disable critical functions such as phone or GPS), hardware safety (not allowing to change the processor's frequency speed, aka overclocking the CPU) or, in some cases, for someone's profit (disabling wi-fi tethering is a typical one as users are forced to buy data plans in order to use their devices to tether). In Android's case, Superuser is composed of an app* and a set of instructions to give this app root rights.
The bootloader is a program which accesses the internal storage and, basically, controls the loading of the programs and data necessary to initiate the sequence of launching the OS (aka booting, thus the name bootloader). We say that a bootloader is locked when it is programmed in such a way that it won't allow to load the device if it detects data from third-party sources. Unlocked bootloaders do allow these data and will load what these data contain, which will be usually a modified version of the phone's firmware, known as "Custom ROM".
As we can see, there was the fear that one would need to have unlocked bootloaders (i.e the ability to load third-party data in the booting sequence) in order to gain root rights. This would have been terribly inconvenient because only a minority of users will have unlocked bootloaders, since the phones with unlocked bootloaders by default are the ones sold carrier-unlocked. Said carrier-free phones will be a minority as the phone is pretty expensive: most Xperia Plays will be sold using carrier subsidies.
However, our fellow member Chainfire found an exploit (a programming loophole) in Gingerbread which allows said app and instructions to be loaded without the need of touching the bootloaders. Basically, his Gingerbreak program allows the user to have root rights without loading any bootloader-sensitive data. This widens the possibilities for the majority of users who will buy this phone with a subsidy.
*edit 3* Later on, it has become possible to unlock the bootloader even for SIM-locked devices, thanks to different unlockers like Alejandrissimo and Jinx13. This means that, provided that you pay what they charge, you can have your device set up without the bothers of having to buy a SIM-free phone. What's better: their method of unlocking the bootloader SIM-unlocks the phone as well.
I think this is more or less a succint framework of ideas which allows us to define "root" and "unlocked bootloaders" properly. As they say, knowing is half the battle, so I hope this nugget of information allows users to deal with their phones with more confidence.
*edit* as of version 2.3.3, this information has changed. Gingerbreak doesn't work with 2.3.3 anymore, and it seems now that the only way to root with locked bootloaders is to flash a 2.3.2 rom with FlashTool and update through OTA.
*edit2* note that this explanations pertains mostly to the Xperia Play. Other devices are NAND-locked, which means for us that they need unlocked bootloaders to even get root access.
*Note that Android is built in such a way that every app is a user account with limited rights (the ones specified before you download it). Thus, Superuser is a user account as any other app and the set of instructions is meant to give this user account root rights.

Thank you! This was very helpful in clarifying some things.

"As we can see, there was the fear that one would need to have unlocked bootloaders (i.e the ability to load third-party data in the booting sequence) in order to gain root rights. This would have been terribly inconvenient because only a minority of users will have unlocked bootloaders, since the phones with unlocked bootloaders by default are the ones sold carrier-unlocked. Said carrier-free phones will be a minority as the phone is pretty expensive: most Xperia Plays will be sold using carrier subsidies"
by carrier unlocked do you mean sim unlocked? sorry 4 noob question

Indeed, that is what I mean.

Logseman said:
Indeed, that is what I mean.
Click to expand...
Click to collapse
Alright, I asked this question and it was answered, but I want to make sure before I try anything.
I just found out from SE that my phone is the Rogers version. It's obviously been unlocked because I'm using it on AT&T.
What I don't know, though, is whether the bootloader is unlocked. Another member recommended that I check TrackID to see if it worked because it depends on the manufacturer DRM's that are wiped in unlocking the bootloader. It did work, so I assume it's still locked, but I wanted to confirm because of being carrier unlocked.
Sent from my R800a using XDA App

If TrackID works, your bootloader is locked, regardless of simlock.

I have a Sim-Unlocked Xperia Play from Rogers that I am using on ATT's network. My phone is boot-locked. When powered off, if I hold the search key while plugging in the USB cable, I do not get a blue light.
I was able to flash the firmware by holding the back key while plugging in the usb cable (with the phone off). I get a green light when I do this. Using flashtool, I was able get 2.3.3 rooted by loading the 2.3.2 firmware, rooting, and then updating OTA.
I bricked my phone several times while loading the firmware and each time I was able to fix it with flashtool or Sony Ericsson's Upgrade Utility. I found that you need a good USB cable, and even then it failed sometimes. I just kept trying and eventually it worked.

We wanted to provide an update on HTC’s progress with bringing bootloader unlocking to our newest phones. We know how excited some of you are for this capability, and we’ve put significant resources behind making this change as soon as possible. While we wish we could flip a simple switch and unlock all bootloaders across our device portfolio, this is actually a complex challenge that requires a new software build and extensive testing to deliver the best possible customer experience.
We’re thrilled to announce today that software updates to support bootloader unlocking will begin rolling out in August for the global HTC Sensation, followed by the HTC Sensation 4G on T-Mobile USA and the HTC EVO 3D on Sprint. We’re in the testing phase for the unlocking capability now, and we expect it to be fully operational by early September for devices that have received the software updates. We'll continue rolling out the unlocking capability over time to other devices as part of maintenance releases and new shipments.
HTC continues its commitment to unlocking bootloaders and supporting the developer community. Because of the importance of this community to us, please expect an update on this about every few weeks as we make progress toward launch. Thank you for your patience and continued support!
(they claim it will come to only two devices for starters the EVO 3D and the Sensation 4G and then it will slowly rollout to other devices that already have 2.3 or enough internal memory on them, this will all start in last August an early September for the first two droids listed... and others will soon follow suit, the only question is do you want you bootloader to come unlocked stock? Or will you buy it locked and be able to sit around and wait for your device to get an update to do so?? LOL

thats why my phone couldnt flash back to 2.3.2..(?)
I live in singapore.. phones are not carrier specific.. so does that mean my BL was unlocked even before I used gingerbreak?

I know this doesnt pertain to the play per se, but maybe you should add that, with nand locked devices, an unlocked bootloader is required to acheive full root, just incase someone with another device googles this question and ends up here

pros and cons of unlocked bootloader
Pros/Cons of rooting WITHOUT unlocking bootloader?
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).

tommyinhi27 said:
Pros/Cons of rooting WITHOUT unlocking bootloader?
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
Click to expand...
Click to collapse
The N1 is made by HTC, generaly with htc devices, flashing a stock rom, will re-lock the bootloader, If you decide just to root, you will need a custom kernel before you can O/C All that unlocking the bootloader does is 2 things, It will security unlock the nand (on nand locked devices) allowing r/w access to read only partitions, and it allows you to issue fastboot commands to your device, the main reason alot of play owners went down the unlocking the bootloader path, is that atm it is the only way to flash custom roms other devices, have found sneaky ways to push a custom recovery without unlocking bootloaders, and thus do not need one to flash a custom rom

AndroHero said:
I know this doesnt pertain to the play per se, but maybe you should add that, with nand locked devices, an unlocked bootloader is required to acheive full root, just incase someone with another device googles this question and ends up here
Click to expand...
Click to collapse
I'm not too knowledgeable about the whole Nand thing, so I think you could give a much better explanation about it. I'll include it then

whoa whoa whoa!!!! i achieved root on 2.3.3 with no prob using superoneclick v2.3.3. it works beautifully!

Yes, but you're replying to a thread that's 8 months out of date too!
Sent from my R800x using XDA

Lol. I know, but I've been trolling the site, and I think it may need a bit of new info so someone doesn't follow the steps here now that a better method has been found.
Sent from my R800at using XDA

isavegas said:
Lol. I know, but I've been trolling the site, and I think it may need a bit of new info so someone doesn't follow the steps here now that a better method has been found.
Sent from my R800at using XDA
Click to expand...
Click to collapse
why not just stop bumping heavily old threads? then they can rest in piece
and nobody would care
the information thatit's outdated is alreada given in 1st post.
u also could ask a mod to close this as its outdated...

Hey, this thread may be outdated, but it's not my fault if someone necros old threads. Just let it die.

question
can i flash custom roms in a locked bootloader?

yes
big txmer said:
can i flash custom roms in a locked bootloader?
Click to expand...
Click to collapse
only stock gb ones nothing else

Xperia Play question here and I am in need of a few answers

Hi there so I am not new to rooting and flashing roms but not an expert either. I have a Xperia play I got from Verizon(yes horrid verizon) few problems as I can see I cant unlock bootloader, I assume this because in configurations settings there is no root option or even a bootloader unlock yes or no so from what iveread im screwed in that area.
My other problem is and htis is now on 3 phones of xperia play verizon has sent me they all have version of android 2.3.2 and when i try to do the manual update I get this mssg and I have bene trying this on all the ones they sent me and even contacted them with sony on the line and they cant understand why(morons). only solution is to send to them but perhaps someone here can help me. Here is the mssg. it tells me there was an error downloading hte software and it please try again later it has said this for weeks since ive had it everytime i try even after doing a hardreset and this is on all 3 xperia plays they have sent me so it must be something they have done.
Can I still manual update it at least to 2.3.4 using the method from sony and discussed on here using a flashtool x10 but im not sur what version of flash to use since they show like 3 main ones for different types and if so if im using windows what version of flashtool for my xperia play from verizon would i get for my xperia play r800x?
Any ideas and help would be great thanks agian.

You can use the latest one.

Hi talrune,
I'll try to answer some of the questions you posted, but I may be wrong on some things. (If anyone can see anything wrong please feel free to correct me) As far as rooting the device it can be done. It has been awhile since I rooted mine and I cannot remember how I did it. I'm sure a quick google search will pull it up. As far as the bootloader, you can unlock it but you have to pay to have it unlocked. Alejandrissimo was offering this service a while back and I assume he still is. If you would like to get your bootloader unlocked you will have to get in touch with him.
I do not know why you would be having trouble with upgrading to 2.3.4 from Verizon OTA. I am pretty sure however that you cannot use flashtool to install the update without having an unlocked bootloader. Also, the directions from sony are no good. Unless they have changed things they want you to use PC companion or something to download and install the update. This works fine, however, when they ask you to connect the phone they require they phone be connected in MTP mode (I believe) and there is no way to put the R800x into this mode. I called sony and they asked me to go into the system menu and go to the Sony Erriccson tab, but this tab does not exist on the verizon phones (dang verizon!!!)
If you have the money I would strongly suggest getting the bootloader unlocked. It is extremely helpful when Verizon fails in epic fashion. Plus its fun to play around with different roms and kernels. Goodluck :laugh:

with a locked-bootloader flashtool should work, but fastboot should not.
there a firmware stickied in the Development forum for the VZW R800x

Bootloader unlock allowed : no

As the title says, It seems the bureaucrats at EE UK network are using phones that cannot be bootloader unlocked, even if Sony do allow, albeit with some loss of features.
Considering I flashed a generic rom, and my important photos/whatsapp files got wiped (I forgot to backup) as it was stated with flashtool only account based user data will get wiped not data from internal memory/sd card, well that didn't work.
I needed to root to allow some recovery software get my photos/whatsapp files back.
Now finding that the booloader is unlockable . I just want to throw the phone at the kunts at EE management. " EE the UK's biggest and fastest growing, bunch of dicks!"
Is their anybody else on EE who's bootloader is unlockable?
I'm so depressed with this all.

You needed to root to recover deleted files that you deleted by rooting?

davestuarts said:
As the title says, It seems the bureaucrats at EE UK network are using phones that cannot be bootloader unlocked, even if Sony do allow, albeit with some loss of features.
Considering I flashed a generic rom, and my important photos/whatsapp files got wiped (I forgot to backup) as it was stated with flashtool only account based user data will get wiped not data from internal memory/sd card, well that didn't work.
I needed to root to allow some recovery software get my photos/whatsapp files back.
Now finding that the booloader is unlockable . I just want to throw the phone at the kunts at EE management. " EE the UK's biggest and fastest growing, bunch of dicks!"
Is their anybody else on EE who's bootloader is unlockable?
I'm so depressed with this all.
Click to expand...
Click to collapse
In Poland Orange locks bootloaders for good in SONY devices, as I know there are tricks to make it unlockable, but not sure if possible to do it at home.

adamk7 said:
You needed to root to recover deleted files that you deleted by rooting?
Click to expand...
Click to collapse
I have not rooted yet, have only applied a generic less bloated rom. But now I need to root, so I can use software like 'hexamob recovery' which needs root to access the internal memory.
Tbh, the photo's I took that got wiped are sentimentally so important, hence me getting so stressed about it.
rollesky said:
In Poland Orange locks bootloaders for good in SONY devices, as I know there are tricks to make it unlockable, but not sure if possible to do it at home.
Click to expand...
Click to collapse
Oh, so orange there do the same. Here its now T-mobile/orange joined together as EE.
There must be a way to change that Bootloader state to yes. I know Orange/EE won't do it. Many people have asked in their forums about similar devices.
Thx for the insight tho...

I'll be totally honest with you here & you wont like the answer...
...if it says "bootloader unlock allowed: no" it will most probably stay that way.
My last Sony phone was from O2 & it was the same story.
The history of Sony phones with that state have stayed that way, as far as I'm aware
This means, once (optimistic) we get root you will only be able to flash stock based roms
Considering rooting newer versions of android seem to be getting more difficult, finding a way to bypass the bootloader is going to be near impossible...never say never but don't hold your breath.
The only Sony phone I had where the bootloader got unlocked unofficially was the X10 mini pro (beast phone) & that is when they were still Sony Ericsson & over 2 years after release (luckily back then you could flash CM / AOSP etc with locked bootloader, not any more though!)
Best bet is, give the phone back & buy it from a reseller like Clove / Handtec if unlocking the bootloader is that important to you & its not a contract deal you're after (or get sim only contract or something...PAYG FTW)
Otherwise, remember this for next time...

davestuarts said:
I have not rooted yet, have only applied a generic less bloated rom. But now I need to root, so I can use software like 'hexamob recovery' which needs root to access the internal memory.
Tbh, the photo's I took that got wiped are sentimentally so important, hence me getting so stressed about it.
Oh, so orange there do the same. Here its now T-mobile/orange joined together as EE.
There must be a way to change that Bootloader state to yes. I know Orange/EE won't do it. Many people have asked in their forums about similar devices.
Thx for the insight tho...
Click to expand...
Click to collapse
phroenix said:
I'll be totally honest with you here & you wont like the answer...
...if it says "bootloader unlock allowed: no" it will most probably stay that way.
My last Sony phone was from O2 & it was the same story.
The history of Sony phones with that state have stayed that way, as far as I'm aware
This means, once (optimistic) we get root you will only be able to flash stock based roms
Considering rooting newer versions of android seem to be getting more difficult, finding a way to bypass the bootloader is going to be near impossible...never say never but don't hold your breath.
The only Sony phone I had where the bootloader got unlocked unofficially was the X10 mini pro (beast phone) & that is when they were still Sony Ericsson & over 2 years after release (luckily back then you could flash CM / AOSP etc with locked bootloader, not any more though!)
..
Click to expand...
Click to collapse
What phroenix said is true.
From Xperia T (2012) onwards, there's no chance to get the bootloader unlocked if you read "bootloader unlock allowed: no".
@davestuarts Your old customization was 1289-4465 (T-mobile/EE) so I'm making a new FTF for you with that old firmware, let's try this way

istux said:
What phroenix said is true.
From Xperia T (2012) onwards, there's no chance to get the bootloader unlocked if you read "bootloader unlock allowed: no".
Sony, will they ever learn. I'm glad I didn't get rid of my viper running One X yet.
Tbh, the Sony layer on kitkit is pretty good considering and I'm plenty happy keeping stock roms, My main things are to run exposed and xprivacy.
@davestuarts Your old customization was 1289-4465 (T-mobile/EE) so I'm making a new FTF for you with that old firmware, let's try this way
Click to expand...
Click to collapse
Thanks istux, appreciate the help and less stress feeling.
Tha

Official Asus ZE551ML Bootloader Unlock *10/16: CAUTION ADVISED*

10/16/2015:
*CAUTION ADVISED*
Individuals have reported fastboot problems impacting their devices after attempting an official unlock. Review thread and proceed at your own risk.​
----------
Official unlock!
Just noticed this on the official Asus site under 'Utilities':
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V2.20.40.59 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.​https://www.asus.com/us/support/Down...Ulh0Ph49Hl/32/
Update: Date stamp on the APK of 7/23/2015 is interesting. Ran on my unlocked ZE551ML and after accepting the terms of use, it complained that my model was not supported.

Oh crap nice find... Now if I use this I cannot or can do ota updates?

Worked here perfectly fine! Thanks!! Make sure you are on a stock ROM when you try

this is a great step!! thank you!!!
i checked: there is also for ZE550ML !!!

It's announced now
Khanger posted the announcement on reddit about an hour ago in /r/zenfone2/

Took 7 months but it's finally here haha.

Is there a difference between the official unlock and the previously known method of unofficial unlock? Unlocked bootloader is the same either way, correct?

Reddit thread says you will not get OTA after using this file.

onurd said:
Is there a difference between the official unlock and the previously known method of unofficial unlock? Unlocked bootloader is the same either way, correct?
Click to expand...
Click to collapse
Would like to know this as well.

Sad it does only concern 551ml version.

A, Does this unlock automatically give root?
B, And lets say I use this BUT I remain with stock, will I still be barred from OTA?

550 - direct download (source page, look under "Utilities"), mirror: mega
551 - direct download (source page, look under "Utilities"), mirror: mega

gontie said:
Sad it does only concern 551ml version.
Click to expand...
Click to collapse
nope
also for 550ml version
https://www.asus.com/Phone/ZenFone_2_ZE550ML/HelpDesk_Download/
under utilities

sumean said:
A, Does this unlock automatically give root?
B, And lets say I use this BUT I remain with stock, will I still be barred from OTA?
Click to expand...
Click to collapse
A) why would it? Root access and unlocking bootloader are completely different things.
B) if you unlock via official method, your warranty is void and your phone is barred from receiving OTAs.

I understand it voids the warranty but what I don't understand is why no updates? If you take an OTA and it hoses your out of warranty phone its on you.

hope someone discover relock method

Druboo666 said:
hope someone discover relock method
Click to expand...
Click to collapse
From the official unlock, there likely will never be a way to relock and get back OTA functionality. That being said, adb sideloading OTA files should still work. Reasoning as such:
* Unlocking your device using the official APK sends a notification to ASUS that your device is now unlocked, out of warranty, and will not have OTAs pushed to it.
* Whether or not you can manually grab OTAs using the system app has yet to be seen, as we haven't received a new update since the official bootloader unlock method has been released. Personally, I believe our SSIDs will be blocked from getting anything from the OTA server based on the verbage in the disclaimer.
* adb sideloading a ZIP file should have no reliance on the bootloader status. As long as you're flashing the right file, it should work because adb sideload has no internet functionality so it can't call home to check on your ability to flash things. It would be a very poor decision to actively bar users who do the unlock from using official firmware updates on their own terms.
Anyways, I'm adventurous so I've taken the plunge of my own accord. I don't plan to put TWRP on or flash CM12.1 until the majority of the CM bugs have been resolved. When the next OTA comes out, I'll post my experience in obtaining and flashing it so that others can know if they want to unlock the bootloader officially as well.
I will comment specifically that Motorola bootloader unlocks did not bar their users from getting official OTAs after the fact. It is an assumed risk to unlock the bootloader and it's a bit salty to basically say "well, you did this, you don't deserve to automatically get what we're baking for you now". The fact that we got an official unlock at all is scores above what most other manufacturers have done, though. Hopefully, ASUS backs off of the no-OTA thing at some point as it is a bit unnecessary. At worst case, I'm trusting us all here at XDA to work your magic if we end up in a corner somehow.

my question is: if their unlocking method brick my phone???? warranty is expired and they don't take him ???
this method is a weird thing.

MatteXperiaU said:
my question is: if their unlocking method brick my phone???? warranty is expired and they don't take him ???
this method is a weird thing.
Click to expand...
Click to collapse
Attempting to unlock your phone is the same this as actually unlocking your phone: you're taking it's life in your hands. If you brick it trying to unlock it, it's not covered. If something happens to it after it's been unlocked, it's not covered. This does not necessarily mean that they won't repair it, it means that:
a) any repairs cost money out of pocket and
b) they have the right to say a device is unrepairable and send it back to you with no obligation to fix it or compensate you in any way.
Them's the breaks for being a tinkerer!

Level99 said:
Attempting to unlock your phone is the same this as actually unlocking your phone: you're taking it's life in your hands. If you brick it trying to unlock it, it's not covered. If something happens to it after it's been unlocked, it's not covered. This does not necessarily mean that they won't repair it, it means that:
a) any repairs cost money out of pocket and
b) they have the right to say a device is unrepairable and send it back to you with no obligation to fix it or compensate you in any way.
Them's the breaks for being a tinkerer!
Click to expand...
Click to collapse
yeah, i think there are no phones with unlocked bootloader and warranty ok..
the only way is relock bootloader..no news for that now..
you said it is not possible..are you sure? i think unlock bootloader is an offline method?

Moto X Style updates without cell carrier?

I'm thinking about getting a Moto X Style just for use everywhere I have wifi coverage (I'd have no cellular service/carrier at all). Does anyone know if I will still get all of the security/OS updates or can they only come from a carrier?

If you buy it from Motorola directly, the carrier is not involved. But don't think that means you'll get timely updates. Apparently Moto used to be good at this, but no longer. Mine is still on Android Security Patch Level: February 1, 2016

Can anyone confirm they've gotten an OTA update without a SIM card installed or been able to load current updates with Motorola Device Manager?

xdafan15 said:
Can anyone confirm they've gotten an OTA update without a SIM card installed or been able to load current updates with Motorola Device Manager?
Click to expand...
Click to collapse
I have with my Moto G3 which is unlocked, purchased from Motorola. Haven't tried with the Pure, but it is a carrier free device as well.
If you watch logcat and check for updates on the device, you'll see it connects to a Motorola server to check as well.

Pretty sure that's how all the tmo people got the update before it was released to them.

Has anyone had experience using Motorola Device Manager to load current updates or are they only available over the air?

MXPE is not carrier branded so you can get OTA without a SIM. Doesn't matter where you buy the phone (I have seen it sold on Amazon and Best Buy as well)
Sent from my awesome phone!

xdafan15 said:
Can anyone confirm they've gotten an OTA update without a SIM card installed or been able to load current updates with Motorola Device Manager?
Click to expand...
Click to collapse
I received my Moto X Style on Friday, didn't have a sim card inserted when I plugged it on. It was on Android 5.1.1 and as soon as I set out the home wifi, it told me there was a software update, and I got 6.0 installed.

xdafan15 said:
Has anyone had experience using Motorola Device Manager to load current updates or are they only available over the air?
Click to expand...
Click to collapse
Has anyone used MDM?

xdafan15 said:
Has anyone used MDM?
Click to expand...
Click to collapse
We're all trying to tell you that it works, it's fine, you don't need to worry. Carriers are not involved in delivering updates for unlocked devices because a) nothing is customized by any carrier on the unlocked device and b) your only relationship with them is via the SIM card, and you haven't paid them anything for the device. At the risk of sounding condescending, the thing you're worried about is just not how it works.
However, I went ahead and tried to install MDM just to test it out, and it seems that software has other unrelated problems and I can't use it.
So instead, I turned off mobile data and took the SIM card out, and confirmed yet again that it can connect to Motorola's update server and report that there are no updates available. So that's the real problem: you can update the device, but there are no updates to be had.
Edit: maybe the confusion is that term "OTA". Are you just talking about OTA as in over the cell network, or are you referring to WiFi as "OTA" as well? You know that those two work differently, right? OTA updates from a carrier via the cell network clearly only come from them, and clearly can't happen without a SIM. But there's not much difference in downloading the update from Motorola's server via WiFi on the device vs. downloading it via WiFi on your computer with MDM and sending it to the device via USB; it still comes from Motorola.

thejoelpatrol said:
We're all trying to tell you that it works, it's fine, you don't need to worry. Carriers are not involved in delivering updates for unlocked devices because a) nothing is customized by any carrier on the unlocked device and b) your only relationship with them is via the SIM card, and you haven't paid them anything for the device. At the risk of sounding condescending, the thing you're worried about is just not how it works.
However, I went ahead and tried to install MDM just to test it out, and it seems that software has other unrelated problems and I can't use it.
So instead, I turned off mobile data and took the SIM card out, and confirmed yet again that it can connect to Motorola's update server and report that there are no updates available. So that's the real problem: you can update the device, but there are no updates to be had.
Edit: maybe the confusion is that term "OTA". Are you just talking about OTA as in over the cell network, or are you referring to WiFi as "OTA" as well? You know that those two work differently, right? OTA updates from a carrier via the cell network clearly only come from them, and clearly can't happen without a SIM. But there's not much difference in downloading the update from Motorola's server via WiFi on the device vs. downloading it via WiFi on your computer with MDM and sending it to the device via USB; it still comes from Motorola.
Click to expand...
Click to collapse
Thank you for trying to test MDM for me, I really appreciate that. I wish it had worked properly.
I'm not asking about MDM because I'm still questioning the OTA availability. That has been answered.
I'm asking because in the past, rooted phones wouldn't accept OTAs, so I'm trying to figure out how to apply security updates without having to un-root, then re-root. Maybe the answer to this is obvious, but it isn't to me.
Maybe the OTA availability problem mentioned above isn't an issue any more as I believe Marshmallow uses systemless root? I probably will stick with the stock ROM, just rooted.
 @thejoelpatrol, are you rooted? If so, have you continued to be able to apply updates OTA?

xdafan15 said:
Thank you for trying to test MDM for me, I really appreciate that. I wish it had worked properly.
I'm not asking about MDM because I'm still questioning the OTA availability. That has been answered.
I'm asking because in the past, rooted phones wouldn't accept OTAs, so I'm trying to figure out how to apply security updates without having to un-root, then re-root. Maybe the answer to this is obvious, but it isn't to me.
Maybe the OTA availability problem mentioned above isn't an issue any more as I believe Marshmallow uses systemless root? I probably will stick with the stock ROM, just rooted.
@thejoelpatrol, are you rooted? If so, have you continued to be able to apply updates OTA?
Click to expand...
Click to collapse
Ah, ok, now see that is a whole other issue. That would have been good to know from the start. No, I'm not rooted, but it's getting increasingly tiresome, so I'll probably need to do that at some point. I've mostly used Cyanogenmod in the past but last I checked it wasn't ready for clark. I'll probably take a look at some stock root options when I get around to it. And so your concern here is worth thinking about.