yashsingh1/xdaforums huggingface dataset:
[Moto X Original Android Development] lulajardim:
For me if I do a full reboot, install xposed and then a soft reboot, most of my modules (including some custom I wrote myself) work fine.

I only have two modules that are not working: Crappalinks and Chrome New Tab

But a few hours after doing a soft reboot my Package Manager("pm" command line) and Activity Manager("am" command line) stop working. Sometimes I have a segmentation fault, sometimes it says that it cannot link executable.

And today, after 4 days of uptime, I had to do a full reboot because ALL my apps were crashing when trying to start it. I'm pretty sure it is related to the workaround for xposed to work.
[Moto X Original Android Development] bongostl:
Ok, so I'm thinking. In theory, shouldn't we be able to create a flashable zip upgrade from 4.4 to 4.4.2 that bootloader locked people could flash via safestrap? Wouldn't this be an effective work around?

People who know more than me - thoughts?
[Moto X Original Android Development] lucfig:
My experience with root and the update to 4.4.2.

I was able to keep root and activate xposed with soft reboots.

After a week or so, xposed stopped working and I lost the ability to write on the system partition.

The next day I lost root altogether.

So, if you have a locked bootloader and needs root, don't update to 4.4.2. I might never be able to root again unless I unlock the bootloader or someone comes with another exploit.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] lulajardim:
did you upgrade your SuperSU app?
[Moto X Original Android Development] lucfig:
Yep, but I don't have the paid version. And now SuperSu returns an error when trying to update the binary. As I said, no root anymore.

Not a big deal, I'm OK, but I would like to have root.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] lowvolt1:
Have you tried to reboot "recovery" like we used to to temporarily disable write protect? And then update supersu binaries.
[Moto X Original Android Development] lulajardim:
Just redownload the older version from chainfire's website. (you probably had v1.91... link here -> http://download.chainfire.eu/381 )

You'll find the apk inside the zip on a folder named "common"

When you install v1.91 if it still asks to update su binaries, try v1.89 from here http://download.chainfire.eu/376

If it still asks to update su binaries, then you I believe that you really lost root.

And remember that if this works, you should not update your SuperSu from play store or it will ask to update su binaries again.

This only worked with previous root methods and with SlapMyMoto you keep the stock recovery.
[Moto X Original Android Development] lucfig:
Just tried without success.

Thanks anyway.

Enviado de meu XT1058 usando Tapatalk

---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------

Thanks guys!

The combination of reboot recovery and installing an older version of SuperSu worked!

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] lowvolt1:
I thought it might be worth a try.
[Moto X Original Android Development] lucfig:
And it was. Read the post below that!

Thanks.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] ecetim:
What do you mean by "reboot recovery"?
[Moto X Original Android Development] lowvolt1:
Its not really recovery, as in "recovery". It's a way to temporarily remove write protection.

What you do is power off the device, then press and hold power and volume - for about 3-5 seconds. Let go and navigate to "recovery" using volume - and then select it using volume +. Your phone will boot "normally" but write protection will be disabled until you reboot again.
[Moto X Original Android Development] ecetim:
Gotcha! So this allowed you to update SuperSU and regain root? What about xposed?

Sent from my Slapped Moto X
[Moto X Original Android Development] lowvolt1:
It didn't help me. I suggested it to a user and it worked for them. I would assume it would work with xposed as well
[Moto X Original Android Development] lucfig:
It worked for me.

I had to install an older version of SuperSu and regain root.

Xposed works after a soft reboot.

Enviado de meu XT1058 usando Tapatalk
[Moto X Original Android Development] JGoN86:
If I'm already on the 4.2.2 camera update firmware do I start from there in the process or do I being from the beginning
[Moto X Original Android Development] lowvolt1:
Start there. Root using rockmymoto. Then motowpnomo. Then slapmymoto. You will be prompted to take the 4.4 OTA in the slap processes. Depending on carrier and where they are with 4.4.2 OTA roll out. You may be updated to 4.4.2. If that's the case, don't OTA.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] tejaskary:
So wait, if we reboot from recovery, are we still bypassing write protection on 4.4.2 and root and xposed works fine? I have been doing this in 4.4, and I don't really see this as an issue if it works in 4.4.2
[Moto X Original Android Development] lowvolt1:
Theoretically. Yes.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] _litz:
why is this "MotoWPNomo" now required?

Previously, in version 0.5c, root was attainable without removing the write protection.

For someone who wants to make sure they can restore the device back to factory condition, WITH WP ENABLED, removing it is not desirable.

So how do you do the "old" method, that 0.5c used, where write protection is maintained, and you use the recovery to boot as writable system, as needed?
[Moto X Original Android Development] lowvolt1:
Are you asking how to reboot "recovery"

Power off device

Press and hold power and volume down for 3-5 seconds and let go

Use volume - to navigate to recovery.

Use volume + to select.

Your phone will boot "normally" but write protection will be disabled.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] _litz:
No, that's not what I asked.

Go to the wayback machine and read the instructions for 0.5c, as captured on 12/7.

When that version was out, removing write protection permanently on /system was not required.

Instead, a special boot kernel was placed in the recovery partition, allowing you to boot to recovery, which booted the phone normally, except /system is not read only.

Now, we have version 1.0 which includes "MotoWPNomo" ... which permanently removes the write protection on /system.

My question is simple : why is this now required, and how does one achieve root using the old method without permanently removing /system's write protection?

Edit: there is a reason for asking this. "MotoWPNomo" is not reversible. This is not desired for some.
[Moto X Original Android Development] lowvolt1:
The "simple" answer to your question is because that's the way it works. If you don't desire it don't use it.

You may be able to use .05c but I don't know.

If you use .05c you may not be able to gain root on 4.4.

If you choose to root using 1.0 and going to 4.4 and you permanently disabled write protection. Have no fear. When you take the 4.4.2 OTA your write protection will be restored.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] winn75:
Could someone just make a SlapMyMoto apk app that would Directly root Moto 4.4 in one process without going through so many steps?
[Moto X Original Android Development] M973:
I have a question I've recently been wondering about. With 4.4.2 being pushed to many or most of the carriers... I'm on AT&T XT1058 4.2.2 pre camera update (I feel like I'm the only one left) rooted with pwnmymoto

I have seen people struggling so with the process, I've been holding off, and I know there would first be un-rooting, restoring (I only froze a couple of things) and I see xposed can't just be "uninstalled" "Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip" via dray_jr's thread http://xdaforums.com/showthread.php?t=2603358

*I know step 3 will prompt me to take the 4.4 OTA -what if when I finally get myself to try to do the root process the OTA only offers 4.4.2? (which i guess will happen eventually) Is there another way to take 4.4 at that point other than OTA? (I'm guessing not)

So, I'm wondering, if I don't try Slapmymoto soon, could I be SOL? :confused:

Thanks

Edit: and wanted to mention, I appreciate all the help I have seen many offering in this process, and hope that some will be there when I get to it :)
[Moto X Original Android Development] lowvolt1:
It is very possible that you would/could be SOL.

Your already rooted with pwn. So why not just run motowpnomo and then root using slapmymoto before 4.4.2 comes out.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] M973:
Thanks

-you mean I could skip updating to the camera update and rooting with rockmymoto (which makes sense), and start with step 2
[Moto X Original Android Development] lowvolt1:
Maybe I should clarify.

You should be able to run motowpnomo because you are rooted with pwn.

You will still have to flash to 4.2.2 camera update, but you won't have to root with rockmymoto. Once your on clean 4.2.2 camera update and write protection is disabled the rest is relatively easy.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] M973:
ok, thanks! -will hopefully try this in the next day or so
[Moto X Original Android Development] lowvolt1:
Hit me up if you need help.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] M973:
^

Thanks much, appreciate it!
[Moto X Original Android Development] _litz:
If 4.4.2 ota restores the write protection, does it also defeat the root?
[Moto X Original Android Development] bigv5150:
It doesn't defeat root but makes root almost useless. You can't make system changes. So you have root just very limited.
[Moto X Original Android Development] lowvolt1:
The reports are that you can still reboot "recovery" and write to system.

With that being said, there have been reports of other weird anomalies a couple weeks after OTA.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] bongostl:
When I reboot into recovery on the 4.4.2 OTA (i have root), it actually opens up the recovery.

