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

[Q] a501 sim unlock without code possible?

It's a Rogers a 501 running randomblame's jellytime build 3(awesome ROM!) with v8 unlocked bootloader and 1.7.3 thor CWM. I was hoping to test the data on this ROM. I've seen I can buy the code and Rogers wants $50 but I would prefer to find a free way of doing it. I unlocked my galaxy s3 by using the *#197328640# into phone. Anyone figure out a way to unlock on this acer a501 tab?

matt1515 said:
It's a Rogers a 501 running randomblame's jellytime build 3(awesome ROM!) with v8 unlocked bootloader and 1.7.3 thor CWM. I was hoping to test the data on this ROM. I've seen I can buy the code and Rogers wants $50 but I would prefer to find a free way of doing it. I unlocked my galaxy s3 by using the *#197328640# into phone. Anyone figure out a way to unlock on this acer a501 tab?
Click to expand...
Click to collapse
In the past, there has been some success of getting the unlock code, by repeatedly e-mailing Rogers, ATT, or whichever provider you purchased the tablet from.
Typically, those that had success, simply explained they purchased the tablet and currently do not live in the area where the network coverage is. Also, in the beginning, some overseas folks bought the tablet not knowing it was sim locked to a specific network. Of course it took several e-mails, and persistance.
Unfortunately, there is no known way to generate the "unlock code", at least here at XDA. Also, some of the "unlock sites" who claim they can do it, generally can't. Although there was 1 case where the user sent his tablet to them, then got it back a week or so later.
The sim unlock codes are "device specific", which means you can't use another's unlock code.
So your best bet, especially if the tablet is over a year or so old, is to argue your point with Rogers, in a polite way of course. Perhaps they might eventually give the unlock code for free. Always remember to be polite.
Cheers!
MD

Thanks for the info! I will try emailing them and see if I can put on some charm. Too bad tho if you could find the file or get into the device like you can with the Samsung's it would make life so much easier! Also anyone who reads this randomblame's jellytime build 3 is an awesome rom! I have been using it daily and it is incredibly stable working great! Anyone with an a501 should try this out!
Moscow Desire said:
In the past, there has been some success of getting the unlock code, by repeatedly e-mailing Rogers, ATT, or whichever provider you purchased the tablet from.
Typically, those that had success, simply explained they purchased the tablet and currently do not live in the area where the network coverage is. Also, in the beginning, some overseas folks bought the tablet not knowing it was sim locked to a specific network. Of course it took several e-mails, and persistance.
Unfortunately, there is no known way to generate the "unlock code", at least here at XDA. Also, some of the "unlock sites" who claim they can do it, generally can't. Although there was 1 case where the user sent his tablet to them, then got it back a week or so later.
The sim unlock codes are "device specific", which means you can't use another's unlock code.
So your best bet, especially if the tablet is over a year or so old, is to argue your point with Rogers, in a polite way of course. Perhaps they might eventually give the unlock code for free. Always remember to be polite.
Cheers!
MD
Click to expand...
Click to collapse

Well I have found a site cellunlocker.net who was able to gererate the unlock code. Only problem code not accepted in cm 10.1 so I am going to try and flash the stock ICS a501 and hope it will work on that.
EDIT- just tried this on Acer_AV041_A501_0.001.00_WW_GEN1 (Stock ICS pre-rooted)
With baseband version: Cust:R3C01 Config:R4B01 Conf:R3C01 Protocol:R3B01 App:R3C01
My other option is to downgrade further back to HC bootloader and HC rom. The other issue is I can't find any roms that end in PA_ROG(Rogers based ROMS). My stock 3.2 was ACER_A501_4.042.01_PA_ROG didn't back up but everything I can find to flash ends in COM1. Will I still be able to unlock without actually being on a rogers based ROM? I know I'm going to find out soon but any help is appreciated. If anyone has this rom ACER_A501_4.042.01_PA_ROG you'd make my life much simpler!! Would the skrilax v8 unlocked bootloader have any effect on this or not? Just wondering if going back to honeycomb is really even worth trying especially if I don't have a Rogers based rom to try.

