Super simple, Android simulator manual root

This article was reproduced from: http://quantoubao.blog.163.com/blog/static/2083211702013870501987/

The way to install Android SDK Android Simulator is very simple, online a lot, fool-style. But for its root method, the online version is not so easy. Online approach from the directionality is right, is the details did not give clear, or wrong, or did not mention the root way to different versions of the API differences, leading to many people follow the so-called tutorial to do root failure.

Here I Android4.0.4 the root method of the Android SDK virtual machine which is suitable for the high version of API, very simple.

This is the case without root, and the frame buffer has no content.

The first step of root is to prepare the tool. There are two of files. ① Internet search A "yaffs2img" Mirror browser, temporarily suggested with 1.5 version, 2.0 version I download several (of course not Z version) seems to have a problem. ② on this site, is the Superuser designer's website androidsu.com, download the corresponding simulator version of the super-authorized user files (the page has its compression package). The so-called corresponding version, on the one hand, corresponds to the simulation of the CPU version, ARM or x86, can not choose the wrong. If you choose a MIP CPU when you simulate it, you will die the root of the heart. At present, the overwhelming web of tutorials are not clear this point, but also in the text to refer to the third-party download files, is the culprit that led to the novice operation failed! On the other hand is to choose suitable for their own simulator simulation system version, the current androidsu.com to provide the latest official version of the cracked file, suitable for android2.0-4.1. For older versions (as if there is no root meaning), you can find a history version of it, and for a newer edition you can consider its beta version or wait a while. Download, as long as the next Superuser package can be, already contains a full range of documents.

Root in the second step, use "yaffs2img" in the Virtual machine directory "System-images" in the corresponding target simulator used in the System image directory (I here is "android-15\armeabi-v7a") in the "system.img" open. Extract the "Build.prop" file from its root directory to the hard disk, open it with a text editing tool (such as Notepad), and delete its "Ro.config.nocheckin=yes" line. Of course, the outfit plus the "#" comment off can also seem superfluous. Then import the changed "Build.prop" back to the original location in the image to replace the original file. Remember to set the file permissions to "0644". It must be remembered that this can only be "0644", not according to other tutorials and other permissions!

Root of the third step, the first step to download the Superuser compressed package, the inside of a file called "su" (no extension) into the second step to open the image "bin" directory, the permissions set to "6755". The "Su" is then directed to the "XBin" directory, if you encounter an existing old file, directly overwrite, and set the permission to "0755". Remember, the previous one is "6755" and the latter one is "0755". Don't get it wrong! Online harm of the tutorial, or the right to say wrong (perhaps it set the permissions for the old and old version of the SDK emulator), or leaked the "xbin" this directory! Then the unpacked package "superuser.apk" import into the image of the "app" directory, set the permission to "0644", can not be wrong!

The last step of root, save the modified image, select "No ecc/no FFFF flag" This set of parameter combinations.

Come on, this is the situation after root. Once.

The file modifications mentioned above are not expected to be done in the virtual machine, and a reboot of the virtual machine will be lost. Even if a snapshot is used, the AVD that mirrors the other references is not valid. Change the image is the most appropriate, change it all with the image of the AVD are in effect. This method for Android SDK simulation 4.0/4.1 available, as for the 4.2/4.3, wait for the new version Su again try it.

Please see the following paragraph Android SDK Emulator root method Advanced

The previous article continued, the book connected to the previous ("Android SDK Emulator for the 4.0.4 and other high-level API, the simple root method"). In terms of the current Android SDK emulator virtual machine root, most use androidsu.com's Superuser scheme. In fact, with other SU also can not be, the method is very simple.

Preparation time In addition to the previous article mentioned in the general "yaffs2img" browser, is the APK file for each Rights Management tool and the corresponding Su file.

The general approach is (real machine same root method, real machine system with re tool or even computer run ADB command, virtual machine system with YAFFS2IMG):

⑴ refer to my old text 2nd step.

⑵ The main file name of the APK file to its original full package name, use the lucky cracker to see the package name.

⑶ will plug the renamed APK file into the target system "System\app", the permission to take 0644.

⑷ apk file with the decompression tool to unpack, see if there is a Lib directory, if any, in the corresponding CPU directory (Armeabi or x86 or MIP) all the files in the target system to the "System\lib", access to all 0644.

⑸ put the Su file in the appropriate location and modify the permissions. Depending on the root tool, here are a few things

① only put "System\bin", permission is 0755, "system\xbin" must not have su.

② only put "System\bin", permission is 6755, "system\xbin" must not have su.

③ only put "System\xbin", permission is 0755, "system\bin" must not have su.

④ only put "System\xbin", permission is 6755, "system\bin" must not have su.

⑤ put "System\bin", the permission is 0755, and put "System\xbin", the permission is 0755.

⑥ put "System\bin", the permission is 6755, and put "System\xbin", the permission is 0755.

⑦ put "System\bin", the permission is 0755, and put "System\xbin", the permission is 6755.

⑧ put "System\bin", the permission is 6755, and put "System\xbin", the permission is 6755.

For example, in the case of androidsu.com, the situation ⑥ should be used, and the situation ④ must be used for EU.CHAINFIRE.SUPERSU's programmes. Other root schemes are similar. The above-mentioned status of SU is a virtual machine, because the virtual machine is a write mirror, independent of the system virtual operation, and the real opportunity to restart the automatic processing of this redundant su.

⑹ Restart the target system acceptance results.

Attached IntelX86 su file:superuser-3.1.3-x86-signed.zip

Attached yaffs2img browser:yaffs2img Browser

Super simple, Android simulator manual root