Database Develop

dm verity (red)

I want do clean install so I evrything wipe expect user data. And there problems started. I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
I tried full wipe data - don't work. I was looking in the forum Oneplus any tutorial didin't work.
I tried this tutorial https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094 to remove warning. It works but after update from 4.0.2 to 4.1.6 warning screen again came back. It started after updating 4.1.6 to 4.1.7.
If you can slowe this problem I will be grateful. And i sorry for my engilsh

Wronko said:
I want do clean install so I evrything wipe expect user data.
Click to expand...
Click to collapse
If you want a "clean" install, user data is the most important thing to wipe; as it is the mostly likely thing to cause problem (on a new ROM, etc.).
Not related to the other issues you mentioned. But important to note, anyway.
Wronko said:
I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
Click to expand...
Click to collapse
I'm confused. If you haven't installed TWRP, how you are trying to root? You need TWRP, in order to root.
Also, sideload can be more problematic than just flashing a ROM in TWRP. My suggestion, would be to stop messing around, and just flash TWRP.

* I wanted to write that After installing update 4.1.6 as well as on the factory as a TWRP warning appears.
*On TWRP can't root device, TWRP think the su ZIP archives od broken.
*And TWRP by bluetooth Spark can't decrypt device (my old password od bot working )
Device works fine by In addition to the aforementioned problems

Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...

ilyr73 said:
Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...
Click to expand...
Click to collapse
Can you link for your SuperSU zip and TWRP?

Wronko said:
Can you link for your SuperSU zip and TWRP?
Click to expand...
Click to collapse
TWRP for Oneplus 3T
SuperSU 2.79 for Oneplus 3T

After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.

Wronko said:
After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.
Click to expand...
Click to collapse
Have you flashed TWRP and 3.5.4 first? Have you used bootloader with "fastboot format userdata" before flashing supersu (remembering that after this, normal boot should not start before supersu is flashed)?
Also I am not sure if flashing 3.5.4 image will update the firmware as well, but for safety, you might try to flash that as well: Oneplus 3T Firmware collection

I didn't flash 3.5.4 at all, just 4.0.2. I used "fastboot format userdata" in bootloader. And then there was a problem (boot loop.). And after that i booted into recovery(I had then stock) asked me for password )At this point I did not have any) so I wiped my device again (recovery suggest it). The device turned on normally, but still i had dm verity. Finally I updated by OTA to 4.1.6 and dm verity screen was gone.
At this point I install TWRP and rooted, without any problem.
So i think fix for this situation was going back to full stock and use OTA. (Again sorry for my English, I trying my best)

[Solved] Official Oxygen OS 5.0 boot loop problem for rooted users

Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.

Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.

I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.

Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?

DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.

Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.

fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files

so...the no verity is only for decrypted users right?

fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.

The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.

igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?

Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.

I've triyed this. All good till i flash 5.0 & Magisk & no verity....

Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.

Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,

1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?

MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.

BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.

MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.

raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.

Dm verity triggered oxygen OS 5.0.0

I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.

Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.

do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?

przemcio510 said:
Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.
Click to expand...
Click to collapse
I cant find the proper files. Can you please link me a thread from which i can follow the step and find the files.

Bradl79 said:
do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?
Click to expand...
Click to collapse
Yes

FOLLOW THIS GUIDE TO DISABLE DM-VERITY
READ POST 2 IN OP, I HAVE ALSO DESABLED DM-VERITY FOLOOWING THE GUIDE BELOW:
You will need to reinstall custom ROM+gapps package if you are using custom ROM but if your are using official oxygen OS or oxygenOS based OS like theOne3t, you will not need to reinstall the full ROM at the end of process.
Have a look and carefully proceed. It works..........
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748

usually happens when u install stock OxygenOS without root or no_dmverity, u can install 4.0.2 fw via twrp and go to fastboot and type via cmd
Code:
fastboot oem enable_dm_verity
then u can reflash current fw of what u r on.

