Qualcomm crashdump mode что делать

【HELP!】QUALCOMM Clash Dump Mode

Breadcrumb

dogman.jp

New member

MrSteelX

Senior Member

Hako06

Member

The Marionette

Senior Member

I had the same issue but I could actually boot into GSIs. Although it would reboot into the crash dump screen after the phone went to sleep.

Flashing stock 5.1.11 did temporarily fix it but as soon as I installed any custom rom, the issue would return.

Long story short, some file got corrupted or something and nothing besides an EDL flash can fix it. You need to enter EDL ( power off the phone, hold volume up for 10 seconds and connect it to the pc while still holding vol up ) and if your PC recognizes the phone as qcom 9008 or something like that, open up the program and let it flash all the stuff onto the phone.

After it’s done, the issue should be solved.

ereneren564

Senior Member

I had this issue while I was trying to port roms. What I did was go to fastboot, boot twrp, flash OOS OTA.

Edit: Now I’m dead stuck at crash dump mode. I cant boot TWRP over fastboot it goes back to crash dump mode and I dont have windows machine so I cant use MSM tool I will try fastboot OOS installer now.

Edit2: I managed to boot the phone now. I have followed the following way:

1. I have dumped the Beta 3’s payload.bin with: python payload_dumper.py payload.bin
2. I have flashed the following partitions through fastboot:

fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img

And it works after that. If you can’t dump the files, I can upload them for you.

The bad thing is, you can’t install custom rom, custom kernel, install twrp or do anything that makes Oneplus Oneplus. This needs to be fixed as soon as possible.

Источник

Qualcomm crashdump mode что делать

По вопросам наполнения шапки обращаться к куратору темы AcidRain2010

IN: 11.0.4.5.KB05DA (Индия)
EU: 11.0.4.5.KB05BA (Европа)
NA: 11.0.4.5.KB05AA (Другое)

Распространение в ближайшие дни

ukv29, пишут что это хот фикс, changelog тот же что и для 11.0.3.4

We are starting to push the incremental rollout of a new OxygenOS hot-fix update for the OnePlus 8T in India. Europe and North America will soon follow:

IN: 11.0.4.5.KB05DA
EU: 11.0.4.5.KB05BA
NA: 11.0.4.5.KB05AA

Changelog
System
Optimized the call stability
Improved system power consumption performance to reduce heating
Improved mis-touch prevention to offer better gaming experience
Optimized fluidity with some mainstream games to reduce lagging risks
Optimized user experience with Alert Slider by adding toast messages when switching among the 3 modes
Fixed the issue that the status bar kept hovering on the screen in landscape mode
Fixed the issue that NFC cannot be turned on in a small probability
Camera
Optimized the imaging effect to bring you with better shooting experience
Improved camera stability
Network
Optimized mobile network connection to improve the network intensity with signal
Fixed the small probability issue with network interruption while playing games

Для замены HydrogenOS на OxygenOS необходимо:

Обновление/замена прошивки с помощью утилиты Oxygen Updater:

Источник

Qualcomm crashdump mode что делать

AFH | Minimal ADB and Fastboot | 1.4.3 | Setup.exe
AFH | Minimal ADB and Fastboot | 1.4.3 | Portable.zip

ZippyShare | 15 seconds ADB Installer | 1.4.3

4PDA | Qualcomm USB-Driver
4PDA | ADB Driver Lite (32/64-bit)

4PDA | Platform-tools с поддержкой Windows XP | r.23.1

Тема на XDA
MTP:
RedWolf-installer-enchilada-3.2.2-0.zip ( 16.85 МБ )

По вопросам наполнения шапки, обращайтесь к модераторам раздела через кнопку под сообщениями, на которые необходимо добавить ссылки.

Правильно ли я вижу последовательность действий для свободной установки кастомных прошивок?
— устанавливаю adb драйвера
— разблокирую загрузчик
— прошиваю на постоянку twrp
— получаю рут прошивкой magisk

В дальнейшем скачиваю прошивку в zip и устанавливаю через twrp?

Не совсем понял, как потом xXx NoLimits 2.0 установить?

igur723110, если я не знаю, что за модуль, логично что и не знаю где лежит. Но спасибо за информативный ответ :rolleyes:

Если сам магиск шью, зачем модуль то ещё какой то? В чем смысл?

fantomrik, Почитай в Гугле о магиске, ставятся доп. модули, можешь скачать ХХХ полную прошивку 1.8 г, можешь модуль, функции одинаковые. На XDA подробно описано как ставить, как менять плюшки при установке.Прошивка получше стока. Можно заменить звонилку от Гугла.
Неплохо редактирует систему Renovate.

Это автор NoLimits? Или модуль для magisk?

igur723110, благодарю!

И renovate и NoLimits ставятся как модуль magisk и удаляются так же легко выходит?

Вышло обновление ядра «Flash Kernel» :happy:

Самое главное для меня, что ув. Nathan по моей просьбе добавил поддержку фиксации TTL. Всё работает!

А так вот short changelog:

Это старое ядро, для первых версий Орео. Новые версии ищите на XDA.

тут какое-то интересное TWRP попалось. может я не совсем понял, но вроде как пр прошивке не слетает (нужно тестить). проинструктироваться и забрать можно тут ТЫК
а ещё там ядер развелось, как грибов после дождя. пора спойлер в шапке делать

Источник

How to Fix Qualcomm CrashDump Mode in OnePlus

In this guide, we will show you the steps to fix the Qualcomm CrashDump Mode in OnePlus devices. It’s no hidden secret that this OEM is among the most active players in custom development. Be it for flashing custom ROMs to installing a custom recovery like TWRP, there’s a lot to try out.

Likewise, you may even try out a plethora of mods such as Magisk Modules, Xposed Framework, Substratum Themes, Viper4Android, etc. However, each of these tweaks comes with an associated risk factor as well. Issues such as bootloop or soft brick could still be easily dealt with by flashing the stock OxygenOS ROM via Fastboot Commands.

However, it is issues involving hard brick that is mostly a cause of concern for many users. In this regard, the CrashDump Mode is among the most concerning issues for a lot of users. If your device is also getting bugged with it, then fret not. In this guide, we will outline two different methods to fix this Qualcomm CrashDump Mode on your OnePlus device. Follow along.

What is Qualcomm CrashDump Mode

When your device’s partition gets corrupted (mostly the system partition), then it wouldn’t be able to boot to the OS. Along the same lines, you wouldn’t be able to access Fastboot and Recovery Mode either. You would only see the Qualcomm CrashDump Mode written in the top left and in some instances, a little technical information beneath it.

If at this instance, you take your device to the Service Center, then it would classify it as a hardware issue and would inform you that the motherboard has been damaged. You would then have to shell out a lot of bucks to get it rectified.

However, truth be told, it is never a hardware issue in the first place. It is just a software issue that would no doubt require quite a few efforts, but could still be rectified by the user itself. So with that said, let’s get on with the guide to fix the Qualcomm CrashDump Mode issue on your OnePlus device.

How to Fix Qualcomm CrashDump Mode in OnePlus

There are two different methods to deal with this issue. It is highly recommended that you start off with the first one. And if it doesn’t work out, then proceed with the next method.

Method 1: Exit the Qualcomm CrashDump Mode

Well, if you haven’t performed any system-level tweaks but were still taken to this mode, then chances are you end up pressing the incorrect hardware key combinations that took you straight away to this mode. So in this regard, your next course of action is fairly simple- you simply need to exit this mode. To do so, press and hold the Power and Volume Up button for around 8-10 seconds.

Doing so shall force-shutdown your device. Once that happens, just press the Power key to turn on your device. Your device shall now boot to the OS and this should have fixed the Qualcomm CrashDump Mode issue on your OnePlus device. However, if that doesn’t happen, then you have no alternative but to flash the entire firmware using the second method given below.

Method 2: Flash Firmware using MSM Download Tool

Every Qualcomm-powered device comes with a special Emergency Download Mode. We will now be using this mode to force-flash the unbrick firmware onto your device using the MSM Download Tool. However, this method will wipe off all the data from your device. So if by any means you could take a backup, do so right away.

Moreover, you cannot download this tool as a standalone version, rather it comes baked in with the device firmware. So make sure to download that corresponds to your device and region only. All this have been explained (with screenshots) and the download link has been provided in the below-linked guides, please refer to it:

So with this, we round off the guide on how to fix the Qualcomm CrashDump Mode on your OnePlus device. We have shared two different methods for the same. If you have any queries, do let us know in the comments section below.

About Chief Editor

Sadique Hassan

A technical geek by birth, he always has a keen interest in the Android platform right since the birth of the HTC Dream. The open-source environment always seems to intrigue him with the plethora of options available at his fingertips. “MBA by profession, blogger by choice!”

Источник

Oneplus 6T qualcomm crash dump error, recovery not working

Breadcrumb

flash713

Senior Member

The story and how it happened:

What happened: op states that his OnePlus 6t went to crashdump screen on its own one day and he cannot get out of it. Device was not modded at all when this occured. Went to a service center and they told him he needed a motherboard replacement.

Has a locked bootloader.
Developer options and usb debugging are NOT enabled.
Phone will only go to fastboot mode by doing button press combo..

osm0sis

Senior Recognized Developer / Contributor

gazitonmoy

Member

ms2020

Member

