[Q] Boot Loop after full discharge - Galaxy S II Q&A, Help & Troubleshooting

Hello.
I have a i9100 smartphone with stock XWLSW firmware. After last change of firmware I did not even root it. So it was all stock without root.
My battery was already in bad condition - from 9 AM till 2-4 PM it gets to 15%.
But anyway.
Yesterday it discharged to 1%, when I plugged charger into the phone. I left it working, and after a while I tried to turn the screen on, but the phone was not responding to power key. It was not turning on the screen, and long hold did not turn the phone on.
I unplugged the charger, took out battery and saw a small wet spot on sticker and on battery (maybe it leaked a bit).
Well, it was not the first priority at the moment, so I just wiped it, and put the battery back, then I turned the phone back ON.
It started, but now I have a boot loop at Samsung Logo. When the battery was still discharged I could hear the discharge signal after logo, and then the logo starts again, and discharge signal again, etc.
I left it in that state for a night with charger plugged in. In the morning - it was in the same condition.
Things I tried:
Removing battery for over 10 minutes, clearing Cache from recovery.
Both recovery and download modes are working.
So the question is - can I restore the phone without Factory reset?
If not - can I somehow backup my data (savegames, etc) before doing factory reset?

I just tried to update the firmware again using ODIN with no luck. It updated successfully, but than again hangs on Samsung Logo.

Rule 1: Don't complain until you haven't tried factory reset.So be a man,and do a full wipe.

^^^^
What he said. Also, flash a 3 part firmware, which will also wipe your phone & has a funny habit of fixing situations like this.

I was going to do a Factory Reset or flash 3 part firmware, but only after I backup data. That was my main point of creating this thread - how to backup data in this situation.
Anyway, I did install Philz kernel, wiped dalvik cache, cache partition - it helped, but not for long. I saw my desktop, but after few seconds it went into boot loop again. I then did a Custom backup of data only, and did a Factory Reset through recovery.
Now I try to restore data to see what it will give me.

So i have been having pretty much the same problem with some little differences.
First my battery seems OK, no leaking no nothing, but it might just got old as I've got the phone for over 2 years now... Second, my bootloop occurs after full discharge, when i try to turn on the phone afterwards it just gets stuck on Galaxy SII logo, not even the boot, and stays that way no matter how long i wait. Third, at about the last 5-8% my screen starts flickering as if it wasn't getting enough electricity which shouldnt happen too and never happend before 4 months or so.
So lastly I've been getting this bootloop every now and then. Ive got a temporary fix by backing up my phone through recovery then wiping it clean and then restoring. But i just cant figure out why it does that.... I mean wipe helps, but i do restore everything afterwards....
Without restoring the problem still occurs so its not like i restore something deffective in the sw that makes this happen...

Related

Bricked?

My phone was running at about 60% battery last night, and working fine. It was in my pocket and it vibrated. I was unable to turn it on or reboot it, even after removing the battery. I tried using the battery from my wife's S2 but still no luck. I tried connecting the power supply but it still wouldn't boot so I left it charging overnight.
This morning it alternately flashed a fully green battery and a fully black battery. If I press and hold the power button it starts the boot process - I get past the Samsung splash screen and see the first "Resurrection Remix" splash screen, but then it reverts to displaying the green battery.
Any ideas for how I can revive the phone??
itm said:
My phone was running at about 60% battery last night, and working fine. It was in my pocket and it vibrated. I was unable to turn it on or reboot it, even after removing the battery. I tried using the battery from my wife's S2 but still no luck. I tried connecting the power supply but it still wouldn't boot so I left it charging overnight.
This morning it alternately flashed a fully green battery and a fully black battery. If I press and hold the power button it starts the boot process - I get past the Samsung splash screen and see the first "Resurrection Remix" splash screen, but then it reverts to displaying the green battery.
Any ideas for how I can revive the phone??
Click to expand...
Click to collapse
Ok We cant say its bricked!! Because its booting up but not coming to homescreen rite? Are u able to get into recovery or download mode?? If ur able o then wipe the data cache and dalvik cache, reinstall the ROM again.. If Recovery doesnt shw up.. Then Use ODIN to flash original fw!! Even if u still couldn get it.. Order a USB JIG from Ebay and try getting into DOWNLOAD MODE!! Even after this its still working means ITS BRICKED !!
Start download mode and the flash a new stock firmware . And your phone isnt bricked .!
This is why I always make a backup.
If you can get into download mode you can fix it, if you can't it's a service centre job. Pretty simple really.
Try cleaning charging port..
Sent from my GT-I9100 using XDA
Uh oh...I managed to get into Recovery mode, did a factory reset and kicked off a re-install of the Resurrection Remix ROM from the external SD and it's hung at 50% (for 10 mins now) - at the "Extracting /system..." stage. I daren't interrupt it.
Any ideas???
Yes stop messing
1: If you dint have to save anything, wipe better to full wipe
Flash a stock Rom using Odin, than start again with custom roms.
OR
2: download your custom Rom again and flash, might be corrupt download.
atifsh said:
Yes stop messing
1: If you dint have to save anything, wipe better to full wipe
Flash a stock Rom using Odin, than start again with custom roms.
OR
2: download your custom Rom again and flash, might be corrupt download.
Click to expand...
Click to collapse
So it's OK to interrupt this ROM flash, even though it's stuck at 50%? Should I just hold the power button or remove the battery??
pull the battery
But I say flash stock Rom first, lengthy procedure I know, but safer
OK I decided to reflash RR 2.3, which had been running fine for a couple of weeks previously. Immediately after flashing (which worked OK) the boot process wouldn't complete - it got as far as the RR splash screen then died (screen blank, and needed a long press on the power button to restart).
This happened several times. Eventually I removed and replaced the battery and it finally booted.
Does this sound like a hardware problem? I've noticed that the phone often runs quite warm, but I don't know if that's normal.
You have to flash stock rom, only way to know if there is something wrong with your phone, run it for couple days.
Now to the heat issue, it is due to
1: modem
2: kernel
3: both

[Q] HTC ONE Stuck On Rom Installation Screen

At first I tried flashing the ElementalX kernel and my screen didn't turn on. So I waited a day and the htc logo finally showed up and I immediately went into recovery. I already had the Renovate Rom before so I tried installing it as I did a while back. I made a noobie mistake by not realizing that my battery life was at 13 percent. So I tried installing the rom. And its stuck where it says "System Unmounted Already" At the bottom it says its at 20 percent and its installing the rom. However, its already been 2 hours since its been at 20 percent. I currently have the htc one charging but I presume that it wont be solved by just charging it considering that the red light isn't on. Please help me find a solution. To make matters worse I only have a mac laptop.
Alexrt890 said:
At first I tried flashing the ElementalX kernel and my screen didn't turn on. So I waited a day and the htc logo finally showed up and I immediately went into recovery. I already had the Renovate Rom before so I tried installing it as I did a while back. I made a noobie mistake by not realizing that my battery life was at 13 percent. So I tried installing the rom. And its stuck where it says "System Unmounted Already" At the bottom it says its at 20 percent and its installing the rom. However, its already been 2 hours since its been at 20 percent. I currently have the htc one charging but I presume that it wont be solved by just charging it considering that the red light isn't on. Please help me find a solution. To make matters worse I only have a mac laptop.
Click to expand...
Click to collapse
Help would highly be appreciated.
Alexrt890 said:
At first I tried flashing the ElementalX kernel and my screen didn't turn on. So I waited a day and the htc logo finally showed up and I immediately went into recovery. I already had the Renovate Rom before so I tried installing it as I did a while back. I made a noobie mistake by not realizing that my battery life was at 13 percent. So I tried installing the rom. And its stuck where it says "System Unmounted Already" At the bottom it says its at 20 percent and its installing the rom. However, its already been 2 hours since its been at 20 percent. I currently have the htc one charging but I presume that it wont be solved by just charging it considering that the red light isn't on. Please help me find a solution. To make matters worse I only have a mac laptop.
Click to expand...
Click to collapse
I had a flash go bad and get stuck on mine, I just rebooted it into Recovery (power & vol down), did a full wipe, including cache & dalvik cache, and ran the flash again, it worked. Are you not able to get back into recovery?
trjlive said:
I had a flash go bad and get stuck on mine, I just rebooted it into Recovery (power & vol down), did a full wipe, including cache & dalvik cache, and ran the flash again, it worked. Are you not able to get back into recovery?
Click to expand...
Click to collapse
I fixed it. At first I wasn't able to get back into recovery since the phone was turned off and didn't turn on. However, I let the phone stay still for about a day and let the battery die. I than charged it and put it back into recovery as soon as I saw the htc logo.

[Q] 5.0, Mostly Boot Loop with Battery Icon

