Database Develop

Install GSI on S9 Exynos

Guys I successfully installed HAVOC-OS located https://forum.xda-developers.com/project-treble/trebleenabled-device-development/gsi-havoc-os-t3930030. The steps I followed are mentioned below
1. Wipe everything except internal storage.
2. Flashed BRK3 Vendor https://mega.nz/#F!wFFQUYbI!GZvNOBSn1wVn8U9mQDzBiw!IQsjlYzA
2. Installed Endurance GSI kernel https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/kernel-endurance-kernel-v1-0-t3849434
3. Flashed the system image for ARM 64 A only
4. Boot system
5. Reboot to recovery and Flashed Mgisk
6. Gapps will fail to install at first. Just goto wipe -> Adv wipe -> system partition -> Resize. Reboot to recovery and flash Gapps
7. Reboot and enjoy
8. You can test other GSI Roms also and report. The thread is located at https://forum.xda-developers.com/project-treble/trebleenabled-device-development

Thanks buddy. I was looking for the ways to run the GSI. And the method works. Good job

thanks for the guide! im still on an unrooted s9, but if everything works ill definetly make the jump. Can you tell us more about stability, bugs and if there are things not working

So after testing the ROM for 2 days I can say that
1. It is very stable and can be used as a daily driver
2. Everything works, I am not sure about Bluetooth audio though, haven't checked it
3. It can be heavily customized. Unlike LOS, where we have only few of these features available
4. Battery life is the best I got using any other ROM out there (check the screens below). and I am the guy who gets 3 hrs of SOT, when others claimed 5+ hrs on the same ROM.
5. Security patch is latest even as compared to the TW ROMs
6. Regarding camera... Its the same as LOS pie. Use gcam by idan 3.5 fixed and you are good to go.

fingerprint working?

andreMusers said:
fingerprint working?
Click to expand...
Click to collapse
Yes it is

Thanks for trying this out. I'm only a few months in with my exynos S9 on android pie, so I haven't yet learned the details about rooting/recovery for this phone.
I'll wait for your next update regarding daily use, and would love a more detailed step-by-step for installation if that's not too much trouble. I'm honestly loving those screenshots.

How about IMEI, BRK3 Vendor safe..?

Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.

burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Thanks for the extra instruction man, will test this out soon.

burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Doesn't work. Stuck on boot logo, loading forever.

Zwulf said:
Doesn't work. Stuck on boot logo, loading forever.
Click to expand...
Click to collapse
me too dont know any fix
EDIT: Somehow i managed to boot the rom but sim won't get detected

Double tap and AOD - work correctly? On snap it does not work well

My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected

Masterofchicken said:
My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected
Click to expand...
Click to collapse
So camera isn't working ,root is still present with magisk and i couldn't disable it with the adb command so safetynet doesn't pass ,i'll say it's not really usable ?

Has anyone found a fix for getting stuck at the s9 logo?..wanting to move to GSI ROMs

I have tried this,
After flash GSI rom, reboot recovery, reboot system and I have bootloop with the first logo Galaxy S9. Can anybody please help me?

@arunrawat2112
Finally I was able to flash some roms but none of them work properly. Can you please help me?

[Treble Project] How to download and install Treble Project for J7 Prime

Steps to install Treble ROMs on Galaxy J7 Prime.
Prerequisite:
1. Flash TWRP recovery. For Treble Project I suggest version 3.2.1 here because there is an issue about mounting /preload partition with 3.2.3+. You can try newer versions for your choices. If you see /preload error, Some suggested to ignore this error.
2. For emergency, please download Stock ROM here. If you accidentally mess up your partitions or consistently bricks, Stock ROM will reset everything back to start.
Needed Files:
1. Files from Project Spaget X here.
Exynos7870_CreateVendor.zip is to create /vendor partition.
Exynos7870_ProjectSpaget_V3.0.zip is to install necessary for Treble Project.
Exynos7870_RevertVendor.zip is to delete /vendor partition, in case of uninstalling Treble Project.
2. Treble ROM with ARM64 A only here. My favorite Treble ROMs are Lineage, Arrow and Havoc. I am currently using Arrow.
3. ARM64 GAPPS here.
4. Kraken Kernal here or here. Please download for Treble only. RC12 is universal.
5. Magisk here.
Step I Flash Treble project:
1. boot TWRP recovery
2. wipe Data, Cache, Dalvik, System
3. flash Exynos7870_CreateVendor.zip and reboot to recovery
4. flash Exynos7870_ProjectSpaget_V3.0.zip
Step II Flash Treble ROM:
1. flash Treble ROM ARM64 A only, no need to reboot to recovery in order to install the ROM.
Edit: Reboot to Recovery > Install > press Install Image > choose your Rom.img
2. After flashing the ROM, I usually reboot to system in order to test whether or not the flashed ROM can boot nicely.
2.1 If the flashed ROM cannot boot or brick or bootloop in Logo, press Home + Power + Vol Down to force reboot to Bootloader and boot to recovery.
2.2 Back to recovery. wipe Data, Cache, Dalvik, System
2.3 flash Exynos7870_ProjectSpaget_V3.0.zip before flashing new Treble ROM.
Step III Flash ARM64 GAPPS:
1. Choose Wipe > Advanced Wipe > choose System > Repair > Resize. Sometimes you need to do this twice in order to resize since the first time will show error.
2. flash GAPPS
Step IV Flash Kraken Kernal:
1. Mount > System and Vendor partitions
2. flash KRAKEN-Kernel-RC12-universal7870-Treble-20200314.zip (The latest version of Kraken)
3. reboot to system
I usually reboot once to system before flashing Magisk.
Step V Flash Magisk:
1. Mount > System and Vendor partitions
2. flash Magisk to root
3. reboot to system
4. run Play Store and set up your account
5. run Magisk Manager. When you press Tap to start SafetyNet check, you will find out that ctsProfile: false.
Please note that Usually it will be installed when you have GAPPS installed. If not, you can install Magisk Manager manually.
6. choose Downloads > search "SafetyPatch by hackintosh" > download and install > reboot This will fix ctsProfile false to be true.
Now you are done the basice steps to flash Treble ROMs for your J7 Prime. Any questions please leave a message under the thread.
Cheers, :highfive::highfive::highfive:

Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
---------- Post added at 05:11 PM ---------- Previous post was at 04:53 PM ----------
dctviphb2 said:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
Click to expand...
Click to collapse
i can flash now but when i flashed system.img completed, TWRP said that no OS installed, what can i do. thanks for your help

dctviphb2 said:
Thanks for your helpful post, but when i tried to flash system.img via TWRP, it showed just boot and recovery partition, i cant see system partition to choose, please help me. Thank you and sorry for my bad English
---------- Post added at 05:11 PM ---------- Previous post was at 04:53 PM ----------
i can flash now but when i flashed system.img completed, TWRP said that no OS installed, what can i do. thanks for your help
Click to expand...
Click to collapse
Please follow the attached screentshot.
1. In the main menu of TWRP, choose Install.
2. Choose your ROM.img
3. Select System Image. This step will tell TWRP to flash your ROM.img to the /system partition.
Note: Attached Screenshots #1-3 is to show steps to mount your /system and /vendor partition. Before your can do these steps, you need to flash Spaget X in the step I of my original post.
Hope this help.

siamese007 said:
Please follow the attached screentshot.
1. In the main menu of TWRP, choose Install.
2. Choose your ROM.img
3. Select System Image. This step will tell TWRP to flash your ROM.img to the /system partition.
Note: Attached Screenshots #1-3 is to show steps to mount your /system and /vendor partition. Before your can do these steps, you need to flash Spaget X in the step I of my original post.
Hope this help.
Click to expand...
Click to collapse
Thank you. I just remember that when i flash spaget my TWRP said "symlink: some symlink faild. Error 7". I have tried both TWRP 3.2.1 and 3.2.3 but both of them didnot work. I think i will try another version, or if you have any idea please tell me. Thank you so much

dctviphb2 said:
Thank you. I just remember that when i flash spaget my TWRP said "symlink: some symlink faild. Error 7". I have tried both TWRP 3.2.1 and 3.2.3 but both of them didnot work. I think i will try another version, or if you have any idea please tell me. Thank you so much
Click to expand...
Click to collapse
You're welcome. I honestly never experience this kind of error.
I found a solution about this error on youtube.
This solution is to extract ROM file and edit updater-script file with notepad++.
Edit: try this Spaget X file. I followed this youtube tutorial trying to fix error 7 that you got when flashing Spaget X.
Another possibility of this error is Partition messed up.
I would try to flash stock ROM with Odin to reset everything to factory default.
Caution: Back up your data before flashing Stock ROM.
Follow the instruction of how to flash Stock ROM in the Stock ROM page or here. Flashing Stock ROM will also remove TWRP recovery and re-partition.
Hope one of this solution help, :highfive::highfive::highfive:

Thank you so much. I think the problem is I am using HROM, which has Repatition.zip, so I think that my partition has messed up, that the reason I face the issue. I will try to solve it with your idea. Thanks so much for helping me, if I can solve the problem I will tell you

Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much

dctviphb2 said:
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
Click to expand...
Click to collapse
That's great NEWS. You've managed to find a solution for No OS installed error.
By the way, for the deep sleep problem that you mentioned, I also experience the same thing. My solution is to press home button to immediately wake the phone up from deep sleep.

[HELP]Treble Incompatible device (J7 PRIME)
I'm also using J7 prime G610F...but when i used Treble Checker is showed my device is Treble Incompatible...I don't understand why it is not working for me while you guys have the same phone and its working...also i'm using a custom rom (reserruction remix) so perhaps should i load up my stock system then try? I also tried to install the Treble project using the steps above but i couldn't flash the image...twrp was only detecting zip files and when i clicked in INSTALL IMAGE it would.nt show any image file which i transferred in my phone

hussain_mdj said:
I'm also using J7 prime G610F...but when i used Treble Checker is showed my device is Treble Incompatible...I don't understand why it is not working for me while you guys have the same phone and its working...also i'm using a custom rom (reserruction remix) so perhaps should i load up my stock system then try? I also tried to install the Treble project using the steps above but i couldn't flash the image...twrp was only detecting zip files and when i clicked in INSTALL IMAGE it would.nt show any image file which i transferred in my phone
Click to expand...
Click to collapse
Unpack .xz file

TWRP still doesn't detect the image
thanhphat95 said:
Unpack .xz file
Click to expand...
Click to collapse
...
---------- Post added at 12:53 AM ---------- Previous post was at 12:48 AM ----------
thanhphat95 said:
Unpack .xz file
Click to expand...
Click to collapse
i'm dummy dum so forgive and thenk

dctviphb2 said:
Thanks for your helping, after having flashed PIT files I has installed ArrowOS. I found that if TWRP show "No OS installed" after flashing ROM.img we must flash Spaget again to boot normally. Anyway I found that ArrowOS when I turn off screen for a while, when turn it on, it takes about 5s to screen on, do u have any solution? anyway tks so much
Click to expand...
Click to collapse
There is a solution...in phh treble settings go to doze then turn on out of pocket feature....works like a charm for me.....
------------
HAPPY TO HELP..

[Guide] [SM-T515] android 9 Install custom ROM'S and ROOT

SIZE="6"]Use this guide if your tablet is running on android 9. Android 10 is not covered in this guide[/SIZE]
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.

one last question
massivekind said:
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
Click to expand...
Click to collapse
you have been very kind. I'd like to ask you one last question. for the t515 (since the lineage os is generic) do you also use a particular kernel (which optimizes performance maybe) ?. thanks

gcomunale71 said:
Instructions:
you have been very kind. I'd like to ask you one last question. for the t515 (since the lineage os is generic) do you also use a particular kernel (which optimizes performance maybe) ?. thanks
Click to expand...
Click to collapse
No I don't have any, but if there is one for the 510 give it a try.
Of course backup before flashing

Hi,
Thanks for the guide. Which ROM you recommend? Everything working for you (LTE modem etc)?
Can you now install 64bit apps from Google Play? Any chance you can check if the DJI Fly app is working on your SM-T515?
https://play.google.com/store/apps/details?id=dji.go.v5
Thanks

liamR said:
Hi,
Thanks for the guide. Which ROM you recommend? Everything working for you (LTE modem etc)?
Can you now install 64bit apps from Google Play? Any chance you can check if the DJI Fly app is working on your SM-T515?
https://play.google.com/store/apps/details?id=dji.go.v5
Thanks
Click to expand...
Click to collapse
Well, It's still a 32bit rom. I've tried to install the app but I'm unable (prob because the app is 64bit)
Everything works fine, I'm running the lineageOS ROM. I have a data bundle and I'm able to internet with it (if I want )

massivekind said:
Well, It's still a 32bit rom. I've tried to install the app but I'm unable (prob because the app is 64bit)
Everything works fine, I'm running the lineageOS ROM. I have a data bundle and I'm able to internet with it (if I want )
Click to expand...
Click to collapse
I thought that this custom ROM is 64bit
When I bought the TAB A I thought it's a bargain, I didn't know that I wouldn't be able to install 64bit apps.

