So i had lineage os 16 until it started to randomly restart multiple times. so i got the newest available Stock rom for the marlin, had some weird trouble flashing it until it finally worked. the phone booted and i set everything up. after a couple of log ins with apps and downloading it just turned off and started boot looping. Now usually you could enter the bootloader but.. it only stays in that for .5 to 4 seconds before restarting. i cant power off because the home button isnt working and i cant flash a clean rom.
Any ideas???
(currently letting my phones battery drain and leaving it for a bit. hopefully that could help but unlikely)
Related
I really don't know what happened, but all of a sudden yesterday my phone started to behave really strangely.
I turned on airplane mode and the little airplane icon never appeared. Turning it off didn't restore the cellular connection so I rebooted the phone, like usual. Since then:
- Reboots take 2x or 4x longer than usual. Sometimes it gets stuck on the boot animation and I have to turn it off.
- Flashing roms/gapps/kernel with TWRP takes forever. At least 4 or 5 times longer than usual. Sometimes TWRP reboots to system without asking.
- Restoring a previous known working TWRP backup took forever, and the phone had multiples FCs on first boot.
- A few times in android the screen just went dark. Pushing the button activates the button lights but nothing else happens without a reboot (which takes forever).
Besides reflashing the rom and restoring a backup I tried to wipe everything and reinstall the rom from scratch, but I still get very slow boots and occasional problems with the "dark screen".
Is there something else I can do? I've had problems with an external microsd before, but the symptoms were very different. Should I try to mess with the internad sd partitions or flash an official samsung rom with odin?
Btw I have a canadian I317m rocking Temaksek v40-41 for the past month without any problems whatsoever.
Hello
Have a GS3 running Rootbox 4.2. Was running stable for probably around 6 months, no issues at all except for the occasional random reboot which seems to plague all S3s.
Felt it vibrate in my pocket, assumed I had a message. But when I looked it was restarting. It gets to the rom loading screen then abruptly restarts.
Now it even doesn't get that far. The samsung screen shows up and the phone restarts in a loop.
Cannot stay booted into recovery. CWM recovery screen shows for about 2-3 secs then phone restarts.
Download mode through odin works, but I'd like to avoid wiping everything if at all possible.
thank you for any help.
an easy try to fix is to pull battery , wait a couple minutes and then either just hold power button till vibrate or do button combo to get to recovery.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Try re-flashing an updated version of CWM via Odin and see if you can remain in recovery mode.
Thanks for the replies
Tried pulling battery for few mins (actually a few days since I did not have time to mess with phone) - No good, phone gets partway through the rom load screen then reboots.
Tried the odin suggestion - home +vol. down+ power opens download mode, but download mode stays open for around 10-15 sec before the phone restarts itself.
I have tried swapping back to the oem battery since i have an extended battery and the problem still remains.
Sounds like a hardware problem to me since you can access download and recovery but it turns itself off. You've tried a couple of batteries so that kind of rules out any software issues.
Did you try booting the phone with a de-brick image from XDA?
I've had an M9 for 2-3. After the first year I got my phone, I installed a custom recovery and rooted it but later uninstalled root and custom recovery. It has been fine ever since except recently. Last month, my phone randomly crashed for the first time and got stuck in the infinite bootloop. It was as if everytime it tries to boot up, it crashed during it. If I hit the power, vol up, and vol down button, I make it to the screen with the option to go into recovery, download, etc. But when I actually try to go into either bootloader, recovery, or download mode from that menu, it crashes and goes back to the white htc logo. I've have gotten the phone to bootup a couple times by leaving it in the freezer as it tries to boot up but after using it for 1-5 minutes, it crashes again. If I don't use the phone at all, then it usually wont crash. After a day or 2, the phone fixed itself. Then one morning, my notifications got stuck together and my screen became unresponsive. So I took my death sentence and restarted my phone and now my phone has been doing the same exact thing for a week. I don't know how to fix this problem because getting it crashes trying to go into recovery and trying to do a factory reset is risky since it could crash during the reset. If also manage to make it into safe mode thinking maybe an application or virus is causing this but the phone crashed in SAFE MODE so I don't know what the problem is. I doubt there is any saving this phone because is probably a hard ware problem but who knows. Any help would be greatly appreciated!! Thank you.
Flash back to stock. Stock firmware fixes all sorts of issues.
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.
Hello!
After recently getting my hands on an old Samsung A50, I thought I might as well reflash and do some stuff with it.
After installing Orangefox and Lineage, everything worked fine until the phone eventually ran out of power.
I plugged it in and let it charge for a bit, but it was just constantly showing the gray circle with a charging/power icon in it, but no battery indicator.
This usually means that the phone is completely empty and has to charge a bit before booting.
After letting it sit for a long while and nothing changing, I got a bit worried.
At this point, unplugging the phone does not change anything - it will continue showing the indicator even while unplugged.
Holding power and volume down (or power + both volume) briefly blacks out the screen, but it simply comes back to the indicator a few seconds later.
All of this happened a few days ago - I eventually got it to boot again through some key combination while the screen blacked out, sending me to orangefox or download mode (i dont remember),
from which I was then able to boot into lineage again. In lineage, everything worked fine again, including the battery indicator which showed that the phone was full, and the battery seemed to work completely fine.
After that, I turned from lineage to Fresh, which also ran fine until Fresh wanted to install an update which sent me to TWRP. Not sure what to do, i just booted back into System which worked fine, but the Fresh update hadn't succeeded.
I attempted to update again and this time shut down from TWRP - big mistake. Now i am once again stuck in the low-power indicator.
I believe that last time i escaped by booting into orangefox - but i think fresh replaced orangefox with twrp?
Anyway, i tried holding different button combinations while the screen is briefly blacked out but nothing is happening (also tried getting into download by plugging into pc, holding power+volumedown, then holding volume up+down while screen is black).
I also let the battery empty itself until it went black by itself and then tried again, but no success.
I'm now again unsure what to do. How do i unbrick this to boot into the OS again? How do i prevent this from happening again?
Thank you all.
Same issue with my Redmi 9, it seems a battery issue idk if i had rekt mine after flashing a latest CN rom then after not being satisfied tried to flash thru recovery to its stock rom and it went bootloop. Fixed it by flashing with SP flashtool and some bypass stuff, but damage has been done with my batt. Maxing out the volume when I try to play something video or music would trigger a reboot to my phone.