Hi all
I have a Samsung S20 Ultra with a memory card that all of my photos are saved to, unfortunately I had to take my phone into Samsung experience store for a screen / back cover repair, the staff removed my Memory card and told me to factory reset due to GDPR as the device had to be sent away, when my device returned in the post 5 days later I went to put the memory card back in and a notice appeared stating the memory card is encrypted to a different device! I am totally devastated as there are pictures of my father who has passed away and other images that they are the only copies I have, I know now I should have unencrypted the memory card before the factory reset. I have spoken to Samsung directly so say there is nothing that can be done.
does anyone know of a way I can get round this I would be so very grateful!
Thanks in advanced
Stu
The best thing I could suggest is a third party solution that may be able to decrypt the information on the card, such as FeExplorer. Check to see if you have a "Decrypt SD card" option in the Lock Screen and Security settings, although I suspect it won't be able to do it.
The problem is, the encryption key is unique and stored in user data. When data is wiped during a factory reset, the key is wiped as well, so even if the user configures the same lock settings (password, pattern, etc) they key would be different.
I am not aware of an absolute solution, but here is what I would strongly suggest you do:
If able, make sure the contents of the card are backed up. Use cloud storage such as Google Drive.
Keep the card in a safe place; maybe put it in a small envelope or something, and mark it in such a way as to discourage accidental discarding or wiping.
Buy a new SD card to use in the meantime while you look for a way to recover the information on the encrypted card.
I am sorry for your loss, and I wish I had a better answer for you.
Edit: Found this on another site, maybe it's worth a try. MAKE SURE YOU BACK UP THE DATA ON THE CARD IN CASE THIS GOES WRONG.
On a PC: Copy (the encrypted and unreadable) contents of the sd card from the phone to your harddrive
On the phone: Settings -> Storage -> Sd Card -> Format sd card (this erases all the data on the sd card but don't worry you have a copy on the PC)
On the phone: Settings -> Security -> Encrypt sd Card (should be real fast since it's an empty sd card)
On the PC: Copy the contents of the sd card onto the phone
On the phone: Settings -> Security -> Decrypt sd card (edit: this may take a while depending on how much data was on the card)
sorry but none of the above "solutions" makes any sense. it is not possible to recover data. encryption key was located /data/misc/vold and /data itself was encrypted, too. Furthermore one can't access /data aka userdata partition.
BUT... and here comes the but.. adoptable-storage usually is DISABLED in One UI
So how is it possible your MicroSD Card is encrypted at all? It's not, except you have installed custom ROM or installed any 3rd party encryption tool (you would remember)
There is a good chance your MicroSD Card is plain exFAT or Fat32 unencrypted file system. I recommend to use a card reader for PC and make a 1:1 dump with gddrescue and analyze the dump with photorec or other file carver solutions.
There exist tools for windows too, for example
https://www.klennet.com/carver
https://www.z-a-recovery.com
https://www.runtime.org
Don't buy any software if your MicroSD Card is encrypted, it will definitely not work.
You can easily check if your MicroSD Card is encrypted by opening raw disk image with HxD hex editor and search for any plain text or series of zeros. gparted or testdisk will tell you if partition table exist
aIecxs said:
sorry but none of the above "solutions" makes any sense. it is not possible to recover data. encryption key was located /data/misc/vold and /data itself was encrypted, too. Furthermore one can't access /data aka userdata partition.
BUT... and here comes the but.. adoptable-storage usually is DISABLED in One UI
So how is it possible your MicroSD Card is encrypted at all? It's not, except you have installed custom ROM or installed any 3rd party encryption tool (you would remember)
There is a good chance your MicroSD Card is plain exFAT or Fat32 unencrypted file system. I recommend to use a card reader for PC and make a 1:1 dump with gddrescue and analyze the dump with photorec or other file carver solutions.
There exist tools for windows too, for example
https://www.klennet.com/carver
https://www.z-a-recovery.com
https://www.runtime.org
Don't buy any software if your MicroSD Card is encrypted, it will definitely not work.
You can easily check if your MicroSD Card is encrypted by opening raw disk image with HxD hex editor and search for any plain text or series of zeros. gparted or testdisk will tell you if partition table exist
Click to expand...
Click to collapse
when you put an SD card into a Samsung ultra it asks if you want to encrypt it through their own software, no third party apps were used
True, I realized after posting. Samsung is always bit special, they tried to think differently... In that case your data was lost in the moment of factory reset.
https://www.samsung.com/au/support/mobile-devices/how-to-encrypt-decrypt-sd-card
Stu_C said:
Hi all
I have a Samsung S20 Ultra with a memory card that all of my photos are saved to, unfortunately I had to take my phone into Samsung experience store for a screen / back cover repair, the staff removed my Memory card and told me to factory reset due to GDPR as the device had to be sent away, when my device returned in the post 5 days later I went to put the memory card back in and a notice appeared stating the memory card is encrypted to a different device! I am totally devastated as there are pictures of my father who has passed away and other images that they are the only copies I have, I know now I should have unencrypted the memory card before the factory reset. I have spoken to Samsung directly so say there is nothing that can be done.
does anyone know of a way I can get round this I would be so very grateful!
Thanks in advanced
Stu
Click to expand...
Click to collapse
Hello, have an experience that my samsung device were dead and my sd card still encrypted.
Firstly, you have to backup entire data on your sd card just in case.
And then, format your sd card using another device (maybe your another android).
Last, put your sd card to windows device and recover all data with DiskDigger software.
It's work on my sd card, give it a try.. Dont forget to backup all data
Related
Tired of that small 5gb usb storage? Here is my hack to swap your external SD card with the USB storage!
This is usefull especially if you use GPS apps that download maps or games that download big data files! I got the idea and studied several hacks for the galaxy 1900 so partial credit goes to whoever made those hacks.
DISCLAIMER : I have only tested this on the 4.0 U.S version running 2.3.5 and am not responsible for a brick (although it seems impossible to brick your phone while messing with this file).
So basically start by going to /system/etc using root explorer or similar (yes, you need root). Once there backup the vold.fstab file to somewhere ON ROOT (I put it in /data/app/)! This is important so you can access it if you need to restore it (also make sure root explorer is installed on device memory, not SD card). Now take my modified vold.fstab and replace the original in /system/etc, then change the permissions to rw-r--r-- (long click the file, then select permissions) . If all goes right after you reboot your device, USB storage should now be your SD card and vise versa! Be aware any apps on your USB storage will now have to be transfered using a PC, move the .android_secure folder to your SD card. Hope it works!
EDIT: here is a modified version for the yp-g70, all credit goes to rjsmith2007 for making and testing this!
Won't Maps pull data from the Ext SD anyway? All my music is on ext SD and players have no problem finding it; I would think maps would be the same. It's really like a 5gb and 16 gb (in my case) partition (isn't it?).
I'm looking for a reason to root, SD card/space is not one of them. My battery only charging to 90% is though, need to recalibrate (since it's never hit 100%)
tcat007 said:
Won't Maps pull data from the Ext SD anyway? All my music is on ext SD and players have no problem finding it; I would think maps would be the same. It's really like a 5gb and 16 gb (in my case) partition (isn't it?).
I'm looking for a reason to root, SD card/space is not one of them. My battery only charging to 90% is though, need to recalibrate (since it's never hit 100%)
Click to expand...
Click to collapse
I am referring to when you download maps with an app like sygic;
it saves it to the /sdcard/ directory instead of the /sdcard/external_ed/. Also gameloft games do the same and can use up your room pretty fast. I find this pretty useful myself, since I have a 32gb sd card, but just wanted to post it so if anyone does ever need it, it's here for them.
iJimaniac said:
DISCLAIMER : I have only tested this on the 4.0 U.S version running 2.3.5 and am not responsible for a brick (although it seems impossible to brick your phone while messing with this file).
Click to expand...
Click to collapse
I just tried it with my Galaxy S Wifi 5.0. The mapping of the internal sd to the external_sd folder fails, but it works for mapping my external sd to the sdcard folder.
Edit: I took a look at the original and made a modification to yours to work with the YP-G70 model (the 5 inch one). Just copy the file from within the zip folder to your /system/etc folder.
rjsmith2007 said:
I just tried it with my Galaxy S Wifi 5.0. The mapping of the internal sd to the external_sd folder fails, but it works for mapping my external sd to the sdcard folder.
Edit: I took a look at the original and made a modification to yours to work with the YP-G70 model (the 5 inch one). Just copy the file from within the zip folder to your /system/etc folder.
Click to expand...
Click to collapse
Thank you! I appreciate it! I post it on the original post and give you the credit.
Thanks man. I appreciate it. I was trying to do this myself before, but ended up having to format my SDcard and gave up. Thanks for the help!
rjsmith2007 said:
Thanks man. I appreciate it. I was trying to do this myself before, but ended up having to format my SDcard and gave up. Thanks for the help!
Click to expand...
Click to collapse
glad I could help!
Can't I just copy all of the data from my internal sd card onto my computer, remove the internal sd card, copy those files onto a larger sd card and put the larger sd card back into the galaxy player? Im sorry if this Queston has been asked before, or if it sounds stupid, but I can't find the answer to this Queston anywhere! Thanks in advance!
(P.S) This post was made with a Samsung Galaxy Player 5.0! No joke!
freshpintreez said:
Can't I just copy all of the data from my internal sd card onto my computer, remove the internal sd card, copy those files onto a larger sd card and put the larger sd card back into the galaxy player? Im sorry if this Queston has been asked before, or if it sounds stupid, but I can't find the answer to this Queston anywhere! Thanks in advance!
(P.S) This post was made with a Samsung Galaxy Player 5.0! No joke!
Click to expand...
Click to collapse
Hi,
There's still a bit of confusion with respect to terminology, I think (including myself).
I *think* that when the SGP5 displays "internal sd card", it's only part of the "internal 8GB memory". That "internal 8GB memory" is probably, I guess, something like an SDCARD or flash memory module that's soldered to the mainboard, and with Android, I think that it's split into a couple of areas.
Here's my "guess" of how things are arranged, using the terminology from Settings==>SD card and device storage:
"System storage": Part of the 8gb internal memory, e.g., includes /system, etc.
[1.65GB, in my SGP5]
"USB Storage" = "internal sd card" = /sdcard: The rest of the 8gb internal memory.
[5.01GB, in my SGP5]
"SD Card": The external microSD card, if you have one plugged in. Appears at /sdcard/external_sd.
[29.81GB, in my SGP5, where I have a 32GB microSD card plugged in.]
That System storage + USB Storage totals 1.65+5.01 GB, or 6.66GB. I guess the remainder of the 8GB is for bootloader, etc.?
Jim
Looks about right. Task Manger has them labeled like you list them, except there is a "Personal data" partition. It's 133mb on my 5.0. Maybe email and contacts?
I'm guess apps get installed on "System Storage", plenty of room there without having to move stuff to USB or Ext. I pretty much just use my ext card for media and pictures.
For some reason this caused issues with my Market connecting to the internet, any idea why? Anyone else experience issues with this modification?
Hmm, no no one has mentioned that problem, and I have been using this for months - no problem. Sorry if it did that, have you tried restoring the original? Also, an update to the instructions is to change the permissions to rw-r-r. I didn't notice anything wrong without changing the permissions, but you never know.
jimcpl said:
Hi,
There's still a bit of confusion with respect to terminology, I think (including myself).
I *think* that when the SGP5 displays "internal sd card", it's only part of the "internal 8GB memory". That "internal 8GB memory" is probably, I guess, something like an SDCARD or flash memory module that's soldered to the mainboard, and with Android, I think that it's split into a couple of areas.
Here's my "guess" of how things are arranged, using the terminology from Settings==>SD card and device storage:
"System storage": Part of the 8gb internal memory, e.g., includes /system, etc.
[1.65GB, in my SGP5]
"USB Storage" = "internal sd card" = /sdcard: The rest of the 8gb internal memory.
[5.01GB, in my SGP5]
"SD Card": The external microSD card, if you have one plugged in. Appears at /sdcard/external_sd.
[29.81GB, in my SGP5, where I have a 32GB microSD card plugged in.]
That System storage + USB Storage totals 1.65+5.01 GB, or 6.66GB. I guess the remainder of the 8GB is for bootloader, etc.?
Jim
Click to expand...
Click to collapse
Pretty close.
https://github.com/Entropy512/initramfs_yp-g70/blob/master/misc/recovery.fstab is the Player 5.0 partition table.
As you can see, nearly everything is on partitions of mmcblk0 - on the Player 5.0, this is eMMC (embedded MMC) storage. The total size of mmcblk0 is 8GB
The partitions here include (but are not limited to):
p10 - EFS - this contains device-specific config data, on phones that includes IMEI, on our device it's probably Bluetooth and WiFi MAC addresses
p11 - Kernel
p12 - Recovery (on some devices, recovery is a separate kernel partition - Samsungs have this partition set aside even though most of their devices don't actually use it. You can put anything you want on p12 and it won't do anything usually. For us, recovery is part of the kernel initramfs on p11)
p13 - /system - This is where the system firmware, often called the "ROM" sits. A number of people are trying to fight the "ROM" terminology, since it's not really true - flash isn't read-only, thus it isn't the "ROM" any more
p14 - In the linked file it's /datadata, but the device actually mounts it as /dbdata - various SQL databases for apps live here
p15 - /cache - a cache partition separate from data. Files stored here are intended to be safely wipable/deletable
p16 - /data - Various user data. Your apps live here unless you've moved them to SD. Most system settings are here too. ICS merges this partition with the internal SD so they are one and the same
p17 - /emmc in recovery and, if someone ever has the time to port it, CM7, /sdcard in Samsung factory firmwares. This is the "internal SD card".
There are a few other partitions that are not touched by recovery that exist, such as the LFS partition and the bootloader partitions. These are all small.
mmcblk1 is the external SD. Usually only one partition, which is /sdcard in recovery/CM7 and /sdcard/external_sd in Samsung factory firmwares
On the 4.0, I believe it uses Samsung's older NAND flash technology and not eMMC, so the partitions on internal storage appear as stlN/bmlN
i think i did something disaster...
i am using Samsung Galaxy W. I did follow your above instruction. The problem is after restarting my phone, I go to setting>storage and it shows total space and available space for SD card and USB storage is UNAVAILABLE. What is available is only Device Memorry which is 1.03GB.
Thinking that your vold.fstab is not compatible with my Samsung Galaxy W, I replace it with the original vold.fstab that I backed up earlier. However this does not solve the problem.
Then what I did is I tried to reset the phone to its original factory setting (Setting>Privacy>Factory Data Reset..),. Unfortunately the same problem still persist. And i think this is silly and catastrophic step since i loss my original vold.fstab which is stored in the internal memory.
Any of you can help me?
Many thanks to all of you
Well, did you change the permissions on your backup back to rw-r--r--? And yes, this mod should only be used for the device intended for. Are you sure that you replaced the modified vold.fstab with the original one? Did it give you an warning about overriding (it should have)? Are you sure you used your backup and not accidentally mine? What program did you use to copy?
Hmm stupid question, but how do you replace the existing file? I am using root explorer an it says it is read-only when I try to paste it in there.
Edit... Never mind... I didn't have it mounted correctly.
I have tried this multiple times, but every time I reboot it says "USB storage damaged, may need reformatting." So I press reformat, and it's done in like 1 sec and the problem still persists.
Any ideas?
Hmm, odd. I know you have the same version player as me, are you running 2.3.5 or 2.3.6, maybe that could affect it? Did you try before you did a lot of modifications to your device? What type of SD card you got, I use a 32gb class sandisk. I don't think that would matter, but you never know. I recall getting that error when I was working on the mod, but I got it fixed before I released it. Weird.
Oh yeah, what do you have your sd card formatted as? I use FAT32, not sure if that could affect it. May want to try reformatting the card on a PC, then try.
I have a 8gb kingston micro sd card, and I'm running 2.3.5. I had this problem a long time ago too when I was still on stock. Maybe it's my sd card. I will reformat it and try again, and if it doesn't work I will try a different sd card.
Hi guys, I've been a little concern about my files on my memory card, so I moved them to the internal storage for "safety" my files are blocked by a security pattern, but if you take the memory card out people would be able to see whats in it, thats why I decided to move it to internal memory. But I found out that, even if I have a security pattern, people still can access to both, internal and external memory by using usb cable to connect the phone to the computer!! So, how do I block my internal and external memory from being accessed in the event that my phone get lost or stolen??
One possible option is to use anti thief programs like cerebrus. It allows you wipe the data from the phone by remotely sending SMS codes. Maybe encryption is also the way to go for you. But I am sure about that.
haulero said:
Hi guys, I've been a little concern about my files on my memory card, so I moved them to the internal storage for "safety" my files are blocked by a security pattern, but if you take the memory card out people would be able to see whats in it, thats why I decided to move it to internal memory. But I found out that, even if I have a security pattern, people still can access to both, internal and external memory by using usb cable to connect the phone to the computer!! So, how do I block my internal and external memory from being accessed in the event that my phone get lost or stolen??
Click to expand...
Click to collapse
Encrypt it. System settings/Encrypt device. You can, apparently, do both internal memory and SD card.
poldie said:
Encrypt it. System settings/Encrypt device. You can, apparently, do both internal memory and SD card.
Click to expand...
Click to collapse
I wanted to try that... however, it says password will required to decrypt each time you power it on..... so thats why I didn't do it. Cause of course, if I lost or someone steal my phone, phone is going to be ON, so that makes no sense because they will have access to my files anyways, since I already provided the password to decrypt it, right?
anubius said:
One possible option is to use anti thief programs like cerebrus. It allows you wipe the data from the phone by remotely sending SMS codes. Maybe encryption is also the way to go for you. But I am sure about that.
Click to expand...
Click to collapse
Thats a good idea, however. If I lose my phone at walmart, it will take a little while before I can get in a computer to wipe my data off! by then, people will have accessed my info already. It make take 30 minutes before I realize my phone was lost, then I need to get home and log in to cerebrus.com (or whatever its spelled lol) and wipe data from my device. What I would like to find is something that will block my data from being read if the phone is connected to computer via usb cable.
Like I said before, I already have pattern block, they will not be able to access my internal memory without the correct pattern, they can take the sd card and see my files in another device, but I'm not worried about that because I already moved all the important files to the internal memory of the phone.
I too want an answer
Yes off course, someone can just take my phone and can easily copy my internal data. We need a solution for that.
This has been talked about over and over I believe, but a real "solution" has not been found yet I guess. I just want to direct you to another thread with my take on this issue.
Hey there,
I was reading about encrypting my SD card via settings > storage, but am turned off by the thought that flashing a rom or doing a factory reset will render the sd card useless because the encryption key would be bad. What is the best alternative for securing the SD card say, if the device was stolen? Can this be avoided by "keeping the previous Android device ID" in titanium backup when prompted?
As for the device itself, I am putting some trust into the Android Device Manager, which finds the phone much like Apple's 'Find my iPhone' via the google dashboard, but worry about the feature working when the time comes (if ever!)
Ammi doing it rite? What are some security advices you can give an android user, or perhaps a worthy article on the topic?
EDIT: After looking into the security > storage screen for my phone(HTC One M8), the process only encrypts new files, not currently existing files- which seems to be ineffective and a pain for encrypting all files. I am assuming files transferred to the SD card via USB connection on a PC is never encrypted? Only files loaded onto the SD card through the OS?
Hi to all
after going thru all relevant pages about this I could not find solution.
I wish to password protect sd card in my phone. I have Sony Xperia neo with latest official rom and option for sd card encryption is missing. Now I know that there are programs to encrypt specific folders but that to my knowledge is not transparent to system and requires me to decrypt each file before use. I had older phones (nokia and palm) that could set sd card password and remember it but sd card was useless on other device, or if original device was reseted to factory defaults.
Any idea on how to address this problem? I find it interesting that this simple option is missing from such advanced os as android is.
I know using a thread it not necessarily the best way to ask a question but since the cause of this issue is unknown (and might just be SD corruption) and there are a few other threads where it might come up, this thread can be used as a reference.
The issue is: An SD card that rather suddenly became unwritable in every way and can no longer be mounted by Android (although it is detected) but on which all existing data was undamaged, can be viewed and copied via USB card reader to Windows or Linux PC. The drive behaves much as if it was write protected or as if the file system (particularly the FAT) was corrupted in a way that mimics digital SD write protection. Here are the details.
L5.1.1/CM12.1 December 2015, SuperSU 2.65, TWRP3.0.2,
- 64GB Sandisk Ultra SD, initially accepted as formatted or formatted upon first use to Fat32; Working fine for a few months as repository for static data (ROM zips and app apks), work material (frequently edited text, DOCX and XLSX files), as well as apps and app data with a dynamic presence on the drive.
- Drive suddenly stopped appearing on device in CM and in TWRP. When re-inserted in CM, the system detects a card but times out as it is unable to find a mount point. Attempts to mount SD card in ROM result in the following error in CatLog:
"E/Vold (222): /dev/block/vold/179:65 failed to mount via VFAT (No such device or address)
E/Vold (222): Volume sdcard1 found no suitable devices for mounting "
- Attempts to repair, partition or format the drive in TWRP result in mount error and the details of the drive have zeros where there should probably be other values.
/external_sd | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: MicroSD Card
Storage_Name: MicroSD Card
Backup_Path: /external_sd
Backup_Name: external_sd
Backup_Display_Name: MicroSD Card
Storage_Path: /external_sd
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
MTP_Storage_ID: 65537
- With SD in card reader attached to PC, the contents of SD are visible and can be copied to PC but files cannot be copied from PC to SD card. It looks like they are copied but they are gone when card reader is disconnected then reconnected. Same in Linux Ubuntu 14.x.
- Unable to delete or reformat partitions in any utility that I tested including: Dedicated GParted boot USB, EaseUS Partition Master, HP USB Disk Storage Format Tool on PC, GParted in Ubuntu 14 VM, GParted in Ubuntu 10.x live CD/USB.
- Although the SD drive shows as Fat32 in GParted, Windows 7 only offers exFat and NTFS as formatting options. Some research shows exFat can digitally "write protect" drives with a dirty bit or byte which causes very similar symptoms.
- Windows Chkdsk requests to convert lost chains to files but must not be doing so as this occurs on every scan.
Soooo...the questions are: What in the realm of relatively normal android use might cause this? Has anyone heard of a disk or partition management setting or common form of drive corruption that could cause this? Could such a thing be caused by a file manager? A 32GB replacement SD is doing OK but I'm left wondering if the issue with the 64GB SD card was caused by a utility on the device or if it was just SD corruption (that looks conspicuously like digital write protection).
[EDIT] A minor correction I should make: The reason Windows 7 only offers NTFS and exFAT is not because the drive is damaged (although it may be) but rather because Windows 7 cannot format USB drives over 32GB with FAT32 although it can mount and use larger FAT32 SD drives that were formatted elsewhere. In this case I let android do the initial format months ago (Fat32) and never had problems during the times I connected it to card reader (although I usually leave it in the device and use Wifi or MTP through device USB to PC).
[] AL [] said:
Since your running 12.1, I imagine that you don't flash too many nightly build's... So this (not) variable is may be put aside from suspects list.
Click to expand...
Click to collapse
Correctamundo
[] AL [] said:
Recovery: well, I don't know but for that, I'm always following the if it ain't broke, don't fix it rule. You have specific reasons to keep it updated? Like you, I've also read many posts reporting USB related issues with v > 3.0. I still use v2.8.7.0 on my device and don't feel the need to update soon.
Click to expand...
Click to collapse
I'm now on the fence about reverting to the longer standing 2.8.7 version of TWRP, but since the primary maintainer for my Otus CM12.1 and CM13 ROMS (@squid2) also creates the build of TWRP and has included in his 3.0.2 version some forward fixes that might be better for CM13 especially where encryption is used, I have been updating it. A consideration in this regard is; what if it was not the different version of TWRP that caused this but rather a one-time instance of something that went wrong in the act of flashing it - which I would be more at risk of because I do occasionally update TWRP.
Hmmmm...I did recently restore a nandroid of stock Moto L 5.0.2 then flashed stock recovery in an attempt to install a pending L5.1 OTA (Moto finally released it!) which failed AFAIK due to unlocked bootloader, then I flashed TWRP 3.0.2 and restored a CM12.1 nandroid. If that was a factor it merely planted the seed of the problem but did not grow into the problem until some other later action .
[] AL [] said:
As for apps, what I find strange is that even a format didn't fix things up with it.
Click to expand...
Click to collapse
The drive became un-writable in every way including the ability to format or change any properties of the drive in any drive/partition manager even though the data was all there in perfect shape. Ironically the problem with the drive is now protecting the data
[] AL [] said:
...I would hope to believe that a file explorer alone can not mess it up THAT much alone...
Click to expand...
Click to collapse
Likewise but at this point it would not surprise me considering that Android is a bit fast and loose with more basal aspects of the system including drive management.
Ultramanoid said:
I've used extensively SanDisk 64 GB microsdxc cards with Android. Given all the information you've given, I'd lean towards physical card failure.
It happens. In my experience, very rarely, but it does.
If the same thing happens again to another of your cards anytime soon, that's when you should start a serious investigation about it.
To be honest I've had more smartphones failing on me for a myriad different reasons in the last few years than problems with a card from a reliable manufacturer.
I have washed some of these cards in the washing machine by mistake, and I've used some intensively non-stop every single day for two or three years without an issue. I've run OSes from them often, and always replaced them for another because of speed or space concerns, very rarely because of failure.
They are incredibly resilient. And yet sometimes ( again, rarely ) one will spit input / output errors, or simply die on me, no matter what the format, filesystem, or OS. In fact it happened once with a brand new card that I had just used for a couple of weeks, the irony...
Click to expand...
Click to collapse
Good points. Thanks! I've had similar experiences with Micro SDs surviving through accidental washings as well as heavy use as USB boot drives running various utilities or Linux distributions (one of which had a persistent cache cache right on the card - thats a lot of read/writes) and I can't remember encountering a corrupted SD card that was not physically damaged.
That being said I did once support an outdoor system of over 300 units each of which ran off of a proprietary Linux system on an 8GB SD card where SD card corruption was not uncommon but those "devices" were exposed to thermal extremes, traffic vibrations, and poor quality field work and remote management the likes of which our devices rarely experience.
At first I was leaning toward SD card corruption but now wonder if this was an accidental digital write-protect, perhaps caused by an extremely localized bit of SD card corruption... or something like that... and that is an area where android is faster and looser than many other device/OS combinations.
What is the result of fsck with Linux ?
Ultramanoid said:
What is the result of fsck with Linux ?
Click to expand...
Click to collapse
Similar to Windows chkdsk; In Ubuntu 14.x Live USB boot, fsck (supposedly) reclaims lost clusters, and reports "free cluster summary wrong...". When option to fix is selected the command cannot gain write access to the drive. Re-scan verifies same errors persist.
Here's an idea that worked for me once with a card that refused to be formatted on Linux and OS X; try with a digital camera or DSLR, you may need a micro to SD adapter.
In that case though, mine was a defective card indeed. The camera did format it, and was usable for a little while, before giving errors again, and I discarded it definitely.
Edit : to be precise, the camera did not recognize it and offered to format it ( to FAT being an old DSLR, but a new camera might go for exFAT, and you already suspect foul play because of exFAT ), which worked, and then I could format it again ( ext4 ) in Linux. As mentioned, the card failed again soon afterwards anyway.
Ultramanoid said:
Here's an idea that worked for me once with a card that refused to be formatted on Linux and OS X; try with a digital camera or DSLR, you may need a micro to SD adapter.
In that case though, mine was a defective card indeed. The camera did format it, and was usable for a little while, before giving errors again, and I discarded it definitely.
Edit : to be precise, the camera did not recognize it and offered to format it ( to FAT being an old DSLR, but a new camera might go for exFAT, and you already suspect foul play because of exFAT ), which worked, and then I could format it again ( ext4 ) in Linux. As mentioned, the card failed again soon afterwards anyway.
Click to expand...
Click to collapse
I tried that yesterday in a relatively new camera that is supposedly capable of handling 64GB SDXC but the camera reports that the card could not be used but offered not other information.
As to exFAT - this correction to my initial assessment of the situation: The reason Windows 7 only offers NTFS and exFAT as formatting options is not necessarily because the drive is damaged or had a read only flag applied (although both off those thing now seem likely*) but rather because Windows 7 cannot format USB drives over 32GB as FAT32 even though it can mount and use them if they were formatted elsewhere. This does not really change things other than meaning that the available Windows formatting options are not informative.
* I just called SanDisk support and learned that the card supposedly has some sort of data preservation feature where; when an imminent potential failure is detected the card is indeed digitally write protected. This might mean that there is a way to undo the digital protection although that would put the data risk and the protection is non-standard as the Windows Diskpart command line utility does not show the disk or the volume as write protected.SanDisk even offered to replace the card but I declined (for now) because I want to hack at it some more. At least there now seems to be an understandable mechanism for how this happened.
Thanks for throwing some thought into it
It's interesting, the card I mentioned was a 64GB one, but the camera formatted it to FAT creating a 32GB partition, same limit as Windows. It pretty much ignored the other half of the card that showed up just as free space, but it also undid whatever was blocking the formatting before, which may have been that protection scheme from SanDisk as in your case. Good to learn about that.
Interesting...
I have the same issue with my Samsung 64gb sd. I was moving a zip file from internal sd to external sd with ES File Explorer and all of a sudden my phone froze and I had to hard reset. When I rebooted external was screwed. I have been looking for days for a fix and have come up with nothing. TWRP can see the card but no values. Please any help would be very much appreciated because I have ALL the pictures of my 2 week old son stored in ext sd.
noob4598 said:
I have the same issue with my Samsung 64gb sd. I was moving a zip file from internal sd to external sd with ES File Explorer and all of a sudden my phone froze and I had to hard reset. When I rebooted external was screwed. I have been looking for days for a fix and have come up with nothing. TWRP can see the card but no values. Please any help would be very much appreciated because I have ALL the pictures of my 2 week old son stored in ext sd.
Click to expand...
Click to collapse
See if this helps. Read through it, it has allot of helpful information.
http://forum.xda-developers.com/showthread.php?t=1192508
noob4598 said:
I have the same issue with my Samsung 64gb sd. I was moving a zip file from internal sd to external sd with ES File Explorer and all of a sudden my phone froze and I had to hard reset. When I rebooted external was screwed. I have been looking for days for a fix and have come up with nothing. TWRP can see the card but no values. Please any help would be very much appreciated because I have ALL the pictures of my 2 week old son stored in ext sd.
Click to expand...
Click to collapse
The incident about which I created this thread was sudden as yours was. Try viewing the contents of the SD card in a card-reader on a computer. If you can see the contents and copy to the computer but cannot write to the SD card you may be experiencing the same issue describe in the OP of this thread (irreversible dirty bit write protection due to impending failure detected), in which case you would have to backup the data on the card and get a new one. Also, it is best to keep internal/adoptable storage completely out of this equation as that re-formats and encrypts the SD card.
@MatisyahuSerious
Since this was a bit OT for LOS I've expanded upon this post (https://forum.xda-developers.com/showpost.php?p=71903594&postcount=4155) here where the reply is less off topic.
Off course there are many other bad things that can happen to SD cards, and frequent ROM flashing and TiBU backups put a particular stress on them. Another factor, at least in my case, is that when a high speed SD card (eg Sandisk Ultra red/grey) is used in a USB 3 port (to move data much quicker than MTP) the SD card gets so hot that the painted logo scorches and changes color. Those thermal cycles cant be good for the cards either. I've had 3 go bad in about 6 years, one in the manner described in linked post.
A bit of somewhat related OT: For what this is worth I once supported a system which ran Linux based OS from 8GB SD cards and the most frequent fix was to replace corrupted SD cards. SD cards have gotten better, and some brands may be better than others, but they were not originally designed to handle so much fast R/W and IMO the SD industry is still catching up.