Hey everyone. I've been having a pretty bad past two days. Yesterday, my sink flooded, and my Nexus 5 was on the counter, leading it to get water damaged. I made the mistake of trying to turn it on to see if it still worked, and I think this hurt it a bit. I stopped after two or so times of trying to turn it back on and I put it in a tupperware container with rice to suck the moisture out of it. Well, it's been twenty four hours, and when I tried to turn it on, it didn't work. I plugged it in to my computer via USB, and the red light at the bottom started flashing, showing me that it still worked, and just need to charge. Earlier, I had a doctors appointment, so I decided to plug it in to the car and let it charge from there. I tried turning it on, and it loaded up normally, but since the battery was so low, it died again in about a minute. From then on, I let it charge, assuming that it would turn on like normal again, but now it's just getting stuck on the 'Google' screen that comes up before it loads. I don't know why it worked the first time but it's not working now. Also, when I plugged it into the computer, a little notification would pop up telling me that the Nexus 5 is connected to the computer and I could go through the files and such, but now it just tells me it's an unidentified USB, but it still charges the phone, and the little battery charging animation comes up on the phone and everything.
I've seen a lot of 'factory reset' solutions, but I want to see if anyone has an idea that doesn't require me to erase all of the stuff on my phone. Thanks for any feedback, whether it works or not, I really appreciate that you'd take the time out to help me! This phone is so great, and I would really hate to have to factory reset it.
EDIT: I went to http://forums.androidcentral.com/nexus-5-rooting-roms-hacks/352008-guide-nexus-5-recovery.html this guide, and I noticed that when I opened up recovery mode and it gave me the clear cache/factory reset/etc options, there is a yellow text prompt that says:
E: failed to mount /cache (No such file or directory)
E: Can't mount /cache/recovery/log
E: Can't open cache/recovery/log
E: failed to mount /cache (No such file in directory)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (No such file in directory)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file in directory)
E: failed to mount /cache (No such file or directory)
I dont know what this means, but it said this before I wiped the cache partition, and still says it even after I did it. I also tried to reboot the system, but it looks like it had the same problem. Hope this might help.
I've seen a lot of 'factory reset' solutions, but I want to see if anyone has an idea that doesn't require me to erase all of the stuff on my phone. Thanks for any feedback, whether it works or not, I really appreciate that you'd take the time out to help me! This phone is so great, and I would really hate to have to factory reset it.
EDIT: I went to http://forums.androidcentral.com/nexus-5-rooting-roms-hacks/352008-guide-nexus-5-recovery.html this guide, and I noticed that when I opened up recovery mode and it gave me the clear cache/factory reset/etc options, there is a yellow text prompt that says:
E: failed to mount /cache (No such file or directory)
E: Can't mount /cache/recovery/log
E: Can't open cache/recovery/log
E: failed to mount /cache (No such file in directory)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (No such file in directory)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file in directory)
E: failed to mount /cache (No such file or directory)
I dont know what this means, but it said this before I wiped the cache partition, and still says it even after I did it. I also tried to reboot the system, but it looks like it had the same problem. Hope this might help.
Last edited: