MotoWPNoMo how to get back to 1 - Moto X Q&A

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.

Related

[Q] Fastboot failure help needed

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.

Root and BL help

Hi everyone
Okay so Im going to ask a couple of noob questions here. I have been doing a lot of searching on and off xda but I still have a few doubts about rooting/flasing/unlocking my moto x.
If these questions have been asked before I apologize.
First off, I know that my motoX is from ATT, so it has a locked bootloader, right?
And also that it is a 16GB version so is definitely not DE.
I came across a source where it said I can still root my X with a locked bootloader and that must enable me to flash custom roms. Is this true? (I am a little hesitant about trusting websites other than xda). Why do we even need to unlock the bootloader then? if flashing custom roms is a go with root.
My phone is currently on 4.2.2. How am i supposed to find out if this is the pre or post camera update?
I would really appreciate your replies here as I am holding back from updating to KitKat (I read bootloader cant be unlocked on 4.4). Thanks a lot!
See this thread...
http://forum.xda-developers.com/showthread.php?t=2826159
And you can not flash roms without a custom recovery. And you can't have a custom recovery without an unlocked bootloader.
Whatever you read on another site sounds plain wrong. So proceed with caution.
You can try the thread in general about the Chinese Middleman and see if you can unlock your bootloader for $45. That's your only hope at the moment.
Good luck!
alimzia said:
Hi everyone
Okay so Im going to ask a couple of noob questions here. I have been doing a lot of searching on and off xda but I still have a few doubts about rooting/flasing/unlocking my moto x.
If these questions have been asked before I apologize.
First off, I know that my motoX is from ATT, so it has a locked bootloader, right?
And also that it is a 16GB version so is definitely not DE.
I came across a source where it said I can still root my X with a locked bootloader and that must enable me to flash custom roms. Is this true? (I am a little hesitant about trusting websites other than xda). Why do we even need to unlock the bootloader then? if flashing custom roms is a go with root.
My phone is currently on 4.2.2. How am i supposed to find out if this is the pre or post camera update?
I would really appreciate your replies here as I am holding back from updating to KitKat (I read bootloader cant be unlocked on 4.4). Thanks a lot!
Click to expand...
Click to collapse
There is either a lot of misinformation, or misunderstanding, or both. My guess is a little of both.
What you have read about is using an exploit to root and disable write protection. This is VERY different from actually unlocking the bootloader. These exploits are temporary, and they do not allow you to flash custom roms. They only allow flashing "stock-based, safestrap-compatible" ROMs. While this can be useful, there is no comparison to unlocking the bootloader. Be careful to not confuse the two.
@KJ has pointed you in the right direction. I only wanted to clarify that what you are referring to is "write-protect disable", which again is very different from bootloader unlock. Follow his advice and read up so you can better understand. In the mean-time, don't accept any OTAs until you have decided which option is best for you.
Good Luck :good:
samwathegreat said:
There is either a lot of misinformation, or misunderstanding, or both. My guess is a little of both.
What you have read about is using an exploit to root and disable write protection. This is VERY different from actually unlocking the bootloader. These exploits are temporary, and they do not allow you to flash custom roms. They only allow flashing "stock-based, safestrap-compatible" ROMs. While this can be useful, there is no comparison to unlocking the bootloader. Be careful to not confuse the two.
@KJ has pointed you in the right direction. I only wanted to clarify that what you are referring to is "write-protect disable", which again is very different from bootloader unlock. Follow his advice and read up so you can better understand. In the mean-time, don't accept any OTAs until you have decided which option is best for you.
Good Luck :good:
Click to expand...
Click to collapse
Okay i just need root for using titanium backup. Just one question though before i go on with it. After rooting my device (currently 4.2.2) can i continue to get OTA updates? If so, till what version (4.4 max)?
Again thankyou for your replies. Appreciate it.
alimzia said:
Okay i just need root for using titanium backup. Just one question though before i go on with it. After rooting my device (currently 4.2.2) can i continue to get OTA updates? If so, till what version (4.4 max)?
Again thankyou for your replies. Appreciate it.
Click to expand...
Click to collapse
If you are now on 4.2.2, you're one of the lucky ones..... You can still use the slapmymoto method and get full root with write protection disabled!!
See that section in the one stop shop thread.
?
But you can't go higher than 4.4 to keep all that.
Hey Sam i know this is Off topic but tell me more about Republic wireless and why you like them im thinking of switching from big red
qweesy said:
Hey Sam i know this is Off topic but tell me more about Republic wireless and why you like them im thinking of switching from big red
Click to expand...
Click to collapse
Sent you a PM.
KJ said:
If you are now on 4.2.2, you're one of the lucky ones..... You can still use the slapmymoto method and get full root with write protection disabled!!
See that section in the one stop shop thread.
?
But you can't go higher than 4.4 to keep all that.
Click to expand...
Click to collapse
Okay, after rooting will i be able to receive OTA for 4.4? If so, will it still be write protection disabled?
alimzia said:
Okay, after rooting will i be able to receive OTA for 4.4? If so, will it still be write protection disabled?
Click to expand...
Click to collapse
You would have to read the slapmymoto thread, but I believe you would flash 4.4 with fastboot . And that's it. If you upgrade to 4.4.2 or higher, you will have write protection enabled again.
KJ said:
You would have to read the slapmymoto thread, but I believe you would flash 4.4 with fastboot . And that's it. If you upgrade to 4.4.2 or higher, you will have write protection enabled again.
Click to expand...
Click to collapse
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Isnt there a way to root directly from 4.4? (Wont slapmymoto work?)
alimzia said:
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Click to expand...
Click to collapse
Yes, it is that important. Without write protect disabled, you have to re-root after every reboot. Titanium backup won't work fully because all changes are reverted upon reboot. You will have a heck of a time getting xposed to word if you even can without it disabled.
Yes you can update to 4.4 but not higher. If you use safestrap, you can flash stock based Roms all the way up to 4.4.4. But your bootloader and partition table will remain on 4.4 - this allows you to keep root and write protect disabled.
Be very careful. If you update the bootloader or partition table past 4.4 there is no going back and you will lose the ability to disable write protect permanently.
Basically, without write protect disabled, anything you change gets reverted back upon reboot. You also lose root and have to re-root after every reboot... Not very useful...
alimzia said:
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Isnt there a way to root directly from 4.4? (Wont slapmymoto work?)
Click to expand...
Click to collapse
I'm not a slapmymoto expert, since I never needed it... But I believe you need to start on 4.2.2 with it. Then upgrade. Again... You'd need to read on it.
With write protection disabled you can store to the system then. Definitely needed for Xposed.
Trust me.... There's people with locked bootloaders on 4.4.2 and up that would kill to be able to use slapmymoto. ?
Alright thanks a lot guys. Ive made up my mind, going to go through with it, definitely need xposed!
Oh btw just out of curiosity, does Towel-pie-root work with 4.4?
alimzia said:
Alright thanks a lot guys. Ive made up my mind, going to go through with it, definitely need xposed!
Oh btw just out of curiosity, does Towel-pie-root work with 4.4?
Click to expand...
Click to collapse
I believe so.... But people have trouble with Xposed.
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
Same thing too.... Even IF you get Xposed to work... All undone on a reboot or power down.

New Moto X. can I put a rom on it?

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.

[Q] 5.0 and rooting on locked device

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.

[Q] XT1058 (AT&T) lollipop root

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.

Categories

Resources