21

The exact location of the contacts database might depend on your manufacturer's "customization". While "plain Vanilla Android" has them in /data/data/android.providers.contacts/databases, the stock ROM on my Motorola Milestone 2 e.g. uses /data/data/com.motorola.blur.providers.contacts/databases/contacts2.db instead. A raw mask to check for is /data/data/*....


19

The sms database is stored in /data/data/com.android.providers.telephony/databases/mmssms.db which is what you want to do. Best thing to do, is this, do not plug in USB cable yet: Reboot into ClockWorkmod Recovery. Go into Mounts and Storage Select mount /data Plug in the USB From the windows command shell or terminal, adb shell Since you are in ...


11

As of Android 4.3+ and the implementation of TRIM it is now incredibly difficult to recover deleted files on the internal memory. Some of the suggested solutions probably will not be worthwhile unless you are able to scan the memory for the deleted file(s) very rapidly after deletion. Moreover, in the case of recovery after a factory reset, as of Android ...


11

A factory reset reformats the phone's user-data partition, but it's not a "secure" wipe; it doesn't overwrite everything with zeroes. If you want to be sure everything is erased, you can encrypt the phone first (which overwrites all the data with encrypted versions of itself), then do a factory reset (which sets up a new unencrypted filesystem). (Update: ...


9

First to clarify root and data: Root directory / of Android devices is a read-only pseudo (temporary) filesystem (rootfs) that lives in RAM and is vanished when device is powered off. When device is powered on, it's again extracted from initramfs that lives in boot partition along with kernel. On newer devices with system-as-root, system partition is ...


8

There is an app for this called Secure Deletion for Android, which can be used to overwrite the data. Another way to obfuscate the data would be to encrypt the device before using factory reset. This encrypts all your data, and after the device is reset, it will be very unlikely that the data can be recovered.


7

All of the solutions above require USB Debugging to be on. If it is not and you are using Android 4.0 then you can press power and volume down buttons simultaneously to obtain screenshot. If USB is not connected it will be placed somewhere on the SD card (e.g. \Pictures\Screenshots). Then you can connect USB to see the screenshot, then disconnect, navigate ...


7

There isn't an easy way, but still, it might be possible. The keyword to it is File carving (find some more links on this topic in our data-recovery tag-wiki). Make sure to not have any modifications/changes going on on your device, or at least as few as possible! Each change (written file etc.) lowers your chances of a successful recovery. A crucial pre-...


7

android_secure folder contains those apps which you have moved to external SD. Files inside them would have .asec extension Android 6.0 upwards don't allow you to move apps to external SD as you have been doing. They use adoptable-storage wherein the external SD card and internal storage are merged to create a bigger storage. You can read more in adoptable-...


6

Does your device has HDMI or TV out facility? If so, you can connect it to another display device (monitor/TV) and install applications to backup your stuffs. Another solution you could try is to install an app called Remote phone access via adb and control your device through PC. But the catch here would be that if have to configure the app for remote ...


6

HOW DELETED DATA IS RECOVERED? Data (un)deletion strongly depends on how a storage media (HDD, SSD, eMMC etc.), filesystem (NTFS, FAT32, ext4 etc.) and OS save and delete files. File carving / signature search / content-aware recovery identifies standard signatures values in the headers of deleted files (as file command and antivirus programs do to ...


5

These are located in /data/data/com.android.providers.telephony/databases/mmssms.db and /data/data/com.android.providers.contacts/databases/contacts.db Edit: I couldn't get adb pull working (requires root, can't remember how to call adb pull with root) but I just opened adb shell and used cp as root to copy it to /sdcard. Edit2: I found this thread ...


5

This suggestion assumes familiarity with connecting to the phone via ADB I had a similar situation on my previous phone. I was able to pull the important stuff over ADB when the phone was in recovery. In my case I had to mount some of the filesystems to access everything I wanted to retrieve. I'm not sure if it is dependent on the phone whether the ADB ...


5

In addition to the well-known Titanium Backup app (for which you must purchase the Pro key to unlock the CWM/TWRP nandroid backup support), there is another app now: Nandroid Manager, which according to its description can restore apps from nandroid backups even with the free version (there is a Pro key too, but it is required if you want to restore special ...


5

It contains 96x96 pixel versions of your photos. The file is simply a concatenation of JPEG files. You can split it into individual JPG files by searching for the signatures indicating the start and end of a JPG file, i.e. the two bytes FF D8 for the start and FF D9 as the end. If you can transfer the file to your computer and you can access Python, the ...


5

Note: OP already knows the answer but the following info is for those souls who might be troubled with the same issue. Disappointment! CM11 in OnePlus One (be it 44S or 05Q update) doesn't have any provision to get the Contacts and Call logs get backed up and restored using ADB. So unfortunately, the answer is simple: your contacts and call logs were not ...


4

I had the same problem with my S3 (broken screen, locked phone, Kies doesn't let me access it, etc). Solution: Get another working S3 from a friend, take off the backs of both phones, take off some screws, take the motherboard out, put your motherboard in the phone, turn it on, back up, done). Your data is saved on the motherboard, so you can just put it ...


4

You still got your SDcard contents You still got synced data on Google cloud associated with your Google account and other cloud services. Everything else is wiped out and cannot be restored All you can do is log in with same Google account on your device and it will restore some data from cloud like Google Contacts, Calendar and, maybe, settings for some ...


4

For common system apps like the ones you've mentioned, there's no way to uninstall or reinstall them: without root, it at all you can disable them (not all of them even). But they are usually not held in the playstore for re-installation. Even if they receive updates via the playstore (like GMail, Maps, and the Playstore app itself), some of them must reside ...


4

There is some hope to recover data which was stored on the “internal SD card”. Samsung Galaxy S2 supports USB connection in the mass storage mode (unlike some other more recent models). This mode provides the required block-level access to the partition which holds your media and other files (but not contacts, SMS and app data). Therefore you can connect ...


4

The Official XDA Discussion for CF Auto-Root (The tool OP linked) includes the following line: Note that if your device had not been unlocked before, this procedure will wipe all your data! So to answer your question: Does rooting format the /sdcard/ partition? No, rooting alone will not format the partition mounted at /sdcard/. When I root for the ...


4

I had the same promblem. A solution which worked for me was an app "MP4Fix", which you can get in google play for free. It repaired my video in a few sec and placed it in different folder (it kept corrupted video in the same place and also created new repaired one). I know this info might be too late for you but it might help some others.


4

Personally, I am a Nexus user. But having repaired a friend's international variant S3 before, I do know some things about Samsung. And since you don't have custom recovery, you cannot access /data (the partition where data is stored). So the way I know of will use a custom recovery to backup/restore data. This voids your warranty. I am assuming you already ...


4

You can't restore chat history from one platform to a different platform. Eg:- Window to Android or vice-versa as in your case. Read the below Whatsapp faq, http://www.whatsapp.com/faq/en/wp/28060005 It tells, You cannot restore chat history from any other phone type to Windows Phone, or from Windows Phone to another phone type. The Whatsapp for ...


4

Taking a screenshot requires root or system permissions (or an root exploit). I assume your ROM is a official Lineage release. Assuming further that their signing key has not leaked the app you are searching for should use root permissions is part of the OS. Therefore a first step would be revoke all allowances for apps to use root permissions. List ...


4

No you can't access your phone via adb while you are in fastboot menu. While in fastboot menu only the fastboot binary + driver can access your device. ADB is only available when the device is booted (adb is usually already available from a certain boot stage on while the device is still booting). Also certain recovery ROMs provide full ADB access. ...


3

File systems are organized in "blocks" of data, where each block has the same size. Internal storage (as well as some others which use NAND-Flash) on Android uses a block size of 128kB. Especially video files are a bit larger, so they do not fit in a single "block" on the file system. In order to store them, they are split and spread about multiple blocks. ...


3

It's impossible to obtain block level access to a block device without root, since all of those files grant the write permission only to root. At least I have never seen it any other way and I doubt that the S3 is an exception here. It's not because it's technically impossible, the default permissions simply forbid it. A this is done for a pretty good ...


3

If you were going from CM10 to CM10.1 — that is, moving from Android 4.1 to 4.2 — your data "loss" is probably because the path to your emulated SD card has changed due to the new multiuser support. Previously, the SD card was /data/media, but now it's a subdirectory such as /data/media/0, with additional subdirectories (such as /data/media/1) for ...


3

General information As The Andro Nerd pointed out in his answer, most apps store passwords (and other sensitive information) encrypted. Some even don't store them at all (they use a kind of "tokens", as is available with most Google apps -- or they don't store anything like that). Unfortunately, only most apps seem to care this way. Some store ...


Only top voted, non community-wiki answers of a minimum length are eligible