Related
I hope its a simple mistake on my end of being blind, but i have not been able to locate ( if possible ) a way to root 4.2.2 with already running wpnomoto. I was hoping i could do that and get back on SS and run a ROM. Can someone point me in the right direction?
I was on 4.4 and went back to 4.2.2.....or am i out of luck and have to just settle for rooted stock 4.4?
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
matt99017d said:
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
Click to expand...
Click to collapse
i rooted mine then tried to put 4.4 update, and now it keeps rebooting.. won't stop. ideas?
xpsychox said:
i rooted mine then tried to put 4.4 update, and now it keeps rebooting.. won't stop. ideas?
Click to expand...
Click to collapse
Fastboot erase cache
Sent on my Moto X
flashallthetime said:
Fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
so after I do the root and click install 4.4, shoudl I go to fastboot and clear cache?
xpsychox said:
so after I do the root and click install 4.4, shoudl I go to fastboot and clear cache?
Click to expand...
Click to collapse
You can not flash the 4.4 ota with any form of custom recovery or root , it will bootloop as you found out. So to stop the bootloops you need to delete the ota in the cache folder. What method did you use to root?
Sent on my Moto X
flashallthetime said:
You can not flash the 4.4 ota with any form of custom recovery or root , it will bootloop as you found out. So to stop the bootloops you need to delete the ota in the cache folder. What method did you use to root?
Sent on my Moto X
Click to expand...
Click to collapse
rock my moto.. how do i delete the cache? and i didn't flash any 4.4.. i took the OTA like i was told. per the instructions.
xpsychox said:
rock my moto.. how do i delete the cache?
Click to expand...
Click to collapse
Fastboot erase cache, read the slapmymoto thread, I believe you need to be on 4.2 to root 4.4 kitkat
Sent on my Moto X
flashallthetime said:
Fastboot erase cache, read the slapmymoto thread, I believe you need to be on 4.2 to root 4.4 kitkat
Sent on my Moto X
Click to expand...
Click to collapse
yes, i was on 4.4 and put 4.2.2 back on and gained root access and then went to install 4.4 OTA like the rockmymoto instructions say, and then i get stuck in reboot..
xpsychox said:
yes, i was on 4.4 and put 4.2.2 back on and gained root access and then went to install 4.4 OTA like the rockmymoto instructions say, and then i get stuck in reboot..
Click to expand...
Click to collapse
Read slapmymoto, it says you need to install jar files and then you can take the ota
Try this thread http://forum.xda-developers.com/showthread.php?t=2573177
Sent on my Moto X
flashallthetime said:
Read slapmymoto, it says you need to install jar files and then you can take the ota
Try this thread http://forum.xda-developers.com/showthread.php?t=2573177
Sent on my Moto X
Click to expand...
Click to collapse
i did, i adb pushed rockmymoto, with su, and slapmymoto jar files... but then it says to take OTA 4.4 and that's when it reboots indefinitely...
xpsychox said:
i did, i adb pushed rockmymoto, with su, and slapmymoto jar files... but then it says to take OTA 4.4 and that's when it reboots indefinitely...
Click to expand...
Click to collapse
Wish I could help further but lucky me , I have a unlockable boot loader, ask in the thread that I linked in my previous post
Sent on my Moto X
flashallthetime said:
Wish I could help further but lucky me , I have a unlockable boot loader, ask in the thread that I linked in my previous post
Sent on my Moto X
Click to expand...
Click to collapse
i did, they're all offline.. *sad face* ...lol
matt99017d said:
With me being impatient i ended up going back to 4.4 I know that safestrap does not "work" on 4.4, BUT I was able to install it and flash the eclipse ROM on the stock slot! Booted up and seems to be running like a champ! Id still like to find out in regards to the OP though.
Click to expand...
Click to collapse
Matt, I guess that was what you did:
1. You had a root 4.4.
2. You run MotoWpNoMo to turn off WP permenently (yes, it is permenent).
3. You flashed the unit back to 4.2.2 for a reason (but you should lost the root) .
4. With 4.2.2 and WP off, you wished you can run RockMyMoto to gain the root again (in 4.2.2).
5. But you found that RockMyMoto stopped at the Step 1 since the WP is off or "0". No more Step 2 and 3. So basically, you wasn't able to re-gain the root.
6. So you decided to reflash the unit back to 4.4.
7. Then you installed again the Safestrape.
8. And you found that SS was still working.
But, after you lost your root, how did you make the SS to work? Very interesting!
danhe said:
Matt, I guess that was what you did:
1. You had a root 4.4.
2. You run MotoWpNoMo to turn off WP permenently (yes, it is permenent).
3. You flashed the unit back to 4.2.2 for a reason (but you should lost the root) .
4. With 4.2.2 and WP off, you wished you can run RockMyMoto to gain the root again (in 4.2.2).
5. But you found that RockMyMoto stopped at the Step 1 since the WP is off or "0". No more Step 2 and 3. So basically, you wasn't able to re-gain the root.
6. So you decided to reflash the unit back to 4.4.
7. Then you installed again the Safestrape.
8. And you found that SS was still working.
But, after you lost your root, how did you make the SS to work? Very interesting!
Click to expand...
Click to collapse
Update. SS is sketchy. I tried to use it and its rough around the edges. I think I flashed my phone via RSD today around 6 times..... I ended up back on rooted 4.4
I though I read somewhere that someone had altered the program so it'll root 4.2.2.......
FYI I was able to obtain root on just 4.2.2 using slapmymoto and NOT taking the OTA. I did every step and I was able to install super su and get root access.
That means I have tried SS ON 4.2.2 AND 4.4 I got the same result on both stock Roms. The only thing I tried to flash was ECLIPSE ROM. Maybe that ROM was what was being finiky and NOT SS......MAKE SENSE?
Sent from my XT1058 using XDA Premium 4 mobile app
matt99017d said:
Update. SS is sketchy. I tried to use it and its rough around the edges. I think I flashed my phone via RSD today around 6 times..... I ended up back on rooted 4.4
I though I read somewhere that someone had altered the program so it'll root 4.2.2.......
FYI I was able to obtain root on just 4.2.2 using slapmymoto and NOT taking the OTA. I did every step and I was able to install super su and get root access.
That means I have tried SS ON 4.2.2 AND 4.4 I got the same result on both stock Roms. The only thing I tried to flash was ECLIPSE ROM. Maybe that ROM was what was being finiky and NOT SS......MAKE SENSE?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Matt, thanks for your quick response. I found that I wasn't able to gain the root for a WP-Off unit with 4.2.2 by the "old" SlapMyMoto. jcase released a new version that works perfectly for a WP-Off unit. Thanks, jcase!
I am about to get a Moto X from Verizon and I know it has a locked bootloader
I never dealt with a locked phone in the past and this will be my first moto so I am doing a lot of reading
Correct me if I'm wrong, but I guess the phone will come with 4.2 on it so I'll have two options:
1) Use safestrap and flash 4.4 as a second rom. I am guessing the disadvantage will be loss of disk space for the second rom (maybe other disadvantages, I don't know) but I'll be able to do nandroid backups and flash zips
2) Use the JCase method to root using SlapMyMoto and MotoWpNoMo, etc. (I'll be rooted, but no flashing roms or zips, or nandroid backups)
In that case, which method do you guys really recommend? Do I really need custom roms on this phone since it is almost stock and I can still get xposed to do a lot of the things I'd be interested in with just the root?
If I use the JCase method, do I lose the ability to use safestrap in the future?
Thanks
The moto xs leaving moto maker for Verizon should all be 4.4 at this point. Can't whole heartedly speak to your other questions though.
Sent from my SCH-I925 using Tapatalk
I used to be a flash-o-holic and so far I'm perfectly satisfied with just having root and xposed
sent from my Moto X
I'm rooted, using xposed and gravity box. Very happy with phone. Came from an s3 and have to say I don't miss flashing Roms. Real learning curve for me to root but JCase methods worked perfect and google was my friend through the many steps. Good luck!
Sent from my XT1060 using Tapatalk
SlapMyMoto. You're not gonna want to flash roms on this phone.
Thanks for the replies.
I guess if the phone comes with 4.4 already, I only have the JCase's root option, anyway.
But reading the replies here as well as other threads, I see that most people are pretty content with the stock rom + root + gravitybox/xposed. That's great to know.
I can't wait to get the phone tomorrow
Does Safestrap load 4.4.2 roms now?
aptalca said:
Thanks for the replies.
I guess if the phone comes with 4.4 already, I only have the JCase's root option, anyway.
But reading the replies here as well as other threads, I see that most people are pretty content with the stock rom + root + gravitybox/xposed. That's great to know.
I can't wait to get the phone tomorrow
Click to expand...
Click to collapse
Safestrap works on 4.4 too
But you have to have satestrapped it when you were on the 4.2 bootloader, correct? So if you took an ota or if your phone shipped with 4.4, your bootloader was updated and you can no longer safestrap
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.
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
first, sorry if this has been asked b4, xda/google saeearch didn't find anything.
I need xposed, and I also need root. ( both, root for other things besides xposed.)
just got my moto g2, 4.4.4., and I wanted to know, should I root now, or wait till the 5.0 update and then root? or should I root now and install xposed and not update to 5.0 when it comes out? I read online that there probably will not be xposed fully working on lollipop.
advice anyone?
Root it now, you can aways install the update on your phone, rooted or not.
Hakkinan said:
Root it now, you can aways install the update on your phone, rooted or not.
Click to expand...
Click to collapse
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Kobro said:
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Click to expand...
Click to collapse
You can be rooted and still be fully stock.
Kobro said:
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Click to expand...
Click to collapse
Only if you want to receive it by OTA, besides that, it doesn't matter if you are fully stock or not.
There are some known issues relocking bootloader and returning to stock at all. In most of all cases it works without problems but not in all. If you can´t get back to stock there still will be future options to get lollipop,by sideloading as a zip though recovery for example,ota is not the only way.
I am still on stock 4.4.4 and will wait for the ota,then relock bootloader and root.The Moto G is the first phone I didn´t root at once because it works really good and has farly not as much crapware as others, so I´m able to wait. But I don´t need xposed desperatly, I badly need Adway,Titanium and some others more.
It´s still not clear if xposed will work under lollipop.
So it´s your choice, it´s up to you. You can stay on Kitkat,root and install xposed. And you can update to lollipop later,when/if xposed is running.
Or you can stay stock,wait for ota and root later wich is my way.
Coming from 2 nexus devices, i can't imagine to have a phone without unlocked bootloader, root, custom rom and kernel, that's the point of android for me, customization
Thanks all for your responses! Much appreciated! Now all i have to do is find some way of rooting the thing, vroot failed- first time ever for me
To root Moto G 4.4.4 you have to unlock the bootloader,install custom recovery and flash superSU.zip.
Just follow this guide: http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245
But use the CWM-recovery from here: http://forum.xda-developers.com/moto-g-2014/development/recovery-cwm-philz-touch-6-moto-g-2014-t2896586
or TWRP from here: http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165
xposed not working
Kobro said:
first, sorry if this has been asked b4, xda/google saeearch didn't find anything.
I need xposed, and I also need root. ( both, root for other things besides xposed.)
just got my moto g2, 4.4.4., and I wanted to know, should I root now, or wait till the 5.0 update and then root? or should I root now and install xposed and not update to 5.0 when it comes out? I read online that there probably will not be xposed fully working on lollipop.
advice anyone?
Click to expand...
Click to collapse
plz send a link where i can download xposed for moto g 2014 tx
najm555 said:
plz send a link where i can download xposed for moto g 2014 tx
Click to expand...
Click to collapse
One post above yours.......
http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1