yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
Updates

21/11/22 - Released the XDA thread as a guide to remove the ugly "Your device has been unlocked" message for the OP8 Pro

Not sure if this method does work, but I have contacted ROM developers and they say this is the way...

I'm currently not on OOS 13 based ROM, so I can't try and hopefully this does work :)

21/12/22 - It has been a month and after checking with devs + testers the method does work!

I have tested the method myself

I have updated the method as there's new steps you need like flashing abl.img in both slots

But the method does work on OOS 13 based ROMS! The message can be removed! 🥳

22/12/22 - I have found the method that works on Stock OOS 13 thanks to @MeHigh.G

Stock OOS 13 users should be able to remove the bootloader unlocked message

Added new OOS 13 F.10 abl.img file and removed OOS 12 C36 abl.img due to F.10 being newer to ensure users have a newer bootloader

Credited Bowow for giving the F.10 abl.img file for OP8/8 Pro

5/1/23 - Updated methods to flash abl.img in both slots easily instead of flashing abl.img in one slot

Changed "fastboot flash abl abl.img" to " fastboot flash --slot=all abl abl_filename.img " which will flash abl.img in both slots.

For custom ROM method, you will no longer need to reboot and switch slots with the new command
[OnePlus 8 Pro  Guides, News, & Discussion] MeHigh.G:
Nice!
[OnePlus 8 Pro  Guides, News, & Discussion] gregpilot:
Hello!

Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?

Thank you

Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
[OnePlus 8 Pro  Guides, News, & Discussion] ShadoV90:
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.

Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.

EDIT: i found this topic here

Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
That's for the OP9 Pro not the OP8 Pro...

I only learned about this from the dev @HELLBOY017 and it worked for him. He never stated u needed a data wipe.

So I did check that it was working otherwise I would never post something that wouldn't work and wasn't tested.

And I did say.... *I am not responsible for bricked devices, damage to your device* I am here to post my method for anyone who is interested.

I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.

It was from EU OOS 12 C36 full zip

We'll see how it goes as this is new for 8 Pro users and hopefully it does work

Thanks for the reminder of the missing info to include
[OnePlus 8 Pro  Guides, News, & Discussion] ShadoV90:
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.

Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.

We don't even know possible bad outcome. That's all.

And to be clear...

I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
Never considered it as an attack, just posting to clarify where I got this info and everything from.

I only found out about this yesterday from Hellboy017 and it worked for him.

I would recommend this only for users on OOS 13 just to be safe

If something does go wrong, follow the link by @ShadoV90

Do a factory reset or use MSMDownload Tool
[OnePlus 8 Pro  Guides, News, & Discussion] Neil_Armstrong_:
thanks for the tip, i'll check it out asap

Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')

we might have to use the --force argument in the fastboot command

try at your own risk
[OnePlus 8 Pro  Guides, News, & Discussion] ShadoV90:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".

Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.

Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.

Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):

fastboot flashing unlock_critical

Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
[OnePlus 8 Pro  Guides, News, & Discussion] Neil_Armstrong_:
the flashing unlock_critical output is the fastboot help, i guess it's not working

I will try again saturday on Linux to see if it helps
[OnePlus 8 Pro  Guides, News, & Discussion] MeHigh.G:
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!

But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.

I talk from experience! And BTW just did that a minute ago.
[OnePlus 8 Pro  Guides, News, & Discussion] Neil_Armstrong_:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
[OnePlus 8 Pro  Guides, News, & Discussion] b0l5:
so this work or not?
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
There's no custom recovery currently for OOS 13... Only for custom ROMs
[OnePlus 8 Pro  Guides, News, & Discussion] MeHigh.G:
I use oFox or the one provided with Flamingo OS or Pixel Blaster
[OnePlus 8 Pro  Guides, News, & Discussion] STALKER18:
so the steps are :

1- extracting the abl file from the rom we are running using paylaod.bin.

2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.

3- booting from there to fastboot

4- flashing the abl file.

right .?
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
I've already extracted it for the 8 pro... Up to u

For step 4 it's fastboot flash abl abl.img
[OnePlus 8 Pro  Guides, News, & Discussion] wtf!!droid:
i'm unable to unlock bootloader says command not supported in default implementation.

