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/
Related
My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.
Bad cable or need to reinstall drivers...
marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.
Say sth more about your phone state and history...
marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
I've no idea how to help you... Sorry.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.
Is yours 722?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.
gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.
So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium
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.
Hello, I flashed a firmware update through a modified recovery and now phone doesn't boot. It doesn't even show the logo, seems completely dead.
I've tried all combinations of keys, none work; if I push vol+ & vol- and connect it to pc nothing happens, it's not detected by windows or MSM Tool
Could anybody help me?
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using international tool or India while using indian tool or EU when using european tool.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
If this does not work, plugin your device and hold vol-,vol+ and power for a long time.
Make sure that you have qualcomm drivers etc installed.
Win11 can cause problems.
I think I didn't make myself explain correctly; the phone is off and I can't make it switch on. I already tried to enter EDL mode with vol+ and vol- pushed, but the phone is not detected by windows nor by msmtool.
Hammerhand.17 said:
I think I didn't make myself explain correctly; the phone is off and I can't make it switch on. I already tried to enter EDL mode with vol+ and vol- pushed, but the phone is not detected by windows nor by msmtool.
Click to expand...
Click to collapse
You did explain yourself correctly. I had the same problem and by pressing buttons i somehow entered edl mode and it was working.
I think it worked that way for me:
I started MSM tool, changed to eu and pressed start. Than i connected my phone and held down power, vol+ and vol-. But it could be that i hold the buttons before i connected the phone.
It will work somehow im sure. Its nearly impossible to brick a a/b device with a simple rom flash.
As english is not my mother language, I always doubt if I explained correctly, thanks!
Do you remember if there were any sound in windows when you plugged the phone? In mine, nothing happens, as if I wasn't connecting anything.
I've been bricked before but I always got to oneplus logo, but now I have an all-black screen and no reaction at all.
Hammerhand.17 said:
As english is not my mother language, I always doubt if I explained correctly, thanks!
Do you remember if there were any sound in windows when you plugged the phone? In mine, nothing happens, as if I wasn't connecting anything.
I've been bricked before but I always got to oneplus logo, but now I have an all-black screen and no reaction at all.
Click to expand...
Click to collapse
English is not my native language, too.
I had no windows sound, no nothing. My pc didnt know there was something connected.
Did you use the MSM tool before? Because you have to make sure that all drivers are installed.
Yes, I have used it several times but any time I used it, the pc made the sound for device connected. Anyway, I'm gonna search the drivers and install them again just in case.
Your phone was completely dead too?
Edit: the drivers I found are for the case I have an unknown device in device administrator, but windows doesn't recognice no device, so I can't use them.
Hammerhand.17 said:
Yes, I have used it several times but any time I used it, the pc made the sound for device connected. Anyway, I'm gonna search the drivers and install them again just in case.
Your phone was completely dead too?
Edit: the drivers I found are for the case I have an unknown device in device administrator, but windows doesn't recognice no device, so I can't use them.
Click to expand...
Click to collapse
My phone was dead too. But it did something if i hold all 3 keys together for a very long time but i dont remember completly. But i guess you know how a/b devices work, you never flash both slots at the same time so a hard brick by flashing is nearly impossible.
So the drivers wont help until your pc recognice the phone. ANd if you used msm before, the drivers should be installed.
Are you using the original 1+ cable? if yes try a third party cable.
Try switching the usb ports too.
Yes, my only doubt is that I flashed several partitions from a payload (just as I did several times before, to update firmware), but they were from oos open beta 1. Don't know if this flask affects to both slots or just live any other flash.
I've tried all key combinations, with three different cables and in four different ports. I have to be skipping something.
Hammerhand.17 said:
Yes, my only doubt is that I flashed several partitions from a payload (just as I did several times before, to update firmware), but they were from oos open beta 1. Don't know if this flask affects to both slots or just live any other flash.
I've tried all key combinations, with three different cables and in four different ports. I have to be skipping something.
Click to expand...
Click to collapse
hello did you get solution i have same phone in same state what is needed here is opening phone and using testpoint to get edl mode but question is how to locate the testpoint
jroki said:
hello did you get solution i have same phone in same state what is needed here is opening phone and using testpoint to get edl mode but question is how to locate the testpoint
Click to expand...
Click to collapse
No, I didn't. I didn't even know that you could achieve edl mode this way. If you make some progress, please share it.
i have opened phone but still failed to locate the edl testpoint incase i succed will make updates here
jroki said:
i have opened phone but still failed to locate the edl testpoint incase i succed will make updates here
Click to expand...
Click to collapse
Have you tried to use deep flash cable?
If you have a voltmeter that can help you in your search.
You're looking for a pair of points, conspicuously by themselves.
They could be blocked by a connector for something like a camera.
One point should measure 1.8V That is the internal power supply.
One point should measure 0V That is the sensing input pin.
If you have any resistors of say 200-3000 ohm that is a safer thing to jump test points that you're not sure of.
When you jumper the points the 1.8V stays the same and the 0V goes to 1.8V
If all else fails you can try to disable the flash by using a 100-200 ohm resistor to ground on testpoints near the flash memory.
If the ROM bootloader finds it can't even access the flash it will also go to EDL mode.
I believe (but don't know) that the "deep flash" cable support is part of the SBL/XBL (and not the boot ROM) and so it may not work on all models.
I've never got one to work, but that may be my fault.
In any case, if someone has authoritative info on it, I'd love to know.
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.
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Ezzell said:
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Click to expand...
Click to collapse
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
HolyHog said:
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
Click to expand...
Click to collapse
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Ezzell said:
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Click to expand...
Click to collapse
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
HolyHog said:
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
Click to expand...
Click to collapse
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Ezzell said:
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Click to expand...
Click to collapse
If MSM does not recognize your phone there is something wrong with your PC.
Make sure that you read the full post:
[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
Use another USB Port and/ or another USB cable.
Dont use Windows11
Install latest Universal ADB Driver
Install latest Qualcomm Drivers
Install latest OnePlus drivers.
In fact the last thing that will NOT work is MSM. If MSM does not work your phone is completly dead. (Which yours is obviously not because it boots into bootloader) This means if MSM does not work, there is something wrong on your end.
Talking about dead devices, be etremly careful what you do in Fastboot mode!
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anything you do in the OS, like allowing OEM unlocking has **nothing** to do with MSM. In fact, a MSM flash will relock the bootloader. You will have to unlock again if you want to run anything except stock.
You have to boot the phone into EDL mode. Start MSM, then while holding the volume bar down, (UP and down, the entire button) plug into usb. Dont use the power button. (You may let volume keys go once done) There will be a dark screen, the only way to tell if in EDL mode is to check your device manager for the correct device. If you see anything on the screen you are not in EDL mode. I did use USB 2.0, do not use a hub.
I ask to start MSM first because on my Oneplus8, the EDL mode wont stay active for too long, unless MSM finds the phone.
If that does not work, put the phone into EDL mode and check your device manager (ports COM anf LPT) for QDLOADER 9008. Anything else, and the driver is not installed correctly and MSM won't work, If adb is working you can issue "adb reboot download" but the button press seems more applicable in your case.
There is a lot in the link below, it is for A10, I believe there is now a MSM for A11 but I have no experience with them.
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
I have tried all these and msm will not recognize the device in any state so Iv reverted to using a repair shop msm was successful in making the device stock the problem came from rebooting the device while msm was still connected and running. Pressing any button would lead to the download failed screen where the device is not recognized or into bootloader where oem is locked and even though before boot I checked unlocking enabled the fastboot command would not unlock the bootloader, if the store fix it I will try get details on what they did