Develop Bugs

Android pie

Which is the best pie Rom?

[email protected] said:
Which is the best pie Rom?
Click to expand...
Click to collapse
The one that suits your needs?
Try some and find out

I have only one device so if I mess that up. I am screwed.
So better to know from someone who has used.

Cr droid! Best stable pie rom!

Easy easy liqid remix

Thankyou all for the responses.

There is no stable Pie ROM yet.
All of them have broken keystore, so certificate based VPN's won't work.
But if you don't use VPN i can recommend AEX or crDroid.

I tried two Pie-ROMS (crDroid 5.0[24-12-2018] and Havoc-OS-v2.0-20190101) and with both I had several issues:
1) could not install Magisk 18.0 - fixed by installing TWRP 3.2.2 build from Linage 15.1 here: https://androidfilehost.com/?fid=5862345805528044694
2) could not get LED flashlight in Havoc running, third-party apps also did not work - just no response, don't know how to approach a fix/error search
3) camera(s) always force-closed on start, tried natively installed and gcam-ports - restarts, removing pins + restarts, flashing extra zip (https://forum.xda-developers.com/le...enovo-p2-kuntao-main-camera-fix-hal3-t3819258) did not work
4) could not connect to my hidden SSID 5GHz WIFI, although hidden extra option when entering login information was checked - this is especially frustrating, as I have no idea how to solve this
5) Update2: and with AOSP, I cannot write with Open Camera or other third party apps to the SD card.
If anyone has suggestions how to fix any of these, you are welcome!
Update: I also tried AOSPExtended6.1-Unofficial which did not show issues 2-3.

abprie said:
I tried two Pie-ROMS (crDroid 5.0[24-12-2018] and Havoc-OS-v2.0-20190101) and with both I had several issues:
1) could not install Magisk 18.0 - fixed by installing TWRP 3.2.2 build from Linage 15.1 here: https://androidfilehost.com/?fid=5862345805528044694
2) could not get LED flashlight in Havoc running, third-party apps also did not work - just no response, don't know how to approach a fix/error search
3) camera(s) always force-closed on start, tried natively installed and gcam-ports - restarts, removing pins + restarts, flashing extra zip (https://forum.xda-developers.com/le...novo-p2-kuntao-main-camera-fix-hal3-t3819258) did not work
4) could not connect to my hidden SSID 5GHz WIFI, although hidden extra option when entering login information was checked - this is especially frustrating, as I have no idea how to solve this
If anyone has suggestions how to fix any of these, you are welcome!
Click to expand...
Click to collapse
Thankyou for deep insight. I wanted to install but after checking the thread and your comment I think I have to wait.

[GUIDE] GSI ROMs installation tutorial. In pursuit of the best ROM that is not MIUI

Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this.
Disclaimer: Only tested with RR, PixelExperience, and ArrowOS GSI.
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
4. Fluid NG - App in Google Play Store to have the same recents/home/back gestures from MIUI 10.

reasonablebasis said:
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
Click to expand...
Click to collapse
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well. CTS will fail for obvious reasons

Mackay53 said:
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well.
Click to expand...
Click to collapse
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?

reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Can't remember as it was a while ago, possibly OctoOS and descendant and 1 other, omni ROM maybe.
For the ones that come with SU you need to navigate to the xbin folder in the system and remove the SU file.
Then cause Xiaomi EU uses the wrong fingerprint props you need to use the magisk props config module and manually type in the mix 3 fingerprint (unless the module has been updated to include mix 3).
If you installed the Chinese dev vendor then the props will be there ready to be used so the magisk module can make them active without manually typing it. This will sort out both safety net fails.

If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.

reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Pixel dust gsi too....

reasonablebasis said:
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
Click to expand...
Click to collapse
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.

Mackay53 said:
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Click to expand...
Click to collapse
Ok, I'll put a disclaimer that this only works on RR, PixelExperience, and ArrowOS. Anyway, I'm sure that the latest stable Xiaomi.EU vendor works without any issues with ArrowOS, else why would I be using it as my daily driver.

[deleted, duplicate post]

Someone know if there is a GSI with gapps and that don't have issue with bluetooth?

SafetyPatch module
reasonablebasis said:
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-...mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Click to expand...
Click to collapse
Mate, I can't find this module via Magisk Manager... Please help!

jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
You sure? Try searching for "SafetyPatch"

reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Strange....

reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....

jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
On Arrow ?

Wahoux said:
On Arrow ?
Click to expand...
Click to collapse
Yep! Not sure how to prove that though xD

Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/

Wahoux said:
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Click to expand...
Click to collapse
Dare to try? xD

jonny908 said:
Dare to try? xD
Click to expand...
Click to collapse
ahah no xD
Right now i'm about to flash Arrow, I hope I won't have bluetooth issue . On the non-GSI Pixel Experience, some reported issue with bluetooth whereas it was working fine for me... so let's see :fingers-crossed:

jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
Wow good for you. You flashed xiaomi.eu prior to GSI right? enumerate the steps you did, so that we we hopefully can replicate your success. Hehe

[ROM] [OFFICIAL] [AOKP 9.0/Pie] [cheeseburger] AOKP Pie for OnePlus 5

{
"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"
}
[ROM][AOKP 9/PIE][cheeseburger] AOKP Pie for OnePlus 5
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Introduction
WE ARE LIVE!!
AOKP is a ROM developed by TeamKang, based on AOSP/LineageOS with magical unicorn bytes (awesome features) baked right in!
Features
Android 9 Pie
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
Custom animations
Customizable AOKP logo in status bar
So many other features, explore and find them on your own!
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
Click to expand...
Click to collapse
Known Issues
Pixel Launcher crashes constantly if you try to use it. This is an upstream issue, Lineage-16.0 has the same issue.
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Ensure you have the proper firmware installed (9.0.9)
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
Official AOKP download page:
AOKP cheeseburger files
Source:
AOKP Source
Kernel source
Click to expand...
Click to collapse
Changelog
Initial Official release.
Thanks To/Credits
TeamKang
tdm
LineageOS
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Pie Android Open Kang Project for OnePlus 5 [cheeseburger], ROM for the OnePlus 5
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, TWRP 3.2.3 or later by codeworkx (Other TWRP versions not tested!!), Firmware package from OOS 9.0.9
Based On: LineageOS, CyanogenMod, OmniRom, AOSP
Version Information
Status: Nightly
Created 2020-01-20
Last Updated 2020-01-24

Reserved

Reserved

Builds are LIVE!!
Hey guys, AOKP Pie is OFFICIAL! Download links are in the OP, and I am including them below.
http://xfer.aokp.co/?developer=AOKP&folder=cheeseburger

This ROM doesn't officially support signature spoofing/microg?

Pokemetti2 said:
This ROM doesn't officially support signature spoofing/microg?
Click to expand...
Click to collapse
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.

Does this rom has a working googlepay support?
I have been on stock oxygen OS roms for too long and i am thinking about a change.
EDIT: it is working. Had to make sure that safetynet is passed and using hidemagisk on google products

shane87 said:
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.
Click to expand...
Click to collapse
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.

d1n0x said:
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.
Click to expand...
Click to collapse
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.

shane87 said:
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.
Click to expand...
Click to collapse
That's fine by me, just wanted to know whether I had to flash NanoDroid Patcher.

Update to OP
Hey guys, I just wanted to point out that I made a small update to the OP. I included a notice of the required firmware package from OOS that this ROM needs. Currently that is 9.0.9. We ran into an issue over on 5T, and it likely had to do with incorrect firmware on the phone. I forget that not everyone pours over gerrit as much as I do, so they don't see the required firmware commits.
I will update the OP, and post an announcement, any time that we update the firmware base required.

