Related
Is there a way to recognize the windows like a memeoria internal 16gb usb stick? Why I accidentally formatted everything and so I wanted to retrieve data
Thanks in advance
The information is gone. When you ran the superwipe script it deleted it completely
No, because it is impossible that in less than a minute to be able to perform a full format of the memory and then a possible recovery is still possible
You were given your answer. Stop spamming. No further answers are needed.
is not true because it is impossible to have formatted 16 GB in less than a minute so there was a full format so the data are potentially recoverable
Just Google file recovery. There's plenty if free and paid software that can do this. I doubt there's one for android but if there is Google is your friend.
Oh wait...you meant tthe internal storage...why did you call it a USB stick. Youvd need a more raw access to the data..which I dont think you'd get with the tfs standard USB protocol (mtp?).
There's brute force methods to do this if indeed your data still exist...but if you don't know about them now...you wouldn't be able to do them even if you did.
Perhaps you can extract the data partition of the tf via nvflash..mount it to your computer and try few recovery on that...but that's a bit of a longshot
Just a tip... key to get good answers is asking your questions properly. Your question was very badly laid out.
Sent from my Transformer TF101 using Tapatalk
Thank you for your very thorough answer, I thought I'd try to make sure to connect the memory of 16 GB of disk drives as a tablet with special software so that I can try data recovery, I am sure that it is possible because the formatting I've done has put too little to be complete then can not be recovered
Hi there XDA !
I can`t find an answer for my problem..even google did not helped me!
I bought Nexus 7 32Gb GSM (tilapia) to try out Ubuntu Touch and to play with other OS`s and roms. I flashed the device many times with native roms and with Multirom so the last events are: removed all secondary roms (Plasma active,ubuntu core and ubuntu touch), removed multirom with multirom_uninstaller, upgraded bootloader to 4.23, upgraded radio to 1231_0.18.0_0409, flashed stock Android 4.3 and installed again Multirom (multirom_v12_n7-signed) with kexek kernel, installed Bodhi linux.Then I tried to put back again Ubuntu core and the process was stopped with msg like "there is not enough space".When i check in "Storage" tab in Android the info is Total space 6.02Gb and available 5.81Gb..
Is there any junk left after the old roms and how can I fix this mess?
Please help!!!
I remember I was having a lost memory issue, not nearly as bad as you, but if you have root Explorer or some way to get to /data/media/0/multirom check the ROMS folder and ensure it is empty. If it isn't, then you still have old ROMS there. Not sure if that will help but let me know
Sent from my SCH-I535 using xda app-developers app
bass0324 said:
I remember I was having a lost memory issue, not nearly as bad as you, but if you have root Explorer or some way to get to /data/media/0/multirom check the ROMS folder and ensure it is empty. If it isn't, then you still have old ROMS there. Not sure if that will help but let me know
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I`m sorry but I can`t find /data/media/0/multirom ! The folder /data is empty ! Right now I don`t have multirom installed. I used Root Browser and ES Explorer cause Root Explorer is payed
Is there someone who can help me ?
Blown_ouT said:
I`m sorry but I can`t find /data/media/0/multirom ! The folder /data is empty ! Right now I don`t have multirom installed. I used Root Browser and ES Explorer cause Root Explorer is payed
Click to expand...
Click to collapse
If /data is empty then you have no files on your SD card I'm guessing? If you have files on your SD card then you are looking at the data folder in your SD card and you need to get a root app which allows you to see the data folder on the root of your system
Sent from my SCH-I535 using xda app-developers app
Blown_ouT said:
Hi there XDA !
I can`t find an answer for my problem..even google did not helped me!
I bought Nexus 7 32Gb GSM (tilapia) to try out Ubuntu Touch and to play with other OS`s and roms. I flashed the device many times with native roms and with Multirom so the last events are: removed all secondary roms (Plasma active,ubuntu core and ubuntu touch), removed multirom with multirom_uninstaller, upgraded bootloader to 4.23, upgraded radio to 1231_0.18.0_0409, flashed stock Android 4.3 and installed again Multirom (multirom_v12_n7-signed) with kexek kernel, installed Bodhi linux.Then I tried to put back again Ubuntu core and the process was stopped with msg like "there is not enough space".When i check in "Storage" tab in Android the info is Total space 6.02Gb and available 5.81Gb..
Is there any junk left after the old roms and how can I fix this mess?
Please help!!!
Click to expand...
Click to collapse
I had the same problem and it was caused by nandroid backups, duplicated 0/0/0/0 folders (with allll my files mirrored) and misc junk items in my system. I used disk view app to determine where all my space went and deleted all the appropriate files. This was on my 16gb N7, which lost 12gb once. That's how I was able to recover most of that space. Now, whenever I do nandroids on my 32gb N7, I move them to my computer immediately. I also make sure to clean up with root cleaner every so often, wipe cache and dalvik, etc. Get the disk view app, it will show you where your space has gone. I was able to recover almost all of my lost 12gb on my 16gb N7 by doing this.
http://forum.xda-developers.com/showthread.php?t=2382756
I understand this is an old thread, but I recently had the same thing happen AGAIN on my Nexus 7 32gb. This time I updated from 4.2.2 to 4.4.4. After the flash, I had 6gb of usable space. I reflashed 4.2.2 to no avail, updated my recovery, and checked all my files/folders. I found an interesting, unexpected solution...
I upgraded my bootloader to 4.23, then I re-locked it, and then re-unlocked it. Voila, it was back to my normal space (something like 27gb usable). I read somewhere this worked for someone else, so I tried it, and it worked. Locking & unlocking the bootloader could help others reclaim their missing unused space.
absinthesummer said:
I understand this is an old thread, but I recently had the same thing happen AGAIN on my Nexus 7 32gb. This time I updated from 4.2.2 to 4.4.4. After the flash, I had 6gb of usable space. I reflashed 4.2.2 to no avail, updated my recovery, and checked all my files/folders. I found an interesting, unexpected solution...
I upgraded my bootloader to 4.23, then I re-locked it, and then re-unlocked it. Voila, it was back to my normal space (something like 27gb usable). I read somewhere this worked for someone else, so I tried it, and it worked. Locking & unlocking the bootloader could help others reclaim their missing unused space.
Click to expand...
Click to collapse
An alternative that is much easier if you're familiar with fastboot is:
fastboot format system -w
It completely erases your rom and the entire user data partition. The partitions will have to be reformatted in recovery, but you'll be sure that there aren't any orphaned folders anymore.
brandon_edge1994 said:
An alternative that is much easier if you're familiar with fastboot is:
fastboot format system -w
It completely erases your rom and the entire user data partition. The partitions will have to be reformatted in recovery, but you'll be sure that there aren't any orphaned folders anymore.
Click to expand...
Click to collapse
I'm always happy to learn new methods- the more, the better. Thanks! Also wanted to add, I didn't have to update the bootloader, I just chose to. It would have also worked had I simply locked & unlocked the BL. It was super easy & didn't have to reformat anything. Anyway, I have a list of commands I'm compiling & saving for future use, so I'll add yours to the list.
absinthesummer said:
I understand this is an old thread, but I recently had the same thing happen AGAIN on my Nexus 7 32gb. This time I updated from 4.2.2 to 4.4.4. After the flash, I had 6gb of usable space. I reflashed 4.2.2 to no avail, updated my recovery, and checked all my files/folders. I found an interesting, unexpected solution...
I upgraded my bootloader to 4.23, then I re-locked it, and then re-unlocked it. Voila, it was back to my normal space (something like 27gb usable). I read somewhere this worked for someone else, so I tried it, and it worked. Locking & unlocking the bootloader could help others reclaim their missing unused space.
Click to expand...
Click to collapse
I had the same problem with my 32gb nexus 7 2012. And this method worked. Thanks man.:good:
pol359 said:
I had the same problem with my 32gb nexus 7 2012. And this method worked. Thanks man.:good:
Click to expand...
Click to collapse
No problem, glad it worked! Worked for me (twice haha)
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.
The dual boot 6 thread says it creates a secure micro SD partition but Its only for the 128gb devices. I have the 240gb device and I'm wondering if there is another way to make a partition like that.
Unfortunately, I'm not sure what you mean. Do you want to have a split SD partition or reformat the internal "SD card" (storage)?
I want to create a new separate partition one that would not be wiped when you format data. In the dual boot thread it says that it creates a new partition so there is a way I'm just wondering how to do it. Unfortunately the dual boot only works on 128gb device I got the 240...
Macusercom said:
Unfortunately, I'm not sure what you mean. Do you want to have a split SD partition or reformat the internal "SD card" (storage)?
Click to expand...
Click to collapse
jessejamesd2i said:
I want to create a new separate partition one that would not be wiped when you format data. In the dual boot thread it says that it creates a new partition so there is a way I'm just wondering how to do it. Unfortunately the dual boot only works on 128gb device I got the 240...
Click to expand...
Click to collapse
I'm not sure if this is easily possible due to how the super partition works. Unfortunately, this is out of my knowledge. There are ways of repartitioning your device but I'm not sure how it plays together with encryption
I found a guide for doing it but i cant because i need a twrp that has the commands to create or modify partition sizes. I have some knowledge about how to do it because i used to play with linux alot when i was younger. I know how to do it but im worried about encryption & whatever else that i dont know. All i know is they figured out how with the dualsix, I sent him a pm asking how hopefully it was him who compiled the scripts & knows exactly what to do. I really appreciate you taking the time to try to help. I love XDA & its members everyone is quick to try and help and there is not very many people who talk **** and act disrespectful. Thanks for being one of those awesome people!
Macusercom said:
I'm not sure if this is easily possible due to how the super partition works. Unfortunately, this is out of my knowledge. There are ways of repartitioning your device but I'm not sure how it plays together with encryption
Click to expand...
Click to collapse
Hi there, I was trying to flash a combination file on my s10+. then i saw a thread about flashing combination without etoken. to do that i need to delete bootloader with flashing uh.bin instead of sboot.bin. so did that. as a result my phone is dead now. and i follow the tutorial but no success. with multi downloader program it gives error that dram_el3mon not found. is there anybody who can help me about it? is there any other way to fix it?
not sure if this will work, but it worked on the S3's when they "hard bricked". If you can get the bootloader and mount it on a card that is the exact same size as internal storage, the hardware will look at external storage for a bootloader if the one on the internal storage is corrupted. Not sure if they still implement this as a boot strategy in their boot order, but worth a shot
Youdoofus said:
not sure if this will work, but it worked on the S3's when they "hard bricked". If you can get the bootloader and mount it on a card that is the exact same size as internal storage, the hardware will look at external storage for a bootloader if the one on the internal storage is corrupted. Not sure if they still implement this as a boot strategy in their boot order, but worth a shot
Click to expand...
Click to collapse
can you tell me how can i mount bootloader on a card?
ariful.sahed said:
can you tell me how can i mount bootloader on a card?
Click to expand...
Click to collapse
Rufus. use it to mount the iso on the card. Rufus is free and i use it for pretty much every image i need to mount. IMGBurn does it too i think