[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12

[ko_hi]

I wish it was not the case. Idk but in my country there are cheap and good samsung phones for under 150€, at amazon too.

I don't like samsung

 

[dargur.mikk]

So, to clarify,
i have ota oxygen os 11.0.11.11.IN11BA, unlocked bootloader, root, magisk 25.2 with zygisk and ramdisk
will i brick my op8p if i apply ota IN2023_11.C.16_1160_202204222258?

should i do all this before applying the update?
1. uninstall magisk
2. factory reset
3. unroot
4. flash original boot.img
5. lock bootloader

 

[ko_hi]

So, to clarify,
i have ota oxygen os 11.0.11.11.IN11BA, unlocked bootloader, root, magisk 25.2 with zygisk and ramdisk
will i brick my op8p if i apply ota IN2023_11.C.16_1160_202204222258?

should i do all this before applying the update?
1. uninstall magisk
2. factory reset
3. unroot
4. flash original boot.img
5. lock bootloader

Most likely you just need to remove the safetynet props or any that tampers the props in general

 

[x_files_X]

Is there any other way but to replace the motherboard?

 

[sketch.droid]

Some extra warnings:
1. OnePlus 8T/9R also has LPDDR4x variant, make sure the variants before flashing.
2. The DDR detection process was artificially killed, stay away from the Magisk modules to keep safe.
3. TWRP is no longer recommended, use OxygenOS modified recovery or other ROM's recovery instead.
4. Flash/Root has huge risks, all operations need to be careful.

OnePlus 8 - LPDDR4x
OnePlus 8 Pro - LPDDR5
OnePlus 8T - LPDDR4x/LPDDR5
OnePlus 9R - LPDDR4x/LPDDR5

This whole situation scares me from even attempting any Updates anymore.... I cant afford a new phone!

but while reading about this I came across a Reddit post confirming that 8T variants came with both LPDDR4x and LPDDR5, and poster provided an adb command to check which RAM type you have.
Not sure if I'm allowed to post a link to it...

I think this should be added to the first post.

adb shell getprop ro.boot.ddr_type

getting a 0 (zero) means LPDDR4x
getting a 1 (one) means LPDDR5

 

[AboAnas25]

So if my device was broken and got black screen without any response even edl
, no hope to fix?

 

[denvit]

I too bricked my phone by running (as per my usual):

```
for i in *.img; do fastboot flash ${i/.img/} $i; done
```

from the extracted payload.bin of the global C.16 build (ota_target_version=IN2025_11.C.16_1160_202204222300)

This caused the `xbl.img` to be flashed on the xbl partition and the xbl_lp5.img to not be flashed anywhere.
Rebooting the phone bricked it: can't enter EDL in any way (maybe pin shorting is our last resort) and the phone is basically a brick.

Analyzing the bootloader difference, there seems to be the check mentioned in the initial post. I'm not sure why you think this is not working (other than the fact that the phone doesn't show anything).

It would be interesting to get some UART logs, but I have no clue on how the motherboard looks like, let alone where the pins are.

xbl.img​

xbl-lp5.img

If anyone has any tip on how to proceed, it would be great - tbh I'm surprised the bootloader wasn't a protected partition to begin with, or that they don't fall back to EDL in this case.

 

[Peter Linzbauer]

Hi I am trying to flash lineage 19 on my Oneplus8 Pro. I tried a bunch of stuff and now I need some help. I understand how to unpack the OnePlus8ProOxygen.zip via payload-dumper-go. I had Problems flashing the .img in fastboot. When I entered fastboot with the lineageOS-recovery it worked fine.

My Problem now, I can't find the xbl_lp5.img & xbl_config_lp5.img files. Where do I get them from?

Edit: So I found them in the .zip I downloaded with the Oxygen Updater App. I installed it on an other phone. Then I proceeded to unpack with the payload-dumper-go Tool und flashed the .img via fastboot.

 

[ikram.senguen]

Hi I am trying to flash lineage 19 on my Oneplus8 Pro. I tried a bunch of stuff and now I need some help. I understand how to unpack the OnePlus8ProOxygen.zip via payload-dumper-go. I had Problems flashing the .img in fastboot. When I entered fastboot with the lineageOS-recovery it worked fine.

My Problem now, I can't find the xbl_lp5.img & xbl_config_lp5.img files. Where do I get them from?

Edit: So I found them in the .zip I downloaded with the Oxygen Updater App. I installed it on an other phone. Then I proceeded to unpack with the payload-dumper-go Tool und flashed the .img via fastboot.

Lieber Peter, lieber versuchs erst garnicht, habe mein phone gebricked und ich bin eigentlich erfahren in allem hier, das geschilderte problem mit dem ram zerstört das handy und es könnte überall die falsche xbl file drinn sein

gehst du auf lineage 19, kommst du nich zurück auf OOS, und versucht du es, brickst du dein phone, für immer ( wusste auch nicht das das möglich is per adb und fastboot, aber scheinbar ist es das! )

am besten bleib auf oos

 

[Nimueh]

Lieber Peter, lieber versuchs erst garnicht, habe mein phone gebricked und ich bin eigentlich erfahren in allem hier, das geschilderte problem mit dem ram zerstört das handy und es könnte überall die falsche xbl file drinn sein

