Database Develop

[Q] Emergency Calls Only after CM install?

I've spent the last few days trying to figure this out without any luck. I have GT-S5830D (Canadian Koodo version) on stock firmware TLKI4, unlocked with SpeakOut sim (which operates on Rogers network).
Android Version: 2.3.4
Baseband Version: S5830DTLKI4
Kernel Version: 2.6.35.7-perf-CL568978 [email protected] #1
Build Number: GINGERBREAD.DTLKI4
PDA: S5830DTLKI4
PHONE: S5830DTLKI4
CSC: S5830DTLSKI4
In this stock firmware, I have no issues at all. Everything works fine, can place calls, WIFI, GPS, data all works. If I flash a new rom to the phone, I can see the networks still show up with signal strength showing okay, but the phone will not place calls. Just says Emergency Calls Only.
I've been reading about everything I can about this phone, and I just can't figure out what the problem is. I have flashed the modem with DDKQ7 and I was able to again place calls, however with this modem firmware, the connection was very unstable and would drop frequently.
Is there an issue with directly updating the stock rom to CM7 or CM9 that would cause problems with this baseband? I was under the impression that baseband wasn't really important. Interestingly enough, I have another phone that is the same make and model and is not experiencing this problem. I feel there must be something I am missing, if anyone can shed some light on this, I would appreciate it.
Thank you.

I have a feeling that I may be the only person that has experienced this issue. Continuing to search the internet for other answers, I've discovered that the baseband is the cause of this issue, but I still don't quite understands how it relates. My other phone is on the stock firmware (TLKI4) and is running CM7 without issue, on the same network even.
Do the APN settings have effect on voice calls too? Or is it strictly for data?
Also, I read a post on here that sounded like there was a limit to how many times you can perform a complete flash with Odin? Is that true? I'd love to keep experimenting, but each time to roll back the stock firmware, I need to use Odin and I'm hesitant due to the thought that will eventually brick the phone.
Thanks again.

tried to flash cm7 again??

Yes. I have installed cm-7.2.0-cooper.zip as well as some of the nightly's and still only get emergency calls only. I have another phone, exactly the same setup, and it works without issue. I even tryed GalaxyICS-latest and the same problem.
Now I did install a different modem firmware, and performed the upgrade and I don't have the issue anymore, however I have other issues, dropped service, 3g doesn't work properly, wifi and mobile data won't switch, gps is has extremely long lock time if it locks at all.
Does anyone here have the D version of this phone from Koodo? Which modem firmwares are you using? Anyone specifically using the phone on SpeakOut? Any hints would be helpful because I'm completely at a loss, will just have to keep it stock until I can figure it out.