matt1515 said:
Well I have found a site cellunlocker.net who was able to gererate the unlock code. Only problem code not accepted in cm 10.1 so I am going to try and flash the stock ICS a501 and hope it will work on that.
EDIT- just tried this on Acer_AV041_A501_0.001.00_WW_GEN1 (Stock ICS pre-rooted)
With baseband version: Cust:R3C01 Config:R4B01 Conf:R3C01 Protocol:R3B01 App:R3C01
My other option is to downgrade further back to HC bootloader and HC rom. The other issue is I can't find any roms that end in PA_ROG(Rogers based ROMS). My stock 3.2 was ACER_A501_4.042.01_PA_ROG didn't back up but everything I can find to flash ends in COM1. Will I still be able to unlock without actually being on a rogers based ROM? I know I'm going to find out soon but any help is appreciated. If anyone has this rom ACER_A501_4.042.01_PA_ROG you'd make my life much simpler!! Would the skrilax v8 unlocked bootloader have any effect on this or not? Just wondering if going back to honeycomb is really even worth trying especially if I don't have a Rogers based rom to try.
Click to expand...
Click to collapse
Mate, save yourself some heartache. The AT&T and Rogers tablets came with configurations that are different than the unlocked 501's. The code, as I mentioned before, is based on the IMEI number ( International Mobile Station Equipment Identity) which is independent of the Operating System version.
As with the Bootloader if you were to roll back to an HC Rom, your V8 bootloader would be replaced by a new stock bootloader.
As I said, your best bet would be communication with Rogers, or just save some heartache and pay the $50.
MD

Moscow Desire said:
Mate, save yourself some heartache. The AT&T and Rogers tablets came with configurations that are different than tjusthe unlocked 501's. The code, as I mentioned before, is because on the IMEI number ( International Mobile Station Equipment Identity) which is independent of the Operating System version.
As with the Bootloader if you were to roll back to an HC Rom, your V8 bootloader would be replaced by a new stock bootloader.
As I said, your best bet would be communication with Rogers, or just save some heartache and pay the $50.
MD
Click to expand...
Click to collapse
Thank you. So basically it wouldn't matter what rom or bootloader(locked or unlocked) I was on the code would work if I get the right code? I just wouldn't of wanted to pay the $50 and have it not work because of bootloader or rom. I didn't think the ROM you were on would be the issue but I didn't know if the v8 unlocked bootloader could be an issue?

matt1515 said:
Thank you. So basically it wouldn't matter what rom or bootloader(locked or unlocked) I was on the code would work if I get the right code? I just wouldn't of wanted to pay the $50 and have it not work because of bootloader or rom. I didn't think the ROM you were on would be the issue but I didn't know if the v8 unlocked bootloader could be an issue?
Click to expand...
Click to collapse
No problem Mate. The sim unlocking debate was looked into well over a year ago or longer. Acer programmed a module that runs independent of the android operating system. A lot of guys bought these tabs while visiting the States, because of it's discounted price at the stores. Just didn't know you had to use an AT&T sim card, which of course you can't get in Europe. The stores of course didn't tell them this when they bought them.
As with the bootloader, it has nothing to do with it. The bootloaders are the same between roms. Only big differences are with the major versions (HC, ICS), so example an AT&T rom uses the same bootloader as the non AT&T rom, same with Rogers. Although they may issues updates with different bootloader.blob's to patch security holes (root vulnerabilities). But generally most HC roms will run with any HC bootloader. Same with ICS. The only exception was the 3.2.1 HC that was never fully published for the 501. It was a bit strange when I did the custom rom for it. Had to install it 2 or 3 times to make it stick But was a smooth running rom.
Wish you luck with getting Rogers to unlock it. Still, I would go with persistent e-mailing higher up their customer service chain first, before shelling out the $50. Especially if you've had their service for over a year.
MD

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?

Will flashing LineageOS break my Passport 2.0 Warranty?

I know that a while back this was true. But today I saw a few answers on here saying that ZTE was reviewing their terms related to the warranty, something about voiding the software warranty but not the hardware one.
Anyone knows where we stand regarding to that? On the same note, what about just rooting the phone without unlocking the bootloader?

The official answer from ZTE is that unlocking the bootloader invalidates the entire warranty. Only the US/NA model had the ability to unlock the bootloader, and it was only available on B20 when filling out the Google Docs request form.
Everything else is just speculation. Apparently, people on the Nougat beta seemed to say that the update would have the ability built into the base software load, but it appears to be not true for the official release. Other people (myself included) seemed to think that ZTE was just waiting for the Nougat release to put out the new unlock method, but that appears to not be the case. Everything thinks they should just invalidate the SW part and now the HW part, because that is what makes sense, but that's not the current situation.
I haven't seen any reports of people that unofficially unlocked and then sent their phones back to see if it got covered under warranty (as in, did they check the bootloader status).
Hopefully ZTE does something about this soon.

TeutonJon78 said:
The official answer from ZTE is that unlocking the bootloader invalidates the entire warranty. Only the US/NA model had the ability to unlock the bootloader, and it was only available on B20 when filling out the Google Docs request form.
Everything else is just speculation. Apparently, people on the Nougat beta seemed to say that the update would have the ability built into the base software load, but it appears to be not true for the official release. Other people (myself included) seemed to think that ZTE was just waiting for the Nougat release to put out the new unlock method, but that appears to not be the case. Everything thinks they should just invalidate the SW part and now the HW part, because that is what makes sense, but that's not the current situation.
I haven't seen any reports of people that unofficially unlocked and then sent their phones back to see if it got covered under warranty (as in, did they check the bootloader status).
Hopefully ZTE does something about this soon.
Click to expand...
Click to collapse
I know of at least one (but probably more) who borked their modem using signed twrp efs backup and sent it in for replacement.
Honestly I do not think warranty should cover user error/abuse but I suppose I would do it as well if it happened to me.
Weather or not they will honor warranty would depend on the issue and if it is obviously unlocked (custom rom/xposed/root clearly visible). If you relock/stock before sending it in they could not tell.

T-Mobile OS help

Forgive me if there is already an answer to this. I am very new to Android. By new I mean 2 weeks. I have been on Apple for many years now. Jailbreak and customizing is kind of a thing of the past. But to my question...
T+Mobile software is way behind and feels somewhat restricted. Is there a simple way of going to the full version of the latest OnePlus OS?
Thanks in advance for any help and insite.
Chris

wheeler77 said:
Forgive me if there is already an answer to this. I am very new to Android. By new I mean 2 weeks. I have been on Apple for many years now. Jailbreak and customizing is kind of a thing of the past. But to my question...
T+Mobile software is way behind and feels somewhat restricted. Is there a simple way of going to the full version of the latest OnePlus OS?
Thanks in advance for any help and insite.
Chris
Click to expand...
Click to collapse
By far, the best link to get you from T-Mobile software to the International ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-flashing-t-mobile-oneplus-6t-to-t3865966
I've got the T-Mo version and (once I got my phone and bootloader unlocked) was able to convert to the International ROM in less than 10 minutes.
NOTE: You won't be able to get OTA updates (as of yet) but the process of flashing the new updates is super easy.

I followed the how to linked here, updated to the .11 version manually using local update.
On the international Beta 2 now, and it works flawlessly.
brisseau said:
By far, the best link to get you from T-Mobile software to the International ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-flashing-t-mobile-oneplus-6t-to-t3865966
I've got the T-Mo version and (once I got my phone and bootloader unlocked) was able to convert to the International ROM in less than 10 minutes.
NOTE: You won't be able to get OTA updates (as of yet) but the process of flashing the new updates is super easy.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6013 using Tapatalk

