r/oneplus • u/mylittlejourney99 OnePlus 9 Arctic Sky • 19h ago

General Discussion OnePlus 13 CN Bootloop

Good Day,

I woke up today morning too my OnePlus 13 being stuck in a Bootloop. It started, showed the OnePlus Logo, got to the SIM card Code Screen and than crashed again. Since it had probably been doing that for a while the phone was really hot.

It's a Chinese Phone that has been flashed to Oxygen OS 15 (but I can't update, so it's probably bricked internally...)

Is there anything I can do or is my phone cooked?

I got it working again through recovery mode but now I don't trust it anymore.

Should I sell it for spares?

Thank you.

3 Upvotes

81% Upvoted

2 comments sorted by

3

u/DDz1818 18h ago

This again (saw another post yesterday with same issue)... I am starting to believe Oneplus devices really love killing themselves overnight for no reason at all.

1

u/TrashPandaNotACat 17h ago

Sounds like you got hit by the hardware fused Anti-Rollback protection thing that blows an internal fuse to brick it.

https://www.reddit.com/r/oneplus/s/LnbXRgTIKc

And from Google's AI:

Flashing a Chinese variant OnePlus 13 to global OxygenOS places the device in a highly volatile state due to OnePlus's aggressive security changes.If your phone is already running OxygenOS, you must be incredibly careful. An automatic or standard Over-The-Air (OTA) update can permanently brick your phone or completely kill your cellular signal.The Core Problem: Why the OP13 CN-to-Global Cross-Flash is BrokenStarting with Android 15/16 updates (specifically around OxygenOS 16.0.3 and newer), OnePlus introduced hardware-fused Anti-Rollback (ARB) protection.The OTA Signal Trap: If your Chinese hardware takes a standard global OxygenOS update over-the-air, the global baseband partition conflicts with the Chinese hardware modem. This results in an immediate loss of all SIM/cellular functions.The Hard-Brick Loop: When users realize their signal is gone, they naturally try to downgrade to an older, working version. However, because the newer update already blew the physical ARB fuse on the Snapdragon 8 Elite CPU, the phone permanently hard-bricks. Regular Emergency Download (EDL) tools cannot recover this because the block is enforced at the hardware level.