Develop Bugs

[Q] Lenovo S820 bootloader problem

Hello everyone.
I am trying to get into the bootloader, so i will be able to use fastboot commands.
Prior to post here i made a thread in the [HELP THREAD] but unfortunately since the person that tried to help me did not had this device, he couldn't help me, thus i'm posting here
So, first i tried to get into the bootloader by pressing the physical keys:
if power button and both volume keys are pressed i get into Android System Recovery(3e).
if power button and volume down key are pressed i get into meta mode.
if power button and volume up key are pressed i get into factory mode, which is entirly in chinese.
in all 3 occations, fastboot devices command did not reply anything....
Now the device is recognized by adb (i made the udev rule for it), all commands are working as should except one.
all except one: "adb reboot-bootloader" or "adb reboot bootloader" or "adb reboot fastboot" do not do anything. they just reboot the device into android os.
even "adb reboot recovery" works correctly...
Lenovo S820 is a new device. it was released in 2013, is it possible that it doesn't have proper fastboot mode??? or is it possible that it needs to be unblocked in some way???
What should i do?
P.S.
Android system recovery <3e> options are:
reboot system now
apply update from ADB
apply update from sdcard
apply update from sdcard2
apply update from cache
wipe data/factory reset
wipe cache partition
in Meta mode just get this: Have been in meta mode, long press the power button and the normal boot.
factory mode (which is completely in chinese) has 8 options.
-EDIT-
I am 100% sure that i found the translations of the 8 options of the factory mode:
Manual Test
Auto Test
Item Test
Test Report
Debug Test
Clear eMMC
Version
Reboot

Any help at all???
What did i do wrong? why no one is replying?
Does the need for the same device is so great???
Isn't it a bit of generic question at all???
I don't need a -like- guide how to do it, i just need some infos, tips and guidance.
I am new to android os, i don't even know what to search/look for, so i can start solving this issue...
HELP!
I need somebody!
HEELP!!
not just anybody
HEEELP!!!
you know I need somebody
HEEEELP!!!!

I am looking for a damaged or broken physically or software lenovo s820
please get back to me on sohelv.00 @ gmail DOT com

why there is no help???
50437s said:
I am looking for a damaged or broken physically or software lenovo s820
please get back to me on sohelv.00 @ gmail DOT com
Click to expand...
Click to collapse
My s820 is not broken. it's working like a charm.
my problem is that i can't get into the bootloader.
Is there a chance that the bootloader is blocked?
I also, honestly, do not understand why no-one is replying, i am not asking for a how-to guide, just for some tips/infos so i can start investigating how to get into the bootloader....

i know hoow to unlock bootloader in lenovo s820
KottttoK said:
Hello everyone.
I am trying to get into the bootloader, so i will be able to use fastboot commands.
Prior to post here i made a thread in the [HELP THREAD] but unfortunately since the person that tried to help me did not had this device, he couldn't help me, thus i'm posting here
So, first i tried to get into the bootloader by pressing the physical keys:
if power button and both volume keys are pressed i get into Android System Recovery(3e).
if power button and volume down key are pressed i get into meta mode.
if power button and volume up key are pressed i get into factory mode, which is entirly in chinese.
in all 3 occations, fastboot devices command did not reply anything....
Now the device is recognized by adb (i made the udev rule for it), all commands are working as should except one.
all except one: "adb reboot-bootloader" or "adb reboot bootloader" or "adb reboot fastboot" do not do anything. they just reboot the device into android os.
even "adb reboot recovery" works correctly...
Lenovo S820 is a new device. it was released in 2013, is it possible that it doesn't have proper fastboot mode??? or is it possible that it needs to be unblocked in some way???
What should i do?
P.S.
Android system recovery <3e> options are:
reboot system now
apply update from ADB
apply update from sdcard
apply update from sdcard2
apply update from cache
wipe data/factory reset
wipe cache partition
in Meta mode just get this: Have been in meta mode, long press the power button and the normal boot.
factory mode (which is completely in chinese) has 8 options.
-EDIT-
I am 100% sure that i found the translations of the 8 options of the factory mode:
Manual Test
Auto Test
Item Test
Test Report
Debug Test
Clear eMMC
Version
Reboot
Click to expand...
Click to collapse
just install a miui v9 in your s820 then hold power button then click reboot then click bootlloader
watch how to install custom rom in any android
search how to install custom rom on android
miui v9 custom rom for s820 it has gapps so dont worry you dont have to download gapps
just search s820 custom rom then choose needroms then choose the one with 24 stars
so yeah just wait when you click bootloader until it says Fastboot Mode..... its in the lower left side
Remember:
follow the steps in the video

i bricked my ZE551ML bad need help PLZ

i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:

FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.

now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse

Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app

i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse

it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse

Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse

Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.

Tried flashing CM13, now can't enter normal boot

So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks

Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.

Phone might be bricked. Need help to find a solution!

Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.

Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk

waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)

i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.

Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?

Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition

waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!

Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.

saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?

Question 9 Pro crashed to lockscreen on loop, forced reboot and will no longer boot

hey, i have a completely stock 9 pro, i was texting someone and sending them pictures from the night but while i was doing that the phone suddenly crashed to the lock screen over and over again. so i just hard rebooted it since it was completely unresponsive and just crashing on the lock screen and now it will not even boot up it just shows the oneplus log and a field to put in a password and after entering the password its looking to format the phone and probably factory reset the whole device i was hoping that there would be some way to use adb to get my photos back since i didnt get a chance to save or send them and it would be a real bummer if they were gone. not enough to pay 1000s of dollar but enough that i would spend time playing with adb to recover them. im very familiar with commandline and adb but i dont know of a way to get in without unlocking the bootloader first.... any help would be very much appreciated.

Can you manage to boot into fastboot and try some things there?
Setup platform tools (let me know if you do not have it setup) and then boot into fastboot. Connect your device to your computer and try out the following commands :
fastboot getvar current-slot
If this outputs something like :
current-slot: b
Then run the following command :
fastboot --set-active=a
otherwise, run the following command :
fastboot --set-active=b
After this is done, reboot your device by running :
fastboot reboot

Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.

I never set bios or lockscreen passwords, or encrypt data drives. You are the one most likely to be locked out, sometimes through no fault of your own. People will steal these devices regardless if they're locked or not; physical security is the only type of security that works.

wjcrabtree said:
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
Click to expand...
Click to collapse
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.

ekin_strops said:
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
Click to expand...
Click to collapse
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.

wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/

wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
You can't do a factory reset from there?
It's rare but a SEU can corrupt any part of the flash memory. It causes no physical damage but the altered memory cells will need reset.

I think the best way to recover is MSM tool for youre specific model phone.
My phone power off by it self after watching a video on a received link with whatsapp.
Nothing workt beside MSM. I factory reset, downgrade rom. flash-reflash rom's.
MSM wipe all in youre phone.

ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Thank you so much!!
Sorry for the slow reply, but I haven't had time to deal with the problem because of work. I'll be looking into this today.

ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Ho Lee Sheet! I finally got around to dedicating serious time to working on this.
I had to jack-around with it quite a bit to get Windows 11 to load the proper drivers so that the phone would be recognized, but: BOOM! BACK IN BUSINESS!
Thank you so much for the guidance.