General GSIs on OP10Pro - OnePlus 10 Pro

With an unlocked BL, flash an ARM64 AB GSI within fastbootd, format userdata from recovery, reboot, profit. vbmeta should only be needed if you do Magisk.
Google GSIs simply boot; PHH-based ones (which are ones people will actually want to use) don't boot just yet, but was just fixed thanks to @phhusson (see here), and will be in GSIs updated afterwards.

Hi ! Did you try the GSI ?Could you tell us what is not working at the moment ?
I'm hesitating on trying to flash one

AndyYan said:
With an unlocked BL, flash an ARM64 AB GSI within fastbootd, format userdata from recovery, reboot, profit. vbmeta should only be needed if you do Magisk.
Google GSIs simply boot; PHH-based ones (which are ones people will actually want to use) don't boot just yet, but was just fixed thanks to @phhusson (see here), and will be in GSIs updated afterwards.
Click to expand...
Click to collapse
Maybe move to development or how to guild thread and post links and how to flash etc

toolhas4degrees said:
Maybe move to development or how to guild thread and post links and how to flash etc
Click to expand...
Click to collapse
For how immature GSIs are (e.g. no FP, spotty or no VoLTE, tricky resolution switching), I think it's fine to let this get less exposure. Being a "proper" OnePlus device, pretty sure it'll get device-specific ROMs eventually.

Related

[GUIDE] Flash Treble ROMs on OP7 Pro

Hey folks, after some digging I found a method how to flash Treble ROMs on our OP7 Pros!
I've only achieved this by following many great guides here on xda so credits go to: @Exelios and @demkantor for their threads which you can find here respectively:
https://forum.xda-developers.com/oneplus-6/how-to/treble-mistery-solved-developer-t3800716
https://forum.xda-developers.com/showthread.php?t=2277112
Prerequisites:
Make sure all drivers for your device have already been installed. Otherwise plug in your phone to your PC and wait for all drivers to finish installing
Latest fastboot - minimal packages won't work, so follow the guide from the second link above
Stock boot.img and vbmeta.img which you can get from stock fastboot ROMs found here: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Inside these zips there's another zip called images.zip in which you can find required imgs for your particular device
Treble ROM of your choice (arm64 a/b)
Steps:
Copy all sensitive data from your phone as this process will wipe your phone entirely!
This includes: photos, songs, and any other files!
Put all needed files in one folder
Run cmd
Type: cd <your folders directory>
Reboot your phone in fastboot mode (hold power+vol up+vol down for a few seconds)
and connect it to your PC
Then type:
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
After that:
Code:
fastboot -w flash system <your Treble ROMs name>.img
Using just the inactive partition and OxygenOS on another didn't seem to work for me.
This is the point at which your data will be erased so make sure again you have all your files
And finally:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This is required. If you want to go to stock either flash it again without
Code:
--disable-verity --disable-verification
or use aforementioned stock fastboot ROM package
Now reboot and wait for the phone to boot
Success!
If you got a bootloop or something just didn't go right you will have to repeat all of the steps
Now you can flash patched boot image to get root or try any of the fixes found here
Bugs:
60Hz
Fingerprint sensor
After using front camera it's stuck - it won't slide back inside the phone
Only 3G data connection
Wi-Fi signal seems to be quite weak
No Warp Charge
Credits:
@Exelios
@demkantor
@mauronofrio
I got 90Hz working on my FlokoROM GSI with this dirty hack:
https://github.com/AndroPlus-org/an...mmit/724725063f12dfa7b95b43d97114149831f748b0
dtbo.img for 9.5.4 (flash it by fastboot flash dtbo dtbo.img, don't know if it work on other version)
https://drive.google.com/open?id=1X7W9iyKVy7gmkBjCSght7gy_Sbl4t3Iz
It replaces default 60Hz config with 90Hz one lol
For Warp charge, we need to place "dashd" to somewhere in system and run it:
https://github.com/FlokoROM-GSI/device_phh_treble/commit/1ef10fa131d6e350a2cd00fd25c10b621cbb1d5f
dashd should be added to device_phh_treble, but currently I added it with Magisk Module.
https://drive.google.com/open?id=11eD8CqJmdblfYlLXuiHMIhkxweTD9hzD
AndroPlus said:
I got 90Hz working on my FlokoROM GSI with this dirty hack:
https://github.com/AndroPlus-org/an...mmit/724725063f12dfa7b95b43d97114149831f748b0
dtbo.img for 9.5.4 (flash it by fastboot flash dtbo dtbo.img, don't know if it work on other version)
https://drive.google.com/open?id=1X7W9iyKVy7gmkBjCSght7gy_Sbl4t3Iz
It replaces default 60Hz config with 90Hz one lol
For Warp charge, we need to place "dashd" to somewhere in system and run it:
https://github.com/FlokoROM-GSI/device_phh_treble/commit/1ef10fa131d6e350a2cd00fd25c10b621cbb1d5f
dashd should be added to device_phh_treble, but currently I added it with Magisk Module.
https://drive.google.com/open?id=11eD8CqJmdblfYlLXuiHMIhkxweTD9hzD
Click to expand...
Click to collapse
Very cool! I'm not as tech savvy so could I point to your post in the main one for additional fixes?
maxtreme said:
Very cool! I'm not as tech savvy so could I point to your post in the main one for additional fixes?
Click to expand...
Click to collapse
OK
Legend! I managed to get havoc up and running. There is a OOS camera magisk port in the op6 forum I used and updated the camera to current one plus version and its working well. Front can doesn't work as you know.
Most things are working fine for me at the moment. No real issues yet
Camera quality is poor, but I'm not that fussed by it at the moment. Just want to play!
Thanks heaps for the guide.
---------- Post added at 09:54 AM ---------- Previous post was at 09:54 AM ----------
AndroPlus said:
I got 90Hz working on my FlokoROM GSI with this dirty hack:
https://github.com/AndroPlus-org/an...mmit/724725063f12dfa7b95b43d97114149831f748b0
dtbo.img for 9.5.4 (flash it by fastboot flash dtbo dtbo.img, don't know if it work on other version)
https://drive.google.com/open?id=1X7W9iyKVy7gmkBjCSght7gy_Sbl4t3Iz
It replaces default 60Hz config with 90Hz one lol
For Warp charge, we need to place "dashd" to somewhere in system and run it:
https://github.com/FlokoROM-GSI/device_phh_treble/commit/1ef10fa131d6e350a2cd00fd25c10b621cbb1d5f
dashd should be added to device_phh_treble, but currently I added it with Magisk Module.
https://drive.google.com/open?id=11eD8CqJmdblfYlLXuiHMIhkxweTD9hzD
Click to expand...
Click to collapse
Will floko be updated with the op7 stuff you fix?
miffymiffy said:
Legend! I managed to get havoc up and running. There is a OOS camera magisk port in the op6 forum I used and updated the camera to current one plus version and its working well. Front can doesn't work as you know.
Most things are working fine for me at the moment. No real issues yet
Camera quality is poor, but I'm not that fussed by it at the moment. Just want to play!
Thanks heaps for the guide.
---------- Post added at 09:54 AM ---------- Previous post was at 09:54 AM ----------
Will floko be updated with the op7 stuff you fix?
Click to expand...
Click to collapse
I'll add it at the weekend (with June security patch)
Great walkthrough! Two questions, any way to flash treble ROMs in twrp for us? and how do you think we could get erfanoabdi's android q gsi that's ported from the pixel to work on the device?
eqbirvin said:
Great walkthrough! Two questions, any way to flash treble ROMs in twrp for us? and how do you think we could get erfanoabdi's android q gsi that's ported from the pixel to work on the device?
Click to expand...
Click to collapse
+1 to this.
What are treble ROMs and how does this benefit my use?... Is it different from a custom ROM?
i have tried every gs rom by erfan for this non eof them work all stuck at boot logo
maybe permissive issue which has to be flashed in A partion rom
eqbirvin said:
Great walkthrough! Two questions, any way to flash treble ROMs in twrp for us? and how do you think we could get erfanoabdi's android q gsi that's ported from the pixel to work on the device?
Click to expand...
Click to collapse
mlock420 said:
What are treble ROMs and how does this benefit my use?... Is it different from a custom ROM?
Click to expand...
Click to collapse
Treble ROMs can be used on any project treble supported phone
Treble roms? Do you mean gsi's?
lichtblitz said:
Treble roms? Do you mean gsi's?
Click to expand...
Click to collapse
Exactly that is
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
mlock420 said:
What are treble ROMs and how does this benefit my use?... Is it different from a custom ROM?
Click to expand...
Click to collapse
It's a custom ROM, but the thing is you can flash it on literally any device with Project Treble support
Someone succeded to flash q6 gsi?
I tried the guide on the op but its stuck on the bootscreen like forever :\
@maxtreme
Kookitza said:
Someone succeded to flash q6 gsi?
I tried the guide on the op but its stuck on the bootscreen like forever :\
@maxtreme
Click to expand...
Click to collapse
Tried it before as well and no success. Q beta uses different kernel or sth so it won't work
maxtreme said:
Tried it before as well and no success. Q beta uses different kernel or sth so it won't work
Click to expand...
Click to collapse
Do you think that when open beta will release by OnePlus, the gsi should work on our device?
Kookitza said:
Do you think that when open beta will release by OnePlus, the gsi should work on our device?
Click to expand...
Click to collapse
I guess so
Maybe try using vbmeta and boot from the Q beta released by OP
Anyone able to get gsi working on 9.5.11?
I cant get havoc to work and wondering if that may be why
I'm not sure why you would bother flashing things like Havoc treble rom when the official Havoc rom is available for OP7 pro?
I tried flashing many gsi but all stuck at boot animation .. any solution for this?

[Solved] GSI Installation — Finally booted!!!

Hi guys, this is my first time owning a Redmi/Xiaomi with a MediaTek SOC (G80). The device was released with Android 10 so it definitely supports Project Treble. My experience with booting GSIs on Qualcomm Snapdragon devices is straightforward but I attempted the same on the Redmi 9 and I noted the following things:
With no kernel sources released, no stable custom recovery to customize my Redmi 9, I went the GSI route via the standard fastboot commands in the bootloader before I discovered that it uses fastbootd instead to flash the system image. Phew! Also the Redmi 9 (lancelot) is compatible with arm64-ab GSIs.
UPDATE 1: GSI booted. Current custom recoveries cannot be used to flash GSIs on devices launched with Q because the system partition is logical and can only be flashed through fastbootd.
UPDATE 2:First successful boot at post #33. I wanted us to share ideas to make it possible for those interested to boot GSIs.
UPDATE 3: Some screenshots are attached below. Go to the guide for how to install.
nielsync said:
Hi guys, this is my first time owning a Redmi/Xiaomi with a MediaTek SOC (G80). The device was released with Android 10 so it definitely supports Project Treble. My experience with booting GSIs on Qualcomm Snapdragon devices is straightforward but I attempted the same on the Redmi 9 and I encountered the following things:
With no kernel sources released, no stable custom recovery, I went the GSI route via fastboot.
Flashing the vbmeta.img and running fastboot flash system system.img gives an error so i experimented with fastboot flash super system.img which worked without giving any errors. My understanding is the super partition contains more than just the system partition.
Despite successfully flashing the system image as the "super" image, I was unable to boot none of the arm64-ab GSIs I tried which included AOSP 10.0 v222 by @phhusson, Havoc-OS-v3.8 by @SKULSHADY and LineageOS 17.1-20200808 by @AndyYan
Lastly, this device being an MTK is very easy to brick!
Anyone successfully booted? Share your experience here with me.
Click to expand...
Click to collapse
You should not play with your device because this device is MediaTek processor device. I already broke my phone twice and I have to go to service centre my luck was good because I do not have to to pay any money but I learn that I never play with my device
[Update]:
This device launched with Android Q with dynamic partitions within the super partition and a relocated fastboot implementation from bootloader to user space. Theoretically to flash a GSI, boot into fastbootd from the bootloader by running the commands as below [Only proceed if you know what you are doing!!!]:
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
fastboot erase userdata (if this command doesn't work type fastboot reboot bootloader then fastboot erase userdata)
fastboot reboot
As a result of restoring my bricked device after flashing an unstable custom recovery, my bootloader relocked and therefore can't run above commands now to test if they work. I'll try again after 336 hours!
nielsync said:
[Update]:
This device launched with Android Q with dynamic partitions within the super partition and a relocated fastboot implementation from bootloader to user space. Theoretically to flash a GSI, boot into fastbootd from the bootloader by running the commands as below [Only proceed if you know what you are doing!!!]:
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
fastboot erase userdata (if this command doesn't work type fastboot reboot bootloader then fastboot erase userdata)
fastboot reboot
As a result of restoring my bricked device after flashing an unstable custom recovery, my bootloader relocked and therefore can't run above commands now to test if they work. I'll try again after 336 hours!
Click to expand...
Click to collapse
Ok i also wait for you...in my case i get 7 day wait time.....after your waiting time finished you should try as follow
Fastboot earse system
Fastboot flash system system.img.
Fastboot flash vbmeta vbmeta.img(download vbmeta.img from this post..it is important to disable Android verified boot.
You can warp data first or latter this prossess...
But i confused what type gsi should download.
A/b or a only....
I know our device does not support a/b. But it use system as root....
Shas45558 said:
Ok i also wait for you...in my case i get 7 day wait time.....after your waiting time finished you should try as follow
Fastboot earse system
Fastboot flash system system.img.
Fastboot flash vbmeta vbmeta.img(download vbmeta.img from this post..it is important to disable Android verified boot.
You can warp data first or latter this prossess...
But i confused what type gsi should download.
A/b or a only....
I know our device does not support a/b. But it use system as root....
Click to expand...
Click to collapse
The above commands can only run after booting into fastbootd apart from "fastboot flash vbmeta" due to the partitioning of the Redmi 9 and other devices launched with Android 10 that come with a SUPER partition that includes the SYSTEM, VENDOR and PRODUCT images. When you boot into fastbootd your device will be listed as "lancelot" in Device Manager under "other devices". Just make sure you have latest Xiaomi drivers and running fastboot commands via the latest Android Platform Tools. Use arm64 A/B GSIs even though it doesn't support seamless updates. I am still waiting for the bootloader unlock to start enjoying
nielsync said:
The above commands can only run after booting into fastbootd apart from "fastboot flash vbmeta" due to the partitioning of the Redmi 9 and other devices launched with Android 10 that come with a SUPER partition that includes the SYSTEM, VENDOR and PRODUCT images. When you boot into fastbootd your device will be listed as "lancelot" in Device Manager under "other devices". Just make sure you have latest Xiaomi drivers and running fastboot commands via the latest Android Platform Tools. Use arm64 A/B GSIs even though it doesn't support seamless updates. I am still waiting for the bootloader unlock to start enjoying
Click to expand...
Click to collapse
Tnx for great answer...
But why we use a/b gsi image file when our device does not support seamless updated??
Our device has a slot only
Shas45558 said:
Tnx for great answer...
But why we use a/b gsi image file when our device does not support seamless updated??
Our device has a slot only
Click to expand...
Click to collapse
Well I can't give a technical answer but I've come to realize that not all system-as-root devices support A/B partitioning but all A/B devices are definitely system as root! Similarly the Redmi 8a (a64-a/b) and 8 (arm64-a/b) also boot A/B GSIs. I say this after flashing GSIs on both devices in the past before I got the Redmi 9. I'm a Redmi boy :good:
nielsync said:
Well I can't give a technical answer but I've come to realize that not all system-as-root devices support A/B partitioning but all A/B devices are definitely system as root! Similarly the Redmi 8a (a64-a/b) and 8 (arm64-a/b) also boot A/B GSIs. I say this after flashing GSIs on both devices in the past before I got the Redmi 9. I'm a Redmi boy :good:
Click to expand...
Click to collapse
It is very great bro... I already broke my phone two time and I have to go to service centre. I was lucky because they do not take any money from me. When your waiting time is over then you flash gsi rom... And if you successfully boot your device then you you must share the process how you do it... I am very excited To use a gsi rom in my device...with out break it again... Because this time I think if I break my device
Then I have to pay the service centre
You should not flash unofficial TWRP recovery because our redmi 9 source code not published yet so the recovery has some problem and if you flash IT again your device is broke again. So I think fastboot method is safe for us
Shas45558 said:
It is very great bro... I already broke my phone two time and I have to go to service centre. I was lucky because they do not take any money from me. When your waiting time is over then you flash gsi rom... And if you successfully boot your device then you you must share the process how you do it... I am very excited To use a gsi rom in my device...with out break it again... Because this time I think if I break my device
Then I have to pay the service centre
You should not flash unofficial TWRP recovery because our redmi 9 source code not published yet so the recovery has some problem and if you flash IT again your device is broke again. So I think fastboot method is safe for us
Click to expand...
Click to collapse
You are right. Flashing that recovery caused me problems too and that's why my bootloader got locked again after restoring. Before that I tried everything to flash a GSI but could not boot. So I tried installing the GSI via that recovery and kaput
nielsync said:
You are right. Flashing that recovery caused me problems too and that's why my bootloader got locked again after restoring. Before that I tried everything to flash a GSI but could not boot. So I tried installing the GSI via that recovery and kaput
Click to expand...
Click to collapse
That's mean we have to wait when stable recovery made for our device....
It took forever
We may be out of luck with the kernel sources. Last I checked, Xiaomi had also not released sources for the Redmi Note 9 series so at least we are not alone. With no hope for Xiaomi EU ROMS, booting a GSI is now our only hope of customizing our device. The problem is, it has not happened yet. @Shas45558 maybe you will be the hero who boots the GSI
nielsync said:
We may be out of luck with the kernel sources. Last I checked, Xiaomi had also not released sources for the Redmi Note 9 series so at least we are not alone. With no hope for Xiaomi EU ROMS, booting a GSI is now our only hope of customizing our device. The problem is, it has not happened yet. @Shas45558 maybe you will be the hero who boots the GSI
Click to expand...
Click to collapse
Ha ha ha......
Shas45558 said:
Ha ha ha......
Click to expand...
Click to collapse
You are the most active guy in the Redmi 9 forums :good:
So moving forward I need you to try and boot a GSI on this phone. This post on Mi Community is helpful in understanding our device partition structure.
I think its fairly safe to boot a GSI because the stock recovery is actually maintained. The problem for me was the unofficial TWRP that caused my device to brick.
nielsync said:
You are the most active guy in the Redmi 9 forums :good:
So moving forward I need you to try and boot a GSI on this phone. This post on Mi Community is helpful in understanding our device partition structure.
I think its fairly safe to boot a GSI because the stock recovery is actually maintained. The problem for me was the unofficial TWRP that caused my device to brick.
Click to expand...
Click to collapse
Fastboot and fastbootd are not same...
But how i understand that my device is boot into fastbootd mood not fastboot mood....
Is their any secret key combination to go to fastbootd??
I think twrp methods is lot easier....but unfortunately we have not get stable twrp as soon ...
Shas45558 said:
Fastboot and fastbootd are not same...
But how i understand that my device is boot into fastbootd mood not fastboot mood....
Is their any secret key combination to go to fastbootd??
I think twrp methods is lot easier....but unfortunately we have not get stable twrp as soon ...
Click to expand...
Click to collapse
Sure with official TWRP life would be easy because you can also easily flash the dm-verity and forceencrypt disabler zip otherwise the device fails to boot even when you follow steps correctly. There's no key combination for fastbootd as far as I know. You have to use a command.
To enter fastbootd, run the following commands;
adb reboot fastboot (to boot into the bootloader)
fastboot reboot fastboot (to boot into fastbootd)
For the device to be recognized in Windows 10 you need to manually install unsigned Xiaomi drivers as shown here and after continue with the commands below;
fastboot flash system name_of_system_image.img
fastboot reboot recovery (and format data using MIUI recovery)
fastboot reboot (fingers crossed )
This post from the Redmi Note 9S may be helpful. The difference is that device has a Snapdragon processor as opposed to ours which is a MediaTek.
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....
Shas45558 said:
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....
Click to expand...
Click to collapse
Yeah I've seen it, thanks. That looks more promising than the first one. I haven't tested it yet but I'll do so as soon as I can on my own device. Have you tried it yourself though?
nielsync said:
Yeah I've seen it, thanks. That looks more promising than the first one. I haven't tested it yet but I'll do so as soon as I can on my own device. Have you tried it yourself though?
Click to expand...
Click to collapse
No i afraid to try.....u should try because you can restore your device...i can restore also but my laptop has some problem so do not want to take risk and unoffical is unofficial .....
And i think it is for chaina rom...ii use redmi 9 prime rom....
I'm still waiting a few more days now before I can unlock my bootloader. Can't wait to test it and use it to flash a GSI. The device you helped me root yesterday is also a Redmi 9 but wasn't mine and I can't mess around with someone else phone
nielsync said:
I'm still waiting a few more days now before I can unlock my bootloader. Can't wait to test it and use it to flash a GSI. The device you helped me root yesterday is also a Redmi 9 but wasn't mine and I can't mess around with someone else phone
Click to expand...
Click to collapse
I have also a waiting time of 98 hrs so im also here to help u all and flash gsi.Also theres a new for ya'll that PTRB RECOVERY is being tested nd booted also without any problem so jus wait some time nd stable version will be released .

Any official or unofficial lineage OS for Samsung galaxy M21

Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!!
Join telegram
they have CrDroid android 11
sinkoo1979 said:
Join telegram
they have CrDroid android 11
Click to expand...
Click to collapse
Thanks so much I'll join the telegram channel.
Before you waste ur time on telegram, the crdroid 11 does not work as of now and the dev isn't prepared to fix it. So wait until it is posted in xda
GuruPrasadAH said:
Before you waste ur time on telegram, the crdroid 11 does not work as of now and the dev isn't prepared to fix it. So wait until it is posted in xda
Click to expand...
Click to collapse
Any GSI you will recommend? (for M215G)
OldNoobOne said:
Any GSI you will recommend? (for M215G)
Click to expand...
Click to collapse
Any will work. I personally use crdroid since it is lightweight, has good performance, and has a lot of customizations. Use soulr344's twrp and use the built in super cmd to flash. Then flash Multidisabler, null vbmeta and magisk.
Use this build: https://github.com/eremitein/treble-patches/wiki/crDRom11-Project
Also don't plug in charger while power off, it will become stuck on boot screen. Use vol down+ power to reboot if that happens. Also DONT install hktweaks and overclock/underclock, it will cause random reboot
Chill
GuruPrasadAH
GuruPrasadAH said:
Any will work. I personally use crdroid since it is lightweight, has good performance, and has a lot of customizations. Use soulr344's twrp and use the built in super cmd to flash. Then flash Multidisabler, null vbmeta and magisk.
Use this build: https://github.com/eremitein/treble-patches/wiki/crDRom11-Project
Also don't plug in charger while power off, it will become stuck on boot screen. Use vol down+ power to reboot if that happens. Also DONT install hktweaks and overclock/underclock, it will cause random reboot
Chill
GuruPrasadAH
Click to expand...
Click to collapse
thanks bro ,
I dont have null vbmeta though, can you post link for null vbmeta if possible and the sequence of flashing the files as per your opinion.
I am downloading ( crdrom-v313-210921-arm64-BvZ-lite.img.xz ) for M215G (Galaxy M21 2021 Edition)
#Note -
I tried to flash another lineage GSI for android 11-> LirRMod ( lir-v313-210915-arm64-bvZ-lite.img) but failed so. Thanks in advance bro
OldNoobOne said:
thanks bro ,
I dont have null vbmeta though, can you post link for null vbmeta if possible and the sequence of flashing the files as per your opinion.
I am downloading ( crdrom-v313-210921-arm64-BvZ-lite.img.xz ) for M215G (Galaxy M21 2021 Edition)
#Note -
I tried to flash another lineage GSI for android 11-> LirRMod ( lir-v313-210915-arm64-bvZ-lite.img) but failed so. Thanks in advance bro
Click to expand...
Click to collapse
Yes... I failed many times, but it is all about the null vbmeta. That only disables dm-verity. I made this vbmeta flasher myself, bc no other existed.
Order-
1. WIpe data and reboot to recovery
2. Plugin to pc and transfer gsi image, vbmeta zip, multidisabler, and magisk(optional) to documents folder.
3. Go to terminal
4. Type the following cmds one by one
cd sdcard
cd documents
super mount system
super flash system [Name-of-the-image].img
5. Flash vbmeta
6. Flash multidisabler
7. Flash magisk(again, optional)
8. Flash custom kernel if u want( I recommend PrishKernel)
9. Reboot to system and enjoy.
Bro thanks so much, I will try your steps and tell you what happens ok
GuruPrasadAH said:
Yes... I failed many times, but it is all about the null vbmeta. That only disables dm-verity. I made this vbmeta flasher myself, bc no other existed.
Order-
1. WIpe data and reboot to recovery
2. Plugin to pc and transfer gsi image, vbmeta zip, multidisabler, and magisk(optional) to documents folder.
3. Go to terminal
4. Type the following cmds one by one
cd sdcard
cd documents
super mount system
super flash system [Name-of-the-image].img
5. Flash vbmeta
6. Flash multidisabler
7. Flash magisk(again, optional)
8. Flash custom kernel if u want( I recommend PrishKernel)
9. Reboot to system and enjoy.
Click to expand...
Click to collapse
Hi bro, I followed the steps above till step 5:
1. cd sdcard (worked)
2. cd documents (worked)
3. super mount system (worked)
4. super flash system crdrom-v313-210921-arm64-bvZ-lite.img (flashed but in 1s time)
so , I think gsi did not flash properly. any idea why?
OldNoobOne said:
Hi bro, I followed the steps above till step 5:
1. cd sdcard (worked)
2. cd documents (worked)
3. super mount system (worked)
4. super flash system crdrom-v313-210921-arm64-bvZ-lite.img (flashed but in 1s time)
so , I think gsi did not flash properly. any idea why?
Click to expand...
Click to collapse
Actually, raw images flash like this only. Carry on doing all the steps bro(did u try flashing every thing else and try booting?). Anyway, hope this helps you
GuruPrasadAH said:
Actually, raw images flash like this only. Carry on doing all the steps bro(did u try flashing every thing else and try booting?). Anyway, hope this helps you
Click to expand...
Click to collapse
Thanks bro, finally CRD managed to boot , I flashed stock rom then after that I followed your steps and it booted! . You saved my life bro coz GSI flashing guide on xda looked very complicated to me.
You said you made the vbmeta file on your own so you should be senior member in xda not new member XD . If you have donate button then pls post coz you & CrD deserve some donations. Thanks a lot
Can you also make vbmeta for Redmi Note 10 Mojito? Pls Pls
OldNoobOne said:
Thanks bro, finally CRD managed to boot , I flashed stock rom then after that I followed your steps and it booted! . You saved my life bro coz GSI flashing guide on xda looked very complicated to me.
You said you made the vbmeta file on your own so you should be senior member in xda not new member XD . If you have donate button then pls post coz you & CrD deserve some donations. Thanks a lot
Can you also make vbmeta for Redmi Note 10 Mojito? Pls Pls
Click to expand...
Click to collapse
Just a few clarifications:
1. I only made the flasher zip for the vbmeta. The image itself - was provided by google.
2. This zip should and will probably work on all phones, except maybe a few with weird vbmeta partition name( samsung vbmeta partition name is actually vbmeta_samsung instead of vbmeta only, and I think LG does the same too).
If it does not work( shows failed msg ) then send me the link of that device's twrp. I will maybe make an update if i find time.
Chill
GuruPrasadAH
Also, I'm just 13 yo as of now, so no donation for me. However, if u want to donate to crd, follow these two links:
https://www.paypal.com/paypalme/crdroidandroid -For crDroid themselves
For the guy who built the GSI, there seems to be no donate button.
Also, I saw ur post asking question about how M215G is different. Actually it is same, and remember - fastboot can never be installed on samsung. Also, turn off auto reboot when flashing twrp with odin, then hold down vol down+power for 7 secs until it reboots, then immediately press vol up+power. After this, wipe data and flash ROM.
If u reboot back to system without flashing multidisabler/rom, twrp will automatically be replaced with stock recovery. Hope this helps.
Chill
GuruPrasadAH
GuruPrasadAH said:
Also, I'm just 13 yo as of now, so no donation for me. However, if u want to donate to crd, follow these two links:
https://www.paypal.com/paypalme/crdroidandroid -For crDroid themselves
For the guy who built the GSI, there seems to be no donate button.
Also, I saw ur post asking question about how M215G is different. Actually it is same, and remember - fastboot can never be installed on samsung. Also, turn off auto reboot when flashing twrp with odin, then hold down vol down+power for 7 secs until it reboots, then immediately press vol up+power. After this, wipe data and flash ROM.
If u reboot back to system without flashing multidisabler/rom, twrp will automatically be replaced with stock recovery. Hope this helps.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Thanks bro, I am surprised how all the developers I came across are 13 year old
Wish you luck bro
CrDroid is good but I think ROMs are better than GSIs, for example -
1. CrDroid GSI has issue with MTP, device not getting recognized by PC! but inside TWRP I can transfer files from pc to Internal Storage
2. Also 3-button NavBar background is opaque not transparent so NavBar takes up 10% of the screen, gesture is fine but navbar is very handy.
I did not find any CrDroid vanilla version
OldNoobOne said:
Thanks bro, I am surprised how all the developers I came across are 13 year old
Wish you luck bro
CrDroid is good but I think ROMs are better than GSIs, for example -
1. CrDroid GSI has issue with MTP, device not getting recognized by PC! but inside TWRP I can transfer files from pc to Internal Storage
2. Also 3-button NavBar background is opaque not transparent so NavBar takes up 10% of the screen, gesture is fine but navbar is very handy.
I did not find any CrDroid vanilla version
Click to expand...
Click to collapse
Actually, one guy Daniel on telegram built a crdroid 11 rom(not gsi) for m21, however last I checked, it did not boot and booted into fastboot(pls don't ban me lol).
The dev said it was a DT(device tree) bug and that the fix wud take time.
And since there was more trolling than development happening in that group, I exited it.
Once it boots, it wud probably be posted under roms, so no need to join that toxic group as of now
GuruPrasadAH said:
Actually, one guy Daniel on telegram built a crdroid 11 rom(not gsi) for m21, however last I checked, it did not boot and booted into fastboot(pls don't ban me lol).
The dev said it was a DT(device tree) bug and that the fix wud take time.
And since there was more trolling than development happening in that group, I exited it.
Once it boots, it wud probably be posted under roms, so no need to join that toxic group as of now
Click to expand...
Click to collapse
Thanks bro, t.me is crazy with bots monitoring everything. Its not very secure as per me coz it downloads unwanted things to our device. It feels like as if soviet kgb is watching every group we join LOL.
I just wanted to say that if you're in android 11, you can flash the GSI image directly to system. Use TWRP 3.5.1 v3
Wipe data ( If you want to decrypt internal storage, flash multi disabler and format data )
Flash GSI
Flash dmverity disabler or magisk
Fredin_ said:
I just wanted to say that if you're in android 11, you can flash the GSI image directly to system. Use TWRP 3.5.1 v3
Wipe data ( If you want to decrypt internal storage, flash multi disabler and format data )
Flash GSI
Flash dmverity disabler or magisk
Click to expand...
Click to collapse
Hi Fredin bro, long time ..how you been? Youre the most helpful nice guy in t.me
My Redmi Note 10 came with MiUi 12.5.1 Android 11 out of the box, in these two months that ive been using Nebrassy2-Twrp and its different than Soulr344-Twrp, (Soulr344-Twrp 'super ' command = Nebrassy2-Twrp '#su' command), I couldnt flash GSIs using ( TWRP-3.5.2-mojito-Nebrassy-2.img ) so far.
Ive requested Soulr344 dev to make Soulr344-Twrp for RN10 Mojito/Sunny. If he ever drops by XDA perhaps he might notice.

[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!

I need some well working GSI's for my A605FN

Im on my A605FN right now and i have installed AOSP v222 (treble_a64_bvS-userdebug 10 QQ3A.200805.001 200805 test-keys) as my system. Can someone send me a working android 8 GSI? Android 10 is too much for this device and my 3gb of ram cant take it. I dont have time searching for well working GSI's to this phone. I need well optimized system that will use minimum ammount of resources. Thanks.
MDN2137 said:
Im on my A605FN right now and i have installed AOSP v222 (treble_a64_bvS-userdebug 10 QQ3A.200805.001 200805 test-keys) as my system. Can someone send me a working android 8 GSI? Android 10 is too much for this device and my 3gb of ram cant take it. I dont have time searching for well working GSI's to this phone. I need well optimized system that will use minimum ammount of resources. Thanks.
Click to expand...
Click to collapse
Just try that Lineage R mod - it should work fine. However if you want so old builds, then there is best list with Android 8 Oreo section:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
When i try to install lower android version than 10 my phone boots in download mode... Yes, regular odin mode, no errors, etc. Please help, i want to get rid of that android 10 no matter what version it is, even LineageOs or AOSP, its still android 10 that use a lot of resources to work smoothly
1. Download this and extract.
2. Go to TWRP.
3. Follow this guide (flash this in TWRP, not in Odin).
It should work well. Older Android versions may require older kernel versions to run or you just chosen wrong builds (it needs to be A/B arm32_binder64 (A64 - not arm64) vndklite).
In case that Lineage R mod is not smooth enough do the same with other GSI's from the list from my previous post (always choose arm32_binder64 vndklite (A/B) builds). Some will be lightweight enough for your needs.
Ye i know build for my phone . I will try the GSI you linked but which gapps should i use to this system?
And i have another great idea, what if i just not install the gapps and run clear CLEAR android
Hmm... Also i can install the most important gapps, I didnt think about that, that should use very small ammount of ram, cpu, etc.
MDN2137 said:
Ye i know build for my phone . I will try the GSI you linked but which gapps should i use to this system?
Click to expand...
Click to collapse
Just use build I linked above. It has integrated Gapps and passes needed certfications out of the box. You can also download vanilla build and flash pico gapps yourself. However option with integrated gapps is just fine and sufficient. Read whole thread - author had the same problem as you and solved it by flashing Lineage R mod with integrated gapps - it's the most simple way.
Idk why but when i flash this GSI with no error and then i try to boot to the system it goes download mode. I think i know how to flash GSI's, I'm doing it 100% right. I flashed it in every possible way. It is getting boring
MDN2137 said:
Idk why but when i flash this GSI with no error and then i try to boot to the system it goes download mode. I think i know how to flash GSI's, I'm doing it 100% right. I flashed it in every possible way. It is getting boring
Click to expand...
Click to collapse
Well, flash maybe at first stock firmware via Odin to ensure that kernel and vendor partiton are untouched. And then flash GSI in TWRP two times like it was said in guide.
However the most common cause of such effect (booting to download mode) is just wrong build (wrong architecture - you need to always download arm32_binder64 (A64) builds).
I already tried to flash GSI after flashing ROM via Odin3. Still booting to download mode. Im 420% sure i downloaded right build.
Well, I'm out of ideas. However you can still try to resize system partition in TWRP to make it a bit bigger and then try to flash GSI image (two times). You can also just try to play with different GSI's from the GSI list - just look for the smallest images and try to flash them. If some will properly boot then just go back to TWRP and flash rest of your needs (pico gapps, Magisk, etc.).
I will try that in future

Categories

Resources