yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] beaups:
Introducing MotoWpNoMo. The purpose of this application is to disable the pesky write protection on BL-locked motorola devices. After successfully running this application, you will no longer need to boot recovery or use other methods to temporarily remove write protection. This exploit is permanent in the sense it will survive factory resets, reflashing the device, etc. However, like with any exploit, you should not expect it to survive OTA's or other updates. This application will work with many motorola devices, however I'm only posting it here to keep the files and feedback consolidated (plus, I'm lazy). THIS IS NOT A BOOTLOADER UNLOCK, IT ONLY REMOVES WRITE PROTECTION. Let's get started....

Credits and terms:

beaups and fuses for MotoWpNomo application. jcase for root and gunnyman and brianr134 for testing. MotoWpNomo MAY NOT BE REHOSTED, REPACKAGED, INTEGRATED INTO A ONE-CLICK, BAT, SHELL SCRIPT, OR ANY OTHER APPLICATION. THE ONLY PLACE TO ACQUIRE THIS APPLICATION SHALL BE RIGHT HERE, IN THIS THREAD. THIS IS NOT OPEN SOURCE, DON'T ASK!

Pre-requisites:

1.) Working root (su). Jcase's methods are fully supported here

2.) Working adb and fastboot drivers. Yes, that means WORKING. Don't clutter this thread with driver issues

3.) Linux (32 bit) or windows

4.) Disable all firewalls/internet security/antivirus before running. This is the #1 issue encountered when running the application

Instructions:

Linux (preferred):

1.) download the application: motowpnomo

2.) extract the archive: tar -xf [filename]

3.) run the application: sudo ./wpbegone

4.) follow the on-screen prompts

Windows:

1.) download the application: motowpnomo

2.) extract the archive

3.) run wpbegone.exe as administrator

4.) follow the on-screen prompts

After the application is complete, you can verify with:

adb shell getprop ro.boot.write_protect

If you see "0", that pesky write protection is gone

Donations are appreciated and can be made to (paypal): motowpnomo@gmail.com

support is available in #MotoWpNoMo on the freenode and andirc networks.
[Moto X Original Android Development] Ctrl-Freak:
Wow... Sounds great.

So... What part of the phone is changed? How do you revert to stock?

Thanks!
[Moto X Original Android Development] beaups:
1.) a magical part

2.) you don't
[Moto X Original Android Development] gunnyman:
It works! Thanks Beaups
[Moto X Original Android Development] graffixnyc:
Nice. Will try when I get home
[Moto X Original Android Development] gunnyman:
If you are running this on a Mac in a VM, each time the phone reboots and the program is waiting for adb, unplug the phone and plug it back in once the phone is started up again or else the process will fail.
[Moto X Original Android Development] RobertsDF:
Sounds great but is there no way to get back to write-protected other then OTA? Will flashing the FXZ restore it?
[Moto X Original Android Development] TheWhiteChallenger:
would this work on the droid line up?
[Moto X Original Android Development] beaups:
possibly. try it.
[Moto X Original Android Development] beaups:
in what case would you want write-protection back? also, no, flashing FXZ will not restore it.
[Moto X Original Android Development] Gundabolu SC:
PERFECT!!! Hated that i couldnt write protect off even with an unlocked bootloader!! Now everything is fine!!! :D :D :D :good:
[Moto X Original Android Development] TheWhiteChallenger:
cool. i will. if it works ill let you know so you can setup a thread in the droid ultra/maxx forum if you would like

---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------

