For no apparent reason on Saturday, my touchscreen decided to stop working. I was running the latest WWE iMate ROM, with the .10 Radio installed over the top.
I tried soft reseting a few times, with no luck - so moved onto a hard reset as well. That failed
Having seen someone post a link to a proper T Mobile download for the original ROM for the phone, I thought it best to try that. Unfortunately it doesn't fix the problem, but at least has put my phone back to a state where I can cheerfully give it to T Mobile and claim on the 12 month warranty.
I'm dropping it into my retail store today... but am disappointed it has only lasted 3 months before dying.
It hasn't been dropped, water damaged or anything like that - just simply gave up the ghost.
my touchscreen sporadically stops working (mda pro), but then will start again, if I rub the wider end of the Stylus across the screen quickly a few times.
I'm contemplating taking it back, let us know how you get on with T-Mobile.
Do t-mobile UK give a replacement unit?
Well mine's gone into the store today. Reckon I'll get something back from them by the end of the week. They reckon 5-7 days turnaround, but the phone won't even be sent offsite until tomorrow. (They have collections 2 or 3 times a week I think...)
Its a far cry from Orange where, with Orange Care, having stopped working Saturday, it would have been replaced on Sunday.
Luckily I still have my Orange C500, so I unlocked it, put an iMate ROM on it, and inserted my T Mobile SIM.
No question that it'll be repaired or replaced - but if you rely on the device, a week (or more!) is a long time to be without it...
Had I had the T Mobile equivalent of Orange Care, it wouldn't be sorted any quicker - so at least I can be happy I didn't waste my money with that.
I did try slightly flexing the screen and repeated tapping to try and get it to work again, but no joy. Perhaps the screen IS the weak link afterall, despite me religiously closing it up clamshell before putting in my pocket etc.
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.
So in the last couple weeks my phone has developed a really strange issue. When I put my phone in my pocket for any amount of time more than a few minutes the phone gives me a message saying that I need to install a valid sim card. At first I thought it might be a ROM issue so I tried several different ROMs including stock and have had the problem with all of them. I left the phone on my desk at work all day yesterday and it worked fine. Put it in my pocket to walk from work to my truck and by the time I got in to drive home the message was back. Has anyone ever heard of such a thing before?
Also, just got a new sim card on Wednesday and that didn't help at all.
hi all i have a galaxy s4 usa at&t
i unlocked from at&t now it works on any sim
now the android version is 4.2.2 i want to update to 4.4 stock
now should i use the at&t rom or the factory unlocked rom
or if anyone could help and give me a link to download
thnxx
If you have an at&t i337 use the AT&T rom
Sent from my Nexus 5 using XDA Free mobile app
I'm in the U.K. and have the sim error problem. Phone has never been rooted always on stock.
1st occurrence within 3 months ownership but it got to a point, after a week, where it always read no sim even after restart. Samsung warranty repair changed mother/main board.
Phone was dropping calls after the warranty repair so went back to Samsung. Warranty repair 2. Changed 2 wires, don't know which ones. But now phone was working fine.
3 Weeks after repair 2, the screen went black. I could still hear all tones etc but no screen so can't answer calls (most basic function of phone). Samsung put new screen and another new main/motherboard. So now this is the 3rd mainboard. Phone came back on 2/10/14 after the repair. After 2 days I have again got message about 5 times at a time but restart is solving it for now.
So I think the problem lies in the faulty mainboards Samsung are manufacturing. Why? Because my 1st board failed and eventually always had the message no sim inserted. The engineer report said main board was changed. If it was too do with a faulty sim tray then wouldn't they have fitted one of those instead. 2nd board worked fine even though calls were dropping. This board was in phone for 3 weeks until screen got changed so I'm presuming had to change board along with screen. The latest main board which is apparently new has lasted 2 days. Like I said above its only happened a few times so far but I rather it happen all the time so I can send it in again.
I have spoke to Samsung UK escalation and they said if I require another repair then they will take it higher up but even with an exchange what is there not to say new/refurbished S4 wont be faulty down the line.
What is Samsung doing about this, absolutely nothing. My worst ever experience with a phone and I got a s 1,2,3 which all still work not even a glitch. Will buy another phone but keep fighting for a resolution with this one. Still has 17 months warranty.
Facts: I'm in the US, have an XT1575 that I'm having issues with, Carrier is Verizon (Nano Sim).
So, I had a MXP (SE) for about a year and a half, no issues, going great. So, about 2 months ago, I drop it, cracked screen, and a botched replacement job, I picked up another one, used on eBay.
It arrives, I unlock it the bootloader, throw the latest TWRP and updated to the latest Cyanogen nightly, and get No Service. Wifi works, no cell signal voice or data. Won't connect to the network, put stock back on it, went to verizon, got to tier 2 tech support, they said they don't know what's going on.
Is there any way anyone knows how I can fix this, been googling around and the answer for many was to just flash back to Stock, I've been fussing around with the 2 different stock firmwares, several custom ones, and am all out of ideas. Would really like to have a working phone again. For the record, I can still fastboot and navigate my old (same model Moto X Style (Pure Edition) 16GB), though half the screen is gone in case that might help in getting this off the ground.
I'm at the end of my rope with this after 5 days of wrangling, thanks.