I had the same problem as you, don't worry though because there is a solution. The Koodo Samsung Galaxy Ace only receives a signal when using the original Koodo baseband. (Basebands have to do with wireless signal, sometimes referred to as modems.) The good thing for you is that you can use any ROM or firmware you like, as long as after installing it you flash the original Koodo baseband (S5830DTLKI4) using Odin. I found a download link for the baseband in this thread: http://forum.xda-developers.com/showthread.php?t=1381595
After downloading, (I'm assuming you know how to use Odin, if not you can find a guide easily) open Odin, and in the "Phone" section browse to the file and select it. (You will have to extract the ZIP) Then press start and wait until it is finished downloading and that should do the trick. If you need any more help post back because I know what a pain it is to try and get this particular phone rooted and install a custom ROM.
ALSO MAKE SURE TO BACKUP IN CLOCKWORK MANAGER BEFORE FLASHING THIS
cause you never know what can happen.

If I flash CM7, it still shows my baseband being the same. It doesn't appear to have been changed. So what I need to do is flash CM7 and then just reflash the baseband with Odin and it should work? Even though the baseband shows the same? I'll give it a shot and let you know how it works out, but does anyone know why this would be required, to have to reflash the baseband even though it was never changed?

Is your current baseband S5830DTLKI4? Because in my experience that's the only way I could get service unless I was on the Koodo stock ROM.
Sent from my GT-S5830 using XDA

Yes, that is the firmware that I'm on. That firmware was installed with the stock rom that the phone came with and I have not changed it. Although I have changed it before, it fixed the issue with getting 'emergency calls only' in CM7 but the service was so flaky it wasn't worth keeping as a solution. If I leave the firmware from stock DTLKI4 and flash CM7 over it, I end up getting stuck with emergency calls only problem.
Is the current official CM7 not compatible with DTLKI4 firmware? Could that be the problem I'm having? I'm still really confused why this isn't working, but I will try to install CM7 again, and then use Odin to flash the DTLKI4 on top to see if the install is causing any issue with it. It doesn't really make sense.

Alright, interestingly enough, I just flashed it again and all is working as expected. I've flashed this phone about 10 times, using the same files and it would not work.
This time however, what I did differently is not root the phone. I've been using the universal_gb_root_v20.zip to root the phone previously, but I found that rooting before installing CM is waste of time as root is enabled in the CM7 rom already.
Also, when I flashed the stock rom with Odin, it usually used selected the KDO CSC automatically, last time I flashed it came up with TLS CSC and had the Telus branding. I don't know if that made any difference. All I know is that it worked and I am able to make calls and use data without any problems.
Thank you Dynamic_Apple, although your recommendation was not required, it did give me the motivation to try again and that was enough to get it working. I've never had so much difficulty modding a phone in my life, especially a model that I have messed with before.

Glad I was able to help, I had just as much trouble getting mine modded too, it makes me jealous of all the generic Galaxy Ace owners, but it's good to know that you can actually get past Koodo's sneaky limitations.

ATT blocked my device

So, just a heads up guys (and gals); it looks like ATT blocked my device (reported it stolen) and now I'm locked out of the wireless network.
I still need to call them to see if I can resolve this issue, but it happened after I flashed the latest nightly CM10 and was running it all weekend with no problems, wake up this morning and I can't text, get no data. Try making a call and it states; "This device has been blocked". After using Google, that message is one that happens when a device is reported stolen.
Since I've had this device for it's entire life, there is no chance someone else reported it stolen.
I'll keep this thread updated with what ATT does, if they re-enable my device, etc.

Somebody else had this happen to them on CM10, and it was because their IMEI became generic overnight. You can read about it in the Helly Bean thread.

korockinout13 said:
Somebody else had this happen to them on CM10, and it was because their IMEI became generic overnight. You can read about it in the Helly Bean thread.
Click to expand...
Click to collapse
Huh. How does it overwrite the IMEI on it's own?
I did have a backup of my IMEI from last october (the entire EFS folder) I used ES File explorer to copy it over... But forgot to fix permissions... SLAP forehead.
(Fixed Permissions)
Now I'm back on ATT, guess it wasn't there fault.
:cyclops:

So after reading the other thread, I have to wonder if changing /System to RO mode (via SGS Toolbox) will prevent the EFS folder from being overwritten again? Or am I going to run into this again? The problem seems pretty clear, the EFS folder for some reason has R/W privileges, when it should be RO.
The second part of the equation, is _what_ in JB is deleting that folder?

scythekain said:
So, just a heads up guys (and gals); it looks like ATT blocked my device (reported it stolen) and now I'm locked out of the wireless network.
I still need to call them to see if I can resolve this issue, but it happened after I flashed the latest nightly CM10 and was running it all weekend with no problems, wake up this morning and I can't text, get no data. Try making a call and it states; "This device has been blocked". After using Google, that message is one that happens when a device is reported stolen.
Since I've had this device for it's entire life, there is no chance someone else reported it stolen.
I'll keep this thread updated with what ATT does, if they re-enable my device, etc.
Click to expand...
Click to collapse
This same exact thing happened to me, but I'm on CM9 Stable... Still trying to figure out why my IMEI is the generic one...

I had this happen to me also,,and when I called att customer service they told me that the emei belonged to an iphone that was stolen,,in my case this actually happened three times,,I finally flashed back to stock to reset the emei and it seems to be holding,, I was running helly bean v24 and had been on the rom for a day or something ( well since that version came out ) in fact I have two captivate handsets and one was on v23 and they both switched the emei to the same one,,I have no idea what caused the emei to change but it sure caused some hair pulling on my part lol,, all seems well now

wilson735 said:
This same exact thing happened to me, but I'm on CM9 Stable... Still trying to figure out why my IMEI is the generic one...
Click to expand...
Click to collapse
Same here, but on CM 7.2.0 RC2. I'm not sure if the IMEI just now changed or if it was this way since I flashed CM and AT&T is now cracking down.

The above posts, kind of confirm what I'm sensing is ATT doing something that flashed a stolen IMEI onto rooted android devices.
1) What was the timing of your problem? - For me this happened yesterday morning, or Sunday night after 9 PM PST. I restored my IMEI about 9 AM, and the service restored itself around 13:32 8/20/2012 PST
2) It makes me wonder IS this the custom ROM that changed the IMEI to a stolen iPhone? Why would the ROM choose an iPHONE IMEI? I think this was pushed by ATT. Was it a mistake or was it intentional? Proof? CM 7.2, CM9, CM10 and HellyBean (which is based on CM10 with custom kernel, partitioning). ALL of them set the IMEI to the stolen iPhone THIS last weekend though?
For those of you still needing to restore your IMEI and you don't have a backup, use this thread;
http://forum.xda-developers.com/showthread.php?t=881162
EDIT:
You can also flash back to stock via ODIN to restore your IMEI.

