Database Develop

[guide][kernel] how to install a gsi[eu variant only guaranteed]

Hey folks i took the afford and unlocked by bootloader and flash a gsi , i noticed sound and wifi were broken and investigated then i recompiled the olive kernel with some changes hacked together a working kernel image (the sources xiaomi provided are broken)
DOWNLOADS:
AndroidFileHost
STEPS
1. unlock your bootloader
2. disable avb by reflashing vbmeta "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2. boot into twrp on your pc type "adb shell" then "mount -o rw /dev/block/bootdevice/by-name/vendor /vendor " (if your touch works in twrp you can just hit mount and vendor)
4. push the edited fstab file "adb push fstab.qcom /vendor/etc/"
5. flash the gsi , download the one of your choise , even tho we are a only we need arm64 a/b gsis others wont work "fastboot flash system pathtogsisystemimghere"
6. wipe the data to remove the encryption "fastboot -w" (if touch in twrp works hit wipe format data type yes)
7. flash my kernel (fastboot flash boot BOOT_GSI.img )
8 reboot the device (fastboot reboot)
9. after first boot is done enable adb
10. type "adb root" then "adb remount" then "adb push pathtotheoverlayapkilinked /system/overlay/" then "adb reboot"
ALL COMMANDS ARE TYPED WITHOUT ""​
Thanks
phh for his gsis
erfan adbi for helping me figuring out how to fix module loading
sellerie for his method of reusing a kernel dtb
me for putting this all together and recompiling the kernel
SOURCES

Thanks for figuring out and writing it all down for us!
Where can I download the vbmeta.img?
Trying to do this. Got a Redmi 8 EU version with novatek touchscreen, no touch in twrp. Should still work, right? I do not need to do anything in twrp correct?
EDIT: Never mind, other recovery works. How does your kernel compare to stock? Why was it necessary to recompile it? I just installed LOS gsi 5 minutes ago, thanks for your help.
(Also, just out of curiosity: What does fstab.qcom do exactly?

M47Z said:
Thanks for figuring out and writing it all down for us!
Where can I download the vbmeta.img?
Trying to do this. Got a Redmi 8 EU version with novatek touchscreen, no touch in twrp. Should still work, right? I do not need to do anything in twrp correct?
EDIT: Never mind, other recovery works. How does your kernel compare to stock? Why was it necessary to recompile it? I just installed LOS gsi 5 minutes ago, thanks for your help.
(Also, just out of curiosity: What does fstab.qcom do exactly?
Click to expand...
Click to collapse
which recovery does work for you also how can i find out what screen i do have , the kernel was needed to be recompiled since the modules werent loading at all so we had no sound and no wifi i edited the kernel config to ignore module signatures and also force load modules.
the new fstab does disable the force encryption if it is enabled the gsi will bootloop

M47Z said:
Thanks for figuring out and writing it all down for us!
Where can I download the vbmeta.img?
Trying to do this. Got a Redmi 8 EU version with novatek touchscreen, no touch in twrp. Should still work, right? I do not need to do anything in twrp correct?
EDIT: Never mind, other recovery works. How does your kernel compare to stock? Why was it necessary to recompile it? I just installed LOS gsi 5 minutes ago, thanks for your help.
(Also, just out of curiosity: What does fstab.qcom do exactly?
Click to expand...
Click to collapse
got ya , uploaded vbmeta.img also uploaded redmi8 overlay apk so brightness will start work etc just check the updated steps 9 and 10

J0SH1X said:
which recovery does work for you also how can i find out what screen i do have
Click to expand...
Click to collapse
probably property sys.panel.display show it. By me:
Code:
~$ adb shell getprop sys.panel.display
tianma

Compatibility
Does all redmi 8 olive support this? ( im new in this gsi and im also noob bout this stuff) thanks!:fingers-crossed::fingers-crossed:

Probe07 said:
Does all redmi 8 olive support this? ( im new in this gsi and im also noob bout this stuff) thanks!:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You are in correct thread. If something is not working in GSI for your olive , you can report it here.

jkkk88 said:
You are in correct thread. If something is not working in GSI for your olive , you can report it here.
Click to expand...
Click to collapse
yeah he is in the right thread , it might work on other variants or maybe not , it will boot for sure but idk if my kernel will work for any other variant then eu , just test and report

Could you give a noob a link to where I can find gsi's. If there are more than one please give me a link to the one you used succesfully. Thanks.

OK, found little time and tried:
history:
MIUI version: MIUI Global 10.3.1 | Stable / 10.3.1.0 (PCNEUXM)
MIUI version: MIUI by xiaomi.eu 11.0.4 | Stable / 11.0.4.0 (PCNCNXM)
GSI AOSP 10.0 v.208 / AOSP 9.0 v.123 installed according J0SH1X guide
Wifi, touchscreen working only till first display lock. Display brighthness and volume cannot be smoothly set
Currently getting warning before first login after each reboot:.
There's an internal problem with your device. Contact your manufacturer for details.
When touchscreen doesn't respond to your taps, you can still use mouse connected via OTG or ADB cli.
Mouse and adb is working fine also in Unofficial TWRP 3.3.1-1127 for REDMI 8 by wzsx150, just checked.

jkkk88 said:
OK, found little time and tried:
history:
MIUI version: MIUI Global 10.3.1 | Stable / 10.3.1.0 (PCNEUXM)
MIUI version: MIUI by xiaomi.eu 11.0.4 | Stable / 11.0.4.0 (PCNCNXM)
GSI AOSP 10.0 v.208 / AOSP 9.0 v.123 installed according J0SH1X guide
Wifi, touchscreen working only till first display lock. Display brighthness and volume cannot be smoothly set
Currently getting warning before first login after each reboot:.
There's an internal problem with your device. Contact your manufacturer for details.
When touchscreen doesn't respond to your taps, you can still use mouse connected via OTG or ADB cli.
Mouse and adb is working fine also in Unofficial TWRP 3.3.1-1127 for REDMI 8 by wzsx150, just checked.
Click to expand...
Click to collapse
the warning is expected because my kernel securety patch level is newer then the one provided by vendor , the boot level is the day i packed the bootimage thats why this is happening and i dont have an idea how to set

J0SH1X said:
got ya , uploaded vbmeta.img also uploaded redmi8 overlay apk so brightness will start work etc just check the updated steps 9 and 10
Click to expand...
Click to collapse
Alright so this took me a while, this is what I found out:
I got Redmi 8 EU 4/64GB, on MIUI V11.0.1.0.PCNEUXM. I tried all this stuff with LineageOS 16 GSI (download here)
So I tried to follow your steps and it seems to be working alright. But there were some bugs: Fingerprint would not work. When I would set up a pin, pattern etc, it would not work after setup. LineageOS complained about decrypted phone. I then tried all kind of things and this is what I found out:
- We dont need a custom kernel. The stock one from latest stable MIUI (V11.0.1.0.PCNEUXM) works just fine as far as I have tested.
- We do not need a modified vbmeta, just flash the stock one with --disable-verification option.
- Instead of flashing fixed overlay we can also fix the brightness in LOS by entering "setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)" in adb su shell.
So the fastest way to get LOS running (at least on EU version, without TWRP) should be:
0. Make sure you are on latest stable MIUI V11.0.1.0.PCNEUXM. Download and unpack LineageOS 16 GSI, also download vbmeta_stock_V11.0.1.0.PCNEUXM.img from attachments.
1. Unlock bootloader.
2. Flash system image: "fastboot flash system /path/to/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img"
3. Wipe data: "fastboot -w"
4. Disable verification: "fastboot flash vbmeta --disable-verification /path/to/vbmeta_stock_V11.0.1.0.PCNEUXM.img"
5. Reboot: "fastboot reboot"
6. Fix screen brightness: Enable developer settings, in there enable root for adb. Connect to PC and type:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Done! LineageOS 16 works, fingerprint and pin working, encryption working, brightness working,found no bugs so far but only tried it for a couple of hours. Don't know if we need your kernel and mods for other roms though. On LineageOS something in your steps breaks the system, I guess it is the edited fstab and/or the --disable-verity option when flashing vbmeta (or vbmeta itself? ).
Hope this helps someone! Merry christmas!

M47Z said:
Alright so this took me a while, this is what I found out:
I got Redmi 8 EU 4/64GB, on MIUI V11.0.1.0.PCNEUXM. I tried all this stuff with LineageOS 16 GSI (download here)
So I tried to follow your steps and it seems to be working alright. But there were some bugs: Fingerprint would not work. When I would set up a pin, pattern etc, it would not work after setup. LineageOS complained about decrypted phone. I then tried all kind of things and this is what I found out:
- We dont need a custom kernel. The stock one from latest stable MIUI (V11.0.1.0.PCNEUXM) works just fine as far as I have tested.
- We do not need a modified vbmeta, just flash the stock one with --disable-verification option.
- Instead of flashing fixed overlay we can also fix the brightness in LOS by entering "setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)" in adb su shell.
So the fastest way to get LOS running (at least on EU version, without TWRP) should be:
0. Make sure you are on latest stable MIUI V11.0.1.0.PCNEUXM. Download and unpack LineageOS 16 GSI, also download vbmeta_stock_V11.0.1.0.PCNEUXM.img from attachments.
1. Unlock bootloader.
2. Flash system image: "fastboot flash system /path/to/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img"
3. Wipe data: "fastboot -w"
4. Disable verification: "fastboot flash vbmeta --disable-verification /path/to/vbmeta_stock_V11.0.1.0.PCNEUXM.img"
5. Reboot: "fastboot reboot"
6. Fix screen brightness: Enable developer settings, in there enable root for adb. Connect to PC and type:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Done! LineageOS 16 works, fingerprint and pin working, encryption working, brightness working,found no bugs so far but only tried it for a couple of hours. Don't know if we need your kernel and mods for other roms though. On LineageOS something in your steps breaks the system, I guess it is the edited fstab and/or the --disable-verity option when flashing vbmeta (or vbmeta itself? ).
Hope this helps someone! Merry christmas!
Click to expand...
Click to collapse
vbmeta is stock non patched one i extracted out of a stock rom zip i downloaded also i noticed the kernel thing aswell , idk why it wasnt working earlier for me but if anyone has no working wifi and sound we atleast know how to fix that , also install the overlay apk it will fix up notch and statusbar and rounded corners aswell

M47Z said:
Alright so this took me a while, this is what I found out:
I got Redmi 8 EU 4/64GB, on MIUI V11.0.1.0.PCNEUXM. I tried all this stuff with LineageOS 16 GSI (download here)
So I tried to follow your steps and it seems to be working alright. But there were some bugs: Fingerprint would not work. When I would set up a pin, pattern etc, it would not work after setup. LineageOS complained about decrypted phone. I then tried all kind of things and this is what I found out:
- We dont need a custom kernel. The stock one from latest stable MIUI (V11.0.1.0.PCNEUXM) works just fine as far as I have tested.
- We do not need a modified vbmeta, just flash the stock one with --disable-verification option.
- Instead of flashing fixed overlay we can also fix the brightness in LOS by entering "setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)" in adb su shell.
So the fastest way to get LOS running (at least on EU version, without TWRP) should be:
0. Make sure you are on latest stable MIUI V11.0.1.0.PCNEUXM. Download and unpack LineageOS 16 GSI, also download vbmeta_stock_V11.0.1.0.PCNEUXM.img from attachments.
1. Unlock bootloader.
2. Flash system image: "fastboot flash system /path/to/lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img"
3. Wipe data: "fastboot -w"
4. Disable verification: "fastboot flash vbmeta --disable-verification /path/to/vbmeta_stock_V11.0.1.0.PCNEUXM.img"
5. Reboot: "fastboot reboot"
6. Fix screen brightness: Enable developer settings, in there enable root for adb. Connect to PC and type:
Code:
adb shell
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
Done! LineageOS 16 works, fingerprint and pin working, encryption working, brightness working,found no bugs so far but only tried it for a couple of hours. Don't know if we need your kernel and mods for other roms though. On LineageOS something in your steps breaks the system, I guess it is the edited fstab and/or the --disable-verity option when flashing vbmeta (or vbmeta itself? ).
Hope this helps someone! Merry christmas!
Click to expand...
Click to collapse
how did you fix fingerprint and pattern im kinda loosing my mind over it here , if i reenable force encryption the phone will ALWAYS reboot to twrp with pstore telling me vold died , im using aosp not lineageos tho

J0SH1X said:
how did you fix fingerprint and pattern im kinda loosing my mind over it here , if i reenable force encryption the phone will ALWAYS reboot to twrp with pstore telling me vold died , im using aosp not lineageos tho
Click to expand...
Click to collapse
Thought I was not the only one restore latest MIUI with fastboot method. Important: Check "clean all" instead of "clean all and lock" or you will have to do the whole unlock process again. After that, follow the steps exactly as I wrote in the post before. Do NOT flash BOOT_GSI.img, fstab.qcom or treble-overlay-xiaomi-redmi8.apk. You do not need TWRP for this, but you can just install it afterwards if you want. Good luck! :good:
J0SH1X said:
vbmeta is stock non patched one i extracted out of a stock rom zip i downloaded also i noticed the kernel thing aswell , idk why it wasnt working earlier for me but if anyone has no working wifi and sound we atleast know how to fix that , also install the overlay apk it will fix up notch and statusbar and rounded corners aswell
Click to expand...
Click to collapse
I guess vbmeta changed with some later update then! The one I attatched is also just pulled from latest MIUI, no modification. I strongly think wrong/mismatching vbmeta and/or --disable-verity option while flashing it causes the fingerprint/pattern/pin/... bug, at least in LineageOS 16 GSI.

M47Z said:
Thought I was not the only one restore latest MIUI with fastboot method. Important: Check "clean all" instead of "clean all and lock" or you will have to do the whole unlock process again. After that, follow the steps exactly as I wrote in the post before. Do NOT flash BOOT_GSI.img, fstab.qcom or treble-overlay-xiaomi-redmi8.apk. You do not need TWRP for this, but you can just install it afterwards if you want. Good luck! :good:
I guess vbmeta changed with some later update then! The one I attatched is also just pulled from latest MIUI, no modification. I strongly think wrong/mismatching vbmeta and/or --disable-verity option while flashing it causes the fingerprint/pattern/pin/... bug, at least in LineageOS 16 GSI.
Click to expand...
Click to collapse
The vbmeta flag is not it that's the official way of disabling avb documented in Google docs.
Also I pred phh to fix brightness
https://github.com/phhusson/device_phh_treble/pull/137

J0SH1X said:
The vbmeta flag is not it that's the official way of disabling avb documented in Google docs.
Click to expand...
Click to collapse
Well we surely do not need it to run LOS. Is it possible it does not need avb disabled? OP in the thread says: "verified booting on an arm64 ab device I own".
But I am 100% sure: On untouched latest stable MIUI, if you follow the steps by OP exactly with LOS, it will not work, you will get fingerprint/pin/... error and non encrypted device. If you do it like I wrote, flashing latest stock vbmeta with --disable-verification only, and NOT installing fstab.qcom, BOOT_GSI.img or treble-overlay-xiaomi-redmi8.apk, it will all work nicely. If vbmeta is not the issue, then it is the fstab. Might be different for other roms of course.
J0SH1X said:
Also I pred phh to fix brightness
https://github.com/phhusson/device_phh_treble/pull/137
Click to expand...
Click to collapse
Nice :good:

As there is a new Version , here is the vbmeta for those who want to try it out with V11.0.2.0.PCNEUXM. I got it from here:
https://xiaomifirmwareupdater.com/miui/olive/
I will try it in a few weeks.
And many thanks to @M47Z for your instructions. This will save me and others much time.

rudolfm said:
As there is a new Version , here is the vbmeta for those who want to try it out with V11.0.2.0.PCNEUXM. I got it from here:
https://xiaomifirmwareupdater.com/miui/olive/
Click to expand...
Click to collapse
Hmm maybe I am blind but... there is no V11.0.2.0.PCNEUXM right? Global and China got 11.0.3.0, Indonesia and India got 11.0.2.0, and Europe and Russia got 11.0.1.0 at the moment. So latest for European phone is V11.0.1.0.PCNEUXM right?

M47Z said:
Hmm maybe I am blind but... there is no V11.0.2.0.PCNEUXM right? Global and China got 11.0.3.0, Indonesia and India got 11.0.2.0, and Europe and Russia got 11.0.1.0 at the moment. So latest for European phone is V11.0.1.0.PCNEUXM right?
Click to expand...
Click to collapse
Global version has two different versions.one of them PCNEUXM (Europe)
and one is the real global PCNIM blah blah blah blah blah.....really stupid xiaomi ...
Sent from my Redmi 8 using Tapatalk

Question How to flash gsi without twrp?

Sorry Im new in xiaomi modding,is there a way to flash gsi without twrp?,can I flash gsi from fastboot?

yes, via fastboot. the command is flash system system.img (replace system with the name of the rom). connect to nippon gsi telefram Channel. you can find a large choice of ported rom from xiaomi devices. but i'm not sure vendor are fully compatibile with mediatek. but you can try. flashing system don't damage the bootloader. so you can reflash easy stock in case of problems

wetito said:
yes, via fastboot. the command is flash system system.img (replace system with the name of the rom). connect to nippon gsi telefram Channel. you can find a large choice of ported rom from xiaomi devices. but i'm not sure vendor are fully compatibile with mediatek. but you can try. flashing system don't damage the bootloader. so you can reflash easy stock in case of problems
Click to expand...
Click to collapse
You tried it first???

no... my phone is 3 days old. First i want to test miui. and i think this phone will recive miui 13. so at now i don't want to do heavy modding. only debloating. i like miui. aosp rom have bored me. on my old mi A3 i have try many gsi also android 12 beta. but mi a3 is not an mtk phone. so the only way to know if gsi works is try. i'm quite sure that many gsi will boot. i think the gsi much compatible are note 8 ported

Installed android 12 gsi via dynamic system update. Requires a unlocked bootloader.
Note that my phone has dm-verify corrupt on boot, but still works. The dsu loader seems to be functional. You would have package custom gsi's to load via dsu.
But being able to duel boot std ROM + gsi ROM is a win

Auswolf said:
Installed android 12 gsi via dynamic system update. Requires a unlocked bootloader.
Note that my phone has dm-verify corrupt on boot, but still works. The dsu loader seems to be functional. You would have package custom gsi's to load via dsu.
But being able to duel boot std ROM + gsi ROM is a win
Click to expand...
Click to collapse
Can you try to flash only gsi ROM?

if dsu work well, is the best safe way to try a12. great tips!!!!! sometimes gsi are not fully compatible with vendor. and in particular MTK devices are not modding phones. 99,9% of dev hare on snapdragons. maybe if xiaomi will launch more mtk devides out of China, the situation could change. But in my opinion MIUI don't need to be modded. only debloated and unlocked. Our phone sure will recive miui13 based on A12. I have tryed aosp beta, and the dynamic theming is a fantastic function. implemend on miui will make this rom super cool

Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.

Auswolf said:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Click to expand...
Click to collapse
nice! connect to nippon gsi. there is a lot of gsi. of all major custom rom. and also miui

Auswolf said:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Click to expand...
Click to collapse
But I want only 1 boot not dual boot

use command fastboot flash system... or via twrp (twrp touch don't work but you can use twrp manager in pc terminal with phone connected via usb). internet is full of guide how to flash gsi via twrp. if you like aosp rom try android 12 beta. or dot os. new 5.2 is out. the system ui is very cool. and official gsi for all android go out soon

wetito said:
use command fastboot flash system... or via twrp (twrp touch don't work but you can use twrp manager in pc terminal with phone connected via usb). internet is full of guide how to flash gsi via twrp. if you like aosp rom try android 12 beta. or dot os. new 5.2 is out. the system ui is very cool. and official gsi for all android go out soon
Click to expand...
Click to collapse
Can you try I don't want to brick my phone

oh no! my phone is 3 day old and i love miui. it's impossibile damage bootloader flashing a generic system img. you have alreagy unlock bootloader. if phone dont dont boot you can easily reflash stock via miflash. i will bootloader only when xiaomi will stops major updates. i post my news only for user that live aosp roms

wetito said:
oh no! my phone is 3 day old and i love miui. it's impossibile damage bootloader flashing a generic system img. you have alreagy unlock bootloader. if phone dont dont boot you can easily reflash stock via miflash. i will bootloader only when xiaomi will stops major updates. i post my news only for user that live aosp roms
Click to expand...
Click to collapse
My bootloader still not unlocked ._. but I bricked my phone just putting it in fastboot mode

it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding

wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
My phone bricked after going to fastboot and DM verify corrupted
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse

Fire1511 said:
My phone bricked after going to fastboot and DM verify corrupted
Click to expand...
Click to collapse
because you flashed a bad full rom with boitloader locked. i suppose a china rom. all guide are clear "Unlock bootloader before"
using a gsi is safe to prevent big damage. because flash only system partition. probably you didn't read guide with attention. modding must do carefully. i suggest you reflash stock in edl mode. is the only solution

wetito said:
because you flashed a bad full rom with boitloader locked. i suppose a china rom. all guide are clear "Unlock bootloader before"
using a gsi is safe to prevent big damage. because flash only system partition. probably you didn't read guide with attention. modding must do carefully. i suggest you reflash stock in edl mode. is the only solution
Click to expand...
Click to collapse
I don't flashed anything lol

Fire1511 said:
I don't flashed anything lol
Click to expand...
Click to collapse
you said "my phone is bricked after going to fastboot". it can happen only if you have made a mod. like a no stock recovery or a non stock rom. or you said a lot of stupid claims

wetito said:
you said "my phone is bricked after going to fastboot". it can happen only if you have made a mod. like a no stock recovery or a non stock rom. or you said a lot of stupid claims
Click to expand...
Click to collapse
I went to fastboot fastboot

Question Where do I find TWRP for the Redmi Note 11 and how do I flash it?

As the title says. I managed to unlock the bootloader but now I need to install TWRP to install magisk, right? How do I get around doing that? There are some shady downloads on the internet but on twrp.me there is nothing for the phone. What do I do? Thanks in advance!

the device does not have official TWRP, the others available on telegram group do work fine

Thank you, but what telegram group? Could you forward me a link to it or something?

GeoS__ said:
Thank you, but what telegram group? Could you forward me a link to it or something?
Click to expand...
Click to collapse
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

SubwayChamp said:
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thanks a lot. Is there a spesn version? Can I flash this spes version on my spesn phone? Thank you in advance

GeoS__ said:
Thanks a lot. Is there a spesn version? Can I flash this spes version on my spesn phone? Thank you in advance
Click to expand...
Click to collapse
spes and spesn are the same device. the "n" in spesn stands for NFC support

MarvavCZE said:
spes and spesn are the same device. the "n" in spesn stands for NFC support
Click to expand...
Click to collapse
Oh really? Can i flash it then? I really do not care much for NFC.

GeoS__ said:
Oh really? Can i flash it then? I really do not care much for NFC.
Click to expand...
Click to collapse
Of course, you can, in recovery builds these differences don't matter.

just rooted with FASTBOOT and latest Magisk.App
How to Root Xiaomi MIUI 13 based on Android 12 via Magisk
In this guide, we will show you the detailed steps to root your Xiaomi device running MIUI 13 based on Android 12 via Magisk.
www.droidwin.com
Installation
The Magic Mask for Android
topjohnwu.github.io
Current installed MiUi version needs to match the complete Recovery Image you have to download
in my case:
https://bigota.d.miui.com/V13.0.11.0.RGKEUXM/spesn_eea_global_images_V13.0.11.0.RGKEUXM_20220606.0000.00_11.0_eea_5c36ea339b.tgz
or
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Extracting the Boot.Img - let magic app patch it on your fone copy back to Computer and install it like described on "droidwin":
fastboot flash boot magisk_patched-25100_0UGhl.img
have fun
linolino

GeoS__ said:
As the title says. I managed to unlock the bootloader but now I need to install TWRP to install magisk, right? How do I get around doing that? There are some shady downloads on the internet but on twrp.me there is nothing for the phone. What do I do? Thanks in advance!
Click to expand...
Click to collapse
I am in the same situation,
ie. I have a Note 11 Pro without NFC
[Phone code: SPES ]
• bootloader unlocked from Xiaomi (after 7+ days waiting)
• running MIUI Global 13.0.15 [ RGCMIXM ] , Android v 11 RKQ1.211001.001
I have following TWRP
- twrp-3.6.2-12.1-21.06.22
- twrp-3.6.2_12-0-spes-Jabiyeff
and I tried to flash TWRP in fastboot (below), but it always fails and does not work
Code:
fastboot flash recovery twrp.img
I'm used to flashing TWRP and ROMs, but it's been a while since I touched a Xiaomi device,
so I am wondering is there anything different that I need to do ?
also, any 'new methods' for flashing Magisk ?
( and passing SafetyNet )

I am typing this on my custom ROM. I did not flash through fastboot. I booted to the twrp img with it though (fastboot boot twrp.img if i remember correctly.) and, well, i flashed from the option inside twrp

GeoS__ said:
I am typing this on my custom ROM. I did not flash through fastboot. I booted to the twrp img with it though (fastboot boot twrp.img if i remember correctly.) and, well, i flashed from the option inside twrp
Click to expand...
Click to collapse
so, you flashed TWRP recovery, by booting the TWRP from your PC ?
OK... I can try that.

exactly. i connected with adb and checked with adb devices, then pushed the twrp image to the phone and booted off of it through fastboot. if it works booting off of the img it's pretty safe to flash

To flash a custom recovery on Spes, you need to first run the following command in fastboot on the pc:
fastboot boot XXX.img (this is the name of twrp/ofox/Shrp image)
then inside the recovery, you must go to advanced and select the option flash this twrp, with that the recovery is installed by default. But remember that every time you install a new rom, the recovery will change, so you should flash twrp every time you finish installing a new rom.

Microsheepcl said:
To flash a custom recovery on Spes, you need to first run the following command in fastboot on the pc:
fastboot boot XXX.img (this is the name of twrp/ofox/Shrp image)
then inside the recovery, you must go to advanced and select the option flash this twrp, with that the recovery is installed by default. But remember that every time you install a new rom, the recovery will change, so you should flash twrp every time you finish installing a new rom.
Click to expand...
Click to collapse
exactly! twrp even offers a checkbox to automatically reflash itself after the rom when flashing

interesting, it seems to work a little bit different than what I did before! thx for sharing your knowledge

metaxda said:
I am in the same situation,
ie. I have a Note 11 Pro without NFC
[Phone code: SPES ]
• bootloader unlocked from Xiaomi (after 7+ days waiting)
• running MIUI Global 13.0.15 [ RGCMIXM ] , Android v 11 RKQ1.211001.001
I have following TWRP
- twrp-3.6.2-12.1-21.06.22
- twrp-3.6.2_12-0-spes-Jabiyeff
and I tried to flash TWRP in fastboot (below), but it always fails and does not work
Code:
fastboot flash recovery twrp.img
I'm used to flashing TWRP and ROMs, but it's been a while since I touched a Xiaomi device,
so I am wondering is there anything different that I need to do ?
also, any 'new methods' for flashing Magisk ?
( and passing SafetyNet )
Click to expand...
Click to collapse
Have these twrp you used decrypted the device succesfully? The both twrp i used didnt work on decrypt, and both bootlooped my phone after trying to flash them to recovery(others/flash to device), The one that worked on me was a unnoficial Ofox

UltimaDea said:
Have these twrp you used decrypted the device succesfully? The both twrp i used didnt work on decrypt, and both bootlooped my phone after trying to flash them to recovery(others/flash to device)
Click to expand...
Click to collapse
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"

gentano said:
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
Click to expand...
Click to collapse
3.6.1 only works for MIUI A11 ROMs
3.6.2 only works for AOSP and A12 MIUI (but no for MIUI ROM flashing)
3.7.0 fully works for any ROM except A11

gentano said:
This is actually pretty tricky. I found 5 different recoveries for spes/n:
OrangeFox-R11.1_A12.1-Unofficial-spes.img
twrp_v.3.6.2_11_spes-2022.08.14.img
twrp-3.6.2_12-0-spes-Jabiyeff.img
twrp-3.7.0_12-0-spes-dblenk9.img
and the one and only working one:
twrp_3.6.1-spes.img (google it), my SHA256 is: 27335ab466fadb458e090bce098b3bc9302b2876d0faf392371a23bf6fe902c
Only with this last one I was able to successfully decrypt my existing (PIN protected!) data partition of the following ROM I currently use: MIUI Global 13.0.13.0 (RGKEUXM)
I hope this helps anybody.
Also I just installed Magisk 25.2 zip via this TWRP version and its working like a charme.
Edit: Flash TWRP via fastboot with the following fastboot command:
"fastboot boot twrp.img"
twrp.img is the name of your twrp file.. this will boot up this TWRP and You can directly check if You can decrypt ur existing data partition.. if You succeed then go to Advanced and click on "Flash current TWRP"
Click to expand...
Click to collapse
Both the TWRP 3.6.2-12.1 and TWRP 3.7.0_12-0-spes works on my phone (SPES Global)
I am on android 12 version of MIUI 13. In fact I used the TWRP 3.7 to flash MIUI13.EU 13.0.5 A12 ROM and it works.
The two versions above can decrypt my phone without any problem. MTP also works in recovery mode.
Your phone is using Android 11. Probably that's the reason the TWRP versions I've mentioned above does not work for you.
I tend to agree with NeoSDAP.

Question HELP I bricked my phone - Stuck on fastboot loop

So I really new into this, I didn't really know what I was doing but i tried to install Pixel Experience on my device. After some struggle it seems that I managed to flash the rom into system. I followed the instruccions to the part where you wipe all data from the phone, but then it got stucked and didn't start the OS, maybe system got corrupted or something bc when I try to reinstall the rom cmd tells me "This partition doesn't exists".
As far as i know there isn't a version of twrp for Redmi note 10 5g so all I have is Xiaomi ADB Fastboot Tools. Pls help me.

What firmware do you want to install？
Can you elaborate on your installation process, guide instructions and firmware sources?

1:
Do not need to use twrp, general Fastboot command to brush the GSI on the line, after installation to play some black screen patch and settings.
GSI always jumps to Fastboot and Recovery after booting, indicating that there is a problem with GSI, replace it with another variant or downgrade version.
2:
Fastboot Method
https://c.mi.com/thread-1857937-1-0.html

jianjianus said:
What firmware do you want to install？
Can you elaborate on your installation process, guide instructions and firmware sources?
Click to expand...
Click to collapse
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
Fire1511 said:
Code:
I am NOT responsible for bricked devices, destroyed SD cards or any
damage that may happen to your device.
Requirements:
Unlocked bootloader.
WARNING​Don't use Nippon gsi they aren't working,I recommend using phh gsi by @phhusson lineage os by @AndyYan and PE 12 by @ponces
How to guide:
power + volume down button
fastboot reboot fastboot
install fastbootd drivers,follow this tutorial
fastboot set_active a
fastboot erase system
fastboot flash system (name gsi.img)
fastboot --disable-verity --disable-verification flash vbmeta (vbmeta.img)
fastboot flash vbmeta_b (vbmeta.img)
fastboot set_active a
fastboot reboot recovery
in recovery select wipe data
reboot to system
The GSI will be installed in your phone
Bugs:
Brightness slider but you can fix it
Recommended rom:
Pixel experience:
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Select arm64 ab variant
How to fix brightness slider:
Go to phh treble settings,misc settings enable "use alternative brightness scale", "use linear screen brightness slider" and "allow setting brightness to the lowest possible",reboot the device
There is an better alternative to fix this annoying bug,follow this guide!
[GSI] Brightness Fix & Other Fixes
Brightness black lockscreen fixed & Brightness Slider fix. GSI Misc Settings ✅Use Linear Brightness Scale ✅Force Alternatice Backlight Scale ✅Allow Settings to the lowest Flash this file on magisk and reboot :) Note: There's a better fix...
forum.xda-developers.com
How to fix bluetooth audio:
Go to phh treble settings,misc settings, "Force enable a2dp off-load" and "Bluetooth workarounds" select mediatek option and reboot the device.
How to install magisk on your device:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
How to flash gapps:
You need magisk on your phone
Download this file then flash from magisk
MagiskGApps - Browse /r/Stock at SourceForge.net
GApps for Magisk
sourceforge.net
Click to expand...
Click to collapse
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab

chileangarbage said:
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
Some people have given feedback that this phenomenon occurs with v415.
I tried it and this problem also appeared. They said that dropping down to V414 would not cause this problem.
I don't know if the latest version has a fix?
I have not tried this firmware again and am currently using lineageos19.1
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

Pixel Experience Plus v415.1 is also reported not to work on MediaTek devices. v414 is the latest working version.

chileangarbage said:
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
chileangarbage said:
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
This tutorial works. But not ABSOLUTELY. I did get stucked on bootloader ever after flashing 3 different images. I think that problem was caused because versions of bootloader in my original ROM and installed GSI image didn't match(I was trying to flash latest Android version but my original ROM was Android 11). So I tried flashing the GSI image with Android version 11 and that worked. Therefore, I wanna say that just don't worry just keep flashing and you'll see the Love One.

Question Phone starts only in Fastboot

Hello dear forum
Just got a huge problem, after installing twrp, i wanted to update from Miui13 to Miui14.
it chopped everything up a bit. But then finally done with a message, see attachment.
Since then I can no longer do a normal restart, the phone just hangs in fastboot mode.
Tested a fastboot boot twrp.img, no success.
Does anyone have advice for me?

Which TWRP(full name)?

this one
twrp-3.7.0_11-0-star.img​

i test now a recovery flash with Mi Flash Pro, i thing is the one solution.

Are you sure of the version of your device, Star and not Venus?
Anyway you used a TWRP A11 while the system is A12.
try flashing the correct TWRP A12 again.
star/
Recovery for Xiaomi devices - Browse /star at SourceForge.net
List of relevant recovery in one place
sourceforge.net
venus/
Recovery for Xiaomi devices - Browse /venus at SourceForge.net
List of relevant recovery in one place
sourceforge.net
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP
If the TWRP flash works:
TWRP/wipe format data type yes reboot TWRP.
Sideload or use OTG for flashing the rom.
If nothing works use Miflash.
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com

bjnass said:
i test now a recovery flash with Mi Flash Pro, i thing is the one solution.
Click to expand...
Click to collapse
Not a official tool.

that should be official
only works if you log in with the Xiamoi account.
But pimps with all Roms

by the Mi 11 Ultra write -> star

bjnass said:
that should be official
only works if you log in with the Xiamoi account.
But pimps with all Roms
Click to expand...
Click to collapse
Miflash does not require Xiaomi account only MiUnlock.

But it was like that, maybe the Pro version.
now currently I come to the Chinese Recovery 5.0
What is the best thing for me to do?

bjnass said:
by the Mi 11 Ultra write -> star
Click to expand...
Click to collapse
Useful details :Mi 11 venus/Mi 11 ultra Star.

bjnass said:
But it was like that, maybe the Pro version.
now currently I come to the Chinese Recovery 5.0
What is the best thing for me to do?
Click to expand...
Click to collapse
If that didn't work use Mi Flash (dont relock the bootloader).
Phone starts only in Fastboot
Hello dear forum Just got a huge problem, after installing twrp, i wanted to update from Miui13 to Miui14. it chopped everything up a bit. But then finally done with a message, see attachment. Since then I can no longer do a normal restart...
forum.xda-developers.com

now the phone has reset itself
So install everything again from the beginning, hope it works directly with Miui 14.
Which twrp should I take A12 Or A13?

bjnass said:
now the phone has reset itself
So install everything again from the beginning, hope it works directly with Miui 14.
Which twrp should I take A12 Or A13?
Click to expand...
Click to collapse
If the system is A12 Miui 13, TWRP A12.
If the system is A13 Miui 14,TWRP A13.
Why didn't you flash MIUI 14 with Miflash?

Yes i test it but dont work.
when i take the xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13 rom mi Flash say
-> couldn't find flash script.
and on the server dont have more Miui14 Rom with fastboot script include

bjnass said:
Yes i test it but dont work.
when i take the xiaomi.eu_multi_MI11Pro_MI11Ultra_V14.0.6.0.TKACNXM_v14-13 rom mi Flash say
-> couldn't find flash script.
and on the server dont have more Miui14 Rom with fastboot script include
Click to expand...
Click to collapse
TGZ files not ZIP.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Package Name: star_global_images_V14.0.1.0.TKAMIXM_20230210.0000.00_13.0_global_3abbe1c73e.tgz​
Version CN
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com

This is the gobal image ??

i like the EU Rom

bjnass said:
This is the gobal image ??
Click to expand...
Click to collapse
Yep, and below the CN version.

bjnass said:
i like the EU Rom
Click to expand...
Click to collapse
Xiaomi EU rom is a custom rom not a stock.