I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
STEyeAndroid said:
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
Click to expand...
Click to collapse
I would start here: http://forum.xda-developers.com/showthread.php?t=2536200
I don't know why the unlocked bootloader warning screen would stay set if you relocked it, but you can change that screen to display whatever you want. See here for details:
http://forum.xda-developers.com/showthread.php?t=2417961
Since you have the dev edition, you should be able to unlock, install TWRP, and root without slapmymoto or pwnmymoto. I did it all AFTER installing the latest OTA, and I had no trouble.
I have not used RSDLite, but that is the way I understand it.
STEyeAndroid said:
I have the Verizon Dev Edition Moto X. Understanding that I won't void my warranty if I unlock the bootloader, it has been stated in many threads that even if you re-lock the bootloader it still will give you a warning boot screen (unlocked BL) because there are flags that are permanently changed on the phone once you unlock it.
That being said, I am very non-committal, so I first want to just root the phone and install safestrap. I have seen a ton of tools out there that root your device, however I am confused as to which one I should run (e.g. slapmymoto, pwnmymoto, etc). I am on the latest firmware (4.4), so I think it requires you to downgrade? Any words of sage advice is appreciated...
Also, any changes I make to my phone, I can always RSDLite my way back to 100% stock correct?
Click to expand...
Click to collapse
Sell or trade your dev edition. Installing SafeStrap on that phone is such a waste of time and energy.
Or read more. There are ways to remove the boot logo screen.
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
STEyeAndroid said:
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
Click to expand...
Click to collapse
It appears to. And the statement about still receiving the unlocked bootloader warning after re-locking the bootloader is correct.
However, since the warranty of the Dev Edition is not voided, just unlock the bootloader, root, and then get rid of the message by replacing the logo.bin
STEyeAndroid said:
Can anyone confirm whether or not unlocking the boot loader sets a permanent flag?
Click to expand...
Click to collapse
You bought a dev edition, it doesn't matter if the flag is set or not.
Related
I need help and that's an understatement. It comes down to this... I'm super confused as what I need to do to flashing a custom recovery and ROM. I'm on a Sprint Moto X running 4.4.
Someone just tell me what to do if you can. This downgrading and what not is confusing me when I see people saying not to worry about it.
Thanks in advance.
Sent from my XT1056 using Tapatalk
Since the downgrading and what not is confusing you, I'm not sure what you know and what you don't so let me start at the beginning...
When you purchase the Sprint, T-Mobile, AT&T, Verizon and other carrier editions, they come with their bootloaders locked. You can only flash/install roms and parts of ROMs which are signed by Motorola. This means you have to use some tricks and exploits to root your phone and disable the phone's Write Protection. This is why you see the SlapMyMoto, and MotoWPNoMo, and the like. These processes involve downgrading the rom on your phone so you can take advantage of "flaws" which are present in the older rom and exploited to gain root and disable write protection.
With ROM updates, Motorola can/will close the holes and flaws, meaning new exploits are needed to gain root and such. With 4.4.2, Moto closed the loop hole that allowed downgrading the ROM version on your phone, so you can't use the older tricks to gain root and disable write protection. So if you have 4.4.2 on your X, you are stuck.
If you purchased a developer edition, you can unlock your bootloader, and do so without voiding your phone's warranty. This allows you to flash things/roms/parts that are not signed by Motorola. You can flash a custom recovery for example. Unlocking the bootloader also disables the Write Protection. So you can easily root by flashing a custom recovery, booting to it, and installing SuperSU to root. And you can even flash a custom rom if you want, and if there is one available for your X. This works no matter what ROM version you flash. (this still works for 4.4.2)
Thankfully, some carriers allow you to unlock your Non-Developer Edition X's bootloader. Sprint and T-Mobile allow this. However some, like Verizon and ATT do not. Motorola has a web site setup where you can request the unlock code for your phone. However if your carrier allows this, and you have a Non-Developer edition phone, your warranty is voided when you Accept the terms and REQUEST the code. BUT this does give you the exact same flexibilty to root and disable write protection as a Developer Edition does, just with a voided warranty.
So when you read these threads, there will be info for LOCKED Bootloader and UNLOCKED bootloader.
Ok, that being said.. Since you have a Sprint X, if you are ok voiding your warranty, the best thing to do is get the unlock code from Moto's web site, unlock your bootloader, and use the Root Process for developer edition Moto X. (there is a thread for it) If you already have 4.4.2 on your phone, this is the only way to root and disable write protection.
If you do not want to void your warranty & unlock your bootloader, then you have no choice but to follow the SlapMyMoto thread to root. it does involve downgrading your rom,etc. BUT do not even think about taking the 4.4.2 update if you want to keep root and write protection disabled. And this doesn't work if you already have 4.4.2 on your phone.
Jon.StatiK said:
I need help and that's an understatement. It comes down to this... I'm super confused as what I need to do to flashing a custom recovery and ROM. I'm on a Sprint Moto X running 4.4.
Someone just tell me what to do if you can. This downgrading and what not is confusing me when I see people saying not to worry about it.
Thanks in advance.
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
The Sprint model has an unlockable bootloader so you wont need to follow the SpapMyMoto steps. That's only for those with a locked bootloader (although you could do it if you really wanted to).
I unlocked my US Cellular Moto X which is pretty much the exact same thing but without the same model number. So this is what I did:
Unlock the boatloader through the Motorola unlock program. This voids your warranty though.
Flash twrp
Flash supersu
And now your rooted!
Now that you've flashed a custom recovery, the only thing left to do on your list is flash the rom you want.
NOTE: This will only work of you have an unlockable boatloader in which case - you do. If you are able to request an unlock code through the program then just follow those steps and you'll be sweet. Just make sure you copy the code into a word document then remove the spaces first. I made the error of leaving the spaces in there and wondered why I couldn't request a code. Also the request button is at the very bottom of the page so just scroll to the bottom to find it once you input the code. A message will pop up if you forgot to remove the spaces.
Sent from my SM-N9005 using xda app-developers app
If I unlock the bootloader and go that route I'm open to flash any ROM I want right?
Sent from my XT1056 using Tapatalk
Right. Thanks for the help!
Sent from my XT1056 using Tapatalk
KidJoe said:
Since the downgrading and what not is confusing you, I'm not sure what you know and what you don't so let me start at the beginning...
When you purchase the Sprint, T-Mobile, AT&T, Verizon and other carrier editions, they come with their bootloaders locked. You can only flash/install roms and parts of ROMs which are signed by Motorola. This means you have to use some tricks and exploits to root your phone and disable the phone's Write Protection. This is why you see the SlapMyMoto, and MotoWPNoMo, and the like. These processes involve downgrading the rom on your phone so you can take advantage of "flaws" which are present in the older rom and exploited to gain root and disable write protection.
With ROM updates, Motorola can/will close the holes and flaws, meaning new exploits are needed to gain root and such. With 4.4.2, Moto closed the loop hole that allowed downgrading the ROM version on your phone, so you can't use the older tricks to gain root and disable write protection. So if you have 4.4.2 on your X, you are stuck.
If you purchased a developer edition, you can unlock your bootloader, and do so without voiding your phone's warranty. This allows you to flash things/roms/parts that are not signed by Motorola. You can flash a custom recovery for example. Unlocking the bootloader also disables the Write Protection. So you can easily root by flashing a custom recovery, booting to it, and installing SuperSU to root. And you can even flash a custom rom if you want, and if there is one available for your X. This works no matter what ROM version you flash. (this still works for 4.4.2)
Thankfully, some carriers allow you to unlock your Non-Developer Edition X's bootloader. Sprint and T-Mobile allow this. However some, like Verizon and ATT do not. Motorola has a web site setup where you can request the unlock code for your phone. However if your carrier allows this, and you have a Non-Developer edition phone, your warranty is voided when you Accept the terms and REQUEST the code. BUT this does give you the exact same flexibilty to root and disable write protection as a Developer Edition does, just with a voided warranty.
So when you read these threads, there will be info for LOCKED Bootloader and UNLOCKED bootloader.
Ok, that being said.. Since you have a Sprint X, if you are ok voiding your warranty, the best thing to do is get the unlock code from Moto's web site, unlock your bootloader, and use the Root Process for developer edition Moto X. (there is a thread for it) If you already have 4.4.2 on your phone, this is the only way to root and disable write protection.
If you do not want to void your warranty & unlock your bootloader, then you have no choice but to follow the SlapMyMoto thread to root. it does involve downgrading your rom,etc. BUT do not even think about taking the 4.4.2 update if you want to keep root and write protection disabled. And this doesn't work if you already have 4.4.2 on your phone.
Click to expand...
Click to collapse
I gotta say @kid Joe this is an awesome explanation. I'm on the fence about voiding my warranty never have I seen such a detailed explanation without any animosity or being rude. I love Xda.
Sent from my XT1053 using Tapatalk
r_diaz13 said:
I gotta say @kid Joe this is an awesome explanation. I'm on the fence about voiding my warranty never have I seen such a detailed explanation without any animosity or being rude. I love Xda.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Agree completely. I was about to comment the same. Great response.
So I've just ordered an unlocked black 16gb Moto X from Amazon and would like to update it to 4.4.2 and get root access. I know there are a few guides and threads around but am confused as to which variant I'll have as all the guides seem to be carrier specific, and whether my bootloader will be unlocked or not...
Also, I think it'll come with 4.2.2. Should I go ahead and do the 4.4.2 OTA update, or will that make rooting more difficult? Can I root first then update?
I'm not entirely clueless about this kind of thing, having successfully rooted and installed custom firmware on previous android phones but this seems a little more complicated.
Any help much appreciated. Thanks!
If it's an unlockable bootloader, just take all the updates, unlock the bootloader, mfastboot your choice of recovery, boot immediately to recovery and root. Done.
Since its not a developer edition, unlocking your bootloader will void your warranty. You can request the unlock code directly from Moto's web site for free.
To root after your bootloader is unlocked, just follow this -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
Once you get the code from Moto, you can unlock the bootloader at any point, no matter what rom is on your phone. But you might as well either take the OTA update or flash the 4.4.2 SBF to get to 4.4.2 on your phone, then unlock the bootloader and root. (unlocking the bootloader does factory reset the phone, and erases data and apps, so don't go nuts customizing the phone or installing apps until after you unlock the bootloader).
Thanks for the replies.
How do I find out if my bootloader is unlockable? The Motorola site says that Sprint, USC and TMO phones can be done but nothing about factory unlocked ones...
What if the boitloader can't be unlocked?
seebasso said:
Thanks for the replies.
How do I find out if my bootloader is unlockable? The Motorola site says that Sprint, USC and TMO phones can be done but nothing about factory unlocked ones...
What if the boitloader can't be unlocked?
Click to expand...
Click to collapse
The SIM unlocked version can be bootloader unlocked.
Follow the instructions and steps to request the code at -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth once you hit the final submit button, your warranty will be voided.
Awesome thanks, not as complicated as I had anticipated then...
And once I'm on 4.4.2 and rooted, I won't be able to Do any future OTA updates without losing root right?
seebasso said:
Awesome thanks, not as complicated as I had anticipated then...
And once I'm on 4.4.2 and rooted, I won't be able to Do any future OTA updates without losing root right?
Click to expand...
Click to collapse
Wrong. Rather than my re-typing... see -> http://mark.cdmaforums.com/MotoX-OTA.html
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.
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 must have missed a step when I unlocked my XT1053 last year. I never did anything with it and assumed that because it gives the the caution screen when I turn it off and back on, that the bootloader is unlocked. However, now that I decided to get down and do stuff, it's telling me via third party apps that my phone isn't actually unlocked. There's no super user app or anything. Do I need to go through the unlocking process again? I'm on 4.4.4.
Me again. I'm following the directions for rooting it and have flashed TWRP 2.8.6.0 but when I select Recovery, there's a dead android and it says "No Command."
You have an unlocked boot loader but you don't have root privelages.Also try holding down volume down+power on no command
It takes some reading comprehension but the tutorials here really are excellent. I guess I have a philosophical question: why would you unlock the bootloader without the intention of rooting the phone? I had (obviously) confused the terms.
s3ars said:
I must have missed a step when I unlocked my XT1053 last year. I never did anything with it and assumed that because it gives the the caution screen when I turn it off and back on, that the bootloader is unlocked. However, now that I decided to get down and do stuff, it's telling me via third party apps that my phone isn't actually unlocked. There's no super user app or anything. Do I need to go through the unlocking process again? I'm on 4.4.4.
Click to expand...
Click to collapse
Can you boot the phone into Fastboot/Bootloader mode? What does it say for the status?
If its LOCKED Status 0, then your bootloader is locked. If its LOCKED Status 2 (or 1), then you are "Relocked" (i.e. the bootloader was unlocked, then someone used the Fastboot OEM LOCK process to relock the bootloader). The phone will always show the UNLOCKED Warning message screen if your status is no longer 0. (As users, we can toggle between Unlocked and Relocked, but can't get it back to Locked Status 0).
Since the XT1053 can unlock its bootloader via the code from Moto's web site, you can always just follow the bootloader unlock process again, using the same unique code for your phone.
After your phone's bootloader is showing UNLOCKED Status 3, you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 (Step 8 IS necessary) Please be sure to use the latest TWRP fastboot IMG file and Installable ZIP of SuperSU
---------- Post added at 08:31 AM ---------- Previous post was at 08:26 AM ----------
s3ars said:
It takes some reading comprehension but the tutorials here really are excellent. I guess I have a philosophical question: why would you unlock the bootloader without the intention of rooting the phone? I had (obviously) confused the terms.
Click to expand...
Click to collapse
Since doing the bootloader unlock process is "desctructive" (i.e. wipes use data/apps from the phone), some will unlock the bootloader when they first get the phone, run with it, and maybe root later... that way when they do decide to root, they wont need to also wipe the phone and have to set it back up from scratch.
But that is the only reason I can think of why one would unlock the bootloader, and not root. At the same respect, if you don't have a phone which is branded Developer Edition, you've already voided the phones warranty by requesting the code from Moto, so, why not root immediately?