Develop Bugs

[ROOT] Request for tester

Hi all,
I've generated root-ing boot.img for Pixel C, based on my root ( http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ):
Based on latest factory image (MXB48K)
The boot.img is available at http://superuser.phh.me/nexus/ryu/MXB48K/
There are three interesting variants: eng, noverity, nocrypt.
- eng is "standard" version with crypted /data, and dm-verity enabled for /vendor and /system
- noverity only has dm-verity on /vendor and /system disabled
- nocrypt has both dm-verity and crypted /data disabled.
The process to flash it is:
- Go in Settings, Developer settings, tick "Allow OEM Unlock"
- Reboot to fastboot mode
- fastboot oem unlock
- fastboot boot boot-su-eng.img
- install phh's Superuser from Play Store ( https://play.google.com/store/apps/details?id=me.phh.superuser ) (or FDroid)
- And if it works, to really install it, do fastboot flash boot boot-su-eng.img
This is working, thanks to everyone here, especially @cheep5k8

I might be getting my usb type c cable today! If I do I'll definitely test this out!

Potential tester
phhusson said:
Hi all,
I've generated root-ing boot.img for Pixel C, based on my root ( http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ):
Based on latest factory image (MXB48K)
The boot.img is available at http://superuser.phh.me/nexus/ryu/MXB48K/boot-su-eng.img
The process to test it is fastboot oem unlock, fastboot boot boot-su-eng.img and then install phh's Superuser from Play Store ( https://play.google.com/store/apps/details?id=me.phh.superuser )
And if it works, to install it, do fastboot flash boot boot-su-eng.img
Can someone test it for me on a Pixel C?
Thanks
Click to expand...
Click to collapse
I take it you don;t have a Pixel C to test yourself? Just got one yesterday and a type c cable today, adb working fine. Not sure I want to be guinea pig though :-\

the unlock command on the pixel c is the same as the 6p

CharlesW123 said:
I take it you don;t have a Pixel C to test yourself? Just got one yesterday and a type c cable today, adb working fine. Not sure I want to be guinea pig though :-\
Click to expand...
Click to collapse
You can do fastboot boot nameoffile.img
It won't change anything .. Fastboot flash flashes to memory
Sent from my Nexus 6P using Tapatalk

I wish this device came with a data cable. I would've already tested this if it wasn't for that.
Sent from my Pixel C using Tapatalk

This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.

ericvh said:
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
Click to expand...
Click to collapse
Tried flashing to recovery image and booting from that, but also didn't seem to work - I think ultimately it just dumped me into normal boot.
Maybe part of the problem is the double-clutch bootloader, what loads first isn't fastboot -- its something else. Looking at headers in the recovery image, seems like maybe a chromeos loader?
Also tried to just go ahead and flashboot flash boot boot-su-eng.img, but its complaining about multiple of block size:
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.047s]
sending 'boot' (9413 KB)...
OKAY [ 0.257s]
writing 'boot'...
(bootloader) writing flash
FAILED (remote: image not multiple of block size)
finished. total time: 0.342s
I got around this with some rounding, but maybe that's what is screwing up for me.

Well you weren't supposed to flash it until you booted it first to make sure it worked.
The obvious fix would be to flash the stock boot and recovery then factory reset in recovery. Then try again from a clean slate with encryption turned off.
Sent from my iPhone using Tapatalk

ericvh said:
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
Click to expand...
Click to collapse
Interesting.
Have you done the fastboot flashing unlock? (some devices might allow fastboot boot without fastboot flashing unlock)
(Or oem unlock?)
Did the unlock forced factory reset?
I guess flashing back stock boot.img made everything back working?
What have you done to go past the rounding error?
Please note that this boot.img is signed, so rounding it shouldn't be just appending zeros to the end (though it might be interesting to test withotu signing)
This bootloader is really interesting.
It shows the bootloader has been done by Chrome team, which is amazing news compared to N9's HTC crappy bootloader.
This means that actually most (all?) of the source of the bootloader is available in chromium os tree, to better understand what happens.
Thanks for your tests
Edit 1: Ok, the bootloader is:
git clone https://chromium.googlesource.com/chromiumos/third_party/coreboot -b firmware-smaug-7132.B
Edit 2: I'm not seeing anywhere where fastboot could be handled...

If this isnt tested and what not when I get mine I'm sure I could try it
But...google screwed me and sent it overnight tonight but fedex is saying its not coming until tuesday...

superchilpil said:
Well you weren't supposed to flash it until you booted it first to make sure it worked.
The obvious fix would be to flash the stock boot and recovery then factory reset in recovery. Then try again from a clean slate with encryption turned off.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Indeed, I tried the vanilla boot first following the instructions exactly, I just did the flash to see if that made a difference after the 'test' boot failed. It was easy enough to reflash with a recovery image. It does seem to be the case that booting with fastboot somehow messes with whatever encyrption is being used on the user data. Although perhaps the 'flashed' boot just didn't get far enough to trip over it.
---------- Post added at 06:13 AM ---------- Previous post was at 06:09 AM ----------
I have not tried fastboot flashing unlock yet, oem unlock is done however - that did force a factory reset, but from what I can tell Marshmellow always enforces an encrypted image. I got past the rounding error by appending zeros as you suggest. flashing back stock boot.img restored the device to normal use.
There appears to be a two stage boot, when I boot into the bootloader it has an option to enter fastboot, enter android recovery (which doesn't work), enter usb recovery (which doesn't work) and continue with the boot process. Neither fastboot nor ADB interact with the system when its in this state. Once I'm in fastboot mode on the tablet, I can see interact with fastboot. Its also worth noting that despite enabling developer mode, I can't see the tablet with adb when running.
phhusson said:
Interesting.
Have you done the fastboot flashing unlock? (some devices might allow fastboot boot without fastboot flashing unlock)
(Or oem unlock?)
Did the unlock forced factory reset?
I guess flashing back stock boot.img made everything back working?
What have you done to go past the rounding error?
Please note that this boot.img is signed, so rounding it shouldn't be just appending zeros to the end (though it might be interesting to test withotu signing)
This bootloader is really interesting.
It shows the bootloader has been done by Chrome team, which is amazing news compared to N9's HTC crappy bootloader.
This means that actually most (all?) of the source of the bootloader is available in chromium os tree, to better understand what happens.
Thanks for your tests
Edit 1: Ok, the bootloader is:
git clone https://chromium.googlesource.com/chromiumos/third_party/coreboot -b firmware-smaug-7132.B
Edit 2: I'm not seeing anywhere where fastboot could be handled...
Click to expand...
Click to collapse

ericvh said:
[/COLOR]I have not tried fastboot flashing unlock yet, oem unlock is done however - that did force a factory reset, but from what I can tell Marshmellow always enforces an encrypted image. I got past the rounding error by appending zeros as you suggest. flashing back stock boot.img restored the device to normal use.
There appears to be a two stage boot, when I boot into the bootloader it has an option to enter fastboot, enter android recovery (which doesn't work), enter usb recovery (which doesn't work) and continue with the boot process. Neither fastboot nor ADB interact with the system when its in this state. Once I'm in fastboot mode on the tablet, I can see interact with fastboot. Its also worth noting that despite enabling developer mode, I can't see the tablet with adb when running.
Click to expand...
Click to collapse
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)

I am welcome to testing. Just got my Pixel C and would love to help achieve root thank you for your work thus far and if needed let me know what I can do!

Okay, will give unsigned a shot. About to jump on a plane to Europe so I may not be as responsive (and less likely to want to factory reset) for about a week.
I was speaking of android developer mode, not aware of any chromeos development mode. Depending on level of "commitment" I may consider just going for coreboot to Linux and ditching android all together. I'm assuming I can probably prototype that on my JTX1 which has a serial port and then prep images for the Chromebook -- but that would mean ditching android altogether which in some ways would be a shame. Dual boot is definitely the preference for me at the moment.
phhusson said:
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
Click to expand...
Click to collapse

