Database Develop

Moto X, Intermittent Root

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?

[Q] Debloat D950

Night Everyone,
I just ordered a D950 LG G Flex AT&T, and i havent received it yet, however, i wanted to ask some stuff.
Im not a newbie on the android section, but each hpone acts different, as example, i had a E980 [LG G PRO AT&T] before this one, and wha ti know, is that, removing any carrier system app, using any root explorer, managed to get stuck at the boot screen on the device, saying, Security Error, and then had to reflash it again using the KDZ or the TOT method.
I wanted to ask, if its the same thing with the D950, if i remove the system apps from AT&T, will my device stuck at the Boot Screen with any kind of Security Error message?, since there is not much action on the development of this phone, i wanted to know before start messing with it.
I saw the ROOT method and everything, as soon as i get it i will root it and set TWRP or CWM, however, even on the E980, when the security error appeared, it was almost a 100% rate to flash it with a KDZ to get it working again, and i was curious if this was the same thing with the D950.
Also, i saw the Hyelton guide, its the same one to flash the KDZ, but since the E980 Bootloader was locked if i remember right, and it was needed to be lokified in order to isntall a custom recovery, is the bootloader of the D950 locked? will i face the same issues while trying to remove the system apps, i used to mod my R800X and my E980 ALOT, LIKE 5 flashes at day, both of them, and now i just wanna keep my phone without bloatware, and remove the system apps from AT&T.
So, im open to any idea/suggestion/advices or whatsoever.
p.d. Sorry for my mistakes if any~

Weekly bump!

[Q] Having problems when trying to ROOT Moto G LTE x1040

Hi, I'm relatively new to this forum and I've been trying almost all day to root my phone...
First, I had problems trying to get a working recovery (they just crashed to random colors/or loaded fine and then rebooted like nothing happened). Tried with CWM Recovery but it seems this model is not supported atm, tried with TWRP v2.8.3.0 and also crashes... ATM the only custom recovery that has started without going haywire is TWRP v2.8.0.0 (at least for my phone).
I prefered using 'fastboot boot recovery.img' before 'flash' since it's the first time I'm trying to root a phone. The recovery mode starts okay and I also placed the UPDATE-SuperSU-v2.46.zip in the internal storage before hand. I try to install the .zip file and all goes well, no errors and a blue 'Successful' message. This is where the 'root' procedure fails. Since you can reboot or go home to check other stuff I just tried rebooting the first time and it asked me that I had a SuperSU in the device and that if I wanted to install it to have root. I obviously swiped to install it and it displayed for a split of a second the window from before and just shut down and rebooted...
I tried several other methods to try and root my phone after this failure, but none worked. I checked again if trying this procedure would serve a purpose but I got the same thing always. But since I saw the process so many times I could see for a moment a red line saying something like 'E: failed to copy su binary to /system/bin (...)' but couldn't read more because it was a split of a second there xD. I googled this weird error and I found that my /system is in read only state and not writtable... But to change it to writtable I need root too it seems <_<)
So, any help? I'm sorry if this long text makes someone just look away but I don't really know how to explain my problem in more simple words xD. Any help will be appreciated .
EDIT: Forgot to say that my phone has its bootloader unlocked already and it has USB Debugging enabled.
Moto G LTE x1040
System version (as my phone says) 21.31.1.peregrine.retla.retla.en.01 entcl
Build: KXB21.14-L1.56-1
OS: KitKat 4.4.4

Any help ?
Bump.

Bump. Tried with CF Root by Chainfire but no root gained =/ .

Wait you are in the wrong forum, this is for the second generation search for moto g 2013 all recoveries here are for different device

fburgos said:
Wait you are in the wrong forum, this is for the second generation search for moto g 2013 all recoveries here are for different device
Click to expand...
Click to collapse
I suppose that would be this one then? http://forum.xda-developers.com/moto-g
Thank you for the response, I'm going to repost this in that section, sorry for the mistake >.<

[Q] Wifi not turning on after flashing Lollipop Root

So just to summarize what I've done so far, I have a Moto G (2014) which has been updated to Lollipop through normal means. I started off following this guide: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818/page12
The guide then lead me to this one, as my model is XT1064, a Moto G from Windmobile. I had no issues unlocking my bootloader. http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
With the guide above, after I flashed that file, my wifi would not turn on. Every time I pressed the toggle, it would immediately switch back to off. I then flashed the TWRP Recovery, and used that to finally root my device with SuperSU.
I checked my root, and my device is confirmed to be rooted, but the wifi is still not working. I looked around a little, and found this: http://forum.xda-developers.com/moto-g-2014/general/guide-lollipop-xt1064-north-edition-t2955076
The problem with the guide above is that its for a phone that was kitkat, while my phone is already lollipop. The guide does mention the wireless issue though, so I was thinking of trying out the steps outlined in that guide, also using that file (though that file is for 4.4).
Would this work? Or is the safer bet finding an 5.0.1 stock rom, and flashing back to that?
Edit: I found a link to a 5.0.2 stock rom (which is the version my phone currently is) I think downloading that and using that to fix the modem files is the better thing to do. (link: http://www.filefactory.com/file/53c1pepzp9cp/RETCA_XT1064_5.0.2_LXB22.99-24.2_cid14_CFC.xml.zip)
Thanks for all and any help.

I recommend flashing the stock images, that will almost certainly fix your issue with Wifi.

Help, moto x 2014 stuck in 'MOTO' logo

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.