Hello,
I recently installed Lineage OS 16.0 (from the official website and latest version to this day for my exact model) on my SM-A520F/DS (whatever the one in Australia). I use TWRP 3.3.1-1 -a5y17lte and flashed no-verity-opt-encrypt, open gapps STOCK and addonsu but later removed with the addonsu-remove zip.
The problem: ONLY when I restart my phone, the boot animation goes on for a very long time (probably forever). The circle just keeps going from one end to the other on a line and shrinks. Then repeats. You know, how boot animations normally go. However, if I shut down my phone and then power it on with the power button, it boots up in seconds and works perfectly fine. When the boot animation gets stuck, I have to force restart the phone (volume up + power) and then it boots up fine in seconds.
Please tell me what is going on and if there is a possible fix for this very annoying problem.
Thanks
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
I recently updated Magisk from 16.0 to 17.1. The installer asked to reboot after finishing up. After rebooting, however, the phone gets stuck on boot animation. I've tried to let it run all night and I've tried charging/discharging a few times. The bootloader is still unlocked (the opened lock icon shows up under the Google logo on boot). I can't get into recovery/fastboot mode: Holding power+volume down turns on the phone but gives a black screen with backlight on. My computers also don't recognize the phone. I haven't found any similar issues here while searching so I am at a loss on how to fix it.
Possibly related: Charging the phone has been weird for a few months: the charging LED indicator only turns on when the phone screen was on. It seemed to charge slower compared to previously and the OS doesn't recognize that the phone is charging.
With the phone off, hold the volume down button and connect the phone to your computer. This may force the phone into fastboot mode.
Thanks for the advice! Although that didn't immediately work (it still booted to a black screen w/ backlight on), I tried one or two more times to boot holding down volume down + power with the phone unplugged. I got lucky somehow and it finally booted to Fastboot. From there, still neither my MacBook nor my Windows computer recognized my phone (nothing in device manager). I booted to TWRP, and saw that Magisk had .zip's of previous versions stored in /sdcard/MagiskManager. I flashed the last working version, 16.0, wiped Cache and Dalvik, rebooted and finally got through boot animation.
Time to backup!
Edit: Resolved
I flashed a nightly release of LineageOS and it's working like before!
Software
TWRP 3.1
LineageOS 14.1
Magisk 18.1
Magisk Manager 7.0
Rooted (unsure)
Background
Google Pay recently declined contactless, so I tried re-enabling it with Magisk and changing device fingerprint, to no avail. I rebooted into recovery to install Magisk Canary, by running the magisk-uninstaller.zip. As soon as I swiped right to run it, it rebooted into the turquoise "Downloading... do not turn off target" screen (with no text in the corner). Every attempt to boot into system yielded this.
Troubleshooting Attempts
Holding volume down + power, reboots to Samsung S7 screen then quickly back to the same "Downloading..." screen
Holding volume down + power, then as soon as screen flashes black quickly holding volume up + power goes into TWRP
Cleared cache in TWRP and tried rebooting, same results
Other Information
I can still enter TWRP and see my files via USB on my computer
Even after phone is powered off and I recharge it, the screen goes back to the turquoise "Downloading..." screen. Powering on is the same..
Questions
Does anyone have suggestions as to what I can try next? Or should I create a backup while I can, then reinstall TWRP or another ROM?
Thanks!
therollingthunder said:
Software
TWRP
LineageOS
Rooted (unsure)
Background
Google Pay recently declined contactless, so I tried re-enabling it with Magisk and changing device fingerprint, to no avail. I rebooted into recovery to install Magisk Canary, by running the magisk-uninstaller.zip. As soon as I swiped right to run it, it rebooted into the turquoise "Downloading... do not turn off target" screen (with no text in the corner). Every attempt to boot into system yielded this.
Troubleshooting Attempts
Holding volume down + power, reboots to Samsung S7 screen then quickly back to the same "Downloading..." screen
Holding volume down + power, then as soon as screen flashes black quickly holding volume up + power goes into TWRP
Cleared cache in TWRP and tried rebooting, same results
Other Information
I can still enter TWRP and see my files via USB on my computer
Even after phone is powered off and I recharge it, the screen goes back to the turquoise "Downloading..." screen. Powering on is the same..
Questions
Does anyone have suggestions as to what I can try next? Or should I create a backup while I can, then reinstall TWRP or another ROM?
Thanks!
Click to expand...
Click to collapse
If the rom zip is on your sd card and you can boot into TWRP, you can flash the rom again, do not wipe anything! and all your apps files etc should be still there when the phone reboots. It's the same process as updating lineage over the existing build.
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.
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.