Related
This has happened once before, but just for a small amount of time to to the heat (I believe). The phone has been off for over and hour and refuses to turn on whether I hold down the volume button, don't hold down the volume button, or push the battery in at the exact time as I'm doing the other one or two. The splash screen flashed for half a second and immediately went back off when I plugged my evo charger, the usb part, into my portable ipod charger, so I believe this means there is still help available! Last time this happened, which was months ago, it seemed as if it just needed to cool down a bit, and my reading on the internet confirmed that the phones shut off when their batteries reach too high of temperatures. So what I did was wrap the phone and the battery, separately, in a large wash cloth and let them sit it the fridge for a little while. No luck, I'm running out of ideas (and I realize a ziplock bag may have been better but who cares). A few days ago I installed cm7gginggerbread7 (wimax) over cm7gingerbread2, but have not had any issues up until now and everything has run perfectly as well as smoothly. Is there any way I can turn my brick into a phone? Perhaps there's a way to adb something even though the phone wont boot (im a noob). I'm just pissed cuz I finally got every little thing exactly the way I wanted it, and now I'm stuck with a paperweight :/ I thank you for all your help, brave knights
It just suddenly shut off and won't turn back on?
And you weren't messing with anything?
If so, sounds like it's a hardware or battery issue.
Can you try a different battery?
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
sitlet said:
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
Click to expand...
Click to collapse
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
matt2053 said:
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
Click to expand...
Click to collapse
If they can't get it to power on then it really doesn't matter if it's rooted or not because they won't be able to find out.
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Raillery said:
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Click to expand...
Click to collapse
If this occurred while you were NOT changing anything with the radio partition or recovery partition then it's not a brick issue.
Sounds like you have a hardware issue.
Take it to the store.
If you smash it you will be paying $100 to asurion for a replacement as Sprint changed the TEP again.
Just wondering was your battery completely dead before this happened. I have read some people here and other places have said that if the battery completely dies that it won't charge unless you put it on a actual battery charger made for it. Does the charge light come on when you plug it in? Also, like my friend before me said, take it to Sprint. Ask them if they have a battery you could try. If it doesn't work it will eliminate the battery being the issue. If it won't boot they will replace it. They won't be able to tell if it is rooted because it won't boot. If you were flashing a radio and didn't let it finish or the battery died during the process, you are bricked.
Does the charge light flash when plugged in?
Sent from my PC36100 using Tapatalk
The light doesnt change
clean off the battery contacts
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
vespix said:
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
Click to expand...
Click to collapse
Take the original battery to sprint. Tell them the story and get a replacement, ask for some free accessory since you've helped them isolate a reliability issue.
LOL
There are two known issues with the Evo to be aware of. The first is the charging bug. If the Evo shuts off due to low battery level there is the possibility that the charging circuit fails to recognize the dead battery as even being there and will not charge. The workaround is to charge the dead battery in another compatible phone or use an external battery charger. This is supposed to be fixed in the next update but we'll see.
The second is the thermal sensor bug. The thermal cut off starts to trigger at lower and lower temps til even freezing the phone won't work. I thought the local service center was joking til I actually saw it reproduced. This is a hardware issue and the only fix is a replacement phone.
The first issue is intermittent but knowledgeable service centers are aware of this and will either charge the dead battery or swap out with a charged one.
The second issue is reproducible but can take some time to do so depending on how far off the sensor is. Again, knowledgeable service centers are aware of this and will want to reproduce it before ordering a replacement.
Not sure what technical thong is happening, but I do know I panicked when it happened to me, bit it turns out if you try to charge EVO from a USB port while its in the recovery mode it will eventually drain and **** off. I forgot I was on recovery mode and came back to what you described. After doing the swap with my GF's EVO and realizing my battery was fine, I remembered how I had left the phone in the first place and Googled it to confirm that will cause the dead EVO scare.
Sent from a corrective lens wearing eskimo translating Turkish smoke signals viewed over a streaming webcam at 640x480 resolution via a U.S. Robotics 14.4 Hayes compatible modem.
This has happened to me twice, but since I was on the extended battery from sprint, I would just pop my stock battery in and it powered up fine. Each time I just brought my battery in to sprint and they replaced it. Also, when it happened to me the charging light wasn't turning on or anything.
Sent from my PC36100 using XDA Premium App
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
cjh6386 said:
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
Click to expand...
Click to collapse
Blinking charge light means that the battery v has dropped below the required v to turn on the phone. I see 4-5 Evo's a day like this as well as the charge bug.
I actually got it booting again somehow. Now, it consistently turns on, will boot to the bootloader, but recovery doesnt work and it wont boot into the phone. It does search for pc36 image though... i might try that.
I just sit here and shake my head on a daily basis when I see people talk about problems and inevitably, and I'm not saying this is applicable in this case, but they say in their post they were using ROM or Kernel Manager.....
I've been runnin the unity rom for a couple of months now( i was) with no issues at all, when yesterday morning my phone turned off itself and i haven't been able to bring it back to life. i dont know if i have the bad chip, never cared to check but i regret it now lol... any sugestions would help.... also i have tried turning on w/o sim card with a different battery, also tried to get it to bootloader but it just wont turn on at all.. thanks in advance
frankgbacoa said:
I've been runnin the unity rom for a couple of months now( i was) with no issues at all, when yesterday morning my phone turned off itself and i haven't been able to bring it back to life. i dont know if i have the bad chip, never cared to check but i regret it now lol... any sugestions would help.... also i have tried turning on w/o sim card with a different battery, also tried to get it to bootloader but it just wont turn on at all.. thanks in advance
Click to expand...
Click to collapse
Does the computer recognize it?
Sent from my HTC Glacier Sense 3.0 using xda premium
If you're talking about no power at all, it doesn't sound like a software issue. It sounds like an electrical issue.
If the screen backlight comes on when you hit the power button, then it could be software or electronic (borked chip, broken circuit board, etc)
Plugging it in, even if it's a dead phone, should still charge the battery if the electrical circuits are good. The LED will come on at orange or green and that should tell you if there is physically electricity running through the circuits.
If you get nothing, something in the phone died. I'm starting to realize the MT4G has a pretty poor build quality.
If the battery is charging and the backlight comes out, maybe a quick vibrate to indicate charging, then you could have some kind of an electrical short in the circuitry somewhere.
Or you just have a bad power button. That's a possibly. But that's odd that it turned itself off. That's what makes me think the power button itself isn't what's wrong.
In all cases it sounds dead. If you can't get to the recovery screen there's not much you can do.
saranhai said:
Does the computer recognize it?
Sent from my HTC Glacier Sense 3.0 using xda premium
Click to expand...
Click to collapse
no the computer does not recognize..thanks
Skipjacks said:
If you're talking about no power at all, it doesn't sound like a software issue. It sounds like an electrical issue.
If the screen backlight comes on when you hit the power button, then it could be software or electronic (borked chip, broken circuit board, etc)
Plugging it in, even if it's a dead phone, should still charge the battery if the electrical circuits are good. The LED will come on at orange or green and that should tell you if there is physically electricity running through the circuits.
If you get nothing, something in the phone died. I'm starting to realize the MT4G has a pretty poor build quality.
If the battery is charging and the backlight comes out, maybe a quick vibrate to indicate charging, then you could have some kind of an electrical short in the circuitry somewhere.
Or you just have a bad power button. That's a possibly. But that's odd that it turned itself off. That's what makes me think the power button itself isn't what's wrong.
In all cases it sounds dead. If you can't get to the recovery screen there's not much you can do.
Click to expand...
Click to collapse
no led lights it just died lol... it wont do a thing. im starting to think that it has some kind of short between the battery and the circuit that distributes power through out the phone.. thats my best guess.thanks
You can also check to make sure the battery isn't the problem by removing it and plugging the phone in. Again, the best you'll get is a brief flash of the backlight. But if you don't get that, you can be sure the battery itself isn't the problem.
Or just put a new battery in and see if that works.
This is highly unlikely to be the cause. But it's all about narrowing the possibilities. I've been fiddling with electronics for 20 years now. One thing I'm sure of is that you should never discount the really unlikely source of a problem. It won't usually be the answer, but every once in a while something you'd just never suspect ends up being the culprit.
I had the exact same issue, earlier this year. Your emmc chip gave you the bird. Go into Tmobile store, tell then your phone won't turn on, you tried the normal tricks, but nothing works. Act a little dumb with them,I did that an got a new one under warranty for $5, came in the mail the days later. DO NOT MENTION ANYTHING BOUT YOUR PHONE BEING ROOTED. If you do, your gonna have to pay full price for a new one or though the issuance company a $130(or whatever your deductible is).
Trust me on this, it works. I'm still using the phone they sent to me back in June.
If I helped, give thanks(via the button )
From my fist to your face, enjoy!
Mr.Highway said:
I had the exact same issue, earlier this year. Your emmc chip gave you the bird. Go into Tmobile store, tell then your phone won't turn on, you tried the normal tricks, but nothing works. Act a little dumb with them,I did that an got a new one under warranty for $5, came in the mail the days later. DO NOT MENTION ANYTHING BOUT YOUR PHONE BEING ROOTED. If you do, your gonna have to pay full price for a new one or though the issuance company a $130(or whatever your deductible is).
Trust me on this, it works. I'm still using the phone they sent to me back in June.
If I helped, give thanks(via the button )
From my fist to your face, enjoy!
Click to expand...
Click to collapse
ill try it tomorrow see if it works lol.... hopefully...thanks i was afraid of being the emmc chip.... damn it..
frankgbacoa said:
ill try it tomorrow see if it works lol.... hopefully...thanks i was afraid of being the emmc chip.... damn it..
Click to expand...
Click to collapse
It's always good to be safe then sorry
If I helped, give thanks( via the button )
From my fist to your face, enjoy!
Went out yesterday afternoon with some friends, had about 80% charge on the battery. Probably an hour into my night, I went to check my phone (i always keep it in my front pocket), and to my confusion, it wouldn't power on. Okay...maybe somehow an app left running killed the battery (although I think they designed the phones not to do this). Fast forward about 4 hours, when we get back home. I plug the phone into the wall charger and instantly see an unfamiliar blinking red led light just above the charge port. The phone wouldn't power up, decided to check back later. 30 Minutes later, still nothing. 8 Hours later on charge, still nothing.
I've tried hard resetting, I've tried holding the power button for 30 seconds, I've tried holding all three simultaneously. I guess it's just a dead phone.
I didn't root the phone, I didn't custom-rom the phone, no 3rd-party kernel...nothing...she was completely stock.
I called google, their support agent wasn't familiar with the phone. Said he'd get an RMA started, would email me the details he needed from me...never got back to me. I'm pretty pissed.
Waiting 5 weeks for a phone that dies in a month....not a happy camper.
UPDATE! FIXED IT
Following the guide here:
http://www.ifixit.com/Teardown/Nexus+4+Teardown/11781/1
I took it apart, disconnected the battery lead, and reconnected the lead...poof it boots!!
Click to expand...
Click to collapse
UPDATE #2
The phone "died" again. Took it apart again, pulled the battery, again. Factory Reset, the phones been on a charger since then and it is still on, we'll see how it lasts the day.
I'm not sure if there is any proof of this, but I read somewhere that benchmarking apps can cause this(?) I had Quadrant installed on my device shortly before this happened. Anyway, I'll let you guys know if I have any more problems.
UPDATE #3
I've lost it again. I don't know what to do at this point...
Before I proceed,
1) Are you comfortable working on electronics
if yes, continue to 2. if not, stop here.
2) Do you have the appropriate tools?
rr5678 said:
Before I proceed,
1) Are you comfortable working on electronics
if yes, continue to 2. if not, stop here.
2) Do you have the appropriate tools?
Click to expand...
Click to collapse
Yes and Yes, but I don't want to void my warranty on such an unknown problem. I'd rather see it replaced and they can research the problem on my phone and try to prevent it in the future so others don't have to go through this. Thanks
Don't you just hate the fact that some random employee at Google will easily have access to all of your personal data left on the phone?
Oh well, at least you get taken care of.
ethugp3pp3r said:
Yes and Yes, but I don't want to void my warranty on such an unknown problem. I'd rather see it replaced and they can research the problem on my phone and try to prevent it in the future so others don't have to go through this. Thanks
Click to expand...
Click to collapse
I'm not aware of any warranty/void stickers on this phone.
have you seen this?
If
If the phone battery has been discharged too far then it becomes dangerous to try and recharge it as it can explode, this is why these sorts of safety mechanisms kick in sometimes.
Your only option is to send it back, if the battery safety device has been activated, it will be permanent and can only be fixed by a new battery
Regards
Phil
rr5678 said:
I'm not aware of any warranty/void stickers on this phone.
Click to expand...
Click to collapse
Are you sure? Can anybody else verify this? What were you going to suggest doing? I'm having lots of complications with the RMA process because i'm currently visiting in England until the end of the month and then I'll go back to Germany where I'll be living for the next ~7 months. I got this phone last month when I was visiting home in the US. It's a total disaster and if disconnecting and reconnecting my battery is all I need to do (and I won't void the warranty), I'd prefer to give that a go.
oh and another thing...when I connect the phone to my laptop, the USB connect/disconnect sound plays every 5-6 seconds. So it seems like the phone is turning on, and then off again...over and over again.
ethugp3pp3r said:
oh and another thing...when I connect the phone to my laptop, the USB connect/disconnect sound plays every 5-6 seconds. So it seems like the phone is turning on, and then off again...over and over again.
Click to expand...
Click to collapse
I figured that all this red light stuff could be solved by a simple battery pull, but LG was too STUPID to realize that people need an accessible battery and now to even try it, you have to open the phone and unscrew the battery connector.
rr5678 said:
I figured that all this red light stuff could be solved by a simple battery pull, but LG was too STUPID to realize that people need an accessible battery and now to even try it, you have to open the phone and unscrew the battery connector.
Click to expand...
Click to collapse
Is it really that easy? Will the warranty be voided?
Following the guide here:
http://www.ifixit.com/Teardown/Nexus+4+Teardown/11781/1
I took it apart, disconnected the battery lead, and reconnected the lead...poof it boots!!
ethugp3pp3r said:
Following the guide here:
http://www.ifixit.com/Teardown/Nexus+4+Teardown/11781/1
I took it apart, disconnected the battery lead, and reconnected the lead...poof it boots!!
Click to expand...
Click to collapse
There you go. You've confirmed the fix.
HI EVERYBODY.
I'm back. The phone has done it again. I've not got the patience to peel the back off, but it's gone into the blinking red light on charge/not booting up at all mode.
GOOGLE/LG, IF YOU'RE READING THIS, Send us all a new battery as well as the tools to replace it, and update the software, too. I'd also like $50 for the trouble, and please, fire every single "support technician" that thinks the sim card is behind the battery on a nexus (I've had that 2 times now from support)
The phone is great when it works, but it's "infrastructure" is absolutely god awful.
Will report back. Recommendations are welcome!
ethugp3pp3r said:
HI EVERYBODY.
I'm back. The phone has done it again. I've not got the patience to peel the back off, but it's gone into the blinking red light on charge/not booting up at all mode.
GOOGLE/LG, IF YOU'RE READING THIS, Send us all a new battery as well as the tools to replace it, and update the software, too. I'd also like $50 for the trouble, and please, fire every single "support technician" that thinks the sim card is behind the battery on a nexus (I've had that 2 times now from support)
The phone is great when it works, but it's "infrastructure" is absolutely god awful.
Will report back. Recommendations are welcome!
Click to expand...
Click to collapse
Did you let your battery drain all the way or something?
Sent from my Nexus 4 using xda app-developers app
BigDig said:
Did you let your battery drain all the way or something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, I haven't done that. I just took it apart and reconnected the battery for the 3rd time. I really don't know what the f**k to do at this point. Does anybody have any idea what could be causing this? Google will not allow me to RMA the phone because I bought it in the US and I live in Germany (they won't ship it to Germany for some **** reason).
ahhhhhh!!
ethugp3pp3r said:
Nope, I haven't done that. I just took it apart and reconnected the battery for the 3rd time. I really don't know what the f**k to do at this point. Does anybody have any idea what could be causing this? Google will not allow me to RMA the phone because I bought it in the US and I live in Germany (they won't ship it to Germany for some **** reason).
ahhhhhh!!
Click to expand...
Click to collapse
bad battery is causing it...
Find a replacement.
You can also call LG instead of google. They may RMA for you.
tweaked said:
bad battery is causing it...
Find a replacement.
You can also call LG instead of google. They may RMA for you.
Click to expand...
Click to collapse
It's lasted through the night off the charger on Franco's Kernel and CM 10.1
not sure what that tells us, but I'm happy!
I'm 90% sure all of these weird battery problems + red light are because of stock charger!
Search around and see..
calanizzle said:
I'm 90% sure all of these weird battery problems + red light are because of stock charger!
Search around and see..
Click to expand...
Click to collapse
Good thing I hardly use that one
But instead of telling us to search, could you provide us with sources? Because this is interesting.
Somebody should compare the LG charger with another good quality charger, a Samsung or Nokia for example, using a scope.
I was playing around with my Nexus 4. It fell in a glass of water. I took it out within 2 seconds. Phone booted up and worked fine except Camera and the earpiece. Those started to work fine after around 5 hrs automatically. I flashed Stock Android 4.2.2 via Fastboot after everything was working fine. It failed while flashing bootloader and then the phone went completely blank. I did 30 mins of work and google search and I was trying all sorts of combinations and the phone booted by luck. After then it went in Blank many times showing *white* LED. I was always able to take it out of that by some combinations. Now the phone got stuck in bootloop. I switched off the phone and plugged it for charging. It charged upto 100%. My mom took my phone and locked in the cupboard (due to exams) I got it today (after 2 days) and when I try to boot then it just shows *Red* LED for some time and then goes off. If I plug it to a wall charger then the Red LED lasts merely a second.
Please help me guys.
iHarkunwar said:
I was playing around with my Nexus 4. It fell in a glass of water. I took it out within 2 seconds. Phone booted up and worked fine except Camera and the earpiece. Those started to work fine after around 5 hrs automatically. I flashed Stock Android 4.2.2 via Fastboot after everything was working fine. It failed while flashing bootloader and then the phone went completely blank. I did 30 mins of work and google search and I was trying all sorts of combinations and the phone booted by luck. After then it went in Blank many times showing *white* LED. I was always able to take it out of that by some combinations. Now the phone got stuck in bootloop. I switched off the phone and plugged it for charging. It charged upto 100%. My mom took my phone and locked in the cupboard (due to exams) I got it today (after 2 days) and when I try to boot then it just shows *Red* LED for some time and then goes off. If I plug it to a wall charger then the Red LED lasts merely a second.
Please help me guys.
Click to expand...
Click to collapse
Take out the battery and reinsert it,i have seen people complaining of red blinking led issue,but in their case,the phone shut down due to 0 battery,and when try to turn on by connecting wall charger,the issue showed up.If there's a possibility that the phone got completely discharged in cupboard(due to low or no signal),then that might be ur issue as well.
ashishv said:
Take out the battery and reinsert it,i have seen people complaining of red blinking led issue,but in their case,the phone shut down due to 0 battery,and when try to turn on by connecting wall charger,the issue showed up.If there's a possibility that the phone got completely discharged in cupboard(due to low or no signal),then that might be ur issue as well.
Click to expand...
Click to collapse
The phone was powered off in the cupboard
ashishv said:
Take out the battery and reinsert it,i have seen people complaining of red blinking led issue,but in their case,the phone shut down due to 0 battery,and when try to turn on by connecting wall charger,the issue showed up.If there's a possibility that the phone got completely discharged in cupboard(due to low or no signal),then that might be ur issue as well.
Click to expand...
Click to collapse
I am afraid taking out the battery. What if voided the phone ?
If the phone has been water damaged, warranty won't help you anyway so you haven't got anything to lose! Just a reminder, if you drop your phone in water, turn it off (take out the battery if possible) and put it in a bowl of rice for 12-48 hours to help dry it out, do not turn it on before then!
iHarkunwar said:
I am afraid taking out the battery. What if voided the phone ?
Click to expand...
Click to collapse
You are already voided due to water damage.....
BigDig said:
You are already voided due to water damage.....
Click to expand...
Click to collapse
And btw no international warranty for this phone.
But it is already worked completely fine after around 5 days. I also instantly blew a hard dryer on it and it go to work. It shows no signs of Water Damage
ashishv said:
And btw no international warranty for this phone.
Click to expand...
Click to collapse
I can ship it back to US. I bought it from Indian site which ships phone to US if any problems come and will deal with RMA.
iHarkunwar said:
I can ship it back to US. I bought it from Indian site which ships phone to US if any problems come and will deal with RMA.
Click to expand...
Click to collapse
Which site?I used ppobox.
ashishv said:
Which site?I used ppobox.
Click to expand...
Click to collapse
TheAmericanBazaar
Also when it fell in water it had the cover on and the screen protector over too.
Was going to sell and buy HTC One and Google trolled me
iHarkunwar said:
I am afraid taking out the battery. What if voided the phone ?
Click to expand...
Click to collapse
The phone isn't really hard to take apart, I posted a video on YouTube a while back showing how to take apart the phone and replace the screen.
https://www.youtube.com/watch?v=A1aiut8RXhc&feature=youtube_gdata_player
Sent from my Rooted Galaxy S III using xda premium
speedygonzo said:
The phone isn't really hard to take apart, I posted a video on YouTube a while back showing how to take apart the phone and replace the screen.
https://www.youtube.com/watch?v=A1aiut8RXhc&feature=youtube_gdata_player
Sent from my Rooted Galaxy S III using xda premium
Click to expand...
Click to collapse
Will try then
I have a complete set of screw drivers. None worked on the Nexus 4 :/
Similar
Dropped phone in toilet. 2 seconds max. Didnt have luxery of a torque screw or pop open capabilities threw the N4 in bag of rice. 4 days later. it turns on and the screen looks fine, but auto shut down right when main screen loads. Checked for water damage on the inside: void stickers were pink, but phone seemed fine and no sign of water damage, until I took out the battery. it looked a bit damaged. I replaced it today and I am still getting the same issue. Right when I am taken past the Cyanogenmod loading screen, the main page loads and says "shutting off" or "powering down" whatever it says. The battery seems to always be between 16-18% also. Anyone ran into a situation like this or have any suggestions? please!!!! thanks!
I decided on packing up my s8 and use it later.
I charged it up to a 100(shutdown) at 4:30 used it for a bit and then shut it down kept it back in the box.
Around 7:00 i took it out to extract the sim card but when i took the phone out it was so hot that I couldnt hold it so i put it next to the AC.
My question why it overheated and if I have harmed the battery how do I check the harm done?
Unrooted s8 g950fd
What else harm has ovverheating done to my phone?
Return it asap.
drew272011 said:
Return it asap.
Click to expand...
Click to collapse
Why?
Am115h said:
Why?
Click to expand...
Click to collapse
Cause a phone that is powered off should not get warm, let alone get so hot you can't touch it. You have a serious hardware defect that is likely very dangerous. Perhaps you've heard of the Note 7?
Words right out of my mouth , You can't touch it ???? Something is Really wrong
You sure it didn't get turned on by accident, overheated then shut off?
There's always that possibility the power button got pressed while it was in the box. Cuz there was no air flow in the box, the heat got trapped in.
Still sounds unlikely so to be on the safe side return the device and get it swapped for one that isn't faulty.
Sent from my Samsung Galaxy S8 using XDA Labs