Source: https://forum.xda-developers.com/t/...net-test-on-coloros-6-1.4094995/post-82499427
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alright guys. I found a solution! Actually, yes, I just found it but someone else came up with it. As of now I'm running latest RUI on my Realme Q. It's a bit newer (RMX1971_11.C.11, released: 2020/12/27) than the Indian or EU update (RMX1971EX_11.C.08, released: 2020/11/28) but that shouldn't make a difference in our case. I'm now running the above mentioned, stock, official ROM with a few modifications. I migrated from Pixel Experience Android 11 by Bablus by clean flash.
Saved all my data to external SD card.
Cleaned everything in TWRP.
Formatted all partitions to ext4 (since sadly RUI doesn’t support f2fs)
Flashed the official .ozip update file through wzsx’s TWRP that is capable of direct flashing .ozip files (I’m unsure about the TWRP you RM5P guys use though… But you can find this TWRP online or in the group)
Without exiting TWRP, I flashed the TWRP.img as recovery since stock rom overwrites that.
Flashed modified vbmeta.img too for the same reason.
Flashed SilonT Kernel v5 Hana, then Magisk Stable release 21.4
Then formatted data just to make sure.
After first startup when tried to launch Magisk Manager it said it was incorrectly or partially updated, probably because of RUI. It fixed itself by downloading the latest Manager.
As of now SafetyNet fails, both CTS and basicIntegrity, don’t fret.
Download and install from Magisk module repo: MagiskHide Props Config, AR Core/Playground Patcher and lastly Busybox (I’m unsure of this had anything to do with successfully passing the test, probably not but I use it frequently)
Turned on MagiskHide from Magisk settings.
Rebooted the device. After reboot SafetyNet Passes.
Debloating is done though I'm still polishing here and there.
As of now:
Roughly debloated ROM : ✓ Shown in video:
Magisk : ✓ (21.4 stable release)
Busybox : ✓ (Magisk module)
SafetyNet : ✓ (CTS profile & BasicIntegrity)
Custom kernel : ✓ (SilonT Hana v5 release)
Kernel manager : ✓ (SmartPack kernel manager)
Free apk installing without restriction : ✓ (ADB debug: "adb shell pm disable-user --user 0 com.coloros.phonemanager")
Permissive SeLinux : ✓ (turn off MagiskHide, Change Selinux State with The SeLinux switch app, turn MagiskHide back on, check SafetyNet, it'll probably pass. Only works until reboot or till you change selinux state yourself)
Remove recovery rootcheck: ✓ (delete recovery rootcheck and ck.fs files from root/vendor/oppo folder. These files detect if the System is rooted and makes battery consumption higher, also makes the device overheat faster thus subtly prompting the user to revert to unrooted device. Clever Oppo. Very clever.)
Related
Hello, I just figured out what are the differences and made my custom update to get Magisk v14 on the current rom from arceoxis.
Wht i did? I just copied a few files and some lines to the install script.
Download: https://drive.google.com/open?id=0B8MwnzXpkFQhOURiVmpxY1FNSW8
Instructions: flash from TWRP and hope it works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great work! I can confirm that this version can be installed on ResurrectionRemix rom as well. I manage to get xposed v25 installed too.
But whey I do safetyNet check, I see both ctsProfile and basicIntegrity are set as false even though I have switched my SELinux to enforcing mode and removed all SuperSU related stuff based on this android.gadgethacks link. Any ideas how to fix that? or is it an issue?
leonidas1573 said:
Great work! I can confirm that this version can be installed on ResurrectionRemix rom as well. I manage to get xposed v25 installed too.
But whey I do safetyNet check, I see both ctsProfile and basicIntegrity are set as false even though I have switched my SELinux to enforcing mode and removed all SuperSU related stuff based on this android.gadgethacks link. Any ideas how to fix that? or is it an issue?
Click to expand...
Click to collapse
To be honest im new to magisk and i barely know what safetynet is. I just reproduced the work from the rom with the same modifications adapted for the new version.
BTW: Can you BTW confirm if the kernel in RR is the same as the other rom? ([email protected] #1 Fri 8/Sept)
leonidas1573 said:
Great work! I can confirm that this version can be installed on ResurrectionRemix rom as well. I manage to get xposed v25 installed too.
But whey I do safetyNet check, I see both ctsProfile and basicIntegrity are set as false even though I have switched my SELinux to enforcing mode and removed all SuperSU related stuff based on this android.gadgethacks link. Any ideas how to fix that? or is it an issue?
Click to expand...
Click to collapse
Try Universal SafetyNet Patch module, it should solve it.
WARNING : Install it with TWRP, not via magisk update. I did it, I've to reinstall the ROM and all my params...
leonidas1573 said:
Great work! I can confirm that this version can be installed on ResurrectionRemix rom as well. I manage to get xposed v25 installed too.
But whey I do safetyNet check, I see both ctsProfile and basicIntegrity are set as false even though I have switched my SELinux to enforcing mode and removed all SuperSU related stuff based on this android.gadgethacks link. Any ideas how to fix that? or is it an issue?
Click to expand...
Click to collapse
arceoxis said:
Try Universal SafetyNet Patch module, it should solve it.
Click to expand...
Click to collapse
You cannot pass safetynet check with Xposed installed at all.
If you want to pass safetynet, install Magisk only and use the safetynet patch module in magisk, but do not install xposed.
Slow boot & cannot enable Camera2 API systemlessly on recent MIUI Dev ROM [with log]
My whyred is running MIUI 10 China Developer ROM with BL unlocked and OrangeFox R8.3 recovery. After OTA update to 8.11.29, the boot time is slowed down to more than 80 seconds, it used to be about 25 seconds.
If I dirty flash 8.11.23 ROM, the boot time returns to normal, but it becomes slow again if I dirty flash the latest 8.12.6 ROM.
With logcat, I can see it repeats MTServiceDaemon: fs is not ready, waiting (count down)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is part of the log. View attachment 8.12.6_stockREC.txt
And, with newer ROM, I can't enable Camera2 API neither with setprop method, nor with a Magisk module. But they were both working on 8.11.23 and earlier ROM. :crying:
Any suggestions? Thanks in advance
Still slow after OTA update to 8.12.13, almost 90 seconds :crying:
I had the same issue with camera2api and latest Global Beta, After the update i can't enable HAL3, tried with build.prop and Magisk Manager, just returned to Stable ROM.
I'll follow this thread for any solution
N1ck474 said:
I had the same issue with camera2api and latest Global Beta, After the update i can't enable HAL3, tried with build.prop and Magisk Manager, just returned to Stable ROM.
I'll follow this thread for any solution
Click to expand...
Click to collapse
Are you also experiencing a slow boot? Or just can't enable Camera2 API but boots fast?
I can enable Camera2 API by mounting /system RW and manually edit build.prop. I just can't do it systemlessly.
With the setprop method, getprop persist.camera.HAL3.enabled returns 1 in adb shell under OrangeFox recovery, but after a reboot, it returns nothing, the setting is lost.
With a Magisk module, there is no error in log, but it just don't work. While modules moding other files are working, such as WiFi bonding and MiCam V2.
Everything works like a charm if I flash back to 8.11.23 ROM.
I hope someone can help me find the reason.
5460 said:
Are you also experiencing a slow boot? Or just can't enable Camera2 API but boots fast?
I can enable Camera2 API by mounting /system RW and manually edit build.prop. I just can't do it systemlessly.
With the setprop method, getprop persist.camera.HAL3.enabled returns 1 in adb shell under OrangeFox recovery, but after a reboot, it returns nothing, the setting is lost.
With a Magisk module, there is no error in log, but it just don't work. While modules moding other files are working, such as WiFi bonding and MiCam V2.
Everything works like a charm if I flash back to 8.11.23 ROM.
I hope someone can help me find the reason.
Click to expand...
Click to collapse
I don't have problems of slow booting, just Camera2Api, i can't enable it...
I'll retry to install Beta again and enable HAL3 with Orange Fox Recovery
Sent from my Redmi Note 5 Pro using XDA Labs
Captured logcat and dmesg on 8.12.13 ROM, found a line in dmesg saying
Code:
Command 'restorecon --recursive --skip-ce /data' action=post-fs-data (/init.rc:566) returned 0 took 54543ms.
Seems that is quite a long time, but I can't understand these logs. Hope someone would help. Thanks very much.
Here is part of the log.
View attachment 8.12.13_logcat.txt
View attachment 8.12.13_dmesg.txt
use this app to enable HAL3
https://play.google.com/store/apps/details?id=com.proxdz.hal3enabler
This thread well be helpful for users who have Official China Beta or China Stable ROM! I'll made MAGISK Module for Pass Safety NET and use Gpay on this rom without losting OTA on my Redmi K20.
For More detail on my telegram channel MOD EDIT: Link Removed
I tested on my devices MI 9/9T. Everything works as it should. Everything that you do, you do at your own peril and risk!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After flashing Module no need flash Gapps, i already add it to the module! Google Backup system also work!
Tutorial:
1. Download FULL ROM what you have installed on your Device. And flash it via Orang Fox TWRP without wipe.
2. Download module
3. Download Google Pay fix.
4. Remove all the gapps if there are any, and were installed via the Google play installer, install Orange Fox TWRP and flash the full rom for the recovery of your smartphone so that there is support for the future. In device storage you find folder FOX - DONT DELETE IT!!
5. Download Magisk 19.3 and install it, then install module through twrp. DONT UPDATE MAGISK to 20+!!!
6. Make wipes Cache, Dalvik / ART Cache and flash GooglePay-fix.
7. Reboot into the system.
8. Open the Magisk manager and hide only Play services Unstable like on screenshot hide
must be already hiden, if yes - dond hide other apps from google.
Next, go to the modules item and install module again. Reboot smartphone. Download Gpay and enjoy.
IMPORTANT! AFTER EACH OTA, FLASH MAGISk AGAIN, AS IF THE FIXES WERE BEEN CORRECTED IN BOOT.IMG, the magisk unistall automaticaly. After re-installing Magisk, make wipes from point 6. THE MAGISK DOES NOT UPDATE !
Is it still working on MIUI 12.5 China Beta Rom?
THREAD LOCKED
On account of no valid download link available.
Regards,
shadowstep
Forum Moderator
Hello Guys,
I was trying to install Nethunter On my OnePlus 7T Europe with Android 10
10.0.9-EUROPE-OnePlus7TOxygen_14.E.11_OTA_011_all_2003271950_b7c5bfe612-FASTBOOT.zip using following instruction:
Installing NetHunter On the OnePlus 7 | Kali Linux Documentation
From a reset to running NetHunter in 4 steps: Flash latest Android 10 with the unbrick tool Flash TWRP and Magisk Disable force encryption of data partition Install NetHunter Disable OnePlus update service 1. Flash latest stock (OOS) Android 10 1.01. Download and unzip...
www.kali.org
But I had used:
Twrp:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
eu.dl.twrp.me
Magisk:
Release Magisk v23.0 · topjohnwu/Magisk
This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...
github.com
I am unable to install with error from screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Error Failed to mount /system_ext also appears on Magisk and decrypt tool installation.
I saw that a lot of people have seen this, but no one has commented, so I'll just throw you a few guesses. 1. Possibly a bad download of either Kali or your Recovery. 2. However, you said it happens with Magisk too, so I'm thinking it also might be the wrong recovery, are you sure that you have the right recovery.img for your model number? And if so, is it a reliable recovery.img? I know that there is guacamole, guacamoleb, hotdog and hotdogb and there were a handful of unstable TWRP builds due to the force encryption. More information about your device and resources would help, what's your model number, what version of platform tools are you on?
P.s. I'm also assuming that the photo of the log isn't of an instance where you were flashing it through Magisk as a module because you said it happens with Magisk too.
P.s.2 I know you said your phone is the Europe variant, but I'd assume not to many people memorize every model number for devices that they don't own, I'd say that's why we have codenames like guacamole, lol.
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
stefan_at_localhost said:
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
Click to expand...
Click to collapse
You'll want to use fastboot to boot recovery (not flash)
And install the recovery via the on device gui
Also, I would use orangefox recovery, it was built from twrp, but has more features.
Use "method 2" in this guide:
https://theandroidrush.com/how-to-flash-orangefox-recovery-on-xiaomi-phone/
Hi,
I flashed the patched magisk boot via orangefox, but no success. Magisk still N/A
Step1: Patch boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step2: Flash via TWRP or Orangefox
no screenshot available
Step3: Result, no Magisk (N/A)
I don't understand this. Is there a greater change in MUI14?
I also installed the Magisk APK via TWRP and Orangefox, but no other result.
Thanks,
Stefan
After serveral hours of debugging I found out, that there was a post on the net, which recommended to install the debug version of Magisk. This was a first step into the right direction. But the GUI crashed and removed the Magisk App.
The strange thing was, that all other whitelisted root apps worked. But no access to change the Whitelist.
So I tried to get the GUI back. But there was no way.
When I installed the APK, it was automatically killed and removed :/
After reinstalling via the xiaomi.eu repair (update) script I decided to to try an older Magisk Version (26.0). This crashed also, but I was able to re-run the app again.
Finally it seems that Magisk implemented a change, that crashes with my MIUI version. I will observe this and try to file a bug report.