Hi,
My friend has a Sensation with a broken LCD. His contacts are stored on the internal memory and not synced to google. While they are his main concern, I'd also like to get a backup of other data if possible.
The phone is not rooted, S-ON etc. and USB debugging is not on. It's pretty much stock.
I am able to get into fastboot, but that is about it.
Running through a few options, I managed to adb into my (rooted, with USB debugging) DHD and pull the contacts2.db file. I'm thinking backup over adb is going to be my best bet, but I'm not sure how to connect to the Sensation.
Is it possible to turn USB debugging on without access to the screen? Is there another way I can adb into the phone? Or perhaps another way I could access the internal memory?
Cheers
If I can get an adb connection, can I temproot, tar the app data and then transfer it to the SD/pull it over adb?
I've read that adb can be accessed through recovery, does this apply to the stock recovery? I've tried accessing it, but I'm still unable to make a connection.
I think I could flash another recovery without use of the screen, but getting S-OFF first could be a whole other issue.
Can anyone offer some advice?
It's unfortunate that this went unanswered, because now I have the exact same problem on my wife's phone. All stock - just want to be able to grab contacts and sms/mms data if possible. Other backups would be great.
if usb debugging is enabled and adb is working then backing up some data is possible
you need to have a sdcard in phone too...with atleast 1.5 GB of space
adb devices (check whether devices got connected or not)
adb shell
mkdir /sdcard/tmp_data
cp -rf /data/* /sdcard/tmp_data/
the above commands might probably copy the stuff from /data partition to /sdcard/tmp_data
the data partition has all data ..contacts ,call logs, sms logs, even user apps and its data
Related
[resolved]
I have a broken (completely black) screen on my captivate Im trying to back up all my files from the INTERNAL memory. I can't see the screen so obviously I can't mount the phone to view the files on my PC. I have gotten 'pull /system/ /local/' to work however when I try something like 'pull /data/ /local/' it says "pull: building file list... 0 files pulled. 0 files skipped."
Basically, how do I use ADB to get all of my files to my computer? Help is certainly appreciated. After this I will probably reset the phone and then maybe sell it as is. Not too sure.
Question: Do u happen to have any recent clockwork backup and/or tibu backups on ur phone? If either is present u could directly navigate to those folders (in adb) and pull the files u want.
Alternate option: U cud put in an external sd card, and copy the files from internal sd to external sd if u are not comfortable with the pull commands.
diablo009 said:
Question: Do u happen to have any recent clockwork backup and/or tibu backups on ur phone? If either is present u could directly navigate to those folders (in adb) and pull the files u want.
Alternate option: U cud put in an external sd card, and copy the files from internal sd to external sd if u are not comfortable with the pull commands.
Click to expand...
Click to collapse
I do not have any type of backups apps or anything like that on the phone.
I have an external sd card however Im not sure how thats different than using adb to copy the files from the internal memory to my computer. I am fine with using pull but maybe im using the wrong directory name for my personal files?
Have you tried qtadb or droidexplorer. Would be easier imo.
newter55 said:
Have you tried qtadb or droidexplorer. Would be easier imo.
Click to expand...
Click to collapse
That requires a rooted phone right? My phone is currently not rooted and I don't know if I would want to. How come I cant just use the adb pull command on the folder with my data in it?
edit - i might have found a command that works, i will update when finished.
ok this worked for me: 'adb pull / d:\backup\'
thanks everyone for your help.
Yeah. Assumed you were rooted sorry. Just thought that way you could see everything and point and click.
So I have a similar situation to this only I have a phone that isnt rooted and usb debugging isnt enabled. However I know the phone boots on, and I can also get into recovery mode where I am able to ADB to get a basic shell, and see the device but that is about it. I feel that if I could enable usb debugging thru recovery mode I might be able to mount the /sdcard and then pull files from there. anyone got any ideas if I could get a reboot with usb debugging enabled from recovery or maybe just a command that I could use in shell via recovery?? Please Please lol. I have a strong feeling i might have hit a wall.
http://forum.xda-developers.com/showthread.php?t=1164598
Hi, I accidently master reset my atrix 2 and want to recover SMS from my device memory
I have done the following
- rooted my phone and activated CWM recovery but I am not able to access the internal memory as USB device so I can run any recovery program
- I tried to access the mmssms.db file in /data/data/com.android.providers.telephony/databases/mmssms.db through command prompt but the file is only 42KB, which means a blank file is created.
Is there a way I can access the internal memory as USB device?
or
are there any SU or ADB commands by which I can restore mmssms.db to an older date?
or
Any linux commands i can run to read the data on physical blocks (assuming some blocks of memory will still have some data even if the file is overwritten or the new .db file is not necessarily at the same physical location)
Any Linux developers out there who can help me with any commands to try?
As flash memory is actually erased, not just marked as no longer in use (like magnetic media) there may be no way to get you data back. However this is not ALWAYS the case, but I think it would be pretty difficult.
You may be able to dd the partition where your data was to a file on the sd card and then try to recover data from that once you transfer it to your pc.
Hello,
I have Samsung Galaxy Core Plus (SM-G350) with broken screen (totally black) and password set up.
I want to recover my internal card data, but any of my ideas wont work.
I have already installed CWM and tried to blindly mount /sdcard by USB, but I dont see any new drive on PC.
I wanted to root it, but any of methods I found wont work (maybe cause Im running in CWM? Yes, USB debugging is disabled).
I tried also 'adb pull', but I need to mount /sdcard (am I right?) where I get 'permission denied' error - in adb shell I cant perform any command except 'cd'.
Im thinking about flashing /data by Odin, but how to create the 'script' for it?
Anybody has any idea how can I do it?
Same Boat...
I've got a broken screen on Centura Galaxy. I managed to blindly ODIN CWM on it, and now get ADB in recovery, but debugging is off so I'm stuck with there. I've tried recovery screenshot tools to try to load rooted ROM, but had no luck. I know JUST enough to be dangerous, and not much more. Just need to get DCIM folder.
@xNombre
If this is still valid, you could try flashing TWRP onto the phone, where it should mount the SD Card automatically and it should connect to the PC automatically too. Search for TWRP (either 2.8 or 3) here on XDA
Hello Everyone,
I've been trying for more than a week now to recover data (photos, contacts, messages) from my HTC One M7 after I accidentally hit the factory reset button (was in a hurry to play squash and was fumbling around till the disaster happened!) :crying: Worse of all, I have no backups :crying::crying: My phone has no SD card, only the internal memory. It runs on Android 5.0.2 and has been rooted. I have busybox and TWRP installed on the phone. I have Android SDK and cygwin on my PC.
Initially, I tried to mount the phone's internal memory as a drive on Windows so I can do a scan of it using a data recovery tool. But I wasn't successful as MTP seems like the only option and there's no way to diable it. Even the disable MTP option inside TWRP doesn't make the drive accessible via USB! I have tried various recovery software available online but none of them can see my phone thanks to the stupid MTP!
Finally, I tried the steps on this thread precisely
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
Have managed to copy the whole memory block of the phone using
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
and created a mmcblk0.raw file which I can open using Disk Internals (Linux Reader). I found only the data that currently exists on the drive after the factory reset. Tried to access the image with TestDisk (as shown here - http://www.df.lth.se/~jokke/androidfilerecovery/) and I cannot see any of my old files there too! (I'm trying the Deeper Search Option now)
I'm not sure if 'dd' command copies the disk sector-by-sector. I think any data recovery software can scan the disk image and find the old files as long as I can create a sector-by-sector image of the phone's internal drive. If not, any way to mount the internal drive as a USB drive on Windows could work too! Can anyone please help me with this?
Many thanks in advance!!!!
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
johnfr92 said:
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
Click to expand...
Click to collapse
Hey...did u get dmsetup to work?