Hi,
I am using Island (play.google.com/store/apps/details?id=com.oasisfeng.island) which create another user in my Pixel 3. Now I find that in TWRP 3.2.3-0 I can only decrypt the main user's internal storage (/data/media/0). In /data/media/10 for another user, all the directories and files are still encrypted. My phone can't boot into Android now, so I am wondering if I can access the second user's internal storage in recovery mode? Thanks for considering my problem.
(And in /data/data there are only data of main user's applications, where's the data of the second user's applications?)
Related
Hello,
I have a big problem..... This is it:
1. I had my Samsung Note 10.1 and my external SD card encrypted
2. Due to problems with apps I decided to reset the tablet
3. Before the reset, I had to decrypt the Tablet, but i was not told to do the same with the sd card, so I let the sd card enrypted
4. I decrypted the tablet and I did the reset
5. I did start the tablet, I encrypted the tablet again with the SAME password as before
6. But I cannot open the files, I see them in the explorer, but the apps can not open them as they are encrypted.
7. There is also not the posibility in the settings to decrypt the sd-card.
What can I do ?
Thanks
Sorry to hear that, the only way to recover the data on your sdcard is to restore a previous complete backup of your device (cwm backup). This way you restore the encryption master key and you will be able to access the data on your sdcard again. If you haven't got a backup you loose
The master encryption key used is randomly generated at the time of intitial encryption. Decrypting en reencrypting your device will result in using a different master key.
---quote from: http://source.android.com/tech/encryption/android_crypto_implementation.html---
"The master key is a 128 bit number created by reading from /dev/urandom. It is encrypted with a hash of the user password created with the PBKDF2 function from the SSL library. The footer also contains a random salt (also read from /dev/urandom) used to add entropy to the hash from PBKDF2, and prevent rainbow table attacks on the password.
---end quote--
Thanks a lot for your answer. I have already expected that. I thought, that the encryption key being generated is only using the passwort like in the really very well programed software truecrypt. It allows very good security combined with very good usability. It would be much better if the android developers would to the same. I try to suggest that to the android developers.
So now I am going to format my SD card and try to calm done due to the loss of important data :crying:.
Thanks and Happy New Year
Hello,
I want to ask something about an ideea i had.
Alot of apps asks for permisions for SDCARD storage & main storage ( where all the files & photos are stored).
Why not should we have another permission (Photo/Video Acces & Senssible information access), on a separate partition on the phone or on the SDCARD.
I thought like this, you add a sd-card, it will be formated in 2 partitions 1 encrypted/or not based on the phone settings & another general)
The general partition will be used like now. The user will be allowed to select the size for the secure partition.
Also at the first boot of the phone the user will be asked to select the size of the main storage for secure content (mostly 20-30%) of the main storage.
After this, when you install Instagram for ex it will require access to usb & photos and sensitive informations. You will accept.
When you will install...XX Messenger and will require full access to storage, you will accept and you will not be worried that your photos,etc will be shared with China for example )
What do you think? Is it possible something like this now with some app?
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.
I will try to make it short. While trying to install edxposed, I messed up. It went into startloop. Then I flashed the custom ROM, twrp, base rom, formatted internal storage etc. But now I lost the access to internal storage.
So, current scenario is
1. TWRP can access internal sdcard. It's not even showing any encrypted folders, only 2 folders showing - TWRP & Obb
2. Google play can install apps, but no apps can write anything to internal storage I.e. Camera cannot save Photos, cannot save screenshot, Chrome cannot download anything etc.
3. Settings app showing 0b/0b. Es explorer showing 100% filled. Storage showing 12gb used of 56gb.
4. PC can see my phone storage but cannot paste anything in it.
So it seems to me that somehow my internal storage has become RO or something. So if anyone can help me solve this problem, I will be highly grateful. TIA
UPDATE:
problem not solved yet, but what I found is, the main problem is the root directory for the internal storage has changed somehow. By default, it resides in root/storage/emulated/0, but now it has changed to root/storage/emulated, so the apps cannot access it. Now how can I turn it back to default?
Android_Attitude said:
I will try to make it short. While trying to install edxposed, I messed up. It went into startloop. Then I flashed the custom ROM, twrp, base rom, formatted internal storage etc. But now I lost the access to internal storage.
So, current scenario is
1. TWRP can access internal sdcard. It's not even showing any encrypted folders, only 2 folders showing - TWRP & Obb
2. Google play can install apps, but no apps can write anything to internal storage I.e. Camera cannot save Photos, cannot save screenshot, Chrome cannot download anything etc.
3. Settings app showing 0b/0b. Es explorer showing 100% filled. Storage showing 12gb used of 56gb.
4. PC can see my phone storage but cannot paste anything in it.
So it seems to me that somehow my internal storage has become RO or something. So if anyone can help me solve this problem, I will be highly grateful. TIA
Click to expand...
Click to collapse
It sounds like to me you have corrupted your internal SD card you will have to format SD card instead of normal wipe and then reflash rom via Computer
SAMSUNG_MANIX_64 said:
It sounds like to me you have corrupted your internal SD card you will have to format SD card instead of normal wipe and then reflash rom via Computer
Click to expand...
Click to collapse
I have formatted it already. And what's the difference between flashing a ROM via computer & via USB?
Android_Attitude said:
I have formatted it already. And what's the difference between flashing a ROM via computer & via USB?
Click to expand...
Click to collapse
Wipe vs format. Wipe is just removing files from partition without destroying the partition. Format is rebuilding the partition fresh. You did not format phone because that would fix this problem. Format data partition and this will be fixed.
I also had the same issue so i flashed stock through pc. Now its fine. Only issue is on Twrp data shows encrypted, i think i have to flash dm verity zip to decrypt it
twrp recovery showing 0 files in internal storage and showing some random file names I am unable to do anything please help how to fix it
KARTHIKMC007 said:
twrp recovery showing 0 files in internal storage and showing some random file names I am unable to do anything please help how to fix it
Click to expand...
Click to collapse
If you're using a relatively new phone (shipped with android 9.0 or later versions), you most likely have an encrypted data partition. This kind of encryption is relatively new and is called FBE (File Based Encryption), where every file and folder are encrypted separately. (those random file names!)
To access your data partition through twrp, you need to input your lock screen (or boot-up pin) credentials when prompted at the beginning, if you don't receive such a warning at twrp startup, then your custom recovery image may simply not support decrypting storage. In that case use another one .
Slim K said:
If you're using a relatively new phone (shipped with android 9.0 or later versions), you most likely have an encrypted data partition. This kind of encryption is relatively new and is called FBE (File Based Encryption), where every file and folder are encrypted separately. (those random file names!)
To access your data partition through twrp, you need to input your lock screen (or boot-up pin) credentials when prompted at the beginning, if you don't receive such a warning at twrp startup, then your custom recovery image may simply not support decrypting storage. In that case use another one .
Click to expand...
Click to collapse
thank you
but I have flashed orange fox recovery and twrp latest in both it is showing the same random file names