Help Recover deleted files on Android 6.0

[umeryamin]

Hello, I have a Samsung Galaxy A5 (2016) currently running Android 6.0.1. There were some photos which I deleted back in July, I want to recover them from the internal memory, however the storage is only 16 GB and most of the time it has remained almost full since then, also there are some whatsapp conversations, text messages, and whatsapp images and videos that I want to recover ever since I bought the phone, most of the images and videos were deleted immediately after I received them. Is there any way to recover all of this data? My phone is not rooted, if the process requires root and can be done, do let me know, thanks.

 

[scary alien]

Welcome to AF, @umeryamin .

Unfortunately, when you delete a file, the storage locations that were linked/associated are freed-up and made immediately available for other files to use when they are created.

So, any additional activity (i.e., new file creation and/or file growth) will make recovery of the original file nigh impossible.

There are recovery strategies available for rooted devices, but you'd still have to deal with the consequences of the subsequent file activity after the delete...

Not sure what else to tell you .

 

[umeryamin]

Welcome to AF, @umeryamin .

Unfortunately, when you delete a file, the storage locations that were linked/associated are freed-up and made immediately available for other files to use when they are created.

So, any additional activity (i.e., new file creation and/or file growth) will make recovery of the original file nigh impossible.

There are recovery strategies available for rooted devices, but you'd still have to deal with the consequences of the subsequent file activity after the delete...

Not sure what else to tell you .

What consequences? Even thumbnails or blurred low quality images would work. If that's what you mean.

 

[scary alien]

The consequences are that you've changed files and made it virtually impossible to put Humpty Dumpty back together again.

Android and it's Linux kernel are not like MS/Windows where a recycle bin feature has been implemented.

Basically, when a file is deleted, it is gone.

 

[umeryamin]

The consequences are that you've changed files and made it virtually impossible to put Humpty Dumpty back together again.

Android and it's Linux kernel are not like MS/Windows where a recycle bin feature has been implemented.

Basically, when a file is deleted, it is gone.

Alright thanks, then what about all these data recover softwares that I found on Google? Most of them require root.

 

[scary alien]

Well, even if you found a reputable one that wasn't snake oil and you managed to root your device, there's still the issue of how long it's been since your deletes and the subsequent activity that would mean there's nothing the utility could recover anyway.

 

[chanchan05]

If you want to keep data, you should copy the stuff to a PC or hard drive, not delete. OneDrive is better than Google in the sense that you can set it to automatically backup any folder with photos on your phone, even a newly created one. You can install that.

As for the recovery software, as stated above, any activity could have deleted them. Basically the recovery software only works if you use them right after deletion. If you so much as received a text message after deleting, they'd be unrecoverable.

Think of it this way: Windows has a bin in the house. You can review your trash there before you take it out. Android doesn't have a bin. Deleting in Android is like flushing stuff in a toilet. You can't put your hand in there to pull crap back up.

 

[umeryamin]

If you want to keep data, you should copy the stuff to a PC or hard drive, not delete. OneDrive is better than Google in the sense that you can set it to automatically backup any folder with photos on your phone, even a newly created one. You can install that.

As for the recovery software, as stated above, any activity could have deleted them. Basically the recovery software only works if you use them right after deletion. If you so much as received a text message after deleting, they'd be unrecoverable.

Think of it this way: Windows has a bin in the house. You can review your trash there before you take it out. Android doesn't have a bin. Deleting in Android is like flushing stuff in a toilet. You can't put your hand in there to pull crap back up.

Thanks alot.

 

[scary alien]

Just to explain a little more on what goes on when you create a file and populate it with data. Here's a simplified and somewhat generic example:

- file creation request is made
- an entry for that file is added to the directory where the file will live (in Linux, that entry is called an inode)
- if and when data is added to the file, storage blocks are allocated / taken from a free list by the filesystem
- the directory entry for that file gets updated with links/pointers to the storage blocks that were allocated

/mydirectory [directory]

file pointer entry for file1.txt

pointer to now allocated storage block (#1111)
pointer to now allocated storage block (#1112)
pointer to now allocated storage block (#1113)
​

file pointer entry for file2.txt

pointer to now allocated storage block (#2222)
pointer to now allocated storage block (#2223)
pointer to now allocated storage block (#2224)​

So now imagine that you've deleted file1.txt...what happens next?:

- storage blocks #1111, #1112, and #1113 are de-allocated and made available/free to be allocated to other files

- if file2.txt grows, it's entirely possible that one or more of the now free storage blocks #1111, #1112, and #1113 could be assigned and allocated for file2.txt; so things might now look like this:

/mydirectory [directory]

​

file pointer entry for file2.txt

pointer to now allocated storage block (#2222)
pointer to now allocated storage block (#2223)
pointer to now allocated storage block (#2224)
pointer to now allocated storage block (#1111)​

As you can see, block #1111 that was previously used by file1.txt has now been used and re-written with contents for file2.txt, thereby making the recovery and reassembly of file1.txt impossible.

Hope that helps!

 

[michaelkenward]

This bit is another reason why you have to accept what other people have said.

...however the storage is only 16 GB and most of the time it has remained almost full since then

If the storage space has always been full, then your phone is constantly busting a gut to use the space that you freed up by deleting things.

The bit of memory where you had your pictures will have been used many times since you made that fateful click.

You have a slim chance of recovering things from memory that is mostly empty. If it is full, forget it.

 

[umeryamin]

Just to explain a little more on what goes on when you create a file and populate it with data. Here's a simplified and somewhat generic example:

- file creation request is made
- an entry for that file is added to the directory where the file will live (in Linux, that entry is called an inode)
- if and when data is added to the file, storage blocks are allocated / taken from a free list by the filesystem
- the directory entry for that file gets updated with links/pointers to the storage blocks that were allocated

/mydirectory [directory]

file pointer entry for file1.txt

pointer to now allocated storage block (#1111)
pointer to now allocated storage block (#1112)
pointer to now allocated storage block (#1113)
​

file pointer entry for file2.txt

pointer to now allocated storage block (#2222)
pointer to now allocated storage block (#2223)
pointer to now allocated storage block (#2224)​

So now imagine that you've deleted file1.txt...what happens next?:

- storage blocks #1111, #1112, and #1113 are de-allocated and made available/free to be allocated to other files

- if file2.txt grows, it's entirely possible that one or more of the now free storage blocks #1111, #1112, and #1113 could be assigned and allocated for file2.txt; so things might now look like this:

/mydirectory [directory]

​

file pointer entry for file2.txt

pointer to now allocated storage block (#2222)
pointer to now allocated storage block (#2223)
pointer to now allocated storage block (#2224)
pointer to now allocated storage block (#1111)​

As you can see, block #1111 that was previously used by file1.txt has now been used and re-written with contents for file2.txt, thereby making the recovery and reassembly of file1.txt impossible.

Hope that helps!

Yes that was really helpful and simple, thank you