hi all.
i've had a KF since christmas and it's been running an old build of ClassicNerd ICS for while (you'll understand why it's an old build in a second). I took my KF on spring break in Florida in April and that's why my problem started. I took my KF on a boat to an island, the water wasn't rough on the way out so it wasn't a big deal. On the way back to shore, however, the water got ridiculous and water was splashing over the side of the boat (i'm really not kidding, the boat was about to break in half from hitting the water so hard). With the water being so crazy, i wrapped my KF (and phone) in a plastic bag and stuck it in a part of the boat that was covered, hoping that it wouldn't get wet. once we returned to shore, i checked my phone and KF and both were working just fine. the battery ran down on my Kindle and ever since then i've had a problem where it won't charge. I cana plug in the charger, the FFF screen will pop up for about 2-3 seconds, and then it turns off again. The Kindle heats up a bit during this process as well. i've let it do this over night before hoping that it would charge but it never does and just keeps repeating the power on, power off, power on process. sometimes the screen stays on for longer, but never enough time for me to boot into TWRP or for the system to boot.
might anyone know what could be causing this?
What version of fff did you have?if older than 1.4a likely your battery died http://forum.xda-developers.com/showthread.php?t=1623244
Related
On the occasion, my phone acts all wonky. This morning it was stuck on a boot loop for quite some time, but it got fixed. This morning it was plugged in and it constantly shut down and rebooted for a few hours. Sometimes when it's plugged in the touch screen is all wonky, and I can't do anything. I'm due for an upgrade some time near my birthday, but 6 days is a while to wait with a badly working phone. This morning I tried to write down some of my friends numbers because I figured this phone was on its last legs, but I only got 1 number before the phone shut down. Then I got another number, but that was it. It shut down again so I plugged it in. I drop my phone a lot too, and it recently started doing this thing where when it gets dropped, it turns off. Usually it would turn on again by itself, but one time it didn't. My dad had to hold the lock button for a few minutes just to boot it up. I might get an otterbox case for my next phone, and it's probably gonna be either another HTC or an iPhone. Also, what can I do for the time being to help keep my phone as OK as it's gonna get? Thank you in advance.
Best thing to do? Don't drop your phone. I had a Galaxy SIII and every time it had a slight shake, the display would freeze and go all fuzzy. The issue was a loose display cable that wobbled a lot. You may want to check your phone for any damaged/loose cables since it's been dropped too many times.
My Dad dropped his phone accidentally onto hardwood floor and worked for 2 weeks. Yesterday the phone was in boot loop and now doesn't boot at all. The phone cannot charge at all nothing no red light indicator. This phone is as Dead as a dodo. If only i can get into download mode. Any suggestions?
Our home has a hardwood floor and the phone fell onto the ground. The distance was 1.4 Meters it was completely working until while my dad was using it it turned off and was in a boot loop. then the phone wouldn't boot at all.
I'm trying to at least get data off of it however the phone is completely stock (unlike my LG G3 he is using today) so i cannot use ADB cannot boot to recovery as well. Computer doesn't recognize phone at all.
Meanwhile i may do the following:
I may get a new battery (original of course)
maybe a USB Jig ( I may buy one off Ebay or ask my uncle to make me an homemade one since he is an electrician there is an xda post about how to make one)
open it up to see if any damage to circuit since it has been dropped
Hopefully I can fixed this any suggestions are welcome since the phone is Out of warranty.
Thanks
SHOTTZZ99
I don't think that a physical damage due to a dropping can wait 2 weeks for showing affect.
Perhaps if it was falling into water, you could say that a corrosion slowly spreaded until harming the core components.
Perhaps it's no more than a coincidence, and you ran into the famous sudden death syndrome (aka "sds").
I'm wondering, what android version did the device have before the brick?
MeiR_ct said:
I don't think that a physical damage due to a dropping can wait 2 weeks for showing affect.
Perhaps if it was falling into water, you could say that a corrosion slowly spreader until harming the core components.
Perhaps it's no more than a coincidence, and you ran into the famous sudden death syndrome (aka "sds").
I'm wondering, what android version did the device have before the brick?
Click to expand...
Click to collapse
It had 4.4.2 kitkat for a while. i tried changing phone and gets a little warm. I'm buying a new battery today to see whether it is a battery issue since i had this battery for over 3 years! (crikey)
Like MeiR_ct i think you coincidently ran into SDS.
Definitely try the things you mentioned
See if the power button is stuck. Did you say your dad switched it off? Sometimes some gentle tapping might help release the button if it is stuck/damaged as a result of the fall.
Also try pulling battery and holding power button for 30 seconds, put battery back in and see it it comes on. If no, then same routine for 1 minute, etc up to 3 minutes or so.
Hello everyone.
I have a 100% stock nexus 5X, never did any modification to it. One or two weeks ago I installed the official Android 8 OTA. Some hours ago while I was looking at some options of the google assistant (the one about enabling geolocalization-based tabs) my device froze and then shut down but didn't rebooted automatically. I wasn't able to boot it again since after nor I was able to boot in fastboot mode. When this happened the battery should have been at least at 50% of charge. If I connect it to the wall plug adapter it doesn't show the usual charging animation. The only result I was able to accomplish is that, while it was plugged in, I tried to boot in fastboot mode and it displayed the charging icon. I then unplugged it and tried to boot it but I failed and I wasn't able to reproduce that. Currently it's plugged in the wall-plug adapter and I can tell by the noise that it makes that is probably charging, but it doesn't display the usual charging animation. Any suggestion about what I could do?
That is what my phone did before it eventually bootlooped. It died while in use and did not bootloop until after recovery efforts. When it wouldn't start at all, I tried freezing/ice bath, and it would then actually boot into recovery and even got to where I could use adb to reinstall the OS. But it never would boot until I used a heat gun on it. After I recovered my data, it did eventually finally bootloop. But the dying and not turning on was due to the same cause as the boot loop.
This was back in June on 7.1.2, so perhaps your phone is doing something related to the OS update, but it really is acting just like mine did when it was dying.
Voicebox said:
That is what my phone did before it eventually bootlooped. It died while in use and did not bootloop until after recovery efforts. When it wouldn't start at all, I tried freezing/ice bath, and it would then actually boot into recovery and even got to where I could use adb to reinstall the OS. But it never would boot until I used a heat gun on it. After I recovered my data, it did eventually finally bootloop. But the dying and not turning on was due to the same cause as the boot loop.
This was back in June on 7.1.2, so perhaps your phone is doing something related to the OS update, but it really is acting just like mine did when it was dying.
Click to expand...
Click to collapse
Could you please give me more info about the freezing/ice bath process? You just put it in a freezer for some time? For how long?
Update: I was able to boot into fastboot mode, then I selected recovery mode and it displayed "GOOGLE" for a while, then powered off
Update 2: keeping the power button pressed for longer than usual it displayed "GOOLGE" for a while as usual during boot, but then powered off.
My Nexus 5x has the exact same problem.
Installed new App-Updates, for example the Facebook Beta, and after browsing on FB my phone died.
Android 8 September Patch, Locked Bootloader, 100% Stock
GTP95 said:
Could you please give me more info about the freezing/ice bath process? You just put it in a freezer for some time? For how long?
Click to expand...
Click to collapse
Some background. If this is the infamous boot loop issue, it is hardware based where possibly some solder is cracked around the CPU or some joints came apart, or something similar. The idea behind cooling (or heating the motherboard in say an oven), is that the contraction or expansion closes the crack for a limited amount of time. You then may have a chance to backup photos or data, reinstall the OS, etc. However, it does not fix the underlying problem, and will go back to dead when it warms up. However, if you are able to unlock the bootloader, you could try to install the fix that disables the big cores. If that works for your phone, then you would have a usable phone, but at reduced performance.
That fix in this thread below, though there is also a thread about doing it with a locked bootloader. Though I have never looked through that one so don't know about it.
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
About the freezing: Some people have just put it into the freezer for some period and then turned it on while inside the freezer. Then waited to see if it would boot. I tried this inside a ziploc bag because otherwise it got condensation when I pulled it out. I ended up just freezing first, then putting it inside a ziploc bag in an ice bath since that kept it cold and then I could bring it to the laptop and plug it in and re-installed the OS. Just freezing didn't get mine to boot, but other people have claimed to have gotten their phone to boot and yank data off after just freezing it.
You put it into the freezer until you think it has cooled down the motherboard since that's where the cracks would be. So that's maybe half an hour in the freezer or more depending how cold the freezer is. About half an hour worked for me since the refrigerator is only 2 years old and the freezer is really cold.
I did manage to reinstall the OS after freezing/ice bath, but the phone didn't actually fully boot until I used a hair dryer on the motherboard. But it then instantly died after unlocking the phone. Only using a heat gun on the motherboard got it to where I could boot and take data off of it. I even got it to work normally for 9 hours by using a heat gun since they are hot enough to actually melt solder.
The method to disable the big cores wasn't around back then, but I think I might have been able to get it on there if it had been.
Voicebox said:
Some background. If this is the infamous boot loop issue, it is hardware based where possibly some solder is cracked around the CPU or some joints came apart, or something similar. The idea behind cooling (or heating the motherboard in say an oven), is that the contraction or expansion closes the crack for a limited amount of time. You then may have a chance to backup photos or data, reinstall the OS, etc. However, it does not fix the underlying problem, and will go back to dead when it warms up. However, if you are able to unlock the bootloader, you could try to install the fix that disables the big cores. If that works for your phone, then you would have a usable phone, but at reduced performance.
That fix in this thread below, though there is also a thread about doing it with a locked bootloader. Though I have never looked through that one so don't know about it.
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
About the freezing: Some people have just put it into the freezer for some period and then turned it on while inside the freezer. Then waited to see if it would boot. I tried this inside a ziploc bag because otherwise it got condensation when I pulled it out. I ended up just freezing first, then putting it inside a ziploc bag in an ice bath since that kept it cold and then I could bring it to the laptop and plug it in and re-installed the OS. Just freezing didn't get mine to boot, but other people have claimed to have gotten their phone to boot and yank data off after just freezing it.
You put it into the freezer until you think it has cooled down the motherboard since that's where the cracks would be. So that's maybe half an hour in the freezer or more depending how cold the freezer is. About half an hour worked for me since the refrigerator is only 2 years old and the freezer is really cold.
I did manage to reinstall the OS after freezing/ice bath, but the phone didn't actually fully boot until I used a hair dryer on the motherboard. But it then instantly died after unlocking the phone. Only using a heat gun on the motherboard got it to where I could boot and take data off of it. I even got it to work normally for 9 hours by using a heat gun since they are hot enough to actually melt solder.
The method to disable the big cores wasn't around back then, but I think I might have been able to get it on there if it had been.
Click to expand...
Click to collapse
Thanks for your detailed answer, I would never have thought about disabling big cores. Anyway I checked and found out that my phone is still under the warranty protection (less than two months left, I was lucky!) so I decided to take the "official way" and bring it to LG's assistance. I've been told I would have to wait about 20 days, in the meantime I'm using my old Galaxy S3. I hope they will fix it so I don't loose anything but I will be happy anyway if they replace it because I have a backup of most things. I wonder though if with so powerful processors with so many cores this is an issue other phones are facing too and how much this is common.
GTP95 said:
Thanks for your detailed answer, I would never have thought about disabling big cores. Anyway I checked and found out that my phone is still under the warranty protection (less than two months left, I was lucky!) so I decided to take the "official way" and bring it to LG's assistance. I've been told I would have to wait about 20 days, in the meantime I'm using my old Galaxy S3. I hope they will fix it so I don't loose anything but I will be happy anyway if they replace it because I have a backup of most things. I wonder though if with so powerful processors with so many cores this is an issue other phones are facing too and how much this is common.
Click to expand...
Click to collapse
That is the best way to deal with it. They replace the motherboard and I'm guessing it is done as a complete unit, so I think you will lose all your info that isn't already saved. Though I'm not sure since I received a replacement from Google when mine died.
This same issue came up on the LG G4 and another LG phone that came out at the same time as the Nexus 5X. So hopefully LG figured out what the underlying issue is and will not make the same mistake again. But I will not be buying another LG phone for a long time. As an example, I would have considered the large version of the Pixel 2. But that phone is made by LG, so I just went with the Moto X4 and I'll decide next year if I stay with Fi or switch back to a regular provider.
I got my charging port a little wet today. No submersion, just got splashed. Ever since then, for the last few hours the phone has been shutting down randomly. Once it went to the factory flash mode which was interesting. Giant blue circle with a "waiting for connection, do not power down during flashing" warning. That was interesting. The phone intermittently will try to take a charge but will shut down after about 10-15 min of charging.
I'm sure it'll be fine once it fully dries out overnight but still, a word of warning to those who get theirs wet. I never had this issue with my note 8 which I would weekly take in the pool for my daughter's swim lessons which meant for about 30 minutes it was fully underwater 2-3 ft. With this just taking a splash and misbehaving this badly, I don't even want to try that.
I put mine in the filled up sink just to scare my wife, and no issues FWIW...
Sent from my [device_name] using XDA-Developers Legacy app
arcanexvi said:
I got my charging port a little wet today. No submersion, just got splashed. Ever since then, for the last few hours the phone has been shutting down randomly. Once it went to the factory flash mode which was interesting. Giant blue circle with a "waiting for connection, do not power down during flashing" warning. That was interesting. The phone intermittently will try to take a charge but will shut down after about 10-15 min of charging.
I'm sure it'll be fine once it fully dries out overnight but still, a word of warning to those who get theirs wet. I never had this issue with my note 8 which I would weekly take in the pool for my daughter's swim lessons which meant for about 30 minutes it was fully underwater 2-3 ft. With this just taking a splash and misbehaving this badly, I don't even want to try that.
Click to expand...
Click to collapse
That's very odd. How long after the port got wet did you plug in a charger? It sounds like something happened when charging possibly. Getting this phone wet should not cause any issues like you described. Unless maybe the port was still a little wet when it was plugged in.
js042507 said:
That's very odd. How long after the port got wet did you plug in a charger? It sounds like something happened when charging possibly. Getting this phone wet should not cause any issues like you described. Unless maybe the port was still a little wet when it was plugged in.
Click to expand...
Click to collapse
A couple hours but it was doing it before I plugged in a charger (and after). It's been fine since last night though.
Was it fresh water or salt water?
Sent from my Pixel 2 XL using Tapatalk
Fresh out of the tap
Watch TV while taking a shower and no problems. Aaahh... Taking a shower and watching TV, so nice
Mine got water splashed too, at first I thought it was nothing because it kept working perfectly, but then I tried to plug in my headphones (with the usb-c/3.5mm adaptor) and they were not working properly. They function, but it's like if certains sounds were not capture by it, like voices. Is it possible that it's just still a little wet, and I need to dry the port out somehow? Or is it that maybe one of the pins on the USB port are now broken and I need to replace it?
Whilst hiking, we had to wade our way through a body of hip-level still freshwater. in my oblivion, I forgot to remove my phone from my pocket. As soon as I realized that my phone was immersed, I took it out of the water immediately and shut it down.
After returning home (~8 hours later), I placed the phone in silica gel for 12 hours and tried to boot the phone. It booted till the mid-boot PIN prompt. However, the touch didn't work. Seeing this, I shut the phone down again and placed it in silica for another 8 hours. The next time I booted the phone, I could use the touch to enter the PIN, but the boot seemed to abruptly stop during the boot animation and restart.
I approached an authorized service center in my city and asked them to diagnose the problem. After no more than 5 minutes, I was told that my motherboard was damaged and that it had to be replaced with a new one.
Is there any chance or recovering my phone? It's in top-notch shape since it's been just more than one year since I've bought it.
Not rooted, no unlocked bootloader. Simply stock firmware.
Is there any hope for my phone?
rahulkulhalli said:
Whilst hiking, we had to wade our way through a body of hip-level still freshwater. in my oblivion, I forgot to remove my phone from my pocket. As soon as I realized that my phone was immersed, I took it out of the water immediately and shut it down.
After returning home (~8 hours later), I placed the phone in silica gel for 12 hours and tried to boot the phone. It booted till the mid-boot PIN prompt. However, the touch didn't work. Seeing this, I shut the phone down again and placed it in silica for another 8 hours. The next time I booted the phone, I could use the touch to enter the PIN, but the boot seemed to abruptly stop during the boot animation and restart.
I approached an authorized service center in my city and asked them to diagnose the problem. After no more than 5 minutes, I was told that my motherboard was damaged and that it had to be replaced with a new one.
Is there any chance or recovering my phone? It's in top-notch shape since it's been just more than one year since I've bought it.
Not rooted, no unlocked bootloader. Simply stock firmware.
Is there any hope for my phone?
Click to expand...
Click to collapse
Leave it in silica gel for longer?
I dropped mine in the sink a couple of months ago, but I was lucky. I didn't even bother turning it off, I just plugged in my hot air gun and let it blast the phone for 1 hour. At first the jack and the USB ports weren't working but they were fine after the hot treatment. I was lucky
XDRdaniel said:
Leave it in silica gel for longer?
I dropped mine in the sink a couple of months ago, but I was lucky. I didn't even bother turning it off, I just plugged in my hot air gun and let it blast the phone for 1 hour. At first the jack and the USB ports weren't working but they were fine after the hot treatment. I was lucky
Click to expand...
Click to collapse
Sure thing. What if it doesn't work, though? I've voided my warranty anyways, so I can play around with the software; what do I have to lose? The thing is, my phone is COMPLETELY stock - A locked bootloader, and a mid-boot pin. I'm currently downloading the software required for the mega unbrick guide and I've got universal ADB installed. Also, I can reboot into recovery.
Hope this helps.
rahulkulhalli said:
Sure thing. What if it doesn't work, though? I've voided my warranty anyways, so I can play around with the software; what do I have to lose? The thing is, my phone is COMPLETELY stock - A locked bootloader, and a mid-boot pin. I'm currently downloading the software required for the mega unbrick guide and I've got universal ADB installed. Also, I can reboot into recovery.
Hope this helps.
Click to expand...
Click to collapse
Water damage will not corrupt the software. It is the hardware (mostly contacts) that is damaged. You can dismantle the phone and clean it with cleaning agents for electronics. Dry it for a day, then assemble and then try to boot. The various contacts are important. Clean them with extra care.