Database Info

[Q] [i9023] Water damage - USB won't connect to PC.

Hi there,
My Nexus S (i9023) phone recently fell into a water bucket and I immediately pulled it out.
Not much damage was done to it except of one thing: after I put it in a bag of rice like stated on the internet for overnight, and then plugged it in again to the charger, it seems like something was different.
When I plug the phone to the AC power - phone DOES charge, but nothing else happens.
It doesn't turn on screen and informs "charging", and doesn't have the "charge when phone is off" option anymore. Instead it would just turn the phone on.
Also, when connecting the phone to the computer nothing happens, it's just charging the phone! can't mount USB anymore
I took the phone to a lab which handles these cases. They replaced the USB port and cleaned all the corrosion. They said it's fixed now, and indeed the USB port is new.
But then after coming back home it's still the same.
I'm sick of being dependant on other people and would like to fix it myself.
Any clue which part of my phone was fried? Where can I get it?
Thanks!
-zeek

Are u rooted?
Try a different ROM. Maybe one ur ur backups.
If it still does connect then it has to be the ROM assuming ur computer has the proper drivers still.
Good luck
Vs Nexus S 4G

Thanks!
Thank you!!!
Problem solved after I loaded one of my backups.
Any explanation to that? even when the phone was turned off it couldn't charge it in off mode and now it can.
How come it's a software issue?
Thanks!

I can only guess that ur ROMs kernel had a "fast charge" option. If so this doesn't allow computer connection. How it got switched to that option... who knows .... maybe the sudden power surge.
If not that, then ... strange things happen when a phone get wet.. the sudden power surge could have changed the power output causing CPU adjustments... who knows.
I'm just happy it worked for u.
I'd recalibrate ur battery asap.
Good luck
Vs Nexus S 4G

Hi, the same thing happened to me, only it wasn't a bucket, it was a pool, and changing the ROM didn't work (I've flashed at least three different ROMs since then, kind of hard when the USB port doesn't work but eh, what can you do).
Also, it's on a Gio, not a Nexus S, but the principle should still be the same, yes?

Charging problem on stock ROM?

Hello,
My wife and I both have a Nexus S, which are both almost 2 years old now. She has always been running stock ROMs and only updated when there was an OTA update available. No rooting, no nothing I however tried as much as possible and currently running SlimBean 4.2.2 Build 5 :good:
Since 3 days now, the battery in my wife’s phone isn’t charging anymore. I tried the following:
- Use my charger and an old Nokia charger: doesn’t work
- Put my battery in her phone: doesn’t work
- Put her battery in my phone and charge mine: works like a charm
The last one’s the solution for now: at night I charge one of the batteries in my phone and put it in hers, while at work I charge the other battery from my PC via USB.
Based on my ideas I’d say that something in the USB-port on my wife’s phone might be broken. However, there are 2 phenomena that I find rather strange:
- When her phone says it’s time to connect the charger, I take out the battery and put it in my own phone. I power up and the battery level reads somewhere between 60 and 80 percent
- When I power off her phone and connect the charger, I’d expect to see either the charging symbol or nothing. But none of these: it powers up as soon as I connect the charger
I don’t know about the first issue, but could it be the battery stats might be corrupted? The last issue makes me believe that the USB-port is at least not completely disconnected/broken.
Has anyone got an idea what the issue could be? I wouldn’t want to work on her phone rooting it if it isn’t necessary, but on the other hand she might be better off in various other ways as well
Thanks in advance,
Pieter

stalensnuitje said:
Hello,
My wife and I both have a Nexus S, which are both almost 2 years old now. She has always been running stock ROMs and only updated when there was an OTA update available. No rooting, no nothing I however tried as much as possible and currently running SlimBean 4.2.2 Build 5 :good:
Since 3 days now, the battery in my wife’s phone isn’t charging anymore. I tried the following:
- Use my charger and an old Nokia charger: doesn’t work
- Put my battery in her phone: doesn’t work
- Put her battery in my phone and charge mine: works like a charm
The last one’s the solution for now: at night I charge one of the batteries in my phone and put it in hers, while at work I charge the other battery from my PC via USB.
Based on my ideas I’d say that something in the USB-port on my wife’s phone might be broken. However, there are 2 phenomena that I find rather strange:
- When her phone says it’s time to connect the charger, I take out the battery and put it in my own phone. I power up and the battery level reads somewhere between 60 and 80 percent
- When I power off her phone and connect the charger, I’d expect to see either the charging symbol or nothing. But none of these: it powers up as soon as I connect the charger
I don’t know about the first issue, but could it be the battery stats might be corrupted? The last issue makes me believe that the USB-port is at least not completely disconnected/broken.
Has anyone got an idea what the issue could be? I wouldn’t want to work on her phone rooting it if it isn’t necessary, but on the other hand she might be better off in various other ways as well
Thanks in advance,
Pieter
Click to expand...
Click to collapse
Being completely stock and never modified, I'd say it's the usb.. Have you tried the OEM connector for the computer?..
1. I would take it to a shop
2. You could also try cleaning the contacts
3. May do nothing but if you take the battery/sim out and hold the power button for a minute, this is supposed to completely power down the phone, and then reinstall sim/battery and reboot..
4. Use this as an excuse to modify her phone (telling her that you can put it back to stock if she doesn't like it)..

This happens a lot on my phone, .. Be careful with my solution, I hope it works for you..
Basically inside the usb port on the phone, there is a flat pin. On my phone, this pin ends up bending downwards towards the bottom of the phone.. What you could do is get a very thin knife or a swiss army blade and just try and lift the flat pin in order to make it locate in the center of the usb port (hole) .. The issue being the pin doesnt connect with the charger ..
I hope you understood this
PS: Don't snap it !

[Q] What just happened to my phone?

This is very strange. I have my phone completely normal. It's been charged and is running fine. The phone is unlocked, rooted, and running CM10.1. I decide I want to use an external controller to play one of my games. It is a Xbox 360 wireless controller. I load up Beach Buggy Blitz on my device, close all the other apps, and return to my home screen. I then plug in the wireless adapter for the controller via USB OTG. I have used this controller fine on my N7 and maybe even my SGS3 at one point. Everything seems all good and normal. So, I plug in the micro USB into my phone and wtf. It just completely and instantly shuts off and the screen goes pitch black. I mean as soon as I plugged it in, there was an instant and total shutdown of the device. I thought this was weird, so I unplug the USB adapter and try to turn on my device. No dice. I remove the battery and try again. No dice. I hold down the power button for a really long time. I charge the device. Nothing. I charge the device with and without the battery, while pressing and holding the power button and with different button combinations multiple times. Nothing. The device will just not respond in any way. I even tried my N7 charger, but it doesn't work. The USB port feels fine and it seems like the chargers are going in just fine. I'm leaving the device the charge overnight with the battery in it, but I don't know if even that will work. I can't believe this happened. I just plug in a USB and it seemingly kills my device. That doesn't make any sense. Anyway, what should I try? What if it doesn't turn back on? I did buy Squaretrade warranty that covers accidental stuff and I've never made a claim with them yet. Any help will be appreciated, thanks!
TL;DR: I plugged Xbox 360 wireless controller adapter into my completely normal GS3 rooted and unlocked with CM10.1 via USB OTG and now the device won't respond at all despite several and varied attempts.

Your Power Management IC self destructed. It's a common occurrence with S3's. Some devices overload it and it kills the phone.
It should be covered under basic warranty through Verizon, and they'll ship it to you overnight. I'd recommend not mentioning your usage of the OTG though. I've had to get a replacement for the same reason.
Just tell Verizon that your phone won't power on, charge, or show any signs of functionality whatsoever.

themusicmonkey said:
Your Power Management IC self destructed. It's a common occurrence with S3's. Some devices overload it and it kills the phone.
It should be covered under basic warranty through Verizon, and they'll ship it to you overnight. I'd recommend not mentioning your usage of the OTG though. I've had to get a replacement for the same reason.
Just tell Verizon that your phone won't power on, charge, or show any signs of functionality whatsoever.
Click to expand...
Click to collapse
I kind of figured it would be some sort of power issue. But man, completely killing a normal device just by plugging in something for just a second is insane. So does this mean I get a completely new phone (same model) when I send my old one in? Can I retrieve any data still on the device? I hope I have a decent Titanium still on my SD card. Will I have to re-unlock, re-root, and re-flash my ROM? That would be annoying seeing how I haven't unlocked or rooted my device in several months. Thanks.

Dillon610 said:
So does this mean I get a completely new phone (same model) when I send my old one in? Can I retrieve any data still on the device? Will I have to re-unlock, re-root, and re-flash my ROM?
Click to expand...
Click to collapse
They send a refurbished phone, Certified Pre-owned or something, and you keep the back cover, cards, and battery. You'll have to send your phone back in the box, or they'll charge you. Call them ASAP, because I pre-ordered the phone, and my manufacturer warranty expires on the 4th. If they try to charge you, remind them that it's covered under that.
I don't know of a way to get any data off of it, other than physically hacking/repairing your phone of course. If you could do that, you could also fix it yourself
You will have to do all rooting and flashing again, but here's a good tool to root it. http://forum.xda-developers.com/showthread.php?t=2332825

Having some issues with Samsung Galaxy S6...

Hey there,
I'm wondering if there may be a problem with my Samsung Galaxy S6 and I wanted to get some opinions before I try one last thing and fully reset it.
I've had the phone since April last year and for some reason the battery life has never really been good anyway. This isn't the main reason I am posting though as only recently I noticed a different issue when I tried to transfer some files onto the phone.
I was trying to use the cable that comes with the phone to charge it, and I've done so before when I've transferred files before from my Macbook. However, that time before I also found it very difficult to detect the phone and kept having to unplug it and plug it back in before it would see it. I was using the software Android File Transfer. Last night I could literally not get it to see my phone whatsoever... I plugged it into the computer and it would charge but it literally could not detect a connected device.
So here's where it gets frustrating as I spent the next two hours trying to fix this issue. I tried searching for a solution online which is why I'm now here after everything as all that I tried didn't work. I tried switching to SmartSwitch (and uninstalled AFT first), but that program also didn't detect my phone. Then I tried Airdroid, which worked only when I used the file upload under the browser but refused to connect to the phone when I clicked it on My Devices.
I even tried the method of *#0808# but it was actually already set to the correct settings so now I'm completely at a loss as to what it could be.
I've previously also had issues where I've plugged in the phone and it hasn't started fast charging and I haven't realised for an hour that it's only been cable charging and had to plug it back in for it to recognise it... is this likely a problem with the phone or cable?
I mean, aside from the also frustrating battery issues which have been worsening as time goes by (currently phone is on 79% having only used 39m screen time), I'm not sure whether it's time to give the phone a reset before actually taking it in to the store or whether it's likely an issue with the connector port at the bottom too which means it's probably not worth the hassle of resetting?
I won't go too much into the battery issues here, but I've been trying to use Greenify, App Optimisation, literally EVERYTHING I can think of, and I still don't get any more than 4 hrs and a half screen time.
My phone is not rooted. (though I'm wondering whether rooting it may help me). Thanks and I hope you have some advice that may resolve my issues!

I have the same issue.. muy phone won't charge unless otra on the wireless charging port

I have the SAME issue. I really don't know how to fix it!

Hmmmm sounds like your charging port is starting to go either that or maybe you could try flashing some new software through Odin and hope that's it's a software issue and as for the battery of course rooting does help bc it lets you get rid of the bloatware on the phone either that or try package disabler pro.

Huye battery issue?

I'm having an issue with a 3 year old Google pixel where the phone is no longer bootable due to it dying anytime it is turned on. Symptoms started about a year ago, the device would occasionally die randomly when opening apps especially with a camera like Snapchat. The issue was originally very infrequent but got more and more common until every app that is opened would kill the device if not plugged in. At this stage anytime the device died it wouldn't use to boot until plugged in. About 4 months ago it started dying even if it is plugged in and now it refuses to boot rom or stay alive in recovery long enough to even decrypt the device. Device is also unstable if plugged into a computer as it constantly reconnects and disconnects. The really odd part about all of this is booting into fastboot works just fine and it will stay in fastboot as long as it's plugged in. I'm thinking I'm gonna have to tear down the device and replace the battery manually but I'm not 100% sure if this is the cause so I'm asking here for confirmation first. Any advice would be greatly appreciated as I need to get data off the device to move to my new pixel3
EDIT: Well, f*** me, after looking through q&a section for 2 minutes I found other people have started having this issue around same time frame as me and it turns out the problem is the motherboard is shot which I was also thinking in the back of my head but didn't want it to be true. I'm so not spending $300 to replace the Mobo of a 3 and a half year old phone, but I do need to get the data off of it. My understanding is that adb DOESNT work over fastboot so I think I'm gonna try to plug it into my laptop and see if I can get twrp alive long enough to get any kind of filesystem access.

Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.

uaDPJ said:
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
Click to expand...
Click to collapse
It's not the battery. Many other sources confirm that this is a motherboard problem. At first it definitely seemed like a battery problem given original symptoms but at this point there is a wide range of random symptoms that point to the board being shot.
On a brighter note I've managed to keep the device alive in twrp long enough to pull data off by plugging into a computer. Wall charger would cause it to die despite charger working fine with several other devices

A bad battery can leak onto the board and fry the board, so you may both be right.