Develop Bugs

Having trouble flashing custom ROM

Hi everyone
I have tried flashing a custom ROM. TWRP3.3.1 is installed and therefore bootloader unlocked. I tried flashing resurrection remix as per this guide:
1)Full wipe (system,data,vendor, dalvik,cache,internal storage) + format data.
2)Flash No-verity-opt patch + xiaomu.eu developer on Oreo or xiaomi.eu 10.2.1 Stable
3)Factory reset
4)Reboot to recovery
5)Flash Resurrected Kernel v3.3
6)Flash POST-sGSI_3_v0.6 .zip
7)Flash RR System.img
8)Flash Magisk 18.0 (if you get an error that /vendor can't be mounted then just reboot recovery and flash Magisk again)
9)Reboot to system
10)Setup system
11)Reboot to recovery
12)Flash BiTGApps or OpenGapps + Magisk 18.0
13)Reboot to system
Although I used Kernel 5.1 PIE
Before this attempt I tried Havoc and I tried lineage and it's always the same... flashing the system.img takes only seconds and declares success. Then the boot screen of the respective ROM stays forever.
I just flashed xiaomi.eu ROM 10.2.1 and that boots fine.
What am I missing here?
Thanks!

Also I don't seem to have anti rollback protection enabled (or I guess I would have bricked the phone anyway by now):
getvar:anti FAILED (remote: GetVar Variable Not found)

Looks like nobody has this phone seeing as there is no official custom ROM development... interesting considering the thread about the 6GB version has 13k views....

Marco2G said:
Looks like nobody has this phone seeing as there is no official custom ROM development... interesting considering the thread about the 6GB version has 13k views....
Click to expand...
Click to collapse
Custom Rom development seems to have started very recently after the statement of XIAOMI that there will not be a MAX 4 this year.
But from what I've seen so far, most people are on some kind of MIUI Custom Rom and only a few went the route of trying a more AOSP like Custom Rom.
Regarding your statement that you don's seem to have Anti Rollback Protection, I am 100% sure this is wrong. I've seen threads about that topic that asked why they can't get the ARP value anymore with the method you used and if I recall correctly there was a different way of doing it.
Cheers

I just managed to solve my issues.
I installed the patched TWRP for Nitrogen https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
Interestingly enough, installing a custom ROM image still only takes about ten seconds or so. But now the stuff actually boots.
The Xiaomi.eu ROM that Tradingshenzhen packaged in their tutorial does not have ARB yet. I believe the latest ROMs do.

Look inside your ROM for antiroll the same say to me not found but the beta stock ROM have the 4. This is stopping me to do anything on this phone. Never buy xiaomi again. They add this stupid antiroll they stop betas they make always year after year the phones cheaper.. I mean they remove custom led rgb only white then they make it so small you can't see it. To have the phones cheap they go down on quality

Installing GSI ROMs on Mi8 Pro

The below is a guide to installing GSI images on the Mi 8 Pro. I specifically have experience with the PixelExperience 9.0 (Unofficial) but have had other GSI ROMs booting and working. I hope this is useful for some.
GSI (Generic System Image) ROMS can be flashed to any Project Treble enabled device. These devices have either an A/B partition layout (these allow for seamless updating as the system can boot from A or B partition) or just an A only partition layout. The Mi 8 Pro is an arm64 a only device and support project treble ROMs. You can choose from suitable ROMs listed here and here.
The instructions given below are for Android Pie (9.0). The same basic setup can be used for Android Oreo (8.0, 8.1) ROMs, but the Mi 8 Pro should be flashed with the appropriate Xiaomi base ROM first before flashing any 8 based GSI ROM
As the ROM development for the Mi 8 Pro is basically dead, I decided to buy a OnePlus 6T and sell my Mi 8 Pro. However, due to having my new OnePlus 6T stolen, and due to a lack of funds to buy a new device, I have revived my Mi 8 Pro to try to get something other than MIUI working on it. I now have The PixelExperience (Unofficial) GSI ROM running very smoothly on my Mi 8 Pro.
As the PixelExperience team has stated they will be delivering GSI images again, if there are enough of us asking, we could get better support for things like the fingerprint sensor, for a more complete experience.
Some of the below steps may be unnecessary, but are there for a complete beginner's guide to doing this and getting the right results.
Working:
WiFi
Bluetooth (with APTX)
NFC (Including Google Pay)
RIL
Mobile data (LTE / HSPDA / 3G / EDGE)
GPS
Camera (with camera built in to ROM, as well as some GCAM implementations)
Video Camera (not working on GCAM implementations tested so far - only working on Camer built in to ROM)
Flashlight
Sound / Vibrations
Face Unlock
Hotspot
Not Working:
VoLTE (I have had it working, but unable to end phone calls and problems receiving SMS messages, so reverted)
Fingerprint (There is some support. The fingerprint area of the screen lights up when trying to enrol a new fingerprint. The screen dims when a finger is placed on the sensor, and a green light us emitted from the sensor area, but it does not register the fingerprint and this is not currently working.)
Notification LED
You Tell Me
How to install
Flash the latest Fastboot Global Stable Android PIE (9.0) ROM for the Mi 8 Pro. (eg. equuleus_global_images_V10.3.4.0.PECMIXM_20190712.0000.00_9.0_global_9a181f79c1.tgz) using the Xiaomi Tool.
Update: Use the latest MIUI system. The contents of the vendor partition are important. The most compatible vendor partition as of 2019-08-19 is from equuleus_global_V10.3.5.0.PECMIXM. You can download and flash that vendor independantly, if you have already set up your GSI image.
Reboot and finish basic MIUI setup.
Reboot to recovery.
[*]Format data (Wipe - Advanced - format data - confirm by typing yes)
DO NOT FORMAT DATA. Just perform a factory reset. Formatting data can cause issues and prevent booting.
Wipe Cache - Dalvik Cache and System
Reboot recovery
Use adb to push PixelExperience GSI image (img file extracted from download) and latest version of Magisk to root of SDCard. (Empty due to formatting data).
("adb push c:\path\system.img /sdcard/" and then "adb push c:\path\Magiskv19.3.apk /sdcard/")
Flash the image to system partition by taping INSTALL and then on the "Install Image" button (to toggle between flashing zip and img files). Do not reboot yet.
Flash magisk zip in the normal way (hit the same button as in previous step to show zip files to flash. (This is necessary to avoid bootloops)
Reboot, and enjoy.
You can now set up your "PixelExperience" device with your apps and settings, including registering a face for face unlock.
To pass cts validation for the safetynet and to allow service such as Google Pay to work
In Magisk, under settings - Find “Magisk Hide” and toggle the switch on
Magisk restarts. Go to Magisk Hide from the Magisk menu and ensure that...
Google Pay
Google Play
Google Play Services
Google Service Framework
Any Banking Apps
...are checked so that they cannot see Magisk (canont see phone as rooted).
Now go to downloads and install the SafetyPatch v3 module (created by hackintosh5).
Reboot.
Open settings - go to apps and notifications - and find the above apps to clear all data.
Enjoy your rooted safetynet compliant, as close to stock as possible Xiaomi Mi 8 Pro.

nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!

axelgrox said:
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
Click to expand...
Click to collapse
Face unlock works fine. I have it paired with Pick to wake phone - so when I pick it up it wakes up to allow face unlock.
However, be prepared for some investment of time (not for face unlock).... I am a bit stuck now and cannot reproduce the above to get this working. Sometimes the results are different depending on base ROM etc.
Share how you get on and anything you may need to do to get this working.
Thanks

Nice work, i will try it .
The mi8 pro 's fingerprint is so bad which can be ignored, and the face unlock is the mostly used, hahahah
thank you very much for your work

Hi, I am waiting to unlock bootloader. Need 148hrs. Will install this. Thanks for sharing.

Quick update: There are some issues with GSI ROMs and the Mi 8 Pro. SOe of these relate to the SIMcard settings - and selection of preferred SIM for data, calls etc.
My experience shows that the vendor image from equuleus_global_V10.3.5.0.PECMIXM fixes many of these. The vendor image from the original MIUI ROM is used with the GSI system image to make the whole Project treble stuff work. I advise flashing this latest vendor image for maximum compatibility.

Do you know what issues remain after flashing the latest vendor image?

Does the face unlock on Pixel Experience work with IR camera or front cam?

I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!

eremeya said:
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
Click to expand...
Click to collapse
Have experienced this on occasion also.
What GSI image have you tried? after my multiple efforts, I would recommend... in this order: Omni. HavocOS, Descendant(no future updates), PIxelExperience. I am hopeful about the PixelExperience team who have made an announcement that as of August they will no longer produce CAF versions of PixelExperience, and that they will maintain regular GSI builds also. PE official GSI - I am full of hope.
Anyway, back on topic: Try this.
Follow the instructions - a few precisions:
Use XiaoMiFlash to flash the equuleus_global_images_V10.3.4.0 as a base. You can update the vendor partition once you have GSI up and running, but don't let the MIUI update to 10.3.5. Ensure you define a PIN to make sure that data partition is encrypted. (everyone should use encryption nowadays, and besides, I have had bad experiences whn using a xiaomi eu or mi-globe ROM (unencrypted) as the base
Reboot and finish basic MIUI setup. - What I mean here is to let the ROM boot, don't have to sign in to Google or Mi, but get to the home screen after the initial setup.
Then reboot fastboot and flash TWRP 3.3.0. Search for TWRP-3.3.0-0504-XIAOMI8UD-CN-wzsx150.zip.
Boot to TWRP. Make sure that you are able to decrypt the data partition with the PIN you set earlier. If TWRP does not ask you for the passcode / PIN - something is wrong. Try again. ONce all is OK in TWRP, perform factory reset. (DO NOT FORMAT DATA for the aforementioned encryption reason).
adb push the img file.
adb push the Magisk 19.3 zip.
Flash both in TWRP
Reboot TWRP
Reboot system. If it appears to hang, after 5 minutes you can force restart with the power button. I have had the ROM boot OK after second boot only?
Pretty sure that if you strictly follow the above you should get a working GSI image on Mi 8 Pro. Let me know...
It's a bit flaky to set up, but once set up, apart from fingerprint sensor not working, very stable and lovely to have the stock ish android system on a MIUI phone!
Be careful with preferred network type for mobile network as some selections have messed up incoming SMS messages for me... a dealbreaker.
What happens when you flash Magisk? What does TWRP say? Have you tried flashing Magisk, rebooting TWRP, and flahing Magisk again? It may be a TWRP version issue?

Thanks for your reply!
The version of twrp you mention is what I have used. I have not tried installing then rebooting to twrp so I try that.
When flashing magisk it usually flashes fine (I have had a couple times where it just throws an error) then when I reboot the phone will boot past the Mi logo the the Android boot logo then after 10-15 sec. it just reboots to twrp.
I was finally able to get the twrp to stick across boots by flashing twrp, signing boot image, removing twrp then reboot to Miui.
Do I need to adb push the GSI image or should it be fine to install from a USB drive?
The SMS issue isn't really a big deal for me as I use Google Fi routed through hangouts for one sim and a local sim where I'm living for mostly data and a few phone calls for the second one

Thanks so much for this post. I was completely oblivious to the fact that the Mi 8 Pro would actually be different to the Mi 8 when it comes to custom roms. When I decided on my next phone, I read the positive reviews and saw enough Mi 8 roms to be willing to make a switch to Xiaomi. Until I read your post I was close to despairing as I don't want a Xiaomi rom on my phone for various reasons (among them is the fact that I don't trust them and the way they have decided to collect user data).
I've tried to follow your guide in every step (I've also flashed the updated vendor.img), but unfortunately I have not been able to install the Pixel Experience rom on my device. I do see the boot animation but it never stops, I'm forever stuck with the Google-G and the progress bar below it. Has anyone else managed to install the Pixel Experience rom on the Mi 8 Pro? If yes, did you follow the guide here or did you do something else?
Also, in your initial post you write that we should wipe the system in TWRP but as far as I can tell GSI roms need you to wipe data, cache and dalvik cache but not the system partition (if you do it, you also don't get asked for your PIN code in TWRP any more, which - as you said - indicates that something went wrong).
Did you install a particular version of the Pixel Experience rom? Maybe that might be part of my issue?

I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.

tllim73 said:
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
Click to expand...
Click to collapse
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.

eremeya said:
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
Click to expand...
Click to collapse
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.

tllim73 said:
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
Click to expand...
Click to collapse
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?

eremeya said:
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
Click to expand...
Click to collapse
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
I try rooting it with magisk but unable to boot up. That's why I turn to Miroom Rom. They have done something which can boot it up.

tllim73 said:
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
Click to expand...
Click to collapse
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.

eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
Might be the developer version is only for the Chinese Rom. Anyway I am happy now running with GSI Rom.

eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
What version of TWRP are you using?

[GUIDE] Unlocked BL, Installed TWRP and Rooted but cannot install custom ROM...

This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.

Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me ? You've got my respect.

greenys' said:
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me You've got my respect.
Click to expand...
Click to collapse
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.

jijojamie said:
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
Click to expand...
Click to collapse
Ah I see! That's indeed a whole adventure. Thank you for sharing. It was worth reading

jijojamie said:
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Click to expand...
Click to collapse
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?

grand2SD said:
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
Click to expand...
Click to collapse
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.

jijojamie said:
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
Click to expand...
Click to collapse
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back

grand2SD said:
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
Click to expand...
Click to collapse
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.

jijojamie said:
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
Click to expand...
Click to collapse
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader

grand2SD said:
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
Click to expand...
Click to collapse
I suggest you check this with another derpfest user, please. I never got to boot to derpfest.

I downloaded Evolution X 4.7 Rom zip file and followed the instructions given in thread to flash zip file. But after flashing when I tried to reboot in system, it gave me a message on swipe screen that OS is not installed but still I swiped to boot in system. My device tried to boot a couple of time and ended up in fastboot again. Fortunately I had already made backup so I restored my backup.
As per your post I should have flashed color os 6 ozip file with twrp before flashing evox rom.

Every thing ok.i think you are not flash Vebeta after flash recovery.

Phone keeps booting into fastboot

Hi all,
I am using the weekly xiaomi.eu ROM til almost year now. The latest update from 21.4.28 to 21.5.12 somehow went wrong. I used twrp-3.4.0-2grus.img which was working perfectly for all previous updates. Now my Mi 9 SE is always booting into fastboot mode instead of MIUI. When I try to boot into one of the official TWRP versions v3.5.x the phone strangely boots into MIUI but unfortunately many things don't work (phone calls, fingerprint, WLAN, speaker). I tried to use a newer TWRP (twrp-3.5.A9-grus-geoanto555.img) to flash any of the mentioned images and the latest 21.5.20 but same result.
Is there anything I can do except of resetting to factory default? I would like to avoid loosing all my data and settings.
Thanks for any help!
Buzzy

BuzzyB said:
Hi all,
I am using the weekly xiaomi.eu ROM til almost year now. The latest update from 21.4.28 to 21.5.12 somehow went wrong. I used twrp-3.4.0-2grus.img which was working perfectly for all previous updates. Now my Mi 9 SE is always booting into fastboot mode instead of MIUI. When I try to boot into one of the official TWRP versions v3.5.x the phone strangely boots into MIUI but unfortunately many things don't work (phone calls, fingerprint, WLAN, speaker). I tried to use a newer TWRP (twrp-3.5.A9-grus-geoanto555.img) to flash any of the mentioned images and the latest 21.5.20 but same result.
Is there anything I can do except of resetting to factory default? I would like to avoid loosing all my data and settings.
Thanks for any help!
Buzzy
Click to expand...
Click to collapse
Have you checked on their forum/in the thread:
MIUI 12.6 - 21.5.20/21
Status: RELEASED 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
what is the proper TWRP to use with your device?
I don't have 9 SE but 9 T (and I'm using the latest official 3.5.2_9-0 for my device) but there was a lot of discussion about TWRP versions required for 21.5.20 (and future Xiaomi.eu weeklies) - generally TWRP 3.5+ versions must be used (for some devices n/a and then only specific 3.4 versions can substitute)

Hi zgfg,
thank you for your answer. I just read the whole thread but the update seems to work for the MI9SE in general. Initially I was using the twrp-3.4.0 which worked fine for all previous updates. I also tried the official TWRP version 3.5.x from twrp.me but they did not work for me. Every time I am fastbooting them my phone does not boot to recovery. Strangely after the failed update trying to boot the official TWRP leads to a boot into MIUI instead of fastboot. I dont't know what went wrong.
I also found this thread https://xiaomi.eu/community/threads/official-twrp-for-mi-9-se.58589/page-4. The mentioned twrp version from geoanto boots and lets me install the ROM but with the same outcome.

General Bootloop Fastboot (stock) / Phone locked for security reason (Xiaomi.eu)

Xiaomi 11 Lite 5G NE (Lisa)
Stock 12.5.8 EEA
Bootloader unlocked, Orange Fox recovery and Magisk Canary 25.2
I was running the same set-up for a couple of months, by only updating when newer Magisk was released or some module.
I never had any problem
Used to reboot like twice a week. On Sunday I wanted to reboot for a benign reason, since I installed a new weather widget
But instead of rebooting, the phone immediately went to Fastboot.
Tried couple more times, always rebooting to Fastboot
By Vol+, I rebooted to Orange Fox, wiped Dalwik and Cache and /data/system/package_cache but it didn't help
Then, from Orange Fox I flashed the boot img without Magisk, but no help, Lisa still rebooting to Fastboot.
I flashed even stock Recovery back, no help
---
Downloaded fastboot/tgz MIUI 13.0.9.0 EEA, un-gzipped, un-tared, ran flash_all.bat script (incl. wiping Data but not relocking Bootloader) through Fastboot - all partitions were flashed OKAY but Lisa still rebooted to Fastboot
From stock Recovery I performed Factory reset, but again no help
---
At that time I was pretty desperate. I was thinking about re-locking Bootloader and going to service shop, to claim for Warranty
But I decided to try Xiaomi.eu 13.0.2.0 Stable - also a Fastboot ROM
(Actually, few days before, I finally made my mind that I would go for Xiaomi.eu Weeklies - they are now Recovery ROMs
For preparation, I did all kinds of backups, planning to switch that same Sunday evening - therefore, I had one trouble less, although the phone was not operational, I didn't loose any photos, WA chats, etc and I already had a second/another/old Xiaomi phone prepared to serve for personal and work activities while I would be setting, rooting, etc Xiaomi.eu on Lisa)
Hence I ran windows_fastboot_first_install_with_data_format.bat through Fastboot - flashing was longer (few more partitions than when I flashed the stock) and again, all partitions flashed with OKAY
---
TG, the phone now rebooted to MIUI - but there was a blocking alert that For security reason, my phone was locked (see the screenshot)
I had to enable WiFi and activate/unlock by logging to my Mi Account
Still there was a catch - I forgot my Mi Account password. But I used my old/second Xiaomi (Mi 9T) phone, opened Mi Account there in Settings, and found the Change password option
Although not knowing my old password, I was allowed to set the new password by authorizing myself through an SMS code received to my pre-configured phone number associated with my Mi Account
Then I entered that new Mi Account password on Lisa, and I was finally allowed to enter and set the new MIUI 13
---
I don't know was all that related to my extensive playing with Find My Device (Google) and Find Device (Xiaomi) from the browser. Over the last week's I was testing from time to time how fast they can locate both my phones
But I can swear that I never pushed Secure or Lock my phone(s) remotely. Btw, if I did, Lisa would be locked/blocked immediately, not on the next reboot (by ambush)
Hence I don't know what was the cause
But although flashing the stock Fastboot ROM did not help, flashing Xiaomi.eu Fastboot ROM successfully unblocked/revived my phone

This is a Xiaomi Mi account security feature. If your device is linked to a Mi account, this feature is enabled.
I don't know how it works but I has happened to me with several devices.
If you unlink your Mi account from a device, then this alert is not shown.

raulci said:
This is a Xiaomi Mi account security feature. If your device is linked to a Mi account, this feature is enabled.
I don't know how it works but I has happened to me with several devices.
If you unlink your Mi account from a device, then this alert is not shown.
Click to expand...
Click to collapse
That's all ok. And I want Mi Account bcs I use it Mi Cloud backup
However, I'm surprised why that same alert (same MIUI feature), did not show upon flashing stock MIUI Fastboot ROM (instead, it was immediately dieing to Fastboot)

zgfg said:
But instead of rebooting, the phone immediately went to Fastboot.
Tried couple more times, always rebooting to Fastboot
Click to expand...
Click to collapse
I'm curious now, I had to try:
fastboot continue

zgfg said:
but Lisa still rebooted to Fastboot
---
At that time I was pretty desperate.
Click to expand...
Click to collapse
I'm pretty much stuck at this point after following the guide to flash lineage failed.
zgfg said:
But I decided to try Xiaomi.eu 13.0.2.0 Stable - also a Fastboot ROM
(Actually, few days before, I finally made my mind that I would go for Xiaomi.eu Weeklies - they are now Recovery ROMs
Hence I ran windows_fastboot_first_install_with_data_format.bat through Fastboot - flashing was longer (few more partitions than when I flashed the stock) and again, all partitions flashed with OKAY
But although flashing the stock Fastboot ROM did not help, flashing Xiaomi.eu Fastboot ROM successfully unblocked/revived my phone
Click to expand...
Click to collapse
Currently downloading the latest Eu Weekly to see if that will help. My phone is the global version, I had OTA updated it to the latest ROM, turned on developer mode, allowed USB debugging, and unlocked the bootloader before the failed flash of lineage.
Hopefully it works.

Old_Mil said:
I'm pretty much stuck at this point after following the guide to flash lineage failed.
Currently downloading the latest Eu Weekly to see if that will help. My phone is the global version, I had OTA updated it to the latest ROM, turned on developer mode, allowed USB debugging, and unlocked the bootloader before the failed flash of lineage.
Hopefully it works.
Click to expand...
Click to collapse
I intentionally used Fastboot Xiaomi.eu ROM since it seems it flashes more partitions then Recovery type, but maybe I'm wrong
Btw, did you try to connect to PC, and when your phone unsuccessfully reboots to Fastboot (instead of to the system) that you command:
fastboot continue
I didn't try myself, I later came across that suggestion by someone

zgfg said:
I intentionally used Fastboot Xiaomi.eu ROM since it seems it flashes more partitions then Recovery type, but maybe I'm wrong
Btw, did you try to connect to PC, and when your phone unsuccessfully reboots to Fastboot (instead of to the system) that you command:
fastboot continue
I didn't try myself, I later came across that suggestion by someone
Click to expand...
Click to collapse
I tried the fastboot continue command, but it failed saying there was no image on the partition.
After downloading the weekly ROM from the eu community site, I unzipped it, only to find that the .bat files they reference in the fastboot installation instructions weren't included in the .zip...?

Old_Mil said:
I tried the fastboot continue command, but it failed saying there was no image on the partition.
After downloading the weekly ROM from the eu community site, I unzipped it, only to find that the .bat files they reference in the fastboot installation instructions weren't included in the .zip...?
Click to expand...
Click to collapse
That's the point. Recovery type ROM must be installed from the custom Recovery
Therefore I used Fastboot type ROM...

zgfg said:
Therefore I used Fastboot type ROM...
Click to expand...
Click to collapse
However, there are no fastboot ROMs listed for the Mi 11 Lite 5G NE under either the Weekly tab or Stable tab...both list them as recovery ROMs now, and I have no working recovery so this is probably a dead end.

Old_Mil said:
However, there are no fastboot ROMs listed for the Mi 11 Lite 5G NE under either the Weekly tab or Stable tab...both list them as recovery ROMs now, and I have no working recovery so this is probably a dead end.
Click to expand...
Click to collapse
There is Stable, but not the latest

zgfg said:
There is Stable, but not the latest
Click to expand...
Click to collapse
I'm guessing that since it's not the latest, if I try and flash it that the antirollback protection will brick the handset...?

Old_Mil said:
I'm guessing that since it's not the latest, if I try and flash it that the antirollback protection will brick the handset...?
Click to expand...
Click to collapse
There is no anti-rollnack protection in Xiaomi.eu scripts
In the Xiaomi.eu Forum, Stable MIUI 13 thread, post #1 there is a link to AFH:
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED 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
Scroll there to find the zip for 5G Lite NE that has Fastboot in the name. There are two (third is the newest, no fastboot in the name, it's recovery type ROM) and take the newer fastboot
And please read instructions in that thread, same post #1, how to install. EVERYTHING is explained there (read about Fastboot installation part), do not ask me how to install or so, I will no more help you with additional info or so, because everything explained there (I will really not waste my time for writing the same things
All of us were able to install by properly following that same guide - hence for those who want to concentrate and read, the guide is enough
Good luck

zgfg said:
There is no anti-rollnack protection in Xiaomi.eu scripts
In the Xiaomi.eu Forum, Stable MIUI 13 thread, post #1 there is a link to AFH:
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED 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
Scroll there to find the zip for 5G Lite NE that has Fastboot in the name. There are two (third is the newest, no fastboot in the name, it's recovery type ROM) and take the newer fastboot
Click to expand...
Click to collapse
Thanks! This worked perfectly, flashed the EU Rom and the phone booted - initially into Mi Recovery and then into the full Mi13/A12 OS.
The problem I was having is I was trying this on my 2-1 with a 7 inch screen, and the filenames on Sourceforge were truncated so I couldn't see that any had fastboot in the name. I hovered over the files with 5GNE in the filename and then found the one you describe.
Thanks again, it's working.
Now I just have to supress the urge to try flasing Pixel Experience and breaking it again.

Old_Mil said:
Thanks! This worked perfectly, flashed the EU Rom and the phone booted - initially into Mi Recovery and then into the full Mi13/A12 OS.
The problem I was having is I was trying this on my 2-1 with a 7 inch screen, and the filenames on Sourceforge were truncated so I couldn't see that any had fastboot in the name. I hovered over the files with 5GNE in the filename and then found the one you describe.
Thanks again, it's working.
Now I just have to supress the urge to try flasing Pixel Experience and breaking it again.
Click to expand...
Click to collapse
Now, you can update to the latest Xiaomi eu Stable (that third, latest ROM for Lisa without the fastboot in the name), released Sep 10
You will need Orange Fox (OF, custom recovery). Open the following thread, in the post #1 there is a link to AFH, find Lisa and download OrangeFox-R11.1_2-Unofficial-lisa:
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Download and unzip, take the img file. DO NOT FLASH, just boot:
fastboot boot <OF img file>
and then from Orange Fox flash that Xiaomi.eu Stable zip (without Formatting or Wiping since you are now updating Xiaomi.eu)
Stable (being now Recovery type) will permanently install OF and for the next Xiaomi.eu update you will already have Orange Fox on your Lisa
---
I didn't try that latest Stable since I had already switched to Xiaomi.eu Weeklies (Betas) - they are also Recovery type ROMs, hence the procedure is the same

This worked as well, flashed the latest Stable ROM, flashed Magisk 25, and rooted the phone. I can delete some of the stock apps with a PC based debloater but still looking for an android app that will ..

Old_Mil said:
This worked as well, flashed the latest Stable ROM, flashed Magisk 25, and rooted the phone. I can delete some of the stock apps with a PC based debloater but still looking for an android app that will ..
Click to expand...
Click to collapse
You can not hard debloat because your SAR is read-only. Not even with custom recovery
However, you can systemlessly debloat by:
GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com