Related
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 rooted wife's Nexus 7 sometime in last year (or so) so that she could play movies/tv-shows from an attached flash drive (using Stickmount).
First off, i don't need the root for anything else.. is rooting still required to be able to access/play video from an attached flash drive (without copying it first from the flashdrive to your nexus)?
If still needed then I would like to preserve the root.
She informs me that there is a notification for pending software 4.4.2 update ready to install (apparently been there for months) . Is there an easy way to install the OTA 4.4.2 update and preserve my root? So i dont have to re-root the device?
Thanks in advance to any that are kind enough to offer suggestions!
Well i got impatient and loaded TWRP manager but miss understood the part about requiring superSU Pro to retain root and wound up installing the update and wiping out root access.
What i didn't realize (or remember) is that the device is not re-locked so can re-root the device using wugfreshs nexus root toolkit (took couple minutes) without losing anything.
So wife is happy camper
hinsdale1 said:
Well i got impatient and loaded TWRP manager but miss understood the part about requiring superSU Pro to retain root and wound up installing the update and wiping out root access.
What i didn't realize (or remember) is that the device is not re-locked so can re-root the device using wugfreshs nexus root toolkit (took couple minutes) without losing anything.
So wife is happy camper
Click to expand...
Click to collapse
You didn't need the toolkit. All you needed was the super su zip and flash it in recovery...
Sent from my Nexus 5
Pirateghost said:
You didn't need the toolkit. All you needed was the super su zip and flash it in recovery...
Sent from my Nexus 5
Click to expand...
Click to collapse
For future i would like to learn this (sorry i only work on her nexus for a few minutes a year so very unfamiliar with the hacks)
I found the newest super su zip relatively easily.. but the "flash it in recovery" part needs a little more step-by-step instruction for the unbaptized.
Thanks for the help.
hinsdale1 said:
For future i would like to learn this (sorry i only work on her nexus for a few minutes a year so very unfamiliar with the hacks)
I found the newest super su zip relatively easily.. but the "flash it in recovery" part needs a little more step-by-step instruction for the unbaptized.
Thanks for the help.
Click to expand...
Click to collapse
You should spend a few minutes reading some of the sticky threads we have around here. Everything has already been laid out for you in them
Sent from my Nexus 5
Had anybody successfully rooted 6.0 yet, and if so, can you point me to the right place. Just got 2 of these devices for my son and daughter, and my son likes his rooted, but it updated to marshmallow the first night he had it. Have found several guides to rooting 5.1.1, but don't want to risk since muy wife would kill me if I mess it up.
Sent from my LG-H901 using Tapatalk
Check this out.
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
I got success, but I used SuperSU 2.46.
Basically, you do the following steps:
1. Backup your data
2. Copy necessary files onto memory card.
3. Boot into bootloader and unlock it.
4. Boot into bootloader reboot into TWRP and install SuperSU
5. Update the binary and restore data
That's it.
calexchelse said:
Had anybody successfully rooted 6.0 yet, and if so, can you point me to the right place. Just got 2 of these devices for my son and daughter, and my son likes his rooted, but it updated to marshmallow the first night he had it. Have found several guides to rooting 5.1.1, but don't want to risk since muy wife would kill me if I mess it up.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
there's been root since day 1 follow this guide or the link @mingkee posted
T-Mobile H20i MM Root Steps.
SKIP : Steps 4, 5 and 6 if you are in MM already
Hey Everyone.
This is my first ever post to XDA forums, so pardon me if do something wrong
I recently got a Nexus 6 XT1103 (T Mobile). My software version is still at LYZ28N and whenever I try to update it, it says "Your System is up to date". I check the TMobile's website and the latest update is MMB29K. I have no idea why am I not getting the updates. Further information my Nexus 6 is not rooted or modified in anyway. I am using this unlocked cell phone in Pakistan. I have done some search but I couldn't find some reliable method to update without incurring any major risk.
I'd highly appreciate if someone can guide this noob Needless to say I am a total noob when it comes to advanced android stuff.
PS: Again apologies if I said something wrong.
Regards,
Ahmed
If you have the bandwidth available, download a factory image from Google and update your device manually using the instructions given or the instructions in the Nexus 6 all-in-one guide in the general subforum. You may not be getting updates as you have a North American device and are using it in Asia.
Strephon Alkhalikoi said:
If you have the bandwidth available, download a factory image from Google and update your device manually using the instructions given or the instructions in the Nexus 6 all-in-one guide in the general subforum. You may not be getting updates as you have a North American device and are using it in Asia.
Click to expand...
Click to collapse
As per T Mobile's website the latest version is MMB29K, from the link you posted should I straight away download the image for this MMB29K?
ahmedmateen said:
As per T Mobile's website the latest version is MMB29K, from the link you posted should I straight away download the image for this MMB29K?
Click to expand...
Click to collapse
No, MMB29K is several security updates ago (december I believe). Download and install the last one on the list (as of today MMB29X).
Didgeridoohan said:
No, MMB29K is several security updates ago (december I believe). Download and install the last one on the list (as of today MMB29X).
Click to expand...
Click to collapse
This is the first time ever I am playing with this stuff (nervous as hell coz I dont want to brick my fone, had to save for months to buy this one), I have searched sideloading, it seems a bit easier or noob friendly then this flashing. Whats your advice on it?
This is XDA, so a majority of the folks will recommend flashing the factory images
Since this is the first time you are considering this, I understand - it looks scary. Honestly, it is really not that hard to do - I never wait for OTA anymore - just download the factory images and flash it as soon as it is released. (takes me all of 5 minutes or so after the download) - but I've been doing this every month.
Just remember that Unlocking (or relocking) the bootloader will wipe your data. So I unlocked the bootloader the day I got the phone, and just leave it unlocked.
Flashing the factory images is pretty straightforward - read the first post at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 - and use Method 2 (in step 5) - don't flash the userdata.img if you want to retain your user data, and don't perform the "Wipe data/factory data reset" step towards the end of first post.
Read that first post a few times, and make sure you understand it before you proceed.
The hardest part is getting your fastboot and drivers set up. Before attempting any fastboot commands, you should test and make sure your fastboot is working - Connect your phone to your PC, and then, in a command prompt window, type "fastboot devices" (without quotes) and hit enter. Make sure you get back a serial #. If it tells you device not found or not connected or something like that, don't try flashing anything. Get that sorted out first.
Great advice from jj14.
Sideloading is gonna take longer time than doing a straight up flash of the latest factory image. You'd have to sideload every single incremental OTA.
First thing to do is to unlock your bootloader and letting it stay unlocked. You can fix almost everything that could happen to your phone if your bootloader is unlocked. And, as stated previously, it will wipe your phone.
jj14 said:
This is XDA, so a majority of the folks will recommend flashing the factory images
Since this is the first time you are considering this, I understand - it looks scary. Honestly, it is really not that hard to do - I never wait for OTA anymore - just download the factory images and flash it as soon as it is released. (takes me all of 5 minutes or so after the download) - but I've been doing this every month.
Just remember that Unlocking (or relocking) the bootloader will wipe your data. So I unlocked the bootloader the day I got the phone, and just leave it unlocked.
Flashing the factory images is pretty straightforward - read the first post at - and use Method 2 (in step 5) - don't flash the userdata.img if you want to retain your user data, and don't perform the "Wipe data/factory data reset" step towards the end of first post.
Read that first post a few times, and make sure you understand it before you proceed.
The hardest part is getting your fastboot and drivers set up. Before attempting any fastboot commands, you should test and make sure your fastboot is working - Connect your phone to your PC, and then, in a command prompt window, type "fastboot devices" (without quotes) and hit enter. Make sure you get back a serial #. If it tells you device not found or not connected or something like that, don't try flashing anything. Get that sorted out first.
Click to expand...
Click to collapse
Thank you, I followed some tutorial for side loading the update. After the first update the OTA's starting working again, as of this moment installing Feb's patch I have to say the guys at XDA rock, extremely helpful :good:
Didgeridoohan said:
Great advice from jj14.
Sideloading is gonna take longer time than doing a straight up flash of the latest factory image. You'd have to sideload every single incremental OTA.
First thing to do is to unlock your bootloader and letting it stay unlocked. You can fix almost everything that could happen to your phone if your bootloader is unlocked. And, as stated previously, it will wipe your phone.
Click to expand...
Click to collapse
It may take longer but for a noob like me it just did the trick
Awesome! You just needed that first push I guess.