Tried this method and still the folders are encrypted in twrp :/Here are the instructions on how you should flash the new OSS Vendor ROM since most people here are confused:
- Flash latest TWRP by brigudav
- Flash Android 11 12.0.7 MIUI firmware
- Reboot recovery
- Format Data
- Reboot recovery
- Flash ArrowOS
- Flash Magisk
- Flash Gapps (If you're on Vanilla build & If you want custom gapps)
- Reboot system
- Firmware: https://xiaomifirmwareupdater.com/firmware/surya/stable/V18.104.22.168.RJGEUXM/
- TWRP: You can find it on 4pda but you need an account. I'm not allowed to share it, so you have to get it yourself.
This firmware is for NFC model as I'm not sure where is A11 firmware for non-NFC model. It can possibly work for non-NFC model, feel free to try.
It seems brigudav's files (including TWRP) are also available from androidfilehost. I only checked the latest twrp.img from there and it's the same file I had on my pc.- TWRP: You can find it on 4pda but you need an account. I'm not allowed to share it, so you have to get it yourself.
I'm yet in the process of figuring it out. I'm completely caught off-guard by this weird issue all of a sudden as there has been literally no changes been made to the device sources nor the rom source so at this point i'm not sure what's even causing it. I've also decompiled the twrp and went through its contents but everything looks fine and dandy in there.Ganesh, since you're here, any information on the TWRP encryption issue after the June 9 build?
Not good! I haven't tried Migrate yet, it was just presented to me as an option for the task at hands, so either someone comes up with a success story, or I will have to just try all three backup methods and find out for myself if any of these is going to work.I have tried Migrate since my phone was rooted but had issues restoring the backup. The phone got into a bootloop, so I have been forced to set everything back up from scratch again
Why would TWRP (any version, same as any version of OrangeFox) have any issues if you have an unencypted device???Just now, I installed TWRP 3.5.2_10-2 (Brigudav) on my Poco X3 NFC ... then I flashed "Disable_DM-Verity_ForceEncrypt" ... and I have no issues with the TWRP reading files unencrypted.
After testing, I can affirm that TWRP 3.5.2_10-2 by brigudav cannot decrypt the data encrypted with Android 11 + OSS vendor.Hello everyone,
I saw that brigudav updated his TWRP version to 3.5.2_10-2.
Did anyone try it yet? Does decryption with OSS builds work? (I don't have the time to experiment with the new OSS builds atm)
Like i said the Arrow recovery is only intended for OTA updates with no extra features. You won't be able to access internal data as its posed as a security risk.
I have answered and added a few FAQ's to the original post. Those who are still having difficulties switching to OSS builds have to check them out.I just installed this ROM, but my wifi does not work. Any suggestions?
No news about updates to OrangeFox and TWRP yet, hopefully this issue is being worked on.
To everyone, please STOP this misconception about having the need to flash magisk in order to pass safety net. Do read the OP I've clearly mentioned there's no need of a magisk or modules for safety net. Device is certified and passes safety net out of the box without need of any modifications.Mission Impossible in all custom ROMs !
1. Safetynet check the bootloader status and will automatically fail if magisk is not installed (Magisk Hide ON must be applied for this) !
2. Furthermore, now you have to install the safetynet-fix module to make your banking apps working !
3. Finally, you must hide Magisk Manager.apk with a random name too (Magisk Settings)
I'm aware of the notification led issue, its interlinked to an sepolicy denial from vendor which is quite tricky to address it while we're using the prebuilt/stock vendor. For now you can assume it as a trade off for enforcing builds. I'm working on a fix, once we start a full transition towards an OSS vendor these issues will be more convenient to be addressed.Even dev says in dec the 3rd changelog that notification led was implemented, it still doesn't work for me