Magisk - OnePlus 3T Questions & Answers

Can't reboot after installing modules
If you have updated Magisk from v13.3 and Magisk Manager v5.1.1 you might come across this issue. The solution is to clear data for the Magisk Manager (busybox integration has been updated and needs to be reloaded).
After clean install of beta 14 --> magisk 14.000 problem persists.. (im only using unified hosts adblock module)
Any idea for fix?

It has been mentioned a dozen times already.
Why don't you make a search before posting?
Just reflash 13.3 from recovery and this is it.
Just wait for a compatible Xposed module.
Unleashed by ONEPLUS 3T rooted

oTeMpLo said:
Can't reboot after installing modules
If you have updated Magisk from v13.3 and Magisk Manager v5.1.1 you might come across this issue. The solution is to clear data for the Magisk Manager (busybox integration has been updated and needs to be reloaded).
After clean install of beta 14 --> magisk 14.000 problem persists.. (im only using unified hosts adblock module)
Any idea for fix?
Click to expand...
Click to collapse
Did you try clearing data for the Manager? Logs?
RASTAVIPER said:
It has been mentioned a dozen times already.
Why don't you make a search before posting?
Just reflash 13.3 from recovery and this is it.
Just wait for a compatible Xposed module.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
What? What Xposed module? Did you read before replying?

Didgeridoohan said:
Did you try clearing data for the Manager? Logs?
What? What Xposed module? Did you read before replying?
Click to expand...
Click to collapse
What's your issue pal?
You didn't like the word "module"?
Xposed's version is creating the problem.
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
What's your issue pal?
You didn't like the word "module"?
Xposed's version is creating the problem.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
No issue... I just didn't see the OP mentioning anything about Xposed, that's all. And I haven't seen Xposed causing the "can't reboot after installing module" problem before... But Xposed can cause a lot of problems, that's true.

Didgeridoohan said:
No issue... I just didn't see the OP mentioning anything about Xposed, that's all. And I haven't seen Xposed causing the "can't reboot after installing module" problem before... But Xposed can cause a lot of problems, that's true.
Click to expand...
Click to collapse
I font have can not boot probelm..
I have Reboot never complete s.. problem! And its there with 13.3 too..
Mybe coised by unified hosts 2.9 modul...
Sent from my ONEPLUS A3003 using Tapatalk

oTeMpLo said:
I font have can not boot probelm..
I have Reboot never complete s.. problem! And its there with 13.3 too..
Mybe coised by unified hosts 2.9 modul...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
This thread is getting more and more confusing.
Are you saying that your device isn't booting after installing the Unified Hosts module?? That's a different issues than the one you wrote about in the OP (the text from my troubleshooting guide about not being able to reboot after installing a module)...
I have no issues installing the Unified Hosts Adblock module (v2.9) on my OP3T.
You're gonna have to provide a lot more details about your setup. And logs.

Didgeridoohan said:
This thread is getting more and more confusing.
Are you saying that your device isn't booting after installing the Unified Hosts module?? That's a different issues than the one you wrote about in the OP (the text from my troubleshooting guide about not being able to reboot after installing a module)...
I have no issues installing the Unified Hosts Adblock module (v2.9) on my OP3T.
You're gonna have to provide a lot more details about your setup. And logs.
Click to expand...
Click to collapse
it BOOTS FINE!
in does not REBOOT (restart) -after some time (rebooting is endless..) have to forcepower off!! and unified host is the only module i am using... in Magisk
unistaling magisk .. phone reboots fine.
EDIT:
(ok its magisk alone.. endless reboot) again.. mybe have to disable Systemless hosts ? -- will try next...

in my experience, magisk v14 does not create magisk.img, which makes modules fails to install.
i have to clean flash 13.3 and upgrade to 14 beta directly via twrp, then it works even via magisk manager

Related

[Discussion] PokeMon Go Magisk Discussion Thread

[size=+2]This thread has been created to reduce the amount of clutter in the main Magisk thread, please discuss Magisk + PokeMon Go here.​[/size]
With me is this happening, did the process and pokemon jog go wheel with root, however when I install Xposed does not work, I downloaded the zip and the apk Xposed, desintalei what was, I was in recovery installed the zip, when you restart disable the root by magisk manager and I run the game without success, to turn off the Xposed and restart the game runs, but when active and restart does not work, sometimes the apk Xposed for work, or is giving error and asking to check records, someone help there? They will excusing my English
So at this point I can't log into pogo because I have Xposed installed (systemless). I was using magisk with phh super user...wasn't working with SuperSU (even with compatible magisk)
At this point if I do a soft reboot it deactivates Xposed (for whatever reason) I can play Pokemon but have to reboot to activate Xposed. So anytime I want to play I have to soft reboot then full reboot. Luckily I don't have to go through optimizing apps...but is there a way around this?
Someone bored should make a zip that removes everything and reinstalls the rest of the stuff needed.
Sent from my SM-N920W8 using XDA-Developers mobile app
DAGr8 said:
Someone bored should make a zip that removes everything and reinstalls the rest of the stuff needed.
Sent from my SM-N920W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
You?
I rather wait for an xposed update. I can play with 0.35 if I really get the itch in the meanwhile. I hardly battle and until legendaries start to appear, I'm just slowly leveling up.
If 86.2 is working, like someone mentioned on the other thread, there has to be a workaround for the 86.5 (maybe a future 86.6?)
Only gripe is that Google is all over this because of paynet so it will be a constant battle.
Only way to calm down this race is for Google/Niantic easing pressure on pogo security so there aren't so many people trying to hack the system and leaving paynet alone.
That would be the smartest move for all (not mentioning calming down thousands of root users).
Interesting times
Enviado do meu GT-I9195 através de Tapatalk
anthonymackay said:
So at this point I can't log into pogo because I have Xposed installed (systemless). I was using magisk with phh super user...wasn't working with SuperSU (even with compatible magisk)
At this point if I do a soft reboot it deactivates Xposed (for whatever reason) I can play Pokemon but have to reboot to activate Xposed. So anytime I want to play I have to soft reboot then full reboot. Luckily I don't have to go through optimizing apps...but is there a way around this?
Click to expand...
Click to collapse
Actually systemless xposed v86.2 is working fine woth Pokemon go. Some people posted the steps in the other thread.
So I flashed the latest chainfire SuperSU 2.78 r1, v86.2 systemless xposed, and suhide v0.53. Everything works good only problem I'm having excessive location jumps to/from real location while playing pogo with xposed pokemon. Used to have the odd jump back/forth but this is every 5-10 seconds.
juangcardoso said:
Actually systemless xposed v86.2 is working fine woth Pokemon go. Some people posted the steps in the other thread.
Click to expand...
Click to collapse
I thought I was going crazy. One whole day, two full resets and re-roots later and found the system-less xposed glitch that took me here. Does this 86.2 really works?. Don't want another round with my phone.
sigiloso said:
I thought I was going crazy. One whole day, two full resets and re-roots later and found the system-less xposed glitch that took me here. Does this 86.2 really works?. Don't want another round with my phone.
Click to expand...
Click to collapse
Yes, but there are the correct way to flash it with SuperSU and suhide. You can find these steps in the systemless xposed as I told u.
juangcardoso said:
Yes, but there are the correct way to flash it with SuperSU and suhide. You can find these steps in the systemless xposed as I told u.
Click to expand...
Click to collapse
I have tried so many times to do xposed systemless but none of them worked.
I returned to stock image. I created file with "SYSTEMLESS=true" in /data/.supersu
I flashed SuperSU 2.78. Then I flashed systemless xposed v.86.2.
I flashed suhide 0.53. wipe cache/dalvik and nothing works because I think its detecting the xposed framework
juangcardoso said:
Actually systemless xposed v86.2 is working fine woth Pokemon go. Some people posted the steps in the other thread.
Click to expand...
Click to collapse
Hi!
Could you link the post to this thread please? I'm sure it would help a lot of people (me included). I scanned through the other thread but couldn't find it. Perhaps, I missed it somewhere.
naeco said:
Hi!
Could you link the post to this thread please? I'm sure it would help a lot of people (me included). I scanned through the other thread but couldn't find it. Perhaps, I missed it somewhere.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3450396
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
anthonymackay said:
So at this point I can't log into pogo because I have Xposed installed (systemless). I was using magisk with phh super user...wasn't working with SuperSU (even with compatible magisk)
At this point if I do a soft reboot it deactivates Xposed (for whatever reason) I can play Pokemon but have to reboot to activate Xposed. So anytime I want to play I have to soft reboot then full reboot. Luckily I don't have to go through optimizing apps...but is there a way around this?
Click to expand...
Click to collapse
Magisk requires a full boot too load is modules, that's why xposed is disabled with a soft boot.
You can also use the disable xposed toggle in the material xposed installer. It would still require a reboot.
Guess I'm out of luck. My phone doesn't meet SuHide requirement. I'm running twrp v.2.8.7.0 not v.3.x.
Anyone know if there is an 86.2 version for Lollipop? all I can find is the sdk23 version for Marshmellow.
Habulda said:
I have tried so many times to do xposed systemless but none of them worked.
I returned to stock image. I created file with "SYSTEMLESS=true" in /data/.supersu
I flashed SuperSU 2.78. Then I flashed systemless xposed v.86.2.
I flashed suhide 0.53. wipe cache/dalvik and nothing works because I think its detecting the xposed framework
Click to expand...
Click to collapse
naeco said:
Hi!
Could you link the post to this thread please? I'm sure it would help a lot of people (me included). I scanned through the other thread but couldn't find it. Perhaps, I missed it somewhere.
Click to expand...
Click to collapse
I manage to play Pokemon Go w/ xposed and root with these tips: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post68778700
Hey guys. Galaxy s3 mini with cm12.1 (android 5.1.1) fresh install. Tried to install magisk but it says unable to detect boot image. What is the problem ? Please help me.
I need download xposed-v86.2-SDK22.arm. Please post the link for donwload XPOSED 86.2 SDK22 arm!! Help me please.
I find the zip file anywhere. I need SDK22 arm 86.2 for android 5.1 - Someone can attach the direct link to download the ZIP please?
naeco said:
Guess I'm out of luck. My phone doesn't meet SuHide requirement. I'm running twrp v.2.8.7.0 not v.3.x.
Click to expand...
Click to collapse
a user report that it works with twrp 2.8.7

[MODULE] Google Pixel experience, v3.5.1, systemless by anupritaisno1

Update: it's finally here!
https://raw.githubusercontent.com/a...enceOneplus/master/PixelExperienceOneplus.zip
This module just copies @FaserF's pixel experience and brings it to magisk
Repo link: https://github.com/anupritaisno1/PixelExperienceOneplus
Note that this is universal
Thanks: @Link_of_Hyrule, @stangri and @FaserF!
Reserved
when it'll be available in Magisk module section or download link to install manually?
DeathStroke said:
when it'll be available in Magisk module section or download link to install manually?
Click to expand...
Click to collapse
Download link is not yet available as there is some stuff that I'm not yet satisfied with
Btw I'm constantly pushing commits to my github as soon as I find an issue and fix something. You could clone my repo, put it in a zip and flash it. Report back any issues and I'll gladly look into them
As for donations, I did this just for fun.
If you want to donate to someone then @FaserF is the one who should get it
It's perfectly fine now. However you will need to clone my repo and archive it.
Here's what happened:
You see, I started this just for fun and to see how I could experiment with magisk. I then started work on it and once it was a little bit stable with basic stuff working, I pushed it to git
However I did this entirely on phone using nethunter and as such I currently don't have a PC to upload the module as a flashable zip
So you will have to download everything from my git, put it into a zip and flash it in twrp/use the magisk flasher
I don't think I'll have access to a PC until Thursday evening (GMT +5.30)
More info for this module????
Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
anupritaisno1 said:
It's perfectly fine now. However you will need to clone my repo and archive it.
Here's what happened:
You see, I started this just for fun and to see how I could experiment with magisk. I then started work on it and once it was a little bit stable with basic stuff working, I pushed it to git
However I did this entirely on phone using nethunter and as such I currently don't have a PC to upload the module as a flashable zip
So you will have to download everything from my git, put it into a zip and flash it in twrp/use the magisk flasher
I don't think I'll have access to a PC until Thursday evening (GMT +5.30)
Click to expand...
Click to collapse
Is there any way that I can do that from my phone?
Sent from my shamu using XDA Labs
harpin14789 said:
Is there any way that I can do that from my phone?
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Yes, go to my git and switch to desktop mode
Then download it as a zip and use solid file explorer to extract it (don't use others)
Then inside it you'll see a folder. Open this up and select all the contents in this folder except README.md and put it in a zip with compression level "normal"
Go to magisk manager and flash this
Reboot and send me a log in private
https://raw.githubusercontent.com/a...enceOneplus/master/PixelExperienceOneplus.zip
bug report on op3t/oos 3.5.4
has two contact apps
still in original dialer
Hey, I'm having a bug. I have a SM-G935F s7 phone, using magisk v9, manager v2.5 and phh's superuser. When installing the module, I'm stuck in a bootloop. I experience the same bug when installing the Pixel Launcher module from Jaimbo. Is there any chance to get it fixed? Thanks for your work though!
CamilleBC said:
Hey, I'm having a bug. I have a SM-G935F s7 phone, using magisk v9, manager v2.5 and phh's superuser. When installing the module, I'm stuck in a bootloop. I experience the same bug when installing the Pixel Launcher module from Jaimbo. Is there any chance to get it fixed? Thanks for your work though!
Click to expand...
Click to collapse
Try Hydra ROM or "AOSP Engineering Build Samsung Factory"
I believe these would work
felixrao said:
has two contact apps
still in original dialer
Click to expand...
Click to collapse
This is not a bug
Flash a bigger opengapps package
anupritaisno1 said:
Try Hydra ROM or "AOSP Engineering Build Samsung Factory"
I believe these would work
Click to expand...
Click to collapse
Thanks, I'llt try those.
For some reason, after I installed this one my OnePlus One, I lost root (PHH superuser was installed). I had to reflash ROM, keeping stock root, to recover.
jhedfors said:
For some reason, after I installed this one my OnePlus One, I lost root (PHH superuser was installed). I had to reflash ROM, keeping stock root, to recover.
Click to expand...
Click to collapse
That isn't caused by my zip.
You shouldn't be using phh's superuser anyways
supersu.com here flash the correct superuser management app
Remember
Flash order is
SuperSU, magisk
Otherwise you may brick
jhedfors said:
For some reason, after I installed this one my OnePlus One, I lost root (PHH superuser was installed). I had to reflash ROM, keeping stock root, to recover.
Click to expand...
Click to collapse
anupritaisno1 said:
That isn't caused by my zip.
You shouldn't be using phh's superuser anyways
supersu.com here flash the correct superuser management app
Remember
Flash order is
SuperSU, magisk
Otherwise you may brick
Click to expand...
Click to collapse
Why should I not use PHH superuser? It is what is recommended for Magisk, and is what works with Magisk Hide.
I have been using that combination for some time now with no problems, and decided to give this module a try, after which I lost root. It is one thing to state that the module is not compatible with PHH superuser, but onother saying I should not be using the recommended one.
Could you clarify what you mean?
Thanks!
jhedfors said:
Why should I not use PHH superuser? It is what is recommended for Magisk, and is what works with Magisk Hide.
I have been using that combination for some time now with no problems, and decided to give this module a try, after which I lost root. It is one thing to state that the module is not compatible with PHH superuser, but onother saying I should not be using the recommended one.
Could you clarify what you mean?
Thanks!
Click to expand...
Click to collapse
You can use superSU or phh with magisk. Phh was recommended for magisk for some time because it helped in making Android pay work. Now that magisk breaks saftynet. There is really no advantage to using phh or super su. Magisk hide works with both super su and phh. Magisk hide only hides magisk and it's modules (from what I remember). But it is still up to you which you prefer. Just try flashing phh root zip again to see if you get root back.
harpin14789 said:
You can use superSU or phh with magisk. Phh was recommended for magisk for some time because it helped in making Android pay work. Now that magisk breaks saftynet. There is really no advantage to using phh or super su. Magisk hide works with both super su and phh. Magisk hide only hides magisk and it's modules (from what I remember). But it is still up to you which you prefer. Just try flashing phh root zip again to see if you get root back.
Click to expand...
Click to collapse
Not true. I'm using MagiskHide and ohh 266-2 and pass safety net. MagiskHide cannot hide SuperSU and that will break Safety net. People have reported using MagiskHide + SuoerSu + SUHide + RootSwitch and passing as well. Depends on what you want, but I definitely pass safety net with phh and Magisk hide.

[SOLVED]Magisk v10 - su binary out of date, but root still works

Since I upgraded from Magisk v9 to v10, every time I reboot my phone, I get a notification from phh's Superuser that says "Install Superuser" "The su binary is out of date." When I tap the notification, it just opens the Superuser app and doesn't ask me to update anything. Root still works normally, though. This is happening on a Nexus 5X running stock build NMF26F with no modifications other than Magisk itself, and no modules except for Superuser. The same thing happens whether Magisk Hide is on or off. I tried completely uninstalling and reinstalling Magisk, which didn't fix it either. What could be causing it, and how can I fix it?
EDIT: Solved: Magisk 10.2 includes a new version of the su binary that fixes this issue.
josephcsible said:
Since I upgraded from Magisk v9 to v10, every time I reboot my phone, I get a notification from phh's Superuser that says "Install Superuser" "The su binary is out of date." When I tap the notification, it just opens the Superuser app and doesn't ask me to update anything. Root still works normally, though. This is happening on a Nexus 5X running stock build NMF26F with no modifications other than Magisk itself, and no modules except for Superuser. The same thing happens whether Magisk Hide is on or off. I tried completely uninstalling and reinstalling Magisk, which didn't fix it either. What could be causing it, and how can I fix it?
Click to expand...
Click to collapse
This is because the su binary included in Magisk is a modified one & the official phh root manager detect that it is not equal to the lastest official su binary... just ignore that notification.
This happens on Magisk 9 as well I wish there was a way to turn it off but it's not really a big deal I guess.
Deic said:
This is because the su binary included in Magisk is a modified one & the official phh root manager detect that it is not equal to the lastest official su binary... just ignore that notification.
Click to expand...
Click to collapse
Yep, I did some poking around and confirmed that. (It's also entirely because of the new Superuser module, not the new Magisk). I guess as a workaround for now, I can block the Superuser app from sending notifications. The good news is this, though:
topjohnwu said:
Right now you still have to install the phh Superuser application, however the root management should move to Magisk Manager soon, please stay tuned.
Click to expand...
Click to collapse
This will take care of it. I'm not sure why he didn't wait to change the su version code until that was done, though, as that would have avoided this problem.
EDIT: And I also now see this listed as a known issue in the main Magisk post.
I am having the same issue, except none of my apps can see root.
kiefferbp said:
I am having the same issue, except none of my apps can see root.
Click to expand...
Click to collapse
It's not at all the same issue then. You should post about it in another thread.
josephcsible said:
It's not at all the same issue then. You should post about it in another thread.
Click to expand...
Click to collapse
Sorry if I sounded like one of those noobs that posts unrelated things in a random thread. I originally thought it was somewhat related since Magisk Manager said root was properly installed, but no other app recognized it.
I managed to fix that by un-installing and re-installing the phh superuser module. I am now just in the same boat as you, and I'll patiently wait for a fix.
kiefferbp said:
Sorry if I sounded like one of those noobs that posts unrelated things in a random thread. I originally thought it was somewhat related since Magisk Manager said root was properly installed, but no other app recognized it.
I managed to fix that by un-installing and re-installing the phh superuser module. I am now just in the same boat as you, and I'll patiently wait for a fix.
Click to expand...
Click to collapse
Can confirm. On Nexus 5x 7.1.1 with no other modifications, but lost root after I updated to v10. However, after an uninstall and reinstall I was back in business. One note though, the installation through magisk manager failed, and I had to manually flash the zip in recovery.
Fixed with Magisk 10.2.
josephcsible said:
Fixed with Magisk 10.2.
Click to expand...
Click to collapse
Magisk 10.2 here .. not fixed
warriorvibhu said:
Magisk 10.2 here .. not fixed
Click to expand...
Click to collapse
Make sure it automatically updated you to the topjohnwu r2 version of Superuser. If it didn't, do it manually from https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921. If that doesn't fix the problem, then your problem isn't this problem.
josephcsible said:
Make sure it automatically updated you to the topjohnwu r2 version of Superuser. If it didn't, do it manually from https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921. If that doesn't fix the problem, then your problem isn't this problem.
Click to expand...
Click to collapse
Yup all that done .. still have the same notification ..
I have the same problem.
1) i have tryed to flash magisk 10.2 by recovery but after flashing the s7 edge goes in bootloop (tyed with SuperSu disabled and without binary installed). So i had to flash the unistaller.
2) I even tryed enabled the chainfire SuperSu just for trying to flash the magisk+phh by magisk manager. Out of date. I think it cames cause magisk try to load the chainfire supersu binary and not the SU binary magisk has.
Help me please.
P.s. i have tryed with a clean boot image charged.
I had the same issue, and also noticed that su wasn't working in ADB. It looked like some permissions were wrong on the /magisk/phh directory. I solved it by uninstalling the phh superuser module from in Magisk Manager, then reflashing phh-superuser-topjohnwu-r2.zip in recovery.
Noxious Ninja said:
I had the same issue, and also noticed that su wasn't working in ADB. It looked like some permissions were wrong on the /magisk/phh directory. I solved it by uninstalling the phh superuser module from in Magisk Manager, then reflashing phh-superuser-topjohnwu-r2.zip in recovery.
Click to expand...
Click to collapse
Tryed, no well news!
Did y have SuperSu binary installed during flashing?
Mr.Fearless said:
Tryed, no well news!
Did y have SuperSu binary installed during flashing?
Click to expand...
Click to collapse
No, I haven't had SuperSU on here at all.
Noxious Ninja said:
No, I haven't had SuperSU on here at all.
Click to expand...
Click to collapse
I've just tryed deleting all the root binary files. Nothing, After flashing magisk 10.2 by recovery the phone goes to bootloop.
Thread closed at OP's request.

Disable Xposed Modules while Bootloop.

Hello
Flashed Xposed via Magisk Manager.
Tried several modules which worked until i got some outdated and now my phone is in bootloop.
Anyone know how i can deactivate Xposed?
Already tried the Xposed Disabler Zip and tried to delete the module list which doesn't exist on my phone.
I think thats cause i got "systemless Xposed".
What should i do now ? Maybe uninstalling Magisk so Xposed doesnt work anymore?
Thanks
Nico1300 said:
Hello
Flashed Xposed via Magisk Manager. Tried several modules which worked until i got some outdated and now my phone is in bootloop......
Click to expand...
Click to collapse
I don't use Magisk myself but, your best bet is to post this question within the following Magisk XPosed thread.
https://forum.xda-developers.com/showthread.php?t=3388268
If all else fails, and you don't receive any responses (within a reasonable amount of time) from the above thread, your next best bet is to ask for some member guidance within the following Magisk General Q&A thread.
https://forum.xda-developers.com/showthread.php?t=3432382
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Nico1300 said:
Hello
Flashed Xposed via Magisk Manager.
Tried several modules which worked until i got some outdated and now my phone is in bootloop.
Anyone know how i can deactivate Xposed?
Already tried the Xposed Disabler Zip and tried to delete the module list which doesn't exist on my phone.
I think thats cause i got "systemless Xposed".
What should i do now ? Maybe uninstalling Magisk so Xposed doesnt work anymore?
Thanks
Click to expand...
Click to collapse
Uninstalling magisk won"t help you much
Link below might help you out.
If modules are outdated or not working properly it would cause issues whether systemless or not.
https://www.didgeridoohan.com/magisk/MagiskModuleIssues
Sent from my Samsung Galaxy S8 using XDA Labs

Viper4Android Pie Compatible???

As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.
bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?
recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try
I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share
old legacy magisk module has been working for months and months.

Categories

Resources