Develop Bugs

Has anyone tried DirtyUnicorns?

Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:

errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
It is AOSP based compared to LOS (CM) which the majority of the ROMs posted are.
DU is a great ROM. I found that it lacked some important features that I like, but a very solid ROM.

Yes i tried on Sprint but there was no data...even after entering the apn in

errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
Encryption was not working, even with a full data format prior to flashing.
Any other opinions?

I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.

mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!

errikosd said:
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
Click to expand...
Click to collapse
It comes WITHOUT root. So you can choose your preffered method or no root at all.
I don't know about safetynet as I am not using android pay or anything that relies on it to pass.
Also I have not had any encryption issues as someone earlier replied

mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..

Scutariu said:
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Click to expand...
Click to collapse
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.

mrrflagg said:
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
Click to expand...
Click to collapse
I've tried several combinations, with older/latest firmware.
Every time, It would ask for the encryption password on bootup.
Even if I haven't set one up.. With data format prior to installing
Anyway, got sick of re-setting apps on my phone, just installed Maximus HD ROM, and that's that ?

Dirty Unicorns
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there​ is not a thread in the ROM section for DU.

morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there​ is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
I think it was the DU team's decision to close all and not allow any XDA threads. Someone correct me if I am wrong.
No idea why though.

morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there​ is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone

Encryption
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
I have had that happen when switching from a sense based ROM to LOS or AOSP and it's a "pita"... Anything that I want to keep gets moved to my SD card before I reboot to recovery.
I read through several threads and tried several possible solutions so I can't remember exactly which one worked.
I am currently on Verizon, official Nougat with the flashed us unlocked "patch", TWRP 3.1.0-1. If you are on Verizon or Sprint you need to patch the image with a missing image that is found in the us unlocked model (there are threads discussing it where you can find the file).

LOS
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Here is another thread on twrp issues
https://forum.xda-developers.com/htc-10/how-to/guide-fix-pin-pattern-password-t3538438

morr22066 said:
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Click to expand...
Click to collapse
It was not related to the data partition.
The format user data was done prior and after flashing it.

There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.

errikosd said:
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
Click to expand...
Click to collapse
Yea I'm having that sane problem with the touch key lights not working n it bothers me a bit. I didn't notice if the led was working or not. Keep me posted if u figure out the the key problem plz.

Looking for a ROM

As it appears StatixOS is going to no longer be maintained for whatever reason, I'm stuck with a soon to be outdated ROM on my, to me, expensive phone. So I have a simple question...
What ROMs are there for this phone? I'm aware there are some that aren't listed here, but I'm looking for one with the same features as Statix (plus some other features). I'd also prefer it if the ROM were official, as that tells me it's receiving proper support and likely won't be dropped for some time.

Karitoriki said:
As it appears StatixOS is going to no longer be maintained for whatever reason, I'm stuck with a soon to be outdated ROM on my, to me, expensive phone. So I have a simple question...
What ROMs are there for this phone? I'm aware there are some that aren't listed here, but I'm looking for one with the same features as Statix (plus some other features). I'd also prefer it if the ROM were official, as that tells me it's receiving proper support and likely won't be dropped for some time.
Click to expand...
Click to collapse
Stock is so good now days that a custom rom is not needed anymore.
Use the stock rom with a custom kernel and you can find find a few addons to your liking.
Sent from my Pixel 3a XL using Tapatalk

