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.
Related
I am about to install Magisk 12.0 but never used Magisk before and suddenly unsure if I need something together with Magisk, like SuperSU or similar?
BTJ
Ok, think I found it.. I can use MagiskSU and that one comes with Magisk-12.zip file?
Also, I see there is some talk about needing to install latest dm-verity and forced encryption disabler? I am running stock OOS 4.1.3 and just need root and perhaps install a custom kernel, for now .
Never mind.. Took a chance and installed twrp, Magisk 12 and Franco kernel and everything seems to be working...
xda890 said:
Never mind.. Took a chance and installed twrp, Magisk 12 and Franco kernel and everything seems to be working...
Click to expand...
Click to collapse
Exact same setup I'm running and it's working great! Time for you to start making some modules next...
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Did it really lose root? I've found that randomly when you open Magisk it will claim that it has no root access, but when you close it (exit the app and swipe it away from the recents menu) and reopen it it will start functioning properly again.
Neo3D said:
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Click to expand...
Click to collapse
Use un su zip first to remove the pre-installed root that rr has. Don't know if RR has root inbuilt now or not. But if it comes with root uninstall it and flash magisk on top of it and you are good to go
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
exodius48 said:
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
Click to expand...
Click to collapse
Did u remove built in root
shantam3108 said:
Did u remove built in root
Click to expand...
Click to collapse
If you installed magisk it will remove built in root automatically. -_-
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
I did some more searching and someone said just flash Magisk again. I did that and it worked! But, then I lost root again several hours later, seems so random? I flashed Magisk again and it worked again.
I can only get two green on Magisk, the third green seems to run forever, I left it on for 10+ minutes and it still showed "testing".
BTW, I didn't flash the uninstall Magisk zip before re-flashing. I tried that way and my phone got into a bootloop. Luckily, I had a TWRP backup.
Kris Chen said:
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
Click to expand...
Click to collapse
Thanks! I'll try this and see if it helps!
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
---------- Post added at 01:21 AM ---------- Previous post was at 01:20 AM ----------
Neo3D said:
Thanks! I'll try this and see if it helps!
Click to expand...
Click to collapse
Also keep in mind do run magisk without any modules first to check
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
Then why on AEX still loose root? It has no root prebuilt
exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Didgeridoohan said:
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Click to expand...
Click to collapse
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Neo3D said:
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
That's the one to use. :good:
Neo3D said:
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
Click to expand...
Click to collapse
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
[email protected] said:
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
Click to expand...
Click to collapse
I just flashed magisk again and safety passed!
Neo3D said:
I just flashed magisk again and safety passed!
Click to expand...
Click to collapse
Tell me how much time you have safety net pass?
[email protected] said:
Tell me how much time you have safety net pass?
Click to expand...
Click to collapse
Hi, what do you mean "how much time you have safety net pass?
Neo3D said:
Hi, what do you mean "how much time you have safety net pass?
Click to expand...
Click to collapse
This time after reinstalling magisk is it working till now?
Or root is gone after some time?
I have successfully installed Magisk on my device Root works but when I try to install a magisk module I get an error about not being able to mount magisk.img. When I try to install through recovery the module is flashes without any errors but once you open the app It displays "no modules installed". Before the G5s plus that I have a had the Moto G5 Plus. It had the same problem I just had to install another kernel over stock one and Magisk would work as expected. Is there a kernel for stock room that would support Magisk. Anyone else had this problem or is it just me?
ive no issue installing modules through magisk. Theres a lot of factors here. You didnt mention but id presume you installed magisk through recovery. Also, I presume you installed xposed. Maybe the modules your using require xposed to work. I forgot the exact steps to install xposed through magisk, but its not hard, and Id assume anyways you tried all of that. Have to flask xposed through recovery if I remember, then you can install xposed app apk too through recovery, then open magisk and install the latest xposed there. Im not using a stock rom, however Im fully confident if you properly rooted, and unlocked your phone of course, (I assume you did, just saying) its not a kernel issue. Sorry if I wasnt any help, its all i can think of right now.
When I got the phone I unlocked the bootloader and installed TWRP. When I set up my device I went back to recovery to install Magisk 14.3. It installed correctly and I got root using Magisk but when I try to install any module through the Magisk app I get an error. If I got you right should I try to install Xposed too? I was planning to install Xposed, Magisk version. But when I try that I get an error. I have attached a screenshot of when I try to install Xposed by topjohnwu and Greenify for Magisk. I get the same error.
well, xposed may not be your issue if you cant install any module with magisk manager. The modules, majority of them, if not all of them, i dont know, do not require xposed. Some do, most do not. Now please keep in mind, i could be wrong. I would say this, no harm in installing xposed, its basically a must get anyways for many awesome apps/modules. How you install, first install the xposed manager, youll have to look around for it, its not on the play store. Then downkoad magisk xposed through magisk. Once you download that zip file boot into twrp and install xposed through twrp.
This is a youtube on it: https://www.youtube.com/watch?v=MCcvsOp83A4 Now thing is, this may not fix any of your problems. But theres a chance it may. Like i said either way you want xposed on rooted phones anyways.
Patched kernel for stock. I have no problem running modules on Magisk. Flash in recovery.
https://forum.xda-developers.com/showthread.php?p=73930507
Sent by way of magic
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Ae3NerdGod said:
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Click to expand...
Click to collapse
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Ae3NerdGod said:
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Click to expand...
Click to collapse
Is there a thread for these kernels or any for G5S Plus?
THERAJ12 said:
Is there a thread for these kernels or any for G5S Plus?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g5s-plus/development/kernel-t3707143/post74562730#post74562730
wifi fixed btw
So I had trouble installing Viper through Magisk on Pie on my Exynos Note 9. It always told me to reinstall the drivers, but that didn't seem to work.
But I found a solution:
On XDA-Labs is a new version of viper available (Version 2.6):
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Simply install this version (I chose the beta), give it root permissions and you are set!
I also installed audio modification lib from Magisk to be on the safe side.
Only issue I noticed is that YouTube videos seem to hang for a few seconds before they start playing (I am using YouTube vanced from Magisk). Apart from that everything seems to be working well!
Hope that helps everyone who is having trouble on Pie!
It isn't asking me for root permission?
Strange.
But you are rooted with Magisk and have Magisk Manager installed?
Is the app showing up in Magisk Manager under the SuperUser section?
Maybe trying to install the app again solves your issue.
Rowe90 said:
Strange.
But you are rooted with Magisk and have Magisk Manager installed?
Is the app showing up in Magisk Manager under the SuperUser section?
Maybe trying to install the app again solves your issue.
Click to expand...
Click to collapse
Correct, and nope it isn't showing up in the superuser section. Re-installing did nothing, it isn't working without root, atleast that's why I think it isn't working.
aussiesausage said:
Correct, and nope it isn't showing up in the superuser section. Re-installing did nothing, it isn't working without root, atleast that's why I think it isn't working.
Click to expand...
Click to collapse
Yeah it needs root to put itself into some system files.
I just saw they released an update yesterday which is know marked as stable. (version 2.7). Maybe you have better luck with that.
It was working on 2.7 but it suddenly stopped
Now it's not enabled and not processing
Don't know how to fix
(Btw on Samsung Galaxy A8)
This was the only thing that worked. I've been trying different things and searching for hours. The stable version does not work on my exynos note 9. The beta does though!
Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you
urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!
For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.
One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.