Pushas:
No wonder Nigeria is not developing. Op asked a valid and smart question. Just look at the STUPID responses above? Fools.

@OP I am also waiting for an answer too.

Pushas:
No wonder Nigeria is not developing. Op asked a valid and smart question. Just look at the STUPID responses above? Fools.

@OP I am also waiting for an answer too.

Mckandre:
On any hard disk, there is a table stored that says "File xxxxxxxx is stored in the following location(s): "
This ensures that for any request to file xxxxxxxxx, the drive knows where to go look for it. When a file is deleted, the first character of the filename is removed and marked as "unknown". This was the key to let the drive know that any of the locations listed for any filename starting with an unknown character were free to be overwritten with new data.
As long as no new data had been written over the sectors that originally housed that information, everything was still there and you could recover it simply by telling the table to restore the first character of the filename (I remember having to go through entire directories of data back in the 80s, trying to recall the first character of all the filenames so they could be undeleted, kind of like this:

"deleted file ?utoexec.bat -- First character: _"

Complete. Nightmare. Anyway, I digress)

So that allows a pretty easy method of recovering a file providing the sectors that housed it hadn't yet been overwritten. The Windows recycle bin simply delays this process by moving "deleted" files into a special holding area, noting the original location and date it was deleted. After a certain period of time, the "proper" delete takes place.

Now, some people realised that if they wanted to actually get rid of a file, a simple delete might not be sufficient, after all simply by restoring the data in the file table, there's a reasonable chance it might be able to be recovered, especially if it hadn't been a long time since the delete took place. So a method called "zero filling" was invented. This involved filling every byte of the original file with a "0", and then deleting the file. That way, even if you do restore the data in the file table, all you're going to get back is an empty file. It effectively ensures that the disk sectors are already overwritten at the time of deletion.


If u understand how magnetic media operates and still wanna understand the next phase follow the link.
https://www.quora.com/Where-do-deleted-files-go-1

Pushas:
No wonder Nigeria is not developing. Op asked a valid and smart question. Just look at the STUPID responses above? Fools.

@OP I am also waiting for an answer too.

sinaj:
Lwkmd

Op just go sleep. I doubt if u will get the answer here

Mckandre:
On any hard disk, there is a table stored that says "File xxxxxxxx is stored in the following location(s): "
This ensures that for any request to file xxxxxxxxx, the drive knows where to go look for it. When a file is deleted, the first character of the filename is removed and marked as "unknown". This was the key to let the drive know that any of the locations listed for any filename starting with an unknown character were free to be overwritten with new data.
As long as no new data had been written over the sectors that originally housed that information, everything was still there and you could recover it simply by telling the table to restore the first character of the filename (I remember having to go through entire directories of data back in the 80s, trying to recall the first character of all the filenames so they could be undeleted, kind of like this:

"deleted file ?utoexec.bat -- First character: _"

Complete. Nightmare. Anyway, I digress)

So that allows a pretty easy method of recovering a file providing the sectors that housed it hadn't yet been overwritten. The Windows recycle bin simply delays this process by moving "deleted" files into a special holding area, noting the original location and date it was deleted. After a certain period of time, the "proper" delete takes place.

Now, some people realised that if they wanted to actually get rid of a file, a simple delete might not be sufficient, after all simply by restoring the data in the file table, there's a reasonable chance it might be able to be recovered, especially if it hadn't been a long time since the delete took place. So a method called "zero filling" was invented. This involved filling every byte of the original file with a "0", and then deleting the file. That way, even if you do restore the data in the file table, all you're going to get back is an empty file. It effectively ensures that the disk sectors are already overwritten at the time of deletion.


If u understand how magnetic media operates and still wanna understand the next phase follow the link.
https://www.quora.com/Where-do-deleted-files-go-1

hajlat2:
Back to play store, Apple store etc. My reason is simple, if you bought a product and you are not satisfied , all you need to do is to return it to the store you bought it.

rozay12345:
In simple terms, all information which include media, files are stored in a disk drive. These information are just a series of 0s and 1s on the magnetic drive with a pointer being directed to them. If information a is saved as 00000001, when you delete it from your hard drive, the information become scrambled and there will be no pointer to it, these information might result into 11110101. That is why it is said there is no true deleting, with a Magnet, you can always retrieve your information back.

Pushas:
No wonder Nigeria is not developing. Op asked a valid and smart question. Just look at the STUPID responses above? Fools.

@OP I am also waiting for an answer too.