Database Develop

[GUIDE][GSI] Flashing GSI's with TWRP Fixes and Workarounds

Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators

Screenshots of Havoc OS gsi running on my zte axon 10:

Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor

That all is great news.....bravooo

Any issues with the havoc gsi?

blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken

noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.

Bliss 12.7 Android 10 gsi on a2020u.

rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"

Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.

i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?

honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what

Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.

cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details

ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work

In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.

[Guide] [GSI] Install Lineage OS 17.x [Q] Redmi 7A

WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Tested with MIUI version 10.2.5.0 Global.
Bootloader must be unlocked (https://en.miui.com/unlock/)
1. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
2. Rename patched boot to boot.img. Rename recovery file to recovery.img. Place boot.img, recovery.img, vbmeta.img in ADB folder.
3. Enable USB-debugging in developer options on your phone.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. On your PC open command prompt and nagivate to ADB folder.
6. Enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe Dalvik / ART cache, System, Data, Cache. Format Data > Yes
Do not wipe Internal Storage!
9. Unpack the downloaded GSI Rom and move it to your phone.
10. Flash the Rom (Install image).
11. Reboot to Recovery.
12. Move files Magisk, Permissiver, FM-Radio fix, GApps to your phone.
13. Flash Magisk (optional)
14. Flash Permissiver
15. Flash GApps (optional).
If you get 'insufficient space' error, first resize System partition.
16. Flash FM-Radio fix:
In TWRP, Mount System. Then flash fix.
17. Reboot system and enjoy.
-----------------------
Downloads:
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
GSI Rom:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
You need to get a64_bvN version from folder lineage-17.x.
Patched boot img file:
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Check your MIUI version in System, so that you download the correct boot img file.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
https://androidfilehost.com/?fid=6006931924117940902
GApps (choose 'ARM' & '10.0')
https://opengapps.org/
FM Radio fix:
https://androidfilehost.com/?fid=8889791610682885147

After installing Gsi
After installing Gsi, can I get the fast boot mode later

Ts40 said:
After installing Gsi, can I get the fast boot mode later
Click to expand...
Click to collapse
Yes, you can still get into fastboot mode.

TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?

Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?

kra_ppo said:
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
Click to expand...
Click to collapse
i would recommend you to flash MIUI global first, because if somethings goes wrong you can't say whats the reason for the error.
and the encrypted folders can be deleted in twrp by format data -->yes

raijinlee said:
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Click to expand...
Click to collapse
thats the one i'm using and never had problems with this, so yes

Question How I can root realme 8 5g

I submitted on ( in deep tool ) still application approved
Can I open bootloader now ?
I need rom for my device and all file to root it

V ( RMX3241_11_A.15 )

do you still want to root smartphone?

Please don't root , useless as no custom ROM is available or you might brick your device

I have rooted my smartphone, on realme 8 5G

Rzk09 said:
I have rooted my smartphone, on realme 8 5G
Click to expand...
Click to collapse
Hello, can you tell me how you got root access, thanks

frenon76 said:
Hello, can you tell me how you got root access, thanks
Click to expand...
Click to collapse
has your device been unlocked bootloader?

Not yet, I'm working on it

frenon76 said:
Not yet, I'm working on it
Click to expand...
Click to collapse
what version of the firmware build is on your device?

RMX3241VF_11_A_23

frenon76 said:
RMX3241VF_11_A_23
Click to expand...
Click to collapse
Global or India?

Global

frenon76 said:
Global
Click to expand...
Click to collapse
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you

Muchas gracias, voy a intentar

Rzk09 said:
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Click to expand...
Click to collapse
HELP, I did this on my phone (realme 8 5g global) and now the system does not turn on as something is recovery (TWRP) and fastboot works normally
this is my main and the only relatively new phone so please help
PS sorry for mistakes, I'm from Poland and I'm writing through a translator

Rzk09 said:
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Click to expand...
Click to collapse
bro please i need your help i'am on A24 Global version version do u have boot.img of this version if not please give me link of A23 global version full rom thank u

mantap, how to downgrade into RMX3241VF_11_A_23? ada no wa or youtube or ig?.. thank u, terima kasih

Rzk09 said:
I have rooted my smartphone, on realme 8 5G
Click to expand...
Click to collapse
Vbmat.img and boot.img for RMX3241_11_A.16 please

Rzk09 said:
if you have unlocked your device, follow these steps
1.donwload boot.img and vbmeta.img, if your firmware version is A.23 global version you can download it in Attachments
2. Patch the boot.img that you downloaded earlier in the magisk manager, when it's finished you can change the name to "boot.img" to make it easier to patch
3. Copy the boot.img patch to your laptop/PC in "adb and fastboot" folder, together with vbmeta.img (don't patch the vbmeta.img file in magisk manager)
4. turn on usb debugging option
5. enter fastboot mode (turn off your device and hold vol up and power)
6. if you have entered fastboot, plug your devices into your laptop/pc and type in adb "fastboot devices" (make sure your devices are connected)
7. And now start patching the boot.img file that you patched earlier and disable boot verification (vbmeta.img)
8. Ok,Patch the boot.img file with the command "fastboot flash boot boot.img"
9. and finally disable vbmeta copy this command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
10. and restart your device
I hope this can help you
Click to expand...
Click to collapse
Can you send me the attachments for RMX3241_11_C.04 this android version?

Rooted Realme 8 5G to fix unknown IMEI but in the end I know that unknown baseband is the major problem, and no custom ROM for RMX3241.
Stock firmware: RMX3241_11_A.26
Magisk 25.2
Root Tool: MTKClient (GitHub) with Brom/Edl Mode since I got no fastboot
For MTKClient, you'll need to install "MediaTek CDC driver 1.0.8" and manually add legacy hardware in device manager "MediaTek USB PORT" and other thing that you need in the github link.
Root method just same as fastboot method, patch your boot.img with Magisk app and flash patched boot.img + vbmeta.img or using MTKClient flash the patched boot.img and vbmeta.img.empty included in MTKClient.
Where to get your stock boot.img vbmeta.img? Use MTKClient or MTKMETAUTILITY to dump it from your phone. Dump the whole img except userdata to backup just incase....
If somehow the root fail after like 1h bootloop at logo, just reflash with stock boot vbmeta. So keep in mind to backup your stock img file.
I also have TWRP as recovery flashed using MTKClient but no custom ROM?

Trouble installing Magisk on the November Android update

Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.

Curiouser and curiouser: this works
adb reboot bootloader
fastboot boot redfin-2111_boot_magisk_patched.img

gone_bush said:
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Click to expand...
Click to collapse
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.

xunholyx said:
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
Click to expand...
Click to collapse
Thank you for your reply. Some questions:
1) What's changed that required a wipe? (Let's face it, it's a MAJOR PITA! Thankfully, I do use TitaniumBackup )
2) You state "download both the ota.zip and the factory image" - what's the difference?
3) Re "Pull the vbmeta.img" - in the current instance, is that from the November file (SP1A.211105.004), if not, from where?
4) Do I have this right for future updates?
* Unpack the downloaded file and put the boot.img and vbmeta.img files in a safe place
* Sideload the update by
adb reboot recovery
Apply update from ADB
adb sideload <ota-update.zip>
* Use volume buttons to boot into bootloader (booting into system will mean I'll have to do another wipe!)
* fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
* flash patched boot.img
* boot
5) Re using Magisk to patch the boot.img: can, say, the November boot.img be patched whilst the phone is running the October update?
Yeah, I know, answering my questions is all you've got to do with your life

1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)

xunholyx said:
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
Click to expand...
Click to collapse
Thank you for yor replies and time - much appreciated!

How To Guide HOW TO INSTALL PIXEL EXPERIENCE GSI ON POCO M4 PRO 5G GLOBAL (EVERGREEN)

Disclaimer, I am not responsible for any damages that the flashing my cause to your beloved phones.
THINGS YOU NEED BEFORE FLASHING
- unlocked bootloader
- a pc ofc you need adb installed
-YOU NEED TO BE AT MIUI 13.0.2 OR ELSE PE 12.1 WONT BOOT! PLEASE DOWNGRADE!
-Download the gsi here :
https://github.com/ponces/treble_build_pe/releases/download/v414-plus/PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img.xz
unzip till you get the .img file and rename it to system.img then move it on your adb platform tools folder
- a fully functional cable and brain.
FLASHING STEPS:
-Turn your phone off
-Boot your phone in fastboot mode
- Connect it on your PC
-Run cmd inside the adb platform tools folder
-Type "fastboot devices" and see if it detects your phone if yes then type fastboot reboot fastboot and you'll see that your phone is on fastbootd mode.
- Type fastboot erase system
Then
- fastboot flash system system.img
- fastboot reboot fastboot
- fastboot -w ( if this doesn't work then try the next one)
-fastboot format userdata ( if this doesn't work then proceed to the next one )
-fastboot erase userdata
-to be sure type fastboot reboot recovery then wipe the data there
-reboot and enjoy the gsi
NOTE:
-If the scrolling is lag , go to phh treble settings and disable hw overlay
-if you're having bluetooth issues then go to phh treble settings and force disable a2dp.
It is a solid GSI and I have been using it for 2 weeks now and no issue.

Something went wrong and now fastboot erase system returns "FAILED (remote: 'partition doesn't exist')" and I can not find anybody to help x.x What do I do?

Do you got bugs on statics?
My battery usage and data usage not working