Hey,
So as mentioned in the large "How to root" thread, any update after 4.4.3 will essentially make your device unrootable (or unwritable).
I have the xt1058, which is one of the devices with a locked bootloader. This device is also compatible with Android 5.0, so I was wondering if I flash a captured OTA of 5.0 for the xt1058, will that lock out my bootloader and ensure that I can never root again?
Thanks!
5.0 > 4.4.3 so logic would lead me to say yes, you're stuck running stock.
If you are locked, you will not be able to Root on 5.0 for now, or for awhile.... If ever.
---------- Post added at 10:26 AM ---------- Previous post was at 10:26 AM ----------
Once it comes out of course.
---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------
if you really want to Root.... Best to not update, as they may figure out how to Root kit Kat and not Lollipop. Usually how it goes.
themsftcpu said:
Hey,
So as mentioned in the large "How to root" thread, any update after 4.4.3 will essentially make your device unrootable (or unwritable).
I have the xt1058, which is one of the devices with a locked bootloader. This device is also compatible with Android 5.0, so I was wondering if I flash a captured OTA of 5.0 for the xt1058, will that lock out my bootloader and ensure that I can never root again?
Thanks!
Click to expand...
Click to collapse
Not sure what you mean by "flash a captured OTA" but with a locked bootloader all you can flash is a ROM or OTA which is digitally signed by Moto and meant for your phone and its CID value. In other words, you can't capture an OTA zip file, modify, repack it and flash it to include Root, if you have a locked bootloader.
If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection.
If you have a locked bootloader you need someone to find these exploits and create a repeatable process to use them to gain root and disabling write protection. You basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It.
When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you install 4.4.2), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.
On a locked bootloader you are relying on someone finding vulnerabilities in the phone or its software to both root and disable write protection. Period. No way around that.
As it stands right now, no one has released info on any vulnerabilities which could gain root on a locked bootloader 2013 X which have been upgraded to 4.4.4. So there is no process for rooting those locked bootloader phones.
While JCASE's Sunshine tool can exploit a vulnerability to unlock the bootloader (disabling write protection), it needs to be able to ROOT, or Temp Root, the phone first, which leaves out phones on 4.4.4 (unless I've missed a change recently). (and before you ask, no, you can NOT safely downgrade from 4.4.4 to 4.4.2 or lower, nor can you get to a state where Sunshine will work once you have 4.4.4 on your phone.)
With further security enhancements as android evolves, its only going to get more difficult finding vulnerabilities to exploit and creating repeatable processes for those with locked bootloaders. In other words while there might be a chance someone comes up with something for locked bootloader 2013 X's on Lollipop, I wouldn't count on it happening, nor would I "bet the farm" that it will ever happen.
KidJoe said:
Not sure what you mean by "flash a captured OTA" but with a locked bootloader all you can flash is a ROM or OTA which is digitally signed by Moto and meant for your phone and its CID value. In other words, you can't capture an OTA zip file, modify, repack it and flash it to include Root, if you have a locked bootloader.
If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection.
If you have a locked bootloader you need someone to find these exploits and create a repeatable process to use them to gain root and disabling write protection. You basically need to find and exploit a flaw or vulnerability in the phone, or its software. i.e. Hack It.
When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you install 4.4.2), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.
On a locked bootloader you are relying on someone finding vulnerabilities in the phone or its software to both root and disable write protection. Period. No way around that.
As it stands right now, no one has released info on any vulnerabilities which could gain root on a locked bootloader 2013 X which have been upgraded to 4.4.4. So there is no process for rooting those locked bootloader phones.
While JCASE's Sunshine tool can exploit a vulnerability to unlock the bootloader (disabling write protection), it needs to be able to ROOT, or Temp Root, the phone first, which leaves out phones on 4.4.4 (unless I've missed a change recently). (and before you ask, no, you can NOT safely downgrade from 4.4.4 to 4.4.2 or lower, nor can you get to a state where Sunshine will work once you have 4.4.4 on your phone.)
With further security enhancements as android evolves, its only going to get more difficult finding vulnerabilities to exploit and creating repeatable processes for those with locked bootloaders. In other words while there might be a chance someone comes up with something for locked bootloader 2013 X's on Lollipop, I wouldn't count on it happening, nor would I "bet the farm" that it will ever happen.
Click to expand...
Click to collapse
What about using safestrap? I also own a locked moto x and am currently running a rooted 4.4.4 ROM via safestrap.
Would this be possible to do with lollipop while retaining root?
frenchie007 said:
What about using safestrap? I also own a locked moto x and am currently running a rooted 4.4.4 ROM via safestrap.
Would this be possible to do with lollipop while retaining root?
Click to expand...
Click to collapse
You'll likely still need to find a software vulnerability to exploit to gain root. And if Lillipop uses a new Kernel (which is does) it may not be compatible with the current Safestrap. And Hash stopped developing Safestrap.
That being said.. Safe strap requires the host phone/os be rooted with write protection disabled. So if you are running Safestrap on a 2013 X, you likely have Android 4.4 or lower as your host OS and have used something like SlapMyMoto/RockMyMoto along with MotoWpNoMo to root and disable write protection on your host OS. If this is the case, use Sunshine to unlock your bootloader. It will be much easier.
KidJoe said:
You'll likely still need to find a software vulnerability to exploit to gain root. And if Lillipop uses a new Kernel (which is does) it may not be compatible with the current Safestrap. And Hash stopped developing Safestrap.
That being said.. Safe strap requires the host phone/os be rooted with write protection disabled. So if you are running Safestrap on a 2013 X, you likely have Android 4.4 or lower as your host OS and have used something like SlapMyMoto/RockMyMoto along with MotoWpNoMo to root and disable write protection on your host OS. If this is the case, use Sunshine to unlock your bootloader. It will be much easier.
Click to expand...
Click to collapse
Yep, I was holding out on unlocking with sunshine but seems like its necessary to keep root for lollipop. Thanks!
frenchie007 said:
Yep, I was holding out on unlocking with sunshine but seems like its necessary to keep root for lollipop. Thanks!
Click to expand...
Click to collapse
Why would you ever wait to unlock your bootloader if you're able to? You wouldn't have to worry about any of this with an unlocked bootloader.
nhizzat said:
Why would you ever wait to unlock your bootloader if you're able to? You wouldn't have to worry about any of this with an unlocked bootloader.
Click to expand...
Click to collapse
My only guess would be.... he is still under warranty and isn't in a hurry to void it?
nhizzat said:
Why would you ever wait to unlock your bootloader if you're able to? You wouldn't have to worry about any of this with an unlocked bootloader.
Click to expand...
Click to collapse
KidJoe said:
My only guess would be.... he is still under warranty and isn't in a hurry to void it?
Click to expand...
Click to collapse
Because sunshine costs money and yes, I'm in no hurry to unlock it (until lollipop comes along that is)
frenchie007 said:
Because sunshine costs money and yes, I'm in no hurry to unlock it (until lollipop comes along that is)
Click to expand...
Click to collapse
Just keep in mind.... As soon as you update to 4.4.4 or Lollipop, There's no guarantee you'll ever be able to unlock with Sunshine.
You likely know this... But just checking. ?
Darth said:
Just keep in mind.... As soon as you update to 4.4.4 or Lollipop, There's no guarantee you'll ever be able to unlock with Sunshine.
You likely know this... But just checking. ��
Click to expand...
Click to collapse
using safestrap to flash only parts of 4.4.4 (excluding bootloader if I'm not mistaken) allows me to retain full root even on 4.4.4 even with a locked bootloader. however from what I understand you're right this won't be possible for lollipop :/
frenchie007 said:
using safestrap to flash only parts of 4.4.4 (excluding bootloader if I'm not mistaken) allows me to retain full root even on 4.4.4. however from what I understand you're right this won't be possible for lollipop
Click to expand...
Click to collapse
Maybe it could..... But based on the issues I've seen in the N5 section, likely not. Lollipop probably won't play well with anything kit Kat or earlier.
Pretty hard to test too... Who knows what would happen if you tried. Also, who knows when or if SBF files will turn up.
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
Off topic.... But I will feel bad for anyone who has Lollipop complaints and tries downgrading. Could be the end of their device.
Unless moto changes that quirk with their bootloader.
Related
For starters, I have no root, no xposed, no unlocked bootloader, now....
Like the title says, how do I get the phone to undo MotoWPNoMo & write protection back to 1? Is there a method? Where does does MotoWPNoMo make it's changes (bootloader or recovery)?
I'm under the assumption that the changes are made in the bootloader since that's the only thing that doesn't get flashed when downgrading/upgrading from 4.2.2 to 4.4, so updating to 4.4.2 will do it? also should I use fastboot or will an OTA be enough?
Thanks in advanced!
I think I saw you also post this question in another thread, and get the answer... but for those who stumble upon this thread while searching..
If your phone has a locked bootloader and you've rooted with SlapMyMoto (or similar) and Disabled Write Protection by using MotoWpNoMo, but want to re-enable Write Protection for some reason...
There is no way to remove the effects of MotoWpNoMo on 4.4 or lower.
4.4.2 closes the loophole exploited by MotoWpNoMo, so Yes, just get as close to stock and take the OTA to 4.4.2, or use RSDLite to flash the FULL 4.4.2 SBF to your phone, or mFastboot to manually flash ALL parts, one at a time, to your phone. Write protection will become re-enabled once 4.4.2 is on your phone.
Keep in mind, once on 4.4.2 there is no way to root or disable write protection unless you unlock your bootloader.
KidJoe said:
I think I saw you also post this question in another thread, and get the answer... but for those who stumble upon this thread while searching..
If your phone has a locked bootloader and you've rooted with SlapMyMoto (or similar) and Disabled Write Protection by using MotoWpNoMo, but want to re-enable Write Protection for some reason...
There is no way to remove the effects of MotoWpNoMo on 4.4 or lower.
4.4.2 closes the loophole exploited by MotoWpNoMo, so Yes, just get as close to stock and take the OTA to 4.4.2, or use RSDLite to flash the FULL 4.4.2 SBF to your phone, or mFastboot to manually flash ALL parts, one at a time, to your phone. Write protection will become re-enabled once 4.4.2 is on your phone.
Keep in mind, once on 4.4.2 there is no way to root or disable write protection unless you unlock your bootloader.
Click to expand...
Click to collapse
Thanks, I kinda new but wanted to be 100% since I oculdn't find the thread I read it in soo long ago.
also, no ones been able to answer this maybe you can. Does MotoWpNoMo perform it's hackery in the bootloader? I assumed yes since that's the only change between 4.2.2/4.4 and 4.4.2 when flashing. I'm really curious also if you have any links to a more in depth answer to this I would love to read it!!
drago10029 said:
Thanks, I kinda new but wanted to be 100% since I oculdn't find the thread I read it in soo long ago.
also, no ones been able to answer this maybe you can. Does MotoWpNoMo perform it's hackery in the bootloader? I assumed yes since that's the only change between 4.2.2/4.4 and 4.4.2 when flashing. I'm really curious also if you have any links to a more in depth answer to this I would love to read it!!
Click to expand...
Click to collapse
I don't know for sure. I can only suspect. Beaups or JCase might be able to tell you, since they worked on the tool...
KidJoe said:
I don't know for sure. I can only suspect. Beaups or JCase might be able to tell you, since they worked on the tool...
Click to expand...
Click to collapse
I think i asked in one of their threads but got no response. thanks though.
i really need help trying to figure how to root my AT&T Motorola Moto x. i tried to downgrade but couldnt succeed and i tried unlocking bootloader as well and couldnt succeed either. if anyone can help me please reply! thank you.
Sorry for the long answer, but I think you're going to need this info....
The Moto Maker and Retail Moto X from ATT and Verizon have locked bootloaders and can't have their bootloaders unlocked. Moto doesn't give out the bootloader unlock codes for them. There was a Chinese site selling the codes but it got shut down.
Since you couldn't downgrade successfully, I'm going to guess that you have 4.4.2 on your phone?
Due to changes in the bootloader, GPT.BIN and other parts included with 4.4.2, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2!! i.e. do NOT attempt to downgrade from 4.4.2 to anything lower.
I don't know what state your phone is in now, but if you had 4.4.2 on your phone, and you tried to downgrade, but didn't brick, do NOT take any OTA's!!! That will definitely brick your phone. For now, you'll likely get HAB Check errors, and other things if you try to reboot into bootloader or recovery. If you try to go under Settings -> Security you likely be "kicked back" to the settings screen instead. If you are experiencing these or similar issues, when the ATT 4.4.2 SBF gets leaked and posted to -> http://sbf.droid-developers.org/phone.php?device=0 you'll want to download it and flash your phone with it to get back to a stable/consistent foundation.
As for rooting the X with a locked bootloader... (like the ATT Moto X, or non-Developer Verizon X)
If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection.
When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you take the 4.4.2 OTA), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.
Even if you have root, but lost Write Protection, any apps you've installed that need to write to system can't permanently save their changes (you have to re-do every time your phone powers off/on), and any Root type app, or app that gets installed to /system after WP is enabled will be lost at power off/on.
MotoWpNoMo was used on 4.4. and below to Disable Write Protection. Part of the 4.4.2 update patches the exploit that MotoWpNoMo used, so it wont work on 4.4.2.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower to Root, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone, so you can't use these anymore.
JCASE has already posted he has an exploit to use to gain root on 4.4.2, but due to job and family, wont release it or a process making use of it until the fall. Who knows what ROM Moto will push out by then, and if they will have patched the exploit already. BUT before you get mad at JCASE for waiting so long, that doesn't address a Write Protection dis-abler. I've not seen any talk about work on that for locked bootloaders (when you unlock the bootloader, like on Dev Editions, the write protection is disabled). So JCASE could release his Root exploit, he or someone could develop that process, but it would be kind of useless without the ability to disable write protection since all your changes would be lost as soon as you power off/on.
Trust me, *IF* or when a Root and Write Protection bypass is out for 4.4.2, you will see threads on it. Until then, you have to sit tight.
Now, if you have 4.4 on your phone, you can root and disable write protection by using SlapMyMoto and MotoWpNoMo, but then you must NOT take the 4.4.2 OTA update, as you will keep root, but write protection will become enabled again. You can use a root capable file explorer (like Root Explorer) to navigate to /system/priv-app and rename the 3C_OTA.APK to 3C_OTA.APK.BAK to prevent the OTA update prompts.
If you are on 4.4 rooted with write protection disabled, you might want to check out the SafeStrap discussions over at Rootzwiki.com. That might at least afford you a way to run 4.4.2.
I had a Moto X that I unlocked via the China seller, and it's being replaced because it's bricked. is there a way to put roms on a locked device? or can I unlock the bootloader again for cheap? I paid roughly 40 dollars for it last time.
jcase has a thread for using an exploit to root your phone without unlocking the bootloader. It can be found here:
http://forum.xda-developers.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957
NOTE: Please read the entire jcase link so you understand the risk/process!
Is there a reason why you want a custom ROM? It's certainly your choice, and respectable but if you're looking for minor tweaks to make it look different you may just want to try the GravityBox module with the Xposed Framework. That way you can just worry about rooting your phone, and then tweaking everything else to your liking after that.
I enjoy PA pie along with halo, PA has the best pie controls in my opinion. So it seems they sent me a moto x on 4.4.2, is my only option pie root than using safestrap? Or what is the best way to go about putting a ROM on this?
ovismos said:
jcase has a thread for using an exploit to root your phone without unlocking the bootloader. It can be found here:
http://forum.xda-developers.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957
NOTE: Please read the entire jcase link so you understand the risk/process!
Is there a reason why you want a custom ROM? It's certainly your choice, and respectable but if you're looking for minor tweaks to make it look different you may just want to try the GravityBox module with the Xposed Framework. That way you can just worry about rooting your phone, and then tweaking everything else to your liking after that.
Click to expand...
Click to collapse
^^^
scottshebs said:
^^^
Click to expand...
Click to collapse
You'll need a way to get a custom recovery running to install the ROM. TBH, I have a Dev Edition VZW Moto X, so all I do is unlock my bootloader.
Having that being said it looks (from what I read!) like Safestrap allows you to use a custom recovery, in addition of making nandroids and such. From what you're telling me, it pretty much looks like the way to go.
ovismos said:
You'll need a way to get a custom recovery running to install the ROM. TBH, I have a Dev Edition VZW Moto X, so all I do is unlock my bootloader.
Having that being said it looks (from what I read!) like Safestrap allows you to use a custom recovery, in addition of making nandroids and such. From what you're telling me, it pretty much looks like the way to go.
Click to expand...
Click to collapse
Would the 4.4.2 pie root work? It says it does not disable write protection and it is a tethered root.
Right. And safestrap won't work on 4.4.2.
So no, unless you unlock the bootloader again, you won't be able to flash a custom rom or recovery unfortunately.
scottshebs said:
Would the 4.4.2 pie root work? It says it does not disable write protection and it is a tethered root.
Click to expand...
Click to collapse
It doesn't look like it.
http://forum.xda-developers.com/moto-x/moto-x-qa/att-moto-x-rooting-long-term-effects-t2854742
From KidJoe in that post:
"As for safestrap, I don't use it since I have a Dev Edition and unlocked my bootloader. There are some threads and discussions over on Rootzwiki.com BUT you will need to be rooted with write protection disabled to use SafeStrap... Since you are now on 4.4.2, you can't disable write protection, so safestrap is out. "
So I think customer recovery is out unless you get a bootloader unlocked. And without custom recovery, you wouldn't be able to do a custom ROM.
You can still root the stock ROM though! That's what the PIE method will do. Don't think that will give you custom recovery.
Also, you want TowelPieRoot. Not either individually. That will give you root, but not disabled write protection. So mostly it's only useful for certain apps to be used.
KJ said:
Right. And safestrap won't work on 4.4.2.
So no, unless you unlock the bootloader again, you won't be able to flash a custom rom or recovery unfortunately.
Click to expand...
Click to collapse
Beat me to it.
ovismos said:
Beat me to it.
Click to expand...
Click to collapse
So I'm basically ****ed. Any possible way to downgrade to 4.4?
KJ said:
Also, you want TowelPieRoot. Not either individually. That will give you root, but not disabled write protection. So mostly it's only useful for certain apps to be used.
Click to expand...
Click to collapse
scottshebs said:
So I'm basically ****ed. Any possible way to downgrade to 4.4?
Click to expand...
Click to collapse
Downgrading is a dangerous thing on the X... It can easily end up in a brick, or other issues... Or a brick later.
No one who knows how this phone works ever recommends downgrading.
So no.... You are out of luck right now.
You can try the Middleman again... Or wait for a Possible exploit maybe being released, sometime.
But most advise not to upgrade either until this exploit that maybe will come out comes out. In vase 4.4.4 is incompatible with it.
It will also cost you money though.
---------- Post added at 03:17 PM ---------- Previous post was at 03:11 PM ----------
BTW, mixing the dangerous on its own downgrading with slapmymoto and safestrap is a definite recipe for disaster.
scottshebs said:
So I'm basically ****ed. Any possible way to downgrade to 4.4?
Click to expand...
Click to collapse
Not the parts that matter when it comes to disabling write protection on a locked boot loader phone, and certainly not safely for the rest of the Roms.
Rather than retype...
KidJoe said:
No.
For ALL Developer Editions Moto X, and some carrier editions (Like T-Mobile, Sprint, Rogers and others), Motorola freely gives away the BootLoader Unlock codes when requested On Motorola's Web SIte. In the case of the Non-Developer Editions, it voids their warranty to request the code. However, for some carriers (like ATT, Verizon and republic Wireless in the USA) motorola does not give out the unlock code.
So when you get your X, try to get the unlock code from Moto's web site. Then....
If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
If you can NOT unlock your bootloader, and you are on 4.4.2 you can use TowelPieRoot to root (but write protection is still enabled).
If you can NOT unlock your bootloader, and your are on 4.4.4 you can not root.
If you can NOT unlock your bootloader, and by some miracle your phone is still on 4.4 (aka 4.4.0) or below, you can look at SlapMyMoto and MotoWpNoMo to root and disable write protection. HOWEVER, once you upgrade you will lose write protection, and be subject to the above conditions on rooting depending on your ROM version
And no, if you are on 4.4.4 you can NOT fully downgrade to 4.4.2 or lower. If you are on 4.4.2 you can NOT fully downgrade to 4.4 (aka 4.4.0) or lower! If you try, you will likely brick your phone or set it up to brick with future OTA's.
EDIT: And if Moto's web site doesn't give out your bootloader unlock code, you MIGHT have a chance using the China Middleman (see the thread in the general section). If its available and you can purchase that way, you can then unlock your bootloader exactly as if you got the code from Moto's own web site and follow any instructions as if you got the code from moto. The only difference is where you got the code, and how much it cost.
If you decide to go the China Middleman route, see -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/post52648309
Click to expand...
Click to collapse
oh and about safestrap, it needs write protection disabled to install. Something that can only be done on 4.4.0 and 4.2.2 with camera fix Roms if you have a locked boot loader
KidJoe said:
Not the parts that matter when it comes to disabling write protection on a locked boot loader phone, and certainly not safely for the rest of the Roms.
Rather than retype...
oh and about safestrap, it needs write protection disabled to install. Something that can only be done on 4.4.0 and 4.2.2 with camera fix Roms if you have a locked boot loader
Click to expand...
Click to collapse
****
So if I towelpieroot I could use xposed for the time being?
scottshebs said:
****
So if I towelpieroot I could use xposed for the time being?
Click to expand...
Click to collapse
Seems people have trouble getting Xposed to work. Read through that thread about it.
I have a locked BL VZW XT1060 on 4.4.2 stock
It was/is rooted.
It has SuperSU installed but without binaries installed.
A little history:
Originally on 4.2.2 then OTA to 4.4.
Downgraded to 4.2.2 and applied SlapMyMoto.
I believe I took OTA to 4.4 with the intention to sit tight there.
I accidentally took OTA to 4.4.2.
This is where it gets weird.
Root was still intact but write protection was temporary, meaning after reboot, I lose it.
This was fine as it allowed me to temporarily disable write protection and enable the native hotspot.
Then, one day I was updating some apps on my phone, I noticed that I completely lost the ability to disable to write protection. I tried uninstalling all to the app updates to no avail.
What are my options to get WiFi tether/Hotspot back?
Sunshine, unlock the bootloader, and have a fully unlocked device. Anything else and you'll likely run into issues similar to what you have now.
Sent from my Moto X
What the guy above me said.
@slingblade01 what you described is exactly what happens.
The vulnerability which MotoWpNoMo exploited to disable write protection was patched in 4.4.2, so if you have a LOCKED Bootloader, and updated from 4.4 you could keep root, but write protection became enabled with no way to disable it again.
If you don't care about upgrading past 4.4.2, you can search for TowelPieRoot, and gain temp root to.
Otherwise, as @imnuts and @nhizzat say, If you are still on 4.4.2, and have its bootloader, then you can use Sunshine to unlock the bootloader, after witch your phone will be just like a Developer Edition, or other edition with the bootloader unlocked.
In other words, once you unlock using Sunshine, you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Just please be sure to use the latest TWRP fastboot IMG file and Installable ZIP of SuperSU. Once completed, you will have root with write protection disabled.
And it does not matter what Stock ROM or Android version is on your phone (Android 5 has some changes, so stay tuned) , once your bootloader is unlocked, you can always root or re-root it. (You just can't take OTA with custom recovery on there!!).
For Sunshine discussion see -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471
and -> http://forum.xda-developers.com/showthread.php?t=2792487
and most importantly....
http://theroot.ninja/
Sunshine will check if its compatible with your phone first, if it is, it will charge you $25 before proceeding to unlock you. Unlike using the bootloader unlock code from Moto or the middleman, using Sunshine to unlock your bootloader is not destructive.
Once your bootloader is unlocked via Sunshine, do NOT attempt to re-lock it. because if you do relock it, you wont be able to unlock it again!! BTW, there is no need to relock anyway. It doesn't impact taking OTAs, etc.
Thank you and last question.
Thanks, that was the answer I was expecting but wanted professional opinions first.
Before I use Sunshine, do I need to do any prep work first, such as disable/remove root (remove SuperSU)?
Thanks again.
slingblade01 said:
Thanks, that was the answer I was expecting but wanted professional opinions first.
Before I use Sunshine, do I need to do any prep work first, such as disable/remove root (remove SuperSU)?
Thanks again.
Click to expand...
Click to collapse
Because I have a developer edition, I got my bootloader unlock code from moto, and haven't tried Sunshine.
From my brief reading/following of the Sunshine thread, I don't think you have to un-do anything. But I would consider flashing back to stock to remove any traces of SlapMyMoto and the like AFTER you unlock via Sunshine.
I haven't seen any root methods listed here for 5.0.
I'm still on 4.4 because I didn't want to lose system write or root. Has anyone been able to successfully root 5.0 with system write ability? What method did you use?
I've seen mentions of using Chain Fire but the articles are usually poorly written, so I don't trust them.
d3athsd00r said:
I haven't seen any root methods listed here for 5.0.
I'm still on 4.4 because I didn't want to lose system write or root. Has anyone been able to successfully root 5.0 with system write ability? What method did you use?
I've seen mentions of using Chain Fire but the articles are usually poorly written, so I don't trust them.
Click to expand...
Click to collapse
Twrp has the option to root.
When you reboot from it.
That's how I rooted twrp
I'm on AT&T, so my bootloader is still locked. Unless someone has figured out how to unlock without paying $25.
d3athsd00r said:
I'm on AT&T, so my bootloader is still locked. Unless someone has figured out how to unlock without paying $25.
Click to expand...
Click to collapse
If you have a locked bootloader you need someone to find a in the phone, or its software. Then a repeatable process must be created to use the exploit to gain root. i.e. Hack It.
Root is only part. There is also Write Protection to worry about.. When Write Protection is enabled (the phone's default state with locked bootloader, any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on. Starting with 4.4.2, on a locked bootloader we can't disable write protection. No Vulnerabilities have been found/posted. However, Unlocking the bootloader disables write protection.
So if you have a locked bootloader, and want to root 5.02, you first need 5.02 to come out, then vulnerability found, tested, and a process created. When 5.1 comes out, it needs to be tested to see if the vulnerability was patched. if it was, the work starts all over again.. Its like playing "whack a mole." And even then you likely will have write protection enabled... so any power off/on or "hard boot" will mean lost changes to your phone.
Since the 2013 X is getting old, and only ATT, Verizon, and Republic wireless can't unlock their bootloader through Motorola's site, Paying $25 to use Sunshine if your phone is still on 4.4.2 or lower, is not a bad deal if you want to be sure you can root and disable write protection no matter what Android version comes to your phone.
NOTE: I am not affiliated with Sunshine... just trying to help you understand... Coming up with a root process for a LOCKED Bootloader isn't "quick and easy"
d3athsd00r said:
I'm on AT&T, so my bootloader is still locked. Unless someone has figured out how to unlock without paying $25.
Click to expand...
Click to collapse
That's literally the only way you are going to have root on lollipop. At least for a while anyways. I don't think many people would be interested in finding and creating exploits after this phone has already be exploited to the point where almost everyone can unlock their bootloader. I started at 4.4, went down to 4.2.2, used RockMyMoto and MotoWPnomo, then used SlapMyMoto when upgrading back to 4.4. After that I installed Safestrap and was able to use the stock (and rooted) ROMs by @Ctrl-Freak all the way up to 4.4.4. But after I heard about Sunshine... That was the holy grail. Unlocked my bootloader, flashed a clean install of stock 4.4 and just upgraded till 4.4.4 again, flashed TWRP, rooted, and that was it.
Thanks guys. I was always wary about Sunshine. Just never sat well with me, but I think I'm going to do it after I move into my new house since I have no plans to upgrade anytime soon.
d3athsd00r said:
Thanks guys. I was always wary about Sunshine. Just never sat well with me, but I think I'm going to do it after I move into my new house since I have no plans to upgrade anytime soon.
Click to expand...
Click to collapse
Its true, Sunshine is kind of risky... BUT because of those involved with it, I would consider it as safe as any "hack" can get.
If I didn't have a Dev Edition X, and needed to unlock my bootloader, I would not hesitate to use Sunshine.