Hey guys, I've been searching for a new ROM for a while now, I was running pure nexus on 6.0.1 but obviously that's been updated and that's where I ran into my issue. Pure nexus seemed to work fine for me and all was well but, slowly as the ROM became outdated and everything moved onto 7.0 my battery life and quality seemed to get worse and worse. Eventually my phone was randomly turning off at 60-70% battery. So, I figured it was time for a new ROM however, when I installed the Nougat version of pure nexus I was unable to receive cell service and data. Now I'm assuming this is due to the fact that my phone is tied to Credo Mobile, for a carrier and they have some funky proprietary firmware they put on their phones. So my question is, does anybody that is on Credo know of any ROMs that might work on our phones, and/or does anybody know what could possibly be going wrong? I've tried quite a bit of troubleshooting, flashing the stock bootloader and radios, editing my APNs to match the ones I could find online for Credo, I've tried multiple different ROMs including OctOS, Carbon, Zephyr, CM, and many more, and of course the other troubleshooting options such as updating recovery, supersu, etc. I am completely stumped, and any help is appreciated. Thanks!
Every nexus phone comes unlocked even when purchased from a carrier, so there should not be any proprietary firmware on your phone from the carrier. My guess is your EFS got messed and thats why you arent getting any cell service. Goto settings and check if your IMEI is displayed. If it is a 0 then your EFS is the problem. Also did you revert to the latest stock version and see if the problem still existed? It can be found here : https://developers.google.com/android/images#hammerhead
I'm fairly certain my service still works on stock, I haven't checked in a while, but I'll do that just to be sure. I doubt all of that really helps but I figure you know more than I do haha. To further explain I also seem to be able to proc my service to work when I switch airplane mode off and back on again, but only for a couple seconds and it craps out after that. It at least detects the SIM card, but no service whatsoever. I'm thinking it could possibly have something to do with the APNs but, I've tried so many different combinations of different Credo APNs online I'm not sure that's actually what's wrong.
Edit: I should also add that on the Credo SIM card under mobile networks in the settings there are carrier settings where you can choose to update your PRL and update your Profile. When I do this the PRL successfully updates but the profile update gets stuck on "The network is preparing your services."
Okay so I reverted to stock and after successfully updating my PRL and Profile I was able to verify service and data are working perfectly. Getting an average of 4-5 bars.
Related
I have an HTC Desire. The first one, not HD or Z etc. I rooted using Unrevoked3 and since then tried, with no success, to flash various different ROMs.
The problem I'm having is that right after first loading the ROM, an unending barrage of force close messages flood me (the process com.android.phone has stopped unexpectedly. Please try again), and there's no signal. By struggling my way through all of these FC's, I manage to get to the wireless and network settings and I notice that the Airplane mode switch is being turned on and off repeatedly. The bottom option for the network settings also appears to be going in and out of "greyed out" mode. The only way to stop the FC's is by somehow managing to press the Airplane mode button at just the right time so that it stays on. Once Airplane mode is on, there are no FC's but, also, still there's no signal since it's airplane mode. I can, however, turn on my wifi and internet works perfectly.
So obviously the phones inability to connect to my network is what causes all of these FC's. The question is why?
I have tried several different ROM's, among them a few versions of Cyanogen including the latest one and the latest CM6, Oxygen, DevNull... All had the same issue.
I am wiping my Data, cache and Dalvik Cache before every flash. I tried running Fix Permissions from ROM Manager. I even tried flashing several different Radios. Nothing works!
After restoring my official rooted Sense ROM, everything works perfectly. What the hell is in (or missing from) these custom ROM's that prevents the phone from connecting to my network??
Please, Please help! It's driving me crazy...
Finally got it sorted. The solution seems a bit weird.
It seems that that the cause of the problem was the USIM card that the network provided me when I signed up. It worked perfectly fine with the stock Sense ROM, but once I tried any other ROM, the phone just couldn't connect to the network. After replacing the card with an older version, it suddenly works fine with Cyanogen. It doesn't seem like my card was defective because the same thing happened to a lot of other people with that same USIM model.
Any idea on how is it that a certain SIM card just wouldn't work on custom ROM's, but would only work on the stock one?
ToastMan12 said:
Finally got it sorted. The solution seems a bit weird.
It seems that that the cause of the problem was the USIM card that the network provided me when I signed up. It worked perfectly fine with the stock Sense ROM, but once I tried any other ROM, the phone just couldn't connect to the network. After replacing the card with an older version, it suddenly works fine with Cyanogen. It doesn't seem like my card was defective because the same thing happened to a lot of other people with that same USIM model.
Any idea on how is it that a certain SIM card just wouldn't work on custom ROM's, but would only work on the stock one?
Click to expand...
Click to collapse
Hi ToastMan,
- from which provider is your SIM card? Tmobile, eplus, ...?
- is your Desire SIM-locked (probably not, but how knows ...)?
- from which provider was the working SIM card?
I also have the original Desire and all of the yet installed ROM's (a lot!) worked.
I'm on German Tmobile, last year on Vodafone, never had any problems.
My phone is unlocked. I'm from Israel, so I'm using an israeli provider called Cellcom. Both the problematic and working sim cards are from them. Its just that the one I replaced the bad one with is an older version.
ToastMan12 said:
My phone is unlocked. I'm from Israel, so I'm using an israeli provider called Cellcom. Both the problematic and working sim cards are from them. Its just that the one I replaced the bad one with is an older version.
Click to expand...
Click to collapse
I'm getting old, thought you are from Germany. Maybe I need new glasses Sorry for useless provider questions/info from my first post.
I searched a little bit around in XDA but couldn't find anything which could help. And my knowledge with errors related to SIM cards is very poor.
On ROM side:
You wrote it happend on every custom ROM. Where they all AOSP (=without Sense) ones? I never read that anybody had SIM problems installing different ROM.
Or do you have a CDMA decice and not a GSM model? Than there will be a big problem if you flash a CDMA ROM on a GSM device and vice versa.
They were all AOSP. I never tried Sense based ones. And yes, I paid attention to what ROM version I was downloading. I have a GSM device so I downloaded GSM versions.
Oh boy. I've done something ..interesting.. to my new nexus s. Could you guys help me?
Okay, So I've been running miui for about a month now, and today I decided I will try the oxygen rom, along with a new radio (K3B). I flashed the radio over miui and all was fine.
Next I wiped and installed oxygen. No service. I couldn't even view available networks. I had a play around with the service menu (*#*#4636#*#*) and changed regions etc, but no luck.
The next thing I did was to try and revert to stock, by following the unlockrs guide (http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/). This seemed strange to me, as it was only a nandroid backup. Now I'm on 'stock' with no cell radio and a small wifi only tablet.
So, my real question is, can I fastboot or ODIN back to complete stock (radio, system, recovery, etc) or are there any other fixes for this problem?
Thanks! I'm desperate :S
Which Nexus S you got? Which ROMs you flashed exactly? Which radio did you flash, never heared of KB3b?
I'd assume you have a i9020T (since you used the GRH78 nandroid backup)? Then you could use the ROM in my sig to flash back to stock.
However, I never flash any nandroid backup that isn't my own, especially if they are crossing release numbers, eg 2.3.5 to 2.3.3.
I have the i9020T, flahsed the XXKB3 Radio (see here: http://forum.xda-developers.com/showthread.php?t=1116884).
I don't think flashing back to stock helps too much
Go here and get yourself a flashable full ROM for the i9020t, it will include a fitting radio (and a stock recovery). Remember to wipe everything before installing the ROM via cwm recovery. I'd also format stuff in "Mount and storage" (except sdcard for obvious reasons ).
Tried that. No success. I also used ODIN to revert to stock again. No success. Tried all the radios available for i9020t, none of them work.
My IMEI is intact still, my baseband /should/ be working, I really don't see anything more I can do except assume its a hardware issue. I'll give samsung a call now and see what I can do. Thanks for your help.
Maybe your carrier banned your IMEI for w/e reason.
Sent from my Nexus S using XDA App
I've tried multiple sim cards, and even if my carrier did block me (why would they do that?) I would still be able to at least view other network operators (and mine) in the Mobile networks menu.
Well multiple sim cards NOT working in your device could mean your IMEI is banned. Carriers block IMEIs for several reasons, stolen phones, contract abuse, carrier crossing, unpaid bills, etc etc.
Contact them and ask. If they didn't block anything you're still one step closer to solving the problem, next step exchange the SIM card, final step would be to contact Samsung and have them check for faulty hardware.
I'm starting to think thats the case.. My original sim card is dead and won't work in other phones now.
What I really don't understand is why they would blacklist me. I've been with my carrier for two years, since they started up. I'm a prepaid customer, so no unpaid bills. My phone is brand new, purchased it at Best Buy in the US four weeks ago
Maybe they were mistaken? I'll call them later in the day.
Ugh. I talked to my service provider, they said they couldn't do anything and were very unsure. They handed me over to samsung, who were unbelievably unhelpful and told me to turn my phone off and on, and that they couldn't do anything more. Just sent an email to my service provider hoping I get someone more 'higher up' who can deal with it.
A few weeks ago I started having signal losses on my D820, later on it stopped detecting my SIM card altogether after I reset it.
It's been going on-and-off until about 2 weeks ago when a factory reset and cache wipe seemed to have fixed the problem - or so I thought - until it happened again today in what seems to be a permanent metamorphosis of my phone into an over-glorified 5" tablet with NFC.
So I started snooping around the googles, seems to be a common problem.
(can't post links yet but google isn't lacking results under "nexus 5 no sim no signal" and "Nexus 5 SIM not recognizing")
So far none of the "Turn airplane mode on and off" or "Reinsert the SIM / clean the slot" tech support quotes helped. The phone is physically intact, and none of the 3 SIMs I have in my disposal get any signal on the device in the rare case they even get recognized (My brother's G4 works fine with all 3). I did a few full factory flashes - ROM, Radio, recovery, everything (M4B30Z - latest 6.0.1, MMB29S, and even went back to 5.1.1 LMY48M). Also tried the latest CM13 snapshot, later on with a factory radio image on top but absolutely nothing. The CM ROM managed to consistently read the SIM but it didn't get any signal.
I would highly appreciate any information or insights, and even though I'm not exactly an expert I will be more than happy to help troubleshooting this jazz.
The phone shows the correct IMEI#? Phone is not blacklisted for some reason?
audit13 said:
The phone shows the correct IMEI#? Phone is not blacklisted for some reason?
Click to expand...
Click to collapse
No reason to believe it is. Had it for over a year now, came unlocked without any contract with in closed packaging from a trusted retailer, IEMI was fine on the day of purchase.
It shows the correct imei via dialler?
Did you check imei on blacklist checker on swappa? Not likely to be blacklisted but you may as well rule it out.
If it's not blacklisted and can't be resolved via flashing roms, it could be a hardware failure.
The IEMI is fine and the phone is clean.
It could be hardware but that doesn't explain the problem being temporarily solved for quite a while by wiping the system, and a lot of the users complaining stated they started having the problem after upgrading to 6.0.1.
I've been running on stock unrooted MM for a while with no problems. A couple of people at work also run stock MM without an issue. I wonder if the problem is related to a particular batch.
Hi all,
Phone was working fine but after upgrading to Android 7 I'm unable to place calls. it says "Emergency calls only" and when I try to place a call I get " Not registered on network".
- Phone was working fine prior to upgrade
- Tried different ROMs and got same result
- Tried another SIM card. Same problem.
- Used my SIM on another phone. Works fine
I read somewhere that this has something to do with the modem certificate and that the only way to fix the problem is by getting a Z3X or Octoplus box to connect to the phone.
Can anyone shed some light on this? I've been messing around with it for the last couple of days but still no luck...
Thanks in advance!
IMEI blocked, phone reported stolen, lost or contract not paid
*Detection* said:
IMEI blocked, phone reported stolen, lost or contract not paid
Click to expand...
Click to collapse
I don't think it's like that. It may be, but it's not sure.
If OP said that phone was working properly before the update, I think that his EFS partition's got messed up.
If you have a total TWRP backup or an EFS backup, try to restore it.
If you still have no luck, your only option is Octoplus Box or such things.
Second hand phone right?
Mine is second hand phone, as well. 930S. Have had the same issue when I've flashed to 8+ ROM, and moving from no cell coverage area and then back into cell service area. I'm able to to a service search and it will find the towers and upon selection will connect back up.
If I flash to a different ROM, about same issue. As long as I remain in service area does fine. Skip out of the area and I may have to re-search.
I'v flashed different CSC's, no change really, except when I flash an AT&T CSC, then it seems to stay locked on a bit better, though with AT&T CSC I am unable to enter phone codes, so I went back to 'stock' (Korean phone Chinese regions). Stock has no CSC directory present in the root/system directory, which is interesting. I leave the Chinese regions unchecked and the phone finds local towers, US west coast, AT&T networks, T-Mobile, etc, just fine, overall. It's just on very weak signal or no signal that I may occasionally have to do a re-search when I'm back in a coverage area.
Your's sound much more a PITA.
So, I have an S10e (SM-G970U) that was bought from Verizon a while back. The phone was set up on a Verizon post-paid plan, but was later switched to prepaid. The phone worked fine for months, but about a week ago, the phone randomly stopped making and receiving calls, texts, and the ability to use mobile data. It was taken to Verizon, and they tried "all they could" in their words, which included a new SIM card, resetting network settings, and eventually a factory reset from settings. Nothing seemed to work, and they gave up, claiming it "seemed like a bad antenna." They did call their "tech support" who claimed the most recent Android 11 update supposedly caused an issue with mobile network connection with the Verizon S10e devices, which I haven't heard of, but didn't know. He claimed a reset would fix it.
Since none of that fixed it, it was taken to a shop to be inspected. They claim the phone has nothing wrong with it. So, that, in theory, rules hardware issues out. Their only claim was that when an AT&T SIM was inserted, it was able to connect to the network, but never tried to make any calls due to the SIM not being activated. I assume this is due to someone trying to "help" inserting an activated AT&T SIM into the slot when testing, which I assume ended up installing the carrier branded version of the firmware. They gave a couple possible reasons, but neither seemed to make sense.
Since it had the AT&T bloatware and was working with only AT&T SIMs, I decided to flash both the VZW G970U firmware (the earliest version I could to ensure the supposed "issue" from Verizon support wasn't a problem) and the G970U1 firmware. Both firmware flashes have seemed to have done nothing, as the phone is still having the issue. Most times, it will connect to the Verizon network, but the signal seems to rise and fall quickly (like the bars going from 5 to 1 to 3).. Still no calls, texts, or data, though. I have no idea what's going on, at this point, honestly. Any ideas?
Hardware problem
iBowToAndroid said:
Hardware problem
Click to expand...
Click to collapse
LanGar21 said:
Since none of that fixed it, it was taken to a shop to be inspected. They claim the phone has nothing wrong with it. So, that, in theory, rules hardware issues out.
Click to expand...
Click to collapse
If the people it was taken to were competent and did their jobs correctly (one of the best around, according to reviews and carrier recommendation), their diagnostic results show no hardware damage to the phone. Then again, their explanation for the problem was that it had been locked to ATT network (a Verizon bought phone that never had any affiliation with another carrier, aside from Verizon and a month-long stint with Straight Talk). Some idiot she knows that used to work for a Verizon retailer popped his ATT SIM in there, and it flashed ATT firmware.. Their POSSIBLE solution was to try and have it network unlocked from ATT. As we know, though, the IMEI obviously did not change, and the process of confirming the identifier is done on the mobile network level. Therefore, flashing a different carrier's firmware won't do much (permanently), aside from changing the boot screen and bloatware apps. We even tried to explain to the guy that the ATT SIM had never been popped in until after the problem began, as there was no reason to beforehand. I also mentioned I had flashed firmware multiple times before I ever came to him, to no avail. I should've pushed harder, but I had been out all day, frustrated and ready to go home.
It's been over a month since that issue began, and I haven't thought much of it lately.. We've since found her a new phone (and stowed the other one in a drawer). Those guys did blurt some moronic statements.. In hindsight, I'm not too sure I should trust their judgement after hearing what I did. Maybe it was an antenna issue or otherwise hardware, but I sort of assumed if anyone can happen to keep a repair shop open, they'd at least be able to complete the simple tasks fairly easy. I don't know. I'm not paying another repair shop to find out, though.
I had a very similar problem where my phone would just randomly lose all connection for about a minute, then it would reconnect I would start doing whatever I was and it would do it again and this one on for months. I took it to AT&t and they told me to replace the SIM which I did and it didn't work. after a couple updates it fixed itself.