Database Info

[HOW-TO] Flash A/B Treble GSI ROMs without TWRP

Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547

I'll add that the Basic Package directly from Google in OP's post does not have functional call audio.
I highly recommend anyone try out Lineage 17: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673. Call audio works. FP sensor works. Camera also seems to work but I didn't really test it. I recommend flashing OP's patched boot image, too. Then all you have to do is install the Magisk Manager apk.
None of ExpressLuke's builds boot. Evolution hangs at the Evolution boot screen.
What we're missing now is TWRP. Lineage doesn't have gapps pre-installed, so we need a method for flashing them. I couldn't get MicroG services to work--apps could not see the accounts.

thatguy222 said:
I'll add that the Basic Package directly from Google in OP's post does not have functional call audio.
I highly recommend anyone try out Lineage 17: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673. Call audio works. FP sensor works. Camera also seems to work but I didn't really test it. I recommend flashing OP's patched boot image, too. Then all you have to do is install the Magisk Manager apk.
None of ExpressLuke's builds boot. Evolution hangs at the Evolution boot screen.
What we're missing now is TWRP. Lineage doesn't have gapps pre-installed, so we need a method for flashing them. I couldn't get MicroG services to work--apps could not see the accounts.
Click to expand...
Click to collapse
Call Bug confirmed but i had personally no Issue with the ExpressLukes Build. Just make Sure You don't use A64 Builds but ARM64 Builds (AB). Only GSIs with GApps was Havoc and Pixel Experience i think...
I'm running PE without issues Here (vbmeta from Google)

Can you elaborate on the vbmeta from Google comment?
And yes, only took one attempted flash with an A64 build to realize I needed ARM64 AB

thatguy222 said:
Can you elaborate on the vbmeta from Google comment?
And yes, only took one attempted flash with an A64 build to realize I needed ARM64 AB
Click to expand...
Click to collapse
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
That needs to be done with the vbmeta image from the Google Basic package together with the flash of the System/Kernel and fastboot -w to be able to boot Up some ROMs. That needs to be done after each Stock Firmware flash...
In other words. It's a vbmeta image with disabled verify boot Checks that works on modern Treble Device Like the Xperia 1 & 5
Don't know btw what A64 is ... lol

Miustone said:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
That needs to be done with the vbmeta image from the Google Basic package together with the flash of the System/Kernel and fastboot -w to be able to boot Up some ROMs. That needs to be done after each Stock Firmware flash...
In other words. It's a vbmeta image with disabled verify boot Checks that works on modern Treble Device Like the Xperia 1 & 5
Don't know btw what A64 is ... lol
Click to expand...
Click to collapse
Still hanging at the boot up screen for both Evolution and Havoc. Following your directions exactly. I must be doing something wrong.

thatguy222 said:
Still hanging at the boot up screen for both Evolution and Havoc. Following your directions exactly. I must be doing something wrong.
Click to expand...
Click to collapse
Have You tried Pixel Expierence? If that doesn't works must be something wrong :fingers-crossed:

PixelExperience does boot successfully. Wonder why Havoc and Evolution didn't...
Is anyone able to get IMS working? I can't get VoLTE to enable (on any non-stock ROM) and checking the short codes menu confirms IMS is unavailable. Re-flashed stock and it provisioning correctly.

Thanks a ton for this guide. I have the Xperia 1 and am about to go unlocked. Too much google in my life. I am assuming all this stuff is basically the same. I've been around more than my share of unlocking / rooting experiences, so I am not sweating it too much.

Updated the Thread. No need for the vbmeta Image with Havoc 3.5 (Official GSI with GApps)! Means a more secure Device somehow...

I did an Overlay for GSIs, based on our latest Android 10 Framework https://github.com/phhusson/vendor_hardware_overlay/pull/214
Possible that You can grab it here: https://forum.xda-developers.com/showpost.php?p=82550641&postcount=889
Rename to FrameworkResCommon.apk and push it to /vendor/overlay (Replace). Should work in Theory... Maybe. It's a first try and i don't know how it will be implented

Updated the Thread with some Changes

Thread updated again with My latest findings. The OEM Vendor from SONY has to be flashed to A/B to. Added that Steps! Enjoy

Talented developer here, nice work. Been a while since Sony devices have had this level of support. My messing around days are behind me but it's nice to see as an old XDA fan.

augie7107 said:
Talented developer here, nice work. Been a while since Sony devices have had this level of support. My messing around days are behind me but it's nice to see as an old XDA fan.
Click to expand...
Click to collapse
Feeling honored to hear this! I was always a Friend of Xperia Devices and was User of NUTs Dual Recoveries, FXP and Doomkernels and started making/publishing own ROMs with the Xperia T back in the Days. It's really sad, seeing all the Telegram Chat Groups around with no Structure and all the missing Development over here on XDA. A lot of stuff around Android has changed the last Years, but it's still fun to try and mess around with all the new stuff. I just wish i had a Team to grow up the Support...
Hope i can bring some Life onto the new Xperias in a new age of Android. Your Words really pushed Me up again :angel: Thank You! :highfive:

System_A && System_B?
Are system and vendor taking up double the amount of space on the drive by being installed for two paths?

&(*) said:
Are system and vendor taking up double the amount of space on the drive by being installed for two paths?
Click to expand...
Click to collapse
No. You have ROM storage and userspace storage on Your Device. Treble Android Devices have the Double amount of ROM Storage compared to non treble Devices. So it doesn't Matters If You only flash one Slot, Your user storage won't show more Space to use...

I understand the partitions are sized for two paths, which is the difference between an A only or A/B device (one system flag or two). Strange that the total space used wound't be displayed regardless of what the partitions are using. I was trying to gather the correct way to install a GSI rom and your instructions provided a new method for doing so. I guess I have to question whether the device I am installing on now is an A only or A/B device. Judging by the install size of 12gb for system which on other devices is roughly half, I am guessing it is an A/B device due to the space used.

Hi everyone, I just bought an Xperia 5, and being a little privacy concerned , I want to get rid of the Google parts of Android. After reading all the threads I found about this phone, and seeing that the Xperia 5 doesn’t have official support for LOS, I understand the most stable way to have a Google-free phones is by installing the GSI and then a Treble rom. I have the following doubts:
- Once I get everything installed following @Miustone 's guide, will I have to update the binaries every month? (I saw Sony posts vendor binaries every month on the Open Devices Website)
- If I install PHH’s treble Rom, will all the hardware work correctly (one message in this thread mentioned call volume problem)? What about the camera button?

[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1

⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10

Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.

mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.

KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.

I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.

KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?

mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post

mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with

SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .

working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!

LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9

any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?

Does OnePlus 8 tmobile version work with dual sim on this rom?

veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them

@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1

Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.

passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.

KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.

passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.

Is WiFi calling and LTE calling working?

How To Guide Install any custom ROM on ROG Phone 5 / 5s (GSI)

Install any GSI on your ROG Phone 5​​First of all I want to say that I am NOT responsible of anything you do to your device.​
What is a GSI?
A generic system image (GSI) is a system image with adjusted configurations for Android devices. It's considered a pure Android implementation with unmodified Android Open Source Project (AOSP) code that any Android device running Android 8.1 or higher can run successfully.
GSIs are used for running VTS and CTS-on-GSI tests. The system image of an Android device is replaced with a GSI then tested with the Vendor Test Suite (VTS) and the Compatibility Test Suite (CTS) to ensure that the device implements vendor interfaces correctly with the latest version of Android.
What GSI do I install?
There are multiple GSI you can choose (AOSP, LineageOS, Pixel Experience, ProtonAOSP, etc).
Here is a list of every GSI you can install: Generic System Image (GSI) list
For ROG Phone 5, you need to choose a A/B partition style and arm64 architecture GSI.
How do I install a GSI?
First of all, make a backup of your device (optional):
In the Settings app: "Settings > System > Backup > Backup now" or "Settings > System > Local backup"
In TWRP (TWRP for ROG Phone 5/5s): "Backup > select Data and Super > Swipe to backup"
And unlock the phone using the app in the official site: AsusUnlock_1.0.0.7_210127_fulldpi.apk
Factory reset your phone in recovery or Android
Now, reboot your phone into fastboot mode (shutdown then press Volume up + Power)
Connect the phone to the PC with the side port of the phone
Make sure you have ADB and Fastboot installed, if not install this: Minimal ADB and Fastboot or this: Android SDK Platform Tools latest
Download the vbmeta and extract it: vbmeta.img
Now flash everything:
In a command prompt, type the following commands:
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot -w flash system yourgsi.img
Replace yourgsi.img with the GSI you want to install
Now reboot your phone:
fastboot reboot
And that's it! You successfully installed a GSI on your ROG Phone 5!​
Common problems:​
Not enough space to resize system partition?​
If when you try to flash the GSI you get this error:
Resizing 'system' FAILED (remote: 'Not enough space to resize partition')
Then that means that your GSI is too big.
But don't worry, there is a solution!
Just type this before flashing the GSI:
fastboot delete-logical-partition product
This will delete the product partition and let enough space for the GSI.

Including Android 12 gsi? Has anybody tried this on this phone?

chairman011 said:
Including Android 12 gsi? Has anybody tried this on this phone?
Click to expand...
Click to collapse
Hi,
I installed a Android 12 GSI on my device and it worked. I recommend you Pixel Experience (choose arm64-ab-vndklite I recommend)

Alex2008Ex said:
Hi,
I installed a Android 12 GSI on my device and it worked. I recommend you Pixel Experience (choose arm64-ab-vndklite I recommend)
Click to expand...
Click to collapse
Any known bugs / issues you've noticed so far ?

JazonX said:
Any known bugs / issues you've noticed so far ?
Click to expand...
Click to collapse
Yes, on every GSI, the integrated phone speaker (for calls) doesn’t work. I didn’t noticed any other issues for the moment (not anymore with A12)
For the moment, only the fingerprint scanner, ROG specific features and secondary cameras are not working

Alex2008Ex said:
Yes, on every GSI, the integrated phone speaker (for calls) doesn’t work. I didn’t noticed any other issues for the moment
Click to expand...
Click to collapse
Ouch, So permanently on headsets ?

Sorry noob question
If I flash pixel experience android 11, armoury crate or dirac service still exist?

JazonX said:
Ouch, So permanently on headsets ?
Click to expand...
Click to collapse
I don’t know if we can use jack or Bluetooth headsets for calls but it doesn’t work directly on the phone.
Maybe it is possible to modify the /vendor partition to repair the problem(s)

Devaanp said:
Sorry noob question
If I flash pixel experience android 11, armoury crate or dirac service still exist?
Click to expand...
Click to collapse
No. This is a clean Android with Google pixel interface so Asus or ROG services are not installed by default like for example RGB on the back doesn’t work (I don’t know if it is possible to install them)

Alex2008Ex said:
No. This is a clean Android with Google pixel interface so Asus or ROG services are not installed by default like for example RGB on the back doesn’t work (I don’t know if it is possible to install them)
Click to expand...
Click to collapse
I'll think twice before flashing then, since RGB and dirac service doesn't work
Armoury crate can replace with kernel manager, but idk about RGB control apps

Alex2008Ex said:
Hi,
I installed a Android 12 GSI on my device and it worked. I recommend you Pixel Experience (choose arm64-ab-vndklite I recommend)
Click to expand...
Click to collapse
Awesome thank you I'm going to give it a shot do you have root working or are you just testing it out I think I'll test it out for a few days thank you for the response and the recommendation.

Forgot to ask, how to get back to ROG rom again? after flashing GSI?

Devaanp said:
Forgot to ask, how to get back to ROG rom again? after flashing GSI?
Click to expand...
Click to collapse
You can flash a RAW Rom in Fastboot to revert to stock anytime.

JazonX said:
You can flash a RAW Rom in Fastboot to revert to stock anytime.
Click to expand...
Click to collapse
Okay thanks, I'll try

chairman011 said:
Awesome thank you I'm going to give it a shot do you have root working or are you just testing it out I think I'll test it out for a few days thank you for the response and the recommendation.
Click to expand...
Click to collapse
Hi, you can use Magisk it works. Flash the apk in twrp it is the easiest (flash the apk after flashing system and before rebooting to system because encryption doesn't work) or use boot.img method.

Hey, good job on the tutorial but I was wondering whether you found a way to activate haptics and/or the audio jack

vinotux said:
Hey, good job on the tutorial but I was wondering whether you found a way to activate haptics and/or the audio jack
Click to expand...
Click to collapse
Hey, you can maybe copy the files from the vendor of the official firmware on the GSI but I don’t know what files and if it works.

Can I install android 10 or 9 on my Asus ROG phone 5?

HunterTik said:
Can I install android 10 or 9 on my Asus ROG phone 5?
Click to expand...
Click to collapse
Yes I think.

Alex2008Ex said:
Install any GSI on your ROG Phone 5​​First of all I want to say that I am NOT responsible of anything you do to your device.​
What is a GSI?
A generic system image (GSI) is a system image with adjusted configurations for Android devices. It's considered a pure Android implementation with unmodified Android Open Source Project (AOSP) code that any Android device running Android 8.1 or higher can run successfully.
GSIs are used for running VTS and CTS-on-GSI tests. The system image of an Android device is replaced with a GSI then tested with the Vendor Test Suite (VTS) and the Compatibility Test Suite (CTS) to ensure that the device implements vendor interfaces correctly with the latest version of Android.
What GSI do I install?
There are multiple GSI you can choose (AOSP, LineageOS, Pixel Experience, ProtonAOSP, etc).
Here is a list of every GSI you can install: Generic System Image (GSI) list
For ROG Phone 5, you need to choose a A/B partition style and arm64 architecture GSI.
How do I install a GSI?
First of all, make a backup of your device (optional):
In the Settings app: "Settings > System > Backup > Backup now" or "Settings > System > Local backup"
In TWRP (TWRP for ROG Phone 5/5s): "Backup > select Data and Super > Swipe to backup"
And unlock the phone using the app in the official site: AsusUnlock_1.0.0.7_210127_fulldpi.apk
Factory reset your phone in recovery or Android
Now, reboot your phone into fastboot mode (shutdown then press Volume up + Power)
Connect the phone to the PC with the side port of the phone
Make sure you have ADB and Fastboot installed, if not install this: Minimal ADB and Fastboot or this: Android SDK Platform Tools latest
Download the vbmeta and extract it: vbmeta.img
Now flash everything:
In a command prompt, type the following commands:
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot -w flash system yourgsi.img
Replace yourgsi.img with the GSI you want to install
Now reboot your phone:
fastboot reboot
And that's it! You successfully installed a GSI on your ROG Phone 5!​
Click to expand...
Click to collapse
im sorry noob question, what about the peformance increases (longer batery life, less throttling when playing high end games, etc) when i installed the custom rom compare to stock rom on rog phone 5 8/128, is it noticable ?

How To Guide [OUTDATED - PLEASE USE UNOFFICIAL LINEAGEOS INSTEAD] Installing a GSI on Samsung M12/A12.

I am deleting this guide since M12 will soon recieve an unofficial build of LineageOS 19.1. Don't ask when, as I'm not the lead developer but I helped with it

Update 1: I figured out how to make script run on boot. Instructions revised. If you followed earlier check them again
Update 2: Magisk 24.1 is now stable. Instructions revised.
Update 3: I contacted phh and he implemented the script inside his trebleapp. Instructions revised and modified trebleapp is attached. NOTE: GSIs newer than 7/Feb/2022 will include this workaround by default.
Update 4: This guide is now unnecessary now that unofficial LineageOS is very close to release

Achievement unlocked: flashed GSI with FBE enabled! ​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.

Amazing work. If you need testers feel free to PM me. As a sidenote, poking in sysfs led me to believe that android is sending the info needed to read the proximity but the kernel is sending garbage which gets interpreted as the sensor not being triggered. Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered

ap4ss3rby said:
Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.
Click to expand...
Click to collapse
Unfortunately, the commit was reverted as of master branch, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...

SB3P said:
Unfortunately, the commit was reverted as of master repo, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.
Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...
Click to expand...
Click to collapse
I guess for now we have two options:
A: Build custom kernel/vendor specifically for GSIs that correctly reports sensors as GSIs expect them to
B: Fix GSI issues through Magisk services implementing various workarounds in scripts. (an example is the touchscreen sleep/wake issue)

ap4ss3rby said:
Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered
Click to expand...
Click to collapse
Also that's interesting those virtual sensors are still present, I personally thought that Samsung made it the way there's an virtual device create as on Linux and there's their proprietary software running somewhere in the system that uses the camera as an input and calculates it to provide the data... On the other hand, when I think about that logic, even some (if not all) virtual devices on Linux (e.g. v4l2loopback) needs to have their module loaded with the kernel to work. I'm glad at least there's no need to reinvent the wheel and no one really needs to recreate the entire algorithm for it if it's going to be in the kernel sources...
ap4ss3rby said:
I guess for now we have two options (...)
Click to expand...
Click to collapse
I feel like the B option is worse than patching the GSI ROMs, either via flashable ZIPs or on your own... This is because I couldn't find anything in docs that would let me run services before /data is going to be decrypted... Personally, I've made myself a such service using the statically-compiled Linux ARM binary (non-NDK, using GNU libs – yes, it is still runnable on Android as well) – it applies the workaround for now both when screen is turned on and off (I had no idea on which event it should really run, so I made it to run on both just to be safe) by watching the file changes based on (AFAIK) filesystem events – so it has a major advantage over your script, as it won't run in endless loop, yet watch the file responsible for brightness to change and then do its job. But even with that, TSP doesn't seem to make touch available immediately and it is still expected to be revived after 1-2 seconds.
Also, as of the methods of applying these workarounds, the other way could be modifying the ramdisk (maybe with the help of Magisk, which I believe has documented how it's actually doing it itself and how others could modify the root and init as Magisk does to load files before the OS will properly initalize itself. Yet I don't like an idea of messing myself with the boot partition, at least for now...

Debug info: I tried flashing stock to grab logs from the touchscreen driver. The logs attached here do not appear at all on an unpatched GSI (I.E flashing the GSI as is without any touch workaround).

ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
Great guide.
Well done

Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)

matahbeyz said:
Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)
Click to expand...
Click to collapse
You don't have to resize TMPFS if you don't want to have FBE encryption or have the external SD card (you can use microSD for flashing, which might be a better choice if you need to flash a larger devices). Also you can't resize TMPFS to 64 GB, it uses your RAM to store regular data instead of storage (this is basically the concept of TMPFS). What I was mentioning is that /data won't work under FBE and custom recoveries for now, so you need to use your RAM instead if you don't have any external storage device to save images somewhere via ADB.
As of resizing the TMPFS, you should be able to find some Linux tutorial how to do that, on Android this is works basically the same (even on both Linux and Android you have /tmp directory with TMPFS by default).
Anyway, I've decided to share some stuff that you may need for that. Here's the multidisabler script I was using for flashing GSIs with FBE encryption preserved. I was also working on the native binary that would work as the workaround for the touchscreen so it can be used instead of the script. The advantages are that it actually listens to filesystem events and therefore does not need to read file in loop in order to get the information if brightness has changed. Maybe I'll share it with you once I find it to be ready, right now I'll just share my multidisabler script with patches.
BTW, I've tested LineageOS GSIs (both 11 and 12) and noticed they behave completely different, no matter of variant (the USB actually uses some driver, which is not fully compatible with M12 but close enough to provide basic communication through ADB). I guess pphusson just changed something and now these drivers aren't applied by default, yet I think I've noticed the issues with Bluetooth's HSP/HFP profiles which as I remember was not the case with latest stable pphusson's vanilla Android 12 GSIs. Now I just hope these problems are going to be resolved in the next builds of Android's GSIs with phhusson's patches and with the knowledge that MTP just worked fine on TWRP I used, there's a little hope that we will gain the proper combination of drivers/firmware to have both USB and Bluetooth functional at the same time someday.
I've also approached patching the kernel under newer kernel base 4.19.112, yet I gave up on properly resolving its conflicts. I may work on that as well in order to patch some vulnerabilities, with a hope that I'll succeed updating kernel as closest to the latest patch as possible. The 4.19.112 is going to be just a test if Samsung is capable of actually booting from it and if I may be able to use git with common human logic and my limited programming skills to actually patch it the way it would do so (without much understanding about the code itself, yet basic knowledge about C syntax). For now I've only succeed reproducing the upstream Linux kernel commit structure from 4.19.111, with a single additional commit for Samsung changes and another one for physwizz ones.

can anyone guide me how to unlock bootloader on Samsung Galaxy M12G ?

@SB3P Thanks so much. Sorry for my late reply, but thank you!

SB3P said:
Achievement unlocked: flashed GSI with FBE enabled! ​View attachment 5533799​In short, I've successfully done flashing of @phhusson's latest version of Android 12 GSI (which is v402 as of today). To do this, I needed to modify the multidisabler script so it won't disable FBE, format the userdata using the stock recovery, flash TWRP, resize tmpfs to proper size, push GSI image into tmpfs and flash it using TWRP. I used the securized image with vndklite variant, since there was no securized images for regular vndk releases (but it seemed that vndk was working better for me, at least I have no USB connection anymore where with VNDK I was able to have USB debugging). Maybe I'll try re-flashing it once I'll patch the regular images and securize them (since I'm on *nix, I can just mount them and modify their contents) and take an approach of finding how Samsung ROMs are working OK. For now, I need to take a break from all bootloops I had in the process of FBE flashing .
Anyway, the goal of this experiment was to use GSI ROMs as a daily driver and having FBE disabled could otherwise cause a serious problem on device loss.
So, onto the list what's been tested (that wasn't noted before):
Screen locking – it seems that the workaround for the screen is not applied before unlocking the phone, probably because the app is not running yet. This might work with the script used as postfs module.
EDIT: I've found some notes in the Magisk documentation that both post-fs data and late_start services are run after data is decrypted, which basically means applying this workaround using Magisk seems to be pointless for now (maybe not after PPH app will stop providing the workaround)... Probably the best option would be patching the ROM itself, either with flashable ZIPs or directly before flashing it (most GSIs can be mounted under Linux and tweaked).
Adaptive brightness – not working, since all virtual sensors are not working for now. Might be easy to fix through as I've found some stuff in the official ROM that I had an idea to experiment with putting them into GSIs (as a Magisk module, to avoid a breakage).
USB – as I said, a data transfer via USB is not working for me for some reason. It worked for me once I had VNDK Android 12 GSI installed (same version).
Booting with stock kernel – I had some successful attempts doing that, but it further was a cause of a bootloop, at least once I had installed Magisk. Therefore, I'll recommend patching the Magisk the way as in tutorial (after patching the kernel) to have everything working for now.
For people who wants to play with stock images but don't know how: you can use simg2img, lpunpack and Linux to extract and mount the official ROM image in approach of finding there some tips like in initrc services why some stuff is working fine on Samsung while it doesn't on GSIs. Maybe I would tinker with it a bit, trying to export a few services and libraries in an approach to create a Magisk module with all stuff needed to have a fully functional GSI, but I'm tired of modding for now, especially when this is my first Samsung phone I had to deal with.
Edit: Typo fixes, added additional text formatting.
Click to expand...
Click to collapse
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance

milindbhaliwade said:
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance
Click to expand...
Click to collapse
If you would see the *untested* section at the initial post of this thread, it is unknown whetever this works or not for M127G phones (if it bootloops it might not work at all). Anyway, here's how I did it on M127F (at least how I remember this):
1. I did steps from 1-6, I believe I skipped 7 since I was aware it will mess something up with the data partition.
2. I modified the multidisabler script and pushed it to my phone via the ADB (to TMPFS). You can find this script pushed as xz compressed file. Before executing multidisabler script I have done a backup of the recovery and system partitions (using dd tool) which I am going to reflash later.
3. I rebooted to download mode and flashed TWRP image.
4. After TWRP ended flashing, I booted into the recovery. I flashed the physwizz kernel and then my own GSI image as it was described in the instructions at the initial post. Just remember that /data partition is not functional with FBE and TWRP so you need to push your images somewhere else like microSD card or TMPFS partition. OTG might work here as well, this is something I haven't tested yet through...
5. Once you are done with flashing you need to restore the original recovery partition via the download mode. TWRP won't boot the GSIs with FBE encryption enabled actually it does boot now for me, yet I still recommend switching to stock recovery if your phone bootloops or you need to format/wipe userdata partition. You can then safely format your /data partition with the stock recovery.

ap4ss3rby said:
Hi, I installed LineageOS 18.1 GSI on my M127F. I want to share my guide to installing this GSI.
Code:
DISCLAIMER:
By following this guide you accept that you
may do irreversible damage to your phone.
If something breaks the responsibility is
yours only. If you want stable software that
is guaranteed to work 100% don't follow
this guide.
I assume you are running a fully stock system and and locked bootloader and firmware U3/U4.
Installing TWRP and custom kernel
Enable Developer Options by tapping on software information > build number 7 times
Enter developer options then toggle OEM Unlocking on.
Power off your phone.
Hold Vol Up + Vol Down then plug in your phone to enter download mode
THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY. Follow on screen instructions to unlock your bootloader. THIS WILL ERASE ALL YOUR DATA AND VOID YOUR WARRANTY
After this you want to download and install attached Orangefox recovery using odin. After odin is done flashing enter recovery
Format data (not wipe) in recovery
Enter terminal and type multidisabler twice
Reboot to system and verify that under security encryption is disabled
Download TWRP and custom kernel for your phone
Reboot into recovery and locate the downloaded twrp image
Select recovery.
Reboot into recovery
Install kernel, then wipe cache and reboot. You should now see that it is complaining about some internal issue. This is normal.
Installing the GSI
Download your favorite ROM from the list provided below. You want to install an arm64 a/b image.
Extract the image file
Reboot to recovery.
Select install then install image
Locate the GSI image
Select install system
After that is done return to recovery and select factory reset.
Reboot then do setup (if applicable) then download attached magisk and phh trebleapp. If your phone is stuck on bootanimation check under to fix it.
IMPORTANT: DO NOT LET THE SCREEN TURN OFF OR YOU WILL HAVE TO REBOOT TO MAKE TOUCH WORK AGAIN.
Install attached magisk
Open magisk and click on install then direct install
Download and install the attached phh-treble app apk.
Touch should now work. Enjoy your GSI.
Extras
Magisk 24.1
Open Magisk
Go to settings
Update Magisk Manager app to version 24.1
Relaunch Magisk then install magisk
Choose direct instal
Migrating to patched trebleapp
Download and install attached trebleapp
Open your root file manager
go to /data/adb/service.d
Delete the script you added earlier
Tips in case things don't work
In case after rebooting to the GSI the phone bootloops:
Download stock image from wherever you download your firmware (I use a python program called samloader)
Extract the AP of the downloaded firmware
Find userdata.img.lz4 and create a .tar archive only containing this file
Reboot to download mode
In odin select AP then locate the newly created .tar archive Then click on flash
Reboot
Continue from step 7 under the "Installing the GSI" portion of the guide
To revive the touchscreen using ADB:
In case you didn't grant adb root access but installed magisk, run adb shell then su. A root access for the app shell will appear. Grant root permission
Plug in phone to a computer with ADB
adb shell
su
cat /sys/class/sec/tsp/cmd_result
echo check_connection > /sys/class/sec/tsp/cmd
What works:
Boots
RIL
Fingerprint
Main rear camera
Front camera
Sleep/Wake (workaround in steps above, may need to sleep wake several times before it works)
WiFi
Flashlight
Rotation
Magisk 24
90Hz (M12 only. A12 doesn't have 90Hz refresh rate)
LineageOS 18.1
LineageOS 19
CAOS (GApps variant available)
phh AOSP 11 v313
phh AOSP 12 v400h
Untested
GPS
Flashing GApps. (I use fdroid and aurora store on LineageOS and CAOS has built in GApps)
USB-OTG
A127F
M127G
If I didn't list it under broken or working I didn't try it or forgot to test it.
Broken
Double tap to wake. Touchscreen turns off and I have no idea how to keep it alive while lcd is off
MTP
Virtual Proximity. Screen will stay on in phone calls and WhatsApp will always play voice messages through speaker
Flashlight brightness. Flashlight will always stay on weakest brightness with no way to adjust.
Adaptive refresh. The framerate you set in phh addons is what you get. Be prepared for slightly reduced battery.
You tell me (even though I probably don't have the solution)
Bugs
You may need to wait a little bit before touchscreen responds or sleep/wake several times before screen responds after turning the screen off
Credits
@physwizz for kernel, TWRP and orangefox
@phhusson for implementing workaround in trebleapp as well as GSI list
me for touch workaround
Links
Kernels and recoveries: https://t.me/a127f_res/113
GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
try to install @phhusson (system-squeak-arm64-ab-vndklite-gapps-secure.img) GSI using above method on Samsung Galaxy M12G (SM-M127G) BUT failed to boot up
facing following issue:
1) unable to boot in OrangeFox Recovery
2) boot in TWRP Recovery but not detected MicroSD Card
3) samehow manage to push Kernal.zip, SystemGSI.img by adb push file_name_with_extension /sdcard BUT not flash properly as TWRP reboot again and again in 2-3 minutes
so friends, don't try this method on Samsung Galaxy M12G (SM-M127G) unless Senior member come up with this specific model

For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread

ap4ss3rby said:
For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread
Click to expand...
Click to collapse
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.

SB3P said:
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.
This is why I think it is better to not close this thread and maybe revive original guide.
Click to expand...
Click to collapse
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware

ap4ss3rby said:
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware
Click to expand...
Click to collapse
I haven't said GSI are better, I personally use this unofficial LineageOS build. But what I've said, GSI brings much more variety of picking the OS you can install. Even Linux can be installed on phones nowadays using GSI with only Halium-patched kernel as an requirement. This is why I think leaving this tutorial archived (no updates, interest on fixing bugs etc.) is better than removing it.

How To Guide List of Working GSI's for Realme GT Neo 2 | GSI of Custom Rom

WARNING
Author of this guide won't be responsible for damages that occur to your device
Proceed at your own risk
​
Overview-
After reading excellent guide by @SirCDA - Guide Link ,
I have tried several GSI's for our phone GT NEO 2 and in
this post I am sharing which GSI worked for me .
Requirements-
1) Backup All data , Internal storage will be wiped !
2) Use latest adb and fastboot binaries - Link
3) Enable USB Debugging
4) Bootloader should be unlocked - Link
5) TWRP installed (by @SathamHussainM - Link )
first connect phone to pc by usb cable
6) Empty vbmeta files by @SirCDA - Link )
Instructions-
Follow Guide from here ,
Basically you have to reboot to fastboot mode using adb or by going to TWRP and in reboot section selecting fastboot mode
after that flash vbmeta files
Then erase system partition by using command fastboot erase system
Then flash the downloaded GSI using fastboot flash system gsileos.img
It will take some time after that
Wipe all data using command fastboot -w
Then reboot to sysem using fastboot reboot command
List of Working GSI
​1) LeOS Arm64 A/B Android 11 - reported by me
Boots =Yes​Working = Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock(with third party app)​Bugs= Volte,Fingerprint ,Fast Charging , and some minor bugs​
2) Havoc Os Arm64 A/B Android 11 - reported by me
Boots =No​Working=NA​Bugs= NA​
3) Ancient OS Arm64 A/B Android 11 - reported by @SirCDA
Boots =Yes​Working=Camera,GPS,Bluetooth,Wifi&Hotspot,​Bugs=Not Reported​
4)Ancient OS Arm64 A/B Android 12 - reported by me
Boots = No​Working=NA​Bugs= NA​
5) crDRom11 Arm64 A/B Android 11 - reported by me
Boots = Yes​Working=Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock,Fingerprint(enrollment takes time to detect finger press slightly harder)​Bugs= VOLTE and Fast Charging​

LeOs Tips
​Use Signal as SMS app for working Messaging ,​Dont try to enroll fingerprint , it make system UI crash ,
Only use this Magisk if you want to root it else other magisk will cause system to hang at bootanimation .​Follow this guide to get supefast face unlock Click Here​Use LeOS laucher instead of Trebutchet Launcher since it has many customistaions .​Enable Devloper mode and inside that setup Smallest Width as 392 and Display Cutout as Punch Hole Cutout .​Customise your OS from these settings - Settings> Display>Styles and Wallpapers and Setting>System>Buttons , Status Bar and Gestures​​​crDRom11 Tips
Use Signal as SMS app for working Messaging ,​Be patient while enrolling fingerprint , use thumbs and make whole area of thumb connect with screen at the light green spot​Only use this Magisk if you want to root it else other magisk will cause system to hang at bootanimation ​FaceUnlock is included by default and it works​Enable Devloper mode and inside that setup Smallest Width as 392 and Display Cutout as Punch Hole Cutout Many customisations available in crDroid settings.​Screenshots attached in this post ​
Thanks to @SirCDA for his guide from which I understood that you need to flash empty vbmeta files else phone will directly boot to fastboot mode only.
Thanks to @phhusson for making tools that allow GSI to work properly
Thanks to @harvey186 for making LeOS .

I also tried
Havoc OS Android 10 Arm64 A/B but that did not boot .
Ancient OS Android 11 Arm64 A/B but that did not boot .

RMX3370 said:
I also tried
Havoc OS Android 10 Arm64 A/B but that did not boot .
Ancient OS Android 11 Arm64 A/B but that did not boot .
Click to expand...
Click to collapse
Ancient OS Android 11 on mine it started normal

SrCDA said:
Ancient OS Android 11 on mine it started normal
Click to expand...
Click to collapse
Please also mention the bugs and exact ROM name

RMX3370 said:
Please also mention the bugs and exact ROM name
Click to expand...
Click to collapse
AncientOS-R-Society-v5.4_arm64_AB_bvN-IRON

Updated OP , currently the least buggy working GSI is crDrom11 with only two recognised bugs VOLTE and Fast Charging

I've tried the following roms:
https://sourceforge.net/projects/ancientrom/files/gsi/V6.2/AncientOS-S-Shield-v6.2-arm64_bgN-Steel-20220417.img.xz/download
https://builds.haridhayal.workers.dev/ProtonAOSP/2022_03_24/proton-12.3.0-2022_03_24-vndklite-arm64_bgN.img.xz
Haven't tried phone functions cause don't have a second sim card.
AncientOS have no fingerprint and face unlock. For face unlock there is the option but cannot detect the face. With magisk v24.3 there is no way to pass safetynet. On this one I've also copied my apps and settings from my previous phone and haven't found any malfunctions.
Proton also have no fingerprint and face unlock options into settings. After installing magisk v24.3 the system broke. It boots but the launcher sometimes works sometimes no. Settings app not opening and some other apps crashes (com.android.phone, etc). I've tried this for just a fews minutes so probably there is a solution for magisk but I don't like the rom and lack of personalization so no more testing for me..
For both roms the recovery is partially broken. /data and /cache partitions are inaccessible. Even if I format them, after a normal boot the partitions are broken again.
Also if the brightness is reduced to zero it completely disables the screen but the touch continues to work.
I think I'll try corvus as the next rom.

@maxysoft @RMX3370 crDroid Android 11, works fingerprint reader and face unlock

SrCDA said:
@maxysoft @RMX3370 crDroid Android 11, works fingerprint reader and face unlock
Click to expand...
Click to collapse
I had already added it to working list (I tried them on 20 but was not having enough free time to update OP)

maxysoft said:
I've tried the following roms:
https://sourceforge.net/projects/ancientrom/files/gsi/V6.2/AncientOS-S-Shield-v6.2-arm64_bgN-Steel-20220417.img.xz/download
https://builds.haridhayal.workers.dev/ProtonAOSP/2022_03_24/proton-12.3.0-2022_03_24-vndklite-arm64_bgN.img.xz
Haven't tried phone functions cause don't have a second sim card.
AncientOS have no fingerprint and face unlock. For face unlock there is the option but cannot detect the face. With magisk v24.3 there is no way to pass safetynet.
Proton also have no fingerprint and face unlock options into settings. After installing magisk v24.3 the system broke.
I think I'll try corvus as the next rom.
Click to expand...
Click to collapse
Please also comment if VOLTE works oon these ROMs by trying to open any webpage while on a call

RMX3370 said:
WARNING
Author of this guide won't be responsible for damages that occur to your device
Proceed at your own risk
​
Overview-
After reading excellent guide by @SirCDA - Guide Link ,
I have tried several GSI's for our phone GT NEO 2 and in
this post I am sharing which GSI worked for me .
Requirements-
1) Backup All data , Internal storage will be wiped !
2) Use latest adb and fastboot binaries - Link
3) Enable USB Debugging
4) Bootloader should be unlocked - Link
5) TWRP installed (by @SathamHussainM - Link )
first connect phone to pc by usb cable
6) Empty vbmeta files by @SirCDA - Link )
Instructions-
Follow Guide from here ,
Basically you have to reboot to fastboot mode using adb or by going to TWRP and in reboot section selecting fastboot mode
after that flash vbmeta files
Then erase system partition by using command fastboot erase system
Then flash the downloaded GSI using fastboot flash system gsileos.img
It will take some time after that
Wipe all data using command fastboot -w
Then reboot to sysem using fastboot reboot command
List of Working GSI
​1) LeOS Arm64 A/B Android 11 - reported by me
Boots =Yes​Working = Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock(with third party app)​Bugs= Volte,Fingerprint ,Fast Charging , and some minor bugs​
2) Havoc Os Arm64 A/B Android 11 - reported by me
Boots =No​Working=NA​Bugs= NA​
3) Ancient OS Arm64 A/B Android 11 - reported by @SirCDA
Boots =Yes​Working=Camera,GPS,Bluetooth,Wifi&Hotspot,​Bugs=Not Reported​
4)Ancient OS Arm64 A/B Android 12 - reported by me
Boots = No​Working=NA​Bugs= NA​
5) crDRom11 Arm64 A/B Android 11 - reported by me
Boots = Yes​Working=Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock,Fingerprint(enrollment takes time to detect finger press slightly harder)​Bugs= VOLTE and Fast Charging​
Click to expand...
Click to collapse
Hey, crdroid a11 gsi volte isnt working???

akgosai96 said:
Hey, crdroid a11 gsi volte isnt working???
Click to expand...
Click to collapse
Nope, not working on any GSI