Related
Q: Can I use Substratum even if my ROM does not have OMS support?
A: Yes, under the following conditions:
It must be a close to stock/AOSP ROM. Some users report OxygenOS works, others don't. Other stock firmwares will most likely not work
If you are on a firmware that is on the November security patch or later, they MUST have patched it using this commit: http://review.projektsubstratum.com/#/c/153/. Without this, the Android overlay (framework) will bootloop your phone and you must flash the rescue zip
Click to expand...
Click to collapse
Has anyone made any experience with substratum on stock OOS 3.5.5/6/7 on the OnePlus 2? If yes, which theme do you use? Would try it myself but the November security patch thing worries me
An experimental version has been released I tried it on RR with magisk version most apps force closed can others try on other custom rom perhaps aosp and stock 7.1 and please report success that would be great
Link https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
Yup, it's all working good on Dirty Unicorns ROM. I have flashed the regular ARM version and not the Magisk one though. This has caused the SafetyNet test to fail.
Also anyone trying this do make a note that most of the Xposed modules haven't been updated in a long time(well, because Xposed for Nougat wasn't available until today), so there is a good chance you'll run into errors and other problems. But it's still great that Xposed is finally out for Nougat.
Huge thanks to the PurifyOS Team for this.
Edit: a lot of apps are crashing after installing this. And the original developer of Xposed, rovo89, has advised not to use this on a daily basis and you'll face many app crashes. And not many modules work. So until modules are updated and Xposed reaches a stable state, it's advised to not use it.
Hi all RR users & moderators
As you guys know xposed has released a beta version which requires some modifications in the ROM sources .
Just to let you guys know , none of the team members will support xposed or any of its modules for RR N
Why?
Many reasons .
- It causes issues with ROM features and breaks several of them
- Its hard to keep track of bugs and difficult to know what causes the issue if you are facing any
- It will be difficult to maintain ROM source with the constant changes
- Xposed is still beta and it does not have an uninstaller yet .
To sum this up , NO bug reports with xposed will be entertained . all future bug reports HAVE to come with a log if we find any traces of xposed in the log , it will be discarded . Any bug reports without logs will be discarded as well .
NO OFFICIAL SUPPORT FOR XPOSED so please do not request for xposed support
Thank you and have a great weekend
#Getresurrected
Sincerely
Team RR
Original Source Facebook Official Page
Read on XDA it will be included in some ROMs by default so I guess it a matter of choosing a ROM with it baked in in a working state? Link https://www.xda-developers.com/art-...1-2-adds-xposed-functionality-to-custom-roms/
Subins Mani said:
- Xposed is still beta
Click to expand...
Click to collapse
It's not even beta, a beta would be more stable
Much more stable the new magisk version of xposed
digiscales said:
Much more stable the new magisk version of xposed
Click to expand...
Click to collapse
What rom are you using?? In my xt1541 AEX rom it just stuck on boot animation when i flash xpose..i have tried classic and magisk but still my device wont boot up
RR on osprey my moto x is broken I read aex has problems i could get it to boot try RR or aosp close ROM or lineage os let me know as well how it goes might be useful if I can get moto x.repaired
What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)
Universal SafetyNet Fix
Magisk module
Magisk module to work around Google's SafetyNet attestation.
This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
If you still have trouble passing SafetyNet with this module, use MagiskHide Props Config to spoof a certified device profile. This is a common issue on old devices, custom ROMs, and stock ROMs without GMS certification (e.g. Chinese ROMs).
Android versions up to 13 Beta 3 are supported, including OEM skins such as Samsung One UI and MIUI.
How does it work?
The way this workaround works is relatively low-level. An in-depth explanation, as well as source code and ROM changes, can be found on GitHub.
Ideally, this workaround should be incorporated in custom ROMs instead of injecting code with a Magisk module. See the ProtonAOSP website for more information.
Downloads
Downloads and changelogs can be found on GitHub. The topmost release is the latest.
Latest release
v2.4.0
Spoiler: Changelog
Highlights
Play Integrity bypass without breaking device checks or causing other issues
Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
Other changes
Updated instructions for newer Android and Magisk versions
Better debugging for future development
This version only supports Zygisk (Magisk 24 and newer).
It's taken a while to find a way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!
If you found this helpful, please consider supporting development with a recurring donation for rewards such as early access to updates, exclusive behind-the-scenes development news, and priority support.
Alternatively, you can also buy me a coffee. All support is appreciated
Source code
Note 8 pro Android 9 and Android 10 not working
Tested succesfully on Pixel 4a 5G, but Google Pay says "Your phone doesn't meet security requirements" even though PayPal can be set up.
Magisk Hide is activated.
Magisk says SafetyNet passes but Google Pay still doesnt
Dydnlee said:
Note 8 pro Android 9 and Android 10 not working
Click to expand...
Click to collapse
Please test it again with this version: https://github.com/kdrag0n/safetynet-fix/archive/e82c3d0674e6452938e49bc6ee6848aa2a603c27.zip
[QUOTE = "kdrag0n, gönderi: 84286879, üye: 7291478"]
Lütfen bu sürümle tekrar test edin : https://github.com/kdrag0n/safetynet-fix/archive/e82c3d0674e6452938e49bc6ee6848aa2a603c27.zip
[/ALINTI]
İnstall failed
Thank you a lot, Universal SafetyNet Fix v1.1.0 working excellent on Xiaomi Mi 9T, Xiaomi.eu 21.1.6, MIUI 12.5 / Android 11 Beta
Device certified but not using Google Pay
Safety net fix 1.0.2 worked for miui Eu 12.0.3.0 Android 10 for Poco F1.
Only that the ocbc bank Singapore app still able to detect the root and became unusable.
But I know that this doesn't relate to safetynet fix here because the issue already existed before the CTS false.
tylerdurden said:
Tested succesfully on Pixel 4a 5G, but Google Pay says "Your phone doesn't meet security requirements" even though PayPal can be set up.
Magisk Hide is activated.
Click to expand...
Click to collapse
Clear app data from Google pay aswell as Google play services.
Tested on Samsung S9:
- 1.0.2 worked in MM, but Root Checker said 'cannot access GPS'.
- 1.1.0 fails ctsProfile in MM, but Root Checker now can access GPS, also returns ctsProfile fail.
Massive thanks for this. Version 1.1.0 confirmed working on my device:
- Pixel 3, stock room
- Magisk 21.2, magisk manager 8.0.5
- Magisk hide enabled and magisk manager renamed
All banking apps and google pay work correctly, including contactless payments.
working on poco f2 pro,android 11,rom one os thanks
Tested on Huawei Mediapad M5 with EMUI 9.1.0 and Magisk 20.4:
- 1.1.0 fails ctsProfile in MM, basic integrity is ok
Working OK on Mi Note 10 Lite, Android 10 and ROM xiaomi.eu
Thanks
I tried this on my Samsung Galaxy A6 (official samsung firmware patched with magisk) - and even version 1.1.0 causes bootloop when using zip inside Magisk Manager - Android 10
Good morning. Working on Redmi Note 9 Pro xiaomi.eu 12.0.1 Android 10. No MagiskHide Props Config needed: basicIntegrity passed, ctsProfile passed, evalType BASIC.
Thank you so much
MI10 Global with V12.2.8 xiaomi.eu , used V 1.0.2 works
Thank you!
Works on pixel 3a, last A10 patch, using magisk hide props config to force basic attestation. Was already using mhpc so not sure if it works without it. Fixed my CTS issue though, so thanks!
@kdrag0n Thank you so much for this awesome masterpiece!
I find it a bit interesting, that I experience a problem which nobody else seems to have reported so far. I'm using a Galaxy S10 (Exynos, G973F), rooted with latest canary Magisk, no EdXposed or whatsoever...
If I enable this module, no bootloop, basic attestation, CTS passes. "Yes", so I thought...
The problem now... My bank app tries to access the keystore and crashes. This does not happen without having this module enabled... I have attached a fully logcat and hope that you have some insights...
EDIT1: re-attached file, didn't work on the first go.
EDIT2: oh... search for "easybank" or "keystore"
EDIT3: Android 11, One UI 3
POCO F1 user here. After flashing the module the phone stucks on the Google logo at boot.
The MHPC module didn't solve the problem either.
ROM: Pixel Experience 11 Beta (20201223)/Encrypted
Hi,
I'm planning to flash CarbonROM to my OP8P and wondering if the ROM comes with the following.
DRM Info - Security Level L1
YASNAC Safetynet - Basic Integrity & CTS profile match
I don't want to root my device, but still want to enjoy custom ROM with banking apps.
I've tried different profile for banking apps, but not quite satisfied.
Thanks
If you've got any of the 8 series. Just install EvoX.