Develop Bugs

[Q] Clockworkmod and ICS-encryption

I found following article: "android.stackexchange.com/questions/19286/will-a-custom-recovery-work-with-an-encrypted-device"
According to this description, it should be possible to use the ICS encryption after partitioning the SDcard. Has anyone already tried it?
Article:
"Mount one partition on /sdcard so that it could be used by system & leave other one (Clockwork Mod can do mounting too)."
How can I do this?

Bump
Nobody tried it yet???

i think is better u dont use encryption at all...
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom (easy to search around to discover this, as i just did now)

Why do you think there are no point with encryption with unlocked bootloader and root?
To me it seems thats when its most important, since its then very easy to get to your data and the only way to protect them?
I am using Titanium Backup and send the backups encrypted to Dropbox, not that much work to wipe and flash ROMS. Kernels you can still flash, at least With Francos app. The only downside is that need a PC to wipe since you have to do it through fastboot.
andQlimax said:
i think is better u dont use encryption at all...
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom (easy to search around to discover this, as i just did now)
Click to expand...
Click to collapse

B1ny said:
Why do you think there are no point with encryption with unlocked bootloader and root?
To me it seems thats when its most important, since its then very easy to get to your data and the only way to protect them?
Click to expand...
Click to collapse
yes, infact what i mean is that if u want protect more ur data, then stay also with the bootloader locked etc (even if the encryption should be enough)

Have thought about also locking the bootloader since you have to wipe anyways, and need a PC. Will not be much more work/time. But is it really any need?
andQlimax said:
yes, infact what i mean is that if u want protect more ur data, then stay also with the bootloader locked etc (even if the encryption should be enough)
Click to expand...
Click to collapse

if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
Click to expand...
Click to collapse
From my point of view I also think that encryption is very important for rooted devices. If you loose your phone, it's very easy to get your privat data on the sdcard and app-data (acounts,...). With an encrypted device, the data are safe and that's all what I want.
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom
Click to expand...
Click to collapse
Also if you create a seperate partition - see article in my first post ???

I would also be interested if this was possible.
Reason being - my employer requires that my phone be encrypted and unrooted. I have been investigating a dual boot setup where I could boot my unrooted, encrypted, stock android image so that I can use it for corporate email and when I need root for something like tethering I could boot off the rooted image.
This way my corporate data would be encrypted and I would be adhering to company policy but I can also enjoy the flexibility of a rooted phone when I need it without wiping my phone every time I want to switch back and fourth.

the /cache partition is the answer, i think
I found out that the stock recovery, as expected, also cannot access the /SDcard partition. However, it looks in the /cache partition for update.zip files when the phone is encrypted. I was able to copy the 4.0.4 update to the cache partition and load it from there. Seems like CWM just needs to be updated to have an option to look there for zip files and we should be able to load them up.

chhall said:
I found out that the stock recovery, as expected, also cannot access the /SDcard partition. However, it looks in the /cache partition for update.zip files when the phone is encrypted. I was able to copy the 4.0.4 update to the cache partition and load it from there. Seems like CWM just needs to be updated to have an option to look there for zip files and we should be able to load them up.
Click to expand...
Click to collapse
The problem is /cache is 100 MB, and some (most?) ROMs are way more than that.
So I don't think using /cache is a fix.
I'm not sure of how CWM mounts the external SD card, but if it uses /mnt/sdcard/external_sd then it's impossible to use the external SD card because it depends on the internal SD for the mount point.
If this isn't the case, then it should be possible to partition the external SD card... Is it?
That leaves us with the only possible solution the partitioning of the internal SD card as mentioned in the link provided by OP.
Has anyone done this?
EDIT:
According to CM9's nightlies "know issues" list, encryption has already been solved and is working. I'm wondering how did they fix it.

bump
anybody knows the answer?

ghost shell said:
According to CM9's nightlies "know issues" list, encryption has already been solved and is working.
Click to expand...
Click to collapse
Could you give me a link to this?

