Database Info

[A-ONLY][TREBLE][8.0][A530F/A530W/A730F]Vendor Oreo For Galaxy A8/A8+ 2018

VENDOR FOR GSI (Generic System Image)
I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Bevice By This Guide here​ If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal ​
Just to Make it clear, Treble Vendor for A8/A8+ is been ported from A7 2018 Oreo. We have tested many Oreo GSI from phhuson generic list and they are booted with this vendor. We have also tested Pie GSI, most of them didn't booted but few did(Phh-AOSP-9.0).
What is GSI?
A Generic System Image (GSI) is a system image. It is considered a "pure Android" implementation with Android Open Source Project (AOSP) code that any Treble device can run successfully. For more info visit here : https://source.android.com/setup/build/gsi
What is working?
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
2D/3D Graphics + Vulkan
What is not working?
VoLTE
**Important: Vendor attached to this thread is stable, If you find any bugs on GSI, report it to their respective maintainer's with logs.
Instructions
1- Make Sure u Treble your device
2- Wipe System, Vendor, Data, Cache
3- Flash Vendor-Installer.zip (includes Kernel)
4- Flash GSI as system_image on TWRP
5- Reboot and start using your device
Downloads. Changelogs below
Credits
IF you helped in this project and i forgot you, tell me in a PM or in a reply
@corsicanu for repartition help
@lzzy12 , @TaifAljaloo , @Griffin98 , @somadsul , @ananjaser1211 for lot of contributions and helping to fix bugs
@enesuzun2002 , @neondragon1909 for helping to fix FP and NFC
@587.saboor for testing
XDA:DevDB Information
Project Treble, Vendor for Samsung Galaxy A8 / A8+ 2018
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: v1.0
Created 2019-02-12
Last Updated 2019-02-12

Download
Vendor-Installer For Android 8.1 / 9.0 GSIs (includes Kernel)
You can download an A only ARM64 GSI from here
OpenGapps
Fix for bugs
Camera Fix
Fingerprint Fix
Changelog
V1.0
-initial release

reserved 2

Massive thanks to you guys !

Instructions
1- Make Sure u Treble your device
2- Flash Vendor-Installer.zip (includes Kernel)
3- Flash GSI as system_image on TWRP
4- Reboot and start using your device
bro after no. 1 am i wipe chache dalvik system and vendor and go to no. 2?

freemod said:
Instructions
1- Make Sure u Treble your device
2- Flash Vendor-Installer.zip (includes Kernel)
3- Flash GSI as system_image on TWRP
4- Reboot and start using your device
bro after no. 1 am i wipe chache dalvik system and vendor and go to no. 2?
Click to expand...
Click to collapse
Yes, u should wipe first

any screenshots?

