Develop Bugs

A beginner and a Google pixel C

Hello,
I am looking, as a perfect beginner, to know what the root of my Google pixel C will allow. I encounter one or two problems (screen that freezes during heavy tasks, connections that breaks) on this tablet like many owners of this one and I have heard that the installation of a new system based on android can cancel these problems. So I would like to be enlightened on this subject! What are the best software to install? How to proceed (is it simple after all )? What can this bring?
That's it, I'd like to learn something. Thank you in advance for your answers

LineageOS 15.1 is a great advantage in contrast to the stock ROM (more settings, more smooth, more updates).
You have first to unlock the bootloader (developer settings), install TWRP and then flash lineageos, GApps, Vendor Image.
For detailed instruction search in this forum.

braunie said:
LineageOS 15.1 is a great advantage in contrast to the stock ROM (more settings, more smooth, more updates).
You have first to unlock the bootloader (developer settings), install TWRP and then flash lineageos, GApps, Vendor Image.
For detailed instruction search in this forum.
Click to expand...
Click to collapse
All right, very well, thank you. I still had some questions ?.
1. Can this improve performance as well? For example in games ?
2. what are the risks?
3. what does the term "Flash" mean?
4.Can I, if I wish, go back to the original version without any problem?
5. Is it complex to update lineageOS where can we do it from the system settings simply?
Thank you for your answers that's awesome!

I forgot to ask if:
Do we need a computer necessarily?
Is root required?
Sorry, there are a lot of questions. I hope you will take the time to answer ?

Hawkeye5 said:
All right, very well, thank you. I still had some questions .
1. Can this improve performance as well? For example in games ?
2. what are the risks?
3. what does the term "Flash" mean?
4.Can I, if I wish, go back to the original version without any problem?
5. Is it complex to update lineageOS where can we do it from the system settings simply?
Thank you for your answers that's awesome!
Click to expand...
Click to collapse
1. I'm not playing on my Pixel C, but LineageOS is more smooth than the stock ROM on my Pixel C
2. The risk is that you maybe brick your tablet
3. Flashing means to install an image (new Firmware) on your device
4. Yes, it is possibel
5. If you've never done this, it is difficult to do that, I've done this a few times, but it is every time a challange for me, so I would suggest you: let it be or find someone with expirience!!!

braunie said:
1. I'm not playing on my Pixel C, but LineageOS is more smooth than the stock ROM on my Pixel C
2. The risk is that you maybe brick your tablet
3. Flashing means to install an image (new Firmware) on your device
4. Yes, it is possibel
5. If you've never done this, it is difficult to do that, I've done this a few times, but it is every time a challange for me, so I would suggest you: let it be or find someone with expirience!!!
Click to expand...
Click to collapse
Thank you! I'm going to try to install lineageOS 15.1. In the meantime, I've been looking for a lot of tutorials so I think it should be fine. Anyway, just follow the instructions on the lineageOS website for installation and everything will be fine I think. What would you advise me as a topic on the forum about the advantages and inconveniences of lineageOS? Where can I find the vendor.img files specific for pixel C?

You might want to have a look at this topic
https://forum.xda-developers.com/pixel-c/help/pixel-c-oreo-8-1-unlock-bootloader-t3849422
starting at message 19 where I outline what is required to root and flash a ROM image.
I use the example of a Google Factory Image but Lineage will do.

m+a+r+k said:
You might want to have a look at this topic
https://forum.xda-developers.com/pixel-c/help/pixel-c-oreo-8-1-unlock-bootloader-t3849422
starting at message 19 where I outline what is required to root and flash a ROM image.
I use the example of a Google Factory Image but Lineage will do.
Click to expand...
Click to collapse
Where can I find vendor.img for lineageOS?: o

Not a clue, sorry.

Hawkeye5 said:
Thank you! I'm going to try to install lineageOS 15.1. In the meantime, I've been looking for a lot of tutorials so I think it should be fine. Anyway, just follow the instructions on the lineageOS website for installation and everything will be fine I think. What would you advise me as a topic on the forum about the advantages and inconveniences of lineageOS? Where can I find the vendor.img files specific for pixel C?
Click to expand...
Click to collapse
The vendor.img is a part of the factory image. The factury image is accessible here:
https://developers.google.com/android/images
Scroll down to "ryu" for Pixel C and download the latest factory image, unzip it and you'll find the vendor.img.
Alternative here is a link to the latest vendor.img on my google drive:
https://drive.google.com/file/d/1ptXKX_QGIb0EJRaBzap1fWYM5N507khL/view?usp=sharing
Good luck!

braunie said:
The vendor.img is a part of the factory image. The factury image is accessible here:
https://developers.google.com/android/images
Scroll down to "ryu" for Pixel C and download the latest factory image, unzip it and you'll find the vendor.img.
Alternative here is a link to the latest vendor.img on my google drive:
https://drive.google.com/file/d/1ptXKX_QGIb0EJRaBzap1fWYM5N507khL/view?usp=sharing
Good luck!
Click to expand...
Click to collapse
After all, is vendor.img really useful or is it optional?

Well, finally I flashed an Android 7.1.2 factory rom to start. And frankly, I did well. I'm happy with myself. It's true that I wanted to have lineageos at the base but I was a little afraid of the result. But finally it's perfecto with nougat 7.1.2. It's my first time.

Hello. Well, in the end I have a big problem with the c pixel. I followed all the steps on the Google site. So install adj and Fastboot with their drivers. Then double click on Flash_all.bat. All went well it rebooted and I can use the tablet without any problem. The only thing I didn't do was lock the bootloader because I thought it would wait until tomorrow. So everything works fine I have some features for you then I test the restart and there is a big mistake. I see the message: bootloader is unlocked and os verification is off the device continues booting in 30 second. Then a high-pitched beep and the Google logo appears but never changes. So nothing left and blocked on this logo. And did I do something stupid, did I brick it. I'm lost ?

It has now turned into a bootloop I think because it only restarts up to the four small circles that rotate the Google logo and then turns off and on again. I can still go to Recovery.

Hawkeye5 said:
It has now turned into a bootloop I think because it only restarts up to the four small circles that rotate the Google logo and then turns off and on again. I can still go to Recovery.
Click to expand...
Click to collapse
I had a similar issue. The cause seems to be TWRP-Recovery. Could you enter TWRP-Recovery mode?
If so; you have to flash lineageos, vendor.img and gapps by sideload. This is an option in TWRP to flash from your PC direct in TWRP. (Option: Advanced - ADB Sideload.)
This may be helpful:
https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/

braunie said:
I had a similar issue. The cause seems to be TWRP-Recovery. Could you enter TWRP-Recovery mode?
If so; you have to flash lineageos, vendor.img and gapps by sideload. This is an option in TWRP to flash from your PC direct in TWRP. (Option: Advanced - ADB Sideload.)
This may be helpful:
https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/
Click to expand...
Click to collapse
I created another post to better explain my problem. I also mentioned that I had managed to solve it but I still thank you for offering your help I flashed a Factory rom so I didn't have to install twrp. Actually I didn't know that I had to lock the bootloader immediately after flashing a Factory rom. Unlike custom rom. So I almost bricked my tablet at 400€
But it's good that you told me, though. ADB sideload is used to install the system and the Gapps at the same time, for example?

You do not have to lock the bootloader after installing a ROM or flashing a factory image.
I flash the factory image every month after a security update and have never locked the bootloader.

m+a+r+k said:
You do not have to lock the bootloader after installing a ROM or flashing a factory image.
I flash the factory image every month after a security update and have never locked the bootloader.
Click to expand...
Click to collapse
But you can still restart or turn off your device without any problem? It was when I restarted that I had the bootloop problem.
This is what is said on the Google developers website: "Once the script is finished, your device restarts. You should now lock the bootloader for security reasons:
Restart the device in Fastboot mode, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking the bootloader will erase data on some devices. After locking the bootloader, if you want the device to flash again, you must run fastboot oem unlock again, which will erase the data."

Hawkeye5 said:
But you can still restart or turn off your device without any problem? It was when I restarted that I had the bootloop problem.
This is what is said on the Google developers website: "Once the script is finished, your device restarts. You should now lock the bootloader for security reasons:
Restart the device in Fastboot mode, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking the bootloader will erase data on some devices. After locking the bootloader, if you want the device to flash again, you must run fastboot oem unlock again, which will erase the data."
Click to expand...
Click to collapse
Yes, of course I can restart and switch off without problems.
The problem with locking the bootloader again is, as Google says, you lose your data when you next want to install a ROM of flash a factory image.
The state of your bootloader isn't what is causing the bootloop.

Hawkeye5 said:
I created another post to better explain my problem. I also mentioned that I had managed to solve it but I still thank you for offering your help I flashed a Factory rom so I didn't have to install twrp. Actually I didn't know that I had to lock the bootloader immediately after flashing a Factory rom. Unlike custom rom. So I almost bricked my tablet at 400€
But it's good that you told me, though. ADB sideload is used to install the system and the Gapps at the same time, for example?
Click to expand...
Click to collapse
You could install system image, vendor image and gapps by sideload flashing in one session.

Would this procedure work? (install magisk and twrp on 10.0.3.0)

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~

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?

Full factory reset ? (locking bootloader, OTA updates,...)

