Cracking S60v3 System Permission Cracking S60v3 System Permission A few days ago, I saw a foreign guy cracking S60v3 machine. You can use Y-browser to browse protected folders such as Sys and private. Out of curiosity, I studied it and succeeded. Under the pressure of public opinion, I wrote it down and shared it with you. In fact, most of them are found online. In this special statement, most of the articles in this article come from the internet, so please check the credibility by yourself. I just sum it up, let it be written and give my personal experience appropriately. I am not responsible for any loss caused by reading this article. If you don't know what a brush machine is, please stop here. Thank you. First, the principle of cracking by modifying the mobile phone configuration file "SWIPOLICY". INI ",the system has full permissions. The modification method is to modify the ROM file of the brush machine first, and update this configuration file through the brush machine to realize "cracking". The original text is quoted in:/thread-1 908099-1-1.htmln71brush course application for refining brush preparation:1. This system is SP2 Windows XP system. 2. Please make a backup of your mobile phone before upgrading to avoid losing important data. 3. It is best to refresh the mobile phone with a newly installed system without installing other third-party software to avoid software conflicts. 4. It is strongly recommended to use the newly installed system. 5. Never modify the installation directory of the software. 6. Download the software package and related documents of the brush machine. 7. Close other running programs during the brushing. It is recommended to turn off anti-virus software, firewall and system monitoring to avoid brush machine failure. 8. No matter how you brush the computer, there are certain risks. Please be careful. Your psychological quality should be excellent and you can withstand the blow. Necessary software: 55667793 Diego 306. MSI Phoenix Service SW 2004397 70.exe original program Phoenix Service SW 200439770 crack.exe cracked the file Phoenix Service sw 2006 12. 5136.exe 0.exe Nokia conncable driver 159 ita.msi upgrade package (there are two, all of which need to be found) RM-67 _ phone _ data _ package _ APAC _ 2 _ RM-67 _ phone _ data _ package _ APAC _ 2.065436.00000000005 . Exe (2.0 before 2.0, 2.0 1 during installation) Steps: 1: Install 5566793diego306.msi2: First open Phoenix SW200439770 crack.exe and crack the file to the installation interface to minimize. After installing the original program of Phoenix Service SW 2004397 and 70.exe, a message box "No dongle found" will appear. Click Retry (using the shortcut key R), then quickly click the minimized Phoenix service software 200439770 crack.exe to click All, and then select Yes All (using the shortcut key A). What warnings will the driver issue during the installation process? A desktop not found prompt box will appear and will be displayed all the way down. 3. Install Nokia Conncable driver 159 ita.msi4: Connect N7 1 (remove SIM card and SD card). Selecting PC suite mode will automatically install drivers. Finally, you will be asked to restart, start N7 1 and disconnect it from the computer (key). 5. Double-click the desktop icon to open Phoenix2004. Minimize Phoenix2004 (keep running while doing the following). Open Phoenix2006 Setup. When prompted whether to restart, select "No, I will restart the computer later" 6: Close the newly opened Phoenix2004 (it must be kept in a minimum state), double-click the desktop icon to open Phoenix2006 again, click the help menu item, and select about confirming whether the version is 2006. 12.5. 136. If yes, click OK to complete the upgrade 7: Install the N7 1 brush package respectively, first 2.0 and then 2.0 1 8: Connect N7 1 with the data cable, select the PC suite mode, then drive the automatic update, and the prompt box DESKey not Found will appear, all the way down. 9: Open Phoenix2006, click File, select Manage Connection Settings Connection, click New to create a new connection, select USB, and click Next, and the system will scan the USB port. There must be something, and there is no need to stop it. After scanning, click Next, click Finish, click USB, click Apply to accept, and then click Close. Click Scan Product Scan Connection in the menu file. After completion, a status bar will appear at the bottom of the window, showing the version information (if it is not produce, please stop) 10: click the flashing menu to select SW Update, and the software will automatically select files according to your Code code. If you have a European version of the mobile phone, please manually select the Asia-Pacific file (I don't know which one), click Start, and start to brush the mobile phone software 1 1: If it is successful, it will take 10 minutes. I hope everyone will succeed! ! Note: Step 4 above is different from the common online textbooks. You can follow the online brush first, but you can't use my method any more. The reason why I can't follow the method of online brushing is because I can't use the driver and can't connect to the mobile phone for identification. So before installing Phonix2006, connect the mobile phone to install the driver, and then restart the recognition driver. If you restart it later, Phonix will be scrapped! ! Don't know much about the brush machine, please search for the corresponding courses and required software yourself. Skip here. It is recommended to brush the original version first and be familiar with the brush process. Third, modify the ROM If you have a further understanding of the brushing process, you can start to modify the ROM. Take my Phoenix Brush software as an example. The location of the flash rom for software call is C: \ Program files \ Nokia \ Phoenix \ Products \ RM-67 \ 3. 0620. 1 .25 _ cc _ apac.fpsx. Then this is the 3.0620.1we want to modify. Now back up this file, then use UltraEdit to open this file, and use Ctrl+F to find unsigned. Remember to select the Find ASCII(A) check box. Generally, the first one found is AllowUnsigned = swipolicy.ini, F3 continues to search. Found the following contents: allow unsigned = false mandatory policies = false mandatory codesigningextension = false oid =1.2.3.4.5.6 oid = 2.3.4.5.6.7 DRM enabled = true. DRMIntent = 3 ocsp mandatory = false OcspEnabled = true AllowGrantUserCapabilities = true AllowOrphanedOverwrite = true user capabilities = NetworkServ ic es local services read user data write user data user environment AllowPackagePropagate = true siscomptibleifnotargetdevices = false RunWaitTimeoutS econds = 600 AllowRunOnInstallUninstall = false deleterpredefilesonuninstall = true AlternativeCodeSigningOID = 1 . 3 . 6 . 6 . 1 . 4 . 654333349. 1.2 . 2. 1.3 . 6. 1.4 . 1.94 . 1.49 . 1.2 . 2.5 phone syna。 Then create a new blank file in the UE and copy the contents into the new file: allowUnsigned = True MandatePolicies = False MandateCodeSigningExtension = False oid =1.2.3.4.5.6 oid = 2.3.4.5.6.7 allowGrantUser. capabilities = true AllowOrphanedOverwrite = true user capabilities = network services local services read user data write user data user environment L ocation read device data write device data power mgmt surrounding DD ProtServ TrustedUI SwEvent DRM TCB disk admin all files CommDD multimedia add netw Ork controlallow package propagate = true runwaittimeoutseconds = 600 deletepreinistalledfile uninstall = true Copy the contents to the clipboard, select all the contents, and confirm whether it is 536 bytes. Be careful here, none of the bytes are bad. If something goes wrong, you will ruin the machine with a brush. Remember! Copy it after confirmation, then switch to ROM file, confirm that it is still the 536 bytes just selected, and paste it directly with ctrl+v, and then save it. Confirm the file size again after saving, be sure to confirm! ! ! ! ! Look at the properties of the modified file and the original file and see that one byte is not bad. If there is a difference, then use the original backup file to modify the rom again! Fourth, the cracked system should be refreshed with the modified ROM, which should be no different from normal refreshing. The only difference is that I am excited at the thought of cracking the permissions of the third edition, haha. When the machine is finished and restarted, we can test when it succeeds. If you can't turn it on, mourn for your machine. . Find an unsigned software installation and see if there is a certificate error prompt. Ok, success ... f.jpg (49.39 KB) 2007-11-417: 08 It should be noted that the file management software needs to add permissions to. So as to gain browse permission for all folders. The specific process is as follows: decompress the s is software, such as FExplorer, ActiveFile, etc. Put elftran.exe and FExplorer.exe in the D drive, run the CMD command line and switch to the D drive letter. Enter FExplorer.exe: d: \ elf tran-capabilities network services+local services+read user data+write user data+user environment+all files, and then repackage and install the software, so that when you ship a new one, you will find it magically. You can browse all folders freely, including SYS and private folders, but it seems that you can't edit and operate the innermost files yet. This requires further study of authority. 5. To sum up the above record of a process of cracking my version, the key is to be careful. If something goes wrong, it will be all over. Maybe my RP is better, and I have successfully brushed the computer three times in my life. Once again, most of the contents of this article are not original by myself, all the contents are from the Internet, and the copyright belongs to the original author. This article is only for learning and communication.