UPDATE: I kept finding bugs in josh1x's rom, so i installed the LOS17 GSI instead. Guide for that outline in reply #11
Figured this out and thought i'd write a simple tutorial that covers stock (i was at 20e) to lineage. You'll need the LG USB Drivers and adb/fastboot. There are a couple other things to download through out the tutorial and the unlock tutorial in step 1.
LG USB Drivers 4.2.0
ADB/Fastboot
LGUP with partition DL
Note: I was able to reach download mode and fastboot at any point in this process and even when it went wrong (kernel crashes, boot loops etc) while figuring out this tutorial. I found that i could just hold vol down or up in a bootloop with the usb connected to get to the mode i wanted.
Typical combos:
-Download mode: power off phone with usb disconnected. hold vol up and plug in cable
--NOTE: after wiping laf_a and boot_b, you must switch to slot b to access download mode (run command: fastboot -ab)
-fastboot: power off phone with usb disconnected, hold vol down and plug in cable. or adb reboot bootloader
--NOTE: after wiping laf_a and boot_b, you can only access fastboot from slot a by holding vol up on boot (for 20e/21d, on 11g vol down still works).
-Recovery: power off. hold power and vol down, when you see the white LG G7 logo temporarily release just the power button. Continue to hold power and vol down till you get to the option menu. Select Yes three times.
Guide:
1. Follow the universal unlock method here.
1.5. You need to zero out laf_a and boot_b before flashing 21d/20e to maintain fastboot access. Use adb to run the following commands
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
1.75. Enable usb debugging (should already be done). Open LGUP and connect to your phone. dont close it. If you open it after booting to DL mode it wont recognize it
2. 21d ULM firmware (here) must be flashed to use the latest twrp (20e works as well). The 11g twrp cannot install lineageos. I would imagine the EU firmware could be flashed as well, but I used ULM.
Code:
Boot into fastboot
fastboot -ab
Boot into download mode
Use the lg up linked in this post to flash 20e/21d without laf_a and boot_b with partition dl mode
3. Format userdata to decrpyt your file system so TWRP can access it. Then flash TWRP; boot_twrp-june.img can be found here. It's from Josh1x's post here. Note: this TWRP is non persistant.
Code:
Boot to bootloader
fastboot format userdata
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Select restart in fastboot
Boot to recovery
4. Obtain the latest lineage build here. This is from Josh1x's post here. I attempted to flash gapps at this point and it failed, see the next steps.
Code:
Wipe everything
Transfer lineageos to your phone and install it
Restart normally
5. Gapps
Code:
Reboot to bootloader
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Reboot to recovery
Transfer opengapps 9.0 to your phone and install.
Reboot to bootloader
6. We need to flash the stock lineage boot image (here) again now that we are done. The file was obtained with this method
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Restart normally
if you have magisk, it would be magisk_patched_boot.img (here). this one was made from the above image with magisk on my phone.
Code:
fastboot flash boot_a magisk_patched_boot.img
fastboot flash boot_b magisk_patched_boot.img
Restart normally
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
I am so glad to be off of stock, enjoy guys and girls!
Bugs (from my ULM phone)
-flash doesnt work in the camera. also probably why gcam crashes (gcam works on an EM phone somehow)
-brightness slider is calibrated incorrectly compared to stock. way too bright when set to 0%
NOTE: using ULM vendor fixed the flash and brightness, but gcam still doesnt work. This would make it the most functional rom for this phone at this point (vibrate does work).
Being that since day1 of g710pm/ulm could be boot unlocked, all ypu had to do is flash the eu firmware and go to lineage frlm there due to twrp incompatibility.
I have not tested it, but does being on lineage based off EU blobs, do you still get full LTE and/or volte.
If sprint users have switched to eu/lineage do you have full lte/ril compatibility.
Ah crap I didn't know that. I tried unlocking through LG when I got it a couple months ago and that didn't work of course. At that time the phone was working well (not going on a background apps killing spree), so I didn't bother. I couldn't find anything on here at the time for unlocking, but I obviously missed that.
LTE and wifi are working fine. Maybe that has something to do with me never flashing the EU rom to install lineage? Anyways, I couldn't find a volte toggle, but I'd assume it is working. I'm on Verizon and I believe they are killing their cdma network, so I'll find out.
Would this work on sprint phones? There is a warning at the end of the unlocking guide about sprint phones loosing fastboot when upgrading to ulm pie.
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Emanel000000 said:
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Click to expand...
Click to collapse
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Have you tried the other twrps?
sirbow2 said:
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Click to expand...
Click to collapse
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk)
Click to expand...
Click to collapse
oh yea. i see, yes, they might as they are from the lineage rom.
Emanel000000 said:
... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
sirbow2 said:
oh yea. i see, yes, they might as they are from the lineage rom.
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
Click to expand...
Click to collapse
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
Emanel000000 said:
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Click to expand...
Click to collapse
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Edit: Update 2: dont use the vendor in this post. I patched the ULM vendor, but vibrate and gcam are still an issue with a GSI. links here: https://forum.xda-developers.com/showpost.php?p=81563763&postcount=41 Also, using the ulm vendor on Josh1x's rom fixed everything but gcam.
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
sirbow2 said:
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Click to expand...
Click to collapse
i just had 20c for em it doesnt matter the version
sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Thanks. You're process got my audio working on GSI. Not sure what incorrect image I was installing or what the issue was.
Just need to disable the LED notification and get vibration working.
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
thats what i was kind of thinking the issue was. thats over my head though.
sirbow2 said:
thats what i was kind of thinking the issue was. thats over my head though.
Click to expand...
Click to collapse
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
loonycgb2 said:
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
Click to expand...
Click to collapse
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
sirbow2 said:
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
Click to expand...
Click to collapse
Once you got twrp running with stock then do the normal thing of format userdat to decrypt it then flash the no dmverity zip mentioned in the thread or magisk then backup vendor via twrp or dd...
That will give you a usable vendor for lineage and such.
All josh1x or whoever did to the EM vendor was modify fstab to remove the force encrypt so that way decrypted roms would work.
sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Nevermind
I tried using the vendor from ULM 20e and it doesnt work, i even tried flashing dm verity right after. How would one modify the vendor partition anyways?
Hi, so I have a Blackview A60 which I adore for the price, fantastic!
Looking to get custom recovery to get Magisk up and running.
I've flashed a 3.1.1 twrp (apparently for Blackview A60 Pro) which caused a bootloop
I had to stock rom it via fastboot.
It's working, however I've tried a few Twrp version via fastboot boot <img's>
Any help in trying to get one to function? Cheers.
Android 9.0
Edit: I got Magisk working with a back up patched boot.img, didn't think to try flashing it since it was a patch of the boot.img before I updated. I'm a dope.
You need to flash vbmeta with --disable-verity --disable-verification, that fixed my bootloop and my twrp worked.
Hi,
Could you please let me know which recovery and vbmeta files you used?
Thanks in advance.
Hi all,
Quick follow-up to my question, and hopefully some help for others.
I did NOT flash TWRP because I wanted to used an Android 10 GSI roms (and TWRP doesn't support, yet, Android 10). However I did flash a custom Android 10 ROM.
Here is what I did :
* Activate bootloader OEM unlock from boot ;
* Reboot phone to fastboot, then "fastboot flashing unlock" ;
* Get vbmeta file from here : https://developer.android.com/topic/generic-system-image/releases ;
* Flash it : "fastboot --disable-verification flash vbmeta vbmeta.img" ;
* Then erase system : "fastboot erase system" ;
* Flash your desired rom : "fastboot flash system your_desired_iso.img" ;
* Wipe user data : "fastboot -w"
* Reboot : "fastboot reboot" and voilà !
Source, mainly DuckDuckGo searches + https://source.android.com/setup/build/gsi#flashing-gsis
Nesousx said:
Hi all,
Quick follow-up to my question, and hopefully some help for others.
I did NOT flash TWRP because I wanted to used an Android 10 GSI roms (and TWRP doesn't support, yet, Android 10). However I did flash a custom Android 10 ROM.
Here is what I did :
* Activate bootloader OEM unlock from boot ;
* Reboot phone to fastboot, then "fastboot flashing unlock" ;
* Get vbmeta file from here : https://developer.android.com/topic/generic-system-image/releases ;
* Flash it : "fastboot --disable-verification flash vbmeta vbmeta.img" ;
* Then erase system : "fastboot erase system" ;
* Flash your desired rom : "fastboot flash system your_desired_iso.img" ;
* Wipe user data : "fastboot -w"
* Reboot : "fastboot reboot" and voilà !
Source, mainly DuckDuckGo searches + https://source.android.com/setup/build/gsi#flashing-gsis
Click to expand...
Click to collapse
Thank you for the details.
Can you tell me of the Blackview A60 Pro works OK with GSI (phhusson). I am interested in general browsing, whatsapp, basic -camera. (no games).
EtoileLabrie said:
Thank you for the details.
Can you tell me of the Blackview A60 Pro works OK with GSI (phhusson). I am interested in general browsing, whatsapp, basic -camera. (no games).
Click to expand...
Click to collapse
Hi,
I think it does, but don't remember. I tried many roms, but then returned the phone to Amazon. I did not really like it for everyday use.
thank you for the reply. I am wondering to buy but it is very heavy!
Hello,
How can i boot up custom ROM Android (LineageOS) ?
Do i need to have change something inside boot.img / or something command?
Note:
Phone (Umidigi Power)
Android 9
Unlocked bootloader,
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
What i want is:
1. I want a Custom OS like (LineageOS)
2. Install another ROM or fix the stock ROM
What i found out.
1. After flash a system i got bootloop, see umdiigi power boot logo and reboot
2. Stock ROM / deos not work anymore before i get black screen
3. use alot of commands and nothing working
4. try to install system from TWRP but bootloop
Questions is (I think):
How i can fix it or install custom OS
Can you help me?
Thanks for your time
007fred62 said:
Hello,
How can i boot up custom ROM Android ?
Do i need to have change something inside boot.img?
Note:
Phone (Umidigi Power)
Android 9
Unlocked bootloader,
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.im
Can you help me?
Thanks for your time
Click to expand...
Click to collapse
look up for Project Treble this are custom rom that only require you to flash system.img
The Fastboot command mentioned only prepares phone to allow modifications of Android system, e.g. for installing a Custom ROM. A Custom ROM gets flashed via a Custom Recovery you flashed before.
ineedroot69 said:
look up for Project Treble this are custom rom that only require you to flash system.img
Click to expand...
Click to collapse
there to download it?
jwoegerbauer said:
The Fastboot command mentioned only prepares phone to allow modifications of Android system, e.g. for installing a Custom ROM. A Custom ROM gets flashed via a Custom Recovery you flashed before.
Click to expand...
Click to collapse
I have try this command:
fastboot --disable-verity --disable-verification flash system system.img
still not boot up after this command
007fred62 said:
I have try this command:
fastboot --disable-verity --disable-verification flash system system.img
still not boot up after this command
Click to expand...
Click to collapse
As I can see you didn't get it.
what? you want custom recovery like TWRP or custom rom like LineageOS?
also we can barely understand you.. please write in full sentence don't type fragment phrases
ineedroot69 said:
what?you want custom recovery like TWRP or custom rom like LineageOS?
Click to expand...
Click to collapse
Sorry for my Questions. updated post 1.
i trying to find another custom OS or fix the system.
Yes like LineageOS
Would anyone be able to direct me or send me the proper information on how to root my OnePlus 9 global LE2115? Because their are to many threads and Im getting confused
You can either use boot.img or you can boot into twrp and flash magisk.apk. 2 options for A11
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
xLLALLOx said:
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
Click to expand...
Click to collapse
A12 root method is different. Not like A11 where you flash the patched boot.img,it won't work. VBmeta and a vendor.img is used also. Also, TWRP is for A11. If you want root,Use the tool here: https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/
Use option 5 and then 6 and reboot. Magisk will be installed. Click the magisk app and update it.
Note: use your phone to download and extract file with password that OP provides in the link
In a moment of weakness, I finally allowed my G Stylus to update to Android 12, and my stability has been a nightmare since then. I have been reading through many guides here and elsewhere to getting a GSI installed.
So far, I have unlocked the bootloader and followed the instructions for installing TWRP using adb/fastboot for my device. When try to flash a GSI, the partitions in TWRP don't look like anything I've seen in guides. The options it shows me are:
-Boot
-Dtbo
-Persist
-Super (system system_ext product vendor)
-Install Recovery Ramdisk
I tried installing on Super, as I found a thread mentioning it should contain both vendor and system. However, when I flash the img for a gsi to it, it will only boot to bootoader. I can get it into TWRP recovery but the screen is entirely unresponsive, even attempting to power off prompt's a restart. I was able to use Moto's Rescue program to get it back in working order, but each time this happens I have to start over at square one.
I tried with a GSI for crDroid on my first attempt, and then LineageOS on a follow-up attempt, both I had the same issue.
I'm new to Android modding, so I could really use some guidance through getting this set up. I've extensively referenced guides on here and elsewhere, but I've struggled with parsing and figuring out what I need to do in this case. Currently my device has TWRP installed but I'll be doing nothing else until I know what the best way forward is. I'd be happy to provide additional info.
Edit: Just found the dedicated 5G section. Sorry about this.
I am not sure why people use TWRP and a GSI/crDroid /w LineageOS rom.
All you need to do is install the magisk module L Speed
Remember this phone has 2 boot partitions....1 is secured (even if you have the bootloader unlocked and your rooted) So if you trip the SafetyNet your going to have bootloading issues and boot loops
Not sure what the previous comment was about, what does safetynet have to do with anything? It fails the second you unlock the bootloader.
First, you'll want to make sure to have installed at least one OTA update so both your slots are occupied. You could also install copy-partitions from a custom recovery. Otherwise your phone might brick if it ever switches to slot b.
Download and extract the official firmware for your device that matches what is installed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
And reflash your vbmeta partition(s) from fastboot to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_system.img
Then you need to reboot into fastbootd (you can also get into it from a custom recovery)
Code:
fastboot reboot fastboot
From there you can erase your system, install the GSI, wipe data, and reboot
Code:
fastboot erase system
fastboot flash system GSI_system.img
fastboot -w
fastboot reboot