IN2021 One plus 8 pro.
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
U need to have a unlocked bootloader before doing any of this
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
Updated the method!

I have tested it myself! But it works on OOS 13 based ROMs and stock OOS 13

This obviously not for OOS 12 based ROMs as the message is removed in OOS 12 😂
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
You need to be on an OOS 13 based ROM sadly...

I'll ask and see if u can remove the message on stock OOS 13
[OnePlus 8 Pro  Guides, News, & Discussion] wtf!!droid:
i'm on oxygen os. Oneplus ****ed up everything
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
New update

Added new method for stock OOS 13 users to remove the bootloader unlocked message
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
I found and added a new method for stock OOS 13 users.

It has been tested and does work :)
[OnePlus 8 Pro  Guides, News, & Discussion] Kuronosu:
Thank you so much for this. It worked like a charm ♥

I'm using:

- OnePlus 8 Pro (EU) (IN2023)

- LineageOS 20 (2023.02.26) (Android 13)

- Drivers: OxygenOS 13 (F.62)

- Root (Magisk Canary 25208)
[OnePlus 8 Pro  Guides, News, & Discussion] bebop80:
Hello everyone,

I tried to follow the instructions but I get this message:

error: Could not check if partition abl has slot all

Am I doing something wrong?
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
Are u in fastbootd mode? fastboot reboot fastboot?

The command is fastboot flash --slot=all abl abl_filename.img
[OnePlus 8 Pro  Guides, News, & Discussion] Spusuf:
No F.13 firmwares :(
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
What? Wrong XDA thread
[OnePlus 8 Pro  Guides, News, & Discussion] bebop80:
Hello, thank you for your reply and please forgive my late answer.

I did again the procedure, all went ok on the pc, no problem at all, but it seems that nothing has happened as after the reboot I still have the annoying message.

I am on European Oneplus 8 pro OOS13 F15 Original.

Anyway I appreciate your help and efforts :-) thank you so much!
[OnePlus 8 Pro  Guides, News, & Discussion] parenne:
great job. oneplus 8 pro OOS 13 IN f13 no orange messages. Thanx
[OnePlus 8 Pro  Guides, News, & Discussion] jotha.dx:
Working Perfectly here too with oos13 IN2025_11.f.62. Thanks!
[OnePlus 8 Pro  Guides, News, & Discussion] @muja@:
Mates,will that work on oneplus 8T cRdoid 9.2 ??
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
Did u even check the mediafire link? It has the KB abl.img file for the Op8T, so it should work too

MediaFire

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[OnePlus 8 Pro  Guides, News, & Discussion] AidenDRJr:
i am on cos 13 f.63

what link should i check
[OnePlus 8 Pro  Guides, News, & Discussion] bebop80:
Thank you! I did try again the procedure and it worked perfectly! thank you very much!
[OnePlus 8 Pro  Guides, News, & Discussion] tfae:
It seems that it is not working on OOS13 F.63:
[OnePlus 8 Pro  Guides, News, & Discussion] b0l5:
yep i have this same

OnePlus 8 Pro IN2023

Oxygen 13

IN2023_11_F.63

PS C:\Android> fastboot devices
a6fedb33 fastboot
PS C:\Android> fastboot flash --slot=all abl IN20XX_abl.img
fastboot: error: Could not check if partition abl has slot all

hmm maybe rename slot=all to slot=a and slot=b?

/// works!
[OnePlus 8 Pro  Guides, News, & Discussion] b0l5:
1. adb reboot bootloader

2. fastboot devices

3. fastboot reboot fastboot

4. fastboot devices

5. fastboot flash --slot=all abl IN20XX_abl.img

@tfae

​
[OnePlus 8 Pro  Guides, News, & Discussion] tfae:
Still returning with the same error on F.64:

fastboot: error: Could not check if partition abl has slot all
[OnePlus 8 Pro  Guides, News, & Discussion] sgeoxd:
So for the reboot process. After executing step 3 get nothing but a Fastboot logo, waiting several minutes doesn't make a difference. Able to reboot into the system, recovery, or back into Fastboot.

