[Q] No Network Data After Flash Custom ROM - General Questions and Answers

Kind of long, but it's just a difficult explanation, please read and try to help me. Thank you.
Okay, so I have a really weird problem, and I can't seem to fix it at all. I rooted my T-Mobile Galaxy S4, and had no problem with data loss, then I flashed Darthstalker, and everything went fine and it flashed but then I noticed that whenever I shut my screen down when I was on anything other than E or 4G LTE, the phone would lose network signal, but what was weird is that I could still receive texts and phone calls. In order to get the signal back though, I had to go change the data type, and then change it back to normal.
So, then I read that wiping the Dalvik and the regular cache would fix it, and it didn't. Then, I also tried flashing a different ROM (Wicked v9.1) which also didn't fix it. So, I flashed the stock firmware and just got rid of the root and the problem was gone. I even tried rerooting and just installing only Wicked first just to see if maybe Darthstalker corrupted something. But, it still had the same issue, so I just went back to stock again.
Can someone please help me fix this? I've looked everywhere and I can't really find anything to help me out with this.
Thank you in advance.

Related

[Q] Nexus S no network service! What do I do?

Hi guys I have a 2 month old Nexus S and for no apparent reason all of a sudden today I noticed I am not getting any network service (australia vodafone).
I've tried removing and trying other sim cards which are known to work. My sim card works in other phones so it's nothing wrong with the sim card. Wifi still works perfectly. I've tried going in and out of airplane mode to restart the antenna and I've tried to turn it off and on again. I've also done a factory reset and erased all data through the android menu as well as the bootloader separately to no avail.
However what I also noticed is even though I did factory resets it doesn't seem to completely reset it as the android version still shows 2.3.3 which I applied using a manual update. The phone had 2.3.1 when I bought it. How do I do a full reset to send it back to 2.3.1?
The phone is still under warranty however if it is a software issue I would rather fix it myself then send it away.
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Additionnal bit of info.
Someone on Cyanogen forums asked me to try to flash the radio through fastboot instead of clockwork recovery..
If I do that, it is able to send the file but it seems unable to write. It gets stuck here:
fastboot flash radio XXKB1-GRI40-radio-nexuss-unsigned.zip
sending 'radio' (4126 KB)... OKAY
writing 'radio'...
(I've tried flashing both KB1 and KB3 through flashboot, same results)
Hello everyone,
I have the same issue. I turned my phone on this morning and it said "no service, emergency call only".
I used wifi to apply the OTA 2.3.4 with hope that it'd fix the issue as I read from my google searches. But it does not.
I tried flashing back to KB3 to run with 2.3.4 as well but that doesn't help.
If the phone can still do emergency call, it means the hardware is OK, right?
any suggestion? Thank you very much.
Opteron.
Did anyone ever find a solution?
you could try dialing *#*#4636#*#*, going to phone information, and looking at your preferred network type (might be the wrong one). you could also go to phone information, push menu, go to select radio band, and try a few different ones. hopefully that solves it, or you might have to flash a different radio/rom
edit: make sure you write down the original preferred network type before you change it. it could screw with what kind of service you get if you set it to the wrong one
Hi,
I am having the similar problem with my Nexus S
Tried the *#*#4636#*#* settings to EURO and GSM only but with no success.
Did anyone ever find a solution?
hi, im just wondering what type of root did you use for the AU nexus s. im not sure what root method to use for the SCLCD :S
thanks
fooraide said:
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Click to expand...
Click to collapse
Hello! did you find any solution or you repaired your nexus s? Im having the same problem. when i try to back to stock from Cyanogen..Any suggestion? Regards
found a solution
hi guys ! I recently had the same trouble that no signals were being received after updating to 4.1.2 but then i dialed *#*#4636#*#* and turned off the radio and turned it on again and now its all fine

[Q] Does anyone want to help me out yet? -_-

Okay, I'm basically going to just copy and paste my issue and edits here from the Zeus thread I couldn't get any help on. The edits are so anyone who actually read this can see what I did and have been doing so they don't suggest something I already did.
So the other day, I tried to flash to the Doctorz ROM and of course, made a Nandroid backup. After messing with Doctorz, I went back to Nandroid or clockwork recovery (whatever it is) and after restoring, I was on another modem and stock kernel. I tried to reflash Zeus and wiped partitions cache and dalvik cache and now I'm having serious issues. I have my SIM card in my phone, but it keeps telling me I don't even though it's there. Even weirder, I have one or two bars even after I pull out the SIM card. Earlier, it was detecting that I had a SIM card, but said "Invalid SIM card" or something and now whether it's there or not, my phone says it has one or two bars even though I can't do anything. What's going on??
I've tried rebooting several times and activated Wifi and airplane mode, but had no luck. SIM card's in right now, but my phone says no service.
EDIT: Forget it. I just did a factory restore and wiped everything and reflashed Zeus.
EDIT 2: Okay now I'm having other issues. My phone recognizes my SIM card again and now I'm getting my normal signal, but I can't do anything wirelessly, like send a text or use up data. It SAYS I have signal and am connected to the HSPA+ network and the arrows are flashing and whatnot, but I can't do anything wireless. I can't go into the market, send a text or use the internet browser. Someone please help?
EDIT 3: Okay, I was wrong on that last part. My texts weren't going through because of bad signal, but I definitely have no data AT ALL. All I have are a few bars, but nothing about 3g/EDGE/HSPA+. I think this is an issue with APN settings?
EDIT 4: Messed with some APN settings... kinda back to square one, where the H+ shows up and I get Edge sometimes (I have bad signal where I'm at) and the arrows are flashing, but NOTHING. I still can't use the market or any data at all.
EDIT 5: I just decided I'd try to be next to my router and turned on Wifi... my phone would not pick up a signal from my router at all, and it works just fine. I'm starting to think this is a modem-related issue...
EDIT 6: Okay, I kinda fixed the problem, but my data speeds are SUPER SLOW and sending one message takes a really long time. I know I have bad signal, but it's never been this slow, even when I manage to pull up two or three bars. I tried messing with build.prop, but as I'm on Zeus, the settings were already fixed up.
EDIT 7: Okay, the Wifi issue was because I used the wrong WEP key. Oops. After I managed to connect though, I couldn't get any data. My phone just doesn't want to use up any data apparently? I reflashed the modem Zeus normally uses and now if I manage to get some data, it's unbelievably slow and can't use Wifi data.
EDIT 8: I forgot to mention that if I don't get to connect somewhere with data, my phone will just tell me there's no data connection or whatever even though I have two bars. I tried to fix permissions and rebooted, but no luck.
Someone please help. This is really annoying.
FaintPuppet said:
Okay, I'm basically going to just copy and paste my issue and edits here from the Zeus thread I couldn't get any help on. The edits are so anyone who actually read this can see what I did and have been doing so they don't suggest something I already did.
So the other day, I tried to flash to the Doctorz ROM and of course, made a Nandroid backup. After messing with Doctorz, I went back to Nandroid or clockwork recovery (whatever it is) and after restoring, I was on another modem and stock kernel. I tried to reflash Zeus and wiped partitions cache and dalvik cache and now I'm having serious issues. I have my SIM card in my phone, but it keeps telling me I don't even though it's there. Even weirder, I have one or two bars even after I pull out the SIM card. Earlier, it was detecting that I had a SIM card, but said "Invalid SIM card" or something and now whether it's there or not, my phone says it has one or two bars even though I can't do anything. What's going on??
I've tried rebooting several times and activated Wifi and airplane mode, but had no luck. SIM card's in right now, but my phone says no service.
EDIT: Forget it. I just did a factory restore and wiped everything and reflashed Zeus.
EDIT 2: Okay now I'm having other issues. My phone recognizes my SIM card again and now I'm getting my normal signal, but I can't do anything wirelessly, like send a text or use up data. It SAYS I have signal and am connected to the HSPA+ network and the arrows are flashing and whatnot, but I can't do anything wireless. I can't go into the market, send a text or use the internet browser. Someone please help?
EDIT 3: Okay, I was wrong on that last part. My texts weren't going through because of bad signal, but I definitely have no data AT ALL. All I have are a few bars, but nothing about 3g/EDGE/HSPA+. I think this is an issue with APN settings?
EDIT 4: Messed with some APN settings... kinda back to square one, where the H+ shows up and I get Edge sometimes (I have bad signal where I'm at) and the arrows are flashing, but NOTHING. I still can't use the market or any data at all.
EDIT 5: I just decided I'd try to be next to my router and turned on Wifi... my phone would not pick up a signal from my router at all, and it works just fine. I'm starting to think this is a modem-related issue...
EDIT 6: Okay, I kinda fixed the problem, but my data speeds are SUPER SLOW and sending one message takes a really long time. I know I have bad signal, but it's never been this slow, even when I manage to pull up two or three bars. I tried messing with build.prop, but as I'm on Zeus, the settings were already fixed up.
EDIT 7: Okay, the Wifi issue was because I used the wrong WEP key. Oops. After I managed to connect though, I couldn't get any data. My phone just doesn't want to use up any data apparently? I reflashed the modem Zeus normally uses and now if I manage to get some data, it's unbelievably slow and can't use Wifi data.
EDIT 8: I forgot to mention that if I don't get to connect somewhere with data, my phone will just tell me there's no data connection or whatever even though I have two bars. I tried to fix permissions and rebooted, but no luck.
Someone please help. This is really annoying.
Click to expand...
Click to collapse
Damn! That's a lot of edits. Odin back to stock, and start from scratch. But remember to do a factory reset from Phone, go to settings, Privacy and erase everything. that will clean up everything that you have there.
That's the only option I see will fix all your problems
Ltilt2 said:
Damn! That's a lot of edits. Odin back to stock, and start from scratch. But remember to do a factory reset from Phone, go to settings, Privacy and erase everything. that will clean up everything that you have there.
That's the only option I see will fix all your problems
Click to expand...
Click to collapse
Yeah, that's all I could come up with. Thanks anyway. I did that a few minutes ago and flashed Zeus. I'm just waiting for my phone to load up. I tried to let it load up, but it kept saying not enough data on the partition or something. I probably shouldn't have tried to flash Zeus immediately after flashing back to stock. After I went to CWM from flashing to stock, I immediately tried to flash to Zeus, but had issues. I'll take the blame for trying to rush and take shortcuts. I'll see how this goes again though.
Okay, after flashing back to stock with Odin, my phone loads up and does the "Rethink possible" thing when you turn it on and after that, nothing happens. The screen just stays off. If I press the power button, nothing happens, but if I hold it, it just reboots and goes back off. This is just annoying...
EDIT: Okay, it worked the second time. I have no idea why as I did nothing different, but it works. Now I'm gonna try to flash Zeus again.
FaintPuppet said:
Okay, after flashing back to stock with Odin, my phone loads up and does the "Rethink possible" thing when you turn it on and after that, nothing happens. The screen just stays off. If I press the power button, nothing happens, but if I hold it, it just reboots and goes back off. This is just annoying...
EDIT: Okay, it worked the second time. I have no idea why as I did nothing different, but it works. Now I'm gonna try to flash Zeus again.
Click to expand...
Click to collapse
Faint,
I got lost trying to understand what you were trying to ask.
Gtg unbrick is prob the best option.
It's usually best to describe the system, setup, the bug and the attempt.
Then pose the bottom line question.
Check my last sigs link.
qkster said:
Faint,
I got lost trying to understand what you were trying to ask.
Gtg unbrick is prob the best option.
It's usually best to describe the system, setup, the bug and the attempt.
Then pose the bottom line question.
Check my last sigs link.
Click to expand...
Click to collapse
Well what I was asking originally was how I can fix the problem I was having, but flashing back to stock via Odin helped. Now I'm having ANOTHER issue... after FINALLY having fixed up everything, I tried to restore some stuff with Tibu, but then my phone started saying a bunch of processes were force closing or something, so I tried to reboot and now I think I'm bootlooping. I'm stuck at the "The Collective" thing that shows up when you boot up your phone and it doesn't do anything. It'll go and do what it normaly does, go black and start up again, then come to a complete stop and repeat the process. I then went to CWM and tried to wipe factory settings, cache and dalvik cache, but I'm still having this issue. Geez, it's one problem after another, and all I wanted to do was restore my apps. On the bright side, I DO KNOW flashing from Odin helped because once I regained control of my phone at the way it should be normally, I had my normal data speeds and didn't have issues with data. I'm going to try to fix this bootlooping issue now. :|
EDIT: Escaped the bootloop(?). Thank God... I honestly thought I'd have to flash back to stock with ODIN AGAIN and then redo everything.
Hey, so another question... before I flashed to stock and everything, I backed up all of my apps with TiBU, but now I can't find them; the restore file(s?) so I can get all of my apps and their data back. Was it saved to the internal SD card? Because I formatted that after backing up...
EDIT: Never mind. I looked around my SD card and... ugh. All my apps are gone and so are my backup files for the apps. Great. Thanks anyway, you two.
FaintPuppet said:
Well what I was asking originally was how I can fix the problem I was having, but flashing back to stock via Odin helped. Now I'm having ANOTHER issue... after FINALLY having fixed up everything, I tried to restore some stuff with Tibu, but then my phone started saying a bunch of processes were force closing or something, so I tried to reboot and now I think I'm bootlooping. I'm stuck at the "The Collective" thing that shows up when you boot up your phone and it doesn't do anything. It'll go and do what it normaly does, go black and start up again, then come to a complete stop and repeat the process. I then went to CWM and tried to wipe factory settings, cache and dalvik cache, but I'm still having this issue. Geez, it's one problem after another, and all I wanted to do was restore my apps. On the bright side, I DO KNOW flashing from Odin helped because once I regained control of my phone at the way it should be normally, I had my normal data speeds and didn't have issues with data. I'm going to try to fix this bootlooping issue now. :|
EDIT: Escaped the bootloop(?). Thank God... I honestly thought I'd have to flash back to stock with ODIN AGAIN and then redo everything.
Hey, so another question... before I flashed to stock and everything, I backed up all of my apps with TiBU, but now I can't find them; the restore file(s?) so I can get all of my apps and their data back. Was it saved to the internal SD card? Because I formatted that after backing up...
EDIT: Never mind. I looked around my SD card and... ugh. All my apps are gone and so are my backup files for the apps. Great. Thanks anyway, you two.
Click to expand...
Click to collapse
If you did a factory reset from within the phone, it will erase everything...
After you odin or heimdall a stock package, and flash a new ROM, don't restore tibu or apps. Download new.
Occasionally they get corrupted and cause you phone to soft boot
FaintPuppet said:
Well what I was asking originally was how I can fix the problem I was having, but flashing back to stock via Odin helped. Now I'm having ANOTHER issue... after FINALLY having fixed up everything, I tried to restore some stuff with Tibu, but then my phone started saying a bunch of processes were force closing or something, so I tried to reboot and now I think I'm bootlooping. I'm stuck at the "The Collective" thing that shows up when you boot up your phone and it doesn't do anything. It'll go and do what it normaly does, go black and start up again, then come to a complete stop and repeat the process. I then went to CWM and tried to wipe factory settings, cache and dalvik cache, but I'm still having this issue. Geez, it's one problem after another, and all I wanted to do was restore my apps. On the bright side, I DO KNOW flashing from Odin helped because once I regained control of my phone at the way it should be normally, I had my normal data speeds and didn't have issues with data. I'm going to try to fix this bootlooping issue now. :|
EDIT: Escaped the bootloop(?). Thank God... I honestly thought I'd have to flash back to stock with ODIN AGAIN and then redo everything.
Hey, so another question... before I flashed to stock and everything, I backed up all of my apps with TiBU, but now I can't find them; the restore file(s?) so I can get all of my apps and their data back. Was it saved to the internal SD card? Because I formatted that after backing up...
EDIT: Never mind. I looked around my SD card and... ugh. All my apps are gone and so are my backup files for the apps. Great. Thanks anyway, you two.
Click to expand...
Click to collapse
One more thing to add on to the TiBu thing, when you restored your apps what option did you use? If your restoring the batch options only select "missing apps with data.". Any other option and you run the risk of getting constant FC's.
Sent from my Transformer Prime TF201 using xda premium
That's why every time I flash a new Rom, I always never back up anything. I rather start from scratch and go from there. This I know for sure I wont have any issues.
Sent from my SAMSUNG-SGH-I997 using XDA App
Did we helped you out yet?
I have found this to be the best for me also, new ROM...fresh install of all apps...so easy when you have the apk's, I just put them in a folder, then to my sd and install away and if I need to update I look that app via the market and update that way, or via the desktop pc thru the market online.
I found this site very useful has all my apps I need/require:
http://www.apktops.com/
Ltilt2 said:
That's why every time I flash a new Rom, I always never back up anything. I rather start from scratch and go from there. This I know for sure I wont have any issues.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
xIC-MACIx said:
One more thing to add on to the TiBu thing, when you restored your apps what option did you use? If your restoring the batch options only select "missing apps with data.". Any other option and you run the risk of getting constant FC's.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
^Yeah I didn't use that option because it had a zero and didn't let me do anything, so I tried another option. I can't remember which one, but yeah I did get constant FC's.
Ltilt2 said:
That's why every time I flash a new Rom, I always never back up anything. I rather start from scratch and go from there. This I know for sure I wont have any issues.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Yeah, it seems that's the best way to go. Even though I backed it up with CWM, I didn't expect it to not backup the kernel and modem. I realized the kernel part a lot sooner, but after having a lot of texts that didn't go through the way they normally would, I thought it was an issue with my phone and then I decided I'd check the modem and found out I didn't have the KL2 modem I'd normally have.
qkster said:
Did we helped you out yet?
Click to expand...
Click to collapse
Well I already had everything figured out by the time everyone said something, but I appreciate the effort and tips nonetheless.

[Q] Verizon Galaxy s3 roaming only, not activating

So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.

[Q] At a loss, data but no voice/sms

I was running the latest stable version of CM10.1 on my GS3 and all was going well until someone sent me a text message and I tried to respond. I was greeted with the error of message not sent. I attempted to text someone else to have the same error. Attempting to call someone will just hang and eventually say call failed.
I thought it was a radio issue so attempted to flash different modems but had the same result. So I restored my previous rom Beans 11 that was working after wiping and the same issue. Data works perfect, but voice and text does not. I searched and odin'd back to stock VRLG1 and entered *2767*3855# in hopes of that fixing the problem, again no voice/text.
Any suggestions further help? I don't know what else to try!
*CM10.1 was working fine, and then calls/texting stopped but data continued to work without trouble.
*IMEI seems to be intact
*Flashed backup of known working rom and issue still persists
*Flashed back to VRLG1 and attempted *2767*3855# as per another post to no avail and this is where I sit.
Same thing. Installed jellybeans 12 now I can't call or text. Prior text was hit and miss some days....restored stock rooted image flashed other Roms....no help. Dialed the ** number....so screwed. Ayneegry should have backed up my few several times. No idea what to do.
Sent from my SCH-I535 using Tapatalk 2
When you say "Data" do you mean wifi or 3g/4g? If you have no phone/text/3g/4g then it's probably your imei. Check under phone settings, see if it's gone. If it's gone you gotta restore, do a search.
If you have 3g/4g then I don't know what the problem is. Sorry, just trying to help
Odin back to ICS and reprovision your phone by going into the dialer and typing *2767*3855#
rgrossie - data as in 3G/4G works no problem... phone showed IMEI still there but followed a thread to restore it anyway to make sure that wasn't the issue...
Edgehood -- I've tried that, and that's where I currently sit, stock ICS with 4G data but doing the re-provision doesn't seem to fix anything -- occasionally a text will slip through, but I'm unable to reply
astrocity said:
Same thing. Installed jellybeans 12 now I can't call or text. Prior text was hit and miss some days....restored stock rooted image flashed other Roms....no help. Dialed the ** number....so screwed. Ayneegry should have backed up my few several times. No idea what to do.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I hear ya, if I can't figure out what's up, I'll end up having to go back to verizon and see what I can do... It was out of the blue, everything was working and then suddenly it just stopped. Happened on a flash that was a little over a day old, so who knows.
Check Mobile network
I have thiss problem happen occasionally when I flash custom roms. Look under your mobile networks, see if either CDMA/SIM is checked or NV. If NV is checked switch to CDMA/SIM and then reboot. That seems to fix that problem most of the time.
Edit: After some tests found out this doesn't always stick, but I did find out that after switching from NV to CDMA/SIM turn on airplane mode so the radios are tunred off, wait a few moments, then turn airplane mode off. That worked more consistently than restarting it.
MrRevesz said:
rgrossie - data as in 3G/4G works no problem... phone showed IMEI still there but followed a thread to restore it anyway to make sure that wasn't the issue...
Edgehood -- I've tried that, and that's where I currently sit, stock ICS with 4G data but doing the re-provision doesn't seem to fix anything -- occasionally a text will slip through, but I'm unable to reply
Click to expand...
Click to collapse
Did you ever fix this? I currently have the same problem and have no idea what to do.
i had the same problem but a imei/efs restore fixed it. My imei was not missing but data worked and not calls or text. Changed sim and still same, even odined back to stock and unlockex and rooted no luck restored nandroid no luck. Then restored synergy imei/efs backup and good to go. Hope it helps.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
I had the same issue two days ago when I flashed to the latest MIUI Rom. Here's how I fixed it.
Go into settings, mobile networks, make sure subscription is set to SIM. After that open the phone, type *#*#4636#*#* make sure it's set to LTE/CDMA/AUTO
Reboot phone and all should be well.
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
If you Odin back to the original stock unroofed ROM, you'd have to take all the ota Verizon updates to vmf1. Then reset your phone.
Pain in the a$$ but has always worked for me. I had same problem running carbon.
I read in another post that Odin back to root66, them reset your phone would work too.
Sent from my SCH-I535 using xda app-developers app

No LTE

Hello!
I was running CM11 7/17 build and randomly my phone lost all phone service. Or so it seemed. So it seemed. I was able to call *228 to try to update roaming service. Well, it worked, except now, my phone stays in 3G and still doesn't seem to be full strength. Does anyone know what I need to do.
Also, I've updated to 7/27 CM11 and that didn't change anything service wise.
Thank you!
ESCollins90 said:
Hello!
I was running CM11 7/17 build and randomly my phone lost all phone service. Or so it seemed. So it seemed. I was able to call *228 to try to update roaming service. Well, it worked, except now, my phone stays in 3G and still doesn't seem to be full strength. Does anyone know what I need to do.
Also, I've updated to 7/27 CM11 and that didn't change anything service wise.
Thank you!
Click to expand...
Click to collapse
im pretty sure you dont want to use 228 on a smart phone, its not like a dumb phone that needs updates like that.
i would put stock on and see if you still have the issue.
if that doesnt fix it, or you dont want to do that, i would get a new sim card and see if that helps. you may have burned the 4g out of the sim.
bweN diorD said:
im pretty sure you dont want to use 228 on a smart phone, its not like a dumb phone that needs updates like that.
i would put stock on and see if you still have the issue.
if that doesnt fix it, or you dont want to do that, i would get a new sim card and see if that helps. you may have burned the 4g out of the sim.
Click to expand...
Click to collapse
Stock works fine. And I had this problem before when I used a locked boot loader ROM. But when I upgraded to KitKat and unlocked the boot loader and tinstalled CM11 everything was fine.
Is there a way to reset my phones cell/data service back? Instead of Verizon Wireless it just says T-CDMA 64 now as well.
ESCollins90 said:
Stock works fine. And I had this problem before when I used a locked boot loader ROM. But when I upgraded to KitKat and unlocked the boot loader and tinstalled CM11 everything was fine.
Is there a way to reset my phones cell/data service back? Instead of Verizon Wireless it just says T-CDMA 64 now as well.
Click to expand...
Click to collapse
i dont know exactly, i can only say what i would try if i were in your situation.
first i would re-flash the rom, just wipe cache's and system.
if no fix, i would try re-flashing only the modem's. edit the stock xml file and dump every line except the modem's and modem wiping lines then flash with rsd.
if no fix, i would have to say, a full wipe and re-install of the rom is in order.
if that dont fix it, i dont know what else to try.
i would do a backup before you try any of that, although its mostly useless, as you would just be backing up the broken setup. would just help to recover any data if you need to.
bweN diorD said:
i dont know exactly, i can only say what i would try if i were in your situation.
first i would re-flash the rom, just wipe cache's and system.
if no fix, i would try re-flashing only the modem's. edit the stock xml file and dump every line except the modem's and modem wiping lines then flash with rsd.
if no fix, i would have to say, a full wipe and re-install of the rom is in order.
if that dont fix it, i dont know what else to try.
i would do a backup before you try any of that, although its mostly useless, as you would just be backing up the broken setup. would just help to recover any data if you need to.
Click to expand...
Click to collapse
Okay. That was what I was fearing. But I'll give it a try when I get home! Thanks!!
I had the same problem, and I ended up getting a new SIM card. That fixed the problem, but I don't know if that was the only way to fix it...
Sent from my DROID RAZR HD using XDA Free mobile app

Categories

Resources