[How-To] Disable Forced Encryption
- Thread starter bbedward
- Start date
I'm pretty sure you are decrypted now. Your second picture looks like mine...if you click on encrypt phone, the next page should say how to do re-encrypt, which would mean you currently aren't encrypted
My phone is still stock do to some data problems. I'm guessing the greyed out part on the encryption means the phone is encrypted.
Yep, I think so!
Apparently there are two different memory configurations\memory types with the Nexus 6 and I guess this could also account for the difference in Androbench as well?
Cheers,
M
It looks like you're unencrypted. Do you try antutu benchmark. I use that. Then post the results. I think I was around a 51722
Is it technically possible to permanently decrypt a /data partition over for example a modified TWRP? Why did Google not include a way to undo the device encryption?
TWRP is already able to mount my encrypted /data without any password prompts but I don't want to perform a full factory reset right now.
TWRP is already able to mount my encrypted /data without any password prompts but I don't want to perform a full factory reset right now.
fastboot flash boot boot.img would upload boot.img to the phone and flash it to the boot partition so that every time you boot that's what runs. Fastboot boot boot.img would boot the phone using boot.img over usb one time only, most likely it's done on purpose for the rooting process to happen without permanently altering the boot image.
I've seen a HUGE improvement to the lag. The phone can actually keep up with me when I type now. I should have done this a long time ago.
Shouldn't really make a difference typing. Only storage activities are affected.
I am encrypted-complete stock at the moment and I do not experience any lag. I am wondering if decrypting my phone will make a difference in day to day use? I realize the Read/Write speeds are lower with encryption enabled but to me the phone feels fast and I don't experience any lag whatsoever. For those who did it do you see a difference?
It boots faster and backups were faster unencrypted, other than that I didn't see any real difference.
Yeah I'm completely stock, just rooted and unencrypted. And yeah there is a minor difference in speed with the screen transitions and multi app switching. I believe benchmarks are higher. But if you like being encrypted, I'd say keep it. Its just us power users that like to squeeze every bit of power out of our devices. And I believe there is a small difference in battery life. But none to make a casual user go wow.
hi i used auto root to unlock my boatload/root.
Is there an easier way to disable encryption?
I dont understand/know how to do any of the steps
Is there an easier way to disable encryption?
I dont understand/know how to do any of the steps
Plain nope. Hardly can tell the difference but that's just my opinion.
Seems about right..I've gotten 180/50 at times… ur browser speed is good… lowest I?got was 65
Via my NeXus™ 7FHD on XDA Premium app
I tried removing decryption while on cm12, is there any way to remove it? I tried using this same method but it hasnt removed the encryption. I have an unlocked bootloader and twrp, I fastboot flash the boot img, I then went into twrp and did a factory reset, nothing, then I did wiped, dalvik and cache, data and system and still nothing. Any suggestion?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
206I'm not responsible for anything blah blah
This is intended to disable forced encryption on the nexus 6. You can still encrypt the device after doing this, but it won't be automatically done.
After observing how this force encryption stuff works, I got it mostly figured out. (It's entirely a SW layer, as is already widely known). Basically when all the devices from fstab are mounted in android with the forceencrypt option, fs_mgr sets a flag for encryption (something like IF This_Device_Isnt_Encrypted; then This_Device_Needs_Encryption). on devices (looks like android only allows you to encrypt 1 device, which is probably to prevent such cases as over-resource usage ,maybe some other conflict that it doesn't support over 1 device, idk) that have forceencrypt set on them, if it can't unmount the device before doing these encryption checks - in other words if it's usy (like a file is open) - it just skips encryption all together. So if the device had a file preventing it from being unmounted, it just says "oh well, skip encryption." I found this kinda odd behavior anyway
You can still encrypt the device, it just isn't forced. Some people are complaining about the slowness of the encryption SW-layer (why force SW encryption? At least put some HW for it in the device). This makes it the way it probably should be - optional.
Stock LMY47D/LMY47E/LMY47M/LMY47I (5.1.0) - No force encrypt:
https://www.androidfilehost.com/?fid=95916177934540533
Stock LRX22C (5.0.1) - No force encrypt:
https://www.androidfilehost.com/?fid=95857557620392411
Stock LRX21O (5.0) - No force encrypt:
https://www.androidfilehost.com/?fid=95784891001613336
Prerequisites:
- You should be running the same build as the kernel you install (E.G. if you are running 5.1.0 LMY47D you should install the LM47D no force encrypt kernel)
- Your bootloader must be unlocked (fastboot oem unlock)
How-to install kernel:
1.) Reboot to boot loader
2.) Download the appropriate boot.img above
3.) Install it via fastboot (fastboot flash boot boot_noforceencrypt.img)
To disable forced encryption after kernel is installed:
1.) Reboot to boot loader
2.) Format userdata (fastboot format userdata) - This will erase all of your data (apps, sd card, etc.) - so make appropriate backups22
Here's one for LYZ28E
Doesnt take a genius to mode the boot.img
- Extract the Android Image Kitchen zip i uploaded in this post
- drag in the boot.img file you wish to modify onto the unpackimg.bat file
- you should get a command window pop up, it should say succesfull and you will get a few folders added.
- open the ramdisk folder and open the fstab.shamu file using notepad++
- search for forceencrypt and replace it with encryptable. there should be only one case where this exists.
- save the file, go back to the root of the image kitchen folder, and run the repackimg.bat file.
- you should get a new boot.img build called image-new.img, you can use this now to flash on your device
10
Couple of options, but first to note:
- adb sideload from stock recovery will not work if you are not completely stock. It does a block-level update so it will fail if it finds a mismatch on the device boot.img and what it expects, like if you are already unencrypted.
First option:
- Flash the 5.1.0 factory image, and repeat the entire process
- Will wipe everything
Second option (ONLY if you are on stock LRX22C
- You can extract the OTA update
- Hack the script to not install boot img patch and disable md5 checks.
- Don't do it this way
Third option
- Get the factory image and extract it
- Flash the bootloader (fastboot flash bootloader bootloader-shamu-blah.zip)
- Flash the radio (fastboot flash radio radio-shamu-blah.zip)
- Reboot bootloader (fastboot reboot-bootloader)
- Extract the: image-shamu-lm47yd.zip
- Flash recovery (fastboot flash recovery recovery.img) Skip this if you are using a custom recovery and want to keep it
- Flash modified boot.img in OP (fastboot flash boot bootimg_noforceencrypt_lmy47d.img)
- Flash system (fastboot flash system system.img)
The cache/userdata img are only needed if you want to full wipe.
You will lose root, obviously, but can easily get it back from twrp. - Extract the Android Image Kitchen zip i uploaded in this post
