Database Users

Just purchased a MXP and have questions

While I wait for the arrival of my MXP I have some questions for the community so that I can hit the ground running. First thing, I'd like to unlock my boot loader but I was just curious if there is a way to re-lock it afterwards just in case I need to send in for repairs or something along those lines? Also wondering about VOLTE support. I see some roms that state they have it working but is this a stock feature or do I need to use a custom ROM to get VOLTE to function? Also is there any known method of rooting without unlocking the boot loader just in case re-locking it is not possible? Thanks for the help everyone.
I am coming from a g920a. That phone is torture for someone like me who likes stock Android and rooted devices. Probably the worst phone I have ever had. Can't wait to get my hands on my MXP and leaves this piece of junk behind!

I'm on Verizon and I can confirm it supports advanced calling, which is VoLTE as far as I know but it might require turning it on at the provider level.
Sent from my XT1575 using Tapatalk

I haven't messed with VoLTE yet so I can't answer those questions, but as for your others: The bootloader can be relocked, but the unlock method involves submitting an unlock request code to motorola, and they immediately email you an unlock key, along with a warning about voiding your warranty, so even relocking it does not unvoid your warranty. HOWEVER, it only voids your warranty for software issues. If it's a hardware problem unrelated to the bootloader being unlocked, they'll still handle it, and accidental drops and things are still covered if you buy an accidental damage warrenty. Also, as far as I know there is still no way to root without unlocking the bootloader.

10 characters

squallz506 said:
Volte is only available on stock roms.
Click to expand...
Click to collapse
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk

countryfolk07 said:
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Whoops, yeah I guess they fixed it down the line. Sorry, I've been enjoying stock+xposed too much to follow custom development.
Edit: also root without bootloader unlock will likely never happen. We have a root method already, so there's no incentive to find another method.

The answer you seek was right in the first page of this forum....
http://forum.xda-developers.com/moto-x-style/general/moto-x-style-how-to-unlock-bootloader-t3192140
That being said, I would consider waiting until after Marshmallow drops before you unlock your bootloader so as not to interfere with any OTA's. Conventional wisdom is that it is coming within the next few weeks as the "test drive" has already started and a "soak test" should follow shortly.

yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?

timde9 said:
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
Click to expand...
Click to collapse
Well as to it being a thing, I certainly can't say for sure. But what reason is there to unlock the bootloader if you're not going to root? And once you do that, you almost certainly will not get OTA's. What am I missing? Is there another reason you are looking to unlock?
The one thing I don't know is if there a some type of a "tamper flag" that would require something like triangle away.
You don't think you could just do a fastboot oem lock?

Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again

timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
I'd still recommend waiting at least a couple of weeks to see if Marshmallow shows up!
I'm coming to the MXPE from a OnePlus One which I have to say was one of the funnest phones I've ever owned. I wasiunlocked, rooted and flashing CM12.1 nightlies about twice a week.
I thought I would miss it, but so far so good on the MXPE without rooting. We'll have to see what happens after MM drops. I'd like to get it rooted, but I haven't done nearly the amount of modding you've done.
Good luck with your phone. I can honestly tell you it's a really nice device!

While its tempting to wait for marshmallow to show I cannot live without root any longer. I have already been without it for months because of this damn s6. I'm sure someone will upload the OTA as soon as it's available so I'll just flash it when the time comes.

timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
Well if you're an xposed user you should root immediately with no concern about the 6.0 OTA, since xposed doesn't work on 6.0. I'm not moving to 6.0, myself, until xposed is released for it. I use xposed modules everyday and am not giving it up, not even for doze mode.

That's kinda how I am feeling as well. I can achieve similar results to doze with the xposed app amplify with enough tweaking so its not a big deal.

Will Non-Verizon Firmware Work?

Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.

btonetbone said:
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
Click to expand...
Click to collapse
we're stuck on verizon's firmware. i use viper and the software is updated to the latest release, just not using the eu/intl firmware.

btonetbone said:
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
Click to expand...
Click to collapse
If you are on Verizon you should be using Verizon firmware. Just because a version number is different doesn't mean it's ahead. They are different forks tested and tweaked for entirely different networks.
Sent from my HTC6545LVW using Tapatalk

dottat said:
If you are on Verizon you should be using Verizon firmware. Just because a version number is different doesn't mean it's ahead. They are different forks tested and tweaked for entirely different networks.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
But does that hold true when flashing the Verizon radio behind the other firmware?(not challenging your statement here, just asking a variation of the OP question)
I think that is the main thing people want to know when this topic comes up. I've seen the question and information on it scattered in pieces across multiple threads, but never fully answered by being backed with a report by someone who did it.
So you don't think I am one of those that just sits back to let someone else do the work - I am willing to try such a thing by flashing the US unlocked or Europe FW followed by the VZW radio you pulled, but would need a little guidance in terms of how to provide feedback. Test signal before/after? I know from Viper thread loss of camera is something to watch out for. Any other specific items/parameters to check before/after? Since Viper just did a re-base, I have been searching and debating between those two FW anyway. First the Euro to match the ROM, then the US because they have the ROM flashing on all FW out at the moment.

