yashsingh1/xdaforums huggingface dataset:
[OnePlus 10 Pro] sykozylot:
Getting a Pro 10 (used). Any setup tips?

Also will mostly be using with with wifi calling T-Mobile USA on a Google Nest mesh network. Anything I should know? Thanks!
[OnePlus 10 Pro] dlads:
Don't get a 10 pro. Best advice I could give you.
[OnePlus 10 Pro] whitey13:
that's helpful...
[OnePlus 10 Pro] dlads:
Read some threads.... The informationis out there, there are better alternatives.

I have never seen a device be abandoned so much.. I'm not going to write everything I've already written again because people won't be bothered to look themselves, the info is there, have a look.
[OnePlus 10 Pro] omega552003:
You must be confused, this device got Android 13 update this summer and just got a big update this week. Very much not abandoned.
[OnePlus 10 Pro] omega552003:
I'm on TMobile US with the NE2215 and it works fine.
[OnePlus 10 Pro] dlads:
Abandoned by developers...100% true... Not only that but oppo/oneplus are locking these devices down. Unlocking the bootloader on the 10T is already an issue.

Think it's you who's confused pal
[OnePlus 10 Pro] GuyInDogSuit:
They're mostly referring to the fact that OnePlus, once developer-friendly, has reversed that stance and with every flagship phone, has found more and more new and exciting ways to make developers' lives a living hell. Hence, no developer support. Meanwhile, OP releases updates that only seem to break things more than anything else. Buyer beware, as they say.
[Touch Diamond, MDA Compact IV Themes and Apps] gobmonster:
A while back this cab was floating around from a samsung install, its piscelbrowser, and nearly the best IMO, but its not friendly to our new screens

The icons arent sized for vga and its really hard to double tap zoom due to the pixel count going up 4 times a qvga device. Can we get a repack with these issues ironed out? Bigger icons and a larger double click area?

Edit* I forgot that this file cannot be shared, am i right?
[Touch Diamond, MDA Compact IV Themes and Apps] the-equinoxe:
Yups you are right..

So I'll close this thread.
[Google Pixel 6 Pro] hanschke:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com
[Google Pixel 6 Pro] fil3s:
I flashed the privacy sandbox beta with flashtool. Seems pretty stable
[Google Pixel 6 Pro] 96carboard:
I think you mean "64 bit only". x64 is a shorthand for x86_64, which is a totally different CPU architecture.
[Google Pixel 6 Pro] hanschke:
thats wrong. x86 is for 32 bit and x64 for 64 bit.
[Google Pixel 6 Pro] 96carboard:
Did you even read what I said? Those are DIFFERENT CPU ARCHITECTURES.

x86 is 32bit x86

x86_64 is 64bit x86.

x64 is SHORTHAND for x86_64.

These phones are ARM CPUs. ARMv7 is 32bit. ARMv8 is 64bit.
[Off-topic] Smotpokera:
Just a question.... Is there any development in the drone industry, especially within the Chinese drone manufacturer DJI where the main focus is looking into the code to see what types of data is being collected and sent to the Chinese Government? ...

Then or also has there been any attempts to root the drones and remotes so that Americans can controls where that data may be sent. Like instead of using DJI.s servers you can send data to your desktops home network through 5g. via different firmware and software that's customisable....

{Mod edit: In reference to rule 2.4 of the forum rules, political content removed. Oswald Boelcke}
[Off-topic] Renate:
Are you using your own phone and the DJI Fly app or like the Mini 3 Pro with the RC (builtin screen).

If you had the RC you could (probably?) just never enable WiFi.

Nah, I don't own one yet. I'm torn between the Mini SE and the Mini 3 Pro and I don't buy anything!
[Off-topic] Smotpokera:
I have a Mavic 2 pro the controller doesn't have a built in screen so i fly with Dji's fly more app.

correct me if I'm wrong, I herd that the drone its self uses a custom version of android for its on bord flight controller. I was wondering if anyone has thought about rooting the flight controller?
[Off-topic] Renate:
I'm not sure what benefit rooting the drone would be, but I'm always interested in analyzing things.

You'd think that they'd be enough semi-destroyed drones around to be able to do a teardown.

I can see the benefit of rooting the builtin hand controllers.
[Off-topic] TravisBean:
Well I blew $1,250 on a DJI mavic Zoom about a year-and-a-half ago and it has magnificent flight characteristics and it's a real pleasure to fly. Unfortunately, I live within two blocks of a no-fly zone and I never get a chance to fly it cuz I have to drive somewhere to fly it. If you do an extensive Google search on the Mavic and no fly zones you'll come across many links to companies that specialize in hacking software for DJI drones. I haven't used any of them so I can't recommend one, but you can certainly find out for yourself. Good luck and report back to us with your findings if you so desire.

Edit: Actually directed @

Smotpokera​
[Off-topic] JohnNokomisClark:
I have the DJI RC Pro Enterprise. The hardware is identical to the standard RC Pro. For some reason, DJI has made this controller unusable with anything other than the Mavic 3 Enterprise. Here's DJIs letter to the FCC confirming the hardware is the same View attachment 5790587How can I force this controller to be compatible with other drones? I've gained ADB access and can install apks along with logcat viewing and everything else. However, if you try to install the DJI Fly app it's blocked by DJI, even through ADB. Any help would be awesome!
[Off-topic] vamsi209:
how did you manage to do that mate?
[Nokia 3.2 Questions & Answers] vewu101:
Does anyone know where I could find the nokia 3.2's kernel source? Nokia doesn't list it on their site.
[OnePlus 9 Pro] UpArrows:
Okay，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

View attachment 5765551

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 :

View attachment 5765553

F.16 contains orange state ,F.11 not.

View attachment 5765555

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 vacation
[OnePlus 9 Pro] UpArrows:
I've uploaded both f.11 & f.16 abl.img to gdrive ,my device is le2125 https://drive.google.com/file/d/1AKivwtKzF2cMXM15TQA1AlQVCpuUy1ck/view?usp=share_link
[OnePlus 9 Pro] UpArrows:
or maybe you'll get bootloop after flash this partition
[OnePlus 9 Pro] Steve0007:
Or a brick that could be maybe recovered by MSM
[OnePlus 9 Pro] TheGhost1951:
Can you open the current able.img and edit out any warning txt info? Or is an image (png or jpg) that gets displayed?
[OnePlus 9 Pro] UpArrows:
it's hex string , i don't know how to repack the img file after modified
[OnePlus 9 Pro] UpArrows:
Finally i flashed f.11's abl.img ,actually it works , no Orange state message text ,but emm , stuck at setupwizard o_O,continue button not work ,i can't enter the desktop ,

View attachment 5766189
[OnePlus 9 Pro] Rootk1t:
As far as i know message about unlocked state comes from bootloader.

OOS11 bootloader has this message, OOS12 hasn't, but OOS13 starting from some build has it again. As you probably identified right, abl.img is a bootloader one.

If oneplus implemented additional checks in bootloader, you will not be able to run one firmware build with bootloader from another, because bootloader allows boot after checks of digital signatures of partitions at minimum: system, vendor, dtbo, boot, vbmeta. If they mismatch boot is not allowed, so you can't just use bootloader from one build on another.

But as OOS13 is relatively new at the moment, additional investigation on the topic should be made to clarify some things.
[OnePlus 9 Pro] UpArrows:
Finally 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 .

View attachment 5766199

View attachment 5766201
[OnePlus 9 Pro] UpArrows:
finally it works ,haha,
[OnePlus 9 Pro] Rootk1t:
So using bootloader from recently released builds is possible.

Thanks for checking!
[OnePlus 9 Pro] Steve0007:
To make it clear, just removing com.coloros.bootreg before flashing DD the beta abl.img should work?

Will flashing DD erase data?
[OnePlus 9 Pro] UpArrows:
I'm recommended to clear all data after updated and flashed abl.img, if not full screen gestures may not work properly .
[OnePlus 9 Pro] UpArrows:
The 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 !
[OnePlus 9 Pro] UpArrows:
Before flash abl.img , use command : getprop ro.boot.slot_suffix to identify currently active slot ，make sure do not flash to current slot .
[OnePlus 9 Pro] Zeus0fyork:
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.
[OnePlus 9 Pro] Steve0007:
Thanks. What is the purpose of restoring boot with magisk and patch the other slot? Did you flash again F16?
[OnePlus 9 Pro] Steve0007:
Can anybody understand the purpose of restoring original boot using Magisk and patching the other slot before replacing the abl.img?