Hi everyone,
i've recently put the hands on a MI A2 Lite. The previous user made some tricks on it and I want to do a full reset before trying some improvements on it.
For exemple, the bootloader is unlocked but i don't need it for now. I can run ADB prompts but the terminal doesn't recognize the phone when it's in Fastboot mode (fastboot oem lock OR fastboot flashing lock)
Also, the phone is currently in build V10.0.15.0.PDLMIXM. I can't get OTA updates.
Magisk was installed but i don't now which method was used.
What can i do to restore the phone as factory-like as possible ?
Thks

There's a bug with Xiaomi Mi A2 Lite fastboot drivers on modern versions of Windows. It is probably fixable by installing "optional updates" from the Windows Update settings screen, but I think that easier is booting up FWUL by @steadfasterX (you can make a bootable USB drive with Rufus) -- it has fastboot/adb drivers pre-configured. Before locking the bootloader, you will probably want to flash the latest firmware -- simply download it, unzip it, and run
Code:
bash flash_all.sh
, which will flash it through fastboot. It's a good idea to do this even if you want to flash a custom ROM right after.
Be aware that the stock ROM has some problems with task management, killing background activities very eagerly. I recommend to use a stable custom ROM, like Android 10 crDroid.

pufpufpuf said:
There's a bug with Xiaomi Mi A2 Lite fastboot drivers on modern versions of Windows. It is probably fixable by installing "optional updates" from the Windows Update settings screen, but I think that easier is booting up FWUL by @steadfasterX (you can make a bootable USB drive with Rufus) -- it has fastboot/adb drivers pre-configured. Before locking the bootloader, you will probably want to flash the latest firmware -- simply download it, unzip it, and run
Code:
bash flash_all.sh
, which will flash it through fastboot. It's a good idea to do this even if you want to flash a custom ROM right after.
Be aware that the stock ROM has some problems with task management, killing background activities very eagerly. I recommend to use a stable custom ROM, like Android 10 crDroid.
Click to expand...
Click to collapse
Unfortunately I have yet to find a custom ROM where Android Auto works. So far, only stock makes it possible to use Android Auto on this phone.

IkkeZelf1000 said:
Unfortunately I have yet to find a custom ROM where Android Auto works. So far, only stock makes it possible to use Android Auto on this phone.
Click to expand...
Click to collapse
That's a shame. Have you tried different GApps implementations? (OpenGapps, NikGapps, FlameGapps, ...) Also the Pixel Experience ROM has Gapps included, that might help with compatibility.

pufpufpuf said:
That's a shame. Have you tried different GApps implementations? (OpenGapps, NikGapps, FlameGapps, ...) Also the Pixel Experience ROM has Gapps included, that might help with compatibility.
Click to expand...
Click to collapse
Tried them all on most if not all ROM's. Even PE (still Android 10 at the time, but discontinued since) didn't work.

Thanks for your responses.
I tried FWUL, its a great tool but I miss a decent USB stick to get full use of it. So I've updated ADB related USB Drivers on Windows update and it worked like a charm.
I'm giving a try on the last stock ROM for now, otherwise I'll go for CRdroid.
For apps requiring a non-rooted phone (banking for ex), I'll try sandbox apps like Island or Shelter, because Magisk Hide wasn't enough in the past.

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

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

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

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

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

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

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

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

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

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

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

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

Old_Mil said:
I'm guessing that since it's not the latest, if I try and flash it that the antirollback protection will brick the handset...?
Click to expand...
Click to collapse
There is no anti-rollnack protection in Xiaomi.eu scripts
In the Xiaomi.eu Forum, Stable MIUI 13 thread, post #1 there is a link to AFH:
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Scroll there to find the zip for 5G Lite NE that has Fastboot in the name. There are two (third is the newest, no fastboot in the name, it's recovery type ROM) and take the newer fastboot
And please read instructions in that thread, same post #1, how to install. EVERYTHING is explained there (read about Fastboot installation part), do not ask me how to install or so, I will no more help you with additional info or so, because everything explained there (I will really not waste my time for writing the same things
All of us were able to install by properly following that same guide - hence for those who want to concentrate and read, the guide is enough
Good luck

zgfg said:
There is no anti-rollnack protection in Xiaomi.eu scripts
In the Xiaomi.eu Forum, Stable MIUI 13 thread, post #1 there is a link to AFH:
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Scroll there to find the zip for 5G Lite NE that has Fastboot in the name. There are two (third is the newest, no fastboot in the name, it's recovery type ROM) and take the newer fastboot
Click to expand...
Click to collapse
Thanks! This worked perfectly, flashed the EU Rom and the phone booted - initially into Mi Recovery and then into the full Mi13/A12 OS.
The problem I was having is I was trying this on my 2-1 with a 7 inch screen, and the filenames on Sourceforge were truncated so I couldn't see that any had fastboot in the name. I hovered over the files with 5GNE in the filename and then found the one you describe.
Thanks again, it's working.
Now I just have to supress the urge to try flasing Pixel Experience and breaking it again.

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

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

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