Before starting, your phone must have an unlockable bootloader. If your Xperia M5 have a permanently locked bootloader, unfortunately you can't use this kernel.
As you may already know, Sony enabled verified boot on Xperia M5 starting with the Marshmallow firmwares (30.2.A.0.100 / 30.2.B.0.100) just like on their recent flagships (Z3+/Z5/X Performance) and thus, dd Flasher Minimal won't work anymore because it writes into system partition, and so, dm-verity verification would fail and the phone would refuse to boot.
How it works?
The main issue is dm-verity, which prevents any kind of modification on system partition, so we must disable it. Unfortunately, you need to modify the kernel to disable dm-verity, and to flash a modified kernel, you'll need to unlock the bootloader, wiping your device unique DRM keys in the process. Fortunately, @tobias.waldvogel developed a tool which includes a DRM fix, aimed mostly at the Xperia flagships, but it also works very well with Xperia M5, and thanks to iovyroot/iovySU and the previous exploitable firmwares, we can take a TA Backup without much trouble!
So, in other words, this kernel is exactly the same as the stock from 30.2.A.0.100/30.2.B.0.100 firmware despite the following changes:
• Verified boot (dm-verity) disabled
• SuperSU v2.76 in system-less mode (and a small modification to make it survive factory reset)
• DRM fix library (more about that later)
Requirements
• Your device must have an unlockable bootloader. (you can check that in the Service Menu, on your phone, open the dialer and enter *#*#7378423#*#*, then go to Service Info => Configuration => Rooting Status)
• You must be running one of the supported firmwares (30.2.A.0.100/30.2.B.0.100) before flashing this kernel.
• ADB drivers and fastboot should be installed on the computer.
• (Optional, but highly recommended) A TA backup of your device, taken before unlocking its bootloader, to restore DRM related functions.
Instructions
I've splitted the instructions into three smaller sections. If you already have unlocked the device bootloader, jump straight to the 2nd section.
Backing up the TA partition and unlocking the bootloader
Flashing your device key
Flashing the modified kernel
Frequently Asked Questions
< placeholder >
Credits
The most important piece of this kernel (the DRM Fix library) was made by @tobias.waldvogel. He's also the developer of Root Kernel, which can patch kernels with this library on the fly. Unfortunately, Mediatek kernels have some oddities (like a 512-bytes header at the beginning of the zImage and RAM Disk) that prevents most tools from working without modifications, so I had to edit and patch those kernels manually. The system-less integration of SuperSU on this kernel was done using the official SuperSU installer from @Chainfire despite a minor tweak I did to make root access survive Factory Resets, so, credits (and thanks) to them.
As you may already know, Sony enabled verified boot on Xperia M5 starting with the Marshmallow firmwares (30.2.A.0.100 / 30.2.B.0.100) just like on their recent flagships (Z3+/Z5/X Performance) and thus, dd Flasher Minimal won't work anymore because it writes into system partition, and so, dm-verity verification would fail and the phone would refuse to boot.
How it works?
The main issue is dm-verity, which prevents any kind of modification on system partition, so we must disable it. Unfortunately, you need to modify the kernel to disable dm-verity, and to flash a modified kernel, you'll need to unlock the bootloader, wiping your device unique DRM keys in the process. Fortunately, @tobias.waldvogel developed a tool which includes a DRM fix, aimed mostly at the Xperia flagships, but it also works very well with Xperia M5, and thanks to iovyroot/iovySU and the previous exploitable firmwares, we can take a TA Backup without much trouble!
So, in other words, this kernel is exactly the same as the stock from 30.2.A.0.100/30.2.B.0.100 firmware despite the following changes:
• Verified boot (dm-verity) disabled
• SuperSU v2.76 in system-less mode (and a small modification to make it survive factory reset)
• DRM fix library (more about that later)
Requirements
• Your device must have an unlockable bootloader. (you can check that in the Service Menu, on your phone, open the dialer and enter *#*#7378423#*#*, then go to Service Info => Configuration => Rooting Status)
• You must be running one of the supported firmwares (30.2.A.0.100/30.2.B.0.100) before flashing this kernel.
• ADB drivers and fastboot should be installed on the computer.
• (Optional, but highly recommended) A TA backup of your device, taken before unlocking its bootloader, to restore DRM related functions.
Instructions
I've splitted the instructions into three smaller sections. If you already have unlocked the device bootloader, jump straight to the 2nd section.
Backing up the TA partition and unlocking the bootloader
Flashing your device key
Flashing the modified kernel
Frequently Asked Questions
< placeholder >
Credits
The most important piece of this kernel (the DRM Fix library) was made by @tobias.waldvogel. He's also the developer of Root Kernel, which can patch kernels with this library on the fly. Unfortunately, Mediatek kernels have some oddities (like a 512-bytes header at the beginning of the zImage and RAM Disk) that prevents most tools from working without modifications, so I had to edit and patch those kernels manually. The system-less integration of SuperSU on this kernel was done using the official SuperSU installer from @Chainfire despite a minor tweak I did to make root access survive Factory Resets, so, credits (and thanks) to them.
from xda-developers http://ift.tt/2c8tjg8
via IFTTT
No comments:
Post a Comment