Thanks for your help so far.. at least it gives satisfaction that i have tried before dumping..
I am not going for motherboard replacement as u can buy new one by adding few extra.. if i come across a used one with working motherboard i may still try to get it fixed. as i liked my op6t
Also learnt a lesson to keep developer and debug options enabled.

The story and how it happened:

Has a locked bootloader.
Developer options and usb debugging are NOT enabled.
Phone will only go to fastboot mode by doing button press combo..

flash713

Senior Member

From what I’ve read there are two outcomes when crash dump happens. Either you can do like I did or if that doesn’t work run MSM tool how the directions say to run it or you are pretty much screwed.

I was just going to say and I know this sounds really dumb but have you tried holding down those 3 buttons for say a minute straight? Pretty sure you have already tried this o just figured I’d come and make one last comment here and hope like hell it will help.

There must be multiple ways why a qualcomm device goes in to crash dump mode and multiple things that occur that send it there. I’m going to dig deeper about it and see what I can try and learn.

ms2020

Member

ofcourse have tried and within 10 seconds i get fastboot menu.

There must be multiple ways why a qualcomm device goes in to crash dump mode and multiple things that occur that send it there. I’m going to dig deeper about it and see what I can try and learn.

svaika

New member

Hi all. My problem was not as described in your messages, but I bought from eBay 6T, and it was lagging with screen goes off and then on, problem. Thanks for your fresh messages, I just downloaded:

So thanks for your messages in the forum, I fixed the problem. By the way, the same help OnePlus wanted to do with remote session, but they just finished answering me by e-mails It is fear enough, the unit is out of warranty by purchase date for sure, but they at first wanted to help, then just silence started. and still is. Thank you guys, you saved one more OnePlus 6T

P.S. I was afraid, what flash713 wrote, that I shouldn’t unlock second time bootloader, but I had nothing to loose. Well, 120 euro, but I just won perfect phone

flash713

Senior Member

You tried running the msm tool and your computer can’t see your device once you connect to it or?? What does device manager say when you are hooked up doing the button press combo? I know for me I had to remove the Qualcomm drivers, reinstall them and reboot before msm worked for me on my 6t. Your device is an international model or T-Mobile model that you converted?

@svaika
If you ever end up just out of the blue getting put in crash dump mode and your bootloader is locked and USB debugging and developer options isn’t on then there is no way to fix it. Because people have been reporting this happening on 6t devices I would definitely keep BL unlocked and Dev options on and USB debugging on. It makes the difference whether or not you will be able to fix your device «if» you are ever in this same situation..

Sidenote: Since I started first using custom roms, kernels and themes on Android and still to this very day the very first thing I do when I install a rom and wipe my device, as soon as it boots up I always enable developer options and USB debugging. Sometimes I feel like a crazy person because I check to make sure that’s all enabled multiple times before I install anything new, just to be safe.

Najmus

Senior Member

GO THE FIX : AT LEST IT WORKED FOR ME.

First of all I was disappointed after reading multiple articles, threads & trying MSM & flash_all.bat method. It wasn’t working for me so I gave up. It happened to me yesterday evening & I kept trying the whole night.

How it crashed? My case has been exactly same as @ms2020, my fingerprint sensor wasn’t working & I thought a restart should fix it & that took me to CrashDump Mode.

Thank you @flash713 after you telling to try different combo with volume +- & power buttons, I started doing it & When I tried | fastboot mode > restart > press & hold volume + button VOILA! It booted up the OS.

Current situation? I had flashed an old OS with MSM and as I write I’m trying to upgrade it to Android 10, Thankfully I have OEM Unlocked now! I can do whatever I want now You know how it feels

I’m still getting CrashDump Mode when I restart, gonna try different ways to fix it now.

Will post the final result.

ms2020

Member

Sorry for late reply.

1 ) When I connect for msm tool (press up + down volume key ) and connect the cable device manger shows
Qualcomm HS-USB QDLoader 9008(COM4)

2 B)ut when I am connected in fastboot mode (press up + down volume key + power )
Kedacom USB Device
->Android bootloader Interface

Also when i am in fastboot mode, msm tool does not identify my device. it shows waiting for device. i have to press key combo as stated in 1 to run msm tool

my device is international model i did not convert or tried to update anything. just one fine day got this qualcom.

sanskar0612

Member

please give the solution if you have

flash713

Senior Member

Just like osmosis said here if msm tool does not work you’re basically out of luck.

Were you able to get the qualcomm drivers installed on your PC and did your computer show what it should in device manager or no?

Seems there are two types (at least) of being in crash dump mode. Sometimes people get stuck in it and other times you can get out of it how I mentioned. Also make sure you are charged on your phone..

sanskar0612

Member

Just like osmosis said here if msm tool does not work you’re basically out of luck.

Were you able to get the qualcomm drivers installed on your PC and did your computer show what it should in device manager or no?

flash713

Senior Member

When your bootlooder is locked and developer options and USB debugging are not enabled in settings on your phone that rules out «other possible methods » of fixing it.

if that weren’t the case. If you had an unlocked bootlooder and those two things enabled in phone settings then you could quite possibly boot twrp via fastboot command and install a rom and see what happens. But those things MUST be done for it to work otherwise it won’t. Msm tool does not work that way. That’s why it’s such a savior and why you plug up with phone powered off and holding the button down while plugging in. Is your model TMobile? If so was your device converted to global model using patched msm tool for 6t or no?

Читайте также: квартира 44 часы работы

sanskar0612

Member

When your bootlooder is locked and developer options and usb debugging are not enabled in settings on your phone that rules out «other possible methods » of fixing it.

If that weren’t the case. If you had an unlocked bootlooder and those two things enabled in phone settings then you could quite possibly boot twrp via fastboot command and install a rom and see what happens. But those things must be done for it to work otherwise it won’t. Msm tool does not work that way. That’s why it’s such a savior and why you plug up with phone powered off and holding the button down while plugging in. Is your model tmobile? If so was your device converted to global model using patched msm tool for 6t or no?

flash713

Senior Member

flash713

Senior Member

Just read that crash dump happens due to a kernel issue on OnePlus 6/6t. Read that on a telegram group.

This must mean that this is one way that crash dump occurs. Because not all crash dumps are the same. If so then how come I’ve been there 7-8 times and always gotten back to a working device by going to fastboot mode manually and rebooting system.

And some people are stuck in crash dump and cannot do anything about it.

Every time I’ve been to crash dump mode I could always do the manual button press to enter fastboot mode and then hot exit that and reboot system by selecting «start » using power button when it’s at the bootloader mode. Except yesterday.

sanskar0612

Member

Just read that crash dump happens due to a kernel issue on OnePlus 6/6t. Read that on a telegram group.

And some people are stuck in crash dump and cannot do anything about it.

Yesterday I had just installed OOS and Pixen 11 and booted system and setup my phone. All was good and my battery was at 55%. Then I booted twrp to flash magisk debug for root and instead of rebooting system like I selected from twrp it went to crash dump and when I tried the usual solution instead of rebooting to system it looped around right back to crash dump again. I booted twrp and installed OOS + Corvus and formatted data and booted fine.

sanskar0612

Member

Just read that crash dump happens due to a kernel issue on OnePlus 6/6t. Read that on a telegram group.

And some people are stuck in crash dump and cannot do anything about it.

flash713

Senior Member

How did you try a rom with a locked bootloader? You have. A 6 or 6t?
If you cannot get msm tool to work unfortunately you’re out of luck unless you take it to a service center and from what I’ve seen on here the cost isn’t worth it. Better to get another device.. There are two threads for this crash dump, this one and another in oneplus 6 forums. I probably got confused and that’s why I commented what I did. Windows is ****. I can’t stand it and don’t use it ever, except when it’s absolutely mandatory because whatever I’m using requires it, which is extremely rare. The only thing you can do at this point unless you have already done it is read the entire thread a few times on msm tool and if you can’t get it to work then sell it as is or take it to a service center. Most of the time, not always but most of the time msm tool will work. Unless you already have,, If I were you in same situation I’d try the patched msm tool, the one for converting from T-Mobile to international model, and I would also try and run the T-Mobile msm tool 40 exe or whatever it is. Not saying you you have but I’ve been on xda since Nexus S days modding my phone’s and tablets and there are times I look over something simple and realize later and go back to it and end up getting it to work. I hope you get it going.

——————————————————————————————-
From here down is not directed at anyone particular just some tips for anyone with a locked bootloader and a 6 or a 6t. From what I’ve read crash dump mode happening is kernel related and there are different reasons why a device goes to crash dump mode.

One of the riskiest moves anyone can ever make is locking their bootloader. I say this because I’ve seen many people ruin their phones that way over the years here on xda. I think maybe many people don’t understand about the whole bootloader unlock, lock.. All it means if a bootloader is unlocked is it’s a sign to whoever has the phone that it’s been altered. Besides that idk of any other security issues having an unlocked bootloader may cause. I keep mine all and always have kept bootloader’s unlocked and dev options and usb debugging checked.

**If anyone reads this and has a locked bootloader and or doesn’t keep dev options and usb debugging enabled I would definitely unlock it and keep it unlocked and make sure you always enable developer options and usb debugging as soon as you install and reboot system. Seeing how this seems to fatally kill people’s devices in some situations where what I say here is not done. Anyone using a 6 or 6t without an unlocked bootloader and dev options and usb debugging not enabled is asking for it. You can always delete lockscreen. Directions on how to delete lockscreen are on the how to root thread in guides section by FunkWizard.

Источник