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.

[Q] Permanent no service - tried multiple roms...revert to stock?

HI all,
First post, go easy on me!
I've searched the forums trying to find the answer to this problem but have been unsuccessful. I successfully flashed my Galaxy W with slimbean 3.1.0 and had been using it successfully for over a month. I put it in airport mode to save battery, as I had done many times before, but this time when I turned it off the service never came back. I haven't had service since.
I have tested the SIM in another phone and it is working fine. I have also tried flashing a different ROM (CM10 Alpha 1) with no luck. I would reflash the phone with the stock firmware if there is any chance that would help, but I haven't been able to figure out how to do that via CWM. At this point I'm not exactly sure what to do. Is it possible that the this is a hardware issue?
Any advice would be greatly appreciated!

mitchm said:
HI all,
First post, go easy on me!
I've searched the forums trying to find the answer to this problem but have been unsuccessful. I successfully flashed my Galaxy W with slimbean 3.1.0 and had been using it successfully for over a month. I put it in airport mode to save battery, as I had done many times before, but this time when I turned it off the service never came back. I haven't had service since.
I have tested the SIM in another phone and it is working fine. I have also tried flashing a different ROM (CM10 Alpha 1) with no luck. I would reflash the phone with the stock firmware if there is any chance that would help, but I haven't been able to figure out how to do that via CWM. At this point I'm not exactly sure what to do. Is it possible that the this is a hardware issue?
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
Yes it´s possible it´s a hardware issue you got after a while.
First thing I would try is to flash back to stock ROM and see if this fixes your issue. (With Odin)
There is a guide about how to do that, but am sorry not to point you to it right now. Its 4am here righ now and I already am having difficulties to write correctly. (need to go to bed soon )
If this helps I would suggest to update the baseband and then to try again with CyanogenMod.
But if reflashing the stock ROM doesn´t help either, I would suggest to contact the Samsung Service Center.
By flashing back to the stock ROM make sure you are flashing the one used in your specific country, because in the first place it also inculdes the baseband used in your country and in the secound place it also inculdes the country code Samsung might look at while testing your phone.
In Germany for example most SGW´s were sold with it´s specific coutry code. But there were also a few sold with the county code for the whole EU.
So you must care about such things when flashing back to stock ROM. For fixing it the country code is not important. Only the baseband used in your region is important. But I case you need to contact the Samsung Service Center it will be important.
Hope this helps a bit. Now I really need to go to sleep.

Does your IMEI number still ok? Cause I lost my Efs folder with IMEI number some time ago, in another Galaxy fone i had.
you can check it in Settings / About fone / Status / IMEI
If you lost it, you will have no service, no matter what rom you try.
In this case, you can try to repair using this http://forum.xda-developers.com/showthread.php?t=1308546 , not simple but saved my fone.

[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

My MIED is gone....

Can I write it back with VIA_ESNWRITER or is it the same as in the back of the phone still?

all unknown meid,esn,imei,cdma radio,network,phone number
TitanTaber said:
Can I write it back with VIA_ESNWRITER or is it the same as in the back of the phone still?
Click to expand...
Click to collapse
i dont how to post a problem if it is wrong way excuse me ,the issue regarding sprint gnex,below i mentioned thing which i observed in my mobile.in india i contacted samsung services but no use .i dont have place to get solution right now.
hello gurus,
hello my name is sreenath reddy from bangalore city of india.here i have problem with my sprint gnex,that i am using it from past 1 year.
recently i updated to kitkat toroplus cynogenmod 11 nightlies on stock 4.3 worked good for some days.
i went roaming to other state suddenly. i lost signal,empty (meid,imei,esn,phone number,unknown network,unknown icc id),in bootloader
screen lte radio showing, but unknown cdma radios .manually i flashed back to stock but no change.
i flashed to stock 4.1.1 and 4.2.1 and 4.3.when it working i backed up stock 4.3.as well as 4.4.2.
i restored with twrp 2.6.3.2 its taking again it showing unknown all.here one more problem is
i can acess diag but in data mode if i input msl it making the problem stating that modem exception problem.with some apk to force to
ets channel.but it is not taking ets usb mode.i tried to write meid with ets app but it is taking comm port not usb port.
i have to put into ets usb then,only i can recall the obove mentioned things.i tried to rootz wiki
msl finder but no use.i tried of that script manager from xda but no result not found msl,with terminal emulator no result.
to put manually in diag or data mode i need msl.for hard rest i need msl,plz if you encounter the the same problem get me the procedure to do .
currently i am in reliance cdma network.my phone bluetooth and wifi working fine phone also working fine.phone functionning normal
only i can not make calls ,sms,not using 3g.adb working fine,fastboot,odin working fine.
*#*#3282#*#* in this trasaction if i tried with my old msl,modem eception problem, i will get message stating that android process.com stop the process.
i tried of hard reset but it asking msl again.even i flashed team eos rom 4.2.1 but i kept dignostic mode and ets usb mode but useless.
.please some body shed some light on this issue.i am not able
to use the phone from past 30 days.if some one not making the answers from mail through get me atleast
some phone numbers.
i can contact you imm.suggetions will be appriciated.
i am attaching the bug report of my mobile as attachment
thanks,regards
reddy
[email protected]
09591491769
bangalore,india

[Q] Phone Flashed to Page Plus Stuck on Boot Screen

Hello all,
I tried searching for a similar scenario but wasn't able to find anything so I thought I'd try posting here.
I purchased a flashed Sprint Samsung Galaxy S3 from ebay about 6 months ago. I'm assuming the phone is rooted, I had my number flashed with page plus service to the S3 without problem and it has worked fine since then. Apart from the initial flash to page plus by the ebay vendor I've used the phone daily without flashing anything else, just using apps from the store and basic daily functions like email, social media and camera use. Today while using the phone it randomly shut off. When starting up the phone again it gets stuck on the "Samsung" logo, it does not reboot either.
I know that a hard reset can fix this issue but the problem is I believe a hard reset might break the page plus flash and I'm afraid of losing the number I have on this phone. Has anyone experienced this problem with a phone flashed to page plus and has successfully fixed this? Or will I just have to buy a new phone to flash my page plus number to?

Write down your flashed page plus number to external paper and after hard reset flash it again using dfs software.
Or if you don't want to hard reset... Flash the tar file via Odin to repair the stuck boot then root it.
But i recommend to flash a new rooted ROM from recovery after wiping data/factory reset.. It will not wiping your flashed status.
Sent from my SPH-L720 using Tapatalk

update
Thanks for the reply, unfortunately I don't really flash on my own and didn't quite want to experiment just yet.
What I ended up doing was esn swapping the page Plus number I was using from the Sprint s3 to an htc rhyme that was also activated on page Plus in a hope of salavging my #. I then went ahead and factory reset the s3 and that fixed the stuck on boot problem.
My question is now this, would it be possible to esn swap the number back to the s3 and have it function on page plus once again. from what I can tell in the settings it still has the 65002 prl I believe is uses to flashthis model and my orginal phone number still appears in the s3 device settings (and 3g username aferrad) despite my swapping the number to the rhyme.
I would be happy to provide addtl info and appreciate any help you can offer.