[Help] Phone won't detect sim. Unknown Baseband and IMEI - T-Mobile Samsung Galaxy S II SGH-T989

So... I seem to be having the efs corruption issue with my co-worker's phone. I've been searching all over and have found how others have solved the problem, but it seems that our nv_data.bin is not located in our efs directory.
Does anyone have any idea where these files are? I need to check the last modified dates of their backup files to see if I can restore them >.<
Any help is greatly appreciated!!

Bump.. If anyone knows where these files are this could help us from running into the corrupt efs problem that many people have had. Usually backing up your efs prevents your phone from becoming unable to function as a phone.
I do remember reading something about our unlock code not being present in our nv_data.bin.. And when I check my efs folder in both my, as well as my co-worker's phone there is no nv_data.bin so maybe it has been relocated??
Anyone with knowledge on this subject.. your input would be greatly appreciated! I'm also gonna read over the unlock threads to see if there is any relevant info there.

I am having this problem now, I know you posted this over a month ago, but please tell me you know the location of the backup files or any other solution for this?'
Thank you,

[Q] T989 - Baseband and IMEI Unknown
I have searched and read many threads already. I understand the i9100 uses a file called nv_data.bin and requires its .bak file for a fix.
But, I dont think the t989 is the same because these files dont seem to exist, or at least not in the locations the threads for i9100 state. I am wondering if anyone has had this problem and/or how they fixed it. I know it was caused because of trying to unlock, but I'm looking for a solution.
Thanks!

just buy one of those $20 online unlock or go to your local phone kiosk to have it unlocked
any one with a machine to unlock Samsung phones can get this phone unlocked easily
there's no software unlock yet, as you have found on your searches

I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"

svahora said:
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
Click to expand...
Click to collapse
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!

KillaHurtz said:
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
Click to expand...
Click to collapse
What does the (d) stand for?
And, how can I make sure this never happens again in the future? I know there are backup options out there (CWM, Nandroid), but are there any that make a complete clone of the phone's image? In case I mess up the efs or IMEI files again I can restore and be ok.
Thanks!

T989D = Canadian release of T989
they are identical, the just use the D for Canadian

AllGamer said:
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
Click to expand...
Click to collapse
Would a Nandroid backup fix this in the future?

is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder

AllGamer said:
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
Click to expand...
Click to collapse
I wonder if the new Galaxy Nexus has its IMEI files stored similarly. If so, we can join forces with that forum group.

If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.

-Mr. X- said:
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
Click to expand...
Click to collapse
Did it twice, the stock rom, modem, and kernel.

The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).

cyberjam said:
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
Click to expand...
Click to collapse
Would the KL1 work any different than the older one? I tried ODINing the original one, and it didn't work and increased the count so I didn't try the KL1.

I just got my replacement phone yesterday for this same problem. Flashed the stock kernal, and also the modem just to be safe and nothing would fix it. From what I know its just a hardware issue, not software. I was chatting with samsung and t-mobile people about this trying all kinds of fixes to nothing left but hardware defect.

Related

[Q] Trouble with network connectivity probably caused by EFS???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
artorelis said:
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ya, I was asking this question on the Omega forum and I am waiting for the right response.
Sent from my GT-N7100 using xda premium
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
joshphilips said:
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I did downgrade from v17 back to 16 since something went wrong with Poweramp but I forgot that if I selected for the efs backup or not since I (stupidly) didn't think that efs is important...:banghead:
Sent from my GT-N7100 using xda premium
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
Click to expand...
Click to collapse
Thanks for replying, I should have a backup, but it probably be the wrong one. Anyway I will go for a full stock restore since I have the firmware with me now.
Sent from my GT-N7100 using xda premium
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
Good luck.
Click to expand...
Click to collapse
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Dan Law 001 said:
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Click to expand...
Click to collapse
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
muppetmania said:
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
Click to expand...
Click to collapse
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Dan Law 001 said:
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Click to expand...
Click to collapse
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
muppetmania said:
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
Click to expand...
Click to collapse
Thanks for information, but how do I know that if the EFS is "totally" corrupt, "partially" corrupt, or not corrupt at all? In fact, I never touch the EFS in the root. Also, as I am not quite sure that if I have any previous EFS(S) backup or not, so, if possible, where does the backup(s) most likely to be found?
If you haven't taken an EFS backup yourself, then you won't have any.
I don't know the difference between corruption levels either, all I know is I've read a number of forum posts where someone has reflashed stock and their EFS data (i.e. the right IMEI number) is back. So I'd consider that to be a partial corruption. Others have flashed back to stock and it's still a bogus IMEI
Basically, flash back to stock. If it doesn't work, you'll have to take it in for repair.
UPDATE: Please read on - this information is incorrect - it is possible to recover with the correct modem flashed.
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
NOTE: The information from me in this post below is wrong
Dan Law 001 said:
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
Click to expand...
Click to collapse
It's normal your device got unrooted, yes. If your IMEI is still the same after ODIN and stock flash, then you have major issues (sorry!)
Doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What IMEI does *#06# show?
muppetmania said:
it's normal your device got unrooted, yes. If your imei is still the same after odin and stock flash, then you have major issues (sorry!)
doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What imei does *#06# show?
Click to expand...
Click to collapse
004999010640000 / 01
Dan Law 001 said:
004999010640000 / 01
Click to expand...
Click to collapse
Type 004999010640000 into Google...
Sorry man. Good luck getting it fixed.
just flash ME4 modem everything will be alright
bhasg1007 said:
just flash ME4 modem everything will be alright
Click to expand...
Click to collapse
Interesting to know - why does that work? (I don't doubt you, I just like to know why things work)
Just go through this thread http://forum.xda-developers.com/showthread.php?t=2333216
Even i had the same problem no network no imei nothing after downgrading so i just changed the modem and now everything is fine as it should be

[Q] EMEI number changed. how to restore it?

Hi,
I bought second hand a Galaxy Note II. everything works fine except it can´t connect to any provider. I checked the EMEI and it is not the one in the back label.
I searched in Lost or Stolen phones database and this altered EMEI showed up as belonging to an Apple iPhone stolen in Kenya. The search of the legal EMEI in the back label showed no results so I suppose if I can restore the correct EMEI, it should work.
Why the former owner changed a working EMEI to a not working one is beyond my understanding. The phone seems to have the legal not altered firmware or so it says when you enter download mode. May be he attempted to unlock the phone but instead of that he ended up replacing the EMEI information and blocked the phone.
I bought the phone from a trusted seller in ebay who sells stock returns, shop liquidations, etc. I trust them but they don't know the history of the phone before they received it.
jedikalimero said:
Hi,
I bought second hand a Galaxy Note II. everything works fine except it can´t connect to any provider. I checked the EMEI and it is not the one in the back label.
I searched in Lost or Stolen phones database and this altered EMEI showed up as belonging to an Apple iPhone stolen in Kenya. The search of the legal EMEI in the back label showed no results so I suppose if I can restore the correct EMEI, it should work.
Why the former owner changed a working EMEI to a not working one is beyond my understanding. The phone seems to have the legal not altered firmware or so it says when you enter download mode. May be he attempted to unlock the phone but instead of that he ended up replacing the EMEI information and blocked the phone.
I bought the phone from a trusted seller in ebay who sells stock returns, shop liquidations, etc. I trust them but they don't know the history of the phone before they received it.
Click to expand...
Click to collapse
Did your imei change to 004999010640000? this is a common problem happening to lots of people when they flashed the newest firmware and then an older, if thats the case; you should try to flash the original firmware(Sammobile), or look if somewhere in the memory of the phone a file called efs backup is found. Otherwise you're having a big problem.
Armazia said:
Did your imei change to 004999010640000? this is a common problem happening to lots of people when they flashed the newest firmware and then an older, if thats the case; you should try to flash the original firmware(Sammobile), or look if somewhere in the memory of the phone a file called efs backup is found. Otherwise you're having a big problem.
Click to expand...
Click to collapse
Yes, that's exactly the EMEI number!
no efs backup file found.
I will try flashing stock BTU firmware from Sammobile but can this restore the EMEI?
jedikalimero said:
Yes, that's exactly the EMEI number!
no efs backup file found.
I will try flashing stock BTU firmware from Sammobile but can this restore the EMEI?
Click to expand...
Click to collapse
You can try, I heared rumor that it saved some of their phone. If that doesn't work there won't be any way you'll get your original imei back for free, so you'll possibly need to contact Samsung. Try to install the latest firmware of samsung(MG1 I guess).
Armazia said:
You can try, I heared rumor that it saved some of their phone. If that doesn't work there won't be any way you'll get your original imei back for free, so you'll possibly need to contact Samsung. Try to install the latest firmware of samsung(MG1 I guess).
Click to expand...
Click to collapse
I found this thread:
http://forum.xda-developers.com/showthread.php?p=44346301#post44346301
I have downloaded the mentioned ZIP file but I don't know how to flash it.
jedikalimero said:
I found this thread:
http://forum.xda-developers.com/showthread.php?p=44346301#post44346301
I have downloaded the mentioned ZIP file but I don't know how to flash it.
Click to expand...
Click to collapse
Well just go through the original dev thread and search fr dr.ketan thread on how to root etc u will find answer to evrytying u want to know abt the device
Hello All,
I'm having the same problem, no Imei and no phone signal
I have a efs.tar.gz backup file but I don't know how to restore it.
I saw methods to restore .bin files but not tar.gz
Can someone help me with that?
Thanks in advanced :good:
Use this
http://forum.xda-developers.com/showthread.php?t=1918601
Worked for me
Sent from my GT-N7100 using xda app-developers app
Techno848 said:
Use this
http://forum.xda-developers.com/showthread.php?t=1918601
Worked for me
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
The OP says this won't work in my case:
Q: My imei number like 0000**** or 0049**** if i flash this patch it will work or it will bring my original imei number back ?
A: This patch is not about your EFS Folder it is just about network so it won't fix your imei number or bring your original imei number back.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1518694

[Q] No IMEI means radio is broken?

Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
samdev09 said:
Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
Click to expand...
Click to collapse
If you have a nandroid back up, try and restore with it. This could solve ur problem.
saishyamk said:
If you have a nandroid back up, try and restore with it. This could solve ur problem.
Click to expand...
Click to collapse
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
samdev09 said:
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
Click to expand...
Click to collapse
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
saishyamk said:
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
Click to expand...
Click to collapse
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
samdev09 said:
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
Click to expand...
Click to collapse
I'm not sure how to check if your radio is fried. Basically, it means something's wrong with your hardware, where you experience occasional or complete signal loss. But in your case, you lost your IMEI. So, back up your nv_data files, flash using NRT or ODIN and see what happens.
NRT will push the stock radio while doing the "Flash Stock + Unroot" Option. So, you'll get the stock baseband as well. This should fix it. If your IMEI still doesn't work, try restoring the nv_data.bin and md5 files you backed up as mentioned in the link I posted.
Let me know how it works out. :good:
Always make a backup of /EFS (Support in both PhilZ_CWM & TWRP )for safety, though the IMEI would be only wiped by CWM wipe /factory option......happened to me a few days back, luckily i got my /efs restored & flashing stock doesn't bring any IMEI back since it's actually phone specific plus comes with a proper MD5 !!
the above method should work and here more info on the EFS

T-mobile S4 Stock Android 4.3, Cannot Unlock, IMEI unknown after attempt by localshop

Hi All,
I had purchased T-Mobile Samsung Galaxy S4 (SGH-M919) with Stock android 4.3 while I was in usa, and want to use it in my home country now as I have left usa. I couldn't found any unlock solution on internet for stock android 4.3, and T-Mobile would not give me the unlock code. I tried third party services to provide unlock code and it did not work either. So I went to a local shop, and he screwed everything up. When I went back to the local shop to receive my phone (hoping it might have been definitely unlocked by them), he told me that he tried to downgrade it to 4.2.2 but it did not work (only after reading through all the forums I realize there is no way to go back to stock 4.2.2 if you are on stock 4.3 because of knox / bootloader issues on 4.3, leads me to think the shopowner did not really do his research before touching my phone, and no, he did not do any EFS backup). In an attempt to unlock my phone, he also flashed Metro PCS stock ROM on my phone, not to mention, my IMEI number is also 'Unknown' now. I managed to get back on T-Mobile stock 4.3 ROM now but still IMEI is unknown. I also tried to go to nearest Samsung center and they said they would not touch international phone models. At this point I have no idea what to do. Any suggestions how to get back my IMEI and or at the least to get the phone working to my country's network?
Thanks.
Try flashing the mk2 modem using odin. That may work but not sure.
Sent from my SGH-M919 using Tapatalk
Shop just need to pay you for new phone.
☞ Sent from here☜???
I won't provide a link but there are ways to restore your imei and as for unlocking I have used fast gsm dot com and it has worked every time. I hope u get ur issues fixed. Good luck
Sent from my SGH-M919 using Tapatalk
sd_N said:
I won't provide a link but there are ways to restore your imei and as for unlocking I have used fast gsm dot com and it has worked every time. I hope u get ur issues fixed. Good luck
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Hi sd_N, is it possible for you to provide me the link in private so I can just restore my original imei. I will then try fastgsm.com to unlock as you suggested. Thanks.
Anyone?
galaxysiv said:
Anyone?
Click to expand...
Click to collapse
Did you ever make any nandroid backups through recovery or save your /efs?
xdapowerapps said:
Did you ever make any nandroid backups through recovery or save your /efs?
Click to expand...
Click to collapse
Hi xdapowerapps, no I did not, I didnt knew the local shop would try to downgrade or flash METRO PCS rom on it :crying:
galaxysiv said:
Hi xdapowerapps, no I did not, I didnt knew the local shop would try to downgrade or flash METRO PCS rom on it :crying:
Click to expand...
Click to collapse
The local shop broke it. Tell them to pay for it.
Also, the only reason T Mobile won't give you an unlock code is if the phone isn't paid for in full. If the phone is paid for in full, they HAVE to give you the unlock code.
Are you sure you didn't buy the phone in the US, then leave the country without paying the bill so you could use the phone internationally without paying full price? If not, there is no reason T Mobile wouldn't give you the unlock code. So there's some missing information in this story.
Also, we do not discuss how to change IMEI's on XDA. The only thing permissable on XDA about flashing IMEI's is restoring YOUR OWN IMEI from a backup. That is done by restoring the EFS partition. But you didn't have a back up so you can't do that. That means anyway to fix your IMEI involves what is an illegal hack and that discussion is expressly not permitted on XDA. That information is used for illegal purposes and XDA is not going to be the place where it's shared for legal reasons.
Skipjacks said:
The local shop broke it. Tell them to pay for it.
Also, the only reason T Mobile won't give you an unlock code is if the phone isn't paid for in full. If the phone is paid for in full, they HAVE to give you the unlock code.
Are you sure you didn't buy the phone in the US, then leave the country without paying the bill so you could use the phone internationally without paying full price? If not, there is no reason T Mobile wouldn't give you the unlock code. So there's some missing information in this story.
Also, we do not discuss how to change IMEI's on XDA. The only thing permissable on XDA about flashing IMEI's is restoring YOUR OWN IMEI from a backup. That is done by restoring the EFS partition. But you didn't have a back up so you can't do that. That means anyway to fix your IMEI involves what is an illegal hack and that discussion is expressly not permitted on XDA. That information is used for illegal purposes and XDA is not going to be the place where it's shared for I also still see the imei folder inside EFS with a file mps_code.bat, but no nv files. (The imei folder was not regenerated on deletion either) Am I missing something? also still see the imei folder inside EFS with a file mps_code.bat, but no nv files. (The imei folder was not regenerated on deletion either) Am I missing something? egal reasons.
Click to expand...
Click to collapse
Hi skipjacks, thanks for responding. Nothing is pending with t-mobile, I was on prepaid account. I bought the phone like 10 days before leaving usa (due to emergency). T-mobile says my number on this new device should have being working for at least 45 days or so with refill balance. My cycle ended after 15 days of purchase and I really didnt see any reason to refill it as I was no more in usa. And no, I dont want to CHANGE my IMEI, only want to restore my own IMEI only. I am not sure if my EFS partition is corrupted, because I rooted my phone tried to backup EFS folder now (I know its too late but still), deleted it and rebooted (as a few threads suggested it would regenerate nv data files), but neither did I see any nv files when I did a back up now, nor after I rebooted. When I rebooted, the EFS folder did regenerate but there were no nv files in there. Also, after deleting EFS and regeneration the serial number was corrupted, but when I restored my backup, the serial number showed up correctly again. Also my current backup contains the imei folder with mps.code_bat file. I noticed that even imei folder was not regenerated on deletion of EFS and reboot. I somehow have the feeling that this is still indicating that my original EFS folder is still present (though I may be wrong, because I dont know). But my concern is the nv data files, which I dont see anywhere. I did come across several threads about imei corruption and restoration, but the only one I didnt come across was T-mobile SGH-M919 with stock android 4.3. I am wondering if this has some different file storage structure for imei (which again I dont know). At this point I am concerned about getting back my imei, I can get the unlock code from some reputed paid service again. I understand that open discussion about imei involving anything CHANGING IMEI is not allowed here. If anyone could just help me out restoring my original imei, even by pm, I would really appreciate it. I just dont want to throw away the phone and lose my money because of the error done by repair shop.
galaxysiv said:
Hi skipjacks, thanks for responding. Nothing is pending with t-mobile, I was on prepaid account. I bought the phone like 10 days before leaving usa (due to emergency). T-mobile says my number on this new device should have being working for at least 45 days or so with refill balance. My cycle ended after 15 days of purchase and I really didnt see any reason to refill it as I was no more in usa. And no, I dont want to CHANGE my IMEI, only want to restore my own IMEI only. I am not sure if my EFS partition is corrupted, because I rooted my phone tried to backup EFS folder now (I know its too late but still), deleted it and rebooted (as a few threads suggested it would regenerate nv data files), but neither did I see any nv files when I did a back up now, nor after I rebooted. When I rebooted, the EFS folder did regenerate but there were no nv files in there. Also, after deleting EFS and regeneration the serial number was corrupted, but when I restored my backup, the serial number showed up correctly again. Also my current backup contains the imei folder with mps.code_bat file. I noticed that even imei folder was not regenerated on deletion of EFS and reboot. I somehow have the feeling that this is still indicating that my original EFS folder is still present (though I may be wrong, because I dont know). But my concern is the nv data files, which I dont see anywhere. I did come across several threads about imei corruption and restoration, but the only one I didnt come across was T-mobile SGH-M919 with stock android 4.3. I am wondering if this has some different file storage structure for imei (which again I dont know). At this point I am concerned about getting back my imei, I can get the unlock code from some reputed paid service again. I understand that open discussion about imei involving anything CHANGING IMEI is not allowed here. If anyone could just help me out restoring my original imei, even by pm, I would really appreciate it. I just dont want to throw away the phone and lose my money because of the error done by repair shop.
Click to expand...
Click to collapse
First off....the enter key is your friend. Hit it every so often when typing giant blocks of text like that. :laugh:
Second, since your IMEI has been deleted, you now have to change it, even if you just want to change it back to what it was before. The process to fix it now is what can't be discussed here.
IF you had backed up your EFS partition, then it would be as simple as restoring it in recovery. That's all well and good. But your IMEI is now 0, so you have to change it to what it was.
But all that aside, you went to a store and they broke it. Take it back there and raise holy hell until they fix it for you or buy you a new one. I know consumer protections are stronger in some countries than others, but wherever you are, yelling and screaming is a universal language.
Skipjacks said:
First off....the enter key is your friend. Hit it every so often when typing giant blocks of text like that. :laugh:
yelling and screaming is a universal language.
Click to expand...
Click to collapse
You
learn
new
things
every
day. :silly:
Can someone at least tell me what file in T-Mobile Galaxy S4 SGH-M919 Stock Android 4.3 contains imei number, so at least I know if I even have that file or not or whether it is missing? Thanks.
galaxysiv said:
Can someone at least tell me what file in T-Mobile Galaxy S4 SGH-M919 Stock Android 4.3 contains imei number, so at least I know if I even have that file or not or whether it is missing? Thanks.
Click to expand...
Click to collapse
Whether your file is missing, modified, or corrupted, you need your /efs folder to restore it. You do not have have a nandroid backup or the /efs folder. I am sorry but the simplest we can put it without sounding harsh, you're screwed. You need to request the local shop give you a replacement phone or credit to get a new one.
Update: I went back to the shop and told them "You broke it, you fix it, I don't know how and I don't care, you gotta fix it". They managed to fix the imei number somehow. Regarding unlock, the shop ended buying the unlock code themselves. They mentioned that no one is able to unlock T-Mobile S4 with Stock 4.3 as of now without unlock code, unless they have some device like Z3x box. The phone is finally unlocked and working fine on my network. (YES, A HUGE HUGE RELIEF).
Everything is fine, except for 2 issues.
1. I want to backup my EFS folder so that I don't enter into trouble with IMEI again. I tried EFS Pro, but its not working. All I see is "'Initializing ADB server..." (the phone is rooted, usb debugging mode enabled, and supersu permission granted when prompted). I also tried to backup using Andromizer, but it says "Notification: File not found in /storage/emulated/0/Amdromizer/efs/efs.img". What is my best option as of now to backup and store my imei safely somewhere?
2. I am having issues with Wi-Fi. Before the shop flashed my phone, it was all good, but now it doesn't auto-connect to my home Wi-Fi anymore. Everytime I reboot or get out of range, I have to manually select my home network everytime and also enter the password everytime. Nothing has changed on my router. The other Samsung device that I have still auto-connects to my home Wi-Fi as usual. How can I fix this?
Thanks.
galaxysiv said:
Update: I went back to the shop and told them "You broke it, you fix it, I don't know how and I don't care, you gotta fix it". They managed to fix the imei number somehow. Regarding unlock, the shop ended buying the unlock code themselves. They mentioned that no one is able to unlock T-Mobile S4 with Stock 4.3 as of now without unlock code, unless they have some device like Z3x box. The phone is finally unlocked and working fine on my network. (YES, A HUGE HUGE RELIEF).
Everything is fine, except for 2 issues.
1. I want to backup my EFS folder so that I don't enter into trouble with IMEI again. I tried EFS Pro, but its not working. All I see is "'Initializing ADB server..." (the phone is rooted, usb debugging mode enabled, and supersu permission granted when prompted). I also tried to backup using Andromizer, but it says "Notification: File not found in /storage/emulated/0/Amdromizer/efs/efs.img". What is my best option as of now to backup and store my imei safely somewhere?
2. I am having issues with Wi-Fi. Before the shop flashed my phone, it was all good, but now it doesn't auto-connect to my home Wi-Fi anymore. Everytime I reboot or get out of range, I have to manually select my home network everytime and also enter the password everytime. Nothing has changed on my router. The other Samsung device that I have still auto-connects to my home Wi-Fi as usual. How can I fix this?
Thanks.
Click to expand...
Click to collapse
For the efs you can back it up using recovery. Just boot to recovery and its one of the options in the backup menu. The resulting file will be like a few KB. Its supposed to be small. Dont worry
Sent from your phone. You should be more careful where you leave that thing.
Tmobile gave me an unlock code and my phone isn't paid for but I used the region lock away app before I got the unlock code and it worked but u got to be rooted
Sent from my SGH-M919 using xda app-developers app

[Q] Generic IMEI after OTA 4.3 upgrade

Hello to everyone, I was wondering if anyone can help with this. I have a Galaxy Note 2 branded by an Italian company (3hg Italia). It recently received its update to Android 4.3 (update N7100XXUEML2). It was the official update OTA, the phone is not rooted and it had the stock ROM on it. The update somehow messed up my IMEI making it appear as the generic 0049 forcing me on "Emergency calls only" mode. I already tried flashing the same ROM with Odin and repeating the update with KIES, but while the updates always results successful the IMEI remains 0049. I never made a backup of the EFS folder for this phone since I haven't rooted it or flashed any different ROM on it yet. There is any chance that the phone made an automatic backup? I live in the States right now and Samsung tells me I need to ship it back to Italy to have it fixed, but that costs a lot and would take forever, and I would much prefer try to solve the problem locally. Any suggestions would be greatly appreciated, if not for any fix that I can try myself, at least some place on the West Coast that can fix the problem!
Thank you!
Lorenzo
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
rext said:
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
Click to expand...
Click to collapse
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
phluid01 said:
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
Click to expand...
Click to collapse
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
rext said:
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
Click to expand...
Click to collapse
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
phluid01 said:
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
Click to expand...
Click to collapse
Thank you so much! I'll take a look into it tomorrow and try it!
rext said:
Thank you so much! I'll take a look into it tomorrow and try it!
Click to expand...
Click to collapse
So I found someone nice enough to give me a hand with this situation, but still no luck yet! Here what they say:
At first glance, the EFS data on the phone was corrupt. I re-generated
that data and restored it to the phone without success.
The GSM radio itself is operational, and the firmware for it is
installed and functional. diagnostic data flows to the towers and back
to the phone but it's not reading the IMEI from the copy of
nv_data.bin contained within EFS. I've re-generated and installed
those files as well, again with no luck.
I rolled the device back to it's original factory firmware and radio
baseband, then ran through the update for the radio baseband, which
also regenerates the contents of EFS, and still no luck.
Given the situation, anyone have other suggestions?

Categories

Resources