Database Info

Update with root/unlock

I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?

Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.

Anyone know how to root if I'm already on 9.5.6?

hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.

I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk

hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.

larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.

The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk

larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions

OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you

With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk

skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.

Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi

Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.

Issue with Magisk/TWRP

Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Not sure what to do at this point. Any ideas?
Thanks!

mobbdeep said:
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Edit sorry I updated magisk and now I don't have twrp
Not sure what to do at this point. Any ideas?
Thanks!
Click to expand...
Click to collapse
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry

SirFronts said:
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
Click to expand...
Click to collapse
I guess I will just backup my phone completely, factory reset it, and re-root the device again.

mobbdeep said:
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
Click to expand...
Click to collapse
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4

SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
I'll give that a try tonight.

I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?

SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
alex.coffen said:
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
Click to expand...
Click to collapse
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Boot TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.

mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
I tried something and soft bricked my phone...
Anyway, lucky that I did a backup with twrp for boot when magisk was 19.3, then i can get into twrp by "fastboot boot" the twrp boot img temporarily and restored the boot.
Now everything works fine.
Ps: fastboot boot is not 100% safe...

mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
My TWRP is gone too. But I can temporarily get in TWRP using my computer.
How do I flash OOS firmware? I am currently on PIE 9.5.13 intl. version. Should I download the full zip OOS and then flash it via TWRP ?
Then flash TWRP ?
And then flash Magisk 19.4 ?
Another question: DO you think uninstalling magisk via magisk uninstaller and installing the canary version of it would allow TWRP to stick ? There's threads that mention that the canary version doesn't erase TWRP.

mobbdeep said:
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.

redpoint73 said:
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
Click to expand...
Click to collapse
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh?

Dogstarlooma said:
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh
Click to expand...
Click to collapse
I just read that Magisk 20 has a bug, that prevents TWRP from "sticking", and to use 20.1 (or in your case, looks like 19.4).

I accidentally bricked my phone

Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?

Did you try with Miflash?

try with MiFlash. Flash stock rom in fastboot mode

Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now

Thelm76 said:
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Click to expand...
Click to collapse
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules

dhaern said:
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
Click to expand...
Click to collapse
Well that the thing I tried when I accidentally replaced my boot partition... And my phone was only booting on twrp or fastboot... also the weird thing I found is that /data/adb didn't exist
But many thanks to you all it works now.
I'll maybe try to make a guide on how to install Magisk on the Xiaomi EU weekly rom, as android 11 is only supported by the canary build. (if I manage to find a way to properly remove defective modules in TWRP :fingers-crossed

Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data

Tecardo said:
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Click to expand...
Click to collapse
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module

If you want everything to work you need to format data!!

Thats the point why using android 11 roms is hard, twrp cant decrypt it (until you flash rom with a10 and then a11 because partition is encrypted in a10 style)

Thelm76 said:
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
Click to expand...
Click to collapse
That's easy to fix, you installed Android 11 or? Don't use pin, use gesture. Twrp can't decrypt android 11 pin right now

Thelm76 said:
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Click to expand...
Click to collapse
NO flash only fastboot boot twrp.img

Cannot fastboot into TWRP

Hey,
I updated already rooted phone with Oxygen updater (forgot that he will remove TWRP in auto install) and now can't get it to fastboot into TWRP with ADB. I tried several .img files but non worked. Every time it goes to Crash dump.
Did someone successfully fastbooted into one? Or the only solution is to go back and do it manually from OOS 10?
Thank you!

99mike199 said:
Hey,
I updated already rooted phone with Oxygen updater (forgot that he will remove TWRP in auto install) and now can't get it to fastboot into TWRP with ADB. I tried several .img files but non worked. Every time it goes to Crash dump.
Did someone successfully fastbooted into one? Or the only solution is to go back and do it manually from OOS 10?
Thank you!
Click to expand...
Click to collapse
If you are on OOS 11 then use the attached file and try the below steps.
1. Reboot to Fastboot mode.
2. Use command : Fastboot boot boot.img (use attached TWRP alone)
3. Once rebooted to recovery mode Install recovery by Advanced -> Install Current TWRP . This should install the image automatically to your device.
Reboot your phone to system mode and then reboot it back to recovery mode later.
Hope the above helps.

TWRP is wonky on A11, for now.
If I'm not mistaken the TWRP provided by other poster will have issues with making and restoring backups.
If you are still rooted and looking for a backup/restore method, you might as well leave TWRP alone for now and simply maintain root through the Magisk app. If root was lost, then you can use the version provided here: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4306803/ which is likely what other user posted, to restore root and then wait for Google to release the full deets on A11 to hobby developers who can then make a new TWRP.

This worked for me to get back TWRP and root after upgrading. Thank you very much!

TWRP can't decrypt + Fastboot loop

Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work

I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/

I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯​
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp

MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.

No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop

RIP
Started ranting instead

TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY

Pics

RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while

Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.

the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325

****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install

Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help

MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp