Hi guys. My little story about my SM-G920W8 (original firmware) :
I went to a waterfall boat cruise and my phone got wet while I was taking some pics. It didn't fall into the water; it only got some spray and that was all.
A few minutes later it started to behave weird, like the buttons were pressed randomically, and weird stuff appeared on the scream (three keyboards kinda overlapping each other, horizontal colored lines, green rectangles, etc). I didn't turn it off and 5 minutes later the phone screen went black and the blue LED got on.
After that the phone got irresponsible at all and stayed with the blue LED on until the battery was dead (+- 4 hours later). I charged it again and nothing happen, until I tried to turn it on in different modes. The only thing that worked was the download mode.
Since I need to recover some pics from this cruise, I tried connecting via usb and using ADB; No success: the phone is detected by the computer (samsung drivers are installed), but "adb devices" doesn't show it at all. I'm not 100% sure, but I remember turning the debug mode on prior to the accident because I was developing an app for it. The phone has been into the rice for the last 2 days, but nothing has changed.
My questions:
Is there any chance to recover the pics from the phone? What else should I try to get ADB working? Is there an alternative for ADB to access the files?
Related
All I can say is; 'Obi Wan Kenobi, You're My Only Hope!'
Here's the deal. Was on vacation, first trip to Jamiaca, and using my phone as a camera. Was relaxing on the beach and forgot my phone was on my chest. Sat up and it landed right on rocks. Shattered everything. No screen, no picture, just lights. For whatever reason, I thought I'd switched it, the new pictures I'd taken weren't on the external sd card.
I'm 2 months away from upgrading so can't see the use of fixing the phone, I had an old LG standby. It's like going back to the dark ages but I can last a little longer.
So the S3 has a 6 digit lock code on it and it isn't in USB Debugging mode. I've tried the following:
Downloaded Kies (shows phone is locked)
Downloaded SDK (doesn't recognize phone)
Downloaded Android Toolkit with proper drivers
Tried to get it to recovery mode (Using Volume + & Home & Power Button)
Tried blindly typing in 6 digit passcode
I've spent a lot of hours so far reading posts and trying this and that with no luck.
My phone is the S3 verizon model SCH-I535
While on vacation my wife dropped her nexus 5 into a toilet in a drunkin stooper, All I'm trying to do is retrieve the photos for now, ill worry about trying to get the phone back to operational after I get some vacation pics off of it.. everything I try to do seems to end up not working or another roadblock.. ill just list step by step what happenned..
-phone dropped in water
-i remove the back cover to remove the battery and seen i need tools and its not easily removed so i left the phone in a bowl of rice for the night.. everything appeared dry on the inside and it wouldnt turn on.
-next day it did power on but the touchscreen was unresponsive, removed battery, reinstalled and a screen appeard that said android is starting and optimizinf app ** of**, would keep nearing the end and powering off on its own for hours.. manually powered off and left for another day in rice..
-plugged in and phone would turn on but would not load, the google sign comes on and gets stuck on those four circles just moving around forever..
-hold the volume down and power button to get in the options screen, try powering off and back on, restarting bootloader and etc to no avail. wiped cache and restarted. still same thing.
-when i try recovery it just goes to android with red exclamation mark.
since i got home.....
-when i connect the phone to computer the mtp? driver wouldnt install correctly
-came to this website...
-installed adb, fastboot, and the universal driver. adb doesnt see the device, fastboot does.
im lost, am i missing something?
phone is still under warranty, is it worth sending in to LG?
Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.
I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead
Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.
I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.
reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?
Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here
Hi,
My customer brought me a phone after a water damage. He claimed that the phone has been working fine for a few days after being dropped into the water untill it has discharged. Now when connected to the charger it just normally shows battery percentage level and is charging fine, but if try to turn it on it just shows Samsung Logo, vibrate twice, again vibrate twice and turns off.
What I have done:
- i've fully dissasembled the phone and clean everything with isopropyl alcohol (99%) (most of the water damage was on the bottom panel with usb charging and LCD connector, mainboard and batterry looked untouched)
- i've put both boards for an hour onto the 100 Celsius board
- after another 24 hours i've reassembled the phone and the problem remained
- I've replaced usb charging board and cabel between it and main board with working ones (still the same)
- I've reflashed stock ROM for SM-A515F Poland (without CSC)
- wiped cache
Nothing worked. Moreover, when I tried to enter Safe Mode the screen went "static"? It just looked like analog TV when you have no signal. Every restart ended up with this "static screen". However when i enter the recovery or download mode it looked sometimes fine. After another Stock ROM flash "static screen" has no longer showed up, but the device still "turns off" after Samsung logo and 2x2 vibrates.
Right now I'm not really sure if it is software or a hardware issue. Had anyone dealt with something like this? Any advice is welcome
I haven't tried factory reset yet, because the customer has many important photos on the device (with no backup :/)
Have a good day!
P.S. Tomorrow i will replace LCD to check if it's faulty. If don't I'll be looking a way to retrieve photos from this bricked phone. It's locked with Google Account and PIN, has not enabled debugging or anything else. Is it possible to somehow restore photos from this phone? Some way to install CWM without unlocking BL (to prevent data wiping)? Then from CWM i should be able to fire up ADB and pull personal data? Has someone any idea if it is possible?
Hi again,
I was so happy that i've fixed this smartphone for my customer that i've forgot i've wrote here
Finally I was able to fix the phone. Even the screen looked fine in the download/recovery modes it turned out that it's faulty. With new screen phone is starting fine and everything works correctly. Here's the link where i show the old screen and new one and how the phone responds: