Database Develop

[D65XX] CWM-Based Recovery 6.0.4.7 + ROOT for Xperia Z2 [20141105]

CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z2!
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!​
[ info ]
This Recovery is built from CWM 6.0.4.7 sources!
[ PROOF ]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
CyanogenMod and FreeXperia Team (especially jerpelea) for too many things *
special thanks to @yeeson for helping out with testing and risking his devices for the sake of development!!! and NO, his phone was NOT damaged during testing
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
STOCK ROM FW:
4.4.4
23.0.1.A.0.167 - v07
4.4.2
17.1.2.A.0.314 - v06
17.1.1.A.0.438 - v05
17.1.1.A.0.402 - v04
17.1.A.2.69 - v03
17.1.A.2.55 - v02
17.1.A.2.36 - v01
or ROMS BASED ON THAT FIRMWARE
[ features ]
standard CWM recovery 6.0.4.7!
kernel is insecure (ro.secure=0)
disabled kernel level RIC
adb debugging is enabled by default in OS
TIP: if u are experiencing very slow backup in CWM do this
[ WARNING ]
ITS HIGHLY RECOMMENDED TO FIRST ROOT ON LOCKED BOOTLOADER AND TAKE TA BACKUP BEFORE BOOTLOADER UNLOCK!
for flashing this kernel you WILL NEED TO UNLOCK BOOTLOADER! Check this thread for more info (same steps as Xperia Z1 are used for Xperia Z2)
UNLOCKING BOOTLOADER WITHOUT TA BACKUP WILL LEAD TO IRREVERSIBLE LOSS OF DRM KEYS!!!
AND YES CAMERA STILL WORKS AFTER UNLOCKING BOOTLOADER!!!
[ known issues ]
adb is not working in recovery (can be fixed later)
[ how to install my kernel ] (via recovery) [RECOMMENDED]
download the kernel package
save it to the sdcard
reboot into recovery
flash the kernel package using recovery
reboot from recovery into system
the device should now start booting
enjoy the kernel
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
[ how to enter recovery ]
when you see the Sony logo and the LED light turns pink/amber/orange keep tapping/pressing VOLUME UP key
[ how to Root ]
for instructions on how to root please check this post
[ sources ]
https://github.com/DooMLoRD/android_device_sony_honami
for now recovery is same is same as honami
[ donations ]
Please do consider donating as I plan to get this device!
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
OR
you can buy one of my awesome apps from Play Store!
[ download links ]
PLEASE DO NOT MIRROR, REDISTRIBUTE, REPACK MY FILES
NEW:
Advance Stock Kernel with CWM Recovery v07 (FW: 23.0.1.A.0.167}
MD5HASH: ade2fd4d1edf9355089170ecfbf72d2d
OLD:
Advance Stock Kernel with CWM Recovery v06 (FW:17.1.2.A.0.314}
MD5HASH: 9dda203d813ac6ff7f2b80d85f4de2c5
Advance Stock Kernel with CWM Recovery v05 (FW:17.1.1.A.0.438}
MD5HASH: 1857871ed72fc5c2c665c24e30cfd2c4
Advance Stock Kernel with CWM Recovery v04 (FW:17.1.1.A.0.402}
MD5HASH: 629761c9b73cad8ae177b7ad9edcb196
Advance Stock Kernel with CWM Recovery v03 (FW:17.1.A.2.69}
MD5HASH: a0d584009b50b19b3b965ccf339f7d86
Advance Stock Kernel with CWM Recovery v02 (FW:17.1.A.2.55}
MD5HASH: a0d584009b50b19b3b965ccf339f7d86
Advance Stock Kernel with CWM Recovery v01 (FW:17.1.A.2.36}
MD5HASH: 6e0c418d299780bd0ac74e69ff46a199
...
enjoy!!!

Rooting Instructions
[ proof ]
[ how to root ]
once you have flashed the kernel from the 1st post
download the latest SuperSU update.zip from: http://download.chainfire.eu/supersu
save it on sdcard of device
reboot into recovery
flash the supersu update.zip
reboot from recovery into OS
you should now get proper root access!
[ installing busybox ]
it is highly recommended to install busybox after rooting!
just go to andorid play store and download the busybox installer.
once the installer is downloaded, install busybox in /system/xbin
reboot device after install and thats it!
regards,
DooMLoRD

Thank you very much @DooMLoRD！

Is it possible to do a TA backup of the Z2 yet since there is no root with a locked bootloader?

JMonkeYJ said:
Is it possible to do a TA backup of the Z2 yet since there is no root with a locked bootloader?
Click to expand...
Click to collapse
not at the moment... we will have to wait for an exploit...

Congratulations @DooMLoRD and thanks for the helping hand @yeeson people like you are extremely important for the devs on xda

I'll wait for an exploit for locked bootloaders to back up the DRM keys
Many Thanks to you and awesome job by doing this

That was quick! Can't wait to have my Z2 <3
Gesendet von meinem Nexus 5 mit Tapatalk

And so @DooMLoRD does it again!
Great stuff mate!

Does it support exFat or ext4 filesystems on sdcard?

I am from Singapore and due to get my Z2 in 2 days time. I am very familiar with the rooting procedure for Samsung phones but this is my first Sony phone. I would like to root it but how can I tell that my bootloader is locked or not? Based on the instructions it seems we cannot install this without unlocking the bootloader, yet to unlock it we need root. Kinda like chasing the tail, isn't it?

Seifer1975 said:
I am from Singapore and due to get my Z2 in 2 days time. I am very familiar with the rooting procedure for Samsung phones but this is my first Sony phone. I would like to root it but how can I tell that my bootloader is locked or not? Based on the instructions it seems we cannot install this without unlocking the bootloader, yet to unlock it we need root. Kinda like chasing the tail, isn't it?
Click to expand...
Click to collapse
All Z2s come with the bootloader locked, so yours will be locked.
The unlock and root procedure in the OP does NOT require root, so you can accomplish it as soon as you get your phone and have an unlocked, rooted phone. The warning is that you will not be able to do a TA backup (which is NOT necessary to complete the unlock and root procedure described) if you don't have root already, so you will lose your DRM keys which are needed for some special functions on the Z2. You may or may not care about the special functions.

i found the entire system got a bit slower after flashing... especially the camera, it has very noticeable lag. but meh, i got root

theclueless said:
i found the entire system got a bit slower after flashing... especially the camera, it has very noticeable lag. but meh, i got root
Click to expand...
Click to collapse
That's what happened to me after unlocking the bootloader. I spent the whole day with unlocked bootloader and NO root yet, about to do it now. Phone was lightning fast yesterday, especially the camera, now it is anything but fast......why would this happen? Again, for me, it's not the kernel as I haven't flashed it yet/

@DooMLoRD
Have you tried or think about making MultiROM like tool for Xperia or Galaxy devices?
http://forum.xda-developers.com/showthread.php?t=2011403

jiggyb21 said:
That's what happened to me after unlocking the bootloader. I spent the whole day with unlocked bootloader and NO root yet, about to do it now. Phone was lightning fast yesterday, especially the camera, now it is anything but fast......why would this happen? Again, for me, it's not the kernel as I haven't flashed it yet/
Click to expand...
Click to collapse
could you try to relock your bootloader and see if it resolves the issue?

theclueless said:
could you try to relock your bootloader and see if it resolves the issue?
Click to expand...
Click to collapse
I think I might....Just factory reset....dalvik cahe, etc, etc...Still stutters and slow. Unbearable really. Now to figure out how to relock it, Flashtool hopefully? I was having trouble locating the folder in which to place a tft firmware in for flashtool to access. I assume I'll have to have the stock tft firmware to relock the bootloader.....
EDIT- nevermind....I was confusing the flashtool I just downloaded with some older flashtool I had used on an LG at some point. I see the firmware folder now.

jiggyb21 said:
I think I might....Just factory reset....dalvik cahe, etc, etc...Still stutters and slow. Unbearable really. Now to figure out how to relock it, Flashtool hopefully? I was having trouble locating the folder in which to place a tft firmware in for flashtool to access. I assume I'll have to have the stock tft firmware to relock the bootloader.....
EDIT- nevermind....I was confusing the flashtool I just downloaded with some older flashtool I had used on an LG at some point. I see the firmware folder now.
Click to expand...
Click to collapse
if you didnt flash the advance kernel, you can just boot to fastboot and do "fasboot bootloader lock"

