Database Develop

[Q] Any software that would mess up modem to prevent signal?

Before I buy another used Captivate to swap motherboards, I'd like to know if there's anything else I should look at.
Scenario: Bought used Captivate with bad USB port and running CM9 Beta. Once I finally got my SIM card, I had no network signal (couldn't even find any operators when you search for them). Redid the APNs multiple times though those seem to be for Internet and MMS rather than cell. Wifi works fine. Flashed to CM 9.1 stable. No difference. Verified phone is unlocked. Verified IMEIs match. Verified baseband was listed. Verified my phone # is listed. Flashed to CM 7.1. No difference. I wanted to flash to stock but can't because Mobile Odin won't work with CM's partition layout. Thus, it seems I am stuck with CM or MIUI.
Is there anything in efs or another system directory that could prevent me from getting a signal?

topshot said:
Before I buy another used Captivate to swap motherboards, I'd like to know if there's anything else I should look at.
Scenario: Bought used Captivate with bad USB port and running CM9 Beta. Once I finally got my SIM card, I had no network signal (couldn't even find any operators when you search for them). Redid the APNs multiple times though those seem to be for Internet and MMS rather than cell. Wifi works fine. Flashed to CM 9.1 stable. No difference. Verified phone is unlocked. Verified IMEIs match. Verified baseband was listed. Verified my phone # is listed. Flashed to CM 7.1. No difference. I wanted to flash to stock but can't because Mobile Odin won't work with CM's partition layout. Thus, it seems I am stuck with CM or MIUI.
Is there anything in efs or another system directory that could prevent me from getting a signal?
Click to expand...
Click to collapse
I've been with you on another thread so I know for a fact you've tried all that stuff. But I don't recall did you ever try to flash an new or different modem? If you haven't or just want to try a new one I attached the one I use. Or I can get you the link to a page with a whole lot of others to choose from.
Other than trying a new modem I'm at a loss as to what it could be besides hardware at this point. Btw were you ever able to test your sim card in another phone to make sure it's functioning? Or do you know anyone with an att sim that you could test your phone with?

Things you could try:
1. Turn the flight mode on and then turn it off and see if that helps.
2. Open the phone and see if the antenna's contact points are okay.
3. Open the nv_data.bin in efs directory and see if the value at the offset(you can search for the exact value) that stores the network lock flag is 00. If it is 01 then it is still locked. I know you checked for the lock already but it never hurts to double check. You could also take a look at nv.log and see if there is anything there at the end that might be helpful. You could also check for lock by dialing *#7465625#.

m1batt1 said:
Other than trying a new modem I'm at a loss as to what it could be besides hardware at this point. Btw were you ever able to test your sim card in another phone to make sure it's functioning? Or do you know anyone with an att sim that you could test your phone with?
Click to expand...
Click to collapse
My next move was to flash some other modems actually, but I may wait until after tomorrow (see below). I tried to swap with my SIL who is on the same service but her phone takes the micro SIM. I'll try again Wed night with another choir member that has an ATT S2 I think.
uhm said:
Things you could try:
1. Turn the flight mode on and then turn it off and see if that helps.
2. Open the phone and see if the antenna's contact points are okay.
3. Open the nv_data.bin in efs directory and see if the value at the offset(you can search for the exact value) that stores the network lock flag is 00. If it is 01 then it is still locked. I know you checked for the lock already but it never hurts to double check. You could also take a look at nv.log and see if there is anything there at the end that might be helpful. You could also check for lock by dialing *#7465625#.
Click to expand...
Click to collapse
1. No help.
2. Where are the contact points? I've not found any schematic or disassembly instructions for this phone. I can see the external antennae connector, of course.
3. That was how I verified it was unlocked. All the bits in the appropriate area were 00. I'll have to look at the log file.
How would I dial any service code with no service? It tells me "mobile network not available" once I hit the Phone button.
New Info
I'm really hoping this is the answer to all my headaches the past several days trying to figure out why this phone won't get service. I just spent the past hour on the phone with my OLD carrier trying to re-activate my OLD phone with a different number to give to my son. We had to jump through a bunch of hoops because my old line was still "suspended" because of the port order. It is due to be "deleted" tomorrow. So even though my NEW carrier said activation was complete and my OLD phone stopped making and receiving calls 8 days ago, could the fact my number has been "suspended" be the reason I can't see any GSM networks?

Sadly my SIM worked in another phone but his didn't in mine.
Looks like I have a mini netbook.

topshot said:
Sadly my SIM worked in another phone but his didn't in mine.
Looks like I have a mini netbook.
Click to expand...
Click to collapse
Any luck changing modems?
Sent from my SGH-I897 using XDA

m1batt1 said:
Any luck changing modems?
Click to expand...
Click to collapse
I flashed back to CM 9.1 and then flashed in XXJVU - 12/28/2011

are you getting a good signal strength? that would veify antenna is okay.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

laughingT said:
are you getting a good signal strength? that would veify antenna is okay.
Click to expand...
Click to collapse
I'm not getting ANY signal. It always shows -110 dbM or less and 0 or 1 asu. The seller said the GPS worked fine, but I don't get a lock on that either (but maybe you need to "fix" the GPS with each ROM flash?). I've only been concerned with cell service at this point.
I'm going to pick up another Captivate in another hour. I'd like to root and unlock it right there to make sure it works, but don't think I'm that good yet to do quickly and safely. Assuming it's running KK4, the Easy Root pgm seems simple enough to root. May also try SuperOneClick.
For unlocking, I'd hoped to use Galaxy_S Unlock, but couldn't figure out how to get it onto my micro SD card to load onto the other phone.

The "new" Captivate works. It came with KK4 and a good USB port. I'll flash something onto it soon once I learn how to properly back up everything.

glad your new one works.
re: old phone gps. i think you may need to edit gps.conf in etc folder to set gps mode to standalone, rls the gps wants a network connection. in standalone mode, expect a v long time to lock, like 15 minutes.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

topshot...
While u r on kk4 see this post for gps fix... http://forum.xda-developers.com/showthread.php?p=19422197.
Sent from my SAMSUNG-SGH-I897 using xda premium

If you start the phone without a sim card in it, does it detect its absence and vice versa too? If that functions properly then another possibility could be that the IMEI of the phone might be blacklisted. It might have been reported as stolen. You could call your carrier to find that out.

uhm said:
If you start the phone without a sim card in it, does it detect its absence and vice versa too? If that functions properly then another possibility could be that the IMEI of the phone might be blacklisted. It might have been reported as stolen. You could call your carrier(AT&T I suppose) to find that out.
Click to expand...
Click to collapse
Yes, it detected whether a SIM was in it or not. When I had signed up for the new service it had said the IMEI was OK. I guess that doesn't mean it stayed that way. I would think that would just prevent you from accessing the service, not prevent you from detecting a signal at all. When I picked up the second used Captivate, his SIM card had been deactivated, but it still showed it was getting a signal.

topshot said:
Yes, it detected whether a SIM was in it or not. When I had signed up for the new service it had said the IMEI was OK. I guess that doesn't mean it stayed that way. I would think that would just prevent you from accessing the service, not prevent you from detecting a signal at all. When I picked up the second used Captivate, his SIM card had been deactivated, but it still showed it was getting a signal.
Click to expand...
Click to collapse
Once I had my efs folder deleted while flashing a rom and my IMEI defaulted to some value and it showed no signal at all. I checked IMEI and realized it was a different one and that led me to look at the efs. Once I restored the efs folder from my back up, all was fine again. Therefore I think if your IMEI is blacklisted it could happen and hence made that suggestion to call your carrier. Your carrier might also be able to tell you if your phone made any attempts to register on their network or not.

Atrix HD - Having intermittent signal loss using Straight Talk.

The wife and I have Atrix HD phones that we bought used but in great condition a couple months ago. We purchased the Straight Talk at&t compatible micro sim kits from walmart.com and set up our service. We previously had Samsung Captivates also on Straight Talk and they worked flawlessly. I put in my APN settings and I get data and MMS perfectly but occasionally I get a red triangle where my signal bars should be and my phone says "Emergency Calls Only" and I will wait 30 seconds or so and my signal returns. There is no steady decline in signal that leads up to this. It goes from like 4 bars to a red triangle with a cross inside it.
I live in a fair sized town and have always had 3 or more bars of at&t service with phones in the past so I do not think its an issue with poor coverage. I am attaching pictures of my APN settings.
Any help would be appreciated.

Applehater87 said:
The wife and I have Atrix HD phones that we bought used but in great condition a couple months ago. We purchased the Straight Talk at&t compatible micro sim kits from walmart.com and set up our service. We previously had Samsung Captivates also on Straight Talk and they worked flawlessly. I put in my APN settings and I get data and MMS perfectly but occasionally I get a red triangle where my signal bars should be and my phone says "Emergency Calls Only" and I will wait 30 seconds or so and my signal returns. There is no steady decline in signal that leads up to this. It goes from like 4 bars to a red triangle with a cross inside it.
I live in a fair sized town and have always had 3 or more bars of at&t service with phones in the past so I do not think its an issue with poor coverage. I am attaching pictures of my APN settings.
Any help would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue since switching to to the 4G LTE micro sim. It only seems to happen on mine when I'm connected to Wifi though. I get the red triangle intermittently. This never happened to me until I went from the old sim to the new one. Can't find anything on it yet.

same thing
The same thing is happening to me here as well but using a Net10 LTE sim card (same as straight talk basically). I notice it the most after I complete a phone call. It takes a minute or two to regain service again. This is really annoying. Would like to see a solution to this problem.

So I worked with Straight Talk support for about 5 days, back and forth, bounced to several reps throughout and nothing substantial has come of it. It seems a little better after they made "adjustments" to my account as they put it, but I still get disconnected from mobile data when on wifi.
Don't get me wrong, their support people were very responsive and seemed to genuinely want to help me, but in the end they said "your ticket has been open for more than 24 hours so it has been closed. If you continue to have issues please open a new ticket." Anyone else have any luck on this?

I also was having this problem found that if you edit existing att apn (phone needs to be rooted)with sqlite editor it seems to work fine.
tether also works fine this way.I am still not able to get lte to work with straight talk even with new sim.

Just to follow up. As usual, it seems with ST support, one rep tells me they have some things they can try once I call back on another line and then I get a new rep who says nothing can be done until 10 people complain about the exact same issue I'm having. I'm assured this is an isolated incident...
I went ahead and purchased a new SIM card (looks different than the first LTE card I had) in case I had a faulty SIM. Worked flawlessly for a day and now it's back to the same issue of cutting out completely throughout the day.

same problem here on wifi get red triangle (especially after phone call).
More since i switched from 4g sim card to lte sim noticed that data disconnect from time to time like make impossible to watch video flawlessly...
with old 4g was yes only 4g but never loss a bite....could watch anything also streaming tv.....now it is impossible.....
the end of the month going to switch to old sim and see if the problem is in the new sim cards they tried may be to limit access or is in the new service doesn't matter what sim card you possess..
we'll see...

htchd2fix said:
same problem here on wifi get red triangle (especially after phone call).
More since i switched from 4g sim card to lte sim noticed that data disconnect from time to time like make impossible to watch video flawlessly...
with old 4g was yes only 4g but never loss a bite....could watch anything also streaming tv.....now it is impossible.....
the end of the month going to switch to old sim and see if the problem is in the new sim cards they tried may be to limit access or is in the new service doesn't matter what sim card you possess..
we'll see...
Click to expand...
Click to collapse
Switching to my old sim was my first thought to. However when I tried it didn't work. I called ST and they informed me that once you switch sims, the old one can never be reactivated. On top of that they don't offer the non LTE sims anymore. Such a pain. Hope you have better luck though.

pentjaksilat8 said:
Switching to my old sim was my first thought to. However when I tried it didn't work. I called ST and they informed me that once you switch sims, the old one can never be reactivated. On top of that they don't offer the non LTE sims anymore. Such a pain. Hope you have better luck though.
Click to expand...
Click to collapse
Some one could correct me if I'm wrong here but I'm pretty sure this is a result of ROMS using a 4.4 rom. Modem crashes. If you want to test it run a Stock ROM... If you are already using a completely stock ROM then Idk what to tell you. But same thing happens to me using any version besides stock. And yes only when on WiFi

metalmike6 said:
Some one could correct me if I'm wrong here but I'm pretty sure this is a result of ROMS using a 4.4 rom. Modem crashes. If you want to test it run a Stock ROM... If you are already using a completely stock ROM then Idk what to tell you. But same thing happens to me using any version besides stock. And yes only when on WiFi
Click to expand...
Click to collapse
I'm on a 100% stock ROM, I haven't unlocked my boot loader, just rooted.

pentjaksilat8 said:
I'm on a 100% stock ROM, I haven't unlocked my boot loader, just rooted.
Click to expand...
Click to collapse
Then unlock your bootloader and try flashing different radios from the different stock fastboots we have. Depending on the fastboot I can have next to none or almost full in my bedroom. For me, ATT JB is in the middle, JB Mex Retail is the best, Bell ICS is the worst. ATT ICS was about the same as ATT JB.

skeevydude said:
Then unlock your bootloader and try flashing different radios from the different stock fastboots we have. Depending on the fastboot I can have next to none or almost full in my bedroom. For me, ATT JB is in the middle, JB Mex Retail is the best, Bell ICS is the worst. ATT ICS was about the same as ATT JB.
Click to expand...
Click to collapse
For the time being, I just switched to Aio and so far so good with LTE coverage and no disconnecting issues. If they return I'll try different radios as you suggested.

So I've been with Aio for about a week now and everything is working great (knock on wood). I've had 2 mobile data drops at work with Wifi turned on, but they only lasted for a second and I do have really bad reception here inside the building. Outside of that no issues at all so far. I'll update if anything changes.

[Q] Phone Roams All The Time

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.

Weird issue with no data while making phone calls

Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?

Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475

HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.

The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.

Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933

Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)

Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.

zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.

BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.

Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...

Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.

.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color

Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?

You need to add it in your account then. Easy enough to do online. You want to, "manage features."

Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!

Glad you're all set. ?

SM-N910T on T-Mobile USA in 2023?

I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.

https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.

SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.

Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.

The N910T still supports VoLte.. It is still compatible with cellular networks.