Related
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?
Introduction
This is a LineageOS Recovery compiled from the source tree of LineageOS 17.1 for Redmi K30 5G. This is part of my ongoing work to port LineageOS 17.1 to this device. Work on the actual LineageOS 17.1 ROM is still under way (but it should be available very soon), while the recovery has been usable for quite some time now. Since it is not possible for TWRP to support any device launched with Android 10 for now, I figured that this might be useful even before I release the LineageOS custom ROM (e.g. people may want to flash Magisk on official ROMs).
I am aware that there is a TWRP port for this device, but since the source code is not accessible (as for as I can tell, maybe I just did not look hard enough for the source code), I can only advice against using it. The official TWRP open-sourced under GPLv3 does not even support devices launched with Android 10 yet, so there's clearly something going on here. I do not fix compatibility issues between my ROM and that TWRP port.
Instructions (Installing Recovery)
This recovery ONLY works on MIUI firmware version v11.0.11.0 (stable firmware before May 2020). Xiaomi hasn't released kernel source update for later firmware versions and you may experience blank screen and similar issues if you are on a newer firmware.
1. Download vbmeta.img, recovery-XXXX.zip (extract to get recovery.img)
2. Reboot to bootloader (`adb reboot bootloader`)
3. Run `fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img`
4. Run `fastboot flash recovery recovery.img`
5. Run `fastboot reboot recovery` to enter LineageOS Recovery
Instructions (Installing Magisk)
You have to use the official Magisk, version 20.4 or later. Installing an older Magisk will make the system unbootable.
1. Download Magisk >= 20.4, put onto computer
2. Reboot to LineageOS recovery, select `Mount /system` (you may see some errors, but they can be safely ignored)
3. Select `Apply update from ADB`
4. Run `adb sideload Magisk-xxx.zip`
5. You will see a signature verification error, select `Yes` to bypass the check
6. Reboot to system to enjoy your Magisk installation.
Caveats
1. Since it's not TWRP, you cannot decrypt your /data in recovery for now, which means no data backup or recovery, and you cannot install on-device flashable zips through this recovery.
2. Since it's not TWRP, it cannot prevent your OS from overwriting recovery automatically. If you use official ROM, you may need to manually re-flash the recovery every time. I'm not sure whether this can be bypassed with some Magisk module.
3. Don't expect to be able to flash anything into /system (e.g. OpenGAPPS) on stock ROMs; you might be able to do so once my LineageOS ROM is released
4. When trying to install OpenGAPPS on LineageOS 17.1 (not released yet as of 2020-03-06), it will get stuck at the end of the flashing process. This does not affect the functionality of the installed system and gapps, and a force-reboot into system will work just fine. Use my patched OpenGAPPS in the LineageOS thread.
5. You need to always click "Mount /system" before flashing any mods into the system (i.e. Magisk, OpenGapps, etc., ROMs themselves are not affected), otherwise they will fail to install. (Clicking the option does not actually mount /system; it just sets up necessary mappings from the super partition to each of the dynamic partitions so that the installation scripts will work)
Downloads
LineageOS Recovery (17.1, 2020-03-06): https://mega.nz/#!PZRCBaiA!L-c3Tn6E295xcAIZCSt9ribpGsutX3QJRt04uyQGg_k
Changelog: Improved compatibility with OpenGAPPS (won't work with MIUI; this change is solely for the soon-to-be-released LineageOS 17.1 port)
LineageOS Recovery (17.1, 2020-03-01): https://mega.nz/#!XI4BGDQS!CPH2kIUdqaTtU_Zdzx8bUiL7FcU-G51RwmdH0MGbSRk
vbmeta.img: https://mega.nz/#!vQohmJgJ!IWAjbxGIxxxQ4OScQH8YT8oKJMx8Q-2pV83zqxbItD4
Source Code
Device Tree (including LineageOS 17.1 port): https://github.com/PeterCxy/android_device_xiaomi_picasso
Kernel: https://github.com/PeterCxy/android_kernel_xiaomi_sm7250
Hello,
Thanks for the custom recovery and Magisk. Would that recovery work on K30 (not 5G) or Poco X2?
Good work and keep it up!
DyXen said:
Hello,
Thanks for the custom recovery and Magisk. Would that recovery work on K30 (not 5G) or Poco X2?
Good work and keep it up!
Click to expand...
Click to collapse
Probably won't. Those two phones are totally different from the 5G version, despite their similar name / non-SoC specs. They are closer to K20 than K30 5G.
What is the progress of this LineageOS?
How long can you experience it?
syutung said:
What is the progress of this LineageOS?
How long can you experience it?
Click to expand...
Click to collapse
I'm dogfooding right now. If I don't brick my phone by dogfooding my LOS port then it will be available for download in one or two days.
PeterCxy said:
I'm dogfooding right now. If I don't brick my phone by dogfooding my LOS port then it will be available for download in one or two days.
Click to expand...
Click to collapse
I got blanky blank screen on booting this recovery :/
It only shows the first two lines
Help
Hello!
I am trying to follow the instructions to install the Lineage Recovery on my K30 5G (Speed edition), which is also codenamed "picasso" and shares the same MIUI ROM with normal K30 5G.
No luck with a mostly blank screen after booting into recovery:
imgur.com/a/cmpDedZ (sorry for the bad quality because I shot it with a webcam). As in the picture, only one and a half lines of yellow text are visible near the top, which reads "Lineage Recovery" and "Redmi/picasso/picasso". The other part is just in grey without anything except a dotted vertical blue line (almostly invisible in the picture; not the thick white lines which is just reflection) in the middle of the screen. Besides, it seems to respond to the power/volume key.
I notice that you mentioned in the other thread that your ROM requires a specific MIUI firmware version. Then does the Recovery also require so? (I didn't have a chance to try that because my phone got fully bricked immediately after downgrading to V11.0.11.0 (now fixed).) Or do you kindly have any advice?
Thanks.
Pycoo said:
Hello!
I am trying to follow the instructions to install the Lineage Recovery on my K30 5G (Speed edition), which is also codenamed "picasso" and shares the same MIUI ROM with normal K30 5G.
No luck with a mostly blank screen after booting into recovery:
imgur.com/a/cmpDedZ (sorry for the bad quality because I shot it with a webcam). As in the picture, only one and a half lines of yellow text are visible near the top, which reads "Lineage Recovery" and "Redmi/picasso/picasso". The other part is just in grey without anything except a dotted vertical blue line (almostly invisible in the picture; not the thick white lines which is just reflection) in the middle of the screen. Besides, it seems to respond to the power/volume key.
I notice that you mentioned in the other thread that your ROM requires a specific MIUI firmware version. Then does the Recovery also require so? (I didn't have a chance to try that because my phone got fully bricked immediately after downgrading to V11.0.11.0 (now fixed).) Or do you kindly have any advice?
Thanks.
Click to expand...
Click to collapse
The recovery may not work on newer MIUI firmware versions because Xiaomi didn't release corresponding kernel source updates for those newer versions. This is unfortunate, but I can do nothing about it. Ask Xiaomi to release their source code.
Hi Peter,
Thanks very much for porting Lineage OS onto the Redmi K30 5G Pro. Mine arrived today, and I'm planning on installing your port ASAP.
However, I have run into a problem: The device shipped with MIUI version 11.0.12.0. Your post in the Lineage OS Recovery thread says that I can only install it on MIUI 11.0.11.0.
Do you know how I can downgrade my MIUI software so that I can install Lineage OS Recovery?
Thanks!
After doing this now I can't flash Twrp anymore (got bootloop). pls help
Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
If you are using MIUI V12.0.5.0 or higher, TWRP V11.0.4.0 will not work.
If you want to keep TWRP V11.0.4.0 working on MIUI V12.0.5.0 or higher, you need to flash the stock rom lk partition from V12.0.4.0 (or lower).
It will works perfectly with lower lk partition version.
LK partition images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
RECOVERY partition images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
(Tested on V12.0.5.0 and V12.0.6.0).
Good luck.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
I got my redmi note 9 10 days ago. I was so stupid to run an update and I really do not know which version it was on but it updated to 12.0.9. On this version I have been trying to install twrp to no avail. fastboot boot recovery.img does nothing either I just the xiami revevery.
So after some struggeling I flashed back to 12.0.4 and after that tried to install twrp again (the TWRP V11.0.4.0 version) but still the same effect. I managed to install magisk and now I am root but the mu ui does not work with edXposed/gravitybox and I really need to be able to split the volume of alert messages and incoming calls and like to config my navbar etc. I tried custoMUIIzer and it has an option to show the notificaiton value but they are still linked. I do not get calls much but if I get them they could be really important. I get 100's of nitofications a day . sometimes 500 (like monitoring altets) and they need to be off or very quit most of the day. I managed to fix this on my stock android 9 phone using edxposed/gravetiybox but xiami ignores every thing. Also saftynet and magisk fail too.
So I might aswell try lineage os or the pix experience. Maybe Xposed works there. If I need it al all.
But I really like twrp to work so I can flash those zip files using twrp.
Can it be that I have a differend hardware version or something?
I also red about bypassing EDL via python? But that was needed to flash on older rom and I am really running 12.0.4 now.
Should I still try that EDL by pass trick?
What else could I be missing?
I seems very typical that a fastboot boot recover.img does not even work for 1 time. It should load that image from my pc and boot from it right?
Why google decided that we can not have seperate volumes for incomming phonecalls and general notifications is beyond me. It was posible in android 4.4 and lower. How much would it hurt them to make it a configuration option in the settings.
I am thinking more and more to have a very small and simple phone for phone calls and my banking app. If only we culd run that in an emulator.
Sorry again. After updating edXposed to EdXposed-v0.5.2.2_4683 custMIUizer started to work. (after reboot)
I thought I had the latest since I just installed it via magisk. So now I actually can set different volumes Happy again. Now how to get rid of the rounded corners and how to get a black background behind my nav buttons...
But it would still be nice to get twrp working.
Hans de Groot said:
Sorry again. After updating edXposed to EdXposed-v0.5.2.2_4683 custMIUizer started to work. (after reboot)
I thought I had the latest since I just installed it via magisk. So now I actually can set different volumes Happy again. Now how to get rid of the rounded corners and how to get a black background behind my nav buttons...
But it would still be nice to get twrp working.
Click to expand...
Click to collapse
Try this:
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G Warnings: - This is not a development thread. This is a help thread. - I didn't build any of them. Use at your own risk. - I don't have the source code for any of them. Use at your own...
forum.xda-developers.com
Hi!
I wanted to simply update to v24.1 in Magisk Manager on my Xiaomi Mi 9 SE. It rebooted successfully but the wi-fi wouldn't turn on (automatically turned off right when I tried turning it on) and the fingerprint sensor wouldn't recognize my fingerprint.
I looked it up and people recommended disabling and/or uninstalling all modules but it didn't work (I only had Magisk Hide and some other I don't remember). Another was to uninstall Magisk so I tried it and accidentally clicked "restore images". After that, it would only load into TWRP.
It's been like 2 years since I've done any of this stuff so I don't remember much. I didn't even install the official Xiaomi update for well over a year so I'm not even sure which Android version it had, maybe 9?
I have tried flashing Magisk uninstall.zip and also a boot.img (unfortunately I have no clue which the exact ROM is so I just randomly tried this 2019-10-23 one). No luck.
Should I keep trying boot images? I don't want to flash the wrong file and make it worse or lose my data, especially not the app data. I did a TWRP backup now but I don't have a previous one from before I could boot into Android.
Can someone walk a noob through what to do so I don't mess it up more?
Just flash an entire Fastboot ROM without wiping user data (mi flash allows you to do that) and make sure the ROM's version is the same as your device or higher
You can find fastboot images at xiaomifirmwareupdater.com
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