Related
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
Guys I successfully installed HAVOC-OS located https://forum.xda-developers.com/project-treble/trebleenabled-device-development/gsi-havoc-os-t3930030. The steps I followed are mentioned below
1. Wipe everything except internal storage.
2. Flashed BRK3 Vendor https://mega.nz/#F!wFFQUYbI!GZvNOBSn1wVn8U9mQDzBiw!IQsjlYzA
2. Installed Endurance GSI kernel https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/kernel-endurance-kernel-v1-0-t3849434
3. Flashed the system image for ARM 64 A only
4. Boot system
5. Reboot to recovery and Flashed Mgisk
6. Gapps will fail to install at first. Just goto wipe -> Adv wipe -> system partition -> Resize. Reboot to recovery and flash Gapps
7. Reboot and enjoy
8. You can test other GSI Roms also and report. The thread is located at https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Thanks buddy. I was looking for the ways to run the GSI. And the method works. Good job
thanks for the guide! im still on an unrooted s9, but if everything works ill definetly make the jump. Can you tell us more about stability, bugs and if there are things not working
So after testing the ROM for 2 days I can say that
1. It is very stable and can be used as a daily driver
2. Everything works, I am not sure about Bluetooth audio though, haven't checked it
3. It can be heavily customized. Unlike LOS, where we have only few of these features available
4. Battery life is the best I got using any other ROM out there (check the screens below). and I am the guy who gets 3 hrs of SOT, when others claimed 5+ hrs on the same ROM.
5. Security patch is latest even as compared to the TW ROMs
6. Regarding camera... Its the same as LOS pie. Use gcam by idan 3.5 fixed and you are good to go.
fingerprint working?
andreMusers said:
fingerprint working?
Click to expand...
Click to collapse
Yes it is
Thanks for trying this out. I'm only a few months in with my exynos S9 on android pie, so I haven't yet learned the details about rooting/recovery for this phone.
I'll wait for your next update regarding daily use, and would love a more detailed step-by-step for installation if that's not too much trouble. I'm honestly loving those screenshots.
How about IMEI, BRK3 Vendor safe..?
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Thanks for the extra instruction man, will test this out soon.
burninitup said:
Ok here is the detailed tutorial on how to install a GSI rom
1. First you need to wipe everything in TWRP. Just like you do, when you clean flash any rom
2. Than install the BRK3 vendor. Link is provided by the OP. It's a flashable zip file so just flash it like any other zip.
3. Flash the Endurance GSI kernel. Link is in the OP.
4. Next, download the GSI rom from the link in the OP. Remember to download the ARM 64 A-only variant.
5. Extract the files and you should get a . Img file. Copy that in the SD card
6. In the TWRP, goto install. Select flash image from the bottom right corner of your screen. Now browse the image file, that you copied and choose system image and install.
7. Boot to the system and than boot back to the recovery.
8. Now flash the magisk
9. If you try to install gapps, it will give an error regarding space. So just goto wipe -> advance wipe > system repartition > resize
After resize, you will be able to install gapps.
Flash gapps, automatic brightness fix ( link in the rom thread), AOD fix ( link in the rom thread) and reboot.
Click to expand...
Click to collapse
Doesn't work. Stuck on boot logo, loading forever.
Zwulf said:
Doesn't work. Stuck on boot logo, loading forever.
Click to expand...
Click to collapse
me too dont know any fix
EDIT: Somehow i managed to boot the rom but sim won't get detected
Double tap and AOD - work correctly? On snap it does not work well
My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected
Masterofchicken said:
My Baseband version is now unknown
I have an SM-G960F and its german
EDIT:I just flashed the latest firmware from soldier and now sim card gets detected
Click to expand...
Click to collapse
So camera isn't working ,root is still present with magisk and i couldn't disable it with the adb command so safetynet doesn't pass ,i'll say it's not really usable ?
Has anyone found a fix for getting stuck at the s9 logo?..wanting to move to GSI ROMs
I have tried this,
After flash GSI rom, reboot recovery, reboot system and I have bootloop with the first logo Galaxy S9. Can anybody please help me?
@arunrawat2112
Finally I was able to flash some roms but none of them work properly. Can you please help me?
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
Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much
Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com
Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again
It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.
Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...
Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article
nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again
Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Maybe I have to try with sideload ?
Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.