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.
Related
Hi guys,
Hoping my noob self can get some guidance here.
Basically i followed this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
But after doing so it seems that Magisk isnt working.
Is there anything i can do; installing a CROM, any work arrounds?
I've tried this as well but no avail: https://forum.xda-developers.com/apps/magisk/safetynet-fix-pass-safetynet-2017-07-17-t3637801
ChrisChan92 said:
Hi guys,
Hoping my noob self can get some guidance here.
Basically i followed this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
But after doing so it seems that Magisk isnt working.
Is there anything i can do; installing a CROM, any work arrounds?
I've tried this as well but no avail: https://forum.xda-developers.com/apps/magisk/safetynet-fix-pass-safetynet-2017-07-17-t3637801
Click to expand...
Click to collapse
Google has just updated the play store, there is a topic on here with the commands you need to execute via adb or command prompt in order to get magisk working properly, but seems you already did that, what version of magisk and magisk manager are you using
sakumaxp said:
Google has just updated the play store, there is a topic on here with the commands you need to execute via adb or command prompt in order to get magisk working properly, but seems you already did that, what version of magisk and magisk manager are you using
Click to expand...
Click to collapse
I'm using Magisk v12.0 and Manager v5.05
Magisk 13.2 gives me a system could not be mounted error
ChrisChan92 said:
I'm using Magisk v12.0 and Manager v5.05
Magisk 13.2 gives me a system could not be mounted error
Click to expand...
Click to collapse
Then go into mount, check system then recheck it, that used to fix it for me
sakumaxp said:
Then go into mount, check system then recheck it, that used to fix it for me
Click to expand...
Click to collapse
I've tried it multiple times, even rebooting in between
The Pixel doesn't use the official version of Magisk so any instructions for how to get the official version working might not apply on the Pixel. For a while if you enabled core only mode in the unofficial version the Pixel would still pass Safety Net even though the official version had stopped working. I have no idea if this workaround still works or not since I went back to stock but if you haven't tried it yet its certainly worth a try. Since the official link for the unofficial Pixel version of Magisk is hosted in the Resurrection Remix rom thread and discussion of Magisk issues frequently goes on there as well you might want to check the later posts in the rom thread and see if there is updated info regarding unofficial Magisk.
jhs39 said:
The Pixel doesn't use the official version of Magisk so any instructions for how to get the official version working might not apply on the Pixel. For a while if you enabled core only mode in the unofficial version the Pixel would still pass Safety Net even though the official version had stopped working. I have no idea if this workaround still works or not since I went back to stock but if you haven't tried it yet its certainly worth a try. Since the official link for the unofficial Pixel version of Magisk is hosted in the Resurrection Remix rom thread and discussion of Magisk issues frequently goes on there as well you might want to check the later posts in the rom thread and see if there is updated info regarding unofficial Magisk.
Click to expand...
Click to collapse
Ressurection Remix is a custom rom? Do you know if it works with Pixel? Because i'm fine with installing custom rom its not a must for me to have stock
ChrisChan92 said:
Ressurection Remix is a custom rom? Do you know if it works with Pixel? Because i'm fine with installing custom rom its not a must for me to have stock
Click to expand...
Click to collapse
Resurrection Remix is a custom rom but there is no need to install it to use Unofficial Magisk. That's just where the official download link is hosted, probably because the dev has some link to that particular rom. But Unofficial Magisk is not included or integrated in any way into that rom--Magisk is downloaded and flashed separately from the rom and should work the same on that rom, a different custom rom or stock.
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
As a side note there's nothing wrong with Resurrection Remix but if you did want to give a custom Rom a try I would personally recommend Dirty Unicorns or Screwed. They aren't hosted on XDA but don't let that bother you. A quick Google search will turn up where they are officially hosted and in my personal experience they are easily the best custom Roms available for the Pixel. That said, I went back to stock so I could try Android O and have stayed on stock so far.
jhs39 said:
Resurrection Remix is a custom rom but there is no need to install it to use Unofficial Magisk. That's just where the official download link is hosted, probably because the dev has some link to that particular rom. But Unofficial Magisk is not included or integrated in any way into that rom--Magisk is downloaded and flashed separately from the rom and should work the same on that rom, a different custom rom or stock.
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
As a side note there's nothing wrong with Resurrection Remix but if you did want to give a custom Rom a try I would personally recommend Dirty Unicorns or Screwed. They aren't hosted on XDA but don't let that bother you. A quick Google search will turn up where they are officially hosted and in my personal experience they are easily the best custom Roms available for the Pixel. That said, I went back to stock so I could try Android O and have stayed on stock so far.
Click to expand...
Click to collapse
Only because I just found out, screwed doesn't support Pixel Google Photos Unlimited Upload at Original
pcriz said:
Only because I just found out, screwed doesn't support Pixel Google Photos Unlimited Upload at Original
Click to expand...
Click to collapse
That's true but it's probably temporary. The devs have been notified of that bug and they are usually pretty responsive. I could actually see Google changing their code to deny the unlimited original photo backup to Pixels that are altered--i.e. unlocked bootloader, root, custom recovery or custom rom since Google has made it pretty clear they don't want people doing these things on the Pixel, but I haven't read anything that indicates Google has done this. But don't be surprised if they do it in the future.
jhs39 said:
That's true but it's probably temporary. The devs have been notified of that bug and they are usually pretty responsive. I could actually see Google changing their code to deny the unlimited original photo backup to Pixels that are altered--i.e. unlocked bootloader, root, custom recovery or custom rom since Google has made it pretty clear they don't want people doing these things on the Pixel, but I haven't read anything that indicates Google has done this. But don't be surprised if they do it in the future.
Click to expand...
Click to collapse
I feel like the roms where it is working is just a matter of something NOT being changed in them and needing to find the delta but I agree I wouldn't be surprised if they look the stance of purposefully not allowing modded devices.
pcriz said:
I feel like the roms where it is working is just a matter of something NOT being changed in them and needing to find the delta but I agree I wouldn't be surprised if they look the stance of purposefully not allowing modded devices.
Click to expand...
Click to collapse
I'm not a programmer and can't say for sure but you might be right. I think the devs at Screwed (if I remember correctly) are the ones who say they create as lean of a rom as possible by removing useless code. They might have removed something they shouldn't have. It's still an excellent rom but that is a serious bug for people who rely on the photo at full quality backup feature and take a lot of pics.
i bought a razer phone and its the mail now. the seller told me that it was on the stock razor ROM. I plan on rooting it and installing TWRP but I was wondering if I should stay on the stock ROM or if was worth going to the trouble to install a custom ROM?
Aosp 8.1 or Stock + root are most stable and don't have broken features
Any pie gsi without root should work but might need a quick WiFi fix
SeriousFlash said:
Aosp 8.1 or Stock + root are most stable and don't have broken features
Any pie gsi without root should work but might need a quick WiFi fix
Click to expand...
Click to collapse
thank you. would you suggest the aosp from this post? https://forum.xda-developers.com/razer-phone/how-to/treble-install-generic-image-gsi-razer-t3770684
or what pie gsi would you suggest?
edit, update: this is a list of pie gsi's i found
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I would agree with @SeriousFlash, any 8.1 GSI or Stock plus Magisk 17.1 is a good bet.
I had Pixel Experience 8.1 (https://forum.xda-developers.com/pr...-development/8-1-0-pixel-experience-t3796011) for a while, great looking ROM with nice features. I had some trouble with Bluetooth but that doesn't seem to be a common experience...
If you want Magisk, all the Pie ROMs will break in some way - no data. WiFi, Bluetooth etc.
Just one thing, I have never actually installed TWRP, just loaded it temporarily via fastboot. I do it this way just because of some of the bad luck stories I've read when folks have flashed it permanently. YMMV.
Peace.
chris5s said:
I would agree with @SeriousFlash, any 8.1 GSI or Stock plus Magisk 17.1 is a good bet.
I had Pixel Experience 8.1 (https://forum.xda-developers.com/pr...-development/8-1-0-pixel-experience-t3796011) for a while, great looking ROM with nice features. I had some trouble with Bluetooth but that doesn't seem to be a common experience...
If you want Magisk, all the Pie ROMs will break in some way - no data. WiFi, Bluetooth etc.
Just one thing, I have never actually installed TWRP, just loaded it temporarily via fastboot. I do it this way just because of some of the bad luck stories I've read when folks have flashed it permanently. YMMV.
Peace.
Click to expand...
Click to collapse
I just got my razer phone not long ago as well.
So just to clarify... If I want data, wifi, Bluetooth etc to function as they should then I should temporally load TWRP and use 8.1 GSI (e.g. Lineage 15.1 from here) with Magisk as an option for root?
-SKYLINE- said:
I just got my razer phone not long ago as well.
So just to clarify... If I want data, wifi, Bluetooth etc to function as they should then I should temporally load TWRP and use 8.1 GSI (e.g. Lineage 15.1 from here) with Magisk as an option for root?
Click to expand...
Click to collapse
Yes.
Magisk breaks those things on Android 9/Pie. If you don't use Magisk then give them a go. There are versions of Pie which are already rooted without Magisk, check the threads to see.
Otherwise Magisk seems to work with 8.1 ROMs without issue :good:
Peace
-SKYLINE- said:
I just got my razer phone not long ago as well.
So just to clarify... If I want data, wifi, Bluetooth etc to function as they should then I should temporally load TWRP and use 8.1 GSI (e.g. Lineage 15.1 from here) with Magisk as an option for root?
Click to expand...
Click to collapse
xda has a treble dev forum so you could try this link for more roms
https://forum.xda-developers.com/project-treble
ive been using my phone for a few days now and im still on the stock rom. has anyone tried xposed or maybe have a suggestion for magisk to get some more customizations like qs edit or advanced reboot?
update. im using xposed, gravitybox and magisk 18 now
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.
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. ^^