Database Users

*** ATTENTION *** STOCK FIRMWARE I9300XXEMG4 -> Changes EFS Folder

Just to update you guys,
What happened?
Several of the guys who flashed the MG4 firmware had their EFS partition modified. Which means that MG4 ROMs work only with MG4 modems at this moment.
Which ROM?
[Stock Official Firmwares] I9300XXEMG4 (4.1.2) - United Kingdom (BTU) and all firmware above MG4
What does it mean to us?
So in case if you have to go back to earlier firmware you will have problems with IMEI. You have to then,
(1) Restore EFS (that is backed up before this change) or
(2) Flash MG4 modem which can still read the modified EFS.
----------------------------------------------------------------------------------------------------
Samsung starting from firmware MG4 is changing the format of the EFS folder partition from one version (read v1) into some kind of new format (read v2). The EFS v2 is only readable by the latest modems from MG4. If an old modem is used with EFS v2 firmware there will be no network connectivity and the IMEI will change to unknown (starting from numbers 0079).
Make a Nandroid / EFS v1 backup, if you plan to flash MG4 firmware or above.
----------------------------------------------------------------------------------------------------
Update: Take a look at the helpful post from User 'JustArchi'
And discussions: here
Thanks: JustArchi, Peter (User:whiskerp) and User:SignetSphere

I have it detailed here too: http://forum.xda-developers.com/showpost.php?p=43935512&postcount=11934

I think this needs more studying, I'm not sating it's not an issue, but I just checked mount points for each partition in adb checking the mounts folder, and that shows this:
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
which tells me that /efs is not seen as a folder, but a seperate partition with the mount point mmcblk0p3. Therefore unless the Odin tar has an efs.img inside it cannot be changed flashing a stock rom, and this rom only contains system, recovery, boot, modem, cache, hidden, bootloader and trustzone, so by all rights the update cannot change the efs, therefore the problem you are explaining must be down to something else.

delsus said:
I think this needs more studying, I'm not sating it's not an issue, but I just checked mount points for each partition in adb checking the mounts folder, and that shows this:
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
which tells me that /efs is not seen as a folder, but a seperate partition with the mount point mmcblk0p3. Therefore unless the Odin tar has an efs.img inside it cannot be changed flashing a stock rom, and this rom only contains system, recovery, boot, modem, cache, hidden, bootloader and trustzone, so by all rights the update cannot change the efs, therefore the problem you are explaining must be down to something else.
Click to expand...
Click to collapse
Hmm... I kinda of agree to what you're saying. It may not be changing the EFS but it maybe changing on how it reads it I really can't say for sure. The truth is I'm still confused by this issue and since i'm no developer i'm just stating the problem based on what I and some others experienced it. I do hope that a more advanced user(s) can enlighten us with this issue since it can confuse others.

SignetSphere said:
Hmm... I kinda of agree to what you're saying. It may not be changing the EFS but it maybe changed on how it reads it I really can say for sure. The truth is I'm still confused by this issue and since i'm no developer i'm just stating the problem based on what I and some others experienced it. I do hope that a more advanced user(s) can enlighten us with this issue since it can confuse others.
Click to expand...
Click to collapse
I would suggest trying to find a developer who will help us to at least understand what's going on, just mention there is a problem, and try to find the root cause of the issue, then tell people what it is and what they can do.

Yes, let's wait for a developer to zero-in on this.

ysrini said:
Yes, let's wait for a developer to zero-in on this.
Click to expand...
Click to collapse
better change the title of the thread then. Add something like *Not confirmed yet, developer input needed*

SignetSphere said:
better change the title of the thread then. Add something like *Not confirmed yet, developer input needed*
Click to expand...
Click to collapse
I'm not sure if I can edit it now

deleted

EVERYONE on this section of the site (at the least) should be backing up their EFS folder.

His happened to me too => after few hours i lose my IMEI too with just flash modem & ril from this rom (EMG4) and i use Wanam7.1 based on FME7 leak. But thanks to my EFS save . I restored my EFS folder & i recover my original IMEI.
And people READ the Advice on this forum => save your EFS folder before any flashs,mods,unlock, etc ...

I backed up my efs ages ago when i first got my phone to this day i never had to once restore it. Then yesterday i was flashing the new EMG4 and it changed my imei number. so i just restored it woot...

wtf... i have no efs backup.
what can ibdo now?

diddsen said:
wtf... i have no efs backup.
what can ibdo now?
Click to expand...
Click to collapse
Stick with EMG4 modem, it only breaks if you try to downgrade.

delsus said:
I would suggest trying to find a developer who will help us to at least understand what's going on, just mention there is a problem, and try to find the root cause of the issue, then tell people what it is and what they can do.
Click to expand...
Click to collapse
Hello guys. I'm glad to tell you that today I've tested everything attached to this issue and want to let you know.
1. Problem is caused by a modem. On the first boot with XXEMG4 modem it changes /efs folder/partition into some kind of new format.
2. This problem isn't caused by RIL or Samsung ROM. It's caused by a modem. That means it also affects CM/AOSP/AOKP/Other, tested on ArchiDroid 2.X.
3. If we use old modem with already changed /efs we won't be able to connect to the network and our IMEI will change to unknown, starting from numbers 0049.
4. If you don't want to mess with /efs folder anymore or don't have a backup of your old /efs you can temporarily use my emergency zip, which changes modem into XXEMG4, not touching RIL or any other stuff, so it's also compatible with CM/AOSP/AOKP/Other variants.
Most important thing - XXEMG4 doesn't corrupt your /EFS, it changes it into a new format.
For now I strongly recommend to not touch anything linked to XXEMG4 and if you did that already I recommend immediately creating a backup of current already changed /efs partition and using my zip to stay on XXEMG4 modem unless we'll have more info.
I'm using XXEMG4 for about a few days already and don't have any problems with it so we can say that it's stable enough. Just keep in mind changes and you can use it.
It's possible that Samsung made it on purpose so basicly they'll fix it in next release or from now modems pre-XXEMG4 won't be compatible with XXEMG4+.
Thanks, hope it helps.
EDIT:
Yes, you can use any rom for SGS3 with already changed /efs to V2, just stick with my emergency zip and flash it every time you're flashing a new version of your rom. This way you'll have xxemg4 modem whole the time and every rom will work with that. Tested on ArchiDroid 2.0.3 (AOSP), 1.6.1 (XXUFME7) and 1.5.3 (XXEMF1).

JustArchi said:
Hello guys. I'm glad to tell you that today I've tested everything attached to this issue and want to let you know.
1. Problem is caused by a modem. On the first boot with XXEMG4 modem it changes /efs folder/partition into some kind of new format.
2. This problem isn't caused by RIL or Samsung ROM. It's caused by a modem. That means it also affects CM/AOSP/AOKP/Other, tested on ArchiDroid 2.X.
3. If we use old modem with already changed /efs we won't be able to connect to the network and our IMEI will change to unknown, starting from numbers 0079.
4. If you don't want to mess with /efs folder anymore or don't have a backup of your old /efs you can temporarily use my emergency zip, which changes modem into XXEMG4, not touching RIL or any other stuff, so it's also compatible with CM/AOSP/AOKP/Other variants.
Most important thing - XXEMG4 doesn't corrupt your /EFS, it changes it into a new format.
For now I strongly recommend to not touch anything linked to XXEMG4 and if you did that already I recommend immediately creating a backup of current already changed /efs partition and using my zip to stay on XXEMG4 modem unless we'll have more info.
It's possible that Samsung made it on purpose so basicly they'll fix it in next release or from now modems pre-XXEMG4 won't be compatible with XXEMG4+.
Thanks, hope it helps.
Click to expand...
Click to collapse
I wouldn't assume that Samsung will "fix" anything, since this is not broken. I don't think a recommendation to NOT use is advisable at all. Samsung wouldn't risk changing the EFS format of many, many phones only to go ahead and rerun the same risk unchanging them... especially considering the boost in performance this new radio has supposedly brought about.

Kryten2k35 said:
I wouldn't assume that Samsung will "fix" anything, since this is not broken.
Click to expand...
Click to collapse
Same. Especially because I still think that they made it on purpose.
---------- Post added at 09:15 PM ---------- Previous post was at 09:06 PM ----------
Kryten2k35 said:
I wouldn't assume that Samsung will "fix" anything, since this is not broken. I don't think a recommendation to NOT use is advisable at all. Samsung wouldn't risk changing the EFS format of many, many phones only to go ahead and rerun the same risk unchanging them... especially considering the boost in performance this new radio has supposedly brought about.
Click to expand...
Click to collapse
As for now it's just the first release of a new format and it takes some time to prove stability. You can't say after first day of a release that it's completely fine and nothing to worry about . If same situation appears with newer versions then yes, slowly people will change into new /efs base with less worries.

Well, they wouldn't issue the update OTA and via Kies if it was a problem, imho.

Kryten2k35 said:
Well, they wouldn't issue the update OTA and via Kies if it was a problem, imho.
Click to expand...
Click to collapse
Sudden Death also wasn't a problem until some moment .

So if i have this firmware i should play with it at all ?
Can i at least reflash it , i wanna root it , use triangleaway and than reflash whole firmware again with odin ?

[GUIDE] How to restore EFS on I9300

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 .

Null IMEI... Help please...

In all my foolishness and ignorance I have managed to lose my IMEI number while changing my firmware... Now my phone does not have a IMEI number...
An somebody help me??
EDIT: OK I realised my IMEI is written at the back of my phone all along... How do I get it to work in my phone?

rocker128 said:
In all my foolishness and ignorance I have managed to lose my IMEI number while changing my firmware... Now my phone does not have a IMEI number...
An somebody help me??
EDIT: OK I realised my IMEI is written at the back of my phone all along... How do I get it to work in my phone?
Click to expand...
Click to collapse
Have you tried flashing stock?

Not yet. I will get it done now. Will report any results

Flashing stock doesn't help. I have flashed the N9005DXUGNH1 firmware, both the imei and baseband remain unknown.
Now I'm using the mokee rom

rocker128 said:
Flashing stock doesn't help. I have flashed the N9005DXUGNH1 firmware, both the imei and baseband remain unknown.
Now I'm using the mokee rom
Click to expand...
Click to collapse
Try flashing this: http://forum.xda-developers.com/showthread.php?t=2507403

nicholaschum said:
Try flashing this: http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
What does this do? Will it restore my corrupted efs folder and restore my IMEI? Do I need to revert to stock?

rocker128 said:
What does this do? Will it restore my corrupted efs folder and restore my IMEI? Do I need to revert to stock?
Click to expand...
Click to collapse
It tries to restore your corrupted efs folder.

rocker128 said:
What does this do? Will it restore my corrupted efs folder and restore my IMEI? Do I need to revert to stock?
Click to expand...
Click to collapse
if that is not work your IMEI is on the BLAKLIST of samsung.

Nico231995 said:
if that is not work your IMEI is on the BLAKLIST of samsung.
Click to expand...
Click to collapse
Uhm. NO. Samsung does not blacklist any IMEI's just because we are rooting/flashing our handsets.
A blacklisted IMEI will not be null/null, a blacklisted IMEI will be the original IMEI.
This is some kind of software fault (Or ofcause HW)
Try to reboot into recovery, do you get failed to mount /EFS?
Best regards

Ratata82 said:
Uhm. NO. Samsung does not blacklist any IMEI's just because we are rooting/flashing our handsets.
A blacklisted IMEI will not be null/null, a blacklisted IMEI will be the original IMEI.
This is some kind of software fault (Or ofcause HW)
Try to reboot into recovery, do you get failed to mount /EFS?
Best regards
Click to expand...
Click to collapse
you and me have desame problem but my phone have IMEI NULL and BASEBAND unknown i restore my imei and baseband but NO SIGNAL that's my POINT. the only way to fix my phone is to change IMEI from the original one to have Signal. and now my phone is working.

nicholaschum said:
It tries to restore your corrupted efs folder.
Click to expand...
Click to collapse
Nope it does not work. I reflash the mokee rom, gapps then this and now it still says baseband and imei unknown

rocker128 said:
Nope it does not work. I reflash the mokee rom, gapps then this and now it still says baseband and imei unknown
Click to expand...
Click to collapse
Try do it on stock ROM.
While you're in stock ROM, use this: http://forum.xda-developers.com/showpost.php?p=46391737&postcount=350

nicholaschum said:
Try do it on stock ROM.
While you're in stock ROM, use this: http://forum.xda-developers.com/showpost.php?p=46391737&postcount=350
Click to expand...
Click to collapse
That instruction is for T-Mobile Note 3.
On Note 3 International version the partitions may be different, so doing that may mess up with partitions and may brick the device.
Be careful.

vndnguyen said:
That instruction is for T-Mobile Note 3.
On Note 3 International version the partitions may be different, so doing that may mess up with partitions and may brick the device.
Be careful.
Click to expand...
Click to collapse
Partitions are the same. You can install N900T ROMs on N9005 devices easily.

nicholaschum said:
Partitions are the same. You can install N900T ROMs on N9005 devices easily.
Click to expand...
Click to collapse
Yes, but the EFS partition may be different.
In that instruction, I see the EFS partition is mmcblk0p12.
But on my Note 3 N9005, the EFS partition is mmcblk0p11.
So just a warning.

vndnguyen said:
Yes, but the EFS partition may be different.
In that instruction, I see the EFS partition is mmcblk0p12.
But on my Note 3 N9005, the EFS partition is mmcblk0p11.
So just a warning.
Click to expand...
Click to collapse
It's quite an old post, it could have been for 4.3...not sure though.

nicholaschum said:
It's quite an old post, it could have been for 4.3...not sure though.
Click to expand...
Click to collapse
I believe that updating from 4.3 to 4.4.2 will not change the partition structure.
The partition structure is device-dependence, and vary from model to model (N900T vs N9005).
@ OP: you can follow that instruction, but you may need to replace its efs partition (mmcblk0p12) to your efs partition (mmcblk0p11, if your device is N9005 international version, as mine).

vndnguyen said:
I believe that updating from 4.3 to 4.4.2 will not change the partition structure.
The partition structure is device-dependence, and vary from model to model (N900T vs N9005).
@ OP: you can follow that instruction, but you may need to replace its efs partition (mmcblk0p12) to your efs partition (mmcblk0p11, if your device is N9005 international version, as mine).
Click to expand...
Click to collapse
Yeah try that.
4.3 Bootloaders can't boot KK ROMs, which is how I came to that conclusion - and vice versa.

nicholaschum said:
Try do it on stock ROM.
While you're in stock ROM, use this: http://forum.xda-developers.com/showpost.php?p=46391737&postcount=350
Click to expand...
Click to collapse
Ok, im downloading an international firmware now (XXUEND3), will try that method once it flashed it. One question though... how do i do an "adb shell"?
Thank you both of you for helping a noob like me...

rocker128 said:
Ok, im downloading an international firmware now (XXUEND3), will try that method once it flashed it. One question though... how do i do an "adb shell"?
Thank you both of you for helping a noob like me...
Click to expand...
Click to collapse
Enable USB debugging, connect your phone to the computer.
Install adb using the 15 second adb installer (Google it) and in the directory adb is installed in, hold down shift then right click on a blank area, click on Open command window here, then type adb start.
Sent from my OnePlus One using Tapatalk VIP

[Q] [i9505] Galaxy S4 Baseband and IMEI: Unkown

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?

galaxy s5 (SM-G900F) with no imei please help

i have galaxy s5 (SM-G900F) with no imei
the imeisv is 04
i didnt backup it or anything there is a way to restore it?

ben.anter said:
i have galaxy s5 (SM-G900F) with no imei
the imeisv is 04
i didnt backup it or anything there is a way to restore it?
Click to expand...
Click to collapse
Have you tried flashing stock with Odin?

Have you still got a radio signal (Make calls / text etc) ?
If not, you might have lost your EFS partition, which afaik, needs a professional repair to fix unless you backed up that partition first

RuffBuster said:
Have you tried flashing stock with Odin?
Click to expand...
Click to collapse
yep i have tried to update it with stock frimware but didnt help.
*Detection* said:
Have you still got a radio signal (Make calls / text etc) ?
If not, you might have lost your EFS partition, which afaik, needs a professional repair to fix unless you backed up that partition first
Click to expand...
Click to collapse
i have the signal bars working but no imei. no backup.
there is no other way to restore it somehow?

ben.anter said:
yep i have tried to update it with stock frimware but didnt help.
i have the signal bars working but no imei. no backup.
there is no other way to restore it somehow?
Click to expand...
Click to collapse
Before you try anything, I strongly advise you to backup your EFS partition or you could end up with no signal at all
IMEI and Radios are both contained in the EFS partition, lose that, your screwed
http://forum.xda-developers.com/showthread.php?t=2696153

*Detection* said:
Before you try anything, I strongly advise you to backup your EFS partition or you could end up with no signal at all
IMEI and Radios are both contained in the EFS partition, lose that, your screwed
http://forum.xda-developers.com/showthread.php?t=2696153
Click to expand...
Click to collapse
i have signal but when i try to make a call it says "not registered in the network"
and i have backup my efs partition to my sdcard as you said.
what now?

ben.anter said:
i have signal but when i try to make a call it says "not registered in the network"
and i have backup my efs partition to my sdcard as you said.
what now?
Click to expand...
Click to collapse
Might be too late if the EFS partition is corrupted and you don't have an IMEI and can't make calls
There are a couple of threads kicking about on XDA S5 forums where people have managed to recover their phones with similar problems, have a read through the Q&A forum and see if you can find them, some fixed by flashing stock, not sure how that worked, but apparently it did
Read others saying they backed up a working S5 EFS and restored it to the broken one
Have a read and see what you can find

*Detection* said:
Might be too late if the EFS partition is corrupted and you don't have an IMEI and can't make calls
There are a couple of threads kicking about on XDA S5 forums where people have managed to recover their phones with similar problems, have a read through the Q&A forum and see if you can find them, some fixed by flashing stock, not sure how that worked, but apparently it did
Read others saying they backed up a working S5 EFS and restored it to the broken one
Have a read and see what you can find
Click to expand...
Click to collapse
so you saying the only thing i can do is to flash a new imei with octoplus or some other kind of boxes.
and if i recover imei from other phone it will not cause network problem becuase there is two phones with the same imei ??

The law in most countries states that the only IMEI number you can use in your phone is the one it came with.....
Nobody here on XDA is going to give you advice on how to change your IMEI for that reason......it's against the law..... *and* as such, it's against XDA rules as well......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
The law in most countries states that the only IMEI number you can use in your phone is the one it came with.....
Nobody here on XDA is going to give you advice on how to change your IMEI for that reason......it's against the law..... *and* as such, it's against XDA rules as well......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
^^This.
Thread closed.