​
theclueless said:
if you didnt flash the advance kernel, you can just boot to fastboot and do "fasboot bootloader lock"
Click to expand...
Click to collapse
I really don't want to hijack this thread and turn it into something it's not. For now I think it belongs because I'm not 100% sure if it's the kernel or unlocked bootloader slowing my phone down. I flashed the kernel from page 1.... 'Advance Stock Kernel with Recovery v01 (FW:17.1.A.2.36}".
I relocked the bootloader using flashtool. It said it was successful but upon rebooting it soft bricked and the only thing I could do was get into flashmode again. Went back to flashtool and relocked the bootloader again and the phone rebooted no problem, just slowly. Not sure what else to do. Can I reflash the stock kernel?

jiggyb21 said:
​
I really don't want to hijack this thread and turn it into something it's not. For now I think it belongs because I'm not 100% sure if it's the kernel or unlocked bootloader slowing my phone down. I flashed the kernel from page 1.... 'Advance Stock Kernel with Recovery v01 (FW:17.1.A.2.36}".
I relocked the bootloader using flashtool. It said it was successful but upon rebooting it soft bricked and the only thing I could do was get into flashmode again. Went back to flashtool and relocked the bootloader again and the phone rebooted no problem, just slowly. Not sure what else to do. Can I reflash the stock kernel?
Click to expand...
Click to collapse
if you flashed the kernel from the first post, you will need to flash the stock kernel after relock the bootloader

Questions/concerns about CM12.1 + rooting + unlocking bootloader

Hey guys
So I just bought a new Z3C and I'm planning on rooting it and installing CM12.1 on it. But before that I wanna make sure I perfectly understood the entire process. So if anyone could help by answering/confirming some of the things below, I would really appreciate that.
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Thank you very much.

arsradu said:
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Click to expand...
Click to collapse
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
arsradu said:
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Click to expand...
Click to collapse
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
arsradu said:
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Click to expand...
Click to collapse
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
arsradu said:
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Click to expand...
Click to collapse
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
arsradu said:
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
Click to expand...
Click to collapse
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
arsradu said:
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Click to expand...
Click to collapse
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.

MyPictures said:
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
Click to expand...
Click to collapse
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.

arsradu said:
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
Click to expand...
Click to collapse
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?

MyPictures said:
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
Click to expand...
Click to collapse
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk

arsradu said:
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Did you install the drivers properly and on which Operating system are you flashing it?

MyPictures said:
Did you install the drivers properly and on which Operating system are you flashing it?
Click to expand...
Click to collapse
I would say yes. I mean...after googling a bit, I saw that I actually don't need to just "ignore" that message asking to press the Back button, but to actually press Volume Down instead. Which I did. And I was able to go into Flash Mode. (Flash Tool says "device connected in Flash Mode"). The device was properly recognized in MTP mode. Still, I had to manually install the Flash-tool drivers to get it recognized in flash mode, as well. Not sure why...
I mean, if the phone was properly recognized without manually installing anything (Windows downloaded and installed its own drivers), why the hell do I need to install custom drivers to get it recognized in flash mode? By the way, this "flash mode" is similar to Samsung's "Download Mode", for as far as I could see. And, just like on Samsung's devices, the access is made by pressing the Volume Down upon booting up.
Anyway, even though the device is now recognized in flash mode, I still get an error trying to flash stock 4.4.4.
I get this:
Code:
14/014/2015 21:14:34 - INFO - Please connect your device into flashmode.
14/016/2015 21:16:28 - INFO - Device disconnected
14/017/2015 21:17:03 - INFO - Device connected in flash mode
14/017/2015 21:17:03 - INFO - Opening device for R/W
14/017/2015 21:17:03 - INFO - Reading device information
14/017/2015 21:17:03 - INFO - Unable to read from phone after having opened it.
14/017/2015 21:17:03 - INFO - trying to continue anyway
14/017/2015 21:17:03 - INFO - Start Flashing
14/017/2015 21:17:03 - INFO - Processing loader.sin
14/017/2015 21:17:03 - INFO - Checking header
14/017/2015 21:17:03 - ERROR - Processing of loader.sin finished with errors.
14/017/2015 21:17:03 - INFO - Ending flash session
14/017/2015 21:17:03 - ERROR - Error in processHeader : 1 : Incorrect function.
14/017/2015 21:17:03 - ERROR - Error flashing. Aborted
14/017/2015 21:17:03 - INFO - Device connected in flash mode
And after a while, it automatically reboots in normal mode.
Windows version is Windows 10. But I'm not sure that's the problem here since, as I said, the device does get recognized both in MTP and flash modes. Also, for as far as I could see, other people are having the same issues on other versions of Windows.

Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.

