[Replicant] [libsamsung-ipc] [PATCH] nv_data-imei: indicate that write-imei may or may not work

[Denis 'GNUtoo' Carikli]

I had two Nexus S: after breaking one, I've tried moving the
IMEI of the broken one on the working one:
- Earlier I did some backups of the EFS.
- I went into recovery mode
- I removed the .nv_data.bak and .nv_data.bak.md5 files
- I copied the .nv_data.bin to my computer and changed the
  IMEI with nv_data-imei
- I copied back the .nv_data.bin and the generated .nv_data.bin.md5
  and fixed the permissions.
- I booted the device

However not only the IMEI didn't change, but it was also set back
to the old one in the file.

I've also asked Paul Kocialkowski if he remembered if changing the
IMEI worked in his original code or on which device he tried it,
but he didn't remember.

So more information is probably needed to either understand if
that code is supposed to work and if so if there are conditions
in which it works or doesn't work (specific EFS, devices, etc).

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org>
---
 tools/nv_data-imei.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/nv_data-imei.c b/tools/nv_data-imei.c
index dfa3d86..8f4986a 100644
--- a/tools/nv_data-imei.c
+++ b/tools/nv_data-imei.c
@@ -244,7 +244,7 @@ static struct command commands[] = {
 	},
 	{
 		"write-imei",
-		"Store the given IMEI to nv_data",
+		"Store the given IMEI to nv_data (may or may not work)",
 		OPTION_FILE|OPTION_IMEI|OPTION_OFFSET,
 		OPTION_FILE|OPTION_IMEI|OPTION_OFFSET,
 		write_imei,
-- 
2.29.0