Is this the same vendor as in this thread (but it's only the vendor here), or are there any differences? (if this is any better/different, can I "upgrade" to it without wiping my existing phh-treble install?)

Gabriel529 said:
any screenshots?
Click to expand...
Click to collapse
This is not a ROM, just a Vendor which lets you flash GSI ROMS. Therefore, no screenshots could be given.
VDavid003 said:
Is this the same vendor as in this thread (but it's only the vendor here), or are there any differences? (if this is any better/different, can I "upgrade" to it without wiping my existing phh-treble install?)
Click to expand...
Click to collapse
It's not the same, he fixes a lot of things to make it stable now (as NFC or Camera). About your installation question, I don't know.

ROM
Good night my friend. I wonder if using this increases the possibility of being compatible with other Roms, or does it basically equal to TWRP treble and creator treble equal to what you have here on another topic? If the answer is that it increases the possibility of roms compatible, can I do the installation over the other version creator and twrp treble? Sorry the English.

To anyone wondering: I've managed to replace my existing vendor+kernel by flashing the zip and suprisingly I had to remove the pattern lock from my phone and re-add it because system ui just chrashed every time I entered my pattern. Note: I'm on AOSP Phh-treble 9.0 V109 (I know V110 is already out but I'm lazy..)
Also I had to reflash magisk but that's expected after a new boot img.

Hi,
thank you so much for that vendor base. Everything seems to be ok, except one thing though : MTP does not work if i activate usb debugging. Is this vendor or gsi related ? btw i tried the four gsi you recommend in your original post, same behaviour. I'm on sm-a530f
Nice week end to all.

VDavid003 said:
To anyone wondering: I've managed to replace my existing vendor+kernel by flashing the zip and suprisingly I had to remove the pattern lock from my phone and re-add it because system ui just chrashed every time I entered my pattern. Note: I'm on AOSP Phh-treble 9.0 V109 (I know V110 is already out) but I'm lazy..
Also I had to reflash magisk but that's expected after a new boot img.
Click to expand...
Click to collapse
I didn't get u , also why r u using old builds, always go with the latest which includes fixes
cedlefou said:
Hi,
thank you so much for that vendor base. Everything seems to be ok, except one thing though : MTP does not work if i activate usb debugging. Is this vendor or gsi related ? btw i tried the four gsi you recommend in your original post, same behaviour. I'm on sm-a530f
Nice week end to all.
Click to expand...
Click to collapse
Thanks for the complement, issues related to mtp and usb debugging is because of magisk..... just report it to magisk developer with proper logs

prashantp01 said:
I didn't get u , also why r u using old builds, always go with the latest which includes fixes
Click to expand...
Click to collapse
It's just that I only checked the xda thread for phh treble and that still has v109 as the newest. (On github there is a v110 build) and I'm just lazy to upgrade, since this version is good for me.
About the thing, idk what you didn't get.
Anyways, great work!

Someone can post any screenshot?

Asop extended

mchlbenner said:
Asop extended
Click to expand...
Click to collapse
Here in my those rom based on Android 9, the video call of whatsapp hangs. Does this bug also occur?

VDavid003 said:
To anyone wondering: I've managed to replace my existing vendor+kernel by flashing the zip and suprisingly I had to remove the pattern lock from my phone and re-add it because system ui just chrashed every time I entered my pattern. Note: I'm on AOSP Phh-treble 9.0 V109 (I know V110 is already out but I'm lazy..)
Click to expand...
Click to collapse
How reliable is it? Is there any major bugs? How is battery life compared to OEM firmware?

How can I flash a .img.xz file?
edit: its an archive lol

mchlbenner said:
Asop extended
Click to expand...
Click to collapse
hello . are u can use fingerprint in aosp extended?

[UNOFFICIAL][11] LineageOS 18.1 w/ microG patch for Pixel 4a (sunfish) (20210610)

Introduction
This is my personal build of LineageOS 18.1 for Pixel 4a with the microG patches applied. If you do not want / need to use microG, it may be a better idea to use the official build available here: https://download.lineageos.org/sunfish. This build is exactly the same as the official build except for the microG patch.
For discussion about the official build, please use the other thread instead: https://forum.xda-developers.com/t/rom-official-sunfish-lineageos-18-1.4255751/
Installation
Before installation, make sure your phone is updated to Android 11 firmware on both of the slots.
Whether you are installing the ROM for the first time or updating the ROM, please make sure you reboot to recovery again after `adb sideload`-ing the ROM before installing add-ons such as Magisk and GAPPS.
1. Download `boot-XXXX.img` (this contains the recovery needed for initial flashing)
2. Download `lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip`
3. Reboot your phone to fastboot mode
4. Run `fastboot flash boot boot-XXXX.img` from your PC
5. Reboot your phone into recovery mode (`fastboot reboot`, then press volume up immediately)
6. Erase data
7. Select Apply Update -> Apply Update from ADB
8. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
9. If you do not need to install any add-ons (e.g. Magisk or GAPPS), then just reboot into system
10. Otherwise, if you do need to install add-ons, reboot into recovery again (this puts your phone into the recovery of the newly-installed system), then install the add-ons using sideload. If you want to use GAPPS, they must be installed here before you boot into system for the first time (this doesn't apply to microG).
11. Enjoy
Updating
1. Download the newly released zip and reboot your phone into recovery
2. Select Apply Update -> Apply Update from ADB
3. Run `adb sideload lineage-18.1-XXXX-UNOFFICIAL-petercxy-sunfish.zip` and wait for installation to finish
4. If you did not have any add-ons installed before update (e.g. Magisk or GAPPS), then just reboot into system
5. Otherwise, if you did, you need to reboot into recovery again at this point before rebooting to system and re-flash every single one of the add-ons you had before. If you do not re-flash them before rebooting to the new system, the boot will fail and your phone will switch back to the old system automatically.
6. Reboot and enjoy.
Note: You don't need to update official firmware manually while LineageOS is installed by flashing latest official factory images. This LineageOS build now ships with latest official firmware updates which are tested to work with the ROM. Please avoid flashing the firmware manually while LineageOS is installed to avoid unnecessary issues.
Known Issues
- Use Magisk v21.4 or later if you want Magisk
- Some applications require microG to be installed in system partition to function, in which case you can consider using the Magisk microG module
- The eSIM manager only works with either GAPPS or microG installed. Without them, you can use eSIM, but you will not be able to add / remove / rename / disable your eSIM. The eSIM manager will also crash once or twice on first boot without GAPPS or microG, but after that it won't crash anymore (the system automatically disables it until you install microG or GMS)
- Disabling / Enabling eSIM may hang even with GAPPS or microG. However, rebooting normally fixes the issue and makes your action effective.
- I provide no guarantee for SafetyNet status or compatibility with any app that requires SafetyNet. Google has been tightening its SafetyNet verification and there is really not much we can do about it, and frankly most apps that require SafetyNet should not have done so in the first place. If you need SafetyNet, you are on your own.
Downloads
Note: This build has compatibility issues with MindTheGapps (just like the recent LineageOS weekly builds). It will be fixed in newer official weekly builds, but since this build is for microG users, I am not going to upload a new microG-patched build just to work around a GAPPS compatibility issue.
20210610: June 05 security update; sorry for the delay, LineageOS had some issues while merging this month's ASB.
This update also fixed some long-standing bugs, such as the initial crash dialog of the eSIM manager (when GAPPS or microG is not installed), and the extraneous battery percentage option in settings -> battery. Read the LineageOS changelog for the full update.
- boot-20210610.img: https://mega.nz/file/TVolEYKL#MrJH-AVk37JDc_iKCVJ2lFGgFLG9czrE4FnJokbjnqI
- lineage-18.1-20210610-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/uYw30SxT#CwWc0GwqMYoAT54TJqPK2U7M8Y3OzhbpPuvejkOB65o
20210507: May 05 security patches
- boot-20210507.img: https://mega.nz/file/rcJVHQYZ#KjFu84Wnqdx4Rq0fd6TZUlJuaD-RXFXmMCJM4V4z0Tc
- lineage-18.1-20210507-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/jYBTESqZ#ZRc7CkUt8aUYgZRLpF6S1_LHdUXwcUOKPsCBorcYZ1w
20210410: April 05 security patches
- boot-20210410.img: https://mega.nz/file/eYggCKba#l7QJUMkvyEBtyptVMmWVbXochJKmY__X4VIwTla1KqE
- lineage-18.1-20210410-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/bUpQhAQJ#uTe-2nHLKYsfFBKuJg0VAYISUCGMTbIpaC9qjEHFZ1c
20210308: March 05 security patches and official firmware / binary updates.
- boot-20210308.img: https://mega.nz/file/WIZxjAwA#P77ZdJ2YEed5WWmlijKcyRMLJ30KG36eL0mhQGjZWjI
- lineage-18.1-20210308-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/eRBTkYzC#iNZUA84XR80V1so7YvjQ7TyJuZKGY9BZf-MGRtgQOH8
20210222: Updated sources; Removed some non-functional LiveDisplay features; Switched to using Google's wifi_ext HAL; Reserved more space in system partitions for potentially larger GAPPS packages
- boot-20210222.img: https://mega.nz/file/KVxRDY6L#7l7oejw-XEd_m1BUdp0_Z2TyHVLE2KkaGQ6g7Op7dpk
- lineage-18.1-20210222-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/mUgzGSbC#88q95qVsI-7RJsecM8L2MHZ6EwNXrs54Xk6yi428rjU
20210207: Updated LineageOS source; Applied 2021-02-05 security patches; Added support for glove mode; Enabled support property for Google Assistant; Optimized vibration
- boot-20210207.img: https://mega.nz/file/aZxlDKgC#_9VR2ruCYUqmX8gLCBKX1KSMAsBYFDsLA6utk5EjB-g
- lineage-18.1-20210207-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/yZpFQQRJ#PZlNYzI2t2fZdf1T3v6pMRi1zJe7J26f-Eu_Pohm7p4
20200118: Updated LineageOS source; Attempted to fix GAPPS bootlooping issue
- boot-20210118.img: https://mega.nz/file/ONYSRLKC#FhRYEhfsBndqcrJrhd1F4Tv3uu3UZNDYnQe3EcrMyC0
- lineage-18.1-20210118-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/3VRgwZQQ#ynCPIDbW42hXvBWp8MoG-R9eEEzvnaQ649ULZM8lrAc
20210109: Updated LineageOS sources and updated build fingerprint to January.
- boot-20210109.img: https://mega.nz/file/qU5T2CLY#A7dkDfRS0gUaKzphT2_mm0IHW9_-3cIR76yvNV1Cs4A
- lineage-18.1-20210109-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/GNwyxb4S#UGHclk8p60QuRWrGl3LI-Hur9X_VKF46tBNfuD0Z9-o
20210107:
1) Synchronized LineageOS updates and AOSP Jan 5 security patch
2) The ROM now ships with latest official firmware, so you won't need to worry about updating firmware separately (you still need latest official firmware when installing the ROM for the first time though)
- boot-20210107.img: https://mega.nz/file/OYRnwaII#3Ipj99mG5tpXouRRKMqWDJmimH8U2q5mZ5LKj8ZEmdo
- lineage-18.1-20210107-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/aEBTFAwK#EM3fKYQG4Y2najLhRkZlPqDwPSwkV-yfsSlH7Za7UYM
20201229: Synchronized LineageOS updates and fixed biometric authentication (fingerprint) in third-party applications.
- boot-20201229.img: https://mega.nz/file/yMow3aDb#ByY4yG6LeAquqBd2vu2UnZUz2xukHYjWbIfXnlkT_XM
- lineage-18.1-20201229-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SA5WDAZQ#fMRB9w4LLSxSAGxHOtEmN9gRBTmrnF8ozKawM34cIxU
20201227:
- boot-20201227.img: https://mega.nz/file/6cI3lKKK#p8Nq3jUOsOoPDeV6yPj4hQtXGIHu8-D54_g3gkzdi0w
- lineage-18.1-20201227-UNOFFICIAL-petercxy-sunfish.zip: https://mega.nz/file/SdQnTaBa#83JjZojOS9JCRdYOng6Y0LLoUl8StAdrwsTbCSqAMhs
Sources
Device Tree: https://github.com/PeterCxy/android_device_google_sunfish
Kernel: https://github.com/PeterCxy/android_kernel_google_sunfish
Thanks: DirtyUnicorn sunfish contributors, SuperiorOS sunfish contributors, LineageOS coral contributors and the LineagOS community.

After some trial and error I got it up and running. After booting the ROM I returned to recovery, factory reset then side loaded Razorloves micro gapps.
Thanks for the build

Nice! Appreciate the work you've done on the trees!
@PeterCxy what vendor do you use? Can I clone it? Or should I extract myself?

Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?

ny-hardcore said:
Nice! Appreciate the work you've done on the trees!
@PeterCxy what vendor do you use? Can I clone it? Or should I extract myself?
Click to expand...
Click to collapse
I pushed the vendor blobs I extracted on my GitHub at https://github.com/PeterCxy/android_vendor_google_sunfish, but you can also extract it yourself as I have also pushed my full sunfish-proprietary-files{,-vendor}.txt

This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17

xeropressence said:
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
Click to expand...
Click to collapse
Unfortunately I have zero clue about this, and I don't live somewhere Call Screening is supported in the first place. This would probably need to be figured out by someone other than me :/

EggZenBeanz said:
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
Click to expand...
Click to collapse
Yes you can, but that flash-all script only flashes it on one slot, so to guarantee you have A11 on both slots you'd still need to manually switch the slot and execute that script a second time. The reason why you need A11 on both slots is that the recovery installs the new ROM to the inactive slot, so if the inactive slot is not also on A11, the ROM will probably not boot properly.

PeterCxy said:
Yes you can, but that flash-all script only flashes it on one slot, so to guarantee you have A11 on both slots you'd still need to manually switch the slot and execute that script a second time. The reason why you need A11 on both slots is that the recovery installs the new ROM to the inactive slot, so if the inactive slot is not also on A11, the ROM will probably not boot properly.
Click to expand...
Click to collapse
Thank you

EggZenBeanz said:
This is amazing, thanks @PeterCxy
Where the instructions state to be on A11 on both slots does that mean I can do a flash-all with the latest A11 factory image? Currently on LOS 17
Click to expand...
Click to collapse
You could just sideload the ota after booting the factory image as well.[/QUOTE]

10 hours so far and everything is smooth, great ROM, but I've noticed the battery consumption is less on SuperiorOS, need couple of days to confirm.

xeropressence said:
Gave this a shot, everything seemed to loadup fine. Wasn't able to get call screen to show up tho, I flashed razorloves gapps, anything to do to get that to work?
Click to expand...
Click to collapse
Considering call screen doesn't work on other Lineage pixel ROMs, this wouldn"t be any different.

Thank you very much @PeterCxy
I flash-all latest december 11 images and --set-active= slot to other partition and re flashed again. Following the instructions I now have LOS18 with micro-g running. Awesome! I would be interested in any builds with micro-g patches even when/if sunfish goes official LOS

Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps

EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com

jawz101 said:
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
Click to expand...
Click to collapse
I don't use play services, but biometric unlock like autofill I think doesn't rely on play services, its part of AOSP? Both my Tab S5e and previous pixel 4a builds were LOS17 with no google services or microg installed and I have Biometric support in all usual apps

jawz101 said:
Do you have Play Services on it? I assume they use the Biometric API for that feature. And I assume that requires Play Services. Or a locked bootloader, some Trust Zone thing... basically it probably isn't designed to work on a ROM that doesn't have some integrity check or secure thingy access.
info:
Login with Biometrics on Android | Android Developers
In this codelab you will add biometric authentication to your app as part of your login process. You will not replace your current login process – users can still log in with their account password. Instead, you will augment your login process, giving users the convenience to not have to...
developer.android.com
Click to expand...
Click to collapse
I noticed the same issue with bitwarden, never had this issue before

EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
hmmm it's also not available in my Keepass2Android. I'll look into this later -- I don't think fingerprint support is part of Play Services.

EggZenBeanz said:
Biometric/fingerprint unlock is not available in any apps like Bitwarden, wirex etc. Has this feature been removed in A11?
I have a working fingerprint and pattern unlock working on the phone, just no options in any usual apps
Click to expand...
Click to collapse
It might be an issue with the LineageOS source tree when I last synchronized. I checked some of my other devices with LOS built on the same date and they all don't have the fingerprint option available in apps.

PeterCxy said:
It might be an issue with the LineageOS source tree when I last synchronized. I checked some of my other devices with LOS built on the same date and they all don't have the fingerprint option available in apps.
Click to expand...
Click to collapse
I came from this build, https://forum.xda-developers.com/t/lineage-18-android-11-for-pixel-4a-sunfish.4199889/
And there it worked fine
I first installed with MicroG, then went with Gapps, and neither work

Question Does the X3 Pro support project treble?

I'm looking into buying a Poco X3 Pro in the next few days and I'm wondering if I could try loading a Havoc OS GSI onto it once there's a twrp for it. I really don't like mi ui lol.

Our phone seem to work well with gsi roms. I have tried Havoc, Crdroid and Caos. They are all successfully flashed via fastbootd. One common bug of these gsi roms is broken sound but they can be fixed by installing Viper4Android through Magisk. Get the arm64-bgN-userdebug (with gapp and magisk supported) version. The link for havoc-arm64-bgN-userdebug.img is https://sourceforge.net/projects/braiagsi/files/HavocOS/4.3/ .
I have been using Havoc as my daily driver. It is stable and smooth and no bug (except dt2w not working which is a feature not bug) noticed so far for my type of usage.

hey @jngiag, would it be fine if you could give just a brief steps on how to flash one of these roms?​

xelrix said:
hey @jngiag, would it be fine if you could give just a brief steps on how to flash one of these roms?​
Click to expand...
Click to collapse
Sure. This is what I have done:-
1) OrangeFox Recovery -> format data
2) In Pc
./fastboot devices
./fastboot reboot fastboot
./fastboot erase system
./fastboot flash system havoc-arm64-bgN-userdebug.img
./fastboot flash boot boot_magisk.img (boot_magisk.img prepared separately)
./fastboot reboot
3) Fix
a) Magisk -> Update magisk
b) Fix “Device is not Play Protect certified”
-> install Device+ID.apk -> get Google Service Framework (GSF)
-> Go to Google’s Device Registration page here and type your GSF ID on the Android ID box and tap Register
c) Viper4Android -> Magisk -> flash ViperFX_Android11.zip -> flash Ainur Narsil
-> Setting -> Phh Treble Settings -> Qualcomm features -> use alternate audio policy (optional for better sound)
d) Refresh Rate Setting -> Qualcomm features -> Misc features -> Force FPS -> [email protected] (optional)