MyPictures said:
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
Click to expand...
Click to collapse
Yes, I'm running FlashTool64.exe since I'm running a 64-bit version of Windows.
The device is correctly recognized in flash mode (after manually selecting the driver installed with flash-tool). See the attached image for more info.
But indeed maybe I got the wrong firmware. Problem is that I'm not really sure which one should I choose.
I got one called D5803_23.0.1.A.5.77_Customized_FR.ftf. I don't mind it that it's in French. All of them have English anyway.
Also, I saw one for UK here called D5803_23.0.A.2.105_UK.ftf. Seems to be different.... I will try with that as well.
Update: same error with that UK firmware, as well.
Update2: Well I'm half way there. Got 4.4.4 installed and got it rooted. YAY. Still trying to figure out why adb is not correctly running when trying to backup TA.
Update3: ok, backup done too!
Update4: the boot.img that comes with CM12.1 doesn't seem to have a recovery.... Or if it does, I couldn't boot in it so I can flash CM12.1.
I tried the one from Doomlord (Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img) and that seems to be based on CWM v6.0.4.7.
Problem with that is that, even though I can boot into recovery, I can't flash CM12.1. It says error status 7. Any idea why or how to fix this?

I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).

MyPictures said:
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
Click to expand...
Click to collapse
Might be. The problem is the device is not correctly recognized upon flashing (it says the device is "Aries" but the ROM is for D5803, D5833, z3c LOL), due to the check made within the updater-script (first line). For as far as I could see, this is a known issue... Not sure why it hasn't been fixed by now.
Anyway, removing that line will get the ROM installed successfully (at least with THAT recovery).
So I'm on CM12.1 , been for a few days now (thank you for your help), and I was wondering if there are any "permanent" recoveries (compatible with CM12.1, of course) that I can flash, something that can give me the ability to boot into recovery (and not Cyanogen Recovery, since that one sucks) and do things like nandroid backup (I know TWRP and CWM can do that, but I couldn't find any permanent version of those (or maybe I just didn't dig deep enough), and I'm not sure they are compatible with CM12.1) and formatting /system. The last one is really important for a clean installation of the ROM, especially since it doesn't look like it's done by the ROM itself.

Potentially bricked device...is it fixable?

Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb

MrMeeb said:
Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb
Click to expand...
Click to collapse
First of all don't worry, Sony's phone doesn't brick that easy ?
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk

OsGhaly said:
First of all don't worry, Sony's phone doesn't brick that easy
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?

MrMeeb said:
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?
Click to expand...
Click to collapse
You're more than welcome dear, glad to hear you've successfully did it :good:
Concerning TWRP flash, you can try one of these:
1- Use rasher tool to flash the TWRP img (the easiest way).
2- Adb Sideload:
AdrianDC said:
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
​
Click to expand...
Click to collapse
3- Using terminal emulator app such as $cripter:
Place twrp.img in the root of your /sdcard folder then run the following commands using $cripter app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
P.S. You can download the latest TWRP from here