There is a work around for flashing in CWM recovery by using the system ram as a temp file system.
You can use the dd command in adb to backup the entire current firmware and restore it in fast boot.
You can also use the backup and restore feature in ics to backup your sdcard contents and some apks.
There is a dev who is working on a full nandroid equivalent on an encrypted system. He is half way there. It requires cm recovery which has dmcrypt support.
http://forum.xda-developers.com/showpost.php?p=25635462&postcount=54
Check out the entire thread for other info for flashing custom roms via system ram.
ghost shell said:
bump
anybody knows the answer?
Click to expand...
Click to collapse

DanderMan said:
Could you give me a link to this?
Click to expand...
Click to collapse
http://teamhacksung.org/wiki/index.php/CyanogenMod9:GT-I9100:Nightly:Known_issues
Encryption used to be on the know issues, but not anymore. I don't know the status for the Nexus.
Also: http://forum.xda-developers.com/showpost.php?p=25515675&postcount=53
@bunklung
Thanks.
I'm still digesting the information.
The sad part is that even a normal factory reset doesn't allow removing encryption. If at least that would be possible it wouldn't be that bad.
EDIT2:
I've been reading and not even the ram trick would work with me because I can't get adbd running in CWM.
adb doesn't detect any device when the phone is in CWM-recovery mode.

Anyone found a way to revert to stock with cwm already installed for an encrypted phone?

Upgraded to 6.0.1, and now my 5X is Encrypted again

Hey
I disabled encryption my Nexus 5X once I was on 6.0 using TWRP.
Now after upgrading to 6.0.1 the device is encrypted again.
How can I avoid that in the future? I want to device to stay decrypted when I upgrade.
Thanks

When upgrading, if you flash the stock boot/kernel and start up Android it will encrypt your data again. To avoid this make sure you flash a custom boot/kernel that does not force exception before booting into Android

So installing twrp and elementalx right after upgrading should be OK?

Upgrade
Flash TWRP
Format
Flash systemless SuperSU
Flash ex kernel
That's the order I did it in and my phone is not encrypted

If you are already decrypted, upgrade by flashing system.img (along with vendor, radio, bootloader). Don't flash data.img, so you don't lose your current data. You also won't need to format the data partition if you are already decrypted.
Just make sure you flash a modified boot.img each time you upgrade before booting back into the system (best to make sure the modified boot.img is for that specific build) - or go systemless and flash SuperSU that modifies the boot.img automatically to remove encryption.

Thanks I'll do that next time!

I'm completely stock and have the same issue after 6.0.1 upgrade. Phone shows as encrypted and nothing happens when I tap on it.
Any suggestions?
Sent from my Nexus 5X using Tapatalk

hamedunix said:
I'm completely stock and have the same issue after 6.0.1 upgrade. Phone shows as encrypted and nothing happens when I tap on it.
Any suggestions?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then it already is encrypted. You need to format data in twrp and flash modified boot.img / systemless root / kernel that doesn't force encryption
All your data will be lost..

tacofromhell said:
Then it already is encrypted. You need to format data in twrp and flash modified boot.img / systemless root / kernel that doesn't force encryption
All your data will be lost..
Click to expand...
Click to collapse
Coming from Nexus 4, I'm new to encryption by default. So nexus 5x is encrypted and there's no way a normal user could decrypt it. I think I'd be fine with that. [emoji4]
Sent from my Nexus 5X using Tapatalk

hamedunix said:
Coming from Nexus 4, I'm new to encryption by default. So nexus 5x is encrypted and there's no way a normal user could decrypt it. I think I'd be fine with that. [emoji4]
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well, if you're a "normal user" you'd probably don't even know your phone is encrypted.
You probably also won't even know what root is. Most users just want it to work and nothing more.
Forced encryption is an inconvenient thing for us 'advanced users' though.

peltus said:
Well, if you're a "normal user" you'd probably don't even know your phone is encrypted.
You probably also won't even know what root is. Most users just want it to work and nothing more.
Forced encryption is an inconvenient thing for us 'advanced users' though.
Click to expand...
Click to collapse
Been into rooting and stuff like that; however, I don't mind encryption as long as it won't affect my experience on N5X.
Sent from my Nexus 5X using Tapatalk

