Database Users

i337M Abrupt Signal Loss

Hi everyone,
So about five days ago I was in the middle of using my Galaxy S4 (I think I was playing a game or something) and all of the sudden my cellular signal dropped out completely—from 4 bars to zero with a little X in it. There it's remained ever since.
My first thought was that I ought to reboot the thing and see if that would solve anything. The answer was no.
My second thought was that maybe my contract was up (as that was due to happen this month), and rather than auto-renewing, they kicked me off. Weird, but possible. But that's not it: I phoned up my provider and they said that all systems are go, there are no outages, your account is active for a week still, and even past that contract expiry I'll just get bumped to month-to-month and never experience a blip in service. So that's not it.
So then I put my SIM in another unlocked phone, and lo-and-behold, it connects just fine. So clearly the problem is with my phone.
My i337M is running Liquid Smooth 2.9 and KToonSez' kernel. I decided to make a nandroid and flash back to stock ROM/kernel. Still I could not connect to the network.
I can only think of two potential problems. First, I unlocked the phone myself via FastGSM.com's tethered USB method. It was a Bell-locked phone, and I'm on Rogers. This was accomplished back in July, and since then, there haven't been any issues to speak of (i.e., the unlock worked flawlessly). I tried to see if those unlocks ever expire, and couldn't find any reason why they ought to. I personally don't think it's that, but I mention it out of interest in being thorough.
Second, I messed around with my phones NVData a few weeks back to enable the AWS network via this method. I didn't experience any signal problems after doing so. Again I mention this out of interests of being thorough. Could that have had something to do with it? I suppose I could try flashing back my original NVData, but honestly I don't see why that would suddenly kick in now since I did it weeks ago originally.
Any thoughts? This is really bizarre, and it sucks being without connection.
I was also thinking of flashing back to stock and going to a Bell shop to see what happens when I put a tester SIM in.

It sounds to me like it's hardware related. Don't see anything you've done that would have caused it. I'd flash back to stock and if it still persists I'd file a warranty claim.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Hi, thanks for your reply.
An additional thought's occurred to me: I lost signal at or about the same day I setup Android Device Manager to allow for remote lock/wipe directly from Google. That couldn't possibly be responsible for signal loss, could it...?
Currently flashing back to stock, and I'll unroot/restore kernel/restore NVData and make it look factory, and see what the store says about it. Hopefully I don't have to pay for another unlock at some point.

Okay, this is very messed up. Nobody has any idea why my phone isn't getting signal. I can scan for networks and everything shows up, but in any case with any SIM it says "unable to connect to network". It doesn't matter what ROM I'm on. I flashed back to stock and updated to latest using KIES of all things, which found a firmware/modem/baseband update, and still no dice. I don't know what to do with this thing except take it to an unlocking store that might be able to figure something out for me, but it'll cost me. This is messed, I've never had to get someone else to look at my tech for me.

Okay, so the situation is that it most probably is a hardware failure related to the radio.
I am a Rogers customer who bought the phone from a guy from CraigsList who apparently got it from Bell. I went into Bell and explained the situation, and they scanned the IMEI and printed me out a proof of purchase of the guy's name and told me I should take that to the Bell service centre, and it doesn't matter if I'm not the guy. I also had them check to see if he reported the phone stolen; it turns out he did not—though it should be known that if he had done so, then that could have very well been the reason I wasn't getting signal from anyone, as all providers across Canada apparently share their blacklists with one another now (including the little guys like Wind/Mobilicity).
So now I am in the process of making it look like it's never ever been hacked before: I shall restore my NVData, unroot, and update everything using KIES, and then perform a factory data reset. I'm also on the hunt to figure out what the heck the "flash counter" is and whether or not I need to reset that, but perhaps since mine is the i337M Canadian variant, I don't need to worry about that. (Any advice on restoring my phone to factory condition would be welcome, thanks.)
Edit: Figured out TriangleAway and everything associated. I'm all stock now and ready to bring it back to the factory.

MAJOR UPDATE: PROBLEM IDENTIFIED
So I got my phone back from the factory today. They reported that everything is 100% a-ok on the hardware/software side of things. The radio IC is NOT blown as was suspected.
You know what they said? The problem is on the network. I have a story to tell that I think people should hear, as I've learned something very valuable today and people need to learn this lest they get conned themselves.
Today I phoned in Rogers again, armed with new information, to ask what's up. They ran the IMEI number, and this time... it's come up on the blacklist.
It wasn't there last week. In fact, it wasn't even there an hour ago. It actually only appeared there as the clock ticked past midnight Eastern time... as that is EXACTLY 90 days from when the phone was reported missing. It took them a long time to track down this information.
To reiterate, I did not steal the phone. I bought it from a guy on Craigslist who had it brand new in box with the screen-protector sticker still on the front of it. I checked it out, tried it, and unlocked it myself and have been using it since July without issue, until a week ago.
There is the trouble of, why now? Why only now does the IMEI come up blocked? What the senior rep at Rogers thinks happened was that the guy had it delivered to his house, didn't sign for it, kept it in box, reported it as "undelivered", and flipped it to me for cash. Insurance has meanwhile hooked him up with a new phone, and the factory kept my phone in the "we're looking for it" pile for the requisite 90 days, after which they officially publish its IMEI as "blacklisted". That would explain why it worked for a while but doesn't now; and this 90-day TO THE DAY period is the same for Rogers as it is for AT&T apparently (which is where the rep used to work for 10+ years).
I am in possession of stolen property. I've little hope of recuperating my losses. I've been advised to file a police report, and I think I will actually, given that I've got a receipt with the "anonymous" guy from Craigslist's name on it which I had printed out from Bell after they scanned the IMEI number for my factory warranty receipt. This phone will officially never work in Canada, as there is no way for it to be removed from the blacklist. I've been very unfortunate in this case, and it's a real shame.
People should take note: If buying a phone, ALWAYS do it in-store and have the IMEI number run first to check and see if it's on the blacklist. Next, have the phone transferred into your name so that the IMEI and you are officially linked, and the guy can't report his gear stolen or lost. That should suffice in most cases... except in the case of insurance fraud, which is my case, where there is a 90-day delay period in the IMEI number being added to the blacklist (which is why it didn't come up on the blacklist last week when I had the Bell rep run it in-store for me). Another point of interest is that in my case, I found it was possible to lose service BEFORE the number is on the blacklist—assuming the Bell guy didn't run the number wrong last week.
So f**k me. All I can do is try to hack the number, I guess, or find a way to spoof the IMEI.
Edit: Unf***ing believeable—I somehow reenabled data and texting by messing around with QPST. Calls still not happening, though.

Help please! SiM card not working

Good morning, my phone card suddenly stopped working on the network a few months ago. I believe I may have disabled some things here and there the night prior, I can't remember. I was moving from Germany to the U.S. the next day, so I had alot on my mind. This is the European variant (SM-G935F). I have tried 3 different SIM cards, one from German T-Mobile and two from Verizon in the U.S. to no avail. I have posted screenshots showing what it says I have for signal. Every once in a while it pops up with a message saying SIM card refreshing or something like that. I have tried putting a piece of paper by the SIM card because possibly the contacts were lose and I also factory reset my phone but nothing works. To send it back to Germany to have them fix it is very expensive and also I don't want to try and interpret everything. I have done that for the last 3 years and would probably end up signing a lease for a car with my limited German language skills. Any thoughts? The phone is perfect other than this issue and I am about to put it on Ebay if I can't get it squared away.
Thanks in advance for any thoughts!
Yandawg

did you try to root it and put the bootloader and firmware of t mobile or verizon?

I haven't tried that because I wanted to keep it unroofed if I needed to sell it on eBay. I might try that as a last step before I sell it though

try to flash your phone with smartswitch or odin with original rom if you are skilled, reset seems cannot recover all your settings.

[No service] rooted v20 h910 connection issues

I bought an unlocked h910 on ebay a little while ago and rooted it the day I got it by following the typical root guide. Everything seemed to go smoothly with rooting, and I have SuperSU and the stock rom. I have had terrible connection problems ever since rooting. I never actually used the phone with a sim before rooting it (my other device takes micro sim and I didn't have an adapter, do I got a nano and activated over the phone after rooting). As soon as I put the activated nano sim in, the phone would lock onto a tower and continuously drop and say "No service", then lock again, repeat repeat.
After a little while, the phone magically fixed itself and was working OK for the rest of the day. Then the next day, I started getting the No service problem again. I tried lineageOS with the werewolf kernel, but that didn't quite work out due to crashes. So, I figured I would do the typical restore procedure from this thread:
https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060
That went through OK, and I figured everything was fixed, but then I started getting the No service problem again after a little while :crying::crying::crying:. At that point, I decided to do some reading and it appears that some folks with unrooted phones have had connection issues on the v20 that they got warranty replacements for. I am concerned that there may be a hardware problem that is causing the No service issue if other people have experienced this too. Unfortunately, since I never used the phone with a sim before rooting it, I don't know if it was working correctly before rooting or not. I can say that it was sold as "new, sealed box", however, with original packaging.
Now I am at a bit of an impasse. The service on the phone works sometimes, but is not reliable enough to be usable, so I went back to my other device and have had the v20 sitting around doing nothing for a bit now. I am tempted to send it back to LG for repair, but it has clearly been rooted already and since there are no kdz files available for the h910, there is no way to revert to complete stock. So I suppose I am hoping someone can give me some ideas here. I have been trying to figure this out for weeks now and haven't had much luck. As I see it, here are the options:
1. Perhaps this is a software problem that someone on the forums knows how to fix, which would be ideal. I have seen some threads regarding modem settings, but none of the ones I have seen apply to the h910.
2. If this is a HW problem, I could send the phone back to LG as rooted and effectively guarantee I will have to pay the repair cost. I have no idea how much that will be, but I would like to avoid it.
3. I could intentionally brick the phone and send it back claiming that it bricked itself. Seems ridiculous, but I have heard of this before.
4. Sell the phone as rooted. Haven't had much luck in that regard yet.
I must say that having a very unreliable phone has not been a pleasant experience so far. Can anyone offer some advice?

Does anyone know if LG is going to make a fuss about the phone being rooted if I send it back to repair? Can they at least reflash it to stock kdz for free?

Radio / SIM stopped working

I bought two E4s (perry xt1768) direct from Motorola the day they were released for my kids. My daughter's went on Sprint and my son's went on Cricket. Around 11/1 my son's phone stops getting any service. Two weeks later my daughter's phone does the same. Neither phone shows any service or will recognize a SIM.
Anyone else have this problem?
I'm sending them in on Monday for warranty if I must but both have seen some bumps and scratches so I'm worried they won't cover it.

Same here. Have had about two-months. No event that I can point to, received a call fine, put back in pocket, noticed I hadn't heard from anyone or received any texts in a while (about an hour and a half), checked phone and no connect. Doesn't recognize SIM. Tons of info online about this issue, usually happens around 2-months into ownership. Can't seem to find anything about this issue here on XDA??

SOLVED: OP6T no network (Coaxial connectors)

Its rare that i have an issue i cannot solve on my own, but this one has me stumped. last friday, i took the newest update on my OP6t 8/256 to 10.3.10 (unlocked, bought from OP directly). After the update, i lost cell service.and signal. i am bootloader unlocked, and eventually ended up using msm tool, which did not resolve my issues, despite wiping and relocking my device.
now, i am back on 10.3.10 and i only have some service when i am on wifi. i have cleared network settings and also manually added Tmob which errors out. i have tested the sim in my old Axon 7, and it works perfectly. also, the settings menu appears to show another update still, but it is not clickable. anyone have an idea? Thank you in advance for any help!

On that last screen where it shows your MAC address does your phone still have a IMEI ? (Don't post it, just it should have a number, yes or no?)

OhioYJ said:
On that last screen where it shows your MAC address does your phone still have a IMEI ? (Don't post it, just it should have a number, yes or no?)
Click to expand...
Click to collapse
It still has both of them. (Dual sim). I have an axon 7 that lost it's EFS partition, so of course that was one of the first things I looked at. Having had that happen before, that was one of the first things I backed up when I got my fajita in 2018.

well, even a new sim card did not fix whatever has gone awry....
update: i took it apart, and pulled the shield over the board. tapped around. put sim in, it didnt work. rebooted with the sim still in and it worked almost all day. set it down on my desk, network disappeared again. pressed on the back just below and to the left of the camera hump, and it came back. worked for 5 min before stopping again. picked up a op9. but i will attempt to fix it later down the road. im guessing either the antennae is loose (checked all coax to ensure they were seated) or one of the multitude of drops, albeit in a good case, broke something beyond repair.

Update: after ordering a new sim reader and evaluating the phone some more, I realized the signal antennae was on the verge of breaking. Moving it with a nylon spudger finished the job.

Update 2, replaced snapped off gray coaxial and still had no network. Realized the other coaxial connector had popped loose and felt like it was seating, but it waant. So issue resolved not at all the software. It was the other coaxial connector. It felt like it was seating, but was not. Fixed and working well now. Woot. Thank you anyone who helped!!