LineageOS - Wifi doesn't connect after Magisk installation

LineageOS - Wifi doesn't connect after Magisk installation - OnePlus 7 Pro Questions & Answers

Hello everyone.
First of all, please take into account that English is not my native language, but I will do my best.
Yesterday, I wanted to install Lineage Os (v16.0-20200122) on my oneplus 7 pro. I had no problem accessing the bootloader, then TWRP (vt3.3.1-4). I then installed and configured Lineage Os on my phone, at that time the Wifi works properly.
Then comes the step of installing Magisk (v20.3 zip file) via twrp, the installation is done correctly, but from that moment, the wifi no longer works. When I activate it, it deactivates immediately.
Here's what I tried:
- Several versions of Lineage OS
- Several versions of TWRP
- Install TWRP before any operation
- To search the internet for similar cases, (I found this one on this forum) but I either did not understand, or it didn't work for me.
I'm a bit lost because I bought this phone for compatibility with Lineage Os and this problem completely blocks me

Related

[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
6. Uncheck Update Lineage Recovery alongside the OS option during start wizard
Work
Almost all
Known Issues
video recording
Links
3. 20210509: may security patch: https://drive.google.com/file/d/1qYWhEj4L1XidBnasg0ug00fsquV0smjD/view?usp=sharing
2. 20210430: april security patch: https://drive.google.com/file/d/1N5IgMEqjezZIxkfntKY6EydGRbRV7a7Q/view?usp=sharing
1. 20201224: initial technical build: https://drive.google.com/file/d/1uKoPL8nBlYQumNKjxwyH795eotDeGC5j/view?usp=sharing
Gapps
opengapps: https://sourceforge.net/projects/opengapps/files/arm/test/20210130/
BiTGApps: https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/
P.s. for BiTGApps: Chrome workaround with gapps: Chrome should be a part of system app in Android R (11) but we install it as user app, which break sign-in and sync in chrome. To fix this, allow contacts permission for chrome. Restart chrome and you can add your google account.
Root
Install latest magisk (21.1+) from canary channel: https://github.com/topjohnwu/Magisk/releases/tag/v21.1
Recovery
this is my build, the error with the screen off is still present, but I added an option for twrp with unlimited screen timeout, as a result, the screen does not automatically turn off.
for recovery: https://drive.google.com/file/d/1UeC4LwVEA6d46y0UPpuuipHbcjAtAo0Q/view?usp=sharing
for odin: https://drive.google.com/file/d/1WmAzhWkq9l_3d4m3Ft1xmihZaYfccUym/view?usp=sharing
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_picassolte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_picassolte

Thank you for your hard work !
Unfortunately too laggy for daily use... I have to stay with 17.1 ver....

Salut
Pour ma part je l'ai testé et effectivement elle est lente. 10 fois meilleurs est la ColtOs 6.5 dans ces 2 tests
Mais peut être que je m'y suis mal pris avec cette rom
Hi
For my part, I tested it and indeed it is slow. 10 times better is the ColtOs 6.5 in these 2 tests
But maybe I did it wrong with this rom

I updated to the 20210430 version from 17.1 doing a full wipe (including internal storage). Everything seems to be working at least as well as with 17.1. TWRP-3.3.1 still bootloops but 3.2.2 got the job done.
I installed the latest core BitGapps but got "No space left on device" error when trying to install the addon package. Netflix and Disney+ sideloaded nicely and so far I haven't encountered any issues with my daily apps. Will keep you posted if something weird occurs. Note though, that I'm not using Phone, Mobile Data, BlueTooth or Camera.
Huge thanks to @Valera1978 for keeping our device alive!

Two minor issues I've found in 20210509:
If I try to access settings through the status bar by sweeping down twice and hitting the cogwheel, System UI restarts.
Reddit app doesn't respect screen orientation. If I set the screen to portrait so that the USB connector points to the right, the app starts upside-down. No setting makes it reverse that. In 17.1 I could use it in either portrait orientation.

works well for me for now, thank you for your work dev.

how to turn on the backlight of the touch buttons?

Since the SM-T525 is basically the SM-T520 with LTE, is it possible to just install this on the SM-T520?
Edit: nevermind, found the answer here.

L1feGuard said:
how to turn on the backlight of the touch buttons?
Click to expand...
Click to collapse
I don't think you can. They used to work in 17.1 but not in this one so the developer needs to make some (kernel config?) modifications to make it happen in future versions.

All works well, but the current build contains a very nasty bug that might corrupt your SD-Card during heavy write activity. The only fix (if you're lucky) is to connect it to a Windows machine via TWRP and repair it there. It's been fixed some time ago, so is there any chance we could get an up-to-date build?
Many regards,
Zy.

Just a fair warning for anyone using BitGapps. Any version beyond R29 will set your SELinux status to permissive.
Description for a fix can be found here.
Regards,
Zy.

Flashing the May Package with OpenGapps Nano, Magisk 21.1 with the linked twrp didn't work for me.
Even though i wiped cache before the install, i don't get past the lineage boot animation after 30m.

Hello. Wich TWRP Version is needed to flash LOS 18.1 to T525 ? My Problem, i found only an older TWRP 3.0.2.0 well working Version but this carnt flash newer LOS. I get Error 7. Newer TWRPs like 3.2.2.0 makes a restart, if i select an Feature. Can anyone make an easy unterstand way ?

The 3.2.2 version found in the LineageOS 16.0 for T525 thread worked for me. Anything newer caused a boot loop.
I used it to flash 16.0, 17.1 and 18.1.

Thanks, and wich Gapps Version i need ? Wheres ARM ARM64 x86 and x86_64 available.

Thank you. I sucessfully installed lineageos 16 and gapps arm 9.0 pico and first time it looks good running. my problem was the to old twrp version

Now i found 2 Prolems. First is that i see no more the ChargeIcon (Batterie Icon with green load state) if Tab is shutoff but it charge. And Second if i start booting i get a yellow Erro Message Set Warranty Bit Kernel. What could be reason and should i flash 18.1 better ?

@FrankLinke
The yellow message is normal, you have flashed a custumrom and a New Kernel.
The missing charging icon is a bug, it was also on other device with LOS 18.x
I think with the next Version it will be fixed.

Ok thanks, so i can wait till newer fixed lineageos comes, because 16 runs well.

Hi
Finally got it working. As an absolute noob in this matter it took me a while (2 days) but finally my brief log for those who may still have issues.
TWRP throught Odin - Odin version has no relevance - I could patch TWRP with any, most important is to rename TWRP .img from a specific name to recovery.img and tar with 7zip (for example).
TWRP 3.2.2 only - other versions failed for me, however even with 3.2.2 it was quite an effort.
I patched it with all three versions of LineageOS 18.1 , one after the other but keep touching the screen to avoid get it blank. After 1st time I got this , patching resulted in a bootloop.
Then google apps - I got the micro version - mini was too big.
Now it works , I think it is at least as fast as before or even better but keep in mind I had veeery old 4.2.2 and the apps from the stone age as well - so it could be the issue.
Currently the only issue I have is the netflix app, it says it is not compatiblewith the device - I cant view it also in the web browser. Before that the app was working well on 4.2.2 (installed from the apk for incompatible ones).
I'd like to thank Valera1978 for this effort - as well as the other people who are involved in this work. THANKS!

[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

How To Install Magisk On Poco X3 NFC ?

I've unlocked bootloaders, installed Magisk and installed plenty of custom ROMs on different phones,
but this Poco X3 NFC has been just a bit 'annoying' from the beginning (ie. I had to try many different ways * before ability to 'register' for unlocking the bootloader, and then had to wait 7-days to actually do that )
Now, I just want to know how to get Magisk working ?
Currently I'm on MiUI ROM (but I will install AICP or CrDroid, in a few days),
and trying to install Magisk on this now.
I've got TWRP installed but Magisk doesn't have flashable .ZIPs,
because Magisk has moved to the .APK manager now.
So, in Magisk Manager, it asks me to patch a file, but which file would this be ?
How to get Magisk v23 installed on this Android 11-based MiUI ROM ?
Thanks.
*
I had to:
- register a Xiaomi account (this must be logged on the phone)
- put in a SIM card, with data activated (this must be enabled, to get the Xiaomi account working)
- send a SMS, to verify the number (Xiaomi checks/logs/records multiple levels of my identity)
- download a Xiaomi tool to unlock the bootloader (Xiaomi's tool did not work & I had to find one, from Github (and XDA) )
I have unlocked bootloaders on Samsung, Motorola, Oneplus, Asus … and Xiaomi is the most annoying, intrusive and cumbersome unlocking.

metaxda said:
I've unlocked bootloaders, installed Magisk and installed plenty of custom ROMs on different phones,
but this Poco X3 NFC has been just a bit 'annoying' from the beginning (ie. I had to try many different ways * before ability to 'register' for unlocking the bootloader, and then had to wait 7-days to actually do that )
Now, I just want to know how to get Magisk working ?
Currently I'm on MiUI ROM (but I will install AICP or CrDroid, in a few days),
and trying to install Magisk on this now.
I've got TWRP installed but Magisk doesn't have flashable .ZIPs,
because Magisk has moved to the .APK manager now.
So, in Magisk Manager, it asks me to patch a file, but which file would this be ?
How to get Magisk v23 installed on this Android 11-based MiUI ROM ?
Thanks.
*
I had to:
- register a Xiaomi account (this must be logged on the phone)
- put in a SIM card, with data activated (this must be enabled, to get the Xiaomi account working)
- send a SMS, to verify the number (Xiaomi checks/logs/records multiple levels of my identity)
- download a Xiaomi tool to unlock the bootloader (Xiaomi's tool did not work & I had to find one, from Github (and XDA) )
I have unlocked bootloaders on Samsung, Motorola, Oneplus, Asus … and Xiaomi is the most annoying, intrusive and cumbersome unlocking.
Click to expand...
Click to collapse
You just have to rename magisk.apk to magisk.zip and flash it via TWRP without wiping cache

Moreover, latest TWRP build from brigudav can do it for you -- look at "Advanced" options...

pnin said:
Moreover, latest TWRP build from brigudav can do it for you -- look at "Advanced" options...
Click to expand...
Click to collapse
Very good.
Yes, thank you.
I tried this and it was easy,
ie. to go into TWRP (by Brigudav) --> Advanced Options --> Install Magisk
Simple and effective.
My next issue then, was finding out,
that in TWRP, if I wanted to install TWRP.img (in phone's storage) ,
all files/folders in SDCARD were "encrypted" but I don't have lockscreen or PIN pattern turned on.
What causes this 'encryption' ?

Same here, it's the default on recent Android systems, it seems -- and can also be checked by entering the following in a terminal:
$ getprop | grep encrypt

You need to reset to factory setings in TWRP after removing any types of pin, or pattern lock.

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 5533799In 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.

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.

[Guide] Installing Updated GSI

So, I was testing various and came across the guide for installing LineageOS17 GSI in the guides section. The way mentioned seems to be working
Procedure-
Install TWRP with latest security patches according to this guide https://forum.xda-developers.com/t/updated-september-2022-how-to-root-a7-2018.4488289/
Now, download Latest LineageOS19.1 vndklite-secure GSI.
Make sure to have backup of your internal storage, it might need to be wiped.
Install this GSI and right after that install Quantum Kernel 2.5 GSI version(for mtp) (check in attachments, it has Magisk 25.2 instead of 20.4 as mentioned in verbose) and then Magisk. After boot, check if MTP works in system, if it reboots, force reboot to TWRP and format Data and then reboot. That should fix it.
Without the kernel, seems to be stuck at logo.
No critcial bugs I have seen till now.
PS: always maintain a backup, I am not responsble if something goes wrong, like data loss.
Now, haven't tested it, but seems to me that any version other than vndklite-secure will have the 'camera in use' problem. So, try and let me know if that's the case.
Note - TWRP used is from a telegram group, which I couldn't share without the permission of owner. Search for it and you'll find it in A7 2018 telegram support group. TWRP version is 3.6.2.
Dmverity-disabler is to be flashed according to how to root guide only.
Tested on SM-A750F/DS (INS).
The reason why GSIs later than android 11 have a lockscreen bug is due to a vendor issue, in which Android 10
vendor of A7 2018 is not compatible with these GSI's. Apart from some Android 10 GSIs (like Havoc), lockscreen and everything works on these.
Abridged from https://forum.xda-developers.com/t/sm-a750fn-ds-unofficial-lineageos-17-1-gsi.4195065/
The img file for TWRP 3.6.2 is https://sourceforge.net/projects/batuhan-s-builds/files/TWRP/a7y18lte/recovery.img/download
To flash it as tar, use 7zip or any alternative to arcive as tar with default options, just make sure the image file remains as recovery.img, because it is present in this form on the phone partition. Tar can have any file name.
Source Telegram group for TWRP img file is @Exynos7885Updates
No sources have been specified by the developer.
For Indian SM-A750F, BL FILE IS INCLUDED

Note: For Camera in use error, always try to use vndklite versions of GSI, they have specific patch to work with some specific types of vendors. Currently looking for lockscreen fix, most probably, it is also a vendor related problem.
All of these are android 12 or 13 ones.
Possibility of usage:
Works Complete with magisk (including working Lockscreen): FLOS19.1(https://github.com/ChonDoit/treble_flos_patches/releases) [use (VNDK)lite secure ones, stability check needed]
no lockscreen : AncientOS S,ProtonAOSP 12.4.1, ProjectBlaze12.1, LineageOS19.1, LineageOS 20.0 TD-based VNDKLite(no bluetooth), pHH A12.1 GSI (secure), OctaviOS(vndklite), Evolution X 13 vndklite (no bluetooth), Miku UI 13 (no bluetooth), Pixel Experience Plus 13 (VNDK)lite, (no bluetooth),
with 'camera in use': ArrowOS 12.1, CherishOS, DotOS, Pixel Extended 13, Pixel OS 13
Don't boot at all: CorvusOS, BlissOS, Crdroid, ProjectAwaken 415, DerpFest A13
Android 13 GSI's have a problem with bluetooth that allow connection but no audio to go to headset.
Downloads links: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-List

where can you get twrp 3.6.2 for a750?

I have the latest stock firmware. Do I have to downgrade?
Did your phone has the latest firmware when you installed GSI ROM? Did you downgrade the firmware?
Also are banking apps like GPay work on GSI ROMS?

blazzer12 said:
I have the latest stock firmware. Do I have to downgrade?
Did your phone has the latest firmware when you installed GSI ROM? Did you downgrade the firmware?
Also are banking apps like GPay work on GSI ROMS?
Click to expand...
Click to collapse
No you don’t have to downgrade, just use the older 2020 Update BL file.
You can use UPI if you can securize the gsi and follow the steps of fixing safetynet. Search them

Thank you for the response.
Can you update the BL file file from 2020?

blazzer12 said:
Thank you for the response.
Can you update the BL file file from 2020?
Click to expand...
Click to collapse
No, updating with later BL's can cause issue with custom recoveries.

Does anyone have issues with mobile hotspot in GSIs. In OneUI roms, mobile hotspot works normally, but on GSIs, it does turn on and discoverable, but without internet access. USB tethering works fine on all roms though.
My phone is SM-A750GN

VorzaCu said:
Does anyone have issues with mobile hotspot in GSIs. In OneUI roms, mobile hotspot works normally, but on GSIs, it does turn on and discoverable, but without internet access. USB tethering works fine on all roms though.
My phone is SM-A750GN
Click to expand...
Click to collapse
My 2.4Ghz hotspot work fine. SM-A750F/DS INS

Do sms and calls work properly in FLOS 19.1?

Database Info

welcome