How To Guide Remove OOS13 Orange state message text

[TheGhost1951]

Update to C16 A12 and it will be gone.

 

[immortalwon]

Update to C16 A12 and it will be gone.

I would but I like my stable a11 firmware. No need to change something that's not broken

 

[TheGhost1951]

I would but I like my stable a11 firmware. No need to change something that's not broken

 

[Nimueh]

@Nimueh it does actually, look at this. If someone could make an ABL file that works to skip or remove it, would be cool.

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.

 

[MEIMSGAF]

So 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.

Your only option is to contact Oneplus, because as of op10 there is no longer the MSM tool to recover from the brick

 

[immortalwon]

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.

Thanks for correcting me I always thought that was the same orange message

 

[Psk.It]

Tried it your way and it worked. I'm curious, though, to know what (if any) the difference is between the LE2123 and LE2125 ABLs. Will using the LE2123 one affect how my LE2125 works? No problems so far, but I'm wondering about the long term.

so basically image i supposed to be working only for LE2123 is working for both, LE2123 and LE2125, isn't it?
if so, i'll simplify the script to flash just 1 abl.img file

did I understand correctly?

 

[Nimueh]

It self disable once applied
you should remember to re-enable on ota update

There seems to be a new update for 13.1 rolling out. Can I just use your module again or does anything have to be changed/modified so it works with new updates?

 

[Psk.It]

There seems to be a new update for 13.1 rolling out. Can I just use your module again or does anything have to be changed/modified so it works with new updates?

Unfortunately i think no changes could be applied, or it works or not

You can try, i think it will work untill OP does not chance abl image definition

 

[Nimueh]

Unfortunately i think no changes could be applied, or it works or not

You can try, i think it will work untill OP does not chance abl image definition

I haven't gotten the update yet but sure, I'll try once it reaches the EU lol - thanks for replying

 

[TheGhost1951]

How do I create a magisk module to patch for Orange State for the TMO LE2127 if I have the OS12 abl.img?

 

[TheGhost1951]

Nevermind, I got it done with manual install commands using a partition backup I had of OS12 abl.img.... no more otange state!

 

[frost_icewind]

getprop ro.product.model gives me LE2120

Can I use the magisk module?

 

[Psk.It]

getprop ro.product.model gives me LE2120

Can I use the magisk module?

I don't know
up to you if you want try

or if you remember la test build without the orange state, you can try to.extract abl.img from that rom, try manual install processo, if it works you can copy the abl.img file in the LE2125 module subfolder (in order to automatically reapply when needed)

 

[Ruben.gm]

How can I reverse the process? The software update causes me an error on the 9 pro Le2123. Could it be because of this?

 

[Psk.It]

How can I reverse the process? The software update causes me an error on the 9 pro Le2123. Could it be because of this?

You van try installing abl.img from your latest installed rom
or at worst reset the phone using edl tool

 

[TheGhost1951]

How can I reverse the process? The software update causes me an error on the 9 pro Le2123. Could it be because of this?

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...

 

[TheGhost1951]

How can I reverse the process? The software update causes me an error on the 9 pro Le2123. Could it be because of this?

Fixing to do some testing to fix the error. Will advise the results.

 

[Ruben.gm]

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.

 

[Ruben.gm]

You van try installing abl.img from your latest installed rom
or at worst reset the phone using edl tool

I am unable to find the abl.img file in the oxygenos rom update file. Can you guide me where to find it?