Hi at all...
I need help ....my nexus s shows the dev IMEI004999010640000..so the EFS folder is corrupted.
What i did and what my problem is:
I bought my nexus s a few months ago make a efs folder backup like everyone recommend and everything was fine i run JB-DoubleX no problems at all. One day in the morning nexus s want turn on ....dead... i tried everything...nothing ....so i sent it for repair...last friday it come back with Gingerbread 2.3.4on it then i made the ota update to ICS and then flashed the last bootloader LC2 and radioXXI1 after that i flashed my standard JB ROM Double X. This time i don´t make a new efs-folder backup because i thought i already had made one and phone came from repair with same imei and serial number.
As i recognized that my imei was corrupted i thought no problem i have already a backup so i copy the efs backup folder in my phone like it is discribed in some treads here on xda but mei imei doesn´t change to the right one it stays at 004999010640000 now i run out of ideas.
Also courios things are that i have any problems with playstore or with calls, mms, sms all seems tho work normal.
Can anyone of you help me please...????
I have had this issue since shortly after the Nexus S came out. So over year and half. The phone is still in use by my wife, running latest jb build. Every feature works.
First, try to flash it back to factory stock. If that don't work, copy over the efs folder, but remember to boot into CWM and choose the "fix permissions" option.
Thanks guys for the answers...
But I have allready flashed stock ROM from Google Server (Gingerbread 2.3.x) with fastboot....not working.
Flashed Gingerbrad 2.3.x with Odin....same ...not working followed some treads here on XDA....allways same result....generic IMEI.
So now I have a backup of my efs that seems to mismatch to my phone after repair....so i think there is no hope to get back my IMEI..
I think its a md5 hash problem i believe that the md5 of the nv_data.bin(or an other file in the efs folder) must match to some other md5 somewhere in the system....otherwise the change is locked.
This is not a fact its only what i think by myself.....
S.R.
Related
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
I have been running a rooted samsung infuse with various roms for the past 6 months. I went to flash the latest modem this morning and when my phone came back on I had no service. At that time I was running CM7 and updating to the KK4 modem.
As I have worked through this problem I have returned to stock via ultimate unbrick. I have searched all over, but cant seem to find a solution.
Details:
Samsung Infuse running Stock 2.2.1
Problem:
No Service
No IMEI - reads null/null
About says: Baseband Version: Unknown
after doing several hours of research and trying various things I have not been able to find a solution.
Any help would be greatly appreciated.
I am not so sure if KK4 would work on 2.2. It is a GB modem.
And flashing back to stock overwrites modem and kernel and all back to stock, except formatting internal SD.
It appears I may have some backups of my nv_data files under:
/efs/root/afs/settings/
with the following files:
.nv_data.bak
.nv_data.bin
.nv_data.md5
can someone tell me if these are backup files and if I just need to move them into some other directory?
What directory does the phone read the normal nv_data files from?
Thanks
If you have a backup of your efs folder why not just try putting it where it would usually go?
well the easy fix that adam outler said would be to delete the efs folder all together and you will get a generic imei number but i never tried that. somehow you wound up with corrupt files in the efs partition. but if you have backups you can try to copy them over the originals.
you can also dd the efs partition and tell it to ignore bad blocks with
dd if=/dev/block/stl3 of=efs.img conv=noerror
this will make a backup of whatever is still good for a last ditch effort to recover what ever files you can.
my guess is that you played with an aosp rom. i believe that converts /efs to ext4 since rfs is closed source. i dont know how our aosp kernels work, since it is all unofficial lb may have had a different way to do it. but im guessing the conversion either corrupted the partition or that the kenrel you have cant read ext4. you might just need to install a voodoo kernel for the phone to be able to mount it. im not really sure.
@wiredcowboy....have got it fixed buddy??
i m also having same issue....
khan_frd2002 said:
@wiredcowboy....have got it fixed buddy??
i m also having same issue....
Click to expand...
Click to collapse
This was a long time ago. But I believe the solution was exactly what was said above. Delete the EFS folder and have it recreate your IMEI. You should also check to make sure you have a phone compatible modem. Check your modem and reflash another one if that's where the problem could have come from.
Almost same Problem
Even I have the same problem, but with a slight plus point
Sometimes, I get the network, but after a while,it's gone .
If I'm on a call (when I luckily get network) , it gets disconnected within a minute or two .. and in a minute ,I get back the signals (nd sometimes,it takes hours to get back the network)
What could the problem possibly be ??
Is there anyone on the forum to help me out ??
Thanks.
P.S : There is no fault with the Sim,I have tried multiple SIMs , the problem remains same throughout .
Ok, so I am somewhat new to the whole rooting and flashing of phones. I own the Samsung Galaxy Ace, from Koodo, and last night following a tutorial to install CWM4 and updating it to CWM5, followed by making a Nandroid backup and flashing Ice Cream Sunday Final, I had some issues.
The flashing went without any real problems, except one with installing CWM, but I sorted that out. I booted into the new ROM, and liked it, but after testing it I noticed it wouldn't load anything from my Koodo SIM card, like my contacts, and in the notifications bar where it shows your service carrier, it just showed a number. I was still able to send and receive calls and messages, but it was as if it didn't fully support my SIM. After finding a few things I didn't like with the ROM, I decided to use my Nandroid backup to restore, and after following a tutorial, I "successfully" restored the backup, according to Nandroid... But upon booting the phone, it was stuck on the boot logo.
After about an hour of searching, I was able to find out that CWM5 has issues restoring backups through Nandroid, and that I was screwed out of using my restore. I found the stock Koodo 2.3.4 ROM, and flashed it with Odin, and had to do a Recovery System Wipe to get out of a bootloop. I thought I was back to square one, and began installing my apps again and such with no issues.
---------EDIT---------
So, after hours of fooling around I replaced my save file with Root Explorer, like I was before, but then gave Terminal Emulator SU Permissions and used it to give the save file the right APP ID and Permissions, and it's working without freeze-ups now. I also used SQLite DB Editor to edit a fresh save on Where's My Water to reset my progress back to where I was before the update broke my save.
I am still wondering why my SIM Card didn't work properly in that ROM, and if there is a way I could make it work.
Is your model number GT-S5830D with baseband S5830DTLKI4? This is my model of the SGA and I've been reluctant to try flashing any ROMs because I can't find any success stories for this exact model. I'm also with Koodo and have concerns about how the SIM card will handle the custom ROMs too. If you do have this model, what has your experience been since your original post?
Winner Winner Chicken Dinner!
dhx138 said:
Is your model number GT-S5830D with baseband S5830DTLKI4? This is my model of the SGA and I've been reluctant to try flashing any ROMs because I can't find any success stories for this exact model. I'm also with Koodo and have concerns about how the SIM card will handle the custom ROMs too. If you do have this model, what has your experience been since your original post?
Click to expand...
Click to collapse
My model is GT-S5830D and I am on that baseband and have tried a few ROMs, all of which work. I would say try a ROM as the you should be fine, and you can always do a CWM Backup.
The SIM issues I was having has been resolved, as it is simply caused by being in Canada, and my carrier not being in the phones list, so it still displays a number, but all of my features (Calling, SMS, MMS, Data, etc) work fine.
admiralspeedy said:
Ok, so I am somewhat new to the whole rooting and flashing of phones. I own the Samsung Galaxy Ace, from Koodo, and last night following a tutorial to install CWM4 and updating it to CWM5, followed by making a Nandroid backup and flashing Ice Cream Sunday Final, I had some issues.
Click to expand...
Click to collapse
Where is this tutorial??? I have yet to find one for the Koodo Ace that works.
I tried all the ICS flavours on captivate, finally ended to stock KK4, then I decided to try WeUI rom. After installing the ROM, I get an error message of MM#6.
I went to stock I897UCJF6 using one click download; still I am having the same problem of MM#6
I tried restoring to stock KK4 again. Unfortunately, I am still stuck at error MM#6.
I saw IMEI is changed to default not the actual number found at the back of phone. Tried restoring the IMEI using the other thread in development category. MM#6 error still exists.
I can see the signal bars in the phone, but I cant receive or make calls.
PLEASE HELP !
Please don't make double post just because you're frantic.
sulaimanz said:
I tried all the ICS flavours on captivate, finally ended to stock KK4, then I decided to try WeUI rom. After installing the ROM, I get an error message of MM#6.
I went to stock I897UCJF6 using one click download; still I am having the same problem of MM#6
I tried restoring to stock KK4 again. Unfortunately, I am still stuck at error MM#6.
I saw IMEI is changed to default not the actual number found at the back of phone. Tried restoring the IMEI using the other thread in development category. MM#6 error still exists.
I can see the signal bars in the phone, but I cant receive or make calls.
PLEASE HELP !
Click to expand...
Click to collapse
Trying repairing your IMEI to be the original assigned to the phone.
DMgals said:
I got my original IMEI back on Galaxy S (after I tried ICS custom rom) with this procedure:
1. Delete all 2 nv_* files in "etc" folder
2. Reboot into download mode
3. Flash back to gingerbread 2.3 XXJVU stock or possibly back to eclair 2.1
4. To me it worked and I got my original IMEI now restored.
5. I am not kidding that's how I got it really fix from my 47000000...XX funny looking IMEI.
You can try this procedure and hope it works for you like it worked for me.
Click to expand...
Click to collapse
Try that.
Koodos Nexus S i9020A.
I took ICS update a few days ago and phone was very buggy... not to mention no data. I wanted Gingerbread back... Looked in this forum and found a post how to unlock and recover to gingerbread. Followed dirrections and got phone unlocked and before restoring to gingerbread, I took a backup. Then did the gingerbread restore. The phone booted fine (with the now unlocked symbol at bottom). A voila in gingerbread... But no service (no bars with a x). Phone funtions fine other than not being able to call, text, or use 3g. After futher searching I found that there's diffrent versions of Nexus S software. And didnt put the i9020a file on it.... so im assuming thats why its not working. I went back into CWM and tryed to restore my backup I made... I get MD5 Mismatch... I also wanted to be sure it wasnt my SIM card so i put my girlfriends SIM card in and same thing no service..PLEASE HELP... I know im a NOOB to the fullest.. but I really dont have the money to buy a new phone. Thanks in advance for anyone willing to give me some help.
Bruce