oh, so are you guys flashing your stock recovery back after this w/o issues?
[Moto X Original Android Development] beaups:
Recovery will not affect this. If you get issue on other device, pm me. Should be able to add support.
[Moto X Original Android Development] TheWhiteChallenger:
ok ill let u know via pm, im trying something else right now if that works i should be able to tell you in a couple hours. and i was wondering if stock recovery could be re-flashed to re-enable a standard factory reset not to remove mod. so that should work right?
[Moto X Original Android Development] beaups:
Yes you can flash stock recovery after this.
[Moto X Original Android Development] Gus194:
Do you thing this would work on the Droid RAZR?
[Moto X Original Android Development] shane1:
After running it said no su fu after rebooting su binaries weren't up to date and su couldnt fix. Ran adb and got the 0 so it worked then had to run a couple commands from the root thread and all is well again.
[Moto X Original Android Development] rmead01:
Ran into an issue and jumped in your IRC. Hopefully someone is around to help.
[Moto X Original Android Development] AdhvanIt:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (4/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must play a little while longer...

it's so cold in here
hmm, hold please
..............................................
[*********************************************]
ERROR: looks like device is not rooted. su or FU!!!
adhvanit@Lisa ~ $ adb shell getprop ro.boot.write_protect
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1

Any idea what would cause it to not work? If there's a way for me to pull a log of what failed specifically, I could probably be of more help.

VZW Moto X locked BL running 4.4.
[Moto X Original Android Development] gunnyman:
Are you rooted?
[Moto X Original Android Development] ConstantHero:
Capitalize the "Y"es
[Moto X Original Android Development] jellman:
thank you

wow im stupid lol
[Moto X Original Android Development] corywf:
Kill write protection error "FATAL: Download updated package"

I wanted to know if anyone else ran into a problem

while doing the kill write protection step?

I've tried to get this to work several times now and still no luck.

The steps I followed are listed below:

My moto x was originally on stock 4.4.4

then I used rsd lite to downgrade to 4.2.2

I used rockmymoto to gain root and it was successful,

motowpnomo fails every single time I've tried to use it.

I tried using USB 2.0 rather than 3.0, not sure if that would matter

I turned off my anti-virus

This is the error message I get when using MotoWpNoMo:

[---------------------------------------------]

FATAL: Download updated package

If you are running the latest version, and continue to receive this error

you have a network problem. Disable firewalls, antiviri, security softwares etc

Press ENTER to exit
[Moto X Original Android Development] beaups:
Network/firewall/antivirus interfering.
[Moto X Original Android Development] robsharp78:
NVM just used linux...
[Moto X Original Android Development] Dragon31337:
I'm on 4.2.2, rooted with RockMyMotot and seems like it does not work:

Please wait....

..........

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (3/120)

Waiting

Test 2: Booting device

Waiting for ADB (40/120)

must play a little while longer...

it's so cold in here

hmm, hold please

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

[CCCC*****************************************]

Press ENTER to exit

>adb shell getprop ro.boot.write_protect

1

On previous try it showed TTTT instead of CCCC....

---------- Post added at 01:38 AM ---------- Previous post was at 12:39 AM ----------

I figured it out. Device was going offline randomly and lost adb connection. I read about it on internet, triggered off\on debugging and plugged into another port. And it worked! thanks!
[Moto X Original Android Development] corywf:
AV and FW turned off, Router's FW turned off. Still getting the same error message.
[Moto X Original Android Development] corywf:
I'm still having issues with this. Now I am getting

Checking for updates......

ERROR: Cannot check for updates

Again, this is with Firewall off, AV off, and Router's firewall turned off
[Moto X Original Android Development] easting:
Same error message I just got.
[Moto X Original Android Development] corywf:
I'm guessing it's a problem with the server
[Moto X Original Android Development] SomeoneE1se:
Did you try running as an administrator?
[Moto X Original Android Development] corywf:
Yes, tried as an admin and not as an admin just in case. Still no dice.
[Moto X Original Android Development] Khanusma:
This is what a successful run looks like....

==================== Moto-WP-NoMo 0.0.4 ==============================

Moto-WP-NoMo comes with NO WARRANTY (express or implied)

and NO GUARANTEE OF FITNESS for any particular task.

We have made every effort we can to make this a safe process for users

however the authors disclaim any liability for damage to your phone

or other materials or devices used during this process.

The entire risk of running Moto-WP-NoMo lies with you, the user.

By using this software you acknowledge and accept that the authors

are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?

(Yes/No)

Yes

Dear User: We will expect that YOU:

(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 (42/120)

must play a little while longer...

it's so cold in here

hmm, hold please

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

[---------------------------------------------]

doing some *stuff*..................

this is getting boring, let's go ahead and get started..

clobbering (1).........................................

clobbering (2)......

Waiting for ADB (43/120)

must play a little while longer...

lets put some things back in place...

installing root stuff, thanks chainfire

wait for it.........

yep, done. bye bye pesky write protection!

send your money, ALL OF YOUR MONIES to - motowpnomo@gmail.com

Press ENTER to exit
[Moto X Original Android Development] SomeoneE1se:
Keep trying it, mine just spontaneously worked last night.
[Moto X Original Android Development] StealthPanda:
Will you please post if you get this to work?

Mine got stuck at the exact same spot yesterday. I tried it ~10 times or so, with admin/non-admin, and a bunch of different firewall/DMZ settings on. Is this thing trying to connect to some external server at this point or something?
[Moto X Original Android Development] beaups:
Server was down much of yesterday. If you are still having issues, it's a network/antivirus/firewall problem on your end.
[Moto X Original Android Development] corywf:
I tried on 2 different computers and 2 different networks all with anti-virus and firewalls turned off. It fails each time at with "fatal download upload package". Are there any logs I can pull for you?
[Moto X Original Android Development] 640k:
any plans to modify your utility to bypass the server dependency in the future?
[Moto X Original Android Development] hdmunger:
Just ran through this successfully...only a couple of hiccups that I noticed and possible solutions...

1. I turned of AV and FW and the dependency server appeared not to be an issue this morning.

2. First time through, when SuperSU need me to grant permission to the adb shell, I think the delay between it asking and me noticing may have been more than the script could handle...turning off/uninstalling superuser protection temporarily may help...but on the second attempt with superuser granted it just proceeded each time it asked for access.

3. Each time the script rebooted into the system I needed to immediately unlock the screen so that usb debugging would activate...seemed not to do so in a timely enough manner unless the screen was unlocked on each reboot. (turning off the screen lock temporarily before starting may have helped streamline the process)

4. It also seemed to help having the screen off delay set to a longer setting (5 or 10 minutes) so I could keep a closer watch on the progress and knew when the phone was rebooting and not just timing out the screen.

Anyway...just my observations (may or may not help).
[Moto X Original Android Development] beaups:
Nope.
[Moto X Original Android Development] Lynx83:
Ran this multiple times with no errors but I still get "1" when I check write protection... Is this common?
[Moto X Original Android Development] lowvolt1:
Means it didn't work. Your missing something.

Slapped the sh*t out of my X
[Moto X Original Android Development] Lynx83:
Ya I get that but I dont get what. Downgraded to 4.2.2 rooted, went to run this. It runs fine, but I still get the "1". No clue why.
[Moto X Original Android Development] lowvolt1:
I guess to better understand what's going on, I would need screenshots and or explanation of what you did.

Maybe try a reboot.

Slapped the sh*t out of my X

---------- Post added at 09:14 PM ---------- Previous post was at 09:14 PM ----------

You are rooted?

Slapped the sh*t out of my X
[Moto X Original Android Development] bisbers:
I was getting that message too, followed dhoppy advice, instead of running from cmd I right clicked directly on program and chose run as administrator. Seemed to work.
[Moto X Original Android Development] Lynx83:
Ok I will re-do it tonight and try it again. I tried it on my own and running 640k script. Both finished successfully but neither got rid of write protection. I want root, but I want 4.4 for the transparent status bar lol.
[Moto X Original Android Development] lowvolt1:
Just to get on the same page. You are on 4.2.2 camera update rooted with rockmymoto correct?

Slapped the sh*t out of my X
[Moto X Original Android Development] Lynx83:
I was yes, no I am stock 4.4 no root. I am going to start fresh tonight.

Re-Install 4.2.2 via RSD

Root with RockMyMoto

Try this and ill take screen shots along the way.
[Moto X Original Android Development] Lynx83:
Ok so last night I started from scratch. I noticed that my pc (I am a Mac user) accepted an update and turned on the windows firewall back on. Turned it off and everything worked the first time. Rooted on 4.4 now :)
[Moto X Original Android Development] NWKENT:
Allow me to understand your posts please..

You started with Rooted 4.2.2, attempted the 4.4 retain Root from 4.2.2 then failed, had 4.4 No ROOT..

FXZ'd back to 4.2.2

Ran the 4.2.2 process, from 4.2.2 to 4.4 and now have successfully completed the process, and now have 4.4 Rooted.?

Are you positive.??

Do you own the DEV version device.??

sent by my MZ617-32 XYBoard 10.1_SafeStrap v3.12_Jelly Bean 4.1.2

Please donate to: jcase & Hashcode (if you can)
[Moto X Original Android Development] Lynx83:
I have a Moto Maker VZW version of the phone.

I started at 4.4 originally since it shipped with that.

Downgraded to 4.2.2 via RSD

Rooted via RockMyMoto

Removed WP succesfully (after I realized WF was still active and I deactivated it)

Verified WP was removed. Showed a '0'

Ran RSD again to get a clean install of 4.2.2

Ran SlapMyMoto to the step where I need to take the OTA

Took the OTA

Finished the process

Installed SuperSU to verify I had root

Installed XPosed Module

Having fun customizing my rooted phone :)
[Moto X Original Android Development] tCizler:
How long does the RED part take?? Mine has been sitting there for about 10 minutes and my phone's lockscreen keeps lighting up and then turning back off every 10 seconds or so. I don't want to bite, punch, or molest my phone in any way, :) so i'm not sure what to do at this point??

