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

Update issues?

strangest thing, i confirm the update and it closes and thats it. It doesnt show a download in the status bar or anything. any ideas?

Mine still says it is already upto date even though I know the 2.3.3 update is out for almost everyone else?!?

FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.

Mozza2k11 said:
FK1983 do you have an o2 branded phone? (with o2 crap installed on/o2 boot up screen?) If so then you are probably waiting for o2 to ok the actual update as well as installing all their extra crap onto 2.3.3 before they let you update
Same probably for magicriggs and anyone else that has not recieved their updates yet. The update you are seeing will be the generic 2.3.3 update you have to wait for verizon to ok the update first then customise it with all the crap/restrictions they want on it.
Click to expand...
Click to collapse
It's on Virgin Mobile, must be why?

FK1983 said:
It's on Virgin Mobile, must be why?
Click to expand...
Click to collapse
It doesn't matter which network the phone is on. If you got it direct from virgin or it has the virgin boot up screen then its virgin "branded". Until virgin or any other network decides to ok the update (and make any modifications they want) unfortunately you will be waiting. Unless you unlock your boot then you can flash the generic 2.3.3 that people with unbranded phones got.
P.s i said o2 since the o2 logo is under your name

Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.

Flava0ne said:
Would that be the same case with me? I originally got my XP from my carrier but I had already network unlocked it with a code that I purchased from Theunlock.ca and de-branded it with a generic R800i UK firmware where mines was originally a R800a.
Click to expand...
Click to collapse
No this only applies to people with a branded phone and a locked bootloader. If you unlock your boot which you have done you can do as you did and flash the generic fw (without extra branded crap on just standard bloat) From now on you will just update using the fw posted here instead of waiting for rogers.

Cool, thanks for clearing that up a bit!
But I didn't unlock my bootloader, I can't because it came from my carrier. What I unlocked was the network and now I can use another SIM card from a different carrier on it if I wanted to. But I guess it's still the same since I was able to flash it with a generic fw already.

I had no issues with the updating itself.
But I noticed that the standard music player sometimes doesn't play sound at all. I first have to kill it with a program like 'Advanced Task Killer' and then it works again. Anyone else has this problem?

My Unlocked XP can download the update but fails on the install, its attempts to install, resets, unpacked update, then attempts to update (icon on screen goes from two dots and openbox icon, to three dots and phone with arrow above) then screen goes blank, phone boots as normal (takes about 2-3mins) then warns that update was unsuccessful after pincode entry.
Thought it might due to lack of internal space, so cleared 80 megs on application space and still no luck.
Sent from my R800i using XDA App

Bricked after OTA update
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.

I just checked for the update manually on my PLAY earlier today and it was able to find the update. But I'm not going to install it until you can root v2.3.3 on a locked bootloader.

ritap said:
My husband's Xperia play got bricked today after an OTA update. It had no customized software, just an unlocked bootloader.
Looks like this issue it's just affecting those ones with an unlocked one.
Click to expand...
Click to collapse
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore. You will have to flash the lastest fw onto the phone. See here to 2.3.3 firmware http://forum.xda-developers.com/showthread.php?t=1097591 also if you flash the first one you can then flash the rooted 2.3.3 http://forum.xda-developers.com/showthread.php?t=1098736 Same goes for Da22a since your XP is unlocked

So still no way to root 2.3.3 on a locked bootloader yet, only with an unlocked bootloader at the moment? Because it's not possible for my to unlock my bootloader on my PLAY because it was originally from my carrier.

Mozza2k11 said:
If you unlock your bootloader you cannot use SEUS or OTA to update your phone anymore.(snip)
Click to expand...
Click to collapse
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .

I don't think SE speculated in making money here. It's a more like a 'here you go' now you have control over your phone to do almost what you like. The main target here I think is devs and flashaholics and such. There's always a risk involved with unlocking your bl and changing the S-ON to S-Off and such things. Ofcause you loose your warranty otherwise every john/jane does would come back and reclaim a new device when they bricked there phone. This comes from a demand within the android community that this is an option.
Further more I don't think SE knew about this. The .img to flash is not comming from We but from this community so they can't be held responsible for putting out an OTA that bricks your phone cause of what people might flash onto there phones. I hope that they will make some kind of check in the software updater similar to SEUS in the future or the ones who make flasheble .imgs will be able to disable OTA in the .imgs to come or upload a new one for people to use.
Regards Dousan...

