Database Develop

[SCRIPT] Root for 4.1.57 (Depreciated, use newer version)

HTML:
The new update blocks the current ways of attaining root for the device. However, if you have root before you update, it is possible to retain this during the upgrade.
Script is online!
A newer version is available here:
http://forum.xda-developers.com/showthread.php?p=12540398#post12540398

Yeah... I'll just wait for you
Thanks for this! been holding out on the update ever since I found out you lose root during the beta testings

if this works i guess it's time to get my desktop back up and running so i can flash back and use this. damn power supplies dying on me.

ill wait for ur auto script
will this b possible btw neone?
Flash the 1.5.7 sbf -> run gblur custom rom -> run the root scrip

No Gingerblur needs root to push its files, also if you need a host I can host

Scripts are online!
Run beforeupdate.bat, update, then run afterupdate.bat.

Haven't tried it yet but wanted to say thanks and great work!

--EDIT -- BELIEVE THIS IS FIXED--
you didn't package the bin folder with psneuter.. :X

In reference to "adb.exe push movesu.sh /data/local/tmp > NUL 2>&1"
movesu.sh is now backup.sh, yes?
Also busybox "mv /system/xbin/su /system/bin/frozenfish" clobbers the copy from system/bin, if there is a difference, i thought it was generally a symlink to /system/bin.
Other than that, good idea in renaming the binary file, I probably won't use frozenfish in case Motorola targets that now..

Sounds sweet! If I already updated can I flash back to old then re root? Then run script then update?
Sent from my MB860 using XDA App
Update: Yes You Can ! just finished..

Whoops - I based it from adeo without making the proper changes. Corrected one should be live in a few minutes.

all good take your time..
so far the only corrections were the movesu.sh in beforeupdate.bat
and the missing /bin folder :X .. well technically you just need psneuter in there.. and just change the /bin/psneuter.. to /psneuter saves you time lol

The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.

curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work

"movesu.sh" is called but doesn't exist.

shawnbuck said:
The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.
Click to expand...
Click to collapse
Do you have the su that does not require Superuser.apk installed?

Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.

I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu

dLo GSR said:
curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work
Click to expand...
Click to collapse
Root here is a normal root, anything you could do before you'll be able to continue doing.
eval- said:
I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu
Click to expand...
Click to collapse
Thats right - I corrected that and added a new version.
OrangesOfCourse said:
Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.
Click to expand...
Click to collapse
Exactly right. I'll clarify the directions in the OP.
lpsi2000 said:
Do you have the su that does not require Superuser.apk installed?
Click to expand...
Click to collapse
This doesn't come bundled with a copy of su, it uses the one already installed in the system.

will this work on flash sbf?

Root instructions...

Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe

Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.

Any reason to not use the one click method? Seems to be working

bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.

Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.

Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .

MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.

Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?

Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.

navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App

MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.

Just so everyone knows. SuperOneClick can root and unroot this phone ok.

navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!

Thanks for posting this here for me Haxcid!
Sent from 1885

navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App

Is there recovery for this now? Did I miss something?

stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.

Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.

stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?

make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools

Maintain Root from V7 into OTA V8

This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.

Flashing back to v7 now to test this out.
:::EDIT::::
So far it is failing. I get to step 5 and I am not able to remount. Permissions denied.
Also your rar file has tripped my antivirus software.
Please post a link to any original instructions.
:::EDIT::::
Yep still fails completely at step 5. The root is not carried over at all.

These are original instructions. I emailed Dan (djrbliss). Your anti-virus picked up on one of the exploits contained in the .rar. Once you download even if your anti-virus removes one of the files the rest works fine. This is how I was able to keep root. It does work.
adding the ro.kernel.qemu=1 and the adb commands were from djrbliss.. the rest is all me
Just try the super1click.
in adb type "adb shell id" what is the output?
*Should read "uid=0(root) gid=0(root)" <--- if anything but, go back to /data/local.prop and make sure it is still there.. I might be crazy but think it disappeared once or twice on me..
then the S1C or just the adb commands from OP should work..
(Your anti-virus removed psneuter from the exploit folder.. not needed anyways)

