I've got a Sprint Galaxy S6 SM-G920P (original stock firmware) which I was doing a routine battery replacement on, but when I reassembled it and tried to power it up, it got stuck with a dark screen and throbbing blue indicator LED. I'm not able to do a volume-down + power reset, and I tried multiple times to boot into safe mode, but with the screen black I can't tell when to push volume down.
When I connect it to a PC via USB, it's detected as a USB device but does not link up as an MTP device, so I can't access the directories, and KIES won't work. I installed android-data-recovery, but the SM-G920P was not on the list of devices for broken phone recovery.
I've written the phone off, but I'd really like to recover the photos. Any ideas or suggestions? I don't mind soldering.
Thanks,
LR
larry5b6 said:
I've got a Sprint Galaxy S6 SM-G920P (original stock firmware) which I was doing a routine battery replacement on, but when I reassembled it and tried to power it up, it got stuck with a dark screen and throbbing blue indicator LED. I'm not able to do a volume-down + power reset, and I tried multiple times to boot into safe mode, but with the screen black I can't tell when to push volume down.
When I connect it to a PC via USB, it's detected as a USB device but does not link up as an MTP device, so I can't access the directories, and KIES won't work. I installed android-data-recovery, but the SM-G920P was not on the list of devices for broken phone recovery.
I've written the phone off, but I'd really like to recover the photos. Any ideas or suggestions? I don't mind soldering.
Thanks,
LR
Click to expand...
Click to collapse
Have you had any luck recovering the data? I have a stock Galaxy S6 from Sprint with a broken screen. No screen lock is enabled, no passcode. I don't have ADB debugging enabled on the phone so all the recovery software out there isn't working. If I somehow figure out how to recover anything off of this phone I'll let you know the steps I've taken
atvcache said:
I don't have ADB debugging enabled on the phone
Click to expand...
Click to collapse
As long as you cant't establish an USB-connection ( read: ADB connection ) you can't revover any data: ADB is the door to any Android device.
jwoegerbauer said:
As long as you cant't establish an USB-connection ( read: ADB connection ) you can't revover any data: ADB is the door to any Android device.
Click to expand...
Click to collapse
I figured as much for as long as I can remember ADB yes has always been the doorway. It'd be nice if ADB was a built in software standard, not only an option you can choose to turn on and off but with security features that would enable people that break their screens to still be able to access their data with a code only verified owners can get from their service providers or manufacturers, it would also stop criminals from being able to access peoples data. ADB is an outdated/old standard in my opinion. In concept it's great but if you don't have it turned on what good is it.... if you need access to your phone through an OTG cable. If you do have it enabled and your phone is stolen, screen locks can be bypassed. We need a new type of ADB, hopefully that becomes a thing in the near future! How many people are tech-savvy or even interested in these type of things, less than the majority. How many people lose memories along with other forms of data and money because of these old standards.....
Related
Hello everyone.
My S2 had a water-damage. My friend wanted to be kind to wash my pants after spilling some tomato-dinner on it, so everything got to rumble a bit in the washer
Then, the only thing that doesn't work is the display.
It's all black, but the boot-sound comes, I can swype away the lock-screen (of course without seeing it) and with a bit of coordination turn it off ..
It's detected in Windows 7 as Composite Device and Modem. I had it detect "ADB Device" at one point, but it wouldn't show up in "adb devices" whatsoever, since then Win has only detected Composite and Modem.
I also tried to boot it in recovery mode, since another brand new S2 I got can actually ADB in Recovery with XWKI8 firmware delivered stock, although this doesn't work for the broken one, or maybe I just haven't reached recovery yet, I am trying to count seconds of booting to time it right, most of the time it just boots fully with boot sound if I keep holding vol+home ..
I am thinking if I could put some custom kernel on it by putting it to download mode, or somehow reach a state where I could transfer files with the display off.
Any ideas?
And is the phone in USB debugging when it shows as Composite Device / Modem or is this a bad sign of driver-fault, bad recognisition, or is it indeed a confirmation that the phone is in debug-mode?
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Thx Red_81, again. Glad to see u put this here for the i777. Appreciate u sharing this. It should provide some good help for many users. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium
So much easier than trying to explain how to install the sdk and then what commands to run. The only problem is you need to have working drivers.
Sent from my SGH-I777 using xda premium
Red_81 said:
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Click to expand...
Click to collapse
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
lambition said:
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
Click to expand...
Click to collapse
Never mind. I just got it working.
Had to just enter adb command directly. wait-for-device is not working for my phone for some reason.
If you get stuck there again, unplug and plug in the device again.
Sent from my SGH-I777 using xda premium
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Phalanx7621 said:
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Script already does that
Sent from my SGH-I777 using xda premium
Thanks
Thanks i was tinkering with a noria 7" tablet, which hasn't worked right since i got it but for 65 bucks its to be expected, but i used sdk manager to get it to register on my computer as an android adb device and for some reason i tried to turn the wifi on and it crashed and got stuck in a boot loop idk why. like i said hasn't worked right since i bought it. But i did use adb portable like you said to get into recovery mode and it worked great thanks! For other noria users when i figure out how to flash a rom to it i'll start a section here on xda as soon as i figure it out. Thanks again
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
BrockSamsonFW said:
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
Click to expand...
Click to collapse
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
creepyncrawly said:
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
Click to expand...
Click to collapse
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
BrockSamsonFW said:
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
Click to expand...
Click to collapse
It's pretty difficult to recover information from the data partition when the phone is in a state such as you describe. Maybe the developers and technogeeks can do it. I can't. However, depending on where the game saves it's game data, you may be fine. If the game data is saved to the USB memory (internal sd card) then it will still be there once you flash new firmware. Your pictures should also be fine, since they are on the sdcard.
Hopefully this is the right place to post this.
I have a Samsung Galaxy S4 (completely stock as it is my work phone), however I have some personal data on it (photos etc.).
The screen and digitiser are completely broken, however the phone still boots; I'm just unable to see what is occurring, or interact with the device.
The device broke without USB debugging enabled, so I am unable to use adb to access the device. I have tried booting into both recovery and download modes (but I have been unable to access using adb regardless of mode). The device is also not set to act as USB mass storage, so it only displays as a media device within Windows.
I have also tried using Kies to access the data, however I receive a message saying that the phone needs to be unlocked. Obviously I am unable to do this, as neither the screen nor adb commands work. Using the Samsung website to unlock the device is out of the question too, as I do not have a Samsung account.
In addition, I have tried booting into download mode and using ODIN to flash ClockworkMod to the device, but ODIN was unable to connect.
I do not have another S4, so swapping the screens temporarily isn't possible, and obviously using an OTG mouse wouldn't work, as I cannot see the screen.
I am really at a loss here, is there any way I can get the data off of this device?
Any help is greatly appreciated.
Only way without replacing the screen is going to be a custom recovery and adb at this point. I'm hard pressed to understand why Kies recognizes your phone but Odin doesn't. Only thing I can think of is that once you boot to Download Mode via Power + Home + Volume Down is that starts the caution message about installing custom stuff and you need to hit Volume Up at that point to continue to actually be able to use the mode. Either that or check your Device Manager for driver issues as the driver loaded for that is a little different than like for MTP.
es0tericcha0s said:
Only way without replacing the screen is going to be a custom recovery and adb at this point. I'm hard pressed to understand why Kies recognizes your phone but Odin doesn't. Only thing I can think of is that once you boot to Download Mode via Power + Home + Volume Down is that starts the caution message about installing custom stuff and you need to hit Volume Up at that point to continue to actually be able to use the mode. Either that or check your Device Manager for driver issues as the driver loaded for that is a little different than like for MTP.
Click to expand...
Click to collapse
The only way I can tell it is in any mode other than normal boot is due to the red LED. After the first vibrate I repeatedly pressed Volume Up to ensure I'd got past the disclaimer, but obviously I'll never know for sure.
I found a tutorial for flashing CWM, however it was for an older version of ODIN (3.07). It mentions to put the CWM tar file in the "PDA" field, however this field is not present in the newer version (3.10 I think?).
As such, I was unsure how to proceed.
PDA is now the AP slot in newer versions of Odin.
Thank you, I'm going to give it another go today.
Does the device need to be rooted in order to use ODIN? I've used it once before but it was a long time ago, so I don't fully remember.
I also don't want to void the warranty on the device, as it's technically not mine.
Root is not necessary to use Odin, however, if you are able to install a custom recovery, and your phone has Knox, it will be tripped, thus voiding the warranty. There are plenty of people who have returned phones with it tripped without issue, but no way to guarantee they won't care. Most likely since it's obviously a physical issue, and not from any attempt at modding, they shouldn't care. However, they do reserve the right to refuse warranty claims if they so chose.
Just in case anyone comes across this via Google, I managed to get my files using the following method:
First, I loaded up Samsung Kies on my PC, and plugged in a standard USB male to microUSB male cable.
Then I used an OTG adapter (USB female to microUSB Male) and plugged a USB keyboard into the phone. After a few attempts, I felt the phone vibrate when I typed my PIN in and pressed return.
I then quickly unplugged the OTG cable from the phone, and plugged in the PC USB cable. This allowed Kies to connect to the phone, and I was able to pull my files.
Hopefully this helps someone if they are having the same issue.
Good work! Glad you were able to find a solution.
Hi all,
I wonder if somebody could help me.
At the moment I have a Z5 compact with a broken screen (totally black) and touch. I know it still can boot, because it responds to my fingerprint when booted up. However, it does respond to my finger, but still needs a patern on first boot, which I cannot do on account of the broken touch screen. Also, my computer detects the phone.
I want to access my data, but for that I would have to use the onscreen menu which pops up when I connect the phone with usb. That's impossible.
I looked around on the internet and it is possible to remotely control the screen or access via adb. However, for that I either need to install some app on the phone, enable usb-debugging or authorise access via adb. All of those are impossible.
My phone has un unlocked bootloader and is rooted, so as a last resort I've tried to flash a modified kernel to enable usb debugging by default. This fails. Probably because I make some mistake in modifying the kernel, but I don't know. There's not a lot of response from my phone, as you understand ... Besides, I've absolutely no experience modding myself.
Anybody any idea, please?
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
The Z5C isn't the easiest phone to take apart but it's not that difficult either. Just requires some basic tools (Hair dryer, tweezers and some precision screw drivers). There's a bunch of videos showing you how on ifixit or youtube. You just have to go all the way to the part where they flip over the motherboard and unplug the two ribbon cables, one of those two will be the culprit.
This is the first and only phone I've taken apart so any amateur can do this.
Boot to recovery and connect your phone to PC
Nutchos said:
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
Click to expand...
Click to collapse
Yes, actually I've had problems with a broken backlight before and opening the phone and re-adjusting the cable solved that. Not in this case however. Thanks for your suggestion, anyways.
mlleemiles said:
Boot to recovery and connect your phone to PC
Click to expand...
Click to collapse
Would recovery provide me with some way to enter my pattern via a PC, e.g. with ADB?
Actually, I'm not sure I had any recovery installed at all. I've tried this before and just tried it again. I press the on/off-button while holding volume down. After that no response whatsoever. My computer does not see any device when connected. I suppose my recovery does not work properly, but without screen I can't be certain.
mlleemiles, you are a _hero_!
After reading your post I decided to try flashing another recovery to try if that might work. Now I can access my files without ever having entered any pattern .
Nevermind that it turns out my files weren't encrypted and I thought they were.
If anyone has a similar problem in the future, this is what worked for me:
My exact situation:
- My phone runs a stock rom (downloaded from XperiCheck) with version 32.4.A.1.54. When my phone was still running ok I had the bootloader unlocked and my device rooted with Rootkernel.
Working solution:
- I downloaded Twrp, version 3.2.1, from this page:
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
- Shut down my phone by disconnecting the battery and reconnecting it again
- Started my phone in fastboot mode and flashed recovery to my phone with:
Code:
fastboot flash recovery recovery_suzuran_220218_2.img
- Booted my phone in recovery with volume down + on/off-button.
- Connected my phone to my PC, et voila.
Turns out I can also access my phone with ADB as root, so after backing up the entire internal memory, I might try to get some remote screen tool working.
So thanks for the help and if I find something interesting and new, I'll post that too.
Small update:
After successfully flashing Twrp I backed up the internal memory, so must of the important stuff was safe by then.
However, it turned out that my phone now wouldn't boot into anything other then Twrp. I decided to flash my rom again. First I installed my apb keys using Twrp:
Code:
adb push adbkey.pub /data/misc/adb/adb_keys
It turned out I already had usb debugging enabled.
I then flashed my original firmware again, and connected with adb. This time it connected correctly, without me having to click any dialogue on my phone. I fiddled with several remote control Android tools most of which didn't work. Finally, it turned out Vysor does exactly what I want to do. It is a bit unstable, but workable.
Anyways, I've finally managed to copy all the stuff I wanted from my phone.
I have a Verizon LGV30 that got wet and now the screen is unresponsive. Is there a way to get info from my phone to a computer? It turns on, I've pressed power and vol down to get it to power off and restart but can't do anything else. Booting into safe mode also doesn't do anything. Any ideas? Thanks.
charulo316 said:
I have a Verizon LGV30 that got wet and now the screen is unresponsive. Is there a way to get info from my phone to a computer? It turns on, I've pressed power and vol down to get it to power off and restart but can't do anything else. Booting into safe mode also doesn't do anything. Any ideas? Thanks.
Click to expand...
Click to collapse
When
your device is completely dried
USB debugging got enabled on device
You check this running
Code:
adb devices
to get your data back then to retrieve back the data can be tried via a so-called Android Data Recovery Software what all are Windows apps - some of them are free-of-charge: GIYF.
jwoegerbauer said:
When
your device is completely dried
USB debugging got enabled on device
You check this running
Code:
adb devices
to get your data back then to retrieve back the data can be tried via a so-called Android Data Recovery Software what all are Windows apps - some of them are free-of-charge: GIYF.
Click to expand...
Click to collapse
I have USB debugging on the device, but if I can't get into the phone, how can I check if its running?
charulo316 said:
I have USB debugging on the device, but if I can't get into the phone, how can I check if its running?
Click to expand...
Click to collapse
You connect your phone with PC via USB-cable, power on the phone and then on PC run the ADB command mentioned