camparks said:
But does that hold true when flashing the Verizon radio behind the other firmware?(not challenging your statement here, just asking a variation of the OP question)
I think that is the main thing people want to know when this topic comes up. I've seen the question and information on it scattered in pieces across multiple threads, but never fully answered by being backed with a report by someone who did it.
So you don't think I am one of those that just sits back to let someone else do the work - I am willing to try such a thing by flashing the US unlocked or Europe FW followed by the VZW radio you pulled, but would need a little guidance in terms of how to provide feedback. Test signal before/after? I know from Viper thread loss of camera is something to watch out for. Any other specific items/parameters to check before/after? Since Viper just did a re-base, I have been searching and debating between those two FW anyway. First the Euro to match the ROM, then the US because they have the ROM flashing on all FW out at the moment.
Click to expand...
Click to collapse
So here's the thing... you will see unlocked users who simply flashed the radio complain they often get stuck on 3g/1x. You will see the posts about the camera loss. You will see things about loss of volte. The firmware is always optimized for the rom/carrier for which it was written. They won't include vzw fixes in unlocked firmware since that phone isn't targeted for use on the vzw network.
Between the rom and the firmware it's really just a different fork altogether. They aren't mean to be used without each other as a dependency.
Euro firmware will likely have some odd wifi side effects for some folks as they use different bands over there.

dottat said:
So here's the thing... you will see unlocked users who simply flashed the radio complain they often get stuck on 3g/1x. You will see the posts about the camera loss. You will see things about loss of volte. The firmware is always optimized for the rom/carrier for which it was written. They won't include vzw fixes in unlocked firmware since that phone isn't targeted for use on the vzw network.
Between the rom and the firmware it's really just a different fork altogether. They aren't mean to be used without each other as a dependency.
Euro firmware will likely have some odd wifi side effects for some folks as they use different bands over there.
Click to expand...
Click to collapse
So can we back up just a bit to where I believe this all stems from - Is the HTC 10 truly a single-hardware phone? Therein, making all "variants" manifested only by which firmware is flashed? Is that true globally? If not, is that true for all in a particular "zone"(Europe, Asia, US, etc.)?
Ok, with the Euro FW the issues are apparent, given different standards not only for cellular, but also the camera and wi-fi vary from those here in the US. Even if one were to flash a US carrier radio, the camera and wi-fi issues could still pop up. Moving on from that consideration.
For US unlocked, there should be no standards issue, correct? Assuming hardware is the same for atleast all US carriers, what besides the radios would differ between carriers when not running stock ROMs?
Obviously there would be issues when on stock ROMs due to custom apps, features, etc. that would break not only when running different non-stock FW, but also when running one carrier's stock ROM on another carrier's network. All that is ill-advised and goes back to you only recommending stock FW.
Thanks for discussing this. I do not question your advise at all, I just want to explore the what and why of it all to put it all in one place. Thanks for humoring me and my questions!

camparks said:
So can we back up just a bit to where I believe this all stems from - Is the HTC 10 truly a single-hardware phone? Therein, making all "variants" manifested only by which firmware is flashed? Is that true globally? If not, is that true for all in a particular "zone"(Europe, Asia, US, etc.)?
Ok, with the Euro FW the issues are apparent, given different standards not only for cellular, but also the camera and wi-fi vary from those here in the US. Even if one were to flash a US carrier radio, the camera and wi-fi issues could still pop up. Moving on from that consideration.
For US unlocked, there should be no standards issue, correct? Assuming hardware is the same for atleast all US carriers, what besides the radios would differ between carriers when not running stock ROMs?
Obviously there would be issues when on stock ROMs due to custom apps, features, etc. that would break not only when running different non-stock FW, but also when running one carrier's stock ROM on another carrier's network. All that is ill-advised and goes back to you only recommending stock FW.
Thanks for discussing this. I do not question your advise at all, I just want to explore the what and why of it all to put it all in one place. Thanks for humoring me and my questions!
Click to expand...
Click to collapse
Hardware wise most are the same. And you are right about me recommending firmware that matches your carrier. That aside, my experience has been like this....
I have been asked a couple times to try to fully convert a phone from one carrier to another. On the 10, we know that unlocked<->verizon works and we thought it would since HTC gave them the same MID (different CIDs though). On the m9, I have attempted to fully convert a verizon m9 to an ATT model. The RUU flashes everything BUT tp and one or two other ones. It boots up fine (att death star and all)... but it will never boot to recovery and never load TWRP when flashed. There's something about the overall partition structure that makes it different.
On the rom/firmware front.... Verizon and HTC do very specific testing for firmware/OS releases. They do this not only to ensure optimal performance for the user, but also to make sure that the phone itself doesn't cause issues on the network itself. As the manager of an engineering team for a huge US based ISP, I can tell you that firmware of devices CAN and DOES impact the network stability from time to time. I'm not talking about capacity issues, I'm talking about your phone making a phone call and causing a network card back at the CO/Tower/ETC reset. It does happen.
Lastly, I measure things by what you gain. What would gain by flashing unlocked or EU firmware images onto a phone on the verizon network? An increase in number version? As much as I see people who change their aboot do so to avoid red text, it always surprised me to see a VZW phone with a third X.X.401.X number on their bootloader indicating non-vzw firmware. There's a new piece of fun around since the m9 and present on the 10. If you manage to get an aboot on your phone doesnt match your firmware and you reboot the phone you will be stuck in bootloader with no access to download/recovery and often OS. The only fix is to manually flash each firmware image / partition file by name manually and it must match the aboot for it to work. So that's another reason to not go and mix and match because to be honest... most people don't make it beyond the panic moment of that. That phone gets returned and added to the reasons verizon makes it more difficult going forward.
\
There's my 2 cents

