Related
*8.1 Official is here! -Updated 1/7/18*
Thank you to @osm0sis for the Android Image Kitchen tool used to modify the boot.img's, found here. An especially huge thanks to @Tigerstown for teaching my Windows-using rookie ass, and just for supporting a device he doesn't even own for so long. It is incredibly appreciated.
Next to each build number you'll find the first links are simply boot.imgs modified to just disable forced encryption. The second links are stock boot.imgs that have both disabled forced encryption, and dm verity has been disabled as well - take your pick. Only SYSTEMLESS ROOT is working with these boot.imgs. Tigerstown has put a lot of effort into trying to get system root working, but unfortunately it doesn't seem doable yet.
Naturally, the regular warnings and disclaimers apply here. I cannot be held responsible if anything goes wrong, no warranties, etc. Of course should something happen, myself and the community are here to help.
Going from using a boot.img that is just decrypted to one that also has dm-verity disabled will cause SuperSU to fail when flashing - specifically when the script gets to patching sepolicy.
Starting with NRD90R and on, see the download links in this thread below. Any build prior you will find the modified boot.imgs for your respective builds in Tigerstowns thread here.
Simply flash the corresponding boot.img for your build number via fastboot:
Code:
fastboot flash boot boot.img
If your device is currently encrypted and you are looking to decrypt it, use the commands below. Please note that coming from an encrypted device, when you decrpyt it you WILL WIPE YOUR PHONE AND YOU LOSE YOUR DATA.
Code:
fastboot flash boot boot.img
fastboot format userdata
fastboot format cache
LG NEXUS 5X NOUGAT & OREO MODIFIED BOOT.IMG DOWNLOADS
Android Nougat 7.0
NRD90R 7.0 September Security Update #1- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
NRD90S 7.0 September Security Update #2- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
NBD90W 7.0 October Security Update- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
NDR91N 7.0 November Security Update #1- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N5D91L 7.0 November Security Update #2- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
NRD91P 7.0 December Security Update- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Android Nougat 7.1.1
NMF26F 7.1.1- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N4F26I 7.1.1 January Security Update- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N4F26O 7.1.1 February Security Update- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N4F26T 7.1.1 March Security Update- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Android Nougat 7.1.2
N2G47F 7.1.2 April- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N2G47O 7.1.2 May- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N2G47W 7.1.2 June- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N2G47Z 7.1.2 July- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
N2G48C 7.1.2 August- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Android Nougat 8.0 Oreo
OPR6.170623.013 8.0 Aug. forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPR4.170623.006 8.0 Sept. forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPR4.170623.009 8.0 Oct. forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPR6.170623.023 8.0 Nov. forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
***Android 8.1 Oreo***
OPM1.171019.011 8.1 Dec. forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPM3.171019.013 8.1 Jan. forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
DEVELOPER PREVIEW DOWNLOADS FOR NOUGAT & OREO
Android Nougat 7.1 Developer Preview
NPF10C (DP1) forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
NPF26F (DP2) forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Android Nougat 7.1.2 Developer Preview
NPG05D (DP1)-forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
NPG47I (DP2)-forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Android 8.0 Developer Preview
OPP1.170223.012 DP1- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPP2.170420.019 DP2- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPP3.170518.006 DP3- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPP4.170623.014 DP4- forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Android Oreo 8.1 Developer Preview
OPP5.170921.005 DP5 - forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
OPP6.171019.012 DP6 - forced encryption disabled - link / forced encryption disabled & dm-verity disabled - link
Looks great man nice job. I'll drop a link in my modified boot.img to direct everyone here and I'll close mine as we talked About.
I think they'll have a security update out tomorrow. As soon as factory images are online I'll post the new boot.img.
Awesome!! Looking forward to flashing with these...
November security update images are live now, should have this ready tonight after I'm home from work. If anyone is updating to the new build and feels like testing out really quickly, please feel free to PM me.
New boot.img is up in the OP for NRD91N (November update).
I'll really appreciate a boot.img for the latest bulid for 5X, which is currently N5D91L (November security follow-up patch)
Oversemper said:
I'll really appreciate a boot.img for the latest bulid for 5X, which is currently N5D91L (November security follow-up patch)
Click to expand...
Click to collapse
There was a 2nd update for Nov? I don't have device so I had no idea if so
---------- Post added at 01:22 AM ---------- Previous post was at 01:21 AM ----------
Tigerstown said:
There was a 2nd update for Nov? I don't have device so I had no idea if so
Click to expand...
Click to collapse
I forgot there is a new thread my bad this is no longer my old thread got confused lol
Oversemper said:
I'll really appreciate a boot.img for the latest bulid for 5X, which is currently N5D91L (November security follow-up patch)
Click to expand...
Click to collapse
Holy ****, I don't know how I missed this. I had no idea there was a second Nov. update...I've just been keeping my eye's open for the new DP. I'll have it online shortly.
Oversemper said:
I'll really appreciate a boot.img for the latest bulid for 5X, which is currently N5D91L (November security follow-up patch)
Click to expand...
Click to collapse
@Oversemper, I have it ready to go but I don't have the time to install this firmware on my phone to test it, and I don't want to make it available in the OP until it has been tested. If you'd like I can DM you the link to it in Google Drive so that you can test it. It should be all set to go...this is a really simple alteration. Would you be willing to test it?
stmims1124 said:
@Oversemper, I have it ready to go but I don't have the time to install this firmware on my phone to test it, and I don't want to make it available in the OP until it has been tested. If you'd like I can DM you the link to it in Google Drive so that you can test it. It should be all set to go...this is a really simple alteration. Would you be willing to test it?
Click to expand...
Click to collapse
Theoretically, if something is wrong I will be able to just flash stock boot.img? If so, then I will be glad to try it out first.
Oversemper said:
Theoretically, if something is wrong I will be able to just flash stock boot.img? If so, then I will be glad to try it out first.
Click to expand...
Click to collapse
My apologies, I didn't realize XDA was going to be down for maintenance. I'll have it tested and uploaded as soon as I get home from work today and I'll let you know as soon as it's online.
Nothing should go wrong, but if it did, then it could encrypt your phone on first boot, which I'm sure you'd like to avoid. I'll test it out myself then upload it ASAP this evening.
Oversemper said:
Theoretically, if something is wrong I will be able to just flash stock boot.img? If so, then I will be glad to try it out first.
Click to expand...
Click to collapse
@Oversemper, and anyone else that may need it, the decrypted boot.img for 95D91L is uploaded. Download link the OP.
Worked like a charm, thank you @stmims1124!
Oversemper said:
Worked like a charm, thank you @stmims1124!
Click to expand...
Click to collapse
Happy to help. FYI, the new Develop Preview was released today (NPF26F). Should have the new boot.img up in the OP at some point this evening. It sounds like their is basically no difference except new, more politically correct emojis. I doubt anyone is rushing home to flash this, but it will be up today.
Developer Preview 2 (DP2) decrypted boot.img is now up in the OP.
stmims1124 said:
Developer Preview 2 (DP2) decrypted boot.img is now up in the OP.
Click to expand...
Click to collapse
File size only 12MB for DP2?
rogconnect said:
File size only 12MB for DP2?
Click to expand...
Click to collapse
Yeah, they're pretty small files. I think they're all about 11.7-11.8mb. Should you extract the stock boot.img from Google's firmware, you'll see it's the same. This is a very slight alteration.
stmims1124 said:
Yeah, they're pretty small files. I think they're all about 11.7-11.8mb. Should you extract the stock boot.img from Google's firmware, you'll see it's the same. This is a very slight alteration.
Click to expand...
Click to collapse
I have flashed your modified boot.img and it works great. But I have a small problem. If I flash any mods e.g. hosts,pixellauncher, surround etc but dont root, they don't work. They o ly work if I flash supersu zip alongside
Psychofrantics said:
I have flashed your modified boot.img and it works great. But I have a small problem. If I flash any mods e.g. hosts,pixellauncher, surround etc but dont root, they don't work. They o ly work if I flash supersu zip alongside
Click to expand...
Click to collapse
The boot.img itself will not give you root, it's just so encryption isn't forced-used either to decrypt the phone, or keep it decrypted when flashing new builds (the stock ones force encryption on first boot). Even after flashing new custom kernels, you will still need to flash supersu or your preferred root method afterwards. Every time you flash a new boot.img or custom kernel, you will lose root and have to re-flash supersu all over again.
I only mentioned root in the OP because I wanted folks to know that in 7.0 and higher, so far only systemless root is working with these (I could be wrong, but I think that for the most part people seem to prefer systemless anyway). I hope this helps clarify.
Maybe I need to edit the OP if it's misleading.
I noticed that the current TWRP version for Pixel (sailfish) now supports data decryption in Oreo. It would be nice to not have to remember to turn off your password before using TWRP. Not to mention having to re-setup all your apps that use fingerprint security after your done with TWRP.
I imagine if it were easy, @invisiblek would have done it. But it would be sweet to have.
Here is a discussion about Pixel 2 that is probably relevant and explains why it is unlikely.
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
I've tried both RR and Havoc with the latest TWRP avaliable, decrypt with password still doesn't work. I just want to have FDE on my device without losing the ability to update.
Hi all,
I'm jumping from LOS 14.1 to 16.1, I have the last unofficial TWRP 3.2.3 installed from the nearby thread, used to work well before encryption, now I can't decrypt the data partition, thus no backups, zip flash, OTA...
Any ideas? Thanks.
[Update]: it seems LineageOS 16 installs its own bootloader on some models that allows the encryption while being compatible with OTA. However, on Z1 it keeps TWRP and thus the incompatibility with the encryption. Any way to install with its bootloader on Z1?
[Q&A] [Collection] Latest TWRP for Asus ZenFone Max Pro M1 & Can TWRP Decrypt?
Hi there. If you still wonder that Can TWRP Decrypt Encrypted Data? The answer is YES. I will explain you why it's always FAIL.
Can TWRP Decrypt Data?First, you must understand HOW does TWRP Decrypt works.
Every month, Google will release new Security Patch for Android. Each version of Security Patch will have different (Minor) Encrypt algorithm. (change monthly. EG: July 4, July 19 will have same algorithm)
So, TWRP must have the same Security Patch as your current ROM on the phone to Decrypt Data Encrypted by that ROM.
What is my current security patch?On phone, go: Settings > About Phone, scroll down, you will see current security patch. If not, go: Settings > About Phone > Android Version.
Don't care about date of security patch, just care about month.
I'm just encrypt but not set any Password and TWRP keep asking to decrypt?Use "default_password" to decrypt.
What is the password to decrypt?Same as your lockscreen PIN/Password/Pattern.
I'm using PIN but TWRP always ask for Pattern. How to decrypt?In TWRP, go to Terminal. To decrypt, type in the terminal: "twrp decrypt <Password/PIN>" and tap Enter.
Note: <Password/PIN> is your lockscreen Password/PIN.
EG: My lockscreen PIN is 4294967296129009, I will type "twrp decrypt 4294967296129009" in the terminal and press enter.
Can I Backup my data when I forgot my Password to decrypt Data.?No.
What is SAR and non-SAR recovery?SAR: Makes System partition as Root.
non-SAR: Normal version, nothing changes.
Android 10 ROMs are SAR, some are non-SAR but can't use old tweaks that modify /System folder because it does not exist. Android 9 ROMs are non-SAR.
Use SAR recovery for SAR ROMs, non-SAR recovery for normal ROMs.
If anyone have question, just reply to the thread, I will answer as much as possible and put it in the second post.
Latest TWRP for ASUS ZenFone Max Pro M1Stock Oreo 334 --> 340 & LineageOS 15.1:
Source / Mirror
Pie May Security Patch:
Source / Mirror
Pie June --> August Security Patch:
Source / Mirror
Pie September --> May 2020 Security Patch:
Source / Mirror
Android Q SAR: (No decrypt)
Source / Mirror
TWRP Mods:
OrangeFox (by gourabpa):
Thread
Pitch Black (by akshat2012):
Thread
SkyHawk (by gourabpa)
Thread
Note:
1. These TWRPs is not my work, I'm just collect links for you for easy download.
So, all credit is to:
KrasCGQ (Oreo and Pie May Security Patch)
alex9yust (Pie September --> August)
Cecell3000 (September --> Feb 2020)
SagarMakhar (SAR Build)
2. Why do I reupload it on my drive? To backup. If the owner delete these files, I will not able to download it again and continue sharing.
Asked Question:
By AVinaSh_S
If Android 10 Beta is SAR then it will not support old Magisk Modules using /system correct me if mistaken.
Also what about disabling the force encryption in Android 10. How to do it.
Click to expand...
Click to collapse
- Yes, you cannot use Magisk Module or any old mod that modifies /system because it doesn't exist. To disable encryption, just format Data Partition normally using TWRP. (Don't use rm -rf)
Thanks for the detail post.
Question : If Android 10 Beta is SAR then it will not support old Magisk Modules using /system correct me if mistaken.
Also what about disabling the force encryption in Android 10. How to do it.
AVinaSh_S said:
Thanks for the detail post.
Question : If Android 10 Beta is SAR then it will not support old Magisk Modules using /system correct me if mistaken.
Also what about disabling the force encryption in Android 10. How to do it.
Click to expand...
Click to collapse
Yes, you cannot use Magisk Module or any mod that modifies /system because it doesn't exist. To disable encryption, just format Data Partition normally using TWRP. (Don't use rm -rf)
Sent from my ZenFone Max Pro M1 using XDA Labs
RedGreenBlue123 said:
Yes, you cannot use Magisk Module or any mod that modifies /system because it doesn't exist. To disable encryption, just format Data Partition normally using TWRP. (Don't use rm -rf)
Sent from my ZenFone Max Pro M1 using XDA Labs
Click to expand...
Click to collapse
Thank you .. so after each OTA update, I will need to format data each time if I do not want to use encryption?
AVinaSh_S said:
Thank you .. so after each OTA update, I will need to format data each time if I do not want to use encryption?
Click to expand...
Click to collapse
Yes. But you can disable force encryption by magisk. Open Magisk Manager, expand Advanced Settings, untick Preserve force encryption and dm-verity. Now, you didn't need to do a clean install every update.
Sent from my ZenFone Max Pro M1 using Tapatalk
I don't set any screen lock pin,
Tried twrp decrypt command, but still i am not able to get rid of problem
I flashed 059 firmware from official asus site, then flash decrypt zip for pie, after that this problem arises,
Using latest twrp recovery 3.3.1-0
ramansehra said:
I don't set any screen lock pin,
Tried twrp decrypt command, but still i am not able to get rid of problem
I flashed 059 firmware from official asus site, then flash decrypt zip for pie, after that this problem arises,
Using latest twrp recovery 3.3.1-0
Click to expand...
Click to collapse
twrp decrypt default_password
Make sure you have a correct TWRP that match the security patch.
Sent from my ZenFone Max Pro M1 using Tapatalk
RedGreenBlue123 said:
twrp decrypt default_password
Make sure you have a correct TWRP that match the security patch.
Click to expand...
Click to collapse
Currently I installed AEX ROM based on android 10,
Its security patch is 05 Feb,tried android Q twrp,
060 January twrp, 060 Feb twrp, but same problem persists,tried decrypt command in every twrp,
But still data is encrypted,
Do I need to install decrypt zip for android Q also.
ramansehra said:
Currently I installed AEX ROM based on android 10,
Its security patch is 05 Feb,tried android Q twrp,
060 January twrp, 060 Feb twrp, but same problem persists,tried decrypt command in every twrp,
But still data is encrypted,
Do I need to install decrypt zip for android Q also.
Click to expand...
Click to collapse
1. There are no TWRP to decrypt Android 10 now.
2. TWRP Decrypt is like explore an encrypted Data Partition, cannot fully decrypt it to unencrypted.
RedGreenBlue123 said:
1. There are no TWRP to decrypt Android 10 now.
2. TWRP Decrypt is like explore an encrypted Data Partition, cannot fully decrypt it to unencrypted.
Click to expand...
Click to collapse
I want to revert to stock ROM agian ,but problem is there of data encryption.
How to flash stock ROM ROM again?
ramansehra said:
I want to revert to stock ROM agian ,but problem is there of data encryption.
How to flash stock ROM ROM again?
Click to expand...
Click to collapse
1. Download TWRP flashable stock ROM to your computer.
2. Format Data Partition
3. Unmount Data then Mount again
4. Enable MTP
5. Copy stock to the phone
6. Install stock
Sent from my ZenFone Max Pro M1 using Tapatalk
Jan 2020 security patch is out
Sent from my ZenFone Max Pro M1 using XDA Labs
can you please upload the april 4 security patch twrp
After installing Pixel Experience now i cant Encrypt my Device
After installing Pixel Experience Plus now i cant Encrypt My device. I'm using Asus Zenfone Max Pro M1 Pleas Help me
Help and guidance needed. Noob here.
Bootloader unlocked. On stock pie rom. Build No: 087.
I want to flash PR10 or PR11.
Ive downloaded twrp for pie september patch.
Do we still need “decrypt.zip” and “Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip” ?
Is this step correct?
1. Put phone in fastboot mode.
2. Enter fastboot flash recovery command.
3. Straight boot to recovery.
4. Install dm_verity and decrypt.
5. Flash Rom.
6. Reboot.
Pls help...