i was on twrp 2.8.7.0 and installed http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-kushan-cm-marshmallow-rom-t3258489. then formatted my sd card as internal storage. today i wanted to update to the latest build of kushan rom, but in twrp my sd card was listed as 0 mb and i couldnt enter it. so i decided to flash latest cwm trough rom manager. after flashing cwm my internal sdcard was wiped(not by me-automaticly) and now marshmellow tells me that te sd card is not supportet...please format.....
i think that as the cwm wiped my sd card "the unique? encrpytion key?" got lost and therefor i cant axcess the sd card. im i right?
if yes i hope the encryption key is not unique and i can recover the files on the sd card
k2828 said:
i was on twrp 2.8.7.0 and installed http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-kushan-cm-marshmallow-rom-t3258489. then formatted my sd card as internal storage. today i wanted to update to the latest build of kushan rom, but in twrp my sd card was listed as 0 mb and i couldnt enter it. so i decided to flash latest cwm trough rom manager. after flashing cwm my internal sdcard was wiped(not by me-automaticly) and now marshmellow tells me that te sd card is not supportet...please format.....
i think that as the cwm wiped my sd card "the unique? encrpytion key?" got lost and therefor i cant axcess the sd card. im i right?
if yes i hope the encryption key is not unique and i can recover the files on the sd card
Click to expand...
Click to collapse
As stated many many times. The only recovery you can use is TWRP. Your sdcard shows 0 mb because it became part of your internal storage. So reflash TWRP and try again.
after flashing cwm i did nothing but booting once the rom and notice that everything was wipped and then flash twrp.
the result is i cant axcess my sdcard as the rom sais that the sdcard needs to prepared.
so my question is, can i recover the data on the sd card?
Not if you're at the point where the card needs to be prepared. What you should have done if you wanted to decrypt the MicroSD, is pulled the data off both card and internal storage, then gone into Settings > Storage & USB and converted the card to portable storage.
One thing. With CWM running, did you have any nandroid backups? If you did, you likely will have to reinstall CWM to free up the internal storage reserved for the nandroid backups. CWM by default allocates space for its nandroid backups that cannot be touched by the system or TWRP. Once you do that, you can then reinstall TWRP.
OK THX. I just created a image of the SD card.maybe in the future there will be a toop to decrypt such SD cards. For the future:
Is the SD card lost everytime i update the Rom build?
Is the SD card lost Ehen i change the Rom to another Android 6 Rom?
What do i have to do when updating to a Newer build oft the same rom,vor change to another Android 6 rom? Pull everything from bouth cards? Really? Thats a pain in the ass even with a uhs 1 SD card.
Whats the best way for backing up the data, so i can cop them back without trouble? Maybe ADB?
Whats about changin the recovery? Thats a nogo i think and whats about updating twrp?
What is a absolut nogo? What i ahouldnt do to f*** up the card again?
So many questions, but I'm going to answer just the last two, as their answer covers every other question in your post.
What is an absolute no go? What shouldn't I do to f*** up the card again?
Click to expand...
Click to collapse
The answer to this is so easy it's astounding. The answer is to not combine the card with the internal storage. Here's why. If you switch ROMs regularly in order to try them out, every single time you combine the storage the card has to be prepared for use, which means all data on it gets wiped. If you do a clean install of your current ROM and combine the storage, all data on the card is wiped. The reason the card gets wiped is because Android 6.x creates a virtual volume which spans both internal storage and the MicroSD. In order to ensure the data is secure Android encrypts the volume. This encryption is part of the reason Google throws up a warning to restore the card if you pull it out of the device.
By not combining the storage, you avoid the encryption problems, but you do have to deal with the issue of apps not seeing the MicroSD card. Unless an app with this issue is no longer being updated, this problem will resolve itself. Developers have to adapt to the new setup.
The encryption also impacts performance, though on my tests with it I didn't notice anything. The one thing it will do is impact the ability to perform backups. In my tests, the encryption prevented TWRP from doing anything useful, meaning no ability to install flashable zips or updated TWRP recovery images from the storage and no ability to do nandroid backups. TWRP could see the directory structure of the combined storage but could not see any files within the folders to install. Nandroid backups instantly failed with an "out of storage" error, even though I had some 15GB of space available on the MicroSD. TWRP's developers will need to adapt to this and custom ROM developers will have to recommend that users not combine storage.
Strephon Alkhalikoi said:
So many questions, but I'm going to answer just the last two, as their answer covers every other question in your post.
The answer to this is so easy it's astounding. The answer is to not combine the card with the internal storage. Here's why. If you switch ROMs regularly in order to try them out, every single time you combine the storage the card has to be prepared for use, which means all data on it gets wiped. If you do a clean install of your current ROM and combine the storage, all data on the card is wiped. The reason the card gets wiped is because Android 6.x creates a virtual volume which spans both internal storage and the MicroSD. In order to ensure the data is secure Android encrypts the volume. This encryption is part of the reason Google throws up a warning to restore the card if you pull it out of the device.
By not combining the storage, you avoid the encryption problems, but you do have to deal with the issue of apps not seeing the MicroSD card. Unless an app with this issue is no longer being updated, this problem will resolve itself. Developers have to adapt to the new setup.
The encryption also impacts performance, though on my tests with it I didn't notice anything. The one thing it will do is impact the ability to perform backups. In my tests, the encryption prevented TWRP from doing anything useful, meaning no ability to install flashable zips or updated TWRP recovery images from the storage and no ability to do nandroid backups. TWRP could see the directory structure of the combined storage but could not see any files within the folders to install. Nandroid backups instantly failed with an "out of storage" error, even though I had some 15GB of space available on the MicroSD. TWRP's developers will need to adapt to this and custom ROM developers will have to recommend that users not combine storage.
Click to expand...
Click to collapse
thx for your very detailed answere. but whats about when i am using i.e. kushan rom build 07.12.2015 and i update to kushan rom build 11.12.2015. will the sd card have to be prepared to use also? and what about when i update twrp to a marshmellow support twrp. di i need prepare the sd card then again?
TWRP could see the directory structure of the combined storage but could not see any files within the folders to install. Nandroid backups instantly failed with an "out of storage" error, even though I had some 15GB of space available on the MicroSD.
Click to expand...
Click to collapse
This is the point where my trouble began. as so as the sd card is prepared as internal you cant even see files of the real internal storage. flashing zips you can still do with adb sideload. another question could we backup the internal flash inlcuding prepared sd card with this:
http://forum.xda-developers.com/showthread.php?t=1818321
?
If yes, is there also a way to restore the backup made?
To make things crystal clear, once the card is set for portable storage you will not have to reconfigure the card again unless you choose to combine the storage. Upgrading a ROM to a newer version will generate a message in the notification bar that you have to prepare the card, but you simply select the portable storage option and the notification goes away. Upgrading TWRP doesn't require doing anything to storage.
Should you choose to combine storage, upgrading a ROM may cost you whatever is on both the internal storage and microSD. Upgrading TWRP with combined storage would require you to flash it using Odin, because you wouldn't be able to copy the TWRP image to the device storage.
Backing up the internal storage doesn't require anything more than a copy operation from the S4 to the PC, so no special tools should be required. That applies regardless of whether the storage is combined or separate. However, for best results with TWRP, the storage should not be combined.
Sorry for reviving this old thread, but I've the same issue.
I flashed a new rom without getting the decryption code or backing anything up(No NANDs, no sd backup). Is there still currently no way to retrieve the files that are encrypted on this SD?
I've done exactly the same, I'm hoping theres a way to decrypt it.
k2828 said:
i was on twrp 2.8.7.0 and installed http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-kushan-cm-marshmallow-rom-t3258489. then formatted my sd card as internal storage. today i wanted to update to the latest build of kushan rom, but in twrp my sd card was listed as 0 mb and i couldnt enter it. so i decided to flash latest cwm trough rom manager. after flashing cwm my internal sdcard was wiped(not by me-automaticly) and now marshmellow tells me that te sd card is not supportet...please format.....
i think that as the cwm wiped my sd card "the unique? encrpytion key?" got lost and therefor i cant axcess the sd card. im i right?
if yes i hope the encryption key is not unique and i can recover the files on the sd card
Click to expand...
Click to collapse
Have you found solution to decrypt the Sdcard.
I was facing this problem for almost 1 year I need only sdcard not data in it but I am unable to format it due to encryption but any device able to read the data and copy from that.
Even I can play Music out that SD card
Unless you're immortal, you're not decrypting the MicroSD card via brute force. Currently, the amount of time required to find the decryption key is longer than the current age of the universe.
If looking to simply format an existing card, use SDFormatter from http://www.sdcard.org.
Well I did not think this through lol
I had Adopted Storage set up on my 2017 16 Gb Shield and I had to re-flash some partitions, so I used Flashfire to create a backup, and silly me saved it on the external USB drive. Now that I'm done with all the flashing, the shield is back to being set up to use the actual internal storage again, but it can't read the encrypted USB.
Trying to set it up as either portable or internal storage warns that it will be reformatted, so haven't done either, the USB is just as it was before any flashing.
Is there any way for me to get my /data partition back with all the apps/settings i had? I guess either:
1) somehow access the Flashfire backup, then "adb push" it to my laptop, set up adopted storage again and wipe the USB and recover the data partition from the backup?
2) maybe somehow reactivate internal storage to use the /data partition from the usb drive?
Any help would be appreciated, thanks!
(if it makes any difference, I was on full android nougat, flashed nvidia 5.0.1 recovery with flash-all.bat, did the OTA to 5.1, then flashed system/vendor of an updated full android nougat, and rooted it. now im back at full android but blank, hoping i can restore. if not, i guess i'll just have a few hours of reinstalling haha)
The only way to read an encrypted card is with the key. Keys are stored in /data/misc/vold. If you don't have a copy of your key then you're out of luck, sorry.
Yea you're screwed
Dang it. /data/misc/void is empty, the wipe took care of that.
Thanks anyways.
I install a stock 6.0.1 UK(BTU) ROM on a Samsung Galaxy S5 (SM-G900F).
Then I encrypt internal storage (all of it). I don't setup any unlock method.
At this point, the phone can boot by itself, there has to be a "default_password" for dm-crypt master key.
But usually when only the default password is used for encryption and user don't have to type it to boot, TWRP knows it and uses the default password to decrypt and mount the partition.
But I install TWRP and go in recovery and I can not mount /data (invalid argument). I can mount all other partitions.
My question is: is there any other tool to access the encrypted /data? Or if not, is this storage really safe without setting a password you need to enter at boot?
I know encryption without password is not secure on AOSP, but is the Samsung version secure? If so, how did they do it?
Thanks!
Unsubsidized, bootloader unlocked, rooted (supersSU). Phone is brand new and has stock (137-35-5) with Vanche TWRP (3.1.1).
The phone is encrypted (out of the box that way) and TWRP shows 0MB on all storage media.
While I can save to the SD, no app can write to the internal memory. In fact, simply trying to change the global phone ringtone to a different (stock) selection doesn't work.
Any ideas how I can get this to work?
deleted
assuming you're talking about /sdcard what is just a bind mount of /data/media/0 and not related to /external_sd MicroSD card, that indicates your whole phone storage is encrypted.
no-verity-opt-encrypt-6.1.zip does not decrypt phone, it is prerequisite to run phone unencrypted. to remove encryption, formatting userdata is required (aka factory reset)
however the mentioned zip has a bug, it will mix up file-based encryption with full-disk encryption.
Luckily it does not have any effect on read-only vendor partition, as it tries to modify /vendor/etc/fstab.* file.
official TWRP is capable of decrypting userdata partition (except for stock samsung encryption), it will ask for lock screen pin. if it's a pattern you can translate into password (not sure TWRP provides pattern screen, though)
https://twrp.me/faq/openrecoveryscript.html
if you're talking about encrypted MicroSD Card that is probably Samsungs own encryption feature and can only decrypted within the ROM itself.
https://www.samsung.com/ca/support/mobile-devices/galaxy-phone-use-a-microsd-card
deleted