Database Develop

Installing OEM GSIs on Jasmine (A2)

I think, that im not the only one who is facing problems installing the Erfan OEM GSIs on our Mi A2
Ive tried OOS and it wont get to the Oneplus Bootanimation
Same with the other GSIs
Instuctions i used are:
1.Install stock Boot.img and stock Vendor.img
2. install the OOS AB GSI as System image
3. install permissiver2 ZIP
But it wont Boot
If there is anybody who got it working please reply to this topic since there is no real Installation process for our device

I follow this post
https://www.xda-developers.com/install-android-q-beta-gsi-project-treble/
No problem during installation but when it finished, it only reboot to recovery,.. Nothing more

Aziziamran said:
I follow this post
https://www.xda-developers.com/install-android-q-beta-gsi-project-treble/
No problem during installation but when it finished, it only reboot to recovery,.. Nothing more
Click to expand...
Click to collapse
So for you IT wont Work too

StarSix01 said:
So for you IT wont Work too
Click to expand...
Click to collapse
I get it to working and booted fire, trust me you don't need , too much bugs and soft reboot every 5 mins,,

fir1996 said:
I get it to working and booted fire, trust me you don't need , too much bugs and soft reboot every 5 mins,,
Click to expand...
Click to collapse
How you got IT working im Just curious

StarSix01 said:
How you got IT working im Just curious
Click to expand...
Click to collapse
Pls don't even try it, i flashed it over lineage 16 vendor then factory reset using fastboot -w,, then flash permissiver.zip , that's it,
Very buggy experience, camera not working, google play crashing , device soft reboot every 5 mins, phone calls through speaker only,,

fir1996 said:
Pls don't even try it, i flashed it over lineage 16 vendor then factory reset using fastboot -w,, then flash permissiver.zip , that's it,
Very buggy experience, camera not working, google play crashing , device soft reboot every 5 mins, phone calls through speaker only,,
Click to expand...
Click to collapse
Sounds bad tho.. By the way, did you notice any new changes compared to pie?

fir1996 said:
Pls don't even try it, i flashed it over lineage 16 vendor then factory reset using fastboot -w,, then flash permissiver.zip , that's it,
Very buggy experience, camera not working, google play crashing , device soft reboot every 5 mins, phone calls through speaker only,,
Click to expand...
Click to collapse
Which lineage 16 you used?

StarSix01 said:
Which lineage 16 you used?
Click to expand...
Click to collapse
The one here on xda,

fir1996 said:
The one here on xda,
Click to expand...
Click to collapse
Is IT the only working vendor ?

StarSix01 said:
Is IT the only working vendor ?
Click to expand...
Click to collapse
Yeah, but dude trust me don't try it, it's super buggy

I successfully installed Oxygen OS OEM GSI on the Mi A2 and it's running late flawlessly
Only bugs that I noticed are:
Fingerprint not working and faceunlock not working
Brightness is a bit ****ed up, but usable

StarSix01 said:
I successfully installed Oxygen OS OEM GSI on the Mi A2 and it's running late flawlessly
Only bugs that I noticed are:
Fingerprint not working and faceunlock not working
Brightness is a bit ****ed up, but usable
Click to expand...
Click to collapse
Now we are waiting for tutorial

Ir works well, Google play crashing you can resolve updating Google play services with apk.

0. I would recommend To Format Data completely and copy the files from your PC to the Phone then
1. Flash boot.img as boot img and vendor.img as vendor.img in TWRP
2. Flash the OxygenOS ABGSI as System Img
3. wipe Data
4. Flash FBE Disabler
5. Flash permissiver2 (don't know if this is nessesary but it did it)
6. Flash the Latest Hex Kernel by Draco
7. Flash Magisk
8. Reboot
And don't forget to wipe cache and dalvik always

StarSix01 said:
0. I would recommend To Format Data completely and copy the files from your PC to the Phone then
1. Flash boot.img as boot img and vendor.img as vendor.img in TWRP
2. Flash the OxygenOS ABGSI as System Img
3. wipe Data
4. Flash FBE Disabler
5. Flash permissiver2 (don't know if this is nessesary but it did it)
6. Flash the Latest Hex Kernel by Draco
7. Flash Magisk
8. Reboot
And don't forget to wipe cache and dalvik always
Click to expand...
Click to collapse
I used Dec update vendor.img and boot.img

Any fix for fingerprint issue?

which stock rom did you tried ? i dont remember but 10.0.2.0 or 9.6.16.0 i manage to boot coloros, miui and nubia. also i installed force encyrpt disable but i dont think it is necessary

q0kHaN said:
which stock rom did you tried ? i dont remember but 10.0.2.0 or 9.6.16.0 i manage to boot coloros, miui and nubia. also i installed force encyrpt disable but i dont think it is necessary
Click to expand...
Click to collapse
latest

Divyam2201 said:
Any fix for fingerprint issue?
Click to expand...
Click to collapse
its not working?

[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

[SHARE] [10] [gsi] android 10 aosp gsi - phh-treble gsi

We successfully booted the Android 10 AOSP GSI by phhusson. Got it flashed using fastboot.
Test in Realme C3/Narzo 10A. (RMX2020/RMX2027)
Steps to flash:
I am not responsible for your loss
Note (all your data will get erased back it up if you are not lazy )
1. unlock bootloader
2. enable usb debugging
3. adb reboot fastboot
4. fastboot reboot fastboot
5. fastboot --disable-verification flash vbmeta vbmeta.img
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot -w
9. fastboot reboot bootloader
10. fastboot erase usrdata
11. fastboot reboot
Not Working:
VOLTE
VOWIFI
Some Fixes For GSI
For this fixes to run you should have adb running on you pc and have your devices connected via adb
>adb shell
>su
Brightness_Fix:
setprop persist.sys.qcom-brightness 2047
Headphone_Jack_Fix:
setprop persist.sys.overlay.devinputjack true
Google Play Service Fix
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Download Link:
https://github.com/phhusson/treble_experimentations/releases
Flash on the ARM64 ab build
Android version: 10
Build Author: https://forum.xda-developers.com/member.php?u=1915408
{Mod edit}
Special thanks to @phhusson, Google and all other developers.
Thanks to Okta Viano to test the GSI in his device.

@sarthakroy2002
We only grant developers the privilege to provide a link to their social media in the OP of their own development threads. These conditions obviously don't apply to you or your thread. Reference to Telegram has been removed.
Additionally, I've moved the thread from the development to the "Guides etc." section. Please refer to here.

Bluetooth calling issue in Samsung Galaxy M30S with GSI ROM PixelExperience
Hi, I have flashed my Samsung Galaxy M30S with PixelExperience-10.0-20200328-GSI-ARM64-AB ROM, Everything is working fine except Bluetooth calling, Bluetooth music is working but unable to receive/connect calls via bluetooth.
Can someone help ?

back it up if ur not lazy. lmao that so funny ???

This rom fix gyroscope delay in Pubg???

Sarathi4936 said:
This rom fix gyroscope delay in Pubg???
Click to expand...
Click to collapse
noo

sarthakroy2002 said:
noo
Click to expand...
Click to collapse
You can fix it??

Sarathi4936 said:
You can fix it??
Click to expand...
Click to collapse
No one can fix indeed...lmao

Anything else not working?

Any Experience?
How's this GSI so far?
Battery performance any review ?

Are there any ROMs with notch support, or is there a way to adjust the status bar margins? I'm tempted to flash this on my RMX2020.

Need Help through this !!!!!!!!!!!!!
Facing an error ____ System partitioned doesn't exist (got an error at very beginning of the process )!!!! while Gsi flashing on Realme 7 RMX2151(MTK G95) , seeking help here & there.

...Saurav said:
View attachment 5234329
Need Help through this !!!!!!!!!!!!!
Facing an error ____ System partitioned doesn't exist (got an error at very beginning of the process )!!!! while Gsi flashing on Realme 7 RMX2151(MTK G95) , seeking help here & there.
Click to expand...
Click to collapse
sorry previous one was my fault (was skipping a line of command ) but now I"m facing is that my device is booting into fastboot mode but got stucked on recovery(stock) page & on cmd its shows waiting for device .(previously tried on CUstom PBRP recovery same result that's why this time tried with stock recovery but same can't boot Dynamic Fastboot.

Need testers for egis fp in gsi with realme ui 2 base

rabim94 said:
Need testers for egis fp in gsi with realme ui 2 base
Click to expand...
Click to collapse
Confirmed working in realme UI 2 base. Need testers for UI 1 base

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.

[GSI] Pixel Experience 13.0 for A71 4G and TWRP ( Newbie flashing guide )

What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Please note that: this will void your warranty.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BUGS
-Finger Print sensor NOT working
-Sim 2 Slot NOT working
-Notifications may be delayed
That's all i know, let me know if you find any more bugs.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do you need to flash?
1. Must have an unlocked bootloader and have some custom romming knowledge.
2. Download the TWRP, VBMETA and boot.img, should be down in the thread.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How do I flash?
Put your phone in download mode and open odin, there you will click on AP and put your TWRP, after that put your VBMETA Disabler in the USERDATA slot.
After your done flashing the TWRP, shut off your device and hold POWER and VOLUME UP untill you boot into the TWRP.
Once you're in, go to wipe-format data-type yes.
Flash the boot.img ( IMPORTANT )
Flash the MultiDisabler
And now flash the GSI, I will be using the Pixel Experience 13.0 GSI https://github.com/ponces/treble_build_pe/releases ( BIG THANKS TO PONCES ON GITHUB FOR MAKING IT <3 )
After you're done flashing the GSI, reboot and you should be done.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CREDITS!
https://forum.xda-developers.com/t/...-android-12-gaming-rom.4515187/#post-87812539 ( from here i got the twrp, multidisabler and boot.img )
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/ ( from here i got the VBMETA Disabler )
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FIRST TIME MAKING A POST! SO PLEASE TELL ME WHAT I CAN DO TO IMPROVE! <33

IF YOU BRICK YOUR DEVICE I WILL ACTUALLY TRY TO HELP YOU UNBRICK IT NO MATTER WHAT!

honestly, I'm not flashing Android 13 on my device so does it work on android 12 or 11 vendors?
No android 13 GSI boots on this a71 for me.
Also FOD will most likely NOT work since PHH had backed away from gsi development, so it's trebledroid based most likely, which will have more bugs and less stable overall.
Also I can't flash Faizauthar's kernel on A13 anymore.

S8hype said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Please note that: this will void your warranty.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BUGS
-Finger Print sensor NOT working
That's all i know, let me know if you find any more bugs.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do you need to flash?
1. Must have an unlocked bootloader and have some custom romming knowledge.
2. Download the TWRP, VBMETA and boot.img, should be down in the thread.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How do I flash?
Put your phone in download mode and open odin, there you will click on AP and put your TWRP, after that put your VBMETA Disabler in the USERDATA slot.
After your done flashing the TWRP, shut off your device and hold POWER and VOLUME UP untill you boot into the TWRP.
Once you're in, go to wipe-format data-type yes.
Flash the boot.img ( IMPORTANT )
Flash the MultiDisabler
And now flash the GSI, I will be using the Pixel Experience 13.0 GSI https://github.com/ponces/treble_build_pe/releases ( BIG THANKS TO PONCES ON GITHUB FOR MAKING IT <3 )
After you're done flashing the GSI, reboot and you should be done.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CREDITS!
https://forum.xda-developers.com/t/...-android-12-gaming-rom.4515187/#post-87812539 ( from here i got the twrp, multidisabler and boot.img )
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/ ( from here i got the VBMETA Disabler )
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FIRST TIME MAKING A POST! SO PLEASE TELL ME WHAT I CAN DO TO IMPROVE! <33
Click to expand...
Click to collapse
Also, what is the source of your boot.img file?

TigerLake said:
honestly, I'm not flashing Android 13 on my device so does it work on android 12 or 11 vendors?
No android 13 GSI boots on this a71 for me.
Also FOD will most likely NOT work since PHH had backed away from gsi development, so it's trebledroid based most likely, which will have more bugs and less stable overall.
Also I can't flash Faizauthar's kernel on A13 anymore.
Click to expand...
Click to collapse
Actually, I tried PE 13 on Android 12 vendor and it worked fine except for :- sim2 and fingerprint.
Which is quite common in GSI...
Edit :- also faced delayed notifications, which I still face even in samsung android 13 original firmware

S8hype said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Please note that: this will void your warranty.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BUGS
-Finger Print sensor NOT working
That's all i know, let me know if you find any more bugs.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do you need to flash?
1. Must have an unlocked bootloader and have some custom romming knowledge.
2. Download the TWRP, VBMETA and boot.img, should be down in the thread.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How do I flash?
Put your phone in download mode and open odin, there you will click on AP and put your TWRP, after that put your VBMETA Disabler in the USERDATA slot.
After your done flashing the TWRP, shut off your device and hold POWER and VOLUME UP untill you boot into the TWRP.
Once you're in, go to wipe-format data-type yes.
Flash the boot.img ( IMPORTANT )
Flash the MultiDisabler
And now flash the GSI, I will be using the Pixel Experience 13.0 GSI https://github.com/ponces/treble_build_pe/releases ( BIG THANKS TO PONCES ON GITHUB FOR MAKING IT <3 )
After you're done flashing the GSI, reboot and you should be done.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CREDITS!
https://forum.xda-developers.com/t/...-android-12-gaming-rom.4515187/#post-87812539 ( from here i got the twrp, multidisabler and boot.img )
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/ ( from here i got the VBMETA Disabler )
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FIRST TIME MAKING A POST! SO PLEASE TELL ME WHAT I CAN DO TO IMPROVE! <33
Click to expand...
Click to collapse
TigerLake said:
honestly, I'm not flashing Android 13 on my device so does it work on android 12 or 11 vendors?
No android 13 GSI boots on this a71 for me.
Also FOD will most likely NOT work since PHH had backed away from gsi development, so it's trebledroid based most likely, which will have more bugs and less stable overall.
Also I can't flash Faizauthar's kernel on A13
TigerLake said:
honestly, I'm not flashing Android 13 on my device so does it work on android 12 or 11 vendors?
No android 13 GSI boots on this a71 for me.
Also FOD will most likely NOT work since PHH had backed away from gsi development, so it's trebledroid based most likely, which will have more bugs and less stable overall.
Also I can't flash Faizauthar's kernel on A13 anymore.
Click to expand...
Click to collapse
i think it will work!
Click to expand...
Click to collapse

TigerLake said:
Also, what is the source of your boot.img file?
Click to expand...
Click to collapse
i got the boot.img from this thread https://forum.xda-developers.com/t/...-android-12-gaming-rom.4515187/#post-87812539

SolitaryRockzy said:
Actually, I tried PE 13 on Android 12 vendor and it worked fine except for :- sim2 and fingerprint.
Which is quite common in GSI...
Edit :- also faced delayed notifications, which I still face even in samsung android 13 original firmware
Click to expand...
Click to collapse
thanks for telling me! i will add these bugs to the bug section

S8hype said:
i got the boot.img from this thread https://forum.xda-developers.com/t/...-android-12-gaming-rom.4515187/#post-87812539
Click to expand...
Click to collapse
oh lol, thats the stock boot.img, the only boot.img with at least some compatibility with gsis. Others just boot to fastboot....

SolitaryRockzy said:
Actually, I tried PE 13 on Android 12 vendor and it worked fine except for :- sim2 and fingerprint.
Which is quite common in GSI...
Edit :- also faced delayed notifications, which I still face even in samsung android 13 original firmware
Click to expand...
Click to collapse
early adopter tax.
A13 is still very buggy on this phone, so I don't really recommend it. Will port A13 roms when things get a little more stable....
SIM2 works on A12
Plus the brightness bug on gsis with Android 12 vendor, this is why I am still clinging to A11 vendor (bit sv rev 8, downgraded from Android 13 vendor). Samsung just makes things worse and worse...

TigerLake said:
early adopter tax.
A13 is still very buggy on this phone, so I don't really recommend it. Will port A13 roms when things get a little more stable....
SIM2 works on A12
Plus the brightness bug on gsis with Android 12 vendor, this is why I am still clinging to A11 vendor (bit sv rev 8, downgraded from Android 13 vendor). Samsung just makes things worse and worse...
Click to expand...
Click to collapse
Does Sim 2 work on GSIs for you? I was unable to hear or speak on calls using Sim 2 when I was using PE12

found some bugs a71
So i cant find a signal neither on sim 1 nor sim 2 and the top speaker doesnt work thats it for now but other than that it does work... thanks for this tutorial
Edit: I can call and receive calls but it still doesnt show a signal

The latest build of PE 13 has plus version in it. And the FOD is working now.

I'll try the latest one

S8hype said:
IF YOU BRICK YOUR DEVICE I WILL ACTUALLY TRY TO HELP YOU UNBRICK IT NO MATTER WHAT!
Click to expand...
Click to collapse
Can I flash it over One UI 5.0? Or do I need to downgrade stock firmware first?

Bro need some help
I installed it on my a71 but seems that the brightness of the device is broken, how can I fix it?

Also as I tested the Bluetooth isn't working, even I try to enable it in Phh Treble Settings, btw the brightness is fixed by opening Phh Treble Settings, but the Bluetooth problem have been make me a tons of problems, like I can't really use my Bluetooth headphones, please some expert can help me

S8hype said:
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Please note that: this will void your warranty.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BUGS
-Finger Print sensor NOT working
-Sim 2 Slot NOT working
-Notifications may be delayed
That's all i know, let me know if you find any more bugs.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do you need to flash?
1. Must have an unlocked bootloader and have some custom romming knowledge.
2. Download the TWRP, VBMETA and boot.img, should be down in the thread.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How do I flash?
Put your phone in download mode and open odin, there you will click on AP and put your TWRP, after that put your VBMETA Disabler in the USERDATA slot.
After your done flashing the TWRP, shut off your device and hold POWER and VOLUME UP untill you boot into the TWRP.
Once you're in, go to wipe-format data-type yes.
Flash the boot.img ( IMPORTANT )
Flash the MultiDisabler
And now flash the GSI, I will be using the Pixel Experience 13.0 GSI https://github.com/ponces/treble_build_pe/releases ( BIG THANKS TO PONCES ON GITHUB FOR MAKING IT <3 )
After you're done flashing the GSI, reboot and you should be done.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CREDITS!
https://forum.xda-developers.com/t/...-android-12-gaming-rom.4515187/#post-87812539 ( from here i got the twrp, multidisabler and boot.img )
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/ ( from here i got the VBMETA Disabler )
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FIRST TIME MAKING A POST! SO PLEASE TELL ME WHAT I CAN DO TO IMPROVE! <33
Click to expand...
Click to collapse
In all GSI if you go in phh treble setting - misc - under display fp color and select white the fingerprint work

Vastiano2 said:
In all GSI if you go in phh treble setting - misc - under display fp color and select white the fingerprint work
Click to expand...
Click to collapse
Thank you so much now it works, thanks for helping me but I got another question is how about Bluetooth?

Hello S8Hype! Well I Installed The Rom on my A71 but there are no display drivers (it always less bright on the screen) The AP On The Phone Is A715FXXU8DVK3. If There's A way to fix this reply!