So it looks like the CM10 flash I did Saturday did muck up my IMEI. I was logging into the Google Play store to try and restore my apps from the web, and found out I have two captivates registered.
One with the correct IMEI, the other with this bogus IMEI:
IMEI: **********640000

Here's the whole story:
On Sunday, in the course of 5 hours: 3 times AT&T blocked my device, I called them and got in unblocked. In one of those times, the guy says that the system logs say that my sim card was in an iPhone 3gs that was reported stolen. They also credit me with $25 for each of the 1st 2 times I called.
Anyway, on the 3rd time I ask to speak to a floor supervisor. She is able to tell me that because my phone is reporting an IMEI of a stolen phone, she'll forward it to the Stolen Devices team/department, and that they would get back to me on Tuesday. She can unblock it again on the spot, but eventually it'll get read by the system and blocked again.
I confirm with her that the IMEI that my phone software is showing is the Generic one (004999010640000), and not my actual one that I read to her from underneath the battery.
I was reading through the forums all day on Monday and came to the following conclusions:
1) That Generic IMEI may be what a ROM is mistakenly putting in place, it must use this as a failsafe of some sort, so it can have an IMEI, any IMEI. In reality it should be reading the hardware's IMEI.
2) Our IMEI's did not necessarily get changed this weekend. Last time I flashed, it was when CM9 Stable was released, and that was a couple of weeks ago. So, we may have had this IMEI for weeks, if not months. I know I may have. 1 month ago, my phone got blocked. They said that someone reported it stolen. I called, got my $25 credit, and the service reinstated. I may have had that Generic IMEI at the time.
Last night a technician from the Stolen Devices team instructed me to remove my SIM card from the device for 24 hours so that the network can refresh the IMEI (his exact words, I don't know exactly how the network works, but...) and that this was necessary. Yes, I could ignore him and put by SIM card back into my Captivate, but eventually it would get blocked again. So leave it out of the Cappy, he said, use it in any other device, and after 24 hours you can slip it back in. He said that recently (in the past day or two), many users had been calling about the same problem.
Anyway, just to be on the safe side, I'll be following fohdeesha's instructions here:
http://forum.xda-developers.com/showpost.php?p=30563493&postcount=1780
Flashing back to stock 2.3.5, and seeing if I can get the correct IMEI. If so, I'll backup that EFS folder in 10 different places, revert back to ICS or JB, and if the IMEI is messed up there, I'll restore my EFS backup.

wilson735 said:
Here's the whole story:
On Sunday, in the course of 5 hours: 3 times AT&T blocked my device, I called them and got in unblocked. In one of those times, the guy says that the system logs say that my sim card was in an iPhone 3gs that was reported stolen. They also credit me with $25 for each of the 1st 2 times I called.
Anyway, on the 3rd time I ask to speak to a floor supervisor. She is able to tell me that because my phone is reporting an IMEI of a stolen phone, she'll forward it to the Stolen Devices team/department, and that they would get back to me on Tuesday. She can unblock it again on the spot, but eventually it'll get read by the system and blocked again.
I confirm with her that the IMEI that my phone software is showing is the Generic one (004999010640000), and not my actual one that I read to her from underneath the battery.
I was reading through the forums all day on Monday and came to the following conclusions:
1) That Generic IMEI may be what a ROM is mistakenly putting in place, it must use this as a failsafe of some sort, so it can have an IMEI, any IMEI. In reality it should be reading the hardware's IMEI.
2) Our IMEI's did not necessarily get changed this weekend. Last time I flashed, it was when CM9 Stable was released, and that was a couple of weeks ago. So, we may have had this IMEI for weeks, if not months. I know I may have. 1 month ago, my phone got blocked. They said that someone reported it stolen. I called, got my $25 credit, and the service reinstated. I may have had that Generic IMEI at the time.
Last night a technician from the Stolen Devices team instructed me to remove my SIM card from the device for 24 hours so that the network can refresh the IMEI (his exact words, I don't know exactly how the network works, but...) and that this was necessary. Yes, I could ignore him and put by SIM card back into my Captivate, but eventually it would get blocked again. So leave it out of the Cappy, he said, use it in any other device, and after 24 hours you can slip it back in. He said that recently (in the past day or two), many users had been calling about the same problem.
Anyway, just to be on the safe side, I'll be following fohdeesha's instructions here:
http://forum.xda-developers.com/showpost.php?p=30563493&postcount=1780
Flashing back to stock 2.3.5, and seeing if I can get the correct IMEI. If so, I'll backup that EFS folder in 10 different places, revert back to ICS or JB, and if the IMEI is messed up there, I'll restore my EFS backup.
Click to expand...
Click to collapse
Good information. I've restored my EFS from a backup I made last october when I first rooted and flashed CM7.
Not sure what leaving the SIM out does? Does it correct the IMEI folder on it's own?

Sooo, I ended up having this situation for first time last night.
What I did was:
1) One click kk4 stock
2) Flash Devil's kernel to get CWM
3) Flash Helly Bean 8/13.
4) Flash ugjk4 modem.
Bam wrong IMEI.
Did the whole thing again, this time using ugjk3 modem - bad IMEI again.
Then I just copied back my efs folder, chown to radio:radio, chmod to 0700 and reboot - IMEI got fixed.
What is really shady is when is this happening? After the initial devil kernel flash? Or the initial helly bean flash when it does the partitions and reboots you back into recovery?

