Hi, have a bit of an issue. My sister dropped her GXS in a pool today. she got it out and wiped it and it seemed to work fine (i told her that she should have taken the batt out immediately... she didn't) She went on then the phone died and got stuck in an endless reboot cycle. i opened it up and cleaned it and dried it, looks clean, from what i can tell. the screen shows the little refresh circle in the center, then shows the battery image for a few seconds then repeats the process (if i connect it to a wall charger, the battery image lasts about a second longer but it still restarts). it constantly restarts. and here is the problem, i can get it to download mode, but even in download mode it restarts after 3-4 seconds so i cant flash anything in such a short period. recovery does not work (even if it did i bet it would still restart after 3-4s). it starts doing this as soon as the battery is inserted.
It was running an old nightly of CM9 (about 2-3 months old)
Any help will be greatly appreciated
UPDATE:
Left it out on the sun for a few hours to dry even more off, now shows the galaxy I9000 splash screen and the semaphore kernel logo but it still restarts after 3-4s
UPDATE 2:
Dissasembled it and put it in a jar of rice, not expecting much. Took a look at the motherboard to prepare for the unbrickable mod. Those pads are TINY, i mean really tiny
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FULL size image here:
http://dl.dropbox.com/u/11992935/2012-09-08 18.32.42.jpg
That HUGE thing on the chip above is the microsd card
So my new questions are, in the original unbrickable thread i dont quite understand the instructions. IS it like in the picture near the enlarged piece numbered 1. that you must resolder the yellow marked resistor to the blue marked pads, or like in number 2. you must remove the resistor and put a wire (drawn grey) like in the picture or do you do first number 1. and then attach the wire to the upper end of the moved resistor and then to the other pad?
Congrats to your sister, looks like she killed her SGS.
Looks like the battery's not the problem, if it reboots when it's unplugged (an almost empty battery -almost empty = already shut down, but reboots for a few seconds- shows at
least unlock screen for me when I turn it on).
If recovery and download mode don't last enough to flash, it's over IMHO. And even if your warranty is still valid, water damage is not covered..
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
quantity rostsrt
total.destroyer said:
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
Click to expand...
Click to collapse
Try to put the phone in a jar of rice for 24H.
After that try to flash a rom using odin.
total.destroyer said:
I am starting to consider doing the unbrickable mod, but i dont know whether this is a software or a hardware problem. any way to test that?
Click to expand...
Click to collapse
I doubt this has anything to do with Unbrickable mode solutions, anyway links to test mode tare on My Android Solutions, link below.
You problem would be most likely due to moisture shorting power and usb ports/contacts
xsenman said:
I doubt this has anything to do with Unbrickable mode solutions, anyway links to test mode tare on My Android Solutions, link below.
You problem would be most likely due to moisture shorting power and usb ports/contacts
Click to expand...
Click to collapse
I went over your list before posting, nothing helped in my situation, and there is no test mode on your list, or maybe i missed it. I cleaned the usb port and it looks clean, the battery contacts are also clean, no obvious damage shows, and the power on button can not be shorted because it is a potted foil membrane and the leading contacts are clean, and the button works otherwise i could not get temporarily in download mode. gonny try and mess about with adb if i can get the phone to be seen.
total.destroyer said:
and there is no test mode on your list, or maybe i missed it.
Click to expand...
Click to collapse
Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
you can only revive phone using unbrickable mode when phone is totally dead with only this words SEC S5PC110 TEST B/D, that why I said, i am doubtfull you need to use it.
xsenman said:
Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
you can only revive phone using unbrickable mode when phone is totally dead with only this words SEC S5PC110 TEST B/D, that why I said, i am doubtfull you need to use it.
Click to expand...
Click to collapse
I think i have no other choice, i have tried everything, my only options now are to get it repaired without warranty (probably will cost more than a new gxs off ebay), use it as a paperweight or try to do the unbrickable mod and see if that works.
Is there a possibility that a software error is constantly rebooting the phone or is there a hardware problem? I mean, could a corrupted bootloader constantly reboot the phone, no matter what mode the phone is in, like in download mode is the bootloader still runing in the background? or the kernel?
Good luck if you decide to try. I'm considered extremely good at soldering by many, I have all the proper tools including a top notch soldering station, and moving that 0201 resistor took me like an hour. One of the most difficult things I've ever had to do, and I didn't think it would work in the end. Having two irons and a microscope would have helped a lot but it's not a mod for the faint of heart. That said it saved my phone from some nasty software business.
I really doubt it would solve this problem, since it's water damage it's probably long gone. If you have no possible other option though, there's no harm in trying this.
FjarrKontroll said:
Good luck if you decide to try. I'm considered extremely good at soldering by many, I have all the proper tools including a top notch soldering station, and moving that 0201 resistor took me like an hour. One of the most difficult things I've ever had to do, and I didn't think it would work in the end. Having two irons and a microscope would have helped a lot but it's not a mod for the faint of heart. That said it saved my phone from some nasty software business.
I really doubt it would solve this problem, since it's water damage it's probably long gone. If you have no possible other option though, there's no harm in trying this.
Click to expand...
Click to collapse
I have a friend that does electronics and solders daily so he should be able to do it, but the big question is, is this actual hardware damage from water or a short caused data corruption and the problem is software, because the thing works, the display works, animation works, the buttons work, it only decides to repeat the process every 3-4s (it varies, sometimes it last about 6-7s, especially if i plug it in to charge, or it dies in a second or two). Could water damage it so precisely to do that, or was there a short that caused some data corruption of the rom/bootloader/kernel/whatever that makes it reboot after the boot process encounters that section of bad data, or the memory chip got corrupt. Is there a way to find out, can a log be dumped out while it is booting? my pc does not recognize anything is connected while it does its refresh battery thing, or maybe you need special drivers.
total.destroyer said:
I think i have no other choice, i have tried everything, my only options now are to get it repaired without warranty (probably will cost more than a new gxs off ebay), use it as a paperweight or try to do the unbrickable mod and see if that works.
Is there a possibility that a software error is constantly rebooting the phone or is there a hardware problem? I mean, could a corrupted bootloader constantly reboot the phone, no matter what mode the phone is in, like in download mode is the bootloader still runing in the background? or the kernel?
Click to expand...
Click to collapse
If your phone had no problems and this problem only developed after the water damage it has nothing to do with software and all to do with hardware . I think the Phone reboots due to minute shorts in the hardware ..moisture underneath the chips could be one...you can try heating a few of larger chips...best would be to keep the phone wrapped in tissue and in a pot of rice for a week or so
solved
i see one galaxy s like this before.
the phone boots if after u see a green battery on screeen
1.but u have to connect a strong charger (1 to 2 Amps) or a USB (1 Amp) laptop computer .
2.after connect the phone, u have to wait aprox. 30 sec, if nothing happened u ned to reconect (pull out battery , then insert it back in the same time with usb or charger plug )
3.if the grenn battery appears on screen wait to charge to 50% then press power button but not detach cable or charger
4.after complete boot , u are free to use your phone (ALL THINGS WORKS)
Related
All of a sudden I started getting this error when plugging into my PC.
I booted into the bootloader (tricolor screen) and still didn't work. It charges but doesn't connect properly.
I have searched around and read a few things (disable advanced networking, take out battery for 30 mins) Nothing seems to work.
Seems like it's a device problem... any suggestions because I'm kind of screwed here.
gilligan8 said:
All of a sudden I started getting this error when plugging into my PC.
I booted into the bootloader (tricolor screen) and still didn't work. It charges but doesn't connect properly.
I have searched around and read a few things (disable advanced networking, take out battery for 30 mins) Nothing seems to work.
Seems like it's a device problem... any suggestions because I'm kind of screwed here.
Click to expand...
Click to collapse
Hit up htcwiki.com there is a solution there, I had the same problem and it sorted itself out by buying a docking station station. I also use a three adapter (3.5mm head, sync cable and headset)which also works.
If you have the same issue as me chances are that your pda does not charge when connected either.
Hope this helps
No, as stated, mine charges when plugged in... I have a cradle, but it hooks up with the same usb cable so I can't see how that would make it better... it's just essentially an extension isn't it?
Could be a glitch in the phones software, a cable going bad, a plug going bad or a windows problem.
I've gone through a few cables and a dock, something always gets bent or something and it won't sync, I just grab another cable and it works. It's a shame the dock is bad now, it will only charge.
ChumleyEX said:
Could be a glitch in the phones software, a cable going bad, a plug going bad or a windows problem.
I've gone through a few cables and a dock, something always gets bent or something and it won't sync, I just grab another cable and it works. It's a shame the dock is bad now, it will only charge.
Click to expand...
Click to collapse
+1 All of a sudden a few weeks ago, my phone stopped syncing, panic, because I flash a lot . Tried everything, the list of things to try over at htcwiki was edited by me, and nothing worked, until I changed the cable. Voila ! been working ever since.
No good... not working even on another PC with another cable... and it worked before on that setup.
Um you only have troubleshot half of it. Did you say you reset the phone? LOL oh yeah my phone never worked on the original cable. Just because something was cool for one minute doesnt' mean it won't **** up the next.
Hard reset the phone. If that doesnt' work, than you are one step closer to a broken phone.
Have fun lol.
gilligan8 said:
All of a sudden I started getting this error when plugging into my PC.
I booted into the bootloader (tricolor screen) and still didn't work. It charges but doesn't connect properly.
I have searched around and read a few things (disable advanced networking, take out battery for 30 mins) Nothing seems to work.
Seems like it's a device problem... any suggestions because I'm kind of screwed here.
Click to expand...
Click to collapse
Try here it may help ...
Found my problem in the last post (second to last post now )
My 2nd pin (closest to the middle) was laying flat and didn't have the curve the others had.. so it wasn't making contact. I used a caligraphy pen to get under it and pop it back up and now it works... I'm sure I'll have to keep an eye on it but for now it's working.
Hope this helps others that are reading everyone saying "it's the cable" and that isn't your problem
Thanks for all the suggestions, it had to be one of them!
ChumleyEX said:
Could be a glitch in the phones software, a cable going bad, a plug going bad or a windows problem.
I've gone through a few cables and a dock, something always gets bent or something and it won't sync, I just grab another cable and it works. It's a shame the dock is bad now, it will only charge.
Click to expand...
Click to collapse
Like I said, it could be the port. booya
Well, you did mention everything except for solar flares.
denco7 said:
+1 All of a sudden a few weeks ago, my phone stopped syncing, panic, because I flash a lot . Tried everything, the list of things to try over at htcwiki was edited by me, and nothing worked, until I changed the cable. Voila ! been working ever since.
Click to expand...
Click to collapse
Which OS on your comp. are you using Denco? I've been using vista with no problems until now and it's more than funny how this syncing issue has just been popping up all over (most likely from vista updates). First instinct with vista is updates and firewall; killed and accepted every option, still with no dice. I seriously doubt it's the cables since they worked just fine for the last several hundred syncs and now sync problems abound...any help would be appreciated brother
gilligan8 said:
Found my problem in the last post (second to last post now )
My 2nd pin (closest to the middle) was laying flat and didn't have the curve the others had.. so it wasn't making contact. I used a caligraphy pen to get under it and pop it back up and now it works... I'm sure I'll have to keep an eye on it but for now it's working.
Hope this helps others that are reading everyone saying "it's the cable" and that isn't your problem
Thanks for all the suggestions, it had to be one of them!
Click to expand...
Click to collapse
WTF?! That fixed it?
hmmm, I smell something fishy...so many people having issues with connecting at the same time...upgrade to newest devices? This war with Wm and Apple makes me want to get a simple razr; tired of all this bull****
gilligan8 said:
Well, you did mention everything except for solar flares.
Click to expand...
Click to collapse
I kept silent out my internal dignity
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everyone knows USB is shielded for solar flares.
GOSH!!!!
kaalgoosy said:
WTF?! That fixed it?
Click to expand...
Click to collapse
Yep... that pin is half of the data (1st pin is ground, last is power and two in the middle are data)... obviously ground and power are working as it charged, but if one of the data lines isn't making contact then the PC is going to be confused because it knows something is there just not getting enough info.
I tried everything, straightened my pins, shut off firewalls and security, I use Windows Xp running with Bootcamp on an iMac. I have never installed service pack 3, because I read that , that was a problem with syncing. Shut off advanced network functionality, everything I could think of.
I had sync'd a thousand times with that cable, and flashed at least one hundred roms. Then one day it just stopped syncing. After pulling my hair out for two days, trying everything, I pulled a new cable out of the overflowing cable draw, fixed, haven't had a problem since. Go figure !
denco7 said:
I tried everything, straightened my pins, shut off firewalls and security, I use Windows Xp running with Bootcamp on an iMac. I have never installed service pack 3, because I read that , that was a problem with syncing. Shut off advanced network functionality, everything I could think of.
I had sync'd a thousand times with that cable, and flashed at least one hundred roms. Then one day it just stopped syncing. After pulling my hair out for two days, trying everything, I pulled a new cable out of the overflowing cable draw, fixed, haven't had a problem since. Go figure !
Click to expand...
Click to collapse
HUh, It seems you might be right about a simple cable replacement. My previous cable synced me up for several hundred syncs and just crapped out one day; dug up one of my older cables and it synced just fine and now it just took a dive for charging but not syncing. Guess I'll have to hit Best Buy for a new one. Like you said; go figure. Although I noticed some new gray hairs sprouting from searching and tweaking for fix
Buy online.... Best Buy RAPES you on cables!
Hi my friends,
I have an A855 that seems to have died; I try to turn it ON but it does nothing (absolutely nothing!) without even lit the screen.
The only sign of life is that I get a white lcd when I plug it to the AC adapter and also got it recognized with my PC and able to use ADB.
The phone it's not water damaged and it died from one moment to the other.
Taking it to Verizon is not an option as live outside USA.
Best Regards and hope you can give me your opinion.
Hi MGA2009!
MGA2009 said:
I have an A855 that seems to have died; I try to turn it ON but it does nothing (absolutely nothing!) without even lit the screen.
The only sign of life is that I get a white lcd when I plug it to the AC adapter and also got it recognized with my PC and able to use ADB.
Click to expand...
Click to collapse
This is little more than nothing
Try this:
First you might charge your battery with the wall charger untill the white LED at the USB connectors goes off. So this makes sure the charging works.
Remove battery measure the voltage (~4.0V) and insert battery again.
With full juice, you might try to enter bootloader mode by pressing the D-pad up while powering on the device.
Do you see some message from the bootloader?
Next steps depend on this....
Regards,
scholbert
Thanks for your answer!
I charged the battery with a wall charger, the white led turned off.
Then I tried the volts with my "el cheapo" multimeter and gave me 3.20V
So I said... hey maybe my multimeter is giving me wrong measures... and I tried my Nokia's X3 battery (also 3.7V) and it measured 4.05V with the same multimeter.
Do you think that is the reason the phone is not turning on?
0.8V seems quite a lot for a phone that uses 3.7.
I don't have another battery but I can test it with my Nokia battery.
MGA2009 said:
I charged the battery with a wall charger, the white led turned off.
Then I tried the volts with my "el cheapo" multimeter and gave me 3.20V
So I said... hey maybe my multimeter is giving me wrong measures... and I tried my Nokia's X3 battery (also 3.7V) and it measured 4.05V with the same multimeter.
Do you think that is the reason the phone is not turning on?
0.8V seems quite a lot for a phone that uses 3.7.
I don't have another battery but I can test it with my Nokia battery.
Click to expand...
Click to collapse
A battery at 3.2V might be little low for operation...
For your Nokia.... 4.05V at a fully charged battery is O.K.
You should verify your multimeter to get sure
Anyway check if you see the bootloader message.
Insert battery and plug in your charger as well, this should at least allow you to power up the device.
Good luck!
scholbert
Sounds like a dead lcd. I have one I bouught to fix with the same problem, do the soft keys light up or any startup sound play? If your computer sees it you can get its state with adb in the terminal to see how far its getting.
bitz_dv said:
Sounds like a dead lcd. I have one I bouught to fix with the same problem, do the soft keys light up or any startup sound play? If your computer sees it you can get its state with adb in the terminal to see how far its getting.
Click to expand...
Click to collapse
My friends,
I can't boot into bootloader and the keyboard does not lit up.
The only sign of life is thatis recognized by my computer as and ADB interface and I can try some commands... Also the white lcd lit up when I connect it to my PC.
I have tried with another battery (tested on a Milestone at 70% power) and the phone does nothing.
Any guess? I also tried different buttons combinations to power it on but none does the trick.
It is most likely a battery issue. I had this happen to me twice. Go to store and have them try a different battery. Most likely will fire up.
Personally don't think that it's a battery issue.
Little strange though
MGA2009 said:
I can't boot into bootloader and the keyboard does not lit up.
Click to expand...
Click to collapse
AFAIK entering bootloader should always work.
...unless you brick the bootcode or installed unsigned images without applying some hacks.
So maybe some problem with the keypad as well (D-pad not working correctly to enter bootmode)
MGA2009 said:
The only sign of life is thatis recognized by my computer as and ADB interface and I can try some commands... Also the white lcd lit up when I connect it to my PC.
Click to expand...
Click to collapse
Sorry, do you refer to your LCD (display) or LED (white LED for charging control)???
Mmmh if it's your LCD that it's going from black to white there's some logic working
Could be some problems here.... Could you make a picture of the LCD?
If you may connect to ADB, your android system should be up and running.
At least with some basic functions.
Maybe some parts of your system partition got corrupted.
Do a little research about bootloader mode and how to use RSD lite.
Maybe you should prepare for that....
Again try to enter bootloader and connect to your PC.
The best is using a linux host and type lsusb. What do you see?
Regards,
scholbert
Sorry sholbert;
My LED lit up when I connect it to my USB not my "lcd".
The "lcd" is always dark.
I know how to use RSDLite, I use it with my Milestone.
I thought It could me the LCD but then the keyboard would be lit.
Any possibility that a corruption in the system structure could lead to a non powering state?
WIll post the "lsub" results.
Results:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Best Regards.
Hi,
would have been sufficient to post the entries here
No doubt your device get's properly recognized.
I think bitz_dv is right and it's that simple: LCD is dead
There'd been some reports of damaged backlight.
You could try the following:
Reboot
Connect to ADB again
Chdir to your sdcard and type dmesg > dmesg.txt
Post the resulting file here.
If the LCD logic is damaged the kernel will indicate this.
If your logic is fine, it's a backlight issue i guess.
There's nothing much you could do in this case apart form buying a new display (or your a genius in electronics and fix it yourself )
There are also a lot of other nice tools to check your systems integrity.
Do little research about logcat and debugging user events.
Best regards,
scholbert
Thank you very much.
I tried to CHDIR my SD but I could not get it, tried with /system/sdcard and /sdcard
So could not retrieve dmesg.txt
But I logged logcat.txt
There is some interesting part and the end of the LOG:
Code:
E/IMGSRV ( 1304): framebuffer.c:273: framebuffer_device_open: No devices (check permissions)
E/FramebufferNativeWindow( 1304): couldn't open framebuffer HAL (No such device)
D/libEGL ( 1304): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1304): loaded /system/lib/egl/libEGL_POWERVR_SGX530_121.so
D/libEGL ( 1304): loaded /system/lib/egl/libGLESv1_CM_POWERVR_SGX530_121.so
D/libEGL ( 1304): loaded /system/lib/egl/libGLESv2_POWERVR_SGX530_121.so
What do you think?
Hi.
RSDLite Recognized my phone.
My guess is that the previous owner tried to flash an SBF for the Milestone not the DROID; producing a mess on all partitions. I don't know if it is possible.
When I try to flash an STOCK SBF I get: "FAILED FLASHING PROCESS,FAILED FLASHING PROCESS. UNABLE TO RETRIEVE INITIALIZATION VALUES FROM INI FILE (OX7029); PHONE CONNECTED".
What else could be?
Did you manage to go into the bootloader?
Try using RSD 4.6 for flashing...Let me know if that works!
Will try RSDLite 4.6 and report my results.
Thank you very much.
I as able to flash using RSDLite 4.6
It completed successfully but still no LCD light, not touch response to led black lighting no 3.5mm jack sound, etc...
It seems that is a lost cause but I would like to know which is the cause of this...
Best Regards.
MGA2009 said:
I as able to flash using RSDLite 4.6
It completed successfully but still no LCD light, not touch response to led black lighting no 3.5mm jack sound, etc...
It seems that is a lost cause but I would like to know which is the cause of this...
Best Regards.
Click to expand...
Click to collapse
You didnt tell us what happened in the first place? How did the phone stop responding?
What was the last thing you did before it happened? What rom you were using? Overclocked? vsel?
Please tell us more!
I received the phone AS IS; I do not know what the previous owner did to this poor thing.
I think it is not water damaged as the water sticker is still white.
MGA2009 said:
I think it is not water damaged as the water sticker is still white.
Click to expand...
Click to collapse
May I ask how should the sticker look with no water damage and with water damage? Mine looks like white/red "stars", surely isn't just white.
100% white when NOT EXPOSED TO HUMIDITY/WATER
lightly pink with some white dots when exposed to humid places like lot of time in bathroom with moisture
100% pink/red when submerged in water
I did a google search for this and everywhere where I found the battery compartment photo of droid it was actually partially red (the crosses). So 100% white you've is kinda weird.
I've been getting this error every few days since I got the phone, but now I've gone a day without being able to plug it in (this is why I only buy phones with wireless charging). I tried rebooting, shutting it down for a while, etc.
And it's gotten nowhere near water.
Any solutions for this? Do I just need to take it to a t-mo store and ask?
knoxjon said:
I've been getting this error every few days since I got the phone, but now I've gone a day without being able to plug it in (this is why I only buy phones with wireless charging). I tried rebooting, shutting it down for a while, etc.
And it's gotten nowhere near water.
Any solutions for this? Do I just need to take it to a t-mo store and ask?
Click to expand...
Click to collapse
I'd already be on my way back to the store. Besides, it's supposed to be water resistant- take it back let them figure it out
Cheers,
StevenRN
steven.rn said:
I'd already be on my way back to the store. Besides, it's supposed to be water resistant- take it back let them figure it out
Cheers,
StevenRN
Click to expand...
Click to collapse
I got the same problem since 3 days ago, I think it is a software bug, as my G6 charges when it's off but gives me the same error when it's on! try to charge it while off. I am looking to find the actual problem, if anyone know why this happens??
Solved for me
knoxjon said:
I've been getting this error every few days since I got the phone, but now I've gone a day without being able to plug it in (this is why I only buy phones with wireless charging). I tried rebooting, shutting it down for a while, etc.
And it's gotten nowhere near water.
Any solutions for this? Do I just need to take it to a t-mo store and ask?
Click to expand...
Click to collapse
I took my phone to spain and it had loads of sand on it by the beach. I couldn't charge due to the moisture warning for 3 days. Eventually i found a solution. I loaded a bathroom sink with about 2/3rds water. I swilled only the port area in the sink. I then dried the phone as well as possible. I screwed a thin tissue paper up and dabbed round the port. I then found a rectangle piece of card (it was a clothes price tag) it was probably 1 millimetre thick and i pushed it in deep into the usb port to aid cleaning using the corners of the tag. It solved the issue and didnt break anything and cleaned out some of the deep sand and cotton that wasnt drying at 30 celicus heat this week. Saved me claiming on my insurance and the headache of installing all my apps etc. Try it, but be very careful with the card tag as you dont want to break any terminals in the usb slot. I used this forum to try and find a fix and i couldn't, hence me putting my solution on here.
bhupindra said:
I took my phone to spain and it had loads of sand on it by the beach. I couldn't charge due to the moisture warning for 3 days. Eventually i found a solution. I loaded a bathroom sink with about 2/3rds water. I swilled only the port area in the sink. I then dried the phone as well as possible. I screwed a thin tissue paper up and dabbed round the port. I then found a rectangle piece of card (it was a clothes price tag) it was probably 1 millimetre thick and i pushed it in deep into the usb port to aid cleaning using the corners of the tag. It solved the issue and didnt break anything and cleaned out some of the deep sand and cotton that wasnt drying at 30 celicus heat this week. Saved me claiming on my insurance and the headache of installing all my apps etc. Try it, but be very careful with the card tag as you dont want to break any terminals in the usb slot. I used this forum to try and find a fix and i couldn't, hence me putting my solution on here.
Click to expand...
Click to collapse
I got mine working via a similar method & haven't had the problem since. It's only given me the warning once since then, and a reboot fixed it.
knoxjon said:
I got mine working via a similar method & haven't had the problem since. It's only given me the warning once since then, and a reboot fixed it.
Click to expand...
Click to collapse
Aaand my phone is doing it again. 24 hours and unable to charge except wirelessly or by plugging it in when it's turned off. Trouble is, I'm going out of town tomorrow and am counting on it for GPS.
edit: there's some relationship between the moisture alert and charging settings in developer options. Some people seem to be able to fix it totally that way, but I am seeing only partial success.
Same has happened to me. I am resetting right now to see if this works.
Any luck? They are replacing mine, but it's going to take a week or so.
This has been occurring on my device for a while as well. Usually the reboot while keeping the device plugged in would reset the software bug and charging would continue like normal. Now I can't get the phone past 4 or 5 percent charged. Every time I try to power off the device and charge that way, the phone automatically turns on after it gets to about 5 percent, and the cycle repeats with the charging blocked due to moisture in the usb port error. This is certainly very frustrating, not to mention I also had the weird camera glass cover anomaly where the glass shatters outside the lens, rendering my standard camera lens unusable with a foggy/smoky effect due to the glass on the outside cracked. I loved my LG G4, but I don't know about LG after this debacle of events. I too have tried changing charging settings in developer options with no success. I will be taking this back to T-Mobile tomorrow unless some miracle happens.
knoxjon said:
Any luck? They are replacing mine, but it's going to take a week or so.
Click to expand...
Click to collapse
Nope it did not work. My next trick is to put it in a silica bag if that does not work I will take it back to T-mobile.
I keep seeing people come to this thread with hopes of a fix. I highly recommend you return your device if you have this issue. I have taken my G6 through the ringer at the water park (swimming, water slides, etc.) and have not once received this warning. It must be a defect.
Milly7 said:
I keep seeing people come to this thread with hopes of a fix. I highly recommend you return your device if you have this issue. I have taken my G6 through the ringer at the water park (swimming, water slides, etc.) and have not once received this warning. It must be a defect.
Click to expand...
Click to collapse
Caught between a rock and a hard place there. I don't know if you're familiar with some G6's getting that crazy spider crack on the camera glass, but that freak occurrence happened on my device as well, so LG won't validate a return on the manufacturer's warranty due to that, and I really have no way of doing a factory reset since the phone won't charge anywhere past 5% while the phone is off before it turns on automatically at that point. $175 to get it replaced under T-Mobile insurance. Never thought a device so highly praised would be such a disappointment.
televate said:
Caught between a rock and a hard place there. I don't know if you're familiar with some G6's getting that crazy spider crack on the camera glass, but that freak occurrence happened on my device as well, so LG won't validate a return on the manufacturer's warranty due to that, and I really have no way of doing a factory reset since the phone won't charge anywhere past 5% while the phone is off before it turns on automatically at that point. $175 to get it replaced under T-Mobile insurance. Never thought a device so highly praised would be such a disappointment.
Click to expand...
Click to collapse
So T-mobile wanting you to pay the $175 fee? Did you tell them you put it in the water?
There was no contact with any significant amount of water at all since I got the phone, but thanks for adding your skepticism.
So I am no longer getting the moisture error I am getting the "Power Supply Tap To Change USB options message" and a different battery icon error which I think is making me have high phone idle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had this issue, and sent it in to LG. They told me there was a software glitch that once that alert was activated, the software wouldn't turn it off. You can prove this by restarting the phone, and plugging in the charger before it boots back up again. It will charge perfectly fine, but then if you unplug it and plug it back in, the error comes back. Send it in, they'll fix it.
Brandonsmerry said:
I had this issue, and sent it in to LG. They told me there was a software glitch that once that alert was activated, the software wouldn't turn it off. You can prove this by restarting the phone, and plugging in the charger before it boots back up again. It will charge perfectly fine, but then if you unplug it and plug it back in, the error comes back. Send it in, they'll fix it.
Click to expand...
Click to collapse
For what it's worth, that wasn't the case for me. I tried every variation of plugging it in on/off/rebooting/tweaking every setting I could find or anyone suggested. The last time I had it happen, it took 3 days before it let me charge any way but wireless. Finally I went to the T-Mo store and they spent five minutes on it before ordering a new phone. That was a month ago. Knock on wood, I haven't yet seen the problem with the new phone.
ughhhhh.... tried everything. I absolutely hate having to reload everything on my phone!
Yup, last LG phone I'm buying. Software error or not I just came from a bootlooped LG G4 that I had to fight tooth and nail to get replaced and still wasn't free ($20.) I've never damaged a smartphone in the last 7 years of owning one. No cracked screens or water damage. Not only that, in an attempt to charge the phone while powered off it charges slowly AND forces my phone back on even though I select power off. Seriously people, stop buying LG.
Replace port charger this fix issue whith moisture charging blocked! i test this works fine
Hi Guys
Sad situation (as my P9 was always kept in a case and after almost a year still looks like new/mint condition) where I have dropped my phone to a bath, and phone went under the water for around 2-3 seconds (was still in protective case).
It has received some water through jack (headphones) socket, charging port and through the speaker crate.
As soon as I have rescued it, I have took all the water off the phone using towel and placed it quickly on a radiator/heater.
Unfortunately, did no have any rice to put the phone into a bowl of rice (don't even know if that is the best way).
Phone did act like it's absolutely fine, had some notifications that headphones are connected, but I remember when once I spilled some water on my desk and had one of the work iPhones on this desk, it was having same/similar issue for couple of hours (as water did come in contact with headphones port), but the problem did resolve itself after some time.
Same happened with Huawei P9. The headphones port has started to work after some time without any action taken from my side.
After that, I did have a situation where my P9 dropped on the floor and it has received some scratches (same day, an unlucky day).
Went home, connected phone to the charger and left it overnight.
In a morning found that it is only showing 40% (charging, but 40%).
On unplugging, it does stay on 40% for some time, it does not indicate any power loss after time (for example, if I will play a game or use camera). However, after for example hour, it does say that it has only 10% battery, on reboot it does say that it has 30% battery.
On next reboot it tells me that I have 10%. Always full numbers, like 10, 20 or 30 or even 40% but appearing randomly.
Now - after 2 days of being constantly on a cable (charger) it is constantly showing that it has 2% of battery.
On disconnecting, it goes off in 30 seconds.
On connecting, it does start up and it does show that it is charging, but it remains on 2%.
Anyway - I have already opened the phone and tried with replacing the charging port (board).
This did not resolve the issue.
On Saturday (in 2 days) I may receive a new (OEM) battery and I will see if this will resolve the problem.
But in the meantime, does anyone may have an idea where to look for or how to troubleshoot to find the cause of an issue?
Phone inside looks perfectly fine.
Honestly in such situation there is no simple solution. Its all about luck...
Water is really sneaky, and even such thing like putting phone on heater can actually damage it even more, because some people seriously put it on lava-hot places where water just vapor and enter even smaller spaces inside phone.
What I would do after few minutes of panic and few hours of swearing, is to dissemble it with the speed of light just to disconnect battery from mainboard. This is really important, and one of thing that I hate in phones today(you cant disconnect battery easily).
After that I would take paper towel and dry everything if I could not get my hands on rice. Then take super soft pain brush and scrub all spaces on boards and case inside, because for most of time water it self dont damage phone, but rust/calcium that settle between circuit paths. So its important to carefully brush every space blow it with compressed air.
Then its good to check if battery didnt get swollen and if all smaller lego-like connectors are clean inside(good magnifier is handy here).
But if after that phone work but dont charge its probably one of the charging component on board or usb socket it self is rusted. Problem is that in today phones those components are so fricking small that I sometimes cant distinguish resistor from capacitor or transistor...
And of course beside that its good to do full wipe, today phones are like magic box, no one really know what is going on because everyone have different problem with them, so maybe phone need to wipe its battery informations/stats to fix it self...
I cant really thing about anything else, because you cant do much more by your self in home, Phones are not designed to be easy to fix. And sometimes its eve cheaper to buy new phone instead(eg. Huawei P10 is now available for damn 420Euro... when P9 is still 350...)
Battery did arrive today. I will see if this will resolve the issue.
Once I will replace and test it - I will update this thread.
I can confirm that replacing battery did resolve the problem. Phone is charging again.
Last thing I have to fix now is the rear camera as it does not focus correctly.
Don't know if that is because of my disassembly and assembly or by the water damage.
Update: Still haven't found why the colour camera does not autofocus.
Strangely, if I will take off the back cover (plate), the autofocus is fully working, but as soon as I will clip it back on and the phone will be "fully assembled" - it does not autofocus. Still trying to understand what is causing the issue. Black and white / monochrome works absolutely fine.
I will open the phone today or tomorrow again and see if I can spot the (probably obvious) reason of the issue.
I do remember that autofocus did work fine before opening the phone (so before replacing the battery) so most likely I have not attached something correctly or something is misaligned (however I have checked it twice and all looks perfect).
I do have an option to send phone for the repair to Huawei, but I do feel that they will cancel the warranty anyway. Luckily the camera module on eBay does not cost a lot, so maybe I will just replace it by myself if I won't find solution today or if Huawei won't fix the problem.
And another update.
Still can't confirm 100% sure about the camera problem.
I have disassembled it, assembled it back all together.
Found that I have scratched (at the first time when I was replacing the battery) the gold foil on a side which is touching the small connector on the right hand side of the camera.
After assembling carefully all together, it does look like camera is alive and it does autofocus almost 100% perfectly.
There is however this missing 1% when it does kind of rattling movement at the end of auto focusing, and can't find out if it is because it still slightly misaligned, or is it because the golden foil is slightly damaged (on a side of the camera module).
I am thinking about getting a new camera module but first I would have to understand how to assemble it in such a way, that it will just fit it without scratching the side of the camera module (it is tricky to do this).
Anyway - the camera is almost working. If I will decide to make it work absolutely ideal - I would probably have to learn how to assemble it properly.
P.S. And just to explain to everyone, I am watching YouTube videos and learning from those.
I guess I have damaged the camera module when I was replacing the battery due to lack of understanding how it is assembled in the first place.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's weird, the rear dual camera is detachable but is not removed in that guide, there is a metal cover if you didn't know already that just pops off then you can unplug the camera.
Yeah. I was following a different guide and I did took it off (completely) off the main board.
The problem is the small metal "clip" on the right hand side which links to the metal screw-able cover.
Visible here:
https://youtu.be/TM6t_iAce-Y?t=3m26s
(3:26)
That little thing did mess up the golden side of the camera module which looks like foil.
Now I am struggling to place it all together in place perfectly aligned.
As mentioned - the camera works almost almost perfectly however after pay day I am about to order a full camera module to replace it.
Get a new camera module. They should be cheap from aliexpress.
I have seen plenty of the "OEM" ones but I am not 100% sure if those are "really" the same as original ones.
Payday is in 4-5 days, so I will just order a genuine one on ebay with delivery in several days, not in 3 weeks
edmun said:
I have seen plenty of the "OEM" ones but I am not 100% sure if those are "really" the same as original ones.
Payday is in 4-5 days, so I will just order a genuine one on ebay with delivery in several days, not in 3 weeks
Click to expand...
Click to collapse
You are Very Talented And Enthusiastic Person :good:
Good Luck
Ok. An update.
I do have an original new Huawei P9 Camera module, but.....
Before I have attempted to place it in, I was trying to find out how to properly assembly it so I have done several dry runs on the current camera module.
So instead of trying to put the new one in place and damage(?) it by a mistake, I have decided I will try on the one which is already in my smartphone.
And I will say this way - my camera is fully working. Including Autofocus on colour camera and on black and white one.
It was (as I suspected) a basic mistake during the assembly, where I was constantly doing things wrong
For anyone which would be trying to do the same.
If you have (accidentally) disassemble the board with camera module and now the autofocus does not work as expected, make sure that you will assemble it following steps below:
1) With metal cover taken off, attach cameras tape to the board
2) Leave the camera module away from the board
3) Screw in the metal plate (two screws) which holds the camera tape
4) Once the plate is in place, clip in the camera module into the designated hole/place
My mistake was, that I was constantly trying to place the camera in the designated camera place before screwing in the metal plate which is above the cameras tape.
Now I have a spare original camera module I will keep testing my phone but after a week after the final repair, I don't see any issues at all.
My Huawei P20 Lite does not charge after 5 min in water
Hi Edmun
Did you find any solution to your troubles?
I have the same troubles with my Huawei P20 Lite. I was swimming with it for 5 min (Yes, really stupid!) and now it wont charge. I turned it off immediately, and I dried it for 4 days in 35* C with the back plate removed, and it now works fine as long as the charger is connected. However the battery level went from 90% to 2% in a few days, and now it remains there no matter how long time I charge it. It turned into a wired phone! Why doesn't it take charge when everything else works? What can I do to solve it? Obviously the current goes in through the socket as it works when connected, and it makes the usual beep at the moment of connection. I have cleaned the female socket on the phone with a fine brush and inspected it with a loupe and it looks perfectly OK. What can I do to fix it? Should I get a nwe circuit bord, and in that case wihch one? Or should I try a new battery?
Please, help me! I bought the phone just a month ago! Many thanks for any hints on solutions.
/Nils
Replacing battery worked.
had exactly the same situation.
Can't promise it will fix your issue but it worked for me. Replacing is tricky because of the glue underneath the battery but if you ever fixed any smartphones then you should be fine
Brother....I am right now in same situation...can you tell that the cell phone work ???
My cell phone had the same situation and its shows only 2% and switch off in 30 sec... Pls update....
On the board I see six test points. The question is if any of these can be shorted to be able to get the device in a mode where it can be flashed despite being OEM locked.
OK, so the test points are below the fingerprint flex cable connector:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here’s roughly how I proceeded:
Made sure that I’m grounded by touching a grounded metal piece in my apartment.
Removed the SIM tray.
Opened the device according to the instructions by Wit Rigs (youtu.be/1VIdpuXSFmI). Separating the top with the screen was quite hard as it is glued.
Popped out the battery flex cable connector, then the fingerprint flex cable connector.
On my laptop (Windows 7 X64) started MiFlash 2016.08.30.0, downloaded from en.miui.com/thread-345974-1-1.html.
Inserted the USB-C cable that came with the phone into the phone. (not yet into the laptop!)
Using a bent and cut staple, I connected the test points, then inserted the USB-C cable into my laptop.
Windows reported that a new device is connected.
Removed the staple, clicked refresh in MiFlash: A device showed up.
Flashed the latest official stock Android One ROM V9.6.10.0, downloaded from en.miui.com/download-353.html:
Initially I got a message that MiFlash cannot receive a “Hello” packet. It turned out that I was too slow. After connecting the device, one only has limited the time to start the flashing. I read elsewhere that it’s 15 seconds.
Success, my A2 boots up again! Now I’m only waiting for thermal paste to arrive in the mail, I will apply that, then close the phone again.
feklee said:
I found the points, and I would like to post a photo, but I can’t because I cannot add attachments to posts.
Click to expand...
Click to collapse
Can you upload the photo else where and provide a link maybe?
Please stop opening new threads for the same issue.
I think this is the third one I have seen now. I'm sure someone will be able to help you but with the phone being as new as it is you may have to wait or figure it out for yourself. I have the phone but have not tried root yet because it's too early in the phones life to be messing around with it. Let the community grow first.
I do hope you made to get it solved though and if so you could document it so we can all learn from it in the future
mauley said:
Please stop opening new threads for the same issue.
Click to expand...
Click to collapse
Coming from Q&A platforms such as StackOverflow, I was assuming it’s better to use separate threads: The other ones are about Magisk on the A2, about clean installing the A2 ROM, and about using a deep flash cable on the A2. Finally being able to upload pictures, I am now fleshing out my earlier posts with details.
Anyhow, I hope that the information can be of help for others!
feklee said:
OK, so the test points are below the fingerprint flex cable connector:
View attachment 4571595
Here’s roughly how I proceeded:
Made sure that I’m grounded by touching a grounded metal piece in my apartment.
Removed the SIM tray.
Opened the device according to the instructions by Wit Rigs (youtu.be/1VIdpuXSFmI). Separating the top with the screen was quite hard as it is glued.
Popped out the battery flex cable connector, then the fingerprint flex cable connector.
On my laptop (Windows 7 X64) started MiFlash 2016.08.30.0, downloaded from en.miui.com/thread-345974-1-1.html.
Inserted the USB-C cable that came with the phone into the phone. (not yet into the laptop!)
Using a bent and cut staple, I connected the test points, then inserted the USB-C cable into my laptop.
Windows reported that a new device is connected.
Removed the staple, clicked refresh in MiFlash: A device showed up.
Flashed the latest official stock Android One ROM V9.6.10.0, downloaded from en.miui.com/download-353.html:
View attachment 4571596
Initially I got a message that MiFlash cannot receive a “Hello” packet. It turned out that I was too slow. After connecting the device, one only has limited the time to start the flashing. I read elsewhere that it’s 15 seconds.
Success, my A2 boots up again! Now I’m only waiting for thermal paste to arrive in the mail, I will apply that, then close the phone again.
Click to expand...
Click to collapse
I bought a Mi A2 and tried to put android pie on it, but I failed successfully. I'm gonna try this endpoint method, cause I cant flash images with fastboot.
Unfortunately I can only try this on Monday, cause I don't have the tools, but a friend in college has. I wanna know a few stuff for the grand day:
You told that the device is glued. Is it really hard to open it? and do i need to glue it back?
In the endpoint method, I need to manage to connect the two points with a metal tool, right? And i'll do the process with the battery disconnected, correct?
You wouldn't believe it, but this is my first android and I had it working for less than an hour. I have always being an apple user, but my devices were always jailbroken. I thought that with android things would go easy, but I ****ed them up hahah
As I saw you posted somewhere else, I always like to push my devices to the limit and thats why I am a computer science student...
thanks a lot anyway, and wish me luck on Monday!! Hope I can do it...
zemariolac said:
You told that the device is glued. Is it really hard to open it?
Click to expand...
Click to collapse
I used an X-ACTO knives (careful!), and yes it was somewhat hard to open.
and do i need to glue it back?
Click to expand...
Click to collapse
The A2 is glued with double sided tape going along all the edges. I removed that tape, then applied pieces of double sided tape (red TESA) in select locations. Applying double sided tape along all the edges should be practically impossible to do manually. Notes:
The original tape provides a certain level of water protection. So I’m not sure that it was a good idea to remove it. Between the pieces of tape that I applied there now are gaps, which however are not visible from the outside.
The device can be put together without tape at all, and the screen keeps attached to the body. What happens without tape in situations of stress, I don’t know.
So far everything has been working out fine for me, and my A2 already survived a couple of crashes (don’t use the ugly case).
In the endpoint method, I need to manage to connect the two points with a metal tool, right?
Click to expand...
Click to collapse
Yes. Note that after shorting the contacts, you have limited time to start the flashing. I think it was 40 seconds.
And i'll do the process with the battery disconnected, correct?
Click to expand...
Click to collapse
Yes that’s the recommended method. It also allows you to quickly reset the device, i.e. by unplugging the USB cable.
I always like to push my devices to the limit
Click to expand...
Click to collapse
Same for me! Along the way I learned more than I wanted to. It’s interesting to see the device opened with all its components, removes a bit of the magic.
Anyhow, good luck!
feklee said:
OK, so the test points are below the fingerprint flex cable connector:
Click to expand...
Click to collapse
Why do I see a single camera module on the motherboard?
[email protected] said:
Why do I see a single camera module on the motherboard?
Click to expand...
Click to collapse
Front camera
Benjamin_L said:
Front camera
Click to expand...
Click to collapse
Oh, right. It's the front. My bad.
Typing from my unbricked MI A2!
Thank you for the post. Everything went well. It only took me more time than it needed cause i was trying to flash the comrpessed ROM (yes, I really did it). After that everything worked fine. Remind on your post for noobs like me that you need to extract the file before flashing it!
Hello
I just try the method but me it does not happen anything if I disconnect the battery I tried with several usb cable on several computers on several USB port and it is not strictly nothing
prblem
i have same problem