yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] lowvolt1:
Safe strap doesn't work on 4.4?

I am on 4.4 OTA and safe strap works for me.

Am I missing something?
[Moto X Original Android Development] sorullo_xgrx:
You installed safestrap while on the KK 4.4 ota? I never tried that, just went the safe road reverting back to 4.2.2 as hashcode advice still doesn't support 4.4

---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
[Moto X Original Android Development] lowvolt1:
Yes. Was on 4.2.2 rooted with rockmymoto, ran motowpnomo, flashed back to 4.2.2 clean. And rooted with slapmymoto. Then installed safestrap. 3.65
[Moto X Original Android Development] KidJoe:
Wait. Safestrap is part of the MotoWpNoMo process THIS Thread is talking about???

If Safestrap is not, then wouldn't this question be more appropriate in a thread about safestrap?
[Moto X Original Android Development] th4t1guy:
me too brotha
[Moto X Original Android Development] NWKENT:
Excuse me..What may I ask that you'all are trying to download.?

sent by my 4.3_14.14.14

XT1028 (aka) Moto-G

The LAST American Cell Phone.!
[Moto X Original Android Development] knewman:
The Windows version of the application on the OP - http://www.rumrunner.us/MotoWpNoMo-0.0.4.zip
[Moto X Original Android Development] NWKENT:
Here is my personal copy >> https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit?usp=docslist_api

sent by my 4.3_14.14.14

XT1028 (aka) Moto-G

The LAST American Cell Phone.!
[Moto X Original Android Development] _litz:
It's more like w/the newer rooting methods, WpNoMo is part of the rooting process that's required before safestrap can be installed.
[Moto X Original Android Development] packhex:
(1) Know how to use ADB and FASTBOOT binaries

---- [Yes, use these tools to test USB connection BEFORE running Moto-WP-NoMo] -

---

(1) Know how to enable USB-debugging on YOUR device (Yes, do that now)

(2) Understand that you may NOT repack or redistribute Moto-WP-NoMo

Ok?

(Yes/No)

Yes

!! Do NOT for any reason bite, punch, or molest your device !!

Please wait....

..........

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (3/120)

Waiting

Test 2: Booting device

Waiting for ADB (26/120)

must play a little while longer...

it's so cold in here

hmm, hold please

..............................................

[-TTTT****************************************]

Press Enter to EXIT

and

c:\adb shell getprop ro.boot.write_protect

* daemon started successfully *

1
[Moto X Original Android Development] Kiwironic:
Thanks, however the windows motowpnomo link is dead.
[Moto X Original Android Development] NWKENT:
Here is my personal copy >> https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit?usp=docslist_api

sent by my 4.3_14.14.14

XT1028 (aka) Moto-G

Donate to HashCode (If you can)

http://waynekent.com/page6.html
[Moto X Original Android Development] Mustang02:
So I went through RockMyMoto, obtained root. Installed SuperSU from play store. Went through MotoWpNoMo and get this. Checked write_protect and it's still 1.

Any ideas?

Edit - It finally worked. Not sure what happened but I rebooted the device when I got that error and it kept going through. Now WP= 0!!
[Moto X Original Android Development] NWKENT:
A Reboot was the key..

sent by my 4.2.2_139.15.1

Jelly Bean TWRP 2.6.3.1

XT1060 Moto XDEV

Please donate to: jcase & Hashcode (if you can)
[Moto X Original Android Development] ReadyMadeFire:
Alright, I used RockMyMoto to obtain root and verified I had root access. I used MotoWPNoMo and the first instance it failed. During the second instance it removed su and supersu from the device but completed and stated that I have write protection turned off. If I check for write protection, it returns a 0 but I can not root the device with RockMyMoto or SlapMyMoto. Each step goes into step 3 which states that I should have root but I do not have root access.

How would MotoWPNoMo remove root from a device?
[Moto X Original Android Development] NWKENT:
Dont know how, but maybe start the process over, with this if you haven't gone to far to begin again..

Here >> http://waynekent.com/page5.html

sent by my 4.3_14.14.14

XT1028 (aka) Moto-G

http://waynekent.com/page6.html

Donate to jcase & HashCode

(If you can)
[Moto X Original Android Development] ReadyMadeFire:
I used RSD Lite to go back to 4.2.2 and each time I use Telnet to start over, the first try says it is the the 3rd try. It never installs su nor do I gain root access. I can take the OTA but when I get to 4.4 I am not able to connect with Telnet.

Sent from my Slapped XT1060
[Moto X Original Android Development] NWKENT:
Don't take the OTA..see my link with how the OTA process is done another way..OTA is possible trouble any time..and very risky in this process..especially..

sent by my 4.3_14.14.14

XT1028 (aka) Moto-G

http://waynekent.com/page6.html

Donate to jcase & HashCode

(If you can)
[Moto X Original Android Development] ab.:
Got it working on the second try on my xt1058 4.2.2 rooted

Here are some of the things I noticed

1. Turn off your firewall and must be rooted.

2. Keep your phone's wifi on during the process

3. After the first reboot, there's a prompt on your phone to Allow root access.

Hope this helps :good:
[Moto X Original Android Development] ReadyMadeFire:
The root is the problem. I lost root when running the MotoWPNoMo. Su was uninstalled during that process. I do not understand how but it was. When I check to see if I have write protect off, it returns a 0 so that part was successful but the su binary is not installed. How can I install the su binary if I do not have access to the system folder. It returns a read only for the system folder.
[Moto X Original Android Development] lowvolt1:
Have you downloaded SuperSU from the play store?
[Moto X Original Android Development] ReadyMadeFire:
Yes I have and when you open it, the program states that su binary is not installed and force closes.
[Moto X Original Android Development] lowvolt1:
Okay. Flash back to 4.2.2 if you haven't already. Since your write protection is already 0, you can root using slapmymoto.
[Moto X Original Android Development] ReadyMadeFire:
When I check for write protection with ADB, i return a 0 but I am not able to write to /system. ADB states this is read only. Is it possible that the system is still write protected but I can return a 0 when I check with ADB?
[Moto X Original Android Development] lowvolt1:
Are you rooted? If you answer yes, explain what you did after running motowpnomo.
[Moto X Original Android Development] ReadyMadeFire:
I was rooted when I ran MotoWPNoMo but I lost root after successfully disabling write protection. Now when I try RockMyMoto or SlapMyMoto, I can not regain root. Anytime I try to write to /system, it says that the system is read only. This is why I can not gain root. I can not get Su to install.
[Moto X Original Android Development] lowvolt1:
Okay, have you rebooted?

Rsdlite back to 4.2.2

Run slapmymoto

Do not take 4.4 OTA until prompted to do so.

Do not take 4.4.2 OTA at all.
[Moto X Original Android Development] ReadyMadeFire:
I have flashed back to 4.2.2. Ran SlapMyMoto. When I run the Jar file, it states that Write protection is off executing step 3 after reboot, apply 4.4. I reboot and do this again and then apply 4.4 (NOT flashing with RSD Lite). After I boot into 4.4 I apply the commands stated in SlapMyMoto. The last command does not execute as it returns "permission denied".
[Moto X Original Android Development] lowvolt1:
Are you running cydia impactor in 4.2.2 and using telnet or puttytel to run the dalvikvm commands? You should be, after pushing the .jar with adb. Do the cydia impactor and telnet twice. Rebooting in between as stated in the instructions. Then when prompted take 4.4 OTA. After you OTA you will need to slide unlock the phone and grant permission. Then complete slapmymoto.
[Moto X Original Android Development] ReadyMadeFire:
I am using cydia impactor and telnet to execute the commands for the .jar file. It states that the system is not write protected, executing step 3, apply 4.4 after reboot. I ran this command, rebooted, ran command again in telnet, then applied 4.4 When it was done I did not have to grant permission after slide unlock.
[Moto X Original Android Development] lowvolt1:
Will you type me the command you are using in telnet?

Also, after 4.4 have you verified that USB debugging is still on?
[Moto X Original Android Development] ReadyMadeFire:
USB debugging is enabled.

Code:

dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto

this is done in a telnet session.
[Moto X Original Android Development] lowvolt1:
Are you taking OTA or side loading
[Moto X Original Android Development] ReadyMadeFire:
The OTA that downloads is 4.4 and not 4.4.2. I updated with the OTA.
[Moto X Original Android Development] lowvolt1:
Are you running the dalvikvm command twice? Rebooting in between?

---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------

Are you pushing the slapmymoto.jar to SD card first?

---------- Post added at 07:15 PM ---------- Previous post was at 07:07 PM ----------

You posted in the slap thread that on first run it says executing step 3.

Its been awhile since I rooted but I don't think it is supposed to say that.

