Related
Android Version : MIUI-11-EU-PIE Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working MIUI-11--EU-PIE running rom. With the help from Mohzuned. I have removed what I believe to be all of the bloat. We worked to modify a working pie vendor. Magisk v20 modified boot for root access, Just install magisk manager.
All Credit goes to respective developer/s. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to Test MIUI-11-EU-PIE on Mi Max 2 (Oxygen). This ROM recovery is ported from the Xiaomi RedMi with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile and MOST features I need are currently working.
1a. Treble Mi Max 2 Recovery 3.2.1 https://androidfilehost.com/?fid=5862345805528056270
1b. OrangeFox Recover 10
https://sourceforge.net/projects/ora...n.zip/download
2. MIUI-11-EU-PIE
https://drive.google.com/file/d/15lRb49s75rqVV0Kg8C16Eao_BuTPvBWr/view?usp=drivesdk
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 1-2 Minutes for first boot.
What works:
?
What doesn't work:
?
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb max HDD at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits.
Any Others Who May Have Been Missed
Best of Luck and Happy Flashing )
Camera/Torch.
Camera, fingerprint and fm radio, dont work, congratulations, good rom. Thanks.
Cool....... thanks dude
liammc83 said:
Camera/Torch.
Click to expand...
Click to collapse
Iam ready for the test ride......
I will test today. Thank you for your job!
Beast developer...too fast man thanks
If you will fix Camera and Torch it will be great! We are all waiting! Thank you!
---------- Post added at 06:51 AM ---------- Previous post was at 06:38 AM ----------
May be it is better to do Port from Mi Mix 2S? Camera and Torch worked on that port.
Bro.......
I cannot find the fingerprint option in the rom..?
Firstly I upgraded from the nougat rom.,it made me to suck....it booted but instantly rebooted to recovery on every boot......
Cannot find the fingerprint option ..,Cannot add the face unlock option due to the camera bug...,it's harder always using pattern/pin.,? flashlight ? issue is negligible.....
But mi cloud has no issues and working fine able to login..
Home button isn't working.,full screen guesture option isn't seen in the rom..
May be it's because of the redmi note 4x....it might be good if it's from max3 or mix2s as u done previously.,only hotspot bug majorly
You are too good bro....,you are beastly fast and tough..,???
Please fix the camera!!!
zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
He is trying continuously and I believe soon it will be resolved.
zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
I'm not screaming "Donate!!!!!"
I do this for free for a phone I no longer use, please be patient.
Considering all sources from xiaomi are outdated, And this is being done again for FREE with modifications on an ancient netbook.
I also can now verify, I have a working modified vendor/boot image that will run gsi images, But again since problems with vendor no camera, Still working on it.
Sorry, I just asked. I understand your position and ready to test new changes
No need to wait for me to port.
https://forum.xda-developers.com/mi-max-2/development/mi-max-2-oxygen-gsi-bootable-vendor-t3987191
I really liked this rom .. I want to use daily ... only thing that is bothering me is the home button and the camera that is not working? already have a solution? fingerprint to taste .. but you can use with the pin normally
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
PriPhaze said:
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
Click to expand...
Click to collapse
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Robbo.5000 said:
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Click to expand...
Click to collapse
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then flash DM verity again with the force encryption on?.
PriPhaze said:
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then glad DM verity again with the force encryption on?.
Click to expand...
Click to collapse
Ordinarily you shouldn't need to flash dm-verity. And as far as I'm aware, there is still no need to.
Normally it's just a case of formatting data to temporarily remove encryption, if flashing over MIUI.
As to your specific question, I couldn't say, as I've never needed to flash a dm-verity, disable force encrypt, or vbmeta file/script.
Personally, I would flash the latest fastboot MIUI ROM for the phone, then reinstall EvoX.
Before installing the ROM, in TWRP do the factory reset and then format data (There is no need to wipe anything else). Then reboot into TWRP to ensure the newly formatted data partition is properly mounted and flash as normal.
This has worked for me every time.
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Sandeeep Kiran said:
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Click to expand...
Click to collapse
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Robbo.5000 said:
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Click to expand...
Click to collapse
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Numerous cases? Who's we? What roms on what devices need dfe then? Only seen 2 roms ask for dfe, everything else it's as easy as 'going to and from miui, format data and reboot recovery' works every single time.
Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Try this next time you see somebody saying they have tried may things and always get bootloops when trying to flash an AOSP ROM and you want to advise them to flash dfe.
Instead tell them to flash the latest MIUI fastboot ROM for their device, then install TWRP, in TWRP do a factory reset followed by format data, then reboot into TWRP and flash the ROM.
I bet they will come back and tell you it worked.
Again there should be zero need to flash dfe scripts.
If there are any AOSP ROMs out there that genuinely won't boot without flashing dfe (and here I'm talking about all users of such ROM), then the dev had done something stupid and everyone should seriously avoid the ROM.
At least half of the 50+ ROMs are no longer actively maintained.
The vast majority of Orange Fox extra features are specific to MIUI and so are redundant for AOSP ROMs. Mauronifrio's latest TWRP is the most stable for this phone, so if you're going with AOSP ROMs then the extra stability makes most sense.
I've been aware that mauronifrio does not own this phone ever since his initial build. I was also aware back then that he is also an official TWRP maintainer for other devices and so would mostly likely become the maintainer of the official version for this phone, which has now happened. If you go to the official TWRP site and download for this phone, it is by mauronifrio. You can also download the official version from the OP of his TWRP thread.
I would suggest that in most cases, people getting error 7 issues are not on the latest mauronofrio TWRP build.
Are you aware that all these different recoveries are just TWRP with a fancy dress. This is the great thing about TWRP. It was designed to be extensible, to allow others to build on it, in terms of functionality and design. So really there is only TWRP, just many different flavours.
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Ezio553 said:
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Click to expand...
Click to collapse
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Robbo.5000 said:
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Click to expand...
Click to collapse
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Ezio553 said:
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Click to expand...
Click to collapse
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Robbo.5000 said:
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Click to expand...
Click to collapse
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Ezio553 said:
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Click to expand...
Click to collapse
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Robbo.5000 said:
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Click to expand...
Click to collapse
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Ezio553 said:
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Click to expand...
Click to collapse
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Robbo.5000 said:
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Click to expand...
Click to collapse
Thanks for the info.
I tried custom miui rom and well flashing dfe worked fine so i think its just for official miui.
Hey guys,
as my last phone was an OPO where flashing custom roms was pretty simple, I don't understand the principle of flashing the Mi 9T Pro, where you always have to consider and install separately the right version of firmware, vendor etc. I would be thankful if someone could explain it to me.
I try to order my questions:
Why are ROM, firmware and vendor separated and don't come together in a single file?
How do I find out the correct version of firmware for my phone? And what is the difference between those versions, eg. China, Global and EU? And is EU the same as EEA?
The recommendation is always to update the firmware when flashing a ROM - but for vendor it is not (like for LineageOS 18.1) - why? Wouldn't it be beneficial to update vendor, too? As I understand, vendor contains necessary proprietary binaries.
Is it recommended to regularly update the firmware even if there is no update for my ROM? And what is the most comfortable way, is something like OTA possible?
What is different about TWRP images with a "_9"? (twrp-3.5.0_9-0-raphael.img vs. twrp-3.4.0-0 or -1). Recently broke the recovery of my OPO when I installed its latest twrp version which had the 9
Thank you for helping an interested person with little IT/android knowledge
oriped said:
Hey guys,
as my last phone was an OPO where flashing custom roms was pretty simple, I don't understand the principle of flashing the Mi 9T Pro, where you always have to consider and install separately the right version of firmware, vendor etc. I would be thankful if someone could explain it to me.
I try to order my questions:
Why are ROM, firmware and vendor separated and don't come together in a single file?
How do I find out the correct version of firmware for my phone? And what is the difference between those versions, eg. China, Global and EU? And is EU the same as EEA?
The recommendation is always to update the firmware when flashing a ROM - but for vendor it is not (like for LineageOS 18.1) - why? Wouldn't it be beneficial to update vendor, too? As I understand, vendor contains necessary proprietary binaries.
Is it recommended to regularly update the firmware even if there is no update for my ROM? And what is the most comfortable way, is something like OTA possible?
What is different about TWRP images with a "_9"? (twrp-3.5.0_9-0-raphael.img vs. twrp-3.4.0-0 or -1). Recently broke the recovery of my OPO when I installed its latest twrp version which had the 9
Thank you for helping an interested person with little IT/android knowledge
Click to expand...
Click to collapse
If you stick with stock ROMs, you don't need to worry anout firmware, vendor, etc.
You update by OTA or by downloading the so-called zip/recovery package that can be installed by the stock recovery or from TWRP
Only in rare occasions (usually when people screw something, want to go back from custom ROMs and so), you would need Xiaomi Flash tool and the so-called tgz/fastboot packages.
They include vendor and again, you don't need to worry about downloading and flashing vendor
How (and do you really) need downloading and flashing vendor for LOS, I have no idea (I don't use AOSP ROMs)
What do you mean by Eu?
If you mean Xoaomi.eu ROMs - they are not the same as stock EEA ROMs.
Actually, Xiaomi.eu IS NOT stock or even not an official ROM endorsed by Xiaomi Inc.
Personally, I started on my Mi 9T two years ago with A9/MIUI 10 (I think). Mine was EEA and I followed the updates till A10/MIUI 11.
From the beginning I unlocked Bootloader, played with various versions and incarnations of TWRP, I always rooted my phone with the latest (Canary) Magisk, played with debloating, various Magisk modules, etc.
I also played with Kali Nethunter at the time
Never in my carrier I needed to use Xiaomi Flash tool and tgz/fastboot firmwares (specially not vendor packages), always only zip/recovery ROM packages were enough for me
A year ago I moved to Xiaomi.eu weeklies. A month ago I decided it was enough and settled to Xiaomi.eu but Stable.
Xiaomi.eu, both weeklies and stable are built on A11/MIUI 12.5 (recently stock was finally also updated to A11/MIUI 12+ but I didn't return to stock)
Since 'official' Magisk is kind of 'dead' for 5 or so months, for the last two months I play with Magisk Alpha (recently incl. Zygisk and so)
Again, I have no experience (and no interests at all) about AOSP and GSI ROMs, particularly the LOS (in my past life with another phone, I used an earlier version of LOS for quite some time there)
Some links maybe of interest for you to read/learn from:
https://c.mi.com/thread-1857937-1-1.html
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
[INFO] Widevine L1 Support
This thread should answer most of your questions regarding Widevine L1 support on your device(s). I will try to keep it maintained and up-to-date. Notes: * This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu...
xiaomi.eu
What the letters in the MIUI version designation mean
MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...
xiaomi.eu
PS: Yeah, I am from Mi 9T (not Pro) world, but your questions and my comments and links are common and more general (not limited to Mi 9T Pro or plain, or to MI 9 *** range of models, but general for Xiaomi devices)
But if you meant EU letters in the stock ROM name - then yes, EU means European and that is EEA stock ROM
Similarly like MI letters (probably abbreviated from MIUI) in the stock ROM name mean International - see the attachement
Btw, this app might be also useful (not only for newbies):
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Open your Settings/My Device/MIUI Version (top left), aka System Updater app, read the full name of your stock ROM and compare against the attached chart
Thank you!
One more question: How do I change magisk to vvb2060 alpha version?
oriped said:
Thank you!
One more question: How do I change magisk to vvb2060 alpha version?
Click to expand...
Click to collapse
His Github page where you can download the 'latest official' Alpha:
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Newer, unofficial (I'm on the latest) can be downloaded here:
Magisk alpha
带遥测的第三方Magisk版本，比Canary通道更加不稳定，与上游行为有较大不同，无安全性保证，无可用性保证，无隐私协议。 问题反馈请加群发送日志文件，非alpha独有问题建议先在GitHub反馈。
t.me
You download and install Magisk (Alpha) apk (formerly, in Magisk v22 it was Magisk mngr)
If you are already rooted, you can take then Direct install to 'upgrade' to the same Magisk Alpha version
If you were not rooted yet, you can patch your boot.img (it can be extracted from your zip/recovery or tgz/fastboot stock ROM), later you will flash that patched img by Fastboot.
Instead of boot.img, you can patch boot.emmc.win Boot backup from TWRP
You can also rename magisk apk file (that Magisk Alpha app you downloaded) to install.zip and flash through TWRP (old school for those who are accustomed to flash Magisk zip through TWRP).
If you have the latest 3.5.-9 official TWRP, you don't even need to rename, you can flash as it was downloaded as magisk apk file
But be aware that Magisk Alpha has no more MagiskHide, instead it is now DenyList.
And configuring DenyList to pass SafetyNet is another (short) story
zgfg said:
If you stick with stock ROMs, you don't need to worry anout firmware, vendor, etc.
You update by OTA or by downloading the so-called zip/recovery package that can be installed by the stock recovery or from TWRP
Only in rare occasions (usually when people screw something, want to go back from custom ROMs and so), you would need Xiaomi Flash tool and the so-called tgz/fastboot packages.
They include vendor and again, you don't need to worry about downloading and flashing vendor
How (and do you really) need downloading and flashing vendor for LOS, I have no idea (I don't use AOSP ROMs)
What do you mean by Eu?
If you mean Xoaomi.eu ROMs - they are not the same as stock EEA ROMs.
Actually, Xiaomi.eu IS NOT stock or even not an official ROM endorsed by Xiaomi Inc.
Personally, I started on my Mi 9T two years ago with A9/MIUI 10 (I think). Mine was EEA and I followed the updates till A10/MIUI 11.
From the beginning I unlocked Bootloader, played with various versions and incarnations of TWRP, I always rooted my phone with the latest (Canary) Magisk, played with debloating, various Magisk modules, etc.
I also played with Kali Nethunter at the time
Never in my carrier I needed to use Xiaomi Flash tool and tgz/fastboot firmwares (specially not vendor packages), always only zip/recovery ROM packages were enough for me
A year ago I moved to Xiaomi.eu weeklies. A month ago I decided it was enough and settled to Xiaomi.eu but Stable.
Xiaomi.eu, both weeklies and stable are built on A11/MIUI 12.5 (recently stock was finally also updated to A11/MIUI 12+ but I didn't return to stock)
Since 'official' Magisk is kind of 'dead' for 5 or so months, for the last two months I play with Magisk Alpha (recently incl. Zygisk and so)
Again, I have no experience (and no interests at all) about AOSP and GSI ROMs, particularly the LOS (in my past life with another phone, I used an earlier version of LOS for quite some time there)
Some links maybe of interest for you to read/learn from:
https://c.mi.com/thread-1857937-1-1.html
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
[INFO] Widevine L1 Support
This thread should answer most of your questions regarding Widevine L1 support on your device(s). I will try to keep it maintained and up-to-date. Notes: * This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu...
xiaomi.eu
What the letters in the MIUI version designation mean
MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...
xiaomi.eu
PS: Yeah, I am from Mi 9T (not Pro) world, but your questions and my comments and links are common and more general (not limited to Mi 9T Pro or plain, or to MI 9 *** range of models, but general for Xiaomi devices)
Click to expand...
Click to collapse
Hi I'm K20pro/Mi 9t pro user currently on latest 12.5.1.0 raphael stock rom, can you give bit of advice about going to eu stable rom(12.5.6.0 latest) from stock miui. I do have orange fox recovery installed but confused about what to wipe(dalvik/cache/...other options) or format data(yes confirmation option) and if rom flash needs to be in clean internal storage via format data(yes confirmation option), will i need latest firmware with it or just eu rom.
After that i will install magisk
I'm pretty much new custom roms with just a week of 35-40 hours of research, I will be glad if you or anyone reading this, willing to clear my doubts.
Thank you in advance
jacksterky said:
Hi I'm K20pro/Mi 9t pro user currently on latest 12.5.1.0 raphael stock rom, can you give bit of advice about going to eu stable rom(12.5.6.0 latest) from stock miui. I do have orange fox recovery installed but confused about what to wipe(dalvik/cache/...other options) or format data(yes confirmation option) and if rom flash needs to be in clean internal storage via format data(yes confirmation option), will i need latest firmware with it or just eu rom.
After that i will install magisk
I'm pretty much new custom roms with just a week of 35-40 hours of research, I will be glad if you or anyone reading this, willing to clear my doubts.
Thank you in advance
Click to expand...
Click to collapse
When switching to Xiaomi.eu (and generally when switching the ROMs) it's required to Format Data (not just to Wipe Data - fornatting does more than wiping)
More about downloading and installing Xiaomi.eu ROMs find on their forum, in the OP posts:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Better also Wipe Cache (Dalwik will be wiped as part of Data partition hence you can wipe it too but it won't matter)
You can use OF but make sure you use a recent/latest version, or use the latest official TWRP. More about the suitable custom recoveries can be found in the Forum/thread as above
Generally:
- backup your photos, docs, etc (transfer to PC)
- use Google to backup, some apps like Whatsapp provide backing up to clouds, etc
- With Xiaomi Cloud you can backup installed apps and their settings, Contacts, Call History, SMS, even WiFi passwords
- Download the ROM to Internal memory
- reboot to OF/TWRP and install (flash) the downloaded zip
- Wipe Dalwik and Cache (TWRP automatically offers upon installing)
- Do not reboot to System but go back in OF/TWRP and do Format Data (do not Format Data before flashing the zip because Formatting Data will wipe your Internal memory, hence it would also wipe your downloaded zip - although you could, but then flash the zip from OTG stick)
Then reboot to System, setup your new Android/MIUI, restore things...
zgfg said:
When switching to Xiaomi.eu (and generally when switching the ROMs) it's required to Format Data (not just to Wipe Data - fornatting does more than wiping)
More info about downloading and installing Xiaomi.eu ROMs find on their forum, in the OP posts:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Better also Wipe Cache (Dalwik will be wiped as part of Data partition hence you can wipe it too but it won't matter)
You can use OF but make sure you use a recent/latest version, or use the latest official TWRP. More about suitable custom recoveries can be found on the Forum/thread as above
Generally:
- backup your photos, docs, etc (transfer to PC)
- use Google to backup, some apps like Whatsapp provide backing up to clouds, etc
- With Xiaomi Cloud you can backup installed apps and their settings, Contacts, Call History, SMS, even WiFi passwords
- Download the ROM to Internal memory
- reboot to OF/TWRP and install (flash) the downloaded zip
- Wipe Dalwik and Cache (TWRP automatically offers upon installing)
- Do not reboot to System but go back in OF/TWRP and do Format Data (do not Format Data before flashing the zip because Formatting Data will wipe your Internal memory, hence it would also wipe your downloaded zip - although you could, but then flash the zip from OTG stick)
Then reboot to System, setup your new Android/MIUI, restore things...
Click to expand...
Click to collapse
I'll follow your instructions step by step.
Again thank you for your quick support, really appreciate your help
jacksterky said:
I'll follow your instructions step by step.
Again thank you for your quick support, really appreciate your help
Click to expand...
Click to collapse
Do not wipe any other partition, specially not Persist (you would loose DRM L1), modem, and so on.
Since you are on stock, all that is good and Xiaomi.eu will actually flash only to System and Vendor
You probably use pin or pattern for screen unlocking, you will need to enter the same when you boot to OF/TWRP that it can read Internal memory (later, when you Format Data it will be gone and you will have to setup your pin/pattern again once you boot to your new System)
First time you boot to the new System give it some time (might be slow at first, doing things in the background)
Xiaomi.eu 'hides' that Bootloader is unlocked, hence you will pass SafetyNet (i e., Device will be certified in Playstore) right away
You will also have DRM L1 (you may need to download the certificate, but that's easy)
When you later need to reboot to OF/TWRP, you don't need to struggle with key combos - in Xiaomi.eu, from System updater, when you open the top-right menu, you have Reboot to recovery option (root not needed)
Later you can think about rooting with Magisk, installing nodules, additionally debloating, etc
Be aware that raphael is on the end-of-line and it's not clear would it receive any more Xiaomi.eu updates (or if, then just a newer Security Patch).
But that's also the case with stock
zgfg said:
Do not wipe any other partition, specially not Persist (you would loose DRM L1), modem, and so on.
Since you are on stock, all that is good and Xiaomi.eu will actually flash only to System and Vendor
You probably use pin or pattern for screen unlocking, you will need to enter the same when you boot to OF/TWRP that it can read Internal memory (later, when you Format Data it will be gone and you will have to setup your pin/pattern again once you boot to your new System)
First time you boot to the new System give it some time (might be slow at first, doing things in the background)
Xiaomi.eu 'hides' that Bootloader is unlocked, hence you will pass SafetyNet (i e., Device will be certified in Playstore) right away
You will also have DRM L1 (you may need to download the certificate, but that's easy)
When you later need to reboot to OF/TWRP, you don't need to struggle with key combos - in Xiaomi.eu, from System updater, when you open the top-right menu, you have Reboot to recovery option (root not needed)
Later you can think about rooting with Magisk, installing nodules, additionally debloating, etc
Be aware that raphael is on the end-of-line and it's not clear would it receive any more Xiaomi.eu updates (or if, then just a newer Security Patch).
But that's also the case with stock
Click to expand...
Click to collapse
Okay i'll follow your given directions, I'll update you after installation, Thank you
I'm now on latest weekly build on eu rom, and it's butter smooth and i know this might be the last beta version for the raphael but experience is just flawless and new features work perfectly fine, again thanks for your instructions i'll remember them for future installations.
jacksterky said:
I'm now on latest weekly build on eu rom, and it's butter smooth and i know this might be the last beta version for the raphael but experience is just flawless and new features work perfectly fine, again thanks for your instructions i'll remember them for future installations.
Click to expand...
Click to collapse
Doesn't matter if it's last Weekly as long as you are satisfied with.
Btw, I thought you'd be little more conservative and go for Stable, but probably differences are minor
Stable is MIUI 12.6 (also A11) with Security patch Oct 1 - what are your parameters?
Also, check Widewine L1 certificate and update if neccessary:
Settings / Passwords and security / Fingerprint unlock / Fingerprint payments
Check do you have Widevine L1 cert.
If necessary, take Certificate update
Btw, you are ready now for Magisk, AdAway, Vanced YT, Viper4Android, CustoMIUIzer and so