Device: Galaxy Player 5.0 INTL (YP-G70)
ROM: Cyanogenmod 10.1 (7/23/2013)
Kernel: Sultan r5 INTL
Problem: The battery appears to be malfunctioning somehow. After using "Pimp My Rom" and enabling some tweaks, the device began to randomly turn off and loop on and off with a white battery outline onscreen. Now, the battery has sufficient charge. When it finally turns on, it's always over seventy percent. When it does turn on, if it is plugged in on the wall charger, it immediately turns off upon disconnecting this wall charger. Also, it displays "Android is upgrading, starting apps" at every boot. Managing to turn on the device after doing a reboot with the power button many times takes up to 15 minutes. It sucks. ):
Steps attempted:
Reflashing ROM and kernel using exact steps (wiping all data, /system, cache, etc.).
Flashing Cyanogenmod 10.2 (8/05/2013) with Sultan r6.
Deleting battery stats.
Cleaning charger and microUSB port.
Rechanging tweaks to the values I remember in Pimp My Rom. (IDK about all of them, if someone could post the defaults that would be great).
Draining battery (I did to 1%) and then recharging. Should I drain until it turns off?
[EDIT]: Tried flashing to Chip v1.5 with r14 kernel. No luck; it is just a different battery icon.
[EDIT]: Tried flashing to stock with Odin.
Are there any steps that I could possibly take to fix this? Perhaps flash to stock and see if the problem persists?
[WORKAROUND!] I've found a workaround, however annoying it may be. Plug in the YP-G70 and it should bootloop with the battery icon. However, as the icon disappears and the screen is black for about a second, just before it is about to reboot with the icon, pull the charger from the device. This has guaranteed my device to start every time; I can't ensure that it will work for you, but it is worth a try.
Please help!
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Click to expand...
Click to collapse
I have done many factory resets from CWM. Would flashing back to stock do anything that flashing another rom wouldn't?
Also, after scouring xda for answers, I saw iurnait recommended draining the battery until the device turns off. I'm going to try that I suppose.
I'd flash back to stock if that doesn't work
Sent from my YP-G1 using xda app-developers app
Unfortunately, flashing to stock using Odin didn't remove the problem.
I used a guide from androidromupdate
To be honest, I've given up. I'll update the original post with what I've tried and the workaround that I've found for this dreadful issue. If anyone else has this issue, best of luck!
I've got the same "boot loop with battery logo" problem, but without the random shutdowns are "android is upgrading" message on boot.
Some additional details:
I can boot into download mode without any trouble.
It will occasionally complete a boot, but gets stuck in the loop as soon as something causes it to reboot or shutdown.
I can sometimes boot into recovery mode. It will successfully go into recovery mode about 2-3 times before it will go into a normal boot.
Flashing alternate kernels (even going all the way back to stock) just changes the battery logo, but does not stop the bootlooping problem
The stock kernel was far more reliable than the others, often booting all the way after only 3 or 4 tries.
Throughout the boot loop, the battery logo (except in the stock kernel) will show as empty, even after being charged overnight
Upon a successful boot (all the way to android home screen), the battery is shown as fully charged (if it's been charging) or a level that seems probable (e.g. it'll show as 70-80% if it's been in download mode (which keeps screen on at full brightness) for a while or left to bootloop for close to an hour.
If it's not plugged into a charger, it only loops once each time you turn it on (i.e. battery logo shows for a few seconds then the device shuts itself off).
An update to Joseph's posted workaround:
I've found the button lights a perfect indicator for the timing. Wait for them to go black and then come back on very dimly then unplug the cable before the screen shows anything or the key lights go full brightness (like they are when device is fully booted and awake).

I think I bricked my phone :(

First, some background. I've been happily using NeatROM 4.9.1. A few nights ago, my phone started beeping a lot. It kept thinking the charger was attached, though it wasn't. Somehow, after a number of restarts, battery removals, and plugging/unplugging the charger, it started working normally. Then today it started beeping again for the phantom charger. I decided the phone needed to go to Samsung to see if there is a hardware issue. So, I used Odin and restored the factory 4.1.2. Well, since doing that, the phone gets stuck on the Samsung splash screen. I was able to boot into recovery, so I re-rooted the phone with Philz kernel, cleared the dalvik cache and regular cache. But it wouldn't reboot out of recovery. So, i reflashed 4.1.2, via Odin and it's still stuck.
update: i did a factory/data reset and the phone is booting normally, but I think I might still have a short or a micro-usb connector issue.
Could be charger
Could be usb
Could be battery.
Sam will find the fault

[Q] Recovering contacts from a soft bricked S2

Basic info: phone is not rooted, the only messing I have done with it was to flash an updated official firmware via Odin (2 years ago) and after that even Kies recognised the firmware as the one I should have.
Yesterday I had a freeze at ~44% battery, did a reset and the phone booted with 0% battery. It switched off, so I took the battery out, put it back in and swtiched it on again. It showed 10% battery, but before completely booting up it froze again. From this point on every time I switch it on it gets to the pulsing 'SAMSUNG' screen at startup and stays there forever.
I am buying a new battery tomorrow. I have researched some ways I can recover the phone, but I am not sure if they will wipe the data. In particular, I would very much like to save my contacts. Is there a way to do this? For example, I read that to flash CWM recovery with Odin I need to unlock bootloader, which will wipe my data. Would one of the various data recovery softwares work in this case (Yodot, Dr.Fone)? Can I get an update to the firmware to my SD card and apply it from the stock recovery, possibly not wiping the phone and recovering the OS?
Also, FYI, I can get to recovery mode, to download mode, but not to safe mode.

Categories

Resources