Database Info

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

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.

Pixel 2 stuck on G loading screen

My Pixel 2 took a dive on a few days ago and I've been trying to get it operational ever since. The things i've tried are
1. Waiting it out
2. Force restart
3. Force restart more than 7 times in a row to get it to revert back to another version
4. ADB sideload the proper system image to get it to begin working
But none of these has worked. Right now all I'm really concerned about is trying to salvage my data and create a backup file for all my apps and data but when I try to do the backup through the adb using 'adb backup -apk -shared -all -system -f Direction:\filename.ab' it gives me an error that says "adb: unable to connect for backup: closed" And there's no other way around it.
Side note, I've only been able to get my phone to show up on the adb devices list when i say to do a recovery through adb, otherwise it simply doesn't show up there and only shows up under fastboot devices.
I would love some help here, anything you all can do to point me in the right direction would be fantastic.

@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.

jwoegerbauer said:
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
Click to expand...
Click to collapse
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?

Otonirez said:
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Click to expand...
Click to collapse
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%

jwoegerbauer said:
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
Click to expand...
Click to collapse
I really wish I would have seen this a few minutes ago because I did a factory reset on my phone like right before i saw this. I doubt there's anything I can do at this point to reclaim my stuff

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.

problems with phone decryption

I have older device, it is htc 10.
I was using corporate MS Teams on it however at some point corporate required encryption to be done on my phone i got poop-up and trigger encryption.
Now phone consume much more power, i think because of the encryption.
I would like to decrypt the phone however there is no such button.
Any idea how to trigger this decryption without factory reset, it is Android 8.0 ?

It can't be undone normally. Back up all critical data, factory reset.
I never encrypt any device as it will come back to bit you sooner or latter.
-Never- encrypt backup data drives or set PC bios passwords. You are the one most likely to get locked out, sometimes through no fault of your own!!!

seba.kwiat said:
...
I would like to decrypt the phone however there is no such button.
Any idea how to trigger this decryption without factory reset, it is Android 8.0 ?
Click to expand...
Click to collapse
3 methods possible
1.
You can turn your device's /data partition to an unencrypted state if you do a backup of this partition via the adb backup command and play back the backup via the adb restore command.
2.
Boot phone into recovery and then from your computer run
Code:
adb shell "recovery --set_filesystem_encryption=off"
3.
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with): in a terminal window run
Code:
recovery --set_filesystem_encryption=off

jwoegerbauer said:
3 methods possible
1.
You can turn your device's /data partition to an unencrypted state if you do a backup of this partition via the adb backup command and play back the backup via the adb restore command.
2.
Boot phone into recovery and then from your computer run
Code:
adb shell "recovery --set_filesystem_encryption=off"
3.
If you need to run it from the phone itself (ie: you don't have a computer nearby to adb with): in a terminal window run
Code:
recovery --set_filesystem_encryption=off
Click to expand...
Click to collapse
Could u recommend any terminal app, I have tried a couple but looks like recovery command is missing on them?

Question Write to /data/... folder

I just switched to the Pixel 6a and have botched something with an app I use.
I have the app's files from the old phone, which were in /data/data/com... folder, and want to overwrite files on the new phone, with them.
I did "adb pull ..." on the old phone to get files on the computer and intended to do "adb push ..." to the new,
but I can't get it to connect to adb, in recovery mode.
The old phone had TWRP.
When I rebooted it into recovery and connected with cable to PC, "adb devices" would print:
List of devices attached
<device_ID> recovery
On the new one, when I go into recovery (stock), "adb devices" prints nothing.
When I select the sideload option, "adb devices" prints:
<device_ID> sideload
In this sideload mode, the pull, push, shell... adb commands don't work.
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?

Stock recovery isn't TWRP! You have no access to anything in your file system.

Svrmirac said:
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?
Click to expand...
Click to collapse
Use TWRP. Stock recovery has no adbd, only a minimal adbd with no features except a sideload option for signed update.zips

Thank you for the suggestion, @WoKoschekk, but I don't think I can do that.
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
I seem to be at an impasse, with the stock ROM/recovery.

Svrmirac said:
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
Click to expand...
Click to collapse
Yes, (un-)locking wipes all data. But that is exactly the reason why /data is inaccessible from recovery. To keep your data safe.

I don't even think TWRP is a thing for modern pixels

ctfrommn said:
I don't even think TWRP is a thing for modern pixels
Click to expand...
Click to collapse
No it isn't the closing thing you'll find to TWRP on Pixel 6A is the Lineage Recovery.
I would suggest using a tool like Titanium Backup. That allows the saving and reinstating of apps.

Booting a custom recovery requires unlocking the bootlader, which I don't want to do now.
Titanium backup requires rooting as well...
Thank you for the suggestions but I'm counting this one as lost.

You won't be able to directly write to the /data/data/com.your.packagename folder without root. The only options I can think of are
1. Using adb backup... backup your app data from your old phone and restore it to the new phone
Bash:
To backup
# adb backup -noapk com.your.packagename -f backup.adb
To restore
# adb restore backup.adb
2. If the app in question is debuggable, you can assume the application permission and access the folder
Bash:
# adb shell
bluejay:/ $ run-as com.your.packagename
bluejay:/ $ cp -r /storage/emulated/0/Download/backup/* /data/data/com.your.packagename