Database Users

[FIX][DM-Verity][Oneplus3/3T]DM-Verity/Force Encryption Patched Boot Image

I am creating this thread keeping in my mind the several posts in various threads mentioning that they have accidentally triggered the DM-Verity flag and have an annoying message during startup or due to force encryption in the boot image the phone went back to encrypted state after flashing a new Stock Oxygen OS zip file in TWRP recovery.
So I decided to start a thread where I will post the links to the OFFICIAL BOOT IMAGES of Oxygen OS ROMs for both OnePlus3 and OnePlus3T which have been patched to disable the DM-Verity Flag and to disable the Force encryption that is present in the Stock Oxygen OS ROM.
NB: This thread is only for Nougat Based OOS ROMs. For disabling Dm-Verity and force Encryption in PIE OOS ROMs refer to my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324. For Disabling DM-Verity in Oreo Based OOS ROMs visit my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
THIS IS FOR BOTH ONEPLUS 3 and 3T and read the instructions carefully and apply the file specific for your model
Disclaimer: I am not responsible for any damage to your phone by using this...
Nothing has been changed....
It is 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Links:
For ONEPLUS 3T
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/vm2k81s3pregdiv/boot-patched-4.5.1-OP3T.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/m8e3nu4ak4u1zkz/boot-patched-4.5.0-OP3T.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/g5rk4284lzyvqnu/boot-patched-4.1.7-OP3T.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/j3802c259gea6f2/boot-patched-4.1.6-OP3T.img[/URL]
Patched Boot Image Stable OOS 4.1.5
[url]http://www.mediafire.com/file/78ej52gmthok212/boot-patched-OOS4.1.5.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 15
http://www.mediafire.com/file/a436larx3ddx00l/boot-patched-Beta15-OP3T.img
Patched Boot Image OOS Beta 14
http://www.mediafire.com/file/brlvdth86lxi0yl/boot-patched-Beta14-OP3T.img
Patched Boot Image OOS Beta 13
http://www.mediafire.com/file/2clnhl0x4vu8bu8/boot-patched-Beta13-OP3T.img
Patched Boot Image OOS Beta 12
http://www.mediafire.com/file/2214mr1adpdwlx4/boot-patched-Beta12-OP3T.img
Patched Boot Image OOS Beta 11
http://www.mediafire.com/file/hywcwmv0a993ah5/boot-patched-Beta11-OP3T.img
Patched Boot Image OOS Beta 10
http://www.mediafire.com/file/n7nu0wj266e8fhh/boot-patched-Beta10-OP3T.img
Patched Boot Image OOS Beta 9
[url]http://www.mediafire.com/file/5lkp6fi33u9lkpt/boot-patched-Beta9-OP3T.img[/URL]
Patched Boot Image OOS Beta 8
[url]http://www.mediafire.com/file/4d5zrpff4jakjgk/boot-patched-OOS_Beta_8.img[/URL]
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/srdurw9pg4f614f/boot-patched-4.5.1-OP3.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/nrbuddj0652bf4u/boot-patched-4.5.0-OP3.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/2cb3jrqckb4suxw/boot-patched-4.1.7-OP3.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/ytax9vfa9lyhd6d/boot-patched-4.1.6-OP3.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 24
http://www.mediafire.com/file/8fcbeiduhiewc9v/boot-patched-Beta24-OP3.img
Patched Boot Image OOS Beta 23
http://www.mediafire.com/file/9i3snrmmsinczct/boot-patched-Beta23-OP3.img
Patched Boot Image OOS Beta 22
http://www.mediafire.com/file/bauq66z2s6o2k1q/boot-patched-Beta22-OP3.img
Patched Boot Image OOS Beta 21
http://www.mediafire.com/file/r31feak94y3cm5z/boot-patched-Beta21-OP3.img
Patched Boot Image OOS Beta 20
http://www.mediafire.com/file/5h32hzw5ot1gbba/boot-patched-Beta20-OP3.img
Patched Boot Image OOS Beta 19
http://www.mediafire.com/file/y6446j7sxiw9jwx/boot-patched-Beta19-OP3.img
Patched Boot Image OOS Beta 18
http://www.mediafire.com/file/zfsji9mjjds7a6n/boot-patched-Beta18-OP3.img
Patched Boot Image OOS Beta 17
[url]http://www.mediafire.com/file/mrqhkq7igt7x4na/boot-patched-Beta17-OP3.img[/URL]
USAGE FOR STOCK OOS:
# Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)
# Restart back to TWRP Recovery.
# Done.
# Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual
# You dont have to worry about triggering DM-Verity or Getting Force Encrypted again...
VERY IMPORTANT: FOR PEOPLE WHO HAVE ALREADY TRIGGERED DM-VERITY ON THEIR OOS OR CUSTOM ROM AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY, READ MY POST 2. AFTER GETTING RID OF DM-VERITY BY FOLLOWING THE STEPS IN POST 2, NEXT TIME ONWARDS WHILE UPDATING YOUR OOS OR CUSTOM ROM FOLLOW THE INSTRUCTIONS IN THIS OP TO KEEP YOUR OOS AND PHONE FREE FROM THE TROUBLE OF DM-VERITY AND FORCE ENCRYPTION...
FAQs:
Q: Is the boot.img file altered in anyway?
A: As mentioned above its 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Q: My phone is already encrypted, will I lose encryption?
A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..
Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose data/apps accidentally while updating OOS after I lose TWRP ...Can this be corrected by using this method?
A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..
Q: I am Rooting my phone using Magisk/Supersu then why do i need this?
A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..
Q: How to flash the patched boot.img in TWRP?
A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.
Q: Can I use it for CUSTOM ROMs? / What to do while updating CUSTOM ROMs?
A: For hassle free and the best results whenever you update CUSTOM ROMs always do it this way...
The below steps are for CUSTOM ROMs only. (For STOCK ROMs follow the main step mentioned above in the section USAGE)...
1.Go to TWRP
2.Flash the required firmware zip file
3.Flash the corresponding patched boot IMG
4.Flash the ROM whether LINEAGE, RR, ASOP, etc.
5.Flash gapps
6.Flash root (magisk /su)
7.Flash kernel
8.At last Reboot...
There will not be any problem ever...
You can reboot after step 5
Steps 6,7 are optional
Q: What is "-Xn" seen after the OOS Version in the settings menu?
A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity and forced encryption..
Hope you find it useful...
Will update as newer OOS versions come....
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...

THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS OR OPEN BETA OR CUSTOM ROM. CONFIRMED WORKING EVEN IN THE LATEST OOS 4.5.1/BETA Nougat Roms...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
10) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
11) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT: If you are attempting this method on a a CUSTOM ROM then after Step 10 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...

Thanks mate..... You made my day..... Working perfectly.

Nice to see this thread on the day of release of oos 4.1.5 itself.

Deleted..

So well explained and working perfectly
One if the most detail step by step explanation
Thanks dev.

Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?

MohamedRaafat said:
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
Click to expand...
Click to collapse
Do the second method only if you trigger DM Verity while installing 4.1.5
To be sure you don't trigger DM Verity while installing 4.1.5 follow the instructions in the OP...

Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...

prorokrak said:
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
Click to expand...
Click to collapse
I have been thinking about it for the past few days...
Anyways I thought as no one asked they were not interested in getting the patched boot images for op3...
Ok.. they have released OOS 4.1.6..
So will push the links for the patched boot images for both op3 and op3T tomorrow after I test and get hands on the flashable ROMs.

The OP has been updated to accomodate both ONEPLUS 3T and ONEPLUS 3
Now this thread can be used for both models and will be updated as new OOS version come..
Enjoy!!!

NEW UPDATE RELEASED!!!
Links in OP...
Oxygen OOS 4.1.6 patched boot images for ONEPLUS 3T and ONEPLUS 3...

Thenks for this!

sparky vicky said:
How did you flashed the bootimg? through twrp? it's asking for 3 options like boot, recovery,system? im confused
Click to expand...
Click to collapse
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...

Xennet said:
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Click to expand...
Click to collapse
Yes i choose boot but still the warning showing on boot

sparky vicky said:
Yes i choose boot but still the warning showing on boot
Click to expand...
Click to collapse
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??

Im on OP3T, OOS 4.1.6

sparky vicky said:
Im on OP3T, OOS 4.1.6
Click to expand...
Click to collapse
Which is the warning being shown and explain the steps you did

Xennet said:
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Click to expand...
Click to collapse
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
Xennet said:
Which is the warning being shown and explain the steps you did
Click to expand...
Click to collapse
Flashed 4.1.6 with twrp at same time without reboot flashed bootpatch and rebooted to system and still the dm verity showung
Did i collapsed the procedure?:silly:

sparky vicky said:
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
Click to expand...
Click to collapse
Mate do read the second post in the OP...
For getting rid of the DM-Verity message..
The first OP post is only for those who have no DM Verity warning on their phone..
If you already have DM Verity warning on your phone you have to follow the second post..it is clearly mentioned in the OP.. AND WRITTEN IN BOLD LETTERS..
Once you get rid of the DM Verity warning from next time onwards you have to follow only the instructions in the first OP post..

Magisk 16.4 (Error : 1) [TREBLE]

Hello guys i want to use Crdroid official 4.2 Treble build on my Redmi 3S with Magisk - 16.4 [treble flashable zip. But when flash Magisk 16.4, I was found Error 1 in my Twrp Recovery.
Using Rom : Crdroid official 4.2
Recovery : TWRP 3.2.1.0 (Treble mod), allso I'll trid on Redwolf (treble).
How to fix that issue?? Because I want to root my phone.

Please help me guys. I want to flash treble rom with Magisk

MAH35H said:
Please help me guys. I want to flash treble rom with Magisk
Click to expand...
Click to collapse
oh ,this magisk is not support treble,because,it doesn't mount vendor.so you have to use modify mod magisk。you can serch in xda for more help

MAH35H said:
Hello guys i want to use Crdroid official 4.2 Treble build on my Redmi 3S with Magisk - 16.4 [treble flashable zip. But when flash Magisk 16.4, I was found Error 1 in my Twrp Recovery.
Using Rom : Crdroid official 4.2
Recovery : TWRP 3.2.1.0 (Treble mod), allso I'll trid on Redwolf (treble).
How to fix that issue?? Because I want to root my phone.
Click to expand...
Click to collapse
reflash u boot.img from u rom
then instal again magisk treble
if error. try to download again
maybe ur package zip is eror

Can anybody paste a downloadable link for magisk treble. I am facing the same problem. Please help!!!!

That same problem. I'm trying to flash clean boot.img over and over and no solution

Magisk 16 treble beta
Skys源儿 said:
oh ,this magisk is not support treble,because,it doesn't mount vendor.so you have to use modify mod magisk。you can serch in xda for more help
Click to expand...
Click to collapse
Magisk 16 treble beta is working fine and flashable ..

Install latest TWRP r2.

Hello, I got error: 255 when I tried to flash Magisk 16.4 with TWRP r2 for treble
any ideas ?

aryancol31 said:
Can anybody paste a downloadable link for magisk treble. I am facing the same problem. Please help!!!!
Click to expand...
Click to collapse
http://downloadmirror.co/Wso/Magisk-v16.4.zip

The error occurs because twrp is unable to mount vendor
Use twrp treble mod and
Magisk cust.zip
it worked for me

pavanp1 said:
The error occurs because twrp is unable to mount vendor
Use twrp treble mod and
Magisk cust.zip
it worked for me
Click to expand...
Click to collapse
how i can download twrp treble mod and Magisk cust.zip,my drive is redmi 3s
Sent from my land using XDA Labs

I haven't tested this project, but it seems to work with our treble ROMs.
https://gist.github.com/Jerry981028/b6a7fdfcf1823325c2f94f83677fa554

I am too facing issue with magisk. The phone does not boot after I flash it through twrp (treble supported recovery) and when i many tries to boot it gets soft bricked.

It has been reported many times...
Treble recovery is mandatory, if you have not already install it, pick the R2 version here :
https://sourceforge.net/projects/team-reloaded/files/land/TWRP/Treble/
You can find a working magisk 16.4 here :
https://forum.xda-developers.com/showpost.php?p=77062410&postcount=1322

Magisk issue is due to corrupt file.
Magisk issue is due to corrupt file. First be sure to have a treble compatible recovery and to enable treble if needed.
you can find a working magisk here : https://forum.xda-developers.com/sho...postcount=1322

Flash twrp treble recoveryagain, you must have flashed wrong recovery....
Same happened with me...
Flashed twrp again then flash magisk

How to flash a Treble img on redmi 4 prime

I am used to normal flashing. But there is no good official rom for markw. Mokee lags and unstable,I didn't like dotOS ui, havoc was great but unstable with many problems like bettary draining, heating even in sleeping etc. I want to install RR or aosp extended treble img.
Did anyone in this forum flash treble img?? Can anyone help me?? I didn't find anyone who flashed a treble img on an unofficially treble supported device like markw.
Thanks in advance.

Use treble recovery to flash treble roms. GSI's can be flashed with it, you'll additionally need vendor to flash after flashing GSI.

Process
kibria.mgk said:
Use treble recovery to flash treble roms. GSI's can be flashed with it, you'll additionally need vendor to flash after flashing GSI.
Click to expand...
Click to collapse
Will this process work?
1) Flash a treble enabled rom(havoc).
2) Factory data reset with twrp.
3)Install treble gsi.
Thanks for reply.

Fateful n5 user said:
Will this process work?
1) Flash a treble enabled rom(havoc).
2) Factory data reset with twrp.
3)Install treble gsi.
Thanks for reply.
Click to expand...
Click to collapse
I think the following is better:
1. Flash gsi (with all fundamental wipes, ofc.)
2. Flash vendor
3. Flash post gsi's if required (ported sgsi's require this normally)
4. Flash gapps and magisk (both optional)
5. Boot system

Flashed Recovery and OS from OP5T on OP5

Hi,
i've made a big mistake, i have flashed TWRP and LineageOS/Stock-Roms from Oneplus 5T on my Oneplus 5. There was only a few things that don't work. Now when i boot into Recovery i can't install LineageOS for the OnePlus 5 because of Error 7. Is there a special TWRP for Oneplus 5T and Oneplus 5 or is it the same for both devices? At the moment there is no OS installed. I have flashed this Recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 and tried to flash LineageOS for OnePlus 5 but it failed with
zip treble compatibility error!
invalid zip file format
Click to expand...
Click to collapse
I have the same error when i try LineageOS and LineageOS microG. What is wrong here? Is there any way to start again with a new fresh stock rom for the oneplus 5?

gene2 said:
Hi,
i've made a big mistake, i have flashed TWRP and LineageOS/Stock-Roms from Oneplus 5T on my Oneplus 5. There was only a few things that don't work. Now when i boot into Recovery i can't install LineageOS for the OnePlus 5 because of Error 7. Is there a special TWRP for Oneplus 5T and Oneplus 5 or is it the same for both devices? At the moment there is no OS installed. I have flashed this Recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 and tried to flash LineageOS for OnePlus 5 but it failed with
I have the same error when i try LineageOS and LineageOS microG. What is wrong here? Is there any way to start again with a new fresh stock rom for the oneplus 5?
Click to expand...
Click to collapse
Yes, there are 2 ways.
1. Flash OOS from bootloader, or via adb sideload. Else use MSM Tool to flash OOS. Then lock bootloader, and unlock again to flash the TWRP. After that all back to normal.
2. Lock the bootloader and unlock, then flash CodeworkX Force Encrypt TWRP from the same link. Format data and try.
#1 will make it all clean with no need of vendor again.
#2 will have the need to flash vendor image again.

is it stable? did u have navigation gestures hahaha just wondering
what didnt work?

Most works. Microphone didn't work and sometimes bluetooth.

Is Magisk 23.0 compatible with latest stable oxygen os based on adroid 12...?

hello geniuses..!!
i tried the basic method to root latest oxygen os IN2021_11.C.21 with magisk 23 zip through fastboot. i follow all the steps like extract boot img than patch with magisk 23 loader and after that patched boot image flashing with fastboot. but it doesn't work. is there compatibility issue with magisk 23..?? please solve this. and also is there any way to install twrp..?

Pretty sure those old Magisk versions don't support OOS12, I know they don't support A12 either - just use the latest one, 25.1.

Ok brother. I understand. And is custom recovery available for Android 12 oos12..?

aakashishere said:
hello geniuses..!!
i tried the basic method to root latest oxygen os IN2021_11.C.21 with magisk 23 zip through fastboot. i follow all the steps like extract boot img than patch with magisk 23 loader and after that patched boot image flashing with fastboot. but it doesn't work. is there compatibility issue with magisk 23..?? please solve this. and also is there any way to install twrp..?
Click to expand...
Click to collapse
I use magisk 25.1 on the same rom without any issues

Any custom recovery available for that rom..?

aakashishere said:
Any custom recovery available for that rom..?
Click to expand...
Click to collapse
Not yet, just keep an eye on the TWRP thread