diff options
author | Martin Szulecki | 2010-07-08 19:10:00 +0200 |
---|---|---|
committer | Martin Szulecki | 2010-07-08 19:10:00 +0200 |
commit | 742d9e87ad40c6d338ea2bf050ea5fb527a59b58 (patch) | |
tree | d53c52c7d4d7de0e33a4b93c2dac04c8c7604e63 | |
parent | 410767972692ac699f7f7b40a65467fe9824a623 (diff) | |
download | idevicerestore-742d9e87ad40c6d338ea2bf050ea5fb527a59b58.tar.gz idevicerestore-742d9e87ad40c6d338ea2bf050ea5fb527a59b58.tar.bz2 |
Improve error message if a device mode can not be determined
Most of the time it means that there is no device attached as we
should be able to detect any mode of a device.
-rw-r--r-- | src/idevicerestore.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/idevicerestore.c b/src/idevicerestore.c index 6b17ad3..2a7a96b 100644 --- a/src/idevicerestore.c +++ b/src/idevicerestore.c @@ -126,7 +126,7 @@ int main(int argc, char* argv[]) { // check which mode the device is currently in so we know where to start if (check_mode(client) < 0 || client->mode->index == MODE_UNKNOWN) { - error("ERROR: Unable to discover current device state\n"); + error("ERROR: Unable to discover device mode. Please make sure a device is attached.\n"); return -1; } info("Found device in %s mode\n", client->mode->string); |