I just flashed HavocOS "bvN" version (minimal). God it's fast without all this crap from xiaomi and google. I can confirm it works as far as I could check for now.
I just wonder - can HavocOS be auto updated ? I haven't found any updater in the OS itself.

jngiag said:
Our phone seem to work well with gsi roms. I have tried Havoc, Crdroid and Caos. They are all successfully flashed via fastbootd. One common bug of these gsi roms is broken sound but they can be fixed by installing Viper4Android through Magisk. Get the arm64-bgN-userdebug (with gapp and magisk supported) version. The link for havoc-arm64-bgN-userdebug.img is https://sourceforge.net/projects/braiagsi/files/HavocOS/4.3/ .
I have been using Havoc as my daily driver. It is stable and smooth and no bug (except dt2w not working which is a feature not bug) noticed so far for my type of usage.
Click to expand...
Click to collapse
Does it pass safetynet?

I finally settled on CAOS. A piece of advice to add to @jngiag post:
1. Sound is distorted even after installing Viper4Android. To overcome this problem head to Settings --> Phh Treble Settings --> Misc Features --> check "Disable audio effects".
2. There is a problem with backllight not behaving correctly. To correct this go to Settings --> Phh Treble Settings --> Misc Features --> check "Force alternative backlight scale".
@Linkfire360 - there are 4 ways to pass safety net in CAOS. Go ahead and read --> https://github.com/eremitein/treble-patches/wiki/CAOS11-Project

Thanks guys for the instructions and tips.
I managed to get crDroid 7.5 (crDrom11) flashed crdrom-v306-210425-arm64-bgZ.img. Had to switch from Pbrp recovery to OrangeFox. With Pbrp the fastboot reboot fastboot didn't activate the fastbootd mode. Flashed also the miui boot.img patched by magisk.
Sound works fine, following the above tips. Adaptive brightness is a mess, usually too bright, sometimes too dark, even with the Force alternative backlight scale ticked. But it was like this also on Miui. Phone is encrypted. SE Linux is enforcing, Play store is certified with Magisk Props module and Poco X3 Pro fingerprint. DRMInfo shows L1 Widevine, but Netflix shows L3 and and only SD quality playback. DT2W does not work, even with phh treble settings - xiaomi features - DT2W enabled set. Wifi display - casting screen to Sony ATV works, chromecast also works. Android Auto works. All 4 lenses work with NGCam_7.4.104-v2.0. Charging info seems to be incorrect on lockscreen, when fast charging with original charger. Charging speed seems to be correct.
Haven't yet tested call/call recording/mobile data/NFC contactless payment functionality. Edit: NFC payment works.
Updating to new build with fastboot flash system and wiping cache worked fine.

pryggi said:
Thanks guys for the instructions and tips.
I managed to get crDroid 7.5 (crDrom11) flashed crdrom-v306-210425-arm64-bgZ.img. Had to switch from Pbrp recovery to OrangeFox. With Pbrp the fastboot reboot fastboot didn't activate the fastbootd mode. Flashed also the miui boot.img patched by magisk.
Sound works fine, following the above tips. Adaptive brightness is a mess, usually too bright, sometimes too dark, even with the Force alternative backlight scale ticked. But it was like this also on Miui. Phone is encrypted. SE Linux is enforcing, Play store is certified with Magisk Props module and Poco X3 Pro fingerprint. DRMInfo shows L1 Widevine, but Netflix shows L3 and and only SD quality playback. DT2W does not work, even with phh treble settings - xiaomi features - DT2W enabled set. Wifi display - casting screen to Sony ATV works, chromecast also works. Android Auto works. All 4 lenses work with NGCam_7.4.104-v2.0. Charging info seems to be incorrect on lockscreen, when fast charging with original charger. Charging speed seems to be correct.
Haven't yet tested call/call recording/mobile data/NFC contactless payment functionality. Edit: NFC payment works.
Updating to new build with fastboot flash system and wiping cache worked fine.
Click to expand...
Click to collapse
CherishOS also works by dirty flash over HavocOS.
You may also try using the new twrp by just "fastboot boot TWRP-3.5.1-vayu-Nebrassy-1.img" (keep the OrangeFox as permenant recovery) and flash it like normal recovery. Use fastbootd with OrangeFox as a combination if necessary. If gapp could be flashed separately (as what I tried on vanilla Arrow), more choices of gsi roms (vanilla version) will be available then.

Anyone attempted installing gsi rom with 12.0.6 vendor? Any new issue?

Can we flash gsi directly from twrp ?

AmmarHaseeb said:
Can we flash gsi directly from twrp ?
Click to expand...
Click to collapse
No, phone has to be in fastbootd mode, where you can get with "fastboot reboot fastboot" command. You have to have quite recent fastboot binary/exe which supports this - download latest Android platform tools. Also the recovery on the phone has to support fastbootd, OrangeFox does.

xelrix said:
Anyone attempted installing gsi rom with 12.0.6 vendor? Any new issue?
Click to expand...
Click to collapse
I tried the vanilla version of Crdroid (crdrom-v306-210428-arm64-bvZ) and flashed gapp separately using new twrp. No issue from vendor 12.0.6. Very nice rom.

jngiag said:
I tried the vanilla version of Crdroid (crdrom-v306-210428-arm64-bvZ) and flashed gapp separately using new twrp. No issue from vendor 12.0.6. Very nice rom.
Click to expand...
Click to collapse
I flashed the Crdrom version with gapps. It has the Google Phone app by default. I can't seems to find the call recording functionality in there. Maybe not available in my region. Does the vanilla phone app have call recording?
Anyhow, 3rd party Cube ACR seems to record okay.
My banking apps work, streaming apps DisneyPlus and Prime Video work too. Only regrets so far is the Widevine L3 and SD quality in Netflix and the bad adaptive brightness behaviour.
Crdrom11 GSI seems to have a dedicated xda thread too:
[UNOFFICIAL] crDroid R Mod //crDRom11
crDroid 7.16 Your warranty is now void! We're not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in...
forum.xda-developers.com

Will any GSI work ex. those from Phh's list or it has to be "modified" first to work with X3 Pro?
I'm thinking about flashing Pixel Experience+ (or normal) from Braialindo repo
Also - is 90hz max or is 120hz also available somewhere?
Thanks

pryggi said:
I flashed the Crdrom version with gapps. It has the Google Phone app by default. I can't seems to find the call recording functionality in there. Maybe not available in my region. Does the vanilla phone app have call recording?
Anyhow, 3rd party Cube ACR seems to record okay.
My banking apps work, streaming apps DisneyPlus and Prime Video work too. Only regrets so far is the Widevine L3 and SD quality in Netflix and the bad adaptive brightness behaviour.
Crdrom11 GSI seems to have a dedicated xda thread too:
[UNOFFICIAL] crDroid R Mod //crDRom11
crDroid 7.16 Your warranty is now void! We're not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't answer you as I have moved to another rom. Likely it should be the same as the gapp version. CrDroid must be very popular and good to have a dedicated thread on it.
Th3 Ant said:
Will any GSI work ex. those from Phh's list or it has to be "modified" first to work with X3 Pro?
I'm thinking about flashing Pixel Experience+ (or normal) from Braialindo repo
Also - is 90hz max or is 120hz also available somewhere?
Thanks
Click to expand...
Click to collapse
Not all the gsi roms in Phh's list will work with our phone without modication. 90hz or 120hz setting is available.

