Develop Bugs

Will Pixel XL get a Magisk rom ?

Does anyone know if pixel xl will get a custom rom with Magisk built right in, like the Htc 10 has with Viper10 ?
I was checking out the Htc 10 forum and now Viper10 has Magisk built right in. Its really beneficial because you can disable the root with Magisk and take ota updates then turn the Magisk back on. This would make things so much easier for everyone.
I would love to see roms like Pure Nexus come with Magisk as that would be awesome.
I know its offensive to ask rom devs on roms they are building and or when they will be out and such, but maybe someone has heard through the grape vine and may be able to give a heads up on if Magisk could possibly be added to the coming customs roms for the pixel xl.

I think you misunderstood what that Magisk ROM is. It's not a ROM with Magisk built in. Magisk ROMs work like MultiROM on the Nexus 7 or 5 did and allow you to dual boot multiple ROMs. (In this case, HTC Stock and Viper)
Also even if somebody did make one, Magisk doesn't work on the Pixel devices due to the weird partition layout so you wouldn't even be able to use it.

We can already dual boot different Roms and kernels

bgiesing said:
I think you misunderstood what that Magisk ROM is. It's not a ROM with Magisk built in. Magisk ROMs work like MultiROM on the Nexus 7 or 5 did and allow you to dual boot multiple ROMs. (In this case, HTC Stock and Viper)
Also even if somebody did make one, Magisk doesn't work on the Pixel devices due to the weird partition layout so you wouldn't even be able to use it.
Click to expand...
Click to collapse
I meant a rom with Magisk built right in. The Magisk is systemless root which you can turn it off and be able to take over the air updates because your system is 100% stock with the Magisk turned off.
I was talking about such as the new Htc 10 Viper10 4.4 rom with Magisk built right in to the rom. I would imagine it could still work with the dual partition Pixel XL and I was curious if any rom devs might be working on just such a feature.

M9guy said:
I meant a rom with Magisk built right in. The Magisk is systemless root which you can turn it off and be able to take over the air updates because your system is 100% stock with the Magisk turned off.
I was talking about such as the new Htc 10 Viper10 4.4 rom with Magisk built right in to the rom. I would imagine it could still work with the dual partition Pixel XL and I was curious if any rom devs might be working on just such a feature.
Click to expand...
Click to collapse
That's what I'm saying though, a ROM with Magisk built in is completely different from that Viper thing from today.
The Viper ROM is a Magisk module for the devices existing stock ROM that replaces some files to turn it into a custom ROM (like the framework-res.apk)
You are asking for a ROM with Magisk preinstalled so you don't have to flash extra zip files.
Also, it wouldn't because Magisk itself doesn't work with the Pixel (the first known issue on the official Magisk thread and a post reply under that OP says until the creator of Magisk get's a Pixel, Magisk is incompatible with both Pixels so it wouldn't matter if it's preinstalled or you flash it, it wouldn't work. And not working means you can't even install a Magisk ROM like Viper.

bgiesing said:
I think you misunderstood what that Magisk ROM is. It's not a ROM with Magisk built in. Magisk ROMs work like MultiROM on the Nexus 7 or 5 did and allow you to dual boot multiple ROMs. (In this case, HTC Stock and Viper)
Also even if somebody did make one, Magisk doesn't work on the Pixel devices due to the weird partition layout so you wouldn't even be able to use it.
Click to expand...
Click to collapse
I disagree. Magisk worked on the Pixel's earlier firmware. I used it to decrypt my Pixels. The O update killed it.
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/

quangtran1 said:
I disagree. Magisk worked on the Pixel's earlier firmware. I used it to decrypt my Pixels. The O update killed it.
http://www.theandroidsoul.com/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Okay one, that website has hundreds of fake how-to guides that are the same one and all they do is change the device/OS name so I wouldn't trust that at all.
Second, maybe it worked but my point is the official Magisk thread says it doesn't work on Pixels because the layout. Since you said it "decrypted" your Pixels, I'm pretty sure Magisk does do that before installing but Magisk itself didn't actually install.
Lastly, there's no such thing yet as Android O so I know you are either trolling or don't know what you are talking about. Not only is 7.1 still Nougat/N but the Pixel launched with 7.1 so it hasn't had a major update that could have killed it if it worked before.

bgiesing said:
Lastly, there's no such thing yet as Android O so I know you are either trolling or don't know what you are talking about.
Click to expand...
Click to collapse
NMF26O is a build number, not an android version number.

xocomaox said:
NMF26O is a build number, not an android version number.
Click to expand...
Click to collapse
LOL. Thanks. I just didn't think an explanation was needed for the gentleman.

[ROM][GSI] Official Android Q

BETA Version
Ready to try?
I start....
https://developer.android.com/preview/gsi-release-notes

Is very difficult to make it stable....
Wifi connection and screen lock password issue,
second reboot impossible....
But nice to see this evolution.
Stay tuned, work on it....

Booted googles Android Q gsi. Everything works fine, mobile data, calls, Bluetooth etc. Only secured WiFi is messed up can't connect. Reboot bootloop issue is fixed by deleting vendor/app/
Steps I did was,
-have a fresh install of miui 10.3 (from xiaomi.eu) on to system
-flash Q gsi to system partition on twrp
-after gsi flash, reboot twrp then mount vendor and through twrps file manager locate vendor/app and delete it.
-reboot
And done bootloop after restart issue should be home.
Things I found are sounds are very static and distorted I got it fixed my flashing viper4android and you'll need root for that. Use magisk 19. Also I'm using global version. I'm sure chinese version will be fine but again I'm not sure

romen288 said:
Booted googles Android Q gsi. Everything works fine, mobile data, calls, Bluetooth etc. Only secured WiFi is messed up can't connect. Reboot bootloop issue is fixed by deleting vendor/app/
Steps I did was,
-have a fresh install of miui 10.3 (from xiaomi.eu) on to system
-flash Q gsi to system partition on twrp
-after gsi flash, reboot twrp then mount vendor and through twrps file manager locate vendor/app and delete it.
-reboot
And done bootloop after restart issue should be home.
Things I found are sounds are very static and distorted I got it fixed my flashing viper4android and you'll need root for that. Use magisk 19. Also I'm using global version. I'm sure chinese version will be fine but again I'm not sure
Click to expand...
Click to collapse
You sticking with it?

i found a big issue : wifi doesnt work for me.....

rafik25 said:
i found a big issue : wifi doesnt work for me.....
Click to expand...
Click to collapse
Flash the andro kernel

Mackay53 said:
Flash the andro kernel
Click to expand...
Click to collapse
Sorry i tried several times but no changes with andro kernel

Looks like incall voice is buggy too. I can't hear the person on the other end. And system notification sounds are still distorted like staticky.

Hope Q beta 3 will be available for Mix 3 )
Great. Only for mi9 and Mi Mix 3 5 f***** G

wyciunia said:
Hope Q beta 3 will be available for Mix 3 )
Great. Only for mi9 and Mi Mix 3 5 f***** G
Click to expand...
Click to collapse
Lets hope someone ports it over to the normal Mix 3 variant.

sandyrokr said:
Lets hope someone ports it over to the normal Mix 3 variant.
Click to expand...
Click to collapse
No need to port as it will be a GSI

Mackay53 said:
No need to port as it will be a GSI
Click to expand...
Click to collapse
Yeah I forgot about that but as this device is not specifically supported for a beta, it might have issues like previous GSI betas.

Mackay53 said:
No need to port as it will be a GSI
Click to expand...
Click to collapse
The official support would be nice. I understand the mi9, but i don't see the point i mix 3 5g. the user base is too low. It went on sale only week ago. 5g is still few years ahead from global adoption. Mix 3 4g would be better choice for beta testing.

wyciunia said:
The official support would be nice. I understand the mi9, but i don't see the point i mix 3 5g. the user base is too low. It went on sale only week ago. 5g is still few years ahead from global adoption. Mix 3 4g would be better choice for beta testing.
Click to expand...
Click to collapse
but still, going for 5g model helps xiaomi show their muscles...

Any one tried beta 3 ?
Tried......but bootloop

rafik25 said:
Any one tried beta 3 ?
Tried......but bootloop
Click to expand...
Click to collapse
Same here, tried to get it to work but constantly bootlooped

Anyone tried the latest beta?

But...by the end of the year Android Q will be officially avaible as OTA update for mi mix 3 and other Xiaomi phones as confirmed by them. So why messing things up with unifficial GSI "just to try" a new release? I'm not blaming anyone who wants to, but it is really necessary? It's so terrible to stay on MIUI rather than stock or so bad to stay on Pie (both stock or custom) rather than on a newer OS version?
Personally i prefer a stable software (or an almost bug free one at least) than an unstable one with possibly many non working/partially working features. What do you think?
P.s before the bull**** storm by someone:
1) Yes, i used custom roms before on other devices, i liked them and they always made my devices better in terms of performances and upgraded them to the latest OS avabile when the official support ended. (Galaxy SII Plus, Galaxy Tab S2, Honor 8)
2) You can do whatever you want with your device, i really couldn't care less, but wer're on a forum, i'm just taking a conversation to hear other opinions about GSI (or other custom roms) for this devices wich i found to be very fast, complete and battery friendly even without them.
3) Thank you

I couldn't care less

ROM ❯ PIXEL 2 XL ❯ OFFICIAL ❯ ProtonAOSP 11

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.

Question Going back to original (MIUI Global stable) after flashing many custom roms

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. ^^

General [CLOSED BETA 4] ColorOS 13 | OnePlus 9 Pro

ColorOS 13 based on Android 13 has finally arrived for the OnePlus 9 Pro.
It's a Closed Beta version for the moment and therefore unstable (you could potentially encounter some bugs).
If you want a review :
Download Links (please flash at your own risk) :
ColorOS F.03 :
https://gauss-componentotacostmanua...22/08/05/eb43c65721f14cfead64de23686dd181.zip
ColorOS F.04 : https://yun.daxiaamu.com/OnePlus_Roms_2/一加9 Pro/ColorOS 13.0.0 F.04/
ColorOS F.05 :
一加9 Pro/ColorOS 13.0.0 F.05 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
ColorOS F.06 :
一加9 Pro/ColorOS 13.0.0 F.06 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
F.06 was the latest Closed BETA version.
OPEN BETA -> https://forum.xda-developers.com/t/open-beta-1-coloros-13-oneplus-9-pro.4493509/

Changelog (F.04) :
[Optimization] System stability in some scenarios.
[Fix] Icons in the notification bar are overlapped.
[Fix] Slow response to automatic adjustment of screen brightness.
[Fix] Some application icons on the desktop display blurry.
[Fix] Probabilistic screen-off or phone flashing when unlocked.
[Fix] The drop-down status bar probabilistic control center display is transparent.
[Fix] Double-click on the screen and the screen off function in guest mode are invalid.
[Fix] The "other" type of storage space in the settings is displayed abnormally.
Changelog (F.05) :
[Optimization] System stability and fluency in some scenes
[Fix] The charging prompt keeps popping up when charging probabilistically
[Fix] The app icon is not fully displayed when using the home screen style
[Fix] The multitasking icon does not match the app

Whyyyyyy C.47?! If I could keep C.62 on one slot and flash COS to the other, I would do it, but I'm not in the mood to go through the hassle of downgrading.

EtherealRemnant said:
Whyyyyyy C.47?! If I could keep C.62 on one slot and flash COS to the other, I would do it, but I'm not in the mood to go through the hassle of downgrading.
Click to expand...
Click to collapse
You can try to use something like clone phone

progerturn said:
You can try to use something like clone phone
Click to expand...
Click to collapse
If it's anything like with the switch from 11 to 12, the tools change too, and they aren't compatible with each other.
I already backed up to Google. That's all that I really need, I just really don't want to nuke my phone. I was hoping to be able to flash alongside C.62 so I can just switch slots to get back to OOS when I'm done tinkering.
I am pretty sure that my radio will not work (I have a global 9, it's single SIM, and when I tried COS12 I had to use a Magisk module to get my radio back) so being able to switch back easily would be nice.
EDIT: Yeah, there's no way I can convert without nuking. Going to be with my boyfriend this weekend, I'll mess with it on Sunday night when I get back. I'll have to downgrade to 11.2.8.8, upgrade to C.48, unlock the bootloader, convert to COS13, then hope that the Magisk module for OOS12/COS12 works on COS13 to get my radio working again.

It is closebeta not openbeta

EtherealRemnant said:
If it's anything like with the switch from 11 to 12, the tools change too, and they aren't compatible with each other.
I already backed up to Google. That's all that I really need, I just really don't want to nuke my phone. I was hoping to be able to flash alongside C.62 so I can just switch slots to get back to OOS when I'm done tinkering.
I am pretty sure that my radio will not work (I have a global 9, it's single SIM, and when I tried COS12 I had to use a Magisk module to get my radio back) so being able to switch back easily would be nice.
EDIT: Yeah, there's no way I can convert without nuking. Going to be with my boyfriend this weekend, I'll mess with it on Sunday night when I get back. I'll have to downgrade to 11.2.8.8, upgrade to C.48, unlock the bootloader, convert to COS13, then hope that the Magisk module for OOS12/COS12 works on COS13 to get my radio working again.
Click to expand...
Click to collapse
What Magisk module is this? I've had trouble getting my SIM to work on COS so I'm interested.

If this is a closed beta and someone leaked it they're gonna get their ass kicked, they could even get sued.

Mohsin6643 said:
What Magisk module is this? I've had trouble getting my SIM to work on COS so I'm interested.
Click to expand...
Click to collapse
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing multi sim. So props were added to make it like a conversion to...
forum.xda-developers.com
Says TMO but it works for any single SIM variant.

djsubterrain said:
If this is a closed beta and someone leaked it they're gonna get their ass kicked, they could even get sued.
Click to expand...
Click to collapse
I highly doubt anything will happen. There's no way to prove who leaked it because it's not like OnePlus is going around tagging individual OTA files and closed beta tests are dumb anyway. I get it for devices like the 10 Pro that don't have MSM Tools but all of us with the 9 series can recover pretty easily. This is not the first closed beta test that leaked and it undoubtedly won't be the last.

djsubterrain said:
If this is a closed beta and someone leaked it they're gonna get their ass kicked, they could even get sued.
Click to expand...
Click to collapse
No one is getting sued over this. Especially not from Chinese. lmao.

brmbjn said:
It is closebeta not openbeta
Click to expand...
Click to collapse
thx, edited

EtherealRemnant said:
If it's anything like with the switch from 11 to 12, the tools change too, and they aren't compatible with each other.
I already backed up to Google. That's all that I really need, I just really don't want to nuke my phone. I was hoping to be able to flash alongside C.62 so I can just switch slots to get back to OOS when I'm done tinkering.
I am pretty sure that my radio will not work (I have a global 9, it's single SIM, and when I tried COS12 I had to use a Magisk module to get my radio back) so being able to switch back easily would be nice.
EDIT: Yeah, there's no way I can convert without nuking. Going to be with my boyfriend this weekend, I'll mess with it on Sunday night when I get back. I'll have to downgrade to 11.2.8.8, upgrade to C.48, unlock the bootloader, convert to COS13, then hope that the Magisk module for OOS12/COS12 works on COS13 to get my radio working again.
Click to expand...
Click to collapse
Alright good luck sir

progerturn said:
Alright good luck sir
Click to expand...
Click to collapse
Ended up figuring it out.
I unlocked the bootloader and used Fastboot Enhance to flash directly from C.62 to F.03. I deleted the cow partitions to make enough room and just directly flashed the payload.bin. Worked perfectly.
Unfortunately, I was correct about the SIM issue. I did indeed have to root and flash the data fix patch to get data. Fortunately, the patch still works fine on COS13. You can even force enable 5G on T-Mobile using the Force 4G LTE app.
I have way too much stuff that I need from my Google backup that I can't restore to COS due to the lack of Google services at boot so I won't be able to daily drive it but it's looking pretty promising. Definitely noticed my phone was running on the warmer side as well though but that is to be expected.
I went ahead and flashed C.48, since that's the most recent full OTA available for NA 9s, over it using Fastboot Enhance (FBE has no qualms about upgrading and downgrading) and that also worked without an issue after I factory reset in fastbootd so if people are wanting to mess with it, they don't have to deal with the whole process of downgrading, flashing COS, then downgrading or MSM to get back.

progerturn said:
ColorOS 13 based on Android 13 has finally arrived for the OnePlus 9 Pro.
It's a Closed Beta version for the moment and therefore unstable (you could potentially encounter some bugs).
If you want a review :
Download Links (please flash at your own risk):
Closed Beta 1 : https://gauss-componentotacostmanua...22/08/05/eb43c65721f14cfead64de23686dd181.zip
I'll update this topic as soon as there is a new release.
Click to expand...
Click to collapse
Do you have link for this closed beta but to OnePlus 9 global?

Gabiru05 said:
Do you have link for this closed beta but to OnePlus 9 global?
Click to expand...
Click to collapse
一加9/ColorOS 13.0.0 F.03 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
Beware that you'll need the Magisk data retention fix on T-Mobile devices and that ColorOS has a lot of bloat. There are also issues with third party app notifications if you want them to wake the display. It ran pretty warm, battery was IDLING at 40C and the CPU was idling about 48~58C (because it doesn't really idle, it's always doing something). For comparison, my 9 running the India C.62 firmware right now is at 28C battery and idling about 30~31C on the CPU.
Also, to install it, you either need to be on C.47 or you need to use Fastboot Enhance (make sure to search the partitions for cow and delete every one of them or you'll brick and have to MSM) to flash over whatever else you're running.

ДDo you have link for OnePlus 8?

kovaljet said:
ДDo you have link for OnePlus 8?
Click to expand...
Click to collapse
This is a OP9 forum.

kovaljet said:
ДDo you have link for OnePlus 8?
Click to expand...
Click to collapse
Hi, check on the OnePlus 8 forums here:
OnePlus 8
The OnePlus 8 is a 6.55" phone with a 1080x2400p resolution display. The Qualcomm SM8250 Snapdragon 865 chipset is paired with 8/12GB of RAM and 128/256GB of storage. The main camera is 48+8+2MP and the selfie camera is 16MP. The battery has a 4300mAh capacity.
forum.xda-developers.com

Is there a way to googlefy Cos13?