Won't replacing abl.img work as it should w/o having to do 2 and 3 from above instructions?
[OnePlus 9 Pro] UpArrows:
Still works on LE2125_11_F.17View attachment 5774721

View attachment 5774723
[OnePlus 9 Pro] sefai77:
i have LE2123 F72 version,how can i use for this version this methot ?
[OnePlus 9 Pro] Wishmasterflo:
Yes I think so
[OnePlus 9 Pro] Psk.It:
it should, make a backup (in any case)
[OnePlus 9 Pro] b0l5:
but I have OnePlus 8 Pro
[OnePlus 9 Pro] MJPollard:
Then it's probably not going to work. This Magisk module is for the various models of the 9 Pro, not the 8 Pro.
[OnePlus 9 Pro] AstronxD:
From my testing its working on Stock OOS 13, 13.1, 14

Upto 14.0.0.202(EX01)

Also tested working on nameless AOSP android 13 based rom.

I think it works with any ROMS out there released before this comment is published.
[OnePlus 9 Pro] AstronxD:
I'll add it by next week.
[OnePlus 9 Pro] STiLTSKiNRuMP:
Can Confirm, it works for LE2123_14.0.0.501(EX01)
[OnePlus 9 Pro] Psk.It:
do you have a clean abl.img?
[OnePlus 9 Pro] b0l5:
yes

yes
[OnePlus 9 Pro] Psk.It:
so you can try flashing it manually

check commands insidie the .sh files of module to reproduce, if working you can male your own module version

so

running getprop ro.boot.slot_suffix on terminal it should tell you the active slot (_a or _b)

with FILE your img full path and SLOT the previous detected

dd if=$FILE of=/dev/block/by-name/abl${SLOT}

sloud update the abl partition

if it works,

with getprop ro.product.model you can detective the device name (to update the module)
[OnePlus 9 Pro] ananno_here:
Tried on LE2121_14.0.0.600(EX01)

working perfectly (flashed with magisk)
[OnePlus 9 Pro] Chrisch_91:
How to flash the file with magisk?
[OnePlus 9 Pro] bubobih:
How to restore to main one because u cant update if u remove orange state
[OnePlus 9 Pro] TheGhost1951:
If done properly, you would have a backup and just change the name to original and flash it. I believe in the first post guides you in the process.
[OnePlus 9 Pro] Psk.It:
currently the back-up has been removed

for custom rom, flashing the firmware is enought (or just the abl.img, not dure it will work also for OOS)
[OnePlus 9 Pro] Wishmasterflo:
I created an updated Module which should work for the whole Oneplus 8 and Oneplus 9 series and 9R.

DOWNLOAD
[OnePlus 9 Pro] b0l5:
I try on OnePlus 8 Pro, doesn't work.
[OnePlus 9 Pro] Chrisch_91:
Doesn't work on op9p (nameless os, a14).
[OnePlus 9 Pro] Wishmasterflo:
Hmm? What doesnt work, is it giving some error or just not removing the yellow bootloader message? Weird, it should work is I use the same abl file as in my flashable firmware files.
[OnePlus 9 Pro] MJPollard:
Doesn't work on my LE2125 running OOS13 firmware and LineageOS, either. Had to use the older orange state remover from this thread. (Not my primary phone; the screen is cracked, so I use it as a test bed for my custom LineageOS ROM.) I doubt it will work on my LE2127 (TMO converted to global), either.
[OnePlus 9 Pro] Wishmasterflo:
Hmm strange. Have to check what I did wrong. I just added the directories for the other phone models and put the correct abl.img which removes that warning inside of it.

