Hey people,
I'm getting mixed signals from my phone on whether it is encrypted or not and I would like to know how to find that out for sure.
My goal is to have a stock rom android 8 on my S7, rooted, with encryption.
I recently flashed the latest stock oreo build with odin, I don't remember if I let it boot once before the next step, but I think I did (I read the following thread only after I did this: https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007)
Then, I installed TWRP via odin, booted into TWRP, formated /data, copied the magisk v16.0 installer zip to the now mounted /data and installed it.
Next, I booted the phone and set up all my accounts and apps.
Finally, I looked into how to get Samsung Health running on the rooted phone and manually set the ro.config.tima property in build.prop to 0 (and I still have no trouble restarting the phone).
The result is, that the phone is rooted, TWRP can not mount /data anymore (which seems to be a hint that the phone is encrypted), but in the android settings, I still have the option to encrypt the device (right above the option to encrypt the sd card) and changing the tima property did not cause any trouble, which again seems to be a hint the phone is not encrypted.
Does anyone know how to check if the phone is now encrypted or not?
If /data can be mounted in TWRP, you aren't encrypted. I'm trying to do the same thing only in an S8, with no luck getting encryption working. If I try to encrypt using settings, the phone reboots after a few minutes on the encrypting splash screen without encrypting anything. It worked fine on an S7 with Nougat stock.
danielwbn said:
Hey people,
I'm getting mixed signals from my phone on whether it is encrypted or not and I would like to know how to find that out for sure.
My goal is to have a stock rom android 8 on my S7, rooted, with encryption.
I recently flashed the latest stock oreo build with odin, I don't remember if I let it boot once before the next step, but I think I did (I read the following thread only after I did this: https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007)
Then, I installed TWRP via odin, booted into TWRP, formated /data, copied the magisk v16.0 installer zip to the now mounted /data and installed it.
Next, I booted the phone and set up all my accounts and apps.
Finally, I looked into how to get Samsung Health running on the rooted phone and manually set the ro.config.tima property in build.prop to 0 (and I still have no trouble restarting the phone).
The result is, that the phone is rooted, TWRP can not mount /data anymore (which seems to be a hint that the phone is encrypted), but in the android settings, I still have the option to encrypt the device (right above the option to encrypt the sd card) and changing the tima property did not cause any trouble, which again seems to be a hint the phone is not encrypted.
Does anyone know how to check if the phone is now encrypted or not?
Click to expand...
Click to collapse
First thing first. When following old guides, sometimes they still work, often a security patch has closed the loop. So it is always preferable you look for a guide which specifically mentions OREO and the firmware versions your using.
Secondly, flash latest stock Oreo for your region (preferably unbranded) then root via any Oreo root guide on the forum and job done. Phone on stock, rooted and encrypted. Encryption is enabled by default on INTERNAL storage of stock ROM, rooting or TWRP doesn't change that. SD card remains open until you encrypt.
TWRP reporting internal storage at 0mb because it's encrypted yay!
Related
I have the TX1541 model, 16GB ROM. I just got the device a few hours ago so here's a quick rundown of exactly what I have done with it so far.
1. Boot
2. Go through google setup
3. Install marshmallow update
4. Format Sandisk 32GB SDCard as internal storage
5. Enable Developer options, allow OEM unlock, enable USB Debugging
6. Move latest CM13 nightly and OpenGApps to internal storage using MTP
7. Boot into fastboot
8. Unlock bootloader successfully
9. Flash latest TWRP build (twrp-osprey-3.0.2-r1) successfully
10. Reboot into recovery
11. Swipe to allow TWRP to allow modifications
Now, I can't install any of the zips I moved on the device earlier because according to the log neither "storage" nor "/data" can be mounted. So obviously, if I go to Install -> Select Storage everything has "0MB" and wiping doesn't work. . Oh yeah and MTP doesn't work either so I can't really get any files on the device ATM, maybe using push in fastbooot...
I'd appreciate any help on this...
Don't wipe anything yet... Once you boot into TWRP once and allow changes to system, go to Reboot menu and reboot to Recovery again. Test to see if you can see storage now...
Encrypted?
When you format your SD card as internal, it encrypts it so that you can't use it with other phones, and it protects your data.
If you encrypted it and then installed TRWP you've essentially changed the phone, you won't be able to access it without booting into the android OS that you encrypted it on.
Hope that it wasn't what you did. Otherwise the only way in is to load it into android, connect to the computer, and get the files from there.
RylenWolf said:
When you format your SD card as internal, it encrypts it so that you can't use it with other phones, and it protects your data.
If you encrypted it and then installed TRWP you've essentially changed the phone, you won't be able to access it without booting into the android OS that you encrypted it on.
Hope that it wasn't what you did. Otherwise the only way in is to load it into android, connect to the computer, and get the files from there.
Click to expand...
Click to collapse
how do you fix it on the computer?
mjf042 said:
how do you fix it on the computer?
Click to expand...
Click to collapse
@Jisifus You need to go in twrp ans change the filesystem to ext4
mjf042 said:
how do you fix it on the computer?
Click to expand...
Click to collapse
@Jisifus You need to go in twrp ans change the filesystem to ext4
Hi
You found solution to this problem :C??
I have the same problem :crying:
This is a known issue in the official version... @Alberto97 has submitted the fixes, we just need to wait until it's merged into official build.
An unofficial build with the fixes applied is available here: https://forum.xda-developers.com//2...t/twrp-twrp-moto-g-2015-t3170537/post71386235
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.
Hey guys just want to know if there's a way to avoid samsung encrypting the internal storage. I know there's the no-verity-opt-encrypt but I read even if I flash that and proceed to root with magisk the internal storage will be encrypted anyways. I'd like to have it encryption free with magisk without having to go for a custom rom. Is that possible?
soarespt said:
Hey guys just want to know if there's a way to avoid samsung encrypting the internal storage. I know there's the no-verity-opt-encrypt but I read even if I flash that and proceed to root with magisk the internal storage will be encrypted anyways. I'd like to have it encryption free with magisk without having to go for a custom rom. Is that possible?
Click to expand...
Click to collapse
You cannot i'm afraid it's part of the stock image, the applicable files are weaved throughout the stock firmware, no one has been able to break Samsungs encryption on a stock image or turn it off.
Wiping internal storage is the only way to get rid of it, Hence the TWRP method of wiping internal storage then flashing a custom Rom.
Yeah last time I formated data, got magisk installed right away. But of course months later I want to install some module and get the can't mount data error. So that means i'd have to "format data" on twrp and get magisk and the module installed before the first boot, right?
soarespt said:
Yeah last time I formated data, got magisk installed right away. But of course months later I want to install some module and get the can't mount data error. So that means i'd have to "format data" on twrp and get magisk and the module installed before the first boot, right?
Click to expand...
Click to collapse
Possibly but if i remember correctly there's a modified version of TWRP which can handle the encrypted internal storage they way you want.
https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
cooltt said:
Possibly but if i remember correctly there's a modified version of TWRP which can handle the encrypted internal storage they way you want.
https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
Click to expand...
Click to collapse
Tried to install that one but yeah still can't mount data. Edit: Well not sure if it was the twrp change or so but now managed to be able to install the module but from magisk itself. Thanks!
I upgraded to the latest Q4 beta. When doing this following instructions when flashing in TWRP it said to flash the file from USB otg since you couldn't flash from internal storage.
my question is, once you have Q installed as I do can you never flash files from internal storage? i assume this must be the case, or i have something very wrong with what i'm doing. I can't mount my internal storage at all in TWRP or see any of the files.
knives of ice said:
I upgraded to the latest Q4 beta. When doing this following instructions when flashing in TWRP it said to flash the file from USB otg since you couldn't flash from internal storage.
my question is, once you have Q installed as I do can you never flash files from internal storage? i assume this must be the case, or i have something very wrong with what i'm doing. I can't mount my internal storage at all in TWRP or see any of the files.
Click to expand...
Click to collapse
Everything works but decryption.
We may have to wait until official q comes before decryption works.
You may find ways to run unencrypted using search function. I know it has been talked about in the forum.
twinnfamous said:
Everything works but decryption.
We may have to wait until official q comes before decryption works.
You may find ways to run unencrypted using search function. I know it has been talked about in the forum.
Click to expand...
Click to collapse
Do you have any idea what could be wrong with my install or setup? I can't mount system. It can't even see my internal sd card it lists it as 0. Never had anything like this happen
knives of ice said:
Do you have any idea what could be wrong with my install or setup? I can't mount system. It can't even see my internal sd card it lists it as 0. Never had anything like this happen
Click to expand...
Click to collapse
U can't see anything in SD card if decryption doesn't work.
What twrp and what where your steps to get where you are now?
twinnfamous said:
U can't see anything in SD card if decryption doesn't work.
What twrp and what where your steps to get where you are now?
Click to expand...
Click to collapse
yes, i know what you are saying with encryption when you can't decrypt it still shows everything with crazy decrypted numbers like 8784322qzzwerei, etc. Even if i turn off my security and boot into twrp (i'm running the latest version i believe 3.3.1-50 according to the twrp menu) it can't see anything on internal storage. when you go to select storage it shows 0mb under internal storage. if i plug in a usb otg it immediately shows and reads that.
if i want to select a file it says select file from internal storage (0 mb)
I have things installed to slot A. these slots i'm not used to using but maybe someone when it boots to twrp its not on the right slot or something? any ideas?
knives of ice said:
yes, i know what you are saying with encryption when you can't decrypt it still shows everything with crazy decrypted numbers like 8784322qzzwerei, etc. Even if i turn off my security and boot into twrp (i'm running the latest version i believe 3.3.1-50 according to the twrp menu) it can't see anything on internal storage. when you go to select storage it shows 0mb under internal storage. if i plug in a usb otg it immediately shows and reads that.
if i want to select a file it says select file from internal storage (0 mb)
I have things installed to slot A. these slots i'm not used to using but maybe someone when it boots to twrp its not on the right slot or something? any ideas?
Click to expand...
Click to collapse
Has the rom booted yet? Did u wipe? Nevermind forgot on q it just shows 0mb
U can try switching slots but it might put u back to rom u had before.
As was previously stated, TWRP cannot decrypt data on q. TWRP will have to be updated to address this. It will be the same for everyone.
Once you boot into rom, all your data will be accessible.
Maybe try fastboot boot twrp.img as that may allow decryption
miffymiffy said:
As was previously stated, TWRP cannot decrypt data on q. TWRP will have to be updated to address this. It will be the same for everyone.
Once you boot into rom, all your data will be accessible.
Maybe try fastboot boot twrp.img as that may allow decryption
Click to expand...
Click to collapse
even if i remove all encryption from my device the system still shows at 0mb. which means you can't flash anything in twrp from the sd card.
i'm trying to figure out why i can't get magisk vanced to work and i assume it is because the flashing in magisk isn't occurring correctly.
so does everyone show a system in twrp for q at 0mb? if what i have is normal and the norm, fine but that was the reason for this thread to list the differences/limitations of twrp in q.
I believe TWRP can't access the internal sdcard due to the change in Q called Scoped Storage:
https://developer.android.com/preview/privacy/scoped-storage
This is also why Magisk vanced isn't installing properly
docnok63 said:
I believe TWRP can't access the internal sdcard due to the change in Q called Scoped Storage:
https://developer.android.com/preview/privacy/scoped-storage
This is also why Magisk vanced isn't installing properly
Click to expand...
Click to collapse
i agree.
the problem is, some are reporting no problems with youtube vanced through magisk. others are claiming that they can see the data on their sd card. i have no idea, maybe some of these people don't even have the q beta installed.
knives of ice said:
i agree.
the problem is, some are reporting no problems with youtube vanced through magisk. others are claiming that they can see the data on their sd card. i have no idea, maybe some of these people don't even have the q beta installed.
Click to expand...
Click to collapse
I've been on DP2, 3, and now 4 and never been able to see internal in TWRP. All flashes have had to be done via OTG after the initial Q install.
docnok63 said:
I've been on DP2, 3, and now 4 and never been able to see internal in TWRP. All flashes have had to be done via OTG after the initial Q install.
Click to expand...
Click to collapse
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
knives of ice said:
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
Click to expand...
Click to collapse
I have YouTube Premium so I don't mess with vanced. Sorry...
knives of ice said:
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
Click to expand...
Click to collapse
Because if your run your device unecrypted you can access the data partitions in TWRP while running Q.
Namolas said:
Because if your run your device unecrypted you can access the data partitions in TWRP while running Q.
Click to expand...
Click to collapse
i remove all fingerprints/pins and have no security. i should be able to boot into TWRP and see data then correct?
it still shows 0mb for me and won't mount.
knives of ice said:
i remove all fingerprints/pins and have no security. i should be able to boot into TWRP and see data then correct?
it still shows 0mb for me and won't mount.
Click to expand...
Click to collapse
Currently decrypted state, and running the device unencrypted aren't the same. Even with your fingerprints pins removed if you look in Settings/Security you'll see your device still shows as encrypted.
OnePlus 7 forces encryption by default. To run your device unencrypted you have to format the internal storage (wipes everything pictures media etc) and make sure you flash a special disable force encrypt zip every time you flash anything system related in TWRP.
Its a lengthy process to get it running unencrypted and if you forget to flash the special script even one time OP7P will force encrypt on boot and you have to start over. Its not for everybody but I know a lot of people running this way, myself included.
This should all be fixed with and update to TWRP but who knows how long that will take.
Not sure if this is worth anything or not, but it's decryption related: https://gist.github.com/mauronofrio/af29bad34ad87a1a957d193794f0bf5f
Namolas said:
Currently decrypted state, and running the device unencrypted aren't the same. Even with your fingerprints pins removed if you look in Settings/Security you'll see your device still shows as encrypted.
OnePlus 7 forces encryption by default. To run your device unencrypted you have to format the internal storage (wipes everything pictures media etc) and make sure you flash a special disable force encrypt zip every time you flash anything system related in TWRP.
Its a lengthy process to get it running unencrypted and if you forget to flash the special script even one time OP7P will force encrypt on boot and you have to start over. Its not for everybody but I know a lot of people running this way, myself included.
This should all be fixed with and update to TWRP but who knows how long that will take.
Click to expand...
Click to collapse
Thanks for your post.
So if I want to "dirty flash" a rom on android q, is it still possible with data encrypted or should I format internal storage anyway ? (and clean flash...)
Gabrech said:
Thanks for your post.
So if I want to "dirty flash" a rom on android q, is it still possible with data encrypted or should I format internal storage anyway ? (and clean flash...)
Click to expand...
Click to collapse
On my Pixel (original) with TWRP 3.3.0-0 and Q, I am able to do everything normally, including decrypting, dirty flash, cutstom ROMs, factory, nandroids, etc .... However, /system and /vendor won't mount. But, it works anyway!
The scoped storage is still a pain in the butt.
Guys, having a lot of trouble getting the Havoc ROM on my device. I am new to this slot A/B thing so please bear with me. I am coming from OOS 9.5.13 with unofficial twrp 3.3.1-70. Active slot is B. I rebooted to recovery, it asked me for my password, entered password, wipe data, flash rom, flash twrp installer, and when I reboot recovery I can't access my sd storage!! I see a 0 folder with random folders inside. So I figured TWRP is unable to decrypt the other slot. I start from scratch, i.e, format data and let it boot, strangely OOS boots with again like a fresh install To prevent encryption again, I don't go throught the setup, reboot to bootloader, then select recovery, inside twrp again (note: wasn't asked for password this time; I assumed because I didn't go through the OOS initial setup (no PIN etc) the storage in currently decrypted), connect to PC for transferring ROM back onto the phone again, disconnect from PC, wipe data, flash rom, flash installer, revoot recovery, reboots to slot A, and AGAIN no access to the SD card contents (folder 0 with random folders inside again). So my questions are:
1) Can someone please explain to me what's going on...?
2) Is there a way to permanently disable encryption on the device? (no-verity, etc)
3) Can I read something to get up to speed with this two slot thing and how things are supposed to work with OnePlus devices (was a long time Samsung user)
I am terribly frustrated with this; I have gone through this process a ridiculous number of times. I have fastboot flashed stock OOS several times. Even did the MSMTool to get back to as-stock-as-possible (somehow frying my SIM in the process, which I also suspect has something to do with Magisk modules). I am absolutely loosing my marbles over this.. Someone please help me!!
My device is retail Indian unlocked OP7P.
Why are you so hellbent on disabling encryption?
Format data, install rom over adb sideload, boot the rom, profit?