Hello.
Using BlissROM since many months ago.
Just recently, perhaps a month ago, I've had this recurring issue of getting into the Qualcomm Crashdump Mode upon restart.
The ROM would be working fine (for BlissROM at least) and by simply restarting the phone, 60 or 70 per cent of the time it would go to the crashdump mode.
I would have to press Vol Up + Power to make it boot into the ROM.
Today though, that would not work, neither trying to go into TWRP. Pressing Vol Down + Power when the phone was restarting would get me to the TWRP splashscreen for less than a second and then the Crashdump mode.
I've used the MSM tool so I can recover from it, but what I would like to know is why this is happening. Why I cannot restart the phone without issues anymore.
Can anyone assist me?.
Thank you!
Happened with me too on CrDroid 6.10,
SirRhor said:
Hello.
Using BlissROM since many months ago.
Just recently, perhaps a month ago, I've had this recurring issue of getting into the Qualcomm Crashdump Mode upon restart.
The ROM would be working fine (for BlissROM at least) and by simply restarting the phone, 60 or 70 per cent of the time it would go to the crashdump mode.
I would have to press Vol Up + Power to make it boot into the ROM.
Today though, that would not work, neither trying to go into TWRP. Pressing Vol Down + Power when the phone was restarting would get me to the TWRP splashscreen for less than a second and then the Crashdump mode.
I've used the MSM tool so I can recover from it, but what I would like to know is why this is happening. Why I cannot restart the phone without issues anymore.
Can anyone assist me?.
Thank you!
Click to expand...
Click to collapse
I had that issue once I flashed a rom to only one partition, apparently, you need to flash roms twice so it is on both partitions. I would reboot to TWRP and flash the rom, then twrp, reboot to recovery, flash the rom again, flash twrp, wipe data, reboot system, complete setup, go back to twrp and flash magisk. That works for me. I am issing the latest 3.4 twrp, it seems to automatically flash the rom to the inactive partion, so if you boot on a it flashes on b and viceversa. It seems that every time you reboot, the system boot in the next partition, that's why you have the issue with the qualcomm crash half the times.
Related
Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989
Did you try clearing the cache and doing a factory reset ?
SpectreFang said:
Did you try clearing the cache and doing a factory reset ?
Click to expand...
Click to collapse
That's impossible for me to do since I can't get to launcher or recovery.
No acess to recovery?? Then better take it to service center... Atleast can u boot to fastboot mode or adb accesible then use oneplus one toolkits
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Install oneplus tool kit, while optimising apps it gets dectected by pc, just make it reboot mode & do reset.... Dnt worry this can be fixed, if all these seems messy then take it to service center
danq989 said:
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989
Click to expand...
Click to collapse
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?
Bradl79 said:
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?
Click to expand...
Click to collapse
Yes, just tried it. Same thing as described in my original post. When I hold power+volup the screen goes blank. I switch to power+voldown until the 1+ logo. At that point:
1. If I continue to hold the power+voldown key through the 1+ logo, the screen goes blank briefly, the phone vibrates once and reboots. If I continue to hold the power+voldown key, the vibrate&reboot cycle continues indefinitely
2. If I let go of either the power button, the voldown button, or both at or before the 1+ logo, the phone boots normally and goes to "Android is starting... Optimizing app n of 119). When the optimization finishes, the phone instantly reboots.
It's like the phone recovery is gone or inaccessible. Could this have to do with the phone tampering setting? As I said, I had this phone rooted and bootloader unlocked, working fine with CM12 for some time before trying an in-place upgrade to 12.1. That's when things went south.
---danq989
Hey everyone, I hope this is the right place to ask for help. Something very weird happened yesterday. After removing my 2-year old Y2 from charging, I started using it normally. After a few minutes, it lagged somewhat and then stopped responding. Without thinking much, I pressed and held the power button to restart it like I have done many times before. But this time, it got stuck on the Mi logo. It kept getting stuck on the Mi logo (after switching off for about a second) no matter how many times I held the power button to restart again. I left it on the logo overnight and it stayed that way.
What I have tried yet:
1. As I said, I tried to restart it multiple times by holding the power button to no positive effect.
2. I tried to boot it up into recovery mode by holding Volume up and power button. That restarts the phone back to the Mi logo and it is stuck again. The "Main Menu" (which I think is the recovery mode) with options like Reboot, Wipe data, etc doesn't appear.
3. I tried to boot it into fastboot mode by holding Volume down and power button. It boots up to the fastboot logo so I guess it is working.
4. I followed the steps in this video. The phone stays in fastboot and nothing happens.
5. I let the phone discharge completely once, and tried charging and booting again. This also did not make any difference.
I could not find any information about something like this anywhere. Since it happened on its own, maybe it is a hardware problem? I did not install anything new in the past few days, not even a new app. Maybe it has got something to do with the battery or some other part?
I'd really appreciate any type of help in how to fix this, in particular the following issues:
1. Is there any way to know if it is a software or hardware problem without complicated tampering with the hardware?
2. Can I do anything to recover the data? I'd be really upset if I lost it all.
3. What all steps can I take to fix it if it is a software problem, preferably without losing the data?
4. If it is likely a hardware problem or a difficult to solve software problem, how I can I encrypt (or even wipe) the data before giving it to someone for repairs? (since I'm not able to boot into recovery mode)
Some extra information if you need it: my phone is not rooted, bootloader is locked, OS is Miui 11 (Miui 12 is also available for it but I haven't installed it yet. Maybe there's a way to install it externally which would boot up my phone?)
Thank you for your help! I'd really appreciate it
Same problem with me please suggest some best sort of solution
pcjha said:
Same problem with me please suggest some best sort of solution
Click to expand...
Click to collapse
Hi, I recommend you first of all back up your data if still possible.
Then, reboot into fastboot.
-fastboot erase system
-fastboot erase cache
- fastboot erase userdata
-fastboot erase recovery.
Then clean flash a rom.
I ran a TWRP backup today, and when I rebooted after finishing the backup, my phone got stuck in "Downloading, do not turn off target". I restarted a few times with vol down + home + power, and it went back to the same screen each time.
I figured something must have happened to the recovery, so I fired up Odin and reflashed TWRP onto the phone (without first checking that I really needed to do that). In TWRP, I restored the backup I just made, but to no avail. I had to go back to the previous backup a week ago before my phone would boot up and operate normally.
What was most likely the problem? I'd really like to avoid this happening again!
Apparently this is the problem:
Feenix0 said:
I restarted a few times with vol down + home + power, and it went back to the same screen each time.
Click to expand...
Click to collapse
The combination key you was pressing was the bootloader's combination, so obviously you'll reboot back to the download mode in a loop until you break the loop.
You probably, mistakenly rebooted to download mode from TWRP, of which you might not be remembering well.
There was no need to restore the old backup, all you had to do was reboot to system.
And yes, the right combination to get out of download mode is: VOLUME DOWN + POWER.
Ok thanks!
So I have Galaxy S7 (Flat). It had installed TWRP with Magisk on stock Android. I decided to install LineageOS (https://forum.xda-developers.com/t/rom-q-s-lineageos-with-microg-for-samsung-s7-flat-edge.3921094/) (clean install using TWRP) and it installed successfully, everything was fine, I've turned my phone off and on few times and system was booting without any problems.
But then I decided to boot into TWRP (using key combination) to install magisk and... it's stuck on loading screen forever.
I can't even turn it off ! And my phone is getting hotter and hotter. Please help !
I can't turn it off, because simply holding power button doesn't do anything.
I can restart it by holding power + volume down ,but it just opens TWRP again.
I've read I could boot into Maintenance Boot Mode ,but it requires to turn off a phone, which I'm unable to do.
Only thing I am able to do is to boot into Download Mode, but it doesn't change anything (still cant turn off phone in this mode)
Should I try to disassembly the phone and take out the battery manually? I don't really see any other option.
Did I bricked my phone ?
@edit
I have backup of stock system made by TWRP, but it doesn't change anything as I cant use TWRP.
I didn't install LineageOS custom recovery.
Ok, so I left phone overnight to deplete the battery. And it didn't work ! I thought that battery is dead and phone is off, but the moment I've plugged the power cord it automatically turned on into TWRP screen, like a zombie !
However I've solved the problem. As I was able to get phone into Download Mode (by holding power+volume down+home) I used Odin. I've installed newest Odin on PC, Samsung USB drivers and flashed the newest TWRP tar. Although it was scary, I was almost sure I've bricked my phone. Adb/fastboot were not detecting the phone.
And after re-flashing TWRP everything works fine. Also LineageOS booted like a charm, it stay intact.
So, it seems that installing LineageOS somehow corrupted my TWRP, despite that I un-ticked the option to install LineageRecovery ,so technically it shouldn't mess with it at all.
Anyway, problem solved.
Hi, I don't know what is happening, but I've been having issues with my phone. I was trying to enter recovery and pressed the button combination for fastboot instead. After that, I tried to get out of fastboot, but it kept going back to fastboot. I noticed holding up for a couple of seconds would boot me into my OS. When I try to enter recovery, the screen goes black and it restarts the phone. It will just keep going in a loop if I hold the buttons. My phone was rooted with magisk and I uninstalled to see if that would help, but it didn't.
I installed an update(I use lineage OS) out of curiosity to see if it would boot to recovery. It booted to fastboot, but after restarting and holding the recovery button combo it booted to twrp and installed the update, then restarted. Now my stupid mistake made my phone unusable. Everything is the same, except Lineage is stuck at the boot screen now. Sometimes it restarts to fastboot, but other times it stays there for possibly infinity.
I don't know what to do. All help is appreciated?
TL;DR Fixed, I think my volume down button was stuck.
Nevermind, I flashed with miflash and still had the problem, then for some reason it worked, but only once. I removed my phone from the case and found that it was booting to os. It is still kind of hard to enter the recovery. I think hitting volume up was cancelling the volume down which was stuck, or something. Now I'm pissed cause I wasted so much time on nothing