Alright, so I paid cellunlocker to unlock a new to me Note 3. Not blacklisted, everythings good on that end.
my IMEI shows as the correct number with two extra digits - not sure if thats my issue.
However I cannot connect to any mobile network. Well thats not true, I can see I'm connected to their tower but cannot get any phone calls, texts I just get the message on the screen.
I didn't back up my EFS partition, having 6 android phones so far all, rommed, and everything I never had to do that.
I understand its likely that this partition is messed up.
.. So how can I restore it?
I'm rooted, I'll install a recovery I don't mind any of that. however I do not have a backup of my EFS partition. Is there any way to extract this from a stock file?
Can I just use Kies or something to flash the entire software and restore this partition?
Seeking some guidance from the Note Experts.
Thanks,
KeirP said:
Alright, so I paid cellunlocker to unlock a new to me Note 3. Not blacklisted, everythings good on that end.
my IMEI shows as the correct number with two extra digits - not sure if thats my issue.
However I cannot connect to any mobile network. Well thats not true, I can see I'm connected to their tower but cannot get any phone calls, texts I just get the message on the screen.
I didn't back up my EFS partition, having 6 android phones so far all, rommed, and everything I never had to do that.
I understand its likely that this partition is messed up.
.. So how can I restore it?
I'm rooted, I'll install a recovery I don't mind any of that. however I do not have a backup of my EFS partition. Is there any way to extract this from a stock file?
Can I just use Kies or something to flash the entire software and restore this partition?
Seeking some guidance from the Note Experts.
Thanks,
Click to expand...
Click to collapse
- The extra 2 digits after the IMEI is the IMEISV. It is not the issue.
- The EFS partition is store inside your device, not in the stock firmware. Of course you can not extract it from the stock files.
- You can try to flash the entire stock firmware (using Kies or Odin). Sometime that may help to fix the problem.
Appears to be a case of delayed blacklist or something.
Didn't show up in any searches and not to my carrier, yet later now it does appear it is.
Now to return it to the carrier so they can get it back to the owner, and to track down the ass I bought it from.
Related
hii all
i had a problem with my galaxy s i9000. about 2 weeks ago when i turn my phone on i got no service, the flight mode allways on and i can't turn it off, the imei and baseband and phone number and many things in the about phone in the system sytings are unknown i try to check my sim card on another phone it work with no problem, and i try to root it and changing the room by odion with repartion but nothing happend, then today i take it to the service to solve my problem they tell me that they must change the system but it solve it or it may get black screen of death and they can't get it back.
please help me to solve the problem and sorry about my bad language
thanks...
don't worry about the black screen of death, it can be fixed
just out of curiocity, what happens when you disable flight mode?
allotrios said:
don't worry about the black screen of death, it can be fixed
just out of curiocity, what happens when you disable flight mode?
Click to expand...
Click to collapse
thanks for your reply
is it realy that i can solve the black screen of death myself !!!
the answer for the question is that when i go to system then wireless sitings when i try to turn the flight mode off it takes a long time and nothing happend and when i go back and enter the wireless sytings again it goes on
Kabooot said:
thanks for your reply
is it realy that i can solve the black screen of death myself !!!
the answer for the question is that when i go to system then wireless sitings when i try to turn the flight mode off it takes a long time and nothing happend and when i go back and enter the wireless sytings again it goes on
Click to expand...
Click to collapse
Unless the hardware is broken you can always reflash the phone, even if 3 button download mode is not working.
Does the phone give you the option to search for networks? I had the problem you describe whenever I was going roaming and I would come off the flight safe mode. The phone would not connect to the network until I restarted it.
allotrios said:
Unless the hardware is broken you can always reflash the phone, even if 3 button download mode is not working.
Does the phone give you the option to search for networks? I had the problem you describe whenever I was going roaming and I would come off the flight safe mode. The phone would not connect to the network until I restarted it.
Click to expand...
Click to collapse
the 3 botton are working on my phone
i don't understand you what do you mean by "Does the phone give you the option to search for networks?" but the wifi work perfect on my phone
if you type *#06# does the imei show ok? if not it could be a corrupt nvdata.bin file. If you delete nvdata.bin and nvdata.md5 file it will reload them from the nvdata.bak files but do this only as a last resort.
Edit: Back them up first mind.
I'd just reflash if I were you, you can use it as an opportunity to load a newer firmware if you're not already using a new one, JPM is working great for me. I'd advise using Titanium to backup your contacts, accounts, wifi access points, launcher layout, etc, etc, first though. You should be able to restore the entire look and feel of your phone then, not to mention all the app data, etc.
n1kon said:
if you type *#06# does the imei show ok? if not it could be a corrupt nvdata.bin file. If you delete nvdata.bin and nvdata.md5 file it will reload them from the nvdata.bak files but do this only as a last resort.
Edit: Back them up first mind.
Click to expand...
Click to collapse
when i type *#06# the imei dosn't desplay for me
how can i get the nvdata back??
phynios said:
I'd just reflash if I were you, you can use it as an opportunity to load a newer firmware if you're not already using a new one, JPM is working great for me. I'd advise using Titanium to backup your contacts, accounts, wifi access points, launcher layout, etc, etc, first though. You should be able to restore the entire look and feel of your phone then, not to mention all the app data, etc.
Click to expand...
Click to collapse
thank you for your reply
but I had flashed it many times but nothing happen
give me the site to the JPM room
Is there any one who got the solve??
Kabooot said:
Is there any one who got the solve??
Click to expand...
Click to collapse
This very same thing happened to me as well. This is because your IMEI is gone or is invalid.
Networks detects your IMEI so when you don't have one, they won't give you permission to their signal.
I didn't backed up my EFS folder before this happened.
Luckily, SGS Toolbox did make a back-up of my nvdata.bin when I checked for my product code before I screwed up my IMEI and I just replaced the corrupted EFS folder files with whatever SGS toolbox backed up to fix the issue (whew!)
I don't think you can fix this on your own unless you backed up your EFS folder before having this issue.
Try to follow the other user's suggestiong to delete the two files and reboot ]but ENSURE that you back up your EFS folder. I suggest creating 2 back up files. 1 in your PC and 1 in your phone's SD.
Note: Flashing will not solve this. Since ODIN does not touch your IMEI. If its' invalid, it will stay invalid regardless of how many flash you make.
android.francis said:
This very same thing happened to me as well. This is because your IMEI is gone or is invalid.
Networks detects your IMEI so when you don't have one, they won't give you permission to their signal.
I didn't backed up my EFS folder before this happened.
Luckily, SGS Toolbox did make a back-up of my nvdata.bin when I checked for my product code before I screwed up my IMEI and I just replaced the corrupted EFS folder files with whatever SGS toolbox backed up to fix the issue (whew!)
I don't think you can fix this on your own unless you backed up your EFS folder before having this issue.
Try to follow the other user's suggestiong to delete the two files and reboot ]but ENSURE that you back up your EFS folder. I suggest creating 2 back up files. 1 in your PC and 1 in your phone's SD.
Note: Flashing will not solve this. Since ODIN does not touch your IMEI. If its' invalid, it will stay invalid regardless of how many flash you make.
Click to expand...
Click to collapse
thank you very much for your help
but i don't understand you very much, did you mean that my problem won't solve or it can be solved??
how can i get the EFS folder back i didn't made a backup for my phone.so what can i do to repare my phone please help me
for more information about my problem is that some time when i try to change some sitings on sgs tools i get my imei back and the baseband but the service won't get back and the flight mode allways on
today i called samsung repair in my country (kuwait) they told me that it's a motherboard problem they must change it with 300dolar is this real or it's a frameware problem?
because i don't want to pay 300 to change tha motherboard
if any one has an idea please help me
Kabooot said:
today i called samsung repair in my country (kuwait) they told me that it's a motherboard problem they must change it with 300dolar is this real or it's a frameware problem?
because i don't want to pay 300 to change tha motherboard
if any one has an idea please help me
Click to expand...
Click to collapse
Hold on, a Galaxy S must be within it's warranty period, it's a recent product. If you have a faulty product, it's Samsung's responsibility to honour their parts warranty. I would have gone mad if Samsung had asked me for $300 for something that is their responsibility. Call them again and request a repair under warranty.
phynios said:
Hold on, a Galaxy S must be within it's warranty period, it's a recent product. If you have a faulty product, it's Samsung's responsibility to honour their parts warranty. I would have gone mad if Samsung had asked me for $300 for something that is their responsibility. Call them again and request a repair under warranty.
Click to expand...
Click to collapse
i don't buy it from my country i bought it from ebay it's an orange version i don't have a warranty on my country i must send it back to where i buy from soo i have a warranty there
Is it a motherboard problem??
I lost efs together with imei last week when I tried to flash a different modem. Running out of options I sent the phone to a repairer.
Today, after one week, I picked it up from them and they somehow got the imei back and the phone is working while I was still at their office.
Now I'm home and tried to connect it to my home's wifi, as soon as it connects, the phone reboots. It's very stable on mobile data though.
I cleared data, flashed different roms, but wifi connection always reboots it.
Then I looked in the efs folder and surprise, it's empty!!! I don't know whether that's the cause of the wifi problem, but isn't it odd that the phone runs ok otherwise without efs?
Anybody has any idea of what's happening to my phone? Can my wifi problem be fixed?
I do actually have an efs backup that I've done back in January. But I just can't remember what tool I used to make that file. The file name is "efs.img". Any suggestion at all?
ioneng said:
I do actually have an efs backup that I've done back in January. But I just can't remember what tool I used to make that file. The file name is "efs.img". Any suggestion at all?
Click to expand...
Click to collapse
Use IMEI Tool N9005 Free 1.1
I bought a rooted G2 from ebay. My IMEI is 0 (Setting>About Phone>Status). I suppose it got lost during rooting. Is there a way to restore it?
1. The sticker on the battery cover still has IMEI number. Can I somehow write it back?
2. The phone has clockworkmod directory and has .recovery_version file in it. Can this be used somehow for the restoration purpose?
3. Android 4.4.2, kernel 3.4.0, software version D80020c, Build KOT49I.C80020c, Baseband version M8974A-AAAANAZM-1.0.190082. Is this LG ROM?
4. I am still connected to network somehow.
Thanks.
palmgrower said:
I bought a rooted G2 from ebay. My IMEI is 0 (Setting>About Phone>Status). I suppose it got lost during rooting. Is there a way to restore it?
1. The sticker on the battery cover still has IMEI number. Can I somehow write it back?
2. The phone has clockworkmod directory and has .recovery_version file in it. Can this be used somehow for the restoration purpose?
3. Android 4.4.2, kernel 3.4.0, software version D80020c, Build KOT49I.C80020c, Baseband version M8974A-AAAANAZM-1.0.190082. Is this LG ROM?
4. I am still connected to network somehow.
Thanks.
Click to expand...
Click to collapse
Usualy to fix this you need to have an efs backup of your imei but you probably don't as from what I understand, you recieved the phone without the imei.
try to go back to completely stock: http://forum.xda-developers.com/showthread.php?t=2432476
if you manage to get back your imei that way, you'll easily be able to root your phone again and this time around make if the imei shows up, you can make an efs backup so that if it ever happens again you can always restore your imei through the efs backup. (you can google how to make an efs backup.)
but start of by going back to stock and let us know if it worked.
Arju007 said:
Usualy to fix this you need to have an efs backup of your imei but you probably don't as from what I understand, you recieved the phone without the imei.
try to go back to completely stock: http://forum.xda-developers.com/showthread.php?t=2432476
if you manage to get back your imei that way, you'll easily be able to root your phone again and this time around make if the imei shows up, you can make an efs backup so that if it ever happens again you can always restore your imei through the efs backup. (you can google how to make an efs backup.)
but start of by going back to stock and let us know if it worked.
Click to expand...
Click to collapse
I read the linked procedure. It is a very scary-looking one. Honestly speaking, I am afraid of screwing the phone up majorly. (All my pc's are ubuntu (linux) except a Vista laptop)
The phone is working, 4G LTE data, voice, texting, one app from google play. What is the likelihood of losing these all of a sudden because IMEI=0? Would you still recommend to get IMEI straight in the first place?
Thanks.
PS: I just talked to Cricket Wireless, my service provider. According to the rep, I will not lose connection all of a sudden just because my IMEI is 0. Can I trust this semi-technical person?
palmgrower said:
I read the linked procedure. It is a very scary-looking one. Honestly speaking, I am afraid of screwing the phone up majorly. (All my pc's are ubuntu (linux) except a Vista laptop)
The phone is working, 4G LTE data, voice, texting, one app from google play. What is the likelihood of losing these all of a sudden because IMEI=0? Would you still recommend to get IMEI straight in the first place?
Thanks.
PS: I just talked to Cricket Wireless, my service provider. According to the rep, I will not lose connection all of a sudden just because my IMEI is 0. Can I trust this semi-technical person?
Click to expand...
Click to collapse
That's your call. If everything works and you're satisfied, then let it be. That was the only solution I could come to think of. By following the tutorial to the dot, you can't go wrong. But if you're uncomfortable, I'll say let it be.
I bought the N910F a few weeks ago. I'm traveling so I had it unlocked in Bangkok to use other Sim cards. That's when my problems began.
They rooted the phone and changed my IMEI number. The result is: Knox flag tripped, fingerprint sensor not working anymore (error), losing WiFi passwords (had to do ro.securestorage.support=false to fix it) and worst of all lag and bad battery life. I can't even watch a HD movie without lag. AnTuTu score 36000.
The efs folder is empty (not mounted). I have no backup of the folder. The phone functionality works fine. I got no problems with any Sim card. I have a valid imei, just the wrong one. I tried firmware installation and initialization with Kies, but it didn't change anything.
I'm traveling through Asia for many months so I can not get a replacement or send it in for repair at home in Europe.
Do you have an idea how I could get my original imei back? or how to mitigate the issues?
I had a very similar problem, I thought I was sunk. But then I found THIS post, I used the Edit 2 method and it worked a treat, hope you have similar luck. If you don't have TWRP, then I'd recommend you install it, can be a real lifesaver.
thanks for the link. it worked partially. I managed to mount the efs folder. the partition for n910f is mmcblk0p13! I used the terminal emulator on my rooted phone with busybox. no need to use recovery.
the bad thing thing is, I still don't have my original imei. the good thing is, my fingerprint sensor works again, I don't need the Wi-Fi fix with ro.securestorage. support=false and the phone feels much faster, less laggy now.
kinda happy with that. If I had the efs backup now....
would a initialization with Kies restore my original imei?
Sorry, I really can't say, I've never used Kies. Glad it seems to be running better now.
Should have mentioned the partition on a N910 is /dev/block/mmcblk0p13, getting old and forgetful, LOL.
That's a bummer OP - a non-factory unlock on newer Samsung phones involves writing another phone's hacked EFS data.
If the store didn't do a backup of your old modem data, your original IMEI is gone.
DO NOT attempt to use Qualcomm NV Tools to change your IMEI back to stock. (Guess how I wrecked my Note 3 the first time around!) - you need a valid IMEI Certificate to access 3G/LTE networks so you'll be stuck in 2G mode.
Samsung service centers have the tools to write any IMEI they want and generate the valid certificate, though it'll be expensive. I'd just advise OP to Odin to stock and wipe data, then root and disable ro.securestorage.support.
Having a wrong IMEI's not too bad, although a big no-no in terms of the GSM standard.
1) I think I have a valid certificate for my 'new' imei. Mobile data connections work fine and fast (H+). I prefer my original imei though.
2)why should I disable securestorage.support? It works fine enabled.
gattacus said:
1) I think I have a valid certificate for my 'new' imei. Mobile data connections work fine and fast (H+). I prefer my original imei though.
2)why should I disable securestorage.support? It works fine enabled.
Click to expand...
Click to collapse
As part of the unlocking process, they wrote a new (rather, copied from another phone) IMEI to your Note 4. It'll work just fine. However, the IMEI may be shared with other phones, and may one day be blacklisted. When/If that happens, you'll need to write a new IMEI again.
I think I didn't come across right the last time - don't try to change your IMEI to your original one with Qualcomm NV Tools without a matching, proper certificate for it. It's a world of hurt.
As for ro.securestorage.support, it _might_ be needed for keeping WiFi passwords saved on reboot. Or not. IIRC, my rooted Note 3 needed it set for WiFi and S-Health to work right. I'm staying unrooted on my Note 4, so I don't know if you'll still have to do that.
I will go to a service center and ask if they can restore my imei but it doesn't seem to be urgent now. I just hope that a kies install of lollipop doesn't bring back the problems (unmounted efs).
WiFi passwords survive a reboot without the fix. So far so good.
Thanks for your help.
rastus.rob said:
I had a very similar problem, I thought I was sunk. But then I found THIS post, I used the Edit 2 method and it worked a treat, hope you have similar luck. If you don't have TWRP, then I'd recommend you install it, can be a real lifesaver.
Click to expand...
Click to collapse
Your post helped me a lot. I just wanted to say that you made my day. THANK YOU!!!!!
you can use darkmed repair tools
gattacus said:
I bought the N910F a few weeks ago. I'm traveling so I had it unlocked in Bangkok to use other Sim cards. That's when my problems began.
They rooted the phone and changed my IMEI number. The result is: Knox flag tripped, fingerprint sensor not working anymore (error), losing WiFi passwords (had to do ro.securestorage.support=false to fix it) and worst of all lag and bad battery life. I can't even watch a HD movie without lag. AnTuTu score 36000.
The efs folder is empty (not mounted). I have no backup of the folder. The phone functionality works fine. I got no problems with any Sim card. I have a valid imei, just the wrong one. I tried firmware installation and initialization with Kies, but it didn't change anything.
I'm traveling through Asia for many months so I can not get a replacement or send it in for repair at home in Europe.
Do you have an idea how I could get my original imei back? or how to mitigate the issues?
Click to expand...
Click to collapse
you can use Darkmed S7 S7 Edge Imei Cert Repair Tool v.1.1.7 and I am sure, they will solve your problem.
allan maanson said:
you can use Darkmed S7 S7 Edge Imei Cert Repair Tool v.1.1.7 and I am sure, they will solve your problem.
Click to expand...
Click to collapse
This post is really old bruh ?
Sent from my SM-N910G using Tapatalk
Hello.
I'll first describe the secuence of events and then tell which solutions I've tried. Bear with me. I'll be brief.
I've bought a second hand Samsung Galaxy S4 (i9500) sold through a local carrier. By law the carrier can only give the unlock code to the original buyer of the phone, and the person from who I bought it from wasn't him/her.
I tried to unlock it by my means (basically this, trying lots of variants until "186" code dead-end), which resulted in rooting, flashing diferent modems and trying a CM based custom ROM (GearCM). Before going on any of this, I made an EFS, cdma-radio, radio, m9kefs1/2/3 backup.
As I couldn't do it, I took the phone to a repair shop, where they unlocked it with a box. Then they told me that the SIM tray was broken, and after trying a different one, they concluded that it was a software problem (I suggested it) and flashed a stock ROM from the carrier, which still didn't recognized any SIM.
This is when I took back the phone.
I've restored the EFS and flashed the correct modem (In fact I've found two which work: I9500UBUHPB2-CP and I9500UBUHOI1), but even if the SIM card is recognized, I can't connect to the network, I think, because the IMEI which displays the phone is different from the factory IMEI. In fact, is the infamous generic IMEI 0049... with IMEISV 01.
I've since tried this methods:
- Changing permissions of the EFS folder
- Flashing the stock ROM after completly wiping out the phone
- Manually deleting the EFS contents and restoring
And combinations of the above with RegionLockAway and with both working modem drivers.
I still have to try rooting an older stock ROM, maybe 4.4.2, but I wanted to ask more wise people if there is a logical, correct order to any of the above steps, or if you think I'm missing something here.
The only other answer that comes to me is that it's something done by the repair shop with the box, but still I've no conclusive proofs of that. I wanted to exhaust options.
Thanks in advance. Any answer will do good.
Restoring the EFS does nothing, as the IMEI is no longer stored in it. Thus none of the things you tried will help. You'll have to take the device back to the place who fixed it for you.
Strephon Alkhalikoi said:
Restoring the EFS does nothing, as the IMEI is no longer stored in it. Thus none of the things you tried will help. You'll have to take the device back to the place who fixed it for you.
Click to expand...
Click to collapse
I would have thought that it was stored on it. Do you infer that from my failed attemps? Where should it be "stored"?
I don't "infer" anything. It's a fact. IMEI was stored in a file named nv_data.bin in EFS, but for some time now it's no longer been located there. It's been moved to three hidden partitions that a nandroid backup does not touch. You'd have to use Wanam Partition Backup and Restore to see the partitions in order to be able to back them up as well as restore them. Thus, your IMEI is gone, and the repair shop is going to have to fix it.
Strephon Alkhalikoi said:
I don't "infer" anything. It's a fact. IMEI was stored in a file named nv_data.bin in EFS, but for some time now it's no longer been located there. It's been moved to three hidden partitions that a nandroid backup does not touch, m9kefs1, m9kefs2, and m9kefs3. You'd have to use Wanam Partition Backup and Restore to see the partitions in order to be able to back them up as well as restore them. Thus, your IMEI is gone, and the repair shop is going to have to fix it.
Click to expand...
Click to collapse
But I have a backup of those partitions, made with Wanam Partition Backup. I've restored them in this order: cdma-radio, EFS, radio, m9kefs1, m9kefs2, m9kefs3. Somehow, its not working.
That's why I think maybe it has to do with the order of the steps I'm taking, maybe even before restoring the partitions.
I edited my post while you were making yours.
My backup consists of much more than those three partitions. I have in addition to those efs.img, fsg.img, modemst1.img, and modemst2.img. The IMEI is in one of those partitions, NOT EFS.
Well then... I hope they can repair the IMEI then. It would be a damn shame if not... Thanks for your time.