yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] JohnTheFarm3r:
It can be sideloaded on Android 12 (latest OOS12 based custom ROMs) and 13 (NOT FLASHED, SIDELOADED), but the internal storage is not readable unless you force decrypt your storage and keep it like that.
[OnePlus 9 Pro] no111one:
It now boots, I downgraded to ColorOS C.65 and instead of livebooting, just magic-flashed the installer. Problem is, I can't boot Android anymore!

Other than that decryption doesn't work.
[OnePlus 9 Pro] Redn2000:
Decryption doesn't work because A12+ isn't supported yet, so you might need to use the MSM tool to recover.

And what version of magisk are you trying to use? I found that 23 doesn't play nice with A12 when I tried before.
[OnePlus 9 Pro] no111one:
I extracted the boot image from payload.bin, so just flashed it back, booting again.

I used Magisk 25.2 and if I try to use both TWRP and magisk it just does not boot for no reason.

P.S. removing the ls password as stated fixes decryption, and storage is mountable.
[OnePlus 9 Pro] leviackerman91:
Hi! I lost root after last update

I can't boot the patch imaged or twrp, it always says command failed, drivers and cable should be ok

How can I solve?
[OnePlus 9 Pro] jamescable:
So, new to 9 pro from 8 pro. So how do we force decrypt storage?
[OnePlus 9 Pro] rejectedjs:
That's the neat part, you don't
[OnePlus 9 Pro] jamescable:
Then how do we get it to work on a12 custom?
[OnePlus 9 Pro] osm0sis:
Just wait a few days and new TWRP will likely be available.

https://gerrit.twrp.me/c/twrpme/+/5910
[OnePlus 9 Pro] jamescable:
Glad to see you on the 9 pro. Loved working with you and infected on 8 pro twrp
[OnePlus 9 Pro] osm0sis:
Hmm, or not: https://jenkins.twrp.me/view/TWRP Release Android-12.1/ ☹️

We need a new maintainer to bring-up the device tree to android-12.1, since @Nebrassy has confirmed he is stepping down.
[OnePlus 9 Pro] jamescable:
Feel like taking the reigns?
[OnePlus 9 Pro] MJPollard:
That's a bit distressing. TWRP already seems to be akin to a loyal dog that's been abandoned by the side of the road; this piece of news doesn't exactly brighten one's hopes. 😢
[OnePlus 9 Pro] osm0sis:
Nah, not at this point anyway. I've been trying to simply set up my new laptop for like 5 months, but there just hasn't been enough time between work and with our 7 month old baby at home.
[OnePlus 9 Pro] jamescable:
I would try and get infected to help but he abandoned the 8 pro and haven't been able to communicate with him for months so not sure what's going on there
[OnePlus 9 Pro] filjusz:
Really bad news... I was hoping to see TWRP on our device working this month... What a shame
[OnePlus 9 Pro] CZ Eddie:
What am I doing wrong?

I'm on Android 11 AOSP custom ROM that uses their own custom recovery.

When I go into fastboot mode and run "fastboot boot twrp.img" it "flashes" without any error.

Then when it reboots and tries to go into TWRP, my phone gets stuck at a "fastboot mode" splash screen.

This is my TWRP file. twrp-3.6.2_11-0-lemonadep.img

EDIT: RESOLVED:

I tried to reflash my ROM but it failed.

Then, I flashed this kernel: Requiem-Nightly-03092022-LEMONADE.zip

That soft-bricked me. So, then I flahed a much older version of my ROM and that worked fine.

Now I'm able to fastboot boot to TWRP without any issue.