Went ahead and tried the commands to install after reaching step 2. Duplicate the "Could not check if partition abl has slot" whether specifying all, a, b, or removing the slot parameter altogether.

Would venture to guess several of us remain in the wrong fastboot mode. If we can figure out how to do that would likely address the error messages.
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
Are u on OOS?

Or if you're on a Custom ROM, u have to be on the ROM recovery, not a custom recovery
[OnePlus 8 Pro  Guides, News, & Discussion] Nimueh:
On my 9P I wasn't able to get into fastbootD either, I always ended up in TWRP with an error message.

So I simply used Firmware Flasher (and the file with my current OOS version) - it put the same firmware on both slots AND got rid of that annoying orange state warning. No data lost either, root and full device setup was still there. :cool:
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
U have to be on the stock recovery not have a custom recovery installed
[OnePlus 8 Pro  Guides, News, & Discussion] Nimueh:
Yea someone in the Telegram group told me that too, but too late. Doesn't matter now, I sorted it with the Firmware Flasher.

I already had TWRP installed and rooted the device, there was no way I was going back and starting all over just to flash a file in fastbootD when I had another option 😇 :D
[OnePlus 8 Pro  Guides, News, & Discussion] rwub7007:
I see this worked for the IN2023...

Can anyone give me any peace of mind before I do this? That orange message is buggin me buti right now I've got this sucker running beautifully. I don't want to eff it up.. again. 😂

I've got almost the same setup..

Pretty sure recovery is not stock. Lineage is all over it.

- OnePlus 8 pro ( Global IN2025)

- Lineage OS 20 (20-20230611-NIGHTLY-instantnoodlep. 6-11-2023) Android 13

- Drivers (idk how to find which F. Version)

- Root (magisk 26.1)
[OnePlus 8 Pro  Guides, News, & Discussion] Kuronosu:
Still working for me ☺️
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
It worked for me especially as I own a IN2025 model...

The abl works on any 8 pro model and just follow each step

Stock lineage recovery works

About the recovery part, I'm just talking about totally custom recoveries that aren't custom ROM ones.

Like TWRP and OrangeFox

"If you're on a custom ROM that'll be the ROM recovery"
[OnePlus 8 Pro  Guides, News, & Discussion] rwub7007:
finally took a deep breath and went through with it.. lol, all 2 seconds it took to actually flash it.

went through just fine! orange state gone.

thanks guys!
[OnePlus 8 Pro  Guides, News, & Discussion] rwub7007:
i dickered with my phone too much and needed a reinstall.

just updated to most recent lineage - this method isnt working for me anymore. I get stuck at "waiting for device"

fasboot devices shows the device recognized -

lineage lineage-20.0-20230716

same setup as listed above.

any suggestions?
[OnePlus 8 Pro  Guides, News, & Discussion] shpitz461:
Hi, I'm on stock F.63 IN2025, getting same errors as above:

fastboot flash --slot=all abl IN20XX_abl.img

And if I try to a specific slot I get this error:

fastboot flash --slot=a abl IN20XX_abl.img

I'm on stock firmware with Magisk and xXx magisk ROM.
[OnePlus 8 Pro  Guides, News, & Discussion] ShadoV90:
I misread that post and needed to edit... now twice xD

wait... i'm on 13.1 so it seems fastboot mode changed... so nevermind

my fastboot options:

reboot reboot device normally

reboot-bootloader reboot device into bootloader

---> Earlier versions needed only fastboot reboot fastboot to unlock critical partitions flash.
[OnePlus 8 Pro  Guides, News, & Discussion] devildogwillbur:
So this does work for 13.1 and are the instructions the same?
[OnePlus 8 Pro  Guides, News, & Discussion] ShadoV90:
I don't know sincerely. For me this message isn't annoying, so i didn't try to remove. IF somehow fastboot changed, then i don't recommend risk, until you know how to rescue your phone.
[OnePlus 8 Pro  Guides, News, & Discussion] Nimueh:
You could simply use firmware flasher, at least if you have a custom recovery installed or can boot one. I did that on my 9P after I got it and it worked flawlessly.

