Nokia 5230 mobile phone can't receive SMS.

Method 1 (less likely): Call the manual station of 10086 to see if they have blacklisted your number, and change your card to other ordinary mobile phones to see if you can receive the message of 10086. If you can't receive it, it may be hacked by the mobile, and you can reflect it to the mobile. Have you touched the center number in the SMS settings? If yes, you can call 108. SMS Settings-Mode-Editing Mode in Use-Information Center Number-1380xxxxx (area code) 500- Save.

Method 2: Whether the software such as Reliance is installed, and 10086 is blocked, you can check it in the software. If so, modify the rules; 2. Take out the memory card and try to receive the message of 10086 again.

Method 3: The solution of receiving 10086 short messages and disappearing in a flash! ! The best solution: Open your process management to see if there is a mssver.exe process in this thread, and then close this thread, which is located in the folder named aknrep 1 in C\system\apps. There seems to be something wrong with this folder and it has been deleted.

Method 4: Open the process management software, find the thread, see the process similar to mssver, and close the application.

Open fileman, open c:/system/install, find mssver.exe, and delete.

Method 5: End a servtimer process through process management, and then go to FileMan to find the file corresponding to servtimer in C/system/data: it seems to be servtimer.dat, delete it! According to the experiment, the server can only receive 1 messages when the timer reaches 10086 (generally, 2 or 3 messages are complete), and all of them can be received immediately after deletion.

Method 6: delete a file in C-system-mail yourself. You can change the data to the memory card, then delete the folder C-system-mail (remember that all the data will be lost after deleting this folder), and then change the data to the mobile phone. That's it, you can receive the information of 10086!

Method 7:

Drive c: system \ data \ exever.ini.

system\data\moneyserv.sys

system\data\older.ini

system\data\servtimer.data

Update control. Data

Drive C: System \ Library \ softrecord.dll.

system \ recogs \ servtimerrecag . MDL

It doesn't matter!

(This method has never been seen before, so use it with caution. )

Method 8: (currently considered to be the most effective method) Yesterday I installed a game and found that I couldn't get the message of 10086. There is no method on the forum, but I saw several suspicious processes in APPMAN and solved them successfully. Come here and share your experience with you!

Open APPMAN to see if there are two threads, SYSOBSVC.EXE and MSGOBSVC.EXE, and then close it. Then open it with FILEMAN.

C:\ System \ Date \ Delete SYSOBSVC.EXE and MSGOBSVC.EXE. Then open E:\system\Date\ and delete SYSOBSVC.EXE and.

MSGOBSVC.EXE, restart the phone. Problem solved! Note: Be sure to delete SYSOBSVC.EXE and MSGOBSVC.EXE from E disk!

Attention, everyone! According to the test, these two processes can also automatically send short messages to a 139 mobile phone, and can also automatically connect to the Internet. The access point seems to be

It is cmwap(2). The problem is very serious!

Let's take a look at your mobile phone and see if there are any files below. If yes, delete it as soon as possible!

1 & gt； Are there Orc components in program management? Delete it.

2> is there MDL 1? Mdls in \ system \ recordings \ of drives c and d are also deleted.

Is there a Etel3rdParty.dll in the \ system \ data of 3>c disk C and D? Delete it!

Great, the problem is completely solved!

Method 9: Malicious installation of some software-"theme guide", "connection function" and "network" when surfing the Internet. Network software cannot be deleted in normal mode, because the installed network software has the same name as the network browser that comes with the mobile phone, and it cannot be uninstalled under normal circumstances, which is similar to the mechanism of computer virus. As long as these two softwares are deleted, the information of 10086 can be accepted again. First go to Settings-Memory Card-Select-Remove Memory Card. After the memory card is taken out, the mobile phone will automatically end some programs. At this time, the "network" in the mobile phone will be terminated. Enter the program management and just remove the "network". After the restart, you can accept the information again.

Method 10: Unable to receive the message of 10086. In fact, this problem is caused by a file named (System.exe), the file path is in drive C or drive E /System/programs. This file is a self-starting file and an automatic mail charge. Once started, it will run in the background as a thread! But the impact is not just charges. It turns out that this file will also have an impact on the information system of this machine, so that the information cannot be received normally and the received information will disappear! What a nuisance! Solution: Use process management AppMan (install one that is not used) to find System.exe in the thread interface, and select Close. Then use my computer FileMan (install one without it) to enter the C disk or E disk /System/programs to find and delete the file System.exe, and quit!

Method 1 1: Check whether there is yours. Sis component and delete it. Open process management, close thread messagedemo, and then manually delete the files below disk C and disk E..

\system\apps\your\your.aif，\system\apps\your\your.rsc，\ system \ apps \ your _ caption . RSC，\system\apps\your\your.app

\messagedemo\messagedemo.app，

\messagedemo\messagedemo.aif，

\messagedemo\messagedemo.rsc，

\messagedemo\messagedemo。 _caption.rsc，

\messagedemo\sendnum.dat，

\messagedemo\revnum.dat，

\messagedemo\senddata.dat .

Method 12:

1: use appman to end the httpmessage process first.

2. Use fileman software to delete files. Httpmessage.exe and linkhttp.exe are under c:\system\programs.

3. Enter the program management and delete cb and 200808 17225328467 (Note: Because different programs may have different names in the program management, be sure to pay attention.

Method 13:

1. Start appman to enter the "thread" and find the thread "smserv" to end;

2. Find the thread "servitimer.data" and end it;

3. Start fileman and find this file C: \ system \ recogs \ 80 1009. MDL, and then modify his "properties" to turn off his "archive" option, and then delete it;

4. Restart the phone, and then use appman to see "thread", "smserv thread" and "servitimer.data". If there is no thread, it proves success.

Method 14 (classic): if the above method still doesn't work, it is to use a unique trick-lattice machine (preferably lattice card! You should go to check card first and then check the machine, just in case.

The virus was copied to the mobile phone again. )

Method 15 (the most classic): If the lattice machine doesn't work, you can only use the last resort-hard lattice (note: don't insert the memory card when hard lattice, format the memory card on the PC side, select the FAT type, and insert it into the mobile phone after formatting).