If it were me I would rsdlite back to 4.2.2 and try again.
[Moto X Original Android Development] ReadyMadeFire:
I would like to thank you all who helped me with my problem but I was an idiot last night and was using the wrong jar file of slapmymoto. I was using the one for. Version . 5c instead of 1.0. Once I used the correct jar file, things went smooth from then on. Again thanks for all the help.

Sent from my Slapped XT1060
[Moto X Original Android Development] atomicspaceindian:
Can somebody post a mirror of the windows version of this?
[Moto X Original Android Development] atomicspaceindian:
For some reason I am still getting a 1 :/. Any ideas? I have rebooted twice already.
[Moto X Original Android Development] lowvolt1:
Re root with rock my moto and run it again. Some people had to use a different computer.
[Moto X Original Android Development] atomicspaceindian:
Will try, thanks. Unfortunately, my other computer isnt in the "best" of condition, so I have to bear through it. I hope it all works on this

---------- Post added at 02:29 PM ---------- Previous post was at 02:26 PM ----------

I am trying to reroot, but it says "You are rooted, please install SuperSU. Exiting..."
[Moto X Original Android Development] lowvolt1:
I helped a guy through this one time and it would not go until he tried a different PC. I will be here to help.

---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------

I thought you said you flashed back to 4.2.2.

I would do that. Root with rock then run motowpnomo
[Moto X Original Android Development] atomicspaceindian:
Okay, hold up. this is what i did

Flashed to 4.2.2 using RSD

Rooted using RockMyMoto

Used motowpnomo

Didnt work so I reflashed to 4.2.2 using RSD

Rooted using RockMyMoto

Used motowpnomo

Didnt work so consulted XDA
[Moto X Original Android Development] lowvolt1:
As long as your on 4.2.2 camera OTA and root using rockmymoto, then run motowpnomo. You are doing it right.
[Moto X Original Android Development] atomicspaceindian:
I am using the second one listed [http://sbf.droid-developers.org/phone.php?device=0 Is it right?
[Moto X Original Android Development] lowvolt1:
Sorry. Can't get your link. Your on at&t so I can't be sure of what version you need. Google it
[Moto X Original Android Development] southern87:
If it's for att then the 2nd one is correct
[Moto X Original Android Development] atomicspaceindian:
yeah, thats what im using

---------- Post added at 02:04 PM ---------- Previous post was at 01:48 PM ----------

YES. Running in Compatibility mode works!
[Moto X Original Android Development] drago10029:
Hey Beaups can you update the OP with the file NWKENT uploaded? the link posted has been killed.
[Moto X Original Android Development] silvernirvash:
the link no longer works :/
[Moto X Original Android Development] silvernirvash:
the link keeps leading me to a 404 error saying the page is no longer available. Did you remove the page or is this just for me that's having this issue?
[Moto X Original Android Development] NWKENT:
Sir..which link are you referring to..more info would be Awesome..If you are having trouble with my link..I can send PM with the link, if that helps..?

Sent from my 4.4_19.5.3

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Moto X Original Android Development] silvernirvash:
http://www.rumrunner.us/MotoWpNoMo-0.0.4.zip

every time i click on it it just says page not found and all i see on the main page is the HTC version of the download. :/
[Moto X Original Android Development] NWKENT:
Here's a link to my personal copy, I had posted it a few pages back..

Hope this helps..

Here >> https://drive.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit?usp=docslist_api

sent by my MZ617-64 XYBoard 10.1_VRoot_SafeStrap v3.12_Jelly Bean 4.1.2
[Moto X Original Android Development] silvernirvash:
zomg tysvm!
[Moto X Original Android Development] drago10029:
Magical part?

but seriously, I want to go back to Write Protection 1, I'm assumed the bootloader is what's changed. I'm complete stock 4.2.2 with "MotoWPNoMo' as well and want to know if I updated to 4.4 then to 4.4.2 would that get me back to Write protection on? Would I have to OTA or download directly from Motorola?

thanks in advance for the response!!
[Moto X Original Android Development] mschumacher69:
Once on 4.4.2, there's no way (currently) to disable write protection anymore, unless you unlock the bootloader that is...
[Moto X Original Android Development] drago10029:
I understand that but my question is about how to get write protection turned on. And how to do it exactly. Make sense?
[Moto X Original Android Development] mschumacher69:
Ahhhh you want to enable it! Once you update to 4.4.2, it would be enabled automatically...
[Moto X Original Android Development] drago10029:
Yeah enable lol also would i OTA or have to download from Motorola and flash that way? Also are you 100% certain this would do it? I need Write protection on 100% for sure!
[Moto X Original Android Development] hank110:
Just wanted to say good work beaups. Worked great!
[Moto X Original Android Development] beaups:
error looks plenty self explanatory to me.
[Moto X Original Android Development] gunnyman:
Has anyone who's done this been able to put on stock recovery for 4.4?

I get precheck validation fails when I try to do so.
[Moto X Original Android Development] Dark9781:
Ran into an issue after running this. I'm currently on KitKat 4.4 and rooted using SlapMyMoto. Everything installed properly, but after rebooting the phone would not boot back up. Luckily the bootloader was unaffected and I was able to flash back to 4.2.2 and re-root. Those on 4.4 with root through SlapMyMoto may want to be cautious.
[Moto X Original Android Development] shane1:
I believe with our root process you'd have to flash the rocovery from jb
[Moto X Original Android Development] gunnyman:
So Slapmymoto broke KitKat recovery, not this?
[Moto X Original Android Development] shane1:
I think so. In the root we only flashed certain kk parts so the recovery can't validate ....... I think

---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------

I had the same error but the code showed up as 0 and then had to adb the su commands from the root process so su would update
[Moto X Original Android Development] gunnyman:
putting back the files altered by slapmymoto allowed me to keep root install stock 4.4 recovery, and WP is still off :)
[Moto X Original Android Development] rmead01:
I'm not exactly sure how to explain my experience but I'll try and sum it up as it's now solved.

Jcase root on 4.4 was my base. Ran through this process attempt #1, it just failed about half way through and window closed. phone was unaffected. reboot phone and began process again. This time the process went all the way through. There were moments where it took a long time but eventually completed. My phone reboot but never came fully on.

The screen would show boot animation then just go black, forcing a hard power off. I could boot to bootloader but nothing else. I attempted the 4.4 recovery and system flash, no go. Locked out. It was a long time and alot of retrying to flash files before I thought to flash the 4.2 files.

I flashed the 4.2 recovery and booted to it. was given the choice to factory reset device and did it. Phone finally booted up. I ended up with android 4.4 rooted,with no write protection, and the 4.2 recovery.

I'm setting up my phone right now but i'm not sure where to go from here or if I should just stop. I'm rooted and everything is working fine. Just not sure if I should attempt the 4.4 recovery flash or just leave 4.2 and go with it.
[Moto X Original Android Development] beaups:
couldn't you just dd that recovery from android?
[Moto X Original Android Development] gunnyman:
oh sure now you remind me :D

I'm back to where I want to be though
[Moto X Original Android Development] mj0528:
glad I saw this before I pulled the plug, who would've known we'd be restoring yet again.......

I'm good with WP LOLOLOLOL

---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------

Yes, be very cautious. I thought everyone was rooted on 4.4 these days but I'm guessing not
[Moto X Original Android Development] beaups:
not sure what in this application could cause this. it's quite simple....
[Moto X Original Android Development] mj0528:
so this should work on a rooted 4.4 moto x?
[Moto X Original Android Development] beaups:
It *should* yes.
[Moto X Original Android Development] gunnyman:
Worked on my rooted kitkat. No problems
[Moto X Original Android Development] stonesaber:
Thanks beaups. Worked the second run on my VZW 4.4 Moto. Some of the prompts made me chuckle.
[Moto X Original Android Development] Dark9781:
As stated before it wouldn't let me boot my phone back up. I flashed back to 4.2.2. Turns out it worked and I have no write protection, but now I can't re-root. I try running SlapMyMoto and RockMyMoto and all I get is System Is Not Write Protected Executing Step 3 and it does nothing.
[Moto X Original Android Development] lowvolt1:
Worked second time around for me!

I noticed late in round one that I had to give permission by unlocking the screen and pressing accept in SuperSU.

Thank you.
[Moto X Original Android Development] mj0528:
Worked as advertised!! Thanks!!
[Moto X Original Android Development] mschumacher69:
Yes I'm 100% sure, this is actually the only way to enable it, there was no way to enable it again before 4.4.2 was released.

