Dead oneplus 8 pro! - OnePlus 8 Pro Questions & Answers

Hello guys
My oneplus 8 pro had soft brick then I tried msm tools but for different reasons not recognized phone
So I thought to use enhance fastboot app to flash payload.bin directly after flashing the device completely dead even no response with charger nor edl mode
Can someone help me?

[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
[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:
[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
[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 tried to enter edl to use MSM but no response from phone
Any other method?

AboAnas25 said:
I tried to enter edl to use MSM but no response from phone
Any other method?
Click to expand...
Click to collapse
Do you install good driver?
File folder on MEGA
mega.nz
and
Do you try enter on OP EDL mode? Hold 3-4 sec volume up and volume down?

AboAnas25 said:
I tried to enter edl to use MSM but no response from phone
Any other method?
Click to expand...
Click to collapse
The real question is: Did you try to flash a Android 12 Payload?
The answer is probably yes because your pc does not regognize the device.
This means your device is probbly a brick now.
[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

zioloiso said:
Do you install good driver?
File folder on MEGA
mega.nz
and
Do you try enter on OP EDL mode? Hold 3-4 sec volume up and volume down?
Click to expand...
Click to collapse
Drivers are ok
The problem is not the drivers
The device is completely dead and not responding to any thing

xtcislove said:
The real question is: Did you try to flash a Android 12 Payload?
The answer is probably yes because your pc does not regognize the device.
This means your device is probbly a brick now.
[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
Click to expand...
Click to collapse
Yes android 12

AboAnas25 said:
Yes android 12
Click to expand...
Click to collapse
This means you have a dead phone and need to replace the motherboard. Im sorry for you

xtcislove said:
This means you have a dead phone and need to replace the motherboard. Im sorry for you
Click to expand...
Click to collapse
How not to make such a mistake?

zioloiso said:
How not to make such a mistake?
Click to expand...
Click to collapse
Dont use fastboot enhance on oneplus devices for now. at least not on 8/9 series as far as i know. And most important, only follow guides on the correct device forum. Its known since eraly april that A12 can brick your device. There is no guide for fastboot enhance here and every fastboot guides mention that you need to check your ram and flash the correct images.
Its a hard lesson but if you follow the guides in the future you are good to go.
[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

As i see OOS 13 ROM have only one xbl version, so from A13 isn't possible to flash wrong (ddr4 into ddr5) xbl.

ShadoV90 said:
As i see OOS 13 ROM have only one xbl version, so from A13 isn't possible to flash wrong (ddr4 into ddr5) xbl.
Click to expand...
Click to collapse
This all came from people flashing the wrong rom or flashing it the wrong way. As long as you have A12 on both slots you won't have any problem flashing a A13 rom.

HolyHog said:
Your xbl version is for your phone version, not the rom version. OP8Pro is xbl ddr5 no matter what rom you have. If you want to have an after market A13 rom you have to have A12 on both slots.
Click to expand...
Click to collapse
I know that xbl version is for phone version, but idk what OnePlus wanted to do.
Out of curiosity, do you ever extract OOS12 for oneplus 8 pro?
I did many times, and on OOS11 and 13 there are one version of xbl, on OOS12 there are TWO versions of xbl. xbl+config (for ddr4) AND xbl_lp5+config (for ddr5). People who flashed OOS12 on pro devices via fastboot ended often with dead devices due to flashing wrong xbl. Well, if you don't believe me, then you have some threads on this forum, see https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/, or download oos11 (or 13) packages and oos 12, extract images and see it in your own eyes.
EDIT: Adding some words.

ShadoV90 said:
I know that xbl version is for phone version, but idk what OnePlus wanted to do.
Do you ever extract OOS12 for oneplus 8 pro? On OOS11 and 13 there are one version of xbl, on OOS12 there are TWO versions of xbl. xbl+config (for ddr4) AND xbl_lp5+config (for ddr5). People who flashed OOS12 on pro devices via fastboot ended often with dead devices due to flashing wrong xbl. Well, if you don't believe me, then you have some threads on this forum, see https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/, or download oos11 (or 13) packages and oos 12, extract images and see it in your own eyes.
EDIT: Adding some words.
Click to expand...
Click to collapse
I am on A13 right now and have no problem going from A12 to A13 or A13 to A12. I am just saying once you A12 on both slots you don't have to worry about xbl status if you follow their instructions.

HolyHog said:
I am on A13 right now and have no problem going from A12 to A13 or A13 to A12. I am just saying once you A12 on both slots you don't have to worry about xbl status if you follow their instructions.
Click to expand...
Click to collapse
Well, i'm on OOS13 and had no problems with OOS12, but as i said, there are people who ended with (as they said) fried motherboards and needed to replace them because of wrong xbl flash (i guess via fastboot or all-in-one tool).
I'm curious what is the real reason of dead devices in this case, fried motherboard because ddr4 needs higher voltage and this higher voltage on ddr5 will cause damage (i want to know if really something is physical damaged like motherboard or RAM)? Or maybe phone don't let to run because of mismatch ram and xbl... (But there should be sign of booting something) Idk. Result is that these phones don't react to anything. I read somewhere that after replace motherboard device is able to boot. I'm curious if motherboard is really damaged via flashing wrong xbl of OOS12 package.

ShadoV90 said:
Well, i'm on OOS13 and had no problems with OOS12, but as i said, there are people who ended with (as they said) fried motherboards and needed to replace them because of wrong xbl flash (i guess via fastboot or all-in-one tool).
I'm curious what is the real reason of dead devices in this case, fried motherboard because ddr4 needs higher voltage and this higher voltage on ddr5 will cause damage (i want to know if really something is physical damaged like motherboard or RAM)? Or maybe phone don't let to run because of mismatch ram and xbl... (But there should be sign of booting something) Idk. Result is that these phones don't react to anything. I read somewhere that after replace motherboard device is able to boot. I'm curious if motherboard is really damaged via flashing wrong xbl of OOS12 package.
Click to expand...
Click to collapse
I read somewhere about the wrong voltage applied so they probably are dead but I would still like to try to fix one. I had my phone so broke one time, it had no fastboot or recovery. Just nothing on the screen at all and I resurrected it with MSM using my $6,000. server computer. I can't help but think I could fix one of these phones, but don't know for sure, but I would like to try.

There is a whole thread on this already and no, the phones can't be fixed with MSM. But it's good to hear that the issue can't repeat itself on OOS 13 since OP went back to having only 1 xbl file in the rom

Moderator Announcement
Thread cleaned from posts violating rule no. 7 of the XDA Forum Rules:
7. Do not sell or trade on the forums.
If you wish to advertise a product, simply contact us. We can provide ads but you are not permitted to just post it in the forums. If you do, it will be removed and you're likely to receive a ban.
The buying, selling, trading and / or exchanging of any item is now prohibited on XDA, in any forum or via Private Messages. We now use www.swappa.com
Click to expand...
Click to collapse
Please refrain from such posts in future.
Regards
Oswald Boelcke
Senior Moderator

Related

Need help to go back to stock 11.0.2.2IN11AA

I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[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
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[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
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.

[Solved] Stuck in Bootloader

so i was trying to flash CherishOS so i followed the instruction and found some problem but i was managed to solve the problem. FYI, the rom gave the link to the custom recovery which is the PixelExperience one, since i'm coming from the stock latest rom so i flashed that. until i done everything and boot to system, and it just keeps returned to the bootloader no matter which option i choose (boot to system & recovery), but luckily the device is still detected in my computer
What i've tried :
- flash recovery (PixelExperience & TWRP)
- Followed this instruction
but none of that is working, one thing i found out while doing the 2nd method is that it shows some errors like "flashing is not allowed for critical partition" and "partition not found".
I have no clue what to do, i've tried whatever solution i could find and none are working. please help, thanks
edit:
I also tried the "fastboot flashing unlock_critical" and tried to reboot into fastbootd but failed and the fastboot shows all command list
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[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
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
xtcislove said:
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[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
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
Click to expand...
Click to collapse
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
B1nz said:
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
Click to expand...
Click to collapse
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
flo musti said:
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
Click to expand...
Click to collapse
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
B1nz said:
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
Click to expand...
Click to collapse
already tried but the phone is not going in Qualcomm EDL mode...
flo musti said:
already tried but the phone is not going in Qualcomm EDL mode...
Click to expand...
Click to collapse
in my experience, my phone is just showing nothing it's like the screen is off. i realized that my phone is in EDL mode is it's detected in my computer as qualcomm something.., when it shows like that that means you haven't installed the qualcomm driver. after that the name will change to "more normal" name. and then you can proceed into the tools

"Warning" Total Brick After Flashing Android 12 Beta

My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
xtcislove said:
Flashing roms via fastboot never works for me.
You should read the threads next time, there is no custom rom that works from a12, every rom need a11 as a base. And yes the a12 custom roms too.
Your only option is and was the MSM tool.
I was in a similar situation, i got my phone back with pressing vol +, vol - and power for i think several minutes while connected with a third party cable to my pc with msm tool where i already pressed start.
It started to flash everything somehow and i got a working phone.
Good luck.
Click to expand...
Click to collapse
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
nkhater said:
Yes, OSS 11 is a must, I have tried downgrading and I guess "downgrading" is the issue here.
I have been using OnePlus since its first release, I am very familiar with it,
I have tried everything, but nothing works, I read more about this, and looks like the circuit is out of order, it will not pass anything "signal", especially to the screen.
Click to expand...
Click to collapse
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
daviddosa said:
A quick note: EDL mode will show nothing nor vibrate. The only way you know it's in EDL mode is that it's going to show up in MSM tool.
Just try using the MSM tool.
Start the program.
Hold the Vol Up and Vol Down at the same time for 5 seconds, then connect your phone to your PC.
If it doesn't show up in the MSM tool list, just hit Enum.
If you see the phone just click Start and wait for it to complete. For me it's usually around 300 sec.
Click to expand...
Click to collapse
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
xtcislove said:
Thats possible im not a pro. But from my understanding, its nearly impossible to brick a phone which is using a/b partitions via fastboot.
You tried a third party cable?
Click to expand...
Click to collapse
Yes fail-safe a/b partition, and Yes I have tried several cables
nkhater said:
true, but no Qualcomm port is shown in the windows device manager, and no sound coming from the laptop, it's cooked
Yes fail-safe a/b partition, and Yes I have tried several cables
Click to expand...
Click to collapse
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
daviddosa said:
My last suggestion is to try to charge overnight and see if things are different tomorrow.
Other than that, only option is RMA as it's still under warranty.
Forgot that you already opened up the phone, so most likely they'll throw it back as it was opened by an unauthorized party.
Click to expand...
Click to collapse
did that too, leaving it overnight did not work either.
I hope this will be an eye-opener for other flashaholics, things are different in A12
my phone has the same problem, have you fixed it, i need help
[email protected] said:
my phone has the same problem, have you fixed it, i need help
Click to expand...
Click to collapse
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
nkhater said:
no fix has to call support and use your warranty, the logic board is fried, this is a disaster, everyone, be careful, I want to sue them so bad
Click to expand...
Click to collapse
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[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
ProtoDeVNan0 said:
Made a thread about it to warn others and hopefully prevent more bricks from happening.
[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
Click to expand...
Click to collapse
OMG
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Mar 3rd I posted for the 1st time about it.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
djcrystals said:
Nobody believed me in the threads when this happened (end of Feb/early Mar). This wasn't spiteful in anyway either. It was more/less just unheard of and my methods and adherence to the most vital aspects for EDL recovery, were justifiably questioned. Unfortunately, in my case, I have had years of experience jacking-up my devices and I immediately knew/felt there was something different with this situation. In my situation though, when introducing how I had entered the predicament, it was strictly self-inflicted, complacency at its finest and terrible terrible timing for a well overdue slap-in-the-head to interject itself into my life. Did I mention I was OMW to Disney with m/wife, kids.....driving. I had 7 days to deal with at Disney with a pre-planned, fresh-flashed A-12 OP8....I ended up using my LG G3 which I had been spending significant time trying to develop into a dedicated full-fledged Kali device (had success w/that actually).
So seeing these posts and threads now is dis-heartening but vindicating. Had I not flashed A-12 the way I did, I would've been fine. I can not blame OnePlus for anything, I bought a locked-down (carrier unlocked) Note 10+ in its place and its driving me bonkers. I thought I would be able to tolerate the non-rootiness, but I've been flashing since my 1st smartphone, one of the 1st Galaxy's, the Verizon Fascinate.....good ol' Jelly Bean. Meanwhile, my lifeless OP8 sits on my desk upstairs surrounded by older devices.....its the only one that doesn't turn on.
Click to expand...
Click to collapse
That's so fed'ed up man, I am in the same boat as you, total loss, I am done with OnePlus, they can enjoy Oppo and ColorOS, A12 sucks and it's not for me.
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Andre Cancian said:
Had to replace the motherboard (and flash the old persist partition to get the fingerprint sensor to work) due to this flash ddr mismatch crap. Shame on oneplus. They're being way too careless on this "unifying" trend.
Click to expand...
Click to collapse
how much did you pay for the motherboard?
nkhater said:
how much did you pay for the motherboard?
Click to expand...
Click to collapse
I paid something like 250 USD for a working 8 Pro with a broken screen. Motherboards on their own were available for a similar price on sites like aliexpress, but the wait was too much.
nkhater said:
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot.
I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from Fastboot, it did not work either, I tried EDL MSM tool, it did not work either, it kept on booting into fastboot, fastboot loop, I extracted the payload.bin from A12 Beta using payload_dumper, I ran flash-all script, the phone successfully booted into fastboot the at the first section from the script, flashed the remaining files, when the phone attempted to rebooted for the final time after the script was completed successfully with no errors, the phone died at the final part of the script, which is the final boot, and it will not respond to anything, no sign of anything, complete black screen, I tried EDL mode, I tried everything, it's not responding to anything, I opened the phone and reseated the battery and the motherboard, still nothing. So Sad
Click to expand...
Click to collapse
hello, did you solve your problem? Or did you change your motherboard? I'm having the same problem right now and I don't know what to do
you need to replace the motherboard, the phone is completely dead, it's gone

OnePlus 8 Pro hard bricked

Hi, I was just wondering if anyone can help me. I know it's a lost cause at this point cuz it was my fault but I managed to get my phone to get bricked as I was trying to flash newer firmware for the phone. It succeeded without issues but when it rebooted it never wants to turn on. I've checked with an ampmeter and it's only drawing little power. It does try to boot but it thinks it doesn't have any firmware on it if that makes sense. I can't get it to EDL or even diagnostic mode.
Note:
Running Pixel Experience 12
Android 11 firmware (Tried to update to 12 for 5g modem)
Any sort of help or info would be appreciated cuz I'm pretty devastated from my mistake
Thank you
Note: I've realised that the video didn't load so here is the link of my trying to power it on to EDL 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
If you flashed the wrong images via fastboot you killed your phone.
xtcislove said:
[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
If you flashed the wrong images via fastboot you killed your phone.
Click to expand...
Click to collapse
I was flashing the firmware that was from the official OTA firmware and it just decide to crap itself. I have assumed and probably will think that the device is fried cuz of the memory confusion.
Rain_- said:
I was flashing the firmware that was from the official OTA firmware and it just decide to crap itself. I have assumed and probably will think that the device is fried cuz of the memory confusion.
Click to expand...
Click to collapse
Its not a problem if you flash it as local upgrade inside OOS but it can be a problem if you flash it via fastboot
Were you able to fix this somehow?
hello, did you solve your problem? Or did you change your motherboard? I'm having the same problem right now and I don't know what to do
Had my motherboard replaced by OnePlus service.
7bob said:
Had my motherboard replaced by OnePlus service.
Click to expand...
Click to collapse
hello, is your device working now? How much did the service charge?
x_files_X said:
hello, is your device working now?
Click to expand...
Click to collapse
Yes
x_files_X said:
How much did the service charge?
Click to expand...
Click to collapse
Depends on the country and RAM / ROM size, see here https://www.oneplus.com/support/repair-pricing/details?code=25 or https://www.oneplus.com/support/repair-pricing
Rain_- said:
Hi, I was just wondering if anyone can help me. I know it's a lost cause at this point cuz it was my fault but I managed to get my phone to get bricked as I was trying to flash newer firmware for the phone. It succeeded without issues but when it rebooted it never wants to turn on. I've checked with an ampmeter and it's only drawing little power. It does try to boot but it thinks it doesn't have any firmware on it if that makes sense. I can't get it to EDL or even diagnostic mode.
Note:
Running Pixel Experience 12
Android 11 firmware (Tried to update to 12 for 5g modem)
Any sort of help or info would be appreciated cuz I'm pretty devastated from my mistake
Thank you
Note: I've realised that the video didn't load so here is the link of my trying to power it on to EDL Mode
Click to expand...
Click to collapse
Rain_- said:
Hi, I was just wondering if anyone can help me. I know it's a lost cause at this point cuz it was my fault but I managed to get my phone to get bricked as I was trying to flash newer firmware for the phone. It succeeded without issues but when it rebooted it never wants to turn on. I've checked with an ampmeter and it's only drawing little power. It does try to boot but it thinks it doesn't have any firmware on it if that makes sense. I can't get it to EDL or even diagnostic mode.
Note:
Running Pixel Experience 12
Android 11 firmware (Tried to update to 12 for 5g modem)
Any sort of help or info would be appreciated cuz I'm pretty devastated from my mistake
Thank you
Note: I've realised that the video didn't load so here is the link of my trying to power it on to EDL Mode
Click to expand...
Click to collapse
Bro just use msm tool that will fix it anyways

I did a big dumb. Failed root

Howdy. Tried to root my OnePlus 8 Pro. First time trying such a thing... Having now bricked my phone into a boot loop, I'm pretty sure that the guide I followed missed an important step. It said to download the latest patch, extract it, then use magisk to patch it and flash it. I'm pretty sure that the part I missed was actually updating to that patch before flashing. So I have whatever latest patch that I didn't have the foresight to write down, but my original build was IN2025_11_C.33 . Am I boned completely and thoroughly or is there any hope of recovering? Thanks either way.
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
SomeRandomGuy said:
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
Click to expand...
Click to collapse
thanks!
dimlu said:
thanks!
Click to expand...
Click to collapse
In case you haven't sorted it yet - this is a great MSM guide which also links to the Windows drivers you need and the MSM tools for your device.
Good luck

Categories

Resources