I bought captivate from ebay, the phone came rooted.
I installed few applications to unlock the phone, tried to use PC .bat files to extract the code, no luck, I was getting no code at all or FFFFFF.
Later I found out that in my main sd directory i have a 40mb nv data with FFFFFF.
I am not sure if this was generated as a backup .bak file from efs folder, so I went and installed terminol and tried accessing the efs folder, no luck, but I can access other folders. if i access efs it says premission denied, but using app android mate i am able to browse efs folder but it shows 0 files. other folders are ok.
My question is, after 2 days of headache, what should I do now, I have been searching all day long for answers.
Also if i run .bat files from PC while device connected, sometimes i also get permission denied message.
I'ts possible this phone was flashed before because I get the FFFFF from nv data?
plz help.
ok i was able to copy via emulator using this line
busybox cp /efs/nv_data.bin /sdcard
to sdcard and the file was 2mb in size, i have another .bak file 40mb in size, so, is this some kind of an application did this to the phone?
The phone is
2.1 update 1
i897ucjf6
kernel 2.6.29
eclair
i also have md5 file copied to sd is 1kb file.
I would say the phone definitely was flashed. With android mate did you allow for hidden files or something like that. I use root explorer.
Can you make and receive calls?
Miui
First of all, you don't seem like you know what you're doing, so back up /efs in its entirety to the sd card, then again to your computer before you do anything else and break something.
Secondly, if you're on 2.2 (which I assume you are), there is a thread that tells you how to do a carrier unlock with step by step instructions. Search for 'carrier unlock' and it should be on the first page of results.
nothing like hidden files or anything, i'll try but i get accessed already with emulator
i have a backup of most of the efs content, that's 2 files or so, i will try to search for additional files. I think one of the apps did a .bak file to the nav_data and saved it in the sdcard folder.
i'm on 2.1 i assume it was flashed forwards and backwards because the nv data is 40mb but has FFFFFF in it.
what do you think?
I saw this thread http://forum.xda-developers.com/showthread.php?p=8182729#post8182729
i think my last resort. I'll try to search for the thread you specified but im running 2.1.
p.s no luck on hidden files i cant find that setting.
p.s i bought this phone on ebay cant make calls until i unlock it for my sim. but i do have wireless connection.
p.s my kies keeps saying "connecting" to the phone, but that's i guess a different problem, i run drivers and kies full from samsung site.
nv.log shows
Fri Nov 5 14:00:33 2010: secondary NV built.
Fri Nov 5 14:00:39 2010: Plain text NCK deleted.
Thu Feb 17 10:42:30 2011: NV data back-up begin.
Thu Feb 17 10:42:31 2011: NV data back-uped.
anybody99 said:
nothing like hidden files or anything, i'll try but i get accessed already with emulator
i have a backup of most of the efs content, that's 2 files or so, i will try to search for additional files. I think one of the apps did a .bak file to the nav_data and saved it in the sdcard folder.
i'm on 2.1 i assume it was flashed forwards and backwards because the nv data is 40mb but has FFFFFF in it.
what do you think?
I saw this thread http://forum.xda-developers.com/showthread.php?p=8182729#post8182729
i think my last resort. I'll try to search for the thread you specified but im running 2.1.
p.s no luck on hidden files i cant find that setting.
p.s i bought this phone on ebay cant make calls until i unlock it for my sim. but i do have wireless connection.
p.s my kies keeps saying "connecting" to the phone, but that's i guess a different problem, i run drivers and kies full from samsung site.
nv.log shows
Fri Nov 5 14:00:33 2010: secondary NV built.
Fri Nov 5 14:00:39 2010: Plain text NCK deleted.
Thu Feb 17 10:42:30 2011: NV data back-up begin.
Thu Feb 17 10:42:31 2011: NV data back-uped.
Click to expand...
Click to collapse
*#7465625# <- Dial that number. Does it say 'off' for everything? If it does, you already have an unlocked phone.
If you're on 2.1, you might as well try the SGS Unlock tool from the market in the off chance that it WASN'T flashed forward and back to 2.1. If it was, there isn't really a reason to stay on 2.1. You might as well flash to some 2.2 rom and follow this procedure I mentioned earlier:
http://forum.xda-developers.com/showthread.php?t=831569&highlight=carrier+unlock
it says network lock is ON.
i tried the market app tools, 2-3 tools, doesn't work. they doesn't work because i have extracted nv data and the code is FFFFFF. now i don't know if it was flashed forwards and backwards, i'm just assuming.
rom 2.1 or 2.2 means the version software? can i update to 2.3? what's the best way to update it?
also i have 2 bin/bak files, 1 is 2mb and 1 is 40mb, which one should i use with the thread you specified?
in efs folder i had nv data bin as 2mb and in sdcard i had nv data bak 40mb
nv data bak file created just yesterday i think as the date says 29march.
his Step 1: Install / Verify that you have a v2.1 ROM or v2.2 ROM installed.
does it mean i can use it on my 2.1 as well?
I have no idea why one of yours is 40mb, but it sounds messed up. Both nv_data.bin and .nv_data.bak are supposed to be 2mb. You can use either, as they're supposed to be the exact same file. There shouldn't be any files in /efs that are 40mb.
You're all over the place. You really need to spend a day or two reading the forums; especially the stickied threads about how to flash a new rom.
And yes, it means you can use that procedure on a 2.1 rom.
it was nv_data.bak inside sdcard folder, not efs.
but anyway, i think i got it. in that thread you specified some people said there's an helroz app does the same thing, unlocking without using a code, so i used it and it worked, network lock is now off and it catches orange provider.
i think the only thing left is to root it to a new version.
I would flash back to stock 2.1 using Odin and do a Master Clear. Then root phone again and and install CWM. After that flash a custom rom.
Have you tried the app Galaxy S Unlock from the app store, worked well for me.
Fixed problem.
Got the phone from ebay was locked, was unable to unlock with most market apps, but helroz app got it unlocked the same way his thread specifies, by replacing the FFFFFFF. my nv data file was bad but imie code was ok. i got it unlocked, then flashed to stock + master clear with odin, then i got unregistered error with kies mini program, the nv_data created by the helroz app wasnt so good and had bad product code, followed the thread at http://forum.xda-developers.com/showthread.php?t=881162 to fix the file, replaced old file, first rooted, then used emulator and busybox with cmd only.
got a good product code, then did once again a master clear, then upgraded to 2.2 via kies mini, got a fresh version and a clear phone.
i spent 3 days on that averaging 10 hours a day. madness.
Related
This Guide is for any user that has a Rom installed. This will back-up almost everything the user has put on the phone.
So, here are some things you need.
Heimdall One Click KB2 - http://forum.xda-developers.com/showthread.php?t=1266172 (thanks to AdamOutler)
1) First, make a nandroid backup.
2) Make an /efs backup (adb pull /efs) (also can use an app called nitrality available in market)
3) Now, you will need to Plug in your phone to the computer. Take ALL the folders on your SD card and copy them to your laptop. (Mine was user/android/sdcardbackup)
4) Remove Micro-sd card, and SIM card
5) Open up your dialer and dial this code *2767*3855# THIS WILL WIPE YOUR SD CARD and /DATA
6) Reboot the Phone
7) put your Phone in download mode, open heimdall One Click and insert the phone and make sure that heimdall recognizes it
8) Flash the new firmware Bootloaders not required
9) Have the Phone Boot up Completely (takes a long time)
10) Check to see if your /efs has been edited. Use this thread http://forum.xda-developers.com/showthread.php?t=881162 (and your efs backup) to get it back.
11) You might want to dial *2767*3855# Just in case if there is anything left.
12) You should be running KB2, have your SD cleared, and ready to be turned into samsung.
Post Questions and comments below!
i decided to save this one, no clue why, just wanted to feel important...
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
bigbooty said:
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
It isnt supposed to erase the /efs but ill include it, thanks!
sepherian said:
It isnt supposed to erase the /efs but ill include it, thanks!
Click to expand...
Click to collapse
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
When my cappy messed up, my imei got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs. Product code was different also. Flash enough roms and it can mess up something as someone might be a novice coder and mess your device up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: fixed Imei
Nucleartx said:
When my cappy messed up, my meid got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
meid? i think you mean imei?
bigbooty said:
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
Click to expand...
Click to collapse
Yes, I know. This Flash is not intended to mess with the /efs AT ALL, i have checked the package and it has no reference to /efs in the scripting. The post including the package also says this:
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
Click to expand...
Click to collapse
So as you can see the number i have them call wipes the data and SD but they have their nandroid and SD backups. The number i have them call also doesnt touch the /efs. Trust me, I tested this method before i posted it and i didnt make an efs backup and my IMEI was perfectly fine afterward. I assume that nothing here messed with my /efs at all.
The only thing that would change the NVdata.bin would be an unlock tool. And i doubt that it even changes it.
OP was updated with more accurate steps.
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"
Hi guys,
One miraculous day, my efs folder became corrupt, when it just so happened to be the week after the hard drive on my computer took a dump! What a week this has been.. I was wondering if it is possible for someone to zip their EFS folder and send it to me to see if I can't get this phone to connect back to the network again. I honestly think there are applications on androids marketplace that will wipe things if you have superuser installed.. because it was like BAM, one morning I wake up and my efs folder was deleted the day after I had installed some new apps.
So my question is - Will someone send me a backup of their EFS? If that won't conflict with their phone of course -- I would send it back to Samsung, but their 3rd tier support has no idea what I'm talking about - they just hear root and think I'm a piece of trash.
Any help would be greatly appreciated - I have not seen anything about trying someone elses efs so I thought it could be a bit experimental as well.. Thanks
-Brett
Salmiery said:
Hi guys,
One miraculous day, my efs folder became corrupt, when it just so happened to be the week after the hard drive on my computer took a dump! What a week this has been.. I was wondering if it is possible for someone to zip their EFS folder and send it to me to see if I can't get this phone to connect back to the network again. I honestly think there are applications on androids marketplace that will wipe things if you have superuser installed.. because it was like BAM, one morning I wake up and my efs folder was deleted the day after I had installed some new apps.
So my question is - Will someone send me a backup of their EFS? If that won't conflict with their phone of course -- I would send it back to Samsung, but their 3rd tier support has no idea what I'm talking about - they just hear root and think I'm a piece of trash.
Any help would be greatly appreciated - I have not seen anything about trying someone elses efs so I thought it could be a bit experimental as well.. Thanks
-Brett
Click to expand...
Click to collapse
This is an interesting request, Brett.
I thought the efs.rfs file contains one's phone imei number/network id etc.
idk for sure...
I thought using someone else's imei is kinda like "let me borrow your ss# so i can check the ss office to see if mine is working.
I didn't know if you found this link and tried it?
http://forum.samdroid.net/f28/complete-imei-restore-how-1817/
http://forum.xda-developers.com/showthread.php?t=882039
http://forum.xda-developers.com/showthread.php?t=953436
Fortunately for me, I had a efs backup on my hd.
I think I also saw scripts in Zeus and Doctor ROM that backs up efs also prior to flash..
good luck
I wasn't trying to steal anyone's IMEI.. I just have tried multiple techniques, but I have not tried the first link..
I've been having trouble getting a shell with adb, does it need to be in download mode?
I was trying to see if it were possible to copy someone's existing files, and use a hex editor to change things, but reading into it, the IMEI is not able to be edited easily without knowing the encyrption type.
I'm just frustrated and have been back and forth with both at&t and also samsung (Their support is a joke, no one I spoke with even knew what the EFS folder was..)
I will try this technique and will report back later when I get home from work tonight. I've been reading a lot of similar issues with the null/null IMEI in the infuses and the guy at the AT&T store said that this was the reason they stopped selling the phone in their store.
Thanks for the help, I'll let you know what happens.
-Brett
Goodluck.
From the tone of your post, I didn't suspect any malice...I had a gist of what you were trying to do.
From reading some of links, there may be some method of recovery.
I hope that you're able to get it back.
I posted one a while back. I think it was in the q&a section. I won't be at my computer for a couple of days or I'd upload it for ya. Try searching or scrolling thru there.
Edit: I just uploaded an EFS.zip, unzip and flash the included efs.tar thru Odin or heimdall.
I had the same problem but i fixed it through Odin. There is an option in odin where you can click on the side (sorry i just reformated the comp so i dont have odin installed) that says something about the EFS. Try that, it fixed it for me.
On a related note. I thought I read somewhere that typical backups such as tibu and nandroid do NOT back up the efs folder. Is this correct? Should we all be doing this manually to protect against corruption?
Try searching here or on market. I remember there was this app called "nitrality" something. This app backs up EFS that we can restore in case we mess it up.
diablo009 said:
Try searching here or on market. I remember there was this app called "nitrality" something. This app backs up EFS that we can restore in case we mess it up.
Click to expand...
Click to collapse
I did try to dl that app and ran it. It didn't work for me. The app hung up the system until you fc it.
If you're versed in linux or Term emu, you can use script to back up your efs.
If you had flashed zeus or doctorz, there are scripts build in that backs up your efs.
if you had root explorer, you can find efs folder in your root. long press on the folder allows you to create zip or tar of this as well.
Any harm in just copy/paste the whole folder to external SD with root explorer? Then copy paste to windows over USB? Will permissions get messed up?
I think I've already backed it up but there have been a couple threads on this. Wonder if it should be part of superthread or a sticky...do this first :...
Sent from my SAMSUNG-SGH-I997 using XDA App
rxnelson said:
Any harm in just copy/paste the whole folder to external SD with root explorer? Then copy paste to windows over USB? Will permissions get messed up?
I think I've already backed it up but there have been a couple threads on this. Wonder if it should be part of superthread or a sticky...do this first :...
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
no problem with copy/paste that I know of.
Being cautious, I have a zip, a tar, and the whole folder on my PC, USB and box.net.
Hypothetically,
I have access to another Infuse on the same family plan at that, if i were to copy the efs folder to mine what would that do?
I want to make sure not to have the same IMEI number on the network though, but this could save me a lot of hassle...
any thoughts?
Read the threads on the links I provided...you will get more understanding.
I have multiple times, but the first post that seemed like it would be the best fix, I have to get him to send me a fixed nv_data file and he seems to be unresponsive at the moment.
I think I'm going to root the 2nd infuse, back up her efs folder (MULTIPLE times lol) and fix it so it's generic and not an exact replica of hers..
Do you see any problems there? I'm definitely not an expert at all with this.
Salmiery said:
I have multiple times, but the first post that seemed like it would be the best fix, I have to get him to send me a fixed nv_data file and he seems to be unresponsive at the moment.
I think I'm going to root the 2nd infuse, back up her efs folder (MULTIPLE times lol) and fix it so it's generic and not an exact replica of hers..
Do you see any problems there? I'm definitely not an expert at all with this.
Click to expand...
Click to collapse
In order to see what is on the root of a phone, you may need to root it.
Once rooted, you can look for the efs folder.
I haven't used z4root in a while on an unrooted phone, I don't know if this program will let you see the root folder or not. It's possible.
The efs on my phone shows several programs and folders.
One of the folder is /imei. I suppose this is where the unique id is located.
read the thread: http://forum.xda-developers.com/showthread.php?t=1372455
as you can see, the efs contains unique id...i'm not sure of even how to make up a different imei file from using someone else's efs folder.
if your phone boots up but does not connect, if you go to settings/about phone/status
does it list the imei?
if it does, are you able to use a script in terminal emulator to back it up?
if you can't find the script, you can try flashing doctor or zeus rom, they have scripts to back up your efs folder. then try locating it on your phone.
the other thought i had was for you to call your provider to see if they can give you your previous imei number.
I'm only reasoning from what I have read...these are new territory to me.
Right, I have rooted my phone and for whatever reason the EFS folder is completely empty... The folder is there, but completley empty.
I have the IMEI number, its on the back of the phone as well as AT&T gave it to me.
The fact that my entire folder is empty, and I hadn't backed anything up because I never flashed the kernel or rom makes me think that the android marketplace does have malicious code that simply says:
if(phone==rooted){
wipe efs foler
}
continuing to pull my hair out and attempt new things, if anyone has any ideas let me know.
Salmiery said:
continuing to pull my hair out and attempt new things, if anyone has any ideas let me know.
Click to expand...
Click to collapse
Check out Post # 5, I just edited my post.
its not simply a folder its actually a partition, on Linux you can mount drives/partitions however you like so it can appear to be under another directory and be an entirely different device.
you can make a .rfs image from the dd command through adb or terminal emulator.
if it is corrupt you "may" be able to salvage it through options of the dd command.
I gotta look up the device path and whatnot but if there is anything on there, visable or not, you might be able to recover the unique files and paste them over the files from someone else's efs backup. if not I have heard but never tried it, but I heard that fromatting the partition will cause the system to generate a generic efs, but I don't know for sure.
edit: the device location is /dev/block/stl3
you can dump it to the SD card with
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
if there are bad blocks I think but not quite sure you can add noerror to the end
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096 noerror
but if the information has actually been deleted unless it was overwritten it is mostly intact. it is not well known that delete doesn't actually delete the data, even after a format data can be recovered with the right program. if the dumps come up empty there is also dd_rescue and foremost but I don't know if those commands are available on android, but you may be able to loop mount the dump on a Linux box or in cygwin and try the ddrescue or foremost commands.
http://www.linuxquestions.org/questions/linux-newbie-8/learn-the-dd-command-362506/
hopefully you can recover something. and learn something along the way. this is also useful for recovering deleted files and securely deleting stuff you want gone for real.
i remember I lost my efs on my captivate. There are tools in the forum to get it back.
Salmiery said:
Hi guys,
One miraculous day, my efs folder became corrupt, when it just so happened to be the week after the hard drive on my computer took a dump! What a week this has been.. I was wondering if it is possible for someone to zip their EFS folder and send it to me to see if I can't get this phone to connect back to the network again. I honestly think there are applications on androids marketplace that will wipe things if you have superuser installed.. because it was like BAM, one morning I wake up and my efs folder was deleted the day after I had installed some new apps.
So my question is - Will someone send me a backup of their EFS? If that won't conflict with their phone of course -- I would send it back to Samsung, but their 3rd tier support has no idea what I'm talking about - they just hear root and think I'm a piece of trash.
Any help would be greatly appreciated - I have not seen anything about trying someone elses efs so I thought it could be a bit experimental as well.. Thanks
-Brett
Click to expand...
Click to collapse
Uh, NO than you. My EFS folder has nothing to do with yours. Don't know how that would work...
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,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
penandweb said:
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
Click to expand...
Click to collapse
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly.
There are different backup solutions (e.g. EFS Pro) confirmed working which may help you prevent future issues. I prefer the manual backup using adb shell or terminal emulator:
dd if=/dev/block/mmcblk0pXX of=/storage/SdCard/efs.img bs=4096
(XX needs to be replaced with the model specific partition number as they use different partition tables)
Restore:
dd if=/storage/SdCard/efs.img of=/dev/block/mmcblk0pXX bs=4096
thanks LS.xd, but i guess i have a pretty solid backup as i did create backup various ways, some were corrupt, but one that i working with has nvdata and every other file along with imei pretty intact....
i can open it up with winrar, and open the nvdata with hexeditor, i was wondering if i could confirm some way that the back up is actually 100% solid?
wondering if the partition's aren't aligned. I don't know for sure if EFS folder in the root directory is the same as being pointed by /mmcblkp03/platform/by-name/EFS ?
i mean they should be the same thing, its just a redirection right?
what should i be doing now? the baseband is unknown and the imei wont just work, waste the phone? or it could be done via some boxes or some other process?
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
penandweb said:
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
Click to expand...
Click to collapse
So you got some non TWRP made EFS backup, too? You can list your partitions using shell:
[email protected]:/ # cat /proc/emmc
You can use the dd command once you know the layout. Backups not generated manually may only be restored with the specific app/version and are probably not compatible using other restore methods. For my OnePlus 3 EFS backup can generated fine using TWRP but restoring it screws up the partition. Manually created image works fine. As I don't have a Note 3 Neo I don't know how it behaves for your device.
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
penandweb said:
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
Click to expand...
Click to collapse
After 3 years I had to retire my HTC One S. I flashed roms and firmwares up to 3-4 times a week without having any issues. One sunny day some update bricked then nvdata. I spent a bunch of hours trying to restore it in different ways, extracted data from stock firmware as well as using dumps from other user's phones, as some users reported this error fixed doing so. Even when the files was identical it just did not work for me. Changing the mainboard was the only possible solution so I decided to get a new device.
All I want to say is try to restore a valid backup in a way confirmed working. If you don't have a usable backup ask in your device's forum for somebody may upload it. Or spend 100 hours messing around with hex editors until you reach then point where you realize its cheaper to switch the device as wasting a year's holidays browsing the internet for some solution.