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.
Related
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.
My mother's nexus 5x has just died.
no fastboot no recovery nothing.
I have tried to charge it, but after more than an hour connected to the charger still nothing.
I checked that this charger works on my nexus 5x so it's not the problem.
I also tried to connect it to a computer, but the computer detected nothing.
the phone had 7.1.2 stock (either april or may security update I don't remember which one).
Anyone has an idea why it happened or how to fix this?
Thanks,
Orma
Wow, my 5X just died this morning. Wonder if it isn't just a coincidence or maybe some update like to the Fi app or something messed it up. So I'll post in case others have also had the same thing happen. The Fi app was last updated May 8, so that's not it. But maybe there was some other app or something updated that caused problems. Some of the core apps were recently updated and my phone tried to update some behind the scenes type app, but it didn't work. So I tried manually and it did work. Maybe I shouldn't have done that. Can't remember which app, but checking on my Google playstore apps, maybe it was Google Connectivity Services.
Mine was fully charged and I was using it while still connected to the charger after waking up in the morning. It just went black suddenly. I tried holding power button to shut it down, but it never made any vibration as if it was force shutting off. Power button and volume down button didn't work to shut down or boot either. The computer recognized it the first time I plugged it in showing Qualcomm HS-USB QDLoader 9008 has completed setup. But after that it would show as device unrecognized.
The only way I got anything to look like it was starting ok was by disconnecting the battery for a while. Then it started booting and then the screen just went black again. I unhooked the battery again for a while, reassembled, and plugged the phone in and the battery charging screen showed up, but then went black again without showing the filling up graphics.
So it seems to momentarily kinda act ok, but then soon goes black. Disconnecting the battery seems to reset it to a state where it can try again.
The battery read as 4.16 volts, so seems to be fully charged as I thought it was. I'm going to try doing the battery disconnect again, but I'm thinking this thing is done.
This may not just be a random thing. Several people on Google forums have the same sounding issue from yesterday or today.
https://productforums.google.com/forum/#!topic/nexus/iKXTmQ04YeM;context-place=forum/nexus
https://productforums.google.com/forum/#!topic/nexus/DINPhe1nb4c;context-place=forum/nexus
https://productforums.google.com/forum/#!topic/nexus/lWKu7eEfHhc;context-place=forum/nexus
By disconnecting the battery and then reassembling, I was able to get to the recovery menu. I chose Restart Bootloader, and after a few moments, go a screen showing the android character laying on the ground with a triangle with an exclamation point and "No Command" text at the bottom.
Holding power button and volume down got it to go back to the menu.
So I tried Recovery and it showed Google in white letters, then went black. Trying Start does the same thing.
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
kakah2011 said:
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Click to expand...
Click to collapse
Voicebox said:
By disconnecting the battery and then reassembling, I was able to get to the recovery menu. I chose Restart Bootloader, and after a few moments, go a screen showing the android character laying on the ground with a triangle with an exclamation point and "No Command" text at the bottom.
Holding power button and volume down got it to go back to the menu.
So I tried Recovery and it showed Google in white letters, then went black. Trying Start does the same thing.
Click to expand...
Click to collapse
if I open the phone to disconnect the battery will it void the warranty?
any one has any idea on why it happened?
my nexus 5x is totally fine
edit: I tried again to turn it on, but this time the notification light turned red, so i tried to connect it to the charger again and it seems to be alive now,
that's really weird but it turned on with 1% meaning that for some reason when I charged it yesterday it wasn't really charging
orma1 said:
if I open the phone to disconnect the battery will it void the warranty?
any one has any idea on why it happened?
my nexus 5x is totally fine
edit: I tried again to turn it on, but this time the notification light turned red, so i tried to connect it to the charger again and it seems to be alive now,
that's really weird but it turned on with 1% meaning that for some reason when I charged it yesterday it wasn't really charging
Click to expand...
Click to collapse
Sounds like you got lucky.
As far as I could see, there is nothing inside the phone that would indicate that you had opened it up. There's no glue, except under the battery, and maybe under the motherboard. But you don't need to lift those to disconnect the battery connector. However, it does require prying the back off and then unscrewing 10 screws. Then lifting off two pieces with stuff like the fingerprint sensor and speaker attached to them. If you make any dings in the plastic back cover while prying, they could see that. And the screws have lock tite on the threads so take some care to remove. I think I slightly stripped the top of one. So if someone really looked, they could see that. But otherwise, except for leaving fingerprints on parts or debris or whatever in there, I don't think they'd notice. I highly doubt they'd have someone go check for other than obvious signs of prying the back off. I'm 2 months past warranty so it was a non-issue for me.
Following someone's advice on the Google forum, I cooled the phone down in an ice bath (in a bag of course) and was able to get it to boot to recovery and even installed the OTA via adb. It then booted to the point of the 4 colorful circles and died again. After putting it in the freezer, it then returned to acting somewhat normal, as in it showed the battery charging graphic while off. The battery is about 1/2 full. But then I booted and it would get pretty far into the 4 circles spinning, then boot looped. So mine is bootlooping and I'm going to see if I can get Google to step up even though it is 2 months past warranty since I bought it from them. The Google people say to contact them with the bootloop problem. I hope they are quietly replacing them since this this appears to result from the last OS update for many people.
That other person was able to boot it and pull their pictures off it. But looks like mine is down for the count. I luckily had backed up pictures and most of my other stuff recently before I went on a trip. And I uploaded pictures while on the trip and pulled pictures off the phone right after the trip. But I've lost some info that I hadn't copied off the phone.
---------- Post added at 02:17 PM ---------- Previous post was at 01:59 PM ----------
kakah2011 said:
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Click to expand...
Click to collapse
I'm 2 months out of warranty, so I hope Google does something since I bought it from them and they seem to be providing some relief since this seems to be due to the most recent OS update. Or at least some of the people in their forums seem to imply they'll do something.
Well here you go. Explanation was at XDA all along. There's a class action lawsuit against LG for using solder that didn't withstand the level of heat or heating and cooling cycles. Started with the G4, but in April the 5X and other phones were added to the class action. So I guess I could try touching up solder points and get my phone maybe to start up, or try for warranty repair since they seem to have extended the warranty because of this lawsuit.
https://www.xda-developers.com/lg-bootloop-lawsuit-adds-nexus-5x-lg-g5-v20-case/
One guy at bottom of this thread has screen capture and says his 18 month old 5X shows as covered by warranty in their system.
https://productforums.google.com/forum/#!topic/nexus/PZrVO8g9Y9M;context-place=forum/nexus
Same here.
Nexus died after some freezes. After 7-10 failed boots it suddenly booted, just to freeze again after 1 or 2 minutes.
Tried every button combo with and without power plugged, no luck at all, just a dead brick with no signs of life at all.
Device was perfectly working till yesterday. No issues at all
Latest purenexus version. Everything was fine.
Don't get it.
Only thing what came to my mind was that we have been to the beach the day before. Had the phone in the backpack, but it went still really hot since the sun was strong.
But hey. Have been to definitiv hotter places last year in Croatia.
I thought i try the revive Motherboard in oven trick, since this oven thing already worked once for my laptop graphic chip which died also from overheating.
Put the MB in the oven for 12min at 200C.
No luck. Dead brick.
Any ideas?
Thanks for reading!
When my Nexus 5x died, LG replaced the motherboard and then everything was even much better than before.
quark-lepton said:
When my Nexus 5x died, LG replaced the motherboard and then everything was even much better than before.
Click to expand...
Click to collapse
Well. Got it from ebay.. No invoice.
Don't know if i can claim warrenty?
SchWeinSAuG said:
Well. Got it from ebay.. No invoice.
Don't know if i can claim warrenty?
Click to expand...
Click to collapse
LG has agreed to extend warranties on a case by case basis after they were sued. One lawsuit was dropped as a result, but the other remains. So they may be more willing than usual to fix it without proof of purchase, but only way to know is to call them.
http://www.androidpolice.com/2017/05/25/one-lawsuits-lg-nexus-5x-bootloop-dropped/
If you can't get any warranty help, then you can try the heatgun method. This seems to basically melt the solder again so that it'll work. If you're lucky, you get the one or few connections that are messed up.
Using a heatgun, I got mine from completely dead to where it performed normally for 9 hours. I thought I was back in business until it rebooted. Then it lasted a bit before rebooting, and every time would get shorter and shorter before rebooting. Now it is bootlooping at startup, but still alive. So I can adb the OTA back on there, clear cache and factory reset. And it charges. But it just bootloops.
https://www.youtube.com/watch?v=KQrsC2VZY0c
https://www.youtube.com/watch?v=wxQehPw4yPY
By they way, I tried a hairdryer for 30 seconds and it did boot to where I could unlock it, then it froze. The hairdryer just doesn't get hot enough to melt solder and only just heats things up to where there might be a temporary restoration of whatever connection or solder is broken. So I tried about 2 minutes and I could boot and swipe one screen left before it died. The heatgun took 1 minute 30 seconds to get it to where it would boot and work. I'm not going to go at it again since I have a chance at just getting a warranty swap if they extend it since I'm 2 months past the year coverage.
I just unlocked my phone and swiped down to check notifications. It immediately froze and the screen stayed on for awhile. Then the screen went black and I can't get the phone to start up. Tried holding power for a real long time and also volume down + power but still can't get it to start up. After messing with it for awhile I got it to briefly show the boot screen once and then once more I had it in the bootloader and I was able to scroll through the boot options but when I tried booting to recovery it died again. Connected to my computer the device manager sometimes shows it as "Qualcomm HS-USB QDLoader 9008". Any ideas if there's anything else I can try, or am I totally screwed?
I'm sorry to hear this, but is the known bootloop problem with hardware. It's caused by loosing solder balls on CPU. The best option tries to RMA, if you have a warranty.
That's what mine did. I was able to put it in the freezer and get a little life out of it, but never booted all the way. I used the hair dryer (following youtube videos on using a heat gun) heating of the CPU and motherboard and got some life out of it, but not a full boot.
So I bought a heat gun and got it to boot and for me to take most of the data off of it. Then it had issues, so I did a longer heating and it booted and acted normally. I thought it was actually fixed. But after 9 hours of acting like is was normal, it rebooted itself. It lasted for a while, then rebooted and lasted less time, and the cycle reduced really quickly to just bootlooping. I gave the heat gun one more try and pressed the CPU down with a wooden spoon to see if that made a difference, but it started the reboot cycle maybe 30 minutes into trying to set it back up. Google replaced mine though it was a few months past the end of the 12 month warranty since I bought it from them.
LG is extending the warranty on the 5X on a case by case basis. So you should give them a try.
Thanks guys. I did get it to boot into the bootloader a couple more times last night, but I wasn't able to get it to do anything meaningful. Whenver I tried booting to system or recovery it just hung up on the Google screen. I have it boxed up now and looks like it's going back to LG again.
UPDATE: Got an update from LG that my phone is undergoing repair. When I started the RMA and gave my IMEI they warned me the phone may not be under warranty. But according to the update they sent me they're indicating that it is covered under warranty - so apparently it's true that they're extending warranties to cover the hardware boot loop issues from faulty solder connections. Hopefully they'll even send my phone back with the SIM tray this time...
Heya, would someone be willing to help me root my LG G3 (D855)?
I've tried OneClickRoot before a few years ago and it worked great. However somewhere along the line it stopped working, I assume I installed an update that broke it.
OneClickRoot seems to work okay, no errors. But after it's done apps such as Root Checker say it's not rooted, and SuperSu is nowhere to be found.
It's 5.0, if anymore info is required just let me know.
I loath asking, but most of the guides that I come across seem outdated or have many other people saying it's no longer working.
Thanks for any help
Welp, I tried StumpRoot. Which stated that the phone was already rooted. Installed SuperSu from the play store and it told me there was no root detected.
Phone was on 95% battery, then it turned off and doesn't boot or charge...
Have I bricked it?
Have you tried doing a hard reset? Hold the power and volume down buttons for 10 seconds.
Another possibility (though unlikely to make much of a difference) would be to remove your battery for a few minutes, then put it back in and try booting.
M0rtiferrimus said:
Have you tried doing a hard reset? Hold the power and volume down buttons for 10 seconds.
Another possibility (though unlikely to make much of a difference) would be to remove your battery for a few minutes, then put it back in and try booting.
Click to expand...
Click to collapse
I tried everything I can think of. Best I managed to do was get it to boot twice by doing a combo of charging, taking the battery out, and then holding the power button for 10 seconds. But after about 30 seconds of being on the lock screen it blue screens. Most of the time it only shows the LG screen then blue screens.
It's either the mobo or the battery, I'm 99% certain it's because I left it on charge every minute I was home from the moment I bought it. I'll buy a spare battery and see if that works. It's no biggie though, I'm upgrading to a LG G6 on Tuesday.
If you've got any other ideas on the blue screen issue I'd be happy to try solutions. Thanks
I can think of 3 more things you can try:
1. Get the phone into recovery mode. If you have TWRP installed you can wipe the storage, flash a new ROM, and save the phone.
2. Get the phone into download mode and flash stock firmware using LGFlashTool.
3. Your phone's soldering may have just gone bad coincidentally. This is a common issue with G3's as they get older and generally signals the end of the phone's life. You can try reflowing the solder by baking the motherboard in the oven around 500 degrees for 15 minutes holding a hair dryer over the NAND while applying pressure for 2 minutes. I've heard of this extending people's phones' lives anywhere from 3 months to 0 months. As a last resort, it's worth a shot.
Edit: took a second look at this thread: https://forum.xda-developers.com/lg-g3/general/g3-hardware-problems-solved-bsod-screen-t3597086
Apparently a hair dryer is good enough. For sure a hot air rework station is better. Either way, consider this a last resort method that has a significant chance of rendering the phone completely inoperable.
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.