Related
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
TWRP
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
Orangefox TWRP
https://sourceforge.net/projects/or...OrangeFox-R9.0-2-whyred-MIUI-Pie.zip/download
(This version not compatible with oreo so use it for miui pie only)
https://youtu.be/1WnxULKjgdE
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
gursewak.10 said:
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
https://youtu.be/1WnxULKjgdE
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
Click to expand...
Click to collapse
So from what I've read, if you flash the rom first, then update your recovery you should be good?
Sent from my Redmi Note 5 using Tapatalk
OrangeFox
gsmyth said:
So from what I've read, if you flash the rom first, then update your recovery you should be good?
Sent from my Redmi Note 5 using Tapatalk
Click to expand...
Click to collapse
Yeah sure
gursewak.10 said:
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
Click to expand...
Click to collapse
does this version support f2fs? Thanks in advance.
sushuguru said:
does this version support f2fs? Thanks in advance.
Click to expand...
Click to collapse
Yes it supports.
Remember to backup internal storage before changing file system.
Thanks bro it works like charm
Working good but after the restart the twrp is gone, stock recovery gets replaced
I tried to flash then no-verity-opt-encrypt-6.0.zip but getting error not installing
Please tell me what to do now, twrp is replacing by stock recovery
Update - It is resolved now, I flashed magisk over it and twrp is not replaced anymore
gursewak.10 said:
This work is not mine. Just sharing.
Most of the users of whyred has updated to miui10 pie update 9.3.28 but finding data encrypted on recovery boot.and are unable to decrypt it.
Try this recovery file in the link and the data partition works fine without any password problem.
TWRP
https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
Orangefox TWRP
https://sourceforge.net/projects/or...OrangeFox-R9.0-2-whyred-MIUI-Pie.zip/download
(This version not compatible with oreo so use it for miui pie only)
https://youtu.be/1WnxULKjgdE
For xposed on miui 10 see here:
https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
Click to expand...
Click to collapse
Thank you for sharing.
Can I install it without magisk?Will it be gone after the device restarted without installing magisk?
Just info : Link updated https://github.com/GuaiYiHu/android...2.3.0-whyred/TWRP-20190330-3.2.3.0-whyred.img
it's a recovery so magisk is your choice if you want it or not.
ashish1989 said:
Working good but after the restart the twrp is gone, stock recovery gets replaced
I tried to flash then no-verity-opt-encrypt-6.0.zip but getting error not installing
Please tell me what to do now, twrp is replacing by stock recovery
Update - It is resolved now, I flashed magisk over it and twrp is not replaced anymore
Click to expand...
Click to collapse
I had this problem before. when you flash twrp, try to reboot to twrp again. then the twrp won't be flashed by stock recovery.
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
matusala said:
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
Click to expand...
Click to collapse
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Horgar said:
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Click to expand...
Click to collapse
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
matusala said:
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
Click to expand...
Click to collapse
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Horgar said:
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Click to expand...
Click to collapse
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
jackdubl said:
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
Click to expand...
Click to collapse
Magisk is systemless root maybe that's why it did that.
matusala said:
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
Click to expand...
Click to collapse
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Horgar said:
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Click to expand...
Click to collapse
Have you tried just booting twrp instead of flashing it?
jackdubl said:
Have you tried just booting twrp instead of flashing it?
Click to expand...
Click to collapse
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Horgar said:
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Click to expand...
Click to collapse
I seem to remember getting some strange messages while flashing Magisk, like it couldn't mount system or something. It was in red. It seemed bad but it also came after successfully flashing Magisk, so it said. Everything was working fine after I rebooted. All root apps working as normal.
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
jeffritz1 said:
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
Click to expand...
Click to collapse
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
junglism93 said:
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
Click to expand...
Click to collapse
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
is rooted Magisk on Android 10 or 11 with Pixel 1 possible?
jeffritz1 said:
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
Click to expand...
Click to collapse
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
YogaSlackers said:
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
Click to expand...
Click to collapse
Hey, almost a week late but hope it's still helpful. Yes I recommend the official 10 firmware with Magisk, flashed through a temporary TWRP.
I've been running this setup for months, I can use all my root apps, even Google Pay and Netflix no problem.
Hi Guys,
I have downloaded the android 10 update and have followed all the steps to make the OS updated and successfully with magisk.
And when everything was working with Android 10+Magisk I have flashed twrp via magisk and Magisk is gone.
When i try to flash that from TWRP. TWRP doesn't show my internal storage or any USB storage via OTP.
Can anyone please help to decrypt my storage in TWRP without losing data.
slst said:
Hi Guys,
I have downloaded the android 10 update and have followed all the steps to make the OS updated and successfully with magisk.
And when everything was working with Android 10+Magisk I have flashed twrp via magisk and Magisk is gone.
When i try to flash that from TWRP. TWRP doesn't show my internal storage or any USB storage via OTP.
Can anyone please help to decrypt my storage in TWRP without losing data.
Click to expand...
Click to collapse
Which TWRP did you use? Take the latest version
Kollachi said:
Which TWRP did you use? Take the latest version
Click to expand...
Click to collapse
I have 3.3.1-1 I assume thats the latest. I have got the magisk working. And I have tried removing screen lock tried adding back password(instead of pattern) but nothing is working for TWRP to detect encrypted storage. It usually asks for password to decrypt but i dont get that prompt. Can you please help me.
slst said:
I have 3.3.1-1 I assume thats the latest. I have got the magisk working. And I have tried removing screen lock tried adding back password(instead of pattern) but nothing is working for TWRP to detect encrypted storage. It usually asks for password to decrypt but i dont get that prompt. Can you please help me.
Click to expand...
Click to collapse
No it's the second version.
3.3.1-65 is the latest!
https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
Thanks it worked.
slst said:
Thanks it worked.
Click to expand...
Click to collapse
Hi, i had the same problem.
So what exactly are the steps after u have the latest twrp?
It's says about encryption password and it's your screen lock pin
Hi,
I would like to know if anybody encountered this. This is my second time encountering this issue. I was on 12.0.4 and received a notification to perform update to 12.4.0. After downloading and rebooting, my twrp launched and after a few seconds instead of flashing, it went to the main menu page. After that, the phone just goes to fastboot mode and refused to boot. My phone has been rooted with magisk. Much appreciated for experts inputs.
The only way for me to boot my phone is to do a clean flash using mi flash tool and fallback to the old version...
Thank you.
spicediablo said:
Hi,
I would like to know if anybody encountered this. This is my second time encountering this issue. I was on 12.0.4 and received a notification to perform update to 12.4.0. After downloading and rebooting, my twrp launched and after a few seconds instead of flashing, it went to the main menu page. After that, the phone just goes to fastboot mode and refused to boot. My phone has been rooted with magisk. Much appreciated for experts inputs.
The only way for me to boot my phone is to do a clean flash using mi flash tool and fallback to the old version...
Thank you.
Click to expand...
Click to collapse
V12.0.4.0.QJKMIXM is a android 10 stable rom and V12.2.4.0.RJKMIXM is a android 11 stable beta rom which has many bugs.
V12.2.4.0.RJKEUXM is a stable rom that you can flash with miflash(but EEA not global).
After successfully going to v12.2.4.0, now I am finding that my current TWRP 3.4.1b unable to decrypt the phone thus not able to root it. I guess I have to fall back to 12.0.4.0 to be safe... I was tempted to go to 12.2.4.0 due to android 11 but looks like it's too problematic now due to beta. I was actually wondering why beta was pushed to me.
NOSS8 said:
V12.0.4.0.QJKMIXM is a android 10 stable rom and V12.2.4.0.RJKMIXM is a android 11 stable beta rom which has many bugs.
V12.2.4.0.RJKEUXM is a stable rom that you can flash with miflash(but EEA not global).
Click to expand...
Click to collapse
"I was actually wondering why beta was pushed to me "
You are not the only one, many users have reported this problem to XDA and c.mi.com
Try xiaomi.eu_multi_HMK30Pro_V12.2.2.0.RJKCNXM_v12-11 better than stock and on android 11.
spicediablo said:
After successfully going to v12.2.4.0, now I am finding that my current TWRP 3.4.1b unable to decrypt the phone thus not able to root it. I guess I have to fall back to 12.0.4.0 to be safe... I was tempted to go to 12.2.4.0 due to android 11 but looks like it's too problematic now due to beta. I was actually wondering why beta was pushed to me.
Click to expand...
Click to collapse
Now it is a stable rom https://xiaomifirmwareupdater.com/miui/lmi/stable/V12.2.4.0.RJKMIXM/
seems to be the same
Try flashing stock recovery before performing ota update. Flashing ota via twrp cause /storage inaccessible for me.
Thanks, so you updated with stock recovery without issues but are you able to flash twrp with the updated rom?
kopter36 said:
Try flashing stock recovery before performing ota update. Flashing ota via twrp cause /storage inaccessible for me.
Click to expand...
Click to collapse
NOSS8 said:
"I was actually wondering why beta was pushed to me "
You are not the only one, many users have reported this problem to XDA and c.mi.com
Try xiaomi.eu_multi_HMK30Pro_V12.2.2.0.RJKCNXM_v12-11 better than stock and on android 11.
Click to expand...
Click to collapse
Is that the most stable android 10 based on miui? I'm thinking about downgrading to many android 11 bugs on 12.2.4.0 global
Latin_lion_ said:
Is that the most stable android 10 based on miui? I'm thinking about downgrading to many android 11 bugs on 12.2.4.0 global
Click to expand...
Click to collapse
This is not a stock ROM and it is a android 11.
spicediablo said:
Thanks, so you updated with stock recovery without issues but are you able to flash twrp with the updated rom?
Click to expand...
Click to collapse
Yes i am able to successfully flashed twrp via fastboot afterward and directly proceed to root using magisk.
Everything works as usual, except, for me atleast, twrp now require pattern-type (3x3 dot) as password for decryption. Pin or character doesnt works.
Deleted.
To solve update problem you need to Rollback to stable stock rom, I used this:
Code:
lmi_global_images_V12.2.4.0.RJKMIXM_20201228.0000.00_11.0_global
extracted it.
then used mi flash from this toolkit:
Code:
mi-globe.com_Xiaomi_MiFlash_Pro_EN_5.3.1104.39.exe
sorry, but I cant provide links to downloads.
Moribus said:
To solve update problem you need to Rollback to stable stock rom, I used this:
Code:
lmi_global_images_V12.2.4.0.RJKMIXM_20201228.0000.00_11.0_global
extracted it.
then used mi flash from this toolkit:
Code:
mi-globe.com_Xiaomi_MiFlash_Pro_EN_5.3.1104.39.exe
sorry, but I cant provide links to downloads.
Click to expand...
Click to collapse
This is nothing new. With the bootloader unlock you can flash any version of stock rom with miflash.
kopter36 said:
Yes i am able to successfully flashed twrp via fastboot afterward and directly proceed to root using magisk.
Everything works as usual, except, for me atleast, twrp now require pattern-type (3x3 dot) as password for decryption. Pin or character doesnt works.
Click to expand...
Click to collapse
Successfully updated to 12.2.4.0. However, my nova launcher has been 'uninstalled' after this upgrade and I am unable to reinstall it with install fail error coming up. I am installing from apk. Anybody has this issue?
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.