Database Develop

Encrypted partition cannot be decrypted in TWRP 2.8.0.2

I'm wondering if anyone else who's encrypted their data partition as per the security settings on your HTC One if you've been able to access the partition in TWRP 2.8.0.2, I keep getting password fails.

fluxgfx said:
I'm wondering if anyone else who's encrypted their data partition as per the security settings on your HTC One if you've been able to access the partition in TWRP 2.8.0.2, I keep getting password fails.
Click to expand...
Click to collapse
From what I read recovery cant touch an encrypted partition at all. This is why you have to un encrypt the device before flashing a new rom. The main reason that the auto encryption will be disabled by default on custom roms once L release comes out.

zelendel said:
From what I read recovery cant touch an encrypted partition at all. This is why you have to un encrypt the device before flashing a new rom. The main reason that the auto encryption will be disabled by default on custom roms once L release comes out.
Click to expand...
Click to collapse
Interesting. Haven't read that anywhere at this time. Even if I wanted to decrypt the partition it wouldn't be possible. It's permanent on the HTC One M7. Decryption isn't available on 4.4.3, but that's ok. The only thing that's encrypted is the storage, which doesn't stop me from flashing a rom, kernel, images of any kind since most of the flashing I do, I never leave anything on the data partition.

I did read that HTC uses different crypto keys which aren't AOSP which means recovery suchs as TWRP or CWM won't decrypt. By reading other material on the subject it probably will be possible on future versions.
It's mild annoyance at the moment...

fluxgfx said:
I did read that HTC uses different crypto keys which aren't AOSP which means recovery suchs as TWRP or CWM won't decrypt. By reading other material on the subject it probably will be possible on future versions.
It's mild annoyance at the moment...
Click to expand...
Click to collapse
Couldnt say on Sense roms as I have not run a Sense based rom since back on WM 6.

zelendel said:
Couldnt say on Sense roms as I have not run a Sense based rom since back on WM 6.
Click to expand...
Click to collapse
Yeah apparently Sense roms are using a variation of the crypto keys. Which means TWRP standard decrypt keys with proper pwd might not work. Seems like something should be fixed at somepoint for this.
Will have to look into it more on L release or go back to an AOSP rom like CM11 or OmniROM, but that brings a whole can of others problems

Lollipop 5.1.1 stock image is up !

Finally ! Straight from Google DEVS
"nakasi" for Nexus 7 (Wi-Fi) 5.1.1 (LMY47V)

I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).

fortissimo said:
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
Click to expand...
Click to collapse
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.

iBolski said:
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
Click to expand...
Click to collapse
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars

gsmyth said:
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Click to expand...
Click to collapse
thats for the Nexus 5 though, I havent seen anything for the N7 yet.
2 of mine are bricked (one APX mode, the other corrupted emmc but seems to "work" - sort of - with all F2FS rom), I bought a board for $40 to replace one of them but the digitizer clamp and pins flaked off on contact when trying to reassemble it so Im reluctant to do anything with it without touch capability. its just going to sit there with my blutooth mouse for kitchen-netflix for now. Im thinking of selling them all "as is" but Im curious if this update pans out, I might keep the touchless one.

There's a lollipop rom for F2FS??

Varnak said:
There's a lollipop rom for F2FS??
Click to expand...
Click to collapse
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden

JerryPi said:
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
Click to expand...
Click to collapse
ok thanks. But i need to format system with normal partition?

Varnak said:
ok thanks. But i need to format system with normal partition?
Click to expand...
Click to collapse
You leave system partition on default ext4.

JerryPi said:
You leave system partition on default ext4.
Click to expand...
Click to collapse
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140

Varnak said:
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Click to expand...
Click to collapse
With the newer versions of twrp that zip is really not necessary to convert your partitions to a different file system.
To check and change format of your partitions go in your twrp recovery under wipe -advanced wipe - choose your partition - then repair or change your file system - there it says wich file system you are using and you can change it accordingly.

in twrp when you are changing the filesystem, it tells you which is the current.
Edit: just saw JerryPi's post

