in the process of flashing the phone no longer show it's IMEI in status or in *#06#.
Carrier blocks the phone, i assume because of this.
seems to me that /efs/root/afs/settings/nv_data.bin is corrupted.
there is no backup file. :-( How do I recreate the file? can I use some other file and patch it with the correct IMEI?
zagzag99 said:
in the process of flashing the phone no longer show it's IMEI in status or in *#06#.
Carrier blocks the phone, i assume because of this.
seems to me that /efs/root/afs/settings/nv_data.bin is corrupted.
there is no backup file. :-( How do I recreate the file? can I use some other file and patch it with the correct IMEI?
Click to expand...
Click to collapse
What were you doing prior to this?
Does it ask you for a unlock code?
Details please.
i used odin to flash roms to upgrade to gingerbread.
kc1, kh1, voodoo kernel... it's now at kg6.
the phone was t-mobile unlocked, supposedly.
after i had issues with no calls in or out i noticed the imei reported in software (about phone or *#06#) is 00000000000000.
phone reports registered to the cellular network.
nv_data.bin in /efs/root/afs/settings is only 265kb and in hex editor it's all FF apart from one location with 00000000 values.
on an identical phone i have imei reported correctly. can i use it to recover the other one?
Sent from my NookColor using xda premium
zagzag99 said:
i used odin to flash roms to upgrade to gingerbread.
kc1, kh1, voodoo kernel... it's now at kg6.
the phone was t-mobile unlocked, supposedly.
after i had issues with no calls in or out i noticed the imei reported in software (about phone or *#06#) is 00000000000000.
phone reports registered to the cellular network.
nv_data.bin in /efs/root/afs/settings is only 265kb and in hex editor it's all FF apart from one location with 00000000 values.
on an identical phone i have imei reported correctly. can i use it to recover the other one?
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
256kb is the right size. It sounds like someone went the route of trying to hex edit the nv_data.bin to unlock and so on.
It's protected by a md5 checksum file.
Try this - back up the nv_data.bin.md5 in the /efs/root/afs/settings folder as well as the nv_data.bin ( just in case ) and DELETE only the nv_data.bin.md5 file. Reboot. Check your IMEI. Post back.
thegoo said:
256kb is the right size. It sounds like someone went the route of trying to hex edit the nv_data.bin to unlock and so on.
It's protected by a md5 checksum file.
Try this - back up the nv_data.bin.md5 in the /efs/root/afs/settings folder as well as the nv_data.bin ( just in case ) and DELETE only the nv_data.bin.md5 file. Reboot. Check your IMEI. Post back.
Click to expand...
Click to collapse
I've tried different, suggested to me in another forum, deleting both files. They got recreated at boot. Still imei zeros.
Sent from my HTC HD2
zagzag99 said:
I've tried different, suggested to me in another forum, deleting both files. They got recreated at boot. Still imei zeros.
Sent from my HTC HD2
Click to expand...
Click to collapse
Did you try just the.md5 file? And also, did you check your lock statuses? *#7465625#
I have tried that didn't help still zeros.
As for locks, it reports all off.
Sent from my HTC HD2
zagzag99 said:
I have tried that didn't help still zeros.
As for locks, it reports all off.
Sent from my HTC HD2
Click to expand...
Click to collapse
Try this.
Download hex editor.
Open hex editor.
Go look for the nv_data.bin file.
Hit options (the paper looking icon on the botton left of your phone) and click jump to address.
Type 1x1468.
After FF, the next 2 digits probably say 00. Try changing it to 01. And reboot.
If it doesnt work, go back to hex editor and change it back to 00 as thats the network lock.....
Sent from my SGH-T959V using XDA Premium App
You mean address 1468 in hex?
Tried it.
It turned back to 00 after reboot.
Imei still in problem.
Do I need to have the sim in?
I took it out for fear of troubling the network.
Sent from my HTC HD2
I guess not. And no. Having the sim in or not, it doesnt really matter. And you can use the phone perfectly with the imei being straight out 0's. You can call, text, and even use data. Tried it for myself . Unless theres someone else with the same imei. Id say thats a pretty low chance seeing that most people want their own unique imei. Sorry i couldnt help. but hope you can solve your problem!
Sent from my SGH-T959V using XDA Premium App
Unfortunately I can't use the phone with IMEI all in Zeros.
The Carrier blocks me out :-(
I can only switch carrier, but that's a hard option.
Do you think this could help?
Anyone had success?
http://forum.gsmhosting.com/vbb/f452/nvm-repair-android-phones-gift-spt-team-1296409/
Some more ideas, anyone?
Sent from my HTC HD2
I dunno i read around the forums try taking out the sim and sd card, delete the md5 file, and factory resetting. Then turn off your phone for 15 minutes. Havent tried it myself
Sent from my SGH-T959V using XDA Premium App
Light-라이트 said:
I dunno i read around the forums try taking out the sim and sd card, delete the md5 file, and factory resetting. Then turn off your phone for 15 minutes. Havent tried it myself
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Tried that, it results with new efs files being created with the default 000 IMEI :-(
I suspect I found the offsets of the IMEI in the file of the SGS4G (it differs from other models) but I can't decrypt/encrypt it so to write there the correct IMEI value matching the sticker.
Parallel to that I could find people able to do that to other samsung models , but no one that can do that to SGS4G
did u get a solution
hi i am using SGH-t959v samsung galxy s 4g. and i unlocked it using nv_data.bin file modification. after i unlocked it says NO service.
did u find any solution for it
Related
hi there experts
i am having a hard time sim unlocking this particular phone. i have no idea what else to do.
the applications by DaGentooBoy do not work. the code comes back NULL
there is no nv_data.bin file anywhere to be found in the phone
i tried the BML5 method, but the string is nowhere to be found in that file.
it seems that the t-mobile galaxy s 4g phone do not have this unlock code incorporated in.
i have tried Galaxy_s Unlock took from the market but it always gives an error saying that i have a problem with busybox. i have tried it on rooted 2.2 froyo the phone came with. i have 2.3.6 gingerbread on right now (stock from samsung loaded with kies and rooted with superoneclick 2.2) but no go same issues. i tried installing different busybox versions. still nothing. i have tried other roms, still nothing. the developers of galaxy_s unlock tool say that there are issues with busybox and droid2.2, but it does not work on 2.3.4, 2.3.6. nothing works.
i have tried and unlocked an att captivate with the galaxy_s unlock tool after root. that phone also had the codes coming up NULL and no nv_data.bin files, but it works with galaxy_s unlock tool.
i am reading here (http://techlab102.com/samsung-galaxy-s-carrier-unlock/) that the t-mobile vibrant phone has a bunch of bloatware that prevents busybox from installing correctly or at all. they said they installed some manager and uninstalled this bloatware, but fails to says which ones. i am looking at a ton of stuff in the phone with the manager, and i have no idea what to uninstall in order for the busybox to install correctly anf for glagy_s unlock tool to work.
if anybody can point me in a direction that would allow me to do this i would really appreciate it. thank you very much.
jmecherul
EDIT: this is the galaxy s 4g from t-mobile (no the vibrant). is it possible that the nv_data.bin files is somewhere else in the phone no in the usual spot?
The nv_data.bin should be found in
/efs/root/afs/settings.
i dont recommend the apps as ive tried them, and all of them nulled my imei. (maybe thats just me).
Sent from my SGH-T959V using XDA Premium App
i found it
wondering why the nv_data.bin is in that folder instead of just /efs on the galaxy s 4g. funny.
If your imei is already null and you have no backup of the efs folder or even the nv_data.bin, im sorry i cant help you, you should ask a true expert.
If you do have a backup of the original unedited nv_data.bin, youre in luck.
Step 1: delete the nv_data.bin file from the original folder.
Step 2: move the backup of the nv_data.bin file you have into the original folder.
Step 3: open up your hex editor of choice, and go to the nv_Data.bin file. Hit options, jump to address ->1468 after the ff, you will see 01 00 00 00. (these numbers represent the locks. 01 is the network lock.)
change the 01 to 00. Save it, and close hex editor.
Step 4: delete the nv.md5 file located in the same folder as the nv_bin file.
Step 5: reboot.
if you dun have the backup, i just spent time writing that for nothing T-T
Sent from my SGH-T959V using XDA Premium App
i see where it is now. i did read that procedure with the nv_data.bin on the website, but seemed complicated and i thought the file is somewhere else. but, follower the procedure and worked like a charm. thanks
hi LIGHT
thanks for the heads up. my imei was fine. i suppose by NULL you mean that it shows NULL instead of the 16 digits in settings/about phone/status. it was never the case with mine. i am a little bit of an idiot because i was trying to do it the easy way using the software instead of dipping my toes into a little bit of linux stuff. the procedure was right there in front on me (there is a big post about it) but mentions the software below the hard way. but, got it working and now shows network unlocked and takes other sims.
it is kind of funny how the att captivate worked with the GALAXY_S UNLOCK software and the S 4G does not. it seem that t-mobile is doing something funky. although, it just struck me that i could have called t-mobile and ask them for an unlock code, but i kind of wanted to do it myself.
thanks anyway. it is much appreciated
By null, i mean 0000000000000000.
But glad you figured it out.
Sent from my SGH-T959V using XDA Premium App
For future referencing, there is an easier method/guide here:
Err.... Apparently I cant post links yet, but just Google "dkszone unlock galaxy s 4g"
My IMEI number got changed and also WIFI and Bluetooth address are missing... how do the i fix
SR doesn't have nv_data.bin. Search for 'corrupt efs', there is a thread with the solution.
Try ODIN back to stock. Trying to unlock your phone did you?
http://www.en.lmgtfy.com/?q=corrupt+efs
Pick the first link
xcrazydx said:
http://www.en.lmgtfy.com/?q=corrupt+efs
Pick the first link
Click to expand...
Click to collapse
Nice, I need to use that more often!
ah, i tried all that option of restoring EFS... no luck.... my IMEI number is still unchanged... WIFI / Bluetooth not working.... Serial number of phone shown as 00000000
it does work and i can make calls/receive... is it possible to restore it from another skyrocket or modify any files
Try:
Dial:
*#197328640#
In service mode menu select:
[6] Common
[6] NV Rebuild
If the bottom of screen says:
Golden-backup exist
You can Restore Cal/NV
Then you can try:
[4] Restore Cal/NV
Then reboot.
DO NOT USE MENU ITEMS 1, 2, or 5 - These will wipe the hidden efs1, efs2, or efs backup partitions.!!!
Proceed at your own risk.
I tried using below option... still IMEI number not changed ...Serial number still showing 0000000
*#197328640#
In service mode menu select:
[6] Common
[6] NV Rebuild
Did you do select [4] Restore Cal/NV and reboot ?
Yes.. i did select [4] Restore Cal/NV and reboot.. is there anyway to rebuild the efs
So what exactly were you doing to the phone that caused the imei to be lost? Rom flash? Deleting files in /efs? Knowing the cause will help with solution. What Rom are you currently on? What file names are in /efs/imei folder?
IMEI folder contains - bt.txt / keystr / mps_code.dat... i set to default nv_ram from dial secret codes.
nkamurlekar said:
IMEI folder contains - bt.txt / keystr / mps_code.dat... i set to default nv_ram from dial secret codes.
Click to expand...
Click to collapse
If I'm understanding correctly, the reason the IMEI was lost in the first place was because you did a 'Load Default NV' from the 'REBUILD NV' menu?
Sorry, but your out of luck. That menu option rebuilds the efs partitions containing the IMEI information stored in mmcblk0p18 and mmcblk0p19 with default values and is not recoverable.
Is there no way to fix this? I'm in the same boat. I have the IMEI number (it's on a sticker on my retail box).........but which file(s) need hex edited to get it back in there? I had to do this with my Sensation once (I believe it was editing mmcblk0p4 5 and 6?).
Any idea on this phone???
If cschmitt says it can't be done.... it probably can't be done.
Sorry!
--
sent from my I727 TROLLING DEVICE using XDA premium. Questions? look here: http://forum.xda-developers.com/search.php
Not sure if this is relative but check out MobileTechVideos. Maybe he can help you.
From the sounds of it blk18 and blk19 have the IMEI embedded in there somewhere according to his post? I looked at them both and don't see it, though.
cybertlc said:
From the sounds of it blk18 and blk19 have the IMEI embedded in there somewhere according to his post? I looked at them both and don't see it, though.
Click to expand...
Click to collapse
Try pm'ing him (cschmitt). Dude is a genius.
--
sent from my I727 TROLLING DEVICE using XDA premium. Questions? look here: http://forum.xda-developers.com/search.php
mindmajick said:
Try pm'ing him (cschmitt). Dude is a genius.
--
sent from my I727 TROLLING DEVICE using XDA premium. Questions? look here: http://forum.xda-developers.com/search.php
Click to expand...
Click to collapse
Thanks, I'll do that.
cybertlc said:
From the sounds of it blk18 and blk19 have the IMEI embedded in there somewhere according to his post? I looked at them both and don't see it, though.
Click to expand...
Click to collapse
You don't see them because both of those partitions are encrypted. One is the working copy other is a fail over backup, in case the first is corrupted. They also contains radio calibration data, phone isn't much use without it.
Did you attempt the restore golden backup thing listed a few posts back?
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null http://imageshack.us/photo/my-images/546/sc20120828223834.png/
http://imageshack.us/photo/my-images/266/sc20120828223733.png/
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dutchthomas said:
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I tried ics and ginger stock and nothing
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
kishke said:
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
Click to expand...
Click to collapse
I try this method and repair the lock screen that did not work but still not working imei imei null / null thank
That is REALLY BAD.... Not sure what to tell you... Heard someone else did that and they were screwed....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
If it's only IMEI number that's missing use the search, there was a thread a while back with someone having the same issue, he got told to edit some file and enter his IMEI from the phone's sticker.
aiyoros02 said:
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null
Click to expand...
Click to collapse
Exactly what rom framework did you flash?
cschmitt said:
Exactly what rom framework did you flash?
Click to expand...
Click to collapse
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
aiyoros02 said:
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
Click to expand...
Click to collapse
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
aiyoros02 said:
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
Click to expand...
Click to collapse
Sorry to say then, without a nandriod backup you're SOL.
cschmitt said:
Sorry to say then, without a nandriod backup you're SOL.
Click to expand...
Click to collapse
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
talk2sharn said:
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
Click to expand...
Click to collapse
Check out these threads, there are solutions but you got to pay up at least €10
http://forum.xda-developers.com/showthread.php?t=2288390
http://forum.xda-developers.com/showthread.php?t=2287136
how to use efs1.bin efs2.bin and efs3 bin to restore imei
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
bmyury said:
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
Click to expand...
Click to collapse
howto backup/restore efs
dont know if it will fix the imei though
This may help if You are having "Unknown Baseband" Problem, Low Signal , No 3G
or using XXKP7
DOWNLOAD
http://www.mediafire.com/?24uc31ur1mc9di4
dev0xteam said:
This may help if You are having "Unknown Baseband" Problem, Low Signal , No 3G
or using XXKP7
DOWNLOAD
http://www.mediafire.com/?24uc31ur1mc9di4
Click to expand...
Click to collapse
you do realise that this is a modem file and it can potentially harm the device... I appreciate your effort but I am just worried if some one who is having a low signal problem and flashes this and looses their baseband/IMEI...
Btw what is the version number of the modem file?
It is a XXKPE + some features from the Samsung Service Baseband
Which is enhanced in this modem?
Sent from my GT-I9003 using xda premium
how can install it ?
dev0xteam said:
It is a XXKPE + some features from the Samsung Service Baseband
Click to expand...
Click to collapse
no offence but is it worth that risk??
I was just curious about it so I installed it and have been trying for two hours or so. Not enough time to make conclusions. But I can confirm it is not dangerous (also, if you are on cm, you don't even have to flash from Odin, so you don't touch the radio partition). Picture attached.
Look at the "Versión de banda base" field, which is the baseband. It now says service. Very interesting, thank you!
Sent from my GT-I9003 using xda premium
rodero95 said:
I was just curious about it so I installed it and have been trying for two hours or so. Not enough time to make conclusions. But I can confirm it is not dangerous (also, if you are on cm, you don't even have to flash from Odin, so you don't touch the radio partition). Picture attached.
Look at the "Versión de banda base" field, which is the baseband. It now says service. Very interesting, thank you!
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
how do i install the baseband without odin ??? am lil bit confused with it.
Do you use a cm build newer than cm 10 alpha 4?
Then just copy the modem.bin inside this .tar to /radio, change owner to radio:radio and permissions to 655 and reboot.
If, just in case, it didn't work, just move your old modem.bin to /radio again.
rodero95 said:
Do you use a cm build newer than cm 10 alpha 4?
Then just copy the modem.bin inside this .tar to /radio, change owner to radio:radio and permissions to 655 and reboot.
If, just in case, it didn't work, just move your old modem.bin to /radio again.
Click to expand...
Click to collapse
Well i didn't wait for your reply and flashed it via odin and i lost my IMEI no. .
Could u help me fix this issue now.
I have backup of efs folder thats done by cm10.
anigr88 said:
Well i didn't wait for your reply and flashed it via odin and i lost my IMEI no. .
Could u help me fix this issue now.
I have backup of efs folder thats done by cm10.
Click to expand...
Click to collapse
Easy, download a file explorer with root permissions, copy your efs backup and paste it over the efs folder in "/" (root folder)
You'll get your IMEI instantly (of course reboot).
If that doesn't work, download a modem.bin that works in your country and do what rodero said
giovox said:
Easy, download a file explorer with root permissions, copy your efs backup and paste it over the efs folder in "/" (root folder)
You'll get your IMEI instantly (of course reboot).
If that doesn't work, download a modem.bin that works in your country and do what rodero said
Click to expand...
Click to collapse
Thanks for the info.
let me try and i ll let you know the status.
EDIT : well i just fixed it by flashing xxkpe through odin. I guess my modem file was corrupted.
anigr88 said:
Thanks for the info.
let me try and i ll let you know the status.
EDIT : well i just fixed it by flashing xxkpe through odin. I guess my modem file was corrupted.
Click to expand...
Click to collapse
Good to know, I've had some of those mini-heart attacks when my IMEI got erased too, luckily I have a copy of my efs in every disc, every pc and every sd in my house
Sent from my GT-I9003 using xda app-developers app
giovox said:
Good to know, I've had some of those mini-heart attacks when my IMEI got erased too, luckily I have a copy of my efs in every disc, every pc and every sd in my house
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
I ll try to backup my imei using different methods. Hope that will reduce the mini heart attack for me in future
Nope, it is very unlikely that the problem was caused by the modem, its just that, since alpha 4, our device is using an mtd partition layout and Odin uses a bml partition layout, so you probably just screw up your partitions.
Sent from my GT-I9003 using xda premium
rodero95 said:
Nope, it is very unlikely that the problem was caused by the modem, its just that, since alpha 4, our device is using an mtd partition layout and Odin uses a bml partition layout, so you probably just screw up your partitions.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Now i don't have the IMEI issue but i still have the network drop issue and i tried to apply the modem file as u told but i couldn't find any difference in it.
The issue remains almost the same.
I need this network drop issue to be solved because of it am missing many important calls daily.
If some one could help me out, it will be a great help, thanks
I flashed this modem but i am still getting unknown baseband on my phone..any other way?
Sent from my GT-S7562 using xda premium
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.