I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
Click to expand...
Click to collapse
if you have any other issues beep me on IRC freenode #lgrevolution

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.
Click to expand...
Click to collapse
Glad to hear.. I was close to starting over from scratch to make sure I didn't miss something.. lol

Hmm, didn't work for me will try again later
Sent from my VS910 4G using Tapatalk
Edit: Got it working, typo for me too it's qemu not qenmu lol

JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..

Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol

drt054 said:
JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..
Click to expand...
Click to collapse
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
---------- Post added at 10:02 AM ---------- Previous post was at 09:55 AM ----------
dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
.
I flashed back using the tot file, rooted then proceeded from there. Once I fixed my ignorant spelling issues everything worked great. Now that I have renamed the prop file and rebooted sound seems to be working.
My issue is now battery. The phone with no use is eating battery like a thunderbolt. It has been off charger for 2 hours with no use and its down to 84%.

dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
Yes if you already have the V8 update in order to gain root you have to go back to V7 Stock firmware. If you are on GingerVolt 2.0 you have to flash the V7 Firmware to get back to LG-STock and Stock Recovery. The LG1click does NOT work on the V8 update so there is no CWM-Recovery, or GingerVolt at this time until MT figures out how once again..

Haxcid said:
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
SORRY!!!.. like I said didn't realize it until it happened, lost vibration and went to check my voicemail and no sound. But made that /data/local.prop into a .bak file, rebooted and was fixed. MT said has something to do with that entry in place the phone thinks it is a terminal emulator instead of a phone or something like that..lol So hopefully this is only temporary.
There may be a new root out soon.. not by me, like I said by someone much smarter than me may have found a way.
Click to expand...
Click to collapse

Worked like a charm DRT thanks so much!
Here is what I did:
1) Flashed MTs ZV7 Rooted Stock (RevoZV7GBStock.zip)
http://forum.xda-developers.com/showthread.php?t=1348637
2) Created the local.prop file, etc.
3) Used MTs All-in-One tool to flash Stock Recovery (Option 5)
http://forum.xda-developers.com/showthread.php?t=1348557
4) Downloaded and installed the ZV8 update OTA
5) Used ADB to push files per DRT instructions
6) Rebooted
7) Confirmed that I still have root using Root Checked Basic!
A little bit different than DRTs posted method but I wanted to avoid having to use LGNPST, so at least I can confirm that this alternate approach works as well!

drt054 said:
This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.
Click to expand...
Click to collapse
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks

Nckmsn said:
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks
Click to expand...
Click to collapse
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium

elreydotcom said:
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.

Haxcid said:
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.
Click to expand...
Click to collapse
Ive been unable to get the adb part to work. I can't get the adb command line to come up on my pc. Anyway, so I'm on v7 unrooted with no sound. I have change the name of the prop file and even removed it but my sound wont come back. Do i need to complete the whole process for the sound to come back?

If you are unrooted you can't create the file, you need to get rooted first. Use the all in one package to root.
Sent from my VS910 4G using xda premium

Once I was able to finsh the entire process, I managed to rename the prop file and all sound came back. success!
Thanks

Made a post in another thread but any word yet I how we get CWM recovery from rooted zv8?
edit: MT let me know that I needed to recreate the prop file, reboot, and then choose the root option in his new all in one package for ZV8...worked like a charm!
Sent from my VS910 4G using xda premium

OTA Update! SW Version: 98.72.18-8

