I used the Moto x toolkit to root my phone today but I am beginning to think it did not work. Root checker fails and I can not get any root apps to work. I am back on 4.4 at this point with write protection off. do I just need to run Slap my moto again from that point. Or will I need to downgrade to 4.2.2 and do everything all over again?
rdbutler624 said:
I used the Moto x toolkit to root my phone today but I am beginning to think it did not work. Root checker fails and I can not get any root apps to work. I am back on 4.4 at this point with write protection off. do I just need to run Slap my moto again from that point. Or will I need to downgrade to 4.2.2 and do everything all over again?
Click to expand...
Click to collapse
Personally, I'd try from the beginning again. I think that will yield the best results.
Thanks. That worked perfectly.
Related
Some games I wanted to play doesn't support 4.4 so I flashed back to Camera update 4.2.2 and tried again games worked. So, I decided to stay on 4.2.2.
I tried rockmymoto again and I get is system is not write protected... executing step 3... nothing happens
toolkit even doesn't work. Any methods to root only 4.2.2? at&t user here...
Thanks in advance!
I believe since you disabled write protection you need to root using slapmymoto 4.4
slapped the sh*t out of my X
LeonKnight12 said:
Some games I wanted to play doesn't support 4.4 so I flashed back to Camera update 4.2.2 and tried again games worked. So, I decided to stay on 4.2.2.
I tried rockmymoto again and I get is system is not write protected... executing step 3... nothing happens
toolkit even doesn't work. Any methods to root only 4.2.2? at&t user here...
Thanks in advance!
Click to expand...
Click to collapse
Root in 3 mins or less
Easy..... Just install recovery twrp 2.6.3.1, it works with 4.2.2 and 4.4. This recovery will ask u if u want to root/install superSU.
Then...when the moto x starts goto playtore and update/install superSU.
omias said:
Root in 3 mins or less
Easy..... Just install recovery twrp 2.6.3.1, it works with 4.2.2 and 4.4. This recovery will ask u if u want to root/install superSU.
Then...when the moto x starts goto playtore and update/install superSU.
Click to expand...
Click to collapse
I think you missed where LeonKnight12 says " at&t user here." so can't install TWRP since ATT can't unlock bootloader, unless I missed something.
U right...... Fk at&t !!!
First time I rooted I made back up and updated I forgot to take that back up into PC :banghead:
Sent from my XT1058 using xda app-developers app
lowvolt1 said:
I believe since you disabled write protection you need to root using slapmymoto 4.4
slapped the sh*t out of my X
Click to expand...
Click to collapse
You are right, I never realized slapmymot 4.4 can be used on 4.2.2 to root. I wasted many hours to find solution. I'm glad I rooted 4.2.2 and staying there.
What would be the easiest way to upgrade to kit kat and keep root? Im on verizon, non dev with version 4.2.2. System version is 139.10.53.ghost_verizon.Verizon.en.US. Also using a Mac.
.Grizz. said:
What would be the easiest way to upgrade to kit kat and keep root? Im on verizon, non dev with version 4.2.2. System version is 139.10.53.ghost_verizon.Verizon.en.US. Also using a Mac.
Click to expand...
Click to collapse
Follow the SlapMyMoto thread. Have you disabled write protection with MotoWpNoMo yet? That would be your first step. Then you would reflash 4.2.2 camera update (I used RSD Lite), and then follow the SlapMyMoto thread. It eventually has you take the 4.4 OTA and then run a couple commands afterwards to reactivate root.
nm3210 said:
Follow the SlapMyMoto thread. Have you disabled write protection with MotoWpNoMo yet? That would be your first step. Then you would reflash 4.2.2 camera update (I used RSD Lite), and then follow the SlapMyMoto thread. It eventually has you take the 4.4 OTA and then run a couple commands afterwards to reactivate root.
Click to expand...
Click to collapse
I think I have write protection off, is there a way to check this. Would I still need to flash the camera update, I haven't accepted that update yet.
.Grizz. said:
I think I have write protection off, is there a way to check this. Would I still need to flash the camera update, I haven't accepted that update yet.
Click to expand...
Click to collapse
Code:
adb shell getprop ro.boot.write_protect
If that command returns "0" then you indeed have write protection disabled. If not, head on over to the 'Original Android Development' subforum...
And yes, I think you need to be on the camera update, expect to completely wipe everything. Have you been holding off for a few months?? They've had 4.4 rooted for a couple months now.
Take the camera update. That will put you on .57, then root using rockmymoto, run motowpnomo to disable write protection, then rsdlite back to 4.2.2 camera update .57, then use slapmymoto.
Slapped the sh*t out of my X
if you found me to be helpful, throw me a thumbs up.
Yea ive been holding off, I have no experience using adb so ive been nervous about updating. I was hoping for a one click method like when the moto x first got root.
.Grizz. said:
Yea ive been holding off, I have no experience using adb so ive been nervous about updating. I was hoping for a one click method like when the moto x first got root.
Click to expand...
Click to collapse
I had no adb experience either. Just a want to do it and Google. You can do it. We can help.
Slapped the sh*t out of my X
if you found me to be helpful, throw me a thumbs up.
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
I am getting of very good price on a Moto X from AT&T. I plan to unlock it for use in Canada.
I am wondering if tethering / wifi hotspot will be available ? since the bootloader is not unlockable and even rooting might be impossible depending on what android version it comes with, i'm worried i might be stuck with it. and the wifi hotspot is a must for me.
any help would be appreciated.
thanks,
armrob said:
I am getting of very good price on a Moto X from AT&T. I plan to unlock it for use in Canada.
I am wondering if tethering / wifi hotspot will be available ? since the bootloader is not unlockable and even rooting might be impossible depending on what android version it comes with, i'm worried i might be stuck with it. and the wifi hotspot is a must for me.
any help would be appreciated.
thanks,
Click to expand...
Click to collapse
i don't know what ATT's policy is but if you're on a tiered data plan through VZW, tethering is enabled by default.
If you're running 4.4 you're golden can permanent root and disable write protection using slapmymoto, I did it with the toolkit, you can find it here, send me a pm if you need help. If you're on 4.4.2 you can use towelPie to root and the entitlement hack linked below the towelPie root link. I have a moto x verizon locked boot on 4.4.2 and have towelPie set to root at reboot and works flawlessly, but beware verizon is sending 4.4.4 to phones starting today, I got the update downloaded it just to see which update it was and than quickly opened FX explorer and went to the root cache folder and sent it to outerspace LOL and than went to the root/system/pri-apps folder and deleted the 3c_OTA.apk and 3c_OTA.odex files so it wouldn't ever download it again.. beware each time you rebooot you must redelete those two files since towelPie is only good til the next reboot.
After rooting with towelPie than run the entitlement hack linked below.. the dev has set it up to run at reboot, but it doesn't work currently with the 4.4.2 combo using towelPie, towelPie does run and root automatically at each reboot but the entitlement hack is running at the same time during boot and it tries to do its thing before towelPie has done its thing LOL and fails. the solution is easy just run it manually after each boot. works like a charm.
Edit: I have wrote the developer and he has informed me he is going to fix the entitlement hack by placing a time delay in the app so it gives towelPie time to finish root first, so just keep a lookout for his vers. 1.3 in the entitlement hack thread.
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
doitinthedirt said:
If you're running 4.4 you're golden can permanent root and disable write protection using slapmymoto, I did it with the toolkit, you can find it here, send me a pm if you need help. If you're on 4.4.2 you can use towelPie to root and the entitlement hack linked below the towelPie root link. I have a moto x verizon locked boot on 4.4.2 and have towelPie set to root at reboot and works flawlessly, but beware verizon is sending 4.4.4 to phones starting today, I got the update downloaded it just to see which update it was and than quickly opened FX explorer and went to the root cache folder and sent it to outerspace LOL and than went to the root/system/pri-apps folder and deleted the 3c_OTA.apk and 3c_OTA.odex files so it wouldn't ever download it again.. beware each time you rebooot you must redelete those two files since towelPie is only good til the next reboot.
After rooting with towelPie than run the entitlement hack linked below.. the dev has set it up to run at reboot, but it doesn't work currently with the 4.4.2 combo using towelPie, towelPie does run and root automatically at each reboot but the entitlement hack is running at the same time during boot and it tries to do its thing before towelPie has done its thing LOL and fails. the solution is easy just run it manually after each boot. works like a charm.
Edit: I have wrote the developer and he has informed me he is going to fix the entitlement hack by placing a time delay in the app so it gives towelPie time to finish root first, so just keep a lookout for his vers. 1.3 in the entitlement hack thread.
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
Click to expand...
Click to collapse
OK, perfet. I will try that.
thanks,
armrob said:
OK, perfet. I will try that.
thanks,
Click to expand...
Click to collapse
and by the way you have to check the option to run those apps at reboot they're not automatically set to do it.