Database Users

[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.

[F31xx][F32xx][Guide][MM] How to root your Xperia XA (as noob friendly as possible)

Hi all,
I'm happy to share with you an updated guide on how to root the Xperia XA and Ultra, big thanks to @luis1981 for the update.
This guide is Only for Marshmallow (Android 6.0), for Nougat (Android 7.0) it's here: https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3638727
## How to root the Sony Xperia XA
The Sony Xperia XA is a midrange smartphone with a bezeless design. It has adequate specs and run Android aptly. These aspects make this phone a great daily driver, however the Sony stock Android is plagued with trashware and all the hurdles Android itself has several privacy problems.
By rooting the phone one can circumvent these limitations. You will be able to install the Xposed framework, improve sound with Viper4Android, block hosts, install dns-crypt and improve overall customability. In the follwing sections I will present the steps to root your phone.
But before proceeding a word of caution (or why you wouldn't like to root your phone):
1. Unlocking your BootLoader will void your warranty, break your device DRM and lose X-Reality and image optimisation on low light when taking pictures, I found a workaround here: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672, use zip for Z3+ devices.
2. You can save your DRM keys (TA backup) by following this guide: http://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236. You have to do it BEFORE unlocking the bootloader, for now you can't restore your backup.
3. You can re-lock your phone but it will not restore DRM
4. Unlocking your bootloader will wipe the device (factory reset)
5. If you have confidential files in your phone don't unlock your bootloader, as long as your phone is locked your data are officially secured.
## Method
1. Find out whether if you bootloader is unlocked, which is needed to proceed. Type: *#*#7378423#*#* then choose Service info ---> Configuration ---> Check for "Bootloader unlock allowed: Yes". At this point if the phone has No or any other answer at the screen you shouldn't porceed as rooting will be impossible.
2. Download XA ADB and Fastboot drivers: https://developer.sonymobile.com/downloads/drivers/
3. Download FLASHTOOL with integrated Xperifirm 0.9.22.3 for Windows, note that you can also use it to unlock your bootloader(http://www.flashtool.net/downloads_windows.php)
4. Follow the official Sony instructions for getting the unlock code from [here](https://developer.sonymobile.com/unlockbootloader/). Further paste the code in BLU menu of Flashtool. You can also find video instructions [here](https://www.youtube.com/watch?v=6lKWd5LlUoA).
5. Root Your Stock Rom with TWRP and in order to do that you will need the proper files for your phone version:
SuperSu zip package for all XA: http://www.supersu.com/download
For XA single sim = F3111, F3113, F3115
TWRP recovery: https://forum.xda-developers.com/xperia-xa/development/f3111-f3113-f3115-twrp-recovery-xa-t3606488
Boot: https://forum.xda-developers.com/xp...3111-f3113-f3115-stock-kernels-built-t3573119
For XA dual sim = F3112,F3116
TWRP recovery: https://forum.xda-developers.com/xp...3112-f3116-twrp-recovery-xa-dual-sim-t3606232
Boot: https://forum.xda-developers.com/xp...12-f3116-stock-kernels-built-sources-t3526496
6. Copy SuperSu zip package on your MicroSD.
7. Enter the phone in Fastboot mode (when power off, hold Vol+ and plug the phone). The led should be blue.
8. Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands (rename downloaded boot/recovery image if needed). The simplest way is to use fastboot from Flashtool in x10flasher folder, copy recovery and boot in it, open command prompt, flash them and then delete them.
9. Unplug the phone, hold "Vol-" and "Power" buttons. Release all buttons after phone vibrate.
10. You are in TWRP recovery, on password prompt press "Cancel"
11. On next screen press "Swipe to allow".
12. Go to "Install", "Select Storage", click "Micro SDCard". Optionally, you can format "userdata" partition now and remove internal encrytion for restoring TWRP backups/acces of /data partition, go to "wipe" and tap "format data".
13. Go to your SuperSu zip directory and click on it to install. Optionally, If you want to flash Xposed, DRM fix or any flashable zip, repeat the previous step for each zip. You can mount your SD to PC in TWRP for easy access.
14. Reboot the phone, during init the phone will reboot one more time.
15. Your phone is rooted
You can optionally switch from SuperSu to Magisk by following this guide:
https://forum.xda-developers.com/xperia-xa/how-to/guide-how-to-install-magisk-xperia-xa-t3555911
## Conclusion
After these steps your phone should be rooted and you will be able to have root access to the system. This tutorial comes with no garanties that it will work and the author does not take any responsibility for you bricking your device. Also, installing third party files are a security liability, you should be aware of that. Despite these issues, rooting the Xperia XA has been confirmed to work in all models.
Note that this the guide is the same for XA Ultra, the only differences are the boot/recovery files. You can find files for XA Ultra in their respective forums.
## Old guide with video
Hi all
As requested I make a "how to" video to be more noob friendly, the video is probably not perfect and my English too but I do my best to be understandable to all
PLEASE READ
I'm not a dev and I have no responsability if you flash my files.
As said in the video you must wipe "userdata" partition when flashing IF your phone memory IS crypted or if you don't know the uncrypt password, someone on the web speak of "default password" but what is it ?? If cryped (with no password) you can't backup /data and can't mount internal memory in TWRP. You can manually enable encryption and be able to set YOUR OWN password, but you can't revert back. And in theory you can make full nandroid backup and mount /data partition when in TWRP but can't mount inernal memory.
Regarding mounting /system rw in TWRP, seen on other tuto, you must never "swipe to allow modification" when prompted, after installing root package /system is mounted rw with no problem (look at "mount" menu). EDIT: tested on my device without issues but be careful.
IF YOU UPDATE OR FLASH STOCK BOOT and power on the device to Android, it will encrypt again the internal memory and if you shutdown the device before the end (xperia screen for hours) it will corrupt your data, not the SD card).
For futur, if you want to update, ask me and will release modified boot. I don't know what it does if you update stock after setting password encryption :/
Why I changed that by replacing "FORCENCRYPT" by "ENCRYPTABLE" in fstab Boot:
http://arstechnica.com/gadgets/2015...-mandatory-device-encryption-for-new-devices/
and
http://www.androidcentral.com/inside-marshmallow-adoptable-storage
Before continue, you must understand that unlocking your BootLoader will void your warranty, break your device DRM and lose X-Reality and image optimisation on low light when taking pictures (seen some workaround but not for XA).
You can't re-lock your phone and it will not restore DRM.
If you have confidentials files in your phone don't unlock your bootloader, as long as your phone is locked your data are officially secured.
This will be repeated when following Sony step by step guide. YOU ARE AWARE !
To verify bootloader lock state after unlock, on phone dialer:
*#*#7378423#*#* ---> Service info ---> Configuration ---> Check for "Bootloader unlocked: Yes" IT MUST BE YES !!!
By rooting your phone you will be able to install/uninstall system apps, install Xposed framework (Gravity Box, Dark Pokemon Go,...) or Viper4Android for an awesome sound! You can tweak and mod your phone deeper (battery,CPU,...), build and flash custom ROMs and many other things
If you have problems or want to unroot you can flash stock firmware like in the video with Flashtool, no need to wipe userdata.
Please watch my video one time before begin, to understand what you have to do.
Free to you to distribute or modify my files but please link this thread as source.
BY FOLLOWING THIS GUIDE YOUR PHONE WILL PERFORM A FACTORY RESET WHEN UNLOCKING BL ( it will not format SD card) , MAKE BACKUPS !
Edit 3/08/2016: Found a workaround for Sony DRM function restoration for UB devices based on Z line and working on XA Please read the thread, download package zip for Xperia Z3+ and install it with TWRP, that's all! I recommend you to install it just after SuperSU zip package (working too if not doing this). Thanks to @jimRnor
http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
EDIT 13/08/2016: TWRP is 99% working (can't wipe /cache), you can do all as you want, as long as no encrypted partition is present or locked.
Let's begin!
YOU NEED:
My first video guide : http://www.youtube.com/watch?v=nnOoLo31ka0
MP4 offline video download: https://mega.nz/#!RlwVSAKC!6lTBZxVnLQ-Mxz8er0_dg1r36dCNnUWIq8lEUfSp4Zw
Download XA ADB drivers, all models for Windows
http://dl-developer.sonymobile.com/drivers/Xperia_XA_driver.zip
Download XA Fastboot drivers, all models for Windows (if needed, installation is same as ADB drivers in video)
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Download FLASHTOOL with integrated Xperifirm 0.9.22.3 for Windows
http://www.flashtool.net/downloads_windows.php
(if needed you can unlock bootloader with it, I unlocked my device with it)
Just follow official way and when you get the unlock code, paste it in BLU menu of Flashtool. (faster way)
The step by step guide to unlock BootLoader by official way:
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Video (not mine): https://www.youtube.com/watch?v=6lKWd5LlUoA
(Just select Xperia XA when asked)
Now depending the firmware you want to root ( the one you downloaded with Xperifirm) choose your rootpack:
For XA single sim (33.2.A.x.xx) = F3111, F3113, F3115
33.2.A.x.x: https://mega.nz/#!ZsQhwbTC!rvw437H0ZujR5Ic02Rhlap6fQ4sLLyPmSRjyfZlMFiU
For XA dual sim (33.2.B.x.xx) = F3112,F3116
33.2.B.x.x: https://mega.nz/#!xgoXxBTa!DKAwKELVs0UvkZN0X53ZVM7I4U_XnCgG73RswzMPUi0
EDIT 29/11:
I see some users who ask without searching (a very little) before, PM messages inclued, some others who spam threads not related to their problem or create new thread for nothing and who do not know what politeness is at all . Until now I was nice and answered them but now I will change that, NO MORE HELP FOR THAT KIND OF USER !!!
Now if you have no answer from me you will know why.
Good luck

Many thanks for the effort mate. Will try it.
Btw, what is the bug with google store and user data, right after root.
edit
01/039/2016 11:39:08 - ERROR - Processing of boot.sin finished with errors. As u said data wipe is needed when unlocking the bl, but i have my BL unlocked earlier without data wiped...so i started the flash method ,on my old version of flashtool.Now i have the newest version, so got to try it...or i should skip the flash and go to root step...
edit2
01/006/2016 13:06:39 - INFO - Ending flash session
01/006/2016 13:06:39 - INFO - Flashing finished.
For this phone use the newest version of flashtool.
Edit3: I need to enter some kind of password on boot menu.Now what ?

rrvuhpg said:
Hi all
As requested I make a "how to" video to be more noob friendly, the video is probably not perfect and my English too but I do my best to be understandable to all
PLEASE READ
I'm not a dev and I have no responsability if you flash my files.
As said in the video you must wipe "userdata" partition when flashing IF your phone memory IS crypted or if you don't know the uncrypt password, someone on the web speak of "default password" but what is it ?? If cryped (with no password) you can't backup /data and can't mount internal memory in TWRP. You can manually enable encryption and be able to set YOUR OWN password, but you can't revert back. And in theory you can make full nandroid backup and mount /data partition when in TWRP but can't mount inernal memory.
Regarding mounting /system rw in TWRP, seen on other tuto, you must never "swipe to allow modification" when prompted, after installing root package /system is mounted rw with no problem (look at "mount" menu).
IF YOU UPDATE OR FLASH STOCK BOOT and power on the device to Android, it will encrypt again the internal memory and if you shutdown the device before the end (xperia screen for hours) it will corrupt your data, not the SD card).
For futur, if you want to update, ask me and will release modified boot. I don't know what it does if you update stock after setting password encryption :/
Why I changed that by replacing "FORCENCRYPT" by "ENCRYPTABLE" in fstab Boot:
http://arstechnica.com/gadgets/2015...-mandatory-device-encryption-for-new-devices/
and
http://www.androidcentral.com/inside-marshmallow-adoptable-storage
Before continue, you must understand that unlocking your BootLoader will void your warranty, break your device DRM and lose X-Reality and image optimisation on low light when taking pictures (seen some workaround but not for XA).
You can't re-lock your phone and it will not restore DRM.
If you have confidentials files in your phone don't unlock your bootloader, as long as your phone is locked your data are officially secured.
This will be repeated when following Sony step by step guide. YOU ARE AWARE !
To verify bootloader lock state after unlock, on phone dialer:
*#*#7378423#*#* ---> Service info ---> Configuration ---> Check for "Bootloader unlocked: Yes" IT MUST BE YES !!!
By rooting your phone you will be able to install/uninstall system apps, install Xposed framework (Gravity Box, Dark Pokemon Go,...) or Viper4Android for an awesome sound! You can tweak and mod your phone deeper (battery,CPU,...), build and flash custom ROMs and many other things
If you have problems or want to unroot you can flash stock firmware like in the video with Flashtool, no need to wipe userdata.
Please watch my video one time before begin, to understand what you have to do.
Free to you to distribute or modify my files but please link this thread as source.
BY FOLLOWING THIS GUIDE YOUR PHONE WILL PERFORM A FACTORY RESET WHEN UNLOCKING BL ( it will not format SD card) , MAKE BACKUPS !
Tested on my device F3112 and reported as working on F3116, other models may work as well if you do ALL steps. Will confirm after positive feedbacks.
Let's begin!
YOU NEED:
My first video guide (will be on youtube after validation) : https://mega.nz/#!RlwVSAKC!6lTBZxVnLQ-Mxz8er0_dg1r36dCNnUWIq8lEUfSp4Zw
Download XA ADB drivers, all models for Windows
http://dl-developer.sonymobile.com/drivers/Xperia_XA_driver.zip
Download XA Fastboot drivers, all models for Windows (if needed, installation is same as ADB drivers in video)
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Download FLASHTOOL with integrated Xperifirm 0.9.22.3 for Windows
http://www.flashtool.net/downloads_windows.php
(if needed you can unlock bootloader with it, I unlocked my device with it)
Just follow official way and when you get the unlock code, paste it in UB menu of Flashtool. (faster way)
The step by step guide to unlock BootLoader by official way:
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Video (not mine): https://www.youtube.com/watch?v=6lKWd5LlUoA
(Just select Xperia XA when asked)
Now depending the firmware you want to root ( the one you downloaded with Xperifirm) choose your rootpack:
For XA single sim (33.2.A.2.xx) = F3111, F3113, F3115
33.2.A.2.73: https://mega.nz/#!ZsQhwbTC!rvw437H0ZujR5Ic02Rhlap6fQ4sLLyPmSRjyfZlMFiU (NOT TESTED)
For XA dual sim (33.2.B.2.xx) = F3112,F3116
33.2.B.2.35: https://mega.nz/#!5lZFhapC!SrYt1HmOICEyMh2Afl2EUn4nY0bRwL-Pd1f0Bpkireg
33.2.B.2.73: https://mega.nz/#!xgoXxBTa!DKAwKELVs0UvkZN0X53ZVM7I4U_XnCgG73RswzMPUi0
Good luck
Click to expand...
Click to collapse
Will this work with F3116 running 33.2.B.2.66 firmware?

@hp6830s you talk about bugs seen in video? If I remember, error in TWRP is about wiping /cache but no a real problem and in video got 2 force close of Play service because I'm updated from .35 without wiping userdata (not crypted /data) and I think update wasn't fully finished. Never FC again after that and no problems. But if YOU have errors about /data in TWRP it's because of encrypted phone memory. During tests I got 1 bootloop in TWRP but can't repeat the problem again after wiped userdata on first root. That's why I recommend wipe. And that's strange if your phone not wiped when unlocked, for me no choice...
@tthmatt It works but really not recommended (for boot.img), as ramdisk and kernel are from an other firmware. For recovery it's less problematic. You can try and feedback us

Ok ,how to remove phone encyption on boot menu ,so i can install custom user ?

hp6830s said:
Many thanks for the effort mate. Will try it.
Btw, what is the bug with google store and user data, right after root.
edit
01/039/2016 11:39:08 - ERROR - Processing of boot.sin finished with errors. As u said data wipe is needed when unlocking the bl, but i have my BL unlocked earlier without data wiped...so i started the flash method ,on my old version of flashtool.Now i have the newest version, so got to try it...or i should skip the flash and go to root step...
edit2
01/006/2016 13:06:39 - INFO - Ending flash session
01/006/2016 13:06:39 - INFO - Flashing finished.
For this phone use the newest version of flashtool.
Edit3: I need to enter some kind of password on boot menu.Now what ?
Click to expand...
Click to collapse
I don't know the password to enter, seem to be randomly generated on first init by phone or a unknown default password is set. That's why you have to wipe userdata and after if you want you can recrypt phone in security menu and set your own password to use in TWRP. Have you seen a password in my video?? As said before I'm not a dev and my help is limited, my step by step guide is working, confirmed on F3116 and tested many times on my device. But if you want to not follow all steps you can but you will probably have problems. I said to use 0.9.22.3 Flashtool since first days, you use an older one and have problem. I said to flash and root and you want to root directly. I said to wipe and you don't do it... and finally problem again. Please follow ALL steps as described and at end if you have problems I will help you. If you want to continue with experimental way, just click Cancel on password prompt, on next screen don't swipe to allow modification, press "keep read only". At end if you have a recovery bootloop or corrupted userdata, don't ask why I don't want to say that my way is the only one but for now it's the working one (if you follow it carefully)

I didnt said - not following your guide. I did every step, as soon i discovered error on flashing (from the older version). But i did wipe everything, now my phone is empty. Yet it asks for password in order to install superUser, do i need to perform factory reset from recovery menu ?
edit: Wipe/ Factory - OK. FORMAT - YES...and password should be gone.
edit2: phone is rooted, and installing apps.

hp6830s said:
I didnt said - not following your guide. I did every step, as soon i discovered error on flashing (from the older version). But i did wipe everything, now my phone is empty. Yet it asks for password in order to install superUser, do i need to perform factory reset from recovery menu ?
Click to expand...
Click to collapse
Flash full stock firmware with Flashtool and check "userdata" in "wipe" column as in the video (don't wipe/factory reset from Android) , JUST AFTER flash boot.img and recovery.img with Fastboot (don't boot android before that) . Boot to Android to verify and set up your phone, when finished reboot to TWRP to install UpdateSuperSU.zip No passwords needed if followed that, if you defined pin/password for lockscreen or to start phone, try it. Or don't set any password before the end of root process. I don't understand why it ask for a password

Its all set.Battery seem more stable now...but cant find some of diagnostics tools in About Phone, like battery optimization (but i use greenify now) and move apps to SD card wizzard.
Do i need to create backup from flashtool / boot ?

hp6830s said:
Its all set.Battery seem more stable now...but cant find some of diagnostics tools in About Phone, like battery optimization (but i use greenify now) and move apps to SD card wizzard.
Do i need to create backup from flashtool / boot ?
Click to expand...
Click to collapse
You finally successfully rooted your phone :good:
You can find battery optimization in "settings " --> "battery". You can't move apps on external SD since a looong time (or with workaround) , just pictures, videos, music ????
For that go "settings" --> "storage and memory".
Android 6 have a new feature "Adoptable Storage" to integrate external SD as phone memory like "ARCHOS Storage Fusion" (but it encrypt SD and is no more readable on PC with USB readers, disable acces to internal memory, not good if you break your phone) but seem to not be present in our firmwares. Next challenge is to enable feature and make encryption as a choice for user.
And for your last question I recommend you make full backup with TWRP, by this way you can backup all partitions. Not sure if it works for XA with Flashtool.

rrvuhpg said:
You finally successfully rooted your phone :good:
And for your last question I recommend you make full backup with TWRP, by this way you can backup all partitions. Not sure if it works for XA with Flashtool.
Click to expand...
Click to collapse
thx ,but i cant backup, my m card is less than 8 gb (8.2 gb backup img) so i have to wait till my 16 gb card arrives.i
btw what is Xposed framework , Viper4Android. And how to tweek my battery settings more deeper...or greenify hibernate its fine.

hp6830s said:
btw what is Xposed framework , Viper4Android. And how to tweek my battery settings more deeper...or greenify hibernate its fine.
Click to expand...
Click to collapse
Google is your friend ????
http://www.howtogeek.com/195476/7-t...ramework-on-a-rooted-android-phone-or-tablet/
http://forum.xda-developers.com/showthread.php?t=2191223
I will make a guide for installing Xposed and Viper4Android with all working packages for XA.

Yippee-ki-yay! DRM keys are back! Noice reduction and screen optimizations are working again. Used DRM fix found on XDA. Look screens of DRM keys state and the time stamps. Verified with comparative pictures/screenshots :fingers-crossed:
Link to the fix: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Use zip for Z3+

rrvuhpg said:
Yippee-ki-yay! DRM keys are back! Noice reduction and screen optimizations are working again. Used DRM fix found on XDA. Look screens of DRM keys state and the time stamps. Verified with comparative pictures/screenshots :fingers-crossed:
Link to the fix: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
Use zip for Z3+
Click to expand...
Click to collapse
There not really back there still gone for good, know idea how he does it, but it fools/emulates the keys tricking the Sony software into reactivating the Bravia engine+x-reality+camera imaging/low light algorithms. Good to know that there are two ways to do it now though. If I can be bothered I need to try this ivyroot tool for backing up your drm keys before unlocking the Bootloader. Until I know I can back up the keys I won't be unlocking the Bootloader.
Sent from my Xperia XA using XDA Labs

aidy.lucas said:
There not really back there still gone for good, know idea how he does it, but it fools/emulates the keys tricking the Sony software into reactivating the Bravia engine+x-reality+camera imaging/low light algorithms. Good to know that there are two ways to do it now though. If I can be bothered I need to try this ivyroot tool for backing up your drm keys before unlocking the Bootloader. Until I know I can back up the keys I won't be unlocking the Bootloader.
Click to expand...
Click to collapse
iovyroot seem to use a security exploit in LP (kernels before Dec 2015) but patched in MM (or missed the news) and no LP firmware for XA to flash, next exploit for MM can take months or more to come... But I can understand your opinion, the choice is difficult, root or warranty. For me rooting my phones is not optional, when you used custom ROMs, Xposed, Viper4Android, Lucky Patcher and GameKiller one time you can't stay without them after and say f**k to the warranty . If we talk about Xperia X I'm fully OK with you as it cost $$$ and will try to preserve the warranty.
EDIT: The fix is really good, ALL is working again (backup with Xperia PC Compagnon too) and very interesting thing it can show my REAL warranty date in Xperia Care as before. That's strange ...

Looking forsome help
Umm I got the boot loader unlock code. From sony on there web sit, I am new to this. But do I have to flash the phone if my bootloader is unlocked?? I don't want to mess it up I just got it and payed full price i rooted my other phones easy I just am new to android 6

just check XFirmware and xxx.73 version is only available in Brazil
should I tried it?
my version is customizedVN :crying:

Willismetal said:
Umm I got the boot loader unlock code. From sony on there web sit, I am new to this. But do I have to flash the phone if my bootloader is unlocked?? I don't want to mess it up I just got it and payed full price i rooted my other phones easy I just am new to android 6
Click to expand...
Click to collapse
You can test, don't worry about phone brick as long as you don't play with preloader, in Flashtool stay in "normal" mode. I hard bricked XA many times during my private tests (no screen, no sound, only charging led) and always unbricked Mtk are strong for that.
@caosugai you can flash without problem but don't know if it's good for daily use. Tested .66 TW on .35 FR before . 73 out for France, but for test only.
Look here for more:
http://techbeasts.com/how-to-download-sony-xperia-official-firmware-and-create-ftf-file/

Think i lost access to my personal prediction settings, the one that pinpoints my email when entering on login screens over the apps /web ( for example on typing Us3r ,the texting app predicts my mail : [email protected] ,so i dont need typing the whole email over and over )

rrvuhpg said:
You can test, don't worry about phone brick as long as you don't play with preloader, in Flashtool stay in "normal" mode. I hard bricked XA many times during my private tests (no screen, no sound, only charging led) and always unbricked Mtk are strong for that.
@caosugai you can flash without problem but don't know if it's good for daily use. Tested .66 TW on .35 FR before . 73 out for France, but for test only.
Look here for more:
http://techbeasts.com/how-to-download-sony-xperia-official-firmware-and-create-ftf-file/
Click to expand...
Click to collapse
then it's a soft brick not a hard brick. A hard bricked Xperia is irreversible. Bootloop is always recoverable as is a device with only led response when connected to USB and if it does nothing on connection to USB and pc doesn't recognize the device it's a paperweight, that's what I learnt when I first got into rooting and modding my old m2 device.
Sent from my Xperia XA using XDA Labs
---------- Post added at 04:12 PM ---------- Previous post was at 04:05 PM ----------
hp6830s said:
Think i lost access to my personal prediction settings, the one that pinpoints my email when entering on login screens over the apps /web ( for example on typing Us3r ,the texting app predicts my mail : [email protected] ,so i dont need typing the whole email over and over )
Click to expand...
Click to collapse
Mines the same or at least it was earlier on not bringing up email address when logging on to pretty much anything, maybe it's something to do with this SwiftKey thing going off where it predicts someone else's email address and stored words. Maybe it's turned off at there end while sorting the issue out.
Sent from my Xperia XA using XDA Labs

Help me to twrp/root/xposed/kernel my XC

Hi,
I'll received my XC this week, and I'd like to root it.
I don't want a custom ROM, but just a stock one with xposed and remove some bloatwares.
Here are my needs:
keep DRM
latest stock rom
twrp
untouched system partition
easy OTA
XC Genesis kernel
xposed + module
Do you think it possible to achieve such a configuration?
How-to?
Thanks
EDIT: I'll update this post to make it an HOW-To for futures users with same questions.

Assuming you're unable to unlock your BL the steps are as follows...
Flash back to 198.
Backup your TA.
Unlock your BL
Update to 311
Extract kernel - ftf/sin/elf
Run elf through Rootkernel_v5.23 - (In cmd prompt window - rootkernel kernel.elf boot.img)
Create DK ftf with Rootkernel_v5.23 (In cmd prompt window - flash_dk TA-19022017.img DK.ftf)
Flash new boot.img
Flash TWRP.img
Flash Super User zip
Flash DK.ftf with Flashtool 9.22
...and that should be it.

Latest stock Rom + xposed will not be possible...

mika91 said:
Hi,
I'll received my XC this week, and I'd like to root it.
I don't want a custom ROM, but just a stock one with xposed and remove some bloatwares.
Here are my needs:
keep DRM
latest stock rom
twrp
untouched system partition
easy OTA
XC Genesis kernel
xposed + module
Do you think it possible to achieve such a configuration?
How-to?
Thanks
EDIT: I'll update this post to make it an HOW-To for futures users with same questions.
Click to expand...
Click to collapse
Forget about OTA when rooted...

I though that using xposed leave the system partition untouched, so OTA updates are possible...

mika91 said:
I though that using xposed leave the system partition untouched, so OTA updates are possible...
Click to expand...
Click to collapse
OTA is not possible once bootloader is unlocked. System partition touched or not played no role.

ok.
So if I want root the XC, I have to unlock the bootloader, loose DRM and ota?
How is the camera quality without the drm keys?
Thanks

mika91 said:
ok.
So if I want root the XC, I have to unlock the bootloader, loose DRM and ota?
Click to expand...
Click to collapse
See my post to get a rooted stock with DRM.

mika91 said:
ok.
So if I want root the XC, I have to unlock the bootloader, loose DRM and ota?
How is the camera quality without the drm keys?
Thanks
Click to expand...
Click to collapse
You HAVE to unlock. There is NO root on LOCKED bootloader.
Unlocking bootloader deletes TA partition, containing DRM keys. You should BACKUP your TA partition BEFORE unlocking using DirtyCow Backup tool from Sony Cross Devices forum.
After unlocking, you can either flash kernel that supports DRM patching either by using fake DRM libraries, or your real DRM keys, either flashed in alternative location (see RootKernel tool in Z5 forums, works on almost all modern Xperias) or PoC TA tool from Sony Cross devices, that mounts your TA backup as TA partition, therefore your phone looks as having DRM keys and locked.

XperienceD said:
Assuming you're unable to unlock your BL the steps are as follows...
Flash back to 198.
Backup your TA.
[*]Unlock your BL
[*]Update to 311
[*]Extract kernel - ftf/sin/elf
[*]Run elf through Rootkernel_v5.23 - (In cmd prompt window - rootkernel kernel.elf boot.img)
[*]Create DK ftf with Rootkernel_v5.23 (In cmd prompt window - flash_dk TA-19022017.img DK.ftf)
[*]Flash new boot.img
[*]Flash TWRP.img
[*]Flash Super User zip
[*]Flash DK.ftf with Flashtool 9.22
...and that should be it.
Click to expand...
Click to collapse
Would you mind detailing a bit more those steps, especially the first 2? Im coming from a really old phone so im still a bit lost. (where can i learn about ftf/sin/elf?)
How can we flash back to 198? Flashing doesnt require an unlocked BL, wich to be achieved deletes your TA?
im on a brand new X Compact, 7.0 (34.2.A.0.292), secure patch 01/01/17
managed to get flashtool, adb/fastboot and Universal TA Backup v2 on my pc but no dice on TA backup yet

fredsky2 said:
Would you mind detailing a bit more those steps, especially the first 2? Im coming from a really old phone so im still a bit lost. (where can i learn about ftf/sin/elf?)
Click to expand...
Click to collapse
Sure. You don't really need to learn about those stuff but is handy to know, you'll pick stuff up along the way. They are basically firmware files.
fredsky2 said:
How can we flash back to 198? Flashing doesnt require an unlocked BL, wich to be achieved deletes your TA?
Click to expand...
Click to collapse
Open the flashtool and run Xperifirm (icon with XI) on it, then browse to the XC, then click on F5321 and it will load up the different regions and available firmware. If you click on "check all" it will then show which FW is available to download, Central Europe 5 still shows as 198, so you need to select it on the right of the screen under the picture of the phone, it will then download and it's simply a matter of following the instructions to flash it.
fredsky2 said:
im on a brand new X Compact, 7.0 (34.2.A.0.292), secure patch 01/01/17
managed to get flashtool, adb/fastboot and Universal TA Backup v2 on my pc but no dice on TA backup yet
Click to expand...
Click to collapse
When you get 198 on your phone then you'll be able to back your TA. If you get stuck give us a shout.

XperienceD said:
Sure. You don't really need to learn about those stuff but is handy to know, you'll pick stuff up along the way. They are basically firmware files.
Open the flashtool and run Xperifirm (icon with XI) on it, then browse to the XC, then click on F5321 and it will load up the different regions and available firmware. If you click on "check all" it will then show which FW is available to download, Central Europe 5 still shows as 198, so you need to select it on the right of the screen under the picture of the phone, it will then download and it's simply a matter of following the instructions to flash it.
When you get 198 on your phone then you'll be able to back your TA. If you get stuck give us a shout.
Click to expand...
Click to collapse
Thank you, i was able to successfully backup my TA earlier yesterday. But now im struggling with how to restore it in MM 6.0.1 (34.1.A.1.198).
I've read that i'll need a custom kernel for that (and to get TWRP+supersu+magisk+xposed) but im unsure if i should use Genesis (probably unsuported but the only one that says it'll restore MY TA) or Advanced Stock Kernel from Androplus. Ive read that messing with TA can hardbrick my phone so im trying to be extra careful.
atm im following ondrejvaroscak's quickrecap to make sure everything goes smooth with my TA keys and then i plan to downgrade to 6.0, install Advanced Stock Kernel, supersu 2.79 and magisk and then pray for the best (without reflashing my own DK.ftf?)

fredsky2 said:
Thank you, i was able to successfully backup my TA earlier yesterday. But now im struggling with how to restore it in MM 6.0.1 (34.1.A.1.198).
Click to expand...
Click to collapse
Download Flashtool 9.22.3 and flash your DK.ftf, flashing with a newer version doesn't work, you should then be able to verify it's worked in the service menu.
fredsky2 said:
I've read that i'll need a custom kernel for that (and to get TWRP+supersu+magisk+xposed) but im unsure if i should use Genesis (probably unsuported but the only one that says it'll restore MY TA) or Advanced Stock Kernel from Androplus. Ive read that messing with TA can hardbrick my phone so im trying to be extra careful.
Click to expand...
Click to collapse
You can use the RootKernel tool to modify your own kernel, extract the kernel.sin from the ftf with a zip program, then use the flashtool to extract the kernel.elf, Tools-Sin Editor-Extract Data then run it through the RootKernel tool and flash the boot.img it creates, then flash TWRP separately to the recovery partition which will allow you then to flash SuperSU.
SuperSU and BusyBox are the only options I didn't include when creating my kernel. Others will have to help with the other two things you want as I refuse to use them.

XperienceD said:
Download Flashtool 9.22.3 and flash your DK.ftf, flashing with a newer version doesn't work, you should then be able to verify it's worked in the service menu.
You can use the RootKernel tool to modify your own kernel, extract the kernel.sin from the ftf with a zip program, then use the flashtool to extract the kernel.elf, Tools-Sin Editor-Extract Data then run it through the RootKernel tool and flash the boot.img it creates, then flash TWRP separately to the recovery partition which will allow you then to flash SuperSU.
SuperSU and BusyBox are the only options I didn't include when creating my kernel. Others will have to help with the other two things you want as I refuse to use them.
Click to expand...
Click to collapse
Thanks again. I was worried that the drm-fix from the kernel editing tool could corrupt my TA partition but thankfully i was wrong on that .
Im now at MM 6.0, original DRM keys, TWRP, xposed, rooted with magisk and im almost sure that with busybox. Why do you refuse to use them? Just curious!
Thanks a lot for your help, cheers

fredsky2 said:
Thanks again. I was worried that the drm-fix from the kernel editing tool could corrupt my TA partition but thankfully i was wrong on that .
Click to expand...
Click to collapse
I flashed a kernel I made with the Rootkernel tool without the drm fix but it showed some mumbo jumbo where it should say ok and provisioned, included the drm fix in the next one and it worked fine then.
fredsky2 said:
Im now at MM 6.0, original DRM keys, TWRP, xposed, rooted with magisk and im almost sure that with busybox. Why do you refuse to use them? Just curious!
Thanks a lot for your help, cheers
Click to expand...
Click to collapse
You're welcome. I refuse because I prefer to know how to mod apks directly and I found Xposed to be quite buggy. I can see the benefits, it's just not for me.

Z1C: First Custom-ROM

Hello,
my Sony Xperia Z1 Compact has the standard Android 5.1 version of Sony. Now I want to upgrade to a new Android version.
I need it for everyday-use and it should be relatively stable. The camera is not that important, but it should work. I use especially the browser, so the mobile datas should also work. Otherwise it should be only be stable and the battery should not discharge too fast. Is there any good build for me?
That one looks very interesting: AICP 7.1 ROM amami (I can't link the URL, because I am a new user )
Is it okay for a Custom-ROM beginner? I think I will find some instructions and tutorials how to install it. I just have to know if it is a good choice.
If there are any English mistakes, please correct me. I have to improve my English.
Thank you!

Skylac06 said:
Hello,
my Sony Xperia Z1 Compact has the standard Android 5.1 version of Sony. Now I want to upgrade to a new Android version.
I need it for everyday-use and it should be relatively stable. The camera is not that important, but it should work. I use especially the browser, so the mobile datas should also work. Otherwise it should be only be stable and the battery should not discharge too fast. Is there any good build for me?
That one looks very interesting: AICP 7.1 ROM amami (I can't link the URL, because I am a new user )
Is it okay for a Custom-ROM beginner? I think I will find some instructions and tutorials how to install it. I just have to know if it is a good choice.
If there are any English mistakes, please correct me. I have to improve my English.
Thank you!
Click to expand...
Click to collapse
Anything over LP 5.1 has an unusable camera, with one possible exception: DU Marshmallow rom with custom kernel. Read op of this thread - https://forum.xda-developers.com/sony-xperia-z1-compact/general/z1c-marshmallow-roms-t3372565 Note the addenda at the bottom.

levone1 said:
Anything over LP 5.1 has an unusable camera, with one possible exception: DU Marshmallow rom with custom kernel. Read op of this thread - https://forum.xda-developers.com/sony-xperia-z1-compact/general/z1c-marshmallow-roms-t3372565 Note the addenda at the bottom.
Click to expand...
Click to collapse
Thank you for your fast answer.
Is the camera completely unusable or just "not good"? I do not need the best quality, but it should at least work and you should be able to identify what the picture shows.
However, thank you for the link. I think I will try it. Android 6 is, I hope so, an improvement. Maybe I will then upgrade to Nougat.
There are no other options like Ubuntu Touch or Sailfish, right?

Skylac06 said:
Thank you for your fast answer.
Is the camera completely unusable or just "not good"? I do not need the best quality, but it should at least work and you should be able to identify what the picture shows.
However, thank you for the link. I think I will try it. Android 6 is, I hope so, an improvement. Maybe I will then upgrade to Nougat.
There are no other options like Ubuntu Touch or Sailfish, right?
Click to expand...
Click to collapse
Put a piece of tape over your camera lens, and turn off the lights, and shake the phone back and forth while taking a picture... That's what most of the photos will look like.
No Sailfish, and @munjeni has built Ubuntu touch for Z1c, but I couldn't get the Internet to work, (except for Ubuntu store, which downloads apps fine). - https://mega.nz/#!YEpCHLoS!tRxZpJHUSKL_cZz9wisGZvWl7igYAlYJRjwbcT_s868 Besides that, fxp has built Firefox OS, but probably hard to find at this point, and there are a few MIUI builds out there that are very good. Check here - https://forum.xda-developers.com/showpost.php?p=71329395&postcount=5 and here - https://forum.xda-developers.com/so...lopment/23-2015-miui-v6-5-5-22-d5503-t3116494

Hello again,
I decided to try out some Custom-ROMs.
Now I find many different ways how to root my phone and unlock the bootloader. Which way do you here recommend?
And how difficult is going back to the stock ROM and lock the bootloader againg, if nothing works?
Thank you!

Skylac06 said:
Hello again,
I decided to try out some Custom-ROMs.
Now I find many different ways how to root my phone and unlock the bootloader. Which way do you here recommend?
And how difficult is going back to the stock ROM and lock the bootloader againg, if nothing works?
Thank you!
Click to expand...
Click to collapse
Backup TA - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Root and recovery :
Download custom kernel to pc, and extract boot img to ADB directory - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 and download twrp img to ADB directory - https://www.androidfilehost.com/?fid=457095661767147235 then use fastboot commands to flash boot and recovery. Now you have recovery, and you can either flash SuperSU zip, or flash custom rom.
Restore TA - https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893 or use Flashtool relock bl option - http://www.flashtool.net/

levone1 said:
Backup TA - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Root and recovery :
Download custom kernel to pc, and extract boot img to ADB directory - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 and download twrp img to ADB directory - https://www.androidfilehost.com/?fid=457095661767147235 then use fastboot commands to flash boot and recovery. Now you have recovery, and you can either flash SuperSU zip, or flash custom rom.
Restore TA - https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893 or use Flashtool relock bl option - http://www.flashtool.net/
Click to expand...
Click to collapse
One little question: if I unlock my bootloader, my complete internal storage is wiped, right?
But if my bootloader is locked, I can not use the nandroid-backup-function of TWRP, because I can not use the custom kernel to root my phone. (Am I right? )
Currently I only have done your first step - backup the TA.
And of course, thank you again. :fingers-crossed:

Skylac06 said:
One little question: if I unlock my bootloader, my complete internal storage is wiped, right?
But if my bootloader is locked, I can not use the nandroid-backup-function of TWRP, because I can not use the custom kernel to root my phone. (Am I right? )
Currently I only have done your first step - backup the TA.
And of course, thank you again. :fingers-crossed:
Click to expand...
Click to collapse
You can root with locked bl, but your options are: 1) use Kingroot, (and it's generally preferred to not keep Kingroot, so after rooting you can replace Kingroot with SuperSU or wipe everything and flash a new rom with SuperSU), or 2) downgrade to KK and use doomlord rootkit, then flash LP prf.

levone1 said:
You can root with locked bl, but your options are: 1) use Kingroot, (and it's generally preferred to not keep Kingroot, so after rooting you can replace Kingroot with SuperSU or wipe everything and flash a new rom with SuperSU), or 2) downgrade to KK and use doomlord rootkit, then flash LP prf.
Click to expand...
Click to collapse
Okay.
I would like to avoid using Kingroot and downgrade to 4.4 is not even better.
But I found the Sony-Flashtool "Emma" for Windows. It seems to be able to restore completely the Stock-5.1-ROM. So I think I don't need a whole nandroid-backup. Am I right?
So I will unlock my bootloader, flash the custom kernel using TWRP-Tool and have a rooted phone. Then I am able to flash any custom-ROM I want to try out.
Did I misunderstand anything?

Skylac06 said:
Okay.
I would like to avoid using Kingroot and downgrade to 4.4 is not even better.
But I found the Sony-Flashtool "Emma" for Windows. It seems to be able to restore completely the Stock-5.1-ROM. So I think I don't need a whole nandroid-backup. Am I right?
So I will unlock my bootloader, flash the custom kernel using TWRP-Tool and have a rooted phone. Then I am able to flash any custom-ROM I want to try out.
Did I misunderstand anything?
Click to expand...
Click to collapse
True, Emma will restore you to stock. The backup would be if you want to restore the particular state of your phone right now.
Unlock bl, then flash the boot and recovery imgs, and you will be able to get into recovery. You'll want to have whatever rom you want to flash already downloaded on sdcard.

It works.
Now I have the AICP 12.1 7.1.2 Nightly Version.
Only the camera is not good, but better than expected. The aroma-GApps-package does not work, the GUI is hidden under the GUI of TWRP, but you can select your choice. However, after clicking install nothing was installed. After I downloaded and installed the super-GApps-package everything works fine.
If I find some issues, where can I report them? In the officiall AICP-12.1 N 7.1 amami Thread?
And at least a great thank you to levone1. :fingers-crossed:

Skylac06 said:
It works.
Now I have the AICP 12.1 7.1.2 Nightly Version.
Only the camera is not good, but better than expected. The aroma-GApps-package does not work, the GUI is hidden under the GUI of TWRP, but you can select your choice. However, after clicking install nothing was installed. After I downloaded and installed the super-GApps-package everything works fine.
If I find some issues, where can I report them? In the officiall AICP-12.1 N 7.1 amami Thread?
And at least a great thank you to levone1. :fingers-crossed:
Click to expand...
Click to collapse
https://forum.xda-developers.com/so...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288

levone1 said:
https://forum.xda-developers.com/so...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288
Click to expand...
Click to collapse
That is the thread I meant, but I can not post any URLs.

Best Custom ROM for Z1C
Not to open a new thread, which Custom ROM would you guys recommend to install on my Z1C?
I'm having some issues atm. It keeps restarting; I did a factory reset, it worked well for a while, now the issue is back. However, it does seem to work fine when hooked up to my PC (with the PC Companion active). Before I start shopping for a new phone, I'd like to root it first.
For this purpose, I'd like to know whick custom ROM is the most stable that you would recommend I install. Also, I'd be very helpful if you could direct to a good guide about the entire process.
Thank you in advance, I appreciate it!

levone1 said:
Backup TA - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Root and recovery :
Download custom kernel to pc, and extract boot img to ADB directory - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 and download twrp img to ADB directory - https://www.androidfilehost.com/?fid=457095661767147235 then use fastboot commands to flash boot and recovery. Now you have recovery, and you can either flash SuperSU zip, or flash custom rom.
Restore TA - https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893 or use Flashtool relock bl option - http://www.flashtool.net/
Click to expand...
Click to collapse
OP's intention is different than mine but this approach looks suit me well. I would like to keep my stock (14.6.A.1.236), so can I flash kernel.sin from Stock Rom via Flashtool after restoring TA and keep root status and recovery or should I use the custom kernel henceforth?

prustr said:
OP's intention is different than mine but this approach looks suit me well. I would like to keep my stock (14.6.A.1.236), so can I flash kernel.sin from Stock Rom via Flashtool after restoring TA and keep root status and recovery or should I use the custom kernel henceforth?
Click to expand...
Click to collapse
I don't think I've ever done it that way, but I don't see why not. As long as you don't wipe your recovery, you should still be good... (if you'd rather use stock kernel for whatever reason).

levone1 said:
I don't think I've ever done it that way, but I don't see why not. As long as you don't wipe your recovery, you should still be good... (if you'd rather use stock kernel for whatever reason).
Click to expand...
Click to collapse
Thanks for the answer. Actually the whole story is, the phone belongs to my wife and she is neither techsavvy nor has patience with electronics, especially when any problem come up. I would like to remove bloatwares and have backup yet keep the phone as Stock as possible. I'm trying to keep my ROM related modifications at minimum. That's been said, I would welcome any correction on this manner as I feel you found returning the stock kernel is pointless.

prustr said:
Thanks for the answer. Actually the whole story is, the phone belongs to my wife and she is neither techsavvy nor has patience with electronics, especially when any problem come up. I would like to remove bloatwares and have backup yet keep the phone as Stock as possible. I'm trying to keep my ROM related modifications at minimum. That's been said, I would welcome any correction on this manner as I feel you found returning the stock kernel is pointless.
Click to expand...
Click to collapse
I wouldn't say pointless, but for the most part, any custom kernel is an improvement. Most of the customizations wouldn't mean anything to someone like that, but I doubt there's any harm or risk in keeping it.

New!! [MTK-SU temp root] TA Backup BEFORE Unlocking your bootloader. MTK SoC Only!!

This works for MediaTek SoC ONLY!! XA XA1 and variants of C4/5's, M5's, L1, L2 and Maybe even L3's
Update: A Bootless/System only Root is now reported as working again thanks to diplomatic.
Can XA1 users who have benefited from mtk-su and the System only Root please report back their experience here also so other XA1 users will know what to expect. ​
Thanks to dev @diplomatic All Sony Mediatek devices should now be able to obtain a /ta partition backup before unlocking their bootloader. :victory:
It works by getting temporary "root" with a easy to use method which will then allow you to grab a /ta backup via the dd cmd
I did some testing for diplomatic and I can confirm this works with my locked bootloader XA1 on Android 8.0 lesser versions should also work.
I also tested this on my other Mediatek devices with the same successful results upto and including Android 8.1
Please visit diplomatic's Thread HERE for instructions and details also remember to Hit his Thanks Button or the :good: Thumbs Up Button if your using a phone app.
How do I backup the /ta ???
See this here.
Use MTK-SU to get temp root then use my dd backup helper script
Thread is HERE for instructions and info
https://github.com/bigrammy/dd-backup-helper-script/blob/master/dd-backup.sh
I am new to Sony whats all this stuff mean???
The below will help anyone new to Sony Gain a little insight into the slight differences over stock Android.
So take time to read it
New to Sony then read the info HERE it will save you a lot of head scratching and google time and I created the thread for just such as you. :good:
As a Footnote for the over enthusiastic:
You only need dd backup what is specific to your device so everything that is NOT included in the FlashTool/Xperifirm firmwares. Like the /TA, /Protect_f, /Protect_s, to name a few for example.
Backing up stock boot or fotakernel is kinda pointless because these are contained in the XperiFirm/FlashTool firmwares and can be easily restored using FlashTool or xflasher to flash those Stock ROM parts.

This is all a little over my head, to be honest. But it looks like I won't be able to install TWRP unless I unlock my bootloader if I'm reading this right?
My phone's bootloader can't be unlocked so that'll be a real shame if that's so.

Ticklefish said:
This is all a little over my head, to be honest. But it looks like I won't be able to install TWRP unless I unlock my bootloader if I'm reading this right?
My phone's bootloader can't be unlocked so that'll be a real shame if that's so.
Click to expand...
Click to collapse
Sure. But you will be able to temp root phone.

Ticklefish said:
This is all a little over my head, to be honest. But it looks like I won't be able to install TWRP unless I unlock my bootloader if I'm reading this right?
My phone's bootloader can't be unlocked so that'll be a real shame if that's so.
Click to expand...
Click to collapse
Sorry for the super late reply but for some reason I don't get a notification when someone post's I guess I must have forgot to subscribe to my own thread. :silly:
Why cant you unlock your bootloader

bigrammy said:
Sorry for the super late reply but for some reason I don't get a notification when someone post's I guess I must have forgot to subscribe to my own thread. :silly:
Why cant you unlock your bootloader
Click to expand...
Click to collapse
I have the message "bootloader unlock allowed: no" so I'm stuck.
I was hoping to be able to install TWRP so I can start modding my system apps.
Sent from my Sony Xperia XA1 using XDA Labs

Ticklefish said:
I have the message "bootloader unlock allowed: no" so I'm stuck.
I was hoping to be able to install TWRP so I can start modding my system apps.
Sent from my Sony Xperia XA1 using XDA Labs
Click to expand...
Click to collapse
Hmm My XA1 is with a relative just now so can't check but we used to have this problem on the C4 and C5.
I just Ignored that and tried the unlock code anyway. It worked for me on the C4 and XA but but not tested it on the XA1 so no guarantee's.
The other option is to use xflasher which worked for me on my XA1 (BL Locked) and flash only the system, boot, recovery, oem and userdata of the earliest 7.0 you can get your hands on and see if it boots. :fingers-crossed: It may even work for the preloader lk etc but I did not want to risk bricking the XA1 so never tried to flash those sensitive area's
If it does let you flash a earlier version then just wait for the ota and install it. The OTA will flash the perloader and lk of the next 7.x update and hopefully that will allow you to unlock the BL unless your phone is locked to specific carrier then I am unsure about that.
Again this is the method used on the C4/5 for rolling back to 5.0 so we could unlock the bootloader.

bigrammy said:
Hmm My XA1 is with a relative just now so can't check but we used to have this problem on the C4 and C5.
I just Ignored that and tried the unlock code anyway. It worked for me on the C4 and XA but but not tested it on the XA1 so no guarantee's.
The other option is to use xflasher which worked for me on my XA1 (BL Locked) and flash only the system, boot, recovery, oem and userdata of the earliest 7.0 you can get your hands on and see if it boots. :fingers-crossed: It may even work for the preloader lk etc but I did not want to risk bricking the XA1 so never tried to flash those sensitive area's
If it does let you flash a earlier version then just wait for the ota and install it. The OTA will flash the perloader and lk of the next 7.x update and hopefully that will allow you to unlock the BL unless your phone is locked to specific carrier then I am unsure about that.
Again this is the method used on the C4/5 for rolling back to 5.0 so we could unlock the bootloader.
Click to expand...
Click to collapse
Interesting. I might try the unlock code just to see what it does. I think Vodafone may have locked my phone, which is understandable but annoying.
I can't afford a new handset and all my old ones are either broken or so underpowered that they're pretty useless, so I won't try flashing anything right now. Too risky.

Ticklefish said:
Interesting. I might try the unlock code just to see what it does. I think Vodafone may have locked my phone, which is understandable but annoying.
I can't afford a new handset and all my old ones are either broken or so underpowered that they're pretty useless, so I won't try flashing anything right now. Too risky.
Click to expand...
Click to collapse
Hmm I thought they could only really sim lock the device but maybe that's why your not been shown the Option to unlock the bootloader.
If you have the sim lock removed by fair or fowl means then the unlock option may become available to you. I have flashed full Vodafone Virgin O2 ROM's with FlashTool before now and none ever locked the bootloader I have only ever heard of people having problems who accidentally flash the sim.lock part of the firmware. :silly:
PS: I have used these before for sim unlocking and all was ok. HERE also cheaper than most.

New bootless/System Only Root
A Heads up for everyone!!!
Well @diplomatic has done it again with a New bootless Root for locked bootloaders it has been reported to be working on the XA1 which I am sure will be good news for many. :victory:
Remember to Hit the thanks button of diplomatic or better still buy him a Beer or Pizza for liberating your phone. :good:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
@Ticklefish

Bootless magisk root
Bootless magisk root working on XA1!!!
Updated tutorial: https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135

Wow, cool! You mean I don't have to unlock my phone to get root? Can't wait to try it on my XA1...
---------------------
But seriously, this bootless root may be a bigger headline than the temp root shell itself.

diplomatic said:
Wow, cool! You mean I don't have to unlock my phone to get root? Can't wait to try it on my XA1...
---------------------
But seriously, this bootless root may be a bigger headline than the temp root shell itself.
Click to expand...
Click to collapse
Awesome work all round and yes you are correct it may even warrant a thread of its own since itś not limited to MTK devices.
On a side note.
Safestrap recovery would be the next logical thing for the XA1 then the locked bootloader circle should be complete.
It will be like running the Fire Phone again :laugh:
https://github.com/bigrammy/android_bootable_recovery-safestrap

Yeah, you're right, I'll make a new thread eventually. Just wanted to start slow and see where it goes...
Unfortunately, safestrap recovery will be problematic because this method doesn't let you write to /system or boot. It doesn't do anything about dm-verity and all that.

diplomatic said:
Yeah, you're right, I'll make a new thread eventually. Just wanted to start slow and see where it goes...
Unfortunately, safestrap recovery will be problematic because this method doesn't let you write to /system or boot. It doesn't do anything about dm-verity and all that.
Click to expand...
Click to collapse
I need to get around to unpacking the boot of the XA1 and look at the lk too. If they moved the fstab to system/vendor then there maybe a way.
My thoughts are as yet untested and based off vague memories but if I manage to put them all together I will let you know.
Real busy just now with Work and ongoing home improvements so not got much time for playing

Read this before thinking about bootless recovery:
https://source.android.com/security/verifiedboot/dm-verity

Any method to root with magisk that allows modifying / system?

leonardo.teseyra said:
Any method to root with magisk that allows modifying / system?
Click to expand...
Click to collapse
Yes for sure but you need to be officially bootloader unlocked for that.
You use the mtk-su to gain temp root then make a couple of dd backups of your /ta and any other partition you think maybe useful which is basically
anything not contained in a firmware package using FlashTool/Xperifirm
EG:
ta
nvram
nvdata
protect_f
protect_s
When you have what you need Unlock the bootloader officially.
Convert your boot.elf to boot.img have Magisk patch the new boot.img and flash it via fastboot.
If you need more detail please provide more such as your device etc it make helping easier. :good:

bigrammy said:
Yes for sure but you need to be officially bootloader unlocked for that.
You use the mtk-su to gain temp root then make a couple of dd backups of your /ta and any other partition you think maybe useful which is basically
anything not contained in a firmware package using FlashTool/Xperifirm
EG:
ta
nvram
nvdata
protect_f
protect_s
When you have what you need Unlock the bootloader officially.
Convert your boot.elf to boot.img have Magisk patch the new boot.img and flash it via fastboot.
If you need more detail please provide more such as your device etc it make helping easier. :good:
Click to expand...
Click to collapse
Thanks for the help, I have a Sony Xperia XA1 with android 8.0. Do you know of any tutorial I can follow? I need to root with magisk to be able to hide the root.

leonardo.teseyra said:
Thanks for the help, I have a Sony Xperia XA1 with android 8.0. Do you know of any tutorial I can follow? I need to root with magisk to be able to hide the root.
Click to expand...
Click to collapse
Backup your ta partition then unlock your bootloader using Sonys official method.
Flash the boot and recovery for your device which are located in this thread HERE
Format your data again with TWRP and flash magisk thats it your done.
To revert your devices back to 100% stock dd back your ta backup and reflash the 100% stock ROM using FlashTool or maybe Sonys official tool.

bigrammy said:
Backup your ta partition then unlock your bootloader using Sonys official method.
Flash the boot and recovery for your device which are located in this thread HERE
Format your data again with TWRP and flash magisk thats it your done.
To revert your devices back to 100% stock dd back your ta backup and reflash the 100% stock ROM using FlashTool or maybe Sonys official tool.
Click to expand...
Click to collapse
How can I backup my TA partition?. I have root access but I can't find /ta any where