OsGhaly said:
You're more than welcome dear, glad to hear you've successfully did it :good:
(Rest cut as I'm not allowed to post external links)
[/CODE]
Click to expand...
Click to collapse
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?

MrMeeb said:
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?
Click to expand...
Click to collapse
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
-----
Another workaround is to install XZDualRecovery to have Philz touch and TWRP recoveries working alongside with the stock kernel and use it to install LineageOS ROM.

Hi bro
neva mind wat happened to u ,do as wat i say
First search n find the proper (stock .tft) file as per your country and version.
Download FLASHTOOL
now paste ur stock.tft file (around 1-2 gb) in flash folder
open flashtool and connect ur sick brick SP-Xepria in fastboot
install ur stock onces it done successfullly u wil get ur phone as stock .
i too bricked now im on andriod 7
no worries bro
---------- Post added at 09:31 AM ---------- Previous post was at 09:24 AM ----------
Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/show....php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/show....php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/show....php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes

You too have Sony.yt procedure with s1boot in the last case...

OsGhaly said:
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
Click to expand...
Click to collapse
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MrMeeb said:
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
Click to expand...
Click to collapse
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.

OsGhaly said:
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.
Click to expand...
Click to collapse
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread

MrMeeb said:
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread
Click to expand...
Click to collapse
You're welcome dear, glad to hear that you finally got lineage os and TWRP on your phone.. Well done
Sent from my Xperia SP using Tapatalk

Does XperiFIX work with 47.1.A.12.145 aka the April patch?

I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?

Pickx said:
I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?
Click to expand...
Click to collapse
Have you thought of asking in the Xperiafix thread ?

Didgesteve said:
Have you thought of asking in the Xperiafix thread ?
Click to expand...
Click to collapse
No, because nobody in that thread has answered that question for the March update either.

Pickx said:
No, because nobody in that thread has answered that question for the March update either.
Click to expand...
Click to collapse
Well if no one has answered then it's probably a no then

I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
I haven't installed the .145 FW atm, because I couldn't boot into Android with TWRP from 05.03.18.
But I read that TWRP came out for the april patch, so I will try to update at the weekend and check again with XperiFix.
Proof FW .119:
Phone Settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone Security Settings:
XperiFix:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Phone Settings:
XperiFix:

Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?

Raz0Rfail said:
I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
[...]
Click to expand...
Click to collapse
Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?

Raz0Rfail said:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Click to expand...
Click to collapse
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!

nataelj said:
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!
Click to expand...
Click to collapse
I wrote you a pm to modify xperifix.
You need only the current kernel for the fw installed. It comes with flashing firmware.
The temp TWRP inside the data folder is only get booted from the XperiFix tool.
The XperiFix tool boot this temp TWRP to change the libs, install magisk and so on.
If you change the TWRP temp through another TWRP image, all commands to flash magisk etc. Won't work, so for the work is the temp TWRP required.
Important is that you use the correct kernel before you use xperifix, because this kernel get flashed and TWRP temp got booted as recovery, so nothing changes what you have currently installed as boot or recovery image.
So the second TWRP I let It as it be. After flashing the XperiFix files and the phone restart correctly, I boot into bootloader and flash the new TWRP recovery and then I reboot into TWRP to check if all files shown in /sdcard are correctly named. If the names are correct, you use the right TWRP to the installed security patch from Google. If you have only cryptic names inside /sdcard you have the wrong TWRP to the installed security patch. If it's so that the wrong TWRP is installed download the correct one and flash the recovery again.
Edit: sorry I forget I wrote am pm to pickxx.
I send it to you too.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.

Raz0Rfail said:
I wrote you a pm to modify xperifix.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.
Click to expand...
Click to collapse
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.

nataelj said:
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.
Click to expand...
Click to collapse
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.

Raz0Rfail said:
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.
Click to expand...
Click to collapse
Cool; will look forward to the details!
To be clear though, I have an unpatched, unrooted device that's on the most recent firmware. I'm not just updating to access the sdcard and create backups, I'm updating to crack the phone in the first place (without having to do a downgrade, which I haven't worked out the full process for yet). Not sure if that changes anything or not but figured I'd mention in case.

I had .34 firmware, used Xperifix, than upgraded to .119 and indeed it stopped working.

This is a Tutorial about patching XperiFix from Storm// to use it with new Firmwares.
It's not officially provided or allowed by him!
At first I have to be clear at the following points:
The Patch has the same requirements as XperiFix itself (without the old firmwares)
Your Device must have a unlocked bootloader.
With unlocking your bootloader, you will loose your DRM Keys for this phone forever!
The XperiFix is only simulating DRM-Keys, so the camera and other things can be used again.
You should have installed the correct drivers for bootloader and USB-Debugging
Get Software
Download and install XperiFix first on your PC:
https://www.xperifix.com/download/xperifix-latest/ Version2.2
For patching XperiFix download DnSpy on Github(https://github.com/0xd4d/dnSpy/releases/tag/v4.5.3)
Get TWRP for your FW: https://androidfilehost.com/?w=files&flid=232371 (current for .145 FW is twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img)
Get and install Firmware
At first you need the Current firmware on your Device.
I use FlashTool to download and flash the Firmware: http://www.flashtool.net/downloads.php
Download new XZ1c-Firmware trough XperiFirm inside FlashTool.
After the download close XperiFirm to create the new FTF-file from FlashTool automaticly.
In FlashTool click Flash --> Flashmode --> Select new Firmware (don't change anything at wiping or excluding), execute the flash.
After flash reboot phone into system, it needs time just wait!
If reboot is from Android needed to finish upgrade, let the phone do it.
Patch XperiFix
Extract DnSpy from zip-file.
open DnSpy.exe, Open XperiFix.exe under File --> Open (C:\XperiFix\XperiFix.exe).
In "Assembly Explorer" switch to XperiFix (2.2.0.0) --> XperiFix.exe--> (XperiFix (Yellow Color) --> Form1 in tree structure.
Right Click on public Form1(), "edit Method".
In the new Window, you are able to change the source code.
replace the following variable
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75"
};
with
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75",
"47.1.A.12.119",
"47.1.A.12.145"
};
Click on the Button compile. You will see the changes in the main Window from DnSpy.
Click on File -> Save Module --> enter name, save the .exe-file.
Start the patched XperiFix.exe
reboot phone into Bootloader and connect it to your pc, because there XperiFIX can detect it without crashing.
If everything was correct patched with DnSpy you should be allowed to use it.
Set the hook and click on "FIX my Device!" then let XperiFIX do it's work.
if you see magisk and XperiFIX get flashed inside twrp everything is fine.
if the phone restarts into system, reboot phone into bootloader to flash your twrp recovery.
Flash Recovery
reboot phone into Bootloader and connect it to your pc.
"Path to fastboot\fastboot.exe" flash recovery "Path-to-Twrp\twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img"
"Path to fastboot\fastboot.exe" reboot
Phone should start into android, first time needs time because it has wiped dalvic and cache.
In Android take a photo and check album if there is a green picture or not (shouldn't be).
You can start telephone APP call *#*#SERVICE#*#* or *#*#7378423#*#* and inside the Service Menu switch to "service tests" and there to Security.
Should be near identically to mine, some Thread entries before.
You have now the new Firmware and XperiFIX installed.
Afterwards I'm using root Explorer and Titanium Backup to clean the Bloatware which come from installing the new Firmware.
If something is not clear or detailed, please write it to me.

Raz0Rfail said:
This is a Tutorial about patching XperiFix from Storm//
Click to expand...
Click to collapse
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?

nataelj said:
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
You only need the Firmware, how you get to the Firmware is secondary. But if you unlocked your bootloader you can't install the new OTAs.
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
The TWRP recovery is only in your phone. XperiFix pushes it's own twrp trough the process.
The XperiFix TWRP is located at C:\XperiFIX\DATA\TWRP\xz1c-twrp.img.
But if you flash your own recovery as in step 5 described, the xperiFix twrp is obselete.
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?
I understand your concern. You will be able to forget about the OTA updates as soon as you unlock the bootloader.
My recommendation is to wait as soon as a new firmware is out until TWRP has been adapted.
Because I had to redo my mobile 3 times because I didn't wait and couldn't flash XperiFix.
This means you need to download 2.5 GB+- for each update, patch XperiFix, and start the process from the beginning.
This is the price to use the phone with root and Magisk.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Do you understand better now?

@Raz0Rfail everything worked. I had to wipe and install janjan's ROM because magisk wasn't working after XperiFIX, but other that your guide worked perfectly. Thanks again.

Raz0Rfail said:
Do you understand better now?
Click to expand...
Click to collapse
Seems to have failed for me. I now get green camera images and have no root; something went wrong somewhere... :-/

Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.

Raz0Rfail said:
Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.
Click to expand...
Click to collapse
Hmm, maybe I could use more clarification on that step then. I actually just went into TWRP and then hit install and pointed it to install the new file (copied to the phone) as a new recovery. Would that not work? If not, is the above meant to say I should use flashtool and flash that new TRWP with it?
EDIT: Hey!!! Something worked! I checked the logs and saw some failed file copies and permission errors so I played around with it some and reran as you suggested and it seems to have worked now! I'm up and running and my photos are no longer green!!
I am not seeing Magisk as an app though, and when I try and open Titanium Backup it just cycles while looking for SU and Busybox. If I get the Root Checker app it says not rooted too even though it finds an Su; does that actually mean not rooted or does Magisk work in some other way to give permission?

[SOLVED] - PIE - Temp Root Achieved?

Hello guys.
I've managed to root my G8441 which was on FW 47.2.A.10.28.
Bootloader unlocked and went to FW 47.2.A.10.45
Followed all the instructions and guides from:
https://forum.xda-developers.com/showpost.php?p=79368241&postcount=12
(help through help, through help, xda love)
Root successfully working and was already busy applying dark-mode from Swift Installer. (reason why i was doing this in the first place)
SwiftInstaller even rebooted successfully after applying themes, and no problems so far. (disabled ''soft reboot'' as i use simpin)
After a manual device reboot, the device seemed to got stuck into a bootloop.
I could get it into flashmode and reflashed the FW named above.
After this the device booted up again.
Files deleted before flash: *.ta (except from .\boot), persist*.sin, Qnovo*.sin, amss*.sin, ssd*.sin
Rootchecker, swift installer don't seem to get root-access anymore since.
Magisk is successfully installed through TWRP, and I've repeat the last steps of the guide.
Any ideas?
I am almost back to the beginning after my 4 hour journey with a unlocked bootloader ;p
And happy i could get the device back from the boot-loop again though.

Why not flash Magisk?

Magisk is on.
With re flashing i've probably forgot to re-run the renoroot again.
Busy with that now.
*edit, did not had so much events yet.
Hopefully this is it.
On 140000 events now though.
Much files.

If you already have an unlocked bootloader and TA backed up and restored you don't need a temp root anymore. Just flash magisk (or j4nn's modified kernel with magisk preinstalled) and you have root.

vofferz said:
If you already have an unlocked bootloader and TA backed up and restored you don't need a temp root anymore. Just flash magisk (or j4nn's modified kernel with magisk preinstalled) and you have root.
Click to expand...
Click to collapse
Check, thanks.
When i woke up it was still busy at 140k events
TA is restored, and bootloader is unlocked.
Flashed modified kernel from:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
(boot-G8441-47.1.A.8.49-hideunlock-rooted.img)
Code:
downloading 'boot.img'...
OKAY [ 0.458s]
booting...
OKAY [ 5.742s]
finished. total time: 6.204s
No change after fastboot reboot, i must do be something wrong somewhere. allthough i cant find the miss-step, need fresh eyes.
So close until completion.. I still get the ''you must lock your bootloader'' alert when starting up the device after flashing this kernel. FYI.
MAGISK Install process repeated through TWRP just to be sure.

