Does on custom ROM works encryption? I tried a couple ROMS, but encryption never works. Always starts encryption and after a a couple seconds phone reboots, do not encrypted. I tried encrypt after fresh install, but always unsuccessful. I googled, some peoples with other devices encrypt their devices. If I remember good, my nexus4 on paranoid was encrypted. Maybe this problem only on s6?
paulyz said:
Does on custom ROM works encryption? I tried a couple ROMS, but encryption never works. Always starts encryption and after a a couple seconds phone reboots, do not encrypted. I tried encrypt after fresh install, but always unsuccessful. I googled, some peoples with other devices encrypt their devices. If I remember good, my nexus4 on paranoid was encrypted. Maybe this problem only on s6?
Click to expand...
Click to collapse
I've got a feeling it's because knox has been tripped.
---------- Post added at 10:16 PM ---------- Previous post was at 10:09 PM ----------
paulyz said:
Does on custom ROM works encryption? I tried a couple ROMS, but encryption never works. Always starts encryption and after a a couple seconds phone reboots, do not encrypted. I tried encrypt after fresh install, but always unsuccessful. I googled, some peoples with other devices encrypt their devices. If I remember good, my nexus4 on paranoid was encrypted. Maybe this problem only on s6?
Click to expand...
Click to collapse
Actually just saw this:
http://forum.xda-developers.com/galaxy-s6/general/device-encryption-root-t3400259
@sofir786, thanks. I checked my logs, the phone always reboots, because he can't unmount files. I found information how temporary disable root, but no succes.
yes encryption works on any rom you just need to unroot ,encrypt ,and root .
1. unroot your phone from su app ( or try to perform a factory reset and wipe Dalvik cache in TWRP )
2. encrypt your phone
3. your phone is now encrypted try flash "CF-autoroot"via odin .
ok, encryption worked, but after encryption boot loop (stuck on samsung logo) Why?
Second time I tried fast encryption, but same end, won't boot, stuck on samsung logo.
booted to TWRP, but can't decrypt or enter to any partition.
so, guys, does somebody has encrypted s6 with custom rom? Always after encryption I get bootloop, but after unrooting device boots without problem. And, after encryption TWRP do not show encrypted partition, do not ask for key or etc.
paulyz said:
so, guys, does somebody has encrypted s6 with custom rom? Always after encryption I get bootloop, but after unrooting device boots without problem. And, after encryption TWRP do not show encrypted partition, do not ask for key or etc.
Click to expand...
Click to collapse
Twrp won't recognise the partition from what I've read that's why you don't see it, have a little Google it seems it's a common issue with twrp and encrypted partitions
sofir786 said:
Twrp won't recognise the partition from what I've read that's why you don't see it, have a little Google it seems it's a common issue with twrp and encrypted partitions
Click to expand...
Click to collapse
I googled, but no 100% true information. But if I understand good, the problem is with samsung encryption and TWRP.
So, if encryption + TWRP do not work, so custom rom with encryption bad choice, because you can't update your rom, make backup or flash new after encryption. Yes, is one possibility, to decrypt, but for this need a lot of time (if I remember good, 24+ hours).
Related
While attempting to flash the latest unofficial MIUI build yesterday, I got stuck at the animation logo, so I gave up. Instead, I flashed the Android L developer build, which did boot up completely for me. However, when I attempted to boot back into recovery, I got prompted to enter my encryption passcode, which I did. However, TWRP keeps telling me that decryption failed and to try again. The issue isn't an incorrect passcode, so I'm at a loss to try to figure out what's going on. Also, because TWRP won't decrypt my storage, I can't flash anything (despite the fact that I'm able to access SD card files from a file manager app when the phone is on). Any way I can get TWRP to decrypt my storage without having to wipe everything completely? Has anyone else experienced this?
tattedupboy said:
While attempting to flash the latest unofficial MIUI build yesterday, I got stuck at the animation logo, so I gave up. Instead, I flashed the Android L developer build, which did boot up completely for me. However, when I attempted to boot back into recovery, I got prompted to enter my encryption passcode, which I did. However, TWRP keeps telling me that decryption failed and to try again. The issue isn't an incorrect passcode, so I'm at a loss to try to figure out what's going on. Also, because TWRP won't decrypt my storage, I can't flash anything (despite the fact that I'm able to access SD card files from a file manager app when the phone is on). Any way I can get TWRP to decrypt my storage without having to wipe everything completely? Has anyone else experienced this?
Click to expand...
Click to collapse
Reflash recovery
Lethargy said:
Reflash recovery
Click to expand...
Click to collapse
I can't without root access.
tattedupboy said:
I can't without root access.
Click to expand...
Click to collapse
Recovery is flashed in fastboot/bootloader...
Unless you used Towelroot, then you'll have to unlock the bootloader, which will wipe.
Really what I need is to figure out why TWRP isn't recognizing my encryption PIN. My storage is encrypted, but whenever I input my encryption PIN, I get an error message. How do I get it TWROP to recognize my encryption PIN?
Doesn't flashing L mess with your sdcard anyway?
Sent from my Nexus 5 using Tapatalk
tattedupboy said:
Really what I need is to figure out why TWRP isn't recognizing my encryption PIN. My storage is encrypted, but whenever I input my encryption PIN, I get an error message. How do I get it TWROP to recognize my encryption PIN?
Click to expand...
Click to collapse
Encryption always causes issues. I suggested to reflash TWRP with fastboot to rule out TWRP itself being the issue.
This is why I never encrypt. I just don't trust it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
This is why I never encrypt. I just don't trust it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
slightly running off topic but .. i have the same issues ... so i pushed twrp 2711 via adb .. now I did a factory reset .. still the request for the encryption password, and i cant seem to get rid of it.
Really frustrating, to the point where i want to smash my phone on the wall.
How can i get rid of it? im just confused,
Onecton said:
slightly running off topic but .. i have the same issues ... so i pushed twrp 2711 via adb .. now I did a factory reset .. still the request for the encryption password, and i cant seem to get rid of it.
Really frustrating, to the point where i want to smash my phone on the wall.
How can i get rid of it? im just confused,
Click to expand...
Click to collapse
Flash factory images lol
Lethargy said:
Flash factory images lol
Click to expand...
Click to collapse
hahaha, i nearly went ballistic on that thing yesterday ... i have no idea how i managed to get rid of it .. first i updated to 2.7.1.1. Twrp... Then i reflashed the Rom ...
Then i did a factory reset .. then i whiped data .. and reflashed rom .. anyways encryption is gone .. but i cant copy stuff from my pc to the handset well ... not that i care .. but kind of inconvenient
Was this resolved?
I am facing the same issue with the AOSP builds of L. I wanted to take new Nandroid backups and realized that TWRP cannot decrypt the partition.
tattedupboy said:
While attempting to flash the latest unofficial MIUI build yesterday, I got stuck at the animation logo, so I gave up. Instead, I flashed the Android L developer build, which did boot up completely for me. However, when I attempted to boot back into recovery, I got prompted to enter my encryption passcode, which I did. However, TWRP keeps telling me that decryption failed and to try again. The issue isn't an incorrect passcode, so I'm at a loss to try to figure out what's going on. Also, because TWRP won't decrypt my storage, I can't flash anything (despite the fact that I'm able to access SD card files from a file manager app when the phone is on). Any way I can get TWRP to decrypt my storage without having to wipe everything completely? Has anyone else experienced this?
Click to expand...
Click to collapse
nirudha said:
I am facing the same issue with the AOSP builds of L. I wanted to take new Nandroid backups and realized that TWRP cannot decrypt the partition.
Click to expand...
Click to collapse
No it cannot.
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
update: it's all gucci, i've managed to figure it out.
Have you tried the patched twrp version? There is a link in google camera port thread. I havent tried but that could work.
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
not a professional but coincidentally this happened to me today while rooting and installing twrp on my s7 sm-g930L 8.0, i installed twrp 1st and was just using a supersu.zip to root it, booted straight into twrp after flashing and had the same problem you have and couldnt install the zip as it wasnt showing up and also saying 0mb, i couldnt even send the zip to it from my computer either until i pressed format in the wipe menu next to advanced wipe button , it was in a bootloop so i hit format cause i was just gonna reinstall stock firmware but i noticed all the correct mb's appeared in system data etc and i could copy/paste n install the zip, flashed it rebooted and it all works, rooted and twrp on official fw 8.0, you might have to reinstall apps and stuff after but hopefully this helps, goodluck
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
ttuleyb said:
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
Click to expand...
Click to collapse
This is just temporary the next time you flash you will see 0mb again you will need to format again.
mkl.xda said:
This is just temporary the next time you flash you will see 0mb again you will need to format again.
Click to expand...
Click to collapse
Unless you flash decrypt zip before booting after flashing
ttuleyb said:
Unless you flash decrypt zip before booting after flashing
Click to expand...
Click to collapse
Still the same. Tried it many times.
mkl.xda said:
Still the same. Tried it many times.
Click to expand...
Click to collapse
Try using superman rom and use option called disable encryption that might work,
If you just wanna root then install magisk because it works with encryption
Got my brand new U11+ today, applied november patch update, but now even with latest TWRP the phone keeps encrypting data. Any tip?
Sadly it looks like this device forum is poorly attended. Just so few U11+ out there? Really a shame
Please have a test and give me a feedback
https://www118.zippyshare.com/v/hUetNmUq/file.html
Please help me, somehow your version encrypted my phone.... What is password?
Thank you so much!
Just to give you feedback, here is what I did (and what happened):
- Reverted back to stock with RUU
- Applied OTA, security patch 2018 11 01
- Flashed according twrp
At first boot encryption occurred again and in security options I could read 'phone encrypted'; still I could enter recovery and normally see data. No request to decrypt, data perfectly accessible and I've been able to flash magisk from internal storage. This was all I needed. Yet, out of curiosity, I tried to wipe data to decrypt the phone. TWRP read something like 'unable to wipe data, you should reboot recovery to access data again'. And then data were gone. No mount, no access.
Once selected reboot to recovery, the phone rebooted system instead. This time there has been no encrypting message, but the phone was wiped. And again, reading in security options, it was encrypted. Going back to recovery I had exactly the same situation as before wiping data: I could see them and normally flash zip.
Even with this weird behaviour, so far I'm satisfied with the result, so again thank you very much!
Glower said:
Thank you so much!
Just to give you feedback, here is what I did (and what happened):
- Reverted back to stock with RUU
- Applied OTA, security patch 2018 11 01
- Flashed according twrp
At first boot encryption occurred again and in security options I could read 'phone encrypted'; still I could enter recovery and normally see data. No request to decrypt, data perfectly accessible and I've been able to flash magisk from internal storage. This was all I needed. Yet, out of curiosity, I tried to wipe data to decrypt the phone. TWRP read something like 'unable to wipe data, you should reboot recovery to access data again'. And then data were gone. No mount, no access.
Once selected reboot to recovery, the phone rebooted system instead. This time there has been no encrypting message, but the phone was wiped. And again, reading in security options, it was encrypted. Going back to recovery I had exactly the same situation as before wiping data: I could see them and normally flash zip.
Even with this weird behaviour, so far I'm satisfied with the result, so again thank you very much!
Click to expand...
Click to collapse
Okay, seems it works in a right way, I will post it to U11+ TWRP released page.
sabpprook said:
Okay, seems it works in a right way, I will post it to U11+ TWRP released page.
Click to expand...
Click to collapse
How can I get my phone decrypted? Why was it encrypted?
drtopjoe said:
How can I get my phone decrypted? Why was it encrypted?
Click to expand...
Click to collapse
You must flash the TWRP recovery which security level is the same as your current android system, otherwise you will get phone encrypted after reboot to android system or TWRP's data decrypting do not work.
sabpprook said:
You must flash the TWRP recovery which security level is the same as your current android system, otherwise you will get phone encrypted after reboot to android system or TWRP's data decrypting do not work.
Click to expand...
Click to collapse
TWRP says decrypted successfull with default password. In twrp I can see all my apps, but when reboot I cannot see.
Ehat version of twrp Shoul I use? Or which security patch should I flash?
Hi Folks, I updated the OS, got everything up andrunning, setup a pin & fingerprint, my settings in Elementalx were lost so I made the mistake the backup kernel was the settings and it a big mistake.
Long story short I am only able to boot to Blu_Spark v9.86 to see all my files and data names encrypted. Ugh.
And I cannot boot into the os. What are my options? Heh? If any?
https://youtu.be/X7yDPszoQ5s
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
Also this.....https://************/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
georgiapi said:
Hi Folks, I updated the OS, got everything up andrunning, setup a pin & fingerprint, my settings in Elementalx were lost so I made the mistake the backup kernel was the settings and it a big mistake.
Long story short I am only able to boot to Blu_Spark v9.86 to see all my files and data names encrypted. Ugh.
And I cannot boot into the os. What are my options? Heh? If any?
Click to expand...
Click to collapse
First i suggest you to update TWRP, reboot to bootloader and boot with blue spark v9.101, you would be able to put your pin and decrypt data, if so, flash the blue spark v9.101 to make it persistent, then reboot to recovery.
Now if everything is gone fine, you can access your storage by putting your correct pin in TWRP and from there i think you can try first to flash oos twice (with TWRP everytime) and see if system will boot-up, if not you need to wipe Data/cache/dalvik (factory reset). Do not flash anything else till system is working and booted
Thank you. Before I begin,
I am new to the term "make it persistent"? I hope you hang with me here....
To clarify, it was late and I was fatigued so I may have left out important details. FYI I run rooted stock roms.
After my fiasco I somehow managed to get booted to TWRP with access to my nandroids, both of which were made or ROMS with no pin or fingerprint. This is left over from the days it was suggested to not make nands of protected roms. Unprotect first.
So I choose restore one and TWRP asks for my pin (before I did the elementalx kernel restore I set a pin) which I entered and now I can only boot to TWRP but all the file names and such are encrypted.
I can also tell you my Slot B is trashed. I had to fastboot set_active _a to get off of it.
Thanks,
Would this be as simple and deleting .key files? I can see them in TWRP /file manager/Data/. I do not see a system file-folder.
Ok first off Everytime you flash the any rom the twrp will be overwrited by stock recovery, this is because with A/B partitioning system there's no more recovery partition and recovery it self is integrated in boot partition so for make it persistent you need to reflash twrp Everytime you flash a rom.
For this I've suggested you to update twrp via fastboot method.
And you can change slot A/B from Twrp too
Now you're problem is encrypted data so you MUST try to update TWRP first, then try what I've already explain before and let me know if it works
OK guys, I bit the bullet and did a full wipe factory reset. I deserve it. You guys are not only off the hook but great. I decided not to burden here over my blunder. I have a data backup about a month old so.........
Long story short. I got in a bootloop cause I think the rom I tried to install is failing. Now I'm into the recovery and can't do nothing cause the TWRP won't let decrypt my data. I already type the password and it shows "password incorrect"
So, I can't boot my phone and am not able to decrypt the data for me to back it up.
Is there any way to bypass encryption or delete the file which saves the PIN CODE? I already tried using DFE but it stuck in the logo.
PocoF3 said:
I already tried using DFE but it stuck in the logo.
Click to expand...
Click to collapse
why DFE? that is only for one purpose - disable forced encryption. it helps to stay unencrypted after formatting.
you messed up everything so you probably already destroyed encryption. your data is lost.
encryption depends on files from /system and /vendor, you could try to restore exact ROM version from your backup like it was before. even then your encryption keys might still flagged as invalid meanwhile because of rollback protection.
learn your lesson to use TWRP for what it is intended - **BACKUP YOUR DATA**
aIecxs said:
why DFE? that is only for one purpose - disable forced encryption. it helps to stay unencrypted after formatting.
you messed up everything so you probably already destroyed encryption. your data is lost.
encryption depends on files from /system and /vendor, you could try to restore exact ROM version from your backup like it was before. even then your encryption keys might still flagged as invalid meanwhile because of rollback protection.
learn your lesson to use TWRP for what it is intended - **BACKUP YOUR DATA**
Click to expand...
Click to collapse
DFE is needed to flash after installing ANY ROM to KEEP the system "unencrypted". That's what I keep doing since many rom updates ago, and always work without any issue.
The point of the thread is strictly aimed to TWRP and its decrypting process, not "what I should have done with my data" or "asking for lessons/advices". Let's keep that false condescension away from the thread.
The problem with decrypting in TWRP is well known, had it like twice, the first solution is what you said, trying to find an exact ROM to flash it over it but the thing is there's no "exact ROM version" atm, so I need to find another solution via TWRP if possible.
your question was about "decrypt the data for me to back it up"