Related
I apologize in advance if there is a similar thread; I could not find one.
My EVO has been fine, no issues. I use it heavily every day. I'm running Cyanogen 7 nightly 147 (I think) and have been for 4 or 5 days. Using the Tiamat kernel running SMARTASS.
Last night I shut down around midnight with around 50% power. I plugged in the charger but don't remember if the charging light came on then. This morning there is no charging light and the phone won't boot. Tried long holding the power button, battery pulls, pulled the SD card (for lack of anything else to try). Nothing has had any effect.
Does anyone have other ideas? I'm at a loss. If it's dead, it sure chose a strange way to go. Any advice would be very appreciated. I need this thing for work and home. Many thanks.
Just after posting I went back to playing with different chargers and power button pushes. The white HTC logo flashed for a second and the phone vibrated but it went right back off. It's the first sign of life I've seen, but I can't get it to repeat or go further.
This happened to my sisters Evo when she first got it last summer. Luckily it was the battery and HTC shipped a new one for free. The warranty on the evo is 15 months so you can try and request a new battery!
Sent from my PC36100 using XDA App
I have found one similar thread: http://forum.xda-developers.com/showthread.php?t=913258. So maybe it is a dead battery. Been getting amazing life recently, so it seems crazy that it would suddenly be dead. Is this common?
Any suggestions for going to the Sprint store with a rooted phone? Since it's a bad battery, they may not need to look at the phone once it boots. I haven't had to do this before, so I'm not sure what to expect.
if you do go to a sprint store, i would not let them keep the phone or even take it out of your sight. if that happens you may well find yourself unrooted. but thats just a guess. you can get on ebay or any other similar site and buy a cheap battery for less than $5. then if thats not the problem go from there. this same problem happened to me but luckily one of my friends also has an EVO so i just used his battery and my phone worked great. so i just bought a new battery
Thanks for the input. Headed to the Sprint store in a minute to see if a battery will solve it.
It was the battery. They tested in at the Sprint store and pronounced it DOA. They said they don't normally have spare batteries but they happened to have one, luckily. I was pretty grabby with the phone and didn't let it go for long. Once it started to boot I took it back and they never saw the Cyanogen screens.
Overall they handled it very well. I was impressed with how responsive they were. I was out of there in 10 minutes.
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
S.H.A.D.E said:
Hey Guys.
I'm very excited to get my nexus 4 but I've been hearing a lot of people talking about the RLOD!!
What causes this problem and is there anyway to fix this??
Click to expand...
Click to collapse
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
propably you could check the rev of those n4's (asking them in pm's). i can't imagine rev11+ have this problem anymore. I still won't believe this happened without a reason
S.H.A.D.E said:
Thanks for the reply,
Ive heard many people who had a completely stock and unrooted nexus 4 say they got a red light of death too... The problem is, I don't live in any of the countries that have playstore devices. So I'm having somebody from the US bring it for me...
Click to expand...
Click to collapse
These many people you speak of? That's not even half possible for it to RLOD on pure stock without any mods it's just to save the hardware its the phones built in safety net...unless you plan on OCing to 1.98ghz and set it to performance and run antutu that will most likely do it for you
Sent from my Nexus 4 using xda app-developers app
Hi,
It happened wih or without running an Antutu bench. Yes some users have reported the red light on stock with rev 10 or with rev 11.
Antutu is not directly the culprit, it's due to a bad read of battery stuff (in a stress condition even at 50% battery the phone think you are out of battery then shutdown + heat, there is an issue with some phone about the battery contact inside the phone). If it's happen you can try to let your phone in charging for hours, sometimes it's enough. But the better thing is to open your phone then disconnect / reconnect the battery.
It happened also while flashing something in recovery mod, 40% battery, flash then reboot and bam red light...
Also on a French forum it happened during a download while browsing...
I agree we not know all the conditions together when it happened but it seems this is slightly random. Maybe a combination of circumstances...
It's "just" related to some weird battery reading issue.
For example I ran a bunch of Antutu bench with / without overclocking at different battery % (even at 11% battery ) without any issues, at least until today...
Take a look here: http://forum.xda-developers.com/showthread.php?p=36304348
So does this problem happen to everybody or is only a minority of nexus 4 users affected? Do you think google would've fixed this problem by now??
Re,
It seems it's a minority phones who are concerned...
I don't know if Lg / Google have worked on the problem. As I read maybe the rev 11 are less concerned? But I'm not sure...
Don't be afraid, use your phone and if that happens rma or open your phone, there is always a solution
Alright, read a lot of threads and it looks like removing the battery and starting it again works perfectly. I also read somewhere that its due to too much pressure being applied on the thing the connects the battery to the phone.. - http://forum.xda-developers.com/showthread.php?t=2128392&highlight=red+light+of+death&page=2
Yes, it's what I said, ah I forgot this link.
When you search, you find
Happened to me a few days after I got it (100%stock, not rooted); I left it charging for some time and it turned on again like nothing happened. Didn't happened since.
Only time I had it was when I first rooted.
It got stuck in a boot loop on the "X" screen and when I rebooted to clear the cache the red light flashed and I had to hold the power button in to turn it off.
Booted into recover fine after that.
No issues since.
Alright that's good to hear. When did you guys get your nexus?? Maybe google resolved this issue.
I got mine very recently ordered in late February. It did red light because I flashed a mod which was for the nexus 7 but i flashed it on my nexus 4. I just went into recovery and flashed stock, phone was fine.
Sent from my Nexus 4 using xda app-developers app
Alright. Sounds good.
Got mine last week but it's a Rev 10 not an 11.
indoh said:
the red light is just caused by using your phone the wrong way. it won't happen if you do not flash a custom rom anyway.
And if you flash custom roms it won't happen either, if you follow the standard steps you have to follow on every android phone. It's just a brick that can happen on every android device if you flash broken .zip's or anything else comparable .
People who claim this happened from a moment to the next without them doing anything wrong, are just not telling the truth. Even IF this would happen this way(not your own fault), you could easily get a replacement from google without any costs or problems.
Click to expand...
Click to collapse
That is not true.. Red light appears due to some small chip next to the battery which is hardly put in there, you just need to release some pressure and it will be fine.. (there's a youtube video)
Loosen the screws?? Do you have a link to the YT video?
Ordered mine when they were first available, got it 2-3 weeks later (end of November).
Got a bricked rev11 301k here. Tried everything untill I get my replacement (takes a bit longer since I live in holland). Check out http://forum.xda-developers.com/showthread.php?t=2177787&highlight=nexus+4+bricked for more info. Now I try to drain the battery and let it charge (put it in a cold enviroment for a full 24 hrs. Got past the google logo for half a second and saw the stock recovery before it went dead again
Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...
Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2
This looks pretty strange 0.o
Consider buying a new recovery
HITTTTTTT THANNNKKKKSSS
galaxy star duos ****rooted*** xda offical app ) )
I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.
nwsk said:
I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.
Click to expand...
Click to collapse
Well *#!$
I'll observate it for the next few days and see if it's getting worse...
If your phone is rebooting as opposed to just powering off, then I suspect it is hardware related (motherboard) as already mentioned.
I do hope I'm wrong though.
Maybe try using it for extended periods while plugged into a charger and see what happens. If it doesn't reboot then it may just be the battery.
Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.
I9500 owner. Had this exact same problem when using older firmware. After updating to the latest one, never had this issue again. Its been two months now, even more.
Try this. Flash the latest available firmware for you phone, not talking about OTA but the downloadable one from any region (whichever is latest for i9505). I guess it may have something to do with the kernel too.
Edit: wait a minute, why is your battery level going up when it isn't even charging in the second screenshot. Middle of the battery timeline. That's weird. I guess you should send the phone back
Sent from my GT-I9500 using xda premium
Its a hardware issue(motherboard).I hope your under warranty.Best of luck .
i have something strange like that also on my device ..
http://forum.xda-developers.com/showthread.php?t=2409284
Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)
E_Cartman said:
Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)
Click to expand...
Click to collapse
Same problem here. It started three days ago and today I'm barely able to use it... I'm still on warraty and I even have insurance, but it's a major inconvenience anyway.
Mines gone in for repair back to my carrier still no movement despite them having it for 2 days now really should have sent it back to Samsung directly. Will keep you guys posted.
Sent from my Nexus 4 using Tapatalk 2
Will send it in tomorrow. Lady on the hotline told me apparently the motherboard is defect and I'll get a new S4. Exchange, no repair. I'm fine with that...
Sent from my GT-I9100 using Tapatalk 4
That's good to hear, just inconvenience but at least you won't have to pay for it (or have the defect materialize a year later or something)
E_Cartman said:
Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...
Click to expand...
Click to collapse
nikzDHD said:
Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
nikzDHD said:
Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.
Click to expand...
Click to collapse
im4eversmart said:
Its a hardware issue(motherboard).I hope your under warranty.Best of luck .
Click to expand...
Click to collapse
Hey
I am new here.
but i was looking for information becuase my s4 9505i has the same problem
shuts of almost everytime i open apps too quickly or stream youtube or some other high usage apps etc.
battery drops up to 50 percent then back 40 percent then to 0 percent, the fact it that the phone never seems to know where the battery is.
by the way my phone is not rooted and i have done the factory reset a few times.
samsung... hmmm.. they seem to be real hard to talk to on the phone, i have had to call them 4 times already about the s4 i ahve had since june, and they just play me off like i am some kind of idiot etc. and deny that there is possibly any reason for random shutdowns, phone freezing, and now this battery/motherboard issue.
next bit is kinda stupid, the phone has a few internal scratches on it from when i ahve stupidly had the phone next to keys and all that. im sure they are going to try and void my warranty and say i have mistreated the phone...
had many phones before, maybe close to 50 and never, never, never have had to ring up a company to try and complain etc.....
any ideas.
I am in Australia,
I am thinking of trying the CONSUMER AFFAIRS kind of threats, but i have to word it the right way...
I seem to be experiencing some weird problem with the battery on my I9500.
I only get about 12 hours battery life with minimal usage and can drain the battery completely within 3 hours or less if I keep the screen on which is much less than what it should be. When the battery reaches <10% the phone sometimes suddenly drops to 0% and switches off. This happened last night and I charged for about 1 minute, switched it on and it showed 50% again and lasted another 1.5 hours. The actual battery has an ever so slight bulge (not even 1mm but you can notice when putting it flat on the table).
I flashed the phone with OMEGA and Adam kernel about 3 weeks ago, the problems started about 1.5 weeks ago. Thus not sure if there might be a problem with the kernel or ROM causing this.
Any ideas what may be causing this? Defect battery or device or may a reflash help? Also anything I can do with resetting battery stats?
Any help would be appreciated!!!
It seems like a faulty battery, which is quite common for Samsung phones. You should ask for a replacement. Not Omega ROM issue.
Knowing the service centres this will probably mean sending in the device for a few weeks which is not an option with the counter and no way to reset this yet on the I9500... May have to just buy a new battery then. Any other ways of testing?
Have you tried flashing your device back to Samsung stock ROM? If the problem still persist, it is not a custom ROM/kernel issue then.
windozeanti said:
Have you tried flashing your device back to Samsung stock ROM? If the problem still persist, it is not a custom ROM/kernel issue then.
Click to expand...
Click to collapse
Still have to... Will try that as soon as I have time.
How do everyone else's batteries look? 100% flat or the tiniest of bulges (and I really mean tiny...)?
Tim182 said:
Still have to... Will try that as soon as I have time.
How do everyone else's batteries look? 100% flat or the tiniest of bulges (and I really mean tiny...)?
Click to expand...
Click to collapse
Hi, look at this thread and read my last reply http://forum.xda-developers.com/showthread.php?t=2397950
I've found 5 threads with this problem, probably faulty motherboard and all of these people had Omega rom including me. But if Omega rom broke motherboard a lot more people would have this problem...so just a coincidence maybe? Also all these threads are not older than one month. I suppose that the only solution is reclamation.
Hi guys, I have bought a nexus 6P secondhand but I'm dealing with the problem of random shutdowns. After that it won't boot unless it is hooked to a charger. Some facts that I think might be of some influence or what I have tried:
- I bought it with Cyanogenmod 14.1, first day flashed back to stock 7.0 but kept my bootloader unlocked;
- Today I flashed an OTA update to 7.1.1;
- It happens random while using the phone, but I manage to reproduce the failure when using Google Camera and take pictures very rapidly (don't really know what the phone activity is at that moment)
- I've got a new battery on the way, might that be the issue?
- Battery status (percentage etc) doesn't make a difference. Might as well happen at 100%
- It doesn't happen while on the charger;
- It didn't happen in safe mode (didn't test this for too long though, but the fast camera action didn't kill the phone;
Does these descriptions make any bells rinkle? For me it looks like a defective battery but I'm happy to hear some expert about this
Thank you all for reading!
Yup, mine does the same thing. I believe it is supposed to be fixed with the new 7.1 release. Its the most inconvenient thing ever. I rarely takes pics now because nobody has a usb-c charger to get my phone turned back on. I'm running stock 7.0. It's not your battery.
Well that would kinda suck, I just updated to 7.1.1 and the problem is still there. Do you have a source for this thing?
I had the same random reboots.
I too suffered from random reboots in 7.1.1 dp2. They increased in frequency gradually. One night, it stuck in bootloop. Couldn't even boot into recovery. Browsed through threads here and reddit posts. All said the only solution was to RMA as without recovery nothing is possible. Huawei is replacing the motherboard as it's under warranty.
I just updated to 7.1.1 and I also can still confirm it's happen. I called huawei and they told me it was a software issue and it's not resolved and there is no fix other than to load 6.x on the phone. So basically, I we have a turd of a phone and nobody seems to want to fix it. Google told me it was a hardware issue and now Hauwei tells me it's a software issue. Maybe it's time for a new phone.
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
IM0001 said:
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
Click to expand...
Click to collapse
I loaded the image directly from google. I've never rooted or loaded a rom on this phone. I've only run factory images. I don't have the time to tinker like I used to.
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Well that was how I reverted from CM to stock 7.0, by using the flash-all function (even though the flash all didn't work, had to flash the seperate files, but result was the same). The 7.1.1 upgrade was with a OTA flash using ADB sideload because I was rooted and TWRP recovery was active, so the OTA update didn't work for me. To be honest, I don't think my problem is a software issue. Is there any 'deeper' software than the complete rom? Is the kernel flashed seperately?
IM0001 said:
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Click to expand...
Click to collapse
This fiasco has been happening for tons of people for weeks now, including me. Mine was just 2 weeks out of warranty, both google and huawei are pointing fingers at each other and nobody cares. I have tried all the methods possible, to flash different versions of pure factory image, nothing worked.
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
also face this problem previously and Huawei replace battery. just 1 week before the warranty run out
Sent from my Nexus 6P using Tapatalk
rmoney said:
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
Click to expand...
Click to collapse
Every charger worked for me. Now even carry a powerbank with me for when it lets me down outdoors I can get it powered on again. Plugging it in the PC also works just fine. Even a standard samsung charger (with micro-usb -> usb C adapter) works.
hah! Mine just started doing this!
I got the phone back from huawei for the 15% battery issue.. and it came back with this issue after going to 7.1.1
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Hafidel36 said:
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Click to expand...
Click to collapse
Mine is locked, on 7.0 I didn't have this issue.. on 7.1.1 It started.
on developer previews for it wasn't an issue either..
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
andrewnelson23 said:
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
Click to expand...
Click to collapse
That seems to be another know defect, you should look it up on here. Plenty of people are having that problem, but it is different from this thread.
I am having the same problem too! I was trying to raise this for two times on both XDA and reddit and no body seemed to care until you came up with this!
Mine randomly happens when taking photos with HDR+ and with the battery less than 50% (based on my observation). I replaced the battery by myself not long ago though.
Huawei says going back to 6.0.1 will fix the issue... and is blaming google, saying their pixel devices have this issue on 7.1.1 too.