[How-To] Disable Forced Encryption
- Thread starter bbedward
- Start date
Do you mean a nandroid backup with for example TWRP or do you mean backups over adb?
Sorry i replied quickly cause i was in a hurry. Yes, make a backup in twrp, copy it off to your pc, decrypt, copy your backup back to your phone, restore, enjoy unencryption exactly where you left off.
If only it could be done without root, without disqualifying my phone from OTA updates.
-----------------------<SiG>-------------------
My house phone is better than your iPhone.
-----------------------<SiG>-------------------
My house phone is better than your iPhone.
It seems like TWRP's backup ignores /data/media and I can't find a way to include it.
Why would you want to do that? Just drag and drop whatever you want to keep to your pc, then put it back when your done.
efrant
Retired Senior Moderator & Developers Relations
It seems like TWRP's backup ignores /data/media and I can't find a way to include it.
/data/media is your internal storage, i.e., it is where TWRP stores the backup. What do you think would happen if TWRP would allow you to backup the location where it is storing the backup? ?
As was mentioned, once you complete your TWRP backup, just copy the entire /data/media to your computer.
Sent from my Nexus 6 using Tapatalk
M
moonbutt74
Guest
I think if twrp could back up it's backups while making it backups would cause a dimensional rift to open,
from which an abyssal devourer would emerge, playing celine dion's best songs on a kazoo.
[i am sooo bored...]
How do I do that? I am extremely new to osx. This is my first Mac ever.
BTW I have adb and fastboot installed on my macbook. It is the phone that I can't get to connect I guess.
Last edited:
open a Terminal window and change directories to where you have adb and fastboot. then run the command(s)
if you dont know where it is you can use the which command, so which adb and that should tell you where it is.
GL
if you dont know where it is you can use the which command, so which adb and that should tell you where it is.
GL
Is it possible to de-crypt without losing anything if you:
1) Take a nandroid backup
2) Decrypt
3) Restore backup
?
Will this get you to the exact same point as you were when you started the process, only this time decrypted? Also, what needs to be included in the backup for this to work? I guess system, data, boot and what about EFS partition? Recovery? Do they need to be included too?
1) Take a nandroid backup
2) Decrypt
3) Restore backup
?
Will this get you to the exact same point as you were when you started the process, only this time decrypted? Also, what needs to be included in the backup for this to work? I guess system, data, boot and what about EFS partition? Recovery? Do they need to be included too?
After disabling forced encryption nexus 6 wants a password
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Last edited:
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
