Hey guys was using my phone, Bluetooth on music streaming and I was typing away on WhatsApp and all of a sudden my phone froze up and then black screen. Then a few seconds later got a Qualcomm Crash dump screen with something about modem crash?
Anyone have this issue? Was able to reboot device after holding volume up and power button for a few seconds.
I havent had the issue myself but I've heard other OnePlus devices with this problem. Luckily you were able to fix it with a reboot but worse comes to worse you'll have to use the MSM tool.
What does the msm tool do? I've seen weird things with the phone, it does this shift to the screen sort of like you are taking a screen shot of the screen.
I do have this problem too since 2 weeks. I´m not rooted and not Bootloader unlocked. (waiting for my favourit rom)
It happens randomly. I didn´t had the time to go into it.
This is the issue see image
ludester said:
This is the issue see image
Click to expand...
Click to collapse
Yesterday, after flashing OOS 10.0.1 again to go back to stock kernel and after flashed xXx_NoLimits_module, and while REBOOTING, I got into Qualcomm Crash dump screen and somehow I managed to boot back to system.
After trying couple times to enter twrp(VolDown+Power Button), with VolUp+Power Button I got into system again
id get that when is select wrong slot in twrp but when i change it back to slotA it reboots as normal i never get it at random though came up when selecting slot b to active.
refedit said:
Yesterday, after flashing OOS 10.0.1 again to go back to stock kernel and after flashed xXx_NoLimits_module, and while REBOOTING, I got into Qualcomm Crash dump screen and somehow I managed to boot back to system.
After trying couple times to enter twrp(VolDown+Power Button), with VolUp+Power Button I got into system again
Click to expand...
Click to collapse
Use msm tool to load everything to stock and then try update again. Using msm tool fixed my issue
ludester said:
Use msm tool to load everything to stock and then try update again. Using msm tool fixed my issue
Click to expand...
Click to collapse
So far I'm good. It didn´t boot to QUalcomm screen again.
Although, to prevent future issue, I'm backing up everything so I use the msmtool. Although, I don't if the issue isn't related from Upgrading from Android Q to A10. So I rather'd use the msm tool with Android 10. As far as I know, there's no msm tool for BA version
Related
Hi,
SITUATION : I just had a big problem with my OP6. First of all, I was on Oreo stock Rom and I decided to upgrade to Pie by flashing .zip via TWRP. Everything goes well, but after some days of use and for some reasons I wanted to roll-back to Oreo and I flashed the downgrade .zip but this time via Local upgrade. Again, everything goes well but when trying to flash TWRP via Fastboot, I used "fastboot boot TWRP.img" and phone booted into it. Then, BEFORE flashing the TWRP.zip file I accidentally changed the slot (b to a) and rebooted to system.
PROBLEM : Now, the device is stucked on a black screen with withe notification LED on, and whatever the situation. Bootloader isn't accessible anymore. None of the buttons combination work properly. I don't know what to do. I looked for MSM software but do I need to access Bootloader to use it ? It's possible to power off the device (white LED turn off), but nothing more.
Thanks for any future advices
power off ur device !!!
open msm software and connect ur phone through usb and press up volume + power button and u will see it getting connected to the msm software and leave it till ur phone starts booting ito OOS 5.1.5
Here is the Link to the MsmDownloadTool V4.0:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
With this Tool, you get your Phone working again.
StandBrik said:
Hi,
SITUATION : I just had a big problem with my OP6. First of all, I was on Oreo stock Rom and I decided to upgrade to Pie by flashing .zip via TWRP. Everything goes well, but after some days of use and for some reasons I wanted to roll-back to Oreo and I flashed the downgrade .zip but this time via Local upgrade. Again, everything goes well but when trying to flash TWRP via Fastboot, I used "fastboot boot TWRP.img" and phone booted into it. Then, BEFORE flashing the TWRP.zip file I accidentally changed the slot (b to a) and rebooted to system.
PROBLEM : Now, the device is stucked on a black screen with withe notification LED on, and whatever the situation. Bootloader isn't accessible anymore. None of the buttons combination work properly. I don't know what to do. I looked for MSM software but do I need to access Bootloader to use it ? It's possible to power off the device (white LED turn off), but nothing more.
Thanks for any future advices
Click to expand...
Click to collapse
I hope u fixed it by now, but if you still haven't fixed it yet, you can go back to slot b by using this commands "fastboot --set-active=B" without the quotes
Because I messed up my slot a, so i used that command to boot using slot b and it worked. So, if the problem is with your slot a and everything with your slot b is fine, then you just need to change to slot b with that command and all should go well :highfive:
just noticed that you're having a problem accessing the bootloader. First, make sure your device is not connected to your pc or anything. Then, whether your device is off or stuck in that black screen, just hold vol up and power off at the same time and wait until it eventually boots into the bootloader mode.
Problem solved with MSM software. Thanks everyone. If someone has the same issue. Just download MSM software and use the following guide :
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
It is actually quite impossible to totally hardbrick a device like this one.
Cheers
Glad to hear that.
Just in case i got into that problem, could you lead me to the files you downloaded since the ones in that link seem to be for OnePlus 5
In my situation, I have a black screen, and a fixed blue LED.
I want to put the LineageOS ROM, but it's impossible, even though it performs the installation of the ROM correctly, when you restart it that happens, and then it doesn't even let you install or start the TWRP again.
It only remains to use MSMDownloadTool, to return to the Stock rom.
So, i`m pretty sure my phone is hard bricked.
I was running with it for several months with no issues, so today i decided to flash EK 1.15 and then rebooted my phone, but instead of booting it went to CrashDump Mode and i can`t get it to boot or enter fastboot.
I`ve tried to use MSMtool but to software does not recognize my phone and on the device manager it shows as `Qualcomm HS-USB Diagnostics 900E`, on the CrashDump it shows `Could Not Decompress Initial ramdisk image.rd_load_disk`.
I`m opening a ticket with OnePlus, but as i live in Brazil and this phone was imported i think i`m fu****
Does anybody had this problem or knows if it is indeed a hardbrick?
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
I'm so glad you got it up and running again! There's nothing worse than thinking there's no way out!
bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
Glad to see you got it. I had the same issue few days ago and, indeed, it was quite hard to run fastboot mode.
Sent from my GM1913 using XDA Labs
Good recovery! Cheers
I had a OnePlus 6t around the time they first came out and I ended up in crash dump mode probably 12-15 times, sometimes just randomly without doing anything to my phone..I would look at it and it was in crash dump. I recall the devs saying something about a fix for it back then... I have a OnePlus 7 pro 1917 global model now and I bought it used and only had it about one week now. Same exact cinereous. I looked down at my device on day one of me having it and there it was, crash dump mode. Since then on my Guac I've seen crash dumb four times. I've only flashed dotOS and DerpFest but the first crash dump I experienced on this phone was before I flashed anything. I was stock with TWRP installed.. I'm back at my home base now so if and when it happens again ill grab logs and share them. I have always been lucky enough to be able to get control of my device back by holding down power+ volume until I boot to bootloader and then tap power at the "start" screen and ive always booted back up. Have you all experienced crash dump mode often on 7 pro? Hopefully this will be fixed we some point.
Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan
Check this:
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode
Mohamedkam000 said:
Check this:
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode
Click to expand...
Click to collapse
As I have said earlier it is hardware issue not software so MSM tool has low chance of fixing it. It might succeed and boot but crashdump will come back again.
drsaog said:
Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan
Click to expand...
Click to collapse
Same here..
Now i'm scared of using OOS
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
Thanks for the reply, I will try this as a last resort, but I've already rebooted my phone many times and I can't boot into OOS..
tiga016 said:
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
Click to expand...
Click to collapse
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
adeklipse said:
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
Click to expand...
Click to collapse
The same thing happened to me about a year ago. After completing the msm tool procedure my phone got stuck in a permanent bootloop w/ the bootloader locked of course. I suggest using the msm tool sparingly as this happened to me after about the tenth time I used it.
First of all thanks to the contributors here for pulling together the user guides for unbricking the phone. I am in a rather weird situation. While trying to flash my hard-bricked onePlus 6 - I think the battery was low, and the download did not complete fully. Since then, I have recharged the phone but the download gets stuck on this error: Firehose GetUSInfo Failed
I think my phone does not power-off fully somehow. I keep holding the powerbutton for over a minute, but the minute I connect the phone to my PC, it gets recognized immediately with the correct Qualcomm 9008 port. So the drivers are correct, and the PC recognizes the phone correctly.
Any idea how to switch off the phone fully, and then how to get past the 'Firehose GetUSInfo Failed' error?
Thanks in advance!
bro izi fix, i get this before and oneplus agen in jordan cant fix it so i fix it by myself, now im going to sleep pls send me a msg on telegram ( @NotReal0 ) i will learn you how to fix it but pls tomorrow u go to any pro dev shot ask them to get you the imei partation EFC that file have imei number and mac address you will need it for real
just send me a msg so i can help you step by step
( i dont need your money )
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
I have an OP 9 LE 2115 Global in USA
I was on LOS 19.
I had some issues and wanted to revert back to stock OOS 11.
First I tried via Recovery to flash Stock ROM OOS 11, but I had an error regarding the system version being too old and it didn't complete. The phone would no longer boot to OS.
I got the MSMDownloadTool from here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9/Global_LE25AA/R/
I used the tool successfully and got my phone booting to OS again.
But now my power button IMMEDIATELY turns off the phone whenever pressed, and does this kind of CRT TV shutdown, where the screen phases out vertically with colors.
This happens in recovery/fastboot menus as well, most of the time, and makes booting into recovery/fastboot *almost* impossible, as when I let go of the power button it turns off, and when I select and option with the power button it shuts off.
Any information would be so helpful! Thank you fine knowledgeable people of XDA.
For anyone to help, we need to know which model you have and which version of msm tool did you use?
Updated my original post. My apologies for the lack of important details.
Also I got a TWRP recovery successfully installed, so I have a recovery again.
I found this article that explains how to install each part individually via fastboot
Do you think this would help with my errors of non-existent partitions?
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
I'm tempted to try, but if anyone could chime in first?
Still having this issue, has anyone ever even heard of this problem?
wakeeshi said:
Still having this issue, has anyone ever even heard of this problem?
Click to expand...
Click to collapse
This sounds like a hardware problem. If just after msm the phone does this, hardware it is then.
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
wakeeshi said:
Thank you for the reply.
Do you have any more information or an idea on how to fix it? Or are you implying I may have caused permanent damage?
Click to expand...
Click to collapse
Flash with msm again. If problem persist after first time setup, hardware problem.
MrSteelX said:
Flash with msm again. If problem persist after first time setup, hardware problem.
Click to expand...
Click to collapse
I have flashed with MSM a couple more times and same thing.
But for example, I got it to boot without the issue again, and everything works as normal, but as soon as I turn the phone off or it dies, I will struggle to get a boot that works properly.
I end up fiddling with the holding the volume buttons and power buttons in different combinations and eventually it works. I'm not sure if that's just random, or if I'm actually causing it.
If I can have a completely working boot, where the power/sleep button functions as normal, it seems like it's a firmware, data issue. Could you elaborate?
Thank you!
Hoping to bump this and try to get some help. My GPS also has failed to get a fix in this kerfuffle. (this is one of the reasons I was originally resetting to stock from LineageOS 19). Any advice?
Hardware problem and the fact it is 100% repeatable is a sign of hardware problem.