I just received an update and downloaded the ZIP file to flash in recovery. Can we do it or must we run the modded version?
I did a search and didn't see anything good or bad, just the announcement in the Magisk thread.
I went for it and updated the manager app, followed by Magisk.
I updated both via the manager app, choosing the recommended option.
I did not use TWRP or reboot, prior to updating both.
It's been an hour or so. No issues.
I did 2 days ago ..no issues so far
No issues after 4 days.
I figured that since I didn't see anyone complaining about issues, it was a good risk.
Related
Okay so I have seen an update to SuperSU in the app store.
I had manually installed SuperSu through TWRP recovery when I rooted the tablet, as per the instructions on this thread:
http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-10-5-wifi-semi-t3242433
However, now I'm unconvinced of the benefits of updating SuperSu through the Google Play store, as I have had issues updating it previously (with the welll-known updating binary issues). Also I've heard of many issues where the binary doesn't update properly (both on the Tab S and other devices).
The way I see it, SuperSu is doing its job, and I don't make drastic modifications to my tablet that require an update to SuperSu at present. I have also disabled OTA updates as they tend to not work with rooted devices. So I'm holding off on the update for now.
Any thoughts?
If it ain't broke don't fix it.
@snapper.fishes:
That's what I was thinking too...Thanks!
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for
Hi guys,
Since the last few days my snapchat keeps getting temporarily blocked, I'm on a SM-G960F (Galaxy S9_9.0_JULYSecurity) rooted with Magisk and flashed with latest Ambasadii Rom(19.0). The first 3 weeks using snapchat with root & custom rom there weren't any problems at all. Can somebody help me?
Grtzz
Koovah_SC said:
Hi guys,
Since the last few days my snapchat keeps getting temporarily blocked, I'm on a SM-G960F (Galaxy S9_9.0_JULYSecurity) rooted with Magisk and flashed with latest Ambasadii Rom(19.0). The first 3 weeks using snapchat with root & custom rom there weren't any problems at all. Can somebody help me?
Grtzz
Click to expand...
Click to collapse
A lot of people are having the same issue. Magisk Hide doesn't seem to work with the latest versions of Snapchat. No matter what you do you will keep getting locked out of your Snapchat account. I'm a bit of a NOOB when it comes to this stuff but here is what has worked for me so far. Firstly, you have to serve your penance. There's nothing you can do about that. My most recent ban was 2 weeks. When your access has been restored delete the Snapchat app. Download an older version of Snapchat from apkmirror.com and install it. Version 10.540.31 worked for me. **IMPORTANT** You must untick auto-update of the Snapchat app in Goggle Play. Hide the Snapchat app with Magisk and then hopefully you should be OK. It's only a workaround but it's the only solution I've come across that works. Having said that, it's only been several days but so far so good. If I get locked out again I'll let you know. Good luck.
bulky68 said:
A lot of people are having the same issue. Magisk Hide doesn't seem to work with the latest versions of Snapchat. No matter what you do you will keep getting locked out of your Snapchat account. I'm a bit of a NOOB when it comes to this stuff but here is what has worked for me so far. Firstly, you have to serve your penance. There's nothing you can do about that. My most recent ban was 2 weeks. When your access has been restored delete the Snapchat app. Download an older version of Snapchat from apkmirror.com and install it. Version 10.540.31 worked for me. **IMPORTANT** You must untick auto-update of the Snapchat app in Goggle Play. Hide the Snapchat app with Magisk and then hopefully you should be OK. It's only a workaround but it's the only solution I've come across that works. Having said that, it's only been several days but so far so good. If I get locked out again I'll let you know. Good luck.
Click to expand...
Click to collapse
Same issue here and Im on a SM-G960FD with lightROM v23 and magisk 19.3. I tried randomly with 10.60.5.0 but it didnt work. I will try with version 10.540.31 of snapchat when my 2 day ban is over.
It's been 2 weeks and Snapchat hasn't locked me out using my workaround. So far so good. :good::good:
How to use Snapchat with magisk (After Ban)
Koovah_SC said:
Hi guys,
Since the last few days my snapchat keeps getting temporarily blocked, I'm on a SM-G960F (Galaxy S9_9.0_JULYSecurity) rooted with Magisk and flashed with latest Ambasadii Rom(19.0). The first 3 weeks using snapchat with root & custom rom there weren't any problems at all. Can somebody help me?
Grtzz
Click to expand...
Click to collapse
bulky68 said:
A lot of people are having the same issue. Magisk Hide doesn't seem to work with the latest versions of Snapchat. No matter what you do you will keep getting locked out of your Snapchat account. I'm a bit of a NOOB when it comes to this stuff but here is what has worked for me so far. Firstly, you have to serve your penance. There's nothing you can do about that. My most recent ban was 2 weeks. When your access has been restored delete the Snapchat app. Download an older version of Snapchat from apkmirror.com and install it. Version 10.540.31 worked for me. **IMPORTANT** You must untick auto-update of the Snapchat app in Goggle Play. Hide the Snapchat app with Magisk and then hopefully you should be OK. It's only a workaround but it's the only solution I've come across that works. Having said that, it's only been several days but so far so good. If I get locked out again I'll let you know. Good luck.
Click to expand...
Click to collapse
drowsy_fish said:
Same issue here and Im on a SM-G960FD with lightROM v23 and magisk 19.3. I tried randomly with 10.60.5.0 but it didnt work. I will try with version 10.540.31 of snapchat when my 2 day ban is over.
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account :crying: and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
Hello guys,
after rootin and updating my phone several times i somehow broke my safetynet so i restored my phone to the latest Firmware.
On the latest Firmware i tried to root it with magisk canary but i everytime get stuck at the point, where magisk want to do the additional setup with takes about a few seconds. Mine just stuck there until i close the App. The weird thing about is, that when i use the stable/beta version (7.5.1) it works. When i upgrade to Canary again, i cant rename Magisk, it always fails. When i do all the steps in the stable/beta version it works fine but i cant just upgrade to canary as ive no option in the settings to change from stable to canary, only beta is showin up. When i install the canary manager, ive 2 magisk installed and cant really get the canary version to work. Is here someone who has the same problem and know, how to fix it ? Do i have to wait for an update ?
I wanted to post this as a issue on github but i dont have any logs so.
Thanks for any reply
Hello
I full OTA update to my rooted OnePlus 7T
But I forgot to disable Magisk modules, etc.
So from the attached screenshots: Magisk manager is complaining that root was denied; yet, I'm still rooted. Other apps needing root have root access and root check app states I'm rooted.
So far I've tried to install the full update again but Magisk manager will not let me install root to inactive slot after OTA update... Only allowed to patch boot image.
So what am I doing wrong? And how can I get root through Magisk Manager (or not)?
Edit: looks like I don't have root anymore either (wither Manager says so or not cause apps that used root have now lost access.... Installed the OTA full update and skipped install root b4 reboot since Manager didn't provide me the option to install after OTA and before reboot)
Thanks
Ok all sorted out thanks. Hid Magisk and forgot. Installed full update then tried to root with new Magisk Manager install (so now I had two installed Magisk Managers cause I forgot I told one to go hide just a few days ago!). So that's not gonna work.
Solution: lots and lots and lots of reading cause I have never hid Magisk. But, finally I read and reread and read some more.
Finally, I remembered that I never uninstalled the hidden Magisk Manager - I just hid and forgot (never hidden Magisk until this first instance so I never had to consider that).
Looking in my app drawer... Yup, 2 instances of Magisk Manager... One hidden right beside the other installation.
Uninstalled the hidden Magisk Manager and the newly installed Magisk Manager worked like it should and patched boot to root (or is it root to boot?).
YAY THANKS XDA. Couldn't have done it with out you all here.
And no more pressing any more buttons that I don't know what the result is. I'll read first, then press buttons, then complain here for help. PS: it gave me something to do for two straight days yay. Can't wait for new XDA app.
Peace