gehst du auf lineage 19, kommst du nich zurück auf OOS, und versucht du es, brickst du dein phone, für immer ( wusste auch nicht das das möglich is per adb und fastboot, aber scheinbar ist es das! )

am besten bleib auf oos

Please translate your post to English, as required by the XDA rules

 

[ikram.senguen]

Please translate your post to English, as required by the XDA rules

sry for my offending, im so pissed, thats no excuse either, just know that it was not personal, this rom flash was expensive af and i wish i could knew this earlier, so now im just boykotting oneplus and warning others

 

[runhard]

Hi I am trying to flash lineage 19 on my Oneplus8 Pro. I tried a bunch of stuff and now I need some help. I understand how to unpack the OnePlus8ProOxygen.zip via payload-dumper-go. I had Problems flashing the .img in fastboot. When I entered fastboot with the lineageOS-recovery it worked fine.

My Problem now, I can't find the xbl_lp5.img & xbl_config_lp5.img files. Where do I get them from?

Edit: So I found them in the .zip I downloaded with the Oxygen Updater App. I installed it on an other phone. Then I proceeded to unpack with the payload-dumper-go Tool und flashed the .img via fastboot.

Peter, do you have the xbl_lp5 files you would be able to share? Thankfully the Lineage instructions warn against flashing the wrong version, but now I am stuck needing those before I can continue with the install on a OnePlus 8 Pro. Otherwise, if you could provide the steps you took to find the files, that would be helpful, too.

EDIT: Was able to locate. Now the Fastboot screen is cycling through the input options and not responding to add.

 

[Renate]

Anyway you probably can't run EDL without working ram.

Mmm, I don't think that's true.
I can't speak for every processor, but they mostly (all?) include static RAM on the chip just for starting up.
The ROM bootloader is simple and doesn't configure any external DRAM (AFAIK).
I have worked with secondary loaders where I have seen that they configure external DRAM.
It seems to me that just a processor by itself should be able to get the Sahara protocol running at least.
Whether the Firehose loaders use external DRAM is a different question.
I think that I have a phone that I can actually check that with. I can hit the DRAM with a center punch.

Also, that this whole thread is about the DRAM configuration code in xbl...

As far as getting into EDL mode, I think EDL test points are the "gold standard".
Just as adb reboot edl is dependent on the reboot executable and abl that knows to look for something in /misc or elsewhere, buttons are random GPIOs that abl polls,
There's no reason that Qualcomm when they make a chip would know/care that a Zircon 3000 phone uses GPIO 27 for VolUp.
I do not believe that "EDL mode USB cables" are detected inside the SoC ROM, but in abl or elsewhere.

I'd welcome any corrections to my understanding.

 

[rmedure]

I took the android 12 OTA on OP8 Plus, version IN2025_11_C.21, downloaded with the "Oxygen Updater" app. Using payload dumper shows that there are only 2 xbl images:

xbl.img
xbl_config.img

So then, how do I tell if these are the correct xbl images?

 

[ShadoV90]

I took the android 12 OTA on OP8 Plus, version IN2025_11_C.21, downloaded with the "Oxygen Updater" app. Using payload dumper shows that there are only 2 xbl images:

xbl.img
xbl_config.img

So then, how do I tell if these are the correct xbl images?

If you took A12 official OOS ROM, then after using payload dumper, you should have:
xbl.img
xbl_config.img

xbl_lp5.img
xbl_config_lp5.img

As first post says with bold letters:
"If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img"

"If You have OnePlus 8 Pro [...] (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img"

IN2025 is OnePlus 8 Pro (NA variant)
Double check everything. It's better to check 100 times, than end with dead device.

 

[rmedure]

Hmm, my bad. All 4 xbl images are there ... I swear I checked twice and only saw the 2. Anyway, I was able to dd the xbl partition and compare and find that it does indeed match xbl_lp5.img in the payload. So I guess I was lucky to happen to follow a procedure that worked.

I used the Magisk manager app to "uninstall Magisk" (I guess this restores the boot partition to original). Then ran "local update" with OTA zip downloaded with OxygenUpdater (did NOT reboot yet). Then used Magisk manager to install Magisk to inactive slot. Seems all went well.

I am not trying to use any custom recovery yet. My understanding is that new A12 TWRP for OP8 Plus is not yet done.

Hopefully this helps some of y'all.

Cheers!

 

[Winstarshl]

Please help, after the OnePlus 8 Pro was bricked through the wrong firmware XBL, there is no way to recover
Is there still a way?

And what if I replace the board with a new one from Aliexpress will then work my fingerprint scanner?

 

[AkayamiShurui]

So I don't know if a lot of people know this or not I've been on here for a year and a half studying and studying and trying to figure out how to unbrick my OnePlus 8 pro I got it out of deep sleep mode I got my computer to pick it up I haven't got the flash yet cuz I worked today but I'm going to try it soon so I will post an update in a separate form post

 

[FateRover]

how to fix hard brick 9r (Can't get into EDL mode/9008)

Few monthes ago, some 9R devices were killed by an mistake of 1+ commpany,this is link https://forum.xda-developers.com/t/guide-how-to-avoid-killing-your-oneplus-8-pro-8t-9r-with-oxygenos-12-coloros-12.4426167/ As we know,if wana flash stock...

forum.xda-developers.com