Related
Hello all.
Ok, I have read all the posts/threads for rooting and am still confused as each thread links to another which links to another, which changes another ,etc. Need proper organization of threads it looks like.
Anyway, I just received the GSM Unlocked MOTO X (NOT DEV ED.) for TMO or ATT.
How do I root? Again, I have read the threads and am terribly confused. I have the 4.2.2 software and have NOT updated to any OTA.
Can someone clearly highlight the steps I should be taking?
Am not a noob and currently own N5 and S4 Dev Edition.
Thanks!
ditto
I am also confused, do I download the pwnmymoto for the att or tmobile version? Just got my moto x today.
markwebb said:
Hello all.
Ok, I have read all the posts/threads for rooting and am still confused as each thread links to another which links to another, which changes another ,etc. Need proper organization of threads it looks like.
Anyway, I just received the GSM Unlocked MOTO X (NOT DEV ED.) for TMO or ATT.
How do I root? Again, I have read the threads and am terribly confused. I have the 4.2.2 software and have NOT updated to any OTA.
Can someone clearly highlight the steps I should be taking?
Am not a noob and currently own N5 and S4 Dev Edition.
Thanks!
Click to expand...
Click to collapse
RockMyMoto
then, MotoWpNoMo to keep root as w/o you have a "temp" root, or tethered, if that is the correct term. AKA, reboots/shutdowns can trip it back to stock w/o root.
so are these phones the x1053 or x1058?
buschris said:
so are these phones the x1053 or x1058?
Click to expand...
Click to collapse
X1053
Sent from my XT1053 using xda app-developers app
TKTAB911 said:
RockMyMoto
then, MotoWpNoMo to keep root as w/o you have a "temp" root, or tethered, if that is the correct term. AKA, reboots/shutdowns can trip it back to stock w/o root.
Click to expand...
Click to collapse
Thanks... then can I take the ota to kit Kat 4.4 or will I lose root? I did unlock bootloader BTW.
Sent from my XT1053 using xda app-developers app
markwebb said:
Thanks... then can I take the ota to kit Kat 4.4 or will I lose root? I did unlock bootloader BTW.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
I am thinking of unlocking mine as well, and I am on 4.4 already, just got the phone today.
Not sure if I should unlock, it will be my daughters phone and I'll probably need the warranty
markwebb said:
Thanks... then can I take the ota to kit Kat 4.4 or will I lose root? I did unlock bootloader BTW.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
Since you've unlocked the bootloader, follow the root directions for the dev edition. What you're doing is wholly unnecessary.
Unlock bootloader, download latest CWMR or TWRP and SuperSu, then fastboot (or mfastboot) flash recovery, boot into recovery, adb push supersu.zip /sdcard, flash in recovery. Done.
buschris said:
I am thinking of unlocking mine as well, and I am on 4.4 already, just got the phone today.
Not sure if I should unlock, it will be my daughters phone and I'll probably need the warranty
Click to expand...
Click to collapse
I'd start with root without unlocking.
nhizzat said:
Since you've unlocked the bootloader, follow the root directions for the dev edition. What you're doing is wholly unnecessary.
Unlock bootloader, download latest CWMR or TWRP and SuperSu, then fastboot (or mfastboot) flash recovery, boot into recovery, adb push supersu.zip /sdcard, flash in recovery. Done.
Click to expand...
Click to collapse
Thanks..that is what I was looking for. So, should I update to OTA first since I am unlocked, or root now per dev edition instruction? If so, then how would I take the OTA if I am on custom recovery? Is there a zip of the OTA?
Thanks again!
markwebb said:
Thanks..that is what I was looking for. So, should I update to OTA first since I am unlocked, or root now per dev edition instruction? If so, then how would I take the OTA if I am on custom recovery? Is there a zip of the OTA?
Thanks again!
Click to expand...
Click to collapse
You should take the 4.4 OTA first. In order to take the OTA you need to have stock recovery. Once you take the OTA then you can flash a customer recovery and flash a super user app through it.
Sent from my Moto X on KitKat
Dark9781 said:
You should take the 4.4 OTA first. In order to take the OTA you need to have stock recovery. Once you take the OTA then you can flash a customer recovery and flash a super user app through it.
Sent from my Moto X on KitKat
Click to expand...
Click to collapse
From current experiences with other devices, that is exactly what I did. I am now updated to 4.4, with custom recovery and root!
Thanks guys...shame this isn't in an updated simple "how to" thread
markwebb said:
Thanks guys...shame this isn't in an updated simple "how to" thread
Click to expand...
Click to collapse
It isn't difficult at all. People seem to be easily confused and make things more complicated than necessary.
markwebb said:
From current experiences with other devices, that is exactly what I did. I am now updated to 4.4, with custom recovery and root!
Thanks guys...shame this isn't in an updated simple "how to" thread
Click to expand...
Click to collapse
Rooting with an unlocked bootloader is perhaps the easiest thing to do. You know this from past experience so why would it be any different with the Moto X?
The real challenge is when you want to root with a locked bootloader (and even that is becoming gradually easier).
esskayy said:
Rooting with an unlocked bootloader is perhaps the easiest thing to do. You know this from past experience so why would it be any different with the Moto X?
The real challenge is when you want to root with a locked bootloader (and even that is becoming gradually easier).
Click to expand...
Click to collapse
Correct.
But i began the process with a locked bootloader and getting to the answer/correct path was a challenge in these threads compared to other threads.
So I took the plunge and unlocked.
Sent from my Nexus 5 using xda app-developers app
I want to root again but am on 4.4.2 and can't do it.
Sent from my XT1060 using XDA Premium 4 mobile app
That's been talked about very often. One of the hottest Moto x topics.
You can search xda or Google for a lot of info. A lot!
http://www.google.ca/search?hl=en-C...rade+4.4.2+to+4.2.2+locked+bootloader&spell=1
I'll tell you this. If you don't do it exactly right, or take an ota anytime after, you may brick your phone. So make sure you know what what you are doing before you do it.
Sent from my cell phone telephone....
If possible just unlock your boot loader and fastboot flash what you need to root. I read on here earlier some Chinese dude had unlock codes. Not sure how legit it is but unlocking your bootloader is the safest way to root I'm my opinion
Moto X developer edition
SymbioticGenius said:
If possible just unlock your boot loader and fastboot flash what you need. I read on here earlier some Chinese dude had unlock codes. Not sure how legit it is but unlocking your bootloader is the safest way I'm my opinion
Moto X developer edition
Click to expand...
Click to collapse
So far, it's been 100% legit as far as the codes working to unlock devices. The codes could stop anytime since no one knows where they are actually getting them from.
SymbioticGenius said:
If possible just unlock your boot loader and fastboot flash what you need. I read on here earlier some Chinese dude had unlock codes. Not sure how legit it is but unlocking your bootloader is the safest way I'm my opinion
Moto X developer edition
Click to expand...
Click to collapse
Even with an unlocked boot loader, you can not downgrade the boot loader from 4.4.2. No matter what version of the X you own, once you are on 4.4.2, you are stuck on 4.4.2.
Mr. Orange 645 said:
Even with an unlocked boot loader, you can not downgrade the boot loader from 4.4.2. No matter what version of the X you own, once you are on 4.4.2, you are stuck on 4.4.2.
Click to expand...
Click to collapse
Who needs to downgrade when all he was asking for was root? An unlocked bootloader will allow for you to flash a custom recovery and flash root or ROMs. If the the OPs only intention is downgrading the unlock codes are probably his best bet.
Mr. Orange 645 said:
Even with an unlocked boot loader, you can not downgrade the boot loader from 4.4.2. No matter what version of the X you own, once you are on 4.4.2, you are stuck on 4.4.2.
Click to expand...
Click to collapse
Yeah, but if you read the op you'd see the only reason he wants to go back is root. Thus I gave him a realistic way to achieve his goal.
Moto X developer edition
meber said:
Who needs to downgrade when all he was asking for was root? An unlocked bootloader will allow for you to flash a custom recovery and flash root or ROMs. If the the OPs only intention is downgrading the unlock codes are probably his best bet.
Click to expand...
Click to collapse
For one I was responding to another poster who incorrectly told him he could just downgrade if he unlocked his boot loader. I wasn't replying to the OP, as evidenced by the fact I quoted the poster above me.
Secondly, with a locked boot loader, the only way to root was to downgrade to 4.2.2, use an exploit to root, then upgrade to 4.4. There is currently no way to root 4.4.2 without unlocking the boot loader.
---------- Post added at 12:34 PM ---------- Previous post was at 12:27 PM ----------
SymbioticGenius said:
Yeah, but if you read the op you'd see the only reason he wants to go back is root. Thus I gave him a realistic way to achieve his goal.
Moto X developer edition
Click to expand...
Click to collapse
That is the reason but his specific request was to downgrade from 4.4.2 to 4.2.2. When you said unlock and fast boot flash what you need, in the context of the thread it came across as you were saying he could downgrade with an unlocked boot loader. If the OP is new to Android, rooting, or the Moto X, then he could easily misinterpret what you were saying and end up bricking his device. You have to be clear when talking about rooting and unlocking.
If I misinterpreted your post, others easily have as well. However, the OP should have taken about ten seconds and searched for his answer before starting another thread that just muddies an already confusing issue.
Nothing I post is intended to hurt your feelings or call into question your knowledge. I just don't want people to break the devices they spend hard earned money on.
@ Orange, I didn't mean to offend you if it came off that way, and you didn't offend me either.
Nonetheless I don't really see how my post could be misunderstood. The original post clearly says he wants root. I gave him a straightforward way to achieve that. Unless someone only read the title skipped everything else and read my post, which would be just silly
I did however add two words (to root) to my first post. Just in case
Moto X developer edition
SymbioticGenius said:
@ Orange, I didn't mean to offend you if it came off that way, and you didn't offend me either.
Nonetheless I don't really see how my post could be misunderstood. The original post clearly says he wants root. I gave him a straightforward way to achieve that. Unless someone only read the title skipped everything else and read my post, which would be just silly
I did however add two words (to root) to my first post. Just in case
Moto X developer edition
Click to expand...
Click to collapse
No offense taken.
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 just got this phone and unfortunately didn't get the developer edition. I am using the "Towel Pie Root" made by a developer here on XDA and got temporary root. So under this temporary root is it possible to flash a recovery and if it is, is it possible to then flash ROMs with the recovery? Thanks in advance!
Sent from my XT1058 using XDA Premium 4 mobile app
You have to have a unlocked bootloader to use twrp. If you are locked down look into safestrap.
Travisdroidx2 said:
You have to have a unlocked bootloader to use twrp. If you are locked down look into safestrap.
Click to expand...
Click to collapse
Alright thanks. I'll look into that tomorrow.
Sent from my XT1058 using XDA Premium 4 mobile app
procitysam said:
I just got this phone and unfortunately didn't get the developer edition. I am using the "Towel Pie Root" made by a developer here on XDA and got temporary root. So under this temporary root is it possible to flash a recovery and if it is, is it possible to then flash ROMs with the recovery? Thanks in advance!
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When the bootloader on the X is locked, you can only flash components which are signed by Motorola's "digital key" as being for your phone. So you can only flash an entire rom, or parts of it, which are for your phone.
This prevents using 3rd party or custom recoveries, custom roms, etc. as they are not signed by Motorola's key.
PIE, TowelRoot, TowelPieRoot, SlapMyMoto, RockMyMoto, MotoWPNoMo, etc. does NOT allow for bypassing this.
Only unlocking your bootloader will allow you to use parts not signed by moto, like custom recoveries, 3rd party roms, etc.
My thought is that you are on 4.4.2 because you have used TowelPieRoot. Is that correct?
@Travisdroidx2 suggested SafeStrap, but to install/use Safestrap you need to be rooted and have write protection disabled. Unfortunately, on the Moto X, the MotoWpNoMo exploit was used to disable write protection if you can't unlock your bootloader, BUT the vulnerability in the bootloader that was exploited by MotoWpNoMo has been patched in 4.4.2 ROM and above. So you can't use it on 4.4.2, 4.4.3, and 4.4.4. You can't downgrade the bootloader either. In fact, once on 4.4.2 or above, NEVER try to downgrade your ROM, as you could brick your phone!!
i.e. If you have a locked bootloader and are on 4.4.2 or above, you can't disable write protection, and you can't downgrade your phone safely. If you do try, you can't downgrade Motoboot.img (bootloader and a couple of other things), and GPT.BIN (partition table). which can brick your phone and cause other problems.
However, if you were on 4.4 (aka 4.4.0) with its vulnerable bootloader, you could use SlapMyMoto with MotoWpNoMo to root and disable write protection, then use Safestrap to install 4.4.2 and 4.4.4, and retain root and write protection disable.
KidJoe said:
When the bootloader on the X is locked, you can only flash components which are signed by Motorola's "digital key" as being for your phone. So you can only flash an entire rom, or parts of it, which are for your phone.
This prevents using 3rd party or custom recoveries, custom roms, etc. as they are not signed by Motorola's key.
PIE, TowelRoot, TowelPieRoot, SlapMyMoto, RockMyMoto, MotoWPNoMo, etc. does NOT allow for bypassing this.
Only unlocking your bootloader will allow you to use parts not signed by moto, like custom recoveries, 3rd party roms, etc.
My thought is that you are on 4.4.2 because you have used TowelPieRoot. Is that correct?
@Travisdroidx2 suggested SafeStrap, but to install/use Safestrap you need to be rooted and have write protection disabled. Unfortunately, on the Moto X, the MotoWpNoMo exploit was used to disable write protection if you can't unlock your bootloader, BUT the vulnerability in the bootloader that was exploited by MotoWpNoMo has been patched in 4.4.2 ROM and above. So you can't use it on 4.4.2, 4.4.3, and 4.4.4. You can't downgrade the bootloader either. In fact, once on 4.4.2 or above, NEVER try to downgrade your ROM, as you could brick your phone!!
i.e. If you have a locked bootloader and are on 4.4.2 or above, you can't disable write protection, and you can't downgrade your phone safely. If you do try, you can't downgrade Motoboot.img (bootloader and a couple of other things), and GPT.BIN (partition table). which can brick your phone and cause other problems.
However, if you were on 4.4 (aka 4.4.0) with its vulnerable bootloader, you could use SlapMyMoto with MotoWpNoMo to root and disable write protection, then use Safestrap to install 4.4.2 and 4.4.4, and retain root and write protection disable.
Click to expand...
Click to collapse
Yes that's correct that I'm on 4.4.2. Thank you for clearing that up, everything I looked at was confusing. So my last question is Towel Pie Root can only be used for root access apps?
Sent from my XT1058 using XDA Premium 4 mobile app
procitysam said:
Yes that's correct that I'm on 4.4.2. Thank you for clearing that up, everything I looked at was confusing. So my last question is Towel Pie Root can only be used for root access apps?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sort of.
TowelPieRoot provides READ access to protected folders that you can't touch/see without root permissions. So apps like Root Explorer and the like which don't need to WRITE files in /system and such will be fine.
Apps like AdFree, Xposed, and other things that need to write in /system either wont install, or will need an alternate install process. (Xposed does have a way to install without write permissions).
And of course, any changes done to the write protected folders will be lost at power off/on or "hard boot." This poses a challenge for many when installing Xposed, as they do a normal reboot after install which is a "hard boot" and they lose root and xposed and have to start all over. There is a "soft boot" option that can be used when installing xposed.
Note: I have an unlocked bootloader so I've only read about the challenges of installing Xposed and others who use PIE, Towel ROot, and TowelPieRoot and still have write protection enabled. So you'll really want to read those threads that deal with the ROOT app you want to use, or the root method you are using, to find the details of what can/can't be done.
KidJoe said:
Sort of.
TowelPieRoot provides READ access to protected folders that you can't touch/see without root permissions. So apps like Root Explorer and the like which don't need to WRITE files in /system and such will be fine.
Apps like AdFree, Xposed, and other things that need to write in /system either wont install, or will need an alternate install process. (Xposed does have a way to install without write permissions).
And of course, any changes done to the write protected folders will be lost at power off/on or "hard boot." This poses a challenge for many when installing Xposed, as they do a normal reboot after install which is a "hard boot" and they lose root and xposed and have to start all over. There is a "soft boot" option that can be used when installing xposed.
Note: I have an unlocked bootloader so I've only read about the challenges of installing Xposed and others who use PIE, Towel ROot, and TowelPieRoot and still have write protection enabled. So you'll really want to read those threads that deal with the ROOT app you want to use, or the root method you are using, to find the details of what can/can't be done.
Click to expand...
Click to collapse
Awesome explanation thanks. The app has the option to re-root after a reboot so that shouldn't be a problem. Thanks so much for helping!
Sent from my XT1058 using XDA Premium 4 mobile app
procitysam said:
Awesome explanation thanks. The app has the option to re-root after a reboot so that shouldn't be a problem. Thanks so much for helping!
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure, re-root after reboot... BUT any changes you made to the write protected folders while would still be lost and have to be redone after a power off/on or "hard boot".
KidJoe said:
When the bootloader on the X is locked, you can only flash components which are signed by Motorola's "digital key" as being for your phone. So you can only flash an entire rom, or parts of it, which are for your phone.
This prevents using 3rd party or custom recoveries, custom roms, etc. as they are not signed by Motorola's key.
PIE, TowelRoot, TowelPieRoot, SlapMyMoto, RockMyMoto, MotoWPNoMo, etc. does NOT allow for bypassing this.
Only unlocking your bootloader will allow you to use parts not signed by moto, like custom recoveries, 3rd party roms, etc.
My thought is that you are on 4.4.2 because you have used TowelPieRoot. Is that correct?
@Travisdroidx2 suggested SafeStrap, but to install/use Safestrap you need to be rooted and have write protection disabled. Unfortunately, on the Moto X, the MotoWpNoMo exploit was used to disable write protection if you can't unlock your bootloader, BUT the vulnerability in the bootloader that was exploited by MotoWpNoMo has been patched in 4.4.2 ROM and above. So you can't use it on 4.4.2, 4.4.3, and 4.4.4. You can't downgrade the bootloader either. In fact, once on 4.4.2 or above, NEVER try to downgrade your ROM, as you could brick your phone!!
i.e. If you have a locked bootloader and are on 4.4.2 or above, you can't disable write protection, and you can't downgrade your phone safely. If you do try, you can't downgrade Motoboot.img (bootloader and a couple of other things), and GPT.BIN (partition table). which can brick your phone and cause other problems.
However, if you were on 4.4 (aka 4.4.0) with its vulnerable bootloader, you could use SlapMyMoto with MotoWpNoMo to root and disable write protection, then use Safestrap to install 4.4.2 and 4.4.4, and retain root and write protection disable.
Click to expand...
Click to collapse
Thanks for the info. I have a Dev edition so never used safestrap myself. I just know it was a option for locked down phones. Thanks for the clarification.
When using the Towel Pie Root app, do you need Superuser installed as well? And if so do you or don't you need the su binary installed?
Title says it all. Will I get the new radio/bootloader when CM12 gets updated? The update includes the ability to use the 700Mhz TMobile freq as well as VoLTE.
They normally do, yes.
Custom ROMs do not provide bootloaders
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
I didn't think so. I went ahead and restored back to stock and updated to 5.1 from the google factory images. I'll probably go back to CM when they update to 5.1.
Thanks!
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
Cm does
Sent from my Nexus 6 using XDA Free mobile app
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Tasssadar said:
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Click to expand...
Click to collapse
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
rootSU said:
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
Click to expand...
Click to collapse
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. "Tend" . This one piqued my interest as it was asking about the bootloaders though.
rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
randy6644 said:
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
Click to expand...
Click to collapse
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
rootSU said:
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
Click to expand...
Click to collapse
relocking bootloader leads to a bootloop , and it's nothing like a real hard brick like mine. So sad~
rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Most bricks are happening because CM includes the bootloader and you cannot downgrade bootlodaers, if you tried in fastboot it will stop you from doing this. CM uses an old way of accomplishing this which force downgrades the bootloader and messes up the partitioning, resulting in a brick.
I have seen 3 or 4 cases in person from this, and those users never relocked their boot loader like you described.
Circaflex said:
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Click to expand...
Click to collapse
Great. Got it. At some point in the future, cm "will" upgrade the bootloader but right now they will refuse to flash.
I'm safe. Haven't used cm since cm6.