Develop Bugs

Emergency Calls Only...

Hi,
last night this problem just came out of nowhere. I was texting and calling fine like hour before I noticed it happen, but whenever I try to call it hangs up, and whenever I try to text it tells me to try again when service is available. On the lock screen it tells me "Emergency Calls Only", but sometimes it shows "Virgin" I'm with Virgin Mobile Canada, but still doesn't work. I've tried the following:
1. Pulling out battery and putting it back in.
2. Nandroid restore to when I first rooted it, and when it was working fine.
3. Take out SIM card, battery, and memory stick
4. Putting it into airplane mode and disabling airplane mode about 30 seconds later.
5. Unrooted to original Bell Stock Rom image from a thread and now have normal recovery
6.Data/factory reset
The only thing I do have a possible lead on is that yesterday I created a recovery tar file, from a recovery image I got from cwm website under AT&T, thought it was also for Bell (Model wise) as well, so don't know if that's the case, does that have to do with anything? I'm back to stock recovery and rom and from a thread here: http://forum.xda-developers.com/showthread.php?t=1739426 and downloaded the Bell/Virgin image, and flashed with Odin, I am back to stock, but still did not fix issue. It says Virgin on the top sometimes, and sometimes back to "Emergency calls only" could the recovery flash have changed radio or something? I also did do a restore before I flashed the new recovery and when phone was being normal just before unrooting but that also didn't work. Now I am unrooted and not on custom recovery. But still no service. Most of the time the service is 1 bar, but even when it's on 5 for like 10 seconds, it still doesn't work. Is it me or my carrier? I also noticed that even when the signal shows full strength it tells me "Emergency Calls Only". Thanks for the help.

I'd call Virgin and ask if your service was interrupted for any reason.

Yeah I'm going to do that, but I just looked at the IMEI number on the back of the phone, and looked at it in settings, but it did not match the number it had at the back. It just says 0 in the phone settings. Does that have anything to do with it? I wanna know if this is has anything to do with that first before calling.
EDIT: Okay so I did some research and yes that is apparently the problem, so I rerooted to custom recovery, and followed this guide: http://forum.xda-developers.com/showthread.php?t=1801997 my IMEI is back, and matches, and it says "Virgin" now at the top of my lockscreen, but still, I can't send messages or call. Did the deleting of IMEI also delete something else I should restore? Or is it something on their side? I am connected to Virgin Mobile, but the connection is extremely weak, and does not complete any calls or texts. There's also "IMEI SV" under settings and it says "01" is that an issue?
EDIT 2: Nevermind I just had to follow post 3 after fixing IMEI in that thread I linked and it worked! In case you researched and got here. Follow thread I linked up.

rise chicken
I'd like to resurrect this thread for a moment. Papaniz's problem is exactly like mine, same carrier & country.. but the link is dead.. any idea what the process was or where another link might be? Thanks Guys

tutorialhedz said:
I'd like to resurrect this thread for a moment. Papaniz's problem is exactly like mine, same carrier & country.. but the link is dead.. any idea what the process was or where another link might be? Thanks Guys
Click to expand...
Click to collapse
The thread was remove to avoid illegal problem. You'll most likely have to look somewhere else to recover your IMEI if flashing stock firmware doesn't fix it.

Today,no mobile service - have worked hard for solution - no success

