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
Related
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?
Hi,
my name is Frank and this sad post will be my first post on XDA...
My phone fell off my pocket when i was crossing a road, when i noticed it wasnt on my pockets i went back my steps and saw my phone on the middle of the road but sadly some car passed and my phone got smashed. Now i have my Oneplus One with the screen broken on 100000 pieces. The LCD connector/wire at the top right is broken, i only have half screen left , the rest fell off.
Ok, clearly im not going to repair it. But i have some important pictures that i want to recover, for example photos of my last trip to China and some PDF document.
By now, the phone is turned on, the notification led is flashing, windows 10 recognizes it like "One", Volume UP/Down button is broken, not the button itself, i mean the wires inside, i know it because ive opened the device to take a look. It had a 4 pin code to unlock.
Debugg Mode is OFF, Official Stock Rom (the version is the first one, lets call it "vanilla" i bought the phone on the first days and i never updated)
I used some "handsome" software found in google to recover the data, many of them do not find the phone, others ask for debug mode on.
ADB devices command from SDKPlatforms Tools do not detect any device.
What can i do? Help me please. Sorry for my grammar, but english isn't my mother language
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
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?
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.
s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?