Two days in, 5.1.1 clearly better than 5.1 on my 32gb n7 2012 wifi.
Stock load/kernel/ext4 filesystems maintained, factory reset, full device restore/reinstall from cloud backup, rooted via TWRP, updated with SuperSU.
Nova Launcher, I just prefer it, no functional reason over stock Launcher.
Kindle app runs noticeably better, heck the Zinio reader app seems to work well too.
Google sheets/docs/presentation seems good.
TapaTalk Pro works well, as does Feedly. Notably less latency on network i/o and page transitions.
Facebook app doesn't seem to bring it down, even without any services disabled.
Haven't tried Chrome yet, and need to reload my music/video content to see how Rocket Player does.
disclaimer: I've taken to running "Trimmer (fstrim)" on an automatic schedule, daily, to keep nand free block lists healthy. That probably helps. I was doing that on 5.1 though.
If this keeps up I'd consider it a completely reasonable upgrade from KK.

Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.

Marcovanbasten said:
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Click to expand...
Click to collapse
You need to flash via fastboot.

Non force encrypted kernel for 7.1.1?

Hey guys, is this a thing yet? Haven't had much luck in my search, might be too early.

The majority of the custom ROMs have been on 7.1.1 for quite some time now, and pretty much all the kernels have been updated to support it. I wouldn't imagine there are any crazy changes in official released 7.1.1 to break compatibility with existing kernels. So pick your poison. My go to is Singularity right now.
edit: unless you mean't the "stock kernel" with no force encryption enabled. In which case just use the FED patcher before you boot, it will unpack the kernel and ram disk, disable dm verity and some other voodoo, and repack the kernel and ramdisk and allow you to boot. I've used it on Marshmallow on CM to try the stock kernel without force encrypting and it worked great. Pretty sure it works for Nougat too but haven't used it in a while.

Dopamin3 said:
The majority of the custom ROMs have been on 7.1.1 for quite some time now, and pretty much all the kernels have been updated to support it. I wouldn't imagine there are any crazy changes in official released 7.1.1 to break compatibility with existing kernels. So pick your poison. My go to is Singularity right now.
edit: unless you mean't the "stock kernel" with no force encryption enabled. In which case just use the FED patcher before you boot, it will unpack the kernel and ram disk, disable dm verity and some other voodoo, and repack the kernel and ramdisk and allow you to boot. I've used it on Marshmallow on CM to try the stock kernel without force encrypting and it worked great. Pretty sure it works for Nougat too but haven't used it in a while.
Click to expand...
Click to collapse
An issue I just came across with custom kernels is that I get no sound whatsoever out of my N6, not even in calls. I tried Elite and ElementalX and both did this. I'm thinking something must have changed in the official 7.1.1 image involving the way it handles sound. Really weird!

H4X0R46 said:
An issue I just came across with custom kernels is that I get no sound whatsoever out of my N6, not even in calls. I tried Elite and ElementalX and both did this. I'm thinking something must have changed in the official 7.1.1 image involving the way it handles sound. Really weird!
Click to expand...
Click to collapse
Thanks for info, and I read fed patcher v8 doesn't work with Nougat but dev working on v9. So for now I guess no kernel that doesn't force encrypt is available.

Dopamin3 said:
Thanks for info, and I read fed patcher v8 doesn't work with Nougat but dev working on v9. So for now I guess no kernel that doesn't force encrypt is available.
Click to expand...
Click to collapse
I ended up using magisk for my issue, it disables dm-verity and turns off forced encryption, hopefully new kernel will be around soon and I have a good feeling they will be!

H4X0R46 said:
Hey guys, is this a thing yet? Haven't had much luck in my search, might be too early.
Click to expand...
Click to collapse
I was curious about this as well since I recently unencrypted my phone. Turns out SuperSU fixes forced encryption so as long as you flash it in your recovery before booting your phone back up you should be good. On 7.1.1 stock at the moment without encryption and all I did was flash the new radio, boot, and system images in Fastboot. I then booted into recovery, flashed SuperSU and rebooted. So far, so good.

[Q] Magisk data partition remain encrypted.

Hi, everyone
Is it possible after installing magisk and rooted,to keep the data partition remain encrypted without bootloop ?

I have yet to find a way, however there is a user claiming to have root with data & system encryption on the Oreo 8.1 ROM. I'm on 9.0 Global, and tried a million different ways. Encryption is different from 8.1 to 9.0 ROMs. I think the .eu multi-language ROM based on China disables the Data encryption (even though it reports Encrypted, the system is encrypted). There was a thread here that told about possibly enabling data encryption while keeping root on the .eu multi-roms, but i have not tried. I prefer the Global ROM.
If anyone can get root with the System partition AND the Data partition fully encrypted, please let us know!

Here in the forum there is a topic where one member helps another to get it done, and the encryption is done. I do not know if there's root in the middle of the tutorial.

on official global I think there is no way to run rooted and encrypted.
on xiaomi EU encryption is disabled by default, but you can enable it by editing fstab. qcom in /vendor/etc. I have already posted about how to do it, search xda

The newer versions break twrp encryption support I was running miui.eu with encryption up untill stable 10.0.0.2. in 10.0.0.3 their must have been some sequrity upgrade that changed the encryption because twrp would no longer decrypt the data partition

mikefallen said:
The newer versions break twrp encryption support I was running miui.eu with encryption up untill stable 10.0.0.2. in 10.0.0.3 their must have been some sequrity upgrade that changed the encryption because twrp would no longer decrypt the data partition
Click to expand...
Click to collapse
The new TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150 does decrypt 9.0 without issues. I use it, but still no way to have encrypted data with ROOT that i know of on Global ROM.

Is there any way to root/magisk global rom 10.0.3 ?, no need encrypted data.

Agimax said:
The new TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150 does decrypt 9.0 without issues. I use it, but still no way to have encrypted data with ROOT that i know of on Global ROM.
Click to expand...
Click to collapse
Oh sweet ill have to check that out i hate not having encryption'
And yes you can run global with no encryption and root just flash no dm-crypt and wipe userdata, lots of guides

Is it possible to encrpyt a ROM and dont lose anything.?

The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond

PriPhaze said:
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
Click to expand...
Click to collapse
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.

Robbo.5000 said:
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Click to expand...
Click to collapse
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then flash DM verity again with the force encryption on?.

PriPhaze said:
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then glad DM verity again with the force encryption on?.
Click to expand...
Click to collapse
Ordinarily you shouldn't need to flash dm-verity. And as far as I'm aware, there is still no need to.
Normally it's just a case of formatting data to temporarily remove encryption, if flashing over MIUI.
As to your specific question, I couldn't say, as I've never needed to flash a dm-verity, disable force encrypt, or vbmeta file/script.
Personally, I would flash the latest fastboot MIUI ROM for the phone, then reinstall EvoX.
Before installing the ROM, in TWRP do the factory reset and then format data (There is no need to wipe anything else). Then reboot into TWRP to ensure the newly formatted data partition is properly mounted and flash as normal.
This has worked for me every time.

Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?

Sandeeep Kiran said:
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Click to expand...
Click to collapse
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.

Robbo.5000 said:
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Click to expand...
Click to collapse
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.

Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Numerous cases? Who's we? What roms on what devices need dfe then? Only seen 2 roms ask for dfe, everything else it's as easy as 'going to and from miui, format data and reboot recovery' works every single time.

Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Try this next time you see somebody saying they have tried may things and always get bootloops when trying to flash an AOSP ROM and you want to advise them to flash dfe.
Instead tell them to flash the latest MIUI fastboot ROM for their device, then install TWRP, in TWRP do a factory reset followed by format data, then reboot into TWRP and flash the ROM.
I bet they will come back and tell you it worked.
Again there should be zero need to flash dfe scripts.
If there are any AOSP ROMs out there that genuinely won't boot without flashing dfe (and here I'm talking about all users of such ROM), then the dev had done something stupid and everyone should seriously avoid the ROM.
At least half of the 50+ ROMs are no longer actively maintained.
The vast majority of Orange Fox extra features are specific to MIUI and so are redundant for AOSP ROMs. Mauronifrio's latest TWRP is the most stable for this phone, so if you're going with AOSP ROMs then the extra stability makes most sense.
I've been aware that mauronifrio does not own this phone ever since his initial build. I was also aware back then that he is also an official TWRP maintainer for other devices and so would mostly likely become the maintainer of the official version for this phone, which has now happened. If you go to the official TWRP site and download for this phone, it is by mauronifrio. You can also download the official version from the OP of his TWRP thread.
I would suggest that in most cases, people getting error 7 issues are not on the latest mauronofrio TWRP build.
Are you aware that all these different recoveries are just TWRP with a fancy dress. This is the great thing about TWRP. It was designed to be extensible, to allow others to build on it, in terms of functionality and design. So really there is only TWRP, just many different flavours.