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?
Related
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
EDIT: I see that Puddi Puddin beat me to it.
Puddi_Puddin said:
Unbrick guide method 2 should fix it, otherwise ask Oneplus support.
Click to expand...
Click to collapse
tnsmani said:
If this doesn't sort out the issue, use Method 2 from the Mega Unbrick Guide in XDA and follow every instruction scrupulously, especially relating to drivers.
If even this fails, it is a hardware issue.
Click to expand...
Click to collapse
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
tnsmani said:
Which TWRP are you using? Try using the latest from eng.stk's (Blue Spark).
If you want MM, the more stable and improved version is 3.2.8. What you downloaded is 3.2.4. So, download 3.2.8 and boot into recovery, wipe system, dalvik cache, cache and data including internal storage (you will lose all your files including photos, videos etc). Boot the phone into the bootloader mode and push the ROM to the phone and flash it from recovery or flash the ROM from PC using adb commands. Flash TWRP again and boot into recovery and if ok, boot into system. If everything is ok, you can flash SuperSU/Magisk, if you need root. A couple of wipes of both the caches in between may also be done.
Click to expand...
Click to collapse
I am using the newest (twrp-3.1.1-2-oneplus3.img) but the problem is that I can't see anything in recovery or elsewhere :/
Peybro said:
Step 8 doesn't work for me...
I guess the phone goes back to the repair company then
Click to expand...
Click to collapse
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Peybro said:
Hey guys,
I think I'm a little bit in trouble: I just got a OP3 and wanted to root it as I'm used to it from the OPO.
But there were problems because of Force Encyption... After a few trys and flashs, I flashed Stock OOS (
OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
) from TWRP and after rebooting...
THE SCREEN IS YELLOW AND FULL OF PIXELS (like an olt TV).
You can feel it works from vibrations but you can't see what's going on... I tried this for unbricking but no success.
I think my phone's display drivers might be broken but idk.
Does anyone maybe know what to do here?
Click to expand...
Click to collapse
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Puddi_Puddin said:
Well you have really messed up something it seems.. This shouldnt be happening by rooting and stuff, I think it is pure coincidence
Click to expand...
Click to collapse
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
Renosh said:
What exactly did you flash other than OOS and recovery? Why did you need a few flashes? You flashed SuperSU or Magisk? Root still works on an encrypted system so not understanding some things from your post
Click to expand...
Click to collapse
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Peybro said:
I hope so - maybe the repair company messed the screen connection up and they fix it for free... :angel:
First I flashed newest TWRP and Paranoid Android but it wasn't as good as expected and so I flashed back to OOS (_008 I think) and everything worked but when I wanted to flash Magisk (because SafetyNet) via TWRP I couldn't because the phone wanted a pattern to unlock encryption.
I read that it would be the same as I used to unlock my phone (btw the only 1 I use) but it didn't work...
Before I found a guide with the right order to remove the encryption I tried different ways by myself (that's because I flashed a few times) (Toolkit, "Fastboot format userdata", TWRP format) but nothing removed it.
Then I wanted to follow that guide but meanwhile there was no OS at all and img Install via fastboot didn't work but I managed to get the newest stable OOS (_16 I think) on the phone, installed it with TWRP aaaaaand...
YELLOW-ORANGEish PIXEL SCREEN
fastboot and everything works - I just can't see what's going on
Click to expand...
Click to collapse
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
I can give it a try later (and in the future when everything works again) but I do not think (at least I can't imagine) that the problem I have comes from recovery.
I know the reason!
I found other people who also had a static screen and they said they could fix it by pressing the screen back on its contacts...
I did so and it worked!... A bit... For a few minutes...
So the static definitely wasn't the result of rooting and stuff but the repair company's fault.
I hope they accept their mistake and fix it. Thx for everyone here trying to hel me!
P.S.
tnsmani said:
I already asked you to use the TWRP from eng.stk
The official 3.1.1-2 works well with OOS but is cranky with custom ROMS. eng.stk's works both with OOS and custom ROMs.
Click to expand...
Click to collapse
And as soon as I can I will try this TWRP
-------------------------------- Edit: --------------------------------
(Just in case people get same problem)
[after Mega Unbrick Method 2 finally worked (I put the stock zip in the tool's folder)]
This morning I restarted the phone just because and I could see what was going on on the phone - but the display was still crazy with yellow tint and colorful stripes etc.). After setup it asked me to download & install newest stock rom; I did and after reboot everything was fine again....
Don't know what happened here but it seems to work again.
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?
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked
Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?
hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...
Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk
Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.
viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!
thanks InfinityXDA for the tutorial, you should create a post just for it~
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?
.
rodagola said:
Hello everyone on xda, please bare with me. Here's my story
I own a Redmi Note 8 pro, chinese rom model. It was running miui 11.0.3 over android 9 If I recall correctly.
Ok so... I was tired of some of the china apps pushing their notifications over and over and auto installing stuff, so I looked up how to apply adb commands to remove such bloatware, which was a fairly simple process. I copied and pasted a list of safe stuff to delete I found around some forums.
then... there were some other packages I checked out using an app called "app inspector", which directly tells you which app is under which package (totally useful for this purpose).
I tried to be careful not go overboard since I don't have any root access, or custom recovery, and wasn't really planning to have these, just wanted to keep this as my simple daily driver cellphone, but also perform this little maneuver to get rid of some bloatware.
little did I know, I was about to somehow softbrick it. More info: I did not use a screen lock method other than the "swipe up".
Ok, so I uninstalled some packages I cannot remember exactly how they went, but they had the terms "xman" and "yman" on them I think, I wasn't so sure about them because I looked them up on the web yet they didn't appear anywhere. I think they went something among the lines of "com.android.miui.xman". I also uninstalled 2 or 3 more, but after googling, they seemed unsuspecting.
Anyways, I'm aware there's a command to reinstall the packages because they're still on the phone's ROM image. That is in case I had to restore anything back to normal. Turns out I later rebooted the phone and when it launches the lock screen, I keep swiping up but it won't take me over to the actual MIUI launcher. The screen is frozen on the lock screen.
I'm not freaking out at this time because I still tried to connect the device to the pc, and it still shows as connected, I then go to the adb console and type "adb devices", it is still recognized, however, it says next to it that it is unauthorized... damn it. So now I might not be able to run the commands that allow me to reinstall the exact packages that are rendering the phone softbricked (I guess), plus I'm not really sure which package caused this.
After about a minute or two on the lock screen, the phone takes me to the "redmi-recovery 3.0",
which displays 3 options:
Reboot to system: which basically forms a loop
Wipe date: godforbid... really don't want to do it since I likely had many files not backedup
Contact miassistant: not sure what to do with this, says "pcsuite.mi.com" at the bottom
on the miassistant option you can apparently sideload stuff, idk how to go about this, maybe it allows me to install a slightly upgraded ROM, which in turn will work the same as if it was an OTA update (so it will keep my data as it was instead of wipe)? Because the point is not to erase my user data!!
I'm not sure how to feel or what to do without losing my pictures, notes and documents
I have hopes this situation can be turned around back to normal, and like the title implies... I'm WILLING to PAY you through paypal or something to WHOEVER offers to guide me through in the best way possible. Please if you have the knowledge/experience don't hesitate I'll also be grateful timelessly.
I'm not an expert at these scenarios so I might as well ask on xda where most are really skilled! Thanks in advance to those amazing souls
Click to expand...
Click to collapse
tldr;
If you can boot into fastboot mode you can just flash a official MIUI fastboot ROM:
Xiaomi Firmware Updater (where you can download official MIUI ROMS): https://xiaomifirmwareupdater.com/
This is the current hard unbrick method: https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
It should also work in your case and there's even a video guide.
This is another video guide for fixing a hard brick:
Both methods above will format your phone though (afaik all data will be lost).
Compass.
.
rodagola said:
are these the kind of roms that you unzip and have the BL, AP, CP, CSC files? I could try that, but I've heard installing home_csc will not override/wipe my personal data. If this is what you meant, can you confirm? Or do you reckon these linked video tutorials would not wipe the data?
Click to expand...
Click to collapse
Nope, it doesn't.
If you can boot into Fastboot, flash the ROM using Mi Flash, otherwise, use this tutorial:
.
Compass Linux and juliusjr have told you the method, so I will just add supplemential infos.
In your case, I think simple upgrade will do the trick, dirty flash is applicable both via fastboot flash (mi flash) and recovery flash (the mi assistant method). If you want to stop the ads, I will recommend you to unlock your bootloader, move to global, root, and use an adblocker (a bare minimum config, in trade of some bangking apps being blocked).
I don't know the corresponding version for miui china rom, but in global rom, prior 12.0.0.7 (the one with the early 2021 security update), you can dirty flash back and forth while keeping your data.
.
rodagola said:
Hi, thanks for your info, I would like to try the mi flash tool as I've been told before the stock recovery thing has less chances of working. However, I had dev options turned on before but didn't manage to turn on the "OEM unlock" option, will flashing original ROMs work this way? or did I need that option toogled on? That's my last doubt, and thanks a lot. Btw, the China ROM this Redmi N8P had never ever showed me any ads, but thanks a lot as well for such input
Click to expand...
Click to collapse
You still have a locked bootloader? (How do I know? You will see "Unloked" on the bottom of the screen everytime your device reboots and showing mi logo if your device is unlocked)
Hmm, mechanically it work like normal ota update. Full recovery update will ony erase nessesary partitions (system, boot, and some other things) while keeping your data intact. So doing this to your phone technically safe. You can do this with MiFlashPro, do a recovery update using a recovery rom (the 2 gigs one) greater than your current MIUI version. But please bear in mind that I have never done this before to a locked phone. A same distribution version IS A MUST (i.e. global with global).
Oh and it will need you to log in to your xiaomi account. My guess is you need the flash permission open for your account (if you have unlocked your phone you shouldn't have a problem). I have never flashed with an account that never have been used to unlock a bootloader, so I might be wrong.
If your phone is bootloader unlocked, Mi Flash is the least demanding and it can retain your data with "save user data" in the bottom right corner option on, regardless your miui version (but I think there will be some problem with installed apps if you downgrade from A10 to A9).
Hope this help.