Related
Now, you can encrypt your device once only and still have the ability to backup/restore, upgrade or change to a different rom without losing encryption or re-encrypting your device. You can also get rid of screen lock pin/password, which is required by Google to have encryption.
As many of us may know, TWRP unlike CWM can deal with encrypted Data partition and internal storage. As such, if you encrypt your custom CM/AOSP based rom and subsequently enter recovery (TWRP only), you are asked for your password and then TWRP decrypts and mounts your encrypted Data, which allows you to upgrade the rom, install a different custom rom or backup your current rom while preserving encryption. What is interesting is that when you install a new rom (or reinstall the old one), you can get rid of screen lock password completely. In other words, your password is used only for encrypting/decrypting.
Now, a word of caution about short passwords. A 4-5 character pin/password defeats the purpose of encryption, since it takes about 4 minutes to break it. There are ways, however, to have separate passwords for encryption and screen lock or, as shown in this guide, get rid of screen lock password completely. Here is what you can do:
1. Have TWRP recovery (CWM does not work)
2. Encrypt your current data and internal storage (go to Security menu and choose encrypt; you will be forced to set encryption password, which will also be your screen lock password).
3. When you are done, turn the phone off and on to check that decryption/encryption works.
4. Next, install encryption password changer from fdroid:
https://f-droid.org/repository/browse/?fdfilter=encrypt&fdid=com.kibab.android.EncPassChanger or this one:
https://f-droid.org/repository/browse/?fdfilter=encrypt&fdid=org.nick.cryptfs.passwdmanager
5. Change your password to a strong and long one. Make a note of it, as if you forget it, you will have to reset your device in flashtool, meaning flashing stock et al, which is pain. You will only need your long password when you are turning your device on. You won't have to enter that or another password, when the device is running.
6. Next, you want to reinstall your current rom or install a new one. For that do:
7. Enter TWRP recovery, enter your password and your system/data/cards will be mounted. Reinstall your rom (install, not restore) or install a new one. Remember, the only thing you need in your new rom is TWRP recovery. Once you are done, reboot the device. You will have your new rom encrypted with no screen password. From that point and on, you can backup your rom (and do other things) that TWRP recovery allows.
Thanks for your guide.
I really tried to follow it to the end, but TWRP will not mount my internal storage. Neither with the original password nor after I changed it to a more complex one.
Unfortunately, I always end up with the "Password Failed, Please Try Again" error message.
Is there any way to make TWRP work with my encrypted internal storage?
As the title states, I flashed the lastest Cataclysm (stable) and ElementalX kernel(also TWRP asked me that SuperSU wasn't present and to flash it so I did, that might've messed it up), phone booted up fine and set my fingerprint password and everything. I decided to reboot my phone and the phone encrypted itself and now the ROM is force closing and I can't do anything. It asks for a password every time the recovery starts up (I tried default_password, no go) and TWRP won't let me decrypt.
So my question is, is there a way to decrypt without erasing userdata? Would really like to keep my internal storage. I have lots of important pictures and files.
Jimlarck said:
As the title states, I flashed the lastest Cataclysm (stable) and ElementalX kernel(also TWRP asked me that SuperSU wasn't present and to flash it so I did, that might've messed it up), phone booted up fine and set my fingerprint password and everything. I decided to reboot my phone and the phone encrypted itself and now the ROM is force closing and I can't do anything. It asks for a password every time the recovery starts up (I tried default_password, no go) and TWRP won't let me decrypt.
So my question is, is there a way to decrypt without erasing userdata? Would really like to keep my internal storage. I have lots of important pictures and files.
Click to expand...
Click to collapse
Transfer the files to your computer and decrypt properly, either via fastboot line command, or one of the toolkits that will do the fastboot command lines for you...there is no way around nuking your internal memory if you want to decrypt...it's that simple.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
micmars said:
Transfer the files to your computer and decrypt properly, either via fastboot line command, or one of the toolkits that will do the fastboot command lines for you...there is no way around nuking your internal memory if you want to decrypt...it's that simple.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
Damn, thought there might be a magic guru way of decrypted your storage. Why did it encrypt in the first place? Can ROMs encrypt devices when flashed?
Also, I thought it being encrypted prevented me from moving any of the files out of my phone?
Jimlarck said:
Damn, thought there might be a magic guru way of decrypted your storage. Why did it encrypt in the first place? Can ROMs encrypt devices when flashed?
Also, I thought it being encrypted prevented me from moving any of the files out of my phone?
Click to expand...
Click to collapse
Nope, unfortunately, no magic way around it...
As to whether roms can or cannot encrypt, it is the kernel that either forces encryption or allows for you to remain in your current state (either encrypted or decrypted)...you'd never want a kernel to force decryption, as that rom would erase your entire internal memory.
As to moving files from your phone, here's a very simple way of looking at it that is not too far from the reality of things under the hood...
When you have an encrypted device, and you have a password set, once you enter your password, you can move files freely from your device to your computer, etc, without issue, and they'll be decrypted.
If you are encrypted, do not know your password, and try to move those same files, they'll be encrypted and unreadable to anyone. To many, that's a excellent feature...it's comforting to know that any unsuspecting thief can't get access to your stuff...and it also allows you time to remotely wipe your device using Android Device Manager from your computer.
Finally, as to how it works, it is my understanding that the device stores your password on the same partition from where it decrypts files prior to opening them, making for a very efficient and effective security measure.
I hope this helps.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
FYI:
- twrp backup data
- copy /sdcard to pc
- fastboot format userdata
- copy from pc to /sdcard
- restore data in twrp
are the needed steps to decrypt without losing any data.
Delete
I somehow got my filesystem encrypted when I flashed TWRP and rooted. When I try to boot into TWRP, I have to enter a password to be able to see anything or do any modifications. What happened?
I didnt have this problem on my Axon but googled.
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
I have no idea if this will help you or not but it will wipe data so your phone will be factory reset. Do at your own risk.
Twerkules said:
I somehow got my filesystem encrypted when I flashed TWRP and rooted. When I try to boot into TWRP, I have to enter a password to be able to see anything or do any modifications. What happened?
Click to expand...
Click to collapse
bhint15 said:
I didnt have this problem on my Axon but googled.
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
I have no idea if this will help you or not but it will wipe data so your phone will be factory reset. Do at your own risk.
Click to expand...
Click to collapse
This is from the Thread @bhint15 posted ,
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
and the reason why ask for password is cuz Axon 7 Data/Storage is Automatically encrypted out of the box, that's why you don't or not going to find any sort of encryption data setting under Settings and That's the reason a lot of users here have issues trying to get back to stock or something similar.....
This may give you some insight.
https://youtu.be/y0fHGJY-vFE
For me it's the Axon 7. I like the bigger res screen, the upcoming daydream compatibility and superior audio and non-Apple like OS.
The Honor 8 dies seem to have a better camera, but I can live with that. Plus I have an LG G5 for when I want photos.
You just have to decide witch Frasier is more important to you.
RojasTKD said:
This may give you some insight.
https://youtu.be/y0fHGJY-vFE
For me it's the Axon 7. I like the bigger res screen, the upcoming daydream compatibility and superior audio and non-Apple like OS.
The Honor 8 dies seem to have a better camera, but I can live with that. Plus I have an LG G5 for when I want photos.
You just have to decide witch Frasier is more important to you.
Click to expand...
Click to collapse
Wrong Thread mate LoL,
DrakenFX said:
Wrong Thread mate LoL,
Click to expand...
Click to collapse
What the neck how did u end up here....
Disregard ?
DrakenFX said:
This is from the Thread @bhint15 posted ,
and the reason why ask for password is cuz Axon 7 Data/Storage is Automatically encrypted out of the box, that's why you don't or not going to find any sort of encryption data setting under Settings and That's the reason a lot of users here have issues trying to get back to stock or something similar.....
Click to expand...
Click to collapse
Alright, I managed to be able to write to /system temporarily by formatting the Data partition in TWRP, then rebooting back into TWRP. However, after rebooting into OS and setting up my phone, I rebooted into TWRP and was faced with the encryption password prompt again! Does the filesystem just re-encrypt itself when you start the OS, or am I doing something wrong?
Twerkules said:
Alright, I managed to be able to write to /system temporarily by formatting the Data partition in TWRP, then rebooting back into TWRP. However, after rebooting into OS and setting up my phone, I rebooted into TWRP and was faced with the encryption password prompt again! Does the filesystem just re-encrypt itself when you start the OS, or am I doing something wrong?
Click to expand...
Click to collapse
I gave up for now. I tried for 4 days to fix this. In the end I have 30 days to return the phone. Hopefully someone will figure out a work around for this issue. I really like using twrp. I have not read a comment on here of anyone being able to boot into system then back into twrp with out having to enter a password to decrypt. I hope someone out there can do it and they figure out a way to fix it for the rest of us..
HonestOtter said:
I gave up for now. I tried for 4 days to fix this. In the end I have 30 days to return the phone. Hopefully someone will figure out a work around for this issue. I really like using twrp. I have not read a comment on here of anyone being able to boot into system then back into twrp with out having to enter a password to decrypt. I hope someone out there can do it and they figure out a way to fix it for the rest of us..
Click to expand...
Click to collapse
When does twrp prompt for password? I just booted into TWRP and it didn't prompt me. Then I simply booted back into the rom. Never prompted for a password.
runderekrun said:
When does twrp prompt for password? I just booted into TWRP and it didn't prompt me. Then I simply booted back into the rom. Never prompted for a password.
Click to expand...
Click to collapse
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Twerkules said:
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Click to expand...
Click to collapse
Which bootloader unlock did you do? I wonder, why would this not happen to me but happen to you? I am willing to test anything that needs to be tested.
You cannot fix that. Like DrakenFX said, the partition encrypts itself in the OS. You cannot disable/bypass this!
XblackdemonX said:
You cannot fix that. Like DrakenFX said, the partition encrypts itself in the OS. You cannot disable/bypass this!
Click to expand...
Click to collapse
Auto-encrypted can be disabled but that's way, way out of my league, need to rebuild boot. Img with that feature disabled.
There are two different scenarios that will be in play here. Is the bootloader unlocked or not. If the bootloader is unlocked then boot.img can be patched with the zip from idlekernle that disables the dm-verity and fstab. You cannot do this if your BL is locked, because it will modify the signed boot.img that that provides root, and will not boot anymore.
After it's patched, the system will not encrypt after /data wipe and TWRP will access it without problem. The downside is no encryption.
For the BL locked crowed, the /data has to be reformatted after flashing new rooted boot.img. This image also enforces encryption so one way to solve this would be for @tenfar to provide us with signed boot.img that set encryption of as well as. Otherwise the TWRP will need a password to decrypt /data if it can't use the default_password. In this case you should be able to enter the same pin you have setup for lock screen to decrypt the main encryption key.
The system re-encrypts itself on every system start after factory reset or /data format because of the forceencrypt flag in fstab, so the pin will be needed as long as that's the case. While TWRP should be able to try to decrypt with "default_password" in case you have not setup any on lockscreen, this sometimes fails, so having a pin on lockscreen usually helps. The cause is most likely that /cryptkey is altered somehow and TWRP can't use it. Wiping /data and rebooting should generate an fresh /cryptkey. I have been able to just flash modded recovery while still on stock boot and backup the /data with no key.
/system should not be encrypted ever since it would make block level OTA impossible to do. Why TWRP is not mounting it or seeing it 0b is a separate question.
Twerkules said:
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Click to expand...
Click to collapse
That would be dreamy. I have no issues waiting, fingers crossed.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
peramikic said:
There are two different scenarios that will be in play here. Is the bootloader unlocked or not. If the bootloader is unlocked then boot.img can be patched with the zip from idlekernle that disables the dm-verity and fstab. You cannot do this if your BL is locked, because it will modify the signed boot.img that that provides root, and will not boot anymore.
After it's patched, the system will not encrypt after /data wipe and TWRP will access it without problem. The downside is no encryption.
For the BL locked crowed, the /data has to be reformatted after flashing new rooted boot.img. This image also enforces encryption so one way to solve this would be for @tenfar to provide us with signed boot.img that set encryption of as well as. Otherwise the TWRP will need a password to decrypt /data if it can't use the default_password. In this case you should be able to enter the same pin you have setup for lock screen to decrypt the main encryption key.
The system re-encrypts itself on every system start after factory reset or /data format because of the forceencrypt flag in fstab, so the pin will be needed as long as that's the case. While TWRP should be able to try to decrypt with "default_password" in case you have not setup any on lockscreen, this sometimes fails, so having a pin on lockscreen usually helps. The cause is most likely that /cryptkey is altered somehow and TWRP can't use it. Wiping /data and rebooting should generate an fresh /cryptkey. I have been able to just flash modded recovery while still on stock boot and backup the /data with no key.
/system should not be encrypted ever since it would make block level OTA impossible to do. Why TWRP is not mounting it or seeing it 0b is a separate question.
Click to expand...
Click to collapse
Well i have formatted my data maybe 30 times with all sorts of different recoveries and boot images. My original boot image is long gone so hopefully that isn't the key. I also don't use a lock screen, I guess I could if it unlocks the data, but I certainly wouldn't want to keep using a lock screen. Anyways I am done with the phone for now, will revisit it when someone fixes posts they had the decrypt PW issue and fixed it.
HonestOtter said:
That would be dreamy. I have no issues waiting, fingers crossed.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
Well i have formatted my data maybe 30 times with all sorts of different recoveries and boot images. My original boot image is long gone so hopefully that isn't the key. I also don't use a lock screen, I guess I could if it unlocks the data, but I certainly wouldn't want to keep using a lock screen. Anyways I am done with the phone for now, will revisit it when someone fixes posts they had the decrypt PW issue and fixed it.
Click to expand...
Click to collapse
See if you can set the pin, go into TWRP and us it. If it works, go back to OS and remove lockscreen, set to none and then go back to TWRP and see if it still asks for one. Did you run TWRP in read only mode or did you swipe to mount as RW?
peramikic said:
See if you can set the pin, go into TWRP and us it. If it works, go back to OS and remove lockscreen, set to none and then go back to TWRP and see if it still asks for one. Did you run TWRP in read only mode or did you swipe to mount as RW?
Click to expand...
Click to collapse
I assume you mean the lock screen pin? I set a lock screen pin of 1234, but "password failed, please try again". So that didn't work. Is there a different pin for the encryption?
***update
That sucked. I don't use a lock screen but after I tried the pin it won't let be go back to none for the lock screen. I was just starting to use this phone to, now its back to the old phone because I can't use a phone with a lock screen . So sad. Hopefully someone figures out a solution to all this security crap.
I'm having the same issue on B27. Do a factory Reset, then a Format, and after it boots to the OS, the data is encrypted again. I'd be somewhat ok with it but I'm not clear on how to install things like Xposed if the drive is encrypted? I assumed ADB SIDELOAD... but not through encryption.
If the answer is "I don't know" -- then can someone help me restore to stock B27. I have a locked bootloader.
zigzampow said:
I'm having the same issue on B27. Do a factory Reset, then a Format, and after it boots to the OS, the data is encrypted again. I'd be somewhat ok with it but I'm not clear on how to install things like Xposed if the drive is encrypted? I assumed ADB SIDELOAD... but not through encryption.
If the answer is "I don't know" -- then can someone help me restore to stock B27. I have a locked bootloader.
Click to expand...
Click to collapse
Xposed should install just fine if you're getting the message in TWRP. Id you're getting the encryption message after the phone is booted and can't access the phone, then you need to format data, then install Xposed so you can use the phone.
Some zips like SuperSU zip will not be able to be installed when the partition is encrypted. Xposed zip should install just fine
mmamedov said:
Xposed should install just fine if you're getting the message in TWRP. Id you're getting the encryption message after the phone is booted and can't access the phone, then you need to format data, then install Xposed so you can use the phone.
Some zips like SuperSU zip will not be able to be installed when the partition is encrypted. Xposed zip should install just fine
Click to expand...
Click to collapse
But if TWRP cannot access the encrypted data, how can one select and flash the TWRP flashable zip that accompanies the Xposed APK? Is the only solution to sideload? I see the option in TWRP but I am not familiar with how to do it.
I'm currently running the stock OOS 4.5.8 with the official TWRP v3.1.1.1 & magisk installed. Last night I received the latest OTA update notice on the phone, now since my phone has been rooted, I know that I needed to download the whole OS file. So I downloaded the full OOS 4.5.10 and copied the zip file to the root directory of the phone, but when I tried to flash the zip file via twrp, I noticed that I cannot locate the file with twrp's built-in file manager, nor could I gain any access to my phone's internal storage. Also, when I booted into TWRP, it asked for a password, I was able to get in by simply pressing cancel. I'm not sure if that action has contributed towards the actual issue.
I tried to use the USB OTG function by placing the OS file on an USB stick, but TWRP failed to detect that as well. So I'm running out of ideas here....
I believe that the culprit is the permission setting problem, and started googling around for a bit, that's when I found this string of codes (quoted below for reference), while the codes from the tutorial could potentially rectify the permission issue, I just want to make sure that the codes won't wipe all the data off from my phone. Can someone please confirm this? Alternatively, if there are other solutions, please let me know. Thanks in advance.
casual_kikoo said:
If you say you can't read/write your internal memory when your phone is booted, it seems to be a permissions problem: follow this tutorial in TWRP to get good permissions back.
Click to expand...
Click to collapse
The problem is that the data on your phone is encrypted. If you set up a pin to unlock your phone when it boots up you enter the same pin into TWRP. Then it can decrypt your data. If you cancel out of the password screen then TWRP doesn't have access to your data which is why you can't find your folder.
jhs39 said:
The problem is that the data on your phone is encrypted. If you set up a pin to unlock your phone when it boots up you enter the same pin into TWRP. Then it can decrypt your data. If you cancel out of the password screen then TWRP doesn't have access to your data which is why you can't find your folder.
Click to expand...
Click to collapse
Thanks mate, that fixed everything. Much appreciated. :good:
Can Moto Stock 8.1 ROM be decrypted ? I have tried no-verity-opt-encrypt-6.1.zip and formating the data partition using TWRP. AFter the phone reboots, the phone reports its still encrypted. Thanks,
Nivead said:
Can Moto Stock 8.1 ROM be decrypted ? I have tried no-verity-opt-encrypt-6.1.zip and formating the data partition using TWRP. AFter the phone reboots, the phone reports its still encrypted. Thanks,
Click to expand...
Click to collapse
It absolutely can and you seem to have done the right things, maybe in the wrong order.
Check this post:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
And more information:
https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption
Normally the way should be:
Boot into TWRP
Format (not just wipe) data
Flash magisk (see "and more information" above)
Flash Disable_Dm-Verity_ForceEncrypt.zip
I had flashes where I had to repeat the steps but actually I'm rooted and decrypted on stock 8.1
Sent from my Moto G5 Plus using XDA Labs
Procedure I used;
Boot into recovery mode
In TWRP goto WIPE then FORMAT DATA, yes, then Back, then back navigation arrow, then back navigation arrow, then INSTALL, select storage, select micro SD card, ok, tap Magisk.zip, then tap Add More Zips, tap no-verity...zip, then Swipe to confirm flash, (no errors on installs), then REBOOT SYSTEM.
Phone reboots, set up google stuff, then to SETINGS, SECURITY & LOCATION, ENCRYPTION & CREDENTIALS, and phone shows its encrpyted.
I have tried different combos, followed the guides posted, maybe I missed something ?
Thanks for your help.
Nivead said:
Procedure I used;
Boot into recovery mode
In TWRP goto WIPE then FORMAT DATA, yes, then Back, then back navigation arrow, then back navigation arrow, then INSTALL, select storage, select micro SD card, ok, tap Magisk.zip, then tap Add More Zips, tap no-verity...zip, then Swipe to confirm flash, (no errors on installs), then REBOOT SYSTEM.
Phone reboots, set up google stuff, then to SETINGS, SECURITY & LOCATION, ENCRYPTION & CREDENTIALS, and phone shows its encrpyted.
I have tried different combos, followed the guides posted, maybe I missed something ?
Thanks for your help.
Click to expand...
Click to collapse
I'm not sure but it sounds as if you flash magisk and no-verity in one task. If so I wouldn't do that, maybe a reboot between the both files could be helpful.
You could also try the following (see also https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption ):
Run the following command in your recovery's terminal before installing magisk.zip:
Code:
echo KEEPFORCEENCRYPT=false>>/cache/.magisk
Magisk should set the force encryption flag to false then.
I don't know which disable....zip you're using, I had always success with this one: Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
And as I wrote above I (and other users too) had to repeat the whole process from formatting data on to get it stick.
Sent from my Moto G5 Plus using XDA Labs
Bingo. This what finally worked:
""Run the following command in your recovery's terminal before installing magisk.zip:""
""
Code:
echo KEEPFORCEENCRYPT=false>>/cache/.magisk
Magisk should set the force encryption flag to false then.""
reboot
""I don't know which disable....zip you're using, I had always success with this one: Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw""
-used yours-
reboot
then format data under TWRP wipe
reboot - and then settings - and under encryption - phone ask if I want to encrypt it, instead of being encrypted by default.
I learned a couple of things tonight. I found if you set "secure start up" on the google start/setup, TWRP was asking for PIN and it did not work to the PIN I had entered - the errors were "unable to Mount Storage and Failed to Decrypt Data".
Thank you very much !! I appreciate your patience - I am 64 years old, was a Linux administrator 35 years back for a few years and then was promoted up, and did not have time to keep the skills up to par. I know enough to be dangerous. I forgot that android was forked from Linux and when I realized it...here I am playing with the phone !!
Nivead said:
Bingo. This what finally worked:
""Run the following command in your recovery's terminal before installing magisk.zip:""
""
Magisk should set the force encryption flag to false then.""
reboot
""I don't know which disable....zip you're using, I had always success with this one: Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw""
-used yours-
reboot
then format data under TWRP wipe
reboot - and then settings - and under encryption - phone ask if I want to encrypt it, instead of being encrypted by default.
I learned a couple of things tonight. I found if you set "secure start up" on the google start/setup, TWRP was asking for PIN and it did not work to the PIN I had entered - the errors were "unable to Mount Storage and Failed to Decrypt Data".
Thank you very much !! I appreciate your patience - I am 64 years old, was a Linux administrator 35 years back for a few years and then was promoted up, and did not have time to keep the skills up to par. I know enough to be dangerous. I forgot that android was forked from Linux and when I realized it...here I am playing with the phone !!
Click to expand...
Click to collapse
You're welcome. Glad that I could help you to make everything work as you want. We oldies have stick together.
Sent from my Moto G5 Plus using XDA Labs
I found a procedure that works everytime. Fastbooted the potter 8.1/op28.85-17-6-2 flashes so the phone would be clean. Reboot then set up google/phone.
Then Fastboot Flash mode and pushed in TWRP to recovery. Then switched to recovery, then in TWRP went to wipe then format data. Then to install and installed magisk. Then reboot system.
Then setup google/phone and confirmed magisk is on the phone.
Then reboot to recovery mode. In TWRP goto wipe, then format data. Then to install, install Disable_Dm-Verity_ForceEncrypt_02.04.2018.zip Reboot system
Then setup google/phone. Noted No Encryption, and Magisk gone. Reboot to recovery and in TWRP install Magisk. Reboot and all is well.
(did the whole procedure three times to make sure all results were repeatable)(and did not need the TWRP terminal commands) (sure is a pain in the rear setting up the phone everytime its reset).