yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] KidJoe:
Unless you have a custom recovery installed, you can't do a "recovery install" of SuperSU.

there should be other options to install the update.
[Moto X Original Android Development] twinkyz1979:
there should have been another option to go ahead and install while in the SuperSu app without going through recovery.
[Moto X Original Android Development] JarMagic:
Write Protection Off but...

So, I now have write protection off, but I am not able to maintain root after re-boot. As well, I am getting an error message when I open supersu app.
[Moto X Original Android Development] twinkyz1979:
If your write protection is off try upgrading SuperSU using SafeStrap to flash it.

SuperSU
[Moto X Original Android Development] JarMagic:
safestrap for Droid Maxx

I can't find the download for the Maxx specific. Do I use the Moto X one?
[Moto X Original Android Development] twinkyz1979:
If your write protection is off try upgrading SuperSU using SafeStrap to flash it.

SuperSU

SafeStrap v3.63a
[Moto X Original Android Development] JarMagic:
apk

Now I'm getting error problem parsing package. In a mess.
[Moto X Original Android Development] JarMagic:
Towelroot

I tried a couple of things, then I used towleroot, and now I don't loose root on reboot:)
[Moto X Original Android Development] smile_hh:
4.4.2 xt1058 version

LB 30. B4

Or you can write in addition to the protection??????????
[Moto X Original Android Development] Diego1751:
So the droid turbo recently got a root method (MoFo lets you flash system images but write protection is on) willl this work for us? 4.4.4 kk
[Moto X Original Android Development] beaups:
No.
[Moto X Original Android Development] JulesJam:
So for sure the MoFo exploit only works on DT? Even if we have a pre-rooted system.img for Moto X 2013 running 4.4.4, the exploit won't work to allow us to flash it?
[Moto X Original Android Development] beaups:
This isn't the mofo thread, no idea.
[Moto X Original Android Development] masterchapter:
Hi, this break even anti tamper if present?
[Moto X Original Android Development] mschumacher69:
This is obsolete...
[Moto X Original Android Development] rmead01:
This is what happened to me except when I flashed the 4.2 recovery I just did a factory reset. My system was still not write protected and when i finished setting up the phone i installed SU from the play store, updated binaries, and was rooted no issue. I didn't flash the 4.2 system though, just the recovery.
[Moto X Original Android Development] stonesaber:
That happened to mine as well. I think that's why it took running it twice to complete.
[Moto X Original Android Development] MaKTaiL:
Guys, I'm new to this phone. What exactly does this do?

I though root meant gaining write protection abilities to system.

Do I still need to run this even if I'm already rooted? I don't get it.
[Moto X Original Android Development] Dark9781:
Yeah. Wish I would of done that. I think the root exploit sees I have no write protection and thinks it ran the first 2 steps.
[Moto X Original Android Development] grifforama:
What's the benefit of this mod? I'm rooted already, and as we don't have an unlocked bootloader yet, I'm wondering why this would be necessary?
[Moto X Original Android Development] hank110:
I believe the benefit comes from this exploit surviving a factory reset and by extension has the potential to survive updates pushed by Motorola. In effect this would mean future updates should be easily rootable unless whatever hole it exploits gets patched.

This is purely speculation because we don't know exactly how the exploit works or if it can be reversed by an OTA update.
[Moto X Original Android Development] rmead01:
Have you tried the ADB command to see if you actually do or don't have write protection?
[Moto X Original Android Development] Dark9781:
Yup. Write protection is disabled.
[Moto X Original Android Development] rmead01:
I would think you could root at this point. That's kinda what I did, but i didn't write the system partition. that's an odd place to be stuck at.
[Moto X Original Android Development] Dark9781:
Yeah. I'm sure that root is possible like this just need to figure out how. May need to do some things manually.
[Moto X Original Android Development] rmead01:
Def don't want to start advising you what to try, since I was one last attempt from giving up myself. But maybe you would be able to fastboot flash the 4.4 system and bits and pieces 1 at a time?
[Moto X Original Android Development] Dark9781:
Yeah. May just try that tonight after I get home. The only thing that I really miss about root is greenify. At least this phone is great without root. Can't say the same for every phone I've had.
[Moto X Original Android Development] rmead01:
This exactly. I was highly considering ordering a dev ed just so it'd be easier to manage, but really greenify is what I use root for now. I'm even staying on dalvik for the donate package extras.
[Moto X Original Android Development] brianr134:
Rooting is possible but needs to be done manually for the time being, jcase's root method needs an update to accommodate for if wpnomo has disabled wp. after rooting and returning to 4.4 you can rerun wpnomo and then reflash the recovery.IMG.
[Moto X Original Android Development] Dark9781:
I figured it was. I just got to figure out what I need to run to do it. If not I'll wait for an update to jcase's root method.
[Moto X Original Android Development] :
Maybe I'm crazy, but if you've successfully killed write protection to /system, can't you just manually push SU back into the system partition?

JCase's install script installs SU into two places, so if you look at it and pick out the pieces from his script, then change it around so you can run it from ADB instead of as a shell script (note that the su binary needs to be in the same directory as the adb.exe file), you get:

adb shell
/system/bin/mount -o remount,rw /system
adb push su /system/xbin/su
adb push su /system/xbin/daemonsu
/system/bin/chmod 06755 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/daemonsu

Full install.sh script is below ripped from his SlapMyMoto install zip:

#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/rm /system/bin/log
/system/bin/ln -s /system/bin/toolbox /system/bin/log
/system/bin/cat /data/local/tmp/su > /system/xbin/su
/system/bin/cat /data/local/tmp/su > /system/xbin/daemonsu
/system/bin/cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh
/system/bin/chmod 06755 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/daemonsu
/system/bin/rm /data/local/tmp/setup.sh
/system/bin/dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/system/bin/reboot recovery

Someone should indeed error check me since I know about enough to be dangerous :eek:
[Moto X Original Android Development] shane1:
I ran all the commands from step 6 in slapmymoto and was able to update su afterwards
[Moto X Original Android Development] gunnyman:
Seems legit.
[Moto X Original Android Development] Dark9781:
You are awesome. Was going to check this when I got home tonight, but you beat me to it. Will give it a try when I get home.
[Moto X Original Android Development] beaups:
what exactly are you guys trying to do? you need root to push root, so even though wp is disabled, if you don't have root you are going to have issues.
[Moto X Original Android Development] gunnyman:
so mounting system rw isn't possible without root first?
[Moto X Original Android Development] bliu:
Finally got it to work after I reread the thread and saw you need to allow SU to grant permissions during the first stage. Also, to keep this thread about the WP bypass only, I posted a question here regarding 4.4 recovery/boot images. If anybody can help, I'd appreciate it!

http://xdaforums.com/showthread.php?p=48079829#post48079829
[Moto X Original Android Development] gitku:
I'll throw out my situation. A particular app I use isn't yet compatible with 4.4. I used jcases root method and then wpnomo afterwards but then realized my beloved app didn't work any longer. So I flashed back to 4.2.2. ... Like you said originally the wp is nomo :) but now the 4.2.2 root method fails because it detects wp is already off so it skips right to step 3.

I've only tried once so I don't know that I just wasn't patient enough or went through not paying as close attention as I should have but this may be how someone else lost root or by trying to go back to stock recovery and mistakenly flashing all.

So I think what these guys want to know is - is there an easy method to get root back or do we just need to go back through all the steps again and pay close attention?
[Moto X Original Android Development] matt99017d:
Have you tried to use slapmymoto since killing write protection? If so, have you gotten the same result?
[Moto X Original Android Development] mistermojorizin:
when you say jcase's methods are fully supported, you mean ALL the methods, or just current ones, all of which already have write protection off built in? cause i'm on motoroot, which was one of his methods, but i don't have SU access right at boot into android (adb mode), it takes a few seconds before i can start modifying system. and i dont' have write protection off.

do you think this root is good enough for your app? because if i could add write protection off to this without losing recovery this would be perfect.
[Moto X Original Android Development] Dark9781:
I tried both RockMyMoto and SlapMyMoto and it thinks that it already ran through steps 1 and 2. It skips to step 3 and does nothing. I haven't tried running the script manually through adb yet. I'm on 4.4 and really didn't want to flash back to 4.2.2 again and have to setup the phone again. May try it sometime in the future. Right now I'm fine with no root since appopps in 4.4 allows me to turn wakelock off on whatever app I want to it is like having greenify.
[Moto X Original Android Development] shane1:
If you ran this exploit just run the adb commands from step 6 in the 4.4 exploit reboot then install su and update that's what I did and it worked
[Moto X Original Android Development] Dark9781:
Unfortunately that didn't work. It may be because I did a complete flash back to 4.2.2 after running the exploit and failing to boot back into android.
[Moto X Original Android Development] grifforama:
How exactly did you do that ?

