Related
It happend while I was taking my cloths off for taking a bath
I dropped it inside our WC and my 2GB SD Card was gone far away inside that damn WC and never found it
I tried to pull out the battery but I couldn't pull that damn battery out for 5 min.
Anfter 5 hours drying with a hair dryer I put the battery and other stuff back and there was NO life After pushing the softreset hole some 10-20 times and putting it to charge there was a little life back some blue lines at the screen.
Now after 5 more hours it starts, but after some resets (some times there is only blue lines) and when it starts it freezez very much...
Should I send it for repairing?
Does the worranty covers it? (I bought it from Internet)
Would reflashing help?
Please advice...
tbh, I would have left it to dry normally in a warm place for 24 hrs before even considering to power it up, as (not 100% certain) I think the hairdryer creates static, which could damage the electronics inside, plus, you can't guarantee that it will have dried it out completely, which means, when you started it up, it could have still been damp in the middle and damaged something.
does it look like it has been water damaged? if not, then your best bet would be to not mention that fact, and just say it has suddenly started being funny, not booting up and freezing alot.
I doubt a reflash will fix it, but it is something for nothing, so worth a shot, however long it is.
*edit* if the company won't replace it, you could try your house insurance...
Thanks alot for the reply wytey,
I think there is something damaged, becouse when I soft reset it after freezing there comes a couple of times a light blue screen with blue and white lines...after soft reseting 3-4 times again it loads normaly again but freezez after 5-10 mins again
I was soo happy with my Jasjar >:'(
Your device has been damaged by water.
This is not covered by warranty.
It might not be covered by any insurrance you might have through your service provider.
You may be able to get it covered under home insurrance.
There isn't a case for a wet PDA. But I've read a recent article of getting back a Linksys router that has been soaked wet by rain water. See the real life experience here
http://www.grynx.com/index.php/projects/salvage-your-device-after-liquid-spill/1/
Probably you can do the same?
I dropped my Wizard in the bath, took out the battery and let it dry for about a day or so. Evrything works just fine.. So you should have dry it for over a day or more to be shure no water is left in it
Very timely.
http://www.lifehacker.com/software/hardware/save-your-electronics-from-spilled-liquid-150085.php
V
Thanks for replies guys,
Usefull article, but I think it's too late now, I couldn't take out the battery for 5 mins, then how to open the device and clean the components/circute
Can they prove it if I don't mention water?
Home insurrance would be a big lie, but who cares they get money from me every month (what to say to them? stolen? bropped in water?)
Thanks again for your times guys
I may be wrong , but I beleive there is an "indicator" in most modern equipment that shows up if there has been any water damage
anyone who knows how to repair phones and look at pcb boards etc. will KNOW right away that it has been water damaged. Impossible to hide (unless you yourself are also a technician).
I know because I own a phone repair shop and have been doing repairs for a lot of years.
One of the IC may be damaged, so when your device starts to get warm (as you said 5-10 mins) it cannot hold the power.
Just think yourself lucky that it's only an IC and not a CPU.
E-mail me on [email protected] if you need more help and advice
hb328_dtdd said:
anyone who knows how to repair phones and look at pcb boards etc. will KNOW right away that it has been water damaged. Impossible to hide (unless you yourself are also a technician).
I know because I own a phone repair shop and have been doing repairs for a lot of years.
One of the IC may be damaged, so when your device starts to get warm (as you said 5-10 mins) it cannot hold the power.
Just think yourself lucky that it's only an IC and not a CPU.
E-mail me on [email protected] if you need more help and advice
Click to expand...
Click to collapse
THanks alot for the info hb328_dtdd
If it's an IC, is it hard to repair it? how much would it cost me?
thanks
I (or whoever you decide to check the device) will have to open the unit up and clean out the residue of water and then do thorough tests first, it may not be an IC problem, even if it is an IC problem it may not actually be broken and will work again after cleaning and sonic waves passed through it.
Depending on which IC is broken and how hard it is to replace it, and also if it has caused any other side effects to the other chips, the repair in theory should not cost too much at all as it does not seem serious (from what I read from your post anyway).
E-mail me with more description of the problem and I will try and give you some tips to get it running, if that fails then you can decide whether to send it away or take it to local engineer to repair.
Hope this helps
the Gadget (Ch 5 UK )show did a piece on stuff getting wet. I htink they all came back to life one way or another but the were left to dry slowly I think for a day or 2. so you could hold out for live in the thing yet?
I hate the fact that Dopod 900 is very slippery, don't you think? I'm looking for a rubber casing like the one for O2 and Ipod.
Dopod 900 enclosure is too slippery, I'm so worry I may drop it too.
I am selling some Pocket PCs and this happened to two of my customers. But the device was an Ipaq 37XX and 38XX.
Both devices I put on a warm place and left there for 4 days. Then after this I powered them up. The Ipaq 37XX had only a bad LCD light, which was flickering sometimes and was not bright. the 38XX worked good again.
Anywasys, you need to check your device and have it cleaned. The biggest problem is the fact that there is so little space between smd mounted chips and the PCB that the water stays in between never drying and makes the metal rust. I had this experience with a cell phone already.
So you can try following:
(1) pay for cleaning and repair
or
(2) try to get it guarantee exchanged, which is also possible as for a pocket pc the technicians normally do not check for water damage. But if you have bad luck, somebody will notice this and you get nothing replaced.
I managed the same thing a while ago with my Xda2, and the symptoms were pretty much the same when it first happened (random lines and 'blotches' across the screen, freezing)..
Without haste, I removed the battery, sd card and mopped up any moisture from inside the battery compartment.. placed it in a warm place in an attempt to evaporate the moisture from the device. I left it for 24 hours before powering the device back up.
It DID work afterwards and I was a bit suprised and relieved at its resilience to liquid.
The important thing is to make sure the board and pins of the chips are not shorted by liquid, if you cannot get to the board, evaporation in a warm place is probably your best bet...Just watch out how you apply heat for the sake of the screen (and possibly the keys on the exec).
I dropped my XDA II into a canal and managed to save it. The problem is the water can't evaporate easily. I took the battery off and put it on a radiator. It took 7 days to finally dry out! It worked ok though.
You probably still have water in yours, so I would recommend putting it on a radiator or somewhere hot and just leaving it. You haven't got anything to lose
After almost 2 days inside the radiator it still has the same freezing/dying problem I thinks something is damaged inside ((( And now I can't find any electronic service in Denmark who can repare it
just because it's dry doesn't mean it fix itself, people often mistake this. Sometimes people get their phones to WORK after it's DRY but little do they know what is really happening inside the phone each time they power it back on and the residue is still there inside the phone lurking in the spaces between the pcb and the chips.
no matter what anyone says, I always tell people the same thing:
YOU MUST GET IT PROFESSIONALLY FIXED
My suggestion and this has never failed me yet.
1. After being dropped in liquid, DO NOT SWITCH ON - This is where most of the real damage will occur. If it is/was switched on remove battery as quickly as possible.
2. Strip down and remove any thing you can do easily, covers, sd card, stylus, sim, battery.
3. Waste a whole aerosol of switch cleaner, squirt it anywhere and everywhere you possibly can, literally fill it up with the stuff so it is pouring out of every hole. Do NOT use WD40, it must be electrical switch cleaner that will leave no residue at all!
4. Allow as much as possible of the switch cleaner to drip out and then allow it to dry, do not force dry with a hair dryer and even a radiator is too harsh. I find airing cupboard where the hot water tank is is the best place.
5. Leave at least 48 hours before putting everything back together and switching on, if it does not work straight away, strip it down again and leave another 24 hours, keep repeating for 7 days.
http://www.maplin.co.uk/Module.aspx?ModuleNo=27515&criteria=switch cleaner&doy=29m1
Good luck!
Gurus,
I am one of the unlucky ones who experienced the unforgiving flashflood courtesy of Typhoon Milenyo here in Los Banos, Laguna. In the haste and confusion while trying to save anything i can as the water was rising inside our house, i forgot all about my lovely xda. I found it submerged for about an hour under 3 ft of murky water. I left it to dry for 4 days. Only when the electricity was back was i able to open, thoroughly clean and dry the poor thing with my wife's hair dryer. Praying all along that the cleaning and drying would resurrect it back to life. I was hopeful that the motherboard would survive the beating but not the LCD. Usually it's the first thing that conks out when water is the culprit. The battery was also damaged - it bloated, so there was no way i can test if my phone was still functional.
I went to SM Megamall the other day in search for a battery that I can use to test the phone. There was a store that fortunately had a battery that wasn't sealed. And surprise! surprise! The phone sputtered to life! The LCD was working. I heard the beep sound that you hear when you hard reset the phone. So the speaker was working too! BUT, the thing stopped right after that message that says something like touch the screen to proceed with the setup. And it kept on restarting every 2 minutes - hangs, restarts, hangs, restarts. The water might have corrupted the ROM and the software wouldn't load. Or probably something else. I'm a bit hesistant in buying a new battery unless the phone would still work by flashing the memory and restoring the software. (If only i can borrow someone's spare battery to see if it is still possible to flash this before i buy a new battery). Hmmmm....
What do you think guys? You think the memory just needs flashing to get the xda running again?
qtek 2020 splashed
Hello from Italy, my qtek 2020 splashed (adverse effect of holiday) and then it had the same problem, when resuscited the "object" never charged radio rom but only the other parts of extended rom also after hard reset appair the script "no gsm" and the telephone don't play.
Than the object only play like a pocket PC without phone and other radio application (gprs, blu etc...). Sorry but i think is necessary to change the main board. Good holiday.
ok so what happened was is that i dropped my phone although when i looked at it it seemed fine, not even a scratch, calling worked...but a couple of hours later i got no signal in this place although my dad had signal and we're on the same network and we have the same phone too. I received signal as soon as I left the place.
And here is where my problem comes, everything was working fine and i had my phone in my pocket for the whole day cause i was at school and after school i decided to take a look at the time, but my phone was off and wouldn't turn on, but i expected that it ran out of battery.
I got home and tried charging it, but nothing happened, so i decided to use my dad's battery (fully charged) it still wouldn't turn on, i've tried soft/hard resets still nothing.
can it be the hardware? what is broken? it won't turn on/won't charge/no led lights/no red led when charging without battery/ nothing so what is wrong please help.
Probably battery contacts... If you can see a crack, you might be able to resolder them and fix however the Hermes uses a multi layered board and if the break is there then you need a new mainboard, in a few words, your Hermes is toast....
is there any possible fix? if the board is broken, where can i get a replacement and instruction on how to fix? thanks :]
Find an old Hermes on ebay. If the screen doesn't work or something, DON'T get one with "No GSM", then you should be able to replace the Mainboard.
Find the HTC Service Manual here - http://michael-channon.spaces.live.com/PersonalSpace.aspx?_c02_owner=1
You need a size 6 torque key and a small flatbladed screwdriver to get the Mainboard. Pretty easy, I've taken my Hermes apart more times than I can count.
Cheers...
thanks for the help so far :]
but is there a site that just sells the part? cause i really don't want to end up buying a mainboard on ebay that ends up not working too.
Hi there, people.
I am having a weird issue with my Note4.
After tons of reading about it(here and all over the net), I don't seem to be able to fix it.
So... here's the situation -
I tend to put my phone next to me in bed, on charger, when I go to sleep. One morning I woke up and I saw it continuously restarting, only managing to get to the "Galaxy Note4" screen.
It was running 6.0.1 stock the last time it worked.
I've played with my old Galaxy S2 before and got some Cyanogenmod (and other) ROMs on it. So I decided to try to fix this one. I googled about the issue and tried a few things, but was left a little baffled, since I was unable to enter Recovery mode.
So basically I was left with the only option to reflash stock rom with ODIN. I did, but nothing really changed.
I saw on the net, that commonly this is a battery issue. I was almost sure it's that, so I went to a shop and tried booting it up with a brand new battery. Didn't work out, nothing changed. So I decided not to get a new battery, since that wouldn't really change anything.
Therefore I decided to bring it to a local phone repair shop and have it checked by someone more skilled at this.
I did, and few days after I got my phone back, in a working condition, back to 6.0.1 stock (just as it was before). The repair man said that it was pretty messed up but he managed to get it back running. Apparently, he reflashed it few times. At least that's what I understood.
Nothing has been replaced in terms of hardware.
Few HOURS after I got it back from the repair shop, I was just randomly browsing on it, and it decided to restart itself and went into bootloop again.
Recovery mode was once again, non-available.
I set it aside for few months, since I was really busy with work and had no time to spend on it, and used my old S2 in the meantime.
Recently I picked it up again to try to fix it. What I noticed is that when plugged into USB (doesn't matter if PC or wall charger) it does not show the Battery charging icon, but it's either off, or boot looping.
It apparently charges while looping, because the battery is not dying even after hours of this.
I decided it might have something to do with the charging/power PCB module, so I got a spare and replaced it myself. Unfortunately it made absolutely no difference.
Some facts, so I can cover most of the questions you might have:
-It has no microSD/SIM card inserted.
-When I got this phone it was on 5.0.1 and after few months of use I updated it to 6.0.1, using the regular procedure.
-No custom ROMs or anything unofficial has been flashed on it.
-Power button is fine, it does not power on by itself, hence it's not stuck or anything. I took the time to actually remove the power button module (with the vibrator) and power it up with the battery insertion method. No difference.
-The rest of the buttons are also fine. Vol Up/Down both work in Download Mode, Menu Button also works as expected.
-ODIN manages successfully to flash whole packages of pretty much any N910C 6.0.1 firmware I tried. (and the TRELTE_EUR_OPEN.pit, with or without NAND Erase All) That changes nothing. (hence why I suspected a power module issue, not a software one)
-I tried pretty much any version of ODIN, and this also made no difference.
-Changing to a new battery does not resolve it.
-By some chance it managed to go into Recovery ONCE (with a freshly reflashed 6.0.1 firmware) and I did wipe cache, but this changed nothing. Since that, I never got into Recovery again.
- In Download Mode it says:
ODIN MODE
PRODUCT NAME: SM-N910C
CURRENT BINARY: Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1
RP SWREV: 2
I am running out of ideas.
I'd really love to hear your thoughts on this, since I really like this phone, and I have the feeling it might be something simple software-wise I'm missing.
I had a similar problem with Note 10.1 (N8000). It went into infinite loop. I could boot into download mode with buttons but not into recovery. So I just flashed a TWRP recovery and everything has been fine since then...
falconsson said:
I had a similar problem with Note 10.1 (N8000). It went into infinite loop. I could boot into download mode with buttons but not into recovery. So I just flashed a TWRP recovery and everything has been fine since then...
Click to expand...
Click to collapse
I tried that too, but it doesn't seem to work. I get the "RECOVERY IS NOT SEANDROID ENFORCING" in the upper left corner.
I am doing it according to this guide (which uses twrp-2.8.7.0-treltexx.img.tar):
rootmygalaxy.net/install-twrp-root-samsung-galaxy-note-4-android-6-0-1-marshmallow/
I also tried with the latest twrp version released... same SEANDROID error in the upper left.
Am I doing something wrong?
boogiesamy said:
Phone should work with stock recovery, for sure you issue is a hardware one
Click to expand...
Click to collapse
I am considering this outcome.
Although, I hope someone can shed some light, why with TWRP's version for N910C 6.0.1 it still gives me the seandroid enforcing error...
I have installed many ROMS, allways with TWRP, and every time I've had "Recovery is not seandroid enforcing" without any problems.
If you get that message then you succesfully installed a custom recovery.
As somebody said before, it seems like a hardware problem.
boogiesamy said:
because before flashing twrp you must enable oem unlock and usb debugging from developers option
Click to expand...
Click to collapse
Yeah, but how if the phone is bootlooping?
@faeterov thanks for clarifying!
mstoynov90 said:
Yeah, but how if the phone is bootlooping?
@faeterov thanks for clarifying!
Click to expand...
Click to collapse
I have flashed TWRP recovery many times on different phones including N910C, i don't remember doing anything about USB debugging and OEM thing. Anyway, I can recommend something like flashing a custom rom, try if It doesn't do anything then, I will be sorry to give you the idea. Thank you...
PS: About the SEANDROID error in the upper left, there is nothing wrong with that error. If your recovery is not original then that error will be there. Which is not an actual error... I have it too...
Try to flash Twrp, then try a custom ROM.
Also try to flash supersu 2.78 SR5 through twrp if it works. Sounds silly but sometimes after flashing root the phone will boot.
Good news, people.
I managed to fix it in the weirdest way possible.
Maybe some of you have heard of this method!
Since I accepted the fact that the mainboard might be the culprit and I had no other options left, I decided to go for it.
What followed might sound pretty scary and illogical to some, but oh well:
- made sure all residual electric charge is discharged (removed battery and hold buttons for a minute)
- disassembled the phone.
- removed the mainboard from the frame.
- removed all the modules that allow removal (front camera, rear camera, earpiece, etc)
- soaked the mainboard PCB in window cleaner
- rinsed it with warm water, thoroughly
- wiped off
- left it under the air-conditioner to dry out for about an hour
- cleaned it up thoroughly with rubbing alcohol
- let it evaporate
(here comes the scary part)
- fired up my kitchen oven to 200C on a ventilated mode and let it heat up
- wrapped the mainboard in aluminium (kitchen) foil with the shiny side out
- made two rolls of the foil and put them on the oven rack
- set the wrapped up mainboard on the rolls
- closed the oven door and left it in for 5 minutes exactly.
- at the end of the 5th minute I opened the oven door and shut the heating off.
- I left the oven fan running and the oven door open for about half an hour until the wrapped mainboard SLOWLY cooled down to room temperature.
- unwrapped it, put the modules back on, connected all the wires and screwed it in the phone
- BOOM it booted up, without a problem whatsoever.
- I'm a happy camper
So, to summarize and explain -
This method is called reflowing. What it does is that it slightly melts the solder connections inside the PCB, and resolves microscopic cracks and bad connections, which might have been caused by extreme heat or cold.
(which turns out to be one of the main reasons for such bootloop issues, as many people just wake up to a looping phone, after it has overheated in the warm bed)
Professional electronic engineers have actual reflowing ovens that bring the PCB inside through some very specific temperatures, way more accurately than a kitchen oven, so it produces way more reliable results.
Of course 200C is pretty hot, so any plastic parts that can be removed, SHOULD be removed, or they might melt and you really don't want that. Good example for this could be the front camera, which while probably having a glass lens, it has a plastic housing which will probably go soft and render the camera useless, if not break it completely.
Reflowing should not be done to components you suspect might have just a software problem.
It is pretty much a russian roulette if you're gonna get anything out of the oven, that is not baked and dead.
I might have been lucky, and I probably am.
Therefore I want to say this out and loud:
============
THIS IS NOT A SOLUTION OR A REPAIR GUIDE BY ANY MEANS. I DO NOT SUGGEST IT TO ANYONE, I AM JUST SHARING MY PROCEDURE.
THERE'S NO GUARANTEE THAT YOU'RE NOT JUST KILLING IT COMPLETELY BY ATTEMPTING A REFLOW.
YOU SHOULD ATTEMPT THIS ONLY IF THERE'S NOTHING ELSE TO BE DONE AND YOU'RE PLANNING TO THROW IT AWAY.
============
So... now for the reflowing enthusiasts:
-aluminium foil wrap is there to spread the heat evenly and protect the components from direct heating
-aluminium foil rolls are there to keep it off the metal rack so it doesn't get a massive heat transfer from its contact with the rack.
-water/alcohol/windowcleaner rinsing is fine for electronics as long as they're not powered. (water leftovers can cause oxidation of metallic components, so make sure it dries out well)
-make sure the board is completely, completely, completely dry, before plugging it back in. Water drops could settle in the metallic hollow chip guards/heatsinks (i suppose that's what they are)
-do not just remove it from the hot oven, as you may just reintroduce new micro cracks by subjecting it to a sudden temperature change. Let it cool off on its own first.
-be careful as some components on some PCBs can emit some pretty poisonous fumes. Ventilate the area and give your oven a good run after that, to make sure it's all gone, before you decide to cook in it again.
- and MOST IMPORTANTLY - if you have any suspicion it might be a software issue, do not bother with this destructive method. You might break it even further or even kill it off, completely.
DISCLAIMER - I take no responsibility if you decide to go the reflowing road.
Any questions are welcome!
Anyone manage to resolve this problem ? I mean beside that weird solution
Agreed - reflow is little bit risky but it comes handy with micro cracks. This method also helps to improve performance after mmc memory fail.
In Androidbench app I still got around 30MB/s when it should be above 100. I've heated my motherboard on 140 deg for 5minutes and will try with 180 right now. Fingers crossed and do not try this if you're not ready to your phone be another brick in the wall
Edit: tried reflow again on 200deg for 5minutes and amazing results! Memory speed increased from 30MB/s to 190MB/s! If you're thinking about buying new motherboard you should try with this method - at worst scenario you will buy a new motherboard.
Mind to wrap in aluminium sheet and leave it to cool down in cooker for 10-15 minutes just like author said
Hi all,
last week we had a really heavy rain and I was outside. As a precaution I put my phone out of my front pocket into my backpack only to realize that the backpack was filled with water when I came home.
The phone was swimming in water but still on and working but I had no equipment to open up the phone (damn T3) so I had to leave it powered on and put it in rice over night.
The next day when I tried to boot the phone the screen stayed off and you could see the liquid between the lcd and the digitizer.
I went to a local repair shop and they opened up the phone. I let it dry for some more days but the problem with the display remains.
I washed out the mainboards with iso and cleaned all corrosion I could see with a toothbrush but after replacing the screen it looks like the issue remains.
The phone makes sounds like it is working and giving notifications but the screen is just dead.
Do you have another Idead what I could do or do I need a new phone?
Thanks
crckmc
I am in the exact same boat (almost literally)
I dropped mine into the toilet (how cliche) and it also worked for a few minutes, then eventually the screen went black. I see nobody responded to you here, may I ask what have you ended up doing with it? Replace screen? Get a new phone?