Favorite xt1765 ROM and why

I am just wondering what you guys(or girls) favourite custom ROMs are for the Perry xt1765 and why?
Or do you prefer stock and why?
I'm currently running Resurrection Remix and I do really like the look and all the customization and the smooth and snappiness of the ROM overall, but I made several mistakes during the install and can't get it unencrypted.
So I was planning on reinstalling RR but the only other ROM I've used is the stock ROM.
So basically, I'm wondering if there's something better for me or more my style.
I just don't have the time or patience to read the info about all the ROMs and install them for a few days to test them out.
Once again, when giving your opinion, please go into detail about WHY you like that ROM so much.
Thanks in advance
:good::fingers-crossed:

AesopRock127 said:
Hi I'm not sure if this should be in the questions and answers section or this section. Since it's a discussion, and this section had the word discussion in it, I am assuming this is the correct section....
Basically, I am just wondering what you guys(or girls) favourite custom ROMs are for the Perry xt1765 and why?
Or do you prefer stock and why?
I'm currently running Resurrection Remix and I do really like the look and all the customization and the smooth and snappiness of the ROM overall, but I made several mistakes during the install and can't get it unencrypted.
So I was planning on reinstalling RR but the only other ROM I've used is the stock ROM.
So basically, I'm wondering if there's something better for me or more my style.
I just don't have the time or patience to read the info about all the ROMs and install them for a few days to test them out.
Once again, when giving your opinion, please go into detail about WHY you like that ROM so much.
Thanks in advance
:good::fingers-crossed:
Click to expand...
Click to collapse
My preference for virtually every Android gizmo that I own/owned (dozens) is stock, xposed framework (if supported), and a few essential modules. Why be that you may ask? First - I only nab devices that have near AOSP stock rom or a well established stand-in. An unlockable bootloader is absolute table stakes; have no interest in fighting with vendor imposed restrictions. Then there's stability and functionality. Typically everything just works with stock. I'm not into perpetual beta testing everyday commodities. Life is too short to be doinking around with ROM idiosyncrasies and developers who are unable (or insufficiently skilled) to adapt generic ROMs for specific hardware. Might sound crass but reflects pragmatic priorities and limited discretionary time. I prefer to use my gizmos, not manage them.
tl;dr: pick your poison wisely.

Davey126 said:
I prefer to use by gizmos, not manage them.
tl;dr: pick your poison wisely.
Click to expand...
Click to collapse
Wise words my friend.

Davey126 said:
My preference for virtually every Android gizmo that I own/owned (dozens) is stock, xposed framework (if supported), and a few essential modules.
Click to expand...
Click to collapse
First off, thanks for your thorough and well thought answer. I actually know this about you from browsing other threads. Secondly, I'm curious what you consider to be essential Xposed modules? I have Xposed installed but find it hard to pick through and find the gems in the largely useless (to me at least) download section. Been experimenting with different custom rooms and while I still really like the RR one, I'm starting to feel like I may be happier in stock as well, maybe just a debloated one. So although I didn't intend this with my OP, I'm interested what you or anyone considers to be essential modules on Xposed or even Magisk. Thanks for your opinion
Sent from my Motorola XT1765 using XDA Labs

AesopRock127 said:
First off, thanks for your thorough and well thought answer. I actually know this about you from browsing other threads. Secondly, I'm curious what you consider to be essential Xposed modules? I have Xposed installed but find it hard to pick through and find the gems in the largely useless (to me at least) download section. Been experimenting with different custom rooms and while I still really like the RR one, I'm starting to feel like I may be happier in stock as well, maybe just a debloated one. So although I didn't intend this with my OP, I'm interested what you or anyone considers to be essential modules on Xposed or even Magisk. Thanks for your opinion
Click to expand...
Click to collapse
I like to keep things simple and functional; reliability is a top priority. I also demand full control over my gizmo's while rarely using those capabilities. Could care less about theming and other eye candy.
My essentials:
- AOSP based ROM
- TWRP
- Root manager (SuperSU or Magisk)
- Kernel manager (typically EX)
- Nova launcher
- Xposed framework w/gravitybox and edge
- Greenify w/xposed (used sparingly)
- SD Maid
- Adguard
Of course I have dozens of high quality apps that are universal along with a handful that are device specific. The only Magisk modules I use are those that are absolutely necessary for device compatibility. I do use other Xposed modules (eg: Wifi password; OwnOrientation) but typically only where needed.

Davey126 said:
I like to keep things simple and functional; reliability is a top priority. I also demand full control over my gizmo's while rarely using those capabilities. Could care less about theming and other eye candy.
My essentials:
- AOSP based ROM
- TWRP
- Root manager (SuperSU or Magisk)
- Kernel manager (typically EX)
- Nova launcher
- Xposed framework w/gravitybox and edge
- Greenify w/xposed (used sparingly)
- SD Maid
- Adguard
Of course I have dozens of high quality apps that are universal along with a handful that are device specific. The only Magisk modules I use are those that are absolutely necessary for device compatibility. I do use other Xposed modules (eg: Wifi password; OwnOrientation) but typically only where needed.
Click to expand...
Click to collapse
Yes I see the benefit of this.
I'm starting to agree more and more.
You get the stabability of the stock rom with the customization of a custom rom with gravitybox.
I personally dislike most pie and edge type apps and my preferred launcher is adw EX but besides that I can really see your point.
Sent from my Motorola XT1765 using XDA Labs

AesopRock127 said:
I am just wondering what you guys(or girls) favourite custom ROMs are for the Perry xt1765 and why?
Or do you prefer stock and why?
I'm currently running Resurrection Remix and I do really like the look and all the customization and the smooth and snappiness of the ROM overall, but I made several mistakes during the install and can't get it unencrypted.
So I was planning on reinstalling RR but the only other ROM I've used is the stock ROM.
So basically, I'm wondering if there's something better for me or more my style.
I just don't have the time or patience to read the info about all the ROMs and install them for a few days to test them out.
Once again, when giving your opinion, please go into detail about WHY you like that ROM so much.
Thanks in advance
:good::fingers-crossed:
Click to expand...
Click to collapse
Honestly, none of the nougat roms are great.
Lineage, Dot, RR all suffer from serious SD failures and crashes because of the USB bug when you plug it into the computer.
All the nougat roms, including stock, have a real serious problem with calls and texts coming through. I've tried ALL the roms and even made the XT1765 stock rom, and my phone just will not ring every time someone calls it. It goes into a weird sleep and just won't shake itself out unless i make a call/text.
Hold out for Oreo.

Articul8Madness said:
Honestly, none of the nougat roms are great.
Lineage, Dot, RR all suffer from serious SD failures and crashes because of the USB bug when you plug it into the computer.
All the nougat roms, including stock, have a real serious problem with calls and texts coming through. I've tried ALL the roms and even made the XT1765 stock rom, and my phone just will not ring every time someone calls it. It goes into a weird sleep and just won't shake itself out unless i make a call/text.
Hold out for Oreo.
Click to expand...
Click to collapse
I have not noticed any of these issues on stock or RR except for out of state texts seem slow.... Take awhile to come in. Besides that though I do have to agree N is nothing special
Sent from my Motorola XT1765 using XDA Labs

Articul8Madness said:
Honestly, none of the nougat roms are great.
Lineage, Dot, RR all suffer from serious SD failures and crashes because of the USB bug when you plug it into the computer.
All the nougat roms, including stock, have a real serious problem with calls and texts coming through. I've tried ALL the roms and even made the XT1765 stock rom, and my phone just will not ring every time someone calls it. It goes into a weird sleep and just won't shake itself out unless i make a call/text.
Hold out for Oreo.
Click to expand...
Click to collapse
Have two E4s in the family associated with Verizon. One totally stock; not rooted/unlocked; routinely takes OTAs. Other is BL unlocked, rooted, running stock 7.1 ROM from late 2017. Neither exhibit the symptoms you describe. Actually, quite the opposite. Rock solid performers.
Why would you think Oreo is going to solve your problems which are likely the result of heavy tinkering and incomplete restoration attempts?

AesopRock127 said:
I have not noticed any of these issues on stock or RR except for out of state texts seem slow.... Take awhile to come in. Besides that though I do have to agree N is nothing special
Sent from my Motorola XT1765 using XDA Labs
Click to expand...
Click to collapse
When you plug the phone into the computer via USB, you have to fight to get it to accept if you're doing transfers. While you can drag and drop files to your device via PC, you cannot delete anything on the phone via PC or transfer anything from device to PC. That is a SERIOUS BUG that creates the hassle of taking the battery out to retrieve the SD card to put it into a SD adapter and into the slot if your pc has it. Not a dealbreaker, but terribly inconvenient on the model since you have to take the battery out every time.
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
Davey126 said:
Have two E4s in the family associated with Verizon. One totally stock; not rooted/unlocked; routinely takes OTAs. Other is BL unlocked, rooted, running stock 7.1 ROM from late 2017. Neither exhibit the symptoms you describe. Actually, quite the opposite. Rock solid performers.
Why would you think Oreo is going to solve your problems which are likely the result of heavy tinkering and incomplete restoration attempts?
Click to expand...
Click to collapse
Have 2 E4s in the family associated with MetroPCS. Now we're over to TMobile, devices are unlocked straight from Metro. Both are rooted/bootloader unlocked. Only one took that March OTA (the significant other's) and it was a ***** undoing the damage on their phone that caused with the root.
Since I unlocked the bootloaders on these variants, stock or custom OS we miss phone calls. It does weird things where text messages will not come in unless you send one out first. It also will not ring once its sleep for so long; I literally have to make a phone call and "activate it" to get it ringing. Many people over the last 2-3 months keep telling me they've called and it DOESN'T RING on their end. I've also called folks and heard no ringing.
You CANNOT compare the Verizon variant to any other since you can't do squat with it but maybe root. Also, verizon always seem to have the better phones that hold up NO MATTER WHAT. Hard price to pay when you can't really do nothing with it.
Metro's variant has been a pain in the ass since day 1. And from what I've seen on here so have the Sprint ones. I don't like stock on this phone at all, even though I made a stock rom which was necessary to unlock it down the row, but this model sucks.
---------- Post added at 03:05 PM ---------- Previous post was at 03:02 PM ----------
Davey126 said:
Why would you think Oreo is going to solve your problems which are likely the result of heavy tinkering and incomplete restoration attempts?
Click to expand...
Click to collapse
Maybe once Squid2 gets the device trees properly some of the isms will go away.
Also, if unlocking the bootloader is "heavy tinkering" then what are we doing on here? I do complete restoration attempts just fine, these and other problems started the minute the bootloader was unlocked and not before. And on the Metro variant, which is a POS, well, guess it was coming. Won't be getting another phone from them, tell you that much.

Articul8Madness said:
When you plug the phone into the computer via USB, you have to fight to get it to accept if you're doing transfers. While you can drag and drop files to your device via PC, you cannot delete anything on the phone via PC or transfer anything from device to PC. That is a SERIOUS BUG that creates the hassle of taking the battery out to retrieve the SD card to put it into a SD adapter and into the slot if your pc has it. Not a dealbreaker, but terribly inconvenient on the model since you have to take the battery out every time.
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
Have 2 E4s in the family associated with MetroPCS. Now we're over to TMobile, devices are unlocked straight from Metro. Both are rooted/bootloader unlocked. Only one took that March OTA (the significant other's) and it was a ***** undoing the damage on their phone that caused with the root.
Since I unlocked the bootloaders on these variants, stock or custom OS we miss phone calls. It does weird things where text messages will not come in unless you send one out first. It also will not ring once its sleep for so long; I literally have to make a phone call and "activate it" to get it ringing. Many people over the last 2-3 months keep telling me they've called and it DOESN'T RING on their end. I've also called folks and heard no ringing. .
Click to expand...
Click to collapse
Not to be contrary but I'm on metropcs and I have literally none of these issues.
Not on RR and not on fully updated stock.
Not sure what happened with yours and maybe I just got lucky but the only thing that I couldn't do on fully up to date stock was install xposed.
I think that was because you need a patched boot IMG to get it running not sure.
Like I said before sometimes out of state texts take a while to come in but I'm talking 5 minutes later and not activated by a phone call like in your case.
My phone connects to my computers just fine with any old cable.
Can fastboot or transfer files to and from SD or internal and delete as well with no issues.
Maybe mines newer and they fixed it somehow because I've only had mine about six months but only started unlocking the bootloader a few weeks ago
Sounds like a serious PITA for you my friend I've been a loyal metropcs customer since they first came to my state and I've only had one problem phone from them so I'm sorry you've had such a crqp experience but believe me they either fixed the problem or like @Davey126 said its more likely something botched.
Do they have twrp flashed on them?
Are they encrypted or not?
Just curious
Ive never had to take my SD card out I can even transfer files in TWRP mount section...

Articul8Madness said:
You CANNOT compare the Verizon variant to any other since you can't do squat with it but maybe root. Also, verizon always seem to have the better phones that hold up NO MATTER WHAT. Hard price to pay when you can't really do nothing with it.
Click to expand...
Click to collapse
Did no such thing. Our E4s are associated with Verizon but not tied to that provider. As noted, one is bootloader unlocked with all of the associated magical powers (ooo!). Second remains locked and unrooted by choice; like 'dem OTAs. One does not have to purchase Verizon's crippled handsets to leverage their service. As for "better phones" (cough) your E4 hardware and mine are virtually identical. No more, no less.
Articul8Madness said:
Also, if unlocking the bootloader is "heavy tinkering" then what are we doing on here? I do complete restoration attempts just fine, these and other problems started the minute the bootloader was unlocked and not before. And on the Metro variant, which is a POS, well, guess it was coming. Won't be getting another phone from them, tell you that much.
Click to expand...
Click to collapse
Have no idea what transpired after unlocking but whatever happened your experiences don't mirror those of others.