massivekind said:
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
Click to expand...
Click to collapse
first of all thanks for the great work.
Sorry if this is a stupid question , but before i brick my new SM-T515 I would rather ask the experts.
Now, i have rooted the stock ROM folowing the steps in https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root with no TWRP and want to install one of the custom ROMs you have tested.
will I lose root if flash the Legion ROM GSI?
if yes, can you please put some steps together to root and install TWRP?
i still have the “magisk_patched.tar" from the stock ROM, would that work for the Legion ROM GSI?

dj-rjay said:
Instructions:
first of all thanks for the great work.
Sorry if this is a stupid question , but before i brick my new SM-T515 I would rather ask the experts.
Now, i have rooted the stock ROM folowing the steps in https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root with no TWRP and want to install one of the custom ROMs you have tested.
will I lose root if flash the Legion ROM GSI?
if yes, can you please put some steps together to root and install TWRP?
i still have the “magisk_patched.tar" from the stock ROM, would that work for the Legion ROM GSI?
Click to expand...
Click to collapse
In theory it should work. I've already covered "root" also in the guide

I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?

Sambuca11 said:
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Click to expand...
Click to collapse
Mm strange, i don't use both functions so I can't really help you.
Maybe you could format the sd card via twrp?
On my side the sd card works. Didn't format the sd card so don't really know

Sambuca11 said:
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Click to expand...
Click to collapse
I have the same issue. Any solution?

zamboj said:
I have the same issue. Any solution?
Click to expand...
Click to collapse
I haven't found one yet, I'm going to try go back to Stock as I need my computer to be able to see the tablet to transfer files over. I've tried installing the Legion custom rom and it does the same thing. I'm not sure but I'd love to get an answer to this and I'd love to use a custom rom.
Are there any other Android 10 roms that I could try?

Sambuca11 said:
I haven't found one yet, I'm going to try go back to Stock as I need my computer to be able to see the tablet to transfer files over. I've tried installing the Legion custom rom and it does the same thing. I'm not sure but I'd love to get an answer to this and I'd love to use a custom rom.
Are there any other Android 10 roms that I could try?
Click to expand...
Click to collapse
I have a work app that need a little more ram: the solution is LineageOs (used 1,2gb vs 1,5gb of the stock rom) and I transfer files through recovery. I tried LegionOS but is full of bugs and file transfer doesn't work the same.

I'm back to stock and my computer and can see my table and the SD card is working fine. Its a shame as I'd love to use LineageOS but for now I'm stuck on stock.

I don’t know what I’m doing wrong so need some help please. I’ve installed TWRP and multidisabler. I’ve wiped the system cache data etc like I was flashing a custom rom.
I’ve downloaded the rom from the links flashed it via system image but I still get the message no os installed rebooted and just a bootloop saying unlocked boot loader press power button to start then nothing no booting image from linageos. Just repeats.
Can anybody tell me or guide me on what I could have done wrong and what what I should being

daljitbanga said:
I don’t know what I’m doing wrong so need some help please. I’ve installed TWRP and multidisabler. I’ve wiped the system cache data etc like I was flashing a custom rom.
I’ve downloaded the rom from the links flashed it via system image but I still get the message no os installed rebooted and just a bootloop saying unlocked boot loader press power button to start then nothing no booting image from linageos. Just repeats.
Can anybody tell me or guide me on what I could have done wrong and what what I should being
Click to expand...
Click to collapse
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.

Thanks for the reply I will try that when I get home later in the day and will post the outcome after.
Are there any other roms the we could also try.

massivekind said:
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Click to expand...
Click to collapse
I followed what you said but I’m stilling getting the bootloop for some reason could share links of what rom you downloaded and etc.
Because there must be a mistake in making.
Also to what I’ve been reading is that I need something of treble enabler for the device but I really don’t know.

massivekind said:
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Click to expand...
Click to collapse
I finally managed to get LineageOS installed. I just deleted all the files and redone loaded them, returned back to stock and did the whole process all over again.
And it worked. ? ? so maybe somewhere down the line put have been a corrupt download or something.
Custom rom has whole different feeling on the tablet now. Thanks again for tutorial, I’ve been waiting for something like this for a while.
You don’t know of any other roms there out there to try?

