[Eee Pad Transformer Q&A, Help & Troubleshooting] boogje@:
Ok, so this is the problem:

I have a TF101, rooted since 3.2. I have been able to do OTA updates without problems so far, keeping my root with OTA Rootkeeper.

Last week, I tried figuring out how to automatically mount cifs-shares through Tasker. Whatever I tried, the share would not mount through Tasker. It mounted without problems through command line in Terminal Emulator.

Eventually, i narrowed it down to a root acces problem in Tasker, or the Locale Execute plugin, or the secure settings plugin. I noticed that neither of those had ever asked for SU-acces and there were no logs of it in the Superuser app. When downloading other root-needing apps (e.g. rootchecker), I had the same problem: whenever a new app would normally ask for root acces, instead of the usual Superuser-prompt, the app stalled for a few seconds and then gave an error message or just plain nothing. There was no log of this in the superuser app.

When setting the superuser app to 'always grant root', the situation stayed the same: new apps didn't get root, older apps still had root without problems.

While searching for similar occurences on the internet, I saw a suggestion somewhere to clear the cache and data for the superuser app, so I did.

Now superuser still doesn't prompt and NONE of my apps have root. Apparently even the superuser app itself has no root acces anymore, since it fails to get root acces when updating the su-binary.

My guess was that completely removing su and the superuser app and subsequently re-rooting the whole thing would fix this.

I tried unrooting/rerooting through various methods (Brk, Vipermod, this one, and the new Wolf's thingy), but to no avail.

Brk tells me eveything worked fine, but changes nothing, except it gave me an even older version of the su-binary.

Vipermod hangs on "daemon started succesfully" but apparently does nothing even after 10 minutes.

The Asus Backup Utility method changed absolutely nothing

The Wolf's method looked promising, but installing the "Superuser-3.0.7-efghi-signed.zip" failed. (maybe because I did this from CWM recovery instead of his recoveryblob recovery? Dunno.)

So far I can't seem to remove root, as OTA Rootkeeper assures me the superuser app is installed and the device is rooted, even if the root acces is not granted to it (or any other app).

Any ideas?

Update: tried installing SuperSU from CWM recovery to replace Superuser app, but it gave the same 'installation aborted' message. Is this because CWM has no root acces also?

update2: I have root acces through adb shell apparently. I looked here and here for a way to replace the superuser app. I managed to remount /system, delete Superuser.apk and push the Superuser.apk and su from "Superuser-3.0.7-efghi-signed.zip" onto the device.

No apparent change, not even in the su binary version number reported by Superuser app.

I downloaded the standalone su-binary from here too, and replaced /system/bin/su with that one, too, but after reboot the Superuser app still indicated su binary version 2.3.2-efgh.

I don't know exactly when this problem started, but it could have been caused by the recent update from 9.2.1.17 to 9.2.1.21? Is it possible to revert to the previous version? If so, how? Would I lose data/apps?