How to flash PE ROM in MI MIX2S device? - Treble-Enabled Device Questions and Answers

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?

Related

Lineage OS 15.0 Dev Thread [DISCUSSION]

Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
When does the development starts?
I don't know the procedure of ROM development. Are devs waiting for the oreo update from HTC?
Some devs already work on Oreo aosp, but it's not that easy to get it working on the 10 so that everything works. Maybe even stock will be earlier here than custom Roms like aosp and los
Sent from my HTC 10 using XDA Labs
Don't really know about LOS but AOSP based is already here...
https://forum.xda-developers.com/htc-10/development/rom-official-pure-fusion-os-oreo-t3694203/page2
P.S why is there a Dev in the Title?
Is there any news?
kingfared said:
Is there any news?
Click to expand...
Click to collapse
Lineage has a whole site with news and downloads and everything: https://www.lineageos.org/
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Honestly Annoying said:
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
Click to expand...
Click to collapse
You can't start a "Dev thread" if you aren't a dev on the project; you can only start a "Nag thread".
Sorry for unqualified question. I know the new site but I don't know where to find dev threads. If you can help me I'll be glad.
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Ndaoud360 said:
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Click to expand...
Click to collapse
That device still has an active developer working on it. crpalmer, the user who brought 14.X to HTC 10 seems to have moved on to newer devices.
hope it will have LOS15.1
Even though Raymon left development does this mean there are no los 15 for us?
As already stated by fagyi, once he solves all bugs on aosip 8.1 he will build los.
15.1 Running flawless albeit hot sometimes!
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
heyChristo said:
Ladies and Gentleman,
I have been extremely pissed off lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
If you are so frustrated about stuff you get for free than just stay stock and stop being frustrated.......mwuhahaha funny how the world works these days......oh and by the way, you don't downgrade your kernel, you downgrade your firmware.
Cheers, have an absolutely fabulous Sunday
heyChristo said:
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Musthafa-Noor said:
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Click to expand...
Click to collapse
Nougat.
heyChristo said:
Nougat.
Click to expand...
Click to collapse
Maybe was wrong. Maybe was Oreo firmware. Switched to this and had to go the other one. Sometimes I just go into a flashing rage and can't rememember what happened after.
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Click to expand...
Click to collapse
I'm using that ROM build of 15.1 on my HTC 10 (Android 8.1), and it works pretty good actually. besides a few minor issues.
Unlocked Bootloader from HTCDev, Running latest TWRP Recovery, S-On (for me at least was not needed to turn this off), Latest Magisk (which seems to pass the Safetynet check) / Busybox.
I changed the Kernel afterwards to "kernel_htc_pme_aosp_tabp0le_eas_4.02-O" (from tabp0le) because it has the "performance" cpu governor that i can enable using Kernel Adiutor.
The bugs i encountered so far :
- Camera apps open slowly, except for "Open Camera" , not a big issue.
- HTC Sense Launcher doesn't seem to work, just get the famous (app has stopped) message, but maybe it's a conflict with my GAPPS installation
- Only 1 speaker works, HTC10 has Boomsound with 2 speakers on stock rom, 1 is a treble speaker, the other one is kinda like a small subwoofer for the low frequencies.
Is there any soundmod that would enable both speakers again?
There is not any mod to do that. But the dev of this ROM is working on getting the bottom speaker working.
I just saw that a new build-version is released for HTC10.
lineage-15.1-20180624-UNOFFICIAL-pme.zip

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?

[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.

How to install LineageOS on the Mi 10T Lite

Hey guys, if you're a noob or you haven't flashed a custom ROM to an android device since the likes of the Galaxy S2 like me, this guide is made for you!
Disclaimer: I am by no means taking credit for any links posted, credits to the creators of anything mentioned! And a special thank you to the creators of the TWRP and the ROM, hopefully development will grow for such an awesome device! I am not responsible if you brick your device (by not following my tutorial :/)
The only complaints I have about this ROM is the camera quality but install the GCAM port for the Mi10T Lite, it may help!
You will need:
A Mi10T Lite (duh) or any other supported device with MIUI Installed (Android 10)
A SD card
A laptop with fastboot installed ( [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 | XDA Developers Forums (xda-developers.com) )
A Mi account
TWRP (https://www.mediafire.com/file/qaea...0I_3.5.A10_05-01-2021_BL-L-fixsdcard.img/file)
The ROM (https://forum.xda-developers.com/t/rom-unofficial-10-0-gauguin-lineageos-17-1.4224633/)
GApps (I used this one: Download NikGapps from SourceForge.net)
B*lls
First (Ignore this if you already unlocked your bootloader):
Download MiFlash_Unlock (http://miuirom.xiaomi.com/rom/u1106245679/4.5.813.51/miflash_unlock-en-4.5.813.51.zip)
Make sure you have a Mi account and a SIM
Go to settings, enable developer options
Once you have done this, go to developer options (additional settings, scroll down)
Enable OEM Unlocking
Enable USB Debugging (not sure if this is necessary but I like to have it enabled anyway)
Click on Mi Unlock status and add your account, remember your details! (You may need to sign out and sign back in again)
It should say account linked to device successfully or something along those lines
Grab a cable (the included cable worked for me but other cables didn't)
OPTIONAL: YOU MAY WANT TO BACK UP ALL OF YOUR DATA
Open MiFlash_Unlock which you previously downloaded and connect your phone in fastboot mode (if it doesn't show up follow this tutorial: Fixed: Fastboot not detecting your Android device (qasimtricks.com) )
Click on unlock device! It should automatically reboot when it's done
Complete the set-up process, input your Mi account details and you should be good to go!
Enable developer options again and enable USB debugging
Installing TWRP (Ignore this if you already have TWRP installed!):
Turn off your device and boot into fastboot, connect and verify that it is connected by opening command prompt then typing "fastboot devices", it should show up
Point command prompt to the folder where your TWRP is downloaded (if it is located in downloads, type cd c:/users/(your username)/downloads
Then type fastboot flash recovery "twrp".img (replace "twrp" with the name of the recovery installed)
It should say successful, then type fastboot reboot and hold volume up + power
You've booted into TWRP! Hooray!
If it asks for the password to decrypt put it in, if it doesn't then no worries
You will notice that your internal storage is encrypted, not to worry!
Installing the ROM:
Connect your phone to your laptop (it can be in TWRP) and move the ROM to your SD card
Boot into TWRP if you haven't already, click wipe, advanced wipe and wipe Dalvik Cache/ART, Data and Cache
Once this has completed, go to install, then change the storage to SD Card
Locate the ROM file and swipe to flash!
Once the flash has completed, DO NOT REBOOT
Go to wipe and click format data, then type yes
Reboot to system! Done!
Installing GApps (Optional):
Move the GApps file provided to your phone
Boot to TWRP
It will prompt you to enter your passcode, this will decrypt the internal storage!
Click on install and locate GApps, swipe and flash!
Reboot
Congratulations! You have installed the first custom ROM made specifically for the device You can install Magisk if you want, I'm in the UK and my metro bank app didn't work but by using Magisk hide and changing the name of the Magisk manager everything worked (hide every Google app)
Enjoy! I hope you found this useful
thanks, after installing it can i go back to stock with locked bootloader?
jeuxtype said:
thanks, after installing it can i go back to stock with locked bootloader?
Click to expand...
Click to collapse
yes you can using xiaomi flash tool
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Chari69 said:
yes you can using xiaomi flash tool
Click to expand...
Click to collapse
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
jeuxtype said:
so it's safe to flash lineage, i want to use it but i need to get back to stock to watch netflix and for google pay?
Click to expand...
Click to collapse
Yes its safe, download the stock fastboot ROM online and use miFlash as mentioned, before you start flashing make sure the setting at the bottom right of the app is set to wipe + lock, I've already done it once and it worked fine
benfleet5 said:
Might want to confirm when to install gapps as if it's done after a boot it's not going to work!
Click to expand...
Click to collapse
Hey, that's awfully weird. When I tried flashing alongside the ROM I kept getting an error, but after I booted and done initial set up and tried installing it worked fine
Good guide a++++
deanlee121 said:
Good guide a++++
Click to expand...
Click to collapse
Thanks Dean!
Google pay works on this?
Xts7 said:
Google pay works on this?
Click to expand...
Click to collapse
Yeah just changed the magisk package name, enabled magisk hide and used gpay sqlite fix and it was all working. Metro Bank worked too
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
jdtanner said:
The only thing I'd say is that Open GApps Micro is the package you want to install; anything larger won't fit in the system partition - you get an Error 70! JT
Click to expand...
Click to collapse
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
fizzy900 said:
Hey, I've just been made aware that that works too, but NikkGapps also works! Also, ArrowOS comes pre-built with GApps and it's better imo, only thing is bluetooth audio doesn't work and the speaker crackles occasionally.
Click to expand...
Click to collapse
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
jdtanner said:
Waiting until these bugs are sorted before trying that ROM. Bluetooth and general audio are fairly important to me
Click to expand...
Click to collapse
Same somewhat lol, its annoying but thank God my headphones have a 3.5mm jack too!
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Jonny5isalivetm said:
Thanks for the guide, I recently got a redmi note 9 pro 5g from chinaland shipped to the uk then followed this guide pretty much, but instead of going twrp and lineage I went Orangefox and Arrow OS
I wasn't sure how all would go so was grateful of the guide as my first flashing on the new beasty..
I used this guide + info from the arrow thread before I jumped in..
just for info's it worked flawlessly
Steps I did
1. Unlocked bootloader ofcourse
2. installed Orangefox via fastboot
3. flashed latest version of china android 10 from sdcard (no reboot)
4. flashed arrow OS android 11 from sdcard
5. wiped data
To my amazement it booted first go and real fast like in under 5min!
can somebody explain why we need to wipe data after flashing ? surely wiping data means wiping ? but I guess it is not somehow wiping the good flash data..?
Where does all the data go when I flashed the first chinarom and why is it required to flash chinarom first ?
I have one bug bar the odd crackle, has anyone else noticed keyboard issues ? When i type sometimes it shows up backwards
ie google will appear as elgoog ?
I tried swiftkey keyboard + changing languages still the issue persists..
Thanks again @ Fizzy900
Click to expand...
Click to collapse
Hey bro, nice glad you enjoyed! So you have to format data after flashing a custom ROM from what I know in order to remove encryption, if you don't it'll show your internal files in a strange way and if you further tinker with it and do something it might stop you from installing apps full stop (happened to me cause I was being a tw*t lol). You need to flash the latest stock firmware (if the ROM requires you to) so you get the latest vendors which work with the custom ROM, although I believe there is a method to just flash vendor images themselves (fastboot flash vendor nameofvendorfile.img).
Yeah so arrowOS has notification crackles for some reason, most of the bugs are audio related (BT audio doesn't work either).
My typing was backwards too sometimes, it's because you're touching the fingerprint slightly which goes to the first element on a page or something (when you're typing it goes to the start of the box where you enter text). To understand what I mean go onto your launcher and tap the fingerprint scanner, it should highlight something.
I just flashed dotOS from arrow, works a charm! No audio related bugs afaik and BT audio works (lifesaver, phew).
Any other questions feel free to drop me a message on Telegram, @stillw0rking.
Take care! Also how in the world did you import the device from China hahahaha
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Jonny5isalivetm said:
epic fast reply!
<3
ahha the fingerprint!! I was wondering why I got random white box appearing on my home screen (and at random times) can it be disabled ?
So we got another rom already lol how excellent, I would like a rom that is stripped to the bone so we can install what we like, aka the least amount of crap running in the backround the merrier I am
Yea I just ordered from one of the china phone shops, got a note 9 pro 5g for £ 211 including postage, when I saw the price I just had to buy even tho my trusty oneplus 3t is still fine but but had the upgrade bug hehe, was from giztop, risked the custom charge and succeeded haha
Finally thanks for explaining the Encryption bit, yes I did read that but it seemed to go in one ear...
Guessing you are on the mainland somewhere, Greetings from across the pond
Click to expand...
Click to collapse
Haha yes I'm from near London! You must be the first English person I've actually bumped across on XDA ever lol. Aah yes, as far as I know it can't be disabled, it'll be stuck w that until the dev fixes it... ROMs have started to release quite quickly for the phone ever since the mi10i got dropped thank God, hopefully this is a good sign!
DotOS seems to be pretty light, heavy on the customizing side but when I started from fresh I had the basic google apps but gmail wasn't even installed lol. Dot is giving me the same sort of sot as Arrow, so really its up to you, but if the BT audio bug is a major thing for you (thank God one of my headphones can be used with a 3.5mm jack too lol) then I'd recommend Dot, but otherwise they're both extremely similar in terms of performance
And I was gna try and order the mi9T Pro like that but didn't bother, read some bad stories lol.
And no worries But yeah I'm pretty sure that is all it is, when you modify /system or something, the internal storage encrypts so you can't access it on stock ROM with TWRP but with custom you can decrypt easily
Take care mate!
Does lineage for mi 10t lite support 120 hz on screen ? Is it adaptive or locked?

Question Xiaomi 11 Lite 5G NE - OFFICIAL MIUI 14 GLOBAL V14.0.2.0MIXM - ANYONE UPDATED YET ? Thread starter k500zm Start date 1 minute ago Tags

Has anyone been offered the Global version by their phone and updated ?
If Yes - what is your experience with MIUI 14 and does Dark mode work for individual apps listed separately in dark mode options?
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Today monring i make an update, it is super. System is faster, but Leica cam app is not possible instal, have anybody newer version of leiaca cam app fo A13? THX
thecumbackkid said:
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Click to expand...
Click to collapse
@thecumbackkid - Please tell me in settings - display - more dark mode options - does it list all the individual apps to choose dark mode for each app ? (it may take a second or 2 to list them)​
This is what it shows for me.
Thanks for the info thecumbackkid
Looks like its time to upgrade I was stuck on Miui 12.5 as when I updated to 13 all individual dark mode apps options disappered.
Someone stole my phone on holiday so I bought a new one and stuck on 12.5 as Dark mode for individual apps is essential for my over sensitive eyes!
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
snyfear said:
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
Click to expand...
Click to collapse
@snyfear
Thanks for the info - if you notice anything else let us know
Awful battery drain here. Charged to 100% barely did some basic browsing and half is already gone in a short amount of time. Noticed whenever I have it charged to 100% at night and by the middle of the next day where I barely use it for nothing but just to check for notifications on stuff it's already down to 80%...
AFAIK, this appears to be some pilot program build? I never asked to participate in it so how did I get this update?
Does any one know how to Facemoji keyboard in MIUI 14 for Lisa ?
I am not rooted. its plain stock MIUI.
Tried ADB shell uninstall, it gave me failure.
Also tried Xioami debloater tool. That also didnt work.
I still haven't received the update for some reason and i tried to update it manually but it didn't work what should I do
Updated to 14.0.4 EUXM and can't get root to work anymore.
Patched the boot image via Magisk 25.2 and then tested via fastboot, as always.
I run directly into a bootloop, which after a while sometimes returns to the bootloader or automatically deletes the temporary boot and boots with the normal image.
It's also strange that during the bootloop the device vibrates once every 3-5 seconds briefly. I've never had that before either.
Update:
I found a solution without wiping my device.
I remembered that I had a problem during the last update with shamiko and I didn't uninstalled magisk or removed any modules before the update. So in order to remove the modules without access to /data/adb and wihtout root rights you need to do the following, maybe it's interesting for you folks.
1. Open shell with command: "adb wait-for-device shell magisk --remove-modules"
2. Open second shell and boot with patched boot.img: "fastboot boot boot_patched.img"
The short time at boot, where root is present, was enough to remove the modules via the CLI during the boot loop.
Lessons learned:
Before the next major update definitely remove all Magisk modules before, if not root entirely.
Saves the work afterwards.
Btw:
Update is running smoothly so far. No battery drain noticed.
can anyone link me to a tutorial on how to rollback from custom rom (currently AOSPA) to stock MIUI ROM? want to move to MIUI 14 eventually. greatly appreciate it!
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
telefoongids said:
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
Click to expand...
Click to collapse
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
theanik said:
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
Click to expand...
Click to collapse
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash the rom with fastboot first, to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 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
Just search for mi11le in the downloads.
telefoongids said:
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash it first with fastboot to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 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
Just search for mi11le in the downloads.
Click to expand...
Click to collapse
thank you!
any one from Philippines received the update?

Categories

Resources