Hi there,
Something very strange has appears to my Nexus S.
It's been more than one year that my phone works perfectly with ICS 4.04 flashed by recovery and ROM stock, I've never reflashed my phone since this day.
Then two days ago, no more GSM network, can't pass any call or text, but data in WCDMA works perfectly.
I've tried :
- Factory reset
- Cyanogen Mod last ROM
- Tried my SIM card on the Nexus S of a friend --> works perfectly
- Tried my friend SIM card on my phone --> same issues, no GSM but data works in WCDMA
I've search a lot on google and XDA, and I've discovered what was IMEI and /efs.
But it's too late for me, my IMEI is the cursed generic IMEI, not the one written behind my battery.
I've tried to flash with stock ROM Stock Android 2.3.6 (GRK39F) with Odin because I've read that it could retrieve my original IMEI. There was no .md5 file inside so I can't flash it with Odin, else I've flash it with ADB / Fastboot.
Phone start and GSM mobile works !
But I got generic IMEI yet, and data is stuck on edge, no WCDMA.
I was thinking it was caused by the old ROM radio flashed with ROM Stock Android 2.3.6 (GRK39F).
So I've flash using recovery the latest Cyanogen and ROM radio KB3 (which was working great in WCDMA for me before all this mess).
No change, GSM works, but data network is stuck in Edge, even if I force WCDMA in *#*#4636#*#* menu, it keep staying in edge.
I don't understand all of this, but I think this is again link to this generic IMEI.
My /efs folder is not empty, I have nv_data.bin but file is dated from yesterday and I can't find any backup like ".nv_data.bin" or "nv_data.bin.bak".
This story seems to be classic in XDA forum, but it's really difficult for me to find a solution, especially for a Nexus S.
This phone is pretty old, you guys are experienced with it and I really need your help, I like this phone and I don't want to change it =(
Is there any way to regenerate my original IMEI ?
Maybe I'll try a flash with Odin and 2.3.4 GRJ22, I never tried Odin, but it seems sometimes to solve the problem. Do you think it could work ?
I really need your help guys, I'm so sad : /
Thanks for reading this, and thanks again if your reply.
hey man,
sorry to hear that...
have you tried to use your sim on another phone? the phone is 2 years old and possibly the problem is from the simcard\network.
another option is to check weather your APN's are as supposed to be.
you can check online or via customer service.
sheeen said:
Hi there,
Something very strange has appears to my Nexus S.
It's been more than one year that my phone works perfectly with ICS 4.04 flashed by recovery and ROM stock, I've never reflashed my phone since this day.
Then two days ago, no more GSM network, can't pass any call or text, but data in WCDMA works perfectly.
I've tried :
- Factory reset
- Cyanogen Mod last ROM
- Tried my SIM card on the Nexus S of a friend --> works perfectly
- Tried my friend SIM card on my phone --> same issues, no GSM but data works in WCDMA
I've search a lot on google and XDA, and I've discovered what was IMEI and /efs.
But it's too late for me, my IMEI is the cursed generic IMEI, not the one written behind my battery.
I've tried to flash with stock ROM Stock Android 2.3.6 (GRK39F) with Odin because I've read that it could retrieve my original IMEI. There was no .md5 file inside so I can't flash it with Odin, else I've flash it with ADB / Fastboot.
Phone start and GSM mobile works !
But I got generic IMEI yet, and data is stuck on edge, no WCDMA.
I was thinking it was caused by the old ROM radio flashed with ROM Stock Android 2.3.6 (GRK39F).
So I've flash using recovery the latest Cyanogen and ROM radio KB3 (which was working great in WCDMA for me before all this mess).
No change, GSM works, but data network is stuck in Edge, even if I force WCDMA in *#*#4636#*#* menu, it keep staying in edge.
I don't understand all of this, but I think this is again link to this generic IMEI.
My /efs folder is not empty, I have nv_data.bin but file is dated from yesterday and I can't find any backup like ".nv_data.bin" or "nv_data.bin.bak".
This story seems to be classic in XDA forum, but it's really difficult for me to find a solution, especially for a Nexus S.
This phone is pretty old, you guys are experienced with it and I really need your help, I like this phone and I don't want to change it =(
Is there any way to regenerate my original IMEI ?
Maybe I'll try a flash with Odin and 2.3.4 GRJ22, I never tried Odin, but it seems sometimes to solve the problem. Do you think it could work ?
I really need your help guys, I'm so sad : /
Thanks for reading this, and thanks again if your reply.
Click to expand...
Click to collapse
Still nothing,.. Sorry you haven't got this resolved yet.. Hopefully some fresh eyes here can make short work of it..
Thanks for your reply guys.
I've tried the sim in another phone and it works great, the real problem is generic IMEI I guess.
Thanks for your help and your link in PM Setting Out, I think I'll try the second one.... the first can't work with me because my /esf and /data/radio does not have an old backup of nv_data.bin.
I have two questions please :
- How the holy s*** this thing can happen randomly after ONE YEAR of fully founctional phone ? (not a single flash since one year)
- How can it be so ramdom ? I mean, before rom stock flash, GSM does not work but I was having Data (WCDMA). Now, After rom stock flash, GSM is working but Data is stuck in Edge. I can't understand how IMEI can impact such randomly issues.
Well, as you know the IMEI is sent to your operator as long as you have signal.
if the operator doesn't get a valid one problems may occur.
In order to find out if this really is a EFS problem go into /data/radio/log and cat the nv.log, find a line like this:
MD5 fail. orignal md5 '84373eddf2a1617f795b1c1af650f8a784373eddf2a1617f795b1c1af650f8a7' computed md5
'3eddf2a1617f795b1c1af650f8a7' (rild)
put the phone in airplane mode then use a unix text editor and manualy edit nv_data.bin.m5d and make sure the string of numbers is equal to the string after "computed md5" (in this case 3eddf2a1617f795b1c1af650f8a7) save the file take the phone out of airplane mode then reboot check the IMEI with the *#06#
Thanks a lot for your reply.
I have /data/radio/log/nv.log file.
But I have no checksum in this file, only text like "/data/radio/nv_data.bin does not exist."
This is strange because /data/radio/nv_data.bin file exist.
But in /efs folder, I have a nv.log file too, and in this file I have some checksum.
Any way to do something with this one ?
EDIT : I've tried the manipulation with /efs folder, it does not change my generic IMEI =(
Sure, I verified permissions and owner of file.
sheeen said:
Thanks a lot for your reply.
I have /data/radio/log/nv.log file.
But I have no checksum in this file, only text like "/data/radio/nv_data.bin does not exist."
This is strange because /data/radio/nv_data.bin file exist.
But in /efs folder, I have a nv.log file too, and in this file I have some checksum.
Any way to do something with this one ?
EDIT : I've tried the manipulation with /efs folder, it does not change my generic IMEI =(
Sure, I verified permissions and owner of file.
Click to expand...
Click to collapse
Here are some detailed steps
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)
Thanks for the reply, but it can't work.
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Click to expand...
Click to collapse
I have no good copy of nv_data.bin, date shows that all have been generated last week.
So, I'd like to flash the phone with Odin rom stock 2.3.4 AND re-partition with the .pit file.
I've already flash it without the .pit, but my IMEI is still generic, I need the .pit file.
But the .pit file is nowhere, even on samfirmware : /
If somebody got this file, plz send it to me.
sheeen said:
Thanks for the reply, but it can't work.
I have no good copy of nv_data.bin, date shows that all have been generated last week.
So, I'd like to flash the phone with Odin rom stock 2.3.4 AND re-partition with the .pit file.
I've already flash it without the .pit, but my IMEI is still generic, I need the .pit file.
But the .pit file is nowhere, even on samfirmware : /
If somebody got this file, plz send it to me.
Click to expand...
Click to collapse
-I too have looked high and low for the Odin file since the Nexus S can be put in download mode holding the volume button while pluging in the micro USB. I did find some odin files but any one who tired them ened up perm bricking their phone.
-If you have a good backup it should restore the EFS partition as well as the RADIO.
-The only other way that I know of, I am afraid is to get the phone JTAGed by Samsung.
Good Luck
After two weeks of trying everything, I gave up and used a Z3X.
Now my IMEI is restored, and backup on my PC, my laptop, my sdcard and on cloud...
Thanks all for trying to help me.
Hi guys,
I have a Galaxy Core i8262b (Brazil), after updated started giving problem. I tried to fix it, but I couldn't, so I sent for assistance. The phone came back working, but the IMEI is different from the original, behind the battery.
Used like this a long time, but the memory was clogged, I needed to reset and then started all over again.
-Not registered on the network.
-IMEI with different ending of the original.
-Serial number reset (I visualized with root explorer).
-EFS incomplete Folder (I have no files nv data, imei).
-Odin does not recognize phone in download mode.
-Install zip sdcard recovery mode of this message: unknown volume path
Any chance of recovering without box?
Sorry my English, I am using bing translator.
I'm sorry if I posted in the wrong place.
Thank you to those who have help.
Even more.
jaquecalixto said:
Hi guys,
I have a Galaxy Core i8262b (Brazil), after updated started giving problem. I tried to fix it, but I couldn't, so I sent for assistance. The phone came back working, but the IMEI is different from the original, behind the battery.
Used like this a long time, but the memory was clogged, I needed to reset and then started all over again.
-Not registered on the network.
-IMEI with different ending of the original.
-Serial number reset (I visualized with root explorer).
-EFS incomplete Folder (I have no files nv data, imei).
-Odin does not recognize phone in download mode.
-Install zip sdcard recovery mode of this message: unknown volume path
Any chance of recovering without box?
Sorry my English, I am using bing translator.
I'm sorry if I posted in the wrong place.
Thank you to those who have help.
Even more.
Click to expand...
Click to collapse
You have to flash its stock firmware, as it seems like your efs partition is messed up...
I got this phone (Lenovo A606) about a month ago with the following problems:
1) Modem (the one with the SIM card) doesn't work, status in the about section shows "invalid IMEI" and "unknown baseband". SIM card settings are greyed out in the settings.
2) Wi-fi works fine, but i always have an additional SSID in wifi menu that says 0x010 something error
According to previous owner, it went bad after bad flash or update, but he might have been lying and modem is physically dead due to some reason.
3) Serial number is also a blank
So far i've tried:
1) Flashing different stock firmwares with full flash format and DA DL flags checked/unchecked in SP Flash tool
2) Fixing nvram/trying to restore IMEI and SN through numerous tools of different versions: Maui Meta 3g, SN Writer tool, SN Station Writer tool, infinity box CM2MTK, etc - every one of tools that i've tried (i've also tried different versions of the same tools) show me different errors, best solutions online for which are "check your drivers, change usb cable or change computer" all of which i've obviously tried with the exact same result
3) Fixing nvram by deleting nvram folder in /dev/nvram
4) Replacing MP0B_001 in the nvram folder (rather putting it in, the target folder is empty after stock flashing)
5) Using nvram fixes through both custom and stock recovery menus prepared by the poor bastards like me, but with more knowledge about this stuff
6) Flashing nvram from a donor working phone through SP Flash tool
And since i'm making this post nothing of the above has worked.
So far i've came up with two possibilities:
1) The modem is physically dead and i lost in total 72 hours of my life on a goose chase. If this case is true, how can I make sure of it? Is there a low-level recovery menu or a factory mode that can confirm/deny it?
2) I'm doing something wrong and there is a simple fix for it. In this case, I ask for help guide me in the right direction, if possible with exact instructions.
fdxcd said:
I got this phone (Lenovo A606) about a month ago with the following problems:
1) Modem (the one with the SIM card) doesn't work, status in the about section shows "invalid IMEI" and "unknown baseband". SIM card settings are greyed out in the settings.
2) Wi-fi works fine, but i always have an additional SSID in wifi menu that says 0x010 something error
According to previous owner, it went bad after bad flash or update, but he might have been lying and modem is physically dead due to some reason.
3) Serial number is also a blank
So far i've tried:
1) Flashing different stock firmwares with full flash format and DA DL flags checked/unchecked in SP Flash tool
2) Fixing nvram/trying to restore IMEI and SN through numerous tools of different versions: Maui Meta 3g, SN Writer tool, SN Station Writer tool, infinity box CM2MTK, etc - every one of tools that i've tried (i've also tried different versions of the same tools) show me different errors, best solutions online for which are "check your drivers, change usb cable or change computer" all of which i've obviously tried with the exact same result
3) Fixing nvram by deleting nvram folder in /dev/nvram
4) Replacing MP0B_001 in the nvram folder (rather putting it in, the target folder is empty after stock flashing)
5) Using nvram fixes through both custom and stock recovery menus prepared by the poor bastards like me, but with more knowledge about this stuff
6) Flashing nvram from a donor working phone through SP Flash tool
And since i'm making this post nothing of the above has worked.
So far i've came up with two possibilities:
1) The modem is physically dead and i lost in total 72 hours of my life on a goose chase. If this case is true, how can I make sure of it? Is there a low-level recovery menu or a factory mode that can confirm/deny it?
2) I'm doing something wrong and there is a simple fix for it. In this case, I ask for help guide me in the right direction, if possible with exact instructions.
Click to expand...
Click to collapse
Greetings and welcome to assist. Changing IMEI numbers is illegal and can not be discussed on xda so we have to be careful. If you have the original IMEI number it may be possible to restore it with an octoplus box or something similar but we are limited to what can be discussed on xda
Regards
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. Changing IMEI numbers is illegal and can not be discussed on xda so we have to be careful. If you have the original IMEI number it may be possible to restore it with an octoplus box or something similar but we are limited to what can be discussed on xda
Regards
Sawdoctor
Click to expand...
Click to collapse
Never tried to change it, since there wasn't any imei in the firmware to begin with. I only fruitlessly trying to return sim functionality
I have a Lenovo tab 2 A10-70l mt8732. It received an official update to marshmallow a while back. After update, the official recovery didn't backup properly. Error can't perform backup was the message. Even though the files were created, they showed checksum fail error while restore. Due to my need to backup, I flashed my tab with splash tools and files given in official forum. After flashing, I tried to root using the superuser install button in twrp. The screen went totally blank and there was no response. In a hurry, I gave full factory reset and flashed my device. On switching on, there was an invalid IMEI sign under network settings and many device information were missing. I learns that I have corrupted my nvram folder. I have no backup with me. I can use any flash file or terminal commands but will have no access to PC or laptop for a long time. It would be very convenient if you provide help by instructions. I would be grateful for both of based and independent solutions. Feel free to ask any other info of my tab. Since I have deleted and custom installed a ROM, I am ready to take risks if they are promising.