Related
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.
ProtonAOSP
Android 11 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
componentchunk said:
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
Click to expand...
Click to collapse
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
fastboot flash boot boot.img (stock October). That booted it for me until he can update a fix. This ROM btw is phenomenal on battery life
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
kdrag0n said:
ProtonAOSP • Pixel 2 XL
Click to expand...
Click to collapse
Hello. Proton is incredible. Very fast, smooth and tenacious. Tested it from the first version. Thank you very much. I want to clarify something else for myself: Do I need to flash in both slots if a stock is installed?
palimatix said:
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Click to expand...
Click to collapse
No, you only need to wipe data if switching from another ROM.
73sydney said:
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
Click to expand...
Click to collapse
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
73sydney said:
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Click to expand...
Click to collapse
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
componentchunk said:
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
Click to expand...
Click to collapse
Sorry for the inconvenience, the problem lies in a botched SafetyNet fix that was missed in testing due to not flashing all partitions. You can make it boot temporarily by flashing the stock boot image. A hotfix that boots out-of-the-box will be up shortly.
pablo9023 said:
Hello. Proton is incredible. Very fast, smooth and tenacious. Thank you very much. I want to clarify something else for myself: I tested it from the first version. Do I need to flash in both slots if a stock is installed?
Click to expand...
Click to collapse
No, ideally the latest stock ROM would be installed in both slots beforehand but that's only because this build is missing firmware. A hotfix will be up shortly with the latest firmware included.
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
componentchunk said:
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
Click to expand...
Click to collapse
Xposed will never be supported, you are on your own if it's broken. I wouldn't recommend using it because it can cause all sorts of weird bugs.
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
kdrag0n said:
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
Click to expand...
Click to collapse
Great work, and thank you for the fast updates. Really looking forward to using the ROM when I clean format next time. Waiting for Google to release the last Security patch in December before making the jump, don't want to clean install every month. I usually stick with a ROM for a few months at a time.
Just to clarify if anyone is confused: this is an Android 11 ROM, not Android 10. XDA DevDB has no option for 11 so I had to put 10. I've just edited the DevDB info out of the post now and added 11 to the header so there should be no more confusion.
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
GROOVYJOSHCLARK said:
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
Click to expand...
Click to collapse
thank you very much for your assessment! I also find this rom to be very stable, snappy and the slight changes to the stock rom are very well thought out - next to perfect! big thanks to the dev krag0n!
I'm coming from an Android 9 Custom ROM and I wanted to switch to this, the instructions states that it should just be a simple flash. Should I still start from a clean reinstall of stock Android 11 or does flashing this come with that already?
kdrag0n said:
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
Click to expand...
Click to collapse
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
kdrag0n said:
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
Click to expand...
Click to collapse
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
73sydney said:
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
Click to expand...
Click to collapse
My Pixel 2 XL has been getting hardware attestation in all of my tests recently if the model name is set to "Pixel 2 XL". It's possible that I'm being A/B tested and most users don't have this problem, but either way, I haven't been able to pass SafetyNet without changing the model name because of it.
Either way, I've added hacks into the system in my ROM to avoid spoofing the model name while still defying hardware attestation and passing SafetyNet despite being on a mismatching security patch level. I agree, I don't want to change the model name just to pass SafetyNet, so I've been coming up with other solutions to avoid doing that.
There are too many useless functions in Miui，and so many bugs ,such as auto brightness,
ofcos ,anyone can tell me how to build a pe for 12x?
only gsi
I got my 12X today, global version. Most of the pre-installed apps I was able to uninstall, the only thing that really annoyed me was the gestures locked to the default launcher. I'm used to the Niagra launcher and its minimalistic approach, but I don't like the old three button layout, so I'm stuck with the MIUI launcher apparently :/ I hope we get some custom roms ASAP
rdadalte said:
I got my 12X today, global version. Most of the pre-installed apps I was able to uninstall, the only thing that really annoyed me was the gestures locked to the default launcher. I'm used to the Niagra launcher and its minimalistic approach, but I don't like the old three button layout, so I'm stuck with the MIUI launcher apparently :/ I hope we get some custom roms ASAP
Click to expand...
Click to collapse
Install "My Gesture" from google play and follow this instructions:
Btw: Fluidgestures like used in the video work too but for my opinion my gestures is better...
Voodoojonny said:
Install "My Gesture" from google play and follow this instructions:
Btw: Fluidgestures like used in the video work too but for my opinion my gestures is better...
Click to expand...
Click to collapse
Thanks! I've already tried to use FNG, but I couldn't hide the 3 nav buttons, I took a quick look at the video, but still no success, I'll check it later and I'll try to reproduce their settings. I'm just waiting my 168h to unlock the bootloader, then I'll try to run MIUI.EU and root it, then I'll be able to hide the nav buttons properly.
rdadalte said:
Thanks! I've already tried to use FNG, but I couldn't hide the 3 nav buttons, I took a quick look at the video, but still no success, I'll check it later and I'll try to reproduce their settings. I'm just waiting my 168h to unlock the bootloader, then I'll try to run MIUI.EU and root it, then I'll be able to hide the nav buttons properly.
Click to expand...
Click to collapse
From my experience, MIUI.EU is a little bit laggy, especially camera app. I flashed Miui TW rom and I think it's the best rom for the time being
mejgs said:
From my experience, MIUI.EU is a little bit laggy, especially camera app. I flashed Miui TW rom and I think it's the best rom for the time being
Click to expand...
Click to collapse
Oh, I heard some people saying that MIUI.EU was the best one. The TW one isn't like the chinese, without Google apps by default and filled with chinese apps bloatware? My friend got a 12X china version and he's struggling with some strange bugs with Google apps and other apps too, he's wating for the bootloader unlock to change it too.
rdadalte said:
Oh, I heard some people saying that MIUI.EU was the best one. The TW one isn't like the chinese, without Google apps by default and filled with chinese apps bloatware? My friend got a 12X china version and he's struggling with some strange bugs with Google apps and other apps too, he's wating for the bootloader unlock to change it too.
Click to expand...
Click to collapse
Miui TW is Taiwanese version of Global rom...everything is the same basically but with Miui dialer and contacts
I am also keen on just having any other option than MIUI. I've read in another thread (Link) that gsi roms are still buggy, especially with auto brightness, vibrator and fingerprint...
Does anyone know if the Chinese community could already build a stock Android 12 rom?
Prolution said:
I am also keen on just having any other option than MIUI. I've read in another thread (Link) that gsi roms are still buggy, especially with auto brightness, vibrator and fingerprint...
Does anyone know if the Chinese community could already build a stock Android 12 rom?
Click to expand...
Click to collapse
no,there is no stable rom for 12x till now
What do you guys use as daily driver?
I would really like to install pixel os on my 12x, but there is no project at the moment
Hello, guys! I have a question for you; I hope you could help me out with this, I've been looking over the web and couldn't find anything.
First some background.
Right after I bought my POCO F3, I unlocked the bootloader and flashed the xiaomi.eu rom, I stayed there for months, but then I wanted to try some AOSP ROMs, so I flashed crDroid, it wasn't what I was looking for, so I switched to Pixel Experience, I was pretty happy with it but some banking apps didn't work even with Magisk and zygisk and all that stuff, so I tried to flash Pixel OS but their recovery didn't work for me, my last shot was Lineage OS, but it was similar to crDroid, long story short, I decided to go back to MIUI global.
I used the official MiFlash tool and flashed the latest release of MIUI global stable through fastboot.
My concern is the following, after flashing the original rom through fastboot with the option "clean_all" is the phone stays the same as before flashing all that stuff? If not, what should I do?
Somehow I feel like there is a huge mess in the internal memory and I just want to make sure that everything is formatted, cleaned and original, like it never had any custom rom installed before.
If you chose clean all it will be like Brandon new, take note if you leave the bootloader un locked it will not pass google play store of certification, how lame right ,they want you to lock the bootloader, that's why I chose Arrow
jefffrom said:
If you chose clean all it will be like Brandon new, take note if you leave the bootloader un locked it will not pass google play store of certification, how lame right ,they want you to lock the bootloader, that's why I chose Arrow
Click to expand...
Click to collapse
I didn't now that, I just installed safetynet test and it fails the CTS profile match
Can I just lock the bootloader again to go back to normal? I don't plan to keep messing around with custom roms again
woix said:
I didn't now that, I just installed safetynet test and it fails the CTS profile match
Can I just lock the bootloader again to go back to normal? I don't plan to keep messing around with custom roms again
Click to expand...
Click to collapse
Yes
jefffrom said:
Yes
Click to expand...
Click to collapse
Thanks bro, I'll do that
You don't need to lock the BL.
Get Magisk, enable Zygisk, and use the Magisk Module "SafetyNet Fix" from GitHub. The Module did the job for me.
Might also work on Pixel Experience. ^^
I'm currently just using Stock MIUI 13.
cyanGalaxy said:
You don't need to lock the BL.
Get Magisk, enable Zygisk, and use the Magisk Module "SafetyNet Fix" from GitHub. The Module did the job for me.
Might also work on Pixel Experience. ^^
I'm currently just using Stock MIUI 13.
Click to expand...
Click to collapse
I already did that in pixel experience, but there was just one banking app that didn't want to work no matter what I try. I really wanted to stay in pixel experience but now that I'm back in MIUI 13 with poco launcher 4 it's not that bad either, at least I have Dolby Atmos, HDR and all that stuff.
woix said:
I already did that in pixel experience, but there was just one banking app that didn't want to work no matter what I try. I really wanted to stay in pixel experience but now that I'm back in MIUI 13 with poco launcher 4 it's not that bad either, at least I have Dolby Atmos, HDR and all that stuff.
Click to expand...
Click to collapse
Yeah because of Dolby Atmos and MIUI Camera I'm also staying on MIUI. ^^
BTW, just to really make sure, you used Magisk Module "SafetyNet Fix" on Pixel Experience, yes?
You can try deleting the folder "TWRP" if existent (some apps check for that folder, e.g. Mario Kart). You can also try hiding Magisk App (apps also check for that app).
cyanGalaxy said:
Yeah because of Dolby Atmos and MIUI Camera I'm also staying on MIUI. ^^
BTW, just to really make sure, you used Magisk Module "SafetyNet Fix" on Pixel Experience, yes?
You can try deleting the folder "TWRP" if existent (some apps check for that folder, e.g. Mario Kart). You can also try hiding Magisk App (apps also check for that app).
Click to expand...
Click to collapse
Yes, All of that. I followed this tutorial btw
cyanGalaxy said:
Yeah because of Dolby Atmos and MIUI Camera I'm also staying on MIUI. ^^
BTW, just to really make sure, you used Magisk Module "SafetyNet Fix" on Pixel Experience, yes?
You can try deleting the folder "TWRP" if existent (some apps check for that folder, e.g. Mario Kart). You can also try hiding Magisk App (apps also check for that app).
Click to expand...
Click to collapse
if you want the goodies of MIUI but also to pass safetynet without issues i suggest you to try "xiaomi eu"
they are based on the chinese rom which is ahead in terms of features and bugfixes (specially the beta) and have some optimizations to make the experience better
emmanuelin14 said:
if you want the goodies of MIUI but also to pass safetynet without issues i suggest you to try "xiaomi eu"
they are based on the chinese rom which is ahead in terms of features and bugfixes (specially the beta) and have some optimizations to make the experience better
Click to expand...
Click to collapse
Tried it.. it's oky... I like Google System Apps more. Call Recording Feature was nice. :v
But unfortunately, GSI's didn't work/boot with Xiaomi.eu (Generic System Images). I like to be able to use GSI's, to try out other new OSes from time to time, Dual Boot sorta. ^^
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 BootloaderUNLOCKING 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 RecoveryCredit 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/