Joke Collection Website - Public benefit messages - Why did the original card information disappear after 10086 card replacement procedure, but the SMS was still there?

Why did the original card information disappear after 10086 card replacement procedure, but the SMS was still there?

Cause analysis: The reason why I didn't receive the short message of 10086 was mostly because someone was implanted with a malicious plug-in when installing the software. Those malicious plug-ins that charge will automatically block the SMS of 10086, so that you can't know which charging services you have customized. (The communication department has regulations to customize SP services.

Service, there must be a prompt, if you can't see the prompt information of 10086, it means that you have customized SP service by default).

Solution: When encountering such a problem, be sure to use APPMAN to check whether there are suspicious threads. When checking threads, you should set it and choose to check non-ROM threads.

Note: When you see a suspicious thread, don't close it. Using APPMAN's function to check the details of the thread, you can find out which files in the phone are called by the system. Accordingly, delete the malicious plug-in.

Originally, my Xiaoqi didn't receive the news of 10086, but it's good to have your great help. In order to thank everyone, I specially sorted it out and talked about my own methods to solve this problem: (many of them are the methods of other friends, so I will borrow them here)

Method 1: Call 10086 to see if they have blacklisted your number (unlikely). Change the card to another ordinary mobile phone, and try 10086 to receive the message. If you don't receive it, it will appear on the mobile side. It may have been hacked by the move, so it can be resolved by reflecting to the move. Have you touched the center number in the SMS settings? If yes, you can call 1006.

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;