As you can have multiple devices associated with the same account (even if they're all of the same brand and model) and still target them separately, there must be an identifier. Logical conclusion is that identifier being the GSF1
android_id. When you register your "replacement", a new
android_id will be created for your specific installation2, and stored with the device's configuration. This serves as device identifier for all related operations/interactions between your device and Google services, e.g. for GCM3 and Google Play (apps).
Hence I'd say it's safe to assume the same is used by ADM4, as it's part of Google Services as well. So as long as you don't restore a full backup of your old device, but register e.g. via the setup assistant, your replacement will get a new
android_id and thus not receive the "wipe request" addressed at a different
Another proof to that I've just found on Reddit: Someone had setup multiple devices using the same Nandroid backup taken from a fully configured device, and hence with the same
android_id. Result was ADM seeing them all as one device, always "communicating" with the last-used device.5 The issue was solved by resetting the ID.
References for further investigation
- XDA: What is the Android Device-ID?
- SO: GSF ID KEY (google service framework id) as Android device unique identifier
- Reddit: Multiple devices with the same android ID
1: Google Services Framework
2: This is done whenever you register a device, i.e. associate it with your Google account
3: Google Cloud Messaging, e.g. used in the SE app to notify you that you've been mentioned or got an answer to your questions
4: Android Device Manager
5: Quote: it seems like the last device booted is recognized online, the other one isn't