Related
I have successfully rooted my phone with SuperSU and it works fine. But I want to switch to MagiskSU so I can use snapchat. When I go to settings in SuperSU and click full unroot it says uninstallation failed. I know the other way to remove it is by flashing UPDATE-unSU.zip but when I do so it only removes the SuperSU app and not the root. I was wondering if there was any other way of unrooting SuperSU that allows me to install MagiskSU. I have a Oneplus 3T and have all the latest updates. Please help.
Magisk needs a kernel that haven't been patched by supersu. Reflash boot so that you have a "clean" kernel and try magisk again. Then, with magisk root you can remove the su.img in /data if it's still present.
Sent from my SM-A310F using Tapatalk
tys0n said:
Magisk needs a kernel that haven't been patched by supersu. Reflash boot so that you have a "clean" kernel and try magisk again. Then, with magisk root you can remove the su.img in /data if it's still present.
Sent from my SM-A310F using Tapatalk
Click to expand...
Click to collapse
How do I reflash the boot.img in recovery for my Oneplus 3t?
Hi all,
I have lost the ability to root my EMUI 5.0 v360 rom using either Magisk or SuperSU with the TWRP designed for EMUI 5.0.
I had SuperSU installed and working but I wanted to try Magisk for the Magisk Hide feature.
I uninstalled SuperSU through the app settings. It succeeded.
Then I installed Magisk. It also succeeded.
That was fine, and I noticed that Magisk has its own internal BusyBox so I figured out would uninstall BusyBox that I had installed and use that.
But from that moment I lost root.
Then I tried uninstall of Magisk using its flash able uninstall. And then reinstall it.
Root was not activated by reinstalling even though Magisk was successfully installed.
The I uninstall Magisk completely to go back to SuperSU.
The flashable SuperSU installs fine. But the app does not recognise that the binaries are installed at all.
So right now I can patch the relevant files in twrp but the system no longer recognises root.
I don't know how this could happen from uninstalling BusyBox. But that's where I am stuck at...
Sent from my Honor 6x using XDA Labs
Man with every little thing you do, you need to take a backup from TWRP. Now the only solution to your problem is to reflash your firmware.
Sent from my Honor 8 using XDA Labs
So now that the unofficial Xposed for Nougat is out, has anyone gotten it to work on a rooted stock mate 9?
It looked like it might be just for magisk, but root is via SuperSU for us.
benjmiester said:
So now that the unofficial Xposed for Nougat is out, has anyone gotten it to work on a rooted stock mate 9?
It looked like it might be just for magisk, but root is via SuperSU for us.
Click to expand...
Click to collapse
We have Magisk too
I'm not sure if the magisk module works though.
ante0 said:
We have Magisk too
I'm not sure if the magisk module works though.
Click to expand...
Click to collapse
can u tell me how can we root using magisk i have unrooted before because of apps not running with root
Iloudsan said:
can u tell me how can we root using magisk i have unrooted before because of apps not running with root
Click to expand...
Click to collapse
First off you need to be on a B182+ firmware and flash Twrp 3.1.0-1.
For decrypted (Wipe - 'Format Data' in twrp then back to twrp start screen and Reboot - Reboot recovery, this erases all user data/apps and you need to flash public and hw zip after you've formatted) use the official Magisk 13.3 zip: http://tiny.cc/latestmagisk
For encrypted (no need to format data or do anything special, downside is you won't be able to backup /data partition) use: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
If you have any root flashed currently, flash back stock boot.img before flashing Magisk.
benjmiester said:
So now that the unofficial Xposed for Nougat is out, has anyone gotten it to work on a rooted stock mate 9?
It looked like it might be just for magisk, but root is via SuperSU for us.
Click to expand...
Click to collapse
+1...I have been using Xposed for a long time on all my devices and would love to have it on my Mate 9. I am also rooted via SuperSU.
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7
virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?
quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4
quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.
virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes
So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0
16.4... notice the 4
Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure
Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
I have attached the screenshots below. And I understand that I'm using Magisk 16.0
skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs
Just Posted
https://developers.google.com/android/images#sunfish
fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs
hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.
moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary
@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)
fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik
tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints
Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy
I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?
Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk