i seem to have hardbricked my mytouch 4g. no signs of life no bootloader recovery charging lite nothing. it is shown as a qualicom hs downloader device on my pc. does annybody have the files to flash through qpst by chance to restore the partition table. because if i can atleast get a working partition table i can get somewhere and possibly recover the device. a qpst factory device image would be even better though if anyone has eather of these please post them in the thread
Anybody
Somebody
I gave it a shot, but a few issues led me to give up the attempt:
1) The QPST instructions I found required using an mmi code to put it into diagnostic mode in order for QPST to operate. Those have never worked on my phone (either my old mytouch or new one, on both stock and custom ROMs). It might have something to do with being no-contract/prepaid.
2) I searched around and couldn't find a single successful story of someone using QPST on any HTC gsm phones with a qualcomm msm8255. Lots of noble attempts, but no results.
3) A QPST backup would contain the phone's IMEI, which is pretty sketchy and not something I would want to share. I was going to look into making a backup for myself, and if I could find a way to zero out the IMEI I would consider sharing it for unbricking purposes, but couldn't even get past step 1 anyway, so that was a bust.
4) FYI, for $12 I picked up a broken mytouch on ebay and swapped the motherboard when I destroyed mine a couple months ago. Far lower frustration level. That's my contingency plan, anyway.
These are the Folders & Files I used in the DE-HARD-BRICKING of the Verizon variant of the LG G4. The word out on the streets is that plenty of infected Qualcomm tools have been floating around, so I decided to share with the XDA community, as far as I know, the most recent and infection free versions that really work. I can feel for the ethical hackers out here that need to get things done with the peice of sound mind that there is nothing involved that may risk their machines security or waste time with tweaked versions that wont work for some reason or other. About the Firehose, Raw, & Patch... These are THEE ones for vs986 & ls991. I DO NOT KNOW if they will work with any other variants, although, I SUSPECT that they may work with all G4's. On the other hand . . . they very well may not. AGAIN, I DO NOT KNOW. Only vs986 & ls991 are confirmed. I am looking for HardBricked G4 owners to use these with non-confirmed variants to establish a consensus of statistics to universally root the G5 using Qualcomm Utilities. I know, Iknow. eMMc & UFS are different, Bro. BLAH! Blah! BlAh! I'm only asking for volunteers whom have a G4 in the 9008 coma and have nothing to loose. If somebody knows something that I don't, that can convince me I'm wasting my time, I am open to "practical reason". or if somebody knows that these DO WORK for all G4 models on all Android LP & MM, then this I'd also like to know also. Misdirection shan't be tolerated. MY un-bricking method is posted here
DriverPack>https://drive.google.com/file/d/0B41ACD_ESYnHQU1qSnVlVXhORjA/view?usp=sharing
G4BootRepair>https://drive.google.com/file/d/0B41ACD_ESYnHQy1sY0paaWYwQUU/view?usp=sharing
method>https://forum.xda-developers.com/g4/help/lg-g4-vs986-super-hard-brick-unbrick-fw-t3666784
QPST>https://drive.google.com/file/d/0B41ACD_ESYnHemxoOEdGVFVOVUE/view?usp=sharing
QFIL>https://drive.google.com/file/d/0B41ACD_ESYnHRG4ta2ZZMFVtcW8/view?usp=sharing
Driver Enforcement>https://drive.google.com/file/d/0B41ACD_ESYnHWWY4Rm1GelZZZ2c/view?usp=sharing
I'll be putting together a more detailed tut. if I feelm it's needed. but for now I'm assuming most of us are pretty far along. A big thank You to TheMadScientist for being the first volunteer of the G5. MODs , if this needs to be moved feel free.
CAN'T FORGET TO MENTION THIS GREAT WORK OF ART https://forum.xda-developers.com/showthread.php?t=2600575 & * USE BOARD_DIAG-2.99 FOR TOTS
There are things which are important when it comes to using this method
first of all there are no infected files out there. at least none I'm aware of and you can believe me I know a little about this topic.
the next thing is that it highly depends on what files you are using because they are device specific! I don't say they would not work though but they will make your phone a different one.
there is NO universal one package available to unbrick all device models with the same files! This is just imposssible.
There is one method available which is able to convert any G4 and for this just check my PoC thread in the G4 forum.
It's not possible to make all this without device specific files because you flash parts of the bootloader stack and those are always device specific.
I haven't looked into your files here yet but when they work for both device models then your files are converting ones which means either it will convert to ls991 or it will convert to vs986 depending on what files you have. I strongly believe you have those for the ls991.
I can say that I have all of them and I investigated then in deep.
There are some rare for ex for the H815 which work without converting and without blowing the fuses. But there some named as h815 but containing converting to ls991.
Keep in mind that converting a device this way may be irreversible depending on the files used.
If you blow efuses you're lost and its not possible to have your previous device model back again. Well ok when you buy a new mainboard then.. But that's the only way.
I just want to warn users especially bc I'm working on a safe way for converting a device forward and backwards.
When you have a vs986 and used that method: you should bring your device in fastboot mode. Check the serial. Does it starts with LGLS991....? Then you converted the device.
sfX
Sent from my LG-H815 using XDA Labs
Well put.I agree with every thing you mention. Although the end result I'm achieving is download mode to flash the correct FW that matches the board. This is why I only use the files related to laf and take notice that I am not including the boot.IMG because that would essentially be a game changer like you said. I personally am not interested in converting carrier variants.
I'd like to add, I have personally used these firehouse ,raw, & patch on both sprint and Verizon g4's to handle 9008 bricks. I just don't have in my possession an AT&t or TMO to try these files with. If anybody has an AT&T or TMO G4 that is 9008 bricked and would like to attempt something they have not tried yet. Do Not include any boot.IMG in the created recovery folder that is to be flashed. We are achieving download mode. That's it. To be able to use LGUP TO FLASH kdz or tot.
ls991 "Download Mode" recovery image
I have taken this https://drive.google.com/file/d/0B41ACD_ESYnHa3pIQlFLYUttdzg/view?usp=sharing and simply relaced sprint stuff with verizon stuff. maybe I should rename my thread from "unbrick " to "recover download mode".
If when
If when I flash the ls991 recovery folder to vs986 in QFIL, fastboot is acheived and the command prompt window report back as my verizon with the correct serial number. maybe this info can be useful to you, I hope. Because I change carriers more than I change devices and the crossover is a major PITA.
gratefuldeaddougie said:
If when I flash the ls991 recovery folder to vs986 in QFIL, fastboot is acheived and the command prompt window report back as my verizon with the correct serial number. maybe this info can be useful to you, I hope. Because I change carriers more than I change devices and the crossover is a major PITA.
Click to expand...
Click to collapse
What do you see in fastboot? Can you make a pic for me?
Sent from my LG-H815 using XDA Labs
I can not today. As I have sold the vs986 but am receiving 2 more bricked vs986's this week. I will post a pick. Pic of phone or PC cmd window? Which is of interest. Just curious although I'll post both.
gratefuldeaddougie said:
I can not today. As I have sold the vs986 but am receiving 2 more bricked vs986's this week. I will post a pick. Pic of phone or PC cmd window? Which is of interest. Just curious although I'll post both.
Click to expand...
Click to collapse
no just a photo of the fastboot screen is enough. thx
btw: the download you link in your OP does not contain any image files - only the XMLs and the firehose?! or do i miss something here?
thx
sfX
I wanna jump on the hard brick train
Just everybody remember improper use or jumping the gun can lead past hard brick to totally unrecoverable device seen it happen a many times.
Ready Set Go
Before I begin, In reference to infected files, there are many discussions such as this https://forum.xda-developers.com/g4/help/mbn-msm8992-qpst-2-7-430-unbrick-g4-t3292097 Today I received a vs986 that as of first connection does not appear in device manager. I'm gonna be reviving it regardless of what it may needs. It's 98% cosmetically and I got it for $29 and I love doing this. the process will be documented and posted. And most of all I'd like to thank TheMadScientist & steadfasterX for their inspiration or I wouldn't be doing this. Let's cross are fingers and hope for a 9008 brick. I'll force QDloader mode with test points and screenshot the device manager and go from there. If a hardware issue is present then I will deal with that deck of cards first. Until then. . . . . . . . .. .
@ steadfasterX
Maybe I assume too much. I imagine that those who have made it this far are aware of the fact that they should have a copy of the firmware version they bricked on. At least as the bare minimum to get started with. Be back tomorrow with the results.
Having trouble?
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder. (for ls991 sprint>https://drive.google.com/file/d/0B41ACD_ESYnHa3pIQlFLYUttdzg/view?usp=sharing
i have my g4 on 28a so it means is not possible yet with mine ? :S
This guy figured it out back in May. Exactly the method I used. Here is his guide> http://forum.gsmdevelopers.com/showthread.php?t=28897&highlight=VS986+REPAIR I can now confirm this works only with the files from the version of FW that the device bricked on. .
28a kdz mega link
gustax said:
i have my g4 on 28a so it means is not possible yet with mine ? :S
Click to expand...
Click to collapse
https://mega.nz/#!blN0UCRB!OqJbq776ePL_PNBjzzooGU8kwTPWLAHNyXQz52TxovI
I HAVE TRIED TO EXTRACT THE FILES FROM FW 28A WITH WindowsLGFirmwareExtract-1.2.5.0, I CAN EXTRACT THE DZ FROM KDZFILE BUT WHEN I TRY TO EXTRACT THE FILE FROM DZ, THE SOFTWARE CRUSHED, I HAVE TRIED WITH WINDOWS 10 AND WINDOWS 7 AND THE SAME ISSUE. THE KDZ IT IS OK BECAUSE IT IS THE ONE I USED TO UPDATE MY PHONE
COULD YOU HELP WITH THIS
i downloaded the fw 27c and tried to extract the dz and happened the same issue, so i guess the problem is te software, but i dont know what a i need, any advice?
gustax said:
i downloaded the fw 27c and tried to extract the dz and happened the same issue, so i guess the problem is te software, but i dont know what a i need, any advice?
Click to expand...
Click to collapse
I will try the extraction on my PC. I have learned something about this method this weekend. This is a one time shot. After the second attempt the device blows a fuse. I believe the firehose programmer is the same, but, the raw & patch files are specifically for the sprint. I think I may have permanently bricked a device attempting to re-create the scenario in which I was successful with during the first go at it. I'm gonna look at the 27C.kdz real quick
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
HelpOneplus6t said:
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
Click to expand...
Click to collapse
Did you figure it out?
FireRattus said:
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, thank you for your response.
I'm not sure the issue you had is the same as mine. My Oneplus 6T does not show up in the device manager at all.
I tried doing the unsigned device drivers thing, but when I select the folder that contains the onplus_android_winusb folder, it says it cannot find the drivers.
Sadly I think I have to give up on this one I am not very tech savvy and really don't know what else I can do.
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
HelpOneplus6t said:
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
Click to expand...
Click to collapse
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
FireRattus said:
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
Click to expand...
Click to collapse
Hi,
I believe you are right, that makes sense.
I see that the 1 phone that was fixable is very slightly different than the other 4- it doesn't have an IMEI code on the back, so likely it was a different version or something.
Where do I find the right recovery files? I searched for Verizon Oneplus 6t MSM Download Tool but I don't see anything different.
Sorry for my incompetence, I appreciate your help
I was able to fix a few more phones using the Tmobile 9.0.13 MSM Tool here:
[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
2 of the phones didn't work, they have Sahara communication errors still. I am not sure how to locate the right MSM tools for these- any ideas?
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
HelpOneplus6t said:
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
Click to expand...
Click to collapse
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
I managed to fix them by flashing the T-mobile version. This worked, but then I needed to unlock them since they were T-mobile locked. I converted them to the international version earlier successfully.
I am on 9.0.11 stock now! All I need to do really is update to 10.3.11
I will try following the links you have provided.
They are definitely 6ts
Thanks for your continued help.
FireRattus said:
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
Click to expand...
Click to collapse
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
Yes you are right but you do not need to download Every single update
I have found that these are the files I need to upgrade, I keep them saved for easy access
Code:
1-OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905(9.0.17).zip
2-OnePlus6TOxygen_34_OTA_047_all_2007171912_ac6dc9b(10.3.5).zip
3-OnePlus6TOxygen_34.J.48_OTA_048_all_2010042240_dbd576b615(10.3.6).zip
4-OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee(10.3.12).zip
If you wanted 10.3.11 instead of 10.3.12, I don't see why that wouldn't work
These are all the full upgrade zips, but if you have a locked bootloader and use the official update method through the settings, I have been able to use the smaller OnePlus6TOxygen_34.J.55_OTA_048-055_patch_2107132253_b96081(10.3.6-10.3.12).zip Upgrade Zip to go from 10.3.6 to 10.3.12
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
I have actually found from testing that I did not need to flash the 10.3.5 or 10.3.6 Zips and could go from 9.0.17 to 10.3.12 if I used the full flashable update zips
so I am not sure why it failed for you
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
HelpOneplus6t said:
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
Click to expand...
Click to collapse
I am glad I could help and I do understand the hesitation, it is smart to be careful and not flash the wrong recovery file, the only time I have truly bricked a phone was by flashing the wrong recovery
I use the fajita twrp from the official source that you linked but the version you want to use does depend on your android version
You can get a crash dump error by using the latest TWRP on older OOS
I have been using Jaguar ROM for the OnePlus6T
My own installation process is as follows and WILL WIPE ALL DATA ON THE PHONE
Assuming you are coming from Latest Official OOS 10 (10.3.12)
Enable Developer mode and OEM Unlocking (In the Hidden Developer Settings)
(Optionally enable USB Debugging to adb reboot to bootloader)
(You may have to Disable Driver Signature Enforcement on Windows 10/11 to install correct drivers)
Reboot your phone to Fastboot by holding volume up and down during power up or with "adb reboot bootloader" in terminal, allowing the connection on your phone.
In Terminal
fastboot flashing unlock
FastBoot to TWRP 3.5.2
fastboot boot twrp.img
Install TWRP 3.5.2 .zip and Reboot to TWRP
WIPE Data Factory Reset and type YES to confirm and Reboot to TWRP
Flash the ROM and then flash TWRP 3.5.2
Reboot to TWRP Again
Flash ROM again then TWRP again
Reboot once then flash magisk etc via twrp
The process is more simple to just install magisk on stock OOS and I hope soon Jaguar will update to android 12, then the latest twrp should work with it
You will of course also need to have the android platform tools installed
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Worst case scenario I have found with OP6T, like not able to boot into recovery or anything
I can just do a factory flash with MSM tool using the patched version and then follow the above steps again
Everything is working, thanks so much for your help- I will pay it forward.