orangechoochoo
Active Member
Rootkeeper worked for me going from 219 to 206, so it should work if someone is going from 219 to 208. What we don't know is will rootkeeper work going from 206 to 208.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
[HOW TO] Install the leaked Android 4.0.4 ICS build on the Droid 4 (XT894)
- Thread starter r314bd
- Start date
The differences...
.219 (GB) to .208 (ICS) is that you are using the OTA "update" process which just updates your system.
.206 (ICS) to .208 (ICS) if possible using the same .200 (ICS) to .206 (ICS) process....your are fastbooting your system partition and a few others wiping them back to stock then updating a semi stock system to .208 (ICS).
I don't see OTA rootkeeper having the ability to retain root on a system that is fastbooted with stock images.
.219 (GB) to .208 (ICS) is that you are using the OTA "update" process which just updates your system.
.206 (ICS) to .208 (ICS) if possible using the same .200 (ICS) to .206 (ICS) process....your are fastbooting your system partition and a few others wiping them back to stock then updating a semi stock system to .208 (ICS).
I don't see OTA rootkeeper having the ability to retain root on a system that is fastbooted with stock images.
Voodoo OTA keeper did work when following the steps
View attachment 50843
View attachment 50843
droidian1441
Member
hey can you get me the kernel for 6.16.208? please?
orangechoochoo
Active Member
What were you coming from (GB or ICS)?
If you copy the blur_... file to your external SD card, update to .219 first then immediately update to to ICS 206 it will work. Just don't use RSD Lite, use the bootloader. Mine failed several times using RDS but it worked fine after I did the "STOCK" update then the ICS leak.
There is a new version of ICS out already, it's 208. I'd wait before trying it though...
droidian1441
Member
The way OTA rootkeeper works is to make a backup of su in the root directory as su-backup. It then executes it to regain root and copies it to /system/bin or /system/xbin thereby re-rooting the phone. So it will be able to retain root on a stock update. It doesn't really matter though, stock GB is easily rooted. Fastboot or update from sdcard makes no difference. Neither of them delete the root partition or any files in the root directory. None of the updates wipe the root file system so it should always work, unless you've trashed your root file system and the install has to rebuild it. The catch is the version of su it saves. When I installed ICS the version of su that was saved was compiled using the system relocatable library. One, or more, of the functions it calls is not in the ICS library, or it's renamed. Probably on purpose to make it harder. This prevents the su-backup from running successfully. I get a "relocat library error cannot find "_mktem" CANNOT LINK EXECUTABLE when I run it.
That is the very reason Dan Rosenberg stated he will not release the ICS root methood until the final ICS update is out for the D4, to prevent them (meaning verizon) from doing exactly what they did with the leak. Do you think it was really an oversight on the part of Moto that the ICS was leaked? Hardly, they want to know how it's going to be rooted.
From what I understand it's not Motorola that dislikes or blocks root access, it's Verizon. If you don't know why it's all about MONEY. They can't collect their extra $30 a month for tether or some of the other apps they charge for if you root your phone and run a different app to gain tethering. Since Moto is a "Partner" with verizon they have to bow to the wishes of the GODS and at least half-heartedly try to prevent root. It's obvious if they wanted to they could make the filename "su" an illegal filename, or install a blank file named "su" and make it unreadable/unwritable owned by user 0. This would effectively prevent the use of su.
Anyway...
Should work or work 100%?
This is my third droid4 and don't lost root. The other too d4 lost root.
...Tapatalk