Database Develop

Root - System vs Systemless

I have a SU question for those in the know.
Device: SCH-I545 VZW SGS4
Bootloader: VRUAMDK Original Loki exploitable, never took an OTA
ROM: Custom AOSP 7.1/CM14 based Nougat
Here goes, hopefully I make sense.
In the past custom ROMs used "system mode" for SU, 2.52 or 2.65. With the introduction of "systemless" the way of the future is becoming apparent. Some updated apps don't work well or at all with system mode.
The SCH-I545's bootloader is locked but can be gotten around with the "Loki" exploit by @drbliss for installing custom ROMs/kernels. The problem with SuperSU in systemless mode is patching the ramdisk with a locked bootloader. During the install of a systemless package when it gets to the step where the boot.img is patched it fails. Screen output will say "decompressing ramdisk" then "failure, aborting" and continue until complete but SU does not work.
Some SGS4 variants like the I9505 have an unlocked bootloader. So, for an experiment, I got a copy of the boot.img from someone using the same ROM as I (we have a unified device tree) after SU install and boot. This file has been patched by the SU flash process.
I took the ROM zip, deleted the boot.img, replaced it with the patched img, and flashed the ROM. Lo and behold it booted AND has SU access. The ROM flashes SuperSU 2.78-SR1 by chainfire.
During SU install from recovery it showed the usual failure when it attempted to patch the boot.img but since I had a "Pre-Patched" file systemless mode installed and works just fine. A quick look in the file system shows a systemless install. End result? Systemless install is possible on a locked BL device.
My question is how to get there. I am no developer. Beyond hacking/modding zips and editing the build.prop, updater-script, update-binary, etc. I get lost and java/C++ is a mystery. Is it possible to get it to succeed with something similar to the Loki process or by modifying Loki??
Just thinking out loud here but thought, input, etc. is most certainly welcome.

[Solved] Magisk?

Solved: See this post.
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
Sony Devices: If you're using stock kernel, it is using Sony's special ELF format. Magisk will repack it to standard AOSP format, which requires your device to be unlocked.
Click to expand...
Click to collapse
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?

I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.

Chamelleon said:
I'm on latest MM and no problems with new SuperSU. All latest updates installed and 2.81 and 2.82 are working well.
Click to expand...
Click to collapse
I guess you must be lucky then since Chainfire has advised Xperia users to stay on 2.79, as per the news article I linked.
Still, regardless of whether SuperSU works for some people or not, I'd still like to find out if MagiskSU is a viable alternative for Sony devices and what the correct procedure is to install it and retain all the phone's features.

Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.

Chamelleon said:
Did Your SuperSU app was converted to system app? Mine wasn't, maybe thats an answer.
Click to expand...
Click to collapse
Possibly; can't remember to be honest. Anyway, flashing back to 2.79 fixed the boot loop and I've disabled auto-update until Chainfire says otherwise.
I still want to learn about Magisk though; not keep discussing SuperSU
I found a few bits of info on the subject:
RootKernel can apparently repack the stock kernel with a DRM fix so that all the DRM features can be restored with an unlocked bootloader.
BootBridge can install Magisk without repacking the ELF kernel in AOSP format, which the author says is preferable. However, BootBridge itself requires an unlocked bootloader so the DRM is still an issue I guess... <-- This is only meant for specific older devices; not the Z3C.
Magisk Patch claims Magisk won't work without disabling Sony RIC and provides a fix if you haven't used RootKernel already.
Trying to piece it all together is a little confusing so if anyone has actually done it, I'd be interested to hear from you.

