Hi guys - I'm having trouble with the latest version of Magisk...
My ROM - ViperOne M9 (for HTC One M9) - comes packaged with Magisk 10.6 and phh's Superuser, and it seems to work ok out of the box. However, I can't get it to pass SafetyNet checks with HideMagisk enabled, which is an annoyance as I can't use certain apps (no, NOT Pokemon GO FYI ). The Magisk Manager was advising to update itself, which I thought might help - so I did. After a reboot I have now lost root on my device, and cannot get it back.
A knock-on effect seems to have taken out phh's Superuser too, as it now complains of out-of-date binaries when the phone boots up, and I'm not getting any permission requests any more. I tried revoking Magisk's permissions, but it never tried requesting them again.
I flashed the phone using the latest TWRP, and my firmware and bootloaders are up to date also.
Not sure whats going on here - any ideas?
I could re-flash the phone, as I did a complete wipe earlier today to update ViperOne to the latest version (version 6.00) - so it's not a major headache, and should give me root back. But then I'm back to a broken hide-root/SN bypass. Again, this isnt a major problem since I'm used to not using those apps - but it would be nice to have.
Cheers.
Guys, managed to resolve my problem.
I downloaded the latest ZIP for Magisk 11.6 and phh Superuser, and flashed using TWRP. Rebooted, and all working!!
Also FWIW, I solved the problem with SN failing.... well I installed Magisk 11.6 and the work you guys did obviously did it for me, so thank you!
Related
I'm right now I'm at a point where I hate stock and these custom roms are great, but hate being held back by the Play store no longer allowing me to download/update Netflix which is used often.
Previously I had installed
KatKiss - Nougatella #023,
SuperSU
Gapps - Stock
I suppose I could have just installed netflix through the apk but I figured that would only be a temp solution.
So my first steps were to wipe and go back to stock.
I then proceeded to add CWM recovery back (Also tried with TWRP)
I wiped
I then ran an uninstall SuperSU zip (which may or may not have been needed but seemed safer to try.
I installed KatKiss
Then Magisk
Then Gapps - Stock
This will cause lots of crashing right from the start of the setup wizard... the the app/stopped don't ever stop. A lot of google related stuff as soon as I conect to Wifi.
I started over.
This time I installed Gapps - Mini instead.
No longer crashes the set up wizard. Everything seems stable.
At this point I have access to the tablet through KatKiss.
When I run Magisk Manager, the safetynet check never finished. Just spins.
If I hide the PlayStore from root and try to find Netflix it won't be there.
However, if I now install Gapps-Stock through recovery at this point... I can then go back to the Play Store and find Netflix. It will be there.
However, I still can't pass SecureNet check. It just spins.
I first thought to myself... Thats ok. I don't need it, Netflix was really the issue I needed addressing and I have that.
So I started putting apps back on my tablet to find... apps were crashing more. Facebook for example will never work. Just crashes on startup.
So something just isn't right and I don't really know what I'm doing. In the past I always just followed easy to follow guides.
Note: I believe I have better luck with KatKiss build #021. 023 gave me more issues with this process so I had 021 on hand.
You really should go with the gapps version recommended by the dev of your rom and that would be pico gapps in this case. If you flash a different gapps package you're on your own for trouble shooting fc'ing apps and system UI and such...
I have no idea if this rom works with Magisk and would be tickled to find out, but I don;t have the time for it right now. On other devices there were problems when the rom was pre-rooted or for some the build-in busybox did not work and they had to flash a different version. There could also be a problem if the boot image has been modded for SuperSU and idk if it has been on this rom.
Try this first:
If you flashed any other than pico gapps version you really should format /data before reflashing the rom. That done:
format /system, wipe /cache and Dalvik, then flash the rom and pico gapps, then flash unsu by osmosis followed by the Magisk flash. Then install Magisk Manager and try to pass Safetynet with both Busybox enabled and disabled.
Let me know how it goes
https://forum.xda-developers.com/showpost.php?p=63615067
Edit: couldn't help myself - had to try it :cyclops:
So I tried a quick and dirty switch from SuperSU rooted Katshmallow v33 to the same rom with Magisk. No reflash, just wiped cache and Dalvik, flashed unsu and then Magisk. Root works fine but it does not pass Safetynet check, Netflix app does not show in Playstore, device is uncertified in Play.
The failed check says: CTS profile mismatch and I believe that is the problem with the Busybox version that comes with Magisk. Read something somewhere about replacing it with a different one which solved the problem for some folks...
I'll dig some more later....
Thanks for the info. I didn't realize the importance of using Gapps-Pico in this case. I just figured they were recommending a light-weight Gapps opposed to a larger one... So I always went with "stock" and never had an issue.
I'll keep that in mind for debugging future issues.
I'm not sure how important formatting /system was... I always left that one alone, but I was formatting /data /cache and Dalvik
That CTS profile stuff all seems beyond my knowledge at the moment. I guess let me know what you find when you do.
Thanks again
No issues? I thought you had "lots of crashing".. ??
So you want me to do all the leg work, yes? Sorry man, it's you who wants Netflix :silly:
I dirty flashed the rom, ran unsu, then flashed Magisk and osmosis' Busybox but Safetynet check still fails for me...
Don't have time to do a clean install just now, but that would be the next step...
I like Magisk as systemless root and I got it working for my purposes.
As for Netflix - I don't use it much on the tablet and I just squirreled away the 4.16.1 version. Just in case I accidentally update it to the newer ones....
Sorry if that was unclear. I meant I never had any issues using Gapp Stock before this whole Rooted/Netflix thing came up last week. Now it is what it is.
And yeah, I didn't mean for it to be like I was asking anything of you. I'm not. You just seemed like the type who would be tinkering with this kind of stuff. If not, no worries.
Information/guidance is what I'm after. Not leg work.
I'm sure I just need to be patient really. Since a lot of people use Netflix I'm sure this will get a lot more attention in the near future.
Thanks again.
[Problem]
I noticed google pay not working after enjoying magisk happily for two days.
[Research]
I searched the forum and found many others have issue with google pay, too.
[Trial]
I started to do something with the hope to solve this problem.
1. I changed the update channel to beta test and installed magisk v19. Google pay was not working.
2. I then changed back to stable update channel to install magisk v18. Strange thing happened.
3. Phone booted fine but magisk manager detected no trace of magisk. I re-flashed patched_boot.img. Same thing, magisk was gone.
4. I am on stock ROM (S6 edge) and installed magisk by patching boot.img. I had no TWRP recovery. I could not do much under this circumstance.
5. So, I was in a situation of missing magisk and disabled google pay.
[Final]
I flashed the stock ROM via odin.
1. The google pay was working again in stock ROM (without root).
2. I lost magisk (and root).
I will install magisk again if google pay can work with it. The problem is the security check by google. I still hope there will be some work-around method.
You can never be certain that a dirty downgrade will work. You can of course try, but be prepared for trouble.
If I remember correctly, in this case, simply uninstalling the Manager and reinstalling the apk that comes bundled with v18.1 might have fixed things.
Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help
Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break
Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8
I have Magisk 20.1 (Magisk Manager 7.5.1) currently installed on my Samsung Galaxy Tab A (2016). While initially installing it was not as straight forward as it might have been (install doc could use some work; I think it's written for folks with more familiarity with android devices on a day to day basis than those who root a phone maybe once every few years); I installed Magisk and it's been working fine.
However, this morning I had a notification that I needed to run Magisk setup. I told it to do so; it downloaded something; rebooted the tablet ( which wasn't warned of in the notification); and on coming back up ran Busybox so I'm assuming that was the setup. Going into Magisk Manager, however, I got the same notification over again. So I let it update again with the same result.
This time I told it to cancel the update/setup. I then tried to manually do the update from 20.1 (20100) to 20.3 (20300, latest available version). Update proceeded normally until repacking; which failed. Since Magisk is already installed and working (with several root level apps) on this phone; I can't see where this could be the "wrong image problem" which seems to be the most prevalent root cause of this kind of error. Unfortunately the update as distributed doesn't say anything about *why* it can't repack the image; so the message doesn't help us ordinary folks in debugging.
Any ideas as to what the actual issue is?
Android info:
Version 8.1.0
Kernel 3.18.14-1570595
Build M1AJQ.T580UEU4CSC1
Note: Busybox had an update I believe came out sometime yesterday (saw notification it updated successfully). Could it be that something in the Busybox update broke the Magisk update process?
The latest OTA update made my phone bootloop if i re-flash magisk patched init_boot image...
After I asked Stock users, it looks like it's a GrapheneOS june update + Magisk specific issue.
Do someone else also have this issue?
Phone boots normally, then reboot to recovery instead of reaching lock screen.
For now, I re-flashed panther-factory-2023061402 init_boot.
Have you tried Magisk canary version? or maybe GrapheneOS doesn't like june update and newest Magisk and you need to either go back down to stable Magisk or an older version of Magisk?
Actually, after re-reading your OP, a module might be the cause of the bootloop -- I've recently seen similar behavior from other members where device bootloops or crashes during/right-after loading & starting up -- if you were on the stock ROM I would suggest you loading up in Safe Mode to see if it is a module issue; I don't know anything about GrapheneOS so I don't know if it offers anything similar. I wonder if the adb command to remove modules at boot would work....
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Albirew said:
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Click to expand...
Click to collapse
knew it....
glad I helped get you there!