After setting up Windows, OnePlus 6T is Stuck at the Qualcomm CrashDump Mode. I tried many solutions to no avail.
The problem may be caused by A/B, please try to flash boot again in fastboot, if it still does not work, use edl (9008) to unbrick
Maybe my statement is not very accurate. What I mean is that I can enter Android and see the loading screen of Windows, but when Windows is loaded, it will be stuck at the crashdump mode. I think this is a driver problem. Also, the boot I am using is the latest in the github repo, compiled by myself, and the driver is also the latest, but it still doesn’t work.
I tried the old version of the driver and upgraded the driver after installing the system, and found that it works.
There are still some questions:
My touch is not working (the device cannot be started, code 10)
Power management is not working
We have noticed that many people have encountered similar problems, but we still don’t know how this problem is caused. You can join the group chat to find out the cause of this problem.
When shutting down Windows, OnePlus 6T is also Stuck at the Qualcomm CrashDump Mode…
I have also noticed this problem, maybe it is occasional, sometimes it can be a normal blue screen (what am I talking about) XD
Yes, exactly. And I have found that if BSOD appears, Qualcomm CrashDump Mode will not happen. That’s strange.
This thread started way early before I encountered crash dump mode, may not be the same cause but I got the help from github, this thread should help with some cases
TheMorc went straight to the root cause and helped me fixed it
Thanks for your help!
Ok, the problem is raised by me, now I will summarize it.
The screen of my OnePlus 6T has been repaired and it caused this malfunction. The problem had been fixed by TheMorc, he provided a suitable touch driver.
I also Stuck at the Qualcomm CrashDump Mode now, but it only appears in certain scenes.
As you know, I have no idea to fix it and if you can, please contact me