That is NOT the "Orange State Warning" this thread is about. That's the plain old "Bootloader unlocked" message all devices get and you can't remove it. Either update to OOS 12 which has no warning at all, or OOS 13 which has the warning discussed here that you can remove.
Your only option is to contact Oneplus, because as of op10 there is no longer the MSM tool to recover from the brickSo I was researching the message "Remove OOS13 Orange state message text," not paying much attention to the actual device forum I was in. Only quickly skimming for the info I wanted to find. Little did I notice that I was using Oneplus 9 magisk module to flash on my Oneplus 10 Pro. I figured everyone was just using this fix on multiple devices models. Major idiotic move by me, yes I know. I don't need to feel worse than I already do. I may have permanently bricked my device.
So after installing the module through Magisk and rebooting, my 10Pro now stays on black screen. No display whatsoever after multiple hard reboots with Power+Volume up buttons. When connecting to my Windows machine I can hear the device connecting and disconnecting after each reboot. Is there anything I can do to at least get back to bootloader or recovery? Please I don't need any lectures on this, only helpful information on recovering from my dumb mistake.
I've already tried adb kill-server, get-state, remount, devices, etc. No device listing.
Thanks for correcting me I always thought that was the same orange messageThat is NOT the "Orange State Warning" this thread is about. That's the plain old "Bootloader unlocked" message all devices get and you can't remove it. Either update to OOS 12 which has no warning at all, or OOS 13 which has the warning discussed here that you can remove.
so basically image i supposed to be working only for LE2123 is working for both, LE2123 and LE2125, isn't it?
Unfortunately i think no changes could be applied, or it works or not
I haven't gotten the update yet but sure, I'll try once it reaches the EU lol - thanks for replying
I don't know
I don't believe the update failure is due to the orange state fix. It has to do with installing TWRP and/or root.... My wife's op9p with orange state, TWRP, and root fails to update...
I see I'm not the only one with the problem. The issue occurs just before finishing installing the update. Error appears. I have tried to remove root and try to update without root but the problem persists. I understand that the problem does not come from abl.img.
0.install adb tools on your pc
soooooooooooooooo....I was already on F16. Just wanted to say that all I did wasThe steps are below：
1. upgrade from c66 to F16 & do not reboot
2. magisk patch another slot & do not reboot
3. dd flash abl.img
4. reboot & upgrade
5. you'll got stuck at setupwizard ,if uninstall com.coloros.bootreg ,also you can entered the desktop ,but full screen gestures may not work properly .
6 . reboot to recovery & clear all data ,and everything works well !
The steps are below：