Database Develop

[Discussion] TREBLE Support for Motorola G5s

Hello developers ( @kalyansundhar@govind1233 @lohanbarth @squid2),
I think everybody heard of project Treble. (Link, Link)
Of course Motorola isn't going to support it to our device(OTA update with repartition is very risky).
But somebody did already a unofficial port to the Xiaomi redmi note 4. This device isn't the same as the Moto G5s.
Today there is a developer doing it to the Xiaomi redmi 3s(Screenshots). This device is almost the same as the Moto G5s.
Specs of Xiaomi redmi 3s(Link)
Qualcomm MSM8937 Snapdragon 430
Adreno 505
5.0 inches
Accelerometer, gyro, proximity, compass
16 GB, 2 GB RAM
Specs of Moto G5s (Link)
Qualcomm MSM8937 Snapdragon 430
Adreno 505
5.2 inches
Fingerprint (front-mounted), accelerometer, gyro, proximity, compass
32 GB, 3 GB RAM
Do you developers think its possible for the Motorola G5s?
If this works we can make a lot of custom roms based on Treble.

Update
I think we must use OEM partition as Vendor partition.
Since a new partition was required for full treble we converted an unused cust partition into vendor which is almost 830mb in size, No we are not re-partitioning your device or anything else which may hardbrick your device
(Source)

GoldeneyeS2 said:
Update
I think we must use OEM partition as Vendor partition.
Since a new partition was required for full treble we converted an unused cust partition into vendor which is almost 830mb in size, No we are not re-partitioning your device or anything else which may hardbrick your device
(Source)
Click to expand...
Click to collapse
We could take one step at a time. First within the current setup, we should separate system and vendor libraries completely. There should not be any mix. Means /system/lib and /system/bin should have only system related. Similarly /system/vendor/lib and /system/vendor/bin should have only vendor related stuff. If we make the device work with this change, then it would be easy to make 'vendor' as separate partition. Even now we have /vendor folder in device root. This is just a symlink to /system/vendor, not a partition. In my opinion this would be a better way to go. Please correct me if I am wrong.
Thanks
KS

kalyansundhar said:
We could take one step at a time. First within the current setup, we should separate system and vendor libraries completely. There should not be any mix. Means /system/lib and /system/bin should have only system related. Similarly /system/vendor/lib and /system/vendor/bin should have only vendor related stuff. If we make the device work with this change, then it would be easy to make 'vendor' as separate partition. Even now we have /vendor folder in device root. This is just a symlink to /system/vendor, not a partition. In my opinion this would be a better way to go. Please correct me if I am wrong.
Thanks
KS
Click to expand...
Click to collapse
Its a good idea to take one step at the time.
What's wrong with this vendor tree? https://github.com/kayesk/android_ve...torola_montana
Project Treble on the Xiaomi Redmi Note 4
How did he do it? He used the “cust” partition on the device for his make-shift vendor partition. The cust partition normally holds a lot of device-specific stuff from MIUI, so it’s essentially wasted space on an AOSP build. Using the approximately 830MB unused partition, he moved the vendor HALs from system into cust without needing to repartition—which was a justification that OEMs such as Nokia and OnePlus used in their statements about why they weren’t going to bring Treble compatibility to their devices
We can use OEM partition. But what's the size of the OEM partition? And how do we make the HAL files?
We can also wait for the xiami 3s and port it to our phone.

GoldeneyeS2 said:
Its a good idea to take one step at the time.
What's wrong with this vendor tree? https://github.com/kayesk/android_ve...torola_montana
Click to expand...
Click to collapse
There is nothing wrong with the vendor tree you mentioned. You take any device tree in github, you could notice mix of libraries and binaries in /system/lib and /system/bin folder. It was ok to have it mixed till Nougat. But with Oreo and with the introduction of HIDL, things are changed. In Nougat we had only one binder. But in Oreo we have 3 binders (binder, hwbinder and vndbinder). Inter process communication is dealt differently. Even with OREO the mixed setup would work. But If we want to go Treble route, then it is better to move out remaining vendor binaries and libraries from /system partition.
We can download the factory image of one of the Pixel like BULLHEAD, MARLIN, etc. And study how the system and vendor partitions are laid out in their OREO release. Theoretically a treble supported system image should be device and make independent (a plain android system). Boot and Vendor partitions would be device specific. I mentioned boot partition here because it would be having device specific boot scripts like init.qcom..., init.mmi..., etc.
Thanks
KS

