Related
Hi all.
So, as we know with recent MIUI update Xiaomi screwed our whyred. And this gave birth to many questions which is like a struggle for many users to find all those answers. So, I tried to answer all your questions. If you think your question isn't included please feel free to ask.
Q1: What is this "Anti-Rollback" thing?
A: Its a security measure that Google brought with the release of Android Oreo. It makes sure that your data is secure even when phone is stolen or if any attacker tries to downgrade the software and wants to gain control over your data.
Q2: How is this harmful to my device?
A: Well, as a security measure it should never give you a hard-brick. When someone tries to downgrade, it should display a warning and get turned off but there's difference between how things should work and how Xiaomi does. As Google has stated, "Anti-Rollback" should get automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks. Hopefully the developers of MIUI should push an update soon and if they don't, our beloved devs will find a way for sure
Q4: So, what now? Will Xiaomi solve this issue?
A: We do not know. But our beloved developers in the XDA-Forum will find a way for sure
Q5: How to know if my device is affected by it?
A: Run fastboot command :
Code:
fastboot getvar anti
The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Q6: I'm in the Anti-Rollback squad what now?
A: Don't worry you can still flash custom recovery and roam around custom ROMs but avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device.
Q7: Which MIUI builds include "Anti-Rollback"?
A: All the MIUI builds which are released after Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5 include "Anti-Rollback". And yes the Chinese versions are affected as well.
Q8: Do MIUI Stable V9.5.17.0 and Beta V8.7.5 have "Anti-Rollback" enabled?
A: NO. If you're on either of these builds you are safe to downgrade and use any older version.
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first by running fastboot command:
Code:
fastboot boot xyz.img
(where xyz is name of your recovery file). Once you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs. WARNING: Avoid flashing any firmware.
Q10: Can I migrate from Stable to Beta and vice-versa?
A: You can install Beta from Stable, make sure you flash latest Beta build same is the case with Stable. If you're on anti-4 firmware, whether its Beta or Stable you can switch to any anti-4 MIUI ROM Beta or Stable but remember you must flash latest version available while switching. (anti-4 means "Anti-Rollback" enabled firmware)
Q11: Can I unlock bootloader and flash custom ROMs on an "Anti-Rollback" enabled device?
A: Yes. Again to flash custom ROMs and recovery refer to Q9.
Q12Can I flash "Anti-Rollback" enabled ROM via TWRP?
AWell, in some cases it did work, just flash lazy flasher zip file after flashing MIUI ROM via TWRP. But while switching to MIUI from AOSP based ROMs on an "Anti-Rollback " enabled device I recommend you to go with fastboot method to avoid chances of brick.
For active discussion join whyred telegram group: https://t.me/redminote5proofficial
Hit thanks if helped.
Saabu said:
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first
by running fastboot command:
Code:
fastboot boot xyz.img
(where xyz is name of your recovery file). Once
you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery
from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs.
WARNING: Avoid flashing any firmware.
Click to expand...
Click to collapse
Thanks for the above, but I believe that #9 is true. All MIUI roms regardless of version and anti roll back protection willl reflash the default MIUI recovery when you boot the OS. The only way to get it to stay is by flashing a custom ROM after TWRP, or by obtaining root and removing the "/system/bin/install-recovery.sh" file. If you're on anti-rollback you won't even be able to flash the recovery - you'll get an anti-rollback protection error.
This only concerns the "Xiaomi Redmi Note 5"?
For the Fastboot Command : fastboot getvar anti , I have : Anti:1 .. What does means ?
When you says "avoid flashing any firmware or any MIUI ROM which is older than what you're using now." , So Imagine if I have MIUI 10 Official with Android 8.1 and I Would like to flash like Xiaomi.eu or Lineage OS with Android 8.0 , The phone will brick ?
If I want to Flash Mod with TWRP Flashable Zip , the phone will brick or not ?
Thanks for your FAQ !
For me when i type fastboot devices it shows my device number but when i type this command fastboot getvar anti it shows nothing please help and im using Redmi note 5 vince version and miui version is 9.6.2.0 global stable.
kunal bro said:
For me when i type fastboot devices it shows my device number but when i type this command fastboot getvar anti it shows nothing please help and im using Redmi note 5 vince version and miui version is 9.6.2.0 global stable.
Click to expand...
Click to collapse
You answered yourself... It is ONLY for Redmi Note 5 (Pro) aka whyred! You are even in wrong device forum!
One doubt..... I am on AOSP right now. If I flash global beta 8.7.12 in twrp and then flash lazyflasher, will my twrp be removed !! Will I be able to go back to AOSP ?? @Saabu
DEBASISH said:
One doubt..... I am on AOSP right now. If I flash global beta 8.7.12 in twrp and then flash lazyflasher, will my twrp be removed !! Will I be able to go back to AOSP ?? @Saabu
Click to expand...
Click to collapse
After you flash a ROM that has Anti-Rollback enabled, you can still switch to AOSP anytime as I discussed in Q9. And yes, flashing lazy flasher simultaneously after MIUI will keep your TWRP.
Happy flashing
Saabu said:
Q5: How to know if my device is affected by it?
A: Run fastboot command :
Code:
fastboot getvar anti
The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Click to expand...
Click to collapse
Hi, @Saabu,
Many thanks for the clarification.
However to enter the code through the fastboot, it has to be with the equipment turned off in fastboot mode, right?
Best regards,
Jorge
Jorge Moreira said:
Hi, @Saabu,
Many thanks for the clarification.
However to enter the code through the fastboot, it has to be with the equipment turned off in fastboot mode, right?
Best regards,
Jorge
Click to expand...
Click to collapse
Ofc.
Fastboot commands work only in fastboot mode?
Saabu said:
Ofc.
Fastboot commands work only in fastboot mode
Click to expand...
Click to collapse
It was a silly question, I know ...
Just to confirm....
Thanks,
I am a little concern about all this anti rollback matter...
well, the point is i am in xiaomi.eu rom, 8.6.28 (miui 10). I have checked the "anti" variable via the "fastboot getvar anti", and return 3.
Now, I would like to downgrade to miui 9 via twrp, and since I have "the 3 value" I understand that I can downgrade without any trouble, rigth?
However, I have found this https://xiaomi.eu/community/threads/antiroll-back.44975/
Here a guy have tried somehing similar and...briked phone.
What do I do now? Flash? i stay in a rom version that i dont like?
Thanks for your answers
nolohedecidido1 said:
I am a little concern about all this anti rollback matter...
well, the point is i am in xiaomi.eu rom, 8.6.28 (miui 10). I have checked the "anti" variable via the "fastboot getvar anti", and return 3.
Now, I would like to downgrade to miui 9 via twrp, and since I have "the 3 value" I understand that I can downgrade without any trouble, rigth?
However, I have found this https://xiaomi.eu/community/threads/antiroll-back.44975/
Here a guy have tried somehing similar and...briked phone.
What do I do now? Flash? i stay in a rom version that i dont like?
Thanks for your answers
Click to expand...
Click to collapse
You can flash any MIUI 9 with anti 3 via TWRP. Dont flash the ROMs with anti 4 via TWRP. Last MIUI ROMs with anti-3 were: Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5.
Saabu said:
Hi all.
So, as we know with recent MIUI update Xiaomi screwed our whyred. And this gave birth to many questions which is like a struggle for many users to find all those answers. So, I tried to answer all your questions. If you think your question isn't included please feel free to ask.
Q1: What is this "Anti-Rollback" thing?
A: Its a security measure that Google brought with the release of Android Oreo. It makes sure that your data is secure even when phone is stolen or if any attacker tries to downgrade the software and wants to gain control over your data.
Q2: How is this harmful to my device?
A: Well, as a security measure it should never give you a hard-brick. When someone tries to downgrade, it should display a warning and get turned off but there's difference between how things should work and how Xiaomi does. As Google has stated, "Anti-Rollback" should automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks. Hopefully the developers of MIUI should push an update soon and if they don't, our beloved devs will find a way for sure
Q4: So, what now? Will Xiaomi solve this issue?
A: We do not know. But our beloved developers in the XDA-Forum will find a way for sure
Q5: How to know if my device is affected by it?
A: Run fastboot command : The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Q6: I'm in the Anti-Rollback squad what now?
A: Don't worry you can still flash custom recovery and roam around custom ROMs but avoid flashing any firmware or any MIUI ROM which is older than what you're using now. Remember you cann't flash MIUI Stable over Beta otherwise you'll brick your device.
Q7: Which MIUI builds include "Anti-Rollback"?
A: All the MIUI builds which are released after Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5 include "Anti-Rollback". And yes the Chinese versions are affected as well.
Q8: Do MIUI Stable V9.5.17.0 and Beta V8.7.5 have "Anti-Rollback" enabled?
A: NO. If you're on either of these builds you are safe to downgrade and use any older version.
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first by running fastboot command: (where xyz is name of your recovery file). Once you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs. WARNING: Avoid flashing any firmware.
Q10: Can I migrate from Stable to Beta and vice-versa?
A: You can install Beta from Stable and make sure you flash latest Beta build but installing Stable over Beta isn't possible yet.
Q11: Can I unlock bootloader and flash custom ROMs on an "Anti-Rollback" enabled device?
A: Yes. Again to flash custom ROMs and recovery refer to Q9.
For active discussion join whyred telegram group: https://t.me/redminote5proofficial
Hit thanks if helped.
Click to expand...
Click to collapse
Deleted
i have a question for my understanding. for example i want to install LOS 15.1. Where do i know if LOS uses ARB 3 or 4 ?
TM147 said:
i have a question for my understanding. for example i want to install LOS 15.1. Where do i know if LOS uses ARB 3 or 4 ?
Click to expand...
Click to collapse
When updating to LOS/AOSP based rom, its installer does not include firmware update. So you gonna have the same anti value after flashing it. Btw, check their official thread, they have clear installation instructions now.
what about my warranty if my phone is bricked?
will they do for free of cost
as my phone got bricked today 3 months old phone
If I delete firmware update folder in any rom ( with ARB4 ,ARB4,any older ROM) and flashing that will brick my phone ?
hargitomi said:
When updating to LOS/AOSP based rom, its installer does not include firmware update. So you gonna have the same anti value after flashing it. Btw, check their official thread, they have clear installation instructions now.
Click to expand...
Click to collapse
Thanks. but now i have some more question. Sorry this ARB Think is
Which official thread did you mean ? I found the official installation guide but i can't read anythink about devices with ARB4
... sorry can't post the link to LOS
Another thing that makes me thoughtful is Q2 in the beginning. "As Google has stated, "Anti-Rollback" should automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks."
So unlocking the bootloader is essential for flashing a custom recovery. What can/ must i do if i have a ARB4 Device to install TWRP ? On the TWRP side i can't read anything about this problem
.. sory can't post the link to TWRP
So please help me because i don't want to brick my device
iam on 8.7.5 with unlocked bootloader can i flash custom roms like los and rr rom by using twrp
Though everyone seems bz with antirolback or pie "Dual Boot Patcher" has officially supported whyred. Thanks to "chenxiaolong" (its completely his work)
here's official site https://dbp.noobdev.io/
downloads:
https://dbp.noobdev.io/downloads/
we have lots to talk about and there will be many success story to discuss . lets start.
those who dosen't know or new to this it actually uses other storage partitions to flash roms and there are many unique features like app data sharing on multiple roms , in app flashing roms etc.
welcome to the party .
process to flash
1. patch the rom.zip file with app or from windows for multi slot partition . e.g. rom-multi-slot-1.zip (not sure secondary works or not)
2. try add rom from in app (if its aroma you have to flash from twrp)
3. switch rom from menu
4. reboot
everything for better understanding is here https://forum.xda-developers.com/showthread.php?t=2447534
Last I knew even oreo wasn't supported on dbp.
Sent from my Redmi Note 5 Pro using Tapatalk
no Boot UI for whyred/Xiaomi Redmi Note 5? how to switch the rom without UI?
Boot UI
Supported: no
Click to expand...
Click to collapse
Hey i will unlock my device in the next days and actually have global stable rom with arp4. My idea was to unlock, boot twrp through adb, save stock rom and stock recovery, flash twrp, flash root, install dual boot patcher and test/install roms as second rom and leave stock rom as primary. My hope is that this way there is no risk of bricking my device. am i right? thank you
@ecrum you got dual boot patcher successful installed on whyred? Didn't test it till now but i am not sure if there could be problems because of ARP and a risk of bricking the device? Thank you
i know that i doesn't support Oreo
alfredxyz said:
@ecrum you got dual boot patcher successful installed on whyred? Didn't test it till now but i am not sure if there could be problems because of ARP and a risk of bricking the device? Thank you
Click to expand...
Click to collapse
still no update from dev's side. but no risking bricking either. for now it only see all the partitions and it can set the kernel for primary rom for pie. in case of oreo a non gsi rom perhaps Ressurection Remix could work. in case of dual pather the rom updater script must support DBP ...
things have to go long way for now. but its not bricking anything. test if you like but nonetheless you have taken a proper nand backup
Any news?
still not working?????
Hey OP6 users
i thought of something. that might have been obvious for some people but maybe not for everyone.
when doing a clean flash for a custom ROM it is often needed that we flash a required base. Either OOS stable or a OOS beta version.. which ever is needed by the custom ROM.
we don't need to flash the base again when we're just updating the custom ROM (unless the custom ROM needs a newer version of the base
knowing that, is it still needed to flash the base when changing to a custom ROM that needs the exact same base?
correct me if I'm wrong, but it would save some time for us to not have to flash the same required base for another custom ROM which needs the same one we previously flashed.
it would save: two OOS + TWRP flashes every time and two TWRP reboots, which would be pretty nice?
it would also be nice to save that time if we just wanted to re flash the current ROM I/you/we were using for any reason.
then a clean flash of a current custom ROM in use or changing to another ROM with the requirement of the same base would just be as simple/fast as
Format Data !!!!(optiona)!!!!
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash GApps.zip + Magisk
Reboot System
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
How much time do you think you are wasting out of your life when you have to flash a base file (give me seconds and % of HP)? ROFL...?
If I am flashing a new ROM, usually I clean flash, test the ROM... IF I LIKE --> clean flash again, and set it up proper.
Feels good coming fresh out of the box, knowing everything is working optimized.
Anways, with xXx.NoLimits and how smooth OOS is, personally I don't really see any point on flashing custom ROMs anyways anymore.
castrum_doloris said:
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
Click to expand...
Click to collapse
Aight yeah it thougt so. Ofc I wipe data before flashing a new rom. But thanks for your input/confirmation feels good to have other opinions and experiences then there's also the fact you also have to wait until your rom supports the new base, so u don't flash a new base then switch to your custom Rom and stuff won't work correctly hehe
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
kewinhw said:
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
Click to expand...
Click to collapse
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
castrum_doloris said:
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
Click to expand...
Click to collapse
okey I'm using the disable dm-verity, forceencrypt script btw. but okey i see now hehe. thanks for your answer
Some background: I'm coming from an OP3 which did not have this Slot A/B thing and you could easily just flash firmware going forward. I'm currently confused as to how custom roms will update firmware and such going forward.
I noticed there's 'systemless' roms now (like NoLimits), I don't really understand what the advantages/disadvantages vs something like Havoc OS are.
If I go with a custom rom, will I need to flash to OOS to update firmware then reflash back to the custom rom in the future?
I apologize if these are really newb questions, trying to find specific details with some of these keywords makes it really hard to find relevant information (and I've tried).
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Link above is some info on A/B partitioning.
The benefit of systemless ROMs are that they are just Magisk Modules so installing and uninstalling is very easy. You don't need to boot into recovery or wipe anything.
Havoc is a full ROM and based on AOSP so wiping is needed, especially when security patches are different. Some people are decrypting their phones with the no verity zip but I won't say too much about that to keep things as simple as possible.
You don't need to flash any OOS firmware when on Havoc, and I think it's because custom ROMs have their own vendor image. More advanced users feel free to correct me if I'm wrong about this.
Flashing isn't really too different and I personally don't even think about A/B slots. You just need to remember to flash the TWRP zip file after a ROM flash to keep TWRP. And you also need to reboot back into recovery to install Google apps, rather than just after the ROM flash.
Custom kernels are now flashed last (after TWRP and Magisk).
This is how I've done it and have been issue-free.
I am using my poco x3 pro with mi eu as my daily driver; however, duplicate apps still reign supreme and the default mi music app doesn't get recognized in Android Auto.
I have dabbled in custom roms before, a couple times but most of them have stopped me from completely using the phone normally, namely broken camera support with drive doesn't recognizing the camera (even with gcam, don't @ me), slow document viewer and so on. As such, I generally refrained from using them, until I saw Crdroid 8 with MIUI cam, which seems like the best of both world for me.
The guides on the thread are too vague? And Im not sure about updating (the rom required a custom recovery image, however, my recovery is too old and i don't want to risk my phone getting bricked)
Can someone help? Thanks a lot!
bump
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
AmmarHaseeb said:
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
Click to expand...
Click to collapse
Does this erase the internal storage? I don't have an SD card and a usb otg
BreadGyarados said:
Does this erase the internal storage? I don't have an SD card and a usb otg
Click to expand...
Click to collapse
I already got that figured out
BreadGyarados said:
I already got that fig
Click to expand...
Click to collapse
BreadGyarados said:
I already got that figured out
Click to expand...
Click to collapse
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
irmas5 said:
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
Click to expand...
Click to collapse
I see!
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
BreadGyarados said:
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
Click to expand...
Click to collapse
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
pl1992aw said:
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
Click to expand...
Click to collapse
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
BreadGyarados said:
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
Click to expand...
Click to collapse
The deciding matter is the Android system currently installed in the phone.
Your example is MIUI.eu with Android 11, in custom recoveries should be able to see internal storage.
[Phone is now Android 11]
After you install CrDroid Android 12 and boot, then custom recoveries cannot see internal storage if it's encrypted.
[Phone is now Android 12]
If you revert from CrDroid Android 12 to MIUI.eu Android 11 and boot, then custom recoveries should be able to see internal storage again.
[Phone is now Android 11]
If your phone is now Android 12, when you want to install something or flash/update a ROM in custom recoveries, it will be a bit complicated as mentioned earlier. You have to sideload with commands.
If you have microSD cards in the phone or USB OTG, then custom recoveries should be able to read them even under when phone is Android 12.
Whether ROMs can dirty flash or not, you have to read the ROM thread and replies (or Telegram if there is no XDA thread), especially replies by the developer.
Some version cannot be dirty flashed, even if it's by the same developer.