Related
I rooted my galaxy S6 a couple of days ago and wow was it totally worth tripping Knox, any way I am writing this because I could not find a thread that had a guide usng these methods. I had to figure out how to get past several errors in TWRP and Magisk and I thought some people might be curious how I did it. I did not make any of these programs used, credit to the original authors. I did this so I could play Pokemon Go with root.
WARNING: THIS WILL TRIP KNOX AND MAY BRICK YOUR PHONE. DO THIS AT YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS. MAKE SURE YOU HAVE A FULL BACKUP OF YOUR DEVICE BEFORE CONTINUING. THIS WILL ALSO DISABLE OTAS.
Prerequisites:
Odin (make sure its version 3.10.6 others may not work): https://androidmtk.com/download-odin-downloader-versions
Galaxy s6 (have not tested on edge)
TWRP in .tar format for your model: https://dl.twrp.me/zerofltespr/
Stock ROM in case you mess up
Windows PC
Magisk v11.1: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk manager: https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en
Installing TWRP:
1.) Download all the necessary files and extract Odin to your desk top.
2.) Go into developer mode on your phone and enable OEM unlocking and USB debugging.
3.) Turn off your phone and enter download mode by holding power button, home button and volume down until the screen comes up that says something along the lines of installing a custom OS is dangerous, push volume up to continue.
4.) Plug your phone into your computer and start Odin.exe.
5.) Make sure Odin says "added" in the text window.
6.) Click on AP and browse for the TWRP .tar that you downloaded in the beginning.. Check the box next to AP once TWRP is loaded, then click "Start".
A.) If TWRP fails to install go to "options" and un-check "auto reboot". If this is un-checked make sure to reboot into recovering when Odin says "reset" by first exiting download mode by repeating the steps used to get into it and then holding home, power button and volume up until the TWRP logo appears.
7.) Congratulations you have now installed TWRP!
Rooting and installing Magisk:
1.) This will not work unless you have followed my previous steps.
2.) Make sure your phone is in recovery mode by holding power button, home, and volume up until the TWRP logo appears.
3.) Make sure your PC recognizes the phone and copy the Magisk 11.1 .Zip you downloaded earlier.
4.) Tap install on TWRP and and browse for the Magisk 11.1 .Zip, swipe to install.
5.) When it is done installing tap reboot.
6.) When your phone is done rebooting install Magisk manager from the play store.
7.) When you open Magisk it should say rooted with MAGISKSU in the center box.
A.) If it does not say that flash Magisk 11.1 in TWRP again.
B.) If the above does not work re-flash to stock and repeat all steps again.
8.) You are now rooted.
A.) If you would like to use Magisk hide tap the first box where it says install Magisk and follow the onscreen instructions.
1.) You can try rebooting your phone when it asks you too, but it would not install this way for me.
B.) After you have installed Magisk Framework, go into to settings and enable the hide Magisk option.
C.) Go back to the status section and tap on safety net check, it should be a green check-mark
1.) If it is not green restart and install Magisk again, then go into settings and disable and re-enable Magisk hide.
2.) If it is not green after doing the above re-flash the stock ROM and start over.
9.) You will have to reinstall Magisk Framework every-time you reboot, your root should stay installed after a reboot though.
That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
koop1955 said:
That is the wrong version of TWRP for a Sprint phone. The correct version is here: https://dl.twrp.me/zerofltespr/
There is a thread with links to the latest stock TAR files, correct version of TWRP for this phone and SuperSU here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
Thanks for pointing that out.
hmm, may I ask what advantages we get from this root method?
thank you.
You can hide your root and play Pokemon Go XD. I just think its more convientant having all my control apps super su and busy box in one place.
Sent from my SM-G920P using Tapatalk
Thank you for this.!!!!!!!!! 10/10
joej191 said:
Thank you for this.!!!!!!!!! 10/10
Click to expand...
Click to collapse
Your welcome. Glad I could help.
Sent from my SM-G920P using Tapatalk
Is magisk supposed to be installed after every reboot, or is that one of the many G920p specific issues?
I believe it is a GP20 specific issue because I have install mine after every reboot.
flett044 said:
I believe it is a GP20 specific issue because I have install mine after every reboot.
Click to expand...
Click to collapse
I just read this on the OP magisk thread: "magisk doesn't play well with Samsung devices. Try a custom kernel"
So i flashed the skyhigh kernel and now magisk is surviving restarts... the trouble is, Skyhigh auto intalls supersu and busybox.
Supersu isn't compatible with magisk, and i THINK that kind of busybox fails safetynet.
... so i used the busybox app to Uninstall busybox and the supersu app to do a full unroot and mount the stock boot image. (All to see if I could get magisk fully working) Then wipe davlik/cache, flashed the magisk.zip... booted up and opened the magisk manager, magisk was still installed, and magisksu was "properly installed"... but i fail safetynet attest now so i don't know what thats about.
Wondering if any of the veterans can chime in about any of this, since magisk indeed is pretty glitchy on the stock kernel.
Tl;dr: magisk doesn't work well with stock kernel, not sure how to get it working with custom kernel
I would also like to learn how to install magisk in sky high kernal.
Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.
still work?
@flett044,
Does this hidden root option still work with latest version of Pokemongo?
thanks
Yes it still works.
Nye-uhls said:
Hey @tdhite do you have any input on this? I assume it would break synapse support to use magisk and magiskSu instead of supersu and the normal busybox, but worth it.
Quick recap: trying to run a magisk set-up with a custom kernel. Presumably using magiskSu.
Click to expand...
Click to collapse
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.
How would I go about replacing supersu with Magisk?
tdhite said:
The boot routines currently use a policy tool specifically provided by SuperSu which is not available in Magisk. Access to files needed by various processes executed periodically (cortexbrain, cron jobs and others) may fail, but that would not be a critical failure, just a 'bummer' in the worst case. The startup routine is smart enough to check the policy tools and will cleanly boot even if SuperSu's tools aren't around.
Long story short, the kernel should work fine, you'll just miss out on certain things that try to run now and then to 'tune' the system.
Click to expand...
Click to collapse
That sounds like a pretty solid explanation for what happened when i tried running stock with skyhigh kernel and magisk.
Huge hit to battery life, and i still failed safetynet. Probably because the system showed i was using a custom kernel? I haven't been able to figure out a good way to mask that...
Anyways, good luck with implementing magisk like you said you would! I'm sure it won't be easy! You better have paypal links littered in the release post, you'll deserve it
What is the difference between Magisk and SuperSU?
JoeFCaputo113 said:
What is the difference between Magisk and SuperSU?
Click to expand...
Click to collapse
So I'm not super technical so i hope someone corrects me if i misrepresent this...
Magisk itself is basically a framework (think like xposed) except it functions from OUTSIDE of the system partition. Its only compatible with MagiskSU (a modified version of phh's superuser), magisksu is also not installed on the system partition...
Through magisk manager you can enable root, which as i understand, puts MagiskSU in the system partition in a sort of ghosted way, so its not really there? (As you can see I'm fuzzy on this part) And a step further, even with root still enabled, magisk can hide magisk and magiskSu's presence entirely from chosen apps (it automatically hides from play services so you pass safetynet)
So plain and simple, it theoretically works the same as supersu with the added benefit of being able to fully and effectively hide root...
There's still a lot of work to be done to reach it's full potential, especially in regards to compatibility with vendors and apps, but the dev believes magisk can do a lot eventually... including genuine multi-rom support.
https://www.xda-developers.com/magi...es-samsung-bugs-adds-core-only-mode-and-more/
Good news! Magisk update specifically for samsung devices! I can't wait to try this out!
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.
For this procedure is necesary unlock the bootloader?
Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.
Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!
And how are we gonna unlock the bootloader?
Is there a way to do that?
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
Hi all I got a 7T in the US. I got an update notification, and i wanted to uninstall Magisk, perform the update, reinstall Magisk and reboot. In Magisk I get the message, "stock image does not exist." I never had this problem with my Pixel, how can I get Magisk to save an image after I update and reroot?
Thanks
Droid_Nut said:
Hi all I got a 7T in the US. I got an update notification, and i wanted to uninstall Magisk, perform the update, reinstall Magisk and reboot. In Magisk I get the message, "stock image does not exist." I never had this problem with my Pixel, how can I get Magisk to save an image after I update and reroot?
Thanks
Click to expand...
Click to collapse
Why do you want to uninstall magisk?
1. Install update and don't reboot.
2. Go to magisk and install after ota
3. Reboot
I don't know about restore stock image with magisk and never did that.
If you really want to unroot your phone now, download the correct boot.img and flash it. There are a few threads available here to find that image you need.
Also you can download the ota.zip and dump that payload.bin which is inside the zip.
Like kollachi said, you don't need to follow the standard pattern of uninstall/ota/install-inactive with the 7t. I imagine that's because with a rooted device, it pulls the full rom instead of a diff.
But it sounds like you directly flashed a rooted boot.img which is why magisk doesn't have a backup. Instead, you should have done a `fastboot boot patched_boot.img` and then done a magisk install. It would have taken a backup of your original boot.img and then installed a patched version.
So basically install the Ota right over root, open magisk manager and install root, then finally reboot?
With the pixels and others, you have to uninstall magisk with restore boot image, install the update, install magisk again, then reboot.
Thanks for all of the help.
ziddey said:
Like kollachi said, you don't need to follow the standard pattern of uninstall/ota/install-inactive with the 7t. I imagine that's because with a rooted device, it pulls the full rom instead of a diff.
But it sounds like you directly flashed a rooted boot.img which is why magisk doesn't have a backup. Instead, you should have done a `fastboot boot patched_boot.img` and then done a magisk install. It would have taken a backup of your original boot.img and then installed a patched version.
Click to expand...
Click to collapse
I installed magisk with twrp, the twrp that you boot off of pc into temporary memory.
it's the same procedure you're used to. you just don't need to uninstall first since it's a full ota instead of a diff
Just wondering, will it back up my new stock boot image after the update, and the install from Magisk Manager?
Droid_Nut said:
Just wondering, will it back up my new stock boot image after the update, and the install from Magisk Manager?
Click to expand...
Click to collapse
No I don't think so. I can't find anything on my phone.
Kollachi said:
No I don't think so. I can't find anything on my phone.
Click to expand...
Click to collapse
I guess it really does not matter, considering we don't have to uninstall root.
yes it does..
backups are saved to /data/magisk_backup_<hash>/boot.img.gz
I have one for every time I've (re)installed magisk
ziddey said:
yes it does..
backups are saved to /data/magisk_backup_<hash>/boot.img.gz
I have one for every time I've (re)installed magisk
Click to expand...
Click to collapse
I still do not have a backup I did the OTA, and then reinstalled Magisk "Direct Install (Recommended)", but I guess I should have picked "After OTA to slot A or B" as I had no root on reboot. So I had to TWRP it back to root.
Lots to learn, but I am gaining. :good:
Droid_Nut said:
I still do not have a backup I did the OTA, and then reinstalled Magisk "Direct Install (Recommended)", but I guess I should have picked "After OTA to slot A or B" as I had no root on reboot. So I had to TWRP it back to root.
Lots to learn, but I am gaining. :good:
Click to expand...
Click to collapse
Yep the correct way is install after ota.
Droid_Nut said:
I still do not have a backup I did the OTA, and then reinstalled Magisk "Direct Install (Recommended)", but I guess I should have picked "After OTA to slot A or B" as I had no root on reboot. So I had to TWRP it back to root.
Lots to learn, but I am gaining. :good:
Click to expand...
Click to collapse
I mean you did that last time and it didn't backup your boot. Fair to assume you'll get the same results if you do it again.
When you install to inactive next time, it should create a backup since the boot image will be intact
With the Pixel it always recommended install to inactive slot and I went with what was recommended.
With the Pixel it always recommended install to inactive slot and I went with what was recommended.
Hi,
I was trying to update my OnePlus 7t to 10.3.3HD65AA but I am not able to do it. This is what I am doing
1) downloading the update package from oxygen updater application
2) going to setting then in system update I am clicking on more option and then on selecting local update then selecting the package waiting for upgrade to complete.
3) now going to magisk manager and installing the manager in inactive slot and rebooting the device
The phone gets reboot but doesn't update also attaching my magisk log here
Hi,
I was trying to update my OnePlus 7t to 10.3.3HD65AA but I am not able to do it. This is what I am doing
1) downloading the update package from oxygen updater application
2) going to setting then in system update I am clicking on more option and then on selecting local update then selecting the package waiting for upgrade to complete.
3) now going to magisk manager and installing the manager in inactive slot and rebooting the device
The phone gets reboot but doesn't update also attaching my magisk log here
jazzy ╰_╯ said:
Hi,
I was trying to update my OnePlus 7t to 10.3.3HD65AA but I am not able to do it. This is what I am doing
1) downloading the update package from oxygen updater application
2) going to setting then in system update I am clicking on more option and then on selecting local update then selecting the package waiting for upgrade to complete.
3) now going to magisk manager and installing the manager in inactive slot and rebooting the device
The phone gets reboot but doesn't update also attaching my magisk log here
Click to expand...
Click to collapse
I used method 3 to root my 7T a while back and did the update from 10.0.9 to 10.0.11 this morning. Did you do the full update? AFAIK the incremental update won't work
Used Oxygen Updater to download the update (DO NOT FOLLOW THEIR INSTALLATION INSTRUCTIONS)
Did local upgrade from Settings/System/System updates (options wheel) DO NOT REBOOT
Opened Magisk Manager and did a direct reinstall of Magisk (not manager) then
Installed Magisk into inactive slot
Reboot.
I am on 10.3.2, rooted with Magisk Manager version 07f712a1 and Magisk 87de0e7a. These are the version numbers I can see when i open Magisk Manager. Magisk Hide is enable for banking apps mainly, systemless host module is enabled and Magisk package name is also hidden.
Most apps needing root are working fine and most Banking apps requiring root to be hidden are also working fine.
However BHIM UPI is not working, I get a message of root detected after putting the PIN and it does not open. If I uninstall or clear storage and register my mobile again, it gives the root detected error but still logs in. However as soon as I exit and open again, it does not log in. Any way to get this working?
Adaway had been working properly but now it is not able to update hosts, says Root permission not granted, even though in Magisk default permission is Grant. I have tried to uninstall and reinstall, change options in Magisk, install F-droid version but nothing works. Systemless host is enabled. I have restored a working app version and data using Titanium backup so ad-blocking is working. But unable to update with new host file. How to fix this?
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Macusercom said:
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Click to expand...
Click to collapse
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
gpz1100 said:
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
Click to expand...
Click to collapse
Is this meant as a reply to my post? My issue with Adaway on Magisk Canary is that suddenly it is not able to get root permission.
So it worked before? I had to mess with the systemless hosts to get it working. It didn't have issues acquiring root though.
jesrani said:
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
Click to expand...
Click to collapse
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Macusercom said:
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Click to expand...
Click to collapse
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
jesrani said:
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
Click to expand...
Click to collapse
Afaik only for custom ROMs. Otherwise, you can still remove Magisk in Magisk Manager and then patch the boot.img with the stable Magisk version or you remove ALL modules first, then make an OTA update to your existing version.
Then patch boot.img and flash it via "fastboot flash boot.img".
@jesrani What was the solution finally ?
Yea I'm having the same issue, tried everything i could and even using 'hide my applist' and it IS working. Its just that all apps except BHIM just won't even open now.