TGN said:
Check, thanks.
When i woke up it was still busy at 140k events
TA is restored, and bootloader is unlocked.
Flashed modified kernel from:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
(boot-G8441-47.1.A.8.49-hideunlock-rooted.img)
Code:
downloading 'boot.img'...
OKAY [ 0.458s]
booting...
OKAY [ 5.742s]
finished. total time: 6.204s
No change after fastboot reboot, i must do be something wrong somewhere. allthough i cant find the miss-step, need fresh eyes.
So close until completion.. I still get the ''you must lock your bootloader'' alert when starting up the device after flashing this kernel. FYI.
MAGISK Install process repeated through TWRP just to be sure.
Click to expand...
Click to collapse
The topic talks about Pie, but you mention an ancient Oreo fw version...
If you have already restored the TA partition after unlock, just manually flash the newest Pie firmware of your desider customization (remove persist...sin before flash) and then either boot with j4nn's modified kernel OR flash magisk from TWRP to get root with magisk.
The boot notification about unlocked bootloader will stay whatever you do. Just ignore it.

I am at 47.2.A.10.45.
And flashed Magisk from TWRP.
Can't get root-access.
I've restored TA partition earlier after unlock.
First time Renoroot successfully completed and i performed the last ''sync'' and ''sync'' commands.
Now Renoroot seems to go on above 200k files without completing.
*edit.
Hmm interesting.
Within Magisk, SuperUser settings ive set ''Automatic Response'' to always ''grant''.
Now the apps which needed root seem to start, and until so far problem seems solved. (at first the apps were hanging, giving no prompt for SU)
Of course not the safest way, shall see if i can manage to create exceptions.

The renoroot exploit for temp root does not work with any other firmware versions than those mentioned in the thread.
And after unlocking and restoring TA you have no use for it anyway as you can get fully working root with magisk.
Anyway, I would never grant all root requests by default...

Reflashed 47.2.A.10.45.
Downloaded and flashed Magisk Beta from official site.
Upgraded Magisk Manager on device as prompted.
This solved my problem, SU grants permission to app after when i give permission (within Magisk->SU)
FYI.