I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.

fosunite said:
I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.
Click to expand...
Click to collapse
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.

shane87 said:
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.
Click to expand...
Click to collapse
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.

fosunite said:
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.
Click to expand...
Click to collapse
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).

Added to the OnePlus 5 Index Thread here.

shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Sorry it will take a while, because i am unfamiliar with doing logcat. I will try connect my phone to pc via adb and try to log the events. It s quite tough doing while phone should boot.

newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?

shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Ok, Finally managed to pull a logcat. Hope this helps.
rikkker said:
newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?
Click to expand...
Click to collapse
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.

fosunite said:
Ok, Finally managed to pull a logcat. Hope this helps.
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.
Click to expand...
Click to collapse
Thanks for the logcat. I'll dig into it this weekend and see if it shows anything interesting. Quick question, have you tried lineage 16? If so, does it do the same thing as far as the sim1/sim2? Since we base off of Lineage, I want to make sure that the issue is linked to AOKP, and not something that we have inherited from lineage. I only have a single sim, so I can't test myself.
On the flashing sequence, I have personally never had any issues with flashing magisk right away, but ymmv. I do a wipe/factory reset, (after backing up via tibu and/or nandroid back up in twrp), manually wipe system, cache, and dalvik cache, flash ROM, flash magisk, flash gapps. Again, YMMV.
Also, you ONLY need the no verity flash if you have unencrypted your data partition. I left my data partition encrypted.
I have not flashed the 01/31 build yet, but I will check it out, probably tomorrow.

[ROM][UNOFFICIAL][woods] darklineage-14.1-20200913 [MOD of lineageOS]

{
"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"
}
Hi guys, I have been working on this rom from corona vacation due to some other works, I couldn't push the stable version of this rom. Today I'm releasing my modified rom of lineage as darklineage.
Key features
Full OMS support
Signature spoofing support
Pixel animated navbar (with on/off switch)
Pulse Notification LED Works (notification & Charging) [ Can be customize led notification light for apps]
Wifi hotspot client counts
Pixel accent colors
Rounded icons
LiveDisplay with Color Calibration
Ambient display (default - pulse notification) [ can be enabled to work with the proximity sensor (Reboot Required)]
Custom Headers (Added New Header images)
Quick unlock with Fingerprint After reboot
Change navbar height
USB Tethering tile
Separate ring and notification volume
Choose Ambient display brightness
Dynamic navbar color (changes color to the same of the status bar)
Quick Magisk Manager & Substratum dashboard launcher (Fixed magisk launcher error)
Two Column Dashboard
Memory bar on recent
immersive recent
enable/disable clear all button
SafetyNet
Install Hidden Core module from Xposed to pass SafetyNet.
Installation
If You are on custom rom with a working fingerprint than no pre-requirements just clean flash this rom. If not you are on a stock rom with the latest version (NMA.26.42-169) than downgrade your Rom with Spflash tool (Flash NMA26.42-113 / NMA26.42-75) rom and come to this rom otherwise the Fingerprint not work correctly.
- Backup first... always backup first
- Wipe system, data, cache, and Dalvik cache
- Install darklineage
Optional
- Install GAPPS / MicroG ( NanoDroid zip)
- Install root package of your choice (I recommend Magisk)
Enjoy!
Donations
I added a Donation Button in Settings → about. Please consider small support for me. Thanks in Advance. :good:
Screenshots
Check It in screenshot tile.
Download
darklineage-14.1-20200913-UNOFFICIAL-woods.zip
Motorola_Moto_E4_XT1762_MT6737M_WOODS_NMA26.42_75_04082017_7.0.zip
Support
join on Telegram Group : Moto_E4_Plus_Custom_Roms
XDA:DevDB Information
Dark Lineage, ROM for the Moto E4
Contributors
Zumairmhd, Dark_Eyes_, iykeDROID™ , @vishalk17 , @SamarV-121 , @RebelLion_ , @manjuyashu & Many others
Source Code: https://github.com/mhdzumair
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: <= NMA.26.42-113
Based On: lineageOS
Version Information
Status: Stable
Current Stable Version: 14.1-20200913
Stable Release Date: 2020-09-13
Created 2020-09-13
Last Updated 2020-09-13

