Nexus S touchscreen died - how to get data off the phone?

Nexus S touchscreen died - how to get data off the phone? - Nexus S Q&A, Help & Troubleshooting

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.

Related

[TOOL] ADB Data Recovery (recover data from a phone with broken screen)

**UPDATE**
NEW VERSION
THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
For anyone having issues...
If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB
SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERYfirst, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING
SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERYnow things get complicated...
*The following is paraphrased from this site
1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page
2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode
[FASTBOOT]3. Connect your device to your computer via USB and wait till you see the PC recognize the device
to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices
you will see a list of connected devices. if not, something went wrong.
4. Launch Command Prompt and type the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img
5. Wait for the process to finish.
6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
[RECOVERY MODE (SAMSUNG)]USE THE INSTRUCTIONS ON THIS PAGE
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
Don't forget to hit "Thanks"

i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much

Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers

Thank you!
I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!
:good:
Thanks again!
-th3r3isnospoon

Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys

koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.

FuzzyMeep Two said:
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
P.S. I apologize if i have posted this in the wrong place, if so please let me know.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.

Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used

alisdairjk said:
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.

When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?

Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).

joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.

Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.

Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:

Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:

Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.

Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.

Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?

Amazing app. thank you so much :good:

FuzzyMeep Two said:
**UPDATE**
NEW VERSION
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel:

Someone smashed my phone with a rock. (data recovery ?s)

Greetings et al,
Backstory: I climb large granite walls and my phone was left part way up and a party following found my phone and decided to smash the crap out of the screen. They left it on prominently displayed along a trail on a rock and someone else I knew found it and returned it to me.
Device: Google Pixel 3
Status: Screen smashed to bits, but I can power it on and see it in "adb devices" etc...
So it was this past Sunday that the scalawags smashed my phone. Saturday I had taken my daughter and son-in-law on their first ever large/multi-pitch rock climb, 600ft. plus. Unfortunately I had no downloaded the pictures of that event nor the videos.
* I don't know how to get this device in MTP mode so I can transfer the data w/o a screen
* I tried to shell to it and I get "error: insufficient permissions for devices"
* Does anybody have any suggestions on what path I should head down to attempt to pull the files off this thing?
-Thanks in bunches for any and all replies...

nemanator said:
Greetings et al,
Backstory: I climb large granite walls and my phone was left part way up and a party following found my phone and decided to smash the crap out of the screen. They left it on prominently displayed along a trail on a rock and someone else I knew found it and returned it to me.
Device: Google Pixel 3
Status: Screen smashed to bits, but I can power it on and see it in "adb devices" etc...
So it was this past Sunday that the scalawags smashed my phone. Saturday I had taken my daughter and son-in-law on their first ever large/multi-pitch rock climb, 600ft. plus. Unfortunately I had no downloaded the pictures of that event nor the videos.
* I don't know how to get this device in MTP mode so I can transfer the data w/o a screen
* I tried to shell to it and I get "error: insufficient permissions for devices"
* Does anybody have any suggestions on what path I should head down to attempt to pull the files off this thing?
-Thanks in bunches for any and all replies...
Click to expand...
Click to collapse
Since you don't have USB debugging enabled and can't swipe the screen to unlock the lockscreen, there aren't really any options for you other than replacing the screen or sending the device to a professional shop to see if they can retrieve the data from the hardware by pulling it directly from the chip.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Since you don't have USB debugging enabled and can't swipe the screen to unlock the lockscreen, there aren't really any options for you other than replacing the screen or sending the device to a professional shop to see if they can retrieve the data from the hardware by pulling it directly from the chip.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do have USB debugging enabled.

nemanator said:
I do have USB debugging enabled.
Click to expand...
Click to collapse
Ok then, you might have an option. If there is a TWRP custom recovery for your specific model number, TWRP natively supports adb so it should work. You don't have to root but you can try flashing TWRP recovery on your device and then boot into TWRP then connect to PC and use adb with the "adb backup" command to backup all user data then extract the data that you want from the backup.
To find instructions for adb backup, do a google search for:
"ADB backup/restore"
Find the command to backup user data.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Ok then, you might have an option. If there is a TWRP custom recovery for your specific model number, TWRP natively supports adb so it should work. You don't have to root but you can try flashing TWRP recovery on your device and then boot into TWRP then connect to PC and use adb with the "adb backup" command to backup all user data then extract the data that you want from the backup.
To find instructions for adb backup, do a google search for:
"ADB backup/restore"
Find the command to backup user data.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I'm getting device unauthorized at this point so now adb doesn't work. I'm not sure what changed to cause that. It was working. I had/have twrp installed. I tried a "flashboot boot twrp.img". I had to temp boot like this when I was rooting this thing. The fastboot flash w/ twrp.img bricked the phone. Anyway, after a flashboot boot twrp.img. adb devices lists nothing. So either it's not booting twrp.img successfully or I'm missing something.

nemanator said:
I'm getting device unauthorized at this point so now adb doesn't work. I'm not sure what changed to cause that. It was working. I had/have twrp installed. I tried a "flashboot boot twrp.img". I had to temp boot like this when I was rooting this thing. The fastboot flash w/ twrp.img bricked the phone. Anyway, after a flashboot boot twrp.img. adb devices lists nothing. So either it's not booting twrp.img successfully or I'm missing something.
Click to expand...
Click to collapse
Ah, your bootloader is locked, that is probably why you previously had to boot a TWRP .img instead of flashing it. Now, I'm not sure it will boot anything. Try flashing a copy of stock recovery, then try the fastboot boot TWRP again.
Other than that, I think you might be at the end of your rope.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Ah, your bootloader is locked, that is probably why you previously had to boot a TWRP .img instead of flashing it. Now, I'm not sure it will boot anything. Try flashing a copy of stock recovery, then try the fastboot boot TWRP again.
Other than that, I think you might be at the end of your rope.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
The device unauthorized was from the windows machine. I'm back on the linux box and adb can see the device again. I've tried oodles of ways of getting mtp enabled.
When in adb shell and trying to find my photos/videos, I'm getting funky filenames.
sargo:/storage/emulated/0 # ls
+dn0VjXCwXIGBTRlAAdSqA NKZ4osL+U6zJbQICkOBoOB VqEBnQxs1hu4ncv3woVfCB kmOAbyd,bVAJDnQSbomLyA wXQ6rmjvahUKbZQtHof35D
7CdpRTZ8PchPMx4DOUvlLD OuATvxF3HNScfmEIoaabiB Ya0QbX5aki6BstVDxMXi5LRPcRD nZETC6WByAa5h7jO2tDyqC
I didn't have much success with mtp when my phone was screen was operational but at least I could see and navigate to the DCIM folder. I'm not sure why adb shell is rendering the files as such.

nemanator said:
The device unauthorized was from the windows machine. I'm back on the linux box and adb can see the device again. I've tried oodles of ways of getting mtp enabled.
When in adb shell and trying to find my photos/videos, I'm getting funky filenames.
sargo:/storage/emulated/0 # ls
+dn0VjXCwXIGBTRlAAdSqA NKZ4osL+U6zJbQICkOBoOB VqEBnQxs1hu4ncv3woVfCB kmOAbyd,bVAJDnQSbomLyA wXQ6rmjvahUKbZQtHof35D
7CdpRTZ8PchPMx4DOUvlLD OuATvxF3HNScfmEIoaabiB Ya0QbX5aki6BstVDxMXi5LRPcRD nZETC6WByAa5h7jO2tDyqC
I didn't have much success with mtp when my phone was screen was operational but at least I could see and navigate to the DCIM folder. I'm not sure why adb shell is rendering the files as such.
Click to expand...
Click to collapse
If adb is working, try this:
https://stackoverflow.com/questions/54959259/enable-mtp-using-adb
Or this:
https://forum.xda-developers.com/showthread.php?t=2786395
Sent from my SM-S767VL using Tapatalk

Droidriven said:
If adb is working, try this:
https://stackoverflow.com/questions/54959259/enable-mtp-using-adb
Or this:
https://forum.xda-developers.com/showthread.php?t=2786395
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Well I believe I mucked it up worse. I used the command line to do a set persistent mode to mtp and forgot to add adb e.g. "mtp,adb"
I forget the specific syntax but it worked. I'm in MTP mode persistently but I'm not able to mount the device from windows or linux and both operating systems see the device.
I have no idea how I'm going to get back to adb mode.
Anybody have a clue as to why I cannot see the proper file names in /storage/... ?
Does MTP mode do some magic and decrypt the files or something?
They file names looked to be encrypted when I was able to get at the file system with adb.

How do you backup data in a rooted phone using adb twrp?

I have a Galaxy Note 5 and I have important data in it. The screen is broken so I can't do anything, but I see recovery listed with a bunch of characters when I do
Code:
adb devices
. I can run some adb commands, adb root tells me I have root, I can do "id" inside of adb shell. Though, whenever I try running any twrp commands inside adb shell, it says "TWRP does not appear to be running. Waiting for TWRP to start."
What can I do here? I also see SAMSUNG Android under devices on this linux distro I'm running but I am getting an mtp error whenever I try connecting to it.

Sorry to hear that. If your Samsung Galaxy Note 5 can be detected by the computer via USB cable connecting, and the USB debugging on it is enabled, try Coolmuster Android Backup Manager. Its free backup function can help transfer data to the computer for backup directly. It's easy and safe. Good luck to you.

nazhai said:
Sorry to hear that. If your Samsung Galaxy Note 5 can be detected by the computer via USB cable connecting, and the USB debugging on it is enabled, try Coolmuster Android Backup Manager. Its free backup function can help transfer data to the computer for backup directly. It's easy and safe. Good luck to you.
Click to expand...
Click to collapse
It doesn't seem to be working, well at least not when the phone's in recovery. I'm not sure if I can boot it up normally.

tesiz22 said:
I have a Galaxy Note 5 and I have important data in it. The screen is broken so I can't do anything, but I see recovery listed with a bunch of characters when I do
Code:
adb devices
.
Click to expand...
Click to collapse
Indicates your phone boots into Recovery mode and not into Normal ( ADB ) mode.
To get rid off of booting into Recovery mode you run
Code:
adb devices
adb reboot
Once your phone boots into Normal mode you can pull out the data of interest: take note that adb pull has a size limit, hence probably
Code:
adb pull /sdcard C:\PULLED-DATA
doesn't work as expected if amount of data to pull is >= 2GB in total ( e.g. a stored movie file may have up to 8GB ). That means, to be on safe side, you have to pull the files of interest one-by-one.

Backup with Smart Switch a black screen Galaxy S5 (Unauthorised device in adb - Root - Usb debugging ON - Unlock patern OK - Recovery accessible)

Hi,
I think I've already explain everything in title.
My Galaxy S5 on Android 8 (I think) as her screen broken (black)
Before that it already wokr badly and slowly. I bought a new phone but this one break just before I can transfer data.
I can unlock the patern (I know that because the volume + buton react)
Smart switch say that the phone is locked (even it's not true). Tested on 2 PC
The phone appear in Windows but no file or folder appear.
In adb the device is shown unauthorised and even if I click where the message to unlock should be, notihng append.
The phone is connected on Wifi, apparear in Google Find it but not Samsung find it...
I think that it's already to much information...
My question : how can I do the unlock the phone and do a smart switch backup ? or an other way to transfer data.
Regards
James

The Samsung Galaxy S10 comes with a USB OTG adapter. OTG stands for "On the Go" and is used for the connection between smartphone and USB stick / cable. Connect this USB OTG adapter to the USB Type C port of your Samsung, then connect the USB OTG adapter with USB Type C port of your computer.
You should see the data stored on your Samsung.

jwoegerbauer said:
The Samsung Galaxy S10 comes with a USB OTG adapter. OTG stands for "On the Go" and is used for the connection between smartphone and USB stick / cable. Connect this USB OTG adapter to the USB Type C port of your Samsung, then connect the USB OTG adapter with USB Type C port of your computer.
You should see the data stored on your Samsung.
Click to expand...
Click to collapse
It's an S5. But I have a OTG adaptor for it but my new phone A52s doesn't connect to the S5.
I try with a S7 but I can see that there is a lot autorisation to give on the old phone which will be very hard to do with a black screen.

If ADB is unauthorized, the only way to back up any data would be via a custom recovery. That would require that the device have an unlocked bootloader though

iBowToAndroid said:
If ADB is unauthorized, the only way to back up any data would be via a custom recovery. That would require that the device have an unlocked bootloader though
Click to expand...
Click to collapse
ADB authorised is not require for Smart Switch... I think
And my device have access to recovery and it's root so the bootloader is unlocked.

jameslevalaisan said:
ADB authorised is not require for Smart Switch... I think
And my device have access to recovery and it's root so the bootloader is unlocked.
Click to expand...
Click to collapse
So then flash a custom recovery, and then enter it. That will either give you MTP access to the files and folders, or ADB should also be enabled - and does not require authorization

iBowToAndroid said:
So then flash a custom recovery, and then enter it. That will either give you MTP access to the files and folders, or ADB should also be enabled - and does not require authorization
Click to expand...
Click to collapse
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.

jameslevalaisan said:
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
Click to expand...
Click to collapse
1. No, I didn't forget that the screen is broken
2. I wasn't telling you to press anything in TWRP. When it's in TWRP and you plug it in, you will either get MTP and/or ADB access automatically
3. Yes, it is perfectly normal to not have access to the files and folders in Windows, when it's powered on normally. There's a popup on the phone that you have to tap in order to grant permission to the folders and files. That's why it shows up as an empty device when you plug it in while in normal mode

iBowToAndroid said:
1. No, I didn't forget that the screen is broken
2. I wasn't telling you to press anything in TWRP. When it's in TWRP and you plug it in, you will either get MTP and/or ADB access automatically
3. Yes, it is perfectly normal to not have access to the files and folders in Windows, when it's powered on normally. There's a popup on the phone that you have to tap in order to grant permission to the folders and files. That's why it shows up as an empty device when you plug it in while in normal mode
Click to expand...
Click to collapse
Ok excuse me.
Hum when I'm in recovery mode, my phone doesn't appear in Widows. And in adb, I haven't access to all folder. Data is empty for exemple.
For 3. Ok, I don't remember this notification. But I'm shure that I'have already use this phone with my PC. If I wasn't able to ring it on Whastapp, I will think that the phone doesn't works anymore at all. But it's not the case.

jameslevalaisan said:
purehaps you have forget that the screen is broken. I can't access the phone for complicated manipulation. I'have already have TWRP installed on it but without a view it's impossible to manipulate it. Also, it's not normal that the phone are not viewed on windows or is shown locked on smart switch.
In recovery mode, the phone isn't show on windows also. Find the MTP option in TWRP without a screen view is very diffucult and dangerous, (the wipe option are near)
If I can access file on phone I will be able to view screenshot and configure it.
Click to expand...
Click to collapse
ADB commands work by default while in TWRP, you can back up almost anything that your TWRP version allows through your PC using ADB commands, TWRP will serve as intermediary, but you will not go to operate over your broken screen device but through your ADB/fastboot CMD.

In normal mode I can unlock the phone but after that even if I click where the message should appear it doesn't do anything.
In adb I can't access a backup command (and if I can do this, It will not the easyer way to transfer my sms.)

I have some old other phones to see some message exemple and know where to clic but it doesn't works. I have install Vyzor, It asks me a permission but even if I tap in the right of the screen the permission doesn't works.
I also try to transfert a new adb key but I think it doesn't work because Wyzor still ask permission.

jameslevalaisan said:
In normal mode I can unlock the phone but after that even if I click where the message should appear it doesn't do anything.
In adb I can't access a backup command (and if I can do this, It will not the easyer way to transfer my sms.)
Click to expand...
Click to collapse
There is no backup command in ADB that you can use. And the reason that you can't access /data is because that requires going into TWRP settings and mounting the system partition.
What you can do in TWRP is to adb pull all of the files and folders off of the internal storage

Other thing, I can phone my phone with Whatsapp but I can't click to hang off.

iBowToAndroid said:
There is no backup command in ADB that you can use. And the reason that you can't access /data is because that requires going into TWRP settings and mounting the system partition.
What you can do in TWRP is to adb pull all of the files and folders off of the internal storage
Click to expand...
Click to collapse
ok to do have a exemple of command to tap ?
And there no way to just be able to connect my phone with smart switch on windows ?

jameslevalaisan said:
I have some old other phones to see some message exemple and know where to clic but it doesn't works. I have install Vyzor, It asks me a permission but even if I tap in the right of the screen the permission doesn't works.
I also try to transfert a new adb key but I think it doesn't work because Wyzor still ask permission.
Click to expand...
Click to collapse
ADB backup is not to operate while your device is on, but it is to operate while your device is in TWRP mode.
TWRP has integrated by default the ADB options not need to authorize through your broken screen because it is already authorized.
Messages as an app user (the same with root or system user) is part of userdata, you want to back up userdata to restore it after in other device or a scenery where your device get repaired, no?
I'll give you an example, you have to use this command, create a folder on a convenient place onto your PC directory, something like "BACKUP", assuming that you set it up correctly the environment for ADB/fastboot to use it along all of your system, you should open from this newly created folder an CMD (I use the new Windows terminal for easy/comfortable results) then type from the terminal adb shell twrp backup userdata , you'll have the userdata backed up in your PC in less of 2 minutes depending on the size of the partition, and so on successively.
What you can back up from TWRP depends on the restrictions from your TWRP version, you should back up the normal that you can see from the TWRP screen and even more but for example if your TWRP have some issues mounting vendor partition of course the ADB commands can't do the job for this specific partition, but anyway you have a lot you can do through it.

jameslevalaisan said:
ok to do have a exemple of command to tap ?
And there no way to just be able to connect my phone with smart switch on windows ?
Click to expand...
Click to collapse
1. The command depends on what the mount point for your internal storage is. The command would be "adb pull /(mount point)" , so it could be:
adb pull /sdcard
adb pull /storage0/sdcard
Or several others
2. No, you can't connect with Smart Switch without allowing permission on the popup box on the phone screen

Hi guys,
I'm very happy to find here some people to help me. thank you a lot. I just now in recovery mode.
here is some result of command
Code:
adb devices
List of devices attached
487e969e recovery
adb root
adbd is already running as root
adb shell
~ # ls
cache init.recovery.qcom.rc selinux_version
charger init.recovery.service.rc sepolicy
data init.recovery.usb.rc service_contexts
default.prop license sideload
dev oem sys
etc prebuilt_file_contexts system
file_contexts proc tmp
fstab.qcom property_contexts twres
init res ueventd.qcom.rc
init.rc root ueventd.rc
init.recovery.hlthchrg.rc sbin vendor
init.recovery.nano.rc seapp_contexts
~ #
as you can see there is not storage in the ls result
Code:
~ # ls /res
images keys
~ # ls /data
~ # ls /data
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db ./
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
Is there something inspired you ?

iBowToAndroid said:
1. The command depends on what the mount point for your internal storage is. The command would be "adb pull /(mount point)" , so it could be:
adb pull /sdcard
adb pull /storage0/sdcard
Or several others
2. No, you can't connect with Smart Switch without allowing permission on the popup box on the phone screen
Click to expand...
Click to collapse
1. the ls command doesn't show any sdcard or storage
2. Ok bit wyh I can't click on the permission popup ?

SubwayChamp said:
ADB backup is not to operate while your device is on, but it is to operate while your device is in TWRP mode.
TWRP has integrated by default the ADB options not need to authorize through your broken screen because it is already authorized.
Messages as an app user (the same with root or system user) is part of userdata, you want to back up userdata to restore it after in other device or a scenery where your device get repaired, no?
I'll give you an example, you have to use this command, create a folder on a convenient place onto your PC directory, something like "BACKUP", assuming that you set it up correctly the environment for ADB/fastboot to use it along all of your system, you should open from this newly created folder an CMD (I use the new Windows terminal for easy/comfortable results) then type from the terminal adb shell twrp backup userdata , you'll have the userdata backed up in your PC in less of 2 minutes depending on the size of the partition, and so on successively.
What you can back up from TWRP depends on the restrictions from your TWRP version, you should back up the normal that you can see from the TWRP screen and even more but for example if your TWRP have some issues mounting vendor partition of course the ADB commands can't do the job for this specific partition, but anyway you have a lot you can do through it.
Click to expand...
Click to collapse
I try this...
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp backup userdata
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp plat-form-tools userdata
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
I'm not sure I understand your command. But it return a result. "Backup" is the name of a folder ? or it's a commande for twrp ?
Is there a way to be sure that twrp is installed (with all my phone, sometime, I don't remember what is on it. The thing it's sure it that this phone is root because I use root function with some app but perhaps just with magisk or Super SU.

Phone's screen partially working, need to activate USB Debug

Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you

Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.

V0latyle said:
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.
Click to expand...
Click to collapse
Do you know if changing the screen could solve the problem? Or do you think there's a way to copy data 1:1 on another device (such as a used mi 9t I could buy)?

Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?

Droidriven said:
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?
Click to expand...
Click to collapse
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.

Dona2592 said:
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.
Click to expand...
Click to collapse
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.

Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?

Dona2592 said:
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?
Click to expand...
Click to collapse
Yes USB should work in place of sdcard

Dona2592 said:
Plus, I don't really get why the system fails right after the lockscreen, I'm actually able to enter the code and the phone unlocks but the launcher seems not working, while the notifications bar works fine, and after some seconds the phone reboots. How can the system work fine in some aspects and bad in others at the same time? Can it be some flash memory issue?
Click to expand...
Click to collapse
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.

Droidriven said:
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.
Click to expand...
Click to collapse
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?

Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot

Dona2592 said:
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?
Click to expand...
Click to collapse
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.

xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
Thanks mate, I'll give it a try for sure

Droidriven said:
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.
Click to expand...
Click to collapse
Ok, but do you know what could be the damaged piece of hardware?

Dona2592 said:
Ok, but do you know what could be the damaged piece of hardware?
Click to expand...
Click to collapse
NO

xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.

Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Is your bootloader locked?

Droidriven said:
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.
Click to expand...
Click to collapse
Yeah in fact when I type "adb shell" it gives me error, but I can enter fastboot mode and the phone is seen. Unfortunately I can't do much from there

Arealhooman said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yeah. **** me, for once I kept everything stock and this happened . I've always rooted and customized my phones and nothing like this has ever happened.

Database Info

welcome