hi guys I have a Nexus 9020a I was on CM7 and used the power widget 2g/3g (this was a week ago) and suddenly my phone wouldn't get radio so format system,data,cache and installed again from scratch and no luck
Ive hhad a dump of my efs tried yo restore it and it said it was full so after tinkering I saw on dmesg that efs partition had bad blocks probably causing the error while restoring efs that I've got No space left for the backup to restore to any one else experiencied this PR something similar? I was wondering if it is possible to make a CM7 like on i9000 partition containing my efs data
Sent from my Nexus S using XDA App
davioxx said:
hi guys I have a Nexus 9020a I was on CM7 and used the power widget 2g/3g (this was a week ago) and suddenly my phone wouldn't get radio so format system,data,cache and installed again from scratch and no luck
Ive hhad a dump of my efs tried yo restore it and it said it was full so after tinkering I saw on dmesg that efs partition had bad blocks probably causing the error while restoring efs that I've got No space left for the backup to restore to any one else experiencied this PR something similar? I was wondering if it is possible to make a CM7 like on i9000 partition containing my efs data
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
romkitchen --> extract cm7 --> add /efs --> repack --> flash
Borky could you elaborate that alittle more please I really want to you use my nexus s as phone not as multimedia player lol
Sent from my Nexus S using XDA App
Do you fix it? I have a same problem.
davioxx said:
Borky could you elaborate that alittle more please I really want to you use my nexus s as phone not as multimedia player lol
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Use rom kitchen to package your eds backup into a rom then flash it.
Sent from my Nexus S 4G using xda premium
Can U explain what happen with my EFS?
Code:
Sat Jan 1 00:18:16 2005: No NV backup found. Create one before MD5 on.
Sat Jan 1 00:18:16 2005: NV data back-up begin.
Sat Jan 1 00:18:16 2005: nv_data.bin does not exist.
Sat Jan 1 00:18:16 2005: NV data backup stopped due to NV data size.
Sat Jan 1 00:18:16 2005: MD5 is turned on.
Sat Jan 1 00:18:16 2005: nv_data.bin does not exist.
Sat Jan 1 00:18:16 2005: default NV restored.
Sat Jan 1 00:37:26 2005: MD5 is turned off on 0
Wed Mar 16 13:37:27 2011: NV data back-up begin.
Wed Mar 16 13:37:27 2011: NV data back-up begin.
Wed Mar 16 13:37:27 2011: NV data back-uped.
Wed Mar 16 13:37:27 2011: MD5 is turned on.
Thu Mar 17 01:11:23 2011: MD5 is turned off on 0
Thu Mar 17 01:12:46 2011: NV data back-up begin.
Thu Mar 17 01:12:46 2011: NV data back-up begin.
Thu Mar 17 01:12:46 2011: NV data back-uped.
Thu Mar 17 01:12:46 2011: MD5 is turned on.
Thu Mar 17 03:24:27 2011: MD5 is turned off on 2
Thu Mar 17 05:37:04 2011: enabling MD5 automatically because it was off temporarily.
Thu Mar 17 05:37:04 2011: NV data back-up begin.
Thu Mar 17 05:37:04 2011: NV data back-up begin.
Thu Mar 17 05:37:04 2011: NV data back-uped.
Thu Mar 17 05:37:05 2011: MD5 is turned on.
Thu Mar 17 05:37:18 2011: MD5 is turned off on 0
Thu Mar 17 05:38:50 2011: NV data back-up begin.
Thu Mar 17 05:38:50 2011: NV data back-up begin.
Thu Mar 17 05:38:50 2011: NV data back-uped.
Thu Mar 17 05:38:50 2011: MD5 is turned on.
Thu Mar 17 05:39:37 2011: MD5 is turned off on 0
Thu Mar 17 05:40:19 2011: NV data back-up begin.
Thu Mar 17 05:40:19 2011: NV data back-up begin.
Thu Mar 17 05:40:19 2011: NV data back-uped.
Thu Mar 17 05:40:19 2011: MD5 is turned on.
Thu Mar 17 05:42:06 2011: MD5 is turned off on 2
Thu Mar 17 05:43:02 2011: MD5 is turned off on 0
Thu Mar 17 05:43:27 2011: NV data back-up begin.
Thu Mar 17 05:43:27 2011: NV data back-up begin.
Thu Mar 17 05:43:27 2011: NV data back-uped.
Thu Mar 17 05:43:27 2011: MD5 is turned on.
Thu Mar 17 06:02:44 2011: MD5 is turned off on 2
Thu Mar 17 06:02:52 2011: NV data back-up begin.
Thu Mar 17 06:02:52 2011: NV data back-up begin.
Thu Mar 17 06:02:52 2011: NV data back-uped.
Thu Mar 17 06:03:07 2011: MD5 is turned on.
Sun Sep 18 14:35:10 2011: backup NV restored.
Sun Sep 18 14:35:16 2011: invalid size /efs/nv_data.bin, 1662976 bytes.
Sun Sep 18 14:38:53 2011: backup NV restored.
Sun Sep 18 14:38:59 2011: invalid size /efs/nv_data.bin, 1662976 bytes.
Sun Sep 18 14:48:01 2011: invalid size /efs/nv_data.bin, 1601536 bytes.
Sun Sep 18 14:54:24 2011: backup NV restored.
Sun Sep 18 14:54:25 2011: MD5 fail. orignal md5 'aed944d19cfa8f586f0e0186d4d7b244' computed md5 'e73aa90496c8baaf0419ddd631285728' (rild)
Sun Sep 18 15:27:19 2011: invalid size /efs/nv_data.bin, 937984 bytes.
Sun Sep 18 15:40:28 2011: backup NV restored.
Sun Sep 18 15:40:28 2011: MD5 fail. orignal md5 'aed944d19cfa8f586f0e0186d4d7b244' computed md5 'e73aa90496c8baaf0419ddd631285728' (rild)
Sun Sep 18 15:48:40 2011: backup NV restored.
Sun Sep 18 15:48:46 2011: invalid size /efs/nv_data.bin, 1662976 bytes.
Sun Sep 18 16:20:14 2011: invalid size /efs/nv_data.bin, 1531904 bytes.
Sun Sep 18 14:29:25 2011: backup NV restored.
Sun Sep 18 14:29:25 2011: MD5 fail. orignal md5 'aed944d19cfa8f586f0e0186d4d7b244' computed md5 'e73aa90496c8baaf0419ddd631285728' (rild)
I have already sent the phone to the service, whether they can see from this that I had a phone and rootan custom rom? I has this files in folder EFS:
Code:
bluetooth\
imei\
.nv_data.bak
.nv_data.bak.md5
.nv_state
adb.exe
efs_backup.bat
efs_restore.bat
nv.log
nv_data.bin
nv_data.bin.md5
Where is .imei file?:/
I backed up too late (it seems)...
sorry, delete post.
It took me a while to understand how the imei system woks but i think i have the gist of it now. i don't know if this works for other models but it must considering i took information from a multitude of sources to work out a solution here's what I did
Before starting this tricky set of commands please make sure your phone has the following settings:
ROOTED
HAS BUSYBOX INSTALLED
HAS EITHER ROOTEXPLORER OR ADB
YOUR PC HAS A PROPER UNIX TEXT EDITOR (NOTEPAD++ OR JEDIT)
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery):good:
If you have any problems please list them below and i will do my best to solve them
Thank you for posting. Awesome!
Sent from my SGH-I897 using Tapatalk 2
Saved. My. Ass.
Thanks!
Hi,
I have this problem with my GT-N7100 where I've rooted it, flashed a ROM and somewhere along the way (I think it was when it rooted), I have lost my IMEI to this generic one. I have been following the steps but I'm a little stuck.
I have found nv_data.bin and nv.log in the /efs folder... but the nv.log doesn't have anything about a corrupted MD5?
This is my nv.log file:
Sun Jan 1 00:02:12 2012: nv data does not exist
Sun Jan 1 00:02:12 2012: md5 compute error
Sun Jan 1 00:02:12 2012: md5 compute error
Sun Jan 1 00:02:13 2012: default NV restored
Sun Jan 1 00:02:21 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:21 2012: 2nd NV built
Sun Jan 1 00:02:21 2012: NV data back-uped
Sun Jan 1 00:11:44 2012: check off
Tue Mar 26 17:23:05 2013: MD5 status = (OFF)
Sun Jan 1 00:00:02 2012: check off
Sun Jan 1 00:00:02 2012: MD5 status = (OFF)
Sun Jan 1 00:00:07 2012: MD5 status = (OFF)
Sun Jan 1 00:00:08 2012: MD5 status = (OFF)
Sun Jan 1 00:00:13 2012: MD5 status = (OFF)
Sun Jan 1 00:00:13 2012: MD5 status = (OFF)
Sun Jan 1 09:36:24 2012: check off
Sun Jan 1 09:36:24 2012: MD5 status = (OFF)
Sun Jan 1 09:36:29 2012: MD5 status = (OFF)
Sun Jan 1 09:36:29 2012: MD5 status = (OFF)
Sun Jan 1 09:36:34 2012: MD5 status = (OFF)
Sun Jan 1 09:36:34 2012: MD5 status = (OFF)
Wed Mar 27 14:21:54 2013: MD5 status = (OFF)
Wed Mar 27 14:21:54 2013: MD5 status = (OFF)
Wed Mar 27 14:21:55 2013: MD5 status = (OFF)
Wed Mar 27 14:21:55 2013: MD5 status = (OFF)
Wed Mar 27 14:21:59 2013: MD5 status = (OFF)
Wed Mar 27 14:21:59 2013: MD5 status = (OFF)
Wed Mar 27 14:22:18 2013: MD5 status = (OFF)
Wed Mar 27 14:22:18 2013: MD5 status = (OFF)
Wed Mar 27 14:23:47 2013: MD5 status = (OFF)
Wed Mar 27 14:23:47 2013: MD5 status = (OFF)
Wed Mar 27 14:23:57 2013: MD5 status = (OFF)
Wed Mar 27 14:23:57 2013: MD5 status = (OFF)
Wed Mar 27 14:23:58 2013: MD5 status = (OFF)
Wed Mar 27 14:23:59 2013: MD5 status = (OFF)
Wed Mar 27 14:23:59 2013: MD5 status = (OFF)
Wed Mar 27 14:24:00 2013: 2nd NV built
Wed Mar 27 14:24:00 2013: NV data back-uped
Wed Mar 27 14:24:00 2013: check on
Wed Mar 27 14:29:40 2013: check off
Wed Mar 27 14:30:05 2013: 2nd NV built
Wed Mar 27 14:30:05 2013: NV data back-uped
Wed Mar 27 14:30:05 2013: check on
Wed Mar 27 14:30:58 2013: fail - no checksum info
Wed Mar 27 14:30:58 2013: NV restored
Wed Mar 27 14:34:48 2013: OFFSET_FOR_PRESET1 writing input
Wed Mar 27 14:34:48 2013: 2nd NV built
Wed Mar 27 14:34:48 2013: NV data back-uped
Wed Mar 27 14:34:54 2013: OFFSET_FOR_PRESET2 writing input
Wed Mar 27 14:34:54 2013: 2nd NV built
Wed Mar 27 14:34:54 2013: NV data back-uped
Wed Mar 27 14:34:57 2013: OFFSET_FOR_PRESET2 writing input
Wed Mar 27 14:34:57 2013: 2nd NV built
Wed Mar 27 14:34:57 2013: NV data back-uped
Tue Jun 18 14:31:16 2013: input from cp
Tue Jun 18 14:31:16 2013: 2nd NV built
Tue Jun 18 14:31:16 2013: NV data back-uped
Tue Jun 18 19:18:19 2013: OFFSET_FOR_PRESET2 writing input
Tue Jun 18 19:18:19 2013: 2nd NV built
Tue Jun 18 19:18:19 2013: NV data back-uped
Click to expand...
Click to collapse
Any ideas?
Thanks.
readinc cuneiform
I have the same problem, my nv.log is this:
Fri Jun 21 16:54:32 2013: md5 compute error
Fri Jun 21 16:54:32 2013: md5 compute error
Fri Jun 21 16:54:32 2013: default NV restored
Fri Jun 21 16:54:59 2013: OFFSET_FOR_PRESET2 writing input
Fri Jun 21 16:54:59 2013: 2nd NV built
Fri Jun 21 16:54:59 2013: NV data back-uped
Fri Jun 21 17:07:09 2013: input from cp
Fri Jun 21 17:07:09 2013: 2nd NV built
Fri Jun 21 17:07:09 2013: NV data back-uped
Been trying to fix this damn problem for ages. I have two logs, one looks exactly like the post above, the other looks like the one OP posted but just says expected ms5 "" and then the current one. Anywhere else to find the expected one?
Thanks
If your nv.log ends with backup NV restored.(GED) that is good it mean even though the m5d didn't mach the expected md5 hash it still restored the proper IMEI. If however your nv.log end in default NV restored that is a sure indication that the default IMEI i.e 004999901064000 is in use.
With my Nexus S even though my EFS partition is corrupt I was able to restore the proper IMEI from the /data/radio partition. I suspect every Samsung model stores its NV data (i.e the IMEI and Blue Tooth Data) in different places. I have noticed if I try to flash a custom rom like CM10 over a stock rom 4.1.2 JZ054K that is when I loose my NV data.
004999010640000 IMEI on my Samsung N7100
Hi
I downgraded my phone to a previous stock samsung rom via odin, due to battery back up issue and I got this generic IMEI. I had previously used the same rom to downgrade and it all went well(unfortunately it got updated back then :silly: , so I had to downgrade again ). This time it gave me a generic IMEI 004999010640000 and I'm in a fix . My phone has been never ever rooted. I googled and somewhere, it was a mentioned that efs folder should be deleted and then a reboot would do the trick. Don't know how right that was, but I couldn't delete/move/rename the efs folder. Secondly, it shows 0 bytes and is empty.
Pls help me. Thanks in advance!
Dave
i wish this thread had been out back in the summer of 2011... i had such a hard time trying to fix this on my own and ended up just pulling a old switcharoo on bestbuy
imei
ethan_hines said:
If your nv.log ends with backup NV restored.(GED) that is good it mean even though the m5d didn't mach the expected md5 hash it still restored the proper IMEI. If however your nv.log end in default NV restored that is a sure indication that the default IMEI i.e 004999901064000 is in use.
With my Nexus S even though my EFS partition is corrupt I was able to restore the proper IMEI from the /data/radio partition. I suspect every Samsung model stores its NV data (i.e the IMEI and Blue Tooth Data) in different places. I have noticed if I try to flash a custom rom like CM10 over a stock rom 4.1.2 JZ054K that is when I loose my NV data.
Click to expand...
Click to collapse
hi my nv.log ends with backup nv restored but still 00499......should i still do this method:fingers-crossed:
zadia24 said:
hi my nv.log ends with backup nv restored but still 00499......should i still do this method:fingers-crossed:
Click to expand...
Click to collapse
Unfortunately I don't have a correct nv.log and everything is corrupted and I'm in generic IMEI. How can I fix it without efs? Is it possible to use someone else files?
I have a nand backup but after I restored it nothing changed. It seems that efs are not backed up in nand backup. Please help me. I spent more than 12 hours to fix this problem.
Bom dia amigo, não consegui encontrar nenhum arquivos com vários números e letras, exemplo xxxxxxxxxxxx. E meu log está assim:
Sun Jan 1 00:00:30 2012: no nv data
Sun Jan 1 00:00:31 2012: default Nv restored.
Sun Jan 1 00:00:31 2012: Nv created
Sun Jan 1 00:00:42 2012: item 2 written
Sun Jan 1 00:00:42 2012: Nv core done
Sun Jan 1 00:00:42 2012: Nv data backup
Sun Jan 1 00:06:29 2012: checksum off
Wed Apr 17 11:12:47 2013: current checksum status is off
Sun Jan 1 00:00:02 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:01:35 2012: current checksum status is off
Sun Jan 1 00:01:42 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 02:54:29 2012: current checksum status is off
Sun Jan 1 02:54:36 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Thu Apr 18 22:00:10 2013: current checksum status is off
Thu Apr 18 22:00:17 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:57 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:59 2013: Nv core done
Thu Apr 18 14:01:59 2013: Nv data backup
Thu Apr 18 14:01:59 2013: checksum on
Thu Apr 18 14:49:10 2013: checksum off
Thu Apr 18 14:50:06 2013: Nv core done
Thu Apr 18 14:50:07 2013: Nv data backup
Thu Apr 18 14:50:07 2013: checksum on
Thu Apr 18 14:50:09 2013: checksum off
Thu Apr 18 14:50:32 2013: Nv core done
Thu Apr 18 14:50:33 2013: Nv data backup
Thu Apr 18 14:50:33 2013: checksum on
Thu Apr 18 21:20:53 2013: item 1 written
Thu Apr 18 21:20:53 2013: Nv core done
Thu Apr 18 21:20:53 2013: Nv data backup
Thu Apr 18 21:21:02 2013: Nv core done
Thu Apr 18 21:21:02 2013: Nv data backup
Tue Jan 1 08:02:35 2013: item 2 written
Tue Jan 1 08:02:35 2013: Nv core done
Tue Jan 1 08:02:36 2013: Nv data backup
Tue Jan 1 08:02:38 2013: item 2 written
Tue Jan 1 08:02:38 2013: Nv core done
Tue Jan 1 08:02:39 2013: Nv data backup
Tue Jul 30 23:22:40 2013: Nv core done
Tue Jul 30 23:22:40 2013: Nv data backup
Fri Aug 23 13:59:45 2013: item 2 written
Fri Aug 23 13:59:45 2013: Nv core done
Fri Aug 23 13:59:45 2013: Nv data backup
Can you help me please?!
---------- Post added at 08:45 PM ---------- Previous post was at 08:39 PM ----------
Good day friends, I could not find in my Galaxy S4 any files with multiple numbers and letters, eg xxxxxxxxxxxx, just found nv_data.bin, nv_data.bin.md5 and nv.log. And so is my log:
Sun Jan 1 00:00:30 2012: no nv data
Sun Jan 1 00:00:31 2012: default Nv restored.
Sun Jan 1 00:00:31 2012: Nv created
Sun Jan 1 00:00:42 2012: item 2 written
Sun Jan 1 00:00:42 2012: Nv core done
Sun Jan 1 00:00:42 2012: Nv data backup
Sun Jan 1 00:06:29 2012: checksum off
Wed Apr 17 11:12:47 2013: current checksum status is off
Sun Jan 1 00:00:02 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:17 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:00:18 2012: current checksum status is off
Sun Jan 1 00:01:35 2012: current checksum status is off
Sun Jan 1 00:01:42 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 00:01:43 2012: current checksum status is off
Sun Jan 1 02:54:29 2012: current checksum status is off
Sun Jan 1 02:54:36 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Sun Jan 1 02:54:37 2012: current checksum status is off
Thu Apr 18 22:00:10 2013: current checksum status is off
Thu Apr 18 22:00:17 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 22:00:18 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:36 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:40 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:43 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:00:58 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:42 2013: current checksum status is off
Thu Apr 18 14:01:57 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:58 2013: current checksum status is off
Thu Apr 18 14:01:59 2013: Nv core done
Thu Apr 18 14:01:59 2013: Nv data backup
Thu Apr 18 14:01:59 2013: checksum on
Thu Apr 18 14:49:10 2013: checksum off
Thu Apr 18 14:50:06 2013: Nv core done
Thu Apr 18 14:50:07 2013: Nv data backup
Thu Apr 18 14:50:07 2013: checksum on
Thu Apr 18 14:50:09 2013: checksum off
Thu Apr 18 14:50:32 2013: Nv core done
Thu Apr 18 14:50:33 2013: Nv data backup
Thu Apr 18 14:50:33 2013: checksum on
Thu Apr 18 21:20:53 2013: item 1 written
Thu Apr 18 21:20:53 2013: Nv core done
Thu Apr 18 21:20:53 2013: Nv data backup
Thu Apr 18 21:21:02 2013: Nv core done
Thu Apr 18 21:21:02 2013: Nv data backup
Tue Jan 1 08:02:35 2013: item 2 written
Tue Jan 1 08:02:35 2013: Nv core done
Tue Jan 1 08:02:36 2013: Nv data backup
Tue Jan 1 08:02:38 2013: item 2 written
Tue Jan 1 08:02:38 2013: Nv core done
Tue Jan 1 08:02:39 2013: Nv data backup
Tue Jul 30 23:22:40 2013: Nv core done
Tue Jul 30 23:22:40 2013: Nv data backup
Fri Aug 23 13:59:45 2013: item 2 written
Fri Aug 23 13:59:45 2013: Nv core done
Fri Aug 23 13:59:45 2013: Nv data backup
Can you help me please?!
Same here
My log says nothing
Fri Aug 23 19:29:02 2013: default NV restored
Fri Aug 23 19:29:40 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 23 19:29:40 2013: 2nd NV built
Fri Aug 23 19:29:40 2013: NV data back-uped
Hi,
I have the same problem, my log doesn't contain the MD5 failure messages:
Code:
Sun Jan 1 00:02:16 2012: nv data does not exist
Sun Jan 1 00:02:16 2012: default NV restored
Sun Jan 1 00:02:24 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:25 2012: 2nd NV built
Sun Jan 1 00:02:25 2012: NV data back-uped
Sun Jan 1 00:08:02 2012: check off
Sun Jan 1 00:00:08 2012: check off
Sun Jan 1 00:00:02 2012: check off
Sun Jan 1 09:27:28 2012: check off
Tue Dec 4 03:45:25 2012: 2nd NV built
Tue Dec 4 03:45:25 2012: NV data back-uped
Tue Dec 4 03:45:25 2012: check on
Tue Dec 4 03:46:13 2012: check off
Tue Dec 4 03:47:36 2012: 2nd NV built
Tue Dec 4 03:47:36 2012: NV data back-uped
Tue Dec 4 03:47:36 2012: check on
Tue Dec 4 03:47:44 2012: check off
Tue Dec 4 03:47:59 2012: 2nd NV built
Tue Dec 4 03:47:59 2012: NV data back-uped
Tue Dec 4 03:47:59 2012: check on
Tue Dec 4 03:48:20 2012: fail - no checksum info
Tue Dec 4 03:48:20 2012: NV restored
Tue Dec 4 03:49:02 2012: OFFSET_FOR_PRESET1 writing input
Tue Dec 4 03:49:02 2012: 2nd NV built
Tue Dec 4 03:49:02 2012: NV data back-uped
Tue Dec 4 03:49:07 2012: OFFSET_FOR_PRESET2 writing input
Tue Dec 4 03:49:07 2012: 2nd NV built
Tue Dec 4 03:49:07 2012: NV data back-uped
Tue Dec 4 03:49:09 2012: OFFSET_FOR_PRESET2 writing input
Tue Dec 4 03:49:09 2012: 2nd NV built
Tue Dec 4 03:49:10 2012: NV data back-uped
Fri Jun 21 10:40:51 2013: input from cp
Fri Jun 21 10:40:51 2013: 2nd NV built
Fri Jun 21 10:40:51 2013: NV data back-uped
Fri Aug 30 03:11:27 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 30 03:11:28 2013: 2nd NV built
Fri Aug 30 03:11:28 2013: NV data back-uped
I checked /data/radio but there is no folder with that name. Any idea where I can find this file on SG Note2 ?
Any further advice?
ethan_hines said:
It took me a while to understand how the imei system woks but i think i have the gist of it now. i don't know if this works for other models but it must considering i took information from a multitude of sources to work out a solution here's what I did
Before starting this tricky set of commands please make sure your phone has the following settings:
ROOTED
HAS BUSYBOX INSTALLED
HAS EITHER ROOTEXPLORER OR ADB
YOUR PC HAS A PROPER UNIX TEXT EDITOR (NOTEPAD++ OR JEDIT)
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery):good:
If you have any problems please list them below and i will do my best to solve them
Click to expand...
Click to collapse
Hey i have the same problem in my I9500. But i dont see the log saying MD5 fail. I am confident from you post that this is why one country's modem is working and my country's is not working. Can you tell me how to find out the MD5 my Country's modem is expecting?
What's the best/preferred method to create a backup for this issue? I tried flashing CM 10.x on my Galaxy S3 (GT-I9300) a few days ago and I had this problem. By some miracle, and after about 30 flash attempts, I got my proper IMEI back. Just in case this happens again, I want to create a suitable backup file(s) to have the option to use this "fix".
when I get my phone back from service is show that imei ...is a problem?
anyone ?
What is the significance of having the generic IMEI?
I'm hoping to hide the identity of a phone by using this. I don't want to use any DATA on A** network, but I don't want to get smashed with a Data plan just because. I just need 2G and 3G voice to work.
I wasn't able to even make phone calls when it had that generic imei.
Hi, I have latest Paranoid build (RC2) on my device flashed clean about one week ago. I try to connect to my PPTP VPN server without succes. On the PPTP server I get this error message:
HTML:
Jun 23 09:39:23 pppd[644]: Connect: ppp10 <--> pptp (192.168.10.238)
Jun 23 09:39:26 pppd[644]: Peer danut.sun failed CHAP authentication
Jun 23 09:39:26 pppd[644]: Connection terminated.
Jun 23 09:39:26 pppd[644]: Exit.
Jun 23 09:39:26 pptpd[643]: CTRL: Reaping child PPP[644]
Jun 23 09:39:26 pptpd[643]: CTRL: Client pppd TERM sending
Jun 23 09:39:26 pptpd[643]: CTRL: Client pppd finish wait
Jun 23 09:39:26 pptpd[643]: CTRL: EOF or bad error reading ctrl packet length.
Jun 23 09:39:26 pptpd[643]: CTRL: couldn't read packet header (exit)
Jun 23 09:39:26 pptpd[643]: CTRL: Fatal error reading control message in disconnect sequence
Jun 23 09:39:26 pptpd[643]: CTRL: Client 192.168.10.238 control connection finished
I have to mention that on stock ROM I don't have this problem. I also have success connection on other phone.
-----SYSTEM INFORMATION-----
Build: lineage_a5y17lte-userdebug 7.1.2 NJH47F 6130578a64 test-keys
CM version: 14.1-20180213-UNOFFICIAL-a5y17lte
Build fingerprint: 'samsung/a5y17ltexx/a5y17lte:7.0/NRD90M/A520FXXS2AQF2:user/release-keys'
Bootloader: A520FXXS2AQF2
Radio: A520FXXS2AQF2
Network: MOBITEL
Kernel: Linux version 3.18.14-gacc44c75f95 ([email protected]) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Feb 14 00:28:08 CET 2018
Command line: console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 DynSysLog=0 androidboot.debug_level=0x4f4c ess_setup=0x46000000 [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0x67000000 lcdtype=4259858 consoleblank=0 vmalloc=384m sec_debug.reset_reason=7 ehci_hcd.park=3 oops=panic pmic_info=3 ccic_info=1 cordon=277790bc1ea6f80f42cb0c7577a5e3b3 connie=SM-A520F_OPEN_EUR_dcf53c782347f3688fd08e45ccf1e757 fg_reset=0 androidboot.emmc_checksum=3 androidboot.boot_salescode= androidboot.odin_download=1 androidboot.bootloader=A520FXXS2AQF2 androidboot.selinux=enforcing androidboot.security_mode=1526595584 androidboot.ucs_mode=0 androidboot.hw_rev=8 androidboot.hardware=samsungexynos7880 androidboot.warranty_bit=1 androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=5200ed5afeed64c3 snd_soc_core.pmdown_time=1000 androidboot.em.did=07740e7bccf8 androidboot.em.model=SM-A520F androidboot.em.status=0x0 reserve-fimc=0 firmware_class.path=/vendor/firmware factory_mode=0
Bugreport format version: 1.0
Dumpstate info: id=1 pid=7364
-----------------------------------------------------------------------------------------
My volume is way too loud after I did a backup onto my external sdcard.
When I first got this error, I formatted my device and flashed LineageOS again and it fixed the problem. Now i've been using my phone for a while and I don't want to lose all my data and stuff again.
I don't even know where should I start, so tell me if you need more information about bug.
I know about mixer_paths.xml but there is no label for speakers or something like it should be.
Thanks for all help!
p.s. sorry for bad english
Thread closed as per OP request
Hey guys, i need some help with something.
I have a chinese device ( SLIDE SP 4013)
Here's the info:
BB chip: MT6580
MS Board: t53_A_X40
Build Time: 2016/10/25 13:10:17 CST
Kernel Ver: 3.10.72 ([email protected]) (gcc version: 4.8) (GCC)
#1 SMP PREEMPT tue Oct 25 13:22:37 CST 2016
Android Ver: 5.1
SWver: ALPS.L1.MP6 V2_ALONG6580.WE L_P18
Custom Build Verno: Unknown
Modem Ver: MOLY.WR8.W1449.MD.WG.MP.V6.P10 2016/08/10 01:43
Bar Code: 10
I've tried to unlock bootloader via fastboot ( fastboot oem unlock), but the bootloader is locked.
I Need to root this phone and instal CWM recovery as well. (bootloader locked)
Screen is brocken, so touch-screen doesn't work but it displays.
Any idea about it?
Regards