[Asus Transformer TF700] d14b0ll0s:
Perhaps some of you have already noticed, as I have recently, that there is something called Asus Device Tracker, which enables you to use a kind of stock backdoor in your device in order to - for example -

track it via GPS, read your data, take a picture, make a loud sound, wipe it or block it

"in case it gets stolen". It's nice to have something like this... but not as an obligatory app. And if you can do it with your device remotely when it's connected to the network, so can somebody else in power (ASUS, some hacker, the police, etc.).

So the question is - how do we disable it?

Edit: Seems that

CMClient

(and possibly DMClient) is responsible (see discussion below). Removing /system/app/CMClient* helps, but it could disable some functionality, however some preliminary attempts below say maybe it won't after all, unless you remove DMClient.

Edit:: The TF300 users are affected by this as well.

Edit: unknown_owner shared his story in this post: I found this thread after searching for more info on the Device Tracker. To make a long story short,

Asus has voided my Prime warranty saying my tablet has been rooted

. After digging into them about how they got that information knowing I never sent my tablet to them,

they said that they were able to get that from the devicetracker.asus.com website

. Not only is it used to used to track the GPS of your tablet, but apparently they are able to get system information as well and something in there told them that my tablet was rooted.

My tablet is not unlocked

though. So be careful what you do. [highlighting - d14b0ll0s]; see also his follow-up

Edit: Some info from my other posts combined:

I went throught logcat and it seems CMClient can even turn GPS on when it's off and do pretty much any nasty stuff to your device, as it communicates with ASUS servers via https and has all permissions it needs. Interesting. Android devices are as far from open (or free, from that matter) source, as they can be, if we end up with things like this. Freezing CMClient only worked initially, as another process woke it up after another call.

I've just removed CMClient.apk and CMClient.odex from /system/app/ and it won't lock the device remotely anymore, but it still receives the requests to do so through other processes.

It seems the device is still able to look for the OTA updates, DMCommunicator reports sending IMEI number (so this is how the batches are handled?) to https://mdm.asus.com/DMServer/AsusDMServlet and it reports back no new updates. On the other hand, removing DMClient removes OTA functionality completely (you won't even see "check for updates" in your settings menu).

It is not clear where the data is stored. ASUS denies storing it on their servers, while they certainly have access to it. Their support said it was being stored on Google servers, while it's nowhere to be seen on one's Google account. There is no option to opt out from the Device Tracker, too. The company's final statement on this so far seems to be this.

A simple tutoral added - follow this link.

Update: OTA fails if there is no CMClient.apk present:

Verifying current system...
failed to stat "/system/app/CMClient.apk": No such file or directory
file "/system/app/CMClient.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/CMClient.apk"

... so disconnect when you have the dlpkgfile, restore CMClient, update, restore root, remove CMClient, then reconnect to the WiFi.