Related
I had a interesting Chat session today with a Moto CSR here is the log:
Me: I purchased a Used Motorola Droid RAZR HD (Verizon) Retail Version Phone. The purpose was to work on android development. I am interested in unlocking my bootloader for that purpose. The phone itself is out of warranty and therefore I am not concerned about voiding the non-existent warranty. Your Bootloader Unlock webpage here seems to not allow me to do so as it is not developer edition.
Me: From my understanding a Dev Version is the only phone listed. However as previously stated I am out of warranty and wondering if it were possible through customer support to unlock my bootloader.
Gerald Ray: I see. Thanks for the information. Please know that here with Motorola we do not advice to unlock the Bootloader of our phones and for that we don't have steps to do it. If you need further assistance, you may check our nearest Repair Center in your area.
Me: Sorry your response is not clarifying.
Me: Is it possible to unlock the bootloader of a Retail XT926 Motorola Droid RAZR HD that is a Non-Developer version?
Gerald Ray: Yes, it is possible.
Me: I live in Sacramento California where is the nearest Motorola Repair center?
Gerald Ray: This is the site to check: http://www.service-center-locator.com/motorola/motorola-service-center.htm
Gerald Ray: Is there anything else that I can assist you today aside from this?
Me: based on the information provided it seems there are no service centers in my immediate area
Gerald Ray: I understand. You may check the nearest one.
Me: Does this require for me to be there in person?
Gerald Ray: You may try calling them first. We have phone numbers from that site.
Me: Ok thank you
I have emailed three of the service centers provided on the webpage he indicated to get their response to this possibility. I will update the thread once I get confirmation or denial of the ability to unlock the bootloader from the service center.
This thread has potential!
As long as the latest ota hasn't been applied, you can unlock the boot loader. Not sure why you're going through all the hassles of calling a csr.
That is unless you're talking about a phone that does have the latest ota which patches the boot loader unlock exploit.
Sent from my Droid RAZR HD under an Eclipse.
I hoping it works because I have a RAZR Maxx HD... That I would like to unlock the boatloader.
Sent from my SGH-T889 using Tapatalk
Y
TheGman125 said:
I hoping it works because I have a RAZR Maxx HD... That I would like to unlock the boatloader.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
Unless another exploit has been found for the latest ota, and believe me we would know if there was, you will not be able to unlock the bootloader unless the phone was already unlocked before the ota.
The ability to unlock the bootloader on the hds was due to a security exploit in the code that existed before the latest ota. Using this exploit, Dan came up with code that fooled the phone into unlocking the bootloader. Once it did this, there was an eFuse that was blown to signal that the bootloader was unlocked. This fuse cannot be reset ever back to a locked state.
However, if you applied the ota before unlocking the bootloader, then what the ota did was patch/fix the exploit which means Dan's unlocking code no longer works, therefore you cannot unlock the bootloader.
It took Dan a long time to find the exploit. He has stated he does not have the time to look for a different one. In fact, there may not be another one. We were lucky that the first one was even found.
So unless Motorola decides to allow the hds to be part of the unlocking tool, I would not hold my breath.
The only other hope for you is if someone were to get kexec running on the HD. However, since because of the (now closed) exploit, no one has attempted it. Since a lot of people have their phones unlocked, I don't think the developers are working on kexec.
Plus, with the HDs being about a year old, and newer phones especially are being released, I just don't see anyone putting forth the time and effort to do this.
But, you could always put out a bounty to see if you raise enough cash to give someone if they attempt and succeed. Usually these don't result in anything coming to fruition.
Sent from my Nexus 7 using Tapatalk 4
iBolski said:
Y
Unless another exploit has been found for the latest ota, and believe me we would know if there was, you will not be able to unlock the bootloader unless the phone was already unlocked before the ota.
The ability to unlock the bootloader on the hds was due to a security exploit in the code that existed before the latest ota. Using this exploit, Dan came up with code that fooled the phone into unlocking the bootloader. Once it did this, there was an eFuse that was blown to signal that the bootloader was unlocked. This fuse cannot be reset ever back to a locked state.
However, if you applied the ota before unlocking the bootloader, then what the ota did was patch/fix the exploit which means Dan's unlocking code no longer works, therefore you cannot unlock the bootloader.
It took Dan a long time to find the exploit. He has stated he does not have the time to look for a different one. In fact, there may not be another one. We were lucky that the first one was even found.
So unless Motorola decides to allow the hds to be part of the unlocking tool, I would not hold my breath.
The only other hope for you is if someone were to get kexec running on the HD. However, since because of the (now closed) exploit, no one has attempted it. Since a lot of people have their phones unlocked, I don't think the developers are working on kexec.
Plus, with the HDs being about a year old, and newer phones especially are being released, I just don't see anyone putting forth the time and effort to do this.
But, you could always put out a bounty to see if you raise enough cash to give someone if they attempt and succeed. Usually these don't result in anything coming to fruition.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
That sounds like a good idea... Would you be able to help with that? The devices are still good and a lot of people like my self would like to try 4.3 and get that great battery life on most if my devices.
Now, could we create community in Google+ and twitter to increase awareness of the bounty?
Sent from my SGH-T889 using Tapatalk
Since my tiny hopes of N5 coming on Verizon is now official dashed, I need to unlock my phone...
i'll be patiently waiting for this thread to update!
Sorry to bring up an old thread, but apparently, no news from the op with a reply is bad news.
Okay we have a Bounty thread... Leave that for just plain Bounty pledges..
In here feel free to talk about BootLoader discusions, Root discussions..
Nice thread. Would be nice to discuss about Moto Maxx root as well. Since it has unlockable bootloader, I believe root is pretty doable, but I have no idea how to, since there's no custom recovery yet.
Nice thread.... looking forward
[ ]'s
some one knows how can we help to find a exploit or something that will make our Turbo able to get root??
When lollipop gets released for the Turbo, I'm going to have a tough decision. I really want that sweet new lollipop, but I also know that the chances of rooting it will go down significantly. So, the question is, should we stay on KitKat in hopes of getting root? It's going to be really hard to resist 5.0. And since the 2014 Moto X just got it, I think we're not far behind.
There's a vulnerability in KitKat, we just have to figure out how to exploit it. CVE-2014-7911. More info can be found at http://seclists.org/fulldisclosure/2014/Nov/51.
Your chances of getting root with LP and a locked bootloader depend on an exploit which has yet to be found and that may be some time and on some phones has never happened on previous operating systems. You would be much better off if the phone was released for unrestricted world wide sales but being CDMA and a Verizon exclusive is guaranteed to prevent the large scale adoption that would have made it more attractive to developers. Realistically no one here knows better than you whether root is more important than getting LP are for you. For my purposes I consider root a must have while having no issues with kk which I like just fine which would make it an easy choice.
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
madeiracam said:
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
Click to expand...
Click to collapse
Maybe. With Qualcomm chips, it's possible to make reverting to an older version result in a hard brick. With Big Red's knowledge of what they can do, unfortunately, they might implement this "feature". Plus, a vulnerability has already been found. We just need to figure out how to exploit it.
madeiracam said:
Correct me if I'm wrong, but can't we just revert to kitkat if an exploit is found?
http://forum.xda-developers.com/showthread.php?t=2929737
That's the factory firmware we could flash if need be.
Click to expand...
Click to collapse
At least with my Motorola RAZR M, every time they had a big version upgrade they also upgraded the security partition (which would be incompatible with prior firmwares), making it impossible to downgrade without an unlocked bootloader.
Sent from my Droid Turbo.
I think I have an idea on how to obtain a bootloader unlock. It most likely will not work, though, as I highly doubt it would be this stupid simple. As I do not yet have a Turbo, could someone send me the result of "fastboot oem get_unlock_data"? PM it to me and I'll test my theory. I'll also need one from some other (model doesn't matter) Motorola device, too, that actually is eligible for official bootloader unlocking.
r3pwn said:
I think I have an idea on how to obtain a bootloader unlock. It most likely will not work, though, as I highly doubt it would be this stupid simple. As I do not yet have a Turbo, could someone send me the result of "fastboot oem get_unlock_data"? PM it to me and I'll test my theory. I'll also need one from some other (model doesn't matter) Motorola device, too, that actually is eligible for official bootloader unlocking.
Click to expand...
Click to collapse
I have both a Droid Turbo and a Motorola device that is eligible for bootloader unlocking, but I don't know if I can trust to give my oem unlock data if that is in any kind "dangerous" for me or my guarantee. Can you just give me a hint and I check it out?
josebama said:
I have both a Droid Turbo and a Motorola device that is eligible for bootloader unlocking, but I don't know if I can trust to give my oem unlock data if that is in any kind "dangerous" for me or my guarantee. Can you just give me a hint and I check it out?
Click to expand...
Click to collapse
Yeah, sure. I'll send I sent you a PM.
Do you still need this? I have a Turbo with a cracked screen um about to send back.
greekstile said:
Do you still need this? I have a Turbo with a cracked screen um about to send back.
Click to expand...
Click to collapse
Yes, but not if you're about to send it back. I'll get another one. I wouldn't be able to test if the unlock worked.
When I say send it back, I don't have to send it right away. If the unlock does work, I assume I could lock it back down before sending back?
greekstile said:
When I say send it back, I don't have to send it right away. If the unlock does work, I assume I could lock it back down before sending back?
Click to expand...
Click to collapse
With Motorola devices, I don't think it's possible. I think the qfuse gets permanently blown. I would send it back if I were you. This method probably won't work anyways.
EDIT: qfuse, stupid autocorrect
I'm willing to give it a shot. Just let me know.
r3pwn said:
With Motorola devices, I don't think it's possible. I think the cause gets permanently blown. I would send it back if I were you. This method probably won't work anyways.
Click to expand...
Click to collapse
i will help u too if needed
got a Droid turbo
danger2u said:
i will help u too if needed
got a Droid turbo
Click to expand...
Click to collapse
How does one have a Turbo that is eligible for unlocked bootloader? This sounds like candy covered in gold to me.
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
JulesJam said:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
Click to expand...
Click to collapse
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
I can't imagine the OTA would lock the bootloader, but who knows...
fury683 said:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
Click to expand...
Click to collapse
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.
Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.
JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.
fury683 said:
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.
fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand
But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.
For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.
So yeah, as you said...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse
superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.
it leaves a copy of the fxz on your computer.
sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.
Any Updates on this situation?
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.
Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.
The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.
I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.
Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
breakthestatic said:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
Click to expand...
Click to collapse
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Maverick-DBZ- said:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked
Droid turbo "OEM unlocking allow the bootloader to be unlocked" option under develope
I have a screenshot but I don't know how to upload it srry. But it is there. Is this for real?
The thread was supposed to say under developer options. My bad.
nils39 said:
I have a screenshot but I don't know how to upload it srry. But it is there. Is this for real?
Click to expand...
Click to collapse
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
tgambitg said:
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
Click to expand...
Click to collapse
I had a feeling that's what it was. But we can always hope.
I tried to unlock it just for shiggles, and of course it didn't work. It even gives you a finished response, but alas, was still locked.
Sent from my Droid Turbo
thats for device protection, a function like apple iphone lock,
http://www.greenbot.com/article/290...ow-about-device-protection-in-android-51.html
http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
if you disable that option, you can flash things on the phone leaving the phone unlocked and open.
Here's a screenshot from mine. It's kind of strange to me that they're talking about security and locking features but it clearly says allows bootloader to be unlocked. But I'm skeptical, unlocking a bootloader in my experience has never been as simple as a flick of a toggle.
Sent from my XT1254 using XDA Free mobile app
It's like we're repeating threads from a week ago.
matt30 said:
It's like we're repeating threads from a week ago.
Click to expand...
Click to collapse
Welcome to XDA, where the people can't read and the search button doesn't matter. :silly:
A mod needs to close this thread.
tgambitg said:
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
Click to expand...
Click to collapse
My Moto Maxx/Moto Turbo XT1225 has unlocked bootloader, as does the U.S. Moto Maxx XT1250, which is the device IDENTICAL to the Droid Turbo XT1254 (same FCC ID). The XT1250 runs just fine on Verizon with Verizon LTE SIM card (like a non- Verizon Nexus 6).
Speaking of which, the Motorola Nexus 6 has unlocked bootloader.
My point is, it's Verizon that is obsessed with locked down bootloaders, not Motorola.
Sorry, but
tgambitg said:
It's part of Lollipop, part of the security measures. And no, it won't mean that we can unlock our bootloaders. Unless Verizon and Motorla change their stance on unlocked bootloaders.
Click to expand...
Click to collapse
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
NapoleanSolo said:
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
Click to expand...
Click to collapse
Sorry, I don't believe you.
Install TWRP and root and post screenshot. If your bootloader is unlocked, that will take 5 minutes.
Another reason I don't believe you is because if this were true it would be all over the Droid Turbo 2 forum and over there they are still complaining about locked bootloader and no root. So, you really don't know what you are talking about.
_____
The Moto X Force (KINZIE) is the International version of the Droid Turbo 2 (KINZIE). It does have unlock-able bootloader, and has TWRP and root. When the Droid Turbo 2 bootloader actually is unlocked TWRP and root for KINZIE will work on it, just like TWRP and root for QUARK works on the Droid Turbo XT1254 (Quark) with all the other Quarks.
And over there, they are still ONE forum, just like all Quarks were one forum until a couple of months ago. So, it's easy to keep track of what's happening with all Kinzies.
NapoleanSolo said:
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
Click to expand...
Click to collapse
No it doesn't, what would make you think this would work, have you actually tried it?
Sent from my DROID Turbo using Tapatalk
Let's keep piling on...
NapoleanSolo said:
Sorry, but it DOES mean the bootloader is unlocked this time. Turbo 2, in fact. Verizon + Moto must have changed their minds..
Click to expand...
Click to collapse
Sorry to bust your bubble, but that slider...yeah, it was on the Turbo when we got the 5.1 update. I could slide it to the "Unlock" position until I was blue in the face, but it had about a snowball's chance in hell of actually unlocking the bootloader. As @ChazzMatt suggested, try to flash TWRP and if you can, I'll eat my words. But the days of an easy unlock on VZW phones are long gone.
So, I just bought a Moto X Style.
And on the Developer options, also have the slide saying OEM Unlock.
It said that, meaning, during the process, the system/ tool will need the permission to unlock
and that slide allows that to happen
hieutrinh85 said:
So, I just bought a Moto X Style.
And on the Developer options, also have the slide saying OEM Unlock.
It said that, meaning, during the process, the system/ tool will need the permission to unlock
and that slide allows that to happen
Click to expand...
Click to collapse
Not relevant whatsoever for the Verizon locked down bootloader Droid Turbo XT1254. I wish people wouldn't keep digging up old threads that have been refuted.
The only thing that works with the XT1254 is paid Sunshine fueled exploit. Other Quarks (XT1225/XT1250) can be unlocked via Motorola website for free.
Hey Im getting the Moto X Pure Editon and I was wondering if there are any viable one click root methods, or a way to root without unlocking the bootloader. I have read that one certain (very questionable) method that XDA is against (and rightly so) can be used, but I have no plans on going that route. Im certainly not new to unlocking a bootloader and am not against it. Ive had the original Moto X Developer Edition, and currently have the Nexus 6, but the whole void the warranty deal I would like to avoid if at all possible. If I could get root and use titanium backup and ad free I could be fine with that. That being said is there a way to root without unlocking the bootloader. And is there something like on the old Droid Razr where you could install a recovery while the bootloader is still locked. Yes I know google is my friend and I have looked but haven't seen anything. So my assumption is I will probably have to unlock the bootloader. But I did want to ask before I jumped and unlocked it, because if anyone would know I know I could find out on here.
pacman377 said:
Hey Im getting the Moto X Pure Editon and I was wondering if there are any viable one click root methods, or a way to root without unlocking the bootloader. I have read that one certain (very questionable) method that XDA is against (and rightly so) can be used, but I have no plans on going that route. Im certainly not new to unlocking a bootloader and am not against it. Ive had the original Moto X Developer Edition, and currently have the Nexus 6, but the whole void the warranty deal I would like to avoid if at all possible. If I could get root and use titanium backup and ad free I could be fine with that. That being said is there a way to root without unlocking the bootloader. And is there something like on the old Droid Razr where you could install a recovery while the bootloader is still locked. Yes I know google is my friend and I have looked but haven't seen anything. So my assumption is I will probably have to unlock the bootloader. But I did want to ask before I jumped and unlocked it, because if anyone would know I know I could find out on here.
Click to expand...
Click to collapse
No, no one has developed a method to root without unlocking the bootlader and i doubt there will be one anytime soon(if ever since it's so easy and is an unlocked phone)
Ok thank you.
pizzlewizzle said:
No, no one has developed a method to root without unlocking the bootlader and i doubt there will be one anytime soon(if ever since it's so easy and is an unlocked phone)
Click to expand...
Click to collapse
With the hassles Motorola gives people trying to get warranty support after unlocking the bootloader, it would actually be quite beneficial.
Unlocking bootloader does not void warranty completely!!! Software issues caused by the user are indeed not under warrenty anymore. Hardware related issues are.. I had 2 times screen blemishes and both times my screen got replaced for free. Great service from motorola.
bartjeh1991 said:
Unlocking bootloader does not void warranty completely!!! Software issues caused by the user are indeed not under warrenty anymore. Hardware related issues are.. I had 2 times screen blemishes and both times my screen got replaced for free. Great service from motorola.
Click to expand...
Click to collapse
Ok I have done that with other phones but I had read mixed results concerning the Moto X Pure. So if it is hardware related Motorola will honor the warrenty, software your SOL. But software we can always reflash the stock system and all.
pacman377 said:
Ok I have done that with other phones but I had read mixed results concerning the Moto X Pure. So if it is hardware related Motorola will honor the warrenty, software your SOL. But software we can always reflash the stock system and all.
Click to expand...
Click to collapse
If you unlock boot loader ur self. Theres a oneclick root app calles kingroot they quote they can root amy phone its one of those china made apps and closed source, id only use ir if your that desperate. Also they install there own version of supersu.. but theres a way to remove it just.google it..
Kingroot doesn't work. At least it didn't on mine. Only way I've found is either systemless or toolkit if you're on lollipop
Jay794 said:
Kingroot doesn't work. At least it didn't on mine. Only way I've found is either systemless or toolkit if you're on lollipop
Click to expand...
Click to collapse
well i found this https://www.search4roots.com/how-to-easily-root-moto-x-style-marshmallow-6-0-1/
StreetkillnHD said:
well i found this https://www.search4roots.com/how-to-easily-root-moto-x-style-marshmallow-6-0-1/
Click to expand...
Click to collapse
I'd stick with the tested and tried methods. One click options have the potential for opening the doorway to unwanted content.....
Chainfire's supersu has been around for a long time.
Unlocking the bootloader is a must if you want to root on this phone... ATM anyway and I doubt it will change. I used to think one click root was the way to go too but once again, there are potentially many things that can go wrong so knowing the tried and true manual ways is always best. Knowing how to recover from botched attempts has allowed me to bring my phone back from soft bricks several times.
Sent from my awesome phone!