daljitbanga said:
I finally managed to get LineageOS installed. I just deleted all the files and redone loaded them, returned back to stock and did the whole process all over again.
And it worked. ? ? so maybe somewhere down the line put have been a corrupt download or something.
Custom rom has whole different feeling on the tablet now. Thanks again for tutorial, I’ve been waiting for something like this for a while.
You don’t know of any other roms there out there to try?
Click to expand...
Click to collapse
You've could try havoc os https://sourceforge.net/projects/ha...v3.5-20200522-Official-a64-ab.img.xz/download
Topic over here, I'm not sure if there are things not working, thats something you'd could figure out
https://forum.xda-developers.com/galaxy-tab-a/how-to/rom-havocos-v3-5-treble-guide-t4108127
I didn't tried this one, but is could be an option

[GUIDE] ROM flashing the easy way

We all know flashing ROMs got a lot more complicated with the advent of A/B partitions.
This is not my work, the aim here is only to highlight a process which simplifies the task.
Original post on the OnePlus 6 forum can be found here:
https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
It makes use of a script which copies the flashed firmware to both slots without having to reboot recovery and do it a second time. Also by not having to reboot recovery you avoid the issue where internal storage becomes unreadable.
Credit for this goes to:
LineageOS @erfanoabdi @filipepferraz @Prakyy @drpradsms
Download by prakky (hit the thanks button on his post below):
https://androidfilehost.com/?fid=8889791610682890605
The following posts detail it's usage which you follow at your own risk.

Clean Flashing a new ROM
Disable lockscreen security
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Format data; type 'yes' (backup as this wipes phone)
6) Boot System
Reboot recovery to flash additional zips.

Updating OOS base whilst on a custom ROM
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Boot System
Reboot recovery to flash additional zips.

Updating a custom ROM (nothing fancy here)
Boot TWRP 3.4+
1) Flash ROM
2) Flash TWRP installer
3) Boot System
Reboot recovery to flash additional zips.

Reverting to OOS
WARNING I've yet to test this!
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash Finalize.zip
3) Format data; type 'yes' (backup as this wipes phone)
4) Boot System
Note: this will revert you to stock recovery as well.

Tip:
Chain install the zips by selecting 'Add more Zips' after selecting the first zip.
Only 'Swipe to confirm Flash' once all zips have been queued.
I recommend numbering the zips in the order they need flashed.

Note: this issue is now resolved as of 09/08/20 as per https://forum.xda-developers.com/oneplus-6t/how-to/guide-rom-flashing-easy-t4143701/post83241857
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.

Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979

Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.

Deleted. Think maybe I'm getting altimeters. ?

Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Edited first post to make it clearer this is your work.

mitchst2 said:
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Click to expand...
Click to collapse
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??

Prakyy said:
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Click to expand...
Click to collapse
Good question.
Is 'Android Development and Hacking / General' the right place? There are some all device guides with a lot of views in there.
https://forum.xda-developers.com/android/general

mitchst2 said:
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Click to expand...
Click to collapse
As of 09/08/20 build and this commit all is well with OMNI and TWRP again. No need to edit the ROM zip anymore.

Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.

brajesh.sharma87 said:
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
Click to expand...
Click to collapse
No when switching ROM formatting data will be necessary. Not used it myself but others recommend Migrate to restore apps and data.

I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.

brajesh.sharma87 said:
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
Click to expand...
Click to collapse
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit

flash713 said:
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
Click to expand...
Click to collapse
I had to mandatory format data when I wanted to move from evolution x to aospa.

brajesh.sharma87 said:
I had to mandatory format data when I wanted to move from evolution x to aospa.
Click to expand...
Click to collapse
And I've also had to format data before as well but not lately. Could it be because I format both slots coming from OOS or because I use Canary Magisk or the recovery I use.. No idea but next time you are on EvoX backup system, data and boot and try and restore it using that recovery that comes with EvoX and see what happens. These last few weeks I've stayed on AOSiP and PixeN and I flashed Omni once I think but restoring from AOSPA to Pixen was flawless for me and also restoring Pixen to Pixen was also fine, which I do because I always mess around with sound mods.... I'm on AOSiP now and soon as I get more charge on my phone I'm going to try and restore to something I have a backup already made on one of my USB drives and I'll edit this post and report what the outcome is...

how downgrade sm-a605fn from android 10 to 9

Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you

1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.

nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.

I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks

Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.

I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much

Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
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

Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.

Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com

Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again

It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.

Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...

Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article

nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again

Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.

The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.

Maybe I have to try with sideload ?

Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?

nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?

Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.