Hoping that someone can help me here. I'm currently on 4.4, I tried using Moto X Root Script (Locked Bootloader) and followed all of the prompts, it seemed to image to 4.2.2 but failed the Telnet session. After giving up I realized the phone is still on 4.4 and never flashed to 4.2.2. After several attempts, even trying stillthisguys toolkit (option 11) it's still on 4.4 and now whenever I try to open my security setting I get an error message of "Unfortunately settings has stopped". And now the new OTA update wont take.
Good info in this thread, as well as people who may be able to help.
http://forum.xda-developers.com/showthread.php?t=2664444
Sent from my cell phone telephone....
Do it manually instead?
Related
I rooted my phone via PwnMyMoto when I first got my Moto X. Then the OTA happened, and I held off on it until someone came out with a new root method (RockMyMoto). So I used the Moto X Toolkit to restore my recovery.img from a file titled "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml" and proceeded to take the OTA. However after my phone finished rebooting, I got an error message saying something to the effect of "the software update has failed!". But I checked my version #s and they seemed to be up-to-date with the OTA, and I can't pull any more software updates... and my root was gone. I then ran RockMyMoto and all the steps seemed to go smoothly. Can someone confirm that I have the right version #s?
Current: first attachment
"Status: Update Failed": second attachment
Thanks!
ikarios said:
I rooted my phone via PwnMyMoto when I first got my Moto X. Then the OTA happened, and I held off on it until someone came out with a new root method (RockMyMoto). So I used the Moto X Toolkit to restore my recovery.img from a file titled "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml" and proceeded to take the OTA. However after my phone finished rebooting, I got an error message saying something to the effect of "the software update has failed!". But I checked my version #s and they seemed to be up-to-date with the OTA, and I can't pull any more software updates... and my root was gone. I then ran RockMyMoto and all the steps seemed to go smoothly. Can someone confirm that I have the right version #s?
Current: first attachment
"Status: Update Failed": second attachment
Thanks!
Click to expand...
Click to collapse
idk what flashed and what didn't flash when you tried to take the ota but it doesn't seem to have flashed everything or maybe anything. Your FW is still .51 not .57 which is the ota FW version. restoring recovery might not have been enough because if your /system was changed by any rooted apps then the update would have failed (which is probably why it did). There are several options for how to take the ota, and you would benefit the most from learning how to use fastboot/adb instead of toolkits because then you will know what is done and what hasn't been done. you can also just flash the ota to your phone as well instead of taking through the phone itself. You will lose your data flashing it though. But if you want to take the ota, just flash recovery.img and system.img in fastboot and then put the "ota file" in your /cache folder. Do some reading and you can solve your problems and won't run into close to as many in the future because you will actually know whats going on with the phone instead of using toolkits for the phone.
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?
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?
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
mikestrong19 said:
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
Click to expand...
Click to collapse
Do NOT upgrade until you've read another 24 hours on this board!!!!! I think you should take a second look at your status and see if you misread 4.4.2 as 4.2.2
If I may ask, why not update?
mikestrong19 said:
If I may ask, why not update?
Click to expand...
Click to collapse
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
doitinthedirt said:
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
Click to expand...
Click to collapse
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
mikestrong19 said:
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
Click to expand...
Click to collapse
Wow, what a waste. You could have just flashed the entire STOCK SBF as per the Return to Stock thread, and avoided costing Moto money, and hence raising the prices for everybody... :/
This would have repaired any filesystem corruption/damage, which is the only conceivable thing that might have caused your issue.
Your new one will probably have 4.4.2....which means no write protection disabling.
D'oh!
---------- Post added at 07:17 PM ---------- Previous post was at 07:17 PM ----------
You could have had FULL root on 4.2.2.