yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] TheGhost1951:
Another possibility is to extract the zip file to get the payload.bin file and flash it with fastboot enhanced!
[OnePlus 9 Pro] der_akinator:
Unfortunately, you can't flash OOS OTAs with TWRP. At least not if you have a custom ROM installed. I never tried to do this with OOS already installed, but it might work. This is because all OOS full OTAs are marked as partial updates, which only updates a subset of partitions that have a time stamp older than the OTA. The problem is that custom ROMs, most of the time, don't have this time stamp set or are too recent.

You can either use MSM tool or extract the OOS OTA and flash partitions with fastboot.

Here is a project/script that uses the fastboot approach:

https://xdaforums.com/t/fastboot-rom-oos-oneplus-9-pro-stock-fastboot-rom-eu-cn.4588383/
[OnePlus 9 Pro] lg-optimus:
Sorry, I am a little bit confusted what to do exactly, because there are 3 files in the download.

There are 3 files in twrp-installer-3.7.0-12.1-8-lemonadep.zip

boot.img

ramdisk-recovery.img

twrp-installer-3.7.0-12.1-8-lemonadep.zip

I have a misflashed phone, which starts only in fastboot-mode, there is no recovery.

I have been told to install oneplus_9_pro_13.1.0.500ex01_firmware_flasher.zip too.

Please tell me which steps I have to do first.

The attached file, is the only screen where I can do something. Selecting recovery brings me back to this screen.
[OnePlus 9 Pro] shadabkiani:
Use the MSM Tool to revert your phone back to initial factory settings. This will revert back to OOS11. Download the correct version of MSM Tool for your phone variant from this link. Turn off your phone and set it aside, DO NOT connect to PC yet. Once your download MSM Tool zip, extract it. Then run the exe file. Once it loads, click Start. It will now wait for device. Now come back to your phone, hold vol+ and vol- buttons (without power button) and connect the data cable. Your phone will enter EDL mode, but the screen will still be off. Your PC will recognize the device, and flashing will start. In about 4-5 mins, it will be done. Once your phone reboots, upgrade your phone through System Update OTA.
[OnePlus 9 Pro] der_akinator:
You only need boot.img and you can probably skip permant Installation (steps 4 and 5) in your case. If you cant boot you habe to flash vendor_boot and dtbo images of any known a12 vor a13 rom.

I don't know what oneplus_9_pro_13.1.0.500ex01_firmware_flasher.zip does and what your exact issue is so you have to rely on the recommendations you got
[OnePlus 9 Pro] lg-optimus:
Thank you both. I have to say, that I want to install crdroid on the Lemonadep.

I don't use Windows, but Linux-Ubuntu or Debian. I can organize a Win-Notebook if necessary. Is the Stock-ROM mandatory for going on?

So in which cases is ramdisk-recovery.img needed and when twrp-installer-3.7.0-12.1-8-lemonadep.zip

At the end I wand to have https://crdroid.net/apollon/9 installed, using the newest file from https://sourceforge.net/projects/crdroid/files/apollon/9.x/ Looks like newer files disappeared today, which yesterday existed.

For crdroid the following files exist: https://sourceforge.net/projects/crdroid/files/lemonadep/9.x/firmware/ I assume this is a fw-file? should be installed too with crdroid, but when.

As I undestand it, I should start with

fastboot boot boot.img

And then, there is the download link in the top of this thread, which is a zip file. Do I need to unpack this zip file?

Please tell me the steps exactly which I have to do.
[OnePlus 9 Pro] der_akinator:
If you just want to install crdroid it's best to follow the instructions from this thread:

https://xdaforums.com/t/rom-13-oos-cam-op9pro-crdroid-v9-5-09-06-2023.4511627/unread

BTW your crdroid links are for another device and you should only download from this page:

crDroid.net - Download crDroid v9 for OnePlus 9 Pro (lemonadep)

official crDroid v9 for OnePlus 9 Pro (lemonadep)

crdroid.net

Running "fastboot boot boot.img" just loads TWRP into ram, without any modifications to your device. From there you can do all the TWRP things and also permanently install it. twrp-installer-3.7.0-12.1-8-lemonadep.zip is only needed if you want to install TWRP from any other recovery or from a userspace app (see installation options 1 and 2).

For more information about ramdisk-recovery.img read this post:

https://xdaforums.com/t/recovery-3-...-a13-encryption-support.4523857/post-88474771

Edit:

If you have problems with fastboot, you have to add your user to the "plugdev" group on debian systems. You can read more about this in section "How to use MTP, adb and fastbootD" of first post.
[OnePlus 9 Pro] shadabkiani:
If you wannna flash crDroid, you don't need TWRP. Read the instructions on crDroid thread and you will see that you have to flash through adb sideload from the recovery image provided by crDroid. I must point out the fact that in OnePlus 9 (and all modern phones now) there is no dedicated recovery partition. Instead, recovery now resides inside boot.img. So thats why crDroid (and other ROM) instructions ask you to flash boot.img (along with dtbo.img and vendor_boot.img).
[OnePlus 9 Pro] lg-optimus:
There I started and now I am in this discussion. But maybe you see, what I did wrong:

fastboot --version
fastboot version 34.0.3-10161052

So the platform-tools were the newest about 1 week before.

fastboot oem unlock
OKAY [ 0.035s]
Finished. Total time: 0.035s

then:

fastboot flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.600s]
Writing 'dtbo' OKAY [ 0.054s]
Finished. Total time: 0.683s

fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (196608 KB) OKAY [ 4.753s]
Writing 'vendor_boot' OKAY [ 0.467s]
Finished. Total time: 5.268s

I see no problems.

Then I downloaded from https://twrp.me/oneplus/oneplus9pro.html the file twrp-3.7.0_11-0-lemonadep.img and renamed it.

fastboot boot twrp.img
Sending 'boot.img' (196608 KB) OKAY [ 4.644s]
Booting OKAY [ 0.443s]
Finished. Total time: 6.956s

Looks still good, doesn't it?

Note, I flashed the official version and not the xda-twrp. Maybe this was the problem.

Errors, but it says twrp flash complete.

View attachment 5932203

Then I didn't find the Option “Fix Recovery Bootloop”. Maybe TWRP from XDA is needed.

View attachment 5932205

View attachment 5932207

Then I shut down TWRP and started the phone again with the buttons and i ended, that there is only fastboot mode.

I never noticed problems. "fastboot devices" always worked. I have flashed more than 10 Xiaomi phones without problems, the newest is MI 10T Pro Apollo. Looks like the partitioning is different to OP 9Pro. The Apollo belongs to devices with a dedicated recovery partition (non-A/B), so there is no need to flash twrp into RAM first with Apollo.

Not sure, if I understand this correctly.

Can I do

fastboot boot boot.img

Then

fastboot reboot recovery

If that doesn't work, which buttons should I try?

Assuming, I started TWRP in RAM now, should I flash then:

twrp-installer-3.7.0-12.1-8-lemonadep.zip

You write it is only needed, when... But is it wrong to do it?

Do I have to restart recovery then?

Is the next step to install the custom rom?

There was something strange, when I wrote the post above, but didn't find out what was wrong. Locally I have crdroidandroid-13.0-20230612-lemonadep-v9.5.zip I hope this is a correct file.

Thanks, but I have no adb-access anymore, there is only fastboot. See the screenshot above
[OnePlus 9 Pro] shadabkiani:
It seems you don't read properly what we are telling you, do you? You DO NOT need TWRP to flash crDroid...... Follow crDroid thread, read the instructions properly, then you will understand.... Forget about TWRP if your only purpose is to flash a ROM....
[OnePlus 9 Pro] shadabkiani:
@der_akinator I see that in the latest folder 23-05-16, you have removed the OnePlus 9's unified recovery. Was there a problem? I remember it worked fine on my device, which is OP9. I still have it downloaded, but I just wanna know if there was an issue since you removed it.