Is VoLTE working sucessfully on this build?
also does it has edge lighting support?..
I'll try this after exams

Abish4i said:
Is VoLTE working sucessfully on this build?
also does it has edge lighting support?..
I'll try this after exams
Click to expand...
Click to collapse
I don't sure volte working or not. I added some of the volte wanted vendor blobs need to test by jio users.
Secondthing, you earlier also mention about this light. But in my device i have white led in the front of the phone (near to front camera). I mentioned in my post as notification led. So in this build That is work perfectly for battery charging, low batter and notifications.

really a great rom, very smooth, you gave this old smartphone a second life

VOLte status
hitman72 said:
really a great rom, very smooth, you gave this old smartphone a second life
Click to expand...
Click to collapse
Is Volte working on this rom
& Is it for xt62 or for moto e4 plus?

I have installed to xt1761 (standard "moto e"), sorry I don't know about volte. previously I had installed a rom from this forum with always a kernel present here, the phone was laggy like hell... about these kernels... guys don't use zram in your kernels! zram is the absolute evil for an android smartphone

hitman72 said:
I have installed to xt1761 (standard "moto e")
Click to expand...
Click to collapse
If you have this rom running can you please check for volte provisioning from ussd pls!
SINCE Only stock supports VOLTE and No other custom rom so I was thinking If this kernel has volte Functionality ... :fingers-crossed:

Abish4i said:
If you have this rom running can you please check for volte provisioning from ussd pls!
SINCE Only stock supports VOLTE and No other custom rom so I was thinking If this kernel has volte Functionality ... :fingers-crossed:
Click to expand...
Click to collapse
I found this after reading some guide, I hope it will be useful to you

Where can I download the 113 firmware? Which part of it is exactly needed for the working fingerprint?
Edit: Found the thread with the backup of 113. We will see...
Ok, fingerprint not working anymore, even with this 113 twrp backup. Original 113 firmware not available anymore, just the latest for the SP flash tool. Not important, my mother don't like the fingerprint scanner, so it doesn't matter. Original IMEIs back with Toolhero has worked perfectly, just the serial number is wrong and this is not fixable and maybe not important like the right imei numbers.
There is one bug, safety menu in settings is not opening and seems to crash. That's because fingerprint is not working here, for sure. Or, all fine so far for mother.
And I have changed the bootanimation for her
Edit: Now she got a new battery. Hope the phone is not going down anymore around 75%

I have installed it on my Moto e4 XT1762 (2017), and my camera and gallery are not working... When I try to acces one of this futures, the phone stops and reboot.
It's there something to do with it?
Thx

Notification Lights are working perfectly which is blinking lights that were disabled in stock rom and in all custom ROM .
This is the only ROM that has enabled blinking notification lights for each added apps the pulse and speed of blinking.
Notification lights are white only & not RGB colors.
Wifi Calling also enabled and is supported by my carrier.
Screenshots below August 2020 security patch.
If all restored userapp icons dissapear like as if it was formatted, just clear Dalvik and cache.

Why doesn't the screen lock work? Clicking on "security" in the settings closes automatically. With the error "settings stopped"

