Database Info

[RECOVERY] LineageOS 17.1 Recovery [X3][2020/08/24]

Introduction
This is a LineageOS Recovery compiled from the source tree of LineageOS 17.1 for Realme X3/X3 Superzoom.
Instructions (Installing Recovery):
1. Download recovery.img & vbmeta.img
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Flash vbmeta
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
4. Flash recovery
Code:
fastboot flash recovery recovery.img
5. Run
Code:
fastboot reboot recovery
to enter LineageOS Recovery
Instructions (Installing Magisk):
You have to use the official Magisk, version 20.4 or later. Installing an older Magisk may make the system unbootable.
1. Download Magisk >= 20.4, put onto computer
2. Reboot to LineageOS recovery, select `Mount /system` (you may see some errors, but they can be safely ignored)
3. Select `Apply update from ADB`
4. Run
Code:
adb sideload Magisk-xxx.zip
5. You will see a signature verification error, select `Yes` to bypass the check
6. Reboot to system to enjoy your Magisk installation.
Notes:
- Since it's not TWRP, you cannot decrypt your /data in recovery for now, which means no data backup or recovery, and you cannot install on-device flashable zips through this recovery.
- Since it's not TWRP, it cannot prevent your OS from overwriting recovery automatically. If you use official ROM, you may need to manually re-flash the recovery every time. I'm not sure whether this can be bypassed with some Magisk module.
- You need to always click "Mount /system" before flashing any mods into the system (i.e. Magisk, OpenGapps, etc., ROMs themselves are not affected), otherwise they will fail to install. (Clicking the option does not actually mount /system; it just sets up necessary mappings from the super partition to each of the dynamic partitions so that the installation scripts will work)
Download:
https://sourceforge.net/projects/siddharthbharadwaj-s-builds/files/Realme X3/LOS Recovery/
Source Code:
Kernel: Used stock prebuilt one.

Thank you! This is now my preferred method to root Lineage that I haven't seen anywhere else.

[MAGISK][ROOT][BOOT.IMG] How to patch the Oneplus 8, 8T and 8 Pro stock Boot Image (boot.img) from the currently installed Stock ROM

Quick and concise how to for obtaining a Stock Boot Image from your Oneplus 8, 8T or 8 Pro device and patching with Magisk to create a fastboot flashable patched boot.img.
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked, broken or dead devices. This is a high-level
* how to for users with a basic knowledge of ADB and Fastboot. YOU alone are
* choosing to make these modifications, and you are solely responsible for your
* device's fit for use and wellbeing.
*
* Backup your data!
*
*/
PREREQUISITS:
An unpatched Stock Boot.img running on your device
General knowledge and understanding of ADB and Fastboot
Download latest op8, op8p, or op8t Horizon Kernel img from [e.g., op8p_7.img]:
https://dl.akr-developers.com/?dir=oneplus/horizon_kernel/R/images
Download latest Magisk Canary build from Github [e.g., app-debug.apk]:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
DEVICE/PC OPERATIONS:
→ ADB
Enumerate devices
Code:
adb devices
Boot into Fastboot
Code:
reboot bootloader
→ FASTBOOT
Enumerate devices
Code:
fastboot devices
Determine the current slot (A/B), whichever slot you're on should be the "good" img
Code:
fastboot getvar current-slot
Boot with the custom kernel downloaded from Horizon to use root [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot boot "C:\Users\User\Downloads\op8p_R7.img"​
Code:
fastboot boot xxxxxxx.img
→ ADB
Copy the boot.img from each slot to the root of the device
Code:
adb shell
su
dd if=/dev/block/sde11 of=/sdcard/boot_a.img
dd if=/dev/block/sde35 of=/sdcard/boot_b.img
→ Android Device [NOTE: Some Android 11 devices experience patching issues on the Beta Channel like bootloop] [NOTE: Some users experience issues on Canary like no SIM detected; if so switch to Beta]
Install Magisk app-debug.apk (Canary)
Go to Settings → Update Channel → Canary
Go to Home → Install → Install → Select and Patch A File
Navigate to internal storage and select the stock boot.img [choose the img from whichever slot you're on]
When it’s done patching copy the file, named magisk_patched.img, from the root → Downloads of your device to PC
→ ADB
Code:
reboot bootloader
→ FASTBOOT
Test to ensure it boots before flashing; if not you'll need to patch the other img
Code:
fastboot boot magisk_patched.img
→ Android Device
If the device boots and you have root in the Magisk Manager app, reboot the device into Fastboot then flash the active slot [NOTE: Both slots do not need to be flashed; just the current active slot]
→ FASTBOOT
Flash the patched image file [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot flash boot_b "C:\Users\User\Downloads\magisk_patched.img"
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
- OR -​
Code:
fastboot flash boot_a magisk_patched.img
fastboot reboot
- OR -​
Code:
fastboot flash boot_b magisk_patched.img
fastboot reboot
ADDITIONAL RESOURSES:
→ FASTBOOT
If you need to set the other slot to be the active slot use:
Code:
fastboot --set-active=a
- OR -​
Code:
fastboot --set-active=b
→ ADB
ADB Magisk Bootloop Fix
Code:
adb shell
magisk --remove-modules
→ OTA Help
Magisk stock boot.img missing fix [NOTE: Android 11 onwards, the /sbin folder might not exist, so Magisk will randomly create a folder under /dev and use it as the base folder]
Rename to: stock_boot_0.img
Compress with gzip = stock_boot_0.img.gz
Copy stock_boot_0.img.gz file to the root of: /data
Edit the config file: /dev/xxxxxxx/.magisk/config → Change SHA1= to 0
Magisk Manager → Uninstall Magisk → Restore Images
→ ADB
Determine the random folder name generated by Magisk on Android 11+
Code:
ls -laR /dev | grep '.magisk/rootdir'
→ ADB
Determine the Boot Image partition location [NOTE: Will list all partitions; look for boot_a and boot_b]
Code:
ls /dev/block/bootdevice/by-name/ -all

Tried some other way on android 11 but failed, so back to android 10.
maybe i won't get android 11 until TWRP is work.
can't easily backup data without root is very annoying, thanks for the work!

I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?

mrram said:
I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?
Click to expand...
Click to collapse
Guessing here, but have a second look at these two commands:
Code:
fastboot boot magisk_patched.img
△ This will NOT flash the rooted image, it will only boot up once so you can test it or use it for temporary root
verses
Code:
fastboot flash boot magisk_patched.img
▲ This will flash the rooted image and is used after you've tested the patched image to be sure it doesn't bootloop and to have persistent root

If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.

MagikGab said:
If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.
Click to expand...
Click to collapse
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.

CarvedArt said:
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.
Click to expand...
Click to collapse
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root

MagikGab said:
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root
Click to expand...
Click to collapse
Just follow the steps above -- that'll get you a stock kernel (your current kernel) patched with Magisk and permanently rooted. The above process is only using the Horizon kernel to boot your device with root so that you can extract your kernel and patch it. The final result will be as stock as you can get with root.

Hey everyone. OP8 Pro user here. Just took OTA going from 11.0.9.9 running Magisk Canary 23 to the newest 11.0.10.10. I restored images before taking the OTA and reinstalled magisk to the other slot like I always do to retain root. Ive now lost root and am trying to boot the last two versions of the Horizon kernel. Ive tried the two latest ones (r9.2 and r9.2.1 from February 2021) and while they do boot my phone, I cant get SU access to extract the stock images.
Anything else that anyone things I should try? All i want from Christmas is root.

Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.

Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"

tosho1 said:
Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"
Click to expand...
Click to collapse
Magisk → Settings (Gear icon) → Systemless hosts ← Click it

tosho1 said:
Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.
Click to expand...
Click to collapse
LineageOS is not the stock ROM so it's slightly different and not covered in this thread.

Thank you, CarvedArt. I wasn't aware of this.

Does anyone have the latest stable Android 13 patched boot image for the IN2015 that they can share with me ?

Guide to Install GApps and Magisk on Custom ROMs for Nokia 7.2

While I was trying to install GApps for Lineage OS 18.1 on my Nokia 7.2, I always lost my wi-fi. This is apparently due to flashing TWRP as boot image, which replaces the stock boot messing with wi-fi as the boot image has thee kernel.
Although, I did figure it out, it took me three days to get a proper solution from multiple sources. Here, I will explain how to install Lineage OS 18.1 on Nokia 7.2 with Gapps and Magisk. This can be applied to other ROMs as well. I am assuming you are on stock firmware.
Requirements:
Any custom ROM without GApps
vbmeta file
vendor image
Gapps zip file of your choice
platform-tools
twrp image
magisk file
payload dumper tool
Preperation:
The wifi stops working because we change the boot image. To prevent this, we must flash the boot image of the rom after we are done with our work with TWRP
For this, we ,ust get the boot image for the ROM. As this is not available readily, we must extract it from the ROM zip
Install latest python on your pc
Get the payload dumper tool from the link given below. Extract the contents into the root directory of python. It should be in C:\Users\USER-NAME\AppData\Local\Programs\Python\Python <version number>
Extract the ROM zip into any folder. Copy the payload.bin file and paste it in the folder where you put the payload dumper tool
Open a command prompt in the python root folder and type
Code:
python -m pip install -r requirements.txt
Then type
Code:
python payload_dumper.py payload.bin
After it finishes, go to the folder named Output inside the python folder. Here there will be a file named boot.bin. Rename this as lineage_boot.bin and paste it into the platform tools folder
Installation:
Download the twrp image, rename it to twrp.img and place it in the platform-tools folder. Connect your phone to the computer, switch on usb debugging on your phone.
Open command shell in the platform-tools folder and type
Code:
adb reboot bootloader
. In the bootloader, type
Code:
fastboot flash boot_b twrp.img
.
Next, type
Code:
fastboot --set-active=b
and then reboot to recovery using volume buttons and selecting using power button
In TWRP swipe to allow modifications. Copy your ROM and vendor image files to your SD Card. Now, click wipe, format data and type yes. Go back to home screen and the press install. Select your ROM file and install it. Sometimes it is required to flash vendor image. In that case flash that too. This step is required for Lineage OS 18.1
Now on the twrp home screen, tap on reboot. At the bottom, the current slot should be B. Tap slot A. THis changes the active slot to A. Now go back and tap on bootloader, this should boot you to the bootloader.
Take your vbmeta.img file and place it in the platform tools folder. Now, while in the bootloader mode, type,
Code:
fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Next type
Code:
fastboot flash boot_a twrp.img
and boot to recovery using volume buttons
Now, press install in TWRP and select install and install the GApps file and reboot to bootloader
Next, in the bootloader type
Code:
fastboot flash boot_a lineage_boot.img
. Now start your phone. You should have lineage os with GApps
Installing Magisk:
Copy the lineage_boot.img into your phone. Download magisk.apk file from the link given below
Install the magisk app and open it. If it asks for additional setup select no. Beside the magisk option select install. Under options, if Recovery Mode is selected, deselect it and click next.
Now click on Select and patch a file under method. Select the lineage_boot.img
The patched image will be saved in downloads folder. Rename this file to lineage_magisk.img and copy it to the platform tools folder on your computer. Reboot your phone to bootloader mode
On your computer in the command window opened in the platform tools folder, type,
Code:
fastboot flash boot lineage_magisk.img
Reboot and you will have a rooted lineage os with GApps
Files:
Lineage OS 18.1 and vbmeta.img
TWRP
vendor
NikGApps
Payload Dumper tool
platform tools
Magisk
Guides that I Followed:
Extracting boot.img from ROM zip
Installing magisk using patched boot image
Credits:
Raghu varma for Lineage OS 18.1 port and twrp
Providers of the guides mentioned above

Hi @Ujwal2000 thanks for the guide.
I am using the stock android 10 rom and magisk patch method.
This also leads to non working wifi and magisk does not recognize that its installed.
Which steps of your guide apply to the stock rom?
i do not need gapps nor twrp I guess I only wanted to root the stock rom with magisk.

For stock, use this guide. They maintain a repository if patched boot images
Guide - How to root the Nokia 7.2 and Nokia 6.2 using Magisk
Nokia 7.2 and Nokia 6.2 come with an unlockable bootloader. The thing that compliments unlocked bootloader best is root access. So, this guide will help you in rooting the Nokia 7.2 or Nokia 6.2. You have a choice between Magisk patched boot images and TWRP recovery. I’d recommend going the...
www.techmesto.com

@Ujwal2000 , can you please look at my posting here? Thank you.

after fallowing the steps(except installing lineageOS with twrp flash everything was encrypted even tough i have the bootloader unlocked, managed to install it via adb sideload) the wifi doesnt work at all. When i try to turn it on is switches off on its own. Do anyone know a fix?

i had problem with latest version of python (3.10), version 3.7 was working for me

[HOW-TO] Install LineageOS 18.1 on the Google Pixel 3a XL (bonito) w/ Google Apps and Magisk (root)

I've been trying to find a good phone for my wife that is officially supported by LineageOS and settled on the Pixel 3a. If you're thinking of purchasing this device, make sure the listing says that it has an UNLOCKED BOOTLOADER. Just "unlocked" doesn't cut it, you'll probably get a phone that works on any carrier but won't allow an OEM unlock. Third time is the charm, we finally ordered from eBay; the listing said unlocked bootloader, and it was.
I had some trouble getting started so hopefully this will help others. This guide will probably work on the Google Pixel 3a (sargo, not XL), and possibly other Pixel devices as well assuming you adjust your release version appropriate to your model.
Note that TWRP doesn't work well (or at all), and don't even try because the Pixel 3 and newer are slot A/B devices so LineageOS uses their own recovery to manage switching between boot slot A/B during update. (Of course, if you do get TWRP working, then I do prefer it so let me know how!)
Enable developer mode
OEM Unlock: method 1, method 2
Unlock the bootloader:
adb reboot bootloader
fastboot flashing unlock
Install the latest android platform tools for fastboot and adb:
https://developer.android.com/studio/releases/platform-tools
Install the official Android 11:
https://developers.google.com/android/images?authuser=3#bonito
Agree to terms and conditions
Download the latest v11 zip (RQ3A.211001.001, Oct 2021)
Unzip and run:
Windows: flash-all.bat
Linux: ./flash-all.sh
Repeat #3 above if necessary
Download and transfer LineageOS 18.1:
https://download.lineageos.org/bonito
Download the latest recovery .img to your desk
Download the latest .zip to your desk
Install the recovery image:
fastboot flash boot_a lineage-18.1-20211023-recovery-bonito.img
fastboot flash boot_b lineage-18.1-20211023-recovery-bonito.img # (might not need this one)
Reboot to recovery (may need to power off first)
From the Phone: In recovery it should show the LineageOS icon:
Advanced->Enable ADB (may not be necessary)
Apply Update
Apply from ADB
From your desk:
adb sideload lineage-18.1-20211023-nightly-bonito-signed.zip
If you get errors like error: protocol fault (no status) then your version of adb is too old.
It should say Total xfer: 1.00x but the official LineageOS installation docs say that it might hang at 47% and that is ok because it is done transferring to the phone at that point.
From your phone:
If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
If so, then tap Apply Update->Apply from ADB and follow Google Apps .zip install notes below in #7.3
If not, then tap the left return arrow and then tap "reboot now"
Optional ZIPs:
If you are already in recovery, go to step #7.2. Otherwise, get into recovery. If you already booted into LineageOS, then I find it easiest to reboot into recovery by enabling "Advanced Restart" :
Systems->Advanced->Gestures->Power->Advanced restart
Then hold down the power button and select Power->Reboot->Recovery
To install zips:
First mount /mnt/system: Adbanced->Mount/Unmount System
This is necessary because the Pixel is a A/B boot slot device and not all .zip's will know how to mount.
Use adb sideload <filename.zip> as in #6.4 above (but with the .zip you want!)
You may be prompted on your phone to install even though the signature is untrusted.
Download the latest Google Apps for arm64. (Do this before booting LineageOS for the first time!)
Most people recommend MindTheGapps,however:
Because the Pixel is a A/B boot slot device, MindTheGapps doesn't know how to mount /mnt/system so it fails.
This is probably a bug in MindTheGapps, if you find a way to fix it let me know.
Others like OpenGApps.
I installed this one, but for some reason it didn't work the first time. It did the second! Maybe I missed something.
Well Play Store is hanging, so trying MindThe Gapps
Root your device with Magisk:
Download the latest Magisk APK:
Note that the .apk is also a .zip, so rename it if you must (but I didn't need to).
Enable adb
Install the apk:
adb install Magisk-v23.0.apk
Troubleshooting:
LineageOS recovery doesn't like to install multiple zips at once. If you get the error adb: sideload connection failed: closed then click the left back arrow, then again folow steps from 6.4
Try factory reset if you have boot issues the first time

In Step 5, sub-step 3 you typed "Download the latest v11 zip (SP1A.210812.015, Oct 2021)". The latest Android 11 image for bonito is "RQ3A.211001.001, Oct 2021". The image you reference is the new Android 12 image for bonito.

Thanks for catching my copy-paste bug! I've updated the article.

[ROM] [GSI] [AOSP] [10] [A041C] [PhhTreble] CUBOT NOTE 7

Before doing any of this, I am not responsible of any bricked devices, carefully read everything I written before doing anything. I wish you the best luck . You do it once and you will know how to do it every other time.
Spoiler: Minor bug
Keep in mind with this GSI the home screen (custom too) and quick settings will be choppier than on stock firmware on idle (when I charge up the battery it is less noticeable), this can be less annoying by disabling all animations in developer options.
Spoiler: Magisk
Magisk with TWRP
If you want to flash magisk you need TWRP and only place to download it i unofficialtwrp for the phone (be careful what you do while flashing it and DO NOT FLASH orange-Red-state-disabler because your phone will not boot after you flash it and reboot) and when you have it installed you download magisk apk, rename magisk.apk to magisk.zip, put it on an SD card because internal storage is encrypted and flash. If you get issues you will need to download V12 Firmware and reflash all of it using SP Flash tool, but when I did it the phone generated a new IMEI??? I fixed that using MAUI Meta and the IMEI was working after that so when I flashed modded magisk boot img from V12 firmware it all worked.
Magisk with official app
If you want to flash Magisk using magisk app and you are on latest firmware V15 you can’t do it by using Magisk app because every link to the V15 firmware is dead (but if you are on V12 you are lucky because the link for it is alive ) but you do get a working SuperUser app in the GSI if that’s enough. If you want Magisk, your boot img needs to match the firmware or stuff like WIFI will not work because the kernel does not match the rest of the firmware. That means you need to use the SP Flash Tool to completely reflash the whole firmware, but when I did it the phone generated a new IMEI??? I fixed that using MAUI Meta and the IMEI was working after that so when I flashed modded magisk boot img from V12 firmware it all worked.
-----------------
Spoiler: Known issues
Known issues:
So far none besides what I mentioned in minor bug.
-----------------
Spoiler: Things needed
Things needed:
Computer running Windows XP or newer
Phone itself booted into Android and a USB cable
ADB and Fastboot driver with Platform-Tools (there is a tutorial on my youtube channel how to use it)
ZIP file attached below
Phh Terble GSI (only these builds worked for me):
Full gappps
GO Gapps
AOSP Vanilla
If you want to use anything but Phh Treble you need to find an Android 10 arm32 binder64 ab image.
Time and Patience.
------------------------
Spoiler: Preparation
Preparation:
In phone settings, go to about phone and last thing which says "Build Number" tap it 7 times to unlock developer options, go back and go to System, Advanced and developer options.
In developer options, scroll down to "USB Debugging" and toggle it.
Plug the phone into the computer, and on the computer go to platform-tools folder and in the toolbar (thing which shows the path to folder) type cmd.exe.
in command prompt, type in adb devices, and the phone should have a popup asking to allow this computer, check the "Always allow from this computer" option and tap OK.
When you have ADB and Fastboot and Platform-Tools on your computer download the ZIP attached below, open it and copy all the files from it into your platform-tools folder, than download the GSI, open it, copy the img file in the same platform-tools folder and rename it to system.img if you want for convinience.
---------------------
Spoiler: Procedure
Procedure:
In CMD type:
Code:
fastboot reboot bootloader
Now type these commands seperately
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Code:
fastboot reboot fastboot
Computer will say <Waiting for device> and when the phone boots into fastbootd computer will detect it
Now type in:
Code:
fastboot flash product product_gsi.img
Code:
fastboot flash system system.img
Code:
fastboot –w
Code:
fastboot reboot
If there is a wrong resolution boot screen and the phone boots congratulations your phone is now running a GSI

Delete

Smedslund said:
Delete
Click to expand...
Click to collapse
cant delete myself from what i seen so i reported myself and will get deleted at one point, i moved to here
*REMOVED LINK*
and let me know if I made the same mistake
EDIT: The thread has been moved to the right place by itself and the repost had been deleted. I am glad this is over.