Hi there
I am in New Zealand, recently rooted with DR Ketan’s help and installed PhilzCWM. Also on Ketan’s advice, I backed up my EFS.
My problem: just today I realised I cannot send text, or make phone call. I am on X-Note ROM from 3-4 days ago. I am very sure that after installation, I had normal Mobile connectivity and was surprised to find I didn't. Not sure if my EFS became corrupted, or other ROM setting is wrong.
Under Settings About Device:
My SERVICE STATE says Out of Service
My Mobile NETWORK STATE says disconnected.
My phone number says UNKNOWN
What's weird is
My IMEI lists a long number, assumed correct and not corrupted
So if my EFS partition is corrupted I assume I wouldn't see any IMEI at all?
Far as I know my SIM is activated (I am on a company plan & coworker's phones are normal)
Just now I restored my stock nandroid and .... same thing! No service. So I doubt it's even a modem problem.
Guys I'm screwed, any tips what settings to check etc??

sounds like your IMEI is invalid. i had something random recently. all my flatmates use iphone 4s. they had no signal when @ home. cant send texts etc. wifi works.
then next day my LTE N2 did the same thing. I changed MODEM/BASEBAND problem corrected it self. went back to old MODEM/Baseband. no problems since.
only other thing i can think of is, someone has reported your IMEI to police or your provider..
does it say "NOT REGISTERED" ? or something similar where your provider name appears?

R0B3RTF1SH3R said:
sounds like your IMEI is invalid. i had something random recently. all my flatmates use iphone 4s. they had no signal when @ home. cant send texts etc. wifi works.
then next day my LTE N2 did the same thing. I changed MODEM/BASEBAND problem corrected it self. went back to old MODEM/Baseband. no problems since.
only other thing i can think of is, someone has reported your IMEI to police or your provider..
does it say "NOT REGISTERED" ? or something similar where your provider name appears?
Click to expand...
Click to collapse
Hey thanks for th tip.
My phone recognises Vodafone as my provider but still won't connect.
I will try flashing a different modem, I may not have paid enough attention to different versions when I flashed the aroma installer.
Thanks, I'll report back.

update: Vodafone shop confirms my SIM is 100% good, and it works in another phone. So I think you're right, my IMEI is fukt.
I was told by Voda that my proper IMEi is listed on my phone innards. The IMEI shown in phone settings is waaay different. So it's corrupted somehow. I gotta familiarise myself with how to flash my backup image. Damn just what I need on beer day Friday

I restored my backup image of EFS/IMEI - it solved my problem.
Because there was an IMEI listed in phone settings I wrongly assumed it was the correct one. So flashing ROMS can muck up your EFS.....thank god for backups

you can still use the custom roms. just if your IMEI stuffs up, there is methods to reset it. i had to do it once. wasn't that difficult but was rather troublesome. i just wanted to use the custom rom at the time.

[Q] Band Handover/voice network issues

So I have been waiting patiently for the 4.3 update to roll out to me OTA with hopes that it would fix my issues but my phone has been saying download interrupted and so I have gone back to completely stock and triangle away to get my device status back to normal but it still wont let me download. When looking around for other possible causes I saw that my build number is JRO03L.I747UCDLK3 which comes up as a build number for a nexus 7, the correct build number for my att should be JRO03C. I have no idea how it got that way but I am wondering if the person who bricked it might have put the wrong version of the bootloader or some other part of the firmware on and it somehow didn't brick but is detecting a conflict and not letting me OTA. Or that is what is causing my cell network issues as well. Wanting input from a a few devs as I am not 100% sure what the first part of the build number represents.
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for tag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.

Bump
Bump!...not looking good.

madnesshero86 said:
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for Jtag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Click to expand...
Click to collapse
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail

Tried
View attachment 2362929
winosxbuntu said:
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Click to expand...
Click to collapse
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?

madnesshero86 said:
View attachment 2362929
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
Click to expand...
Click to collapse
I think I can help, I just need to pull up some files and I might get you the software or program I used to back -up and restore my EFS folder/files
Even fix it, so plz hang in there........will report back later on

Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

madnesshero86 said:
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
this is the software/programme i used to back-up, recover or even fix my EFS files (if they are corrupt and can be used) NV items reader writer
type it on google and pretty sure you will find something , try different links and again am sure you will find a download
have you tried flashing the new 4.3 stock firmware and modem follow this link for everything http://forum.xda-developers.com/showthread.php?t=2498233 or you can wait for AT&T to release the official 4.3 firmware and that will be 100% satified to be stable and will fix all your EFS/IMEI problems FOR GOOD :laugh:
i have the NV items reader writer software that can fix your problems but i dont know how i can share it with you without breaking any rules
ULTIMATE/final solution send it to MOBILETECHVIDEOS and will fix it like its nothing, take it to samsung and have to play some ball, or BUY A NEW PHONE
tried kernels (idont think it will make any difference) but its good to check

I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

madnesshero86 said:
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
NV items reader writer
type exactly as it is on google or here on XDA

New Info
See new info in OP Please, and before anyone says anything I have spent half the day searching with various keywords trying to find a fix so be kind if it seems obvious to you, I couldn't find it and I did try.

Bump

[Q] Mobile data suddenly dropped

I'm running CM-10.1.3 (stable) on my phone (T999) with the UVMD5 modem and last night I lost all signal for about 30mins. I rebooted a few times and toggled air plane mode on and off without any success. Eventually, I got signal again but no data. I can send and receive calls and SMS but I have no data connection (can't browse, no email notifications, etc.). I have tried all the options under the Network Mode settings without any success. Occasionally, I'll see the "E" sign for Edge/2G but there is no data available even then. I also tried updating the modem to UEMJ4 and UEMJC but observed no changes. WiFi works just fine. Could this be a hardware issue? Is the antenna somehow damaged? Is there anything else I could try?

Try another Kernel. If that does not help, Odin flash to Stock. If that too doesn't work then suspect tower issue.
Hardware is a possibility. But lets not get ahead of ourselves

Thanks, I'll give that a shot and report what I find. I doubt that it's tower related since I'm having the same issue at home and at work and my roommate, who has an original Galaxy and is also on Tmobile, is not having any problems.

I flashed stock JB 4.1.2 (UVDMD5) using Odin since I had it laying around and I'm still seeing the same issue. What else can I try?

EvilBoz said:
I flashed stock JB 4.1.2 (UVDMD5) using Odin since I had it laying around and I'm still seeing the same issue. What else can I try?
Click to expand...
Click to collapse
Check your APNs. Those are under Settings > Advanced > Network. Its called Access Point Names. It should be set to epc.t-mobile.com. See this thread for details.
Try UVDLJC or the prior version to MD5. If that too does not help then take to T-mo for antenna Repair.

Check your IMEI number. If it is zeroed out PM me. Otherwise just let us know here, (but don't actually post it).

DocHoliday77 said:
Check your IMEI number. If it is zeroed out PM me. Otherwise just let us know here, (but don't actually post it).
Click to expand...
Click to collapse
The IMEI is 0. I never backed up the EFS folder but I was able to get the number from tmobile.

I have been having the same issue since June 2013 after doing to 4.1.2 OTA update from T-Mobile, at the time I didn't realize the IMEI was listed as unknown. So for months I have not gotten a cellular data connection better than Edge. Also after that update trying to check for a software update on the phone resulted in an error, and Kies told me my firmware was not supported for upgrade. Looking in some support forums and talking to T-Mobile got me nowhere, so I have just been dealing with it.
Wanting to upgrade I recently used Odin to load the official T-Mobile 4.3 ROM on the phone, actually hoping that would fix my issue (still in the dark about IMEI) which it did not.
I had never backed up the EFS folder, since as a standard user I had no idea what it was and while performing an update from my provider I didn't realize anything would need to be backed up outside of Kies. Now that my warranty is expired and having to take matters into my own hands I am on a quest to find a fix, however I don't want to "brick" my phone in the process, at this point I know enough to be dangerous.
Currently;
Android 4.3 Official T-Mobile ROM
BASEBAND is good T999UVUEMJC
Kernel 3.0.31-1962493
IMEI is Unknown
Looking at some other posts here at xda-developers I tried to follow some instructions on repairing or restoring IMEI using NV reader/writer, however I cannot get NV reader/writer to connect to my phone.
I have noticed in 4.3 when using *#7284# in the dialer the QualComm settings are no longer present, only MODEM and PDA are available.
I have poked around in Service Mode *#197328640# and found a setting that I thought might help, but I have a feeling it is the same thing as 8#7284#
[1] UTMS > [6] COMMON > [4] DIAG CONFIG > [1] USB or [2] UART
So at this point I don't know how to proceed, again I am not thrilled about loading a custom ROM, or really any ROM for fear of making the issue worse or bricking the phone. I have read a lot of posts about no longer being able to make calls due to IMEI issues. Everything works right now except cellular Data.

[Q] [VERIZON] Repaired IMEI, Updated with OTA, Phone keeps roaming...

Really not sure what to do here, and I'm starting to get very frustrated, especially since I know exactly what the issue is and I can't find a solution... So here is everything I did up to this point in detail. I wanted to go back to stock for a while, but I remembered not being able to update at all last time I tried this. I used the LG Flash Tool to go back to 10b (I think? Earliest firmware out there) It started when my phone would tell me that "My Device was not registered yet" in the System Update settings. I did some Googling and found out it was because my IMEI number was blanked out (All zeroes), and I found a tutorial that was for the G2, but worked for the G3, to repair the IMEI. I first rooted with the LG One Click Root Tool when I got to Lollipop, used the IMEI that was under my battery, converted it to HEX and injected it into my phone with RF_NV_Manager, which was installed with QPST by Quallcom. After doing this, my IMEI was fixed, it matched the same IMEI that was under the battery on my phone, though I never texted or called anyone from there so I never noticed anything strange. I was able to update to the latest official Lollipop firmware, but then my phone started telling me I left the home network. Thinking it was just a glitch or something, because I had roaming issues before on stock, I switched to a custom ROM since that fixed it last time before I even knew that IMEI's existed. That didn't fix it at all. I was on LiquidSmooth Alpha and my phone will still go to roaming, and the way I would fix it was to piss around with the mobile network settings and change them back, then I would get 4G LTE for a few minutes, but I would NEVER be able to call or text. Since it was a discontinued ROM, I thought I just got unlucky, so I went to an official Nightly for CM12.1. At the moment I have LTE but no calling or texting... Then I found out that these issues tend to occur after IMEI fixes, so what do I do? Can anyone point me to a proper tutorial on how to fix this? After looking, I ended up downloading and installing something called EFS Professional 2.1 but now I'm even more confused...
EDIT: I tried going into ADB and inputting "adb reboot nvrestore" but that didn't fix it... The site said it's based on a backup that was automatically created when the phone was first built but that was on a completely different forum for a different phone. Going to try to flash back to stock KitKat.
EDIT: Alrighty! I'm getting somewhere! I flashed back to 10B with the Upgrade DL option, before I used Board DL. I can call and text now, as well as LTE, and OTA updates work, but I'm just going to root and go straight to the Nightly CM12.1 that I wanted to go to in the first place.
EDIT3: That seems to have done the trick. For people who have had issues with roaming after IMEI repairs, try flashing your stock TOT with the Upgrade DL option, then root and install your preferred ROM.