AesopRock127 said:
Not to be contrary but I'm on metropcs and I have literally none of these issues.
Not on RR and not on fully updated stock.
Not sure what happened with yours and maybe I just got lucky but the only thing that I couldn't do on fully up to date stock was install xposed.
I think that was because you need a patched boot IMG to get it running not sure.
Like I said before sometimes out of state texts take a while to come in but I'm talking 5 minutes later and not activated by a phone call like in your case.
My phone connects to my computers just fine with any old cable.
Can fastboot or transfer files to and from SD or internal and delete as well with no issues.
Maybe mines newer and they fixed it somehow because I've only had mine about six months but only started unlocking the bootloader a few weeks ago
Sounds like a serious PITA for you my friend I've been a loyal metropcs customer since they first came to my state and I've only had one problem phone from them so I'm sorry you've had such a crqp experience but believe me they either fixed the problem or like @Davey126 said its more likely something botched.
Do they have twrp flashed on them?
Are they encrypted or not?
Just curious
Ive never had to take my SD card out I can even transfer files in TWRP mount section...
Click to expand...
Click to collapse
A lot of Metro users on here reported about the transfer issues using custom roms in the approprpiate threads. So that isn't isolated. Maybe it's the batch of phones perhaps. I know running DotOS or RR specifically, the phone would run, but if I rebooted it would bootloop. Considering I rarely rebooted once on, that was something I noticed after having to pull the SD card out. But no big thing - Lineage was my go to OS anyway, and had no probs with that.
Yes, both phones have twrp flashed on them. No, not encrypted.
These aren't the first Metro phones I've had. Had the LGL70 before and the LGOptimusL9. No probs with those until years after having them. With the E4's, its been struggle since day one (which wasn't a total loss because I wound up writing guides and really studying this variant).
---------- Post added at 05:28 PM ---------- Previous post was at 05:21 PM ----------
Davey126 said:
Did no such thing. Our E4s are associated with Verizon but not tied to that provider. As noted, one is bootloader unlocked with all of the associated magical powers (ooo!). Second remains locked and unrooted by choice; like 'dem OTAs. One does not have to purchase Verizon's crippled handsets to leverage their service. As for "better phones" (cough) your E4 hardware and mine are virtually identical. No more, no less.
Have no idea what transpired after unlocking but whatever happened your experiences don't mirror those of others.
Click to expand...
Click to collapse
In fairness, I did get the phones from an authorized retailer and not corporate themselves. Maybe the phones were duds from the start, but what is so weird is that they came from 2 different metropcs' stores about a month apart from each other.
Can't say Davey. But if you read the Moto forums, the Metro folks got more than their fair share of probs. I've always loved a Moto phone, but the way Lenovo's been acting since acquiring them, they may be intentionally sending out lemons. I make my phone usable, but at the 3 month mark its time for another one and with the E4 being cut from Oreo because of the premature release of the E5, I don't know if I want to stick with Moto.
My Metro service sucked. Switched back to TMobile just from the last week of service being slowed to a crawl and being non-existent, even on my Iphone SE. After calling and complaining about it they said to take my business elsewhere, so I took it to their head company, who TMO says they don't get priority on service as a MVNO.
I was stuck with Verizon for 7 years after they bought PrimeCo. Never liked them - they locked my Moto Razr down so tough it was ridiculous and all I wanted was RINGTONES, custom RINGTONES on the thing. The one and only time I took an unlocked phone to them S4Mini, they said it wouldn't work on their network (which was crap). But their phones do hold up when cotton and corn won't, sadly.

Articul8Madness said:
A lot of Metro users on here reported about the transfer issues using custom roms in the approprpiate threads. So that isn't isolated. Maybe it's the batch of phones perhaps. I know running DotOS or RR specifically, the phone would run, but if I rebooted it would bootloop. Considering I rarely rebooted once on, that was something I noticed after having to pull the SD card out. But no big thing - Lineage was my go to OS anyway, and had no probs with that.
Yes, both phones have twrp flashed on them. No, not encrypted.
These aren't the first Metro phones I've had. Had the LGL70 before and the LGOptimusL9. No probs with those until years after having them. With the E4's, its been struggle since day one (which wasn't a total loss because I wound up writing guides and really studying this variant).
---------- Post added at 05:28 PM ---------- Previous post was at 05:21 PM ----------
In fairness, I did get the phones from an authorized retailer and not corporate themselves. Maybe the phones were duds from the start, but what is so weird is that they came from 2 different metropcs' stores about a month apart from each other.
Can't say Davey. But if you read the Moto forums, the Metro folks got more than their fair share of probs. I've always loved a Moto phone, but the way Lenovo's been acting since acquiring them, they may be intentionally sending out lemons. I make my phone usable, but at the 3 month mark its time for another one and with the E4 being cut from Oreo because of the premature release of the E5, I don't know if I want to stick with Moto.
My Metro service sucked. Switched back to TMobile just from the last week of service being slowed to a crawl and being non-existent, even on my Iphone SE. After calling and complaining about it they said to take my business elsewhere, so I took it to their head company, who TMO says they don't get priority on service as a MVNO.
I was stuck with Verizon for 7 years after they bought PrimeCo. Never liked them - they locked my Moto Razr down so tough it was ridiculous and all I wanted was RINGTONES, custom RINGTONES on the thing. The one and only time I took an unlocked phone to them S4Mini, they said it wouldn't work on their network (which was crap). But their phones do hold up when cotton and corn won't, sadly.
Click to expand...
Click to collapse
I got to agree with you there....
Difficult phones provide the opportunity to learn which is always a good thing, albiet frustrating at times.
MetroPCS just announced a rebranding to Metro by TMobile.
I was under the impression they used the same exact network since when TMobile bought Metro they gave me a free phone because my old one would no longer get a signal when they moved to TMobile network....
At least that's how they described it to me at the store.
But you notice a difference on TMobile over Metro?
I personally have no problems here in NH, works all over my state and the LTE literally screams, i sometimes even get a better speed test then my Xfinity.
The only issue I've had so far on my current setup is I no longer am notified of voicemails and visual voicemail won't load....
Not sure why that is but I can still check voicemails manually...
Is this an issue anyone has run into?
If so, anyone have a solution?
Was considering stopping at Metro and seeing if they could help, maybe it needs another Metro app or something but they will just tell me not to tinker with my phone and refuse to help me.
They are pretty ignorant of anything not involving selling a phone or normal everyday setup.
For a corporate store, they sure lack in the support department....

