To reset the data/cache you need to load into fastboot recovery. To do so:
1. Turn off your Droid 4
2. Power on your Droid 4 while holding both volume keys in
3. Your Droid 4 will boot into Fastboot (black and whit menu)
4. It sounds funny, but press volume down, and then volume up and the screen will change to the motorola dual core logo(like 30 seconds), then load the android with a caution sign.
5. At the android caution screen, simultaneously press the volume up and down buttons.
6. Voila, you are in stock recovery, and you can wipe data/cache, or apply OTA updates manually. The volume keys control "UP" and "DOWN", whereas the power button acts as "ENTER"
---------- Post added at 04:54 PM ---------- Previous post was at 04:52 PM ----------
Basically what I did though, was mess around until I got the unroot exploit to make my superuser.apk dissappear. That is the key, once you are completely unrooted with no superuser.apk, you should be able to run the root exploit again.
So here's what I'm trying. First I wipe the Dalvik/cache/data in both the Safestrap and Moto recovery. Then, once the phone is rebooted, I try the root method. It fails (see below). Then I try unroot. It still fails to remove superuser. Then I try running Root again and it fails again.
Any other tips? I just can't seem to get rid of the superuser.apk. I've been at it for hours with basically the same results.
When I run the root option, here's what I get:
Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
Device found.
Deploying payload...
3440 KB/s (359392 bytes in 0.102s)
Owning phone...
Waiting for phone to reboot.
* daemon not running. starting it now *
* daemon started successfully *
Root successful! Persisting...
remount succeeded
3639 KB/s (22364 bytes in 0.006s)
link failed File exists
2481 KB/s (1867568 bytes in 0.735s)
3120 KB/s (843503 bytes in 0.264s)
Cleaning up...
Rebooting...
* daemon not running. starting it now *
* daemon started successfully *
Exploit complete!
When I run the unroot option here's what I get:
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
--- Superuser check successful
--- cleaning
rm [-rR] <target>
--- pushing busybox
3188 KB/s (1867568 bytes in 0.572s)
--- correcting permissions
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
mount: permission denied (are you root?)
--- pushing unroot script
535 KB/s (1645 bytes in 0.003s)
--- correcting permissions
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
--- Starting unrooting script on DEVICE
--------------------------------------------------------------------------
--- DooMLoRD Unrooting script v1.0
--- part of Easy rooting toolkit
--- based heavily on FlashTool scripts maintained by Bin4ry and Androxyde
--------------------------------------------------------------------------
--- correcting path
--- correcting busybox permissions
--- cleaning busybox in /system
--- removing busybox symlinks from /system/bin
--- removing busybox symlinks from /system/xbin
--- removing busybox from /system/bin
--- removing busybox from /system/xbin
rm failed for /system/xbin/busybox, Read-only file system
--- busybox cleaned
--- removing SU files
--- removing su from /system/bin
rm failed for /system/bin/su, Read-only file system
--- removing su from /system/xbin
rm failed for /system/xbin/su, Read-only file system
--- removing Superuser app
rm failed for /system/app/Superuser.apk, Read-only file system
rm failed for /data/app/com.noshufou.android.su-1.apk, No such file or directory
--- removing Superuser app data
rm failed for /data/data/com.noshufou.android.su, Permission denied
--- SU cleaned
--- COMPLETED unrooting script on DEVICE
--- cleaning
rm [-rR] <target>
--- rebooting
ALL DONE
Press any key to continue . . .
When I look at the Voodoo OTA rootkeeper, it shows that the device is rooted, but that root permission has not been granted.
When I try ADB to delete superuser.apk, it says that it is a Read-only file system.
I wonder.... when you run the exploits, are you making sure your phone is in charge-only mode, and the screen is unlocked and on. Also, when it reboots, make sure to unlock your screen as well. I know it sounds silly, but hey, I felt it was hopeless in your situation and got root back, so GOOD LUCK!
I wonder.... when you run the exploits, are you making sure your phone is in charge-only mode, and the screen is unlocked and on. Also, when it reboots, make sure to unlock your screen as well. I know it sounds silly, but hey, I felt it was hopeless in your situation and got root back, so GOOD LUCK!
Yeah, I've double checked that it's in charge only and I unlock as soon as it reboots. I'm still working at it. I'm determined to get this done tonight!
Thanks for the pointers.
---------- Post added at 06:24 PM ---------- Previous post was at 05:30 PM ----------
I GOT IT!!!
It took a while, but I finally got the Superuser off of the phone! Rerooting now!
I got into ADB and finally didn't get rejected for file permissions. Then did the usual
su
mount -o rw,remount /dev/block/system /system
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/bin/su
Hi, I'm having problems getting the update on my rooted Droid 4. I'm pretty sure it's because I screwed with my build.prop file though. I wanted to get the Order and Chaos app and disguised my phone as a Droid 3 so I'd be able to download it. Now I could care less about it..
I first factory resetted my phone and on-board system memory, in hopes that this would restore the original build.prop file. (I'm a bit of a novice.) When this didn't work, I re-rooted my phone.
I went and replaced my current build.prop with rumgool's build.prop (in the Motoblur Update 219 thread.) (i.e. I carfeully copied their build.prop and pasted it directly into mine with no changes to [the stock].)
I then used the VooDoo OTA app to back up my root and temporarily un-root my phone.
Next I downloaded and saved Blur_Version.6.13.215.XT894.Verizon.en.US.zip to my micro-SD card.
I restarted my phone, and booted into recovery mode.
When I select the option to apply the update from sdcard, and select the file, I get this error message:
I went and replaced my current build.prop with rumgool's build.prop (in the Motoblur Update 219 thread.) (i.e. I copied their build.prop and pasted it directly into mine with no changes.)
I'm new to this, what do you mean "fix the permissions?" My phone is rooted, so is this something that has to do with Superuser, or the build.prop itself?
I'm new to this, what do you mean "fix the permissions?" My phone is rooted, so is this something that has to do with Superuser, or the build.prop itself?
Ahh sorry I didn't reply quicker, just got back from dinner. If you notice when you look at the build.prop file in Root Explorer, it will have "permissions" listed next to it. The permissions for the build.prop file should be "rw-r--r--" but rumgool's file has permissions "---rwxr-x"
When you copy it over to the system folder, click "Mount R/W" then paste/overwrite the build.prop file, then long press the file and click "Permissions." Make sure all three boxes under the "Read" column are checked, and also that the first box (Owner) under "Write" is checked, and everything else is unchecked, then press OK.
Then make sure the permissions for the build.prop file now say "rw-r--r--" and hit the "Mount R/O" button.
When you side load the update via stock recovery it goes through the file just like safe strap or clockwork would when installing a rom.
All I did to replace it was delete the old one from system and then moved the downloaded unmodified one back in the system folder with root browser rebooted then went back into stock recovery and flashed the update. I was a bit nervous when deleting the old one but it worked out perfectly.
Ahh sorry I didn't reply quicker, just got back from dinner. If you notice when you look at the build.prop file in Root Explorer, it will have "permissions" listed next to it. The permissions for the build.prop file should be "rw-r--r--" but rumgool's file has permissions "---rwxr-x"
When you copy it over to the system folder, click "Mount R/W" then paste/overwrite the build.prop file, then long press the file and click "Permissions." Make sure all three boxes under the "Read" column are checked, and also that the first box (Owner) under "Write" is checked, and everything else is unchecked, then press OK.
Then make sure the permissions for the build.prop file now say "rw-r--r--" and hit the "Mount R/O" button.
Let us know if that helps
Hey! It worked! Previously I wasn't replacing the entire file, just copying and pasting the contents of rumgool's over mine. Then again, I was using Astro, and not Root Explorer. Thank you so much!
Will I have to go through a similar process when installing ICS when it comes out?
Will I have to go through a similar process when installing ICS when it comes out?
Hopefully not...I'm not sure what caused the build.prop file to be modified in the first place but a lot of people including myself had the same issue and it is a bit unusual.
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
Droid 4 Update
Print
Email
View Profile
View Forum Posts
Linear Mode
