Database Develop

TWRP, Root, CN vs EU...Confusion!

OK, I need some clarification please. I just ordered the phone on Swappa and will have it soon but I would like to have a plan in place for reaching my goal...A rooted phone with TWRP (don't know about what ROM yet)
I'm not sure what software will be on this phone when I get it (EU or Chinese stock/dev) but does that make a difference when attempting to put TWRP on the phone? Also, are there still 2 separate versions or is there just one now?
Also in regards to the initial root and TWRP procedure is it not possible to have SU zip on your phone beforehand or does it have to be transferred from your computer while in TWRP? Finally, the verity no opt encrypt zip must be flashed regardless of whether you are rooting or not? Many thanks for any and all help!

SantinoInc said:
I'm not sure what software will be on this phone when I get it (EU or Chinese stock/dev) but does that make a difference when attempting to put TWRP on the phone? Also, are there still 2 separate versions or is there just one now?
Click to expand...
Click to collapse
Presently if you read max of the posts in major of the forums, you will find out there are three versions of ROM majorly (removing Chinese dev from the list as many don't seem to be on this) - If you are buying the phone from a reseller and not directly from xiaomi, mostly you will end up with Vendor ROM
1) Vendor ROM global (8.08.0 something version) which comes with very less bloatware and Google play services. Sometimes people said their bootloader was unlocked and for some its not. (mine was locked, so had to apply for unlock - It took 3 days to get the approval).
PLEASE NOTE THAT MANY TIMES THIS VENDOR ROM HAS A "NOTES APP" WITH TROJAN ON IT. MALWARE BYTES DETECTS THIS. HENCE I DECIDED TO GET OFF IT.
2) Chinese stable ROM - The official miui ROM. It has OTA updates but comes with bloatware and quite cumbersome to use for a non Chinese person like me or thats what I felt. If you really want to use Chinese stable (and still need google apps) there is a guide which is available some where in one of the forums, right now can't get hold of it somehow.
3) EU ROM (weekly updates - I believe to be done manually) - This one is so far the best I have used and very less bloatware (there is "Qunar travel" and one Chinese app that came with it. I simply uninstalled them blindly). Comes with google play services and you can download the rest from google store.
My journey so far is Vendor ROM --> Chinese Stable --> EU ROM (Non-root)
Why i didn't go directly from Vendor ROM to EU ROM is because
1) some of the users had issues with TWRP's touch non-responsiveness.
2) I want to see what is there on Chinese Stable before going to EU ROM, so that I can do a comparison.
For Vendor ROM to Chinese Stable use the guide below (by @satishp)
https://forum.xda-developers.com/mi-mix/how-to/kindly-help-flashing-to-china-stable-t3528652
For Chinese Stable (or if you want to try from Vendor ROM directly to EU ROM) to EU ROM use the guide below (by @underlines)
https://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592
Following the steps exactly in the above two guides, I was able to install EU ROM without any issues.
SantinoInc said:
Also in regards to the initial root and TWRP procedure is it not possible to have SU zip on your phone beforehand or does it have to be transferred from your computer while in TWRP?
Click to expand...
Click to collapse
When you enable developer options on your phone and enable USB debugging, then I believe when you connect your phone to laptop/desktop it should connect using MTP and should be seen as device. So I guess you can copy the zip before hand on to the phone.
SantinoInc said:
Finally, the verity no opt encrypt zip must be flashed regardless of whether you are rooting or not? Many thanks for any and all help!
Click to expand...
Click to collapse
All the guides mention that whenever you want to install the EU ROM without root, the dm-verity is compulsory to flash before reboot.
Hope this helps!!. Enjoy your MIX.

thehearty said:
Presently if you read max of the posts in major of the forums, you will find out there are three versions of ROM majorly (removing Chinese dev from the list as many don't seem to be on this) - If you are buying the phone from a reseller and not directly from xiaomi, mostly you will end up with Vendor ROM
1) Vendor ROM global (8.08.0 something version) which comes with very less bloatware and Google play services. Sometimes people said their bootloader was unlocked and for some its not. (mine was locked, so had to apply for unlock - It took 3 days to get the approval).
PLEASE NOTE THAT MANY TIMES THIS VENDOR ROM HAS A "NOTES APP" WITH TROJAN ON IT. MALWARE BYTES DETECTS THIS. HENCE I DECIDED TO GET OFF IT.
2) Chinese stable ROM - The official miui ROM. It has OTA updates but comes with bloatware and quite cumbersome to use for a non Chinese person like me or thats what I felt. If you really want to use Chinese stable (and still need google apps) there is a guide which is available some where in one of the forums, right now can't get hold of it somehow.
3) EU ROM (weekly updates - I believe to be done manually) - This one is so far the best I have used and very less bloatware (there is "Qunar travel" and one Chinese app that came with it. I simply uninstalled them blindly). Comes with google play services and you can download the rest from google store.
My journey so far is Vendor ROM --> Chinese Stable --> EU ROM (Non-root)
Why i didn't go directly from Vendor ROM to EU ROM is because
1) some of the users had issues with TWRP's touch non-responsiveness.
2) I want to see what is there on Chinese Stable before going to EU ROM, so that I can do a comparison.
For Vendor ROM to Chinese Stable use the guide below (by @satishp)
https://forum.xda-developers.com/mi-mix/how-to/kindly-help-flashing-to-china-stable-t3528652
For Chinese Stable (or if you want to try from Vendor ROM directly to EU ROM) to EU ROM use the guide below (by @underlines)
https://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592
Following the steps exactly in the above two guides, I was able to install EU ROM without any issues.
When you enable developer options on your phone and enable USB debugging, then I believe when you connect your phone to laptop/desktop it should connect using MTP and should be seen as device. So I guess you can copy the zip before hand on to the phone.
All the guides mention that whenever you want to install the EU ROM with/without root, the dm-verity is compulsory to flash before reboot.
Hope this helps!!. Enjoy your MIX.
Click to expand...
Click to collapse
Wow, thank you so much for that very thorough answer! I will be getting the phone tomorrow and my goal will be to get the EU Rom on my phone with TWRP and Xposed.
One more small question. So if I happen to get the touch screen freeze (in TWRP or after system reboot) how do you recover from this situation?

SantinoInc said:
One more small question. So if I happen to get the touch screen freeze (in TWRP or after system reboot) how do you recover from this situation?
Click to expand...
Click to collapse
I believe you have to go to Chinese Stable then using MiFlash or install one more version of TWRP which is compatible with Chinese ROM and then other steps. (one of the guides mentions these too)
But my suggestion is simply follow the steps in both the guides, go to chinese stable and then to EU ROM. Its worth the 15 min extra effort as surely i can tell this will not have problems and I believe you can definitely got to root/xposed too finally.
There is a small typo in my previous answer (I corrected it now). Sincere apologies for the same.
Dm-verity is not needed if you are going to root. If you flash to EU ROM and don't want root, then install dm-verity. This is as per the guide mentioned in my last answer.
Hope this helps.

Help requested with updating Custom ROM.

Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!

Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.

Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?

Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.

DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,

Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.

DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs

Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,

Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.

Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!

Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.

Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.

Anyone got a working TWRP for Mi 8 global? MIUI 10.

As title. I've tried like 5 different TWRP versions linked from all over the Mi 8 forums and none have worked for me. Any and all versions have made the ROM unable to boot, every restart will load recovery instead and I have to flash stock boot to get the ROM to work. Bootloader unlocked, ROM rooted by having Magisk create a patched boot cos every other way also failed.

I'm also looking for it.
ArmedandDangerous said:
As title. I've tried like 5 different TWRP versions linked from all over the Mi 8 forums and none have worked for me. Any and all versions have made the ROM unable to boot, every restart will load recovery instead and I have to flash stock boot to get the ROM to work. Bootloader unlocked, ROM rooted by having Magisk create a patched boot cos every other way also failed.
Click to expand...
Click to collapse
Currently https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745 this version working but you've to format all of your data then flash your rom. I know its not the standard solution and even I'm waiting for official TWRP for our beloved Mi 8.

You need to choose Format Data first, Reboot again to Recovery, and then flash the DM Verity and Encryption Disabler.
After that, you can go ahead to flash any ROM you like.

mrnannu said:
Currently https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745 this version working but you've to format all of your data then flash your rom. I know its not the standard solution and even I'm waiting for official TWRP for our beloved Mi 8.
Click to expand...
Click to collapse
Aw man crap, I don't want to wipe my phone againt, bootloader unlock already did it ): I'll wait for a regular version of TWRP then thanks!
motherninja said:
You need to choose Format Data first, Reboot again to Recovery, and then flash the DM Verity and Encryption Disabler.
After that, you can go ahead to flash any ROM you like.
Click to expand...
Click to collapse
Thanks! It's more work than I want to deal with now, phone just got wiped from unlocking bootloader, I don't wanna go through another 5 hours of downloading and reinstalling everything.

ArmedandDangerous said:
Aw man crap, I don't want to wipe my phone againt, bootloader unlock already did it ): I'll wait for a regular version of TWRP then thanks!
Thanks! It's more work than I want to deal with now, phone just got wiped from unlocking bootloader, I don't wanna go through another 5 hours of downloading and reinstalling everything.
Click to expand...
Click to collapse
Believe me, it worth the efforts! It would be much better than staying with crappy MIUI 10 Global Stable.
Currently, I'm with MIUI EU 10.0.6.0 Stable and I don't want to go back to stock MIUI Stable, just don't forget to install Magisk 17.2 for root access, replace the GPS.conf with your preferred country server URL (I believed it should be Malaysia) - look for a thread by @RainGater for the complete walkthrough - and although it is not necessary, it would be better to edit the default Xiaomi EU build.prop to change the region to match your country (by default it is set to Romania or some EU country, I forgot)

motherninja said:
Believe me, it worth the efforts! It would be much better than staying with crappy MIUI 10 Global Stable.
Currently, I'm with MIUI EU 10.0.6.0 Stable and I don't want to go back to stock MIUI Stable, just don't forget to install Magisk 17.2 for root access, replace the GPS.conf with your preferred country server URL (I believed it should be Malaysia) and although it is not necessary, it would be better to edit the default Xiaomi EU build.prop to change the region to match your country (by default it is set to Romania or some EU country, I forgot)
Here, I uploaded the needed files to my personal Drive account to save your time, those are the files that I use personally for my Mi 8.
Click to expand...
Click to collapse
I don't actually have a problem with my ROM. My GPS works fine, and I've already gotten root on my stock Global. Right now in my journey with Android which started with the HTC Desire Z, I don't need a custom ROM, I just need root for the occasional app that needs it I do have root now, but would love TWRP too so I can make full backups. Will check out your links regardless, thanks!

Enabling encryption on Pixel Experience ROM

Hi everyone! I'm very much a newbie when it comes to custom ROM's, so apologies if this is a a dumb question...
I just managed to install the latest Pixel Experience ROM on my K20 Pro, from the stock Chinese ROM. Before installing it, I had to flash DFE. So, from my understanding, it is now blocking me from re-enabling encryption. I need to have encryption enabled for work email access, so is it possible to enable it somehow? I'm not worried about losing any data on the phone, but I would certainly prefer to use Pixel Experience than to go back to MIUI.
Per another forum thread I found, one member suggested to "reflash your vendor/firmware." Is that accurate? If so, how do I do that, and what would be the result?

shleepy said:
Hi everyone! I'm very much a newbie when it comes to custom ROM's, so apologies if this is a a dumb question...
I just managed to install the latest Pixel Experience ROM on my K20 Pro, from the stock Chinese ROM. Before installing it, I had to flash DFE. So, from my understanding, it is now blocking me from re-enabling encryption. I need to have encryption enabled for work email access, so is it possible to enable it somehow? I'm not worried about losing any data on the phone, but I would certainly prefer to use Pixel Experience than to go back to MIUI.
Per another forum thread I found, one member suggested to "reflash your vendor/firmware." Is that accurate? If so, how do I do that, and what would be the result?
Click to expand...
Click to collapse
Why did you have to flash DFE? It's only used if you change roms frequently to avoid encryption.

I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.

shleepy said:
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
Click to expand...
Click to collapse
Your best bet is to go back to stock and start again. I believe installing an official fastboot ROM will restore encryption. Your previous issues were probably caused by not formatting data when flashing PE.
There is no requirement to disable encryption on this phone, ignore any guide that adds that as a step. You should only disable encryption if it's your personal preference to disable it.
Follow this guide.
Flash the latest Chinese 11.0.5 fastboot ROM. Make sure you don't lock the bootloader if using the Mi Flash Tool.
Boot into MIUI once to allow it to finalise the install, you don't need to do the initial phone setup once it boots into MIUI.
Boot into fastboot and install TWRP. I recommend the latest from mauronofrio which should be 3.1.1-32
Boot immediately into TWRP. I use the volume up button while powering up the phone.
Perform a factory reset in TWRP (using the swipe button), then format data (need to type 'yes' to confirm).
Reboot into TWRP using the TWRP boot menu, this ensures the newly formatted data partition is correctly mounted.
Copy over the PE ROM, then flash.
Boot into your new ROM, everything should be OK. Then boot back into TWRP to install Magisk if you want root.

shleepy said:
I initially had trouble successfully installing the ROM. So, I started from scratch and followed some thorough instructions I found online, which included the DFE step. (I noticed that TWRP was previously showing an encryption error at the start of ROM installation; but I guess it could just be a "warning" more than an error. I suspect my problem before was probably more related to not having the latest MIUI update installed, or something like that.)
I don't plan on frequently swapping ROM's.
Click to expand...
Click to collapse
Do yourself a favour and follow the instructions in the description of the rom, not some instructions you found online telling you to do some unnecessary stuff. Going to and from miui, format data, everything else just wipe cache, system and data to avoid issues, even then you can get away with dirty flashing aosp based roms 99% of the time imo.
As for the miui update, I have no idea how you came to that conclusion but just no, that's not how it works at all. Vendor firmware and the rom is all you need for pixel experience at the bare minimum.

You can try flashing the rom again, but don't flash the DFE.

Question MIUI Rollback 13.0.17.0.SKFEUXM to 13.0.16.0.SKFEUXM

Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.

awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .

I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A

awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.

awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.

Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader​2. Flash any latest OSS ROM (this is just to remove MIUI)​3. Use MiFlash and fastboot method to install old versions (re-lock if you want)​Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.​​Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?

wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?

awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.