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

[gladiac]

Hello everybody,

I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for other devices too. (See the list below to see if your device is supported)

Disclaimer

/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about the features in this tool
 * before using it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
 */

Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in current devices it's the CPU's task. Even though modern devices have quite fast CPU cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any scientific measurements though)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher).

How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This 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 of unmkbootimg.
4. It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
5. Then, if necessary, it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
6. Creates a new boot.img. The unpacking process is done via 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) support
• v2 - Added Motorola Nexus 6 (shamu) support
• v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
• v4 - Added support for signed boot-images
• v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
• v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would 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 support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)

What do I need to make this work?

1. A supported device
2. An unlocked bootloader
3. An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
4. A recovery that includes busybox (TWRP, CWM)

How do I use it?

1. Make a thorough, conservative backup of your data if there is any on your device
2. Go into your recovery (TWRP, CWM)
3. Flash fed_patcher-signed.zip
4. If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal 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 offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.

IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.

Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.

Screenshot
Scroll down to the attached thumbnails.

Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.

GibHub: https://github.com/gladiac1337/fed-patcher

XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)

Contributors
gladiac, rovo89

Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27

Created 2015-10-27
Last Updated 2016-10-23

 

[cyberon]

Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.

I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.

1 - Does this work on stock?

2 - Would i be able to flash the monthly security update images without having to wipe my device every time?

3 - In your opinion, do the speed gains justify the all the work?

Thanks in advance.

 

[gladiac]

Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.

I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.

1 - Does this work on stock?

2 - Would i be able to flash the monthly security update images without having to wipe my device every time?

3 - In your opinion, do the speed gains justify the all the work?

Thanks in advance.

Hi @cyberon,
good questions!

1. Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
2. Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
   To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
3. Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)

I hope I could help.
Enjoy, gladiac

 

[cyberon]

Thanks for the quick and detailed answer @gladiac, now regarding point number 2.

I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.

Am i missing something?

 

[gladiac]

Thanks for the quick and detailed answer @gladiac, now regarding point number 2.

I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.

That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.

 

[cyberon]

Thanks @gladiac, will try that way.

PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.

 

[provolinoo]

hi @gladiac
first of all thanks for your patch

I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?

Thanks a lot

 

[stonebear]

Worked on my N9 - thanks!

 

[gladiac]

hi @gladiac
first of all thanks for your patch

I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?

Thanks a lot

Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac

 

[dmantilal]

Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1

The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?

Don't some major vendors allow the disabling of encryption from within Android?

Anyway, thanks for the patcher.

 

[provolinoo]

Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.

The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?

Don't some major vendors allow the disabling of encryption from within Android?

Anyway, thanks for the patcher.

I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense

 

[jamesalfred]

Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?

EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.

 

[dmantilal]

Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?

EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.

Did you follow the directions and format the entire "data" partition?

 

[nextelbuddy]

Did you follow the directions and format the entire "data" partition?

I too have the same problem didnt work for me.

im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.

Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.

 

[dmantilal]

I too have the same problem didnt work for me.

im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.

Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.

It did not work because you did not follow the directions.

Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.


Give us more info so we can help (assuming you fid it right initially).

P.S. - 6.0 is M(arshmallow), not L(ollipop).

 

[nextelbuddy]

Did you follow the directions and format the entire "data" partition?

It did not work because you did not follow the directions.

Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.


Give us more info so we can help (assuming you fid it right initially).

P.S. - 6.0 is M(arshmallow), not L(ollipop).

i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED

THANKS!

so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?

 

[dmantilal]

i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED

THANKS!

so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?

Side-loading the OTA then following that with a FED flash seems much safer.

Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.

 

[jamespat93]

I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?

 

[rawdealer]

I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?

You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.

 

[Emilius]

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?