vandyman said:
Stock is so good now days that a custom rom is not needed anymore.
Use the stock rom with a custom kernel and you can find find a few addons to your liking.
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
Unfortunately I don't find that to be the case - the stock ROM doesn't offer the options that I like, such as navbar/statusbar cust., custom fonts, and precise DPI control, among others. Addons and third party apps can accomplish a lot of it, but very imperfectly, being more prone to bugs and issues than the same feature built into the ROM itself.
After having given Bootleggers ROM a try, I was VERY unimpressed, running into issues with it just minutes after booting and, even later after setting some things up, facing frozen apps, UX not responding properly and some rather suspicious activity (such as it somehow knowing what email I originally logged into my phone with, despite doing MULTIPLE full system wipes prior to install and being the ONLY custom ROM that triggered a "Severe security alert" from google upon trying to sign in), I've decided to stick with StatixOS until the LineageOS devs get off their butts and make an official ROM for this phone, as the unofficial one doesn't support eSIM which is required for Google Fi. StatixOS has the features I want, it's actually stable unlike Bootleggers "stable" build, and GPay works on it.
Note that my gripes with Bootleggers and the unofficial LineageOS are not meant to say you're not working hard at making a ROM - it's entirely a subjective review, and as a ROM enthusiast I understand the time and effort that goes into making a ROM even run partially right.

Have you tried Dirty Unicorns?
Or stock with edxposed and GravityBox (this is what I am currently using and it has been working perfectly for the last 2 months)?

How do you get GPay to work on StatixOS, I have tried using Magisk hide but it still detects root?

rzcay69 said:
How do you get GPay to work on StatixOS, I have tried using Magisk hide but it still detects root?
Click to expand...
Click to collapse
It may be an isolated case, but I had all google play services modules hidden along with google pay and other google apps (just in case they talk to each other), along with the safety patch module from magisk.

creeve4 said:
Have you tried Dirty Unicorns?
Or stock with edxposed and GravityBox (this is what I am currently using and it has been working perfectly for the last 2 months)?
Click to expand...
Click to collapse
I'm using the latest DU official for bonito right now, and at first everything was working wonderfully - except Google Fi is running into some issues on it where I can't send messages or make calls without being connected to wifi or enabling mobile data. I might reflash Statix, or I might just live with having to keep mobile data on when I'm not at home or work until they patch it up.

[ROM][OFFICIAL][11.0_r15] hentaiOS 11 for Pixel 2 / 2 XL

Removed by XDA Staff

Pictures ?
Enviado desde mi Pixel XL mediante Tapatalk

I've been using this rom for a few days, it's amazing, stock rom pixel 5, even i use adb mod installer for pixel 5 it works fine, thanks @Lunarixus

a_khusairi said:
I've been using this rom for a few days, it's amazing, stock rom pixel 5, even i use adb mod installer for pixel 5 it works fine, thanks @Lunarixus
Click to expand...
Click to collapse
Can you please give us a hint how to find "adb mod installer for Pixel 5"?
Thanks in advance

MartinN6 said:
Can you please give us a hint how to find "adb mod installer for Pixel 5"?
Thanks in advance
Click to expand...
Click to collapse
This https://forum.xda-developers.com/pixel-5/themes/custom-adb-magisk-module-mod-maker-t4186841

Downloaded and flashing now to test
Dont be dissapointed if i revert back to 10, i had issues with the 1st build of stock 11 (i havent tried the 2nd build), and ive seen others have them too
So dont take it personally if it doesnt pan out
Heres how i installed (much like most ROMS)
With the following in platform tools folder (unless you have your adb and fastboot in path) and at command prompt:
1) rom.zip (renamed from its longer name to make flashing easier)
2) twrp.img (renamed from its longer name to make flashing easier)
3) magisk.zip (renamed from its longer name to make flashing easier)
adb reboot bootloader
fastboot boot twrp.img
On device: wipe usual partitions &/ delete /sdcard/Android folder
push rom.zip /tmp
adb shell twrp install /tmp/rom.zip
adb reboot bootloader
fastboot boot twrp.img
push magisk.zip /tmp
adb shell twrp install /tmp/magisk.zip
adb reboot system
Setup ROM.....all good so far
Install full Magisk Manager (only stub appears from flashing zip) and reboot for full Magisk
Only gripes so far:
1) As with all ROMs ive ever seen with inbuilt G-Apps: Wheres Gmail? Annoying....
2) Be preprared for pretty much every app to need an update out of the box....needs more recent G-Apps cooked in if possible

73sydney said:
Downloaded and flashing now to test
Dont be dissapointed if i revert back to 10, i had issues with the 1st build of stock 11 (i havent tried the 2nd build), and ive seen others have them too
So dont take it personally if it doesnt pan out
Click to expand...
Click to collapse
Please let us know your thoughts and experience whether you continue to run this build out revert to 10 - thank you!

Great ROM definitely will stay here ??.... Maybe you should add more features in next builds like the possibility to hide the navbar without having to root (I only root because of this)
Just one question (I'm curious) why the name is Pixel 5a? @Lunarixus

images ? What a mania to present a product to us and not leave images of them
Enviado desde mi Pixel XL mediante Tapatalk

stifmaster81 said:
images ? What a mania to present a product to us and not leave images of them
Enviado desde mi Pixel XL mediante Tapatalk
Click to expand...
Click to collapse
In this case it's Pixel experience, so what you get is the same visually as a Pixel with Android 11.

@Lunarixus
I suspect youre using the device name Pixel 5a to pass SafetyNet out of the box?
I would personally rather it was left at original values (Pixel 2/XL) and then use MagiskHide Props Config to change the fringerprint to Pixel 2/XL Android 11 to pass SafetyNet (as with every other custom Pixel 2/XL ROM 10 ive tested with post-October security patches (Pixekl 2 XL - Android 10), that way its still recognised as a Pixel 2/XL, but maybe thats just me
I mean, i get it, less faffing about for users, but well, its not for me personally - ive just used MagiskHide Props Config to change it back to Pixel 2XL - Android 11

73sydney said:
@Lunarixus
I suspect youre using the device name Pixel 5a to pass SafetyNet out of the box?
I would personally rather it was left at original values (Pixel 2/XL) and then use MagiskHide Props Config to change the fringerprint to Pixel 2/XL Android 11 to pass SafetyNet (as with every other custom Pixel 2/XL ROM 10 ive tested with post-October security patches (Pixekl 2 XL - Android 10), that way its still recognised as a Pixel 2/XL, but maybe thats just me
I mean, i get it, less faffing about for users, but well, its not for me personally - ive just used MagiskHide Props Config to change it back to Pixel 2XL - Android 11
Click to expand...
Click to collapse
The stock Pixel 2 XL fingerprint has an older platform security patch level so it won't pass on a newer ROM (in this case the stock FP is October and my ROM is November)
So I use Pixel 5a as the device name to keep Safetynet in BASIC mode and I user the Pixel 5 fingerprint to have a newer security patch fingerprint.
So no, using Pixel 2 XL as stock is not an option anymore.

excellent, I would prefer the rom like this, I had a problem with my jabra helmets, for a moment it is heard with jumps, but then well, another thing, for my curious, I have seen that in google photos, the unlimited storage in original photos It does not have an expiration date, it will always be like this, like the first pixels?

supergenio2 said:
excellent, I would prefer the rom like this, I had a problem with my jabra helmets, for a moment it is heard with jumps, but then well, another thing, for my curious, I have seen that in google photos, the unlimited storage in original photos It does not have an expiration date, it will always be like this, like the first pixels?
Click to expand...
Click to collapse
Yes, it uses the first Pixels permission to make that happen so it will be indefinitely unlimited.

Lunarixus said:
The stock Pixel 2 XL fingerprint has an older platform security patch level so it won't pass on a newer ROM (in this case the stock FP is October and my ROM is November)
So I use Pixel 5a as the device name to keep Safetynet in BASIC mode and I user the Pixel 5 fingerprint to have a newer security patch fingerprint.
So no, using Pixel 2 XL as stock is not an option anymore.
Click to expand...
Click to collapse
All custom ROM's ive tested on the post-October security patch will pass SafetyNet with MagiskHid eProps Config, setting it to Pixel 2/XL and choosing Android 10 fingerprint. It passes in basic mode, without forcing basic mode....
Anyways this is a moot point for me as im heading back to Android 10 as this seems to have the same as yet unfixed issue with battery usage, it dropped dramatically on idle after i went to sleep last night, chewing through through battery. Your mileage may vary.

73sydney said:
All custom ROM's ive tested on the post-October security patch will pass SafetyNet with MagiskHid eProps Config, setting it to Pixel 2/XL and choosing Android 10 fingerprint. It passes in basic mode, without forcing basic mode....
Anyways this is a moot point for me as im heading back to Android 10 as this seems to have the same as yet unfixed issue with battery usage, it dropped dramatically on idle after i went to sleep last night, chewing through through battery. Your mileage may vary.
Click to expand...
Click to collapse
I'm not forcing people to root to have a device name changed.

Lunarixus said:
I'm not forcing people to root to have a device name changed.
Click to expand...
Click to collapse
Not arguing, just pointing out, its a custom ROM, 99.9% of people are gonna root it, otherwise they'd be on stock...
Changing the device name has potential issues....

Hello!! Been using for couple of days, everything is great! Battery isn't still stable yet but that's normal in initial setups.
I'm just missing one thing (for now): Add cards to power menu is not possible... Can you please add it to next build? Thanks! @Lunarixus
EDIT: The option is there, didn't see it till today!

Lunarixus said:
I'm not forcing people to root to have a device name changed.
Click to expand...
Click to collapse
good luck with this one, been there, done that, not again, certain users like to make things more complicated than they need to be but fail to read the "whys" things are the way they are (like in this instance of taimen no longer supported) then argue back. thanks for the awesome ROM and all the work you do for us throughout the years! I appreciate it!

Thread closed .
The "owners" of ROM were previously warned against posting HentaiOS ROMs on XDA.
Guess they forgot to intimate their maintainers
- XDA Staff

Development [ROM][13][ENCRYPTION] Official LineageOS 20 for A72

Link to original thread: A52 4G forum

Updated to Lineage 19.0!

Hey man! Everything is working great as far as I can see right now. Only one big drawback is the fingerprint scanner not working on Galaxy A72. It's not that it's registered and then it's failing. You can't even register it sadly.
Any fixes soon? Or is there a workaround which I am supposed to do, that I don't know about?
Thanks!

nadtonii1 said:
Hey man! Everything is working great as far as I can see right now. Only one big drawback is the fingerprint scanner not working on Galaxy A72. It's not that it's registered and then it's failing. You can't even register it sadly.
Any fixes soon? Or is there a workaround which I am supposed to do, that I don't know about?
Thanks!
Click to expand...
Click to collapse
Sorry, sadly I only own A52 which makes it really hard for me to fix it on A72.

Simon1511 said:
Sorry, sadly I only own A52 which makes it really hard for me to fix it on A72.
Click to expand...
Click to collapse
There are some suggestions.
Google Camera does not start, crashes. On GSI it helped to turn on the vendor Q.
In the screen settings, can you add a graph of picture saturation settings?
And is it possible to add a system backup to Lineage Recovery?

Realees56 said:
There are some suggestions.
Google Camera does not start, crashes. On GSI it helped to turn on the vendor Q.
In the screen settings, can you add a graph of picture saturation settings?
And is it possible to add a system backup to Lineage Recovery?
Click to expand...
Click to collapse
1. Which version of GCam? BSG works fine for me.
2 & 3: No, such features don't exist.

Simon1511 said:
1. Which version of GCam? BSG works fine for me.
2 & 3: No, such features don't exist.
Click to expand...
Click to collapse
Also BSG
Is it by any chance due to the rise kernel?

Realees56 said:
Also BSG
Is it by any chance due to the rise kernel?
Click to expand...
Click to collapse
No, it shouldn't be related to the kernel.
I'll investigate soon.

Simon1511 said:
No, it shouldn't be related to the kernel.
I'll investigate soon.
Click to expand...
Click to collapse
Of course it's a pity lineage recovery won't have a backup function, it's inconvenient to flash twrp every time.
And the colour saturation setting as on oneui is missing. I don't understand why you chose LOs, there's nothing in it at all, you can't even choose colours in styles. I was sitting on GSI 12A CrDroid before your firmware, great firmware in terms of customization. Never used google services. Never used google services.
Unfortunately when upgrading to GSI v402 the phone is extremely hard to start. About 8 times on reboot out of 10, 8 times caught bootloop. And this is on any v402 firmware.
In any case your firmware is better, even without having to patch separately the boot for magisk in order to run it on 12A GSI

Realees56 said:
Of course it's a pity lineage recovery won't have a backup function, it's inconvenient to flash twrp every time.
And the colour saturation setting as on oneui is missing. I don't understand why you chose LOs, there's nothing in it at all, you can't even choose colours in styles. I was sitting on GSI 12A CrDroid before your firmware, great firmware in terms of customization. Never used google services. Never used google services.
Unfortunately when upgrading to GSI v402 the phone is extremely hard to start. About 8 times on reboot out of 10, 8 times caught bootloop. And this is on any v402 firmware.
In any case your firmware is better, even without having to patch separately the boot for magisk in order to run it on 12A GSI
Click to expand...
Click to collapse
If you're unhappy with lineage feel free to build any other ROM on your own, the device trees are all on my Github.

friend! please don't stop developing this system, it's the best I could find for me a72, as soon as I can I'll send support through paypal

¿Funciona en Samsung A71?
Translated by GT: Does it work on Samsung A71?

usuario888 said:
¿Funciona en Samsung A71?
Translated by GT: Does it work on Samsung A71?
Click to expand...
Click to collapse
No. As the thread says, this is exclusively for A52 4G and A72.

Is this Rom still in development I have the A72 4G. Want to load the custom OS

GoldenJet said:
Is this Rom still in development I have the A72 4G. Want to load the custom OS
Click to expand...
Click to collapse
Yes, it is.

tried this rom its quite unstable loads of issues, still its the only rom at the moment. I reverted to stock.
Ok this was posted in haste and a bit in irritation what I meant is simply this is not useable as stable rom,
Its unstable and has issues. This is not meant as a revieuw or judgement of said rom. Its the first and currently only one avalible and kudo's to the creator. Its listed as development. Its just a quick feedback for those like me that just like to know if its stable or not.

Spacecabbie said:
tried this rom its quite unstable loads of issues, still its the only rom at the moment. I reverted to stock.
Click to expand...
Click to collapse
Would you mind telling me about the issues you experienced?
From my point of view (and from what others told me) it runs pretty stable and mostly bugless on both A52 and A72.

I have it running for weeks now as second device. Only real issue is fingerprint sensor and camera, could not find any gcam mod that would work properly. Apart for it - runs stable.

Simon1511 said:
Would you mind telling me about the issues you experienced?
From my point of view (and from what others told me) it runs pretty stable and mostly bugless on both A52 and A72.
Click to expand...
Click to collapse
Sorry Muyst have missed this,
Also edited initial post cause it was imho blunt and to negative. Sorry about that I have nothing but respect for mod creators.
I din't extensivly test but:
Vingerprint reader but this was known.
I had some screen issues (swiping up from bottem wouln't work so couln't close apps.
pixel launcher kept crashing (yes this might not be rom related but nova launcher also had issues)
General instability possibly all related to screen.
There where some other issues but as said my intention was not to extensivly screen it the above combined with the other small issues made me decide to remove it again.

I was using lineage os 19 in my Samsung Galaxy A72. It's better than pixel plus ui rom. It has 90hz screen refresh rate. But this rom has the following bugs also:
1. Proximity sensor not working at all;
2.Fingerprint or face unlock not working;
3. No safety net pass.

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/