Secondly, I would like to make a humble suggestion on the thread title. It currently says 3.7.0-12.1 but the recovery has been updated to 3.7.0_12-8. Also notice the _ and -. It would be better if written correctly, in my humble opinion.

P.S. I just downloaded boot.img from 23-05-16, and it worked too. Previously, it wouldn't work so you compiled and uploaded a separate version for OP9 for testing. So have you now fixed the main boot.img, and that's why you removed the test one?
[OnePlus 9 Pro] der_akinator:
Sorry for the confusion. After I got conformation that the boot images in lemonade-test work, I moved it to 23-05-16. That boot image now works for OOS 12 and 13 firmware and also on pro and non pro. There are no changes to twrp, just the kernel that is used to temporarily boot
[OnePlus 9 Pro] shadabkiani:
Awesome. So now we have finally got the truly unified image (excluding A11; who cares about that anyway?! :cautious:). Also, I noticed you updated the thread title too. Really appreciate it.
[OnePlus 9 Pro] Thomas.swe:
I installed this twrp with method 1. and now i can't sign in to my google account that require Yubikey, the fido2 test page from yubico fails too. I had to use another device to sign in to Google on my phone.
[OnePlus 9 Pro] shadabkiani:
Are you rooted? Is SafetyNet test passing?
[OnePlus 9 Pro] Thomas.swe:
Yes and yes
[OnePlus 9 Pro] shadabkiani:
I thought it was because of SafetyNet failing, but since you are rooted and must have already fixed the SafeyNet, I can't think of anything else. Maybe OP will see your post and come up with a solution.
[OnePlus 9 Pro] osm0sis:
Are you using Shamiko? Have you added those failing apps to DenyList? Have you changed the TWRP folder location under Advanced? Are you using Storage Isolation root app on the failing apps? All these things prevent detection, and there's nothing to be done from the TWRP developer's side.
[OnePlus 9 Pro] Thomas.swe:
There is no failing apps. The Google hardware key screen loads forever and the yubico webpage fails. I'll post some screenshots later. Worked before twrp. Edit: yes I have Shamiko and when installing with option 1 there is no advanced options.
[OnePlus 9 Pro] osm0sis:
What do you think the Google hardware key is checked in? What do you think the webpage runs on? Apps. Failing apps. Hide root/TWRP from them appropriately and it'll probably work.
[OnePlus 9 Pro] Thomas.swe:
Have any one got hardware keys like yubikey to work with this twrp?
[OnePlus 9 Pro] Thomas.swe:
I'm hiding everything that don't need root but Google services framework don't want to be hidden. When I go out of magisk deny list and back it's unchecked. No sure if that was hidden before I installed twrp. Any thoughts?
[OnePlus 9 Pro] osm0sis:
It might be one that USNF keeps off the DenyList because it spoofs it on-the-fly.

Have you done Change TWRP folder yet? That's what Pokemon GO looks for, for example. I changed mine to /sdcard/Recovery and PoGO works, you can also use Storage Isolation on PoGO and it can't find /sdcard/TWRP anymore and works too. That's probably what your issues stem from.

You can also test that theory by deleting /sdcard/TWRP while booted, rebooting the ROM and trying your apps again.
[OnePlus 9 Pro] Thomas.swe:
I deleted the twrp folder and restarted. Still the same.

Edit: I also tried the yubikey with otg adapter and it doesn't register at all anymore
[OnePlus 9 Pro] der_akinator:
I never used a yubikey and I don't have a clue what the problem might be. If it's due to some file checks, you might also want to delete /data/recovery. You can also test the safetynet-fix fork by Displax, which can be used to pass checks related to google play.

GitHub - Displax/safetynet-fix: SafetyNet & Play Integrity API workarounds for Magisk

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com
[OnePlus 9 Pro] Thomas.swe:
Ok. It's not a big deal right now. Already using Displax fork
[OnePlus 9 Pro] kdrv3xc:
edit: nvm
[OnePlus 9 Pro] TheGhost1951:
Anyone on TMO A13 that installed this TWRP have any success in reverting back to stock boot img?
[OnePlus 9 Pro] shadabkiani:
You need to have stock boot.img backed up. If you didn't back up and flashed TWRP permanently, I don't think you can just revert back to stock. TWRP doesn't back up stock boot.img when you flash it permanently, unlike Magisk which backs up if you choose Direct Install.
[OnePlus 9 Pro] TheGhost1951:
I did an MSM read back after updating to A13. So I have the stock boot.img. But flashing it to get back to stock causes phone to freeze at OnePlus logo.
[OnePlus 9 Pro] der_akinator:
Does this action extract the boot image from device or just from the payload bundled with MSM?
[OnePlus 9 Pro] shadabkiani:
Are you sure that you read back the active slot boot.img? Did you run OTA update after you backed up through MSM? Seems to me that your backed up boot.img isn't for current firmware.
[OnePlus 9 Pro] TheGhost1951:
Yes, did all the correct backups. I was able to restore stock recovery through temp booting TWRP. However, trying to "fastboot boot magisk-patched or stock boot images" ends up with being frozen at OP boot logo. Tried fastboot flash boot_a stock_boot.img fails with being frozen at OP boot logo. OS13 is a weird animal because didn't have these issues with OS12 or OS11. Has to be something new with OS13. Previously I was able to take OTA updated with unlocked bootloader, rooted with Magisk but not on OS13. Go figure!
[OnePlus 9 Pro] shadabkiani:
There has to be something wrong with your boot.img. If it's correct, it should boot up. I have restored and unrooted a number of times on A13. Anyways, whatever the case, next time you decide to root, don't flash the patched boot.img. Instead boot it, and then from Magisk app, use Direct Install option. Magisk will automatically backup the stock boot.img and you can restore it later from Magisk. Secondly, I strongly recommend against having TWRP flashed permanently, my reason has always been the current predicament of yours. If you wanna use it for whatever reason, just boot it and use.
[OnePlus 9 Pro] TheGhost1951:
Agreed, I'm just trying to understand and find solutions for problems that will help others... 🙂
[OnePlus 9 Pro] TheGhost1951:
You are correct, I had found and downloaded an A13 TMO flash able firmware, used the boot.img from it and it worked. Thank you for such a simple solution. Now that that is done and no root and stock boot and recovery, OTA 13.1 still has installation problem... Trying to figure that out.
[OnePlus 9 Pro] shadabkiani:
What is your variant? LE2117?
[OnePlus 9 Pro] TheGhost1951:
LE2127
[OnePlus 9 Pro] shadabkiani:
You said you booted the stock boot.img, right? Well, you since that boot.img worked, you need to flash it too in order for OTA to succeed.
[OnePlus 9 Pro] TheGhost1951:
I flashed to both a and b.
[OnePlus 9 Pro] Mohdfazrin:
Support me pleas
[OnePlus 9 Pro] mustangtim49:
Right?
[OnePlus 9 Pro] TheGhost1951:
Support you how?
[OnePlus 9 Pro] shadabkiani:
Financially I guess :ROFLMAO::ROFLMAO::ROFLMAO:
[OnePlus 9 Pro] osm0sis:
Could be emotionally 😛
[OnePlus 9 Pro] ffejy462:
Hopefully not athletic...
[OnePlus 9 Pro] Gersp52366:
Hello I have oneplus 9 in trwp does not work screen on android 12 is there any solution to this problem?
[OnePlus 9 Pro] shadabkiani:
Use older build with A12 support. You will see that in the filename. Latest builds are only supported on A13.
[OnePlus 9 Pro] der_akinator:
Which ROM and TWRP version do you use? I would recommend using the 23-05-16 build from this thread, which should work with A12 and 13. The official builds don't support A12 and onward.
[OnePlus 9 Pro] Gersp52366:
не работает
[OnePlus 9 Pro] shadabkiani:
Use the one with oos12-firmware name from 23-03-14
[OnePlus 9 Pro] der_akinator:
I was able to reproduce it with OOS12 and fix it. I didn't caught that when I did my tests with LOS 20 + OOs12 firmware. After testing it with A13 ROMs, I will provide an update.
[OnePlus 9 Pro] der_akinator:
Update

