Greetings y'all.
I'm rocking a Moto X from the Canadian carrier Rogers and I'm currently running on Android 4.2, with the well... what was latest version for the Moto X, the update that included the camera fixes. I originally rooted my Moto X with the first root method that became available and then recently I used the new RockMyMoto method and I've experienced a peculiar issue and I was hoping someone would be able to offer me some advice.
After rooting my device with RockMyMoto my device had root working perfectly! The applications that rely on root were working perfectly and then one day... something happened. AdAway failed to install the updated host file, so I went into AdAway and it gave me a warning that said root was required.
I found this to be odd... so I exited the application and tried again. The same dialog came up with the same message. I decided to clear the application data and remove AdAway from SuperSU and then reinstalled the application. The problem persisted. I then rebooted my device and tried again and all of a sudden it worked. Now it appears my device is getting intermittent root?
When I turn my phone on I get a notification from Koush's Superuser (I switched from SuperSU, this might be the issue, at least I thought it might be until I switched back to SuperSU) saying that the binary was outdated and I needed an update, so I updated it and it was working so then I decided to try AdAway and... it worked! Success! or so I thought... a few minutes later I tried again and that same dialog came up.
Herumph! I proclaimed. What is this sorcery? Well... it seems my Moto X is getting an intermittent root or something that's only available once the system starts up again.
I tried running RockMyMoto again but that didn't seem to work, mind you I didn't unroot and then reroot.
My question for you is, well... how can I fix this? I don't want to restore my device to stock Android and I also don't want to do some sort of complex trickery because I'm expecting a 4.4 update sometime soon. Anyways, give me a hand guys!
You may not have root after 4.4 anyway... Some say.
Sent from my Moto X cell phone telephone...
Turbocom said:
Greetings y'all.
I'm rocking a Moto X from the Canadian carrier Rogers and I'm currently running on Android 4.2, with the well... what was latest version for the Moto X, the update that included the camera fixes. I originally rooted my Moto X with the first root method that became available and then recently I used the new RockMyMoto method and I've experienced a peculiar issue and I was hoping someone would be able to offer me some advice.
After rooting my device with RockMyMoto my device had root working perfectly! The applications that rely on root were working perfectly and then one day... something happened. AdAway failed to install the updated host file, so I went into AdAway and it gave me a warning that said root was required.
I found this to be odd... so I exited the application and tried again. The same dialog came up with the same message. I decided to clear the application data and remove AdAway from SuperSU and then reinstalled the application. The problem persisted. I then rebooted my device and tried again and all of a sudden it worked. Now it appears my device is getting intermittent root?
When I turn my phone on I get a notification from Koush's Superuser (I switched from SuperSU, this might be the issue, at least I thought it might be until I switched back to SuperSU) saying that the binary was outdated and I needed an update, so I updated it and it was working so then I decided to try AdAway and... it worked! Success! or so I thought... a few minutes later I tried again and that same dialog came up.
Herumph! I proclaimed. What is this sorcery? Well... it seems my Moto X is getting an intermittent root or something that's only available once the system starts up again.
I tried running RockMyMoto again but that didn't seem to work, mind you I didn't unroot and then reroot.
My question for you is, well... how can I fix this? I don't want to restore my device to stock Android and I also don't want to do some sort of complex trickery because I'm expecting a 4.4 update sometime soon. Anyways, give me a hand guys!
Click to expand...
Click to collapse
I presume you're making changes/updates to SuperSU booting into recovery? I'm not sure, but I know I had some problems, lost root briefly when I updated but wasn't in recovery.
Issue resolved! I wasn't applying the update in recovery. Silly me!
The annoyance I saw was I had to reboot into "recovery" to make it have R/W status. That only lasts until the next reboot.
I ran the new pwnnomo or however its spelt, and don't have to worry about that anymore. And also now have safestrap
Sent from my XT1049 using Tapatalk
It is a Rogers Moto X so you can always make life simple and simply unlock the bootloader, no stopping you from enjoying root then even with the 4.4.x update.
Steve-x said:
It is a Rogers Moto X so you can always make life simple and simply unlock the bootloader, no stopping you from enjoying root then even with the 4.4.x update.
Click to expand...
Click to collapse
Are you using 4.4?
Related
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.
UPDATE:
So I'm trying the reddit instructions again, and I'm making more progress than before. Here's where I'm at now: Everything works flawlessly until I get to step 19. I get a message saying "can't create /sys/kernel/uevent_helper: Permission denied" and my phone never reboots. I've browsed through the comments there and everyone else who gets hung up there just repeats previous steps and has it work (which I've tried) or can't remember how they got it to work. I thought I'd reach out here and see if anyone has any suggestions now.
==================================================
Hey everyone, I've been desperately trying to root my Moto X and I just can't get it to work. I ordered mine about a week ago and I've spent the last two days tinkering away with no success. I've rooted my Droid X and my Droid Razr Maxx in the past, so I would say I have a moderate level of understanding, but I'm stumped by this one.
I tried going the easy route using the Moto X Root Script but it continuously failed for me. I would have posted there, but unfortunately since I'm not the most active user, I haven't even made it to the 10 posts mark so I'm not allowed to... so then I took to the internet and used these instructions I found on Reddit to run through RockMyMoto manually followed by MotoWpNoMoto. I successfully achieved root on 4.2.2 and then accepted the OTA to move to KitKat. However, my phone went into a boot loop and I couldn't get it to respond to anything, so I flashed back to 4.2.2 to try running through the process again. Now, I can't get it to root on 4.2.2 anymore, and I'm not sure what's going wrong.
MotoWpNoMoto does tell me that write protection is already removed, but I'm still not getting anywhere. After flashing back to a clean 4.2.2, I try running the first part of SlapMyMoto, and it says it's all successful, but then when I accept the OTA and try to proceed to the second part of it where you push install.sh, I get an error saying "Install script failed! You received a Permission Denied error while attempting to load the install script into the UEVENT_HELPER. This means that root was not successfully obtained." If I try downloading SuperSU from the marketplace, it tells me no SU binary is installed and the SuperSU can't install it.
Does anyone have any ideas on where to go from here?
pianoman674 said:
Hey everyone, I've been desperatley trying to root my Moto X and I just can't get it to work. I ordered mine about a week ago and I've spent the last two days tinkering away with no success. I've rooted my Droid X and my Droid Razr Maxx in the past, so I would say I have a moderate level of understanding, but I'm stumped by this one.
I tried going the easy route using the Moto X Root Script but it continuously failed for me. I would have posted there, but unfortunately since I'm not the most active user, I haven't even made it to the 10 posts mark so I'm not allowed to... so then I took to the internet and used these instructions I found on Reddit to run through RockMyMoto manually followed by MotoWpNoMoto. I successfully achieved root on 4.2.2 and then accepted the OTA to move to KitKat. However, my phone went into a boot loop and I couldn't get it to respond to anything, so I flashed back to 4.2.2 to try running through the process again. Now, I can't get it to root on 4.2.2 anymore, and I'm not sure what's going wrong.
MotoWpNoMoto does tell me that write protection is already removed, but I'm still not getting anywhere. After flashing back to a clean 4.2.2, I try running the first part of SlapMyMoto, and it says it's all successful, but then when I accept the OTA and try to proceed to the second part of it where you push install.sh, I get an error saying "Install script failed! You received a Permission Denied error while attempting to load the install script into the UEVENT_HELPER. This means that root was not successfully obtained." If I try downloading SuperSU from the marketplace, it tells me no SU binary is installed and the SuperSU can't install it.
Does anyone have any ideas on where to go from here?
Click to expand...
Click to collapse
I we to assume you have a consumers version and not the developer edition?
Sent on my Gummy running Lenoto X
flashallthetime said:
I we to assume you have a consumers version and not the developer edition?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
That is correct, sorry I forgot to put that in there.
32 GB Consumer on Verizon, Came with KitKat preinstalled.
As for the Moto X my issue seems isolated. Heres what happened.
1.After successfully gaining root access on 4.4, I notice one big problem. My touchless control wouldn't activate via saying ok google now unless I was google search. I tried everything I could to get it to work (check my recent post) but going back to 4.2.2 to re-slapmymoto was the only option.
2.Flashed to 4.2.2 using RSD Lite. Good news is touchless control worked again. Now the disappointing news...
3.Before slapping I wanted to see what was lost and what stuck after flashing, so I checked my write protection. It came back '0'. Check for root access, it showed su: not found or in other words, not rooted.
4.I was going through the rockmymoto process then hit a snag. After entering the dalvikvm code into puttytel/telnet, it took me straight to step 3 and did absolutely nothing (see picture). I waited for 1min anyways and checked root again...no dice. Adb rebooted the device, reconnected to puttytel and checked again...nothing.
I've searched for about 4hrs straight trying to figure this out. Is there really no way to root again???
Verizon Moto X (currently 4.2.2)
I've been reading that if you downgrade to 4.2.2 then receive OTA update you will brick the phone, be careful.
sent via tapatalk
SPACE-AGE-INC said:
As for the Moto X my issue seems isolated. Heres what happened.
1.After successfully gaining root access on 4.4, I notice one big problem. My touchless control wouldn't activate via saying ok google now unless I was google search. I tried everything I could to get it to work (check my recent post) but going back to 4.2.2 to re-slapmymoto was the only option.
2.Flashed to 4.2.2 using RSD Lite. Good news is touchless control worked again. Now the disappointing news...
3.Before slapping I wanted to see what was lost and what stuck after flashing, so I checked my write protection. It came back '0'. Check for root access, it showed su: not found or in other words, not rooted.
4.I was going through the rockmymoto process then hit a snag. After entering the dalvikvm code into puttytel/telnet, it took me straight to step 3 and did absolutely nothing (see picture). I waited for 1min anyways and checked root again...no dice. Adb rebooted the device, reconnected to puttytel and checked again...nothing.
I've searched for about 4hrs straight trying to figure this out. Is there really no way to root again???
Verizon Moto X (currently 4.2.2)
Click to expand...
Click to collapse
Lol,you won't brick.
To get phone rooted again since you already have write protection turned off, just use slapmymoto instead of rockmymoto. I know you said you were on 4.2.2 but the write protection turned off will not let rockmymoto complete.
Good luck and hope this helps!
eksasol said:
I've been reading that if you downgrade to 4.2.2 then receive OTA update you will brick the phone, be careful.
sent via tapatalk
Click to expand...
Click to collapse
Klown80 said:
Lol,you won't brick.
To get phone rooted again since you already have write protection turned off, just use slapmymoto instead of rockmymoto. I know you said you were on 4.2.2 but the write protection turned off will not let rockmymoto complete.
Good luck and hope this helps!
Click to expand...
Click to collapse
I love you
SPACE-AGE-INC said:
I love you
Click to expand...
Click to collapse
I'm having the exact same problem as OP doing the exact same thing WP 0 etc.. I used SlapMYMoto, after the reboot on step 2 I waited about 5 minutes installed Supersu and same error OP was getting, thoughts?
I'm on Verizon 4.4 never took update since no root (that I know of) woke up a few days ago and saw titanium backup said "unable to gain root access" somehow I lost it? I used jcades way with adb and gained root.. Killed WP. I downloaded root checker and said I had none.. Ideas?
Slapped my Moto
I don't know how root would go away without something on your phone changing...but best place to ask might be in the thread you got the root method from.
xpsychox said:
I'm on Verizon 4.4 never took update since no root (that I know of) woke up a few days ago and saw titanium backup said "unable to gain root access" somehow I lost it? I used jcades way with adb and gained root.. Killed WP. I downloaded root checker and said I had none.. Ideas?
Slapped my Moto
Click to expand...
Click to collapse
Sounds like you either accepted the OTA to 4.4.2, or the 4.4.2 OTA was FORCED on you. Double check your phone under Settings -> About.
With 4.4.2, the vulnerability that allowed MotoWpNoMo to disable write protection with a locked bootloader has been patched, and the ability to safely and successfully downgrade your ROM to 4.4 and below (in order to make use of MotoWpNoMo to disable write protection, and SlapyMyMoto or the like to root) has been taken away too. No new vulnerabilities have been found, nor has a replacement for MotoWpNoMo been found/created/released.
In short, if you have 4.4.2 or above on your X, and you can't unlock the booloader (like Verizon and ATT, unless you are able to make use of the Chinese web site or MiddleMan), you can't disable write protection (so any apps that need to write/save to /system, /system/bin, etc wont work even if you manage to gain root) and while PIE roots 4.4.2 it is "temporary" in that its lost every time you reboot (power off/on). NOTE: the vulnerability used is patched in 4.4.3 so PIE can't be used on 4.4.3 and above.
If by chance you are still on 4.4,I don't know why you would have lost root, but I would consider backing everything up,flashing the stock VZW 4.4 SBF, and following the SlapMyMoto/MotoWpNoMo processes from scratch. When completed find the /System/priv-app/3C_OTA.APK and rename it so your phone doesn't check for future OTA's.
I've got moto ota froze..
Slapped my Moto
xpsychox said:
I've got moto ota froze..
Slapped my Moto
Click to expand...
Click to collapse
And did you double check your version?
Yes..checked before postinf
Slapped my Moto
Screen shot that I just took
Slapped my Moto
xpsychox said:
Screen shot that I just took
Slapped my Moto
Click to expand...
Click to collapse
And you never flashed 4.4.2 and downgraded to 4.4, right?
Yes..I used the jcase method by adb shell before someone made a tool.. With slapmymoto etc.like in said wokebup one day (about a week ago?) And said no more root?
Slapped my Moto
xpsychox said:
Yes..I used the jcase method by adb shell before someone made a tool.. With slapmymoto etc.like in said wokebup one day (about a week ago?) And said no more root?
Slapped my Moto
Click to expand...
Click to collapse
I have no idea then. The only times I've seen root lost is those where update was forced on them. And the only time I've seen root lost when using SlapMyMoto/MotoWPNoMO on reboot was one or two who had 4.4.2 and did a partial down grade to 4.4 and tried Slap/WpNoMo.
When I get home I'll have to try and re root...
Slapped my Moto
I just noticed something strange as I was checking my root and updates status, system updates is now at the bottom of the menu .. used to be top. I rooted with slap and than renamed the 3c_ota.apk and .odex files and I force a system update check and it fails.. so im still good on root but dont know how the menu has changed on my phone. I dont freeze anything dont have titanium thing installed..
This is weird...lol
Slapped my Moto
so i've decided to go ahead and try to re root my moto x. I'm following the instructions i did last time, the slapmymoto (don't need to do motowpnomo cuz i did check the WP, i have 0), pushed rockmymoto but i can't get cydia impactor to connect, keeps saying "signature bugs unavailable" and if i click "usb" drop down and say "scan for device" it say "no device" ideas?
xpsychox said:
so i've decided to go ahead and try to re root my moto x. I'm following the instructions i did last time, the slapmymoto (don't need to do motowpnomo cuz i did check the WP, i have 0), pushed rockmymoto but i can't get cydia impactor to connect, keeps saying "signature bugs unavailable" and if i click "usb" drop down and say "scan for device" it say "no device" ideas?
Click to expand...
Click to collapse
Straight from jcase's slapmymoto thread: "This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4."
Your screenshot shows that you are running 4.4. Additionally, you start off saying you followed instructions for slapmymoto, then you reference rockmymoto... Which one are you using? Or are you using both?
Additionally, you need to be VERY careful if you downgrade. Follow jcase's instructions exactly. There is a big risk of bricking if you make even one innocent mistake.
Please advise...
samwathegreat said:
Straight from jcase's slapmymoto thread: "This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4."
Your screenshot shows that you are running 4.4. Additionally, you start off saying you followed instructions for slapmymoto, then you reference rockmymoto... Which one are you using? Or are you using both?
Additionally, you need to be VERY careful if you downgrade. Follow jcase's instructions exactly. There is a big risk of bricking if you make even one innocent mistake.
Please advise...
Click to expand...
Click to collapse
I was pushing both BC it says to..as I said in first post I did jcases root and had then somehow lost it... So idk how/why just did.. I was hoping I didn't have to downgrade but I had a feeling... But even so it wouldn't explain why I can't use the err.. That program that starts with a c.. Only thing I can remember from last time I think I had to play with my phone setting and put it from USB to photo mode or something like that... Other thing I have thought about is now I am using a cradle point mbr95 modem/router combo. Idk if it blocks it? I know HW to downgrade to 4.2.2 u have to edit one of the lines in the script for the fxz. Done it before... Just don't understand why that program wouldn't work?
Slapped my Moto
Have you tried going into SuperSU > settings tab > unchecking and checking "enable superuser"? I know this sounds like a stupid question but sometimes stating the obvious can help narrow things down. I had this problem on my old Skyrocket before where I would suddenly lose root but be able to gain it back again simply by refreshing this setting in SuperSU.
1ad_m12 said:
Have you tried going into SuperSU > settings tab > unchecking and checking "enable superuser"? I know this sounds like a stupid question but sometimes stating the obvious can help narrow things down. I had this problem on my old Skyrocket before where I would suddenly lose root but be able to gain it back again simply by refreshing this setting in SuperSU.
Click to expand...
Click to collapse
Wtf.... Wow disabled and renamed and it worked.... Never heard if it.. Thanks!!
Slapped my Moto
xpsychox said:
Wtf.... Wow disabled and renamed and it worked.... Never heard if it.. Thanks!!
Slapped my Moto
Click to expand...
Click to collapse
:good: glad to help!
1ad_m12 said:
:good: glad to help!
Click to expand...
Click to collapse
I still can't believe that worked... Lol
Slapped my Moto
Hey, I have a moto X 2014 (xt1097)(brazil), unlocked bootloader,previously had root.
I updated to marshmallow about a month ago and had no problems whatsoever with it aside from the fact that root didn't already work for it.So yesterday I saw a post about a user that flashed the "SuperSU 2.62 v3" and got root, so I did the same but without flashing twrp(I just booted it)... It worked (sort of) but it was having some problem about a super su binary not working(I lost the screenshot).
With that I started searching for a way to make it work correctly, until I saw someone in a post saying that they wiped the phone and re-flashed the root file and it worked correctly, and that was what I did.. with one little difference I flashed the latest superSU file released (SuperSU-v2.64),but it didn't work, it initiated but there were notifications all the time about something not working(a lot of things).
With that in mind I started the same process I had done to flash the first superSU,wiped the data and cache, turned it on so that I could enable debug mode to start flashing the superSU but this time the phone didn't get out of the big `M` (powered by android) logo.
I seached a fix for it, on other posts people said that wiping everything(except system) and rebooting worked for them, but for me it didn't.
So I need help with this, if anyone can help please do so, thank you.
UPDATE: I just remembered that before that I didn't use the "unroot" function in the superSU version that didn't work, so I think that I got bootloop because of that, but I still don't know what to do.