Hello Gurus, my Samsung Galaxy S4 Active AT&T is water damaged. I removed the battery and buried phone in a box of rice for more than 24 hours. The battery is fat now and when I inserted the battery and tried to turn it on, there is no display. However, it vibrated when I pressed the power key to turn and also vibrated when the charger was connected.
I wanted to know what is the easiest way to get the display fixed.
I also want to retrieve data from the phone and my phone was pattern locked. Is it a possible to retrieve data from a damaged phone which is pattern locked?
Looking forward for your help.
If the phone vibrates it means that something it's still alive, but probably not the entire phone. In any case, there is no easier way to change display than another one: if the display is gone than change the display, but you could not know if there is something else damaged, so the expense of the display itself should be useless. However, if the phone is alive you could connect the phone to the pc and try to transfer any data to the pc unlocking the phone with the computer and than copying files
Related
hey guys -
I'll try to give a brief rundown of my situation
When the problem started: I had let the battery drain to a critical level. While at this level, I dropped it on the floor and it turned off. From this point forward, I could turn the phone on and it would start up. The phone would almost fully boot, show the correct time - my current # of messages and everything - but the screen wouldn't respond to my taps and about 10 seconds after making it to the main screen, the phone would do the critical battery failure thing and shut off.
Now here are the weirder specifics
a. when plugged in to any sort of charger, phone won't boot past AT&T screen (but the amber charging light is shown)
b. phone won't recognize a charger once already booted (sort of)
b1. occasionally, if I plug in the charger on the Windows splash screen, the screen will light up a little more (indicating it knows a charger is there) and once windows loads, it will actually show the charger icon in the top right hand corner. but I still get the critical battery failure and the phone shuts off.
c. if I plug the phone into my computer, during those 10 seconds when the phone is booted, I can access the files on it thru ActiveSync. Not enough time to take anything off though, I'm afraid.
c1. if I plug the in charger at any point past the windows screen, I can get an audible indication from my computer a connection has been made.
d. tried charging over night - didnt work
e. tried leaving the battery out over night - didnt work
f. tried fiddling the battery in and out with charger plugged in - no joy
g. used friend's fully charged tilt battery/bought a new tilt battery - nope
I would like to get the data off (I was delinquent backing it off) and am avoiding a hard reset if possible. The phone is covered by insurance so replacement isn't a big deal - it would just be real convenient to get the data off the phone.
If anybody has an idea or has a solution...! Your help would be appreciated VERY much.
- John
try a new battery, but this phrase stands out to me.
"I dropped it on the floor and it turned off"
My phone suffered some water damage and everything seems fine except for whatever piece of hardware checks if the battery is fully charged (is it on the battery itself?). The amber charging light was on for 5 hours and yet my phone would just boot up to the Today screen, produce a Battery Low message and shut off. I had my phone in the bootloader for a few minutes so I was fairly certain that the battery was charged. By some stroke of luck, I was able to use my phone for a short time. The phone recognized that the battery was full and I was able to browse the internet, make calls, etc. When I rebooted the phone to check if this was a permanent change, I found out that it was not. My phone went back to shutting off upon startup.
Is there a registry entry to disable automatic shut off? I could cook a crude ROM with just this registry entry so that at least my phone would be functional.
Or do I need a new battery?
Thanks in advance for your help
im having similar issue but not from water.. every time i use speakerphone the phone dies or using the camera.. this happens most of the time if i use either one.. im thinking its battery shorting out maybee.. once i plug it in via use or ac to give it power its fine.. i have a replacement battery coming so i hope that will fix it
My Kaiser phone also suffered some water damage from a spilt bottle of water. The amber charging light was on for hours and yet my phone would just boot up to the Today screen, produce a Battery Low message and shut off. By some stroke of luck, I was able to use my phone for a short time after the phone recognized that the battery was full and I was able to make calls etc. When I rebooted the phone after charging to check if this was a permanent change, I found out that it was not. My phone went back to shutting off upon startup. Brought a new battery but still experiencing the same problem. HELP
Hey XDA!
Got a problem with my Xperia Z1. It was working fine before the battery swap, aside from a problem with the battery (failing to hold more than 5% charge), hence the swap.
But after removing the old battery and attaching the new one, the phone will not boot, and when plugged into a wall socket, it flashes the red LED in 1~ second intervals. The pow+volume up combination doesn't result in any changes or "3 vibrations", and it won't enter flashboot mode. When plugged into a Windows PC, it registers it being connected, but when the LED turns off, the "disconnected device" sound plays, and it does this every time the LED comes on then off again.
Worst part is that hooking the old battery up doesn't work either!
I'm fairly certain I'm royally screwed but I cannot see clearly why; I checked the phone and anywhere I touched, and I can't see anything wrong. It could be that I was sent a faulty battery replacement and it broke it, or I installed it slightly incorrectly that resulted in the same thing.
Has anyone got a potential solution or am I well and truly screwed?
Cheers!
Phone: Samsung Galaxy SIII LTE GT-I9305
Problem: It doesn't turn on or charge, absolutely no reaction
ROM: Stock KitKat 4.4.4
The phone had the stock KitKat 4.4.4 flashed by me in 2016. For about 4 years everything was ok, it only occasionally hanged up so it needed to be restarted by removing battery or holding volup+power. Also at the end the charging port sometimes caused little problems so it was a lil fussy about the cable. Half a year ago the phone was replaced by a new one, so it was shutted off and put 'as is' into the locker without removing the battery (was fully charged before). Few days ago, when I needed it as a backup phone it doesn't boot up or charge the battery - there is absolutely no reaction. The battery measured by micrometer showed 3.87V - I've fully charged it in an external charger. I also cleaned the charging port and folded back the pins in it. Checked with the multimeter the contracts looks good, the current is able to flow. Anyway the phone is not charging and nothing happens when I'm pressing the power or even the mode combinations volumeup/down key + home + power for more than 30 seconds. It looks like there is flowing a 0.11A current and a battery voltage drops about 0.06V when it's connected to charger and I'm pressing the power button. The power button itself is ok, I've tested it with a multimeter. Nothing changes when I'm connecting the charger directly for the pins for battery.
So I've checked on the web that there is a common problem in that models called "sudden death" so the memory gets damaged after some time if using the stock old kernel. It had the symptoms (hangs, restarts) but I even didn't know about that problem, and I only know that it had a stock KitKat, don't know anything about the bootloader or kernel versions. But is it possible that the phone which was turned off and only laid with battery inserted in a locker for half a year get damaged?
I've tried connecting the usb jig, the "debrick.img" sdcard method (I've created the image by myself with the stock ROM file using a tutorial), the uart connection with both 150K and 560K resistors and NOTHING seems to work. Is there anything else that I could possibly try doing by myself to get it back to work? I'm afraid that the only way is replacing the memory or trying to re-flash it in an external programmer. The phone has MHL and LTE so would be good as an multimedia and web player for an old TV so I would like to save it. But anyway, at this moment it's a hard brick. Please help.
Mmmh i think its memory is dead, my s3 dead same u s3, and no response from anything, I change s3 motherboard with lte version.
Yea, it looks like the most probable cause is damaged eMMC chip on board. I only wonder why it got damaged just lying switched off in the locker, the battery was in unfortunately so maybe that matters. Probably replacing only the eMMC memory with a new, programmed one would fix the problem. Anyway, because it's nothing to be quite sure about, UART doesn't work to make sure about it and the current value of the used working phone is close to the eMMC chip it's not worth it and it's probably time to just toss it out or sell as an parts donor. So sad, that Samsung didn't send any notification about that problem directly to the phone via the notification channel, I had no idea about that problem before. Fortunately I've migrated all the crucial data to the new phone before so it's not a big loose at all. Thanks anyway.
ah Mathey, when my default smartphone was s3 i usually was turn off it when i going to sleep and one day without signal my phone not want turning on when i woke up that morning, i have a charger that do a little beep when a device is conneted to it and s3 was do it but not turn on.
So maybe half a year ago when I was doing data transfer to a new phone it was the last time when the memory was in good condition, sth caused damage and the next boot was not possible, but the time I tried to do that was the few days ago. Fortunately I've moved everything crucial, so it's not a big lost. We could only wonder if leaving the phone with the battery inside can cause the problem or that's something what happens only when the phone is on and after a reboot there is no guarantee it will start up. Someone told me that GT-I9300 with the same problem could be bringed back to life just by USB, but the GT-I9305 have a different memory chip and that's not possible. Only the external programming. Sad but true :|
Essentially, been using LineageOS ROMs since I got this phone two years ago, everything had been working just fine and generally happy with this phone.
The story starts that I had just charged my phone overnight, had woken up, unplugged it and was looking at my notifications.
Opened a WhatsApp notification, instantly the launcher seemed to crash and was unresponsive, although the notification tray was functioning still. Tried to turn off the phone via the power menu, device did not shutdown. Forced power off on the phone, phone turned off.
Immediately I was unable to turn the phone back on. Tried recovery, fastboot boot methods and the device would not turn on at all. The screen is black and the device not responding to anything power related button combinations. When I plug the device into power, no charging light appears on the phone, the screen doesn't turn on at all with the typical charging animation when it's in the off state. When I plug the device into my Ubuntu machine, no USB device is detected by the kernel - as though nothing is plugged in at all. When I plugged it into my battery pack however, it did appear that it detected a device and flashed it's LED as though it was charging a device that was plugged into it.
I had not wet the device, or *recently* dropped it. It lives in a pretty reasonable case and has stood the couple years of my use with essentially no scratches other than some very minor abrasions on the screen.
I have a little phone electronics tool kit and a hair dryer, and as the battery was fully charged before this had occurred, I decided to pull the phone apart and disconnect the battery from the mainboard behind the NFC assembly. I also tried disconnecting the power charging circuitry in case something was shorting in that area - still nothing. Left the device with the battery unplugged from the mainboard for 5 days, and just tried it again - still no dice.
I'm just wondering if anyone knows what the cause might be. At this stage, I'm suspecting a mainboard failure, in which case data recovery seems unlikely. I have had over two years out of the device, it's far from the end of the world. I'm reluctant to spend any money trying to repair it particularly if it's the mainboard, I'll lose my data anyway. If I were able to retrieve the data from the device that would be of some benefit to me, about a weeks worth of photos and some chat history with my GF; so some questions I have:
1. Should I be able to power on the device with a USB C cable plugged in but the battery unplugged?
2. Apart from what happened above, does anyone have any suggestions about the cause remembering that it doesn't turn on into any boot mode at all?
Do you have any windows device?
jjgvv said:
Do you have any windows device?
Click to expand...
Click to collapse
No I don't sorry. I also bought a new battery for the Mi 8, the device still didn't turn on or charge. I think I can safely say the phone is cactus.
berglh said:
No I don't sorry. I also bought a new battery for the Mi 8, the device still didn't turn on or charge. I think I can safely say the phone is cactus.
Click to expand...
Click to collapse
you are probably in edl mode and linux does not kinda very like edl mode
Hi, I have the same problem, but with the latest Xiaomi eu stable. I just put my phone in my pocket after a full charge and when pulled it out just a black screen and now it's exactly like yours
Did you solved the problem?