I keep getting FATAL: Download updated package error after "hmm, hold please"

Then it talks about a network problem ? Why is there a network problem ? What exactly is this attempting to do with my network ?
[Moto X Original Android Development] beaups:
It checks with auth server to make sure package is current and safe. Network/firewalls/ etc frequently conflict with that check.
[Moto X Original Android Development] redhonker:
This would mean the SuperSU will be able to survive the OTA update, right?

Thanks
[Moto X Original Android Development] altvolt74:
we are now in the same boat wp off and not able to get root any more ...any help whil be apreciated
[Moto X Original Android Development] mj0528:
Can you not simply install supersu?
[Moto X Original Android Development] altvolt74:
i try install superuser on both stocks 4.2.2 and no luck 4.4 ..In my case ...I had a bootloop and was unable to go to safesrptrap so I decide to do downgrade from 4.4 to 4.2.2 and re root but RW off is not allow in me to go further step 3 ..curents root method requires to be on ..and now im are stuck without root..
[Moto X Original Android Development] altvolt74:
THIS IS WHAT CAME UP C:\ADB>adb shell

/system/bin/mount -o remount,rw /system

adb push su /system/xbin/su

adb push su /system/xbin/daemonsu

/system/bin/chmod 06755 /system/xbin/su

//system/bin/chmod 06755 /system/xbin/daemonsusystem/bin/mount -o

stem

adb push su /system/xbin/su

adb push su /system/xbin/daemonsu

/system/bin/chmod 06755 /system/xbin/su

shell@ghost:/ $ /system/bin/mount -o remount,rw /system

mount: Operation not permitted

255|shell@ghost:/ $ adb push su /system/xbin/su

/system/bin/sh: adb: not found

127|shell@ghost:/ $ adb push su /system/xbin/daemonsu

/system/bin/sh: adb: not found

127|shell@ghost:/ $ /system/bin/chmod 06755 /system/xbin/su

Unable to chmod /system/xbin/su: No such file or directory

10|shell@ghost:/ $

/system/bin/chmod 06755 /system/xbin/daemonsu

Unable to chmod /system/xbin/daemonsu: No such file or directory

10|shell@ghost:/ $:(
[Moto X Original Android Development] :
Yeah, I wasn't entirely sure if this mod would allow adb to write to the system without the su binary installed. As indicated earlier in the thread, this isn't the case.

You will have to re-root. A couple people have said they just re-executed the SlapMyMoto install starting at Step 6.
[Moto X Original Android Development] rmead01:
hopefully some newer users will read and see that if for some reason they get stuck, to flash the 4.2 recovery only, perform a factory reset, then when it boots into 4.4 you can just install SU from the playstore and all works.

Maybe for those that are stuck with write protection off but not able to execute the root exploits, someone could remove the part in step 3 that checks for write protection so the install can proceed as normal.
[Moto X Original Android Development] TheWhiteChallenger:
Well I'm glad I waited to try this on the maxx. I think ill wait till 4.4 rolls out before I mess with this. Awesome hack tho
[Moto X Original Android Development] altvolt74:
LMAO!!!! I JUST HARD BRICK MY MOTOX :silly:

I WAS ON 4.4 WP OFF AND TRYIGN RE ROOT AGAIN I TRY THIS COMMANDS

fastboot flash partition gpt.bin

fastboot flash motoboot motoboot.img

fastboot flash logo logo.bin

fastboot reboot

BOOM Qualcomm HS-USB QDLoader 9008 oooh this is bad!!!! remind me my htc evo lte :silly:

BECAREFULL WHIT TRING TO REROOT WHILE YOUR ON MOTO WP NO MO!!!

---------- Post added at 08:42 PM ---------- Previous post was at 08:08 PM ----------

atleast i do have warranty and soon wp on:good::cyclops:
[Moto X Original Android Development] TheWhiteChallenger:
Wow, F*** that, not worth the risk just to avoid a reboot to recovery. This is a cool idea but if hard bricking from a simple reboot occurs the cost/benefit just didn't make sence
[Moto X Original Android Development] shane1:
Using your warranty when you break your device is half the reason bootloaders are locked. You break it pay for insurance or buy a new phone
[Moto X Original Android Development] EeyoreSyndrome:
Thank you very much for this! No more pesky issues with Xposed mods not sticking or file explorers / titanium not having complete R/W access!

! :)
[Moto X Original Android Development] beaups:
This user's brick had nothing to do with lack of write protection or motowpnomo. Doesn't even belong in this thread, in fact.
[Moto X Original Android Development] jonathanphx1:
beanups,

Is there something in the works that will reverse this tool. As others have said if you have to flashback to 4.2.2 there is no way to re root because jcases tool goes straight to step 3.
[Moto X Original Android Development] shane1:
The hard brick was aimlessly flashing things. Blaming the exploit is totally uncalled for!
[Moto X Original Android Development] Dark9781:
I can confirm this. When I attempted to re-root I flashed the 4.2.2 gpt.bin, motoboot.IMG, and logo.bin and had no issues.
[Moto X Original Android Development] TheWhiteChallenger:
i mean no disrespect, im sure your right, but could you elaborate? i havent run through slapmymoto yet but what was being flashed sounded right. im buying a dev editon maxx soon and this sounds great but a reboot ALOT (checking if mods worked or not) and i cant afford a hard brick even with warrenty as this will be my primary phone and my cpnsumer ed. will be sold.
[Moto X Original Android Development] shane1:
With a developer edition you do not need this exploit.
[Moto X Original Android Development] :
What's there to elaborate on? The developer of the exploit has stated it can't hard brick your phone. That means that he's not doing anything to the phone that would cause a corruption in the bootloader and prevent the phone from powering up or being recovered via, fastboot/RSDlite.

It's really quite hard to completely brick a phone. The bootloader survives even the most mangled Android install, allowing you to recover it.

All that said - it doesn't matter to you. If you have a developer edition, you don't need an exploit to root or attain r/w system access. You can do it right through the ADB tools.
[Moto X Original Android Development] TheWhiteChallenger:
Wow I've gotten so many mixed answers about that. I was under the impression the Dev editions still had r/w. I think someone even mentioned it on the first page or 2 of this discussion.

---------- Post added at 08:48 AM ---------- Previous post was at 08:46 AM ----------