ericvh said:
Okay, will give unsigned a shot. About to jump on a plane to Europe so I may not be as responsive (and less likely to want to factory reset) for about a week.
Click to expand...
Click to collapse
Ok no problem.
I was speaking of android developer mode, not aware of any chromeos development mode. Depending on level of "commitment" I may consider just going for coreboot to Linux and ditching android all together. I'm assuming I can probably prototype that on my JTX1 which has a serial port and then prep images for the Chromebook -- but that would mean ditching android altogether which in some ways would be a shame. Dual boot is definitely the preference for me at the moment.
Click to expand...
Click to collapse
That's unrelated, but I think I'll probably buy a Pixel C when we'll see first non-Android development (Or I might jump straight to it, I already did it for good old Toshiba AC100)
I almost expect Google to publish a ChromeOS image for Pixel C, or at least see an official Chromium OS....
Considering you definitely sound like the hacker-type. How does the keyboard feel? Do you feel you could code hours-long on it?
Also, since there is "usb recovery" mode, I think you could always dual-boot back to Android with a usb stick (ok, there is no usb type c usb stick yet, that means ugly cable ATM)
Linux4Tegra should make porting full-blown Linux very easy, including OpenGL/GLX

phhusson said:
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
Click to expand...
Click to collapse
boot-tmp.img has the same behavior.
My theory is fastboot is just there for reflashing via otg, not for actual booting and we'll need a chromeos wrapper + the payload burned to flash in order to get anywhere. I need to do some reading up on chromeos and coreboot and probably go thorugh and setup a chromeos enviornment.

ericvh said:
boot-tmp.img has the same behavior.
My theory is fastboot is just there for reflashing via otg, not for actual booting and we'll need a chromeos wrapper + the payload burned to flash in order to get anywhere. I need to do some reading up on chromeos and coreboot and probably go thorugh and setup a chromeos enviornment.
Click to expand...
Click to collapse
What has to be tested first is building from AOSP (i assume aosp tree is available for ryu?)

Not sure. I briefly looked for the kernel source, but wasn't sure I found the right one. There's some stuff in there for Smaug, but I assume the android kernel is probably bit different (although it doesn't seem to be the same as the one on the JTX1 or the Nvidia Shield TV -- so google must be doing something a bit more aggressive than Nvidia is in their products).
phhusson said:
What has to be tested first is building from AOSP (i assume aosp tree is available for ryu?)
Click to expand...
Click to collapse

I'm still in hope to find who implements fastboot...
Can someone give me the result of:
fastboot getvar product
fastboot getvar kernel
This doesn't require oem unlock, and doesn't have any risk, so anyone with working fastboot can do that

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?

Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.

adb didnt recognize my device -but how do I do that just in case I'm able to get it working?

Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.

ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone

tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??

Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.

tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.

Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.

tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted

**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.

If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.

RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."
Hi everybody,
my Aquaris X2 Pro worked fine with rooted BQ 1.7.3 firmware (Android 8.1 based) - Magisk was installed and worked fine and also the xposed framework.
Today the device was normally working as it suddenly just reboots
After that the usual "unlocked bootloader" screen appears but then it only shows a screen with the message "Your device is corrupt. It can’t be trusted and may not work properly."
I can select "continue" - but that only leads back to the "unlocked bootloader" warning screen --> a boot loop :crying:
Does anybody know how I can bring back my device back to work - without losing all my settings and stuff?
And any idea what happened (so that I can prevent it to do so in future)?

Hmm, I'm not 100% sure, but I think I saw that message / boot process once as I tried to root my X2 Pro.
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
(or the other way round? Definitely only done one of them - I was following instructions from a thread here)
and was trying to boot a magisk patched boot-img via
Code:
fastboot boot magisk_patched.img
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Perhaps check your unlock status via
Code:
fastboot getvar all
But note - UNLOCKING again will wipe your data ... and can only be done if the setting in developer options is active (I fear that THAT may have changed on your device)
You could also try booting the second slot
Code:
fastboot getvar current-slot
and then
Code:
fastboot set_active a/b
(if current-slot gives a, boot b and vica versa).
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium

Thanks a lot for your help!
Inbetween I had to go the hard way and reflashed the newest BQ factory image v2.0.2 (based on Android 9) to both parts _a and _b - losing all my data...
after that I patched the boot.img for magisk and reflashed that to my _a boot partition (and still have the original boot.img in _b).
It did cost me a bit of my spare time - but it wasn't as hard as I expected...
I was able to restore a lot of my settings with Titanium backup....
merlinwv said:
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
Click to expand...
Click to collapse
That was exactly what I did - the first time I only did a "flashing unlock", no "unlock-critical" - so now I had to do it to flash the complete factory image, and therefore it wiped all my data again
merlinwv said:
I was following instructions from a thread here)
Click to expand...
Click to collapse
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
merlinwv said:
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Click to expand...
Click to collapse
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
merlinwv said:
Perhaps check your unlock status via
Code:
fastboot getvar all
Code:
fastboot getvar current-slot
Click to expand...
Click to collapse
Very interesting commands which I didn't know - I already wondered how I can get that information
merlinwv said:
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Click to expand...
Click to collapse
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back