brisseau said:
By far, the best link to get you from T-Mobile software to the International ROM:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-flashing-t-mobile-oneplus-6t-to-t3865966
I've got the T-Mo version and (once I got my phone and bootloader unlocked) was able to convert to the International ROM in less than 10 minutes.
NOTE: You won't be able to get OTA updates (as of yet) but the process of flashing the new updates is super easy.
Click to expand...
Click to collapse
Thank you for the info. I will give it a shot in a few.

wheeler77 said:
Forgive me if there is already an answer to this. I am very new to Android. By new I mean 2 weeks. I have been on Apple for many years now. Jailbreak and customizing is kind of a thing of the past. But to my question...
T+Mobile software is way behind and feels somewhat restricted. Is there a simple way of going to the full version of the latest OnePlus OS?
Click to expand...
Click to collapse
If you've been on Apple devices for the past few years, isn't it a bit quick to jump to the conclusion that the T-Mobile branded version of OxygenOS is "way behind" and "feels restricted?"
The only "restrictions" on the T-Mobile version of the phone are the T-Mobile branded boot animation and the inclusion of the T-Mobile app and SIM Unlock app, both of which can be disabled (but not removed). It also doesn't support dual-SIM even though the hardware is there. Aside that there are no other differences.
The system updates are pushed much more slowly on the T-Mobile version. For example we just got the 9.0.2 update while OnePlus has recently released 9.0.11. So yes, the updates are "way behind" if you consider a 2-3 month delay to be a concern. There aren't any significant restrictions. The same restrictions apply to the non-Tmo variant, and in either case you can easily bypass them by rooting.
Now if you want the dual SIM capability, unbranded OS, and more recent system updates, then go ahead and convert. That's exactly why I'm doing it.
As for the OTA updates, I'm reading mixed reviews. Some claim they have successfully received OTA updates after converting. Its not clear if they were real OTA updates that were downloaded and installed automatically or if those users had to manually download and install (in which case it isn't an OTA update, some people just don't understand terminology) It is confirmed that after converting, it is most certainly possible to download the latest software update from OnePlus and use the local upgrade option (no need to manually flash via adb) which is fine by me.

bassic said:
If you've been on Apple devices for the past few years, isn't it a bit quick to jump to the conclusion that the T-Mobile branded version of OxygenOS is "way behind" and "feels restricted?"
The only "restrictions" on the T-Mobile version of the phone are the T-Mobile branded boot animation and the inclusion of the T-Mobile app and SIM Unlock app, both of which can be disabled (but not removed). It also doesn't support dual-SIM even though the hardware is there. Aside that there are no other differences.
The system updates are pushed much more slowly on the T-Mobile version. For example we just got the 9.0.2 update while OnePlus has recently released 9.0.11. So yes, the updates are "way behind" if you consider a 2-3 month delay to be a concern. There aren't any significant restrictions. The same restrictions apply to the non-Tmo variant, and in either case you can easily bypass them by rooting.
Now if you want the dual SIM capability, unbranded OS, and more recent system updates, then go ahead and convert. That's exactly why I'm doing it.
As for the OTA updates, I'm reading mixed reviews. Some claim they have successfully received OTA updates after converting. Its not clear if they were real OTA updates that were downloaded and installed automatically or if those users had to manually download and install (in which case it isn't an OTA update, some people just don't understand terminology) It is confirmed that after converting, it is most certainly possible to download the latest software update from OnePlus and use the local upgrade option (no need to manually flash via adb) which is fine by me.
Click to expand...
Click to collapse
Well you did leave a handful of features the TMO firmware does away with.
But yes, it's easy to "uncarrier" this phone, as i was given my unlock before i paid it off and before the 40 days, submitted to 1+, and in due time and no time fast forward to beta 2