I flashed to the new 4.0.4 ICS update from the google page. Now I can't get su to work. When I try to run titanium backup it says it doesn't have root access. When I run super user and try to run updates, it also says it can't get root access. Am I missing something? I installed the new stock image, softbooted into cwm, pushed the su, and applied it through cwm.
I lost root as well and downloaded a new su.zip replacement from here Hotfile.com: One click file hosting: su.zip - droped it on the root of the Gnex and flashed in CWM recovery, rebooted and hey presto, root was restored (didn't delete previous su etc.). The reason I looked for a new su.zip was that I think each ROM requires a slightly modified su file, although I'm not 100% certain. In any event the original su was just over 1MB and the replacement I found is around 679KB.
P.S. mine is the jakju (GSM) version but I think the rooting file should work on a CDMA version as well - not entirely shure though.
Last edited by heat57; March 30th, 2012 at 04:49 AM.
The Following User Says Thank You to heat57 For This Useful Post:
SuperUser comes in 2 parts. The apk file that controls access by asking you and the binaries that do the actual stuff. I'd imagine its the second that gets wiped by an update. It's an overwrite after all and I wouldn't imagine everything would survive.
The Following User Says Thank You to GrenW For This Useful Post:
I would think that the older su.zip flashable root installers should still work, regardless of the ROM or version of Android--as long was you have a custom recovery that's compatible with the update binary that's referenced by the recovery (CWM changed to a newer edify format a while back).
I'm curious about the su.zip file that you linked below, heat57, to see if it differs materially from the one that's mainly referenced here at AF.
When an OTA is applied, the /system partition's files are stripped of their suid/guid permissions, so that's why the su binary get's disabled (its usually still there).
The OTA RootKeeper app is great for "saving root" ahead of an OTA and for "restoring root" after installing the OTA. Or, if you have a custom recovery installed or soft-booted, flashing an su.zip root installer works great, too.
Such I noob I am. On a side note to my question, I initially bought a Canadian Nexus and did the How to change from yakjuux to yakju – Galaxy Nexus | Xtremel, I followed the same instructions to update to the new release (4.0.4). I lost everything (because I am an ultranoob). In the future, if I want to update a stock ROM, which step of that process to I skip to not lose everything (I also will be better about backups, just in case)?
On a side note, I noticed on the su page that is says ICS is supported up to 4.0.3, not sure if this is was the problem. I found this How to: Root Android 4.0.4 on the Galaxy Nexus – Droid Life to install that su file and then was able to update it in the market (couldn't update the other one) and it seems to be working now. Hoping for an "official" su update to come down.
The Following User Says Thank You to pappabacon For This Useful Post:
Such I noob I am. On a side note to my question, I initially bought a Canadian Nexus and did the How to change from yakjuux to yakju – Galaxy Nexus | Xtremel, I followed the same instructions to update to the new release (4.0.4). I lost everything (because I am an ultranoob). In the future, if I want to update a stock ROM, which step of that process to I skip to not lose everything (I also will be better about backups, just in case)?
On a side note, I noticed on the su page that is says ICS is supported up to 4.0.3, not sure if this is was the problem. I found this How to: Root Android 4.0.4 on the Galaxy Nexus – Droid Life to install that su file and then was able to update it in the market (couldn't update the other one) and it seems to be working now. Hoping for an "official" su update to come down.
Scary Alien is without question right - he is an expert, I'm not. There is only one thing to add "more than one way leads to Rome". Whatever gets you to the desired end result is fine. Although following Scary's advice probably saves a lot of time
I would think that the older su.zip flashable root installers should still work, regardless of the ROM or version of Android--as long was you have a custom recovery that's compatible with the update binary that's referenced by the recovery (CWM changed to a newer edify format a while back).
I'm curious about the su.zip file that you linked below, heat57, to see if it differs materially from the one that's mainly referenced here at AF.
When an OTA is applied, the /system partition's files are stripped of their suid/guid permissions, so that's why the su binary get's disabled (its usually still there).
The OTA RootKeeper app is great for "saving root" ahead of an OTA and for "restoring root" after installing the OTA. Or, if you have a custom recovery installed or soft-booted, flashing an su.zip root installer works great, too.
Thanks for the information Scary. I did (what I shouldn't have) a full new installation of 4.0.4 from google which erased everything. So when I softbooted into cwm I put su on there and flashed it, it said it worked. When I turned the phone on the su icon was there but it said it couldn't get root. I tried to take it off, reboot, put it back on, still couldn't make it work.
Thanks for the information Scary. I did (what I shouldn't have) a full new installation of 4.0.4 from google which erased everything. So when I softbooted into cwm I put su on there and flashed it, it said it worked. When I turned the phone on the su icon was there but it said it couldn't get root. I tried to take it off, reboot, put it back on, still couldn't make it work.
I've looked at the su.zip that referenced in the "CWM Method" of rooting in the main stickies quite closely and I'm not sure it wouldn't work on a 4.0.4 version of stock...
I obviously can't install the 4.0.4 version if its only out for the GSM devices, but I'll take a look again (at the su.zip) to see if there's something obvious (like an assert check, etc.).
I've looked at the su.zip that referenced in the "CWM Method" of rooting in the main stickies quite closely and I'm not sure it wouldn't work on a 4.0.4 version of stock...
I obviously can't install the 4.0.4 version if its only out for the GSM devices, but I'll take a look again (at the su.zip) to see if there's something obvious (like an assert check, etc.).
Apologies for not posting back here sooner...
I looked at the new root su.zip that heat57 provided right after we discussed this and its a very simple, very straight-forward root binary installer.
I finally remembered this thread and promise and got-around to testing this tonight on a stock 4.0.4 install on my VZW (LTE) Galaxy Nexus. The old (admittedly somewhat convoluted su.zip) still works just fine on the 4.0.4 version of ICS for my device--the su and Superuser.apk were installed just fine.
[by the way, I say convoluted above since the update-binary (which is actually a script) for the original su.zip takes a somewhat circuitous route to installing the su and Superuser.apk vs. the su.zip that heat57 referenced].
Anyway, not sure why folks would have had problems with the old su.zip--I would still think that it would work just fine, even on a 4.0.4 GSM device.
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
Flashed to ICS 4.0.4 and now SU wont work
