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.

Nexus 6P, TWRP, Stock image, NetHunter... what could possibly go wrong?

I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!

[email protected] said:
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
Click to expand...
Click to collapse
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk

I formatted, installed factory image, installed TWRP, flashed Magisk, confirmed root, flashed NetHunter ZIP, same result
Droidriven said:
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse

So if anyone else is facing the same issuing of wanting to install this old(ish) software onto this old(ish) hardware, and got stuck in the same place as me, here are the three steps that I had to take to succeed that were not in official documentation:
1)When flashing the factory Android image, make sure that you are using the newest version that is supported by NetHunter. At time of writing, this is not the same as the newest version of Android.
2)Remove the -w option from the installation script
3)Be sure to install a compatible kernel from builds.nethunter.com
Thanks again to @Droidriven for the tip on using Magisk

Help access internal storage from fastboot

So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.

I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.

To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.

Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.

I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"

a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.

cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.

DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com

DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking

DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.

urgent: oneplus 7 pro TWRP bootloop

I'm very new to everything related to rooting and I think I screwed up, I'm not even sure if this is what a bootloop is.
My device won't boot back into android, I've tried to look for a solution but I don't understand any of the terms those people use.
I followed a tutorial to help me root my phone which I think might have worked but now I can't do anything.
I installed the latest twrp .zip on my phone and elementalX (I think I downloaded it for android 10 instead of 11), I tried a couple of commands in the terminal suggested by other people but none of them did anything.
I really want my phone back, even if that means that it won't be rooted, I made a backup of my data so all that matters to me is that I can use my phone again.
If you know anything that can help me, please try to explain it in a way I might understand as I don't even really know what flashing means.

wattage0 said:
I'm very new to everything related to rooting and I think I screwed up, I'm not even sure if this is what a bootloop is.
My device won't boot back into android, I've tried to look for a solution but I don't understand any of the terms those people use.
I followed a tutorial to help me root my phone which I think might have worked but now I can't do anything.
I installed the latest twrp .zip on my phone and elementalX (I think I downloaded it for android 10 instead of 11), I tried a couple of commands in the terminal suggested by other people but none of them did anything.
I really want my phone back, even if that means that it won't be rooted, I made a backup of my data so all that matters to me is that I can use my phone again.
If you know anything that can help me, please try to explain it in a way I might understand as I don't even really know what flashing means.
Click to expand...
Click to collapse
Can you boot into fastboot then toggle the volume key to recovery , does it go to twrp or something else?

hammered58 said:
Can you boot into fastboot then toggle the volume key to recovery , does it go to twrp or something else?
Click to expand...
Click to collapse
that goes back to twrp

wattage0 said:
that goes back to twrp
Click to expand...
Click to collapse
Good then try the below steps
This sequence has worked for me every time
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage. Or OTG drive,, Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS in both slots

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