You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a recent OTA update, I was left with a non-setuid /system/bin/su. OTA Rootkeeper seemed to be confused by this, thinking the device was rooted, but unable to get root. As a result, the only buttons available on the UI were temp un-root (which didn't work because /system/bin/su didn't grant root) and delete su backup (Noooooo!).
Thankfully I was able to use a terminal app to manually restore rootkeeper's su backup, but it would be much preferable if it handled this situation properly itself.
The text was updated successfully, but these errors were encountered:
After a recent OTA update, I was left with a non-setuid /system/bin/su. OTA Rootkeeper seemed to be confused by this, thinking the device was rooted, but unable to get root. As a result, the only buttons available on the UI were temp un-root (which didn't work because /system/bin/su didn't grant root) and delete su backup (Noooooo!).
Thankfully I was able to use a terminal app to manually restore rootkeeper's su backup, but it would be much preferable if it handled this situation properly itself.
The text was updated successfully, but these errors were encountered: