Develop Bugs

Updated TWRP, now system only boots back into TWRP

I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks

I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.

facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse

TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse

My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.

alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12

We're can I download v8?
Sent from my Pixel XL using Tapatalk

The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347

So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.

cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.

Slowclap

Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse

Magisk Issues on Fresh System Image Install (Feb. 2019)

I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.

clambert11 said:
I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.
Click to expand...
Click to collapse
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!

sb1893 said:
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!
Click to expand...
Click to collapse
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.

clambert11 said:
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.
Click to expand...
Click to collapse
If your platform-tools are r28.0.1
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- install ElementalX kernel
- tap Add more zips
- select Magisk-18.1.zip
- swipe slider to install
- reboot

Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!

clambert11 said:
Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!
Click to expand...
Click to collapse

I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?

Ivanstein said:
I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?
Click to expand...
Click to collapse
Forget side loading!
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- tap install select Twrp-3.2.3-1.zip
- swipe slider to install
- reboot recovery
- tap install select Magisk-18.1.zip
- swipe slider to install
- reboot

Rooting issues

I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.

What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?

ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.

Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.

ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?

Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL

Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.

No worries, I forgot to mention that I restored a back up

Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.

ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.

Damn Root......

No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,

Don't bother with twrp
Just use magisk.
Download the factory pixel image on your PC , unzip the boot.img file and transfer to your phone.
Open magisk manager and install magisk by patching the boot.img file U just transferred.
Copy that new patched boot img back to your PC.
Use ADB to ADB reboot bootloader
Type: fastboot flash boot patched_boot.img
That's it

mediaman123 said:
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Click to expand...
Click to collapse
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.

Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.0-0.img; in twrp, flashed 3.3.0-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.

Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx

1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
My safety net passes in magisk, but I don't use any apps that I can verify that with.

jlokos said:
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.3-0.img; in twrp, flashed 3.3.3-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Click to expand...
Click to collapse
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks

docluv01 said:
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
Click to expand...
Click to collapse
Sorry; an extra 3; I'm using TWRP 3.3.0.0.
---------- Post added at 07:58 AM ---------- Previous post was at 07:37 AM ----------
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
I DL magisk hide module and use it for two apps, one for comcast business and the other which regulates my home thermostat.

Wow, thanks guys.....you have all laid out pretty well your processes which I will go through later on....
It's strange, as everything is installed and magisk believes it working it just doesn't pass thee root check..
I'll get back to you with my progress...??

OnePlus 7T India, 11.0.9.1, booting only to recovery / fastboot after incorrect Magisk update

I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!

Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.

jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions

HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??

jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com

HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1

jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com

HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.

jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse

Only data partition is shared. All else have both A and B parts