---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------

OK, it just finished... but it looked more like this

[TT***********************************]

Press ENTER to exit

Any ideas of what went wrong? Also, i ran WP check in ADB and it still says =1

EDIT: OK i just rebooted my phone and reran the WP exploit and it worked WP=0. I'm only leaving my post in case someone else has a similar experience. Just rerun it.
[Moto X Original Android Development] NWKENT:
PLEASE..I plead with anyone that remains on 4.2.2 (if any)..WAIT..Truly I Say To You..there will be a much simpler way to gain Root from 4.2.2_12.15.15 (to) 4.4_19.5.3

PATIENTS..will be rewarded.

Those that have a device on 4.4 w/o Root..YOUR hope is that someone claims the bounty..or a new device and start over, or an OS update that is Rootable..

sent by my 4.4_19.5.3

SlapMyMoto Root

XT1080M (aka) Droid Maxx PE

(device #2)

Please donate to: jcase & Hashcode (if you can)
[Moto X Original Android Development] lowvolt1:
I would reboot and run it again

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] tCizler:
I agree!!! I traded my wife my Maxx running 4.4 and got her replacement phone (vibrate was defective/intermittent), luckily it was on 4.2.2 still. Hence why i'm here. And trust me after being on 4.4 w/o root vs 4.2.2 with root..... 4.2.2 w/root is the best way to go for now.
[Moto X Original Android Development] tCizler:
Got another question. Since rooting with RockMyMoto and running this MotoWpNoMo, I can not get Adaway to work. It installs but when I open it, it doesn't fully open, (pic attached) and after long enough, it says it's not responding and I have to close it. Same goes for holo reboot, it installs but just freezes when I press any buttons after it opens. Is there something I'm missing?? Do I need to mess with permissions or something?

