Related
It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
FAQ
If you need the ODIN, you can find theme over here. Myself I've always used version 3.07. And as always under options you only need the 'Auto Reboot' and 'F. Reset Time' checked. Whether it a modem or stock ROM, click on 'PDA' choose the correct file and than click on start.
Q: Won't flash the EFS image I provide means I'm getting your IMEI?
A: I've wondered this as well. If it were so simple, there wouldn't be so many thread on recovering and so may people cry for help... (I'm included). As my last resort before I buy Chimera Tool's license, I flashed over my bro's S3 EFS, which I didn't want to, as I said it was a last resort. And as it turned out, I didn't get his IMEI. Instead I got his phones' Update S3 product code and serial number. And that was it. IMEI has changed from my previous 'NULL' to the infamous generic 004999010640000.
Q: Why do I still need to do EFS recovery if Chimera Tool can restore it.
A: I've experiment this myself, as I also absolutely did not want my bro's EFS. But unfortunately Chimera can only restore the IMEI and serial number, not rest of the missing files in the EFS folder. If I repartition the EFS folder and using Chimera to restore my IMEI, it would show the correct IMEI but still refuse to connect to the network. And it will have the annoy overly showing my CSC and other bunch of info on my homescreen, as if my EFS is still corrupt.
Q: Does Chimera need some special box?
A: No, a normal USB cable will work. That pretty much means standard ADB command would work, but unfortunately I can't find any info on that. I wish I did, so I don't need to get the Chimera Tool but there was no other way for me. I was also sceptical at first, as I read over many forums and they say it impossible with some sort of service box/tool. I gambled, and luckily it worked out.
Q: Where does the EFS image go for kTool?
A: Sorry, don't remember. Google it, or use the backup option first than overwrite the EFS.IMG file. That what I did.
Q: Now that I got my IMEI back, how do I back it up?
A. Use kTool again? Personally I use TWRP, as I think it the easiest. Since you can do it at a recovery level. No trying of ODIN the OS for corrupt OS before restoring the EFS. In any case, Chimera would still be function for the next couple of month and you can still mess around until than.
Q: Why the need of ODIN the original firmware?
A: I was on a custom TW ROM and Chimera didn't work. Maybe CM and other custom ROM will will work, you can give it a try. But this is how I did it and I know it works.
EFS / Baseband(modem)
It easy to criticize a member and simply tell him use the 'search function', but without realize sometimes the article will help you the most, simply just doesn't come up. Murphy's law. I was on stock 4.1.2 and after restore IMEI and EFS, the phone indicate it register on the network, but I couldn't make calls or connect to the net. This is a vary good article regarding EFS, and sadly it didn't come up easily on my search result. I came across it after I fixed the issue with tones of Googling and was searching for a different topic. But I understand people that desperate need to solve the problem quick (like I was) simply spent hour reading over hundreds of post under that article is just testing a persons sanity. So I'm going to summarised some of the stuff along with my experience. First thing you need to know:
- EFS v2 Basebands (modem) was introduced at Android 4.3 and can read EFS partition v2 and EFS v1
- EFS v1 Basebands (modem) CANNOT read EFS v2, ONLY EFS v1
If you phone is still under warranty and cannot connect to network, the best way is to stay on stock firmware and use TriangleAway to reset the flash counter and sent back to Samsung. With your IMEI number correctly showing, Samsung has absolutely no excuse on not fixing it. If you are no longer warranty, read on.
Q: My IMEI is now showing correctly but I still cannot make calls!
A: This is where the Ariza Patch kicks in. If you are on stock fimware 4.1.2, you need the Ariza Patch to fix the baseband. But after long reading over plenty post, it seems once this patch has been done, it irreversible. So beware. Before you try this patch, you may want to try update to the stock 4.3 firmware and see if it solves the problem before applying the patch.
Q: I'm on stock 4.3, now what?
A: If you still have problem connecting to the network, you need a patched modem (baseband) file. You can find them here. I think this is from the original author who did it. Instead of searching over the forums and files scatter all over the place, I'm pretty sure I dug the link out of XDA while reading through. Someone please tell me if it isn't and provide the the proper link. I'll fix it.
Q: I was on stock 4.1.2 and went to a custom 4.3 ROM, what fix shall I apply?
A: This was my scenario. And I was kind of desperate as well since I just fix my IMEI and was expect the phone to work. I wish I could come across the article on top earlier. I would've tried stock 4.3 first instead of applying the Ariza patch. Any ways, I was on stock 4.1.2 and it didn't work, so I tried a modified 4.3 TW ROM. I wish the OP would mention the EFS thing, which he didn't. I'm not blaming him or anything, but seriously not everyone keep in track of what happening with Android. The OP should mention about the EFS thing or simply post a link such as the topic above and just let people know instead of wasting hours on figuring out why it wasn't working. What I did was, after using the mod 4.3 TW ROM, the IMEI went crazy. So I thought it was corrupt again, so I ODIN back the stock 4.1.2 TW. Than I applied the Ariza patch, wolla, I could call and browse again. So I decide to give the mod 4.3 TW ROM another try. To my surprise, the IMEI still went crazy. So after more Googling only I found out because I wasn't on stock 4.3, my baseband would still 4.1.x. I tried the modem (baseband) patch which for some reason still did not work for me. So I decide to keep the stock 4.1.2 baseband and simply use a custom kernel that could read EFS v1 and v2 - Boeffla Kernel. Remember to download the 4.3 kernel not the 4.1.x! That it, you should now have a working phone.
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
nainaabd said:
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
Click to expand...
Click to collapse
Didn't try SA manager as I was in a rush and looking specifically for Samsung phones only. But it definately somehting I want to try if I get a Sony phone. Though I still prefer at a recover level. It just so simple.
keenimo said:
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
Click to expand...
Click to collapse
TAR file is just a compressed version of IMG file.
im in nairobi kenya, unfortunately i can not buy the chimera tool because we dont have the necessary paying methods. anyone who can lend me theirs please? my S3 has the generic imei, repair would cost 15k here, which is too much. anybody that can help will be highly appreciated.
TNCS said:
It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
Click to expand...
Click to collapse
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Xubair91 said:
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Click to expand...
Click to collapse
From what I understand, that still under the condition of prior having an EFS back-up first, right? My guide is for people who doesn't. Like in my situation, where the app screwed up the EFS partition and I had no back-ups.
If you really want in details - Swapper 2 moved the EFS partation on to my ext SD card and format the EFS partition. I was in a flat panic with the soft-brick froze at the Samsung boot logo, assume the SWAP was on the ext SD and screwed it up than format the ext SD. Well, boom, without expectation the app would do something like that and had no prior experience with EFS - no back-ups of EFS at all. And no, full nandroid back-up from CWM does not contain EFS, I've tried that. This isn't some normal scenario of incompatibility between kernel/ROM and EFS/Modem. This is recovery guild for corruption of EFS with NO back-ups.
trying ....
mezo_mmm said:
trying ....
Click to expand...
Click to collapse
And how did it go? The suspense it killing me .
Hi,
I've been having problems with my 4 month old GS4 lately, mainly because I was not able to make or receive calls and texts. I looked up my problem, and eventually traced it down to a unknown baseband and IMEI problem. Sure enough, my baseband and IMEI was missing. I researched and found out that you need to backup your EFS folder as it may have been corrupted, unfortunately I was not able to do so. I even tried factory resetting my phone to stock TouchWiz, hearing reports that a hard reset can fix the problem; unfortunately, I'm still missing my IMEI and Baseband. All help is appreciated
This Phone was/is rooted, and has been flashed several times with custom ROMS.
Thank you in advance.
If the problem started without you flashing or doing anything else, then you have a hardware failure. Your emmc chip is probably broken. Bring it to a service center.
Lennyz1988 said:
If the problem started without you flashing or doing anything else, then you have a hardware failure. Your emmc chip is probably broken. Bring it to a service center.
Click to expand...
Click to collapse
I'm not so sure really. I flashed Cyanogenmod and it was working fine, I could make and receive calls. However, my SIM card died and I had to replace it. That was when I noticed the problem.
EDIT: Okay, I failed to read completely. I kept reflashing nandroid backups however, after experiencing problems unrelated to this.
HeadhuntrActual said:
I'm not so sure really. I flashed Cyanogenmod and it was working fine, I could make and receive calls. However, my SIM card died and I had to replace it. That was when I noticed the problem.
EDIT: Okay, I failed to read completely. I kept reflashing nandroid backups however, after experiencing problems unrelated to this.
Click to expand...
Click to collapse
Try using root explorer and see if your efs folder is ok?
Old_Geezer said:
Try using root explorer and see if your efs folder is ok?
Click to expand...
Click to collapse
How do I know if it is okay??? P.S. I can't find certain files like nv_data.bin... sign of corruption?
HeadhuntrActual said:
How do I know if it is okay??? P.S. I can't find certain files like nv_data.bin... sign of corruption?
Click to expand...
Click to collapse
It might be, since my efs folder have nv_data.bin but i can't tell for sure since i'm still a newbie here.
Did you try searching for efs backup on the phone? I know some roms do automatic backup after flash so it might be left there somewhere.
HeadhuntrActual said:
I'm not so sure really. I flashed Cyanogenmod and it was working fine, I could make and receive calls. However, my SIM card died and I had to replace it. That was when I noticed the problem.
EDIT: Okay, I failed to read completely. I kept reflashing nandroid backups however, after experiencing problems unrelated to this.
Click to expand...
Click to collapse
I don't understand what you are saying.
When did your problem start? Did you do anything or did it happen without you doing anything.
Old_Geezer said:
It might be, since my efs folder have nv_data.bin but i can't tell for sure since i'm still a newbie here.
Did you try searching for efs backup on the phone? I know some roms do automatic backup after flash so it might be left there somewhere.
Click to expand...
Click to collapse
I tried, there was none unfortunately, I also flashed back to stock twice. If there was, it was probably wiped.
Lennyz1988 said:
I don't understand what you are saying.
When did your problem start? Did you do anything or did it happen without you doing anything.
Click to expand...
Click to collapse
I can't say for sure. My IMEI and Baseband was visible when I was running CM11. My SIM died eventually, so I had 0 service after that for about a week. During this time, I flashed AntaresOne's Unofficial cm12 5.0. Maybe it was corrupted when I flashed it? Anyway, My efs folder appears to be missing files aswell. I can't seem to find nv_data.bin perhaps my efs folder really is corrupted?
So, my Note 3 N9005 worked fine, then i tried to install CM 12 The phone kept locking so i tried to install CM 12.1 instead. It did the same thing. Then i tried to install CM11. Phone got stuck to a bootloop. Then i tried to install the stock firmware. It launched but the phone lags like hell, apps don't open at all. Waking up the phone takes a lot of time. And the phone doesn't recognize the sim-card anymore. I used CWM to install all the custom roms, and i wiped cache, dalvik cache and did a factory reset every time before i installed a new rom. I used Odin v. 3.04 to flash the stock firmware.
So my question is this, how do i get my phone back up and running smoothly again, like it was fresh out the box? I'll appreciate all the help i can get because i am starting to get very desperate, i really wouldn't like to tell my mom i need a new phone. Note 3 cost like hell after all.
I am from Finland so i used the N9005XXUEND5 version of the stock firmware, KitKat 4.4.2.
The only thing i can think of that can cause this problem is that if the OS's i installed didn't get deleted fully, so there would be multiple OS's on my phone running at the same time. This may be a bit far fetched.
Please help as fast as possible. And i'm not that good at these things so i would appreciate if you could walk me through this step by step and explaining each step as specifically as you can.
Judging from your post, you didn't even bother to read the install instructions of the roms you were flashing.
And this is the result you get.
In CWM recovery mounts and storage format sdcard system cache data preload .
Reboot to download mode and flash stock rom .
The last time i flashed the stock ROM I formatted everything, including the firmwares and such. Now i flashed AOKP ROM and the phone is working fine, except it doesn't recognize the sim card. Any idea how to fix that. Thanks for all the help so far
Basics check you have correct IMEI and correct modem change sim card .
I'm sorry, i have no idea what IMEI and correct modem change sim card. :/
If you don't understand the very basics of flashing and firmware then i suggest you take your phone to a repair shop .Its not a game you are going to end up with a dead phone with no chance of a fix .
I think i understand the very basics of flashing, considering i have done it before twice and on both times it has worked. My sim card worked on my moms Lumia, so is it possible that the sim card reader broke. Can flashing a rom or formatting system do that? Are there a kernel i should flash? I heard it might fix problems like these. And when i go to settings there are no options for IMEI or modem change, that's why i'm confused.
**********************************************
I do have my backup still, but when i try to restore it with CWM, it says something about md5 sums, any idea how to deal with that, because i think that would help if i could use that backup. The stock rom that i downloaded wasn't from any known page. Mostly because SamMobile doesn't have my version anymore for some reason. And i tried to download it from samsung-updates.com but it said that the download would take about 9 hours. I think that the download time would only keep growing and growing so eventually it would be a waste of time.
I think i understand the very basics of flashing,
No you don't and that's your problem this post only makes it more obvious and makes it nearly impossible to give guidance .
MD5 and cwm basics turn off MD5 check in recovery .
You cannot go flashing kernels for no reason .
Modem change is not settings neither is IMEI .
Broken sim reader yes its possible but highly unlikely from a firmware bad flash .
Its entirely possible that you have downloaded a bad firmware .
You also have a non Samsung rom flashed now (aokp)
suggest you read up on that for problems .Though i cannot see any 9005 AOKP roms here .
But first you need to check you have the correct IMEI if your IMEI does not match then you restore the EFS folder you backed up before you started flashing .
I said that i would appreciate that if you would guide me through this step by step. How can i check IMEI? I'm sorry i'm making this so hard for you. The only thing i care about now is that i get my phone back stock and running smooth.
*****************************************************
That is also true that i might have downloaded a bad firmware. Are there any other place to get a stock firmware other than samsung-updates.com?
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
WhateverMan said:
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
Click to expand...
Click to collapse
I checked and it sais my IMEI is unknown. But i will try to flash that software you suggested
Restore the EFS folder you backed up .
JJEgan said:
Restore the EFS folder you backed up .
Click to expand...
Click to collapse
I think i already said something about it not working because of incorrect md5 sums.
You said backup that's not your EFS backup .
Solution given for MD5 .
JJEgan said:
You said backup that's not your EFS backup .
Solution given for MD5 .
Click to expand...
Click to collapse
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
The EFS folder contains your phones unique identification code or IMEI . Without correct IMEI your phone cannot connect . That is why the EFS folder is backed up before anything is ever flashed . No backup and wrong IMEI then you probably need a service centre repair . EFS/ IMEI can be damaged during flashing that is why rule one is backup your EFS folder first .
Nansus said:
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
Click to expand...
Click to collapse
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
You can restore your backed up EFS folder .
CWM backup restore does not include EFS .
You can flash lollipop .
You can flash a matching modem .
All these may restore IMEI or make the situation worse that is why a service repair is recommended .
phonexpert_alex said:
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
Click to expand...
Click to collapse
I'm sorry if i sounded rude towards to anybody, that is totally not what i'm trying to be. I know you guys are trying to help so i really don't see why i would be rude towards to anyone. I guess my english is still so bad that i'm sounding rude.
I think the best option now is to take the phone to a service repair. Especially if flashing anything can make the situation worse.
I thank everyone that has tried to help. It seems like that i have to accept the fact that i ****ed up my phone. At least this will serve as an example to anyone who's trying to flash custom roms and don't know what they are doing.
Oh, and the reason i have this phone because i'm a student i high school. I just started doing flashing and trying custom roms and i guess i thought it would be really simple. Clearly it wasn't.
Hey, I started flashing custom ROMs to my S4 (GT-i9506) about three months ago and everything was okay, but just recently I tried to return to my stock i9506 4.4.2 ROM and i succeeded in doing so, but afterwards I noticed that my S4 wasn't recognising my SIM.
At first I assumed it was a faulty SIM card (my SIM had multiple scratches on it), so I bought a new SIM card and yet the problem persisted. I tried to make calls and etc but my phone retuned an error stating, "Mobile network not available". I decided to check my settings and I noticed that my Baseband Version was labelled as "unkown".
After seeing this I searched for solutions online and came upon S4 service codes, I used the "*#06#" code and it returned a message saying "IMEI... null/null". Yet again I searched for a solution and came upon none to help me
I soon found out that my problem had something to do with the EFS parition in my phone. I re-rooted and installed ES File Explorer and opened up my EFS folder. In her everything looked ordinary, but then I noticed that my .nv_data file was missing, which, if i remember correctly, is responsible for important functions such as the IMEI and Baseband
I tried every solution I could find online and nothing fixed my issue - I'm only writing this as it's the only option which doesn't require me to go to my local Samsung Experience Store.
TL;DR
My GT-i9506 doesn't know its own IMEI and Baseband version and I'm all out of solutions at this point.
Am I better off going to the Samsung Store?
BUMP
More BUMP
Please help me
BUMP
IMEI no longer inhabits the EFS folder, so you're not missing anything. Flash the modem for your ROM again through Odin and see if that corrects the issue. If it does, use Wanam's EFS Backup to properly backup the hidden partitions where the IMEI is now stored.
Flash the latest stock lollipop rom for your device and you will be fine. Sounds to me you were on Lollipop stock and you downgraded to Kitkat.
Strephon Alkhalikoi said:
IMEI no longer inhabits the EFS folder, so you're not missing anything. Flash the modem for your ROM again through Odin and see if that corrects the issue. If it does, use Wanam's EFS Backup to properly backup the hidden partitions where the IMEI is now stored.
Click to expand...
Click to collapse
So then where is the IMEI stored? I'd just like to know for future purposes
The modem didn't fix it
Lennyz1988 said:
Flash the latest stock lollipop rom for your device and you will be fine. Sounds to me you were on Lollipop stock and you downgraded to Kitkat.
Click to expand...
Click to collapse
Tried this too, but failed also
I don't know which of the hidden partitions the IMEI is stored in. I only know where it's not, and that's not in the EFS folder. However, based on the partition names, the IMEI is likely stored in any or all of the following partitions: m9kefs1, m9kefs2, m9kefs3. While unlikely, it could also be stored in the following partitions: modemst1, modemst2.
Strephon Alkhalikoi said:
I don't know which of the hidden partitions the IMEI is stored in. I only know where it's not, and that's not in the EFS folder. However, based on the partition names, the IMEI is likely stored in any or all of the following partitions: m9kefs1, m9kefs2, m9kefs3. While unlikely, it could also be stored in the following partitions: modemst1, modemst2.
Click to expand...
Click to collapse
Would it be possible to mount any of those partitions?
jakeshekukanneh said:
Tried this too, but failed also
Click to expand...
Click to collapse
I need more info then this.
jakeshekukanneh said:
Would it be possible to mount any of those partitions?
Click to expand...
Click to collapse
You can try it, but I doubt you'll find anything human readable within them.
Lennyz1988 said:
I need more info then this.
Click to expand...
Click to collapse
I flashed the stock I9506XXDOA6 NEE ROM in Odin once more but my IMEI remained null.
So I decided to extract the modem.bin after installing the Lollipop ROM and it too didn't work
jakeshekukanneh said:
I flashed the stock I9506XXDOA6 NEE ROM in Odin once more but my IMEI remained null.
So I decided to extract the modem.bin after installing the Lollipop ROM and it too didn't work
Click to expand...
Click to collapse
Maybe I didn't elaborate enough....
Try This Maybe This Help!!
use samsung kies fimeware upgrade and instalition then it waant youre imei or s/n and its rightet under battry
Note: Do That in download Mode
I've already tried that multiple times though. Thanks for the suggestion however
Sent from my GT-I9506 using XDA Free mobile app
Strephon Alkhalikoi said:
I don't know which of the hidden partitions the IMEI is stored in. I only know where it's not, and that's not in the EFS folder. However, based on the partition names, the IMEI is likely stored in any or all of the following partitions: m9kefs1, m9kefs2, m9kefs3. While unlikely, it could also be stored in the following partitions: modemst1, modemst2.
Click to expand...
Click to collapse
Hi, I used to use Optimus G, it has IMEI in m9efs* and Modem in modem, modemst*. I never had IMEI problems but on S4 it is really scary. Will backing up EFS in TWRP, manually dd'ing EFS, modemst*, m9kefs* block10 make me stay on safe side?
Sent from my GT-I9505
Just use Wanam's EFS Backup tool. It backs up all those partitions, so no need to run commands in a terminal.
jakeshekukanneh said:
I've already tried that multiple times though. Thanks for the suggestion however
Sent from my GT-I9506 using XDA Free mobile app
Click to expand...
Click to collapse
There was a guy that claimed that his method fixed it for him:
https://www.youtube.com/watch?v=LgPEIeXDPNA
Lennyz1988 said:
There was a guy that claimed that his method fixed it for him:
https://www.youtube.com/watch?v=LgPEIeXDPNA
Click to expand...
Click to collapse
Hey, I've already tried that method prior to posting, unfortunately it didn't work. I might just go see the Samsung Experience Store tomorrow
Hello everybody,
What can I do if my Axon 7 has lost the IMEI by restoring a backup through TWRP? My baseband version is unrecognized.
I have tried to save on this thread the mobile phone, but the problem "IMEI Changer" does not recognize DIAG port.
Windows only shows:
Sry for my bad english. I use Google Translate.
I hate to say this, but you're out of luck. If you restored your EFS partition via a bad version of TWRP, you're stuck. Send it back to ZTE.
Controllerboy said:
I hate to say this, but you're out of luck. If you restored your EFS partition via a bad version of TWRP, you're stuck. Send it back to ZTE.
Click to expand...
Click to collapse
Damn and I was hoping through the program IMEI Changer could save the phone ...
I have the A2017G model and the bootloader has been unlocked. The device was bought at Amazon in Germany. Is it possible to send the device to the manufacturer because of the warranty?
logimowl said:
Damn and I was hoping through the program IMEI Changer could save the phone ...
I have the A2017G model and the bootloader has been unlocked. The device was bought at Amazon in Germany. Is it possible to send the device to the manufacturer because of the warranty?
Click to expand...
Click to collapse
I encountered the exact issue you told me. I restored a TWRP backup that I had made through a faulty TWRP version and it made me lose my IMEI and baseband. Tried just about anything. Nothing worked.
Restored everything to stock, reflashed stock recovery and locked bootloader and sent it back. Got a new one, only had to pay the shipping costs of my device to Germany. I hope you're as lucky as I have been. Thumbs up.
How can we make a backup of imei?
SilentEYE said:
How can we make a backup of imei?
Click to expand...
Click to collapse
Folks need to stop messing with the EFS partition. The only things you should be backing up with twrp is boot, system, and data. Nothing else.
Have you tried the zadig tool?
http://zadig.akeo.ie
Also, I've found this Qualcomm Driver to always work for me in the past. Surprising. It's the ONLY one that could help my device get detected by certain tools.
I uploaded it to my AFH for safekeeping: https://www.androidfilehost.com/?fid=817550096634746189
If you haven't tried any of this yet, just give it a whirl. I used the IMEI tool to rewrite my IMEI when I accidentally wiped it, and it was perfect.
My imei is shown as unknow i have a US phone but its working fine so i dont really pay much atention to it lol, but i will try the app kwesi posted to see if i can get it working