Instructions for zeroing the meter and the receipt of the status"Normal" via В® Triangle Away

1. Download and enable set on the phoneВ® Triangle Away
2. Run the application and confirm that our phone isGT-I9300
3. If the application ask for something to download via the Internet ClickContinue
4. In the column"System" we find "Allow tracker to run" And put the "tick"
5. Click"Reset flash counter" and affirm - "Continue"
6. The phone will restart in the program menu - will showFlash counter (Number) and will offer two options for further action:
* Press Volume Up to Reset Counter and Status
* Press Volume Down to Reboot
To reset and choose the first pressing reiterateVolume up , For easy reboot without resetting the counter select Volume down
7. There will reset the counter and restart the phone

All the charm of using this version of the program is a simple and accessible method of receipt."Normal" the state of the phone, even with the presence of custom "Recovery" , for example CWM , on the latest versions of firmware, including XXELLA

There are, of course, and catch - as we still have a custom"Recovery" , then at the first use of it all "will return to the circles again!" - Counter "Tiknet" and a state "Changed"
ReuseВ® Triangle Away will allow you to reset the counters again - until the next use CWM .




Post has been editedVetal`M - 08.05.17, 14:43

Tonight! But you can make like this.

Instructions for the return of the state of the phone on the "usual" onNew loader and custom recoveryand reset the meters on NULL:
1. Reset the TRIANGLE AWAY counter program
2. Do all then according to the instructions below
Samsung GT-I9300 Galaxy S III - Firmware
And to fly the state to "change" will not be checked personally. Useful for those who have gathered in the SC carry and can not make a downgrade on the old bootloader


Post has been editedVetal`M - 08.05.17, 14:43

Maybe someone will come in handy.
Turn off the computer all the sounds of the photo / camcorder, the sound of charging and sound when downloading i9300.

Q: What is the difference between 1 file, 3 file and 5 file firmware?
A: Mostly differences in filling, but the result may differ. 1-file firmware - official, 3-file - service (emergency), and 5 files are the same emergency firmware, but made by our respected forumchanicA.S._id In the image and similarity of service, but for our region.

To begin with, I will cite examples of content.
The 1-file contains the archive * _home.tar.md5 and the ss_dl.dll file (DLL - Windows library we are not interested, we forget about it).
3 file contains 3 * .tar.md5 (if it is 4.0.4, then MX.PIT)
5-file contains 4 * .tar.md5 and mx.pit
(once met 4-file, about it below)

All .tar.md5 files are .Tar archives with MD5 as a signature.

The number of files .tar.md5 in the firmware does not have any semantic load for smartphone users, because it is done for the convenience of packing developers to have the opportunity for services in different countries to put this or that modem, CSC (Country Specific Configuration) from the same firmware. The number of files in the archive (in .tar.md5) of the service firmware variable variable and conditional, and can change due to service requests, there can also add empty images of EFS, UserData, Data, Bootloader and others.

1-file. The firmware is the official firmware manufactured by Samsung to update by phone. When using these firmware, all user data are saved, that is, after the firmware of the same-name firmware, the phone is immediately ready for further operation without any additional settings. Please note that it is the presence in the name HOME in a single-foam firmware signals users that user data is not deleted, and that the firmware is designed for a particular region. For sewing on the same as it was installed. This condition is maintained in the event of an increase in the firmware version as they are released by Samsung. In the case of using single-foam firmware to reduce the version, it is necessary to reset to the factory parameters before firmware and wipes from the recovery after the firmware, otherwise the phone will go to the cyclic reboot and will not boot, since the old firmware versions cannot read the databases created in new firmware.

3-file Russian The service firmware exists in a single instance (actually four files). Firmware version 4.0.4. Regional identity by default SER (Russia), however, suitable for all CIS regions (SEK and RTL - Ukraine, SKZ - Kazakhstan, CAC - Uzbekistan), respectively, regional affiliation from other regions will continue.

3 file service firmware were obtained using samsung kies and serial numbers From i9300 for some countries.

4 files It was obtained once, where the bootloader was allocated by a separate file. See Research.

5-file - these are firmware made by our respected forumchanic A.S._id Based on firmware 4.1.1 and 4.1.2 for the CIS regions. They differ from the three-fiction 4.0.4 presence of a separate file for the bootloader firmware (sboot.bin). From the 3 and 4 file service 4.1.2 differ in essentially packaging and the presence of a PIT file. Those. The essence has not changed, and the amenities have become more.

All service firmware apply to emergency recovery of the phone's performance. For example, in the phone's software failures, after Firmware Over-the-Air, Fota-update), after the firmware failure, after the firmware failure, SAMSUNG KIES program fails. All firmware can be sewed from ODIN PC and Mobile Odin programs, but with different results.

When installing service firmware from ODIN PC, user data is completely deleted (including SDCard0), third-party programs installed by the user and is replaced by bootloader. When installing service firmware from Mobile Odin, user data is searched only when the appropriate setting is set in the program itself. Bootloader from Mobile Odin will not flash.

Multifile firmware, as a rule, includes PDA-part (bootloader / bootloader-sboot.bin, core / kernel-boot.img, system-system.img, recovery - recovery.img, arm trustzone - tz.img, bootloader pictures - param.bin), regional part of the CSC (regional part-cache.img, auxiliary section-hidden.img), modem (modem.bin) and so-called PIT file (MX.PIT) for the markup of the system sections of the internal EMMC Memory. Separate parts can be flashing from Mobile Odin.


This information was provided by respected forum users.vasyadubov , A.S._id and zhakevich And later, with obtaining additional knowledge and experience, I compiled by me in this post.


Post has been editedVetal`M - 08.05.17, 11:58

Android - Jelly Bean 4.1.2

PDA:
I9300xxellc_root_odex Cl 764725
I9300xxellc_root_deodex Cl 764725


CSC_HOME:
CSC_I9300PHEELL3_PHE SPAIN.

BOOTLOADER:
Bootloader_i9300xxellc

DearViewer2007, GJF, Dima8389 Maybe now this post I brought your fair anger to my head, but I would like to ask you one question. Where do you have such confidence that the bootloader does not play any role in cure phones from "sudden death", and everything is laid only in the firmware core and you can not flash a new bootloader? I followed all the information that appeared in the topic about this and re-read all the links that were postponed on this issue. And nowhere, I have not seen an accurate description of the algorithms for the work of the fixing phones with this ill-fated chip from the "sudden death syndrome", only assumptions. And why not think about the fact that Samsung laid the fix launch algorithm through the bootloader. After all, this fix is ​​not needed for other chips, but only for one and the loader, defining the chip, gives a command to the kernel for the execution of the Fix if it detects the presence of this chip or does not give the command. I have repeatedly paid attention to the very close interconnection of the software components, and the appearance of fixes in the kernel with the advent of a new booter can be really interconnected. After all, none of us really knows what the unlable Samsung Corporation works there. Therefore, I think you should not give categorical recommendations to users that you do not need to install a new bootloader, as everything works so well. None of us knows thoroughly and exactly how it will refer further on the viability of the phone, so the user needs to give an independent choice, warning it about the consequences of installing a new bootloader and problems related if he, from his whim, will want to return to the old firmware. Hopefully for understanding and further fruitful cooperation.

Posted on 13.01.2013, 14:53:


I would put on a torrent with pleasure, but I can not support him for a long time. You can pull out the commander from the original firmware cache.img, hidden.img, sboot.bin, tz.img and from the last Russian back to the original cache.img, hidden.img. You don't need the second part, there are only in the CSCVersion.txt and SW_CONFiguration.xml files which is replaced by the firmware version from Russian to Spanish. To work the phone and the quality of communication does not affect.

Post has been editedvasyadubov - 13.01.13, 15:08

I have not said anywhere that the loader cannot be installed. I said "I would not put." SDS does not care in principle, because I have 32 GB.
And to put or not - the solution of everyone.
And I do not recommend on a very simple reason. MBR has never affected the vulnerability of the Windows kernel. LILO, GRUB and other did not affect Linux in any way. Their task is to provide download.
For this reason, I extremely doubt that the loader sews any algorithm that eliminates vulnerabilities and kernel errors.
To the question. Why updated the bootloader in XXELLA will answer this: the protection algorithm is tested from lowering the version and firmware of customs. Apparently, they found bugs - released xxellc. Perhaps they updated the blacklist in it. I won't be surprised if on xxellc return the old bootloader would be more difficult. Well, so on.

We emphasize once again: described - only my opinion that shares some masty developers from XDA,savagemessiahzine.comand a number of simple users. But I in no way impose him to anyone.

Post has been editedloza - 13.01.13, 16:31

Because he cannot play any role because his role is to raise the kernel.
Exception - Odin mode.



Because it is that the kernel is engaged. Determines the chip, raises the driver and at this point all operations occur through requests to the kernel. The loader itself is too small to accommodate everything necessary for working with a disk / flash drive. His role is to read the desired block from the flash drive to memory and transfer control.
The patch itself is that with each start and initialization of the flash drive after sleeping will ship into it a corrected firmware. How the mode works

Odin - I do not know. It may be in it there is some kind of loader role, but I doubt it to think that the entire software that is necessary for a full-fledged data record via USB cable.

Options:
To full clarity, I avoid using both the usual and mobile one.
Firmware I only put custom, which I wish, through Phils Touch.

Post has been editeddima8389 - 13.01.13, 16:46

For fans sewn

1. You can go crazy as you like. Those who write that the inner flash drive - the faster "wear out" the inner flash drive - never heard either the SSD drives and most likely never used flash drives.
2. When firmware there are two points that are fraughtbigProblems:

1. When changing CSC or something else may damage the EFS section and to fly IMEI. In total, the phone will be a good toy, just can't be able to call. It is treated with full backup and EFS recovery. How - already unsubscribed and more than once. No backup - most likely no phone. Cases in SC.
   
2. Invalid bootloader firmware. This is a sandy. What is the full. It is treated in SC, and is treated expensive. Avoid simply: with bootloader we take only when itreallyneed to.
   

I would raise it into the header and allocated. Because a huge amount of to put it mildly - novice users - just burn the desire to sew a phone for $ 600? Not quite understanding than risks.


Post has been editedVetal`M - 08.05.17, 13:59

download onto the people

Starting with LLA, the developers rule the bootloader in each next version. MD5:
sboot_ll4.bin - 3F24DF1C6F8106BA8722BC79E6149070.
Sboot_LLA.BIN - E475EAC5F710C97B0EB700487A3B74B2.
Sboot_llc.bin - 582CF3B9D6F2AFA1AA65CB585A3DC856.
Sboot_ma1.bin - A7C4C2390E5246AA2CB510BE63980C06.

With this, inside the incomprehensible response file, the MD5 remains unchanged from the LLA version of MA1. Maybe someone has already conducted a reizing bootloader, the information did not run?

Android ID can be viewed in: /data/data/com.android.providers.setting/databases/
Base: settings.db ->Section Secure ->Name: Android_ID ->Value - here and he



Post has been editedvasom - 15.01.13, 14:09

Not quite so - in Cache lies the execution file is not on the firmware, and after, from the recovery so you can flash and just CSC ... MD5, only if you flash the factory, then the wipe will be definitely, what is not sewed, but the bootoder can be flash at all without a computer - from the terminal

I think you should not roll back to the old bootloader, if you have already laid a new one (there is little, and then a friend with a scythe is waiting for an angle} -))
I see Samsung began to shove a new bootloader in all January firmware.
This means that in about the summer with the output of Android 4.2 ... the loader will not be old!
I doubt that people will sit on the old bootloader with the new 4.2 ...
Always flashingonly forward (already 5 years) and I do not feel any problems.
Samsung while "Pig" did not fit ...

