My phone has been operating perfectly fine up until a video meeting I had today, where the phone went from 100% to 0% by the end. This Axon 7 has had a lot of wear and tear on the battery so that is normal. Today the phone was very very hot during shutdown.
Upon trying to reboot, I am stuck in a bootloop. I have Lineage installed, and tried Stock but that wouldnt even get to the booting animation. I uninstalled Magisk before these tests. Now I am back on Magisk, in LineageOS (latest build) and managed to get back to the booting animation.
Does anyone know any kind of damage that could occur with a hot phone during normal operation (not boot or shutdown) shutting down? A bootloop seems like a strange result.
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
otaconremo said:
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
Click to expand...
Click to collapse
This was the solution, however, along with something else.
The phone only charged correctly in TWRP, so I advise that. Definitely uninstall magisk so it doesnt patch other installs (I've noticed its installer gets called every time I flash a rom). I still had bootloop so I assume all my hard-resetting didnt help. I got it to fully boot on Bliss, but since I kinda miss Lineage I may return to it later today. (I love my "0% brightness" and blue light filter among other lineage features).
Related
Hey Guys,
My phone gets stuck in a bootloop if I don't use a charger while turning it on. Actually, doesn't even get past the splash screen and reboots every 1 to 2 seconds. I also need to connect it to the charger to access TWRP. Normally, when I disconnect the charger after the phone has turned on, the phone suddenly turns off. But when I do the same when I'm in TWRP, nothing happens and I can continue using it without any problems. I'll put the logs if you neeed. And yes, I don't need the charger to get into fastboot mode. I'm currently on lineage 15.1 unofficial but the problem persists over other roms too. Please help...
Change the battery
It's the battery , which is under performing with the voltage needed to run the rom process,
That's why you are able to use with charger and got bootloop without charger. In twrp or any recovery mode most of the hardware is disabled and does not need much power.
Telling you with personal experiences
jakir69 said:
It's the battery , which is under performing with the voltage needed to run the rom process,
That's why you are able to use with charger and got bootloop without charger. In twrp or any recovery mode most of the hardware is disabled and does not need much power.
Telling you with personal experiences
Click to expand...
Click to collapse
Thanks!! It worked.. I got my battery replaced and not my phone is as good as new ?
Hello,
I'm currently experiencing a bootloop on my phone, it gets to the resurrection remix logo screen during boot then restarts. I've tried booting into recovery and download mode. When I try to boot into recovery it loads the factory reset screen as usual but when I say yes to the reset in order to launch TWRP it just goes to the LG logo, then remix and restarts all over. I got into download mode one time since this started but since then I've made countless attempts to boot into it again and can't.
What I was doing right before this happened is, I recently completely wiped my phone, flashed stock firmware, wiped, then installed resurrection remix. Everything was going perfect, it started no problem, I went through and cleaned up some apps I didn't want etc normal setup steps then I used the power menu to boot into recovery instead of just using the hardware keys and the bootloop started.
Besides the not booting, the other major issue here is that it never stays connected to the pc via adb long enough to do any actions or flash a single file. By the time the pc sees it and adb sees it, I have roughly 2 seconds before it restarts again.
I really really really need any help I can get please ASAP as this is my mom's phone and she needs it for work in 4 hours. This issue started about four hours ago and I've been trying to fix it ever since. I feel like I have looked everywhere on here and through google but probably missed the solution. Before you ask, I'm 28 not a teenager and work in IT as a career for the last 12 years so don't get the wrong impression. She asked me to work on it because I had set it up a few months back with a lollipop version of resurrection remix and magisk, but in the last month or so she was having really poor performance and issues with settings crashing and a few other apps.
I hope you don't need any more info from me, if you do however I'll be here trying to fix it until she goes to work at least. I really could use the help and would greatly appreciate it.
Thank You
hey guys. have my redmi note 7 here with me
i successfuly installed the LOS 17 rom on it, through OrFox (after unsucessfully trying with with the unofficial TWRP, not following the developers advice!), but it had some bugs and i decided to try his previous LOS 16 rom
after wiping system, data, cache and dalvik partition i tried flashing the rom zip file - i got back and error and it didn't flash. i rebooted to recovery to retry flashing but got the same error
as has happened to me before in other devices, i suspected the file could be corrupted, since i had a very slow connection that day and paused the download 2 times, and also decided to download the correct firmware just to be sure, in order to flash the two
since i was waiting a lot for the download to finish, i left the phone overnight without a rom installed. i think i left it turned on recovery and so next day, when i pick it up it had no battery
i tried to boot it and got a "no battery" sign right after the splash screen. so i plugged it into the adapter.
as soon as it got plugged, the phone screen turn on with the splash screen and right after a "no battery" sign again. (i think think is normal and then you usually get the "charging battery" animation, after some seconds?)
but the then it just rebooted: splash screen again and the "no battery" sign once more. and then again...so it seems to be stuck on a charging bootloop, always showing the "no battery" sign and getting no charge at all, no matter how much time it stays plugged in
i tried connecting it with a different charger and another cable and get the same result..even tried with a charger with no fast charge (i read it would be a solution to some other device) but still the same bootloop
i can boot it into fastboot but it reboots quickly also (with the "no battery" sign right after)
so i can't get back into recovery or whatever since the phone gets no charge at all.
does anyone know a solution for this? thank you
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
spencetj said:
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
Click to expand...
Click to collapse
Never mind, I got it working with a different charger. Very strange. The first charger works fine with my Huawei P20, maybe too high power for the S5? Although I thought the device only draws the power it needs even if the charger is capable of more.
Even before I had issues it would stay relatively warm when just charging it at 5W (it still does that when it's turned off) so I started suspecting liquid damage (prior experience) or the battery starting to show its age even though it's only been charged about 300 times. This all started after I flashed LOS on it where hwc was disabled. The phone had pretty much stayed unused until late 2021 and was meant as a dev/backup phone.
After a second hard crash it stopped trying to boot and will now only enter Download mode and nothing else. Prior to this I only had to reflash it, but this time it's not looking so good.
I'm too facing the same, tryin to revive my cousin's s8, which is not even rooted once. Tried flashing stock fw using odin. It just doesn't show samsung logo but still goes to download mode. Any help devs?