Hi, everybody!
Several days ago i've got OTA update from VERIZON. You can download it from attach.
Changelog from official Motorola site
I agreed and installed this update. After it i had 98.72.18-8 SW version.
So, i have had the trouble: i couldn't got root rights by Dan Rosenberg exploit - Motorola fixed the way, we had root on previous JB 98.72.18 and 98.72.18-2 !
After analysing install-script file from OTA update and thinking around it i decided to downgrade with RSDLite to 98.72.18 and do some manipulations with SU binary:
Start point: 98.72.18-2 installed, rooted
Code:
adb kill-server
adb start-server
sleep 5
adb shell su -c "mount -o remount,rw /system"
adb shell su -c "cd /system/bin/ && mv run-as run-as2 && mv /system/xbin/su run-as" #because of script do chmod on this file
adb reboot recovery
#turn on Sideload manually in recovery
adb sideload Blur_Version.98.72.182.XT894.Verizon.en.US.zip
sleep 400
adb kill-server
adb start-serversleep 5
adb shell run-as -c "mount -o remount,rw /system" #i used RUN-AS instead SU =)
adb shell run-as -c "cd /system/bin/ && mv run-as /system/xbin/su && mv run-as2 run-as"
adb shell su -c "chmod 6755 /system/bin/su"
this way gave me root rights for adb Shell, but applications still not getting root.
Any ideas, how to fix?))
Sorry for mistakes, i've tryed to avoid it)

way to fix
So, i fixed it!
1. At the start, we have 98.72.182 system, rooted by Dan Rosenberg exploit
2. Installing Safestrap recovery
3. Downloading on sdcard-ext latest SuperSU
4. Under Safestrap, installing UPDATE-SuperSU-v1.89.zip
5. Reboot to stock Android, bying SuperSu pro key, installing
6. Going to settings, and uncheck Screen block (set NONE)
7. Going to Superuser -> settings, install checkboxes: Survival mode, Enable su during boot, Trust system user
8. Reboot to the stock recovery, installing OTA update
9. Booting to OS.... (After booting you can return screen block )
10. Enjoy!

Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk

rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I can take a video with Vodoo, which will fail with restoring root.
Before posting, i've tryed voodo ota keeper, and ota keeper function in another superuser software)

Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat.
Update.....
I tried voodoo and the OTA would not come through for me. It looks like the update will be more complicated than it's worth so the kitkat rom's will be in my near future.

Voodooo worked for me on latest O.T.A
karlsdroids said:
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat
Click to expand...
Click to collapse
Voodooo worked for me on latest O.T.A

rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
mercermtn said:
Voodooo worked for me on latest O.T.A
Click to expand...
Click to collapse
Voodoo worked for me too. Just got the OTA notice today from VZW. Followed rruleford's steps and it worked.
This was my first time using Voodoo, and possibly my imagination or possibly not - but something funky happned where I needed to reboot the phone and re-check enable in SuperSU, which was obscured by the fact Voodoo was stating it ~had~ root...

So, is there anything besides these bugfixes in the update? Any Android version updates or maybe a fix for the Shift key behaving like a lunatic?

Dang.
My wife already applied the update to her D4 and now I've lost root on that device. Can anyone advise me what to do? Should I use RSDLite like OP states? I am confused because Moto SBF page says "never flash an older version"...

tried using voodoo and the update wouldn't work...dono what to do.

svrnmnd said:
tried using voodoo and the update wouldn't work...dono what to do.
Click to expand...
Click to collapse
Did you disable SuperSU after you backed up w/ Voodoo?

Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app

svrnmnd said:
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...

bigmatty said:
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
Click to expand...
Click to collapse
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk

rruleford said:
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?

Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk

bigmatty said:
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Click to expand...
Click to collapse
Not to sure as I deleted all mine when installing cm11 on stock ROM slot. Try above method with RAZR blade?
Sent from my XT894 using Tapatalk

tcrews said:
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
On 1 & 2 - not entirely sure anyone said to unroot or unfreeze, but I did read where it was advised to 'temp disable root', and when I followed that step voodoo did work great to allow me to update and restore root.
THANK YOU for 3!! I assumed based on some of the other comments that it didn't work. I just tried it on the other phone, and it DID restore root. VERY MUCH appreciated!!

So I use voodoo to unroot I disabled superuser but the update starts and fails everytime, I don't know why, the little android starts to update, then just gets a red x through it...
Sent from my DROID4 using xda app-developers app

I have quite a few apps frozen, but apparently nothing that prevented the install from being downloaded automatically. I unrooted with Voodoo, installed the update, restored root and all is well.

[Q] Official update January 2014

Hi everybody!
I noticed there is another update...it should not be so strong, just minor fixes...
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/97885/p/30,6720,8302/action/auth
I haven't done it yet, but after 12 hours I have always the notice about it.
I'm using Droid 4 in Europe, so I'm not so interested.
Anyway, do you know if I will lose the root permission?
Thanks!

I currently have 98.72.18.XT894.Verizon.en.US and 4.1.2, so I'm curious as to what the new updates are for the xxxxxx.188 and xxxxx.189. I would suggest something like VooDoo OTA to attempt to save your root but there is no guarantee that it will protect it if Motorola has figured out how to patch the exploit.
From Motorola, new software is .....
98.72.188.XT894.Verizon.en.US or 98.72.189.XT894.Verizon.en.US

Voodooo worked for me on latest O.T.A
karlsdroids said:
I currently have 98.72.18.XT894.Verizon.en.US and 4.1.2, so I'm curious as to what the new updates are for the xxxxxx.188 and xxxxx.189. I would suggest something like VooDoo OTA to attempt to save your root but there is no guarantee that it will protect it if Motorola has figured out how to patch the exploit.
From Motorola, new software is .....
98.72.188.XT894.Verizon.en.US or 98.72.189.XT894.Verizon.en.US
Click to expand...
Click to collapse
I used Voodoo root keeper for the latest ota update. Worked for me. Just needed to reinstall SU

mercermtn said:
I used Voodoo root keeper for the latest ota update. Worked for me. Just needed to reinstall SU
Click to expand...
Click to collapse
ok! thank you for your answer...
except for what mentioned by Motorola, the update changes something else? I mean speed or other aspects?

Same with voodoo here, didn't uninstall the SU app though
Sent from my XT894 using Tapatalk

Using voodoo to temp unroot and install the update did not work for me. I've decided to pass on the update and instead I'll just do a different rom. I found what the update consisted of and basically it's "bug fixes and security updates"- no real benefit there for me.

woodoo didn't work for me...can I use the same procedure to root again?
Sent from my DROID4 using xda app-developers app

For those who failed with voodoo, you could try Saferoot, it harmless to try...
Just root my RAZR HD although it designed for VZW Galaxy S4...
http://forum.xda-developers.com/showthread.php?t=2565758