Bodenseematze said:
Thanks a lot for your help!
...
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
Click to expand...
Click to collapse
You are most welcome
The erase commands are not the ones doing the factory-reset - if you want to keep your data during a "factory-flash" you need to comment/delete the lines which flash the userdata-partition.
But I do not know if you can flash the factory image without unlocked critical (=boot) flashing. I never tried this myself. Some phones allow flashing of correctly signed boot images even when critical is locked, others prevent ALL flashing then.
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode (turn off, afterwards keep vol+, Vol- and Power pressed - will bring you to a special flash mode that allows flashing even when locked - but via a special serial interface etc. pp.). Google it - this would have helped you regarding "loose of userdata when doing unlock critical". But of course - you need to edit the file because in EDL mode, normally userdata is flashed, too.
Just something to keep in mind for the next time
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Click to expand...
Click to collapse
I think that perhaps an update was installed (explanation for the reboot?!) that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)

merlinwv said:
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode
Click to expand...
Click to collapse
Again: very interesting information! :good:
merlinwv said:
I think that perhaps an update was installed (explanation for the reboot?!)
Click to expand...
Click to collapse
I hope that wasn't the reason, because I explicitly switched off all automatic updates. And I did not do a manual update!
merlinwv said:
that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
Click to expand...
Click to collapse
I tried to switch to the other slot and boot it - but that didn't help either and led to the same problem...
What I didn't tried was to only flash the boot.img - will do this next time

