[How-To] Disable Forced Encryption
- Thread starter bbedward
- Start date
Just follow the instructions and you'll be ok, twrp and root don't matter for it - it's just changing the kernel/ramfs partition out. You have to factory reset in order for the encryption to "turn off." Normally encryption is forced at bootup on the Nexus 6 (can't be disabled), this just gives you the ability to disable it - which apparently fixes some I/O read issues (as expected from an encryption SW layer I guess).
I booted into fastboot mode and did the fastboot flash which said it completed. Then I did the fastboot erase user data to factory reset the device, no it's stuck in twrp recovery mode blinking on and off. Any suggestions? Do I need to reflash the factory image?
That's weird. It shouldn't have anything to do with TWRP or recovery in general. If you can't get it to boot, then you're probably best of reflashing the factory image. (You did "fastboot flash boot" not "fastboot flash recovery" right
)
That's weird. It shouldn't have anything to do with TWRP or recovery in general. If you can't get it to boot, then you're probably best of reflashing the factory image. (You did "fastboot flash boot" not "fastboot flash recovery" right
Lol yes I did. I actually copied/pasted the command. Ok I'll reflash the factory image and go from there. Thanks
If I have backups (from TiBu) created while the entire phone is encrypted and I pull the backups off the storage, can they be restored on the phone after I go through the process to disable mandatory encryption, or on any other unencrypted phone?
Hmmmmm could be a pattern.
I tried flashing the factory image and this is what I"m getting:
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>flash-al
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.333s]
finished. total time: 0.457s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.686s]
finished. total time: 2.794s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1679592636 bytes
error: update package missing system.img
Press any key to exit...
STUCK!!!!!!!!!
I did it the manual way just fine here: http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Going to attempt disable forced encryption again.
Edit: Manually go back to stock that way then attempt to disable encrypt again. Worked 100% for me with the same error you pasted before (I received it also).
Last edited:
Cool thank you I'll give that a shot. :good:
Edit - seems to work, thanks so much @cheami! I'm all out of thanks for the day but really appreciate it. I was swettin' bullets
Last edited:
In my mind it makes sense that it should especially in the event that its not utilizing the hardware to do it as it is believed. I have to imagine that the CPU cycles required to de encrypt the files needed every time is worse not only for CPU performance, but for the battery as well. How much of course, I have no clue.
---------- Post added at 11:19 PM ---------- Previous post was at 11:17 PM ----------
Please let us know when u get results! I'm sure many are eagerly waiting.
this is very interesting.. and someone even post this amazing result (he did ran few times just to confirm) .. is this true?
if true than it is clear winner faster than iphone6+ except that it is not encrypted
if true than it is clear winner faster than iphone6+ except that it is not encrypted
this is very interesting.. and someone even post this amazing result (he did ran few times just to confirm) .. is this true?
if true than it is clear winner faster than iphone6+ except that it is not encrypted
Where did you find that ? can't verify its the N6 i guess.
---------- Post added at 09:06 AM ---------- Previous post was at 09:05 AM ----------
Does it feel any different in usage?
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
New posts
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
-
