Related
Hello everybody. Today, i managed to kill my MATE 9.
In short :
MHA-L09C435B156
I wanted to update to a newer fw. Used on forum Guide for debranding,changed oeminfo to c636, flashed with offline_update ,dload method.
It failed at 31%. Tried to fastboot flash boot,userdata,system, fastboot ok,but still bootloop.
I had no twrp full backup.
So i tried this killer method:
Unpacked Update.app with huawei firmware extractor. Created a flashable zip.Flashed in twrp. At the end,i got errors that /system; /product ; /vendor, could not be mounted.
Rebooted the system, ignoring the 'no os installed' warning.
And since then, mate 9 no sign of life.
More details?
Battery was around 45% when started playing with firmwares
Kept power button for 30sec-1 minute,nothing
Plugged charger, usb,nothing
Disassembled the phone,disconnected battery (measured it first,and it was at 3.91v - every phone needs 3.7v to start up),reconnected battery,nothing.
In usb,no message,or sound of device connected.
So,it is really dead.
SO:
Don't make flashable zip with Firmware Extractor Tool.
Anyway, any place to buy Mate 9 Motherboard?
Oh, this is sad. Where did you read to do so?
We have functional guides. They work different.
I guess this what you did, may be similar to that what happened to Luca (shield Rom) when flashing dts.img.
He send the device to Huawei and got a new one. Maybe you are lucky, because this can also happen due to a manufacture error.
My device: Mate 9 superroot, Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
well, since there are few methods to flash mate 9, i had that 5 second idea, to use that feature in this tool.
about getting another one..no warranty. bought it second hand but sealed box.no chance to get another one.
when i have time,i will try to revive it. i work in a gsm repair shop, so i think there could be few tools capable of reading mate 9 emmc
only thing i can think of to fix it is fh, im really surprised no one has found a way to spoof huawei servers to push firmware over erecovery.
can you get into erecovery? (button up + power, when vibrates, let go of power, or button up + down + power)
@Monster.Kali,
As @virtyx stated, erecovery may be an option. Also, if you are able to connect to Huawei HiSuite, it may be a second option.
no,it doesn't make nothing.
no erecovery
no fastboot
no recovery
virtyx said:
only thing i can think of to fix it is fh, im really surprised no one has found a way to spoof huawei servers to push firmware over erecovery.
can you get into erecovery? (button up + power, when vibrates, let go of power, or button up + down + power)
Click to expand...
Click to collapse
Really?
That's amazing.
these phones are a total waste, the partitions are stupidly relying on each other. you cant even restore from within TWRP without the entire phone breaking.
well,i had all huawei mate models since first one,until mate 9.
i was happy with them
but this one....
huawei service center in my country, finaly accepted to fix it if i agree to pay, due to not having warranty.
i wait them to receive it, so we'll see.
they said they are able to reflash it,some factory method,without changing the main board.
good !
Gesendet von meinem MHA-L29 mit Tapatalk
@duraaraa
Sir, i want to ask you, because i think you know more things than any of us about Huawei phones / firmwares / bricks
Would have been any chance to fix my hard brick mate 9 at home?
Thank you in advance
And many thanks for the others that tried to help me. Thank you all for your time.
Monster.Kali said:
@duraaraa
Sir, i want to ask you, because i think you know more things than any of us about Huawei phones / firmwares / bricks
Would have been any chance to fix my hard brick mate 9 at home?
Thank you in advance
And many thanks for the others that tried to help me. Thank you all for your time.
Click to expand...
Click to collapse
If you plug it into the USB port of a computer and check device manager, and nothing happens, then no. You can't fix it.
ok, nothing happened when plugging in. so i'm lucky that huawei accepted it for fixing
thank you, sir
e-recovery doesnt work either way for mate 9. try holding vol down + power, while plugged into usb 3 port (not sure why usb2 doesn't work for this in vmware) but then use the hisuite.
One word @op and other pro members can I flash twrp and then phh for root? And then install custom rom.
I have warranty, in Samsung there is knox counter which detects and warranty void, is here is the same case likewise? Can I flash stock fw if dont like the custom rom.. @Tkkg1994 he is very awesome developer and also a best of the best person I know who tried his lvl best to answer and solve the each n everyone's problem but he left this device, hes working on S7/S7E.
I have attached my device info pic
wrecklesswun said:
e-recovery doesnt work either way for mate 9. try holding vol down + power, while plugged into usb 3 port (not sure why usb2 doesn't work for this in vmware) but then use the hisuite.
Click to expand...
Click to collapse
well, this one i didn't tried. but it is already sent for repair
[email protected] said:
One word @op and other pro members can I flash twrp and then phh for root? And then install custom rom.
I have warranty, in Samsung there is knox counter which detects and warranty void, is here is the same case likewise? Can I flash stock fw if dont like the custom rom.. @Tkkg1994 he is very awesome developer and also a best of the best person I know who tried his lvl best to answer and solve the each n everyone's problem but he left this device, hes working on S7/S7E.
I have attached my device info pic
Click to expand...
Click to collapse
Thanks for your kind words heeheh and mentioning me here so I can share my experience!
Monster.Kali said:
Hello everybody. Today, i managed to kill my MATE 9.
In short :
MHA-L09C435B156
I wanted to update to a newer fw. Used on forum Guide for debranding,changed oeminfo to c636, flashed with offline_update ,dload method.
It failed at 31%. Tried to fastboot flash boot,userdata,system, fastboot ok,but still bootloop.
I had no twrp full backup.
So i tried this killer method:
Unpacked Update.app with huawei firmware extractor. Created a flashable zip.Flashed in twrp. At the end,i got errors that /system; /product ; /vendor, could not be mounted.
Rebooted the system, ignoring the 'no os installed' warning.
And since then, mate 9 no sign of life.
More details?
Battery was around 45% when started playing with firmwares
Kept power button for 30sec-1 minute,nothing
Plugged charger, usb,nothing
Disassembled the phone,disconnected battery (measured it first,and it was at 3.91v - every phone needs 3.7v to start up),reconnected battery,nothing.
In usb,no message,or sound of device connected.
So,it is really dead.
SO:
Don't make flashable zip with Firmware Extractor Tool.
Anyway, any place to buy Mate 9 Motherboard?
Click to expand...
Click to collapse
Don't ever flash anything from huawei extractor.
I broke my device twice with this method. First I was so stupid and created a flashable zip of ALL partitions available on the firmware dump (my aim was to provide a full stock upgrade package with TWRP method). Well didn't end so well, my mate 9 was dead. Like dead forever. I sent it back and told them it suddenly didn't start after all. Well they couldn't fix it, couldn't check for unlocked bootloader, received a brand new one.
After that I thought, yeah maybe it was stupid to flash all paritions including xloader and more. So I wanted to test only with ONE file, the dts file. So I flashed it using the twrp .img flash option, rebooted. Dead. Same as you and same as me before, sent it back again, received a new one.
So that's the 3rd phone I got now, I decided to sell it. I mean what should I do with a phone that can't be rescued after a flash with one file? Nothing, I can't experiment, not test out anything otherwise it will be broken again.
Also the fact that huawei seemed to troll me about my open source requests (the wrote me back to google for the opensource kernel code) helped me to decide to ditch huawei.
You won't ever face this issues on samsung devices, not opensource requests for kernel, not for killing device suddenly. I have to say the huawei mate 9 is great if you use this device "as is" without trying to develop anything for it.
I hope I could explain you my point a bit better, I advice you to send the phone back with the same method as I did. :good:
Tkkg1994 said:
Thanks for your kind words heeheh and mentioning me here so I can share my experience!
Don't ever flash anything from huawei extractor.
I broke my device twice with this method. First I was so stupid and created a flashable zip of ALL partitions available on the firmware dump (my aim was to provide a full stock upgrade package with TWRP method). Well didn't end so well, my mate 9 was dead. Like dead forever. I sent it back and told them it suddenly didn't start after all. Well they couldn't fix it, couldn't check for unlocked bootloader, received a brand new one.
After that I thought, yeah maybe it was stupid to flash all paritions including xloader and more. So I wanted to test only with ONE file, the dts file. So I flashed it using the twrp .img flash option, rebooted. Dead. Same as you and same as me before, sent it back again, received a new one.
So that's the 3rd phone I got now, I decided to sell it. I mean what should I do with a phone that can't be rescued after a flash with one file? Nothing, I can't experiment, not test out anything otherwise it will be broken again.
Also the fact that huawei seemed to troll me about my open source requests (the wrote me back to google for the opensource kernel code) helped me to decide to ditch huawei.
You won't ever face this issues on samsung devices, not opensource requests for kernel, not for killing device suddenly. I have to say the huawei mate 9 is great if you use this device "as is" without trying to develop anything for it.
I hope I could explain you my point a bit better, I advice you to send the phone back with the same method as I did. :good:
Click to expand...
Click to collapse
that's sad....and disturbing for me as huawei fan. the biggest problem is the kirin processor. on snapdragons, we have qhusb, which most of time,solves any problem.
the biggest problem for me, is that i don't have warranty.
the official huawei service center in my country, accepted to fix it, after i told them that i pay any price. they told that are able to flash empty boards, like your 2 cases, and mine.
the worst part is they also mentioned pcb replacement. the phone is new, i can't find any pcb for it, so i can't refuse the fix
ok, they f***d me up.....
they wanted to replace the mainboard, at 454 eur.
i paid 505 eur for the full box sealed phone.
bye bye huawei. moving to xiaomi mi 6 plus....waiting it to be released.
Monster.Kali said:
ok, they f***d me up.....
they wanted to replace the mainboard, at 454 eur.
i paid 505 eur for the full box sealed phone.
bye bye huawei. moving to xiaomi mi 6 plus....waiting it to be released.
Click to expand...
Click to collapse
That is horrendous......
Hey a midnight black O3t - you'll even have taxi money.
Sent from my MHA-L29 using XDA-Developers Legacy app
Yes folks,
As I said, I discovered SUPER BRICK, TOTAL BRICK, COMPLETE FAILURE or whatever yoy want to name this new brick. It has been like this: I was following the instructions to update oreo in HONOR 8 LITE, at the end I had to write some codes in twrp (advance / terminal ...) so it was starting to do the last update (sd card update.zip) and by accident I touched the screen where it appears: REBOOT, so the phone restarted but the screen is not working when it tries to enter erecovery mode, so here is the list of my problems:
- it does not work: erecovery (so I can not recover the phone)
- fastboot works: when I install something (twrp or firmware, I have tried everyone of them) the phone does not start
- if I try to go to TWRP (after installing an oreo one): the screen seems to break and you can not see anything
Please, my phone is 2 months old, man I need to make it work again, I need it.
Help help help
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Nikola6511 said:
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Click to expand...
Click to collapse
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
alopez_666 said:
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
Click to expand...
Click to collapse
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Nikola6511 said:
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Click to expand...
Click to collapse
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
alopez_666 said:
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
Click to expand...
Click to collapse
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Nikola6511 said:
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Click to expand...
Click to collapse
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
I think your EMMC memory might be fried
Nikola6511 said:
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
Click to expand...
Click to collapse
What about using DC PHOENIX???? What do you think????
alopez_666 said:
What about using DC PHOENIX???? What do you think????
Click to expand...
Click to collapse
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Nikola6511 said:
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Click to expand...
Click to collapse
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Same for me, how to fix please. Bricked following this "guide"
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official Emui Nougat, wanted Oreo, forced update with nocheck, everything is broke except fastboot.
When I want to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk /path/to/img" it work but can't reboot to recovery.
I press Power + Vol+ but it reboot "phone untrusted" with Vol+ for going to eRecovery (usualy it's here you can shutdown the phone) but error mode.
Maybe the OreoTWRP work after my command but can't boot into it. Please help.
alopez_666 said:
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Click to expand...
Click to collapse
Bro my P8lite is also bricked, I accidentally wiped the EMMC then I showed it to a repairer and he somehow took me to fastboot mode, now I can't flash anything because that repairer has partitioned the EMMC and now it is showing 486mb total storage so no ROM is flashing because of size. Can you please give me your USERNAME and PASSWORD of DC Pheonix as you've already bought it. It will solve my issue and it will also save me some money.... I will be very thankful to you....
WAITING FOR A POSITIVE REPLY.
I bought it some time ago and it was a 72 hours license and it expired so I do not have anything from that situation. I will check my computer but I will not probably find anything.
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
legionfx said:
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
Click to expand...
Click to collapse
Problem was solved, I used DC Phoenix and installed a rom, but I did it some time ago. Thanks anyway
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
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
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You all are flashing wrong xbl img. Wrong ram versions
what do u mean xbl img? I remember I have read about the ram versions but I think it wasn't the 8 pro...
duxler said:
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Click to expand...
Click to collapse
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
Im am sorry for you guys but you hard bricked your phones for real.
The only thing you can do now is to replace the motherboard.
[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
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Unfortunately that's the case...
jimger said:
Unfortunately that's the case...
Click to expand...
Click to collapse
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
xtcislove said:
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
Click to expand...
Click to collapse
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
jimger said:
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
Click to expand...
Click to collapse
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
xtcislove said:
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
Click to expand...
Click to collapse
Yeah tbh I have every photo etc backed up. Also run my daily swiftkey backup before updating. But the big big bummer now is that I have no way to restore banking apps to tablet atm... Anyway let's hope at least they replace it...
As I understand it, the phone can be thrown away
how will Qualcomm ® Package Manager help if the computer does not see the device.
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Tbh at least I hope they replace it... For now found an Mi A1 from a friend...
I know this topic has been brought up before. But there is not always a half and full explanation.I have Oneplus 8 pro too. I can't enter recovery mode. Boots into fastboot. I've printed a wide variety of msm tools files from edl. It writes smoothly, but when opening the boot screen, it says "your device is corrupted it cannot be trusted and may not work properly" and does not open. What could be the reason? Android 10 11 msm roms, Coloros Hydrogenos all but all tried. There is no recovery. I can't open the oem lock, I can't do anything.
xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
AkayamiShurui said:
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
Click to expand...
Click to collapse
Im sorry my friend i dont understand your post.
xtcislove said:
Im sorry my friend i dont understand your post.
Click to expand...
Click to collapse
If your got discord I can show you
duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Hold up. I'm looking for a dead OP8 Pro. I have started a conversation with you; check notification.