yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] Aballamis:
Aaahh, yes will try that next. I used the included LOS-style recovery for watch dogs ROM to sideload the 01/05 install.zip. got some errors like sig verification failed and couldn't mount Metadata as none existed but it flashed. Gonna reboot to recovery and hope my touchscreen works.
[OnePlus 9 Pro] rav3ns:
can you try with old twrp ? open twrp and execute the dd with terminal option.
[OnePlus 9 Pro] der_akinator:
I think that should work
[OnePlus 9 Pro] arsalturtle891:
Understood. BTW, I followed step 4 and flashed the vendor_boot and the boot imgs from the OP9 folder and 8 was stuck on the fastboot icon. However, I was able to get out of it
[OnePlus 9 Pro] der_akinator:
I don't know whats going on with OOS13 at this point but if you really want to install TWRP you could try this.

https://xdaforums.com/t/recovery-3-...-a13-encryption-support.4523857/post-87984021
[OnePlus 9 Pro] der_akinator:
Does everything work with the installer or do you still have touchscreen issues?
[OnePlus 9 Pro] Aballamis:
Nah it still doesn't work. Abandon ship. I do t get it. It flashed just fine. Boots and all. Flashed the zip with adb sideload.

I'm using the 9 pro on f.18

Still having issues. But I also then tried to use the los recovery included by OP for watchdogs ROM to flash his included twrpinstaller.zip, which is your same twrp and same issue.

So then I tried to just say to hell with it and use his los to flash watchdogs and it gave an error that package is for OnePlus9Pro but expected lemonadep.

So, then I tried to flash his firmwareflasher.bat as he said I prolly didn't have firmware flashed on both slots. It gave an error

Fastboot: error: cannot check for partition <> on slot all (or something really close to that) for all the partitions except modem_a & modem_b.

So now I'm going back and unpacking the msm and gonna flash back to I guess 11. Start over.

I updated using Ota all the way to f.18 before flashing anything. But I didn't think that in doing so, I'd probably have f.18 on one slot and the last ver of f.17 on the other. Maybe this is where the BS came in?
[OnePlus 9 Pro] rav3ns:
For what reason is the copy of the ROM vendor_boot and fash in the last step?

Where we can obtain TWRP vendor_boot image ?

And another question;

instead of fastboot boot boot.img is possible to fastboot flash boot boot.img?
[OnePlus 9 Pro] der_akinator:
You find TWRP vendor_boot in the test-op9 folder.

Depending on your ROM vendor_boot contains some kernel modules, dtb and some configurations necessary to boot.

Directly flashing boot shouldn't be done because it would overwrite the ROM kernel and other files that might be needed to boot the ROM.
[OnePlus 9 Pro] der_akinator:
I hope you haven't lost any data. I will install OOS13 see what I can do.

i don't think it has to do with different versions on different slots.
[OnePlus 9 Pro] Aballamis:
Oh well I already had to msm back. I didn't lose anything. I just got the phone and hadn't moved anything over. Just waiting on the msm to finish.
[OnePlus 9 Pro] Mogster2K:
My phone seems to be completely frozen after booting TWRP. I can't even turn it off. My computer doesn't see it at all. What can I do, except wait for the battery to drain?

OnePlus 9 Pro TMO, just converted to EU and unlocked the bootloader again

OS: Android 13, Nov 2022 (dunno the build number)

TWRP: Unofficial Jaunary 5th build (3.7.0_12.1-2-lemonadep)

For some reason the build number displayed on the screen is 3.7.0_12-0.
[OnePlus 9 Pro] Aballamis:
I was having same issue. I think its an issue with OOS13. Push both volume up & down & power same time to power off. Then release. Then you can use power to boot system, or all 3 buttons again to boot bootloader and flash/boot something else
[OnePlus 9 Pro] Mogster2K:
Thank you! I was afraid I'd have to wait a couple of days for the battery to go dead...
[OnePlus 9 Pro] Aballamis:
Yea, nowadays with the devices, encryption, firmware and all that the software entails things are getting more and more complicated.

I would suggest rolling back to A11 and using the official TWRP to start. In the thread for Watchdogs ROM, the OP said it could be not having firmware flashed to both slots.

