Related
I was recently on vacation taking a "Photo Sphere" with my Nexus 4 and suddenly my phone just turned off. It didn't power down, it just suddenly was off. I felt the back of my phone and it was particularly hot right in the center of the phone. Since that event, my phone is highly unreliable when unplugged and will continue to immediately turn off when I either try to use the phone's camera, or sometimes: try to make a phone call, watch a video, and other random things. After the phone has powered off, it gets stuck in a reboot loop. The phone is bootable and works reliably when it is plugged in. When I am able to successfully reboot the phone, when plugged in, I can see that the battery has plenty of charge remaining. The phone will work for hours or minutes after it has been unplugged as long as I am doing very little with it.
Things I have tried so far have been rebooting into safe mode and formatting my phone with the stock Android 4.4.2 image. Both of these things have not worked out.
I'm trying to determine if I need a new phone if there is something else. Is there anything that would be indicated by a crash log and if so, how would I access that log.
Think it is a hardware issue
I can't help but think that this is a hardware issue. So, I just bought a new HTC One (M8). It is a fantastic phone. I am going to keep my glitchy Nexus 4 as a development/test device.
Hi eveybody,
Today, a problem I have been experiencing for months (years ?) became critical : I cannot charge my Nexus 10 (lollipop) anylonger. To make it as simple as possible, here are the symptoms :
1) When my tablet is ON, if I plug the micro-charger (or any other one, same), nothing happens, no charge ( and no PC recognize if connected to PC).
2) When the tablet is OFF, if I plug the charger, the tablet viber briefly (this is normal) - which means the tablet realize I plugged the charger - but the screen stay black, and after about 10 seconds, I can see a (very very) brief flash on the screen, then the tablet viber again (same like the first one !), and it restarts over an over again in a infinite loop. I never see anything on the screen, just infinite loop viber every 10 secondes. If I unplug the charger, then the next reboot the tablet will boot normally... Of course, when plugged and looping, the only way I have to power it off is a hardreboot (or unplug, wait it boots, and the poweroff.)
I have NO IDEA on what to do... In one hand it seems an hardware problem, on the other hand (due to the past experience, when it worked in a wierd way, see below) it doesn't. At this time, I still have 60% of battery, so things can be done (dunno, change to factory version of android ? but without PC...) ; when it will reach 0%, this is the end I guess. :crying:
Any help is welcome... thanks !
Here are the previous "version" of this problem, I had been experiencing for more than one year : exactly the same thing happened but only when the tablet was hot (after I used it). When it happened, I just waited for a whole night, and on the morning, I plugged, and it charged normally. Don't ask me why, this is completely mysterious for me, but that what happened : hot, didn't work, cold, worked...
Hello,
So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of
Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.
Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.
So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.
Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.
On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.
To skip any unnecessary questions, I will make a short QA.
Q: Did you tried to boot into recovery/bootloader?
A: yes, nothing happens
Q: Any sign of life on adb while connected to a pc??
A: no
Q: Is battery dead?
A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.
Q: Why don't you just buy a new phone?
A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.
Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?
A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.
So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.
In the best scenario, my almost 2 years old phone will revive.
Also, I have a multimeter - I can check the electricity. Just tell me what to check.
Thanks.
edbr said:
Hello,
So let me give you a brief so you'd know everything - a few days ago, I'm gonna call it day 1, I walked under light rain with the phone in my pocket, it worked until the night of
Day 2 - started to lag a bit, it was like I was running some heavy apps and like the ram was insufficient. Restarted the phone, everything seemed normal.
Day 3 - Phone went off while was browsing. So I have to make a note here. I was running cm13 with android m and twrp 2..something and there were occasional reboots by itself rarely prior to Day 1. Also, I was using a supercharger (or whatever it is called, it is a charger that charges faster) for about a month.
So when the phone went off while I was browsing, it started by itself and stuck on the android loading. I restarted, cleared dalvik and regular cache - still stuck on boot. Flashed many times, changed the recovery to twrp, and still was stuck on rebooting and occasionally it didn't turn on. There were random occurrences of errors on flashing roms, which never happened before (for example, "cant mount system or data"). Within the time passing by, the phone started not to turn on when I tried to. By this time rarely got stuck on the first boot screen saying with the text "Samsung S4". Yesterday, Day 4, the phone never turned on, except one time. I don't remember doing anything special. I just pressed and held the power button and it turned on, but went off shortly after the android boot animation appeared.
Also there was times on Day 3, when I was trying to boot into the system, it got stuck on the android booting animation.
On and prior to Day 3, while I was charging, whenever it is on or off - I had the indicator light for charging. Now when I plug it in to charge - nothing happens.
To skip any unnecessary questions, I will make a short QA.
Q: Did you tried to boot into recovery/bootloader?
A: yes, nothing happens
Q: Any sign of life on adb while connected to a pc??
A: no
Q: Is battery dead?
A: I don't think so, but actually I'm not that sure. When I connect a separate led light to it, the led lights up Whatever, if it was a faulty battery when I plug the phone on the charger, it should've worked fine.
Q: Why don't you just buy a new phone?
A: I was planning to buy a new one, but after just 4 months when I have to renew my contract. I don't want to buy a phone off contract.
Q: Are you stupid, if you can't manage to fix it by yourself, why don't you give it to a repair?
A: I truly believe that the professionalism of repairers doesn't exist in my country via old experiences with them.
So in the worst scenario I will loose time by trying to fixing it and for 4 months I will use my old android phone.
In the best scenario, my almost 2 years old phone will revive.
Also, I have a multimeter - I can check the electricity. Just tell me what to check.
Thanks.
Click to expand...
Click to collapse
Probabily the rain damaged a part of your hardware. Did you solve?
If the battery is dead, the phone won't work.
The battery needs to have at least a bit of charge in order for the device to work, even if it is plugged in.
If the battery can't hold the charge, and the device uses more power than it gets, it turns off. I speak from experience.
These devices don't seem to work without a battery. Power goes to the battery, and the phone takes the power from there. Power doesn't go straight to the phone.
Anyway, I don't think a bit of light rain hurts the devices, especially if it was in your pocket. I walked through rain with my device in the pocket many times and no problem.
It looks to me that the hardware is failing. I don't believe that a faulty battery can cause a bootloop. I also don't believe that the power button causes a bootloop.
What I suggest would be:
1) Try going back to stock ROM.
2) Maybe try to get an S4 with a broken screen and switch the motherboards.
Verizon V20, bought it new, no software mods.
I can't remember the error code, but if I shut down the phone and restart...for example, when I swap batteries, the phone gets stuck in "Firmware Update Waiting for any connection."
I found I can get to another menu by tapping the power button 7 times, but not much I can do but scan for wifi or shut down. After reading around, I found that I can start the phone just fine by shutting down, plugging in a charging cable, waiting for the battery icon, and then powering on.
So yes, so long as the phone is plugged in I can start it up, and I'm even using it now. But it's frustrating that I can't swap batteries on the fly, anymore, and I can get stuck without a phone. Happened 2x now, with a sick wife at home and I have no way to contact her.
What I know so far is that the phone is probably stuck in download mode. 2 things may have caused it.
1. I have been avoiding an update, up until yesterday, mostly just never a convenient time of day. Not sure if something got stuck in the boot command.
2. I was at the beach the other day before it happened. Phone wasn't near the water, but wouldn't surprise me if the charging port got sand or salt in it. I noticed it was harder to get a charging cord to lock in. Perhaps it thinks there's a data connection plugged in when there's not.
Ninety-9 SE-L said:
Verizon V20, bought it new, no software mods.
I can't remember the error code, but if I shut down the phone and restart...for example, when I swap batteries, the phone gets stuck in "Firmware Update Waiting for any connection."
I found I can get to another menu by tapping the power button 7 times, but not much I can do but scan for wifi or shut down. After reading around, I found that I can start the phone just fine by shutting down, plugging in a charging cable, waiting for the battery icon, and then powering on.
So yes, so long as the phone is plugged in I can start it up, and I'm even using it now. But it's frustrating that I can't swap batteries on the fly, anymore, and I can get stuck without a phone. Happened 2x now, with a sick wife at home and I have no way to contact her.
What I know so far is that the phone is probably stuck in download mode. 2 things may have caused it.
1. I have been avoiding an update, up until yesterday, mostly just never a convenient time of day. Not sure if something got stuck in the boot command.
2. I was at the beach the other day before it happened. Phone wasn't near the water, but wouldn't surprise me if the charging port got sand or salt in it. I noticed it was harder to get a charging cord to lock in. Perhaps it thinks there's a data connection plugged in when there's not.
Click to expand...
Click to collapse
Try to clean it out with the end of a safety pin
Sent from my LG-H918 using Tapatalk
I have a v20, and have the same issue, please help
Hello to all who view this,
I own an unlocked V-20 LG-H918 Its an unlocked T-Mobile variant that I use on Metro PCS, I have never had any issues, the phone works near perfectly.
I have a couple batteries which I switch out periodically, I just decided to switch to my backup battery to ensure that it was still okay, and charged... the phone refused to start, once I placed the new battery into it, instead it went to the "firmware updating screen waiting for a connection"
I was able to get the phone to start by pulling the battery and then plugging it into the wall PRIOR to starting it, and it started fine. however there is a reason I still use this outdated phone. I ENJOY IT. I would hate to end up replacing it, so i would like to know if there is a fix for this issue yet.
*for the record* I have not been able to ROOT this phone, I gave up about 10 months ago, and have had no issues, though as said I was unable to gain root acccess
So, I went for dinner tonight downstairs and when I came back I found my phone(A2017G) turned off with the notification light stuck on red.
Phone's old, bought it in July 2018(bought it resealed), though I had it changed via warranty after about two months due to the top speaker having the crackling/distortion issue. So I basically ended up with a brand new sealed phone for ~225$ at that time.
Back on topic though, plugging it in, it attempts to start up(vibrates and turns on), but displays the discharged battery icon (as if it ran out to 0 and shut itself off). Pressing the power button gives me the ZTE logo, the Unlocked boot-loader warning screen (which I usually bypass by pressing the power button again), then it blinks red three times and shuts itself off again. It's not booting in recovery either(running the nFound TWRP + crDroid ROM). However it won't charge. Tried multiple cables/charger combos, all act the same. it vibrates, displays the icon, then shuts off.
The device being bricked is pretty much out of the question right, unless it went DFU due to the battery? I've had it unlocked for the past 3 years at least...never had much issues with flashing (apart from the initial unlock which I wanted to be extra careful with but the drivers + EDL tool made it dead easy). And I haven't flashed or did anything of sorts recently.
Now, I'm 99% sure that the battery has finally given out, since the screen and presumably everything else work fine. The charging port has had no issues, always charged at QC amperage, no disconnects or anything, no "loosening" as I've had on multiple other phones. To be fair though , phone had started acting out a bit, slowing down and randomly closing apps...in the past few weeks and knowing the battery had already lost ~1000 mAh, I expected it to give out at some point. It's probably the safety mechanism built into it right?
The phone is old, as I said and according to Accu Battery, it's been at ~70% health for a while now.
Fortunately, a service shop in my country seems to have replacement batteries in an outside warehouse in Germany It should take around a week to deliver one to me, I'll change it myself. It seems to be original also. It's 25$, but I kinda wanted an opinion if I should buy it and replace it. I mean, for 25$...I've got nothing to lose, but hey, won't hurt to gather more info first.
I kinda don't want to replace the phone...since it still works fine and I still haven't found a replacement in the audio department. I've had people around me change their phones(to varying models, from low to high end) and tried each and every one of them(with Neutron/Hi-Res and enhancers off) and none sound as good as the Axon on the 3.5mm jack. The Axon simply works for me. Camera with GCam still slaps proper light pictures and documents, screen + sound is still fantastic for movies/anime at night when I can't be bothered to sit in a chair, calls are still crispier and louder than most phones today.