kalyansundhar said:
There is nothing wrong with the vendor tree you mentioned. You take any device tree in github, you could notice mix of libraries and binaries in /system/lib and /system/bin folder. It was ok to have it mixed till Nougat. But with Oreo and with the introduction of HIDL, things are changed. In Nougat we had only one binder. But in Oreo we have 3 binders (binder, hwbinder and vndbinder). Inter process communication is dealt differently. Even with OREO the mixed setup would work. But If we want to go Treble route, then it is better to move out remaining vendor binaries and libraries from /system partition.
We can download the factory image of one of the Pixel like BULLHEAD, MARLIN, etc. And study how the system and vendor partitions are laid out in their OREO release. Theoretically a treble supported system image should be device and make independent (a plain android system). Boot and Vendor partitions would be device specific. I mentioned boot partition here because it would be having device specific boot scripts like init.qcom..., init.mmi..., etc.
Thanks
KS
Click to expand...
Click to collapse
https://forum.xda-developers.com/xiaomi-redmi-3s/development/oreo-xperience-12-t3672111/
TEST build with vendor:
xperience-12.1.0-20180214-NIGHTLY-land.zip
-----------------------
Initial treble support
U need a custom recovery
Downlaod from here!
http://downloads.hostingsharedbox.com/ascarex/XPerience/12/land/3.2.0.1-TWRP-Land-Treble.img
Download the rom from here!.
http://downloads.hostingsharedbox.c...nd/xperience-12.1.0-20180214-NIGHTLY-land.zip
remember this is a initial work may contain some bugs if u are in older xperience build u not need to perform a clean install
Root u need this
https://drive.google.com/a/my.smccd.edu/uc?id=1oi5G-zzmPMX-WurvyiFRF1u1JjGr-Jvt&export=download
was made by abhishek987 AKA TheScarastic for the redmi note 4
https://forum.xda-developers.com/showpost.php?p=75527103&postcount=2233

Moto g5s doesn't support compass.. (model XT1797) and several model doesn't have NFC too

michael50310 said:
Moto g5s doesn't support compass.. (model XT1797) and several model doesn't have NFC too
Click to expand...
Click to collapse
That's not a big problem.

GoldeneyeS2 said:
https://forum.xda-developers.com/xiaomi-redmi-3s/development/oreo-xperience-12-t3672111/
TEST build with vendor:
xperience-12.1.0-20180214-NIGHTLY-land.zip
-----------------------
Initial treble support
U need a custom recovery
Downlaod from here!
http://downloads.hostingsharedbox.com/ascarex/XPerience/12/land/3.2.0.1-TWRP-Land-Treble.img
Download the rom from here!.
http://downloads.hostingsharedbox.c...nd/xperience-12.1.0-20180214-NIGHTLY-land.zip
remember this is a initial work may contain some bugs if u are in older xperience build u not need to perform a clean install
Root u need this
https://drive.google.com/a/my.smccd.edu/uc?id=1oi5G-zzmPMX-WurvyiFRF1u1JjGr-Jvt&export=download
was made by abhishek987 AKA TheScarastic for the redmi note 4
https://forum.xda-developers.com/showpost.php?p=75527103&postcount=2233
Click to expand...
Click to collapse
Wait i'm a little confused. Did you post this rom for our device, because it looks like it's for the Redmi 3s. I know the whole idea is beased on this device, but i'm still confused. Don't want to flash anything and brick my device. Sorry if i'm being dumb, just want to be sure

Joseph Hill said:
Wait i'm a little confused. Did you post this rom for our device, because it looks like it's for the Redmi 3s. I know the whole idea is beased on this device, but i'm still confused. Don't want to flash anything and brick my device. Sorry if i'm being dumb, just want to be sure
Click to expand...
Click to collapse
Don't use this on Motorola G5s. Its for the Redmi 3s.
If there will be a version you will find it in another thread.

@vaserbanix (https://forum.xda-developers.com/moto-g5s/development/kernel-tweaks-t3744384/page2)
also i repaked that XperienceOS for mi3s from new.dat to meta-data for better wiev without install
download the rom and study it
https://drive.google.com/open?id=1Cp...L_gtJ1zQIqIOca
!!! do not install it!!!!
@kalyansundhar
Can you use this?

Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
Yeah I have it for Moto Z play too but u need to wait until my isp fix my internet issues , so for now I can't upload the source sorry
I hope it can be fixed in 3 days
-------------------------------------------------------------------
I ask the developer to release his source code. We have to wait till his internet is fixed:laugh:

Look there is a ARM 32bits system image thats support's Treble
Download:
v12 (android-8.1.0_r15):
system.img for A/B ARM64 devices with GApps and SU
system.img for A/B ARM64 devices vanilla
system.img for A-only ARM64 devices with GApps and SU
system.img for A-only ARM64 devices vanilla
system.img for A-only ARM32 devices vanilla
Patches for custom ROMs build
Source: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659

Dear members, any luck with porting MIUI for Moto G5s plus?
Request you to please guide and share link.

[RECOVERY][TREBLE] TWRP Recovery for Zenfone 3

This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12

@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.

dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now

iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol

dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.

makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?

dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )

makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.

Great work guys!! Waiting for vendor partition, for some tests!

Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.

Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.

Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?

[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.

fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.

I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.

Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition

can i flash android q gsi images using treble recovery.

Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?

Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.

Can i flash android Q gsi image using this recovery on ze520kl

[HOW-TO] Use Generic System Images (GSI A-Only) on Your Xiaomi Mi Mix 2 Devices

Welcome​First of all make sure You know the Basics which are:
-You need to have a unlocked Bootloader
-You need to have the Orange Fox Recovery installed
-You need to have a Kernel and a Vendor Image
-You need to have a Treble A-Only Generic System Image (GSI)
-(Optional) A actual Magisk Installer zip File
-(Optional) A actual Open GApps Installer zip File
(Just use Google and You will find everything)
Alright. Now to the flashing!
-Make sure You have the needed Basics on Your Device including the Files You want to flash
-Wipe everything including data, caches, system, vendor
-Now flash a Vendor and Kernel Image to Your Device
-(You can download My "Vendor Installer" or)
-Flash a Treble AOSP ROM for Your Device and wipe System again
-Flash the Generic System Image using the Image Install from TWRP
DONE!
If You want to install Root and GApps on Your Device:
-Reboot to the Recovery and wipe Data/Caches again
-Install Magisk and GApps (Nothing else yet)
-Reboot to the System
DONE!
This Thread will be updated from Time to Time with new Vendor Installers and better Instructions. Feel free to talk about GSI ROMs in this Thread. I will keep it moderated as good as i can!
Download Links:
https://sourceforge.net/projects/orangefox/files
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Vendor Installer from Me: https://drive.google.com/drive/folders/1onzbCmoy18WlNDNFpq67z0Bv7QHB1d-b?usp=sharing
Actual Vendor: OMNI with EAS Kernel

Hello, I can not flash this vendor file. The orange fox returns ERROR7

q13017 said:
Hello, I can not flash this vendor file. The orange fox returns ERROR7
Click to expand...
Click to collapse
There is a more actual thread around the Mix 2 Forum. Try to search for it over Google, it provides more actual Vendors if i'm not wrong

Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?

Atcastells said:
Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?
Click to expand...
Click to collapse
Same issue here - the last working version is from March 2019.

If I put a gsi with a vendor from custom firmware, will my phone die?

Treble/GSI Megathread

About
I've found information about flashing GSI's on this phone to be fragmented so here's a collection of resources that have worked for me.
If you have any suggestions or issues with popular GSI ROMs, drop them here and I'll do my best to update the thread.
Note: This guide is for users who have already flashed custom ROMs (not necessarily GSI) to their phone. If you're new to this or are coming from any MIUI ROM, please see other tutorials.
Click to expand...
Click to collapse
GSI Installation
1. Flash TWRP
The current latest version (as of the time of writing v3.3.0) supports for flashing GSIs.
2. Update firmware (optional)
I'm currently using the latest global firmware (as of time of writing v10.2.2.0) which seems to work fine. Download the zip from xiaomifirmwareupdater and flash in TWRP.
3. Flash treble BOOT and VENDOR partitions
Download the below image files (source).
boot.img
vendor.img
Install the images by using the following command or optionally using TWRP.
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
4. Flash your GSI ROM
Pick a GSI from the Treble forum and be sure to download an ARM64 and A-Only variant. If the downloaded file is an archive (not an *.img file) you will need to extract the contents.
Go into TWRP
Copy the GSI image to your phone
Wipe "Dalvic/ART Cache", "Cache", "System" and "Data" paritions
Install the GSI image to the System Partition (Install -> Install Image -> yourimagefile.img - System Image)
Reboot back into TWRP
Resize the system partition (Wipe -> Advanced Wipe -> check System -> partition options -> Resize FS)
Install Magisk & OpenGapps (both optional)
GSI ROMs
Pixel Experience 9 (2019-03-24)
Source: XDA
Status: Working.
Additional info: Everything works as expected.
AospExtended v6.2 (20190313)
Source: aospextended
Status: Working.
Additional info: Everything works as expected.
Ressurection Remix v7 (19/04/16)
Source: XDA
Status: Unusable.
Additional info: Everything works aside from video playback (which creates a loud popping/static sound regardless of audio levels).

Has someone tried oui ??

Great guide! Thanks a lot, your way was the only way I could get a treble rom working on the device! I wasn't able to flash the vendor in fastboot coming from miui 10.2.2.0, but it worked from twrp. Now got Havoc booted successfully

has anyone tried q gsi?

xeodm said:
has anyone tried q gsi?
Click to expand...
Click to collapse
If you want to use it, try it out. There's no reason it shouldn't work ?

Anyone successfully flashed Android Q beta 5 GSI?
I tried my best, but it is not booting up!

djmanri3 said:
Has someone tried oui ??
Click to expand...
Click to collapse
I'm going to try it later. I will update if it works.

djmanri3 said:
Has someone tried oui ??
Click to expand...
Click to collapse
Unfortunately, it doesn't boot. I want to try it too !

salahmed said:
Anyone successfully flashed Android Q beta 5 GSI?
I tried my best, but it is not booting up!
Click to expand...
Click to collapse
I remember someone saying u need to use permissiver 3 or 4

gsser said:
I remember someone saying u need to use permissiver 3 or 4
Click to expand...
Click to collapse
Do you have a link?
Regards

salahmed said:
Do you have a link?
Regards
Click to expand...
Click to collapse
I dont have any unfortunately, it might be in erfano's telegram group or mix 2 aosp group.

I'm Stuck Help!
I'm stuck on AOSP EX Boot Animation, What to do now?
I did all right!!
Why is this happening

Fix for the audio problem
andythedev said:
About
I've found information about flashing GSI's on this phone to be fragmented so here's a collection of resources that have worked for me.
If you have any suggestions or issues with popular GSI ROMs, drop them here and I'll do my best to update the thread.
GSI Installation
1. Flash TWRP
The current latest version (as of the time of writing v3.3.0) supports for flashing GSIs.
2. Update firmware (optional)
I'm currently using the latest global firmware (as of time of writing v10.2.2.0) which seems to work fine. Download the zip from xiaomifirmwareupdater and flash in TWRP.
3. Flash treble BOOT and VENDOR partitions
Download the below image files (source).
boot.img
vendor.img
Install the images by using the following command or optionally using TWRP.
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
4. Flash your GSI ROM
Pick a GSI from the Treble forum and be sure to download an ARM64 and A-Only variant. If the downloaded file is an archive (not an *.img file) you will need to extract the contents.
Go into TWRP
Copy the GSI image to your phone
Wipe "Dalvic/ART Cache", "Cache", "System" and "Data" paritions
Install the GSI image to the System Partition (Install -> Install Image -> yourimagefile.img - System Image)
Reboot back into TWRP
Resize the system partition (Wipe -> Advanced Wipe -> check System -> partition options -> Resize FS)
Install Magisk & OpenGapps (both optional)
GSI ROMs
Pixel Experience 9 (2019-03-24)
Source: XDA
Status: Working.
Additional info: Everything works as expected.
AospExtended v6.2 (20190313)
Source: aospextended
Status: Working.
Additional info: Everything works as expected.
Ressurection Remix v7 (19/04/16)
Source: XDA
Status: Unusable.
Additional info: Everything works aside from video playback (which creates a loud popping/static sound regardless of audio levels).
Click to expand...
Click to collapse
https://github.com/hmuny99/GsiSystemAudioFix
Use this flashable zip to fix the audio stuttering issue.

Someone tried it with the Q GSI's from Erfan? I can't get it to work....

pattagalix said:
Someone tried it with the Q GSI's from Erfan? I can't get it to work....
Click to expand...
Click to collapse
Not with Efran's gsi's but I've tried a few times on other 10's and had no luck on my end. I Used the 10 gsi Aonly 64 bit and I've formatted data and decrypted using Zach's force encrypt removal zip and magisk su zip and I've tried without removing encryption and no luck. It hangs on mi boot logo every time. I saw a DerpFest gsi on telegram that's when this whole gsi mission began for me. lol. Maybe we need a different boot.img and vendor.img for 10 idk? ? I tried with and without flashing the boot and vendor, decrypt and not decrypt and no go. ?
Sent from my moto g(7) power using XDA Labs

I booted RR v7.03 from Luke's GSI thread using vendor and boot in op but tried a few more 10 GSIs and they either hang on mi screen or bootloop forever. This RR is bad ass!! V7.03 wasn't made for Chiron and blows 7.02 off the map. Although security patch is from November 2019 I'm going to rock it a while. Sure will miss RR now that main dev stopped. Talk about a bad ass ROM!!! If anyone wants to use it its here. Just click the top link and you'll see the A only 64
https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457

[RECOVERY] [TREBLE] TWRP 3.3.1-0 with Tissot Manager

Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01

Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!

Reserved

Great work.
Sent from my Mi A1 using Tapatalk

Thanks ??

Nice. Bro you carried legacy ?

nice work waiting for shrp version of this ??

Noice :good:
Sent from my Mi A1 using XDA Labs

This is an update of TWRP Comic Dan?

manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op

Any way to flash it using cosmic dan's twrp? I don't have any pc now

Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.

Great job dude ?

Awesome work!
Thank you so much for this.

@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?

sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.

Where is the survival checkbox??

What is this "inject twrp" does ?

oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option

Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?