Hi everyone!!
Must say an awesome ROM. The dark theme was the selling point for me tbh and the fact that its based off LineageOS sealed the deal. Thus, an amazing ROM overall in terms of performance, stability and battery life (the 3 things that someone wants out of a ROM )
But one issue that I am consistently facing is whenever I go into Settings and tap on either "Security" or "Set up Fingerprint" the Settings app either freezes or crashes entirely.
I currently have LineagOS 14.1 Dark installed on my Moto E4 XT1762 "Woods" MediaTek variant
LineageOS version is 14.1-20200913-UNOFFICIAL-woods
kernel version 3.18
Build Number being lineage_woods-userdebug 7.1.2 NJH47F 0b5190fbeb test-keys
I also Magisk version 23.0 installed for root.
Troubleshooting steps that I have taken till yet:
Restarted the device numerous times
Wiped the Cache/Dalvik Cache from Recovery
Signed up using Google Email
Deleted Google's application cache and restarted
Signed up using a new user (that time it just froze on the boot animation until I manually restarted it)
None of the steps work and still whenever I tap on Security or Fingerprint, its like my devices just tells me to eff off and not play around with the security settings. If this is something that the developer intended or locked, I would love to know any way to unlock it
I have also googled the issue quite significantly. However, for my specific device, I was unable to find any good information thus I decided to post on my own. I have tried a couple of different fixes that worked on other devices with similar issues but the same ROM. However, none of them have worked so far.
Otherwise, I must say I have been using this ROM as my daily driver for like 2 weeks and have yet to come across any other issues. All my required apps work seamlessly and its like my 3 yrs old mobile got a new life. Just this one issue is bugging me, and would love if I get some guidance regarding how to resolve this!
Thank you once again !! Y'all are awesome!!

poptart_boi said:
Hi everyone!!
Must say an awesome ROM. The dark theme was the selling point for me tbh and the fact that its based off LineageOS sealed the deal. Thus, an amazing ROM overall in terms of performance, stability and battery life (the 3 things that someone wants out of a ROM )
But one issue that I am consistently facing is whenever I go into Settings and tap on either "Security" or "Set up Fingerprint" the Settings app either freezes or crashes entirely.
I currently have LineagOS 14.1 Dark installed on my Moto E4 XT1762 "Woods" MediaTek variant
LineageOS version is 14.1-20200913-UNOFFICIAL-woods
kernel version 3.18
Build Number being lineage_woods-userdebug 7.1.2 NJH47F 0b5190fbeb test-keys
I also Magisk version 23.0 installed for root.
Troubleshooting steps that I have taken till yet:
Restarted the device numerous times
Wiped the Cache/Dalvik Cache from Recovery
Signed up using Google Email
Deleted Google's application cache and restarted
Signed up using a new user (that time it just froze on the boot animation until I manually restarted it)
None of the steps work and still whenever I tap on Security or Fingerprint, its like my devices just tells me to eff off and not play around with the security settings. If this is something that the developer intended or locked, I would love to know any way to unlock it
I have also googled the issue quite significantly. However, for my specific device, I was unable to find any good information thus I decided to post on my own. I have tried a couple of different fixes that worked on other devices with similar issues but the same ROM. However, none of them have worked so far.
Otherwise, I must say I have been using this ROM as my daily driver for like 2 weeks and have yet to come across any other issues. All my required apps work seamlessly and its like my 3 yrs old mobile got a new life. Just this one issue is bugging me, and would love if I get some guidance regarding how to resolve this!
Thank you once again !! Y'all are awesome!!
Click to expand...
Click to collapse
Thank you for your kind review. in my installation guide i was strictly said before use this rom you need to flash NMA26.42-75 firmware using spflash tool to work the fingerprint. i'll provide the firmware rom link. you need to flash the rom and then come back here. if you need any guides or help please join in our telegram group.
Thanks.