Articul8Madness said:
In fairness, I did get the phones from an authorized retailer and not corporate themselves. Maybe the phones were duds from the start, but what is so weird is that they came from 2 different metropcs' stores about a month apart from each other.
Click to expand...
Click to collapse
I never purchase carrier aligned/branded phones. I seek out the multi-service variant (eg: XT1768), wait for a sale and then add the (unlocked/rooted) device to whatever service I happen to be using at the time. I have neither the time nor patience to dink around with balky firmware. I also expect to be the master of my devices with no restrictions beyond those imposed by the HW itself. That requirement largely determines what gizmos make the short list.

AesopRock127 said:
I got to agree with you there....
Difficult phones provide the opportunity to learn which is always a good thing, albiet frustrating at times.
MetroPCS just announced a rebranding to Metro by TMobile.
I was under the impression they used the same exact network since when TMobile bought Metro they gave me a free phone because my old one would no longer get a signal when they moved to TMobile network....
At least that's how they described it to me at the store.
But you notice a difference on TMobile over Metro?
I personally have no problems here in NH, works all over my state and the LTE literally screams, i sometimes even get a better speed test then my Xfinity.
The only issue I've had so far on my current setup is I no longer am notified of voicemails and visual voicemail won't load....
Not sure why that is but I can still check voicemails manually...
Is this an issue anyone has run into?
If so, anyone have a solution?
Was considering stopping at Metro and seeing if they could help, maybe it needs another Metro app or something but they will just tell me not to tinker with my phone and refuse to help me.
They are pretty ignorant of anything not involving selling a phone or normal everyday setup.
For a corporate store, they sure lack in the support department....
Click to expand...
Click to collapse
The "rebranding" is because Tmobile just bought Sprint, and so from what Tmobile said, they need to "reprioritize" their service from their top tier GSM/CDMA down to their MVNOs. I'm gonna guess this is to get ready for the conversion to 5G, since TMO confirmed to me their users get first dibs on service, then Sprint, then the MVNO's, since while they own Metro and Simple Mobile, they also "lease" airtime from them for service.
Don't get me started at how messy this is, considering Tmobile's computer systems are always down, and something as simple as getting a text to remind me to pay the bill or confirmation I've paid NEVER HAPPENS NOW.
There is a difference over service between Metro and TMO - depending on where you're at in the country you can definitely tell. Never got full LTE on Metro instead H+ barely, but never had problems with TMO in that department. Calls on that last week no matter what phone with Metro...service just would cease to exist.
I always got VM's on Metro but it wouldn't ring and go straight to VM but Visual Voicemail NEVER EVER WORKED, especially since I felt punished because I wouldn't update my data to unlimited.
And yes, their people are ignorant of everything, but then they can be considering they franchise. Their tech support, albeit good English speakers, sucks in comparison to TMO.
I had a situation with TMO where I called and paid the bill over the phone but their new system lost the payment even though it showed I paid, it didn't credit to the account. TMO automatically credited it for me and escalated to see what's wrong with the line. Metro would have NEVER done that. EVER. They wouldn't even credit me a SIM card when one I bought didn't work - made me pay 20 bucks for a replacement because their system couldn't process it. No thanks.
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
Davey126 said:
I never purchase carrier aligned/branded phones. I seek out the multi-service variant (eg: XT1768), wait for a sale and then add the (unlocked/rooted) device to whatever service I happen to be using at the time. I have neither the time nor patience to dink around with balky firmware. I also expect to be the master of my devices with no restrictions beyond those imposed by the HW itself. That requirement largely determines what gizmos make the short list.
Click to expand...
Click to collapse
I didn't have that option when I got service. I hadn't had service for 8 years. Normally I get factory unlocked used phones from ebay as my personal play tinkering devices, but an actual phone to talk with, it was a budget buy and for 50 bucks and being Moto didn't feel it was going to be a clunker. Normally I have to scout and negotiate for the international phones I like, but as Samsung is proving, just because its not carrier aligned doesn't mean the manufacturer won't lock the phone down.

Articul8Madness said:
Normally I have to scout and negotiate for the international phones I like, but as Samsung is proving, just because its not carrier aligned doesn't mean the manufacturer won't lock the phone down.
Click to expand...
Click to collapse
Never said that. A bit of upfront research makes all the difference. Been doing this for nearly 15 years; haven't bricked a handset yet and never experienced the boatload of woes others report. My phones just work.

Davey126 said:
Never said that. A bit of upfront research makes all the difference. Been doing this for nearly 15 years; haven't bricked a handset yet and never experienced the boatload of woes others report. My phones just work.
Click to expand...
Click to collapse
Never said you said that. I was just pointing out the hard fact about Samsung locking down phones post S7. I been tinkering with phones since my Verizon branded Razr3. Ain't bricked a phone yet that couldn't be unbricked, lol. Had some I loved, had some I hated.

Temp root achieved on first Snapdragon 835

If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device. ?