Not only does it remove the orange warning but you'll also have your firmware on both slots and will be all set in case you want to switch to a custom rom :cool:
[OnePlus 8 Pro  Guides, News, & Discussion] Lanchon:
oneplus 8 pro global/US:

works fine with latest firmware (OOS13.1_F67) and latest lineageos.
[OnePlus 8 Pro  Guides, News, & Discussion] Kuronosu:
@Extreme_Ninja2099, I was wondering if you could maybe explain, what exactly you did to the abl.img to have the message gone? Or if you didn't do it yourself, if you know what the difference between stock and modified abl.img is and how to replicate.

Since this works fine with my OnePlus 8 Pro European version (IN2023), I was hoping to do the same with more recent abl.img files, especially for other devices, e.g. OnePlus 11 (OxygenOS 13.1).

Thank you! 🥰
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
I didn't do anything to the modified abl.img. It's from OOS 13 F.10 beta build.

If u actually flashed the F.10 abl.img and read the whole purpose of this thread u would know what is the difference between the current abl and F.10 abl.imgs

"To remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro."

I would not edit or change the abl.img for the OP11 or any OP device that didn't have a abl.img that doesn't have the bootloader unlocked message.

I didn't edit or change the abl.img as stated in the credits...

I would recommend asking the developers for the op11 if it is possible to edit the abl.img to remove the message

I hope that answers all your questions

Credits:

@HELLBOY017 For the method and using abl.img to remove the bootloader unlocked message

@MeHigh.G For his method on flashing abl.img on stock OOS 13

@bowow For this F.10 abl.img for OP8 and 8 Pro
[OnePlus 8 Pro  Guides, News, & Discussion] MeHigh.G:
You need to be in FastbootD.

To get to fastbootD, reboot the device in Bootloader then type fastboot reboot fastboot.

Then do your fastboot flash -slot=all abl abl.img

If you are on a custom recovery go to recovery and select reboot in FastbootD.
[OnePlus 8 Pro  Guides, News, & Discussion] Kuronosu:
Ah, I see, then I misunderstood, sorry. I thought someone took the stock abl.img and edited out or replaced the message.

Thank you for clarifying ☺️
[OnePlus 8 Pro  Guides, News, & Discussion] Lazar81:
Works like a charm - but only with the custom rom/recovery method. On stock it was a pain and refused to perform the fastboot commands. I installed lineageos and followed the custom rom steps - and message is gone. Thank you very much.
[OnePlus 8 Pro  Guides, News, & Discussion] Extreme_Ninja2099:
If you're on a custom ROM then u would use the method that's for custom ROMs.

The stock method is for users on stock OOS (Oxygen OS)
[OnePlus 8 Pro  Guides, News, & Discussion] Lazar81:
I know that. And followed the steps for stock when I was on stock. It just didn't work.
[OnePlus 8 Pro  Guides, News, & Discussion] tfae:
I confirm that for me it doesn't work too, on stock ROM.
[OnePlus 8 Pro  Guides, News, & Discussion] aygul12345:
How to go to stock? While running a Oneplus 8 Pro with Evo x ROM (Android 13) on it?
[OnePlus 8 Pro  Guides, News, & Discussion] JohnnyJEL:
for anyone having issues with flashing with fastboot you can flash it manually with dd using

adb shell

dd if=IN20XX_abl.img of=/dev/block/by-name/abl_a
dd if=IN20XX_abl.img of=/dev/block/by-name/abl_b

Edit: before you do the dd commands you need to run

su

to enter the commands as root
[OnePlus 8 Pro  Guides, News, & Discussion] b0l5:
@Extreme_Ninja2099 could you make new file abl.img? Becouse I try install your file after March update and didnt work. So I quess they something change. Anyway I attach stock file. Version EU.
[Samsung Galaxy S10 5G Questions & Answers] WherE mE weeD:
Latest F/W on my S10 5g drains battery, I have tried wiping and testing new battery still drains anybody have any suggestions?
[MDA III, XDA III, PDA2k, 9090 ROM Development] denyerec:
Hi chaps,

I'm using the WM6.1 CEOS 5.2.20758 Build 20758 Aku 1.4.1 ROM frm the stick on this forum, and have been using ArcsoftMMS_5.0.70.24 with the MMS_enable cab.