Do we even need the SuperSU updates? 2.79 works fine for me without any issues plus the new versions are maintained by the Chinese company (I'm using some different version compiled by Chainfire himself). The only problem is the update notification in Play Store tho....

nogaff said:
After the recent SuperSU 2.81 update sent my Z3C into a boot-loop I came across a few comments on this XDA article saying that MagiskSU is the way to go these days.
Now, I gather from this thread that the best way to root is to just install stock Marshmallow and run the provided installer then flash a root binary via TWRP.
However, the FAQ in the official Magisk post states:
So, if the bootloader needs to be unlocked to install Magisk, does that mean you can't have the phone's DRM features active? Or is it possible to restore the DRM stuff after Magisk has been installed (assuming you've backed up the DRM keys)?
Also, does the fact that Magisk repacks the kernel mean SafetyNet will always fail on a Sony device, regardless of Magisk Hide being enabled?
Click to expand...
Click to collapse
actually, i have my DRM partition and Magisk on my z3c UB. Here is what i did, first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition. oh! magisk hide works properly as well giving me full access to SafetyNet.

espaciosalter20 said:
first i did patch boot.img with magisk and then used ta-poc tool to restore my TA-backed up partition
Click to expand...
Click to collapse
I finally got a chance to try this out and I'm not having much success to be honest.
I'm starting off with an unlocked bootloader and flashing stock MM 23.5.A.1.291, then flashing TWRP.
In TWRP, the current version of Magisk (v14.0) refuses to install; it just complains about Sony ELF32 format and instructs me to use BootBridge, which is only supposed to be required for older devices like the Z2.
Anyway, I tried installing Magisk via BootBridge and it claims to have installed successfully, but then Magisk Manager says Magisk is not installed when I boot into Android (yes, I've rebooted a couple of times as well).
Next, I started over from the beginning and tried Magisk v13.3 instead, which at least begins to install, but then fails to patch the boot image.
Does anyone have a working method they could describe here?

Solution
I figured it all out by myself in the end. For anyone else having trouble, here's what I did:
Made sure I had a backup of my DRM keys!!! I already had one from when I first rooted my phone on KitKat, but I decided to make another backup using Universal TA Backup v2, just in case anything was wrong with the original.
Obtained the official Marshmallow 23.5.A.1.291 firmware from XperiFirm, created a .ftf file with Flashtool, unlocked the bootloader on my device and flashed the .ftf file via Flashtool.
Flashed TWRP custom recovery via fastboot.
Extracted the stock kernel.elf boot image from the .ftf file using Flashtool.
Ran ta_poc on the kernel.elf file, answering "Y" when prompted to disable Sony RIC*. This produced a repacked boot.img with the DRM features added back in.
Copied the boot.img to my SD card.
Booted to Android and installed the Magisk Manager apk.
Used the "Install" button in Magisk Manager and selected the boot.img on my SD card.
Noted the location of the patched_boot.img that Magisk Manager created, then booted into TWRP and flashed patched_boot.img.
Booted back into Android and checked Magisk Manager status.
My device is now fully rooted, has all the DRM features intact and is passing all SafetyNet checks.
As an alternative to steps 7-9, you could simply flash the boot.img from step 6 via TWRP and then also flash the Magisk zip file via TWRP. You'd end up with exactly the same result at step 10.
I believe you could even complete the installation without TWRP or any custom recovery at all, by using Magisk Manager to create a patched_boot.img, then copying it to your PC and flashing it via fastboot.
* Disabling Sony RIC in my boot.img was what solved all my problems. This thread suggests you don't need to do that any more, but I couldn't get it to work without doing so.

Hi, I recently installed magisk 14, I get it to work. However, somehow it broke my wifi and LTE functionality. DNS NOT FOUND. I have a m4 aqua with 6.0.1 ver.1.33. Do you have any idea what could be the cause of this problem?
Enviado desde mi E2306 mediante Tapatalk

any know magisk for Z3 Compact Docomo MM 6.1 Bootloader Lock ?

Hi nogaff,
I tried your solution but there are two difficulties I can't resolve:
1) Where can I download a valid TWRP image for the Sony Xperia Z4 Tablet? My search in the internet was without success, and TWRP doesn't seem to support this device.
2) I used the same procedure to patch the kernel:
TA_POC'd the kernel with disabling DM-verity and disabling Sony-RIC
copied this image to a SD-card
put the SD-card into my SGP771
patched this image with Magisk 22.1 (this version of Magisk supports officially my Android 7.1.1)
flashed this image using FlashTool (because I don't have a TWRP recovery for the SGP771) - flashing ended without error!
BUT​​The SGP771 stucks in a boot loop!!!​​Can you tell me if I forgot something?​
Regards
Ansgar

OTA Updates after Unlocking bootloader

hey guys, i wanna know if i will still get ota updates if i unlocked the bootloader ??
i wanna unlock it and if i didn't flash TWRP after unlocking it i will be able to install the update ??

This thread is pretty old and it's referring to a Nexus 5, but I think the info holds true. Unlocking wont' stop ota updates, and if all it is is unlocked, then the ota update should install.
It's when you install twrp, or root, or a new system image, etc... that's when the ota update won't install.
https://forum.xda-developers.com/google-nexus-5/help/unlocking-bootloader-prevent-automatic-t3003581

When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly
My question is can get OTA update ?

Ravirush said:
When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly
My question is can get OTA update ?
Click to expand...
Click to collapse
In order to maintain the OTA compatibility there is one thing to bear in mind. The system must have the same parity as a standard image.
Changes to the build.prop (camera 2) or swapping out a boot image change this parity. Put the original boot and build.prop back and you should be OK.
Perhaps the best way to think about this is the red pill or the blue pill...
As for rooting - for our Xiaomi A2's the best way to root is to :
Unlock the bootloader (this will wipe your data - ensure you have backups)
Swap the boot.img for one that is Magisk compatible (from this point your OTA is broken)
Install magisk (for the SU)
At this point to get back OTA capability one has to uninstall Magisk and put back a standard boot.img - This hasn't worked for me since going Pie (I have thus swallowed the red pill)
If you touch your build.prop or other system files IMHO you can bury the OTA.
If I want a new version of android I'll manually flash the new image and go back through the rooting process and finish by modifying my build.prop.
There are Magisk modules that provide systemless changes but I've not tested these myself - I prefer to know exactly what I'm doing with my build.prop.
To get back to standard you can always flash a standard system image and if you really want to be clean you can relock the bootloader which will reset your phone as if it was out of the box.

Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.
Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..
Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.
On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.
To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.
After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.

Ashik_salim_ said:
Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.
Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..
Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.
On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.
To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.
After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.
Click to expand...
Click to collapse
hi my friend. i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals

OTA update on rooted device with MagiskProps -> 3a

Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.

swangjang said:
Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.
Click to expand...
Click to collapse
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.

dirtyreturn said:
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.
Click to expand...
Click to collapse
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.

swangjang said:
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.
Click to expand...
Click to collapse
Oh, sorry.
1) I think it changes a build.prop entry for device manufacturer or model.
2) Pixel 5 apps? Do you mean specifically designed for this device? I have a 3xl also, and I think and it seems, that stock apps are the same. Ah, for example, the Google stock camera app - I am not sure if a Pixel 5 specific feature would disappear or not work or something.
3) I THINK you will need to. Like, at least with elementalx and kirisakura kernel the (?)script(?) looks to see if Magisk is installed and retains it. I am assuming the Google stock kernel does not .
4) unlocking the bootloader wipes the device, I believe. I would assume relocking the bootloader would. Personally, I've never relocked the bootloader on any device after unrooting . If you do relock, back up your internal storage as an incase , failsafe, or general rule or something.
Hopefully, there will be someone to chime in in case I am wrong.

Hi, i don't use OTA but full image for update but no, it don't break change props on pixel 5 but yes you need to flash magisk again.
Good update. No issues for november update

As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use

cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.

cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
With the Pixel 2 my process was
1. fastboot flash stock boot and dtbo images for your current build version. (Not sure if dtbo is really needed)
2. Apply OTA via ADB
3. Allow phone to boot and finish update
4. Use magisk to patch the boot image from the new build version
5. fastboot flash patched boot image.
I have used this method for three years with the Pixel 2 and only had one issue. I used smalipatcher to make mock GPS look like real GPS and apparently the magisk module needs to be re-created for each build.

j0nnyd said:
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.
Click to expand...
Click to collapse
I do this as well, but couldn't get the boot image patched through magisk for some reason. Anyone have a patched boot image they can share?

I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.

*deleted*

TonyApuzzo said:
I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.
Click to expand...
Click to collapse
1. What's your build.prop before upgrade?
2. Did you uninstall Magisk (restore/complete) before upgrade?
3. If #2 is 'NO', did your 'Restore Magisk Manager' and disable 'MagiskHide' before upgrade?
Thank you very much!

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.

Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.

pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.

SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!