Sent from Droid Maxx
[Moto X Original Android Development] lowvolt1:
I'm rooted write protect off. And use adaway. No issues at all. I would suggest to make sure write protection is disabled. And reboot phone. possibly even delete app data delete app and reinstall. What version of adaway are you using?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] tCizler:
I tried all that. Uninstalled and reinstalled several times. using version 2.8 and even tried 2.7. WP = 0 so i know WP is off. Also i rebooted into recovery manually and it still didn't work. rebooted several times.
[Moto X Original Android Development] lowvolt1:
Try this version.

https://www.dropbox.com/s/enbzm4b9qa3vl5x/AdAway_2_2-1.apk

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
I'm getting an error/timeout on the first portion:

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 (120/120)

Connection failed!!

FIX IT, yes, YOU fix it now!!!FIX IT NOW!!!!!

Press ENTER to exit

it boots into the boot loader and just sits there...any ideas? I rooted with Jcase's RockMyMoto and have root.

thx
[Moto X Original Android Development] lowvolt1:
Make sure USB debugging is on. Reboot the device.

Toggle between MTP and camera and back to MTP. in the notification pull down.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] tCizler:
Thank you very much, but i just figured it out. I have no idea what made it catch my eye, but i noticed my apps were a little misaligned compared to what i was used to. Then i noticed SuperSU by chainfire was missing. Somehow it uninstalled during the WP off steps. I reinstalled it and let it update, now everything works great.

Thanks again

P.S. somehow titanium backup was working, that really threw me off
[Moto X Original Android Development] Slarti77:
Hey LV thanks for the reply.

debugging is on.

Rebooted.

Verified that it is MTP.

All these were good. Reran. Same results times out at 120/120.

I'm not supposed to make any chocies on the phones fastboot screen...correct?
[Moto X Original Android Development] lowvolt1:
Correct. No choice selection.

So you plug into the pc, phone is booted normal mode. Root verified?

You here connection tone on pc? But times out.

Virus protection off? Fire wall off?

What version of windows?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
LV, see below.
[Moto X Original Android Development] lowvolt1:
0pen adb. And type adb Devices See what it tells you.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
C:\ADB>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

TA4310AK1W device

C:\ADB>

I'm running wpbegone.exe directly from C:\MotoWpNoMo-0.0.4 by right clicking on the EXE and choosing "run as administrator".
[Moto X Original Android Development] lowvolt1:
Did you toggle between MTP and camera and then back?

Try just double clicking onbthe exe instead of right click run as admin.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
toggled back and forth and just double clicked on the EXE. no joy.
[Moto X Original Android Development] lowvolt1:
Okay. There have been reports of this from other users. Do you have access to another pc? You could try a different pc. Also have you rebooted the pc?

And your moto drivers are up to date?

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
Hey LV,

Looks like it worked this time.

I reinstalled the drivers and then ran it and didn't get the double tap previously when it went to fast boot. I did get the following error

==================== Moto-WP-NoMo 0.0.4 ==============================

Please wait....

..........

Checking for updates......

Test 1: Rebooting into bootloader

Waiting for fastboot (12/120)

Waiting

Test 2: Booting device

Waiting for ADB (35/120)

must play a little while longer...

it's so cold in here

hmm, hold please

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

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

Press ENTER to exit

But I just reran it and it looked like it was ok. Then just before teh first clobbering I got a message on the phone that stated SuperSU had stopped working so I closed it. But it went through and looks like it finished correctly.

When I check, I get this....

C:\ADB>adb shell getprop ro.boot.write_protect

0

C:\ADB>
[Moto X Original Android Development] lowvolt1:
You did it. 0 is what you want.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] Slarti77:
Hey LV...something funny happened on boot today...

After the phone booted I saw "Android is updating". I almost wet my pants. I was sure that somehow the 4.4 upgrade that keeps wanting to happen had happened. I immediately went to SuperSU to see if it worked and then went to rootchecker. Both still showed I had root. When I looked at About Phone, it still showed me on 4.2.2.

Any idea what "Android updating" means? Is this possibly related to the removal of write protection?
[Moto X Original Android Development] lowvolt1:
I would guess that since you disabled write protection and have effectively rooted 4.2.2 that it updated the files. I would also assume that if you rebooted again it probably would not happen unless you changed something else before rebooting. I do a lot of tinkering with my phone and when I use root browser to move, change or add system files, I get the same message.

Slapped the sh*t out of my X

if you found me to be helpful, throw me a thumbs up.