scythekain said:
Good information. I've restored my EFS from a backup I made last october when I first rooted and flashed CM7.
Not sure what leaving the SIM out does? Does it correct the IMEI folder on it's own?
Click to expand...
Click to collapse
Leaving the SIM card out cannot change, reset, or fix your imei, it can't effect it at all.
Leaving the sim card out simply blocks your phone from being able to "phone home" to att, and report the incorrect imei to att. Because when att sees this, that is when they block your device.
This is why I suggested in other posts that when you are flashing a new rom, leave your sim card out. This way if the rom flash does reset your imei, you can repair it and THEN put your sim card back in, without the phone automatically phoning home to att with the wrong imei right off the bat and getting your phone blocked

Ok I have a quick question. I copied my entire EFS folder and copied it into my external SD card. Do I need to do anything else to back it up? I have the correct IMEI and want to make sure it stays that way. I noticed one person mentioned the need to fix permissions. Is that all I need to do. Thanks.

I would make a copy and put it on ur computer as well.
Sent from my SAMSUNG-SGH-I897 using xda premium

Has this been figured out yet? Anyone have any idea why this is happening to some people and not others? What's the common factor here? After several initial failed flash attempts I went from one click froyo, to several cm9 nightlys, to hellybean 8/13 , to cm10 nightly 8/18, to cm10 nightly 8/22. So far I've had zero imei issues. My number still matches the back of the phone. Is this something att is sending out, an app, or one of the ROMs being flashed? I just checked and the permissions for my efs folder are set to rwx r-x r-x. It may help if everyone lists their history.
Sent from my SGH-I897 using xda app-developers app

