yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 & 7 Pro Cross Device Development] Cobmaster:
@H4X0R46 , I already had this problem... The only solution I found by myself is:

1) Backup all your data from the internal memory (i.e. using FTP or whatever method you like the most)

2) Download latest MsmDownloadTool for your device, latest driver for Qualcomm EDL and the latest OTA from the OnePlus site ( we will need it later)

3) Power off your device before connecting to the PC. Hold VOL+ and VOL- and connect it to your PC, you should hear the sound of a connected device and the phone's screen is black.

4) Check if the device is properly connected in device manager. (If it doesn't work select manually the driver)

5) Start MsmDownloadTool V4.0.exe and if it asks the login choose from User Type "Others"

6) Click on the enum button a bunch of times and if your PC is saying "Connected" you can start the downgrade... Be wary that this procedure wipes all the data inside and locks again the bootloader!!

7) When it reboots it's back to OOS 11. Skip all configuration steps (it doesn't matter, we have to unlock the bootloader)

8) Proceed to unlock the bootloader and installing TWRP as the OP said

9) Transfer the OTA from your PC to TWRP and install it but make sure to tick the "Keep TWRP after rom install". Go back to the main menu and select reboot select the correct slot in which you just installed the OTA and select system.

10) When the phone boots up, it will be on OOS12 but with TWRP.

11) Reboot in recovery once more and flash again the OTA with the same option as before. (It's not required, but if you want a bootable phone if you mess around with the system, is a good thing to have)

If you want you can flash magisk 25.2 as normally in recovery too...
[OnePlus 7 & 7 Pro Cross Device Development] torben5247:
Will twrp-3.7.0_11-0 work with lineageos 20?

Anyone tried that?
[OnePlus 7 & 7 Pro Cross Device Development] AFAFontes:
twrp-3.7.0_12-0-guacamole.img doesn't work for me.

I go to fastboot mode, type fastboot boot twrp-3.7.0_12-0-guacamole.img on cmd and it gets stuck with OP icon and "Fastboot mode" sign.

build: GM1913_11_H.30

Note: tried 3.6.2 version still not working

Anyone has a working version of twrp or can upload patched boot.img for OOS GM1913_11_H.30 build (op7pro eu)?

UPDATE: I just patched the boot.img but when I flash I get into a bootloop, probably due to a magisk module, is there any way to uninstall a specific module or get a list of all installed modules and then uninstall all the modules without root and without a working twrp?

UPDATE2: SOLVED - so after getting the patched boot.img I just flashed using fastboot and immediately rebooted into Safe Mode using hardware keys, this way the system booted with all modules disabled as Magisk does it once it detects the phone is booting into Safe Mode so no more bootloop with patched img, after that I rebooted again back to normal mode and as the module disable state persists, the phone's rooted and I'm able to manage modules through the manager (remove the module that previously caused the bootloop and enable the others).
[OnePlus 7 & 7 Pro Cross Device Development] Aussiewaterdragon:
Yep had the same problem, had to downgrade to 11, then unlock and flashed TWRP.

Then updated to 12, kept magisk but had to flash patched image with fastbboot, Magisk all good but cant get TWRP installed. Like you waiting for a viable installable twrp for 12
[OnePlus 7 & 7 Pro Cross Device Development] AFAFontes:
Well I honestly don't need twrp anymore. Would be cool and it would save me some time but I can definitely survive without it.

Anyways it's probably my last Oneplu$ device since their OS is not great anymore and they're not community friendly anymore.
[OnePlus 7 & 7 Pro Cross Device Development] Aussiewaterdragon:
UPDATE ON ANDROID 12 and TWRP

yep got it going, I did this, installed the magisk APP,

downloaded the OS version for android 12 extracted the boot image using PAYLOAD DUMPER on PC, transferred the boot image to the phone, used it in MAGISK to create a magisk boot record, sent it back to PC, used fastboot to flash new boot image.

C:\Users\User>fastboot devices

2de5e2fc fastboot

C:\Users\User>fastboot boot magisk_patched-25200_thTUt

.img

downloading 'boot. image...

OKAY [ 2.561s]

booting...

OKAY [ 0.090s]

finished. total time: 2.651s

Then flashed Magisk again, rebooted and finished the magisk install.

Then used Magisk to Flash twrp-installer-3.7.0_12-0-guacamole.zip reflashed Magisk, rebooted and finished Magisk install

Don't forget when running TWRP for the first time to run the reinstall script
[OnePlus 7 & 7 Pro Cross Device Development] kdsgn3:
Please, someone spell it out for me. I have a OnePlus 7 NOT PRO (guacamoleb) and this twrp img seems like it is only for OnePlus 7 Pro (guacamole). Is it compatible with either??

All the links to a guacamoleb version seem to be broken.
[OnePlus 7 & 7 Pro Cross Device Development] Honkette1738:
They're very close hardware wise, the only differences being cameras, display and frame, and battery. I think it works.
[OnePlus 7 & 7 Pro Cross Device Development] nomobytes:
Your method worked for me. Specifically-

fastboot boot twrp-3.7.0_12-0-guacamole.img left me in fastboot mode. But installing twrp-installer-3.7.0_12-0-guacamole.zip from within magisk worked, though I had to run a magisk direct install immediately afterwards as the twrp installer will unroot your device.

That left me with a stock GM1917_11_H.37 (via OTA) rooted with working twrp device.
[OnePlus 7 & 7 Pro Cross Device Development] indiman:
Could you explain more details pls? Thanks.
[OnePlus 7 & 7 Pro Cross Device Development] Sachinkjohn:
Hi, did anyone managed to get recovery and root working with latest oos Android 12 eu?
[OnePlus 7 & 7 Pro Cross Device Development] Zobat:
where you rooted before you installed it?
[OnePlus 7 & 7 Pro Cross Device Development] Sachinkjohn:
Currently with oos 11 and magisk 25.2

Do we have a safe method to upgrade to oos 12 with root and recovery working. Thanks in advance
[OnePlus 7 & 7 Pro Cross Device Development] Zobat:
that's exactly my question also. 😂
[OnePlus 7 & 7 Pro Cross Device Development] warezxts:
i just did...

stay at TWRP-3.6.2-guacamole-Nebrassy-02-10-22.img and twrp-installer-3.6.2_11-0-guacamole.zip

and follow the usual upgrade method. Make sure you have backup.
[OnePlus 7 & 7 Pro Cross Device Development] AdUser:
Do you can explain pls?
[OnePlus 7 & 7 Pro Cross Device Development] Zobat:
i dont think it can be explained in a clearer way.
[OnePlus 7 & 7 Pro Cross Device Development] vivaxp5:
Hey! I am on Android 12 (Oxygen OS), Build#: GM1911_11_H.38. Could you please explain the procedure in a bit more detail? I patched the boot image acquired from the payload dumper in Magisk. What to do thereafter?

I tried booting that image, but the device just shows Fastboot logo, and if I try to flash that image, my device stops getting recognised as an MTP or adb.Any help would be greatly appreciated. Please help people!!
[OnePlus 7 & 7 Pro Cross Device Development] Explorare:
I flashed the ROM between stock Hydrogen OS and LOS 20 back and forth testing out the noise issue and had a frustrating experience with restoring the system. I backed up all partitions of LOS 20 showed up in the list before switching to a previous backup of HOS10 I made last week. I formatted the data using TWRP before restoring the old backup. I switched to the other AB partition after the restore succeed and do it again. But the stock system stuck on bootloader. I then flashed the device using 9008 back to stock HOS 9 and upgrade it to HOS 10. And then restore the backup, and then it worked as intended.

I then formatted the device again and restore the backup for LOS 20 I made just before, and it met a boot loop. I tried a clean install and then restore all partition, but it still results in a boot loop.

What's the correct procedure to back up and restore the ROM in this situation?

Thanks.
[OnePlus 7 & 7 Pro Cross Device Development] Aussiewaterdragon:
I had some fun but you can try this alternative method to keep Magisk?TWRP. it worked for me.

ONE PLUS 7 SYSTEM UPDATE and RETAIN MAGISK

UNINSTALL ALL MAGISK MODULES

IN MAGISK ENSURE “TWRP A/B RETENTION SCRIPT” IS INSTALLED AND ON (Reinstall after last update)

DOWNLOAD UPDATE (From settings/update or use Oxygen Updater) MOVE UPDATE TO ROOT FOLDER

INSTAL UPDATE USING settings/systemsettings/system update/manual update

DO NOT REBOOT

IN MAGISK REINSTALL MAGISK USING “INSTALL TO INACTIVE SLOT” OPTIION -----NOW REBOOT

IF TWRP MISSING THEN IN MAGISK INSTALL TWRP……INSTALLER.ZIP then reinstall MAGISK using direct install

p.s. if you have problems passing Safetynet try trhs

CTS profile match failed

Finally success

of course magisk with deny list setup and the rest

1. remove universal safety fix

2. reboot

3. install displax fork mod 3.0 here

https://github.com/Displax/safetyne....3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip

4. reboot

5. clear cache from google wallet
[OnePlus 7 & 7 Pro Cross Device Development] Nightmare[ITA]:
I'm on OOS11 (7 Pro) with Nebrassy TWRP and Magisk 26.1. Is this method still valid to update?

Deactivate all Magisk Modules

Reboot

Download Nebrassy TWRP (unofficial 12 build for v1) and copy to internal storage

Download Latest Magisk, rename it from .apk to .zip and copy to internal storage

Install OTA update regularly from system setting (local update) but DON'T REBOOT.

Open Magisk and first install to direct install DON'T REBOOT.

Open Magisk again and then install to inactive slot NOW REBOOT.

Boot into fastboot

Boot Nebrassy TWRP

In TWRP go to Advanced > Flash Current TWRP.

Flash latest Magisk.zip that was placed in the internal storage

Reboot and install Magisk again through the app
[OnePlus 7 & 7 Pro Cross Device Development] steev087:
So honestly what's the point in rooting if the phone I've got is only read and not write compatible.
[OnePlus 7 & 7 Pro Cross Device Development] Zobat:
That's a reason to root.
[OnePlus 7 & 7 Pro Cross Device Development] steev087:
So that it can become write compatible?
[OnePlus 7 & 7 Pro Cross Device Development] steev087:
I have the 1910 and it seas that its not write supported. What can I do with it then ?
[OnePlus 7 & 7 Pro Cross Device Development] Zobat:
you need root for that indeed.
[OnePlus 7 & 7 Pro Cross Device Development] mikel10k:
Any news on when they release it for A13?
[OnePlus 7 & 7 Pro Cross Device Development] Ayoub hd dx:
Try this one wip data Unofficially twrp
[OnePlus 7 & 7 Pro Cross Device Development] RelaxDA:
I keep getting failed to decrypt with latest twrp 3.7.0_12-0 version, is there a way to fix this? and therefore I can't flash magisk

EDIT: I'm on OxygenOS 11.0.9.1.GM21BA

EDIT2: This version is also taking like 20 seconds to load and get to decryption screen, the version I used before (can't remember it's been a year) used to not be able to flash permanently but only boot but it was able to flash magisk, decrypt and loaded instantly.
[OnePlus 7 & 7 Pro Cross Device Development] Littlemether:
I modded TWRP70 Guacv1 with setting NOCRYPT/noverity/magisked26.4/sepolicy-inject-overlay.d_selinuxTamed, retamed every boot, /sbin preinstalled terminal apps include...

Magisk_files, busybox, toybox, setools, magic-flash (flash .zip -v), "backup anypartion" to /sdcard/backup/" also it's made for dual-OS A/B/C configs A11-12, Warning this will mod your /selinux/sepolicy or policy to a Tamed state 1st boot. Comes setup fore stock partitions and dualboot. I held off on a few things so you won't get Invalid system error/brick.

I have a modded OxgenOS12 OTA comming out on telegram, (install after stock 12v41 OTA dirty/clean. fully dualbootable and never loos ypour data due to FBE/encrypt. https://t.me/OP7PRO_OXYGENOSmoddedROM/1

and how bout that beer https://paypal.me/crazyinsanejames?country.x=US&locale.x=en_US ty

theres my main quick decrypt/nocrypt and TWRPS- the .IMG IS GOT OXYGENOS12 kernel be carfull if on A11 still
[OnePlus 7 & 7 Pro Cross Device Development] frituurvet:
I'm stuck. On stock A11 I unlocked bootloader and upgraded to stock A12. Now TWRP won't run (oneplus logo and nothing happens).

Can this be fixed without using Magisk? So far, the only thing I've found on here is to downgrade to A11 with some exe program and install Magisk, then upgrade.

The only thing I need on this device is a custom rom, no gapps, no magisk, etc.

Pls halp kthx ^^
[OnePlus 7 & 7 Pro Cross Device Development] Littlemether:
Okay 1 sorry Ill try helping though. I sent my OxygenOS12-TwRPed.img and made a fastboot flash pack to help just unzip it run the exe and it'll expand and rewrite everything I figure may be wrong. ohh and I upgraded my TWRP alot it'll so heres my better coppy. I been busy

https://t.me/crazyinsanejames https://t.me/OP7PRO_OXYGENOSmoddedROM/1
[OnePlus 7 & 7 Pro Cross Device Development] 1nker:
Hi, folks.

Is it possible to decrypt /data in Android 14 by TWRP official rec or other methods?

I need to decrypt /data in order to remove the gapps file to solve the bootloop issue.

Thanks.
[OnePlus 7 & 7 Pro Cross Device Development] cr1cr1:
Not sure the owner of the thread would appreciate us talking this much about other topics, albeit related and enabled by his work, so also I do apologize.

If I understand ur question correctly, I am using the default Beta channel, not a custom one. No idea what is behind. My Magisk is the official one, with defaults.

Yes, I did rename the apk to zip and flashed it using this TWRP release.
[OnePlus 7 & 7 Pro Cross Device Development] Nebrassy:
it is failing on /data/opdiagnose, try deleting that directory and backing up again

magisk.apk can be flashed as is in TWRP, no need to rename

parallel apps, or any such feature that does not use a separate password, if its password is the same as the main, it can not be decrypted, and thus can not be backed up
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
Yes, this is how the action is performed without errors, but it is unlikely that such a backup will be able to restore performance in case of any failure.

Right?
[OnePlus 7 & 7 Pro Cross Device Development] MikeBl1:
I have 3 different app cloners in use under OOS10. Error 255 does not occur in the TWRP for A10. OOS10 is encrypted. So it should theoretically work under oos11, encrypted and the "new" twrp at some point
[OnePlus 7 & 7 Pro Cross Device Development] Fredator:
Hello

if this is a stupid question please forgive me ^^

I'm still on Android 10 for now

i used to update my system and keep root (and data) with this method:

adb reboot bootloader

fastboot boot TWRP xxx .img (only boot, not flash, i don't need twrp installed)

=> Phone then boots in twrp, uncrypt it with pin

and then in twrp:

Flash Rom zip

Flash magisk zip

will it work same way with this new TWRP and Android 11 rom?

And just to be sure: Magisk is now an apk, only rename to zip and flash from twrp is ok?

thanks
[OnePlus 7 & 7 Pro Cross Device Development] Nebrassy:
Yes, and no need to rename magisk
[OnePlus 7 & 7 Pro Cross Device Development] Fredator:
Thanks mister

What do you mean "no need to rename magisk"?

i can flash an apk from twrp?
[OnePlus 7 & 7 Pro Cross Device Development] Nebrassy:
Yes, only magisk apk
[OnePlus 7 & 7 Pro Cross Device Development] HippoMan:
Agreed. I have been using TWRP for nandroid backups of system, boot, and vendor, in addition to data. Doing this kind of backup, I can try an entire new ROM, and then later restore the old ROM in the exact state that my device was in at the moment of backup. Also, even without a ROM installation, restoring this kind of TWRP-initiated nandroid backup is very helpful if I have been messing with my device and have accidentally gotten it into an unusable state. I can easily restore it to a past snapshot.

Backups of data only do not permit any of this.

I'm staying on Android 10, and one of the reasons is because I can use TWRP in this way. Once this new TWRP's backup/restore procedures are working, I would be more willing to possibly try an upgrade to A11.
[OnePlus 7 & 7 Pro Cross Device Development] Nebrassy:
uploaded new build, adb sideload now works
[OnePlus 7 & 7 Pro Cross Device Development] WesTD:
How will i keep twrp after flashing rom? is "flash current TWRP" enough?
[OnePlus 7 & 7 Pro Cross Device Development] xtzy:
Something is wrong with the TWRP, I can't even say how this could be related to the computer.

If the phone is connected to the computer via USB, just for charging and go into the TWRP, then a continuously sound is heard in the speakers: tum-tum-tum-tum ... And this is both on version 2 and on version 3.
[OnePlus 7 & 7 Pro Cross Device Development] lollyjay:
yes
[OnePlus 7 & 7 Pro Cross Device Development] ‬1‬:
Alpha backup pro also does the same job.
[OnePlus 7 & 7 Pro Cross Device Development] ‬1‬:
I could successfully back the phone up but haven't tried to restore it yet.
[OnePlus 7 & 7 Pro Cross Device Development] Ullas_Aithal:
Maybe it's just me, but coming from OOS10, this version didn't boot to twrp after running "fastboot boot twrp.img". It got stuck at "Fastboot Mode".

Flashing older version "TWRP-3.5.1-guacamole-Nebrassy-2.img" worked for me.
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
With the .2 or .3 image version and with ticking all boxes for backup?
[OnePlus 7 & 7 Pro Cross Device Development] ‬1‬:
Second and yes i ticked the all boxes. Before this, I couldn't install oos 11. TWRP gave an error message like yours. It was Error 1 though. So I extracted the OOS boot image and installed it with fastboot and I could install the rom after. You might give it a try not sure if it would help with the backup.
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
I deleted this file and tried again but still the 255 error on backup attempt...
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
I had no issue installing the TWRP image through adb to begin with after I upgraded from OOS 10 to OOS11...

No errors there.

Only error appears to be trying to backup and getting the 255 error notice for me...
[OnePlus 7 & 7 Pro Cross Device Development] Fredator:
i flashed the android 11 rom and then magisk

it booted the first time, but it was not not rooted

So i flashed magisk again

it asked me slot to reboot, i answered randomly as i didn't know

now I have the oneplus logo spinning since 15 minutes

restarted several times, all the same

No idea what to do now
[OnePlus 7 & 7 Pro Cross Device Development] Fredator:
Sorry for the double post

Finally found out, i post it if it can help someone in the same situation

Force phone to reboot in fastboot mode

from adb folder, check the slot with

Fastboot getvar current-slot

then set to the other slot with this command:

fastboot --set-active=a

(or b if you were to boot in slot a)

all good, restared, rooted, data is here, i must confess i was scared to have lost everything and had to spend days to reset all as it was 😅

thanks guys
[OnePlus 7 & 7 Pro Cross Device Development] pawlakbest:
Where can I find USB drivers ? They used to install automatically when I plugged OP7Pro to PC but seems that this is gone on A11. I can't boot twrp.img because devices is not recognized in device manager when I start fastboot.

*Edit: Tried drivers form TOOL_ALL_IN_ONE_2.0.1.4 and Google with no effect.
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
You did input fastboot devices command first in adb I'm assuming...

Google is your friend...

Support - OnePlus (United States)

support.oneplus.com
[OnePlus 7 & 7 Pro Cross Device Development] shuini:
hi

File management does not display system/reserve。
[OnePlus 7 & 7 Pro Cross Device Development] pawlakbest:
Thx for that. But my device is still not recognized (adb devices) in bootloader mode, only on OOS. I never had this problem before and I don't know what to do or how to check what I'm missing. Can you/someone help ? I'm trying to get TWRP for A11 or to reflash back to A10.
[OnePlus 7 & 7 Pro Cross Device Development] midgo12:
Sometimes the USB cable or USB port is at fault.

Try a different USB cable or change to other USB ports and try to run fastboot devices command in bootloader mode again...
[OnePlus 7 & 7 Pro Cross Device Development] dejjem:
Maybe did one? https://dl.google.com/android/repository/usb_driver_r13-windows.zip I seem to remember having that issue months back... from memory, I think you need to go into My Computer/Devices, find the USB with the weird malfunctioning yellow/red symbol and say scan local folder and give it the path u extracted the zip file in...
[OnePlus 7 & 7 Pro Cross Device Development] schumissimo:
Good morning all,

I am using TWRP without encryption on Android 11, if I install this version will I recover the encryption and be able to update OOS as before?

Thank you for your answers.

Greetings.
[OnePlus 7 & 7 Pro Cross Device Development] rvonder:
Hi -

I had the same issue. The official drivers from OnePlus (or almost any other manufacturer) can be found here:

https://www.teamandroid.com/download-android-usb-drivers/

The problem is that the drivers will seem to install, but actually don't. This is due to Windows 10's "driver signature enforcement" security feature: Unless drivers have been submitted to MS for signing, they can't be installed. It appears that OnePlus didn't do so, because after disabling this feature the drivers installed fine, and both adb and fastboot then recognized my phone.

Here's one of many sites that describe three ways to do this - I used the "test signing" option:

https://www.tenforums.com/tutorials...river-signature-enforcement-windows-10-a.html

Hope this helps!
[OnePlus 7 & 7 Pro Cross Device Development] lollyjay:
Has anyone used this TWRP to install OOS 11 or OB5?
[OnePlus 7 & 7 Pro Cross Device Development] Fredator:
Yup. Just did it yesterday. Without installing twrp, only booting on it
[OnePlus 7 & 7 Pro Cross Device Development] Lossyx:
Without decryption, as in flashed disable force encryption?

In that case you'll need to clean flash OOS and format data.
[OnePlus 7 & 7 Pro Cross Device Development] Bleuzen:
Hi @Nebrassy will you submit your changes to upstream so official TWRP can work again?
[OnePlus 7 & 7 Pro Cross Device Development] schumissimo:
Thanks for your answer, so I have to do a backup, format my OS and do a restore?
[OnePlus 7 & 7 Pro Cross Device Development] Korosensei090896:
I don't know what happened during backing up, but as I scan my recovery log, error starts at data/mdm

I:addFile '/data/mdm' including root: 1

==> set selinux context: u:object_r:oem_data_file:s0

failed to lookup fscrypt tar policy for '/data/mdm' - '5789f557000000000000000000000000'

I:Error adding file '/data/mdm' to '/data/media/0/TWRP/BACKUPS/6aa413fb/2021-06-11--19-54-53/data.ext4.win000'

Error creating backup.

I:ERROR tarList for thread ID 0

Error creating backup.

I:InfoManager saving '/data/media/0/TWRP/BACKUPS/6aa413fb/2021-06-11--19-54-53/data.info'

createTarFork() process ended with ERROR: 255

Backup Failed. Cleaning Backup Folder.

I:Copied file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/6aa413fb/2021-06-11--19-54-53/recovery.log
[OnePlus 7 & 7 Pro Cross Device Development] christantoan:
CMIIW but AFAIK adb wouldn't work in bootloader mode, only fastboot
[OnePlus 7 & 7 Pro Cross Device Development] dat_Noko:
Just used this to update to OB5 worked perfectly.

I did only boot TWRP not installed it.
[OnePlus 7 & 7 Pro Cross Device Development] xlxcrossing:
Worked fine upgrading from OB4 rooted w/o twrp to OB5 rooted with twrp.

1. Downloaded OTA first and installed and without rebooting restored stock images from magisk

2. Rebooted to bootloader and flashed twrp as per instructions

3. Allowed OTA to compile w/o root and booted system

4. Rebooted to twrp and adb sideloaded magisk zip

Thank you, donation given