When I turn off the phone, it vibrates to let me know it is off, and then it waits two seconds or so then turns itself back on.
I have done hard reset after hard reset, put the latest KE8 on and it still does it. Could it be a battery fault?
Do you have Advanced Power Menu installed?
Nope. It is now not letting me switch it on unless plugged into the charger.
If I switch it on away from the charger, it shows me a battery on the screen with a flickering yellow warning triangle with a thermometer next to it.
Any thoughts?
sorry to hear that!
i've had this problem about one or two months ago, after i flashed a new rom (can'r remember which one, was it lightning?). did almost everything i could
imagine (flashed other recovery, kernel, modem) and nothing helped. also a
complete fresh install (wipe everything before) didn't solve this!
the only thing which worked for me was to go back to my old rom. after that
everything was fine again!
so, i cannot say what causes this, but if you flash another rom it should work again! if not, try to repartition with odin, using one of the provided PIT files!
yep also had this problem when i first flashed cognition. my phone would reboot after turning it off. and if the battery went dead, when i plugged it into charge it would turn itself on instead of going to the battery charging screen. all i did was reflash the rom and all was fine.
This morning I updated to Android 2.3.4.
If I root like this:
http://androidflip.com/root-samsung-galaxy-s2-android-234-xxkg1-firmware/
Will it help do you think?
Just to update, it seems to be resolved now using this:
http://www.theandroidsoul.com/root-xxkg1-android-2-3-4-firmware-rom-on-galaxy-s2/
Thanks for your help guys!
And now its doing it again lol
I can live with it, but a couple of things like it thinking there is a USB cable connected seem to happen every now and again...?
hmm thats the same way as i did it but i didnt do the yellow triangle trick so im not sure about that. everything else is standard, thats how i flashed my rom and i only had your problem the first time i flashed. did you do the yellow triangle removal?
I did the remove triangle thing yea.
I do think it is a problem with the USB connector, it could be touching itself inside, possibly causing a shortage as it occasionally thinks a USB cable is connected.
So, if I turn off, it could be thinking that the charger has initiated connection and starts up to charge, but can't charge so just continues to boot.
I have plugged the usb cable in and with nothing at the other end, and nothing pops up. So it could be something like what I suggest. It has been ok for an hour or so now so fingers crossed lol!
lol that cud be it then. it wud make sence. might wanna get that looked at tho if you dont wanna risk damaging the phone. if its doing what you said, then it cud end up killing the phone if it shorts it out permantly. let me know how its going in a day or so.
Even on lock screen if you press and hold the power button for 8 seconds the phone does shut off, is it happening for ya?
I had this a few weeks back. Reflashing cf root kernel fixed mine.
minty1978 said:
I had this a few weeks back. Reflashing cf root kernel fixed mine.
Click to expand...
Click to collapse
Likewise, solved my problems with the phone rebooting itself instead of turning off.
Related
I have a 8125 and I was able to unlock it fine. After unlocking it I upgraded to the underground crossbow edition rom - which the 8125 rebooted and was running. I tried out a couple things and everything seemed to be running/working fine. It was getting late so I put it down and went to bed. This morning when I got up the phone was off so I went to turn it on and nothing happened. I figured it just ran out of battery power plugged in the charger and guess what no red light on. I have tried everything under the sun but I cant get it to charge or startup. Anyone have any ideas? It was working fine.
i know u said u've tried everything and i don't mean to sound like i'm takin the buscuit, but leave it on charge for n hour, then try bootloader. taking the battery out completely for a while could work.
i had so many problems with crossbow! think this was one of them.
Unplugged
Well so far I left the charger plugged into the phone with the battery in it for over an hour now - with no luck. The red charging light doesn't even come on. Did you have that problem? I also left the battery out and plugged in - still nothing. Tried taking the battery out and then putting it back in while plugged in - no go.
I have not tried the "bootloader" - but the phone will not turn on at all or respond in anyway. Its in a powered down state (or so it seems) - I dont think bootloader will work?? But I dont know anything about bootloader - is it on the ftp site and how do I use it?
Any chance the battery could have been completely discharged?..just a thought. I think i read that completely flat batteries wont charge up via usb. Disregard if thats a silly suggestion, just thought id offer my two cents.
try getting a new battery and see if it boots up...it can be your battery.and you are trying to charge with an AC adapter right?
Wall Charger
I am charing it via the wall charger (not usb) and I am going to try to get another battery. Just weird that I never had a battery problem until I install the wm6??!! Unless the damn thing drained my battery dry and somehow damaged the battery. I called Cingular and they are sending me another unit as its still in warranty. So we'll see when I get it - I will try the new battery. Strange. Very Strange - because everything was working last night.
Strange
Well after leaving the battery out all afternoon I took a go at the phone again, put in the battery then turned it on. It actually started booting up - showing the WM6 bootscreen. After about a minute it shut down like it was out of power. Strange. I know the phone is not bricked because if it was it wouldn't have just done what it did. Anyone have any suggestions how to fix it?
Could be a bad battery. You need to test out with some one else battery
HuddaDudda said:
Well after leaving the battery out all afternoon I took a go at the phone again, put in the battery then turned it on. It actually started booting up - showing the WM6 bootscreen. After about a minute it shut down like it was out of power. Strange. I know the phone is not bricked because if it was it wouldn't have just done what it did. Anyone have any suggestions how to fix it?
Click to expand...
Click to collapse
HuddaDudda said:
Well after leaving the battery out all afternoon I took a go at the phone again, put in the battery then turned it on. It actually started booting up - showing the WM6 bootscreen. After about a minute it shut down like it was out of power. Strange. I know the phone is not bricked because if it was it wouldn't have just done what it did. Anyone have any suggestions how to fix it?
Click to expand...
Click to collapse
u shud have plugged it in while it was booting...did u?
New Battery
Well I finally got the new battery I ordered today. When I put it into my phone it will boot into wm6 fine but will not sync with activesync 4.0 or charge via USB or plugged into the wall. I uninstalled activesync, rebooted my computer and installed Activesync 4.5 - but still no luck with the phone via usb syncing with my pc. Also when the phone in plugged into the wall via the wall charger it does not charge. I am beginning to think the port on the bottom somehow was disabled from the rom update, although I dont see any posts with people having that problem. I guess my next option is trying to reflash it to stock rom via a sd card since it wont connect via USB - however I can not find the information step by step how to do this. Can someone point me in the right direction?
Try going to the bootloader screen: Turn off your phone and then hold the camera button while you turn it on. When you are at the Rainbow screen (thats the bootloader) plug in your USB cord. You should see in the bottom left (above the left soft key) where it says USB. If it doesn't then I'd say your USB port is broken (I'm not aware of any ROM being able to disable that).
As for flashing from the SD card, I believe thats documented in the Wiki...
Ok this will be a bit lengthy but please bare with me and read...
Ive been running Darkyy 10.1 EE for months now and every has been fine.
Easily a couple of days battery, no force close issues of any sorts... Everything has been perfect.
Then the other day i noticed my battery started dropping fast. NO THIS IS NOT A BATTERY DRAIN THREAD SO PLEASE READ ON.
I took my phone off charge the other night within seconds of hearing the beep for battery full and the fully charged icon in the top right of the bar stayed there for a few seconds ( like maybe 10 ) and then the battery level dropped to 80%.
I thought hhmmm thats not right but left it and went to bed.
6 hours later i woke up to 31% battery.
I thought something must be running killing my battery so i did a reboot...
Now this is where it gets weird. Read on my friends...
after i rebooted the phone it kept rebooting itself every 2 minutes or so.
I pulled the battery of for 30 minutes and put it back but i had the same problem.
When i got home i did a factory rest and wipe cache partition and decided to flash Darkyy 10.2...
I had the same problems as above only now when my phone rebooted the battery lvl would drop by 20% then next time raise by 5% etc etc
NOW THIS BIT IS SCARY BUT READ ON!!!
I decided to flash back to froyo with ezbase using repartition to see if that would help.
I plugged my phone into the computer and nothing happened!!!! My computer wouldnt recognise my phone at all neither would my phone start charging whilst plugged into the computer.
I managed to get my computer to see my phone by booting into recovery and and then download mode and flashed ezbase.
Again same problems. So i thought OK this might be an insurance job so i flashed it back to stock JPY from samfirmware.com. I plugged it back into my computer and my PC says "the USB device you have connected has malfunctioned and windows cannot recognise..."
I have had my phone unplugged over night but the icon on the bar is still there showing USB connected, and in the pull down shade there is still the option to connect USB to copy files.
I have plugged it in this morning and it started charging but windows didnt even recognise that there was anything attached at all! No beep no fault deviced attached message... Nothing!
Oh i would also like to mention that when i flashed ezbase and tryied to do a reboot i would get the battery icon for a second like if you charged while the phone was off and then it would power down again... The only way i could get the phone to boot back up was to flash EZbase again with auto reboot ticked!
Yes that was very long sorry and thankyou to those who took the time to read it.
If anyone has any thoughts on why this would have happened please post.
Do you think this is something caused by the custom rom or is this a hardware issue completely out of my hands?
Thank you again for reading!
Have you tried another battery?
Sent using geek power
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
gsw5700 said:
Have you tried another battery?
Sent using geek power
Click to expand...
Click to collapse
I dont think its a battery issue because the battery wouldnt prevent the computer from seeing the device would it?
mammenj said:
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
Click to expand...
Click to collapse
Im running stock JPY right now and have the same problem
Could it be a damaged usb port, so that it doesn't always charge properly, and doesn't always detect the phone correctly when connected to the computer? That might explain the problems... Especially if that port is getting worse all the time.
Can you get it to detect on the computer if you wiggle the usb plug to the phone? Have you tried a replacement usb lead?
It does sound weird. Hope you manage to sort it out.
Mike
Garbled meaning induced by swype!
don wadte time if ur phone dosnt work on stock then its the port tht got damaged and the hardware,,,,something wrong .....better go to a service center..don expirement ,cause it might damage it more
I have just dropped it off at the shop i bought it from and they are sending it away for repair.
2 weeks of nokia 3210 magic for me!
Thanks for replies guys.
Hello guys, first than nothing, sorry for my bad english, isnt my native languaje. I got this problem yesterday in the night of the new year!!!!!!!:crying: I was rooted, using Xylon and Faux Kernel, but the problem appears from nothing!!
The first thing that I detected was, the phone take a WHILE!!! for charge.... then, out of the power, the phone get overheating and discharging so fast, never in life that happends, when N4 got discharged i try to turn on again but download mode appers in the screen, finally I get in the recovery, then I did a wipe cache/system and factory reset. Install again the Xylon... but when phone finally turns off, when I plugged in to AC absolutelly nothing happends, the led just turn in red, and the N4 dont start in FB, dont get charge, dont do a sh*t !!!! I conect it to the PC but also nothing appends, the N4 doesnt appear in my device list.
So... my N4 its broken?
There was possibly something wrong with the kernel and rom combination that caused your phone to overheat. I think eventually the heat may have damaged your hardware. Sorry but, if something was wrong in the first place it was not a good idea to reinstall the same thing that was causing the problem, if I were you I would have flashed a stock ROM. My only advice now would be to RMA it and pray
EDIT: I found this if it helps at all:
If you are unable to access the settings menu of your device, you can still reset your phone by performing a Hard Reset. Here are the instructions:
If your phone is on, power it off.
Press and hold Power until the device powers on, then immediately press and hold Volume Down (while still pressing Power). You will see the word Start with an arrow drawn around it.
Press Volume Down twice to designate Recovery mode.
Press Power to restart into Recovery mode. You will see an image of an Android robot with a red exclamation mark.
While holding down Power, press Volume Up.
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it.
Scroll down to "Yes - erase all user data" and press Power to select it.
Note: If at any point during the above steps your phone becomes unresponsive, you can restart it by holding down the power button for several seconds.
Before you try anything else, try and leaving it plugged in for a while and then try turning it on. Or leave it plugged in to a computer then try turning it on.
joshnichols189 said:
Before you try anything else, try and leaving it plugged in for a while and then try turning it on. Or leave it plugged in to a computer then try turning it on.
Click to expand...
Click to collapse
Try this. I haven't had it happen to me, but I do have a friend who this exact same thing happened and he thought it was bricked. He left it plugged into AC over night, and in the morning it would turn back on.
First than nothing, thanks for reply, I appreciate your intentions to help me.
I will leave it charging all the night and while Im working too... I hope after that, the phone at least turn on.
I dont install the STOCK ROM because I dont have it in my internal memory and I was in my girlfriend house, the night of the 12/31/12, there is not much to do...
I did the same post, but a little bit more explained
Its here: http://forum.xda-developers.com/showpost.php?p=36165434&postcount=2708
(In case you want to know all details about this problem..)
And Thanks againf for your help!
got the same ****
have a look here
http://forum.xda-developers.com/showthread.php?t=2050811&highlight=bricked+
we are not alone with that problem
some more people have the same problem
i did not even overclocked or benchmarked..
read this post, maybe its helpfull for you
http://forum.xda-developers.com/showthread.php?t=2011328
battery
It could be bad battery, how long did bought of you had working phone, how many times did you charge?
Did you use out of the box charger?
Did you have problems with usb jack?
kibox said:
It could be bad battery, how long did bought of you had working phone, how many times did you charge?
Did you use out of the box charger?
Did you have problems with usb jack?
Click to expand...
Click to collapse
I bought it the 13/nov..
I received it 29/nov.
I ALWAYS use stock charger, only 1 time i try to charge it in my car, but it was less thant 5 minutes, I decided dont charge with the car because the energy variates when I accelerate...
After that, I use my phone quiet normal.
I had this problem with my nexus 7. I think my battery died all the way and it couldn't charge. The stick charger wasn't doing anything. But I plugged it into my computer for a few minutes and tried turning it on. Then when the loading screen appeared I ran it to it's stock charger and charged it to full. Your battery probably died. Try different combinations of ways to get it to take a charge. Just long enough to turn on then plug it into its charger. Though the overheating could have fried it
Sent from my SPH-D710 using xda premium
The title says it all. For extra information:
So I got the battery full using universal direct battery charger and put it back. Switching it on without the charger plugged in won't work but switching it on with a charger plugged in does. You can even unplugged it after that vibration when turning on. That means, it's not the battery... you can even see the battery's full after booting successfully.
Not only that, with or without the charger, the S4 would heat up so much. No it's not the apps, even in safe mode or just while booting it would start to heat up. It wouldn't stop heating.
At first I thought the problem was the switch cause it won't turn on. Then I figured out it would turn on... but with the charger plugged.
Hmmm, any idea what cause it? It just happen all of a sudden one day. I'm thinking that, even if the switch or the port looks fine they may be the cause. Short-circuit I guess. Or I don't know, just my wild guess. If you experienced this one before, please share you experience and how you fixed it.
I'll add the edit I made on my reply here to make it easier to read.
EDIT: The heat is coming from the upper right area. Very close to where the switch is and sd card slot. Do you think it's the switch? If it's the switch, it's working well. No sudden reboots or shutdown due to the button acting like it's pressed when it's not, etc etc
EDIT: FIXED​
Flashed Albe95's LolliRom http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564 and also flashed Imperium Kernel (afterwards... because I thought I already did -_- )
At first I thought I would switch ROM to see if it's really the ROM that caused my problem (Stock with AEL kernel).
I downloaded Albe95's ROM and it took some time before it really boot successfully. On the thread it says that it would after 15mins, but mine after 15mins is still not booting. I flashed many times thinking that I made a mistake, like I forgot to wipe, etc etc.
The overheat problem was still there while it boots. It gets really really hot. I thought it is really a hardware problem now, I flashed a new ROM and therefore the kernel was changed, and if it was changed and it still has that problem my conclusion was right.
BUT...
I put it in the freezer to battle the heat. When I took it from the freezer, the phone's off. I thought the coldness what made it turned off. I took it, charged, and turned it on. And when it turned on after plugging it in... the battery's empty. It was around 50% when I decided to boot again and wait.
While it is still cold, I tried to turn it on again and wait now this time for it to boot.
Albe95 said it would take around 15mins only, but mine did boot past 15 mins. Can't blame me why I thought it's stuck on bootloop for many times. Now I'm thinking if I have only given Imperium ROM a chance... HAHAHAHA too lazy to flash and wait for a long time again.
Please hit thanks if I helped someone in the future with these issues.
what s4 model, rom and kernel do you have ? any mods ?
the battery could still be the problem. can you test it with another one, a friends maybe ?
Maybe a short circuit by sweat water that got into the phone. Open it up, take the board and other other easily removable components out and clean them with Isoprophyl(cleaning alcohol) and a new/clean soft brush, reassemble and see if it helped.
Backe888 said:
Maybe a short circuit by sweat water that got into the phone. Open it up, take the board and other other easily removable components out and clean them with Isoprophyl(cleaning alcohol) and a new/clean soft brush, reassemble and see if it helped.
Click to expand...
Click to collapse
This might do. Did not thought of this.
It's more on hardware I guess... Not kernel or ROM problem. Or, ok fine, just to be sure I'll try to flash Albe95 ROM. I am on Stock before and accidentally wiped the system partition also while trying to factory reset via recovery instead of data, cache, and dalvik only. Even without the ROM, it overheats very much.
EDIT: The heat is coming from the upper right area. Very close to where the switch is and sd card slot. Do you think it's the switch? If it's the switch, it's working well. No sudden reboots or shutdown due to the button acting like it's pressed when it's not, etc etc
Let me explain what happened: I was using the phone as normal, but suddenly it started to reboot itself, and with every reboot it was losing some battery until the point it lost all the energy, and now when I try to charge it, the only thing I get is the battery animation starting and suddenly disappearing, like a bootloop. Same situation when I try to boot into Safe Mode or Recovery Mode. But I was able to boot into download mode, so I tried to flash the stock firmware again both through Smart Switch and ODIN, but I got the same results. And also, this only happens if I have the phone connected to the PC or the charger. If I try to turn it on while disconnected, it doesn't do anything. What can I do???
Update: Well, now it reaches the Samsung logo but it get stuck in a bootloop. I 'm also able to boot to the recovery, but I'm not really sure of what can I do from there
I'm having similar issues!
Upon further investigation, I discovered some pocket lint stuffed in the bottom of the MicroUSB-port. A toothpick was enough to get it out. Still having issues with "mmc_read" failure, booting and long response times, but at least it charges reliably now. Will flash updated recovery/kernel/ROM as it has been a while - fingers crossed this will help.
I'm thinking the root cause of our issues might be different, but check your USB-port if you haven't already.
For my next phone I will consider integrated port covers, like the Xperia series.
I bid you good luck fixing your problem. Would'nt mind knowing what the root cause of your problem is if you find out.
The phone is alive again! The problem was the battery, I just replaced it and the phone booted as normal
Aaron Cruz said:
The phone is alive again! The problem was the battery, I just replaced it and the phone booted as normal
Click to expand...
Click to collapse
Thanks for the update. Just out of curiosity. Was the bad battery a little bit puffy. On my note 3 I could tell by feeling and looking at it from the edge. Battery going bad starts to Puff up in the middle.