Zumairmhd said:
Thank you for your kind review. in my installation guide i was strictly said before use this rom you need to flash NMA26.42-75 firmware using spflash tool to work the fingerprint. i'll provide the firmware rom link. you need to flash the rom and then come back here. if you need any guides or help please join in our telegram group.
Thanks.
Click to expand...
Click to collapse
Most welcomee!!
Plus, regarding the NMA ROM I must have missed that part. I am still a n00b when it comes to rooting/installing custom ROMs, thus pls excuse my silly mistake.
Please do share the link of the NMA ROM, plus if there is any guide to do the installation of the NMA ROM and then this ROM, please do share that as well. Although you have already mentioned that you flash the NMA ROM and then flash this one and the fingerprint should work fine, so not a strict requirement, but would be nice to have if possible
Plus, pls pls pls do share the telegram group link. Tbh after flashing the ROM I have gotten interested in learning about custom ROM development, plus, if I encounter any bugs I can get quicker responses from the OG devs like you, so would greatly appreciate the share !! ^_^
Thanks once again!! Awesome ROM!!

poptart_boi said:
Most welcomee!!
Plus, regarding the NMA ROM I must have missed that part. I am still a n00b when it comes to rooting/installing custom ROMs, thus pls excuse my silly mistake.
Please do share the link of the NMA ROM, plus if there is any guide to do the installation of the NMA ROM and then this ROM, please do share that as well. Although you have already mentioned that you flash the NMA ROM and then flash this one and the fingerprint should work fine, so not a strict requirement, but would be nice to have if possible
Plus, pls pls pls do share the telegram group link. Tbh after flashing the ROM I have gotten interested in learning about custom ROM development, plus, if I encounter any bugs I can get quicker responses from the OG devs like you, so would greatly appreciate the share !! ^_^
Thanks once again!! Awesome ROM!!
Click to expand...
Click to collapse
Here is the telegram link: Moto_E4_Plus_Custom_Roms

essa rom funciona a impressa digital no moto e4 XT1763

Very glad to see that there is development for the E 4 woods. Would like to install this ROM, but only have a hard-bricked E4 XT1762 Mediatek MT6737M. Made already a post on a (very old) thread
https://forum.xda-developers.com/t/e4-sprint-xt1766-unbrick-easy-with-sdcard-method-tested.3833408/
Is there anyone who could kindly try to build an unbrick.img for a XT1762? Don't have access to a working XT1762, so method of post 1 and 5 in the mentioned thread doesn't work for me. Or ist it possible to build an unbrick.img from stock rom? Thanks in advance

pancobe said:
Very glad to see that there is development for the E 4 woods. Would like to install this ROM, but only have a hard-bricked E4 XT1762 Mediatek MT6737M. Made already a post on a (very old) thread
https://forum.xda-developers.com/t/e4-sprint-xt1766-unbrick-easy-with-sdcard-method-tested.3833408/
Is there anyone who could kindly try to build an unbrick.img for a XT1762? Don't have access to a working XT1762, so method of post 1 and 5 in the mentioned thread doesn't work for me. Or ist it possible to build an unbrick.img from stock rom? Thanks in advance
Click to expand...
Click to collapse
you can try to unbrick it with sp flash tool. there plenty of videos around the internet about how to use sp flash tool

Hi,
I get to the first screen and then the phone reboots every time! Do we have a functional Lineage OS that I can use on the phone (android 7.1.2).
Thank you!
KR
Rok

Any idea how to add second SIM on/off switch for adb or rooted terminal?
I tied to use this method but couldn't find correct command.
Turning off second SIM via adb shell/Tasker - using activities/intents
I have a Xiaomi Mi6, which supports two SIMs. I need to figure out how I can switch the second SIM (SIM2) off outside business hours using Tasker. I've got as far as figuring out how to open the
stackoverflow.com

How To Guide A Complete Guide to Unlocking and Flashing for the A52s 5G.

Disclaimer​
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!​Now that we got that out of the way, we can continue.
Unlocking the Bootloader​UNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!​
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom Recovery​Credit to @BlackMesa123 for this guide.
Rooting your Phone​
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)​
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources​
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.

This is very helpful thanks

Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.

BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?

kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t

Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.

Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.

I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.

kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.

What about volte and hotspot on GSI pixel experience 13?

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?

7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.

Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.

Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.

7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.

Thx, all worked.

Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...

I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.

Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/