Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
ampeme12 said:
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
Click to expand...
Click to collapse
Tried wiping cache and dalvik cache in recovery?
Christiaan91 said:
Tried wiping cache and dalvik cache in recovery?
Click to expand...
Click to collapse
Haven't tried that but I will give it a go mate
Related
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
I put my phone at charging last night when it was turned off.
This morning, I saw the screen was on, but black.
I tried pressing some buttons, nothing happened, I pulled out the battery and pulled it in again.
Turned the phone on... the LG logo screen appears, after around 3-4 seconds, it's some kind of blink(0.5-1 seconds) and the LG logo appears again. After another 2-3 seconds, some kind of battery appears that is charging on the screen and then the phone turns off. Tried 2-3 times and same thing. (Note: Phone wasn't charging! The charger was removed)
What to do.....? My ROM is AOKP.
Things I tried:
Charging the phone without battery(reboots again and again)
Pulled out the sd card and pulled in again.
Tried to boot into recovery but no success.
When connecting to PC, the phone is detected, but detection dissapears when phone closes(explained above)
> If you already tried all of those, then recover using kdz updater, flash the stock rom, root back, and flash recovery again.. well.. lets wait for more replies might help you out.
what phone mode should I select?
CS_emergency, diag or Emergency?
My phone screen is right now black(it's turned off but screen is black)
Edit 1: betashot.net/50hZELt.png < open in webbrowser , it's an image.
Edit 2: I managed to boot into recovery mode, cleared cache, dalvik cache and battery stats and now it seems it's working...
> thats goOd to hear now.
Sent from my little fingers.. to your face using XDA app
This is one old problem. Whenever it happens.. just boot into recovery and REBOOT from there!!
This is happening to me and I can boot by getting into recovery, however I need to sell my phone and worried it will be classed as faulty,any idea how to fix properly.
Already tried the delete data etc
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).
Ok, so one night I was using my phone normally (Browsing. Watching YouTube, Playing Games) like everyone else does. Then all of a sudden it shuts off, but immediately turns on again without me pressing a button. (So basically it suddenly auto restarts on its own) This occured maybe 2-4 times (all in one night) until one time, it shuts off but doesn't turn on again (basically an automatic shutdown), so I tried turning it on again (Power button), then I got shocked because all of a sudden it enters a boot loop (Screen displaying this sequence : Samsung Galaxy S4 screen, my carrier logo screen, The encrypted screen (where you have to enter your encryption password) then again the Samsung logo but this time with the colors splashing from the background, then it shuts off again.) Sometimes after the boot loop sequence, it vibrates but never turns on again, sometimes it just turns off after the sequence. And as I try and try to get away from the boot loop, the sequence became shorter. So I'm guessing it's a battery problem, BUT my battery isn't bloated or deformed. I tried clearing the cache first, again the sequence got shorter (never going up to the carrier logo screen), then I tried formatting the data, still to no avail. Now, when I turn it on, It shows the Samsung logo screen for 2 seconds and shuts down.
I tried flashing it with ODIN thru Download mode BUT (HERE'S where another problem occured) :
My phone never get pass on the system.img.ext4 dialogue and my screen just goes blank. But ODIN still recognizes my phone. And when I remove the USB cable, ODIN says FAIL.
I'm sure the cable is working. I downloaded the firmware for my carrier (Tre 3).
What could be the real problem here?
Here is the description of my device :
Samsung Galaxy GT-I9505
Bought from Italy, Tre 3 carrier
Can I download a different region/carrier for my I9505 phone?
Advanced thanks for anyone who comments and I'm very sorry for my English. Thanks!
I would install TWRP recovery, boot to it, and use it to format data, which will remove the encryption. Then I would either push a rom to the phone via recovery or try to reinstall the stock firmware with Odin. Make sure that you run Odin as admin as well. The firmware must be the same version or newer. If you still have the stock recovery and can boot to it, then I think the build number of the currently installed firmware will be visible there. You should be able to use that to Google the correct version you need.
Hey it's me. Just posting a quick reply.
Thanks for replying to my post. Yesterday I successfully flash a rom to my GT-I9505 (Version 5.0.1 Italy HUI 3G). However it still didn't boot up. At first try it booted up to the first setup screen then just randomly shuts down. Then as I try to boot it up again, It just shuts down after the first Samsung logo (with the GT-I9505 logo), I can't boot into recovery cause it shuts down. I'm sure it's not a battery issue cause when I boot into download mode, it can stay in that screen for like 10 minutes. What could be the issue? I'm planning to disassemble my S4 sooner to see if something's wrong inside. Thanks again for the reply
Hello,
maybe someone has suggestions on what to look next or how to determine where the problem actually is.
My Galaxy S3 Tab 10 has suddenly started to freeze after boot + ~1-2min. Even if I wipe everything it freezes even during the initial setup. It is possible to complete the initial setup in minute increments.
When it freezes there is nothing I can do, only Power+vol down for reset. Even to power off I need to press Pwer+vol- then boot it in recovery and then choose power off.
But if it's booted in recovery it can be on for a while and nothing bad happens. That let me think it is more software than a hardware issue.
Have tried to reinstall stock ROM, a few custom ROMs, all the same.
It has not been dropped or "watered" or some other abuse.
Any help?
Thanks!