I'm on kk rooted but wish to go back since my car doesn't work with with 4.4. I used motowpnomov or whatever it's called so I'm wondering the process since rooting attempts with rock with fail since I have no write protection. Thoughts?
Sent from my XT1058 using Tapatalk
Read the slapmymoto thread...
Just need to SBF back to the proper 4.2.2 file for your device/carrier. The first bit of the SlapMyMoto process will accomplish this, as @nhizzat said.
Related
I am using jcase's method of rooting form 4.4 down to 4.2.2 and back to 4.4 with a stock VZW Moto X.
I am trying to get some clarification on finishing on the first set of processes.
I have followed all the instructions for the first part successfully. I have Root and have disabled WP.
I was about to take the next step and "restore to the 4.2.2 Camera update" but this confuses me.
1) Will I lose root and WP?
2) Is this necessary to proceed to a rooted 4.4?
From jcase:
"First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update."
bump
slingblade01 said:
bump
Click to expand...
Click to collapse
You will lose root but not wp off. That's exactly what you want. No root but wp off since the root method for 4.4 is different. So yes you want to restore back to 4.2.2 after root and wp off.
Sent from my XT1060 using Tapatalk
Okay, I've been reading all over the forums here and I can't find a truly definitive answer:
I have an ATT MotoX (non-DE) running 4.4 rooted with SlapMyMoto.
Is it safe to take the 4.4.2 OTA that came out this week? Will this break root? If so, has anyone given instructions on how to re-root?
jaredtritsch said:
Okay, I've been reading all over the forums here and I can't find a truly definitive answer:
I have an ATT MotoX (non-DE) running 4.4 rooted with SlapMyMoto.
Is it safe to take the 4.4.2 OTA that came out this week? Will this break root? If so, has anyone given instructions on how to re-root?
Click to expand...
Click to collapse
my understanding is while you will still have root, you will lose the ability to write to the system, that write protection will be enabled, which makes it much less "rooted", and you won't be able to downgrade with a locked bootloader, there is no root method for 4.4.2
jaredtritsch said:
Okay, I've been reading all over the forums here and I can't find a truly definitive answer:
I have an ATT MotoX (non-DE) running 4.4 rooted with SlapMyMoto.
Is it safe to take the 4.4.2 OTA that came out this week? Will this break root? If so, has anyone given instructions on how to re-root?
Click to expand...
Click to collapse
If you want full root and have a locked bootloader, don't take the OTA.
I have an unlocked/t-mobile Moto X on 4.2.2 right now. Below is the timeline on how I got to that version.
1)Phone came with 4.4, so I rooted using dray_jr's guide here. Everything was working fine for 3 months
2)Yesterday, all of a sudden, my phone started giving me various issues like data turns off when I turn off my wifi, then after couple hours, only EDGE would work (No LTE). So I decided to factory reset my phone and re-root it.
3)So, again using Dray_jr's guide, I reflashed 4.2.2 CU using mfastboot, took the OTA to 4.4 and tried to root it again using mfastboot. But when I try to run RockMyMoto for 4.2.2 root exploit, it says that write protection is not enabled and the process stops there. I know that because I was already rooted once and disabled write protection using MotoWpNoMo, my phone has still write protection disabled.
So right now I am on 4.2.2 CU. I don't know how can I re-root it since the 4.2.2. root exploit won't work anymore. Can anyone please shed light here on how can I proceed? I would prefer to keep my bootloader locked for warranty purposes, but if I absolutely have to,then I don't mind unlocking my bootloader either.
Thanks a lot!
theremix said:
I have an unlocked/t-mobile Moto X on 4.2.2 right now. Below is the timeline on how I got to that version.
1)Phone came with 4.4, so I rooted using dray_jr's guide here. Everything was working fine for 3 months
2)Yesterday, all of a sudden, my phone started giving me various issues like data turns off when I turn off my wifi, then after couple hours, only EDGE would work (No LTE). So I decided to factory reset my phone and re-root it.
3)So, again using Dray_jr's guide, I reflashed 4.2.2 CU using mfastboot, took the OTA to 4.4 and tried to root it again using mfastboot. But when I try to run RockMyMoto for 4.2.2 root exploit, it says that write protection is not enabled and the process stops there. I know that because I was already rooted once and disabled write protection using MotoWpNoMo, my phone has still write protection disabled.
So right now I am on 4.2.2 CU. I don't know how can I re-root it since the 4.2.2. root exploit won't work anymore. Can anyone please shed light here on how can I proceed? I would prefer to keep my bootloader locked for warranty purposes, but if I absolutely have to,then I don't mind unlocking my bootloader either.
Thanks a lot!
Click to expand...
Click to collapse
someone can correct me if I'm wrong but here's what I understand:
RockMyMoto is used to root 4.2.2 in order to be able to run MotoWpNoMo. since you already have write protection disabled, RockMyMoto is useless for you. so just skip that step and go directly to SlapMyMoto. just be careful NOT to take the 4.4.2 update!
frenchie007 said:
someone can correct me if I'm wrong but here's what I understand:
RockMyMoto is used to root 4.2.2 in order to be able to run MotoWpNoMo. since you already have write protection disabled, RockMyMoto is useless for you. so just skip that step and go directly to SlapMyMoto. just be careful NOT to take the 4.4.2 update!
Click to expand...
Click to collapse
Perfect, thanks!
Hey guys,
So i was interested in installing a custom rom im my moto x and started by trying to root it.
Every thing was going fine, but after i placed the unlock code via CMD, i've got an error during the root process and my phone just died. Now all that i've got is a black screen, no matter if I try to hard reset or anything.
Any idea?
tl;dr my phone just died in the root process, wtf can i do?
Unlock code? Root process?
Which model do you have? Which version of Android was it on? What exactly were you doing or using to root or unlock?
Which model you have used ?
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
You will need to be far more specific in what commands you did, if any...and the specific errors.
Only way we'll know what's happened.
It may be of some help if you post the tutorial you followed and say exactly at what step things went wrong.
Sent from my Moto X using Tapatalk Pro
monzillo said:
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
Click to expand...
Click to collapse
The XT1058 has a locked bootloader, so I hope that tutorial didn't have you try to downgrade your ROM in order to use SlapMyMoto/MotoWpNoMo to root and disable write protection.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone anymore. Additionally, 4.4.2 closed the exploits used by SlapMyMoto/RockMyMoto to gain root, and the exploit used by MotoWpNoMo to disable write protection.
As others have suggested, post a link to the turtorial, and any error messages you saw while running the scripts.
Also, try booting into bootloader/fastboot mode. Can you get there? What version bootloader does it say you are on? I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. If you have 30.B4, then your only fix might be using RSDLite to flash the 4.4.2 SBF for your carrier, or mFastboot to individually flash all parts of 4.4.2 on your phone, and then forget about rooting unless Moto's web site gives out the bootloader unlock code for your phone.
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
HTC-OH_SNAP said:
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
Click to expand...
Click to collapse
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
kj2112 said:
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
Click to expand...
Click to collapse
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
kj2112 said:
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
Click to expand...
Click to collapse
The Safestrap process, and installing a proper safestrap rom does not update the phone's bootloader. I think it also doesn't touch the GPT.BIN.
I know you haven't had experience with Safestrap, so think of it as kind of a Host OS/Guest OS setup, or if it was a PC then kind of like a Virtual PC setup where you could have a PC running real Windows 7 on your C drive that you boot too, plus having Windows 8 in a virtual PC and the Virtual PC's image file being stored on your "D drive". Installing W8 in the virutal PC doesn't touch the W7 "host" os, or its boot partition, etc. (its not 100% exactly the same, but that is the best analogy I can come up with at the moment).
---------- Post added at 06:35 AM ---------- Previous post was at 06:02 AM ----------
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
re: safestrap affecting the bootloader, no, it does not. At least if you are using a ROM made for safestrap, and properly follow the process.
To determine the bootloader version, boot the phone to bootloader mode it should show the version number. I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. As @kj2112 has mentioned, If the bootloader has been updated to 4.4.2, do NOT attempt to downgrade. However when using safestrap properly, its different.
As for the error at step 3... apparently it is common for those who had once used MotoWpNoMo to disable write protection, then trying to run though the SlapMyMoto process.
The actual process for getting a working Safestrap setup is the same for all Moto X's, however the Safestrap roms, and possibly the installer, are model specific... So, for example, if you have a Verizon X with locked bootloader, you could still follow [GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo but using the Verizon specific SBFs, SafeStrap and Safestrap Roms instead of the ones for T-Mobile and RW linked in that thread (like on steps 1b, 3a, 5a, 6b).
Because of that, I'll point you to -> http://forum.xda-developers.com/showpost.php?p=52401229&postcount=30 as it is the quickest link I can find to a work around for slapmymoto if you've already disabled write protection with MotoWpNoMo.
I'm sure if you took the time to read every post in the SlapMyMoto thread or the entire MotoWpNoMo thread you will likely find discussions about your situation and a fix. For example: Post 349 through 357 of the MotoWpNoMo thread is a user having the same issue, but later says it was due to the SlapMyMoto file being the older 0.5c version rather than 1.0.
I'm sorry, I'm just not good with RockMyMoto/SlapMyMoto/MotoWpNoMo/etc and Safestrap as I have an unlocked bootloader, so I never had to mess with them to root and disable write protection.
how do i spf back to 4.2.2?
coolguy71261 said:
how do i spf back to 4.2.2?
Click to expand...
Click to collapse
This is someone's thread with their particular issue. If we start helping you in this thread with your issue....that is called thread hijacking.
You need to ask in a thread relevant to your issue, or start a new thread.
However.....since we don't know anything about your situation or your issue.....advice is hard to give.
You can probably start here tho.... http://forum.xda-developers.com/showthread.php?t=2603358
If that doesn't help, you need to make your own thread. And be as specific as possible with the details. But only start a thread if searching comes up with nothing and no existing threads match your issue.
Just some XDA etiquette.
Good luck.
And sorry to OP for off topic.
If you rooted with rockmymoto and took write protection off. You'll still have it so the only process you'll need to do is slapmymoto on 4.4. Safestrap will work with 4.2.2 and 4.4. If you want root stay there don't go to 4.4.2
MOTO X
KidJoe said:
Great Advice
Click to expand...
Click to collapse
Ok... so here is how the whole thing ended.
Checked my Bootloader - it was still 30.71.
Verified I still had Write Protection off.
Ran SlapMyMoto 1.0.
Took the OTA (From 4.2.2 it is still 4.4 and NOT 4.4.2)
Ran the ADB Shell Commands.
Installed SuperSu from the Play Market, and...
Rooted 4.4 with Write Protection Off.
Thanks!