Database Users

Stock ROMs | Custom stuff | Tweaks | Rooting - Tutorial for your 2011 Xperia phone

Tutorial includes stock firmware .ftf files for Flashtool!
Changelog:
22-08-2012 - Expanded to Xperia Arc section.
This tutorial has been created to help XDA members in order to modify their 2011 Xperia phone. This tutorial is originally made for Xperia Ray by hansip87, link to original topic forum.xda-developers.com/showthread.php?t=1426912.
Same tutorial in Xperia Mini & Mini Pro & Active section: http://forum.xda-developers.com/showthread.php?t=1568792
These tutorials can also work on other 2011 Xperia phones. Instructions will also work with ICS unless written otherwise, so read carefully!
All kinds of ideas/comments/critism are always welcome.
Everything you do is on your own responsibility. I am not responsible for any damage that you have made to your phone.
Tutorial includes:
Android Dictionary
Root the Phone(GB and ICS)
What to do after rooting(apps etc)
Installing stock firmware and downgrading
Install Busybox and CWM Recovery
Unbricking your phone(after OTA update)
Install Supercharger to optimize Memory and KAK to optimize Kernel
Edit build.prop for additional optimizations
Enable Dual Band and Burst Mode for Wifi
Unlocking bootloader
Installing custom kernel
Installing custom ROM
Relocking bootloader
Preparing for ICS
Overclock/Underclock/Undervolting guide
Downloads
Frequently Asked Questions(FAQ)
Yet to be added:
List of system apps and which can be removed - Gingerbread and ICS
Optimizing battery life
What will you need:
Stock ROM on your Xperia and USB cable
PC Companion installed on your computer (for base drivers)
FlashTool(Flashtool topic and download)
Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
Set Connectivity mode to MSC from Menu -> Sony Ericsson -> Connectivity -> USB Connection Mode
Root Explorer or any file manager that provides access to root (I personally used ES File Explorer)
1. Android Dictionary
ADB - Short for Android Debug Bridge. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
Android - Operating System for smartphones and tablets, based on Linux, built by Google, similar to Windows on PC.
AOSP - Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK - An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Baseband - System of a smartphone, that controls the cellular radio systems(GSM, 3G, HSDPA etc).
Bootloader - Controls the booting process, makes sure that you will access User Interface. These programs tell the Android device how to start up, and are critical to its functionality.
Build.prop - A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations.
BusyBox - Command line bridge, used to give commands to Android system. You will need app to send commands, it will use BusyBox to send the commands.
Brick - A phone, that you paid a lot for and now you can use it as brick, because it doesn't start up.
CWM/ClockworkMod Recovery - A specific program, that is used before booting to Android. Allows the user to make full backup of system and install custom ROMs, updates etc.
CM - Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
Dalvik Cache - The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
Deodexed - Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
Downgrade - A job, that you have to do, when you want to get from newer firmware to older firmware.
Factory Reset - This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card.
Fastboot - Command Line Tool to edit Android filesystem. Unlike flashmode, this allows flashing unsigned partition images.
FC - Short for FORCE CLOSE. See FORCE CLOSE.
Flashing - The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
Flashmode - Phone mode, where you can freely flash any firmware to your phone via WotanServer or Flashtool.
Force Close - When a program on the Android device becomes unstable, the DALVIK program will force it to terminate to prevent further system instability.
GB/Gingerbread - Android 2.3 version, codename Gingerbread, mostly used shortly as GB.
Governor - A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA - Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS/Ice Cream Sandwich - Android 4.0 version, codename Ice Cream Sandwich, mostly used shortly as ICS.
Kernel - Bridge between hardware and Android, used for hardware information exchange and control hardware parts(CPU etc).
Launcher - A program that launches programs in Android. Examples are Touchwiz (Samsung), Launcher Pro, ADW Launcher, and Go Launcher.
MD5 Checksum - A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
Nandroid Backup - A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
OTA/Over The Air - Updating your phone firmware directly from your phone via 3G or WiFi connection.
Overclocking - Setting the processor's clock speed to run faster than its default setting, i.e. 1200 MHz (1.2 GHz) vs 1000 MHz (1.0 GHz).
RAM - Random Access Memory, data storage area, where are currently in use apps and services. It is used, because it has really high data transfer rate compared to other possibilities(SDcard, hard disks etc).
ROM - Read Only Memory, data storage, where the data can only be read by system itself. It includes all data to start the Android. Many developers edit this ROM to change Android interface.
Root(ing) - Process, during which user gets access to Android system partition and files, giving the possibility to edit Android.
SEUS - Sony Ericsson Update Service, can be used in some cases to get back to newest stock firmware.
Undervolting - Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
WotanServer - A paid application, which can be used to flash any stock firmware version with kernel to your phone.
2a. Root your phone - Gingerbread – only firmware 4.0.2.A.58 or older
Currently ZergRush method by DoomLord is the simplest way to do it.
NOTE: If you have newer firmware(4.0.2.A.0.62 or 4.0.2.A.0.69), check tutorial 3 first to downgrade your firmware.
Download the attached file from here, extract it to a folder using any .zip manager, for example 7-Zip.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser app and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2b. Root your phone – ICS 4.1.A.0.562 ONLY
NOTE: Make sure you have Android 4.0.3 and 4.1.A.0.562 firmware! This might not work on Android 4.0.4!
Download the file from this post, extract it to a folder using any .zip manager, for example 7-Zip/WinRar.
Make sure all drivers are installed.
Make sure USB debugging(Menu\Settings\Developer Options\Development) and Unknown Sources(Menu\Settings\Security) is allowed in the settings.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser and Busybox and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2c. Root your phone – ICS 4.1.B.0.431 and newer
First update your phone to the newest firmware.
Use Flashtool to flash a ICS 4.0.3 stock firmware kernel to your phone.
Run the exploit created for 4.1.A.0.562 firmware, explained in previous tutorial.
Install back ONLY the newest kernel.
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
3. What to do after rooting?
Congratulations! You've rooted your Android phone. But...what now? Here is a list of what you can do:
Install Titanium Backup. It allows you to backup all system and user apps with all data that belongs to the app. Very useful when installing firmwares and wipe is required. Using this program, you can easily backup and restore lots of apps at once. Also includes some other functions, link to Play Store.
Edit your Android. In this tutorial are some modifications that can be done. Read the forum, explore different sections and look for more modifications(there are thousands of them!), that you can do. Watch out, make sure that it will work on your phone, else you might mess up something and need to reinstall the ROM.
Remove unneeded system apps to free up some space on the ROM. This [/B]topic, http://forum.xda-developers.com/showthread.php?t=1089470, includes info about APKs, that can be removed and what must stay.
4. Installing stock firmware and downgrading
In the newer firmware, the ZergRush exploit has been blocked. If you want to return to stock ROM or you want to get your phone rooted, you have to install (older) firmware to your phone, which can be done 2 ways:
Flashtool, you need to find correct files yourself.
WotanServer, you have to register a account. - Costs €1.99
Flashtool method
Download the correct firmware file for your phone at the bottom of the post.
Make sure Flashtool is installed.
Place downloaded firmware file(.ftf format) in Flashtool\firmwares(by default C:\Program Files\Flashtool) folder.
Start Flashtool.
Click the lightning button and choose Flashmode.
Firmware should appear there, if you have it in correct folder. Choose it.
Turn off your phone, connect USB cable to computer, then press Volume Down button and connect USB cable to your phone.
Flashtool should detect your phone and starts flashing. Follow the instructions.
When it says „Flashing completed“, unplug your phone and turn it on.
WotanServer method
Go to WotanServer.com, make an account and download the client.
Start the client.
It wants to find your phone. Turn off your phone, then connect USB cable to computer, press Volume Down button and connect USB cable to your phone.
WotanClient detects your phone automatically.
Click Advanced Settings and choose firmware (4.0.2.A.0.58 or older if you want to root).
For region, it isn’t a big deal, which one you choose, although picking own one is easier.
Next, enter your account details(e-mail address and password) and click Update. Make sure you have enough credit.
Click Next and it will download proper firmware files and automatically install them.
When it’s ready, unplug your phone and turn it on.
After that you can proceed with rooting your phone, which is explained in previous guide. Or just enjoy your recently installed stock ROM
5a. Installing ClockworkMod Recovery
NOTE: You must have stock and rooted phone!
NOTE: Most custom kernels already include Recovery.
What you need to do:
Go to this link: http://forum.xda-developers.com/showthread.php?t=1346190 and download SE Tweak Installer.
Connect your phone via USB cable.
Start SE Tweak Installer.
Pick CWM, which is for your phone.
Click Install and wait. When it is ready, CWM is installed.
There is one more solution to install Recovery.
Go to Android Market/Play Store.
Search for X-Parts.
Download the app to your phone and start it.
Follow the instructions to install the Recovery.
And enjoy having a recovery.
To enter the Recovery, turn off your phone, then turn it again, when Sony Ericsson logo appears, get ready. When screen gets brighter during Sony Ericsson logo, click Volume down button(I usually keep clicking it until I get into the recovery).
To move around in Recovery, use volume buttons to go up/down, Menu button to enter, Power button for back(in some cases, also back button works).
5b. Installing BusyBox
NOTE: Requires root.
NOTE: If you used zergRush method to root, BusyBox is automatically installed already and you can skip this.
Go into Play Store(Android Market) and search for BusyBox Installer.
Download it and start it.
Follow the instructions.
6. Turning the "brick" into a smartphone
If you had unlocked bootloader and did OTA(Over the Air) update, then you probably ended up with a dead phone, aka brick. Don't worry, it is not completely bricked, still can be saved!
Download UnbrickingXperia2011.zip file from this post below.
Unpack the .zip file and place the .ftf file in Flashtool\firmwares folder.
Open Flashtool.
Get your phone to flashmode, make sure it is turned off, press down Volume DOWN button and connect USB cable.
In Flashtool, click the lightning button, pick Flashmode and choose the Xperia_2011_FreeXperia_ALL.ftf file.
Let Flashtool finish.
Install stock firmware and kernel to your phone.
Remove USB cable from your phone and start your phone.
Try not to brick it again, less problems for you.
7a. Installing V6 Supercharger
Both can be used to improve the speed of your phone. Supercharger is meant to improve RAM, KAK is for kernel.
Install Script Manager.
Download Supercharger from this topic, http://forum.xda-developers.com/showthread.php?t=991276, make sure to download the "V6_Supercharger_for_Android-update8.sh.txt" file.
Place the file on root of your SDcard, that is the main folder on SDcard(where everything else is).
Open Script Manager, start the V6 Supercharger as normal. You can choose 0 as scrolling speed.
Pick the choice, that you like. I have used Agressive 1 personally(enter the number infront).
When done setup, just exit from the menu (no.17). The result file named 99Supercharger will be generated at /data/ (or in /system/etc/init.d/99Supercharger if you have init.d mod)
(If you use init.d mod, skip this) Open Script Manager, select the /data/99Supercharger.sh, and when the properties window pops up, tag it as "su" and "boot") The ScriptManager will load it at startup and as root, otherwise it will fail.
To test if the script is loaded or not, launch again the setup script(repeat step 4-5) You will find a text like "Launcher is.. xxxxxxx" if it is written as "weak", the script is not running yet. If it is "hard to kill" it is running correctly.
7b. Installing Kickass Kernelizer
This should improve your kernel, haven't tested myself yet.
Go to http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 and download the file.
Open it with Script Manager.
Follow the instructions.
Press I for Install.
(If you use init.d mod, skip this) Open ScriptManager, select the /data/98KickAssKernel.sh, when the properties window pops up, tag it as "su" and "boot") The Script Manager will load it at startup and as root, otherwise it will not work properly.
Reboot your phone.
To verify, run it again after reboot and when it offers Verify, choose it.
8. Editing build.prop to optimize your phone's system
Build.prop consists of quite a lot lines, which set up, how some phone functions work. To edit the file, you need root rights and a program to explore root(ES File Explorer, Root Explorer etc).
Making a NANDroid backup in Recovery first is a good idea, because if you make a mistake in build.prop file, and phone does not boot into Android, you can still restore it.
Start your Explorer app and go to directory \system
Open build.prop file with a text editor.
Go with your PC to this post: http://forum.xda-developers.com/showpost.php?p=16833651&postcount=1. There are also other tweaks, you can try if you want(you might need init.d script for your ROM for init.d tweaks).
Read the first part of the post, there are some build.prop tweaks, choose which ones you want.
Make modifications in your build.prop file, save it and restart your phone.
Changes should take effect, if you have made a mistake, edit the file again or restore the backup, depending on the situation.
Some more tweaks for build.prop, init.d etc:
http://forum.xda-developers.com/showthread.php?t=1289539
http://forum.xda-developers.com/showthread.php?t=1342241
9. Enabling WiFi Dual Band and Burst Mode
As the title already, this is to increase the internet speed for WiFi on your phone.
Personally, I didn't notice any difference in battery usage.
Open Root Explorer, go to \system\etc and open file named tiwlan.ini with Text Editor.
Edit these lines:
Code:
HT_Enable=0
BurstModeEnable = 0
WiFiAdhoc = 0
to
Code:
HT_Enable=1
BurstModeEnable = 1
WiFiAdhoc = 1
and
Code:
Single_Dual_Band_Solution = 0
to
Code:
Single_Dual_Band_Solution = 1
Reboot your phone.

10. Unlocking bootloader
Unlocked bootloader is needed for most custom ROMs and for ALL custom kernels. It allows the booting system to be changed.
This can be done via official way or via test point method. Official way also removes DRM keys, which cannot be restored at all.
WARNING: You will lose warranty with this!
THE OFFICIAL METHOD - You lose DRM!
Go to http://unlockbootloader.sonymobile.com.
Enter service menu, open keypad and enter *#*#7378423#*#*.
Service Info - Configuration, Bootloader Unlock Allowed: Yes/No. If it says Yes, continue. If it says No, do not continue, because it will not work.
On the website, click "Start Unlocking the bootloader".
In the text, there are instructions, what you need to do. Also there are drivers that are needed for this process. Follow the instructions.
Install the drivers, then click Continue.
Enter your IMEI, name and e-mail. Leave out the last number from the IMEI.
You get a code, leave the website open, you will need this code.
Turn off your phone, then connect USB cable to your PC, hold down Volume UP button and connect USB cable to your phone. Blue LED should light up.
You will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open command prompt, first enter this
Code:
cd C:\...\android-sdk\platform-tools
Replace C with the correct drive letter and ... with the path to the android-sdk folder. Next, enter this command
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
Replace KEY with the key that you got from the website.
Bootloader is now unlocked.
THE TEST POINT METHOD
Go to this topic http://forum.xda-developers.com/showthread.php?t=1285285.
Follow the instructions to patch bootloader.
11. Installing custom kernel
Most custom ROMs will require a custom kernel, some of these include it already(CM, MIUI etc), other you need to find yourself(Hybrom). Installation is done via fastboot. First, you need to find a custom kernel, that will work on your phone. You can find these from Development section.
Make sure your bootloader is unlocked, enter service menu(*#*#7378423#*#*), Service Info, Configuration, if it says Bootloader unlocked: Yes, then it is unlocked.
Make sure fastboot drivers are installed. These should come with Android SDK.
Download the kernel you want. You will need a .img file, which is mostly inside a .zip file.
From the downloads section, download kernel installation package and extract the folder.
Place the .img file inside the folder. If it's name isn't boot.img yet, rename it to boot.img.
Place your phone in fastboot. Turn it off, connect USB cable to your computer, hold Volume UP button and then connect USB cable to your phone. Blue LED should light UP.
Double-click on the flash.cmd file. It will start fastboot automatically and install the kernel.
When finished, disconnect the cable and turn on your phone.
12. Installing custom ROM
Requirements: Unlocked bootloader, ROM .zip file downloaded.
Nothing difficult here.
Place the downloaded .zip file to the root of your SDcard.
Install the custom kernel, explained in previous tutorial.
Enter Recovery(while booting, when screen gets brighter, press Volume Down button until phone enters Recovery).
Make factory reset, wipe cache partition and clear Dalvik Cache(under Advanced).
NB! Do NOT make format /system, because some ROMs require files from system folder and installation will not finish if files are not available. Then you have to install stock ROM again.
Choose install zip from sdcard, pick the downloaded .zip file on your SDcard.
Wait for it to finish and reboot your phone.
13. Relocking bootloader
When you return to stock and/or need warranty back, you will need to relock bootloader. First install stock ROM and kernel and then relock bootloader, else you will have problems. Depending on the unlocking method, there are 2 ways to relock.
TEST POINT METHOD
Start S1 Tool and click Restore button. Should relock the bootloader automatically.
OFFICIAL METHOD
Will not work on test point method, because bootloader was patched there ant not unlocked.
Make sure you have Flashtool installed.
From the downloads section, download Xperia_Relock_Bootloader.zip file.
Extract the package, there is a .ftf file.
Flash the .ftf file with Flashtool.
Bootloader is locked again
14. Preparing for Ice Cream Sandwich update
ICS update is already released. You might want to know, what you need to do to get the update. Make sure, that you have
a working Xperia 2011 device
with stock ROM and stock kernel installed(if you install via PC Companion or SEUS)
and locked bootloader(if you install via PC Companion or SEUS).
Root access doesn't matter(according to current information), whether you have or not. It is lost after update anyway.
PC Companion and/or Update Service installed on your computer.
Drivers working for your phone.
Official update will only be available via PC Companion and Update Service. But you can also use Flashtool to install ICS.
15. Overclock/undervolt/underclock guide
Want to give your phone a small performance boost? Or save battery?
WARNING! The following is done fully under your own responsibility! Overclocking is a dangerous process and doing it without knowledge will end in FULL BRICK! Be careful with what you do and proceed only if you fully understand the process!
You need root, unlocked bootloader and custom kernel, that allows OC/UC/UV, installed.
Install app to edit the CPU, for example SetCPU, SetXperia, NoFrills CPU Control or another one.
Open the application on your phone.
CPU Frequency is the clock, how fast your CPU works. The faster it works, the more power it uses, more heat is generated, info is faster calculated.
CPU voltage is how much power the CPU receives. It can affect, how CPU works. Manufacturers set it to high enough for CPU to work properly. You can set it lower to save battery, however you might occur problems with your phone!
Search on internet for more information about overclocking to know more about it.
Do everything carefully, as a small mistake could result in serious problems(for example, FULL BRICK due to motherboard damage). Repairing can cost more than phone itself.

XX. Downloads
Stock firmwares, ftf file is inside the zip/7z archive(except PreRooted firmwares)
4.0.2.A.0.XX type - Android 2.3 Gingerbread
4.1.A.0.562 - Android 4.0.3 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
4.1.B.0.431 and 4.1.B.0.587 - Android 4.0.4 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
Xperia Mini (ST15i)
4.0.2.A.0.42 - http://www.mediafire.com/?uboo3lrdxnoeldn
4.0.2.A.0.62 - http://www.mediafire.com/?zad88cn2n78ashv
4.1.B.0.431 - http://www.mediafire.com/?wot47vumhstlc4h
Xperia Mini Pro (SK17i)
4.0.2.A.0.42 - http://www.mediafire.com/?hevz3x5w9pqt24q
PreRooted 4.0.2.A.0.69 - http://www.mediafire.com/?desy0bkka1b44g0 - Flashable zip
4.1.B.0.431 - http://www.mediafire.com/?j0bdx06zz5skvzt
Xperia Mini Pro (SK17a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?433tco785pj1y69 - Branded Mexico Telcel firmware
4.0.2.A.0.62 - http://www.mediafire.com/?zykznaar0yjxbp5
4.1.B.0.431 - http://www.mediafire.com/?9d2wcbfqly4lkf3
Xperia Active (ST17i)
4.0.2.A.0.42 - http://www.mediafire.com/?3zm7iss0sid94wr
4.1.B.0.431 - http://www.mediafire.com/?7hsrd2wmuqgmmq1
Xperia Active (ST17a) - "a" model
4.1.B.0.431 - http://www.mediafire.com/?yvjnt0qctun9t6j
Xperia Live with Walkman (WT19i)
4.0.2.A.0.42 - http://www.mediafire.com/?5ahb85ir7ni0i06
4.0.2.A.0.58 - http://www.mediafire.com/?4deeznrbldz886u
4.0.2.A.0.62 - http://www.mediafire.com/?ervpg54922b9c0p
4.1.B.0.431 - http://www.mediafire.com/?xklhl2uk1itk0ey
Xperia Live with Walkman (WT19a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?adigb2qgvpf0o1s
4.1.B.0.431 - http://www.mediafire.com/?4t3mm7dvm01v3mh
Xperia Ray (ST18i)
4.0.2.A.0.42 - http://www.mediafire.com/?0oi9t2m0z5p8a9y
4.1.A.0.562 - http://www.mediafire.com/?1lh84f1nyzoz883
4.1.B.0.431 - http://www.mediafire.com/?2j7i7rruqxnui3q
Xperia Arc (LT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?8aa5x52vc9dc25l
4.0.2.A.0.62 - http://www.mediafire.com/?0ann64yqnl4ei62
4.1.B.0.431 - http://www.mediafire.com/?pzr6phfd19xgbva
Xperia Arc S (LT18i)
4.0.2.A.0.42 - http://www.mediafire.com/?9mz2rhdouu6ggtk
4.0.2.A.0.62 - http://www.mediafire.com/?gn6y626km6nryi7
4.1.A.0.562 - http://www.mediafire.com/?9at03bbhdf72h3h
4.1.B.0.431 - http://www.mediafire.com/?20z5t5tg3dgbugz
Xperia Neo (MT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?4qy6vd4ndbfy8wy
4.0.2.A.0.62 - http://www.mediafire.com/?4apn8hchshmqq07
4.1.B.0.431 - http://www.mediafire.com/?6i2ihiint7tfl79
Xperia Neo V (MT11i)
4.0.2.A.0.42 - http://www.mediafire.com/?8bwwe8m6c49vs4t
4.0.2.A.0.62 - http://www.mediafire.com/?elicesjb6aerb7i
4.1.A.0.562 - http://www.mediafire.com/?aao25nnf30rcs50
4.1.B.0.431 - http://www.mediafire.com/?84d4w462qdfk44a
Xperia Play (R800i)
4.0.2.A.0.42 - http://www.mediafire.com/?cne2yvrtcu3ccvn
Xperia Pro(MK16i)
4.1.B.0.431 - http://www.mediafire.com/?8jdu5dkhlm4psoc
Kernel Installation Package for Xperia phones - http://www.mediafire.com/?c0u0kf0ud5jvkhk
Unbricking Xperia 2011 Package - http://www.mediafire.com/?s166qsg8qaaxc43
Relocking Xperia Bootloader Package - http://www.mediafire.com/?1an09qoq5yq4b5y
XX. Frequently Asked Questions
Q. I just installed custom ROM, but phone is frozen at the logo!
A. Did you install custom kernel, which is confirmed to be working with that ROM? If you did everything correctly, it might take a while, because at first boot new caches are created.
Q. Flashtool won't install stock firmware, gives this-and-this error.
A. Make sure phone is in flashmode(turn off, hold down Volume DOWN, connect USB cable). If yes, make sure, that correct drivers are installed. If yes, post here with FULL log, and I will take a look.
CREDITS
http://forum.xda-developers.com/showthread.php?t=1093062 - Android dictionary
http://forum.xda-developers.com/showthread.php?p=18805532 – zergRush rooting method by DooMLoRD
http://forum.xda-developers.com/showthread.php?t=1346190 - SE Tweak Installer by quangnhut123
http://forum.xda-developers.com/showthread.php?t=1426912 - Original tutorial by hansip87
FreeXperia Team for the unbricking file
http://forum.xda-developers.com/showthread.php?t=991276 - V6 Supercharger
http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 - Kickass Kernelizer by zeppelinrox
http://forum.xda-developers.com/showthread.php?t=1477440 - Stock firmware list for 2011 Xperia phones by benji.berg
http://forum.xda-developers.com/showthread.php?p=24882250 - DooMLoRD ICS Rooting method
http://www.xperiablog.net/2012/04/16/root-for-android-4-0-ics-xperia-update-now-available-guide/ - Original Xperia ICS rooting guide
http://forum.xda-developers.com/showthread.php?p=26914104#post26914104 - Android 4.0.4 rooting guide by puppet13th
All users, who gave me ideas for this topic.
All users, who have shared their stock firmwares.
Everyone else, who I may have forgotten.

Still needs to be edited in order to fit it for Arc/Arc S/Pro.
If you notice a bug or have an idea, let me know.
Also, critism is welcome.

[GUIDE]XT1068 stock | root | backup partitions | system & apps mods

Only valid for Moto G 2014!
Hello, forum mates. I have spent few days with this great device, I gave it meanwhile to my sister as present.
ATM, there are barely any custom ROMs, so I will list here few good things to do right after unlocking its bootloader and obtaining root access :angel:
So here you can read my little checklist and do whatever you prefer:
DISCLAIMER:
Code:
[I]your warranty is now void. All you do
with your phone is on your own risk!
Partitions info is valid for XT1068
international GSM dual-SIM only! Workflow
is tested only on KitKat factory image![/I]
Click to expand...
Click to collapse
Unlocking Bootloader: Motorola's website
Removing startup screen with warning of unlocked bootloader: flash attached zip in custom recovery
(I can confirm that the attached zip works, it will restore the white original Motorola splash screen)
1. Boot custom recovery without flashing it:
Copy and paste custom recovery (file format: img) into your SDK/platform-tools folder, I recommend here TWRP_2.8.0.1_Titan_v2 that I have successfully tested myself. Until this point the latest Motorola USB driver must be installed on your Windows PC, USB debugging (under "developer options") on your phone must be enabled. However, I generally recommend using Linux instead of Windows. You can check in my short guide for Ubuntu users how to install fastboot and ADB in Ubuntu. I have no clue about Mac iOS, sorry.
Here we go:
Navigate in CMD line into the directory where your adb.exe is saved. Example on my PC, it is in the folder "AndroidSDK", and there in the folder "platform-tools". So my commands would be:
Typing on keyboard Win+R
Enter cmd
the command line appears after that
Code:
cd c:\androidsdk\sdk\platform-tools
Now I'm in my desired folder. The next command is checking the USB driver / ADB connection:
Connect the phone to with your PC via USB cable and enter in cmd:
Code:
adb devices
Correct response:
HTML:
xxx(serial No)xxx device
If you don't see serial No of your Moto G, check if USB debugging is enabled. If serial No is there but "offline" instead of "device" appears, you will only have to confirm the promt on your phone's screen to allow USB debugging. If nothing appears, try to update your USB driver (don't go any further without working ADB connection!)
Now we will boot into bootloader mode and check there if fastboot connection is also working:
Code:
fastboot devices
Correct response:
HTML:
xxx(serial No)xxx fastboot
If the response looks like that, we can now boot into the custom recovery without flashing it onto device. The recovery.img will be booted directly from "platform-tools" folder, while stock recovery still remains installed on the phone. My recovery.img file's name is for example "TWRP-Titan", so after I've previously saved it in my "platform-tools" I will now enter in cmd:
Code:
fastboot boot TWRP-Titan.img
The phone will boot into the beautiful touch-recovery TWRP. Blue screen is there? Yesssss!! :good:
Now we can start with backups of our still 100% stock firmware in the next chapture.
Click to expand...
Click to collapse
2. Backup your stock firmware:
While still in the TWRP, simply create backup of all your partitions. It is strongly recommended to save backup on the external SD card, as many modifications or next unlocking of the bootloader (if relocked) will every time blow all your data from the internal memory.
Now still in TWRP, install SuperSU.zip
Reboot into the system
Now we will backup stock recovery, that we can later flash at any point back:
Code:
adb shell (enter)
su (enter)
Look at this point on the screen of your phone, SuperSU will promt you to allow SU access for shell, You should confirm that.
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img
It will save the "recovery.img" file in your /sdcard folder on your phone's internal memory. It is strongly recommended to create the new folder on your external SD card where you can move all backup img files. To move the files, use any root file browser like for example Root Browser. When you open Root Browser for the first time, it will prompt oyu to install few utilities (busybox, unrar etc) which you should allow.
At this point, your entire stock firmware has been saved as backup.
Click to expand...
Click to collapse
3. Backup all partitions of your factory image / firmware:
Just the same way as you have previously created backup of your "recovery.img" you can
create "img" backup files of all your partitions. Check the attached screenshots and simply replace in the adb shell command the number of the mmcblk0p block No with the one you desire to backup and change "recovery" to the proper partition names, just like in the screenshots:
Click to expand...
Click to collapse
4. Restore to 100% stock firmware:
To return to 100% stock, you simply need to flash (or only boot) again TWRP 2.8.0.1, to restore your nandroid backup of your stock firmware and -if custom recovery was flashed- to flash in bootloader mode your stock recovery back. Paste your (stock) "recovery.img" file into "platform-tools" folder and execute in bootloader mode:
Code:
fastboot flash recovery recovery.img
After that simply restore your TWRP backup of stock and flash in bootloader mode your stock recovery back. To unroot permanently, open SuperSU app and choose the option "Full unroot" under "settings".
To relock the bootloader again: reboot to bootloader mode and execute in cmd:
Code:
fastboot oem lock
Your Moto G should be now again 100% stock.
Click to expand...
Click to collapse
If you benefit from this guide, show me your love and please hit "THANKS" button.
Credits also to all guys who have created linked guides (please hit there "thanks" also)

EASY MODS (Moto G 2014 stock firmware)
I am myself very big fan of SlimRoms (I was AlphaBeta SlimKat tester on few devices), so I was desperately missing the "Real Dark Slim" mode (and several other mods) on the Moto G 2014 factory image 4.4.4
I had to darken my Moto G 2014, so here I share now quite easy way how to get dark UI on many apps:
Click to expand...
Click to collapse
DARK UI APPS:
On the attached screenshots is an example of the "normal" Play Store (light UI) YouTube app vs the modified, dark UI YouTube app.
Luckily, the Team BlackOut consisting out of some great developers and contributors has darkened out whole bunch of apps. Please visit their website or please visit their thread where you can get more info and download directly the app TBO updater (ver.5.0.0 is up to date ATM, it is a lot better than the v.3 which was suffering of regular FCs on many devices).
With the TBO app you will find also boot animations, wallpapers etc and info how to install, the most important to avoid data loss and crying is: don't forget to create nandroid backup before modifying!
List of modified apps by the TBO available in dark UI (choice, uncomplete list):
Apollo music
Calendar
Chromecast
Drive
DropBox
Ebay
ES File Explorer
Facebook
Google now
Google+
Gmail
Hangouts
Instagram
Keep
MMS (AOSP)
Netflix
PayPal
PlayStore
WhatsApp
Skype
Spotify
Translate
Twitter
YouTube
etc.
Small tipps for the flawless un/installation of the system apps:
Regarding the fact that issues could occur when replacing the system apps (probably caused by smaller scripts which might remain as "corpses" after removing the apps) here is quite reliable way to go:
gain root access (flash SuperSU zip in custom recovery)
backup all apps that should be replaced with the darkened ones (recommended: Titanium Backup to create backup, or SD Maid to create *apk file)
now uninstall the respective apps (also with TB or SD Maid)
Open Play Store, install again and uninstall respective apps (that will remove reliably all rests)
Install the darkened apps (apk files or flashable zips that you have downloaded with TBO Updater)
Enjoy dark apps!
TROUBLESHOOTING: If anything goes wrong (bootloop, dark app FCs etc) delete darkened app and restore your app backup. I have never faced bootloop, but some apps simply might not work and will FC. Even if somebody would face bootloop, restoring the nandroid backup will revert all changes.
For normally installed apps (non-system apps): simply uninstall them through Play Store and install darkened ones instead. If TBO apps don't work, uninstall them and install again from the Play Store normal versions.
Click to expand...
Click to collapse
All credits here go to @djdarkknight96, @B_Boytm, @Gunthermic, @dafoxs, @train, @darkknight and our beloved SlimGapps maintainer, @dankoman :highfive:
Sorry, if I forgot to mention someone- remind me please!
(please if you use their modified apps, don't forget to find some posts of those guys here on forum and hit several times "thanks" button!)
Xposed frameworks
Add hunderds of mods, change functions of your hardware buttons, add double-tap-to-sleep, make your phone to fly etc, endless mods possibilities with Xposed frameworks (main thread)
Little guide for people who never used Xposed frameworks before:
download Xposed installer apk (v. 2.7 experimental is my recommendation for 4.3 and newer firmwares)
download also Xposed-Disabler-Recovery.zip from the main thread (if anything goes wrong)
create nandroid backup!
install Xposed installer app
open the app and Install/Update framework
reboot
if anything goes wrong, you end up with bootloop or so, reboot recovery and flash Xposed-Disabler-Recovery.zip (if even that doesn't help, restore nandroid backup)
if the phone reboots fine (it should) download modules you desire to use and install them
reboot
enjoy your new, customized firmware
If you find this post useful, please hit "THANKS" and honour my time spent to share this with you. Please also hit thanks to all devs and contributors whose work brought you benefits.
Click to expand...
Click to collapse

Hope to see soon more tweaks from you

Gerriitw said:
Hope to see soon more tweaks from you
Click to expand...
Click to collapse
I will post in the second post few more ideas with smaller mods on the stock firmware like using dark UI apps, some useful little frameworks modules, debloating etc.
This thread is actually not so interesting for experienced users, it's all quite common stuff.
tetakpatalked from Nexus 7 flo

Very helpful for newbies....U have done great job...hope to see more...

Second post updated (mods of stock 4.4.4 firmware)

[Guide]How to backup DRM, unlock and root(for noobs)

Hey friends! I was looking at this thread: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307 and I decided to create my own thread about the same topic, however this thread is much more simplified and is for those people who are new to rooting Xperia smartphones.
So without further ado here are the steps
Part One: downloading prerequisites
in order to flash .ftf firmware files to downgrade your phone to lollipop for TA backup you will need.
1. Java JDK :
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
2. XperiFirm(not neccesary if you plan to stay on LP)
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
3. Flashtool
http://www.flashtool.net/downloads.php
4. Android SDK
http://developer.android.com/sdk/index.html#downloads
5. iovyroot(not necessary if you do not want to backup DRM)
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
other prerequisites:
Patience
Mountain Dew or Starbucks
A small bit of knowledge on command line interfaces
Part Two: Downloading firmware
1. Open up XperiFirm
2. Select your device from the list
3. Select your model number(can be checked in Settings > about phone > Model Number
4. Pick your country and carrier(does'nt really matter, best firmware to use is UK customised and Singapore customised)
5. Click the latest release in 'available releases'
6. A dialogue should pop up, tick 'automatic unpack'
7. Wait for download to complete
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
Part Three: Downgrading firmware
Download the firmware here: http://www.xperiablog.net/forum/resources/xperia-z5_e6653_32-0-a-6-152_central-europe-5_generic.477/
1. Place the file in c: Users/*account name*/.flashtool/firmwares
Open up Flashtool
2. Press the lightning bolt icon
3. Choose Flashmode and click ok
4. choose the firmware you downloaded(Do not choose the one you created)
5. Tick "user data" in the box at the top right hand corner
6. Press flash and wait
Part Four: DRM backup and unlock
1.Extract iovyroot
2. make sure USB debugging and unknown sources are enabled
3. Open up backupdrm.bat and wait
4. make sure there are no errors before proceeding(this usually takes a couple of tries)
5. IMPORTANT keep a safe online backup of your DRM keys.
6. Open up flashtool
7. click on BLU
8. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
9. Select your device and follow the instructions
9. after getting the unlock key, paste it inside the BLU dialogue in flashtool
10. wait, then profit!
11. now flash the .FTF that you created
12. boot your device into fastboot(plug in power cable and press vol down when your phone is switched off)
13. Download androplus kernel v23 and above from here: https://kernel.andro.plus/
14. Extract boot.img and put it in the android SDK inside of 'platform-tools'
15. Press shift+right click inside of the same folder
be sure to install xperia z5 fastboot drivers)
16. click 'open command window here'
17. run fastboot devices and make sure it detects your device
18. run this command here : fastboot flash boot boot.img
19. Reboot and DONE

Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.

gamer649 said:
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
Click to expand...
Click to collapse
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata

_LLJY said:
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
Click to expand...
Click to collapse
Every other Sony phone I've owned (M, Z1 compact, Z2) refused to boot after a downgrade. The main thing to remember when downgrading is to take a backup before doing so to prevent data loss, I've experienced it myself firsthand so I know how stressful it can be.

In the TA backup part you should add a step to make sure the script actually worked and didn't stop with an error, before proceeding on to unlocking BL. I had to reboot my phone & run the script several times before successfully pulling it off.

Hello!
I'm new to the Sony family as you can see in my signature and I wouldn't call myself n00b, but the whole procedure with the extra partitions is so confusing! Thank you for trying to break it down!
the usual 3 step way (1 unlock bootloader, 2 flash recovery, 3 flash SuperSU) is still present but there are some other steps before them.
As i can understand, all the hassle is just for the backup of the TA partition.
I think that we must start with your step 3, just to avoid confusion such as the step 3.4. Please post a direct link to the firmware you suggest, I can't download it because it requires me to register there too.
Also, you should break the part 4 at the step 11. If I'm not mistaken, the order should be 1, 3, 4 (1-10), 2 , 2.5, 4 (11-19).

In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk

DeathStroke said:
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Latest andro kernel have drm keys intergrated bro

working for e6633 dual ?

I had a doubt! On Part Three, can I use the given E6653 ftf for my E6683? Or I should download the .152 ftf for my exact device model i.e. E6683?
Help me bro @_LLJY

good guide
easy follow
had overheat problem i need help...!
any one please ?
updated from support ( device no pc)
after update full overheat on camera use

Can you guys please help me?
My friend got a 5803, I backed up his DRM keys and unlocked the bootloader but can't root it.
If someone could be so kind to help us it'll be great, I did it to my 6653 but for some reason I can't root this one.
Sent from my E6653 using XDA-Developers mobile app

i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?

feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
Unpack firmware Ftf file with flashtool and see is there file called FWINFO.Delete this file and pack Ftf using Ftool and you will not have peoblems with flash.
Sent from my Sony Xperia Z5

Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?

feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
I did two things to try to fix this:
1: Use the previous version of flashtool (0.9.18.6) instead of the current one
2: Use the Software Repair function of Sony's Xperia Companion application
I don't know which of these helped (it might have been neither, actually) but in the end I was able to flash Lollipop 5.1.1 onto my Z5 and use iovyroot to back up the TA partition.

Hi, this is kind of off-topic but this is the best thread for this question I could find.
I was in a hurry to get rid of the bloated, horrible stock rom, and I did not back up my DRM keys. I did patch my current kernel with the DRM fix from another thread here at XDA. Now my question is:
What kind of functionality did I lose from this, except not being able to restore to stock and relocking bootloader?

klemen241 said:
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
Click to expand...
Click to collapse
Hello, look at this video:
h**ps:.youtube.com/watch?v=dTlosea6SJE
But at first, i installed at my Z5 the latest Kernal v36 and then i installed the TWRP 2.8.7.0, but i think you can install the newest TWRP too.
At last you install the SuperSu with TWRP, than you have full root!

Creating FTF not possible
hej,
i have a problem creating the FTF as described in Part 2.5:
-i downloaded the latest version via xperifirm (E6653_Customized DE_1298-3675_32.2.A.0.253_R3C)
-i deleted the fwinfo.xml & all .TA files from the folder
-flashtool is hanging here now:
-05/016/2016 09:16:25 - INFO - Streaming from file : C:\Users\hek\Desktop\Sony Xperia Z5\E6653_Customized DE_1298-3675_32.2.A.0.253_R3C\boot\boot_delivery.xml
05/016/2016 09:16:25 - INFO - Adding rpm_S1_Boot_MSM8994_LA1_2_2_40_AID_1_KITAKAMI-TEST-HWID009400E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
05/016/2016 09:16:25 - INFO - Adding Sumire_S1BootConfig_MiscTA.ta to the bundle
-tried it with singapore customized and german customized (&not deleting the .TA-files & manually unselecting all TA files in flashtool)
what could be the issue here or is there another way to get the latest version on the phone after unlocking it?
or is it safe just to install the latest version as described here without deleting the .TA-files? (http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224)
thanks for any input!
--
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing

I used iovyroot and it created taxxxxxx.img that it has 2mb. I think so I read so time ago that taxxxxx.img had 500kb... Is it my ta wrong?? Or it's normal??
Thanks!
Enviado desde mi Z1 mediante Tapatalk

[Guide] How to root Z5C - the new, less painful way (using dirtycow exploit)

Why yet another guide? Why should you follow this guide?
This is more of a future reference for myself, but might be beneficial to some other people, hence why I decided to post it.
Thanks to the "dirty cow" exploit (CVE-2016-5195), we now have a more simple way of backing up the TA partition compared to existing guides, which all relied on another exploit that involved downgrading the firmware, thus making the whole process a bit more complicated.
Unfortunately, as you can probably tell, it's still not a painless ordeal, just "less" painful. But hey, at least you have a choice.
To keep this step-by-step walkthrough guide simple and straightforward, I am focusing on just the steps and skipping the explanations.
Let's get started!
Prerequisites
Important: Your phone must be vulnerable to the "dirty cow" exploit, any firmware version with security patch level 2016-12-01 or earlier should work, such as 32.2.A.5.11. Basically, any MM or LP firmware.
Currently there is no way of backing up the TA partition on Android 7.0 Nougat firmware, you will need to downgrade to MM or earlier firmware first.
Remember to backup all your data before you downgrade, since a downgrade is akin to a factory reset. Downgrade instructions:
Follow Step 0, skip Step 1 and 2
In Step 3, download a MM or LP version firmware. For the sake of simplicity, I suggest you download the one labeled Storefront.
Follow Step 4 and 5
Done, your phone is now downgraded, skip the remaining steps. Continue with the guide as usual from Step 1
Note: If the DRM keys are irrelevant to you (TA partition already backed up/restored/lost) and would just like to root, then you can root using this guide on all firmware versions including Android 7.0 Nougat without downgrading. In this case, you can skip Step 1 and Step 7. Depending on your situation, you can also skip other parts of this guide, such as Step 2 if your bootloader is already unlocked, or in Step 5 don't wipe anything (leave all boxes unchecked) to retain your apps and data for a firmware upgrade.
Computer setup with correct drivers and adb/fastboot connection ability.
Enable USB debugging on the phone:
Settings > About phone > Tap multiple times on Build number until Developer options is enabled
Settings > Developer options > USB debugging > Toggle ON
XperiFirm for downloading official Sony firmware directly from Sony's servers
Flashtool for flashing firmware
Battery preferably more than 80% remaining, loss of power while flashing can brick your phone
Step 0 - Backup your phone (optional)
Move all your data to your SD card using the native tool: Settings > Storage > Transfer data to SD card
Use Sony's Backup & restore app to make a backup: Settings > Backup & reset > Xperia Backup & restore > More > Manual backup > Select SD card > Select content to backup
Personally, I choose everything except apps, they can be re-downloaded from the Play Store at any time, plus they take a long time to backup and restore not to mention eats up free space
Step 1 - Backup the TA partition
Download this wonderful TA Backup tool, unzip to desired location
With the phone powered on, connect the USB cable to the computer, then plug the micro USB end to the phone
Open command prompt (Start > Run > cmd), navigate to the directory where you unzipped the TA Backup tool
Run the following command:
Code:
backupTA
The tool will run and if successful, you should see at the bottom the words "TA Successfully pulled to TA_E5823.img".
TA_E5823.img is the TA partition image file, actual filename will be longer and differ for everyone so to keep it simple we'll just refer to it as TA_E5823.img in this guide.
Please check that the file is 2,097,152 bytes. If not or file is missing, then the backup has failed.
If it fails, just run the tool again a few times, or try rebooting your phone then rerun the tool. If you just can't get it to work, seek help from the tool thread.
Step 2 - Unlock the boot loader
Visit Sony's website and follow the instructions carefully
Important: Pay attention to the warnings. No, really, unlocking the boot loader will wipe your DRM keys (hence the need to back them up in Step 1) and trigger a factory reset, erasing everything on your phone.
After you've successfully unlocked the boot loader, unplug your phone and leave it powered off
Step 3 - Download stock firmware
Run XperiFirm, locate the correct Xperia Z5 Compact version of your phone (E5803/E5823) and download the firmware of your choice.
General recommendation is to download the "Customized" version that's available for your country.
Step 4 - Create a FTF file from the firmware
Open Flashtool
Tools > Bundle > Create
Select source file > Locate the folder where you saved the firmware from XperiFirm in step 3 > You should see your device name appear automatically in Device and the folder list below populated
Branding > The same as Operator in XperiFirm, e.g. Customized AU
Version > The version you downloaded, e.g. 32.2.A.5.11
Hint: Both Branding and Version information is in the folder name
In folder list, select the first item, hold SHIFT and select the last item so that all items are highlighted, then click the "- >" button > The folder list should now be empty, and the Firmware content field populated
Click Create, if successful you will see "Bundle creation finished"
Note: The FTF file is saved to %userprofile%\.flashTool\firmwares by default
Step 5 - Flash the FTF file
Click the lightning symbol in Flashtool > Flashmode
Source folder should be pre-selected to the default location mentioned above and "Sony Xperia Z5 Compact" listed in Firmwares
Expand all the arrows and select the version number
Under Wipe/Sin check all options (APPS_LOG, DIAG, SSD, USERDATA), leave all other options unchecked
Click Flash, wait for an instruction prompt to pop up
Plug the USB cable to your computer if it isn't already plugged
Turn off your phone if it isn't powered off, hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Flashtool will begin flashing the firmware automatically. It can take a long time, 10~15 minutes is normal, wait until completed
Unplug your phone and do not power it on yet
Step 6 - Patch the kernel
Download this awesome rootkernel tool, unzip to desired location.
Extract the kernel image file kernel.sin from the FTF file using any file compression program such as 7zip, WinZip, WinRAR, etc.
Open Flashtool > Tools > Sin Editor > Sin file > Locate the kernel you just extracted > Click Extract data. You should now have a file named kernel.elf in the same folder
Copy kernel.elf to the rootkernel folder
Download the latest stable version of the SuperSU ZIP file and copy the entire ZIP file to the rootkernel folder. Do NOT unzip it!
Rename the SuperSU ZIP file name so that it starts with SuperSU (case sensitive) instead of UPDATE-SuperSU, e.g. SuperSU-v2.79-20161211114519.zip
Note: if you're patching Nougat firmware, you may want to use phh's superuser instead of SuperSU due to potential battery drain. See rootkernel thread for more info. If you use phh's superuser, you will need to install the apk from the Play store after Step 8.
(optional) Download the latest Xposed framework ZIP file and copy it to the rootkernel folder. Do NOT unzip it!
Note: this only works with rootkernel v5.0 or later, if you're using an earlier version of the rootkernel tool, skip this and skip Step 9
At time of this edit (2017/2/22), Xposed does not support Android 7.0 (Nougat), so if you're trying to patch a Nougat kernel, do not include xposed. You can check the official Xposed thread for latest announcements to see if it's supported
Open command prompt and navigate to the rootkernel directory
Enter the following command:
Code:
rootkernel kernel.elf boot.img
You will be prompted to make a series of choices, including whether you want to install SuperSU and Xposed. Type Y for all of them.
If you didn't see the prompt for SuperSU (required) or Xposed (optional), check the filename of the ZIP files. Remember they're case sensitive.
You should now have a boot.img file in the rootkernel folder, that is your rooted kernel
Step 7 - Flash the DRM keys (one-time procedure)
tobias.waldvogel (rootkernel developer) said:
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade.
Click to expand...
Click to collapse
Copy the TA backup file TA_E5823.img from Step 1 to the rootkernel folder, then enter the following command in command prompt:
Code:
flash_dk TA_E5823.img DK.ftf
This will create a DK.ftf file in the rootkernel folder
Open Flashtool > Click the lightning symbol > Flashmode > Source folder > Locate the rootkernel folder
"Sony Xperia Z5 Compact" should appear under Firmwares, expand the arrows until you see DeviceKey and 1.0. Select 1.0, click Flash and wait for an instruction prompt to pop up
Hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Wait until operation is completed, then unplug the cable from your phone. Do not power on yet
Step 8 - Flash the kernel
Hold the VOLUME UP button and plug in the micro USB cable. Wait until the LED indicator turns blue, then release the VOL UP button.
Enter the following command in command prompt to flash the rooted kernel:
Code:
fastboot flash boot boot.img
After completion, congratulations, you've successfully rooted your phone!
Now you can turn on your phone, the first boot will take a very long time to initialize, don't worry.
If you see the boot animation for more than 30 minutes, then it's time to worry. First try again from Step 6, and if you still can't complete boot, go up a step starting from Step 5. If that still fails, start over from Step 3.
Step 9 - Finish installation of Xposed (optional)
In Step 6, if you chose to include the Xposed ZIP file, which means you want to install Xposed, then there's one more step to complete the installation.
Download the unofficial Material Design Xposed Installer.
Currently, this is the only Xposed Installer that works with the systemless Xposed integration method used by the rootkernel tool. Using the official Xposed Installer will not work.
Go to Settings > Security > Unknown sources > Toggle ON
Copy the Xposed Installer apk to your phone and install it.
Done!
Personal list of xposed modules to install for self reference. This is in no way a recommendation list, your preferences will vary.
Amplify
Android Phone Vibrator
App Locale
BootManager
Disable Low Battery Notifications
DynamicAlarmIcon 2
HideBatteryLowAlert
Keep Trash (broken at the moment)
Lockscreen Album Art Remover
MinMinGuard
NeoPowerMenu
NoHeadsetNotification
Ringer and Notification Volume Unlink
RootCloak
Use USB for Marshmallow V 1.2
XperiaFMwoHS
Xposed Torch: Physical keys
Youtube AdAway
Bonus - How to unroot/fully restore DRM/return to 100% factory state

Thank you for taking the time to write this guide!

best guide for root, thanks!

Fantastic guide, Thank you very much for that!
I had trouble getting the latest version of flashtool (09231) to work (mac and PC). It froze when I was trying to create the new bundle.
After downloading the older version (09186) it worked without problems.
However, currently I am stuck at step 6, running cmd 'rootkernel kernel.elf boot.img':
I get the message:
Code:
Rootkernel V5.11
- Unpacking kernel
error: Android boot magic not found
Unknown boot image format
Aborting
UPDATE:
I found the reason for the img file creation failure.
I was not patient enough in copying the kernel.elf file over. While the flashtool says file with size X created it was still compiling and only a minute later or so finished writing the file. In other words, I copied over the 'unfinished' kernel.elf and that's what caused the issue.
Trying to boot now
Thanks again for this nice guide!
Cheers,
Malcolm

Hey Malcolm, did you manage to complete the process successfully?

good news
thanks for your help. very good tutorial, realy made easy to understand
successfully rooted my nougat z5c with this,
you the best thanks

brokich said:
Hey Malcolm, did you manage to complete the process successfully?
Click to expand...
Click to collapse
Hi Brokich,
Unfortunately not (yet).
After finishing step 7 my device is stuck at the bootloader
I've tried now several times re-flashing (steps 5-7) but unfortunately no luck yet...Will try to repeat the whole procedure over the next days again.

I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..

Hello guys
On step 5 i get this error
5/031/2017 13:31:03 - INFO - Device connected in flash mode
05/031/2017 13:31:28 - INFO - Selected Bundle for Sony Xperia Z5 Compact(E5823). FW release : 1298-5497_32.2.A.5.11_R13C. Customization : Customized UK
05/031/2017 13:31:28 - INFO - Preparing files for flashing
05/033/2017 13:33:12 - INFO - Please connect your device into flashmode.
05/033/2017 13:33:13 - INFO - Opening device for R/W
05/033/2017 13:33:14 - INFO - Start Flashing
05/033/2017 13:33:14 - INFO - Processing loader.sin
05/033/2017 13:33:14 - INFO - Checking header
05/033/2017 13:33:14 - ERROR - Processing of loader.sin finished with errors.
05/033/2017 13:33:14 - INFO - Ending flash session
05/033/2017 13:33:14 - ERROR - null
05/033/2017 13:33:14 - ERROR - Error flashing. Aborted
05/033/2017 13:33:14 - INFO - Device connected in flash mode
Any idea why ?

notabene said:
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Click to expand...
Click to collapse
Did you backup your TA-partition before the bootloader status was unknown?

zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
Yes, why?
---------- Post added at 01:13 PM ---------- Previous post was at 12:49 PM ----------
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
I was able to flash FTF file. But not the kernel.

notabene said:
yes.
Click to expand...
Click to collapse
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.

zegovernator said:
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
Click to expand...
Click to collapse
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Bootloader unlock allowed : yes
Remote Lock state : UnLockd
Checked DRM all OK

notabene said:
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Click to expand...
Click to collapse
Flash a .tft from the MM version your backed up your TA image from. When flashing, ensure to tick everything under wipe except TA Misc.

Well finally was able to do all the steps, but phone wont boot. Stucked in Sony logo, led is yellow and then power off..

Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm

Need to use phone tomorrow, how can i revert to stock for a while since I cannot do it throught Xperia companion?
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
Malcolm143 said:
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Click to expand...
Click to collapse
Did you use customized firmware? I did not, i used Tmobile CZ
Now with bootloader unlocked even PC Companion doesnt work..
So the problem is after flashing custom kernel with rootkernel+DRM fix.
So after hours of trying from step 5 with different settings for kernel, I ended up with stock rom flashed via flashtool..
tried to flash back DRM keys from Dirty cow TA Backup, using this command flash_dk TA_E5823.img DK.ftf but when rebooted in service menu drm keys are still gone..
EDIT:
Seems like there is more users with same issue with Z5C and latest rootkernel
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page200

Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.

mhaha said:
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
Click to expand...
Click to collapse
Thanks, will try in the evening.

Just to know, if I'm upgrading from previous firmware version, do I have to do all steps or I can start from step 4 (flashing ftf file)?

trying to bring my brothers A500 to life in 2019

Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn

Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?

Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.

Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.

Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.