Anyone have a thought?
[Moto X Original Android Development] lowvolt1:
No thought from me at this time. I have not heard of this happening yet.

It would seem that when you took the OTA your recovery was flashed. That is most likely the reason that others are reporting the weird issues.

slapped the sh*t out of my X

if you have found me to be helpful, throw me a thumbs up.
[Moto X Original Android Development] mercado79:
I've been wondering the same thing and would love to hear the real reason for the switch to including

MotoWPNomo in the rooting process.

Yes, 4.4 is rootable using version 0.5c. It was the original method used to root Kit Kat. I remember Jcase modified the process because those that had used MotoWPNomo previously were running into problems rooting using 0.5c.

All the "permanent" talk makes me uncomfortable. I'm still rooted the old fashion way (without MotoWPNomo), but wondering if I should do it over again before the 4.4.2 OTA starts getting pushed to VZ phones.

[MENTION=2376614]jcase[/MENTION], any chance you might comment on this?
[Moto X Original Android Development] jcase:
Because that is how i did it, anyone else is feel to come up with their own root and WP bypass
[Moto X Original Android Development] _litz:
Ok ... so what if you use the 0.5c method, where you replace the recovery with the customized boot image, that enabled write protection?

That's how it works under the 0.5 method currently.

Boot normal, /system is read-only. Boot recovery, you have read-write.

Will that method work for 4.4.2 when it comes along?

honestly, you really only need read-write in /system only rarely, like updating superuser, or busybox.

Otherwise, booting read-only works just fine.

(for those who mentioned AdAway, just boot /system read-write, then symbolically link hosts to /data, and let adaway update hosts in /data, problem solved)
[Moto X Original Android Development] jcase:
You can't boot a customized image.

No it won't work in 4.4.2, nor will it work with the 4.4 bootloaders.
[Moto X Original Android Development] lulajardim:
[MENTION=2376614]jcase[/MENTION], I know you stated before that you have no intention on developing new root methods for the Moto X.

But is there any chance you have reconsidered and decided to take a look on 4.4.2?
[Moto X Original Android Development] _litz:
Ok, I'm confused here.

custom bootloader? huh? I'm talking about a pure stock X here, standard "motomaker" model with locked bootloader.

*Currently* ... the 0.5c method works for this model, provides a root path, is upgradable, and works fine in 4.4.

(e.g., downgrade to 4.2.2, gain root, take OTA, you end up with 4.4 and root; and /system is rw with the reboot via recovery method)

My question is ... this very same method, downgrade to 4.2.2 ... what happens if the OTA you take is 4.4.2 instead of 4.4 ?

Do you no longer have root? If root is still active, will the reboot via recovery allow r/w access to /system?
[Moto X Original Android Development] cpetersen2791:
If your already on 4.4.2 (Kitkat), you cannot downgrade. If you are on 4.4 w/ root, and take OTA, you get this weird root/non-root. Basically, root is there, but /system is not writable. That's how i have been reading this.
[Moto X Original Android Development] jcase:
No time, sorry.

No one mentions custom bootloader.

I am aware 0.5c works, but it has it's own flaws hence no longer beign available. Don't take OTAs with root, it is not a smart move.

JC
[Moto X Original Android Development] _litz:
Quoting from Step 3 :

"Once the device has rebooted, please take the 4.4 OTA."

So what happens if the only OTA available is 4.4.2?
[Moto X Original Android Development] jcase:
The device is not rooted at the step when you are taking the 4.4 OTA. The 4.4 update.zip is available from other sources and can be sideloaded in recovery.
[Moto X Original Android Development] M973:
This would mean that if only the 4.4.2 OTA was available, it's still possible to opt for the 4.4? Though I'd have to learn how to sideload a zip in recovery with a locked bootloader, but at least can be done it sounds like? As I was figuring I need to rush to do this process before only 4.4.2 was available.

Please let me know if I'm interpreting incorrectly :)
[Moto X Original Android Development] _litz:
Can't you just use RSD-Lite to push the 4.4 update via bootloader/fastboot?

All it does, after all, is flash images to partitions.

The locked bootloader doesn't seem to care, when applying the 4.2.2 downgrade, after all ... what's the difference between that, and a 4.4 or 4.4.2 image?

The images themselves are all signed, which is what the bootloader cares about ... right?

Back to previous question ... if I'm understanding this right ...

at Step #3, the device is not rooted. You apply 4.4 update (via OTA or other means), then there are additional steps to gain root. Right?

And these additional steps do not work for 4.4.2? Or they do work, but with varying results?
[Moto X Original Android Development] M973:
If you meant my question re: locked bootloader, I just meant that it doesn't allow for a custom recovery (TWRP, etc) for flashing a .zip
[Moto X Original Android Development] KidJoe:
Rather than taking this SlapMyMoto thread off track, Please READ this other thread -> http://xdaforums.com/showthread.php?t=2635366 and you will get an understanding that if you flash 4.4.2 you can no longer downgrade to a previous ROM even if its signed, etc.
[Moto X Original Android Development] _litz:
That is a very informative thread.

Basically, if I'm reading it correctly, the only "safe" 4.4.2 upgrade method involves piece-meal upgrading from a 4.4.2 SBF archive, and pointedly not upgrading the bootloader.

Per a few posts in that article, running the 4.4 bootloader with the 4.4.2 system does work, and preserves the ability to downgrade.

Someone please double check that I'm reading that right ... this stuff is too important to screw up ....

Note ... in the SBF, the bootloader and partition are the following two items :

<step operation="flash" partition="partition" filename="gpt.bin" MD5="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" />

<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" />
[Moto X Original Android Development] SYNSYNACKACK:
So if I understand correctly, MotoWpNoMo does not permanently disable write protection, as with 4.4.2 it becomes enabled again?

What about using an app like ES File Explorer?

Under the settings, there is an option to Mount R/W which I did to System to remove some bloatware that wouldn't uninstall normally.

Would this work that same as having write protection off ?
[Moto X Original Android Development] flashallthetime:
Yes if you take the ota it will flash the new boot loader 30.b4 and you can not downgrade back to the 4.4 boot loader. The only safe to prevent a possible brick situation is to keep the 4.4 bootloader and flash only the system.img, modem and boot.img from the sbf firmware.

Sent on my Gummy running Lenoto X
[Moto X Original Android Development] tejaskary:
Interesting....So, whenever the ATT/VZ 4.4.2 SBF is posted online, will be it possible to retain root by piece-meal upgrading from the SBF?
[Moto X Original Android Development] Cozume:
I believe that is what FATT is saying in his post just above yours - flash only the system.img, modem and boot.img from the 4.4.2 sbf firmware when it is available.
[Moto X Original Android Development] _litz:
That's the way I interpret it ... of course we need the actual VZW update, first, before we'll know for sure.
[Moto X Original Android Development] tejaskary:
Though flashing the system partition will definitely lose root, right? Flashing this way may only help coming back to 4.4, but no root for sure on 4.4.2?
[Moto X Original Android Development] _litz:
Of that, I have no idea ... I guess if it doesn't work, you either keep 4.4.2, or roll it back to 4.4.

the key is NOT updating the bootloader/partition map, which retains that ability.
[Moto X Original Android Development] flashallthetime:
Avoid flashing the ota, if you do your done, the new bootloader can not be downgraded, so when the sbf firmware is available, open the zip and flash only the system, boot and modem img's. The 4.4.2 system will work with the older 4.4 boot loader fine but not the 4.2.2 boot loader, be aware , do not run the new 4.4.2 boot loader while running the 4.4 system img as this could possible result in a hard brick if by accident you accept the ota

Sent on my Gummy running Lenoto X
[Moto X Original Android Development] AaronCompNetSys:
There are lots of good facts from jcase scattered through this thread. Would a mod with some free time feel comfortable quoting them into the first page of this thread, either in his post or another post close to it?

Not sure if XDA supports post reordering, but I can update if you want to move this to #2.
[Moto X Original Android Development] ApriliaM3:
Done... you're now the OP of Post #2
[Moto X Original Android Development] AaronCompNetSys:
Thanks, I appreciate your promptness.

Other members, please scrutinize what I put in the post and let me know.
[Moto X Original Android Development] somerandomname1:
Complete Edit:

Just want to note that I just ran through this whole procedure no problem, but after the last step, it did not reboot automatically whether I waited or toggled bluetooth. I waited for about 5 minutes and then restarted myself. Still obtained root, but just mentioning in case it doesn't auto-reboot and confuse someone.
[Moto X Original Android Development] megapinky:
my carrier jump from 4.2.2 to 4.4.2 so i try to use SlapMyMoto before take ota, after take ota Write protection is enable again, i lost MotoWpNoMo so i lost root too :crying:
[Moto X Original Android Development] Atook:
Picked up a Verizon MotoX (non-dev) a week ago, And I'm trying to get impactor to work.

I keep getting 'Signature Bugs Unavailable' message when running impactor, so of course I can't telnet in.

Android version in 'About Phone' is 4.4. I haven't taken any OTA updates. I have enabled USB debugging, since I do develop apps.

Am I S.O.L.? I only wanted root to get free tethering.
[Moto X Original Android Development] lowvolt1:
You have to start on 4.2.2 use rsdlite to flash 4.2.2 then root with rockmymoto, then run motowpnomo, then flash back to 4.2.2, you will lose root. Then run the slapmymoto process. In that process you will be prompted to take the 4.4 OTA. If by chance you are prompted to take 4.4.2 OTA don't do it.
[Moto X Original Android Development] Atook:
Thanks for the quick response, that was the route I was going try next. I might wait for a few days till people have a good handle on what's going on with the 4.4.2 update.
[Moto X Original Android Development] lowvolt1:
The 4.4.2 update breaks the write protection enable mod. Meaning you will not be able to write to system.

Also it breaks the ability to downgrade which is needed to gain root. People are saying that you can fastboot push just parts of the update but we need the XML file first. Your best bet, don't take 4.4.2 if you want root.
[Moto X Original Android Development] Droidjava:
Can't boot into recovery

I have a Verizon Moto x and used Slapmymoto and MotoWpNoMo to root and remove write protect. When I power on holding down both the volume up and down while pressing the power on buttons, I get a menu to "Normal power on", "Recovery", "Factory" and so on. I then use the volume down to highlight recovery and the volume up to select recovery. Then the phone just powers on normally. Am I missing something? I've searched and everything I've read says thats how to boot into recovery to be able to flash a zip files, factory reset and clear cache.
[Moto X Original Android Development] lowvolt1:
You don't need to boot into recovery. Your write protection is disabled. Just freely make changes to system.
[Moto X Original Android Development] Droidjava:
Thank you for the quick reply. But how would I do a factory reset other than using the in software reset option.
[Moto X Original Android Development] lowvolt1:
Usually when I want to reset I just flash the XML using rsdlite.
[Moto X Original Android Development] M973:
Worried I didn't do this process quickly enough and only 4.4.2 will be available when I get to the take OTA option. Does anyone know about the statement above re: sideloading the 4.4 update in recovery with a locked bootloader if only 4.4.2 is available? :confused:

Thanks
[Moto X Original Android Development] _litz:
This is a good question... Verizon 4.4.2 OTA is out, basically, now ..

So this method will now BREAK the verizon people, as the OTA won't be 4.4 any more.

Instructions probably need to be changed to indicate a RSD-lite based upgrade to 4.4 instead of taking the OTA.

Edit - is the OTA file for the 4.4 update available (e.g., a .zip based update script, instead of the SBF)? That, presumably, could be flashed via recovery as a substitute for the OTA, correct?
[Moto X Original Android Development] M973:
And appears to be out for AT&T too
[Moto X Original Android Development] _litz:
FYI, for Verizon, I believe I've found the 4.4 update zip here :

http://downloadandroidfiles.org/download-blur_version-139-15-1-ghost_verizon-verizon-en-us-zip/
[Moto X Original Android Development] JarMagic:
Can't disable WP

What should be the easiest part of this, I can't get to work. Is there a trick to running the wp program? Maxx user on 4.2.2
[Moto X Original Android Development] lowvolt1:
Are you rooted? Can't run motowpnomo if your not rooted