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.
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.
Hi, I am new to xda and i'm also quite new to the flashing process. I have a captivate i896 and successfully flashed a rom on to my phone. However after doing so the phone is unable to connect to my mobile carrier. I have also tried to install a modem from the stickied thread how ever it gives me an error::
cwm 3.0.zip error
i'm going to try to flash the helly bean rom in hopes of getting that fixed.
also in the about phone section it says baseband is unknown... ive googled that and it said my IMEI is corrupted or something or other.
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.
hi every one i dont know what to do now at this point i flashed my phone to the cyanogenmod 10.1 nightly which worked but the problem i started to have was could not send txt or calls but could browse the web on 4g so i though i would just restore from my back up of recovery image i did back to original stock which i noticed the proble still ocurred then i tried flashing to another rom called smooth liquid which now at this point it was only stuck on roaming my phone does seem to have the imei still in place, ive been reading aroud and did odin flash to stock touchwiz rom but still did not correct apparantly something messed up with the radio i went to the other forum were i woul dhave to flash the radio i tried the first one which was the lates one vrlk3 modem but when i tried to flash it in clockwork mod it gave me some error saying bad install so i attemted the one below that modem which is VRLK1 which flashed successfully but still did not seem to fix my service issue i read something about RPM on that same forum but there was many options to download i didnt know which one or if i even had to please help me someone. :crying:
Which build did you odin back to? Also did you do the reprovision code in the dialer? If not odin the F2 ICS build and put this in the dialer... *2767*3855#
x714x said:
Which build did you odin back to? Also did you do the reprovision code in the dialer? If not odin the F2 ICS build and put this in the dialer... *2767*3855#
Click to expand...
Click to collapse
the build or what it says here is COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar which is the jelly bean official ota
Flash this with odin http://goo.im/devs/invisiblek/i535/HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 and then in the dialer put *2767*3855# that should fix you up. Then just odin back to the K3 JB release.
ok thanks lets hope this works im trying this right now lets see what happens would it matter if im currently rooted??
droidman89 said:
ok thanks lets hope this works im trying this right now lets see what happens would it matter if im currently rooted??
Click to expand...
Click to collapse
do i have to do any radio flashing in addition to this stock rom flash?
x714x said:
Flash this with odin http://goo.im/devs/invisiblek/i535/HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 and then in the dialer put *2767*3855# that should fix you up. Then just odin back to the K3 JB release.
Click to expand...
Click to collapse
Thanks a million man you saved my life it worked thanks again
Youre welcome!
It Worked
I just want to say this post saved me tonight. I had searched the forums and tried everything to get my phone operational after flashing Slim's 4.2.1 ROM; which I learned I should not have done ... too late. I was stuck on roaming and no matter what I tried nothing worked until I found this post.
Thank you so much for your help.
I rooted my phone, everything was fine running SpaceX Kernel until i started getting reboots. i flashed arters kernel and when my phone restarted from odin i got a message saying : This phone has been flashed with unauthorized software and is locked. the phone won't connect to the network. if i flash the stock firmware with stock kernel it won't boot for some reason. It only boots up with a rooted kernel but my baseband says unknown and my imei is null. if i flash darthstalker ROM i get the baseband back but imei is still null, i tried changing the imei and masking it with apps but no luck. people keep saying that my efs folder got corrupted... so i was gonna try copy somebody's folder to see if my phone connects to the network. that's where I'm at, this sucks and I'm desperate for help. by the way, right now I'm running stock COI5
Anything will be appreciated.
If you search someone else made a very similar post like this. A few options inside. Good luck searching
BADASS NOTE 5 & 4 & LG G4