[FIX] FED-Patcher v8 (ForceEncrypt Disable Patcher)

[rawdealer]

I can't get it work on Nexus 6 and chroma rom r26.

My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system

after boot in setting/security it is again encrypted. what I am doing wrong?

You didn't Format the Data It's quite a large button in twrp

 

[Emilius]

You didn't Format the Data It's quite a large button in twrp

OMG, please don't tell anyone

 

[WarningHPB]

Hi there, sorry to ask this its probably been asked before, but how does one disable encryption and have supersu for root on a Nexus 6? (im completely new to the whole encryption thing since my last device the nexus 5 it wasn't forced)

I understand that disabling encryption is done via your patcher, which mods the boot.img on my device, but if i then flash the supersu boot.img does that mean i'll have to encrypt again? Could i first flash the supersu boot.img and then use your patcher to get root and no encryption?

 

[hlxanthus]

Hi there, sorry to ask this its probably been asked before, but how does one disable encryption and have supersu for root on a Nexus 6? (im completely new to the whole encryption thing since my last device the nexus 5 it wasn't forced)

I understand that disabling encryption is done via your patcher, which mods the boot.img on my device, but if i then flash the supersu boot.img does that mean i'll have to encrypt again? Could i first flash the supersu boot.img and then use your patcher to get root and no encryption?

Well no, because chainfires boot.img has all of this done already. It is only the flag that forces encryption that this changes (as well as disabling the red flag).

Also, this does not actually disable encryption, it just disables a kernel from FORCING encryption. You still need to format your /userdata partition to accomplish that.

Sent from my Nexus 6 using Tapatalk

 

[smclaughlin3]

Well no, because chainfires boot.img has all of this done already. It is only the flag that forces encryption that this changes (as well as disabling the red flag).

Also, this does not actually disable encryption, it just disables a kernel from FORCING encryption. You still need to format your /userdata partition to accomplish that.

Sent from my Nexus 6 using Tapatalk

Hey thanks for the information saw you referred someone else here too, but was just confirming cant you just install a non force encrypt custom kernel such as elite wipe data and be unencrypted too? Thanks

 

[hlxanthus]

Hey thanks for the information saw you referred someone else here too, but was just confirming cant you just install a non force encrypt custom kernel such as elite wipe data and be unencrypted too? Thanks

Yes, of course you can do it that way too. This boot patcher will allow you to keep your current kernel and unencrypt. Useful on stock if you want to unencrypt but not root, or on cyanogenmod which forces encryption.

Sent from my Nexus 6 using Tapatalk

 

[provolinoo]

Does this patch work with CM13 official nightlies? I'm on N6 Shamu.

 

[DanteGR]

Does this patch work with CM13 official nightlies? I'm on N6 Shamu.

Yes it should work

Swiftkeyed from my 1+2 A2003

 

[dmantilal]

Does this patch work with CM13 official nightlies? I'm on N6 Shamu.

Works fine on my Nexus 9 running CM 13 nightlies.

 

[ugabuga]

I am using Franco Kernel with [ROM] [Stock-Debloated][6.0.1][MMB29K][08/12/15][Layers]Rooted-Deoxeded-Fast & Stable.

I am currently encrypted and understand that I need to TWRP and format the data partition. Once this is complete, can i restore the nandroid backup made via TRWP and still be unencrypted? What about restoring just the data part of the nandroid?

Is there any way to do this without completely having to redo all my settings, tweaks, etc?

 

[nellorocca]

What about new systemless supersu? Do I need to flash supersu and then this?

Edit: flashed this fix and then supersu.

 

[dmantilal]

What about new systemless supersu? Do I need to flash supersu and then this?

Edit: flashed this fix and then supersu.

SuperSU already disables ForceEncrypt. There is no need for you to flash FED Patcher.

http://forum.xda-developers.com/app...arshmellow-t3219344/post64161125#post64161125

 

[Konsumhaus]

will v8 do the job on 6.0.1 Roms?

I´ve heard that it didn´t work with v7.

 

[cam30era]

will v8 do the job on 6.0.1 Roms?

I´ve heard that it didn´t work with v7.

V8 works fine for me on 6.0.1..

 

[DanteGR]

Hello all.
If I have already decrypted the tablet and the rom I am using has the forced encryption disabled, do I still need to flash the Fedpatcher zip prior to booting the rom?
Thank you in advance

 

[cam30era]

Hello all.
If I have already decrypted the tablet and the rom I am using has the forced encryption disabled, do I still need to flash the Fedpatcher zip prior to booting the rom?
Thank you in advance

No.

 

[sirdizzle415]

Would this patch work with the stock 6.0.1 rom and stock kernel? I'm having trouble having getting it to show "Unencrypted" in the Settings>Security.

 

[DanteGR]

Would this patch work with the stock 6.0.1 rom and stock kernel? I'm having trouble having getting it to show "Unencrypted" in the Settings>Security.

Yeah it should work with stock 6.0.1 rom.

Swiftkeyed from my HTC Nexus 9

 

[carmatana]

SuperSU already disables ForceEncrypt. There is no need for you to flash FED Patcher.

http://forum.xda-developers.com/app...arshmellow-t3219344/post64161125#post64161125

Are you sure?

 

[dmantilal]

Are you sure?

...
These are the stock boot images from Google, with the ramdisk modified as follows:
- patched sepolicy
- disabled dmverity (if applicable)
- disabled forceencrypt (if applicable)
...

That quote and my personal experience using SuperSU 2.62+ lead me to assume that it is disabled, but I am not 100% sure about anything.


Why do you ask?