rickneworleansla said:
Has this been figured out yet? Anyone have any idea why this is happening to some people and not others? What's the common factor here? After several initial failed flash attempts I went from one click froyo, to several cm9 nightlys, to hellybean 8/13 , to cm10 nightly 8/18, to cm10 nightly 8/22. So far I've had zero imei issues. My number still matches the back of the phone. Is this something att is sending out, an app, or one of the ROMs being flashed? I just checked and the permissions for my efs folder are set to rwx r-x r-x. It may help if everyone lists their history.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
1) I used one click root, to root my phone back in October, then backed up my EFS.
2) Odin CM7 CWM.
3) Flashed CM 7.1 stable, got fed up with the /datadata limitation pretty quickly. Tried Miui. (had same problem)
4) November, flashed last available nightly for CM 7.1 (till march of this year) this change the structure of /datadata to have about 400 Megs and to warn when it's getting full.
5) January, started flashing nightly kangs weekly.
6) Mid March, flashed CNA 4.0.3 - Horribly laggy.
7) Flashed AOKP, CM9 nightlies etc. Ended up sticking with CM9 nightlies.
8) 8.18 flashed CM9 nightly.
9) 8.18 flashed UXKH2 modem (awesome voice quality)
10) 8.20 no wireless data/signal - device blocked.
According to the Google Play store, the incorrect IMEI was registered on Monday. Which means something deleted it Sunday night Monday morning while I was sleeping.
(if you want to you can view your account history and registered devices here
https://www.google.com/dashboard/

IMEI
this recently happened to me over the weekend. I simply flashed back to stock KK4 and i had my IMEI number back to what its supposed to be. I never had to call AT&T to unblock it. once I got my IMEI back, I flashed a custom corn kernel and installed root. while I still had the original IMEI I downloaded an app called Galaxy S Unlock and in this app there is an option to back up only your efs folder and its contents. after making two back ups I decided to flash the latest Helly Bean from Der Teufel whilst leaving my SIM out. once all was said and done I still had my stock IMEI number with CM10 Helly Bean. the only number that I notice changed is the IMEI SV. it went from 00 at stock KK4 to 05 on cm10. I don't know what that number represents but it doesn't seem to affect me. good luck to anyone with this issue.

cheeesboiger said:
this recently happened to me over the weekend. I simply flashed back to stock KK4 and i had my IMEI number back to what its supposed to be. I never had to call AT&T to unblock it. once I got my IMEI back, I flashed a custom corn kernel and installed root. while I still had the original IMEI I downloaded an app called Galaxy S Unlock and in this app there is an option to back up only your efs folder and its contents. after making two back ups I decided to flash the latest Helly Bean from Der Teufel whilst leaving my SIM out. once all was said and done I still had my stock IMEI number with CM10 Helly Bean. the only number that I notice changed is the IMEI SV. it went from 00 at stock KK4 to 05 on cm10. I don't know what that number represents but it doesn't seem to affect me. good luck to anyone with this issue.
Click to expand...
Click to collapse
The "SV" is the Software version, it doesn't affect your IMEI (your device identifier).
http://imeimobile.blogspot.com/2009/11/structure-of-imei-and-imeisv.html

Your sim card has been blocked after put in the lose/stollen AT&T phone .
Your sim card has been blocked after put in the lose/stollen AT&T phone .

[Q] Possible to fix missing baseband, IMEI, and SIM card errors?

I recently bought a for parts Captivate off of Ebay, Description saying the unit would only power on and that the touchscreen wasn't working.
I looked at the photos and determined that it must be a hardware malfunction, I have some spare parts to try and see what I could do.
(since my previous cappy fried after a botched job re-applying the unbrickable mod that had worked once before)
I receive the phone, in near new condition, no battery and dented back cover, and I thought "okay, no problem" and got to work trying see what was wrong exactly
I was unable to determine what android revision since I would reboot after lockscreen, so I flashed it with various roms, including AOCP 2.2, Slim Bean and at&t GB's that had been rooted with odin and cwm for slim bean and aocp and cm10
So the following symptoms happen based on which android revision I use
2.1 stock
- phone reboots seconds after the phone has booted to the touchwiz lockscreen, touch screen has no response, I can't say it's 2.1 definitely but could be since every other rom works fine except any signal or data other than wifi
2.2, 2.3.X and all the way to 4.1.1
- SIM card detection - does not warn of missing sim or bothers to detect once inserted
- IMEI is unknown other than the one on the sticker, which is in one piece
- Baseband is unknown even if I flash a modem
I've replaced the sd card/sim card daughter board that also connects the loud speaker to the mainboard. Still nothing. at least the sd card and speaker work.
So... any ideas or should I use this phone like a Galaxy player minus the front camera?

Gizoid1337 said:
I recently bought a for parts Captivate off of Ebay, Description saying the unit would only power on and that the touchscreen wasn't working.
I looked at the photos and determined that it must be a hardware malfunction, I have some spare parts to try and see what I could do.
(since my previous cappy fried after a botched job re-applying the unbrickable mod that had worked once before)
I receive the phone, in near new condition, no battery and dented back cover, and I thought "okay, no problem" and got to work trying see what was wrong exactly
I was unable to determine what android revision since I would reboot after lockscreen, so I flashed it with various roms, including AOCP 2.2, Slim Bean and at&t GB's that had been rooted with odin and cwm for slim bean and aocp and cm10
So the following symptoms happen based on which android revision I use
2.1 stock
- phone reboots seconds after the phone has booted to the touchwiz lockscreen, touch screen has no response, I can't say it's 2.1 definitely but could be since every other rom works fine except any signal or data other than wifi
2.2, 2.3.X and all the way to 4.1.1
- SIM card detection - does not warn of missing sim or bothers to detect once inserted
- IMEI is unknown other than the one on the sticker, which is in one piece
- Baseband is unknown even if I flash a modem
I've replaced the sd card/sim card daughter board that also connects the loud speaker to the mainboard. Still nothing. at least the sd card and speaker work.
So... any ideas or should I use this phone like a Galaxy player minus the front camera?
Click to expand...
Click to collapse
There could be a lot of things wrong with it since you are at least the second owner and don't know the full extent of possible damage.
But lets assume all things are functional but calls and data. I do want to clarify though, other than the 2.1(?) flash your screen responds as normal? If so try getting a one-click version of 2.2 and flashing it back to stock. Then just for good measure download Kies, which is Samsungs official firmware update client. It should take you to 2.3(Gingerbread). Now is the time to go into your phone settings and check your IMEI. Make sure it matches what's under the battery. Hopefully reverting back to stock with official software will restore your IMEI.
I've personally never had my IMEI get screwed up during a flash but after reading countless posts, and responses regarding the issue it seems that a lot of time if you are missing your IMEI the baseband version will show unknown as well. As for not showing a missing SIM warning I am at a loss but those are the best steps I can tell you to take in an effort to recover your IMEI.
Also if the above steps get you back in business make sure you do a backup of your /efs folder before moving ahead with any other flashing of ROMs to avoid a possible repeat of the same issues.

I'll give kies a try after downgrading, thanks

Kies says connecting... and then after maybe 5 - 10 minutes later says could not gather info on GT-i9000.

Gizoid1337 said:
Kies says connecting... and then after maybe 5 - 10 minutes later says could not gather info on GT-i9000.
Click to expand...
Click to collapse
Hmm well I'm going to say you have i9000 bootloaders installed on your cappy. So Kies is getting confused and can't find the right software for your phone...
You could try doing a Gingerbread one-click with bootloaders for the cappy but you run a serious risk of permanently bricking your phone when you start messing with bootloaders. Of course as it stands you don't have more than an mp3/video player.

My suggestion would be to go ahead and grab one of the stock one-clicks with I897 bootloaders. As long as you don't pull the plug during the 1-2 seconds it's flashing those, you'll be fine. Once you've flashed, if you still can't get it, you can try the /efs repair that's in the development section.
It sounds to me like the SIM card slot could be borked, though. If that's the case, I believe connexion2005 (Josh at mobiletechvideos) offers a service to repair that for a nominal fee. If getting it working as a phone isn't a big deal, then you can just ignore the SIM slot repair and get one of the Captivate Touch roms and make it a media player.

Hello, back and so far flashing with uckk4 with bootloaders, and uckf1 also with bootloaders, so far same issue, no signal,imei, or baseband

Gizoid1337 said:
Hello, back and so far flashing with uckk4 with bootloaders, and uckf1 also with bootloaders, so far same issue, no signal,imei, or baseband
Click to expand...
Click to collapse
I'm gonna say you're definitely having some hardware issues at this point. Sounds like you have a media player.
Sent from my SGH-I897 using xda app-developers app

I also found that I have no gps when running on UCKB2.
Anybody know where a custom 2.1 rom could be found? having a bit of trouble finding 2.1 custom rom that's odin flashable
Because now /efs is now NOT mountable and empty, good thing I made a efs pro backup, But nv_data.bin is mostly blank in hex workshop. Is that how it supposed to be?
EDIT - nvm about 2.1 roms, anything to fix umountable /efs would be nice, also nice would be if I stopped messing with my phones

Gizoid1337 said:
Hello, back and so far flashing with uckk4 with bootloaders, and uckf1 also with bootloaders, so far same issue, no signal,imei, or baseband
Click to expand...
Click to collapse
i had the same problem the other day what worked for me was leaving the sim card out while flashing the modem, reboot, then shut down and insert sim card.

[Q] After flashing: Network weak, only Edge, no modems work

First time poster, long time lurker, absolute phone novice.
I am using a i9305 (Hong Kong model, bought from Kogan Australia). I am based in Malaysia. Before all this I just popped my sim card in and utilised the stock ROMs. No issues with 4G or network whatsoever, but the phone got really slow after 4.3 to I decided to install CM11 using Heimdall.
Long story short, I absolutely screwed it up, and the phone showed the "software fail" screen. After scouring XDA and undertaking a number of fixes which didn't work (I'm scared this is what screwed my phone), I finally worked out to flash the Hong Kong stock 4.3 ROM using Odin,which brought my phone back to me. However, now I can only pick up Edge and barely get network reception. It is definitely not a sim issue as my sim in my wife's identical i9305 picks up 4G and network within a second of switching on.
I've searched every thread but cannot find an answer which works.I've flashed a whole bunch of modems but to no avail. I hope I haven't screwed my phone. Threads I've utilised include:
http://forum.xda-developers.com/galaxy-s3/help-i9305/s3-lte-i9305-3g-4g-2g-wokring-help-t2246437
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-stuck-edge-3g-lte-t2655315
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-2g-3g-4g-t2847184
I'm at a loss. I haven't factory reset my phone again (yet), but that is a kind of last resort. Does anyone have any suggestions?

kirikee said:
First time poster, long time lurker, absolute phone novice.
I am using a i9305 (Hong Kong model, bought from Kogan Australia). I am based in Malaysia. Before all this I just popped my sim card in and utilised the stock ROMs. No issues with 4G or network whatsoever, but the phone got really slow after 4.3 to I decided to install CM11 using Heimdall.
Long story short, I absolutely screwed it up, and the phone showed the "software fail" screen. After scouring XDA and undertaking a number of fixes which didn't work (I'm scared this is what screwed my phone), I finally worked out to flash the Hong Kong stock 4.3 ROM using Odin,which brought my phone back to me. However, now I can only pick up Edge and barely get network reception. It is definitely not a sim issue as my sim in my wife's identical i9305 picks up 4G and network within a second of switching on.
I've searched every thread but cannot find an answer which works.I've flashed a whole bunch of modems but to no avail. I hope I haven't screwed my phone. Threads I've utilised include:
http://forum.xda-developers.com/galaxy-s3/help-i9305/s3-lte-i9305-3g-4g-2g-wokring-help-t2246437
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-stuck-edge-3g-lte-t2655315
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-2g-3g-4g-t2847184
I'm at a loss. I haven't factory reset my phone again (yet), but that is a kind of last resort. Does anyone have any suggestions?
Click to expand...
Click to collapse
Have you tried wiping your cache in stock recovery (or whatever recovery you have, I can't really tell from your post)? I think you had problems with CM11 since you likely dirty flashed (no wipe of cache, data and system) and used Heimdall instead of flashing it through a custom recovery.

Possible answer
kirikee said:
First time poster, long time lurker, absolute phone novice.
I am using a i9305 (Hong Kong model, bought from Kogan Australia). I am based in Malaysia. Before all this I just popped my sim card in and utilised the stock ROMs. No issues with 4G or network whatsoever, but the phone got really slow after 4.3 to I decided to install CM11 using Heimdall.
Long story short, I absolutely screwed it up, and the phone showed the "software fail" screen. After scouring XDA and undertaking a number of fixes which didn't work (I'm scared this is what screwed my phone), I finally worked out to flash the Hong Kong stock 4.3 ROM using Odin,which brought my phone back to me. However, now I can only pick up Edge and barely get network reception. It is definitely not a sim issue as my sim in my wife's identical i9305 picks up 4G and network within a second of switching on.
I've searched every thread but cannot find an answer which works.I've flashed a whole bunch of modems but to no avail. I hope I haven't screwed my phone. Threads I've utilised include:
http://forum.xda-developers.com/galaxy-s3/help-i9305/s3-lte-i9305-3g-4g-2g-wokring-help-t2246437
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-stuck-edge-3g-lte-t2655315
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305-2g-3g-4g-t2847184
I'm at a loss. I haven't factory reset my phone again (yet), but that is a kind of last resort. Does anyone have any suggestions?
Click to expand...
Click to collapse
When you wipe the whole system to change to another rom, there is always a good chance that you can lose the modem during the process. Rom's may come with their on custom modem , but may not be fully compatible. try to download and flash with odin the modem of the stock rom once again. Your problem is related with the modem

Sorry for not responding, I was in Korea for work and left the bad phone back at home for the past 3 weeks.
I tried the clearing cache, but no good.
I will try flash the stock modem now (see below I notice the difference).
I noticed while syncing my google account that the IMEI on my phone had changed. Would this have anything to do with the issues I am facing? The below is my "before and after".
Model: GT-I9305
Hardware Id: 354720053386061
Android Version: 4.3
Build Number: JSS15J.I9305ZHUCNB1
Kernel Version: 3.0.31-2569006
Baseband Version: I9305ZHUCNB1
Last Sync: 16 Aug, 2014 07:36 PM (the day I stupidly started this process)
Registered: 30 Aug, 2013 10:50 AM
Model: GT-I9305
Hardware Id: 42f7ce0338e89f73
Android Version: 4.3
Build Number: JSS15J.I9305ZHUCNB1
Kernel Version: 3.0.31-2569006
Baseband Version: I9305XXBMA2
Last Sync: 2 Oct, 2014 01:29 AM
Registered: 20 Aug, 2014 01:28 AM (the day I installed the stock Hong Kong software and got it back working)
Status: Active

Stock modem didn't work.
Factory reset, odin flashed the stock software again (with the stock modem). Same issue.
Followed instructions on this page for missing IMEI: http://forum.xda-developers.com/gal...warning-guide-backup-restore-imei-nv-t1946915
Tried *#06# but still no IMEI.
Any solutions?

Tried everything I read in lyquidperfection's awesome mega-thread, but nothing works. still got a /01 when I type *#06# and in the 'about' section it now shows IMEI: Unknown.
Everything else works fine, just the internet is stuck on Edge.

so I tried a few more things today but to no avail.
The IMEI shows up as "Unknown" in the phone settings and when I do *#06* I get a /01 message.
However, when I check my IMEI against my Google account, I get the above number.
Any suggestions as how to fix?

as of today, new modem is being release. I9305XXUFNI3
info here
for modem u can read this
download links from page, or this link
im quite new, but i hope this helps.

Thanks. Didn't work, still Edge.
Going to try flash again.

You could try running a different country's stock ROM, or maybe seeing whether you get 4G while using a custom ROM (Liquidsmooth maybe).

kirikee said:
Thanks. Didn't work, still Edge.
Going to try flash again.
Click to expand...
Click to collapse
it seems u're not the only one. later i found this thread, someone found a solution.
try read post #48 here , http://forum.xda-developers.com/galaxy-s3/help-i9305/s3-lte-i9305-3g-4g-2g-wokring-help.....
i guess its realated to IMEI. try find one. im not sure how.

Great success
GREAT SUCCESS.
Follow this post: http://forum.xda-developers.com/gal...te-i9305-3g-4g-2g-wokring-help-t2246437/page5
1. Restore a working QCN backup (like this one) http://www.mediafire.com/download/4j...4_19-53-39.rar through the download tool of the QPST suite
2. Change the IMEI to match yours. <<<<. DON'T SKIP THIS STEP. There are many way to do this, i used RF NV manager. I can't be more specific since this topic is off-limits on XDA.
3. Perform a factory reset.
I can't test LTE connection, because where I live there is no coverage, but I'll try as soon as I can.
Click to expand...
Click to collapse
For absolute n00bs like me:
Step #1, use QPST Suite from this thread to install the QCN backup as per above: http://forum.xda-developers.com/gal...warning-guide-backup-restore-imei-nv-t1946915
Step #2, uninstall QPST, follow this thread (post #4): http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/
>> I didn't have the US version LTE phone, but it works on my LTE International
Step #3, go into recovery and wipe cache and factory reset.
>> *#06# should show your imei, and your 4G should be back. mine came back instantly two months of pain over!!!!!!!!

IMEI lost after unsuccessful flash

Earlier this week I had an unsuccessful install of the alpha CyanogenMod 13.0 rom - didn't want to be encrypted so I substituted the latest HC M kernel. wasn't the first time I couldn't get a new rom to boot so didn't initially think much about it but following that flash I couldn't get any new rom to install and successfully complete setup. Each try would get stuck at step right after wifi was set up. I eventually determined there was an issue trying to connect with Google servers. Tried a multitude of fixes but nothing worked. Ultimately I found that my IMEI and IMEI ID had been hosed and both were now 0's rather than the original IMEI number. I unfortunately did not have the efs partition backed up (at least that I could find). I have tried every method, tool, etc. I have been able to locate to repair or to re-write the IMEI to the phone but so far to no avail.
I restored the original stock software (going back to the original lmy47e on the phone when I purchased it) as well as subsequent releases with a hopeit could somehow restore the IMEI but nothing has worked. I have managed to getto where I can make and receive calls and SMS/MMS but once I'm out of wifi range, no internet access. I even have trid a new SIM from Verizon but tha made no difference. Still a bit confused as to where the IMEI value is stored (and how it could be corrupted) but at this point it looks like new phone time (already ordered a new N6 from Amazon).
Hoping maybe someone might have some suggestion that might help me out. Seems like the N6 is new enough and different enough that the usual fixes don't seem to work. I know discussions around flashing IMEI's isn't really legit on xda but I'm just trying to get back my original IMEI rather than trying to mask a problem phone.

The only accepted way to get it back is to restore a back up. Having the IMEI corrupted happens when roms flash the wrong partitions. Samsung is known for storing the IMEI in a partition that is easily corrupted or erased when flashed. Not normally a nexus issue and I'm not sure which partition the IMEI is stored under.
It is not unheard of that cm roms have some issues like this. It wasn't to long ago that they bricked some nexus.