Database Users

[Xperia SP][INFO][REF] All the info you need before you begin

@MODS
request you to sticky this thread
hello friends,
let me begin by introducing myself, i am developer for Xperia devices (X10, ARC, PLAY, S, T, Z) and am the Lead Developer of Team UtterChaos, member of Team ICX and was associated with Team FreeXperia, ... i have some experience in development for Xperia devices, specifically in kernels, rooting & recoveries and i have various how-to, reference threads which are very helpful to new & advanced users alike across various device communities... i hope even this thread will be useful to everyone... if you would like to know what things i have worked on before feel free to check some of the links in my signature below...
so some of u must be new to the Sony Xperia family & even if u are not this should be useful... this thread should get u up to speed on what you need to know for this device...
i will try to cover some very basic things and try to touch upon some advanced topics...
i will be dividing this thread into various sections, and each section will point to an individual post...
following is the list of sections covered:
Basics
FlashTool
Bootloader Unlocking & Relocking
Rooting
Recovery
Flashing Custom Kernel
Flashing Custom ROMs
for those who are interested in development are free to contact me via p.m.... BUT PLEASE do not ask generic questions, post all generic queries at the forums/threads...
regards,
DooMLoRD

Basics
[ various bootmodes ]
newest Sony devices have three boot modes... these bootmodes can be reached when device is powered off...
Normal - just press power button and device starts booting
Flashmode - this mode is used to flash stock OFFICIAL firmware using flashtool, denoted by GREEN LED (this is similar to DOWNLOAD/ODIN mode of the Samsung devices)
Fastboot mode - this is a special mode, denoted by BLUE LED, used when we want to flash custom kernel, custom system images, for that we need to unlock bootloader, i will tell more details about this later...
[ various key combinations ]
this is most important part...
known key combinations so far:
while device is power OFF
Volume Up + USB cable connected to PC -> FASTBOOT MODE (BLUE LED will light up)
Volume Down + USB cable connected to PC -> FLASHMODE (GREEN LED will light up and quickly disappear)
while device is power ON
There is a special button under a small back cover
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Button Pressed and hold for 5 seconds -> resets the battery, its like removing the battery and putting it back in
Button Pressed and hold for >10 seconds -> will power off hard, device will power down [device will vibrate thrice]
[ understanding About Device ]
What it all means for u:
Kernel version:
Sony has released this device with 3.4.0 kernel. When custom kernels are released (they will surely be soon) this string will change (as can be seen from the screenshot).
Model number:
The Xperia SP has model number as C530x and has three main variants....
C5302
C5303
C5306
the difference is in the radio frequencies each variant supports
Android version: http://en.wikipedia.org/wiki/Android_(operating_system)
Sony officially launched this phone with android version 4.1.2 (aka Jelly Bean).
Baseband version: [linked to firmware version]
(Crudely) this is a software interface which communicates with radio -> gsm/wcdma (2g/3g)/LTE, basically acts as a base for the main OS to ‘talk-to’ the hardware on the phone [I know this explanation isn’t precise even partly incorrect.. if someone can help me out I will update it]
This is similar to the "radio" image of the HTC devices.
Build number: [aka firmware version]
This is dependent on which firmware u flash on ur phone and is linked to the baseband version.
Btw some devs use this field to add their own ‘signature’ to the ROM so if u are using custom ROMs this field might be varying. Though the Baseband version for a particular firmware remains same.
what is firmware?
The firmware is a package containing all the official software for a particular build. It will contain system, kernel & baseband files. Generally the firmware is supplied (on forums) in form of FTF package (a container file ending with .ftf) which can be flashed via FlashTool.
what are the ways to update/repair firmware?
SEUS (Sony Ericsson Update Service) / PCC (PC Companion) / EMMA are all official ways to update to new or repair existing firmware on your device. SEUS/PCC are available to all users (consumers), EMMA is special and is only available to select individuals. This requires you to connect device to PC and then the software will check for updates and download them over the internet.
Updates can also be sent as FOTA (Firmware over-the-air)/OTA (over-the-air) updates where in you can download and install the updates without the need to connect to PC/any software.
FlashTool is an unofficial user-created tool, but the best way to flash official firmwares. Generally the firmware is supplied in form of FTF package (a container file ending with .ftf) which can be flashed via FlashTool. Thus FlashTool is the easiest way to do offline updates, just download the FTF file, it keep on PC and flash ur device when ever you want to.

FlashTool
Flashtool is one of the MOST IMPORTANT piece of software for ur phone, it is an unofficial, but the best way to flash official firmwares on both locked and unlocked bootloader devices. Generally the firmware is supplied in form of FTF package (a container file ending with .ftf) which can be flashed via FlashTool. Thus FlashTool is the easiest way to do offline updates, just download the FTF and keep on PC and flash ur device when ever you want to. One can also flash select partitions using FlashTool, say you want to flash baseband(radio) from newer/older firmware but want to keep the main system the same u can do that using newest FlashTool! FlashTool also supports fastboot modes! so if you are not very comfortable with command line then u can use the FastBoot Toolbox inbuilt into FlashTool to fastboot the kernels!
FlashTool can be used to flash both locked and unlocked bootloaders devices.
For all flashtool informations (download links, release notes, FAQ) go to the Flashtool Homepage
Flashtool specifically for 2013 Xperia devices released!
Flashtool is on github : FlashTool GitHub repo
[FLASHTOOL GUIDE] HOW TO for n00bies (excellent guide for new users, HIGHLY RECOMMENDED!! The info for Rooting, Recovery & Bootloader UNlock in that thread is for older Xperia devices...)
i will try n get more links for FlashTool and post it here
Sony also provides an official FlashTool but it can be used only with unlocked bootloader devices

Bootloader Unlocking & Relocking
[Tutorial] Xperia SP Bootloader Unlocking/Relocking

Rooting
[ROOT][SP] How-to for rooting newest firmware 12.0.A.2.245
[ROOT] DooMLoRD Easy Rooting Toolkit

Recovery
if you are not familiar with custom Android recoveries i suggest that u read this:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
FOR UNLOCKED BOOTLOADERS:
Currently CWM Recovery is available for this device and come as a part of kernel (stock or custom kernel)
Recoveries on stock kernel:
[Recovery] CWM (UNLOCKED Bootloaders)
FOR LOCKED BOOTLOADERS:
[Recovery] CWM (LOCKED Bootloaders)
kindly post queries related to specific recovery at the corresponding thead

Flashing Custom Kernel
CUSTOM KERNELS ARE SPECIFIC TO ROMs...
you cant use stock kernel on CM ROM and you cant use CM kernel on stock ROM....
there are two ways to flash custom kernel
first download the kernel file... if it is a boot.img then use Method 1 (fastboot mode) or if its a update.zip file then use Method 2 (recovery)
Method 1 - fastboot mode
if you get kernel in boot.img format then do the following
reboot device into fastboot mode
then flash the kernel using following command:
Code:
fastboot flash boot kernel.elf
then reboot from fastboot
Code:
fastboot reboot
thats it now device should start booting that kernel
Method 2 - recovery
if you already have recovery working on your device then do the following
save the update.zip on SDCARD
reboot into recovery
flash the update.zip which contains the kernel
reboot into system
thats it now device should start booting that kernel

Flashing Custom ROMs
Most custom ROMs are provided as update.zip. Its a technical term, basically its a special signed ZIP file which can be flashed via custom recovery.
Download the ZIP file and save it on ur PC
now connect ur device and save the ROMs ZIP file on the SDCARD
disconnect the device (after copying is over)
reboot into recovery
go to install ZIP from sdcard menu and navigate to the folder where you saved the ZIP file
now select it
recovery will start flashing the ROM
after flashing is over just reboot device and you will be on the custom ROM
Tips:
some CUSTOM roms require specific kernels (like CM10) in that case FIRST flash the corresponding kernel and then follow the instuctions posted above
sometimes the ROM requires cleaning /data & /cache partitions. you can wipe these before flashing the ROM! [WARNING YOU WILL LOSE UR DATA BY DOING THIS!]

thread is now completed and ready

Very informative thank

Sim-Unlock?
I see no information about unlocking C5303. Is it possible to unlock O2 UK C5303 with any method mentioned above?

Ok.. so I rooted, unlocked bootloader and installed CWM for unlocked bootloader... but I still have my BE2 in settings!

sarkar1990 said:
Ok.. so I rooted, unlocked bootloader and installed CWM for unlocked bootloader... but I still have my BE2 in settings!
Click to expand...
Click to collapse
It will stay in the settings,but without the DRM keys it no longer works for pictures, just video. Also you may not be able to share music likes with walkman, alsoyou cannot share your location via MMS

Thank, it was usefull

Thanks!! Your post made the transition from Samsung to Xperia easy.. :good:
Not so easy compared to Physical buttons of Samsung phones..:cyclops:

[Q] 2-way Call Recording
Thanks for so detailed informations. i have xperia arc s now, and hoping switch to xperia sp.
I use doomkernel v22 GB for my xperia arc s. it work nicely on my phone and 2-way call recording is my favorite fitur.
[Q] Would it be "2-way call recording" on Xperia SP Kernel?
Thanks in advance
NB: sorry for my bad English

i've a 5303 but i cant install flashmode driver and flashtool don't see the phone..

First started rooting my phones 18 months ago when I ran out of memory on my old Xperia Mini Pro and needed to delete all the bloatware.....now after a rooted LG 4x HD, Iv'e just got the new SP and again have it rooted, running on .257
Thanks for your guide and links, worked a treat

anyone have firmware 12.0.A.2.245 generic for C5302 ? i want to back it up incase i ever needed it.
edit: without any modification.

kinda lost
sry bout to ask this here, but im trying to install doomlord's kernel v2 on my xperia sp, but looks like dev-host isn't working at all, is there other way to get that kernel? i just bought my sp yesterday and today unlocked the bootloader and made the backup TA, but since i cant download the kernel i cant install cwm :c hope u guys give me any advice, i still dont have enough posts, thats why im posting here.
PD: sry bout my english, is my 2nd lang, im from Chile. Greetings.