Decrypting Storage

I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?

I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/

Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/

cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.

Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387

blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.

Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs

Kinda of a weird thing can't decrypt recovery

Hey guys i flashed twrp-3.0.2-1.28-oneplus3.img and now when i am trying to put in my pattern i doesn't work and it says it can't be decrypted. So what can i do you guys?
Thank you in advance,
Rick

jamesblunt1 said:
Hey guys i flashed twrp-3.0.2-1.28-oneplus3.img and now when i am trying to put in my pattern i doesn't work and it says it can't be decrypted. So what can i do you guys?
Thank you in advance,
Rick
Click to expand...
Click to collapse
It's the problem with nougat update and twrp currently. Look for other threads to see what options you have.

TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.

abhibnl said:
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
Click to expand...
Click to collapse
.19 worked for me.

Wipe the /data partition and it won't ask for the pattern.

dbabaev21 said:
.19 worked for me.
Click to expand...
Click to collapse
To OP, Can you please try .19 version of twrp as suggested and see if it can decrypt your encrypted storage?

abhibnl said:
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
Click to expand...
Click to collapse
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!

jim262 said:
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
Click to expand...
Click to collapse
Please read what i typed, again. Why would i want to remove encryption and wipe my internal storage just because the TWRP is outdated? /data also includes your /data/media which is internal storage. I mentioned that TWRP is not supporting encrypted storage in it's present state. It's working fine for decrypted storage and it won't ask for a password if your storage is decrypted.

jim262 said:
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
Click to expand...
Click to collapse
Even if you use this method, if you flash the official ROM later via TWRP, it won't work right. TWRP will prompt for a password even though you've never set one. So actually he's not really wrong.

I used this "method" just last night on my OP3. Loaded the OS via side load and SU also. I am writing to you on this device right now. I also got an AnTuTu score of over 157,484 running stock OOS 4.0. If you are having issues, they are more than likely user issues.

Please read this install method. It will help with data encryption.
https://forum.xda-developers.com/showthread.php?p=70429702#post70429702

MIUI 9 encryption

Hi guys,
I'm trying to find ROM that supports encryption. There are two options available:
1. Encrypt using lock screen password
2. Encrypt device
The first one does nothing. I tried booting into TWRP and see all files unencrypted that are supposed to be, according to the disclaimer.
The second does not finish, it just gets to 100% and then stuck (I waited for a few hours) and the only way it to reboot having corrupted FS.
So the question is how to enable data encryption?
I tried almost everything global stable, Chinese stable and dev ROMS, original and miuipro and xioami.eu. And everything with the same outcome.

MIUI should be using file based encryption which will be present when you boot the ROM.
No need to enable it. Just don't disable it....
Most of the Nougat ROMs for Mi 6 support file based encryption now so all you need do is FORMAT data (not just wipe) and it will be present.
My suggestion would be to install and MIUI stock ROM and then format data (that includes internal storage so backup if you are using it now).
Then reboot and start phone as clean device.
There doesn't seem to be an advantage to using ROMs that don't have file based encryption and then trying to enable it later.
Rom either has FBE or it doesn't have encryption at all for me :/

Does it work for you? How do you confirm this?
I did format from TWRP, ran through setup and took a photo.
I still can access files and can see the content without entering any password from TWRP.
By default all encryption options are unset in MIUI.
You are saying right things if that would be vanilla Android but it seems something is broken in MIUI.

conmu said:
Hi guys,
I'm trying to find ROM that supports encryption. There are two options available....
.
Click to expand...
Click to collapse
I flashed last global stable rom (1.9Gb .tgz) using mi flash tool after a format data in twrp and the device was encrypted by default. I only had to switch on "encrypt using lockscreen password" in privacy settings. But i don't know why even though i flash twrp the stock recovery returns after every reboot
Usefull link:
https://gadgets.ndtv.com/mobiles/fe...nstall-redmi-note-4-mi-max-2-6-5s-mix-1771733