improve OOS 12 support

fix bug where vibration is disabled when vendor is mounted and odm not

fix bug in fastbootD that prevents flashing of modem of currently used slot

I tested this new build with OOS 12 and latest crdroid.

23-08-06 - Google Drive

drive.google.com
[OnePlus 9 Pro] TheSayaMan:
Link is broken
[OnePlus 9 Pro] osm0sis:
Works for me 😯
[OnePlus 9 Pro] andi_79:
its working perfect on OP9 with Oxygen 13.1
[OnePlus 9 Pro] solar666:
For me it is not working as well but I observed the same gdrive download problem recently for other provided links as well ... Not sure what's going on here.

Btw. I am logged into Google account, so thats not the point of issue
[OnePlus 9 Pro] TNSMANI:
There is no problem with the link. Even without logging into my Google account, I am able to download.
[OnePlus 9 Pro] der_akinator:
It looks like Google changed their website layout. If you hover over the blank space on the right side next to the file size column, a download button appears. And sometimes files get additionally zipped so you have to decompress them.
[OnePlus 9 Pro] solar666:
Correct, switching to desktop mode on the mobile gives access to the three dots menu on the right side and finally allows downloading the file ... Strange that just following the link and clicking download is not working anymore as before on the mobile
[OnePlus 9 Pro] der_akinator:
I'm not really sure which tutorial you are referring to, but just follow the official LOS installation guide. After that you can install Magisk and TWRP if you want.

You probably have no access to a recovery, because boot, vendor_boot and dtbo don't match, so the kernel can't boot up. If you have flashed vendor_boot and dtbo from the official LOS guide, you should also flash LOS recovery to the boot partition. You also can go with TWRP, but it adds just more steps.
[OnePlus 9 Pro] TheGhost1951:
The boot.img available is the recovery mentioned in instructions....
[OnePlus 9 Pro] shadabkiani:
Why do you wanna have TWRP permanently flashed anyway? Just have a working phone with whatever ROM, and if you ever feel the need to use TWRP for whatever reason, just temporarily boot it with fastboot boot <your_image> and use it. You don't need TWRP anymore to flash ROMs for OnePlus 9. I don't suggest having it permanently flashed.
[OnePlus 9 Pro] TNSMANI:
@drwingman1

You have already created a thread HERE asking the same questions before posting post #731 above. Please understand that we do not want clutter in XDA which is already huge. This also violates Rule 5:

Hope you understand and continue to post your queries in the other thread instead of posting in both.
[OnePlus 9 Pro] benhidalgo:
When you get back to oos13 with unlocked bootloader try this.

Fastboot to TWRP and install the current version then reboot to TWRP.

Wipe and format data

Install dtbo in a/b

Install vbmeta.img in a/b

You can also install the super empty system, your choice.

Install any AOSP - lineage, crDroid, nameless...

Reboot to TWRP

Install any other zips of your choice - magisk, kernel, gapps....

Wipe davisk

Reboot to system

You should rule the world after.
[OnePlus 9 Pro] TheGhost1951:
Almost looks like he is flashing the wrong firmware for the device he has. Obviously he is doing something wrong.
[OnePlus 9 Pro] TheGhost1951:
the uninstalling instructions in post 1 didn't work for me. Flashed boot.img to bot slots and it hung on oneplus logo..... just an FYI

OP(P LE2127 stock TMO.
[OnePlus 9 Pro] shadabkiani:
You have TWRP permanently flashed and now you wanna remove it? You have you flash your currently running ROM's boot.img in order to get rid of TWRP.
[OnePlus 9 Pro] TheGhost1951:
Yes I did have TWRP installed, however, I needed to flash a file in fastbootd mode and TWRP doesn't support that. So I followed instructions in the first post and flashed stock boot.img to boot_a and boot_b. But the device then froze at the OnePlus logo....
[OnePlus 9 Pro] Nimueh:
How did you sort it? In case I ever want to uninstall TWRP lol ;)
[OnePlus 9 Pro] kjslabber:
I think you have to flash boot dtbo and vendor_boot imgs to get back stock recovery.
[OnePlus 9 Pro] benhidalgo:
☝️👆 this will work.

You can also flash the OOS13 fastboot rom.
[OnePlus 9 Pro] shadabkiani:
He hasn't yet.

But if you ever flash TWRP, and later you decide to get rid of it, you simply flash the original boot.img of whatever ROM/firmware you are running. Recovery doesn't have a separate dedicated partition in OnePlus 9. It resides inside boot.img.

By the way, I would strongly recommend against flashing TWRP permanently. If for whatever reason you wanna use TWRP, you can temporarily boot it by the command fastboot boot <your_image> and do the stuff you want and then reboot. TWRP won't be flashed permanently in that case.
[OnePlus 9 Pro] Nimueh:
Thanks for the guide :)

But I prefer keeping TWRP installed, that way if I need it (say due to a bootloop if an updated Substratum overlay or something else caused issues) I already have it and don't have to mess around much. :cool:
[OnePlus 9 Pro] TheGhost1951:
It has been hit and miss. I was able to while rooted to delete all of TWRP from data/recovery folder then uninstall magisk, then flash to stock boot.img to boot. But I haven't nailed it down to an exact science yet.... I have had to temp boot TWRP and do a restore from a TWRP backup. If and when I get the exact steps, I will gladly post them.
[OnePlus 9 Pro] Nimueh:
Yikes, that sounds like TWRP is pretty hard to get rid of. I wish I'd have known that earlier, but I never had the need to uninstall it. Only after fastbootD failed (for flashing that orange screen abl file) did I even consider it, but since Firmware Flasher worked I kinda ignored the fastbootD issue.

Good luck on getting it worked out, looking forward to your findings 🤞 :)
[OnePlus 9 Pro] osm0sis:
This is not my experience. TWRP is only in the boot image, so if nothing else was modified that's all that needs to be flashed. (A custom kernel like blu_spark might modify vendor_boot and vendor_dlkm as well and that's trickier to reflash, maybe needing ROM dirty flash, but unrelated to TWRP and TWRP on its own doesn't touch anything but boot partition.)

As for the abl.img file, you can flash it via command line in TWRP or while booted to rooted ROM without any need for fastbootd. I think it's technically a flash critical partition which can be flashed in normal fastboot if you unlocked critical. My FlashAfterUpdate addon.d-v2 script was updated to flash partitions as well, so between that, my TWRP A/B addon.d-v2 script, and NikGapps, I can just Lineage OTA and forget. 😁🤘
[OnePlus 9 Pro] der_akinator:
I think you are flashing a wrong boot image, that is incompatible with vendor_boot and dtbo. You can either try to find the matching boot image or also flash vendor_boot and dtbo from the same source. Since it's pretty complicated for TMO users to get original images, I added a disclaimer to the installation section a while ago.
[OnePlus 9 Pro] TheGhost1951:
Yes, I believe you are right. After updating again to A13, I used fastbootd to flash my wife's param.bin to remove the MSM targeted IN. Then did an MSM read back and will use the boot from that. You would think a TMO A13 boot.img from any source would work but apparently not! Oh me oh my.....😂
[OnePlus 9 Pro] TheGhost1951:
One more question I hope you can answer. For the sake of argument, you came from A12 to A13, which means your inactive slot is A12. Why do you need to flash stock boot.img to both slots when replacing TWRP? Wouldn't you be overwriting the A12 boot.img by doing so?
[OnePlus 9 Pro] der_akinator:
Yes, you are right, only the currently active slot has to be overwritten. I just left it out for simplicity and to make it more fail-proof, because I'm not sure if fastboot flash boot boot.img would always write to the currently active slot.

To check the active slot, the following command can be used:

fastboot getvar current-slot
[OnePlus 9 Pro] TheGhost1951:
Thank you my friend!
[OnePlus 9 Pro] TheGhost1951:
I understand your reasoning now, if a person doesn't know what slot they are on, flashing to both covers them either way....👍