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.
Related
Hello everyone
Yesterday I tried to reboot my phone because it froze.
After the phone turned down and tried to boot up the only thing it did was showing a green led light (as when the phone is fully charged) and vibrate for 5 times.
As I toughed it was bricked I peeled the battery out and went to sleep.
This morning I putted the battery back in my phone and it booted, but only in safemode.
I noticed that my volume down button only worked in the bootloader and not in recovery or in a safe-booted Android.
I tried serval things like putting the battery out, heating my phone, even got the volume keys out and than booted it but nothing worked.
Then I tried flashing a new Rom but it booted in safe mode right after flashing.
Also factory reset in the bootloader doesnt change a thing.
Can someone help me please?
Thanks in advance!
A few weeks ago, my Tab Pro 8.4 started bootlooping. I did a few cache/dalvik wipes and got it going again. I think I reflashed the ROM and GApps also.
Now It is doing something odd. If I leave it plugged in overnight, it powers off. It takes a very long (20 second) power button hold to get it to wake. That woke it in the past, but today is something new. Now it is going into a bootloop. During the boot animation, it stutters, freezes, then goes back to the bootloader splash page (the one with the "seandroid enforcing" and "warranty bit" message on top).
It has no issue going into TWRP and I have just done a full backup. I am going to go back into TWRP and make a copy of internal. I have a few files in there that I don't want to lose.
Could this be a ROM issue? (I will update ROM info after next time I am in the device/TWRP) Hardware? I just installed a new battery, but this issue started with the old battery. Any ideas on how to get this revived?
Hello there everyone! Let me explain my problem:
Backstory
I have a Samsung Galaxy Nexus GT-i9250 maguro since 7-6 years or so. I've been flashing some roms into it and everything went well since a week ago.
I had installed from a very long time this version of CM "cm-13.0-20160921-NIGHTLY-maguro" and I have not updated it, so I basically was running that from a very long time.
Three weeks ago the phone started behaving strangely, it was closing automatically, and I thought that it was a temperature problem (being a very hot summer) so I did not worry too much.
Everything was working fine, charging and connecting via USB .
Problem
Last week the phone once again died and I tried to boot it up normally as I would normally do, but nothing happened, not even the Google logo popped up.
So I removed the battery and put it back in, the phone booted up to the Google logo, then after two or three seconds the Google logo flashed like brightness went up to 100% and black screen.
Went into fastboot, booted TWRP to see if that was working, and the recovery was working fine.
Things got worse.
At the moment
I cannot get the phone to do anything if it's not connected to a power source.
If the phone is connected via USB, or charger, I can get it to go ONLY on fastboot, and download mode. If I unplug the phone while on fastboot or download mode, the screen brightness goes up to 100% for half a second then it glitches out and goes into black screen immediatelly. I can not access bootloader nor recovery mode from fastboot, because the phone reboots, shows the Google logo and then it dies.
What I tried
Thinking that maybe the ROM went crazy, I followed this guide to flash the phone with all the original ROM and recovery (I downloaded "yakju-jwr66y-factory-4cadea65" and followed the instructions of the guide).
Nothing changed, if the phone is not connected to a power source, it is basically dead, if I put it to a power source it shows the charging logo for a second, then black screen, and I can only boot up fastboot and download mode.
I don't know if this might help but I've also tested the battery voltage and it seems to be fine.
Last thing, if I connect the phone to the PC (with the battery or without) every 2 seconds it shows up that an unidentified device is being detected.
I currently am using a laptop running windows 8.
On my desktop computer the same thing happens (the device detection) but from device manager I see a OMAP4400 (something like that) popping up but at the moment I cannot use my desktop PC since I'm traveling.
I would really like to know what happened to my phone, any answer will be appreciated.
Thanks in advance!
Update [solved]
After doing some research and trying different methods I gave up. But then I realized that maybe trying the stupidest thing could be the solution, so I went to a phone shop and asked them if they had some sort of test battery that I could plug in my phone temporarily to see if it was booting up.
Turns out, it was the battery.
I bought a new battery and now the phone runs smoothly like it's new.
I feel so dumb and I'm so sorry if I've made some of you people waste your time by reading the poem of the first post.
Hopefully this will someday help someone that will have the same problem of my GT-I9250!
(This thread can be closed now)
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Norkzlam said:
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Click to expand...
Click to collapse
Well it sounds like the infamous Bootloop at least the symptoms are the same. The Bootloop issue is not caused by dropping the phone but while booting Android as this is a very CPU intensive process.
Ilapo or not I would take a backup with SALT before anything else.
You can also boot to fastboot and assuming you haven't installed the nougat v29 bootloader stack you can just boot TWRP temporary by using
fastboot boot twrp.img
(where twrp.img should be my latest TWRP version preview 144 or higher)
Sent from my LG-H815 using XDA Labs
No Bootloop. It seems like the power Button is broken. Using SALT I could reboot the phone and it starts and works normal. The knok-on feature makes this situation, at least temporally, bearable.
I will probably try to fix the Button.
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.