I used voodoo on my wife's phone. Saved the su binary, installed the ota, clicked restore root. Voodoo said root restored but the check box for root stayed empty and root apps didn't work (like titanium backup). Found a post that gave terminal commands to manually restore the su backup. Worked perfectly and I now have root back. I forgot the link but luckily I copied and pasted the steps. So If voodoo said it worked but didn't, give this a try...
(I'd give credit where credit is due but lost the link)
"My wife's Transformer Infinity exhibited basically the same behaviour after its last 2 updates (both 4.2.something, IIRC). Fortunately the backup copy of su was intact, as it likely is in your case, and I was able to restore it manually using a terminal emulater app... adb would presumably have worked as well, but my notebook wasn't available at the time. Here's what I did.
.
1. Launch the terminal emulater of your choice (I used Better Terminal Emulater Pro, but the specific app probably doesn't matter)
.
2. Go to the location of the backup copy.
===========================
cd /system/usr/we-need-root
===========================
.
3. Use the su backup to obtain a root shell. This should trigger the usual superuser popup/notification, assuming that it's configured to do so.
=================
./su-backup -
=================
.
4. Remount the /system partition in read/write mode.
============================
mount -o remount,rw /system
============================
.
5. Copy the su backup to the proper location, taking care to keep the permissions intact.
=============================
cp -p su-backup /system/xbin/su
=============================
.
6. Remount the /system partition in the normal, read-only mode.
=============================
mount -o remount,ro /system
=============================
.
7. Reboot the device (might not be strictly required), to ensure that any root-enabled background apps are able to startup cleanly.
.
The usual disclaimers apply, of course. Your device might not have the same configuration as mine, etc., so these commands may need some tweaking. Also, if it was a 4.3 upgrade which caused you to lose root then this procedure likely won't work... I believe that su needs to be running in daemon mode in order to grant privileges, which certainly won't be the case for the backup copy (even if it is a 4.3-compatible version).

squall90x said:
Hi everybody!
I'm using Droid 4 in Europe, so I'm not so interested.
Thanks!
Click to expand...
Click to collapse
I too use this in Europe, and made the mistake of accepting this OTA update, which bricked my data connectivity. More info in this post:
http://forum.xda-developers.com/showpost.php?p=49627296&postcount=23

mike-phone said:
I too use this in Europe, and made the mistake of accepting this OTA update, which bricked my data connectivity. More info in this post:
http://forum.xda-developers.com/showpost.php?p=49627296&postcount=23
Click to expand...
Click to collapse
My data connectivity works without problems...

squall90x said:
My data connectivity works without problems...
Click to expand...
Click to collapse
Your reply inspired me to dig a bit deeper. It looks like the OTA update just cleared the list of APNs. I re-added the APN, and it works fine. Thanks.

mike-phone said:
Your reply inspired me to dig a bit deeper. It looks like the OTA update just cleared the list of APNs. I re-added the APN, and it works fine. Thanks.
Click to expand...
Click to collapse
You're welcome!
Sorry I didn't tell you...it was the same also for me!!

androitri said:
For those who failed with voodoo, you could try Saferoot, it harmless to try...
Just root my RAZR HD although it designed for VZW Galaxy S4...
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Thank you so much for this link. I accepted this OTA update about a week ago and lost my root access, despite having run Voodoo OTA Rootkeeper (maybe I did something wrong?) I tried to re-root it using the Razr Blade tool (which is what I had used originally to get root access), but that didn't work. Apparently motorola/verizon plugged the smart action security hole. But this one (saferoot) got the job done. Back to wifi tethering; thanks!
Richard
edit: I have the Droid 4 XT894, and the OTA update which broke my root was 98.72.189.XT894.Verizon.en.US

squabeggz said:
I used voodoo on my wife's phone. Saved the su binary, installed the ota, clicked restore root. Voodoo said root restored but the check box for root stayed empty and root apps didn't work (like titanium backup). Found a post that gave terminal commands to manually restore the su backup. Worked perfectly and I now have root back. I forgot the link but luckily I copied and pasted the steps. So If voodoo said it worked but didn't, give this a try...
(I'd give credit where credit is due but lost the link)
"My wife's Transformer Infinity exhibited basically the same behaviour after its last 2 updates (both 4.2.something, IIRC). Fortunately the backup copy of su was intact, as it likely is in your case, and I was able to restore it manually using a terminal emulater app... adb would presumably have worked as well, but my notebook wasn't available at the time. Here's what I did.
.
1. Launch the terminal emulater of your choice (I used Better Terminal Emulater Pro, but the specific app probably doesn't matter)
.
2. Go to the location of the backup copy.
===========================
cd /system/usr/we-need-root
===========================
.
3. Use the su backup to obtain a root shell. This should trigger the usual superuser popup/notification, assuming that it's configured to do so.
=================
./su-backup -
=================
.
4. Remount the /system partition in read/write mode.
============================
mount -o remount,rw /system
============================
.
5. Copy the su backup to the proper location, taking care to keep the permissions intact.
=============================
cp -p su-backup /system/xbin/su
=============================
.
6. Remount the /system partition in the normal, read-only mode.
=============================
mount -o remount,ro /system
=============================
.
7. Reboot the device (might not be strictly required), to ensure that any root-enabled background apps are able to startup cleanly.
.
The usual disclaimers apply, of course. Your device might not have the same configuration as mine, etc., so these commands may need some tweaking. Also, if it was a 4.3 upgrade which caused you to lose root then this procedure likely won't work... I believe that su needs to be running in daemon mode in order to grant privileges, which certainly won't be the case for the backup copy (even if it is a 4.3-compatible version).
Click to expand...
Click to collapse
After some days I found time to try...
I put the same command and reboot and it worked!!
Thank you so much!!