ritap said:
I see you're right and i wish i had my husband have a look here before even thinking about it.
The problem is: while SEUS prevents you from unintentionally doing that, which i regard as fair, OTA just bricks your phone without further notice.
We've taken it to SE for repair, which they should do for an amount of euros they still haven't notified us (you see, it's out of warranty). Easy money, then: tell people how to unlock their phones and then spread some code which bricks unlocked phones .
Click to expand...
Click to collapse
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Therefore, you should only unlock the boot loader of your phone if you are an advanced user with good knowledge of the technology and risks involved. We strongly recommend that standard users NOT unlock the boot loader, as it is not needed
Click to expand...
Click to collapse
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Note: We have seen in some forums that customers unlocking the boot loader on their phones have experienced problems when they accept a FOTA (Firmware upgrade Over The Air) update. The issue has been reproduced and we are working on a solution. For customers that have unlocked the boot loader please do not accept the Firmware upgrade OTA.
Click to expand...
Click to collapse

Rogers official one comes July 1st. (Canada Day)

Mozza2k11 said:
Im not sure SE will repair your phone. I have read other people on here have sent it in for repair and got it back the same. Today a fix for bricked phones has come out http://forum.xda-developers.com/showthread.php?t=1126354. I would suggest getting your phone back from SE and fixing it yourself. Since the above thread's fix is free (you could always donate to Bin4ry & Blagus, dont know who else helped?)
I also agree with Dousans comments. Below a quote from http://unlockbootloader.sonyericsson.com/
Also not sure how long this has been posted on the site but se knows now and it working on a fix to stop it.
Click to expand...
Click to collapse
You and Dousan may be right but indeed after unlocking the BL we didn't flash it; moreover, after that the phone has been working perfectly for more than a month, since the ota update of course: so it's their software which has bricked the phone, not us.
Moreover, it's true that we lost our warranty, and it's fair that those Johns/Janes won't get a new phone for free, but this doesn't allow then to spread around dangerous software and allowing free repair only to "warranty" customers.
I've already had a look at the fix described in this forum but it didn't fit, Blagus told me there was no solution, the payservers were down so i took the Play to SE...

Anyone know how to get flashtool to recognize the play? The only options are arc x10 x8 etc.
Same as this guy:
how did you guys even get the flashtool to work with the play? ive got the latest version and i keep getting an error saying it cant identify my device and the only options are for x10, x10 mini, x10 mini pro, x8 and arc, just curious
Click to expand...
Click to collapse

Open letter to our XT925 developers / users

My phone, the Motorola Razr HD LTE is out already since November 2012, with not as much development options as other phones.
Compare to SG3 or the Nexus 4 (newly released), it leave us with very little options when it comes to custom ROMS or functional improvements.
Some of the uncertainty is coming from the lack of communication, between the developers and the community of users, on ongoing technical issues with no solution insight (example: the Rogers issue versions 492002 vs. 49003)
The best available custom ROM is currently uncompleted, and again no communication or reassurance on the work progression.
The truth to matter is that we are lagging behind other phones when it comes to development & improvements.

Figure out a way to unlock the bootloader and you will probably see more development on this phone.
You are not your iPhone 5
#tylerdurden

I agree. I holding back doing anything because of losing the warranty.
I have to say though my XT925 is one of the first Android phones that came to me stock without the bloat I've found on Sony, LG and Samsung devices. I'm still very happy with my stock Razr HD.

SFG said:
Figure out a way to unlock the bootloader and you will probably see more development on this phone.
You are not your iPhone 5
#tylerdurden
Click to expand...
Click to collapse
There already is a bootloader unlock. You can use the motorola bootloader unlock tool. I don't have a developer edition and it worked perfect for me. Other users in the forum also have their bootloaders unlocked.

itzik_man said:
My phone, the Motorola Razr HD LTE is out already since November 2012, with not as much development options as other phones.
Compare to SG3 or the Nexus 4 (newly released), it leave us with very little options when it comes to custom ROMS or functional improvements.
Some of the uncertainty is coming from the lack of communication, between the developers and the community of users, on ongoing technical issues with no solution insight (example: the Rogers issue versions 492002 vs. 49003)
The best available custom ROM is currently uncompleted, and again no communication or reassurance on the work progression.
The truth to matter is that we are lagging behind other phones when it comes to development & improvements.
Click to expand...
Click to collapse
I understand how frustrated you are itzak_man because of the lack of official Rogers firmware and that you almost felt lied to by the whole XDA community over the Rogers firmware scandal. Please remember, this is a risk that you take by modifying your phone outside of the manufacturers intended usage. This its the reason why this its the first phone that I haven't modified.
That being said, I am working directly with the firmware team to try to procure an official version of the Rogers firmware. There are some server issues with the fastboot servers, so please give us a couple more weeks. I want official firmware for everyone here as well, and the ability to modify my phone in the future with the ability to return to official stock.
Sent from my XT925 using Tapatalk 2

alexv305 said:
There already is a bootloader unlock. You can use the motorola bootloader unlock tool. I don't have a developer edition and it worked perfect for me. Other users in the forum also have their bootloaders unlocked.
Click to expand...
Click to collapse
I think that the bootloader unlock that SFG is referring to is a non-Motorola warranty-voiding unlock. It's nice the Motorola supports the unlocking but it really means that they control who gets unlocked and removes any future warranty claims.

waiting for your update. Thanks for checking with the firmware team.
---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------
danifunker said:
I understand how frustrated you are itzak_man because of the lack of official Rogers firmware and that you almost felt lied to by the whole XDA community over the Rogers firmware scandal. Please remember, this is a risk that you take by modifying your phone outside of the manufacturers intended usage. This its the reason why this its the first phone that I haven't modified.
That being said, I am working directly with the firmware team to try to procure an official version of the Rogers firmware. There are some server issues with the fastboot servers, so please give us a couple more weeks. I want official firmware for everyone here as well, and the ability to modify my phone in the future with the ability to return to official stock.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
waiting for your update. Thanks for checking with the firmware team.

I think that the bootloader unlock that SFG is referring to is a non-Motorola warranty-voiding unlock. It's nice the Motorola supports the unlocking but it really means that they control who gets unlocked and removes any future warranty claims.
Click to expand...
Click to collapse
Reporting after a long talk to Motorola Canada services:
The JB upgrade (which is controlled by Motorola) checks your IMEI, android version & the country code.
When I mentioned the 2 versions (492002 & 49003) no body had a clue what I am talking about !
If you bootloader is unlock by Motorola, regardless which version you got, your phone becomes an orphan; No more upgradable !
When I said that there message on line is misleading: Losing the warranty only but nothing about losing any upgrade privileges !
They agree it's wrong & "promise" to fix the worming message (after the fact).
Now I am not sure that there is or was a second version (the 49003) in Motorola arsenal. My guess is that the Boot loader unlock process does more to the phone then just unlock. Possible changing the version system...?
So,our only option is waiting & hopping that we get a full JB version upgradable by RDS.

itzik_man said:
Reporting after a long talk to Motorola Canada services:
The JB upgrade (which is controlled by Motorola) checks your IMEI, android version & the country code.
When I mentioned the 2 versions (492002 & 49003) no body had a clue what I am talking about !
If you bootloader is unlock by Motorola, regardless which version you got, your phone becomes an orphan; No more upgradable !
When I said that there message on line is misleading: Losing the warranty only but nothing about losing any upgrade privileges !
They agree it's wrong & "promise" to fix the worming message (after the fact).
Now I am not sure that there is or was a second version (the 49003) in Motorola arsenal. My guess is that the Boot loader unlock process does more to the phone then just unlock. Possible changing the version system...?
So,our only option is waiting & hopping that we get a full JB version upgradable by RDS.
Click to expand...
Click to collapse
I have a feeling they don't know what they are talking about. There are reports of a number of users who were rooted but still got the upgrade. I've reached out to a couple of them and hopefully we will get a full JB XML restore soon.
Don't forget the date and version differences between 49003 and 492002.
Unlocking the bootloader changes some of the encryption keys used, but definitely not the system version.
Sent from my XT925 using Tapatalk 2

I can understand your frustration but development takes time and requires opportunity. With a locked bootloader & lack of kexec, there simply isn't much developers can do right now. With time, good things may eventually come. But Motorola development will never match that of other popular phones.

I have a feeling they don't know what they are talking about. There are reports of a number of users who were rooted but still got the upgrade. I've reached out to a couple of them and hopefully we will get a full JB XML restore soon.
Click to expand...
Click to collapse
Rooted will get you the OTA, not bootloader unlocked. Once you unlock using your IMEI, your phone info is deleted from Motorola databank.

We need to consolidate the information & comments on the Rogers ICS to JB upgrade to one topic & one location.
The subject is all over in this forum & it creates a great deal of difficulty to trace & follow the objective which is; how to fix the issue of compatibility of versions..

danifunker said:
That being said, I am working directly with the firmware team to try to procure an official version of the Rogers firmware. There are some server issues with the fastboot servers, so please give us a couple more weeks. I want official firmware for everyone here as well, and the ability to modify my phone in the future with the ability to return to official stock.
Click to expand...
Click to collapse
Hi danifunker, for your efforts, thank you.
Out of curiosity:
- what causes the "delay" in you getting official firmware from rogers?
- which version(s) are you planning to get: 2002 and/or JB?
thanks!

I have uploaded Rogers ICS firmware for RAZR HD back in November: http://sbf.droid-developers.org/vanquish_u/list.php
There is no JB for it right now as I'm aware.

Skrilax_CZ said:
I have uploaded Rogers ICS firmware for RAZR HD back in November: http://sbf.droid-developers.org/vanquish_u/list.php
There is no JB for it right now as I'm aware.
Click to expand...
Click to collapse
The version available doesn't allow for OTA update to JB it's the wrong version
Sent from my XT925

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.

Warranty post root?

Is there any official word on whether the warranty will be honored after we unlock the bootloader and root the device or not? From what I could gather, this is the case for most Mi devices but is there any confirmation that the A1 will follow the same as well? I couldn't find anything specific to this device so I'd appreciate it if someone could clear this out for me.
Thank you!

karanrajpal14 said:
Is there any official word on whether the warranty will be honored after we unlock the bootloader and root the device or not? From what I could gather, this is the case for most Mi devices but is there any confirmation that the A1 will follow the same as well? I couldn't find anything specific to this device so I'd appreciate it if someone could clear this out for me.
Thank you!
Click to expand...
Click to collapse
Basically, in my country (Slovakia) and I believe that it's in every country (or at least should be):
If, for example, dead pixels appears on the screen after some time, root procedure or unlocking bootloader has 0 chance of making them dead, so the seller has to prove that the root process made those pixels dead, which is nonsense obviously.
They can deny the warranty if you try to do something with the system itself and you hard brick your device, that's the direct outcome of you trying to play with the phone's software.
Remember, system can be easily unrooted and bootloader can be easily re-locked with no sign of doing such things (not like KNOX), so if you are really afraid of them denying your warranty, you can unroot and re-lock just before the warranty process.

New to the device, planning to root my device. Will MI honor the warranty after root if I flash stock rom before taking it to the service center ?

Yes
karanrajpal14 said:
Is there any official word on whether the warranty will be honored after we unlock the bootloader and root the device or not? From what I could gather, this is the case for most Mi devices but is there any confirmation that the A1 will follow the same as well? I couldn't find anything specific to this device so I'd appreciate it if someone could clear this out for me.
Thank you!
Click to expand...
Click to collapse
I soft bricked my device and it was rooting always into TWRP. Went to the miA1 service centre and told them the truth ( even if I didn't, they could see TWRP). All they asked for is proof of purchase and had to wait my turn for them to flash stock ROM (I couldn't do that as my PC is being win XP)
Free of cost. No questions asked. Thank you Xiaomi
So my understanding is that they do it and there was obviously no need for me to ask for official policy
(Since OP is in the same city as me, it was the service centre close to Navrang theatre)

beeshyams said:
I soft bricked my device and it was rooting always into TWRP. Went to the miA1 service centre and told them the truth ( even if I didn't, they could see TWRP). All they asked for is proof of purchase and had to wait my turn for them to flash stock ROM (I couldn't do that as my PC is being win XP)
Free of cost. No questions asked. Thank you Xiaomi
So my understanding is that they do it and there was obviously no need for me to ask for official policy
(Since OP is in the same city as me, it was the service centre close to Navrang theatre)
Click to expand...
Click to collapse
That's great news! Thank you so much!

beeshyams said:
I soft bricked my device and it was rooting always into TWRP. Went to the miA1 service centre and told them the truth ( even if I didn't, they could see TWRP). All they asked for is proof of purchase and had to wait my turn for them to flash stock ROM (I couldn't do that as my PC is being win XP)
Free of cost. No questions asked. Thank you Xiaomi
So my understanding is that they do it and there was obviously no need for me to ask for official policy
(Since OP is in the same city as me, it was the service centre close to Navrang theatre)
Click to expand...
Click to collapse
Yours being a software problem, they flashed the stock rom even though you had unlocked it. Would they repair the device if it is a hardware problem?

iarshadm said:
Yours being a software problem, they flashed the stock rom even though you had unlocked it. Would they repair the device if it is a hardware problem?
Click to expand...
Click to collapse
No idea