[ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off

[trunghxf]

How about using the search function? If you you had, you would have found the answer to your question inside this thread

thanks dude, i forgot to use it, sorry >.<

 

[akak1]

Hi guys!

I'm a noob and I have three issues:

1. I have a z5 docomo (SO-01H) with bootloader unlock allowed: Yes. I'm on nougat but it only updates via OTA so I only have marshmallow FTF.
How do I extract kernel and system.sin from my phone? If I unlock bootloader on marshmallow I'll be stuck on 6.0 because OTA won't work. Can I use other FTF kernel? I have customized AU ftf on 7.0 or 7.1 for e6653.

2. BackupTA never works, I've been trying for the whole week with no luck. I used flashtool to backup TA partition and now I have two files (1.ta and 2.ta) I don't know what to do with them. Please guide.

3. Can I flash e6653 ftf after bootloader unlock (it gives device not compatible error on flash tool now) and/or use custom roms e6653?

Please guide, I wanna root. Thanks

 

[casouzaj]

Hi guys!

I'm a noob and I have three issues:

1. I have a z5 docomo (SO-01H) with bootloader unlock allowed: Yes. I'm on nougat but it only updates via OTA so I only have marshmallow FTF.
How do I extract kernel and system.sin from my phone? If I unlock bootloader on marshmallow I'll be stuck on 6.0 because OTA won't work. Can I use other FTF kernel? I have customized AU ftf on 7.0 or 7.1 for e6653.

2. BackupTA never works, I've been trying for the whole week with no luck. I used flashtool to backup TA partition and now I have two files (1.ta and 2.ta) I don't know what to do with them. Please guide.

3. Can I flash e6653 ftf after bootloader unlock (it gives device not compatible error on flash tool now) and/or use custom roms e6653?

Please guide, I wanna root. Thanks

Don't unlock your phone's bootloader before you achieve a backup of its TA partition. Backup TA V2 will be able to perform such a backup only if you downgrade to a stock Marshmallow firmware. Use Flashtool to flash it in flashmode. Wipe its data partition, in order to have a stable Marshmallow setup (you'll loose your data during the bootloader unlocking procedure, anyway). Whilst on Marshmallow, activate USB debugging connect your phone to your computer and run the backup TA tool. It will be successful if it produces a 2MB-long TA img file. Run flash_dk with this TA img file to create your DK.tft file.
You can now flash your Nougat ROM back, again through Flashtool.
Copy that ROM's ftf file to the unpacked rootkernel folder, and rename its extention to zip. Extract kernel.sin out of it. In Flashtool, click on Tools > Sin editor, select that kernel.sin file and click on Extract data. A kernel.elf file will be produced. You can use it in rootkernel to produce a new_boot.img. Choose to disable Sony RIC during the process. Say No to all the other questions.
Now unlock your phone's bootloader. Use fastboot commands to flash a TWRP img file to the FOTAKernel partition and the new_boot.img file to the boot partition. To enter TWRP, hold both the power and the volume down buttons. When your phone vibrates, release the power button. When the screen lights up, release the volume down button. Install Magisk. In my Z5 Compact phone I used the stable 19.2 version (had issues with the Canary builds). Install also the DRM fix zip file.
Now copy the DK.tft file produced by flash_dk to C:\Users\your_username\.flashTool\firmwares, and select Device keys in Flashtool, in flashmode. Flash it.
OK, turn your phone on and tweak Magisk Manager the way you have, most probably, read a lot about.

Hope to have not forgotten something important.

Sent from my Xperia Z5 Compact using XDA Labs

 

[akak1]

Don't unlock your phone's bootloader before you achieve a backup of its TA partition. Backup TA V2 will be able to perform such a backup only if you downgrade to a stock Marshmallow firmware. Use Flashtool to flash it in flashmode. Wipe its data partition, in order to have a stable Marshmallow setup (you'll loose your data during the bootloader unlocking procedure, anyway). Whilst on Marshmallow, activate USB debugging connect your phone to your computer and run the backup TA tool. It will be successful if it produces a 2MB-long TA img file. Run flash_dk with this TA img file to create your DK.tft file.
You can now flash your Nougat ROM back, again through Flashtool.
Copy that ROM's ftf file to the unpacked rootkernel folder, and rename its extention to zip. Extract kernel.sin out of it. In Flashtool, click on Tools > Sin editor, select that kernel.sin file and click on Extract data. A kernel.elf file will be produced. You can use it in rootkernel to produce a new_boot.img. Choose to disable Sony RIC during the process. Say No to all the other questions.
Now unlock your phone's bootloader. Use fastboot commands to flash a TWRP img file to the FOTAKernel partition and the new_boot.img file to the boot partition. To enter TWRP, hold both the power and the volume down buttons. When your phone vibrates, release the power button. When the screen lights up, release the volume down button. Install Magisk. In my Z5 Compact phone I used the stable 19.2 version (had issues with the Canary builds). Install also the DRM fix zip file.
Now copy the DK.tft file produced by flash_dk to C:\Users\your_username\.flashTool\firmwares, and select Device keys in Flashtool, in flashmode. Flash it.
OK, turn your phone on and tweak Magisk Manager the way you have, most probably, read a lot about.

Hope to have not forgotten something important.

Thank you so much. But as I stated, I don't have nougat ROM ftf file and its available nowhere. The only ftf files available are lollipop and marshmallow.
I downgraded it to lollipop and marshmallow countless times but backupTA doesn't work at all. So I can't have a TA backup except with flash tool which gives me two files with the extension .ta. I don't know which one to use and what to do with the .ta file.

So j have to extract kernel from my phone which is running nougat. I can downgrade to lollipop or marshmallow but to get back to nougat I have to download OTA. With bootloader unlocked, OTA won't work and i will be stuck with marshmallow, unless I could use ftf files for other models such as e6653, Which currently I can't.

Hope you understood the issue. Thanks

 

[casouzaj]

Thank you so much. But as I stated, I don't have nougat ROM ftf file and its available nowhere. The only ftf files available are lollipop and marshmallow.
I downgraded it to lollipop and marshmallow countless times but backupTA doesn't work at all. So I can't have a TA backup except with flash tool which gives me two files with the extension .ta. I don't know which one to use and what to do with the .ta file.

So j have to extract kernel from my phone which is running nougat. I can downgrade to lollipop or marshmallow but to get back to nougat I have to download OTA. With bootloader unlocked, OTA won't work and i will be stuck with marshmallow, unless I could use ftf files for other models such as e6653, Which currently I can't.

Hope you understood the issue. Thanks

After you manage to get a backup of your TA partition through Backup TA v2, whist running Marshmallow,, prior to unlocking the bootloader, you can perform the OTA upgrade to Nougat and move on.

Sent from my Xperia Z5 Compact using XDA Labs

 

[akak1]

After you manage to get a backup of your TA partition through Backup TA v2, whist running Marshmallow,, prior to unlocking the bootloader, you can perform the OTA upgrade to Nougat and move on.

Tried that hundreds of times even on lollipop. No success. Back TA V2 doesn't work for my phone

 

[casouzaj]

Tried that hundreds of times even on lollipop. No success. Back TA V2 doesn't work for my phone

I'll try to make some tests with TA backup performed by Flashtool, thing I've never made so far, and return to you with my findings.

Sent from my Xperia Z5 Compact using XDA Labs

 

[akak1]

I'll try to make some tests with TA backup performed by Flashtool, thing I've never made so far, and return to you with my findings.

Sent from my Xperia Z5 Compact using XDA Labs

Thank you sir. I finally managed to get the TA backup successfully. I downloaded all MM roms and tried with each one of them. One worked and I got ~2MB img file.
Then i proceeded to unlock the bootloader as stated on Sony's website. The phone did a factory reset (telling from the time it took to bootup).

Did the process and got the modified boot.img while being on MM. Also got the DK.ftf file.

fastboot flash boot boot.img command didnt work while being in the same command window so copied the boot.img in the ADB tools folder, flashed the boot.img via fastboot. No errors.

But when the phone turns on there is no Super SU, i cant manage to boot into TWRP and it seems as if nothing happened. Even the OTA is downloading.

Should i try unlocking the bootloader again? The service menu--> configuration still shows Bootloader unlock allowed: yes and all keys in security test are [Key OK] [Active] except FIDO_KEYS: Not provisioned, provision failed.

I havent flashed the DK.ftf yet.
If the boot.img got pushed successfully, I dont know what i did wrong. the phone works fine as it did before. Even flashtool says root access denied.

Thank you, once again for your support.

 

[casouzaj]

Thank you sir. I finally managed to get the TA backup successfully. I downloaded all MM roms and tried with each one of them. One worked and I got ~2MB img file.
Then i proceeded to unlock the bootloader as stated on Sony's website. The phone did a factory reset (telling from the time it took to bootup).

Did the process and got the modified boot.img while being on MM. Also got the DK.ftf file.

fastboot flash boot boot.img command didnt work while being in the same command window so copied the boot.img in the ADB tools folder, flashed the boot.img via fastboot. No errors.

But when the phone turns on there is no Super SU, i cant manage to boot into TWRP and it seems as if nothing happened. Even the OTA is downloading.

Should i try unlocking the bootloader again? The service menu--> configuration still shows Bootloader unlock allowed: yes and all keys in security test are [Key OK] [Active] except FIDO_KEYS: Not provisioned, provision failed.

I havent flashed the DK.ftf yet.
If the boot.img got pushed successfully, I dont know what i did wrong. the phone works fine as it did before. Even flashtool says root access denied.

Thank you, once again for your support.

As I stated in my first (long) reply to you, use Magisk (stable v19.2) to get root access. SuperSU is deprecated. Yes, flash the DK.tft file in flashmode, through Flashtool. Use a fastboot command to flash a TWRP img file to the FOTAKernel (the exact way it's written) partition. Then, enter TWRP by holding both the power and the volume down buttons. Once in TWRP, install the Magisk zip file and the DRM fix zip file, as well.

Sent from my Xperia Z5 Compact using XDA Labs

 

[akak1]

Thank you sir. I finally managed to get root and TWRP. But i am stuck on MM because i cant flash any other variant's FTF or even international one. It always gives errors and OTAs wont work.
All custom roms bootloop so no use.
But at least Im rooted and debloated on stock MM.

Thank you for your help.

 

[casouzaj]

Thank you sir. I finally managed to get root and TWRP. But i am stuck on MM because i cant flash any other variant's FTF or even international one. It always gives errors and OTAs wont work.
All custom roms bootloop so no use.
But at least Im rooted and debloated on stock MM.

Thank you for your help.

If I remember it right, I stated that you did the OTA upgrade right after you managed to have a backup of your TA partition, prior to unlocking the bootloader. Well, since you have that backup, you could use either Flashtool or a dd command to re-lock your bootloader, then start the whole thing all over again, but now from Nougat. It's your choice.

Sent from my Xperia Z5 Compact using XDA Labs

 

[ZoHere]

Xperia X Performance, XZ and XZs ONLY (Xperia X and Xperia X Compact must skip this):
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:

/system/vendor/etc/[B][COLOR="Blue"]fstab.qcom[/COLOR][/B]
/system/vendor/etc/init/hw/[B][COLOR="blue"]init.qcom.rc[/COLOR][/B]
/system/vendor/etc/init/hw/[B][COLOR="blue"]init.target.rc[/COLOR][/B]

(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)

Rootkernel's procedure for Oreo kernel ONLY:
1. Download and extract attached Rootkernel V5.23 (UNOFFICIAL 2.5)
2. Download attached flashable zip (DRM-fix_System_Mode.zip) and push it somewhere in your device (internal memory or sdcard)
3. Run rootkernel script with Oreo stock kernel.elf (eg.: rootkernel kernel.elf boot.img)
4. Say yes (Y) to everything - If you want munjeni's TA PoC option, ensure your TA.img (case sensitive) is located at rootkernel's root folder, and say no (N) to DRM fix
5. You're done!

Rootkernel's output should look like this:

Rootkernel V5.23 (UNOFFICIAL 2.5)

- Unpacking kernel
  Found elf boot image
  Kernel version: 3.18.66-perf-g27a9189
  Found appended DTB
- Detected vendor: somc (Sony), device: dora (Xperia X Performance), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 8.0.0
- Android Oreo requires additional files! Continue? (Say yes to copy) [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  init.rc (patched)
  fstab.qcom (copied)
  init.qcom.rc (copied and patched)
  init.target.rc (copied and patched)
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] [B][COLOR="Blue"]Y[/COLOR][/B]
  Patching fstab in dtb to disable dm-verity
- Sony RIC is enabled. Disable? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  Disabling Sony RIC
- force-encrypt is enabled. Disable? (Say yes if you decrypt /data) [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  Disabling force-encrypt
- Install DRM fix? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  1. DRM fix preload line added successfully!
  2. DRM libraries still need to be flashed manually on TWRP recovery before 1st boot!!
     System mode, flash: DRM-fix_System_Mode.zip
- All done! Continue? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
- Creating new initramfs
- Creating boot image
- Cleaning up
Done

Flash patched kernel:
1. Flash Oreo ftf (wiping everything, excluding nothing - except *.ta files - if any)
2. Unplug device and DO NOT turn it on
3. Fastboot newly created boot.img
4. Fastboot TWRP for your device
5. Unplug device and DO NOT turn it on again
6. Enter TWRP recovery and flash: DRM-fix_System_Mode.zip << YOU CAN SKIP THIS STEP IF YOU CHOOSE munjeni's TA PoC OPTION!!
7. You're done!

Root:
- After step 6 above, flash latest Magisk zip (SuperSU seems not to work properly yet)

Known issues:
- Magisk zip installation may fail, and device may also fall in a bootloop
- If you're facing this ^, do whole procedure again, but DO NOT flash Magisk zip, instead, turn device on, install latest Magisk Manager, patch boot.img and flash it (fastboot it)!


As always, TRY IT AT YOUR OWN RISK!

Credits:
@tobias.waldvogel ofc
@sToRm// for additional ramdisk files hint (man, you're insane!)

Enjoy it!

I just flashed drm fix via twrp for my Xperia X android 8.0.0 doesn't fix x-reality, vivid mode

 

[someone755]

*snip*

I don't want to quote the entire post, but I've found out something that is very relevant to it;

When using rootkernel on an Xperia X Compact (stock Oreo 8.0), and using munjeni's TA.img hack, there are big problems for users if/when the battery runs out completely (to 0%), and the phone shuts down. This has happened twice to me so far, but I've only just bothered with fixing the issue today.
The problem is that after draining the battery completely and the phone shutting down, the cellular radio no longer works. It finds available networks, but refuses to connect to any of them. At one point it kept saying the SIM card was locked and kept asking for the SIM PIN, every few seconds.
Looking at the logcat, the system implies an error with the 'tad' process being unable to find a `TA.img`:

07-07 15:24:44.157  2476  2476 E tad     : Failed to open /data/local/tmp/TA.img (No such file or directory)

The file at `/data/local/tmp/init.ta_poc-log.txt` also says this:

cat init.ta_poc-log.txt
Executing init.ta_poc.sh:
- /data/local/tmp/TA.img not found!
- Copying /sbin/TA.img to /data/local/tmp/TA.img
cp: bad '/sbin/TA.img': Permission denied
- Wiping drm folders (credmgr, drm and mediadrm)
All done!

Executing init.ua_modem_switcher.sh:
- Removing old modem_switcher_status file
- Running /sbin/ua-modem-switcher binary
- ua-modem-switcher finished with status 255
All done!

So I used adb and pushed my own TA.img to the specified location. Now everything related to cellular networks seem to work, and the `init.ta_poc-log.txt` file also agrees:

cat init.ta_poc-log.txt
Executing init.ta_poc.sh:
- Found /data/local/tmp/TA.img
- Chown-ing /data/local/tmp/TA.img
- Chmod-ing /data/local/tmp/TA.img
All done!

Executing init.ua_modem_switcher.sh:
- Removing old modem_switcher_status file
- Running /sbin/ua-modem-switcher binary
- ua-modem-switcher finished with status 0
All done!

After this, in the logcat, a process called `tadif` complains that it cannot connect to `tad`, literally in the first line of my logcat. This error goes away some hundred lines later, when `tad` announces that it is "Accepting connections." So the problem seems to be fixed.
I have no idea why or how the TA.img gets deleted, or why `init.ta_poc.sh` doesn't have permission to copy it (because it does exist inside /sbin/), or why the TA.img is necessary for the modem to work properly.
Any answers or suggestions are of course appreciated, I just felt the need to share this bug I've found, and how I fixed it; It might help somebody in the future, thinking of flashing the system anew.

______________
EDIT (July 9th, 2019): The 'phone' Android process stops every few hours if I'm abusing my phone and using mobile data constantly. This disables mobile data and calls. Pressing "Ok" in the Android force close prompt reboots the process and mobile network functionality goes back to normal within a few seconds.
This could be a major problem, especially if it happens during a call or some such. I haven't debugged it yet, but I'm jotting it down here just in case I ever come back to this. I don't know what exactly, or why it happens, but after using exclusively mobile data for a few hours of continuous screen on time, it happens seemingly sporadically. It happened to me at least twice yesterday.
I also haven't tried draining the battery to 0% again to see if the TA.img disappears again (as one wouldn't normally try and discharge their phone completely). I also hope to update you on this if I'm ever unfortunate enough to run out of battery again (which, by my recent track record, should happen again by the end of the month, haha).

______________
EDIT (July 14th, 2019): My phone just froze after System UI became unresponsive and I was forced to reboot the device. Upon boot, the TA.img was again missing and my mobile data again broken. It's only by luck that I have my TA.img saved on Google Drive and have a laptop with me on vacation.
I've noticed that the TA.img in /sbin does exist, but it seems to be corrupt, as its size shows 0MB (my TA.img clocks in at about 2MB). It might be that fixing the TA.img inside /sbin could be a permanent fix, but as of right now, all I did was I whipped up a zip to flash my TA.img to /data/local/tmp/TA.img in recovery and saved the zip locally on my phone for any future use. Sadly I didn't manage to get any ADB logs of the SystemUI crash to figure out how and why exactly this crash affected the TA.img specifically, but I'm again just jotting ideas down for any future readers (and very likely my future self as well).
So, a total of 7 days without a mobile data crash -- I wonder if this is a coincidence? I'll of course edit this post in the future if I find any new data.

 

[seyrarms]

Xperia X Performance, XZ and XZs ONLY (Xperia X and Xperia X Compact must skip this):
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:

/system/vendor/etc/[B][COLOR="Blue"]fstab.qcom[/COLOR][/B]
/system/vendor/etc/init/hw/[B][COLOR="blue"]init.qcom.rc[/COLOR][/B]
/system/vendor/etc/init/hw/[B][COLOR="blue"]init.target.rc[/COLOR][/B]

(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)

Rootkernel's procedure for Oreo kernel ONLY:
1. Download and extract attached Rootkernel V5.23 (UNOFFICIAL 2.5)
2. Download attached flashable zip (DRM-fix_System_Mode.zip) and push it somewhere in your device (internal memory or sdcard)
3. Run rootkernel script with Oreo stock kernel.elf (eg.: rootkernel kernel.elf boot.img)
4. Say yes (Y) to everything - If you want munjeni's TA PoC option, ensure your TA.img (case sensitive) is located at rootkernel's root folder, and say no (N) to DRM fix
5. You're done!

Rootkernel's output should look like this:

Rootkernel V5.23 (UNOFFICIAL 2.5)

- Unpacking kernel
  Found elf boot image
  Kernel version: 3.18.66-perf-g27a9189
  Found appended DTB
- Detected vendor: somc (Sony), device: dora (Xperia X Performance), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 8.0.0
- Android Oreo requires additional files! Continue? (Say yes to copy) [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  init.rc (patched)
  fstab.qcom (copied)
  init.qcom.rc (copied and patched)
  init.target.rc (copied and patched)
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] [B][COLOR="Blue"]Y[/COLOR][/B]
  Patching fstab in dtb to disable dm-verity
- Sony RIC is enabled. Disable? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  Disabling Sony RIC
- force-encrypt is enabled. Disable? (Say yes if you decrypt /data) [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  Disabling force-encrypt
- Install DRM fix? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  1. DRM fix preload line added successfully!
  2. DRM libraries still need to be flashed manually on TWRP recovery before 1st boot!!
     System mode, flash: DRM-fix_System_Mode.zip
- All done! Continue? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
- Creating new initramfs
- Creating boot image
- Cleaning up
Done

Flash patched kernel:
1. Flash Oreo ftf (wiping everything, excluding nothing - except *.ta files - if any)
2. Unplug device and DO NOT turn it on
3. Fastboot newly created boot.img
4. Fastboot TWRP for your device
5. Unplug device and DO NOT turn it on again
6. Enter TWRP recovery and flash: DRM-fix_System_Mode.zip << YOU CAN SKIP THIS STEP IF YOU CHOOSE munjeni's TA PoC OPTION!!
7. You're done!

Root:
- After step 6 above, flash latest Magisk zip (SuperSU seems not to work properly yet)

Known issues:
- Magisk zip installation may fail, and device may also fall in a bootloop
- If you're facing this ^, do whole procedure again, but DO NOT flash Magisk zip, instead, turn device on, install latest Magisk Manager, patch boot.img and flash it (fastboot it)!


As always, TRY IT AT YOUR OWN RISK!

Credits:
@tobias.waldvogel ofc
@sToRm// for additional ramdisk files hint (man, you're insane!)

Enjoy it!

Hello sir. I have problem to put aditional filesystem_files folder to rootkernel. can you explain more please, because i'm tired where put this folder and code to run this script just until :

Rootkernel V5.23

- Unpacking kernel
  Found elf boot image
  Kernel version: 3.18.66-perf-g6b8cda40c6b9
  Found appended DTB
- Detected vendor: somc (Sony), device: kagura, variant: kddi
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 8.0.0

I have waited about five minutes and nothing happened

I know what happen can't use, because i use official root kernel and thanks for this tool to give my sony japan can do use this tool :good:

 

[randisaaputra]

Xperia X Performance, XZ and XZs ONLY (Xperia X and Xperia X Compact must skip this):
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:

(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)

Rootkernel's procedure for Oreo kernel ONLY:
1. Download and extract attached Rootkernel V5.23 (UNOFFICIAL 2.5)
2. Download attached flashable zip (DRM-fix_System_Mode.zip) and push it somewhere in your device (internal memory or sdcard)
3. Run rootkernel script with Oreostock kernel.elf (eg.: rootkernel kernel.elf boot.img)
4. Say yes (Y) to everything - If you want munjeni's TA PoC option, ensure your TA.img (case sensitive) is located at rootkernel's root folder, and say no (N) to DRM fix
5. You're done!

Rootkernel's output should look like this:

I just flashed drm fix via twrp for my Xperia X android 8.0.0 doesn't fix x-reality, vivid mode

hey, so my phone was on Nougat 39.2.B.0.36, am i still need to follow this steps or just using the tutorial on 1st page?

 

[seyrarms]

hey, so my phone was on Nougat 39.2.B.0.36, am i still need to follow this steps or just using the tutorial on 1st page?

You can't use this tutor cause for oreo maybe from first page can do. I can help for make this boot for you

 

[foudremars]

Which device version? H43311 or H4331 . I can try but i havent L2 Duo.
---------- Post added at 03:27 PM ---------- Previous post was at 03:19 PM ----------
Hi man can you update twrp version pls?
---------- Post added at 03:46 PM ---------- Previous post was at 03:27 PM ----------

I can help you.
@tobias.waldvogel Hi man can you update twrp version pls?

I need TWPR for L2 H4331. Can you help me? Thanks.

 

[RintSo]

the script 2.3&2.5 works SAME for Nougat kernels
the script 2.3&2.5 works same for OREO KERNELS if DEVICE is X
the script 2.3 wont work for OREO and all other devices (XP XZ XZs etc)
the script 2.5 & non X device with OREO will work only if the required files are extracted from system.sin

---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------



basically script 2.3 was intended to work globally but EXTRA code added to differentiate fstab file for xperia X f5121 and F5122 ONLY!

---------- Post added at 12:51 PM ---------- Previous post was at 12:04 PM ----------



WHICH device sir?
if its z3/z3+/z5/z5 then orginal script works fine!
for X on Oreo (8.0) v2.3 or v2.5 both works (since the fstab file is still in the ramdisk however
for Xperformance, Xcompact, XZc, XZs on Nougat kernel, version 2.5 & placing those files is MUST from system.sin

and last but not least,
for Nougat(7.1.1) all X till Xzs v2.3 works fine

NOTED

 

[zputnyq]

Hi guys,
I want to use root kernel for rooting, but I only have windows xp now. Does this tool works on windows xp ?

 

[rumcum]

Congratulation

Xperia X Performance, XZ and XZs ONLY (Xperia X and Xperia X Compact must skip this):
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:

/system/vendor/etc/[B][COLOR="Blue"]fstab.qcom[/COLOR][/B]
/system/vendor/etc/init/hw/[B][COLOR="blue"]init.qcom.rc[/COLOR][/B]
/system/vendor/etc/init/hw/[B][COLOR="blue"]init.target.rc[/COLOR][/B]

(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)

Rootkernel's procedure for Oreo kernel ONLY:
1. Download and extract attached Rootkernel V5.23 (UNOFFICIAL 2.5)
2. Download attached flashable zip (DRM-fix_System_Mode.zip) and push it somewhere in your device (internal memory or sdcard)
3. Run rootkernel script with Oreo stock kernel.elf (eg.: rootkernel kernel.elf boot.img)
4. Say yes (Y) to everything - If you want munjeni's TA PoC option, ensure your TA.img (case sensitive) is located at rootkernel's root folder, and say no (N) to DRM fix
5. You're done!

Rootkernel's output should look like this:

Rootkernel V5.23 (UNOFFICIAL 2.5)

- Unpacking kernel
  Found elf boot image
  Kernel version: 3.18.66-perf-g27a9189
  Found appended DTB
- Detected vendor: somc (Sony), device: dora (Xperia X Performance), variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 8.0.0
- Android Oreo requires additional files! Continue? (Say yes to copy) [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  init.rc (patched)
  fstab.qcom (copied)
  init.qcom.rc (copied and patched)
  init.target.rc (copied and patched)
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] [B][COLOR="Blue"]Y[/COLOR][/B]
  Patching fstab in dtb to disable dm-verity
- Sony RIC is enabled. Disable? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  Disabling Sony RIC
- force-encrypt is enabled. Disable? (Say yes if you decrypt /data) [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  Disabling force-encrypt
- Install DRM fix? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
  1. DRM fix preload line added successfully!
  2. DRM libraries still need to be flashed manually on TWRP recovery before 1st boot!!
     System mode, flash: DRM-fix_System_Mode.zip
- All done! Continue? [Y/n] [B][COLOR="blue"]Y[/COLOR][/B]
- Creating new initramfs
- Creating boot image
- Cleaning up
Done

Flash patched kernel:
1. Flash Oreo ftf (wiping everything, excluding nothing - except *.ta files - if any)
2. Unplug device and DO NOT turn it on
3. Fastboot newly created boot.img
4. Fastboot TWRP for your device
5. Unplug device and DO NOT turn it on again
6. Enter TWRP recovery and flash: DRM-fix_System_Mode.zip << YOU CAN SKIP THIS STEP IF YOU CHOOSE munjeni's TA PoC OPTION!!
7. You're done!

Root:
- After step 6 above, flash latest Magisk zip (SuperSU seems not to work properly yet)

Known issues:
- Magisk zip installation may fail, and device may also fall in a bootloop
- If you're facing this ^, do whole procedure again, but DO NOT flash Magisk zip, instead, turn device on, install latest Magisk Manager, patch boot.img and flash it (fastboot it)!


As always, TRY IT AT YOUR OWN RISK!

Credits:
@tobias.waldvogel ofc
@sToRm// for additional ramdisk files hint (man, you're insane!)

Enjoy it!

Nice job! Very useful.