Related
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.
So as of saturday my unlocked TMobile Note 4 stopped working as a phone, and won't let me make calls.
Information:
-Was on Dr. Ketan L3 version of his rom when it stopped working
-Using the N910T on AT&T
-IMEI is fine and not damaged, both numbers match (using *#06#)
-It shows bars, but when I go to make a call "Not Registered On Network"
What I've Done:
-Flashed Stock Firmware via Odin (Autoboot, and F.Time Rest checked)
-Factory Reset after odin flash
-Checked APN
-Set on LTE/WCDMA/GSM
-Searched for Networks, finds them, but when I choose AT&T it takes forever and then finally kicks me out and then in notifications, I get the "Not Registered to Network"
-Did the remove the battery thing, and removed sim
-Went to AT&T and got a new sim, worked for 1hr (sporadically) and then went back to "Not Registered on Network"
-At the store I was on phone with AT&T tech trying to troubleshoot the problem and that is when it was working shortly
-Called T-Mobile and checked to see if they blocked my IMEI number, nope they didn't, couldn't help me out further than that
-AT&T was showing that it was a Note 4 so not having that coming up as a Blackberry issue that some reported, so that's not it
-*#0011# shows service limited, but it is unlocked and everything is fine, the IMEI is good, and all is well but the limited service
-Put it in Airplane mode and woke it back from there after 5+minutes
-cleaned the connectors on the sim (new sim anyways so shouldn't really need them)
I'm running out of options, the only thing I can think of being the problem is that I might have started out using this phone on COD2, and when I flashed a COG2 firmware it didn't like that and so my phone's account settings didn't fully transfer.
Also I was messing around with the bands settings (*#2263#) what should they be on? Automatic, LTE/GSM only, or what?
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
kabuk1 said:
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
Click to expand...
Click to collapse
Thanks, yeah it kicks in randomly for like a minute and then dies, I take it to my parent's house (about 10 miles away) and along the way I get a good signal, but then when I reach their house, back to nothing. I was using it just fine the week prior. I partially blame Dr. Ketan, ever since installing his rom, I had multiple issues. I since uninstalled it and tried going back to stock. Any idea on what a good "safe" band setting is? I have that settings set to automatic, but if there was a good "safe" band that would be great. A common LTE tower. Even when I do connect or get connected, I can't register on that network, my phone won't let me. I've tried that. The bars drop to zero. I damaged my antenna wire (white one) and I just replaced it with a new one I purchased, but the hacked together one seemed to be doing the same quality job as the new one is. It shows the signal, but as soon as you try tying it down to a network it rejects it. I was afraid that when I flashed the stock image via odin it removed the unlock, but it was still there. I just hate that now I have a $500 pda, when it was a phone and now i'm relegated to using a f*ing flip phone.
i think your antenna cable is damaged. the only way to know that is be close to a tower, and see if your work or not.
bought and replaced with new ones, I get full bars, in my bedroom, but apparently they're tied to Tmobile since when I try to register it to AT&T they magically disappear, but when I close the app, they come back at the same strength level. I can't register them to Tmo since the sim. Yet my phone is telling me it's unlocked (*#0011#), IMEI = PASS, 1;
I think the prob is due to the different frequencies.
Your baseband would not be tied to a rom(ie Dr Ketan) Unless that rom contains Modem.bin
Your apn needs to be att if that's your Sim obviously.
International version has a different chipset. .. I know it's not your case. .
But it's open to any Sim. ..
I can say this.. I have a N2 unlocked (tmob) I run an Att Sim it works but the sig is really spotty... COD6/ COG2 may not be lining up frequency wise with your att Sim. ..
Try rolling your baseband back even further. .
Flashvetrin
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
dcoke said:
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
Click to expand...
Click to collapse
Well I would think automatic is out for sure.. the other prob would be after reboot the chipset will search for the default.. but I could be wrong.
I do not know what the numbers would be for band identification.
You may get lucky when calling Att and ask for someone in a higher tier. To give you some numbers for frequincies .
But you have ruled out hardware correct??
By putting a tmob Sim in????
Cuz I know you posted you did antenna work..
And I do know you said you get bars then it fades..
The fact it fades and doesn't lock into even a G band for example. Just leads me to believe the apn can't lock down based on the frequincie and the built in lte chipset...
It would be nice to just flash an att modem wouldn't it?? But don't even think about it.. lol you'll soft brick..
I wish I had a better solid answer you. You may just start testing those different bands and see if you get closer to a lock.
Flashvetrin
U rock, lol. Thx man
My Tricked Out N910P
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
dcoke said:
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
Click to expand...
Click to collapse
Heres
A simple method for COD6
And try odin 3.07
I need to think about this some more and get back to you...
This is a partial firmware.. it consists of the modem and bootloader COD6.
Also to rule out damage if you can get a T Mobile Sim put it in the device and see if it locks down a signal....
Flashvetrin
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
dcoke said:
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
Click to expand...
Click to collapse
You are the first of this kind that I'm aware of.. in regards to this issue..
Make sure you read the detail in if your device bootloops, to reboot recovery and flash the Rom.. if you want flash the Rom in the op that I've linked you to.
Wipe sys/dal/cach/data..
And flash it can't hurt.. [emoji16]
I really hope a Tmob Sim and or COD6 gives you results...and good ones at that.. [emoji2] [emoji106]
Flashvetrin
Got the sim card, $65 for that crap, and it didn't work. Called T Mobile customer service, explained my situation and how I was calling on another phone on another carrier and they insisted on calling me back on the broken not working phone. I guess I'm just screwed, and lost $500, which like I said, I can't afford to have. It's just so frustrating. I also tried the COD6 partial firmware, and nothing there also. I'll try t-mobile again. The only and last option I have, if possible, is to try to relock my phone and re-unlock it since there isn't any real way to tell if my GSM is damaged. I think my unlocked status got damaged when my phone upgraded to COG2, and since it's in that weird limbo state I can't use my phone. Do you know how to relock it?
Edit: When I look at my IMEI Number through *#06# it shows that the last two digits (independent of the actual IMEI number, since that matches everywhere) to the right of the "/" as 14, yet through "about device" it shows my imei version as 10. I assume that the 14 in the "06" screen is the version it's reading off the phone, could that be causing the issue? How would you even fix that? I don't know. but thanks again, you've been helpful.
Hello. First of all, I searched the threads before posting to no avail. So if I'm being repetitive I apologize. But here's the problem. I have a t mobile galaxy note 5. Unlocked. It's rooted. Running an arter97 kernel, and Jovys Darkstalker kernel mod. Everything is running smoothly and has been for months. Recently the only problem is my signal. 90% of the time it is saying searching. When I make a call it says not registered on a network. This is strange because I have done nothing to cause this change. No new roms, mods, updates, nothing and it's been working fine all this time. I know it is not location related because it was working 100% fine from day one until now. I tried *#06# to see if my imei was null, it is not.
I let the phone search, and then choose an operator, that works temporarily giving me signal, but eventually goes back to, and stays searching. I tried to pull up the service menu using *#*#4636#*#* to reset the radio, but that number is not pulling up the menu. I was told I may have a bad efs, but I never created a backup because until now I never had this problem and didn't know efs existed . I don't know what my next step should be. Any help would be greatly appreciated!!!!!!
Sn: if there is already a solution to this problem on this forum send me a link please!
Try using the Shortcut Master (Lite) to pull up the service menu.
I've also got same issue.
My phone is n920c. I've spent all day trying fix this issue by new rom, but I didn't find solution yet.
Kind Regards,
Marcin
Moneyomm9 said:
Hello. First of all, I searched the threads before posting to no avail. So if I'm being repetitive I apologize. But here's the problem. I have a t mobile galaxy note 5. Unlocked. It's rooted. Running an arter97 kernel, and Jovys Darkstalker kernel mod. Everything is running smoothly and has been for months. Recently the only problem is my signal. 90% of the time it is saying searching. When I make a call it says not registered on a network. This is strange because I have done nothing to cause this change. No new roms, mods, updates, nothing and it's been working fine all this time. I know it is not location related because it was working 100% fine from day one until now. I tried *#06# to see if my imei was null, it is not.
I let the phone search, and then choose an operator, that works temporarily giving me signal, but eventually goes back to, and stays searching. I tried to pull up the service menu using *#*#4636#*#* to reset the radio, but that number is not pulling up the menu. I was told I may have a bad efs, but I never created a backup because until now I never had this problem and didn't know efs existed . I don't know what my next step should be. Any help would be greatly appreciated!!!!!!
Sn: if there is already a solution to this problem on this forum send me a link please!
Click to expand...
Click to collapse
Where did you buy your phone? Why don't you check to see if it's blacklisted first (maybe it took a little while to get listed). Never ceases to amaze me the number of people selling stolen/balance owing phones, or the number of people buying them, for that matter:
http://www.t-mobile.com/VERIFYIMEI.ASPX
Very true. I think i may have solved the problem though. My phone was bought outright through tmobile. I try not to by second hand phones for that exact reason.
I think i have may have found my the solution. For me it was a sim card related issue. Apparently my sim card was exhausted, or had expired. This is why my phone kept dropping me from the network and i had to keep reconnecting. Accordind to t mobile your sim expires 90 days of no use. This dodnt apply to me but whatever. Got a new sim, transfered the number, problem solved. Also something else that greatly boosetd my service. Take the case off. This was why i got the searching status in low service areas and only 2 bars of service in good reception areas. Crazy that in 2015 cases still affect service but it did greatly. So yea my fix was a new sim and take the case off. Very elementary. But i can say it was not root, kernel related thank god :good:
Hello, my S5 mini has the first problems 1 year after bought, sometimes there was the error not registered on network. I have sent it twice to the support, but it was returned with "no error".
Now warranty over i have the error not registered on network, and can not use it for telefoning. The IMEI was correct, i can receive the network, but i can not register to it. I have the last marshmallow update flashed over OTA.
in former times, i have to remove the sim and reinsert it, to get it work again, but now this does not work. The simcard ist changed from the provider, and i bouhgt another simcard from another networkk, to test it.
Can i fix this problem?
Garfield62 said:
Hello, my S5 mini has the first problems 1 year after bought, sometimes there was the error not registered on network. I have sent it twice to the support, but it was returned with "no error".
Now warranty over i have the error not registered on network, and can not use it for telefoning. The IMEI was correct, i can receive the network, but i can not register to it. I have the last marshmallow update flashed over OTA.
in former times, i have to remove the sim and reinsert it, to get it work again, but now this does not work. The simcard ist changed from the provider, and i bouhgt another simcard from another networkk, to test it.
Can i fix this problem?
Click to expand...
Click to collapse
Sam here, call me cynical but happened 6 months after phone ran out of warranty. Done all the basics, diff SIM from different provider reset phone, even re-flashed phone and no joy, tried all the modem software going and phone will only work on 2G. Samsung support said take it to repairers hmmm wonder what that's going to cost. New phone, New manufacturer I think. This is 2nd Samsung ive had issues with
I've only just got my first Android phone from a mate after obnoxiously using iPhones for years+, an S5 Mini that lags and ****s itself at every moment. I've now got a gangsaf little unit learning anything I can about this phone and after all my errors, not once have I seen this.
Just for relevancy, I have a G800Y model but I'm using one of the two kernels I could find that looked decent which the devs have listed under G800F and as far as I can tell or what I've read, there's no real difference other than a difference between the LTE bands they can access (someone please correct me if I'm wrong). If it would be so much as to ask what exactly is the software specifications of both of your devices? By this I mean:
- What ROM are you running; [Stock] or [Custom]?
- Have you rooted your device?
- Have you tried finding your device's most recent stock modem software?
- Did anything lead to this or is there anything you believe could have contributed to the occurence of such a problem?
- What carrier are you with in what location? If you do not wish to say for whatever reason, have you tried a search for devices with similar problems and a possible resolution method?
Hello, i have stock rom, IMEI is intact, not rooted,
Basisbandversion G800FXXU1CQB2
Kernel Version 3.4.39-895f4887
Buildnummer MMB29K.G800FXXU1CPL1
AP: G800FXXU1CPL1
CP: G800FXXU!CQB2
CSC: G800FDBT1CPL1
SIM-Card from Telekom or blau.de, both does not work.
I can receive the Providers, but can not connect.
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.