In order to be able to run Charter Spectrum, (and other television streaming applications) I've been looking to use some of the more sophisticated root-hiding technologies made available by newer versions of Magisk. I'm currently on version 23 of Magisk itself, and 24.1 of the app, but afraid to go any higher with either due to reports of non-boot conditions or incompatibility with newer versions of the Magisk app itself.
Has anyone been brave enough to try current versions of Magisk with Alpha/Omega Rom and MK2000 kernel (or other comparable custom kernels)? If so, did you have a similar problems, (no-boot, Magisk app ceasing to function, etc.) did it work perfectly, or was there some other outcome?
Your input is very much welcomed!
Bill720 said:
In order to be able to run Charter Spectrum, (and other television streaming applications) I've been looking to use some of the more sophisticated root-hiding technologies made available by newer versions of Magisk. I'm currently on version 23 of Magisk itself, and 24.1 of the app, but afraid to go any higher with either due to reports of non-boot conditions or incompatibility with newer versions of the Magisk app itself.
Has anyone been brave enough to try current versions of Magisk with Alpha/Omega Rom and MK2000 kernel (or other comparable custom kernels)? If so, did you have a similar problems, (no-boot, Magisk app ceasing to function, etc.) did it work perfectly, or was there some other outcome?
Your input is very much welcomed!
Click to expand...
Click to collapse
Hello, your on the latest version that works with Oreo 8.0 at this time. Magisk 25.2 does not work. When I installed Magisk 25.2 app, it would not open. So I just uninstalled the Magisk app and reinstalled a lower version and that fixed it. I am also running Stock Oreo 8.0 ezV2020 kernel.
Darnrain1 said:
Hello, your on the latest version that works with Oreo 8.0 at this time. Magisk 25.2 does not work. When I installed Magisk 25.2 app, it would not open. So I just uninstalled the Magisk app and reinstalled a lower version and that fixed it. I am also running Stock Oreo 8.0 ezV2020 kernel.
Click to expand...
Click to collapse
Thanks for the datapoint. Can a newer version of Magisk itself be used with version 24.1 of the app?
Bill720 said:
Thanks for the datapoint. Can a newer version of Magisk itself be used with version 24.1 of the app?
Click to expand...
Click to collapse
I was mistaken, version Magisk-v24.3.apk is the latest version that will work with the Lgv20 Stock Oreo. And Magisk 24.3 would be the latest version. Just install the apk file from GitHub. Do direct install. I just updated my Lgv20 and it works.
Darnrain1 said:
I was mistaken, version Magisk-v24.3.apk is the latest version that will work with the Lgv20 Stock Oreo. And Magisk 24.3 would be the latest version. Just install the apk file from GitHub. Do direct install. I just updated my Lgv20 and it works.
Click to expand...
Click to collapse
Indeed. The version 24.3 apk installed beautifully, and version 24.3 of Magisk did the trick as well. Unfortunately, after enabling Zygisk and restarting, the device now hangs indefinitely on the boot animation .
Bill720 said:
Indeed. The version 24.3 apk installed beautifully, and version 24.3 of Magisk did the trick as well. Unfortunately, after enabling Zygisk and restarting, the device now hangs indefinitely on the boot animation .
Click to expand...
Click to collapse
I never enabled Zygisk, Do you have a backup of your boot image in twrp? I would re flash the boot image. Or you can try to boot into twrp and run Magisk-uninstaller-20210117.zip Then install the Magisk apk again to get Magisk installed.
Darnrain1 said:
I never enabled Zygisk, Do you have a backup of your boot image in twrp? I would re flash the boot image. Or you can try to boot into twrp and run Magisk-uninstaller-20210117.zip Then install the Magisk apk again to get Magisk installed.
Click to expand...
Click to collapse
I followed a bunch of rabbit trails on this one. Tried disabling Xposed Framework because someone said that it might interfere with Zygisk. No change. Tried disabling all of the Magisk modules, but it still hung. Finally, I did the rename-magisk-apk-file-to-uninstaller.zip trick and uninstalled it through TWRP. The device still hangs on boot. I'm thoroughly regretting this experience right about now. The V20 might just be toast.
Update: it did boot up eventually after uninstalling Magisk completely. I'll have to revisit this later in the day.
Phew! It's back in service. Enabling Zygisk is definitely the thing that causes it to incompletely boot, however.
Update: And it's gone again. I tried enabling Zygisk a second time, but now, I cannot uninstall Magisk from within TWRP any longer because it can't mount /data. It can't mount data because device encryption is enabled. I tried using the "locksettings clear --old xxxx" adb shell command, but it is not accepted:
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder com.android.internal.widget.ILockSettings.asBinder()' on a null object reference
at com.android.commands.locksettings.LockSettingsCmd.onRun(LockSettingsCmd.java:62)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
at com.android.commands.locksettings.LockSettingsCmd.main(LockSettingsCmd.java:50)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:284)
Click to expand...
Click to collapse
Any ideas here, anybody, or am I totally screwed?
Bill720 said:
Phew! It's back in service. Enabling Zygisk is definitely the thing that causes it to incompletely boot, however.
Update: And it's gone again. I tried enabling Zygisk a second time, but now, I cannot uninstall Magisk from within TWRP any longer because it can't mount /data. It can't mount data because device encryption is enabled. I tried using the "locksettings clear --old xxxx" adb shell command, but it is not accepted:
Any ideas here, anybody, or am I totally screwed?
Click to expand...
Click to collapse
That's so odd because I enabled Zygisk on my phone and it booted but I did not have xposed installed. If the data partition is encrypted the only way I know of getting rid of that is to do a format in twrp. That will erase everything on the phone. I don't have any ideas maybe some one will chime in.
Related
Just like the topic says. I'm currently running Magisk 11.6 and was told not to install or upgrade to v 12 since it was buggy. Well it looks like v13 is available (13.1 actually). Is this safe to upgrade?
Rom: NATF 4.0 for H910 (AT&T) - Android v7.0
Sidenote: What is preventing SafetyNet from passing (CTS Profile mismatch) ? Is the due to the DirtyCow exploit? Debugging is disabled and Magisk hide is on.
is definitely safe if you have a US996 variant of the LGV20 as I'm using it on that... about to try it out on my H918 variant of the LGV20, but should be fine with since I went through all the betas fine
I flashed 13beta on my h918 without doing anything special and it works just fine
Well I took the advice and upgraded. It didn't go so smooth. The update feature within Magisk manager didn't work. First it didn't let the device reboot. I had to pull the battery since all the shutdown commands did nothing.
2nd time trying to upgrade, it rebooted this time and when I checked the manager again it said magisk wasn't even installed. So I manually got the zip and updated in recovery and then manually installed the latest apk for the manager and finally I'm up to date. All is well (aside from safetynet).
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
shadavis08 said:
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
Click to expand...
Click to collapse
I completely overlooked the uninstaller. I don't know how, I just did.
Updated to 13.2 and SafetyNet seems to pass now. Although I'm still "Uncertified" in the Play store.
Well goddamn, it must be working because I was able to get Google Wallet to work and Android Pay lets me add a card, although it says my card is not supported. I don't have a second card currently to test it. Maybe I need to enable it on the banks end. I'll call them tomorrow and ask.
Edit: Nope. It's my bank, not the card.
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix
Ok so I've been having a hell of a time with this phone so far. I have the boost mobile variant (xt1766). I unlocked the bootloader, installed twrp, but forgot to make a backup before flashing supersu, after which my phone would no longer boot so I flashed lineageOS. It booted up fine but I had no 3g connection so I wanted to go back to stock. I downloaded the stock firmware, but couldn't get RSD lite to install on my computer so I extracted all the files and flashed them manually with fastboot. After that my phone wouldnt boot and TWRP couldnt mount the data partition so I couldnt restore my lineage backups. I had to format the data partition in order to restore from backup but now I have nothing on internal storage, and my phone wont boot into system unless I boot into factory mode from the bootloader. It boots up fine in factory mode but now I have no network connection, no service whatsoever.
Under sim status it says Network: unknown, cellular network type: unknown, Service state: Radio Off, etc. I tried manually turning the radio on but that didn't work. I really just want to go back to stock but I don't understand how to accomplish this. I flashed everything in the firmware package in the correct order, and somehow it just rendered my phone useless. any help would be much appreciated. I've tried just about everything and I'm at a loss here.
Update:
I successfully got back to stock. For some reason executing the fastboot commands manually one at a time didn't work so I made a bat file with all the proper commands, executed it, and this time it worked. Not sure why it didn't work the other way but it might be because I didn't flash the stock recovery so as not to replace TWRP. Apparently when flashing firmware its all or nothing.
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
AMShiech said:
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
Click to expand...
Click to collapse
Not "lame" unless that's the latest descriptor for a reliable, fully functional, device optimized ROM that just works. If you want additional bling/tweaks flash Xposed framework and a few well regarded modules like GravityBox.
Alternatively, you can cycle through the various custom ROMs and decide which suite of compromises you're willing to live with. Suggest a careful read of the relevant ROM thread before diving in. Be sure to backup what works (including stock!) and store those nandroids on a SD card and/or off-device.
Good luck.
AMShiech said:
Update:
I successfully got back to stock. For some reason executing the fastboot commands manually one at a time didn't work so I made a bat file with all the proper commands, executed it, and this time it worked. Not sure why it didn't work the other way but it might be because I didn't flash the stock recovery so as not to replace TWRP. Apparently when flashing firmware its all or nothing.
Are there any custom ROMs with 3G functionality for this device? Cuz so far every single one I've tried gets no network connection but this stock ROM is lame.
Click to expand...
Click to collapse
That's because you're on boost, not many ROMs here have CDMA support. There is a fix in the help section. But stock is fine for me. Gravitybox and all features of any of the broken unofficial ROMs are all there. Rock solid, and LTE. But flash away dude.
madbat99 said:
That's because you're on boost, not many ROMs here have CDMA support. There is a fix in the help section. But stock is fine for me. Gravitybox and all features of any of the broken unofficial ROMs are all there. Rock solid, and LTE. But flash away dude.
Click to expand...
Click to collapse
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
AMShiech said:
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
Click to expand...
Click to collapse
No, regular Xposed. Wipe cache and dalvik, and wait. Let it sit 5 - 10 minutes. It has to optimize everything. Make sure it's the arm build. It works fine, just gotta let it sit. First boot takes a good bit.
Or use magisk, and install Xposed through that.
Do not use that old purity crap. That's why the links are dead. It's old crap. Xposed works fine with no extra steps or messing with selinux.
AMShiech said:
I haven't been able to install the Xposed framework. Xposed installer says my CPU architecture is incompatible. When I flashed Xposed v89 for nougat my phone wouldn't boot past the boost logo. I keep hearing about people getting Xposed working on this device but I can't figure out how they're doing it. I would love to be able to have gravity box on this ROM.
Apparently the purityOS guys made an unofficial work around a while back but all the download links in that thread are dead and I can't find it anywhere else. It's my understanding that i need to be able to set selinux to permissive on boot in order to install Xposed.
Click to expand...
Click to collapse
That's BS; don't overcomplicate things. Xposed framework installs fine in enforcing mode. Make sure you have the correct framework for Android 7.1 (SDK 25) and your hardware (arm). You will also need the corresponding management app. There is no need to wipe anything before/after flashing the framework although doing so can't hurt. First boot will take awhile; patience is a virtue.
Got Xposed working now with gravitybox and edge in full effect so this stock ROM is now much more tolerable. I guess I had the wrong version of Xposed installer and didn't wait long enough for boot to finish.
It broke safetynet though which I fully expected. I'd rather use the systemless Xposed magisk module so I can pass safetynet but I can't get any magisk modules to install successfully either through magisk or by flashing with TWRP. Apparently I'm not the only one having this issue either and it doesn't look like anyone has found a fix for it as of yet. I guess for now I'll have to live without Pokemon go lol
AMShiech said:
Got Xposed working now with gravitybox and edge in full effect so this stock ROM is now much more tolerable. I guess I had the wrong version of Xposed installer and didn't wait long enough for boot to finish.
It broke safetynet though which I fully expected. I'd rather use the systemless Xposed magisk module so I can pass safetynet but I can't get any magisk modules to install successfully either through magisk or by flashing with TWRP. Apparently I'm not the only one having this issue either and it doesn't look like anyone has found a fix for it as of yet. I guess for now I'll have to live without Pokemon go lol
Click to expand...
Click to collapse
Well yes there is most definitely a fix. Your problem is the f2fs loopback bug. Your solution is the f2fs loopback bug workaround module. It's in the magisk manager app. Download there, but install it in twrp. Then magisk modules will work. You must have halted your research a little early because this is well known, and posted in many places.
You still won't pass safetynet with systemless Xposed. Which a little reading would have also revealed. But, you can turn off Xposed in magisk , then reboot and pass safetynet. Do whatever it is you need safetynet for, then turn it back on and reboot. You must completely uninstall the Xposed you have to use magisk Xposed. You must use the Xposed installer APK that's linked in Xposed for magisk so it recognizes systemless Xposed. So uninstall Xposed with uninstaller zip, uninstall Xposed APK. Wipe caches. Then you can just go in magisk manager, scroll to the bottom of downloads, install Xposed sdk 25 module. Also Xposed installer APK linked 8n the readme that pops up when you click the Xposed module in magisk downloads. See screenshots below.
Also, there is more to pogo than safetynet. There is an entire thread devoted to it (more than one) in the magisk section of the forum.
You have a bit of reading to do in order to do the things you want. It's all very easy to find. You don't seem to be looking very hard.
madbat99 said:
Well yes there is most definitely a fix. Your problem is the f2fs loopback bug. Your solution is the f2fs loopback bug workaround module. It's in the magisk manager app. Download there, but install it in twrp. Then magisk modules will work. You must have halted your research a little early because this is well known, and posted in many places.
You still won't pass safetynet with systemless Xposed. Which a little reading would have also revealed. But, you can turn off Xposed in magisk , then reboot and pass safetynet. Do whatever it is you need safetynet for, then turn it back on and reboot. You must completely uninstall the Xposed you have to use magisk Xposed. You must use the Xposed installer APK that's linked in Xposed for magisk so it recognizes systemless Xposed. So uninstall Xposed with uninstaller zip, uninstall Xposed APK. Wipe caches. Then you can just go in magisk manager, scroll to the bottom of downloads, install Xposed sdk 25 module. Also Xposed installer APK linked 8n the readme that pops up when you click the Xposed module in magisk downloads. See screenshots below.
Also, there is more to pogo than safetynet. There is an entire thread devoted to it (more than one) in the magisk section of the forum.
You have a bit of reading to do in order to do the things you want. It's all very easy to find. You don't seem to be looking very hard.
Also I certainly hope that's not the app I think it is (the smiley face)? You're not allowed to promote or speak of that "warez" here. So screenshot is not a great idea.
Click to expand...
Click to collapse
I'm well aware that the problem is f2fs loopback but due to the bug I'm unable to install the fix. Can't install magisk modules so a fix in the form of a magisk module doesn't really help me. Ive tried installing it with TWRP a couple times with no success. As far as PoGo I've actually never even played that game. Was just curious about it.
And I'm not sure what app you're referring to but that "wow" face is a chrome shortcut. Changed it cuz I didn't like the default grey square.
AMShiech said:
I'm well aware that the problem is f2fs loopback but due to the bug I'm unable to install the fix. Can't install magisk modules so a fix in the form of a magisk module doesn't really help me. As far as PoGo I've actually never even played that game. Was just curious about it.
Click to expand...
Click to collapse
Trend continues; reread post you're disparaging. Or module OP. f2fs loopback 'fix' gets flashed in twrp or via fastboot (for the adventurous).
I edited my post shortly after your quote. Tried installing with TWRP more than once. Doesn't show up in magisk modules.
Just flashed with fastboot and now it seems to have worked. Fastboot for the win.
Maybe all caps will help out
go inside magisk manager> downloads search F2FS LOOPBACK BUG WORKAROUND, FLASH INSIDE TWRP!!! WILL NOT WORK IF ATTEMPTED TO FLASH THROUGH MAGISK MANAGER!!!!
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
maraschino said:
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
Click to expand...
Click to collapse
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Just updated mine via app , after reboot there was no signal , no simcard ,no imei dont panic reboot one more time ,and everything is working as usual.
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
maraschino said:
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
Click to expand...
Click to collapse
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
KOLIOSIS said:
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
Click to expand...
Click to collapse
Thx for info
I always update through TWRP. Just updated. Since I always choose the hide magisk option replacing it with a random name I uninstall the app real quick before I reboot to recovery. Used to be if you didn't you would end up with two apps installed. Don't know if this is still an issue or not. Either way all your settings will still be there. I uninstall the app, reboot to recovery, flash Magisk. Boot back into the OS, all my settings are already there, so the only thing I have to do is rehide Magisk.
Do this update fix the charge problem when the device is off?
ELGeKo24 said:
Do this update fix the charge problem when the device is off?
Click to expand...
Click to collapse
Didn't fix it for me.
OS 9.0.7.
TWRP 3.2.3-9
Magisk v18
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
I usually start over.
I flash a virgin boot age to both slots.
Reboot with TWRP
Install TWRP zip
Install ElementalX and Magisk zips.
Change slots and reboot recovery
Install ElementalX and Magisk in this slot.
I have the same OS version and kernels etc flashed in both slots.
lostunsunghero said:
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
Click to expand...
Click to collapse
Or you can also disable the Battery Optimisation for Magisk
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
What is the recommended install suggestion? Only Zip or with Boot image patch?
Calvin1997 said:
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
Click to expand...
Click to collapse
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
bladestonez said:
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
Click to expand...
Click to collapse
You're right. If tried the safetynet check on the new one, and after that the new one was removed. Completely strange. I hope someone here knows what to do
No problem here just selected install then used recommended.
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
So you just did the direct install option? Also are you running magisk with or without TWRP?
Calvin1997 said:
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
Click to expand...
Click to collapse
This is what I get when I install from magiek manager.
Yes with TWRP
[GUIDE] HOW TO UPDATE TO RUI 2.0 AND ROOT IT
--> Disclaimer: I'm not responsible if you brick your device. Use at your own risk and always backup your data! <--
0. Download linksF.14 OTA: Download
Magisk app: Download
OrangeFox beta: Download
ADB/Fastboot tool: Download
Patched boot.img: Find attached
vbmeta.img: Find attached
Patched safetynet fix: Find attached
1. Update your deviceUpdate your device to the latest firmware version (F.14). Therefor flash the provided OTA zip via stock recovery or OrangeFox beta recovery.
It is recommended to use the stock recovery. You can also update your device to the latest firmware by using the build in update function.
2. Root your deviceBoot into fastboot mode. To boot into fastboot mode, shut down your device and then press the volume down button while clicking on the power button.
Now you have successfully booted into fastboot mode. Connect your device with your computer and flash the patched boot.img and also disable verified boot.
Therefor just type following 3 commands:
1. fastboot flash boot patched_boot.img
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot reboot
Your device should boot up. Now install the Magisk app and you have successfully rooted RUI 2.0.
3. Fix SafetynetInstall the patched "safetynet-fix-v.2.2.0-zip" module via Magisk. It will fix safetynet (Basic integrity and CTS). It works perfectly and won't brick your fingerprint etc. Thanks to @osm0sis
4. Get Widevine L1If you have unlocked your bootlader, Widevine will be set from L1 to L3. This will reduce the quality of certain streaming apps like Netflix from FullHD to SD quality.
However, you can get Widevine L1 back by contacting the Realme support. For more info, check the guide from @hack-os: Widevine L1 FIX
Reserved
DarkImperator said:
3. Fix Basic integrity check (Safetynet)Unfortunately, it is not possible to pass safetynet with rooted RUI 2.0. However, you can still pass basic integrity, which should be fine for most banking apps.
To do so, open the Magisk Manger app and click on the settings button on the top-right corner. Enable "Zygisk" and "Denylist". Then click on "Configure DenyList".
Click on the 3-dots on the top-right corner and select system-apps. Now search for "gms". You should find "Google Play Services". Click it and enable "com.google.android.gms" and "com.google.android.gms.unsuable". Now reboot your device and it should pass basic integrity.
Click to expand...
Click to collapse
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Eng.Raman said:
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Click to expand...
Click to collapse
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
DarkImperator said:
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
Click to expand...
Click to collapse
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Eng.Raman said:
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Click to expand...
Click to collapse
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
DarkImperator said:
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
Click to expand...
Click to collapse
What is your Momo app and magisk Detector results? Can you screenshot ?
Eng.Raman said:
What is your Momo app and magisk Detector results? Can you screenshot ?
Click to expand...
Click to collapse
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
DarkImperator said:
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
Click to expand...
Click to collapse
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Eng.Raman said:
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Click to expand...
Click to collapse
EDIT: @Eng.Raman had to install MomoHider and add config "app_zygote_magic". Now Momo gives me the message.
DarkImperator said:
Installed MomoHider, but it still said "The environment is broken". So I disabled MagiskHide. Only as MagiskHide was disabled, I received a message from Momo. Screenshot attached.
Click to expand...
Click to collapse
That's weird you can't even hide magisk and su file.
Eng.Raman said:
That's weird you can't even hide magisk and su file.
Click to expand...
Click to collapse
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
DarkImperator said:
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
Click to expand...
Click to collapse
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Eng.Raman said:
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Click to expand...
Click to collapse
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
DarkImperator said:
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
Click to expand...
Click to collapse
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Eng.Raman said:
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Click to expand...
Click to collapse
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
DarkImperator said:
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
Click to expand...
Click to collapse
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Eng.Raman said:
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Click to expand...
Click to collapse
With enabled Magisk Hide it will fix basic integrity check, but not CTS. And it also bricks my in-display-fingerprint. Guess I'll stay with Magisk Canary, till there might be an update to fix those issues.
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
jalal.sy said:
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
Click to expand...
Click to collapse
I have the same issue with my banking app that doesn't allow NFC payments even though I've done everything to hide root.