Hello everyone, and my apologies if this is in the wrong section, I wasn't sure where to post this.
I have a Samsung Galaxy Showcase (SCH-I500) running 2.3.7 and I recently installed Cyanogenmod 7 on it. Since I installed Cyanogen I have been unable to send or receive txt's. After doing some research I have concluded that it is a problem with my SMSC number. I have tried several numbers and used the PDU encoder found online all to no avail.
I have also noticed that after "updating" the SMSC number through the *#*#4636#*#* menu that after reboot if I click "refresh" nothing shows up in the box (not 00, just blank).
I have tried clean installed, and resets, but nothing is working. I have tried calling straight talk, and their technical support didn't even know what a SMSC number was same with the walmart store associate. Is there anyone here that can help me out?
PS: This is a Straight Talk phone and I believe I am on the Verizon network.
Related
I am unable to send sms but can receive on my rooted Galaxy Note N7000.
When I check the Phone Information by dialing *#*#4636#*#*, the SMSC: field is blank.
If I click on refresh, it returns "00".
If I attempt to enter the number manually it just returns "update error".
I'm assuming that the number should be stored on the SIM card and for some reason the phone can't read/access the stored number. This happened once before after rooting the phone and all I had to do then was hit refresh and update. I did see that the SMSC field was blank when I re-checked it later, though, but sms was working correctly.
I tried installing Gingerbread 2.3.6. The Settings > About Phone confirms 2.3.6
but
1. it made no difference to the SMSC problem I describe above
2. all my settings, data and apps are still there.
3. the phone is still rooted.
I assumed all that would get wiped with a f/w upgrade. The instructions I followed said the phone would be reverted to non-rooted. I guess I must have got something wrong.
I talked to a guy at my local telco today. He spotted that the phone was rooted so was quick to blame that (maybe correctly) as the cause. However, when I showed him the settings page revealed by the *#*#4636#*#* string, he thought this was some software app I'd installed myself and not the phone's f/w till he typed the string on his own phone and saw it for himself.
Can anyone suggest a fix? Un-rooting? Wait for the next official Android upgrade for my phone/region?
Thanks in advance
Trevor
Try with this
http://forum.xda-developers.com/showthread.php?t=979564
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!
Hi, guys! Before a short time I have bought a Galaxy S3 smartphone (it was brought from USA I think) and it was already rooted. I decided to install Cyanogenmod 10.2.0 (by CWM) on it. After installation my SIM became to be undetectable. So I thought the problem was in modem. I've read about it and I learnt that the stock modem couldn't work with my Cyanogenmod. I tried to find the correct one, but I couldn't. I have found just one modem for my android version (4.3.1) and country (Turkey), it is - I9300XXUGNA8. It can see my SIM but couldn't connect to my cell-operator and I have just emergency calls. Also in information about my phone I can see my IMEI, but I couldn't see my phone number.
Please, help me to find correct modem compatible with android 4.3.1 for Turkey.
P.S. When phone have just started it asked the PIN of SIM maybe 30 times in a row. All times I enter it correctly but it says "SIM is unlocking" only for 1 sec. and asking a PIN again. After 100500 try it gives the same message for 5 sec. and soon throws me to main screen. But with no connection to cell-operator. Just emergency calls.
Help me, please.
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.
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
bornxawkward said:
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
Click to expand...
Click to collapse
Please check your voice mail settings in your phone app. See my screenshots.
There you should select the correct service provider and the Visible mailbox number.