I personally wait for Russian as I ask with a new bootloader (to avoid dancing with CSC)
I do not want, but you have to flash through one PC (to install a new bootloader) with the subsequent reset of the counters, heavily used to the mobile one.

if you about it
recovery.rar(5.61 MB)

(I packed him in the archive)

Skint CTOTO odex

Post has been editedwertu31 - 19.01.13, 16:56

Wertu31, clava.zip. (4.4 MB)

I'll tell you what I learned aboutSudden death syndrome / Sudden Death Syndrome / SDS On samsung gt-i9300 Galaxy S3.

First of all, I note that Samsung did not make any official statements about SDS. Somehow the questions-response of Samsung employee in the media, I do not take into account. However, on our forum there are messages with the problems of reading and writing to the internal flash memory.16Gb When firmware (for example, ODIN PC cannot receive information about posting sections - freezes on Get Pit for Mapping). Extreme case - the device is not loaded.

It is known that samsung is periodicallyPublishes the source codeFirmware, as requires a licensed Google policy for Android. So, in the publishing codeUpdate7.A certain strange fix was found (patch / patch / program code correcting the problem).

What makes this fix? With each initialization of the inner flash drive, it resets part of the flash memory controller code (VTU00M - controller, EMMC or Embedded Multimediacard - flash memory, and all together, figuratively speaking - disk). It is very similar to solving the problem of our SDS in the form of a preventive measure, although Samsung officially did not declare SDS fixes, as did not declare the fact of the presence of SDS itself.

Judging by the fix code, there is a cumulative error when working with a flash memory controller, which Fix constantly resets when the flash memory is initialized. Fix does not write a firmware into the flash memory controller, the Fix does not put the filter on accessing flash memory - Fix constantly reset the controller data. Thus, this procedure is not very correctly called Fix as such, but by solving the problem (I hope is successful). However, everyone got used to the "SDS Fix", so let Fix remain.

Running forward, voiceOpinion from the XDA Forum: During operation, a flush memory blocks can occur, and the SDS fix prevents this damage.

Fix is ​​located in Kernel (kernel), therefore must be present both in the Boot of the main firmware and in the boot recovery. The list where the firmware containing this fixes and parts of the firmware are constantly updated here:[Important] Sudden Death Fix - Are You Covered?.

Regarding the presence of SDS fixes from SamsungUpdate7.In the official firmware 4.1.2 for Russia i9300xxeLL4. ChangeList: 566833, Date: 12/10/2012.

1. Let me remind you, Fix appeared in the open UPDATE7 code. ComediffpresentedAndreiLux(MMC: Soft-Patch Movinand VTU00M (16GB) EMMC Failure).
2. Fixes have specific text strings "CMD13 (VC) Failed" and "VTU00M", which we can independently find in binary files without complicated passages with reengineering.

3. To independently find a boot.img file. I checked on the file taken from code_i9300xxell4_566833_rev00_user_low_ship.tar.md5Ambulance. To search in custom, the method below may not work (random coincidences of the scholar codes). This method for Waste is accurately working.
4. The hex editor will be needed. I tookNotepad ++andHex Editor Plugin.to him.
5. Open boot.img in the Hex editor.
6. Find the first match of 1F 8B (start GZIP)
7. Delete everything from addresses 0 to 1F8B (1F8B will be the beginning of our new file)
8. Find the string 00 1F 8B (in some customs it is not the first, but the second coincidence)
9. Remove everything after 00 from 1F8B to the end of the file (our 00 will be the end of the new file)
10. Save the GZ extension file. I saved like boot.img.gz
11. Either7zipOr using Total Commander (I checked on v7.56a) Remove the file (my WinRAR did not cope with the archive)

Open the extracted file and look for the VTU00M and CMD13 (VC) Failed line there. If found, then you have Fix.
I found Fixes Fixes in i9300xxell4 SER:

And if so, then in the Russian official firmware i9300xxell4 Ser Fix is ​​there! So I confirm researchXDA! Just in case I checked i9300xxeMB5. who already belongs to Update9. - Fix SDS will not go anywhere.

By the way, you can also check the image of the recovery - recovery.img

No longer doubt that Fix SDS is available in all the firmware 4.1.2 without exception. This means that i9300 with firmware 4.1.2 and abovenot Must be subject to SDS. SDS Fixes No. 4.0.4 and 4.1.1 firmware.

We are available for analysis two versions of the Fix Code - fromUpdate7.andUpdate9.. It is written that Update9 corresponds to the firmware XXEMB5. It is also written there that update7 corresponds to xxella, but if the SDS fix was found in XXELL4, then it is not necessary to unconditionally verify administrators OpenSource.samsung.com.

In the messageUltimate Galaxy S3 Unusual Freezing ThreadIt is assumed that without the SDS fixes, the blocks of flash memory deteriorate, and the SDS fixes do not deteriorate, but the phone can be filled with the already spoiled block. It is also indicated that from the XXEmb5 version, the problem of fading was solved with the new version of the Fix SDS ... Well, maybe, I do not know. In the update9 code, I did not understand this, but I do not pretend to the programmer's title. I do not draw conclusions.

In the samethe messageA method for fixing bad blocks is proposed. You need to install the firmware having the Fix SDS, and several times completely score flash memory by any data in order to mark the bad blocks during this operation, and not at the moment when you urgently need a smartphone, because this operation can hire 5 -20 minutes on the block. On there is attached.


At the moment I know:
1. Mobile Odin v3.65.When the firmware uses its temporary recovery - Flashkernels having Fix SDS.
2. TWRP 2.4.x.x Touch RecoveryIt has a fix SDS.

***
Thinking out loud.

If SDS scares you, then hurt any official firmware version 4.1.2, and it is better to firmware not lower than XXEMB5. It will not be worse! How to understand which firmware is newer, detailed in detail inby thismessage.

You can rout the device - the fact of rutting on the SDS does not affect. The CPU overclocking can affect, change sections, and a lot of things can be done under root, but this is another topic.

Bootloader ... if you come from logic, then in new bootloaders, SDS protection should be. At the same time, no one has yet been able to prove that in the bootloader there is a Fix SDS, in contrast to the obvious evidence of the availability of the SDS fixture in the kernel. Establish you, put a new bootloader or leave the old one. I left the old one.

Statistics on this forum shows that the overwhelming number of those who went to the service center had on board the firmware smartphone 4.0.4 and 4.1.1. The SC recorded problems with flash memory and changed the motherboard. Repair cost from 8 to 12 thousand rubles. So is it worth putting 4.0.4 and 4.1.1 if I have 4.1.2? ..


Post has been editedVetal`M - 08.05.17, 14:41

If you have established the British firmware and the Russian region is installed to it, and the modem also has a modem from some other firmware, then sorry, reset the counters and cheat the phone check by the SYSSCOPE file and get the "usual" state or as now in the new "Official" you can and will enjoy it, since you have applied official components, but you will never work update or with the help of the keys, as you never work, as the Samsung server is fooling and slipping them the firmware non-existent firmware for installing this nonsense. Since this was no longer it written in order to get the official update your firmware should have formally coinciding with officially produced firmwareSales Code, Modem, firmware version, CSC. And only when your installed firmware will fully coincide with these requirements, the Samsung server will give you a new firmware if it is released. In all other combinations of these four parameters you will receive a message "Your device is changed. No updates" . The only thing that does not affect the receipt of updates from Samsung is the root that will be deleted when updating. With the root, you can get and updated both through the air, and through the keys, if you still have a custom recovery to get an update and install it only through the vias .


Post has been editedVetal`M - 08.05.17, 14:04

To no longer have questions on this topic, which firmware goes for the CIS regions.