[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Very bad news.

I appear to have had an accident with /efs. Not 100% sure what I did but suspect it related to a product code change.

My SGS2 now will not show an IMEI or connect to the cell network.

I connected with /adb and saw a number of files were updated earlier today

drwxrwxr-x 5 root root 4096 Jan 1 2000 .files

drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei

-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log

-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state

-rwx------ 1 radio radio 32 Jan 1 2011 .nv_data.bak.md5

-rwx------ 1 radio radio 2097152 Jan 1 2011 .nv_data.bak

-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5

-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak

-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode

drwx------ 3 system system 4096 Jan 1 2011 dmp

-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone

-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result

-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin

-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data

-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p

-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language

-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen

-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type

-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern

-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena

bled

-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock

-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata

-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5

-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin

-rw-r--r-- 1 system system 0 Nov 3 18:02 cryptprop_onetimeboot

drwxrwx--x 5 radio system 4096 Nov 3 21:23 .

drwxr-xr-x 21 root root 0 Nov 3 21:58 ..

You can see the changes to nv_data.bin.md5 and nv_data.bin -- I have no idea what crptprop_onetimeboot is but it looks a little suspicious.

Firstly I have a copy of the above as

- a directory on my sdcard

- a dd'd image on my sdcard

- a file copy on my PC (!)

I also see I still have backup files, so with a lot of difficulty (fs kept going read only when trying to copy files, so I ended up renaming the old name to the new name)

ie

.nv_data.bak -> nv_data.bin

.nv_data.bak.md5 -> nv_data.bin.md5

This didn't work (still no service/no imei), so I removed(renamed) the .md5 file -- but it still doesn't work

so it now looks like

# ls -latr

ls -latr

drwxrwxr-x 5 root root 4096 Jan 1 2000 .files

drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei

-rwx------ 1 radio radio 32 Jan 1 2011 nv_data.bin.md5.orig

-rwx------ 1 radio radio 2097152 Jan 1 2011 nv_data.bin

-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log

-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state

-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5

-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak

-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode

drwx------ 3 system system 4096 Jan 1 2011 dmp

-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone

-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result

-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin

-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data

-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p

-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language

-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen

-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type

-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern

-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena

bled

-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock

-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata

-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5.bk

-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin.bk

-rw-rw-rw- 1 root root 0 Nov 3 20:55 p

drwxrwx--x 5 radio system 4096 Nov 3 21:48 .

-rw-r--r-- 1 system system 0 Nov 3 21:52 cryptprop_onetimeboot

drwxr-xr-x 21 root root 0 Nov 3 21:58 ..

#

[/FONT]

I DID NOT BACKUP EFS beforehand (only just learnt I need to) and know this may now be screwed, but I'm still hopeful I have the original file and just made a silly error.

I could also

- try recreating the whole fs and copying files back

- checking the prod code within the rom (but why?)

- flashing original firmware

- modifying the dd'd image *offline*, swapping the files, and dd'ing the image back

Any advice. PLEASE....