Develop Bugs

LG G4: TWRP Recovery not working

Dear folks,
today I ran into a problem while trying to root my new LG G4 (H815).
It seems I succesfully unlocked my bootloader since it writes "BOOTLOADER STATUS: UNLOCKED" at every startup.
Now I tried to install TWRP recovery; I downloaded the newest version for my device from the official TWRP website.
I used the following command:
Code:
fastboot flash recovery twrp.img
I got the following output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (31620 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 1.226s
Then I left fastboot via
Code:
fastboot reboot
.
But when I try to boot into recovery mode via
Code:
adb reboot recovery
I just get a picture of a broken android figure with a red triangle over its chest.
When I use the hardware key combinations and then answer "YES" it simply does a default factory reset.
I'm using elementaryOS 0.3 (based on Ubuntu Linux). I already tried different ways (with or without sudo, using the adb version which comes with the full Android SDK or the version featured in the Ubuntu repositories).
Nothing seems to work...
I hope I described my problem right and you can help me.
Thanks for all replys and greetings from Germany.
EDIT:
I now got into recovery using
Code:
fastboot boot twrp.img
.
From there I installed stock-20a-rooted.zip. That seemed to work. But when I boot the phone normally it just shows me the LG logo forever and doesn't boot into normal os. Only removing the battery gets it off again. Factory reset doesn't help either.

I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!

DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
I did that but now I get a bootloop while starting the normal os. Factory reset doesn't help.

Update: When I connect my device with my PC while the bootloop is active, sometimes a Window pops up on my desktop asking for my PIN to unlock it. When I enter it nothing happens.

Ouch...corrupt twrp.img file?
---------- Post added at 12:49 PM ---------- Previous post was at 12:42 PM ----------
So maybe its best to start all over again...get into download mode via holding volume up and Power on. Then install original kdz via LGUP tool. Maybe you have a look at the german Android Hilfe forum, there are also the kdz files for download. Good luck!

DerPedde said:
Ouch...corrupt twrp.img file?
Click to expand...
Click to collapse
Maybe... While in TWRP it looked like always...
EDIT:
Yes, I'm just downloading the KDZ files... Gonna flash it today. However, Thanks for your support!

I just succesfully installed autoroot kernel, flashing kdz was the solution. However, I still can't write TWRP into recovery partition, but at least I got what I wanted.
Thanks for your support!

you can write twrp by using twrp manager from playstore(2.8.7.0) then when you're IN recovery flash 3.0.0.0 (download from official twrp site or from orginal android development of LG G4) or use in adb fastboot boot (recovery).img

HELP!
DerPedde said:
I would suggest to put a copy of the TWRP recovery to your sd card. Then simply boot into the recovery via the command: "fastboot boot twrp.img" and then flash the copy of the recovery from sd card permanently via the so far only booted but not permanently flashed recovery...good luck!
Click to expand...
Click to collapse
Hi everybody. I'm a newbie in root, xda and forums in general, so please don't shoot me and help me if you can..
I rooted my lg g4 te first time thanks xda, but after having installed nougat via twrp, root is missing in any check, and twrp can be installed but not launched in fastboot. I tried EVERY guide i found in xda, but that famous command "fastboot boot something.img" is still not working... any idea?
Thanks

Help pleasee

Please help
I just updated my swift 1 to Nougat
Now i can't flash twrp
After flash it successfully
It boot the stock recovery not twrp

Hold 'volume-down' and 'power' for the restart after flashing, if you reboot into system, it will overwrite TWRP with stock recovery again.

So how i can boot to twrp
Thanks

Amr.wagde said:
So how i can boot to twrp
Thanks
Click to expand...
Click to collapse
If you press VolDn and connect USB, TOS111B Nougat Swift 1 boots into fastboot which has menu to boot into recovery.
However the twrp-3.1.1-0 cannot not mount f2fs /system, so you can backup/restore all but system. Of course you can always fastboot flash Nougat system. As mentioned, if you do not prevent it, original recovery will overwrite custom one upon system reboot.

Hi I'm very thankful for your reply
But I am i little bit newbie at fastboot
Can you please show me how to do that in steps ?

Amr.wagde said:
Hi I'm very thankful for your reply
But I am i little bit newbie at fastboot
Can you please show me how to do that in steps ?
Click to expand...
Click to collapse
I had a friend's Swift here yesterday. No longer today.
I recall:
Press VolUp and connect USB to computer -> boots into fastboot [-not- VolDn (my bad)]
inside fastboot is a menu to reboot (system or recovery or fastboot)
I think one should also reboot recovery with VolDn+Pwr
sorry to ask: Why do you need to boot into TWRP?
Also, system boot restores stock TWRP. You need to modify system to avoid it. Typically some
rc script copies the partition back so you need to find that script and/or rename the file.

Because i wanna to install linage because after updating to Nougat the touch is not working probably at portrait mode but on landscape it works fine
Example if i want to type hahahahaha
It type the letter between it "sdfsddf"

Code:
fastboot flash recovery twrp.img
After successful installation:
Code:
fastboot reboot
and immediately press and hold 'Volume-down' and 'Power' until your Swift has restarted.
If you want go switch to Lineage, proceed as described here:
https://forum.xda-developers.com/showpost.php?p=72261104&postcount=155

Amr.wagde said:
So how i can boot to twrp
Thanks
Click to expand...
Click to collapse
ok : initially you asked "boot to twrp"
but: it turns out now you want to "install twrp"
I was answering wrong question.
Or, did you already have twrp installed?
Note that even if you have on stock Nougat, it will be overwritten unless you prevent it.
Also note that even if it overwritten.
You may want to boot recovery from fastboot and it may end up in twrp.
I agree that's confusing but that's what I experienced yesterday.
Again I do not have the device here anymore.

Dior DNA said:
ok : initially you asked "boot to twrp"
but: it turns out now you want to "install twrp"
I was answering wrong question.
Or, did you already have twrp installed?
Note that even if you have on stock Nougat, it will be overwritten unless you prevent it.
Also note that even if it overwritten.
You may want to boot recovery from fastboot and it may end up in twrp.
I agree that's confusing but that's what I experienced yesterday.
Again I do not have the device here anymore.
Click to expand...
Click to collapse
Friend i made that but it load the stock recovery

Amr.wagde said:
Friend i made that but it load the stock recovery
Click to expand...
Click to collapse
perhaps try (assuming you already flashed stock nougat from fastboot):
reflash twrp from fastboot and reboot to it from fastboot menu (use volume button to change start to recovery)

Amr.wagde said:
Friend i made that but it load the stock recovery
Click to expand...
Click to collapse
can you confirm that you have done these steps:
Code:
fastboot flash recovery twrp-3.1.1-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16888 KB)...
OKAY [ 0.598s]
writing 'recovery'...
OKAY [ 1.686s]
finished. total time: 2.284s
fastboot reboot

Forgot pattern on Android 10 Beta

Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards

snOwjAwk said:
Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
Click to expand...
Click to collapse
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008

zfk110 said:
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
I tried to install twrp but ran into this error (on mac):
booting...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
EDIT:
Tried it from a windows pc now, got another error:
creating boot image...
creating boot image - 11765760 bytes
Sending 'boot.img' (11490 KB) OKAY [ 0.495s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed

You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img

Phalanx7621 said:
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Click to expand...
Click to collapse
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome

snOwjAwk said:
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
Click to expand...
Click to collapse
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out

zfk110 said:
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
Click to expand...
Click to collapse
Bootloader is unlocked! That's why im curious why it doesnt work...

snOwjAwk said:
Bootloader is unlocked! That's why im curious why it doesnt work...
Click to expand...
Click to collapse
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it

zfk110 said:
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
Click to expand...
Click to collapse
That's what I did... And there was no other USB device connected other than the pixel. Fastboot devices also only showed my device

How to make a backup with LineageOs recovery?

On an older phone I used TWRP recovery. That has a brilliant option to create system backups.
How to do that in the LineageOs recovery?
I want to clone one phone to another identical phone. I hope that can be done by creating a backup on phone 1 and install it from recovery on the other. Hopefully including the OS (with all the setting that take hours of fiddling about), apps and data.

Just use twrp..?

PhotonIce said:
Just use twrp..?
Click to expand...
Click to collapse
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.

carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp

carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Use twrp backup and select all the partitions. It'll back up everything.
Apps and settings are located in the data partition and other files/data is located in the internal storage partition. boot is the kernel, recovery is the recovery and system in the system image.
If you know what you're doing you could even install a fresh copy of lineage onto another phone and just restore the data and internal storage partitions, and still receive an exact copy of the phone you backup up from while using less space in the backup.

... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?

Paul_Neocube said:
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Click to expand...
Click to collapse
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.

PhotonIce said:
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
Click to expand...
Click to collapse
On my device there are two slots... A and B. Like two separate partitions that van have software installed to. When I installed my rom I first installed twrp to slot a and then my Tom to slot b which is what runs now when I power on my device. I can't install twrp to the slot my os is on as I would have issues with the os recovery that is on that slot.

Skorpion96 said:
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
Click to expand...
Click to collapse
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.

zogoibi said:
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
Click to expand...
Click to collapse
It's not. He keeps LineageOS recovery on the phone, and when he wants to use TWRP, he connects the phone to his computer via USB and runs fastboot boot twrp.img from the command line. This reboots the phone and loads TWRP into memory without flashing it to the phone.

@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?

zogoibi said:
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
Click to expand...
Click to collapse
actually i done the reverse, i have twrp installed and when i want to run lineage recovery i boot it with fastboot boot "recovery.img"

Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.

zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
You ever flashed TWRP via cmd (adb) on a pc? It's the same thing but you use fastboot flash rather than fastboot boot. When you flash twrp on phone, you put the recovery.img file in your adb folder, if I'm not mistaken. The same thing goes for booting an .img file (it goes in the adb directory/folder in your pc).

zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
The alternate recovery should remain on the computer. It can be in the same folder as adb and fastboot for easy access (it doesn't need to be there, it's just easier that way). That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.

MJPollard said:
That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
Click to expand...
Click to collapse
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.

zogoibi said:
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
Click to expand...
Click to collapse
Try fastboot boot recovery twrp.img. I don't normally do this so I might have misremembered it. If it works, I'll edit my post so that others don't get confused.

Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!

zogoibi said:
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
Click to expand...
Click to collapse
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.

agamemnonn said:
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
Click to expand...
Click to collapse
I found out that it's not possible. LOS Recovery's fastboot mode has that command disabled.

Question tried flashing a magisk boot img and now phone is stuck on black screen w/ logo. PLEASE HELP

So I tried flashing a boot img that was modded with magisk, and now the phone is stuck on a black screen with the oneplus logo. When I get into fastboot mode the computer does not recognize it when I type "fastboot devices". I want to flash it back to stock but I'm not sure how. I just got the phone not even an hour ago, and it's already ****ed up.
the command i used was:
fastboot flash boot_a '/media/boris/Downloads/lemonadep/magisk_patched-24306_C48.img'
target reported max download size of 805306368 bytes
sending 'boot_a' (196608 KB)...
OKAY [ 0.829s]
writing 'boot_a'...
OKAY [ 0.560s]
then I did the same with flash boot_b and it basically said the same thing. I am freaking out because if it can't recognize commands in fastboot mode, then I don't know what to do.
Any help would be GREATLY appreciated! I just want to flash to stock now so I can turn on the phone. At least the bootloader was unlocked without anything bad happening.
Thanks!

People need to stop flashing patched boot images, you're supposed to boot them instead and use them to direct install Magisk. This solves two problems - your phone won't brick, and you'll be able to restore the images with Magisk to take incremental OTAs.
You will likely need to use the MSM Tool to recover your phone. Check the How To Guide tag to find the one for your model.

On A12 when I try booting "boot.img" I get stuck in fastboot.. I always flash patched_boot.. But I ALWAYS use latest magisk canary download.. Also OP stated his command was
Fastboot flash boot_a "xxxxxxxxxxxxx"
you need to type fastboot flash boot "magisk_patchedboot.img

Shooter7889 said:
On A12 when I try booting "boot.img" I get stuck in fastboot.. I always flash patched_boot.. But I ALWAYS use latest magisk canary download.. Also OP stated his command was
Fastboot flash boot_a "xxxxxxxxxxxxx"
you need to type fastboot flash boot "magisk_patchedboot.img
Click to expand...
Click to collapse
Doesn't make any sense that you get stuck in fastboot when trying to boot the same image that you then flash... This is the proper way to install Magisk with the boot and direct install method and it works when it's done properly.

On The Go Repairs said:
u need to find download of whichever OS u we're on.. OS11.xxx or OS12(C48, or whichever it was) and get it on ur pc, there is thread in this forum that should have all stock boot and patch boot imgs of all different versions. So u don't have to download the whole zip and dump yourself. If u try rooting again u need to just "fastboot flash boot magisk_patchedboot.img." not _a and _b..
Click to expand...
Click to collapse

On The Go Repairs said:
So I tried flashing a boot img that was modded with magisk, and now the phone is stuck on a black screen with the oneplus logo. When I get into fastboot mode the computer does not recognize it when I type "fastboot devices". I want to flash it back to stock but I'm not sure how. I just got the phone not even an hour ago, and it's already ****ed up.
the command i used was:
fastboot flash boot_a '/media/boris/Downloads/lemonadep/magisk_patched-24306_C48.img'
target reported max download size of 805306368 bytes
sending 'boot_a' (196608 KB)...
OKAY [ 0.829s]
writing 'boot_a'...
OKAY [ 0.560s]
then I did the same with flash boot_b and it basically said the same thing. I am freaking out because if it can't recognize commands in fastboot mode, then I don't know what to do.
Any help would be GREATLY appreciated! I just want to flash to stock now so I can turn on the phone. At least the bootloader was unlocked without anything bad happening.
Thanks!
Click to expand...
Click to collapse
what rom are you on? OOS 12?
then you need to patch & flash boot. vendor_boot and reflash vbmeta

Thank you for the prompt responses! My computer can send commands to the phone now through fastboot mode, for a while it was going straight to fastboot mode but now after trying to flash stock, it again is stuck on the oneplus logo on boot. I am downloading the MSM tool now, hopefully it will work. And I was suprised that their isn't a United States version of the firmware, the closest match I have found is the "global firmware" so that's what I will use.
On my other phone (s10 lite) I was able to just flash a lineage recovery image, then install magisk through recovery. I wish it was this easy for oneplus but apparently it's way more complicated. I'm guessing the MSM tool is like Odin for samsung phones. I wish their was an official program that could factory reset the phone, the way samsung does it with odin, or how chrome can factory reset a google pixel straight off their website. oh well. I'm not going to give up just yet...

OnTheGoRepairs said:
Thank you for the prompt responses! My computer can send commands to the phone now through fastboot mode, for a while it was going straight to fastboot mode but now after trying to flash stock, it again is stuck on the oneplus logo on boot. I am downloading the MSM tool now, hopefully it will work. And I was suprised that their isn't a United States version of the firmware, the closest match I have found is the "global firmware" so that's what I will use.
On my other phone (s10 lite) I was able to just flash a lineage recovery image, then install magisk through recovery. I wish it was this easy for oneplus but apparently it's way more complicated. I'm guessing the MSM tool is like Odin for samsung phones. I wish their was an official program that could factory reset the phone, the way samsung does it with odin, or how chrome can factory reset a google pixel straight off their website. oh well. I'm not going to give up just yet...
Click to expand...
Click to collapse
MSM Tool factory resets the phone when it flashes. It's just like Odin only less complicated because once the device is in the right mode, you just click Start and don't have to deal with anything else (I would actually click Start before connecting the device though so it's looking for it, it only stays in edl mode for a few seconds before it tries to reboot so you can get a Sahara error if you aren't quick enough).
Global = USA basically.

I am unable to get the phone into EDL mode, or have it showup in device manager as qualcom whatever. I press both volume up and volume down with phone powered off, then plug in. I even set everything up on a new computer just so it wouldnt have any left over driver stuff from my samsung phone. No matter what I try, it does not show up under COM in the MSM tool. I'm kind of starting to freak out, cuz I just spent almost $450 on this phone, and right now it's useless. And originally it was running stock, (to the person who asked).

OK, it shows in my device manager properly as QUALCOM blah blah blah, but does not show in MSM tool. at least i'm making progress.
OK! I had to open the program while it was in EDL mode, now it shows properly and it is flashing. thank god! I just wish it wasn't so complicated to root this ************...

phone is now unbricked and I will be more careful with rooting from here on out. thank you for the help people! i'm going to try following the main root tutorial on the oneplus 9 pro forums and see how that goes. i tried booting (not flashing) with a magisk modded boot.img and it booted to a black screen (pretty sure edl mode interestingly enough), then I realized it wasn't the same version as what I was running, since the msm tool put it on an old version. i'm going to update to the latest before trying again.

So I followed this guide: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-48.4252373/
and I tried using the patched boot.img's linked on the page and they didn't work. Then I made one from scratch using the latest oneplus firmware and patched it myself, and voila! it worked! I'm pretty happy with this phone so far, although it's a pain in the ass to start over and set everything up again. Not having an sd card sucks, but oh well.. I will try flashing a custom rom at some point when I get bored.