Inerent said:
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device.
Click to expand...
Click to collapse
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
trabadura said:
j4nn said:
trabadura said:
Hi j4nn, i see your post in xda for temp root Sony XZ1c with Snapdragon 835 and I figured you could help us for temp root Verizon Google Pixel 2 Xl for Unlock Bootloader?
Click to expand...
Click to collapse
Hi, I am not sure about that - I do not have that phone and cannot get/borrow it for testing either.
Do you know if it is possible to downgrade it's firmware?
Can you point me to earliest fw for download that it can be downgraded to?
What exactly the problem is - bootloader is not possible to unlock because Verizon (is it a mobile network operator?) disabled bootloader unlock possibility while on general not Verizon variant google allows it?
Is it also sim locked to Verizon operator only?
And how do you know that getting temp root would help you?
Click to expand...
Click to collapse
Hi, аs far as I know, it can not downgrade firmware with locked bootloader. With unlocked bootloader no problem.
The problem is in mobile operator. They lock option "OEM Unlock" (stay grayed out) in developer option. In general not Verizon variant no problem option is active and no problem to unlock bootloader. No sim locked only bootloader. Тhere is a lot of writing about the topic I can give a few links in the forum.
Links:
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
Click to expand...
Click to collapse
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).

j4nn said:
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
Click to expand...
Click to collapse
You are completely right. And that is the difference between Android and iPhone communities. Every Android user prefer to stay aside of this problem, naively thinking that they would not be affected. In Oreo Google has already put all the Root CAs into the System storage. So Nobody knows what kind of data the phone uploads every day to 3rd party servers. Verizon is just an example there are many companies who do the same. iPhone community is great because everybody know that some day under certain circumstances they can lost their JB. I hope one day some mid-range iOS developer will buy Android phone and start developing a great root tools. Sure it will be quite easy because all the source code is available.
I appreciate your work. Thank you and good luck.
First they came for the socialists, and I did not speak out—
Because I was not a socialist.
Then they came for the trade unionists, and I did not speak out—
Because I was not a trade unionist.
Then they came for the Jews, and I did not speak out—
Because I was not a Jew.
Then they came for me—and there was no one left to speak for me.

Why is the Verizon S7 Edge root so crappy (serious, not being mean)?

Hey all,
First off let me just say great work to everyone involved with rooting this now "ancient" phone, especially klabit87 and jrkruse. Additionally, I do not mean to be ungrateful with this post, nor suggest that rooting a phone is easy, especially one with a locked bootloader, or that the users here are entitled to such a feature.
With that out of the way....
I haven't looked into rooting this phone EVER until now. Haven't even peaked at XDA or Googled anything, I didn't even know it was possible until yesterday. I've re-ROMed all my previous phones but was actually satisfied with the stock S7 experience other than a Launcher swap and dealing with the always laggy Google maps. Well recently I got a new car and got fed up with the obnoxious list/action limit that Android Auto has as the voice search can be quite unreliable, the letter search is somewhat bugged on the media player I use, and in the end all it does is encourage people to just use their phone to change songs/settings and send messages, thereby completely failing at its goal of being safer. So, I really wanted to get Xposed installed to use the module that makes AA a lot more usable; however, now that I've looked back into the scene a bit, I'm not so sure I want to move forward.
To preface my question: Every Android device I've had before was essentially either rootable or not and ultimately banked on a security exploit that was eventually found. There were never really any concerns about major issues unless you were changing ROMs, kernels, or testing major CPU behavior changes. Just rooting itself was almost always issue free other than a small bug or two or the need to reapply at reboot.
From what I gather, it seems to me that they only way currently to gain root privileges on this device is to install this ENG kernel that's talked about in a lot of more recent posts. Is it truly the case that someone had to write a kernel from scratch that was pre-rooted and as of right now there is no way to root the device as it is stock? Is it that the only known exploit is how to flash another kernel, and the stock kernel is still locked up tight? It sucks that the current root seems so unstable/slow. I know there are a plethora of fixes but there really is no one major fix (other than potentially reflashing the stock bootloader that for some reason seems to work), and its a matter of installing a boat load of CPU and resource management tweaks and even then the performance/battery life isn't quite stock. Additionally it seems like its definitely a YMMV kind of thing as some users seem to still have significant battery drain or slowness/heat even after trying tons of fixes.
Since I am just now getting familiar with the "homebrew" the phone I've had for 3+ years and know nothing about the work that's been done, I genuinely just want to know the technical implications that got in the way of a cleaner root and why the current root method is stuck as sort of a work-around so to speak. The people that manage these breakthroughs rarely post about the process they went through unless its pertinent to a guide on how to root, so I was just curious why the root for this device is in the current state it is.
I would really like to root my Edge so I can be done with the AA nonsense but after just getting a new battery put in I really don't want to go through ****ty battery life again haha.
Thanks to all who weigh in.

Verizon requires most if not all manufacturers to lock the bootloaders. This is also Samsung choice as well. The T-mobile S7/edge and newer have locked bootloaders as well. Difference is T-mobile leaves it up to the OEMs whether they want to lock it or not. With some U.S. businesses and enterprises using Samsung Galaxy devices. They focus on being "enterprise ready" which makes sense from a business standpoint.
Believe it or not, Samsung used to be developer friendly when the S II came out. They even gave away Galaxy S2 devices to some XDA devs.
So, if you want a Samsung device with an unlock able bootloader. Get one that has an Exynos SoC or the Chinese Snapdragon variant.