Develop Bugs

How to flash PE ROM in MI MIX2S device?

Dear every one, I really like this ROM, but how to flash this ROM?
I try to flash to use fastboot and TWRP with IMG flashIng, but after flashing them, the mobile phone will jump to Bootloader page, but when I use the same method in other ROM(like PHH and RR6.1.0)it works. My last ROM version is MIUI10-8.7.12 Globle.
details here
1.formate data
2.4 wipe
3.install and choose img file with system type.
4.wipe again
5.reboot
THanks.

If supported you can flash the image in bootloader mode.
Type in this command.
fastboot flash system nameofimage.img and reboot.

PE just wont boot for some devices. There is a whole different thread about fixing this, it may be for Huawei, but it could work for more devices. Apparently flashing a patched boot from Magisk works.

flash magisk 16.6 it will boot. but then you will have to also format data(not wipe) in twrp to disable encryption.

It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I used version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!

kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1)
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
9. Rebooted system again and it works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
didnt worked for me rebooted into recovery i used 3.2.1-0 can you link me yours?

From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.

kleinholzinferno said:
From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.
Click to expand...
Click to collapse
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages

PITTAR said:
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages
Click to expand...
Click to collapse
Very good, great it works for you now.
Enjoy the new phone! I have it running for a few days now and so far I love it! I'm never going back to miui again! Never!
Some things are not working at the moment like Bluetooth audio to car stereo. Although it shows the song playing with the title and the correct time on the car head unit I hear no sound. Hands free calls work without any problems.
In band ringing doesn't work so I don't hear my ringtone over the car stereo. I can activate this in developer options but it doesn't stay on and doesn't work. Nevermind, this isn't important.
Haven't found many other things that I need at the moment.
Great rom, hope it gets maintained in the future and there will be a device specific rom for the MiMix2S in the near future.
Hopefully Android P in fall/winter?

kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..Oh, I try to flash Omin ROM, but it can't get into the system..and Magisk16.6 can't be flashed in with error..

jayxiao171735 said:
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..
Click to expand...
Click to collapse
Magisk was mandatory for me because otherwise it ended up booting only to recovery.
I haven't tried what happens when you uninstall magisk after successfully setting up the device.
If you need to hide root use magisk hide, maybe that helps?

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?

WARNING Miui 11 OTA update breaks Mi Max 3 root

If I am in a class of 1 in terms of rank stupidity please feel free to delete this post. :silly:I got sick of the updater nags. With a couple of previous Xiaomi phones I got away with finally saying yes to the OTA update which would inevitably fail after which the nags would stop for a good long while.
Not this time. I now have Miui 11 (which I did not want and which has a completely broken feedback function, btw) but lost root, magisk, and exposed.
I should also note that another Max 3 user posted here that permitting the OTA update bricked their device, so I guess things could be worse.
About to see if I can re root using the same method as before the update.
Sorry if I wasted anyone's time on the blindingly obvious.

Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.

brasscupcakes said:
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
Click to expand...
Click to collapse
Don't worry about anti-rollback unless you go back to rom that has no anti rollback. I go from miui 10 global to miuieu 11 P beta to miuieu 11 Q beta then back to miuieu 10 P stable. Now I settled on miuieu 11 P stable, yes miui 11 Q is very buggy. A few of my app don't work properly.

[Fix] Root on latest MIUI 11 build !
Just update Magisk Manager to 20.2 !

What's with a screen when charging, it keeps turnin on? Happens after MIUI 10 install...

Since the first version of Android Q, I could never do it Root, I can't make Magisk work, whatever I do.
I install it without problems, but when restarting it is not installed, I never have root.
Try 20.1 and 20.2, it still doesn't work.
I have a Mi Max 3 6/128

I installed the latest Miui 11 OTA update last night - taking a full Orangefox backup beforehand. After reboot, the phone was full of ads suddenly and it took me a while to figure out that root had been removed. I soon discovered that Orangefox had also been removed and replaced with a clunky-looking version of TWRP. I reflashed Orangefox and Magisk - coming back to recovery inbetween-times and it booted fine but the ads were still there so I tried to install Xposed via Magisk and that seems to have pretty much soft-bricked it. I can get into Orangefox where it said 'No Rom' which didn't seem like a good sign. I tried to re-flash the full backup I'd made with Organgefox yesterday (and this not really understanding Orange fox that well) but that hung at 'System image' - so I tried to flash without that and that succeeded but it's still totally bootlooping.
I'd very much appreciate some advice:
1. The Orangefox backup I made was with all the boxes ticked - i.e back up everything. I have the dim idea that trying to simply restore all of this won't work (it certainly doesn't seem to work). What parts of the full backup should I try to restore?
2. If I install the latest Global Miui 10 ROM - which is still Android 9 - using the Miui repair tool, will this brick the phone because of ARB? Or is it safe to do this?
3. Will dirty-flashing the latest Miui 11 rom via OrangeFox likely make something I can at least boot up and get some data (it turns out that 'SMS backup and restore' hasn't been working for weeks so I don't have a pile of work texts that I really wouldn't like to lose)?
4. Any other suggestion most gratefully received. Thanks in advance.
(Thinking about it, this thread is for the OTA breaking the MI Max 3, not my particular woes with restoring an Orange Fox backup - so, with apologies, I'll post in the Mi Max3/Orange Fox thread.)
PS: Flashing the OTA again fixed it, short term: no root is better than no phone.

[ROM][10] Lineageos 17.1 [Official] Pixel 3a "Sargo"

Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org

Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.

The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?

pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.

MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10

pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!

I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.

Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).

I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.

In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.

guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?

pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.

MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"

pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)

MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.

For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.

So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##

harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.

nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.

harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.

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