Most of all, with things being so tricky nowadays, and things bugging and changing from one Android version to the next, I would say the 1st thing you should do before you proceed with flashing anything is head to this thread and download the MSMTool for your model. Read the directions and I would go ahead and grab the drivers for the Qualcomm HSBOOT 9008 or whatever, its in the thread - but you gotta click the "source" link to get it. Thread: https://xdaforums.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
[OnePlus 9 Pro] Mogster2K:
The link is broken for the drivers in that post. :( Thanks tho. Anyway, the official TWRP doesn't read /data, but it can read the boot partitions. I was eventually able to get Magisk on the phone which was one of the main things I really wanted. I think I'll stay on A13 for now and see how it goes.
[OnePlus 9 Pro] der_akinator:
Update

This is mainly for OOS13 users that want to install via fastboot.

new OOS13 boot image for installation option 3 (tested on OP9pro with OOS13-F72 and F73)

adb works independently of mtp now. So it works before decryption and in fastbootd mode.

23-01-12 - Google Drive

drive.google.com
[OnePlus 9 Pro] osm0sis:
What's the adb vs MTP fix? I think most OnePlus devices need this!
[OnePlus 9 Pro] der_akinator:
I use the LOS qcom-usb-init + setup shell scrip in the same repo and merged it with the old usb init. Changes to the qcom init are just a couple of generic additions to adb, mtp and mtp,adb targets.
[OnePlus 9 Pro] Aballamis:
The official twrp doesn't read data because it only supports FBEv1 which is Android 11 encryption, so it can't decrypt the data partition to read the files. As for the drivers link, there are 2 links, one is the link, which didn't work for me either, you have to click the one next to it that says "source" of the drivers. I've got the drivers on one of my laptops. I'll see if I can upload them to this thread directly.
[OnePlus 9 Pro] Aballamis:
no, still touchscreen issues. also, later i used TheSayaMan's (OP for WatchDogs ROM) twrpinstall.zip sideloaded from his LOS recovery and from the twrp ver listed on splash it was the same as yours, or it is yours, and same issue. i cant remember now if i was still on f.18 at that time or if I was on OOS11 after having used the msm. Also, it may be noteworthy to mention his los recovery and subsequently ive used the crDroid los recovery installed by their c63 firmware flasher.bat utility, both worked fine. however, in the .bat flashers it showed that they not only flash the boot.img, but the dtbo.img and vendor_boot.img. maybe that's the issue??? because i have not tried method 4 using the vendor_boot.img, as there is not one for the latest (01/05) version, as well as not having the vendor_boot.img from f.18 as it only comes as an incremental and i dont know where/if it's available to download outside of the ota.

strangely enough, in his thread for WatchDogs ROM, he's got a DL link for a TWRP restore for stock f.18 A13 OOS. i was on A11 fresh from using the msm, so i booted then flashed the official twrp, which wouldn't mount data cuz couldn't decrypt, but it worked fine otherwise. However, when following his instructions to restore the twrp f.18 backup to both slots, it says to factory reset, then restore backup, format data, switch slots, reboot recovery, then restore again. but when i rebooted to recovery after reset, restore, format, switch slots, when the official booted up again, the touchscreen wouldn't work then either. which is strange as i mentioned before that it worked fine when booted from bootloader having already updated to f.18 via ota. Which leads me to believe that MAYBE (there are a lot of variables) its an issue with f.18. or maybe f.17 as well, OOS13 in general.

but i did finally manage to get a custom rom, i flashed WatchDogs, using the crDriod los recovery mentioned before. but in that thread he mentions having to have A12 or A13 fw on BOTH slots to avoid touchscreen issues. and when i told him about the issues i was having with the touchscreen on twrp (as he says you can use twrp for clean install of ROM, just problematic for updates), he said it was probably due to not having the same fw on both slots. which, i believe at the time, i was on f.18 via ota, as mentioned earlier. but having updated to f.18 via ota, i assume i still had f.17 on the inactie slot, so it may be an issue with not having the same fw on both slots. but this time around, i updated to c48 OOS12 before even unlocking my BL, and he updated his OP and instructions to include the c63 fwflasher.bat from crDroid, as he found his c66 fwflasher.bat isnt compatible with some variants. It all worked, and i was able to get the WatchDogs ROM flashed and working with his version of nikGapps and magisk, using the crDroid los recovery via sideload.

but i am still very interested in getting twrp installed and working, as obviously it does much more than los style recovery. and now i am not on OOS at all, let alone OOS13. and i Have c.63 A12 fw flashed to BOTH slots. so i'm hoping i can get your twrp working.
[OnePlus 9 Pro] Aballamis:
attached is the qualcomm HSLoader 9008 drivers for windows 10. just extract the files, preferrably into its own folder, then with device connected in edl/HSloader 9008 mode (with device powered off, hold both volume buttons down for a few secs, then plug in the usb cord thats already connected to your computer, then release the volume buttons. screen will stay black) open device manager and under "COMs/ports" there should be a Qualcomm device that is NOT "Qualcomm HSLoader 9008" or whatever. right click on that device, and choose update drivers. then choose browse my computer for drivers, then the little browse button, then choose the folder you extracted the contents of attached zip to, and profit. after the driers are installed, double check in device manager that it has changed to "Qualcomm HSLoader 9008". it did not require me to reboot my pc after updating the drivers. but then you can open the MSM .exe, and follow the directions on that thread and it should work. pretty simple. if you've already connected your device in the EDL mode before running the msm tool, once the msm tool opens it should say "connected" before you hit start. the thread instructions say to run the msm tool first and choose target "02" and hit start before connecting, but i always connect first or connect device before hitting start, so i can see that it's connected.

this tool should unbrick your phone under most all circumstances, provided you can boot into EDL mode. But it will roll you back to OOS11 that comes on the phone originally, as im sure youve read.

hope it works out for you.
[OnePlus 9 Pro] Aballamis:
Is this an update/fix for the issues with OOS13??? maybe it'll solve my issues with the touchscreen. although, as i mentioned in previous post, im on c63 right now. and im on global variant so OOS13 woulld be f.17 & f.18 for me. but imma dl just in case i still encounter touchscreen issues.
[OnePlus 9 Pro] arsalturtle891:
Thank you. That new Oos13 boot file did the trick. The touch works!
[OnePlus 9 Pro] arsalturtle891:
The only issue now is that twrp is giving an error when installing magisk24.2.zip stating "error installing zip file"
[OnePlus 9 Pro] der_akinator:
The 01/05 version had problems on OOS11 and worked only temporarily when booted from fastboot. I think that's also the version that is available with WatchDogs.

Version 01/12 should be backwards compatible because it loads some touche kernel modules that are only present on A11 ROMs. The zip installer was as it seems always fine on A12 and A13 custom and stock ROMs.

With the latest update you can boot from fastboot with OOS13 installed. I hope with that ale use cases are covered.
[OnePlus 9 Pro] Aballamis:
Thank you sir. I'm gonna try it soon.
[OnePlus 9 Pro] der_akinator:
You should probably use version 25.2. The apk can be flashed like a zip installer. This works at least on OOS13-F73
[OnePlus 9 Pro] arsalturtle891:
So I should use the apk and not the zip?
[OnePlus 9 Pro] der_akinator:
Yes, flash the apk in TWRP and install it after booting to system. For other flashing utilities you might have to change the ending to zip.
[OnePlus 9 Pro] Benji1983:
Hi dear dev,

I'm just playing a bit around with the loved twrp

First the pro:

Backup and restore working like a charm (saved me a few times)

Cons for me (I know it's in early stage and not meant to work perfect on oos13)

Formatting data is giving error : unable to check mergestatus ( see screenshot)

Tried installing a Rom just for fun and a few errors appear (mount system, mount vendor etc. Failed) tried to I stall new nameless A13 rom

Overall it's fantastic to have a dev who is working actively on making a great device even better

Device : op9 pro running .F73 OOS13

View attachment 5810375

Just saying it's no big deal just wanted to say this if I could help you

Greetings

Benji
[OnePlus 9 Pro] golfgtiedition30:
This is awesome. Flashed in magisk and rooted again via TWRP. Amazing work 👍
[OnePlus 9 Pro] der_akinator:
There is some works regarding this issue but it isn't production ready yet. Maybe with the next TWRP release.
[OnePlus 9 Pro] NAGARAJU02:
Yesterday I install 13/01/2023 twrp in crDroid 9.1 (clean flash) no any issues

I am waiting for new update (crDroid-9.1)?

Thanks
[OnePlus 9 Pro] HessNL:
I have been trying it on oos 13 and it's seems that nothing is wrong with it decryption worked and flashing and magisk if there where only custom kernels for trying to flash or other StuffView attachment 5813979
[OnePlus 9 Pro] IamTheBRAVE:
Hi, everyone. I recently updated my rom and flashed the twrp installer via magisk. After rebooting, twrp always shows static screen, i can't access anything there. Tried using Fastboot to boot it but no luck. I must be doing something wrong. Can anyone help?
[OnePlus 9 Pro] Mr.Conkel:
Does your android system work correctly?

Try flashing the vendor_boot that is provided?
[OnePlus 9 Pro] IamTheBRAVE:
Yeah system is working fine. Rerooted though boot patching. I thought about vendor boot and i think i did a small mistake there, i did fastboot boot (instead of flash) i'll try again later (don't have access to my pc rn) Thanks for the reply.
[OnePlus 9 Pro] Mr.Conkel:
That won't help at least probably. You should be able to boot the latest img out right. I can on Crdroid
[OnePlus 9 Pro] IamTheBRAVE:
Do you think crdroid rec would work, or maybe Los? Haven't tried yet.
[OnePlus 9 Pro] Mr.Conkel:
Yes it should, I'm using Crdroid v9.1 with it just fine
[OnePlus 9 Pro] der_akinator:
Which ROM do you use? Maybe I can reproduce and find the issue. For ROMs with OOS13 firmware please use boot-oos13.img from latest build for fastboot boot.
[OnePlus 9 Pro] IamTheBRAVE:
I'm on Paranoid android 13 Tobaz beta 2 ( an unofficial buildnot by op)
[OnePlus 9 Pro] der_akinator:
I don't know where to find it. If you provide a link, I will see what I can do. Maybe it has something to do with with the changes to their kernel module, which are now build inline. And did you use latest 12-01-23 build.

Edit: It could be possible that I'm missing to load a kernel module. Could you provide the output of the command "lsmod". Or they are installed to a non standard path.
[OnePlus 9 Pro] IamTheBRAVE:
I used the 05-01 i think. The rom link was posted on telegram.

aospa-topaz-unofficial-oneplus9pro-20230116.zip

drive.google.com

The official build is still not out due to display issues. This build works.

I'll keep trying later. Thanks for taking the time to look into this👍
[OnePlus 9 Pro] der_akinator:
I've read that there are some display issues with the kernel. Stock AOSPA recovery also have some issues and just shows random noise when I try to use it. I think the best thing is to wait for an official build. But with their current kernel, it is probably only possible to install TWRP via zip installer.
[OnePlus 9 Pro] NAGARAJU02:
Are you using new 13/01/2023 twrp

And which rom update bro
[OnePlus 9 Pro] Andsie:
updating in TWRP preferred`?
[OnePlus 9 Pro] TheSayaMan:
No, not if you want boot errors. Update by either custom recovery or built in system updater. You can always restore twrp after that with zip if you retain root with magisk or booting twrp again. Guess it depends on the ROM. If you are using one that requires gapps than definitely NO!!!
[OnePlus 9 Pro] Andsie:
I meant updating the new version TWRP from this thread of the dear host itself
[OnePlus 9 Pro] der_akinator:
There aren't any major changes, but if you want to use adb in fastbootd mode you should use the latest version.
[OnePlus 9 Pro] Aballamis:
@der_akinator

Hey, it's been a while but I wanted to update you. If you remember I was having severe problems with getting my 9 pro going, especially with TWRP. Well, I got profit. I used the crDroid c63 fw flasher instead of TheSayaMan's c66 flasher which apparently doesn't work for my variant, to get fw on both slots. That crDroid flasher installs their LOS style recovery, I believe I saw a post in the crDroid 9.1 thread from you about the kernel on the 20230113 build so I think you already know. But I used that recovery to flash WatchDogs & Magisk, but was getting hella glitches. Seemed like a copy&paste ROM w/different boot animation anyways. So I switched to crDroid. BTW, that comment on the crDroid thread saved my butt again - couldn't figure why Magisk wouldn't go.

Anyways, got crDroid working, flashed your updated TWRP v3 and it's working great. Magisk too, after they updated the boot.img for the 20230113 build - thanks to your comment.

However, when I try to flash blu_spark 120 in TWRP, I get an error: vendor_dlkm larger than vendor_dlkm partition: aborting. But I guess that's a question for the blu_spark thread.

Also, I had meant to say thanks and let you know everything has been working out, but right when I got things going, I got an error on the app/site "oops, someone call neo. We broke the matrix" that my account had been BANNED! I never get in pissing matches or solicit or participate in solicitations or anything, so I dunno. It mentions being hijacked and I hadn't noticed any unusual activity, but now that I got it back (finally), I went to my account info and there was some weird stuff. Said I was in Sweden and an associated account id never heard of. The error msg says "allow 72 hours for response" - took 10 days. But that's still better than starting over from a new account. Kinda sad, but I'd prolly cry if I lost my "senior" status, which is probably just due to membership time. 😒 DroidNerd 4 life.

Thanks again.
[OnePlus 9 Pro] brandon79:
So maybe I'm confused or maybe I'm doing something wrong. IDK. So one plus 9 pro bliss custom ROM. Android 13 based on 12.1. kinda new to 9 pro my last was a 6t. Anyway i had ROM installed flashed TWRP reboot recovery flash magisk again. Reboot system. Decided to reboot to recovery to check it out farther and TWRP is no longer there. It's back to LOS recovery again. So am I doing something wrong or is TWRP not suppose to retain.

Edit: figured out my problem. After I flashed TWRP I rebooted to system. Installed magisk again, select file and patch, with TWRP installed. Then reboot to recovery and flash the magisk patched img. That had TWRP flashed and that did it.
[OnePlus 9 Pro] der_akinator:
I installed blu_spark on top of crdroid 20230113 build because of the magisk issues, but everything went fine for me. Maybe try the latest r123 blu_spark release.
[OnePlus 9 Pro] der_akinator:
You can also flash the Magisk.apk directly in TWRP like a zip. That's a bit more comfortable.

On this device it's also a bit more complicated to keep TWRP installed, because every time the boot partition is overwritten it is gone.
[OnePlus 9 Pro] Aballamis:
I used FKM to install r123 and it went off without a hitch. This was also recommended by a few in that thread.

Thanks for the help and the v3 TWRP.
[OnePlus 9 Pro] Mr.Conkel:
Anyone know if I should use the OOS13 boot.img for oos13 based custom roms?
[OnePlus 9 Pro] der_akinator:
Yes, it's for roms with OOS13 based firmware. For the zip installer it doesn't matter.
[OnePlus 9 Pro] A6ekAK:
Hello, I'm on CrDroid 9.1 and I wanted to go back to OOS 13 but while trying to flash the oos zip in twrp i get error 23 (kdownloadmanifestparseerror), can someone help me?
[OnePlus 9 Pro] der_akinator:
The easiest way is to use the MSM tool for your phone version. You can also try to manually create and flash logical partitions within super.
[OnePlus 9 Pro] A6ekAK:
And that's what I did, thanks for help.
[OnePlus 9 Pro] osm0sis:
@der_akinator, could you add vendor_boot and dtbo to the list of partitions available on the Backup page? It'll cover everything important for custom kernels and recoveries in a backup/restore that way. 🤞😁
[OnePlus 9 Pro] der_akinator:
Yes, I can upload a new build in a couple of hours.
[OnePlus 9 Pro] der_akinator:
Update

add vendor_boot and dtbo to backup targets

add CPU temperature output

fix vibration (still doesn't work in fastbootd mode)

I tested this build on LOS 19.1 (OOS 12 firmware) and crdroid 13 (OOS 13 firmware). Also keep in mind that you have to use the boot image according to your installed firmware, if you want to install/test via fastboot.

23-02-04 - Google Drive

drive.google.com
[OnePlus 9 Pro] Mr.Conkel:
On Crdroid v8.12 with C.63 OOS12 firmware going into any menu freezes the build. Touch will work from the start but after that it freezes completely.
[OnePlus 9 Pro] 1thomas:
Working here perfectly here at OxygenOs F.20, I installed with zip by the Magisk, including the backup of dtbo and vendor_boot occurred successfully, thanks for the work
[OnePlus 9 Pro] osm0sis:
That's the vibration bug again. As a workaround don't decrypt and go to settings and turn off vibration, then go to mount and decrypt and reboot so it saves the settings file.

Guess we'll need another build with vibration disabled again @der_akinator. 🫤
[OnePlus 9 Pro] gsser:
Working fine on latest oos 13 eu
[OnePlus 9 Pro] der_akinator:
I disabled vibration and replaced the last build. Was it the boot image or the zip installer that led to freezing?

23-02-04 - Google Drive

drive.google.com
[OnePlus 9 Pro] Mr.Conkel:
Just the boot.img apologies for the late reply
[OnePlus 9 Pro] solar666:
Have seen that there is a test version on your google drive. What needs to be tested?
[OnePlus 9 Pro] der_akinator:
I uploaded a new test builds with vibration enabled and some additional safety measures to prevent lagging or freezes. Feel free to test it.

05-02-23-vibration-test - Google Drive

drive.google.com
[OnePlus 9 Pro] osm0sis:
Boots and runs fine on LOS 19.1, but no vibration still.
[OnePlus 9 Pro] der_akinator:
Update

improve vibration support

fix kernel modules loading in fastbootd mode for custom roms (might result in an error message regarding vendor_dlkm for OOS users, but it's just cosmetic)

Tested on LOS 19.1 (OOS 12 firmware) and crdroid 13 (OOS 13 firmware).

23-02-08 - Google Drive

drive.google.com
[OnePlus 9 Pro] osm0sis:
Working great now! Well done!! 😁🎉