Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
voolandis said:
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
Click to expand...
Click to collapse
Well using adb commands is out of the question as usb debugging is not enabled. You might get somewhere by connecting a usb mouse or keyboard via otg.
voolandis said:
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
Click to expand...
Click to collapse
Try rebooting your device into recovery, hook your phone upto your computer, and execute these commands in your terminal:
Code:
cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys
adb reboot
Wait for a while to let it boot, and execute
Code:
adb pull /sdcard/
If you didn't have USB debugging turned on, you can execute these commands after connecting your phone in recovery to your PC:
Code:
adb shell
cd /system/
echo "persist.service.adb.enable=1" >> build.prop
echo "persist.service.debuggable=1" >> build.prop
echo "persist.sys.usb.config=mtp,adb" >> build.prop
adb reboot
hope it works
LukeHammer said:
hey, buddy, I had the same problem with you last month, but I solve, I got the help from this post (recover data from broken Samsung screen), now I hope that can help you.:highfive:
Click to expand...
Click to collapse
Many thanks, but this thread is over a year and a half old.
voolandis said:
Many thanks, but this thread is over a year and a half old.
Click to expand...
Click to collapse
But you keep the link.
heidisteen said:
https://youtu.be/dnpTiYnp2A8
Click to expand...
Click to collapse
Does this helpful with my broken S5 ACTIVE?
Related
Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.
Forgive me for asking the obvious, but do you have USB Debugging enabled?
distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.
Fastboot devices gave me this output:
serial# fastboot
kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe
kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).
Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck
My daughter's Nexus S touchscreen has died. It died slowly in that on the first few occasions she couild pop the battery and it would come back. Now it won't come back at all and is stuck on the pattern lock screen.
Before we send the phone for repair under warranty she is keen to get the photos off the phone since a repair might reset the phone. I was thinking we could mount the phone as a USB device but it doesn't show up perhaps because it won't until the pattern lock is entered else anybody could get data off your phone bypassing security.
Any other things we could try before giving up and hoping the repair doesn't delete all the data?
Thanks
Boot into recovery, make a nand then extract data through adb?
adb pull /sdcard/path-to-whatever
Can you explain the path to whatever? Like if I want it in folder "A" on the desktop.
Sent from my Galaxy Nexus using Tapatalk 2
Check this thread
http://forum.xda-developers.com/showthread.php?t=1573744
treUse said:
adb pull /sdcard/path-to-whatever
Click to expand...
Click to collapse
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
lchiu7 said:
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
Click to expand...
Click to collapse
ADB "thought" you meant to copy a file.
To copy the entire sdcard directory you should do something like this:
Code:
adb pull /sdcard/ sdcard/backup/on/pc/
The command parameters are "adb pull <source> <destination>"
Just make sure source ends with a /
Maybe a Windows based software?? Droid Explorer, very useful.. http://de.codeplex.com/ :good:
Well I finally got the phone to play with. The screen indeed dead. I installed the Google USB drivers from the SDK and also the Samsung drivers.
When I boot the phone into the recovery menu I can run fastboot devices and see the following
????0AC4B09900?? fastboot (of course the ? are not there but I wanted to anonmyuse the serial)
So far so good.
In device manager under Android Phone it show Samsung Android ADB Interface
But if I try adb devices I get nothing.
Forgot to mention my daughter said USB Debugging was turned off but I am not sure that makes any difference and anyway, we can't boot Android to turn it on
So I select Recovery and see the Android with the exclamation mark. Windows beeps to indicate that some sort of devices has been installed,
But in Device Manager no phone shows which explains why adb can't fidn the phone but not why.
I can bring up the recovery menu but still no adb
Any suggestions?
Thanks
Boot into Fastboot and flash CWM Recovery.
RL77LUC said:
Boot into Fastboot and flash CWM Recovery.
Click to expand...
Click to collapse
But it looks like I have to unlock the bootloader to do that and the phone is still under warranty so that would invalidate the warranty wouldn't it? She would like to get the data off the phone. A screen fix shouldn't zap the memory but you never know.
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
cukdus said:
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
Click to expand...
Click to collapse
The phone is stock
lchiu7 said:
The phone is stock
Click to expand...
Click to collapse
If you unlock the bootloader to flash CWM your memory will also be wiped, so you will loose all the photos you want to save, so don't do that.
Also if you have the USB debugging off, the ADB commands won't work. I'm afraid you're SOL, since you have the bootloader locked you can't flash a kernel with USB host, that would allow you to use a mouse to navigate in the phone and since you don't have USB debug you can't pull files from the "SDcard"... Better take it to the store and try to ask them if they can save the photos before they do anything to the phone, but i guess if it's a digitalizer problem, they won't mess with the NAND.
Check out http://www.moborobo.com/ and see if it works for you.
If you have root you have extended functionality, like control the device from the PC. But if i recall correctly, even without root you should be able to get your files.
Not sure where to post this. I have worked with roms many many times on android over the years without any trouble. I am on OSX macbook air with brand new HTC One M8 trying to S-OFF. No matter what I try I get this running ADB: "List of devices attached" EMPTY. Nothing listed.
WeakSauce rooted phone no problems.
1. HTC Sync connects to phone just fine.
2. Brand new Android SDK downloaded for use
3. Tried using sudo ./adb devices
4. Tried USB debug switch on/off
5. Tried USB unplug/replug
6. Tried phone on/off
7. Tried macbook on/off
8. System Profiler shows USB HTC device connected
What else can I do to make this work. Starting hour 5 of attempts. Any help much appreciated.
studioleland said:
Not sure where to post this. I have worked with roms many many times on android over the years without any trouble. I am on OSX macbook air with brand new HTC One M8 trying to S-OFF. No matter what I try I get this running ADB: "List of devices attached" EMPTY. Nothing listed.
WeakSauce rooted phone no problems.
1. HTC Sync connects to phone just fine.
2. Brand new Android SDK downloaded for use
3. Tried using sudo ./adb devices
4. Tried USB debug switch on/off
5. Tried USB unplug/replug
6. Tried phone on/off
7. Tried macbook on/off
8. System Profiler shows USB HTC device connected
What else can I do to make this work. Starting hour 5 of attempts. Any help much appreciated.
Click to expand...
Click to collapse
The HTC Sync app on your laptop should be removed. You only needed it to install the drivers, then per the Firewater instructions, Sync should be uninstalled. I don't know if that's what's causing your problems, but try it.
per the Firewater instructions, Sync should be uninstalled
Click to expand...
Click to collapse
I did try that as well. Do I need to remove and restart? I will try that.
studioleland said:
I did try that as well. Do I need to remove and restart? I will try that.
Click to expand...
Click to collapse
Possibly? I'm not a mac guy so I don't know, sorry.
sfreemanoh said:
Possibly? I'm not a mac guy so I don't know, sorry.
Click to expand...
Click to collapse
WOW! Got it! This will no doubt save some people. From stackoverflow:
If you have installed the application EasyTether, this can interfere with ADB.
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
Click to expand...
Click to collapse
Boom! It worked.
studioleland said:
WOW! Got it! This will no doubt save some people. From stackoverflow:
Boom! It worked.
Click to expand...
Click to collapse
Ahh, yeah... That was mentioned in the firewater instructions.
"All other phone software removed or disabled (Samsung Kies, PDANet, etc.)"
studioleland said:
WOW! Got it! This will no doubt save some people. From stackoverflow:
Boom! It worked.
Click to expand...
Click to collapse
hey what did you do to fix it ? i spent hours trying to unlock this thing and now my phone is with a guy that owns a computer store trying to do it for me . please help me out
ANTHONY81L said:
hey what did you do to fix it ? i spent hours trying to unlock this thing and now my phone is with a guy that owns a computer store trying to do it for me . please help me out
Click to expand...
Click to collapse
Happy to be of help if I can. What step are you stuck on. Can you post a list of steps taken already?
studioleland said:
Not sure where to post this. I have worked with roms many many times on android over the years without any trouble. I am on OSX macbook air with brand new HTC One M8 trying to S-OFF. No matter what I try I get this running ADB: "List of devices attached" EMPTY. Nothing listed.
WeakSauce rooted phone no problems.
1. HTC Sync connects to phone just fine.
2. Brand new Android SDK downloaded for use
3. Tried using sudo ./adb devices
4. Tried USB debug switch on/off
5. Tried USB unplug/replug
6. Tried phone on/off
7. Tried macbook on/off
8. System Profiler shows USB HTC device connected
What else can I do to make this work. Starting hour 5 of attempts. Any help much appreciated.
Click to expand...
Click to collapse
How did you do it..mine also says "list of devices attached "..
Step 1 : stop adb by typing code
adb kill-server
Step 2: remove the usb cable from the computer and phone
Step 3: disable usb debugging on your phone
Step 4: Enable usb debugging on your phone
Step 5: Connect usb to your phone and computer
Step 6: kill adb server by typing the code
adb kill-server
Step 7: ???
Step 8: Profit
Hi,
My screen got crack diagonally and touch is not working at all. Is there a way to back up the device?
Worst part : It's in airplane mode and security pattern enabled.
With lock, i could not connect to adb shell and airplane mode not connected to net.
Any suggestions?
KashRaman said:
Hi,
My screen got crack diagonally and touch is not working at all. Is there a way to back up the device?
Worst part : It's in airplane mode and security pattern enabled.
With lock, i could not connect to adb shell and airplane mode not connected to net.
Any suggestions?
Click to expand...
Click to collapse
Oh, I had this problem before. You can connect a mouse to your phone, and use that to control your phone. Just buy a micro usb to usb cable adapter, and connect a usb mouse to it.
http://www.ebay.com/itm/90-Degree-M...TG-Adapter-Cable-Android-Tablet-/301639994675
Mehhish said:
Oh, I had this problem before. You can connect a mouse to your phone, and use that to control your phone. Just buy a micro usb to usb cable adapter, and connect a usb mouse to it.
http://www.ebay.com/itm/90-Degree-M...TG-Adapter-Cable-Android-Tablet-/301639994675
Click to expand...
Click to collapse
Does your phone has been rooted?
If yes, adb shell into your phone as root and dump out all the partiotions on the phone on your SD card and then finally pull them out.
All the partitons can be seen with "ls -l /dev/block/bootdevice/by-name".
If your phone has not been rooted then try to have the SuperU boot.img and boot with to gain root privillege and dump all the partitions out as describe above. ( ATTENTION, I said BOOT with and NOT FLASH it)
Good luck
Cheer.
I was able to reboot in recovery by using key combo and clear the security key thru adb. With that, I have taken backup using titanium backup thru VNC client
Hi!
Help me please, beause i can't unlock my tablet. I forgot the password, but it's the smallest problem. I go to "Android system recovery<3e>" mode, but in there i can't choose the "wipe data/factory reset" option because the tablet don't have volume button, just a power and a home button. I tried select this option with an OTG cabel+keyboard, but nothing happends.
Do you have any idea?
Thanks.
-Sorry for my english-
there are couple of videos on youtube showing how to reset a device without volume button
ineedroot69 said:
there are couple of videos on youtube showing how to reset a device without volume button
Click to expand...
Click to collapse
that' true, but my problem is not only the missing volume button. The OTG cabel + keyboard combination neither working.
@bentudlik
If you can establish an ADB connection - requires USB debugging got enabled on the phone - there is NO need to use the in-built recovery menu to wipe phone's user-data / do a factory-reset: this all can be done by means of ADB, too. But would require you've some knowledge about ADB and know how use its commands properly.
jwoegerbauer said:
@bentudlik
If you can establish an ADB connection - requires USB debugging got enabled on the phone - there is NO need to use the in-built recovery menu to wipe phone's user-data / do a factory-reset: this all can be done by means of ADB, too. But would require you've some knowledge about ADB and know how use its commands properly.
Click to expand...
Click to collapse
would be terrible if you do erase command on /userdata and can't recreate it i experience that and its stuck on boot logo not bootloop
jwoegerbauer said:
@bentudlik
If you can establish an ADB connection - requires USB debugging got enabled on the phone - there is NO need to use the in-built recovery menu to wipe phone's user-data / do a factory-reset: this all can be done by means of ADB, too. But would require you've some knowledge about ADB and know how use its commands properly.
Click to expand...
Click to collapse
Do you have any idea, how to enable USB debugging while my tablet is locked? Because now my laptop can't recognize this device.
I know ADB should be a right method, but firt i have to connect the tablet to laptop somehow.
bentudlik said:
Do you have any idea, how to enable USB debugging while my tablet is locked? Because now my laptop can't recognize this device.
I know ADB should be a right method, but firt i have to connect the tablet to laptop somehow.
Click to expand...
Click to collapse
Enabling USB Debug on an Android phone always should be the 1st action an user should do when he/she puts a phone into operation. On Android-side ADB gets started when Android boots up. So by means of ADB you would be able to bypass / remove FRP-lock etc,pp.
jwoegerbauer said:
Enabling USB Debug on an Android phone always should be the 1st action an user should do when he/she puts a phone into operation.
Click to expand...
Click to collapse
That's true. It's not my device, i just try the solve the problem. I thought it could be fixed with simple solutions., but my steps not work ...