Solutions to mobile game authorization failure, invalid file, and invalid version

1. Solution to authorization failure: Usually authorization failure is due to the fact that the game file is version XX. Here is a brief explanation of the simple principles and methods of Montnet Game XX: The 1st, 11th, and 21st of every month are when Mobile Treasure Box updates new games. The "kind" mobile will launch a one-time trial version of the game (S40, S60V1, SE, and MOTO are all available when launching new games), but only S60V2, which is the 7610 box, does not Yes) The principle of the trial is very simple. It is based on the original game, automatically generates several classes, and determines whether it has been run once by generating an archive. The downloaded JAR file will have a com folder in it, which contains two folders: fourthpass and sincetimes. The principle of XX is to modify the code that handles RMS so that the program can run normally. Generally speaking, if each game is modified directly, the problem of authorization failure will not occur in theory. However, if the XX directly replaces a modified file to save trouble, the problem of authorization failure may occur. The solution is actually very simple: Delete the COM folder in the downloaded JAR file, and then transfer it to the mobile phone, so that there will be no problem of installation failure, but the game cannot run after installation. Then transfer the JAR file without deleting the COM folder to the mobile phone, and use SELEQ to copy it to the game installation directory (SYSTEM/MIDLE Under T/, you can tell by looking at the name of your installation file. It is not under SYSTEM/APP, that is just the registration file generated by the installation), overwrite the originally installed game, and it can run normally. The principle is the same as installing the original SIS game, and then replacing the APP file with the XX file, but the operation is relatively troublesome. 2. Solution to invalid file: The reason for this situation is generally that the MF information in the JAR file has been modified. The solution is very simple. If you can find the original game, just modify the MF information inside. Use WINRAR to open the JAR file. There is a META-INF folder inside, and the MANIFEST. The MF file is information. Open it with Notepad, then modify it and save it again. Remember to use Save As and select UTF-8 format for encoding. The safest way is to install WTK, create a new project, and have the main MIDLET have the same name as the game's MIDLET. Write the information in SETTING as the information needed by the game, such as ICON, author, version, etc. This will automatically generate a MANIFEST in the WTK project APP/project file/bin folder. MF file, using this file to replace the original file can solve the problem of invalid files. 3. Invalid version is usually caused by the version of CLCD. The same is done by modifying MANIFEST. MF file, change MicroEdition-Configuration: This item, such as QD, 6600, is MicroEdition-Configuration: CLDC-1.0. If it is MicroEdition-Configuration: CLDC-1.1, change it directly to Micro Edition-Configuration: CLDC-1.0, but this method can only solve the installation problem and may not be able to run correctly. There are only a few games that are written as 1.1, but in fact they are still 1.0 games. Similarly, QD can also solve the installation problem by modifying the MIDP version. As for whether it can run, it depends on the game itself and RP.