How To Guide Remove OOS13 Orange state message text
- Thread starter UpArrows
- Start date
Steve0007
Inactive Recognized Developer / Retired Forum Mod
If you are on custom rom , you don't need to root. Just flash the abl image in fastbootd mode and reboot.
Hello!!
Do you mind sharing the steps you took to restore your abi.img.bak? I would really appreciate it.
Thank you!!!!
Hello, after this steps you will have abl.img and abl.img.bak on main storage.
abl.img.bak is your original (backuped) abl.
If you want restore it you can rename abl.img.bak to abl.img (before it delete or rename abl.img (modded) to abl.img.bak2 or something else) and follow those steps in terminal again:
su
dd if=/dev/block/by-name/abl_a of=/sdcard/abl.img.bak
blockdev --setrw /dev/block/by-name/abl_a ;
dd if=/sdcard/abl.img of=/dev/block/by-name/abl_a;
if current was slot b ,the flash commands are :
su
dd if=/dev/block/by-name/abl_b of=/sdcard/abl.img.bak
blockdev --setrw /dev/block/by-name/abl_b ;
dd if=/sdcard/abl.img of=/dev/block/by-name/abl_b ;
I know this is a 9 pro thread, but I was wondering if anyone has tried this on a standard OnePlus 9 LE2115?
what to do, when this happens?
PS X:\__Install\__oneplus9Pro> adb devices
List of devices attached
18087faf device
PS X:\__Install\__oneplus9Pro> adb shell
OnePlus9Pro:/ $ getprop ro.boot.slot_suffix
getprop ro.boot.slot_suffix
_a
OnePlus9Pro:/ $ su
su
/system/bin/sh: su: inaccessible or not found
PS X:\__Install\__oneplus9Pro> adb devices
List of devices attached
18087faf device
PS X:\__Install\__oneplus9Pro> adb shell
OnePlus9Pro:/ $ getprop ro.boot.slot_suffix
getprop ro.boot.slot_suffix
_a
OnePlus9Pro:/ $ su
su
/system/bin/sh: su: inaccessible or not found
Last edited:
Hello,
After received a advising from OnePlus, i just have successfully flashing directly with "OPLocalUpdate_For_Android12.apk" my rooted "OnePlus Nord CE 5G 256GB" from "OxygenOS_EB2103_11C10=Android v12.1" up to "OxygenOS_EB2103_11F06 Android=v13.0" with the official ROM package, but after that it show me at the boot screen the following message in yellow :
<
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
>
Q : How can i safely get it removed ?
Thank's in advance ...
After received a advising from OnePlus, i just have successfully flashing directly with "OPLocalUpdate_For_Android12.apk" my rooted "OnePlus Nord CE 5G 256GB" from "OxygenOS_EB2103_11C10=Android v12.1" up to "OxygenOS_EB2103_11F06 Android=v13.0" with the official ROM package, but after that it show me at the boot screen the following message in yellow :
<
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
>
Q : How can i safely get it removed ?
Thank's in advance ...
How To Remove Orange State Warning On OnePlus Android 13 ?
I saw the topic: https://forum.xda-developers.com/t/remove-oos13-orange-state-message-text.4520727/ + https://www.droidwin.com/how-to-remove-orange-state-warning-on-oneplus-android-13/ In case I clearly understood from the comments, it works...
forum.xda-developers.com
Still works on LE2125 F.21. I dumped the C.48 images myself using payload-dumper-go and flashed the abl with fastboot, although you can probably use the images in this thread. I guess the ColorOS merge caused this, pretty funny that they left out the Orange State warning.
Mind sharing your abl file with me? Ill even take a link to the payload file you used, I am on LE2123 F.21 myself.
Thanks!
If you check the pinned threads in the OnePlus 9 Pro section, you'll find a thread for all firmwares. Find any one of the C.* firmwares (I chose 48), and download the zip. After extracting the zip, you'll see the payload.bin, and you can use payload-dumper-go to extract the imgs and flash the abl
Similar threads
- Sticky
- Locked
Top Liked Posts
-
1
the abl image should be the latest build without the orange message, not latest build -
11
yes, as shown here,
detect the acrive slot, check device model
for LE2123 abl is took from F11build, all others from F16
the plus is just to re-apply the patch from magisk with a single tap1
the abl image should be the latest build without the orange message, not latest build -
10Finally finally it works ,Congratulations, while i stuck at setupwizard ,i use command :dumpsys activity top | grep ACTIVITY found com.coloros.bootreg/.security.activity.AgreementPage a996400 pid=4001 Prevent i enter the desktop ，so use command am force-stop com.coloros.bootreg stop this activity ,but it restart automaticly ,then i use command: pm uninstall --user 0 com.coloros.bootreg uninstall package com.coloros.bootreg , haha, successfully entered the desktop ,and there is no Orange state message text on boot now .
9Okay，while you upgrade your op9pro to oos 13 ,and unlock your phone ,you'll got Orange state message , F.16 is upgrade from F.11 ,so ive extract both F.11 & F.16 playload.bin ,and compared each partition of them : those red bleow are different partition between OOS 13.0.0 F.16 and OBT OOS 13.0.0 F.11
so ,which partition contains orange state messages ?
i'm worked for a while try to figure out ,finally ,after extract abl.img ,i got LinuxLoader , use winhex to search key word Orange :
F.16 contains orange state ,F.11 not.
maybe flash F.11's abl.img partition would remove the orange state message text ?
anyone could have a try ? haha ,i'm not sure ,i only have one phone ,I‘ll try it when I am on vacation9
0.install adb tools on your pc
1.unlock your phone and root your phone with magisk
2.download f.11 from https://oxygenos.oneplus.net/LE2123_11_F_OTA_2110_all_4a35ee_01000100.zip
3.extract playload.bin with payload_dumper-master , and copy abl.img to your phone /sdcard directory
4. connect your phone to pc
5.open windows terminal ,type adb shell ,use command getprop ro.boot.slot_suffix to get current slot tag , if current was slot a ,the flash commands are :
su
dd if=/dev/block/by-name/abl_a of=/sdcard/abl.img.bak
blockdev --setrw /dev/block/by-name/abl_a ;
dd if=/sdcard/abl.img of=/dev/block/by-name/abl_a;
if current was slot b ,the flash commands are :
su
dd if=/dev/block/by-name/abl_b of=/sdcard/abl.img.bak
blockdev --setrw /dev/block/by-name/abl_b ;
dd if=/sdcard/abl.img of=/dev/block/by-name/abl_b ;9
soooooooooooooooo....I was already on F16. Just wanted to say that all I did was
1. Got abl.img from F11 and placed at /sdcard
2. Restore images from Magisk
3. Magisk patch to other slot
4. got into a root shell and ran "blockdev --setrw /dev/block/sde13" and "dd if=/sdcard/abl.img of=/dev/block/sde13"
5. Rebooted
no longer have orange prompt and everything is working normal.6
I'm with you. I've made a dozen posts here and reddit with the same thoughts. OnePlus became successful because of us 'techies' having a great experience and putting our friends and family onto OnePlus devices. That's gone now. I told my techie friend to get a 9 pro if anything and I'm telling everyone else to wait. I've been thru samsung and Nexus and Pixel devices. No plans to go back to them. I have a lot of hope in Nothing Phone 2/3 or maybe I'll just get another 9P and stay on oos11 for eternity. It is really sad, I'm with you. We are all with you.
I bought a 10T and didn't know the msm situation. I thought maybe I could work around that since I just need root and don't tend to custom rom. The problem was, oos12 on the 10T was absolute trashcan sauce. I couldn't get over the bad UI AND no msm/development happening. It doesn't feel like a premium device coming from a 7/8/9Pro but I was willing to ignore that too. It wasn't enough for me to stay. I reset it, relocked the bootloader, bricked it (forgot to flash stock boot image back after reset lol). I sent it back and waited 5+ weeks for a refund as their new customer service is also trash can soup. Our real beloved OP is dead.
The 9p will live on for a good while, especially with finds like this thread. I was tempted to replace my 7tp5g screen and battery for $200ish but I may just get another 9P for whenever this one dies.
Sorry we hijacked the thread a bit. Orange text removal is really quite great. Maybe we can conquer everything for the 9P in time. Dual sim in the Tmo model working part time, there must be a way to make it work. The Indian MSM tool changing target ID to IN, there must be a way to undo that too.
One find at a time, I'll be here for a while