valeriopastore20 said:
I flashed last global stable rom (1.9Gb .tgz) using mi flash tool after a format data in twrp and the device was encrypted by default. I only had to switch on "encrypt using lockscreen password" in privacy settings. But i don't know why even though i flash twrp the stock recovery returns after every reboot
Usefull link:
https://gadgets.ndtv.com/mobiles/fe...nstall-redmi-note-4-mi-max-2-6-5s-mix-1771733
Click to expand...
Click to collapse
You have to disable the stock recovery being reflashed from system with a script.
Not sure where you get that though it comes default with Coffaces TWRP.
Are you using the official TWRP?
If so does it work properly?

Dobsgw said:
You have to disable the stock recovery being reflashed from system with a script.
Not sure where you get that though it comes default with Coffaces TWRP.
Are you using the official TWRP?
If so does it work properly?
Click to expand...
Click to collapse
I'm using this one
https://forum.xda-developers.com/mi-6/development/recovery-twrp-3-1-1-0-xiaomi-mi6-t3608008
because with other recoveries i had problems while restoring data from backup (error 255).

valeriopastore20 said:
I'm using this one
https://forum.xda-developers.com/mi-6/development/recovery-twrp-3-1-1-0-xiaomi-mi6-t3608008
because with other recoveries i had problems while restoring data from backup (error 255).
Click to expand...
Click to collapse
Okay cool.
Doesn't look like it has decryption support so maybe I'll try official

valeriopastore20 said:
the device was encrypted by default
Click to expand...
Click to collapse
Sorry for the stupid question but how did you understand this? What is the actual check to confirm this?

conmu said:
Sorry for the stupid question but how did you understand this? What is the actual check to confirm this?
Click to expand...
Click to collapse
Settings - security - encryption = "phone encrypted"

conmu said:
Sorry for the stupid question but how did you understand this? What is the actual check to confirm this?
Click to expand...
Click to collapse
in privacy settings you will see something like this (i don't have miui9 encrypted anymore so i looked for a screenshot on google) http://attach.en.miui.com/forum/201604/10/202340xmpnzcaciianqnpg.png

Dobsgw said:
Settings - security - encryption = "phone encrypted"
Click to expand...
Click to collapse
SYSTEM & DEVICE > Additional settings > Privacy: Advanced # Encrypt phone
If this it then that is point #2 from my initial message and that never finishes with any ROM I tried
So you say this is enabled right after the flashing and you did not actually ran "Encrypt phone" from this menu (that only works if battery charged above 80%)?
And when you boot into TWRP it asks for a password?

conmu said:
SYSTEM & DEVICE > Additional settings > Privacy: Advanced # Encrypt phone
If this it then that is point #2 from my initial message and that never finishes with any ROM I tried
So you say this is enabled right after the flashing and you did not actually ran "Encrypt phone" from this menu (that only works if battery charged above 80%)?
And when you boot into TWRP it asks for a password?
Click to expand...
Click to collapse
Never had to manually encrypt no.
Just choose a ROM with FBE enabled. That includes MIUI stock.
Flash it and then format data with TWRP.
On first boot it creates the encryption.
Then when you set a password this is your key.
When you boot to TWRP it will ask for the password to decrypt. Password is your pin.

Dobsgw said:
Never had to manually encrypt no.
Just choose a ROM with FBE enabled. That includes MIUI stock.
Flash it and then format data with TWRP.
On first boot it creates the encryption.
Then when you set a password this is your key.
When you boot to TWRP it will ask for the password to decrypt. Password is your pin.
Click to expand...
Click to collapse
Did you flash it via TWRP and formatted without reboot in the same session within TWRP? That is probably the only way I did not try.

conmu said:
Did you flash it via TWRP and formatted without reboot in the same session within TWRP? That is probably the only way I did not try.
Click to expand...
Click to collapse
Yeah that would be the best way.
Formatting data deletes entire SD card so back it up to PC!