Oneplus 6t stuck at Qualcomm CrashDump Mode

[Jishun]

I'm new to this forum and trying to install windows 11 pro downloaded with 22000.160_arm64_en-us_multi_fdb8a3c7_convert, after extracting with Dism++ and installed the drivers extracted with extract_mac.sh, it crashed while installing,
all.txt

suspect some drivers may broke the installation. once it crashed, it won't continue again. instead showing an error dialog
'The computer restarted unexpectedly or encountered an unexpected error.' This message also states the following: 'Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation'
don't know what to do
attached the list of files that was extracted . happy to try more if any clues can be provided.

[GoldRenard]

Crashdump on boot is often caused by modem firmware. Sometimes it crashes, sometimes it boots.

If it crashes hard before even first boot forcing you to redeploy everything again and again, as workaround you can try disable AMSS subsystem temporarily so modem firmware will not be loaded and you will be able to pass OOBE to get windows installed and working.

Extract all the drivers as usual. Find a qcsubsys850.inf driver and look for a AMSS descriptor there by its id DEV_023E. Rename it to something like DEV_9999, save and install this driver like that so this subsystem will not be installed, initialized and will not cause a crash. This way wlan/lte will not work but at least you can pass OOBE.

Once you pass OOBE and boot to the desktop, revert inf changes and reinstall original driver using dism++ from PE to get wlan/lte. Try to boot it, it may crash again but reboot it again and again until it finally boots (probably).

I would also recommend to disable windows recovery in BCD so it will not attempt to recover windows installation after crashes

bcdedit /set {Default} recoveryenabled no

[Jishun]

Thank you so much for your comment!
happy to follow your instructions and try again, though I'll need some time to get back to this

just one more thing to confirm
the qcsubsys850.inf does sound logical to me, however, when I tried to boot windows without driver then install the drivers little by little. I did it this way because booting windows without drivers will let it finish the installation so it doesn't stuck to repeating, I think I can revert the change if any driver is breaking it , but I'm not sure if that's a right assumption,

with this approach . I'm sure I did install the Subsystem folder which included this file. the windows did boot without error but didn't enable anything visible to me. did I not take it into effect at all?

[GoldRenard]

Some drivers depends on each other. Subsystem might not be loaded if some of its dependencies are missing so it will not cause a crash even if the subsystem itself is present.

[Jishun]

thanks!!, I couldn't resist trying it again.

you are right. when I modified the qcsubsys850.inf it was able to install. the touch screen worked and I was able to navigate to wifi step then it won't allow me to go through

I then tried to shut it down by using the power button and slide down. the CrashDump happen when it shut down... it didn't matter of course

I then went back to win pe, deleted all drivers and installed all again with only the qcsubsys850.inf is restored back , and rebooted it to windows, but.. I'm not seeing the wifi working so I'm still stuck at the network step :(

[GoldRenard]

Maybe force-refresh hardware configuration after reinstalling driver packages would help in this case. While in PE, mount the \Windows\System32\config\SYSTEM registry hive of your windows installation, navigate to HardwareConfig key and delete all its values and subkeys so windows will reconfigure the hardware on next boot.

I would also suggest to pass network step using USB Tethering from other device.

[Jishun]

The registry approach didn't work for me, I used another phone to finally get over the network requirements
after I got into the system, the wifi still didn't work, I finally found that I can simply uninstall the wifi and lte adapter in device manager and a re-scan will bring them back on working state. all good, except I found I installed win 11 Home version.

now I'm doing all over again, this could be a useful instruction for others.

Thank you for your help!

[Jishun]

weird that when I did this in win11 Home, it worked with the first shot,
however I'm now stuck at refreshing the hardware in pro edition, I can open up device manager and delete the wifi adapter ( not seeing lte adapter, weird too) I can delete the device, and when I click on scan for changes , it gets into crashdump mode in one second, i tried several times with no luck.

i can't think of more that i could have done differently this time :(

[Jishun]

got it working, by
opening the device manager and delete wifi adapter ,
restart instead of scan
scan after restarted, now i have wifi, still don't have LTE..

battery is interesting, when it started with cable connected ( I use fastboot boot uefi.img) it shows charging but the power drops.
if I unplug the cable and connect it back after it started, it doesn't show charging at all

[TheMorc]

battery is interesting, when it started with cable connected ( I use fastboot boot uefi.img) it shows charging but the power drops. if I unplug the cable and connect it back after it started, it doesn't show charging at all

OnePlus uses a proprietary chip for charging so charging works properly only with a USB-C PD@5V charger

[TheMorc]

and for LTE, did you backup QCN using the qualcomm tool or Modem+EFS in TWRP?
it's required to backup it, install Windows and restore it afterwards because if you don't do this step you won't have LTE working in both Android or Windows

[Jishun]

I haven't figured out how the charging works , the only way I can get it charging in windows is to boot to fast boot and connect to my mac and boot with fast boot command fastboot boot uefi.img , and I can't unplug it , if I do, it stopped charging, plugging back in will make it charging the mac instead. ..

I tried my usb-c 5v PD charger, it can charge while in twrt, but doesn't charge when I boot with fast boot( boot from mac then unplug to switch to charger , nor when I flashed uefi to the boot partition and boot from the phone) . .

[Jishun]

and for LTE, did you backup QCN using the qualcomm tool or Modem+EFS in TWRP?
it's required to backup it, install Windows and restore it afterwards because if you don't do this step you won't have LTE working in both Android or Windows

this I'm entirely not aware of, definitly didn't backup, but I didn't change anything else but the boot and android user data partition. my android still boots well and able to recognize both sim slots.
and I'm also very sure when the first time I installed win11 home edition. it has LTE adapter at the side of wifi adapter, in network config it also shows insert sim message as I don't have a sim for this phone

but now in this new installed win11 pro, there isn't this adapter at all. android is not affected anyhow though.

btw, the GPU had an issue shown in device manager, I didn't check it before I finished other setup , after several reboots (rebooted for other purpose, now it is showing no issues )

[flyingduck234]

Try resetting the phone to factory. Install win 11 and 1.0.3 drivers.

[timeallover]

Backup Modem+EFS in TWRP can fix LTE win11 pro,maybe you can use MsmDownloadTool(9008/EDL),then backup in TWRP

[bladeboy2021]

By turning off dormancy and shutting down the cell phone cellular network driver (qualcomm mobile broadband device), Qualcomm crash dump mode can be basically solved, long standby to dead power will not crash, play some games suddenly darkened and never appeared again, basically can be daily. The first time you brush win11 into the system, if you don't get into the system with Qualcomm crash dump mode, you can try twrp to brush with other lower versions of UEFI, or go into pe to delete a driver that's not a core, or go into Android and switch to win11. You can go into the win11 system and you can solve it in this way.