[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro

This is a guide 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.
This message was removed on OOS 12 which was one great thing by OP other than the other broken parts.
So this guide is for OOS 13 not 12 as the message was removed on 12.
But OnePlus brought the message back on OOS 13.
IMPORTANT:
*I am not responsible for bricked devices, damage to your device*
I am here to post my method for anyone who is interested.
The methods have been tested
Prerequisities:
You need a unlocked bootloader
YOU NEED TO HAVE THE STOCK RECOVERY INSTALLED
If you're on a custom ROM that'll be the ROM recovery
This is XDA thread and abl.img is only for the OnePlus 8 Pro, but this method has worked for 8 series devices.
You need to be on OOS 13 and have your bootloader unlocked.
The abl.img doesn't rely on the region so it can be used on any OP8 Pro
The abl.img can be extracted using payload dumper, but download the full zip version.
I have added abl.img from OOS 13 F.10 as this is the newest abl.img that has the message removed and is from @bowow
It is recommended to backup your data before modifying anything on your system
Follow one method and stick to that method
Each method is different where one is for Stock OOS 13 and the other is for OOS 13 based Custom ROMs
Method:
Download the abl.img
Copy and paste the abl.img to platform-tools
If u don't have platform-tools, download the .zip file from download links and extract it
For Stock OOS 13
This method was tested and is from @MeHigh.G
This is for on Stock OOS 13 users
Reboot to bootloader
Type " fastboot devices " to check if your device is connected
Type " fastboot reboot fastboot "
Once booted into Fastbootd Mode, type " fastboot devices " to check if your device is connected
Then type " fastboot flash --slot=all abl abl_filename.img "
Now reboot device and done
For OOS 13 based Custom ROMs
This method was tested by me and it does work
This is for OOS 13 based ROM users
Reboot to recovery
Enter advanced
Enter fastboot
The recovery should now show fastbootd
Type " fastboot devices " to check if your device is connected
Type " fastboot flash --slot=all abl abl_filename.img
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
MSMDownloadTool for OP8Pro Here
Bowow's OnePlus Firmware Updates abl section Here
OrangeFox Recovery for OP8+OP8 Pro ext4 erofs
OFox Install instructions Here
OrangeFox Community Telegram
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

reserved

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

Nice!

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?

gregpilot said:
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?
Click to expand...
Click to collapse
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.

ShadoV90 said:
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.
Click to expand...
Click to collapse
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

Extreme_Ninja2099 said:
That's for the OP9 Pro not 8 Pro...
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
Click to expand...
Click to collapse
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.

ShadoV90 said:
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.
Click to expand...
Click to collapse
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

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

Neil_Armstrong_ said:
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
Click to expand...
Click to collapse
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.

ShadoV90 said:
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.
Click to expand...
Click to collapse
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

ShadoV90 said:
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.
Click to expand...
Click to collapse
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.

MeHigh.G said:
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.
Click to expand...
Click to collapse
Nice feedback, can you share what custom recovery you use on OOS 13 ?

so this work or not?

Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
There's no custom recovery currently for OOS 13... Only for custom ROMs

Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
I use oFox or the one provided with Flamingo OS or Pixel Blaster

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

STALKER18 said:
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 .?
Click to expand...
Click to collapse
I've already extracted it for the 8 pro... Up to u
For step 4 it's fastboot flash abl abl.img

i'm unable to unlock bootloader says command not supported in default implementation.
IN2021 One plus 8 pro.

Question I am lost...please point me in the right direction

I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programmers, ie too much knowledge is assumed when giving steps or making references to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!

coolvan170 said:
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programs, ie too much knowledge is assumed when giving steps or making reverences to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
Click to expand...
Click to collapse
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!

TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
That is one of my problems – I cannot find the image file for my device. All the links I followed lead me to source code which I must compile myself. The TWRP installer 3.6.2_11-0-lemonadep zip RAMdisk-twrp.cpio, magisk boot file which is only 300 K bites and a meta-info folder. But it is a zip file not an image file.

Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)

TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
cant get fastboot to work, but ADB sideload does.

coolvan170 said:
cant get fastboot to work, but ADB sideload does.
Click to expand...
Click to collapse
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.

TheGhost1951 said:
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
Click to expand...
Click to collapse
Found the QPST tool so I will try with that.

Shooter7889 said:
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
Click to expand...
Click to collapse
I found the QPST tool I will try working with that.

coolvan170 said:
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
Click to expand...
Click to collapse
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.

Skynet30 said:
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Click to expand...
Click to collapse
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...

The problem with the new A/B Slot solution is (2) things need to match in order to initiate a correct OS boot:
A Stock or (Working) Custom recovery.img
A Stock boot.img
This need to exist in both slots (A & B)
When in a Bootloop, your device is responding to a mismatch of at least one of these, causing corruption and a looping response.
I've made the same mistake and accidentally soft-bricked (what you're currently experiencing) on both my Oneplus 8 Pro and Oneplus 10 Pro
e.g.
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Try following my guide here to get things on track via Fastboot Mode:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713

TheGhost1951 said:
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
Click to expand...
Click to collapse
Also, be sure you have the correct Qualcomm drivers typically packaged with an MSMTool+Stock ROM

Fwiw. Android auto has worked fine on a11, a12, and a13. Wired and wireless. Multiple head units. Wired is picky with cable however. Bluetooth and wifi both need to be on for wireless.