Related
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.
View attachment 4567426
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI. You can find a GSI here: Phh-Treble
ZTE Axon 7 hardware vs Treble implementation:
Our Axon 7 is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images
What's Packaged in the zip:
A boot image (kernel)
A compressed vendor image (vendor)
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part. How to flash a Generic System Image (GSI) on Project Treble supported devices
- Reboot
Alternative Instruction
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
Broken:
Encryption (format data or remove encryption when coming from a non-treble rom)
Sepolicy is still permissive
Nothing else? Otherwise please report it!
Download:
- TWRP 3.2.1-8 TREBLE
- AXON7_GPT_ADD_VENDOR_800MB
- Project_Treble_v1.1-Axon7-by-NFound
Available GSI images is here
Android Pie Release 1 and other (video proof on Axon 7)
Fixes:
- More fixes for Treble ROM by @Kranoner
Credits:
@djkuz for add part. /vendor
@NFound for the fact that this dude did this for us real
Contributors:
@NFound
OS Version based: 8.X Oreo
ROM Kernel: Linux 3.18.71
ROM Firmware Required: Official BETA B12 Oreo
Version Information
Status: Testing
Source-Code Vendor
Created 2018-08-08
Last Updated 2018-08-12
Reserved
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Waancho said:
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Click to expand...
Click to collapse
Any ARM64 with opengapps.org for 8.x, in GSI 9.x Gapps included
Dear friends! Do not forget to backup before installation, this is a test version. It's time for me to sleep, write. As time will be, I will read your comments. If you find bugs - be sure to specify the version of GSI Android 8.x or 9.x
Thank you!
Hey need fast answer! In this guide is talking about a Vendor 8.1 and 8.0 and 8.0 does not work with this rom, so my question is does this rom support your treble? https://forum.xda-developers.com/pr...development/aosp-9-0-android-9-0-gsi-t3826357
Source code vendor blobs in OP
NFound said:
Source code vendor blobs in OP
Click to expand...
Click to collapse
I am a bit confused: how would non-standard hardware like our famous DAC be used in a treble ROM? Would the vendor partition make specific APIs available for such non-standard hardware?
Thank you for this. Maybe its a stupid question, but does the DAC properly function even when we install a GSI?
I have a feeling that a proper fully functional treble will make the other custom ROM thread for Axon 7 obsolete.
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Zobat said:
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Click to expand...
Click to collapse
You dont need a windows-pc. Only twrp
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Let me see if I got this whole treble situation straight :cyclops:
I'm running the latest AEX but I assume this guide contains a more updated "treble" so to speak, is that correct? In order to try the GSI's do I need to follow this guide and wipe everything or will the next AEX release update treble and contain the new fixes?
https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64aonly/
Arm64 and A only. Should be working right?
BaamAlex said:
You dont need a windows-pc. Only twrp
Click to expand...
Click to collapse
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
troy5890 said:
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Click to expand...
Click to collapse
You will need to install this again Project_Treble_v1.0-by-NFound
it contains bug fixes
bornlivedie said:
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
Click to expand...
Click to collapse
For this zip here he dont need a PC. For the EDL package yes.
Just wanted to thank you and talk about my experience.
Converting the device to Treble was a breeze. Can be done in under 5 minutes with no issues at all. I'm currently running Android P PR1 with no major problems.
However, when trying to install the GSI (totally not related to your work, but wanted to comment on this so everyone can enjoy treble) I ran into a small problem (error 7) when flashing the POST sGSI zip files. I resolved this by doing the following:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
This worked out fine for me.
Again, thanks a million times on your epic feat. This is no small task, and is very welcome. It marks a before and an after.
You, sir, are heaven-sent. Thank you for your good work.
bornlivedie said:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
Click to expand...
Click to collapse
Why a second time?
Dear friends!
In the video I am used Release 1.
1. Flash Project Treble
2. Flash GSI
3. !!! In Mounting - UNMOUNT and MOUNT system and vendor!
4. Install patches 1,2,3
5. Reboot
Android Pie Release 1 (Download A-only and patches): https://androidfilehost.com/?w=files&flid=280192
Work GCam: https://github.com/AospExtended/platform_vendor_aosp/blob/8.1.x/prebuilt/common/apk/Gcam.apk
NOTICE: If during a call on Android 9 you do not hear the subscriber. (thx @atakan33 )
PS Here is another list of available GSI ROMs, use the translator!
9.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-2
8.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-3
Thank you!
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
Hi I Have .img files of precompiled oxygen 10.3.7 OSs that I want to share.
I use a dual boot from Orangefox
The actual firmware came from Oneplus.com
I also used Smurf kernel and xXx NoLimits ☆ for OnePlus
Installation is easy
1. Boot into a twrp
2. Flash Orangefox dual boot (partition I used is a-96gb b-96gb with a C-of 32gb.
3. Flash the .img files to the correct Partitions.
4. Flash orangefox twrp agian updating the filesystem to how you programmed it
5. Enjoy I also recommend updating magisk.
I'll be posting more quick image files of precompiled OSs soon. Mainly off original Oxygen 10.3.7.
Let know if theirs anything to fix or build. This is a quick way to not have to switch slots and get an OS on your phone.
https://mega.nz/folder/qno2HCQa#i9lYlnSOyj7RZe2kNDBCNA
also if you setup Your OS how you want it and make a twrp backup of the data. than you can do the above procedure and also restore your setting and hooks after.
Can You please explain what exactly it is?
spheady said:
Hi I Have .img files of precompiled oxygen 10.3.7 OSs that I want to share.
I use a dual boot from Orangefox
The actual firmware came from Oneplus.com
I also used Smurf kernel and xXx NoLimits ☆ for OnePlus
Installation is easy
1. Boot into a twrp
2. Flash Orangefox dual boot (partition I used is a-96gb b-96gb with a C-of 32gb.
3. Flash the .img files to the correct Partitions.
4. Flash orangefox twrp agian updating the filesystem to how you programmed it
5. Enjoy I also recommend updating magisk.
I'll be posting more quick image files of precompiled OSs soon. Mainly off original Oxygen 10.3.7.
Let know if theirs anything to fix or build. This is a quick way to not have to switch slots and get an OS on your phone.
https://mega.nz/folder/qno2HCQa#i9lYlnSOyj7RZe2kNDBCNA
also if you setup Your OS how you want it and make a twrp backup of the data. than you can do the above procedure and also restore your setting and hooks after.
Click to expand...
Click to collapse
Sorry I the project was not what I expected. Mainly going to make a fastboot installer pakackage for 10.3.7 and another flasher package for if I scew up and get stuck on my bootloader, with the files. I am not able to setup a PC for long right now so it would be wise. The smali thing turned out not working. The twrp can install into The New beta 11 that people are trying to root with boot.img's on another post
Working GSI TAB A8 SM-X200
BUGS: i don't know you tell me?
Instructions:
From OEM stock firmware with root installed
Download the DSU Loader by VegaBobo make sure to download release.apk.
once installed open the app click Select a GSI File to be installed.
once that's done it will ask you to select a folder on where you want it to be installed to for this i just created a folder called gsi in the main directory
then once i have created the folder select the .xz or .gz or .img
and then after that make sure you change your userdata size to around 18gb or 20 if you want space for some apps!
and for the last bit all you have to click on is install gsi via DSU and from there it will do its work
Also make sure your running firmware: X200XXU1AVG1
Remember this gsi is only temp and will not replace your main android system
Downloads:
GSI ROMS: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Official GSI from google: https://developer.android.com/topic/generic-system-image/releases
DSU Downloader: https://github.com/VegaBobo/DSU-Sideloader
Credits to :https://github.com/VegaBobo
I'd love to use this but the A8 and it's tiny storage space prevents DSU from even being installed
kevinco1 said:
I'd love to use this but the A8 and it's tiny storage space prevents DSU from even being installed
Click to expand...
Click to collapse
rip
Should I use ARM64 or ARM64 binder ROM?
You have to be running X200XXU1AVG1 in order to get DSU to work? Just upgraded to Android 12...
Wich android 13 gsi work?
How did you get DSU to work on this device? The storage limitations have always prevented me from using this method
which gsi should i use for tab a8(ARM64+GMS or ARM64) ?
thaovd1712 said:
which gsi should i use for tab a8(ARM64+GMS or ARM64) ?
Click to expand...
Click to collapse
If you want the google services, you need GMS.
WackyHacky1 said:
rip
Click to expand...
Click to collapse
can you downgrade from stock 12 to gsi 11?