Hello everyone! It's me again! Great and mighty!
I did not so long ago, he was terrified of those strange words that occurred in subjects with an android, so on a whim good people here decided to write about what I know, that it became easier in such a complex matter as firmware Samsung GT-i9000 Galaxy S ...Used files: .tar, .md5, .pit, etc
* .tar- a simple tar-archive that contains a particular firmware Comp
* .md5- same* .tar, Only with an added extension* .md5
* .enc- zip-archive with a password, for KIES firmware (we will not use it)
* .pit- file for layout space. That is, it is designed for splitting a 2-gigabyte system partition to the desired section. It should be used only if this is specified separately. They have two - 512 th and 803rd. The most bug free - it's 512 th, it has not seen bugs / lags / red lines at startup. Most importantly if you sewed one with one of the two, you get a broken sections In accordance with the description of the pit, and the partition configuration will affect all your sewing until the next time the firmware you do not change it to another! That is, it all means that beg to 512-th pit 2 months or 8 firmware ago, he continues to work you
BUT! If you are on your device with any of the two pit-s put firmware requires a different breakdown (and not spend repartition include re-partition and selecting the desired pit), it will not be gathered hassle! It makes sense only if a check mark re-partition (see. Below)
* .zip- this is either some kind of your archive or the so-called "update.zip". How to find out if we need it or not - the archive should contain the folder "META-INF", if there is one, then this file is intended for flashing the device
Used programs: Odin, Kies, ADB
Odinorone- flasher service from Samsung, working with* .tar, * .pitand* .md5. There are several versions: 1.0 - the oldest; 1.3 - the most common; 1.7 - the new, comes with the Samsung Galaxy Tab, we also suitable. All three versions are perfectly cope with their tasks
Kiesorkittyorkies- program to synchronize with a desktop computer device, using* .enc
Adb- on-the DAS. (ADB - Android Debug Bus) is a special interface created for debugging based on Android OS devices. It is included in the SDK. It gives access to the phone via a computer even without a loaded / broken OS. To access the phone when running the OS, you must enable debug mode (USB debugging) in the phone's properties.
The main concepts: Re-Partition, PDA, CSC, Modem, Kernel / Kernel, Recovery, Download / Firmware mode, 3KR, root / Root, busybox / biziboks, SU / superuser Re-Partition, repatishn- tick in piercing through odin, which implies the existence of the file and the pitrepartition the phone's internal memory (for firmware), including internal flash drive with a consequent loss of all data from it! (Not all firmware versions)
PDA, pda, pda part- file extension* .tarand / or* .md5which is itself directly to the Android operating system
CSC, CSC- a file that contains additional components for a country / group of countries. Directly affects the initial language settings for specific operators, additional ID program
Modem, modem- specifically the firmware of the telephone part of the device
Kernel, the core- the operating system kernel is in the form of* .tarand / or* .md5for odin'a, as well as a zip for Recovery. It affects the operation of the entire apparatus in the most that neither is full!
Recovery, recovery- a special boot mode to restore / suturing device without using a PC. Can enter with additional commands / scripts / programs, or by a combination of: hold down the volume up button and the center button while continuing to hold them down, press and hold the power button, wait for the white letters "S", then let go of all buttons
Download, daunload, download mode / firmware- a special boot mode for the device firmware via PC. Can enter with additional commands / scripts / programs, or by a combination of: hold down the Volume Down button and the center button while continuing to hold them down, press and hold the power button, wait for the robot with a shovel, then everything let go of the button.
ZKR, 3-Button Modethe transfer to the Download and Recovery modes by the three buttons was called to be called a 3KR worker. If it does not go, 3KR does not work.
Root Law, Ruth. Simply put it is the administrator rights allow you to do whatever you want with your operating system.
Busybox, biziboks. This program / addition to the core system, expands the basic functionality. It contains file and other utility. Need for root.
SU, SuperUser, superuser. This is a program through which the desired application can be given / not allow root access. Need for root.
When flashing through any of the modes, you can separately flash any firmware component without flashing the rest.
What is the Recovery and what it eats: Recovery, recovery- a special boot mode to restore / suturing device without using a PC. Can enter with additional commands / scripts / programs, or by a combination of: hold down the volume up button and the center button while continuing to hold them down, press and hold the power button, wait for the white letters "S", then let go of all buttons
Additionally
It's special. loader that loads of butlodera, the essence of which is to amend the system as these changes can be done while running, to the same standard user simply does not have rights to modify the system (no Rights Ruth count because their initially, the user is not present).
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 opportunities rekaveri. They allow for example to flash custom firmware, give access to the memory card without loading the operating system, clean the Dalvik-cache, etc.
originalThere are three modes of operation:
Recovery2e - supplied firmware based on Android 2.1 Allows you to install / run any update.zip and execute specific scripts / commands used for different purposes in the update.zip
Recovery3e - supplied firmware based on Android 2.2 later he can not run / install update.zip not signed certificate Samsung'a. That is, it is a dead issue. It generally will not be considered.
ClockWorkMod, CWM, clockwork- modified by craftsmen
Recovery2e which allows in addition to installing / running any update.zip perform a variety of tasks: to monitor additional kernel options to install * .zip from anywhere in the internal flash drive, edit permissions, and much more ... Even if this type of you have not, then in the presence of version
Recovery2e can run
ClockWorkMod, CWM, clockwork by downloading it through the update.zip and then perform the required operations
What is lagfix, lagfiks: Single opinion does not exist!
Originally part of the phone system uses the file system (hereinafter - FS) calledRFS . In the opinion it is not very fast file system, although for some reason, Samsung chose it ... This FS has a very low read / write speed and therefore the machine slows down, buggy programs long open well etc .. . currently, the possible replacement of the FS to another (ext2, ext3, ext4, jfs, xfs .......). BUT! It's not so simple - replace it with a 100% impossible! We can replace only certain sections that you can format / convert to a particular file system. This means that when you lazite file manager on the phone's internal, certain daddy is not really dad, and hard disk partitions, that is, the internal flash. This all means that the application of a method for formatting / conversion of a section other than the other FS RFS and there is lagfiksom . It is worth noting that all available FS have some effect on the battery / memory / performance. Now more specifically. If you want to install one or the other lagfiks, first read what he has and what format / Convert to avoid misunderstanding of your own actions! We go further ... So, we have set the right "firmware", and set any certain lagfiks (it can be built into the kernel itself or be invoked through a program / script, etc., always read the original discussion topic or that way ), which does the formatting of section X in the jfs. What we have received is now: this means that all logical partitions have the phone file system RFS, and Section X - jfs. What we get from this: the speed of the work and the possible incompatibility with other software or cores. Why? Because Section X for the phone seems a separate hard drive, which is equivalent to when to take the ancient Windows 98 and shove her hard drive to NTFS, eventually Windows 98 will not see the hard drive. I would also add that the "vision" of the section is exactly and only the kernel, that is, if the kernel supports this filesystem then it can work with it. But with a small caveat - if required we understand the core we needed at the right section of the FS.
That is, it all meansIt is not recommended to combine different LAGFIKSY
Do this only if you have sufficient knowledge!
Other: Deodeksirovannaya, repacked firmware, the BLN De-odexed, Deodeksirovannaya firmwareAlmost all of the APK (the system partition) in a conventional firmware file is accompanied by ODEX. Part of the application (namely himself java code) contained just in this file. Therefore, any change of the apk file must be accompanied by appropriate editing file ODEX. Craftsmen to convert the file in programma.ODEX classes.odex and pushed them into the APK file, thereby reducing the size of the firmware, and most importantly - themselves now APK-files can be changed as you like, it is not a fatal effect on the operation of the system. This is called deodeksirovanie.
What is good - in deodeksirovannoy firmware can easily open the archiver APK-file, change it in resources (images, etc.) and restore the modified file to place into the firmware. In ordinary, this leads to the collapse of the system ...
original. Odeksirovanie itself is an optimization that same java code for a specific processor / device. That there is now a specific and to the point: * .odex file contains java recompiling the program code for a specific device, and the file is in the root file classes.dex * .apk contains java code that can be executed on
anydevice. This is the heart of Android: java virtual machine "Dalvik". And all this together means that each time the system will attempt to precompile
everythingclasses.dex apk are in their absence in dalvik-cache directory.
What does this mean for the user? System files (read fashion ukrashalki etc) to The Code. and deodeks. firmware is different and not compatible! For the average user, both the firmware works and looks exactly the same. repacked firmware. Repack-called update firmware, which lead to the full standard firmware, making three archives:
1. The full flash 3 parts: PDA - Operating System itself, MODEM - radio firmware, CSC -Regional settings, additional content from operators and database access points to internet for a specific region. This firmware sewn, overwriting is everything that was in the phone.
2. In the Update 1 file that contains the modem and firmware, and OSes, and (perhaps!) Data from the CSC, but he rolled over a certain firmware and data in its firmware does not fly off.
Romodel but can on the contrary, repack trehfaylovuyu firmware in the single-or throw out / add / replace if repacking any parts (such as bootloader, dbdata.rfs etc) in terms of adaptation to the region or to users' queries, as if repacking is usually removed passwords on file with the sewing. More
As standard firmwareNative and similar repacked firmware for the user and the work is no different. Other concepts in the modified nuclei and.
BLN, BackLight Notifications- when there are unanswered call or SMS, the backlight touch buttons lit up as long as you will not read or display.
thank
sergmarin for the addition.
Part of the material used
from here, For which a special thank you to the author.
Will complement as the arrival of the right thoughts in your head ...Complemented by concepts from the area close to the firmware, such as root, adb and etc.Post has been editedloza100 - 06.09.11, 20:20Reason for editing: + from TOLM! + From maximdudenko