Uh oh...
After cm11 nightly july1, NO SERVICE!
I assumed this would be modem related stuff, so I reflashed the NAE modem - nothing. I flashed back to cm10.2 - nothing. I flashed back to original full MDC stock rom - still nothing. It just get's stuck on "preparing network" forever. There are rumblings here & there that clockwork recovery (6.0.4.7 touch in this case) is corrupting the efs partition, which may or may not be the cause of this problem. In any case, I can't seem to locate an efs jflte Sprint image to restore from to test this theory because it's not included in flashable roms, and I wasn't even aware that it existed until now. If I can't get this fixed somehow, my "phone" will now be a very expensive wifi screen. Any insight into this issue is mucho grande appreciated as this is a showstopper for me.
Not sure what could be causing your issue, I didn't how ever have that problem before tho, what I did was flash a stock ROM & their should be a dailer code used to reset your data (which I forgot, so look around for it, it has been mentioned on a lot of threads, sorry about that), then after dialing the code, your phone should reboot & it should be good, if not try reflashing the correct radio/modem for your android version.
Another thing, you posted this in the wrong section, their is a Q&A section for things like this.
×Rebel Nation×
r0ckstar said:
Uh oh...
After cm11 nightly july1, NO SERVICE!
I assumed this would be modem related stuff, so I reflashed the NAE modem - nothing. I flashed back to cm10.2 - nothing. I flashed back to original full MDC stock rom - still nothing. It just get's stuck on "preparing network" forever. There are rumblings here & there that clockwork recovery (6.0.4.7 touch in this case) is corrupting the efs partition, which may or may not be the cause of this problem. In any case, I can't seem to locate an efs jflte Sprint image to restore from to test this theory because it's not included in flashable roms, and I wasn't even aware that it existed until now. If I can't get this fixed somehow, my "phone" will now be a very expensive wifi screen. Any insight into this issue is mucho grande appreciated as this is a showstopper for me.
Click to expand...
Click to collapse
Try this:
In cm10.2 find cdma subsciption and change between NV and RUIM.
Or use cdma workshop to change it.
jam97 said:
Try this:
In cm10.2 find cdma subsciption and change between NV and RUIM.
Or use cdma workshop to change it.
Click to expand...
Click to collapse
Well, That probably would have worked yesterday. But sadly, I have managed to brick the phone. I became impatient, tired, and careless after effing with this thing for over 24 hours straight. I think I missed one of the boot images when I was trying to flash back to stock NAE. Now it doesn't even turn on. Let's observe a moment of silence for my $500 brick...
Parkourkid93 said:
Not sure what could be causing your issue, I didn't how ever have that problem before tho, what I did was flash a stock ROM & their should be a dailer code used to reset your data (which I forgot, so look around for it, it has been mentioned on a lot of threads, sorry about that), then after dialing the code, your phone should reboot & it should be good, if not try reflashing the correct radio/modem for your android version.
Another thing, you posted this in the wrong section, their is a Q&A section for things like this.
×Rebel Nation×
Click to expand...
Click to collapse
Yeah, I found the dialer code, but anything I put in just gave me a network unavailable, try later message. Here's what I think happened after thinking about it:
I tried to copy a file to the sdcard with windows7. After that, my sdcard became corrupted and unusable. I think this is also when I permanently lost service. The phone is bricked now, so It's to late for me, but I think this is something to watch out for.
r0ckstar said:
Yeah, I found the dialer code, but anything I put in just gave me a network unavailable, try later message. Here's what I think happened after thinking about it:
I tried to copy a file to the sdcard with windows7. After that, my sdcard became corrupted and unusable. I think this is also when I permanently lost service. The phone is bricked now, so It's to late for me, but I think this is something to watch out for.
Click to expand...
Click to collapse
Can you get it to download mode? You should be able to Odin it back to stock. This phone is very resilient to get it bricked.
Sent from my SPH-L720 using XDA Free mobile app
elfeo0 said:
Can you get it to download mode? You should be able to Odin it back to stock. This phone is very resilient to get it bricked.
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Nope. Boot is gone, recovery is gone, and yes, download mode is gone. It was resilient, but it's met it's match.
r0ckstar said:
Yeah, I found the dialer code, but anything I put in just gave me a network unavailable, try later message. Here's what I think happened after thinking about it:
I tried to copy a file to the sdcard with windows7. After that, my sdcard became corrupted and unusable. I think this is also when I permanently lost service. The phone is bricked now, so It's to late for me, but I think this is something to watch out for.
Click to expand...
Click to collapse
super late reply, i apologize, but damn :/, thats pretty depressing, i remember when i bricked my first phone, bricked it the first day i got it -.-, hopefully you can somehow either get it replaces or repaired
Parkourkid93 said:
super late reply, i apologize, but damn :/, thats pretty depressing, i remember when i bricked my first phone, bricked it the first day i got it -.-, hopefully you can somehow either get it replaces or repaired
Click to expand...
Click to collapse
Sprint cut me some slack on a swap out unit, but now of course I'm stuck with knox. I suppose it could have been worse. I'm not going anywhere near any more nightlies. There are some JTAG flash boxes that could have unbricked the phone, but those are just not in my budget at the moment. I haven't killed enough phones to justify that expense.
r0ckstar said:
Sprint cut me some slack on a swap out unit, but now of course I'm stuck with knox. I suppose it could have been worse. I'm not going anywhere near any more nightlies. There are some JTAG flash boxes that could have unbricked the phone, but those are just not in my budget at the moment. I haven't killed enough phones to justify that expense.
Click to expand...
Click to collapse
The same thing happen to me, ended up with the Knox, even tho in told the sprint guy to not update it for me, but its alright, good think you got to swap tho & I agree, I've been planning on buying one but didn't feel like paying
So what is the answer to this problem? I have the same issue. A few day ago, I was on "Sonic 4.4.4 Weekly" and all was good, this is an awesome ROM. But then I got wind that Sacs v5 was up. And being a "Diehard Sac'ien / Flashaholic".... I was sporting it yesterday and notice that I had no service....... I just spent all day fixing my brick.... I am currently back to full stock NAE with F'n Knox mocking me every reboot....
I am pretty thorough with seeing these things through, so I will report back with any info that can be helpful...
By the way I finally got back to Stock NAE using Odin3 v3.09 which I have shared from my "4Shared" account. And the ROM from Sam Mobile Site
We shall prevail....:fingers-crossed:
Problem Solved...
Wow I just figured it out. So simple that I am pretty pissed, but not as upset that as r0ckstar is going to be.
Settings; More Networks;Mobile Networks;Network Mode; and Select "Automatic".
Nothing was selected on my phone.
All is working now.... :victory:
I hope this works for others too.
If I have helped in any capacity please hit the Thank You button....:good:
As I am wiping the Sweat off my Balls.... I mean my Brows... As an Electrician, I sure thought I was going to be Brick Layer-er today....
bigbry87 said:
Problem Solved...
Wow I just figured it out. So simple that I am pretty pissed, but not as upset that as r0ckstar is going to be.
Settings; More Networks;Mobile Networks;Network Mode; and Select "Automatic".
Nothing was selected on my phone.
All is working now.... :victory:
I hope this works for others too.
If I have helped in any capacity please hit the Thank You button....:good:
As I am wiping the Sweat off my Balls.... I mean my Brows... As an Electrician, I sure thought I was going to be Brick Layer-er today....
Click to expand...
Click to collapse
Well, I would like to think that I tried the automatic setting during my frantic flashing rampage, so I'll just smile painfully and pretend I did, because the alternative would be to go postal. I usually roll my eyes and immediately dismiss anything that has "automatic" or "smart" in the name. Perhaps I'll give these settings the benefit of the doubt just one more time... next time.
This is actually you efs partition somehow being either a. Overwritten or b. Getting corrupted. Your efs is all yourBaseband, meid, min, prl, phone#, imea, iccid info. And ive had this exact problem. Flashing a backup of my efs fixed in 2 seconds. Hope this helps future problems. Always remember to backup your efs people.. sources... http://forum.xda-developers.com/showthread.php?t=2329937
And... http://forum.xda-developers.com/showthread.php?t=2019540
Daisflaque said:
This is actually you efs partition somehow being either a. Overwritten or b. Getting corrupted. Your efs is all yourBaseband, meid, min, prl, phone#, imea, iccid info. And ive had this exact problem. Flashing a backup of my efs fixed in 2 seconds. Hope this helps future problems. Always remember to backup your efs people.. sources... http://forum.xda-developers.com/showthread.php?t=2329937
And... http://forum.xda-developers.com/showthread.php?t=2019540
Click to expand...
Click to collapse
Yes, I believe this must be the conclusion. If you think you're playing it safe by doing a "nandroid" backup that doesn't include the efs partition, you're not. Also, there are some problems with this blurb about backing up the efs partition. It doesn't apply to the gs4. The procedure would have to be modified. Secondly, it says to back it up on the sd card. I lost the sdcard and the efs partition at the same time, so the first thing to go would have been the efs backup. It needs to be taken off the phone and put somewhere else for safe keeping. Ideally, an odin flashable image should be created and stored away on the computer, but I'm not aware of any way to do that. Perhaps with the simg2img or make_ext4fs utils? I've never attempted it, and of course I would be very nervous about testing it as well
For future reference I helped someone out with this issue who was on the L720T. I had him send me his m9kefs partition numbers and created a hex file the exact same size as those partitions (the file I created had all zeros in it) and attached a batch file along with it. It injected this file into his phone and he had baseband, imei, meid and everything else back. You can find this particular situation in Alpinemans thread on flashing phones to different carriers.
Sent from my SPH-L720 using XDA Free mobile app
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
r0ckstar said:
Yes, I believe this must be the conclusion. If you think you're playing it safe by doing a "nandroid" backup that doesn't include the efs partition, you're not. Also, there are some problems with this blurb about backing up the efs partition. It doesn't apply to the gs4. The procedure would have to be modified. Secondly, it says to back it up on the sd card. I lost the sdcard and the efs partition at the same time, so the first thing to go would have been the efs backup. It needs to be taken off the phone and put somewhere else for safe keeping. Ideally, an odin flashable image should be created and stored away on the computer, but I'm not aware of any way to do that. Perhaps with the simg2img or make_ext4fs utils? I've never attempted it, and of course I would be very nervous about testing it as well
Click to expand...
Click to collapse
There seems to be a lot of confusion around the EFS. The EFS is not contained in the EFS partition ironically...its actually split across three partitions on the L720. These would be the m9kefs. On some other phones its on the modemst partitions and FSG. So to recap if youve backed up the efs folder/partition...its a nearly useless backup. Ive ran a G900P with no EFS folder/partition. Worked perfectly fine. However if you're missing your REAL efs partitions...your phone will be working perfectly not fine lol.
Sent from my SPH-L720 using XDA Free mobile app
Uh huh... that sir made more sense than it should have. Lol
EFS partition names
ecs87 said:
For future reference I helped someone out with this issue who was on the L720T. I had him send me his m9kefs partition numbers and created a hex file the exact same size as those partitions (the file I created had all zeros in it) and attached a batch file along with it. It injected this file into his phone and he had baseband, imei, meid and everything else back. You can find this particular situation in Alpinemans thread on flashing phones to different carriers.
Sent from my SPH-L720 using XDA Free mobile app
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
There seems to be a lot of confusion around the EFS. The EFS is not contained in the EFS partition ironically...its actually split across three partitions on the L720. These would be the m9kefs. On some other phones its on the modemst partitions and FSG. So to recap if youve backed up the efs folder/partition...its a nearly useless backup. Ive ran a G900P with no EFS folder/partition. Worked perfectly fine. However if you're missing your REAL efs partitions...your phone will be working perfectly not fine lol.
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Ahhhhhh...........
I see what you're talking about:
mmcblk0p13 (m9kefs1) 0 MB, 798720 bytes
mmcblk0p14 (m9kefs2) 0 MB, 798720 bytes
mmcblk0p15 (m9kefs3) 0 MB, 798720 bytes
They're so obscure and less than 1M each, but apparently oh so important
while these...
mmcblk0p10 (efs) 14 MB, 14286848 bytes
mmcblk0p11 (modemst1) 3 MB, 3145728 bytes
mmcblk0p12 (modemst2) 3 MB, 3145728 bytes
mmcblk0p24 (fsg) 3 MB, 3145728 bytes
are simply diversions for chumps.
Duly noted.
r0ckstar said:
Ahhhhhh...........
I see what you're talking about:
mmcblk0p13 (m9kefs1) 0 MB, 798720 bytes
mmcblk0p14 (m9kefs2) 0 MB, 798720 bytes
mmcblk0p15 (m9kefs3) 0 MB, 798720 bytes
They're so obscure and less than 1M each, but apparently oh so important
while these...
mmcblk0p10 (efs) 14 MB, 14286848 bytes
mmcblk0p11 (modemst1) 3 MB, 3145728 bytes
mmcblk0p12 (modemst2) 3 MB, 3145728 bytes
mmcblk0p24 (fsg) 3 MB, 3145728 bytes
are simply diversions for chumps.
Duly noted.
Click to expand...
Click to collapse
Haha you've pretty much got it BUT those other partitions aren't really diversions. Modemst1, 2 and FSG DO contain some of the NV. What's in them really isn't known since it's encrypted but...I can say that the read only protection on the GSM Qualcomm devices' IMEI is contained in there. The EFS partition itself... Does seem to be for chumps lol. It does have its purpose, but there doesn't seem to be any kind of important information in there. There however is a new flag that will trigger the carrier animation on boot for the G900P. Very miniscule...
In my opinion A) the EFS and NV items are more of a black magic kind of thing where not a lot of people know about it and even less know that its actually spread across partitions on their device. B) the tools and documentation we have to access them are very limited and outdated. A lot of what I've learned about the EFS and NV items has been self taught. There's been a few hard bricked phones...
Sent from my SPH-L720 using XDA Free mobile app
Late but better than never?
r0ckstar said:
Nope. Boot is gone, recovery is gone, and yes, download mode is gone. It was resilient, but it's met it's match.
Click to expand...
Click to collapse
Hi, know this thread is a couple of years old but wanted to ask if you tried to get the phone back up using the tflash option in odin.
If you kill all partitions on your phone like boot recovery and so on or have messed up your emmc storage there is one option you can try to fix it. Basically you take a memory card equivalent in size to your phone internal memory. You then download the full stock firmware for the phone and here's the hard part you need the same phone as yours in which you pop in the memory card and let odin identify and connect and show added. Now go to the options and untick auto reboot and tick the tflash option. Now go to the pit file section and choose the correct pit file for your phone and model /variant.
You can then click on start after having chosen the correct firmware file for each section marked BL, AP, CP, CSC. Once flashing is done. Odin will show reset and you can disconnect the phone and shut it down then take out the memory card and put it in your bricked phone. Odin will basically have flashed your phone partitions on the memory card and mmadeitbootable and on powering on your device should boot boot up normally and will create the partitions on Emmc itself. To make sure you can also turn on USB debugging from Dec options that you can activate by tapping on build no 7 times in the software info screen. You can refresh the phone now as you will have the PC recognize it.
I recently did this to revive a note edge that had died and found odin had created about 32 or more partitions on my micro SD with 32gb capacity. The number was unbelievable as we never get to see that many partitions but apparently the phone does need and have them all as it all worked and brough 4th a dead SM-N915G back to life.
Hope it helps.
Related
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 ?
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,
Phone restarts automatically with no imei and unknown baseband, I download stock firmware 4.4.2 and install on it but same situation,
any suggestion or help pls,
thanks
br
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Elite49 said:
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Click to expand...
Click to collapse
imei is unknow
2 Choices
nsnobel2 said:
imei is unknow
Click to expand...
Click to collapse
Hi
I don't know if you've fixed your issue with your g900v or not, but i have the same problem and the same phone and obviously the same symptoms ...
As far as I've tried, nothing worked not ODIN flashing ROMs, or QPST to write IMEI or EFS professtiona ADB .... etc.
What I've come to know is this :
1- keep the phone in a safe place till next months reveal a solution through developers here or elsewhere.
2- Flash the Original Samsung Verizon Rom ( Full Package with efs and bootloader mounts and all partitions " Clean Flash" ) which costs about 100$ .
3- Change the board for a (200$) new one .
So, I would try to pay the 100$ and flash the original ROM, and comeback to tell if it solved the Problem.
I wish if you share any different approach or feedback . I would love to hear it .
Bye
It could possibly be that your EFS folder is damaged. This is where your IMEI and Baseband info is stored. If that's the case for your device, these steps should work. I've done this on two phones (one being an S5) and it fixed this problem.
I'm assuming that you're rooted. If not then you'll need to root your device first. And you need to have debugging enabled. What this does is backups the files from the EFS folder, repairs the partition tables, then restores the files to the repaired folder.
1. Connect the phone to your computer. (Windows)
2. Download this: https://www.dropbox.com/s/v2h5dzisjd0rgj5/EFS_Professional_2.1.73_Release.zip?dl=0
3. Extract and run the program
4. Click EFS Professional... It will open a window showing that it found your phone
5. Click on the Backup Tab and make sure all of the partitions are checked, and your Device Filter is recognized
6. Hit the Backup button to backup the EFS folder
7. After that's done, click the Restore button and it will restore your files to the EFS folder.
I hope this helps you.
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
joshw0000 said:
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
Click to expand...
Click to collapse
Was it a tool specifically for the Note 2, or multiple Samsung devices, or maybe a universal program like CDMA Workshop? I love that program. It's what I use when it comes to actually entirely rewriting files like this. Most of the time a full rewrite isn't needed though if the EFS folder has just been damaged. Which "damaged" is totally the wrong word here, but that's what it's called for some reason. I really don't even know how it happens, but I do know when it does, it usually just jumbles and/or fragments the info in the folder and needs to be put back in it's correct order. Kind of like defragging in Windows. Just a tool like you're talking about would definitely be cool for me to have though. I shall start my quest to find it. Lol
Please some help
Any luck yet ???
Got the same issue here, and none of the threads here worked .
Same problem
Hello,
I have the exact same problem. I bought the phone here in Mexico, and the phone came with erased EFS folder. Phone restarts automatically when screen turns off. When I'm using the phone, it works just fine, but some seconds after screen goes off, phone restarts automatically. EFS folder is messed up, I've tried out a lot EFS restoring tools with no luck.
I tried QPST but it does not detect the phone, only appears "?" and "No phone" blinking. The same happens with DFS Tool.
I will try to look for that tool joshw0000 talks about.
I hope we can find out a solution for this excellent phone.
Bye.
Hey ...
I did a factory reset and cache wipe, and now the phone stopped restarting when the screen goes off, but still got the "Unknown" issues.
But at least I got rid of the annoying restarts.
570 ppl read this and still no answer, I got to admit ... it's tough.
Sent from my SM-G900V using XDA Free mobile app
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?
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