Database Users

9.0.5 Bricked itself?

Hey guys, I have the T-Mobile 6T, unlocked and rooted, worked perfect until today.
Today it took the 9.0.5 OTA, it downloaded, installed, rebooted and left me with
"<!> BUILD VERSION and HW VERSION IS NOT MATCH"
Any chance someone can help?
I can't get it into recovery or anything.

The MSM download tool will help you.
https://forum.xda-developers.com/on...t-mobile-oneplus-6t-msmdownloadtool-t3868916/

I had hoped that it would. Unfortunately, I can't get it to work..
it seems that the phone just keeps rebooting before the tool can actually do anything.
The most I get is "Start download firehose binary" and the the phone disconnects.
Next is "Sahara Communication Failed."

after a few dozen more tries, I got a bit more. Now it says "Images do not match the phone!"

Try restarting into qcom mode as well as plugging into diff USB ports. Mine was doing that as well and eventually was able to get it to work.

How do I get into qcom mode?

intrusdave said:
How do I get into qcom mode?
Click to expand...
Click to collapse
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.

Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.

intrusdave said:
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
Click to expand...
Click to collapse
Are you using the T-mobile tool? https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916

I thought I was, but I will re-download and see.

That was it, thank you! I don't know where the hell I got the wrong copy from!
You really bailed me out, thank you very much.

intrusdave said:
That was it, thank you! I don't know where the hell I got the wrong copy from!
You really bailed me out, thank you very much.
Click to expand...
Click to collapse
No problem. There's two tools in the guides section and the threads have similar names so it's easy to get mixed up.
In the future if you're going to international 9.0.5 or 9.0.6 make sure to use the full rom and not just OTA.

I have the Same problem
intrusdave said:
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
Click to expand...
Click to collapse
Hi, i have the same problem. what do you do to get it work?

Hi, I lost all my photos by doing this . is there any way i can get all my data back ?Phone is up and running but lost my all data

[email protected] said:
Hi, I lost all my photos by doing this . is there any way i can get all my data back ?Phone is up and running but lost my all data
Click to expand...
Click to collapse
Oh boy, look what I found right in the thread about the MSM tool! Please see attached screenshot.

I have this issue on the international variant of the phone (Yes mine truly is the international model, it has dual sim, although its refurbished so the refurbishers borked something)

mang0 said:
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Click to expand...
Click to collapse
I used the international version on mine (T-Mobile 6T) since was in software and hardware error. You don't have to come back to TMobile software mandatory.

mang0 said:
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Click to expand...
Click to collapse
I've tried the different tools to no avail. also holding power, vol up and down will only go into fastboot mode. I believe just holding vol up and down is the qcom mode and inserting the usb c cable after about 10 seconds of holding those two buttons. otherwise the device will just keep rebooting into fastboot

[SOLVED!] Hard Bricked 6T Help Pls

Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.

You must post in Q/A not here
Tapatalké depuis mon OnePlus 6T Havoc OS avec FP !

What were u exactly trying to do while this happened ?

Extreme_Ninja2099 said:
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
Click to expand...
Click to collapse
You can restore you device using fastboot rom. Search for oos 6t fastboot rom.. There are guides for installation.
P.S. It will give a whole bunch of error in the cmd during installation but don't interrupt the process as your device will be restored in the end

Use Mnm tool to fix your phone. It can fix hard brick devices and guidance is there how to use .
PS: this is not right place post next time post on Q/A section.

Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all

Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.

parker.stephens said:
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
Click to expand...
Click to collapse
Hold down every button till it shuts off, then force reboot to bootloader, then select power off to make sure it's off. Then do as I instructed above to fix it. Sometimes u can just run a fastboot rom to fix it, or boot twrp and flash a rom. I do this multiple times a day sometimes.

fullofhell said:
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Click to expand...
Click to collapse
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone

Extreme_Ninja2099 said:
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Click to expand...
Click to collapse
Everybody, it's called the MSMDownload Tool. It cannot be used in Fastboot Mode or Qualcomm CrashDump Mode, it can only be used in EDL Mode (Emergency Download Mode).

I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help

CaptionNixx said:
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
Click to expand...
Click to collapse
Power off use msm. Done.

fullofhell said:
Power off use msm. Done.
Click to expand...
Click to collapse
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area

CaptionNixx said:
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
Click to expand...
Click to collapse
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?

Extreme_Ninja2099 said:
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Click to expand...
Click to collapse
Yes i did that and driver is fully installed Qualcomm HS-USB QDloader 9008 and there is No yallow sigh in driver

Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected

Extreme_Ninja2099 said:
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Click to expand...
Click to collapse
Thanks brother its done

Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do

Voldemort13 said:
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Click to expand...
Click to collapse
did yoy got any solution

I Can't exit fastboot mode

In the beginning I wanted to upgrade my device to 9.0 ( Korean version ) then when i Update my phone Through LGUP show error message (Approximately 75%)
Then I turn off the phone Then when I want to get in Downloading mode Is directed to fastboot
so I stuck in fastboot
please HELP

Try to force reboot via holding power + vol down for 8 seconds.

themostunique said:
Try to force reboot via holding power + vol down for 8 seconds.
Click to expand...
Click to collapse
Doesn’t work :crying:

Try draining the phone's battery via otg, then hold vol up and plug in usb to computer to download mode.

@a_al_khaled1 you need to provide a bit more info and answer to those questions:
1. Were you bootloader unlocked?
2. What option and partitions you have checked to flash via LGUP?

vlad48 said:
@a_al_khaled1 you need to provide a bit more info and answer to those questions:
1. Were you bootloader unlocked?
2. What option and partitions you have checked to flash via LGUP?
Click to expand...
Click to collapse
1- No
2- update
This is what appears when I try to boot or download mode https://drive.google.com/file/d/1xvEqf1FszSxvMXhJMq-QFM2yIIXwAre7/view?usp=drivesdk

Now we are getting there...
Can you remember OS Oreo version you were using and if your device has AT&T branding or it was a Google - Fi one?

vlad48 said:
@a_al_khaled1 you need to provide a bit more info and answer to those questions:
1. Were you bootloader unlocked?
2. What option and partitions you have checked to flash via LGUP?
Click to expand...
Click to collapse
vlad48 said:
Now we are getting there...
Can you remember OS Oreo version you were using and if your device has AT&T branding or it was a Google - Fi one?
Click to expand...
Click to collapse
V350ULM10i
Amazon version

Now everything is clear.
Try holding and not releasing volume - and power while the phone boots and reboots into fastboot 6 times in a row then release only Vol- while still holding power - phone will change active boot slot and will boot into slot _b (if it was bootable before of course).
If this does not happen then your only way to restore it is via JTAG.
Contact this guy.

vlad48 said:
Now everything is clear.
Try holding and not releasing volume - and power while the phone boots and reboots into fastboot 6 times in a row then release only Vol- while still holding power - phone will change active boot slot and will boot into slot _b (if it was bootable before of course).
If this does not happen then your only way to restore it is via JTAG.
Contact this guy.
Click to expand...
Click to collapse
That what happen when I try to get to download mode https://drive.google.com/file/d/14mKlTCVSYj4bA0LHZ84KfJ4EaAm9608N/view?usp=drivesdk

Yes, I know - you have 75% Korean pie with leftovers from Amazon Oreo (your abl misc and ftm partitions are still from Oreo while the rest is from Pie).
You can enter into 9008 mode for JTAG flashing so just contact the guy and ask him to flash to you back amazon LAF partition, afterwards you will have properly working download mode and you can restore the whole amazon kdz.

@vlad48 I am in the same situation, however mine is the AT&T variety, I tried swapping to boot_b a couple times and no luck. Is my only option to do the 9008 mode for JTAG flashing?
E: I have backups of Boot_a/b, abl_a/b, and xdl_a/b if that is worth anything. However my phone isn't detected by LGUP anymore. I was on oreo 8.0.0 with the july 2018 security update.

Yes - the only way apart from sending it back to AT&T is to flash back your Oreo partitions via JTAG - in your case easiest way will be to re-lash US Open KDZ.

a_al_khaled1 said:
In the beginning I wanted to upgrade my device to 9.0 ( Korean version ) then when i Update my phone Through LGUP show error message (Approximately 75%)
Then I turn off the phone Then when I want to get in Downloading mode Is directed to fastboot
so I stuck in fastboot
please HELP
Click to expand...
Click to collapse
I can't get into fastboot.

Shawnashley said:
I can't get into fastboot.
Click to expand...
Click to collapse
What variant do you have?
If you're running AT&T firmware, you don't have fastboot flash commands.
You have to convert to another firmware via Dev Patched LGUP.

ChazzMatt said:
What variant do you have?
If you're running AT&T firmware, you don't have fastboot flash commands.
You have to convert to another firmware via Dev Patched LGUP.
Click to expand...
Click to collapse
Is there a specific firmware you would recommend? Thanks in advance

Shawnashley said:
Is there a specific firmware you would recommend? Thanks in advance
Click to expand...
Click to collapse
The AT&T V35 I bought from @bacon612 was flashed to Google Fi firmware.

This or US unlocked 'i' are good candidates.
https://lg-firmwares.com/downloads-file/19020/V350ULM10i_00_NAO_US_OP_0221.kdz
Takes ages to download...
The above is US Unlocked firmware for the v35 Feb Security patch.
Sent from my GM1915 using Tapatalk

ChazzMatt said:
The AT&T V35 I bought from @bacon612 was flashed to Google Fi firmware.
Click to expand...
Click to collapse
bacon612 said:
This or US unlocked 'i' are good candidates.
https://lg-firmwares.com/downloads-file/19020/V350ULM10i_00_NAO_US_OP_0221.kdz
Takes ages to download...
The above is US Unlocked firmware for the v35 Feb Security patch.
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
I'm going to look into that one. Thanks for the recommendation. Also, I was able to use LGUP to flash the Korean KDZ. It seemed to work fine, and does now. It flashed perfect, my data was intact until I had to restart my phone a while later and then it was all gone. Looked factory out of the box. However it is smooth as a baby's bottom now.

Shawnashley said:
I'm going to look into that one. Thanks for the recommendation. Also, I was able to use LGUP to flash the Korean KDZ. It seemed to work fine, and does now. It flashed perfect, my data was intact until I had to restart my phone a while later and then it was all gone. Looked factory out of the box. However it is smooth as a baby's bottom now.
Click to expand...
Click to collapse
Which version of LGUP you used? and dll file PLz

Phone stuck on EDL mode and Error firehosecheckrsp failed errno 258

hi, everyone , i m tring to revive my hard bricked oneplus 8 pro but without any luck i m getting "firehosecheckrsp failed errno 258" error , i tried every possible solution a did find (Drivers, Cable, USB 2 , other pc) , i m convinsed tha i shoud start search for a motherboard replacements (even that i coudnt find on the internet)
so please if anyone could help me (Phone stuck on EDL mode - recognised by pc but buttons combination doesn't work )

If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.

dladz said:
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
Click to expand...
Click to collapse
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error

ahmadOnePlus said:
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
Click to expand...
Click to collapse
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed

jamescable said:
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
Click to expand...
Click to collapse
+1 to this

You need these so the phone is detected correctly in windows. Here is a link.
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com

I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258

gcf81 said:
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
Click to expand...
Click to collapse
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)

Nick-Henkey said:
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Click to expand...
Click to collapse
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.

gcf81 said:
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
Click to expand...
Click to collapse
Looking around, the North America version should be running international firmware (HD1905):
OnePlus 7T hardware variants
I was curious about the different hardware variants of the 7T and decided to ask support once EU launch went over and they kindly answered. HD1900: China HD1901: India HD1903: Europe HD1905: North America HD1907: T-Mobile USA
forum.xda-developers.com
I presume that you're using this MSM tool - https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
Did you try all of the steps suggested by OP, yet?
Install drivers
Change to factory cable
Different USB port
Different Windows computer?
The only thread I could find where this problem was solved was on the OnePlus forum. The user completely removed and reinstalled the Qualcomm drivers (a different PC should handle that) - https://forums.oneplus.com/threads/solved-closed-trying-to-unbrick-op5t.956810/

I bricked my Oneplus 6t from tmobile and would like to unbrick it if possible.

So I finally rooted my Oneplus 6t from t mobile. I bought the phone from swappa and it worked great. I installed a random rom and it bricked my phone.
I assume it is a soft brick since i can access adb mode but it requires me to power off the phone
and hold the volume keys along with the power button. Otherwise the phone will just boot up and
will be sutck in a continous boot loop. I then tried to fic this issue by using an msm tool found in
the xda fourms. I then entered recovery mode and perfomed a "wipe data/factory reset. I think it hurt more than it helped. Any suggestions on how to unbrick my phone?
I tried using alll three msm tools in this fourm.
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Also the update would fail if i were to use the msm tool (MSMDownloadTool 9.0v1 and MSMDownloadTool 9.0.13)
I have tried reinstalling the qualcom drivers but no luck.
I tried deleting the drivers and allowing windows to detect the phone nad download its own usb drivers
but it did not help.
i apologize if i post this in the wrong section. I am new here.
all links and info i followed to attemp to unbrick my phone can be found in this fourm
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com

falzer2007 said:
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Click to expand...
Click to collapse
that's not very descriptive, produce the error and share results here

dmtec said:
that's not very descriptive, produce the error and share results here
Click to expand...
Click to collapse
Okay so I open the msm tool. Then I have my oneplus 6t (t mobile) turned off. I hold both volume buttons and keep holding them while I connect the USB cable to the phone. Its basically in edl mode at this point. Then I press the start option on the msm tool. The bar fills up with green and completes itself. However a number appears that saids "4s" inside of the square. I assume that means 4 seconds left or completed in 4 seconds. My phone is still in edl mode at this time and will not boot up in any menu (normal.menu, boot menu/recovery mode). Unlesss I boot it manually.
And yes I tried a scenario where I held down both volume buttons, connected USB cord, and then let go. I also tried the scenario where I held both volume buttons, connected usb cord and kept holding the volume buttons until the process completed itself but I would get the same result. "4s"

dmtec said:
that's not very descriptive, produce the error and share results here
Click to expand...
Click to collapse

falzer2007 said:
So I finally rooted my Oneplus 6t from t mobile. I bought the phone from swappa and it worked great. I installed a random rom and it bricked my phone.
I assume it is a soft brick since i can access adb mode but it requires me to power off the phone
and hold the volume keys along with the power button. Otherwise the phone will just boot up and
will be sutck in a continous boot loop. I then tried to fic this issue by using an msm tool found in
the xda fourms. I then entered recovery mode and perfomed a "wipe data/factory reset. I think it hurt more than it helped. Any suggestions on how to unbrick my phone?
I tried using alll three msm tools in this fourm.
when i use the msm tool (MSMDownloadTool 9.0v2) the update just stops after 4 secounds.
Also the update would fail if i were to use the msm tool (MSMDownloadTool 9.0v1 and MSMDownloadTool 9.0.13)
I have tried reinstalling the qualcom drivers but no luck.
I tried deleting the drivers and allowing windows to detect the phone nad download its own usb drivers
but it did not help.
i apologize if i post this in the wrong section. I am new here.
all links and info i followed to attemp to unbrick my phone can be found in this fourm
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, Falzer. had all but given up and was prepared to head to T-Mobile to buy the 1+ 9 Pro (I almost wish I did not fix my phone... *BUT* I DID!
My issue occurred trying to flash a Magisk patched boot.img to my newly unlocked bootloader phone. I was following an article that alleged one could root the phone without TWRP. I will say this TWRP is your friend; don't dis "him". By the way, unlocking my phone wiped my data so always important to read the whole article first as it was mentioned in the NEXT step.
[Should be including the actual error here - it is found throughout these forums but I cannot recall the exact display. Basically, if you have an unlocked bootloader and then get to the CrashDump screen, follow from here:]
Retrieve the file, boot11.1.1.1.img and download from this thread/link:
OOS stable boot image and patched magisk boot image both for 11.1.1.1.
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out. Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"...
forum.xda-developers.com
Do *NOT* mess with the other file to the right.
Hold all 3 buttons (2 volume buttons + power) and once/if you see Fastboot Mode, release the buttons.
Have ADB installed (you should be able to find plenty of directions for doing this).
From either PowerShell (or *maybe* CMD Prompt started as Administrator as I had been using this "successfully" for most functions):
fastboot devices
fastboot flash boot boot11.1.1.1.img
fastboot reboot
I could not believe my phone ACTUALLY booted (even with the McLaren animation intact; I'm sure one of the gurus here knows why) after all the failed attempts fooling around with MSM Download Tool [4.0] which almost EVERYONE swears by fixes/restores any brick. I understand ON ONE is forcing anyone to use any specific resolution; I am just trying to provide another last ditch effort.
EDIT/Caveat: I did not even check to see how old that thread above is, I believe late September and I had actually taken updates [via TMobile??] until the last one with a week to 10 days *but* that was probably wiped with the boot unlock so I do not know which "update" I got but figured I didn't have much to lose as I already had a "bad" version of a boot.img flashed anyway. Anyone with any technical explanations, feel free to comment. Thanks!