[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] optimumpro:
I normally don't respond to angry rants, but when authors do multiple edits (as you've admitted) and misrepresent facts, I have to. So, for starters, I am posting our entire e-mail communication so that people can see for themselves:

Your first e-mail Yesterday:

Hi, i just booted into recovery (i guess v38) to flash the v40 and it

looks like my phone got bricked by booting into that recovery.

i just get the pixelated image at boot and it wont go any further.

reboot doesnt help. it will boot until pixelated image is shown and

then is stuck there. I'm on locked bootloader. Please help. Cheers Mate

Note, before getting my response, you've already posted and edited your 'stay away' rant.

Me:

Why such an angry post on XDA? "Stay away", "developer treats his

users as beta testers"? You should have read a warning in the thread about V38. I don't have 8

Pro, and it is the only device that has a graphical glitch (for a few

seconds) on boot. So, in V38, I attempted to fix the glitch, which

turned out to break access to recovery.

But under no condition you wouldn't be able to boot in System (normally). So, if you can't boot in System, then you either improperly shut down the phone or you install

something on top of V38 that prevents booting.

If you are able to boot, back up everything you need and unlock

bootloader. Install recovery from XDA and install the latest version.

Then lock bootloader the usual way.

If you had OEM unlock allowed disabled, and you can't boot, then your

only option is to use MSM. I usually tell people with locked bootloader

to enable 'Oem allowed' option before upgrading. Enabling this option

does not unlock bootloader, but rather gives you an opportunity to

unlock in case something goes wrong. Regards

Me:

Also, there is an easier method if you can boot into System. If you do,

open Magisk manager, tap update/install and then pick install into

inactive slot after OTA. Hit 'let's go' and follow prompts. You will

reboot into the other slot with prior Jaguar version and good recovery.

From there, you can install V40.

You:

Haha, at the time of your email i have edited my post since like 4 hours. Not that i dont feel treated like a beta user if you even say u dont own the device yourself to do tests 😉

Sadly that (i cant boot anymore besides fastboot) is exactly what happened.

U also never told me to leave oem allowed enabled. just look up our conversation history (same mail adress).

Msm Tool doesnt work, as my phone does not get recognized in any mode or way. Neither on windows with msm, nor on linux with lsusb.

Im a bit disappointed from your behaviour tbh, ofc i know its my fault for using custom roms in the end. But i use custom roms since 2014. U produced my first brick, so cheers mate. Im just happy that technically it wasnt my fault, and will stick to the bigger projects where every device has its own maintainers which do testing on their site to prevent issues like this in the future.

I still wish you success for your project, just ask you to stick to good developing practices.

Me:

You are absolutely wrong on MSM tool. With proper installation and

drivers, it will even detect the phone that has a black screen, i.e, it

can't be put into fastboot. Yours can.

Just read the appropriate XDA MSM tool section. It tells you what to

do, if the phone can't be detected and how to put the phone into EDL

(emergency download) mode. Otherwise, it won't be detected.

As far as best development practices: you are not the only one with

locked bootloader on 8 Pro. Other users had the same problem, but were

able to successfully boot into the other slot with good recovery (via

Magisk). Also, take a look at this link: that's Google rendering

Pixels unusable with November and January updates:

https://www.bleepingcomputer.com/ne...es-unusable-after-january-2024-system-update/

To conclude:

You've used my rom for more than a year, and at the first glitch you started screaming 'Murder' before even receiving my response.

Although, the glitch (not allowing you to access Recovery) existed in V38 (fixed since then), under no condition that glitch would have prevented you from booting into System. That is unless you screwed your system somehow, probably via a Magisk module. Did you know that Magisk modules could cause bootloop, as well as other problems? Now you know.

I've had a few users on locked bootloader, who faced the same problem, yet they were able to use my method and change slots via Magisk to boot into prior Jaguar version and then install the latest release without losing data.

As far as losing data in the past, because 'something was set to automatically delete something by default", my rom doesn't have anything like that. If you did, then it was something that you've installed, which could also have been the reason for your inability to boot normally.

Good luck with Lineage. Best regards.

P.S. A friendly advice - When on another rom and asking for help, try not to scream "STAY AWAY" in the same post.