However, when I receive and MMS it's always 4k and the image is very small, maybe some 80px on the longest side tops, even though my sister (Who was sending the image) tried sending both the 2mp original, and a 640x480 resized version.

I've tried both auto and manual MMS download, with the image size settings set both to VGA and original and the result is always the same.

Some googling revealed the following thread:

http://xdaforums.com/archive/index.php/t-404644.html

Which suggested that the MMS might be downscaled if my operator can't identify the handset. Only difference being is I'm on Vodaphone PAYG (UK) and not O2.

Does anyone have any suggestions? I managed to receive a normal-sized MMS before upgrading from WM4.x so the idea of the handset idenfitication might not be too far off the mark.

Kind regards,

Denyer
[MDA III, XDA III, PDA2k, 9090 ROM Development] denyerec:
It appears that reverting back to arcsoftmms_5_0_31_7_us.cab found on this forum has solved the issue, as far as I can tell anyway... I get a warning when installing this version saying that it was designed for a previous version of Windows, but it seems to operate ok.

If anyone has any insights on why the most recent version would have screwed up I'd love to know.

Many thanks,

Denyer
[OnePlus 10 Pro] Dragonzord94:
I have encountered a two year (?) Android lock screen glitch on the 10 Pro. I enter the correct pin and it takes it as incorrect. Now, I am locked out for 24 hours at a time. There's no allowance for me to use face unlock or finger print unlock. Encountered the glitch shortly after coming back from a vacation where I have captured 150+ GB of media chronicling my family and I. I cannot afford to lose these pictures and videos so looking for any help in getting my data off/phone unlocked. OnePlus official tech support is horrible and Google has no support on this. It's pretty crappy so looking for a needle in the haystack. Been stuck for two months and a friend recommended this site!
[OnePlus 10 Pro] blackhawk:
Use a data recovery specialist that has worked with that brand before successfully. That's your best shot if really need the data.

I never use screen locks or set bios passwords, you see why now. You are the one most likely to be locked out sometimes through no fault of your own. Redundantly and regularly backup critical data. NEVER encrypt data drives.

Having expandable storage helps too if you use the SD card as an unencrypted data drive. I also use two 500gb OTG flashsticks for "dirty" backups, main backups are on hdds.

All you can do sometimes is to learn from your mistakes... and not repeat them.
[OnePlus 10 Pro] dlads:
Could maybe try resetting system, that'll leave your storage intact?

May be a Fastboot command to kill the kitchen but I'm not sure,, there used to be a file you can delete from twrp but we unfortunately don't have a custom recovery yet.

In future, install the mod I offered in another thread that allows unlimited Google photos backup..

Have you checked your Google photos to see if anything was backed up?

Google Photos: Edit, Organize, Search, and Backup Your Photos

Edit and enhance photos with AI-powered features like Magic Editor and Magic Eraser on Google Photos. Store, organize & search your memories.

google.com
[OnePlus 10 Pro] Dragonzord94:
Hey Blackhawk and dladz. Thanks for the advice! Will attempt to find a data recovery specialist. Thanks for suggesting this as there seems to be some hope that data recovery is doable for a locked phone!

Unfortunately, nothing is backed up to Google photos. It happened just after my trip and I didn't get the chance to back up. Surely in the future,I will not use a password.

If I can't get the data off, is there any possible chance to file a lawsuit against Google?
[OnePlus 10 Pro] dlads:
A lawsuit against Google? You'd have a hard time buddy...it'll be challenging to get the data from a locked phone..

What about connecting your phone to WiFi whilst it's locked and seeing if Google photos syncs and backs up?

Have you checked if photos has been syncing? It'll do it automatically if you've ever accessed and advised the app to back up automatically
[OnePlus 10 Pro] blackhawk:
A OTG .5tb flashstick or two could have backed them up. Too much backup is a good thing.

Less Google is good. I use Gmail and that's it for anything that's cloud based.
[OnePlus 10 Pro] g96818:
try this https://techcrunch.com/2022/11/14/android-lock-screen-bypass-google-pixel/

op is fairly slow with security patches so you might be in luck
[OnePlus 10 Pro] dlads:
That's clever...I like it