jngiag said:
Not all the gsi roms in Phh's list will work with our phone without modication. 90hz or 120hz setting is available.
Click to expand...
Click to collapse
Is it possible to know which one do work without flashing them first? Or is it just trial and error?

Th3 Ant said:
Is it possible to know which one do work without flashing them first? Or is it just trial and error?
Click to expand...
Click to collapse
It is trial and error. There are more not working uaually end up in boot loader or boot loop mode. So far my known list of working gsi are:
1) Havoc (Braialindo)
2) Cherish (Braialindo) - Only if dirty flashed over Havoc
3) Crdroid R Mod (eremitein)
4) Caos (eremitein)
Version : arm64-bgz; arm64-bvz; arm64-ab-gapps; similar but vanilla version
Please share if you have additional.

pryggi said:
No, phone has to be in fastbootd mode, where you can get with "fastboot reboot fastboot" command. You have to have quite recent fastboot binary/exe which supports this - download latest Android platform tools. Also the recovery on the phone has to support fastbootd, OrangeFox does.
Click to expand...
Click to collapse
Just one doubt sir , can we restore a orangefox backup after flashing GSI ?

AmmarHaseeb said:
Just one doubt sir , can we restore a orangefox backup after flashing GSI ?
Click to expand...
Click to collapse
Hi, OrangeFox didn't have access to data partition, so I doubt the full restore will work. I have not tested restore nor backup. Maybe it works with the new TWRP? Anyone willing to test? I already started to use this as my primary device, so do not want to experiment anymore.
Second Crdrom charge cycle with 1 sim, seems to give about 12-13h SOT, over 2 day period for my usage.

[TOOL][SCRIPT] Generic System Image (GSI) flashing tool for Redmi Note 11

Automated GSI flashing tool for Redmi Note 11 (spes)
I WON'T GIVE SUPPORT TO THOSE WHO FACE ISSUES BY NOT READING THE STEPS BELOW CAREFULLY!
I will get right into the topic here, find the answers to your questions below at near the end.
What this tool does:
1. Flash a GSI to your Dynamic partitioned Note 11
2. Patch your Vbmeta
3. Patch Product for magisk flashing
How to use this tool:
0. Flash a rom (stock rom, MIUI EU, AOSP, ...) - IMPORTANT
1. Download your GSI and the tool, extract them
2. Copy your GSI image to the tool's folder, rename the GSI to system.img if you are using Windows
3. Boot your phone to fastboot mode and plug it in
4. Run the "windows.bat" or "macos.sh" script based on your os
5. Wait until the process finishes, your phone will automatically reboot
Download: See attached file
Extras:
A ROM collection Telegram channel of mine, you can see screenshots of GSIs I booted on Note 11 by searching it there
The original post on Telegram
Credit:
kusti420 for Product file
AnhNotAnh (me) for the tool ofc

Main Q&A:
Q: What is a Generic System Image, GSI?
A: A GSI is a prebuilt system image that can be booted on devices that support Project Treble. In short, this System Image is a custom ROM but it uses your Vendor, Kernel from your previous/stock ROM.
Q: Okay, but why I would like to flash it on my Redmi Note 11?
A: As we have already known, MIUI does not perform exactly well in the recent years, especially on such a low end and underpowered phone. GSI helps us getting a taste of AOSP's cleanliness and smoothness before the developers finish making actual custom ROMs. This is a temporary solution, good enough to use, please don't think or complain if your GSI perform badly, since it is not a ROM or trying to be one either.
Q: Why do we need a dedicated tool and such time wasting thing to do? Can't you just flash it in a custom recovery?
A; From Android 10, devices with it come equipped with a new partition scheme, as known as Dynamic Partition. It helps speeding up OTA updates and make the partitions more flexible in size. But also creates a huge difficulty in flashing those GSI, that is why you cannot flash the image in a custom recovery.
Q: My terminal window freezes at a certain progress for too long! What should I do?
A: This case often happens with Windows users. Everything is quite complicated BTS, but the workaround is just spamming Enter key several times every minute or two.
Q: What if I want to install a GSI on top of another one? I already flashed one, do I need to restore my MIUI or AOSP rom to flash GSI?
A: It is not necessary, you can flash a new GSI on top. The tool will clear your previous GSI without erasing required stuff from ROM.
Q: My GSI does not boot, what should I do??
A: I highly suggest using GSIs based on Phh's work. Those are often called Phh GSIs. Secondly I would highly suggest against using "Ported GSIs", those are often based on Erfan or Xiaoxindada's GSI tool, they are a port from a different device's ROM instead of directly built from source like Phh. Here is a list of GSIs based on the man himself, Phh.
Q: Bro my phone just boot to TWRP and nothing happens, computer still waits for my device??
A: Like I said before, you can try spamming Enter key. It is also likely that your TWRP does not support Fastbootd (Fastboot Dynamic) environment, an easy workaround for this is using MIUI's boot (kernel) image, stock Fastbootd mode will be used.
Q: Which Android version can I flash??
A: You can flash corresponding or NEWER Android version GSI with the ROM you are coming from/installing GSI on top, you cannot flash a lower version one. For example, you can flash Android 11, 12, 12.1, 13, bla bla GSIs when coming from stock Android 11 MIUI ROM (Android 11 Vendor for people who understands)
Q: Can I use this tool on another device?
A: Yes, with proper bringup and changes in the tool for it to compatible with your device and it will work. But I will not be responsible for bricks, which I always won't xD
More questions and answers will be updated later.

Reserved.

Thanks for this Awesome Tool. Quiet Simple and efficient.

@PingVN This script works on Xiaomi redmi note 11 4g codename selene?

[ROM][Huawei][12] LeaOS - AOSP 12.1 for Huawei device (EMUI 9)

Official AOSP for Huawei (ane) - LeaOS-PHH (android 12.1 version)
LeaOS is a project which based on AOSP with phhusson's Treble GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, Media App, Default Sound, MediaScanner fixes etc..)
Changelog :
LeaOS-PHH Jul 2022 version
Jul 2022 SPL
Build with last android aosp source (12.1.0_r11) and v415 phh
Fix MediaScanner crash and no default sound (ringtone, alarms..)
Fix all selinux denied
Add dynamic root
Add option in TrebleApp to collect adb log and create txt file in sdcard
Include specific properties for ANE-LX1
Installation
Download file : “LeaOS-A12-20220724-iceows-google-ane.7z" or "LeaOS-A12-20220724-iceows-ane.7z" and extract img file
Flash system image : fastboot flash system <drag system.img here>
Reboot and setup phone with android first start assistant *
* Do not set pin code with google apps version
Source Code:
https://github.com/Iceows
ROM OS Version: Android 12.1
ROM Kernel: Linux 4.9.x
ROM Firmware Required: EMUI 9
Based On: PHH AOSP v415
Credits:
PHH
And all the others who tested my patches and helped me improve this ROM
Support Group

reserved

Is Bluetooth pairing bug fixed for our device in this version?

luka_bubi said:
Is Bluetooth pairing bug fixed for our device in this version?
Click to expand...
Click to collapse
This probably won't help under [A12] GSI, but have you tried bluetooth manager apk? (google play or f-droid)

-Alf- said:
This probably won't help under [A12] GSI, but have you tried bluetooth manager apk? (google play or f-droid)
Click to expand...
Click to collapse
You can solve the problem with this app
Bluetooth Force Pin Pair (Conn - Apps on Google Play
Solve some Bluetooth pairing connect problems such as: Get the error wrong pin..
play.google.com

luka_bubi said:
Is Bluetooth pairing bug fixed for our device in this version?
Click to expand...
Click to collapse
Pairing bug is only with code pin bluetooth device. You can use an app to fix it, see my Alf response

Root don't work for me, i don't know why.. Safetynet don't work too.. Any solutions ?
Dual SIM don't work on custom roms?

I too could not get root to work (in order to remove root) and as consequence pass Safetynet also. I have tried with LeaOS - AOSP and LeaOS - Lineage ROM. As recommended in this comment I went with Pixel experience, but did not like it so I returned to @AndyYan LineageOS ROM.

AndyYan pass safetynet ? And for root you want a root rom or a non root rom ?
Pixel pass safetynet and Netflix stock playstore work fine with my patch for drm.wide (preavs)

As long as there is a clean ROM with no extra stuff that I have to remove then I do not need root. In most ROMs I need to became root to remove root and be able to pass SafetyNet.
As far as AndyYans ROMs go they do not pass Safetynet completely, just enough to fool my banking apps to work normally. That is good enough for me for my normal daily use of this phone.

luka_bubi said:
As long as there is a clean ROM with no extra stuff that I have to remove then I do not need root. In most ROMs I need to became root to remove root and be able to pass SafetyNet.
As far as AndyYans ROMs go they do not pass Safetynet completely, just enough to fool my banking apps to work normally. That is good enough for me for my normal daily use of this phone.
Click to expand...
Click to collapse
Ok so just securize ROM. I have already made a twrp patch to do this job, but not publish for the moment

Hello, I would like to ask if this gsi can be used for hi6250 models?Because the gsi of Android12L that I brushed several phh before can't boot ...

altairfr-huawei - Browse /LeaOS-A13 at SourceForge.net
sourceforge.net
is this for p20lite?
how do i know wich Rom meant for lx1?

lucsol said:
altairfr-huawei - Browse /LeaOS-A13 at SourceForge.net
sourceforge.net
is this for p20lite?
how do i know wich Rom meant for lx1?
Click to expand...
Click to collapse
For the moment this version not boot on ane-lx1. Boot only with mi 10 phone