This has happened to me before, and I had never actually fixed it. Basically what happened was out of the blue, I had no service. I did not do anything to cause this, or at least I don't think I did. I don't know if 4G works, but I'm sure 3G does not. This is all the info I have at the moment (see picture). Last time this happened, I met this guy at my local Sprint store who was cool enough to give me a new phone and make this all go away. But I don't have that option this time, and I would love any help. Thank you in advance.
What did you do before this happened? Did you flash a different ROM? If so, what ROM were you on and which one did you flash to?
I am currently running the latest version of Cyanogenmod, (11/30/13) and when I had updated to today's release there was no sign of the service being gone.
When you go to CDMA subscription in settings, is it set to NV or RUIN/SIM?
How would I get to that in settings on 4.4.1?
Settings>more>mobile networks>CDMA subscriptions
This is what that brings me to.
Hmm network type?
It just brings up a menu to choose either 2G, 3G, or LTE.
I'm not sure but I think the 4.4.1 CM version doesn't have the option. Flash back to 4.3 version and make sure you are set to NV. I think that is your problem.
Installing right now, I'll keep posted
Make sure it is a CM based ROM as the sense based ROMs don't necessarily give you the option either.
After flashing a 4.3 CM ROM and making sure the network mode is set to NV, everything that was in my settings (MIN, MEID, IMEI) is back to normal, except for it still saying it is out of service.
EDIT: 4.2.2 ROM*
OK. Now flash a stock ROM and do a handsfree reactivation. That should get you back up.
Flashing this: http://forum.xda-developers.com/showthread.php?t=2467607 I hope this works.
You sir, are a life saver. I just wish I knew this info when I had my old phone. Thank you very much I hope this helps many other people as well.
Also, I tried flashing the latest CM after all of this, and right after it booted it asked me to insert a sim card. My sim card is in, and I don't know what the problem is there. I also had no service either.
If you are happy with the rom you might want to check with CM devs and see if you can toggle that setting some other way than flashing something else.
RealROGWaffle said:
This has happened to me before, and I had never actually fixed it. Basically what happened was out of the blue, I had no service. I did not do anything to cause this, or at least I don't think I did. I don't know if 4G works, but I'm sure 3G does not. This is all the info I have at the moment (see picture). Last time this happened, I met this guy at my local Sprint store who was cool enough to give me a new phone and make this all go away. But I don't have that option this time, and I would love any help. Thank you in advance.
Click to expand...
Click to collapse
This used to happen to my Galaxy Nexus. The cause may have been the radio I was flashing was a bad download. I would try flashing a new radio in recovery to see if that works...
i removed the default tapatalk signature
Oh, and another thing. What is your IMEI SV supposed to look like? because mine is 00 at the moment.
EDIT: I realize that is normal. I flashed the new radio, and I'm about to see if it works on CM 11
Related
Sorry guys, this is an elaborate one.
So I was running the the 10/19 CM 10.2 nightly and I wanted to fix the GPS issue (and the LTE issue, I feel like I should include that because it might have something to so with the problem). Anyway, the GPS fix asks you to flash back to a sense based rom, download a GPS status app to reset and download new agps data, update profiles and PRLs and get a lock and you're good. After a DAY of trails and errors, got back to stock and fixed my GPS, GPS works fine now. The LTE fix asks you to open of the APN settings using the voice dialer and changing it to one of the LTE ones. I did that, LTE works fine now too. So just when I think I'm in the clear and completely stable, I try to text a friend and the test won't send. I try to call my house and the call just instantly drops, I try to call my phone from my house and it goes straight to voicemail after like a half a ring. I'm starting to think something is just wrong w/ sprint where I live but I don't know. Anybody know what's going on?
So I think I'm just out of luck until s-off becomes available w/ hboot 1.55 or they make a RUU for 3.04. I've tried everything. *sigh* Good thing I don't talk to people, lol.
I'm in the same boat. I tried flashing beanstalk. I noticed I'll have data only if my SIM card is in the phone. If it's not I won't get any data.
Took it to a Sprint store and they fixed it, I thought I was gonna get a new unit for a minute but no, they just fixed it. Funny thing is, my GPS and LTE are messed up again, but I'll live. If that Nexus 5 is under $400 I'm still gettin' it tho...and flashing back to stock (We should have a 3.04 RUU by then) and selling this with the quickness...
kindabizzie said:
Took it to a Sprint store and they fixed it, I thought I was gonna get a new unit for a minute but no, they just fixed it. Funny thing is, my GPS and LTE are messed up again, but I'll live. If that Nexus 5 is under $400 I'm still gettin' it tho...and flashing back to stock (We should have a 3.04 RUU by then) and selling this with the quickness...
Click to expand...
Click to collapse
Here's a fix FYI
cruckus said:
Alright so this is what reenable voice calls. I downloaded omjs ROM from august ( really any stock ROM should do) so I would have the ability to use all the programming codes and update the profile. Obviously do a full wipe( system,data,cache,dalvik cache) loaded the ROM once it got settled and I went past the initial startup stuff I did what's called an "SCRTN" (that's ##72786# on your phones dialer) then hit the three dots and confirmed I wanted to reset the network settings. Also an "RTN" (##786#) won't work because of the custom recovery in case anyone was gonna do that instead. Let the device come back up it should auto activate and go through the hands free activation on its own if it doesn't just go to settings and update the profile you can do the prl too while your doing it just to make sure everything is working fine. Then reload this rom and toggle airplane mode on and then off and there you go. Now this worked for me it may not work for you just keep that in mind but hopefully this helps until they find out what may cause that issue.
---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
Also I forgot to ask did you try taking the sim card out and putting it back in? One other thing you can try is taking a pencil eraser to the back of the sim card ( the golden side) and putting it back in( clean off any pencil shavings) but see if that helps.
Click to expand...
Click to collapse
eastside08 said:
Here's a fix FYI
Click to expand...
Click to collapse
Thx man, next time, lol
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Kraizk said:
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Click to expand...
Click to collapse
Yes, twice
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
I'm going to try this now thanks
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Kdenery said:
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Click to expand...
Click to collapse
Try flashing a CM10 ROM. I've always seen the option there. The kitkat ROMs I have used do not have the option except for the Nocs GE.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
-TheEdge- said:
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i'd kinda like to argue a point here as this just happened to me. i am certainly not new to flashing, starting back with the mogul and having almost every sprint smart phone since then unlocked (windows) or rooted (webos and android).
Using TWRP and previously running ecliptic 4.3 i wiped caches, system and data then installed the 4.4.2 from team d3rp and voila... no service no meid no nothing.... yes i have the latest radio on my phone.
i guess my point in this is that there's a number 3 that you didn't mention.
3. sh!t happens and it's not n00b related.
for anyone else that has this issue... flashing CM 10.1 worked for me. i didn't even have to set up anything, it just picked up signal. so i rebooted, wiped and nandroided back to 4.3 and all is well.
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Robert542 said:
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't... it was SuperOneK. i'm certainly not blaming the rom though. especially not when others are flashing it fine. the ONLY thing i can think of possibly happening is a bad download. I was in a rush and didn't check the md5.
I had a similar problem when flashing miui. Nothing worked. Even went back to a sense backup and nothing worked.
Commit failed as well.
Here's what I did to make it work again.
Flashed cm10. Change the network settings for CDMA. (Boom it SAID I had service..but didn't).
Rebooted a few times (probably not necessary).
Flashed a sense 4.3 ROM that was close to stock.
Update msl and all that. Commit.
For me..changed LTE/CDMA to just CDMA (no 4g in wv).
Boom it worked again. Hope this helps!
Sent from my HTCONE using xda app-developers app
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
EtherBoo said:
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
Click to expand...
Click to collapse
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
dr_w said:
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
Click to expand...
Click to collapse
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
EtherBoo said:
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
Click to expand...
Click to collapse
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
dr_w said:
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Click to expand...
Click to collapse
Alright, so, I have some interesting news.
I got a replacement device from Asurion - not just a replacement, a brand new device out of the box. I pulled it out of the box, swapped the SIM, same exact issue .
I went to Verizon and *****ed up a storm. They basically said "you bought it on eBay, not our problem" (I actually did Swappa - but they don't know Swappa and they do know eBay).
So I got the guy in the store to do some digging, and apparently Verizon has a point opened up with LG as they're seeing this on more and more devices - especially since KK came out. So I figured I could try an older radio. The device was on 12B when it arrived. I just flashed stock to 10B and it's the same issue. I don't know what's going on at this point - nothing makes sense but its apparently a known issue that's been appearing since the KK update.
I'm going to call Asurion and request a new device again since this one is doing the same thing, we'll see what happens. I'm still leaning towards hardware and thinking there was a slew of bad radios that went out.
Just for giggles - and I have no reason whatsoever to think this will work. I'm going to swap out the new SIM that came with the phone. Originally, I just put in my old SIM since the new one was taking too long to activate. I'm having the exact same issue I had previously. With that, I'm going to leave the new SIM in and see if it has the same dropping issue. The guy in the store had mentioned he could swap out the SIM but after a few days it will crap out again... which makes zero ****ing sense. Because of that, I might as well see what happens if I pop a new SIM in. While again, this makes 0 sense, I'm wondering if maybe the phone is frying the SIM somehow?
Again, it makes no sense at all, but I have nothing else left to try other than getting Asurion to repeatedly send me phones until I find one that works or they replace for another type of phone (which I REALLY don't want). I'll drop an edit in an hour or so if what I try makes a difference.
Quick Edit:
I COULD just keep going to the VZW store and have them repeatedly swap out SIMs since it will fix it for a few days .
EDIT:
Got the new SIM installed and it's working. The guy in the VZW store told me that we can keep swapping SIMs and the same issue will happen, which again, makes no sense to me. I'm at a bit of a loss to be honest. I wonder if it's possible that my old device was frying the SIMs (again, makes no sense) and that maybe the new SIM not going in my old device will fix the issue.
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
dr_w said:
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The only ROM I've ever run was CM11.
Same thing happened on stock though after flashing through the LG Flash Tool. Then, with the new phone from Asurion, used old SIM - 3G only. Used new SIM - 4G sticks.
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
rmx36 said:
Anyone have a fix for this? On Verizon and after almost 4 weeks I have lost my cellular service and data. I noticed when I went to check up on my phone right now that it was finishing a boot-up screen and then never had any bars at the top. Dug deeper and found no service at all. Wiped dalvik and cache and seemed to be bars for under a second and then gone. I am on sensei kernel and am thinking about doing a factory reset and reverting to stock kernel. But I really don't want to lose the benefits it came with.
Click to expand...
Click to collapse
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first. EDIT: NOPE! Flashing the stock kernel from the ROM did not do it. Looks like total reformat/flash is next!
markwebb said:
Well, this is odd. After a month of perfect service, I suddenly cannot get LTE, only 3G. Even nandroids of prior ROM's will not boot into LTE. Is VZW LTE down or should I do a total clean reformat? i do have factory images and everything is backed up. Just a pain.
Very strange. I was flashing various ROM's (CM 12 based - am testing for someone) and at one point pulled out SIM and replaced it. I checked to make sure it is seated right since then. Again, no longer get LTE.
Was on Sensei kernel as well. Let me try flashing stock kernel from ROM first.
Click to expand...
Click to collapse
I just got my Nexus 6 and I am also on Verizon and had the cell coverage drop too. I backed up my apps with titanium backup and did a factory reset and signal came back. I only had it for a day and went to Canada and on my way back to the US I noticed the cell bars were gone. I was just rooted and boot loader unlocked and otherwise stock. I read online that others had this issue when they got to places in the US that had little or no signal. I also noticed that under cellular network settings it loads up with Global under the preferred network type even though it has an option for "LTE (recommended)" and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected. With global selected it works perfectly with calls and LTE, so not sure what that means or if my selecting LTE made it drop the signal after going back from Canada.
Yep, total flash of factory image fixed it. Sigh. Early enough in the day for me to get everything set up again.
Same. About to do it too... I've done too many factory resets with this already. Kind of annoying.
I am in the same boat. Had no problems until I flashed bliss 1.5 then was stuck on 3g. Tried a clean flash of Slim and still stuck on 3g. I will try a stock rom but I am not very hopeful at this point. It's looking a like a reformat here as well :/
Ended up having to format everything and start from scratch again. I'm running a stock ROM now and in weary to try another cm ROM
Don't know if it'll help, but try LTE Discovery app in the Play Store. I use it from time to time to reset my data connection.
Having the same issue, running CM12 daily, have been for a week or so. Midday today it drops LTE, 3g data was working, then a few minutes later to no data. I didn't change anything, nothing new installed. I did reboot the phone at some point before this but that is all...
My only fix was to backup via trwp, restore stock rom, factory reset, reboot & let sim activate, then restore cm12 via twrp... it's a 20-30 min fix all said and done.... pita
Maybe its something Verizon is doing, because I didn't change anything and then next thing you know no data. I hope it's a simple fix for CM12 but I see this popping up more the last few days. Hopefully someone will figure it out. I like CM and prefer it over stock but I am not going to do this multiple times a day just to keep CM...
lohonda said:
...and if you choose LTE, global is never an option again until you do a factory reset and it loads with it pre selected.
Click to expand...
Click to collapse
I just checked and global is still an option for me. I've bounced back and forth, looking to see if anything changes..
Same thing has happened to me last night, lost connection to VZW cell and data. Looking at the field test menus, it seems like the SIM/device understand GSM but NOT CDMA anymore. So I believe the issue has something to do with that. Tried everything, but will nuke and repave most likely....also lost Global as well. and LTE Discovery shows GSM stuff nothing for CDMA
Tried the SIM in another device and it works so its not the SIM.
OK I tried a world of things to recover like some of you may have....its something in Userdata because if I flash everything but userdata it wont work. I am going to try and recover from the backup I had before this happened to see if that works....otherwise rebuild from scratch
will post back
UPDATE: So restoring a backup seems to be ok once you get the SIM back.
Having the same issue over here as well... After a month or AI of having the 6, now I randomly drop service where I would normally have full LTE. I almost NEVER get LTE now and am at most on H with a couple bars then it drops out again. Have also.noticed WiFi connection is very shakey.
Any one find a fix?
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
th3g0d said:
I had an issue where i couldnt get my phone to connect any network. Took me long rime to realise, that entering my PIN-number too fast caused the issue xD it unlocked the sim, but didnt let me connect any network... Dunno if this helps anyone, but definetly the most cryptic issue I've ever had.
Click to expand...
Click to collapse
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
quidpro said:
Troubleshooting my wife's N6 here. Your PIN issue doesn't make sense to me because the phone should be connected to the carrier when locked. Are you talking about WiFi? Because that should be connected too when locked unless settings have been changed from their default (ie, turn off wifi when locked/asleep or something)
Click to expand...
Click to collapse
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Edit: OK, just pinpointed MY issue. I have to wait for the "no service" text to change into "emergency calls only" before entering my pin or I don't have any service just the exclamation mark :/
th3g0d said:
I'm talking when you turn on your phone and it asks for pin number to unlock your sim. Some how it seems that if you enter your pin too fast, it bugs the phones radio somehow and you can't connect to your carrier but if you wait like 5sec before entering the pin, it connects to the carrier and the (!) Mark goes away. Try rebooting the phone and see if it helps? Even I think its a weird issue
Click to expand...
Click to collapse
Thanks. I told her about it and she will give it a try, or just remove the pin altogether as a test. It is a weird issue. She is missing important calls from her elderly parents at night and it is rather frustrating. Turning wifi off also seems like a bad fix.
Hello friends,
I have the Z for almost two years now, and have had a issue for a long time; here goes:
A long time ago, I started flashing roms, and everything was all right. After a few months I noticed that I had no H+ any more.
Because I thought that the TELE-2 service was horrible I left it. Eventually I thought I was shut off, and because I'm more of a WiFi user, I left the issue.
Now, after a year, I decided to call TELE-2 and they tried to help me restoring my APN settings. Everything was all right but I still can't use 3g.
I can make calls, but as soon as I turn off WiFi, my network connectivity disappears and shows a exclamation mark.
entering *#*#4636#*#* gives me some information, but I'm not sure what to make of it. Roaming is enabled, HTTP client test gives:
FAIL: IOexeption.
I'm thinking this has something to do with my modem/ baseband?
Can someone point me to a correct thread because I'm not even sure what this issue is called.
Or perhaps teach me how to treat network connectivity issues in the future?
If further information is needed I'll fill it in. Remember, I have some knowledge, but I'm still pretty much a noob!
Bump?
Nyahaha1171 said:
Hello friends,
I have the Z for almost two years now, and have had a issue for a long time; here goes:
A long time ago, I started flashing roms, and everything was all right. After a few months I noticed that I had no H+ any more.
Because I thought that the TELE-2 service was horrible I left it. Eventually I thought I was shut off, and because I'm more of a WiFi user, I left the issue.
Now, after a year, I decided to call TELE-2 and they tried to help me restoring my APN settings. Everything was all right but I still can't use 3g.
I can make calls, but as soon as I turn off WiFi, my network connectivity disappears and shows a exclamation mark.
entering *#*#4636#*#* gives me some information, but I'm not sure what to make of it. Roaming is enabled, HTTP client test gives:
FAIL: IOexeption.
I'm thinking this has something to do with my modem/ baseband?
Can someone point me to a correct thread because I'm not even sure what this issue is called.
Or perhaps teach me how to treat network connectivity issues in the future?
If further information is needed I'll fill it in. Remember, I have some knowledge, but I'm still pretty much a noob!
Click to expand...
Click to collapse
Nyahaha1171 said:
Bump?
Click to expand...
Click to collapse
Well, I would think you have either unlocked bootloader wrongly (usually slight chance) or flashed wrong FTF/ROM for your device.
Now I would suggest you go to STOCK ROM for your device first. You can flash it via flashtool
You would need FTF from general section and also flashtool which you can get from here
http://www.flashtool.net/index.php
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help
Hnk1 said:
Well, I would think you have either unlocked bootloader wrongly (usually slight chance) or flashed wrong FTF/ROM for your device.
Now I would suggest you go to STOCK ROM for your device first. You can flash it via flashtool
You would need FTF from general section and also flashtool which you can get from here
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help
Click to expand...
Click to collapse
Yes, I tried it already, I found a Dutch Generic FTF, flashed it but it didn't work. If I remember correctly there was a option to only flash the Baseband/Radio.
I expected that something like that was broken and that reflashing the original might fix it. But alas, bad luck. Would it be a good idea to learn how to logcat?
Would it be helpful if I provided these?
Thanks in advance.
Nyahaha1171 said:
Yes, I tried it already, I found a Dutch Generic FTF, flashed it but it didn't work. If I remember correctly there was a option to only flash the Baseband/Radio.
I expected that something like that was broken and that reflashing the original might fix it. But alas, bad luck. Would it be a good idea to learn how to logcat?
Would it be helpful if I provided these?
Thanks in advance.
Click to expand...
Click to collapse
I would like you to check on your xperia Z box it's exact model number with baseband and every other detail you can provide. Also, tell me if you got it sim free or had a contract or something like that. Are you on unlocked bootloader ?
Hnk1 said:
I would like you to check on your xperia Z box it's exact model number with baseband and every other detail you can provide. Also, tell me if you got it sim free or had a contract or something like that. Are you on unlocked bootloader ?
Click to expand...
Click to collapse
On a contract, but warranty doesn't matter. Unlocked Bootloader, Rooted, currently running 5.1 Resurrection.
All right, here goes:
- C6603
- GSM/GPRS/EDGE 850/900/1800/1900& UMTS/HSPA Bands 1/5/8 & LTE 1/3/5/7/8/20
- SI 1270-4181.6 NL
- S/N: CB5A1TNCA0
Let's hope this suffices. I presume that by flashing a ROM with wrong Baseband in the
past my phone can't communicate with the towers in my area; because every part of the world uses different frequencies?
Nyahaha1171 said:
On a contract, but warranty doesn't matter. Unlocked Bootloader, Rooted, currently running 5.1 Resurrection.
All right, here goes:
- C6603
- GSM/GPRS/EDGE 850/900/1800/1900& UMTS/HSPA Bands 1/5/8 & LTE 1/3/5/7/8/20
- SI 1270-4181.6 NL
- S/N: CB5A1TNCA0
Let's hope this suffices. I presume that by flashing a ROM with wrong Baseband in the
past my phone can't communicate with the towers in my area; because every part of the world uses different frequencies?
Click to expand...
Click to collapse
Can you check which frequencies your network provider uses ?
Usually it's available on their websites. In the mean time I'll look for a ROM you can flash and see if that helps! We might be going to STOCK ROM !
Also check which model does your custom ROM shows!
In the pictures, you can clearly see the difference in basebands between C6602/03 models.
Hnk1 said:
Can you check which frequencies your network provider uses ?
Usually it's available on their websites. In the mean time I'll look for a ROM you can flash and see if that helps! We might be going to STOCK ROM !
Also check which model does your custom ROM shows!
In the pictures, you can clearly see the difference in basebands between C6602/03 models.
Click to expand...
Click to collapse
All right. I've tried to find out what frequenties my provider uses, asked around on the forum and it seems no one is willing to help me.
It seems they are not willing to disclose frequency information and keep changing subjects; also when other people ask this question.
This might make things a little harder. Also, you advised me to try out stock again, I'm willing to do this, but I have to say:
I hate Google. I hate them more than anything and would like to leave the stock experience as fast as possible.
Let us see what the steps are I should take now.
- Flash Stock ROM/Baseband
- ???
- Profit
As mentioned earlier, I tried this before, and it didn't work. So I must be missing something. Just in case I didn't explain my self well enough;
I can make calls, I can't use 3G/HSDPA. When using network monitor, everything fails, unless I reconnect with WiFi. My Bootloader is unlocked, and I
am rooted. Resurrection Team uses Evo kernel (Which I hate because it's pretty unstable.), However, My issues predate the kernel by far.
It seems I'm really failing in correctly flashing my device, because there always seems to be something wrong.
Either it gets extremely laggy, or it randomly reboots (2 to 3 times a day. Unable to reproduce.), No audio when calling unless on speaker and a plethora of other issues.
This could also explain why my internet doesn't work. But it seems unlikely for me to fail in correctly flashing my device for 2 years, don't you agree?
EDIT: Can't even use *#*#service#*#*, doesn't work like everything else.
Nyahaha1171 said:
All right. I've tried to find out what frequenties my provider uses, asked around on the forum and it seems no one is willing to help me.
It seems they are not willing to disclose frequency information and keep changing subjects; also when other people ask this question.
This might make things a little harder. Also, you advised me to try out stock again, I'm willing to do this, but I have to say:
I hate Google. I hate them more than anything and would like to leave the stock experience as fast as possible.
Let us see what the steps are I should take now.
- Flash Stock ROM/Baseband
- ???
- Profit
As mentioned earlier, I tried this before, and it didn't work. So I must be missing something. Just in case I didn't explain my self well enough;
I can make calls, I can't use 3G/HSDPA. When using network monitor, everything fails, unless I reconnect with WiFi. My Bootloader is unlocked, and I
am rooted. Resurrection Team uses Evo kernel (Which I hate because it's pretty unstable.), However, My issues predate the kernel by far.
It seems I'm really failing in correctly flashing my device, because there always seems to be something wrong.
Either it gets extremely laggy, or it randomly reboots (2 to 3 times a day. Unable to reproduce.), No audio when calling unless on speaker and a plethora of other issues.
This could also explain why my internet doesn't work. But it seems unlikely for me to fail in correctly flashing my device for 2 years, don't you agree?
EDIT: Can't even use *#*#service#*#*, doesn't work like everything else.
Click to expand...
Click to collapse
Thank you so much for your detailed response. We love as much information we can have to answer your queries better.
I was trying to find out your network baseband because this would help me establish which STOCK ROM to flash. To inquire about your baseband, call your network provider from your phone and ask them these questions. Tell them you need to know for a phone you bought internationally and want to know if baseband matches or not. They would tell you in a moment.
I am sure you must know alot about flashing but sometimes, some roms are specific for certain models. Like it might be for a different baseband but not for other. Usually flashing roms doesnot play with your basebands but if you got some home brewed rom which is made over stock, this can actually mess up your device. Same goes for kernels if they are directed at a particular model, and it can act differently.
I am not sure why you blame Google as Sony is responsible for producing this phone so maybe enlighten me a bit ?? Sony has got custom UI , not actually Google.
What I would suggest is that flash an older FTF like KITKAT or Jeally Bean to your device and see if it works. Next if it doesnot, update your device using SONY COMPANION and not flashtool. Sometimes this also helps.
By the way do you have an official Sony care near your place ?
Hnk1 said:
Thank you so much for your detailed response. We love as much information we can have to answer your queries better.
I was trying to find out your network baseband because this would help me establish which STOCK ROM to flash. To inquire about your baseband, call your network provider from your phone and ask them these questions. Tell them you need to know for a phone you bought internationally and want to know if baseband matches or not. They would tell you in a moment.
I am sure you must know alot about flashing but sometimes, some roms are specific for certain models. Like it might be for a different baseband but not for other. Usually flashing roms doesnot play with your basebands but if you got some home brewed rom which is made over stock, this can actually mess up your device. Same goes for kernels if they are directed at a particular model, and it can act differently.
I am not sure why you blame Google as Sony is responsible for producing this phone so maybe enlighten me a bit ?? Sony has got custom UI , not actually Google.
What I would suggest is that flash an older FTF like KITKAT or Jeally Bean to your device and see if it works. Next if it doesnot, update your device using SONY COMPANION and not flashtool. Sometimes this also helps.
By the way do you have an official Sony care near your place ?
Click to expand...
Click to collapse
I blamed Google, because I genuinely hate them. They step on people, and violate human rights many people died defending. But that's a different story. Alas, I eventually flashed Stock 10.3.1.A.2.67; the first rom my phone came shipped with. It didn't work either. I'm starting to think that something might be broken because I don't have warranty any longer that would be a bummer. But let's continue. I can't use Sony update service because my bootloader is unlocked. And last time I checked it couldn't be relocked right? Also, there isn't anything like a Sony center near me.
Nyahaha1171 said:
I blamed Google, because I genuinely hate them. They step on people, and violate human rights many people died defending. But that's a different story. Alas, I eventually flashed Stock 10.3.1.A.2.67; the first rom my phone came shipped with. It didn't work either. I'm starting to think that something might be broken because I don't have warranty any longer that would be a bummer. But let's continue. I can't use Sony update service because my bootloader is unlocked. And last time I checked it couldn't be relocked right? Also, there isn't anything like a Sony center near me.
Click to expand...
Click to collapse
i think you have lost some values from TA backup. Use flashtool to relock it and see if that helps. Did you make a TA backup when you unlocked it ?
Hnk1 said:
i think you have lost some values from TA backup. Use flashtool to relock it and see if that helps. Did you make a TA backup when you unlocked it ?
Click to expand...
Click to collapse
Nope, saw a thread coming by this morning, also about TA partitions. I'm afraid that at the time I wasn't aware yet of the TA. Is this really bad or can it still be saved? When flashing
a rom, does it get overwritten?
Also, the SI number on my box says 1270-4181.6, yet the customization version on the phone states that I'm running 1270-4975_R3B. Even though I found a Dutch version.
Is this correct?
Nyahaha1171 said:
Nope, saw a thread coming by this morning, also about TA partitions. I'm afraid that at the time I wasn't aware yet of the TA. Is this really bad or can it still be saved? When flashing
a rom, does it get overwritten?
Also, the SI number on my box says 1270-4181.6, yet the customization version on the phone states that I'm running 1270-4975_R3B. Even though I found a Dutch version.
Is this correct?
Click to expand...
Click to collapse
TA numbers are device specific and if lost, they can result in WIFI and Bluetooth problems for most users but it is rare. Sometimes relocking bootloader can fix these as well but you said you havenot been able to . Are you connecting in fastboot mode for that using flashtool?
I think you should look at this thread for SI number and try to change it accordingly. Remember only the first link is Xperia Z specific and other links for other devices which might work to change your SI
http://forum.xda-developers.com/xperia-z/general/info-xperia-z-firmware-customizations-t2287283
http://forum.xda-developers.com/xperia-u/general/change-si-easy-t2005562
http://forum.xda-developers.com/xperia-u/general/change-si-easy-t2005562
TA partitions have been successfully repaired by SONY service centres. you can mail them your phone and wait for them to return it back. Make sure you email/call before you dispatch your phone and make details accordingly!
Nyahaha1171 said:
Nope, saw a thread coming by this morning, also about TA partitions. I'm afraid that at the time I wasn't aware yet of the TA. Is this really bad or can it still be saved? When flashing
a rom, does it get overwritten?
Also, the SI number on my box says 1270-4181.6, yet the customization version on the phone states that I'm running 1270-4975_R3B. Even though I found a Dutch version.
Is this correct?
Click to expand...
Click to collapse
Hey I remember that you have not tried this so I thought you should give it a try.
Sony Emma Flashtool
http://developer.sonymobile.com/services/flash-tool/
How to use it
https://www.youtube.com/watch?v=g8azjXu4etI
Try repairing your phone with this and see what happens.
Quote me in case you expect a reply. Good Luck