[INDEX][GUIDE][FAQ] All Things RAZR I

Welcome to the “All Things” Razr I Index thread. This Index thread contains basic information about the Motorola Razr I a.k.a. XT890 to get you started. It won’t contain any KERNEL and ROM Development, because of the numerous kernels and roms people can make. It would just flood this thread if it happens.
All the work that is presented in this thread belong to their rightful owners. I just sorted them and linked the threads in here.
Everything that u do to your phone it totally your own responsibility. Nobody here or elsewhere can be held account for a failure in flashing, device bricked or a rom problem if u tempered with your own device. But maybe we can help if u ask nicely.
This Index thread contains the following in this order:
A. GENERAL DISCUSSIONs
B. GENERAL (DEV) TOOLs
C. UNLOCK BOOTLOADER and ROOT
D. RECOVERYs
E. FIRMWAREs
F. MODs
G. WARNINGs, BRICKED DEVICEs SOLUTIONs/DISCUSSIONs
H. DOWNGRADE TO ICS
I. FROM STOCK TO CUSTOM ROM
J. FROM CUSTOM ROM TO STOCK (with RELOCK BOOTLOADER)
Some important notes:
When using 3rd party software to alter your device u warranty may be voided. In every country this is different. Before going ahead, read your legal rights!!!
Each thread/sections can contain “important” notes
Do your research before doing anything
Read the information the owner of the thread gives u
Highly recommended to have a look at the ‘warnings, bricked devices solutions/discussions’ threads before using RSD-Lite and fastboot commands like flashing manual firmware versions.
Last note:
If u find something missing that should definitely be in this Index thread, please share.
If u find anything wrong and u know the answer, please share.
Can someone have a look at the downgrade section. That’s the only one I don’t know for sure.
A. GENERAL DISCUSSIONs
Are recommended discussions about new firmware and features
RAZR I Help Guide (2013)
Motorola 4.4 (2014)
FM Radio (2013)
RAZRi XT890 USB OTG Capabilities
B. GENERAL (DEV) TOOLs
Contains threads with information about tools that you may need for your device
Motorola USB drivers
Motorola Device manager (driver)(Windows)
Motorola Device manager (driver)(Mac)
Motorola usb drivers for all devices. It also installs the device manager that checks for updates for your device. You can delete the program and still use the drivers. If u want the drivers alone, search the internet. No valid official link yet.
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer
In different threads are different methods to acquire those tools. If u have them ones installed right, u don’t need them twice. It isn’t bad to have them multiple times though.
Motorola mFastboot (fastboot file sized > 100mb)
Put the mFastboot executable as 'mfastboot' in the directory where adb and the normal fastboot file are stored
RSD-Lite
Motorola Tools [Specially for Noobs] (November, 2012)
RSD-Lite in this thread is outdated(5.7), use the newest 6.1.x series from here
If one version doesn’t work, try another. 1 of the 3 should work for you!
ALWAYS USE YOUR CURRENT FIRMWARE OR HIGHER! DON’T DOWNGRADE WITH RSD-LITE. Downgrading with RSD-Lite will cause a soft-brick or if really screwed up a hard-brick. See ‘warnings, bricked devices solutions/discussions’ for more information.
[How to] Change Radio Firmware (February, 2013)
Flashing the radio can do more harm than good, but can also be rewarding, be careful
[DEVS only] Unpacking RAZR i boot images (November, 2012)
C. UNLOCK BOOTLOADER and ROOT
Threads about the bootloader and getting root access.
How To Update/Unbrick/Root Razr I To Jelly Bean (With Review) (Maart, 2013)
Makes use of video’s, a tad outdated.
Unlock the Bootloader on Your RAZR i (Oktober, 2012)
If this doesn’t work, your device isn’t supported (can happen). At this moment u can only achieve root access with the method: TwerkMyMoto, if your bootloader can’t be unlocked.
[Root] TwerkMyMoto 1.0 (no unlock root)(Jellybean) (november, 2013)
Doesn’t require unlocked bootloader
RAZR i Root 2 (Jellybean 4.1.2) (January, 2013)
RAZR i Root (ICS) (December, 2012)
D. RECOVERYs
The recovery’s can behave at every device differently. So a user can have no problems with CWM and almost can’t use TWRP. But it is the same the other way around. Try them and see which one u like and works for u.
To enter Fastboot mode to get to the Recovery
After booting up fastboot mode, navigate with volume - down to the recovery and select it with volume + up
[RECOVERY] Installer for CWM 6.0.1.9 / CWM 6.0.3.6 / TWRP 2.6.3 / STOCK (February, 2014)
To enter stock recovery, press volume up and down at the same time when the Android appears.
CWMR or TWRP install easy 19-Sep-13 (September, 2013)
E. FIRMWAREs
The Unofficial Thread of Official OTA Updates (April, 2013)
Motorola Razr i XT890 Firmware (up-to-date)
F. MODs
Recommended to make a backup before applying
[MOD] Collections of mods for Omar-Avelar Rom (April, 2013)
[MOD] Changing the brightness curve in stock JellyBean (September, 2013)
[Tool] Swap Internal SDcard With External SDcard no init.d need UPDATE (December, 2012)
Enabling USB Mass Storage on the Razr I (Needs root access) (November, 2012)
G. WARNINGs, BRICKED DEVICEs SOLUTIONs/DISCUSSIONs
Downgrade problems JB -> ICS | Black screen green led | service required code currupt
Downgrading from JB to ICS with a locked bootloader is bad. According to a lot of users it will give u a bricked device. This is because RSD-Lite can also flash the motoboot (bootloader), gpt.bin (partition table) and motobp (radio?) and those 3 may never be downgraded only upgraded. Can only be resolved at a service station.
With an unlocked bootloader it is possible, but then again, don’t flash the motoboot, gpt.bin and motobp!
WARNING - Avoiding Bricked Phones + RSD Lite Tutorial (April, 2013)
Recommend to read before attempting to downgrade
RSD-Lite tutorial, not a downgrade tutorial
Unbricking JB to ICS downgraded hardbricks (Maart, 2013)
This is a unbrick method when u have the following message: Service Required Code Corrupt or black screen - green light. But be careful. This fix can help most of the problems, but not all because of the firmware differences. If it doesn't work for you, have a look at the one below. The owner and thread is still worth mentioning because of the finding of a possible fix, the many devices the owner saved and the discussion about the problem that came along.
Unbricking "Service Required Code Corrupt" (May, 2013)
A better documented unbrick method as the one above, but the same. Still won’t help everybody. But won’t harm your device more than it can and already is if u need this. Only for downgrade problems, everything other needs RSD-Lite or Jellybean versions of the files.
Other issues/discussions
Locked Bootloader, can't access Recovery
If u have a locked bootloader and u can’t access the recovery anymore and even RSD-Lite (latest version) with stock firmware (JB) won't work, there is no possible way to resurrect it, yet. Most of the time it means that you have a bad sector in your EMMC (flash memory) and with a locked bootloader it can’t be erased/written to.
PDS Partition Fix (July, 2014)
In TWRP recovery u can erase PDS. Never do it! Will be fixed when 4.4 is out.
Issue Locked bootloader
If u have any issue with your phone (bootloop, stuck on bootlogo) and u have a locked bootloader, try the following:
Reboot to stock recovery
Do a "factory reset"
If that doesn't solve it, flash your original firmware (JB) with RSD-Lite! Make sure u use one of the latest versions of RSD-Lite, 6.1.x. 6.1.5 is the latest (Augustus, 2014)
Unlocked bootloader
If u have any issue with your phone (bootloop, stuck on bootlogo) and u have a unlocked bootloader, try the following (all staps are on there own. If one doesn't work, try another):
Reflash your custom ROM if u use one (don't wipe) (Renews your system partition, stays of your data)
Wipe your data/cache in recovery (does what it says)
Wipe partitions system/data/cache and flash new rom (reflash whole new system)
Do a nandroid restore if u have a nandroid backup of the rom (restore a previous nandroid)
Do a RSD-Lite flash, use latest versions of your stock firmware and RSD-Lite. (reflash to complete stock)
H. DOWNGRADE TO ICS
If u still want to downgrade from JB to ICS for whatever reason, those are the most save methods, because we disable the flashing of the ‘motoboot’, ‘gpt.bin’ and 'motobp'. There are 2 methods, 1 is by RSD-Lite with a modified xml file and the other one is flashing all the files manually. CANNOT BE DONE WITH LOCKED BOOTLOADER only unlocked!!!
RSD Lite:
Follow and read one of the tutorials for RSD-Lite and download your ICS Stock version of your device!
Set everything up and before flashing remove the following lines from the included XML file of the firmware u want to flash:
Code:
“<step operation= “flash” partition= “gpt” filename= “gpt_signed” MD5= “*****”>”
“<step operation= “flash” partition= “motoboot” filename= “motoboot” MD5= “*****”>”
“<step operation= “flash” partition= “motobp” filename= “motobp” MD5= “*****”>”
U maybe need to delete the following line also:
Code:
“<step operation= “getvar” var=”max-download-size”
U should be good to go!
Manually:
For manually flashing we need “mFastboot”. See GERNERAL (DEV) Tools for more information.
Download your firmware and extract it.
Now use the following commands in a command prompt. Make sure they are correctly spelled and return an “OKEY”!
Code:
[LIST]
[*]mfastboot flash boot boot_signed
[*]mfastboot flash recovery recovery_signed
[*]mfastboot flash system system_signed
[*]mfastboot erase cache
[*]mfastboot erase userdata
[/LIST]
I. FROM STOCK TO CUSTOM ROM
See threads that are mentioned above for more details.
Backup your important data from your phone to PC or elsewhere
Get ADB, Fastboot and your device drivers working
Unlock your bootloader with the above method
Install one of the recovery’s
Install a Rom and/or kernel from one of the threads in the Development section of the Razr I Board through custom recovery.
J. FROM CUSTOM ROM TO STOCK
See threads that are mentioned above for more details. If u want to relock too, have a look here (only for jellybean)
Backup your important data from your phone to PC or elsewhere
Get RSD-Lite working
Download the latest official android firmware for your device. (Always jellybean, unless u had ICS installed before the custom rom and to be on the safe side, never used a Jellybean version, then u can try ICS too)
Flash through RSD-Lite

Enormous post hazou! THank's a lot for all your work!
(work on rom, work on thread... etc)

Excellent job!

Thanks for this guide !
A question :
I'm whith KTR rom 2.2 ( JB 4.1.2 ) and, as all users, i have the unlocked phone screen when i boot my razr I.
If i do the step H. of the guide in order to downgrade to ICS, can i change the unlocked screen whith another one, and after reflash KTR rom ( JB ) in order to don't have anymore this unlocked screen at boot ???

elreydelaplaya said:
Thanks for this guide !
A question :
I'm whith KTR rom 2.2 ( JB 4.1.2 ) and, as all users, i have the unlocked phone screen when i boot my razr I.
If i do the step H. of the guide in order to downgrade to ICS, can i change the unlocked screen whith another one, and after reflash KTR rom ( JB ) in order to don't have anymore this unlocked screen at boot ???
Click to expand...
Click to collapse
To flash a working logo image u need the bootloader (motoboot) from ICS. But if u flash the motoboot from ICS coming from a jellybean rom (is using the motoboot from jellybean) u will brick your device. (unless as stated, u have never bean on stock JB or installed the firmware from stock JB and u flashed from stock ICS to KTR-rom. So u have the stock ICS bootloader. But i think nobody in this world has that anymore.)
The bootloader and its necessary files may never be downgraded!! I will make a point in the guide to address your question.
So, to answer your question. No u can't!

OK , thanks hazou !
There is definitively no solutions to remove this shi...of bootscreen ....

hey, I wanted to flash the stock rom with the rsd tool and I got my phone bricked, green light flashing, no code error message. Is there any solution for that problem?
edit: ok, I made a stupid mistake by accidentally downloading the ICS stock rom instead of the JB... f**k

bongofred said:
hey, I wanted to flash the stock rom with the rsd tool and I got my phone bricked, green light flashing, no code error message. Is there any solution for that problem?
edit: ok, I made a stupid mistake by accidentally downloading the ICS stock rom instead of the JB... f**k
Click to expand...
Click to collapse
Always read as much as you can and do lots of research to prevent a brick.

waj3k said:
Always read as much as you can and do lots of research to prevent a brick.
Click to expand...
Click to collapse
yep sure, I got it unbricked with the tut hazou linked in his post, so everything is fine

THX!
Nice thread. Thank you! This helps so much!

Motorola RAZR i xt 890 stuck at bootloader is unlocked
Please help!!!
My Motorola razr i xt 890 is stuck at AP Fastboot Flash Mode(secure boot)
and there are options like:
Normal Poweup
Recovery
Factory
BP tools
Switch Console [NULL: null]
Power Off
Now when I select any of the options from above it shows the screen saying "warning bootloader is unlocked" and after that it remains in the same condition.I can't access any of the options.
Please help me....

anuragtripathi said:
Please help!!!
My Motorola razr i xt 890 is stuck at AP Fastboot Flash Mode(secure boot)
and there are options like:
Normal Poweup
Recovery
Factory
BP tools
Switch Console [NULL: null]
Power Off
Now when I select any of the options from above it shows the screen saying "warning bootloader is unlocked" and after that it remains in the same condition.I can't access any of the options.
Please help me....
Click to expand...
Click to collapse
i have the same problem.
I managed to enter after many power + volume up press and it rebooted after many minutes, to the rom.
and it worked!
the only problem is that I can't make the antenna work. it's not working

[GUIDE] Flash Custom ROMs for the Xperia SP

WARNING
SONY has recently changed the method to unlock a bootloader. A rewrite will be done soon. Sorry for the inconvenience
Welcome to customising your phone! I made this guide specifically for new Xperia SP users (be it secondhand phones or you're just starting to do more with your XSP), and for future references until our Xperia SP forum cease from existence. There are many things to learn, if you search in the forums. This guide is to simply guide you into doing stuff in a more verbosely explained manner, at the same time will always be kept updated along with the progress of our Xperia SP.
This guide is universal — you can use any ROM versions that you like!**
"Universal Guide" Notice **
This guide mentioned "flashing custom ROMs". Though this guide is legitimate as it gets for flashing a ROM, I must warn you that methods provided here are exclusively a general outlook on how to flash a ROM. Always use the extraneous methods provided within a custom ROM's thread. If you fail to meet the exclusive requirements and steps of a ROM you will obviously encounter problems!
Disclaimer
Before you proceed, please understand that everything you do with your device, has many risks. If performed correctly, those terrible consequences may not happen. Any actions you will make are solely decided by yourself, and I have nothing to do with any damages that occur when you follow this very guide. Most importantly, following this guide will definitely void your warranty.
NOTE!
This post relies entirely on heavy formatting so you can understand better. Please open this post in a web browser, if you are viewing from a forum app. Tapatalk, for example. This also includes XDA Labs, which as of writing doesn't parse forum tags properly.
Things to consider before using Custom ROMs for your Xperia SP
Bootloaders
There are two different requirements for each custom ROMs here in the Xperia SP forum, in which there is one that require an unlocked bootloader and another is the one that can be used in a locked bootloader. What is a bootloader? A bootloader is a tiny program that enables you to get into an Operating System. Xperia phones have their bootloader locked by default. The one and only difference between a locked bootloader and an unlocked bootloader is the freedom to flash anything without so much concerns and risks of soft-bricking the device. In worse case scenario, even hard-brick too.
The choice to unlock your bootloader will be made by yourself. This guide will present on how to flash custom ROMs regardless of what bootloader you choose. NOTE however, some Xperia SPs are not allowed to unlock the bootloader. To check if you can unlock your bootloader, dial *#*#SERVICE#*#* (*#*#7378423#*#*) in Dialer. Tap on Service info > Configuration > Rooting Status and check if you can unlock your bootloader. The text "Bootloader unlock allowed: Yes" means that you can unlock the bootloader of your Xperia SP. If "No", I am sorry to say but you cannot do anything to unlock the bootloader. Don't worry yet! You can still use a special type of custom ROMs on a locked bootloader
Unlocking the bootloader will indeed have some drawbacks.
This will remove your DRM keys from your TA partition.
You will lose Bravia Engine on stock ROM forever. This due to the fact that the Bravia Engine requires the DRM keys that resides in your TA partition. This can be remedied, as you can actually back up your TA partition thus preserving your DRM keys as well!
Warranty will be lost for good. If you still have warranty, and quite paranoia if your device somehow magically broken, you also need to know that DRM keys also plays a huge role on confirming whether you have tempered with your Xperia SP's bootloader or not. SONY service centres will always check for the TA partition and also to see if your device is rooted or not. Root is reversible, but lost DRM keys is not. Again, backing up TA partition helps.
For those who can unlock their bootloader, since Xperia SP is no longer maintained officially by Sony and its last official ROM / firmware version is and will always be Jellybean 4.3, it is highly recommended to unlock your bootloader and set your Xperia SP for freedom. Unlocking the bootloader will also and always help you simplify things in the future.
Features
Custom ROMs are ROMs that are specifically made by different developers and teams based on their preferences and general idea. Depending on the custom ROM you want to use, you should understand that stock ROM features (e.g Camera, Walkman, Xperia Keyboard, Bravia Engine, etc) will no longer be available. This only applies on the custom ROMs that does not use the original stock ROM as a base.
Custom ROMs which are based on stock ROM on the other hand, usually contain a customised experience, while also providing the stock features to put into good use.
Stock ROM features aside, custom ROMs mostly are packed with other exciting features and customisations for you to tinker with, thus allowing you to make your ROM as unique to you as possible. You can inspect the screenshots posted on the ROM thread for a view of what features the ROM provides, or alternatively, (my favourite method) flash the ROM and test to see if it meets your preferences, and if the features really hook you up.
Explanation by another website (you will leave XDA)
Concluding
Now choose your device's future:
If you don't give a darn about TA partition, please refer to the guide 1(a). This can greatly reduce the hassle required while following this guide.
If you wish to both preserve your TA partition and unlock your bootloader, follow the respective guide which is guide 1(b).
If you don't want to or can't unlock your bootloader, there is also a guide for that, which is guide number 1(c).
Got questions? Refer to the second post for Q and As. If your question isn't there, feel free to ask!
Requirements!
Backup your apps. Use Helium backup tool. Do a backup of the apps that you want (only user-installed apps, or in other words, the apps that doesn't come with your Xperia SP when you bought it)
Un-metered and fast internet connection
A custom ROM's flashable zip of course. Copy the downloaded zip to your SD Card.
Download it by:
Going through the Xperia SP Lollipop Hub by @TheAvengingTITAN
Going through the Xperia SP Marshmallow Hub by @TheAvengingTITAN
Going to the custom ROM's thread of your choice in the Development subforum or the Original Development subforum
gapps package. Download the one supplied or suggested in the thread of the custom ROM of your choice. If there isn't any, maybe OpenGapps might be useful for you: http://opengapps.org (our device's architecture is ARM). Copy the downloaded zip to your SD Card.
Additional requirements if you want to unlock your bootloader:
Flashtool. Flashtool is a great software for you to flash your stock ROM back and also to do some other stuff. Download and install
Proper device drivers. After installing Flashtool, install the drivers by executing an installer from C:\Flashtool\drivers (assuming you didn't change the install location)
TWRP Recovery. We need the Beta downloads. Please download the twrp-3.0.X-rX-fota-huashan.zip. Copy the downloaded zip to your SD Card.
Unlocking the bootloader will wipe your /data partition. Please backup any files that you find important in the internal storage before performing these steps
Your IMEI written somewhere else. Dial *#06# to get your IMEI
Acceptable battery level (80% recommended)
Bootloader unlock code:
Go to: http://unlockbootloader.sonymobile.com/ and read everything!
At the bottom click 'Start Unlocking the Bootloader'
A number of prompts will be given. All you have to do is proceed (reading is optional and is recommended!)
Eventually you'll end up in the "Create Unlock request" page. From here enter your IMEI, name and email address. If your IMEI is unaccepted, try to enter your IMEI again, but excluding the last digit.
You should then receive the bootloader unlock key inside your email inbox.
1(a) I don't care about TA partition
WARNING: Once gone, you'll never able to retrieve your DRM keys, which will result in unable to use the Bravia engine, if someday, you wish to return to stock.
Just skip the guides below and jump to guide number 2.​
1(b) I wish to both backup TA partition and unlock my bootloader
A working adb bridge is required before you proceed. Install it on your computer from here
Make sure USB Debugging is enabled in Settings > Developer Options
Root your 4.3 ROM with Towelroot!
Download and install the Towelroot apk
Open the newly installed app
Hit the make it rain button
After succession, go to Play Store and install SuperSU
Open SuperSU
It will prompt to update your binary. Continue to do so
It will prompt and ask you to choose which method to update the binary. Choose "Normal"
Reboot your device
Backup your TA Partition. NOTE! You can do a "dry-run" to determine the integrity of your backup. NOTICE! If you are a Windows 10 user, do note that you will need to apply this "patch" for BackupTA to work on your operating system
Follow guide number 2.
1(c) My bootloader is not unlockable / I don't want to unlock the bootloader
A working adb bridge is required before you proceed. Install it on your computer from here
Make sure USB Debugging is enabled in Settings > Developer Options
Root your 4.3 ROM with Towelroot!
Download and install the Towelroot apk
Open the newly installed app
Hit the make it rain button
After succession, go to Play Store and install SuperSU
Open SuperSU
It will prompt to update your binary. Continue to do so
It will prompt and ask you to choose which method to update the binary. Choose "Normal"
Reboot your device
Install CWM recovery
Reboot into CWM recovery by pressing the Camera button whilst on the BLUE light on the LED bar
You can navigate in CWM by using the volume and power keys or by swiping the screen up, right, down, left.
Wipe everything you can.
go to "Mounts and storage"
Format /system
Format /data
Format /cache
Go back to main menu
Get into "Advanced" > "Clear Dalvik Cache"
Go back to main menu
Attempt "Wipe data/factory reset"
Flash the custom ROM zip you've downloaded.
Go to "Install zip"
Choose "Choose zip from /storage/sdcard1" (I am assuming you've put the zip into your SD card)
Navigate to the zip you've copied, and select it
Choose "yes"
Flash gapps. The flashing process is similar to how you flashed the custom ROM zip based on the steps above.
Reboot the phone
You now have your preferred custom ROM installed! Congratulations! Set up your phone as usual now.
Restore your applications backup if you wish to have your apps back.
Your steps end here.
Now jump to the "Have fun" part to continue reading
2) Unlock the bootloader and flash TWRP recovery
Unlocking your bootloader:
Shut your phone down.
Open FlashTool as administrator.
Copy your unlock bootloader key that you received
Make sure drivers are installed. Install them by going to Flashtool install directory (default is C:\Flashtool) and then "drivers" folder. Install the .exe there in.
Click BLU on the toolbar
Connect your phone in flash mode (hold down vol down while device is powered off then connect to your computer. you can release vol button once phone is detected)
This will require you to enter IMEI and bootloader unlock key. You might need to check thrice for this to make sure the IMEI and bootloader unlock key is correctly copied.
Proceed. This will wipe your data completely. I've warned about this earlier on this post so I assume you've did a backup of important files.
Disconnect your phone upon completion. If it restarts, you need to shut it down after it booted.
Leave Flashtool open in order to proceed to the steps below.
Flashing the recovery:
Extract the TWRP recovery zip file you attained earlier. We will need to use the "twrp.img" file
Connect your phone in fastboot mode (hold down vol up while device is powered off then connect to your computer. you can release vol button once phone is detected)
Flash the kernel by selecting the Lightning icon in the toolbar, select Fastboot mode, then select "Select Kernel to Flash". Navigate to and choose the file "twrp.img" extracted earlier
Unplug your phone upon completion
Power up your phone. It will boot directly into TWRP Recovery
Once in recovery, you may now close Flashtool.
Please follow the guide below.
NOTE!
This will only grant you temporary access to recovery, as we are flashing the recovery into your /boot partition. When you flash the ROM zip later, this partition will be replaced with the ROM's kernel and the recovery will be lost!​
3) Flashing the custom ROM
NOTE: Please understand methods are vary for different ROMs. Please prioritise steps provided in a custom ROM thread. This guide however, can be regarded as a "logic" for you to flash such custom ROM.
Wipe everything you can.
go to "Wipe"
Advanced Wipe
Tick Dalvik / ART Cache, System, Cache, Data
Slide the slider to wipe the ticked partitions
Go back to main menu
Flash the zips you've downloaded.
Go to "Install"
Tap on "Select Storage" button to select your storage that contains the flashable zip of your ROM and gapps. Assuming you put it in the sdcard, then it should be "Micro SDCard"
Navigate to the ROM zip, and select it
After that, hit the button "Add more Zips"
Navigate to the gapps zip, and select it
Make sure "Zip file signature verification" is disabled
Optional: You might want to flash the TWRP recovery zip downloaded earlier so that you would have a permanent TWRP recovery
Slide the slider to start flashing process
Choose "Reboot system"
You now have your preferred custom ROM installed! Congratulations! Set up your phone as usual now.
Restore your applications backup if you wish to have your apps back.
Your steps end here.
Have fun
You should now have completed the guide and have a custom ROM running on your device. Have fun with numerous new experiences in the time to come!
If you want to change ROMs in the future, after you have already flashed a custom ROM, you will just have to restart the same flashing procedure.
Don't forget to thank this post if my guide really helped you!

FAQ
FAQ
Q: What are custom ROMs actually?
A: I believe, Google will help you. This link might help you as explained by AndroidPolice: http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/
Q: I can't unlock my bootloader! What should I do?
A: I understand how sucks it is for this to happen. But don't worry, there are also methods for locked bootloader phones. If you read my first post correctly, there is a method geared towards a person who can't unlock their bootloaders.
Q: What is a TA Partition?
A: TA Partition is a unique partition that can be found in almost any Xperia phones. It contains mostly DRM keys and other boot parameters. Unlocking the bootloader does not wipe the TA partition, but somehow edit it. I don't know much about this part.
Q: Why will Bravia Engine not work if I use custom ROMs?
A: In order to use some custom ROMs you'll need to unlock your bootloader. Unlocking the bootloader will definitely remove the DRM keys, which is a requirement for the Bravia Engine. Backing up TA will backup your DRM keys as well, just in case if you want to get back to stock.
Q: If that's the case, what will happen if I relock my bootloader after flashing a custom ROM?
A: Relocking bootloader when using a custom ROM is not a safe practise, and will definitely soft brick your device. Basically, constant SONY logo.
Q: How about flashing custom ROM without unlocking the bootloader?
A: It depends on the ROM. If the ROM is solely for unlocked bootloaders, doing this will of course brick your phone. Please refer to guide number 1(c) on how to use custom ROMs without unlocking a bootloader (which only applies to ROM for locked bootloaders).
Q: Is it really necessary to back up TA Partition?
A: TA Partition backups will help you on getting your phone to its really fresh factory state. Moreover, it allows you to have Bravia Engine working on stock ROM, if you wish to get back to the stock ROM. If your phone has warranty, backing it up is recommended, as you'll need to restore it before handing it to the repair centre.
Q: I didn't backup my TA Partition. Can I ever get it back?
A: You'll never able to get it back. And please don't ever try to restore anyone's TA backup as that will ultimately cause your phone to be bricked very hard.
Q: What is this software called BackupTA?
A: Please read the explanations provided in the thread of such software. The software help you to backup and restore your TA Partition.
Q: Are these guides safe?
A: Sure! :fingers-crossed: But I can't give 100% guarantee. Fortunately, this guides are constructed based on my experience. My Xperia SP is still running and is still being used right now.
Q: I broke my phone while following your guide. What can I do now?
A: I hope its a soft brick. If so, please follow mrjraider's tutorial on how to use Flashtool and then flash a stock FTF to get back your phone to its stock ROM. If your bootloader is unlocked, reverting to its normal state is easy. Just go back to the main post of this thread, and follow the "Flashing the recovery" part of the guide number 2.
Q: What are bricks?
A: There are two types of bricks. First one being soft, and the second is hard. Therefore softbrick and hardbrick. Softbrick is a situation where you cannot use your phone, however it can still boot / start. This applies to events in which you keep having SONY logo shown many times, or the SONY logo stays on the phone after minutes of waiting. Softbrick is repairable. Hardbrick, is a situation where your phone is completely damaged. Usually, the phone will never able to start even after many methods used and will show signs of ultimate death. Repair is possible, though mostly it is not. If you prefer, you can have a look in Wikipedia for a solid and thorough explanation
Q: How can I prevent from bricking?
A: Always know what you are doing and follow the guidelines laid out
Q: How about battery usage, is it good?
A: Custom ROMs are mostly based on the original Android experience (AOSP). AOSP is the purest android you can ever think of. AOSP doesn't have these neat features that most company provides, rather, it is Android at its bare. This being said, Stamina mode will no longer be available on your phone. To counter this you may use Greenify, an app that hibernates apps. Moreover, since custom ROMs aren't developed by the manufacturer of the device itself (in this case SONY), it will not conserve battery as good as stock, but at the same time battery life is still acceptable and long-lasting. Also as of Lollipop, the introduction of Doze to the AOSP makes battery conserving on custom ROMs a lot better. To summarise, the experience is slightly different, but still is amazing. To give a rough comparison on a ratio-based rating, it would be 0.95:1 (custom ROM:stock ROM)
Q: The ROM I use has an update. How can I update?
A: You can just download the new updated zip, and flash it normally. This action is alternatively called "dirty flash". Then, reboot into your ROM. If your ROM is provided with an updater app, you can also use it to simplify the process.
Q: How about root in custom ROMs?
A: By norm, root comes with any custom ROMs that you wish to use. When you have successfully flashed a custom ROM, you don't need to do any additional steps in order to have root access. Exception goes for CM ROMs and some CM-based ones which does not ship SuperSU. You will need to enable root from within the Developer Options in Settings. To enable Developer Options, tap "Build Number" in "About Phone" 7 times.
Q: Can I somehow use stock ROM features on my current custom ROM?
A: No. The stock features on stock ROM is not portable, hence cannot be used freely on a custom ROM. You can however, find a specific port to an Xperia app / feature (e.g Xperia Keyboard) by searching for the port on XDA. Make sure that the port is compatible with the ROM you are currently running. The reliability of these ports are greatly dependant on the ROM version and type that you are running, so you may actually experience either problems or greatness when you are running these ports.
Q: I'd like to use another file system f2fs for my partitions (Advanced)
A: By default, all partitions on Android are formatted as ext4. This can be changed easily by using the TWRP recovery. Note that this is only for unlocked bootloaders only!
Please note that only data and cache could be formatted as f2fs. System partition cannot be formatted as such due to how ROM installations are block based. The steps are as follows:
Boot into TWRP recovery
Select Wipe
Select Advanced Wipe
Tick a single partition you wanted to change its filesystem
Select Partition Options button
Change file system
Select f2fs and proceed
Done
CAUTION! This will also cause data in internal storage to cease from existence as well
NOTE! A ROM may not support f2fs (rare occurrence). So it would always be best to prepare for the worst if you are not certain of a particular ROM supports f2fs or not
Suggestions?
If you have any suggestion that may improve these guides, do tell me about it. I would be happy to make it better

Uhm.. Nice but we don't need a lot of thread with the same instructions.
Doomlord has made a general thread in the Android Development and there was another thread with rooting and flashing and stuff..

mrjraider said:
Uhm.. Nice but we don't need a lot of thread with the same instructions.
Doomlord has made a general thread in the Android Development and there was another thread with rooting and flashing and stuff..
Click to expand...
Click to collapse
Well I tried my best to make it look like if its not a duplicate. It is really a shortcut through things, and yet the guide here in are actually my own way of doing stuff (inspiration from DoomLord's and other guys' tutorials) for example, DoomLord has a guide on unlocking bootloaders with adb command, while I use Flashtool itself to get it done. I see your point really, and I'm okay if this guide should be nominated for deletion (even if I woke up to deletion of this thread). The choice is in the mod's hand now. Thank you by the way
EDIT: Plus, searching is a pain. Links herein this thread are the ones I bookmarked when I was a really noob person back then. Thought of giving them newcomers a head start though. Later on, I am sure they will discover themselves new things, and started diverting from stuffs provided in this thread, to other things based on their choices.
I even wanted to put out links to other tutorials, but..... nevermind

A few questions
Hi sorry for hijacking the thread, I'm not sure if this is the right place to ask a few questions that has been bothering me for sometime. I have followed every step of the guide correctly and successfully installed CM 11 on my Xperia Sp, however there are certain things that I haven't quite understood ..sorry if they are noob questions
> What is the DoomLord kernal supposed to be? Is it same as installing CWM recovery? if yes ,then how can I flash a different recovery like TWRP?[/B]
> Is the kernal different for installing anything other than CM?
> If I am to go back to stock ROM for warranty purpose, should I remove the Kernal first? If yes then how?
Thanks in advance

murky94 said:
Hi sorry for hijacking the thread, I'm not sure if this is the right place to ask a few questions that has been bothering me for sometime. I have followed every step of the guide correctly and successfully installed CM 11 on my Xperia Sp, however there are certain things that I haven't quite understood ..sorry if they are noob questions
> What is the DoomLord kernal supposed to be? Is it same as installing CWM recovery? if yes ,then how can I flash a different recovery like TWRP?[/B]
> Is the kernal different for installing anything other than CM?
> If I am to go back to stock ROM for warranty purpose, should I remove the Kernal first? If yes then how?
Thanks in advance
Click to expand...
Click to collapse
No worries. Asking any questions are indeed welcomed in this thread
DoomLord kernel is a custom kernel. If based on my guide, the kernel mentioned contains CWM recovery with it therefore, making it easier to access recovery compared to traditional method.
Installing CM will wipe the kernel off. The (DoomLord's) kernel is created only for stock ROMs. Flashing such kernel on custom ROMs will usually cause soft brick.
Since DoomLord's kernel are gone during the flashing process of CM, no. But still, NO, flashing stock ROM will wipe the kernel as well and puts in the stock one.
If you requires elaboration, please say so. I would be glad to clarify :angel:

Thank you so much! I was quite worried thinking that I had made a wrong decision.
> so you are saying that custom ROMs use their own Kernels? If so then there are no prerequisites to installing custom kernels beforehand? I'm guessing that would brick the phone?
> If CM does wipe off the kernel then how is it that the recovery is still working? its meant to be the part of the DoomLords kernel right?
>Can I change my recovery now to a different one?

TechnoSparks said:
No worries. Asking any questions are indeed welcomed in this thread
DoomLord kernel is a custom kernel. If based on my guide, the kernel mentioned contains CWM recovery with it therefore, making it easier to access recovery compared to traditional method.
Installing CM will wipe the kernel off. The (DoomLord's) kernel is created only for stock ROMs. Flashing such kernel on custom ROMs will usually cause soft brick.
Since DoomLord's kernel are gone during the flashing process of CM, no. But still, NO, flashing stock ROM will wipe the kernel as well and puts in the stock one.
If you requires elaboration, please say so. I would be glad to clarify :angel:
Click to expand...
Click to collapse
Thank you so much! I was quite worried thinking that I had made a wrong decision.
> so you are saying that custom ROMs use their own Kernels? If so then there are no prerequisites to installing custom kernels beforehand? I'm guessing that would brick the phone?
> If CM does wipe off the kernel then how is it that the recovery is still working? its meant to be the part of the DoomLords kernel right?
>Can I change my recovery now to a different one?

murky94 said:
Thank you so much! I was quite worried thinking that I had made a wrong decision.
> so you are saying that custom ROMs use their own Kernels? If so then there are no prerequisites to installing custom kernels beforehand? I'm guessing that would brick the phone?
> If CM does wipe off the kernel then how is it that the recovery is still working? its meant to be the part of the DoomLords kernel right?
>Can I change my recovery now to a different one?
Click to expand...
Click to collapse
Usually yes. Yes. No, as by the time you flashes the custom ROM zip (in which there is a boot.img file within it), it overwrites the old kernel, so no bricks.
I am not sure as of correct answer, but in my point of view the recovery is loaded into your RAM. When you flash a custom ROM, the recovery files are indeed gone (with the kernel) but the recovery still working as it is residing in your RAM (I still could be wrong though). Once you restart, the recovery you used will be gone but you are still able to access recovery in which were included in the newer kernel.
Yes indeed.
Sorry for the late reply, I am quite busy these days, so my online frequency is not like before.

TechnoSparks said:
Usually yes. Yes. No, as by the time you flashes the custom ROM zip (in which there is a boot.img file within it), it overwrites the old kernel, so no bricks.
I am not sure as of correct answer, but in my point of view the recovery is loaded into your RAM. When you flash a custom ROM, the recovery files are indeed gone (with the kernel) but the recovery still working as it is residing in your RAM (I still could be wrong though). Once you restart, the recovery you used will be gone but you are still able to access recovery in which were included in the newer kernel.
Yes indeed.
Sorry for the late reply, I am quite busy these days, so my online frequency is not like before.
Click to expand...
Click to collapse
Hey sorry for bothering again, but I have noticed that after installing CM11 my RAM memory is only 839MB, can you explain why? Is it because of the recovery which you mentioned above? And if I flash another recovery, will the issue be solved?

murky94 said:
Hey sorry for bothering again, but I have noticed that after installing CM11 my RAM memory is only 839MB, can you explain why? Is it because of the recovery which you mentioned above? And if I flash another recovery, will the issue be solved?
Click to expand...
Click to collapse
I am guessing that you have many apps running in the background. May please share a screenshot?

technosparks said:
i am guessing that you have many apps running in the background. May please share a screenshot?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

murky94 said:
View attachment 3081260
View attachment 3081261
Click to expand...
Click to collapse
OOoooO! For your information, our available RAM for user is indeed 839MB+. I thought you were talking about RAM usage.

TechnoSparks said:
OOoooO! For your information, our available RAM for user is indeed 839MB+. I thought you were talking about RAM usage.
Click to expand...
Click to collapse
Ohh I see thanks again for your time
---------- Post added at 04:47 PM ---------- Previous post was at 04:43 PM ----------
murky94 said:
Ohh I see thanks again for your time
Click to expand...
Click to collapse
By the way, have you ever experienced lag with custom launchers? I have been trying to use a different launcher but there is always a certain seconds of lag when I press the home and background keys and this stays on until I uninstall the launcher itself!

murky94 said:
Ohh I see thanks again for your time
---------- Post added at 04:47 PM ---------- Previous post was at 04:43 PM ----------
By the way, have you ever experienced lag with custom launchers? I have been trying to use a different launcher but there is always a certain seconds of lag when I press the home and background keys and this stays on until I uninstall the launcher itself!
Click to expand...
Click to collapse
No problem mate!
Actually no (or maybe I am used to it). I am using only Nova launcher.
there may be two problems. If your launcher redraws, it seemed that you are using a lot of your RAM.
If your launcher loads okay, then based on community posts, if you have multiple launchers I suggest freezing all of them unused one. You can use Titanium Backup to freeze those other launchers. Alternatively you may use a custom kernel to banish this lag as people claims it came from the default CM kernel.
---
By the way, may I know which method do you used in my tutorial?

TechnoSparks said:
No problem mate!
Actually no (or maybe I am used to it). I am using only Nova launcher.
there may be two problems. If your launcher redraws, it seemed that you are using a lot of your RAM.
If your launcher loads okay, then based on community posts, if you have multiple launchers I suggest freezing all of them unused one. You can use Titanium Backup to freeze those other launchers. Alternatively you may use a custom kernel to banish this lag as people claims it came from the default CM kernel.
---
By the way, may I know which method do you used in my tutorial?
Click to expand...
Click to collapse
Thank you for all your help, I have followed your entire guide.

murky94 said:
Thank you for all your help, I have followed your entire guide.
Click to expand...
Click to collapse
Yes I may aware of that. But may I know which method did you used, 1a, 1b, or 1c?

TechnoSparks said:
Yes I may aware of that. But may I know which method did you used, 1a, 1b, or 1c?
Click to expand...
Click to collapse
I have used 1(b) followed by the rest

murky94 said:
I have used 1(b) followed by the rest
Click to expand...
Click to collapse
I think I may have solved my lag problem, I repeated the whole process, flashed the stock ROM first which restored my stock kernel/recovery and after that I flashed CM11, but without the DoomLord's kernel.

As a token of appreciation to this great device and it being slowly dying, I have again updated this guide to conform with latest changes. I had also verbosely explain some aspects of the things in the guide. Additionally, I also tried to provide better readability of the guide so that readers don't confused with numbers and alphabets eg, 1a is now 1(a).
This guide is pretty useful for new Xperia SP users in my honest (and maybe selfish ) opinion. I hope it benefits new users or old users as well.
Also, I am quite sad that my Xperia SP screen is damaged. This is due to a motorcycle accident that I confront with yesterday. The screen is not cracked, yay to Gorilla glass, but the screen isn't showing any colour. I don't know when will I have the money to fix it.
/monologue off
Ok, thanks.

[GUIDE] How to package and flash stock roms with Flashtool

Flashtool is an extremely useful tool maintained by Androxyde that allows you to download and flash stock roms to your device and more.
I thought it would be a good idea to create a guide showing how to use some of the most useful features of this great tool. It will be focused on the Xperia Z as that's the device I own, but will also apply to other devices compatible with Flashtool. I will add more sections to the guide as I get time to do so.
Contents:
1. Install Flashmode and Fastboot drivers.
2. Download any firmware customisation and create an FTF.
3. Flash stock firmware in FTF format to your device.
4. More coming soon....
Requirements:
Windows PC
Flashtool driver package by DooMLoRD.
Flashtool by Androxyde.
Part 1.
Install Flashtool drivers:
1. Run the installer. You will see this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press "Next" to continue.
2. Select Flashmode and Fastboot drivers. These drivers are common drivers for all compatible devices. Also scroll down the list and select Xperia Z drivers (or the relevant drivers for your device). This installs the ADB drivers for your device.
Press "Install".
The drivers will now install.
Note: If you're on Windows 8, then try this if you have trouble installing the drivers - Resolving driver installation issues on Windows 8 (thanks to fards)
Part 2.
How to create an FTF of any firmware customisation version:
Flashtool now integrates the excellent XperiFirm by Iagucool for downloading firmware. This guide has been updated to reflect that.
For the purposes of this guide, I downloaded the Customized NCB firmware version 10.6.A.0.454 for the C6603.
1. Start Flashtool and wait until it finishes syncing devices.
2. Click on the XperiFirm icon (highlighted red in image).
If this is the first time you've done this, Flashtool will download XperiFirm.
3. Find Xperia Z (or whichever device you like) on the list and click on it.
Select your device variant from the list that expands and click "Check all".
4. Find the firmware version you want in the list, click on it, then click the firmware version you want to download in the list on the right.
Press "Download" in the window that appears.
5. XperiFirm will download and unpack 5 files.
6. When XperiFirm has finished downloading and unpacking the files, press OK and close XperiFirm.
7. Flashtool will automatically create the bundle and will display when it's finished. You can now close Flashtool.
Part 3.
How to Flash an FTF using Flashtool:
Your bootloader does not need to be unlocked and you do not need root to flash roms in FTF format with Flashtool.
1. Place the FTF you have in C:\Users\your username\.flashtool\firmwares if it isnt there already (if you followed this guide to create an FTF it will be in the correct place already).
2. Start Flashtool and wait until it finishes syncing devices.
3. Click on the lightning bolt icon, select Flashmode and press OK.
4. Choose the firmware you wish to flash from the list on the left (highlighted red). If you want to keep data and installed apps etc, then uncheck everything in the Wipe section (highlighted green). Conversely, if you want a clean install, check everything in the Wipe section. Make sure nothing is checked in the Exclude section (highlighted blue). Note that if you're flashing over a custom rom or downgrading, then wiping all data is required.
When everything is as it should be, press Flash (highlighted yellow).
5. Flashtool will prepare files for flashing.
6. This screen will appear:
Power OFF your device. Connect your USB cable to your PC, then while holding Volume DOWN, connect the other end of the USB cable to your device.
Flashtool will now flash the firmware. When the flashing process starts, you can release the Volume down key.
DO NOT disconnect your device at this point, until it says it's safe to do so. When Flashtool says it has finished, disconnect your device and power it on. You have successfully flashed stock firmware to your device.
Disclaimer:
This guide is provided in good faith and the steps as provided work fine for me. However, I will not accept any responsibility for data loss or possible damage to your device. Following this guide is done at your own risk.
Credits:
DooMLoRD for the Flashtool driver package.
Androxyde for Flashtool.
Iagucool for the XperiFirm firmware downloader used by Flashtool.
If I've forgotten anyone please let me know and I'll add them.

Hey @kingvortex bro!
Nice guide. And now I don't have to write a full instructions about how to flash ftf for every newbie need it here
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!

Thanks.
Sent from my C6603 using Tapatalk

Del.

Nice and very useful guide for the new comers. Keep up the good work..

Thank you for great job.
When I create ftf (backup my ROM), the apps I download from Google play and data backup also? Or just ROM?

thedark1979 said:
Thank you for great job.
When I create ftf (backup my ROM), the apps I download from Google play and data backup also? Or just ROM?
Click to expand...
Click to collapse
This guide creates a FTF from files downloaded from Sony's servers. It doesn't backup your rom or data.
Sent from my C6603 using Tapatalk

kingvortex said:
This guide creates a FTF from files downloaded from Sony's servers. It doesn't backup your rom or data.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thank you. But how I can backup my ROM and apps and data with this tools? Not from CWM recovery ?

You can't, as far as I'm aware. If you need help backing up your data, please open a thread in the Q&A section. Thanks.
Sent from my C6603 using Tapatalk

thedark1979 said:
Thank you. But how I can backup my ROM and apps and data with this tools? Not from CWM recovery ?
Click to expand...
Click to collapse
It's off topic but I'll answer you to not post off topic things here and other threads.
For apps backup download titanium backup or ultimate backup from Play store. You can backup your ROM from recovery only.
Those apps need root.
For how to root search around here.
Don't ask about that again here. Do that in a new thread if you still have issues.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!

I have downloaded the firmware from another pc using xperifirm but when i am creating an ftf, i cannot edit the device name. this prevents me from proceeding with the ftf creation. can you tell me how to fix it?

imboy25 said:
I have downloaded the firmware from another pc using xperifirm but when i am creating an ftf, i cannot edit the device name. this prevents me from proceeding with the ftf creation. can you tell me how to fix it?
Click to expand...
Click to collapse
Double click in the field.
Sent from my C6603 using Tapatalk

kingvortex said:
Double click in the field.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Oh my goodness! :silly:

imboy25 said:
Oh my goodness! :silly:
Click to expand...
Click to collapse
Yeah, that's actually easy to miss to be fair. I'm not sure why it's that way. There must be a good reason.
Sent from my C6603 using Tapatalk

Can anyone help me?
I'm trying to install AOKP on my work colleague's C6630 (Xperia Z) which is from O2 in the UK, the bootloader allowed says No and I've tried the flashtool and the process shown in this thread, none of the root methods in the flashtool are working and the FlashMode doesn't respond when I attempt to install the generic UK rom, shows a quick red led, then a quick green led, then nothing (Windows does show a driver problem even though I've installed the fastboot .
I can carry out ADB or flashboot commands by going into those modes but nothing that will let me root or install a custom recovery partition.
I'm stuck and can't get any further, even though a lot of the guides here say you should still be able to get root while the bootloader is locked.

I have xperia z 4.4.2 bootloader unlocked and rooted.. and I have pacman rom..
I downloaded the ftf of 4.4.4 how can i flash it?

djsubterrain said:
Can anyone help me?
I'm trying to install AOKP on my work colleague's C6630 (Xperia Z) which is from O2 in the UK, the bootloader allowed says No
Click to expand...
Click to collapse
You cannot flash AOSP/AOKP/PAC etc or any rom that needs a custom kernel when you have a locked bootloader. There's no way to unlock your friend's bootloader, unfortunately.
SkoopMan said:
I have xperia z 4.4.2 bootloader unlocked and rooted.. and I have pacman rom..
I downloaded the ftf of 4.4.4 how can i flash it?
Click to expand...
Click to collapse
Follow the guide that's in the first post.
Sent from my C6603

kingvortex said:
You cannot flash AOSP/AOKP/PAC etc or any rom that needs a custom kernel when you have a locked bootloader. There's no way to unlock your friend's bootloader, unfortunately.
Sent from my C6603
Click to expand...
Click to collapse
Should it be possible to root though so he could use xposed frameworks to get some sort of custom experience? I did try every single method in the flashtool for rooting but none of them worked.

djsubterrain said:
Should it be possible to root though so he could use xposed frameworks to get some sort of custom experience? I did try every single method in the flashtool for rooting but none of them worked.
Click to expand...
Click to collapse
Yes, you can root without unlocking the bootloader.
On 4.4.2 or below, use towelroot. On 4.4.4, it's slightly more complicated. Guide here.
Sent from my C6603

kingvortex said:
Yes, you can root without unlocking the bootloader.
On 4.4.2 or below, use towelroot. On 4.4.4, it's slightly more complicated. Guide here.
Sent from my C6603
Click to expand...
Click to collapse
Thanks so much, finally got root. Do you know if the dualrecovery allows you to install any custom roms or will it only work for flashing tools, etc?
Having problems trying to find the correct XZdualrecovery for this phone too, it's the Xperia Z (C6603), although I can't seem to find this on the http://nut.xperia-files.com/ site, anyone know which one is for the C6603?

[Knowledge Base] Introduction to the Sony (-Ericsson) Xperia Galaxy

But... why?
Well, many people like and buy the Xperia line of devices currently on the market who previously owned a Samsung, LG or HTC. There are many differences in hardware, but most certainly in how Sony perceives the Android ecosystem and how it differs from the other major brands. This (noob) guide is meant to help people on the path to the Sony side I'm sure it contains lots of info which is even useful for the old timers
Things which differ a LOT from the other brands:
First and foremost: no recovery partition;
Second but not least: no download mode.
Sony has replaced the Android recovery partition with the FOTA kernel, which is meant to aid the device in rolling out OTA updates, which allow kernel updates without the risk of bricking the device. I hear you scream: "But wait, what about the recovery partition announcement by Sony themselves!?", well the answer is simple: that is meant for unlocked bootloader devices ONLY, as a part of their "Open Devices" program.
What is Flashmode, Flashtool and what are these FTF and SIN files I am reading about?
I'm going to quote @Androxyde here (it's a straight copy of his index page), as he is the maintainer of the tool:
Flashtool is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS/SUS or PC Companion.
Based on a command line tool written by @Bin4ry (Andreas Makris), I brought a user interface to sin files flashing.
We worked together to add more features to the tool such as rooting methods implementation or TA backup / restore.
Then I took the lead and got some advice and help from him occasionally on some features like rom cleaner or bootloader unlocking.
From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares) and more features have been implemented.
But flashing firmwares is still the core of Flashtool (that is updated at least to follow Sony improvements around sin files) and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable
The flashing feature as well as bootloader unlock feature are available whatever the phone is recognized or not by the application. What is only mandatory for flashing is to own the FTF file according to the device you want to flash it on.
Why should I use Flashtool?
Once bootloader unlocked, official sony tools do not work anymore.
Using official sony tools, you can only upgrade. No downgrade possible.
Using flashtool, you can choose what to flash and what not to flash. This said, many rooting scenarios are available implying kernel only downgrade to retrieve a patched rooting exploit and then flash back the right kernel.
You said unlocking bootloader?
This process gives you the opportunity to flash custom roms such as CyanogenMod ROMs.
I invite you to visit the FXP Project that brings CM and AOSP to xperia devices.
Click to expand...
Click to collapse
To complete this explanation, Sony devices know 2 bootloader based flash modes:
Flashmode (This is the S1 flash protocol @Androxyde wrote about)
Fastboot (This is the original, unmodified fastboot mode from Google)
In the past there was the Sony-Ericsson Update Software/Service (SEUS, later named SUS because Ericsson got removed from the name) which could update your device to the latest software or recover it from an inoperable state. PC Companion was less of a tool for updating and more of making backups, installing applications and managing the device storage. Sometime the past 3-4 years Sony merged the 2 programs, so if people on XDA or anywhere on the web talk about using PC Companion to restore their device, they are not wrong, they are simply using the latest version
Sony recently released their own package called 'flash tool' (to add to the confusion of noobs in the community), which deep down is a little easier to use and stripped down version of EMMA, which is a tool we mere mortals will probably never use as EMMA is the flash tool for Sony's repair shops and tech support. It's primary function is to allow owners of an unlocked bootloader device (or, 'open device' as Sony named it) to still use Sony firmwares and update their device, because as soon as you unlock the bootloader, the OTA updates will stop.
Things to remember on the files used by these tools:
An FTF file is basically not more then a ZIP archive containing multiple SIN files, you can open the FTF using 7z/WinZip/WinRar and look inside it.
A SIN file is a disk/partition image, which is encrypted by Sony. S1 (the bootloader) will check this encryption to make sure the image was not tampered with before it accepts it for flashing.
Fastboot flashing will always fail when the device is still in a locked bootloader state. For some models it is even disabled entirely or non-functional until you unlock the bootloader.
I am reading about the TA, what is it, why should I make a backup?
The TA partition (Trim Area) is a signed partition which holds various things which are unique to your device, like the device's IMEI, DRM keys and bootloader settings and configuration options. This partition can not be exchanged between devices, because it really is unique. If you would flash the TA backup from someone else it will cause a hard-brick rendering your device only useful as a paperweight...
When you unlock your bootloader you will lose all the DRM features on your device, this makes it valuable to have a backup of the unmodified version stowed away somewhere safe. You will need root level access to create that backup before unlocking. There is a tool called Backup TA which is widely used to create and restore backups of the TA partition. TWRP in XZDualRecovery can do the same.
When you restore the backup TA partition you made before unlocking the bootloader you will essentially re-lock the bootloader and restores the DRM keys. This process is (as far as we know up to now) undetectable by Sony's support staff, which makes it easy to restore the phone to stock for warranty driven support issues as unlocking your bootloader will void your warranty on the device (it is subject to local law though). That is why, for a lot of owners of a Sony device at least, it is considered to be the "Holy Grail" and is usually the reason for a lot of users to wait for a root exploit to be found before unlocking their bootloader.
Okay, I get it now. I would like to unlock my bootloader, how to proceed?
I'm not here to rewrite everything other people or Sony themselves can write just as well or even better, so I have a link for you:
http://developer.sonymobile.com/unlockbootloader/
Read it, it will teach you just about everything you need to know.
Once your bootloader is unlocked, your device will be much like a Nexus device when it comes to rooting, excluding the recovery partition, so that's why we flash or hotboot a custom kernel with a recovery, by using fastboot. If you are afraid of a terminal and typing commands, you can use a tool like QuickIMG or Flashtool to make your life easier.
Right, now I want root!
Well, if you have an 'open device', this is a lot easier then you think. Just remember that using root exploit kits is unnecessary and in some cases even risky as some packages do funky things or jeopardize your privacy.
Try to find a 'stock based' custom kernel. These are custom kernels built by the community to add features to the kernel but are meant to work with Sony's stock firmwares. I'm the maintainer of XZDualRecovery myself and created the Kernel Builder for the supported devices.
These custom kernels will NOT root your device (unless otherwise stated by the creator), but introduce a recovery to the boot process and with that you will be able to flash SuperSU to root your ROM.
But you just said Sony devices don't have a recovery partition, please... UN-confuse me!!
Yes, I did, and I'm right: there have been bright minds in the community who included a recovery in the boot image (the kernel partition) in the past and that way included a recovery on our Sony devices.
With the current 'open devices' policy from Sony, we now have:
Recovery stored inside the system partition, which is meant for locked bootloader devices (closed devices) because they can not run custom kernels;
Recovery stored in the boot image (for open devices);
Recovery stored on the FOTA partition, but with a trigger from the regular boot image at boot (also for open devices);
Recovery stored on the FOTA partition -renamed to recovery- together with an updated bootloader (for open devices, of course).
Hmm, okay... it's still confusing, but OK. My service menu says I'm rooted, but none of the root apps work properly, what gives?!
If you open the phone dialer app and on the keys see the letters below the digits, you can spell the word SERVICE. Type *#*#SERVICE#*#* and a service menu will pop up. Tap 'Service Info' and then 'Configuration'. Then you will see one of these lines there almost on the bottom of the list:
"Rooting status: unknown": it's probably unlocked, but it was unable to verify that;
"Rooting status: rooted": you have unlocked the bootloader;
"Unlock bootloader allowed: YES/NO": this tells you if the bootloader is (vendor-) locked or not, if it says NO, you're out of luck.
The rooting status there is not telling your system is rooted, it tells you your bootloader is and will allow custom rom/kernel flashing. Don't confuse these two.
I'm not allowed to unlock my bootloader But I still want root, can I?
In some cases you can. It depends on the bugs found in specific firmware versions which allow a root exploit to be developed.
From the 2015 range of Xperia devices Sony started using dm-verity, which causes a bootloop once the system partition is modified. This modification of the system partition will be required to include a SU binary in the system to obtain root, so until a dm-verity defeating option is found, locked bootloader root or recovery will not be possible.
For older models, check the device forums and the cross device development forums to check out the community rootkits available. Usually it will tell you what ROM version it is intended for. Be careful with rootkits/roottools though, some are also found to be introducing malware to your device or sending privacy sensitive data to the creators. Use common sense, if you have no valid use for the root user level, keep it off your phone. If you already have recovery, you can use that to modify or clean your device instead.
I have rooted my phone, but whenever I try to modify something on it it spontaneously reboots or I get a message 'Permission denied" when trying to remount the system partition R/W! Why is that?
Like all manufacturers, Sony tries to make it difficult (or downright impossible) to modify the Android base system they created. Because if you can, anyone or anything which obtains root access can. This is a serious security risk, because if it's malware which puts itself on the system partition and locks up your phone, the only way around this is to wipe your entire device and restore a stock ROM using PC Companion or Flashtool. Of course, they have their own proprietary software to protect as well, but security is the main objective here. The really sensitive bits are stored in the TA partition as I explained earlier.
Sony (-Ericsson) had a service called RIC, which in time moved partially in to a kernel feature. What it does is monitor if system is remounted writeable. This usually is a situation you want to avoid at all costs so RIC will deny you permission, cause a kernel panic OR simply reboots your device to get out of that state.
"Remount-Reboot fix", RICKiller, RICDefeat, and XZDualRecovery all (attempt to) disable this service or stop the kernel from acting on a remount of system.
Hard-bricks, Soft-bricks, bootloops??
They are simple to understand, really:
Hard-brick, TYPICALLY NOT RECOVERABLE: The bootloader stopped functioning, this can be caused by a bad flash/update or by restoring the wrong TA backup.
Soft-Brick, ALWAYS RECOVERABLE: the system partition is corrupted or just simply empty, this causes the device to stall at boot. A soft-brick can also make the screen remain off, because of a bad or missing kernel image.
Bootloops, ALWAYS RECOVERABLE: If the system gets powered up and then reboots during the start. This can be at the kernel splash screen or during the boot animation.
In case of a Soft-brick or Bootloop:
Use the installed recovery (if it still works), PC Companion, QuickIMG or Flashtool to restore your device to working order.
In case of a Hard-brick:
You can never recover from that state without physically opening your device and do some heavy duty engineering (JTagging) on it to flash back the correct bootloader/TA (read that link to see what it would take!). This is way too difficult for 98% of the community, which means that hard-bricking your device is typically the creation of a very expensive paper weight.
Please, be extremely careful when dealing with the TA partition.
*********************************************
I will be updating the above text for sure, if you feel anything is missing, please write a post in this thread with the text you wish to include. I want this to be a community driven guide and I know a lot, but I can't know everything
*********************************************
Extended the text some more to include ideas from:
@Klaos3000
@Yenkazu
Thanks for the suggestions/additions guys! :highfive:

As it concern the recovery, i think you can create a partition with EMMA.
Sent from Greece

kos25k said:
As it concern the recovery, i think you can create a partition with EMMA.
Sent from Greece
Click to expand...
Click to collapse
Please, re-read the first part...

Can I root my iPhone 6 with this guide?
That was a bad joke.
Very useful guide. We should probably educate people around here about what an unlocked bootloader actually means and what it let us do. I'm shocked by the number of people using Kingroot and other risky closed-sourced tools, especially the ones with an unlocked bootloader.
People of earth, if your bootloader is unlocked, it means that your device will be much like a Nexus device when it comes to rooting, sans the recovery partition, so that's why we flash or hotboot a custom kernel with a recovery, by using fastboot. If you're afraid of a terminal and commands, then you can use a tool like QuickIMG. After that, you simply flash SuperSU. That's it!

You can add something about TA Partition and RIC server. :3
Good thread btw

Yenkazu said:
You can add something about TA Partition and RIC server. :3
Good thread btw
Click to expand...
Click to collapse
I'd say, give me a piece of text on the subject for the OP and I'll include it :good:

[NUT] said:
I'd say, give me a piece of text on the subject for the OP and I'll include it :good:
Click to expand...
Click to collapse
RIC, from your thread :3
http://forum.xda-developers.com/xpe...b-definitive-root-remount-reboot-fix-t2317432
But, it's kinda useless if people already use your DualRec, since it's already integrated xD
But more info didn't hurt (?)
TA Partition
http://forum.xda-developers.com/xperia-z/help/ta-partition-t2451186
Not really details, but user should know the impact of unlocking bootloader

Updated the OP to include info on the TA partition and RIC protection. Also included a part of the post by @Klaos3000, because it contained some useful info
Thanks guys :highfive:

Very usefull! :good: But for me 2-3 Weeks to late. I'm still quite new on Z3C and I collect all those info the old style
Without this thread you would need days to catch all dependencies - With this you would need approx. 10 min!
Very helpfull and good to link new user to...
And yes - I came form the Sammy side (of the moon ) and was a bit shocked what sony did with "open source android".
Not because of SystemUI ( I love it...) but because of all this "anti modding" stuff they build in.
Sticky? Sure - must be!

Updated the OP to include info on Hard-bricks, Soft-bricks and bootloops.

Please people, if you have anything to add to the OP, let me know!
As I said, I know a lot, but I can't know everything there is to know about Sony devices...

Good work (...as usual from your side) :good:
Very useful tutorial.
No need to write long explanations to Sony beginners anymore - just add a link from here.

Really Helpful
Brilliant.....Really it deserves place at (Sticky Threads).I think if you add minimum One Custom Kernel(for stock firmware)
of every devices..That would b very helpful to recover from Soft bricks.Then this thread will be an "ALL IN 1" thread.Its my Opinion after all...Brilliant work.

Need a little advice.
Hi,
I have a ZL with Locked bootloader and your ZL-lockeddualrecovery2.8.22 installed
I am on stock 5.0.2 now Rooted thanks to your awesome recovery.
Question is now I have your dual recovery would I be able to simply flash crDroid CM zip Thread Here and others like it or would I still need to unlock the bootloader Edit OP of ROM says it is required
So if I flashed the above would it replace your recovery with the boot.img in the zip
Sorry for the noob questions but I am new to Sony devices and still taking baby steps with this phone
I can unlock the bootloader no problem but I am more concerned about your recovery been replaced.
Thanks in advance :good:

bigrammy said:
Hi,
I have a ZL with Locked bootloader and your ZL-lockeddualrecovery2.8.22 installed
I am on stock 5.0.2 now Rooted thanks to your awesome recovery.
Question is now I have your dual recovery would I be able to simply flash crDroid CM zip Thread Here and others like it or would I still need to unlock the bootloader Edit OP of ROM says it is required
So if I flashed the above would it replace your recovery with the boot.img in the zip
Sorry for the noob questions but I am new to Sony devices and still taking baby steps with this phone
I can unlock the bootloader no problem but I am more concerned about your recovery been replaced.
Thanks in advance :good:
Click to expand...
Click to collapse
As long as your phone is locked, you only can flash stockroms and stock-kernels.
You also have to use recovery for stockrom, because you kernel is "untouchable" and recovery have to put in /data and /system partition and can't be put in kernel.
All other roms/kernels will end in errors while flashing.
If you have unlocked your BL, you can flash any rom and kernel you want, as long as your phone is supporting it.
Yes, by flashing a zip, your kernel will be replaced and in most cases they have a recovery in it.
By flashing a rom from another version or changing from stock-based roms to i.e. CM-roms or Omni and vice versa, you have to unpack the kernel (boot.img) by hand and flash (fastboot) this first, before you flash (after a reboot in recovery) the whole zip.
Otherwise it could end in bootloop.
Because of (i most cases) wiping /system, /data while installation, your stock-recovery will deleted too. This depends of the work of the installer in the zip file.
Btw... before unlocking your phone, backup your TA ( with FlashTool). This TA is unique and you may use it to lock your phone again later.
And... if your phone is unlocked - no fear of losing recovery. You always can flash another one with fastboot again.
Someone correct me, if i was wrong or forgot something.

@bigrammi, you can always try yo repack the CM kernel using my kernel builder, that way you will still have XZDualRecovery but then included in the boot image, so no risk of losing it...

akkufix said:
As long as your phone is locked, you only can flash stockroms and stock-kernels.
You also have to use recovery for stockrom, because you kernel is "untouchable" and recovery have to put in /data and /system partition and can't be put in kernel.
All other roms/kernels will end in errors while flashing.
If you have unlocked your BL, you can flash any rom and kernel you want, as long as your phone is supporting it.
Yes, by flashing a zip, your kernel will be replaced and in most cases they have a recovery in it.
By flashing a rom from another version or changing from stock-based roms to i.e. CM-roms or Omni and vice versa, you have to unpack the kernel (boot.img) by hand and flash (fastboot) this first, before you flash (after a reboot in recovery) the whole zip.
Otherwise it could end in bootloop.
Because of (i most cases) wiping /system, /data while installation, your stock-recovery will deleted too. This depends of the work of the installer in the zip file.
Btw... before unlocking your phone, backup your TA ( with FlashTool). This TA is unique and you may use it to lock your phone again later.
And... if your phone is unlocked - no fear of losing recovery. You always can flash another one with fastboot again.
Someone correct me, if i was wrong or forgot something.
Click to expand...
Click to collapse
Thanks yet again bro :highfive:
Wow these Sony Xperia's take some figuring out :laugh:
I think I have just about got my head around it all now
I have managed to get the TA backed up with TWRP and Flashtool so I should be safe now
I will have to unlock the bootloader just to stop it nagging me to upgrade :laugh:
@Nut Thanks bro I will take a look at your suggestion it's a little more complicated than what I am used to or should I say different.

bigrammy said:
[...]
@Nut Thanks bro I will take a look at your suggestion it's a little more complicated than what I am used to or should I say different.
Click to expand...
Click to collapse
Well, i saw HTC M7 in your signature. If you were able to unlocked, s-off-ed, re-flashed firmware and rooted this beast - you don't need to have any fear about a Sony device.

[NUT] said:
@bigrammymi, you can always try yo repack the CM kernel using my kernel builder, that way you will still have XZDualRecovery but then included in the boot image, so no risk of losing it...
Click to expand...
Click to collapse
Hi @Nut,
I thought I would take your advice and expected to download a tool to unpack everything and pick through the files and start editing init.rc etc etc :silly:
I had no idea this was a fully automated Online tool
I still can't quite believe it you're a genius!! :angel:
A BIG THANKS to All the Xperia dev's helpful community members and especially the tool creators XZDualRecovery, Flashtool, XperiFirm and PRFCreator etc you're all Awesome :highfive:
I fear I will become lazy with such great dev's :laugh:

bigrammy said:
Hi @Nut,
I thought I would take your advice and expected to download a tool to unpack everything and pick through the files and start editing init.rc etc etc :silly:
I had no idea this was a fully automated Online tool
I still can't quite believe it you're a genius!! :angel:
A BIG THANKS to All the Xperia dev's helpful community members and especially the tool creators XZDualRecovery, Flashtool, XperiFirm and PRFCreator etc you're all Awesome :highfive:
I fear I will become lazy with such great dev's :laugh:
Click to expand...
Click to collapse
Thanks, glad to have been of help to you