I was reading a thread earlier and some1 mentioned that they had to recover their tgablet from a boot loop by using the ODIN files, i had to do the same after updating to 3.1. They also mentioned that their storage space only showed 13gbs total, instead of 32. I have the same problem, after using odin to fix my tab, i now have only 27gbs total, of which 23 are free. Is there any way to fix this problem anyone knows about?
thanks!
Not sure, but if you are seeing 27GB on a 32GB tablet, that might be normal. You'll never see a full 32GB because of formatting and I believe there are separate partitions for boot and the OS that use up some space too.
while attempting to get the youtube apk on cyanogenmod i noticed that the internal memory on my tab 2 is slightly lacking in the 16gb i was promised when bought i have attached a picture of said tab on the storage page tell me what if anything can be done to correct this or if i should have gotten a memory card or something as im totally lost https://www.dropbox.com/s/eg492s4q5wkjr5n/Screenshot_2012-06-24-17-35-58.png
try to wipe DATA/ Factory setting at CWM
still the total space of 1.97 GB none lost none gained
nvm dont need help figured it out on my own if you loose space just do a hard factory reset from inside whatever version of the os your using and it should come back
I seem to have lost some of the little 16gb's I had. seems like after pressing security mode I am only showing 10.3GM of internal memory. Anyone know what up with this? I have tried searching the forum, but getting error msg's trying to find the answer....
I do have on safestrap, but think this happened befor i installed it. not 100% sure.
10.3GM or 10.3GB? And that seems normal you don't get to use ALL 16GB. The "lost" space is reserved for system
are you referring to "private mode" with the security mode you are talking about? yeah it seems to format a little over 4GB for the "private" encrypted folder, I recently rooted and installed cyanogen and now I seem to have lost that 4GB completely it only shows 11.3gb of total internal memory. If you turn private mode on and plug into a computer does it show 4GB approximately for private and the other 11.x for internal storage? trying to find out if I wipe everything in twrp if I'll brick my phone or be able to reformat internal storage to one partition and have all 16 back minus the little bit that gets eaten up but should still be 14.5 15gb of total storage space granted it wont all be available.
So recently my device stopped recognizing the SanDisk 64gb micro-SDXC I had formatted as internal storage. As far as I am aware when you format a SD this way the phone turns it into an encrypted volume and stores the key on internal storage, presumably somewhere the user cannot normally access it. The card itself is not dead, plugging it into my computer verifies this, but I cannot access it. I think some write operation failed and made it invisible to the phone. the phone did the same thing to a 128gb PNY card, but I reformatted it on PC, then reformatted it again on the phone and now the PNY is working fine. my question is, is there any way to extract the encryption key for my 64gb card(Root based tool or otherwise) from the card profile on my phone and decrypt it on a PC so I can reclaim my data? The phone still has a profile for the card, so presumably the key is still in internal storage somewhere. I had about 40gb of media on that card that I had not backed up (photos, videos, music and such). My ohone is not currently rooted but i wouldnt mind rooting it if someone has a root only solution.
I would wipe cache, then data then try another ROM.
sciencetor2 said:
So recently my device stopped recognizing the SanDisk 64gb micro-SDXC I had formatted as internal storage.
Click to expand...
Click to collapse
It is possible, though I have not done it before, I avoid adoptable storage for this reason. Do NOT wipe your ROM, or you will permanently lose your encryption key to your data that you have on the card.
If you put the SD card into a Linux PC that can recognize the partitions (Windows will not show it), you will see two partitions, android_meta and android_expand. To decrypt the big one, android_expand, you will need to recover your key from the phone.
To recover the encryption key, you will need either root access or a custom recovery like TWRP, to access '/data/misc/vold' to retrieve the encryption key (aes-cbc-essiv:sha256). Save the .key file to somewhere safe.
Then something like
dmsetup create crypt1 --table "0 `blockdev --getsize /dev/sdb2` crypt \
aes-cbc-essiv:sha256 00010203040506070809010a0b0c0d0e0f 0 /dev/sdb2 0"
mount -t ext4 /dev/mapper/crypt1 /mnt/1/
More info here - http://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
Once you have recovered your data, reformat the card and use it as portable storage
SenK9 said:
More info here -nelenkovDOTblogspotDOTcom/2015/06/decrypting-android-m-adopted-storageDOThtml
Once you have recovered your data, reformat the card and use it as portable storage
Click to expand...
Click to collapse
(url edited due to new user restrictions)
Thank you! this is exactly what I was looking for, but i couldn't find anything on google about anyone figuring out all the details (encryption key location, encryption method, usable tool for decryption)
now is there any way i can root, extract the key, then unroot so that i can RMA the phone? It seems to now render any sd i put into it unreadable by itself within about 5 minutes of formatting, regardless whether i format as internal or portable. not sure if this is hardware (reader malfunction) or some software is writing to the card incorrectly, but it is now doing it consistently.
sciencetor2 said:
(url edited due to new user restrictions)
Thank you! this is exactly what I was looking for, but i couldn't find anything on google about anyone figuring out all the details (encryption key location, encryption method, usable tool for decryption)
now is there any way i can root, extract the key, then unroot so that i can RMA the phone? It seems to now render any sd i put into it unreadable by itself within about 5 minutes of formatting, regardless whether i format as internal or portable. not sure if this is hardware (reader malfunction) or some software is writing to the card incorrectly, but it is now doing it consistently.
Click to expand...
Click to collapse
I do not believe it's possible to root or change the recovery without unlocking the bootloader, unless there's some other method I'm not aware of. Even MM systemless root method - http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380, requires unlocking the bootloader, which of course then technically voids the warranty.
However, in this case, it might be worth contacting Moto to inform them of what's happened, it's definitely some kind of bug in the software which has caused this, and thus you are stuck in this catch-22 situation. They might make an exception or have some other solution. Let us know how you go.
SenK9 said:
... requires unlocking the bootloader, which of course then technically voids the warranty. ...and thus you are stuck in this catch-22 situation.
Click to expand...
Click to collapse
Even more of a catch 22 situation, because if i read that correctly, the process for unlocking the bootloader also requires wiping the phone (and thus, the encryption keys) (i miss geohot with his 1 click soft roots). I will wait a little while and see if I or anyone else reading this thread can find a way around that, but it seems ill have to contact Moto support either way, since my 16gb model is barely usable without an SD card.
This is another example of why taking control of your phone before something goes wrong is so important.
Did you try wiping cache yet?
lafester said:
This is another example of why taking control of your phone before something goes wrong is so important.
Did you try wiping cache yet?
Click to expand...
Click to collapse
I checked the recovery menu but there didn't seem to be an option for wiping cache on this device (recovery menu was a little different than I am used to, only had option for factory reset) Also, while wiping cache might conceivably prevent it from screwing up future cards, I don't know if it will fix this one, and i'm not sure if i wanna risk wiping anything without getting my hands on the encryption keys first. if it becomes apparent that i'm just not getting root without wiping, then I'll try playing around with recovery options to at least get back SD slot usage.
You can erase cache in fastboot. If you are locked there is no way to root without wiping data.
lafester said:
You can erase cache in fastboot. If you are locked there is no way to root without wiping data.
Click to expand...
Click to collapse
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
YITBOS said:
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
Click to expand...
Click to collapse
I hadn't heard that... Got a source?
YITBOS said:
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
Click to expand...
Click to collapse
No all that does is allow you to unlock (providing you have a key of course).
well it looks like nobody has found a non wiping solution to root my phone, so I'm going to have to give up on the data and see if I can get back SD functionality, or just RMA the phone. I think i will also publish a script that allows you to plug in your phone and the SD at the same time and allow you to decrypt an internal formatted card by pulling the keys and using them to mount the drive to help people who are in similar situations, but have root. Thanks anyway for the help.
Hi Everyone, I'm stuck in the same catch 22 situation. Device is not rooted or bootloader unlocked, so can't access the key, and trying to root/unlock bootloader will wipe the keys. Any updates, @sciencetor2??
Have you written to Motorola/google about this?
I'm still not ready to give up on the data... hundreds of vacation pictures, that couldn't get backed up.
I'm in the same boat any good news on this?
As long as the phone can see the card, you can change it to portable storage. However, if something goes wrong and phone can not see the card anymore, it's nearly impossible to access the volume without the retrieving the key from the phone, and you must root the phone in order to get the key, as I understand.
I have another similar problem, SD card becomes locked writing and disappears from phone, even I used it as portable storage. And the card can't be formatted at all. So I believe the phone somehow does something and change the state of SD card!
Did anyone find a solution yet. Stuck with same problem. Will loose very important data.
Same here.
I adopted my sdcard as internal storage in CM13.
It was constantly in bootloop, so I formatted the internal memory of the phone to install a new rom ...
But now I can not recover the data within the sd because I can not access it nor with the new rom (I can not even mount it from TWRP) nor from a linux PC (the filesystem is unknown).
Pretty much ... I did not know that the sdcard adopted were encrypted!
Any solution? :\
Hello everybody!
Is there any way to recover the deleted ".key" file?
so i havent gotten back on this thread in a while but i think i at least figured out the "why" on why the card was no longer being recognized. it seems to come down to read/write speed. my 64GB and 128GB cards that i was having the issue with were both U1 cards, which means their read/write is only sitting around 10Mbps, and both of those had issues being detected by the phone after a little bit of time in use. I replaced the card in the same phone a few months back with a high throughput U3 card, and it has been running smoothly ever since. this leads me to the hypothesis that if the card is not fast enough for the phone's taste, it will just ignore it (or timeout on reads, not sure which is actually happening) which is leading to the issues we are experiencing. unfortunately this doesnt lead us to a solution for recovering from the existing cards, but hopefully it will help avoid making the mistake of using a slow card in the future.
I am not the author of this, it is from https://android.stackexchange.com/q/174799/146132 but it has some great info I thought I would share... My thanks to the author.
About a month ago the Moto G (3rdGen) of my wife was not able to recognize the SD-card 32GB Trancend premium 400x (which was formatted as adoptable storage) anymore. On this card were very important pictures and movies for us (of our new born baby). As of a certain Android version the adoptable storage is also encrypted and reading it on a PC or other phone is not possible without the encryption key. Since the phone was also not rooted it was also not possible to get the encryption key from the /data/...something directory... (see https://nelenkov.blogspot.ch/2015/06/decrypting-android-m-adopted-storage.html) So I almost gave up hope...
I bought the exact same type SD-card, also 32GB, only about a year later. Hoping that I would be able to make an exact clone of the card and I would be able to start some experiments with it without the risk of destroying something on the original card and losing all the data. When I mounted the original card under Linux it shows two partitions 17MB and about 31GB. Cloning the card with some Linux command line tools didn't gave me the same result. Next thing I tried was cloning it using HDDrawCopy, first write the entire card to an image on my harddrive. When I copied the data to my new 32GB card I noticed that the new card did not have the same capacity of the image file (image was 32.22GB, new card shows capacity of 31.11GB) so hmmmm that trick doesn't work... Luckily I also happen to have a 64GB SDcard (same type) which should have enough space for this test. So using HDDrawCopy I wrote the image to this card. Checked under Linux if I see the same partition as with the original card and this happens to be (of course it also shows about 32GB of free space not partitioned).
So I thought lets see if the Moto shows the same error with my new card in the phone and that I made an image on which I can start to try to hack the encryption off(now or in the future). To my surprise the Moto shows immediately that the transcend 32GB volume is mounted! I went to the gallery of the phone and IT SHOWS OUR PICTURES AND MOVIES again!!!
So in short when this happens buy a larger volume SD-Card (to make sure that there are enough data-block available). Use HDDrawCopy to make a bit-wise clone/image of the original card. Write the image to your new card and check if it can be read by your phone.
Never do the following or your data will be lost:
Format the cardSet your phone back to factory default (destroys your encryption key)Make the phone to forget/unmount the storage location (also destroys encryption key)upgrade to a newer version of Android (or any other major system update).
(of course make sure to make backups or cloud syncs to prevent this situation at all)
I hope this can help someone out there who might ended up in the same situation.
Unfortunately I have clicked on forget the card. Can anything be done?
Unfortunately I have clicked on forget the card. Can anything be done?
ajparag said:
Unfortunately I have clicked on forget the card. Can anything be done?
Click to expand...
Click to collapse
Unfortunately, no... When you click "Forget" the unlock token is erased and not recoverable by normal means. The daya stored on an internal SD csrd is now lost forever.
Hi, I am in a similar situation. I have a marshmellow phone with an sd card set up as adopted storage, but the phone stopped working and I needed the memory card somewhere else so I took an image backup of the SD card Partition. This is the mistake I did, should have taken the entire disk image backup. So now when I restored the image and the phone is fixed, the phone doesn't recognizes the memory card even though it still has the encryption key.
Any ideas?
The partition table is correct, the first partition "android_meta" probably has the wrong info