Database Users

A Dirty trick ------TO EXTRACT DRMKEYS TA.IMG---- ? - Sony Xperia XZs Guides, News, & Discussion

Sir
I have been asking around this question and I wanted to mention it here (hopefuly I am not too much out of line)
latest build OREO 13march2018 , xperia XZ Kagura F8332 & Xperia XZs Kayeki G8232 is 41.3.A.2.107 ( both having Kernel Version )
on 13MARCH OBHT WERE ON 41.3.A.2.99
on 1MAR2018 both were on 41.3.A.2.75 &
DURING FEB2018 both XZ / XZs were on build 41.3.A.2.58
BOTH DEVICE ARE ON FIRMWARE 41.3.x.x
--------
I was wandering what if XZ - F8332 BUILD 39.0.A.3.30 ( Android 6.01) is flashed on G8232 (both Dual) to extract TA.img via Dirtycow script.
what will happend if XZ android 6 flashed on XZs ?
1. device will freeze on logo (recoverable )
2. device will bootloop (recoverable )
3. device get stuck at boot (black screen) (soft brick)
4. boot get corrupted and device is DONE (hard brick) (wont boot ever) (pc wont recognize any key combinations or will read it as XZ only)
5. XZs will boot in to system with crashing popups for various processes, but I will be able to manage enabling usb debugging and extracting TA.img via dirtycow script
6. what will be the name of the file? TA_G8232 _ABCDEF_07-Mar-171608-1783.img ORR TA_F8332 _ABCDEF_07-Mar-171608-1783.img
7. if its TA_F8332 _ABCDEF_07-Mar-171608-1783.img , then relocking bootloader with this file name, wont BRICK the G8232 FOR GOOD ?
any thoughts plz ?
Code:
the universal TA script has line 22 reading as
TAIMG="TA_${DEVICE}_${SERIAL}_$(date -u +%Y%m%d-%H%M).img"
this "DEVICE" is firmware or actually hardware?

anyone ?

Related

[GUIDE] Sony Xperia Z5
DISCONTINUED - SEE NEWS !
Last update: 20.06.2016​
This guide will help you to root your phone, install new firmwares, unlock your bootloader and much more. Its splitted into 3 sections: StockRom, CustomROM and Tweaks so you should find things easily. I think if you understood this guide you can easily flash different firmwares, kernels and so on. And now - have fun
NEWS
I have to much work to do at the moment to continue this guide. But, the main work is done, now its all about updating the links. If there is something remarkable new, I will add it to my guide.
20.06.2016
- updated links
- minor changes
23.04.2016
- updated download links
- added custom rom (CyanogenMod13)
- some small changes
09.04.2016
- I'm very busy at the moment (exams and hard work). So I cant help you guys that much and cant try new kernels and that kind of stuff Plese ask @gm007 or @zacharias.maladroit if you have problems. I will come back as fast as I can
- updated download links
28.03.2016
- updated download links
12.03.2016
- Android 6.0 compatibility check
- updated download links
- graphical revision
14.02.2016
- updated guide to make it more understandable
QUESTION & ANSWER
Which devices are supported by this guide?
- Sony Xperia Z5
- Model number: E6653 / E6603 (for other models use different kernel)
- OS version: Stock Xperia Android 5.1.1 / 6.0
Whats important to know before I start?
- I´m NOT responsible for any damage.
- Keep in mind that unlocking the bootloader can void your warrenty.
- Save your data, all settings and files will be deleted during this process.
- READ THE ENTIRE GUIDE FIRST!
[GUIDE] GENERAL
FASTBOOT
1) POWER OFF phone
2) Hold VOLUME UP
3) Connect to PC via USB
4) LED turns blue
FLASHMODE
1) POWER OFF phone.
2) Hold VOLUME DOWN
3) Connect to PC via USB
4) LED turns green
RECOVERY
a) You can enter TWRP while booting. If the LED turns yellow, hold VOLUME DOWN till it gets orange.
b) Use this command in Minimalistic ADB and FASTBOOT to reboot to recovery:
Code:
adb reboot recovery
BOOTLOOP / EMERGENCY POWER OFF
1) Hold POWER OFF and VOLUME UP
2) Device vibrates 3 times
DEVELOPER MODE AND UNNOWN SOURCES]
1) settings -> about phone -> touch build number several times
2) settings -> developer options -> enable USB debugging
3) settings -> security -> enable Unknown sources
PC PERMISSIONS
1) Run Minimalistic ADB and FASTBOOT and FLASHTOOL with admin permissions.
2) Use USB 2.0 ports, sometimes 3.0 ports doesnt work.
[GUIDE] StockROM
# BUGS / ISSUES
E6653_32.1.A.1.163
- camera apps (AR Effect,...) do force close
- filesystem (external SD card) does not refresh automatically, so you cant transfer files you copied to sd card via MTP to PC. Solved via restart. --> also on STOCK ROM
# DIRECT DOWNLOAD LINKS
E6653
Kernel
Z5_AndroPlusKernel_Permissive_v30 (for firmware .163 and .185)
Z5_AndroPlusKernel_Permissive_v31 (for firmware .224)
Recovery
twrp-3.0.2-0-E6653-20160417.img
SuperSu
SuperSU (beta but stable)
# DOWNLOAD LINKS
Windows programs
Sony PC Companion
Minimal ADB and Fastboot
Flashtool + patch file
µTorrent (for downloading Flashtool)
Android
AndoPlusKernel
TWRP
# GUIDE
BOOTLOADER STATUS
The bootloader loads the kernel. If unlock isnt allowed, the bootloader will prevent loading a custom kernel.
1) type *#*#7378423#*#* into dialer / phone app
2) service info --> configuration --> rooting status
3) if bootloader unlock allowed says YES, you can continue. If bootloader unlock isnt allowed you CAN NOT root your phone.
INSTALLING PROGRAMS
Flashtool
1) install µTorrent
2) download torrent file from Flashtool website
3) run downloaded torrent file via µTorrent
4) download Flashtool via µTorrent
! You can close and or delete µTorrent now, you will not need it anymore
5) install Flastool
6) open install directory from flashtool and replace x10flasher.jar with new patch
OTHER
1) install all other programs
INSTALL / CHECK DRIVERS
Windows 7 and lower
1) open Flashtool install directory
2) open driver folder
3) run Flashtool-drivers.exe
4) install Flashmode and Fastboot drivers
Windows 8 and higher
1) restart computer with digital driver signature disabled (you have to do this every time you restart your pc)
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2) open Flashtool install directory
2) open driver folder
3) run Flashtool-drivers.exe
4) install Flashmode and Fastboot drivers
! There are no Z5 drivers yet, that’s why you need Sonys PC Companion!
! Flashtool drivers were updated, try the new Z5 drivers before installing Sony PC Companion.
Sony PC Companion
1) run Sony PC Companion
2) connect your Xperia Smartphone
3) wait till it has been detected
4) close Sony PC Companion, you dont need it anymore
ADB driver check
1) enable Developer options and Unknown sources
2) run Minimal ADB and Fastboot
3) type
Code:
adb devices
4) allow dialog on your phone
5) check if your device is shown in command window
fastboot driver check
1) run Minimal ADB and Fastboot
2 put device in FASTBOOT mode
3) type
Code:
fastboot devices
in Minimal ADB and Fastboot
4) check if your device is shown in command window
! When connecting phone in flashmode or fastboot additional drivers will be installed automatically.
! Installing drivers twice can solve problems.
UNLOCK BOOTLOADER
1) open Flashtool
2) click on BLU (Bootloader Unlock)
3) follow the instructions shown by Flashtool
4) you will be forwarded to a Sony website
5) follow the instructions there
6) at the end you will receive a key
7) save this key carefully!
8) enable Enable OEM unlock in developer options
9) copy KEY into Flashtool prompt and click unlock
! You can try to use Flashtool for unlocking first, or continue with step 10.
10) open Minimal ADB and Fastboot
11) your phone has to be in Fastboot mode
12) check if your phone is shown by
Code:
fastboot devices
13) enter the following code:
Code:
fastboot –i 0x0fce oem unlock 0xKEY_FROM_SONY
14) reboot (that can take a long time, so dont worry)
DOWNLOAD XPERIA FIRMWARE - OPTIONAL
If you want to update, upgrade or reset your ROM.
1) open Flashtool
2) click on XperiFirm
3) downloading…..
4) in XperiFirm select your device then choose your preferred firmware (e.g. Z5 --> E6653 ---> Customized DE --> 32.0.A.6.200 R12B)
5) in the right column double click the latest firmware and start download
6) Unpack automatically has to be checked
7) after downloading close download window and XperiFirm
8) now Flashtool should start doing things
! You can identify your phone model by: Settings -->About phone--> Diagnostics
FLASH NEW FIRMWARE - OPTIONAL
If you want to update, upgrade or reset your ROM.
1) in Flashtool click on Flash device and choose your firmware
2) under "Wipe", check all (APPS_LOG, DIAG, SSD, USERDATA)
3) click flash and follow the instructions
4) after successful installation reboot phone (that can take a long time, so dont worry)
! You can flash a new ROM without unlocking your bootloader.
FLASH KERNEL
The kernel has direct control of the hardware.
1) download latest Kernel from download section (AndroPlusKernel is only for E6653 models)
2) extract ZIP
3) put boot.img from zip into your root directory from Minimal ADB and Fastboot
4) put phone into fastboot mode
5) run Minimal ADB and Fastboot and check with
Code:
fastboot devices
6) type in:
Code:
fastboot flash boot boot.img
7) restart phone and look if its working
! If you end up in a bootloop with the LED flashing 3-4 times try to flash Kernel and Recovery again. If this doesnt help, reflash firmware, kernel and recovery.
FLASH RECOVERY
The recovery is something like the boot menu you may know from windows. Its mainly used to install programs and apps.
1) download latest TWRP from download section
2) put twrp.img into your root directory from Minimal ADB and Fastboot
4) put phone into fastboot mode
5) run Minimal ADB and Fastboot and check with
Code:
fastboot devices
6) type in:
Code:
fastboot flash recovery twrp.img
! You can rename twrp image to twrp.img or something shorter if you want.
7) after the first boot - do a reboot into recovery. Otherwise the partitions won't be mounted correctly & flashing will run into trouble. It takes several seconds (or a few minutes) to reboot into recovery - but then you're good to go.
ROOT
Some apps need more permissions than normal. You can compare root with administrator rights on windows.
1) download UPDATE-SuperSU-v2.67.zip
2) copy UPDATE-SuperSU-v2.67.zip to your internal memory
3) enter TWRP
4) click Install
5) navigate through folder structure
6) tap UPDATE-SuperSU-v2.67.zip
7) "Swipe to confirm flash"
8) reboot
RESTORE DRM KEYS
Unlocking the bootloader disables a partition on your phone where software keys are saved. Without this keys xReality, BIONZ, audio processing arent available. This program will restore this features.
! Take a look if xReality is already working before installing DRM keys.
1) download DRM RESTORE (drmrestore.zip) from download section
2) copy drmrestore.zip to your external sd card
3) enter TWRP
4) click Install
5) navigate through folder structure
6) tap drmrestore.zip
7) "Swipe to confirm flash"
8) reboot
! Unfortunately, there is no way to save the original TA partition at the moment.
[GUIDE] CustomROM
# CyanogenMod 13_Alpha for E6653 and E6603
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
### XDA Z5_CyanogenMod 13 Link ###
# AromaROM with Installer for Z5 E6853 / E6883 / E6653
AROMA is a custom ROM with nice tweaks, but it has some serious bugs. I used it for 2 month and there are several issues: random reboot, screen turn off during calling and does not turn on again, problems with notification bar, ... .
### XDA ROMAur Link ###
1) install stock lollipop rom
3) for E68xx models install recovery and kernel for your device
4) For E66xx models install twrp-2.8.7.0-E6653-20151130_material.img and kernel for your device
5) copy ROMAur to your external sd card
6) enter recovery
7) make a full wipe (Wipe --> Factory reset)
8) install ROMAur
9) Reboot
[TWEAKS]
XPOSED
ONLY FOR 5.1.1: When you want to install Xposed you have to deodex your system or install an already deodexes ROM. Without this procedure the camera and other apps wont work. Use this guide to solve this: http://forum.xda-developers.com/crossdevice-dev/sony/z4-z5-z5c-fix-camera-fc-installing-t3246962
XDA Thread: http://forum.xda-developers.com/showthread.php?t=3034811
1) download xposed-v85-sdk23-arm64.zip and XposedInstaller_3.0_alpha4.apk [Android 6.0 versions]
2) copy xposed-v79-sdk23-arm64.zip and XposedInstaller_3.0_alpha4.apk to your internal memory
3) enter TWRP
4) click Install
5) navigate through folder structure
6) tap xposed-v79-sdk23-arm64.zip
7) "Swipe to confirm flash"
8) reboot
9) install XposedInstaller_3.0_alpha4.apk
10) reboot
useful Xposed Moduless
APM+
Xperia / AOSP NavBar Buttons
OGYoutube + OGYoutube Xposed Login Fix
Flat Style Colored Bars
DISABLE SmallApps
SmallApps is that little bar in the overview screen.
1) power on phone
2) unlock your phone (open homescreen)
3) open Minimal ADB and Fastboot
4) type:
Code:
adb shell
pm hide com.sony.smallapp.launcher
pm hide com.sony.smallapp.app.widget
exit
5) after this, type:
Code:
adb reboot
! If you know what youre doing, you can simply delete all the SmallApp stuff via ROOT Uninstaller.

Thanks for quite a nice guide.
I have done rooting on various devices but this seems to be most complicated ever. [emoji14]
Sent from my E6683 using Tapatalk

It has been before this guide. Basically what I did was unlocking the bootloader, booting recovery, flashing kernel, flashing root, wipe, restore DRM fake, done.
Firmware wasn't necessary for me and I've made bad experiences with alternate firmwares / radios and so on in the past.

Hi. Do I have to backup my TA partition ?

there no way to backup your TA partition hopefully for now.

How to increase volume of both speakers
I have rooted z5 but don't know how to edit mixer path.xml

Siudzix said:
Hi. Do I have to backup my TA partition ?
Click to expand...
Click to collapse
Actually there is no need for it, imho. The fake DRM keys are doing a really good job. X-reality back, after picture processing back. It's also currently not possible to backup them afaik.

DeathStroke said:
Thanks for quite a nice guide.
I have done rooting on various devices but this seems to be most complicated ever. [emoji14]
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Mate I see you have Z5 E6683 which is dual sim. Were you able to get your phone rooted using this guide?
Many thanks.

I have XPERIA Z5 Dual Sim (E6633) - will this guide work ?

Siudzix said:
I have XPERIA Z5 Dual Sim (E6633) - will this guide work ?
Click to expand...
Click to collapse
Yes and no. You need a different kernel and mybe recovery. Everything else is the same. I will include a link in my guide if I find a working kernel.

Rooting Z5
Hi all,
Shall i root the phone without unlocking the Bootloader.I dont want to Unlock the bootloader.So please advise me is this root method is work on Locked Bootloader.
Thanks in advance

ramprasaathks said:
Hi all,
Shall i root the phone without unlocking the Bootloader.I dont want to Unlock the bootloader.So please advise me is this root method is work on Locked Bootloader.
Thanks in advance
Click to expand...
Click to collapse
For now, you have to unlock your bootloader to gain root access. There is no other method at the moment. So in conclusion: locked bootloader = no root.

how i root z5 dual 6683

parteek.dandyan said:
how i root z5 dual 6683
Click to expand...
Click to collapse
Follow the guide and do it. Its written there.
Sent from my E6683 using Tapatalk

DeathStroke said:
Follow the guide and do it. Its written there.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Dont blame him. I added this guide for E6683 today. I cant try it myself because I have no E6683, but I hope it will work

alphatact1cs said:
Dont blame him. I added this guide for E6683 today. I cant try it myself because I have no E6683, but I hope it will work
Click to expand...
Click to collapse
I was not blaming, I didn't know that you updated today. Would be great in future if you do any update, add the date and following update.
Thank you.
One thing I noticed while reading your guide was TWRP is not for E6683. Will there be any problem? I haven't yet tried your guide because I was in doubt.
Sent from my E6683 using Tapatalk

DeathStroke said:
One thing I noticed while reading your guide was TWRP is not for E6683. Will there be any problem? I haven't yet tried your guide because I was in doubt.
Click to expand...
Click to collapse
The new Kernel from monx includes TWRP, so you dont need to flash Recovery...normally. I know that my guide works, but only for E6653. I included a link for E6683, but I also wrote that I cant try it because I havent a Z5 E6683. Anyway, TWRP for E6653 should work for E6683 devices. The main difference is the Kernel.

Guys, what about E6633 ? Is it really bad ?

Siudzix said:
Guys, what about E6633 ? Is it really bad ?
Click to expand...
Click to collapse
You can try it at your own risk. Someone said that it will work, but I would be careful.
pesonic said:
Should this be working on E6633 too?
Click to expand...
Click to collapse
arismelachrinos said:
+1
Click to expand...
Click to collapse

@alphatact1cs are you open to suggestions??
we are currently trying to unify devices index here at xda..
would you like to follow what our fellow brother @kuzibri and @sd_shadow has implemented?
http://forum.xda-developers.com/general/about-xda/public-index-program-project-t3147245

** DISCLAIMER: I AM NOT A DEV AND THIS IS MY HOBBY. I ASSUME NO RESPONSIBILITY IF THIS BREAKS YOUR DEVICE **​The following is tested on model SGP-771. For Wifi-only model the procedure is the same but you should use the files and kernels for the Wifi model. Do not flash the ftf and kernel files intended for the cellular model on a Wifi-only tablet.​I am not taking credit for any of the tools and kernels here. They are all developed by others. I am only telling you how to use them.
Credits: @zxz0O0, @AndroPlus, @tobias.waldvogel
0- Prerequisites
You need to have a functioning installation of adb and fastboot tools. You need to have proper Sony drivers installed on your PC to detect your tablet when it is connected to the PC. You should be able to flash an ftf file using flashtool. If any of these sound unfamiliar to you, stop reading, go learn about them, and then come back.
1- How to unlock your bootloader without losing the DRM keys
Sony has designed this tablet such that if you unlock your bootloader you lose your TA partition PERMANENTLY which includes some of the Xperia features and licenses that have to do with image processing etc. forever. You will also no longer receive OTAs. So in theory, without a copy of this TA partition (which is unique to each tablet and cannot be copied over from another tablet) unlocking the bootloader results in an irreversible loss of some of your tablet's features. Relocking the bootloader will not bring them back.
A hack exists that allows you to backup the TA partition before you unlock the bootloader. This backup will make the process completely reversible so if you ever need to send the tablet to Sony for repair or just want to return it to its original state you have a way. Follow these instructions carefully:
1.0- Before you begin keep in mind that this procedure, especially the unlocking step, completely erases your tablet. Disable myXperia and remove your google account before proceeding. The following will likely not work well with encryption.
1.1- Start by clean flashing any 28.0.A.8.260 firmware, For this tutorial I used SGP771_Customized HK_1296-4830_28.0.A.8.260_R10A. You can download it from https://mega.nz/#!YsUWwY5Y!0775_vLpjV9-UkoGjMWP6-Yu8L31LkJVHEyUwA7X9NA. For the wifi only model SGP712 use
https://mega.nz/#!wlIl0JDa!DR0lRL6dDn5Y-K_4768oJnLGWQyrxNV0xLHgKVVesFw (thanks to @kuroneko007)
1.2- Enter service Mode by dialing *#*#7378423#*#* -> Service info -> configuration, and make sure the device is unlockable. (To access service menu on SGP712 (Wi-Fi only model) see: http://forum.xda-developers.com/showpost.php?p=66164176&postcount=5) Also check -> Service Tests -> Security and you will see a bunch of "active" and "OK" attributes. You can take screenshots for your reference.
1.3- Turn on usb debugging mode on your tablet.
1.4- Download iovyroot zip v0.4 or higher from here.
1.5- Unzip this zip file into a folder of your choice and open a command terminal there.
1.6- Connect the tablet which is now in USB debugging mode to your PC and answer yes when it asks to authorize the PC to access the tablet in USB debugging mode. You can check that the PC indeed sees the tablet by running this command
Code:
adb devices
1.7- Run the following command:
Code:
tabackup
1.8- VERY IMPORTANT: Make sure the command completes with no errors. If all goes well you will have a file with a name like TA-07102015.img (the name may be different for you) with a size of 2MB in your folder.
1.9- Save this file in a very safe place. Save it on your hard disk, AND email it to yourself, AND put it on your google drive. If you lose this file you can never reverse the bootloader unlocking process.
1.10- Reboot the device.
1.11- Now you can unlock the bootloader. Follow the instructions at Sony's official website at http://developer.sonymobile.com/unlockbootloader Also save your unlock code that you obtain in this step somewhere. You may need it some day.
1.12- Reboot the device and it will briefly enter recovery and then start the tablet initial setup.
1.13- (Optional) you can easily verify that your bootloader is unlocked by entering the fastboot mode, obtaining any boot image, and running the following command to boot your tablet with that image:
Code:
fastboot boot boot.img
1.14- (Optional) you can see that the DRM keys are erased from your tablet by repeating step 1.2 but this time you will see a bunch of errors under Service Tests -> Security.
1.15- As a side effect of unlocking the bootloader you lose the ability to receive OTA updates. Clean flash a Marshmallow ftf to continue. For this tutorial I used Marshmallow 6.0 SGP771_Customized DE_1295-6955_32.1.A.1.185_R4C (the latest firmware at the time of this writing.)
2- How to emulate DRM keys and/or root after unlocking the bootloader.
A hack exists that can emulate the DRM keys:
2.1- Obtain a kernel boot image. If you want to stick with the stock kernel you need to extract kernel.elf from the ftf that you flashed in step 1.15. If you want a custom kernel you can download one from https://kernel.andro.plus/kitakami.html Note that whatever kernel you are using in this step must match the firmware version currently installed on your system. For this example I downloaded Z4T_SGP771_AndroPlusKernel_v27.zip and extracted the boot.img file from the zip, which matches Marshmallow 32.1.A.1.185.
2.2- Download rootkernel_v4.42_Windows_Linux.zip (or a higher version) from http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 and unzip it in a folder of your choice.
2.3- Copy the kernel (e.g. boot.img) to this folder. If you want root, place SuperSU 2.71 (or higher) in this folder as well. Make sure the name of the SuperSU zip starts with letters "SuperSU". The latest SuperSU can be obtained from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
2.4- Open a command terminal in this folder and run the rootkernel script. Your command should look similar to this:
Code:
rootkernel.cmd boot.img boot-patched.img
When prompted, answer as follows:
- Sony RIC is enabled. Disable? [Y/n] Y
- Install TWRP recovery? [Y/n] N
- Found SuperSU-v2.71-20160331103524.zip. Install? [Y/n] Y (if you want root)
- Install DRM fix? [Y/n] Y (if you want DRM emulation)​This will create a new kernel image called boot-patched.img which you will now flash on your tablet.
2.5- Boot the tablet in the fastboot mode and flash your patched image using the following fastboot command:
Code:
fastboot flash boot boot-patched.img
2.6- (Optional) You can reboot the tablet and see that the DRM keys are indeed retrieved by repeating step 1.2. You can also open settings -> display, and look under Image Enhancement. If the DRM emulation is succesfull you will see this but if it hasn't been successful you will see this.
3- How to flash a custom or stock kernel
3.1- Whether you want to use a custom kernel or stock, and whether you have done the DRM patch described above or not, to flash it on your tablet you need to restart the tablet in fastboot mode.
3.2- To flash the kernel use this command:
Code:
fastboot flash boot [I]name_of_your_kernel[/I]
You will replace name_of_your_kernel with whatever your kernel is called (e.g. boot.img, kernel.elf, etc.)
4- How to flash recovery
4.0- To install TWRP recovery you need to flash AndroPlus kernel first (see sections 2.1 and 3).
4.1- Download a TWRP image from the same webpage. For this tutorial I used TWRP-3.0.2-0-20160417.img.
4.2- Reboot into fastboot mode and run this command:
Code:
fastboot flash recovery TWRP-3.0.2-0-20160417.img
4.3- Reboot the tablet. To enter recovery touch the volume keys when the LED turns yellow during the boot splash screen.
5- How to relock bootloader and return it to original factory state
5.0- To relock the bootloader along with restoring the DRM keys the tablet must have unmodified stock firmware.
5.1- Repeat step 1.1
5.2- Repeat steps 1.3, 1.4, and 1.5
5.3- Copy the TA backup image that you had obtained in section 1 in the iovyroot folder and use the tarestore command to flash the TA partition back onto the tablet. The command will look similar to this:
Code:
tarestore TA-07102015.img
Make sure the command completes with no error. If it fails the first time try again. Reboot the tablet. Your bootloader is now locked and your DRM keys restored.
5.4- (Optional) You can verify that you are back to the original locked state by repeating step 1.2.

Reserved
For FAQ, etc.

Thanks for this great guide.
My question is this. Since it would be easier to avoid all this, can this tool help us do it without having to downgrade?
http://www.xda-developers.com/chainfires-flashfire-can-now-create-fastboot-flashable-backups/
I mean would it also backup the DRM keys? Has anyone tried (preferably with a TA backup already in place so that he may not lose the keys in case that this won't work)...

Stevethegreat said:
Thanks for this great guide.
My question is this. Since it would be easier to avoid all this, can this tool help us do it without having to downgrade?
http://www.xda-developers.com/chainfires-flashfire-can-now-create-fastboot-flashable-backups/
I mean would it also backup the DRM keys? Has anyone tried (preferably with a TA backup already in place so that he may not lose the keys in case that this won't work)...
Click to expand...
Click to collapse
No. This tool cannot help you and trust me there is no shortcut to avoid all of this.
Flashfire (the tool you mentioned) only works if you already have root access. There is no root available for this tablet without unlocking the bootloader, and unlocking the bootloader means you lose the TA partition immediately. So by the time you get this tool to work your TA partition will have been long erased.

Hi. Does this solution suit only for people who have not erased drm keys yet and are be able to backup it? For those who lost, no up-to-date solution except for that http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383 ?

Correct.

Not understand step:
1.1- Start by clean flashing any 28.0.A.8.260 firmware
without this step temporary root not work...
But how flash firmware if device has still locked bootloader? What tool using for this step?

mrdarek said:
Not understand step:
1.1- Start by clean flashing any 28.0.A.8.260 firmware
without this step temporary root not work...
But how flash firmware if device has still locked bootloader? What tool using for this step?
Click to expand...
Click to collapse
You can download a tool called flashtool from http://www.flashtool.net/index.php and flash an unmodified ftf firmware. Because the firmware is unmodified the bootloader doesn't have to be unlocked. Many tutorials are available on xda and elsewhere about using this tool, which you can find by doing a Google search. As I said in the prerequisite section, "You should be able to flash an ftf file using flashtool. "

anybody successfully tried this guide?

I learned how flash and succesfully do my first flash.
Currently I have problem with iovyroot
It always say
Error: Device not supported
rm: /data/local/tmp/tabackup/TA-*.img: No such file or directory
My current software is:
SGP771_28.0.A.8.251_R15A_UK Generic_1295-4697
and it earlier then december 2015 like need iovyroot
I can't find software *.260 like in guide, I don't know if this created that problem...
Maybe najoor version work because it was "customized" - it mean - with patched kernel. But if locked bootloader allow me flash customized firmware?

mrdarek said:
I learned how flash and succesfully do my first flash.
Currently I have problem with iovyroot
It always say
Error: Device not supported
rm: /data/local/tmp/tabackup/TA-*.img: No such file or directory
My current software is:
SGP771_28.0.A.8.251_R15A_UK Generic_1295-4697
and it earlier then december 2015 like need iovyroot
I can't find software *.260 like in guide, I don't know if this created that problem...
Maybe najoor version work because it was "customized" - it mean - with patched kernel. But if locked bootloader allow me flash customized firmware?
Click to expand...
Click to collapse
As you said it, the problem was that you didn't flash the 260 version, not that it wasn't customized.
If you can't find the right version I upload it and post a link in the OP. It takes a little time so check this thread again in about 5 hours.

I found "260" firmware and magically all start work . I finished all job and have now root and recovery .
It worth add tips about fastboot - you can check connection by command but also you can see - if LED on device is blue - connection in fastboot work (if not - try again)
My last question is about how check that DRM emulation work - under security after phone code is still errors. I 100% patched kernel and flash it properly.
Thanks for tutorial and support
Something just not work... Someone can check sizes ?:
boot.img - original kernel androplus 2.5: 17 756 160
andropatched.img - patched with my drm keys: 17 760 256
keys: 2 097 152

mrdarek said:
I found "260" firmware and magically all start work . I finished all job and have now root and recovery .
It worth add tips about fastboot - you can check connection by command but also you can see - if LED on device is blue - connection in fastboot work (if not - try again)
My last question is about how check that DRM emulation work - under security after phone code is still errors. I 100% patched kernel and flash it properly.
Thanks for tutorial and support
Something just not work... Someone can check sizes ?:
boot.img - original kernel androplus 2.5: 17 756 160
andropatched.img - patched with my drm keys: 17 760 256
keys: 2 097 152
Click to expand...
Click to collapse
The sizes sound about right. What errors are you getting?
You can try to relock the bootloader using the instructions and see if your TA backup works. If that works then we can see why the kernel is patched correctly.

Hi - I succesfully restored bootloader (=locked it, and no errors in service) - so I'm sure - my keys are OK. It was very hard - 3x flash, 3 x try use restore (still was errors), and at last success!!!
Now all procedure again, almost from start - but I also more try if need - I send info tomorrow
---------------------------------------
Hmmm not work... Tested original marsmallow germany kernel and androkernel 2.4. Image test described in step 2.6 fail
Under security is: Blobs : generic error!
HUK: generic error!
Flashed kernels names are properly recognized under settings. root work. I not have idea where is bug. It must be during creating andropatched image - but no errors here:
C:\rootkit>drmonly boot.img andropatched.img TA-07102015.img
- Unpacking kernel
Found android boot image
Kernel version: 3.10.84
- Detected vendor: somc (Sony), device: karin, variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 6.0
- Skipping drmfix. Unsuppported/untested for model karin
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
C:\rootkit>
--------------------Maybe that line is wrong!!!!!!!!
Skipping drmfix. Unsuppported/untested for model karin
but how fix it?

mrdarek said:
Hi - I succesfully restored bootloader (=locked it, and no errors in service) - so I'm sure - my keys are OK. It was very hard - 3x flash, 3 x try use restore (still was errors), and at last success!!!
Now all procedure again, almost from start - but I also more try if need - I send info tomorrow
---------------------------------------
Hmmm not work... Tested original marsmallow germany kernel and androkernel 2.4. Image test described in step 2.6 fail
Under security is: Blobs : generic error!
HUK: generic error!
Flashed kernels names are properly recognized under settings. root work. I not have idea where is bug. It must be during creating andropatched image - but no errors here:
C:\rootkit>drmonly boot.img andropatched.img TA-07102015.img
- Unpacking kernel
Found android boot image
Kernel version: 3.10.84
- Detected vendor: somc (Sony), device: karin, variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 6.0
- Skipping drmfix. Unsuppported/untested for model karin
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
C:\rootkit>
--------------------Maybe that line is wrong!!!!!!!!
Skipping drmfix. Unsuppported/untested for model karin
but how fix it?
Click to expand...
Click to collapse
You need to follow the instructions to the letter:
1- flash the esaxt same firmware that you made the TA backup with.
2- Restore TA backup.
I guarantee you it will work or l will help you debug it.

Not very understand. It was done. TA backup was done with "260" firmware. I'm able lock that firmware again, so it work. but it only lollipop, can't go into marshmallow from it.
Goal is: marshmallow with root twrp and drm. How achieve it?
I see - I have new device version (karin) so (hopefully) temporary this solution not work for me. I can have only marshmallow with root and twrp (no DRM) or marshmallow with DRM (no root and twrp). I must wait as developers support my device, and keep my keys in safe place to that time.

mrdarek said:
Goal is: marshmallow with root twrp and drm. How achieve it?
Click to expand...
Click to collapse
mrdarek said:
Tested original marsmallow germany kernel and androkernel 2.4. Image test described in step 2.6 fail
...
Flashed kernels names are properly recognized under settings. root work. I not have idea where is bug. It must be during creating andropatched image - but no errors here:
...
C:\rootkit>drmonly boot.img andropatched.img TA-07102015.img
...
- Skipping drmfix. Unsuppported/untested for model karin
...
Click to expand...
Click to collapse
OK, I see what is going on.
When I use drmonly script version 4.24 I get the following:
Code:
C:\Users\najoor\Desktop\rootkernel_v4.24_Windows_Linux>drmonly.cmd boot.img test.img TA-07102015.img
- Unpacking kernel
Found android boot image
- Unpacking initramfs
- 64-bit platfrom detected
- Configuring secd
- Configuring wvkbd
- Configuring drmserver
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
But if I use version 4.31:
Code:
C:\Users\shervin\Desktop\working\Download\rootkernel_v4.31_Windows_Linux>drmonly
.cmd boot.img x.img TA-07102015.img
- Unpacking kernel
Found android boot image
Kernel version: 3.10.84
- Detected vendor: somc (Sony), device: karin, variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 6.0
- Skipping drmfix. Unsuppported/untested for model karin
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
I have no idea why @tobias.waldvogel decided to remove the support for Tablet Z4 in the latest version of the drmonly script, but I can see that the DRM works fine with the old version.
I do not have persmission from @tobias.waldvogel to post the older version of his script here so you have to ask him to either add support in the new version or give you the older version.

Thanks - so now I see where is problem. I try contact with author.
Heh - I send PM him but it was my fault [added: it not totally fault - Tobias work on new version and soon we should have new working utility for all ]
I'm enough clever to modify script in 5 minutes (it txt ), and enough stupid to flash it immediately. Now I have....
rooted marshmallow with DRM KEY and TWRP - job finished
To finish job I disabled in settings auto-update, because now it start possible

FAILED <remote dtb not found>
Unlocked the bootloader and successfully retrieved TA partion with SGP771_28.0.A.8.260 , installed stock 32.1.A.1.185, tablet runs fine without problems.
Retrieving the boot.img from Z4T_SGP771_AndroPlusKernel_v27 for my SGP771 device and running
Code:
fastboot boot boot.img
gives
downloading 'boot.img' ...
OKAY [ 0.347s]
booting ....
FAILED <remote: dtb not found>
Click to expand...
Click to collapse
This happens even with the 32.1.A.1.185 stock boot.img. Tried on Kubuntu 16.04 and WIN7. Same result. When I flash
the AndroPlusKernel_v27 boot.img,
Code:
fastboot flash boot boot.img
finishes without errors and tablet does not boot any more but -thanks God- fastboot mode still functioning.
I am lost. Can not root my tablet . Any clues?
---------- Post added at 04:14 PM ---------- Previous post was at 03:41 PM ----------
Sorry, correction:
first retrieved TA partion, then unlocked bootloader.

Hybel1507 said:
Unlocked the bootloader and successfully retrieved TA partion with SGP771_28.0.A.8.260 , installed stock 32.1.A.1.185, tablet runs fine without problems.
Retrieving the boot.img from Z4T_SGP771_AndroPlusKernel_v27 for my SGP771 device and running
Code:
fastboot boot boot.img
gives
This happens even with the 32.1.A.1.185 stock boot.img. Tried on Kubuntu 16.04 and WIN7. Same result. When I flash
the AndroPlusKernel_v27 boot.img,
Code:
fastboot flash boot boot.img
finishes without errors and tablet does not boot any more but -thanks God- fastboot mode still functioning.
I am lost. Can not root my tablet . Any clues?
---------- Post added at 04:14 PM ---------- Previous post was at 03:41 PM ----------
Sorry, correction:
first retrieved TA partion, then unlocked bootloader.
Click to expand...
Click to collapse
Please follow the following steps exactly and let me know in what step things fail. If you do not provide detailed information I will not be able to help you.
1- Clean flash a 185 ftf and make sure system boots fine.
2- extract the kernel.elf from the ftf and I use fastboot to see if you can boot using fastboot with this kernel.
3- extract boot.img from AndroPlusKernel_v27 and see if you can use fastboot to boot with this image.
4- use the procedure in the OP to patch AndroPlus kernel and see if you can use fastboot to boot with this image.
5- flash this image using fastboot to see if the system boots fine.

** DISCLAIMER: I AM NOT A DEV AND THIS IS MY HOBBY. I ASSUME NO RESPONSIBILITY IF THIS BREAKS YOUR DEVICE **​
The following is tested on model E6553. This may work for the dual sim model too but I have not verified it. Do not flash the ftf and kernel files intended for one model onto another.​
I am not taking credit for any of the tools and kernels here. They are all developed by others. I am only telling you how to use them.
Credits: @zxz0O0, @tobias.waldvogel
0- Prerequisites
You need to have a functioning installation of adb and fastboot tools. You need to have proper Sony drivers installed on your PC to detect your phone when it is connected to the PC. You should be able to flash an ftf file using flashtool. If any of these sound unfamiliar to you, stop reading, go learn about them, and then come back.
1- How to unlock your bootloader without losing the DRM keys
Sony has designed this phone such that if you unlock your bootloader you lose your TA partition PERMANENTLY which includes some of the Xperia features and licenses that have to do with image processing etc. forever. You will also no longer receive OTAs. So in theory, without a copy of this TA partition (which is unique to each device and cannot be copied over from another) unlocking the bootloader results in an irreversible loss of some of your phone's features. Relocking the bootloader will not bring them back.
A hack exists that allows you to backup the TA partition before you unlock the bootloader. This backup will make the process completely reversible so if you ever need to send the tablet to Sony for repair or just want to return it to its original state you have a way. Follow these instructions carefully:
1.0- Before you begin keep in mind that this procedure, especially the unlocking step, completely erases your tablet. Disable myXperia and remove your google account before proceeding. The following will likely not work well with encryption.
1.1- Start by clean flashing any 28.0.A.8.266 firmware, For this tutorial I used the Customized NL ftf that you can get from here.
1.2- Enter service Mode by dialing *#*#7378423#*#* -> Service info -> configuration, and make sure the device is unlockable.
Also check -> Service Tests -> Security and you will see a bunch of "active" and "OK" attributes. You can take screenshots for your reference.
1.3- Turn on usb debugging mode on your phone.
1.4- Download iovyroot zip v0.4 or higher from here.
1.5- Unzip this zip file into a folder of your choice and open a command terminal there.
1.6- Connect the phone which is now in USB debugging mode to your PC and answer yes when the phone asks to authorize the PC to access it in USB debugging mode. You can check that the PC indeed sees the phone by running this command
Code:
adb devices
1.7- Run the following command:
Code:
tabackup
1.8- VERY IMPORTANT: Make sure the command completes with no errors. If all goes well you will have a file with a name like TA-05052016.img (the name may be different for you) with a size of 2MB in your folder.
1.9- Save this file in a very safe place. Save it on your hard disk, AND email it to yourself, AND put it on your google drive. If you lose this file you can never reverse the bootloader unlocking process.
1.10- Reboot the device.
1.11- Now you can unlock the bootloader. Follow the instructions at Sony's official website at http://developer.sonymobile.com/unlockbootloader Also save your unlock code that you obtain in this step somewhere. You may need it some day.
1.12- Reboot the device and it will briefly enter recovery and then start the phone initial setup.
1.13- (Optional) you can easily verify that your bootloader is unlocked by entering the fastboot mode, obtaining any boot image, and running the following command to boot your tablet with that image:
Code:
fastboot boot boot.img
1.14- (Optional) you can see that the DRM keys are erased from your tablet by repeating step 1.2 but this time you will see a bunch of errors under Service Tests -> Security.
1.15- As a side effect of unlocking the bootloader you lose the ability to receive OTA updates. Clean flash a Marshmallow ftf to continue. For this tutorial I used Marshmallow 6.0 E6553_Customized HK_1294-9654_32.1.A.1.185_R7C (the latest firmware at the time of this writing.)
2- How to emulate DRM keys and/or root and/or add recovery after unlocking the bootloader.
A hack exists that can emulate the DRM keys:
2.1- Extract the boot image from the 32.1.A.1.185 marshmallow ftf that you installed in step 1.15. Here are the steps to take:Open the ftf file with 7-zip or any zip program that you have at your disposal
Look for a file called kernel.sin and extract it.
Start flashtool and from Tools menu choose Sin Editor.
Select the kernel.sin that you extracted in the previous step and hit Extract data.
Flashtool will create a file called kernel.elf which you will use in the next step.​2.2- Download rootkernel_v4.42_Windows_Linux.zip (or a higher version) from http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 and unzip it in a folder of your choice.
2.3- Copy the kernel.elf that you got in step 2.1 to this folder. If you want root, follow this guide through to section 5 place SuperSU 2.71 (or higher) in this folder as well. Make sure the name of the SuperSU zip starts with letters "SuperSU". The latest SuperSU can be obtained from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (The rootkernel tool has a bug in its built-in SuperSU integration. See: http://forum.xda-developers.com/showpost.php?p=67485478&postcount=838)
2.4- Open a command terminal in this folder and run the rootkernel script. Your command should look similar to this:
Code:
rootkernel.cmd kernel.elf boot-patched.img
When prompted, answer as follows:- Sony RIC is enabled. Disable? [Y/n] Y (if you want root plus write access)
- Install TWRP recovery? [Y/n] Y (if you want to have recovery)
- Install busybox? [Y/n] Y (if you want busybox. It is very useful)
- Found SuperSU-v2.71-20160331103524.zip. Install? [Y/n] Y (if you want root)
- Install DRM fix? [Y/n] Y (if you want DRM emulation)​This will create a new kernel image called boot-patched.img which you will now flash on your phone.
2.5- Boot the phone in the fastboot mode and flash your patched image using the following fastboot command:
Code:
fastboot flash boot boot-patched.img
2.6- (Optional) You can reboot the phone and see that the DRM keys are indeed retrieved by repeating step 1.2. You can also open settings -> display, and look under Image Enhancement. If the DRM emulation is successful you will see this.
3- How to flash a custom or stock kernel
3.0- If you have already flashed the patched kernel in part 2 you will skip this part.
3.1- Whether you want to use a custom kernel or stock, and whether you have done the DRM patch described above or not, to flash a boot image (i.e. kernel) on your phone you need to restart the tablet in fastboot mode.
3.2- To flash the kernel use this command:
Code:
fastboot flash boot [I]name_of_your_kernel[/I]
You will replace name_of_your_kernel with whatever your kernel is called (e.g. boot.img, kernel.elf, etc.)
4- How to add and use recovery
4.1- Recovery is added to your kernel in step 2.4.
4.2- To enter recovery reboot the phone and touch the volume up key when the LED turns yellow during the boot splash screen.
5- How to root
5.1- Place SuperSU 2.71 zip (or higher) on the phone's sdcard. The latest SuperSU can be obtained from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
5.2- Reboot to recovery and flash the zip file.
6- How to relock bootloader and return it to original factory state
6.0- To relock the bootloader along with restoring the DRM keys the phone must have unmodified stock firmware.
6.1- Repeat step 1.1
6.2- Repeat steps 1.3, 1.4, and 1.5
6.3- Copy the TA backup image that you had obtained in section 1 in the iovyroot folder and use the tarestore command to flash the TA partition back onto the phone. The command will look similar to this:
Code:
tarestore TA-05052016.img
Make sure the command completes with no error. If it fails the first time try again. Reboot the phone. Your bootloader is now locked and your DRM keys restored.
6.4- (Optional) You can verify that you are back to the original locked state by repeating step 1.2.

Whoa Great
---------- Post added at 01:32 AM ---------- Previous post was at 12:50 AM ----------
najoor said:
** DISCLAIMER: I AM NOT A DEV AND THIS IS MY HOBBY. I ASSUME NO RESPONSIBILITY IF THIS BREAKS YOUR DEVICE **​The following is tested on model E6553. This may work for the dual sim model too but I have not verified it. Do not flash the ftf and kernel files intended for one model onto another.​I am not taking credit for any of the tools and kernels here. They are all developed by others. I am only telling you how to use them.
Credits: @zxz0O0, @tobias.waldvogel
0- Prerequisites
You need to have a functioning installation of adb and fastboot tools. You need to have proper Sony drivers installed on your PC to detect your phone when it is connected to the PC. You should be able to flash an ftf file using flashtool. If any of these sound unfamiliar to you, stop reading, go learn about them, and then come back.
1- How to unlock your bootloader without losing the DRM keys
Sony has designed this phone such that if you unlock your bootloader you lose your TA partition PERMANENTLY which includes some of the Xperia features and licenses that have to do with image processing etc. forever. You will also no longer receive OTAs. So in theory, without a copy of this TA partition (which is unique to each device and cannot be copied over from another) unlocking the bootloader results in an irreversible loss of some of your phone's features. Relocking the bootloader will not bring them back.
A hack exists that allows you to backup the TA partition before you unlock the bootloader. This backup will make the process completely reversible so if you ever need to send the tablet to Sony for repair or just want to return it to its original state you have a way. Follow these instructions carefully:
1.0- Before you begin keep in mind that this procedure, especially the unlocking step, completely erases your tablet. Disable myXperia and remove your google account before proceeding. The following will likely not work well with encryption.
1.1- Start by clean flashing any 28.0.A.8.266 firmware, For this tutorial I used the UK Generic ftf that you can get from here.
1.2- Enter service Mode by dialing *#*#7378423#*#* -> Service info -> configuration, and make sure the device is unlockable.
Also check -> Service Tests -> Security and you will see a bunch of "active" and "OK" attributes. You can take screenshots for your reference.
1.3- Turn on usb debugging mode on your phone.
1.4- Download iovyroot zip v0.4 or higher from here.
1.5- Unzip this zip file into a folder of your choice and open a command terminal there.
1.6- Connect the phone which is now in USB debugging mode to your PC and answer yes when the phone asks to authorize the PC to access it in USB debugging mode. You can check that the PC indeed sees the phone by running this command
Code:
adb devices
1.7- Run the following command:
Code:
tabackup
1.8- VERY IMPORTANT: Make sure the command completes with no errors. If all goes well you will have a file with a name like TA-05052016.img (the name may be different for you) with a size of 2MB in your folder.
1.9- Save this file in a very safe place. Save it on your hard disk, AND email it to yourself, AND put it on your google drive. If you lose this file you can never reverse the bootloader unlocking process.
1.10- Reboot the device.
1.11- Now you can unlock the bootloader. Follow the instructions at Sony's official website at http://developer.sonymobile.com/unlockbootloader Also save your unlock code that you obtain in this step somewhere. You may need it some day.
1.12- Reboot the device and it will briefly enter recovery and then start the phone initial setup.
1.13- (Optional) you can easily verify that your bootloader is unlocked by entering the fastboot mode, obtaining any boot image, and running the following command to boot your tablet with that image:
Code:
fastboot boot boot.img
1.14- (Optional) you can see that the DRM keys are erased from your tablet by repeating step 1.2 but this time you will see a bunch of errors under Service Tests -> Security.
1.15- As a side effect of unlocking the bootloader you lose the ability to receive OTA updates. Clean flash a Marshmallow ftf to continue. For this tutorial I used Marshmallow 6.0 E6553_Customized HK_1294-9654_32.1.A.1.185_R7C (the latest firmware at the time of this writing.)
2- How to emulate DRM keys and/or root and/or add recovery after unlocking the bootloader.
A hack exists that can emulate the DRM keys:
2.1- Extract the boot image from the 32.1.A.1.185 marshmallow ftf that you installed in step 1.15. Here are the steps to take:
Open the ftf file with 7-zip or any zip program that you have at your disposal
Look for a file called kernel.sin and extract it.
Start flashtool and from Tools menu choose Sin Editor.
Select the kernel.sin that you extracted in the previous step and hit Extract data.
Flashtool will create a file called kernel.elf which you will use in the next step.​2.2- Download rootkernel_v4.42_Windows_Linux.zip (or a higher version) from http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 and unzip it in a folder of your choice.
2.3- Copy the kernel.elf that you got in step 2.1 to this folder. If you want root, place SuperSU 2.71 (or higher) in this folder as well. Make sure the name of the SuperSU zip starts with letters "SuperSU". The latest SuperSU can be obtained from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
2.4- Open a command terminal in this folder and run the rootkernel script. Your command should look similar to this:
Code:
rootkernel.cmd kernel.elf boot-patched.img
When prompted, answer as follows:
- Sony RIC is enabled. Disable? [Y/n] Y (if you want root plus write access)
- Install TWRP recovery? [Y/n] Y (if you want to have recovery)
- Install busybox? [Y/n] Y (if you want busybox. It is very useful)
- Found SuperSU-v2.71-20160331103524.zip. Install? [Y/n] Y (if you want root)
- Install DRM fix? [Y/n] Y (if you want DRM emulation)​This will create a new kernel image called boot-patched.img which you will now flash on your phone.
2.5- Boot the phone in the fastboot mode and flash your patched image using the following fastboot command:
Code:
fastboot flash boot boot-patched.img
2.6- (Optional) You can reboot the phone and see that the DRM keys are indeed retrieved by repeating step 1.2. You can also open settings -> display, and look under Image Enhancement. If the DRM emulation is successful you will see this.
3- How to flash a custom or stock kernel
3.0- If you have already flashed the patched kernel in part 2 you will skip this part.
3.1- Whether you want to use a custom kernel or stock, and whether you have done the DRM patch described above or not, to flash a boot image (i.e. kernel) on your phone you need to restart the tablet in fastboot mode.
3.2- To flash the kernel use this command:
Code:
fastboot flash boot [I]name_of_your_kernel[/I]
You will replace name_of_your_kernel with whatever your kernel is called (e.g. boot.img, kernel.elf, etc.)
4- How to add and use recovery
4.1- Recovery is added to your kernel in step 2.4.
4.2- To enter recovery reboot the phone and touch the volume up key when the LED turns yellow during the boot splash screen.
5- How to relock bootloader and return it to original factory state
5.0- To relock the bootloader along with restoring the DRM keys the phone must have unmodified stock firmware.
5.1- Repeat step 1.1
5.2- Repeat steps 1.3, 1.4, and 1.5
5.3- Copy the TA backup image that you had obtained in section 1 in the iovyroot folder and use the tarestore command to flash the TA partition back onto the phone. The command will look similar to this:
Code:
tarestore TA-05052016.img
Make sure the command completes with no error. If it fails the first time try again. Reboot the phone. Your bootloader is now locked and your DRM keys restored.
5.4- (Optional) You can verify that you are back to the original locked state by repeating step 1.2.
Click to expand...
Click to collapse
Very usefull step by step guide.. But is there is any method to root phone without unlocking Bl? Quite curious to know from you.

arokososoo said:
Whoa Great
---------- Post added at 01:32 AM ---------- Previous post was at 12:50 AM ----------
Very usefull step by step guide.. But is there is any method to root phone without unlocking Bl? Quite curious to know from you.
Click to expand...
Click to collapse
Not yet, atleast for my Dual SIM Version.

njaya95 said:
Not yet, atleast for my Dual SIM Version.
Click to expand...
Click to collapse
So you mean there is a way to root single sim version without unlocking BL?

Thanks ú so much! this is well writen, i will try this when i get the time to do a fresh install. Cheers mate

@arokososoo
Please, in the future never quote long OP and any other long posts. This is very annoying for mobile and desktop users to scroll to the next post. Thanks.
Sent from my Sony E6553 using XDA Labs

I wonder if E6533 can use this guide

Got as far as going to the sony website, there's no mention of phones that can be unlocked there and for some reason Ive got bootloader unlock allowed no, even with a sim free phone and my xperia turned off.....bummer

Stoneybridge said:
Got as far as going to the sony website, there's no mention of phones that can be unlocked there and for some reason Ive got bootloader unlock allowed no, even with a sim free phone and my xperia turned off.....bummer
Click to expand...
Click to collapse
I also unlocked my Z3+, although it wasn't supported. I just picked Z4 Tablet since it is the "nearest" one. Worked Got MM rooted now.

How long did that take on your devices? 1.1- Start by clean flashing any 28.0.A.8.266 firmware, For this tutorial I used the UK Generic ftf that you can get from here.
I am waiting for half an hour now...
Spoiler

Trilliard said:
How long did that take on your devices? 1.1- Start by clean flashing any 28.0.A.8.266 firmware, For this tutorial I used the UK Generic ftf that you can get from here.
I am waiting for half an hour now...
Spoiler
Click to expand...
Click to collapse
I can't see your picture, but I assume you have that stucking at modem/system ?
If so, downgrade Flashtool to 0.9.19

Well i got a soft brick, but was able to restore it trough Sony Companion. Here is the picture on another hoster http://fs5.directupload.net/images/160529/gr5fpf8t.png dont know on what point it stuck.
Funfact that two germans writting in english
Edit, big thanks version 0.9.19 worked perfect. Cant understand why the newest one doesnt work
Edit 2: System boots up, but when the setup start the process com.android.phone stops instant and if i hit ok the message comes instantly again after about ten times the phone reboot, i cant do anything else... next repair through sony companion and back to stock german 6.0. I´ll stop try it for today.

Trilliard said:
Well i got a soft brick, but was able to restore it trough Sony Companion. Here is the picture on another hoster http://fs5.directupload.net/images/160529/gr5fpf8t.png dont know on what point it stuck.
Funfact that two germans writting in english
Edit, big thanks version 0.9.19 worked perfect. Cant understand why the newest one doesnt work
Edit 2: System boots up, but when the setup start the process com.android.phone stops instant and if i hit ok the message comes instantly again after about ten times the phone reboot, i cant do anything else... next repair through sony companion and back to stock german 6.0. I´ll stop try it for today.
Click to expand...
Click to collapse
Did you forget to wipe?

In a thread i opened in Q&A a user said that even though service info reported bl unlock allowed NO, he managed to unlock it anyways using standard procedure, what do you think?

it seems like Sony RIC is not fully disabled with this patch.

Finally ! Works like a charm in my E6533 (Dual sim) !!! Thanks a lot !!!

Hi thiefxhunter,
How you do this? could you explain us step by step. I like to root my dual sim model.
Thanks.

Hi.. I am stuck in 2.5
My device is unlocked, It is connected in fastboot mode (blue led).
error msg
'Fastboot is not recognised as an internal or external command, operable program or batch file'
Please help me in this.
Solved..
Thanks for this post..

Thanks for this guide, it worked like a charm on my E6553 with 32.2.A.0.224

CorzCorry said:
I also unlocked my Z3+, although it wasn't supported. I just picked Z4 Tablet since it is the "nearest" one. Worked Got MM rooted now.
Click to expand...
Click to collapse
Can you please explain how did you do that? Thanks

DEVICE XPERIA X - PROJECT NAME SUZU - VARIANTS F5121 & F5122 (DUAL)​
WhatsApp Group[PLEASE PM ME] for Xperia X (ENGLISH ONLY) by@hhjadeja007
A BIG THANKS TO @serajr & @sToRm// and ofcourse @tobias.waldvogel
#DETAILED KNOWLEDGE BASE GUIDE FOR XPERIA 2018 MODELS / THANKS TO @DHGE
Similar Noob Version / DrmKeys, TA, unLock & Lock Bootloader (XPERIA XZ) thanks @nathan30
MAGISK GUIDE THANKS TO @Didgeridoohan
and FINALLY @Chippa_a for TWRP 3.2.2
____________________________________________________________
IF YOU KNOW THE BASICS THEN PROCEED BELOW , OTHERWISE R E A D - H E R E
-OREO KERNELS
ROOT DIRECTORY XPERIA X SUZU
"Xperia X UPDATE" ON -25-SEPTEMBER-2018 -- 34.4.A.2.118 F5121 & F5122 NEW
"Xperia X UPDATE" ON -22-AUGUST-2018 -- 34.4.A.2.107 F5121 & F5122
"Xperia X UPDATE" ON -18-JULY-2018 -- 34.4.A.2.97 F5121 & F5122
"Xperia X UPDATE" ON -14-JUNE-2018 -- 34.4.A.2.85 F5121 & F5122
"Xperia X UPDATE" ON -09-MAY-2018 -- 34.4.A.2.70 F5121 & F5122
"Xperia X UPDATE" ON -10-APRIL-2018 -- 34.4.A.2.50 F5121 & F5122
"Xperia X UPDATE" ON -15-MARCH-2018 -- 34.4.A.2.32 F5121 & F5122
"Xperia X UPDATE" ON -26-FEB-2018 --34.4.A.2.19 F5121 & F5122
"Xperia X UPDATE" ON -06-FEB2018 -- 34.4.A.0.364 F5121 & F5122 - thanks to @Gray47Maxx
-------------------> INSTRUCTIONS <-----------------
1. Paste the following on your sd OR USB OTG AND KEEP IT ASIDE
-DRM-Fix_System_Mode.zip
-Magisk.zip
-FCS_thermal_Xperia_X_V.1.8.zip (optional)
2. FLASH THE LATEST ROM VIA FLASHTOOL , if DURING FLASHING you get script error then
2B. Paste 34.4.fsc from folder1 to [C:\Users\<username>\.flashTool\devices\F51XX] and try TRY flashing again.
3. boot you device in to OREO , enable USB DEBUGGING and Switchoff you device
4. Flash KERNEL " F512X_34.4.A.X.X_CLEAN.img" using FLASHTOOL (fastboot MODE) and unplug device.
5. Paste the " twrp-3.1.1-suzu-2017.08.22.img " (Recovery image) at C:\Program Files (x86)\Minimal ADB and Fastboot & name it something simple such as boot.img. CONNECT DEVICE IN FASTBOOT MODE AGAIN & FLASH Recovery via following FASTBOOT command ("fastboot flash recovery twrp.img" & enter. Once Done; remove cable and after few seconds ......
6. press POWER and VOLUME DOWN keys and HOLD until you are taken to TWRP.
6B. TWRP 3.x.x will ask decryption password, click back and DO - THIS - STEP - THANKS TO @Jomoteck
7A. NOW from SDCARD OR USBOTG flash the items in the same sequence given ABOVE ( DRM-Fix_System_Mode.zip / then Magisk.zip)
7B. FLASH - FCS_thermal_Xperia_X_V.1.3.zip (optional) and
8. clear cache / delvik cache and and switch-off device (DO NOT PROMPT INSTALL TWRP)
9. after a while switch on device. first reboot may take a while and you may face bootloop (atleast once)
10. install magisk_5.X.apk (magisk manager withing android)
11. install rootcheck_615.apk and check the Root access. (optional)
ADDITIONAL STEPS I DO
12. INCREASE VOLUME--replace "mixer_paths_wcd9335.xml" file from /system/etc for HIGH VOLUME AND RINGTONE (TAKE BACKUP OF THE ORIGINAL ONE) (I USE FX EXPLORER
13. ENABLE NIGHTLIGHT FILTER
---- first flash given Night_Light.zip via TWRP and reboot, check if the control appears or not, if NOT then
-- Install Given "android-res-night.apk"; then connect device to pc (via usb cable) and ran the following command on "Minimal Adb & Fastboot Window"
Code:
"adb shell cmd overlay enable --user 0 android.res.night"
nightlight will work after you next reboot PREVIEW NIGHTLIGHT
14. SOME MODULES IN MAGISK --- > "UPDATE" -GOOGLE PLAY SERVICES --> OPEN MAGISK--> FLASH MODULES
15 "UPDATE" Magisk manager 5.6x & then "Xperia X UPDATE" ON -Magisk module to 16.x (direct install) --- N O W. R.E.B.O.O.T. ---
-------- REMOVING BLOATWARE-------
----(A)------------SCRIPT METHOD -------------
16A. make sure usb debugging is ON, connect your device via cable to pc and UNZIP GIVEN "v1.8_Xperia_X_Debloat_By_Serajr_Combined.zip" AND RUN THE BAT FILE- ( read the instructions CAREFULLY ( -----READ HERE-------- ) ) ---- it will prompt permission & then superUser Permission. Grant BOTH ----- the device will reboot and ALL THE BLOATWARE WILL BE VOIDED
16B. after reboot you may get app crashing prompt. SWITCH-OFF device
16C. reboot to twrp and again clean cache and Delvik cache and SWITCH-OFF device
16D. reboot and delete "_debloat_backup" folder (size 1.7gb) from /system by using any GOOD ROOT EXPLORER APP ( I use FX Explorer)
16E. Mr @venomxob has cofirmed that by updating SOFTWARE "Xperia X UPDATE" ON -APP in OREO, fixes the annoying App Crash Popups DOWNLOAD HERE
16E. FROM "Developer Options" disable animation affects for speedy performance
----(B)----------MANUAL METHOD--------------
MAKING SYSTEM WRITABLE to REMOVE BLOATWARE / SYSTEM APP
In order to to remove system App and Bloatware you must make /system partition writable
17A .install busybox (run it and install it in system) and then
17B.install terminal, later type these lines ( no CAPS) and enter one by one in #terminal
Code:
su (grant su access)
busybox mount -o rw,remount,rw /system
17C. FOR OREO THIS BUSYBOX WORKED FOR ME - CLICK HERE
17D. SYSTEM APP UNINSTALLER WORKED FOR ME ON BOTH NOUGAT & OREO CLICK HERE
17E. I PREFER FREEZING SOME CORE SONY APPS WITH THIS APP CLICK HERE
SOME VALUE ADDING APPS I USE
1. YMUSIC ( MP3 Player/downloader for YOUTUBE) CLICK HERE
2. BROMITE (PowerFul Fast Chrome Browser without Tracking ) CLICK HERE
3. LATEST XPERIA HOME APP (3D TOUCH) CLICK HERE
4. OGYOUTUBE (modded Youtube player) CLICK HERE
5. ADBLOCKER (Adaway) CLICK HERE
<_______________________________________________________________________________________________________>
-NOUGAT KERNELS
"Xperia X UPDATE" ON -06DEC2017--34.3.A.0.252 - F5121 & F5122Best Build
"Xperia X UPDATE" ON -09NOV2017--34.3.A.0.244 - F5121 & F5122
"Xperia X UPDATE" ON -04OCT2017 -- 34.3.A.0.238 - F5121 & F5122
"Xperia X UPDATE" ON -08SEP2017-- 34.3.A.0.228 - F5121 & F5122
"Xperia X UPDATE" ON -08AUG2017- 34.3.A.0.217 - F5121 & F5122
"Xperia X UPDATE" ON -12JULY2017 -- 34.3.A.0.206 - F5121 & F5122
"Xperia X UPDATE" ON -23JUNE2017 -- 34.3.A.0.194 - F5121 & F5122
"Xperia X UPDATE" ON -11MAY2017 -- 34.2.A.2.69 - F5121 & F5122
"Xperia X UPDATE" ON -22APR2017 -- 34.2.A.2.27 - F5121 & F5122
GENERAL METHOD (NOUGAT KERNELS)
34.2.A.2.27 / 34.2.A.2.69 / 34.3.A.0.194 / 34.3.A.0.206
34.3.A.0.217 / 34.3.A.0.228 / 34.3.A.0.244/ 34.3.A.0.238
& 34.3.A.0.252
The Process of Flashing these Nougat Kernels and Obtaining Root Access for is SAME as Described ABOVE (for Oreo Kernels) EXCEPT FOLLOWING TWO THINGS
1. DO NOT FLASH "DRM-Fix_System_Mode.zip"
2. FLASH THE bloatware removal script, [v1.8_Xperia_X_Debloat_By_Serajr_Combined.zip], IT works just fine on Nougat.
--------------------------------------------------------------------------------------------------------------------------------------------------
- MARSHMALLOW KERNELS
"Xperia X UPDATE" ON -29APR2016 -- 34.0.A.1.264 (GENERIC & NORDIC) - F5121 & F5122
METHOD ( MARSHMALLOW KERNELS) 34.0.A.1.264
The Process of Flashing MARSHMALLOW Kernel and Obtaining Root Access for is SAME as Described ABOVE (for Oreo Kernels) EXCEPT FOLLOWING TWO THINGS
1. DO NOT FLASH "DRM-Fix_System_Mode.zip"
2. FLASH THE bloatware removal script, [v1.8_Xperia_X_Debloat_By_Serajr_Combined.zip], IT works just fine on Nougat.
​
<<<<---------------------------------------------------------------------------------------------------------------->>>
​HASTAGS : #F5122 #F5121 #ROOT #XPERIAX #STOCK #MODIFIED #KERNELS #STOCKKERNES #

所以 这是一个好消息。

LuxferreX said:
所以 这是一个好消息。
Click to expand...
Click to collapse
I don't know your language sir, but as per google I believe you typed " So it's good news."
so the answer is YES
however this forum is in English, please try to communicate in English because most of the knowledge-base is in English on XDA

I joined this forum to thank you very much. This not only works but restored my camera app which was crashing to launcher last time I attempted to root in MM. It caused the camera app to freeze and crash out even after with software repair and Sony said to send it back then said they didn't want to fix it because I unlocked the bootloader. (Camera worked in other apps etc.)
So not only do I now have root on Nougat but my camera app works too. You're brilliant!
YasuHamed said:
[*]type command
Code:
fastboot flash twrp3.1.img
( assuming you put twrp3.1.img in the minimal adb folder)
Click to expand...
Click to collapse
Actually not quite:
Code:
fastboot flash recovery twrp3.1.img
That should do it. =)

evilicious_evil said:
I joined this forum to thank you very much. This not only works but restored my camera app which was crashing to launcher last time I attempted to root in MM. It caused the camera app to freeze and crash out even after with software repair and Sony said to send it back then said they didn't want to fix it because I unlocked the bootloader. (Camera worked in other apps etc.)
So not only do I now have root on Nougat but my camera app works too. You're brilliant!
Actually not quite:
Code:
fastboot flash recovery twrp3.1.img
That should do it. =)
Click to expand...
Click to collapse
Thank you @evilicious_evil for
1. correcting the code , i have fixed it
2. liking the post and
3. most important for the AdsFree
I know you will enjoy your device because I just couldn't love it more!

im stuck with downgrade step. im new to xperia and really want to root my device but im nougat now due to system update. kindly give steps on how to downgrade. so i can backup my drm keys.

BASICS
1. SONY XPERIAS are SHIPPED with LOCKED BOOTLOADERS with PASSWORD / (UNLOCK KEY)
2. First check your device whether SONY will ever allow you to unlock your bootloader or not? DIAL *#*#7378423#*#* / SERVICE INFO > / Configuration > / and check for "ROOTING STATUS: Bootloader unlocked allowed: " ... if it says NO then you better return your device back to sony. your phone can never be bootunlocked and you can never have root access. Better give the mobile to young sibling...
Hoever if "ROOTING STATUS: Bootloader unlocked allowed: " says YES then we can do the magic (see attached image)
BEFORE YOU UNLOCK BOOTLOADER DOWNGRADING TO 6.01 is MUST - this step will WIPE everything in your device
- GUIDE TO USE FLASHTOOL TO FLASH ANY FIRMWARE (DOWNGRADING TO ANDROID 6)
MAKE SURE ALL DRIVERS ARE INSTALLED
INSTALL SONY PC COMPANION / XPERIA COMPANION and Make FIRST CONNECTION to WINDOWS PC to XPERIA X while running sony pc companion or xperia companion and it will install necessary drivers.
-switch-off xperia X and plug usb in while holding the volume UP key (BLUE LED / FASTMODE) and let your windows install fastboot drivers.
- remove usb, and afte few seconds connect usb again while pressing VOLUME DOWN Key (Green LED / FLASHMODE) and let your windows install flashmode drivers
Click to expand...
Click to collapse
Install FLASHTOOL from http://www.flashtool.net/downloads_windows.php and install it / after installation
1. upgrade the version from 0.9.23.1 to 0.9.23.X by replacing x10flasher.jar files (given in that page) at C:\Flashtool
2. goto C:\Flashtool\drivers and install the setup! there will be many check boxes for you to see according to your sony devices. select common fastboot/flashmode drivers and sony Xperia X motherboard drivers (sa0107)
3. run flastool. run xperifirm (last button at right) (see image)
4. once xperifirm is run select your device SUZU >F5122 (see image)
5. now you will all the countries listed and the latest android versions they have pushed. if you see at the bottom the StoreFront/Service Exchange Unit and Commercial journalist will have the FIRST EVER version on which F5122 was created. the 34.0.A.1.264 is your version. you may install commercial journalist version (see image)
6. download it and once completed close the xperifirm and IMMEDIATELY flashtool will start creating FTF file. if it asks you anything about INCLUDING FSC SCRIPT / click YES
7. click the THUNDER BUTTON and select FLASHMODE (see image)
8. point out on the ftf firmare folder (in your case since you just downloaded it will be already be at right place) (see image) and
9. make a CLEAN FLASH (SEE IMAGE CAREFULLY)
10. click flash / it will take 10 mins to prepare flashfiles and
11. will prompt you to connect your device in FLASHMODE
12. makesure your xperia is switch OFF and now make a connection of your device in flashmode (plugin usb + vol down key (hold) (green led)
13. it will read you device and will start FLASHING / DONOT MOVE SHAKE device incase if usb connection looses your device may be bricked.
14 flashing takes 20-30 mins.
15. at 99% the flashtool seems to hang (while closing headers) and may take upto 15 mins. don't panic.
16. keep reading the screen / once flashing done/ flashtool will indicate.
17. boot your device, first boot may take several mins
congratulations your f5122 is successfully downgraded to ANDROID MM
Enable usb debugging from developer options and EXTACT DRM keys via DIRTYCOW script.
SAVING DRM KEYS
1. DOWNLOAD THE Universal (Dirtycow-based) TA Backup v2 FROM THIS POST
2. EXTRACT the zip on desktop and connect your xperia X running on android 6 / boot LOCKED
3. enable usb debugging under developeroptions
4. run the .BAT file and look at the device.
5. when prompt permission, grant it
6. the script will extract .img file in that same folder having name something like "TA_F512X_<code>_<ddmmyy><timestamp>.img" , you may run the script more than once to extract same copy of TA image. the script will keep saving it in the same folder with current time stamp as part of the file name ,
I ran the script thrice
7. once done SAVE THE .IMG FILES ON SAFE PLACE, CLOUD STORAGE, EMAIL, ETC , use xperifirm again to download the LATEST BUILD and FLASH it via FLASHTOOL as described ABOVE in the flashtool section.
8. once you are on OREO or Nougat, its time to UNLOCK your BOOTLOADER,
UNLOCKING BOOTLOADER SONY XPERIA (DRM KEYS) TA.IMG
PLEASE SEE THE COMPLETE @DHGE #GUIDE FOR XPERIA 2018 MODELS AT https://forum.xda-developers.com/showpost.php?p=70504721 / THANKS TO @DHGE
you may also consider viewing NOOB version for XZ by @nathan30 https://forum.xda-developers.com/xperia-xz/how-to/how-to-unlock-bl-kernel-twrp-root-t3541648
IN SHORT----
To be able to unlock your Xperia X, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning: Device protection features will not work on this device while this setting is turned on.Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked. Continue to http://developer.sonymobile.com/unlo...-verification/ , give your email ID and they will send you link asking you your device's IMEI Number. once you give that sony will email you YOUR BOOTUNLOCK KEYS within minutes. (keep them aside for now)
-using FlashTool "BLU" key you can unlock your bootloader
- your TA partitions / internal storage will be WIPED and device will rebooted.

Thanks alot sir!!
honestly im so excited to root thats why i never even bother to read carefully..
to make story short.. i manage to unblocked BT (w/o downgrading and backing up DRM keys) so lesson learned..
then tried flashing your ( image boot_su_34.2.A.2.47.IMG ) to have root and drmfix as well so everything is okay until i tried to play my favorite game MObile legends and try to use PS3 controller using six axis. ( this is the main reason why i unlook and root) but i failed. so i started thinking maybe i made it all wrong. so i tried to go back unroot and relock using videos and guides online and ending up with a dead xperia x ten i managed to solved it by relocking first and software repair via sony companion and every thing is okay except the camera..
---------- Post added at 12:16 PM ---------- Previous post was at 12:11 PM ----------
now i want MM and drm fix.. question is can i flash your ( image boot_su_34.2.A.2.47.IMG) on MM??
the reason i want MM is that i think its compatible with the game and for me to use ps3 controller
---------- Post added at 12:54 PM ---------- Previous post was at 12:16 PM ----------
or if not can you make a kernel for MM with DRM fix? please

sorry sir i have alot of questions i really wanted to fix my phone. so i will follow all the steps you said but upon installing flashtool and drivers i cant seem to find this (sony Xperia X motherboard drivers (sa0107) ) in the list. i dont want to skip this since i don want to encounter any problems again the way i did last time. Will it be okay to skip this?

jhendsantos said:
honestly im so excited to root thats why i never even bother to read carefully..
to make story short.. i manage to unblocked BT (w/o downgrading and backing up DRM keys) so lesson learned..
then tried flashing your ( image boot_su_34.2.A.2.47.IMG ) to have root and drmfix as well so everything is okay until i tried to play my favorite game MObile legends and try to use PS3 controller using six axis. ( this is the main reason why i unlook and root) but i failed. so i started thinking maybe i made it all wrong. so i tried to go back unroot and relock using videos and guides online and ending up with a dead xperia x ten i managed to solved it by relocking first and software repair via sony companion and every thing is okay except the camera..
---------- Post added at 12:16 PM ---------- Previous post was at 12:11 PM ----------
now i want MM and drm fix.. question is can i flash your ( image boot_su_34.2.A.2.47.IMG) on MM??
the reason i want MM is that i think its compatible with the game and for me to use ps3 controller
---------- Post added at 12:54 PM ---------- Previous post was at 12:16 PM ----------
or if not can you make a kernel for MM with DRM fix? please
Click to expand...
Click to collapse
Good day sir
since I proof read and fixed grammatical errors , your thank is void, plz thanks again
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
...................................
Seems like you have a Full Plate of Experiences with your Xperia X
1. once unlocked, i highly recommend not to re lock the boot loader unless you are selling your device
2. If at any point xperia X is bricked, holding POWER+VOLUME UP key for
-----(a) five seconds will REBOOT the device after 1 JERK
------(b) Fifteen secons will JERK your device THRICE and on second jerk, YOU MUST remove your fingers from power+volumeUP keys and it will make your device SHUTDOWN so that you can reconnect it in FLASHMODE and do the magic again
3. I don't have knowledge about connecting PS3 to XPERIAS but SONY cannot release Android N without checking compatibility of already sold SP3.... so what i can suggest is to find approperiate app on playstore to connect with Ps3 and/or google more on this subject
4. keep your TA IMAGE INTACT / saved / email yourself / back it up on cloud for future use.
5. for you i have created SIMILAR KERNAL for android 6.01 BUILD 34.0.A.1.264 , having superSU
6. using flashtool perform CLEAN flash and send the kernel to your device.
7. I am giving you original STOCK KERNEL SIN file "original_stock_kernel_F5122_34.0.A.1.264.sin" if the modified kernel gives you bootloops OR you have bricked F5122 atleast you dont have to reflash everything. just flash the kernel in fastbootmode and you device will wakeup
https://mega.nz/#F!7UZBiYDI!t7ieYMwHUNsAC5T9iHpyQQ

jhendsantos said:
sorry sir i have alot of questions i really wanted to fix my phone. so i will follow all the steps you said but upon installing flashtool and drivers i cant seem to find this (sony Xperia X motherboard drivers (sa0107) ) in the list. i dont want to skip this since i don want to encounter any problems again the way i did last time. Will it be okay to skip this?
Click to expand...
Click to collapse
yes seems like all drivers are installed
kindly skip

YasuHamed said:
Good day sir
since I proof read and fixed grammatical errors , your thank is void, plz thanks again
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
...................................
Seems like you have a Full Plate of Experiences with your Xperia X
1. once unlocked, i highly recommend not to re lock the boot loader unless you are selling your device
2. If at any point xperia X is bricked, holding POWER+VOLUME UP key for
-----(a) five seconds will REBOOT the device after 1 JERK
------(b) Fifteen secons will JERK your device THRICE and on second jerk, YOU MUST remove your fingers from power+volumeUP keys and it will make your device SHUTDOWN so that you can reconnect it in FLASHMODE and do the magic again
3. I don't have knowledge about connecting PS3 to XPERIAS but SONY cannot release Android N without checking compatibility of already sold SP3.... so what i can suggest is to find approperiate app on playstore to connect with Ps3 and/or google more on this subject
4. keep your TA IMAGE INTACT / saved / email yourself / back it up on cloud for future use.
5. for you i have created SIMILAR KERNAL for android 6.01 BUILD 34.0.A.1.264 , having superSU
6. using flashtool perform CLEAN flash and send the kernel to your device.
7. I am giving you original STOCK KERNEL SIN file "original_stock_kernel_F5122_34.0.A.1.264.sin" if the modified kernel gives you bootloops OR you have bricked F5122 atleast you dont have to reflash everything. just flash the kernel in fastbootmode and you device will wakeup
https://mega.nz/#F!7UZBiYDI!t7ieYMwHUNsAC5T9iHpyQQ
Click to expand...
Click to collapse
----
WOW!! many thanks sir!! will keep this kernel for sure!!
about TA IMAGE -- its DRM keys right i think i lost it already since i unlock BL w/o downgrading to MM and backing it up.:laugh:
----
i unlocked BL again via official way= camera works
flash twrp via minimal adb (to root and flash rom) first boot is as far as i remember it went well, tried to boot to twrp again and was prompted to install TWRP APPS (since i dont understand that) i install and reboot but this time my device wont boot it shows sony logo twice and then this warning : YOUR DEVICE IS CORRUPTED AND CANNOT BE TRUSTED. AND MAY NOT FUNCTION PROPERLY... PRESS POWER TO BOOT but upon pressing power device wont boot
--what seems to be the problem??
--tried to boot to twrp again and wipe dalvik/cache/ = same error
--tried to reflash recovery.img via minimal adb = same error
by the way im a MISS

jhendsantos said:
----
WOW!! many thanks sir!! will keep this kernel for sure!!
about TA IMAGE -- its DRM keys right i think i lost it already since i unlock BL w/o downgrading to MM and backing it up.:laugh:
----
i unlocked BL again via official way= camera works
flash twrp via minimal adb (to root and flash rom) first boot is as far as i remember it went well, tried to boot to twrp again and was prompted to install TWRP APPS (since i dont understand that) i install and reboot but this time my device wont boot it shows sony logo twice and then this warning : YOUR DEVICE IS CORRUPTED AND CANNOT BE TRUSTED. AND MAY NOT FUNCTION PROPERLY... PRESS POWER TO BOOT but upon pressing power device wont boot
--what seems to be the problem??
--tried to boot to twrp again and wipe dalvik/cache/ = same error
--tried to reflash recovery.img via minimal adb = same error
by the way im a MISS
Click to expand...
Click to collapse
1. you need recovery only when you want to flash superSU ,
2. since the kernel i have given in previous post and in the OT have SuperSU flashed, then you don''t need recovery.
please tell me when you flashed twrp,
1. why? for what purpose
2. did you flash the modified kernel also? (before flashing twrp)
3. if you did not flash modified kernel and have flashed twrp and via twrp you have flashed supersu... this means you put recovery on stock kernel and modified /SYSTEM
4. such action will always give you bootloops or "your device is corrupt... error" becuase DM VARITY is active in the stock kernel
simply flash the kernel i provided (having supersu) and wake you device up ROOTED.

YasuHamed said:
1. you need recovery only when you want to flash superSU ,
2. since the kernel i have given in previous post and in the OT have SuperSU flashed, then you don''t need recovery.
please tell me when you flashed twrp,
1. why? for what purpose
2. did you flash the modified kernel also? (before flashing twrp)
3. if you did not flash modified kernel and have flashed twrp and via twrp you have flashed supersu... this means you put recovery on stock kernel and modified /SYSTEM
4. such action will always give you bootloops or "your device is corrupt... error" becuase DM VARITY is active in the stock kernel
simply flash the kernel i provided (having supersu) and wake you device up ROOTED.
Click to expand...
Click to collapse
.
----
thanks sir problem solved i just flashed Poison v2.1 since twrp seems to be working.. tried my luck and its a success.

Im new user of Xperia X, can anyone please explain me what are drm keys for, and what will go wrong in case i dont back them up before rooting my device? Thank you in advance

sleeper994 said:
Im new user of Xperia X, can anyone please explain me what are drm keys for, and what will go wrong in case i dont back them up before rooting my device? Thank you in advance
Click to expand...
Click to collapse
DRM keys are unique to your device and stored on your TA partition. If you unlock your bootloader, they are wiped and they will not be restored if you relock. As a result, some camera functions will be impaired (e.g. photos taken in darkish conditions will be noisy) as well as X-reality (image enhancement). You can backup your own TA by making use of the dirty cow vulnerability in marshmallow. This​ allows you to restore your phone to its original state if you want to go back to stock. In addition you can use your TA to modify your kernel to make your unlocked phone think its drm keys are still intact.

Hi, Does it apply the F5121?

M1chiel said:
DRM keys are unique to your device and stored on your TA partition. If you unlock your bootloader, they are wiped and they will not be restored if you relock. As a result, some camera functions will be impaired (e.g. photos taken in darkish conditions will be noisy) as well as X-reality (image enhancement). You can backup your own TA by making use of the dirty cow vulnerability in marshmallow. This​ allows you to restore your phone to its original state if you want to go back to stock. In addition you can use your TA to modify your kernel to make your unlocked phone think its drm keys are still intact.
Click to expand...
Click to collapse
So, basically I can backup drm keys, root my phone, restore keys, and all functions would be stock-like while phone is still rooted?

Nope, restoring your TA will lock your bootloader and therefore unroot. But you can modify your kernel to make your phone think the DRM keys are still there. Check e.g. https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Edit: It actually will not allow booting since the system or the boot partition were modified.

sangbb said:
Hi, Does it apply the F5121?
Click to expand...
Click to collapse
no it does not! send me your kernel.sin file
i will modify for you

Hi all,
I'm happy to share with you an updated guide on how to root the Xperia XA.
This guide is Only for Nougat (Android 7.0), for Marshmallow (Android 6.0) it's here: https://forum.xda-developers.com/xp...ia-xa-noob-t3430170/post67988142#post67988142
## 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.
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, fro this you need to downgrade to an old Marshmallow firmware, for now you can't root AND restore your backup.
3. You can re-lock your phone and it will restore DRM if you have a backup but you lose root and recovery.
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.
6. Make a full backup of your personnal data before following this guide.
## Method
1. Find out whether if you bootloader can be 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.23.2 for Windows, note that you can also use it to unlock your
bootloader(http://www.flashtool.net/downloads_windows.php) DON'T USE AN OLDER VERSION OF FLASHTOOL AND DOWNLOAD FIRMWARES FROM THE
INTEGRATED XPERIFIRM
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. Download the proper files for your phone version/variant:
Magisk Manager apk package: http://www.apkmirror.com/apk/topjohnwu/magisk-manager/
For XA single sim = F3111, F3113, F3115
TWRP recovery: https://forum.xda-developers.com/xperia-xa/development/f3111-f3113-f3115-twrp-recovery-xa-t3639206
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-t3638725
Boot: https://forum.xda-developers.com/xp...12-f3116-stock-kernels-built-sources-t3526496
6. Power off the phone and flash ONLY "BOOT_DELIVERY" from a Marshmallow firmware with Flashtool ( exclude all other patitions), you must only see
"boot_delivery.xml" in the "Content" column.
7. Power off the phone again and enter the phone in Fastboot mode (when power off, hold Vol+ and plug the phone). The led should be blue.
8. Copy the downloaded boot and recovery to "C:\Flashtool\x10flasher_lib" and rename them to boot.img and recovery.img, if you computer is not set to show file extentions remane them
without .img at the end
9. Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands and then delete them.
10. Unplug the phone, hold "Vol-" and "Power" buttons. Release all buttons after phone vibrate.
11. You are in TWRP recovery, on password prompt press "Cancel"
12. On next screen press "Swipe to allow".
13. Format "userdata" partition to remove internal encrytion for restoring TWRP backups/acces of /data partition, go to "wipe" and tap "format data". If you don't this your phone will
bootloop on Xperia logo. Don't forget to backup your personnal data before !!
14. Reboot to Android (it will takes about 10 minutes) and follow instructions until you are on the Home screen.
15. Install Magisk Manager apk package from the given link, you have to enable "Unknown sources" in the security menu before.
16. Open Magisk Manager and tap "Download" at the bottom, wait until you see download complete and reboot to recovery.
17. Go to "Install" and select "Magisk-vX.XX.zip" located in /sdcard/magisk manager, swipe to intall.
18. Power off the phone again and repeat step 6 with your actual Nougat firmware or the phone will not detect Sim Card(s)
19. Reboot the phone.
20. Tap the "Thanks! :good:" button at the bottom right of this post, optionally you can offer me a coffee/beer/tea or energy drink to support my work, my PayPal adress is in my profil.
21. Your phone is rooted
## 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. If you don't follow exactly the guide you will probably brick your phone.
Despite these issues, rooting the Xperia XA has been confirmed to work on Single and Dual Sim.

Open source archive has been released...
Could we have a nougat boot.img? Because sony has released open source archive.
Thanks:laugh:

Actually, you can use flashtool 9.23.1, but remember to download the 9.23.2 jar file and copy to flashtool folder (overwrite).
Also, if you know how to input adb command, you can enter bootloader using the following:
Code:
adb reboot bootloader
Hopefully the version of XA Ultra will be released.

rrvuhpg said:
Hi all,
I'm happy to share with you an updated guide on how to root the Xperia XA.
This guide is Only for Nougat (Android 7.0), for Marshmallow (Android 6.0) it's here: https://forum.xda-developers.com/xp...ia-xa-noob-t3430170/post67988142#post67988142
## 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.
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, fro this you need to downgrade to an old Marshmallow firmware, for now you can't root AND restore your backup.
3. You can re-lock your phone and it will restore DRM if you have a backup but you lose root and recovery.
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 can be 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.23.2 for Windows, note that you can also use it to unlock your
bootloader(http://www.flashtool.net/downloads_windows.php) DON'T USE AN OLDER VERSION OF FLASHTOOL AND DOWNLOAD FIRMWARES FROM THE
INTEGRATED XPERIFIRM
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. Download the proper files for your phone version/variant:
Magisk Manager apk package: http://www.apkmirror.com/apk/topjohnwu/magisk-manager/
For XA single sim = F3111, F3113, F3115
TWRP recovery:
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-t3638725
Boot: https://forum.xda-developers.com/xp...12-f3116-stock-kernels-built-sources-t3526496
6. Install Magisk Manager apk package, you have to enable "Unknown sources" in the security menu before.
7. Open Magisk Manager and tap "Download" at the bottom.
8. With a file manager copy "Magisk-vX.XX.zip" from /sdcard/magisk manager to your MicroSD
9. Power off the phone and flash ONLY "BOOT_DELIVERY" from a Marshmallow firmware with Flashtool, you must only see "boot_delivery.xml" in the "Content"
column.
10. Power off the phone again and enter the phone in Fastboot mode (when power off, hold Vol+ and plug the phone). The led should be blue.
11. Copy the downloaded boot and recovery to "C:\Flashtool\x10flasher_lib" and rename them to boot.img and recovery.img.
12. Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands and then delete them.
13. Unplug the phone, hold "Vol-" and "Power" buttons. Release all buttons after phone vibrate.
14. You are in TWRP recovery, on password prompt press "Cancel"
15. On next screen press "Swipe to allow".
15.1 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". If you do this,
make a backup before (it will factory reset the phone), reboot to Android an repeat steps 6, 13 and 15
16. Go to "Install", "Select Storage", click "Micro SDCard" and select "Magisk-vX.XX.zip".
17. Power off the phone again and repeat step 9 with your actual Nougat firmware or the phone will not detect Sim Card(s)
18. Reboot the phone.
19. Tap the "Thanks! :good:" button at the bottom right of this post, optionally you can offer me a coffee/beer/tea or energy drink to support my work, my PayPal adress is in my profil.
20. Your phone is rooted
## 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. If you don't follow exactly the guide you will probably brick your phone.
Despite these issues, rooting the Xperia XA has been confirmed to work on Dual Sim but need confirmation for Single Sim.
Click to expand...
Click to collapse
I'm on nougat 33.3.A.0.131 f3116
In 9 th step u have mention boot delivery, i cant understand.
Where to find BOOT_DELIVERY

Is Boot delivery of marshmallows (33.2.B.3.81) and nougat (33.3.A.127) compatible for nougat 33.3.A.0.131. Because I have marshmallows and nougat firmwares(ftfs) only that versions.

Chaminxa said:
Is Boot delivery of marshmallows (33.2.B.3.81) and nougat (33.3.A.127) compatible for nougat 33.3.A.0.131. Because I have marshmallows and nougat firmwares(ftfs) only that versions.
Click to expand...
Click to collapse
I dont underdtand

OK, I will explain a little more the step 9.
You must have 2 Firmwares in Flashtool:
1st is your actual Nougat firmware
2nd is a Marshmallow firmware, I used 33.2.B.4.70 for my F3112 but you can probably use an older.
When you are on step 9, open Flashtool and load the Marshmallow firmware. When you are on the screen to choose parts to flash with boxes to check and uncheck. You have to check all boxes on the up and down right columns, only the "BOOT_DELIVERY" is uncheck in the upper right column. If it's OK you should see only one line in the "Content" column: "boot_delivery.xml". Now clic on "flash" button at the bottom right, if Flashtool asks for using fsc script, clic "yes". You will have to do the same at step 17 but with your actual Nougat firmware.
It's very important to use the last Flashtool version 0.9.23.2 and download firmwares from the included Xperifirm or you will probably have problems or brick.
Edit: I will add files for Single Sim very soon so you don't have to ask for them

In step 17 - Can i flash nougat (33.3.A.127) boot delivery. Xml on nougat 33.3.A.0.131?

Chaminxa said:
In step 17 - Can i flash nougat (33.3.A.127) boot delivery. Xml on nougat 33.3.A.0.131?
Click to expand...
Click to collapse
I don't know, you can try and feedback if working or not

Hey can you upload magisk.zip. plzz
Thanks

TWRP recovery for XA single sim is missing. Not sure if dual sim would work but I'll try it out and see.

goldblot said:
TWRP recovery for XA single sim is missing. Not sure if dual sim would work but I'll try it out and see.
Click to expand...
Click to collapse
If you read at the bottom of the thread, rrvuhpg has not yet released any twrp and any boot.img for nougat on XA single sim , for that you have to wait a little bit.

Hey. I flashed boot dilivery.xml 33.3.A.0.131 . But my phone stuck @ xperia logo. Whats the wrong? Plz help
---------- Post added at 01:28 PM ---------- Previous post was at 01:22 PM ----------
Enyone here? Plzzzzz help me

Will there be a way to root Nougat for F3211 (Single sim XA Ultra)?
And can we use drm fix on Nougat?

Chaminxa said:
Hey. I flashed boot dilivery.xml 33.3.A.0.131 . But my phone stuck @ xperia logo. Whats the wrong? Plz help
---------- Post added at 01:28 PM ---------- Previous post was at 01:22 PM ----------
Enyone here? Plzzzzz help me
Click to expand...
Click to collapse
You followed exactly the guide?
If yes, why you asked to upload magisk.zip?
You flashed boot_delivery for the same firmware? (you asked for using a different one).
You formated Data partition in TWRP?
On the Xperia logo you waited how many time?

Chaminxa said:
Hey can you upload magisk.zip. plzz
Thanks
Click to expand...
Click to collapse
It's already in the description.
5. Download the proper files for your phone version/variant:
Magisk Manager apk package: http://www.apkmirror.com/apk/topjohnwu/magisk-manager/
---------- Post added at 10:55 PM ---------- Previous post was at 10:45 PM ----------
Chaminxa said:
Hey. I flashed boot dilivery.xml 33.3.A.0.131 . But my phone stuck @ xperia logo. Whats the wrong? Plz help
---------- Post added at 01:28 PM ---------- Previous post was at 01:22 PM ----------
Enyone here? Plzzzzz help me
Click to expand...
Click to collapse
Try using boot dilivery.xml Marshmallow firmware 33.2.B.4.70 NOT boot dilivery.xml 33.3.A.0.131

Files for Single Sim XA released on first post !
Files are untested so if you are noob please wait for feedbacks.

Thank you very much indeed.
great tutorial, great work done.

@rrvuhpg when i try to flash boot or recovery i get this message
(target reported max download size of 134217728 bytes
error: cannot load 'boot.img': No error) sony xperia xa f3113

jbenitez821 said:
@rrvuhpg when i try to flash boot or recovery i get this message
(target reported max download size of 134217728 bytes
error: cannot load 'boot.img': No error) sony xperia xa f3113
Click to expand...
Click to collapse
Yes i also faced the same issue.
Try changing the name from boot.img to boot
And recovery.img to recovery.
And enter the command "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img"
It worked for me.
---------- Post added at 11:58 AM ---------- Previous post was at 11:51 AM ----------
Hi @rrvuhpg
I have tried all the steps u have mentioned above, but i have got stuck into bootloop after flashing magisk,
When i swipe to install magisk some cmd are running and i see some red cmd line running like "failed to decrypt" in starting point
I let the device for 30 Mins still its nit booting up.
Is there any issue. Please help.