What is Google’s Project Treble?
You should read here some Frequently Asked Questions (FAQ) thanks to Recognized Developer @phhusson
This is an index for (all) Treble Projects or also Generic System Image (GSI) list.
This is the known compatible device list.
This is a Guide to build Project Treble GSI ROMs from source
Motorola Z2 Force is NOT a Project Treble compatible device, but it IS a semi-compatible. This means that you can move toward Treble ROMs with some previous steps.
Moving from Lineage 15.1 toward Oreo Treble ROMs
1. Unlock your bootloader or, if it is already unlocked, you can, optionally, download and use a flashall solution to turn back to stock if necessary.
2. Flash and boot Lineage ROM 15.1. Here you have guides to do it. Better if you flash to both slots (changing between then via fastboot set_active other command. This is necessary to get boot and vendor partitions compatible with Treble images.
3. Backup everything you need (see step n.6 below).
4. Remove PINs, passwords, fingerprints.
Now you can follow the default flashing GSI procedures:
1. Download an Android 8.1 (Oreo) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
2. Remove all PIN, password, fingerprint security and allow USB Debugging.
3. Uninstall Magisk and reboot the phone. Then reboot again into bootloader.
4. Boot (not flash) TWRP Treble (via fastboot boot <twrp.img file name>)
5. Flash the downloaded Treble system image.
6. Flash Open GApps (Platform ARM64, Android 8.1) (if the GSI image does not include them).
7. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data.
8. Boot the phone and set it up, allowing USB Debugging.
9. Boot TWRP image file and then flash zip file it to make it permanent.
10. Reboot into flashed TWRP (mandatory).
11. Flash Magisk and reboot.
Know issues - Oreo
1. So-called "Technicolor" bug when moving into or out dark mode, or when using Substratum themes, when icons and the screen got weird colors effects and stripes. Generally, you could boot into recovery and wipe Dalvik/Cache.
2. ViPER4Android not always compatible with Treble.
3. VoLTE.
Moving from Lineage 15.1 toward Pie Treble ROMs
1. Requirements: have an Oreo Treble ROM already running.
2. Download an Android 9.0 (Pie) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
3. Remove all PIN, password, fingerprint security and allow USB Debugging.
4. Uninstall Magisk and reboot the phone. Then reboot again into bootloader.
5. If you do not have TWRP yet, flash TWRP image via fastboot flash <twrp.img file name>
6. Reboot into TWRP.
7. Flash the downloaded Treble system image.
8. Flash Open GApps (Platform ARM64, Android 9) (if the GSI image does not include them).
9. Check if vendor partition is mounted via TWRP. If not, mount it.
10. Flash POST-sGSI 3 zip file. More info here.
11. Reflash TWRP.
12. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
13. Boot the phone and set it up, allowing USB Debugging. Reboot into TWRP.
14. Flash Magisk and reboot.
Old method:
1-9: The same as above.
10. Flash POST-sGSI zip files -1- and -2-.
11. Flash the Permissiver zip.
12. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
13. Boot the phone and set it up, allowing USB Debugging. If you can't boot, return to TWRP, flash/sideload the FBE_Disabler zip and wipe data as stated here. In this last case, you'll lose all your data including sdcard.
14. Flash Magisk and reboot.
Know issues - Pie
1. Message on each boot: "Android System: There's an internal problem with your device. Contact your manufacturer for details". Solution proposed by @palbadi. In details, fix for vendor mismatch popup:
A. In a root file manager, backup both \vendor\build.prop and \system\build.prop files.
B. Open \system\build.prop original file with a root text editor. Copy the line with ro.build.fingerprint variable, for instance:
Code:
ro.build.fingerprint=Android/treble_arm64_bvN/phhgsi_arm64_ab:9/PQ1A.181105.017.A1/64:userdebug/test-keys
C. Open \vendor\build.prop original file with a root text editor. Find the the line with ro.build.fingerprint variable, for instance:
Code:
ro.vendor.build.fingerprint=motorola/nash/nash:8.0.0/OPXS27.109-34-10/5:user/release-keys
D. Paste the copied system variable over the vendor one (replace).
E. Save the \vendor\build.prop file.
F. Reboot.
2. ViPER4Android not always compatible with Treble.
3. VoLTE.
4. The combination of TWRP + Magisk could let you without WiFi. You can try not flashing TWRP in any steps above, just booting it: fastboot boot <twrp.file.name>.img
Moving from Lineage 16 toward Pie Treble ROMs
1. Requirements: have Lineage 16 (Pie) already running.
2. Download an Android 9.0 (Pie) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
3. Remove all PIN, password, fingerprint security and allow USB Debugging.
4. Uninstall Magisk (if you have it) and reboot the phone. Then reboot again into bootloader.
5. If you do not have TWRP yet, flash TWRP image via fastboot flash <twrp.img file name>
6. Reboot into TWRP.
7. Flash the downloaded Treble system image.
8. Flash Open GApps (Platform ARM64, Android 9) (if the GSI image does not include them).
9. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
10. Boot the phone and set it up, allowing USB Debugging. Reboot into TWRP.
11. Flash Magisk and reboot.
Know issues - Pie
1. Message on each boot about Vendor is not up-to-date.
2. ViPER4Android not always compatible with Treble. There is a solution here.
3. VoLTE.
4. The combination of TWRP + Magisk could let you without WiFi. You can try not flashing TWRP in any steps above, just booting it: fastboot boot <twrp.file.name>.img
5. If anytime you lost Wi-Fi (or your Mac address become 02:00:00:00:00:00), see this post.
Support
Discord support channel.
XDA Treble-Enabled Device Questions and Answers.
XDA Treble-Enabled Device Guides, News, & Discussion.
Treble-Enabled ROMs Development.
Muchas gracias por tu apoyo, estaba buscando esta información después de ver los links en tu firma
Google translate
Thank you very much for your support, I was looking for this information after seeing the links in your signature
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
asislife20 said:
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
Click to expand...
Click to collapse
Only boot it from the TWRP that used for flash LineageOS
asislife20 said:
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
Click to expand...
Click to collapse
I have changed the guide and added link. Is it clear now? Thanks.
omnismart said:
Muchas gracias por tu apoyo, estaba buscando esta información después de ver los links en tu firma
Google translate
Thank you very much for your support, I was looking for this information after seeing the links in your signature
Click to expand...
Click to collapse
hola podrias ayudarme a hacer esto en mi dispositivo por favor...
AlucardMemnoch said:
hola podrias ayudarme a hacer esto en mi dispositivo por favor...
Click to expand...
Click to collapse
Aún no me muevo a esta rom, he estado un poco ocupado y requiere respaldar toda la memoria interna para evitar problemas, eso me implica depurar whatsapp.
Revisa el siguiente enlace, tal vez y te ayude un poco por si tienes algún problema y quieras volver a stock.
I still do not move to this rom, I've been a bit busy and requires backup all internal memory to avoid problems, that means I debug whatsapp.
Check the [URL = "https://www.htcmania.com/showpost.php?p=29253595&postcount=2"] next link [/ URL], maybe and it will help you a bit in case you have a problem and you want to go back to stock
Flashed PE 9 img (PE-AB-2018-09-20) instead of 8 over lineage-15.1-20181009-nightly-nash-signed.zip by mistake.... and it happened to be ok ))
So far everything works fine ....
Maybe it's time to optimize Guide?
pakhan8 said:
Maybe it's time to optimize Guide?
Click to expand...
Click to collapse
In which point?
Technical said:
In which point?
Click to expand...
Click to collapse
I think he means the need to first install an 8.1 GSI rom before doing a 9 (Pie) GSI?
CykloneFij said:
I think he means the need to first install an 8.1 GSI rom before doing a 9 (Pie) GSI?
Click to expand...
Click to collapse
Well, I never said that. Anyway, I've updated the guide to make it clear the movement from Lineage 15.1 toward Oreo or Pie.
Does Moto Mods work?
Hello, I would like to know if Moto Mods work with this project. Thank you in advance for your attention.
Pedro Gomes said:
Hello, I would like to know if Moto Mods work with this project. Thank you in advance for your attention.
Click to expand...
Click to collapse
Yes, in theory, all mods work. Some controls and apps (and their functions) could not, though.
You can always test and revert to stock if you want
Technical said:
Yes, in theory, all mods work. Some controls and apps (and their functions) could not, though.
You can always test and revert to stock if you want
Click to expand...
Click to collapse
Okay, thanks for the reply. The warranty on my z2 force is over, so I'll risk installing it following your tutorial. The z2 force is more complicated, but with a little patience I think it will work ...
Latest magisk 17.1 leads to "no wifi and no mobile internet" on pie PixelExperience 9 img (PE-AB-2018-09-20)
Does anybody know how to solve it?
did you get the magisk wifi issue sorted out?
McRoberts said:
did you get the magisk wifi issue sorted out?
Click to expand...
Click to collapse
No. I've tested Magisk v17, beta and also older versions (16.7).
anyone tried and make it work successfully with this guide to follow ?
i check all the replies but no one seem to come back and claim it work .
if you are the one pls let me know , thank you.
fisummer said:
anyone tried and make it work successfully with this guide to follow ?
i check all the replies but no one seem to come back and claim it work .
if you are the one pls let me know , thank you.
Click to expand...
Click to collapse
Yes. it works
mattlowry said:
Yes. it works
Click to expand...
Click to collapse
thanks bro,i really appreciated for your comfirmation.
Related
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
shouldn't you be flashing disable_encrypt zip too?
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
PROdelision said:
shouldn't you be flashing disable_encrypt zip too?
Click to expand...
Click to collapse
No, its not required.
chiplovez9x said:
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
Click to expand...
Click to collapse
Make sure you have allowed modifications on system partition and also you dont have system as read only.
Does fingerprint working on GSI?
what is gsi?
I don't know much but gsi means u can flash almost all roms (which have images). And most of ROMs do have gsi images.. So u can install any rom on your phone. I don't know the steps to do so.. ?
bryanngapopala said:
what is gsi?
Click to expand...
Click to collapse
Simple speaking it's a image with clear android from google
Has anyone tested RR PIE GSI on RN7? Does it work?
Is it possible to boot Android O GSI? :silly:
letsmakecakes said:
No, its not required.
Click to expand...
Click to collapse
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Is the. Method the same for the global version with global rom?
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Which GSI should be needed to take? A-only or A/B ?
PROdelision said:
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Click to expand...
Click to collapse
I have no experience with GSI images, but I know in general that PIE breaks the encryption, if you roll back the security patch level. I don't know it this happened in your case, but I have lost couple of times my encrypted storage when I have tried to restore a backup of rom with older android patch level. After that, the bootup encryption pin is no longer accepted, neither by android nor by twrp, so the only option is to format data to remove encryption and start from scratch.
Were your miui beta and rr gsi of the same android security patch level?
Getting WRONG PIN error after setting up pin ???
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Hi!
Did you not disable dm-verity and force-encryption?
Another question, the dev MIUI roms contain both the system and vendor partitions, right? How do you install only the vendor partitions from them? Or do you just flash MIUI and then reflash the custom ROM system? In that case, won't that affect dm-verity and encryption on the data partition?
Flashing correctly a GSI like in this guide; with vendor ecc ecc, will gcam work? Actually i'm on stock MIUI 10 and obv all working fine with a perfect version. My doubt is it.
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
any recommended gsi rom with no bug?
booladi said:
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Did you not erase your /data partition through TWRP?
Click to expand...
Click to collapse
I did wipe userdata but not internal storage. heard its because i have unencrpyed data partition?
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
Since the Pie update GSIs are not working because of System-as-root partiton But ASUS launched a new update in which GSIs are working.
READ WHOLE THREAD CAREFULLY.
REQUIREMENTS:
Unlocked bootloader (After Unlocking bootloader you will get a Red END OF STATE Warning. Don't Worry Press Power Button on that screen
Decrypted Data
Should be on latest firmware
If You're Using PitchBlack Recovery:
1. Boot into Recovery
2. Click On Advanced > Additional > Special > Setting OTA
3. Uncheck "Disable DM-Verity" Option Here
4. Done, Now You Can Use PitchBlack To Flash GSI on Pie Vendor.
INSTALLATION METHOD:
1. Download Any GSI of A/B type.
2. Download latest magisk manager zip
3. Patch your boot.img with Magisk (Tick on Preserve dm-verity by clicking on Advanced settins in magisk) or Download from Here
4. Boot into Recovery and Wipe Data, Dalvik Cache. Do not wipe system
5. Flash patched boot.img
Note: If your data is Encrypted then This step should be done with pitchblack otherwise your data may remain encrypted
6. Flash GSI image
7. Flash latest Magisk.
8. Go to Wipe option > Select Advanced Wipe > Tick on system > Click on Repair or Resize > Click on Resize.
9. Optional : Flash Gapps According to your choice If Gapps are not included in GSI.
10. Reboot System.
There is a possibility That your device will reboot again after asus logo. Don't worry
HIT THANKS IF I HELPED YOU:good:
do you see the red state warning after booting into gsi
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
jeno33 said:
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
Click to expand...
Click to collapse
Sorry I didn't mentioned in guide, that you've to modify script of gapps to get it working. I'll upload modified gapps tomorrow. Again I apologize
jeno33 said:
do you see the red state warning after booting into gsi
Click to expand...
Click to collapse
Red state warning is due to unlocked bootloader. It'll remain as long as bootloader is unlocked. But that doesn't create any problem except for increasing boot time by 5-6 seconds.
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Updater-script needs to be modified inside gapps, because gapps wrongly detects architecture as arm.
Install this gappshttps://drive.google.com/file/d/1nS2z4emxHovZ0x3CqXl59r8oBqx9DiPU/view?usp=drivesdk
I have modified the script
what rums for example are loaded and working?
currently the Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official is being loaded and running.
tried miui, flyme, Havoc-OS other versions
Is there any video tutorial?
Any tutorial videos?
gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Hey you able to flash any GSI except havoc 2.0 ??
I'm not able to access your document
Hello there. Hope this helps!
FIRST OF ALL, this WILL VOID your waranty. Read the steps BEFORE doing anything.
WEWEWEWE lessgooo:
UNLOCK BOOTLOADER: It's not "easy" at all (You'll have to open your tab).
Go to device info on tab settings.
Press compilation number for several times until "you're a dev" message appears (It'll prolly ask your pattern/password to continue).
Go to dev options and enable OEM unlocking.
Shut down the tab.
Download PotatoNV sofware from here. (Credits to mashed-potatoes)
Download minimal adb and fastboot from here.
Prepare your environment:
Open your tablet
Grab a clip or a cable
Keep your cool
Follow the steps shown here.
Here you have an image of where the testpoint is.
FLASH TWRP INTO THE TAB:
Follow CAREFULLY this steps:
Shut down the tab
Connect the tab to the PC and hold vol- & pwr button.
Now it'll appear a white screen with some text. If it appears "OEM unlock" in green, then everything's fine. IF NOT, follow unlock bootloader steps again. Then try rebooting into fastboot mode again (vol- & pwr).
Download most compatible TWRP from here.
Open Minimal ADB and Fastboot and write this:
"fastboot flash recovery_ramdisk path_of_twrp.img" (Move twrp to minimal adb folder for no complications)
It should appear everything OK.
Type "fastboot reboot"
Fastly disconnect the tab from PC and hold vol+ & pwr button before Huawei logo appears (if it appears, just do a hard reboot (hold pwr button) and try again.
You're now booting into TWRP!
DOWNLOAD RESOURCES AND PREPARE YOURSELF FOR THE PARTY (This is the most important step)
Download data decrypter from attached files below the post (decryptemui8.zip)
Download ROM from here (credits: @DarkJoker360 ) DarkJoker's Post here
(OPTIONAL) Download Nikgapps from here
ONCE in TWRP, flash decrypter (decryptemui8.zip) on "install" option
Go to wipe>advanced wipe and select: dalvink/art cache, cache, data, internal storage and system.
Return to main menu and go to reboot>reboot bootloader
Connect your device to the PC (while rebooting) and wait to be into bootloader (white screen with a droid).
Open minimal adb and fastboot tools and type:
"fastboot flash system path_of_rom.img" (it MUST be decompressed to an .img file)
Wait...
Once it has finished, type: "fastboot reboot"
DONE! you have LOS18.1 now!
(optional gapps on next step)
GAPPS INSTALLATION ON MEDIAPAD T5 IT'S DIFFERENT FROM OTHER PHONES!!!!!!!
FOLLOW THIS STEPS VERY CAREFULLY!!!
Move gapps zip and add-ons to an sd card
Reboot to TWRP
Go to mount>select system. Return to main menu
Go to advanced>file manager
Go to system>system_ext>apex.
Once in apex, enter on vndk27 and vndk28 and delete them (once in vndk27/vndk28 folder, in the bottom-right corner, it'll appear a symbol with a folder with a "tick" on it. Just tap it)
LEAVE ONLY VNDK CURRENT AND VNDK26 FOLDERS (and the rest obviously. Just delete 27/28)
Return to main menu
Go to wipe>advanced wipe. Select system and tap on repair/resize partition (slide to continue)
Then go to main menu>install and install gapps as usual (sliding lol)
FOR ROOT METHOD:
Just follow the steps shown on the main post.
WORKING ROOT CAN ONLY BE DONE WITH MAGISK METHOD (installing apk for using preroot MUST perform random SystemUI reboots ; ).
---------CREDITS---------
Amazing rom: @DarkJoker360
HI6250 support group here.
JOIN T5 SUPPORT GROUP CLICKING HERE
Hey,
I've tried this, but cant get it too boot.
My device is Huawei AGS2-W09.
I've unlocked the bootloader/installed twrp, flashed the decrypter etc.
Then after i do fastboot reboot, it loads up the Lineage OS splash/loading screen, but stays on that for about 10 mins, then reboots and goes to Huawei eRecovery screen.
I've tried repeating the steps, in case it didn't flash properly.
Any ideas?
hobbitjack said:
Hey,
I've tried this, but cant get it too boot.
My device is Huawei AGS2-W09.
I've unlocked the bootloader/installed twrp, flashed the decrypter etc.
Then after i do fastboot reboot, it loads up the Lineage OS splash/loading screen, but stays on that for about 10 mins, then reboots and goes to Huawei eRecovery screen.
I've tried repeating the steps, in case it didn't flash properly.
Any ideas?
Click to expand...
Click to collapse
For those facing problems:
PM Me via telegram @Fosanz
JOIN T5 SUPPORT GROUP
I will post the solutions here on the main post as problems appear
Hello,
I have tried too, and I have had exactly the same problem. I couldn’t boot into system.
I followed all the steps as described. I have AGS2-W09 and I was on Lineage 16.0.
Now I’m back again on Lineage 16.0, waiting if there is a solution.
borja113 said:
Hello,
I have tried too, and I have had exactly the same problem. I couldn’t boot into system.
I followed all the steps as described. I have AGS2-W09 and I was on Lineage 16.0.
Now I’m back again on Lineage 16.0, waiting if there is a solution.
Click to expand...
Click to collapse
Recover system with eRecovery and follow steps again. Instructions modified. Making a factory reset is not neccesary
@Fosanz can you share how's the performance of LOS18.1 on MediaPad T5
what is working and what not?
how is the battery on LOS18.1?
my battery sucked on LOS16, hardly 3 hours
kamilmirza said:
@Fosanz can you share how's the performance of LOS18.1 on MediaPad T5
what is working and what not?
how is the battery on LOS18.1?
my battery sucked on LOS16, hardly 3 hours
Click to expand...
Click to collapse
Everything works. No face unlock as LOS16. Animations are simply beautiful, very optimized. Here you can pass safetyNet with some easy tweaks. Battery it's amazing. 1% in 6h deep sleep. While using it (6-7 hours of gaming, instagram, telegram, etc.) battery drain it's amazing. I'll share some screenshots on the telegram group
Fosanz said:
Recover system with eRecovery and follow steps again. Instructions modified. Making a factory reset is not neccesary
Click to expand...
Click to collapse
Follow steps again….Yes, but what will change if I do it again. Same tablet, same instructions. I would like to know first what was wrong. I want to avoid spending hours trying and after that restoring, until I’m sure it will work for me.
Anybody else managed to install LOS18 ? If yes please describe how you did it and from which environment you’re coming.
Does it work for AGS2-L03?
Or this ROM only work for some Variant?
I think mine only has 16GB storage and 2GB RAM.
Also the eRecovery, does it only update or can it flash the full image?
borja113 said:
Follow steps again….Yes, but what will change if I do it again. Same tablet, same instructions. I would like to know first what was wrong. I want to avoid spending hours trying and after that restoring, until I’m sure it will work for me.
Anybody else managed to install LOS18 ? If yes please describe how you did it and from which environment you’re coming.
Click to expand...
Click to collapse
Join support group duh.
theflyingsquirrel said:
Does it work for AGS2-L03?
Or this ROM only work for some Variant?
I think mine only has 16GB storage and 2GB RAM.
Also the eRecovery, does it only update or can it flash the full image?
Click to expand...
Click to collapse
Yeah it should work. Same processor but different amount of Ram. Try it out! Join t5 (Bottom of the main post) support group if you're facing problems!
Fosanz said:
Join support group duh.
Click to expand...
Click to collapse
OK, so, if anybody wants to try to install L0S18, go right away and join Telegram group of this member, beacuse the suport is not provided here (entendi bien?). What is the purpose of this forum then?
borja113 said:
OK, so, if anybody wants to try to install L0S18, go right away and join Telegram group of this member, beacuse the suport is not provided here (entendi bien?). What is the purpose of this forum then?
Click to expand...
Click to collapse
Debido a que tú pregunta no tiene nada que ver con la instalación, sino que estás preguntando por los cambios hechos, no voy a empezar ni una discusión ni una conversación por un hilo con tal de evitar overflooding de mensajes. Así que por favor y si no te molesta, te asistiré por Telegram, de manera que el problema que tú tengas pueda ser solucionado lo más rápido posible para yo poder modificar lo que pueda estar mal en el hilo principal y así no hacer que la gente que quiere instalar Lineage solo mirando el thread principal (que lo hace la gran mayoría) tenga el mismo error que tú y vuelva a preguntarme lo mismo.
Y si, hay gente que ha logrado instalar Lineage os 18.1 correctamente y gracias a que se unió al grupo pude modificar partes de la instalación que eran cruciales para otros modelos de mediapadt5.
Un saludo
Has anyone else successfully installed LO18? I tried going from LO16 to 18 and this didn't work for me. I'm gonna give it a second try when I have more time on my hands. Maybe I'll have more luck going from EMUI to LO18.
Firts of all thanks for the efford you guys spend into a working solution for our device. Second I apology for not joining Telegram group, I simply don't use it.
Device: AGS2-W09 - came from stock
Yesterday the device was successfully booting into LOS18. Might have to do with the new Huawei-Decrypt file. Before I was also getting a boot loop.
LOS is working quite well as I can tell until now.
Aditionally installed apps (sideloaded or alternative store) are freezing after a while. I suspected a dependency to gapps. The apps I tested Brave Browser, Aurora Store, VLC.
Tried to install Nikgapps (core and then basic) but it didn't work. TWRP console tells me installation was successful, but no gapps appear after the boot. I tired BiTGApps package and that was successful.
Additionally installed apps still freezing after a while.
korale said:
Firts of all thanks for the efford you guys spend into a working solution for our device. Second I apology for not joining Telegram group, I simply don't use it.
Device: AGS2-W09 - came from stock
Yesterday the device was successfully booting into LOS18. Might have to do with the new Huawei-Decrypt file. Before I was also getting a boot loop.
LOS is working quite well as I can tell until now.
Aditionally installed apps (sideloaded or alternative store) are freezing after a while. I suspected a dependency to gapps. The apps I tested Brave Browser, Aurora Store, VLC.
Tried to install Nikgapps (core and then basic) but it didn't work. TWRP console tells me installation was successful, but no gapps appear after the boot. I tired BiTGApps package and that was successful.
Additionally installed apps still freezing after a while.
Click to expand...
Click to collapse
Hey Hi!.
Glad to hear you booted! The problem was at the decrypter.
Also, a lot of people are having trouble installing NikGapps. It seems that the package is "wrong" in some way for our device. Reported the issue. Until July 2021 update, devices go very slow. Hopefully, there's a way to fix it .
adb root && adb remount /system
adb push local.prop /system/product/etc/prop/local.prop
Credits to @DarkJoker360
Extracted from HI6250 support group
local.prop file is on "attached files"
I finally had some time to try installing LineageOS 18.1 again. Works beautifully, Magisk and everything. Make you sure you go straight from EMUI to LineageOS 18.1, it doesn't work if you switch from Lineage 16 to 18.1.
In my case I needed to open to the tablet again after doing a Huawei system restore back to EMUI, it relocked my tablet, just be aware of that, that was mildly annoying.
Also make sure you use the Magisk mentioned in the thread if you want root. After installing, don't let Magisk update itself from within the app, updating the ramdisk will remove TWRP and the system will bootloop until you reflash TWRP. It will boot again normally with your stuff still intact after the TWRP reflash.
Been playing around with it for a bit, doesn't seem to have some of the annoying LineageOS 16 bugs. It has full screen navigation controls which I really wanted and was missing earlier. Android 11 (Juli 2021 security update), MicroG is working, seems responsive and smooth. Great! I am very happy with this.
Thanks and special shout out to all the people making this possible, y'all are amazing.
Just as a hint. I don't think you need to open your tablet again.
Keep the unlock code generated by PotatoNV save. In my case I relocked and unlocked the tablet several times with the unlock code without the testpont method.
hi, i just got to the part that i have to make a img file out of the rom zip file....
help pls
can i flash the other img files on the site? (the 650 mb files)
can i flash the new rom from twrp?
thx
kamilmirza said:
@Fosanz can you share how's the performance of LOS18.1 on MediaPad T5
what is working and what not?
how is the battery on LOS18.1?
my battery sucked on LOS16, hardly 3 hours
Click to expand...
Click to collapse
Fosanz said:
Hello there. Hope this helps!
FIRST OF ALL, this WILL VOID your waranty. Read the steps BEFORE doing anything.
WEWEWEWE lessgooo:
UNLOCK BOOTLOADER: It's not "easy" at all (You'll have to open your tab).
Go to device info on tab settings.
Press compilation number for several times until "you're a dev" message appears (It'll prolly ask your pattern/password to continue).
Go to dev options and enable OEM unlocking.
Shut down the tab.
Download PotatoNV sofware from here. (Credits to mashed-potatoes)
Download minimal adb and fastboot from here.
Prepare your environment:
Open your tablet
Grab a clip or a cable
Keep your cool
Follow the steps shown here.
Here you have an image of where the testpoint is.
FLASH TWRP INTO THE TAB:
Follow CAREFULLY this steps:
Shut down the tab
Connect the tab to the PC and hold vol- & pwr button.
Now it'll appear a white screen with some text. If it appears "OEM unlock" in green, then everything's fine. IF NOT, follow unlock bootloader steps again. Then try rebooting into fastboot mode again (vol- & pwr).
Download most compatible TWRP from here.
Open Minimal ADB and Fastboot and write this:
"fastboot flash recovery_ramdisk path_of_twrp.img" (Move twrp to minimal adb folder for no complications)
It should appear everything OK.
Type "fastboot reboot"
Fastly disconnect the tab from PC and hold vol+ & pwr button before Huawei logo appears (if it appears, just do a hard reboot (hold pwr button) and try again.
You're now booting into TWRP!
DOWNLOAD RESOURCES AND PREPARE YOURSELF FOR THE PARTY (This is the most important step)
Download data decrypter from attached files below the post (decryptemui8.zip)
Download ROM from here (credits: @DarkJoker360 ) DarkJoker's Post here
(OPTIONAL) Download Nikgapps from here
ONCE in TWRP, flash decrypter (decryptemui8.zip) on "install" option
Go to wipe>advanced wipe and select: dalvink/art cache, cache, data, internal storage and system.
Return to main menu and go to reboot>reboot bootloader
Connect your device to the PC (while rebooting) and wait to be into bootloader (white screen with a droid).
Open minimal adb and fastboot tools and type:
"fastboot flash system path_of_rom.img" (it MUST be decompressed to an .img file)
Wait...
Once it has finished, type: "fastboot reboot"
DONE! you have LOS18.1 now!
(optional gapps on next step)
GAPPS INSTALLATION ON MEDIAPAD T5 IT'S DIFFERENT FROM OTHER PHONES!!!!!!!
FOLLOW THIS STEPS VERY CAREFULLY!!!
Move gapps zip and add-ons to an sd card
Reboot to TWRP
Go to mount>select system. Return to main menu
Go to advanced>file manager
Go to system>system_ext>apex.
Once in apex, enter on vndk27 and vndk28 and delete them (once in vndk27/vndk28 folder, in the bottom-right corner, it'll appear a symbol with a folder with a "tick" on it. Just tap it)
LEAVE ONLY VNDK CURRENT AND VNDK26 FOLDERS (and the rest obviously. Just delete 27/28)
Return to main menu
Go to wipe>advanced wipe. Select system and tap on repair/resize partition (slide to continue)
Then go to main menu>install and install gapps as usual (sliding lol)
FOR ROOT METHOD:
Just follow the steps shown on the main post.
WORKING ROOT CAN ONLY BE DONE WITH MAGISK METHOD (installing apk for using preroot MUST perform random SystemUI reboots ; ).
---------CREDITS---------
Amazing rom: @DarkJoker360
HI6250 support group here.
JOIN T5 SUPPORT GROUP CLICKING HERE
Click to expand...
Click to collapse
Thx alot for the guide and the help in instegram.
It's working for me with my mediapad t5.
Some things that are still a bit dissfunction:
Mobile network dissconnect every 30 seconds and reconnect.
No support for sd card (can't format it in the tablet).
Thanks again,
Ilan
Hey!
I unlocked the phone (LLD-L31) with PotatoNV and installed TWRP 3.2.1-0 (from this page: https://ministryofsolutions.com/2020/03/honor-9-lite-emui9-1-twrp-and-root-lld-l31-l21-l22-al10.html), so far so good.
Now I found LOS 18 and 19 (testing) for this device: https://sourceforge.net/projects/andyyan-gsi/
But the sideload doesn't work.
Error: insufficient permissions for device.
I can see the phone via 'adb devices' (in the main menu of the TWRP)
BUT if I start adb sideload in TWRP I get no permissions.
tried sudo, but with the same result.
best regards
lay
#Edit1:
I restarted the adb server with as sudo
adb kill-server
sudo adb start-server
Now it shows Total xfer: 0.00x and breaks.
I think it has something to do with the img.xz files.
I just deleted the xz and tried to sideload it as img.
#Edit2:
ok, the ISOs are compressed.
'unxz blabla.iso.xz'
But the same result: Total xfer: 0.00x and breaks
Simply flash image in fastboot
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
-Alf- said:
Simply flash image in fastboot
https://forum.xda-dlinelineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgeveloplineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
Click to expand...
Click to collapse
THANKS!
so it works via 'sudo fastboot flash system blabla.img'
So... LineageOG 19 (testing) gets 'invalid sparce file format at header magic' while flashing, but installes then everything, after that, it's hanging.
After that I tried this step from the link above:
"4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot ."
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP. If I reboot then in eRecovery, I get to LineageOS 18. For my understanding.... VERY strange!
The LineageOS boots and boots and boooooots now...
#Edit1:
tried now the ROMs from your link.
18.1 shows 'invalid sparce file format at header magic' and fails on install.
17.1 without GAPPS succeeds the flashing, but did not reboot in eRecovery, but the TWRP. There I did the same (wipe data, cache, davlik / factory reset) with the error 'unable to wipe cache'.
and it also does NOT boot the system, but TWRP without touchscreen
#Edit2:
I think the phone is dead
maby because of the TWRP wiping the data
The strange thing is, I can still write to the system partition and flash another LineageOS. But it never reboots to system, just to TWRP (in TWRP I can not mount 'system')
#Edit3:
I can not even reboot to fastboot. It always boots the TWRP
#Edit4:
formated (repaired) system in ext4 again
Now it can be mounted, but I can not get to fastboot-mode and get no device via adb.
I can just boot to eRecovery now. So I try the only one thing, that is there: recovery via wifi. It's downloading now the EMUI 9.1. So we'll see.
It's just crazy!
layalala said:
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP
Click to expand...
Click to collapse
Your problem is that you don't read carefully.
Why do you have TWRP installed???
layalala said:
It's just crazy!
Click to expand...
Click to collapse
Indeed!
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
The point is, I got it!!!
After downloading new EMUI via wifi in eRecovery, I got everything back. Meanwhile my VM in the QubesOS did not want to accept the USB-Controller I used for adb-fastboot. So i switched to Windows and followed your tutorial. BUT with the ROMs from Andy Yan (https://4pda.to/forum/index.php?showtopic=896420&st=10780#entry100487186). And everything works! Even the testing LOS 19! Android 12 on that old phone, yeah! but it works rather good.
Your ROM (LOS 18.1) did not work for me. It showed error in header while flashing and broke the process. The ROM from Andy Yan (LOS 19) also showed an error in header while flashing, but the process worked after that.
now I'll try to root it and hope that this will work well
layalala said:
now I'll try to root it and hope that this will work well
Click to expand...
Click to collapse
did rooting succeed?
epicmann24 said:
did rooting succeed?
Click to expand...
Click to collapse
yes!
layalala said:
yes!
Click to expand...
Click to collapse
may i ask which gsi image and which magisk zip did you flash? as for me rooting does not work.
epicmann24 said:
which magisk zip did you flash
Click to expand...
Click to collapse
Running EMUI 9.1 you have to flash magisk_patched recovery_ramdisk (on EMUI 9.1 ramdisk is included in the recovery_ramdisk).
Also you can follow this guide:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
You can use files linked in this post, recovery_ramdisk and erecovery are the same for ANE and LLD devices. Use TWRP linked on this post (important!).
Edit: you can get root rights also via SuperUser:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed)
https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
layalala said:
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
Click to expand...
Click to collapse
Hello,
Everything worked; even to the Lineage 19 rom, but, I couldn't install OpenGapps 12l (error 70).
I tried to replace the system "LOSQ - LineageOS 17.1-[10]-unofficial-GSI" via TWRP (system install) and I had the same problem, in addition to not being able to boot by eRecovery to download EMUI by Wi-Fi.
also, on TWRP, I don't have the option to mount "system"
How did you do?
[2022/07/06 - EDIT]
--> eRecovery done
--> Download in progress
--> EMUI 9 Install done
--> go test lineage 18.1 first
Rahinsoo said:
I don't have the option to mount "system"
Click to expand...
Click to collapse
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
-Alf- said:
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
Click to expand...
Click to collapse
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Rahinsoo said:
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Click to expand...
Click to collapse
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
-Alf- said:
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
Click to expand...
Click to collapse
Can I use this version without particular problems on my honor 9 lite?
Rahinsoo said:
Can I use this version without particular problems on my honor 9 lite?
Click to expand...
Click to collapse
Read carefully.
Oh, I'm sorry, I misunderstood ^^'
my question was for the vndklite version because I'm having a hard time figuring out the difference.
Rahinsoo said:
my question was for the vndklite version
Click to expand...
Click to collapse
I answered you, didn't I?
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Rahinsoo said:
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Click to expand...
Click to collapse
Why do you have TWRP there? You don't need it to install GSI. And if you have TWRP installed instead of Recovery, then it should be clear...