Anyone rooted successfully accept new OTA update?

[dahlheim]

yes, those files appear to be there already. not sure if i'd be able to write them there otherwise if i've lost root, but i guess they don't seem to help...

 

[blaidth]

You are probably at this point going to have to sbf to 234 and reroot with z4, redownload cwr d2bootstrapper and then pull the update, or do the two file update.

 

[dahlheim]

yep, i figured that already. at the moment i'm just waiting to discover when i feel like i am needing root again, or when someone comes out with something new, or a different method, whichever of the three comes first. at least the phone is running nicely and everything i use regularly is working well.

 

[Flawson]

I just caught a p3droid tweet about a moto root exploit that works for dx... Need to investigate further

Sent from my DROIDX using Tapatalk

 

[PappaFloyd]

A 1click is around to I hear. On my way home to try!!

I just caught a p3droid tweet about a moto root exploit that works for dx... Need to investigate further

Sent from my DROIDX using Tapatalk

It

 

[jerseyboy357]

Here...

http://forums.androidcentral.com/motorola-x-rooting-roms-hacks/113766-root-method-602-dx-ota.html

 

[Dubbayoo]

I was on stock .596 rooted, took the OTA update; pulled the battery and reinstalled the superuser.zip via Droid2 bootstrap recovery after a battery pull.

 

[dahlheim]

the below method fixed my problem described above, for anyone interested.

Originally Posted by KevlarGibs
I didn't create the file, but they should be able to update it easily.
in the meantime, open the folder you extracted these files to.
(i'm assuming you are in windows 7 here)
hold Shift+right click a blank spot, select "open a command prompt here"
type: adb shell
when you hit enter, the next line should end with a #
if it's $, run the oneclick again, then start this over

once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
don't worry if it says it can't find the file... the point here is to get rid of it anyway

then run the oneclick again. worked for me
Thanks for helping out. I put a link to your post in my OP's for the DX crowd.

 

[rharv3#AC]

I was on stock .596 rooted, took the OTA update; pulled the battery and reinstalled the superuser.zip via Droid2 bootstrap recovery after a battery pull.

I did the same. Phone's running like a charm on .602 now with no bloat.

Sent from my Droid X most likely while tappin' and takin' a $#!%!!!

 

[rharv3#AC]

You can get the update while rooted.

Sent from my Droid X most likely while tappin' and takin' a $#!%!!!

 

[rharv3#AC]

no prob installing the ota from 596 rooted tbh, but lost root.

some here claim success, but i can't get back into clockwork recovery using the mentioned method(s)...

.602 rooted without SBF'g or wiping!

That way worked fine for me. The trick is to be totally on stock (Odexed) rooted .596 before taking the update. Once I got rid of my deodexed version, I was done in 20 minutes.

Sent from my Droid X most likely while tappin' and takin' a $#!%!!!

 

[jcarlosfox]

the below method fixed my problem described above, for anyone interested.

Originally Posted by KevlarGibs
I didn't create the file, but they should be able to update it easily.
in the meantime, open the folder you extracted these files to.
(i'm assuming you are in windows 7 here)
hold Shift+right click a blank spot, select "open a command prompt here"
type: adb shell
when you hit enter, the next line should end with a #
if it's $, run the oneclick again, then start this over

once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
don't worry if it says it can't find the file... the point here is to get rid of it anyway

then run the oneclick again. worked for me
Thanks for helping out. I put a link to your post in my OP's for the DX crowd.

These instructions were EXACTLY what was needed to root my phone - THANKS!!! (I used the one-click method).