I figured it was probably a kernel issue. I think I was previously on Arter kernel.
[OnePlus 9 Pro] jamescable:
Anyone try it yet?
[OnePlus 9 Pro] filjusz:
It doesnt support android 12/12.1
[OnePlus 9 Pro] MJPollard:
The "_11" suffix on the version number means that it only supports Android 11 or lower. Android 12 (and its encryption) still isn't supported, at least not for the 9 Pro. :(
[OnePlus 9 Pro] jamescable:
Worked for me...we got twrp 12 now...
[OnePlus 9 Pro] jamescable:
Did you not look at the changelog? It literally says it supports it
[OnePlus 9 Pro] osm0sis:
Android 12 decryption is listed in the changelog under the Android 12 branch. Unless something crazy has happened I think you'll find once you boot the ROM and it sets up encryption you won't be able to use TWRP decrypted, if at all.
[OnePlus 9 Pro] jamescable:
I was able to boot ROM, And go back to twrp and use it again just fine. You need this to do a full device decryption
[OnePlus 9 Pro] filjusz:
I have flashed it. Not working on LineageOS 19.1
[OnePlus 9 Pro] osm0sis:
Right, so DFE = Disable Force Encrypt. Most people don't want to run their devices unencrypted. So yeah, TWRP _11 doesn't support Android 12 decryption, as previously stated.

I don't recommend anyone else try using TWRP _11 on an Android 12 ROM with encryption either, since I just did and now I can't get Lineage 19.1 to boot, so :(

Edit: Dirty flash of ROM from Lineage Recovery (+GApps +Magisk since addon.d doesn't work in Lineage Recovery) got it booting again. 😅
[OnePlus 9 Pro] 4Xrayk:
Have you tried the backup function yet?
[OnePlus 9 Pro] MJPollard:
FWIW, I don't ever rely on addon.d working, no matter which recovery I use. Whenever I update my ROM, I always flash the new version, reboot to recovery, flash MindTheGapps, flash Magisk, reboot, profit. :D
[OnePlus 9 Pro] Flecto:
I **might** be interested in helping out. I want to get TWRP running on A12 on my OnePlus 9 Pro, too. I am a software engineer, so I'm familiar with dealing with code, git, and whatnot. But I've never done anything with Android, so I would need some pointers in what exactly is involved with maintaining a device tree. What is the purpose of the code in the device tree? I'm assuming it has to do with configuring TWRP for a specific device? What is the process for figuring out what the configuration is? How do I get started?
[OnePlus 9 Pro] osm0sis:
Hey! Join us on the TWRP Zulip at the link in the release post: https://twrp.me/site/update/2022/10/10/3.7.0-released.html

All the active maintainers are there so I'm sure there will be someone to point you in the right direction! 😁
[OnePlus 9 Pro] gillim74:
TWRP 3.7 released with Android 12 compatibility and support for more devices

Your favorite custom recovery now officially works with Android 12

www.androidpolice.com
[OnePlus 9 Pro] gillim74:
There is a 3.7 build for op9 pro on twrp website
[OnePlus 9 Pro] Flecto:
Yes, but it only supports Android 11. There is no build yet with the new Android 12.1 branch, afaik.
[OnePlus 9 Pro] MJPollard:
I really wish people would stop pointing to this. Yes, 3.7 is released for A9/A11/A12, but the fact remains that the 3.7 version still only works on A11 for the OnePlus 9 Pro; it has

not

been upgraded for A12. Look at the filenames; they're twrp-3.7.0_11-0-lemonadep.img and twrp-installer-3.7.0_11-0_lemonadep.zip. The _11 indicates that it only works for A11 and earlier; it will not decrypt a 9 Pro running A12. The changelog in the article is generic for every TWRP version available, and even though it mentions the A12-specific changes, we still do not have those for our device.
[OnePlus 9 Pro] jamescable:
It works for those that know how to. For me, it works on 12.1 for backup, flashing ROMs, magisk, etc....deleted a bad magisk module during bootloop, able to transfer files in the case of a needed msm to fix, etc. You just can't flash it, but boot it when needed
[OnePlus 9 Pro] osm0sis:
Having to run unencrypted is a pretty huge caveat. 😉
[OnePlus 9 Pro] jamescable:
For some lol. I don't keep important info on phone. And I don't go to sites that download stuff that can hack the device
[OnePlus 9 Pro] MJPollard:
It doesn't work when the phone is encrypted, which I suspect is the majority of cases because that's the default mode of the phone. LIke osm0sis said, that's a pretty important caveat, and just dismissing it out of hand like you're doing (and not even mentioning it when you throw out your blanket claims of "yes, it does work") isn't helpful in the slightest.
[OnePlus 9 Pro] jamescable:
Ive posted how to become decrypted already..., and Osmosis and I have worked together before on 8 pro with another twrp dev. I'm not fighting nor arguing with him or anything.
[OnePlus 9 Pro] MJPollard:
Don't ever recall saying you were fighting, actually, and it doesn't really matter if you've posted how to run decrypted. The fact remains that even the current TWRP 3.7.0 still does not work on the 9 Pro using Android 12 in its default mode (encrypted), and forcing them to decrypt their phones just to run TWRP (as you seem to be advocating) is a step some/many/most don't want to take. I'm hoping that someone else can take over the reigns from Nebrassy and update the 9 Pro TWRP to handle Android 12, because it's rather depressing to be one of the ones on the outside looking in.
[OnePlus 9 Pro] jamescable:
Sorry, I was only posting a way for those who want to do it
[OnePlus 9 Pro] mustangtim49:
Thank you, at least you cleared the air about that. I'll run unencrypted to play with TWRP, hell yeah! I actually downloaded it a few days ago and I kinda figured it out on my own, but thanks again for confirming it.
[OnePlus 9 Pro] more_than_hater:
Somewhy i can't boot any version of this twrp, starting from latest 3.7.0 and down to 3.5.2

A11 11.2.10.10

after the boot command display blinks and after that normal OS boot will occur.

any suggestions, gentlemen?

//Update

I found the culprit. Custom kernel which affects boot, dtbo, vendor_boot causes this.

Even more, i couldn't fastboot boot anything at all.
[OnePlus 9 Pro] erad1:
anyone familiar with siddk? he found a way to get TWRP for A12 working with encryption, wondering if he could help us here?
[OnePlus 9 Pro] Z-Blade:
I looked at other threads about TWRP and it looks like 3.7 will also work with A13 because there is no change in encrption. It saddens me how far OP has fallen, OP phones use to have heaps of choices in regards to custom kernel and roms.
[OnePlus 9 Pro] jamescable:
If you know what you're doing, twrp works fine with 12.1 and 13
[OnePlus 9 Pro] TheSayaMan:
a13 doesn't work. It boots back to bootloader and I have to re-flash boot.img to get it to boot again.
[OnePlus 9 Pro] INviSibl3KIL97:
does it support oos13?
[OnePlus 9 Pro] TheSayaMan:
Did you even read my last comment? That was a dumb question!!! READ!!!
[OnePlus 9 Pro] jamescable:
Not officially. You need to flash a few things that will fully decrypt your device and allow full r/w on device in order to use twrp on 12.1+
[OnePlus 9 Pro] Ionic_:
I've seen that guacamole (OP7P) has an A12.1 branch and FBEv1 and FBEv2 builds, also spearheaded by Nebrassy.

Shouldn't it be possible to base lemonadep (and sm8350-common) device trees on that to get it working? While that was my initial idea, I'm not even quite sure where to start. The android-12.1 branch was probably forked off the android-11 branch in the guacamole repository at some point, so I guess I could just look for that in the git log, figure out what changed after the branching point and adapt that for lemonadep.

Does sound like a lot of work and the basic question is if I can find the branching point and actually understand what other changes have been made.
[OnePlus 9 Pro] IamTheBRAVE:
Can you be a bit more specific and share how you did it with the rest of us?

Because so far, r/w (and maybe data decryption ) is only possible in A11 (and possibly A12, but not confirmed) with a script and by extracting your super.img partitions to modify their fs type.
[OnePlus 9 Pro] jamescable:
[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Disable Force Encryption Native Early Override (DFE NEO v2) | Disable encryption /data | userdata

Brief description: Disabling encryption without direct modification of system files. Mount method, i.e., RW not required. Supports EXT4(RO/RW), EROFS, F2FS(RO/RW). Description: DFE-NEO v2 is a script designed to disable forced encryption of the...

xdaforums.com
[OnePlus 9 Pro] IamTheBRAVE:
I asked the dev earlier, and he said his script is to decrypt data not to get r/w. But if you do decrypt, does everything work in TWRP? Some people seem to think not. Can you give us screenshots of backup, restore, zip flash, etc? Also of file manager making r/w changes to /system partition? Thank you.
[OnePlus 9 Pro] jamescable:
This was discussed in crdroid telegram
[OnePlus 9 Pro] der_akinator:
Hi everyone,

I have got TWRP 3.7 based on android 12.1 working, but data decryption still does not work. Any ideas how to get the logs? They are by default written to data which does not work. Is there a way to get them over adb or so?

In the case someone is interested here are the links to the device tree:

GitHub - nilz3000/device_oneplus_lemonadep-TWRP

Contribute to nilz3000/device_oneplus_lemonadep-TWRP development by creating an account on GitHub.

github.com

GitHub - nilz3000/device_oneplus_sm8350-common-TWRP

Contribute to nilz3000/device_oneplus_sm8350-common-TWRP development by creating an account on GitHub.

github.com
[OnePlus 9 Pro] jamescable:
Have you tried flashing the dfe zip a few posts up?
[OnePlus 9 Pro] der_akinator:
It is not useful because I want to keep encryption. If it's just for testing purposes I would be able to write the logs but I can't see whats going wrong with decryption, because I wouldn't decrypt anything.
[OnePlus 9 Pro] osm0sis:
You should ask in the TWRP Zulip (linked on the website), the devs should be able to point you in the right direction to troubleshoot decryption.
[OnePlus 9 Pro] der_akinator:
Decryption is working now. But the caveat is that you have to flash a vendor_boot image to boot twrp. I'm looking to find a way around this either by avoiding it at all, which might not be possible, or by merging the rom and twrp vendor_boot into one. If someone has some experience or ideas please let me know.

If you want to test it, the best way is to download or extract a copy of your rom's vendor_boot. After that you flash the twrp vendor boot and boot the boot.img the same way as the old twrp. In order to boot into your normal OS, the rom's vendor_boot image has to be reflashed.

Edit: Permanent installation seems to work. So after installation as described by Nebrassy reboot to bootloader and reflash rom's vendor_boot. After that you should be able to boot into your normal OS and TWRP. I tested it with crdroid 13.

Here is a link to the two images you need:

twrp-lemonadep - Google Drive

drive.google.com
[OnePlus 9 Pro] TheSayaMan:
I'm not exactly sure how to do this but I'm on 13 now so I can't test it.
[OnePlus 9 Pro] der_akinator:
I'm on 13 too. It should work on 12 and 13 because encryption is the same. 12.1 is just the base of the TWRP image.
[OnePlus 9 Pro] osm0sis:
2 ideas.

Is there a way to repackage the vendor_boot ramdisk on-the-fly with what it needs and could still work with the ROM? This device is vendor_boot v3 so we could still use magiskboot for it.

I seem to recall the issue is that Lineage moved the recovery resources (images, etc.) to the vendor_boot ramdisk, but I was wondering if some hacks could be made to the TWRP init to force using the boot ramdisk recovery resources again instead.
[OnePlus 9 Pro] TheSayaMan:
Thanks for the info. I'll give this a try then. Thanks!!
[OnePlus 9 Pro] der_akinator:
I have just noticed, after unpacking it, that I build vendor_boot v4, which still boots. Due to the modular design of v4 it might be possible to use twrp's ramdisk as the RECOVERY fragment and repack it with everything besides the recovery part of the rom vendor_boot. Here is a link for those who are interested https://source.android.com/docs/core/architecture/bootloader/partitions/vendor-boot-partitions.

On the other hand does the twrp vendor_boot just contain one kernel module which is also present in the boot image. I also tried to use vendor_boot v2 that moved the dto* files to the boot image, but I was not able to boot that way. Maybe I have to adjust some init stuff for the v2 approach.
[OnePlus 9 Pro] TheSayaMan:
I can confirm this works. I'm on CrDroid a13 and after booting twrp and using my pattern, it decrypts. Thank you!!!
[OnePlus 9 Pro] Vladd:
First, I'd like to thank the developers, and then to put a couple of questions, just to clarify some details :)

I have a stock OP9 11.2.3.3 LE25BA rooted with Magisk-patched boot.img and Magisk 22.0 installed.

The first question is: as far as I understood, after booting into TWRP and permanently installing the TWRP through Advanced tab, I should reboot into Recovery, i.e. that just installed TWRP, and from there flash Magisk (I guess the same version installed on the phone, i.e. 22.0), but with extension changed to zip instead of apk, so it could be flashed? Thus the TWRP is installed and the root preserved?

The second question is: Does the current TWRP build, 3.7.0, have the full and reasonably reliable backup/restore functionality, and if not, what solution for that part, i.e. full backup of the phone and potential restore would you recommend (to clarify, only the local backup solutions, I don't want to have anything to do with any cloud, either BBK or, especially, Google :) )? Thank you very much.
[OnePlus 9 Pro] osm0sis:
v4 boots but this is a v3 device, and all the ROMs use v3 so TWRP should stick with that too for compatibility.

As for where the recovery resources are, OOS keeps them in boot partition ramdisk (i.e. boot-as-recovery/RECOVERY_AS_BOOT), but then Lineage moved them to the vendor_boot v3 ramdisk instead.

So yeah, one of my 2 ideas above could work.
[OnePlus 9 Pro] der_akinator:
I have not tested backup and restore for 3.7.0-12.1 but it should work as good as 3.7.0-11.0. You should not try to install the unofficial 3.7.0-12.1 build, it doesn't work. This is just for testing while temporarily booted.

For the official build I would do the installation as described by Nebrassy but I have not tested it and don't run OOS11.
[OnePlus 9 Pro] Vladd:
Thank you for the warning, I went for 3.7.-11.0 in any case. In the meantime, I decided to try the installation and see what happens, had to install the recovery ramdisc, then flashed the Magisk 22.0 with a zip extension via Install, i.e. normally, rebooted into recovery just to see if all's OK, and then into System, and everything seems to be OK, the root is preserved etc.
[OnePlus 9 Pro] Ionic_:
The Magisk APK is actually a hybrid: it can be used to install the manager on a running system and is also a flashable ZIP file.

You can just flash it without having to worry about the filename extension.
[OnePlus 9 Pro] osm0sis:
Weird with the snow issue; when run with `fastboot boot` is the only time the blu kernel would be used, and that should just work on its own since it's more self-contained with the inline touch modules... 🤔

Edit: Ahh, @Nebrassy informed me it's vendor_boot conflicting, of course. 😕
[OnePlus 9 Pro] osm0sis:
Backup seems to work, and restore completes, but first boot will be a black screen, and the subsequent boot might go back to normal but hard to guarantee everything will work as it should. That's from my testing on OOS stable.
[OnePlus 9 Pro] Rootk1t:
Did you test it on OP 9 Series only, or it will work for 8T also?
[OnePlus 9 Pro] osm0sis:
@bigbiff found similar results in his 8T testing.
[OnePlus 9 Pro] Nebrassy:
Hm, not sure what the problem is, it worked for @neobuddy89 who's also on crDroid, can you check if advanced > install recovery ramdisk works?
[OnePlus 9 Pro] htokluman:
It's working. Thanks(y):love:
[OnePlus 9 Pro] djsubterrain:
Could it be the original OOS base? How much of that is retained after installing crDroid? I was on 11.2.6.6BA cos 7.7 isn't out yet, possibly @neobuddy89 was on 7.7?

Tried installing ramdisk, shows explorer to pick the image file but same error
[OnePlus 9 Pro] Haunt3r:
All went through perfectly. Thank you for this!

Question, I was trying to move from 11.2.7.7AA to 11.2.6.6BA and couldn't through adb/system sideload, would I be able to use TWRP to flash over to this version, or would this cause issues since 11.2.7.7AA is newer?

(Trying to get over to the other firmware since AA only does incremental updates now, and it's a whole hassle to keep safetynet on them from what I read from osm0sis and BA appears to be receiving full updates instead of just OTAs)

Edit, just for the record if anyone else wants to do this, you can, I flashed the 11.2.6.6BA in twrp, and then rebooted (forcing it to boot the opposite slot I was on), then re-installed twrp per OPs instructions (as the recovery img for the opposite slot was still stock) and flashed omega then magisk. No issues so far. Will update if I run into any (dirty flash btw, didn't do a wipe of the system)
[OnePlus 9 Pro] MiDoMo3gza:
Can i install it to color os
[OnePlus 9 Pro] boybkol:
Installed and working perfectly fine on my OnePlus 9 with no trouble installing at all. Thanks.
[OnePlus 9 Pro] Hot-Proton:
Have now installed on EU 2.6.6 and working fine with Magisk. Will test more later. Whene i install stock full oss this replace the recovery? Only whene i reboot now the phone its take a bit longer now to enter the homescreen. Get always now first Phone is starting.
[OnePlus 9 Pro] Hot-Proton:
USB mount not work on 9 Pro.
[OnePlus 9 Pro] toolhas4degrees:
Did you run the adb sideload command, or are you talking about reading file from flash card to flash on phone?
[OnePlus 9 Pro] Hot-Proton:
I mean from USB Drive.
[OnePlus 9 Pro] _MartyMan_:
Does not work on OP9 with Paranoid Android. "Fastboot Mode" screen shows up after fastboot boot and that's all
[OnePlus 9 Pro] Mar-cel:
yup OTG not working and the temperature are not working
[OnePlus 9 Pro] Haunt3r:
One interesting thing I've come across if you are flashing a full update, it flashes to the inactive slot (this is fine), however to continue flashing additional zips (ie custom kernel, magisk etc) you need to reboot to recovery to change the boot slot, and in this process TWRP is lost, and you need to boot from twrp.img and install it. Not a big deal I think but I figured I'd let you know.

Edit: Thought of something, is there a way to boot twrp.img as the recovery during the switchover to the inactive slot?
[OnePlus 9 Pro] GHOST1010:
It's been this way since a/b ,even tho you flashed a rom your active slot remains the same , it is changed on reboot, if you want after the flash check the current active slot form reboot menu in twrp, change it to inactive (other) slot were the update was flashed ,and install twrp recovery again and reboot system / or reboot recovery and flash magisk/kernel .

Takes a bit to learn how it works if your new 👍
[OnePlus 9 Pro] William.trem:
GitHub - Magisk-Modules-Repo/twrp-keep: twrp-keep

twrp-keep. Contribute to Magisk-Modules-Repo/twrp-keep development by creating an account on GitHub.

github.com

🍻
[OnePlus 9 Pro] Libra420T:
for me (9pro) on any rom flashing installing backup restore, etc all work. but I'm not getting connection with pc. Tried on Latest twrp with OOS Los & crD 🤔

Need logs?
[OnePlus 9 Pro] andrew_yousry:
can you please explain again how to test it?

and steps to flash because I didn't understand.

what are the files needed

thank you
[OnePlus 9 Pro] der_akinator:
1. Get your rom's vendor_boot image. For most roms this can usually be downloaded. For OOS based roms you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.

2. Reboot to bootloader.

3. Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.

4. Run "fastboot boot boot.img" with the TWRP boot image.

5. Optional permanently install TWRP as described by Nebrassy in the first post.

6. Reboot to bootloader.

7. Run "fastboot flash vendor_boot vendor_boot.img" with the rom vendor_boot image from step one.

Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other roms or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot.

Here is the link for the two images:

twrp-lemonadep - Google Drive

drive.google.com