Yea see, here it is. Is this incorrect? I'm lost.
[Moto X Original Android Development] altvolt74:
the point is that RW Protection was off and Im not sure if there was a root method... for those who bootloop ther device and the only way to recover was doing a downgrade of upgrade yeah I know I been sarcastic about the brick ...im for sure this is NOT the right thread the process I did to brick the device neither ask for root access
[Moto X Original Android Development] stonesaber:
All you need to do to the d.e. is flash a recovery ( I'm using skrilax's one here http://xdaforums.com/showthread.php?t=2543400 on my Maxx D.E.) and then flash superuser in recovery. No need to do anything else. Period.
[Moto X Original Android Development] TheWhiteChallenger:
I got that part. But root, and r/w access when booted into the OS are separate issues on the consumer version. And that's what I can't get a clear answer on. After unlocking, installing a custom recovery, and flashing the su binary, is the system partition write protected when booted into android? ie can I remount as r/w in root explorer and make lasting changes?
[Moto X Original Android Development] dtrud0h:
I can't comment on 4.4, but on uscc 4.2.2 after the first ota(camera fix) after using rock my moto and just installing the special recovery mode I could make lasting changes in regular android if I used root explorer to set the partition to r/w.

Hope this helps.

My friends call me "Nick Buzz"
[Moto X Original Android Development] Gundabolu SC:
You will find this in Jcase's first root exploit thread! I dont know if this applies to everyone else but i sure couldn't Mount system as RW!
[Moto X Original Android Development] stonesaber:
On the D.E. it is not write protected when you boot up. You can make lasting changes in root explorer and they will stick. Just try it.

---------- Post added at 09:03 AM ---------- Previous post was at 08:59 AM ----------

My Developer Edition Maxx is not write protected, which is the one he's asking about. You do not need to run these programs with the D.E. devices, you need to flash a custom recovery in fastboot and then flash the supersu.zip file in recovery and make sure when you boot up you have supersu installed from the market.
[Moto X Original Android Development] fury683:
Thanks for this. It didn't work the first time (not sure why, but think it had something to do with me needing to approve SU request manually..), but it worked the second time.

Sent you a few bucks for your work.
[Moto X Original Android Development] Rask40:
For what it's worth, I tried this twice on my rooted 4.4 AT&T X. Didn't work either time. Didn't seem to fail (struggled with finding...ADB? I believe) ... but never seemed to fail, either. Never had any issues booting or rebooting after that, but checking the write protection status always indicated that write protection was still on. Did try to go to the IRC room but seemed like the only people there were other users having issues. No big though. Phone works, and I'm plenty used to rebooting recovery if I need to tweak something that requires write protection off so I can live with it like that.

So long as it works for others, guess that's all that matters!
[Moto X Original Android Development] Skyrocket2Paradise:
will this work on rooted 4.4 verizon?
[Moto X Original Android Development] stonesaber:
Yep
[Moto X Original Android Development] Skyrocket2Paradise:
is it normal to sit at the long line of stars? after saying its really cold in here? want to make sure its still working and im not waiting around for no reason..
[Moto X Original Android Development] hartom:
Yeah, it'll then say OK let's get started. Whole process takes ~20 mins.
[Moto X Original Android Development] Skyrocket2Paradise:
mine says:

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

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

Press ENTER to exit

what is this error?

---------- Post added at 01:29 AM ---------- Previous post was at 01:11 AM ----------

I disabled my antivirus and firewall and I still get this and when I check it still has a value of 1. something is messing up
[Moto X Original Android Development] hartom:
Its not done.

Try running it again. Also did u get supersu prompt for adb shell ? U need to grant access to it.
[Moto X Original Android Development] enjoimadcow:
I just want to clarify. You can run this on a at&t 4.4 slapped moto x correct?
[Moto X Original Android Development] beaups:
Yes.
[Moto X Original Android Development] Skyrocket2Paradise:
I didnt is there a way to force it?
[Moto X Original Android Development] rift999:
I don't have the needed skills to edit jcases's SlapMyMoto and forgive me if I am wrong but his script checks write protection to know what step its on. Couldn't you just alter it so that the user manually inputs the proper step?
[Moto X Original Android Development] theascended:
Can someone add a couple of disclaimers to the first post?

1.) Using MotoWpNoMo may prevent users from rooting their phones after WP is removed (e.g. if you need to revert to stock for any reason). If/when the kitkat SlapMyMoto method is updated to allow manually running the stages, this could be removed, but its best to be up front about issues.

2.) There appears to be no way to reenable WP (if there was, I imagine everyone having issues rooting their phones would have done so by now).
[Moto X Original Android Development] hartom:
No. Just make sure adb is installed and working on your pc and if your phone prompts for access you accept.
[Moto X Original Android Development] Rebel908:
Going to assume there is no way to undo this? Trying to re-root, and I cannot proceed since SlapMyMoto isn't going properly since there is no longer any write protection.
[Moto X Original Android Development] enjoimadcow:
I'm in the same boat. Jcase is fixing up slapmymoto to work with this. We just have to patiently wait =). You can see this on post 504 on the slapmymoto thread.
[Moto X Original Android Development] shane1:
its possible to reroot with no write protection. i have 0 for write protection rooted with 4.4 bootloader and stock recovery if someone wants to test hit me up in pm
[Moto X Original Android Development] andino:
So after running this, what recovery should we flash back? Any additional steps in order to do this other than fastbooting a recovery?
[Moto X Original Android Development] barondebxl:
Worked for me the second time.
[Moto X Original Android Development] NJGSII:
Same here.

Xposed framework installation now sticks on reboot.
[Moto X Original Android Development] barondebxl:
Yep, all good!
[Moto X Original Android Development] nhizzat:
Why save it for PM? Why not share how you were able to regain root with write protection off?
[Moto X Original Android Development] shane1:
Because it only worked once I cannot duplicate it as of yet. By blindly posting something that's not tested could bork devices. I'd prefer to only mess up a few phones instead of a bunch of them lol
[Moto X Original Android Development] nhizzat:
I LOL'd IRL. Seriously.