Busybox - He is the same bisibox. This program / supplement for the system kernel is expanding the basic functionality. Some programs are needed
Kernel - He is Kernel, it is the same core. As a rule, this word means the kernel of the operating system. Newbies do not need to know this, advanced users, should know what it is.
Root rights - He is the root. Simply put, these are the rights of the administrator, allow you to do what the soul pleases with your operating system. It happens complete, temporary, permanent, etc.
Previously, in order to get the rights of the root, you had to unlock the bootloader, now, when a bunch of holes in the android came out, a bunch of different methods of getting the root without unlocking appeared.
The easiest way to get root is SuperOneClick.
It uses a vulnerability in ADB, so it works on any firmware of any version.
Hboot - On the same bootloader, on the same bootloader, on the same bootloader. Roughly speaking, this is a bios phone, this firmware that launches your device and is a connected bridge between OS and Radio.
If the firmware fails, the chance to get a non-working brick is nearing 99%.
It is not treated.Stitch the bootloader from the amole nexus to the nexus
CATEGORICALLY CANNOT.How to enter the bootloader - Enable the device with the "Volume Down" button. Butloder navigation is performed by volume buttons. To confirm, use the "Disable" button
Radio - It is the same radio. This is a separate OS, which manages the entire periphery on the phone (camera, sound, etc.). Works on a separate processor and protected from user intervention. The operation of the cellular module and other wireless communication modules is entirely dependent both from the RADIO itself and from the compatibility of the "Radio-Butloder-Firmware"
If the firmware fails, the chance to get a non-working brick is nearing 99%.
Not treated, so before the firmware always check the checksum MD5!MD5 - On the same MD5. Hasching algorithm. To explain for a long time and tediously therefore briefly for the news - in the topics for radio firmware, bootloader and other things, as a rule, they write a string with a checksum of MD5. The checksum is a series of letters and numbers. If the amount of the MD5 of the file you download differs from the amount that is specified by the author of this firmware, it is impossible to flash this firmware, because The difference in sums means that the file was downloaded by broken. View MD5 by any third-party software, for example MD5Summer
Recovery - On the same recovery. This is a special. the bootloader which is loaded from the bootloader, the essence of which is to make changes to the system, since these changes cannot be made with the operating OS, to the same, according to the user, it is simply no right to modify the system (RUT rights do not count. Initially, the user does not have).
The original purpose of the recovery: install updates for the phone or completely remove user settings
There are modified recovery, also referred to as custom recovery that significantly
increase the chances of recovery. They allow, for example, to flash custom firmware, give access to the memory card without booting the OS, clean the Dalvik cache, etc.
AmonRA, the creator of custom recovery, strongly discourages updating the bootloader if you have custom recovery, because When updating the bootloader, changes are made to the recovery, which leads to glitches in the latter.
How to enter the recovery - Through the bootloader. Either via ADB, ADB Shell, Reboot Recovery commands.
Navigation about the recovery is carried out by the trackball.
In the original recovery, a triangle with an exclamation mark on the background of android will appear. To get to the menu, you need to press the power button and not releasing clicking on the top button.
Adb - he is adb. (ADB - Android Debug Bus) This is a special interface designed for debugging devices based on the Android OS. Included in the SDK. Gives access to the phone through a computer, even without a loaded / broken OS.
To access the phone while the OS is running, you need to enable debugging mode (USB debugging) in the phone properties.
Swap - He is swap. This is a special file / partition that expands RAM at the expense of the usual non-volatile memory. Due to the fact that the ordinary non-volatile memory is in tens of times more slowly than the RAM, the use of the swap serially slows down the system. It is worth using only if there is an extreme need for additional RAM.
How to create swap - In the custom recovery, during the creation of an ext part, it is also proposed to create a swap section.
APP2SD - Special script from DarkTremor who is deceiving the system, forcing her to think that the section on the memory card and there is a phone's memory. Used to fully transfer programs from internal memory to a memory card. The same allows you to transfer cache and Dalvik-cache.
There are 2 versions - one uses the FAT file system, another EXT file system. Difference - Option with EXT does not violate the system if you mount the phone as a flash drive, the ability to transfer any programs.
Disadvantage - firmware must be modified to be able to work with this script.
No stock firmware in the original form (without third-party changes) does not support App2SD and will not
How to enable app2sd. - To begin with, you need to flash the firmware in which there is support for this script (see the description of the firmware used). Next, simply create an ext part on a memory card (using a custom recovery), the script will automatically turn on when loading.
Multiple teams for beginners (enter after the SU command):
A2SD HELP - will display a list of commands and a description of them
A2SD REINSTALL - reactive script
A2SD Uninstall - Disable the script, drag all programs back to internal memory
A2SD Zipalign - to transfer to each system loading
A2SD CACHESD - Reset Dalvik Kesh to a memory card
A2SD Nocache - Return Falvik Kesh back
A2SD ResetCache - Clear Kesh.
A2SD Heapsizexx - set the maximum cache size for the application in which Dalvik stores the application code. Instead of XX, you should enter the size you need without a space. The recommended size is from 18 to 32. The smaller - the faster, but there is a chance that heavy programs will fly out with errors. Their code simply does not fit into the specified size. Standard size on stock firmware - 24. Standard size on MIUI - 32.
With incorrect meaning will completely kill your system, it is treated only by flashingSdk - On the same SDK. Developer set for android. Contains various tools for creating programs, among which the debug interface of the ADB. The same contains USB drivers for phones on Android OS.
Where to download SDK -
http://developer.android.com/sdk/index.html Fastboot - On the same fastboot. This is a logoder protocol that allows you to flash any part of the phone based on Android OS without looking at the region or signature. Initially, this feature is blocked, but it can be unlocked. Unlock automatically removes the phone with warranty. Block back unlocked fastboot
DO NOT . When the bootboot is unlocked, an open lock is drawn at the bottom of the screen, and the bootloader itself says * UNLOCKED *
I want to note that it is safer to flash a bootloader or radio through a fastboot than through a recovery, because F
Stut conducts integrity testing but this does not guarantee the absence of problems during the firmware.
How to enter fastbut - Through the bootoder, or include a device with a pinned trackball.
Wipe - Only Wipe. Cleaning, performed in the recovery. Clears the selected partition. Possible options:
Wipe ALL userdata - Clears all sections listed below except for the last two.
Wipe / data - Clears the / data section where user data is stored.
Wipe / sd-ext - Clears the EXT section on the memory card (in case it is present)
Wipe /sdcard/.android_secure - Clears programs installed on a memory card. (Froyo app2sd)
Wipe / Cache - Clears the / cache partition where the cache is stored.
Wipe / Dalvik-Cache - Clears partitions in which Dalvik cache can be stored.
Wipe battery stats - Clears battery usage statistics
Wipe rotate settings - Clears the phone's sensor settings.
It is often said that wipe is an analogue of Hard-reset in WM, but since WM, in contrast to android, uses ROM memory-image - in case of OS crashes as a result of picking, full-wipe will not restore the system. it will just clean the broken system, and it will still not boot.
Wipe should be done when moving from one firmware to another, it is done BEFORE flashing. Otherwise, you will get a dump from 2 firmware, which at best will be buggy, at worst it will not load.
When switching to a similar firmware, for example, from the old version to the new one, it is enough to make a wipe cache and a wipe of the dalwick cache.
When switching to a new kernel, it is enough to make a wipe cache and davick cache
How to unlock bootoder :
1) Install the driver for the phone (included in the SDK)
2) Swing this file:
http: //savagemessiahzine.com/forum/dl/post/392144/fastboot.zip3) Enter the fastbut (you need to turn on the phone with a pinned trackball)
4) Open the command prompt, go to the folder in which there are files from the archive (CD command. For example, CD C: \ temp \ SDK drags you to the C: \ Temp \ SDK folder)
5) Enter FastBoot-Windows OEM Unlock
How to flash custom recovery: Method number 1
* Need unlocked bootloader*:
1) Download the recovery you liked and throw it into the folder where you have adb and fastboot
2) Enter the phone in fastboot mode.
3) In the command line, enter fastboot flash recovery "here the name of the recovery without quotes"
Method number 2, unlocked bootloader is not needed:
1) You will need root explorer, root and terminal rights (Instead of the terminal, ADB will come down)
2) Download this archive
http: //savagemessiahzine.com/forum/dl/post/737671/Archive.rar3) Throw the file nexus2.img in the root of the memory card.
4) Using root explorer, throw the flash_image file into the / system / bin / folder
5) In order in the terminal, enter the following commands:
su
flash_image recovery /sdcard/nexus2.img
reboot recovery
5a) If you are using ADB, enter the following commands in order:
adb shell
su
flash_image recovery /sdcard/nexus2.img
reboot recovery
How to get root rights :
1) Download the super-one-click-root program from here:
http://forum.xda-developers.com/showthread.php?t=8036822) Make sure that the setting mode is enabled and the drivers for the phone are installed.
3) Connect the phone to the computer
4) Run the program and poke root.
How to flash custom firmware 1) Install custom recovery
2) Download the firmware and shove it on the memory card
3) Go to the recovery
4) Select the Flash from zip item, then select your firmware and the firmware process will begin.
DO NOT FORGET BEFORE THE FIRMWARE MAKE A WIPEP.S. For some firmware you need to disable signature verification. This is done there in the same recovery, point other, then Toggle Signature Verify.
P.P.S. Keep in mind that for android 2.3 you need to have a radio not lower than 5.08 and a bootloader version not lower than 0.35!
Links to the most popular firmware :
MIUI ROM -
http://miui-dev.com/forums/forumdisplay.ph...oogle-nexus-oneCyanogenMod7 -
http://forum.xda-developers.com/showthread.php?t=723844.Desirehd ROM -
http://forum.xda-developers.com/showthread.php?t=791151Desire ROM -
http://forum.xda-developers.com/showthread.php?t=730290.Micromod 2.3 -
http://forum.xda-developers.com/showthread.php?t=872441.----
Nevsuses are 2 species:
Operator and original. AMOLED and SLCD.
The original Nexus - delivered only with AMOLED screens, sold and maintained by Google itself. Since the summer of 2010 there are no sales, support has been transferred to the manufacturer of HTC.
Get updates from Google itself.
Camera nexus are the same as nexus, but unlike ordinary nexus, operators support them. These are Korea Telecom, Vodafone, Videotron, etc.
Since summer 2010, only SLCD screens are installed on camera Nexus.
Unlike the usual nexus, on the operator nexus there are firmware supplied from the operators, with various additions / differences such as the presence of a Chinese or Korean keyboard, a dictionary, etc.
How to determine the type of nexus :
In the bootloader version of microp:
0a15 - Amoled Nexus. Prototype.
0b15 - AMOLED Nexus.
0c15 - SLCD nexus.
Note: On SLCD nexus, firmware in which there is no SLCD support will not work. These include any version of Android 2.1 and some others.
Some XDA users also say that the original FRF91 from the amoled nexus does not work for them.
Custom recovery will not work if the version is lower than 1.8.0.0 in Amonra recovery.
Sign of incompatibility - The screen does not show anything, but the rest at the same time continues to work.
Solution - flash another firmware / recovery
------
That was a little afraid, I hope in the future it will be useful to people and stuffed it in the header
Post has been editedJiwan - 10.04.11, 07:12