Sony Ericsson XPERIA arc / arc S - Firmware | Sony Ericsson XPERIA arc / arc S, Anzu, LT15i / LT18i, LT15a / LT18a
Sony Ericsson XPERIA Arc / Arc S - Firmware
Sony Ericsson XPERIA Arc / Arc S, Anzu, LT15i / LT18i, LT15a / LT18a
Description:Arc / Arc-s| Purchase:Arc � / Arc-s � | FAQ � | Arc / Arc S Firmware | Discussion Arc / Arc S � | Modification and decoration of Arc / Arc S � | Accessories �
power usage � | Sony & Sony Ericsson Club � | Arc / Arc S owners communication � | Custom firmware � | Arc / Arc S-MIUI ROM � | Arc / Arc S - Ubuntu Touch �
Arc / Arc S-Cyanogen Mod CM10 M2 (OS 4.1) � | Sony Ericsson Xperia Arc / Arc S - Cyanogen Mod 10.1, 10.2, 11, 12.x Firmware (OS 4.x.x - 5.x.x) �
Post has been editedAUDIMEN - 29.01.18, 09:00
Sony Ericsson XPERIA Arc / Arc S, Anzu, LT15i / LT18i, LT15a / LT18aDescription:Arc / Arc-s| Purchase:Arc � / Arc-s � | FAQ � | Arc / Arc S Firmware | Discussion Arc / Arc S � | Modification and decoration of Arc / Arc S � | Accessories �
power usage � | Sony & Sony Ericsson Club � | Arc / Arc S owners communication � | Custom firmware � | Arc / Arc S-MIUI ROM � | Arc / Arc S - Ubuntu Touch �
Arc / Arc S-Cyanogen Mod CM10 M2 (OS 4.1) � | Sony Ericsson Xperia Arc / Arc S - Cyanogen Mod 10.1, 10.2, 11, 12.x Firmware (OS 4.x.x - 5.x.x) �
Important information!
Answers to frequently asked questions! MANDATORY TO READ BEGINNERS !!!
So, you bought Ark !! Congratulations, this is a great phone if you know how to use it to the maximum.
Heck! That's the problem. You do not know what to do. You read the whole topic and got lost in the pile of information.
Do not worry. Read this guide and you will find answers to most of your questions!
How to flash the device?
You can install the official firmware:
Via"FlashTool"or"Wotan"- the bootloader of the device at the same time, can be both blocked and unlocked!
Or flash the device with"RS Companion"or"Sony Update Service" -
while the bootloader of your device must be locked (or unlocked in an unofficial way)!
* Manuals about the firmware of the device, can be found under the spoiler "INSTRUCTIONS" ...
What is root-rights?
In the world of technology, you can access any file in two modes:
1) As a primary user who can only read the file, but does not have the right to change it in any way.
2) As an administrator / Root, which can read, write and execute any file in OS / firmware.
By default, the operating system treats you as primary users. Ruth is a procedure that provides you
admin / superuser rights / su - which makes it possible to change any files inside your Android operating system.
Ruth is a big deal! You can remove the "shit". “Sran” are those crappy apps that are preloaded in your Arch -
(for example LetsGolf, WhatsApp, Timescape, Cards, PlayNow, etc.) and which are usually uselessly in memory, eating battery and braking the phone.
Also, if you have root-rights, by installing mods and themes, you can change the interface of the phone!
You can get root-rights in several ways (see Instructions)
or (with an unlocked bootloader), you can install a custom kernel with the presence of a built-in root.
Ruth and Warranty!
What is a bootloader?
According to Wikipedia - "When a computer (your smartphone - Arc) turns on, it usually does not have an operating system in memory (ROM or RAM).
The computer (phone) needs to run a relatively small program stored in memory, which loads the operating system. "
What is meant by unlocking the bootloader and why is it necessary?
Every Android phone has a bootloader that instructs the operating system kernel to boot in normal mode. But you have to understand one thing, though open-source Android
operating system and is available on a variety of hardware, all manufacturers (Sony Ericsson including) has its own version of the bootloader, specific to its equipment.
The bootloader is usually locked on Android devices, since manufacturers want you to stick with Android versions specifically designed for their devices.
If you want to install a custom version of the OS (Custom ROM), you need to have your bootloader unlocked. In simple terms: unlocking the bootloader allows you to install
custom (custom) firmware of Android phone, as well as the ability to install custom kernels, which usually have root, rekoveri, which allow you to overclock the phone processor,
provide the ability to record from the line, the ability to use "USB-OTG" and much more ...
There are two ways to unlock the bootloader: official and unofficial via "testpoint".
Check bootloader status:
In the "dialer" dial: * # * # 7378423 # * # *
Next item "Service info" - "Configuration"
At the bottom of the menu that opens, the bootloader "Rooting status:
Bootloader unlocked: Yes - This means the bootloader is UNLOCKED!
Bootloader unlock allowed: Yes - This means that the bootloader is ALLOWED / READY to unlock, but UNLOCKED!
Bootloader unlocked: NO - This means the bootloader has been UNLOCKED and re-LOCKED!
Bootloader unlock allowed: NO - This means unlocking the bootloader is IMPOSSIBLE!
How to unlock a bootloader?
When an unlocked bootloader, you need to know some nuances:
1) If you have a bootloader officially unlocked, you can lose the warranty from Sony Ericsson. And of course you won't be able to upgrade or
flash your phone using official SE programs (Sony Ericsson Update Service or SE PC Companion).
With unofficial unlocking, you can upgrade or reflash your phone using official SE programs (Sony Ericsson Update Service or SE PC Companion).
2) When the bootloader is officially unlocked, the "DRM" "SE" keys recorded in the device are erased. And all the programs that require these keys to work -
will no longer work, for example the official "Track ID". But you can download the "Track ID" in the drivers and utilities - which works with the unlocked bootloader !!
When unofficially unlocking "DRM", the keys "SE" are not erased.
The unlocked bootloader can be locked - but the "DRM" keys (in the case of off-unlock) are still not restored!
3) With the official and unofficial unlocking bootloader"IN NO EVENT, DO NOT DO AN UPDATE BY AIR (OTA Update)" -
because in this case your phone will fail. If this happens, you can usethis guideon reanimation phone!
* The procedure for unlocking and locking the bootloader can be found under the "INSTRUCTIONS" spoiler ...
What if the flash drive does not see the .ftf firmware files?
This problem is solved by installing an older version of the flash drive, for exampleFlashTool 0.9.8.0 Windows Edition(106.57Mb)
You must first completely remove the current version, including its folder on drive C.
What to do if the device went to the eternal reboot (bootlup)?
It is necessary to reflash the device with a flash drive, with a complete reset of the data (by checking all the checkboxes on"WIPE")
What to do if the device went to the eternal reboot (bootlup) - but the flashlight does not "catch" the phone, does the reboot constantly repeat?
What to do if there is a battery problem, all the time shows 100% charge?
You can also trycalibrate the battery
It is also written that the problem is solved byflashing another kernel
May fitthis manual
Was in the subject and such a message about this problem:
I have a 4.0.4 error on the drain of 100% of the battery, that is, either the battery is full, or is it empty how to fix it?
Problem solved, flash new flash drive 0.9.13 with reset customizations function
Another post aboutsolving the problem of 100% charge
Alternatively, use the search onthis issuePerhaps you will find another solution for yourself!
What to do if the flash error "Failed to verify sin header"
May fitthis decision
How to remove (unnecessary programs)?
Very simple - install the program"Titanium Backup"and remove all unnecessary programs through it.
For this:
1) After starting the program, press the "backup" button in the middle in the middle.
2) Click on the program you don't need.
3) In the menu that appears, press the "delete" button.
The list of programs that can be painlessly (or relatively painlessly) removed:
Actual for firmware "4.0.x - ICS"HERE!
For previous versions of firmware "2.3.x"HEREstillHEREandHEREand soHERE!
Applications that are unsafe to remove or are related to the functionality of the phone:HERE!
You can also usethis scriptwhich will remove all unnecessary applications.
You may be more comfortable.such a wayuninstall applications.
How to change the phone interface?
Install one of the mods or theme posted by kind peoplehereor atforum "XDA".
As a rule, when installing mods, system files are replaced.
A good instruction with pictures for installing mods postedhere!
ATTENTION!!! When installing a mod, ALWAYS make a backup copy and carefully monitor the correctly set permissions of the files.
You can transfer system files only with the "MOVE" command. Otherwise, the phone may go into perpetual reboot, which is treated by flashing software with the loss of all data.
Can I back up my system in case of a breakdown?
Yes, there is such an opportunity! To do this, you need to install "CWM Recovery". This can be done in several ways:
1) The easiest way to install * ClockWorkMod Recovery 5.0.2.7-nAa-r2 Auto-Installer * -
for the stock (native) kernel, does not require unlocking the bootloader (download drivers and utilities)!
2) Or install * ClockWorkMod Recovery 5.0.2.7-nAa-r2 * for the stock (native) kernel, does not require unlocking the bootloader (download in "drivers and utilities")!
3) You can install * SE Extreme Tweak Installer v1.8 * for the stock (native) kernel -
does not require unlocking the bootloader and has several useful pluses (download drivers and utilities)!
4) You can unlock the bootloader and install the custom kernel "DooMKerneL", this kernel is already sewn with "CWM Recovery" (or another kernel with the presence of "CWM").
How to use "CWM Recovery"?
To enter "CWM Recovery" - you need when you boot the phone, when the logo appears: often and quickly press the volume key down!
There we select the item "Backup and Restore" and make a backup by selecting "Backup", or restore the system (from our backup copy) by selecting "Restore".
Heck! That's the problem. You do not know what to do. You read the whole topic and got lost in the pile of information.
Do not worry. Read this guide and you will find answers to most of your questions!
How to flash the device?
You can install the official firmware:
Via"FlashTool"or"Wotan"- the bootloader of the device at the same time, can be both blocked and unlocked!
Or flash the device with"RS Companion"or"Sony Update Service" -
while the bootloader of your device must be locked (or unlocked in an unofficial way)!
* Manuals about the firmware of the device, can be found under the spoiler "INSTRUCTIONS" ...
What is root-rights?
In the world of technology, you can access any file in two modes:
1) As a primary user who can only read the file, but does not have the right to change it in any way.
2) As an administrator / Root, which can read, write and execute any file in OS / firmware.
By default, the operating system treats you as primary users. Ruth is a procedure that provides you
admin / superuser rights / su - which makes it possible to change any files inside your Android operating system.
Ruth is a big deal! You can remove the "shit". “Sran” are those crappy apps that are preloaded in your Arch -
(for example LetsGolf, WhatsApp, Timescape, Cards, PlayNow, etc.) and which are usually uselessly in memory, eating battery and braking the phone.
Also, if you have root-rights, by installing mods and themes, you can change the interface of the phone!
You can get root-rights in several ways (see Instructions)
or (with an unlocked bootloader), you can install a custom kernel with the presence of a built-in root.
Ruth and Warranty!
What is a bootloader?
According to Wikipedia - "When a computer (your smartphone - Arc) turns on, it usually does not have an operating system in memory (ROM or RAM).
The computer (phone) needs to run a relatively small program stored in memory, which loads the operating system. "
What is meant by unlocking the bootloader and why is it necessary?
Every Android phone has a bootloader that instructs the operating system kernel to boot in normal mode. But you have to understand one thing, though open-source Android
operating system and is available on a variety of hardware, all manufacturers (Sony Ericsson including) has its own version of the bootloader, specific to its equipment.
The bootloader is usually locked on Android devices, since manufacturers want you to stick with Android versions specifically designed for their devices.
If you want to install a custom version of the OS (Custom ROM), you need to have your bootloader unlocked. In simple terms: unlocking the bootloader allows you to install
custom (custom) firmware of Android phone, as well as the ability to install custom kernels, which usually have root, rekoveri, which allow you to overclock the phone processor,
provide the ability to record from the line, the ability to use "USB-OTG" and much more ...
There are two ways to unlock the bootloader: official and unofficial via "testpoint".
Check bootloader status:
In the "dialer" dial: * # * # 7378423 # * # *
Next item "Service info" - "Configuration"
At the bottom of the menu that opens, the bootloader "Rooting status:
Bootloader unlocked: Yes - This means the bootloader is UNLOCKED!
Bootloader unlock allowed: Yes - This means that the bootloader is ALLOWED / READY to unlock, but UNLOCKED!
Bootloader unlocked: NO - This means the bootloader has been UNLOCKED and re-LOCKED!
Bootloader unlock allowed: NO - This means unlocking the bootloader is IMPOSSIBLE!
How to unlock a bootloader?
When an unlocked bootloader, you need to know some nuances:
1) If you have a bootloader officially unlocked, you can lose the warranty from Sony Ericsson. And of course you won't be able to upgrade or
flash your phone using official SE programs (Sony Ericsson Update Service or SE PC Companion).
With unofficial unlocking, you can upgrade or reflash your phone using official SE programs (Sony Ericsson Update Service or SE PC Companion).
2) When the bootloader is officially unlocked, the "DRM" "SE" keys recorded in the device are erased. And all the programs that require these keys to work -
will no longer work, for example the official "Track ID". But you can download the "Track ID" in the drivers and utilities - which works with the unlocked bootloader !!
When unofficially unlocking "DRM", the keys "SE" are not erased.
The unlocked bootloader can be locked - but the "DRM" keys (in the case of off-unlock) are still not restored!
3) With the official and unofficial unlocking bootloader"IN NO EVENT, DO NOT DO AN UPDATE BY AIR (OTA Update)" -
because in this case your phone will fail. If this happens, you can usethis guideon reanimation phone!
* The procedure for unlocking and locking the bootloader can be found under the "INSTRUCTIONS" spoiler ...
What if the flash drive does not see the .ftf firmware files?
This problem is solved by installing an older version of the flash drive, for exampleFlashTool 0.9.8.0 Windows Edition(106.57Mb)
You must first completely remove the current version, including its folder on drive C.
What to do if the device went to the eternal reboot (bootlup)?
It is necessary to reflash the device with a flash drive, with a complete reset of the data (by checking all the checkboxes on"WIPE")
What to do if the device went to the eternal reboot (bootlup) - but the flashlight does not "catch" the phone, does the reboot constantly repeat?
Trewqaz @ 05/27/2012, 00:19
1 - disconnect phone
2 -Start the flash unit, click on the firmware, click "OK" - a picture appeared about connecting the phone with the "back" button pressed
3 -pull out the battery, connect via USB with the "back" button pressed and insert the battery with the "back" button pressed.
Flashstool will immediately begin to upload the firmware to the processor, which has not yet come to its senses "stuck in reboot"!
2 -Start the flash unit, click on the firmware, click "OK" - a picture appeared about connecting the phone with the "back" button pressed
3 -pull out the battery, connect via USB with the "back" button pressed and insert the battery with the "back" button pressed.
Flashstool will immediately begin to upload the firmware to the processor, which has not yet come to its senses "stuck in reboot"!
What to do if there is a battery problem, all the time shows 100% charge?
You can also trycalibrate the battery
It is also written that the problem is solved byflashing another kernel
May fitthis manual
Was in the subject and such a message about this problem:
Problem solved, flash new flash drive 0.9.13 with reset customizations function
Another post aboutsolving the problem of 100% charge
Alternatively, use the search onthis issuePerhaps you will find another solution for yourself!
What to do if the flash error "Failed to verify sin header"
May fitthis decision
How to remove (unnecessary programs)?
Very simple - install the program"Titanium Backup"and remove all unnecessary programs through it.
For this:
1) After starting the program, press the "backup" button in the middle in the middle.
2) Click on the program you don't need.
3) In the menu that appears, press the "delete" button.
The list of programs that can be painlessly (or relatively painlessly) removed:
Actual for firmware "4.0.x - ICS"HERE!
For previous versions of firmware "2.3.x"HEREstillHEREandHEREand soHERE!
Applications that are unsafe to remove or are related to the functionality of the phone:HERE!
You can also usethis scriptwhich will remove all unnecessary applications.
You may be more comfortable.such a wayuninstall applications.
How to change the phone interface?
Install one of the mods or theme posted by kind peoplehereor atforum "XDA".
As a rule, when installing mods, system files are replaced.
A good instruction with pictures for installing mods postedhere!
ATTENTION!!! When installing a mod, ALWAYS make a backup copy and carefully monitor the correctly set permissions of the files.
You can transfer system files only with the "MOVE" command. Otherwise, the phone may go into perpetual reboot, which is treated by flashing software with the loss of all data.
Can I back up my system in case of a breakdown?
Yes, there is such an opportunity! To do this, you need to install "CWM Recovery". This can be done in several ways:
1) The easiest way to install * ClockWorkMod Recovery 5.0.2.7-nAa-r2 Auto-Installer * -
for the stock (native) kernel, does not require unlocking the bootloader (download drivers and utilities)!
2) Or install * ClockWorkMod Recovery 5.0.2.7-nAa-r2 * for the stock (native) kernel, does not require unlocking the bootloader (download in "drivers and utilities")!
3) You can install * SE Extreme Tweak Installer v1.8 * for the stock (native) kernel -
does not require unlocking the bootloader and has several useful pluses (download drivers and utilities)!
4) You can unlock the bootloader and install the custom kernel "DooMKerneL", this kernel is already sewn with "CWM Recovery" (or another kernel with the presence of "CWM").
How to use "CWM Recovery"?
To enter "CWM Recovery" - you need when you boot the phone, when the logo appears: often and quickly press the volume key down!
There we select the item "Backup and Restore" and make a backup by selecting "Backup", or restore the system (from our backup copy) by selecting "Restore".
WHAT YOU CAN'T DO WITH THE APPARATUS !!!
When unlocked, the bootloader is updated by air (to do an OTA-update). Otherwise, get"dead brick".
If, nevertheless, you did it and your phone was worn out, then you can correct the situationfollowing this manual.
Roll back from 283,42,58, 62 and 69 to 181 because There is a glitch with a battery - it shows the level"0%"and does not charge!
Alternatively, roll back first to 184, and then to 181.The solution is but partialeitherexperience in "SC".
If, nevertheless, you did it and your phone was worn out, then you can correct the situationfollowing this manual.
Roll back from 283,42,58, 62 and 69 to 181 because There is a glitch with a battery - it shows the level"0%"and does not charge!
Alternatively, roll back first to 184, and then to 181.The solution is but partialeitherexperience in "SC".
- The results of the survey on the fastest and most stable version of the firmware - you can seehere!
- The results of the survey on the preference of kernels by users - you can seehere!
- Before you ask a question - look: Android OS FAQandGlossary ............. To compare the device with competitors and on the choice of devices, please contact: Selection and comparison.
- To discuss and search for third-party programs / games, use the following sections: Programs and Games. ... and: Software catalog - Android OS, Digest of programs for Android OS and Game Catalog - Android OS.
- The results of performance tests of Android devices, see the topic: Benchmark and results:Xpreria arc
Instructions
- Are common* UNLOCK AND LOCK BUTTONS:
Unofficial unlocking bootloader"Testpoint on the arch" thanks: dogsly
How to check if a bootloader is locked or unlockedthank youvovin07
Official bootloader unlockthank youRo.Ma.Ns + Video instruction
How to officially unlock the bootloader in 1 clickthank youmax_dor
Unlocking the bootloader and activating the "fastboot" mode using the "WotanServer"thank youcrazyrock
Unlocking the bootloader and activating the "fastboot" mode with "Omnius for SE"thank youff0255
Unofficial blocking of the bootloaderthank yourenai
* NUCLEAR FIRMWARE and CPU overclocking:
Manual for installing a custom kernelthank youeNrg *
Flashing custom kernel using "flashtool" +
Firmware custom kernel using "QuikIMG"thank youogabren
How to overclock the processorthank youeNrg *
How to overclock a simple "Arc" to 1.2 or 1.4Ghz without unlocking the bootloaderthank youwertuda
Detailed description of "Governors" and "I / O Schedulers"thank youmaxworks
* RADIO MODULES:
How to flash radio module separately from any firmware +
Radio modules 66,70,72,73,77 and 83thank youvovin07
Radio modules 36 and 64 + patches to themthank youogabren
A practical comparison of the work of 36, 66 and 72 radio modules +
Updated WiFi modules from 4.1.B.1.13 firmware (ICS 4.0.4)thank youfiberworm
* WORK WITH FIRMWARE FILES:
As with custom kernels and firmwares - it's safe to return to stock +
Restore system files - if there is no backupthank youogabren
aIUP - unpacking of firmware + backupthank youklyauz
* OTHER USE:
"QuikIMG" - Browse files.img quickly!thank you dogsly
How to use "FASTBOOT"thank youDenisjx
How to use "Flashtool" (device firmware)thank youFrozenSE
Record a conversation from the line on the SE Xperia Arc / Arc Sthank youogabren
Improving multitasking - implement the "SWAP"thank youTornadoX
Power Reduction "UNDERVOLTING" on SE Xperia Arc / Arc Sthank youevil_monkey
We implement "USB-OTG" or how to connect a USB flash drive to a phone on any core (only root is needed) +
another way "USB-OTG" (requires an unlocked bootloader)thank youAUDIMEN
How to make a "hard reset" on Arcthank youErmekg - "Android 4.0.x (ICS)"Firmware "Android 4.0.x (ICS)" +
Getting root rights to "Android 4.0.x (ICS)"thank youAUDIMEN
* WORK WITH FIRMWARE FILES:
Manual for pulling the original files from any assembly, any firmware Xperia arc / arc Sthank youcrazyrock - "Android 2.3.x"FIRMWARE Sony Ericsson XPERIA Arc / Arc Sthank youdogsly
Getting root rights to "Android 2.3.x (GB)"thank youAUDIMEN
* WORK WITH FIRMWARE FILES:
Manual for pulling the original files from any assembly, any firmware Xperia arc / arc Sthank youmuzontnt
Another manual for pulling the original files from any assembly, any Xperia arc / arc S firmwarethank youogabren
And another manual for pulling the original files from any assembly, any firmware Xperia arc / arc Sthank youcrazyrock - Archive-outdated1. Get root
2. Get root on any firmware on a phone with an unlocked bootloader , as well as the manual for the firmware via fastboot - thanks tRippinthehead . Another instruction with two ways give thanks tretiakov
3. Xperia firmware manual arc / arc S free tool WotanClient thank you muzontnt
4. Official unlocking bootloader and firmware on the example of android 2.3.4 + getting root. In pictures for beginners thank you dogsly
5. Manual for rolling back to firmware 3.0.A.2.181 using Flashtool + Manual for installing firmware 3.0.1.A.0.145 using Flashtool (for non-user device) thank you Generalgrant
6. The treatment of major problems with Wi-Fi
7. List of regions and how to find out your region
8. Change firmware region to RUS - It is established that the substitution of build.prop leads to the impossibility of updating by air.
9. Beta version of Android IceCreamSandwich 4.0 for Sony Ericsson XPERIA Arc / Arc S - For reference only !!!
Drivers and Utilities
- DriversDriver installation* If after installing these drivers or utilities with the drivers, something does not work, it is probably worth it - RELOAD THE COMPUTER!
* Installing drivers:
1) On the “My Computer” label, right-click (RMB) and select “Management” from the menu that appears.
2) Go to the "Device Manager" and see an unknown device. On an unknown device, press the RMB and select the item "Update driver"
3) Select the section "Search for drivers on this computer"
4) Use the "Browse" button to select a folder with firewood
5) Check if the checkbox next to the item "Including subfolders" is checked (should be) and click the "next" button -
The operating system will install the appropriate drivers and the device will be determined.
* Detailed manual for installing drivers Flashtool-drivers.exe: Tyk!
* Some useful tips on installing drivers: TIME - TWO - THREE - FOUR!
* Installing drivers on WINDOWS 8 / 8.1 x86 / x64: Tyk!
* How to install the "fastboot" driver on "Windows 8 x32 / x64": Tyk!Driver files
Xperia_ARC_PLAY_NEO_acroIS11s_acroSO_02C_USB_drivers.zip(6.11 MB)
* If not suitable, you can try:theseorthese
* Drivers for flash:Flashtool drivers.rar(56.09 megabytes)
* Fastboot drivers:fastboot_with_Android_USB_file.rar - CWM Recovery* ClockWorkMod Recovery - 5.0.2.7-nAa-r2 Auto-Installer * - the easiest way to install "CWM Recovery" on stock firmware!
* ClockWorkMod Recovery 5.0.2.7-nAa-r2 *- "CWM Recovery" only for stock firmware!
* SE Extreme Tweak Installer v1.8 *- "CWM Recovery" only for stock firmware + some useful pluses!
* AROMA Filemanager * - file manager, works from "CWM Recovery" without booting the system! - SEUSWithout registering:
Update_Service_Setup_2.11.10.7.exe (39.04 MB)
Registration required:SE Update Service Pro - FlashtoolBefore downloading and even installing - disable antivirus!Time-tested versions for our device!FlashTool 0.9.10.1 Windows Edition (107.47Mb)
(MD5: F5F14804F28009E76F0A3F7B841FDCE8)
FlashTool 0.9.8.0 Windows Edition (106.57Mb)
(MD5: 02E29366823679DC95498CCC0ADF393C)
FlashTool 0.6.9.1 Windows Edition (123.24Mb)
(MD5: 9E6AEAA286FC145FDEBD65F6CC492585)
Always the latest version of "FlashTool" onsavagemessiahzine.com - It is important: to use versions not higher than 18.5 or 18.6 - Emma"Emma" - tool for Xperia ™ devices only With officially unlocked bootloader !!!
In principle, as I understand it, this is the same "SEUS", but it works on devices with a officially unlocked bootloader!
So, go to the site"SONY" , click on "Download Flash tool for Xperia ™ devices (61.6 MB)" and download the archive.
Unpack the archive and install the program by running "Emma_Setup.exe". After the proposal to restart the computer - restart!
Next, run "Emma", enter the username and password (If you previously registered in "SEUS", login and password are suitable ).
If you are not registered yet, select the item "New user registration" in the window.Note: when entering the password during registration -
it must contain numbers and letters, with letters - both small and large! After registration (as I understand it), the key will come in the mail.
You can do without registration:
To do this, copy the file from the archive "Customization.ini" and drop it into the folder where you installed the program ... / Sony Mobile / Emma
After this procedure, the program will run without prompting for a password!
Having entered the program for the first time, she will install and restart the computer again before it!
Next in the program, select "Close Welcome" and connect the disabled body with the left back button pressed to the computer (flash mode) -
the green diode on the body will light up, the program will detect the device and offer a list of available software versions (if any) ...
How to use "Emma", you can see on page"SONY" - TrackID - works with unlocked bootloader !!!* Install as a normal application:com.sonyericsson.trackid.apk(4.73 MB)
* If it fails to install, then install as all"FASHION"in the system / app folder! - UtilitiesPC Companion (25 mb)
Android SDK Tools
Work with contacts, synchronization and much more:MyPhoneExplorer_Setup_1.8.2.exe(4.41 MB)
Official firmware
- If the firmware accidentally pulled the cord or after the next experiments -
The phone turned off and does not turn on, then before going to the "SC" do: THIS!!!
How to roll back from the firmware "4.0.x" to the firmware "2.3.x"!
Official firmware "Android 2.3.x / Android 4.0.x (ICS)" - The release history of firmwareGingerbread:
3.0.A.2.181 - Mar 25, 2011 (2.3.2)
3.0.A.2.184 - Mar 25, 2011 (2.3.2)
3.0.1.A.0.138 - May 3, 2011 (2.3.2)
3.0.1.A.0.145 - May 24, 2011 (2.3.3)
4.0.A.2.368 - August 2, 2011 (2.3.3)
4.0.1.A.0.266 - September 6, 2011 (2.3.4)
4.0.1.A.0.283 - September 16, 2011 (2.3.4)
4.0.2.A.0.42 - October 7, 2011 (2.3.4)
4.0.2.A.0.58 - October 21, 2011 (2.3.4)
4.0.2.A.0.62 - December 20, 2011 (2.3.4)
4.0.2.A.0.69 - Feb 16, 2012 (2.3.4)
ICS:
4.1.A.0.562 - Mar 30, 2012 (4.0.3)
4.1.B.0.431 - Jun 15, 2012 (4.0.4)
4.1.B.0.587 - Aug 8, 2012 (4.0.4) - Changes in firmwareDepending on the region of the firmware - not everything in the list can match!
* 368>>>283 *
Swipe keyboard
Added bold on the keyboard
New fade effect
3D / panorama
New Widgets
Facebook inside xperia 2.0
New folder view
Removed problems with tags in the music player.
* 283>>>42 *
Added antivirus "McAfee"
Removed applications "download games / applications"
Added file manager "ASTRO"
Now you can remove the icon "data traffic in the tray"
* 42>>>58 *
Added by:
AASTOCKS
YOUKU
JIEPANG
MESSENGER
APPLICATION INSTALLER
ASPHALT5
Power saving mode
And a couple of Chinese applications.
* 58>>>62 *
Changed the radio module to version 64.
And they covered the possibility of obtaining root rights with a blocked bootloader.
* 62>>>69 *
Firmware for another region,
so the difference seems to be only in a couple of some applications!
* 69>>>562 "Android 4.0.x ICS" *
What's new and good in "Android 4.0.x ICS"!
And also - a reasonable opinion about "Android 4.0.x ICS"!
* 562>>>431 *
Any corrections. At least the desktop is no longer so hard!
* 431>>>587 *
Pros and cons "587"!
Custom kernels
- Custom kernels "Android 4.0.x (ICS)"
- Custom kernels "Android 2.3.x"
- Exclusive article describing custom kernels
- Archive-obsolete kernels for "Android 2.3.x"DooMKernel ( v10 ) [Arc / Arc S] (FW: 4.0.A.2.368):boot.img (6.43 MB)
DooMKernel (v11 ) [Arc / Arc S] (FW: 4.0.1.A.0.283 / 4.0.2.A.0.42):boot.img (6.77 MB)
DooMKernel (v12 ) [Arc / Arc S] (FW: 4.0.1.A.0.283 / 4.0.2.A.0.42) [1.6Ghz version] :boot.img (6.77 MB)
DooMKernel (v12 ) [Arc / Arc S] (FW: 4.0.1.A.0.283 / 4.0.2.A.0.42) [2.0Ghz version] :boot.img (6.77 MB)
DooMKernel (v12 ) [Arc / Arc S] (FW: 4.0.1.A.0.283 / 4.0.2.A.0.42) modCWM [1.6Ghz version] :boot.img (7.77 MB)
DooMKernel (v13 ) [Arc / Arc S] (FW: 4.0.2.A.0.42) [1.6Ghz version] :boot.img (7.77 MB)
DooMKernel (v13 ) [Arc / Arc S] (FW: 4.0.2.A.0.42) [2.0Ghz version] :boot.img (7.77 MB)
DooMKernel (v13 ) [Arc / Arc S] (FW: 4.0.2.A.0.42) modCWM-v2 [1.6Ghz version] :boot.img (6.77 MB)
DooMKernel (v13 ) [Arc / Arc S] (FW: 4.0.2.A.0.42) modCWM-v2 [2.0Ghz version] :boot.img (6.77 MB)
DooMKernel (v14 ) [Arc / Arc S] (FW: 4.0.2.A.0.42 / 4.0.2.A.0.58) [1.6Ghz version] and [2.0Ghz version] : HERE
Cap updates
29.01.18 Unlocking the bootloader and activating the "fastboot" mode with "Omnius for SE"
Instructions how to make a "hard reset" on Arc
09.03.16 Changes in Announcement: Theme Designing Rules
03.07.14 LT18i 4.0.2.A.0.62 - rutovannaya assembly, the most cleaned of trash
02.05.14 Fixed outdated / broken links
Added answers to frequently asked questions.
Saved and closed a survey about custom kernels
19.07.13 In custom kernels added: LuPuS V16
16.07.13 In custom kernels added: Vengeance v1.38 (with modified CWM Recovery) - 4.1.B.0.587
29.05.13 In the instructions added: How to officially unlock the bootloader in 1 click
In custom kernels added: LuPuS GB / LuPuS V14 / KTG anzu Kernel v2.00 / Vengeance v1.38
30.04.13 In the instructions added: Route without unlocking the bootloader, for 4.0.x and 2.3.4
In the custom kernels added: Vengeance v1.35 / v1.36 - 4.1.B.0.587
17.04.13 Added to custom kernels: LuPuS V11 / V12 - 4.1.B.0.587
10.04.13 In the custom kernels added: RUSH-Kernel V13 - 4.1.B.0.587
09.04.13 In the official firmware added: LT18i 4.1.B.1.13 Vodafone DE.rar
08.04.13 In custom kernels added: Vengeance v1.34 - 4.1.B.0.587
31.03.13 In the custom kernels added: RUSH-Kernel V11 / V12 - 4.1.B.0.587
27.02.13 In custom kernels added: LuPuSv10 [LINARO]
19.02.13 Added to the general instructions: "83" radio module.
18.02.13 In custom kernels added: Vengeance v1.32 for 4.1.B.0.587
17.02.13 Added to general instructions: Detailed description of "Governors" and "I / O Schedulers"
Added: firmware 4.1.B.0.587 and 77 radio module for LT18a
12.02.13 In custom kernels added: Vengeance v1.31 for 4.1.B.0.587
08.02.13 In custom kernels added: Vengeance v1.30 for 4.1.B.0.587
Added updated WiFi modules from 4.1.B.1.13 firmware to the radio modules (ICS 4.0.4)
31.01.13 In custom kernels updated: Serene to v1.28 for 4.1.B.0.587
15.01.13 In custom kernels added: Serene v1.21 for 4.1.B.0.587
In drivers and utilities added: "FlashTool 0.9.10.1 Windows Edition"
02.01.13 In the custom kernels added: RUSH-Kernel V10 - 4.1.B.0.587
27.12.12 In the instructions added: aIUP - unpacking of firmware + backup
In the custom kernels added: RUSH-Kernel V9 - 4.1.B.0.587
23.12.12 In custom kernels added: LuPuSv9 [LINARO]
In custom kernels added: Core VDS (4.0.x)
19.12.12 In custom kernels added: RUSH-Kernel V8 - 4.1.B.0.587
07.12.12 In drivers and utilities added: tool "Emma"
In the custom kernels added: RUSH-Kernel V6 - 4.1.B.0.587
24.11.12 Added a couple of tips on installing drivers
19.11.12 In the driver added: How to put the driver "fastboot" on "Windows 8 x32 / x64"
15.11.12 In drivers and utilities added: "Flashtool 0.9.9.0 Windows Edition"
In custom kernels added: RUSH-Kernel V3 - 4.1.B.0.587
04.11.12 Added a survey about the best kernel on 4.0.x
Under the first spoiler posted a script that removes all unnecessary applications
02.11.12 In custom kernels added: LuPuSv8 [LINARO], as well as ArcKnight v4.1
30.10.12 In custom kernels added: ArcKnight v4
19.10.12 Added information about "Android 4.1 Jelly Bean"
16.10.12 In custom kernels added: KERNEL SEGA V9 for 4.1.0.B.587
02.10.12 In drivers and utilities added: "Flashtool 0.9.8.0 Windows Edition"
28.09.12 Updated spoiler: "Answers to frequently asked questions"
27.09.12 In the custom kernels added: KERNEL SEGA V8 for 4.1.0.B.587
25.09.12 In custom kernels added: LuPuSv7 [LINARO] for 4.1.0.B.587
02.09.12 In the official firmware added: LT18i 4.1.B.0.587 Baltic
26.08.12 In the official firmware added: LT18i 4.1.B.0.587 PCT
Added custom kernels: ArcKnight RC3.3 Test Version for 4.0.4
21.08.12 In the official firmware added: LT15i 4.1.B.0.587 PCT
18.08.12 In custom kernels added: kernels for firmware 4.1.0.B.587
16.08.12 In the official firmware added: 4.1.0.B.587
Added to general instructions: "77" radio module.
12.08.12 In the official firmware added: All assemblies and regions for "LT18i", in one post - on "XDA"
04.08.12 Added to general instructions: Comparison of work 36, 66 and 72 radio modules
28.07.12 In the official firmware added: LT18i 4.0.2.A.0.69 Germany
23.07.12 In drivers and utilities added: "Flashtool 0.9.0.0 Windows Edition"
15.07.12 Added instructions for unlocking the bootloader and
activating the "fastboot" mode using the "WotanServer"
13.07.12 Added instructions for overclocking SE Arc!
27.06.12 In the instructions added: Manual for pulling the original files from any firmware!
21.06.12 In kernels updated: "ArcKnight Kernel" to version RC3.1 (FW: 4.1.B.0.431)
12.06.12 In the official firmware added: How to roll back from the firmware "4.0.x" to the firmware "2.3.x"!
In the official firmware "2.3.x" added: LT18i 4.0.2.A.0.62 PCT
11.06.12 In the official firmware added: "ICS" LT18i 4.1.B.0.431 PCT
07.06.12 Added to the general instructions: "72" radio module.
Added in the instructions: about the root-rights to the "62" firmware.
In the official firmware added: "ICS" LT18i 4.1.B.0.431 Central European (1254-2716).
05.06.12 In the official firmware added: "ICS" LT15i 4.1.B.0.431 PCT and LT15i 4.1.B.0.431 Generic Global World.
In drivers and utilities added: upgrade to "Flashtool 0.8.5.0 Windows Edition"
01.06.12 Added update information on "ICS".
Instructions how to make a "hard reset" on Arc
09.03.16 Changes in Announcement: Theme Designing Rules
03.07.14 LT18i 4.0.2.A.0.62 - rutovannaya assembly, the most cleaned of trash
02.05.14 Fixed outdated / broken links
Added answers to frequently asked questions.
Saved and closed a survey about custom kernels
19.07.13 In custom kernels added: LuPuS V16
16.07.13 In custom kernels added: Vengeance v1.38 (with modified CWM Recovery) - 4.1.B.0.587
29.05.13 In the instructions added: How to officially unlock the bootloader in 1 click
In custom kernels added: LuPuS GB / LuPuS V14 / KTG anzu Kernel v2.00 / Vengeance v1.38
30.04.13 In the instructions added: Route without unlocking the bootloader, for 4.0.x and 2.3.4
In the custom kernels added: Vengeance v1.35 / v1.36 - 4.1.B.0.587
17.04.13 Added to custom kernels: LuPuS V11 / V12 - 4.1.B.0.587
10.04.13 In the custom kernels added: RUSH-Kernel V13 - 4.1.B.0.587
09.04.13 In the official firmware added: LT18i 4.1.B.1.13 Vodafone DE.rar
08.04.13 In custom kernels added: Vengeance v1.34 - 4.1.B.0.587
31.03.13 In the custom kernels added: RUSH-Kernel V11 / V12 - 4.1.B.0.587
27.02.13 In custom kernels added: LuPuSv10 [LINARO]
19.02.13 Added to the general instructions: "83" radio module.
18.02.13 In custom kernels added: Vengeance v1.32 for 4.1.B.0.587
17.02.13 Added to general instructions: Detailed description of "Governors" and "I / O Schedulers"
Added: firmware 4.1.B.0.587 and 77 radio module for LT18a
12.02.13 In custom kernels added: Vengeance v1.31 for 4.1.B.0.587
08.02.13 In custom kernels added: Vengeance v1.30 for 4.1.B.0.587
Added updated WiFi modules from 4.1.B.1.13 firmware to the radio modules (ICS 4.0.4)
31.01.13 In custom kernels updated: Serene to v1.28 for 4.1.B.0.587
15.01.13 In custom kernels added: Serene v1.21 for 4.1.B.0.587
In drivers and utilities added: "FlashTool 0.9.10.1 Windows Edition"
02.01.13 In the custom kernels added: RUSH-Kernel V10 - 4.1.B.0.587
27.12.12 In the instructions added: aIUP - unpacking of firmware + backup
In the custom kernels added: RUSH-Kernel V9 - 4.1.B.0.587
23.12.12 In custom kernels added: LuPuSv9 [LINARO]
In custom kernels added: Core VDS (4.0.x)
19.12.12 In custom kernels added: RUSH-Kernel V8 - 4.1.B.0.587
07.12.12 In drivers and utilities added: tool "Emma"
In the custom kernels added: RUSH-Kernel V6 - 4.1.B.0.587
24.11.12 Added a couple of tips on installing drivers
19.11.12 In the driver added: How to put the driver "fastboot" on "Windows 8 x32 / x64"
15.11.12 In drivers and utilities added: "Flashtool 0.9.9.0 Windows Edition"
In custom kernels added: RUSH-Kernel V3 - 4.1.B.0.587
04.11.12 Added a survey about the best kernel on 4.0.x
Under the first spoiler posted a script that removes all unnecessary applications
02.11.12 In custom kernels added: LuPuSv8 [LINARO], as well as ArcKnight v4.1
30.10.12 In custom kernels added: ArcKnight v4
19.10.12 Added information about "Android 4.1 Jelly Bean"
16.10.12 In custom kernels added: KERNEL SEGA V9 for 4.1.0.B.587
02.10.12 In drivers and utilities added: "Flashtool 0.9.8.0 Windows Edition"
28.09.12 Updated spoiler: "Answers to frequently asked questions"
27.09.12 In the custom kernels added: KERNEL SEGA V8 for 4.1.0.B.587
25.09.12 In custom kernels added: LuPuSv7 [LINARO] for 4.1.0.B.587
02.09.12 In the official firmware added: LT18i 4.1.B.0.587 Baltic
26.08.12 In the official firmware added: LT18i 4.1.B.0.587 PCT
Added custom kernels: ArcKnight RC3.3 Test Version for 4.0.4
21.08.12 In the official firmware added: LT15i 4.1.B.0.587 PCT
18.08.12 In custom kernels added: kernels for firmware 4.1.0.B.587
16.08.12 In the official firmware added: 4.1.0.B.587
Added to general instructions: "77" radio module.
12.08.12 In the official firmware added: All assemblies and regions for "LT18i", in one post - on "XDA"
04.08.12 Added to general instructions: Comparison of work 36, 66 and 72 radio modules
28.07.12 In the official firmware added: LT18i 4.0.2.A.0.69 Germany
23.07.12 In drivers and utilities added: "Flashtool 0.9.0.0 Windows Edition"
15.07.12 Added instructions for unlocking the bootloader and
activating the "fastboot" mode using the "WotanServer"
13.07.12 Added instructions for overclocking SE Arc!
27.06.12 In the instructions added: Manual for pulling the original files from any firmware!
21.06.12 In kernels updated: "ArcKnight Kernel" to version RC3.1 (FW: 4.1.B.0.431)
12.06.12 In the official firmware added: How to roll back from the firmware "4.0.x" to the firmware "2.3.x"!
In the official firmware "2.3.x" added: LT18i 4.0.2.A.0.62 PCT
11.06.12 In the official firmware added: "ICS" LT18i 4.1.B.0.431 PCT
07.06.12 Added to the general instructions: "72" radio module.
Added in the instructions: about the root-rights to the "62" firmware.
In the official firmware added: "ICS" LT18i 4.1.B.0.431 Central European (1254-2716).
05.06.12 In the official firmware added: "ICS" LT15i 4.1.B.0.431 PCT and LT15i 4.1.B.0.431 Generic Global World.
In drivers and utilities added: upgrade to "Flashtool 0.8.5.0 Windows Edition"
01.06.12 Added update information on "ICS".
Post has been editedAUDIMEN - 29.01.18, 09:00
Muzontnt @ 05/08/2011, 20:24
How does the region change to rus? What for what? Than?
jekwww @ 05/09/2011, 09:20
muzontnt, I join the question. I generally have Hong Kong.
tom044 @ 05/11/2011, 13:51
DO THE SAME JOIN AS A REGION CHANGE WHO CAN ANYTHING IN A COURSE?
muzontnt
jekwww,
tom044,
Download the file from the PCT build.txt phone (attached), rename it to build.prop and using Root Explorer to copy the folder System \ agreeing on a replacement of the same name file in the specified folder (requires root, Root Explorer must be set to mode Mount R / W). And do not forget to specify the file corresponding to the right - in Root Explorer a long tap on the file, the pop-up menu, select the permissions (authorization), put a tick in all the squares of the first column and in the top box of the second, and then restart your phone in order to select the resolution for this file to take effect. Having done all this, you can start flashing apparatus.
build.txt(4.14 KB)Post has been editedGeneralgrant - 24.05.11, 10:18
Manual for rolling back to firmware 3.0.A.2.181 using Flashtool
ATTENTION!!!Be sure to read the spoiler in the topic header:(WHAT YOU CAN'T DO WITH THE APPARATUS !!!)
1. DownloadFlashTool_0.2.9.1and unzip it to C: \ (should look like C: \ Flashtool_0.2.9.1).
If the link failed to download the file, use the alternative link -FlashTool_0.2.9.1.
2. DownloadLT15i_3.0.A.2.181_Russian.ftfand place it in the folder C: \ FlashTool_0.2.9.1 \ firmwares \.
If the link failed to download the file, use the alternative link -LT15i_3.0.A.2.181_Russian.ftf
3. Run X10FlashTool.exe and click on Flash.
4. In the pop-up window, click on ok.
5. Next, do everything as shown in the new pop-up help window with the only difference that the "Back" button on our device is located on the left.
6. Wait for the end of the process of pouring firmware into the phone,the corresponding message will appear in the flasher log window - Flashing finished then disconnect the phone from the BB and turn it on.
7. Well, do not forget to enable debugging via USB and installing applications from unknown sources after first turning on the phone.
Detailed manual in pictureshereunder the second spoiler. Do everything up to 5 points.
Manual for installing firmware 3.0.1.A.0.145 using Flashtool (for non-powered device)
1. DownloadFlashTool_0.2.9.1and unzip it to C: \ (should look like C: \ Flashtool_0.2.9.1).
If the link failed to download the file, use the alternative link -FlashTool_0.2.9.1.
2. DownloadLT15i_3.0.1.A.0.145_Russian.ftfand place it in the folder C: \ FlashTool_0.2.9.1 \ firmwares \.
If the link failed to download the file, use the alternative link -LT15i_3.0.1.A.0.145_Russian.ftf
3. Run X10FlashTool.exe and click on Flash.
4. If there is a desire to save the installed user programs and data, then in the pop-up window, remove the check mark from the "Wipe User Data" item and click on ok. If there is no such desire, then just click on ok.
5. Next, do everything as shown in the new pop-up help window with the only difference that the "Back" button on our device is located on the left.
6. Wait for the end of the process of pouring firmware into the phone,the corresponding message will appear in the flasher log window - Flashing finished then disconnect the phone from the BB and turn it on.
7. Well, do not forget to enable debugging via USB and installing applications from unknown sources after first turning on the phone.
Detailed manual in pictureshereunder the second spoiler. Do everything up to 5 points.
Post has been editedAUDIMEN - 20.02.13, 07:43
ATTENTION!!!Be sure to read the spoiler in the topic header:(WHAT YOU CAN'T DO WITH THE APPARATUS !!!)
1. DownloadFlashTool_0.2.9.1and unzip it to C: \ (should look like C: \ Flashtool_0.2.9.1).
If the link failed to download the file, use the alternative link -FlashTool_0.2.9.1.
2. DownloadLT15i_3.0.A.2.181_Russian.ftfand place it in the folder C: \ FlashTool_0.2.9.1 \ firmwares \.
If the link failed to download the file, use the alternative link -LT15i_3.0.A.2.181_Russian.ftf
3. Run X10FlashTool.exe and click on Flash.
4. In the pop-up window, click on ok.
5. Next, do everything as shown in the new pop-up help window with the only difference that the "Back" button on our device is located on the left.
6. Wait for the end of the process of pouring firmware into the phone,the corresponding message will appear in the flasher log window - Flashing finished then disconnect the phone from the BB and turn it on.
7. Well, do not forget to enable debugging via USB and installing applications from unknown sources after first turning on the phone.
Detailed manual in pictureshereunder the second spoiler. Do everything up to 5 points.
Manual for installing firmware 3.0.1.A.0.145 using Flashtool (for non-powered device)
1. DownloadFlashTool_0.2.9.1and unzip it to C: \ (should look like C: \ Flashtool_0.2.9.1).
If the link failed to download the file, use the alternative link -FlashTool_0.2.9.1.
2. DownloadLT15i_3.0.1.A.0.145_Russian.ftfand place it in the folder C: \ FlashTool_0.2.9.1 \ firmwares \.
If the link failed to download the file, use the alternative link -LT15i_3.0.1.A.0.145_Russian.ftf
3. Run X10FlashTool.exe and click on Flash.
4. If there is a desire to save the installed user programs and data, then in the pop-up window, remove the check mark from the "Wipe User Data" item and click on ok. If there is no such desire, then just click on ok.
5. Next, do everything as shown in the new pop-up help window with the only difference that the "Back" button on our device is located on the left.
6. Wait for the end of the process of pouring firmware into the phone,the corresponding message will appear in the flasher log window - Flashing finished then disconnect the phone from the BB and turn it on.
7. Well, do not forget to enable debugging via USB and installing applications from unknown sources after first turning on the phone.
Detailed manual in pictureshereunder the second spoiler. Do everything up to 5 points.
Post has been editedAUDIMEN - 20.02.13, 07:43
Getting root on firmware 2.3.3 without unlocking the bootloader
- for those who have already updated to 2.3.3 - roll back the flasher to the 181st. All necessary for this can be found at the link.Sony Ericsson XPERIA arc - Firmware (Post # 7696958). After that, get root with GingerBreak and upgrade to FOTA (by air). After the update, the root and installed applications will remain;
- for those who are still on the routine 181st - just upgrade to FOTA. If there are problems during the update -consider my experience.
Post has been editedSmartecs - 02.11.11, 08:16
- for those who have already updated to 2.3.3 - roll back the flasher to the 181st. All necessary for this can be found at the link.Sony Ericsson XPERIA arc - Firmware (Post # 7696958). After that, get root with GingerBreak and upgrade to FOTA (by air). After the update, the root and installed applications will remain;
- for those who are still on the routine 181st - just upgrade to FOTA. If there are problems during the update -consider my experience.
Post has been editedSmartecs - 02.11.11, 08:16
Reason for editing: + from stoat
Restoration of the phone with an unlocked bootloader after the brick from the OTA-update
1. DownloadFlashTool_0.2.9.1_FOTAUnbrick.exeand unpack it on the BB.
2. Run Flashtool.exe, click on the Flash button and select the package (included in Flashtool).
3. Connect the phone to the flash mode (if properly connected, the green LED should light up; if it is lit blue, it means the phone is not connected in the correct mode).
4. When properly connected, Flashtool will detect / recognize the device and the firmware process will start automatically.
5. Make sure that the firmware process is completed, disconnect the phone from the BB and turn it on - it should boot.
6. Do not update on OTA even if you receive a notification about the availability of the update - this will again lead to a phone bricket.
Post has been editedAUDIMEN - 06.03.13, 23:10
1. DownloadFlashTool_0.2.9.1_FOTAUnbrick.exeand unpack it on the BB.
2. Run Flashtool.exe, click on the Flash button and select the package (included in Flashtool).
3. Connect the phone to the flash mode (if properly connected, the green LED should light up; if it is lit blue, it means the phone is not connected in the correct mode).
4. When properly connected, Flashtool will detect / recognize the device and the firmware process will start automatically.
5. Make sure that the firmware process is completed, disconnect the phone from the BB and turn it on - it should boot.
6. Do not update on OTA even if you receive a notification about the availability of the update - this will again lead to a phone bricket.
Post has been editedAUDIMEN - 06.03.13, 23:10
Reason for editing: Edit!
Unofficial blocking of the bootloader
And so, I can congratulate the owners with the good news, on the XDA we found a waylock bootloader. (For those who unlocked it earlier)
Instruction
1. DownloadFlashtool . Who already have, skip step.
2. DownloadXperia Relock bootloader.ftf
3. We throwXperia Relock bootloader.ftf (without unpacking in the format: .ftf) to the folder "FlashTool": c / flashtool / firmwares
4. Run "FlashTool", click on the lightning bolt icon - select "flashmode"
5. ChooseXperia Relock bootloader.ftf and in the pop-up window click on " OK ".
6. Next, we do everything as shown in the new pop-up hint window with the only difference that the "Back" button on our device is located on the left.
7. We are waiting for the end of the process of pouring the firmware into the phone, as the corresponding message will appear in the flasher logs window -Flashing finished then disconnect the phone from the BB and turn it on.
8. After the phone is turned on for the first time, we enable USB debugging and installation of applications from unknown sources.
2. DownloadXperia Relock bootloader.ftf
3. We throwXperia Relock bootloader.ftf (without unpacking in the format: .ftf) to the folder "FlashTool": c / flashtool / firmwares
4. Run "FlashTool", click on the lightning bolt icon - select "flashmode"
5. ChooseXperia Relock bootloader.ftf and in the pop-up window click on " OK ".
6. Next, we do everything as shown in the new pop-up hint window with the only difference that the "Back" button on our device is located on the left.
7. We are waiting for the end of the process of pouring the firmware into the phone, as the corresponding message will appear in the flasher logs window -Flashing finished then disconnect the phone from the BB and turn it on.
8. After the phone is turned on for the first time, we enable USB debugging and installation of applications from unknown sources.
Instructions based on manualsGeneralgrant
K
Added to the instructions!
Post has been editedAUDIMEN - 02.05.14, 10:03
Reason for editing: Editing links.
Get root on any firmware on a phone with an unlocked bootloader
Required files:
-recoveryARC.img:http://www.multiupload.com/MNYO8JIMRO
-RootXperia.zip:RootXperia.zip(469.44 KB)
(the files below are only needed if you do not have fastboot installed)
-fastboot files:http://www.multiupload.com/BMJ24IL6XY
-32 / 64bit drivers:http://www.multiupload.com/0XZV1LXRVA
0. Drop the fileRootXperia.zip to sd card root
1. Fill in the firmware we need into the phone (for example, using FlashTool)
2. Enter RECOVERY with the command:fastboot boot recoveryARC.img (the phone must be connected to the computer in FASTBOOT mode, i.e. the LED is blue)
(navigation through the recovery menu is done with the volume buttons (or menu and home), selected with the on / off button, back with the back button)
3. In RECOVERY, select the itemInstall zip from sdcard . Then once click on toggle scripts assets : the screen will display ENABLED
4. Clickchoose zip from sdcard . We select archive from the list RootXperia.zip , which previously put on the map. Choose it and click YES - Install RootXperia.zip . Then the process of installing the root will go:
5. After installation, selectReboot system now . The phone should reboot and become rooted.
Post has been editedtRippinthehead - 07.07.11, 09:51
Required files:
-recoveryARC.img:http://www.multiupload.com/MNYO8JIMRO
-RootXperia.zip:
RootXperia.zip(469.44 KB)(the files below are only needed if you do not have fastboot installed)
-fastboot files:http://www.multiupload.com/BMJ24IL6XY
-32 / 64bit drivers:http://www.multiupload.com/0XZV1LXRVA
0. Drop the fileRootXperia.zip to sd card root
1. Fill in the firmware we need into the phone (for example, using FlashTool)
2. Enter RECOVERY with the command:fastboot boot recoveryARC.img (the phone must be connected to the computer in FASTBOOT mode, i.e. the LED is blue)
(navigation through the recovery menu is done with the volume buttons (or menu and home), selected with the on / off button, back with the back button)
3. In RECOVERY, select the itemInstall zip from sdcard . Then once click on toggle scripts assets : the screen will display ENABLED
4. Clickchoose zip from sdcard . We select archive from the list RootXperia.zip , which previously put on the map. Choose it and click YES - Install RootXperia.zip . Then the process of installing the root will go:
- Installing: /sdcard/RootXperia.zip
Finding update package ...
I: Update location: /sdcard/RootXperia.zip
Opening update package ...
Installing update ...
Superuser 2.3.4about to run program [/ sbin / busybox] with 3 args
Freexperia
script result was [1.000000]
minzip: Extracted file "/system/app/Superuser.apk"
minzip: Extracted file "/ system / bin / su"
Mounting SYSTEM ...
Deleting old versions ...
Copy files to SYSTEM ...
Setting permissions ...
Creating Symlink ...
Unmounting SYSTEM ...
Finished!
Install from sdcard complete.
Finding update package ...
I: Update location: /sdcard/RootXperia.zip
Opening update package ...
Installing update ...
Superuser 2.3.4about to run program [/ sbin / busybox] with 3 args
Freexperia
script result was [1.000000]
minzip: Extracted file "/system/app/Superuser.apk"
minzip: Extracted file "/ system / bin / su"
Mounting SYSTEM ...
Deleting old versions ...
Copy files to SYSTEM ...
Setting permissions ...
Creating Symlink ...
Unmounting SYSTEM ...
Finished!
Install from sdcard complete.
5. After installation, selectReboot system now . The phone should reboot and become rooted.
Post has been editedtRippinthehead - 07.07.11, 09:51
alchemist13 @ 07/10/2011, 22:06
By flashing, the device can be killed faster than by getting a root
alchemist13,
And by flashing it is impossible to kill.
If the sector boils down, then it is possible, and the case with an open bootloader and an update on the photo bullet is described, with the phone returned under warranty.
The truth in that case has anti-brick already appeared, but still options may be.
Post has been editedalchemist13 - 11.07.11, 15:32
The truth in that case has anti-brick already appeared, but still options may be.
Post has been editedalchemist13 - 11.07.11, 15:32
alchemist13 @ 07/11/2011, 20:19
This is not a specific term for the phone, this is the term for any bootable media, be it a floppy / disk / flash drive.
alchemist13,
I was not talking about the phone, but about the OS, because this is the Android glossary. What is the bootsector in relation to floppy disks, disks, etc., I know very well. But what does this have to do with the firmware of the phone?
alchemist13 @ 07/11/2011, 20:19
Since the recording goes to the USB flash drive, this area is correspondingly present ...
What record goes to the flash drive when flashing the phone and how can it kill the device ???
The body does not boot from the flash drive, boot.img is responsible for loading it. It was his damage, until recently, could damage the device.
Let me remind you, we are discussing the possible "murder" of the apparatus -Sony Ericsson XPERIA arc - Firmware (Post # 8217069).
I dwell on this point in detail in order to bring final clarity to current and future readers of the thread.
Post has been editedGeneralgrant - 11.07.11, 19:49
Based on posts from the forum I decided to write basic methods for treating problems with Wi-Fi.
Post has been editedAUDIMEN - 09.01.13, 22:01
1 If you have 181 firmware, then it is desirable (but not necessary) to flash on 145-146. Most bugs are treated.
2 90% of the problem of disabling Wi-Fi point is to blame.
3 Make a reset or reflash point and re-configure.
4 There is an opinion that arc does not see above port 12, although there is the opposite:
5 Need to know:
Who else has a suggestion, please add and the moderators put in the topic header, I think it will be useful because The question quite often rises.
Supplement fromtretiakov :
I support the FAQ on wi-fay. A couple of comments / additions:
1. The problem is treated by reloading the point in my particular case. That is, if you used to connect normally, but you can't, it makes sense to just reload the point.
If it is impossible to connect at all or the connection is constantly broken, then I doubt that the reset will help.
2. In case of problems, first of all it is necessary to turn on encryption:
a) there is an opinion that Android plohod is friendly with WP2 / AES, so if the point allows it, switch to WPA2 / TKIP.
if there is such an opportunity - generally make an open point or restrict access to it by other methods (for example, by MAC address); You can also switch to WEP encryption - but remember that both the MAC address and WEP encryption are less secure than WPA2.
3. In 50% of cases, flashing the router with the latest software version fixes the problem. In the rest, it is recommended to pay attention to the custom firmware, if you have such for your router - it is especially important for D-link, since their native software often suffers with troubles (at least it was before).
In particular, you can try post-milling, whether your router is supported by dd-wrt firmware (www.dd-wrt.com) - this is the most common and convenient universal request.
2 90% of the problem of disabling Wi-Fi point is to blame.
Tretiakov @ 07/21/2011, 11:28
The problem is treated by an ordinary reload of the point (DOTS, NOT ARCH)
3 Make a reset or reflash point and re-configure.
4 There is an opinion that arc does not see above port 12, although there is the opposite:
Tretiakov @ 07/21/2011, 11:28
Channel 12 arch pulls 100% - at least .146 is quietly connected.
5 Need to know:
Tretiakov @ 07/21/2011, 11:28
That not only the arc is capricious to the points, but the android in general, since many bodies have troubles with Wi-Fi.
Who else has a suggestion, please add and the moderators put in the topic header, I think it will be useful because The question quite often rises.
Supplement fromtretiakov :
I support the FAQ on wi-fay. A couple of comments / additions:
1. The problem is treated by reloading the point in my particular case. That is, if you used to connect normally, but you can't, it makes sense to just reload the point.
If it is impossible to connect at all or the connection is constantly broken, then I doubt that the reset will help.
2. In case of problems, first of all it is necessary to turn on encryption:
a) there is an opinion that Android plohod is friendly with WP2 / AES, so if the point allows it, switch to WPA2 / TKIP.
if there is such an opportunity - generally make an open point or restrict access to it by other methods (for example, by MAC address); You can also switch to WEP encryption - but remember that both the MAC address and WEP encryption are less secure than WPA2.
3. In 50% of cases, flashing the router with the latest software version fixes the problem. In the rest, it is recommended to pay attention to the custom firmware, if you have such for your router - it is especially important for D-link, since their native software often suffers with troubles (at least it was before).
In particular, you can try post-milling, whether your router is supported by dd-wrt firmware (www.dd-wrt.com) - this is the most common and convenient universal request.
Post has been editedAUDIMEN - 09.01.13, 22:01
Reason for editing: Spoiler!
How can I test custom kernels / firmwares and then go back to stock SE 2.3?
Post has been editedAUDIMEN - 09.01.13, 21:37
Sources:
Do not judge strictly) this is a technical translation = * with my additions and notes!
WARNING: ETO TRANSFER! I DIDN'T TEST IT! I submit information in the form of! AS-IS! (!AS IT IS!).
If you have a claim to me here:http://lleo.aha.ru/na/ua(for Ukraine);http://natribu.org(For Russia)
(I advise you to read it right away, I will send this to everyone personally if complaints start to me personally, because I am a translator, not a tester)
[-> Glossary of terms<--]
[-> CAUTION<--]
[-> BEFORE BEGINNING]
1. [Flashing custom NUCLEAR and ROM]
2. [Return to FW]
3. [In case of problems]
4. [Results]
5. [ADDITION]
Do not judge strictly) this is a technical translation = * with my additions and notes!
WARNING: ETO TRANSFER! I DIDN'T TEST IT! I submit information in the form of! AS-IS! (!AS IT IS!).
If you have a claim to me here:http://lleo.aha.ru/na/ua(for Ukraine);http://natribu.org(For Russia)
(I advise you to read it right away, I will send this to everyone personally if complaints start to me personally, because I am a translator, not a tester)
[-> Glossary of terms<--]
Flashing (flashing) - fill.
Custom (Custom) - own made; ready, but edited by you or someone; not official.
Kernel (Kernel) - The core of the Android system.
ROM (System) - firmware.
The firmware (FirmWare, FW, Stock Firmware) is a native (factory) firmware.
FTF package (FTF, FTF package) - FW firmware file itself.
LED - LED indicator (on Arc ‘e near USB is located).
FB (FastBootMode, FastBoot, FBM) ¬– fast load mode (LED - blue)
FLASH MODE (FM) - Flash mode (LED - green)
Custom (Custom) - own made; ready, but edited by you or someone; not official.
Kernel (Kernel) - The core of the Android system.
ROM (System) - firmware.
The firmware (FirmWare, FW, Stock Firmware) is a native (factory) firmware.
FTF package (FTF, FTF package) - FW firmware file itself.
LED - LED indicator (on Arc ‘e near USB is located).
FB (FastBootMode, FastBoot, FBM) ¬– fast load mode (LED - blue)
FLASH MODE (FM) - Flash mode (LED - green)
[-> CAUTION<--]
I am not responsible for the fact that your animal is worn out because of what you did not read to the end or misunderstand / read.
MAKE SURE THE BATTERY IS ENOUGHLY CHARGED (>50%) BEFORE BEGINNING FILLING, and that your PC has a UPS.
!!! If the flashing is interrupted, then VERY SERIOUS CONSEQUENCES can occur !!!
MAKE SURE THE BATTERY IS ENOUGHLY CHARGED (>50%) BEFORE BEGINNING FILLING, and that your PC has a UPS.
!!! If the flashing is interrupted, then VERY SERIOUS CONSEQUENCES can occur !!!
[-> BEFORE BEGINNING]
Requirements:
1. Flashtool (preferably the latest version)
2. Fastboot files - Open bootloader (bootloader)
3. Firmware (FTF packages) -http://forum.xda-developers.com/showthread.php?t=1093523
4. 7zip -http://www.7-zip.org/download.html
5. Knowledge of the command line and two hands grown from the right place, although it is possible and nose)
6. [OPTIONAL] If you want to return a previously ruled firmware - a previously ruled system.img file -http://forum.xda-developers.com/showthread.php?t=1044201
7. How to use FlashTool:
8. How to use FastBoot:
1. Flashtool (preferably the latest version)
2. Fastboot files - Open bootloader (bootloader)
Instructions for unlocking Xperia animals.
ATTENTION! This will erase the entire / data folder.
1. Downloading:
-fastboot package:http://www.multiupload.com/BMJ24IL6XY
-32 / 64bit drivers:http://www.multiupload.com/0XZV1LXRVA
2. Go here:http://unlockbootloader.sonyericsson.com/instructions
3. At the bottom, click 'Continue' and enter your IMEI (on the phone dial * # 06 # to find out your IMEI), name and e-mail.
4. Now you need to get your unique bootloader opening key.
5. Unzip fastboot.rar and open the folder with the unpacked files.
6. Hold down SHIFT and right-click on the background of the folder.
7. Click 'Open command window here' / “Open command window” (on Win7, as it is written in others I xs)
8. Connect the phone in FB mode (turn off, hold down the MENU button and turn on to USB)
9. In the command line we write: fastboot.exe -i 0x0fce getvar version
10. If the return value, then the phone is connected correctly.
11. Enter: fastboot.exe -i 0x0fce oem unlock 0xKEY (where KEY is your number in step 4).
12. Must open the bootloader.
If suddenly you didn’t understand the ChaVo here (but here in English-), and below is a video:
-Instructions:http://www.theandroidsoul.com/how-to-unloc...c-play-neo-pro/
-Video:http://www.youtube.com/watch?v=LRH3pC7MhEA
ATTENTION! This will erase the entire / data folder.
1. Downloading:
-fastboot package:http://www.multiupload.com/BMJ24IL6XY
-32 / 64bit drivers:http://www.multiupload.com/0XZV1LXRVA
2. Go here:http://unlockbootloader.sonyericsson.com/instructions
3. At the bottom, click 'Continue' and enter your IMEI (on the phone dial * # 06 # to find out your IMEI), name and e-mail.
4. Now you need to get your unique bootloader opening key.
5. Unzip fastboot.rar and open the folder with the unpacked files.
6. Hold down SHIFT and right-click on the background of the folder.
7. Click 'Open command window here' / “Open command window” (on Win7, as it is written in others I xs)
8. Connect the phone in FB mode (turn off, hold down the MENU button and turn on to USB)
9. In the command line we write: fastboot.exe -i 0x0fce getvar version
10. If the return value, then the phone is connected correctly.
11. Enter: fastboot.exe -i 0x0fce oem unlock 0xKEY (where KEY is your number in step 4).
12. Must open the bootloader.
If suddenly you didn’t understand the ChaVo here (but here in English-), and below is a video:
-Instructions:http://www.theandroidsoul.com/how-to-unloc...c-play-neo-pro/
-Video:http://www.youtube.com/watch?v=LRH3pC7MhEA
3. Firmware (FTF packages) -http://forum.xda-developers.com/showthread.php?t=1093523
4. 7zip -http://www.7-zip.org/download.html
5. Knowledge of the command line and two hands grown from the right place, although it is possible and nose)
6. [OPTIONAL] If you want to return a previously ruled firmware - a previously ruled system.img file -http://forum.xda-developers.com/showthread.php?t=1044201
7. How to use FlashTool:
FlashTool Beginner's Guide (in English).
It was posted for X10, but still relevant for Arc / Neo / Play.
http://forum.xda-developers.com/showthread.php?t=928343
It was posted for X10, but still relevant for Arc / Neo / Play.
http://forum.xda-developers.com/showthread.php?t=928343
8. How to use FastBoot:
1. [Flashing custom NUCLEAR and ROM]
Flashing custom kernel (boot.img):
Flash ROM / SYSTEM (system.img) flashing:
1. This will not erase your data.
2. Custom kernel as boot.img file
3. Copy the file to the fastboot folder.
4. Turn off the phone and go to FASTBOOT MODE (LED blue) with USB connected to the PC.
5. When in FBM open the command line and go to the folder containing the FB files, then simply enter the code to fill the custom kernel:
Code:
fastboot flash boot boot.img
6. When the flashing is over you will receive a confirmation that everything is ok.
7. Now unplug the phone from the USB and you are on the custom kernel.
2. Custom kernel as boot.img file
3. Copy the file to the fastboot folder.
4. Turn off the phone and go to FASTBOOT MODE (LED blue) with USB connected to the PC.
5. When in FBM open the command line and go to the folder containing the FB files, then simply enter the code to fill the custom kernel:
Code:
fastboot flash boot boot.img
6. When the flashing is over you will receive a confirmation that everything is ok.
7. Now unplug the phone from the USB and you are on the custom kernel.
Flash ROM / SYSTEM (system.img) flashing:
1. This will not erase your data, this will only erase your / system pack.
2. Custom firmware should be in the form of a file system.img
3. Copy this file to the fastboot folder.
4. Turn off the phone and go to FB mode (LED blue) with USB connected
5. When in FBM, open the command line and go to the folder with fastboot files, then use the following code to flash custom ROM / System:
Code:
fastboot flash system system.img
6. At the end of the flashing you will receive a confirmation on your PC.
7. Now unplug the phone from USB and you are on custom ROM / System
2. Custom firmware should be in the form of a file system.img
3. Copy this file to the fastboot folder.
4. Turn off the phone and go to FB mode (LED blue) with USB connected
5. When in FBM, open the command line and go to the folder with fastboot files, then use the following code to flash custom ROM / System:
Code:
fastboot flash system system.img
6. At the end of the flashing you will receive a confirmation on your PC.
7. Now unplug the phone from USB and you are on custom ROM / System
2. [Return to FW]
Further, the general for most instructions that can be applied to any FW / ROM / Kernel
How to return to Stock Firmware (FW):
How to get back to the stock kernel (boot.img / kernel.sin):
How to return stock ROM (system.img / system.sin):
Option - 1: for non-firmware before firmware
Option 2: For the first firmware version
How to return to Stock Firmware (FW):
1. This will return ABSOLUTELY ALL FACTORY SETTINGS !!!
2. ALL YOUR DATA WILL BE ERASED !!!
3. You will have a borehole !!!
4. YOU WILL BACK TO THE STOCK SYSTEM (ROM) !!!
5. Your SD card WILL NOT BE TORN !!!
6. We need STOCK FTF package.
7. Start the phone in FLASH MODE (LED green)
8. Using FlashTool fill the Stock FTF package.
9. For details on how to use FlashTool, use the link above.
2. ALL YOUR DATA WILL BE ERASED !!!
3. You will have a borehole !!!
4. YOU WILL BACK TO THE STOCK SYSTEM (ROM) !!!
5. Your SD card WILL NOT BE TORN !!!
6. We need STOCK FTF package.
7. Start the phone in FLASH MODE (LED green)
8. Using FlashTool fill the Stock FTF package.
9. For details on how to use FlashTool, use the link above.
How to get back to the stock kernel (boot.img / kernel.sin):
1. This will not erase your data.
2. I use 7zip unpack FTF package.
3. See the mms files with a .sin resolution
4. Look for kernel.sin
5. Copy to the fastboot folder
6. Go to FASTBOOT MODE (LED blue) with USB connected
7. In the command line, go to the folder with fastboot files, enter the code to return to the stock kernel:
Code:
fastboot flash boot kernel.sin
8. We are waiting for confirmation
9. Otsoedinya and have a kernel of FW.
2. I use 7zip unpack FTF package.
3. See the mms files with a .sin resolution
4. Look for kernel.sin
5. Copy to the fastboot folder
6. Go to FASTBOOT MODE (LED blue) with USB connected
7. In the command line, go to the folder with fastboot files, enter the code to return to the stock kernel:
Code:
fastboot flash boot kernel.sin
8. We are waiting for confirmation
9. Otsoedinya and have a kernel of FW.
How to return stock ROM (system.img / system.sin):
Option - 1: for non-firmware before firmware
1. This will not erase your data, will CONCERN ALL IN SECTION / system
2. Using 7zip unpack FTF package
3. Get a lot of files with the extension .sin
4. Search for system.sin file
5. Copy to the fastboot folder
6. Now, to return to the drain of the system, turn off the phone and go to FASTBOOT MODE (LED blue) with the USB connected.
7. Open the command line, go to the fastboot folder, enter the code for the flash stock ROM / system:
Code:
fastboot flash system system.sin
8. Upon completion receive confirmation
9. Turn off the phone and we are on the stock ROM / System / firmware.
2. Using 7zip unpack FTF package
3. Get a lot of files with the extension .sin
4. Search for system.sin file
5. Copy to the fastboot folder
6. Now, to return to the drain of the system, turn off the phone and go to FASTBOOT MODE (LED blue) with the USB connected.
7. Open the command line, go to the fastboot folder, enter the code for the flash stock ROM / system:
Code:
fastboot flash system system.sin
8. Upon completion receive confirmation
9. Turn off the phone and we are on the stock ROM / System / firmware.
Option 2: For the first firmware version
1. This will not erase your data, will CONCERN ALL IN SECTION / system
2. Use the previously-ruled system.img u file downloaded from the link above.
3. Copy the file to the fastboot folder
4. To return to the stock rutted firmware, turn off the phone and go to FASTBOOT MODE (LED blue) with USB connected
5. Open the command line, go to the fastboot folder, enter:
Code:
fastboot flash system system.img
6. Receive confirmation
7. Disconnect from USB and you are on a rooted stock ROM
2. Use the previously-ruled system.img u file downloaded from the link above.
3. Copy the file to the fastboot folder
4. To return to the stock rutted firmware, turn off the phone and go to FASTBOOT MODE (LED blue) with USB connected
5. Open the command line, go to the fastboot folder, enter:
Code:
fastboot flash system system.img
6. Receive confirmation
7. Disconnect from USB and you are on a rooted stock ROM
3. [In case of problems]
Sometimes there may be problems after flashing back from the custom system.img to the stock system.img, such as "like apps & core system crashes / force closes"
If you have problems, I advise you to erase your folder (section) / data
1. This will not erase your data (applications, installations), your SD card will remain intact
2. Go to FASTBOOT MODE (LED blue) with USB connected
3. Open the command line, go to the fastboot folder, enter:
Code:
fastboot erase userdata
4. We get a confirmation.
5. Disconnect the phone and there should be no problems.
6. If you still encounter problems, fill in the Stock Firmware using FLASHTOOL.
If you have problems, I advise you to erase your folder (section) / data
1. This will not erase your data (applications, installations), your SD card will remain intact
2. Go to FASTBOOT MODE (LED blue) with USB connected
3. Open the command line, go to the fastboot folder, enter:
Code:
fastboot erase userdata
4. We get a confirmation.
5. Disconnect the phone and there should be no problems.
6. If you still encounter problems, fill in the Stock Firmware using FLASHTOOL.
4. [Results]
I hope this will give you the answers to your questions ...
In case of questions and trawling, write in his topic (link to the materials in the SOURCES)
In case of questions and trawling, write in his topic (link to the materials in the SOURCES)
5. [ADDITION]
How to get back to stock
Requirements:
How to return the stock kernel and system:
Requirements:
1. Fastboot drivers
2. unbrick (softbrick) package (brick-breaking, brick-breaking package)
3. 7zip
2. unbrick (softbrick) package (brick-breaking, brick-breaking package)
3. 7zip
How to return the stock kernel and system:
1. ETO WILL COLLECT ALL YOUR DATA !!!
2. unpack unbrick (softbrick) package.
3. Go to FASTBOOT MODE (LED blue) with USB connected
4. Go to the explorer in the folder with the unpacked package, run (double click) restoreme.cmd
5. When finished ¬– get a confirmation (or the command line will close after a certain time has passed - this is normal)
6. Your phone restartanet automatically
7. Disconnect from USB and you are on the stock core & ROM.
2. unpack unbrick (softbrick) package.
3. Go to FASTBOOT MODE (LED blue) with USB connected
4. Go to the explorer in the folder with the unpacked package, run (double click) restoreme.cmd
5. When finished ¬– get a confirmation (or the command line will close after a certain time has passed - this is normal)
6. Your phone restartanet automatically
7. Disconnect from USB and you are on the stock core & ROM.
Post has been editedAUDIMEN - 09.01.13, 21:37
Reason for editing: Spoiler!
FAQ on unlocking bootloader:
1. Go here http: //developer.sonym….com/unlockbootloader/ and push the button Continue located at the bottom of the page to start the unlock process.
2. In the window that appears, click I’m sure Next, put a tick and click Accept .
3. Enter your name, email address and the first 14 digits of your phone’s IMEI number (the last digit will not be entered to view IMEI, enter * # 06 # on your phone), click Submit .
4. The bootloader unlock code will appear, save it for future use.
5. Download and install the latest Android SDK from here. http://developer.android.com/sdk/index.html
6. Download this archive with firewood, and unpack to any place (not necessarily in the Android SDK folder)usb_driver.7z (8.19 MB)
7. Turn off the phone, press and hold the button menu (far right) and at the same time we connect the USB cable. (the diode should be blue, if not, try reconnecting again).
8. Winda will ask for the driver, point to the usb_driver folder (the one you unpacked), if it doesn’t ask, go to the device manager and select S1Boot Fastboot , if there is no such, then go to the tab * USB controllers * and there will be a SEMC Flash Device, right-click -> update driver -> search for drivers on this computer -> select a driver from the list of already installed drivers -> install from disk -> review and select the file android_winusb.inf from the downloaded usb_driver folder. From the list we choose Android Bootloader Interface and click ready.
9. Go to the folder tools (where the Android SDK is installed) where the file is located fastboot.exe (I, for example, have C: \ Program Files \ Android \ android-sdk \ tools here for someone who can be different)
if not, download and installfastboot separately! Being in the folder tools hold key Shift Click the right mouse button and select * open the command window *.
10. Enter in the command line fastboot.exe -i 0x0fce getvar version If the answer was for example 0.3, then this means that the phone is connected correctly. If gives out waiting for device , check the USB connection status. If there is an unknown device in the device manager, then check the driver installation.
11. We enter fastboot.exe -i 0x0fce oem unlock 0xKEY where KEY This is the 14 digit unlock code that we received earlier and saved. That's it, bootloader is unlocked;)
*Note:
in the mac os x operating system. In the Termenal, you do not need to write fastboot.exe, but simply fastboot
Post has been editedAUDIMEN - 27.04.16, 08:31
1. Go here http: //developer.sonym….com/unlockbootloader/ and push the button Continue located at the bottom of the page to start the unlock process.
2. In the window that appears, click I’m sure Next, put a tick and click Accept .
3. Enter your name, email address and the first 14 digits of your phone’s IMEI number (the last digit will not be entered to view IMEI, enter * # 06 # on your phone), click Submit .
4. The bootloader unlock code will appear, save it for future use.
5. Download and install the latest Android SDK from here. http://developer.android.com/sdk/index.html
6. Download this archive with firewood, and unpack to any place (not necessarily in the Android SDK folder)
usb_driver.7z (8.19 MB) 7. Turn off the phone, press and hold the button menu (far right) and at the same time we connect the USB cable. (the diode should be blue, if not, try reconnecting again).
8. Winda will ask for the driver, point to the usb_driver folder (the one you unpacked), if it doesn’t ask, go to the device manager and select S1Boot Fastboot , if there is no such, then go to the tab * USB controllers * and there will be a SEMC Flash Device, right-click -> update driver -> search for drivers on this computer -> select a driver from the list of already installed drivers -> install from disk -> review and select the file android_winusb.inf from the downloaded usb_driver folder. From the list we choose Android Bootloader Interface and click ready.
9. Go to the folder tools (where the Android SDK is installed) where the file is located fastboot.exe (I, for example, have C: \ Program Files \ Android \ android-sdk \ tools here for someone who can be different)
if not, download and installfastboot separately! Being in the folder tools hold key Shift Click the right mouse button and select * open the command window *.
10. Enter in the command line fastboot.exe -i 0x0fce getvar version If the answer was for example 0.3, then this means that the phone is connected correctly. If gives out waiting for device , check the USB connection status. If there is an unknown device in the device manager, then check the driver installation.
11. We enter fastboot.exe -i 0x0fce oem unlock 0xKEY where KEY This is the 14 digit unlock code that we received earlier and saved. That's it, bootloader is unlocked;)
*Note:
in the mac os x operating system. In the Termenal, you do not need to write fastboot.exe, but simply fastboot
Post has been editedAUDIMEN - 27.04.16, 08:31
Greetings Please tell me if I open the bootloader. Will I do Root and then close the bootloader will remain root?
Also, how do I understand if you open the bootloader (and even closing it later) the trac id will not work? Will it be updated via seus?
Also, how do I understand if you open the bootloader (and even closing it later) the trac id will not work? Will it be updated via seus?
Stas24 @ 09/04/2011, 00:34
Please tell me if I open the bootloader. Will I make Root and then close the bootloader? Will it remain root? Also, how do I understand if I open the bootloader (and even closing it later) will the trac id not work? Will it be updated via seus?
Seus will work. Ruth must stay.
DRM keys will not recover, so bye-bye track id and all that require keys.
I just don’t see any reason to start a loader
Manual for installing a custom kernel!
Requirements:
Unlocked bootloaer.
Fastboot program
Well, the core itself.
1. Download the kernel in the topic header.
2. Download"fastboot"(you should already have it, because you unlocked the bootloader).
3. Unpack "fastboot" (at any place convenient for you).
4. Drop the kernel file (boot.img) into the folder with "fastboot" (where the fastboot.exe file is located).
5. Turn off the device.
6. Turn on the device in the "fastboot" mode (we hold down the "menu" button (it is on the right) and plug the USB cable into the computer; the diode located on the right edge of the phone should glow blue).
7. Go to the folder with the "fastboot" on the computer (where fastboot.exe and boot.img are located) hold down the "shift" and right-click in an empty place in the folder.
In the opened menu, select "Open command window" (At least as in windows 7)
8. In the open command window, we will see the command line "C: \ Users \ eNrg \ Desktop \ fastboot>"(everything before" fastboot "may look different for everyone. Depends on where the" fastboot "itself is located). Now we prescribe
fastboot flash boot boot.img
9. We wait until the command window does not write ok.
10. Disconnect the device from the computer and turn it on in normal mode.
11. Congratulations, you installed the "DoomKernel" custom kernel.
12. You can view the kernel version in the menu =>settings =>About the phone, there will be a tab "kernel version".
How to overclock the processor?
I suggest the option that I used myself (maybe there are other options, but I found this one).
Requirements: Unlocked bootloader, installed custom kernel.
1. Downloading the no-frills CPU program from the market either byThislink.
2. Set up as shown below (This is the optimal frequency, but you can experiment as well, there are rumors that it was accelerated to 1.9 GHz).
 |
3. A message about the successful setting of the processor frequency is displayed.
Congratulations! You have overclocked your processor to 1.4 (or maybe not?) GHz.
You can view the data on the processor frequency using the Android Assistent program (you can download it in the market).
Note: Do not force the device for the first couple of hours. Let it adapt to the new frequency.
If where you made a mistake or missed something, please inform about it. If everything is fine, please attach to the cap.
Post has been editedAUDIMEN - 02.11.14, 18:28
Reason for editing: Corrected outdated, + from Blackvood, + from Romkozr
Tell me, pliz, as registered in SEUS Pro. Filled in the registration form, sent. The following message came to the soap:
Thank you for registering to Update Service Pro,
Please click your link to confirm your email address.
Best regards,
Sony Ericsson Customer Service.
Followed the link there is such crap: Your email address has already been verified. And all the password is no damn. I can't go to SEUS Pro.
Post has been editedGeneralgrant - 10.09.11, 16:29
Thank you for registering to Update Service Pro,
Please click your link to confirm your email address.
Best regards,
Sony Ericsson Customer Service.
Followed the link there is such crap: Your email address has already been verified. And all the password is no damn. I can't go to SEUS Pro.
Post has been editedGeneralgrant - 10.09.11, 16:29
Guerero
in three days the password will come. I have, at least it was.
Post has been editedAUDIMEN - 12.01.13, 21:55
in three days the password will come. I have, at least it was.
Post has been editedAUDIMEN - 12.01.13, 21:55
Reason for editing: Removed too much!
Driver for flashing the phone via FlashTool without installing SEUS
USBFlash_driver.zip(2.7 MB)
Post has been editedAUDIMEN - 13.01.13, 11:55
USBFlash_driver.zip(2.7 MB)K
Added to the cap!
Post has been editedAUDIMEN - 13.01.13, 11:55
If during flashing through Flashtool your device was disconnected from the cable and now does not turn on -
(blinking red LED or / and an exclamation mark appears instead of loading), do the following:
1. Remove the battery from the device.
2. Connect the device to the charging (without battery!).
3. Wait for the green LED, wait about 10 minutes.
4. Remove the device from charging and insert the battery.
5. Start the flashing process again, since you now have an “empty” phone.
A little advice fromin.team.morozoff (it may be useful to someone!)
Post has been editedAUDIMEN - 13.01.13, 23:52
(blinking red LED or / and an exclamation mark appears instead of loading), do the following:
1. Remove the battery from the device.
2. Connect the device to the charging (without battery!).
3. Wait for the green LED, wait about 10 minutes.
4. Remove the device from charging and insert the battery.
5. Start the flashing process again, since you now have an “empty” phone.
A little advice fromin.team.morozoff (it may be useful to someone!)
if after these actions nothing has helped, then we are not in any hurry to run to SC - we sew, sew and sew ...
Until the result arrives, it is possible with different firmware, I have probably fixed it with 10 times ..
Until the result arrives, it is possible with different firmware, I have probably fixed it with 10 times ..
K
Added to the cap!
Post has been editedAUDIMEN - 13.01.13, 23:52
Reason for editing: + by Sharknes
Denisjx
eNrg *,
I try to get the root in the way indicated in the header, when I write the command I get
C: \ Users \ User \ Desktop \ fastboot>fastboot boot recoveryARC.img
downloading 'boot.img' ...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Do not tell me what the problem is?
eNrg *,
I try to get the root in the way indicated in the header, when I write the command I get
C: \ Users \ User \ Desktop \ fastboot>fastboot boot recoveryARC.img
downloading 'boot.img' ...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Do not tell me what the problem is?
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement