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!
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.
My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
...
Sent from my XT1058 using XDA Premium 4 mobile app
kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.
I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app
Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)
Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app
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
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Vebr137 said:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Click to expand...
Click to collapse
Have you tried using RSDLite to flash the original ROM?
Vebr137 said:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Click to expand...
Click to collapse
It has probably been rooted using an exploit. Be VERY careful or you could lose root forever.
Is the bootloader unlocked? Let me know and I may be able to help you with clear and precise steps.
Vebr137 said:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
Click to expand...
Click to collapse
If you erase..are you aware that you will loose Root permanently.?
BUT..If you use the (jcase) RockMyMoto & SlapMyMoto, you can retain Root with these two exploits, Since your device is still on Jelly Bean OS..BUT..to do so, one must be experienced with adb & RSDLite..and you can retain Root over into 4.4_
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
dier325 said:
Have you tried using RSDLite to flash the original ROM?
Click to expand...
Click to collapse
I did. Its just rebooting and its all.
samwathegreat said:
It has probably been rooted using an exploit. Be VERY careful or you could lose root forever.
Is the bootloader unlocked? Let me know and I may be able to help you with clear and precise steps.
Click to expand...
Click to collapse
Bootloader is locked. Thanks)
NWKENT said:
If you erase..are you aware that you will loose Root permanently.?
BUT..If you use the (jcase) RockMyMoto & SlapMyMoto, you can retain Root with these two exploits, Since your device is still on Jelly Bean OS..BUT..to do so, one must be experienced with adb & RSDLite..and you can retain Root over into 4.4_
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Click to expand...
Click to collapse
Root for this phone is not that important. Im tired that every time I want update a program or install a new one I need to delete google profile from the phone, reboot it and again use google profile. Otherwise nothing is installing.
Vebr137 said:
Root for this phone is not that important. Im tired that every time I want update a program or install a new one I need to delete google profile from the phone, reboot it and again use google profile. Otherwise nothing is installing.
Click to expand...
Click to collapse
If root isn't important to you......BY FAR, the easiest solution is to follow the instructions in the "Return to Stock" thread - in general subforum, and flash the entire 4.4.2 SBF to your phone. Everything you need is in that thread, including links to drivers, tools, and the SBF files themselves.
Just keep in mind - you'll permanently lose root/wp-off. You can still use the temp-root methods, for now...but once you update to 4.4.4 (it will be pushed out to everyone SOON), you will have ZERO chance at rooting (unless a new exploit comes along, which is extremely unlikely, OR you get your bootloader unlocked through the middleman).
Good Luck!
samwathegreat said:
If root isn't important to you......BY FAR, the easiest solution is to follow the instructions in the "Return to Stock" thread - in general subforum, and flash the entire 4.4.2 SBF to your phone. Everything you need is in that thread, including links to drivers, tools, and the SBF files themselves.
Just keep in mind - you'll permanently lose root/wp-off. You can still use the temp-root methods, for now...but once you update to 4.4.4 (it will be pushed out to everyone SOON), you will have ZERO chance at rooting (unless a new exploit comes along, which is extremely unlikely, OR you get your bootloader unlocked through the middleman).
Good Luck!
Click to expand...
Click to collapse
Thnx)