2

I had rooted my Samsung Galaxy S 4G, and for some reason it seems to be only partially rooted now. What I mean by this is that while SuperUser is installed, apps such as BusyBox and Titanium Backup are complaining that they cannot get root access. Using apps from the Google Play store, I can neither remove the root or re-root the device. I cannot get to the Recovery menu because the key combinations done at startup just end up rebooting my device. Why is this happening and what can I do to fix it? Resetting the phone to factory settings does nothing.

Despite all this, AVG Antivirus is complaining that my device is rooted. So, what's up with that?

0

I remember encountering a similar problem with superuser. I installed SuperSU from Google Play (replacing the superuser app), and it fixed my problems.

Update #1: As discussed over chat, jeffreylin_'s root was lost, as verified with Root Checker. To fix this, the phone must be rooted again. SuperOneClick can be used; no need to flash ROM or anything. Just run the tool. It supports Samsung Galaxy S 4G.

Edit #2: In case you want to protect root (after phone's been rooted), install OTA Rootkeeper, so you can just restore root if you mess it up.

  • But Super User came installed with my ROM... – user24200 Jul 23 '13 at 11:08
  • @jeffreylin_ Superuser is different from SuperSU. Look for SuperSU in Google Play. I posted the link in my answer. – geffchang Jul 23 '13 at 11:13
  • I pressed all the buttons, none of them work. It also seems that my SU binary is outdated. – user24200 Jul 23 '13 at 11:24
  • @jeffreylin_ What error messages are you seeing? – geffchang Jul 23 '13 at 12:16
  • It tells me that the SU binary is missing, and when I press the normal button, it says installation failed and exits. If I hit TWRP, it doesn't transfer me there, but instead let's me into the app. None of the settings do anything, such as 'install SuperUser into /system' and 'full unroot' – user24200 Jul 23 '13 at 12:24
0

You probably have su installed (the program that allows you to become root) but it may lack the right permissions to run. In this scenario, AVG is probably just checking if su is installed but apps that need root fail to run. You might be able to change the file permission using adb and chmod (I don't know the exact command but may be easy to google for it).

0

you could use chown command to give su its rights.

  • While this might help: How should Jeff accomplish that? Could you please edit your answer and include at least a short step-by-step instruction? – Izzy Oct 28 '13 at 14:12
0

In my case replacing SuperSU from the Play store did not fix the problem.

What did fix the problem was copying su from /su/bin to /system/xbin.