Anyone know about this? I download a lot of recovery software but all can't detect my sd card. It shows portable devices in pc. Is it because of this?
Sent from my GT - I9300 on Omega Rom
Deleted means gone .
jje
johnkhor123 said:
Anyone know about this? I download a lot of recovery software but all can't detect my sd card. It shows portable devices in pc. Is it because of this?
Sent from my GT - I9300 on Omega Rom
Click to expand...
Click to collapse
It's because the internal sdcard is in fact a subfolder of /data partition, formatted in ext 4 file system format. So to be readable by all computers, it's mounted as a virtual fat disk using fuse kernel module.
Recovering data needs a full raw access to the file system, that is not possible here with mtp protocol.
There must be ways to recover but needing probably heavy console use and I don't have much idea about this.
And no, erasing doesn't mean it's gone, simple erasing just remove the file name from the allocation table, but the file is still there. So by reading directly the blocks you can recover files as long as the they have not been overwritten.
A real erase means overwriting the blocks with random data at least 7 times (nsa protocol).
And no, erasing doesn't mean it's gone, simple erasing just remove the file name from the allocation table, but the file is still there. So by reading directly the blocks you can recover files as long as the they have not been overwritten.
As you say but as nobody has yet succeed in recovery for all intents and purpose they are gone .Hence my reply in the negative as per multiple posts all asking the same question and failing to recover by standard methods .
jje
Striatum_bdr said:
It's because the internal sdcard is in fact a subfolder of /data partition, formatted in ext 4 file system format. So to be readable by all computers, it's mounted as a virtual fat disk using fuse kernel module.
Click to expand...
Click to collapse
It's mounted through fuse but not as a Fat device. Why should it if you got Mtp (yuck) which deals with the transfers.
And no, erasing doesn't mean it's gone, simple erasing just remove the file name from the allocation table
Click to expand...
Click to collapse
With Ssd's it's far more complicated than with Hdd's since they have features such as trim. Additionally having Ext doesn't help either since it's notoriously hard to recover files from it due to it's inner workings
A real erase means overwriting the blocks with random data at least 7 times (nsa protocol).
Click to expand...
Click to collapse
Nsa recommends something around 35 for secret informations. High-tech Labs are capable to restore up to 8 overwrites at least partially.
Sent from my GT-I9300 using xda premium
Related
Hi there is there anyone else that have issues with their extsdcard?
I get the folder "LOST.DIR" all the time i boot, anyone know how to fix this?
The sdcard is an Adata 32gb class 10
it's normal, I had it with all my android phones.
That folder is from the filesystem.
If the filesystem should loose any files (meaning loose it's name and folder location) it will put it in there for you to recover.
d4fseeker said:
That folder is from the filesystem.
If the filesystem should loose any files (meaning loose it's name and folder location) it will put it in there for you to recover.
Click to expand...
Click to collapse
how will the filesystem loose any file in the first place.. just curious
Its not lose a file as such .
Its corrupt file folder use the phone with USB connected or pull battery during use and files corrupted get placed there as damaged . Dont think you can recover them .
jje
how will the filesystem loose any file in the first place.. just curious
Click to expand...
Click to collapse
Filesystems are a rather complicated thing.
Modern filesystems such as NTFS, EXT3/EXT4, ZFS, ... all use a so-called Journal in which, as the name implies, they write "I'm now going to create file X in the folder Y", then they create file. Afterwards the entry is removed from the Journal.
If -for whatever reason- the computer or filesystem crashes, on next startup it will look at the entries in the journal and try to roll them back. This MAY cause your computer to loose the data of the last seconds before the crash but it ensres that the filesystem has it's full integrity and won't cause further trouble.
Old filesystems such as EXT2, FAT16, FAT32, exFAT do not have this technology.
If the system had an unclean shutdown it will need to scan the whole filesystem (which can take several hours for modern disk capacities) for any files that have not been completely written or have mismatching entries in the index.
These (partial) files will then be written to the LOST.FOUND folder for Linux-OS's (Windows has other recovery methods)
On EXT3, ... the folder thus seems obsolete but will still be used to recover files which have been corrupted by low-level software issues or hardware failure.
Hope this clarifies it =)
Thankyou eveybody now i can relax!
Weird,
Android says my SD card is corrupt and only offers to format it.
Windows says the same.
CWM doesn't, as far as I can see, see it either, EXCEPT when I ask it to install a zip from it... it can see everything on the SD card and installs successfully from it!
Problem is, I need to copy stuff from the card before reformatting it.
Any ideas on how I might do that?
P.S. Yes, it is definitely the SD card and not the internal one
P.P.S. Windows doesn't see the phone when connecting under CWM...should do though shouldn't it. Perhaps that's my problem..?
Thanks.
Are you rooted? If yes, maybe running e2fsck on the command-line will sufficiently recover it to be mounted.
Alternatively you can use Recuva under Windows to find and rescue the files you need, or chkdsk to attempt a repair.
Is it a Fat32 or exFat (Fat64) filesystem and is there any reason such as removing it without ejecting, that could have caused this?
Sent from my GT-I9300 using xda premium
d4fseeker said:
Are you rooted? If yes, maybe running e2fsck on the command-line will sufficiently recover it to be mounted.
Alternatively you can use Recuva under Windows to find and rescue the files you need, or chkdsk to attempt a repair.
Is it a Fat32 or exFat (Fat64) filesystem and is there any reason such as removing it without ejecting, that could have caused this?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the prompt reply.
It is rooted, although I tried to install this e2fsck through CWM and it gave me generic errors. Not being a Linux man I wouldn't feel that comfy with stuff like that anyway though.
The card is exFAT so I think Chkdsk (Win7) won't fix anything IFAIK. Oh, Windows says the card isn't formatted though, so won't do anything.
Recuva is unable to determine the file system.
:-(
I installed CM9 from the card, which then couldn't read it (I didn't know CM9 didn't support exFAT), so I restored my previous backup from the Sammy rom so it would be back to normal. But when it booted up the first time post-restore, it said the card was corrupted.
The kernel is what defines whether a filesystem can be or can't be mounted since it includes the filesystem logic. So replacing the kernel always helps if a ROM cannot mount the filesystem.
(Except for special userland filesystem based on Fuse)
It sounds like the partition table got badly corrupted, either by software or hardware.
I'm sure it didn't give you the output "generic errors". We're here to help guide you through the process if you have not enough knowledge but you'll at least have to try. However I don't know how I managed to type e2fsck, since that one is for Ext2 filesystems which has nothing in common with Fat64. You'll have to use a computer to repair it...
After having plugged in the card, could you please go to the Start menu and type 'diskmgmt.msc', then hit ENTER.
Check if the removable disk is initialized and contains a partition (aswell as what the type of the partition is)
It probably shows an unitialized disk, a disk with a RAW partition or a disk without any partitions.
If that is the case, try http://www.cgsecurity.org/wiki/TestDisk
You'll find a reference to a lot of other (free and paid) tools on this page: http://www.hiren.info/pages/bootcd in the Section "Recovery Tools"
Depending of what your data is worth to you, you'll want to get a bitwise backup of the content first so if you screw up during recovery nothing is really lost.
I wasn't being lazy, just keeping in mind how important the data is and how much effort it's worth expending.
The answer was 'not that important' and I ended up formatting it using the very brilliant fat32format.exe (after trying with Windows Pish 7).
It must have been pretty screwed as TestDisk found nothing of any value there at all. (It was RAW in Windows).
But the upshot is I now have a FAT32 formatted 64GB (hopefully, unless it's a dodgy one) SD card that will work on Sammy and AOSP roms.
Thanks for your time, d4f.
Hi ive done a bit of searching but was unable to find an answer i was please with...
If i want to update my CM9 to a newer version.. WIll i lose all of the data on my phone (just like reformatting all over again)
or will it just flash over the top of it and carry on as normal..? I found these instructions but they're unclear
Upgrading from earlier version of CyanogenMod 9:
- Copy CM9 ZIP to your internal SDCard
- Boot into Recovery
- Flash CM9 zip
- Reboot.
I also have an issue with my SD card corrupting everytime i flash ROM.. is this normal, or just unlucky and what are the chances of it happening on an update of the ROM?
Your answer's are appreciated
I also have an issue with my SD card corrupting everytime i flash ROM.. is this normal
Totally abnormal and suggests a faulty card .
jje
WIll i lose all of the data on my phone (just like reformatting all over aga
Click to expand...
Click to collapse
No, it will only format and replace the /system which does not include data but only the operating system itself.
Even the configuration for the OS is stored in another location, so it's really install-reboot-enjoy.
I also have an issue with my SD card corrupting everytime i flash ROM
Click to expand...
Click to collapse
I've seen lots of people having issues with the SDcard after format. Mine survived roughly a dozen ROM flashes and it's a FAT32-formatted Class10 Samsung 32GB.
What filesystem is on your SDcard?
d4fseeker said:
No, it will only format and replace the /system which does not include data but only the operating system itself.
Even the configuration for the OS is stored in another location, so it's really install-reboot-enjoy.
I've seen lots of people having issues with the SDcard after format. Mine survived roughly a dozen ROM flashes and it's a FAT32-formatted Class10 Samsung 32GB.
What filesystem is on your SDcard?
Click to expand...
Click to collapse
I will most likely format it to FAT32- it's a class 10 64gig, is there a way to format it without doing it via the phone? it won't let me format just using the phone..
thanks for your above advice
is there a way to format it without doing it via the phone? it won't let me format just using the phone..
Click to expand...
Click to collapse
Through an adapter on the computer. You'll need a non-default Application though, e.g. the HP Format Utility.
Windows, for compatibility reasons, restricts FAT32 sizes to 32GB.
I believe the media is still SDcard but they won't show up in gallery or on my PC. Can anyone please help me out? Am I out of luck?
Sent from my SCH-I605 using Tapatalk 2
probably... there is always a chance that things will get corrupted when you disconnect without unmounting. sorry man!
Look for a app called hexamob sdcard recovery and set the search to jpg and other image file types
Sent from my GT-N5110 using XDA Premium HD app
yeah hexamob might work if youre lucky. but your SD card is likely gone bud.
If im not mistaken, the idea is that when there are any data transfers, bits of data are stored into different addresses in memory, and when you pull it out in the middle of some important read-write operation, the index gets gaps and the information stored on it no longer has the proper addresses indexed. So essentially your device doesnt know where one file starts and another begins.
If its fat sometimes standard utility programs such as Mac OS X's "Disk Utility" or Windows' SCANDISK can be used to repair a corrupted filing system such that it will be usable, and then you can use a data recovery program to recover information, so long as you didnt write over the cells that the data you want was stored in previously after repair. So try to format it without adding new things to the SD card before you do a data recovery.
good luck!
Hello Everyone !
Last week i was trying different ways to mount our phone storage ( internal as well as card ). What im about to share is the result of some experiments done at that time.
This is not a guide exactly, as many of us know the steps done here, but still, i take no responsibility of any type of problem you face.Please ask for help if you need.
for more information : Read this.
When i checked my internal storage, it was 72% fragmented !!!
so i thought may be there are others who haven't formatted internal/external storage for a year or above, thus leading to heavy fragmentation.
here it is :
method 1: (also applicable for card storage)
take backup of all data and format. That should solve it !
method 2:
i recommend using 360 security app(with root access) first.
let the app scan your phone, it will find app cache, trash and user data in your phone. but first uninstall unused apps and delete some data that you don't need. you can always copy it back if you need it.
clean all, including empty folders (it will increase simplicity of your storage).
How to Mount Internal Storage as USB DRIVE :
1. Reboot into CWM
2. Connect phone to a windows PC (prefer win 7)
3. Go to "USB mass storage"
4. Select mount sd card.
5. You should see your internal mounted as removable mass storage drive.
6. Enjoy unrestricted access to your internal drive.
--------------------------------------
All right guys, i dont know much about the ssd, but if it is not necessary (even at > 50% of frag-level ), please tell me.
Thank you !
And here I am, thinking that we are using the EXT file system. :|
at least Samsung uses ext4, i think Sony does that too ...
DigitalDreamer said:
And here I am, thinking that we are using the EXT file system. :|
Click to expand...
Click to collapse
deshx said:
at least Samsung uses ext4, i think Sony does that too ...
Click to expand...
Click to collapse
Samsung uses their own filesystem in the newer devices.
And I think Sony uses ext4. But the thing is why would we need defragmentation if it's ext4. The files aren't accessed as in windows. Of course that windows will find disk errors and that there is a need if defrag. But the way Linux works, do we really need that?
file access is not the issue. i think the way ext4 manages writes makes all the difference.
ext3/ext4 avoid fragmentation of data and the way they store data, they can easily manage new read/writes without decreasing performance.
but even ext4 gets some issues, i found after some googling that when free space is less than ~15%, ext4 does not get enough room to swap things around. that fragments the drive heavily, thus the issues.
in that case, defragmenting might do some good.
DigitalDreamer said:
Samsung uses their own filesystem in the newer devices.
And I think Sony uses ext4. But the thing is why would we need defragmentation if it's ext4. The files aren't accessed as in windows. Of course that windows will find disk errors and that there is a need if defrag. But the way Linux works, do we really need that?
Click to expand...
Click to collapse
deshx said:
file access is not the issue. i think the way ext4 manages writes makes all the difference.
ext3/ext4 avoid fragmentation of data and the way they store data, they can easily manage new read/writes without decreasing performance.
but even ext4 gets some issues, i found after some googling that when free space is less than ~15%, ext4 does not get enough room to swap things around. that fragments the drive heavily, thus the issues.
in that case, defragmenting might do some good.
Click to expand...
Click to collapse
Oh yeah, on low space. Well on my U from 4GB I usually have around 2.5GB free so I guess I'm safe for now.
Btw the fragmentation usually shows losing performance when accessing libs and stuff. But that doesn't apply to us.
i had only 500mb free some time ago, so i did defrag the internal at that time(72% fragmentation), but now i have 3 gb free ! :highfive: .so its same for me ...no need !
DigitalDreamer said:
Oh yeah, on low space. Well on my U from 4GB I usually have around 2.5GB free so I guess I'm safe for now.
Btw the fragmentation usually shows losing performance when accessing libs and stuff. But that doesn't apply to us.
Click to expand...
Click to collapse
Internal storage (/sdcard) uses FAT32 file system, the data partition uses ext4 file system.
I know that defragmenting a flash drive is useful only to cause more wear and tear.
Are you all insane? You can't defragment flash drives!
That slows it down and eventually will ruin it.
Sent from Hacker's U on CM11 Weekly
If sdcard uses fat32, then it should be defragmented....otherwise its fine...
One doubt though, internal is named sdcard too....
You mean external storage, right?
HandyMenny said:
Internal storage (/sdcard) uses FAT32 file system, the data partition uses ext4 file system.
I know that defragmenting a flash drive is useful only to cause more wear and tear.
Click to expand...
Click to collapse
Sent from my ST27i
hackerpower said:
Are you all insane? You can't defragment flash drives!
That slows it down and eventually will ruin it.
Sent from Hacker's U on CM11 Weekly
Click to expand...
Click to collapse
so we shouldn't need to defragment internal or card.... Right?
Well I wasn't aware of this...
Sent from my ST27i
deshx said:
If sdcard uses fat32, then it should be defragmented....otherwise its fine...
One doubt though, internal is named sdcard too....
You mean external storage, right?
Sent from my ST27i
Click to expand...
Click to collapse
Internal storage use FAT32 filesystem, external storage use FAT/FAT32/exFAT.
Both are flash drives and shouldn't be defragmented.