Database Users

Phone bricked, cannot flash because it randomly plugs/unplugs when connected to PC

Hey, first time posting here but a long time lurker. Amazing community from what I've experienced.
Yesterday, my phone bricked out of the blue, not turning on and showing a rapidly blinking LED. It refuses to charge, and when plugged to a computer, it displays in the device manager as a Qualcomm 9008 device.
So far I've tried unplugging the battery once, holding down the power button for three minutes straight, holding down volume- and power button, and none worked.
Apparently, flashing the phone seems to work for a lot of people, but I cannot do it because my phone randomly disconnects and then reconnects to my computer, repeatedly. This happens every 20 seconds or so.
I've tried using different ports, uninstalling then reinstalling drivers, resetting my PC, using a different cable, but nothing helps.
I've got a big trip tomorrow, and I don't want to go away with a dead phone. What can I do?
Update: tried cleaning the phone's USB port and the USB itself, no luck.

You got into EDL mode, search for guides how to use it (basically install correct drivers, flash ROM, reboot).

_mysiak_ said:
You got into EDL mode, search for guides how to use it (basically install correct drivers, flash ROM, reboot).
Click to expand...
Click to collapse
I know it's in EDL mode and I've looked into every single guide I could find, that's why I'm posting here.
Nothing so far has worked and I'm trying to flash the phone to see if it works, since an user here posted a youtube video of someone using MiFlash to get the phone back working.
The issue is that my phone has micro-disconnects when USB plugged to my computer every 20-30 seconds, and because of that I cannot flash it.

Do you have correct drivers installed? Fastboot mode reboots after ~30s if there are no drivers installed. Might be the same for EDL.

_mysiak_ said:
Do you have correct drivers installed? Fastboot mode reboots after ~30s if there are no drivers installed. Might be the same for EDL.
Click to expand...
Click to collapse
I downloaded them from xiaomigeek (cannot share the link due to post count), as suggested in another thread.
Also I tried installing them automatically through Windows device manager, but I still have the same issue.

Hm, don't know then.. Maybe someone else experienced something similar and can help.

Small update, cleaning both the device and the USB ports with a brush and alcohol does nothing to prevent the "micro-disconnects".

KurisuSama said:
Small update, cleaning both the device and the USB ports with a brush and alcohol does nothing to prevent the "micro-disconnects".
Click to expand...
Click to collapse
Buddy those disconnects are not because of dirty port.. cleaning wont help..i actually had this problem with my first gen android phone it disconnects every 5 secs.. but once i hit flash in sp flash tool(mtk flasher) it stops disconnecting and starts receiving rom packets without problem

apexashwin said:
Buddy those disconnects are not because of dirty port.. cleaning wont help..i actually had this problem with my first gen android phone it disconnects every 5 secs.. but once i hit flash in sp flash tool(mtk flasher) it stops disconnecting and starts receiving rom packets without problem
Click to expand...
Click to collapse
Any resources where I could try this on the Mi A1?
Edit: correct me if I'm wrong, but after a bit of searching it seems I'm not unable to find a guide because there isn't one, but because sp flash tool isn't compatible with my phone.

Use another pc may be. Or another USB cable

.:Addicted:. said:
Use another pc may be. Or another USB cable
Click to expand...
Click to collapse
Tried both.
The cable doesn't seem to be the issue as a different cable yields the same results and another phone I've tested doesn't have any issues with it.
And I tried doing this on my laptop instead of my desktop PC, then on my roomate's PC, but the same thing happens.

KurisuSama said:
Any resources where I could try this on the Mi A1?
Edit: correct me if I'm wrong, but after a bit of searching it seems I'm not unable to find a guide because there isn't one, but because sp flash tool isn't compatible with my phone.
Click to expand...
Click to collapse
Sp flash tool is for phones with mtk CPU's only brother.. could u try different pc? Or try flashing via cmd?
---------- Post added at 04:25 AM ---------- Previous post was at 04:21 AM ----------
Btwn have u tried flashing the phon via miflash? Or u didn't cuz it disconnects? Well what happened to me is *I didn't even try to flash the phone with sp flash tool for 5 straight months cuz i thought its impossible to flash when it disconnects like this...but when i finally consoled myself to give it a try it flashed all the way to 100% without any problem..uh the phone stops disconnecting once the software pushes few packets to the phone

I have the same problem :/
If take to warranty they ill help or not?

Go into edl mode. Edit xml file that store info about partitions. Select few necessary. (like bootloader & idk about what other partition needed for sure, but just telling you to exclude big partition like system. You do your research on that. May be cosmicDan can tell you what partition you need to enter fastboot)
Im hoping you will be able to flash small partition.
So you can get into fastboot. Then try to boot twrp in fastboot to flash all partition from twrp image shared in xda. (May be use memory card & flash twrp image from there)
Good luck

this help me without remove battery http://en.miui.com/thread-1680467-1-1.html
i install driver qualcoom, after flashed rom and after i hold button power and work

HELP! I flashed twrp installer

I flashed twrp installer and magisk but now everytime i reboot my phone, it reboots all the way but right as it finishes booting and shows the lockscreen it says powering off. Please help i hope i didnt mess up my phone.

I tried restoring and it had an error now it wont boot past fastboot mode omg help please!!

Use the MSM tool. I had to do that, too, and it saved me!

bigmikey307 said:
I tried restoring and it had an error now it wont boot past fastboot mode omg help please!!
Click to expand...
Click to collapse
link for help: https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448

bigmikey307 said:
I flashed twrp installer and magisk but now everytime i reboot my phone, it reboots all the way but right as it finishes booting and shows the lockscreen it says powering off. Please help i hope i didnt mess up my phone.
Click to expand...
Click to collapse
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.

No, I already tried that msm tool. It doesn't recognize my device. Probably because my device was on 9.0.10 or 9.0.6...im not really sure bc I tried restoring with a backup from 9.0.6 while I was on 9.0.10. But my computer did recognize it while it was in Qualcomm Download mode so maybe the toll just needs to be updated?

This happened to me when I upgraded from 9.0.7 to 9.0.10. When I booted into TWRP, all my internal storage was encrypted, so I couldn't flash the OS again from there. I tried to wipe just the data and dalvik/cache in a hope to fix it. Don't do this as my internal storage got wiped (most likely due to the encryption). I had to download and reflash the OS through OTG with a pendrive in the end. Possibly try to do that first if you have access to it instead of wiping the phone.

bigmikey307 said:
No, I already tried that msm tool. It doesn't recognize my device. Probably because my device was on 9.0.10 or 9.0.6...im not really sure bc I tried restoring with a backup from 9.0.6 while I was on 9.0.10. But my computer did recognize it while it was in Qualcomm Download mode so maybe the toll just needs to be updated?
Click to expand...
Click to collapse
Msm doesn't need update. It's meant to work with phone off just pressing volume up I think, whatever version/type of ROM there is in it. Phone is recognized as a Qualcomm modem by the computer. Read carefully how to use it. It will restore a full out of factory 9.0.5 then you'll update it as usual.

Striatum_bdr said:
Msm doesn't need update. It's meant to work with phone off just pressing volume up I think, whatever version/type of ROM there is in it. Read carefully how to use it. It will restore a full out of factory 9.0.5 then you'll update it as usual.
Click to expand...
Click to collapse
Ok, then if it should work, it isn't working with my device. It's not recognizing it. I tried both msm tools, the T-Mobile one and the regular one and my device just isn't showing up on the tool

bigmikey307 said:
Ok, then if it should work, it isn't working with my device. It's not recognizing it. I tried both msm tools, the T-Mobile one and the regular one and my device just isn't showing up on the tool
Click to expand...
Click to collapse
Power off device then hold volume up & volume down at same time then plug into PC it may take a second but it will recognize it

twinnfamous said:
Power off device then hold volume up & volume down at same time then plug into PC it may take a second but it will recognize it
Click to expand...
Click to collapse
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.

bigmikey307 said:
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
Click to expand...
Click to collapse
I was on windows 10 and I had to unplug and plug in a few times and I could only use the USB 2.0 port. It wouldn't work in USB 3.0 port. That's about what I remember

twinnfamous said:
I was on windows 10 and I had to unplug and plug in a few times and I could only use the USB 2.0 port. It wouldn't work in USB 3.0 port. That's about what I remember
Click to expand...
Click to collapse
Ok thanks, I'll keep trying

H4X0R46 said:
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
Click to expand...
Click to collapse
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!

bigmikey307 said:
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
Click to expand...
Click to collapse
Glad to hear u got it fixed

bigmikey307 said:
It's working now! That msm tool wasn't working for me so I found an all in one tool and I I flashed a whole new rom and it didn't work at first but I tried again and it worked. I tried using adb to flash it but it would boot any imgs but that tool worked!
Click to expand...
Click to collapse
Hi I flashed the installer by mistake once.
The solution is to flash the stock boot image in both slots.
Worked fine for me.

bigmikey307 said:
Yes, I know how to read directions. I'm telling you it didn't recognize it. The drivers are installed and it's recognized in device manager but it's not showing up in the tool.
Click to expand...
Click to collapse
Umm.. That's probably what you did, but make sure to get the driver automatically via internet. If that doesn't help, perhaps a different pc/port/cable will do the trick (different pc worked for me).

H4X0R46 said:
Just out of curiosity, report back if that MSM tool worked for you. Never tried it myself because I've never bricked this phone, but curiosity.
Click to expand...
Click to collapse
I've had to use that tool twice for doing stuff the phone didn't like, testing etc. Saved my bacon both times
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app

Hard Bricked 6T (No TWRP, OEM locked, MSM not working)

Hello dear community,
I've been playing with my 6t for a long time, hundreds of custom roms, kernels, etc..
Lastly I went to official oxygen 10. I tried to install twrp via fastboot but every time I tried to push the files, I would get a error. I reinstalled drivers, tried different ports, different tools..
I got mad and blindly followed some article where someone suggested putting "persist" in the fastboot command, I tried it, I thought it is some kind of "force push" the file and that is how I probably corrupted persist partition. DUMB
Phone not booting of course and I went to restore it with Msmdownload tool.
It did not fixed it.
I tried different versions of msm, I tried going to Hydrogen, tried different USB ports, tried type C ports, different PCs...
No luck, phone is stuck at bootloop, with no TWRP and bootlocked.
I read somewhere that Msmdownload tool is not flashing persist partition and I assume that is the reason why my phone can't be restored.
Fastboot commands are not working anymore and EDL mode is probably the only possible way to communicate with the device.
I live in Montenegro and I can't send phone to oneplus to repair it.
I searched the threads and noticed that some users with similar problem eventually succeed to restore the phone by flashing it with Msm multiple times. I am still trying to do it but no luck.
I would really appreciate help from dev mastermind.
Thank you!

If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
But maybe i'm wrong and someone else know the sollution.

Deurklink73 said:
If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
Click to expand...
Click to collapse
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...

Papagaj said:
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...
Click to expand...
Click to collapse
You are correct. Msm tool will work on locked bootloader.

Man that sucks. Seems like you might be screwed. I screwed up a couple times getting to A10 but I was able to get msm tool to work for me. You are using it while your phone is powered off, correct?

Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool

GeekMcLeod said:
You are using it while your phone is powered off, correct?
Click to expand...
Click to collapse
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...

jamescable said:
Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool
Click to expand...
Click to collapse
I tried several versions. I was hoping to find Android 10 tool for oneplus 6t but it is still not available.

Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead. Not saying that it would work for you but it might. In my case it was a Qualcomm tool. If you still end up with nothing but dead ends today, I'd initiate a chat with OnePlus on this page (select your country at the bottom of the page first).
Wrapped with delicious Fajita [emoji896]

The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.

Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.

amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.
Click to expand...
Click to collapse
@Papagaj do this....thats the only fix....I purposely wipe persist for to test something and I did that to recover from the boot loop.. persist store sensor information that vital to getting phone to boot....that's why it not booting..kernel is look for the sensor info but can't find it

Timmmmaaahh said:
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead.]
Click to expand...
Click to collapse
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
8.- If you have an IMEI backup, just follow this guide
Click to expand...
Click to collapse
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
GeekMcLeod said:
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.
Click to expand...
Click to collapse
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.

Papagaj said:
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Nope....just rewrite you IMEI with a Qualcomm tool..quite a few available

Papagaj said:
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Oh. The few times I used it I just powered off my phone and connected it to my computer. Started msm tool and it did its thing.

Papagaj said:
this A/B partitions really gave me headaches
Click to expand...
Click to collapse
You and me both! ? lol...

I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.

All right, here is the situation.
I finally managed to boot up the phone. amt911 gave working instructions on post #10. Thank you bro, you are awesome, and Thank you Tech_Savvy for confirming the method, you are badass who deletes partitions just for fun!
All right I got the phone booted up but as amt911 mentioned, I lost my IMEI numbers, without IMEI numbers you can't dial numbers, receive calls or use mobile data.
BACKUP IMEI NUMBERS FOLKS, you never know when the partitions will screw you over!
I was dumb one without backup and I had to contact Oneplus support for help. I was suprised how quickly I got into communications with one of the assistants.. in less than 10 seconds.
They ask you to do full reset via stock recovery and some other basic troubleshoots, after nothing, obviously, fix the missing IMEI they will arrange remote session to get your phone fixed.
You have to persist on remote session as some of assistants told me that I have to send the phone to repair.
Before they arrange session for you, you need to show them "proof of the purchase" ALSO KEEP THAT FOLKS I lost mine long time ago but luckily I found photo of invoice I took when I bought phone, phew*
I didnt have it at first when I contacted them and they say there is nothing they can do without a proof! DON'T STEAL PHONES FOLKS and then ask for support...
They will contact me for session within 48 hours and I will share the experience here.
Thank you again people!

JTVivian said:
I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.
Click to expand...
Click to collapse
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.

Papagaj said:
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.
Click to expand...
Click to collapse
Ah you're right, i wasn't sure if that was the case but i thought i'd throw out the suggestion anyways.

Just another victim of the android 12 update, hoping for a revival

So im gonna start off by saying that im just some dumb 18 year old and have never actually posted to ask for help, only reading other peoples situations to try to figure out my own.
but introductions aside im just gonna jump in to everything wrong with my oneplus 8 pro (global)
I was on the OOS 12 beta for a while, ive been way too lazy to change it back since ive been occupied by other stuff.
I was using magisk and decided to do some fun shenanigans with it.
I get into bootloop after flying to close to the sun with modules - a common occurrence.
so I try to switch to a custom rom since I was gonna reset anyway.
I download CR droid's recovery and main rom, went into fastboot and flashed the recovery.
I notced that whenever my phone was plugged into the computer, the options would rapidly switch on fastboot's end
when I tried to boot to recovery after flashing, it would only return to fastboot
confused I thought that maybe the recovery was bad and try another rom, no dice
i submit defeat and go to msm tool to fix the issues
I get that "Sahara communication failed" error so I hold down the volume up + power for 13 seconds before trying again.
it flashed smoothly
after getting sad at all the bloatware that was on oxygen OS after a full reset, I get the motivation to try using a custom rom again, this time using a different rom.
same weird fastboot behavior
I was unable to go into recovery
I then tried downloading stock firmware to flash it manually
fixed nothing
I delete the boot and recovery partitions and flash them again, still no dice
I even make a partion called fart, before remembering that I do not know the partition structure of android so i Ctrl+C out before it makes the partition
I go back to msm tool again in shame
"Unknown Target Device"
I reinstalled drivers
switched computers and cables
changed the source of my drivers
nothing fixed this error
and every time I would try to do anything it would go directly back to fastboot.
I try reflashing partitions in this broken fastboot mode and it would only flash if I unplugged, selected reboot bootloader, and plugged it back in
I would then try to fastboot boot into TWRP or other recoveries i downloaded
they would shut off the phone
I remember a/b partitions exist so I switch over between them and try to flash stock OOS again
after more fiddling and nothing working, I noticed some more weird traits of fastboot
twrp did boot directly after switching my main slot, not specific which one just if the slot was changed.
the "this device has an unlooked bootloader" message did not appear
only on slot a would the oneplus logo show up on boot
again every option I would click would take me right back to fastboot.
I wait a day for the phone to die so I could use EDL that way, at this point the twrp method randomly stopped working so I couldn't go into edl that way.
"Unknown Target Device Param Preload"
and like I know Param Preload is a common error but nowhere could I find information on the unknown target device part.
the phone still vibrates if I hold the power and vol+
it just vibrates in a loop as if it keeps rebooting, probably fastboot just selecting the start key over and over when I hold it down.
vol- and power do nothing, and did nothing for the entirety of this story.
is there any chance of saving my poor instantnoodle professional?
## edit for people googling this
the problem I was having was that I didn't set the "target" button on the MSM tool correctly, so make sure its set to O2 or your appropriate reigon

1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.

xtcislove said:
1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.
Click to expand...
Click to collapse
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.

NatunaSushi said:
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.
Click to expand...
Click to collapse
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.

xtcislove said:
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.
Click to expand...
Click to collapse
after a week of fiddling I DID figure out the issue
unsupported Target unknown was refering to the fact that I had the MSM tool set to Target mode, which I assume tries to set the region according to what the current device has. After selecting that to O2 for the global models, the flash worked fine. I ended up coming across some C stock of a google pixel 3a and will try messing with that so I dont have to go a while without calls or texts. Glad to know I learned some bit of responsibility from this excursion.

Major help needed

OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?

SteveHebe said:
OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?
Click to expand...
Click to collapse
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.

I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?

HolyHog said:
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.
Click to expand...
Click to collapse
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?

SteveHebe said:
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
Click to expand...
Click to collapse
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

xtcislove said:
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I have current drivers, tried different machines, different ports and different cables.

SteveHebe said:
I have current drivers, tried different machines, different ports and different cables.
Click to expand...
Click to collapse
Is your phone regognized in device manager?

No, it is not

SteveHebe said:
No, it is not
Click to expand...
Click to collapse
Your phone boots ot fastboot and your pc does not regonize it? You need to make sure to install the drivers correctly imo.
Please read this sections carefully https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/