Related
I am creating this thread keeping in my mind the several posts in various threads mentioning that they have accidentally triggered the DM-Verity flag and have an annoying message during startup or due to force encryption in the boot image the phone went back to encrypted state after flashing a new Stock Oxygen OS zip file in TWRP recovery.
So I decided to start a thread where I will post the links to the OFFICIAL BOOT IMAGES of Oxygen OS ROMs for both OnePlus3 and OnePlus3T which have been patched to disable the DM-Verity Flag and to disable the Force encryption that is present in the Stock Oxygen OS ROM.
NB: This thread is only for Nougat Based OOS ROMs. For disabling Dm-Verity and force Encryption in PIE OOS ROMs refer to my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324. For Disabling DM-Verity in Oreo Based OOS ROMs visit my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
THIS IS FOR BOTH ONEPLUS 3 and 3T and read the instructions carefully and apply the file specific for your model
Disclaimer: I am not responsible for any damage to your phone by using this...
Nothing has been changed....
It is 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Links:
For ONEPLUS 3T
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/vm2k81s3pregdiv/boot-patched-4.5.1-OP3T.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/m8e3nu4ak4u1zkz/boot-patched-4.5.0-OP3T.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/g5rk4284lzyvqnu/boot-patched-4.1.7-OP3T.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/j3802c259gea6f2/boot-patched-4.1.6-OP3T.img[/URL]
Patched Boot Image Stable OOS 4.1.5
[url]http://www.mediafire.com/file/78ej52gmthok212/boot-patched-OOS4.1.5.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 15
http://www.mediafire.com/file/a436larx3ddx00l/boot-patched-Beta15-OP3T.img
Patched Boot Image OOS Beta 14
http://www.mediafire.com/file/brlvdth86lxi0yl/boot-patched-Beta14-OP3T.img
Patched Boot Image OOS Beta 13
http://www.mediafire.com/file/2clnhl0x4vu8bu8/boot-patched-Beta13-OP3T.img
Patched Boot Image OOS Beta 12
http://www.mediafire.com/file/2214mr1adpdwlx4/boot-patched-Beta12-OP3T.img
Patched Boot Image OOS Beta 11
http://www.mediafire.com/file/hywcwmv0a993ah5/boot-patched-Beta11-OP3T.img
Patched Boot Image OOS Beta 10
http://www.mediafire.com/file/n7nu0wj266e8fhh/boot-patched-Beta10-OP3T.img
Patched Boot Image OOS Beta 9
[url]http://www.mediafire.com/file/5lkp6fi33u9lkpt/boot-patched-Beta9-OP3T.img[/URL]
Patched Boot Image OOS Beta 8
[url]http://www.mediafire.com/file/4d5zrpff4jakjgk/boot-patched-OOS_Beta_8.img[/URL]
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/srdurw9pg4f614f/boot-patched-4.5.1-OP3.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/nrbuddj0652bf4u/boot-patched-4.5.0-OP3.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/2cb3jrqckb4suxw/boot-patched-4.1.7-OP3.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/ytax9vfa9lyhd6d/boot-patched-4.1.6-OP3.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 24
http://www.mediafire.com/file/8fcbeiduhiewc9v/boot-patched-Beta24-OP3.img
Patched Boot Image OOS Beta 23
http://www.mediafire.com/file/9i3snrmmsinczct/boot-patched-Beta23-OP3.img
Patched Boot Image OOS Beta 22
http://www.mediafire.com/file/bauq66z2s6o2k1q/boot-patched-Beta22-OP3.img
Patched Boot Image OOS Beta 21
http://www.mediafire.com/file/r31feak94y3cm5z/boot-patched-Beta21-OP3.img
Patched Boot Image OOS Beta 20
http://www.mediafire.com/file/5h32hzw5ot1gbba/boot-patched-Beta20-OP3.img
Patched Boot Image OOS Beta 19
http://www.mediafire.com/file/y6446j7sxiw9jwx/boot-patched-Beta19-OP3.img
Patched Boot Image OOS Beta 18
http://www.mediafire.com/file/zfsji9mjjds7a6n/boot-patched-Beta18-OP3.img
Patched Boot Image OOS Beta 17
[url]http://www.mediafire.com/file/mrqhkq7igt7x4na/boot-patched-Beta17-OP3.img[/URL]
USAGE FOR STOCK OOS:
# Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)
# Restart back to TWRP Recovery.
# Done.
# Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual
# You dont have to worry about triggering DM-Verity or Getting Force Encrypted again...
VERY IMPORTANT: FOR PEOPLE WHO HAVE ALREADY TRIGGERED DM-VERITY ON THEIR OOS OR CUSTOM ROM AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY, READ MY POST 2. AFTER GETTING RID OF DM-VERITY BY FOLLOWING THE STEPS IN POST 2, NEXT TIME ONWARDS WHILE UPDATING YOUR OOS OR CUSTOM ROM FOLLOW THE INSTRUCTIONS IN THIS OP TO KEEP YOUR OOS AND PHONE FREE FROM THE TROUBLE OF DM-VERITY AND FORCE ENCRYPTION...
FAQs:
Q: Is the boot.img file altered in anyway?
A: As mentioned above its 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Q: My phone is already encrypted, will I lose encryption?
A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..
Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose data/apps accidentally while updating OOS after I lose TWRP ...Can this be corrected by using this method?
A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..
Q: I am Rooting my phone using Magisk/Supersu then why do i need this?
A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..
Q: How to flash the patched boot.img in TWRP?
A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.
Q: Can I use it for CUSTOM ROMs? / What to do while updating CUSTOM ROMs?
A: For hassle free and the best results whenever you update CUSTOM ROMs always do it this way...
The below steps are for CUSTOM ROMs only. (For STOCK ROMs follow the main step mentioned above in the section USAGE)...
1.Go to TWRP
2.Flash the required firmware zip file
3.Flash the corresponding patched boot IMG
4.Flash the ROM whether LINEAGE, RR, ASOP, etc.
5.Flash gapps
6.Flash root (magisk /su)
7.Flash kernel
8.At last Reboot...
There will not be any problem ever...
You can reboot after step 5
Steps 6,7 are optional
Q: What is "-Xn" seen after the OOS Version in the settings menu?
A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity and forced encryption..
Hope you find it useful...
Will update as newer OOS versions come....
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS OR OPEN BETA OR CUSTOM ROM. CONFIRMED WORKING EVEN IN THE LATEST OOS 4.5.1/BETA Nougat Roms...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
10) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
11) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT: If you are attempting this method on a a CUSTOM ROM then after Step 10 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
Thanks mate..... You made my day..... Working perfectly.
Nice to see this thread on the day of release of oos 4.1.5 itself.
Deleted..
So well explained and working perfectly
One if the most detail step by step explanation
Thanks dev.
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
MohamedRaafat said:
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
Click to expand...
Click to collapse
Do the second method only if you trigger DM Verity while installing 4.1.5
To be sure you don't trigger DM Verity while installing 4.1.5 follow the instructions in the OP...
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
prorokrak said:
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
Click to expand...
Click to collapse
I have been thinking about it for the past few days...
Anyways I thought as no one asked they were not interested in getting the patched boot images for op3...
Ok.. they have released OOS 4.1.6..
So will push the links for the patched boot images for both op3 and op3T tomorrow after I test and get hands on the flashable ROMs.
The OP has been updated to accomodate both ONEPLUS 3T and ONEPLUS 3
Now this thread can be used for both models and will be updated as new OOS version come..
Enjoy!!!
NEW UPDATE RELEASED!!!
Links in OP...
Oxygen OOS 4.1.6 patched boot images for ONEPLUS 3T and ONEPLUS 3...
Thenks for this!
sparky vicky said:
How did you flashed the bootimg? through twrp? it's asking for 3 options like boot, recovery,system? im confused
Click to expand...
Click to collapse
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Xennet said:
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Click to expand...
Click to collapse
Yes i choose boot but still the warning showing on boot
sparky vicky said:
Yes i choose boot but still the warning showing on boot
Click to expand...
Click to collapse
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Im on OP3T, OOS 4.1.6
sparky vicky said:
Im on OP3T, OOS 4.1.6
Click to expand...
Click to collapse
Which is the warning being shown and explain the steps you did
Xennet said:
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Click to expand...
Click to collapse
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
Xennet said:
Which is the warning being shown and explain the steps you did
Click to expand...
Click to collapse
Flashed 4.1.6 with twrp at same time without reboot flashed bootpatch and rebooted to system and still the dm verity showung
Did i collapsed the procedure?:silly:
sparky vicky said:
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
Click to expand...
Click to collapse
Mate do read the second post in the OP...
For getting rid of the DM-Verity message..
The first OP post is only for those who have no DM Verity warning on their phone..
If you already have DM Verity warning on your phone you have to follow the second post..it is clearly mentioned in the OP.. AND WRITTEN IN BOLD LETTERS..
Once you get rid of the DM Verity warning from next time onwards you have to follow only the instructions in the first OP post..
Oneplus has released the Stable and Beta OREO Oxygen OS for Oneplus 3T and 3.
This thread is only for OOS Oreo. For disabling Dm-Verity and force Encryption in PIE OOS ROMs refer to my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324. For disabling Dm-Verity and force Encryption in NOUGAT OOS ROMs refer to my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232[/I]
Disclaimer: I am not responsible for any damage or data loss that happens to your device on embarking this procedure...
THE DETAILS....
There has been some modifications that i came across after unpacking and verifying the packages..
After extracting the ramdisk to my surprise there was no fstab file and hence no fstab entries that could be modified to disable Dm-Verity and Force encryption...
After tweaking a little i found that indeed the file fstab does exist but its not in the ramdisk but in an other location..
So i disabled the Dm-Verity and Force encryption entries in the fstab file in the new location and made a flashable zip file which will replace the original fstab file.
As @rk2612 pointed out the fact that indeed the system entries are hashed out in the fstab file and the kernel takes care of the system loading procedure in OREO, I have been working on it. Indeed it is true. After unpacking the boot image into kernel, ramdisk and device tree blobs (dtbs), I came accross 12 entries in the dtb that reference directly to mount the system after triggering the DM-Verity flag. So I patched the dtb binary to clear off the DM-Verity flags and repacked the Boot images. Moreover, in OREO as long as DM-Verity is triggered, any changes made to the system are reverted back once you boot to system which has been clearly stated with the help of posts from @BillGoss.
The other fact is that regarding force encryption, it indeed is taken care of only in the fstab.
So in a nut shell, to disable DM-Verity you will need to flash the patched Boot Images and to disable force encryption you will have to flash the force encryption disabler zip - The links of which are provided below. Do refer to the correct procedure explained in datail before attempting to do anything...
For all those who need an in-depth reading of the nature of patching the fstab in dtb file and my work you can refer here:
https://forum.xda-developers.com/showpost.php?p=74326761&postcount=3
THIS METHOD WILL WORK FOR BOTH ONEPLUS 3 T AND ONEPLUS 3...
TESTED AND WORKING TILL ONEPLUS 3/3T STABLE OOS 5.0.8 / ONEPLUS 3T BETA 30 / ONEPLUS 3 BETA 39..
FOR THOSE WHO HAVE ALREADY TRIGGERED DM-VERITY ON OOS OREO FOLLOW THE STEPS IN POST 2 IN THIS THREAD TO GET RID OF DM-VERITY BEFORE PROCEEDING...
Nothing has been changed....
It is 100% stock boot image except that the DM-Verity Flag has been patched...
Links:
For ONEPLUS 3T
STABLE OOS Boot Images
Patched Boot Image Stable OOS 5.0.8
http://www.mediafire.com/file/xcsiuizziw6xckq/boot-patched-5.0.8-OP3T.img/file
Patched Boot Image Stable OOS 5.0.7
http://www.mediafire.com/file/ckn0012znn8kw8c/boot-patched-5.0.7-OP3T.img/file
Patched Boot Image Stable OOS 5.0.6
http://www.mediafire.com/file/ma4plv5vtom4ih1/boot-patched-5.0.6-OP3T.img/file
Patched Boot Image Stable OOS 5.0.5
http://www.mediafire.com/file/adxxd99bgswez8d/boot-patched-5.0.5-OP3T.img/file
Patched Boot Image Stable OOS 5.0.4
http://www.mediafire.com/file/c8ftkmwqebmrer3/boot-patched-5.0.4-OP3T.img
Patched Boot Image Stable OOS 5.0.3
http://www.mediafire.com/file/z1kut18fycm2k57/boot-patched-5.0.3-OP3T.img/file
Patched Boot Image Stable OOS 5.0.2
http://www.mediafire.com/file/hu6n544a8yhpmma/boot-patched-5.0.2-OP3T.img
Patched Boot Image Stable OOS 5.0.1
http://www.mediafire.com/file/cjxs6plcngqc5g6/boot-patched-5.0.1-OP3T.img
Patched Boot Image Stable OOS 5.0
http://www.mediafire.com/file/dxxgn7i49sxbca1/boot-patched-5.0-OP3T.img
BETA OOS Boot Images
Patched Boot Image OOS Beta 30
http://www.mediafire.com/file/b3fu93f15zd576c/boot-patched-Beta30-OP3T.img/file
Patched Boot Image OOS Beta 29
http://www.mediafire.com/file/w80wj3lql256td3/boot-patched-Beta29-OP3T.img/file
Patched Boot Image OOS Beta 28
http://www.mediafire.com/file/k3fj0u71t85jo8q/boot-patched-Beta28-OP3T.img/file
Patched Boot Image OOS Beta 27
http://www.mediafire.com/file/d1m6awl8oda5087/boot-patched-Beta27-OP3T.img
Patched Boot Image OOS Beta 26
http://www.mediafire.com/file/6c832j5y5hwk68t/boot-patched-Beta26-OP3T.img
Patched Boot Image OOS Beta 25
http://www.mediafire.com/file/6h1h1cammycdu9f/boot-patched-Beta25-OP3T.img
Patched Boot Image OOS Beta 24
http://www.mediafire.com/file/s8q750qedda5c2n/boot-patched-Beta24-OP3T.img
Patched Boot Image OOS Beta 23
http://www.mediafire.com/file/a9r6o20qc865bij/boot-patched-Beta23-OP3T.img
Patched Boot Image OOS Beta 22
http://www.mediafire.com/file/kk5llc6s43kr2bb/boot-patched-Beta22-OP3T.img
Patched Boot Image OOS Beta 21
http://www.mediafire.com/file/di3nm7ci7fn1u6i/boot-patched-Beta21-OP3T.img
Patched Boot Image OOS Beta 20
http://www.mediafire.com/file/woow4q1enart2tf/boot-patched-Beta20-OP3T.img
Patched Boot Image OOS Beta 19
http://www.mediafire.com/file/vqud6vy7k61stzt/boot-patched-Beta19-OP3T.img
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 5.0.8
http://www.mediafire.com/file/6i5yblsbx7rdiba/boot-patched-5.0.8-OP3.img/file
Patched Boot Image Stable OOS 5.0.7
http://www.mediafire.com/file/1xo7e9qr521s9z9/boot-patched-5.0.7-OP3.img/file
Patched Boot Image Stable OOS 5.0.6
http://www.mediafire.com/file/98nyyirwfy2mo9e/boot-patched-5.0.6-OP3.img/file
Patched Boot Image Stable OOS 5.0.5
http://www.mediafire.com/file/12bhw4bo48lrp8o/boot-patched-5.0.5-OP3.img/file
Patched Boot Image Stable OOS 5.0.4
http://www.mediafire.com/file/io7hqnwoiy0i9v5/boot-patched-5.0.4-OP3.img/file
Patched Boot Image Stable OOS 5.0.3
http://www.mediafire.com/file/vdeq5iox0700rou/boot-patched-5.0.3-OP3.img/file
Patched Boot Image Stable OOS 5.0.1
http://www.mediafire.com/file/e1ae6d7ae45571r/boot-patched-5.0.1-OP3.img
Patched Boot Image Stable OOS 5.0
http://www.mediafire.com/file/a69c69gw6gkj860/boot-patched-5.0-OP3.img
BETA OOS Boot Images
Patched Boot Image OOS Beta 39
http://www.mediafire.com/file/3rc3t0zc543oqf7/boot-patched-Beta39-OP3.img/file
Patched Boot Image OOS Beta 38
http://www.mediafire.com/file/6ef5szt65605woh/boot-patched-Beta38-OP3.img/file
Patched Boot Image OOS Beta 37
http://www.mediafire.com/file/856w586ctt39rg8/boot-patched-Beta37-OP3.img/file
Patched Boot Image OOS Beta 36
http://www.mediafire.com/file/2l6mj266z15vbbq/boot-patched-Beta36-OP3.img
Patched Boot Image OOS Beta 35
http://www.mediafire.com/file/cguelk95o3klcki/boot-patched-Beta35-OP3.img
Patched Boot Image OOS Beta 34
http://www.mediafire.com/file/r1sd37135f3d90u/boot-patched-Beta34-OP3.img
Patched Boot Image OOS Beta 33
http://www.mediafire.com/file/vmey23ggvafw2ps/boot-patched-Beta33-OP3.img
Patched Boot Image OOS Beta 32
http://www.mediafire.com/file/7m6gxldmenen2qs/boot-patched-Beta32-OP3.img
Patched Boot Image OOS Beta 31
http://www.mediafire.com/file/2150f2hnaclc1zk/boot-patched-Beta31-OP3.img
Patched Boot Image OOS Beta 30
http://www.mediafire.com/file/5x1bcyxzihscdj3/boot-patched-Beta30-OP3.img
Patched Boot Image OOS Beta 29
http://www.mediafire.com/file/v1cm7ddtmr6tnam/boot-patched-Beta29-OP3.img
Patched Boot Image OOS Beta 28
http://www.mediafire.com/file/1afm13h8ax9d3r0/boot-patched-Beta28-OP3.img
STEPS: This is applicable only to people who have their data currently ENCRYPTED and needs the procedure only for NOT TRIGGERING DM-VERITY
USAGE FOR STOCK OOS:
1. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)
2. Restart back to TWRP Recovery.
3. Done.
4. Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual
5. You dont have to worry about triggering DM-Verity again and any changes made to system via TWRP will not be reverted back..
The 2 Prodeures given below: This is applicable only to those people who needs the procedure for getting rid of FORCE ENCRYPTION AND PREVENT TRIGGERING DM-VERITY
PROCEDURE 1: This is applicable only to people who have their data currently NOT ENCRYPTED AND KEEP IT DECRYPTED
First of all Backup your data preferably to and usb otg or a PC for later restore. You may lose your data from your phone following this procedure...
1. Format SYSTEM, DALVIK, CACHE and then only Flash the Full Rom Oreo Beta OOS zip file in TWRP.
2. DON'T REBOOT
3. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.
4. DON'T REBOOT TO SYSTEM
5. REBOOT TO TWRP.
6. In TWRP, MOUNT SYSTEM, GO TO ADVANCED > TERMINAL and Type "df system"(without quotes) and enter. The details of the system partition will be shown. Look at the Use% and Free Space. Make sure you have atleast 100MB free space in System before you go to the next step. If you don't have enough free space then mount system in TWRP, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps)...If there is low space on your system partition that fstab file flashing fails resulting in blank fstab file and you will end up in bootloop.
7. Once you have confirmed that you have atleast 100MB of free space left in system partition. REBOOT BACK TO TWRP.
8. Flash "Force Encryption Disabler For OOS Oreo v2.zip" in TWRP. (No need to mount system. The v2 zip file does it automatically)
9. Flash SuperSuSR5 / Magisk 15.3+
10. Done.
11. Reboot to System.
NB:f you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file. But if you followed Steps 6 and 7 carefully you wont end up here.
PROCEDURE 2: This is applicable only to people who have their data currently ENCRYPTED AND NEEDS TO GET IT DECRYPTED and PREVENT TRIGGERING DM-VERITY
First of all Backup your data preferably to and usb otg or a PC for later restore. You will lose your data from your phone following this procedure...
1. Go to Bootloader...
2. Connect to your PC..Type "fastboot format userdata" without quotes and press enter. (You will lose your data, do back up if you need something.)
3. Don't reboot to system...Using volume buttons select boot to recovery and Reboot to TWRP.....(Very Important)
4. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.
5. DON'T REBOOT TO SYSTEM
6. REBOOT TO TWRP
7. In TWRP, MOUNT SYSTEM, GO TO ADVANCED > TERMINAL and Type "df system"(without quotes) and enter. The details of the system partition will be shown. Look at the Use% and Free Space. Make sure you have atleast 100MB free space in System before you go to the next step. If you don't have enough free space then mount system in TWRP, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps)...If there is low space on your system partition that fstab file flashing fails resulting in blank fstab file and you will end up in bootloop.
8. Once you have confirmed that you have atleast 100MB of free space left in system partition. REBOOT BACK TO TWRP.
9. Flash "Force Encryption Disabler For OOS Oreo v2.zip" in TWRP. (No need to mount system. The v2 zip file does it automatically)
10. Flash SuperSuSR5 / Magisk 15.3+
11. Done.
12. Reboot to System.
NB: If you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file. But if you followed Steps 7 and 8 carefully you won't end up here.
Rooting:
For Rooting use only SuperSu 2.82 SR5 or Magisk 14.3 or above seems to work for root...
FAQs:
Q: Is the boot.img file altered in anyway?
A: As mentioned above its 100% stock boot image except that the DM-Verity Flag has been patched in the device tree blobs (dtb)...
Q: My phone is already encrypted, will I lose encryption on flashing the zip?
A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..
Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose changes made to system via TWRP or lose data/apps accidentally while updating OOS...Can this be corrected by using this method?
A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..
Q: I am Rooting my phone using Magisk/Supersu then why do i need this?
A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..
Q: How to flash the patched boot.img in TWRP?
A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.
Q: What is "-Xn" seen after the OOS Version in the settings menu?
A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity...
Q: Where to find downloads and queries regarding the Stock OOS ROM and Beta OOS?
A: @Siddk007 has been maintaining Stock and Beta OOS threads were you can find relevant information.
Hope you find it useful...
Will update this OP as newer OOS versions come....
Thanks,
@rk2612 -- For pointing out the presence of DM-Verity checks in dtbs...
@BillGoss -- For testing out the patched boot images and providing useful posts mentioning that DM-Verity triggering reverts changes made to system...
@akhilnarang -- For helping tackle the weirdness of fstab decryption....as he pointed out the fact of clearing the system of free space to get it done...
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
AND IF YOU DO APPRECIATE MY WORK DONATIONS ARE ALWAYS WELCOME...
THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS OPEN BETA OREO ROMs. CONFIRMED WORKING EVEN IN THE LATEST OOS OREO STABLE 5.0.8/ BETA 30/BETA 39...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
READ ALL THE STEPS AND DOWNLOAD ALL REQUIRED FILES BEFORE PROCEEDING. FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for Stable or Open Beta OREO OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for Stable or Open Beta OREO OOS corresponding to your current OOS (current OOS is the version of OREO OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
12) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
13) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT:
1. If you need to keep your phone un-encrypted flash Force Encryption Disabler For OOS Oreo.zip immediately after step 12 and then only reboot.
2.If you are attempting this method on a a CUSTOM ROM then after Step 12 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
Knowledge is always good and Xda is the best place to share it.. So here it is...
This is important for those interested in depth reading and for those who casually use xda to just download and use stuff because it gonna affect you all...
It all begins with the boot.img file which is located inside the Oxygen OS ROM zip file. The Boot image file can be practically for learning purpose be broken down to ramdisk, kernel and dtb(device tree blob) files.
The importance of all this is that from Oreo onwards Oneplus just shifted the fstab entry(in which the code triggering dm-verity is located) into the dtb file rather than in the ramdisk which becomes a little hard to edit rather than while being in the ramdisk.
So the essential steps being unpacking dtb file from the boot image, then editing the code triggering the dm-verity in the dtb file and then repacking the dtb into the boot image file again. Seems simple but its rather difficult...
The dtb file extracted from the boot image file in fact can be further split into 13 dtb dumps, 12 of which having an fstab entry that triggers dm-verity and each has to patched individually and then combined to a single dtb file and then repacked to the boot image....
So what is important is...
The original code in dtb file by Oneplus in the boot image file after decompiling and analysing by the dtc(device tree compiler) is :
Code:
fstab {
compatible = "android,fstab";
system {
compatible = "android,system";
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = "wait,verify";
status = "ok";
};
};
The line fsmgr_flags = "wait,verify"; should be changed to fsmgr_flags = "wait" to avoid triggering dm verity.
So lets see...
What Magisk does... After analysing the patched boot image by magisk 14.5, 14.6 and 15.0 the Fstab entry in the dtb file looks like this:
Code:
fstab {
compatible = "android,fstab";
system {
compatible = "android,system";
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = <0x77616974 0x0 0x0>;
status = "ok";
};
};
The problem is that magisk searches for the hex code for --->,verify and then replaces it with zero bytes....that efficiently disables the dm verity check in fs tab but the line fsmgr_flags = <0x77616974 0x0 0x0>; makes no sense...but when you translate the hex:77616974 to ASCII it becomes "wait". But whether this has any impilcations on the system or performance. I just simply dont know....
And I just couldn't analyse the dtb file produced by Magisk 15.1 as it fails to patch the dtb file in the boot image completely...just giving an error as Segmentation fault...This is well noticed as you cannot see the line stating that patching fstab in dtb file is conspicuously absent when you flash Magisk 15.1.. and hence Magisk 15.1 fails to clear the dm verity flag in the boot image...This can be ascertained by many who reported that they triggered dm verity today as they flashed Magisk 15.1 after flashing the ROM zip file in the Open Beta thread for oneplus 3T on XDA. But many didn't notice it as they just flashed Magisk 15/14.6 and then upgraded Magisk to 15.1 as the earlier versions as stated above took care of dm verity...
I have to say Magisk is one of the wonders in modern day android era and the statements i have given above is just observations and are really not meant to degrade or hurt the dev or anyone associated with magisk. @topjohnwu will already be knowing the issue as he is one hell of a developer and will definitely be correcting it...
Coming to SuperSu..This is what SuperSu does after patching the dtb file...
Code:
fstab {
compatible = "android,fstab";
system {
fsmgr_flags = "wait";
mnt_flags = "ro,barrier=1,discard";
type = "ext4";
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
};
Now here the line fsmgr_flags = "wait"; is good but the line --->status = "ok"; is completely missing as SuperSu appends the line after the word "wait" in the fstab...And now whether this has any implications too whther I really dont know butit too does the job of removing dm-verity triggering...
Post a tiring study through all this I finally managed to patch the Oneplus boot image to as good as possible. I manually unpacked the boot image to dtb. The split the combined dtb to individual dtbs and the removed the line of code manually and the repacked the whole thing again to the original Boot image.
The dtb file in My Patched boot image looks like this after analysing with dtc.. And achieves the desired result...and perfectly avoids triggering dm-verity without causing any untoward effects in the fstab section in dtb file.
Code:
fstab {
compatible = "android,fstab";
system {
compatible = "android,system";
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = "wait";
status = "ok";
};
Now the real question,
What will happen if you flash my patched boot image and then ,
---> When you flash Magisk after flashing my patched boot image it does nothing because it fails to identify the hex code for ",verify" as there is no such word/hex code in my boot.img file so it doesn't change anything to the fstab section in the dtb file in my patched boot image and so there no untoward effects in the code...
--->When you flash SuperSu, but, it still appends the line after "wait" in the dtb file in my patched boot image too and results in removal of the line status = "ok";.
Earlier Boot images posted in the OP, I too patched the hexcodes using a hex editor in the binary dtb file resulting in results in fstab section of dtb file like Magisk...
Now on I will manually patch each boot image file to produce the fstab file with no other alterations done in the dtb file so that there will never be any problems after flashing the patched boot images....
@Xennet that was quick, thanks. However i have already flashed and booted OB 16. can i still flash?
Of Course..
No problems in that...
Did you trigger Dm Verity and is your phone encrypted?
Xennet said:
Of Course..
No problems in that...
Did you trigger Dm Verity and is your phone encrypted?
Click to expand...
Click to collapse
i successfully rooted OB 16 without trigerring DM Verity and yes phone is encryptyed
Siddk007 said:
i successfully rooted OB 16 without trigerring DM Verity and yes phone is encryptyed
Click to expand...
Click to collapse
No problems still you can flash...
Thanks !
Too late for me brothers, I've fallen, I triggered dm verity and now my phone partition was wiped and it won't let me install a ROM.
Still have access to fastboot and adb tho. (Restore not working due to the dm-verity)
I'll try to flash this and play around, hopefully it will resolve my issue.
Thanks for helping everyone anyway
EDIT : Ok so I think it allowed me to restore an old old old backup so probably props to you for giving my brick a second chance.
It stills shows me the "dm-verity not enforced" message when booting up tho.
And TWRP still won't let me install a ROM. Even the officiel beta
I get an error 7 saying my build.pro ro.product.series is " " instead of "OnePlus 3T" but I checked it's OnePlus 3T...
If I remove the update script part about checking my series it just fails to update system image.
This update really ****ed up my phone because of the dm-verity when I tried to flash TWRP and Magisk (I had no issue before and was full stock)
Can anyone help ?
I triggered dm verity with oreo rom but I went and installed backup PA Nougat as I didnt like the OOS Oreo, can I still flash this zip on nougat to disable dm verity or is it only for oreo?
Isus <3 said:
I triggered dm verity with oreo rom but I went and installed backup PA Nougat as I didnt like the OOS Oreo, can I still flash this zip on nougat to disable dm verity or is it only for oreo?
Click to expand...
Click to collapse
This is only for Oreo
For Nougat go to my thread here..
https://forum.xda-developers.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232
Hinoy said:
Too late for me brothers, I've fallen, I triggered dm verity and now my phone partition was wiped and it won't let me install a ROM.
Still have access to fastboot and adb tho. (Restore not working due to the dm-verity)
I'll try to flash this and play around, hopefully it will resolve my issue.
Thanks for helping everyone anyway
EDIT : Ok so I think it allowed me to restore an old old old backup so probably props to you for giving my brick a second chance.
It stills shows me the "dm-verity not enforced" message when booting up tho.
And TWRP still won't let me install a ROM. Even the officiel beta
I get an error 7 saying my build.pro ro.product.series is " " instead of "OnePlus 3T" but I checked it's OnePlus 3T...
If I remove the update script part about checking my series it just fails to update system image.
This update really ****ed up my phone because of the dm-verity when I tried to flash TWRP and Magisk (I had no issue before and was full stock)
Can anyone help ?
Click to expand...
Click to collapse
Install nougat ROM OOS 4.5.0 STABLE and remove DM verity by following instructions from my thread here...
https://forum.xda-developers.com/oneplus-3t/how-to/rom-dm-verity-force-encryption-disabled-t3618232
Then after removing DM verity if needed you can reflash Oreo beta zip after removing the first line in updater script and then immediately flashing the DM verity and force encryption disabled zip from this thread...
Can anyone confirm it works? (disabling forced encryption)
I had changed the flag in fstab manually (forceencrypt to encryptable), and I still got encrypted.
akhilnarang said:
Can anyone confirm it works? (disabling forced encryption)
I had changed the flag in fstab manually (forceencrypt to encryptable), and I still got encrypted.
Click to expand...
Click to collapse
At least for me I couldn't get it to not be encrypted. I've tried for a few hours and had no luck.
akhilnarang said:
Can anyone confirm it works? (disabling forced encryption)
I had changed the flag in fstab manually (forceencrypt to encryptable), and I still got encrypted.
Click to expand...
Click to collapse
Nope it does not. Mine started the encryption process as well.
[EDIT] correction; it does seem to work. Because the first boot took really long and the device ran hot, just like the first time when I did have encryption, I thought it was the case this time as well. Although I had to reflash the TWRP-recovery (it was replaced by stock) but it did not tell me /data was encrypted, so I think we're good!
Thank you Xennet!
Mr_Q said:
Nope it does not. Mine started the encryption process as well.
[EDIT] correction; it does seem to work. Because the first boot took really long and the device ran hot, just like the first time when I did have encryption, I thought it was the case this time as well. Although I had to reflash the TWRP-recovery (it was replaced by stock) but it did not tell me /data was encrypted, so I think we're good!
Thank you Xennet!
Click to expand...
Click to collapse
Hope you will not lose twrp if you had rebooted back to twrp before rebooting to system..
Can you confirm that the phone is not encrypted...
See the encryption status in settings, security..
Xennet said:
Hope you will not lose twrp if you had rebooted back to twrp before rebooting to system..
Can you confirm that the phone is not encrypted...
See the encryption status in settings, security..
Click to expand...
Click to collapse
I did boot TWRP -> TWRP, it become stock after I did a normal boot.
But the sad news is, it does state it's encrypted..
So I thought encryption always required a PIN or Pattern when accessing the phone and/or Recovery, am I wrong?
Mr_Q said:
I did boot TWRP -> TWRP, it become stock after I did a normal boot.
But the sad news is, it does state it's encrypted..
So I thought encryption always required a PIN or Pattern when accessing the phone and/or Recovery, am I wrong?
Click to expand...
Click to collapse
Just sent you a PM..
Check it...
Mr_Q said:
I did boot TWRP -> TWRP, it become stock after I did a normal boot.
But the sad news is, it does state it's encrypted..
So I thought encryption always required a PIN or Pattern when accessing the phone and/or Recovery, am I wrong?
Click to expand...
Click to collapse
Yup but that's right...
To access an encrypted phone data you need a pin in TWRP
Can you check in TWRP again and are you able to see your data and copy and move around files..
Xennet said:
Yup but that's right...
To access an encrypted phone data you need a pin in TWRP
Can you check in TWRP again and are you able to see your data and copy and move around files..
Click to expand...
Click to collapse
Yes I can, but I did notice something interesting in the logs of TWRP:
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
... done
Succesfully decrypted with default password.
So yes it's encrypted, but I don't have to enter any password...
Mr_Q said:
Yes I can, but I did notice something interesting in the logs of TWRP:
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
... done
Succesfully decrypted with default password.
So yes it's encrypted, but I don't have to enter any password...
Click to expand...
Click to collapse
You have not triggered DM verity I suppose??
So my zip file does protect from triggering DM verity but not force encryption that's weird...
Did you use any root methods..?
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
omino said:
The following process is what I have been successfully doing in the last year to keep my Moto G5 Plus on the most up-to-date stock ROM but rooted with Magisk.
The high level process for OTA update and rooting is different from the case where the phone has never been rooted and where the phone is already rooted with this method.
Requirements
1. Unlocked bootloader (https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133).
2. Fastboot tools installed on a PC (https://forum.xda-developers.com/showthread.php?t=2588979).
3. TWRP recovery for the Moto G5 Plus: twrp-3.2.1-0-potter.img (https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html).
4. TWRP recovery for the Moto G5 Plus: twrp-3.1.1-0-potter-decryptdata.img (https://forum.xda-developers.com/g5-plus/development/unofficial-twrp-3-1-0-0-moto-g5-plus-t3576575).
5. Magisk and Magisk Manager (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
6. Magisk Module - F2FS Loopback Bug Workaround: f2fs-loopback-bug-workaround-2018.1.31 (https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875)
7. Micro SD card installed in the Moto G5 Plus.
Items 3. and 4. may no longer be necessary once the official version of TWRP supports decrypting data on the Moto G5 Plus (https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153).
Phone has never been rooted (stock ROM installed)
1. Apply any pending OTA update and verify it succeeds
2. Turn off the phone
3. Boot into fastboot mode (volume down + power)
4. Connect the phone to a computer via USB.
5. Boot into TWRP recovery without flashing with the following command (ignore data decryption): fastboot boot twrp-3.2.1-0-potter.img
6. Take a backup of boot and recovery with TWRP (use external storage)
7. Reboot into fastboot mode (Reboot > Bootloader)
8. Connect the phone to a computer via USB
9. Flash TWRP recovery with the following command: fastboot flash recovery twrp-3.1.1-0-potter-decryptdata.img
10. Reboot into recovery
11. Allow TWRP to modify the system partition and prevent the rom from restoring the stock recovery
12. Root the device by installing Magisk using TWRP.
13. Install the f2fs-loopback-bug-workaround-2018.1.31 Magisk module.
14. Reboot into system.
15. Install Magisk Manager and verify Magisk is correctly installed
16. To install extra Magisk modules is recommended to reboot in TWRP (Magisk Manager > Modules > Reboot Recovery) then install the modules from there (for example, Busybox, Dolby Atmos® Classic (Lenovo_A7000), Youtube Vanced, Tethering Enabler, etc.)
Phone has been rooted with this method before
1. Boot into TWRP recovery (Magisk Manager > Modules > Reboot to Recovery).
2. Restore any boot and recovery images previously created with TWRP (stored on the external storage).
3. Continue with instructions explained in Phone has never been rooted (stock ROM installed).
Click to expand...
Click to collapse
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sure, to be on the safe side, either flash stock ROM then apply all OTA updates as you suggest. Otherwise, one can take a backup of the system partition too. I am not sure why OEM would be modified... but if that is the case, I guess it can be backed up as well.
As a side note, OTA updates from Motorola are downloaded to the following folder: /data/data/com.motorola.ccc.ota/app_download
It is always a good idea to back up the ROM to SD card before applying it, especially for full upgrades (which contain all partitions). That way, it is easy to flash the latest working ROM.
As for the Magisk modules, I had your same experience. It's just my preference to install them through TWRP.
Wolfcity said:
I don't think that you're able to install any OTA without flashing back system and OEM.
If these partitions were tampered in any way (and just mounting system r/w is enough) the OTA installation will fail.
I recommend to flash full stock stock firmware before applying OTA updates.
Maybe this worked in your case but there are too many things that change things in system or OEM so this won't work for everyone.
Also it's possible to install magisk modules through magisk manager, I do that all the time.
The only things that should be flashed through recovery is the F2FS loopback bug module and big modules like YouTube Vanced.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Wolfcity is right. From my own experience ANY use of TWRP (i.e., booting or flashing) modifies the OEM partition and prevents OTA from succeeding.
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
ctwftp said:
Your method does not work. Followed it, backed up right before attempting update in case it failed.... allowed update, it restarted into twrp immediately and then stuck in a twrp bootloop, recovered to backup and I'm still stuck in a boot loop to twrp.
Click to expand...
Click to collapse
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You can't update with twrp installed. If you can get into fastboot mode flash full stock rom incl. recovery and boot via fastboot.
Read my previous post.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
ctwftp said:
I see. His method specifically mentions installing TWRP and being able to update, guess he was wrong.
I ended up having to flash twrp and then was able to load my backup. It booted and said update failed and continues to work fine now. So there is no way to install updates with TWRP installed?
Click to expand...
Click to collapse
No. You have to be on untouched stock firmware incl stock recovery to capture OTA.
Sent from my Moto G5 Plus using XDA Labs
Still need to load up both twrps?
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
TimelesslyPrecise said:
Bump:
Just wondering the status, do we still need to load up both twrp to get this going? or is the latest sufficient?
https://dl.twrp.me/potter/twrp-3.2.2-0-potter.img.html
Thanks,
Click to expand...
Click to collapse
As the latest official TWRP has the decryption issue fixed it should work. Imo this guide won't work, a complete flash of stock is needed as I wrote before.
Sent from my Moto G5 Plus using XDA Labs
For some reason I could not get a backup of system and boot...
Ended up noticing a few issues with aosp, so flashed to lineage. Pretty smooth so far.
Been out of the game for awile, but it's coming back.
How G5 plus could be rooted.
So, I wanted to have a stock rom, rooted with magisk, and data partition decrypted, so what I did is the following:
1) wiped data partition
2) flashed stock OOS (latest, 5.1.6)
3) flashed Magisk
4) flashed DM-verity & force encryption disabler (this link)
Now I have a few questions:
1) I tried flashing the dm-verity from this link (no_verity_op5_v2.zip) but it didn't work so I flashed this newer version (disable_dm_verity_forceencrypt_09_02_2018.zip). Any ideas why it didn't work?
2) What should I do when a new OOS update comes up?
3) What should I do when a new Magisk update comes up?
Regadring Magisk: In Magisk there is a option "Preserve AVB 2.0/dm-verity":
1) What does it do?
2) What is AVB 2.0 in the first place?
Thank You all in advance
0v3rl0rd said:
So, I wanted to have a stock rom, rooted with magisk, and data partition decrypted, so what I did is the following:
1) wiped data partition
2) flashed stock OOS (latest, 5.1.6)
3) flashed Magisk
4) flashed DM-verity & force encryption disabler (this link)
Now I have a few questions:
1) I tried flashing the dm-verity from this link (no_verity_op5_v2.zip) but it didn't work so I flashed this newer version (disable_dm_verity_forceencrypt_09_02_2018.zip). Any ideas why it didn't work?
2) What should I do when a new OOS update comes up?
3) What should I do when a new Magisk update comes up?
Regadring Magisk: In Magisk there is a option "Preserve AVB 2.0/dm-verity":
1) What does it do?
2) What is AVB 2.0 in the first place?
Thank You all in advance
Click to expand...
Click to collapse
Answers:
1. It didn't work because you have to flash that zip BEFORE you flash Magisk (it's stated in the thread's first post too). The zip creates the required files which tells Magisk to disable dm-verity and forceencrypt when it is flashed.
2. When a new OOS comes out, all you have to do is dirty flash it, then the universal zip and then Magisk. You should be unencrypted with the new OOS as well.
3. The universal zip will most likely be updated if there are major changes in Magisk, but if not, then just update Magisk as usual, from within Magisk Manager. If you wish to update from TWRP by flashing the latest Magisk zip, then you have to remember to flash the universal zip BEFORE the newest Magisk zip and you should be fine.
Regarding your other queries, AVB refers to "Android Verified Boot". Google it and you'll find lots of information about it (which may be technical). Regarding the option in Magisk, it's for those people who want to let dm-verity intact while using Magisk (because some phones don't boot when dm-verity is disabled and hence this option is there for those people). Don't fiddle with it since you want to stay unencrypted and disabling dm-verity causes no issues on the OnePlus 5.
shadowstep said:
Answers:
1. It didn't work because you have to flash that zip BEFORE you flash Magisk (it's stated in the thread's first post too). The zip creates the required files which tells Magisk to disable dm-verity and forceencrypt when it is flashed.
2. When a new OOS comes out, all you have to do is dirty flash it, then the universal zip and then Magisk. You should be unencrypted with the new OOS as well.
3. The universal zip will most likely be updated if there are major changes in Magisk, but if not, then just update Magisk as usual, from within Magisk Manager. If you wish to update from TWRP by flashing the latest Magisk zip, then you have to remember to flash the universal zip BEFORE the newest Magisk zip and you should be fine.
Regarding your other queries, AVB refers to "Android Verified Boot". Google it and you'll find lots of information about it (which may be technical). Regarding the option in Magisk, it's for those people who want to let dm-verity intact while using Magisk (because some phones don't boot when dm-verity is disabled and hence this option is there for those people). Don't fiddle with it since you want to stay unencrypted and disabling dm-verity causes no issues on the OnePlus 5.
Click to expand...
Click to collapse
Thank You for Your answer
Regarding point 2 - OOS update: should I reboot after every step or no?
I mean:
1. dirty flash OS
2. reboot to recovery
3. flash universal zip
4. reboot to recovery
5. flash magisk
6. reboot to recovery
Or should I do that without rebooting: flash everything and then reboot to recovery?
0v3rl0rd said:
Thank You for Your answer
Regarding point 2 - OOS update: should I reboot after every step or no?
I mean:
1. dirty flash OS
2. reboot to recovery
3. flash universal zip
4. reboot to recovery
5. flash magisk
6. reboot to recovery
Or should I do that without rebooting: flash everything and then reboot to recovery?
Click to expand...
Click to collapse
It's not necessary to reboot to recovery after each step.
Update 220823: Update for TWRP 12 and some other minor changes due to the switch from SafetyNet API to Play Integrity API
Updated 211203: include Magisk Canary
Edited 220113: correct a mistake in the Keeping Root process; some formatting changes
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
OOS 11: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449
OOS 12: TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/...win-recovery-project-8t-9r-2022-07-27.4473983
Magisk apk - using stable from https://github.com/topjohnwu/Magisk/releases or using Canary from https://github.com/topjohnwu/magisk-files/tree/canary
Universal SafetyNet Fix (UNSF-MOD) by @Displax from https://github.com/Displax/safetynet-fix/tree/integrity
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
Boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it. Also install USNF if you are using Magisk Canary.
If you want to keep TWRP then install the TWRP installer zip.
Reboot.
If you are using Magisk Canary, in Magisk>Settings enable Zygisk, Enforce DenyList, and Configure DenyList. Then reboot.
Keeping Root on an incremental OTA update
Note: you do NOT need to (but can if you want to) follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you.
If your phone tells you you have an update:
If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot.
In Magisk tap on "Uninstall Magisk" and select "Restore images".
Install the OTA update but don't reboot yet.
Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root.
Reboot
When the phone has successfully rebooted the updated system, boot into bootloader mode.
Boot TWRP using fastboot boot x.img where x.img is the TWRP image file.
Take a backup of the current recovery partition as you'll need it for successfully updating when the next incremental OTA becomes available.
Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
If you want to keep TWRP then flash the TWRP installer zip.
Reboot and disable airplane mode.
BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggest this method (https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145) but this doesn't work for everybody (it doesn't for me).
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an OTA update
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
morphius88 said:
ctsProfile fails. Is there a way to fix it? Tried stable Magisk and Canary.
Click to expand...
Click to collapse
Best place for getting support for Magisk is https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
berthur said:
Hi,
Thanks for the guide!
What can i do if i forgot to backup stock boot and recovery?
Click to expand...
Click to collapse
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
BillGoss said:
You have a number of options:
If your update was an incremental OTA:
1. Ask in the Q&A forum or in one of the update threads if someone can share those two partitions with you.
2. If you're on 11.0.10.10kb05aa then you can get boot from a number of the update/rooting threads and the recovery from this thread by @mslezak https://forum.xda-developers.com/t/...-rooted-users-install-from-fastbootd.4316147/
3. Use this tool by @mslezak to create the full partitions from an incremental update https://forum.xda-developers.com/t/...urrently-op8t-11-0-9-9-kb05aa-posted.4314677/
If you updated using a full installation zip:
- use payload dumper to extract the two partitions from payload.bin
Click to expand...
Click to collapse
Than you!
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Wishmasterflo said:
Hello!
Does someone have a backup of the Stock recovery from OOS 11.0.10.10.KB05BA and can share it here?
Thanks in advance.
Click to expand...
Click to collapse
Download the zip from https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ and then use payload dumper to extract the files.
That worked like a charm. Thanks a lot.
I'm Magisk rooted and I have TWRP installed on my 8T EU model.
The OnePlus updater app registers that I am rooted and wants to download the full OTA.
Do I also have to do all the things you described after "Keeping Root on an OTA update" or is there a simpler way?
If yes, then I have a question regarding this step:
2. In Magisk tap on "Uninstall Magisk" and select "restore images".
Click to expand...
Click to collapse
Did Magisk automatically backup these images? Because I didn't do it myself. I only have backed up all my partitions (including boot) after I had installed TWRP and before I rooted.
EDIT:
BillGoss has thankfully already replied in another thread (in which I have basically asked the same question because I am an impatient bast***) where I suggested the overly present "easy" update scheme, which he expects to work. So this should be fine for other people in my situation:
1. Let the system download and install full OTA and DO NOT let the device reboot after it's done
2. Install TWRP A/B Retention Script
3. Install Magisk to inactive slot and reboot
EDIT2:
I just want to add that before having done the above mentioned steps 1-3, I have disabled all Magisk modules and rebooted the device. So the full procedure is the following:
1. Disable all Magisk modules and reboot
2. Let the system download and install full OTA and DO NOT let the device reboot after it's done
3. Install TWRP A/B Retention Script
4. Install Magisk to inactive slot and reboot
Youtube step by step video (he says that he "uninstalls" the Magisk modules but he just deactivates them):
Thanks @haitower
I've updated the OP to make it clear that the process described there only applies to incremental updates.
Also, to answer your question re Magisk backups: Magisk writes a copy of the installed boot image to /data/Magisk* before patching it. A "restore image" uses that backup.
BillGoss said:
I keep seeing posts that say you can't root OOS after an OTA unless you have a full image installation zip. That's just not true these days (September 2021).
You can use @osm0sis' method in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
And @g96818 suggests using "Install to inactive slot" but this doesn't work for everybody (it doesn't for me) which works provided you do it properly - see https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85801253.
And here's how to do it using TWRP.
What you'll need:
• TWRP image (.img) and (optionally) installer zip from https://forum.xda-developers.com/t/recovery-11-alpha-teamwin-recovery-project-8t-kebab.4302449/
• Magisk apk - I'm using v23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I'm also assuming you have an unlocked bootloader, know how to use fastboot, how to use TWRP, and how to use Magisk.
I'll go through rooting a currently unrooted version of OOS and then doing an incremental update OTA.
Root unrooted OOS
1. Install the Magisk APK. I find that this works nicer than letting the stub download the full app the first time you use it.
2. Boot into bootloader mode
3. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
4. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
5. Install the Magisk APK, just like you would install any zip file in TWRP. Note: the APK must be named Magisk-*.apk otherwise TWRP won't list it.
6. If you want to keep TWRP then install the TWRP installer zip.
7. Reboot
Keeping Root on an incremental OTA update
Note: you do NOT need to follow this process if you're installing a full OTA. You only need to install the full OTA and then install Magisk to the inactive slot and reboot from Magisk when it prompts you
If your phone tells you you have an update:
1. If you have TWRP installed, then boot into TWRP and restore the stock recovery and reboot
2. In Magisk tap on "Uninstall Magisk" and select "restore images". Or, if you're like using terminal commands, restore the stock boot image (you backed it up with TWRP) to the current slot using dd
3. Install the OTA update but don't reboot yet.
4. Turn on airplane mode so that apps can't call SafetyNet when you reboot the phone without root
5. Reboot
6. When the phone has successfully rebooted the updated system, boot into bootloader mode
7. Boot TWRP using fastboot boot x.img where x.img is the TWRP image file
8. Take a backup of the current boot and recovery partitions as you'll need them for successfully updating when the next incremental OTA becomes available
9. Clean up old Magisk backup copies of stock boot images by using File Manager to delete /data/magisk_backup_* directories
10. Install the Magisk APK, just like you would any zip file in TWRP. Note: the APK file name must start with Magisk- otherwise TWRP won't list it. Your existing Magisk settings, modules, and [hidden] Magisk app will be preserved.
11. If you want to keep TWRP then flash the TWRP installer zip.
12. Reboot and disable airplane mode
Click to expand...
Click to collapse
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
e1thx said:
Hello,
Thank You for the detailed description, it helped me a lot.
I'm new with the Oneplus 8T phone. The last handset I had was the Mi MIX 2. The rules of using root are familiar to me and I understand everything from your description. I only have a question about TWRP, once I have them permanently installed on device, can I backup the system or date partition via TWRP? I always made backups in case i messed up something and didn't work properly.
This question came from https://twrp.me/oneplus/oneplus8t.html
They write there:
"This device uses Dynamic Partitions
This means that TWRP will not allow modifications to any of the partitions that make up the Super partition on the stock ROM. All backups and restores will include the full Super partition rather than the individual dynamic partitions.
In order to flash the individual partitions, you will have to boot into fastbootd."
I would be grateful for Your information, Thank You.
Click to expand...
Click to collapse
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Hello!
Today I saw that EU: 11.0.12.12.KB05BA was available as OTA Update so I started to download it using the "Keep root on OTA Update".
During the download I recognized that I was still only connected to mobile network 4G instead of WiFi.
So I stopped the download of the OTA, restarted the phone and turned on WiFi but now I don't get the notification for the new OTA Update anymore and when checking for new Updates it says that my OOS 11.0.11.11 is up to date.
I guess the system has somewhere already stored that I started the download of the new 11.0.12.12 OTA but did not finish it and now I don't get the message to download it anymore.
Any idea how I can fix this so that I can download the new OTA again?
Thanks a lot!
EDIT: I am downloading it now via OxygenOS Updater (the full OTA).
BillGoss said:
See post #3 in https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-29-11.4302449/
Click to expand...
Click to collapse
I understand that if I want to restore system and data when something doesn't work for me then I just do recovery for all the partitions, system, data etc that I do in twrp?
Please see the update in the OP regarding OOS 12.