Database Users

Root / Unlock Bootloader without removing encryption!

I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit

Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?

Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil

Don't forget adb sideload for installing zips without using internal storage

Use Oem Unlock?

fastboot oem unlock
Yes

How does this affect using Android Pay?

Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.

So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.

I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?

I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app

I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app

How long does the device take to boot up? I've been sitting at the boot animation for a while now.

You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.

Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?

Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.

dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?

Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.

This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...

dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though

TWRP asking for password I didn't set

I unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
Can anyone help?

exSD said:
I unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
Can anyone help?
Click to expand...
Click to collapse
Give this a shot?
Dees_Troy said:
When you set up a lock screen PIN / pattern / password, you are presented with an option to require a password when turning on the device. If you say no to this option, your device is encrypted using "default_password" as the password.
Click to expand...
Click to collapse

RojoNinja said:
Give this a shot?
Click to expand...
Click to collapse
I tired both a pin/default_password. Neither seems to work.
Do I need to format userdata to decrypt?

Your device is likely encrypted and TWRP can't read the contents of your SD card unless you format /userdata first. This will wipe everything on your phone. The nexus 6P rooting guide will explain this in detail. I'd link it here but I'm new on here and I don't really know how. Look in the Nexus 6P general section. It should be stickied at the top.
Here's the link to the rooting guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

What happens if you boot up and set a password? Does that password work for TWRP?

Cares said:
What happens if you boot up and set a password? Does that password work for TWRP?
Click to expand...
Click to collapse
I flashed the stock image and redid the process.
I booted the phone and did not set any password/pin/fingerprint/etc. No security. Then I redid the boot.img, recovery.
I was then able to reboot into TWRP without the password prompt. Flashed systemless SuperSU and rebooted.
Now I'm stuck in the Google loading screen and has been there for a while. Looks like maybe it's not liking the new boot.img?

exSD said:
I flashed the stock image and redid the process.
I booted the phone and did not set any password/pin/fingerprint/etc. No security. Then I redid the boot.img, recovery.
I was then able to reboot into TWRP without the password prompt. Flashed systemless SuperSU and rebooted.
Now I'm stuck in the Google loading screen and has been there for a while. Looks like maybe it's not liking the new boot.img?
Click to expand...
Click to collapse
You're likely not on the latest build, so you'll have to use the images on Google to put yourself on the MDB08K (or higher) build before proceeding with the modified boot img (unless your devices can get the OTA). Many of the devices shipped with MDA89D out of the box.

Kusanagi Fire said:
You're likely not on the latest build, so you'll have to use the images on Google to put yourself on the MDB08K (or higher) build before proceeding with the modified boot img (unless your devices can get the OTA). Many of the devices shipped with MDA89D out of the box.
Click to expand...
Click to collapse
Is D or K the latest?

exSD said:
Is D or K the latest?
Click to expand...
Click to collapse
Latest is M. Modified boot was created based on K, but I believe has no problems working on M.

Kusanagi Fire said:
Latest is M. Modified boot was created based on K, but I believe has no problems working on M.
Click to expand...
Click to collapse
For some reason I thought D was the latest and flashed that. I'll upgrade to M and use the modified K boot.img.
That should clear it all up. Thanks for your help bud. I appreciate it. Let me know if I can ever help you sometime.

exSD said:
For some reason I thought D was the latest and flashed that. I'll upgrade to M and use the modified K boot.img.
That should clear it all up. Thanks for your help bud. I appreciate it. Let me know if I can ever help you sometime.
Click to expand...
Click to collapse
No worries. Happy to help. I had this problem when trying to root my phone, as well. It happens to the best of us. Hope that clears everything up for you and you're able to enjoy this beauty.

Is this normal for TWRP to ask for a password if you have pattern password turned on. So do I need to turn off all of my security before flashing TWRP 2.8.7.1
Right now my bootloader is unlocked, M6.0 all stock. I’ve been waiting for the source code to be release by Google so we can get a official root SU

boxcar8028 said:
Is this normal for TWRP to ask for a password if you have pattern password turned on. So do I need to turn off all of my security before flashing TWRP 2.8.7.1
Right now my bootloader is unlocked, M6.0 all stock. I’ve been waiting for the source code to be release by Google so we can get a official root SU
Click to expand...
Click to collapse
I'm not sure how TWRP would handle the pattern password. You can flash TWRP 2.8.7.1 and give it a shot. If it doesn't work, just download the stock image and extract the recovery.img from it and flash it back to stock.

Kusanagi Fire said:
No worries. Happy to help. I had this problem when trying to root my phone, as well. It happens to the best of us. Hope that clears everything up for you and you're able to enjoy this beauty.
Click to expand...
Click to collapse
Hey, FYI, that was my issue. Flashed the M image, then the K systemless root boot.img and all is working well now. No password prompt on latest TWRP either.

Resetting the pin worked for me
was having the same problem on Nexus 6P- had previously TWRP/rooted with no problem, don't remember being asked for a password.
After flashing recovery/radio/ROM back to stock and then later deciding to root again ran into this.
Android was still booting up OK so just set a new pin in Settings-->Security-->ScreenLock and selected the require PIN to start option. This PIN then worked as the password in TWRP to decrypt.

I was having the same issue with TWRP 2.8.7.2, I decided to flash TWRP 3.0.0.1 and I did not get prompted for the password. Not sure if this a true solution so at some point I may just decrypt data.

From another forum, This worked for me and couple of other people too
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.

rdskhalsa said:
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
Click to expand...
Click to collapse
Tnx mate, your method worked like a charm for me.

I think I'm having a twist on this problem.
After using Lineage for a while I tried another rom (carbon) which I now think has encrypted my data. I tried going back to lineage but now I cannot access my data, nor the backups I made for both Lineage and Carbon.
I think that if I can put the backup of carbon back I should also have my files back. But with and encrypted file system I can not get back to Carbon.
I think I did set "ask for password at boot" in Lineage but I took off the pattern+ finger prints before making the backup and I did not set pattern or fingerprint after installing carbon.
Is there a way to get back to carbon?

Your data is no longer accessible. Once your storage has been encrypted, the only way to un-encrypt is to flash a full stock Google image, and then do a factory reset from the stock recovery. If you had any backups on PC, you could then restore them and be back in business. This USUALLY only happens to you one time and you never forget. Think of it as a housecleaning day.

[Guide] How to install June Security Update via Image and retain Data (plus Root)

Since the May Security Update, there have been changes.
I won't get into that here, as there are already a number of threads where the new AVB process and what it means for updates and root is discussed at length on this forum.
For example - https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
I'm just going to outline my process for installing the new security updates via full image (Not OTA) and then rooting the phone via TWRP.
A few things to bear in mind first.
You will need to have the following:
0. Know how to use ADB/Fastboot and have them installed. If not, you should please do some research first.
1. Full Image for Pixel (https://developers.google.com/android/ota)
2. TWRP boot image and zip files (https://dl.twrp.me/sailfish/)
3. Latest SuperSU by Chainfire (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip)
4. VerifiedBootSigner by Chainfire (https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606)
Also...I don't make use of the vendor provided flashing scripts, I simply use the script commands and eliminate the '-w' flag manually.
*The SuperSu, TWRP and VerifiedBootSigner zips need to be saved to your phone*
From the bootloader ->
fastboot flash bootloader bootloader-sailfish-8996-012001-1704121145.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot update image-sailfish-njh47b.zip
***The phone will automatically reboot at this phase and you will need to reboot back into the bootloader to continue either by manual means or by using "adb reboot-bootoader"
fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
from TWRP (using files saved on phone) ->
TWRP install twrp-pixel-installer-sailfish-3.1.0-0RC2.zip
reboot TWRP
TWRP install SR3-SuperSU-v2.79-SR3-20170114223742.zip
TWRP install VerifiedBootSigner-v8.zip
reboot system
Edit - You should also update your SuperSU binary to 2.82 from within the app once you're booted into Android.
You're Done!
DISCLAIMER
I didn't create any of these files or take credit for them in anyway. This is simply an instructional that I hope will help many of you.
It requires some proficiency in using fastboot and TWRP.
If you don't know what you're doing and mess up your device, I take no responsibility for your actions or the results.

gonna give it a try, thanks dude.

The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.

churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.

churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
phonepersonality said:
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
Click to expand...
Click to collapse
fastboot has an option to skip reboot:
--skip-reboot
so the command would be something like: fastboot --skip-reboot update image-sailfish-njh47b.zip

Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know

TENN3R said:
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
Click to expand...
Click to collapse
If you'd like.
I don't like to use the OTA files, personally.

Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.

mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.

Tulsadiver said:
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Click to expand...
Click to collapse
I did manual fastboot commands earlier, not the autoscript, automatically wiped my data.
---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------
Not sure what happened. Just pretty much treated like a dirty flash and fastboot flash the image. It must have detected the prior and wiped it. Had the thing rooted which is the only thing I can think of, it was not untouched stock.

mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.

Did anyone else have to install the TWRP 3.1 zip via USB-OTG? After flashing the full factory image for June 2017, rebooting to system, rebooting to bootloader then running fastboot boot twrp3.0.2-RC1.img, I wasn't prompted to enter my password so my user data remained encrypted and I couldn't install the TWRP 3.1 zip from the internal SD card, had to load it on a usb dongle and mount USB-OTG storage.

TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Click to expand...
Click to collapse
I've tried to take out the -w erase flag. I've also tried to reflash the stock boot in the past when reloading a new kernel. Not sure if it is triggering some kind of system default but it just auto wipes. It's not the end of the world, I have everything backed up, I just have to restore everything. Just have not had any luck

Guys I can confirm also sideload ota method works flawlessly, 7.1.2 june rooted

Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?

Coronado is dead said:
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Click to expand...
Click to collapse
A phone setup according to this thread is not expected to pass the Safetynet check. I've been updating with SuperSU using FlashFire, and my phone just shows Netflix VR in the Play Store. The Magisk discussions are primarily the threads that have been active recently for having root and passing Safetynet.
Pixel discussion:
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845
Pixel XL discussion:
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347

TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp.
Click to expand...
Click to collapse
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot

Flitskikker said:
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Click to expand...
Click to collapse
I use the same method I don't think there are any others

TENN3R said:
I use the same method I don't think there are any others
Click to expand...
Click to collapse
Thanks for confirming.

Does this VerifiedBootSigner-v8.zip apply to the August security patch as well?

Essential Phone /sdcard How to Decrypt?

Today, I decided to root my Essential PH-1 on Android 9.0 Pie. I did the downloading, and fastboot the correct way, but when I open TWRP, it says to enter the password to decrypt /sdcard. I never set a password. i tried to just exit out of it, but I am now stuck in the Boot/Reboot loop. Any help would be greatly appreciated

I realized that I forgot to take off my lock screen password, but it was set as fingerprint and pattern if that helps

CarLover014 said:
I realized that I forgot to take off my lock screen password, but it was set as fingerprint and pattern if that helps
Click to expand...
Click to collapse
Next time just put the files needed for flashing in the Data folder in internal storage. It's not encrypted (scratch that, you need root to access it). To get out of your bootloop just reboot to bootloader and reflash a stock image so you can get back to the OS and remove all security so you can access them in sdcard directory.

Okay, but I cant read the files because its all random letters and numbers

CarLover014 said:
Okay, but I cant read the files because its all random letters and numbers
Click to expand...
Click to collapse
Right. Which is why you need to get back to the OS. Get a stock image of your current version and flash it from bootloader. Before flashing, remove the "-w" from the flashall batch file and save it. This will preserve your user data.
It might also be possible to just reflash the stock boot.img also. Someone else can chime in on that.

In the essential flash all.bat it's the "format user data" line you need to remove before saving the file and then running it.

You all are going to have to be much more specific. Like a step by step

Like a guide? https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976

Hey, I got it. I had to sideload

I only got Oreo Now. I can't install the Android Pie .img using TWRP. Anybody have the Stock OTA?

CarLover014 said:
I only got Oreo Now. I can't install the Android Pie .img using TWRP. Anybody have the Stock OTA?
Click to expand...
Click to collapse
You should only be flashing the boot.img for the current build you are in.
If you're currently running Oreo, then you need to use the Oreo boot.img that corresponds to the one on your phone.

The OTA and full download are both on the essential website (with checksums)

twrp gets erased

Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you

Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.

As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.

Or you can just root it and twrp won't erase with stock recover.

naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine

[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.

ahhh, ok I see. Thanks for the explanation.