And the same abl files I use in my flashable firmware files and there it works, so must be something I did wrong here.
[OnePlus 9 Pro] b0l5:
yellow waring os remove, but my phone after reboot run in fastboot mode ;/
[OnePlus 9 Pro] xlinux_:
I was doing some reading up on this old method, anyone that is still doing this probably should not now because the abl.img file is pretty old, from the F.11 and could pose security risks or brick device with newer firmwares.

The abl.img is one of the main components of the bootloader so probably don't revert to an old version if you are concerned of functionality etc.
[OnePlus 9 Pro] UpArrows:
that's only for le2125 ,you can try to download le2123 f11 from https://oxygenos.oneplus.net/LE2123_11_F_OTA_2110_all_4a35ee_01000100.zip ,then extract abl.img & flash to your device .
[OnePlus 9 Pro] UpArrows:
And anyone can do a backup of le2125 f17's abl.img ,i've forgot to backup it . haha
[OnePlus 9 Pro] UltimatPronin:
You didn't try to patch abl.img which is present in the firmware to remove the found lines - fill them with zeros? or will it do nothing?
[OnePlus 9 Pro] Molinagalvezvictor:
Tengo la versión LE2123 F72, ¿cómo puedo usar esta versión para esta versión?

Mod translation: I have LE2123 F72 version, how can I use this version for this version?
[OnePlus 9 Pro] Molinagalvezvictor:
Sorry, I'm a bit of a novice, could you tell me the steps one by one so as not to brick the phone?
[OnePlus 9 Pro] UpArrows:
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 ;
[OnePlus 9 Pro] Andsie:
Hi,

does this guide apply to the f.72 rom version, too?
[OnePlus 9 Pro] Molinagalvezvictor:
Thank you very much, this worked for me.
[OnePlus 9 Pro] Andsie:
when extracting payload.bin from OOS13F.72 there is no abl.img - resolved
[OnePlus 9 Pro] aarkee:
Thanks, worked
[OnePlus 9 Pro] Andsie:
after understanding of the whole process - it worked!

Is this to be done anew after a update?
[OnePlus 9 Pro] yassine2217:
easy steps

adb shell

After that, type in the below command to get hold of your current slot:

getprop ro.boot.slot_suffix

If it is A, then execute the following commands [you will get a Magisk prompt after executing the su command, make sure to tap Grant]:

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

(use abl.img from LE2125 OBT F.11 folder in step 8)​

Credit to droidwin
[OnePlus 9 Pro] luckylui:
Will this wipe any data?
[OnePlus 9 Pro] yassine2217:
No
[OnePlus 9 Pro] luckylui:
Thank you! I'll give it a shot later today 😁
[OnePlus 9 Pro] sshriss:
Thanks, I confirm it is working fine on LE2123 F72. I just used the abl.img from the UpArrows post as it is for LE2123..
[OnePlus 9 Pro] Alberhasky:
This is awesome, it'd be amazing if we got someone to help make this a flashable zip
[OnePlus 9 Pro] jotha.dx:
Hi, this post working too for Oneplus 8 pro with OOS13 IN2025 11.F.15?
[OnePlus 9 Pro] Sergykm:
Will it work for LE2125? Why we must do this extract playload.bin with payload_dumper-master? For what?
[OnePlus 9 Pro] Sergykm:
Finnaly it works for me! No orange state message!

Thank you so much, guys!

Greetings from Ukraine!
[OnePlus 9 Pro] UpArrows:
still wroks on le2125 oos f.18
[OnePlus 9 Pro] holydemon:
Do we have to do it all from the beggining with every update or is it a one time solution?
[OnePlus 9 Pro] Sergykm:
Now I cann't install ota update f18))))
[OnePlus 9 Pro] Sergykm:
Finally I updated to f.18

I restored my abl.img.bak, than restored magisk image, than installed ota update, than installed magisk to inactive slot, than installed abl.img from f.11 and finally I have f.18 with root and without orange state message.
[OnePlus 9 Pro] sshriss:
Just tested it on LE2123 F.73 and it works fine.
[OnePlus 9 Pro] sshriss:
I updated to F73 via OTA, then used the F.72 magisk patched boot to root it again and repeated the steps for the abl. I find it easier than restoring images. ;) The issue was that first time, I got an incremental OTA update 190MB and after it failed, I got the full zip 4.33 GB and installed it via OTA. Those guys form OP are killing me. :D

PS: It seems the OTA zip download location changed, and it is no longer the .Ota folder on sdcard, so I could not find where the full zip was downloaded to extract the stock images. So I will wait for the Oxygen updater as it still not detect that update.
[OnePlus 9 Pro] co4:
I just want to confirm this is also working on a normal OP9

LE2113_11_F.73

using

abl from

LE2113_11.C.88
[OnePlus 9 Pro] Aballamis:
I'm on LE2125 global variant in USA, but I have OOS, not colorOS. But I notice you have OOS as well. Is it just they are putting colorOS system apps in OOS?
[OnePlus 9 Pro] Appreciative:
After oos11, OxygenOS is some type of ColorOS OxygenOS remix hybrid. Which is why many of us stay on oos11. This is the new oppo+oneplus merger result. I've heard it's still pretty peppered in on oos13 also. Some people like ColorOS but I don't find that many people that like the hybrid. Maybe they'll unify it for *OS14
[OnePlus 9 Pro] Aballamis:
I'm finding many people not liking most of the new stuff resulting from the OPPO merger. Namely, the refusal to release kernel source or MSMTool for 10 series. I wanted a 10 pro, maybe 10T, but got the 9 pro as I'm not going without custom stuff.

I've been plastering comments all over the OnePlus Community forums, especially quoting and addressing employees and company folks, even Pete Lau. None of them have responded, lol. I just hope they get it together and hopefully make the "right" decision(s) before the OnePlus that many of us, or at least the OnePlus that I personally know and love, is dead and gone. Outlook kinda bleak ATM. Unless something changes in these regards, this 1+9pro will be my last 1+ device. And I'll admit its a little much to be emotional over a phone, but it really does break my heart.
[OnePlus 9 Pro] Appreciative:
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
[OnePlus 9 Pro] TheGhost1951:
Yeah, I'm on TMO and not knowing used the IN MSM tool when bricked. Now target id is IN instead of TMO.... Grrrrr might be a minor deal but it is an irritating one that!
[OnePlus 9 Pro] TheGhost1951:
There ought to be away to change the Target id on our phones. Software changed it, software should be able to correct it!
[OnePlus 9 Pro] ElitePotato:
I am on nameless rom with f.18 firmware. Can I just flash the abl image through fastboot ?
[OnePlus 9 Pro] DirtryElectroOP3:
i tried the f.11 image, worked fine
[OnePlus 9 Pro] ElitePotato:
Yeah it works
[OnePlus 9 Pro] Psk.It:
could be possible to collect the working abl.img?

(just avoiding download 4gb rom for 20mb) thank you
[OnePlus 9 Pro] ElitePotato:
lol it is already shared in the thread

https://xdaforums.com/t/remove-oos13-orange-state-message-text.4520727/post-87749023
[OnePlus 9 Pro] Psk.It:
thank you.

on 2123 F73 shall I apply images you shared?

(the f11, right?)
[OnePlus 9 Pro] ElitePotato:
Yeah just follow the instructions.
[OnePlus 9 Pro] Psk.It:
worked

thank you
[OnePlus 9 Pro] Benji1983:
Hi

I'm on LE2123 f.73

Used the abl f.11

Worked like a charm on termux

No more orange state

Thank you

Greetings
[OnePlus 9 Pro] brmbjn:
How to remove orange state without root. ?
[OnePlus 9 Pro] Steve0007:
Relocking the boolader
[OnePlus 9 Pro] brmbjn:
isn't there any other way besides relocking ?
[OnePlus 9 Pro] ElitePotato:
If you are on custom rom , you don't need to root. Just flash the abl image in fastbootd mode and reboot.
[OnePlus 9 Pro] sshriss:
Just tested it on LE2123_11_F.74, and it still works fine. ;)
[OnePlus 9 Pro] Alberhasky:
How would I restore the backup abi.img?
[OnePlus 9 Pro] Alberhasky:
Hello!!

Do you mind sharing the steps you took to restore your abi.img.bak? I would really appreciate it.

Thank you!!!!