Force Encrypt Disable Patcher How To FIX FED-Patcher v8

How To FIX FED-Patcher v8 Force Encrypt Disable Patcher:

I created a tool – at intially for LTE – that removes the ForceEncrypt flag in a widely wide-spread means (which means it should work no matter what rom you are on). It does that by using patching the currently established boot.Img.
I superior that instrument to make it work for other contraptions too. (See the record beneath to peer in case your gadget is supported)

* Your warranty is now void.
* i am not dependable for bricked devices, dead SD cards,
* thermonuclear battle, or you getting fired in view that the alarm app failed. Please
* do some study if in case you have any considerations about the features in this tool
* before utilizing it! You’re determining to make these adjustments, and if
* you factor the finger at me for messing up your device, i’ll snicker at you. Rough. Quite a bit.
The Android CDD (Compatibility Definition Document suggests that all devices will have to enable full disk-encryption (FDE) with the aid of default. Although I aid every step towards extra protection I have got to criticize this strategy. Full-disk-encryption comes at a cost. Encryption takes time for the reason that some aspect has to de- and encrypt the stuff on the disk at some factor and in current devices it can be the CPU’s assignment. Despite the fact that trendy instruments have quite speedy CPU cores which you can still effortlessly consider the difference between FDE in the on- or off-state. The I/O is turbo and boot-instances take most effective half of as long. (i didn’t do any scientific measurements although)
there is an ongoing dialogue about this topic in cyanogenmod’s gerrit for the nexus 9. Although it is a fun read it is pretty clear that this alternate of views isn’t going anyplace close a valuable outcome. Additionally, Google’s stock ROMs perpetually have compelled encryption enabled on newer devices.
When you consider that performance is foremost to me and at the least my pill does not want the additional security I created the FED-Patcher (ForceEncrypt Disable Patcher).

How does it work?
FED-Patcher is a straightforward flashable ZIP that is alleged to be run in a recuperation that has busybox integrated (like TWRP or CWM). That is what it does:


  1. Checks if your device is compatible
  2. Dumps the currently installed boot.img.
  3. Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version ofunmkbootimg.
  4. It patches the filesystem tables which include the force-encrypt flags. This procedure will exchange “forceencrypt” to “encryptable”.
  5. Then, if vital, it patches the filesystem tables to now not use dm-verity. That is done by using getting rid of the “verify” mount-parameter.
  6. Creates a brand new boot.Img. The unpacking approach is completed through a self-compiled, statically linked version of mkbootimg.
  7. Flashes the modified boot.Img

Supported Devices:
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)

version history:
v1 – initial version with HTC Nexus 9 WiFi (flounder) help
v2 – added Motorola Nexus 6 (shamu) aid
v3 – added help for HTC Nexus 9 LTE (flounder_lte)
v4 – brought aid for signed boot-portraits
v5 – transformed error handling to compensate for lacking fstab records. Some roms appear to not ship with the complete set of boot-records from AOSP.
V6 – FED-Patcher will implement the identical structure for the patched boot.Img that the long-established boot.Img had. Additionally, the kernel commandline will also be taken over. This should fix mostly each case where devices would now not boot after patching.

v7 – FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
V8 – added help for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)

What do I must make this work?
A supported gadget
An unlocked bootloader
An already set up ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A healing that involves busybox (TWRP, CWM)

How do i use it:
Make a thorough, conservative backup of your information if there is any for your gadget
Go into your restoration (TWRP, CWM)
Flash fed_patcher-signed.Zip
in case your gadget is already encrypted (You booted your ROM at least as soon as) you need to do a full wipe to do away with the encryption. This full wipe will clear your entire data to your data-partition (the place your apps as well as their settings are stored) as good as for your interior storage so please, do a backup before. If you don’t do a backup and want to restore your data… well… Call obama.

How do i know if it worked?
Go into your “Settings”-App. In “security”, if it presents you to encrypt your device it is unencrypted. If it says whatever like “gadget is encrypted” it certainly is encrypted.


if you update your ROM you have got to run FED-Patcher once more in view that ROM-updates additionally replace the boot-partition which without difficulty gets rid of my patch. So, if you’re on CM12.1 for example and you used my patch and do an replace to a newer nightly you have got to run FED-Patcher again. For those who don’t accomplish that Android will encrypt your gadget at the first boot.

Is it dangerious?
Good, I carried out plenty of tests that avert mainly anything unhealthy from going down. However, of course, we’re coping with the boot-partition here. Although I tested FED-Patcher quite rather a lot there may be nonetheless room for crap hitting the fan.

Download Attached Files

File Type: zip