yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] mschumacher69:
Dude if you've unlocked ur bootloader u don't need to kill write protection, unlocking ur bootloader kills it automatically. Just flash supersu and u get root with write access.

This thread is for killing write protection on devices that cannot have their bootloader unlocked.
[Moto X Original Android Development] DonDizzurp:
My bootloader is unlocked and I'm rooted.. why can't I write to system?

I tried to delete the bootanimation.zip, moved my custom bootanimation.zip into /system/media/ and changed permissions as well to 644 but after a reboot it went back to the stock bootanimation.zip

Are you saying the su binary I'm using doesn't have RW access to /system? That's strange.
[Moto X Original Android Development] KidJoe:
The processes and procedures used by those with UNLOCKED bootloaders is completely different than those with LOCKED bootloaders.

As such, I do NOT want to confuse those with LOCKED bootloaders who have come to this thread.

And in any case, unlocked bootloader or locked bootloader, MotoWpNoMo does NOT work once 4.4.2 is on your phone..

For those reasons, I suggested taking this to another thread, rather than continuing in this thread.
[Moto X Original Android Development] rjmohit:
would this work on Moto G?
[Moto X Original Android Development] mschumacher69:
Which Moto G do u have?
[Moto X Original Android Development] rjmohit:
The infamous Verizon Moto G XT1028
[Moto X Original Android Development] distortedloop:
A Mac option would be great, or at least a script of manual terminal commands instead of just Win & Linux executables. Is there something in the executables that can't be done via adb manually?

Anyways, I'm stuck trying to do this on my Mac and Droid Maxx. I have working device drivers, and a good knowledge of adb and fastboot commands. I am using VMWare Win7 installation, with proper/working drivers to try this.

The executable runs fine through every step, reboots to fastboot, reboots regularly, but then always times out with the adb access after the reboot. It times out after the Test 2 waiting for adb 120 seconds.

I have a second CMD session open, and adb won't work in it after the wpbegone app has been started in another CMD shell. As soon as I exit the wpbegone shell, adb works again, and I can reapply jcase's root.

I'm at a bit of a loss figuring out why adb access won't come back in Windows. If I disconnect the phone from the VM, and directly to my Mac, adb works fine.

Any ideas appreciated.
[Moto X Original Android Development] beaups:
Don't use a vm.
[Moto X Original Android Development] tootone:
did you try it? I am not having much luck.
[Moto X Original Android Development] rjmohit:
I'm travelling right now, will try as soon as I get back.
[Moto X Original Android Development] scorpion667:
I'm not trying to be a douche, I'm genuinely interested how one would go about pronouncing WpNoMo. Is it Whoop-nomo?
[Moto X Original Android Development] thelogman:
It stands for write protection no more. But it would be hella lame to call it that.
[Moto X Original Android Development] beaups:
Double you pee noe moe
[Moto X Original Android Development] mschumacher69:
That's how I pronounce it...
[Moto X Original Android Development] NWKENT:
OMGoodness..its an acronym..its not meant to be pronounced..I'd just focus on the matter at hand and learn how to spell the acronym..if it must be translated, here >> (Motorola) Moto Wipe No More..I do believe is the Dev's intention..

:)

sent by my 4.2.2_12.15.15

(Unlocked) XT1080M Droid Maxx #1

http://waynekent.com/page6.html
[Moto X Original Android Development] beaups:
Nope. Moto Write Protection no more.
[Moto X Original Android Development] NWKENT:
Lol..glad someone knows..someone is paying attention..

sent by my 4.2.2_12.15.15

(Unlocked) XT1080M Droid Maxx #1

http://waynekent.com/page6.html
[Moto X Original Android Development] GigaMill:
Hey everyone,

I'm wondering if this is possible with JCase's new 'tethered' root method?

http://xdaforums.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623

I attempted it, and I suppose logically that this method requires a reboot and therefore is incompatible.

What I'm getting at:

Does anyone know of a method that can be done without rebooting? (i.e. tether-friendly)

If not, can an addition be added to OP's post adding that this dosen't work with tethered roots/requires reboot?

A bit about me:

-I'm using a Droid Maxx (Non-Developer Edition) with a locked bootloader on a Verizon plan.

-My Droid was updated to 4.4 19.6.3, but I rolled it back to 4.4 19.5.3 with House of Moto so I could take JCase's new root method.

/EDITED/

I found the process:

http://xdaforums.com/showpost.php?p=53205527&postcount=314&nocache=1&z=2544314579572528
[Moto X Original Android Development] nsmal24:
Is Moto's write protection similar enough to HTCs that this could be slightly modified and used with a VZW HTC One on 4.10.605.3 (Sense 6 4.4.2)? I was one of the lucky ones that picked up my device in between exploits.
[Moto X Original Android Development] champlification:
towelroot

Has anyone tried using Towelroot with this? Geohot says towelroot won't work on Moto x because of wp, but if this removes wp, then why wouldn't it work?
[Moto X Original Android Development] KidJoe:
If your X has 4.4 or below, you can use SlapMyMoto and MotoWpNoMo to root and disable write protection. So there would be no need for towelroot.

But, when you flash 4.4.2 on the X, it enables write protection, and you can't disable it. (i.e. the vulnerability used by MotoWpNoMo was patched in 4.4.2).
[Moto X Original Android Development] champlification:
Right. Guess I thought for some reason that we could use towelroot to unlock the bootloader as well, but I guess not. Nevermind then. Thanks.
[Moto X Original Android Development] doitinthedirt:
It's simple to root the moto x on verizon anyway.. I ordered two in april and they both came with 4.4 on them, I used the took kit available here and it was quick and painless, than got file explorer from playstore and deleted the dang 4.4.2 update because it starts downloading on its own and that will destroy your new root and write, and than used file explorer with root add on to rename the update files so it no longer downloads the darn updates.. and last I used a nifty app here from kryptonite to disable the entitlement check so i can wifi hotspot with my unlimited data plan. Don't have an unlocked boot but do have a nice rooted moto x with write protection off.
[Moto X Original Android Development] NWKENT:
One can "freeze" MotorolaOTA updates with "Titanium Backup Pro".. but device must have Root access..

:)

sent by my 4.2.2_12.15.15

(Unlocked) XT1080M Droid Maxx #1

http://waynekent.com/page6.html
[Moto X Original Android Development] maslan:
I have same phone - tried those instructions and it always comes back as 1 on the MotoWpNoMo after it completes. I verified root with root checker after Jcase Pie. But this MotoWP reboots before it runs so it loses its root - i am guessing that is why it is not working? Am i missing something??

thanks guys.
[Moto X Original Android Development] dinkoh:
It gets stuck at "installing root stuff, thanks chainfire". Anyone experience this?
[Moto X Original Android Development] Stainless316:
No workee on Mini

Dear MotoWPNoMo Developer(s)

Can you please release a version of your software which waits after each reboot for the device to be re-rooted?

I have a brand new Mini. I have successfully run the jcase tethered root. I am trying to make it permanent as per the "

[Root 4.4.X] Pie for Motorola devices" thread. I have spent hours trying to re-root just as the phone boots. It simply doesn't work...

More details:

MotoWPNoMo consistently fails with:

Test 2: Booting device
Waiting for ADB (88/120)
must play a little while longer...

it's so cold in here
hmm, hold please
..............................................
[---------------------------------------------]
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

Windows Firewall is off. No other security software is installed on this machine (Win7 Ultimate x64).

Perhaps it is some other error condition?

Please help....
[Moto X Original Android Development] mschumacher69:
Dude, motowpnomo doesn't work on 4.4.2, it only works on 4.2.2 and survives the 4.4 ota, but not the 4.4.2 ota...
[Moto X Original Android Development] KidJoe:
Mini? As in Droid Mini? This is the X section. There are not too many Droid Mini users hanging out here.

There are apparently a few Droid Maxx users, and they have somethings slightly different (like ROM version, different abilities on downgrading, etc).

So I don't know that we could advise you properly.
[Moto X Original Android Development] Stainless316:
Forgive me if this seems like a really stupid question, but is there a Mini forum and where is it? I looked for it and didn't see one which is one reason why I turned up here (the other is that some of the posts speak of both Maxx and Mini).

Thanks!

---------- Post added at 09:09 AM ---------- Previous post was at 08:52 AM ----------

I am working from http://xdaforums.com/showthread.php?p=53205527&postcount=314 which seems to say otherwise.

Also most of the responses to http://xdaforums.com/showthread.php?t=2771629 are about applying MotoWPNoMo to 4.4 (both 19.5.3 and 19.6.3 are 4.4 F/W). They are all about the [MENTION=2376614]jcase[/MENTION] Pie rooter which is only for 4.4
[Moto X Original Android Development] mschumacher69:
This might be true for maxx and mini, I'm talking about the x... I'm not sure what works and doesn't work for maxx and mini...
[Moto X Original Android Development] superp32:
:( I was sooooooo stoked when I saw this thread , then I realized its not new lol , so close to being rooted and write protection yet so far away lol. Thanks for all the work you developers put in it has made owning my two motorola phones a pleasure .( I miss flashing my atrix hd though lol).
[Moto X Original Android Development] zxz0O0:
Have you tried towelroot temp-root and then run the application from the first post?

See link here: http://xdaforums.com/showthread.php?t=2783157

To temp-root, click "welcome to towelroot v3" 3 times, then enter 1337 0 1 0 4 1

No idea if this will work.
[Moto X Original Android Development] KidJoe:
Towelroot doesn't work on the X due to its write protection. (it says so right in the first post)
[Moto X Original Android Development] zxz0O0:
But temp-root should still work, or does the write protection also apply to /sbin?
[Moto X Original Android Development] KidJoe:
It applies to /system, and the folders under it.

Jcase's PIE exploit/process to temp root works. But it doesn't survive power off/on, and "root type" apps that need to mount /system and the like as R/W wont work.
[Moto X Original Android Development] Bones1304:
When I download MotoWpNoMo from the link in the op my computer scans it and finds a virus. Is there any other place it is hosted?
[Moto X Original Android Development] NWKENT:
Here is my personal copy of 0.0.4 >> https://docs.google.com/file/d/0B67RS0BDBp_iajNtTGEtZ191Ykk/edit?usp=docslist_api

Sent from my:

(Jaocagomex debloated)

4.4_19.6.3 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Moto X Original Android Development] badkarma6085:
Ran through this wpbegone and it gave me the error:

Checking for updates. Checking Failed....press ENTER to exit.

any ideas?
[Moto X Original Android Development] twinkyz1979:
really let's put some things back in place? My root app is gone i hope i didn't lose root trying this. It's been setting here at that screen for about 10 minutes now!! why would this even mess with my root app i just don't understand?

-UPDATE-

I rebooted my phone manually and installed the SuperSu.apk and all is good now. Even though I don't have WP off I am glad just to have SU.
[Moto X Original Android Development] samwathegreat:
You never advised what device you are using, or which firmware version you are on. MotoWpNoMo does NOT work on any Moto X running 4.4.2 or higher.

Some Droid Maxx users are able to successfully use it on 4.4.2 due to differences in the rom/bootloader, but it is a lost cause if you are using a Moto X unless you are on 4.4 or prior.

[MENTION=711482]beaups[/MENTION] : First, thanks for your contributions! Could you please update the OP to specify that your exploit will not work on Moto X with 4.4.2 + ? Your OP says "Jcase's methods are fully supported here", but of course that was written before jcase released PIE. Many users are (understandably) getting confused & expecting that it will work with PIE.
[Moto X Original Android Development] twinkyz1979:
It does work with pie in the case of the droid ultra and maxx on 4.4 but being i just took the jump to the 4.4.4 OTA I was simply trying it out to see what would happen if anything. I just never knew it would mess with root being it says you must be rooted to use it. I still don't understand why it uninstalled my root app. then said it was putting it back and then froze at that point till i rebooted my phone then the program told me write protect was gone which is was still there. I then had to re-install my root app manually which ended up still working as the binary must still have been in it's original spot.

So that being said if your on a Droid Maxx or Droid Ultra and on 4.4.4 this method no longer works.
[Moto X Original Android Development] GnatGoSplat:
Guess I should have checked here first, but I decided to try WpNoMo on my Droid Mini on the 4.4.4 OTA and it did exactly the same thing, removed SuperSU, but su is still there so all I had to do is re-install SuperSU and I have root functionality back.

I think there is a vulnerability here that needs exploring, however! I had installed the SuperSU app to /system on 4.4.2 and it survived factory resets due to being on /system. Somehow, WpNoMo has totally removed the SuperSU app from /system, so it was able to write to /system somehow. I verified it's completely gone by doing a factory reset, and it didn't come back.
[Moto X Original Android Development] s_u_n:
I am having difficulty in turning off write protect on my Droid Maxx.

I downgraded my Maxx to 19.5.3 from 19.6.3 last night and also used the pie exploit, which gave me temporary root.

In another window, I tried the MotoWpNoMo 0.0.4 several times and I observed if the write protect is disabled (0) or not.

After waiting for adb for around 90 seconds, if I run the pie exploit, MotoWpNoMo shows some characters like TTTTT or CCCCCC and then prompts me to press enter to exit.

So, it seems to work, but sadly write protect is still on (1).

What am I missing?

Also, I have super Su app installed via playstore and it tries to update some binaries and then finally says: Installation failed.
[Moto X Original Android Development] twinkyz1979:
I also ran into this problem on my wife's maxx.

1. go back to 19.5.3

2. run PIE

3. run MotoWpNoMo

a. it will boot into bootloader and do it's thing

b. it will reboot and say waiting for ADB

4. while MotoWpNoMo is waiting for ADB run PIE again quickly in another open command window (you must do this before MotoWpNoMo connects with device through ADB)

5. let MotoWpNoMo finish

6. you will have WP off

7. run PIE again

8. download SuperSu from the play store then run SuperSu app and let it install the new su binary

9. you should now have root and WP off

Those are the steps I took after a couple hours of banging my head against my desk.

Now her phone is on 4.4.4 with root but WP is on (WP on is the downside of going to 4.4.4 or at least right now)
[Moto X Original Android Development] s_u_n:
I got a little excited reading your reply and thought I had some new method here.

But, while waiting for ADB, I cannot connect via "adb shell", until the first 90 seconds.

I entered the adb shell /data/local/atvc/root.sh and it just said "error: device not found."

Exactly after 90 seconds, I got the command to get through and it rooted the phone.

On the MotoWpNoMo screen, I got must play a little while longer...

This was followed by must play a little while longer...and the other messages.

Finally I got this message: doing some *stuff*, and that was the first time.

Have a look at the sequence captured here.

Now, at the end of this, the write protect was off (0) and there was no root.

So, I re-ran the PIE exploit and rooted again. Rebooted manually. Root disappeared. Disappointed.

So, I ran towelroot. It rooted successfully (checked with Root checker). Rebooted manually. Root persists. Yay!

I tapped on the SuperSu app that I had previously installed via playstore. I got a message: App is not installed.

So, I went the Playstore and it said showed me that the app was disabled. So, I clicked Enabled. I launched the app and it prompted to update the binaries. There was choice of Normal and TWRP/CWM and I chose Normal.

Finally it showed the success status.

So, I am wondering what next is to be done.
[Moto X Original Android Development] twinkyz1979:
I forgot to say you need to run PIE again and then download SUperSu from the play store and let it install the new su binary.

My bad I am sorry.
[Moto X Original Android Development] rdenova:
I would freeze MotorolaOTA with ROM Manager - appfreeze.apk did not work for me. This will keep the 4.4.4 OTA nag away.:good:
[Moto X Original Android Development] bluebloomers:
Did towelroot give you wp off?
[Moto X Original Android Development] s_u_n:
Well, towelroot did give me root (and that was the first time that towelroot worked for me in the last 5 days).

It sounds strange that after getting WP off, and re-rooting with PIE, root disappeared after reboot, but I documented everything as it was happening. So, there was no mix-up.

All three tools are doing some magic and we don't know their true potential. :)
[Moto X Original Android Development] twinkyz1979:
PIE is only a temp root upon a reboot you must run PIE again to get root back. That is why you have to install SuperSu from the playstore after you run it.
[Moto X Original Android Development] s_u_n:
Ah.. All this while I was thinking that once WP is off, and if I root the phone with PIE, the root will persist across reboots. That did not happen in my case.

The root from towelroot did persist across reboot.

My SuperSU app was already disabled during this process - I don't know how though.

So, I enabled it via playstore and it downloaded a new version I suppose. But this was after I got persistent root.
[Moto X Original Android Development] tscan:
I can confirm that using Towelroot and installing SuperSU AFTER FXZing back to stock retains root on 4.4 if the initial method to turn WP off is followed before the FXZ. My root persists after reboot and I have root access by typing:

1. adb shell

2. su
[Moto X Original Android Development] ciabatoni:
curious

Im curious to kno, If I use this method to turn WP off, Ill be able to gain root, and unlock BL? If in the future I wanna unlock the phone to run on GSM, will running any of these methods to turn WP off or unlock BL screw with the unlocking of my phone, Droid ultra on 4.4.4

Im not new to the root game, SS, or most methods out there, dont care about warranties, Im currently using sprint S4, on cricket after ditching the Verizon s4 with that crazy locked down BL. Just came across this ULTRA and really haven't played with it to much, and recently thought about switching phones due to cricket wanting all there members to upgrade to gsm devices. Thanx as always
[Moto X Original Android Development] brainwash1:
This is not a bootloader unlock, it just allows you to write to system. Well, not you, because it doesn't work on 4.4.4, but someone on an older version could.
[Moto X Original Android Development] s_u_n:
Permanent root - yes

So, a little over a month after getting 'permanent root' and doing everything else that was required to keep the root (and also disable system update), a couple of days ago, my son did a factory reset by attempting to unlock the pattern lock. Well he just followed the on screen prompts (he cannot read much and is generally trigger happy) and when I was back with him after a couple of minutes, I could just see the red Droid boot up screen.

I knew that I am in trouble.

So, after the reset, the phone was up in a few minutes and the first thing that came into my mind was the tons of photos that I had. Luckily I had my photos backed up on Google+ at full resolution. I also had a backup on my computer but that was 1 month old.

The next thing that popped in my head was the root. What would have happened to it?

Well, after setting up my Google account and downloading tons of applications and their updates, I also downloaded and installed the root arsenal - the traditional SuperSU, ROM Toolbox and Root Checker.

I ran Root checker and was surprised when it said I had root. So, the root had persisted even after factory reset.

The next day I noticed that the phone was trying to get the latest system update (298MB) and realized that I need to freeze the Motorola OTA. So, fired up ROM Toolbox and froze the application. Immediately the download process terminated.

Now, I just lost my text messages in the whole restoration process (will have to download SMS backup and restore app soon)

My music is there on the computer and now I just got that back into the phone.

To verify that root really works, I got my Notification Toggles app and set it up the way it was earlier. It is able to toggle GPS with one touch - and that proves that root is working fine.

So, bottom line, factory reset did not change the Android version for me (19.6.3) and it did not get rid of the root (so /system was intact?).

I am happy that I had to just re-freeze the Motorola OTA app.

Hope this helps.

P.S. As a learning, I still have my pattern lock, but this time, I unchecked the Local wipe policy under "Device Administrators"
[Moto X Original Android Development] GnatGoSplat:
Yes, root always survives a factory reset because the root binary (su) and other busybox files are always copied to /system and only /data and /cache are erased on a factory reset. Worst factory reset might do is erase the SuperSU app, which can be reinstalled from the app store. You can also move it to /system and then it will always survive factory reset. /system is only ever touched on updates and reflash using RSDLite, so those are the 2 scenarios you would lose root.
[Moto X Original Android Development] mistermatrix24:
SU file location

So after countless hours of trying to time the command prompts for rooting with PIE while the MotoWpNoMo program did its thing I finally have wp off and root. for me the PIE root is persisting through reboots so I'm not gonna do anything with the towelroot unless someone says i need to. each time i reboot i check with root checker. My question concerns the location of SuperUser. on the root of my phone there are two folders(among others) Xbin and System. In Xbin there are a few files but no SU. In System there are a bunch of folders including app and ANOTHER Xbin folder. SU is in that Xbin folder. Nothing in SU's settings is greyed out and I clicked the option in SU to make it a system app. Is this okay? is this the folder its supposed to ultimately be in since it's a sub folder of System? Also im on a Droid MAXX running 4.4 19.5.3 (I held off updating it so not downgraded) Am i clear to update OTA to 19.6.3 now and keep root?

Thanks

Mistermatrix24
[Moto X Original Android Development] JarMagic:
Triangle

I followed the steps, and when I open the supersu app, it askes to install su binary update. When I click recovery install, the phone shuts off and opens with the yellow triangle. After a few seconds the phone reboots, and I've lost root. Any advise?
[Moto X Original Android Development] twinkyz1979:
I am not understanding why you would do a recovery install?
[Moto X Original Android Development] JarMagic:
The app had a pop up saying it was out of date.