[GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares

[mrsatan]

Could You specify what You mean?

So for a while on my XZ1 we need a kernel to get root. Eventually though Sony stopped gutting the features so you didn't really need a kernel. I figured out that I could just update to the latest security update. Flash twrp.img as recovery via adb. Let android boot so it creates it all. Then reboot to twrp and install magisk from the zip and it patched the boot.img to have root. It is honestly one of the easiest rooting ways I have ever seen on a Sony unit. I know my XZ1 has an A/B partition scheme but the Xperia 5 might be different. Either way it is worth a shot to try.

 

[MiMoHo]

@Miustone Thank you for providing this service! You uploaded a PixelExperience variant yesterday but the Xperia 5's Magisk-patched stock firmware kernel is still from July. Could you keep them up to date with every new firmware release? Would be much appreciated!

 

[Klaus N.]

@Miustone
Here's the boot_X-FLASH-ALL-A2CD.img for the J9210_Customized EU_1320-0801_55.1.A.9.101_R12B firmware, dual sim version (September security patch).
As your last post in your thread here was in July, I hope you don't mind, if I provide the magisk_patched.img for the afforementioned 9.101 firmware (both "Preserve force encryption" and "Preserve AVD 2.0/dm-verity" are set to active, ofc ).

Please let me know, if I should remove the magisk patched image again!

 

[Miustone]

@Miustone
Here's the boot_X-FLASH-ALL-A2CD.img for the 9.101 firmware, dual sim version (September security patch).
As your last post in your thread here was in July, I hope you don't mind, if I provide the magisk_patched.img for the afforementioned 9.101 firmware (both "Preserve force encryption" and "Preserve AVD 2.0/dm-verity" are set to active, ofc ).

Please let me know, if I should remove the magisk patched image again!

Since I have a lack of Time these Days, thanks for sharing! Would just be also good to know from which firmware it is. I will add it to Google Drive once I know it
Btw. It would be nice if more People would contribute Kernels from various firmwares to Me. I really appreciate that as long as it's done with the latest Magisk Managers and kept dm-verity and forced encryption. Community and so...

 

[Klaus N.]

Since I have a lack of Time these Days, thanks for sharing! Would just be also good to know from which firmware it is. I will add it to Google Drive once I know it
Btw. It would be nice if more People would contribute Kernels from various firmwares to Me. I really appreciate that as long as it's done with the latest Magisk Managers and kept dm-verity and forced encryption. Community and so...

I've edited the post above yours and added the exact designation of the firmware.

 

[Magissia]

Are you doing something specific ? Can we patch it ourselves ?
Patching it from magisk manager and flashing it should be enough ?

 

[Klaus N.]

Are you doing something specific ? Can we patch it ourselves ?
Patching it from magisk manager and flashing it should be enough ?

No, nothing specific; it's patched with "Preserve force encryption" and "Preserve AVD 2.0/dm-verity" set to active, nothing else. Yes, you can patch it by yourself, but it's only possible, if your device is alsredy rooted, ofc.

For example, if you're on a previous firmware, download the current firmware via FlashTool, convert the boot_X-blabla.sin to boot_X-blabla.img, then move/copy it to the internal or external sd of your device, then patch it with MagiskManager. Right after that, move/copy the created magisk_patched.img onto your pc. Now flash the appropriate firmware with newflasher. Once done, you can flash the magisk_patched.img with the commands from the op. Done!

 

[Miustone]

Guide overhauled like promised to some <3 Let Me know if i missed something

 

[Miustone]

Updated the Guide

 

[Miustone]

Updated the Thread again with more exactly Instructions and a typo fix