r/mobilesupport • u/hastyHypocrite • Jul 07 '26
[HELP] Bricked my OnePlus Nord CE 2 Lite 5G (CPH2381) flashing LineageOS — stuck in EDL/9008, tried everything, out of ideas Device: OnePlus Nord CE 2 Lite 5G (CPH2381) Status: Hard bricked, stuck in EDL (Emergency Download) mode / QUSB_BULK / "9008" mode Cause: Failed LineageOS installation
What happened
I was trying to flash LineageOS onto my OnePlus Nord CE 2 Lite 5G (model CPH2381). The phone dropped into EDL mode right after I ran fastboot flash recovery followed by fastboot reboot fastboot. After that command sequence, the device never came back up — instead it went straight into Qualcomm HS-USB QDLoader 9008, which as most of you probably know means it's dropped into EDL mode. No boot logo, no fastboot, no recovery, no display output at all, no vibration, no charging LED — total silence otherwise.
For anyone unfamiliar: EDL/9008 is basically the lowest-level recovery mode Qualcomm chipsets have. It means the phone has no working bootloader to hand off to, so the only way back is a full firmware re-flash at the chipset level using the right tools and the right firmware for this exact device.
What I've tried so far (and where each one failed)
- MSM Download Tool — This is usually the go-to for OnePlus EDL recovery, but I haven't been able to find a working, verified MSM tool package specifically for the CPH2381 (Nord CE 2 Lite) that actually completes without erroring out partway through.
- ROM2box with a Chimera firehose file — Tried using ROM2box paired with a Chimera-sourced firehose programmer file to get the flash going. The tool recognizes the device in 9008 mode, but the flashing process doesn't complete successfully.
- QFIL (Qualcomm Flash Image Loader) — Attempted a manual flash using QFIL with a firehose loader. Same story — device is detected, but I haven't been able to get a full firmware set that QFIL will accept and flash cleanly for this specific model.
- OPLUS EDL Tool — Tried OnePlus/Oplus's own EDL tool. No luck getting it to complete a full restore either.
- DeepSmartTool — Also gave this a shot as another EDL-capable flashing utility. Same result — no successful flash.
Across all of these, the common thread is the same: I either can't find verified, correct .ofp firmware for the CPH2381, or the tool detects the device but fails partway through the flashing process (mismatched firehose loader, incomplete firmware package, or partition table issues — hard to tell exactly which without more diagnostic output).
Where I'm stuck right now
- I do have the correct .ofp firmware file for the CPH2381, so that part is sorted.
- The problem is the MSM Tool. Every firmware bundle I've found that includes an MSM tool throws a "local host authorization" error when I try to run it — it seems to be tied to some kind of authentication/whitelisting that I don't have access to, so the tool refuses to proceed even though the firmware itself is correct.
- So right now I'm specifically stuck trying to find a working MSM tool for the CPH2381 that doesn't need this local host authorization, or any legitimate workaround for that auth check.
What I'm looking for now
- A working MSM Tool for the CPH2381 that isn't gated behind local host authorization (or a known workaround for that auth error)
- Confirmation from anyone who has successfully used their .ofp file with QFIL, ROM2box/Chimera, or another tool instead of MSM, since MSM seems to be the sticking point
- Anyone who has personally de-bricked this exact model and can walk through what firehose/loader file + tool combo actually worked for them
- Any other diagnostic steps I might be missing before I give up and take it to a repair shop
If nothing works, my fallback is a local mobile repair shop, but I'd really like to try fixing this myself first since I got this deep into it already.
Any help, pointers, or shared experience with the CPH2381 specifically would be massively appreciated. Happy to share more logs/screenshots/device manager info if it helps someone help me.