You can either OTA or flash the SBF, but don't OTA unless you're 100% stock...
[Moto X Original Android Development] drago10029:
Thanks for the stock reminder but ;) I read up on everything else (I'm as stock as can be). How to eliminate MotoWPNoMo isn't in any of the guides though thanks! I did read about 4.4.2 removing WP but needed to be sure, i'll assume you read it thru the forums like I did.

By any chance does the MMS bug or Loss of signal bug effect your Moto x? I've had it on 3 Moto x so far! I know unbelievable. So I have to get rid of it and I'm getting a new/different phone.
[Moto X Original Android Development] mschumacher69:
This is because there was no way to eliminate it, as I said, once write protection was disabled, there was no way to enable it again until 4.4.2 was released which enables it automatically with no current way to disable it again.

I can't comment on MMS because I don't use it, but I don't have any issues with my signal...
[Moto X Original Android Development] drago10029:
Thanks a lot man, unfortunately these 2 issues are big for me! MMS and having signal are pretty important, but thanks again.
[Moto X Original Android Development] dspolen:
Missed a step!

So...I got a new Moto X and it came with 4.4 installed. I reverted back to stock 4.2.2 before using MotoWpNoMo. So I went back to stock firmware, then rooted the phone with RockMyMoto. Then once it was rooted I installed Stock Rooted Vzw Safestrap ROM build 4.4.2 from KrYpToNiTe. Everything works great. But I noticed that I forgot to kill write protection....

Can I still do this step without hurting my phone now...or do I have to start all over again. Only reason I care to do this is that I was going to us Xposed Installer and gravity box (KK) to have a few more features that I miss with ROM's like AOKP or CM12.

Any help would be appreciated.
[Moto X Original Android Development] jbrukardt:
Ok, having a heck of a time with this

Details:

Republic wireless Moto X 4.2.2 (no OTAs), never been on anything but 4.2.2

RSD'ed back completely to stock

Rooted using Jcase Rockmymoto

All firewalls and AVs off

No AP isolation

ADB and fastboot both confirmed working

Tried two different PCs, one win8, the other win8.1

superSU works just fine outside this process, and i have confirmed im rooted with Root Checker

This is the best progress ive managed to get so far

It seems to process through, but never successfully goes to 0. Also, doesnt seem to clobber twice, not sure if thats necessary

I get a eu.chainfire.supersu force close somewhere in the middle of the process randomly sometimes (and sometimes not). Ive tried updating the su binary (which required a complete rsd back to stock and rerun of rockmymoto), ive tried running superuser from CWM rather than SuperSU, etc etc. Note that superSU works just fine outside this process, and i have confirmed im rooted with Root Checker

What version of SU, and SuperSU is everyone using that doesnt crash? And alternatively, has anyone had it get through the process, but still be 1?
[Moto X Original Android Development] Lazybox:
the download link meet 404 error
[Moto X Original Android Development] SoNic67:
http://rumrunner.us/MotoWpNoMo-0.0.4.zip

Can somebody post it in a new place?
[Moto X Original Android Development] NWKENT:
Here's my personal copy >> https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit?usp=docslist_api

Sent from my 4.3_14.14.14

(Unlocked) XT1028 Moto G

http://waynekent.com/page6.html
[Moto X Original Android Development] DonDizzurp:
4.4.2 OTA supported?
[Moto X Original Android Development] KidJoe:
No. 4.4.2 closes the exploit that was used by MotoWpNoMo.
[Moto X Original Android Development] DonDizzurp:
Thanks.

Any other workaround or do we just have to wait?
[Moto X Original Android Development] KidJoe:
Unless you can get the bootloader unlock code from Moto's web site (which voids your warranty if you don't have a Developer Edition X), you can't do anything.

While JCASE has posted he has a root exploit for the X that he wont release until the fall (due to work and family commitments), it does not address a bootloader exploit which will allow disabling write protection on 4.4.2 like MotoWpNoMo does, nor has anything else been said about a write protect disable exploit.
[Moto X Original Android Development] DonDizzurp:
I have an unlocked bootloader (code from the Moto site)

I have a custom recovery (TWRP)

I have root

I just don't have RW access to /system which is weird because this is the first phone I've owned that requires a special process to gain RW on system.

It's also the first phone where I'm using the stock ROM instead of a custom ROM so maybe all phones do this and I just never had to deal with it before.

If not, it's weird that they did this.
[Moto X Original Android Development] KidJoe:
Then lets take it to a different thread...
[Moto X Original Android Development] DonDizzurp:
What? This thread is talking about killing the write protection. My question is in regards to killing write protection for 4.4.2

Why would this need to be in another thread?

You're mentioning unlocking the bootloader when the OP clearly states this thread is NOT about unlocking bootloader but about killing write protection.