malikahmed205 said:
I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.
Click to expand...
Click to collapse
dm-verity should not (in itself) prevent the update from installing. I have dm-verity tripped (warning screen on boot) and have updated many times (maybe 5-6 updates) with no problems at all. I suspect something else is going on. What version TWRP, and how big is the update file?
When you try to update, how are you doing that, following the notification when the phone is booted to OS? Or are you in TWRP, and try to flash the update?

This happened to me as well when trying to root.
If you are getting warning that dm-verity is not enforcing, then see this thread: https://forum.xda-developers.com/on...e-red-warning-dm-verity-t3727959/post75022331
I also had to use the latest version of Magisk (15.3) for rooting to work properly.
Sent from my OnePlus3T using XDA Labs

Running Root on G6 since July '18. What are my options to upgrade software?

Dear all,
I've rooted my phone in July 2018 with the latest stock build from that timeframe. I'm getting notifications of OTA updates for the past 6 months that I've been swiping away and putting off. Obviously I cannot update OTA.
What are my options to update my phone if I want to maintain root? Is there a full build somewhere that I can install via twrp and flash SU or magisk over? Are there fully functional ROMs that I can periodically flash via TWRP to stay up-to-date and rooted? Or am I forced to revert to stock, update via OTA, then re-root?
I'm familiar with rooting but the G6 pathways have confused me compared to my previous OnePlus and Nexus phones. Thanks for your help.

You should only have to re-flash
OEM
Vendor
Boot
Recovery
to be able to apply the OTA.
Afterwards you just need to boot the twrp and install Magisk again, and maybe use the dmverity patch to disable forced encryption. <-- This has to be done BEFORE the first boot of the upated system, otherwise the phone will be encrypted again.
At least this is how it works on the G6 Play.

So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.

You can do that without loosing your apps/userdata.
Best bet would be to find the latest full image for your make/model and flash everything via fastboot. Just skip the part "fastboot erase userdata" or something like that, and you are good to go. Just remember the dmverity thing, if that is important/applicable for you.
Re-root is necessary either way, but that takes like 5 minutes, that shouldn't hold you up.

tintn00 said:
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
Click to expand...
Click to collapse
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above

HueyT said:
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
Click to expand...
Click to collapse
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!

tintn00 said:
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
Click to expand...
Click to collapse
If u want to backup data partition on TWRP, u have to be unencrypted for Moto G6 as TWRP can't decrypt data.
Rooting is just Magisk 18.1 and has nothing to do with encryption.
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally

HueyT said:
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
Click to expand...
Click to collapse
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.

tintn00 said:
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
Click to expand...
Click to collapse
Unlocked is safest guarantee against bricking. Don't worry about "uncertified" in Play store

Boot loop problem after updating magisk module.

Hello everyone,
Today I had a notification telling me that there is a new version of both magisk manager and module. Therefore I first updated the manager successfully and proceeded to update the module through in-app flash. After the flash completed, app prompted me to reboot. However, the reboot process never finished and the phone got stuck while booting. Since then I only tried factory reset which only booted the phone to let me enter my sim card password but after that, it rebooted itself to boot loop again. Some info about the phone:
TWRP installed and still working,
Latest xiaomi.eu from that won't boot anymore,
Only viper4droid and youtube vanced modules were installed.
AdAway for obvious reasons.
and that's it. Now I am planning on flashing crdroid ROM to make the phone work again but the installation process requires me to do:
Flash MIUI11 eea with miflash : min V11.0.8.0.QFAEUXM note : if already on v11.08.0 there's no need to redo
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" note : if already done there's no need to redo
Flash TWRP in fastboot and boot into TWRP
Click to expand...
Click to collapse
is there a step that I should skip? It's been 6 months since I handled the initial process to be able to flash xiaomi.eu from therefore I don't remember how I exactly did that as I have only been OTA updating the from since then. I don't remember or know how to flash V11.0.8.0.QFAEUXM nor vbmeta.img nor TWRP. I don't even know if I "should" flash those. I am open to any different suggestions or help to let me achieve my goal of flashing crdroid to get out of this mess.
Thanks in advance!