-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oneplus 6t stuck at Qualcomm CrashDump Mode #26
Comments
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 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
|
Thank you so much for your comment! just one more thing to confirm with this approach . I'm sure I did install the |
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. |
thanks!!, I couldn't resist trying it again. you are right. when I modified the 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 |
Maybe force-refresh hardware configuration after reinstalling driver packages would help in this case. While in PE, mount the I would also suggest to pass network step using USB Tethering from other device. |
The registry approach didn't work for me, I used another phone to finally get over the network requirements now I'm doing all over again, this could be a useful instruction for others. Thank you for your help! |
weird that when I did this in win11 Home, it worked with the first shot, i can't think of more that i could have done differently this time :( |
got it working, by battery is interesting, when it started with cable connected ( I use fastboot boot uefi.img) it shows charging but the power drops. |
OnePlus uses a proprietary chip for charging so charging works properly only with a USB-C PD@5V charger |
and for LTE, did you backup QCN using the qualcomm tool or Modem+EFS in TWRP? |
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 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) . . |
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. 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 ) |
Try resetting the phone to factory. Install win 11 and 1.0.3 drivers. |
Backup Modem+EFS in TWRP can fix LTE win11 pro,maybe you can use MsmDownloadTool(9008/EDL),then backup in TWRP |
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. |
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.
The text was updated successfully, but these errors were encountered: