Related
Hi!
I'm looking for the most stable GSI for the razer phone. These forums have been pretty dead honestly, so i'm not sure where to go.
Looking for the most up to date, feature complete, not broken GSI - My Pre-requisites are:
- Must support Magisk (i use the aptx-enabling modules that SHOULD have been in stock)
- Not bothered on android version, 8 or 9 will do
- WiFi & Tethering must work, i have an unlimited (without throttling) data plan, but you need WiFi for tethering
- Bluetooth audio must work, not bothered about calls, but music streaming over BT must work
- Generally stable - Stock rom is great, just missing a few features i like
What would your recommendations be?
If you want Magisk, go for one of the 8.1 GSI's, Pixel Experience would get my vote, nice ROM :good:
Peacce
I'll help in liven things up in this forum. Thinking of flashing (is this still the right term for GSI?) Lineage first when I get around to it over Christmas. I'm coming from a Oneplus one with the last few years on cyanogen / lineage, so I'm biased.
I'm using Lineage w/o gapps. I love it. I just wish I could figure out how to get signature spoofing to work so I could still play PokemonGO
Trollzero said:
I'm using Lineage w/o gapps. I love it. I just wish I could figure out how to get signature spoofing to work so I could still play PokemonGO
Click to expand...
Click to collapse
Does Lineage (or other GSIs) enable miracast? Stock seems to only allow mirroring to Chromecast devices, which I don't have.
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
Hello there,
while we wait for the development of AOSP Android Q ROMs I wanted to make a central hub for discussion related to Android Q GSI by phh, which is the only option we have right now to run an AOSP Q system.
It's also kind of a guide since the GSI doesn't boot out of the box when using the Q vendor by xiaomi.eu, so here's how to boot it.
1. Flash xiaomi.eu 9.10.24+ which is based on android Q. You should be able to get it to boot on your own, if it doesn't I'm sorry but this guide is not about that. One tip, you need to use an up-to-date TWRP, I used 3.3.1-1024 which you can find in the forum.
2. Reboot to recovery
3. Factory reset
4. Mount vendor in recovery and delete the last line of /vendor/etc/selinux/vendor_sepolicy.cil "(allow zygote_28_0 dalvikcache_data_file_28_0 (file (execute)))". The GSI will not boot if you skip this step.
5. Flash the latest Android Q GSI from phhusson's github releases page. It needs to be A/B (yes that's right) and arm64, so it will be something like system-quack-arm64-ab-vanilla.img. You can also use the gapps variant.
If nothing goes wrong the phone should successfully boot to Android 10.
It's stable (no crashes or anything) but I already found a couple bugs which make it unusuable for me, like alarms and notifications are silent (multimedia is fine), screen casting doesn't work and although I'm not entirely sure it was the GSI fault but cellular data felt quite slow.
I've also decided to write this post because it would be ideal if someone who feels like playing around with the phone a bit, or has a spare sirius will try booting the GSI off of Chinese vendor from here.
I know that in the past it used to be the case that xiaomi.eu vendors were more GSI-friendly, though I've checked and the Chinese vendor doesn't have the SELinux problem described above. Also it would be ideal because if we want any help from phh with fixing bugs it would be better to follow his guidelines about using OEM vendors.
Thank you all and let's get Android 10 running nicely on this phone
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.
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/