Related
My friend is using OP6 with stock rom and bootloader locked. He never made any modifications to his phone. Yesterday, he was playing a game and suddenly it went to Qualcomm crash dump mode. After trying several times it was booted in safe mode but crashed again after 10 minutes. I tried to repair it using Msmdownload tool. Everything went fine, tool showed that download was complete. Now, the phone doesn't even turn on. It is just showing black screen from very long time but the notification light is on. I am not even able to go to fastboot mode now. Please help.
Good morning and happy new year( and i guess it didnt start well for your friend) very strange behaviour, maybe you downloaded files for other variant than the phone (64 or 128 or 256 or a6000 or 6003 i dont know i used the tool only with the oneplus one) try to go to qloader mode( if it is like the opo i didnt use it at all ) and try to calm down, put it on charge even if it will not show it and try again that's all i can help with
Edit: just saw the thread about unbricking a'd didnt notice other varient roms only oxygen and hydrogen, be sure that the qualcomm drivers are installed well and try again
Are you sure this isn't a hardware failure?
Chinaroad said:
Good morning and happy new year( and i guess it didnt start well for your friend) very strange behaviour, maybe you downloaded files for other variant than the phone (64 or 128 or 256 or a6000 or 6003 i dont know i used the tool only with the oneplus one) try to go to qloader mode( if it is like the opo i didnt use it at all ) and try to calm down, put it on charge even if it will not show it and try again that's all i can help with
Edit: just saw the thread about unbricking a'd didnt notice other varient roms only oxygen and hydrogen, be sure that the qualcomm drivers are installed well and try again
Click to expand...
Click to collapse
The drivers are installed well and the tool detected the device fine. I used the tool again but still there is no response . Anyways thank you and wish a very happy new year to you too.
Gionikva said:
Are you sure this isn't a hardware failure?
Click to expand...
Click to collapse
Not sure. Anyway to diagnose for hardware problems?
KrishTej said:
The drivers are installed well and the tool detected the device fine. I used the tool again but still there is no response . Anyways thank you and wish a very happy new year to you too.
Not sure. Anyway to diagnose for hardware problems?
Click to expand...
Click to collapse
Send it to oneplus.
Gionikva said:
Send it to oneplus.
Click to expand...
Click to collapse
Turns out it hardware problem. They replaced the motherboard and now it's working fine.
I have made huge mistake and i dont know what to do and would really appreciate some help. I was on Open Beta 17 with magisk and twrp and i decided i wanted to revert the stock using msmtool. I have used it before so i know about all the drivers to install and how to get to edl and so on. So i started the msm software and hit start, but a few seconds into the flash i got the an error "firehosewritedata failed" and since then my device cant be recognised by my computer and its not booting up or even showing that its charging. I tried reinstalling the drivers and trying msmtool but the device isnt recognised at all.
Booting into fastboot only says Update download failed please check your download flow is right
Oh boy, that's a really bad situation. Is your EDL working? In EDL are you seeing the device as Qualcomm device in the device manager? If neither, try installing the Qualcomm drivers again and try EDL again..if still problem persist, head straight to the nearest service centre...
check this link too..
https://forum.xda-developers.com/oneplus-7-pro/help/ultra-hard-brick-t3947127
Use a USB 2.0 port.
amirage said:
Oh boy, that's a really bad situation. Is your EDL working? In EDL are you seeing the device as Qualcomm device in the device manager? If neither, try installing the Qualcomm drivers again and try EDL again..if still problem persist, head straight to the nearest service centre...
check this link too..
https://forum.xda-developers.com/oneplus-7-pro/help/ultra-hard-brick-t3947127
Click to expand...
Click to collapse
MrSteelX said:
Use a USB 2.0 port.
Click to expand...
Click to collapse
Thank you for the feedback, and the late reply. I eventually reinstalled all oneplus drivers again and put windows to debugging mode and tried one more msmtool flash, and after a lot of praying and swearing it finally flashed successfully. For future reference, windows debugging mode is a good place to be in for doing these flashes or to ensure no fails.
Hi, I have a problem that the program cannot see my phone. I have already tried to update the drivers as it is in the manual but it does not work. Do you have any ideas? My phone starts in crashdump mode
czoter said:
Hi, I have a problem that the program cannot see my phone. I have already tried to update the drivers as it is in the manual but it does not work. Do you have any ideas? My phone starts in crashdump mode
Click to expand...
Click to collapse
Are you using windows 10
Greetings to all
After flash rom on fastboot and rebooting the device, the device entered the recovery, but the recovery is not working just black screen
I have pressed the power button and volume down button for a long time but nothing works
Currently the device is completely damaged!!!
I want to get into the bootloader in any way
Power up and connect to a Windows PC, what does the device manager display?
ULTRAJC said:
Power up and connect to a Windows PC, what does the device manager display?
Click to expand...
Click to collapse
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
twuijri said:
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
Click to expand...
Click to collapse
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update.
Click to expand...
Click to collapse
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
OhioYJ said:
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
Click to expand...
Click to collapse
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
twuijri said:
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
Thank you from the heart. I read the entire topic and tried all the methods. It took me 10 hours to work
I was so frustrated that I thought about buying a new device
Only 10 hours after knowing the solution of MsmDownloadTool There was a whole day after the device died
Thank you, thank you for everything you do to serve others
""All user from XDA ULTRAJC & OhioYJ""
The device has returned to work
I have an extremely big problem, maybe someone could help me here?
So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.
Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.
I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
Rayekk said:
I have an extremely big problem, maybe someone could help me here?
So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.
Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.
I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?
Click to expand...
Click to collapse
See link below. Worked for me I was in same position.
ctonylee1965 said:
See link below. Worked for me I was in same position.
Click to expand...
Click to collapse
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Rayekk said:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Click to expand...
Click to collapse
Make sure you look at the rest of the instructions to get back on global from Indian.
Rayekk said:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Click to expand...
Click to collapse
Brother what is your phone model is it Chinese (Le2110)? or another model ?
bro i have the same issues , did u found any solution & can you help me plz
See if these steps work for you: (last post)
Display becomes unresponsive after OOS 12 update
I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever. I upgraded from OOS 11.2.10.10 to OOS...
forum.xda-developers.com
Hey, i have hardbricked my OnePlus 9 and now i have the connect and disconnect-problem in the EDL-Mode. My Model is a Lahaina and i hope it is the same like a Lemonade or a OnePlus 9. I was on the latest Android 12 for the OP 9 before it gets bricked. How i bricked my phone: First i have unlocked the Bootloader and after that i was trying to boot into TWRP. The bootscreen from TWRP comes and the screen gets black and then into boot dump mode. okay, then i installed this: https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/unread and the message <awaiting any device> shows up and i disconnected my phone. After that my phone just shows black and on the pc it just shows up the "QDLoader" (yes, the driver is installed) . How i could bring my phone back to life and fix the partitionproblem/connect & disconnect problem. The MSM just shows "Status of Connection: N/A" and "Waiting for device". I am using an Laptop with Windows 10 on it and an intel chipset.
I think i have killed the partitioning of the oneplus by downgrading from A 12 to A 11. Thanks for your help. By the way: I have downloaded the MSM with Indian OS and I have still the same problem.
I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?
kischde said:
I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?
Click to expand...
Click to collapse
Check this out:
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
DerBaLu841 said:
Check this out:
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi! Have you telegram? Can I ask to you help with the method you posted?