Hello,
When I go to SIM Status in the settings, it says "Unknown" under "Network". I can't make calls nor text. However, 4g LTE data is working.
I live in the US and took a trip to Europe. This happened upon returning. I did not do anything unusual with my phone while abroad. While abroad, my phone connected to local networks without problem and I was able to send/receive text messages and make calls. When I got back to the US, it just says "no service" under the status.
Info:
* I am using the latest nightly of CM (which I flashed AFTER encountering this problem). No change. Before that I was using a nightly from a month or so ago without any issues
* I have checked the APN configuration and it looks correct
* My IMEI is intact and correct
* My baseband version is I545VRUAMDK
* I called Verizon and they said something about my phone not being able to enter the "Active" state. They are unsure as to whether or not it is a software problem or a network problem
Any ideas of how to fix this?
Solved
Just for the record, I fixed this problem by following the directions here.
Just in case the URL eventually fails, I used ODIN to restore back to stock, which did not initially fix the problem. From stock, I used the factory reset option from recovery mode. This fixed the problem. I still do not know what caused it.
One more problem not related to the above. Once I restored to stock and did a factory reset, I attempted to use the built-in updater to get to the latest version (currently Lollipop). The update failed with a 402 error. I was able to update using the Verizon Upgrade Assistant from my desktop computer. After upgrading this way, I ran into yet another problem with an error message that kept coming up, saying "com.android.phone has stopped working". I booted back into recovery and once again did a factory reset of the phone which fixed the problem. Everything is working as intended now.
Related
Alright so I had some issues with my phone and ran a factory reset. Ended up have to flash the stock rom via odin on Windows 7. Since then my phone shows I am roaming, cannot send text messages, look at email, or make phone calls. I found that some files were deleted off of my phone as well. I am guessing that files I need on my phone to link up with Verizon's service are now gone. I need help with this!!!
Check the IMEI, MEID, and Phone Number on the "Phone info" section of your settings.
The Fix
coronelac said:
Check the IMEI, MEID, and Phone Number on the "Phone info" section of your settings.
Click to expand...
Click to collapse
So I fixed all issues by following this link:
http://forum.xda-developers.com/showthread.php?t=2066731
The main issue was the stock radio, I was able to find ATT and Tmobile by searching for networks on my phone haha. The issue was due to installing a Cyanogenmod update and not exactly sure what caused the issue but I am assuming the wrong update (correct Cyanogenmod nightly but wrong carrier) was installed. For now on I will be installing manually.
Thanks for your input!
Before I start with the issue, let me begin with some basic information: This is in regards to my Samsung Galaxy S5 SM-G900T (T-mobile), running Lollipop 5.1.1, FOG6 build, DOB1 baseband, rooted, deodexed, but otherwise stock.
My problem: Today I flashed a rom via Mobile Odin Pro and soft-bricked my device. After a lot of hair pulling and screaming at my phone and computer, I finally got my phone up and running again. After trying many different solutions, I eventually tried re-flashing TWRP through Odin (recovery initially would not boot, hence the soft-brick), which succeeded, and then recovered my phone by restoring from a previous backup.
This got my phone up and running again, but once it boot, I had no service. I first checked my APN settings, but was presented with a message stating, "Unable to view the access point name settings. Access is restricted for the current user profile." I tried adding a new APN, but once I added it, it did not appear in the APN list, which continued to only display the above message. I then tried to "Search now" for Network Operators, but nothing was found. So next I checked my IMEI through "About Device", and discovered it was set to "Unknown". Checking the IMEI through the dialer (*#06#) lists the IMEI as "null / null".
I have searched high and low and tried everything I could find to fix this. I tried restoring my TWRP EFS backup to no effect. I also tried flashing the modem through Odin, as well as restoring my TWRP modem backup. I tried using an Xposed app to manually set the IMEI back to its original value (I happen to have my phone's original IMEI number written down from when I SIM unlocked my device), but while this updated the IMEI displayed in the dialer (through *#06#), it did not change the value in "About Device" and did not restore my service.
The last solution I tried (found here: http://www.technobezz.com/restore-galaxy-null-imei-and-fix-not-registered-on-network/) involves me using the dialer to enter Service Mode to make some changes; however, while dialing *#197328640# did open the Service Mode menu, the menu was totally blank.
Please help! Given the current state of my phone, I cannot make or receive calls or texts or do anything else requiring a mobile connection. I have looked everywhere and I don't know what else to try :crying: :crying:
Assistance in this matter would be greatly appreciated, as until I am able to fix this, I don't have a functional phone
Any suggestions?
I have a Jiayu S2 double-SIM phone, running the most up to date official ROM (4.4.2).
This ROM had a couple of bugs (no GPS and no notifications to external devices such as smartwatches), so I wanted to check other available ROMs. Using the Flash Tool I have tried a couple of the ROMs in the needrom site (https://www.needrom.com/category/jiayu/s2-jiayu/). In particular, a couple of versions of the official ROM, another ROM known as Salamander, and an unofficial port of Cyanogenmod 12 (in which the camera was not working).
The issue is that, for some reason, at some point my phone has stopped getting phone signal. The SIMs ask for the PIN on startup, but there is no signal. I have reverted to the original ROM; plus done a factory reset, and I could still not get signal.
The APNs for both SIMs are fine. Then I have realised that the IMEI was empty. Luckily I had it written down, so I have installed Xposed and the Device IMEI Changer, with which I have been able to restore the IMEI. Now I can see the IMEI on the Settings - IMEI information, as well as with *#06#.
But still, now with the original ROM, and with the IMEI restored, I still cannot get phone signal. I have tried setting the phone to flight mode, restarting, selecting manually the network... When trying to manually select the network I can see several networks, but the phone will simply not connect to the one it should.
Any idea on why could it be that I cannot get phone signal? Thanks.
After trying everything, including restoring the IMEI with Xposed, I have finally managed to restore cell service by restoring the IMEI with this tool: https://play.google.com/store/apps/details?id=com.cryptotel.chamelephon
Hi all!
I bought an S6 Edge second hand and after flashing a stock ROM, I had the "emergency only" calls issue, I tried everything I could find in the forums to no avail and I ended up taking it to a repair service. I did not think they could fix it but they did and I would like to know what they did to it in order to prevent it from happening again and to know if I can leave it as default (not custom OS) so that it can upgrade.
State of phone when bought:
So, the phone was working well with all carriers (from Colombia). The only thing I was able to notice after I bought it was that it was still on Marshmallow (6.0.1) with carrier branded stuff. It was in perfect shape otherwise.
So I downloaded a stock ROM and installed it using Odin. After this the phone would not let me make calls as it was not registering on the network. It did not even let me make emergency calls despite getting full bars of signal and being able to recognise the list of carriers when attempting to manually connect to them.
Important: The ROM downloaded was for the right version of the phone which was the G925i and the IMEI, serial number and baseband were not altered from the original. Also, I checked the phone to see if it was reported as lost/stolen and it was not (of this I'm sure because in Colombia you can consult a centralised database on any carrier's webpage). Also.. Here in Colombia it is illegal for carriers to lock phones.
Steps I took to fix it:
Downloaded ROMs for all carriers, branded and unbranded, I even installed one from Trinidad and Tobago and a LATAM one.
I performed all the tricks to disable and enable flight mode, location services, try con connect manually to the networks, changing to GSM only, GMS/CDMA, international roaming, etc.
I also extracted modem.bin from an earlier version and flashed the modem.bin with Odin (6.0.1 moden on 7.0, 5.1.1 moden on 6.0.1 and 5.1.1 moden on 7.0). All modems flashed correctly and the issue remained exactly the same.
So I finally gave up.. I installed the latest stock ROM which was an unbranded Nougat (7.0) version and took it to a repair service and they fixed it in a couple hours.
What I noticed after the phone was "repaired":
- The phone was rooted, SuperSu was installed, no other root app was installed.
- On SuperSu, there are entries for ADB shell (they all say Superuser command contents have not been logged for this entry) in a two minute timespan.
- The android version was downgraded to 6.0.1, I was told not to try to update it.
- Developer options was enabled with USB debugging turned on.
- The boot option (the one where you can wipe data and cache partition) was left as original (not the TWRP one).
- The ROM used to downgrade was the same I had before but only downgraded the version.
I suspect this same procedure was performed before on the phone but it had the original ROM carrier branded so it seems as if they installed a custom ROM, rooted it, connected with pc and performed some command line stuff to fix it, then cleaned the bootloader to a stock one.
The questions:
Any ideas what did the repairman do to fix the phone? Also, would it be safe to make a full backup with TWRP and flash again a stock ROM upgraded to 7.0 and then flash the backed up modem to get it working? Or would that possibly screw up the repair?
Thank you all in advance for any help. I'm sure there are lots of people out there experiencing the same "emergency only" issue I had but there does not seem to be a fix around, but clearly there is one! So I hope this sheds some light into what could possibly happen.
Hello everyone, I'm a desperate noobie here trying to fix this issue for three days now.
So as stated above I have a Samsung Core Duo (SM-G335H) and three days ago I connected trough SmartSwitch and it offered to update my phone. I agreed and during the middle/second half of it my laptop and phone just crashed. I revived both and SmartSwitch told me about the update failure and I made an Emergency Recovery. After that recovery, at first, everything seemed to be working normally, but on the next day I noticed: "Not registered on network " error. It recognizes the SIM card, but when you try to find a network it says "Can't connect. Try later." and so on. I can't call, other peeps can't call me.
I have been researching this matter for days now and am very upset about this. Some say stuff like Odin/flashing/third party tools/settings, I don't know what to do, as I don't have much experience with those things.
Btw, my IMEI is not null, it is being displayed (so I guess the EPF folder is not damaged). The APN settings (I'm on T-mobile) are still there, I don't know what to fix about them.
I am running 4.4.2 KitKat and my Security Patch Level is dated 2016 if that is of any relevance...
I also did a hard reset: nothing. SIM card works in my other phone, so it's not damaged. I just now saw that the end symbols in my Baseband version and my Build number don't match. Could that be it? I've seen people recommending updating manually/flashing with a modem file. How do I go about this?
Also: my phone is rooted. Only that I very clumsily attempted it months ago and before this matter here I would have problems with binary updates and what not, "phone is not rooted completely", I already fixed that issue though, it has SuperSu on it.
Anyway, I may have messed up somewhere along the way leading to this problem.
Please don't recommend me reseting/rebooting the phone again or just re-inserting the SIM card, that doesn't fix it.
I welcome any other suggestions, I hope somebody can help me.